Develop Bugs

[SOLVED]Koodo Stock Recovery found!

GO TO THE POST BELOW FOR THE RECOVERY AND INFO. PLEASE THANK HIM
CLICK ME FOR POST.
This is his topic full of stock recoveries and what-not
--------------------
Bear in mind that I do not have the time to restore to stock, and then check it for myself if you can extract the stock recovery without root, but you probably can. Please refer to the quote I will post below as I have little time to clean this post up.
Please thank user Davy Jones for actually finding the solution!
Davy Jones said:
Okay, I don't know any coding so I apologize if this is a dumb suggestion, but is it possible to follow the article's directions to pull recovery? So from shell:
dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery.img bs=4096
I'm already on cwm so I have no way of testing this. Also, please don't try this unless you know what you are doing. I tried this on cwm and it created a file that was 10MB instead of the .img I originally flashed, which was 5.98MB.
Click to expand...
Click to collapse
My post starts here
-------------------------------------------
Alrighty that's wonderful. I am trying a guide right now and I will see if I am successful at extracting a recovery and I will report back.
EDIT
I've made wonderful process, and I've extracted a 10mb file which what the recovery.img supposed to be resized to.
So i've basically typed in
After this, I got a huge list of the partitions, and using this I've confirmed that mmcblk0p22 is the block that contains the recovery (I also made sure that I didn't extract something else, etc by checking what the userdata and sdcard size is supposed to be?
Then I typed in
and got
So I ended up with a 10MB file sitting in the root of my internal memory (known as sdcard)
Now I will try to confirm if it is the same file as my recovery.
EDIT
Well after more digging around.. I found this and where it says "Download - Recovery Image Method (using dd):" It shows that the block which the recovery is in in actually the same as the one above, so there was an easier way. Oh well! At least we confirmed that we have the correct file, the question is, can we flash it, guess I'll try after I get home.
If you want to try this out on a NON-Rooted one, you'll have to go to Settings>Developer Options>Root access and allow ADB.
-----------------------------------------------
Quote ends here.
Hopefully you're a Koodo owner reading this and have noticed the title.
Many of us Koodo owners, have rooted, installed a custom recovery, and have started the flashing frenzy, but we have forgot one thing.
No its not making a NAND of the stock ROM, its the fact the we forgot to backup our stock recoveries! I know it might not be a difference compared to the Telus recovery, but we still need to be sure, that when we want to update, or if we want to return the phone, what we are fully stock.
So what I'm asking you, is to make a backup of your Koodo stock recovery, and share it with us
Unfortunately I do not know how to extract a recovery.img. So hopefully an XDA member will post a guide in this to help us extract the .img
or as always, Google is your best friend
Cheers, and thanks
EDIT
Koragg618 said:
I have found a link on how to get it
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Download link for RomDump is at the end of the article
Click to expand...
Click to collapse
Those are the instructions.
Thanks everyone for contributing!

I have a stock phone still but need a guide on pulling my recovery. Would I just use ADB or?...

chevymeister said:
I have a stock phone still but need a guide on pulling my recovery. Would I just use ADB or?...
Click to expand...
Click to collapse
Im not a koodo member but is it not the same way for tmobile users? With stock ODIN flash? when I ODIN flash my t989 to stock it also flash the stock recovery

I have found a link on how to get it
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Download link for RomDump is at the end of the article

Bump, since no one is really noticing the pinned topic

Koragg618 said:
Bump, since no one is really noticing the pinned topic
Click to expand...
Click to collapse
I could help, Ive got a Koodo S2 X. However, its not rooted, would i still be able to make a backup of my stock recovery.

Yes I believe it is still possible, just make sure Debugging mode is on and you are using the ADB method, and not the one that has the Android Terminal one. Thanks

My friend and my girlfriend both have Stock Koodo Phone... so i'm gonne try to bring the original Koodo Recovery.img. I read the articles from addictive tips... but i think i missed something, They said we need to root the phone but the first step in the method to root the phone is to install CWM recovery IMG via Odin... So it will overwrite Koodo original Recovery.img.... before i extract it...
Any clue or hint ???
Maybe another way to root via ADB ???

I have a Koodo T989D still on stock everything. I want to root my phone and do all this fancy stuff on it but I'm not in a hurry. I can make a copy of my stock recovery if I get the proper instructions.
edit: isn't this what you're looking for anyway?? http://forum.xda-developers.com/showthread.php?t=1849748

tazmania12345 said:
I have a Koodo T989D still on stock everything. I want to root my phone and do all this fancy stuff on it but I'm not in a hurry. I can make a copy of my stock recovery if I get the proper instructions.
edit: isn't this what you're looking for anyway?? http://forum.xda-developers.com/showthread.php?t=1849748
Click to expand...
Click to collapse
No. What you're pointing to us is a custom Rom... Based on the Stock Koodo Rom. What we are looking for is the Stock Recovery... Just to put back the entire phone in original condition if you have to bring it back to manufacturer for repair...

Tornade69 said:
No. What you're pointing to us is a custom Rom... Based on the Stock Koodo Rom. What we are looking for is the Stock Recovery... Just to put back the entire phone in original condition if you have to bring it back to manufacturer for repair...
Click to expand...
Click to collapse
Oh i see... I'm still on stock 4.0.4 so i'll definitely try to provide the backup. Like i said, i'd need the proper instructions because i'm new to all of this.

Someone previously posted the stock recovery which I have attached. Use at your own risk since I have not tested it!

Amazing, where did you find this!

Koragg618 said:
Amazing, where did you find this!
Click to expand...
Click to collapse
Someone previously posted it few weeks ago on the XDA forums in the device dev section and I had downloaded and kept a copy in case I needed it.

jumran said:
Someone previously posted it few weeks ago on the XDA forums in the device dev section and I had downloaded and kept a copy in case I needed it.
Click to expand...
Click to collapse
Thanks! This will come in handy.

Sorry to be the bad news but I believe this recovery is the one that I've packaged before I though I've found the TLLG2 stock recovery from this site page 68( post by netusername and uploading it without testing it 1st.... then later installed/tested it and it was a CWM touch recovery and not the TLLG2 stock recovery, Sorry again.
Source:
User:netusername
KOODO STOCK IMAGE/RESTORE
Directions: Download these three in the same folder - Part 1, Part 2, Part 3
Use Winrar/7zip to only extract Part 1 after you have all three parts in the same folder. You should get a folder called clockworkmod. There should be another folder called "backup" inside.
Put the "clockwordmod" folder in your sd card.
Use clockwordmod to restore after factory reset, wipe system, wipe dalvik cache.... It is recommended that you use Clockwordmod 6 - it can be found here - http://forum.xda-developers.com/show....php?t=1823117
Enjoy!
Click to expand...
Click to collapse
Sent from my ♛ SGH-T989 ♛ using XDA app.

Oh well thats confusing Thanks for the info man!

Sorry I'm not following.
Do you mean the post by jumran (http://forum.xda-developers.com/showpost.php?p=32299219&postcount=12) is not the stock recovery and is actually a CWM recovery that you're mentioning?
KRZ-2pa said:
Sorry to be the bad news but I believe this recovery is the one that I've packaged before I though I've found the TLLG2 stock recovery from this site page 68( post by netusername and uploading it without testing it 1st.... then later installed/tested it and it was a CWM touch recovery and not the TLLG2 stock recovery, Sorry again.
Source:
Sent from my ♛ SGH-T989 ♛ using XDA app.
Click to expand...
Click to collapse

Yes it is a CMW Touch recovery and no problem

[curious] What are you guys doing? [/curious]
You realize backing up any part of your original stock ROM is pointless? All you have to do pick up the original stock tarball from Samsung's website, fire up ODIN, flash, and then not even Samsung can tell you ever did something to your phone. It will be stock everything: radio, recovery, ROM...
---------- Post added at 08:41 PM ---------- Previous post was at 08:31 PM ----------
Here, follow the instructions: http://fus.nanzen.se/
There are no presets for Koodo, but all the information you need is readily available on the original box your phones came in.
And if you really need the Koodo recovery for whatever reason, it is an IMG file inside the TARball. You can just DD it in place.

[Q] So, the stupid here just deleted the OS via TWRP

Completely idiot, was trying to wipe my phone to troubleshoot Remote Play app problems, ended up wiping everything off the internal memory. I've been reading through lots of threads and I'm still unsure of what are the correct procedures to avoid a pretty brick on my desk. With that said...
TWRP works, phone is detected, I'm able to do adb and fastboot commands. Some info:
cidnum: HTC__622
version-main: 2.11.708.2
version-bootloader: 3.18.0.0000
Downloaded a stock nandroid backup (based on the info above), but I'm unable to copy it to my phone by mouting USB via TWRP, Windows says file is too large.
So, what would be the correct procedure? Can I install a GPE ROM or should I worry about getting Sense back to work first? Am I screwed?
Thanks.

Adb push it. Twrp needs to be in adb mode.
Other option. Get your backup, or even a rom on a micro SD if you can and install from it.

Htc one?
Try copying to UsbOtg and connect with device. Then just flash it from twrp
Sent from my HTCONE using XDA Free mobile app

or follow the guide in my sig (KJ's second method mentioned above)

felipaopl said:
Completely idiot, was trying to wipe my phone to troubleshoot Remote Play app problems, ended up wiping everything off the internal memory. I've been reading through lots of threads and I'm still unsure of what are the correct procedures to avoid a pretty brick on my desk. With that said...
TWRP works, phone is detected, I'm able to do adb and fastboot commands. Some info:
cidnum: HTC__622
version-main: 2.11.708.2
version-bootloader: 3.18.0.0000
Downloaded a stock nandroid backup (basedi on the info above), but I'm unable to copy it to my phone by mouting USB via TWRP, Windows says file is too large.
So, what would be the correct procedure? Can I install a GPE ROM or should I worry about getting Sense back to work first? Am I screwed?
Thanks.
Click to expand...
Click to collapse
Copy it over to an sd card and insert that into your phone.

I have no backup and no external SD card at the moment.
Which file should I download to get started? When "AD Push", do I need a ZIP file? The one I've downloaded is a "stock nandroid backup", not sure if this is the correct file?

felipaopl said:
Which file should I download to get started? When "AD Push", do I need a ZIP file? The one I've downloaded is a "stock nandroid backup", not sure if this is the correct file?
Click to expand...
Click to collapse
No, I would use a ROM zip, not a nandroid. Reason being, a nandroid has to be in the exact folder location in order for TWRP to see it and RESTORE from it. In contrast, a ROM zip can be anywhere on the internal memory (just pushing it to the root of the folder is easiest) and then you can select INSTALL in TWRP and browse anywhere on the memory or SD to flash a ROM zip.
Alternately, you can use adb sideload to flash a ROM zip.
---------- Post added at 11:42 AM ---------- Previous post was at 11:41 AM ----------
KJ said:
Adb push it. Twrp needs to be in adb mode.
Click to expand...
Click to collapse
adb commands should work with the phone in any mode, as long as its on. The exception is adb sideload, for which you need to be in TWRP and in sideload mode. So that may be what you are thinking of.

redpoint73 said:
No, I would use a ROM zip, not a nandroid. Reason being, a nandroid has to be in the exact folder location in order for TWRP to see it and RESTORE from it. In contrast, a ROM zip can be anywhere on the internal memory (just pushing it to the root of the folder is easiest) and then you can select INSTALL in TWRP and browse anywhere on the memory or SD to flash a ROM zip.
Alternately, you can use adb sideload to flash a ROM zip.
---------- Post added at 11:42 AM ---------- Previous post was at 11:41 AM ----------
adb commands should work with the phone in any mode, as long as its on. The exception is adb sideload, for which you need to be in TWRP and in sideload mode. So that may be what you are thinking of.
Click to expand...
Click to collapse
I've used adb about 3 times in my life. Lol
Appreciate the info. ?
Yes.... Use fastboot all the time. Lol Just not adb.
Adb Noob..... ish.

redpoint73 said:
No, I would use a ROM zip, not a nandroid. Reason being, a nandroid has to be in the exact folder location in order for TWRP to see it and RESTORE from it. In contrast, a ROM zip can be anywhere on the internal memory (just pushing it to the root of the folder is easiest) and then you can select INSTALL in TWRP and browse anywhere on the memory or SD to flash a ROM zip.
Alternately, you can use adb sideload to flash a ROM zip.
---------- Post added at 11:42 AM ---------- Previous post was at 11:41 AM ----------
adb commands should work with the phone in any mode, as long as its on. The exception is adb sideload, for which you need to be in TWRP and in sideload mode. So that may be what you are thinking of.
Click to expand...
Click to collapse
Thanks, the problem is that I'm unable to find a stock ROM for my HTC One M8 variant, from Hong Kong. What would be the outcome when installing a different ROM than the original?

felipaopl said:
Thanks, the problem is that I'm unable to find a stock ROM for my HTC One M8 variant, from Hong Kong. What would be the outcome when installing a different ROM than the original?
Click to expand...
Click to collapse
Since you are bootloader unlocked, you can flash whatever ROM you want, as long as it meets your requirements and preferences for features, language, etc.
If you are asking me what the difference between the stock ROM and custom ROMs are; there are too many custom ROMs (with a wide array of possible features) to even begin answering that question.
You won't get OTA updates on a custom ROM, but you lost that ability when you installed TWRP.

You need to read up before doing anything else... If you value your device. Lack of knowledge and confidence with this stuff is a recipe for disaster.
Start here,
http://forum.xda-developers.com/showthread.php?t=2711073
Then read through some things related to what you want to do in the Q&A section.
Again, the more you learn.... The safer and easier this stuff gets. ?

redpoint73 said:
Since you are bootloader unlocked, you can flash whatever ROM you want, as long as it meets your requirements and preferences for features, language, etc.
If you are asking me what the difference between the stock ROM and custom ROMs are; there are too many custom ROMs (with a wide array of possible features) to even begin answering that question.
You won't get OTA updates on a custom ROM, but you lost that ability when you installed TWRP.
Click to expand...
Click to collapse
Thanks, makes sense. But what about problems with radio version, for example? Not dangerous using a non-original ROM?

felipaopl said:
Thanks, makes sense. But what about problems with radio version, for example? Not dangerous using a non-original ROM?
Click to expand...
Click to collapse
No, its not "dangerous". You might see some impact if the ROM's build.prop doesn't play well with the radio. Use a ROM that supports your version of the M8, to be safe.
You certainly won't be better off than you are now, which is a phone with no OS.
If you were that concerned about the stock ROM, you should have made a nandroid. You should do that before messing with anything in TWRP.

redpoint73 said:
No, its not "dangerous". You might see some impact if the ROM's build.prop doesn't play well with the radio. Use a ROM that supports your version of the M8, to be safe.
You certainly won't be better off than you are now, which is a phone with no OS.
If you were that concerned about the stock ROM, you should have made a nandroid. You should do that before messing with anything in TWRP.
Click to expand...
Click to collapse
Yes, you're completely right. Living and learning, I guess.

By the way, is there a repository for stock M8 ROMs? I was able to find the nandroid backups but not the ROMs in ZIP format to flash via the ADB Push method.

felipaopl said:
By the way, is there a repository for stock M8 ROMs? I was able to find the nandroid backups but not the ROMs in ZIP format to flash via the ADB Push method.
Click to expand...
Click to collapse
Just look in the Development section for stock ROMs.

redpoint73 said:
Just look in the Development section for stock ROMs.
Click to expand...
Click to collapse
Thanks. Another question that just came to my mind right now. If installing a stock, US ROM for example, will I lose LTE? Since my phone is from Honk Kong, not sure about that.

felipaopl said:
If installing a stock, US ROM for example, will I lose LTE? Since my phone is from Honk Kong, not sure about that.
Click to expand...
Click to collapse
Not sure. As I mentioned, install a custom ROM that supports your version, to be safe.
I don't think you would lose LTE. Band compatibility is in the radio, not the ROM. But something in build.prop may cause some glitches or network performance may not be ideal.
I don't see a good reason to install a stock ROM that is not for your region.

redpoint73 said:
Not sure. As I mentioned, install a custom ROM that supports your version, to be safe.
I don't think you would lose LTE. Band compatibility is in the radio, not the ROM. But something in build.prop may cause some glitches or network performance may not be ideal.
I don't see a good reason to install a stock ROM that is not for your region.
Click to expand...
Click to collapse
Problem is that I'm looking over the Development section and I'm unable to find a stock ROM for Europe / Hong Kong.

felipaopl said:
Problem is that I'm looking over the Development section and I'm unable to find a stock ROM for Europe / Hong Kong.
Click to expand...
Click to collapse
Stock ROMs here: http://forum.xda-developers.com/showthread.php?t=2702664
http://forum.xda-developers.com/showthread.php?t=2694994
Although I believe these are for the EMEA version, with the "A" in EMEA standing for Asia; and I think HK is actually a different version.

Firmware Update M8 Rogers

Hi, I've talked of this before. The firmware update, I tried returning to stock then attempting to update the firmware through updating the software OTA but that failed no matter what I did. I returned to stock, flashed the stock recovery, and even locked the bootloader. And finally I attempted an RUU but the RUU failed. So now I lost all my data in vain. I rooted the phone again and reflashed it to Insert coin android 4.4.4, ect.. And I currently am really tired of this. Isn't there any way to get through this? I want the new Insert Coin Lollipop but I have S-ON and cant update the firmware. Can someone please help me? It would be really appreciated. Thanks for reading this lousy comment.

Ali7000 said:
Hi, I've talked of this before. The firmware update, I tried returning to stock then attempting to update the firmware through updating the software OTA but that failed no matter what I did. I returned to stock, flashed the stock recovery, and even locked the bootloader. And finally I attempted an RUU but the RUU failed. So now I lost all my data in vain. I rooted the phone again and reflashed it to Insert coin android 4.4.4, ect.. And I currently am really tired of this. Isn't there any way to get through this? I want the new Insert Coin Lollipop but I have S-ON and cant update the firmware. Can someone please help me? It would be really appreciated. Thanks for reading this lousy comment.
Click to expand...
Click to collapse
I don't know anything about Insert Coin. But if you want stock lollipop from Rogers, you could restore a Nandroid backup via TWRP.

For a start, post your fastboot getvar all (without serial no. and imei no.)
Then most probably the nandroid that ikeny mentioned is the right backup.

I'd be more worried about the RUU failing - I wonder what the error code was?

If OP's M8 was Rogers branded, CID ROGER_001, then RUU from Rogers never existed in the first place. Perhaps this explains the error.

ikeny said:
If OP's M8 was Rogers branded, CID ROGER_001, then RUU from Rogers never existed in the first place. Perhaps this explains the error.
Click to expand...
Click to collapse
Yes, that would be correct. That's my first assumption. Although do you have any methods to update my firmware to the latest android 5.1 lolipop?

Ali7000 said:
Yes, that would be correct. That's my first assumption. Although do you have any methods to update my firmware to the latest android 5.1 lolipop?
Click to expand...
Click to collapse
Use the TWRP nandroid backup image at the bottom of the first post -
http://forum.xda-developers.com/htc-one-m8/help/rogers-m8-lollipop-update-error-t3020675

ikeny said:
I don't know anything about Insert Coin. But if you want stock lollipop from Rogers, you could restore a Nandroid backup via TWRP.
Click to expand...
Click to collapse
I'm actually kinda wondering, is there a method to update to lollipop without returning to stock? I don't have S-OFF so I cant update the firmware alone. All I want is to update the firmware somehow and then I'd be able to use the latest Insert Coin Lollipop Rom. Although thanks a ton for that link, I'll use it as my last resort.

ikeny said:
Use the TWRP nandroid backup image at the bottom of the first post -
http://forum.xda-developers.com/htc-one-m8/help/rogers-m8-lollipop-update-error-t3020675
Click to expand...
Click to collapse
So just a confirmation before I get started, I can just restore this backup despite being in a custom rom at the moment? And will this erase all my data on the phone such as media, ext...? Thanks man, appreciate it a lot.

Ali7000 said:
So just a confirmation before I get started, I can just restore this backup despite being in a custom rom at the moment? And will this erase all my data on the phone such as media, ext...? Thanks man, appreciate it a lot.
Click to expand...
Click to collapse
Yes, and yes.
If you want future OTA, replace TWRP with the attached stock recovery as the final step.

ikeny said:
Yes, and yes.
If you want future OTA, replace TWRP with the attached stock recovery as the final step.
Click to expand...
Click to collapse
Hmnn...Thank you very much. I appreciate it a lot. So now that I have downloaded the last link to the first post which named "Rogers_5_0_1.zip" I just have to backup all my media, apps, ect...Then I can restore the lollipop backup, root the phone, then install Insert Coin 5.1. And I'm also assuming the data being wiped is absolutely unavoidable.

Ali7000 said:
Hmnn...Thank you very much. I appreciate it a lot. So now that I have downloaded the last link to the first post which named "Rogers_5_0_1.zip" I just have to backup all my media, apps, ect...Then I can restore the lollipop backup, root the phone, then install Insert Coin 5.1. And I'm also assuming the data being wiped is absolutely unavoidable.
Click to expand...
Click to collapse
After you unzip the file, you will get the TWRP nandroid image. This image is a 100% stock, and all your files and apps will be wiped. Unavoidable. You could follow the second post in the previous link for rooting. Beyond that, you are on your own.

ikeny said:
After you unzip the file, you will get the TWRP nandroid image. This image is a 100% stock, and all your files and apps will be wiped. Unavoidable. You could follow the second post in the previous link for rooting. Beyond that, you are on your own.
Click to expand...
Click to collapse
Thanks man, I appreciate all your support. I also notice that you were the one who posted nandroid. Many thanks for everything pal.

ikeny said:
After you unzip the file, you will get the TWRP nandroid image. This image is a 100% stock, and all your files and apps will be wiped. Unavoidable. You could follow the second post in the previous link for rooting. Beyond that, you are on your own.
Click to expand...
Click to collapse
Hi, I unzipped the Rogers_5_0_1.zip file and it came out a folder named "2015-02-05--12-39-33 LRX22C release-keys" and an img file named "recovery.img." Do I just copy the folder to my backup TWRP folder then ignore the img file? Sorry for being really annoying and asking a lot of question, I just wanna make sure I'm doing it right.

Ali7000 said:
Hi, I unzipped the Rogers_5_0_1.zip file and it came out a folder named "2015-02-05--12-39-33 LRX22C release-keys" and an img file named "recovery.img." Do I just copy the folder to my backup TWRP folder then ignore the img file? Sorry for being really annoying and asking a lot of question, I just wanna make sure I'm doing it right.
Click to expand...
Click to collapse
You don't need the img file now. That was the stock recovery, for later, if you want to replace the TWPR recovery.

ikeny said:
You don't need the img file now. That was the stock recovery, for later, if you want to replace the TWPR recovery.
Click to expand...
Click to collapse
Thanks a ton man, you honestly don't know how thankful I am now. I'm copying the folder right now and I'm gonna restore it.

Difficulty flashing OTA, OTA thinks It's 4.4.2.

I'm having an issue flashing an OTA, (OTA_M8_UL_L50_SENSE60_MR_Orange_UK_4.19.61.3-4.19.61.2_release_446666.zip), I've checked the build.prop and that says I'm running 5.0.1, however the flash stops with a build fingerprint mismatch.
I've attached a picture. Any ideas on how to get over this?

Wrong stock recovery.img that you installed.
You need to install stock recovery.img 4.19.61.2 not 3.33.61.9 (the one that you currently have on device)
Get the correct stock recovery.img 4.19.61.2 (on post #4) in my thread linked in my signature

ckpv5 said:
Wrong stock recovery.img that you installed.
You need to install stock recovery.img 4.19.61.2 not 3.33.61.9 (the one that you currently have on device)
Get the correct stock recovery.img 4.19.61.2 (on post #4) in my thread linked in my signature
Click to expand...
Click to collapse
Before I do, I have two questions, I'm on S-off, as I had issues (it's been a while since I've tinkered with Android) patching because of my version. Can I still flash this? Also, it says it's modified (assuming you meant this: https://www.androidfilehost.com/?fid=95916177934538955). How is it modified?

I got the recovery flashed, but now I get a different error. See attached.

That error means your current ROM is not stock enough. There will be more errors.
Get the non-rooted 4.19.61.2 backup from my thread and restore that and install stock recovery 4.19.61.2 then do OTA.

ckpv5 said:
That error means your current ROM is not stock enough. There will be more errors.
Get the non-rooted 4.19.61.2 backup from my thread and restore that and install stock recovery 4.19.61.2 then do OTA.
Click to expand...
Click to collapse
You say that, but there's three links
Current ROM
lyapota GPE 5.07.1700.9 MRA85K.H9
Alternate ROM
lyapota Sense 6.12.401.4 MRA58K
SkyDragon MM Sense 7
My TWRP Stock Nandroid Backups & Stock Recovery Collections
Which one?

Which one is "my" thread ?
Which one has the word "backup" ?
There's only one with "my" and "backup"

ckpv5 said:
Which one is "my" thread ?
Which one has the word "backup" ?
There's only one with "my" and "backup"
Click to expand...
Click to collapse
This is why, because control+F doesn't find it.
Don't get me wrong, I really appreciate all the help here, but hunting through 1000's of posts isn't exactly fun.
I'll use the thread search option

I found a backup on Mega with your name on it. Google seems to be better at find this stuff it seems.
https://mega.nz/#!S4g3SRRT!IfFwxkXW7KXh4OUklo3aFp6U7tltaxR9DuVxMmFn-YM

There is no need control+f, just click on the wordings and it opens the link ...
In fact you'll see that thread is 5 or 6 topic under yours.

TWRP keeps coming back with failed. I'm trying to flash 4.19.61.2_ckpv5.zip
Do you have the MD5 or similar for the file?

That's why you need to read my thread on how to use restore a backup.
I never write anywhere to flash but I wrote to restore.
Click (not control+F) on the link in my signature.
That thread now is under your thread.. please have a look of thread listing.
I'm on mobile and it's not easy for me ...

ckpv5 said:
That's why you need to read my thread on how to use restore a backup.
I never write anywhere to flash but I wrote to restore.
Click (not control+F) on the link in my signature.
That thread now is under your thread.. please have a look of thread listing.
I'm on mobile and it's not easy for me ...
Click to expand...
Click to collapse
I should have realised it was a nandroid backup, not a flashable zip. My sincere apologies.
I thought it was corrupt, hence why I asked for the MD5.

I now have Marshmallow on my phone. Thank you!

Flash TWRP on RUU'ed Stock ROM without PC?

Hey,
Quick question, I'm away on holiday and had to use an RUU to reset my phone completely back to stock. I don't have my PC with me but was wondering if there might be any other way to get TRWP installed so I can get back to custom ROM's before the end of my trip?
Regards,
Ravi

rav101 said:
Hey,
Quick question, I'm away on holiday and had to use an RUU to reset my phone completely back to stock. I don't have my PC with me but was wondering if there might be any other way to get TRWP installed so I can get back to custom ROM's before the end of my trip?
Regards,
Ravi
Click to expand...
Click to collapse
I've described how to do this for CM-based ROMS with Samsung devices. Unfortunately, I know of no way to do this for the HTC 10. The issue is getting it rooted. My understanding is that the Sunshine app can root some 10s, but not all. You could try that. When you run the app it will do a series of tests on your device. If it cannot be rooted by the app it will give the message, "Root is required first." Otherwise, the app can root your device and proceed from there. Once rooted you could then use Flashify to install TWRP.

2PS6IMG.zip

rav101 said:
Hey,
Quick question, I'm away on holiday and had to use an RUU to reset my phone completely back to stock. I don't have my PC with me but was wondering if there might be any other way to get TRWP installed so I can get back to custom ROM's before the end of my trip?
Regards,
Ravi
Click to expand...
Click to collapse
Like post 3 said. Just get the no wipe firmware that comes with twrp and change the name then reboot to download and flash it

Haldi4803 said:
2PS6IMG.zip
Click to expand...
Click to collapse
twinnfamous said:
Like post 3 said. Just get the no wipe firmware that comes with twrp and change the name then reboot to download and flash it
Click to expand...
Click to collapse
Thanks guys!!
I'm trying to figure out, if I want to flash just the recovery with the no wipe zip, can I delete all the other .img files within the zip or do I have to edit the Android-info.txt for the corresponding lines?
No issue in flashing the no wipe file as it is, just curious for future reference if I wanted to create easy 2PS6IMG.zip's in the future.
Sent from my HTC 10 using XDA Labs

I simply take the firmware.zip from OTA, delete all .img files, rename twrp.IMG to recovery.IMG and repack it to 2PS6IMG.zip
You don't need to change the android-info.txt as partitions without images won't get wiped, even if it says so.
You can flash Boot, Recovery and..... And.... Which was the third one? Without S-Off or signed firmware package.