Related
Hey all, sorry if this seems like other questions being posted, but I can not get my phone to work even after attempting the other fixes posted on the forums. I rooted my phone and was running the stock rom that came preloaded with it. I attempted to install CM10 through Rom Manager to no success, so I then tried to manually flash it as well as Gapps. My phone initially got stuck at the CM10 bootloader, but i could still go into CWM Recovery 5.8.3.1. After trying to get the rom to work more, it seems as if all I can access is CWM Recovery and nothing else. My phone wont even boot into the bootloader anymore and all i have access to is CWM Recovery.
I am not the most tech savvy individual when it comes to this since it has been ages since i tinkered with roms, but I would really like to fix this. So heres the facts since my post is so long (sorry!):
-Phone WILL NOT go into bootloader
-Can ONLY ACCESS ClockworkMod Recovery (5.8.3.1)
-SD Card wont mount (I get error "E:Unable to open ums lunfile (No such file or directory)")
I really just want to go back to stock and root again from scratch to reduce any errors like this from occurring in the future and ANY help would be appreciated because I am totally lost and without a phone now. To make things even more difficult, I only have access to a Mac running Lion....although i do have Windows 8 through the use of a bootcamp program, so I CAN run windows programs. Thank you all for any information you may have!
Do you have NANDROID backup,if yes do NANDROID restore and see what happens
Sent from my HTC One S using xda app-developers app
luxandroid said:
Do you have NANDROID backup,if yes do NANDROID restore and see what happens
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I do NOT have a nandroid backup. I dont even have access to my SD Card since my phone wont recognize it. I dont know where to even start in terms of fixing this. Any additional information anyone needs who thinks they can help me can be provided.
Porgress (Sort of)
I can now access my bootloader if this helps with anyone answering my issue! As I said before, any additional information from me about my phone that can help can and will be provided...just ask if you think you may be able to help!
fragkiller1 said:
I can now access my bootloader if this helps with anyone answering my issue! As I said before, any additional information from me about my phone that can help can and will be provided...just ask if you think you may be able to help!
Click to expand...
Click to collapse
Well since you in bootloader flash TWRP and then boot.img and then reflash the rom just to make sure.
Progress!
Darknites said:
Well since you in bootloader flash TWRP and then boot.img and then reflash the rom just to make sure.
Click to expand...
Click to collapse
Here is the inexperienced flasher in me asking this: How would I go about doing that? Is there a simplified way you could explain this to me, or even a guide? Thanks so much for the reply!
fragkiller1 said:
Here is the inexperienced flasher in me asking this: How would I go about doing that? Is there a simplified way you could explain this to me, or even a guide? Thanks so much for the reply!
Click to expand...
Click to collapse
Sorry. Best would be the All-In-One Toolkit, TWRP is a recovery to replace CWM because its that what's messing you up and also TWRP is better. Toolkit will also flash the boot.img too.
Darknites said:
Sorry. Best would be the All-In-One Toolkit, TWRP is a recovery to replace CWM because its that what's messing you up and also TWRP is better. Toolkit will also flash the boot.img too.
Click to expand...
Click to collapse
Okay, will do! Also, where would I find the Boot.img?
And on a side note; my phone says S-ON...I thought when rooted it was supposed to be S-OFF. Could that be causing problems as well?
fragkiller1 said:
Okay, will do! Also, where would I find the Boot.img?
And on a side note; my phone says S-ON...I thought when rooted it was supposed to be S-OFF. Could that be causing problems as well?
Click to expand...
Click to collapse
Boot.img is in the rom zip. S-On is not the reason its CWM thats messing you up with getting into the bootloader but also not flashing boot.img is not helping too.
Darknites said:
Boot.img is in the rom zip. S-On is not the reason its CWM thats messing you up with getting into the bootloader but also not flashing boot.img is not helping too.
Click to expand...
Click to collapse
The toolkit isnt working for me. Im not sure why... It seems like ill never get this phone up and running again
fragkiller1 said:
The toolkit isnt working for me. Im not sure why... It seems like ill never get this phone up and running again
Click to expand...
Click to collapse
Does the bootloader say fastboot usb?
Darknites said:
Does the bootloader say fastboot usb?
Click to expand...
Click to collapse
Yes it says fastboot USB, but i can not access it on my computer. Also, every time I try to run the toolkit you mentioned earlier... it says something along the line on "command not recognized" in CMD Prompt.
fragkiller1 said:
Yes it says fastboot USB, but i can not access it on my computer. Also, every time I try to run the toolkit you mentioned earlier... it says something along the line on "command not recognized" in CMD Prompt.
Click to expand...
Click to collapse
Hmm not sure have you tried redownloading it or reinstalling the HTC drivers and if that dont work best ask in the toolkit thread.
Darknites said:
Hmm not sure have you tried redownloading it or reinstalling the HTC drivers and if that dont work best ask in the toolkit thread.
Click to expand...
Click to collapse
That was the problem. the toolkit now works (in terms of doing what its supposed to do), but I can no longer access fastboot....just my recovery. any advice on how to get fix this?
fragkiller1 said:
That was the problem. the toolkit now works (in terms of doing what its supposed to do), but I can no longer access fastboot....just my recovery. any advice on how to get fix this?
Click to expand...
Click to collapse
I see that you got the toolkit and bootloader working but did you end up using the RUU?
Success!
Darknites said:
I see that you got the toolkit and bootloader working but did you end up using the RUU?
Click to expand...
Click to collapse
Yes, i ran the RUU and my phone reverted to its stock factory state, no problems at all! Im going to unlock the bootloader again as well as root and install CM10. Thank you for all your help!
fragkiller1 said:
Yes, i ran the RUU and my phone reverted to its stock factory state, no problems at all! Im going to unlock the bootloader again as well as root and install CM10. Thank you for all your help!
Click to expand...
Click to collapse
Np but this time use TWRP as your recovery and once you up and running with CM10 you can use Flash Image GUI to flash the boot.img if you ever update the rom.
im trying to get back to complete stock to start over again because i cant get help with my 'no signal problem' but it wont start my factory restore even though i am using the right img.
the issues started when i tried to install Cataclysm (http://forum.xda-developers.com/showthread.php?t=2518660) they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
no link and i cant find it on google so any help would be appreciated
image attached its the error when trying to restore the factory image.
dudekiller said:
im trying to get back to complete stock to start over again because i cant get help with my 'no signal problem' but it wont start my factory restore even though i am using the right img.
the issues started when i tried to install Cataclysm (http://forum.xda-developers.com/showthread.php?t=2518660) they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
no link and i cant find it on google so any help would be appreciated
image attached its the error when trying to restore the factory image.
Click to expand...
Click to collapse
You can always try the second method for the "BACK TO STOCK" guide from here:
http://forum.xda-developers.com/showthread.php?t=2513701
Even better you can use the instructions from the second post of that thread to wipe clean all your partitions prior to flashing them via fastboot.
quendil said:
You can always try the second method for the "BACK TO STOCK" guide from here:
http://forum.xda-developers.com/showthread.php?t=2513701
Even better you can use the instructions from the second post of that thread to wipe clean all your partitions prior to flashing them via fastboot.
Click to expand...
Click to collapse
im still getting invalid bootloader img
dudekiller said:
im still getting invalid bootloader img
Click to expand...
Click to collapse
have you extracted all the images on C:/image-hammerhead-krt16m like the example?
Have you renamed "bootloader-hammerhead-XXXXXX.img" to "bootloader.img" and "radio-hammerhead-XXXXXX.img" to "radio.img"?
quendil said:
have you extracted all the images on C:/image-hammerhead-krt16m like the example?
Have you renamed "bootloader-hammerhead-XXXXXX.img" to "bootloader.img" and "radio-hammerhead-XXXXXX.img" to "radio.img"?
Click to expand...
Click to collapse
yes, it seems that twrp corrupted something and it doesnt recognize the device anymore.
dudekiller said:
yes, it seems that twrp corrupted something and it doesnt recognize the device anymore.
Click to expand...
Click to collapse
Oh damn...
On bootloader when you give the command fastboot devices does it show you anything?
i wonder if the TWRP bug is why i was getting bootloop when flashing Bootanimations the other day?
Wug's Nexus toolkit has been my lifeline with 4 nexus devices.
alright guys i figured it out i did a oem lock and unlock and then the factory image worked so im stock right now... it might stay that way for a bit.. lol
comicbookguy72 said:
Wug's Nexus toolkit has been my lifeline with 4 nexus devices.
Click to expand...
Click to collapse
and this is the problem with pretty much everything. people relying on toolkits, then when something screws up, they have no idea what happened.
Zepius said:
and this is the problem with pretty much everything. people relying on toolkits, then when something screws up, they have no idea what happened.
Click to expand...
Click to collapse
his first priority is fixing it. his second priority is possibly finding out why he borked it and not making the same mistake again. i've borked stuff learning and fixed it with toolkits.
not everyone wants to learn ADB or fastboot commands, or install the SDK, and NOT EVERYONE HAS TO. not everyone is a would-be developer
dudekiller said:
they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
Click to expand...
Click to collapse
So why did you flash via TWRP then?
Han Solo 1 said:
So why did you flash via TWRP then?
Click to expand...
Click to collapse
i didnt go through the faqs before installing, i looked at the rom and what it offered. it said stable so i wasnt to worried about bugs since i was coming from cm11
I finally managed to flash a working version of the COS version 1.2 to my OPO 64GB (China set) and it works fine except now i notice my bootloader is totally locked and i've tried 2 other tookits from XDA and manually tried to unlock the bootloader using command but still unsuccessful.
Has anybody got any experience with this?
Solution found at http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 (Credit to @Mnt-XDA)
Scann69 said:
I finally managed to flash a working version of the COS version 1.2 to my OPO 64GB (China set) and it works fine except now i notice my bootloader is totally locked and i've tried 2 other tookits from XDA and manually tried to unlock the bootloader using command but still unsuccessful.
Has anybody got any experience with this?
Click to expand...
Click to collapse
try on another pc
kenzolo said:
try on another pc
Click to expand...
Click to collapse
Tried that too....did not work either.....:crying:
It might be helpful if you could provide a little more detail...
With ADB setup and your phone is fastboot mode, please connect your phone to your PC and run the following:
Code:
adb version
What is the output?
Code:
fastboot devices
What is the output?
Code:
fastboot oem unlock
What is the output?
What exactly is making you think you're locked?
dmarden said:
It might be helpful if you could provide a little more detail...
With ADB setup and your phone is fastboot mode, please connect your phone to your PC and run the following:
Code:
adb version
What is the output?
Code:
fastboot devices
What is the output?
Code:
fastboot oem unlock
What is the output?
What exactly is making you think you're locked?
Click to expand...
Click to collapse
Well....this is what i'm getting :crying:
Might be a small thing and might not help... but can you run "fastboot reboot" after the oem unlock, let it boot into Android, then reboot into fastboot mode and try to flash recovery?
Remember that when you oem unlock you wipe the device.
dmarden said:
Might be a small thing and might not help... but can you run "fastboot reboot" after the oem unlock, let it boot into Android, then reboot into fastboot mode and try to flash recovery?
Remember that when you oem unlock you wipe the device.
Click to expand...
Click to collapse
Right after it run oem unlock, it auto reboots into recovery. From recovery I then reboot into fastboot again and flash recovery and i get the unlock msg :crying:
Scann69 said:
Right after it run oem unlock, it auto reboots into recovery. From recovery I then reboot into fastboot again and flash recovery and i get the unlock msg :crying:
Click to expand...
Click to collapse
If it's auto rebooting into recovery after the unlock, something is definitely wrong. Sorry, not really sure. It should reboot into whatever Android build you've got installed. In TWRP did you try re-flashing whatever build your device came with... try to start fresh? I know you can download the CM 11S builds right from CM, not sure about ColorOS.
dmarden said:
If it's auto rebooting into recovery after the unlock, something is definitely wrong. Sorry, not really sure. It should reboot into whatever Android build you've got installed. In TWRP did you try re-flashing whatever build your device came with... try to start fresh? I know you can download the CM 11S builds right from CM, not sure about ColorOS.
Click to expand...
Click to collapse
Yah.....can't tell what is wrong but in TWRP, when i flash CM11S, it just says fail.
Scann69 said:
Yah.....can't tell what is wrong but in TWRP, when i flash CM11S, it just says fail.
Click to expand...
Click to collapse
Hey Bro any updates, were you able to get things fixed ?
I am having the same issue
tkdsl said:
Hey Bro any updates, were you able to get things fixed ?
I am having the same issue
Click to expand...
Click to collapse
Nup.....am still trying whatever i find on the internet but still can't get it to unlock. There is this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 that i have not tried and am not too sure if i should. no feedback from any developers yet.
Scann69 said:
Nup.....am still trying whatever i find on the internet but still can't get it to unlock. There is this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 that i have not tried and am not too sure if i should. no feedback from any developers yet.
Click to expand...
Click to collapse
thank you, that worked for me to fix the issue.
I now have the bootloader truly unlocked and was able to reset the device.
Great...worked for me too. Finally problem solved. Thanks to @Mnt-XDA
Scann69 said:
Great...worked for me too. Finally problem solved. Thanks to @Mnt-XDA
Click to expand...
Click to collapse
I have THIS SAME EXACT ISSUE where entering that command goes into reboot and into recovery and bootloader does not unlock.
I am happy to know that this has been fixed with that tampering zip fix. I can't wait to try it out myself.
This was my thread.
http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
Scann69 said:
I finally managed to flash a working version of the COS version 1.2 to my OPO 64GB (China set) and it works fine except now i notice my bootloader is totally locked and i've tried 2 other tookits from XDA and manually tried to unlock the bootloader using command but still unsuccessful.
Has anybody got any experience with this?
Click to expand...
Click to collapse
bro i have same issue as you. i read your comments. i also created a thread. if you fixed the issue please reply and help me resolve it as well. here is my thread that i created on same issue: http://forum.xda-developers.com/oneplus-one/help/flash-recovery-please-help-t2841223.
also bro please reply and help me fix the same issue.
---------- Post added at 01:45 AM ---------- Previous post was at 01:40 AM ----------
Scann69 said:
Great...worked for me too. Finally problem solved. Thanks to @Mnt-XDA
Click to expand...
Click to collapse
hey bro can you please reply. i also found the same thread as you-----http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
the thread is not in much detail can you please reply to me and give me step by step instructions?
gur1nder said:
hey bro can you please reply. i also found the same thread as you-----http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
the thread is not in much detail can you please reply to me and give me step by step instructions?
Click to expand...
Click to collapse
You pretty much at boot into recovery mode (fastboot boot <recovery-file-name>.img and then adb sideload OnePlusOne-BootUnlocker.zip in that thread.
Scann69 said:
Nup.....am still trying whatever i find on the internet but still can't get it to unlock. There is this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 that i have not tried and am not too sure if i should. no feedback from any developers yet.
Click to expand...
Click to collapse
Thank you, saved me from RMA my OPO
I can't thank you enough guys... i have been dealing with this issue for the past 2 days... this is the only thing that fixed my phone!! Thank you again!! :good:
Scann69 said:
Nup.....am still trying whatever i find on the internet but still can't get it to unlock. There is this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 that i have not tried and am not too sure if i should. no feedback from any developers yet.
Click to expand...
Click to collapse
Hi,
I am playing with this whole day and I cannot get it fix
I red this: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
but it does not make sense to me at all
I am in this status:
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
How do I supposed to install the OnePlusOne-OnlyBootloaderToggle.zip ???
From fastboot? or from TWRP? or how??
Thank you very much... I am desperate after whole day :crying:
djha53k said:
Hi,
I am playing with this whole day and I cannot get it fix
I red this: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
but it does not make sense to me at all
I am in this status:
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
How do I supposed to install the OnePlusOne-OnlyBootloaderToggle.zip ???
From fastboot? or from TWRP? or how??
Thank you very much... I am desperate after whole day :crying:
Click to expand...
Click to collapse
From twrp.
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/
Hi I'm new, how have I got an acatel Idol 3 (6045 Y)
Well I'll have Idol 3 updated to version 6.0,
I'd like to know how I can go back / downgrade to Android 5
I've already done the hard reset, the cache wipe, but nothing stays the same
Greetings and thanks
Joselito.98 said:
Hi I'm new, how have I got an acatel Idol 3 (6045 Y)
Well I'll have Idol 3 updated to version 6.0,
I'd like to know how I can go back / downgrade to Android 5
I've already done the hard reset, the cache wipe, but nothing stays the same
Greetings and thanks
Click to expand...
Click to collapse
You need to downgrade, only with rom if someone have it.
persona78 said:
You need to downgrade, only with rom if someone have it.
Click to expand...
Click to collapse
With adb? Because it does not work for me, remote command unknown
I've tried everything, that error happens when flashing twrp
regards
Joselito.98 said:
With adb? Because it does not work for me, remote command unknown
I've tried everything, that error happens when flashing twrp
regards
Click to expand...
Click to collapse
Is because with the update you loose bootloader commands ( fastboot)
So, you need to root, after root install Rashr from Google play, with Rashr you can flash twrp, with twrp you can flash aboot.img from 5.0.2 version with a flash zip then you recover bootloader commands like this.
persona78 said:
Is because with the update you loose bootloader commands ( fastboot)
So, you need to root, after root install Rashr from Google play, with Rashr you can flash twrp, with twrp you can flash aboot.img from 5.0.2 version with a flash zip then you recover bootloader commands like this.
Click to expand...
Click to collapse
The problem is there, I want to twrp to do root.
The question is not to get recovery custon, but root
I tried it with adb, but I got the same error ...
regards
Joselito.98 said:
The problem is there, I want to twrp to do root.
The question is not to get recovery custon, but root
I tried it with adb, but I got the same error ...
regards
Click to expand...
Click to collapse
What he's saying is that without fastboot the only way you can flash a ROM is through TWRP. You need to root and then install TWRP, and then install the ROM. Also, if you're doing any kind of reflashing; to do so without a custom recovery is risky at best.
magus7091 said:
What he's saying is that without fastboot the only way you can flash a ROM is through TWRP. You need to root and then install TWRP, and then install the ROM. Also, if you're doing any kind of reflashing; to do so without a custom recovery is risky at best.
Click to expand...
Click to collapse
That's it, but I mean I can not flash the twrp nor the root, I get: unknown remote command
Joselito.98 said:
That's it, but I mean I can not flash the twrp nor the root, I get: unknown remote command
Click to expand...
Click to collapse
You get this because you don't have fastboot any more!!
Do you get this?
You must find another way to root, maybe kingroot!
persona78 said:
You get this because you don't have fastboot any more!!
Do you get this?
You must find another way to root, maybe kingroot!
Click to expand...
Click to collapse
If I have adb and fastboot, with kingroot not working
Now I make a video
Joselito.98 said:
That's it, but I mean I can not flash the twrp nor the root, I get: unknown remote command
Click to expand...
Click to collapse
Look at this thread to get TWRP and root. Works perfectly; I went through this procedure several times on 6045I. Just read carefully to understand the steps; there are couple of other threads that are linked from this one.
kt-Froggy said:
Look at this thread to get TWRP and root. Works perfectly; I went through this procedure several times on 6045I. Just read carefully to understand the steps; there are couple of other threads that are linked from this one.
Click to expand...
Click to collapse
Now take a look, and in step 1 put the twrp but only for idol 4, not for mine
Joselito.98 said:
Now take a look, and in step 1 put the twrp but only for idol 4, not for mine
Click to expand...
Click to collapse
Yes, the TWRP steps are described for Idol 4, but the process works perfectly fine for 6045. That thread is a compilation of steps from few other threads that are linked from there; some may not be specifically for our model, but they work. Just read carefully and make sure you understand. It's quite normal on XDA, when you find some info from another device's forum, and adapt it to your device. Like I said, I did this myself on 6045I at least 3-4 times, while fooling around with the phone after I got it.
kt-Froggy said:
Yes, the TWRP steps are described for Idol 4, but the process works perfectly fine for 6045. That thread is a compilation of steps from few other threads that are linked from there; some may not be specifically for our model, but they work. Just read carefully and make sure you understand. It's quite normal on XDA, when you find some info from another device's forum, and adapt it to your device. Like I said, I did this myself on 6045I at least 3-4 times, while fooling around with the phone after I got it.
Click to expand...
Click to collapse
But does it work with android 6?
And if I get the same error?
Hello ? Can someone help me please
kt-Froggy said:
Yes, the TWRP steps are described for Idol 4, but the process works perfectly fine for 6045. That thread is a compilation of steps from few other threads that are linked from there; some may not be specifically for our model, but they work. Just read carefully and make sure you understand. It's quite normal on XDA, when you find some info from another device's forum, and adapt it to your device. Like I said, I did this myself on 6045I at least 3-4 times, while fooling around with the phone after I got it.
Click to expand...
Click to collapse
Hello, I followed all the steps of this post, but there is a problem, idol 3 6045Y, there is no download mode, as you did
regards
PS: Thank you
Hi, why are not I going? I tried the sahara and firehose
I do everything well does not come out, no error, but at the time of starting the recovery leaves the factory.
I tried that twrp and also several more, but being all ok, I do not know why it's not going
regards
I have tried the Sahara again in every possible way.
And if with the sahara I try to put a rom with android 5?
And what about the flashtool?
regards
Joselito.98 said:
I have tried the Sahara again in every possible way.
And if with the sahara I try to put a rom with android 5?
Click to expand...
Click to collapse
You can't use Sahara & Firehose for flashing the ROM. It will only let you to flash the recovery (TWRP).
You have to understand that you need to go through several steps here...
1. Your goal is to downgrade to 5.x. You can't flash a 5.x official stock ROM, because the only way to flash stock is to use Mobile Upgrade Q, and you already got an update to 6.0 for your phone. Your only choice is to find a 5.x ROM that can be flashed from TWRP.
2. So, you need to install TWRP. I recommended using Sahara & Firehose, because this method works for me every time with no problems. I pointed you to the thread with ALL the information you need. If it doesn't work for you, I don't know why. Maybe you don't have the proper drivers installed? You need the drivers before you try doing anything with your phone from your PC. Maybe you have a bad USB cable or port? Maybe something else? I have no idea... I simply told you what works for me 100%.
3. There may be another way, if you somehow root you phone first, then flash TWRP using Rashr, for example. But I don't know how to root it. I only rooted it by flashing SuperSU, after I already had TWRP installed, so I can't help you with this...
Most importantly, you need to understand what you are doing, why you need to do specific steps, and the purpose of all the tools you use...
kt-Froggy said:
You can't use Sahara & Firehose for flashing the ROM. It will only let you to flash the recovery (TWRP).
You have to understand that you need to go through several steps here...
1. Your goal is to downgrade to 5.x. You can't flash a 5.x official stock ROM, because the only way to flash stock is to use Mobile Upgrade Q, and you already got an update to 6.0 for your phone. Your only choice is to find a 5.x ROM that can be flashed from TWRP.
2. So, you need to install TWRP. I recommended using Sahara & Firehose, because this method works for me every time with no problems. I pointed you to the thread with ALL the information you need. If it doesn't work for you, I don't know why. Maybe you don't have the proper drivers installed? You need the drivers before you try doing anything with your phone from your PC. Maybe you have a bad USB cable or port? Maybe something else? I have no idea... I simply told you what works for me 100%.
3. There may be another way, if you somehow root you phone first, then flash TWRP using Rashr, for example. But I don't know how to root it. I only rooted it by flashing SuperSU, after I already had TWRP installed, so I can't help you with this...
Most importantly, you need to understand what you are doing, why you need to do specific steps, and the purpose of all the tools you use...
Click to expand...
Click to collapse
Here you have all the procedure "well done" of how to download twrp with the sahara, and you will see that it does not work ...
https://vimeo.com/210311115