Hi guys,
so, my LG G5 has just been sent in for RMA, meaning I need a phone while I wait for that, and I have a nexus 4, however, it is stuck in a bootloop. I can access fastboot and adb, and have tried flashing Android 4.4.4 and 5.1.1, with 5.1.1 reaching "Android is starting, loading apps" as the final screen and so far with 4.4.4, just on the google colours booting animation.
I've also tried clearing cache partition, and factory resets. Currently I am using googles flash_all script, but would it be worth flashboot flash recovery etc. etc.
Could anyone suggest how I go about things to fix this?
Thanks, Conn
update
So, as of yet, I have got it to boot into 4.2.2, however, it isn't reading a brand new sim card. also updating to 4.3 through software update causes bootloop, and 4.2.2 seems to be the only working android version. I tried installing custom recovery (twrp) and a custom os (lineage 14.1) and that bootlooped.
Thanks, Conn
EDIT: Also, the IMEI is not being displayed.. From what I've read, the phone is probably stuffed?
It the OS can't read the IMEI, yeah sounds like something is borked.
Are you running flashall wiping everything, or did you take out hte -w switch to leave personal data? I've had issues with my 4 (that led to my buying a refurb 5) that trying to flash but keeping personal data failed, I had to do a full open hose reflash.
\\ Sent from an Android or iOS device //
Related
Hello, a friend of mine gave me his nexus 4 to try and repair. He claims that it was running 4.4.3 and he attempted an OTA update of 4.4.4 and it had failed and ever since it has been stuck in a boot loop.
Well... I have unlocked the bootloader, installed twrp wiped all the data, downloaded Nexus Root Toolkit to make my life easier, and did the flash stock to 4.4.4 BUT it still will not get out of boot loop...... so after try to reinstall twrp in fastboot I wipe the cache, it now will get past the boot logo and on to the updating apps... screen, and hangs there! after a reboot it then hangs at the boot animation.
so i tried to wipe with twrp and just manually flash the stock rom using the fastboot commands... this gives the same results.
frustrated but not giving up I tried installing stock 4.2.2... and of course it boots.... but now all attempts to update from 4.2.2 to 4.3 or 4.4.2-4.4.4 with a full on flash from twrp does not work and just goes back into the boot loop.....
I even tried sideloading some custom roms! PLEASE HELP THIS MAKES NO SENSE TO ME!!!
I think this is normally caused by proximity sensor issue, does your sensor work properly in 4.2.2?
DrFredPhD said:
I think this is normally caused by proximity sensor issue, does your sensor work properly in 4.2.2?
Click to expand...
Click to collapse
how do i check the sensor? also i tried putting my working simcard into the phone and it does not register. possibly a problem with the radio?
Normally I'd make a call and cover/uncover the top of the phone but if it's not reading sims that'll be a problem (does it say no SIM or something else eg. emergency calls only). If you flashed full factory image radio should have been flashed too. Does your IMEI show when you dial *#06#
Hi folks,
I recently rooted by N4. It was running Android 5.0.
I also have MultiROM installed, with CyanogenMod installed as a secondary ROM.
I didn't realise I couldn't apply the OTA updates to the stock Android system (my oversight), and I allowed the device to download and (attempt an) the recent 5.0.1 update from Google.
When the update attempted to reboot the device, I could see in the terminal data that popped up, that it failed.
After that device now gets stuck in the booting stage with the little coloured balls drifting around.
I continued to use my phone with the secondary ROM (Cyanogen) for some days until I had time to sort this out.
MY ATTEMPTED RECOVERY
I read that ordinarily on a rooted device one would manually apply the various image files from the full 5.0.1 package.
So, following instructions found here: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Using method two (long method).
... In fastboot mode I flashed the system, boot, recovery, cache (after clearing cache), radio images from the 5.0.1 stock image.
At first I didn't flash the bootloader (as I wanted to maintain the multiboot loader I had installed) nor the user.img (I don't want to lose my user data). I read this should work. But it didn't.
When it came to booting into recovery mode to finish the process, an android icon with a ! warning on it would appear, and I could not do the recovery.
So, I have since flashed the bootloader also. That didn't change much, except that my dual-boot boot loader is now gone, and the device is still not recoverable.
Is there something I am not doing correctly? How can I recover this device so that it has 5.0.1, my existing user data, and my existing dual boot bootloader?
Cheers,...
May have solved it...
I'll post another update in a moment. Posting this just in case someone starts responding to my question in the interim.
After further fiddling around, I may have resolved this issue. I've managed to get it into recovery menu, rebooted from there, and device is now in "Android is updating" mode. Looking good.
Will post new message soon as to whether this was successful or not.
Issues continue
So, after the device booted a screen appeared for a fraction of a second, that appeared to be the screen for selecting system language (as per what happens when a device is first run after a clean install). But the screen almost instantly goes black except for the little network icon and battery icon and time in the top right of the screen.
If I use the power button to lock the screen and again to activate it, the screen very briefly flashed up the language selector, then goes blank again.
So... it seems something odd is happening after applying the 5.0.1 file.
Any suggestions?
Flash the 5.0.1 factory image with fastboot
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Flash the 5.0.1 factory image with fastboot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well, this is what I resorted to doing. And it worked. Phone started and was as new. Of course, I lost my user data which is a ****. I did pull the SDCARD content over ADB, but am not sure how I'd go about pushing it all back on, into right locations, etc.
BUT—and it's a BIG BUT—when I re-rooted it and applied SuperSu, it couldn't be put into recovery mode any more. It would keep running through the SuperSu install process each time I'd attempt to go into Recovery.
I ended up ignoring this, and installing Busybox (with Play) and SuperSu.apk (via Play). But the SuperSU apk would keep saying its files needed to be installed/updated.
I forget the exact mess that unfolded, but eventually (after installing MultiROM) I could boot the phone as it would ALWAYS go into (custom) recovery.
So I starter the whole process again, with another clean install of 5.0.1, and yet now it is stuck at the bootloader (the little swirling balls screen).
AndroidWelcome said:
Well, this is what I resorted to doing. And it worked. Phone started and was as new. Of course, I lost my user data which is a ****. I did pull the SDCARD content over ADB, but am not sure how I'd go about pushing it all back on, into right locations, etc.
BUT—and it's a BIG BUT—when I re-rooted it and applied SuperSu, it couldn't be put into recovery mode any more. It would keep running through the SuperSu install process each time I'd attempt to go into Recovery.
I ended up ignoring this, and installing Busybox (with Play) and SuperSu.apk (via Play). But the SuperSU apk would keep saying its files needed to be installed/updated.
I forget the exact mess that unfolded, but eventually (after installing MultiROM) I could boot the phone as it would ALWAYS go into (custom) recovery.
So I starter the whole process again, with another clean install of 5.0.1, and yet now it is stuck at the bootloader (the little swirling balls screen).
Click to expand...
Click to collapse
Try a full wipe from Factory Recovery, and see if it will fix the bootloop.
Bootloop no more...
ariesgodofwar said:
Try a full wipe from Factory Recovery, and see if it will fix the bootloop.
Click to expand...
Click to collapse
(wiping the sweat from his brow...)
After many tedious hours of messing around with this beast... there is life beyond the bootloop.
Back to a stock install.
So, now I am wondering why the SuperSu/Root process didn't work on my last round on this.
The SuperSu installer would kick in EVERY time I went into Recovery mode, and would then reboot the phone. This made it impossible to do things with ADP because I essentially couldn't get into recovery mode. I wanted to push through some of the stuff I pulled using ADP before I wiped the phone previously.
I installed MultiROM (which includes TWRP [is that what it's called] recovery system. BUT then go stuck in a Recovery loop.
Not wishing to repeat that fiasco... does anyone more knowledgeable than I (not a difficult status to achieve) have any suggestions to what might have caused those issues?
So, yesterday i tried to install Euphoria OS on my phone, but in all of a sudden, the /cache partition corrupted, i was dumb enough and deleted it via TWRP, making my phone fall into the QPST status.
After fixing it, i proceeded and reflashed KitKat, but the phone only shows 8GB instead of 16GB, so i tried to fix this by flashing TWRP, everything went well, until i upgraded to Lollipop again.
It always bootloops no matter what i do, i really need my phone with my 16GB of storage back, it isn't a Hardware failure since the QPST diagnosis didn't say anything about mobo failures.
I can mount all the partitions, i can wipe it all, i can boot into bootloader and recovery, i can do basically everything but booting the system.
Any light on this? it either happens after i flash TWRP or after i try to root it.
Im running Android 5.1.1 stock.
List of tutorials i have tried (In order): http://forum.xda-developers.com/nexus-4/general/wip-unbricking-nexus-4-using-qpst-t2208289
http://forum.xda-developers.com/nex...unbrick-n4-t2347060/post43164157#post43164157
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632
Don't you dare tell me to reflash the ROM again, this is the first thing i have done, i did this 20 times already and it never worked. It isn't a ROM problem. It is a partition problem somewhere.
Fixed, had to use LGNPST to reflash JB 4.4.2, then upgraded to a ZIP version of the Lollipop ROM, then flashed the stock one.
I'm having the same problem with my Nexus 4. I read also about LGNPST, but I remember something about flashing the Optimus G cache partition I believe, then manipulating one of the prop files afterwards in order to get your 16gigs back. The problem is that all of the files needed to do this flash are attached to a stupid downloader site and so its full of pop up windows and adware from what I've seen. I can't get mine to boot into system, or bootloader, or recovery, etc. The device will not finish looping for debugging to be enabled, and even trying to boot into download mode is not happening. I've tried all I know to do, especially considering fastboot and adb both utilizeusb debugging. I really am baffled. Any root kits I've tried also don't work so far. Help please.
I have 6p since last year 6p is a fantastic phablet , it's been a great experience until yesterday , I was chatting with someone and suddenly everything freezes and then it restarts and stuck on Android logo and restarts again ... And this continues ,so somewhere I read that it because of Android n so I flash latest MARSHMALLOW (MTC20L) factory image and luckily it BOOTS up ,but The real problem is when every I flash any version of android N It starts DOING BOOTLOOP ,, I wanted ANDROID N , so someone know any way to flash it without bootloop ,, help !!!
First off, you could have provided a lot more detail about exactly how (and what) you flashed without shouting. Your post for help comes off like a panicked rant. What is your current configuration... stock rom? rooted? stock kernel? stock recovery? encrypted? My advice would be to stop flashing your device for now. If you haven't done so already, confirm that your bootloader is unlocked. Next, make full partition backups including EFS, and store them somewhere off the phone. Now you can start reading on how to flash correctly with the least amount of risk.
Sorry for bad English
My 6p's bootloader is unlocked and I was using it with latest stock Android 7.1.1 with ElementalX since last month then years suddenly it freezes and stuck on boot loops then I flash Android 6.0 latest and it works fine on it ,and doesn't goes under boot loop but when ever I flash Android 7 it stuck on bootloops ,
I have a full TWRP backup of my android developer preview 4 ,I also restored it but still same bootloop issues with android 7 Roms , I also tried latest factory image of Dec,16 android 7.1.1 ,but still no luck
Once again, short on details.... how did you "try" the factory image? Since you already had 7.1.1 running well for the last month, you could have just done a full factory reset from stock recovery (not TWRP) to rule out personal apps and your setup. Since you have some backups and are unlocked, use ADB to first fastboot format userdata and cache. Then fastboot flash the full NMF26F image- not OTA. Let the phone stabilize first and test it before installing all your applications.
I was running xXx 4.5, and decided to "upgrade" to 5.0.
I did the usual, wiped data/system, then flashed.
I got stuck in a bootloop, and found I had to double back and wipe /data.
I did that, got stuck at the boot animation.
If I go back to recovery, all the data is jumbled, I assume encrypted? I flashed a different twrp for 8.0 compatibility, no change.
I can't push/sideload anything (roms, recovery zips sideload fine), it fails.
So I flashed the stock recovery in fastboot, rebooted there, and tried to sideload via adb the stock 8.0 flash files.
Now it works at it for a few minutes and just comes back as "Installation Failed".
Where do I go next? All i can get to is recovery, fastboot, bootloader.
I've already factory reset/wiped everything, so don't care if I lose anything anymore.
Help?
Thanks.
It appears I found a solution, just a few posts below my own! I hate it when that happens.
Anyways ,
https://forum.xda-developers.com/showpost.php?p=75364805&postcount=7
seems to have got the ball rolling, I was able to copy files to my phone while in twrp, which I couldn't do before, and currently have xXx installing. The first time it installed it didn't ask about encrypted/decrypted and didn't give me any warnings, this time it did.
xXx still won't boot after flashing, trying stock full flash file..
edit 2: Was able to flash full oneplus update file and boot. had to do a factory reset after rebooting as it was crashing a ton and wouldn't get through setup. It's been running fine since though. Now I'm a little skittish to try again, there are some root features I'd really like to still have.
I have a OnePlus 5 phone stuck in the Fastboot mode, been contacting them for days now but I still keep hearing the same excuses that the matter has been escalated to their tier 2 tech support team Nd would be contacted. Please is there a way to copy files off the phone in this state before it's flashed?