Hello!
My nexus 4 started to optimize app on each reloading few days ago. At last reload it stucked on "starting apps". I flashed factory 5.1 rom by default guide("run flash-all"). It not helped, starting apps stuck again. I flashed 4.4, it not helped too.
I find few tips.I tried.
(4.4) lock, unlock bootloader, flash
(4.4) flash twrp, change filesystem of cache to fat, return to ext4, flash
(4.4) flash by update without -w
(4.4) erase all particles by fastboot, flash manually each particle
(4.4) flash by update, go to default recovery and do factory reset
it not helped.
what could happen? What I can do?
Sorry for bad english
Boot into fastboot, issue the commands "fastboot erase userdata", "fastboot erase cache", "fastboot flash userdata usedata.img", use volume button to boot into recovery, perform a factory wipe using stock recovery, and reboot.
The userdata.img file needs to be extracted from the stock ROM.
Hope this helps get the phone booted.
audit13 said:
Boot into fastboot, issue the commands "fastboot erase userdata", "fastboot erase cache", "fastboot flash userdata usedata.img", use volume button to boot into recovery, perform a factory wipe using stock recovery, and reboot.
The userdata.img file needs to be extracted from the stock ROM.
Hope this helps get the phone booted.
Click to expand...
Click to collapse
Thanks, but did not effective: it stuck on boot animation(flying ovals)
It could be a possible hardware problem in that the memory chip is defective.
Try flashing stock ROM with Nexus Root kit. If that ROM fails to start then there is a likely hardware issue
Sent from my Nexus 4 using Tapatalk
Related
My N7 is unlocked, I upgraded to 4.2.2 factory stock, rooted, and flashed ClockworkMod Recovery 6.0.2.3 touch recovery. I ran into a very strange issue; if I flash the custom recovery on the tablet, then the tablet boots into a screen that asks me to type my password to decrypt storage not allowing me to enter the homescreen until I do so. Later, I found out that flashing back to stock recovery fixes the problem and my N7 is functional again. I've tried everything while on the custom recovery: erasing, formatting, writing userdata to the device without success.
I'm not really sure what question you are asking. Also, I think you might be leaving something out which ought to be clarified, the way you describe things seems to have some pieces missing. (And, you really should not be starting yet another thread on this)
You shouldn't be able to flash custom ROMs with a stock recovery; so, are you saying that you:
- flash a ROM with a custom recovery
- try and boot it -- but it fails with the "enter password" prompt (you mention "won't let me enter the homescreen")
- flash the stock recovery into place
- perform a factory reset with the stock recovery
- now the ROM boots?
Also, do you get the same result with TWRP?
bftb0 said:
I'm not really sure what question you are asking. Also, I think you might be leaving something out which ought to be clarified, the way you describe things seems to have some pieces missing. (And, you really should not be starting yet another thread on this)
You shouldn't be able to flash custom ROMs with a stock recovery; so, are you saying that you:
- flash a ROM with a custom recovery
- try and boot it -- but it fails with the "enter password" prompt (you mention "won't let me enter the homescreen")
- flash the stock recovery into place
- perform a factory reset with the stock recovery
- now the ROM boots?
Also, do you get the same result with TWRP?
Click to expand...
Click to collapse
It's a help/troubleshooting post. I know it wasn't good to start another thread, but I felt that people that had already browsed my thread the first time wouldn't come back and now I found the reason behind my issue. I didn't flash a custom rom with stock recovery; I used fastboot on my pc to issue commands. My phone has the factory stock rom on it - then if I flash clockworkmod recovery, the next time I reboot, there's a screen that says I need to type a password to decrypt storage and I'm not able to access anything. If I go back into the bootloader and erase and write the stock recovery, I'm able to boot into the homescreen without the issue. Everything I've flashed to the tablet is done through my pc via fastboot. I never tried TWRP, but I don't like that recovery anyways.
UnlockedNand said:
It's a help/troubleshooting post. I know it wasn't good to start another thread, but I felt that people that had already browsed my thread the first time wouldn't come back and now I found the reason behind my issue. I didn't flash a custom rom with stock recovery; I used fastboot on my pc to issue commands. My phone has the factory stock rom on it - then if I flash clockworkmod recovery, the next time I reboot, there's a screen that says I need to type a password to decrypt storage and I'm not able to access anything. If I go back into the bootloader and erase and write the stock recovery, I'm able to boot into the homescreen without the issue. Everything I've flashed to the tablet is done through my pc via fastboot. I never tried TWRP, but I don't like that recovery anyways.
Click to expand...
Click to collapse
OK, read and understood. Very bizzare, however. Almost sounds more like something caused by the bootloader (during the fastboot write) rather than it mattering which custom recovery is sitting there (it's not clear from the above, but it almost sounds like it is not even necessary to have ever booted the custom recovery from the device's recovery partition for the problem to appear)
Are you also saying that you can not flash a custom ROM from the custom recovery without this "enter password" phenomenon happening, or is it only this combo of pure stock ROM + recovery flashed via fastboot that exhibits the problem?
I have a lightly-rooted JDQ39 Stock (4.2.2) ROM with a custom recovery - no such troubles. But mine was installed by using factory-via-fastboot of 4.2.1, followed by a manually-triggered OTA to JDQ39, and then followed in turn by a fastboot flash of the recovery partition (TWRP 2.4.1.0). That last flash was certainly performed by the 4.18 bootloader.
No troubles, but that is certainly a different installation path.
Two more small questions for clarification purposes: when you installed the factory 4.2.2 ROM via fastboot, did you follow the exact sequence of the install-all.sh script:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.18.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-jdq39.zip
... or did you omit anything (e.g. one or more of the erases, the bootloader flashing, etc)?
Yeah, it's like the bootloader writes bad information to the userdata partition if the recovery isn't stock. I haven't flashed a custom rom from the custom recovery, but I'm assuming the type your password issue would appear again. Yes, it's a combo of pure stock rom + custom recovery when this problem occurs. No, when I installed the 4.2.2 factory stock rom, I unzipped all the image files and typed these commands.
Code:
fastboot oem lock
fastboot oem unlock
fastboot flash bootloader <bootloader name>.img
fastboot flash boot <boot name>.img
fastboot flash system <system name>.img
fastboot flash userdata <userdata name>.img
fastboot reboot-bootloader
fastboot erase cache
fastboot reboot
I've also gone back and manually erased, formatted, and wrote the userdata partition again. Maybe I should try downgrading the bootloader to 4.2.1, reflash userdata, and flash the custom recovery?
UnlockedNand said:
Yeah, it's like the bootloader writes bad information to the userdata partition if the recovery isn't stock. I haven't flashed a custom rom from the custom recovery, but I'm assuming the type your password issue would appear again. Yes, it's a combo of pure stock rom + custom recovery when this problem occurs. No, when I installed the 4.2.2 factory stock rom, I unzipped all the image files and typed these commands.
Code:
fastboot oem lock
fastboot oem unlock
fastboot flash bootloader <bootloader name>.img
fastboot flash boot <boot name>.img
fastboot flash system <system name>.img
fastboot flash userdata <userdata name>.img
fastboot reboot-bootloader
fastboot erase cache
fastboot reboot
I've also gone back and manually erased, formatted, and wrote the userdata partition again. Maybe I should try downgrading the bootloader to 4.2.1, reflash userdata, and flash the custom recovery?
Click to expand...
Click to collapse
Hmmm. Well, I can't say for sure, but I am willing to gamble that the bootloader relocates itself into a load-offset address so that it runs out of RAM rather than running directly out of Flash Memory. Much quicker that way. The implication of that is that once it is fully loaded into RAM and operational, you could actually erase the bootloader and suffer no ill effects - until you powered off the device. Then you would be in real trouble.
The point is, in the Google factory sequence, all of the partition flashing is done by the new bootloader (4.18), whereas in your case none of it is done that way - except for the custom recovery flash. Here's the Google sequence:
- erase all partitions using currently installed bootloader (4.13)
- flash new bootloader and boot into it ( 4.13 -> 4.18 )
- flash all 4.2.2 ROM partitions using new bootloader
whereas your sequence looks like:
- (no explicit erasures)
- flash partitions with old bootloader (4.13)
- reboot into new bootloader ( 4.13 -> 4.18 )
- erase cache
- flash recovery with new bootloader ( 4.18 )
very different!
Also, the "-w" switch used in the google sequence causes partition erasure and re-formatting (depending on partition type) prior to each partition's flashing.
Without going through the lock/unlock procedure, I suppose it would be possible to reflash all the partitions with 4.18 to see if the problem disappears. But, now that I said that, I realize my tab - which had an OTA upgrade - is sort of similar in that the partitions & files patched by the OTA were all initially flashed by 4.13 (by me), patched by the OTA, and then finally I flashed only the custom recovery with the 4.18 bootloader.
Doing further experimentation might mean attempting a bootloader rollback flash. I can't say that I've seen reports here of anybody trying it. And I can't say I blame them - there could be dragons hiding in that process.
Ah, I see. The sequence I followed flashing the partitions would erase and write the partitions automatically done by the fastboot script. The only instance where I erased, formatted, and flashed the partition was the userdata when I was troubleshooting. From reading other threads before, I believe people have done bootloader rollbacks without consequences to the rest of the partitions. The bootloader updates contain fixes, but aren't explicitly required for the rom to run, am I correct?
I'm selling my Nexus 7 and I think I got a little click happy while clearing it out.
I had reinstalled 4.3 and then for some reason I formatted the data. Got stuck in a boot loop.
When I try to install the image again I get the following:
Updating partition details...
E:error opening '/data/media'
E:error: no such file or directory
Any help would be appreciated!
"90% of the time, when someone says something's bricked, the only brick is their head." - Koush
All this means is that your userdata partition got all jacked up. It's restored when you boot into a rom, but of course you can't boot into a rom cause something else must have also went awry. So I suggest you wipe everything and start over. Follow along with me, this will be fun!
Boot into fastboot, send fastboot unlock command if your bootloader isn't already unlocked "fastboot oem unlock." Accept on screen. Reboot back into bootloader/fastboot. Issue FASTBOOT ERASE USERDATA, FASTBOOT ERASE RECOVERY, FASTBOOT ERASE CACHE, FASTBOOT ERASE SYSTEM. Then flash TWRP recovery using FASTBOOT FLASH RECOVERY [NAME OF TWRP GROUPER IMG]. Then adb push your rom and gapps back to your tablet using ADB PUSH [FILE] /SDCARD, then flash your rom and enjoy a fresh clean tablet!
That's why I prefixed with 'possible'...
Thanks - I followed this guide later in the evening and got it all up and going again.
http://goo.gl/BsiewY
0vermind said:
"90% of the time, when someone says something's bricked, the only brick is their head." - Koush
All this means is that your userdata partition got all jacked up. It's restored when you boot into a rom, but of course you can't boot into a rom cause something else must have also went awry. So I suggest you wipe everything and start over. Follow along with me, this will be fun!
Boot into fastboot, send fastboot unlock command if your bootloader isn't already unlocked "fastboot oem unlock." Accept on screen. Reboot back into bootloader/fastboot. Issue FASTBOOT ERASE USERDATA, FASTBOOT ERASE RECOVERY, FASTBOOT ERASE CACHE, FASTBOOT ERASE SYSTEM. Then flash TWRP recovery using FASTBOOT FLASH RECOVERY [NAME OF TWRP GROUPER IMG]. Then adb push your rom and gapps back to your tablet using ADB PUSH [FILE] /SDCARD, then flash your rom and enjoy a fresh clean tablet!
Click to expand...
Click to collapse
Hi there,
I think I screwed in such a fashioned manner that I did not spot any spot to better expose my issue.
I run a Nexus 4 root which used to run fine with 4.3.
I did ota to Nexus 4.4 failure.
Then I did Efrant guide (without step 10) to go 4.4, it worked.
fastboot devices
fastboot reboot-bootloader
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
fastboot flash system system44.img
fastboot flash boot boot44.img
fastboot flash recovery recovery44.img
fastboot format cache
fastboot reboot
I had really bad experience with kitkat. No notification, sms history gone, home virtual button not working (only blipping), same for the top right notification menu.
Well I thought going to 4.3 would be best.
I did 4.3 through the same steps with different archives and boot loop at the X.
Then I tried a 4.2.2 but I did a huge mistake, I did it with Nexus 7 files. After sweating a bit I got it back in fastboot mode.
Then I tried 4.3 occam and 4.4 occam. Bootloop, old style and new one.
Now I can try 4.2.2 or 4.4 with fastboot flash userdata userdata.img
Any clue?
Edit: From Efrants:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (this will obviously delete all your data & files in /sdcard...).
I can go to the red exclamation mark.
Than all the combinations I do just reboot me. What is the trick? Power on then volume up? Power on and volume up at the same time? How long should I press?
Try this
Get proper files for let's say 4.3 mako
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
The bootloader and radio being from stock ota from Google, recovery stable custom one
fastboot reboot-bootloader
Make sure all matches
Boot to recovery
Flash ROM of choice, use a 4.3, maybe slimbean
May need to sideload the ROM though
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Try this
Get proper files for let's say 4.3 mako
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
The bootloader and radio being from stock ota from Google, recovery stable custom one
fastboot reboot-bootloader
Make sure all matches
Boot to recovery
Flash ROM of choice, use a 4.3, maybe slimbean
May need to sideload the ROM though
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK I get the idea. By flashing the ROM of your choice what do you mean, flashing an OTA zip? I know how tosideload, just trying to understand what to flash.
I am about to try to flash a recovery (twrp) to wipe cache.
I tried and added system and boot.
/!\ fastboot erase system -w Erase all userdata I wanted to do that as a last option... Well now it is done...
The phone is now properly booting a 4.2.2 I will see tonight if I can get it to 4.3 or 4.4
ROM of choice is ROM of your choice, hence the recommendation for slimbean but only a recommendation
The fastboot erase system -w will cover wiping cache, but yeh still download and install the twrp image
Sent from my Nexus 7 using Tapatalk 2
demkantor said:
ROM of choice is ROM of your choice, hence the recommendation for slimbean but only a recommendation
The fastboot erase system -w will cover wiping cache, but yeh still download and install the twrp image
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well thanks for your help.
I think that my first install of 4.4 was messy. I really suspect that I installed bad radio and or bootloader. Thank you google for giving same name to different versions. Or may be I got some corrupted stuff on userdata?
When I went back to 4.3 I dont know what went wrong, maybe only that cache issue?
Then messing with the nakasi img (call me stupid) could not do any good.
I took too much confidence in messing the previous upgrades and recovering without loosing personnal data...
Now I have a fresh start to think about it...
I've got one question and one question only: how do I install 4.3 again on my nexus 4 again. I have NEVER rooted or flashed my phone. Would really really appreciate all the help I can get.
omairanwar said:
I've got one question and one question only: how do I install 4.3 again on my nexus 4 again. I have NEVER rooted or flashed my phone. Would really really appreciate all the help I can get.
Click to expand...
Click to collapse
fastboot oem unlock
fastboot flash recovery recovery.img
reboot to recovery
flash rom of choice
There are many guides on rooting and fastboot, i would suggest staying away from any toolkit
as if you would like to learn, you wont from a toolkit.
the above take minuets and is far from a difficult task, its a nexus, its meant to be easy.
peek your nose around the forum a bit, you have any issues or are unsure just ask and id be glad to help
Hi guys,
In front of me, I have my friend's very stubborn LG Nexus 4. It's about 7 months old and a month ago, he dropped it and cracked the screen's glass (and the case's glass back as well). The phone still worked fine for a few weeks after that after that, but the touchscreen was not always responding correctly. He decided to give it to a service center for repair, but they returned it in a few days claiming there's a bootloop and they won't repair it (even if he paid) since the phone wasn't purchased in the same country. (Such BS, isn't it?)
An easy thing to fix, I thought, after fixing all sorts of bootloops on my SGT, SGS1 and my other friend's SGS2. Turns out, it's anything but.
Regardless of whether I flash stock following this guide or CM11 following the CM wiki, the phone is stuck on boot animation. 4 swirling colored balls for stock or an arrow rotating aroud Cid in case of CM11.
I have tried both stock recovery and CWM. I have tried wiping cache, data, Dalvik cache, any combination of only one or two or all three, tried waiting for an hour on first boot (someone suggested the first boot can take up to 15 minutes... find that hard to believe since even my sluggish SGS1 will manage in 3 minutes tops after a flash, but still tried) - all in vain. All I get is the screen's backlight level suddenly jumping up about 5 minutes into the boot process, as if the "Welcome to Android!" menu is about to appear - but it's still bootlooping until the battery runs out. (It gets quite warm too.)
TL;DR Nexus 4 flashes successfully with both stock 4.4.2 and CM11 but bootloops no matter what.
What can I do at this point to troubleshoot it? I'm out of ideas.
Its possible that this is a hardware issue but for now what I would try is download latest stock, Google search
android factory images
And choose the latest for your device, KOT49H
Now boot to fastboot
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now
fastboot flash bootloader nameofbootloader.img
fastboot flash radio nameofradio.img
Now either double click the flashall.bat or I prefer just extracting the rest an manual flash
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
Now
fastboot reboot
If this doesn't work than a good chance of hardware issue from all the falls, if it does work then my guess is you want to root it so go back to fastboot and flash the latest twrp or cwm recovery
Then either boot to recovery and flash su or wipe all and flash a custom ROM
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Its possible that this is a hardware issue but for now what I would try is download latest stock, Google search
android factory images
And choose the latest for your device, KOT49H
Now boot to fastboot
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now
fastboot flash bootloader nameofbootloader.img
fastboot flash radio nameofradio.img
Now either double click the flashall.bat or I prefer just extracting the rest an manual flash
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
Now
fastboot reboot
If this doesn't work than a good chance of hardware issue from all the falls, if it does work then my guess is you want to root it so go back to fastboot and flash the latest twrp or cwm recovery
Then either boot to recovery and flash su or wipe all and flash a custom ROM
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As I said, I've already tried CWM, custom ROM (CM 11 - which required rooting, which I did) and followed the guide I linked for flashing the latest stock ROM I got from Google. The only thing I haven't tried is the fastboot erase commands - thanks for suggesting that, I will try them ASAP before trying to flash stock again though I don't have much hope left
Give it a shot, if you do everything in this order you will be good if its a software issue, if it doesn't work than possibly hardware
Sent from my Nexus 4 using XDA Premium 4 mobile app
It started acting weirdly after shutting down while it was updating some apps. First, it would only function normally when on the charger (it was really erratic off it, shutting down when turning on the data/wifi).
After one day it got briefly stuck in a bootloop, and afterwards it would just display the Google logo and shutdown (or, if on charger, reaching the "Optmizing apps.." screen, and shutdown).
I attempted a "wipe cache", "Factory Reset", and flashed different stock ROMs using the Skipsoft Toolkit, all for no avail.
Is there anything else that can be done?
I suggest manually flashing each partition, including the userdata.img file. After flashing the userdata.img file, boot directly into recovery from fastboot, factory wipe, reboot. Hopefully, this will allow the phone to boot.
audit13 said:
I suggest manually flashing each partition, including the userdata.img file. After flashing the userdata.img file, boot directly into recovery from fastboot, factory wipe, reboot. Hopefully, this will allow the phone to boot.
Click to expand...
Click to collapse
Thanks. I flashed each partition manually, but it then gives mount erros on mount/cache/recovery/log and the boot never ends. These are the steps I took:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase userdata
fastboot flash userdata userdata.img
I also tried directly fastboot -w update "zipfile", but it then shutdowns after booting.
After flashing userdata.img, you boot straight to recovery without trying to boot the rom? For mine phones, it's normal for there to be an cache mount error in recovery. After performing a factory wipe in the stock recovery, everything gets formatted and the phone is able to boot.
audit13 said:
I suggest manually flashing each partition, including the userdata.img file. After flashing the userdata.img file, boot directly into recovery from fastboot, factory wipe, reboot. Hopefully, this will allow the phone to boot.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2160124 try this, but be careful
I am not the person having a problem with the nexus 4.
ftkg said:
It started acting weirdly after shutting down while it was updating some apps. First, it would only function normally when on the charger (it was really erratic off it, shutting down when turning on the data/wifi).
After one day it got briefly stuck in a bootloop, and afterwards it would just display the Google logo and shutdown (or, if on charger, reaching the "Optmizing apps.." screen, and shutdown).
I attempted a "wipe cache", "Factory Reset", and flashed different stock ROMs using the Skipsoft Toolkit, all for no avail.
Is there anything else that can be done?
Click to expand...
Click to collapse
oh sorry, bump op
always first post is full-sized so I didn't see
mesaj said:
http://forum.xda-developers.com/showthread.php?t=2160124 try this, but be careful
Click to expand...
Click to collapse
Thanks, but maybe you intended to refer to this? http://forum.xda-developers.com/showthread.php?t=2099784
I'm not sure of the purpose of converting from 8G to 16G of internal storage
ftkg said:
Thanks, but maybe you intended to refer to this? http://forum.xda-developers.com/showthread.php?t=2099784
I'm not sure of the purpose of converting from 8G to 16G of internal storage
Click to expand...
Click to collapse
This is the same, I posted for N4 which is basically the same as G but G is more detailed. Try it it should format your device, helped me after similar brick issue. Btw. I used NRT instead Skipsoft.