If I'm creating a duplicate post, I apologize. However, I am trying to find a zip of CWM Touch 6.0.2.3.
As I am creating this post, I see that there may be a recovery in other forums. Is the recovery the same across all devices? I just want to make sure I get the right one for my S3.
Thank you,
The one and only GBP.
Just made these .zips...
CWM 6.0.2.3 (SGS3 T-Mobile)
CWM 6.0.2.3 Touch (SGS3 T-Mobile)
Flash either of them in Recovery Mode.
CWM SITE
Thank you, I really appreciate your help.
So I know how to do that the next time, how did you create the zip file? When I was at the CWM site, all I could download was an IMG file.
Try using twrp its nice and user friendly if you want an alternative touch based recovery just download goo manager from the play store and give it a try can't hurt
Sent from my SGH-T999 using xda premium
HOW to create a .zip (flashable rom when new version comes out)
1. Started with older CWM .zip ROM that I knew worked in past...
2. Download Newest CWM Recovery .img file from CWM SITE...
3. Extract older CWM .zip and rename to newest Version number... example "Recovery_CWM_v6.0.2.3"
4. rename newest CWM recovery .img to "recovery.img" and copy to your extracted folder. (Write over older version)
5. Re-compress with WinRAR or 7-Zip and make sure it's .ZIP format, not .RAR or another type.
6. All done
*** All your doing is taking recovery image and updateing into newly created .zip
*** in flash mode, the Recovery option to INSTALL (or flash any zip) always reads META-INF\com\google\android\"updater-script"
the script it reads for this example is...
ui_print("Please Wait");
ui_print("Flashing recovery");
show_progress(0.200000, 10);
package_extract_file("recovery.img", "/dev/block/mmcblk0p18");
show_progress(0.100000, 0);
ui_print("Success!!!");
so you can see it 's just gonna put "recovery.img" in your "mmcblk0p18" Partition which we can see is the recovery partition.
there are many partitions like System, Data, Flexrom, Cache, Dvalk Cache, SD Card, etc...they all have same start with different ending numbers mmcblk0p18
I agree with dscott973, that TWRP v2.3.3.1 is the best RECOVERY ! I'd change to that one (my opinion)
You can do the same thing by puting TWRP image renamed to "recovery.img" in the same format as this thread example (and rename folder accordingly),
but very important, always make sure your using the same type. Make sure your using for Samsung Galaxy S3 (TMobile type).
Example : Don't mix Verizon or AT&T type (just know what your doing and label it correctly)
ktmdave7 said:
1. Started with older CWM .zip ROM that I knew worked in past...
2. Download Newest CWM Recovery .img file from
3. Extract older CWM .zip and rename to newest Version number... example "Recovery_CWM_v6.0.2.3"
4. rename newest CWM recovery .img to "recovery.img" and copy to your extracted folder. (Write over older version)
5. Re-compress with WinRAR or 7-Zip and make sure it's .ZIP format, not .RAR or another type.
6. All done
*** All your doing is taking recovery image and updateing into newly created .zip
*** in flash mode, the Recovery option to INSTALL (or flash any zip) always reads META-INF\com\google\android\"updater-script"
the script it reads for this example is...
ui_print("Please Wait");
ui_print("Flashing recovery");
show_progress(0.200000, 10);
package_extract_file("recovery.img", "/dev/block/mmcblk0p18");
show_progress(0.100000, 0);
ui_print("Success!!!");
so you can see it 's just gonna put "recovery.img" in your "mmcblk0p18" Partition which we can see is the recovery partition.
there are many partitions like System, Data, Flexrom, Cache, Dvalk Cache, SD Card, etc...they all have same start with different ending numbers mmcblk0p18
I agree with dscott973, that TWRP v2.3.3.1 is the best RECOVERY ! I'd change to that one (my opinion)
You can do the same thing by puting TWRP image renamed to "recovery.img" in the same format as this thread example (and rename folder accordingly),
but very important, always make sure your using the same type. Make sure your using for Samsung Galaxy S3 (TMobile type).
Example : Don't mix Verizon or AT&T type (just know what your doing and label it correctly)
Click to expand...
Click to collapse
Thank you for your help. I'll take a look at TWRP. I just wanted the latest recovery because I'm considering upgrading to 4.2.1. I've read that the older recoveries struggle with the new file system, due to multiple users.
Merry Christmas
GBP85 said:
Thank you for your help. I'll take a look at TWRP. I just wanted the latest recovery because I'm considering upgrading to 4.2.1. I've read that the older recoveries struggle with the new file system, due to multiple users.
Merry Christmas
Click to expand...
Click to collapse
^So true, found that out the hard way... :silly:
ok. new noob here. so i have downloaded the file to root and install cwm on my gs3 from rootgalaxys3.com. the cwm in it won't allow me to flash a new rom. 'assert failed' is the only thing that keeps showing up. i looked into it and i think i have to upgrade my cwm version. so i found this link to the touch version for the galaxy s3. after i download it and i go to throw it in to the PDA slot in odin. its not there. so i extract it and i find 'meta-inf' file and a "recover.img" i can end up putting that in to the pda slot. BUT it ends in .img... is this ok or does the file have to end in .tar to flash properly and work?
PLEASE HELP ME!!!!
justinjrdawson said:
ok. new noob here. so i have downloaded the file to root and install cwm on my gs3 from rootgalaxys3.com. the cwm in it won't allow me to flash a new rom. 'assert failed' is the only thing that keeps showing up. i looked into it and i think i have to upgrade my cwm version. so i found this link to the touch version for the galaxy s3. after i download it and i go to throw it in to the PDA slot in odin. its not there. so i extract it and i find 'meta-inf' file and a "recover.img" i can end up putting that in to the pda slot. BUT it ends in .img... is this ok or does the file have to end in .tar to flash properly and work?
PLEASE HELP ME!!!!
Click to expand...
Click to collapse
Download ROM manager for cwm or goo manager for twrp and flash recovery from app in goo manager hit the menu button and flash recovery script. I dont know how to do it off hand in ROM manager but it is in there
Sent from my SGH-T999 using xda premium
The 2 files I posted earlier here are for FLASHING in RECOVERY only, not made for ODIN install.
another separate way to install Recovery is...
A) Download app from Market called "Terminal Emulator" (it's like using ADB commands on cell phone instead of PC).
B) use the same "recovery.img" from either of my 2 Zips earlier posted and then copied it to External SDCard (name of .img file has to match same name as in text below)
C) Run Terminal Emulator and enter these 2 command lines (Cell has to be ROOTED for su permissions to work)
su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
D) Check to make sure you have Recovery.
-with cell being off, Use {Volume Down, Home, Power} to load up recovery and check it.
To directly answer the question, you can only flash .tar files with Odin.
ktmdave7 said:
CWM 6.0.2.3 (SGS3 T-Mobile)
CWM 6.0.2.3 Touch (SGS3 T-Mobile)
Flash either of them in Recovery Mode.
CWM SITE
Click to expand...
Click to collapse
Seriuosly... just attach things like this.. They are small enough. Especially since you chose to use a stupid file hosting site that tells you to register for a free account but doesnt even give that option.
ktmdave7 said:
CWM 6.0.2.3 (SGS3 T-Mobile)
CWM 6.0.2.3 Touch (SGS3 T-Mobile)
Flash either of them in Recovery Mode.
CWM SITE
Click to expand...
Click to collapse
/
Useless, i cant even create a free basic account, could you unload it somewhere else please?
Here you go: http://db.tt/okfh9vzU
ktmdave7 said:
The 2 files I posted earlier here are for FLASHING in RECOVERY only, not made for ODIN install.
another separate way to install Recovery is...
A) Download app from Market called "Terminal Emulator" (it's like using ADB commands on cell phone instead of PC).
B) use the same "recovery.img" from either of my 2 Zips earlier posted and then copied it to External SDCard (name of .img file has to match same name as in text below)
C) Run Terminal Emulator and enter these 2 command lines (Cell has to be ROOTED for su permissions to work)
su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
D) Check to make sure you have Recovery.
-with cell being off, Use {Volume Down, Home, Power} to load up recovery and check it.
Click to expand...
Click to collapse
Don't you mean Volume Up, Home, Power for Recovery?
Can someone reload these links? I need them badly thanks
Related
**PLEASE NOTE, I AM IN NO WAY AFFILIATED WITH CWM RECOVERY. THIS THREAD IS FOR DISCUSSION/TROUBLE SHOOTING/GENERAL INFO ON CWM TOUCH AND CWM RECOVERY FOR THE SPRINT VARIANT ONLY**
Special thanks to koush, TeamEpic and everyone else involved in making CWM Recovery for our phones. Also thanks to reinbeau for allowing me to start a CWM Thread for Sprint SGSIII specifically
**WARNING: ANYONE USING TEAMEPIC'S DUALBOOT FAKE CWM RECOVERY ARE ADVISED NOT TO USE RECOVERIES IN THIS THREAD! PLEASE REFFER TO THEIR THREAD HERE**
CWM RECOVERY AND CWM TOUCH RECOVERY FOR SPRINT SGSIII (d2spr)
DOWNLOADS FOR ALL RECOVERY IMAGES CAN BE FOUND HERE
-Scroll towards the bottom for latest releases. Our device (Sprint SGSIII) is labeled as d2spr
HOW TO INSTALL?
METHOD 1
-Use adb shell or Terminal Emulator (on device)(Must be rooted)
-Download CWM Recovery and place it on the root of your internal storage and rename it to "recovery.img" (without the quotes)
-In adb shell or terminal emulator enter the following commands:
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
reboot recovery
METHOD 2
-Use Mobile Odin
-Download CWM Recovery, rename it to recovery.img and place on root of internal storage
-Open Mobile Odin (may start downloading neccessary files for our device)
-Select "Open File", then select "Internal SD-Card"
-The recovery.img should be listed at the very top. Select it
-In the main menu the only Partition that should be selected is Recovery
-Scroll Down and Select Flash Firmware (after it flashes you may be automatially rebooted into recovery)
METHOD 3
-Use CWM Manager App (**ONLY NON TOUCH RECOVERY IS FREE IF YOU USE THIS METHOD)
-Download and install CWM Manager
-Open the app and select Install CWM Recovery
-Let it install. After installation completes reboot into recovery and see if it works
METHOD 4
-This is a .tar.md5 file I made for CWM TOUCH RECOVERY 6.0.1.2 (I tested it personally, it works)
-DOWNLOAD THE recovery.tar.md5 (md5 checksum: 421b6b467a304532fb19a35d960678bf)
-Open up Odin on your desktop (If using Mobile Odin, Follow same instructions as METHOD 2 except you don't rename it)
-Make sure USB Debugging IS enabled on your device and go into download mode
-once in Download Mode make sure Odin recognizes your device (should be a blue box that says COM then a number)
-In the PDA Slot navigate to wherever you saved the recovery.tar.md5 and select it (again, for the PDA Slot)
-Once selected, make sure Auto Reset and F-Reset Time are the only things checked
-Select Start
-If the installation goes right you should get a PASS! message in Odin
Latest Direct Downloads as of 8-28-12
Direct Downloads of CWM Recovery (Sprint SGSIII Only)(Latest Downloads As Of 8-28-12)
The .img's must be flashed with adb, terminal emulator, or Mobile Odin.
CWM TOUCH
recovery-clockwork-touch-6.0.1.2-d2spr.img
CWM (Regular)
recovery-clockwork-6.0.1.2-d2spr.img
BUGS:
-Incorrect time stamp on backups
-Cannot mount Internal Storage from Recovery
-Cannot create backup's using the option in ROM Manager
How to Make a recovery.tar.md5
This is a guide on how to make a .tar.md5 file to be flashed through Odin or Mobile Odin. These are good to have on hand. If you end up unrooting your phone but re root. Instead of using Odin to flash a CWM Recovery that's outdated you can make one yourself using this process, then flash it using Odin so you can boot into recovery and flash a Root from Recovery zip
I used this guide, I'll just try to expand it and make it a little more simpler for cygwin (Windows) users
1) Navigate to your cygwin directory (ex: C:\cygwin) and go to C:\YOUR_CYGWIN_DIRCECTORY\home\Owner\ and create a folder, name it to whatever you'd like (ex: recovery_odin)
2) Download your CWM recovery image and rename it to recovery.img. Place it in the folder you created in cygwin (for the rest of the guide I'll refeer to this folder as recovery_odin)
3) Double click on your cygwin.bat and type this:
Code:
cd recovery_odin
4) Enter the following commands:
Code:
$ tar -H ustar -c recovery.img > recovery.tar
$ md5sum -t recovery.tar >> recovery.tar
$ mv recovery.tar recovery.tar.md5
5) Inside your recovery_odin folder you'll find your recovery.tar.md5, flash that using Odin (PDA Slot). If you want full root acess you need to flash the Root from Recovery zip immediately after flashing your new recovery. So, in Odin prior to flashing your recovery.tar.img, make sure Auto Reboot option is not checked and you pull the battery out after your recovery successfully flashed so you can enter CWM Recovery and flash that zip (make sure the zip is on your Internal SD prior to flashing the recovery)
woOT!!! First again!
Used the adb method earlier on my own to push the CWM Touch recovery, worked as it should.
Sent from my E4GT packed full of "The Goodness" of TNz Blend ICS on Tapatalk 2 the SGS3 is charging
NICE!!!
Sent from my SPH-L710 using Tapatalk 2
I hope this will cut down on the confusion. I think every variant ha# a CWM Recovery thread in their respective dev sections. I'm leaving right now but when I get back I'll finish the rest of the posts
Sent from my SPH-L710 using xda premium
I suppose this will suffice, till I get my TWRP fix. <3 Thank you.
I used the mobile Odin method earlier today. Worked great!
Sent from my Samsung Galaxy SIII using Tapatalk
I used method 5, I love Rom Manager.
But when backing up rom from rom manager,
it goes to recovery and starts and quickly aborts with error.
It will not do a nandroid, I tried many times.
But if I do a backup directly from recovery clockwork it works
fine other than names with the year 1970. Why doesn't Rom Manager
work, and I have latest version and installed sprint GS3 right from it.
Nice conflation of goodies on this thread
CM9'rs running off Epic CM Team's temp kexec 'dual-boot / red Fake CWM' have been advised NOT to use ROM Manager (ie, to obtain CWM Touch or Nightly updates etc.)......... could bode badly.
sonarchist said:
Nice conflation of goodies on this thread
CM9'rs running off Epic CM Team's temp kexec 'dual-boot / red Fake CWM' have been advised NOT to use ROM Manager (ie, to obtain CWM Touch or Nightly updates etc.)......... could bode badly.
Click to expand...
Click to collapse
Thank you I will post a warning when I'm home
Sent from my SPH-L710 using xda premium
Where are the cm9 nightlies for sprint. I see no thread about it here in the Dec forum?
Sent from my SPH-L710 using Tapatalk 2
ladle3000 said:
Where are the cm9 nightlies for sprint. I see no thread about it here in the Dec forum?
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
You can find those here
fergie716 said:
You can find those here
Click to expand...
Click to collapse
How'd you find these. They don't show in the dev forum for me
Sent from my SPH-L710 using Tapatalk 2
ladle3000 said:
How'd you find these. They don't show in the dev forum for me
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
I'm assuming your on Tapatalk, go to all Forums, Scroll to the very bottom and look for the SGSIII threads, then Sprint Original Development
So if I am already rooted and have the non touch cwm recovery installed I can just not into recovery and flash the touch version?
Sent from my SPH-L710 using Tapatalk 2
JuggZaPoppiN said:
So if I am already rooted and have the non touch cwm recovery installed I can just not into recovery and flash the touch version?
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
yea grab the zip file in the second post and flash it. I've read some ppl having issues with it not sticking after a reboot so I would recommend either using adb or mobile odin, both of those have worked for me. I personally haven't used the zip's CWM published
In fact I removed the links to the CWM zips. I haven't tested those so I can't vouch for them
Use the CWM Images (direct Links in post#2), or use the .tar.md5 file I provided in Method 4 and use those.
fergie716 said:
In fact I removed the links to the CWM zips. I haven't tested those so I can't vouch for them
Use the CWM Images (direct Links in post#2), or use the .tar.md5 file I provided in Method 4 and use those.
Click to expand...
Click to collapse
The zips "work" but they do not "stick"....the IMG file does make recovery stick though...just my 2 cents...
I've seen a lot of people asking about getting the most recent version of getting this flashed on their device.
Here is how I did it (These steps are best taken directly on the phone itself to eliminate the need to transfer files to your device):
1] Download the *.img from clockworkmod's site: CWM Touch 6 image file
2] Download Mobile Odin Lite and the appropriate flash-kernal for i747... for your convenience, here are direct links, though it wouldn't hurt to look at the post and/or buy the full version to support Chainfire-san;
Mobile ODIN Pro
Mobile ODIN Lite
Flash-Kernal for i747
And of course, install the APKs.
3] Open the Mobile ODIN app, and choose "Choose File...". It should be at the bottom of the list of flashable selections.
Select the Clockwork recovery image that you downloaded in step 1 to your phone.
Selecting the CWM Touch*.img file should automatically place it into the recovery slot.
(NOTE: I renamed this *.img file to "recovery.img", I'm not a hacker genius or anything so I'm not sure if this made a difference)
4] Choose "Flash" near the bottom(bottom of selectable options for LITE) and it will almost instantly reboot your phone, normally.
Thats about it.
Reboot into recovery and CWM Touch 6 should be installed.
Worse comes to worse, this doesn't work?
Re-flash recovery via ODIN on a computer if it is unsuccessful.
Keep in mind you are flashing this of your own accord.
What worked for me may not work out for you, so as always, please don't hold me responsible.
Marble White Samsung Galaxy S III;
Running AOKP JB build 9/30 && Ktoonsez KT747 kernal 9/23 && Modem version i747UCLH9
There's already threads for this and you posted completely in the wrong section.
Hi, I've download some files to upgrade my xperia s from "Xperia S Android Development"
After unzip the files, it become two directory files called... "META-INF", "System"
I'm wondering how to set it up those files to my phone???
Please advise and help~~~ thanks!!!
you dont need to extract the files you need to flash it in the cwm.
click my signature "Read ME" , its best to read it.
Quick idea of what to do (it's better to follow a full tutorial though):
- Unlock bootloader ( unlockbootloader.sonymobile.com )
- Put ZIP in the main folder of your phone SDcard (both kernel & firmware/rom image, so 2 ZIPs)
- Get fastboot files for your PC, flash to a CWM image
- Follow a CWM tutorial on how to flash the kernel & firmware
chieh9899 said:
Hi, I've download some files to upgrade my xperia s from "Xperia S Android Development"
After unzip the files, it become two directory files called... "META-INF", "System"
I'm wondering how to set it up those files to my phone???
Please advise and help~~~ thanks!!!
Click to expand...
Click to collapse
1- Unlock the boot loader from sony website.
2- Install CWM recovery
3- copy the rom on the hard drive of the phone
4- open CWM and choose boot in recovery
5- Using the volume buttons choose install zip from sdcard (using the camera button) then go to the directory where you copied the rom and choose it
6- Installation will start and enjoy
P.S: I do recommend NOVA-rom RC2 and the NOVA kernel 1.1.1, very smooth and stable
Hope I helped
i have a old version of cwm i want 2 update cwm .. can some one make a step by step?
iam not a total noob but i dont wanne brick my note 2 haha..
iam now on miui
DLK7
Use mobile odin to flash cwm img file.
Download it and rename it to recovery.img
I recommend using twrp.
Sent From Samsung's Galaxy Note II Using Internet
UtkarshGupta said:
Use mobile odin to flash cwm img file.
Download it and rename it to recovery.img
I recommend using twrp.
Sent From Samsung's Galaxy Note II Using Internet
Click to expand...
Click to collapse
so i download the odin app... then i must download the tar file?
and then done?
thx anyway ^^ the app looks great
download recovery from here[url]
download the one that says " Samsung Galaxy Note 2 (HSPA+) "
what you are gonna get is an *.img file whatever it's name is.
rename it to recovery.img
push it to your phone preferably to the root of internal sd card
open mobile odin
tap recovery
select internal sd card
locate your file.
now odin should say something like - " /sdcard/recovery.img " or wherever your file was located.
don't touch anything else
just scroll down and hit the flash firmware button.
and in 3..2..1.. your phone will BBBLLLAAASSSTTT
into recovery
imao use twrp - [URL="http://goo.im/devs/OpenRecovery/n7100"]download from here
scroll down and download the one in img format and follow the same steps.
current version as of time of posting this
cwm - 6.0.1.9
twrp - 2.3.3.1
only use the latest version
UtkarshGupta said:
download recovery from here[url]
download the one that says " Samsung Galaxy Note 2 (HSPA+) "
what you are gonna get is an *.img file whatever it's name is.
rename it to recovery.img
push it to your phone preferably to the root of internal sd card
open mobile odin
tap recovery
select internal sd card
locate your file.
now odin should say something like - " /sdcard/recovery.img " or wherever your file was located.
don't touch anything else
just scroll down and hit the flash firmware button.
and in 3..2..1.. your phone will BBBLLLAAASSSTTT
into recovery
imao use twrp - [URL="http://goo.im/devs/OpenRecovery/n7100"]download from here
scroll down and download the one in img format and follow the same steps.
current version as of time of posting this
cwm - 6.0.1.9
twrp - 2.3.3.1
only use the latest version
Click to expand...
Click to collapse
woooww many thanks !!! when iam home i gonne try it
edit:
it wooorrkks greaat
I've noticed that many in this forum for the Honor 7x / Mate SE want to try a few ROMS, and then eventually go back to stock - Some just want to go back to stock. I had my own issues and thankfully there were others to help along the way. This method does not use fastboot to flash partitions, it uses TWRP, so the assumption is you have a working TWRP. Also I am not responsible for any bricks, I am just explaining what I did to get back to stock (And based on all the issues people are having, I'm staying there)
If you've tried a Treble ROM or others, the route I took to get back to stock was as follows:
1.) Download your firmware from Firmware finder or the Pro-TeamMT website:
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-l34&firmware_page=0
In this example, mine is the Mate SE..
You should have downloaded 3 files. The important one we want right now is the Update.zip - Extract this file. You should see UPDATE.APP within this folder.
2.) Download the Huawei extractor software by worstenbrood:
https://forum.xda-developers.com/showthread.php?t=2433454
3.) Use this software to extract the files from the Update.App - You may need to disable the Checksum checks under "Settings". When you select the UPDATE.APP file, you should get a list of the files that are compiled or compressed into the app. The main 4 files you want are Ramdisk, Vendor, System, and if you'd like the Stock recovery (Recovey_Ramdisk). Copy these files to your SD card.
4.) Assuming you still have the functioning TWRP, reboot into TWRP and wipe everything but the SD card.
5.) Flash the images to the appropriate partition, Ramdisk = Ramdisk, Vendor = Vendor Image, and System = System Image - Ensure you're flashing the image partitions. Ramdisk is necessary if you've ever rooted or used Magisk.
At this point you should be able to reboot and get back into stock...But you'll notice Themes do not work properly..That's because you've wiped / formatted data at some point in TWRP, and now the Data/hw_int has been wiped. You can fix this by flashing the update on top of itself by the instructions in this thread (Thanks to mrmazak):
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
See the "Flash update while on Oreo"...This has worked twice now to get me back my themes after wiping /data.
I counted on my TWRP backup to get me back to stock after trying a Treble ROM, and I ended up bricked. So hopefully this helps someone!
PS, if anyone has more to add this this, the more help the better.
Wait, wouldn't the recovery be the file "RECOVERY_RAMDIS.img"
???
crayonicle said:
Wait, wouldn't the recovery be the file "RECOVERY_RAMDIS.img"
???
Click to expand...
Click to collapse
You are correct...That is the name of the actual image in the UPDATE.APP, but I was basing the name off of the actual partition.
Corrections, please add to original post
smokinjoe2122 said:
You are correct...That is the name of the actual image in the UPDATE.APP, but I was basing the name off of the actual partition.
Click to expand...
Click to collapse
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
crayonicle said:
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
Click to expand...
Click to collapse
System image can fail too...that's why I said to flash everything in TWRP...Plus, flashing the update on-top of itself will not only give you theming back, but stock recovery.
crayonicle said:
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
Click to expand...
Click to collapse
Is this working ? Did you try ? I'm on RR ROM and couldn't get adb recognize my device. This is my only hope to return to stock as of now.
Adithya Krishnakumar said:
Is this working ? Did you try ? I'm on RR ROM and couldn't get adb recognize my device. This is my only hope to return to stock as of now.
Click to expand...
Click to collapse
Yes, I tried it. It works flawlessly.
How can I get themes to work? I don't understand the original post, it makes no sense when explaining how to get themes to work properly. I do not know what to do with the link provided in the original post.
crayonicle said:
How can I get themes to work? I don't understand the original post, it makes no sense when explaining how to get themes to work properly. I do not know what to do with the link provided in the original post.
Click to expand...
Click to collapse
What part are you stuck on?
Essentially mrmazak created a flashable file that will take the 3 firmware files you download and flash them on top of your current firmware. This is helpful for doing an update or just reloading the firmware completely (Which is what you're trying to do)...
I'd follow the exact instructions that he's put out on that thread, but the 10,000 ft overview:
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
1.) Download files from link for your device
2.) Create a correctly named folder on your SD card, along with those files properly named in that folder (Ensure these files are named properly also.)
3.) Ensure you have the stock recovery on the SD card also.
4.) Copy the "xxx_Update.zip" he created onto your SD
5.) Flash the "xxx_Update.zip"...It will will flash the stock recovery, then boot into update mode and update with the 3 files you downloaded and put into that folder. This will basically "reflash" the firmware and give you back themes.
I would go step by step on his action list and follow them to a "T". I've verified it works perfectly. He also has a "Basic-Instructions" write up in the zip also.
My device build number was BND-L21C185, I bricked my device once but I managed to get it back. Since then I have strange build number which is system 8.0.0.046(063f). Does this method fix it?
This info helped me bring my phone back to life,thank you sir for the step by step instructions.
Found a way to get back to stock without all this hassle lol
So I thought this was the only way to get back to stock... turns out there is a much easier way
This method also enables themes, I checked myself.
https://forum.xda-developers.com/honor-7x/how-to/getting-to-stock-emui-super-easily-t3804722
Is it possible to flash all of the partitions from fastboot?
I have the BND-L34 and I am unsure as to what happened.
I have been running the RROS surdu_petru posted for about 3 weeks now and it was running fine.
2 days ago I grab my phone and it was booted into error mode. Now when I try to boot into twrp I get an error code for my recovery. When I try to boot into the system it throws a different error code for boot image.
I have a twrp backup stored on an sd card, and all 3 OTA's I saved back during the June update. I have the Pro-TeamMT app on my pc and have found/extracted every file for the brick method only get the same errors, 1 right after the other.
I am no noob, (although I am not a Senior Member with a giant banner either ) but I have been rooting android devices going on 8 years now, and have never completely bricked any of them.
My last 2 phones were Oneplus 1 and Oneplus 3, so I am familiar with flashing all the partitions using fastboot. But with those phones there were about 9 different individual flashes that needed to be done in a particular order.
Any help or advice would be greatly appreciated.