Related
My Nexus 4 was previously running 4.4.2 ... I had a modified kernel patch (done via an app and I can't remember the name of it) and it was rooted. On occasion I would pickup the phone just to find out it had shut down. I would reboot it and it would be fine for days. One day it got stuck on the boot animation. It just wouldn't pass that point. Then the battery died (I assume) so I plugged it in via USB to both wall and PC and it would not charge. I had to put in on my wireless charging pad and it charged right up .. but still would not pass the animation.
Since then I have individually flashed each file manually from the newest lolipop ROM. Tried the nexus toolkit including most of the 4.X.X stock ROMS. Did a format and erase. Booted Clockwork Recovery and installed 5.0 from sdcard. (I can access the sdcard via USB on CWM). I flashed the kernel, Radio and bootloader several times each. I tried the Cyan ROM 10.x too
After the second attempt installing 5.0 (using the toolkit) I did get "Android is upgrading ... Optimizing apps" then it hung on "starting apps" and the animation continued for hours. I have had no other success since then.
I am at a complete loss. So I turn to the experts in hope of salvation.
Any idea what I'm doing wrong or what else I should be doing?
Your emmc chip is fried.. Take the phone to a service center
Sent from my Nexus 4 using XDA Free mobile app
http://forum.xda-developers.com/showthread.php?t=2964619
Well, here's a new twist. I'm able to flash 4.2 and 4.2.2 with no problems .. but 4.3 OTA and even manual flash will reproduce the stuck on animated logo problem.
I installed a sensor app and it seems like all sensors are working fine.
I remember that I was using the franco kernel before my problems started. Maybe I have a botched kernel. But I have flashed it when I did all the ROMs did I not?
What is the earliest kernel version that is compatible with 4.3, 4.4 and 5.0?
Does anyone know why I can't flash beyond 4.2.2?
Is there a way to systematically test each .img to discover the problem?
Also, even though I have USB debugging enabled, I can't use ADB to sideload at all. I keep getting ADB was not found. I can use ADB without problems on my nexus 5.
bump
Same issue here. Could flash 4.2.2 and update with ota to 4.4.4, after that the boot animation stay's for more then an hour. Any idea how to solve this?
Just to share my own experience on similar issue..
my N4 was official Lollipop 5.0.1 unrooted & locked.
Unlocked & installed clockworkmod & latest official pa rom -> stuck in boot screen. (had done all resets etc )
full wipe & latest official CM nightly -> stuck in boot screen.
full wipe & installed full official google 4.4.4 image -> phone booted ok.
full wipe & install cwm & latest official pa rom (same as earlier) -> phone booted ok.
So my conclusion was that it had something to do with lollipop modem etc part, that didnt quite work with roms i tried to run.
BTW for some reason wasnt able to get adb sideload to work for me neither, so installed the factory images on fastboot / flash-all.bat
If you have a backup with USB debugging enabled, you could restore it and try to take a logcat while booting. This would make finding the culprit a lot easier.
As above. While the phone technically works I cannot flash the latest stock rom (the set about unlocking, rooting, installing a custom recovery) as it loops....ive dropped back to the original stock image (4.4.4) which boots fine....I then went back up to LMY47V which loops and currently downloading KTU84 to see if that works....now just to add to all of this I was given the phone with a cracked screen which ive replaced but it came to me dead so I don't know the previous history....and thought that the advent of me fitting the screen caused it which I doubt....but the thought was there.....
The only other option if KTU84P doesn't work is to drop back to 4.4.4 and go up gradually......
Anyone else had this...?
Well, so far, nothing works apart from the stock image (tried a few other stockers) but nothing - tried installing custom recovery TWRP 3.x which installs fine....just wont boot...
Try stock flashing using Nexus root kit and check Soft bricked radio button
Sent from my Nexus 4 using Tapatalk
I'm using the Nexus Root toolkit - is that the one youre talking about ( as I cant see the "softbricked radio button") - ive got "Softbricked/bootloop" but tried that which didn't work....
I did try the original 4.4.4 image (the first one) which does boot. And then tried manually flashing the radio separately but that didn't work (but TBH I'm not sure that I did it correctly) - so, do you think its a radio issue - the reason it wont boot??
Yes, that will be the right radio button. There is only one for stock flash section. Which radio are you flashing? If its Nexus LTE zip then it's only for Lollipop ROMs 5+. Try flashing latest Lollipop stock and if it boots then flash radio. That's what I did.
If not then back to KK.
Sent from my Nexus 4 using Tapatalk
Try this: flash the latest stock ROM using fastboot commands and, after flashing the last partition, flash the userdata.img file, use the buttons to boot directly to recovery from fastboot, perform a factory wipe, and reboot.
Ok - thanks for that - haven't done the fast boot commands for a while...! ill try it now....
The other thing I noticed was the battery is draining really fast (while in bootloop) the back of it is very hot....so much so that plugged into the laptop wasn't enough to keep it running - had to transfer it to a charger....
Looking at my file I downloaded from google... (I was just about to start) I noticed I don't have the radio firmware? so, all this time while ive been reflashing and trying different images from google (stock images) ive not been flashing the radio firmware - I thought they would have included that!! am I right in thinking that's why its been bootlooping as the radio firmware is at stock (the reason why only the original base image boots)??
Well, while I was installing I flashed twrp3 as the recovery and used that when I went in to manually reset it gave me the error "cache invalid argument" - would that have any bearing??
Well, tried that and it sat there....thought id try jumping ahead a little....flashed a cm13 nightly along with a radio firmware file (a .zip) using twrp...but still the same....missing something somewhere....
I presume you have NRT installed and tried; it downloads and extracts factory images before flashing. If you are flashing latest official stock lmy48t check contents of the downloaded image. Should be
cd C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Factory_Images\occam-lmy48t-factory-416938f1
dir /b
bootloader-mako-makoz30f.img
flash-all.bat
flash-all.sh
flash-base.sh
image-occam-lmy48t
image-occam-lmy48t.zip
radio-mako-m9615a-cefwmazm-2.0.1701.07.img
Batch file that NRT runs is flash-all.bat; third line is radio flashing
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.07.img
fastboot reboot-bootloader
fastboot -w update image-occam-lmy48t.zip
Executing fastboot commands manually should achieve same result
Yep - using the wugfresh stuff tried it about a dozen times with different stock images....never had a problem like this before....
tried as you said - tried to flash manually and also tried using the bat file....still the same - flashed back to jdq39 and it boots straight back up...weird....
Can I ask silly question? Was bootloader unlocked?
Sent from my Nexus 4 using Tapatalk
If the bootloader was not unlocked, no ROM could be flashed to the phone.
Exactly. So if all fastboot commands in flash_all.bat run error free phone should boot OK. NRT runs log in a separate window so any error is easily noticeable. The only thing that comes to mind is how long it takes to boot after rom flash; I think mine took close to 20 min of bouncing balls before I saw Android logo. So may waiting for longer time will resolve it.
Yep - unlocked the bootloader (and relocked it) hoping that would shift it into life!! but no...
Ive tried the waiting game....left it on at the office at the end of the day, came back in the next day to see it still "trying to boot..."
Came across a procedure on how to pull log during bootloop. Check it out if interested. I haven't tested it. http://forum.xda-developers.com/general/xda-university/universal-test-rom-build-didnt-boot-t3258818
Sent from my Nexus 4 using Tapatalk
Yep - will do - just for the record I reflashed back to 4.2.2 relocked, booted, let the phone download a 4.3 update and flash...totally stock....just sat there.....just had a look at that link (looks promising) so I'm going to go back upto the latest build and then install twrp then flash the file to see if I can see whats going on behind....
I have a 910C at v.5.1.1. I received a 100MB system update a few days ago. The update seems to have been successful as everything works while phone is booted to OS. However I cannot get into TWRP when I try to boot into recovery.
I've also tried to flash TWRP using the unified toolkit and odin. I have the professional ver of toolkit which enables it to work with 5.1.1. Anyway it always boots into stock recovery and the ODIN flash won't take. When I boot to recovery it comes to the android thingy saying installing updates and then fails after a minute of so with message, "no command found." I think this is what is breaking everything. I've cleared everything and done a factory reset but still see the same behavior.
Does anyone know how I can fix this?
Thank you,
@_metafizik
Hi, did you able to fix your issue? I am facing same issue.
Managed to brick my A1. The only screen its able to go to is either fastbook, or recovery. And even then, doesn't always necessarily boot into recovery, have to plug into computer and go into command prompt (fastboot boot oreo_3.2.2_recovery.img) to get it into TWRP.
Currently can't seem to flash *any* roms, I have a stock rom ("tissot_100108_stock" cant remember where i got it from). Which successfully flashes, but then on reboot gets stuck on the Android One screen. Longest i have waited before giving up is an hour. Even when i flash this rom and reboot, i get a message on TWRP saying "No OS installed"
Tried doing this: [wont let me post link] (MiFlash) method and got an error, basically does not work.
Super frustrated, at my wits end, would just like to flash stock rom and sell this thing or let it sit in a drawer at this point. Thanks in advance.
same problem here...
I have the exact same issue and also came here for that to ask for help.
Xiaomi Mi A1 was running 8.1 OTA updated and then I tried to flash Lineage, but it did not work. I wiped my phone and now it can't install anything, not via TWRP nor with Mi Flash.
I hope we can find a solution.
cantras said:
I have the exact same issue and also came here for that to ask for help.
Xiaomi Mi A1 was running 8.1 OTA updated and then I tried to flash Lineage, but it did not work. I wiped my phone and now it can't install anything, not via TWRP nor with Mi Flash.
I hope we can find a solution.
Click to expand...
Click to collapse
hopefully! i posted on the xiaomi subreddit but no help. i was on 8.0 when i started this whole misadventure.
I got somewhere, I think.
I went into TWRP, switched from B to A booting. It then starts Android but gets stuck in the boot screen of Android one with the colored bar.
I then tried MiFlash again, going directly to the folder which containts the .bat files. It started flashing it finally.
I am back to a working system.
Let me know if it works for you.
you guys should try flashing the latest stock rom 8.1 July running the bat file of your choice located in the factory image through fastboot
the different custom recoveries and miflash are sometimes buggy
run the script directly on fastboot
Sent from my Nexus 6 using Tapatalk
Hi everybody,
I want to try some battery friendly rom based on android Marshamallow and currently I am on stock oreo.. The issue is I cant install android 6.0 and encounter error while flashing boot image in fastboot..
Can I directly flash 6.0 based rom through twrp on oreo?
And while I was doing this I wasnt even able to flash 8.0 boot img as well while I was able to install it through twrp..
Sorry If the question is not proper or I am unable to explain it properly
To be precise it gives fastboot: error: Couldn't parse partition size '0x'
joyyia said:
Hi everybody,
I want to try some battery friendly rom based on android Marshamallow and currently I am on stock oreo.. The issue is I cant install android 6.0 and encounter error while flashing boot image in fastboot..
Can I directly flash 6.0 based rom through twrp on oreo?
And while I was doing this I wasnt even able to flash 8.0 boot img as well while I was able to install it through twrp..
Sorry If the question is not proper or I am unable to explain it properly
To be precise it gives fastboot: error: Couldn't parse partition size '0x'
Click to expand...
Click to collapse
I think u also need to change vendor, radio, bootloader according to it. Or switch to stock mm first then flash
Sent from my angler using XDA Labs
Same problem, how I can fix it now? Pls someone help, I flash multirom recovery but I could not flash any rom so I decided back to stock and now I can’t flash boot.img same error help pls, I love my nexus
If you are experiencing what I am, this appears to be working...
In the old days, to flash a Nexus Device, wugfresh's Nexus Root Toolkit was what I used. With my current Nexus 6P, I'd recently been tinkering with a newer LineageOS unofficial ROM, and somewhere along the way, I ended up with that "Couldn't parse partition size '0x'" error, and sometimes others, when trying to flash the original ROM back, and was afraid my phone was history. However, I remembered wugfresh's Nexus Root Toolkit, and that it had options in it to "unbrick/debrick" a nexus device. So, I took my already downloaded latest official GOogle Nexus ROM, hunted down the wugfresh nexus root toolkit, and then it was readily able to restore my phone to its previously functioning state, just like in the old days. Now, at this very moment, I just did this... I don't know if anything else will pop up not right, but it didn't give any errors when it went to flash the official rom, it rebooted, and is now waiting for me to set up my nexus phone... lol... so it looks as though the crisis has been averted... Since it is no longer supported, and bitdefender throws up warnings when i try to go to their original website. I used the techspot's website to download the toolkit. And, of course, the official google android rom site for the latest official ROM.
1. Downloaded Wugfresh Nexus Root Toolkit.
2. Downloaded latest Nexus 6P (angler) official ROM.
3. Installed Wugfresh Nexus Root Toolkit.
4. Put phone in Bootloader and connected to computer.
5. Ran Wugfresh Nexus Root Toolkit
6. Manually selected Nexus 6P.
7. Selected any ROM version.
8. Under (Restore/Upgrade/Downgrade) - Flash Stock + Unroot ... I selected "Soft-Bricked/Bootloop ... and then hit "Flash Stock + Unroot"
9. Selected "Other/Browse... For use with any factory image package: zip/tgz"
10. Selected "I downloaded a factory image myself that I would like to use instead."
11. Clicked OK.
12. Selected the previously downloaded latest Nexus 6P (angler) official ROM.
13. Watched with gratitude as it seemed to resuscitate my favorite phone.
I hope this helps someone else who may have fallen into this... I'll post again if it turns out not to have solved the problem fully.
newcapricasean said:
In the old days, to flash a Nexus Device, wugfresh's Nexus Root Toolkit was what I used. With my current Nexus 6P, I'd recently been tinkering with a newer LineageOS unofficial ROM, and somewhere along the way, I ended up with that "Couldn't parse partition size '0x'" error, and sometimes others, when trying to flash the original ROM back, and was afraid my phone was history. However, I remembered wugfresh's Nexus Root Toolkit, and that it had options in it to "unbrick/debrick" a nexus device. So, I took my already downloaded latest official GOogle Nexus ROM, hunted down the wugfresh nexus root toolkit, and then it was readily able to restore my phone to its previously functioning state, just like in the old days. Now, at this very moment, I just did this... I don't know if anything else will pop up not right, but it didn't give any errors when it went to flash the official rom, it rebooted, and is now waiting for me to set up my nexus phone... lol... so it looks as though the crisis has been averted... Since it is no longer supported, and bitdefender throws up warnings when i try to go to their original website. I used the techspot's website to download the toolkit. And, of course, the official google android rom site for the latest official ROM.
1. Downloaded Wugfresh Nexus Root Toolkit.
2. Downloaded latest Nexus 6P (angler) official ROM.
3. Installed Wugfresh Nexus Root Toolkit.
4. Put phone in Bootloader and connected to computer.
5. Ran Wugfresh Nexus Root Toolkit
6. Manually selected Nexus 6P.
7. Selected any ROM version.
8. Under (Restore/Upgrade/Downgrade) - Flash Stock + Unroot ... I selected "Soft-Bricked/Bootloop ... and then hit "Flash Stock + Unroot"
9. Selected "Other/Browse... For use with any factory image package: zip/tgz"
10. Selected "I downloaded a factory image myself that I would like to use instead."
11. Clicked OK.
12. Selected the previously downloaded latest Nexus 6P (angler) official ROM.
13. Watched with gratitude as it seemed to resuscitate my favorite phone.
I hope this helps someone else who may have fallen into this... I'll post again if it turns out not to have solved the problem fully.
Click to expand...
Click to collapse
I tried this and flashed everything ok. But it´s still in bootloop. I did factory reset and same. idk what to do next.
herr.dalay said:
I tried this and flashed everything ok. But it´s still in bootloop. I did factory reset and same. idk what to do next.
Click to expand...
Click to collapse
Try flash "Blod Patch" after flashing everything
haitham0 said:
Try flash "Blod Patch" after flashing everything
Click to expand...
Click to collapse
Thnx! I used the BLOD patch and it´s back. No performance issues so far using havoc rom.
Thanks very much for pointing me towards Nexus Root Toolkit... its a great bit of software
newcapricasean said:
In the old days, to flash a Nexus Device, wugfresh's Nexus Root Toolkit was what I used. With my current Nexus 6P, I'd recently been tinkering with a newer LineageOS unofficial ROM, and somewhere along the way, I ended up with that "Couldn't parse partition size '0x'" error, and sometimes others, when trying to flash the original ROM back, and was afraid my phone was history. However, I remembered wugfresh's Nexus Root Toolkit, and that it had options in it to "unbrick/debrick" a nexus device. So, I took my already downloaded latest official GOogle Nexus ROM, hunted down the wugfresh nexus root toolkit, and then it was readily able to restore my phone to its previously functioning state, just like in the old days. Now, at this very moment, I just did this... I don't know if anything else will pop up not right, but it didn't give any errors when it went to flash the official rom, it rebooted, and is now waiting for me to set up my nexus phone... lol... so it looks as though the crisis has been averted... Since it is no longer supported, and bitdefender throws up warnings when i try to go to their original website. I used the techspot's website to download the toolkit. And, of course, the official google android rom site for the latest official ROM.
1. Downloaded Wugfresh Nexus Root Toolkit.
2. Downloaded latest Nexus 6P (angler) official ROM.
3. Installed Wugfresh Nexus Root Toolkit.
4. Put phone in Bootloader and connected to computer.
5. Ran Wugfresh Nexus Root Toolkit
6. Manually selected Nexus 6P.
7. Selected any ROM version.
8. Under (Restore/Upgrade/Downgrade) - Flash Stock + Unroot ... I selected "Soft-Bricked/Bootloop ... and then hit "Flash Stock + Unroot"
9. Selected "Other/Browse... For use with any factory image package: zip/tgz"
10. Selected "I downloaded a factory image myself that I would like to use instead."
11. Clicked OK.
12. Selected the previously downloaded latest Nexus 6P (angler) official ROM.
13. Watched with gratitude as it seemed to resuscitate my favorite phone.
I hope this helps someone else who may have fallen into this... I'll post again if it turns out not to have solved the problem fully.
Click to expand...
Click to collapse
thanks, man really appreciate it!
Sent from my angler using XDA Labs