Develop Bugs

[HOWTO] Create a GoldCard - Bypassing the RUU/SPL CID check to Root/Downgrade

If you are stuck on a ROM you don't like (t-mobile/asian carrier etc.) you can use this howto to create a goldcard to bypass the CID checks so you can downgrade and root your Hero.
01. Download QMAT 5.06 here
It’s a demo version so will only run for 10 minutes.
02. Format your SD card to FAT32. Please keep in mind some brands of SD cards do not work.
03. Use adb to run this command: adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
04. Copy the SD card cid code displayed after the adb command.
05. Start Qmat and Click on Cyptoanalysis Tools > Crypto Toolbox.
06. Look at the bottom, there is a text box (beside the “Reverse String” button) enter the SD card cid code you got earlier.
Click on the “Reverse String” button, the result is reversed…
Example: 532600bd227d9c0347329407514d5402
07. Copy the reversed SD card cid code.
08. Go to QMAT goldcard site here to generate your goldcard (yes it says for G1 but works for our Hero too).
09. Enter your email. For the correct SD card cid code, you need to replace the first 2 characters to 00.
Example: From “532600bd227d9c0347329407514d5402” to “002600bd227d9c0347329407514d5402”
10. Click Continue and you will receive the goldcard.img in .zip format in your email.
11. Go to your email, download the zip file and save it to a directory and unzip it to goldcard.img
12. Download HxD Hex Editor from here
13. Install and launch HxD Hex Editor program. (make sure you use "Run as Administrator" under Vista and win 7)
14. Go to Extra tab > Open Disk. Under Physical disk, select Removable Disk (Must be your SD card), uncheck “Open as Readonly), click OK.
15. Go to Extra again, Open Disk Image, open up goldcard.img which you’ve saved/unzipped earlier.
Now, you should have two tabs, one is your removable disk, the other is goldcard.img. Press OK when prompted for “Sector Size” 512 (Hard disks/Floppy disks), click OK.
16. Click on goldcard.img tab. Go to Edit tab > Select All, edit tab again > copy.
17. Click on the “removable disk” tab. Select offset 00000000 till offset 00000170 (including the 00000170 line), click on Edit tab and then Paste Write.
18. Click on File > Save. now you can exit the program.
19. Reboot your phone with this SD Card (now GoldCard) inside
20. Use the Official HTC RUU to downgrade to 2.73.405.5 (which you can get here) from which you can fastboot boot and/or root your phone with flashrec.
Done.
Credits:
Original heads up by tangzq with link to this
That site used the XDA Sapphire goldcard howto here
And apparently myself and XDA as this builds on the HTC knowledge from the old days (here)
In any case, enjoy your new found freedom

Holy ****znit it works! Downgrading!!!!!

Hmm. I've followed the guide and successfully skipped the CID lock check of the device and flashed it to version 2.73.405.5 WWE. Problem is, I can't seem to get the device to boot into recovery mode after using flashrec (I did download and flash it just fine). the recovery mode (home + power) booted the device but it hangs at the boot screen where it says HERO. Any idea?
Edit: Ah. a little bit of the update. while the buttons do not work, i can use adb shell reboot recovery; however, after using flashrec, it still shows the old recovery screen ?
Edit2: confirmed, recovery flasher doesn't work now im using the SEA rom
I'll try the RUU_Hero_HTC_WWE_1.76.405.6_WWE_release_signed_NoD river.exe rom later

I had the same issue with Recovery Flasher I couldn't to boot into recovery. I was also unable to downgrade to the 1.7 roms due to a bootloader version error, arghhh. Anywho, managed to work my way round it, i'll explain below. I've got a T-Mobile G2 updated to the latest rom (so no root access).
I first followed the instructions on making a goldcard and then flashed the 2.73.405.5 WWE rom fine.
Now make sure you have the cm-hero-recovery.img (http://content.modaco.net/dropzone/modacopatchedrecovery-1.0.zip) on the root of your sdcard. Aswell as Instant Root (http://neilandtheresa.co.uk/Android/) now install Instant Root on the phone. It should pop up with a notification "instant root was sucessfully" or along those lines. (If you have a problem installing Instant Root make sure Settings>Applications>Unknown Sources is checked)
Instant root then allows for root access with adb shell using the following 2 commands:
1) adb shell
then
2) su
the icon should change from a $ to #.
Now flash the recovery image with the following command:
1) flash_image recovery /sdcard/cm-hero-recovery.img
This shouldn't take that long once completed it will go back the # prompt example below.
# flash_image recovery /sdcard/cm-hero-recovery.img (I typed this)
flash_image recovery /sdcard/cm-hero-recovery.img (this pops up)
# (this shows the flash completed)
Now pull out your usb cable and battery, turn on the phone with the battery in place while holding the home button and it should boot into the custom recovery .
Well, I hope this helps someone and I didn't just waste my time . Oh, thanks for posting the goldcard instructions.

it worked!!!
Thanks so much! I did the exact process before (see other thread) but I must have missed something. Following this process exactly is what did it. I am guessing something about the reboot and the RUU is where i went wrong before.
I can confirm this works on the 2.73.707.9 ROM

Yaaahaaaayyhaahhahahaahaayyyyyyyyyyyy!!! I feel so happy for all you guys who had this problem (although I myself did not!!)

I kind of half gave up at 6:00 am yesrterday and i just woke up (1
:27pm) and followed the instructions here and BAM! got a working nandroid backup and a custom rom \o/!!! thanks to all of you!

so it's tested and proven for 2.73.707.9?great!

umm ... guys.. if u dont mind me asking...... why do we need it?
do we have hero versions which cant be rooted with any methods?

dying4004 said:
umm ... guys.. if u dont mind me asking...... why do we need it?
do we have hero versions which cant be rooted with any methods?
Click to expand...
Click to collapse
yup, we couldn't root certain asian carrier roms and t-mob rom and they couldnt downgrade so the where stuck, until now....

tianci86 said:
so it's tested and proven for 2.73.707.9?great!
Click to expand...
Click to collapse
CONFIRMED! it works on 2.73.707.9 , just got 2.73.405.5 , im so happy , thanks soo much guys your the best

My Hero..... lol
Thanks, I thought I would be owned by T-Mobile for ever after the ROM update
Now I'm back to the HTC default ROM (NOT T-Mobile G2 Touch!!!), cup of coffee time before Rooting flashing etc and remaining from now on faithful to Paul and the MoDaCo ROM

hey guys!
i have a question
im a owner of an tmobile g2 touch and want to have the new firmware of the htc hero can i use this hack to update to the newest firmware because at the moment it says if i want so update: error this rom is not for your device, and so on..
thx !
bye
sry for my english im from germany

gyounut said:
hey guys!
i have a question
im a owner of an tmobile g2 touch and want to have the new firmware of the htc hero can i use this hack to update to the newest firmware because at the moment it says if i want so update: error this rom is not for your device, and so on..
thx !
bye
sry for my english im from germany
Click to expand...
Click to collapse
ja das stimmt

thx jesterz
successfully update singapore hero 2.73.707 to 2.73.405, rooting in a while...
{
"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"
}

d0s said:
I had the same issue with Recovery Flasher I couldn't to boot into recovery. I was also unable to downgrade to the 1.7 roms due to a bootloader version error, arghhh. Anywho, managed to work my way round it, i'll explain below. I've got a T-Mobile G2 updated to the latest rom (so no root access).
I first followed the instructions on making a goldcard and then flashed the 2.73.405.5 WWE rom fine.
Now make sure you have the cm-hero-recovery.img (http://content.modaco.net/dropzone/modacopatchedrecovery-1.0.zip) on the root of your sdcard. Aswell as Instant Root (http://neilandtheresa.co.uk/Android/) now install Instant Root on the phone. It should pop up with a notification "instant root was sucessfully" or along those lines. (If you have a problem installing Instant Root make sure Settings>Applications>Unknown Sources is checked)
Instant root then allows for root access with adb shell using the following 2 commands:
1) adb shell
then
2) su
the icon should change from a $ to #.
Now flash the recovery image with the following command:
1) flash_image recovery /sdcard/cm-hero-recovery.img
This shouldn't take that long once completed it will go back the # prompt example below.
# flash_image recovery /sdcard/cm-hero-recovery.img (I typed this)
flash_image recovery /sdcard/cm-hero-recovery.img (this pops up)
# (this shows the flash completed)
Now pull out your usb cable and battery, turn on the phone with the battery in place while holding the home button and it should boot into the custom recovery .
Well, I hope this helps someone and I didn't just waste my time . Oh, thanks for posting the goldcard instructions.
Click to expand...
Click to collapse
Did it last night and got it working, used the AMON Hero recovery image instead and partitioned my sd card without going through the manual adb solution.
Cheers

could this be adapted for the sprint hero?

Sprint Hero support request strongly seconded, i am desperate to get my CDMA Hero rooted.

have you guys tried using thesame method and got anywhere? I mean, from what I know is that you can't even boot in to recovery mode right? have you guys tries the adb method to boot into rec mode at least?

Aces!!!!
Worked on Indian 2.73.720 like a charm.
Thanks.

[ROM] EZbase v3.0 [25/04/2011] - odin / heimdall - Easy Full Graphical How-To

{
"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"
}
EZbase, is a fully deodexed and zipaligned pre rooted odin / heimdall image for people wanting to move from stock ROM's to custom ROM's. It used by a lot of people for a recovery image if it all goes wrong, simply flash this and you on a stock Samsung image with root and 2e recovery.
Still testing the new recovery & kernel so attached is a copy of EZbase with stock CWM Recovery, until the new recovery has been 100% tested!
Screenshots:
Main Recovery - Recovery Backup - Recovery Install - EZOdin​
Features:
Gingerbread & Froyo
Simple Recovery Menu
Added:
RomManager 3.0.xxx
TitaniumBackup 3.7.2
Notes:
Please read the EZbase How-To v2.00 - http://nfye.eu/EZbase/i9000/EZbase-2.00.pdf
Donators:
Euphoria
Thanks To:
RazvanG - 3-Button Combo Fix
Tr0jAn - Testing & Documentation Review
​

Downloads:
EZbase How-To
ROM
Gingerbread EZbase v4.0
Froyo EZbase v2.0
Other
EZOdin
Android Debug Bridge (a.k.a. adb)​

Reserved
Reserved 10 Chars

This is a Step by Step guide how to flash EZbase to your Samsung Galaxy S.​
There are lots of different ways to flash ROMs to your Samsung Galaxy S, Personally I use heimdall but thats because I use *nix. I find this one to be easiest and fastest for windows users.
If you complete this guide there the worlds your oyster, simply copy different mods/ROMs to the SD Card and flash directly from there going back to your base at any time should you need to revert back.
If you have any issues what so ever, the best place to begin is a clean EZbase flash.
NOTE: No root or anything is required, you can simply do this on a stock Samsung ROM.
Contents
What you need
Flash EZbase
Install Custom ROM
Other Information
ADB - Android Debug Bridge
Enable Debugging Mode
Mass Storage
Download Mode
Recovery Mode
3-Button Combo Fix
Warning!
There have been many reports about a problematic batch of Samsung Galaxy S phones that are not able to boot into recovery or download mode. If you are going to flash a ROM please make sure you can enter these modes before doing ANYTHING. See the 3-button combo fix if you cannot access Recovery Mode.
What you need:
EZOdin - http://nfye.eu/EZbase/i9000/EZOdin.exe
EZbase
Custom ROM (only if you wish to use a third party ROM)
- E.G. insanity - http://forum.xda-developers.com/showthread.php?t=843019
Nice to Have
Android Debug Bridge (a.k.a. adb) - http://nfye.eu/EZbase/i9000/adb.zip
Download all the EZOdin, EZbase CSC, PDA, PHONE and PIT if you do not have Samsung Kies installed, The Samsung USB Drivers will be required to. For simplicity sake place all the files into a single directory e.g. c:\toolkit\ however they can be placed where you like, hopefully in the future I might get all the requirements into an installer.
If you do not have Samsung Kies installed please install the Samsung USB Drivers and make sure your device is recognised by the OS. Once all the pre requisites have been fulfilled, then please continue to Step One or Step Two. If Samsung Kies is used please make sure you kill all Samsung Kies related services that are running (kies, tray agent, etc.)
Check that your phone has sufficient power, unplug your phone if it is plugged into USB or wall charger. Type *#0228# in to the dialler and check Voltage is at least 3800(mV).
Flash EZbase
Repartition is not mandatory, but it does not hurt to repartition the phone.
Start Phone in Download Mode (No Cable Attached)
Open EZOdin.
- Check Re-Partition
- Select EZbase.pit as PIT
- Select EZbase-PDA-XWJS3.tar.md5 as PDA
- Select EZbase-PHONE-XXJVE.tar.md5 as PHONE
- Select EZbase-CSC-XXJV1.tar.md5 as CSC
Connect Phone with USB Cable - Once ID:COM is yellow you are safe to continue.
Select Start
Complete, now wait for your phone to fully start-up before you continue with anything.
Install Custom ROM
Copy the ROM onto the Internal SD Card. This can be done via adb or placing your phone in USB debug mode and mounting the USB as storage.
Reboot the phone in recovery mode
Select "Install ZIP File"
Select "choose zip from sdcard"
Select "insanity-0.x.x.zip"
Select "Yes - Install"
Wait a while it installs the new ROM.
Select "Reboot Phone"
NOTE: As this is a de-odex`d ROM, First boot will take some time.
Other Information
ADB - Android Debug Bridge
To use the Android Debug Bridge you need to enable Debugging Mode first. Once enabled you will be able to use ADB and do a number of things.
Enable Debugging Mode
Press "Menu"
Select "Settings"
Select "Applications"
Select "Development"
Check "USB debugging"
Select "Yes"
Connect the phone to the USB cable and plug the other end directly into the PC.
NOTE: The computer should start installing the necessary ADB drivers. A total of three devices will be installed (Samsung Android Composite ADB Interface, Samsung Android USB Modem, Samsung USB Composite Device.
You should also now see two icons in the notification area.
Mass Storage
It is possible to mount the internal SD and microSD card as storage on your local pc, this is useful if you do not wish to use adb to copy files around.
If you wish to use your device as Mass Storage:
Pull down the notification area
Select "USB connected"
Select "Connect USB storage"
You should now be able to see your device in explorer
You should always safely eject the storage
Select "Turn Off"
Download Mode
To enter download mode, you hold the Volume Down + Home + Power. See image bellow:
Recovery Mode
To enter download mode, you hold the Volume Up + Home + Power See image bellow:
3-Button Combo Fix
You will need the following:
adb
root
xvi32 - http://nfye.eu/EZbase/i9000/xvi32.exe
P-SBL.tar.md5 - http://nfye.eu/EZbase/i9000/P-SBL.tar.md5
How To Check is Phone is Compatible:
adb shell
$ su (a superuser request will be displayed on the phone screen, accept it).
# dd if=/dev/block/bml1 of=/sdcard/bml1.dump
# exit
C:\adb pull /sdcard/bml1.dump
Open the bml1.dump file with XVI32.
- Search (in ASCII Mode) for OFNI.
If the block reads "[email protected]" just follow the tutorial below, as it is safe to fix.
NOTE: If it reads "x0" then STOP as this FiX will BRICK your phone if applied.
Open EZOdin
- Select the "P-SBL.tar.md5" as PDA file.
- Check "Bootloader Update"
Connect Phone with USB Cable and place phone in download mode (ADB method)
Once "ID:COM" is yellow you are safe to continue.
Select "Start"
NOTE: It should take three seconds to complete. After the update phone will reboot automatically. Do this at your own risk!

Reserved
Reserved Number 2

I was looking for this. Thanks. Will try insanity after this.
Darky's 9.3|Voodoo 5.4.1|ZSJPE|Lagfix OFF

Thanks again nitr8, I will use this on your next update of Insanity rom...
Nice

Great stuff - used EZBase earlier before flashing Insanity 0.6.6.
Like rixsta will use this method before future Rom flashes
Sent from my GT-I9000 using XDA Premium App

Thank you nitr8 =]

As always if you need any help man give me a call

Is this EZOdin safe/tested?
How is it different than the original (besides the UI, ofc)?

RayearthX said:
Is this EZOdin safe/tested?
How is it different than the original (besides the UI, ofc)?
Click to expand...
Click to collapse
Do you think I would release this untested? Yes its been tested, its STOCK Odin, with a revamped UI.

nitr8 said:
Do you think I would release this untested? Yes its been tested, its STOCK Odin, with a revamped UI.
Click to expand...
Click to collapse
YES! You could release it just for testing purposes
Just wanted to be sure.

RayearthX said:
YES! You could release it just for testing purposes
Just wanted to be sure.
Click to expand...
Click to collapse
it is check out post2

Nice you're pulling this up now!
I wondered, why you didn't release this.
Cheers,
Joël
Sent from my GT-I9000 using XDA Premium App

Darkyy said:
Nice you're pulling this up now!
I wondered, why you didn't release this.
Cheers,
Joël
Click to expand...
Click to collapse
It was ready a while back, we was about to do it and then a new firware came out and it got put on the back burner
My phone was on 6.6 but as it needed testing I redid it as per the written instructions just so we knew it worked 100%
IF people follow the guide then they SHOULD get a 100% working insanity rom with no hassle.. (we live in hope )
TrOjAn

Thanks for this, it's a nice initiative. I've been doing the same, just with different files from samfirmwares + I've needed to install a kernel to get easy access to root + cwm so this lets me skip that part
One thing though, you might want to either put this in your guide, or alternatively modify the app, but that Odin you have is version 1.7.. which has given me trouble (Windows 7, 32bit) in the past. Odin 1.82 works fine so just as a tip for people who might have problems getting odin to work
Aside from that this is a great idea!

akselic said:
One thing though, you might want to either put this in your guide, or alternatively modify the app, but that Odin you have is version 1.7.. which has given me trouble (Windows 7, 32bit) in the past. Odin 1.82 works fine so just as a tip for people who might have problems getting odin to work
Aside from that this is a great idea!
Click to expand...
Click to collapse
Hmm.. strange, Im on 1.7 Windows 7 32bit and I have not seen any issues.
What sort of issues have you had??
TrOjAn

TrOjAnUK said:
Hmm.. strange, Im on 1.7 Windows 7 32bit and I have not seen any issues.
What sort of issues have you had??
TrOjAn
Click to expand...
Click to collapse
odin either not connecting or just standing there doing nothing, never found out why but after using 1.82 its worked fine so I never felt like going back
and your files work with the standard odin anyway so it's not a big deal

akselic said:
odin either not connecting or just standing there doing nothing, never found out why but after using 1.82 its worked fine so I never felt like going back
and your files work with the standard odin anyway so it's not a big deal
Click to expand...
Click to collapse
Yes I have has similar like that happen as it goes, re installing the drivers normally fixed it
Anyway, glad you like it.. hopefully more will find the benifits of EZBase
TrOjAn

Sorry, just a mess

But thank all you guys to point it out

Very kind, hope it helps many.

Should we format /system qheb installing rom? When is the best time to wipe battery stat?
Sent from my GT-I8150 using Tapatalk

FelixAusChina said:
[HOW TO]root, flash custom recovery ClockworkMod v5.5.0.4 and ROM Customized 1.8Ghz ROM (now with experiment EUR OC ROM) without odin step by step from offical ROM 2.3.6
1. Root your phone
Rooting via Recovery mode(SD card)
a. Download this Zip-file http://dl.dropbox.com/u/47601401/update.zip copy this into the internal SD card.
b. While switched off, keep the following buttons pressed. Release the power-button once the Samsung Galaxy W(I8150) is switched on. At last press the menu button quickly while pressing the other two buttons.
Note: This instructions is written for the stock recovery. Custom recoverys should work very similiar.
{
"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"
}
c. Navigate with the volume up and down to apply sdcard:update.zip in Recovery Menu. Use the home-button to confirm your selection.
d. Choose (with volume buttons) the update.zip file on your internal sd card and confirm again with Home-button. You will have to wait for several seconds.
e. Now choose reboot system now and confirm with home button.
Now you device should be rooted.
The link: http://forum.xda-developers.com/showthread.php?t=1317394
2. Enable recovery ClockworkMod v5.5.0.4 with flashing in adb shell.
Don't flash the zip file, but extract and flash the img file
a. Root your devece(look above)
b. Copy downloaded recovery ClockworkMod v5.5.0.4http://www.multiupload.com/KTNBHX6JBG on internal sdcard
c. Disconect phone from copmuter and make sure that USB debugging is on
d. Connect it again but don't connect phone memory (computer shouldn't see sdcard and internal memory in Windows explorer)
e. Download the adb shellhttps://rapidshare.com/files/1061144422/android-sdk-windows.zip
note:If you just want to obtain and perform adb command, rather than to develop Android software, in fact, there are many adb streamline packets in internet, don't need the full Android SDK.
As the android-sdk version started from r08, adb wasn't contained in the downloaded files from the beginning, but was downloaeded by SDK Manager after that, and adb wasn't under the original tools directory. To maintain the text of the description of teaching would continue to apply the screen, I made ​​out of adb streamlined package from the r07 version.
f. Extract the file android-sdk-windows.zip into the root directory of C for teaching easily
g. open command prompt
windows 7: start-all programs-accessories-command prompt or search cmd
h. Then in the "Command Prompt" window, type the following command to switch to the adb directory
c:
cd c:\android-sdk-windows\tools
i. Enter the "adb shell", enter the phone to start the next command (think of it as the phone has a similar "command prompt" environment)
go on with this code:
Code:
adb shell
$su
#dd if=/sdcard/RZR-2.1.4-ancora-rec.img of=/dev/block/mmcblk0p13
but change the file name RZR-2.1.4-ancora-rec.img to recovery.img from recovery-clockwork-5.5.0.4-ancora.zip
j. Now turn off phone and turnd it on like this: hold Volume Up + Home + Power button, when Samsung sign appears relese power button but still hold other two, until recovery is loaded.
3. Download which ROM you like
4. Put the zip into Internal SD
5. Boot into ClockWorkMod, backup your current ROM using nandroid (just in case) then, use Install menu to Wipe data/cache and to install it from the SD card.
By the way, when you enter into the ClockWorkMod recovery, press the volume up-down-up for 3 times, you will see the option "go back" in the recovery menu.
Click to expand...
Click to collapse
By this method, is our bootloader is still locked?

Man, with all due respects, your post, and instructions are a mess, and particularly where you show adb commands to flash RzRecovery, then tell ppl here to do this:
go on with this code:
Code:
adb shell
$su
#dd if=/sdcard/RZR-2.1.4-ancora-rec.img of=/dev/block/mmcblk0p13
Click to expand...
Click to collapse
but change the file name RZR-2.1.4-ancora-rec.img to recovery.img from recovery-clockwork-5.5.0.4-ancora.zip
Click to expand...
Click to collapse
That is a total mess, and you make complicated particularly for noobs, something which is not complicated........
don't you know you have to be careful with "dd".....as it is called sometimes Data Destroyer:
http://www.softpanorama.org/Tools/dd.shtml
Just be careful ppl !!!

i just bought the new phone in germany, and updated to 2.3.6 by kies, then i decided to flash the custom rom, from root to recovery and to rom, so i checked all the trreads here, so i did it like i just said above, and it has worked for 3 days perfectly, so i wanna share my way to do that. because my phone is a new one, so i didnt' need to backup anything...
by the way, have u checked the thread [RECOVERY]Samsung Galaxy W i8150 RZRecovery by qzem??? it's here http://forum.xda-developers.com/showthread.php?t=1376196 i just followed that way...

irishpancake said:
Man, with all due respects, your post, and instructions are a mess, and particularly where you show adb commands to flash RzRecovery, then tell ppl here to do this:
That is a total mess, and you make complicated particularly for noobs, something which is not complicated........
don't you know you have to be careful with "dd".....as it is called sometimes Data Destroyer:
http://www.softpanorama.org/Tools/dd.shtml
Just be careful ppl !!!
Click to expand...
Click to collapse
i just bought the new phone in germany, and updated to 2.3.6 by kies, then i decided to flash the custom rom, from root to recovery and to rom, so i checked all the trreads here, so i did it like i just said above, and it has worked for 3 days perfectly, so i wanna share my way to do that. because my phone is a new one, so i didnt' need to backup anything...
by the way, have u checked the thread [RECOVERY]Samsung Galaxy W i8150 RZRecovery by qzem??? it's here http://forum.xda-developers.com/show....php?t=1376196 i just followed that way...

OK, Felix, it's not really a problem.......
but writing or copy/paste stuff in a Admin Command Prompt is hard enough, without having to modify the text you are quoting.
How hard could it be to post this:
adb shell
$su
#dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
Click to expand...
Click to collapse
This is what ppl will have to write into the dd command
if = input file.....of = output file
Use dd cautiously, improperly entering the wrong values could inadvertently wipe, destroy, or overwrite the data on the hard disk drive or device memory
Click to expand...
Click to collapse
BTW, me and qzem were probably two of the first on these forums, before we had dedicated forum......

irishpancake said:
OK, Felix, it's not really a problem.......
but writing or copy/paste stuff in a Admin Command Prompt is hard enough, without having to modify the text you are quoting.
How hard could it be to post this:
This is what ppl will have to write into the dd command
if = input file.....of = output file
BTW, me and qzem were probably two of the first on these forums, before we had dedicated forum......
Click to expand...
Click to collapse
but i have written "but change the file name RZR-2.1.4-ancora-rec.img to recovery.img from recovery-clockwork-5.5.0.4-ancora.zip" in my first post, haven't u seen that? I am gonna highlight it...but thanks for your remind and works for our SGW

Felix, I give up....but thanks for taking on board my suggestion....it may just save someone from a major catastrophe.
thanx again
ATB

FelixAusChina said:
but i have written "but change the file name RZR-2.1.4-ancora-rec.img to recovery.img from recovery-clockwork-5.5.0.4-ancora.zip" in my first post, haven't u seen that? I am gonna highlight it...but thanks for your remind and works for our SGW
Click to expand...
Click to collapse
The point is - why include the first (i.e. incorrect) version of the command at all? It would be much clearer just to include the correct version, after the change you mention. Including the incorrect version just makes the instructions more confusing.

FelixAusChina said:
But thank all you guys to point it out
Click to expand...
Click to collapse
Man, don't cry!!!!
sorry for being so blunt, but it's important, especially when using adb, and commands like dd to get it exactly right/correct......
we don't wanna brick anyone's phone
But, thanks anyway, the guide is basically good!!!
cheers, OK

FelixAusChina said:
But thank all you guys to point it out
Click to expand...
Click to collapse
Don't mistake directness for hostility.
We didn't want you to remove your guide completely - we're just trying to help improve the quality of it, for everyone's sake. Collaboration is what this forum is all about.
Restore the guide, make the suggested improvements, and let's see if we can make it even better.

[Galaxy Note2 TOOLKIT V4.1.0 TMOBILE] Drivers, Backup, Root, Recovery, Flash Stock

INTRODUCING THE SAMSUNG GALAXY NOTE2 TOOLKIT
GSM (GT-N7100) and LTE (GT-N7105) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1923956
AUSTRALIAN GSM (GT-N7100T) and LTE (GT-N7105T) SUPPORTED. USE GSM THREAD
SPRINT (SPH-L900) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957155
TMOBILE (SGH-T889) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957720
MOBILICITY, VIDEOTRON, WIND [SGH-T889V] SUPPORTED. NO THREAD YET. USE TMOBILE THREAD
AT&T (SGH-L317) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052779
BELL, ROGERS, SASKTEL, TELUS [SGH-I317M] SUPPORTED. NO THREAD YET. USE AT&T THREAD
VERIZON ([SCH-I605]) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052788
US CELLULAR (SCH-R950) SUPPORTED. NO THREAD YET. USE ANY
KOREAN SK TELECOM [SHV-E250S] SUPPORTED. NO THREAD YET. USE ANY
NOTE: If you want a new build added to the Toolkit then download and install, Type 'A' in the Model Selection screen and follow the instructions.
HOW TO VIDEOS ARE ON POST#4 (THANKS TO WWJOSHDEW) MAKE SURE YOU HAVE A LOOK AT THEM AS A VIDEO IS WORTH A THOUSAND WORDS
FUNCTIONS OF SAMSUNG GALAXY NOTE2 TOOLKIT V4.1.0 [9TH APRIL 2013]
Install drivers automatically
Backup/Restore a single package or all apps, user data and Internal Storage
Backup your /data/media (virtual SD Card) to your PC for a Full Safe backup of data
Root any public build (different options)
Root with Superuser (ChainsDD) or SuperSU (Chainfire) via CWM (works on ANY build)
[*]Root+busybox+rename recovery restore files via Custom Recovery
[*]Unroot (delete root files and busybox)
[*]Many root/unroot options including adb, recovery and sideload via custom recovery
[*]Perform a FULL NANDROID Backup of your system via adb and save in Custom Recovery format on your PC
[*]Pull /data and /system folders, compress to a .tar file and save to your PC
[*]Auto Update ToolKit to latest push version on startup (donator feature)
[*]Dump selected Phone Partitions, compress to a .zip file with md5 and save to your PC
[*]Install BusyBox binary on phone
[*]Flash Stock Recovery
[*]Flash CWM Recovery (thanks to Clockworkmod Team) or TWRP Recovery (thanks to Team Win)
[*]Rename Recovery Restore files if present
[*]Flash Insecure Boot Image for adb mode
[*]Flash Stock Boot Image back to your phone
[*]Create tar file to flash via Odin (from upto 10 image files) with 1-click process
[*]Download, Extract and Flash Stock Rom (full DETAILED steps) ESSENTIAL FOR WARRANTY RETURNS
[*]Rip cache.img to zip file in CWM format for editing and flashing (thanks to Adam Lange)
[*]Install a single apk or multiple apk's to your phone (being worked on)
[*]Push Files from your PC to your phone
[*]Pull Files from your phone to your PC
[*]Set Files Permissions on your phone
[*]Dump selected LogCat buffers to your PC
[*]Dump BugReport to your PC (if installed)
[*]Help, Information Screen for various tasks
[*]Mods Section to Modify your phone (being worked on)
[*]Reboot Phone options in adb mode
[*]Change background, text colour in ToolKit
[*]Device Information screen which pulls info directly from device
[*]Activate Professional features from within the ToolKit
--------------------------------------------------------------
Mod edit: Download link removed
MD5 Sum for V4.1.0: 37360aabdf3869aad55d12dd2c2b0b07
NOTE: As the ToolKit.exe and ModsSection.exe files are not Digitally Signed with a Microsoft Certificate they 'may' get picked up as potentially harmful by Antivirus Programs and deleted on first run. If this happens restore the file and exclude it from future scans to use it. This seems to happen mostly on AVG Free and Norton which is why I switched to BitDefender which is much better.
IMPORTANT: ONLY FLASH ROMS THAT ARE SPECIFICALLY MADE FOR YOUR PHONES MODEL NUMBER AS FLASHING AN INCORRECT ROM CAN SOFT BRICK YOUR DEVICE!
Credits: ChainsDD for Superuser, Chainfire for SuperSU, Chenglu for modded cwm.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN FREE (PUBLIC) AND DONATE (PROFESSIONAL) VERSIONS?
THE FREE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD POSSIBLY NEED TO MANIPULATE YOUR PHONE. NOTHING IS RESTRICTED. ACTIVATING THE DONATE VERSION WILL ADD THE ABILITY TO CHECK FOR UPDATES VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED TO MY SERVER WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. THIS ALSO MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE VARIANT OR CARRIER SO DONATOR VERSIONS WILL BE UPDATED SOONER. IF YOU ARE NOT ABLE TO, OR DO NOT WANT THE AUTO UPDATE FEATURE THEN ALL UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL DOWNLOAD VERSION AS SOON AS TIME ALLOWS AND THERE ARE ENOUGH UPDATES TO WARRANT IT. DONATORS WILL ALSO HAVE THE QUICK PICKS AND EXTRAS SECTIONS UNLOCKED AND THE 'NAG' SCREEN ON EXIT WILL BE DISABLED. NEW DONATOR FEATURES WILL ALSO BE ADDED TO THE TOOLKIT IN THE FUTURE.
AUTO REPLY LINKS FOR PAYPAL AND GOOGLE CHECKOUT TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
AUTO UPDATES ARE BY FAR THE EASIEST WAY TO KEEP THE TOOLKITS UP TO DATE AS I HAVE LOTS OF OTHER TOOLKITS TO LOOK AFTER. IF ANYONE HAS ANY VIEWS ON THIS PLEASE PM ME OR CONTACT ME AT [email protected]. PLEASE DO NOT POST YOUR VIEWS IN THIS THREAD AS I WANT TO KEEP IT CLEAN FOR USER SUPPORT.
{
"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"
}
(Changelog at the Bottom of Post#1)
--------------------------------------------------------------
PLEASE READ THE *FAQ* IN POST#2 BEFORE ASKING QUESTIONS
--------------------------------------------------------------
1. INSTALLING GALAXY NOTE2 DRIVERS
The first thing you need to do is to install the drivers. These are needed so that you can communicate with the phone via the PC and perform the tasks that the ToolKit offers.
NOTE: If you have Kies installed then it is advisable to uninstall it first to avoid conflicts.
a. Make sure your phone is booted into Android and the USB cable is unplugged.
b. Select Option 1 in the ToolKit to install the Samsung USB Driver pack. This should install all the neccessary drivers you need.
C. While the drivers are installing make sure that USB Debugging is enabled on your phone via the Settings, Developer options Screen.
d. After the drivers have been installed connect the USB cable and the PC should detect the phone and install the correct drivers. This will also happen when you enter Download Mode and Recovery Mode for the first time.
e. If you want to check the drivers then go to your Control Panel on your PC and open the Device Manager. With the USB cable connected you should see a device listed as 'Samsung Android Phone' or something similar and a driver attached to it.
NOTE: If you are having trouble with your device being detected or the drivers installing correctly then you could try rebooting your phone, using a different usb port and making sure no other drivers are installed on your pc.
--------------------------------------------------------------
2. USING MSKIPS' SAMSUNG GALAXY NOTE2 TOOLKIT
a. Download the Samsung Galaxy Note2 ToolKit package and run to install the ToolKit to your PC. The installation will also create a Shortcut on your desktop for easy access. You have the option to include or exclude the drivers files at installation so if you already have your drivers set up and are just updating the ToolKit then you can untick the drivers if you wish.
b. Once the ToolKit is installed make sure your phone is booted and plugged in via USB cable and double click on the shortcut on your desktop to run it.
c. You will be asked if you want to check for an Update. If you type 'yes' this will download and check the latest version numbers against the versions in the ToolKit. If there is an update available then you will have the option to download and install it (professional feature).
d. You will now be presented with a Model Selection Screen to choose the Model/Build that you are currently on. Type the number that corresponds to your desired selection. For example type '12' for INTERNATIONAL GSM MODEL [GT-N7100] 4.1.1 [Build ALJ1-ALJ3]. If you cannot find the build your device is using then type 'h' to select the HELP option to get more info.
NOTE: If you have a new build that isnt covered by the Toolkit you can also type 'a' in the Model Selection screen to see instructions on how to pull your stock image and send it to [email protected] so support can be added.
e. The Toolkit will now locate and download the boot image pack for your chosen Model. This is a new feature so the Toolkit is not limited to how many Models can be added and it cuts down ALOT on the download size. After the zip file has finished downloading it will be extracted to the correct folders and the files checked to make sure everything is ok.
f. When you enter the Main Menu you will see 'Adb Mode' at the top. If you have installed your drivers correctly then you will see your devices serial number under the text with 'device' next to it. If you see this then your device is connected and you can carry on.
NOTE: If you haven't installed the drivers and don't see a serial number at the top then this is the FIRST thing you want to do so the Toolkit can operate properly.
g. Each option in the ToolKit has full information on what it is and how to use it.
--------------------------------------------------------------
3. FLASHING A ROM, RADIO OR KERNEL VIA CWM RECOVERY
a. Download your chosen Rom, Radio or Kernel from the Development Forum, then make sure your phone is booted up as normal and connect your usb cable so it goes into MTP Mode. Copy the .zip file (DO NOT UNZIP IT FIRST) to the 'Internal Storage' part on your phone. Do not copy it to a Sub Directory as it will be harder to find when flashing it.
b. Enter CWM Recovery (shut down the phone then hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds).
c. Select 'Install zip from sdcard' and select 'choose zip from sdcard' if the file is on Internal Memory.
d. Scroll to your zip file and select. Then select 'Yes' in the list to start flashing.
e. When flashing is finished press the BACK Button to go back until you get to the Main Menu and then select 'reboot system now' to reboot your phone into Android.
--------------------------------------------------------------
4. FLASHING A ROM, RADIO OR KERNEL VIA DOWNLOAD MODE USING ODIN
Odin can be used to flash image files or parts of your phone. You can flash something as simple as a boot image or a complete system. Everything is packed in a tar or tar.md5 file on your PC and flashed via Odin which is a Windows OS program.
a. Make sure you have your tar file stored on your PC.
b. Reboot your phone to Download Mode [shut down your phone, then hold down the Home + Volume DOWN Buttons and press the Power Button for about 2 seconds until a Warning screen appears. Press Volume UP to continue to Download Mode.
c. Connect your phone via usb and the first box at the top under ID:COM should turn blue and have some text in it. If you are using Download Mode on your phone for the first time then you will notice drivers being installed to use it.
d. The site or page you downloaded the file from will usually give you instructions to set Odin but if not you want to load boot/recovery/system files to the PDA location and have 'Auto Reboot' and 'F.Reset Time' ticked and nothing else.
e. Click on 'Start' to start the flash. You can see what is happening in the text box in the lower left.
--------------------------------------------------------------
USEFUL INFORMATION
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
ChangeLog
ToolKit v4.1.0 (9th April 2013)
+Updated complete Toolkit structure for easier support and faster updates
+Added GT-N7100T and GT-N7105T models to the support list
+Added 4.1.2 support for many models. See screenshot for full list
+Updated CWM and TWRP Recovery to the latest model specific version
+Added TWRP NAND backup/restore procedure to backups section
+Updated SuperSU Root procedure to V1.25
+Updated Samsung usb drivers to 1.5.18.0
+Added more error detection and updated many parts of the Toolkit procedures
+Added Activation option and support procedure for new builds to Model Screen
+Updated Stock firmware download section with new Samsung images
+Adb server is now shut down if you exit from Model Selection screen
+Added more error control Toolkit processes
+Updated mods section
ToolKit v3.0.0 (18th December 2012)
+Rewrote soo many parts its hard to list them all
+Changed the Model Selection screen
+Split up images for all supported models to make them easier to distinguish
+Added support for Verizon, GT-N7105 (lte), AT&T and Korean SK Telecom
+Added new options to Root/Unroot Screen
+Added root+busybox+rename recovery restore files via Custom Recovery
+Added Root/Unroot via Sideload feature in Recovery
+Updated CWM Recovery to 6.0.1.9
+Updated TWRP Recovery to 2.3.2.3 for all available Models
+Updated SuperSU to 0.99
+Added Device Information Screen
+Added instant reply donate link to Toolkit
+Soo many more behind the scene changes
ToolKit v2.0.0 (27th October 2012)
+Added FULL support for Sprint (SPH-L900)
+Added FULL support for TMobile (SGH-T889)
+Added FULL support for US Cellular (SCH-R950)
+Updated SuperSU Root zip file to V0.96
+Updated CWM Recovery to V6.0.1.5
+Added TWRP Recovery V2.3.1.1
+Added option on all Root procedures to root with Superuser (ChainsDD) or SuperSU (Chainfire)
+Added option in ALLINONE Root routine to flash cwm or twrp Recovery
+Improved Root procedure on all builds
+Made some edits for Toolkit stability
+More tweaks
ToolKit v1.0 (7th Oct 2012)
+First version of Samsung Galaxy Note2 ToolKit released
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.

**FAQ**
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF (e.g removing system apps).
From Google:
Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
----------------------------------------------------------------------------
Q. I flashed CWM but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on Android that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from the Market). Delete the file recovery-from-boot.p from /system. Now when you flash CWM Recovery it will NOT be overwritten after a reboot. You can also use the Toolkit to rename the files if you wish.
----------------------------------------------------------------------------
Q. What is the difference between Nandroid and Titanium backup?
A NANDROID will backup the whole system including boot, system, data and recovery partitions so you can restore a complete rom and all data and settings.
Essentially Titanium Backup is used to backup apps and associated user data. These could be restored AFTER a full wipe and a new Rom had been flashed on your phone.
The other option now which google added into the new adb command list is the adb backup which is in the ToolKit and can do the same job as Titanium Backup but will store the data on your PC rather than on the phone (where it takes up space and could be deleted).
----------------------------------------------------------------------------
Q. When would i perform a nandroid vs a titanium backup?
You would perform a nandroid backup to back up your entire system including boot image and data and system partitions so you can restore your entire system back to that particular point in the future.
You would use Titanium Backup mainly to back up your installed apps and settings so they could be reinstalled easily and quickly on any future roms. You can also choose individual apps to backup or restore on Titanium Backup whereas if you restore your boot partition via CWM Recovery you are stuck with the whole lot.
----------------------------------------------------------------------------
Q. When I try to open the ToolKit I get a box pop up for a split second and then it goes away. My AntiVirus program says the file may be harmful.
The exe files I compiled are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) will pick it up as potentially harmful when it is not. They pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.
----------------------------------------------------------------------------
Q. I have Windows 8 and cannot install the drivers
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. Reboot again once the driver is installed and all will be well.
----------------------------------------------------------------------------
Q. I flashed the Stock Firmware Image. Odin flashes the file successfully and the phone reboots but it stays stuck on the samsung logo
If the firmware tar file does not include a userdata image (which most Samsung firmware do not) then your userdata partition will be left from your previous setup. If this is incompatible with the new firmware because of build or something else then your system will freeze on boot up.
This is easily fixable by holding the Volume UP, Home and Power buttons all at the same time for about 10 seconds until the device reboots to the Stock Recovery screen. Use the Volume Down button to scroll down to 'wipe data/factory reset' and press the Home button to select it. Go down to yes to confirm and your userdata partition will be wiped. Your device should now boot fine.

**RESERVED FOR MANUAL INSTRUCTIONS**

Reserved for how to videos on this incredible toolkit!
http://www.youtube.com/playlist?list=PLwCVKEYxr_z7FBQYT32dbYw_kdSJmSDH2
How To Root
http://www.youtube.com/watch?v=M9zF6x1MURM
How To Flash Stock Recovery
http://www.youtube.com/watch?v=9CL5x84Tu_U
How To Manually Boot to Custom (or Stock) Recovery
http://www.youtube.com/watch?v=9m6Uugh8ps8&hd=1
Sent from my SPH-L710 using Tapatalk 2

Can i unroot with toolkit?.Many thank for awesome work..:good:

thank you! worked like a charm!!!

simplelife said:
Can i unroot with toolkit?.Many thank for awesome work..:good:
Click to expand...
Click to collapse
Yes you can.
Mark.

So does this add to the flash counter?

Tiffany84 said:
So does this add to the flash counter?
Click to expand...
Click to collapse
Flashing any custom firmware (boot, recovery) will add to the flash counter but im sure Chainfire will update his Triangle Away app to include the US variants.
Mark.

simplelife said:
Can i unroot with toolkit?.Many thank for awesome work..:good:
Click to expand...
Click to collapse
mskip said:
Yes you can.
Mark.
Click to expand...
Click to collapse
Just to be certain, I can unroot with this? How? We don't have a stock recovery since there is no stock firmware avail. Can you please clarify? Thanx bud.

GREAT work and thank you for getting this into an easy toolkit form, as many people will be helped out by this!! I was already rooted, as some others were too, but you created a tool that needs a BIG :good:

teshxx said:
Just to be certain, I can unroot with this? How? We don't have a stock recovery since there is no stock firmware avail. Can you please clarify? Thanx bud.
Click to expand...
Click to collapse
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.

Is TWRP supported on the TMo Note II?

mskip said:
Flashing any custom firmware (boot, recovery) will add to the flash counter but im sure Chainfire will update his Triangle Away app to include the US variants.
Click to expand...
Click to collapse
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number

mskip said:
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Click to expand...
Click to collapse
Oh ok. I would, but I haven't rooted mine yet. Still deciding if I want to keep my grey one or exchange it for the white lolol. Hopefully, someone who is already rooted will be kind enough to do it for you.
Thanks for your effort and time.

Chainfire said:
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
Click to expand...
Click to collapse
PM sent w/ link for stock T889 kernel.img. build number is the file name. sorry i can't help with stock recovery.img since i already rooted and flashed CWM recovery.
---------- Post added at 11:43 AM ---------- Previous post was at 11:40 AM ----------
mskip said:
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Click to expand...
Click to collapse
hey mark, if u wanna post or PM me instructions i'll get u the mount points.

Chainfire said:
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
Click to expand...
Click to collapse
So nice to see you here. Thanks for all u do!!
Sent from my SGH-T889 using Tapatalk 2

I am getting issues with both TWRP and CWM. With TWRP, the data partition is unable to mount, making a full wipe a no go. With CWM, data partition can mount...but the external sd can't. Anyone else having these issues, or is it something on my end?

LvDisturbed1 said:
I am getting issues with both TWRP and CWM. With TWRP, the data partition is unable to mount, making a full wipe a no go. With CWM, data partition can mount...but the external sd can't. Anyone else having these issues, or is it something on my end?
Click to expand...
Click to collapse
I can use my extSD with CWM so it's something on your end. I used the toolkit for the N7100 but same stuff...

Chainfire said:
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
Click to expand...
Click to collapse
I just sent you a pm with the stock recovery.img from my device(T-Mobile Galaxy Note 2). My build number is JRO03C.T889UVALJ1. Hopefully this gives you what you need. Thanks again.
---------- Post added at 03:53 AM ---------- Previous post was at 03:43 AM ----------
mskip said:
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Click to expand...
Click to collapse
Just sent you a pm with the mount points for the T-Mobile Galaxy Note 2. Thanks for this tool. It's incredible.

[Guide] Make flashable ROM from the stock Android ROM..

Hey!
I'm not sure which section is better for this: Q&A or General, so I post it here..
On this (REALLY EASY) Guide I show you how you can make own "Flash-able" ROM from Stock Android ROM on your phone:
Requirements:
Galaxy Nexus toolkit / CWM recovery (I recommend the toolkit) <---- Can be downloaded here
Linux Ubuntu (Can be installed as second OS without any disk) <--- Here
Drivers for Fastboot and ADB: Driver for GSM, Win 32-bit Driver for GSM, Win 64-bit for Sprint and Verizon: check the Nexus Toolkit thread..
Let's Begin:
1. Connect Galaxy Nexus to PC via USB cable and go to settings > developer options > and enable USB Debugging
2. Open the Nexus toolkit program
3. Select your Nexus's model and if the Android version on that doesn't exist then choose the older one.
4. Select number (2) Backup and Restore your Phone
5. Select number (9) and then it asks do you have insecure boot.img or custom ROM, if you are using stock Android ROM with unsecured boot.img then type "no" and follow the instructions on it.., if you are using custom ROM then type "yes"
6. select number (2) Boot, System
7. Wait until it have done everything and then you can close it and go to the C:\Galaxy Nexus ToolKit folder and find folder "backups"
8. on that folder "C:\Galaxy Nexus ToolKit/backups/" you have .ZIP file: backup_2partitions_########.zip Move it to somewhere /users/ folder or to Desktop, E.g to /libraries/documents/,
If you are using Ubuntu on the same computer where you do this then move the .zip package to memory stick/another hradware
9. Now boot to Ubuntu OS "reboot" in "Boot configuration" select Ubuntu if you are using Ubuntu on the same computer then connect Memory stick and move the .zip file from it to Desktop, If you are using Ubuntu on the another computer then you can open users-server and copy file from that to your Ubuntu.
10. On Linux Ubuntu install this dsixda's android kitchen: Here and then extract it to somewhere..
Let's build ROM:
1. Move the .zip package from Desktop to Dsixda's Android Kitchen > original_update folder
2. Open runme.sh and run it via Terminal
3. Select number (1) Set up working folder from ROM
4. Press enter all the time when it asks something. (asks about recovery files what you might want to keep, so if you want keep them then jut press enter and don't type no to the terminal
5. when it is extracting system.img and asks password then type your password to the terminal and press enter
7. When you are in main menu, you may want to De-Odex the ROM, select (0) and then (11) De.Odex and then choose both system and framework folder!
8. You may want insecured boot.img, in Advanced options choose (12) and then choose (w), go to BOOT-EXTRACTED folder and then to boot.img-ramdisk folder, now open default.prop and change line
Code:
ro.secure=1
to
Code:
ro.secure=0
Now in terminal press enter and then (b)
9. Now (if you want) add root permission, zipalign apps, add busybox and its run-parts (init.d) support, add apps e.g. Adobe Flash player.apk to /system/app/
10. when you have modified your ROM then choose (99) and press enter then again enter and choose (2)
11. when all is done then go to OUTPUT_ZIP folder and move the maguro_#########################.zip to Nexus and flash it via CWM or ADB sideload or whatever which works with 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"
}
Hopefully this helps someone! DD
I will fix some things on this post when I have fixed my Nexus. EDIT: My Nexus is now OK, have modified this thread quickly..
I made this thread because I was bored and I messed up my Nexus so I had to make flashable ROM form my ROM from my Nexus.. DD

- How badly did you mess up your Nexus to have to use a toolkit and a kitchen to revive it? ADB didn't work? Fastboot didn't work?
- How did you manage to turn on USB debugging inside Android, by going to settings > developer options > USB debugging, if it was messed up? I thought you were on a bootloop, or no system installed?
- I don't get the Ubuntu part, steps 8, 9; care to elaborate?
About ROM building and the script:
- step 4: enter to everything the script asks? What questions? How do I know it's doing everything correctly? Linux isn't Windows, you know?
- step 5, what password do I have to enter?
Thanks...
Edit: it seems the author of that kitchen isn't supporting it anymore.
Edit: oh I see, you're running Ubuntu on a flash drive.
sent from my Google Galaxy Nexus

bk201doesntexist said:
- How badly did you mess up your Nexus to have to use a toolkit and a kitchen to revive it? ADB didn't work? Fastboot didn't work?
- How did you manage to turn on USB debugging inside Android, by going to settings > developer options > USB debugging, if it was messed up? I thought you were on a bootloop, or no system installed?
- I don't get the Ubuntu part, steps 8, 9; care to elaborate?
About ROM building and the script:
- step 4: enter to everything the script asks? What questions? How do I know it's doing everything correctly? Linux isn't Windows, you know?
sent from my Google Galaxy Nexus
Click to expand...
Click to collapse
I got the SystemUI has stopped popup by flashing systemUI.apk so when I flashed the original back and when I wiped cache and dalvik cache then it didn't help so then only think that works is to clean everything and then to flash ROM again.
Now I have fixed my Nexus but I have t install many apps again.
To install Ubuntu you open Wubi.exe and then as you can see you should choose install inside Windows, choose the size for Ubuntu which can be 4GB if you don't want to install any updates to it.. so it's easy...
step 8: you can't actually access the C:// drive via users server if you have not enabled any access to it, so I move files that I need from C:/ drive to somewhere /user/ folder or to desktop.
the step 4: you can choose what you want but it asks about deleting recovery files and deleting install-recovery.sh from update-script..
he is not supporting the kitchen anymore, but it works.
the password: It asks permission from you to unpack system.img
Password asking can be disabled somehow but I don't remember how..
And the ROM in my signature is made this way..

manumanfred said:
I got the SystemUI has stopped popup by flashing systemUI.apk so when I flashed the original back and when I wiped cache and dalvik cache then it didn't help so then only think that works is to clean everything and then to flash ROM again.
Now I have fixed my Nexus but I have t install many apps again.
To install Ubuntu you open Wubi.exe and then as you can see you should choose install inside Windows, choose the size for Ubuntu which can be 4GB if you don't want to install any updates to it.. so it's easy...
step 8: you can't actually access the C:// drive via users server if you have not enabled any access to it, so I move files that I need from C:/ drive to somewhere /user/ folder or to desktop.
the step 4: you can choose what you want but it asks about deleting recovery files and deleting install-recovery.sh from update-script..
he is not supporting the kitchen anymore, but it works.
Click to expand...
Click to collapse
Did you set the permissions right tried to fix permissions in cwm?
Regarding systemUI, you just had to restore a backup previously made before flashing. Or, if you had none.. just format /system and reflash ROM.
So, the toolkit only works in windows? Too bad, I don't have it.
Okay... so I don't have to worry about 8) either since I don't have a c:\ drive (they have ':' on paths? Madness.)
Nah, I'll pass.
sent from my Google Galaxy Nexus

bk201doesntexist said:
Did you set the permissions right tried to fix permissions in cwm?
Regarding systemUI, you just had to restore a backup previously made before flashing. Or, if you had none.. just format /system and reflash ROM.
So, the toolkit only works in windows? Not an issue.
Okay... so I don't have to worry about 8) either since I don't have a c:\ drive (they have ':' on paths? Madness.)
Nah, I'll pass.
sent from my Google Galaxy Nexus
Click to expand...
Click to collapse
It doesn't require C://driver, only that driver where is the installation destination E.g. driver D or F or G or whatever which one it is!
And yes I fixed permissions, it didn't help!
I had same issues when I ported CM9 to my Sasmung Jét, when I changed DPI it still didn't work well but when I deleted all the data, cache and another files e.g. android.log, kernel.log, etc. then it didn't show the SystemUI has stopped popup..
but if I change lcd density to 160 then I get that same popup and it cam be fixed by flashing ROM again without wiping everything..
I messed up my nexus 2 times today and now I try to keep my Nexus alive!

mmm... quite useful since flashing factory image is pain in the ass for noob like me...

Awesome!!