Database Users

[HACK/WORKAROUND] EPF30 (or any Passion EU/VF) to official FRF85B [UNLOCKED ONLY]

Well, from what I've seen so far, the full official Nexus One Froyo build released (FRF85B) does not work on any of the Passion EU(European)/VF(Vodafone) builds like EPF30...
I popped the FRF85B OTA zip onto the SD card (renamed to update.zip) and entered recovery and selected apply update.zip from SD card... but then...
the signature check failed... which at first I though was rather strange considering I had the stock recovery image and the official signed FRF85B OTA... very strange...
But after a bit of digging, it was not so strange after all... the recovery images of the Passion and Passion EU/VF are different and apparently have different signature validations... interesting!!!
So I decided to try and fool the OTA in a simple way... I grabbed the recovery.img of a Passion build like EPE54B... flashed that recovery in fastboot...
Code:
fastboot flash recovery recovery.img
And then I went back into recovery and once again selected apply update.zip from SD card... and bada-bing... it started applying the FRF85B update... and now, I have the FRF85B build from the EPF30 build...
You can move back to the original EPF30 recovery after you apply the update...
NOTE: If you encounter a boot-loop, reboot into stock recovery [not a custom one like Amon_RAs] and wipe. If it still boot-loops, wipe and re-apply update.zip
Link to FRF85B - http://android.clients.google.com/packages/passion/signed-passion-ota-42745.dc39ca1f.zip
Link to EPE54B (to grab to recovery.img) - http://shipped-roms.com/shipped/Pas...gle_WWE_1.09.1700.1_EPE54B_release_signed.zip
Link to EPF30 (if you want the original recovery.img back) - http://shipped-roms.com/shipped/Pas...ogle_WWE_1.14.1700.1_EPF30_release_signed.zip
HAVE FUN!!!!
EDIT: Apparently, this won't work for locked bootloaders!!

I don't think you can flash a recovery image without unlocking the bootloader - even if it is a stock recovery image.

rohandhruva said:
I don't think you can flash a recovery image without unlocking the bootloader - even if it is a stock recovery image.
Click to expand...
Click to collapse
I'm not sure... unlocked my phone an hour after I received it... but I believe you can....
Anyone with a locked bootloader care to try????

I have a locked bootloader on this build, when I try to flash the recovery from EPE54B this is what I get:
C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (2302 KB)... OKAY [ 0.332s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.722s
Click to expand...
Click to collapse

haha jusum beat me to it,

oh well, that put this hack outta the books... Since Google has not yet released the OTA for the Passion EU/VF build, the OTA signature check fails...
I don't know if this is too much to ask, but if you the EPE54B full zip as PASSIMG.zip on the SD card, the bootloader might allow you to flash the entire EPE54B build which can then be updated to FRF85B...

would this be the same as downgrading? I read a post earlier that said you need to downgrade to ERD79 then root it, then upgrade to FRF85B
craigacgomez said:
if you the EPE54B full zip as PASSIMG.zip on the SD card, the bootloader might allow you to flash the entire EPE54B build which can then be updated to FRF85B...
Click to expand...
Click to collapse
would this be trying without unlocking the bootloader as before?

sorry edited above

jusumgeezer said:
would this be the same as downgrading? I read a post earlier that said you need to downgrade to ERD79 then root it, then upgrade to FRF85B
would this be trying without unlocking the bootloader as before?
Click to expand...
Click to collapse
Yes, try without unlocking... don't know if this is considered older... but it would either allow u or not... if it does, great... else...

Just to confirm it didn't work with the bootloader locked.
Kept getting an error about the image being older.
Unlocked the boot loader now & installing as per your original post above, just on reboot now....
Woot!
Just as voda released another statment that their froyo will be another 3 weeks yet!
Ha!

could you not use the battery shaving method to flash the other recovery image i.e.??
http://forum.xda-developers.com/showthread.php?t=710842
with vodafone blatantly changing froyo im not standing for that.

can anyone point me to a guide to unlock the bootloader? is it the same as rooting?
also is there a link to vodafone saying they are screwing us by three weeks?
Ta!

bentez2003 said:
can anyone point me to a guide to unlock the bootloader? is it the same as rooting?
also is there a link to vodafone saying they are screwing us by three weeks?
Ta!
Click to expand...
Click to collapse
Search around in the Development forum, there is a sticky on how to upgrade your phone to Sense UI or CM, which covers unlocking the bootloader.
Also, AFAIk, vodafone or other network operators have no role in distributing updates to the Nexus One -- only Google reserves that right.

Ok im midway through the process but i think ive hit a boot loop. the nexus x keeps appearing as if its booting then restarting. I have unlocked the bootloader then added the recovery image to my phone via dos. i started the flash it it was going fine. went downstairs then when i returned it was looping. should i take out the battery or wait? is this part of the flash?? its been going on for about 15minutes. Please help im starting to freak!

hmm the first Link (Link to FRF85B - ht tp://android.clients.google.com/pa...5.dc39ca1f.zip) dosent work :/

I am looking for someone to try this theory out on a locked bootloader
1: Extract the PASSIMG zip file to your computer
2: Copy the chosen 2.2 zip file to your SD card and ensure it is named update.zip
3: Put the Nexus One into fastboot mode, and connect it to your computer
4: fastboot boot recovery.img (the one that you extracted from the PASSIMG)
The logic is that this is the correct recovery image required to install the 2.2 update, and that your just booting it without actually installing it to the recovery partition.
As I have an unlocked bootloader, I can not test the theory. Would love to hear back if it works or not.

I am looking for someone to try this theory out on a locked bootloader
1: Extract the PASSIMG zip file to your computer
2: Copy the chosen 2.2 zip file to your SD card and ensure it is named update.zip
3: Put the Nexus One into fastboot mode, and connect it to your computer
4: fastboot boot recovery.img (the one that you extracted from the PASSIMG)
5: Continue the normal process (vol up & power), clear, apply update.zip
The logic is that this is the correct recovery image required to install the 2.2 update, and that your just booting it without actually installing it to the recovery partition.
As I have an unlocked bootloader, I can not test the theory. Would love to hear back if it works or not.

mattinglis said:
could you not use the battery shaving method to flash the other recovery image i.e.??
http://forum.xda-developers.com/showthread.php?t=710842
with vodafone blatantly changing froyo im not standing for that.
Click to expand...
Click to collapse
hahaaha, I was wondering a few days ago if anyone else did that to their battery... Is there a good reason NOT to allow the microsd to be removed while the battery is in? Unmount it, remove it, put it back in, mount it.. Right?

kuntstubble said:
I am looking for someone to try this theory out on a locked bootloader
1: Extract the PASSIMG zip file to your computer
2: Copy the chosen 2.2 zip file to your SD card and ensure it is named update.zip
3: Put the Nexus One into fastboot mode, and connect it to your computer
4: fastboot boot recovery.img (the one that you extracted from the PASSIMG)
5: Continue the normal process (vol up & power), clear, apply update.zip
The logic is that this is the correct recovery image required to install the 2.2 update, and that your just booting it without actually installing it to the recovery partition.
As I have an unlocked bootloader, I can not test the theory. Would love to hear back if it works or not.
Click to expand...
Click to collapse
I just tried to boot the recovery.img (extracted the image from PASSIMG_Passion_Google_WWE_1.09.1700.1_EPE54B_release_signed). I didn't bother to copy anything to the SD card either. Here's the output from trying:
Code:
$ /opt/android-sdk-update-manager/tools/fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)

xyellx said:
hmm the first Link (Link to FRF85B - ht tp://android.clients.google.com/pa...5.dc39ca1f.zip) dosent work :/
Click to expand...
Click to collapse
Anyone have a mirror for the FRF85B file?
EDIT: Would it be possible to go to the Universal FRF91 OTA Update directly from EPF30? I'm struggling to find the FRF85B version.

Using System Image to Update your Nexus 6 (no data loss)

Tired of waiting for the OTA? Can't use it because you're rooted? Don't want to wipe your entire phone? No problem! Here's how you can upgrade with Google's Nexus factory images without wiping your apps or sdcard.
NOTE: You must have your bootloader unlocked. If you've never unlocked your bootloader, I don't think there's any way to do this without wiping your data.
STEP 1: Install fastboot
Fastboot is Google's utility for flashing factory images. You can also use it to flash custom recoveries like TWRP and CWM. The standard way to get is is through Google's Android SDK, but that's a bit heavy-duty, so you can also download just the most important tools (fastboot and adb) separately, packaged by users. Here are some links:
Official Google Android SDK (cross-platform): http://developer.android.com/sdk/index.html#Other[1]
Unofficial for Windows: http://developer.android.com/sdk/index.html#Other[2]
Unofficial Mac/Linux: http://code.google.com/p/adb-fastboot-install/[3]
Windows users might also need to install drivers: http://developer.android.com/sdk/win-usb.html[4] (can any Windows users confirm whether it's necessary?)
STEP 2: Prepare factory image
Download the latest Nexus 6 factory image at https://developers.google.com/android/nexus/images#shamu[5]
Unzip it and open the resulting folder
Unzip the "image-shamu-*.zip" file in there
You should now be looking at something like this: http://i.imgur.com/mzrfwrP.png [6]
STEP 3: Flash! (Ah-ahhhhh! [7] )
Connect your phone to your computer via USB, and enter the bootloader. You can enter the bootloader by holding down the power and volume-down buttons to boot. Once you see the bootloader, you can release the buttons.
Open a terminal/command prompt. The syntax might be slightly different on Windows than on Mac or Linux, but basically the same. Anything you see in <> you need to replace, e.g. with the actual path to your factory image folder. The rest you should be able to copy and paste. (Tip: you can easily enter a folder path into your terminal/command prompt by simply dragging the folder onto your terminal window. This works on Mac, Windows, and the vast majority of Linux GUIs.) Enter these commands:
cd </path/to/shamu-lmy47d>
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
Reboot the bootloader.
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
cd <image-shamu-lmy47d>
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
If you DO NOT use a custom recovery (like TWRP or CWM), then also: fastboot flash recovery recovery.img
Don't worry if you see messages like "target reported max download size of 1073741824 bytes". Just wait and let it finish.
Reboot your phone and enjoy. It's normal for the first boot to take a while. Going from Kitkat to Lollipop took about 20 minutes. Going from 5.0 to 5.0.1 took 5-10, I think. YMMV.
A WORD OF WARNING: If you're moving between ROMs, you generally should do a complete reset, including wiping data. Many users have reported problems going from KitKat to Lollipop without wiping data and recommend a factory reset anyway. If you're okay with wiping everything, you can simply use Google's included flash-all scripts, or flash the userdata.img file yourself. Personally, I'm not going to bother wiping adta for an incremental update like 5.0.1->5.1. As always, be sure to back up your data!
Shamelessly stolen from: http://www.reddit.com/r/Nexus5/comments/2phqy7/howto_upgrade_android_using_nexus_factory_images/

Shouldn't you also fastboot reboot bootloader after radio flash?

This is the scenic route.

I tried to update using wugz, without unlocking the bootloader. failed. Oh well, I'll wait to receive ota
Unless this method doesnt require unlocking?

If you have an OTA zip file, this is different than using a System Img?
I do not think you need to lose data or unlock your bootloader?
Found a link for the OTA zip file.
If I remember right you can copy the zip to you phone with a USB cable.
Go into the bootloader, Volume Down and Power.
Select the zip.
I did not think you needed a terminal and all the commands if you had the OTA zip on your phones SD card.
Am I wrong does something like this not work?
or
I can just wait.....

This worked great.
I was unbranded with VZ sim, unlocked, rooted with TWRP recovery. Didn't want to lose all that nor my apps or data. This method upgrades to 5.1 without any loss.
When I was done with the flashing, I rebooted to TWRP recovery (not system) in order to wipe dalvik and cache (just to be certain). I wiped and then rebooted to system. TWRP noticed I didn't have SuperSU installed so it installed it for me. Meaning, once I got my system rebooted, I still had root too.
All in all, this process worked great for me. Thanks.

I run the first two commands
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
they worked, then i moved to the radio
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
but it failed.
Any idea?
---------- Post added 14th March 2015 at 12:17 AM ---------- Previous post was 13th March 2015 at 11:53 PM ----------
Nikos2k said:
I run the first two commands
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
they worked, then i moved to the radio
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
but it failed.
Any idea?
Click to expand...
Click to collapse
This is the message after the radio flash command:
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.697s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing modem ...**☺
FAILED (unknown status code)
finished. total time: 3.721s​
Why the failed message?

I'm decrypted. Will this re encrypt my Nexus or do I have to flash a non enforce img?

Thank you, this really helped.
Since my bootloader was locked i had to unlock it as well.
Had a bit of a scare with the whole erasing screen staying on for too long.
Went back and redid the process, and went downstairs for 5 minutes, came back and phone was booted.
Anyway, thank you again

Will this work on an encrypted phone?

mikeadamz said:
Tired of waiting for the OTA? Can't use it because you're rooted? Don't want to wipe your entire phone? No problem! Here's how you can upgrade with Google's Nexus factory images without wiping your apps or sdcard.
<<snip>>
Click to expand...
Click to collapse
I don't suggest that anyone read and follow someone else's instructions when doing something like this. Not because the instructions are wrong or anything, but because blindly following instructions doesn't involve *understanding* anything.
So rather than reading and following instructions, read and UNDERSTAND the process of installing factory images as delivered with the factory images (flash-all.sh). If you UNDERSTAND the process and what everything does, then (a) you *already know* what needs to be adjusted to do what you want, and (b) if something starts going wrong in the middle of it, you will understand why, and what to do to correct it.

mikeadamz said:
cd </path/to/shamu-lmy47d>
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
Click to expand...
Click to collapse
First, thanks for the write up, I do greatly appreciate it. Second, thanks for the tip on dragging file locations into the command prompt. Very helpful.
Now my question. When I did this I tried using exactly the steps above and had no luck whatsoever. I'd cd to the location of the img files as noted and it would say fastboot is unrecognized as an internal or external command. I moved the file into the fastboot location and got the same issue. I finally ran the fastboot from the adb folder location and just referenced the full file path for each img file (using the drag and drop method) and everything went swimmingly. My question is just about using fastboot. Should it have worked when I used cd to go to the img file location? Is there something I need to do to make it work as you described?
Thanks!
Nick

Nick D said:
First, thanks for the write up, I do greatly appreciate it. Second, thanks for the tip on dragging file locations into the command prompt. Very helpful.
Now my question. When I did this I tried using exactly the steps above and had no luck whatsoever. I'd cd to the location of the img files as noted and it would say fastboot is unrecognized as an internal or external command. I moved the file into the fastboot location and got the same issue. I finally ran the fastboot from the adb folder location and just referenced the full file path for each img file (using the drag and drop method) and everything went swimmingly. My question is just about using fastboot. Should it have worked when I used cd to go to the img file location? Is there something I need to do to make it work as you described?
Thanks!
Nick
Click to expand...
Click to collapse
Install this:
http://forum.xda-developers.com/showthread.php?t=2588979
Now ADB and fastboot are installed system wide. Put your files anywhere, I use the desktop. Hold shift and right click on wherever your files are and select "open command prompt here" and flash away. Simplified, no more dragging and dropping.

Will try with the new update (5.1.1 (LMY48M)) to ensure it works. Thanks!

[/COLOR]
handyarrow said:
Will this work on an encrypted phone?
Click to expand...
Click to collapse
Have been flashing this zip in twrp after the fastboot stage without an issue for the last few updates - http://forum.xda-developers.com/nexus-6/development/mod-disable-force-encryption-rom-kernel-t3000788

Flashed LMY48M with fastboot method and it works great.
My phone is encrypted.

Root HTC Bolt

Hey Everyone....So I just have a question about the HTC BOLT and how to root it
So I guess I am little confused as to how do I go about this in terms of rooting it
My phone must be unlocked through the htc dev site correct? If so then I am good with that step, I also have seen many posts on how to root it but I just need one general site or a way on how to do it...Last thing I want to do is screw this up and brick the phone from reading multiple posts...So any information would def help me...Currently I am on Nougat 7.0
Thanks
Jay

jortiz31877 said:
Hey Everyone....So I just have a question about the HTC BOLT and how to root it
So I guess I am little confused as to how do I go about this in terms of rooting it
My phone must be unlocked through the htc dev site correct? If so then I am good with that step, I also have seen many posts on how to root it but I just need one general site or a way on how to do it...Last thing I want to do is screw this up and brick the phone from reading multiple posts...So any information would def help me...Currently I am on Nougat 7.0
Thanks
Jay
Click to expand...
Click to collapse
you'll need to flash twrp from download mode, then boot into twrp & either flash SuperSU or Magisk v11.1
my preference is now Magisk, as it now has it's own root plus you can install magisk modules (mods or ROM) without breaking /system

Thanks for the information, So i went to the htc dev site to proceed on how to unlock bootload my phone and they mentioned about "fast boot' that is not a option that needs to be selected on my phone while in download mode ...So can i still unlock it with out that "fast boot " option?

jortiz31877 said:
Thanks for the information, So i went to the htc dev site to proceed on how to unlock bootload my phone and they mentioned about "fast boot' that is not a option that needs to be selected on my phone while in download mode ...So can i still unlock it with out that "fast boot " option?
Click to expand...
Click to collapse
you said u were good w/ that step so I didn't mention....fastboot is not an option in the menu, it's a tool...you need to use fastboot command to unlock bootloader & also to flash twrp
install this for fastboot: https://forum.xda-developers.com/showthread.php?t=2317790

Okay so I know the phone must be connected using the command terminals and to simplify this i would:
1- Use fastboot to get the phone unlocked using the code to unlock it then (NOT Choosing to flash a rom at all for my phone)
2- use use maglsk v11.1 or Super Su and follow the instructions while leaving the phone plugged into the PC
3- once done then go to the play store and update magisk manager
4 - Check any rooted apk via the play store to verify if your phone is rooted
If there is something that i am missing please let me know. Much appreciations so far getting me to this point.

jortiz31877 said:
Okay so I know the phone must be connected using the command terminals and to simplify this i would:
1- Use fastboot to get the phone unlocked using the code to unlock it then (NOT Choosing to flash a rom at all for my phone)
2- use use maglsk v11.1 or Super Su and follow the instructions while leaving the phone plugged into the PC
3- once done then go to the play store and update magisk manager
4 - Check any rooted apk via the play store to verify if your phone is rooted
If there is something that i am missing please let me know. Much appreciations so far getting me to this point.
Click to expand...
Click to collapse
after unlocking bootloader, you will need to flash twrp (fastboot flash recovery nameofrecovery.img), the twrp.img needs to be in you sdktools folder on pc, after flashing, then boot into twrp...from download mode, choose reboot to bootloader, then reboot to recovery. once in twrp, you should probably leave /system read only, then copy either supersu or magisk to sd card, and choose install from main menu of twrp....once done, boot device. if using magisk, update from store
u only need to connect to pc when entering fastboot cmds

will this root work with boost mobile HTC bolt or is there a root that will work for this phone

Chrism1971 said:
will this root work with boost mobile HTC bolt or is there a root that will work for this phone
Click to expand...
Click to collapse
Either should work fine
Sent from my unknown using XDA Labs

Question
OMJ said:
you'll need to flash twrp from download mode, then boot into twrp & either flash SuperSU or Magisk v11.1
my preference is now Magisk, as it now has it's own root plus you can install magisk modules (mods or ROM) without breaking /system
Click to expand...
Click to collapse
Look I know you know what your doing I just barley got into rooting my android devices so my question is will this Brick my phone because last time I tried kingroot and it lock everything. I am scared to lose my warranty on my phone and want to know it will work. I had to take my phone to a sprint tech store last time to get it fixed so I was wondering if you could make a video of how to do it. Thanks for your time and effort Sam.

craftingatic said:
I am scared to lose my warranty on my phone.
Click to expand...
Click to collapse
You will lost your warranty anyway, if you open the bootloader via HTCdev.

craftingatic said:
Look I know you know what your doing I just barley got into rooting my android devices so my question is will this Brick my phone because last time I tried kingroot and it lock everything. I am scared to lose my warranty on my phone and want to know it will work. I had to take my phone to a sprint tech store last time to get it fixed so I was wondering if you could make a video of how to do it. Thanks for your time and effort Sam.
Click to expand...
Click to collapse
1st...as far as warranty goes, HTC is pretty good about repair even if you unlock the bootloader. So if you unlock bootloader, then flash TWRP & root, I always recommend restoring to stock before having any warranty work done.
sorry I don't do videos, but I'm always willing to help out...it's really not very difficult, the risk of a brick is very low if u just follow the instructions...if you're just looking for root, here are the basic steps:
1. unlock bootloader via htcdev.com (you'll have to create a account)
-when selecting the device, choose "all other supported models"
-you'll need to install drivers to pc to communicate to phone, see "required resources" to the left of step 1
-you don't need to install SDK but you will need the fastboot binary in step 4
-at step 5 make sure you are communicating w/ the device by using the cmd fastboot devices, it should list your device in the output
-follow the remaining steps to unlock
2. once bootloader is unlocked, boot back into download mode to flash twrp (custom recovery)
-download latest twrp from here: https://dl.twrp.me/aca/ copy the twrp.img to the folder that has the fastboot binary
-use this cmd to flash twrp: fastboot flash recovery twrp-3.1.1-0-aca.img
-it flashes pretty quick, then boot to bootloader, then boot to recovery
3. 1st time u boot twrp it will ask if u want to keep /system read only, if u plan to stay stock w/ only root, then keep read only
-I always recommend to make a system & boot image backup just in case
-flash MagiskSU or SuperSU, I prefer Magisk
the Sprint ROM has a lot of bloat, if you're interested, I have a ROM posted that cleans all that junk up along with a lot of useful mods, with a stock look

OMJ said:
1st...as far as warranty goes, HTC is pretty good about repair even if you unlock the bootloader. So if you unlock bootloader, then flash TWRP & root, I always recommend restoring to stock before having any warranty work done.
sorry I don't do videos, but I'm always willing to help out...it's really not very difficult, the risk of a brick is very low if u just follow the instructions...if you're just looking for root, here are the basic steps:
1. unlock bootloader via htcdev.com (you'll have to create a account)
-when selecting the device, choose "all other supported models"
-you'll need to install drivers to pc to communicate to phone, see "required resources" to the left of step 1
-you don't need to install SDK but you will need the fastboot binary in step 4
-at step 5 make sure you are communicating w/ the device by using the cmd fastboot devices, it should list your device in the output
-follow the remaining steps to unlock
2. once bootloader is unlocked, boot back into download mode to flash twrp (custom recovery)
-download latest twrp from here: https://dl.twrp.me/aca/ copy the twrp.img to the folder that has the fastboot binary
-use this cmd to flash twrp: fastboot flash recovery twrp-3.1.1-0-aca.img
-it flashes pretty quick, then boot to bootloader, then boot to recovery
3. 1st time u boot twrp it will ask if u want to keep /system read only, if u plan to stay stock w/ only root, then keep read only
-I always recommend to make a system & boot image backup just in case
-flash MagiskSU or SuperSU, I prefer Magisk
the Sprint ROM has a lot of bloat, if you're interested, I have a ROM posted that cleans all that junk up along with a lot of useful mods, with a stock look
Click to expand...
Click to collapse
Do u have to rename the twrp to tarp.img? I flashed the latest tarp the direction I saw said rename twrp so did I do it wrong cause I can't boot into twrp at all I get HTC and some red text then boots all the way up

roadkill42 said:
Do u have to rename the twrp to tarp.img? I flashed the latest tarp the direction I saw said rename twrp so did I do it wrong cause I can't boot into twrp at all I get HTC and some red text then boots all the way up
Click to expand...
Click to collapse
twrp can be named anything u want, your fastboot flash cmd just has to match...when u try to boot into recovery & get a red triangle, that's stock recovery, so yeah it didn't flash then

OMJ said:
twrp can be named anything u want, your fastboot flash cmd just has to match...when u try to boot into recovery & get a red triangle, that's stock recovery, so yeah it didn't flash then
Click to expand...
Click to collapse
OK did it twice it said it did with no errors so just keep doing it till it dose? Or is there another way?
---------- Post added at 04:35 PM ---------- Previous post was at 04:34 PM ----------
roadkill42 said:
OK did it twice it said it did with no errors so just keep doing it till it dose? Or is there another way?
Click to expand...
Click to collapse
No triangle just HTC in gray then flashes red letters under it

roadkill42 said:
OK did it twice it said it did with no errors so just keep doing it till it dose? Or is there another way?
---------- Post added at 04:35 PM ---------- Previous post was at 04:34 PM ----------
No triangle just HTC in gray then flashes red letters under it
Click to expand...
Click to collapse
you should only need to flash twrp once....
post your cmds so I can see what you're doing....make sure you're in download mode

OMJ said:
you should only need to flash twrp once....
post your cmds so I can see what you're doing....make sure you're in download mode
Click to expand...
Click to collapse
OK I was in download mode I c what I can do on the rest thanks probly later today or tomorrow

roadkill42 said:
OK I was in download mode I c what I can do on the rest thanks probly later today or tomorrow
Click to expand...
Click to collapse
Is there a complete in full detail way of flashing tarp in download load mode?

roadkill42 said:
Is there a complete in full detail way of flashing tarp in download load mode?
Click to expand...
Click to collapse
full detail? it's 1 cmd.... fastboot flash recovery twrp.img
https://twrp.me/htc/htcbolt10evo.html

OMJ said:
full detail? it's 1 cmd.... fastboot flash recovery twrp.img
https://twrp.me/htc/htcbolt10evo.html
Click to expand...
Click to collapse
OK thanks there is a lot out there I might did wrong one I try this way and let u know thanks again is there a special key combo to get into twrp after flashing ?

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\Program Files\Minimal ADB and Fastboot>adb devices
List of devices attached
HT7120403511 device
when i try to reboot to recovery under the htc says this build for devloping purpose only im on n with no updates installed this phone came to me like this bran new
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
sending 'recovery' (8156 KB)...
OKAY [ 1.782s]
writing 'recovery'...
(bootloader) HOSD CL#821651
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.311s]
finished. total time: 4.096s
C:\Program Files\Minimal ADB and Fastboot>adb reboot
error: device not found
C:\Program Files\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.004s
C:\Program Files\Minimal ADB and Fastboot> I'm on 7.0

HowTo "Unbrick" U-Ultra

Hi all,
this may be helpful for all that have similar problems as I had.
After experiencing with custom ROMs, I wasn't able to boot into System and also not into Recovery anymore (ended in a bootloop).
Because I tried to flash back to a Stock ROM via RUU I also relocked my bootloader and unlocking wasn't possible anymore because the unlock option was not active and not accessible without a system.
Unfortunately there's only the Nougat RUU available and I previously had Oreo installed.
As I also have S-ON, it's not possible to flash back to the Nougat RUU.
I was only able to access the phone in bootloader mode and with fastboot.
Prerequisites:
You should be able to access your phone via fastboot, so the correct USB drivers should be installed on your PC
How did I solve this:
I downloaded the following RUU.exe from US HTC website - I'm not able to post links, but you can find it via Google: HTC U Ultra Firmware Update
Start it and go to "C:\Users\Username\AppData\Local\Temp" (on Windows 10), there you can find a temporary folder of the RUU.exe, for example {50F2F878-636A-496F-A7CB-544C067E0C4B}
You can find some files like adb.exe, htc_fastboot.exe, rom.zip, ...
Copy the folder to any location you want and close the RUU application
I then downloaded the Oreo OTA zip for my phone from androidfilehost (Thank you minhnewpro ) - see: https://forum.xda-developers.com/u-ultra/development/ruu-collection-htc-ultra-nougat-t3830999
Unzip the OTA and copy the firmware.zip to the previously copied folder from RUU (here: {50F2F878-636A-496F-A7CB-544C067E0C4B})
Start the phone into Bootloader or Download Mode and connect it to the PC
Open the commandline on the PC and cd to the copied folder from RUU
Enter the following Commands:
htc_fastboot oem rebootRUU​htc_fastboot flash zip firmware.zip​htc_fastboot flash zip firmware.zip​
htc_fastboot flash zip firmware.zip needs to be done twice, in the first run I got the following error: FAILED (remote: 90 hboot pre-update! please flush image again immediately )
The second time it went through without any error.
Now my phone works again and has the Oreo Stock ROM installed!
I hope this method also works for other phones and not just mine
Greetings

Thank you.
This method works with my HTC U Ultra dual sim.
Thank you very much.

oesiblah said:
Hi all,
this may be helpful for all that have similar problems as I had.
After experiencing with custom ROMs, I wasn't able to boot into System and also not into Recovery anymore (ended in a bootloop).
Because I tried to flash back to a Stock ROM via RUU I also relocked my bootloader and unlocking wasn't possible anymore because the unlock option was not active and not accessible without a system.
Unfortunately there's only the Nougat RUU available and I previously had Oreo installed.
As I also have S-ON, it's not possible to flash back to the Nougat RUU.
I was only able to access the phone in bootloader mode and with fastboot.
Prerequisites:
You should be able to access your phone via fastboot, so the correct USB drivers should be installed on your PC
How did I solve this:
I downloaded the following RUU.exe from US HTC website - I'm not able to post links, but you can find it via Google: HTC U Ultra Firmware Update
Start it and go to "C:\Users\Username\AppData\Local\Temp" (on Windows 10), there you can find a temporary folder of the RUU.exe, for example {50F2F878-636A-496F-A7CB-544C067E0C4B}
You can find some files like adb.exe, htc_fastboot.exe, rom.zip, ...
Copy the folder to any location you want and close the RUU application
I then downloaded the Oreo OTA zip for my phone from androidfilehost (Thank you minhnewpro ) - see: https://forum.xda-developers.com/u-ultra/development/ruu-collection-htc-ultra-nougat-t3830999
Unzip the OTA and copy the firmware.zip to the previously copied folder from RUU (here: {50F2F878-636A-496F-A7CB-544C067E0C4B})
Start the phone into Bootloader or Download Mode and connect it to the PC
Open the commandline on the PC and cd to the copied folder from RUU
Enter the following Commands:
htc_fastboot oem rebootRUU​htc_fastboot flash zip firmware.zip​htc_fastboot flash zip firmware.zip​
htc_fastboot flash zip firmware.zip needs to be done twice, in the first run I got the following error: FAILED (remote: 90 hboot pre-update! please flush image again immediately )
The second time it went through without any error.
Now my phone works again and has the Oreo Stock ROM installed!
I hope this method also works for other phones and not just mine
Greetings
Click to expand...
Click to collapse
Hello, I tried this method, but it can't flash the firmware, "FAILED (remote: cannot flash this partition in s-on state)" . Bootloader is the only way I can enter, Download mode or Recovery mode doesn't work("Can't enter download mode, use volume + or - to go back"). Any other methods available?

BOOT problem issue
hard disk recovery
"jtag"

flashing twrp into recovery

Hi, I'm trying to follow the instructions here to install Lineage OS on my OnePlus6T device: https://www.howtogeek.com/348545/how-to-install-lineageos-on-android/ but I've run into the following issue. It used to show "recovery_a" before but after a bunch of experiments where I switched the partition, I've finally managed to factory reset the device and re-trying the procedure from the start. "fastboot devices" is able to recognize the device fine. Can someone please help?
(base) ➜ fastboot flash recovery twrp-3.5.0_9-0-fajita.img
Sending 'recovery' (30980 KB) OKAY [ 0.667s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed

Flow the instructions on the twrp site, works flawless, read carefully and follow them.
OnePlus 6T (fajita)
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me

Thanks @saint6822, I was able to install the TWRP zip file after
fastboot boot twrp*.img
I then rebooted the device, however now I'm unable to get back into TWRP in order to continue the process of installing Lineage OS. Can someone point to the procedure to install Lineage OS once the TWRP zip file has been installed. I'm able to get into fastboot mode easily but can't boot into TWRP. Thanks!

vv_777 said:
Hi, I'm trying to follow the instructions here to install Lineage OS on my OnePlus6T device: https://www.howtogeek.com/348545/how-to-install-lineageos-on-android/ but I've run into the following issue. It used to show "recovery_a" before but after a bunch of experiments where I switched the partition, I've finally managed to factory reset the device and re-trying the procedure from the start. "fastboot devices" is able to recognize the device fine. Can someone please help?
(base) ➜ fastboot flash recovery twrp-3.5.0_9-0-fajita.img
Sending 'recovery' (30980 KB) OKAY [ 0.667s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Click to expand...
Click to collapse
That doesn't work, because there is no recovery partition, you never flash the the .img on these devices.... Only boot it. That is why there is an installer, it installs the recovery.
Don't use that guide, and back up your data if your phone still boots.
I have a guide here, for the 6T.
I will update it soon, as the latest version of TWRP does work fine with LOS 17.1 and 18.1, doesn't matter. So use the latest version of TWRP.

This post about making your own fastboot ROMs maybe helpful too. Just so you have the latest one. Just in case.

In the guide I I gave you it explains to install the zip file once in twrp after booting with the image to make it permanent. That's why I said follow it carefully. It does work. I am typing this on a 6t that I installed twrp on with that guide.
vv_777 said:
Thanks @saint6822, I was able to install the TWRP zip file after
fastboot boot twrp*.img
I then rebooted the device, however now I'm unable to get back into TWRP in order to continue the process of installing Lineage OS. Can someone point to the procedure to install Lineage OS once the TWRP zip file has been installed. I'm able to get into fastboot mode easily but can't boot into TWRP. Thanks!
Click to expand...
Click to collapse

I beg to differ the guide does work, he didn't follow it, it clearly says once in after booting with the image to flash the zip, thus making it permanent.
OhioYJ said:
That doesn't work, because there is no recovery partition, you never flash the the .img on these devices.... Only boot it. That is why there is an installer, it installs the recovery.
Don't use that guide, and back up your data if your phone still boots.
I have a guide here, for the 6T.
I will update it soon, as the latest version of TWRP does work fine with LOS 17.1 and 18.1, doesn't matter. So use the latest version of TWRP.
Click to expand...
Click to collapse

saint6822 said:
I beg to differ the guide does work, he didn't follow it, it clearly says once in after booting with the image to flash the zip, thus making it permanent.
Click to expand...
Click to collapse
I'm guessing you don't own a 6T? You can't do that on this device. That's immediately how I knew that guide was not right. *** Edit *** I'm just skimming that guide, it appears to say flash the .img file, which is what the OP tried to do. Does it actually say to flash a .zip file? Either way that generic guide is misleading to new users and leads to issues like this.
Another source then, the official maintainer of TWRP for the 6T,
6T TWRP Thread.
I use the old install instructions, and what I recommend, still: (from that thread)
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line (if you want to have it permanently you should flash the installer)
5. If you will flash the installer and you are stock you need also to flash magisk or your phone will not boot again
6. Enjoy it
Click to expand...
Click to collapse
Do NOT run fastboot flash, you can not flash the .img file. The OP is lucky it did not work. This used to result in the boot partition needing to be reflashed, and a phone that would not boot.

Edit: in fairness OhioYJ, you are clicking on the link I gave him TWRP's 6t specific site, not the one he was using? If you are and still can't read then see below.
I'm on a 6t typing this that I followed those instructions for. Fastbooted the image and then flashed the zip. So your lack of understanding and knowledge doesn't translate to something not working just your inept abilities to follow instructions. He didn't flash the zip simple as that. Feel free to hold his hand through what ever method you choose just understand blind leading the blind will be fun for you.
Edit: directly from page I gave,
"First download the TWRP zip file directly on your device. If you don't download the zip file to your device first for any reason, you will need to adb push the zip to the device because MTP is not currently working on the OnePlus 6T in TWRP. If you are unable to use adb, you can also use a USB stick with an OTG cable, if you have those handy. Power off the device. Hold volume up to get into fastboot mode. Run this command on your computer: fastboot boot twrp-3.2.1-0-fajita.img
In TWRP, tap on Install and browse to the zip and install it (the zip will probably be in /sdcard/Downloads). TWRP will now be installed to both slots. TWRP is now installed and you can reboot and use your device as normal."
OhioYJ said:
I'm guessing you don't own a 6T? You can't do that on this device. That's immediately how I knew that guide was not right. *** Edit *** I'm just skimming that guide, it appears to say flash the .img file, which is what the OP tried to do. Does it actually say to flash a .zip file? Either way that generic guide is misleading to new users and leads to issues like this.
Another source then, the official maintainer of TWRP for the 6T,
6T TWRP Thread.
I use the old install instructions, and what I recommend, still: (from that thread)
Do NOT run fastboot flash, you can not flash the .img file. The OP is lucky it did not work. This used to result in the boot partition needing to be reflashed, and a phone that would not boot.
Click to expand...
Click to collapse

saint6822 said:
Edit: in fairness OhioYJ, you are clicking on the link I gave him TWRP's 6t specific site, not the one he was using? If you are and still can't read then see below
Click to expand...
Click to collapse
Haha, I see where the confusion came in. I was referring to the OP link, not yours. I wasn't replying to you. I guess I should have quoted that post. That generic howtogeek article won't work on many devices, any of the ones I use on a regular basis actually.

All good, sorry for getting short with you. I'm old and crusty by nature.
OhioYJ said:
Haha, I see where the confusion came in. I was referring to the OP link, not yours. I wasn't replying to you. I guess I should have quoted that post. That generic howtogeek article won't work on many devices, any of the ones I use on a regular basis actually.
Click to expand...
Click to collapse

Just to be clear, I am able to install the TWRP zip file using the instructions from @saint6822 and @OhioYJ that have been
> adb reboot bootloader
> fastboot devices // To confirm device can be viewed
> fastboot boot twrp-3.5.0_9-0-fajita.img
Then I navigate the "Install" and locate the TWRP zip file, namely twrp-installer-fajita-3.2.3-2.zip and that installs fine. My problem arises after that, specifically after selecting Reboot and then Recovery the device reboots into the fastboot menu (i.e. the same menu I saw in the first step with "adb reboot bootloader").
I have no doubt TWRP has been installed on the device (per the installation messages appearing on the screen) but it does *not* boot back into it

Have you tried powering off and holding volume don't when you power it back on to enter recovery?
vv_777 said:
Just to be clear, I am able to install the TWRP zip file using the instructions from @saint6822 and @OhioYJ that have been
> adb reboot bootloader
> fastboot devices // To confirm device can be viewed
> fastboot boot twrp-3.5.0_9-0-fajita.img
Then I navigate the "Install" and locate the TWRP zip file, namely twrp-installer-fajita-3.2.3-2.zip and that installs fine. My problem arises after that, specifically after selecting Reboot and then Recovery the device reboots into the fastboot menu (i.e. the same menu I saw in the first step with "adb reboot bootloader").
I have no doubt TWRP has been installed on the device (per the installation messages appearing on the screen) but it does *not* boot back into it
Click to expand...
Click to collapse

I did, and it does go back to the same bootloader menu (as with "adb reboot bootloader")

The current slot is "B", hopefully that does not make a difference here. I'm also wondering if I should try different TWRP img and zip than above.

Those files worked for me, the latest LineageOs for Microg has it's own recovery (not twrp) you could try going fastboot the twrp.IMG, and from twrp and flash the OS zip before rebooting and call it done and give up on TWRP.
vv_777 said:
The current slot is "B", hopefully that does not make a difference here. I'm also wondering if I should try different TWRP img and zip than above.
Click to expand...
Click to collapse

vv_777 said:
Then I navigate the "Install" and locate the TWRP zip file, namely twrp-installer-fajita-3.2.3-2.zip and that installs fine.
Click to expand...
Click to collapse
Why are you installing such an old version? Is that a typo? That could be your problem. Have you tried the installer for 3.5.0_9-0?
Slot and name don't make a difference. I've never changed the name.

The TWRP site lists the old version at the top and you have to scroll down to the newer version I bet he's not the first to make this mistake.
OhioYJ said:
Why are you installing such an old version? Is that a typo? That could be your problem. Have you tried the installer for 3.5.0_9-0?
Slot and name don't make a difference. I've never changed the name.
Click to expand...
Click to collapse

saint6822 said:
The TWRP site lists the old version at the top and you have to scroll down to the newer version I bet he's not the first to make this mistake.
Click to expand...
Click to collapse
He's not. It took me a while to see it too.