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

Remove twrp and get back to factory state, need help!!!

Hi guys
I'll receive the rma device tomorrow and i wanted to set to factory state the one i have right now , so that i can send it back to google.
I have installed a custom recovery(twrp) and rooted the device.
Would any one be so kind to guide me to the the reverse process and make the device like it was when it shipped to me.
Thanks in andvance

td32 said:
Hi guys
I'll receive the rma device tomorrow and i wanted to set to factory state the one i have right now , so that i can send it back to google.
I have installed a custom recovery(twrp) and rooted the device.
Would any one be so kind to guide me to the the reverse process and make the device like it was when it shipped to me.
Thanks in andvance
Click to expand...
Click to collapse
See here.

gregc2009 said:
See here.
Click to expand...
Click to collapse
is it necesary to execute all this commands
Code:
fastboot flash bootloader C:/image-hammerhead-krt16m/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-hammerhead-krt16m/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-hammerhead-krt16m/system.img
fastboot flash userdata C:/image-hammerhead-krt16m/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/image-hammerhead-krt16m/boot.img
fastboot flash recovery C:/image-hammerhead-krt16m/recovery.img
fastboot erase cache
or this is enough for my case?
Code:
fastboot flash recovery C:/image-hammerhead-krt16m/recovery.img
fastboot erase cache
just flash the recovery image then
Wipe data/factory data reset"
and for last lock the bootloader?

td32 said:
is it necesary to execute all this commands
Code:
fastboot flash bootloader C:/image-hammerhead-krt16m/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-hammerhead-krt16m/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-hammerhead-krt16m/system.img
fastboot flash userdata C:/image-hammerhead-krt16m/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/image-hammerhead-krt16m/boot.img
fastboot flash recovery C:/image-hammerhead-krt16m/recovery.img
fastboot erase cache
or this is enough for my case?
Code:
fastboot flash recovery C:/image-hammerhead-krt16m/recovery.img
fastboot erase cache
just flash the recovery image then
Wipe data/factory data reset"
and for last lock the bootloader?
Click to expand...
Click to collapse
I would do it all just to make sure you are back to complete stock since you mentioned you rooted the device also.

Follow the instructions in the first post of this thread and since you plan to RMA the phone be sure to check the tamper flag and follow the steps outlined to reset it if necessary... http://forum.xda-developers.com/showthread.php?p=47156064
[TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5
Sent from my Nexus 5 using xda app-developers app

chef_christoph said:
Follow the instructions in the first post of this thread and since you plan to RMA the phone be sure to check the tamper flag and follow the steps outlined to reset it if necessary... http://forum.xda-developers.com/showthread.php?p=47156064
[TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Code:
. If the tamper flag value is "true", then you'll have to reset it. The following steps will reset this flag, and lock your bootloader.
•So, first, go here: http://forum.xda-developers.com/show....php?t=2239421 (Thanks @osm0sis for the wonderful script)
Under "Flashable Zips", you will find the Nexus BootUnlocker script. Download it.
•Put the zip on your internal storage.
•Download the latest TWRP recovery image for the Nexus 5 from here: http://techerrata.com/browse/twrp2/hammerhead. Rename it to TWRP.img.
Now boot it. You do this by booting your phone in fastboot, and typing the following command:
Code:
fastboot boot path/to/TWRP.img
TWRP recovery should boot.
•Flash the zip in TWRP, then reboot.
Now your bootloader should be locked, and your tamper flag should show "false".
So i have to do this before i flash the stock recovery, since it needs TWRP, am i right?
And else it says that this will lock the bootloader, will i be able to execute the previous commands(flashing recovery and stuff) with a locked bootloader?

td32 said:
So i have to do this before i flash the stock recovery, since it needs TWRP, am i right?
And else it says that this will lock the bootloader, will i be able to execute the previous commands(flashing recovery and stuff) with a locked bootloader?
Click to expand...
Click to collapse
No, flash everything back to stock then deal with the tamper flag reset.
Once everything is back to stock but the bootloader is still unlocked, boot into the recovery...
fastboot boot nameofrecovery.img
Then flash the tamper flag script.
Sent from my Nexus 5 using xda app-developers app

chef_christoph said:
No, flash everything back to stock then deal with the tamper flag reset.
Once everything is back to stock but the bootloader is still unlocked, boot into the recovery...
fastboot boot nameofrecovery.img
Then flash the tamper flag script.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Sorry man but i'm not getting something here.
If i flash everything first, even the recovery will be stock, so i have to flash twrp once again to flash the tamper flag script. So i end up with twrp recovery and the tamper flag reset, while it should be stock recovery and tamper flag reset.
What i'm i missing here?

You can boot a custom recovery without flashing it. Like a temporary installation
Sent from my Nexus 5

pepdavies said:
You can boot a custom recovery without flashing it. Like a temporary installation
Sent from my Nexus 5
Click to expand...
Click to collapse
ok thank, now its all clear
i should have paid more attention to the command :silly:
It says boot not flash :silly:
Thanks for you help guys

[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.

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!

How to update newest images without wiping or losing TWRP ?

When there's a new image next month I want to update to can I just use fastboot and flash everything except recovery then reboot and keep.twrp and ha e the newest image without losing data ?
Fastboot flash
Bootloader
Modem
System
Syatem_other
Vendor
Skipping the others then reboot and still have TWRP ? Right now my goal is just to use a stock image, ElementalX kernel and root with TWRP. Just passing on the custom ROMs right now

There's a lot of . img files.
This is more complex than my Nexus 5x which just had a few . img
I don't understand which is which

mikeprius said:
There's a lot of . img files.
This is more complex than my Nexus 5x which just had a few . img
I don't understand which is which
Click to expand...
Click to collapse
You can't do what you want to do because recovery is located in the boot.img file on the Pixel. There is no dedicated recovery partition like on other phones. The only way to do it would be to flash everything but the boot.img file. That may work but if you did do that, you'd miss out on any security updates or whatever other updates there may be to the kernel. I'd recommend just flashing it all. It doesn't take very long to flash TWRP again. A minor inconvenience if you ask me.

I think THIS can help. Follow method 2 - manual.
But skip recovery.img and cache.img (also because there aren't those files) and the userdata.img

robocuff said:
You can't do what you want to do because recovery is located in the boot.img file on the Pixel. There is no dedicated recovery partition like on other phones. The only way to do it would be to flash everything but the boot.img file. That may work but if you did do that, you'd miss out on any security updates or whatever other updates there may be to the kernel. I'd recommend just flashing it all. It doesn't take very long to flash TWRP again. A minor inconvenience if you ask me.
Click to expand...
Click to collapse
Ok thanks for the info. I've been flashing for awhile, but the set up here is very different than prior phones.
So pretty much just run the flash-all.bat, TWRP.img, TRWP.zip, the SuperSU ?
Can I modify the flash-all to prevent wiping, or is it just best to re-do everything fresh ?

TENN3R said:
I think THIS can help. Follow method 2 - manual.
But skip recovery.img and cache.img (also because there aren't those files) and the userdata.img
Click to expand...
Click to collapse
Have you tried this ? I read this article earlier and that's what's confusing:
So here's the process:
bootloader-xxx-xxx.img
radio-xx-xx-xx.img
boot.img
system.img
system_other.img
vendor.img
modem.img
but then later in the article it says:
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot flash userdata userdata.img
it appears there are many other files included beyond this list.

mikeprius said:
Ok thanks for the info. I've been flashing for awhile, but the set up here is very different than prior phones.
So pretty much just run the flash-all.bat, TWRP.img, TRWP.zip, the SuperSU ?
Can I modify the flash-all to prevent wiping, or is it just best to re-do everything fresh ?
Click to expand...
Click to collapse
Modify it, remove the -w
Been doing it that way back to my Nexus 6. No issues.

TonikJDK said:
Modify it, remove the -w
Been doing it that way back to my Nexus 6. No issues.
Click to expand...
Click to collapse
Can I do this dirty ? Basically just flash the stock images over the old, remove -w, then reboot, everything updated ? I don't mind booting the TWRP image and re-flashing superSU, just having to restore from scratch is a pain in the ass

mikeprius said:
Can I do this dirty ? Basically just flash the stock images over the old, remove -w, then reboot, everything updated ? I don't mind booting the TWRP image and re-flashing superSU, just having to restore from scratch is a pain in the ass
Click to expand...
Click to collapse
There's no need to wipe anything. Just make sure to remove the -w from the flashall.bat (dont forget to save it after doing so). If you do it this way, you'll end up with an updated phone with all your data in tact. Same as if you took an OTA.

robocuff said:
There's no need to wipe anything. Just make sure to remove the -w from the flashall.bat (dont forget to save it after doing so). If you do it this way, you'll end up with an updated phone with all your data in tact. Same as if you took an OTA.
Click to expand...
Click to collapse
Cool cool thanks. Will try this next month's update.

mikeprius said:
Can I do this dirty ? Basically just flash the stock images over the old, remove -w, then reboot, everything updated ? I don't mind booting the TWRP image and re-flashing superSU, just having to restore from scratch is a pain in the ass
Click to expand...
Click to collapse
Just to reinforce the post above, I always flash dirty. No issues.