Related
My sisters gnex is acting strange.
I try to unlock bootloader.. it says unlocked, and when rebooted, says again locked.. (in fastboot)
Also when i try to reset the phone(factory reset), using stock recovery, or the option in the settings, NOTHING happens!!!
The phone reboots, and it is in the same state it was a couple of days ago with:
gps opened, 3g enabled...
Whatever i do to the phone, it restores to that state...
Also some random reboots occured in the past, and phone again went to this state, no matter what changes you do on the phone. eg my sister put face unlock.. and after a random reboot we got:
previous unlock method and.. gps on, 3g enabled..
Any ideas???
Phone is on 4.0.4, and IMM76K..
3.0.8 kernel.
Stock
now, i unistalled all apps, restarted, and ALL was back there...
even gps was open...
It seems we cannot do any change....
I would return it, and get a new one.
Sent from my i9250
isnt any solution to this?
fastboot command for factory reset is:
fastboot erase userdata
and ..
fastboot erase cache
?
How do I relock my verizon pixel bootloader without bricking it? I'm 100% on stock X rom anyway, radios and all. I never rooted or ROM'd.
reason behind it, is I want android pay and other things to work like the android lock so if you lose your phone, kind of like icloud lock I assume?. I don't root or rom my phone anymore since galaxy nexus days, I like the stock ROM... and if Verizon is on PAR with giving OTAs immediately as google says they will be controlling OTAs, there isnt a reason for me to unlock this thing anymore. I only unlocked it strictly if Verizon was going to delay stuff.
adb reboot bootloader
fastboot flashing lock
deuce_biggins said:
adb reboot bootloader
fastboot flashing lock
Click to expand...
Click to collapse
so just command promp reboot into bootloader and then
fastboot flashing lock ??
this will not brick my phone as long as im 100% stock which i am? i'm not clean flashed stock, i have apps, etc. but on latest google X build (verizon) right from their website.
imablackhat said:
so just command promp reboot into bootloader and then
fastboot flashing lock ??
this will not brick my phone as long as im 100% stock which i am? i'm not clean flashed stock, i have apps, etc. but on latest google X build (verizon) right from their website.
Click to expand...
Click to collapse
Two things:
1) If your system is normally booting and stock 100%, relock should be fine. in case you do randomly get a red screen after "fastboot flashing lock" and cannot boot... Press power button on the red warning (to pause boot), and "fastboot continue" will allow you to boot and you would then have to unlock again and flash factory image. The "continue" command only reliably works if BEFORE you lock bootloader you can still boot.
2) Do a back up. Boot into OS. Turn on USB debugging and turn on your home screen. Then:
adb backup -all -apk -shared -f backup-Dec1.ab
And restore after locking bootloader. The reason for this is that locking bootloader will probably wipe your device just like unlocking it.
Sent from my sailfish using XDA Labs
nednednerb said:
in case you do randomly get a red screen after "fastboot flashing lock" and cannot boot... Press power button on the red warning (to pause boot), and "fastboot continue" will allow you to boot and you would then have to unlock again and flash factory image. The "continue" command only reliably works if BEFORE you lock bootloader you can still boot.
Click to expand...
Click to collapse
I never hear of this. Can you tell me more?
cam30era said:
I never hear of this. Can you tell me more?
Click to expand...
Click to collapse
It might be new to SDK api 25, but it is the advice I find given to people who foolishly lock their bootloader when not 100% stock (like me).
Basically on the pixel bootloader, it checks for corruption before booting. If you've rooted etc, you must have seen the yellow warning. If system is 1% modified (eg: unlocked), it gives the warning. Pretty sure if you lock bootloader at that point and not 100% stock, it gives red warning and cannot boot.
However, if system COULD boot, "fastboot continue" saves day from red warning.
If you would have been stuck in bootloop and then lock, may be SoL.
Trying the continue command a couple more times after getting stuck rebooting MAY work too, if lucky.
In this scenario... After you get back into OS, unlocking bootloader again is the move to make.
Sent from my sailfish using XDA Labs
nednednerb said:
It might be new to SDK api 25, but it is the advice I find given to people who foolishly lock their bootloader when not 100% stock (like me).
Basically on the pixel bootloader, it checks for corruption before booting. If you've rooted etc, you must have seen the yellow warning. If system is 1% modified (eg: unlocked), it gives the warning. Pretty sure if you lock bootloader at that point and not 100% stock, it gives red warning and cannot boot.
However, if system COULD boot, "fastboot continue" saves day from red warning.
If you would have been stuck in bootloop and then lock, may be SoL.
Trying the continue command a couple more times after getting stuck rebooting MAY work too, if lucky.
In this scenario... After you get back into OS, unlocking bootloader again is the move to make.
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
So say in theory this happened, however you're able to get into Fastboot and such, how might you fix that?
Tisch22 said:
So say in theory this happened, however you're able to get into Fastboot and such, how might you fix that?
Click to expand...
Click to collapse
If you cannot boot into OS, fastboot continue won't help.
If your bootloader is locked, you can't do anything with fastboot.
The hope is "continue" gets you passed red warning, and you can unlock bootloader again. If you can't boot at that point, unlikely to have solution,
Sent from my sailfish using XDA Labs
nednednerb said:
If you cannot boot into OS, fastboot continue won't help.
If your bootloader is locked, you can't do anything with fastboot.
The hope is "continue" gets you passed red warning, and you can unlock bootloader again. If you can't boot at that point, unlikely to have solution,
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
Fastboot continue does load up the OS, however once it starts optimizing the apps it goes to a black screen.
nednednerb said:
If you cannot boot into OS, fastboot continue won't help.
If your bootloader is locked, you can't do anything with fastboot.
The hope is "continue" gets you passed red warning, and you can unlock bootloader again. If you can't boot at that point, unlikely to have solution,
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
Scratch that, I was able to get back into the OS via "Fastboot continue" however unlocking the bootloader again to reflash the img is becoming quite troublesome.
Okay, today evening, my Nexus 5X rebootet already 5 times while I was using it just as every evening (browsing web, watching youtube, nothing special).
After the second reboot, it actually vibrated two times during the boot animation (after entering the decryption pin) like it usually only does when powering it up.
After the third reboot, it bootlooped for more than 30min (!!) ... Just the bootloader (white google logo), then ~3s black screen, then vibrating and Google Logo again!
Entering boot menu was possible... I used it to power off and reboot, but didn't help. I was just letting it bootloop while I searched my old Nexus 4 to reactivate it
After the 30min or more bootlooping (by the time I already found my Nexus 4 and reinstalled its battery ) the Nexus 5X asked for decryption pin.... I entered it, it rebootet. It asked again. If finally bootet.
After ~3min of use (just enough for a whatsapp backup) it rebootet again and bootlooped again for ~15min. And same again.
Now it is back once again - for the moment.
I need help, what can I do now, except backing up all relevant data?
It is stock android, not rooted, bootloader locked
Can I somehow test the memory? See why it rebooted?
It NEVER rebooted before since I own it...
Thx
The device rebooted after few minutes yesterday... It still overcomes the first bootloop from time to time after dozens of bootloops but then crashes most of the time after I was able to enter the pin. Since yesterday, it only managed to finish booting two times but always rebooted after few minutes.
Is this the famous BLOD? Haven't heard of it until today (sorry) ...
I actually had OEM unlock enabled in the developer menu, so I could actually unlock the bootloader...
Can I verify that it actually is the BLOD by unlocking the bootloader and temporary booting the modified boot image using fastboot? I don't want to flash something at the moment, because I might get it replaced... I can lock the bootloader again afterwards, right?
I think it might be possible to use "fastboot boot boot.img" (using the 4-core kernel image) from the bootloader screen. That won't install anything.
Thx. However, it requires me to unlock the bootloader and delete all data, since there is no 4-core kernel provided/signed by google, right? I will be able to lock the bootloader again afterwards, as long as I won't flash a different kernel (or reflash the stock kernel), right?
dude while your phone is on, first backup your files, then enable OEM unlock, if your phone is damaged with bootloop of dead, you will be able to make it work using the 4 kernels fix.
caifaz said:
dude while your phone is on, first backup your files, then enable OEM unlock, if your phone is damaged with bootloop of dead, you will be able to make it work using the 4 kernels fix.
Click to expand...
Click to collapse
I do have all important data backed up, I guess. Doing Backups for Android is just PITA... I wasn't able to get the phone running for more than a few minutes today. OEM unlock is enabled, but the bootloader is locked still, so all data will be deleted. I'll try the 4 core kernel as soon as I completely restored all data to my replacement phone, so I'm really confident I can wipe all data from the old one.
Thx so far!
RFZ said:
I do have all important data backed up, I guess. Doing Backups for Android is just PITA... I wasn't able to get the phone running for more than a few minutes today. OEM unlock is enabled, but the bootloader is locked still, so all data will be deleted. I'll try the 4 core kernel as soon as I completely restored all data to my replacement phone, so I'm really confident I can wipe all data from the old one.
Thx so far!
Click to expand...
Click to collapse
you're welcome, there is no need to flash a bootloader, just flash the TWRP recovery (modded for 4 cores), restart to recovery and then flash EX kernel (modded for 4 cores) according to you SO version.
I have fixed a phone 2 years ago using this instructions
Okay, I just verified it... The device boots fine with the 4 core kernel. I then reflashed the stock image, locked the bootloader, and it bootloops again. Will send it back to the store now and hope I'll get a refund/replacement :fingers-crossed:
Hi, so here's what happened. Over time the phone started to freeze up (I used this phone unlocked on T-Mobile) more and more often, the screen would bug out and it would just straight up freeze. So I managed to turn on usb debugging and oem unlock in developer setting and then I did a complete odin flash to Nougat. Everything seemed fixed until I was changing some settings when it started bootlooping. I have reflashed several times, still bootloops. I tried PrinceComsy's odin, now it just stalls on the samsung galaxy screen and doesn't even bootloop. Also this may be unrelated/irrelevant but while I shake the phone I can hear something loose on the inside bouncing around. What do you guys think?
blu422 said:
Hi, so here's what happened. Over time the phone started to freeze up (I used this phone unlocked on T-Mobile) more and more often, the screen would bug out and it would just straight up freeze. So I managed to turn on usb debugging and oem unlock in developer setting and then I did a complete odin flash to Nougat. Everything seemed fixed until I was changing some settings when it started bootlooping. I have reflashed several times, still bootloops. I tried PrinceComsy's odin, now it just stalls on the samsung galaxy screen and doesn't even bootloop. Also this may be unrelated/irrelevant but while I shake the phone I can hear something loose on the inside bouncing around. What do you guys think?
Click to expand...
Click to collapse
The noise you hear when you shake it might be the camera. I have that too. The root of your problem may be a burned mother board and/or SD card though. Hardware replacement would be required if I'm right.
I know flashing roms are easy. But it might be difficult for newcomers like me. I have always a question in mind what'll happen if my phone shut down due to low battery in fastboot/recovery. If I format the OS before shutdown, is it possible to charge the phone offline without no OS then continue flashing roms?
##Following things happened with me.
I was in MIUI 12.5. I installed Pixel Recovery to flash PE12 via adb sideload. Then I cleared all data/cache. When I tried to update the rom by sideload, it didn't work. I wanted to search the internet and as it would take time, I tried to turn the phone off. I couldn't even shut the phone to save battery. Whenever I pressed power button, instead of shutting down, it always took me to the bootloader menu. Thats when I thought about this question.
that question is so out of the box, i doubt anyone can give you an answer with proof
but yes, i believe it is possible to charge even without OS and no, i dont have any proof to back this up
That's why you need to charge phone first at least until 50% up before flashing any rom.. otherwise if still happen phone shutdown while flashing, yes you still can recover as long your phone bootloader still at unlocked stats also phone still can go into fastboot
If it shuts down when in fastboot/recovery because the battery is empty, you simply charge it and reboot, that should cause no harm. Shutting down while flashing a ROM however is a totally different story. You might get lucky and be able to boot the phone back into fastboot/recovery or you could end up with a paperweight.
jadephyre said:
If it shuts down when in fastboot/recovery because the battery is empty, you simply charge it and reboot, that should cause no harm. Shutting down while flashing a ROM however is a totally different story. You might get lucky and be able to boot the phone back into fastboot/recovery or you could end up with a paperweight.
Click to expand...
Click to collapse
I did shutdown the phone within fastboot to cancel flash all and lock....then booted in forced fastboot end flashed with flash all to not lock the bootloader....and had no prob....! I think those partitions are protected against those scenarios....
Following things happened with me.
I was in MIUI 12.5. I installed Pixel Recovery to flash PE12 via adb sideload. Then I cleared all data/cache. When I tried to update the rom by sideload, it didn't work. I wanted to search the internet and as it would take time, I tried to turn the phone off. I couldn't even shut the phone to save battery. Whenever I pressed power button, instead of shutting down, it always took me to the bootloader menu. Thats when I thought about this question.
Addymore said:
I did shutdown the phone within fastboot to cancel flash all and lock....then booted in forced fastboot end flashed with flash all to not lock the bootloader....and had no prob....! I think those partitions are protected against those scenarios....
Click to expand...
Click to collapse
No. NO NO NO and NO.
You were lucky. This can totally brick your phone. Critical partitions are being modified in the Flashing-process.
There is no protection.
If your phone shuts down during the Flashing-process, your phone can get bricked (black screen) and you can't even boot Fastboot & Recovery anymore. I know this. I have experience.
You must ensure that you have enough Battery (I recommend 75% Battery at least), that the USB connection is stable (will not disconnect randomly), and that your PC won't crash/shut down.
IF IT HAPPENS, that the Flashing-process errors out, DON'T REBOOT THE PHONE. If you do so, you won't be able to enter Fastboot anymore. You must stay in Fastboot. Just reconnect USB, and try again to Flash. Just don't reboot the phone.
Sorry for fear-mongering, but this is definitely dangerous and not to be taken lightly.
dreamytom said:
No. NO NO NO and NO.
You were lucky. This can totally brick your phone. Critical partitions are being modified in the Flashing-process.
There is no protection.
If your phone shuts down during the Flashing-process, your phone can get bricked (black screen) and you can't even boot Fastboot & Recovery anymore. I know this. I have experience.
You must ensure that you have enough Battery (I recommend 75% Battery at least), that the USB connection is stable (will not disconnect randomly), and that your PC won't crash/shut down.
IF IT HAPPENS, that the Flashing-process errors out, DON'T REBOOT THE PHONE. If you do so, you won't be able to enter Fastboot anymore. You must stay in Fastboot. Just reconnect USB, and try again to Flash. Just don't reboot the phone.
Sorry for fear-mongering, but this is definitely dangerous and not to be taken lightly.
Click to expand...
Click to collapse
I think it is because I forced fastboot mode after few seconds of starting flashing....by the way I was avoid the flash and lock option that I selected by error while I wanted flash and clean...
I think, there is no ptoblem, fastboot Mode is Read Only Memory, no one can write/edit this think.
No matter you abort the flashing prosses , or the device loss power from battery, didn't affect the fastboot sector/bios on PC
*IMO