Hey guys, currently stuck in a bootloop....I think it's a hardware problem so I'm currently waiting on an RMA.
I was rooted and unlocked...tried flashing everything via fastboot to stock but it keeps boot looping on the Google logo and I can't access recovery.
Any recommendations/things to try? If nothing works I'd at least like to reset the tamper flag before I RMA it.
Thanks!
Ed
did you flash stock recovery in fastboot?
what are the returns in command prompt when you flash the img files?
mistahseller said:
did you flash stock recovery in fastboot?
Click to expand...
Click to collapse
Yep, I followed someone's steps, tried the whole process a couple times and I couldn't get it working.
Not sure, I'm sorry I don't have access to my phone right now...I believe it ran everything without error but it won't go through to recovery. I'll try it again and post my results. Any recommendations for the time-being or is it tough to say?
Anastasios912 said:
Hey guys, currently stuck in a bootloop....I think it's a hardware problem so I'm currently waiting on an RMA.
I was rooted and unlocked...tried flashing everything via fastboot to stock but it keeps boot looping on the Google logo and I can't access recovery.
Any recommendations/things to try? If nothing works I'd at least like to reset the tamper flag before I RMA it.
Thanks!
Ed
Click to expand...
Click to collapse
Can you get into the bootloader and flash a stock image in fastboot?
yes try again from fastboot and let us know.
Could be memory failure which means RMA, and I think someone posted on the forum that google does not care if the tamper flag is not reset.
gee2012 said:
Can you get into the bootloader and flash a stock image in fastboot?
Click to expand...
Click to collapse
Tried that...and no dice. Do you think google will cover it despite the tamper flag being triggered? I relocked the bootloader but can't get in to reset the tamper flag (unless there's a way to do that without recovery)
Why can't you access stock recovery? Do you see the Android laying on his back after you try to boot to recovery? If so, hold Volume Up + Volume Down until it boots into stock recovery.
If that works for you, perform a factory reset + cache wipe from stock recovery after fastboot flashing factory images. Should clear up any boot loops so long as your memory isn't corrupted...
Edit: Yes you're going to want to do all that with an UNLOCKED boot loader...
Code:
fastboot OEM unlock
Anastasios912 said:
Tried that...and no dice. Do you think google will cover it despite the tamper flag being triggered? I relocked the bootloader but can't get in to reset the tamper flag (unless there's a way to do that without recovery)
Click to expand...
Click to collapse
If you relocked the BL you cannot reset the tampered flag or flash a stock image, first you flash the image, reset the flag and then you lock the BL
BTW if you used the Bootunlocker.zip it both resets the flag and locks the bootloader.
gee2012 said:
If you relocked the BL you cannot reset the tampered flag or flash a stock image, first you flash the image, reset the flag and then you lock the BL
BTW if you used the Bootunlocker.zip it both resets the flag and locks the bootloader.
Click to expand...
Click to collapse
Haha yea I understand that, I meant I can't get into recovery to reset the tamperflag. After messing with it for a while I gave up and figured I'd at least relock the bootloader in case they check for that.
Not sure why I can't get into recovery RoyJ that's why I'm here lol. I click 'recovery' and the bootloop continues.
Anastasios912 said:
Haha yea I understand that, I meant I can't get into recovery to reset the tamperflag. After messing with it for a while I gave up and figured I'd at least relock the bootloader in case they check for that.
Not sure why I can't get into recovery RoyJ that's why I'm here lol. I click 'recovery' and the bootloop continues.
Click to expand...
Click to collapse
Do you have stock or custom recovery?
Related
I'm trying to recover to stock after having a custom ROM for a few days (Cyanogenmod, nothing too fancy).
I was using this guide over on the Nexus dev forum:
http://forum.xda-developers.com/showthread.php?t=2513701
Everything went smoothly until after I flashed the bootunlocker zip to revert the tampered flag back to normal. Then the reboot loop happened.
I've flashed multiple times using both methods to no avail. I also updated the driver on Windows 7.
dabockster said:
I'm trying to recover to stock after having a custom ROM for a few days (Cyanogenmod, nothing too fancy).
I was using this guide over on the Nexus dev forum:
http://forum.xda-developers.com/showthread.php?t=2513701
Everything went smoothly until after I flashed the bootunlocker zip to revert the tampered flag back to normal. Then the reboot loop happened.
I've flashed multiple times using both methods to no avail. I also updated the driver on Windows 7.
Click to expand...
Click to collapse
Try to get into recovery and clear the caches and do a data factory reset. Just hold power down and power at the same time and select recovery.
gee2012 said:
Try to get into recovery and clear the caches and do a data factory reset. Just hold power down and power at the same time and select recovery.
Click to expand...
Click to collapse
This works, and it gets me working again. But I would like to reset that flag if possible. It all breaks when I flash the zip found here:
http://forum.xda-developers.com/showthread.php?t=2239421
The NexusBootUnlocker script is what is being referenced in the restoration guide.
dabockster said:
This works, and it gets me working again. But I would like to reset that flag if possible. It all breaks when I flash the zip found here:
http://forum.xda-developers.com/showthread.php?t=2239421
The NexusBootUnlocker script is what is being referenced in the restoration guide.
Click to expand...
Click to collapse
Did you boot into TWRP to flash the Bootlocker.zip? In cmd type `fastboot boot twrp.img` (or the name you have given it) and reboot?
dabockster said:
This works, and it gets me working again. But I would like to reset that flag if possible. It all breaks when I flash the zip found here:
http://forum.xda-developers.com/showthread.php?t=2239421
The NexusBootUnlocker script is what is being referenced in the restoration guide.
Click to expand...
Click to collapse
You can use that script with twrp by booting it as mentiomed above or if u r rooted then u can also use nexus bootunlocker from play store.
gee2012 said:
Did you boot into TWRP to flash the Bootlocker.zip? In cmd type `fastboot boot twrp.img` (or the name you have given it) and reboot?
Click to expand...
Click to collapse
Yep. I have done the guide to the letter and followed the video. Nothing.
And it might be worth noting that I am doing this on a red Nexus 5 (the new color). Maybe Google changed something?
dabockster said:
Yep. I have done the guide to the letter and followed the video. Nothing.
And it might be worth noting that I am doing this on a red Nexus 5 (the new color). Maybe Google changed something?
Click to expand...
Click to collapse
No, that doesn`t make a difference. What do you see when you type in cmd: `fastboot oem device-info` with the phone in bootloader?
gee2012 said:
No, that doesn`t make a difference. What do you see when you type in cmd: `fastboot oem device-info` with the phone in bootloader?
Click to expand...
Click to collapse
It shows that the bootloader is locked and the tampering flag is false, just like the tutorial said. However, normal boot results in a loop.
dabockster said:
It shows that the bootloader is locked and the tampering flag is false, just like the tutorial said. However, normal boot results in a loop.
Click to expand...
Click to collapse
So it worked, now go into recovery and wipe the caches and do a data factory reset and then it should boot normaly.
Don't use the zip then. Unlock the bootloader, root the phone and download bootunlocker app.
Then, reset tamper and lock from the app. Unroot using supersu
Sent from my Nexus 5 using Tapatalk
gee2012 said:
So it worked, now go into recovery and wipe the caches and do a data factory reset and then it should boot normally.
Click to expand...
Click to collapse
Nope, won't boot to recovery. All I have is the adb at the bootloader.
EDIT: Tried unplugging the USB while it was booting. This fixed everything! Thanks for the help!
dabockster said:
Nope, won't boot to recovery. All I have is the adb at the bootloader.
Click to expand...
Click to collapse
What happens when you type in cmd: fastboot reboot recovery ?
dabockster said:
Nope, won't boot to recovery. All I have is the adb at the bootloader.
Click to expand...
Click to collapse
When you say it won't boot into recovery do you get the dead android with the red exclamation mark? That is recovery just hit vol up
Sent from my Nexus 5
dabockster said:
Nope, won't boot to recovery. All I have is the adb at the bootloader.
Click to expand...
Click to collapse
You can't use adb at the bootloader
Only fastboot works
Sent from my Nexus 5 using Tapatalk
So I just tried booting it while unplugged from my computer and it worked flawlessly. This bit should be added to future unroot guides.
Thanks for the help!
Ok so today i wanted to root my nexus 5 so i unlocked bootloader via androidSDK slim everything went fine but i did not power up my device yet thet i flash the recovery.img of twrp after that i booted into recovery and for a second it displayed some error i could not see it but it said could not read /e..... or i think so and it reboted itself and started booting android and now i think im stuck in boot loop because its booting up for 10 mins. can someone help me?
So now your Bootloader is unlocked, right?
First boot after unlocking the Bootloader takes time... Wait for 10 more mins and then reboot once again and see whether you can get the OS to bootup...
If you can't, you can either try factory reseting from Bootloader or you can flash a custom recovery and then install a custom rom of your choice.
Or you can also go full stock and start over again by flashing a factory image...
-Sent from an IceCold Hammerhead!
You're supposed to reboot the bootloader before flashing anything.
vin4yak said:
So now your Bootloader is unlocked, right?
First boot after unlocking the Bootloader takes time... Wait for 10 more mins and then reboot once again and see whether you can get the OS to bootup...
If you can't, you can either try factory reseting from Bootloader or you can flash a custom recovery and then install a custom rom of your choice.
Or you can also go full stock and start over again by flashing a factory image...
-Sent from an IceCold Hammerhead!
Click to expand...
Click to collapse
yes it is unlocked as i sad and i installed twrp so i have custom recovery ok ill wait a bit more and see what happends. what happens if i factory reset from bootloder?
rootSU said:
You're supposed to reboot the bootloader before flashing anything.
Click to expand...
Click to collapse
after it sad that unlocking is done with ulocking on command promt on my pc and on my phone i flashed the recovery right away. Now i turned my phone down by pressing power and vol down button and booted recovery and it did boot fine in twrp no with errors like first time so i gone to reboot and then system and it said that my phone is not rooted and to install super su i did that and now its booting up for like 10mins again still cant boot up into android. what can i do to fix this?
Alexandar92zr said:
after it sad that unlocking is done with ulocking on command promt on my pc and on my phone i flashed the recovery right away
Click to expand...
Click to collapse
This was your first mistake
Alexandar92zr said:
i turned my phone down by pressing power and vol down button and booted recovery and it did boot fine in twrp no with errors like first time so i gone to reboot and then system and it said that my phone is not rooted and to install super su i did that
Click to expand...
Click to collapse
And this the second mistake. Nothing should have been done before first restarting the bootloader.
Alexandar92zr said:
what can i do to fix this?
Click to expand...
Click to collapse
Flash the factory images from google for the nexus 5. There is a guide in General.
Once your phone boots, flash a recovery
rootSU said:
This was your first mistake
And this the second mistake. Nothing should have been done before first restarting the bootloader.
Flash the factory images from google for the nexus 5. There is a guide in General.
Once your phone boots, flash a recovery
Click to expand...
Click to collapse
can you link me the tutorial how to do that?
Alexandar92zr said:
can you link me the tutorial how to do that?
Click to expand...
Click to collapse
It's in General.
rootSU said:
This was your first mistake
And this the second mistake. Nothing should have been done before first restarting the bootloader.
Flash the factory images from google for the nexus 5. There is a guide in General.
Once your phone boots, flash a recovery
Click to expand...
Click to collapse
rootSU said:
It's in General.
Click to expand...
Click to collapse
sorry im a bin nervous becausemy phone is not working. i ment a tutorial how to flash factory images.
Alexandar92zr said:
sorry im a bin nervous becausemy phone is not working. i ment a tutorial how to flash factory images.
Click to expand...
Click to collapse
Don't be tense, you will tend to do more damage. Calm down m8.
here you go: http://forum.xda-developers.com/showthread.php?t=2513701
vin4yak said:
Don't be tense, you will tend to do more damage. Calm down m8.
here you go: http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
i found a tutorial on yt and now my phone is ok and running now i will flash custom recovery. thanks anyway and thanks a lot @rootSU
Alexandar92zr said:
sorry im a bin nervous becausemy phone is not working. i ment a tutorial how to flash factory images.
Click to expand...
Click to collapse
That was the answer. The tutorial is in the general forum here. ALL our important tutorials are in general
rootSU said:
That was the answer. The tutorial is in the general forum here. ALL our important tutorials are in general
Click to expand...
Click to collapse
now im rooted and everything is working as it should be thanks
os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?
brooklynchildxbc said:
os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?
Click to expand...
Click to collapse
Push a custom rom via adb and flash in recovery or flash stock images via fastboot
acuicultor said:
Push a custom rom via adb and flash in recovery or flash stock images via fastboot
Click to expand...
Click to collapse
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.
brooklynchildxbc said:
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.
Click to expand...
Click to collapse
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?
boober78 said:
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?
Click to expand...
Click to collapse
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
No problem. I'm glad I could help
Sent from my One using Tapatalk
brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
Don't give up.... I was in the same position like you for a couple days....and now is fix by my self..... If you unlock your bootloader try to lock back (fastboot oem lock) now try to flash via fastboot Philz Recovery ( try until is rebooting himself into recovery) .... After that put on a memory stick the new system .... You may need to mount the USB flash drive ..... That's exactly what I have done....Good Luck ...
It is damn near IMPOSSIBLE to actualy, truly "brick" these devices. There are way too many safeguards in place.
Be careful before announcing that you are "bricked". Bootlooping (which is what your device was doing) is not "bricked". As long as you have fastboot, you can always reflash recovery, and then use recovery to reflash your custom ROM (or you can bypass all of that and reflash the factory images from fastboot).
Don't panic, you know more than you think you know. Just don't get freaked out, and read. You'll be fine.
Again...
Three days ago, I wake up and the Nexus 5 doesn't work. I reboot it, and it is stuck on the Google logo screen. When I went in the TWRP recovery, I couldn't find nothing. Everything erased. Today I received my PC (Ram problems with it) and I tried to flash the factory image 4.4.4, but, when writing the bootloader, the cmd says "remote: flash write failure".
It is happened one month ago, and I had to send it to a LG Center because nothing worked (here the post)
There is something that I can do or I have to send it again to a LG Center? And why diid it happened again?
Again it's probably dead eMMC lol
Giolte_ said:
Again...
Three days ago, I wake up and the Nexus 5 doesn't work. I reboot it, and it is stuck on the Google logo screen. When I went in the TWRP recovery, I couldn't find nothing. Everything erased. Today I received my PC (Ram problems with it) and I tried to flash the factory image 4.4.4, but, when writing the bootloader, the cmd says "remote: flash write failure".
It is happened one month ago, and I had to send it to a LG Center because nothing worked (here the post)
There is something that I can do or I have to send it again to a LG Center? And why diid it happened again?
Click to expand...
Click to collapse
Emmc is corrupt you have to send it again. Juat coincedence that it happened again
So I have to send again to LG?
Giolte_ said:
So I have to send again to LG?
Click to expand...
Click to collapse
I just said that -.-
Sorry, I have reloaded the page when only Lethargy had posted
Strange thing... I was following this post, and when I do fastboot boot twrp.img it reboots to twrp and it reboots again, and now there is on my screen the SlimKat boot animation since 5 minutes (SlimKat is the rom that I was running 3 days ago)... what I have to do?
Giolte_ said:
Strange thing... I was following this post, and when I do fastboot boot twrp.img it reboots to twrp and it reboots again, and now there is on my screen the SlimKat boot animation since 5 minutes (SlimKat is the rom that I was running 3 days ago)... what I have to do?
Click to expand...
Click to collapse
Sure looks like you have to rma the device again
Sent from my Nexus 5 using XDA Free mobile app
I can't RMA, I buy it from a retail, in fact I have to reset the temper flag, but when I do this it reboots the system...
Giolte_ said:
I can't RMA, I buy it from a retail, in fact I have to reset the temper flag, but when I do this it reboots the system...
Click to expand...
Click to collapse
Have you tried LG Flashtool?
No, I have not understood how to use it..
I have not understood things like the factory version change, and I don't want to brick the phone... there is anything else that I can do?
The phone is already pretty much bricked imo.. Flash write failure means write access to the eMMC has gone kaappuuuttt!
You need to send the device back to LG as already stated by others. It's very unfortunate that this happened to you twice in such a short period.
Sorry for all these posts, but I don't understand this:
I have locked the bootloader, than I unlock it again. When I navigate to start and "click" it, the device opens TWRP recovery and run a process called "Open Recovery" or something like this.
How is it possible? If I unlock the bootloader why the TWRP recovery is always here?
___
Yes Vin, but how can I send it to LG if I don't reset it?
Giolte_ said:
Sorry for all these posts, but I don't understand this:
I have locked the bootloader, than I unlock it again. When I navigate to start and "click" it, the device opens TWRP recovery and run a process called "Open Recovery" or something like this.
How is it possible? If I unlock the bootloader why the TWRP recovery is always here?
___
Yes Vin, but how can I send it to LG if I don't reset it?
Click to expand...
Click to collapse
Locking the bootloading doesn't wipe your recovery. You will need to flash the stock recovery via fastboot to replace twrp. However, I doubt whether you will be able to replace it since the eMMC has gone bad. Anyways, there;'s nothing to loose.. Give it a shot.
I only have to flash the stock recovery in the google factory image 4.4.4 or I have to do particular passages?
Giolte_ said:
I only have to flash the stock recovery in the google factory image 4.4.4 or I have to do particular passages?
Click to expand...
Click to collapse
1. Unlock the bootloader (if it's locked).
2. Flash stock recovery.img via fastboot.
3. Reboot and use command "fastboot boot twrp.img" //This will boot your device into twrp.
4. Sideload this file in twrp: http://forum.xda-developers.com/attachment.php?attachmentid=2467503&d=1387666907
The above file will reset the tamper flag and lock the bootloader!
When I extract the files from the zip, the boot, system and recovery are dated 12/12/2008... is this normal?
Yes..
Ok, last questions... if I'll flash the zip, I have to use in sideload this: "adb sideload cwm-Nexus.BootUnlocker.zip"?
And why, there is "cwm" in the name? Sorry for all these questions, but I don't want to burn my last hope...
Hi, I really need your assistance for my pixel. I locked my bootloader after unrooting my phone. This process totally bricked my phone(I can't even get to the booting process of the phone) (I get a message saying that my phone is corrupt). I am able to gain access to my fastboot. So I was wondering if there was a way for me to flash the factory image to my phone and get it to work again. Please of there is anything you can do, please help me.
Its_joey_k23 said:
Hi, I really need your assistance for my pixel. I locked my bootloader after unrooting my phone. This process totally bricked my phone(I can't even get to the booting process of the phone) (I get a message saying that my phone is corrupt). I am able to gain access to my fastboot. So I was wondering if there was a way for me to flash the factory image to my phone and get it to work again. Please of there is anything you can do, please help me.
Click to expand...
Click to collapse
I'm really afraid there's nothing you can do. Before relocking the bootloader, you must go back to an approved stock firmware. (See, when you rooted it, you changed it.)
quangtran1 said:
I'm really afraid there's nothing you can do. Before relocking the bootloader, you must go back to an approved stock firmware. (See, when you rooted it, you changed it.)
Click to expand...
Click to collapse
I unrooted my device, so then after I can lock my bootloader. I'm just wondering if that's how I was supposed to do it.
If you have downloaded the full image from Google servers, try if you can fastboot using the boot image from the full image. It that boots your phone, you could try enabling unlock, get into fastboot to unlock for flashing. You can then flash the full image from unlocked fastboot
hackworks said:
If you have downloaded the full image from Google servers, try if you can fastboot using the boot image from the full image. It that boots your phone, you could try enabling unlock, get into fastboot to unlock for flashing. You can then flash the full image from unlocked fastboot
Click to expand...
Click to collapse
Is there any way you could lead my step by step. I don't want to screw up my phone even more. + I'm new to the community and don't know much.
You can use the fastboot continue command.
This will boot up your phone normally and then you will be able to go to developer settings and enable oem unlocking again.
After this you will be able to unlock from fastboot again.
http://forum.xda-developers.com/pixel/help/accomplished-hardbricked-pixel-d-t3516717
Its_joey_k23 said:
Is there any way you could lead my step by step. I don't want to screw up my phone even more. + I'm new to the community and don't know much.
Click to expand...
Click to collapse
If you can put your phone in fastboot mode, you're not bricked yet.
hackworks said:
If you have downloaded the full image from Google servers, try if you can fastboot using the boot image from the full image. It that boots your phone, you could try enabling unlock, get into fastboot to unlock for flashing. You can then flash the full image from unlocked fastboot
Click to expand...
Click to collapse
You saved my life! Thank you.