[Q] Nexus 4 is being really weird - Nexus 4 Q&A, Help & Troubleshooting

So I've decided to switch to a more stable version of PAC, and when I flashed it on top of the latest nightly, things got really weird. So I decided to just reboot, wipe, and flash again. This time when I flashed it, it would go through setup but a dialog box would insistently pop up saying "system.android.phone has stopped". So I decide it must be a problem with PAC, so I go back, wipe, and flash Purity. This time I can't even get a setup wizard because a dialog box says that the setup wizard has stopped. What should I do? Should I just format everything and go from there? Thanks!

Yeah, that would be your best bet. Flash the factory image and start fresh.
Sent from my Nexus 4 using XDA Free mobile app

lolcakes203 said:
Yeah, that would be your best bet. Flash the factory image and start fresh.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
How would I get a factory image onto the device though? My computer recognizes the phone, but I can't get into USB debugging mode.

Are you wiping the system when you do your wipes?
I feel like I should make a poop joke....

Planterz said:
Are you wiping the system when you do your wipes?
I feel like I should make a poop joke....
Click to expand...
Click to collapse
LOL, I've the first time I hadn't, but when I flashed purity, I tried to wipe system but it wouldn't work still..

androidlosernoob said:
LOL, I've the first time I hadn't, but when I flashed purity, I tried to wipe system but it wouldn't work still..
Click to expand...
Click to collapse
Hm, I don't know then. Are you flashing anything else while/after flashing the ROM? You can flash a Gapps package after flashing the ROM before booting, but you really shouldn't flash anything else until you boot, load everything, then reboot.

Okay, so you're going to have to go into fastboot and plug your device in and navigate to your platform-tools folder in CMD and try
fastboot devices
to see if it recognizes your device. If it does than you can follow the instructions around here on XDA to flash the factory image onto the device. I think all you have you have to do is click on "flashall.bat" or something like that and it will flash the entire stock image to your device.
Sent from my Nexus 4 using XDA Free mobile app

Planterz said:
Hm, I don't know then. Are you flashing anything else while/after flashing the ROM? You can flash a Gapps package after flashing the ROM before booting, but you really shouldn't flash anything else until you boot, load everything, then reboot.
Click to expand...
Click to collapse
So I tried flashing Purity again and wiping system, without flashing Gapps and it worked. But when I flashed gapps, this constant dialog box saying setup wizard has stopped came up. What should I do? Just start from a clean slate?

Related

[Q] Nexus 7 Failed ROM Flash Help!

I have CWM 6.0.1.0 on my nexus 7. I was rooted but running the stock ROM. I wanted to flash CM10. I booted into recovery, wiped cache, dalvik, and factory reset. I then flashed the .zip file. When I rebooted the device it never got out of the CM boot screen. That circle just kept spinning. I tried the toolkit but the drivers aren't really working on my computer (crappy old XP laptop). I have formatted the system and SD card out of desperation which was honestly a stupid thing to do. So, where I am at now. I have no way to boot into android. Everything is wiped and formatted. Toolkit, adb, nor fastboot will work. I thought fastboot would save me but I can't get it work. Not even on my wife's mac. So what are my options? Please let me know if there is something important I am leaving out.
It can take a while to get a new rom up and running. How much time did you give CM to install before you interrupted it?
Visa Declined said:
It can take a while to get a new rom up and running. How much time did you give CM to install before you interrupted it?
Click to expand...
Click to collapse
I let it go for at least 30 minutes. I finally got adb to push a ROM to the device. Problem solved. Thanks though.
agroan05 said:
I let it go for at least 30 minutes. I finally got adb to push a ROM to the device. Problem solved. Thanks though.
Click to expand...
Click to collapse
maybe it was a bad download?
It can stand a spell to get a new rom up and jetting. How some instant did you utilize CM to install before you broken it?
redundant409 said:
maybe it was a bad download?
Click to expand...
Click to collapse
Thats possible. I tried re-flashing it numerous times but they all got stuck in boot. I am now up and running with SmoothROM. I might have to re-download CM10 sometime and try again.
Hey guys I now has a similar problem. I flashed a bad copy of my Rom and when it failed to boot I too wiped everything in desperation. I know I'm an idiot! Now I need to push both a Rom an kernal to my root directory but I'm not clear on how to install my kernal. Once I push my Rom I can use my recovery to install the Rom. But how do I install the kernel? I'm using cleanrom which comes zipped with the kernal. I can't fastboot flash it because I cannot turn on USB debugging. Gary
Sent from my HTC PH39100 using Xparent Red Tapatalk 2
kelnhofer said:
Hey guys I now has a similar problem. I flashed a bad copy of my Rom and when it failed to boot I too wiped everything in desperation. I know I'm an idiot! Now I need to push both a Rom an kernal to my root directory but I'm not clear on how to install my kernal. Once I push my Rom I can use my recovery to install the Rom. But how do I install the kernel? I'm using cleanrom which comes zipped with the kernal. I can't fastboot flash it because I cannot turn on USB debugging. Gary
Sent from my HTC PH39100 using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
To use fastboot you don't need to have switched on USB debugging, it's sufficient to go to bootloader mode and connect your PC to it.
(If you have already installed the correct drivers on your PC.)
Sent from my Nexus 7 using xda app-developers app

[Q] Rooted, CM 10.1, clean rom, now stuck...need help!

Hey, I could really use some guidance here. I'll present the information as simply as I can:
I bought a Galaxy s4 AT&T a few days ago. I've been interested in rooting and flashing different roms, but I think I may have done a bit too much.
I rooted using the motochopper method - great, worked like a charm.
I made a backup of my original rom using CWM. I even took that backup and saved a copy of it on my Mac - perfect.
I thought I'd try Cyanogenmod 10.1, so I downloaded the latest nightly build and flashed it using CWM - so far so good.
Everything was working fine, but my LTE (or any data) was not working at all. I could use Wifi, but once I turned wifi off, I had no data, no gps, no 3g, no 4g, no LTE. I tried the *#*#4636*#*# method, the LTEOnOff app, and changing my APN based on the recommendations provided in this thread - I just couldn't get it to work.
I thought I'd try restoring my original backup, but when I went into CWM to do so, it said that my backup could not be found...(I still have a backup on my computer, just in case)
I needed my phone to work, and badly needed LTE to do so. So, I downloaded this rom: [ROM] CleanROM 1.0 -★| Clean and Smooth! | The Way Nature Intended! |★-
So far, this rom was working fine - it's just a debloated version of TouchWiz - which I like. But, here's my problem now - If my phone reboots, it stays frozen on the Samsung logo (with unlocked lock logo underneath), and I can't get past it. I'd have to go BACK into recovery, and flash the CleanROM all over again, and set my phone up as new with all data wiped.
I really need my phone to work again, and I don't know where to go from here. What options do I have left? What can I do to get out of that frozen Samsung loading screen? Can't I just reset my phone to the way it was? Can't the CM10.1 rom work with LTE?
Your help will be greatly appreciated.
Your best option is to flash the stock MDB firmware via odin . After you get the PASS on Odin go ahead and manually boot into stock recovery and wipe data factory reset again then reboot. You will have to re root and reinstall recovery but this will take care of any issues you had from a bad flash.
http://forum.xda-developers.com/showthread.php?t=2261573
Sent from my GT-I9505G using Tapatalk 2
mavverick said:
Hey, I could really use some guidance here. I'll present the information as simply as I can:
I bought a Galaxy s4 AT&T a few days ago. I've been interested in rooting and flashing different roms, but I think I may have done a bit too much.
I rooted using the motochopper method - great, worked like a charm.
I made a backup of my original rom using CWM. I even took that backup and saved a copy of it on my Mac - perfect.
I thought I'd try Cyanogenmod 10.1, so I downloaded the latest nightly build and flashed it using CWM - so far so good.
Everything was working fine, but my LTE (or any data) was not working at all. I could use Wifi, but once I turned wifi off, I had no data, no gps, no 3g, no 4g, no LTE. I tried the *#*#4636*#*# method, the LTEOnOff app, and changing my APN based on the recommendations provided in this thread - I just couldn't get it to work.
I thought I'd try restoring my original backup, but when I went into CWM to do so, it said that my backup could not be found...(I still have a backup on my computer, just in case)
I needed my phone to work, and badly needed LTE to do so. So, I downloaded this rom: [ROM] CleanROM 1.0 -★| Clean and Smooth! | The Way Nature Intended! |★-
So far, this rom was working fine - it's just a debloated version of TouchWiz - which I like. But, here's my problem now - If my phone reboots, it stays frozen on the Samsung logo (with unlocked lock logo underneath), and I can't get past it. I'd have to go BACK into recovery, and flash the CleanROM all over again, and set my phone up as new with all data wiped.
I really need my phone to work again, and I don't know where to go from here. What options do I have left? What can I do to get out of that frozen Samsung loading screen? Can't I just reset my phone to the way it was? Can't the CM10.1 rom work with LTE?
Your help will be greatly appreciated.
Click to expand...
Click to collapse
Factory Reset
Wipe Cache
Wipe Dalvik
Format /system
Flash ROM or ROM and gapps if AOSP
Reboot
KingKongDingDong said:
Factory Reset
Wipe Cache
Wipe Dalvik
Format /system
Flash ROM or ROM and gapps if AOSP
Reboot
Click to expand...
Click to collapse
Having the same issue so I figured I'd give these steps a shot. Followed them exactly and phone (AT&T S4, TWRP) would won't even reboot the first time into CleanROM. I'm stuck on the Samsung screen with the lock.
edit: I've noticed that now, when I reboot into TWRP, it prompts me for a password. Hitting cancel takes me to the regular home screen, but I had not been getting the password prompt before attempting to install CleanROM. A permissions issue, perhaps?
edit 2:
I've just spent some time trying a bunch of things with bits of good luck surrounded with tons of bad. Below are the steps I've taken to try to get CleanROM to boot (and reboot) without any issues. Hopefully they help figure out the issues we're having.
Wipe Cache
Wipe Dalvik
Wipe /system
Flash CleanROM
Reboot
---- Failed
Reboot into Recovery
Prompted for password, hit cancel
Fix permissions
---- Failed
Reboot to recovery
Prompted for password, hit cancel
Format data (type yes)
Reboot
---- Successfully booted to CleanROM
Ran through phone / account setup
Saw home screen
Powered off and then back on (not using reboot)
---- Failed
Reboot to Recovery
No longer prompted for password
Factory Reset
Attempt to Fix Permissions: failed
Restore default settings
Reboot system
---- Failed
Reboot to Recovery
Prompted for Password, hit cancel
Format Data (type yes)
Reboot System
--- Successfully booted to CleanROM
Ran through phone / account setup
Saw home screen
Reboot (using reboot, not power off / on)
---- Failed
Reboot to Recovery
Prompted for password, hit cancel
Factory Reset: failed
Restore Default settings
Prompted for password, hit cancel
Factory Reset: failed
* Internal Storage showing 0MB (as if it's not reading it correctly)
Fix Permissions
Prompted for password, hit cancel
Nothing has changed, my phone is currently chilling in TWRP
MJHawaii said:
Your best option is to flash the stock MDB firmware via odin . After you get the PASS on Odin go ahead and manually boot into stock recovery and wipe data factory reset again then reboot. You will have to re root and reinstall recovery but this will take care of any issues you had from a bad flash.
http://forum.xda-developers.com/showthread.php?t=2261573
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
This. You decided to ignore this post for some reason.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
cuffed zhesea
Cataligh said:
This. You decided to ignore this post for some reason.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I can't speak for OP, but I was hoping there was another way to rectify what has already been done without flashing stock seeing as how I'm on OSX. If that's the only option, then so be it.
Hey. Thanks for the feedback in this thread. I flashed factory through Odin, and everything is working fine. I then factory reset my phone through factory recovery. I'm back to standard touchwiz with all the bloat lol.
I'm going to wait until there a more stable release of cm10.1 - that was a good rom.
Appreciate all the help people!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Your best bet is do what "cataligh" mentioned... flash back to stock via odin...
Sent from my SAMSUNG-SGH-I337 using xda premium
When you flashed cm10 it probably wipe the internal sdcard, you should ALWAYS do you backups to the extsdcard...period.
TheAxman said:
When you flashed cm10 it probably wipe the internal sdcard, you should ALWAYS do you backups to the extsdcard...period.
Click to expand...
Click to collapse
Yeah, absolutely! I always backed up and flashed roms from my external SD.
mavverick said:
I'm going to wait until there a more stable release of cm10.1 - that was a good rom.
Click to expand...
Click to collapse
waiting is for simpletons. get aokp and transcend...
jaboles said:
I can't speak for OP, but I was hoping there was another way to rectify what has already been done without flashing stock seeing as how I'm on OSX. If that's the only option, then so be it.
Click to expand...
Click to collapse
As I mentioned before starting over is always the Best and Safe way to go. Shortcuts will only cause you headaches and possibly get you a brick that is why you see Odin stock threads. Do yourself a favor and start over I know it sucks but when your modifying your phones its gonna happen once in awhile.
Sent from my GT-I9505G using Tapatalk 2
MJHawaii said:
As I mentioned before starting over is always the Best and Safe way to go. Shortcuts will only cause you headaches and possibly get you a brick that is why you see Odin stock threads. Do yourself a favor and start over I know it sucks but when your modifying your phones its gonna happen once in awhile.
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
Wise words. Took your advice, installed Windows with boot camp, and got back to stock via odin.
I am going to say something about this thread, we are all giving advice on how to do this and that, and not once is it mentioned anywhere....in the OP
WHAT DEVICE WE ARE TALKING ABOUT! PLEASE STATE THE DEVICE WHEN NEEDING HELP!
The Ax says, I apologize if I missed what device.
TheAxman said:
I am going to say something about this thread, we are all giving advice on how to do this and that, and not once is it mentioned anywhere....in the OP
WHAT DEVICE WE ARE TALKING ABOUT! PLEASE STATE THE DEVICE WHEN NEEDING HELP!
The Ax says, I apologize if I missed what device.
Click to expand...
Click to collapse
My original question was for the AT&T version of the Galaxy S4 - i337.
xBeerdroiDx said:
waiting is for simpletons. get aokp and transcend...
Click to expand...
Click to collapse
Welllllll I just tried installing AOKP as well (Task650). Buttttttt, same issue with the LTE stuff. I tried reviewing all the APN settings, but didnt get any data connection on my phone except for wifi.
mavverick said:
Welllllll I just tried installing AOKP as well (Task650). Buttttttt, same issue with the LTE stuff. I tried reviewing all the APN settings, but didnt get any data connection on my phone except for wifi.
Click to expand...
Click to collapse
What APN settings were you using?
Sent from my SAMSUNG-SGH-I337 using xda premium
doktor buknasty said:
What APN settings were you using?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Yeah, data was enabled - and I was using ATT LTE apn settings that I found on these forums. I made sure to use the right now. Plus, when I rebooted my phone, it got stuck on the Samsung lock screen again...
Juuuuust ODINed back to factory right now for the second time :crying:
Was it these settings:
Sent from my SAMSUNG-SGH-I337 using xda premium
doktor buknasty said:
Was it these settings:
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Yes, those were the exact settings that I used. Is it possible that I could have a defective phone or sim card?
Right now, I am on factory touchwiz with root enabled, and my phone is working perfectly fine. I can reboot, use LTE, everything. The problem starts when I load any CM or AOKP rom...

[Q] CM10.1.2 Bootloop

I was having a ton of problems with my Nexus 4, like i mean a TON
so I decided to just fix it and factory reset my phone. I rooted it with the nexus 4 tool kit and flashed TWRP. I found the CM10.1.2 zip and the 4.2.2 GAPPS. Flashed the ROM, then the GAPPS, then cleared both caches and Rebooted my phone. It is stuck at the spinning CM circle boot logo forever (I even left it on all night). I tried flashing CM10.1.0 with the 4.2.2 GAPPs same process and still in a boot loop. WTH is going on. I'm so frustrated. My phone was wiped clean and the only app I have is a file explorer besides the preinstalled Google apps.
Help.
I made a backup of when I freshly rooted my phone so I don't have to keep rooting when I enter recovery to get away from the boot loop
Before you flash the ROM did you do factory reset? Go into twrp do a factory reset then flash ROM and gapps then reboot it shouldn't take more then 5 mins for it to boot
From my BLACKED OUT N4
What's the point of XDA,,,, no one ever answers my posts.
michaelsp9 said:
What's the point of XDA,,,, no one ever answers my posts.
Click to expand...
Click to collapse
I answered your post. The point of XDA is to share development work and learn how it works but if you're using a toolkit and not reading you'll never learn that's why you've had "a ton of problems" and don't know how to fix it
From my BLACKED OUT N4
spaceman860 said:
I answered your post. The point of XDA is to share development work and learn how it works but if you're using a toolkit and not reading you'll never learn that's why you've had "a ton of problems" and don't know how to fix it
From my BLACKED OUT N4
Click to expand...
Click to collapse
Sorry I never saw your reply. Thanks for replying. I did a factory reset from the settings menu NOT from within TWRP. And the toolkit is not to blame because I've used it plenty of times before and has not caused any problems. All it does is root my phone.
Umm you need to wipe within twrp before you flash. You're bootlooping because you only did a factory reset which only deletes cache and stuff. Wipe from within twrp and then flash
Sent from my Nexus 4 using xda app-developers app
Warbuff said:
Umm you need to wipe within twrp before you flash. You're bootlooping because you only did a factory reset which only deletes cache and stuff. Wipe from within twrp and then flash
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I wiped from within TWRP, rebooted and then my attenas were not working again. I could at least see the networks in my area but I could never connect on WiFi- it kept saying "Authenticating". It also said "No Service" for my 3G.
I booted back into TWRP and went into the advanced options for wiping and selected everything besides some "usb" thing and I think I deleted my OS -__- . I'm an idiot I should really not do what I don't know. I'm just going to flash stock ROM (4.2.2) with the Nexus 4 Tool Kit and see if things improve.
Thanks for your help.
In twrp if you're flashing a different always do the advanced wipe in order to clear the previous rom. Doing the basic wipe in twrp has the same effect of factory reset from earlier
Sent from my Nexus 4 using xda app-developers app

[Help Needed] Infinite Bootloop on Nexus 4

I have a N4 which was unlocked and rooted after updating to 4.3. I figured, I'd give Franco Kernel a shot so I proceeded to download the Franco Updater from Google Play.
Selected automatic flash and reboot and now it's stuck in a perpetual boot state. I attempted to proceed with a hard reset through the recovery mode; using ClockworkMod Recovery. I wiped my data, cache and dalvik cache and then went on to reboot system.
Up till' now, my N4 is on the boot Google screen. I tried doing the above steps multiple times but the results remain the same.
I'd appreciate if any help is directed on how I would be able to reset my device to factory settings. I don't mind going through the unlocking and rooting process again; I just need it to get through the boot screen
Go to the bootloader and run this tool: https://developers.google.com/android/nexus/images#occamjwr66v
It works every time.
Something went wrong with the flash for sure, I can tell in many ways so wiping will not help anyway unless you flash an other kernel.
This will wipe EVERYTHING so I don't know if it is worth flashing or flash an other kernel, you choose.
Sent from my Nexus 4 using Tapatalk 4 Beta
andyabc said:
Go to the bootloader and run this tool: https://developers.google.com/android/nexus/images#occamjwr66v
It works every time.
Something went wrong with the flash for sure, I can tell in many ways so wiping will not help anyway unless you flash an other kernel.
This will wipe EVERYTHING so I don't know if it is worth flashing or flash an other kernel, you choose.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Alright so I've downloaded the necessary file from your link, how do I go about running it? I apologize if this is a silly question to surface.
omgzam said:
Alright so I've downloaded the necessary file from your link, how do I go about running it? I apologize if this is a silly question to surface.
Click to expand...
Click to collapse
Make sure it is Mako/Occam.
What ever android version you chose extract the file twice until you get to the contents and run flash_all.bat, if the script says that you are missing the Fastboot file you have to get it from the SDK.
Make sure your device is on the bootloader which is unlocked.
Sent from my Nexus 4 using Tapatalk 4 Beta
andyabc said:
Make sure it is Mako/Occam.
What ever android version you chose extract the file twice until you get to the contents and run flash_all.bat, if the script says that you are missing the Fastboot file you have to get it from the SDK.
Make sure your device is on the bootloader which is unlocked.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm guessing this doesn't work on Mac? Because I'm currently on my Mac machine at work. If it's only for Windows, I gotta try it when I get home later.
omgzam said:
I'm guessing this doesn't work on Mac? Because I'm currently on my Mac machine at work. If it's only for Windows, I gotta try it when I get home later.
Click to expand...
Click to collapse
There is .sh has well which should work on Mac BUT you have to go though a lot with drivers.
FACT: Google Developers use Mac.
Sent from my Nexus 4 using Tapatalk 4 Beta
andyabc said:
Go to the bootloader and run this tool: https://developers.google.com/android/nexus/images#occamjwr66v
It works every time.
Something went wrong with the flash for sure, I can tell in many ways so wiping will not help anyway unless you flash an other kernel.
This will wipe EVERYTHING so I don't know if it is worth flashing or flash an other kernel, you choose.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Just to be clear, this solution is just to flash your device back to stock.

Deadliest bootloop ever. Nothing seems to fix it.

I recently fixed an infamous bootloop i had by letting the battery die 100% (yeah I know it is bad), and then it booted. Well i went to flash a new rom and it never rebooted. I then went to flash stock from google. Still a bootloop. tried like 3 roms, still a loop. I then tried the killing my battery thing. Still a loop. Please, i know the phone isn't hard bricked, is there anything else i can do to boot it other than just flashing stock and factory resetting. Thanks.
Another thing, when i try to flash 4.2.2 the phone doesn't go to the boot logo.
Anybody? I need to fix this phone soon.
Wrong thread sorry
YFBanana said:
Anybody? I need to fix this phone soon.
Click to expand...
Click to collapse
Fastboot flash the factory image. Then boot into the stock recovery and do a factory reset.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Fastboot flash the factory image. Then boot into the stock recovery and do a factory reset.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
unfortunately that doesn't work, i have tried it many times.
YFBanana said:
unfortunately that doesn't work, i have tried it many times.
Click to expand...
Click to collapse
Then you have an issue with your device. What happens if you lock the bootloader and then reboot? Does it stay locked or is it still unlocked?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Then you have an issue with your device. What happens if you lock the bootloader and then reboot? Does it stay locked or is it still unlocked?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It stays locked. I am guessing thats a good thing?
YFBanana said:
It stays locked. I am guessing thats a good thing?
Click to expand...
Click to collapse
Yep, if it didn't your emmc flash memory would be bad. I'd try re-downloading the factory image and trying again. Are you using the flash-all.bat to flash? You might try flashing all the components separately and see if any of them fail.
Sent from my Nexus 5 using XDA Free mobile app
You flashed stock firmware and it didn't work? What did it do when you flashed it?
Sent from my Moto G running Carbon ROM 4.4.4
jd1639 said:
Yep, if it didn't your emmc flash memory would be bad. I'd try re-downloading the factory image and trying again. Are you using the flash-all.bat to flash? You might try flashing all the components separately and see if any of them fail.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
None of the flashes failed. I have tried redownloading and i have also checked the md5's, so i dont think that would be it. I have also tried reformatting through twrp, and then flashing stock. Still nothing.
flashing 4.4.4 separately got me on the starting apps step, but that seems to be the place where it gets stuck.
I need to decide if i wanna take another month trying to fix the nexus 4 or just get the nexus 5. Nothing is working and i think i should just leave it now. But at the same time, i just wanna fix it so i don't have to spend money on a new phone. I have run out of things to try and revive the phone so i don't know what to do anymore.
YFBanana said:
I need to decide if i wanna take another month trying to fix the nexus 4 or just get the nexus 5. Nothing is working and i think i should just leave it now. But at the same time, i just wanna fix it so i don't have to spend money on a new phone. I have run out of things to try and revive the phone so i don't know what to do anymore.
Click to expand...
Click to collapse
so now you can boot to 4.4.4 ROM but your phone stuck at the "Starting apps" box rite?
groovepeppy said:
so now you can boot to the ROM? but never pass the "Starting apps"?
Click to expand...
Click to collapse
I think it was just the order i flashed the img files that made it go to that point, but i am pretty sure starting apps is where it gets stuck every time.
YFBanana said:
I think it was just the order i flashed the img files that made it go to that point, but i am pretty sure starting apps is where it gets stuck every time.
Click to expand...
Click to collapse
You can fastboot your phone i believe, you should try [HOW-TO] How to flash a factory image / return to stock / unlock / root #
Start from point C
I hope you haven't tried it yet
groovepeppy said:
You can fastboot your phone i believe, you should try [HOW-TO] How to flash a factory image / return to stock / unlock / root #
Start from point C
I hope you haven't tried it yet
Click to expand...
Click to collapse
I have tried it. Still no boot.
YFBanana said:
I have tried it. Still no boot.
Click to expand...
Click to collapse
there's must be a way cause you can boot on 4.4.4 but unfortunately i'm not that good in these kind of problems
but i hope you can find the cure soon
You can obviously get into flashboot, have you tried booting the latest twrp, wiping /system /data /cache and sideloading something different, like Paranoid Android?
Bootloop fix
First thing is that you have use Wug's Tool and flash the 4.3 stock image. In the Wug's tool select the option 'SOFT BRICK or BOOTLOOP' option and then flash the stock image in the fastboot mode. Definitely, I hope the phone will launch without any problem. The same problem I had faced with my nexus 4 and I flash the 4.3 stock image with the help of Wug's tool. Try it I hope it will fix the problem.

Categories

Resources