Database Users

Easy Rooting Toolkit - GT-I9000 edition

Based on: [ROOTING/UNROOTING] DooMLoRD's Easy Rooting Toolkit [v1.0](zergRush Exploit)
DooMLoRD UNROOTING Script v1.0
it should work/root any Gingerbread at least till 2.3.5 ... we do not have 2.3.6 to test =)
reported not working on XXJPY Froyo ...
Changelog for v103:
+ updated zergRush binary for today's update (21-11-2011)
+ updated Superuser.apk to 3.0.7
Changelog for v102 from DooMLoRD version:
+ modified to free up space for binaries and apps by removing PowerOn.wav and bootsamsung.qmg from /system/ (bootsound and bootanimation)
+ updated Superuser.apk to 3.0.6
+ updated busybox to 1.19.3
+ updaated zergRush binary to latest version for 02.11.2011
Download:
>>> GT-I9000v103.7z <<< - gt-i9000 modified toolkit - LATEST
>>> GT-I9000v102.7z <<< - gt-i9000 modified toolkit
do not get scared of lot +++ LOG: write failed (errno=14) seems to be working anyways
How to restore bootsound and bootanimation:
*) deleted PowerOn.wav and bootsamsung.qmg files are locared in /data/local/tmp/
1) to restore PowerOn.wav and bootsamsung.qmg you first need to free up space in /system/
tutorial by BlackDalmatian
=> install "Mount /system (rw / ro)" (utility from the market)
=> set /system as RW with this utility
=> install "Android Terminal Emulator" (utility from the market)
=> copy the two files with cp command
=> change permissions to 644 with chmod
(you can use any file explorer but DO NOT FORGET TO SET PERMISIONS)
Click to expand...
Click to collapse
2) fastest way to do it is by removing google apps - you can do it with this tool
[UTIL][25/AUG/11] Samsung Galaxy S Chlorine (or cwm update bloat remover generator)
3) after that just push files to their proper locations:
/system/etc/PowerOn.wav
/system/media/bootsamsung.qmg
4) and mow redownload all google apps you need via market,
this time they will be installed to /data/app/ not /system/app/
so no more problems with not enought space =)

Hi!
Do you think it works for my version of Galaxy S?
Firmware Version: 2.3.3
Baseband version: I9000BVJV2
Kernel Version: 2.6.35.7-I9000BVJV8-CL284116 [email protected] #2
Number of compilation : GINGERBREAD.BVJV8
Thanks!

i think that Revolution Team claaims that this exploid works on all froyo and gingerbreads ... i can confirm that it works on I9000XXJVT =)
it should work for you - if it will not, nothing will be broken or whatever - youre not risking anything
in case of root explod fail you will se something like that in log
[-] Bad luck, our rush did not succeed
Click to expand...
Click to collapse
and in case if it will work this
[+] Rush did it ! It's a GG, man !
Click to expand...
Click to collapse
with a bunch of (ignore this log error)
+++ LOG: write failed (errno=14)
Click to expand...
Click to collapse
after that there should be no errors or whatever
best would be for you to post output so i could tell you if it succeded 100%

Thank you so much! It worked!
I think its done because the script said "ALL DONE", and now i have SuperUser and i could install titanium backup.
Thanks again , now im going to copy the EFS folder .
Bye!

no, the script aint superperfect so it does not stop if there are some errors during the process - if ill find time maybe ill update it a bit
but if youve got su seems ok
shot me a pm if you would have any problems :]

I'm waiting daemon started sucessfully and no response yet how much time this takes?

hmmm disable and reenable usb debuging and unknown sources with disconected usb
and btw at what moment that happens, after zerling rushes ?
maybe posy your cmd output or screenshot of it? http://pastebin.com/ ?

$omator said:
hmmm disable and reenable usb debuging and unknown sources with disconected usb
and btw at what moment that happens, after zerling rushes ?
maybe posy your cmd output or screenshot of it? http://pastebin.com/ ?
Click to expand...
Click to collapse
Perfectly done thank you $omator.

ya like that rooting method also easy and clean
but it will probably be patched in 2.3.6/2.3.7

$omator said:
ya like that rooting method also easy and clean
but it will probably be patched in 2.3.6/2.3.7
Click to expand...
Click to collapse
That is amazing! I don't need a custom kernel now. Will we get 2.3.7?

burakgon said:
That is amazing! I don't need a custom kernel now. Will we get 2.3.7?
Click to expand...
Click to collapse
haha thats why i like it also so much =)
it is very hard to tell, but probably till the end of year there will be at least 2.3.6 update and then who knows, i hope that it will be some early ics for sgs1 leak in feb,march,april and in the meantime 2.3.7 most probably

Thanks $omator.It works on JVU
Tested here
http://jjpda.blogspot.com/2011/11/how-to-root-i900xwjvu.html
---------- Post added at 04:00 AM ---------- Previous post was at 03:50 AM ----------
jjamain said:
Thanks $omator.It works on JVU
Tested here
http://jjpda.blogspot.com/2011/11/how-to-root-i900xwjvu.html
Click to expand...
Click to collapse
Testing avatar and signature

hey can i use the unrooting method specified in the link to DooMLoRD's post???

his script should work

$omator said:
his script should work
Click to expand...
Click to collapse
Thanks for the info

thats basicly removing copied files in proper order

$omator said:
thats 'unrooting script' is basicly removing copied files in proper order
Click to expand...
Click to collapse
will add the link in first post
thanks

$omator said:
it should work/root any Froyo / Gingerbread at least till 2.3.5 ... we do not have 2.3.6 to test =)
Click to expand...
Click to collapse
dont work for me
FROYO.XXJPY
PDA.: I9000XXJPY
PHONE: I9000XXJPY
CSC.: I9000XAJPY
Build info: 2010.12
this is the output:
Code:
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a Froyo ! 0x00017108
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
Thanks
Ed

this is not full output

$omator said:
this is not full output
Click to expand...
Click to collapse
that's right, but this output show the zergRush fail, the exit code is 255
zergRush breaks in line 522
link: h ttps://github.com/revolutionary/zergRush/blob/ece853c03e23d190f715a3d9aa776748ab19aa8a/zergRush.c#L522

Full root for A50x ICS 4.0.3[LEAK]. Simple method.

Original article is published on this site and created by ZeroNull and vdsirotkin (4pda.ru).
For A500 and A501 ICS[LEAK] firmware.
How to:
1. The tablet should be already upgraded to stock ICS for A50x (or stock ICS A10x/A510 for other tablets).
2. Download this archive on the computer. Unpack it to any place.
3, On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch on.
4. Сonnect the tablet to the computer (Before connection it is recommended to update the driver for a tablet from here: A10x, A50x, A510).
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
6. Now you will have to install the following programs:
SuperUser APK
Titanium Backup
ATTENTION!
Don't install Busybox! It is already installed and established! If you reinstall it, some programs will become unable to access root permissions!
Change:
The error of final check of receiving root is corrected (The messaging that "root" isn't received, though it was not so)
Support of A510 of tablets is improved
This method uses the 'mempodroid' exploit and some workings out by ZeroNull and vdsirotkin (4pda.ru).
PS: Command "Mount ro/rw" for directory /system (partition) - works perfectly!
PS2: Sorry for the Russian language in the old executable file, the archive has been confused

ZeroNull said:
Original article is published on this site and created by ZeroNull and vdsirotkin (4pda.ru).
For firmware:
Acer_AV041_A500_0.019.00_WW_GEN1
Acer_AV041_A500_0.014.00_WW_GEN1
Acer_AV041_A500_0.009.00_WW_GEN1
How to:
1. The tablet should be already upgraded to ICS 4.0.3[LEAK] for A500.
2. Download this archive. Unpack it to any place.
3, On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch on.
4. Сonnect the tablet to the computer.
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
6. Now you will have to install the following programms:
SuperUser APK
Titanium Backup
ATTENTION!
Don't install Busybox! It is already installed and established! If you reinstall it, some programs will become unable to access root permissions!
This method uses the 'mempodroid' exploit and some workings out by ZeroNull and vdsirotkin (4pda.ru).
PS: Command "mount -o remount,rw /system" for directory /system (partition) - works perfectly!
Click to expand...
Click to collapse
I wrapped something like this up into a GUI ages ago Perhaps I'll make a linux & mac one at some point too. My GUI installs Superuser and allows the user to install Trebuchet, FaceLock (currently buggy) and other tweaks: http://forum.xda-developers.com/showthread.php?t=1520469

blackthund3r said:
I wrapped something like this up into a GUI ages ago Perhaps I'll make a linux & mac one at some point too. My GUI installs Superuser and allows the user to install Trebuchet, FaceLock (currently buggy) and other tweaks: http://forum.xda-developers.com/showthread.php?t=1520469
Click to expand...
Click to collapse
Ok. Read:
blackthund3r said:
exodusevil said:
You are wellcome! And if possible help me grow here in XDA using "Thanks button" (it's free lol).
Well, about the root is the same here, I can see superuser and su, and can go to shell and call #
But, when I try (for example) create a directory inside system the message "ready only" appear.
But it's my firts time trying to use root. Any help will be very glad!
Regards,
Click to expand...
Click to collapse
Simply fire up ICS Root and click "Remount /system rw" In the "Remount Tools" menu
Once you get the success message, feel free to unplug your tablet and play around with the system folder as you see fit
Click to expand...
Click to collapse
My method work "as it should".

ZeroNull said:
Ok. Read:
My method work "as it should".
Click to expand...
Click to collapse
How exactly?! Surely you'd need a patched kernel for that. The bash scripts in the zip file are incredibly complicated

Aw com'on. One of you guys install the full 500 ICS, and see if this works!
Then see if you can push a recovery image.

blackthund3r said:
How exactly?! Surely you'd need a patched kernel for that. The bash scripts in the zip file are incredibly complicated
Click to expand...
Click to collapse
Are you absolutely sure?

I just flash my Acer A500 with Acer_AV041_A500_0.019.00_WW_GEN1
This method works with my. I can use titanium backup and superuser. Thank you!
But I don't know how to test push a recovery image.
below is my way to root.
I use windows Vista.
1. On a tablet: "Settings" -> "Development" -> "USB debugging" switch on.
2. Сonnect the tablet to the computer.
3. Unpack the files. then put ICS_rooting folder in c:\ (I try unpack in other place not work)
4. then run runit-win.bat by run as adminstrator.
Done

This seemed to work for me on Acer_AV041_A500_0.009.00_WW_GEN1
Thanks a lot.

I have installed Acer_AV041_A500_0.019.00_WW_GEN1 and aquired root using this method.
I will try to push CWM or RA recovery.
The root access works perfectly. I just deinstalled all acer bloatware and other stuff.
Edit:
The strange part was, I could not get the ADB interface working on my laptop. When I switched my Acer from MTP (Media Device) to PTP (Camera device), found in storage settings, the ADB interface showed up in my device list under Windows 7. Then after a driver install, it worked perfectly.
When I switch back to MTP, the ADB interface disappears again.

Ping192 said:
I have installed Acer_AV041_A500_0.019.00_WW_GEN1 and aquired root using this method.
I will try to push CWM or RA recovery.
The root access works perfectly. I just deinstalled all acer bloatware and other stuff.
Edit:
The strange part was, I could not get the ADB interface working on my laptop. When I switched my Acer from MTP (Media Device) to PTP (Camera device), found in storage settings, the ADB interface showed up in my device list under Windows 7. Then after a driver install, it worked perfectly.
When I switch back to MTP, the ADB interface disappears again.
Click to expand...
Click to collapse
Maybe a reboot on the win system?

Moscow Desire said:
Maybe a reboot on the win system?
Click to expand...
Click to collapse
Hehe. I tried several windows installations. I think something is wrong with my acer. Like this, I have several strange things, like never get a fast fix on GPS. Whatever fix or GPS.conf I use... But it makes it challenging to het it working again

Pushing a custom recovery fails atm. I even get an error flashing the unlocked bootloader.bin
Code:
Loading bootloader...
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0xxxxxxxxxxxxxxxxxxxx
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 1192188/1192188 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader status: success (code: 0) message: flags: 1073840124
[COLOR="Red"]bootloader failed NvError 0x0
command failure: bootloader download failed[/COLOR]
All other nvflash commands fail afterwards.
After this command, the tablet enters "Entering OS download mode" with the acer logo in the middle.

Just update to Acer_AV041_A500_0.022.00_WW_GEN1.
After update Lost root. But use this method then got root again.
Thank you.

It didnt work for my acer, I meant it wasnt fully rooted. I saw superuser but when in Acer Receovery Installer, it says that Bootloader version 0.03.11-ISC is locked or something. Now I cant install any other rom as it got stucked at boot screen (receovery mode) with a message "Recovery verified failed". Anyone, please help me.
I need to use USB 3G on this tablet with this ISC or please help me downgrade to 3.2.1.
Many thanks

Jamesbond007vn said:
It didnt work for my acer, I meant it wasnt fully rooted. I saw superuser but when in Acer Receovery Installer, it says that Bootloader version 0.03.11-ISC is locked or something. Now I cant install any other rom as it got stucked at boot screen (receovery mode) with a message "Recovery verified failed". Anyone, please help me.
I need to use USB 3G on this tablet with this ISC or please help me downgrade to 3.2.1.
Many thanks
Click to expand...
Click to collapse
Take a look at my A500 APX Flash Tool with the patched bootloader, recovery and kernel package. That will get you ClockworkMod. To downgrade take a look at Timmydean's 3.2.1 downgrade package

Hi, will it work on ACER_AV041_A500_1.031.00_WW_GEN1 ?

CaH9 said:
Hi, will it work on ACER_AV041_A500_1.031.00_WW_GEN1 ?
Click to expand...
Click to collapse
+1 to this anyone try it yet and is their a simple way to unroot ics I need to send unit to Acer but its damaged so till its fixed I want root back!
Sent from my A500 using Tapatalk 2

I can confirm, that it works with ACER_AV041_A500_1.031.00_WW_GEN1 too

+1

How about the unroot part of things anyway to do that? For peeps that need warranty related things to be done?
Thanks
Sent from my A500 using Tapatalk 2

Wolf's ultimate flash and downgrade guide (NO ROOT NEEDED) (root opportunity for .21)

WARNING
This method will not work on any JB rom available, apparently google has patched the exploit.​
Note that downgrading method for unrooted devices is highly experimental and may turn your device into worthless brick. Read this WHOLE thread carefully before you start doing anything with your Transformer.
MOD EDIT: It is reported that this method doesn't work with the new Jelly Bean firmwares on the TF201 and the TF300T,
Sorry, but I will not be able to support you between 3rd and 15th of May because I have to pass my final exams.
However feel free to post your questions in this topic I am sure that somebody will be able to help you.​
Click to expand...
Click to collapse
Description​Method 1 - Rooted Devices
This method allows you to flash any update released by ASUS without need for custom recovery.
ROOT is required to unlock mmcblk0p4 write access for dd.
Method 2 - UnRooted Devices
This method allows you to flash any update released by ASUS, no mater for SKU etc.
It uses file linking trick to unlock mmcblk0p4 write access even when su is not present.
Method 3 - UnRooted Devices - Recommended
This method allows you to directly flash the recovery even on unrooted device. This may be used next to root your TF by prepared su package.
It uses file linking trick to unlock mmcblk0p4 write access.
Click to expand...
Click to collapse
Disclaimer​
Despite both methods have been confirmed (by myself) to work, the whole process of flashing mmcblk0p4 with dd brings high risk of bricking device by for example file system corruption.
I do not take any responsibility for damaged or bricked devices. Before flashing you have to assume the risk and chances of geting bricked.
Under no circumstances should you brake cmd during blob file is flashed by dd. If that happens do not reboot. PM me and go on IRC
Click to expand...
Click to collapse
Requirements​
BLOB file (look at links box at the bottom for few)
ADB enabled
Root acces (only method 1)
Click to expand...
Click to collapse
Notes​Sorry for the mistakes, but English is not my native language PM me if you find any so I will be able to correct them.
Before posting a question look into FAQ maybe it have been already answered.
Guide is inspired by Turge who wrote similar article for TFP (link here). However whole 2nd method was invented and described by me.
Thanks go to:
Code:
[CENTER]
AndroidRoot.mobi - for RazorClaw
ViperBoy - for viperMOD rooting tool
jcase - for NachoRoot
sparkym3 - for his ICS rooting methods
Roach2010 - for all his work
sbiriguda - who inspired me to dig around symlinking
[/CENTER]
Click to expand...
Click to collapse
Instructions - Method 1 - Rooted​1. Upload the BLOB file to internal storage of your tab. (mounted as /sdcard)
2. Connect tablet to the computer and start ADB session.
3. When you will be in adb shell execute following comands:
Code:
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
4. The command prompt will be empty as wnen nothing happen, do not panic wait until the end of the process. DO NOT INTERRUPT (it will take apx.3-10 min)
5. When you see the following message:
Code:
1066806+1 records in
1066806+1 records out
546204969 bytes transferred in 250.309 secs (2182122 bytes/sec)
(the numbers in resulted message may be diffrent but it has to have the same structure)
You can safety reboot the device by exiting shell and executing :
Code:
adb reboot
6. Once rebooted you will see ASUS EeePAD flashing progress bar. Be patient and wait till the end.
7. Tablet will reboot itself and start loading new system. (as it is first boot it may take few minutes)
8. Be happy from your new firmware.
ADDITIONAL OPTIONAL STEP
In some cases flashing previous firmware leaves data partition intact.
I suggest to clean it by booting with [vol down] and [power] pressed (you will see the info about the rom). Than wait until the screen with android and wipe data appear. Select wipe by switching with [vol down] and accepting with [vol up] pressed two times. It mostly happen when downgrading to HC from ICS.
Click to expand...
Click to collapse
Instructions - Method 2 - UnRooted​1. Upload the BLOB file to internal storage of your tab. (mounted as /sdcard)
2. Connect tablet to the computer and start ADB shell session.
3. When you will be in adb shell execute following commands:
Code:
mv /data/local/tmp /data/local/tmp.bak
ln -s /dev/block/mmcblk0p4 /data/local/tmp
exit
4. Now reboot your tab through:
Code:
adb reboot
5. Once you see ASUS loading screen you should be able to start ADB shell session again (if not just wait), than (in shell) execute:
Code:
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
6. The command prompt will be empty as wnen nothing happen, do not panic wait until the end of the process. DO NOT INTERRUPT (it will take apx.3-10 min)
7. When you see the following message:
Code:
1066806+1 records in
1066806+1 records out
546204969 bytes transferred in 250.309 secs (2182122 bytes/sec)
(the numbers in resulted message may be diffrent but it has to have the same structure)
You can safety reboot the device by exiting shell and executing :
Code:
adb reboot
8. Once rebooted you will see ASUS EeePAD flashing progress bar. Be patient and wait till the end.
9. Tablet will reboot itself and start loading new system. (as it is first boot it may take few minutes)
10. Be happy from your new firmware.
ADDITIONAL OPTIONAL STEP
In some cases flashing previous firmware leaves data partition intact.
I suggest to clean it by booting with [vol down] and [power] pressed (you will see the info about the rom). Than wait until the screen with android and wipe data appear. Select wipe by switching with [vol down] and accepting with [vol up] pressed two times. It mostly happen when downgrading to HC from ICS.
Click to expand...
Click to collapse
Instructions - Method 3 - UnRooted
This will definitely not work with Transformer Prime continue only if you are owner of TF101 of TF101G​
1. Upload the RECOVERYBLOB file to internal storage of your tab. (mounted as /sdcard)
2. Connect tablet to the computer and start ADB shell session.
3. When you will be in adb shell execute following commands:
Code:
mv /data/local/tmp /data/local/tmp.bak
ln -s /dev/block/mmcblk0p4 /data/local/tmp
exit
4. Now reboot your tab through:
Code:
adb reboot
5. Once you see ASUS loading screen you should be able to start ADB shell session again (if not just wait), than (in shell) execute (some times it gets longer, but do not panic it is normal):
Code:
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
6. The command prompt will be empty as when nothing happen, do not panic wait until the end of the process. DO NOT INTERRUPT (it will take apx.3-10 min)
7. When you see the following message:
Code:
8860+1 records in
8860+1 records out
4536396 bytes transferred in 1.718 secs (2640509 bytes/sec)
(the numbers in resulted message may be different but it has to have the same structure)
You can safety reboot the device by exiting shell and executing :
Code:
adb reboot
8. Once rebooted you will see ASUS EeePAD flashing progress bar. Be patient and wait till the end.
9. Tablet will reboot itself and start loading new system. (as it is first boot it may take few minutes)
10. Be happy from your new recovery.
ADDITIONAL - ROOTING
11. Download this SU + Superuser.apk package and place it on internal memory or microsd
12. Boot to recovery. (turn off your TF and than boot with [vol down]+[power] pressed, once you see the letters identifying the system press [vol up]
13. Now you should be in custom recovery. Select 'Install from zip file' and then select the file on desired location internal or external.
14. Once flashing is done go back and select 'Reboot system'
15. Now you got freshly rooted Transformer. ENJOY
Click to expand...
Click to collapse
BLOBs​
BLOB file can be extracted from any update file. It is contained inside XX_epad-user-x.x.x.x.zip achive. Where XX (e.g WW or TW) refers to SKU of firmware and x.x.x.x to its version (e.g 9.2.2.3)
Or you can pick up a few here
Now they are ziped to reduce the sizes (MD5 value shows the control sum of each blob not zip) (sorry for hostings but I don't have space on dropbox any more, you may register to increase) (if you know faster mirror PM me)
NEW MIRROR SITE WITH ALMOST ALL FIRMWARES HERE
TF101/G BLOBs (Transformer)
Honeycomb
WW 8.6.6.19 - MD5: D63D60F6C71F5B614B338244D3788735 - or mirrors (1 2)
WW 8.6.6.23 - MD5: 1227F19BC4415661CACB05A483504953 - or mirrors (1 2)
Ice Cream Sandwich
US 9.2.1.11 - MD5: 4F6069430B20C35C8833F50DFA0FE0FD - or mirrors (1 2)
WW 9.2.1.17 - MD5: 5C78C28C31888943AB67CCE4B4448319
US 9.2.1.17 - MD5: 380CA6399374FF5F84154509365A83F7 - or mirrors (1 2)
TW 9.2.1.17 - MD5: CA52E4AD670DFFA29DC1CBA04A0A4164 - or mirrors (1 2)
WW 9.2.2.3 - MD5: 5D5A44069346C4D7D2740E4100520692 - or mirrors (1 2)
TW 9.2.2.3 - MD5: pending
TF201 BLOBs (Transformer Prime)
Honeycomb
WW 8.8.3.33 - MD5: 5136E579FAEDDFE15F6AAE623B6CB67D - (or mirrors 1 2)
Ice Cream Sandwich
WW 9.4.2.11 - MD5: B2668A3387924B19A91F74ABF5DBE4E8 - (mirror)
US 9.4.2.14 - MD5: EF2E635BD6921BFA9D01FC0E4DD0644B - (mirror)
WW 9.4.2.15 - MD5: 55122257B30E9376DF463F3C1A8BA702 - (or mirror 1 )
WW 9.4.2.21 - MD5: 1129DC2643BD0F5DC6C07B9A1B619548 - (or mirror 1 )
RECOVERYBLOBs (only for TF101)
Rburrow's Rogue XM Recovery (mirror) - MD5: 6EE759A84ED02F0D95A029EC245CFDC5 - thread​
Click to expand...
Click to collapse
Hope it will help
Results​Confirmed to work on both TF101/G (ASUS Transformer) and TF201 (ASUS Transformer Prime)
However keep in mind that TFP have to be locked in order to use second method otherwise you may brick your device.
It probably can be used with slider as well
I also confirmed that it is possible to root any official OTA (on TF101/G) by flashing recoveryblob containing custom recovery and than update.zip with su and superuser app.
Proven that Method 2 also work with 9.2.1.21 update to downgrade the software and reroot device. - thanks alvin612.
Method 2 may also work on locked Transformer Prime however be careful and read warning and disclaimer in this thread.
Click to expand...
Click to collapse
Click 'Thanks' if I helped you

Let me just say this: you are a freaking genius. I didn't even think of symlinking /dev/block/mmcblk0p4 to /data/local/tmp so it would change ownership and permissions on reboot. This is f*ing brilliant!
Moreover, if you have a blob for CWM you can also use the second method to install it on an unrooted device and then root it using the customary update.zip with su and superuser.apk (yes, even on 9.2.2.3 TF101Gs).
Again, great job!

A big **sigh**, finally a solution for non-root users/ non-NVflash-ables to get back. I am rooted and will always be as long as the expliot is there but this should help many, many non-rooted people that are frustrated with ICS.
Many thanks.

Worth more than just using the thankometer - thanks for this.
Sent from my Transformer TF101 using XDA

absolute genius!!!!! Thanks

Just GENIUS
you are genius bro thank u so much for this guide. I'll try it tomorrow bcuz it's late " 1:00 am " and report back later.
Thanks again
Edit: I couldn't wait until tomorrow so i said let's try it but something happened and now my tab is bricked ( Stuck on EEE Pad screen )

hearts king101 said:
you are genius bro thank u so much for this guide. I'll try it tomorrow bcuz it's late " 1:00 am " and report back later.
Thanks again
Edit: I couldn't wait until tomorrow so i said let's try it but something happened and now my tab is bricked ( Stuck on EEE Pad screen )
Click to expand...
Click to collapse
OK, easy come on #asus-transformer at webchat.freenode.net will try to manage something.

OMG you saved my transformer!!!
Long story short, my tablet, as of 20mins ago, was in such an awkward status:
- has su and superuser.apk in /system/xbin
- all root checker apps say I'm NOT rooted
- on stock recovery but stock images put on external SD card won't get recognized
- whenever an app requests root, it got automatically denied by SuperUser.
and I saw this post....I'm back on 9.2.17 stock now!!
Thanks a million! ln -s...genius!!

Nice exploit! I knew there was a way!

alvin612 said:
Long story short, my tablet, as of 20mins ago, was in such an awkward status:
- has su and superuser.apk in /system/xbin
- all root checker apps say I'm NOT rooted
- on stock recovery but stock images put on external SD card won't get recognized
- whenever an app requests root, it got automatically denied by SuperUser.
and I saw this post....I'm back on 9.2.17 stock now!!
Thanks a million! ln -s...genius!!
Click to expand...
Click to collapse
Did you start off with 9.2.1.21? Or just fixing your botched 9.2.1.17?

kevchaps said:
Did you start off with 9.2.1.21? Or just fixing your botched 9.2.1.17?
Click to expand...
Click to collapse
9.2.1.21.
I messed up the rooting and recovery after ota from .17 to .21
Sent from my Transformer TF101 using XDA Premium HD app

You are genius wolf
It worked . Yes Yes Yes Yes Yes
THANK YOU SO MUCH WOLF​
FYI: I copied 3 files named ( EP101_SDUPDATE, EP101-SDUPDATE, EP101SDUPDATE ) so i don't know which one worked bcuz i tried the 1st name yesterday but didn't work .

alvin612 said:
9.2.1.21.
I messed up the rooting and recovery after ota from .17 to .21
Sent from my Transformer TF101 using XDA Premium HD app
Click to expand...
Click to collapse
Great that it worked for you.
When I get a new data cable, i think I will be headed back to honeycomb.

Sorry for asking! but Is 'rooted method 1' give any benefit over using CWM to flash stock ROM?

warlord234 said:
Sorry for asking! but Is 'rooted method 1' give any benefit over using CWM to flash stock ROM?
Click to expand...
Click to collapse
Nope, I described it to show the differences between rooted and unrooted methods

Sorry for asking. If I use this method on my tf101 to roll back to HC will it solve reboot and SoD problems?

Im trying method 2 and it wont let me adb shell after reboot.

Rodriger said:
Sorry for asking. If I use this method on my tf101 to roll back to HC will it solve reboot and SoD problems?
Click to expand...
Click to collapse
It should, that depends whether you had such issues on HC. If you did not than by downgrading you should get rid of them.
steven178s said:
Im trying method 2 and it wont let me adb shell after reboot.
Click to expand...
Click to collapse
After 1st reboot? Maybe give it a try after full bootup.

wolf849 said:
It should, that depends whether you had such issues on HC. If you did not than by downgrading you should get rid of them.
Click to expand...
Click to collapse
Should I try it if flashing stock HC by CWM didn't helped solve reboots and SoDs?

Thank you very much, i'm back on 8.6.6.23 from 9.2.2.23. The only thing i had, after the flashing Android want not boot. I made a wipe and everything is ok.
Thank you again.

Messing with a friends old DX

So, just to give a brief intro here... I used to have a DX, first buying it way back in its Eclair days, but have since (regretfully) moved to a D3. Trying to make the best of Moto's D3 flop, I've become pretty active over in the D3 sub-forum and have begun to learn the basics (I stress this, I ported a Bell Canada 2.3.6 ROM to the US D3 with 2.3.4, added light theming and 1% battery mods with assistance) of ROM creation and theming. I'm comfortable with RSD Lite and other programs like that.
Now, for this DX, I'm attempting to root it with Pete's 1 Click (Verision 1.06) which says it has worked on the DX. It fails on Step 3 pushing SU, BusyBox, etc. I thought the MotoFail method for the D4, Bionic, etc. which works for the D3 may work, so I attempted that, but it too failed on the same step. Just this morning I updated it to OTA 4.5.621, could this be the issue?
My friend has since crossed over to the dark side (iOS), so I want to make a nandroid backup of this phone as is, back up his SD cards, then wipe everything and play around with ICS on the DX since ICS on the D3 isn't a daily driver yet IMO, but I still want to mess with ICS.
Any advice about rooting .621? Also, does the DX only have BootStrap, or does a SafeStrap style hijack exist as well?
EDIT:
Ok, after some more Google'ing, I've found I need to root with Linux, and not windows because I've "accidentally" taken .621 OTA. I have a second HDD in my desktop with Ubuntu 12.04, so I should be able to follow a guide to root via Linux from that machine, correct?

redsox985 said:
So, just to give a brief intro here... I used to have a DX, first buying it way back in its Eclair days, but have since (regretfully) moved to a D3. Trying to make the best of Moto's D3 flop, I've become pretty active over in the D3 sub-forum and have begun to learn the basics (I stress this, I ported a Bell Canada 2.3.6 ROM to the US D3 with 2.3.4, added light theming and 1% battery mods with assistance) of ROM creation and theming. I'm comfortable with RSD Lite and other programs like that.
Now, for this DX, I'm attempting to root it with Pete's 1 Click (Verision 1.06) which says it has worked on the DX. It fails on Step 3 pushing SU, BusyBox, etc. I thought the MotoFail method for the D4, Bionic, etc. which works for the D3 may work, so I attempted that, but it too failed on the same step. Just this morning I updated it to OTA 4.5.621, could this be the issue?
My friend has since crossed over to the dark side (iOS), so I want to make a nandroid backup of this phone as is, back up his SD cards, then wipe everything and play around with ICS on the DX since ICS on the D3 isn't a daily driver yet IMO, but I still want to mess with ICS.
Any advice about rooting .621? Also, does the DX only have BootStrap, or does a SafeStrap style hijack exist as well?
EDIT:
Ok, after some more Google'ing, I've found I need to root with Linux, and not windows because I've "accidentally" taken .621 OTA. I have a second HDD in my desktop with Ubuntu 12.04, so I should be able to follow a guide to root via Linux from that machine, correct?
Click to expand...
Click to collapse
Correct.
©2012 Galaxy Note i717

So, for tethering, all I need is WiFi Tether from the Play Store? On the D3, we have to use a Moto proprietary program called RadioComm to rewrite the radio's data type signatures so that all 3G data through the phone looks as if it's phone use 3G and not tethered data.
Also, I'm looking for an ICS ROM... Suggestions?
Lastly, I did the Linux/Ubuntu SBF to the Milestone X, then ran ZergRush from Windows, but don't have root access.
Code:
----------------------------------
Easy rooting toolkit
created by DooM
using exploit zergRush (Re
Credits go to all those involve
----------------------------------
[*] This script will:
(1) root ur device using late
(2) install Busybox (1.18.4)
(3) install SU files (binary:
(4) some checks for free spac
(will remove Google Maps
[*] Before u begin:
(1) make sure u have installe
(2) enable "USB DEBUGGING"
from (Menu\Settings\App
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\App
(4) [OPTIONAL] increase scree
(5) connect USB cable to PHON
(6) skip "PC Companion Softwa
----------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or d
--- pushing zergRush
68 KB/s (23060 bytes in 0.327s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 l
[**] (C) 2011 Revolutionary. All r
[**] Parts of code from Gingerbrea
--- WAITING FOR DEVICE TO RECONNEC
if it gets stuck over here for a l
disconnect usb cable and reconn
toggle "USB DEBUGGING" (first d
--- DEVICE FOUND
--- pushing busybox
3558 KB/s (1075144 bytes in 0.295s
--- correcting permissions
--- remounting /system
mount: permission denied (are you
--- checking free space on /system
214 KB/s (439 bytes in 0.002s)
df: /mnt/secure/asec: Permission d
--- Free space on /system : 92% by
test: 92%: bad number
--- NOT enough free space on /syst
--- making free space by removing
rm: can't remove '/system/app/Maps
--- copying busybox to /system/xbi
/system/xbin/busybox: cannot open
--- correcting ownership
Unable to chmod /system/xbin/busyb
--- correcting permissions
Unable to chmod /system/xbin/busyb
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/sys
--- correcting ownership
Unable to chmod /system/bin/su: No
--- correcting permissions
Unable to chmod /system/bin/su: No
--- correcting symlinks
rm failed for /system/xbin/su, Rea
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.ap
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
I seem to be hitting some errors with ZergRush.
Phone info:
4.5.604.MB809.ACG-nTelos.en.US
Milestone X
2.3.5
BP_C_01.09.15P
4.5.1_57_MX2-34

redsox985 said:
So, for tethering, all I need is WiFi Tether from the Play Store? On the D3, we have to use a Moto proprietary program called RadioComm to rewrite the radio's data type signatures so that all 3G data through the phone looks as if it's phone use 3G and not tethered data.
Also, I'm looking for an ICS ROM... Suggestions?
Lastly, I did the Linux/Ubuntu SBF to the Milestone X, then ran ZergRush from Windows, but don't have root access.
Code:
----------------------------------
Easy rooting toolkit
created by DooM
using exploit zergRush (Re
Credits go to all those involve
----------------------------------
[*] This script will:
(1) root ur device using late
(2) install Busybox (1.18.4)
(3) install SU files (binary:
(4) some checks for free spac
(will remove Google Maps
[*] Before u begin:
(1) make sure u have installe
(2) enable "USB DEBUGGING"
from (Menu\Settings\App
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\App
(4) [OPTIONAL] increase scree
(5) connect USB cable to PHON
(6) skip "PC Companion Softwa
----------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or d
--- pushing zergRush
68 KB/s (23060 bytes in 0.327s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 l
[**] (C) 2011 Revolutionary. All r
[**] Parts of code from Gingerbrea
--- WAITING FOR DEVICE TO RECONNEC
if it gets stuck over here for a l
disconnect usb cable and reconn
toggle "USB DEBUGGING" (first d
--- DEVICE FOUND
--- pushing busybox
3558 KB/s (1075144 bytes in 0.295s
--- correcting permissions
--- remounting /system
mount: permission denied (are you
--- checking free space on /system
214 KB/s (439 bytes in 0.002s)
df: /mnt/secure/asec: Permission d
--- Free space on /system : 92% by
test: 92%: bad number
--- NOT enough free space on /syst
--- making free space by removing
rm: can't remove '/system/app/Maps
--- copying busybox to /system/xbi
/system/xbin/busybox: cannot open
--- correcting ownership
Unable to chmod /system/xbin/busyb
--- correcting permissions
Unable to chmod /system/xbin/busyb
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/sys
--- correcting ownership
Unable to chmod /system/bin/su: No
--- correcting permissions
Unable to chmod /system/bin/su: No
--- correcting symlinks
rm failed for /system/xbin/su, Rea
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.ap
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
I seem to be hitting some errors with ZergRush.
Phone info:
4.5.604.MB809.ACG-nTelos.en.US
Milestone X
2.3.5
BP_C_01.09.15P
4.5.1_57_MX2-34
Click to expand...
Click to collapse
Mine is actually almost bricked right now. I used gummy ics but I'm going to use blackice or something like that. As for tethering I don't know, as this is just my music player.
©2012 Galaxy Note i717

Still can't acquire root... Ideas?

redsox985 said:
Still can't acquire root... Ideas?
Click to expand...
Click to collapse
I literally just went through this process and it worked perfectly. Try SBFing to .621 again then do the Ubuntu steps again then use zergrush v3. That's exactly what I did.
©2012 Galaxy Note i717

Orange_furball said:
I literally just went through this process and it worked perfectly. Try SBFing to .621 again then do the Ubuntu steps again then use zergrush v3. That's exactly what I did.
©2012 Galaxy Note i717
Click to expand...
Click to collapse
I'm supposed to SBF to .621, then to Milestone X .605 via Ubuntu, then ZergRush you're saying? I also tried the live CD method to no avail.

redsox985 said:
I'm supposed to SBF to .621, then to Milestone X .605 via Ubuntu, then ZergRush you're saying? I also tried the live CD method to no avail.
Click to expand...
Click to collapse
Yes that is what I did
©2012 Galaxy Note i717

Ok, so I did the RSD Lite .621 SBF, that worked, I went to Linux, flashed that Milestone X SBF, went back to Windows, ran ZergRush v4, same damn error...

redsox985 said:
Ok, so I did the RSD Lite .621 SBF, that worked, I went to Linux, flashed that Milestone X SBF, went back to Windows, ran ZergRush v4, same damn error...
Click to expand...
Click to collapse
Do you have the drivers installed? Also, is USB debugging and unknown sources checked?
©2012 Galaxy Note i717

Orange_furball said:
Do you have the drivers installed? Also, is USB debugging and unknown sources checked?
©2012 Galaxy Note i717
Click to expand...
Click to collapse
Yep, yep, and yep. Would I possibly be able to manually root via ADB? I have it set up and connected now, the problem lies in that I can't really find much about manual roots any longer.

redsox985 said:
Yep, yep, and yep. Would I possibly be able to manually root via ADB? I have it set up and connected now, the problem lies in that I can't really find much about manual roots any longer.
Click to expand...
Click to collapse
I don't think you can manually root on .621. Have you tried another computer, or have you tried zergrush v3?
©2012 Galaxy Note i717

Just go here and read the instructions. Once you've taken the .621 update it's a bit of a process to regain root, but totally doable.
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
Or here.
http://rootzwiki.com/topic/19318-important-information-regarding-621-system-update/

SaurusX said:
Just go here and read the instructions. Once you've taken the .621 update it's a bit of a process to regain root, but totally doable.
http://rootzwiki.com/topic/19318-important-information-regarding-621-system-update/
Click to expand...
Click to collapse
This is what he is trying to do. Root the .621 using Ubuntu.
©2012 Galaxy Note i717

SaurusX said:
Just go here and read the instructions. Once you've taken the .621 update it's a bit of a process to regain root, but totally doable.
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
Or here.
http://rootzwiki.com/topic/19318-important-information-regarding-621-system-update/
Click to expand...
Click to collapse
I took the .621 OTA, booted Ubuntu 12.04 from my 2nd HDD, SBF'd to Milestone X in Ubuntu, went over to Windows 7 64bit HP, ran ZergRush v4, ZergRush v3, Pete's Moto Root Tools, and MotoFail, all of which failed to root. I then used RSD Lite to apply the .621 SBF (I'm now questioning if I should've done this via Ubuntu), went into Ubuntu, did the MX SBF, tried all rooting methods above and failed.
Then I tried rooting via ADB and I believe I successfully pushed su, busybox, and Superuser.apk to /data/local via ADB, but when issuing "adb remount", I'm unable to mount /system as read-write. I'm applying the .621 SBF via RSD Lite currently and having my second guesses about this doing this via RSD now...
This one via RSD 1FF-p3a_shadow_cdma_shadow-user-2.3.4-4.5.1_57_DX8-51-120111-test-keys-signed-Verizon-US.sbf

redsox985 said:
I took the .621 OTA, booted Ubuntu 12.04 from my 2nd HDD, SBF'd to Milestone X in Ubuntu, went over to Windows 7 64bit HP, ran ZergRush v4, ZergRush v3, Pete's Moto Root Tools, and MotoFail, all of which failed to root. I then used RSD Lite to apply the .621 SBF (I'm now questioning if I should've done this via Ubuntu), went into Ubuntu, did the MX SBF, tried all rooting methods above and failed.
Then I tried rooting via ADB and I believe I successfully pushed su, busybox, and Superuser.apk to /data/local via ADB, but when issuing "adb remount", I'm unable to mount /system as read-write. I'm applying the .621 SBF via RSD Lite currently and having my second guesses about this doing this via RSD now...
Click to expand...
Click to collapse
Why don't you sbf in windows using rsd lite back to .621 Droid x then do the Ubuntu followed by zergrush
©2012 Galaxy Note i717

Orange_furball said:
Why don't you sbf in windows using rsd lite back to .621 Droid x then do the Ubuntu followed by zergrush
©2012 Galaxy Note i717
Click to expand...
Click to collapse
redsox985 said:
I then used RSD Lite to apply the .621 SBF (I'm now questioning if I should've done this via Ubuntu), went into Ubuntu, did the MX SBF, tried all rooting methods above and failed.
Click to expand...
Click to collapse
I did...?

redsox985 said:
I did...?
Click to expand...
Click to collapse
Try it again maybe?
©2012 Galaxy Note i717

Oh man I feel for you redsox985. I love my Droid x and I wish that I could help. But the only thing I can reccomend is try sbfing in windows with the newest version of red lite. And then when it is done or tries to reboot, or then bootloops is to unplug the phone. Boot into the stock recovery or whatever you call it (you get to it by pressing the home and power until you see the android dude and exclamation point. Then you push either search or back. It varies with the version.) Then you want to wipe data and cache. Then try rebooting. It has worked for me in the past when I have come out of 2nd init roms.
If you have tried that then I am sorry. I can't help anymore.

OK here we go... I hope...
1. Boot into windows. I used 7, but whatever.
2. Then download rsd lite 5.x.x and download the Droix X .621 sbf file.
3. Enter download mode on the dx and connect it to the computer.
4. Sbf your phone in rsd lite to .621.
5. Unplug your phone.
6. Pull the battery of your phone.
7. Hold down POWER AND HOME until you see the triangle with exclamation point.
8. Click both the VOLUME UP AND DOWN buttons
9. This is stock recovery.
10. Wipe data/Factory reset.
11. Reboot.
12. Verify it works (connect to wifi, browse a few sites, etc.)
13. Start Ubuntu and follow the guide for sbfing to the Milestone X file.
***back to windows****
14. Root using Zergrush *****v3*****!!!!
15. Install the bootstrap .apk
***on the phone****
16. Install clockwork mod
17. Flash whatever you want*
*Nothing below 2.3.5. Definitely NO Froyo
If this doesn't work I'll walk you through it while IMing or texting or something. If I can follow the steps I can figure it out.
©2012 Galaxy Note i717
IF THIS HELPS... HIT "THANKS"!!!

[14/Feb][ROOTING/UNROOTING] DooMLoRD's Easy Rooting Toolkit [v1.0] (Insecure Kernels)

[ Info ]
(WINDOWS ONLY)
hi guys so i keep getting requests to create rooting kits for specific devices... so i have created a generic rootkit package which should work on any device which has INSECURE KERNEL already installed/flashed... and as a bonus i am also linking to an unrooting script!
it should work on any Andorid version (GB and above)
before we begin let me tell you that there is nothing new in the steps which this rootkit takes, its pretty standard stuff... i have created this only because i was getting numerous request for such a toolkit...
THIS ASSUMES THAT YOU HAVE INSECURE KERNEL FLASHED ONTO YOUR DEVICE (most cases this is possible only if bootloader is unlockable)
Creating insecure kernel for your device is beyond the scope of this thread.
How to use this toolkit:
just download the attached file
extract it using winzip/winrar/7zip to a folder on C:\
go to the folder where its extracted and execute "RUNME.bat"
read and follow the instructions on the screen!
Code:
---------------------------------------------------------------
Easy rooting toolkit (v1.0)
created by DooMLoRD
for in-secure kernels
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device assuming that you have an in-secure kernel (ro.secure=0) installed on your device
(2) install Busybox (1.18.4)
(3) install SU files (SuperSU)
(4) do some checks for free space, tmp directory (will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
---------------------------------------------------------------
[ Tested on ]
since its a generic toolkit it should work on any device, i will try and maintain a list at that following post:
Tested & Reported to be working on the THESE devices
[ Credits ]
Credits go to all those involved in making this possible!
Chainfire for SuperSU
[ Donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc My PayPal Donation Link
[ Download Links ]
DooMLoRD_v1-ROOT-insecure-busybox-su.zip
[ UnRooting ]
want to unroot? read this
regards,
DooMLoRD

List of devices this has been tested on:
Xperia Arc (GB, ICS)
Xperia Play (GB)
Xperia S (GB, ICS)
Xperia T (ICS, JB)
Xperia E Dual (ICS)

my yu yuphoria was bricked recently by doing a flash of miui9 which being on auto update installed the new rom because of which my phone was hard bricked ...i have tried to flash the stock rom and the miui 9 rom too ..but while flashing the system file it says FAILED remote flash write failure ....and it is happening with the system file alone rest all files like the data and all other are flashing just the system file is not i have tried lineage os too but same error for all system files alone ....i am using twrp for the recovery ...and on seeing the internal memory via twrp it shows zero internal memory ...if u could help me in how to fix my phone ...or tell me a thread where i can find the solution ...thank you for your help.....
i know it is out of the thread topic but i cant contact you ..your private message are full