Database Info

Installing Jellybean on HTC one X but not botting

Hello guys,
It was my first time to flash a ROM. I tried to install the ROM of [URL="http://forum.xda-developers.com/showthread.php?t=1763240][ROM][Jul 16]Jellybean 4.1.1 for Endeavoru AOSP Build[/URL]
Here is what I did
1)Download ROM from here http://jellybean.tom.gascoigne.me/continuous/tg_endeavoru-ota-15.zip
2)Put them to sdcard
3)wipe data/factory reset
4)Flash rom
5) I rebooted my HTC but the phone never started I am stuck on the neXus logo :S :S It is like infinite booting... so what did I do wrong guys? and how to fix it ??
Thank you

the_Storm said:
Hello guys,
It was my first time to flash a ROM. I tried to install the ROM of [URL="http://forum.xda-developers.com/showthread.php?t=1763240][ROM][Jul 16]Jellybean 4.1.1 for Endeavoru AOSP Build[/URL]
Here is what I did
1)Download ROM from here http://jellybean.tom.gascoigne.me/continuous/tg_endeavoru-ota-15.zip
2)Put them to sdcard
3)wipe data/factory reset
4)Flash rom
5) I rebooted my HTC but the phone never started I am stuck on the neXus logo :S :S It is like infinite booting... so what did I do wrong guys? and how to fix it ??
Thank you
Click to expand...
Click to collapse
You forgott to flash the Kernel Use Fastboot for this.
1)Download ROM from here http://jellybean.tom.gascoigne.me/continuous/tg_endeavoru-ota-15.zip
2)Open the Zip and Copy the boot.img to your pc
3)Put the ROM to sdcard
4)Boot your phone into fastboot (In Phone power off state press power + volume down)
5)connect to the pc via usb
6)use your commandline on pc + fastboot.exe and do the following command "fastboot flash boot <PathToTheBoot.ImgFromStep2>"
7)use your commandline on pc + fastboot.exe and do the following command "fastboot erase cache"
8)short press power on the phone to get in hboot
9)use volume down and then power to select "Recovery"
10)wipe data/factory reset
11)Flash rom

the_Storm said:
Hello guys,
It was my first time to flash a ROM. I tried to install the ROM of [URL="http://forum.xda-developers.com/showthread.php?t=1763240][ROM][Jul 16]Jellybean 4.1.1 for Endeavoru AOSP Build[/URL]
Here is what I did
1)Download ROM from here http://jellybean.tom.gascoigne.me/continuous/tg_endeavoru-ota-15.zip
2)Put them to sdcard
3)wipe data/factory reset
4)Flash rom
5) I rebooted my HTC but the phone never started I am stuck on the neXus logo :S :S It is like infinite booting... so what did I do wrong guys? and how to fix it ??
Thank you
Click to expand...
Click to collapse
Thank you Bro it worked ansI was able to boot and see the home screen but now I have two problems ...
The first one I don't have any apps even google play.. .I think I have to install this Jellybean Gapps "http://jellybean.tom.gascoigne.me/gapps-jb.2.zip"
but I don't have an idea of how to install it like from recovery mood or something ... so how can I install GApps ...
The other problem is that Is there anyway to activate the audio... cause on my jellybean everything is working except the camera and the Audio.. I don't care about the Camera a lot now but the Audio.. I can't even make calls... so do you know anyway to activate the audio ??

the_Storm said:
Thank you Bro it worked ansI was able to boot and see the home screen but now I have two problems ...
The first one I don't have any apps even google play.. .I think I have to install this Jellybean Gapps "http://jellybean.tom.gascoigne.me/gapps-jb.2.zip"
but I don't have an idea of how to install it like from recovery mood or something ... so how can I install GApps ...
The other problem is that Is there anyway to activate the audio... cause on my jellybean everything is working except the camera and the Audio.. I don't care about the Camera a lot now but the Audio.. I can't even make calls... so do you know anyway to activate the audio ??
Click to expand...
Click to collapse
Hey yes you have to download the Gapps zip, place it on the sd-card and then flash it in recovery.
So:
1) Donwnload http://jellybean.tom.gascoigne.me/gapps-jb.2.zip
2) Push the on your sd-card
3) Boot into the recovery
4) Flash zip from sd-card like you chose the rom.zip
5) Reboot
The mic is not working on this Build, but we except a new Version with working Mic for today.
For latest build see here http://jellybean.tom.gascoigne.me/continuous/
Or you try http://forum.xda-developers.com/showthread.php?t=1780005 this rom. Flashing same procedure. This Rom has a working mic

MarcoHD said:
Hey yes you have to download the Gapps zip, place it on the sd-card and then flash it in recovery.
So:
1) Donwnload http://jellybean.tom.gascoigne.me/gapps-jb.2.zip
2) Push the on your sd-card
3) Boot into the recovery
4) Flash zip from sd-card like you chose the rom.zip
5) Reboot
The mic is not working on this Build, but we except a new Version with working Mic for today.
For latest build see here http://jellybean.tom.gascoigne.me/continuous/
Or you try http://forum.xda-developers.com/showthread.php?t=1780005 this rom. Flashing same procedure. This Rom has a working mic
Click to expand...
Click to collapse
Thank you body trying the latest version of the ROM now. I have a small question you said I should flash rom with Gapps to install google apps on the jellybean ROM. For me that doesn't make sense..I mean how the phone will distinguish between gapps and the jellybean ROM itself. Isn't it possible when I flash gapps it overwrites the jellybean ROM itself and I lost the ROM and the phone will not be working?
Again Thank you so much for your help

the_Storm said:
Thank you body trying the latest version of the ROM now. I have a small question you said I should flash rom with Gapps to install google apps on the jellybean ROM. For me that doesn't make sense..I mean how the phone will distinguish between gapps and the jellybean ROM itself. Isn't it possible when I flash gapps it overwrites the jellybean ROM itself and I lost the ROM and the phone will not be working?
Again Thank you so much for your help
Click to expand...
Click to collapse
Nope because the rom will be extracted to the /system partition on your phone. The gapps.zip also but it will not override anything. It will only copy some apps(.apk) to the /system/app .
Thrust me
PC Example: You copy 2 different files to one folder if the files has different names you can copy without overwriting anything

MarcoHD said:
Nope because the rom will be extracted to the /system partition on your phone. The gapps.zip also but it will not override anything. It will only copy some apps(.apk) to the /system/app .
Thrust me
PC Example: You copy 2 different files to one folder if the files has different names you can copy without overwriting anything
Click to expand...
Click to collapse
Thank you bro I will test it tonight...
If you have time would you look at this please
http://forum.xda-developers.com/showthread.php?t=1781182
Thank you ..

MarcoHD said:
Nope because the rom will be extracted to the /system partition on your phone. The gapps.zip also but it will not override anything. It will only copy some apps(.apk) to the /system/app .
Thrust me
PC Example: You copy 2 different files to one folder if the files has different names you can copy without overwriting anything
Click to expand...
Click to collapse
Thanks very much for all of this it will help me a lot when I get round to flashing!

In reference to this, when I'm coming to update to the latest version of this rom, what's the procedure to follow?

Hi,
I'm trying to flash Jellybean 4.1.1 build #27 but it fails no matter what. I have followed the procedure, flashed the rom, erased cache, wiped data/factory reset, rebooted on recovery.
Here's what I get:
-- Install /sdcard/tg_endeavoru-ota-27.zip ...
Finding update package ...
Opening update package ...
Installing update ...
assert failed: getprop("ro.product.device") == "endeavoru" || getprop("ro.build.product") == "endeavoru"
E:Error in /sdcard/tg_endeavoru-ota-27.zip
(Status 7)
* Verifying filesystem...
* Verifying partition sizes...
Error Flashing zip '/sdcard/tg_endeavoru-ota-27.zip'
Failed
Any idea what I could be doing wrong?
Thank you very much in advance for your help.

MarcoHD said:
Nope because the rom will be extracted to the /system partition on your phone. The gapps.zip also but it will not override anything. It will only copy some apps(.apk) to the /system/app .
Thrust me
PC Example: You copy 2 different files to one folder if the files has different names you can copy without overwriting anything
Click to expand...
Click to collapse
I've got JB running on my phone but when I try to boot into recovery to install the apps it won't work. I get the red exclamation mark. I am coming from twrp2.2.0 I followed these instructions
Download the latest CM10 .zip file from here.
Download JB Google Apps from here.
Reboot into CWM or TWRP recovery.
Factory Data reset. (MUST DO THIS!)
Flash CM10 .zip file.
Reboot.
Reboot into recovery.
Flash JB Google apps.
Enjoy!
Any help would be great

jb 4.1.1 how screenshot??
hello All, this is my first quest in this forum. i'have flashed jb 4.1.1 in my device (one x) ad is all ok (wifi go in sleeping mode too fast but when it stand up go well) i need to make a lot of screenshot and i dont know how. Pls help
PS: i think this forum is very usefull for modding android, great work!!!)
Imerio
HavE fUn

MarcoHD said:
Hey yes you have to download the Gapps zip, place it on the sd-card and then flash it in recovery.
So:
1) Donwnload http://jellybean.tom.gascoigne.me/gapps-jb.2.zip
2) Push the on your sd-card
3) Boot into the recovery
4) Flash zip from sd-card like you chose the rom.zip
5) Reboot
The mic is not working on this Build, but we except a new Version with working Mic for today.
For latest build see here http://jellybean.tom.gascoigne.me/continuous/
Or you try http://forum.xda-developers.com/showthread.php?t=1780005 this rom. Flashing same procedure. This Rom has a working mic
Click to expand...
Click to collapse
I love you and thank you. Simple, easy, quick instructions

[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

[p500][CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just long press outside a menu (2 sec and slightly change pressure after the delay)
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
LG Optimus One P500 (p500)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/p500
Click to expand...
Click to collapse
XDA:DevDB Information
[p500][CWM Advanced Edition] PhilZ Touch, a Tool/Utility for the LG Optimus One P500
Contributors
Phil3759
Version Information
Status: Testing
Created 2014-04-21
Last Updated 2014-04-21

Cool.
Upon which CWM version is this based? Note fundamental differences between newer 6.0.* after June 16 -- can flash new Kitkat ROMs and older 5.* which flash older ROMs.
Because of space limitations -- whole business must fit < 5 meg, functionality such as partitioning SDcard was removed from the 6.0.* versions.
What do we have in this version?

Plz update the post with all the features of this recovery... How can we test, if we don't know what to expect???

ujilraj said:
Plz update the post with all the features of this recovery... How can we test, if we don't know what to expect???
Click to expand...
Click to collapse
If you can't read OP and follow links, just do not test
I am fine with this

Unable to flash!
Can't flash the image file by "CWM 6.0.4.6. 16 Jan" recovery by Mukulsoni.Status 7.Please suggest what wrong i did?
1) After d'loading the .image file, i rename it to "recovery" as it in the zipped folder of Mukulsoni recovery.
2) Then i open the zip of Mukulsoni recovery and drag Phil's image file to replace it.
3) Close the zip, put it in the sd card and flash.
4) Status 7 happened.
What should i do? Please help! :crying:

I suggest that the first link needs to highlighted... My mistake, but honestly i didn't notice a link below the title...

sumansur2008 said:
Can't flash the image file by "CWM 6.0.4.6. 16 Jan" recovery by Mukulsoni.Status 7.Please suggest what wrong i did?
1) After d'loading the .image file, i rename it to "recovery" as it in the zipped folder of Mukulsoni recovery.
2) Then i open the zip of Mukulsoni recovery and drag Phil's image file to replace it.
3) Close the zip, put it in the sd card and flash.
4) Status 7 happened.
What should i do? Please help! :crying:
Click to expand...
Click to collapse
This is NOT a flashable zip file!
1. Download, adb push a 6.0.4.6 image file to sdcard (just in case).
2. adb push the PhilZ file to sdcard.
3. In terminal emulator or adb shell (must be rooted):
4. flash_image recovery path-to-file
If it fits and all goes well, you got it.
In case of error, do same for the 6.0.4.6 image and be back in business.

Dovidhalevi said:
This is NOT a flashable zip file!
1. Download, adb push a 6.0.4.6 image file to sdcard (just in case).
2. adb push the PhilZ file to sdcard.
3. In terminal emulator or adb shell (must be rooted):
4. flash_image recovery path-to-file
If it fits and all goes well, you got it.
In case of error, do same for the 6.0.4.6 image and be back in business.
Click to expand...
Click to collapse
I wouldn't suggest anyone do that, I tried to it and almost bricked my phone (long story). I did it before you mentioned this, so it's not your fault. Apparently there isn't enough space in recovery to flash this. I think our recovery has 5mb and this recovery is almost 6mb. I may be wrong with this, but that was the error that showed up when I tried to flash it with flash_image.
It would be safer to suggest to download the recovery, rename it to recovery.img and place it on the root of another recovery zip, overwriting the old recovery, and then trying to flash it. That way, if something happens you will get an error instead of flashing it wrong. But as I said earlier, even if you try you will most likely get a Status 7 error.

indigobv said:
I wouldn't suggest anyone do that, I tried to it and almost bricked my phone (long story). I did it before you mentioned this, so it's not your fault. Apparently there isn't enough space in recovery to flash this. I think our recovery has 5mb and this recovery is almost 6mb. I may be wrong with this, but that was the error that showed up when I tried to flash it with flash_image
Click to expand...
Click to collapse
This should be the error. Then flash_image the 6.0.4.6 which fits. Do it immediately or else .... I believe I had that happen once. I posted about that 5meg limit above. Did not try this because of the limit.
It would be safer to suggest to download the recovery, rename it to recovery.img and place it on the root of another recovery zip, overwriting the old recovery, and then trying to flash it. That way, if something happens you will get an error instead of flashing it wrong. But as I said earlier, even if you try you will most likely get a Status 7 error.
Click to expand...
Click to collapse
Maybe the op should post a proper flashable zip instead. Problem is that status 7 itself might mean a brick.

Dovidhalevi said:
Problem is that status 7 itself might mean a brick.
Click to expand...
Click to collapse
Thanks for the heads up, I actually didn't try booting in recovery after the status 7 error. Now I can confirm that it tries to flash it even if it shows the error and then forces the phone to go in fastboot mode until the problem is solved.

I built using official p500 armv6 repo
They should fix the device recovery size in that case!!

Hi
Recovery Tools will work on LG p500?
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
I See LG optimus me
Because I Want To Flash The Recovery Without Taking Risk

eran32 said:
Hi
Recovery Tools will work on LG p500?
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
I See LG optimus me
Because I Want To Flash The Recovery Without Taking Risk
Click to expand...
Click to collapse
I believe this is simple a nice GUI for flash_image. Aint no such thing as no risk so beware.
The method I suggested should be safe if one flash_image's a valid recovery immediately after any error (but I make no guarantee!).
I advise against flashing this recovery version at this point because it is clearly too big for our device. We can get along just fine without a touch interface if need be. Never had one.
Changing board partition sizes is not a readily done simple matter by any means.

[RECOVERY][2.8.3.0+] TWRP Materialized Play Themed [02-17-15]

Here is a play themed version of the latest TWRP (2.8.3.0). Hope you like it:
(YOU DON"T NEED S-OFF TO USE THIS RECOVERY. ITS THE ORIGINAL TWRP, ONLY THE INTERFACE IS CHANGED)
Features
Recovery gone App: Designed to mimic the look and feel of an Android app.
Customisable UI: 15 different accent colors, center clock option, different navbar button layouts...
Added functionality: built-in ability to flash image files (recovery, radio, boot), bookmark function for file lists, Aroma File Manager support, theme changer (Flash "TWRP-Themed-Zips.zip" at the end of this POST via recovery for these functions to work properly)...
Availability and Compatibility
HTC One M7 International (Did not check with other versions yet, Anyone who has the guts to check it please check it and reply? )
How to install:
You need to be S-OFF OR have taken HTC's unlock to use a recovery on your device!
Fastboot method:
Download the file below.
Put the file on your adb directory.
Reboot into fastboot mode (Bootloader)
On fastboot mode do " fastboot flash recovery twrp-2.8.3.0-m7-themed.img " (without quotes OFC)
Tadaa, Restart to recovery.
Flashify Method:
Download the img file and copy it to the phone.
Open Flashify App.
Click "Recovery Image".
Click "Choose a file"
Select the img file you downloaded
Click "Normal Android Way"
Click "Yup". Done!
Download:
twrp-2.8.3.0-m7-themed.img
TWRP-Themed-Zips.zip (Optional Flashable zip file at the end of this POST. Flash this file from recovery if you want added functions to work properly.
Thank you. Hope you enjoy it
Credits:
TeamWin
z31s1g - For this is originally his theme. I just put it in the image file and compiled (Original Theme Post)
Special Thanks
D2Dchris
Sebby
XDA:DevDB Information
Materialized Play Themed TWRP Recovery for M7, Tool/Utility for the HTC One
Contributors
driverless, Sebby, Onefast
Version Information
Status: Stable
Created 2014-12-30
Last Updated 2015-02-16

Thanks will check

Great
Works good, looks great!
Confirmed to be flashable with the flashify app.

built-in ability to flash image files
this function does not work
it repacked de image but it did not flash
i tryed to rename the recovery to recovery.img but still did not work
it is maybe a good idea to provide the zip files or what must be in the directory's of twrp dir
i tryed also the aik mobile installer zip what must be provided but it only repacked not flashed the image
or does this option only work on the nexus

Sebby said:
built-in ability to flash image files
this function does not work
it repacked de image but it did not flash
i tryed to rename the recovery to recovery.img but still did not work
it is maybe a good idea to provide the zip files or what must be in the directory's of twrp dir
i tryed also the aik mobile installer zip what must be provided but it only repacked not flashed the image
or does this option only work on the nexus
Click to expand...
Click to collapse
I thought it was because I have an S-ON device >.< Okai I will check this feature more and do something about it. I guess I will release another version soon than (Will provide zips if required ). :3
Thank you for reporting .

driverless said:
I thought it was because I have an S-ON device >.< Okai I will check this feature more and do something about it. I guess I will release another version soon than (Will provide zips if required ). :3
Thank you for reporting .
Click to expand...
Click to collapse
i have s-off

Unable to see the screenshots

Fix Attached
Sebby said:
i have s-off
Click to expand...
Click to collapse
Its fixed. You can flash the TWRP-Themed-Zips.zip on the first POST. (Works without S-OFF)
Thank you
ruubs said:
Unable to see the screenshots
Click to expand...
Click to collapse
Screenies now added to the first POST

Working with UL 1.57 S-ON, love it thanks!

Great work, thank you!!

Awesome theme. Thanks for sharing.

Awesome Work,now also in recovery the L Style!!! Love iit!!
Thanks :good: and Happy NEW Year.

oke i tryed it again and it works now
big thanks from me :good::good::good:

This is amazing, thanks!

Glade that you guys like it ^_^

Great work, thx!

We have to install the zip on top of current recovery. I am on the latest twrp and just from install zip from sd card install it and will work.???

number one twrp theme in the last year!!!
another Thanks!!!!

The recovery looks beautiful. Really nice.
One drawback: system does not boot anymore, hangs on the boot screen forever.
M7 GPE, Lollipop 5.0.1.

Nicely done! Thank you very much.