Database Info

[HOWTO] INSTALL STOCK FIRMWARE USING CWM/TWRP even w/a DEAD USB Port

GUIDE TO FLASHING STOCK FIRMWARE FOR ATT AND ROGERS I727 SKYROCKET PHONES WITHOUT USING ODIN OR KIES ​
THIS METHOD APPLYS TO:
ONLY FOR PHONES THAT CAN BOOT INTO A CUSTOM RECOVERY CWM/TWRP
USERS WHO CANT USE ODIN AND/OR KIES FOR WHATEVER REASON
PHONES WITH A BAD USB PORT
HAVE USB CONNECTIVITY ISSUES
MAC USERS WITH A CUSTOM RECOVERY ALREADY INSTALLED.
YOU ARE ON A CUSTOM ROM WITH USB PROBLEMS AND NEED TO RETURN TO STOCK FOR WARRANTY REPAIRS
NOTE: USING THIS GUIDE TO RETURN TO STOCK WILL PERMANENTLY UNROOT THE PHONE, BUT CAN BE REROOTED AFTER IF NEEDED.
Disclaimer: I am not responsible for your devices, follow guide at your own risk!
READ THE WHOLE POST
HOW TO ENTER INTO RECOVERY MODE, INSTRUCTIONS HERE STEP #4
GUIDE PRESUMES YOU ALREADY KNOW HOW TO INSTALL/FLASH FILES FROM RECOVERY
YOU NEED TO HAVE ONE OF THE RECOMMENDED CUSTOM RECOVERIES ALREADY INSTALLED ON THE PHONE SUCH AS CWM OR TWRP, LINKS IN THE DOWNLOAD SECTION BELOW
IN THIS GUIDE YOU WILL BE INSTALLING THE STOCK FIRMWARE ZIP FILE
OPTIONAL: INSTALLING THE STOCK RECOVERY ZIP FILE ONLY IF YOU NEED TO RETURN FOR WARRANTY, OTHERWISE NOT RECOMMENDED TO INSTALL
GETTING THE STOCK FIRMWARE TO YOUR PHONE
OPTION 1: IF YOUR ABLE TO BOOT INTO ANY ROM:
YOU HAVE A WORKING USB CONNECTION:
Download the files and transfer the files from your computer to your internal or external sdcard
YOU DONT HAVE A WORKING USB CONNECTION: USE EITHER METHOD "A" OR "B" OR "C":
METHOD A: From the phone use xda app or browser and navigate to this page and download the files directly to your device from the links provided below, then move them to the root of your internal or external sdcard, it will make it easier to find.
METHOD B: Use airdroid wirelwss appor kies air to transfer your files from your computer to your phone through your wifi connection and place them in the root of your internal or external sdcard
METHOD C: use an external sdcard reader/writer or another phone that has a micro sdcard slot and transfer files from your computer to the root of the external sdcard, then insert the sdcard back into the phone.
OPTION 2: YOUR NOT ABLE TO BOOT BUT CAN GET INTO A CUSTOM RECOVERY: USE EITHER METHOD "A" OR "B":
METHOD A: If usb port works: enable usb mount in custom recovery and transfer files to the root of your sdcard
METHOD B: If usb port doesnt work: use an external sdcard reader/writer or another phone that has a micro sdcard slot and transfer files from your computer to the root of the external sdcard, then insert the sdcard back into the phone.
FLASHING THE FILES
FIRMWARE
ENTER INTO RECOVERY MODE
PERFORM A RESET AND WIPE BOTH CACHES
INSTALL THE STOCK FIRMWARE ZIP FILE
ONLY INSTALL THE STOCK FIRMWARE(NOT THE STOCK RECOVERY ZIP FILE) THEN REBOOT THE PHONE INTO ANDROID TO CHECK IF IT BOOTS PROPERLY
YOUR GOOD LIKE THIS IF YOU JUST WANTED STOCK BACK ON YOUR PHONE
STOCK RECOVERY: ONLY RECOMMENDED IF RETURNING FOR WARRANTY REPAIR AND NEED TO SHOW FULL STOCK
TO GET THE STOCK RECOVERY ZIP FILE ONTO THE SDCARD FOLLOW THE INSTRUCTIONS FOR THE FIRMWARE GUIDE ABOVE
ENTER INTO RECOVERY MODE
INSTALL THE STOCK RECOVERY ZIP FILE, ONCE YOU DO THIS YOU WILL LOSE THE CUSTOM RECOVERY
IF YOU CANT USE ODIN THERE IS NO WAY TO REINSTALL A CUSTOM RECOVERY ON THE SKYROCKET ONCE THE STOCK RECOVERY HAS BEEN INSTALLED.
REBOOT PHONE INTO RECOVERY TO SEE IF THE STOCK RECOVERY FLASHED PROPERLY.
DOWNLOADS
MOVED TO THE 1STOP STICKY
USE CWM/TWRP FLASHABLE FIRMWARES

This really work. Can you write one for unlocking also?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

chasama said:
This really work. Can you write one for unlocking also?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
you have to buy unlock code, and you have to be on stock when entering code, read this http://forum.xda-developers.com/showpost.php?p=28439204&postcount=10

Samsugn galaxy s2 GT-I9100 help!!
vincom said:
you have to buy unlock code, and you have to be on stock when entering code, read this http://forum.xda-developers.com/showpost.php?p=28439204&postcount=10
Click to expand...
Click to collapse
i am running on RR Jelly bean rom 3.0.6, suddenly my comp stopped detecting my phone nd now its not detected by any comp!!
wen i connect it only charges but the phone is not recognised!! i want to install stock ics firmware plz help me!

Hey thanks for the comprehensive list. One question. I can't boot, but I can access recovery. I can access USB, however, I don't have an external sd card. What are my options, besides buying one.

zgibbyson said:
Hey thanks for the comprehensive list. One question. I can't boot, but I can access recovery. I can access USB, however, I don't have an external sd card. What are my options, besides buying one.
Click to expand...
Click to collapse
use internal if you have usb access to it

thanks

the SD card from my other phone has some folders:.android secure, data; LOST.DIR; DCIM; LGsys.....which folder should I put TWRP2.2.0 & stock firmware in ? which folder is considered A ROOT of the external SD card ? so I can boot the device.I couldn't boot it. I am newbi. please help. Thankss.

Re: [HOWTO] INSTALL STOCK ICS USING CWM/TWRP even w/a DEAD USB Port
PhoneTay11 said:
the SD card from my other phone has some folders:.android secure, data; LOST.DIR; DCIM; LGsys.....which folder should I put TWRP2.2.0 & stock firmware in ? which folder is considered A ROOT of the external SD card ? so I can boot the device.I couldn't boot it. I am newbi. please help. Thankss.
Click to expand...
Click to collapse
Don't put it in any folder, just copy to the SD card.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

I did copy TWRP2.2.0 and stock firmware zip in SD card and hold volume up+down + power button to get recovery mode but I only see pictures of phone & monitor with yellow
triangle at center.( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again.)
---------- Post added at 06:31 AM ---------- Previous post was at 06:23 AM ----------
I upgraded my samsung s2 version 2.3.6 to 4.0.4 through the Kies. Then I tried to install TWRP 2.2.0 and Odin 1.85. I saw COM 14 ; COM 17 when I hit start button .It said
FAILED. Now it showed a yellow triangle in the middle of phone & monitor pictures. ( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again). Please help . Thank you very much.
I just tried other laptop . I saw COM 3 but it said it couldn't open the serial (COM )port . All thread completed (success 0/ failed 1)

PhoneTay11 said:
I did copy TWRP2.2.0 and stock firmware zip in SD card and hold volume up+down + power button to get recovery mode but I only see pictures of phone & monitor with yellow
triangle at center.( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again.)
---------- Post added at 06:31 AM ---------- Previous post was at 06:23 AM ----------
I upgraded my samsung s2 version 2.3.6 to 4.0.4 through the Kies. Then I tried to install TWRP 2.2.0 and Odin 1.85. I saw COM 14 ; COM 17 when I hit start button .It said
FAILED. Now it showed a yellow triangle in the middle of phone & monitor pictures. ( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again). Please help . Thank you very much.
I just tried other laptop . I saw COM 3 but it said it couldn't open the serial (COM )port . All thread completed (success 0/ failed 1)
Click to expand...
Click to collapse
that screen is also odin/download mode
try flashing again
check odin troubleshooting section in the "install cwm/twrp" link in my sig

vincom said:
GUIDE TO FLASHING STOCK FIRMWARE FOR ATT AND ROGERS I727 SKYROCKET PHONES WITHOUT USING ODIN OR KIES ​
THIS METHOD APPLYS TO:
PHONES THAT CAN BOOT INTO A CUSTOM RECOVERY CWM/TWRP
USERS WHO CANT USE ODIN AND/OR KIES FOR WHATEVER REASON
PHONES WITH A BAD USB PORT
HAVE USB CONNECTIVITY ISSUES
MAC USERS WITH A CUSTOM RECOVERY ALREADY INSTALLED.
YOU ARE ON A CUSTOM ROM WITH USB PROBLEMS AND NEED TO RETURN TO STOCK FOR WARRANTY REPAIRS
NOTE: USING THIS GUIDE TO RETURN TO STOCK WILL PERMANENTLY UNROOT THE PHONE, BUT CAN BE REROOTED AFTER IF NEEDED.
Disclaimer: I am not responsible for your devices, follow guide at your own risk!
READ THE WHOLE POST
HOW TO ENTER INTO RECOVERY MODE, INSTRUCTIONS HERE STEP #4
GUIDE PRESUMES YOU ALREADY KNOW HOW TO INSTALL/FLASH FILES FROM RECOVERY
YOU NEED TO HAVE ONE OF THE RECOMMENDED CUSTOM RECOVERIES ALREADY INSTALLED ON THE PHONE SUCH AS CWM OR TWRP, LINKS IN THE DOWNLOAD SECTION BELOW
IN THIS GUIDE YOU WILL BE INSTALLING THE STOCK FIRMWARE ZIP FILE
OPTIONAL: INSTALLING THE STOCK RECOVERY ZIP FILE ONLY IF YOU NEED TO RETURN FOR WARRANTY, OTHERWISE NOT RECOMMENDED TO INSTALL
GETTING THE STOCK FIRMWARE TO YOUR PHONE
OPTION 1: IF YOUR ABLE TO BOOT INTO ANY ROM:
YOU HAVE A WORKING USB CONNECTION:
Download the files and transfer the files from your computer to your internal or external sdcard
YOU DONT HAVE A WORKING USB CONNECTION: USE EITHER METHOD "A" OR "B" OR "C":
METHOD A: From the phone use xda app or browser and navigate to this page and download the files directly to your device from the links provided below, then move them to the root of your internal or external sdcard, it will make it easier to find.
METHOD B: Use airdroid wirelwss appor kies air to transfer your files from your computer to your phone through your wifi connection and place them in the root of your internal or external sdcard
METHOD C: use an external sdcard reader/writer or another phone that has a micro sdcard slot and transfer files from your computer to the root of the external sdcard, then insert the sdcard back into the phone.
OPTION 2: YOUR NOT ABLE TO BOOT BUT CAN GET INTO A CUSTOM RECOVERY: USE EITHER METHOD "A" OR "B":
METHOD A: If usb port works: enable usb mount in custom recovery and transfer files to the root of your sdcard
METHOD B: If usb port doesnt work: use an external sdcard reader/writer or another phone that has a micro sdcard slot and transfer files from your computer to the root of the external sdcard, then insert the sdcard back into the phone.
FLASHING THE FILES
FIRMWARE
ENTER INTO RECOVERY MODE
PERFORM A RESET AND WIPE BOTH CACHES
INSTALL THE STOCK FIRMWARE ZIP FILE
ONLY INSTALL THE STOCK FIRMWARE(NOT THE STOCK RECOVERY ZIP FILE) THEN REBOOT THE PHONE INTO ANDROID TO CHECK IF IT BOOTS PROPERLY
YOUR GOOD LIKE THIS IF YOU JUST WANTED STOCK BACK ON YOUR PHONE
STOCK RECOVERY: ONLY RECOMMENDED IF RETURNING FOR WARRANTY REPAIR AND NEED TO SHOW FULL STOCK
TO GET THE STOCK RECOVERY ZIP FILE ONTO THE SDCARD FOLLOW THE INSTRUCTIONS FOR THE FIRMWARE GUIDE ABOVE
ENTER INTO RECOVERY MODE
INSTALL THE STOCK RECOVERY ZIP FILE, ONCE YOU DO THIS YOU WILL LOSE THE CUSTOM RECOVERY
IF YOU CANT USE ODIN THERE IS NO WAY TO REINSTALL A CUSTOM RECOVERY ON THE SKYROCKET ONCE THE STOCK RECOVERY HAS BEEN INSTALLED.
REBOOT PHONE INTO RECOVERY TO SEE IF THE STOCK RECOVERY FLASHED PROPERLY.
DOWNLOADS
MOVED TO THE 1STOP STICKY
USE CWM/TWRP FLASHABLE FIRMWARES
Click to expand...
Click to collapse
Do you have the Stock ROM for GB 2.3.6 (SkyRocket) which i can flash using TWRP? My PC doesn't recognize my Skyrocket. The only way for me is to flash using TWRP but I can't find the GB ROM for it. There's a lot of ROM of GB but it is for ODIN (with extension .tar.md5) instead.

ntd0626 said:
Do you have the Stock ROM for GB 2.3.6 (SkyRocket) which i can flash using TWRP? My PC doesn't recognize my Skyrocket. The only way for me is to flash using TWRP but I can't find the GB ROM for it. There's a lot of ROM of GB but it is for ODIN (with extension .tar.md5) instead.
Click to expand...
Click to collapse
no, why do u need gb, just flash the ics or jb roms, or if your usb is not dead go through the odin trouble shooting section in the restore to stock sticky to try to solve the connection issue, link to restore to stock is in my sig

Stock Rom Android M.
Hi, could you help me i have TWRP Custom recovery and cm12.1 android lollipop, i want to
Flash Stock Rom Android Marshmallow using TWRP is it possible using this method ,
my Device is Galaxy Tab S 8.4 wi-fi.

invalid zip
I am a mac user without access to a PC (no odin). I have TWRP recovery installed. I used android file transfer to move the stock firmware zip in the download section to the internal SD (root folder). I wiped the system and cache, then install zip - but it fails every time with "invalid zip file format". I have tried a half dozen other versions of the stock ROM from various sources and they all fail with the same error. ZIP signature verification is disabled. Just when I thought that i was doing something completely dumb and not flashing correctly at all - I tried re-flashing the lineageOS ROM i have and that worked fine. I've read a bit about unpacking and re-zipping these zips to get them to work, but that requires 7zip (which I don't have on mac). Help! am I doing something dumb or do I not have the correct zip files? I really need to get back to stock so I can activate my cellular service.

champagne_problems said:
I am a mac user without access to a PC (no odin). I have TWRP recovery installed. I used android file transfer to move the stock firmware zip in the download section to the internal SD (root folder). I wiped the system and cache, then install zip - but it fails every time with "invalid zip file format". I have tried a half dozen other versions of the stock ROM from various sources and they all fail with the same error. ZIP signature verification is disabled. Just when I thought that i was doing something completely dumb and not flashing correctly at all - I tried re-flashing the lineageOS ROM i have and that worked fine. I've read a bit about unpacking and re-zipping these zips to get them to work, but that requires 7zip (which I don't have on mac). Help! am I doing something dumb or do I not have the correct zip files? I really need to get back to stock so I can activate my cellular service.
Click to expand...
Click to collapse
AFAIK all devhosts files are bad/fake, i cant even dl my own files.
if i find them all reup to androidfilehost

Stock Rom
champagne_problems said:
I am a mac user without access to a PC (no odin). I have TWRP recovery installed. I used android file transfer to move the stock firmware zip in the download section to the internal SD (root folder). I wiped the system and cache, then install zip - but it fails every time with "invalid zip file format". I have tried a half dozen other versions of the stock ROM from various sources and they all fail with the same error. ZIP signature verification is disabled. Just when I thought that i was doing something completely dumb and not flashing correctly at all - I tried re-flashing the lineageOS ROM i have and that worked fine. I've read a bit about unpacking and re-zipping these zips to get them to work, but that requires 7zip (which I don't have on mac). Help! am I doing something dumb or do I not have the correct zip files? I really need to get back to stock so I can activate my cellular service.
Click to expand...
Click to collapse
Just use "Flashfire" and do everything from your phone no need for a computer.

Using this to flash 1.7 gb file
I have a moto g5s plus (sanders) and have installed unofficial lineage 15.0 build. before installation , I didn't took backup in TWRP. Now i am downloading stock firmware zip file. can that be installed using TWRP?

ParaSpl01t said:
I have a moto g5s plus (sanders) and have installed unofficial lineage 15.0 build. before installation , I didn't took backup in TWRP. Now i am downloading stock firmware zip file. can that be installed using TWRP?
Click to expand...
Click to collapse
you mean this zip file when you unzip it show you 5 files that you can use with Odin?

I tried and says fail , why would tarp fail to flash a stock firm ?

[Q] How to install a OTA file?

Hi everyone:
I have see that there are OTA updates for my model from Sammobile.
I have two questions:
1.how flash this file? via Recovey?
And, if that it's correct, it's necessary wipe data & factory reset?
2. It's strictly necessary flash that updates having already installing the "required PDA version"?
Please response me. I have 2 old threads and zero responses

Ota: over the air those only appear if you search for updates via setting of you device not via sammobile if you find update this way so just follow instructions in the screen to flash but this kind of updates needs stock firmware and mostly stock recovery not cwm (custom)
If file has extension as zip so could be mostly installed via cwm recovery but make sure about instructions in the thread you downloaded from as it may be just zipped and need to be unzipped first and inside the zipped file you may find file with extension tar or tar.md5 to be flashed via pc odin or mobile odin or heimdall for mac or linux
If file has extension tar or tar.md5 so flashed as mentioned via pc odin or mobile odin or heimdall via pda section in pc odin you need to put device in download mode and need samsung drivers installed
Sent from my GT-P5100 using xda app-developers app

Mohamedselim said:
Ota: over the air those only appear if you search for updates via setting of you device not via sammobile if you find update this way so just follow instructions in the screen to flash but this kind of updates needs stock firmware and mostly stock recovery not cwm (custom)
If file has extension as zip so could be mostly installed via cwm recovery but make sure about instructions in the thread you downloaded from as it may be just zipped and need to be unzipped first and inside the zipped file you may find file with extension tar or tar.md5 to be flashed via pc odin or mobile odin or heimdall for mac or linux
If file has extension tar or tar.md5 so flashed as mentioned via pc odin or mobile odin or heimdall via pda section in pc odin you need to put device in download mode and need samsung drivers installed
Sent from my GT-P5100 using xda app-developers app
Click to expand...
Click to collapse
It's a zip with update-script, so I suppose that it's for recovery. Ok, thanks

[Released][ROM][ODIN] ICS Stock firmware XXLQ9 repacked with CWM 6

Q. Why there is a need to repack the firmware?
A. As you may know, the stock kernel in the stock firmware has the emmc hard brick feature enabled which is believed to be the reason of 2 hard brick incident reported in the forum. And even worse, the emmc hard brick bug (mmc_erase) can be called @ anytime after the system is booted with a buggy kernel, which means that your device can immediately get bricked after the first reboot.
Q. So is it okay to flash the ROM via odin with a different bootloader (i.e. boot.img)?
A. Theoretically, yes. But the problem is that when we repack the odin package with a modified boot.img. The download counter will rise and a yellow triangle will appear on every boot.
Q. So is there any way to flash the stock bootloader but without letting it get booted?
A. Yes. There is a way to do so. After you have successfully flashed a package via odin, the odin bootloader (based on BCT partition) will invoke the recovery bootloader to finish the install process. And if you are not using the stock recovery, the process will get halted and then leave you at the recovery (CWM) screen. And then you can flash a kernel via CWM at this point.
Q. Is there anything that I should aware of?
A. Yes. Just like flashing any firmware, After flashing the ICS package, it is important for you to backup all the important files before flashing.
Guideline 1 [For people who is willing to use CWM6 (provided by Adam77Root)] (prefered way) :
1. Turn on your device and connect it to a computer
2. Place the kernel file, superuser file (which can be flashed via CWM) and new_sec_csc.zip into your internal SD card first and make sure all your important data on /sdcard are backed up (You are free to select any kernel but make sure the mmc erase part get disabled from the kernel completely)
3. Turn it off and remove the external sdcard from the device
4. Download the ICS firmware files which contains GB kernel and CWM6
5. Put the device into download mode and flash the above package via odin 3.07. Place the package file (*.tar.md5) into PDA part (You can now flash with pit file as well, however the internal sdcard data will get wiped so it is important for you to make a backup for important files before flashing) (DO NOT attemp to flash any ICS package via odin 1.85 as there is a high risk that the download process get stuck in odin v1.x series, and you have to unbrick your device with nvflash tool if error occurs)
6. After the device is restarted, it will get into recovery (CWM) mode. And the script provided by Samsung will be failed to execute due to a assert call. (Don't worry, you can execute the script again by using the patched new_sec_csc.zip)
7. Backup any important data in /sdcard (external sdcard) now if you didn't do so. You can do this @ 'Mount and storage' -> 'Mount USB devices'.
8. 'Wipe cache' and 'Wipe data / factory reset' (make sure you have all your important data on /sdcard backed up and your have removed your external sdcard device)
9. If the above stage has wiped your CWM flashable zip file as well, you can mount the device to a computer via mount menu and you can place the zip file to the phone as mass storage again.
10. Install the CWM flashable zip file (superuser, new_sec_csc.zip and your kernel file) from sdcard (For an unknown odd reason, all the packages you gonna install in this step will have signature verification error, but it is safe to proceed. Just switch off the signature verification from the menu or choose to 'Install untrusted package'.)
11. After you flashed kernel, you are free to flash anything and free to reboot now.
12. If you have used a pit file for flashing the package in odin, a message will be appeared in notification center telling you the filesystem on /sdcard cannot be recognized. Just click on it to format the sdcard and then you are free to use anything now.
13. If you are still afraid of breaking system integrity as you were not using the samsung recovery script to finish the update process, navigate to 'Options -> Back up and reset -> Factory data reset' and totally reset the device there.
P.S. If you accidentally pressed reboot the system now in CWM 6, don't worry, the system will not be able to boot into normal mode. And you can redo all the things since the beginning.
Update #1 : During testing the flash process, I have found that the repacked firmware cannot be flashed with odin 1.83. It is important to get all the ICS firmware being flashed with odin 3.07 (or 3.x sereis) instead v1.x series. Otherwise you have made a risk that your partition (PIT) table is messed up so srsly that you have to use nvflash tool to restore everything. I will tell this to cooleagle to get everyone knows of it.
XXLQ9 :
Stock package with GB kernel and CWM6 which is based on safe stock GB ZSLE6 kernel (just extract the file in the splited zip files) : http://www.mediafire.com/?uq5tg9o7nli04b2 and http://www.mediafire.com/?b5i571br0x07c38
CWM flashable package :
- Superuser CWM flashable package : http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip or Superuser-3.2-RC3-arm-signed.zip in attachments (But you will be unable to update with the 3.2 RC3 build, use 3.1.3 one if you want)
- My own kernel (flashable via CWM) : UnknownzD_Kernel_with_superuser.zip (with superuser, good for first time install) and UnknownzD_Kernel.zip in the attachments
- Patched Samsung install script (the one which failed to run) : new_sec_csc.zip in the attachments
Odin v3.07 : Odin307.zip in the attachments
Credits go to Adam77Root for his CWM image and someone(!?) who has uploaded odin 3.07 to xda forum. Will try to check his name later.
Short change log about my kernel (The longer one will get posted when I start another thread for it) :
4 IO scheduler added
Voodoo sound patch added
Full fp calculation based on hardware fp opcode only (which should makes the device consumes less energy while providing the same performance level)
MMC erase function tootally disabled
Default.prop get modified to increase the performance
Based on ICS 3.x kernel src code released by Samsung
If you gonna use my kernel, please make sure that you have efs_backup.img backed up safely after flashing my kernel package, as it contains your device's IEMI info, which can save you from future disaster as you can use the unbrick tool with it. You can backup the efs_backup.img by :
1. Flash my kernel in CWM
2. Mount and storage -> Mount USB devices
3. Copy the efs_backup.img from the sdcard to your own computer (it is vital for you as you can use the unbrick tool later)

Now I am stuck @ finding a proper file host to upload the files.

waiting for this!

Rooted?
BusyBox?
Init.d?
Sent from an GT-I9103 with ICS and Tapatalk 2

Sorry as mediafire.com only allows upload 200MB per file, I need to take some time to split the files into multiple zip, please wait for about 15 minutes.

coldbeermt said:
Rooted?
BusyBox?
Init.d?
Sent from an GT-I9103 with ICS and Tapatalk 2
Click to expand...
Click to collapse
You can root it on your own with superuser zip file. And busybox binary is not yet dropped into /sbin/ as I believe it comprise the system integrity back in GB kernel. Init.d will be supported in near feature. All the things that I changed is just inside the kernel and recovery and provide a safe envrionment for user to continue to flash their own desired kernel. Nothing more.
For kernel development, I will make a separate thread in dev section later.
Sorry I have to postpone the release as I have to repack everything with the nordic release (XXLQ9) now.

Ok, I'm sure you know I asked just for general information. I supposed your answer yet
Anyway, I'm sure its a good job. With the new version (nordic) I suggest you to upload releases to dropbox our something easier. Anybody could make a mirror in other servers later :thumbup:
Sent from an GT-I9103 with ICS and Tapatalk 2

UnknownzD said:
Sorry as mediafire.com only allows upload 200MB per file, I need to take some time to split the files into multiple zip, please wait for about 15 minutes.
Click to expand...
Click to collapse
Man we r RC, we get premium hosting space from DevHost.
Check ur PM
Sent from my Galaxy Royale using Tapatalk 2.

xlm13x said:
Man we r RC, we get premium hosting space from DevHost.
Check ur PM
Sent from my Galaxy Royale using Tapatalk 2.
Click to expand...
Click to collapse
Yea I just saw the PM, it is really useful for me tbh. Thanks for your help.

Okay after many hours of testing, I am happy to release the ICS XXLQ9 package with GB kernel and CWM 6 (based on the one posted by Adam77Root) that should be able to let you flash your own kernel after flashing it. Download links will be up shortly.

So after 5~6 times of srs bricking, I finally get it working correctly after working overnight.

Ok I have released the ROM already, please try to use it if you know how to use the unbrick tool. This is because I want to ensure that the package can be flashed safely in Odin v3.x instead of v1.x series.

UnknownzD said:
Ok I have released the ROM already, please try to use it if you know how to use the unbrick tool. This is because I want to ensure that the package can be flashed safely in Odin v3.x instead of v1.x series.
Click to expand...
Click to collapse
well as a bit newbie i am confused with all tuts floating on XDA
what i intend to is
1. flash Stock ROM via ODIN 1.8
2. flash CWM 5.x via ODIN 1.8
3. Flash ardatdat kernel via CWM
4. Now only i will wipe data thru CWM...
is this ok ?? i am concerned with Austrian firmware currently..rooting is not possible in nordic ROM due to system partition space...
can this be dangerous ??

vipul12389mehta said:
well as a bit newbie i am confused with all tuts floating on XDA
what i intend to is
1. flash Stock ROM via ODIN 1.8
2. flash CWM 5.x via ODIN 1.8
3. Flash ardatdat kernel via CWM
4. Now only i will wipe data thru CWM...
is this ok ?? i am concerned with Austrian firmware currently..rooting is not possible in nordic ROM due to system partition space...
can this be dangerous ??
Click to expand...
Click to collapse
Rooting Nordic ROM is quite easy, that is if you are on GB (if you are on ICS you will have zero free space in system space), so when you are on GB you need CWM http://forum.xda-developers.com/showthread.php?t=1839900 use CWM to wipe data and format system.
Flash Nordic ROM (Odin), than CWM, go to http://androidsu.com/superuser/ and download binary only (ARM), now use CWM to install SU binary.
You need SU app from Play Store and you are rooted.

Nice work! Thanks!
Sent from my GT-I9103

nedooo said:
Rooting Nordic ROM is quite easy, that is if you are on GB (if you are on ICS you will have zero free space in system space), so when you are on GB you need CWM http://forum.xda-developers.com/showthread.php?t=1839900 use CWM to wipe data and format system.
Flash Nordic ROM (Odin), than CWM, go to http://androidsu.com/superuser/ and download binary only (ARM), now use CWM to install SU binary.
You need SU app from Play Store and you are rooted.
Click to expand...
Click to collapse
Basically the things you mentioned above are included in the package / guide already. Tbh this should not be dangerous. But I want more people to test it first because last time when I released the GB kernel, a lot of people complained about the things that do not occur on my phone.
oh btw about the zero free space in system space, I believe it is just a bug in the filesystem. You can fix it easily by using e2fsck, which is actually included in my kernel script.

This is just explanation about staying stock. Your work and effort is well above this. Thanks in name of all flash addicts

So after many times of tests, I guess it is safe to use the build already, just make sure you have everything backed up before updating (actually you should do this for any fimrnware update). If you have found any problem, just report the problem here. I will repack every stock firmware following the same method until Samsung acknowledge that the MMC_CAP_ERASE is removed from stock kernel.
If you have found your device bricked after using any ICS update (for example, unable to flash the device any more via odin protocol), please let me know via pm please so that I can guide you to fix your phone in IRC.

pudup said:
What happens if I don't use data wipe and factory reset? I didn't so it for the CWM installation while upgrading from GB. Is it really necessary?
Click to expand...
Click to collapse
When you are updating the ROM from GB to ICS better to wipe data or else you face some Force Closes and other issues....

pudup said:
What happens if I don't use data wipe and factory reset? I didn't so it for the CWM installation while upgrading from GB. Is it really necessary?
"I like spelling my name backwards"
Click to expand...
Click to collapse
The wiping cache part is actually a part of odin download process. Everytime when you flash a new firmware in odin, the odin bootloader will invoke some scripts stored in /cache within recovery mode, and then wipe out these scripts / the whole partition as they are no longer needed.
However the wiping /data part is actually an essential part of firmware update and you should do it on your own if you are using CWM based firmware. This is because if you flash a firmware via odin, the data partition gets wiped after the device rebooted.
tbh it should be safe if you didn't wipe the /cache partition but not for the /data partition. Just some usls scripts and T9DB left behind in /cache. But incompatible binaries may still stays in /data if you didn't wipe it.
Sent from my GT-I9103 using xda app-developers app

Get your own CWM recovery for newer devices and dont beg anywhere - 2 simple steps

Those who struggle to get CWM recovery for thier newer devices and who are facing problem on romdump your stock rom to get stock recovery.img here you have 2 simple steps to get your CWM recovery for your new device
Step -1
Creating A Dump\Backup
Note: Root Required
1. Set "Settings" -> "Display" -> "Sleep" -> "10 minutes"
2. Install or update "Busybox" from play store
3. Set your phone to "Airplane" mode
4. Make sure that the card is not less than 2Gb of free space
5. Use any one of the following:
BakupTool_sdcard.zip saves a backup copy on the path: /mnt/sdcard/backup_v2
BakupTool_sdcard2.zip saves a backup copy on the path: /mnt/sdcard2/backup_v2
6. Extract the BakupTool_* to sdcard. Full path to the file should be: / sdcard / gscript
7. Install program: /sdcard /gscript /"GScriptLite.apk"
8. Open the program "GScriptLite". Press "Menu button" -> "Add Script"
9. Set tick "Needs SU"
10. Click "Load file" and select "back_mt657x.sh"
11. Click the button "Save"
12. Tap on a new script, "back_mt657x.sh". After that give the program root permissions if asked and wait for 5- 10 minutes. Do not use the phone during the process.
A sign of a normal shutdown of the script is:
Message in the terminal:
100% Backup Complite!!!
Saved to / sdcard/backup_v2/GGGGMMDD-ChChmm
Star Time: hh: mm: ss; End Time: hh: mm: ss
The appearance at the root of SD-card phone the following structure of folders and files:
backup_v2
YYYYMMDD-hhmm
* BDRS-YYYYMMDD-hhmm
boot.img
cache.ext4.tar
data.ext4.tar
nandroid.md5
recovery.img
system.ext4.tar
* misk
cache.img
cmdline.info
config.info
cpu.info
nvram.img
nvram.tar
ram.info
rom.info
* over
expdb.raw
full_preloader_part.raw
misc.raw
pmt.raw
sec_ro.raw
seccfg.raw
unknown.raw
boot.img
dsp_bl.img
ebr1.img
firmware.info
MT6577_a4_v2c.info
logo.img
mbr.img
preloader.img
recovery.img
system.img
uboot.img
data.img
step - 2
upload your stock recovery.img to get cwm recovery
kaushik Dutta has developed a clockworkmod recovery builder on the official site....
http://builder.clockworkmod.com/
so upload your stock recovery.img and get exact cwm recovery.img of ur device....and flash it.
if yours is a new devicw please select new device column.
thanks for this awesome build.
- after u upload your stock recovery.img on clicking fro new device just click on Build icon on the last of the page.....
- then u will be qued and u will gwt build number please save it for further refference...
- click proceed to that server and find ur build number,,,if it finished successfully u will see green icon on the left
- then click on your build number then click status there u will get something like this
Project recovery
Last Successful Artifacts
android_device_lge_cayman.zip 5.12 MB
inputrecovery.img 16.00 MB
manifest.xml 53.95 KB
recovery.img 6.92 MB
finally download recovery.img which is ur cwm recovery and flash it via Mobileuncle MTK tools which can be downloaded from playstore
If something goes wrong u can revert back ur rom or stock recovery itself by flashing ur stock recovery.img from the back up folder...or u can flash ur rom back using SP FLASH tools
IF i helped u please press thanks :victory::victory::victory:

anybody tried???
meanwhile how to extract stock recovery.img from stock ICS

I did test it. The image build does boot for me. But the build recovery i got this way did miss some *.ko files my device needed
The site is not new by the way..
Read here how to dump you're recovery...
http://forum.xda-developers.com/showthread.php?t=1935162

Re: clockworkmod for newer devices - now get CWM recovery for every android
[email protected] said:
I did test it. The image build does boot for me. But the build recovery i got this way did miss some *.ko files my device needed
The site is not new by the way..
Read here how to dump you're recovery...
http://forum.xda-developers.com/showthread.php?t=1935162
Click to expand...
Click to collapse
Dumping rom is bit confusing....because I'm a dentist...
Can u please explain in simple steps to get stock recovery.img
I'm having intex aqua flash which is new in the market but it has all the feature of high devices...
One more thing can I do this in windows? Or should I need linux?
Sent from my Aqua flash using xda premium

Trying this right now. Hope the recovery.img from a stock nandroid works.

Re: clockworkmod for newer devices - now get CWM recovery for every android
McJesus15 said:
Trying this right now. Hope the recovery.img from a stock nandroid works.
Click to expand...
Click to collapse
Share in simple steps to extract stock recovery.img after u successfully get ur cwm
Sent from my Aqua flash using xda premium

Re: clockworkmod for newer devices - now get CWM recovery for every android
drganbds said:
Share in simple steps to extract stock recovery.img after u successfully get ur cwm
Sent from my Aqua flash using xda premium
Click to expand...
Click to collapse
My device is different. Technically I have cwm recovery already. It's just only accessible through a fast boot command. This allows me to have a nandroid back up already so I just took the recovery.img from a stock back up
Sent from my Zio using xda app-developers app

check this thread is updated...

I tried this for a Lenovo IdeaTab A2109 to try and build a touch recovery. It already has a unofficial cwm recovery non touch, so I used that as the recovery.img. It put out 2 recovery.img's. One was a recovery.img and the other inputreovery.img. I'm not sure what one I should flash or if I'm supposed to flash both. Would it put out errors if it didn't work?
Thanks for this post and any help you can give.

linsalata28 said:
I tried this for a Lenovo IdeaTab A2109 to try and build a touch recovery. It already has a unofficial cwm recovery non touch, so I used that as the recovery.img. It put out 2 recovery.img's. One was a recovery.img and the other inputreovery.img. I'm not sure what one I should flash or if I'm supposed to flash both. Would it put out errors if it didn't work?
Thanks for this post and any help you can give.
Click to expand...
Click to collapse
Inputrecovery.img is wat u uploaded and recovery.img is wat u get as cwm recovery.
Sent from my Aqua flash using xda premium

drganbds said:
Inputrecovery.img is wat u uploaded and recovery.img is wat u get as cwm recovery.
Sent from my Aqua flash using xda premium
Click to expand...
Click to collapse
Oh OK. What about the question I asked about errors? Will it give any errors if the recovery wont work?
Thanks for the quick reply.

linsalata28 said:
Oh OK. What about the question I asked about errors? Will it give any errors if the recovery wont work?
Thanks for the quick reply.
Click to expand...
Click to collapse
If it gives error like black screen or volume key unfunction means it is not compiled properly but don't worry your device won't brick and u can revert back ur recovery by placing original.img on the root of phone storage and flash through mobileuncle tool..all the best
Sent from my Aqua flash using xda premium

Three Questions and I'm gonna try this out:
1. If the CWM recovery I build from CWM builder doesn't work, can I flash back the stock recovery by Mobile Uncle Tools, I mean won't it brick the device, can I still boot? I have a MT6577 device.
2. Does the script provided here backups up the stock recovery on Ice Cream Sandwich?
3. What else does this script do? Backup the whole phone?

ApplePriest said:
Three Questions and I'm gonna try this out:
1. If the CWM recovery I build from CWM builder doesn't work, can I flash back the stock recovery by Mobile Uncle Tools, I mean won't it brick the device, can I still boot? I have a MT6577 device.
2. Does the script provided here backups up the stock recovery on Ice Cream Sandwich?
3. What else does this script do? Backup the whole phone?
Click to expand...
Click to collapse
1. Yes u can reflash you stock recovery back via mobile uncle tool
2. Yes it will work on ICS
3. I have shown that wat the backup folder will have...it does full backup of your phone....
Sent from my Aqua flash using xda premium

Okay, Thank you.
I will try and update you on this.
Edit: After flashing recovery, I got blank screen in recovery mode.

thanx mate , really a helpfu guide i have Xtouch x714 with Allwinner A13 chip
before i tried many A13 CWM none of them worked not even boot , they nearly damage my tablet
thank god there is Phoneixcard i was able to revive it .
Anyway , your methode of getting the recovery.img from [gscript] did not work for me , it kept give me errors
even though it shows 100% complete
so i used another method to get my recovery.img , hence my tablet is an Allwinner A13 chip, so
i used [ Rom Dump ] which a small and powerful tool run it in Windows from [ http://www.techknow.me ]
it uses ADB so u have to be rooted and enable developer mode in your device and have ADB drivers in your PC
it backup image of your system and boot.img , recovery.img and data
so i used the extracted recovery.img in the site you provide me and i got my new recovery.img and flash it to my tablet via NovoTools 1.0
and i test it , it works like charm , thanx again mate really helpful

step 2 no working....website down?

Black Screen
When I flashed recovery made through it, it gave me a black screen Is there any way to fix this??

the online one is not working
i tried twice for micromax a84... i got the CWM recovery and flashed it via mobile uncle tools...but it didnt work

?
after hitting "build" it states
your build has been queued.The
build id is
9b42b141e21a35c4007c250f45ab2039
continue to the build sever
view the current build output
when i hit either option i get "HTTP ERROR 404.
can anyone else see my build id and if so can you download it and link it to me via PM.
or what can i do to get my image

[Q] I cant find a clockworkmod file to work with odin

The only clockworkmod files i see are .img, but to use with odin3 1.85 i need a .tar, .md5 or .smd file. What should i do? I just rooted as well. I have a model GT-P5113

easy step here -
install rom manger from play store , then download recovery of your device it's will automatically install cwm