[Dec,31,2013] [S-OFF Needed] [unruu/ruuveal] [rom.zip] - HTC One SV

This is my first post, Mods please move this to Android Development. I will continue to add new features inside the RUU rom.zip(s) as i have time.
I have taken the time to use @kmdm 's unruu and ruuveal binaries to extract and decrypt the Official RUU's posted in @old.splatterhand 's INDEX THREAD.
Not only have i decrypted the rom.zip(s), but i have also modified the android-info.txt inside them, so that as long as you are running Official firmware, you will be able to flash without having to edit the android-info.txt yourselves.
Disclaimer!
Nobody is here twisting your arm to
Download
Flash
Modify
Use or
Read this post.
Please don't twist mine for any damages to your device. I will lend support when I can.
Rules!
Know Your Device's Code Name
Do Not Flash A Rom.zip Of A Device With A Different Modelid
If You Are Unsure About How To Use What You've Just Downloaded, Don't Use It
***********************************************************************************************
First here is K2_U Variant. There are 2 Versions. One is the Europe and the other is Asia. I've edited the android-info.txt inside both versions' rom.zip. Meaning that European may flash Asian & Asian may flash European. Of course European can flash Europe Firmware, and Asian can flash Asia Firmware.
But, just because you can, does not mean you should!
Download the rom.zip and place it in your fastboot directory.
Code:
fastboot erase cache
Code:
fastboot oem rebootRUU
For Europe Firmware
Code:
fastboot flash zip K2_U_Europe_rom.zip
For Asia Firmware
Code:
fastboot flash zip K2_U_Asia_rom.zip
For
Watch your device's screen and your Computer's screen for any errors. If any of the firmware files fail, Do Not Reboot! Simply run the command again.
For Europe Firmware
Code:
fastboot flash zip K2_U_Europe_rom.zip
For Asia Firmware
Code:
fastboot flash zip K2_U_Asia_rom.zip
Code:
fastboot reboot
Now your device will boot into OEM 4.0.4 Firmware, and you may update to 4.2.2 with out issues.
***********************************************************************************************
I have added K2_UL_Europe & K2_CL_America to the Downloads list.
K2_UL_Europe is Official rom.zip only with edited android-info.txt.
K2_CL_America is Unofficial rom.zip containing Unmodified system.img, boot.img, recovery.img, and edited android-info.txt.
Downloads
K2_U_Europe_rom.zip
md5sum
c699ad37349d710755104ea975595f1b
K2_U_Asia_rom.zip
md5sum
2cfbcec83e1e4103c166d973c3e4b7e8
K2_UL_Europe_rom.zip
md5sum
6cf29bd79e412440abbbbe4d49c48959
4.0.4_K2_CL_America_rom.zip
md5sum
be6b897e018eb0c3651dde80cd46ae23
4.1.2_K2_CL_America_rom.zip
md5sum
8a436b51ee526500484577edd8436dcc
Any and all donations received will go to keeping my Dropbox account used as my server open without issues of "Your public links have been suspended because of high volume traffic".

reserved for future modified rom.zip(s)

I will be surprised if you find an ruu for K2_CL
But great work friend.
Sent from my K2_CL using Tapatalk

feel free to post requested extras you'd like in the form of
DEVICE=
WHAT I WANT=
OS=4.0.4, 4.1.2, or 4.2.2
WHERE I FOUND WHAT I WANT=

ha, nice name.....looks familiar lol, looks like you beat me to this good work!

Thread closed

Related

I Need a root package

hey guys... all the root packages I have seen so far have a survey to download ... I cant do surveys because .. well its a long story .
in a short version .. I am looking for a direct root package download without being troubled in doing a survey .
I would be grateful if some one can help me out
Please don't duplicate posts, it's against the rules. I was already helping you in the other thread you posted in but I'll continue here. The root package you were looking at is most likely not compatible with your current firmware version. What are your bootloader details? I need to see the first five lines.
Sent from my Evita
timmaaa said:
Please don't duplicate posts, it's against the rules. I was already helping you in the other thread you posted in but I'll continue here. The root package you were looking at is most likely not compatible with your current firmware version. What are your bootloader details? I need to see the first five lines.
Sent from my Evita
Click to expand...
Click to collapse
*** UNLOCKED ***
evita pvt ship s off RL
CID-HTC__622
hboot-2.15.0000
radio-1.30a.32.45.18
opendsp-v33.1.0.45.1128
What's your ultimate goal? Do you want to root your current stock ROM or install a custom ROM? Either way you need to install TWRP recovery first. I'm assuming you already have adb/fastboot installed on your PC.
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you have TWRP recovery on your phone.
If you want to root your current stock ROM you can just flash SuperSU through the install menu in TWRP recovery. You'll find a download link here:
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
If you want to install a custom ROM, just find one you like, download it, read the install instructions on the ROM thread, perform a full wipe (cache/dalvik cache/factory reset/system) through the wipe menu in TWRP, then install the ROM through the install menu in TWRP.
Before doing either of these options you should make a backup of your current setup in the backup menu in TWRP. Select system, data, and boot, then swipe to backup.
Sent from my Evita
timmaaa said:
What's your ultimate goal? Do you want to root your current stock ROM or install a custom ROM? Either way you need to install TWRP recovery first. I'm assuming you already have adb/fastboot installed on your PC.
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you have TWRP recovery on your phone.
If you want to root your current stock ROM you can just flash SuperSU through the install menu in TWRP recovery. You'll find a download link here:
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
If you want to install a custom ROM, just find one you like, download it, read the install instructions on the ROM thread, perform a full wipe (cache/dalvik cache/factory reset/system) through the wipe menu in TWRP, then install the ROM through the install menu in TWRP.
Before doing either of these options you should make a backup of your current setup in the backup menu in TWRP. Select system, data, and boot, then swipe to backup.
Sent from my Evita
Click to expand...
Click to collapse
tried to flash recovery ...
"error : cannot load "recovery file name" (openrecovery-twrp-2.6.0.0-evita)
though it is in the same folder of android where I put fastboot and all that stuff..
The command should be:
Code:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
Sent from my Evita
timmaaa said:
The command should be:
Code:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
Sent from my Evita
Click to expand...
Click to collapse
oh I forgot the img thing haha
thanks a lot
though now I wanna flash the venom rom (sense 5 , 4.2) and step 3 says : "Confirm the MD5 on the download page matches the MD5 of the file on your phone (ES File Explorer will show the MD5 of the file)" what does that mean ?
If you're downloading the file directly to your phone, use an app called AFV (Android File Verifier) to check the md5. After you've downloaded the ROM just copy the md5 listed on the download site, open AFV, paste the md5 into the box, click the select file button, navigate to the file then long press it and select calculate md5, hopefully it'll say success. If it says anything other than success the download is corrupt.
Sent from my Evita
timmaaa said:
If you're downloading the file directly to your phone, use an app called AFV (Android File Verifier) to check the md5. After you've downloaded the ROM just copy the md5 listed on the download site, open AFV, paste the md5 into the box, click the select file button, navigate to the file then long press it and select calculate md5, hopefully it'll say success. If it says anything other than success the download is corrupt.
Sent from my Evita
Click to expand...
Click to collapse
oh ok thanks alot you are smart you know ?? extremely helpful and nice to have you around the thread
madshark2009 said:
oh ok thanks alot you are smart you know ?? extremely helpful and nice to have you around the thread
Click to expand...
Click to collapse
Thanks, I've just been doing this for a while. Give yourself some time and try to keep up with things and you'll gain a whole lot of knowledge too.
Sent from my Evita

[REF][LP] Galaxy S4 I9500 Modems and Bootloaders Collections [ZIP/ODIN]

Reference Thread
Samsung Galaxy S4 I9500 Lollipop Modems and Bootloaders​
Technical background
Actually, we have a dedicated thread that should host updated modems and bootloaders (for both I9500 and I9505). However, the thread was no longer updated since 2014, even the OP is never online since 2014. So, I created this thread to host all Lollipop bootloaders and modems for I9500.
Why do need we update our modem and bootloader?
As you may know, firmwares are updated often, as long as our device still get support from Samsung. Custom ROMs does the same. And often new updates are giving problems with incorrect version of your modem or bootloader (like you installed Lollipop firmware on KitKat bootloader). We need to update our modem and bootloader to ensure the maximum compatibility available and will keep us secure, everywhere (althrough we need an additional protection too).
Installation procedure
Installation via recovery (modem only):
Make sure you've installed the latest version of CWM/PhilZ/TWRP. I'd recommend TWRP.
Make sure you've done an EFS backup (just to be safe).
Reboot to Recovery mode by combination of Power+Home+Vol(+) buttons.
a. For CWM, select Install zip from sdcard.
b. For PhilZ, select Install zip then select Install zip from sdcard0 or sdcard1.
c. For TWRP, select Install.
Navigate to modem zip.
a. For CWM/PhilZ, select "Yes, instal ..."
b. For TWRP, swipe Install button.
Reboot to system.
If after installation of modem your baseband version is Unknown, restore your EFS backup.
Installation via Odin (modem and/or bootloader):
Make sure you've installed the latest version of Samsung USB Drivers on your computer.
Make sure you've done an EFS backup (just to be safe).
Reboot to Download mode by combination of Power+Home+Vol(-) buttons and proceed by pressing Vol(+).
Plug your phone to your computer.
Extract the archive (if compressed).
Open Odin and select modem and/or bootloader .tar or .tar.md5 file(s) into the corresponding location.
Select Start to proceed.
In case if your modem and/or bootloader isn't updated, repeat step 3-6, untick Auto Reboot, and select Start to proceed. Then, do a hard reboot by holding power button for 10 seconds.
If after installation of modem your baseband version is Unknown, restore your EFS backup.
How to contribute
You're welcome to send your contribution. Make sure that version you want to contribute isn't listed on this thread. You need two files: modem.bin and sboot.bin. You could obtain by extracting both files from stock firmware .tar.md5 using 7-Zip on Windows or Archive Manager on Ubuntu (remove .md5 extension first).
Packing into .tar file(s) (modem and/or bootloader):
You need an Ubuntu-installed machine or any distribution based on Ubuntu installed on your machine.
Move both files into your working directory.
Open Terminal and move it into your working directory. Example, if you're working on Desktop folder, enter this command:
Code:
$ cd Desktop
Pack one by one files using these commands:
Code:
$ tar -h ustar -c modem.bin > MODEMVER.tar [COLOR=Green]# Modem[/COLOR]
$ tar -h ustar -c sboot.bin > BOOTLOADERVER.tar [COLOR=Green]# Bootloader[/COLOR]
Replace MODEMVER.tar and/or BOOTLOADERVER.tar with version you're packing. Example, if you're packing I9500UBUHOK1 modem, change MODEMVER.tar to I9500UBUHOK1-MODEM.tar.
Add md5 checksum into .tar file(s) using this command:
Code:
$ md5sum -t PACKAGE.tar >> PACKAGE.tar
Replace PACKAGE.tar with .tar file(s) you've created. If you've more than one .tar file, insert one first and repeat this for another one.
Finally, rename file(s) using this command:
Code:
$ mv PACKAGE.tar PACKAGE.tar.md5
Replace PACKAGE with .tar file(s) you've created (without .tar extension).
Compress it into zip file(s) then attach it here or upload to somewhere else.
If you're a bit lazy to do all these steps above, grab any Odin flashable .tar files, delete everything and replace it with modem.bin or sboot.bin then rename it.
Packing into .zip file (modem only):
Download the attached template below.
Open it with any archiver app.
Put modem.bin inside modem folder.
Rename the .zip file to the version you've included.
Attach it here or upload it somewhere else.
This list is incomplete. Help me to complete this list by contributing.
Note: Sorted by the changelist number.
Latest:
UBUHPB2 (Latin America)
Changelist number: 7068753
Download: Modem Zip - Odin | Bootloader
UBUHOK2 (Latin America)
Modem version: UBUHOK1
Changelist number: 6332925
Download: Modem Zip
XXUHPB3 (Middle East and Africa)
Modem version: XXUHPB1
Changelist number: 6164126
Download: Modem Zip - Odin | Bootloader
XXUHOC6 (South East Asia)
Modem version: DXUHOA1
Changelist number: 3943544
Download: Modem Zip
Thread closed at OP's request.

Rooted MHA-L29C567B183 Flashable

Is there anyway to flash a full ROM already rooted older version for this model?
This would remove the step to return to factory initial condition to take the upgrade? (I know the device is young, but some established phones this is the way to do it if bootloader and modem is up to date) so the first question is possible to create such a ROM and post?
You could use https://forum.xda-developers.com/android/help/extract-dat-marshmallow-lollipop-easily-t3334117
extract system.img from update.app, unpack system.img using Imgextractor.exe.
Unpack boot.img from update.app.
Extract boot.img using Android Image Kitchen.
Preroot ramdisk.
Make a flashable zip from extracted system.img and boot.img. Set up permissions, copy files..., etc in updater-script. Make the script flash boot.img.
Done. (In theory, I've not built a rom for any Huawei device yet.)
But to answer your question: Yes.
Just look at the KangVIP roms over in Development. You could just build a stock rom with root.
Edit: Imgextractor actually saves permissions to a file.
Edit 2: You could just flash the newer boot.img in TWRP and root it there, then extract boot image using dd and include that in your rom.
OR use su in /system/bin/
Edit 3: Any rom makers here? Would VENDOR and PRODUCT need to be extracted and flashed as well? (Assuming you're on a pre B183 C567 stock rom)
Nevermind, system.img is unextractable :/
Or the tool I use is not compatible with android N.
That would be awesome I'm stuck on c636 and have no way of going to c567 without paying.
Your headed in a direction, lots of us owners have been waiting for...
Sent from my MHA-L29 using Tapatalk
Benefits of 567 over 636?

Need boot.img FRD-L09 B404

Hello everyone.
I unlocked a bootloader in my freshly bought Honor 8 last week and I the first thing I did was to flash a root package (obviously). I'm used to SuperSU, so tha's what I flashed. Then I found out about Magisk. I want to try it, but I need to flash stock boot.img in order to install it. My build number is FRD-L09C432B404 (EMUI 5.0, Android 7.0). Could anyone upload corresponding boot img? I'd be thankful.
Do it yourself! ^^
Wagierek said:
Hello everyone.
I unlocked a bootloader in my freshly bought Honor 8 last week and I the first thing I did was to flash a root package (obviously). I'm used to SuperSU, so tha's what I flashed. Then I found out about Magisk. I want to try it, but I need to flash stock boot.img in order to install it. My build number is FRD-L09C432B404 (EMUI 5.0, Android 7.0). Could anyone upload corresponding boot img? I'd be thankful.
Click to expand...
Click to collapse
Hello!
You can do it yourself, just follow these steps:
1) Download your firmware (update.zip) from hicloud url: update.zip
2) Extract zip
3) Download "Huawei Update Extractor 0.9.9.5" (zip file): HuaweiUpdateExtractor_0.9.9.5.zip
4) Extract zip
5) Open "HuaweiUpdateExtractor.exe" extracted from previous step
6) Click on the 2 dots button and navigate to the file to add the "UPDATE.APP" file ( extracted from step 2) ), it will show you all the files like boot.img , recovery.img , recovery2.img , system.img , etc.
7) Select "BOOT.img" and right-click > "Extract Selected". Choose this destination folder: Where fastboot/adb are installed.
8) Use fastboot command to flash "BOOT.img":
Code:
fastboot flash boot BOOT.img
Hope it helps you!
I'd rather not download 1.3GB of firmware for the sake of one small boot.img which can't be bigger than 50MBs, not to mention additional software I'll use probably never again, so I'd be thankful if someone sent already extracted boot
Wagierek said:
I'd rather not download 1.3GB of firmware for the sake of one small boot.img which can't be bigger than 50MBs, not to mention additional software I'll use probably never again, so I'd be thankful if someone sent already extracted boot
Click to expand...
Click to collapse
BOOT.img file from FRD-L09C432B404 firmware: Google Drive or MEGA
( Because I have nothing more important to do tonight lol )
Thanks for your support. I had to extract it anyways for stock recovery, so here it is in case someone needed it.
https://drive.google.com/file/d/1ILYXoUvKMSsb8uLmSY2pIMvFWeBJ--9X/view?usp=sharing

Updating your P20 Pro (This can be used to restore a bricked P20 Pro)

My daily driver is AOSCP (CypherOS project) P20 pro ROM, but sometimes I flip back to stock every time there is a new Huawei P20 Pro update. Recently they released (9.0.0.213) so I removed the custom ROM and installed stock (9.0.0.213) without issues, just to see how it feels, whats new and such then jump back to custom. These steps helped me when I bricked my phone.
(Bootloader must be unlocked)
- Use at your own risk.
To jump to stock.
1) Go HERE and type in your phone model and click FIND MODEL button. Then click Filelist, copy and paste the first two links to your browser, this will download the main packages.
2) Extract the update.app file from the Update.zip file you just downloaded.
3) Use EMUI extractor application to extract the image files from the Update.app file.
4) Download Re-Flash, place all the images in the Re-Flash folder and flash as many images as you can. (This step simply puts your phone in enough working order for the update to complete)
Open the "cmd-here" file and start flashing:
Example:
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash cust cust.img
fastboot flash recovery_vbmeta.img recovery_vbmeta.img
fastboot flash kernel kernel.img
(Keep going - some will flash others won't)
5) type: Fastboot reboot, quickly unplug your phone and hold the volume up button, this will boot into EMUI recovery, now format data, format cache.
6) Now the two main packages you downloaded in step one, place those zip files in the folder called ZIPS-HERE, located in the Re-flash folder. Rename update_full_CLT-L29_hw_eu to update_all_hw
7) In the cmd-here window, type flash.bat
follow the steps.
Note:--------------------------------------------------------------------------------------------------------------
if the update fails you'll need a userdata.img, this image file isn't in most update.zip files. You can find it here.
Redo the steps again except this would be the last thing to do in step 4.
- fastboot flash userdata userdata.img
Okay, so I have CLT-L09C782, I updated it to 9.0.0.168 using the FunkyHuawei service. I opened Firmware Finder a while ago and I have seen some new versions of firmware there. Can I manually update from there?
aka.petteri said:
Okay, so I have CLT-L09C782, I updated it to 9.0.0.168 using the FunkyHuawei service. I opened Firmware Finder a while ago and I have seen some new versions of firmware there. Can I manually update from there?
Click to expand...
Click to collapse
I tried Firmware finder in the past, hadn't had any real luck with it whereas other have. So I really can't comment on it.

Categories

Resources