|
Welcome to the GSM-Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. Only registered members may post questions, contact other members or search our database of over 8 million posts. Registration is fast, simple and absolutely free so please - Click to REGISTER! If you have any problems with the registration process or your account login, please contact contact us . |
|
Register | FAQ | Donate | Forum Rules | Root any Device | ★iPhone Unlock★ | ★ Direct Codes ★ | Direct Unlock Source |
| LinkBack | Thread Tools | Display Modes |
10-08-2013, 06:28 | #1 (permalink) |
No Life Poster Join Date: Aug 2011 Location: all device sell hear
Posts: 1,494
Member: 1627323 Status: Offline Sonork: WhatsApp+8801763009154 Thanks Meter: 481 | toshiba regza phone root not succes Phone connection is successful. Root process may restart the phone several times, keep your phone and data lines connected correctly. Getting Root privileges, please wait... Phone Model: IS04 Android Release: 2.2.2 Phone is restarting, please keep your phone and data lines connected correctly. >>Disconnect the phone‘£ how to root it ?? |
10-08-2013, 06:33 | #2 (permalink) |
No Life Poster Join Date: Jun 2005 Location: Kamalia, Pakistan. Age: 38
Posts: 16,852
Member: 151871 Status: Offline Thanks Meter: 71,421 | make it hardreset and try again. if again failed then it's not supported Br Faisal_Computer |
The Following User Says Thank You to Faisal_Computer For This Useful Post: |
10-08-2013, 06:47 | #3 (permalink) |
Freak Poster Join Date: Jul 2013 Location: B.A.N.G.L.A.D.E.S.H Age: 28
Posts: 478
Member: 1986151 Status: Offline Thanks Meter: 376 | IS04_root Root of Regupon is more simple In the au Garasuma? May be. ■ auto_rootkit_is04_v2.1 [Requirement] Android Ver:. 2.2.2 Update to 5014.1907.24 → 5014.1907.39:. Base Band Ver ■ make a what? -Permanent root, can be obtained in the base band version 5014.1907.39 → / rw mount possible for the system · Get the temporary root zergRush exploit, The rw mount the / system after patch in kmem, / add and system / bin / su to / system / app / Superuser.apk · The / data / local / kmem.sh / system / etc / install-recovery.sh In / system rw mount permanent. In patch libkddisecure_jni.so, libsecurecheck.so, of libandroid_servers.so You can avoid the su check (It is required in order to adb connection) IS04 ADB USB driver for http://spf.fmworld.net/oss/driver/is...r_IS04_1.0.zip http://spf.fmworld.net/oss/driver/is04/data/Readme.txt Attention Because it is separate from the driver to read the MicroSD with USB! USB driver for Windows to read the MicroSD is here gΡdb(IS04 USBhCo _E[h) - FMWORLD.NETiΒlj : xmΚ On which you installed the "USB Driver normal" of IS04 I will install the " ADB for USB Driver" . In Device Manager " Toshiba HSUSB Device " In IS04 side but if that does not appear " High-speed transfer mode" I try on the connection . ■ check items before running rootkit Setting the IS04 -> Applications - > Development - > Check USB debugging to [ ] Setting the IS04 - Check to > [ to disable the sleep ] - > Applications - > Development The device manager in the PC Android Phone -> Android ADB Interface Make sure that there are Check the results by typing adb shell in the folder of the rootkit Open a command prompt , To proceed as follows, and are able to connect successfully . -------------------------------------------------- --- * Daemon not running. Starting it now on port 5037 * * Daemon started successfully * $ ( Exit by typing exit or . Ctrl + C to be waiting for input here ) -------------------------------------------------- --- If you fail at this point, ready to run the rootkit batch because it does not well , You can state that you can connect to review the installation of ADB USB driver for the PC side , On the checked security software as well as do not interfere with the communication , Check by running the adb shell again . ■ I run the auto_rootkit_is04_v2.1 Su that forwarded to confirm they are functioning properly That it is in view of the following in a terminal window -------------------------------------------------- --- $ Su [Enter] # Id [Enter] uid = 0 (root) gid = 0 (root) -------------------------------------------------- --- The Titanium Backup starts normally - ES file Explorer MENU -> Settings That an error has not come out and check the Root Explorer from ■ Superuser that forwarded to confirm they are functioning properly That the " Superuser Request " is displayed to activate the main root app ( It is also displayed in the application of the above three ) ■ If the behavior of rootkit batch execution after funny - " You can not start for an incorrect application is installed" Message is displayed at startup "Applications of au -made " is not being root into startup The information is displayed to is checked , Possible to erase by pressing "back" button . ※ avoid in return therefore all out in a row 5-6 times when the OS starts In addition, if the error can not be avoided , it is preferable to run the rootkit again . I feel like more ... Because it is a successful method when I ****** the terminal of others , for reference . |
The Following User Says Thank You to _..::MuSa::.._ For This Useful Post: |
Bookmarks |
| |
|