Database Develop

[Root] [Recovery] Galaxy Tab 10.1 LTE

I'm mobile right now... But.... The root and recovery guide are posted on rootzwiki.com... This is the LTE version... Ill pretty this up when I am gone from work....
Sent from my SCH-I510 using XDA App

poitee said:
I'm mobile right now... But.... The root and recovery guide are posted on rootzwiki.com... This is the LTE version... Ill pretty this up when I am gone from work....
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Can you make a recovery file that we can flash with Odin? A few of us have lost stock recovery snd the CWM recovery file we have available won't work.

jimh1999 said:
Can you make a recovery file that we can flash with Odin? A few of us have lost stock recovery snd the CWM recovery file we have available won't work.
Click to expand...
Click to collapse
I'm one of those few...

[HOWTO] Flash provided recovery without ODIN with broken main recovery [HOWTO]
So after 20 minutes of fiddling with things, I figured out how to get the recovery flashed without having to have recovery installed or without ODIN.
You will need
(1) Rooted LTE device
(2) ROM Manager installed *get at App market*
(3) This file from poitee's post: http://www.mediafire.com/?w45j8i0fcj0wck0
(4) ES File Explorer (or any other file explorer, I just use ES) or USB connection.
(5) Patience
=---------=-------=
Start with a rooted tab. Download the Rom manager.
1) In the ROM Manager, click on Flash ClockworkMod recovery. It will ask you what device etc, select Galaxy Tab. Wait for it to flash so it says "Current recovery: ClockworkMod 4.0.0.4".
2) After it's done, scroll down and hit All Clockwork Mod recoveries. Select 4.0.03. Let it download it and flash it.
3) Unzip the recovery.zip and take the recovery.img file and place it on the tablet.
4) Either using ES File Explorer, or just using Windows Explorer with tablet plugged in, find folder called "clockworkmod" in the SDCard root.
5) Navigate to clockworkmod/download/download.clockworkmod.com/recoveries/
There you will see some two files - recovery-clockwork-4.0.0.4-p7100.img and recovery-clockwork-4.0.0.3-p7100.img
6) Delete recovery-clockwork-4.0.0.3-p7100.img from that folder
7) Copy the recovery.img file from the ZIP above into this folder and rename it recovery-clockwork-4.0.0.3-p7100.img
8) Go back to ROM Manager, and select Flash ClockworkMod recovery, select the tab and hit OK. It will flash 4.0.0.4.
9) Place your tablet into Airplane Mode (turn off Wifi/4G/3G)
10) Scroll down again, select All Clockwork Mod Recoveries, select 4.0.0.3, and hit OK. That will now flash the recovery we just replaced.
11) Exit out of the ROM manager.
12) Push power button, hit Reboot.
13) As soon the screen goes blank, hold power button+volume rocker up till you see the box or downloading.
14) Hit UP once so the box is selected.
15) Hit DOWN once so that it boots into CWM.
*updated* Thanks jimh1999 and ~Scott~ for updates and feedback after testing this. I was a little tired and did misspell the filenames
You are done

Success....Thank You for this, I was about to give up.
Notes,
~I had to put Tab in airplane mode after step 9
~I didn't leave Tab plugged in
~nand backup will work but no progress bars in CWM
~Rom Manager will alert of recovery update, just dont update recovery
~edit per Scott's post, name of file should be recovery-clockwork to match filename structure in the folder
Finally we have recovery on LTE Tab.

THANK YOU!
My notes:
- I also had to put it into airplane mode after step 9
- I tried to flash the new recovery.img and it failed so I rebooted the tablet at this point.
- I noticed the the first recovery was named recovery-clockwork-4.0.0.4-p7100.img so I changed recovery-clockworkmod-4.0.0.3-p7100.img to recovery-clockwork-4.0.0.3-p7100.img and flashed it with no issues.
Then I booted into CWM and noticed the progress bar issue during the backup.... but.... I BOOTED INTO RECOVERY!!
Thanks again!

~Scott~ said:
THANK YOU!
My notes:
- I also had to put it into airplane mode after step 9
- I tried to flash the new recovery.img and it failed so I rebooted the tablet at this point.
- I noticed the the first recovery was named recovery-clockwork-4.0.0.4-p7100.img so I changed recovery-clockworkmod-4.0.0.3-p7100.img to recovery-clockwork-4.0.0.3-p7100.img and flashed it with no issues.
Then I booted into CWM and noticed the progress bar issue during the backup.... but.... I BOOTED INTO RECOVERY!!
Thanks again!
Click to expand...
Click to collapse
You are right about the name, same for me.

Thanks jimh1999 and ~Scott~ for updates and feedback after testing this. I was a little tired and did misspell the filenames
Updated the guide with the names and airplane steps.

tijayz said:
Thanks jimh1999 and ~Scott~ for updates and feedback after testing this. I was a little tired and did misspell the filenames
Updated the guide with the names and airplane steps.
Click to expand...
Click to collapse
Thanks to you and poitee for finding the solution. If you find any roms or kernals that work, please report back. Also can we flash the stock recovery back on this Tab?
I would still like to know why the CWM recovery would,nt work on the LTE version

First of all, let me say thanks for the effort and risk for eveyone involved. Now, please excuse my noobiness here, but is there a way in here to back up the stock rom before flashing/rooting? In other words, can I reverse this process to stock for returns/service?
I've seen how to reverse to stock the WiFi version, but this LTE is uncharted territory. Thanks!

My Galaxy LTE is bricked... Is there any way to just install the plain stock image back?

Mine was never rooted, so i'm kind of stuck, anyone have the stock recovery image?

Yep, I think what we need is the stock recovery image right? Anyone?

www.jamezelle.com/myfiles/stockrec.zip
DD the image inside to mmcblk0p2. At your own risk. Its the stock lte recovery.
Sent from my Samsung Galaxy Tab 10.1 using Tapatalk

jamezelle said:
www.jamezelle.com/myfiles/stockrec.zip
DD the image inside to mmcblk0p2. At your own risk. Its the stock lte recovery.
Sent from my Samsung Galaxy Tab 10.1 using Tapatalk
Click to expand...
Click to collapse
Can you elaborate on your instructions? I have done my fair share of ROM flashing and have used CWM for quite a while, but not sure about going back to stock on the recovery.

I accidentally used Rom Manager to flash "recovery" 4.004 to my LTE Tab and then it would no longer boot up (keeps going back to Samsung screen).
Can get to the screen to choose recovery or Odin. Then, I made it worse by flashing (with ODIN) what I thought was the correct stock image, and wound up putting the Wifi model on to it.
After quite a bit of reading (and kicking myself) ...
I have created a ODIN capable stock recovery image, and now I can get into stock recovery, but I need the rest of the LTE image to restore my unit. Can anyone make a dump of the factory stuff (other than the data) ? Heck even if I can get it working on just Wifi for now, that would be ok until the LTE image surfaces.
I really don't want to try to return it since I have only had it for 2 days and it would be pretty obvious that I had messed with it.
Thanks. I can make

Not sure if it will help but I'll wipe data and pull a nandroid if you want but I'm on cwm stock lte since I still can't figure out how tonsetup my PC for rom dev on hc
Sent from my Incredible 2 using XDA Premium App

mattj949 said:
I accidentally used Rom Manager to flash "recovery" 4.004 to my LTE Tab and then it would no longer boot up (keeps going back to Samsung screen).
Can get to the screen to choose recovery or Odin. Then, I made it worse by flashing (with ODIN) what I thought was the correct stock image, and wound up putting the Wifi model on to it.
After quite a bit of reading (and kicking myself) ...
I have created a ODIN capable stock recovery image, and now I can get into stock recovery, but I need the rest of the LTE image to restore my unit. Can anyone make a dump of the factory stuff (other than the data) ? Heck even if I can get it working on just Wifi for now, that would be ok until the LTE image surfaces.
I really don't want to try to return it since I have only had it for 2 days and it would be pretty obvious that I had messed with it.
Thanks. I can make
Click to expand...
Click to collapse
Don't worry man we'll get you going.
~Scott~ said:
Can you elaborate on your instructions? I have done my fair share of ROM flashing and have used CWM for quite a while, but not sure about going back to stock on the recovery.
Click to expand...
Click to collapse
Can you boot into android? If so I can give you the instructions to get the stock recovery back on via command line or mattj949 can post his Odin file.

I wound up returning and exchanging, but I still want to back it up in case it happens again....
However, I did make a fully working CWM ODIN flashable (for LTE Tab), however, not sure how to post it here. I left it on my office PC, will figure out how to post tomorrow.

Bricked?
Im having the same problem with rooting then using clockwork to flash recovery 4.0.0.4. Now Im stuck with the Galaxy Tab boot screen then to black then the boot screen and to black continuously.
I can access Odin but my computer doesn't recognize the Tab and never has. When I plug it in I hear the computer recognize it but gives a different sound doesn't see it. ???
Can anyone help me get this thing booted again.
Thanks

[Q] Droid 3 flash rom

recently I have attempted to flash the monster rom to my droid 3 and I havent had success it was 1.2 version and i used D3 Safestrap. I went into safe mode then installed zip from my sd card and it loaded and was successful. Then went in to reg mode to boot up ( because it is not able to in safe) and nothing changed i went into the about phone and it does not show a new rom was loaded nor does anything look different. Did i miss a step? what happened?

Sounds like it didn't work. The point of safe mode is that it's a separate system to non-safe mode, so non-safe mode should still work exactly like it did.
So your phone not booting in safe mode means that the ROM's not working or whatever. Switching to non-safe mode is like flashing back to the backup before you installed the ROM, it _should_ not look any different.

Ok so then that mean even though it says successfull it is in fact not? I am a noob, so i apologize for my ignorance.

Did you toggle back to safe mode and reboot. That should boot up the new rom.
Sent from my DROID3 using XDA App

Unfortunately MonsterROM is not Safestrap compatible in its current form. You need to unzip it, delete a folder and rezip it for use inside of Safestrap. There's a post somewhere within the Safestrap discussion of the Android Development section that indicates what to do.

Manic_Dragon said:
Did you toggle back to safe mode and reboot. That should boot up the new rom.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
I did and it wont go past the multicore display it just goes blank after

SBF, reroot, then just install the other bootloader. Don't use Safestrap. I had the same problem with Monster. Someone probably should convert it.
Sent from my DROID3 using XDA App

[TESTERS] Beta version of Flash Image GUI

Appreciate all the help testing! Will keep this thread around if more issues are encountered.
For the time being I'm going to close down this thread as I've posted a new official thread!
Thanks everybody, especially PirateGhost!
New official thread: http://forum.xda-developers.com/showthread.php?p=20926830
Goal:
Working on making kernel flashing on the HTC Vivid / Holiday a few steps easier/simpler!
Background:
The HTC unlock method has been out for the last 6 months on the HTC EVO 3D. We've developed some work around methods to make things simpler for both the developers and the users who are stuck using the HTC unlock method.
How:
Fact for EVO 3D and theory for Vivid: The HTC unlock method only allows write access to the kernel (boot partition) in either fastboot mode or the normal android mode.
This means a custom kernel can only be loaded in two modes, either through fastboot or while in the standard Android mode.
Tool:
Flash Image GUI is an application I wrote to load the kernel and modules while in standard Android mode. This eliminates the need for using fastboot which requires a computer and will eliminate the need for using the Windows dependent .bat files for automating the fastboot flashing process. This will also eliminate the need to reboot into fastboot mode.
Current Status:
An updated Flash Image GUI code to support the HTC Vivid device but need a few testers to verify it all works properly on their devices!
Testing Location:
Either post back in this thread if you're able to help or join us on IRC - irc.freenode.net #gen-dev
Testing Steps:
Would recommend joining the irc channel for more detailed assistance but if you'd prefer to test and post in this thread, here are the steps:
**Wild Child told me there is no kernel backup support yet**
Stock Kernel Signed - http://w1z4rd.net/boot.img (Thanks IanWizard)
Stock Kernel Unsigned - http://joeykrim.com/evo3d/files/boot-unsigned-holiday.img
Skip straight to Step 5. The above links can be used to restore the kernel back to 100% stock.
1) Downloading clockworkmod recovery for your device to your local desktop
2) fastboot boot c:\downloads\cwm-recovery.img
3) Make a nandroid of all partitions (will need this in case there are any issues)
4) Reboot into normal android mode
5) Install Flash Image GUI - http://joeykrim.com/evo3d/files/FlashImageGUI.apk
6) Download a kernel to flash - list provided below
7) Push kernel .zip file to /sdcard (either usb mount the device or adb push c:\downloads\kernel.zip /sdcard/kernel.zip
8) Open Flash Image GUI - make a note of the kernel version displayed at the top of the application
9) Click browse and select the kernel .zip file from the sdcard
10) Flash the Image
**11) Reboot
12) Check the kernel version to see if the process worked (Either open Flash Image GUI and kernel version information will be at the top or Menu->Setting->About Phone -> Software Version -> More.
**If you're interested in testing the flashing of a kernel and ROM combination, at step 11, reboot into the standard recovery mode, where ClockworkMod should be loaded and flash the ROM .zip file
Steps to restore previous kernel before testing
1) fastboot boot c:\downloads\cwm-recovery.img
2) Restore Nandroid created in previous section step 3
Kernels to Test Flash:
Thanks to Dodgejcr for the stock vivid kernels for testing!
Stock Kernel boot.img zip with modified kernel version to verify flash worked properly
Stock Kernel anykernel .zip with modified kernel version to verify flash worked properly
PirateGhost Telstra boot.zip - This *probably* requires the associated ROM Raider .zip to be loaded. Don't flash this kernel unless you're also flashing the ROM .zip.
Thanks for the support and willingness to test!

awesome. i just went from stock rooted to my rom using this tool.
might i suggest a 'reboot to recovery for rom flashing' button? that would complete this little project, i think.

Good idea man. I'll surely add this to the superguide once a few more people test it. Less steps is always good.
Sent from my HTC PH39100 using xda premium

slapshot30 said:
Good idea man. I'll surely add this to the superguide once a few more people test it. Less steps is always good.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
i am working with him on IRC to get a one-stop-shop for rooted users to flash a new rom. no more fastboot flash boot for the noobs!
LOL

You are still gonna keep the ROMs and kernals separate for people that would rather do it from adb/recovery right? Cause I've had terrible luck trying to take shortcuts using batches, programs and the like.

travisxcore said:
You are still gonna keep the ROMs and kernals separate for people that would rather do it from adb/recovery right? Cause I've had terrible luck trying to take shortcuts using batches, programs and the like.
Click to expand...
Click to collapse
the beauty of this tool is that you dont use batches and programs on your computer
its all on the phone and will boot you to recovery to flash the rom you want (as soon as he gets all the bugs worked out. im just the guinea pig here, inputting little value)

I've have been able to flash a kernel in recovery. I was using the first compile i think. First step I did was reboot recovery from advanced then I wiped dalvik and flashed the zip containing the kernel. It seemed to work anyways.
Sent from my HTC-X710a using XDA App

Pirateghost said:
i am working with him on IRC to get a one-stop-shop for rooted users to flash a new rom. no more fastboot flash boot for the noobs!
LOL
Click to expand...
Click to collapse
Thank God... lol
It hasn't gotten that bad yet, with not that many people needing to flash kernels, but I was waiting for the onslaught of problems involving it.

Pirateghost said:
the beauty of this tool is that you dont use batches and programs on your computer
its all on the phone and will boot you to recovery to flash the rom you want (as soon as he gets all the bugs worked out. im just the guinea pig here, inputting little value)
Click to expand...
Click to collapse
I'm still a little weary...idk I've never really liked not having control over something like this because if my phone bricks, at least I know its my fault. But I could see the benefit being out and just downloading the ROM/kernal straight to my phone and flashing it. And I definitely see the benefit for people that don't have a single clue what their doing. Would help cut down on the same 1000 help me posts...lol.

ToyGUN said:
I've have been able to flash a kernel in recovery. I was using the first compile i think. First step I did was reboot recovery from advanced then I wiped dalvik and flashed the zip containing the kernel. It seemed to work anyways.
Sent from my HTC-X710a using XDA App
Click to expand...
Click to collapse
bet it didnt flash a kernel even if it was included in the zip....

Appreciate all the help testing! Will keep this thread around if more issues are encountered.
For the time being I'm going to close down this thread as I've posted a new official thread!
Thanks everybody, especially PirateGhost!
New official thread: http://forum.xda-developers.com/showthread.php?p=20926830

[DEV] ClockworkMod 5.5.0.4 [UPDATED: Can't get to CWM? Here's the fix!]

Howdy y'all!
I just compiled a proper version of ClockworkMod recovery 5.5.0.4 off of the ICS branch of CyanogenMod.
It supports backing up boot images (I have heard that the image that is being flashed now doesn't support backing that up), and in the near future will support recovery chargemode.
This repository will hopefully contain in the near future a semi-working copy of CyanogenMod 9 also, but there's no guarantees on that one
So, without further ado:
What is this?
This is ClockworkMod Recovery 5.5.0.4 and the files necessary to build it yourself.
Click to expand...
Click to collapse
How do I use it?
You must first be unlocked with HTCDev.com (there is an excellent guide over there, just click on the Unlock Bootloader button and it'll walk you through)
Once you're unlocked, download the prebuilt image below, and do the following (in the same directory you used to unlock your phone):
Code:
fastboot flash recovery <path/to/prebuilt-image-you-downloaded.img>
You need to replace the stuff in brackets with the path to the img file you downloaded from here...
Alternate Installation Method (ph39img)
Much easier installation once unlocked with HTCDev...
Simply download the ph39img.zip I have linked to in the downloads section, and put it on your external SD card.
Reboot your phone into HBOOT, and allow the update. Then you've got clockwork installed super easy, no computer needed!
Click to expand...
Click to collapse
How is this different from the ClockworkMod image that's floating around here?
Truth be told, I haven't tried the other version yet-- but I have been told that it doesn't back up boot.img, and has a few other bugs.
Also, this version has /sdcard mapped to the external SD card as opposed to the internal SD card. This is a safety feature to prevent losing backups in case your device becomes inaccessible. All backups should be to an external storage medium (even on your desktop, it's a good practice to not backup your hdd to the same device )
I'm sure mine has bugs too, but I'm posting the source so y'all can laugh at me
Click to expand...
Click to collapse
The Goods: Where do I get it? -- Downloads:
recovery-beta2.img - https://github.com/downloads/thecubed/android_device_htc_holiday/recovery-beta2.img
Alternate installation method: ph39img.zip : https://github.com/downloads/thecubed/android_device_htc_holiday/PH39IMG-chargemode.zip
New! PH39IMG.zip for users with ICS OTA: http://goo-inside.me/private/iomonster/htcvivid/recovery/ph39img/hboot-1.85/PH39IMG.zip
Click to expand...
Click to collapse
recovery-take1.img - https://github.com/downloads/thecubed/android_device_htc_holiday/recovery-take1.img
Alternate installation method: ph39img.zip : https://github.com/downloads/thecubed/android_device_htc_holiday/PH39IMG.zip
Click to expand...
Click to collapse
The GitHub source is here:
https://github.com/thecubed/android_device_htc_holiday
Click to expand...
Click to collapse
Please don't mirror the files (hotlinking is okay!), just incase I need to take them down or quickly update them. Thanks!
Click to expand...
Click to collapse
Changelog
recovery-take1 : initial release
recovery-beta2 : now supporting charge mode in all forms just like stock recovery, and a few behind-the-scenes tweaks
Click to expand...
Click to collapse
Tips and Tricks (what works, and what doesn't)
Please read the following-- the HTCDev unlock comes with it's own disadvantages and risks...
The HTCDev unlock adds the word "**UNLOCKED**" to your HBOOT screen. Even if you put your phone to stock with a RUU and re-lock the phone, your phone will show "**RELOCKED**" when booted to the bootloader.
At this time, I am unsure if AT&T will refuse warranty claims if they see that text. Just remember: if you unlock, there may not be any way back to complete stock any time soon.
Another disadvantage of the HTCDev unlock: ClockworkMod recovery CANNOT flash kernels. You must use JoeyKrim's kernel flasher ( http://forum.xda-developers.com/showthread.php?p=20926830 )or fastboot to flash kernels. This includes Nandroid backups.
If you back up your phone and apply a new ROM and kernel, you will have to fastboot flash the old boot.img back or use JoeyKrim's kernel flasher before switching ROMs.
If you flash a ROM, make sure to read the instructions with the ROM. Every ROM developer has a different method of flashing the kernel-- some come with a script to run, and others just give you the files to flash. Please read what they have to say before posting here with a complaint
Not seeing your rom .zips on your SD card, or having trouble restoring a backup?
This version of ClockworkMod has the external SD card set as primary. This is to avoid the problem of "my phone died, and I can't access my backups".
To solve this issue, simply put your ROMs or whatnot on your external SD card. In the future, I may look into how hard it is to add a internal/external SD switcher to clockwork, but for now the safest default is the external SD.
Sorry about that!
Some rom.zip's don't work...
This may be because they're using an old version of the update-binary in their .zip file. Contact your ROM maintainer and ask for an updated version
If you are a ROM developer, here's the updated "update-binary". Drop it in your META-INF/com/google/android directory in your ZIP and update your format() commands properly...
update-binary.bin (rename to update-binary) - http://legacyschool.us.to/htcvivid/update-binary.bin
Click to expand...
Click to collapse
HELP! I CANT GET INTO RECOVERY! *new!
If you find yourself unable to get into CWM (i.e. the screen flashes some text, then reboots immediately), just boot to fastboot (hboot -> fastboot), then issue "fastboot erase cache" on your PC.
Then you should be able to boot into ClockworkMod. After you're in there, make sure to format /cache to fix the problem.
This issue will be fixed soon, I'll add some intelligence to the kernel to not bother rebooting to fsck a partition if it's marked 'dirty' or unmountable. Stock recovery is supposed to fsck the partitions if they're dirty/broken, but CWM doesn't bother, and the kernel gets easily confused.
Click to expand...
Click to collapse
How can I contact (chastise, praise, call names) you?
On IRC (Freenode) you'll find me hanging out in #htc-holiday when I'm available.
Just say my name "IOMonster" (or "IOMonster_desk") and if I'm around I'll answer.
I also will sometimes respond to PM's on XDA, but XDA's forum has a bad habbit of not emailing me when I get a new PM...
Click to expand...
Click to collapse
Standard "it might not work" clause
This software hasn't been thoroughly tested, and it might not work.
It might not backup things correctly, and it might not restore them right.
Please don't trust this software with anything sensitive or life-alteringly important.
I'd hate to say "I told you so!"
That's not to say this software doesn't work, it's just the standard disclaimer.
Click to expand...
Click to collapse
Donation Information
I love to develop. I don't do this for money, I do it just for the "thanks".
Please don't feel obligated to donate, but if you feel like it, you can click the button below to donate a small amount to me. Alternatively, consider donating to a charity of your choice-- there are so many good causes out there that could use your donation.
​Thank you in advance!
Click to expand...
Click to collapse
Credits / Thank You's
IanWizard-cloud (testing, moral support )
Pirateghost (much needed debugging, testing, and flashing his phone no less than 20 times!)
joeykrim
toastcfh
fattire
BananaCakes (for getting clockwork built in the first place and enabling so many mods on day 1 of unlock!)
..and lots of others!
Click to expand...
Click to collapse
Thanks for giving this looong post a read!
Good luck!

Shoot I'll give it a shot. Flashing now. Will edit this post after its been tested.
Edit: Short glance review, I know a lot of this is already stated/known but just posting it anyways
So firstly, I'm still getting no confirmation when I flash images (whether it be recovery or kernal) but again, I think thats from me using a VM to do all the work.
Still boots into recovery when plugged in.
Maybe I'm just being an idoit, but I couldn't get out of the keytest, had to hold power button which booted the rom.
Of course the usb mount and such works.
Will try backup later when I'm not short on downtime.

already flashed... beautiful. will run through some tests tonight. and dont think you are getting rid of me on IRC now

Coming from the HTC EVO 3D land with the HTC unlock method for the last 6 months .. the following tips have been very helpful.
HTC Unlock method only allows kernel write access while in two modes, fastboot and standard android mode. HTC unlock method does NOT allow a kernel to be flashed from standard recovery mode. This includes a ROM .zip with a kernel inside. The ROM will load, but the kernel will not from standard recovery mode.
The ONLY way to flash a kernel whether by performing a full nandroid restore including the kernel or flashing a ROM with a kernel inside, is to use the following command to load the custom recovery:
fastboot boot <destination of recovery.img>
example on windows: fastboot boot c:\downloads\cwm-recovery.img
Everything else will work in the standard custom recovery mode EXCEPT the ability to flash a kernel. To flash a kernel through the custom recovery, fastboot mode must be used per HTC's unlock method.

Updated OP with simpler installation method (ph39img).
Much easier to use, and no mucking around in commandline!

well it most definetly worked. i jus downloaded the zip file and was able to back up my settings. Only problem i have is. ( which is a similiar problem i had before this. if i powered off the phone and plug it to charge it would automatically restart the phone.) When i power off now and plug it in to charge. It automatically goes to the clockworkmod set up. none the less my phone works and i have backed it up. But i still was wondering wat could cause these problems ?

Same issue here can't charge while off,
I not sure boot backups are working,
Was stock did back up, flashed RR betas and then restore to saved image, got bootloop, had flash boot thru fastboot
Sent from my HTC PH39100 using xda premium

Great start for this....from what i was told theres drivers needed in the recovery for it to charge while device is off and fastboot is unchecked...device charges while fastboot is checked and device is off....
WC

Recovery works great for me.
BTW, the offline charge issue is usually in the chargemon file.

for the new recovery, we will need to be using a new update-binary and when flashing a rom, your updater-script must contain 4 arguments in the format line, like this:
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p29", "0");
inside the attached zip you will find the update-binary
if you dont know what update-binary and updater-script is, then this isnt for you and you needn't concern yourself with it.

Just put your new recovery in the superguide and gave you credit. Keep up the good work!

There seems to be some issues pertaining to this CWM and flashing Telstra_boot image and attempting to install Run Runner ROM.
After flashing boot.img and attempting to wipe and isntall the rom i got an aborted error 1. After rebooting back into recov i was stuck at the HTC boot screen
The only way i could get back and working was relocking and flashing the RUU
Drew

drewdatrip said:
There seems to be some issues pertaining to this CWM and flashing Telstra_boot image and attempting to install Run Runner ROM.
After flashing boot.img and attempting to wipe and isntall the rom i got an aborted error 1. After rebooting back into recov i was stuck at the HTC boot screen
The only way i could get back and working was relocking and flashing the RUU
Drew
Click to expand...
Click to collapse
Did you not download the fix I provided in the Rom thread? This recovery works fine with the updated binary.
Sent from my HTC PH39100

Pirateghost said:
Did you not download the fix I provided in the Rom thread? This recovery works fine with the updated binary.
Sent from my HTC PH39100
Click to expand...
Click to collapse
I did notice your fix but i was already about half way through the "long way"
Needless to see im using the slightly older version of CWM and now on RR10
Drew

drewdatrip said:
I did notice your fix but i was already about half way through the "long way"
Needless to see im using the slightly older version of CWM and now on RR10
Drew
Click to expand...
Click to collapse
At that point it was too late for.the fix. It does work now though.
Sent from my HTC PH39100

Question has the flash able zip been updated so it will now work to flash rooms or is it the rom zip scripts that needed updating? Can I place this zip on my SD card and overwrite the old version ( if that's what was in fact wrong)
Sent from my HTC PH39100 using Tapatalk

I have a raider from rogers and tried putting the PH39IMG zip on my htc sd drive and get an error about wrong img (or something to that effect).
So is this for the at&t vivid only?
as I still have cwm from the original raider thread for rogers, bell, fido from here.
and this appears to be updated and backing up to the ext-sd, which is much better.

hackit said:
I have a raider from rogers and tried putting the PH39IMG zip on my htc sd drive and get an error about wrong img (or something to that effect).
So is this for the at&t vivid only?
as I still have cwm from the original raider thread for rogers, bell, fido from here.
and this appears to be updated and backing up to the ext-sd, which is much better.
Click to expand...
Click to collapse
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.

Thanks will try now.
Pirateghost said:
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.
Click to expand...
Click to collapse
---------- Post added at 09:01 PM ---------- Previous post was at 08:29 PM ----------
Worked like a charm, just finished my first nandroid backup as well.
off we go to start testing out a rom.....
wooo hoooo!
Pirateghost said:
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.
Click to expand...
Click to collapse

ok i have a question, after using the phone for a full day know (still stock).
I have noticed I'm unable to keep my connection to rogers for data only.
I have checked and the apn is right.
I have cleared dalvic cache and fixed permissions.
Still when im away from wifi and using data, most of the time i have no connection.
Now before i updated to this version of cwm i had no issue's with my data connection.
anyone else having an issue with a raider on rogers?
Thanks

[RECOVERY] aCWM 6.x - N5100 / N5110 / N5120 - Sr#1

Hey, I bring to you the first Clockworkmod Recovery or commonly known as CWM for your N5100 and N5110. Giving your device the ability to flash your favourite custom ROMs, Kernels, Mods. *Now known as Advanced CWM or aCWM. Thankyou to 'xperiacle' and 'GSLEON3' for giving me the stock recoveries and kernels for N5100/10, so I could start off with my work.
Works perfectly now. OP will only be updated with stable releases, everything else will be floating around the thread.
I have provided the stock recovery if you encounter any issues, you can always flash back.
Featues:
Most things you would expect from stock CWM
EFS backup / restore
Removed option to: report error / show log / testkeys
More to come...
Downloads:
Use this if you are having problems with your SDCard. (Mount / Backup / Restore)
N5100 / N5110
Stable Release #1: ODIN | ZIP
Stock Recovery: http://d-h.st/tHx
N5120
Stable Release #1: ODIN
Stock Recovery: http://d-h.st/51H
Changelog:
Code:
[I][U]Stable Release #1[/U][/I]
Added reboot menu (rom, download, recovery)
Advanced CWM = aCWM
Code:
[I][U]Experimental #6[/U][/I]
Working EFS backup / restore under 'advanced' tab
Removed keytest / report error / show log options
Custom recovery, no more to be called 'stock' CWM, more device specific features to be added
N5120 support
Fix permissions now directed to /sdcard/.android_secure
Cleaned up some code for flashing zips
[I][U]Experimental #5[/U][/I]
[COLOR="Red"]REMOVED DUE TO ISSUES[/COLOR]
Touch recovery (reimplemented)
Universal for 5100 / 5110
Fixed up some mount lengths
Fixed up init.rc
[I][U]Experimental #4[/U][/I]
Display issues fixed
[I][U]Experimental #3[/U][/I]
Built again with fresh tree - n5110
(info: skipped for n5100)
[I][U]Experimental #2[/U][/I]
Touch Input excluded (temp)
kernel built from source with dancing cwm patch
[I][U]Experimental #1[/U][/I]
Public release

emwno said:
Hey, I bring to you, Clockworkmod Recovery or commonly known as CWM for your n5100. Giving your device the ability to flash your favourite custom ROMs, Kernels, Mods in the future. Thankyou to 'xperiacle' for giving me the stock recovery and boot.img. Flash with Odin
This has not been tested by me and is still experimental. I hold no responsibility for any
problems caused. YOU! Are trying this at your own risk. Don't blame me that I wasted your $$$.
Put a scare in you didn't I?
I have provided the stock recovery if you encounter any issues, you can always flash back.
Downloads:
CWM Recovery: http://d-h.st/rDv
Stock Recovery: http://d-h.st/tHx
Changelog:
Code:
[I][U]Release #1[/U][/I]
Public release
Click to expand...
Click to collapse
Thanks now we need one for the N5110.

rfb813 said:
Thanks now we need one for the N5110.
Click to expand...
Click to collapse
Just need to check if this works properly. If yes, then n5110 is up next

emwno said:
Just need to check if this works properly. If yes, then n5110 is up next
Click to expand...
Click to collapse
Thanks!

Thanks man, that was fast work
Sent from my GT-N5110 using Tapatalk HD

Southrice said:
Thanks man, that was fast work
Sent from my GT-N5110 using Tapatalk HD
Click to expand...
Click to collapse
Nothing to be credited for, until the device boots to CWM

How do you flash this custom recovery with ODIN?, what version?, thanks

I flash the file 2 times and it said pass but when reboot to recovery is stock so I don't know what went wrong

Speedy Gonzalez said:
I flash the file 2 times and it said pass but when reboot to recovery is stock so I don't know what went wrong
Click to expand...
Click to collapse
How did you flash, Odin?

brosenz said:
How did you flash, Odin?
Click to expand...
Click to collapse
I added the zip to the pda area and flash Odin v3.07

I installed the image with ADB.
put the recovery image on the sdcard mount or ext sdcard mount
ADB to the note 8.0
su to root
go to your image directory
dd if=xxx.img of=/dev/block/mmcblk0p6
switch back to the note and reboot directly to recovery (i used goomanager)
it does boot the first time - but it is jittery and in landscape mode.
after the first system boot- the device wipes it and goes back to stock recovery.
I have seen this with other stock android devices- sometimes there
is a script that gets triggered on boot to remove any custom recoveries.
I did clear the recovery check from CWM - but it was hard to see because of the
landscape mode and the screen jumping around.
It looks like the full backup is working- now I wonder what ROM will be close enough
to the 8.0 to try flashing.
Speedy Gonzalez said:
I added the zip to the pda area and flash Odin v3.07
Click to expand...
Click to collapse

Any idea why it didn't flash with Odin?

@xbill9
Code:
adb pull /tmp/recovery.log
for fixes

Speedy Gonzalez said:
I flash the file 2 times and it said pass but when reboot to recovery is stock so I don't know what went wrong
Click to expand...
Click to collapse
Found this Q&A in the Note 10.1 rooting guide in RootGalaxyNote.com:
Q: I don’t see ClockworkMod Recovery when I enter recovery, I see stock Android recovery.
A: With newer software updates, you may be encountering this error because it will overwrite ClockworkMod Recovery upon reboot. To get around this, simply boot into ClockworkMod Recovery right after flashing in ODIN. You can set auto-reboot off in ODIN then when done, just hold down Power and Volume Down straight to bootloader menu.
This may have been the problem.

To get it to stop resetting to stock recovery every time you reboot, under /system, there is a file named "recovery-from-boot.p". Rename it to .bak or whatever. That file is typically the culprit for custom recoveries not 'sticking'.
Also, we don't have a factory image yet, do we? I'm hesitant to mess too much with this stuff until we have a way to Odin ourselves out of a softbrick.
---------- Post added at 11:45 PM ---------- Previous post was at 11:42 PM ----------
Also, to the OP, thanks for doing this. I'm pretty familiar with adb if you'd like to do TWRP. Would love to have it instead of CWM!

rfb813 said:
Q: I don’t see ClockworkMod Recovery when I enter recovery, I see stock Android recovery.
A: With newer software updates, you may be encountering this error because it will overwrite ClockworkMod Recovery upon reboot. To get around this, simply boot into ClockworkMod Recovery right after flashing in ODIN. You can set auto-reboot off in ODIN then when done, just hold down Power and Volume Down straight to bootloader menu.
Click to expand...
Click to collapse
Those having issues, try that ^^^
jntdroid said:
To get it to stop resetting to stock recovery every time you reboot, under /system, there is a file named "recovery-from-boot.p". Rename it to .bak or whatever. That file is typically the culprit for custom recoveries not 'sticking'.
Also, to the OP, thanks for doing this. I'm pretty familiar with adb if you'd like to do TWRP. Would love to have it instead of CWM!
Click to expand...
Click to collapse
Yeah, But i'd like to keep, just incase something goes insanely wrong. The stock recovery.img is provided, you can always flash back it something goes wrong. And i am readying up TWRP, may need you to pull some logs if it doesnt boot

jntdroid said:
To get it to stop resetting to stock recovery every time you reboot, under /system, there is a file named "recovery-from-boot.p". Rename it to .bak or whatever. That file is typically the culprit for custom recoveries not 'sticking'.
Also, we don't have a factory image yet, do we? I'm hesitant to mess too much with this stuff until we have a way to Odin ourselves out of a softbrick.
---------- Post added at 11:45 PM ---------- Previous post was at 11:42 PM ----------
Also, to the OP, thanks for doing this. I'm pretty familiar with adb if you'd like to do TWRP. Would love to have it instead of CWM!
Click to expand...
Click to collapse
http://samsung-updates.com/device/?id=GT-N5100
http://samsung-updates.com/device/?id=GT-N5110
I will be releasing a full Note 8.0 Toolkit today or tomorrow with support to rename the stock recovery restore files so that custom recovery isnt overwritten after flashing. If anyone wants to help test please email me at [email protected]
Mark.

Attached is a tar of recovery.log pulled with ADB while booted to CWM.
The display goes to landscape on boot - and the fonts seem extra large.
When the vol up/down navigates the screen jumps and you can't see the
highlighted option.
It is usable with trial and error if you know the order of the CWM menus and
use the vol up/down and power to navigate.
emwno said:
@xbill9
Code:
adb pull /tmp/recovery.log
for fixes
Click to expand...
Click to collapse

Only thing I can judge by that are the missing mount types for the recovery.fstab. Ill fix that now. But someone, try keeping the device physically portrait and see if cwm works properly then, if not then physically landscape.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
P.S try using touch input, its a touch recovery, or so I built it
^thats why fonts are large
^thats why there are no indicators

I tried changing orientation before boot - it always goes to landscape.
I attached 2 images - one is the display after the first CWM boot.
The second is after pressing Vol Up to navigate to the 2nd menu option.
I have seen jumpy CWM presentation like this on some smaller screens like the
Sony Xperia 2011/2012 phones.
emwno said:
Only thing I can judge by that are the missing mount types for the recovery.fstab. Ill fix that now. But someone, try keeping the device physically portrait and see if cwm works properly then, if not then physically landscape.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
P.S try using touch input, its a touch recovery, or so I built it
^thats why fonts are large
^thats why there are no indicators
Click to expand...
Click to collapse