[RECOVERY][N8000/N8013]CWM 6.0.4.4{Fully Working} - Galaxy Note 10.1 Original Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer:
By flashing this recovery you take full responsibility to whatever happens on your device. The developer will NOT be held responsible to whatever happens on your device. Ofcourse, the recovery has been tested but whatever happens on your device will not be held against the developer.
​What Is CWM Recovery ?
CWM recovery is a way that enables you to falsh a custom rom , customize your rom and can save you from bad situations. To Be fully in controll of your android device you need a recovery and this is one of them.​How To Install CWM Recovery ?
There are 2 methods for installing CWM
1.Method (dd method)
You need root before you continue.
now copy recovery.img from second post to your sd card and :
1.On PC :
Make shure that device is on usb debugging mode.
Plug device and open Terminal/command prompt.
Copy Pasta the Following Commands :
PHP:
adb shell
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6
make shure that partion is mmcblk0p6 or you will brick device !
now you can reboot to recovery (volume up + home +power) and enjoy CWM 6.0.4.4
2.On Phone :
First Download Terminal Emulator From Play Store.
Plug device and open Terminal apk
Right the Following Commands :
PHP:
su (you need root acess for it )
Then
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6
make shure that partion is mmcblk0p6 or you will brick device !(guys with fat fingers stay away !)
now you can reboot to recovery (volume up + home +power) and enjoy CWM 6.0.3.3
Second Method Is Via ODIN.
First Download ODIN
Now Download the N8000/N8013-CWM-6.0.4.4.tar From Second Post and put it in same directory as odin.
Go To Download Mod (Volume Down +Home+Power) and plug device.
Now in Odin You Will see {added} and a light blue figure on top that means that device has been recognized if you dont get them uninstall devices drivers and retry.
Now click PDA and select N8000/N8013-CWM-6.0.4.4.tar And Then Click Start .
After Device reboots Your Done and CWM Is Flashed.​Thanks To :
CM Team For CWM recovery .
@Dees_Troy @bigbiff @anders3408 @cybojenix @invisiblek {These Guys Are The Best And I Thank Them for helping me every step in the way and not thinking that i am a nut job }​​
Please Hit The Thanks Button If You Like My Work
Follow Me On Twitter SamerDKingCobra
If You Have Any Kind Of Trouble Feel Free To PM Me As I Am Here Almost 19 Hours A Day.​

Downloads And Q&A
Downloads :
1.IMAGES
N8000-CWM-6.0.4.4.img {For dd Method , Please rename to recovery.img }
N8013-CWM-6.0.4.4.img {For dd Method , Please rename to recovery.img }
2.TAR FILES
N8000-CWM-6.0.4.4.tar Build #1 {For Odin}
N8013-CWM-6.0.4.4.tar Build #1 {For Odin}
Change Log :
Build #1 Fully Working.​Whats To Do In Future Build ?
Enable Touch .
Add OTG Support.​FAQ:{Please Read Before Posting}
Q: OMG ! Recovey Not Booting What To Do ?
Alease Dont try entering recovery first time from advanced power menu just do it the hard way
Q:My Device is not getting read by windows ?
A:Uninstall all drivers that you installed for the device .​​​Please Hit The Thanks Button If You Like My Work
Follow Me On Twitter SamerDKingCobra
If You Have Any Kind Of Trouble Feel Free To PM Me As I Am Here Almost 19 Hours A Day.​

For Later Use

it can't mount the external sd

iRoNX said:
it can't mount the external sd
Click to expand...
Click to collapse
seriously i did not notice such error, i will see what i can do tomrrow Thanks

First, PC odin couldn't flash the device with this recovery (Odin 3.7, PC Win 8.1 x64, Odin works fine with it, checked many times).
After flashing this recovery from terminal it cannot boot by some reasons, and i'm rebooted the device with terminal command "reboot recovery", and i get the bootloop with the orange styled frame of "CWM-based recovery 6.0.4.4", then i reflashed the old version with odin.
P.S. My ROM is ARHD. Device: N8000.

Shmong said:
First, PC odin couldn't flash the device with this recovery (Odin 3.7, PC Win 8.1 x64, Odin works fine with it, checked many times).
After flashing this recovery from terminal it cannot boot by some reasons, and i'm rebooted the device with terminal command "reboot recovery", and i get the bootloop with the orange styled frame of "CWM-based recovery 6.0.4.4", then i reflashed the old version with odin.
P.S. My ROM is ARHD. Device: N8000.
Click to expand...
Click to collapse
Well thats odd :/ are you sure you have n8000 build not n8013 as i am recovery fine

Yes, i'm pretty sure. I've tried to do this few times via both terminal and odin. Now will try one more time...
UPD: I've repacked the img file with the tar archiver+ put md5 checksum (tar.md5) and flashed it with odin successfully.
And like iRoNX said it can't mount extSD: "error mounting /storage/sdcard1"
UPD2: The recovery from similar thread have another issue: cannot format "/data" and cannot explore internal flash )))

Shmong said:
First, PC odin couldn't flash the device with this recovery (Odin 3.7, PC Win 8.1 x64, Odin works fine with it, checked many times).
After flashing this recovery from terminal it cannot boot by some reasons, and i'm rebooted the device with terminal command "reboot recovery", and i get the bootloop with the orange styled frame of "CWM-based recovery 6.0.4.4", then i reflashed the old version with odin.
P.S. My ROM is ARHD. Device: N8000.
Click to expand...
Click to collapse
+1.
The Odin tar file is not OK. Although I did not get a bootloop, the indicator on phone in download mode goes to the end and then stays there at "NAND write". I has to disconnect the phone and reboot manually, and my old version of CWM was still there (phew!). The .img files and dd worked fine.
Thanks anyways for this update !!!! It worked to get me on JB 4.4 !
Update: When phone is powered off and charger connected, upon starting there is a garbled green image that comes on for several seconds - most likely the battery charging icon - and then the phone will start up. It was not there before flashing 6.0.4.4. Anyways my phone does start up........

Tar file not working.. gets stuck at "Nandwrite"

Thanks for the recovery, I made it into CWM zip files so you can flash in CWM or TWRP here:
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/GT-N8000-CWM-Recovery-v6.0.4.4.zip
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/GT-N8013-CWM-Recovery-v6.0.4.4.zip

zedomax said:
Thanks for the recovery, I made it into CWM zip files so you can flash in CWM or TWRP here:
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/GT-N8000-CWM-Recovery-v6.0.4.4.zip
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/GT-N8013-CWM-Recovery-v6.0.4.4.zip
Click to expand...
Click to collapse
Way to go, champion !!

Flashed but the external SD card doesn't work
Sent from my GT_N8000

ODIN Image file attached.
Hello,
The N8013 Odin file in the 1st post does not work as some mentioned in comments. I went ahead and created a proper Odin package from the other images which I am attaching for anyone who needs it. Please unrar and you'll find the .tar.md5 file to use with Odin.
Cheers,
L

SD cards problem
Hello again,
Within this version of CWM, the SD card problem seems to be only for the 64g cards as tested on my N8013. However, after you flash the Rom you'll using, there is no problem with 64g cards outside of CWM recovery mode.
Smaller sized cards 32g and less will mount fine while you are in CWM recovery mode.
Cheers,
L

lobo25 said:
Hello,
The N8013 Odin file in the 1st post does not work as some mentioned in comments. I went ahead and created a proper Odin package from the other images which I am attaching for anyone who needs it. Please unrar and you'll find the .tar.md5 file to use with Odin.
Cheers,
L
Click to expand...
Click to collapse
Not working for me... says img. file is invalid. then ends.

Love it. Thanks.

lobo25 said:
Hello,
The N8013 Odin file in the 1st post does not work as some mentioned in comments. I went ahead and created a proper Odin package from the other images which I am attaching for anyone who needs it. Please unrar and you'll find the .tar.md5 file to use with Odin.
Cheers,
L
Click to expand...
Click to collapse
Anyone confirm this as working?
Edit: Not working. Odin says invalid.

missing file
I seem to have lost my \efs folder, and in searching for a solution one of the steps I'm told to take is to flash "N8000-CWM-6.0.4.4.tar". However, it doesn't seem to exist anywhere (now that goo is gone), other than in this thread and the version here seems to be broken. Does anyone have the N8000 version of the .tar file?

Boot-loop, can't wipe device.
Hey everyone. I'm not exactly sure what happened, but it seems that my GT-N8000 is on the fritz again. The device was screen-off this morning (I left home) and when I came home it was in a reboot loop.
I jumped into recovery (CWM v6.0.4.4) to try to wipe both cache and dalvik (both successful) and rebooted. Same bootloop.
So then I decided to wipe the storage and reinstall the ROM (Gnabo v8 is what I had been running). When I attempt to "wipe data/factory reset", it says "formatting data . . ." and then reboots into the bootloop again.
Then I thought that maybe it was wiped, so I attempted to flash Gnabo. It installs successfully (Installing update, blue bar goes across, "Enjoy!" and "Install from sdcard complete."), however, when the installation starts, I get the first box and then it sits for almost 2 minutes before the blue bar appears, fills in just a few quick seconds, and then displays the completed message. It seems to me that the installation and the blue bar should be taking longer, but what do I know. Anyway, I rebooted (No, don't fix ROM flasing stock recovery on reboot), then back into the bootloop. So I'm still losing.
I don't know if it's related, but some months ago I had something similar happen in that the device was in a bootloop and it turned out that it had somehow lost the /efs folder. I had restored that (thanks XDA forums!) and it had been working fine since about June 2015.
I'm starting to think that my memory has gone bad, and that I basically have a 10.1 inch paperweight. Suggestions? Thanks for any help you can provide.

Related

[RECOVERY] [02/02/12] ClockworkMod [5.0.2.0 and 5.8.1.0] ~Touch Version Added~

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All credit for this software goes to the dev (Koushik Dutta and anyone else on his team).
** Nandroid backups made on previous versions of CWM cannot be restored in CWM 5.0.x.x. So if you have backups made in versions 2.5.x.x or 3.0.x.x, you will not be able to restore them once you've upgraded. **
HOMEPAGE
ClockworkMod.com
DOWNLOAD
Standard recovery
Link: recovery-clockwork-5.0.2.0-glacier.img - Rename to "recovery.img" for easier CLI entry
MD5: a5aea82ec2ad7b836c9c179fce0d520d - To verify, use ManD5 or the below ADB commands:
Touch recovery
Link: recovery-clockwork-touch-5.8.1.0-glacier.img - Rename to "recovery.img" for easier CLI entry
MD5: 687998d5093878147256c10ae9e98e5a - To verify, use ManD5 or these ADB commands:
Code:
adb push recovery.img /sdcard/recovery.img
adb shell md5sum /sdcard/recovery.img
INSTALLATION
- Via the ROM Manager app (version 4.4.0.3 or newer required)
- Via terminal emulator:
Code:
Move recovery.img to the root of your sdcard
Start the terminal app
su (press enter)
flash_image recovery /sdcard/recovery.img (press enter)
reboot recovery (press enter)
- Via fastboot (ADB installation and engineering bootloader version 0.85.2007 required):
Code:
Move recovery.img to a location where fastboot can find it.
Boot your phone into fastboot mode
Connect your phone via USB to your computer
fastboot devices
fastboot flash recovery recovery.img
CHANGE-LOG
5.0.0.1 through 5.0.1.0
Backups now use tar over yaffs for everything except mtd partitions. Backup speed improved.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type.
New color scheme
Status bar when backing up working again
Backing up of .android_secure working again
5.0.2.0
Bug-fix: root no longer lost on rom restore
5.8.0.9
Touch version - initial release (beta stage)
5.8.1.0
Major bug fixed (recovery.fstab malformed)
I'm not in any way responsible if something happens to your device. I'm simply posting this as a courtesy to the community.
I still don't know how this flew over our heads.
Either way, glad you provided every possible method to upgrade.
mackster248 said:
I still don't know how this flew over our heads.
Either way, glad you provided every possible method to upgrade.
Click to expand...
Click to collapse
Was there a 4.0? I was still on 3.0.24 still, and now I find out about this version. does anyone know its new features?
Ace42 said:
Was there a 4.0? I was still on 3.0.24 still, and now I find out about this version. does anyone know its new features?
Click to expand...
Click to collapse
As far as I know, the jump was made straight from 3.0.2.4 to 5.0.0.1. I have yet to see a changelog, but if anyone finds one, I'll add it to the OP. After poking through the menus, nothing obvious stood out, so it seems to be a bug fix and "behind the scenes" release.
-From Mr.Dutta via G+
I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!
Thanks for the heads up. Just flashed via rom manager without any issues.
I decided to flash the upgrade. The flash went perfectly. However, I can't boot into recovery while within Android. I have to power off and boot into the bootloader and then select recovery... Whenever I try to reboot to recovery via the Android UI, it reboots and hangs at the boot splash screen.. It doesn't even work if you select the option from the ROM Manager itself just hangs... I rolled back to previous version and its working again...
Possible bug??...
epolaris said:
I decided to flash the upgrade. The flash went perfectly. However, I can't boot into recovery while within Android. I have to power off and boot into the bootloader and then select recovery... Whenever I try to reboot to recovery via the Android UI, it reboots and hangs at the boot splash screen.. It doesn't even work if you select the option from the ROM Manager itself just hangs... I rolled back to previous version and its working again...
Possible bug??...
Click to expand...
Click to collapse
I'm not quite sure if that's a bug. Since there's a lot of internal changes, I'm assuming the path it takes from Android to CWM has changed. So maybe that's why we're stuck at the splash screen.
But that's not too big of a problem. So far it's much faster than the previous versions.
WOW! I just did a backup of my current Rom and it literally took like 1 minute! It's WAY faster now.
epolaris said:
I decided to flash the upgrade. The flash went perfectly. However, I can't boot into recovery while within Android. I have to power off and boot into the bootloader and then select recovery... Whenever I try to reboot to recovery via the Android UI, it reboots and hangs at the boot splash screen.. It doesn't even work if you select the option from the ROM Manager itself just hangs... I rolled back to previous version and its working again...
Possible bug??...
Click to expand...
Click to collapse
I'm not having that issue at all. I can reboot into recovery using the power menu within Faux's 1.3.1 rom and it works perfectly. I can't speak about other roms, but just letting you all know that Faux's latest works fine.
<EDIT EDIT>
lol wrong forum.
updated to 5.0.0.1. seems pretty neat.
This new recovery backs up roms really fast. With the old version it used to take my phone 2 to 3 minutes to back up. Now about a minute. Its actually kind of scaring me. I don't know if its backing it up correctly. I'm affraid to restore lol.
Sent from my HTC Glacier using xda premium
coupetastic-droid said:
This new recovery backs up roms really fast. With the old version it used to take my phone 2 to 3 minutes to back up. Now about a minute. Its actually kind of scaring me. I don't know if its backing it up correctly. I'm affraid to restore lol.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I posted the changelog on the 1st page.
"I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!"
I also added the info from his Google+ page to the OP.
Any information on whether other built in tools such as sdparted were updated too? I have been having a lot of trouble with my SD card (I couldn't get it to format through sdparted because of some error I can't remember) and the option to partition your SD card through ClockWorkMod Recovery 3.x didn't allow to set EXT to a size of 0. I was able to partition my card the way I wanted through sdparted after flashing the new 5.0.0.1 recovery, but was curious as to whether there was a change within the recovery img that allowed me to finally partition the way I wanted or if the change was something else that caused my SD card to start functioning correctly.
bstapley said:
I'm not having that issue at all. I can reboot into recovery using the power menu within Faux's 1.3.1 rom and it works perfectly. I can't speak about other roms, but just letting you all know that Faux's latest works fine.
Click to expand...
Click to collapse
+1 Same here
Sent from my HTC Glacier using XDA Premium App
Ace42 said:
I posted the changelog on the 1st page.
"I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!"
Click to expand...
Click to collapse
just did a restore and everything went perfectly fine. thanx.
I was just wondering that when I flash a rom and it calls for 3.0.2.4 recovery do I still use that or can I use the new recovery..I know it's a dumb question but just want to make sure
Sent from my virtuous doubleshot glacier using XDA App
darksoul0013 said:
I was just wondering that when I flash a rom and it calls for 3.0.2.4 recovery do I still use that or can I use the new recovery..I know it's a dumb question but just want to make sure
Click to expand...
Click to collapse
Shouldn't be a problem. Nothing was changed that would make affect how a ROM is flashed.

[Q] Flashing rom

hi,
my phone freezed the other time after wiping (becasue I had a screen issue ) and glevitan helpfully flashed an unbranded rom back ( with the hack kit or something ) .
I fixed my screen so there shouldn't be any issues now and just wasn't too sure about flashing to get back my previous rom.
details of phone now
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I checked my SD card and there's a clockworkmod folder with the files .android_secure.vfat (357,525 KB RAR) ,cache.ext4 ( 5KB RAR) , data.ext4 ( 489,783 RAR) , system.ext4 ( 424,852 KB RAR) , boot.img ( 4,096 KB IMG file) , fsinfo (1 KB file), nandroid.md5 (1 KB MD5 file) , recovery.img ( 8,701KB IMG file ) . anything i can do with them? they were the backup I did prior to my wiping disaster earlier.
I also have an ARHD 6.3.3 rom zip on my SD card too.
my volume button is spoilt. I installed 4Ext touch recovery , wanted to update it and it mentioned it needs busybox box from google play , which in turn requires root. So I can just download that , update the 4Ext touch recovery for use ?
thanks !
this too if it's of any use
I'm assuming you flashed 4ext from fastboot? You could restore your CWM backup from 4ext (I'm assuming that your 4ext isn't so old that the backup isn't compatible). Then you would have a rooted ROM. Or clean flash your ARHD.
no, I didnt flash the 4Ext from fastboot. I installed the 4Ext apk as per normal on my SD card after I got my screen repaired. It wasn't really outdated ( probably last month), but actually I can uninstall this and get a new copy from the site and install that too. Do I still have to download busybox or SuperSu , then clean flash the ARHD copy on my SD card ?
If you still have a custom recovery, go ahead and try to restore the backup. Or if you flash ARHD it is already rooted with busy box.
oh, so if I'm doing a clean flash of that arhd , I can use the 4ext recovery to wipe and then flash that without needing to download anything else ? thanks
whateheck said:
oh, so if I'm doing a clean flash of that arhd , I can use the 4ext recovery to wipe and then flash that without needing to download anything else ? thanks
Click to expand...
Click to collapse
Yes.
Here's how you install 4ext: http://www.youtube.com/watch?v=Ih5orslc-4M
If you want you can install a CWM touch recovery instead and do everything as before on the original CWM only no need for the volume keys.
You can install CWM with this app form the market very easily: https://play.google.com/store/apps/details?id=com.simran.recmanager&feature=search_result
After doing that when you want to install a new ROM do a full wipe and flash on! Good luck!
i think it'll ask me to install busybox too if I click on update etc.
So I should be good to go from there ?
otherwise I'll have to have a go at the CWM. you mean to install by flashing cwm touch recovery from the Recovery Manage app, ilans93 ? I haven't used this before - just looked at the page and it's last updated was Feb last year.
I'm not sure if you still have a custom recovery. You could check by connecting your phone to your computer and using adb: adb reboot recovery.
If you don't, you need to fastboot flash a recovery first. Check the DHD General forums, Ace Think Tank guide, bottom of page 9, the section "S-Off no custom recovery." If you want 4ext download the image from their website and use that instead of the CWM image. Then flash ARHD from the recovery.
bananagranola said:
I'm not sure if you still have a custom recovery. You could check by connecting your phone to your computer and using adb: adb reboot recovery.
If you don't, you need to fastboot flash a recovery first. Check the DHD General forums, Ace Think Tank guide, bottom of page 9, the section "S-Off no custom recovery." If you want 4ext download the image from their website and use that instead of the CWM image. Then flash ARHD from the recovery.
Click to expand...
Click to collapse
yes, I should have the custom recovery. as mentioned in 1st post , I have a folder on my SD card "clockworkmod" with the files .android_secure.vfat (357,525 KB RAR) ,cache.ext4 ( 5KB RAR) , data.ext4 ( 489,783 RAR) , system.ext4 ( 424,852 KB RAR) , boot.img ( 4,096 KB IMG file) , fsinfo (1 KB file), nandroid.md5 (1 KB MD5 file) , recovery.img ( 8,701KB IMG file ). that's the backup my previous 4ext did before I wiped and got stuck that time.
So i have to copy the recovery.img file to the PC adb folder and flash it ?
whateheck said:
yes, I should have the custom recovery. as mentioned in 1st post , I have a folder on my SD card "clockworkmod" with the files .android_secure.vfat (357,525 KB RAR) ,cache.ext4 ( 5KB RAR) , data.ext4 ( 489,783 RAR) , system.ext4 ( 424,852 KB RAR) , boot.img ( 4,096 KB IMG file) , fsinfo (1 KB file), nandroid.md5 (1 KB MD5 file) , recovery.img ( 8,701KB IMG file ). that's the backup my previous 4ext did before I wiped and got stuck that time.
So i have to copy the recovery.img file to the PC adb folder and flash it ?
Click to expand...
Click to collapse
Thats the backup file, and it is located at /sdcard/clockworkmod/backup, but in order for you to be able to restore the backup, you must have recovery.. like bananagranola said, you need to flash the recovery first if you didnt have it, or just go to the recovery ( ext4 recovery or cwm depends on what you have installed) and restore the backup..
whateheck said:
otherwise I'll have to have a go at the CWM. you mean to install by flashing cwm touch recovery from the Recovery Manage app, ilans93 ? I haven't used this before - just looked at the page and it's last updated was Feb last year.
Click to expand...
Click to collapse
Exactly. The app does everything for you. There is no need to update the market app because it works perfectly, he only updates the online databases. Trust me, everything is up to date.
Note that the CWM touch can't install the new ViperDHD 2.0.0 ROM. For that you'll need 4ext or TWRP. I switched to TWRP and it's pretty good. I recommend you install it.
The way you install TWRP as easily as possible is to download GooManager from the Play Store (https://play.google.com/store/apps/...251bGwsMSwxLDEsImNvbS5zMHVwLmdvb21hbmFnZXIiXQ..) , run the app, hit menu and select "Install OpenRecoveryScript".
ilans93 said:
Exactly. The app does everything for you. There is no need to update the market app because it works perfectly, he only updates the online databases. Trust me, everything is up to date.
Note that the CWM touch can't install the new ViperDHD 2.0.0 ROM. For that you'll need 4ext or TWRP. I switched to TWRP and it's pretty good. I recommend you install it.
The way you install TWRP as easily as possible is to download GooManager from the Play Store (https://play.google.com/store/apps/...251bGwsMSwxLDEsImNvbS5zMHVwLmdvb21hbmFnZXIiXQ..) , run the app, hit menu and select "Install OpenRecoveryScript".
Click to expand...
Click to collapse
does that recovery manager require root ? i'm only S-off i suppose. (and without volume button )
yumm91 said:
Thats the backup file, and it is located at /sdcard/clockworkmod/backup, but in order for you to be able to restore the backup, you must have recovery.. like bananagranola said, you need to flash the recovery first if you didnt have it, or just go to the recovery ( ext4 recovery or cwm depends on what you have installed) and restore the backup..
Click to expand...
Click to collapse
oh , realised my mistake
bananagranola said:
I'm not sure if you still have a custom recovery. You could check by connecting your phone to your computer and using adb: adb reboot recovery.
If you don't, you need to fastboot flash a recovery first. Check the DHD General forums, Ace Think Tank guide, bottom of page 9, the section "S-Off no custom recovery." If you want 4ext download the image from their website and use that instead of the CWM image. Then flash ARHD from the recovery.
Click to expand...
Click to collapse
tried adb reboot recovery and I indeed didnt have custom recovery. it rebooted and I got a factory reset phone back - had to relog google market etc.
you mean to look at gevitan's ace guide , isn't it - i was looking at the pg 9 thread for a while and saw nothing related ( default forum number of posts per page ) , then realised gevitan's guide on pg 9 for "14. Stuck in the splash screen " seemed more probable .
"
S-OFF with custom recovery: Get a custom rom in your sdcard and flash it.
S-OFF no custom recovery: You need to re flash a custom recovery to be able to flash a custom rom again. Follow these steps:
1) Boot in hboot and choose fastboot.
2) Plug the phone to the pc (you have to see fastboot usb in red in the phone)
3) Open a cmd as admin or terminal as root in the PC.
4) Type (case sensitive):
5) wget http://db.tt/YV7fTEx7 --no-check-certificate (wait until the download is ready)
6) Fastboot oem rebootRUU (that will put your phone in RUU mode, with a black screen with silver HTC)
7) Fastboot flash zipcwm-5.0.2.7-ace.zip (it will send the file first and then flash it)
8) When you see OKAY. Finished (near the bottom in the cmd session even if the green bar in the phone is at half way)
9) Fastboot reboot-bootloader.
10) VOILÁ…check and you should have CWM again.
"
the DB link expired , but in any case, I need a touch recovery since my volume button can't work.
I looked around and saw this thread on CWM touch recovery : http://forum.xda-developers.com/showthread.php?t=1474490
then again, the steps are slightly different too - I'm not too sure about the ENG s-off and whatnot.
but if i follow gevitan's guide, I should need a CWM touch in "zip" file format ? i looked at the CWM site and it only has the img file - do i need to change anything ?
thanks!
Edit: I was wrong. See the link below for the correct way.
http://forum.xda-developers.com/showthread.php?p=37630169

How to unlock bootloader on Note 2

Hi there,
This may seem like a daft question but i have just rooted my Note 2 using Odin and i went ahead and installed CWM from the play store.
However, i don't seem to have the option of making a backup of my current ROM.
All it gives me is (in blue)
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache.
This worked on my HTC One X, am i doing something wrong? My Note 2 was purchased as SIM free from phones4u.
I'm on android version 4.1.2, baseband version N7100XXDLK7, BUILD NO. JZO54K.N7100XXDMB2., MODEL NO. GT-N7100.
Could my bootloader still be locked? Is this causing the issue?
Any help would be much appreciated!
Just flash CWM/TWRP recovery.
Here is one of it
http://forum.xda-developers.com/showthread.php?t=2028103
Loading default android recovery even though TWRP successfully installed
Hi,
I am not sure if I should've started a separate thread for this, please move this if this has to be a separate thread but I've mentioned below why I am posting here.
My phone Galaxy note 2 International version GSM is rooted and I installed TWRP through Goomanager and I got a message stating that "Recovery was successfully installed". After this I shut down the phone and pressed Volume up + Home + Power to go into recovery mode and it still goes into the Android default recovery mode. I tried installing it again and still faced the same issue.
Since I was having a problem, I thought I will install TWRP through Odim 3.7. So, I connect PC to my phone and downloaded the openrecovery-twrp-2.3.1.1-n7100.img.tar.md5 and opened Odim in administrator mode and clicked on PDA >> Start. Within a second I got an error stating "odin downloader has stopped working". I went to task manager and shut down Samsung KIES and tried again but still got the same error.
Next, I tried using the Samsung Note 2 Toolkit. Before I installed TWRP through option 5 in the toolkit, I wanted to Rename Recovery Restore files (if present) as suggested by the toolkit. When I chose this option, I get an error stating adbd cannot run as root in production builds. When I googled this error, it went to a post which said that the bootloader needs to be unlocked.
But then the previous post says that I need TWRP for unlocking the bootloader and I'm doing all this to first of all install TWRP.
Apart from this, as additional Info, when I open ROM Manager - Under Recovery Setup - Current Recovery is Team Win Recovery Project. When I choose to reboot in Recovery mode from the application, it goes to the Android System Recovery. No matter what I do, TWRP recovery just does not seem to open up.
I'm pretty clueless now as to what other options I have or if I have messed up somewhere
Any suggestions would be appreciated.
Thank you
its already unlocked :good:
all u need costume recovery ( TWRP or CWM )
TWRP is far better IMO
http://forum.xda-developers.com/showthread.php?t=1938733
yahyoh said:
its already unlocked :good:
all u need costume recovery ( TWRP or CWM )
TWRP is far better IMO
http://forum.xda-developers.com/showthread.php?t=1938733
Click to expand...
Click to collapse
Hi yahyoh -
The problem as I've described in my post is that I am unable to go into TWRP Recovery mode, I've installed the scripts using goomanager several times but when I shut down the phone and press volume up + Home + Power, it goes to Android Recovery mode and not the TWRP Recovery mode.
gr8one said:
Hi yahyoh -
The problem as I've described in my post is that I am unable to go into TWRP Recovery mode, I've installed the scripts using goomanager several times but when I shut down the phone and press volume up + Home + Power, it goes to Android Recovery mode and not the TWRP Recovery mode.
Click to expand...
Click to collapse
ok forgot goomanager it never worked for me
just download the tar version open odin put it in PDA put ur note 2 in download mode and connect it to ur pc wait for the blue color to show on ID:COM and press start
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
( and make sure kies is fully closed )
Tried that
yahyoh said:
ok forgot goomanager it never worked for me
just download the tar version open odin put it in PDA put ur note 2 in download mode and connect it to ur pc wait for the blue color to show on ID:COM and press start
( and make sure kies is fully closed )
Click to expand...
Click to collapse
Yahyoh,
Thank you for your response but if you see my original post, I have mentioned that I had already tried Odin 3.7 and put my phone in download mode and got the blue color showing ID: COM but when I pressed start, Odin gave an error stating odin downloader has stopped working and the only dialog box was to close. So, once I press START, I get a error message in a second and have to shut down. I did make sure that I have the correct tar version as I downloaded from TWRP's website directly for N7100. I did make sure that Kies was also closed.
After this I tried using Toolkit and that didn't help as well. Kinda going crazy why such a simple thing is getting to become a irritating problem, been sitting on this for the past 4 hours.
try to run odin as administrator
ran odin as administrator
yahyoh said:
try to run odin as administrator
Click to expand...
Click to collapse
Yes. I did run odin as administrator all the time.
try on another PC ? try to download odin again ? try another cable ?
yahyoh said:
try on another PC ? try to download odin again ? try another cable ?
Click to expand...
Click to collapse
I have tried downloading odin 4 or 5 times. The cable I have is brand new samsung cable. Right now, I dont have another pc but might have to go to a friends and try if that helps. I do have a mac but not sure if there is mac version of odin. I'm attaching a picture of what I see when I press volume up + home+power.
abhijitdroid said:
Hi,
1. Check that USB drivers are properly installed.
2. Your USB cable is proper and allows you to charge your phone as well as copy data from your PC.
3. Change USB port and try again. (This has worked in my case)
Click to expand...
Click to collapse
Usb drivers are installed properly. PC reads the phone as soon as itd connected. Tried three different usb ports that is available in my laptop. The phone does get charged when it's connected and I'm able to transfer data. Only thing left to try is a different pc.
Since ur already rooted, y not flash via mobile odin app? Untar to internal storage and rename the twrp image to recovery.img (btw theres a newer v2.5.0.2) and let mobile odin look for it.
Or u can dump the image directly to ur recovery partition using terminal apps:
Code:
su;
dd if=/storage/sdcard0/recovery.img of=/dev/block/mmcblk0p9 bs=4096;
sleep 5;
reboot;
Nazar78 said:
Since ur already rooted, y not flash via mobile odin app? Untar to internal storage and rename the twrp image to recovery.img (btw theres a newer v2.5.0.2) and let mobile odin look for it.
Or u can dump the image directly to ur recovery partition using terminal apps:
Code:
su;
dd if=/storage/sdcard0/recovery.img of=/dev/block/mmcblk0p9 bs=4096;
sleep 5;
reboot;
Click to expand...
Click to collapse
Hi Nazar78,
Mobile odin app is not free, it needs to be purchased. I already have the twrp image in the internal storage and was looking around if there was a free version of mobile odin app somewhere but couldn't find it.
I do not know how to use terminal apps and not familiar with the commands etc. So didn't wanna try that and mess it up. As a temporary solution I have installed CWM latest version using Rom manager but TWRP would be much better as it seems to be more user friendly.
If you could tell me how to enter this terminal apps page, I will probably follow the codes you have given and see if that helps.
Thanks
just install Android Terminal : https://play.google.com/store/apps/...251bGwsMSwxLDEsImphY2twYWwuYW5kcm9pZHRlcm0iXQ..
then type via keyboard what @Nazar78 wrote in the terminal
Just download any free terminal emulator app from play store and enter those commands per line each.
Btw u mentioned previously about adbd can't run on prod builds, its because the adbd binary in ur rom is stock, u need a patched one. Look for app called adbd insecure by CF. Or any custom builds should do the trick...
To flash recovery, tou need not to have paid version of mobile odin
Wait updating this post with link
Edit : here is mobile odin lite
http://forum.xda-developers.com/showthread.php?t=1347899
Download attached mobile odin lite from post 1
Then download flasher kernel from post 7
(download 5.0 versiin) and install
Then open mobile odin Select recovery tab, point to recovery file (tar/img) and flash
Sent from my GT-N7100 using xda premium
Thank you
Thanks Nazar78, Yahoyoh and Ketan, It's about 1:30am now, so I'm gonna shut down now and try these tomorrow. WIll get back with updates. Appreciate.
Also if you have installed EMET, a Microsoft software to stop security exploits, disable it.
It's cause me issues in the past.
I've also seen reports of people not having odin running properly when the kies process runs in the background. This was always the case when flashing with the Galaxy s, and might be a rare occurance with the note 2 too.
Sent from my GT-N7100 using Tapatalk 2

[MEGA]Titanium S1,Cherry Flame2.0,KTouch U86 Kiss,Archos 45 Platinum

Hello Everybody!!
Recently when going through the xda forums for the devices Karbonn Titanium S1, Cherry Mobile Flame 2.0, K-Touch Hornet u86 kiss , I noticed that a lot of people have questions regarding Stock rom, Recovery rooting and Solutions for Brick.However most of the posts have been left unanswered or died for some reason.
Hence I decided to open a thread that can be used to solve general problems and issues regarding the Device.
NOTE:- Archos 45 Platinum too has similar device specifications.The same CWM version worked for @best98 who is using an Archos 45 Platinum.
Tip:Using CWM touch recovery
When using the CWM Touch recovery you may notice that it is not really working properly and that touch is not doing anything. The fact is the touch is being registered and that the touch method is different than normal android because of limited drivers in recovery.
The working
Use one finger touch to scroll
Use two finger touch to select item
Installing a Recovery Menu
Using PC
1) Install the Mobile Drivers.
2) Download Minimal ADB And fastboot [Windows users] Linux and Mac users might have to download the whole Android sdk as of now.
3) Download the recovery you want from the attachments below.
4) Rename them to recovery.img after extracting and copy it to a folder of know location.
5) Boot your device into fastboot mode.i.e Power on your mobile by pressing and holding Power button and vol+ Key.until you see A green screen.
6) Connect your device to the PC and open Minimal ADB and fastboot
7) Run the command " fastboot flash recovery C:\USERS\MYNAME\DESKTOP\ANDROID\RECOVERY.IMG".
Without the quotes replace C:\USERS\MYNAME\DESKTOP\ANDROID\ with the location where you extracted recovery.img.
8) Wait untill it completes and VOILA new recovery installed.
Note: In case you want to preserve your stock recovery, run the command "fastboot boot C:\USERS\MYNAME\DESKTOP\ANDROID\RECOVERY.IMG"
Without the quotes replace C:\USERS\MYNAME\DESKTOP\ANDROID\ with the location where you extracted recovery.img.
Using Mobile
Simple Method.
Just install the TACK Manager from here and install the recovery .Enjoy .
Not so simple method
Download the flashable recoveries from Below and flash it through CWM Or TWRP [Yes, you need custom recovery for this to flash]
Click to expand...
Click to collapse
Rooting Your Device
Method 1: Through CWM/TWRP
1) Download the SuperSU package provided below.
2) Copy it to the root of your SDCard
3) Select Install zip from SDCard
Method 2:Through Framaroot
Personally I Did not get any success by this method.But lot of users reported it to to work by using the Gandalf exploit.
Also some versions of framaroot work better on some devices as compared to others.So maybe just have to check which version works for our Mobile.
1) Download and install Framaroot.apk
2) On the exploits list select Gandalf
3) It'll probably crash the first time and apparently work the second time you launch it.
As I Am not sure which version of framaroot works for this mobile hence no upload
Click to expand...
Click to collapse
Reserved
Flashing Roms and Fix Soft brick
1) Copy Rom to SDCard
2) Boot into Recovery by Powering on while holding power and vol+ Button.Initially you'll see a green screen...Keep holding untill the screen turns red.
3) Goto Mounts and storage and format /Cache and /Data. Format /SYSTEM if installing new rom.
4) Goto Advanced and format Dalvik Cache
5) Select Apply Zip from SD Card
6) Select zip file of rom to install and wait.
7) Reboot and voila.
Note:This is assuming you are using CWMR
Note: Do not format /SYS_BOOT Partition.You'll end up bricking your device and then will not be able to boot into Fastboot mode.
If this happens by mistake.Follow the next Guide.
Click to expand...
Click to collapse
Fixing RESET FOR ENTRY QPST DOWNLOAD
In case you end up Formatting /SYS_BOOT Partition then you'll most likely end up in this.There might be few other cases when this can happen but none that i am aware of.
If you Have a Linux Desktop
If you have access to Linux PC then connect your mobile to it and mount the partition which is around 50 MB. Download the Images.zip from below.unzip the file and copy the whole folder to the 50 MB partition.
Your File structure should look something like this
-\50MBPartition
-\image
-\AMSS.MBN
-\AMSSHD.MBN​
If you have Windows
http://www.filefactory.com/file/2n5ygdzybijv
I'll soon put up a guide for windows users.
This is the guide I found on facebook's CM Flame 2.0 group.
DISCLAIMER:
This fix worked for me. I WILL NOT BE HELD RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE, YOU DO THIS AT YOUR OWN RISK!!! Please do the process step-by-step. DON'T SKIP any step as I don't know what will happen and there's a possibilty that your phone will be dead permanently.
TOOLS NEEDED:
Roadkill and StockROM
DOWNLOAD STEPS:
1. Go to www.dropbox.com
2. SIGN-IN using MY credentials
E-mail: [email protected]
Password: dropbox-pemaustria
3. Navigate to the folder cmflame2, there you can find the file.
4. Right click cmflame2stock.zipx, and click download.
(THIS STEPS LEAVE ME NO CHOICE BUT TO GIVE MY DROPBOX ACCOUNT TO YOU. AS A RESPECT, PLEASE DO NOT CHANGE ANY ACCOUNTS AND SECURITY SETTINGS ON MY PROFILE. THANK YOU)
NOTE: Please use WinZip for extracting files. Thanks
TUTORIALS:
1. Disconnect all USB drives especially flash drives, including memory cards.
2. Turn on your device to QPST Mode, and connect it to computer. When a window prompt you to format card. CANCEL.
3. Extract the contents of cmflame2stock.zipx and run Roadkill.exe. Click 'Yes' if administrative privilages prompt you.
4. In the left side of 'Write image to' choose PHYSICAL DISK 1(3.61GB). In my case it is 3.61 GB. Your size must be approximately 4GB. CHOOSE THE RIGHT DISK. CHOOSING THE WRONG DISK WILL RESULT DAMAGE to the selected disk.
5. In your extracted folder, you will see an image file named CM-Flame2.0-StockROM.img.
6. On source file, browse for the image file you just extracted.
7. Click 'START', wait for the process until it's finished.
Click to expand...
Click to collapse
Custom ROM's
Stock Rom
Karbonn Titanium S1
Flashable ZIP
CWM Backup
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cherry Mobile Flame 2.0
Flashable ZIP
K-Touch Hornet U86 Kiss
K-Touch 1.3.4 Rom
Archos 45 Platinum
Archos 45 CWM Backup
Click to expand...
Click to collapse
Custom ROMS
LeWa OS 14.05.16
Download
One of the most stable ROMs I've seen for our device.It is Continiuosly developed and supported at Lewatek and has weekly updates at friday.OTA update are available so you don't have to download the whole ROM
MIUI ROM 4.1.17
Highly Customizable ROM.
MIUI Is known for the amount of customization you can do with it.From Statusbar to Lockscreen to everything normal android OS can do.
MIUI ROM Download
Lenovo Magic 4.0
With Support for over 11 Languages and
Download
CM10.1
CM10.1 Base ROM
Update File
CM10.2 Alpha
CM10.2 ROM
CM11 Alpha 3
CM11 ROM
Nokia X ROM Port
This ROM is ported by our friend rdis.
You can find the ROM here
AOSP KitkatFlare
More like Stock ROM with KitKat touch in it.Cooler and more Powerful
This is a KitKat Look alike and not the actual kitkat. For KitKat Check CM11 Above.
AOSP KitKatFlare
IXYNOS
Based on stock
Fully themed with color combination of cyan, yellow, purple and white
Slim rom around 189 Mb
init.d tweaks
build.prop tweaks
ttpod
mifileexplorer
pre rooted
zipaligned
net speed in status bar
good battery life
extremely smooth high performance rom
camera with smile detection
Ixynos ROM
Xperia Z
Xperia Z Download
Click to expand...
Click to collapse
Reserved
Reserved
Thanks idrogon81
idragon81 said:
Hello Everybody!!
Recently when going through the xda forums for the devices Karbonn Titanium S1, Cherry Mobile Flame 2.0, K-Touch Hornet u86 kiss [Hence reffered to as TCK-SU186, Simply because it is easier to refer to ], I noticed that a lot of people have questions regarding Stock rom, Recovery rooting and Solutions for Brick.However most of the posts have been left unanswered or died for some reason.
Hence I decided to open a thread that can be used to solve general problems and issues regarding the Device.
Stock Rom
​
Custom Recovery
​
Rooting Method
​
Click to expand...
Click to collapse
Framarook-1.7.0.apk works fine to root karbonn s1 titanium without any crash. use gandalf exploit and its done.
sunilneelam said:
Framarook-1.7.0.apk works fine to root karbonn s1 titanium without any crash. use gandalf exploit and its done.
Click to expand...
Click to collapse
That's strange :/
Didnt work for me
Any Cynogenmod roms
idragon81 said:
Hello Everybody!!
Recently when going through the xda forums for the devices Karbonn Titanium S1, Cherry Mobile Flame 2.0, K-Touch Hornet u86 kiss [Hence reffered to as TCK-SU186, Simply because it is easier to refer to ], I noticed that a lot of people have questions regarding Stock rom, Recovery rooting and Solutions for Brick.However most of the posts have been left unanswered or died for some reason.
Hence I decided to open a thread that can be used to solve general problems and issues regarding the Device.
Stock Rom
​
Custom Recovery
​
Rooting Method
​
Click to expand...
Click to collapse
I loved Cynogenmod and I also want it to be on my device
Any help will be appreciated
LOLya said:
I loved Cynogenmod and I also want it to be on my device
Any help will be appreciated
Click to expand...
Click to collapse
There is CM10.1 for Our device. However i didnt find it to be stable.Didn't find ways to connect to data and some people had issues with microphone not working.
I'll be uploading more unbrick solutuions first, followed by MIUI rom and then CM10.1
TY
idragon81 said:
There is CM10.1 for Our device. However i didnt find it to be stable.Didn't find ways to connect to data and some people had issues with microphone not working.
I'll be uploading more unbrick solutuions first, followed by MIUI rom and then CM10.1
Click to expand...
Click to collapse
If uget it bugfree plz upload it
Thanks
English TWRP
idragon81 said:
Hello Everybody!!
Recently when going through the xda forums for the devices Karbonn Titanium S1, Cherry Mobile Flame 2.0, K-Touch Hornet u86 kiss [Hence reffered to as TCK-SU186, Simply because it is easier to refer to ], I noticed that a lot of people have questions regarding Stock rom, Recovery rooting and Solutions for Brick.However most of the posts have been left unanswered or died for some reason.
Hence I decided to open a thread that can be used to solve general problems and issues regarding the Device.
Stock Rom
​
Custom Recovery
​
Rooting Method
​
Click to expand...
Click to collapse
The TWRP is in Japanese Language can u upload english twrp.img
I googled for it but did'nt get it
Hi,
Great to read that.. at least after crawling the web and finding that Karbon S5 is equivalent to Archos 50 Platinum.. I find from the specs that this Karbonn S1 is the same as the Archos 45 Platinum that I own.
Specs are : here for the Archos 45..
http://www.archos.com/gb/products/smartphones/platinum/archos_45platinum/specs.html?#a
Finally.. I can't wait to see Cyanogen on it.. maybe a chance to have a CM11 ?
Regards
at last i could successfully port android 4.2.2 to karbonn titanium s1...
the rom is being uploaded...its named as "CHEEKUMOD" as it is edited by me
whats working:
ALMOST EVERYTHING :fingers-crossed:
whats NOT working:
CAMERA FOCUS
REST ALL ITS JUST FINE AND AWESOME !!
see the screen shots mean while
Karbonn Titanium S1 custom rom
VOILA !!
At last the first custom rom for Karbonn Titanium S1 is here !!
the most waited Android 4.2.2 for Karbonn Titanium S1
Custom DPI for better looks...
========================================================================================================
Whats WORKING:
VERSION 1
ALMOST EVERYTHING
VERSION 2
ALMOST EVERYTHING
========================================================================================================
Whats NOT WORKING:
VERSION 1
CAMERA FOCUS
SOMETIMES MICROPHONE IN CALL WONT WORK !!
VERSION 2
CAMERA FOCUS
Will give the fix soon,or someone please help me out to fix it...
========================================================================================================
HOW TO INSTALL THE ROM:
Download the rom and gapps and place it in the root of the SD card (Root meaning directly in ur SD card and not in folders so u can find it easily in the recovery)
VERSION 1:
ROM DOWNLOAD: drive.google.com/file/d/0Bz2-ARVuWcM9ZjNvNkJTLWZidnM/edit?usp=sharing
Gapps DOWNLOAD: drive.google.com/file/d/0Bz2-ARVuWcM9LW5TV2xMS2cydnc/edit?usp=sharing
INSTALL CLOCKWORKMOD
How to install clockwork mod for newbies (IF U HAVE CWM ALREADY INSTALLED U CAN SKIP THIS)
Things required:-
Recovery.img (Find in attachments below)
AIO flasher (Find in attachments below)
And of-course ur phone and USB cable
1.Switch off your phone.
2.Boot into fastboot (to boot into fastboot hold volume up+power button for few seconds untill u see a whole green screen and release both the buttons)
3.plug in your phone to pc via USB cable.
4.Download the AIO flasher from attachment below,extract it and open it (Run as admin in pc if required).
5.Select recovery in the AIO flasher and click on select file and select the recovery.img which u downloaded from the attachments below.
6.Now check the erase option and click on flash and wait till it reads "finished" in the AIO flasher dialog box.
7.Remove the cable and pull the battery and re insert it to exit fastboot.
Congratulations !! You have successfully installed CWM on ur device.
BOOT INTO RECOVERY MODE
To boot into recovery mode u need to hold the volume up+power buttons untill the screen turns green and do not release the buttons now hold untill the screen turns red and release the buttons.Wait for sometime untill it boots into the recovery.
navigate using the volume keys and select using the power keys.
1.Select Wipe data/factory reset.
2.Navigate to Advanced and select it.
3.Wipe dalvik cache and go back to main.
4.Now select install zip from sd card.
5.Now select choose zip from sdcard.
6.Select the rom which u downloaded and copied to the root of the SD card.
7.And select yes.
8.Wait until it reads installation complete.
9.And using the same method from step.4 also install the gapps. to flash Gapps u need to select the gapps file instead of rom file.
NOW reboot and enjoy !! IF IT DOSENT REBOOT DONT PANIC PULL THE BATTERY AND POWER ON MANUALLY
Congratulations !!
Your device is running Android 4.2.2 now.
And if u liked this please +1 this
========================================================================================================
DOWNLOAD THE VERSION 2 OF MY ROM HERE WITH MIC FIX AND GAPPS !!
IMPORTANT !!!!!!!!!!!!!!!!!!!!!!! <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
DO NOT FLASH GAPPS WITH THIS VERSION OF MY ROM IT IS PRE INSTALLED IN THE ROM...!!
VERSION 2:
ROM DOWNLOAD: https://drive.google.com/file/d/0Bz2-ARVuWcM9SUVkUnJSSnV3WEU/edit?usp=sharing
GAPPS DOWNLOAD: ITS PRE INSTALLED IN THE ROM DO NOT FLASH AGAIN !! < < < < < < < < < < < < < < < < <---------------------NOTE
Changelog:
1:Fixed "Mic not working in call".
2:have added gapps in the rom file to minimize flashing procedure of flashing each at a time.
========================================================================================================
DISCLAIMER:
NOTHING WILL GO WRONG NORMALLY BECAUSE I HAVE TESTED THESE PERSONALLY BUT IF IT HAPPENS TO U I AM NOT RESPONSIBLE..!!
HAVE A BACKUP OF UR DEVICE so if something goes wrong u can revert the phone to the earlier working stage.
I AM NOT RESPONSIBLE FOR BRICKING OF YOUR PHONES DUE TO THIS PROCEDURE DO IT AT YOUR OWN RISK !!
pls..
idragon81 said:
Flashing Roms and Fix Soft brick
Fixing RESET FOR ENTRY QPST DOWNLOAD
Click to expand...
Click to collapse
Pls.. post a guide for windows users.thanks
CWM is the solution
claymisteryo said:
Pls.. post a guide for windows users.thanks
Click to expand...
Click to collapse
Its not necessary to flash or reset the soft brick using any OS,
U can do it by CWM also.
1]For softbrick u can just factory reset and wipe cache
2] for flashing u can mount and remount sdcard and copy the .zip file to it and choose install zip from sdcard
Plz accept my request
ROM DOWNLOAD: drive.google.com/file/d/0Bz2-ARVuWcM9ZjNvNkJTLWZidnM/edit?usp=sharing
Click to expand...
Click to collapse
Hey Cheetan I just requested u for rom from the link plz accept it I want to try it
LOLya said:
Hey Cheetan I just requested u for rom from the link plz accept it I want to try it
Click to expand...
Click to collapse
me too not able to download
Mincrophone not working!!
when you call, the other person cannot hear your voice.... plz fix this!
its quite a major BUG!
Original Site
chetan007cheeku said:
VOILA !!
At last the first custom rom for Karbonn Titanium S1 is here !!
the most waited Android 4.2.2 for Karbonn Titanium S1
Custom DPI for better looks...
Whats WORKING:
ALMOST EVERYTHING
Whats NOT WORKING:
CAMERA FOCUS
SOMETIMES MICROPHONE IN CALL WONT WORK !!
Will give the fix soon,or someone please help me out to fix it...
HOW TO INSTALL THE ROM:
Download the rom and gapps and place it in the root of the SD card (Root meaning directly in ur SD card and not in folders so u can find it easily in the recovery)
ROM DOWNLOAD: drive.google.com/file/d/0Bz2-ARVuWcM9ZjNvNkJTLWZidnM/edit?usp=sharing
Gapps DOWNLOAD: drive.google.com/file/d/0Bz2-ARVuWcM9LW5TV2xMS2cydnc/edit?usp=sharing
INSTALL CLOCKWORKMOD
How to install clockwork mod for newbies (IF U HAVE CWM ALREADY INSTALLED U CAN SKIP THIS)
Things required:-
Recovery.img (Find in attachments below)
AIO flasher (Find in attachments below)
And of-course ur phone and USB cable
1.Switch off your phone.
2.Boot into fastboot (to boot into fastboot hold volume up+power button for few seconds untill u see a whole green screen and release both the buttons)
3.plug in your phone to pc via USB cable.
4.Download the AIO flasher from attachment below,extract it and open it (Run as admin in pc if required).
5.Select recovery in the AIO flasher and click on select file and select the recovery.img which u downloaded from the attachments below.
6.Now check the erase option and click on flash and wait till it reads "finished" in the AIO flasher dialog box.
7.Remove the cable and pull the battery and re insert it to exit fastboot.
Congratulations !! You have successfully installed CWM on ur device.
BOOT INTO RECOVERY MODE
To boot into recovery mode u need to hold the volume up+power buttons untill the screen turns green and do not release the buttons now hold untill the screen turns red and release the buttons.Wait for sometime untill it boots into the recovery.
navigate using the volume keys and select using the power keys.
1.Select Wipe data/factory reset.
2.Navigate to Advanced and select it.
3.Wipe dalvik cache and go back to main.
4.Now select install zip from sd card.
5.Now select choose zip from sdcard.
6.Select the rom which u downloaded and copied to the root of the SD card.
7.And select yes.
8.Wait until it reads installation complete.
9.And using the same method from step.4 also install the gapps. to flash Gapps u need to select the gapps file instead of rom file.
NOW reboot and enjoy !! IF IT DOSENT REBOOT DONT PANIC PULL THE BATTERY AND POWER ON MANUALLY
Congratulations !!
Your device is running Android 4.2.2 now.
And if u liked this please +1 this
DISCLAIMER:
NOTHING WILL GO WRONG NORMALLY BECAUSE I HAVE TESTED THESE PERSONALLY BUT IF IT HAPPENS TO U I AM NOT RESPONSIBLE..!!
HAVE A BACKUP OF UR DEVICE so if something goes wrong u can revert the phone to the earlier working stage.
I AM NOT RESPONSIBLE FOR BRICKING OF YOUR PHONES DUE TO THIS PROCEDURE DO IT AT YOUR OWN RISK !!
Click to expand...
Click to collapse
Actually Cheetan this is the site with the same ROM,no offence.You might have modified much in this ROM(Your ROM(Cheeku ROM))
Site: http://www.needrom.com/mobile/k-touch-u86-7
Problem is u just need to make account
LOLya said:
The TWRP is in Japanese Language can u upload english twrp.img
I googled for it but did'nt get it
Click to expand...
Click to collapse
can i use any twrp version instead?

[Q] Stuck with a Softbrick device during installing custom rom CM11

Hi there,
I've been working on rooting my htc one X bought in Australia locked to vodafone and now unlocked and used for a while.
I had been planning on rooting the phone for a while and after reading up multiple posts I chose to use the XDA developers video to root the phone. As the video is not very clear towards the end on the processes. But I completed the process somehow with reference to other videos and processes. However, after reading up on the best available ROMs I chose the CM11 with a basic process explained here (unable to post link)- however, that didnt help me much as there's just a basic description of what's to be done (helpful for advanced users).
But as this is my first attempt to rooting my device, I had to look up youtube on videos describing the rooting process for HTC one X. And found another video by the same author -
The author uses another ROM for the process but said this was a universal process. And I ended up copying only the CM11 zip folder of the ROM and not the Gapps zip file. Then his process didn't allow me to boot into recovery as my phone would get to the 'HTC - quietly brilliant' screen and get hang. Then I figured that the recovery image he had in the onexroot folder was an old one so I replace it with the latest image of recovery - recovery-clockwork-touch-6.0.4.8-endeavoru. And tried again, but with no luck.
Then I went in to the HBOOT menu and selected recovery and followed the process of installing from zip file and completed the entire installation process but the phone would go in to a boot loop when I rebooted. I followed some other processes to resolve this and ended up messing up the rom image on the phone. So now i'm unable to do anything with the phone as the stock rom is wiped out and so is the custom rom. I've tried the process of sideloading the zip files but I keep getting an error message of 'device not found'. I tried using the TWRP recovery as well for pushing files, but the the phone is non responsive on the main menu screen of TWRP itself. So I've flashed back to CWM recovery but am out of ideas on how to recover the phone.
Current status of the phone:
Bootloader - Unlocked
CMW - recovery-clockwork-touch-6.0.4.8-endeavoru
Sorry for the long description, but any help will be highly appreciated.
Thanks!
rubendayal said:
Hi there,
I've been working on rooting my htc one X bought in Australia locked to vodafone and now unlocked and used for a while.
I had been planning on rooting the phone for a while and after reading up multiple posts I chose to use the XDA developers video to root the phone. As the video is not very clear towards the end on the processes. But I completed the process somehow with reference to other videos and processes. However, after reading up on the best available ROMs I chose the CM11 with a basic process explained here (unable to post link)- however, that didnt help me much as there's just a basic description of what's to be done (helpful for advanced users).
But as this is my first attempt to rooting my device, I had to look up youtube on videos describing the rooting process for HTC one X. And found another video by the same author -
The author uses another ROM for the process but said this was a universal process. And I ended up copying only the CM11 zip folder of the ROM and not the Gapps zip file. Then his process didn't allow me to boot into recovery as my phone would get to the 'HTC - quietly brilliant' screen and get hang. Then I figured that the recovery image he had in the onexroot folder was an old one so I replace it with the latest image of recovery - recovery-clockwork-touch-6.0.4.8-endeavoru. And tried again, but with no luck.
Then I went in to the HBOOT menu and selected recovery and followed the process of installing from zip file and completed the entire installation process but the phone would go in to a boot loop when I rebooted. I followed some other processes to resolve this and ended up messing up the rom image on the phone. So now i'm unable to do anything with the phone as the stock rom is wiped out and so is the custom rom. I've tried the process of sideloading the zip files but I keep getting an error message of 'device not found'. I tried using the TWRP recovery as well for pushing files, but the the phone is non responsive on the main menu screen of TWRP itself. So I've flashed back to CWM recovery but am out of ideas on how to recover the phone.
Current status of the phone:
Bootloader - Unlocked
CMW - recovery-clockwork-touch-6.0.4.8-endeavoru
Sorry for the long description, but any help will be highly appreciated.
Thanks!
Click to expand...
Click to collapse
flash Philz recovery 5.15.9 mount sd card copy gaps.zip to your folder after this flash again CWM latest version go in recovery install rom.zip after this gapps.zip after this go in fastboot and flash the boot.img from rom.zip via fastboot with the command fastboot flash boot boot.img
Thant said:
flash Philz recovery 5.15.9 mount sd card copy gaps.zip to your folder after this flash again CWM latest version go in recovery install rom.zip after this gapps.zip after this go in fastboot and flash the boot.img from rom.zip via fastboot with the command fastboot flash boot boot.img
Click to expand...
Click to collapse
Hi,
Thanks for your reply. Philz recovery has an updated version available however, in its download screen it is not clear which version corresponds to the One X. There are versions of the software for One V and One S. Could you suggest which one would be the right one?
Thanks.
rubendayal said:
Hi,
Thanks for your reply. Philz recovery has an updated version available however, in its download screen it is not clear which version corresponds to the One X. There are versions of the software for One V and One S. Could you suggest which one would be the right one?
Thanks.
Click to expand...
Click to collapse
Nevermind that. I found the right one after a little more search philz_touch_6.19.3-endeavoru.zip
hope that's okay.
rubendayal said:
Nevermind that. I found the right one after a little more search philz_touch_6.19.3-endeavoru.zip
hope that's okay.
Click to expand...
Click to collapse
The lastest Philz have problem with mounting sd card like CWM and TWRP for this I say to install 5.15.9
rubendayal said:
Nevermind that. I found the right one after a little more search philz_touch_6.19.3-endeavoru.zip
hope that's okay.
Click to expand...
Click to collapse
Hi Thant,
I was able to mount the sd card in Philz, but not sure how to copy the data. Unable to find information on that online.
Any suggestions?
rubendayal said:
Hi Thant,
I was able to mount the sd card in Philz, but not sure how to copy the data. Unable to find information on that online.
Any suggestions?
Click to expand...
Click to collapse
you must to see the device to your computer but on latest Philz sd mount not working install 5.15.9
Thant said:
you must to see the device to your computer but on latest Philz sd mount not working install 5.15.9
Click to expand...
Click to collapse
Hi Thant,
Thank you so much for your help. You were completely right. I downloaded the 5.15.9 version and that let me connect the phone as a usb device and I mounted the device as usb in recovery and copied the gapps. however, there was an issue with the latest CWM that didnt let me install the ROM but philz recovery did the trick. Then again I installed the latest cwm and installed the gapps..wiped the factory data and went back to the fastboot menu, flashed the boot.img from the Rom's folder and rebooted. And now I have the android 4.4.4 working just fine!
Thank you once again for all your help! really appreciate it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Categories

Resources