Some back story. My N5 was stock/rooted, with stock recovery. I had installed the beta Xposed framework, using this post as a guide. Following the install, during the reboot, my phone never restarted. Since then it has not been able to turn on.
Things I have tried:
I have done method 1 & 2 of this guide
I am able to lock and unlock the bootloader, it is currently locked.
I have tried the command fastboot -w
I am unable to perform a factory reset, it hangs at /data
If there is any ideas as to what I should do next, please don't hesitate to let me know.
If I am able to get the Tamper Flag reset, then my plan is to look into the RMA option.
Also, I have been following this thread for info.
jimburke57 said:
Some back story. My N5 was stock/rooted, with stock recovery. I had installed the beta Xposed framework, using this post as a guide. Following the install, during the reboot, my phone never restarted. Since then it has not been able to turn on.
Things I have tried:
I have done method 1 & 2 of this guide
I am able to lock and unlock the bootloader, it is currently locked.
I have tried the command fastboot -w
I am unable to perform a factory reset, it hangs at /data
If there is any ideas as to what I should do next, please don't hesitate to let me know.
If I am able to get the Tamper Flag reset, then my plan is to look into the RMA option.
Also, I have been following this thread for info.
Click to expand...
Click to collapse
when you unlock the phone, and reboot the bootloader, does it stay locked or is it unlocked?
Zepius said:
when you unlock the phone, and reboot the bootloader, does it stay locked or is it unlocked?
Click to expand...
Click to collapse
So earlier when i did this, the phone would freeze. Now it went through with it, and is now showing the animated android images, with a moving bar at the bottom. It has been there for about 4 minutes now.
jimburke57 said:
So earlier when i did this, the phone would freeze. Now it went through with it, and is now showing the animated android images, with a moving bar at the bottom. It has been there for about 4 minutes now.
Click to expand...
Click to collapse
this still does not answer my question.
it sounds like your phone is not dead however. please follow the return to stock thread in the general forum and you should be ok.
Zepius said:
this still does not answer my question.
it sounds like your phone is not dead however. please follow the return to stock thread in the general forum and you should be ok.
Click to expand...
Click to collapse
I have followed it already. The images on the first post are my result.
It is showing as unlocked at the booloader and on fastboot oem device-info.
follow the 2nd post, not the 2nd method in this thread and tell us the results.
http://forum.xda-developers.com/showthread.php?t=2513701
Zepius said:
follow the 2nd post, not the 2nd method in this thread and tell us the results.
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
Same thing as before. All of the erase commands get processed, but when it gets the the system.img it fails to write it.
I think you've done her in. Can you get into recovery? You might be able to push the tamper zip and then run it in recovery.
jd1639 said:
I think you've done her in. Can you get into recovery? You might be able to push the tamper zip and then run it in recovery.
Click to expand...
Click to collapse
I am able to access recovery. This is exactly what I am trying to do at the moment, but now I cannot adb sideload the zip. For some reason the N5 is not being recognized by windows.
jimburke57 said:
I am able to access recovery. This is exactly what I am trying to do at the moment, but now I cannot adb sideload the zip. For some reason the N5 is not being recognized by windows.
Click to expand...
Click to collapse
Use Galaxy Nexus drivers, and make sure you have updated the SDK for the latest adb.
orangekid said:
Use Galaxy Nexus drivers, and make sure you have updated the SDK for the latest adb.
Click to expand...
Click to collapse
Are you talking about these drivers?
jimburke57 said:
Are you talking about these drivers?
Click to expand...
Click to collapse
No, I have had success getting the Nexus 5 working on ADB with the Samsung Galaxy Nexus drivers. Don't ask me why, but it works for me.
orangekid said:
No, I have had success getting the Nexus 5 working on ADB with the Samsung Galaxy Nexus drivers. Don't ask me why, but it works for me.
Click to expand...
Click to collapse
So an update, I am able to sideload the zip in recovery, however, during the install, it fails.
jimburke57 said:
So an update, I am able to sideload the zip in recovery, however, during the install, it fails.
Click to expand...
Click to collapse
Have you tried flashing stock kitkat (from google) via fastboot?
orangekid said:
Have you tried flashing stock kitkat (from google) via fastboot?
Click to expand...
Click to collapse
yes, many times
So this is just a shot in the dark, but the fastboot command screenshot you posted, you had the command "fastboot flash bootloader."
I haven't read the articles you're using, but is there a reason you're flashing a bootloader after unlocking it? Wouldn't that just lock the bootloader again?
I'd start fastboot oem unlock, fastboot flash recovery, and then adb sideload the .zip you are using once you're in recovery.
Good luck.
pantlessjim said:
So this is just a shot in the dark, but the fastboot command screenshot you posted, you had the command "fastboot flash bootloader."
I haven't read the articles you're using, but is there a reason you're flashing a bootloader after unlocking it? Wouldn't that just lock the bootloader again?
I'd start fastboot oem unlock, fastboot flash recovery, and then adb sideload the .zip you are using once you're in recovery.
Good luck.
Click to expand...
Click to collapse
I am just following the guide for How to return to stock. But to answer your question, no it does not re-lock the bootloader.
Here is some additional information. When I perform a factory reset in recovery it freezes while formatting /data. And when flashing the stock images, I am able to flash everything successfully except for the system.img
jimburke57 said:
I am just following the guide for How to return to stock. But to answer your question, no it does not re-lock the bootloader.
Click to expand...
Click to collapse
Have you tried just dirty flashing stock / rooted thru recovery?
edit: or restoring a backup?
Related
I'm returning my Nexus 5 for replacement and I was going to do the following:
- boot into Android and run BootUnlocker to reset Tamper flag
- Go to bootloader, use fastboot to flash factory images
- fastboot oem lock
Would this put the phone in factory state, without triggering tamper flag? I'm worried about step 2... would flashing factory images trip the tamper flag?
You could read the guide in general (sticky thread) which answers all these questions
Sent from my Nexus 5 using Tapatalk
rootSU said:
You could read the guide in general (sticky thread) which answers all these questions
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, however the guide seems to use a separate flash step to reset tamper, I was specifically interested in using the app instead if possible.
Android.Addiction said:
Thanks, however the guide seems to use a separate flash step to reset tamper, I was specifically interested in using the app instead if possible.
Click to expand...
Click to collapse
Your steps look good to me. There are a couple ways to flash the stock firmware, make sure your userdata gets wiped. You could also go into stock recovery when you're finished and factory reset.
Aerowinder said:
Your steps look good to me. There are a couple ways to flash the stock firmware, make sure your userdata gets wiped. You could also go into stock recovery when you're finished and factory reset.
Click to expand...
Click to collapse
So far I've just been running the steps inside ./flash-all.sh manually:
Code:
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-hammerhead-kot49h.zip
I can add this extra step before the above commands if needed:
fastboot erase userdata
Thanks man!
Android.Addiction said:
I'm returning my Nexus 5 for replacement and I was going to do the following:
- boot into Android and run BootUnlocker to reset Tamper flag
- Go to bootloader, use fastboot to flash factory images
- fastboot oem lock
Would this put the phone in factory state, without triggering tamper flag? I'm worried about step 2... would flashing factory images trip the tamper flag?
Click to expand...
Click to collapse
for the record: don't do this! it DANGEROUS to oem-lock without a working stock recovery corresponding to your bootloader version! its not mentioned often, but fastboot oem unlock uses the stock recovery to do the wipe plus unlock. this means: no stock recovery, no unlock!
yes, you can manually unlock THIS DEVICE because we know how to, IF YOU CAN BOOT AND BE ROOT. if you cant get root from android or recovery (say, recovery doesnt boot and android is not rooted) then you CANT UNLOCK EVER AGAIN.
Lanchon said:
for the record: don't do this! it DANGEROUS to oem-lock without a working stock recovery corresponding to your bootloader version! its not mentioned often, but fastboot oem unlock uses the stock recovery to do the wipe plus unlock. this means: no stock recovery, no unlock!
yes, you can manually unlock THIS DEVICE because we know how to, IF YOU CAN BOOT AND BE ROOT. if you cant get root from android or recovery (say, recovery doesnt boot and android is not rooted) then you CANT UNLOCK EVER AGAIN.
Click to expand...
Click to collapse
It's not the same as the OPO, but I'd agree that it's best to get to stock first then relock using the script as opposed to an app
EddyOS said:
It's not the same as the OPO, but I'd agree that it's best to get to stock first then relock using the script as opposed to an app
Click to expand...
Click to collapse
The steps the last guy quoted did flash factory images before locking.
rootSU said:
The steps the last guy quoted did flash factory images before locking.
Click to expand...
Click to collapse
Yeah, but the guy I was quoting was on about the issues present in the OPO where there are issues with the bootloader getting stuck locked if not using a stock recovery
rootSU said:
The steps the last guy quoted did flash factory images before locking.
Click to expand...
Click to collapse
lol yes he did, sorry! i thought he run the toggle-lock/reset-tamper script. my bad.
EddyOS said:
Yeah, but the guy I was quoting was on about the issues present in the OPO where there are issues with the bootloader getting stuck locked if not using a stock recovery
Click to expand...
Click to collapse
Sorry, to clarify -
Poster 1 - Outlines correct steps
Poster 2 - Don't do this this it's dangerous
You - yeah but its not dangerous. You're thinking of opo
Me - Actually the steps highlighted originally are correct and would work even on Opo!
rootSU said:
Sorry, to clarify -
Poster 1 - Outlines correct steps
Poster 2 - Don't do this this it's dangerous
You - yeah but its not dangerous. You're thinking of opo
Me - Actually the steps highlighted originally are correct and would work even on Opo!
Click to expand...
Click to collapse
In a nutshell, although the guide in my signature covers all bases with the OPO as I wrote it when I had one!
EddyOS said:
It's not the same as the OPO, but I'd agree that it's best to get to stock first then relock using the script as opposed to an app
Click to expand...
Click to collapse
what makes you think its not the same? any source to that info? i have a nexus 5 with me here, and i remember that fastboot oem unlock ran something that looked liked a recovery. do you mean to tell me that the bootloader has its own independent recovery image built into part of its partition to boot to and do the unlocking? because otherwise i dont see how it would do it. please explain.
Android.Addiction said:
I'm returning my Nexus 5 for replacement and I was going to do the following:
- boot into Android and run BootUnlocker to reset Tamper flag
- Go to bootloader, use fastboot to flash factory images
- fastboot oem lock
Would this put the phone in factory state, without triggering tamper flag? I'm worried about step 2... would flashing factory images trip the tamper flag?
Click to expand...
Click to collapse
Just reflash a factory image in fastboot with the`flash-all`command in cmd and relock the bootloader afterwards and its completely stock. Nexus 5 doesn`t have a tamper flag afaik anyway.
Lanchon said:
what makes you think its not the same? any source to that info? i have a nexus 5 with me here, and i remember that fastboot oem unlock ran something that looked liked a recovery. do you mean to tell me that the bootloader has its own independent recovery image built into part of its partition to boot to and do the unlocking? because otherwise i dont see how it would do it. please explain.
Click to expand...
Click to collapse
What I mean is there's an issue with the OPO where you relock the bootloader without the stock recovery and you then can't unlock it again. It's not been documented that the same fault happens in the Nexus range, but if the OP follows the guides available on here it'll all be OK
gee2012 said:
Just reflash a factory image in fastboot with the`flash-all`command in cmd and relock the bootloader afterwards and its completely stock. Nexus 5 doesn`t have a tamper flag afaik anyway.
Click to expand...
Click to collapse
all N5 have tamper flag. it was introduced mid life of the N4 via a bootloader upgrade. i had an N4 at the time and thought that move was sh*tty.
gee2012 said:
Just reflash a factory image in fastboot with the`flash-all`command in cmd and relock the bootloader afterwards and its completely stock. Nexus 5 doesn`t have a tamper flag afaik anyway.
Click to expand...
Click to collapse
Yes it does
EddyOS said:
Yes it does
Click to expand...
Click to collapse
Where can you see it? Not in the bootloader menu as i see. So its reset tampered flag (BootUnlocker), flash the factory image and afterwards lock the bootloader in fastbooot?
EddyOS said:
What I mean is there's an issue with the OPO where you relock the bootloader without the stock recovery and you then can't unlock it again. It's not been documented that the same fault happens in the Nexus range, but if the OP follows the guides available on here it'll all be OK
Click to expand...
Click to collapse
yes, we've established the steps are ok and it was my misreading.
but regarding my warning about locking with non working stock recovery: its not been documented, but im sure it happens all the same! the bootloader uses a recovery (presumably the one recovery we know and not an image embedded in the bootloader itself) to wipe data. and it would be a mistake to unlock before wiping. so the bootloader does the wipe-then-unlock by delegating everything to the recovery. no recovery, no unlock.
gee2012 said:
Where can you see it? Not in the bootloader menu as i see. So its reset tampered flag (BootUnlocker), flash the factory image and afterwards lock the bootloader in fastbooot?
Click to expand...
Click to collapse
When connected in fastboot, type
fastboot oem device-info
And it'll show device tampered true or false
To get it all back to stock, flash the factory image completely then boot TWRP (don't flash it) and run the bootunlocker script found in the Nexus 5 unroot thread
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a bootloader and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt bootloader, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Than
Click to expand...
Click to collapse
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a bootloader and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt bootloader, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Than
Click to expand...
Click to collapse
the exclamation point is the stock recovery. once you take in an ota, it removes both root and your custom recovery. to get your custom recovery back so that you can flash a bootloader(and the supersu root binaries). you can flash a custom recovery while youre in your bootloader via fastboot on your desktop.
GUGUITOMTG4 said:
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Yeah just realised that. Sorry its my first post
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
Click to expand...
Click to collapse
why don't you try twrp maybe you can flash twrp then remove the file then go back to cwm
Sent from my Nexus 5 using Tapatalk
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
Click to expand...
Click to collapse
just read this again..when you are flash a custom recovery, and it still goes to the exclamation point, it means that you arent flashing the custom recovery right. its.. fastboot flash recovery recoveryname.img
GUGUITOMTG4 said:
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Thats what I was trying to explain. I tried flashing custom recovery as per instructions but nothing happens. From what I am reading this is because of the reboot-from-recovery.p file which needs to be deleted BUT I cannot do this without root!
luppas said:
Thats what I was trying to explain. I tried flashing custom recovery as per instructions but nothing happens. From what I am reading this is because of the reboot-from-recovery.p file which needs to be deleted BUT I cannot do this without root!
Click to expand...
Click to collapse
na, you dont need to delete that to flash a custom recovery(i never have, in my 6 years with android, and all my devices). is fastboot seeing your device? kkdo you see fastboot going through the process of flashing a recovery? if you are typing it right, and fastboot sees your device, you would have flashed a custom recovery. when you connect to fastboot, type.. fastboot devices. if it sees your device, its id number will be shown.
simms22 said:
just read this again..when you are flash a custom recovery, and it still goes to the exclamation point, it means that you arent flashing the custom recovery right. its.. fastboot flash recovery recoveryname.img
Click to expand...
Click to collapse
C:\Users\user\Downloads\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
I have it right mate. But nothing seems to be happening. Maybe drivers issue? When I do adb version I get the version so I assumed that means its working
luppas said:
C:\Users\user\Downloads\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
I have it right mate. But nothing seems to be happening. Maybe drivers issue? When I do adb version I get the version so I assumed that means its working
Click to expand...
Click to collapse
adb version and fastboot devices is different. adb is not fastboot and you can not use adb as fastboot. fastboot is fastboot.
simms22 said:
na, you dont need to delete that to flash a custom recovery(i never have, in my 6 years with android, and all my devices). is fastboot seeing your device? kkdo you see fastboot going through the process of flashing a recovery? if you are typing it right, and fastboot sees your device, you would have flashed a custom recovery. when you connect to fastboot, type.. fastboot devices. if it sees your device, its id number will be shown.
Click to expand...
Click to collapse
Yeah you were right. Driver issue. fastboot devices showed nothing. Reinstalled drivers and looks to be good now.
Thanks guys sorry for the post in wrong area
luppas said:
Yeah you were right. Driver issue. fastboot devices showed nothing. Reinstalled drivers and looks to be good now.
Thanks guys sorry for the post in wrong area
Click to expand...
Click to collapse
glad you got it
Hi guys,
I run rooted unlocked Nexus 5 with CM11. I wanted to update the ROM but it failed - I read a bit and found out that it is due to old bootloader version. I would like to update it but I'm not a friend with ADB and stuff.... It would be great to use the most easiest way. I got OTA update notification but have no idea what it does - will it unroot the phone? will I lose CM11 ROM? Just trying to figure out what backups and steps shall I do to update my ROM. How shall I continue from here?
Thanks a bunch!
devcager said:
Hi guys,
I run rooted unlocked Nexus 5 with CM11. I wanted to update the ROM but it failed - I read a bit and found out that it is due to old bootloader version. I would like to update it but I'm not a friend with ADB and stuff.... It would be great to use the most easiest way. I got OTA update notification but have no idea what it does - will it unroot the phone? will I lose CM11 ROM? Just trying to figure out what backups and steps shall I do to update my ROM. How shall I continue from here?
Thanks a bunch!
Click to expand...
Click to collapse
Attempting to take the OTA will fail.
Download the factory image and extract bootloader-hammerhead-hhz11k.img
Boot your device into bootloader:
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
You have a custom recovery installed, right? Flash the bootloader zip via recovery. However, you need to get familiar with adb/fastboot as you're gonna need them if you ever find yourself in a tight situation to fix your device.
Open the "must read" thread linked in my signature and find the thread which has all the info about adb and fastboot.
vin4yak said:
You have a custom recovery installed, right? Flash the bootloader zip via recovery. However, you need to get familiar with adb/fastboot as you're gonna need them if you ever find yourself in a tight situation to fix your device.
Open the "must read" thread linked in my signature and find the thread which has all the info about adb and fastboot.
Click to expand...
Click to collapse
Thank you! I get it about ADB, I had to solve one my problem in the past via ADB. Anyway, I just need to find the 4.4.4 bootloader in ZIP (or probalby .img will work too?) and flash it? That's it? Does it wipe my phone or something?
You just need to flash the IMG via fastboot, no wiping required!
EddyOS said:
You just need to flash the IMG via fastboot, no wiping required!
Click to expand...
Click to collapse
Alright. One more thing. Is it possible to convert the IMG file I have into zip to be able to flash it in TWRP?
EDIT: I found that Nexus Toolbox for my 5 has the option to flash the bootloader image so I will try this variant.
devcager said:
Alright. One more thing. Is it possible to convert the IMG file I have into zip to be able to flash it in TWRP?
EDIT: I found that Nexus Toolbox for my 5 has the option to flash the bootloader image so I will try this variant.
Click to expand...
Click to collapse
You don't need to. Just boot into fastboot, connect to PC, fastboot flash bootloader name_of_file.img, reboot, done
it's easy you must become familiar with fastboot and add the second you aren't it will come back to haunt you
Sent from my Nexus 5 using Tapatalk
devcager said:
Alright. One more thing. Is it possible to convert the IMG file I have into zip to be able to flash it in TWRP?
EDIT: I found that Nexus Toolbox for my 5 has the option to flash the bootloader image so I will try this variant.
Click to expand...
Click to collapse
so you learned nothing. awesome.
Zepius said:
so you learned nothing. awesome.
Click to expand...
Click to collapse
Brick waiting to happen.
Add to ignore list
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
rootSU said:
Brick waiting to happen.
Add to ignore list
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
Click to expand...
Click to collapse
I'm still waiting for someone to make a thread saying their device is "bricked because flashed fastboot to adb using bootloader while in recovery with x toolkit"
Hey,
i just re-rooted my One after updating to 38r some days ago, and as it booted up, i got the "audiofx has stopped" bug and the "CM Lockscreen has stopped" bug at the same time. i tried to reset with twrp, reflash the rom and whatnot. I also cant flash roms with toolkits as i can not unlock my Bootloader. Today i finally managed to install a modified 38r via USB Otg after some other rom installations failed (also with USB Otg). I'm all like "Hell Yeah, fvck yeah OnePlus support!" (I wrote to them some days ago but they have not replied). I euphorically booted up my device and waited until the cyanogenmod logo pops up. i waited all the time. And its in a Bootloop now. I tried resetting my device and reflashing the ROM but none works. Can anyone help me please?
Sorry for the typos, i got not much time right now so i had to type fast.
thanks in advance
Have you tried a full wipe and clean flash of 38R?
Transmitted via Bacon
as i can not unlock my Bootloader
Click to expand...
Click to collapse
Could you please elaborate on this? You obviously already have a custom (TWRP) recovery, so you either flashed when sideloading was still possible or your bootloader is unlocked.
also cant flash roms with toolkits
Click to expand...
Click to collapse
A word of advise about using toolkits: don't. _Especially_ not if your phone has already issues as toolkits more often than not run the commands without checking (error) outputs. This has led to disastrous results for some people in the past so be careful!
I can recommend trying to re-flash the 38R via Fastboot after formatting the relevant partitions (cache, system ) to make sure you start from scratch.
d4fseeker said:
Could you please elaborate on this? You obviously already have a custom (TWRP) recovery, so you either flashed when sideloading was still possible or your bootloader is unlocked.
A word of advise about using toolkits: don't. _Especially_ not if your phone has already issues as toolkits more often than not run the commands without checking (error) outputs. This has led to disastrous results for some people in the past so be careful!
I can recommend trying to re-flash the 38R via Fastboot after formatting the relevant partitions (cache, system ) to make sure you start from scratch.
Click to expand...
Click to collapse
He can't flash via fastboot is his bootloader is locked. He'll have to just flash the recovery flashable version via TWRP.
Transmitted via Bacon
timmaaa said:
He can't flash via fastboot is his bootloader is locked. He'll have to just flash the recovery flashable version via TWRP.
Click to expand...
Click to collapse
That's why I asked for elaboration on his bootloader state and fastboot issues. Flashing with fastboot close to _always_ works unless the bootloader is borked which does not seem to be the case as he can at least start the recovery environment. "Does not work" is a rather broad subject from "I don't know how to do it" over "I don't get it working" up to "it shows an error".
d4fseeker said:
That's why I asked for elaboration on his bootloader state and fastboot issues. Flashing with fastboot close to _always_ works unless the bootloader is borked which does not seem to be the case as he can at least start the recovery environment. "Does not work" is a rather broad subject from "I don't know how to do it" over "I don't get it working" up to "it shows an error".
Click to expand...
Click to collapse
Fair enough, although for someone who's inexperienced I think using the flashable version will be an easier and quicker solution.
Transmitted via Bacon
timmaaa said:
Have you tried a full wipe and clean flash of 38R?
Transmitted via Bacon
Click to expand...
Click to collapse
d4fseeker said:
Could you please elaborate on this? You obviously already have a custom (TWRP) recovery, so you either flashed when sideloading was still possible or your bootloader is unlocked.
A word of advise about using toolkits: don't. _Especially_ not if your phone has already issues as toolkits more often than not run the commands without checking (error) outputs. This has led to disastrous results for some people in the past so be careful!
I can recommend trying to re-flash the 38R via Fastboot after formatting the relevant partitions (cache, system ) to make sure you start from scratch.
Click to expand...
Click to collapse
My bootloader is locked, as said. And i use toolkits because i experienced some bugs with the commands on Win8.1.
try...
TWRP.. Terminal Line..
make_ext4fs /dev/block/mmcblk0p15
Crime_Monkey said:
My bootloader is locked, as said. And i use toolkits because i experienced some bugs with the commands on Win8.1.
Click to expand...
Click to collapse
I can't help you if you don't even provide answers to specific questions you've been asked such as how TWRP got on the phone and why you "cannot" unlock your bootloader.
Do please note however that toolkits are not magical software, they just provide a nice clickable wrapper around the same low-level drivers and software such as adb and fastboot. If either of those have issues, so will the toolkits. And that's exactly where my word of caution kicks in; they often don't notice something went wrong. Worst-case you end up with a dead phone which I'm trying to avoid.
d4fseeker said:
I can't help you if you don't even provide answers to specific questions you've been asked such as how TWRP got on the phone and why you "cannot" unlock your bootloader.
Do please note however that toolkits are not magical software, they just provide a nice clickable wrapper around the same low-level drivers and software such as adb and fastboot. If either of those have issues, so will the toolkits. And that's exactly where my word of caution kicks in; they often don't notice something went wrong. Worst-case you end up with a dead phone which I'm trying to avoid.
Click to expand...
Click to collapse
I installed twrp with the toolkit by @manudroid19 when my phone was still functionable.
And the toolkit says that my bootloader is locked and i cannot unlock it. Every time i try to unlock it with the toolkit when in fastboot mode, the phone just boots up to twrp.
Have you tried the instructions in this thread:
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
r0ni3 said:
try...
TWRP.. Terminal Line..
make_ext4fs /dev/block/mmcblk0p15
Click to expand...
Click to collapse
I can not find the folder, with and without an OS installed.
Crime_Monkey said:
I can not find the folder, with and without an OS installed.
Click to expand...
Click to collapse
no folder ..
you just have to write that command
r0ni3 said:
no folder ..
you just have to write that command
Click to expand...
Click to collapse
I can't find this option in twrp either.
Crime_Monkey said:
I can't find this option in twrp either.
Click to expand...
Click to collapse
twrp version?
Advanced -> Terminal Command -> Click on SELECT
and write
make_ext4fs /dev/block/mmcblk0p15
r0ni3 said:
twrp version?
Advanced -> Terminal Command -> Click on SELECT
and write
make_ext4fs /dev/block/mmcblk0p15
Click to expand...
Click to collapse
I am on 2.8.0.1., after executing the command i tried to install the stock 38r update, failed.
Crime_Monkey said:
I am on 2.8.0.1., after executing the command i tried to install the stock 38r update, failed.
Click to expand...
Click to collapse
installa a nightly...
and gapps
you can adb push roms in twrp, so you dont have to resort to otg.
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Edit: CHECK THE COMMENTS FOR SOLUTION
AlexCoetzee said:
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Click to expand...
Click to collapse
Try downloading the stock image and installing that from fastboot. If you are on a Verizon one and on 7.1.1 you are out of luck for root if you bootloader isn't unlocked.
AlexCoetzee said:
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Click to expand...
Click to collapse
Ok, stop freaking, this is very fixable. Assuming you have the Google version, or the Verizon version unlocked.
Short answer, we are going to get it into fastboot mode and we are going to flash you back to stock and probably save your data.
First, we need to make sure you have the correct version of Fastboot/ADB. It must be from GOOGLE.
https://developer.android.com/studio/releases/platform-tools.html
Unzip that onto a spot on your desktop.
Then go here and download the latest image for the Pixel. I am assuming you are in the US, get 7.1.1 (NOF26V, Feb 2017) for the Pixel.
https://developers.google.com/android/images#sailfish
Unzip that into a the Platform folder you made above with the fastboot tools. When you are all done it should look like the picture below. The highlighted items are the items that came from the Factory Image you extracted in step two. Everything else is from the platform tools.
Now RIGHT click 'flash-all.bat' and edit it. Near the end...look for the -w and take it out and save it. Removing that is what is going to save your data.
Power down your phone, restart it in bootloader mode. Power and Vol Down. Connect it to your computer and then double click 'flash-all.bat'.
That will take you back to stock unlocked and all your data and settings will be there.
Get past that and let us know. Then we will get you properly rooted. Yea, you used the wrong root process.
I love you <3
Thank you so much. I stupidly was trying to flash a file that wasn't an image file! I really appreciate your help man I don't know what I'd do if it wasn't for you.
AlexCoetzee said:
Thank you so much. I stupidly was trying to flash a file that wasn't an image file! I really appreciate your help man I don't know what I'd do if it wasn't for you.
Click to expand...
Click to collapse
You are most welcome. Do you need help rooting now?
TonikJDK said:
You are most welcome. Do you need help rooting now?
Click to expand...
Click to collapse
No thank you! I figured that out pretty quickly with TWRP and I am happily rooted now Quite a different process after jailbreaking iOS for 8 years. Thanks for your help!
Misterxtc said:
Try downloading the stock image and installing that from fastboot. If you are on a Verizon one and on 7.1.1 you are out of luck for root if you bootloader isn't unlocked.
Click to expand...
Click to collapse
Glad to see you are still out there @Misterxtc
Seems like you've been a mainstay almost everywhere I've been and I've relied on your threads and guides for a long time.
Tulsadiver said:
Glad to see you are still out there @Misterxtc
Seems like you've been a mainstay almost everywhere I've been and I've relied on your threads and guides for a long time.
Click to expand...
Click to collapse
Good to see you here too. It feels great to be free of TouchWiz!!
Misterxtc said:
Good to see you here too. It feels great to be free of TouchWiz!!
Click to expand...
Click to collapse
And how. I'm done with Samsung.
Thanks for the straightforward instructions!
---------- Post added at 11:45 AM ---------- Previous post was at 11:38 AM ----------
TonikJDK said:
You are most welcome. Do you need help rooting now?
Click to expand...
Click to collapse
Do you have a link to rooting with TWRP? I've found several rooting posts but most talk about rooting via fastboot.
Thanks!
stpbby said:
Thanks for the straightforward instructions!
---------- Post added at 11:45 AM ---------- Previous post was at 11:38 AM ----------
Do you have a link to rooting with TWRP? I've found several rooting posts but most talk about rooting via fastboot.
Thanks!
Click to expand...
Click to collapse
No link handy, but here is how I do it. And yes, it is via fastboot, only way I know of at this point.
Download 2.7.9 SR3 SuperUser and copy it to your phone.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Download TWRP RC1 and copy it to your fastboot folder.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Using other versions than above will bootloop you. Reboot the phone into bootloader mode. Power and Vol down.
fastboot BOOT twrpFilename.img Where twrpfilename.img is the name of the TWRP file you just downloaded. Note is says boot in the command, not flash.
That will boot the phone into TWRP. Select Install and install the SU zip you copied to the phone above. And reboot the phone, done.
Thanks! That worked.
I need help with unlocking bootloader and rooting phone
TonikJDK said:
No link handy, but here is how I do it. And yes, it is via fastboot, only way I know of at this point.
Download 2.7.9 SR3 SuperUser and copy it to your phone.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Download TWRP RC1 and copy it to your fastboot folder.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Using other versions than above will bootloop you. Reboot the phone into bootloader mode. Power and Vol down.
fastboot BOOT twrpFilename.img Where twrpfilename.img is the name of the TWRP file you just downloaded. Note is says boot in the command, not flash.
That will boot the phone into TWRP. Select Install and install the SU zip you copied to the phone above. And reboot the phone, done.
Click to expand...
Click to collapse
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
gandhi98 said:
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
Click to expand...
Click to collapse
If your on Verizon, no, you can't unlock the bootloader
gandhi98 said:
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
Click to expand...
Click to collapse
If it is a Verizon phone, no you can't unlock it. If it is a Google phone to unlock...below is a decent link on how to. Except use the ADB Fastboot tools I link to in the third post of this thread.
https://android.gadgethacks.com/how-to/unlock-bootloader-your-google-pixel-pixel-xl-0174627/
And be aware, when you unlock it...it will wipe all the data on your phone.
My pixel (stock, not rooted) is boot looping after the May OTA updates. Google support says to take it back to the store as it's still under warranty. Would the above fix work for my phone? Is it worth it, or should I just get a new one? This is already my second pixel as the first one died abruptly after 3 months.
moeREM said:
My pixel (stock, not rooted) is boot looping after the May OTA updates. Google support says to take it back to the store as it's still under warranty. Would the above fix work for my phone? Is it worth it, or should I just get a new one? This is already my second pixel as the first one died abruptly after 3 months.
Click to expand...
Click to collapse
Is the bootloader unlocked? If so I would certainly try flashing stock first. It can't hurt, and moments ago my Nexus 6 that I keep for backup was doing the same thing after the OTA. I just reflashed stock and it is fine now.
TonikJDK said:
Is the bootloader unlocked? If so I would certainly try flashing stock first. It can't hurt, and moments ago my Nexus 6 that I keep for backup was doing the same thing after the OTA. I just reflashed stock and it is fine now.
Click to expand...
Click to collapse
I think so, but am not 100% sure. Was bought unlocked from a retail shop. (Sorry, am a bit of a newb!)
So please let me understand
I am on 7.1.2 april (N2G47E), and if I want to update to may N2G47O the steps are:
- sideload ota
- flash new bootloader from may factory image
- twrp RC1 and supersu 2.79 sr3
Does this work or do I have to make something different?
TENN3R said:
So please let me understand
I am on 7.1.2 april (N2G47E), and if I want to update to may N2G47O the steps are:
- sideload ota
- flash new bootloader from may factory image
- twrp RC1 and supersu 2.79 sr3
Does this work or do I have to make something different?
Click to expand...
Click to collapse
I'm having bootloops at the initial white google logo screen with SR3-SuperSU-v2.79-SR3-20170114223742.zip flash method on 7.1.2-May
Re: https://theunlockr.com/2017/02/01/root-google-pixel-pixel-xl/2/