Database Info

[Q] Galaxy Nexus freezes after Google logo

I have successfully rooted my Verizon Nexus version 4.04 build IMM76K and tried to flash two different ROM’s one is "Vicious-TORO-JellyBean-V3-signed" and the other is "Team Liquid Vicious-Toro V3-JellyBean Fully 100% Functional Deodex". On both it seemed to install fine, no error messages. Then at reboot it booted past the Google logo to the ROM logo and never passed it. I waited for a minimum of 20 minutes until I pulled the Battery and flashed back to stock. Please help.

Did flashing back to stock solve the problem, is your device ok?
Before you flash a custom ROM, always try wiping the cache and wiping the dalvich cache. You then wipe data and do a factory reset. After that you THEN install the ROM, that might've caused the problem. Maybe, I am not sure.
Which clockworkmod did you use to try flashing the ROMs, please give us more detail!

I actually did exactly as you said. Wiped, factory reset, wipe cache and then dalvich. Pushed the ROM to the phone and then installed it.I have been useing Gnex Toolkit v1.7

And did it work or what?
Wiping user data/Factory reset is important after installing the Custom ROM.
There is a good way to fix all this, make sure you backup EVERYTHING, and when I say EVERYTHING I mean EVERYTHING (Photos, Videos, EVERYTHING).
USE FASTBOOT, I have mentioned this heaps of times, I have because it just WORKS. I bricked my device before, and I just used fastboot. Understand 2 things if you're going to use it...
1. It DELETES EVERYTHING
2. You need to have your STOCK ROM in fastboot format
If you're willing to use fastboot and have the proper stock files here's how to do it (From Nexus S post: http://forum.xda-developers.com/showthread.php?t=1445635):
I QUOTE: "Put all six fastboot images in one folder, unlock your bootloader, perform the fastboot flashes, then lock the bootloader:
fastboot oem unlock
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
"
Cheers
Oh by the way I am not sure if the oem lock and unlock bit applies to you, check a relative guide to Galaxy Nexus please , this was an example

[Q] Flash stock .zip without flash-all.bat?

Is it safe to wipe everything (including system and internal and so forth) using TWRP, then reboot into TWRP, and then flash only image-hammerhead-krt16m.zip? I ask because the stock .tgz file has a radio image, and I'm wondering if I'll need to flash that as well. I don't want to do flash-all.bat because I want to keep TWRP recovery.

.psd said:
Is it safe to wipe everything (including system and data and so forth) using TWRP, then reboot into TWRP, and then flash only image-hammerhead-krt16m.zip? I ask because the stock .tgz file has a radio image, and I'm wondering if I'll need to flash that as well. I don't want to do flash-all.bat because I want to keep TWRP recovery.
Click to expand...
Click to collapse
No you can't flash that zip in recovery. You can flash the individual files in fastboot though. Just don't flash the recovery.img if you want to keep twrp. I haven't tried this but it should work, if it doesn't you can also flash a twrp.img file after running the bat file.
Edit, if you do flash the bat file, remember you will wipe the device so backup what you want to keep on your pc beforehand.

.psd said:
Is it safe to wipe everything (including system and internal and so forth) using TWRP, then reboot into TWRP, and then flash only image-hammerhead-krt16m.zip? I ask because the stock .tgz file has a radio image, and I'm wondering if I'll need to flash that as well. I don't want to do flash-all.bat because I want to keep TWRP recovery.
Click to expand...
Click to collapse
jd1639 said:
No you can't flash that zip in recovery. You can flash the individual files in fastboot though. Just don't flash the recovery.img if you want to keep twrp. I haven't tried this but it should work, if it doesn't you can also flash a twrp.img file after running the bat file.
Edit, if you do flash the bat file, remember you will wipe the device so backup what you want to keep on your pc beforehand.
Click to expand...
Click to collapse
+1 on what jd says.
OP, you're mixing up 2 completely different processes. i would suggest a little more reading and searching to increase your knowledge and familiarity with fastboot/recovery procedural techniques on this device. cheers

jd1639 said:
No you can't flash that zip in recovery. You can flash the individual files in fastboot though. Just don't flash the recovery.img if you want to keep twrp. I haven't tried this but it should work, if it doesn't you can also flash a twrp.img file after running the bat file.
Edit, if you do flash the bat file, remember you will wipe the device so backup what you want to keep on your pc beforehand.
Click to expand...
Click to collapse
What about the radio image? If I wipe everything in TWRP (dalvick cache, system, data, internal storage, cache, and data), will I lose the radio and therefore need to re-flash it? Or do none of those wipe the radio, so it's safe to wipe all and then only flash image-hammerhead-krt16m.zip?

.psd said:
What about the radio image? If I wipe everything in TWRP (dalvick cache, system, data, internal storage, cache, and data), will I lose the radio and therefore need to re-flash it? Or do none of those wipe the radio, so it's safe to wipe all and then only flash image-hammerhead-krt16m.zip?
Click to expand...
Click to collapse
What are you trying to accomplish? Wiping in twrp will not wipe the radio. But you can't flash the hammerhead.zip. You can extract the files in it and flash them in fastboot.

jd1639 said:
What are you trying to accomplish? Wiping in twrp will not wipe the radio. But you can't flash the hammerhead.zip. You can extract the files in it and flash them in fastboot.
Click to expand...
Click to collapse
Just want to wipe my device as clean as possible and hopefully learn a little in the process. When I got my MacBook the first thing I did was wipe it and then reinstall OS X and the AppleCare people were like "why though?" Because I'm a nerd.
So does it follow the same convention as flashing a recovery? So...
1. ./fastboot flash cache cache.img
2. ./fastboot flash boot boot.img
3. ./fastboot flash system system.img
4. ./fastboot flash userdata userdata.img
?
Or are the commands different for each image? Does the order matter?

.psd said:
Just want to wipe my device as clean as possible and hopefully learn a little in the process. When I got my MacBook the first thing I did was wipe it and then reinstall OS X and the AppleCare people were like "why though?" Because I'm a nerd.
So does it follow the same convention as flashing a recovery? So...
1. ./fastboot flash cache cache.img
2. ./fastboot flash boot boot.img
3. ./fastboot flash system system.img
4. ./fastboot flash userdata userdata.img
?
Or are the commands different for each image? Does the order matter?
Click to expand...
Click to collapse
Yes that all looks correct for the Mac. Order doesn't matter

jd1639 said:
Yes that all looks correct for the Mac. Order doesn't matter
Click to expand...
Click to collapse
Thank you very much.

[Q] Update stock even if rooted

I am thinking of just going on stock android but i like adblock. So i will end up rooting my phone, i was wondering if there is a way to update Lollipop rooted without having to restore. I dont mind loosing my root after every update, i can always re root
thanks guys

rolgar20 said:
I am thinking of just going on stock android but i like adblock. So i will end up rooting my phone, i was wondering if there is a way to update Lollipop rooted without having to restore. I dont mind loosing my root after every update, i can always re root
thanks guys
Click to expand...
Click to collapse
Download new factory images
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
reboot into your custom recovery
flash the latest SuperSU (http://download.chainfire.eu/supersu)

Elluel said:
Download new factory images
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
reboot into your custom recovery
flash the latest SuperSU (http://download.chainfire.eu/supersu)
Click to expand...
Click to collapse
Wouldn't that wipe my data?

rolgar20 said:
Wouldn't that wipe my data?
Click to expand...
Click to collapse
The only things that will wipe your data:
unlocking the bootloader (which I assume you already have unlocked due to having root access)
flashing userdata.img (if you read my previous post, I left this out)
wiping the data partition in recovery
factory reset option in Android (which really just boots into recovery and wipes data from there)

Elluel said:
The only things that will wipe your data:
unlocking the bootloader (which I assume you already have unlocked due to having root access)
flashing userdata.img (if you read my previous post, I left this out)
wiping the data partition in recovery
factory reset option in Android (which really just boots into recovery and wipes data from there)
Click to expand...
Click to collapse
Wonderful, thanks!

Nothing can be written on internal storage (insert sd card error on camera, etc)

I posted this on reddit...but didn't get much help...i hope the geniuses at xda can help me
As the title says, the camera app (any camera app) won't work because as you start any of them, it asks to insert the sd card, but this is a 2013 Nexus 5...so it doesn't have an sd card.
I've done a fair amount of research and the only thing that seems to be mentioned is factory reset. I've done that...both through the settings and twrp. The phone has a stock marshmallow rom.
I tried to download any other file and it won't let me download anything becauase the "sd card" is not available. So it's as if the internal sd card isn't mounted? how do I fix this? I don't have a computer nearby to do anything with adb...any help would be GREATLY appreciated...
The amount of storage according to the settings is correct (3gb used of 12 gb..16gb nexus 5)...all app permissions are correct. I've reflashed two different stock firmwares with the exact same result.

Try this:
boot into fastboot;
run this fastboot command: fastboot erase recovery (to erase existing recovery);
run this fastboot command: fastboot flash recovery recovery.img (to flash stock recovery from stock ROM)
run this fastboot command: fastboot erase userdata;
run this fastboot command to flash the usedata img from the stock ROM: fastboot flash userdata userdata.img;
boot into stock recovery and perform a factory wipe/reset and wipe cache;
reboot.

audit13 said:
Try this:
boot into fastboot;
run this fastboot command: fastboot erase recovery (to erase existing recovery);
run this fastboot command: fastboot flash recovery recovery.img (to flash stock recovery from stock ROM)
run this fastboot command: fastboot erase userdata;
run this fastboot command to flash the usedata img from the stock ROM: fastboot flash userdata userdata.img;
boot into stock recovery and perform a factory wipe/reset and wipe cache;
reboot.
Click to expand...
Click to collapse
I'll try that tonight or tomorrow morning. Where do you suggest I download recovery.img (the stock recovery)?
Thanks for the help one way or another.. Hehe

The stock Google images are here: https://developers.google.com/android/nexus/images?hl=en
I assume the phone has an unlocked bootloader since you were able to flash stock ROMs.

What did you do between all being fine and now this problem?
Sent from my Xperia z5 using Tapatalk

Ben36 said:
What did you do between all being fine and now this problem?
Sent from my Xperia z5 using Tapatalk
Click to expand...
Click to collapse
I sold the phone to someone I know. I had a rom (i can't remember which)...so before i sold the phone, i encrypted it, wiped it clean, flashed the stock rom (and radio)....and did a factory reset.

audit13 said:
Try this:
boot into fastboot;
run this fastboot command: fastboot erase recovery (to erase existing recovery);
run this fastboot command: fastboot flash recovery recovery.img (to flash stock recovery from stock ROM)
run this fastboot command: fastboot erase userdata;
run this fastboot command to flash the usedata img from the stock ROM: fastboot flash userdata userdata.img;
boot into stock recovery and perform a factory wipe/reset and wipe cache;
reboot.
Click to expand...
Click to collapse
Thanks! I used the factory images and flashed everything from the compressed archive and it worked..you're a lifesaver. I guess I had to go further and reset everything..but thanks again!

Update from 5.1.1 to 6.0.1

Hello, i'm trying to upgrade my rooted nexus 5 from 5.1.1 LMY48I to 6.0.1 MOB30H without losing my data, but at first boot, stops at android logo. I follow this steps with nexus root toolkit:
- Erasing Boot, Cache, Recovery and System.
- Flashing bootloader, radio, cache, boot and system with official .img files from Google developers webpage
- Flashing recovery with TWRP .img
After all these steps, stops on android logo...
Any ideas?

marios.v said:
Hello, i'm trying to upgrade my rooted nexus 5 from 5.1.1 LMY48I to 6.0.1 MOB30H without losing my data, but at first boot, stops at android logo. I follow this steps with nexus root toolkit:
- Erasing Boot, Cache, Recovery and System.
- Flashing bootloader, radio, cache, boot and system with official .img files from Google developers webpage
- Flashing recovery with TWRP .img
After all these steps, stops on android logo...
Any ideas?
Click to expand...
Click to collapse
Do a factory reset

Do NOT use toolkits!
My first advice is: Do NOT flash using toolkits! You never know what's exactly going on if you don't do it manually. There are plenty of reasons why to not use them...
Okay, now my second advice: Don't flash cache partitions. Caches are built during boot/runtime. However, as far as I know, a corrupted cache partition can lead to bootloops - so it's better to just wipe them before boot...
I don't know what the toolkit did and what not - but try to follow these steps:
1. Install fastboot and adb
Preferred method is via Android Studio command line tools from official source: http://developer.android.com/sdk/index.html - Scroll down to "Get just the command line tools". You can decide between an installer or just a zip. It's your choice.
2. Boot your phone in bootloader mode and execute these commands one by one...
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery twrp-recovery.img
fastboot flash system system.img
Click to expand...
Click to collapse
Use the proper files! Extract bootloader and radio from latest Google factory image and download TWRP from twrp.me!
3. Boot your phone into TWRP and choose wipe -> DO NOT SLIDE TO FACTORY RESET -> advanced wipe -> cache + dalvik ticked, rest unticked -> slide to wipe
4. Try to boot...
Not sure if it works - but that's the only thing I can think of right now
EDIT: @GtrCraft That would definitely solve his bootloop, but he wants to keep his data Hopefully he heeds my advice to keep his hands off of toolkits!

experience7 said:
@GtrCraft That would definitely solve his bootloop, but he wants to keep his data Hopefully he heeds my advice to keep his hands off of toolkits!
Click to expand...
Click to collapse
Then he should do all the ota's instead of flashing the factory image
Sent from my XT1562 using XDA Labs

Don't do full-quotes please.
Seriously? His device is rooted and therefore not receiving OTA (over-the-air!) updates. He'd have to catch all of the zips and flash them manually. So why not just use the system.img?

experience7 said:
Don't do full-quotes please.
Seriously? His device is rooted and therefore not receiving OTA (over-the-air!) updates. He'd have to catch all of the zips and flash them manually. So why not just use the system.img?
Click to expand...
Click to collapse
Because you have to factory reset the device. That's the downside of being rooted and wanting to update, especially with M

I'm sorry to say that you're terribly wrong. I hope you didn't factory reset your device every single time you did an update just because you're rooted! Actually you can use the flash-all.bat file that's provided with the factory image. Just remove the "-w" flag from the "fastboot update" command. This will stop fastboot from wiping your /data partition.
That's what the OP could use as well - however, for his better understanding I listed the commands separately.

For what it's worth, this is the script that I've been using since the monthly updates started (copied from another XDA thread which I've forgotten - apologies to the OP of this script).
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash SuperSU
Start to finish - 15 minutes, including the rebuilding of the apps. No data loss (because you haven't touched the data/userdata partition).
I don't say that every step is essential (I note the comment from experience7 about cache) - but this works fine for me.
Please feel free to amend or correct...

dahawthorne said:
For what it's worth, this is the script that I've been using since the monthly updates started (copied from another XDA thread which I've forgotten - apologies to the OP of this script).
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash SuperSU
Click to expand...
Click to collapse
Same problem again. I'm trying all 6.x.x versions but same problem. All commands running without error.

In that case all I can suggest is that you bite the bullet and run the flash-all.bat. Back up all your important stuff (photos, etc.) because you'll lose them.
I've seen it suggested often that you should always do a full wipe when upgrading between major versions (e.g. 5 to 6), so maybe this will fix your problem and give you a working phone even if you lose some data and have to set up from scratch.
P.S. Please "Quick reply" - don't repeat the entire previous post. We've all read it; we don't need to read it again.

marios.v said:
Hello, i'm trying to upgrade my rooted nexus 5 from 5.1.1 LMY48I to 6.0.1 MOB30H without losing my data, but at first boot, stops at android logo. I follow this steps with nexus root toolkit:
- Erasing Boot, Cache, Recovery and System.
- Flashing bootloader, radio, cache, boot and system with official .img files from Google developers webpage
- Flashing recovery with TWRP .img
After all these steps, stops on android logo...
Any ideas?
Click to expand...
Click to collapse
Search for a full guide thread. I'm sure you will come out with something.
Sent from my GT-I9505 using XDA-Developers mobile app

"Search for a full guide thread. I'm sure you will come out with something."
Excellent advice. It's amazing that so many experienced senior members with all their years of combined knowledge missed that blindingly obvious idea...

Problem solved by unfreezing all frozen apps from Titanium Backup before upgrade.
Thank you!