Database Info

[Q] Help!, phone now not working after update

This morning my phone (nexus S) told me it had an update to 4.0.4, which i tapped install. I previously had ICS 4.0 (i think).
When the phone boots up all i get is the flashing colourful spash screen, and it doesn't move on from there.
I tried to get into recovery mode, but all i get is a android man lying down with an exclamation mark over him.
What can i do? what commands for ADB do i need to revert it back to a functional state? I hope its not bricked :-{

Was your phone rooted?
Sent from my GT-I9100 using XDA

rooted
Im not sure what the defination of rooted is but i previously had cyanogen mod on, but reverted back to standard android 2.3 then to the standard android 4, which when installed seem to also remove CWM which i had on.
It is unlocked though

it may work
I will suggest you either you can go to Samsung service center as your phone warranty is not void or nigher you have done anything that is not supported by Samsung or 2nd solution is that download the suitable official ROM from this forum for your phone, and also ODIN, and flash it by going into download mode.
also i will suggest you gain some knowledge how to flash your phone with ODIN before flashing it.

Sounds like you bricked it to me... good luck!!

jackwoz said:
This morning my phone (nexus S) told me it had an update to 4.0.4, which i tapped install. I previously had ICS 4.0 (i think).
When the phone boots up all i get is the flashing colourful spash screen, and it doesn't move on from there.
I tried to get into recovery mode, but all i get is a android man lying down with an exclamation mark over him.
What can i do? what commands for ADB do i need to revert it back to a functional state? I hope its not bricked :-{
Click to expand...
Click to collapse
pull the battery out..and try to enter recovery mod and wipe data/factory resert

Brick or no brick
Hi,
In order to find out if your phone is bricked you need to first remove the battery, replace it and then the do the three key boot to get the phone to boot into download mode.
If that works then you can locate the right firmware and then install via Odin.
If not the next step is to get a jig that forces the phone into download mode (provided it still has bootloaders) and then via Odin again install your firmware.
Otherwise it's a trip to Samsung I think.

Try pulling the battery and wait a few minutes, insert battery and try entering recovery mode again.

[Q] Flashed stock root rom, phone just sits at 4GLTE screen

Hey guys,
I am totally freaking out because I was trying to flash my phone back to a somewhat stock position to erase it and just sort of get back to a stock place and then start flashing again. I tried keeping all the different instructions straight and I think I got turned around someplace.
This is where I am at for what is going on:
Flashed the VRALEC bootchain after I flashed the Stock rooted rom root66_VZW_I535VRBMB1.tar.md5.
The phone currently is accessible for the Odin download mode and when it boots I show the Samsung logo with the lock logo that is unlocked. I am totally not sure where to go from here and need some serious help with what to do next. The phone seems to be simply stock at booting on the 4Glte screen with the Verizon logo.
Any help would be very much appreciated as I am so mixed up as to what to do I don't know where to go and I don't want to make matters worse.
:crying:

NeCr0mStR said:
Hey guys,
I am totally freaking out because I was trying to flash my phone back to a somewhat stock position to erase it and just sort of get back to a stock place and then start flashing again. I tried keeping all the different instructions straight and I think I got turned around someplace.
This is where I am at for what is going on:
Flashed the VRALEC bootchain after I flashed the Stock rooted rom root66_VZW_I535VRBMB1.tar.md5.
The phone currently is accessible for the Odin download mode and when it boots I show the Samsung logo with the lock logo that is unlocked. I am totally not sure where to go from here and need some serious help with what to do next. The phone seems to be simply stock at booting on the 4Glte screen with the Verizon logo.
Any help would be very much appreciated as I am so mixed up as to what to do I don't know where to go and I don't want to make matters worse.
:crying:
Click to expand...
Click to collapse
Pull the battery, boot into recovery (hold volume Up, power, and home), then do a Factory reset.

SlimSnoopOS said:
Pull the battery, boot into recovery (hold volume Up, power, and home), then do a Factory reset.
Click to expand...
Click to collapse
Booting into recovery gives me some message about unauthorized software as I had tried that. I was trying this method but the VRALF bootchain was showing as invalid. I just found a copy of it on invisiblek's site and flashed that and was going to continue with that method trying to get this working. I will update once that has gone through as the stock.vzw_root66.tar image is flashing now. Wish me luck!

Ok, so this time when it finished flashing it rebooted, then it showed the android with the spinning hexagon type thing that you would see when doing a rom backup or something of the sort. I pulled the battery rebooted and did a factory reset along with wiping cache directory and now I am waiting at the 4Glte screen again... Keeping fingers crossed and hoping this works.
AND OMG AWESOME!!!!!
Man, now it is time to get back to flashing. Thank you so much SlimSnoopOS for that last thing I was missing, I really appreciate it.

[Q] Stuck at this device is unlocked screen

Looked around a lot and found no solution so here it goes.
I was trying to update to KitKat and at the Pwr Volume- screen I mistakingly hit the wipe data. I wasn't on a custom ROM before, I used the clockwork mod app to install TWRP. Now I'm stuck on the screen where it says This Device is Unlocked and won't do anything else. I've tried every restart button combo but it always goes back to that screen. Can anyone help me out please or is this a lost cause.
Also the computer does not recognize it since it won't get past the opening screen and fastboot/adb wont do anything either

Wipe data in bootloader mode when unlocked = bricked for good unless you have nvflash backups
Or, if you can get back into bootloader mode, follow busters method to unbrick
Sent from my GS3 on AOSB 4.4.2 using Tapatalk 4

Don't have NVFlash backups and I cant get to the boot loader so I guess I'm boned. Was good while it lasted, was running slow towards the end so I guess it was about that time lol

Pixel stuck in bootloader loop and unable to boot in recovery

As per title, it just happened while I was using the phone while charging. Trying my luck as I'm not in the country(Australia) that I bought my Pixel from. Grateful for any suggestion that the sub can provide. Non rooted stock rom

You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.

Yes only bootloader. What you have mentioned do not require recovery mode right ? Cos I can't boot into it. Thanks for your reply

k.s.deviate said:
You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.
Click to expand...
Click to collapse
The bootloader would have needed to have been unlocked already.

indifferent1 said:
The bootloader would have needed to have been unlocked already.
Click to expand...
Click to collapse
no it doesnt, I suggested unlocking the bootloader first, that way it factory resets. this might fix the problem, if not its unlocked so he can flash the factory image.

Bump? I'm having this problem as well.

Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.

graymoment said:
Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.
Click to expand...
Click to collapse
I'm having the same issue. My wife's Pixel entered a continuous boot loop today. It only loads the white screen that says "Google." I can enter the bootloader, but when I select "recover," it goes back to the bootloop. As far as I know, she is on Android 8.1, debugging mode is off and the phone is 100% factory.
If anyone has solved this issue, it would be greatly appreciated!
Thanks

has anyone figured this out?? this happened to me today, i was using the phone, the poof it restarted itself and stayed in a boot loop. i can get into the recovery, i tried wipe/factory reset. any suggestions? google told me i need to send it to whatever company to get it fixed or get a new phone. verizon told me to go through insurance. insurance told me to go through verizon because i may be able to use the extended warranty. went back to verizon but they wont take it because the screen cracked a year ago. its not a deep crack and it didnt affect the phone at all, never had an issue. so now i go back to assurion and now they need an affidavit about my screen being cracked. im at a loss.... i havent rooted a phone since my droid x, then s3 days. so im essentially new again!

Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots

thedosbox said:
Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots
Click to expand...
Click to collapse
I had the same thing happen yesterday (not long after the Android 10 update). I was finally able to get it to boot after multiple tries and it stayed up long enough for me to enable "OEM unlocking" in Developer options. Now at least I have the option of unlocking the bootloader and re-flashing the OS with an image directly from Google.
Has anyone been able to get past this problem by reflashing the image? I suspect the underlying problem is some kind of hardware fault with eMMC, DDR, or the SOC itself.
One other interesting behavior I noticed is that the only way to shut it down and stop the bootloop is to select the "Power off" option in the bootloader menu. However, if I plug it in to charge when it is fully powered "off", it will start up the bootloop again.

Same sitution here. A couple of days after installaing it suddenly went inte a G-bootloop frenzy.
Erratic though, sometimes I could boot up (2-3/40 boots) but then it froze and started again.
Also Recovery and Safemode is very hard to get into.
Got in once or twice out of 100 boots, Bootloader Fastboot is generally reachable though.
It exhausted the battery and now I'm holding off trying to interfere, until I get more info off the net.

ZTE Axon7 HELP! [TWRP problems??]

Hey guys,
Longtime lurker but first time encountering a problem and needing to register.
I've previously ran a nethunter build on an old Nexus 6 which went fine. Now I've picked up the ZTE Axon7 as I needed a new phone.
I followed this thread: HERE
I successfully was able to follow along and get TWRP as my bootloader.
I then followed the instructions to go HERE to grab the Axon7 img file and tried the "TWRP Install" method (install the image to recovery and flash it)
Now upon reboot, I get the ZTE logo (the red dot shows up at the same time like a normal boot) then the log and dot disappear with the red dot then doing one quick flash afterwards. From there the device is just off. Even if I try doing a reboot to the bootloader via power + VolUp the same thing happens. Essentially I think this means the entire bootloader from twrp is now gone??? Plugging into my PC I still get the sound of a device connecting but it is not seen in Windows. HOWEVER while the device is connected to my PC I AM still able to see the Qualcomm port in my Device Manager.
Is there any way to go back to having an OS????? Even my backups I made??? It just seems like there isn't even the bootloader anymore and I just don't know what to do :crying:
If someone could PLEASE help it would mean the world to me!

Did you ever get this resolved?

xerxes_ said:
Hey guys,
Longtime lurker but first time encountering a problem and needing to register.
I've previously ran a nethunter build on an old Nexus 6 which went fine. Now I've picked up the ZTE Axon7 as I needed a new phone.
I followed this thread: HERE
I successfully was able to follow along and get TWRP as my bootloader.
I then followed the instructions to go HERE to grab the Axon7 img file and tried the "TWRP Install" method (install the image to recovery and flash it)
Now upon reboot, I get the ZTE logo (the red dot shows up at the same time like a normal boot) then the log and dot disappear with the red dot then doing one quick flash afterwards. From there the device is just off. Even if I try doing a reboot to the bootloader via power + VolUp the same thing happens. Essentially I think this means the entire bootloader from twrp is now gone??? Plugging into my PC I still get the sound of a device connecting but it is not seen in Windows. HOWEVER while the device is connected to my PC I AM still able to see the Qualcomm port in my Device Manager.
Is there any way to go back to having an OS????? Even my backups I made??? It just seems like there isn't even the bootloader anymore and I just don't know what to do :crying:
If someone could PLEASE help it would mean the world to me!
Click to expand...
Click to collapse
First, TWRP is a custom recovery, not a bootloader.
Second, it seems to me that your device has a locked bootloader, you have to have an UNLOCKED bootloader to flash TWRP, flashing TWRP without unlocking bootloader brocks devices. You need to restore your stock firmware.
What exactly does device manager label your device as when you connect to PC?
Sent from my SCH-I535 using Tapatalk

MelloZ said:
Did you ever get this resolved?
Click to expand...
Click to collapse
Yes, DrakenFX helped me out. Ended up being a long complicated process that I couldn't really rewrite here if I tried.