Related
I've followed the rooting instruction for 2.20 and got confirmation that my CID is at 11111111. I got an unlock token and followed the instructions at htcdev.com I chose "unlock bootloader" and the phone rebooted. I installed a terminal app to see if I was rooted, and I'm not. No "su" command was available. So, I went through the root process again, from the beginning, generating a new code. This time, when I ran "fastboot flash unlocktoken Unlock_code.bin" I got confirmation in the command prompt that it worked, but nothing happened on my phone, i.e. there's no "Unlock bootloader?" screen. I can still use the volume rocker to highlight options, but I don't know what to do from here.
Does anyone have any ideas?
ctennenh said:
I've followed the rooting instruction for 2.20 and got confirmation that my CID is at 11111111. I got an unlock token and followed the instructions at htcdev.com I chose "unlock bootloader" and the phone rebooted. I installed a terminal app to see if I was rooted, and I'm not. No "su" command was available. So, I went through the root process again, from the beginning, generating a new code. This time, when I ran "fastboot flash unlocktoken Unlock_code.bin" I got confirmation in the command prompt that it worked, but nothing happened on my phone, i.e. there's no "Unlock bootloader?" screen. I can still use the volume rocker to highlight options, but I don't know what to do from here.
Does anyone have any ideas?
Click to expand...
Click to collapse
You need to flash a rooted Rom. you were on 2.20, it is a temp.root to change your cid so you can unlock your boot loader.
Did you flash teamwin recovery yet?
Sent from my HTC One XL using xda app-developers app
Not yet. I was following the instruction here: http://forum.xda-developers.com/showthread.php?t=1952038 and in this thread: http://forum.xda-developers.com/showthread.php?t=1954458 which say to get the unlock token and proceed to htcdev right after changing the CID. I thought that teamwin recovery got installed after that. Did I do something out of order? What should I do differently? Thanks.
ctennenh said:
Not yet. I was following the instruction here: http://forum.xda-developers.com/showthread.php?t=1952038 and in this thread: http://forum.xda-developers.com/showthread.php?t=1954458 which say to get the unlock token and proceed to htcdev right after changing the CID. I thought that teamwin recovery got installed after that. Did I do something out of order? What should I do differently? Thanks.
Click to expand...
Click to collapse
After you unlock your bootloader you need to flash TWRP from ADB, since you don't have SU installed.
You have to flash TWRP before doing anything on 2.20
Is your bootloader not unlocked? Retry it, make sure the unlock token is in the PRECISE format that they ask for
absolutelygrim said:
After you unlock your bootloader you need to flash TWRP from ADB, since you don't have SU installed.
You have to flash TWRP before doing anything on 2.20
Is your bootloader not unlocked? Retry it, make sure the unlock token is in the PRECISE format that they ask for
Click to expand...
Click to collapse
Retry what part? I'm sorry. Do you mean I should do the whole process from the start, or just part of it? It actually says "unlocked" at the top of the bootloader screen right now. Should I just go ahead and flash the TW openrecovery?
I downloaded the latest CM10 and ran fastboot on the boot.img. After flashing openrecovery should I be good to flash the ROM and gapps? Thanks for your help.
ctennenh said:
Retry what part? I'm sorry. Do you mean I should generate a new token?
Click to expand...
Click to collapse
Use the same token, but retry the process
Ok, I re-ran "fastboot flash unlocktoken Unlock_code.bin" with the same file. It still says "unlocked" at the top. Then I ran "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img". According to the instructions in the thread on installing custom ROMs I should do a "fastboot reboot" now before installing the ROM, but I don't want to reboot yet if it will undo the root.
ctennenh said:
Ok, I re-ran "fastboot flash unlocktoken Unlock_code.bin" with the same file. It still says "unlocked" at the top. Then I ran "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img". According to the instructions in the thread on installing custom ROMs I should do a "fastboot reboot" now before installing the ROM, but I don't want to reboot yet if it will undo the root.
Click to expand...
Click to collapse
go into adb and type "adb reboot recovery" if TWRP shows up, mount your SD and drag a ROM into your SD and the boot.img from the ROM, and then unmount your SD card. Full Wipe, flash the boot.img and the ROM and reboot.
you never really *had* root.
The 2.20 exploit is a temporary root to change your CID to 1111111, so you can permanently unlock your boot loader at anytime.
absolutelygrim said:
go into adb and type "adb reboot recovery" if TWRP shows up, mount your SD and drag a ROM into your SD and the boot.img from the ROM, and then unmount your SD card. Full Wipe, flash the boot.img and the ROM and reboot.
you never really *had* root.
The 2.20 exploit is a temporary root to change your CID to 1111111, so you can permanently unlock your boot loader at anytime.
Click to expand...
Click to collapse
I'm getting "error: device not found". Can I do the same thing through bootloader-recovery on the phone itself?
ctennenh said:
I'm getting "error: device not found". Can I do the same thing through bootloader-recovery on the phone itself?
Click to expand...
Click to collapse
Yea, you don't have to do it through adb. You know how to get into recovery?
Power off the phone, power it on, then continue to hold Volume Down and you will be at the hboot screen, then go to recovery from there
Edit: If you are already at the hboot screen you don't need to turn off your phone, just go to recovery
absolutelygrim said:
Yea, you don't have to do it through adb. You know how to get into recovery?
Power off the phone, power it on, then continue to hold Volume Down and you will be at the hboot screen, then go to recovery from there
Edit: If you are already at the hboot screen you don't need to turn off your phone, just go to recovery
Click to expand...
Click to collapse
Ok, so this is where I am on the instructions for installing a new ROM.
2. Run the following command:
'fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img' (make sure img file is in same folder as your adb stuff)
then 'fastboot reboot'
3. Run the following command after the phone is rebooted:
'adb reboot recovery'
4. You should be in the new TWRP recovery. From there it is recommended to do a factory reset before flashing the new ROM.
I've flashed twrp. Should I run "fastboot reboot" from the command line, or choose "recovery"? I appreciate your patience with me!
ctennenh said:
Ok, so this is where I am on the instructions for installing a new ROM.
2. Run the following command:
'fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img' (make sure img file is in same folder as your adb stuff)
then 'fastboot reboot'
3. Run the following command after the phone is rebooted:
'adb reboot recovery'
4. You should be in the new TWRP recovery. From there it is recommended to do a factory reset before flashing the new ROM.
I've flashed twrp. Should I run "fastboot reboot" from the command line, or choose "recovery"? I appreciate your patience with me!
Click to expand...
Click to collapse
Recovery. if you can't use adb reboot recovery use fastboot reboot instead and hold volume down until you get into the boot loader, then scroll down to reboot, hit the power button, scroll down to recovery and hit the power button again. That should put you in TWRP
After choosing recovery I get the HTC loading screen with "This build is for development purposes only..." It's rebooted a couple times on its own to this screen, so I'm concerned I'm on a reboot loop.
ctennenh said:
After choosing recovery I get the HTC loading screen with "This build is for development purposes only..." It's rebooted a couple times on its own to this screen, so I'm concerned I'm on a reboot loop.
Click to expand...
Click to collapse
Hold the power button and volume down until the phone turns off. When the screen turns off let go of the power button but not volume down. Continue holding volume down until you see your bootloader screen. It will say UNLOCKED at the top
edit: btw, when flashing boot.img, use the following command fastboot flash boot boot.img so put the boot.img in the folder with fasboot.exe and use that command. When it flashes, then you can flash your ROM
Sent from my HTC One XL using xda app-developers app
Awesome. So I've mounted my SD card and copied my gapps.zip, the ROM zip, and the flashed boot.img into the Download folder. Then I unmount, wipe, and flash the boot.img and the ROM?
ctennenh said:
Awesome. So I've mounted my SD card and copied my gapps.zip, the ROM zip, and the flashed boot.img into the Download folder. Then I unmount, wipe, and flash the boot.img and the ROM?
Click to expand...
Click to collapse
Unmount.
Wipe System
Factory Reset (wipes /data and /cache)
Flash your boot.img from fastboot using "fastboot flash boot boot.img"
Flash your ROM
Flash gapps
Reboot and enjoy
Gah! I've wiped and factory reset, and now it's "waiting for device" when I try to fastboot the boot.img. Is there some option I need to choose on TW recovery in order to run fastboot on the boot.img? I don't see a "flash" option anywhere, but the instruction on flashing new ROMs doesn't say what to do to actually flash something.
ctennenh said:
Gah! I've wiped and factory reset, and now it's "waiting for device" when I try to fastboot the boot.img. Is there some option I need to choose on TW recovery in order to run fastboot on the boot.img? I don't see a "flash" option anywhere, but the instruction on flashing new ROMs doesn't say what to do to actually flash something.
Click to expand...
Click to collapse
Reboot back into bootloader. and then boot into fastboot from your boot loader, then try the command again.
You are a fabulous human being. Thanks so much for being patient with me and helping me through this. It's been a lot tougher than I expected. Now to get to bed. I have to get up early in the morning
ctennenh said:
You are a fabulous human being. Thanks so much for being patient with me and helping me through this. It's been a lot tougher than I expected. Now to get to bed. I have to get up early in the morning
Click to expand...
Click to collapse
You got everything working? Enjoy your root, unlock, and ROM, and good night
I'm posting this in a single thread to minimize clutter.
I recently ran Easy Ace Root tool as instructed on my inspire. The bootloader unlocked, CWM flashed, but there was an error during superuser flash.
After a reflash of superuser things looked okay, but superuser began not responding. I re-flashed superuser twice in attempt to fix it using the Easy Ace Root Tool.
EDIT: I have discovered that superuser will only function with "USB debug mode" enabled. I've tried it on and off several times, and each time it malfunctions but function returns without a problem.
The backup I have been restoring seems to work because it was created with the debug mode enabled. Took a while to see it.
Second, CWM started to exhibit the "power off, charge" recovery bug where CWM opens.
Last, I attempted to install/flash 4ext Recovery Touch twice to address the CWM bug. Both times it hung at "flashing recovery" (approx 20 mins. both times). Eventually, it indicated that 4ext was installed. However, booting into recovery shows that I still have CWM. I used two different versions (RC8 & RC 7) in the attempt.
I'm now using the restored and working ROM. Solutions to the superuser debug issue I haven't seen posted
The failure to flash 4ext is troubling.
Questions
1. Could these issues be related? Or, what should I be looking for?
2. The recovery issue seems to be the most important. What might be the cause of 4ext to fail in this manner?
3. Can the Easy Ace Root Tool be rerun on the unlocked bootloader, and would that fix anything?
4. Is there reason to worry about flashing with CWM?
I see a number of possible solutions, the main one is to flash a new ROM, which I have already downloaded a couple, but doesn't adress the recovery problems.
The issue with CWM and 4ext leave me less than confident in using it to flash with, although CWM seems okay. The other item is that some ROMs indicate that S-off in required, but many of the threads are a couple years old.
5. Is it correct that S-off is not required to flash ROMs (I read it somewhere)?
I found an answer: NO, YOU DON'T NEED S-OFF TO FLASH ROMS....
Solving the issues are good lessons
Stock AT&T ROM
Android 2.3.5, Sense 3.0
Bootloader screen indicates-
UNLOCKED
S_ON
I know that's a lot for one thread but I'm just looking for a direction and I'll do the search.
If anyone has suggestions, directions, or ideas fire away.
Thanks
I think the fact that you are still S-ON is causing problems with the recovery flashing, since S-ON basically means that the recovery partition is not-writeable.
Have you tried using fastboot to flash a new recovery? Plug your phone into a computer, get into the bootloader, select "fastboot" (if not already selected), wait for "FASTBOOT USB" to appear, and then run the following on the computer:
Code:
fastboot flash recovery <path to recovery.img>
However that S-ON still worries me. You might have to do things manually:
Code:
androidforums.com/desire-hd-all-things-root/702100-how-manually-achieve-s-off-simunlock-supercid-inspire-4g-dhd.html
(Sorry for the broken URL - I had to disguise it. Blargh, I hate being a n00b.)
Evil_ryan said:
I think the fact that you are still S-OFF is causing problems with the recovery flashing, since S-OFF basically means that the recovery partition is not-writeable.
Have you tried using fastboot to flash a new recovery? Plug your phone into a computer, get into the bootloader, select "fastboot" (if not already selected), wait for "FASTBOOT USB" to appear, and then run the following on the computer:
Code:
fastboot flash recovery <path to recovery.img>
However that S-OFF still worries me. You might have to do things manually:
Code:
androidforums.com/desire-hd-all-things-root/702100-how-manually-achieve-s-off-simunlock-supercid-inspire-4g-dhd.html
(Sorry for the broken URL - I had to disguise it. Blargh, I hate being a n00b.)
Click to expand...
Click to collapse
Thanks, I think you meant to say the fact that I am still S-ON? The S_ON part shouldn't be an issue from all that I've gathered. In fact, that's how I have CWM. The Easy Ace Root Tool does CWM, with an unlocked bootloader S_ON. Nothing I have come across states that S_OFF is required to flash 4ext recovery.
Other noobs might find this other thread useful as there is some info and links to recovery images. http://forum.xda-developers.com/showthread.php?p=22489317#post22489317
No I haven't tried the fastboot yet. That is an option, I've got it and adb setup on my computer already. I have looked at AAHK, but as it says its no longer supported, and I don't think I need of S_OFF. Taking it slow to sort out the problems so I don't do sumthin stooopid.
How are you flashing 4ext? From fastboot?
Right, S-ON, that's what I get for writing this at 12 AM.
Don't bother with AAHK, it's discontinued, and even if you still had a copy it couldn't download the necessary files.
bananagranola said:
How are you flashing 4ext? From fastboot?
Click to expand...
Click to collapse
bananagranola,
I used the 4Ext Recovery Updater for both attempts. As I said in the OP, both attempts hung at "flashing recovery" approx 20 mins, and eventually indicated that 4ext was installed. In Recovery Updater it listed/highlighted the version I thought I had installed, but CWM was still the recovery that booted.
Cremnomaniac said:
bananagranola,
I used the 4Ext Recovery Updater for both attempts. As I said in the OP, both attempts hung at "flashing recovery" approx 20 mins, and eventually indicated that 4ext was installed. In Recovery Updater it listed/highlighted the version I thought I had installed, but CWM was still the recovery that booted.
Click to expand...
Click to collapse
Try doing it from fastboot.
bananagranola said:
Try doing it from fastboot.
Click to expand...
Click to collapse
I thought that would be next.
Can you confirm for me that the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=1848846 are correct for the Inspire 4G?
It's the EVO 3D forum. And I have some other links to using fastboot I'll check before doing it.
Yes, those instructions will work. If you can't boot into fastboot through the GUI, you can also power on the phone while holding the volume down button, and that will get you into the bootloader.
Evil_ryan said:
Yes, those instructions will work. If you can't boot into fastboot through the GUI, you can also power on the phone while holding the volume down button, and that will get you into the bootloader.
Click to expand...
Click to collapse
Okay, great. This is the only recovery .img that I have found 4EXT-recovery-2.2.7_RC5.img - 3.33 MB
If I install the 4ext recovery Updater after flashing it should work okay?
And, Will I be able to update once I have flashed it (assuming it works) and have installed the recovery Updater?
Cremnomaniac said:
If I install the 4ext recovery Updater after flashing it should work okay?
Click to expand...
Click to collapse
Probably. But I don't think it really matters, since if you can flash a recovery using fastboot, you can do everything that 4ext updater otherwise would.
Cremnomaniac said:
And, Will I be able to update once I have flashed it (assuming it works) and have installed the recovery Updater?
Click to expand...
Click to collapse
See above.
If 4ext doesn't work, you can also try CWM and TWRP (TeamWin Recovery Project). I use the latter with my Inspire 4g.
I strongly advise you use the app to download the recovery, unzip, and then flash it from fastboot.
bananagranola said:
I strongly advise you use the app to download the recovery, unzip, and then flash it from fastboot.
Click to expand...
Click to collapse
I'll take "strongly" as more than a suggestion. Thanks, it had not occurred to me to get the recovery.img from the updater.
I had actually found several other images and was trying to figure out what was what. That saved me some time, but I did read a lot about 4ext.
I was considering trying the Recovery Updater one more time. Bad Idea?
Cremnomaniac said:
I'll take "strongly" as more than a suggestion. Thanks, it had not occurred to me to get the recovery.img from the updater.
I had actually found several other images and was trying to figure out what was what. That saved me some time, but I did read a lot about 4ext.
I was considering trying the Recovery Updater one more time. Bad Idea?
Click to expand...
Click to collapse
I have a hunch that if you are S-On, you can only write to the recovery partition from fastboot.
bananagranola said:
I have a hunch that if you are S-On, you can only write to the recovery partition from fastboot.
Click to expand...
Click to collapse
I am S-ON. Does that present an issue with fastboot of the recovery.img?
I'm just going to overwrite the current recovery. Nothing else needs to be done does it?
Cremnomaniac said:
I am S-ON. Does that present an issue with fastboot of the recovery.img?
I'm just going to overwrite the current recovery. Nothing else needs to be done does it?
Click to expand...
Click to collapse
No.
bananagranola said:
No.
Click to expand...
Click to collapse
Solved the 4EXT flashing issue. Looks like 4ext flashed okay with fastboot, and the 4EXT Recovery Control works. Rebooted into recovery a couple times just to be sure. That kills 2 birds the CWM bug and the recovery flash.
Thanks for the help and suggestions all.
Some notes from a noobs experience -
Setting up ADB and Fastboot is very easy.
If your cautious as I am run some basic commands in ADB and Fastboot that won't do damage [devices, reboot, reboot-bootloader, etc.]
If you get "error: cannot load 'recovery.img" make sure you navigate to folder that recovery.img is located. Then run "Fastboot flash recovery [Filename]." Even though I set system variables on my desktop to point to adb and fastboot, it won't find the recovery image if you start from the wrong directory in terminal (i.e., C:\)
If you're in ADB and you use the command "adb reboot-bootloader" it will boot the device straight to "Fastboot USB".
Don't forget that each time you flash a ROM from recovery, you still need to fastboot flash its boot.img separately.
bananagranola said:
Don't forget that each time you flash a ROM from recovery, you still need to fastboot flash its boot.img separately.
Click to expand...
Click to collapse
Thanks for the reminder. I just spent an hour looking at 4EXT "smartflash no available". I hav some links for doing fastboot flash of the boot.img. I think I'm good there.
One question from my OP remains. Superuser only works (i.e., grants root access) when I have USB debug mode selected. When it's off superuser says the app (e.g., Titanium BU) is granted permission but just hangs until I force close it and re-enable USB debug. i can't find anything on this problem.
Is it an issue to run my phone in USB debug mode all the time? Or, any clue to the problem?
I am not able to flash TWRP recovery after updating my OPO to CM OS 12 via OTA.
I have tried everything and followed every step precisely.
After enabling USB debugging & turning off update recovery in Developer Options.
I used command prompt and flashed the recovery image.
Everything happens smoothly and the command prompt shows flashing successful.
But after rebooting the phone and going to recovery. I get Cyanogen Recovery again and again.
I even tried "fastboot erase recovery" before "fastboot flash recovery recovery.img"
Even then nothing happens. Cynogen Recovery comes again and again.
I have two OPO and another one is running CM11s.
I flashed TWRP without any problem in my old OPO.
If anyone knows the solution, please help.
Read the FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
Transmitted via Bacon
I've read the FAQ and am having exactly the same problem as the orignal poster.
Additionally, I also tried to "erase" boot via flash, got a successful and then reflashed twrp again. It just doesn't work. Has something changed?
Thanks,
/geir
gsjurseth said:
I've read the FAQ and am having exactly the same problem as the orignal poster.
Additionally, I also tried to "erase" boot via flash, got a successful and then reflashed twrp again. It just doesn't work. Has something changed?
Thanks,
/geir
Click to expand...
Click to collapse
Nothing has changed, try powering off your phone completely after flashing, and then using the power + volume down combo to get to recovery.
XDA Moderator
Transmitted via Bacon
Hi all,
I started out on TWRP version 2.7.1.0, and I wanted to flash the latest TWRP recovery (2.8.7.0), so I used the app that was linked by the TWRP site (TWRP Manager). So I tried to flash the latest update, and then a message pops up telling me to check if this was the right partition. I was careless and I didn't check it, and went ahead and installed it. It said it failed, but next thing I know, every time I tried to reboot(into the system/OS) I just boot right into TWRP (version 2.8.7.0). Then from TWRP (2.8.7.0) I tried to reboot into recovery, and it rebooted into TWRP, except that it was version 2.7.1.0, where I started.
So, when I hit boot into system, I got TWRP (2.8.7.0), and when I hit boot into recovery, I got TWRP 2.7.1.0. I was completely confused, so I wiped the OS, and then booted into fastboot to fastboot flash TWRP(2.8.7.0) in my recovery (It worked). Right now, I'm soft-bricked so I don't have an OS, but I have TWRP(2.8.7.0) as my recovery. Except now, I still get TWRP when I try to boot into system, and fastboot flashing, adb sideloading, and regular TWRP flashing is not working...
Any help is very appreciated, I need my phone to just be working!!! Except, if anyone can help me update it to 5.1 while they're at it, that would be awesome!
akn4497 said:
Hi all,
I started out on TWRP version 2.7.1.0, and I wanted to flash the latest TWRP recovery (2.8.7.0), so I used the app that was linked by the TWRP site (TWRP Manager). So I tried to flash the latest update, and then a message pops up telling me to check if this was the right partition. I was careless and I didn't check it, and went ahead and installed it. It said it failed, but next thing I know, every time I tried to reboot(into the system/OS) I just boot right into TWRP (version 2.8.7.0). Then from TWRP (2.8.7.0) I tried to reboot into recovery, and it rebooted into TWRP, except that it was version 2.7.1.0, where I started.
So, when I hit boot into system, I got TWRP (2.8.7.0), and when I hit boot into recovery, I got TWRP 2.7.1.0. I was completely confused, so I wiped the OS, and then booted into fastboot to fastboot flash TWRP(2.8.7.0) in my recovery (It worked). Right now, I'm soft-bricked so I don't have an OS, but I have TWRP(2.8.7.0) as my recovery. Except now, I still get TWRP when I try to boot into system, and fastboot flashing, adb sideloading, and regular TWRP flashing is not working...
Any help is very appreciated, I need my phone to just be working!!! Except, if anyone can help me update it to 5.1 while they're at it, that would be awesome!
Click to expand...
Click to collapse
I would flash the new RUU.
andybones said:
I would flash the new RUU.
Click to expand...
Click to collapse
Thanks for the reply!
I have already tried to flash the RUU for 4.4.4 but the recovery flash method gave me an error, and the fastboot flash method gave me
FAILED...(remote: not allowed)
I will try again in the morning and let you know how it goes, but I have a feeling it will end the same way.
akn4497 said:
Thanks for the reply!
I have already tried to flash the RUU for 4.4.4 but the recovery flash method gave me an error, and the fastboot flash method gave me
FAILED...(remote: not allowed)
I will try again in the morning and let you know how it goes, but I have a feeling it will end the same way.
Click to expand...
Click to collapse
Why not use the new 5.0.1 RUU?
andybones said:
I would flash the new RUU.
Click to expand...
Click to collapse
andybones said:
Why not use the new 5.0.1 RUU?
Click to expand...
Click to collapse
Yup that's what I meant I'll try 5.0.1 in the morning. Just wondering, will I need the firmware for it? Because I am coming from 4.4.4
akn4497 said:
Yup that's what I meant I'll try 5.0.1 in the morning. Just wondering, will I need the firmware for it? Because I am coming from 4.4.4
Click to expand...
Click to collapse
The firmware is apart of the RUU, did you use cmd
fastboot oem rebootRUU
Then flash RUU? Fastboot flash zip nameofRUU.zip
andybones said:
The firmware is apart of the RUU, did you use cmd
fastboot oem rebootRUU
Then flash RUU?
Click to expand...
Click to collapse
Oh shoot, I feel dumb. I'll let you know, thanks!
The RUU worked! I used the exe and I'm up and running. Thanks!!
akn4497 said:
The RUU worked! I used the exe and I'm up and running. Thanks!!
Click to expand...
Click to collapse
When you go to flash your custom recovery, use fastboot rather than twrp manager. If you MUST use such a shortcut, I might recommend flashify.
cntryby429 said:
When you go to flash your custom recovery, use fastboot rather than twrp manager. If you MUST use such a shortcut, I might recommend flashify.
Click to expand...
Click to collapse
Yeah I think I'll just stick with fastboot flashing recoveries from now on! Thanks
akn4497 said:
Yeah I think I'll just stick with fastboot flashing recoveries from now on! Thanks
Click to expand...
Click to collapse
Glad to hear you're up and running my friend.
I was following the directions here on how to unlock and root my new pixel, and after the fastboot boot-to-image step, it restarted a few times (as it was supposed to) and then it got stuck on the bouncing dots stage. When I attempted to restart into recovery, I instead got a "[Ramdump] writing to EXT4 file" message, and I was not able to get into recovery after several attempts. Are there any options for recovering this or did I manage to brick it beyond repair?
Thanks
Are you able to flash the factory image?
roirraW "edor" ehT said:
Are you able to flash the factory image?
Click to expand...
Click to collapse
or flash the recovery TWRP
roirraW "edor" ehT said:
Are you able to flash the factory image?
Click to expand...
Click to collapse
After the battery drained overnight, I manged to boot into recovery. Is it worth it to try and see if it starts normally or should I leave it in recovery and try the factory reflash? If the reflash, should I pick the most recent image, or do I need to pick the correct one that it came with?
henk-jan said:
or flash the recovery TWRP
Click to expand...
Click to collapse
Even though ADB recognizes my device now (I was able to boot into recovery after the battery drained overnight), I can't see it on my computer to manually transfer files, can I push the TWRP .zip file onto the device using ADB, and does it matter where on the device it gets put (the instructions just say to copy it to the device)?
cdenney said:
After the battery drained overnight, I manged to boot into recovery. Is it worth it to try and see if it starts normally or should I leave it in recovery and try the factory reflash? If the reflash, should I pick the most recent image, or do I need to pick the correct one that it came with?
Click to expand...
Click to collapse
It won't hurt anything to see if it'll boot. Most recent image.
roirraW "edor" ehT said:
It won't hurt anything to see if it'll boot. Most recent image.
Click to expand...
Click to collapse
Flashing the factory image worked. Now I just have to decide if I try it again or just relock the bootloader and leave well enough alone. Thanks!
cdenney said:
Flashing the factory image worked. Now I just have to decide if I try it again or just relock the bootloader and leave well enough alone. Thanks!
Click to expand...
Click to collapse
If you're in any way hesitant, don't touch it. I wouldn't relock the bootloader personally.
cdenney said:
Flashing the factory image worked. Now I just have to decide if I try it again or just relock the bootloader and leave well enough alone. Thanks!
Click to expand...
Click to collapse
You don't need anything but SuperSU zip to root. Enable developers option in settings, enable usb debugging, in fastboot mode fastboot boot TWRP IMG, if you want custom recovery, flash pixel TWRP zip, reboot recovery, flash SuperSU, reboot, otherwise skip TWRP zip and reboot recovery part. No boot to root is necessary. Just flash SuperSU. Simple.
Here is link to TWRP IMG to boot into
https://dl.twrp.me/sailfish/twrp-3.0.2-0-RC1-fastboot-sailfish.img.html
...
cdenney said:
Flashing the factory image worked. Now I just have to decide if I try it again or just relock the bootloader and leave well enough alone. Thanks!
Click to expand...
Click to collapse
I will say, I had this exact issue before. The issue was that I had inadvertently used an older version of fastboot. Worth double checking.
Tulsadiver said:
You don't need anything but SuperSU zip to root. Enable developers option in settings, enable usb debugging, in fastboot mode fastboot boot TWRP IMG, if you want custom recovery, flash pixel TWRP zip, reboot recovery, flash SuperSU, reboot, otherwise skip TWRP zip and reboot recovery part. No boot to root is necessary. Just flash SuperSU. Simple.
Here is link to TWRP IMG to boot into
https://dl.twrp.me/sailfish/twrp-3.0.2-0-RC1-fastboot-sailfish.img.html
Click to expand...
Click to collapse
Hey you mind giving me guild on how it is done, i am lost here. I read number of them but do not wish to brick my phone.
Thank you