Develop Bugs

[RECOVERY][INFO] CWM + CWM TOUCH RECOVERY FOR SPRINT SGSIII (d2spr)

**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...

[Q] Is there a zip of CWM Touch 6.0.2.3?

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

I can't install CWM or TWRP on Note II

Hello!
First of all: Excuse me for my english.
I have a "second-hand" Galaxy Note II. I think that the old user try to root it, because I have superuser installed... but I can't grant su permissions.
Well. I try to install CWM or TWRP with heimdall in Download mode: heimdall flash --RECOVERY recovery.img (CWM or TWRP), it seems works fine, and phone restarts. But when I try to access on it I get the (default) Android System Recovery.
I read that it's because I have to delete /system/recovery-from-boot.p to CWM or TWRP can be executed successfully, but I can delete it because I'm not root, and I can't be root because i can't install CWM or TWRP...
- It's possible to be root without CWM or TWRP? (I tryed without exit: towelroot or framaroot)
- It's possible to delete /system/recovery-from-boot.p without be root user? (I tryed adb shell, ES File Explorer, ...)
- It's possible to access CWM or TWRP without delete this file? (I tryed with CWManager, it detects CWM and TWRP flashed, but can't reboot on it, and can't install a new CWM version).
I'm become to be crazy, I suppose that's more easy that I think...
Thank you very much!

Firt... installing custom recovery is very important to flash the right one for your specific model.
What exact model do you have of your phone? Can you download Phone info and give the info there: http://forum.xda-developers.com/showthread.php?t=2609045 or https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en
What Phone Model: ....and Device Type:
When you install TWRP or CWM, it has to be specific for your phone model and device type.

cyberboob said:
Firt... installing custom recovery is very important to flash the right one for your specific model.
What exact model do you have of your phone? Can you download Phone info and give the info there: http://forum.xda-developers.com/showthread.php?t=2609045 or https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en
What Phone Model: ....and Device Type:
When you install TWRP or CWM, it has to be specific for your phone model and device type.
Click to expand...
Click to collapse
Thank you very much for your Reply. I'm installing the recovery for my specific model: GT-N7100, and it was installed succesfully, but when reboot, appears the default Android Bootloader.
Thank you very much!
PS: I'm Android developer and I installed other roms a lot of times in another devices, but I don't have a lot of experience rooting devices (and it's the first Samsung that I try to root), and I think that the first phone owner do something wrong...

I finally solve it installing the stock ROM from sammobile and flashing it with heimdall:
sudo heimdall flash --CACHE cache.img \
--BOOT boot.img \
--SYSTEM system.img \
--RECOVERY recovery.img \
--RADIO modem.bin \
--HIDDEN hidden.img \
--BOOTLOADER sboot.bin \
--TZSW tz.img
Thank you very much!

lol we actually learn a lot more from our mistakes. In the end, you got everything working fine again, so that's all that matters.
Enjoy!

cyberboob said:
lol we actually learn a lot more from our mistakes. In the end, you got everything working fine again, so that's all that matters.
Enjoy!
Click to expand...
Click to collapse
Yes!! But yesterday I was about to be crazy...
Thank you!!

Cyanogen 12 (Lollipop) to Cyanogen 11 (Kitkat)

IT IS POSSSSIIIIIBBBBLLLLLE!​
I am rewriting this tutorial from RDS www.yuplaygod.com member's post
This is only meant for users who had rooted their device, in lollipop, have cwm or twrp recovery installed. IF not rooted find guides for it. (Hint: Google it)
I suggest to not use fastboot for flashing roms... It may brick you device (I meant hard brick)
So here is what we are going to do!
STEPS (VERY SIMPLE)
1) Download Back_to_cm11-signed by Abhiram.zip https://drive.google.com/file/d/0B4etFrzyEA01UklKR3N5T2JYeGc/view?usp=sharing
2)Download recovery-yu.img https://drive.google.com/file/d/0B4etFrzyEA01d2VGRXNuY2I1MGs/view?usp=sharing
3)Copy Back_to_cm11-signed by Abhiram.zip to SDCARD
4)Open recovery and flash it
5)Open fastboot mode.
6)Connect to your computer and flash recovery-yu.img
7)Open recovery by pressing "vol+"+"vol-"+"pwr"
8)Flash stock rom zip. Go to this guide to get it http://forum.xda-developers.com/yureka/orig-development/rom-t3042384
9) Rock with it!.
********FOR THOSE WHO ARE NOT GOOD WITH FASTBOOT**********
So yureka is something different. So you have to specify the device id for the fastboot to find it.
Install adb-setup.1****.exe https://drive.google.com/file/d/0B4etFrzyEA01SE9NTVNRWTl4Y0E/view?usp=sharing
Open CMD
Type fastboot -i 0x1ebf devices
If any device is detected you r good to go
Close CMD
Open the place where you have downloaded recovery-yu.img
By pressing shift, right click the folder (in which you have downloaded recovery-yu.img) click open command window here
and type fastboot -i 0x1ebf boot recovery-yu.img
That's it

Have you tried that and didn't face any hardbricks?

Yes
I risked my own device to prove that. Go ahead 10000% sure that this will work. Because my device did not brick at all
Please hit tanks if you got it working! It is working..

Abhiram Shibu said:
I risked my own device to prove that. Go ahead 10000% sure that this will work. Because my device did not brick at all
Please hit tanks if you got it working! It is working..
Click to expand...
Click to collapse
tank you

The OP suggest not to use fastboot mode as it may hard brick device & the steps tht follow are based on fastboot option... I'm confused, Is it safe to use fastboot mode thn?

ujilraj their is nothing to be confused. You can use fastboot mode. But if you flash system.img and data.img via fastboot, which has different partition styles, then you will end up with hard bricked phone... That's why!
Flashing recovery is very safe! GO for it!
I have tested it

For further clarification i'm asking this, pardon me...
First i boot into CM12 recovery & flash Back_to_cm11-signed by Abhiram.zip
Then,
Enter fastboot mode & install recovery-yu.img tht belongs to CM11.
Then,
I boot into CM11 recovery & flash any CM11 rom... Rite???

A bit confuse
Abhiram Shibu said:
I suggest to not use fastboot for flashing roms... It may brick you device (I meant hard brick)
That's it
Click to expand...
Click to collapse
I am a bit confuse here. Could you explain to me what is the different between:
Code:
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("firmware-update/sbl1.mbn", "/dev/block/bootdevice/by-name/sbl1");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
AND
Code:
fastboot -i 0x1ebf flash tz tz.mbn
fastboot -i 0x1ebf flash hyp hyp.mbn
fastboot -i 0x1ebf flash sbl1 sbl1.mbn
fastboot -i 0x1ebf flash rpm rpm.mbn
fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
fastboot -i 0x1ebf flash modem NON-HLOS.bin

ujilraj said:
For further clarification i'm asking this, pardon me...
First i boot into CM12 recovery & flash Back_to_cm11-signed by Abhiram.zip
Then,
Enter fastboot mode & install recovery-yu.img tht belongs to CM11.
Then,
I boot into CM11 recovery & flash any CM11 rom... Rite???
Click to expand...
Click to collapse
Ujilraj That is absolutely correct ! You got it man.:good:

tirta.agung said:
I am a bit confuse here. Could you explain to me what is the different between:
Code:
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("firmware-update/sbl1.mbn", "/dev/block/bootdevice/by-name/sbl1");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
AND
Code:
fastboot -i 0x1ebf flash tz tz.mbn
fastboot -i 0x1ebf flash hyp hyp.mbn
fastboot -i 0x1ebf flash sbl1 sbl1.mbn
fastboot -i 0x1ebf flash rpm rpm.mbn
fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
fastboot -i 0x1ebf flash modem NON-HLOS.bin
Click to expand...
Click to collapse
That is good question, I appreciate that.​
So.... I got to say is that. When you use "fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn " This will format the desired partition and put files there. If the partition table is modified then more likely it would not flash but erase the whole partion. That will lead to a hard bricked phone. The procedure you told will work.
But zip just copies these files to that location..... Sounds great, i think.
IN my opinion ONLY FASTBOOT CAN CAUSE HARD BRICK which is the greatest issue faced by yureka users.
If you managed to flash a 32bit rom in recovery without flashing the zip I have given you, the chances are you end up into a boot loop or Soft Brick. But do the same with fastboot you will end up with Hard bricked phone!
Zip method is always safe. I mean the safest!
Flashing recovery via fast boot don't cause anu Hard Bricks. I tried in my phone, i ended up with Soft Brick.... I repaired it by using unsafe method flashed ROM via fast boot. Luckily there was no partition mismatch. I could have flashed recovery and flashed my zip file!
So my advise please don't use fastboot. It is too dangerous for your phone ( As most of them can't even contact the customer care ) I don't want you to end up like this....
Note: Most of them flash system.img and data.img first .... don't do that... If you r so sure flash the files you mentioned first. As they contain boot loader(Priorety), Modem, Partiton Style, Touch Drivers.......
Good Luck! :good:
I hope this information helped you
Please hit thanks if I helped you in any manner!

Abhiram Shibu said:
That is good question, I appreciate that.​
So.... I got to say is that. When you use "fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn " This will format the desired partition and put files there. If the partition table is modified then more likely it would not flash but erase the whole partion. That will lead to a hard bricked phone. The procedure you told will work.
But zip just copies these files to that location..... Sounds great, i think.
IN my opinion ONLY FASTBOOT CAN CAUSE HARD BRICK which is the greatest issue faced by yureka users.
If you managed to flash a 32bit rom in recovery without flashing the zip I have given you, the chances are you end up into a boot loop or Soft Brick. But do the same with fastboot you will end up with Hard bricked phone!
Zip method is always safe. I mean the safest!
Flashing recovery via fast boot don't cause anu Hard Bricks. I tried in my phone, i ended up with Soft Brick.... I repaired it by using unsafe method flashed ROM via fast boot. Luckily there was no partition mismatch. I could have flashed recovery and flashed my zip file!
So my advise please don't use fastboot. It is too dangerous for your phone ( As most of them can't even contact the customer care ) I don't want you to end up like this....
Note: Most of them flash system.img and data.img first .... don't do that... If you r so sure flash the files you mentioned first. As they contain boot loader(Priorety), Modem, Partiton Style, Touch Drivers.......
Good Luck! :good:
I hope this information helped you
Please hit thanks if I helped you in any manner!
Click to expand...
Click to collapse
Rather than flashing your zip via recovery, can I not use fastboot to flash the following in the order mentioned:
modem, sbl1, aboot, rpm, tz, hyp, recovery. The files that would be used are a part of cm11 fastboot package. After flashing all of these, boot to recovery and then flash the cm11 zip. I'll be essentially doing the same like you did. But I'll be using fastboot to flash firmware specific stuff. I strongly believe that these would not cause the infamous brick.
Thanks,
Sanjay

Abhiram Shibu said:
That is good question, I appreciate that.​
So.... I got to say is that. When you use "fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn " This will format the desired partition and put files there. If the partition table is modified then more likely it would not flash but erase the whole partion. That will lead to a hard bricked phone. The procedure you told will work.
But zip just copies these files to that location..... Sounds great, i think.
IN my opinion ONLY FASTBOOT CAN CAUSE HARD BRICK which is the greatest issue faced by yureka users.
If you managed to flash a 32bit rom in recovery without flashing the zip I have given you, the chances are you end up into a boot loop or Soft Brick. But do the same with fastboot you will end up with Hard bricked phone!
Zip method is always safe. I mean the safest!
Flashing recovery via fast boot don't cause anu Hard Bricks. I tried in my phone, i ended up with Soft Brick.... I repaired it by using unsafe method flashed ROM via fast boot. Luckily there was no partition mismatch. I could have flashed recovery and flashed my zip file!
So my advise please don't use fastboot. It is too dangerous for your phone ( As most of them can't even contact the customer care ) I don't want you to end up like this....
Note: Most of them flash system.img and data.img first .... don't do that... If you r so sure flash the files you mentioned first. As they contain boot loader(Priorety), Modem, Partiton Style, Touch Drivers.......
Good Luck! :good:
I hope this information helped you
Please hit thanks if I helped you in any manner!
Click to expand...
Click to collapse
2 questions :-
1. ) As you said that do not use the fastboot method to flash kitkat rom. My question is, Can i use fastboot method to flash the lollipop 64bit zip file (that is basically the same OTA update file), using same method which was used to flash kitkat (by extracting the zip file contents to a common folder containing flash-all.bat, if u remmeber?). Basically i want to know a method to re-flash lollipop 64 bit , if any1 knows?
2.) Once i suceed to get kitkat rom back , from the lollipop 64 bit. Can i use FASTBOOT method in FUTURE flashes to flash kitkat based custom roms or should i permanently DISCONTINUE flashing through fastboot, even after getting kitkat rom back by your method?
thanks in advance .... :good:
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
Also i want to know. is there something like 32bit and 64 bit recovery. I hv heard that flashing incoatiable recovery can also lead to hard brick.
which recovery to flash when.??
could be great if any1 has positive information and can guide....

coolboyforeva said:
2 questions :-
1. ) As you said that do not use the fastboot method to flash kitkat rom. My question is, Can i use fastboot method to flash the lollipop 64bit zip file (that is basically the same OTA update file), using same method which was used to flash kitkat (by extracting the zip file contents to a common folder containing flash-all.bat, if u remmeber?). Basically i want to know a method to re-flash lollipop 64 bit , if any1 knows?
2.) Once i suceed to get kitkat rom back , from the lollipop 64 bit. Can i use FASTBOOT method in FUTURE flashes to flash kitkat based custom roms or should i permanently DISCONTINUE flashing through fastboot, even after getting kitkat rom back by your method?
thanks in advance .... :good:
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
Also i want to know. is there something like 32bit and 64 bit recovery. I hv heard that flashing incoatiable recovery can also lead to hard brick.
which recovery to flash when.??
could be great if any1 has positive information and can guide....
Click to expand...
Click to collapse
There is nothing to be confused. there are 32 bit and 64 bit recoveries. Flashing wrong recovery will only softbrick your phone. I did it ones accidentally
32bit recovery https://drive.google.com/open?id=0B4etFrzyEA01d2VGRXNuY2I1MGs&authuser=0
64bit recovery https://drive.google.com/open?id=0B4etFrzyEA01NnZBWHcxWlVHTW8&authuser=0
If you want to flash lollipop then download lollipop flash-able zip file click here for zip file
There are some good working fastboot upgrade packages. So if you have one of them ( Tried it yourself to upgrade and worked earlier) Then use that package it will work!. Flashing with zip file with recovery reduces risk!:good:

Abhiram Shibu said:
There is nothing to be confused. there are 32 bit and 64 bit recoveries. Flashing wrong recovery will only softbrick your phone. I did it ones accidentally
32bit recovery https://drive.google.com/open?id=0B4etFrzyEA01d2VGRXNuY2I1MGs&authuser=0
64bit recovery https://drive.google.com/open?id=0B4etFrzyEA01NnZBWHcxWlVHTW8&authuser=0
If you want to flash lollipop then download lollipop flash-able zip file click here for zip file
There are some good working fastboot upgrade packages. So if you have one of them ( Tried it yourself to upgrade and worked earlier) Then use that package it will work!. Flashing with zip file with recovery reduces risk!:good:
Click to expand...
Click to collapse
ok . m not gonna use fastboot. But how will i flash signed lollipop zip file on custom recovery and unlocked bootloader. it wont boot. I would need an unsigned lollipop 64 bit zip file or rather a locked bootloader + stock 64 bit recovery . Any link for stock 64 bit recovery ? is above link for stock or custom recovery?

coolboyforeva said:
ok . m not gonna use fastboot. But how will i flash signed lollipop zip file on custom recovery and unlocked bootloader. it wont boot. I would need an unsigned lollipop 64 bit zip file or rather a locked bootloader + stock 64 bit recovery . Any link for stock 64 bit recovery ? is above link for stock or custom recovery?
Click to expand...
Click to collapse
Yes it will boot.
Link above is for custom CWM recovery.
Warning ******** Boring Story Ahead*********
So i purchased my yureka from Amazon. When i got it, I unlocked boot loader, installed cwm recovery right away. When the lollipop upgrade showed up I tried to download it via system upgrade. It downloaded but wont flash because of a custom recovery. So... I downloaded a signed zip file from xda attachment which i gave you. I cleared cache and tried installing the zip file.... It actually works.
Why it worked?
Stock rom looks for signed zips and it should be signed my their developer. But custom recoveries installs any zip file which is flashable regardless they are signed or unsigned. The only thing it looks for is the scripts and device compactability.
So try flashing the lollipop signed zip file. It will surely work...
So... What will the zip file do?
It will wipe system, modem, recovery etc exept data. Resize them and copy files in.
So ... What will you end up with.
Obviously,
A locked bootloader ( Which when unlocked wipes data)
A stock old cyanogen recovery.
Non rooted CM12.....
So this means that if you want to be a power user you have to start form beginning. So... consider taking a nandroid backup before you upgrade.....
STEPS TO BACKUP DATA ON CYANOGEN 11
So... Abhiram I cant find my backup on sdcard
answer to this question is very simple. You know that your sdcard and app memory are same. So they created a new folder 0 and mounted as your sdcard.
So... How do you get that out....
There are 2 methords
Common step boot into recovery and connect your mobile to your computer. Make sure that ADB drivers are installed
Methord 1
Type
"adb shell
cp -r /sdcard/clockworkmod/ /sdcard/0/android/
adb reboot"
So after the phone rebooted. Open file manage ( anyone ) Browse into android folder in your sdcard, you will find your backup there. If you cant find your whole backup , the chances are you r running out of memory.
Methord 2
type
"adb pull /sdcard/clockworkmod/ %UserProfile%/documents/backup_from_nandroid/ "
Your backup can be found in c:/users/<your user name here>/documents/backup_from_nandroid/
So that is it....
So when you unlock boot loader you can copy this backup into your phone by....
1) Copy backup to adb folder
2) Type adb push <Directory name> /sdcard/clockworkmod/
Then do a advanced restore. Select data and restore
done!

Abhiram Shibu said:
Yes it will boot.
Link above is for custom CWM recovery.
Warning ******** Boring Story Ahead*********
So i purchased my yureka from Amazon. When i got it, I unlocked boot loader, installed cwm recovery right away. When the lollipop upgrade showed up I tried to download it via system upgrade. It downloaded but wont flash because of a custom recovery. So... I downloaded a signed zip file from xda attachment which i gave you. I cleared cache and tried installing the zip file.... It actually works.
Why it worked?
Stock rom looks for signed zips and it should be signed my their developer. But custom recoveries installs any zip file which is flashable regardless they are signed or unsigned. The only thing it looks for is the scripts and device compactability.
So try flashing the lollipop signed zip file. It will surely work...
So... What will the zip file do?
It will wipe system, modem, recovery etc exept data. Resize them and copy files in.
So ... What will you end up with.
Obviously,
A locked bootloader ( Which when unlocked wipes data)
A stock old cyanogen recovery.
Non rooted CM12.....
So this means that if you want to be a power user you have to start form beginning. So... consider taking a nandroid backup before you upgrade.....
STEPS TO BACKUP DATA ON CYANOGEN 11
So... Abhiram I cant find my backup on sdcard
answer to this question is very simple. You know that your sdcard and app memory are same. So they created a new folder 0 and mounted as your sdcard.
So... How do you get that out....
There are 2 methords
Common step boot into recovery and connect your mobile to your computer. Make sure that ADB drivers are installed
Methord 1
Type
"adb shell
cp -r /sdcard/cyanogenmod/ /sdcard/0/android/
adb reboot"
So after the phone rebooted. Open file manage ( anyone ) Browse into android folder in your sdcard, you will find your backup there. If you cant find your whole backup , the chances are you r running out of memory.
Methord 2
type
"adb pull /sdcard/clockworkmod/ %UserProfile%/documents/backup_from_nandroid/ "
Your backup can be found in c:/users/<your user name here>/documents/backup_from_nandroid/
So that is it....
So when you unlock boot loader you can copy this backup into your phone by....
1) Copy backup to adb folder
2) Type adb push <Directory name> /sdcard/clockworkmod/
Then do a advanced restore. Select data and restore
done!
Click to expand...
Click to collapse
Ok.. I want to revert back to kitkat. i wont be using fastboot to flash rom(only to flash recovery image). Is there anything else which i should avoid and keep in mind in order to prevent hard brick?? please suggest

coolboyforeva said:
Ok.. I want to revert back to kitkat. i wont be using fastboot to flash rom(only to flash recovery image). Is there anything else which i should avoid and keep in mind in order to prevent hard brick?? please suggest
Click to expand...
Click to collapse
Tips to avoid hardbrick.
Don't flash ROM via fastboot
Don't Format partition using fast boot
You can flash boot and recovery via fastboot.
You can do anything in recovery.
Advice backup ROM before you install kernel, or any zip files. That will help you if you soft brick your phone.
Hit thanks if I help you in anyway till now.

On reading the OP's comments another doubt occurred, Do i need to unlock bootloader all the time when switching between KK & LP? (Will the internal SD memory gets wiped all the time... Do i need to backup every data on the internal SD memory onto PC before switching from KK to LP & vice-versa?)

Yes, but in case of upgrading and unlocking boot loader
Nice Question
When you downgrade from CM12 to CM11 your data will be safe. Unlocking boot loader will not do anything with your data:angel:
But When you are upgrading from CM11 to CM12 your data will be also safe, but the problem occurs when you try to unlock boot loader It will wipe all of your data.:crying:
When we unlock boot loader in kitkat CM11 by using command fastboot -i 0x1ebf oem unlock
It doesn't ask for any confirmations.
But in case of CM12 when you unlock boot loader by using the same command, before wiping data, it asks for confirmation. ie It tells to push vol+ to confirm or push vol - to stop.
If you see like this. Fastboot is going to erase your sdcard.
Its a good practice to backup your data when you r playing with your phones firmware, It will help you get back your memorable moments, favorite music etc.
If you have an otg cable. Keep a pendrive for backup
So concluding in unlocking CM11 no data loss unlocking in CM12 there is data loss.
Good luck:good:​

One more doubt, suppose i'm on KK & want to upgrade to some custom CM12.x rom, do i need to go through the process of installing stock cm12 all the time, or do u suggest any other simple way to directly do the same?

Softbricked Mi10t Lite (gauguin)

Hello guys,
I have rooted 2 days ago my phone with TWRP and Magisk; everything worked fine until I tried to change somethin in /system/ folder. It always said I dont have write rights. So I decided to go back to stock rom. I have downloaded the stock rom for my phone (gauguin, Global 12.0.8.0 , Android 10.) Now I have the following problem. My device is soft bricked.
So i decided to google and try to flash another Rom for my phone. I found one here.
https://xiaomirom.com/en/rom/mi-10t-lite-gauguin-global-fastboot-recovery-rom/
How Can I flash that file? its .tgz
I have stock rom installed and I cant flash TWRP
Thanks in advance
Francesco

here is what comes when I try to flash. It fails aftter Flashing super :
error hosted at ImgBB
Image error hosted in ImgBB
ibb.co

Francescohub said:
here is what comes when I try to flash. It fails aftter Flashing super :
Click to expand...
Click to collapse
Unpack TGZ archive, then untar TAR file again. You will see folder with images and script files. Run "flash_all_except_storage.bat".

Francescohub said:
here is what comes when I try to flash. It fails aftter Flashing super :
error hosted at ImgBB
Image error hosted in ImgBB
ibb.co
Click to expand...
Click to collapse
Get it too work ?

_mysiak_ said:
Unpack TGZ archive, then untar TAR file again. You will see folder with images and script files. Run "flash_all_except_storage.bat".
Click to expand...
Click to collapse
For the love of god, I just spent 3 hours to install fastboot ROM and did not succeed. No idea what went wrong, but at the end I finally restored my device..
1. download recovery ROM and transfer it to internal SD
2. download fastboot ROM, unpack it
3. modify flash_all_except_storage.bat and delete lines with CRCLIST and SPARCECRCLIST
4. run the script
5. phone will keep rebooting on MI logo
6. boot to TWRP "fastboot boot twrp.img"
7. install recovery ROM from TWRP
8. (install Magisk), reboot phone to system
For some reason fastboot flashing doesn't install /odm partition correctly. I have the latest drivers, android tools, tried 2 PCs, 2 different USB cables, different USB ports, using Mi Flash, nothing helped. The only solution was to flash recovery rom from TWRP. Fortunately no data has been lost.

Francescohub said:
Hello guys,
I have rooted 2 days ago my phone with TWRP and Magisk; everything worked fine until I tried to change somethin in /system/ folder. It always said I dont have write rights. So I decided to go back to stock rom. I have downloaded the stock rom for my phone (gauguin, Global 12.0.8.0 , Android 10.) Now I have the following problem. My device is soft bricked.
So i decided to google and try to flash another Rom for my phone. I found one here.
https://xiaomirom.com/en/rom/mi-10t-lite-gauguin-global-fastboot-recovery-rom/
How Can I flash that file? its .tgz
I have stock rom installed and I cant flash TWRP
Thanks in advance
Francesco
Click to expand...
Click to collapse
Can you boot into fastboot? You said it's soft bricked so I imagine you can. Reply and I'll get back to you, I soft bricked mine and fixed it fine.

Hey guys, I was finally able to flash the Rom.
I used to flash a Rom with Xiaomi Flash, accidentaly it was a wrong rom, which I saw later on.
So I installed TWRP recovery with fastboot commands and downloaded the right rom. I used to download the EEA Rom instead of Global Rom. So I transfered the EU Rom to micro SD Card and flashed it with TWRP.
Everything is working now, except the access to /system folder, after I rooted with magisk 20.4. Even with the newest Version it does not work.
So I tried in the terminal the following command while I was in /system folder: mount -o rw,remount/ But this does also not work. How can I get acess to it?
Sorry for my english again

Francescohub said:
Hey guys, I was finally able to flash the Rom.
I used to flash a Rom with Xiaomi Flash, accidentaly it was a wrong rom, which I saw later on.
So I installed TWRP recovery with fastboot commands and downloaded the right rom. I used to download the EEA Rom instead of Global Rom. So I transfered the EU Rom to micro SD Card and flashed it with TWRP.
Everything is working now, except the access to /system folder, after I rooted with magisk 20.4. Even with the newest Version it does not work.
So I tried in the terminal the following command while I was in /system folder: mount -o rw,remount/ But this does also not work. How can I get acess to it?
Sorry for my english again
Click to expand...
Click to collapse
Think you storage is corrupted what I did was download the ROM for my phone open the tar ROM to you see a file says images flash all and other stuff play rom folder in mi flash tool folders and open CMD use flash all in ROM folder

Make sure your phone is in fastboot before you use the flash all file it will return your phone to stock ROM