Related
hello, i have a question.
How can I change the kernel or panel type without flashing?
I can't turn PDA in bootloader mode and flash :/
or i need a program, that turn in android BL mode np SSPL-KAIS.exe in Windows Mobile
Please help mi i have bad colors
You can change it using this command:
echo NUMBER > /sys/module/board_htckaiser/parameters/panel_type
but you need to do it every time you boot (or create a script to do it).
Why you can't flash? Your camera button is broken?
Please tell me how to do it.
Problem with buttons is very strange.
Hello, I have a very big problem. I have Htc Kaiser. Keyboar not working in windows (when he still had) apart from d-pad (sometimes, but with times, but more often department into quite other way ) I flash Android (is a problem with colors).
I can't turn PDA in Bootloader mode. I press and hold camera key, soft reset , and sometimes turn on key. PDa turn in SMART MOBILITY text and i can't go back to Windows, or change te Android kernel. Please help me
Sorry for my english
PS. in android after press OK in left side the almost all keyboard working (no working: a, q , shift, fn0
Pleas Help
Click to expand...
Click to collapse
i don't like double post...
press camera button (and keep it), take the pen, reset device, release when you see 4 color screen.
You can now flash from windows.
Did you flash hard-spl correctly?
Please before posting read the nand guide in atools.
You understand? I can'tturn bootloader. I press and hold camera button and reset device pen ( soft reset) and pda turn on text SMART MOBILITY and 10 seconds ago kernel is loading, no BL.
Yes i have HARDSPL 100% correctly.
How i can make this script? I must flash my device?
please help
Thanks , you are god i write script with example in a tools file and i copi this file in a andboot folder on SD card I have a beautiful colors
but i will flashmy device
the install-seq will be renamed on next boot so you need to add it to the init-scripts, write to the release thread to ask the release which file start on boot.
what? i dont understand your answer
Please tell me how can I add this script to boot (autostart)
Another way to get into the boot loader (if its your reset button like mine) is to unplug USB and battery, hold the camera button and power button. Put the battery back in and it will go in.
i try this combination thats not work
Try with this:
Code:
adb shell
echo "echo NUMBER > /sys/module/board_htckaiser/parameters/panel_type" > /system/init
echo "exec /init.android" >> /system/init
chmod a+x /system/init
change NUMBER with correct screen number
this script no working
in boot linux in reading script is error init: blablabla adb ....
corrected, try now
same.
This error:
/init: /install-seq.sh: line 1: adb: not found
sh: 0: unknown operand
arekmelerski said:
same.
This error:
/init: /install-seq.sh: line 1: adb: not found
sh: 0: unknown operand
Click to expand...
Click to collapse
Your phone for whatever reason does not have adb installed on it...
how I can install it?
adb is few lines further
l1q1d, help me please
Did you use exactly the command that i posted?
yes, this command also not working
/init: /install-seq.sh: line 1: adb: not found
line
ENABLING adb
(is after loading kernel?)
after A N D R O I D text
Symphony W25 device Finally Rooted !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All credits go to jason_cheng
Procedure given below:
1. First of all, you need Drivers For your symphony W25 (Smphony.W25/Karbonn.A7/Mobistar.S01/Ktouch.W650 All are the same phone)
Driver for winXP
Get them here (uploaded by prasad12ka4) Or Here uploaded by rainwalker
Click to expand...
Click to collapse
Drivers for Win 7 / Win 8
Get them here
Click to expand...
Click to collapse
64-Bit Win 7 Drivers
Get them here
Click to expand...
Click to collapse
Install them while connecting your phone on "USB debugging mode", and going to "device manager > other devices" on your pc. After installation disconnect the phone.
(I believe some of you are having problems installing the drivers. I recommend you install the drivers on a freshly installed winXP pc. I faced a lot of trouble doing it on my Win8 pc)
2. Download Android software development kit (SDK) from Here and install in pc. Default installation Directory should be C:\Program Files\Android\android-sdk
3. Android SDK may need Java development kit (JDK) installed in pc. If you need jdk, go here or go to their Website to download
3. Download Fastboot From Android Central and keep it inside
C:\Program Files\Android\android-sdk\platform-tools folder
4. Download Clockwork Mod Recovery for w25 from Link #1 or Link #2, unzip and copy to the same folder. replace duplicate (if prompted).
5 hook your phone up with pc in USB debugging mode and go to C:\Program Files\Android\android-sdk\platform-tools folder, Press Shift+right click inside that folder and select "open cmd window here". It opens a cmd window for that folder.
In the cmd window, type
Code:
adb devices
If the driver installations are correct, you'll see your device connected as w650 (as symphony is re-branded from k-touch w650)
6. Disconnect phone from pc and reboot it into the bootloader, by turning it off and holding [vol-up]+[power]
Till screen turns green and says fastboot:recovery ?, Like below
7. Plug your phone into your computer. On cmd window, type:
Code:
fastboot devices
Reply should be "???????????? fastboot" Meanng fastboot detected the device.
8. In the cmd line, type
Code:
fastboot boot recovery-english.img
And that's it. You'll have booted into the custom recovery (cwmr), and from there you can do a full backup, or restore a backup, or wipe the phone. Use vol up/down to navigate through screen and Power to select an item.
9. Use CWMr to backup your ROM. (It will be saved in: "SD card/clockwork mod/backup" on phone.) and reboot. Copy the backup into pc for further use.
Step 8 was to make sure cwmr works on the phone. It's a temporary port of cwmr on your device.
if problem occurs (less likely to occur), let us know in a comment and don't proceed further.
Otherwise, Proceed below for permanent port..
10. Repeat step 6 and 7. Go to C:\Program Files\Android\android-sdk\platform-tools folder and click on recovery.bat file. Click on it and in the next window, Press any key
Permanent port will be completed
reboot phone if not rebooted automatically.
11. To check cwmr, Repeat step 6 but keep pressing the two buttons even if the screen turns green (fastboot). Continue until.....
screen is red (recovery). after that you'll see Clockwork mod recovery page.
You'll need it to restore your original rom if you mess up anything.
12 In CWMr,
a)]Go to Advanced
b) Choose "Wipe dalvik-cache"
c) Now go to "Mounts & Storage"
d) Choose "Format /cache"
e) Shutdown your phone
13. Download and unzip bootrepack from this post (by jason_cheng). Copy the "boot.img" file from "rootrepack" folder and paste to C:\Program Files\Android\android-sdk\platform-tools folder
14. Repeat steps 6 & 7 (green screen)
15. In cmd window type
Code:
fastboot flash boot boot.img
and
Code:
fastboot reboot
see image below if you have any confusion.
16. After the phone is restarted, type in cmd window:
Code:
adb shell id
which should result "uid=0(root) gid=0(root)"
Rooting is now Unofficially completed
17. To verify, Type each line in cmd window, and press enter
Code:
adb shell
Code:
echo "1" > /system/pwned
Code:
cat /system/pwned
If the Reply to the last line is "1", Congrats ! you have root access to your phone!!
Now remove that test file you created just now. Type:
Code:
rm /system/pwned
What now?
18. Install "Superuser" from Play store
It does not come with su binary. For that, Go to this post and download only the attachment. Unzip it and put the files in C:\Program Files\Android\android-sdk\platform-tools folder.
19. Now open cmd window, type each line and enter.
Code:
adb remount
Code:
adb push su /system/xbin/su
Code:
adb shell
Code:
chmod 4755 /system/xbin/su
now open superuser and check for su binary. I don't recommend su update.
20. Install "Busybox free" from Play store (optional)
Rooting Officially Complete.
If you face problems at any step, please let us know in comments. We'll try to help.you out.
Also feel free to try out the IceCream Sandwitch based roms & the upcoming Jelybean rom for Symphony W25 on the second post of this thread.
If any of you come across a new rom for w25. Please do share.
If you come across dead links on my thread, plz let me know by posting comments, or PM me.
If you find this post useful, then plz hit the thanks button and share it with people who have this phone and waiting for root
End of tutorial.
.usefull links:
Karbonn Mobile A5 & A7 (Android 2.3.6)
Link2sd tuorial in bangla: সহজেই বাড়িয়ে নিন অ্যান্ড্রয়েডের ইন্টারনাল মেমোরি
How To Solve Internal Memory Problem(Great Post)
Custom Roms for Symphony W25 / Mobistar s01 / KTouch W650 / Karbonn A7
Custom Roms for Symphony W25 / Mobistar s01 / KTouch W650 / Karbonn A7
Here you'll find Custom ROM For Karbon A7 device. Which might also be campatible for Symphony w25. Read the respective posts/ comments carefully before downloading and installing.
(first of all back up your existing ROM with cwmr before any change you do to it.)
1) ICS ROM v1 for Symphony W25, Created By rainwalker
Click to expand...
Click to collapse
2) ICS ROM v2 for Symphony W25, Created By rainwalker
Click to expand...
Click to collapse
3) MIUI Gingerbread 2.3.7 ROM (update.zip file), moded By rainwalker
Click to expand...
Click to collapse
4) Rooted Stock ROM of Symphony W25 (update.zip file), uploaded By rainwalker
Click to expand...
Click to collapse
5) Stock Google android gingerbread for a7 by meosuper
Click to expand...
Click to collapse
6) ICS Huawei For Karbonn A7 / S01 by meosuper, Uploaded by ItsmezakiR
Click to expand...
Click to collapse
7) Official ICS ROM for Karbonn A7/Symphony W25 Uploaded by The Droid Master
Click to expand...
Click to collapse
8) Walton Primo ROM modified for A7 Uploaded by vinodkbishnoi
Click to expand...
Click to collapse
9) XION ROM FOR A5/A7 Uploaded by deadlyindian
Click to expand...
Click to collapse
10) ICS refresh V3 Uploaded by meosuper
Click to expand...
Click to collapse
11) CyanogenMod 10 (Karbonn A7) Beta Posted by prasad12ka4
Click to expand...
Click to collapse
12) Backstreet MOD™ v4.1.1 created by The Droid Master
Click to expand...
Click to collapse
13) Lithium 7 for Karbonn a7, symphony w25 and Mobiistar s01 Created by rainwalker
Click to expand...
Click to collapse
14) XINIX 8 for Symphony w25 Created by rainwalker (Recommended)
Click to expand...
Click to collapse
15) CyanogenMod 10 rom for W25 [Beta]
Click to expand...
Click to collapse
16) JELLYBEAN rom for W25 [Beta]
Click to expand...
Click to collapse
Maybe is needed to extract the "boot.img" to remove the restrictions on it, and make it rootable... Have you tried with generic "rooters"?
ICS Baseband Versions For Karbonn A7
ICS Baseband Versions For Karbonn A7 (= Symphony W25)
ItsmezakiR said:
1. 591369_8379_WCDMA_V000001
2. 591357_8376_WCDMA_V0005
3. 591352_8376_WCDMA_V0007
4. 591347_8376_WCDMA_V3070
Click to expand...
Click to collapse
ICS Search Key to Power Key (for Symphony W25)
vinodkbishnoi said:
Hi,
Karbonn A7 ICS. Now you can use search key of your A7 as power key.
Follow the procedure...
1. Download 7x27a_kp.kl.zip file and extract it.
2. Open terminal/Command prompt.
3. Connect your phone to PC via USB.
4. Run following commands.
c:/> adb devices
c:/> adb pull /system/usr/keylayout/7x27a_kp.kl
now copy this file on a safe place. So that if anything goes wrong you could be able to restore it.
now open folder where you have extracted the zip file. The extracted file will be of same name as "7x27a_kp.kl"
c:/> adb push <path to file 7x27a_kp.kl> /system/usr/keylayout/
Now reboot your phone. You will be able to use your search key as power key.
Click to expand...
Click to collapse
Change partition size on A7/W25
Part1:
Anil_Sharma said:
To begin with, you need a hex editor, HxD - Freeware Hex Editor is a great editor and it is very small(less than an MB). Then you need a baseband to edit, you need to locate the file named ' appsboot.mbn '.
That file contains the partition tables, remember this tutorial is about editing the partition tables not extending your physical memory.
So, lets get cracking. Open HxD from programs and open the appsboot.mbn file, now press F3 and search for ' cache ' and press F3 until you see something like this
.
As you can see the highlighted section of the picture
,
there are a few repetitions of ' F0 F0 F0 F0 xx ' multiple times, you are concerned with only the first two /system and /cache partitions respectively.
Remember, you don't need to specify the partition size for /data as it is done automatically when you flash the baseband.
Now back to the hex editing part, once you've decided how much space(in MBs only) you wanna allocate to /system and /cache use this link to Convert hex/dec and select the two digits after the F0 F0 F0 F0 like in this pic
and type the hex number for example in the screenshot B4 in hex equals 180 in decimal, which means /system is allocated 180 MB of space and do the same with Cache, I would recommend allocating 10 MB to it as you hardly ever use it. Then flash the baseband like you normally do through Fastboot.
If you have any doubts ask me and I will do my best to clear things to you. Click Thanks if I helped you, doesn't cost anything
Click to expand...
Click to collapse
Part2:
vinodkbishnoi said:
Hi,
I am attaching a file named "appsboot.mbn". This is used to determine partition size on android system.
There are two ways you could use it.
1. Replace appsboot.mbn file in any baseband update BP folder.
2. If you are handy with fastboot commands there is very simple method. Just boot your phone in fastboot mode (green screen mode) and use
following command....
C:\>fastboot flash APPSBL <path to appsboot.mbn>
And you are done.
You will find following changes.
1. Your partition size will be as shown in screenshot.
2. When you run command adb devices you will no more find S01 there, it will be A7
Download file here...
Download
Thanks
Click to expand...
Click to collapse
no one for help??
ahmed.zunaid said:
no one for help??
Click to expand...
Click to collapse
Your phone is the same with mobiistar s01 and karbonn a7, maybe the developer of symphony keep the original cpu clock(1ghz) and s01, a7 was underclocked to 800 to save battery. Now if you want to root.you must install fastboot driver and install cwm recovery for a7 first.then backup your current rom... when done, install rooted rom for s01 and you will have root, but your cpu will be underclocked to 800ghz.
And can you send me the link to download your backup rom??? I need the 1ghz kernel to mod my rom... thanks.
(If install drivers on w7 pc fail, try to use another pc with wXP-32bit).
These phones aren't - or shouldn't be - that difficult to root. I have just rooted an Xplorer W10 from W7 x64 (and reproduced on Linux), and it went without a hitch. Just a number of gotchas to watch out for (from here on I actually refer to W10 and all other models since they are of the same series):
1. Uninstall any kind of driver you have installed. Symphony does not provide drivers for their Android phones, as far as the website is concerned. You get what you pay for, and this is a relatively remote brand, so don't expect much. In fact, don't expect anything at all.
2. Download and run SuperOneClick. Click on the other tab and choose to check for drivers. You should be prompted to install a driver. Do it.
3. Unplug and replug the USB. Go into the ADB folder and shift-right-click, open a command prompt here. Type 'adb devices' and press ENTER. There should be at least one device listed (in the form of an alphanumeric serial).
4. If there is no device listed by ADB, use Linux to root. There is no need to install any driver on Linux, and SuperOneClick is multi-platform. You will need the mono package on Linux instead of .NET.
5. The phone is actually partially rooted. Whether by intention or by mistake, I am not sure. SuperOneClick will warn of this, so just choose to continue with the rooting process.
6. You should now be rooted.
Background:
There is no exotic bootloader locking going on with these phones, as far as I can tell. The manufacturers/vendors are really just trying to capture a certain segment of the market, so I doubt they'd go through extensive efforts to lock you in. Just find any exploit (right now psneuter and zergRush), put them on the phone along with the su and busybox binaries, execute the exploit, and you'll be good to go with the Superuser app.
ok ...
jason_cheng said:
These phones aren't - or shouldn't be - that difficult to root. I have just rooted an Xplorer W10 from W7 x64 (and reproduced on Linux), and it went without a hitch. Just a number of gotchas to watch out for (from here on I actually refer to W10 and all other models since they are of the same series):
1. Uninstall any kind of driver you have installed. Symphony does not provide drivers for their Android phones, as far as the website is concerned. You get what you pay for, and this is a relatively remote brand, so don't expect much. In fact, don't expect anything at all.
2. Download and run SuperOneClick. Click on the other tab and choose to check for drivers. You should be prompted to install a driver. Do it.
3. Unplug and replug the USB. Go into the ADB folder and shift-right-click, open a command prompt here. Type 'adb devices' and press ENTER. There should be at least one device listed (in the form of an alphanumeric serial).
4. If there is no device listed by ADB, use Linux to root. There is no need to install any driver on Linux, and SuperOneClick is multi-platform. You will need the mono package on Linux instead of .NET.
5. The phone is actually partially rooted. Whether by intention or by mistake, I am not sure. SuperOneClick will warn of this, so just choose to continue with the rooting process.
6. You should now be rooted.
Background:
There is no exotic bootloader locking going on with these phones, as far as I can tell. The manufacturers/vendors are really just trying to capture a certain segment of the market, so I doubt they'd go through extensive efforts to lock you in. Just find any exploit (right now psneuter and zergRush), put them on the phone along with the su and busybox binaries, execute the exploit, and you'll be good to go with the Superuser app.
Click to expand...
Click to collapse
I've used SuperOneClick before. In both 7 and XP machines. It gets stuck at "step 7".
Ok i'll try to do it again following your steps. I'll upload the screenshots
thanks for helping btw ...
No use ....
Nope. It didn't work. Hangs at step 7 (Pic Attached). tried on XP and 7.
Drivers install this time. and cmd>adb shell shows attached device, just like you said. but nothing happens after step7: waiting for device
I guess this process in not for me
can you provide link or tell me the process on how to add cwm recovery and backup the stock rom from the phone?
So that I can upload for you guys to check it out.
Note: my phone goes to recovery mode using the same method described in Karbonn Mobile A5 & A7 (Android 2.3.6
I checked.
ahmed.zunaid said:
Nope. It didn't work. Hangs at step 7 (Pic Attached). tried on XP and 7.
Drivers install this time. and cmd>adb shell shows attached device, just like you said. but nothing happens after step7: waiting for device
I guess this process in not for me
can you provide link or tell me the process on how to add cwm recovery and backup the stock rom from the phone?
So that I can upload for you guys to check it out.
Note: my phone goes to recovery mode using the same method described in Karbonn Mobile A5 & A7 (Android 2.3.6
I checked.
Click to expand...
Click to collapse
Unfortunately, CWMR needs to be built for your hardware in order for it to work. I think CWMR for the Karbonn should work without modification if it has the same hardware, so see if you can find info on getting CWMR onto the Karbonn. If the bootloader is really locked then you'll have to find some way to unlock first.
Backup the recovery partition [1] before doing anything, although I cannot verify whether it's the same partition across all phones. If anything goes wrong you will lose the ability to boot into recovery mode, but your phone will work. With a backup of the partition you can just bit-copy and rewrite the partition exactly as it was.
Because you already have the drivers installed using SuperOneClick, you may like to see now if Unlock Root works [2]. Else, go ahead and root the phone using the manual method. First, run the exploit [3]. Tell us how this goes, then we'll continue (basically upload the su binary and optionally the Superuser app). Otherwise we need to see what other exploit works.
[1] http://forum.xda-developers.com/showthread.php?t=1160213
[2] http://lifehacker.com/5873745/unlock-root-roots-nearly-250-android-devices-in-one-click
[3] http://forum.xda-developers.com/showthread.php?t=1296916
Could you please also report back with some files after running the following commands (you will find them prefixed with w25_ from the folder you're running ADB):
Code:
adb shell cat /proc/cpuinfo > w25_cpuinfo.txt
adb shell getprop > w25_propinfo.txt
Thanks. I suspect the W25 does not have the Karbonn A7 hardware. If the Karbonn is a rebranded Mobilstar S01 then it has a Qualcomm ARMv7 processor. The Symphony phones (hypothesis based on the only one phone I have, that is a W10) are rebranded Tinno [1] phones, with MediaTek processors.
My W10 is ARMv6, so it depends on whether the W25 has an SoC based on the latest MTK proc (which is ARMv7) [2]. That is highly unlikely because it (the proc) would be too powerful for the model number. As you may or may not know, binaries are not portable across ARM cores.
The phones do indeed have the same chassis and general specs, but any attempt to port and/or copy files/ROMs must be taken with great care and precautionary steps. There is, of course, no rule that each model must depend on the same manufacturer, but it's better to be safe than sorry.
[1] tinno.com (i'm not allowed to post links, funny, did so in the previous post)
[2] mediatek.com
jason_cheng said:
Could you please also report back with some files after running the following commands (you will find them prefixed with w25_ from the folder you're running ADB):
Code:
adb shell cat /proc/cpuinfo > w25_cpuinfo.txt
adb shell getprop > w25_propinfo.txt
Thanks.
...... ...... ......
Click to expand...
Click to collapse
#1 cpuinfo Attached
#2 Prop info Attached
It says ARMv7 processor. So what should I do now?
[off topic. rooted my friends Xperia arc today. Was very easy, like : DL kernel>click some stuffs>plug out>turn off>press n hold button>plug in>done
they should've made it simple for this one. just sayin .. :/ ]
ahmed.zunaid said:
#1 cpuinfo Attached
#2 Prop info Attached
It says ARMv7 processor. So what should I do now?
[off topic. rooted my friends Xperia arc today. Was very easy, like : DL kernel>click some stuffs>plug out>turn off>press n hold button>plug in>done
they should've made it simple for this one. just sayin .. :/ ]
Click to expand...
Click to collapse
Well, popular devices have more people tinkering with them and hence more results I suppose for budget devices we are on our own. After all, I believe these phones are pretty value for money and the effort to tinker is worth it.
Anyway, my suspicions are wrong. Symphony (or whoever they rely on) hand-pick reference models and do not depend on any particular vendor. The W25 is ARMv7 from Qualcomm, rebranded from K-Touch W650 [1] with modest hardware upgrades, almost similar to the Mobiistar and Karbonn:
Mobiistar Touch S01: Qualcomm MSM7225A
Symphony Xplorer W25: MSM7627A or MSM7625a (but because of 1GHz clock more likely the former) [2]
Either way the differences are minor I presume. Clock speeds are different and on-chip options vary slightly depending on what the manufacturer opts for. So with a bit of work someone could port existing recoveries and ROMs from similar devices. See [2] for a list of such devices in the respective row for MSM7627A.
You can worry about this when you come to recovery. The first hurdle to get through is root, so have you proceeded to run an exploit?
Also, if you haven't done anything, I would suggest doing a factory reset and then backing up the entire ROM simply with the cat command [3]. The homemade unsigned backup may come in handy later as there is no official ROM update.
[1] 123.chinatronic.com/products.php/K-Touch-W650 [replace 123 with www]
[2] en.wikipedia.org/wiki/Snapdragon_(system_on_chip)
[3] android-dls.com/wiki/index.php?title=HOWTO%3a_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
jason_cheng said:
..... Symphony (or whoever they rely on) hand-pick reference models and do not depend on any particular vendor. The W25 is ARMv7 from Qualcomm, rebranded from K-Touch W650 [1] with modest hardware upgrades, almost similar to the Mobiistar and Karbonn:
Mobiistar Touch S01: Qualcomm MSM7225A
Symphony Xplorer W25: MSM7627A or MSM7625a (but because of 1GHz clock more likely the former) [2]
Either way the differences are minor I presume. Clock speeds are different and on-chip options vary slightly depending on what the manufacturer opts for. So with a bit of work someone could port existing recoveries and ROMs from similar devices. See [2] for a list of such devices in the respective row for MSM7627A. ....
Click to expand...
Click to collapse
it says HTC Desire VC T328d, Huawei Ascend C8812 ...
jason_cheng said:
............
You can worry about this when you come to recovery. The first hurdle to get through is root, so have you proceeded to run an exploit?
Also, if you haven't done anything, I would suggest doing a factory reset and then backing up the entire ROM simply with the cat command [3]. The homemade unsigned backup may come in handy later as there is no official ROM update.
[1] 123.chinatronic.com/products.php/K-Touch-W650 [replace 123 with www]
[2] en.wikipedia.org/wiki/Snapdragon_(system_on_chip)
[3] android-dls.com/wiki/index.php?title=HOWTO%3a_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
Click to expand...
Click to collapse
Not sure how to use these commands. It says that the phone needs to be rooted to use these.
I'm trying to install clockworkmod.
meanwhile, If you have time, plz provide a simplified tutorial.
The zergrush in http://forum.xda-developers.com/showthread.php?t=1296916 doesn't download btw
Sorry, yes, that needs root. You must do everything you can to get root on the phone, because whatever you do you must have a backup. For CWMR, you must back up your recovery partition, else if your CWMR image does not happen to be compatible with your device you risk losing recovery mode.
For MTK devices like the W10, there is a method for non-rooted phones to carry out the backup [1], but I'm not sure about Qualcomm. So in the end, root is unavoidable.
1. Just get zergrush binary from the SuperOneClick archive (it is in another folder along with psneuter).
2. Copy the zergrush binary to the ADB folder.
3. Open a cmd window in the ADB folder just as you would normally type adb commands, then:
Code:
adb push zergrush /data/local/tmp/
adb shell chmod 755 /data/local/tmp/zergrush
adb shell /data/local/tmp/zergrush
Report back with the output.
[1] bm-smartphone-reviews.blogspot.com/2012/04/creating-rom-dump-of-your-mt65x3-device.html
jason_cheng said:
1. Just get zergrush binary from the SuperOneClick archive (it is in another folder along with psneuter).
2. Copy the zergrush binary to the ADB folder.
3. Open a cmd window in the ADB folder just as you would normally type adb commands, then:
Code:
adb push zergrush /data/local/tmp/
adb shell chmod 755 /data/local/tmp/zergrush
adb shell /data/local/tmp/zergrush
Report back with the output.
Click to expand...
Click to collapse
Hellions with blue flames !
See The attached pic
I have the same phone It's original model is ktouch w650
i evem tried to use update.zip method but it says sd storage not found
how do i know if my bootloder is unlocked or locked
tried unlock root with driver installed it says failed to aquire root access\
in adb shell it shows $ sign and if i try to get root acess it says acess denied
Oh boy, it looks like the vulnerability has been patched in your version of Android. Either that, or there is some hardware peculiarity (buffer size being reported wrongly - that's also when this zergrush error comes up) which I do not yet know how to deal with. There is another exploit called 'tacoroot' but I do not prefer going that route as it's not as foolproof/universal as zergrush.
Update zips need to be signed. When your recovery tries to verify the signature it fails, as it is not the signature of the manufacturer that made the update.zip.
Have you guys tried ALL the rooting methods posted in the A5/A7 thread? In the meantime I'll take a look at how Qualcomm ROMs can be dumped.
edit: I'm pretty sure your device has a fastboot mode. If so, you can "hot" boot any cwmr image without flashing it using "fastboot boot theimage.img" as far as I can recall. Having fastboot is a blessing (which the MTK devices do not have) so follow the first few pages of the A7 thread.
thanks
thanks for your hard work....
can you tell me how to acess fastboot?
and also when i press and hold vlo up and power button its displayes" Ap fastboot:recovery " and screen becomes green and then if i keep pressing it goes red into recovery mood
but if i let go at green screen it stays that way
and when i pressed vol down+ power key it said im black screen and yello text " ENTRY QPST DOWNLOAD "
shaon121 said:
thanks for your hard work....
can you tell me how to acess fastboot?
and also when i press and hold vlo up and power button its displayes" Ap fastboot:recovery " and screen becomes green and then if i keep pressing it goes red into recovery mood
but if i let go at green screen it stays that way
and when i pressed vol down+ power key it said im black screen and yello text " ENTRY QPST DOWNLOAD "
Click to expand...
Click to collapse
Sorry, the W10 is my first ever experience with Android (I was looking for a cheap way to find out how the stuff works), and as it does not even have a bootloader mode I have no idea about fastboot. I have only been with this phone/Android for about a month, so there's still a lot more to learn.
But as far as I can tell "AP Fastboot" already implies that you are in fastboot mode. You need the fastboot drivers installed on your PC, and then when you are at the green screen the phone will accept fastboot commands. [1]
If you guys manage to do this, what I would suggest is hot-loading a Karbonn A7, Mobiistar S01 or any other potential compatible CWMR image, then immediately making a full ROM backup. You can then upload recovery.img and I'll see if I can port it, and after that boot.img so we can at least get you root adb shell if by then rooting is still a problem.
And btw, if it was not clear in my previous post, rooting using current "standard" methods is not going to work as the latest gingerbread vulnerability (which zergrush exploits and many of the tools use zergrush) has been patched since December 2011. Unfortunately, it looks like the build of 2.3.6 that the W25 has is from a period after that, so zergrush on the W25 is a no-go. If you want to try, just follow the adb steps above which was posted for ahmed.zunaid.
[1] http://www.androidcentral.com/how-i-back-my-stock-unrooted-galaxy-nexus
Rooting Ascend P1 U9200 B315 EUI1.5 JB v4.1.1
----------------------------------------------------------------------------
Anyone wanting to root there Ascend P1 U9200 phone after the new firmware update, here are the files, and info you need, to do so...
First off, plug UR phone in switch it on and let Windows search for the driver, Then click "Let me choose..." or "browse for it..." or similar. Then select "Let me choose which driver to install", then click "list of drivers" or similar, Then click the one near the top that has adb or similar in the title, it don't matter if you choose the wrong one, it just means it wont connect and you'll have to redo this part again and pick a different driver.
Remember!! You MUST run these commands as Administrator.
1. Download the files below, extract them to a folder, preferably one without any spaces in the path, i.e.. C:\U9200Root\ should do perfect.
3. Right Click the "Click-To-Root-U9200.bat" file and under compatibility options click run as administrator or the like.
4. Run (Double Click) the Click-To-Root-U9200.bat (As Administrator!) (or right-click then, "run as administrator...")
4. Reboot your fone and click yes on your fone to install SuperUser.
that's it, your rooted
for those wanting to do the commands there self...
1. Download & extract the files to C:\U9200Root\
2. In the CLI type: "C:\U9200Root\adb reboot bootloader"
3. Then "boot TWRP.img"
4. Then Restart your fone and choose yes to install SuperUser
PS if you've not got much space left in your system partition you may have to delete something from /system/app/ to make space for the SuperUser files.
REMEMBER the space reported on your fone by android is the space on your data partition/memory & sd card and not the system partition!
You can check how much system data etc space you have left from terminal if u have it installed, or on the TWRP recovery which you will have just installed.To do this, Reboot the fone holding the Vol. Up Button, click on advanced then terminal then type "df -h" without quotes if system partition is less than say 10-20mb free then delete maybe, uneeded languages?, chrome.apk?, GSM_Maps.apk? or the like, then reinstall them to the /data/app part later. Since many of these apks get updated and the old ones left undeleted in /system/app/ anyways, I always move the system apks updates from /data/app to /system/app/, makes things a lot tidier and saves a lot of space both in /data/app and /system by not having two of every apk file youve ever updated just remember to copy the libs to /system/lib(s)
Anyways hope I helped someone with this...
cheers John -G-
PS Please Click on Thanks to Thank me as i have 0 in my Thanks Meter lol
PS I moved this to here as it was added to the end of an old un-related topic sooo.... John -G-
ask me any questions you have, do you like my multi color dos txt in my bat file (Coders will get it,its unusual and very hard to do with many colors )
sorry for been so long but i never knew no one would move it or stick it ???? and i was in jail for a while there so,,,
...Good Luck Rooting/Moding!!!
Software LOL
Heres The Software LOL..........
here all my drivers
the drivers------->>>>
shall stonri
sonnettie said:
the drivers------->>>>
Click to expand...
Click to collapse
Where can I find blaze driver?
Hi
After adb reboot bootloader you can also install CWM with fastboot :
fastboot flash recovery clockworkmod.XXXX.img
With CWM you can backup your phone (always a good idea )
After rebooted in CWM install SU with any zip file (ex : SU___Busybox_1.20.2_Flashable.zip )
phoenixpb said:
Hi
After adb reboot bootloader you can also install CWM with fastboot :
fastboot flash recovery clockworkmod.XXXX.img
With CWM you can backup your phone (always a good idea )
After rebooted in CWM install SU with any zip file (ex : SU___Busybox_1.20.2_Flashable.zip )
Click to expand...
Click to collapse
Worked like a charm.
It's what i did with my phone, ans cwm saved me a couple of times
Envoyé depuis mon U9200 avec Tapatalk 4
How to remove TWRP...? I want to update U9200-EM-UMTS-V100R00G411D00B336....thanx in advance.
Stuck
My U9200 is just stuck on the HUAWEI logo when you boot it...
And the cmd application just keeps saying < waiting for device >
Any help is appreciated...
with B336 this method doesn't work.
EDIT:
The problem is not in TWRP or CWM; the problem is that there is not enough space in folder /system/app.
From TWRP I went to "Advanced" and then "file manager"; here from the /system/app I deleted all the languages other than Italian-pack (my language), chrome.apk and gsm-map.apk. Then I flashed SU_flashable and after boot-up SU was finally installed.
It seems that the difficulty of obtaining root permissions in all stock roms from b105 onwards is precisely linked to the lack of space in the / system / app.
I hope to be helpful to those who find themselves with the same problem.
Ricolaa said:
My U9200 is just stuck on the HUAWEI logo when you boot it...
And the cmd application just keeps saying < waiting for device >
Any help is appreciated...
Click to expand...
Click to collapse
you need the fastboot drivers or install hisuite from hauwie
where what is a Blaze driver? It doesn't work!! It asks for the blaze driver which I cannot seem to find!!!!
How can I go back to the stock firmware from CWM ignore if I am posting on a wrong thread
cVinu said:
How can I go back to the stock firmware from CWM ignore if I am posting on a wrong thread
Click to expand...
Click to collapse
Just downloaded the stock rom and flash it with your recovery.
Sent from my U9200 using xda app-developers app
awaisthebest said:
Just downloaded the stock rom and flash it with your recovery.
Sent from my U9200 using xda app-developers app
Click to expand...
Click to collapse
I recovered stock recovery and flash with B123 but showing error msg installation failed!!!!!!
hi im having some issues trying to get the SU, i cannot erase the .apk contained in /system/app in order to gain more space.
- i cannot see any folder inside of system folder just one called /system/bin
i really dont know if that really would be the problem because i checked with "df" command and i see everything righ
but when i reboot even if i swipe to accept the configuration or install de SU.zip archive anything happend.
i will appreciate your help, thx!!
kannox said:
hi im having some issues trying to get the SU, i cannot erase the .apk contained in /system/app in order to gain more space.
- i cannot see any folder inside of system folder just one called /system/bin
i really dont know if that really would be the problem because i checked with "df" command and i see everything righ
but when i reboot even if i swipe to accept the configuration or install de SU.zip archive anything happend.
i will appreciate your help, thx!!
Click to expand...
Click to collapse
Sounds like you need to go to [mount] the check the unchecked boxes well at least [system]
sonnettie said:
Sounds like you need to go to [mount] the check the unchecked boxes well at least [system]
Click to expand...
Click to collapse
Done! Thank you all!
free space
please tell me how i free space to root android because it stuck in hawei logo it said you cant delete files tnx lot sorry for my bad english!
Thanks!
Thanks!
Worked on Linux:
Code:
> sudo apt-get install android-tools-fastboot android-tools-adb
> adb reboot bootloader
> sudo fastboot flash recovery TWRP.img
> sudo fastboot boot TWRP.img
Because it's my first post and that's why i'm not able to reply to the original thread in android development Forum i have to ask start a new thread here.
I received my d5503 few days ago and read the [GUIDE] Back up DRM Keys & unlock/relock Bootloader (Noob proof). I was wondering if i can flash instead of, as stated in step 15.Flash D5503_14.2.A.1.114_Generic UK.ftf in flashmode (boot phone in flashmode again) (select Wipe [Uncheck ALL] and Exclude [Check SYSTEM] (link deleted) my OWN original D5503_14.2.A.1.142_Telekom.de DE.ftf which i made today with the files downloaded today with the sony pc Software and flashtool and which is the newer FW? I mean to have my stock Firmware rooted and afterwards backup TA partititions/DRM Keys.
Thanks in advance
I think you can yes. But probably you also need to have a flashable zip of /system from the german rom (see step 19) (see also this: http://forum.xda-developers.com/showpost.php?p=50355068&postcount=34 ).
By the way we will appreciate if you upload the ftf and post it here: http://forum.xda-developers.com/showthread.php?t=2631291 !
zxz0O0 said:
I think you can yes. But probably you also need to have a flashable zip of /system from the german rom (see step 19) (see also this: http://forum.xda-developers.com/showpost.php?p=50355068&postcount=34 ).
By the way we will appreciate if you upload the ftf and post it here: http://forum.xda-developers.com/showthread.php?t=2631291 !
Click to expand...
Click to collapse
yep, after i read the guide again, i thought so too, but this is now the Point where my noobishness takes part. where do i have to type the
adb push busybox /data/local/tmp/
disconnect usb cable
open terminal emulator and do:
cd /data/local/tmp
chmod 755 busybox
./busybox tar pczvf /storage/removable/sdcard1/system.tar.gz /system
now you have full system backup in your external sdcard. Ater rooting, simple do:
cd /
busybox mount -o remount,rw /system
busybox tar xzvf /storage/removable/sdcard1/system.tar.gz
reboot
Click to expand...
Click to collapse
?? in Windows cmd or terminal Emulator on my phone?
ill upload my ftf asap
The first line is in windows cmd (in adb folder). Later on it's in terminal emulator (on the phone) as described. Then you can make a flashable zip of /system and use that in step 19.
And if you flash your own ftf in step 15, check if simlock.ta or preset1.ta is in the file list ("Content" in flashtool). If there is, exclude it.
zxz0O0 said:
The first line is in windows cmd (in adb folder). Later on it's in terminal emulator (on the phone) as described. Then you can make a flashable zip of /system and use that in step 19.
And if you flash your own ftf in step 15, check if simlock.ta or preset1.ta is in the file list ("Content" in flashtool). If there is, exclude it.
Click to expand...
Click to collapse
ok, i think i'll make it. i skipped all .ta files in my .ftf, because in the how to create .ftf guide it was mentioned. so no need to exclude. I'm uploading it at the Moment and post it to the thread you mentioned when upload is finished.
here's the link for the .ftf. hmm, still not able to post links...
another thing i have to ask is, where do i get the busybox from? for the adb push cmd from munjeni`s post?
You can find busybox inside the Z1C-lockeddualrecovery(...)installer.zip you downloaded on step 13
If you want you can pm me the link and I'll post it. I think you need 10 posts.
next problem, next question
if i try to set permissions for the busybox with the chmod cmd, i get a no permission for chmod error on my phone/terminal emulator. Do i have to make this system dump after step 15. of the Back up DRM Keys Guide, or does this method only work for already rooted devices?
Try this (all steps in adb on computer):
adb push busybox /data/local/tmp
adb shell
cd /data/local/tmp
chmod 777 busybox
./busybox tar pczvf /storage/removable/sdcard1/system.tar.gz /system
Copy system.tar.gz from your sdcard to your computer.
So the rooting guide was quiet good, no errors occurred and finaly i got a rooted uk .114 firmware and i coud backup my ta partitition. But, flashing my own or any other .ftf seems to make no sense, without flashing the corresponding system.zip in step 20 ;(.
I tried your adb cmd and it seemed to work in the first moment, but for the lost&found folder there was the error permission denied and in the end there was the following: tar: error exit delayed from previous errors
and theres no system.tar.gz on my external sd.
Any explanations?
Yes I said you also need a flashable zip of /system (see post #2 and #4 of this thread).
I just tested it and I also have the error "tar: error exit delayed from previous errors" but I do have the system.tar.gz on my sdcard.
Did you already flash something? Because then you overwrote /system partiton.
Another method is: extract system.sin with WinRar from the ftf file. Open flashtool => Tools => Sin Editor => Extract data. Then find a program to open ext4 file (e.g. Ext2Read), extract the data and make a flashable zip.
zxz0O0 said:
Another method is: extract system.sin with WinRar from the ftf file. Open flashtool => Tools => Sin Editor => Extract data. Then find a program to open ext4 file (e.g. Ext2Read), extract the data and make a flashable zip.
Click to expand...
Click to collapse
This is exactly what i'm doing atm and then i'm starting from the beginning...
euronaut said:
This is exactly what i'm doing atm and then i'm starting from the beginning...
Click to expand...
Click to collapse
I think if your phone is rooted now it should be enough to continue from step 15 (and use the german ftf and flashable system zip).
after trying a lot of things, i didn't get a flashable zip . i took my sytems folder and meta-inf folder of the uk flashable zip and made my Firmware.zip with winrar, but got always errors during the flashing in dual recovery. after that i tried with the original uk.flashable.zip and everything went well. probably i'm not good in making flashable zips . is there any trick? my flashable zip is 1.5gb in size?!
Open the uk flashable zip with WinRar and delete system.tgz (right click => Delete file). Then rename your system.tar.gz to system.tgz and drag and drop it into the WinRar window.
zxz0O0 said:
Open the uk flashable zip with WinRar and delete system.tgz (right click => Delete file). Then rename your system.tar.gz to system.tgz and drag and drop it into the WinRar window.
Click to expand...
Click to collapse
Finally, everything flashed properly and seemed to work. But now it stucks at the sony logo direct after switching it on . So back to original FW
Did you follow these steps:
Flash your german ftf in flashmode (boot phone in flashmode again) (select Wipe [Uncheck ALL] and Exclude [Check SYSTEM]
Go to the Recovery Menu. To do that, power off your phone. Then power it on again. After the vibrate and the green LED turns on, hold Volume Up (LED will turn violet)
Now format /system (located under Mounts & Storage) (Important: Do NOT reboot until advised so or you will have to start again)
[*]Do a factory reset
Install the following files in this order (Important) (see steps 4 - 6)
flashable german system zip
Z1C-lockeddualrecovery(...)flashable.zip
UPDATE-SuperSU-v1.(...).zip
If you created the system.tar.gz yourself, it's possible that the files don't have the correct permissions. You can try fixing permission in Recovery Menu. Not sure if it really helps. If it doesn't work I advise you to flash the german firmware (+ factory reset) and try these steps again http://forum.xda-developers.com/showpost.php?p=50559502&postcount=9 (you will lose root though).
what i did and how i did was exactly in this order:
1. I flashed my german .142 FTF to have my stock rom back.
2. i extracted a system.tar.gz according to http://forum.xda-developers.com/showpost.php?p=50559502&postcount=9
3. renamed that to system.tgz and did
4.
zxz0O0 said:
Open the uk flashable zip with WinRar and delete system.tgz (right click => Delete file). Then rename your system.tar.gz to system.tgz and drag and drop it into the WinRar window.
Click to expand...
Click to collapse
5. then i followed step 8 - 14 of your guide http://forum.xda-developers.com/showthread.php?t=2642081 with NO errors
and did these steps:
zxz0O0 said:
Did you follow these steps:
Flash your german ftf in flashmode (boot phone in flashmode again) (select Wipe [Uncheck ALL] and Exclude [Check SYSTEM]
Go to the Recovery Menu. To do that, power off your phone. Then power it on again. After the vibrate and the green LED turns on, hold Volume Up (LED will turn violet)
Now format /system (located under Mounts & Storage) (Important: Do NOT reboot until advised so or you will have to start again)
[*]Do a factory reset
Install the following files in this order (Important) (see steps 4 - 6)
flashable german system zip
Z1C-lockeddualrecovery(...)flashable.zip
UPDATE-SuperSU-v1.(...).zip
If you created the system.tar.gz yourself, it's possible that the files don't have the correct permissions. You can try fixing permission in Recovery Menu. Not sure if it really helps. If it doesn't work I advise you to flash the german firmware (+ factory reset) and try these steps again http://forum.xda-developers.com/showpost.php?p=50559502&postcount=9 (you will lose root though).
Click to expand...
Click to collapse
exactly as you described them here
after like doin your guide 5 or 6 times i'm pretty fast with it
now i'm back on my .142 FTF (flashed via flashtool) unrooted
Hm, sorry I don't know what the problem is then. Maybe @Darkimmortal can help you since he created the uk flashable zip I think.
zxz0O0 said:
Try this (all steps in adb on computer):
adb push busybox /data/local/tmp
adb shell
cd /data/local/tmp
chmod 777 busybox
./busybox tar pczvf /storage/removable/sdcard1/system.tar.gz /system
Copy system.tar.gz from your sdcard to your computer.
Click to expand...
Click to collapse
I get an error during this step:
tar: error delayed from previous errors
Click to expand...
Click to collapse
before i got
tar: /System'/lost+found: permission denied
Click to expand...
Click to collapse
Any ideas?
Root your LG G4S (Model H735)
Tested on Andriod 5.1.1.
Thanks goes to @konsolen for sharing the method to open up the port (see appendix in this post) and to @dominik-p for his guide to determine dd parameters (you won't need this to root with the method described, but you can back up your phone if you're worried). And most importantly, thanks to the author of SuperSU for his excellent script updater-binary which worked pretty much out of the box, with only a few workarounds needed (which is what the instructions below do).
First, a few general notes:
The supersu.zip included in this package is version 2.46.
SuperSU can be downloaded here: http://download.chainfire.eu/supersu
If you want to use a new version, just put the zip file in this directory and rename it to "supersu.zip" (delete the old one in this package first of course).
The busybox binary in this package was used successfully to unzip in the LG G4s H735 (Android 5.1.1).
Some time it should maybe be ensured that this is the newest version. Same holds for Send_Command.exe and adb.exe (and attached libraries).
This script uses the "update-binary" script of the SuperSU package to install it on your phone.
The scripts I attached prepare for it to be called (hopefully) successfully.
Instructions to root
Preparation
You MAY want to create a backup of your system beforehand, in case things go wrong.
This is optional, so if you don't want to do this, you may still rely on the .kdz file (see Appendix below) to restore your phone if things go wrong.
You need to calculate the dd parameters and then backup your system partition into a .img file.
There is an excellent guide by @dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
Keep a copy of your system.img somewhere safe, you can use it to restore
your system if something goes wrong.
Enabling developer options and getting the tools
First, enable developer / debugging mode on your phone:
Navigate to Settings > About Phone > scroll to the bottom > tap Build number seven (7) times.
You'll get a short pop-up in the lower area of your display saying that you're now a developer.
Then, go back and now access the Developer options menu, check 'USB debugging' and click OK on the prompt.
Note: You have to enable USB debugging before plugging your device in to the computer. Unplug device then try to enable USB debugging.
On your computer, install Install and Use ADB (the Android Debug Bridge Utility). Also, download LG Flash Tool.
You can find out how to do both by searching google for it.
Step 1.
Connect your phone via USB (not in download mode yet, just normal).
Then, run Init_Root.bat in order to copy the essential files over to internal storage.
You may do this either by 1) double clicking the file, or 2) executing it from the windows command line.
For Option 2): Open a command line in the folder where you extracted this package. To do this, hold shift while right clicking in the folder opened in the Windows Explorer and select "Open command window here". Then, type
Init_Root.bat
Step 2.
Reboot your phone in download mode and ensure it has opened the port to send commands in download mode.
The port is open if it's displayed on the phone's screen in green letters, like
COMX
(with a number instead of X).
On my LG H735 it was necessary to use "LG Flash Tool 2014" http://lgflashtool.com/ to open the port. So if you don't have the green letters, see instruction pasted below (appendix) on how to open the port.
Step 3.
Open a command line in the folder where you extracted this package. To do this, hold shift while
right clicking in the folder opened in the Windows Explorer and select "Open command window here".
Open a command shell to your phone by typing (replace X with the number displayed on your phone) by typing:
Send_Command \\.\COMX
You should be set to root if the following works:
Typing "ls" returns a long list of file and folder names.
Typing "id" should give you someting like that:
uid=0(root) gid=0(root) context=u:r:recovery:s0
The important bits are the "(root)" uid and gid.
If any of the above is not the case, it will not work, you may search for help in the forum.
Step 4.
Execute the commands below (without the numbering of course).
1. mv /data/local/tmp/busybox /sbin/busybox
2. chmod 755 /sbin/busybox
3. mkdir /tmp
4. mkdir /tmp/supersu
5. /sbin/busybox unzip /data/local/tmp/supersu.zip -d /tmp/supersu
6. mv /data/local/tmp/supersu.zip /tmp/supersu/
7. sh /tmp/supersu/META-INF/com/google/android/update-binary dummy 1 /tmp/supersu/supersu.zip
(Note: Not all commands above may be needed, but this is the conservative approach)
Recommended:
Do sanity checks to see if it's doing its job as expected.
After command 2, type the command ls -l /sbin/busybox to check for sanity.
It must return a line like this (with your own date and time):
-rwxr-xr-x shell shell 1048328 <date> <time> busybox
Command 5 must print several lines containing "inflating" messages, similar to this:
Archive:
inflating: META-INF/MANIFEST.MF
...
Command 7 prints lines like this, and other status messages afterwards:
**************
SuperSU installer
**************
...
Step 5.
Your phone should now be rooted if it all worked ok.
You may now type
LEAVE
to reboot your phone.
Happy rooting!
Troubleshooting
If it doesn't work, for example you phone may be stuck on the boot process displaying the LG logo, then you can use Flash Tool to restore your phone. Use instructions below (how to boot the phone into download mode), but don't pull the USB cable, and just let it run its course. This should restore your phone.
If for some reason this hasn't worked, you may try to "dd" back your system .img which you may have created in the preparation step.
Appendix
How to boot the phone into download mode and open the port
a) Boot the LG G4s in download mode. To do this, first switch it off completely and disconnect USB cable. Then, hold the Volume Up button, and while you keep holding it, plug in the USB cable.
b) Start the LG Flash tool and load the .kdz for your phone. We won't actually complete the flashing, you only need it to start the process, but you should use the kdz for your phone nonetheless.
You can check for your kdz on this link, pasting your IMEI instead of YOUR-IMEI in the link below.
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YOUR-IMEI
I did not find any for mine there, but I did find it on
http://devtester.ro/projects/lg-firmwares/
Which brought me to this link where I could find mine:
http://pkg02.azure.gdms.lge.com/dn/downloader.dev?fileKey=FW703UV132GQAUP7A0ED99N/H73510c_00.kdz
c) Now this is very important: Watch your phone while the .kdz is being flashed by the flash tool.
(the flash tool may complain about error connecting to the update server, but you can ignore this with "ok").
As soon as the green letters show up, UNPLUG THE USB CABLE!
The percentage on your phone has to be 0% still (never mind about percentage in the flash tool, it may not even display it).
Then, kill the Flash Tool with the Windows Task Manager (Ctrl+alt+delete).
When it's closed, you can plug your phone back in.
It's now in download mode with open port.
You may also be interested in optimizing your storage & memory after you have rooted:
http://forum.xda-developers.com/general/general/moving-apps-to-sd-optimize-memory-phone-t3248125
LG-H731 Vigor from Videotron/Virgin Mobile
jen.magnolis said:
Root your LG G4S (Model H735)
Tested on Andriod 5.1.1.
Click to expand...
Click to collapse
Also work on phone listed in title:
LG-H731 (LG G4) Vigor from Videotron/Virgin Mobile
Happy rooting
If you need help, don't hesitate to contact me: [email protected] or here =
Hi
jen.magnolis said:
Root your LG G4S (Model H735)
Tested on Andriod 5.1.1.
Thanks goes to @konsolen for sharing the method to open up the port (see appendix in this post) and to @dominik-p for his guide to determine dd parameters (you won't need this to root with the method described, but you can back up your phone if you're worried). And most importantly, thanks to the author of SuperSU for his excellent script updater-binary which worked pretty much out of the box, with only a few workarounds needed (which is what the instructions below do).
First, a few general notes:
The supersu.zip included in this package is version 2.46.
SuperSU can be downloaded here: http://download.chainfire.eu/supersu
If you want to use a new version, just put the zip file in this directory and rename it to "supersu.zip" (delete the old one in this package first of course).
The busybox binary in this package was used successfully to unzip in the LG G4s H735 (Android 5.1.1).
Some time it should maybe be ensured that this is the newest version. Same holds for Send_Command.exe and adb.exe (and attached libraries).
This script uses the "update-binary" script of the SuperSU package to install it on your phone.
The scripts I attached prepare for it to be called (hopefully) successfully.
Instructions to root
Preparation
You MAY want to create a backup of your system beforehand, in case things go wrong.
This is optional, so if you don't want to do this, you may still rely on the .kdz file (see Appendix below) to restore your phone if things go wrong.
You need to calculate the dd parameters and then backup your system partition into a .img file.
There is an excellent guide by @dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
Keep a copy of your system.img somewhere safe, you can use it to restore
your system if something goes wrong.
Step 1.
Connect your phone via USB (not in download mode yet, just normal).
Then, run Init_Root.bat in order to copy the essential files over to internal storage.
You may do this either by 1) double clicking the file, or 2) executing it from the windows command line.
For Option 2): Open a command line in the folder where you extracted this package. To do this, hold shift while right clicking in the folder opened in the Windows Explorer and select "Open command window here". Then, type
Init_Root.bat
Step 2.
Reboot your phone in download mode and ensure it has opened the port to send commands in download mode.
The port is open if it's displayed on the phone's screen in green letters, like
COMX
(with a number instead of X).
On my LG H735 it was necessary to use "LG Flash Tool 2014" http://lgflashtool.com/ to open the port. So if you don't have the green letters, see instruction pasted below (appendix) on how to open the port.
Step 3.
Open a command line in the folder where you extracted this package. To do this, hold shift while
right clicking in the folder opened in the Windows Explorer and select "Open command window here".
Open a command shell to your phone by typing (replace X with the number displayed on your phone) by typing:
Send_Command \\.\COMX
You should be set to root if the following works:
Typing "ls" returns a long list of file and folder names.
Typing "id" should give you someting like that:
uid=0(root) gid=0(root) context=u:r:recovery:s0
The important bits are the "(root)" uid and gid.
If any of the above is not the case, it will not work, you may search for help in the forum.
Step 4.
Now you have two options:
#Step 4, Option 1 (recommended to try)
Just run the script and you should be done.
Type:
sh root_lgh735.sh
The script contains all commands I (and other people) used to successfully root the phone.
However we have all used option (2) below, so the script itself has not been tested yet,
though it's very simple (feel free to open it with a text editor to look at it).
You can try to run it, and if it's not doing what's expected you can still go to Option 2
and fix things up.
It will have worked if:
It prints several lines containing "inflating" messages, similar to this:
Archive:
inflating: META-INF/MANIFEST.MF
...
It prints 3 lines like this, and other status messages afterwards:
**************
SuperSU installer
**************
....
If it has done that, reboot your phone and you should be set.
If not, do the commands manually as in Option 2.
Please: If the script worked for you, report it in this thread, so I can simplify these instructions here! Thanks for your help :cyclops:
#Step 4, Option 2:
Execute the commands directly (proven to work on several phones).
Type the commands below (without the numbering of course).
1. mv /data/local/tmp/busybox /sbin/busybox
2. chmod 755 /sbin/busybox
3. mkdir /tmp
4. mkdir /tmp/supersu
5. /sbin/busybox unzip /data/local/tmp/supersu.zip -d /tmp/supersu
6. mv /data/local/tmp/supersu.zip /tmp/supersu/
7. sh /tmp/supersu/META-INF/com/google/android/update-binary dummy 1 /tmp/supersu/supersu.zip
(Note: Not all commands above may be needed, but this is the conservative approach)
Recommended:
Do sanity checks to see if it's doing its job as expected.
After command 2, type the command ls -l /sbin/busybox to check for sanity.
It must return a line like this (with your own date and time):
-rwxr-xr-x shell shell 1048328 <date> <time> busybox
Command 5 must print several lines containing "inflating" messages, similar to this:
Archive:
inflating: META-INF/MANIFEST.MF
...
Command 7 prints lines like this, and other status messages afterwards:
**************
SuperSU installer
**************
...
Step 5.
Your phone should now be rooted if it all worked ok.
You may now type
LEAVE
to reboot your phone.
Happy rooting!
Troubleshooting
If it doesn't work, for example you phone may be stuck on the boot process displaying the LG logo, then you can use Flash Tool to restore your phone. Use instructions below (how to boot the phone into download mode), but don't pull the USB cable, and just let it run its course. This should restore your phone.
If for some reason this hasn't worked, you may try to "dd" back your system .img which you may have created in the preparation step.
Appendix
How to boot the phone into download mode and open the port
a) Boot the LG G4s in download mode. To do this, first switch it off completely and disconnect USB cable. Then, hold the Volume Up button, and while you keep holding it, plug in the USB cable.
b) Start the LG Flash tool and load the .kdz for your phone. We won't actually complete the flashing, you only need it to start the process, but you should use the kdz for your phone nonetheless.
You can check for your kdz on this link, pasting your IMEI instead of YOUR-IMEI in the link below.
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YOUR-IMEI
I did not find any for mine there, but I did find it on
http://devtester.ro/projects/lg-firmwares/
Which brought me to this link where I could find mine:
http://pkg02.azure.gdms.lge.com/dn/downloader.dev?fileKey=FW703UV132GQAUP7A0ED99N/H73510c_00.kdz
c) Now this is very important: Watch your phone while the .kdz is being flashed by the flash tool.
(the flash tool may complain about error connecting to the update server, but you can ignore this with "ok").
As soon as the green letters show up, UNPLUG THE USB CABLE!
The percentage on your phone has to be 0% still (never mind about percentage in the flash tool, it may not even display it).
Then, kill the Flash Tool with the Windows Task Manager (Ctrl+alt+delete).
When it's closed, you can plug your phone back in.
It's now in download mode with open port.
Click to expand...
Click to collapse
Have twpr or cwm recovery to install xposed??
I can confirm is working on LG G4 LG-H735P (Latin America version), thanks!
anyone tried updating? just got a system update notification from my phone lol dk if i should update now or not
Good question! I didn't try it yet. Think it should be ok, but if it isn't, you can just root again I guess
jen.magnolis said:
Good question! I didn't try it yet. Think it should be ok, but if it isn't, you can just root again I guess
Click to expand...
Click to collapse
oh.. it wont like brick or anything? :/
dclarkg said:
I can confirm is working on LG G4 LG-H735P (Latin America version), thanks!
Click to expand...
Click to collapse
I could not root my phone, what kdz file did you use??
Backup problems
Hello,
Coming from a Nexus 4, I bought a G4S last month.
I want to do my first root in order to manage the storage, like jen.magnolis talked about.
In case of a problem (bootloop or brick), I need to be able to restore. I don't really mind about restoring my datas, a factory reset would be enough.
But I don't undestand how i can get the system.img without being rooted ? It seems that I can get a "backup.ab" file using adb. Will it be enough to restore in case of brick ?
I also looked about kdz files, but mine doesn't seem to be available. I have a LGH735 (buyer = FRA, suffix = AFRATS, ...). Will it work if I use the one you provided in your post ?
Thanks for your help !
dclarkg said:
I can confirm is working on LG G4 LG-H735P (Latin America version), thanks!
Click to expand...
Click to collapse
I got the same model phone, but I can't find the .KDZ file for it anywhere. Could you post a link to the one you used please?
Excellent step-by-step guide. Should set an example for other "step-by-step guides" which exclude crucial information ("everybody knows lösfhgaeilurhg has to by typed between these steps here, I shall not mention it" )
Thanks a ton Worked on my LG G4S a.k.a H735 like a charm.
Cheers!
dreamnoob said:
anyone tried updating? just got a system update notification from my phone lol dk if i should update now or not
Click to expand...
Click to collapse
jen.magnolis said:
Good question! I didn't try it yet. Think it should be ok, but if it isn't, you can just root again I guess
Click to expand...
Click to collapse
"phone appears to be rooted, will not be updated" - Hiding root did not help, any simple suggestions but total unrooting?
Wanted to upgrade from 10c to 10d...
Cheers!
Doubts.
Hi everyone!
I just cant find my .kdz file! The phone i want to root its a G4 H735AR, im wondering if there are some compatible .kdz that i can use. Im affraid it might get bricked or something...
BTW i¨ve tried the rootworm.bat method and it didnt work. And when i try to open the COMX port, the lg flash tool always crushes and shuts down.
Works!
ascfzz said:
Hi everyone!
I just cant find my .kdz file! The phone i want to root its a G4 H735AR, im wondering if there are some compatible .kdz that i can use. Im affraid it might get bricked or something...
BTW i¨ve tried the rootworm.bat method and it didnt work. And when i try to open the COMX port, the lg flash tool always crushes and shuts down.
Click to expand...
Click to collapse
So, i made it! It works in the H735AR!! The problem with the flash tool was that i was trying to use it without any KDZ file!! I've used @konsolen .kdz and achieved to open ports, and then continue with the rest of the tutorial without trouble.
Thank you so much! Its a great phone, but with so little internal memory is a waste.
chw9999 said:
"phone appears to be rooted, will not be updated" - Hiding root did not help, any simple suggestions but total unrooting?
Wanted to upgrade from 10c to 10d...
Cheers!
Click to expand...
Click to collapse
ya u just update thru lg bridge.. once updated it will be unroot tho so u have to root it back same method as u did before.. and if you use link2sd it dosent matter after root ur link2sd can just reboot and re-read ur partition without needing to wipe and re-partition
It's working in H736P! Thank you só much!
Enviado de meu LG-H736 usando Tapatalk
For people in Brazil that has H736P, to open ports, is necessary the kdz file to use in LG Flash Tool.
Galera do Brasil, consegui rootear o LG G4 Beat usando esse tutorial porém tive que baixar o arquivo kdz pro H736P pra executar o LG Flash Tool. Cuidado ao usar o LG Flash Tool, assim que aparecer a porta COM na tela do telefone, arranca o cabo USB do computador.
Enviado de meu LG-H736 usando Tapatalk
friend you are from argentina?¿
maxiret said:
friend you are from argentina?¿
Click to expand...
Click to collapse
Brasil.
Enviado de meu LG-H736 usando Tapatalk