Related
Ok,
Let me summarize the status of the rooting for the Wildfire because there are some things I don't understand. Please correct me if I'm wrong...
1. HBOOT is able to upgrade all system even the HBOOT itself by: (1) checking the signature of the update file present in the SD card, (2) unprotecting the flash and (3) do the actual flashing
2. We have a temproot working in Android thanks to the exploit of Gingerbreak.
So in this case, the root user can insert a kernel module with the insmod command and execute code with system privileges. That means that this code being executed in the kernel can do exactly the same as the HBOOT code. So it can unprotect the flash and flash it.
Of course, to do that we need some information on how HBOOT is doing it. I will even say that we only need the memory map of the board and the datasheet of the flash chip with detailed commands to unprotect the sectors. I'm sure this information is out there, because usually the flash manufacturer is handling this information public on their web site.
Is all of this correct?? Or am I missing something...?
Just an update:
I managed to compile and insert a kernel module with insmod, so I can confirm that code can be executed with system privileges.
The system io map is this:
02d00000-02d9afff : msm_panel.0
02d9b000-02dbafff : ram_console
02e00000-0fffffff : System RAM
02e28000-03234fff : Kernel text
03254000-033b271b : Kernel data
20000000-26ffffff : System RAM
a0200000-a0200fff : msm_serial_hs_bcm.0
a0400000-a0400fff : msm_sdcc.1
a0500000-a0500fff : msm_sdcc.2
a0800000-a0801000 : msm_hsusb
a9900000-a9900fff : msm_i2c.0
a9900000-a9900fff : msm_i2c
a9c00000-a9c00fff : msm_serial.2
a9c00000-a9c00fff : msm_serial
aa200000-aa2effff : mdp
aa600000-aa600fff : msm_mddi.0
We need now the correct memory addresses to write and unprotect the flash. I'll keep on researching...
Dude
If you don't feel supported or anything because it looks like everybody is ignoring you: it is just because nobody understands what you are saying Or I at least don't.
But if you feel like you are getting somewhere with this in rooting, know that you have the support of the whole wildfire 1.01 hboot community!
Erwin
Yet another unneeded thread ^^, joke, keep on researching..
Sent from my HTC Wildfire using Tapatalk
ErwinP said:
Dude
If you don't feel supported or anything because it looks like everybody is ignoring you: it is just because nobody understands what you are saying Or I at least don't.
But if you feel like you are getting somewhere with this in rooting, know that you have the support of the whole wildfire 1.01 hboot community!
Erwin
Click to expand...
Click to collapse
Yes exactly. It is complicated to me as well. Maybe it is understood only by programmers.
But if u can tell little more basics, i believe everyone attempts to help u .
Maybe also regarding insmod command.
---And i think gingerbreak exploit is not working on wildfire. I tried gingerbreak.apk which tells that phone will be rebooted on success. But upon reboot maybe the changes will be reverted giving nothing. And even tried latest super one click with the gingerbreak exploit, but not succeeded.
---And psneuter works on wildfire but gives only a shell root. And even when we attempt to copy something to the system partition, it gives "out of memory" error and mostly reboots upon remounting as read/write.
those apps will only give temp root ...
bharatgaddameedi said:
Yes exactly. It is complicated to me as well. Maybe it is understood only by programmers.
But if u can tell little more basics, i believe everyone attempts to help u .
Maybe also regarding insmod command.
---And i think gingerbreak exploit is not working on wildfire. I tried gingerbreak.apk which tells that phone will be rebooted on success. But upon reboot maybe the changes will be reverted giving nothing. And even tried latest super one click with the gingerbreak exploit, but not succeeded.
---And psneuter works on wildfire but gives only a shell root. And even when we attempt to copy something to the system partition, it gives "out of memory" error and mostly reboots upon remounting as read/write.
Click to expand...
Click to collapse
Buldog said:
those apps will only give temp root ...
Click to expand...
Click to collapse
And pls specify temp root.
Was it the accessing root over adb. And was it having writable permissions to system partitions atleast from adb.
I think writing to system partition is not yet successful on wildfire hboot 1.01
Sent from my HTC Wildfire using XDA App
temp root allows to do some things via adb.
you re not able to write to the system because its nand protected - s on
bharatgaddameedi said:
And pls specify temp root.
Was it the accessing root over adb. And was it having writable permissions to system partitions atleast from adb.
I think writing to system partition is not yet successful on wildfire hboot 1.01
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Buldog said:
temp root allows to do some things via adb.
you re not able to write to the system because its nand protected - s on
Click to expand...
Click to collapse
Is that nand protection restricts the write access to system partition through shell root on hboot 1.01 only.
Or will it restrict the write access to system folders through shell root on hboot 0.80 as well. Will it have the same "out of memory" error.
Sent from my HTC Wildfire using XDA App
Well, mabe this thread should be in wildfire devloppement forum instead of general.
Sent from my HTC Wildfire using XDA App
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
Hey all in UK as ever
Finally my Arc has been updated to the above OS
Came as a complete shock to me as I was going to start looking round for a diff phone but now am on ICS am happier
Slight problem
Previously I had Superuser App and Titanium backup installed and removed the bloatware from my service provider. I tried doing this again once the update was completed but Titanium says it cannot get root access and Superuser is not listing it at all and I cannot add it.
Please help
Have you read the relevant 587 rooting threads, as you've obviously lost root access during the update.
Sent from Myushi
XperienceD said:
Have you read the relevant 587 rooting threads, as you've obviously lost root access during the update.
Sent from Myushi
Click to expand...
Click to collapse
Yeh that looks like what has happened
Just tried rooting again and it failed Titanium will not get root access
Nath316 said:
Yeh that looks like what has happened
Just tried rooting again and it failed Titanium will not get root access
Click to expand...
Click to collapse
You've obviously missed a step then, re read whatever guide to root you've used and try again.
You got arc (lt15i)
Just testpoint, boot a kernel, install root with cwm
Sent from my LT15i using xda premium
XperienceD said:
You've obviously missed a step then, re read whatever guide to root you've used and try again.
Click to expand...
Click to collapse
Well it looks like the Doomlord thing failed
busybox: /system/xbin/zcip: Read-only file system
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only file system
--- cleaning
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
--- rebooting
ALL DONE!!!
Click to expand...
Click to collapse
I followed each step
Hi Nath,
If you tried to root with Doomlords root toolkit try using DooMLoRD_v1_Xperia-2011-ICS-ROOT-emu-busybox-su instead found here, near the bottom of first post...
http://forum.xda-developers.com/showthread.php?t=1601038
I struggled for a while but this worked first time..
good luck and stick with it..
Onmehedson said:
Hi Nath,
If you tried to root with Doomlords root toolkit try using DooMLoRD_v1_Xperia-2011-ICS-ROOT-emu-busybox-su instead found here, near the bottom of first post...
http://forum.xda-developers.com/showthread.php?t=1601038
I struggled for a while but this worked first time..
good luck and stick with it..
Click to expand...
Click to collapse
thanks for pointing out but this failed also with a read only system error.
suspect it is the carrier
I`m just a novice at this game but I dont see how the carrier could affect root as you flash generic .587 firmware to begin with...
Have a look at this great video and follow it point by point but use the alternative root kit than the one shown, although I didnt run programmes from command prompt like he suggests..
http://www.youtube.com/watch?v=Rjv71b9QcZE
Sorry if you have already seen it.
Keep trying , you`ll get there in the end..
Onmehedson said:
I`m just a novice at this game but I dont see how the carrier could affect root as you flash generic .587 firmware to begin with...
Have a look at this great video and follow it point by point but use the alternative root kit than the one shown, although I didnt run programmes from command prompt like he suggests..
http://www.youtube.com/watch?v=Rjv71b9QcZE
Sorry if you have already seen it.
Keep trying , you`ll get there in the end..
Click to expand...
Click to collapse
Interesting post here saying that 587 cannot be rooted
http://forum.xda-developers.com/showthread.php?t=2105325
May explain why i am having issues
Quite right , .587 cannot be rooted directly. You have to downgrade by flashing an earlier version kernel.
So its...Flash .587 firmware - FLASH .562 KERNEL ONLY - root with DooMLoRD_v1_Xperia-2011-ICS-ROOT-emu-busybox-su - flash original .587 kernel..
Watch the video , all is explained within it ...
SuperUser Fixed
Nath316 said:
Hey all in UK as ever
Finally my Arc has been updated to the above OS
Came as a complete shock to me as I was going to start looking round for a diff phone but now am on ICS am happier
Slight problem
Previously I had Superuser App and Titanium backup installed and removed the bloatware from my service provider. I tried doing this again once the update was completed but Titanium says it cannot get root access and Superuser is not listing it at all and I cannot add it.
Please help
Click to expand...
Click to collapse
Hi I got it fixed by flashing SuperSU, update it, then go into settings of SuperSU and Install , then look for Swotch to SuperUser, it un install itself, then go to SuperUser and update...
All done
Hi all,
I'm the lucky owner of a ZTE Open and i'd like to share with you the process i used to root and install recovery.
Disclaimer: This process is very risky, you may brick your phone permanently, so neither xda nor me could be responsible of the resulting consequences.
Note: I did not dev or contribute to any program/process listed there, all credits are going to the listed sources.
I followed successfuly this processus with Debian 7 (32b) and a UK version of the ZTE Open.
1 - Get Root Access
Pre-requisite:
1/Install adb
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
2/Update your udev rules for adb to recogize your phone:
Code:
#create a file with your udev rules
nano /etc/udev/rules.d/60-fxos
Copy the following in your newly created file:
SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", ATTR{idProduct}=="1350", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d00d", MODE="0666", GROUP="plugdev"
Click to expand...
Click to collapse
Then:
Code:
#update permissions of the 60-fxos file
chmod 644 /etc/udev/rules.d/60-fxos
#Restart udev
sudo service udev restart
On this step my advice is to restart your computer to restart properly adb and to remap udev.
Root exploit:
1/Enable "Remote debugging" on your phone
On your device, in Settings -> Device information -> More Information -> Developer.
Disable
2/Check that your devuce is recognised
Code:
# adb devices
List of devices attached
roamer2 device
Roamer2 is the name of the ZTE Open
3/Root
Download file root-zte-open.zip (see download section below)
uzip its content and put it in your working folder (~/fos/root/ in this example)
Code:
#go to your working folder
cd ~/fos/root/
#update permissions of the root-zte-open file (you probably need admin right to do this)
chmod 755 root-zte-open
#launch exploit AS ROOT USER
./run.sh
The output should be the following:
Code:
# ./run.sh
Connect your phone to USB, then:
Settings -> Device information -> More Information -> Developer
and enable 'Remote debugging'
1142 KB/s (19208 bytes in 0.016s)
== root for Movistar zte open (roamer2) by [user=240671]@pof[/user]
== CVE-2012-4220 - discovered by giantpune
== original exploit by Hiroyuki Ikezoe
== if the phone hangs, remove the battery and try again!
roamer2 (OPEN_EU_DEV_FFOS_V1.0.0B01) is not supported.
Attempting to detect from /proc/kallsyms...
roamer2 (OPEN_EU_DEV_FFOS_V1.0.0B01) is not supported.[diag]
Attempting to inject code...
This works only once a boot.
roamer2 (OPEN_EU_DEV_FFOS_V1.0.0B01) is not supported.[diag]
Attempting to inject code...
This works only once a boot.
failed to get root access
Exploit failed, rebooting and trying again!
[...few more fail attempts, 3 in my case]
== root for Movistar zte open (roamer2) by [user=240671]@pof[/user]
== CVE-2012-4220 - discovered by giantpune
== original exploit by Hiroyuki Ikezoe
== if the phone hangs, remove the battery and try again!
roamer2 (OPEN_EU_DEV_FFOS_V1.0.0B01) is not supported.
Attempting to detect from /proc/kallsyms...
roamer2 (OPEN_EU_DEV_FFOS_V1.0.0B01) is not supported.[diag]
Attempting to inject code...
This works only once a boot.
roamer2 (OPEN_EU_DEV_FFOS_V1.0.0B01) is not supported.[diag]
Attempting to inject code...
This works only once a boot.
Got root! - copying su binary!
Enjoy!
You are now rooted.
Note: my few first attempts failed, i tried few time (restarting all the process) to achieve it successfully.
2 - Install Recovery
1 - Download recovery
In the download section you will find the download link to clockwork recovery 6.0.3.3.
Put the recovery .zip in your working folder.
Navigate into the working foder.
2 - Backup your current stock recovery
If not already done turn on debugging on phone and turn off USB mass storage on phone.
Plug phone in to computer.
Code:
#Launch adb shell
adb shell
#get root access
su
#Backup the stock recovery
busybox dd if=/dev/mtd/mtd0 of=/mnt/sdcard/stock-recovery.img bs=4k
exit
2 - Backup your current stock recovery
Code:
#Push the CW Recovery to your phone
adb push recovery-clockwork-6.0.3.3-roamer2.img /mnt/sdcard/cwm.img
adb shell
[email protected]:/ $ su
[email protected]:/ # flash_image recovery /mnt/sdcard/cwm.img
In my case the output of the las command was:
[email protected]:/ # flash_image recovery /mnt/sdcard/cwm.img
mtd: successfully wrote block at 0
mtd: successfully wrote block at 20000
mtd: successfully wrote block at 40000
mtd: successfully wrote block at 60000
mtd: successfully wrote block at 80000
mtd: successfully wrote block at a0000
mtd: successfully wrote block at c0000
mtd: successfully wrote block at e0000
mtd: successfully wrote block at 100000
mtd: successfully wrote block at 120000
mtd: successfully wrote block at 140000
mtd: successfully wrote block at 160000
mtd: successfully wrote block at 180000
mtd: successfully wrote block at 1a0000
mtd: successfully wrote block at 1c0000
mtd: successfully wrote block at 1e0000
mtd: successfully wrote block at 200000
mtd: successfully wrote block at 220000
mtd: successfully wrote block at 240000
mtd: successfully wrote block at 260000
mtd: successfully wrote block at 280000
mtd: successfully wrote block at 2a0000
mtd: successfully wrote block at 2c0000
mtd: successfully wrote block at 2e0000
mtd: successfully wrote block at 300000
mtd: successfully wrote block at 320000
mtd: successfully wrote block at 340000
mtd: successfully wrote block at 360000
mtd: successfully wrote block at 380000
mtd: successfully wrote block at 3a0000
mtd: successfully wrote block at 3c0000
mtd: successfully wrote block at 3e0000
mtd: successfully wrote block at 400000
mtd: successfully wrote block at 420000
mtd: successfully wrote block at 440000
mtd: successfully wrote block at 460000
mtd: successfully wrote block at 480000
mtd: successfully wrote block at 4a0000
mtd: successfully wrote block at 4c0000
mtd: successfully wrote block at 4e0000
mtd: successfully wrote block at 500000
mtd: successfully wrote block at 520000
mtd: successfully wrote block at 540000
mtd: successfully wrote block at 560000
mtd: successfully wrote block at 580000
mtd: successfully wrote block at 0
Click to expand...
Click to collapse
3 - Restart your phone in recovery mode
Power off your phone.
Hold both volume down up and the power button.
What now?
Now in the recovery you can install custom roms.
For example, you can flash the movistar rom (see dowload section).
Flash zip in recovery as you would do for any android rom.
Troubleshooting
"status 7" error installing or updating
This happend to me after installing the spanish rom on my Ebay ZTE (UK). it seems to me that it changed the name of the device from roamer2 to full_inari and cause the updater-script to crash.
Solution found in this topic: http://forum.xda-developers.com/showthread.php?t=2302599
Opened the update.zip file, in the folder META_INF > COM > GOOGLE > ANDROID, edit updater-script and remove the following lines :
Code:
assert(getprop("ro.product.device") == "roamer2" ||
getprop("ro.build.product") == "roamer2");
assert(getprop_new("ro.build.display.id") == "OPEN_EU_DEV_FFOS");
Save modified zip and try to install again whith CWM.
Dowloads:
root-zte-open.zip
recovery-clockwork-6.0.3.3-roamer2.img
Movistar - OPEN_FFOS_V1.0.0B04_TME
EU_DEV_FFOS_V1.0.0B02_USER_SD2.zip (official rom from ZTE for the UK version)
Many many thanks to my sources:
http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
https://groups.google.com/forum/#!msg/mozilla.dev.b2g/dvXr_Us0HHc/E9U87zK-lUMJ
cimourdain said:
...
What now?
Now in the recovery you can install custom roms.
For example, you can flash the movistar rom (see dowload section).
Flash zip in recovery as you would do for any android rom.
....
Click to expand...
Click to collapse
Give it Custom Roms???For the ZTE Open....
azureus77 said:
Give it Custom Roms???For the ZTE Open....
Click to expand...
Click to collapse
Did not found that much for the moment :-') I'm investigating the way to install 1.1
Envoyé depuis mon GT-I9100 avec Tapatalk
cimourdain said:
Did not found that much for the moment :-') I'm investigating the way to install 1.1
Envoyé depuis mon GT-I9100 avec Tapatalk
Click to expand...
Click to collapse
Any ROM with android and firefox OS for dual boot, i need use whatsapp and others app...
BR
NEOCRIVI said:
Any ROM with android and firefox OS for dual boot, i need use whatsapp and others app...
BR
Click to expand...
Click to collapse
for whatsapp go to connacta2.im
it is WA for FFOS
need a bit of help
i'm kinda new here and i've updated my zte open to firefox os 1.1. i was wondering if there is a way to root it now that i have the new version of firefox os? i searched on google and didn't find anything.
gabyslim said:
i'm kinda new here and i've updated my zte open to firefox os 1.1. i was wondering if there is a way to root it now that i have the new version of firefox os? i searched on google and didn't find anything.
Click to expand...
Click to collapse
Hi, if you did the above, you already rooted your phone. Or was it a normal update, not for the UK version I suppose. For now I did the SD-update to OPEN_EU_DEV_FFOS_V1.0.0B02, from ZTE Suport (cannot link...yet).
I hope to reach your level with all my hair in place! Then what, dual-boot with 512mbROM?
ovasilis74 said:
Hi, if you did the above, you already rooted your phone. Or was it a normal update, not for the UK version I suppose. For now I did the SD-update to OPEN_EU_DEV_FFOS_V1.0.0B02, from ZTE Suport (cannot link...yet).
I hope to reach your level with all my hair in place! Then what, dual-boot with 512mbROM?
Click to expand...
Click to collapse
i have the update coming from firefox i guess. i bought my zte open in spain from movistar with prepay sim.
azureus77 said:
Give it Custom Roms???For the ZTE Open....
Click to expand...
Click to collapse
gabyslim said:
i'm kinda new here and i've updated my zte open to firefox os 1.1. i was wondering if there is a way to root it now that i have the new version of firefox os? i searched on google and didn't find anything.
Click to expand...
Click to collapse
gabyslim said:
i have the update coming from firefox i guess. i bought my zte open in spain from movistar with prepay sim.
Click to expand...
Click to collapse
Gabyslim, the working enviroment of this guide by cimourdain is Debian7 (Linux operating system). Ubuntu Linux listens to the same comands in the CLI ("comand line interface" I think), I use Xubuntu12.04LTS (12.04 seems to be the most suitable for android playing) for the same modification on my ZTEopenEU(UKeBay). So if your PC runs only Windows, you have to use almost the same android-tools to take root control of your device, (like ADB=Android Debug Bridge), but follow another guide for Windows, also in CLI i suppose, not sure...
Now, if you are sure you have 1.1 rather than 1.0.1.0...etc in a ZTEopen, it 's a very usefull information for me, azureus77, cimourdain and many others probably! I tried to find Movistar support, to see if they uploaded any Fos1.1 in .zip format for manual update, but didn 't have any succes until now and my Espanol understanding is very poor to search further... I could install it on my ZTEopenUK even if I am using english language on my phone (no Greek option in 1.0.1.0), because I think that 1.1 gives many lang-options.
So, Gabyslim, if you 'd like to help a little, please check the lang-options on your phone and the excact version if you like, mine is this:
(I can 't post links yet, fill the rest...)
.4shared.com/photo/KzDRva8i/2013-11-03-08-12-58.html
.4shared.com/photo/LzTHsKji/2013-11-03-08-13-52.html
If you could find-out if Movistar has uploaded any .zip update and post a link, would be a nice gift!
BTW, very good price. I paid double € from the UKeBay(ZTE..."official")...
---------- Post added at 10:01 AM ---------- Previous post was at 09:08 AM ----------
cimourdain said:
Did not found that much for the moment :-') I'm investigating the way to install 1.1
Envoyé depuis mon GT-I9100 avec Tapatalk
Click to expand...
Click to collapse
Thanks again cimourdain
I couldn 't use this link
dl.free.fr/f4t178wBA"]Movistar - OPEN_FFOS_V1.0.0B04_TME
is there any other way to have this file?
Also, do you know if this solves the "downloading update error"?
ovasilis74 said:
Gabyslim, the working enviroment of this guide by cimourdain is Debian7 (Linux operating system). Ubuntu Linux listens to the same comands in the CLI ("comand line interface" I think), I use Xubuntu12.04LTS (12.04 seems to be the most suitable for android playing) for the same modification on my ZTEopenEU(UKeBay). So if your PC runs only Windows, you have to use almost the same android-tools to take root control of your device, (like ADB=Android Debug Bridge), but follow another guide for Windows, also in CLI i suppose, not sure...
Now, if you are sure you have 1.1 rather than 1.0.1.0...etc in a ZTEopen, it 's a very usefull information for me, azureus77, cimourdain and many others probably! I tried to find Movistar support, to see if they uploaded any Fos1.1 in .zip format for manual update, but didn 't have any succes until now and my Espanol understanding is very poor to search further... I could install it on my ZTEopenUK even if I am using english language on my phone (no Greek option in 1.0.1.0), because I think that 1.1 gives many lang-options.
So, Gabyslim, if you 'd like to help a little, please check the lang-options on your phone and the excact version if you like, mine is this:
(I can 't post links yet, fill the rest...)
.4shared.com/photo/KzDRva8i/2013-11-03-08-12-58.html
.4shared.com/photo/LzTHsKji/2013-11-03-08-13-52.html
If you could find-out if Movistar has uploaded any .zip update and post a link, would be a nice gift!
BTW, very good price. I paid double € from the UKeBay(ZTE..."official")...
---------- Post added at 10:01 AM ---------- Previous post was at 09:08 AM ----------
Thanks again cimourdain
I couldn 't use this link
dl.free.fr/f4t178wBA"]Movistar - OPEN_FFOS_V1.0.0B04_TME
is there any other way to have this file?
Also, do you know if this solves the "downloading update error"?
Click to expand...
Click to collapse
the version i have installed now is OPEN_FFOS_V1.1.0B01_TME and i was updated from ffos 1.0 to this version on 26/09/2013.
gabyslim said:
the version i have installed now is OPEN_FFOS_V1.1.0B01_TME and i was updated from ffos 1.0 to this version on 26/09/2013.
Click to expand...
Click to collapse
Very good you realy have the 1.1 ! Have you the .zip file of OPEN_FFOS_V1.1.0B01_TME ? Could you attach it here or upload it somewhere easy for us to dowload? With the link cimourdain gave about "status 7" error installing or updating, I wouldn't think much flashing my ZTE too!
Version 1.1 here: download.ztedevices.com/UpLoadFiles/product/550/3363/soft/2013110810201108.zip
pcc00 said:
Version 1.1 here: download.ztedevices.com/UpLoadFiles/product/550/3363/soft/2013110810201108.zip
Click to expand...
Click to collapse
Many thanks pcc00! I 'll post results on ZTEOpen as soon I flash it.
Well, I succefully flashed fos1.1, worked OK, but then I found a "reason" to brick the poor device...
I belive I'm not off-topic because I think the Movistar1.1 flashed the ClockworkRecovery also, so I ended with a StockRecoveryMode, that was also inaccesible from adb with my Xubuntu12.04.
I tried to root the ZTEOpen and install ClockworkRecovery again, but both failled... endless reboots after ./run.sh
From the StockRecoveryMode I tried to "apply update from external stor(age)" with:
EU_DEV_FFOS_V1.0.0B02_USER_SD.zip
images-keon-v1.2-2013-11-04.Gecko-9082581.Gaia-f18e209.zip
B2G_P752D04V1.1.0B04_TME(SD).zip
all gave verification errors, also with and without the fix for "status 7 error".
Then i flashed:
Update package of Android GB for OPEN device
from: firefox.ztems.com (search site, cannot link).
The installation was completed, but after that I did something I didn't expect to end like this: I selected "reboot" but in the next screen (asking reboot or not) I selected NOT to reboot, so I review the previous menu again, BUT the device rebooted anyway! I don't realy know if this caused the final problem.
That's the end of the story for now, the "semi-brick-zte" boots either in "Android system recovery <3a>" (volume-up + power-button) or if I select "reboot system now" endless reboots with the fox looking something to the right of the screen...
I'll try to find how "flashboot" works, for now it does not see the device (recovery only).
Any sugestions/guides?
...last working state...
Stock recovery
I did not bakcup stock recovery and I am not able to upgrade to OPEN_EU_DEV_FFOS_V1.0.0B02 using clockwork recovery that I installed.
Could anyone share a copy of the original stock recovery image?
Hello.
I try to achieve root with OPEN_US_DEV_FFOS_V1.0.0B02 installed.
But the process always stops on "This works only once a boot."
And then phone just reboots and script failes, like this one:
Code:
== root for Movistar zte open (roamer2) by @pof
== CVE-2012-4220 - discovered by giantpune
== original exploit by Hiroyuki Ikezoe
== if the phone hangs, remove the battery and try again!
roamer2 (OPEN_US_DEV_FFOS_V1.0.0B02) is not supported.
Attempting to detect from /proc/kallsyms...
roamer2 (OPEN_US_DEV_FFOS_V1.0.0B02) is not supported.[diag]
Attempting to inject code...
This works only once a boot.
D:\Software\Google Nexus 4 ToolKit>
I would appreciate any suggestions.
Thanks!
PS: Am I right that the official v1.1 is available now? Anyway, I need to get CWM to have more freedom for experiments.
PPS: After all, official Spain 1.1 from ZTE returns me the "Error in /tmp/sideload/package.zip". And if I modify zip to fix Error 7, it doesn't pass signature check and we return to the rooting problem
Please, help me to defeat this damn phone.
ovasilis74 said:
Well, I succefully flashed fos1.1, worked OK, but then I found a "reason" to brick the poor device...
I belive I'm not off-topic because I think the Movistar1.1 flashed the ClockworkRecovery also, so I ended with a StockRecoveryMode, that was also inaccesible from adb with my Xubuntu12.04.
I tried to root the ZTEOpen and install ClockworkRecovery again, but both failled... endless reboots after ./run.sh
From the StockRecoveryMode I tried to "apply update from external stor(age)" with:
EU_DEV_FFOS_V1.0.0B02_USER_SD.zip
images-keon-v1.2-2013-11-04.Gecko-9082581.Gaia-f18e209.zip
B2G_P752D04V1.1.0B04_TME(SD).zip
all gave verification errors, also with and without the fix for "status 7 error".
Then i flashed:
Update package of Android GB for OPEN device
from: firefox.ztems.com (search site, cannot link).
The installation was completed, but after that I did something I didn't expect to end like this: I selected "reboot" but in the next screen (asking reboot or not) I selected NOT to reboot, so I review the previous menu again, BUT the device rebooted anyway! I don't realy know if this caused the final problem.
That's the end of the story for now, the "semi-brick-zte" boots either in "Android system recovery <3a>" (volume-up + power-button) or if I select "reboot system now" endless reboots with the fox looking something to the right of the screen...
I'll try to find how "flashboot" works, for now it does not see the device (recovery only).
Any sugestions/guides?
Click to expand...
Click to collapse
Hi ovasilis74,
there you go, the same text again, but with links:
I've tried something similar you have.
I did root the FFOS V1.0.0, and flashed ClockWorkMod recovery, but then I've tried some Columbia offical Zte Open firmware and it flashed recovery. Then I updated the zip file from the same link as you did (firefox.ztems.com). Then I've downloaded another firmware from here -> triplew.ztedevices.com/support/smart_phone/cba40ed6-d3ab-44c0-bdee-3a15803dc187.html?type=software and sign it with this command -> java -Xmx1024m -jar signapk.jar -w testkey.x509.pem testkey.pk8 test.zip test-signed.zip (thanks to that page -> wiki.rootzwiki.com/Signing ) (I've downloded signapk software somewhere from internet, I can't remember)
Then I've uploaded that signed zip file to sdcard, and ran install from zip file in this android system recovery.
I hope it helps.
walter_wireless said:
Hello.
I try to achieve root with OPEN_US_DEV_FFOS_V1.0.0B02 installed.
But the process always stops on "This works only once a boot."
And then phone just reboots and script failes, like this one:
...
Click to expand...
Click to collapse
I think you are using Windows and executing "run.bat", because in Linux the "run.sh" is automaticaly executed and after some times rooting succedes. My first attempt was this:
Code:
[email protected]:~/root-zte-open$ sudo ./run.sh
Connect your phone to USB, then:
Settings -> Device information -> More Information -> Developer
and enable 'Remote debugging'
444 KB/s (19208 bytes in 0.042s)
== root for Movistar zte open (roamer2) by @pof
== CVE-2012-4220 - discovered by giantpune
== original exploit by Hiroyuki Ikezoe
== if the phone hangs, remove the battery and try again!
roamer2 (OPEN_EU_DEV_FFOS_V1.0.0B02) is not supported.
Attempting to detect from /proc/kallsyms...
roamer2 (OPEN_EU_DEV_FFOS_V1.0.0B02) is not supported.[diag]
Attempting to inject code...
This works only once a boot.
roamer2 (OPEN_EU_DEV_FFOS_V1.0.0B02) is not supported.[diag]
Attempting to inject code...
This works only once a boot.
failed to get root access
Exploit failed, rebooting and trying again!
445 KB/s (19208 bytes in 0.042s)
== root for Movistar zte open (roamer2) by @pof
== CVE-2012-4220 - discovered by giantpune
== original exploit by Hiroyuki Ikezoe
== if the phone hangs, remove the battery and try again!
roamer2 (OPEN_EU_DEV_FFOS_V1.0.0B02) is not supported.
Attempting to detect from /proc/kallsyms...
roamer2 (OPEN_EU_DEV_FFOS_V1.0.0B02) is not supported.[diag]
Attempting to inject code...
This works only once a boot.
roamer2 (OPEN_EU_DEV_FFOS_V1.0.0B02) is not supported.[diag]
Attempting to inject code...
This works only once a boot.
Got root! - copying su binary!
Enjoy!
[email protected]:~/root-zte-open$
I got root the second time, but I think they could be more...
If you use Windows repeat the "run.bat" command or whatever you do in Windows ( I haven't tried) and normaly rooting sould hapen, ...then be careful, I wasn't...
Note, that after flashing the 1.1 the CWM will be replaced by the stock-recovery. I've read somewhere that if you delete the recovery.img from the .zip(e.g. 1.1.zip) you can avoid that.
Good luck!
ovasilis74 said:
I think you are using Windows and executing "run.bat", because in Linux the "run.sh" is automaticaly executed and after some times rooting succedes. My first attempt was this:
Code:
[email protected]:~/root-zte-open$ sudo ./run.sh
Connect your phone to USB, then:
Settings -> Device information -> More Information -> Developer
and enable 'Remote debugging'
444 KB/s (19208 bytes in 0.042s)
== root for Movistar zte open (roamer2) by @pof
== CVE-2012-4220 - discovered by giantpune
== original exploit by Hiroyuki Ikezoe
== if the phone hangs, remove the battery and try again!
roamer2 (OPEN_EU_DEV_FFOS_V1.0.0B02) is not supported.
Attempting to detect from /proc/kallsyms...
roamer2 (OPEN_EU_DEV_FFOS_V1.0.0B02) is not supported.[diag]
Attempting to inject code...
This works only once a boot.
roamer2 (OPEN_EU_DEV_FFOS_V1.0.0B02) is not supported.[diag]
Attempting to inject code...
This works only once a boot.
failed to get root access
Exploit failed, rebooting and trying again!
445 KB/s (19208 bytes in 0.042s)
== root for Movistar zte open (roamer2) by @pof
== CVE-2012-4220 - discovered by giantpune
== original exploit by Hiroyuki Ikezoe
== if the phone hangs, remove the battery and try again!
roamer2 (OPEN_EU_DEV_FFOS_V1.0.0B02) is not supported.
Attempting to detect from /proc/kallsyms...
roamer2 (OPEN_EU_DEV_FFOS_V1.0.0B02) is not supported.[diag]
Attempting to inject code...
This works only once a boot.
roamer2 (OPEN_EU_DEV_FFOS_V1.0.0B02) is not supported.[diag]
Attempting to inject code...
This works only once a boot.
Got root! - copying su binary!
Enjoy!
[email protected]:~/root-zte-open$
I got root the second time, but I think they could be more...
If you use Windows repeat the "run.bat" command or whatever you do in Windows ( I haven't tried) and normaly rooting sould hapen, ...then be careful, I wasn't...
Note, that after flashing the 1.1 the CWM will be replaced by the stock-recovery. I've read somewhere that if you delete the recovery.img from the .zip(e.g. 1.1.zip) you can avoid that.
Good luck!
Click to expand...
Click to collapse
I have tried different variations of this script for many-many times. And it writes nothing, not "failed", just nothing. And then phone reboots.
But OK, I will try to repeat all operations in Linux, although I don't see the principal difference, seems like the problem lies in damn phone
I will post the results. Thanks. And thank you for precautions about recovery.:good:
Hi,
rooting my LG H440n Spirit 4G phone (Lolipop 5.0.1) has failed at the moment when "Firmware Update" notification showed up on the mobile phone screen (after rooting had started and rebooted once). It says on the phone screen that I should not unplug USB connection to my phone. But since rooting failed what should I do now?
Closing down command line with LG Root Script running did not stop Firmware Update and it is still displayed on my phone.
Is it safe to disconnect usb right now from my phone and try rooting my phone again?
Thank you very much for any advise and support.
cbx44 said:
Hi,
rooting my LG H440n Spirit 4G phone (Lolipop 5.0.1) has failed at the moment when "Firmware Update" notification showed up on the mobile phone screen (after rooting had started and rebooted once). It says on the phone screen that I should not unplug USB connection to my phone. But since rooting failed what should I do now?
Closing down command line with LG Root Script running did not stop Firmware Update and it is still displayed on my phone.
Is it safe to disconnect usb right now from my phone and try rooting my phone again?
Thank you very much for any advise and support.
Click to expand...
Click to collapse
I have the same problem I tried one click root 1.3 and the old script 1.2 android 5.0.1 v10f-EUR-XX. HELP US!
Updated to V10j-214-03 and cannot root
Hello.
Last Friday 23/10/2015 I updated my phone to V10j-214-03 and cannot root it again.
Anyone has updated and rooted this version?
Thank you very much!
Hello. I tried to see if we could use the Low Effort Root on our device. I made some progress, but I am unable to finish what I started because I am stuck[ somewhere.
What I did:
1. Extract the v10h kdz.
2. Get the v10h system.img and the file "PrimaryGPT_0.bin" from the extracted files.
3. Inject root into the v10h system.img: http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
3. Rename the "PrimaryGPT_0.bin" into "gpt.img". Then go to ubuntu, open a terminal and run: "# sudo gdisk /path/of/gpt.img"
This gives us the partition info for our device: http://pastebin.com/u9maAAdm
This will help us determine the bs, seek and count when we will use the "Send_Command.exe" to push the v10h system to our device.
4. Based on @autoprime 's help, we have to do some calculations. http://pastebin.com/brcXBpja
[I think that he made a mistake though (missed to multiply by 512 on count). This seems more correct to me: http://pastebin.com/tHUbicR8 )
5. After calculating bs, seek and count, we are supposed to run the Low Effort Root procedure for our device.
But, after running the dd command, a "#" comes immediately, which means that something is going wrong. The "#" should take some time to appear, meaning that the copy is in progress. I couldn't identify what I am doing wrong, so I publish my effort, because maybe someone has more knowledge and may be able to make it work! @midzan21 maybe?
Autoprime, thanks for your help and guidance through irc.
Original Low Effort Root thread: http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
polfrank said:
Hello. I tried to see if we could use the Low Effort Root on our device. I made some progress, but I am unable to finish what I started because I am stuck[ somewhere.
What I did:
1. Extract the v10h kdz.
2. Get the v10h system.img and the file "PrimaryGPT_0.bin" from the extracted files.
3. Inject root into the v10h system.img: http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
3. Rename the "PrimaryGPT_0.bin" into "gpt.img". Then go to ubuntu, open a terminal and run: "# sudo gdisk /path/of/gpt.img"
This gives us the partition info for our device: http://pastebin.com/u9maAAdm
This will help us determine the bs, seek and count when we will use the "Send_Command.exe" to push the v10h system to our device.
4. Based on @autoprime 's help, we have to do some calculations. http://pastebin.com/brcXBpja
[I think that he made a mistake though (missed to multiply by 512 on count). This seems more correct to me: http://pastebin.com/tHUbicR8 )
5. After calculating bs, seek and count, we are supposed to run the Low Effort Root procedure for our device.
But, after running the dd command, a "#" comes immediately, which means that something is going wrong. The "#" should take some time to appear, meaning that the copy is in progress. I couldn't identify what I am doing wrong, so I publish my effort, because maybe someone has more knowledge and may be able to make it work! @midzan21 maybe?
Autoprime, thanks for your help and guidance through irc.
Click to expand...
Click to collapse
Well that what you try to did we got for v10a ROM via Universal LG Root for Lollipop. There is something that you can look about commands. Unfortienatly I can't try anything for now, because I need fully working phone and fully working Arch Linux VM for some networking testings.
midzan21 said:
Well that what you try to did we got for v10a ROM via Universal LG Root for Lollipop. There is something that you can look about commands. Unfortienatly I can't try anything for now, because I need fully working phone and fully working Arch Linux VM for some networking testings.
Click to expand...
Click to collapse
I think it's not the same. With Universal tool we ran a script that was stored on internal SD and this script pushed SuperSU.apk su.bin etc to the system. Now, we replace the whole System.img with a rooted one, and I think this is the point of Low Effort Root.
polfrank said:
I think it's not the same. With Universal tool we ran a script that was stored on internal SD and this script pushed SuperSU.apk su.bin etc to the system. Now, we replace the whole System.img with a rooted one, and I think this is the point of Low Effort Root.
Click to expand...
Click to collapse
so here are some of calculations which I did on my Windows ... I think that somewhere calculation for count is weird because it get into floating data point (decimal numbers)
skip/seek = 51008
count = 314530.125
bs = 8192 (used that as default)
edit: calculated using this calculations for count
[(end sector - start sector +1)*Logical sector size] / bs
Logical sector size iz 512 b
midzan21 said:
so here are some of calculations which I did on my Windows ... I think that somewhere calculation for count is weird because it get into floating data point (decimal numbers)
skip/seek = 51008
count = 314530.125
bs = 8192 (used that as default)
Click to expand...
Click to collapse
Aha, I noticed this and I set the bs to 1024. Then, I made the calculations and they seemed normal. But I 'm not sure if changing the bs would mess up things. The thing is that, whatever I used as numbers, the command wouldn't run.
I mean like how will ur calculations help us to root our phones? Is there a way to root my LG spirit?
JJolii said:
I mean like how will ur calculations help us to root our phones? Is there a way to root my LG spirit?
Click to expand...
Click to collapse
They can help us write a dd command correctly, so that we can send a rooted system.img in the correct partition of our device. So basically, if it worked, we would have had root on v10h now. But as I said, I am missing something.
polfrank said:
They can help us write a dd command correctly, so that we can send a rooted system.img in the correct partition of our device. So basically, if it worked, we would have had root on v10h now. But as I said, I am missing something.
Click to expand...
Click to collapse
Ive got v10f-eur-xx
I've tried SRSroot v5.1.
20:02:34 [+] Testing exploit: root8 (please wait..)
20:02:35 [+] Remounting /system Filesystem as R/W..
20:02:35 [+] Installing SU Binary...
20:02:35 [+] Installing SuperUser APK...
20:02:35 [+] Remounting /system Filesystem as R/O..
20:02:42 [+] Rooting Complete !
After restart theres not SU apk and I checked if my phone is rooted by Root checker basic and it says its not rooted. Im so frustrated in rooting my phone.. Im out of solutions how to root that piece of ****.
JJolii said:
Ive got v10f-eur-xx
I've tried SRSroot v5.1.
20:02:34 [+] Testing exploit: root8 (please wait..)
20:02:35 [+] Remounting /system Filesystem as R/W..
20:02:35 [+] Installing SU Binary...
20:02:35 [+] Installing SuperUser APK...
20:02:35 [+] Remounting /system Filesystem as R/O..
20:02:42 [+] Rooting Complete !
After restart theres not SU apk and I checked if my phone is rooted by Root checker basic and it says its not rooted. Im so frustrated in rooting my phone.. Im out of solutions how to root that piece of ****.
Click to expand...
Click to collapse
Have you tried kingroot?
polfrank said:
Have you tried kingroot?
Click to expand...
Click to collapse
Yes I did, Pc version and android app version, none of them worked.
Well, just go back to v10e-EUR-xx with the LG Flash Tool and root it with Kingroot. Worked for me.
Not mentioning the amount of hair I pulled out trying to root v10f...
Tomo123 said:
Well, just go back to v10e-EUR-xx with the LG Flash Tool and root it with Kingroot. Worked for me.
Not mentioning the amount of hair I pulled out trying to root v10f...
Click to expand...
Click to collapse
Just CSE flashed v10c and rooted with kingroot
Tomo123 said:
Well, just go back to v10e-EUR-xx with the LG Flash Tool and root it with Kingroot. Worked for me.
Not mentioning the amount of hair I pulled out trying to root v10f...
Click to expand...
Click to collapse
can u help me/guide me through Skype or Teamviewer? Please.
k got v10e-eur-xx rom and tried to root with kingoroot and oneclickroot 1.3 still doesn't root. What could be the problem?
JJolii said:
k got v10e-eur-xx rom and tried to root with kingoroot and oneclickroot 1.3 still doesn't root. What could be the problem?
Click to expand...
Click to collapse
Which version of kingroot are you using?
polfrank said:
Which version of kingroot are you using?
Click to expand...
Click to collapse
BETA : 2.5 android app
JJolii said:
BETA : 2.5 android app
Click to expand...
Click to collapse
Try this one: http://forum.xda-developers.com/devdb/project/dl/?id=14576
Click Direct Download.