Related
To downgrade your HBOOT to go back to 2.2 visit this link http://forum.xda-developers.com/showthread.php?t=1255474
This will allow you to flash 2.2 to perm root the phone
If you wish to help with perm root status for Android 2.3.3, please visit this thread http://forum.xda-developers.com/showthread.php?t=1218580
Thanks to everyone in this post who has helped get this far. You will need to have the Android SDK installed and working knowledge of ADB and basic file system structure.
Major help from minneyar
TEMP ROOT Instructions:
Download http://tinyw.in/1lI
Unzip if required and put in your ADB folder
Launch command prompt and navigate to your ADB folder
adb push fre3vo /data/local/tmp/
adb shell
chmod 777 /data/local/tmp/fre3vo
/data/local/tmp/fre3vo -debug -start fbb58a00 -end FFFFFFFF (if this doesn't work, try rebooting phone)
Download these 2 files here and put them in your ADB directory: http://forum.xda-developers.com/showthread.php?p=14927732#post14927732
exit back to command prompt if you aren't there already
adb push Superuser3-beta1.apk /data/app/
adb push su-3.0-alpha7 /data/local/tmp
adb shell (should now see # instead of $)
cd /data/local/tmp
chmod 777 su-3.0-alpha7
./su-3.0-alpha7
cd /
mount -o remount,rw -t rootfs rootfs /
rm vendor
mkdir vendor
mkdir vendor/bin
cat /data/local/tmp/su-3.0-alpha7 > /vendor/bin/su
chmod 4755 /vendor/bin/su
You now have temp root. Disregard any notification about outdated SU binary. Root will go away if you reboot. If you reboot your phone you can obtain root again by just running the following
adb shell
chmod 777 /data/local/tmp/fre3vo
/data/local/tmp/fre3vo -debug -start fbb58a00 -end FFFFFFFF
adb shell (should now see # instead of $)
cd /data/local/tmp
chmod 777 su-3.0-alpha7
./su-3.0-alpha7
cd /
mount -o remount,rw -t rootfs rootfs /
rm vendor
mkdir vendor
mkdir vendor/bin
cat /data/local/tmp/su-3.0-alpha7 > /vendor/bin/su
chmod 4755 /vendor/bin/su
I haven't found a way to re-root after rebooting without connecting to a PC
Type su and see if it gives you root permissions
Sent from my MiuiSpeedy
says su: not found.
You are saying you cannot install the superuser app? From reading in the Evo3D forums, you could install Superuser, even without being rooted, but it obviously won't allow root access, until you run a root exploit.
Try rebooting the phone, installing superuser, run fre3vo, and then try the adb shell, and su method.
This is getting interesting. Hopefully you are on to something.
Stuke00 said:
See screenshot. Doesn't the # mean temp rooted? Tho I cannot install SU and Root Explorer isn't working. Anything else I need to do first or something?
Click to expand...
Click to collapse
Looks hopeful!
tokuzumi said:
You are saying you cannot install the superuser app? From reading in the Evo3D forums, you could install Superuser, even without being rooted, but it obviously won't allow root access, until you run a root exploit.
Try rebooting the phone, installing superuser, run fre3vo, and then try the adb shell, and su method.
This is getting interesting. Hopefully you are on to something.
Click to expand...
Click to collapse
Okay let me clarify
I can install SU but it wouldn't install the binaries. I did all of the above. Says su: not found.
I then tried something else.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cat /system/bin/sh > /system/bin/su
# chmod 4755 /system/bin/su
I was then able to get the SU binaries to install but Titanium Backup says:
"Busybox works but the "su" command does not elevate to root: "whoami" reports "app_135" instead of root/uid 0.
then su from the command prompt was saying "link_image[1935]: 3160 missing essential tablesCANNOT LINK EXECUTABLE" and now back to su: not found again....
I don't know enough about linux commands to give you any real info. Like in the other thread, talk to agrabren, to see what he has to say.
tokuzumi said:
I don't know enough about linux commands to give you any real info. Like in the other thread, talk to agrabren, to see what he has to say.
Click to expand...
Click to collapse
Yeah I tweeted him with what I could provide with 160 characters. Just waiting now.
Well here's a tweet he put out a couple of hours ago.
@agrabren: For those with the SHIFT, it's a known bug in my code that we missed the address. One too many zeroes in the list. I'll try to fix it soon.
Sent from my PG06100 using XDA App
crump84 said:
Well here's a tweet he put out a couple of hours ago.
@agrabren: For those with the SHIFT, it's a known bug in my code that we missed the address. One too many zeroes in the list. I'll try to fix it soon.
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Yeah he posted that right after I gave him the memory address for the exploit. Just means that I did it the manual way through debugging. At least I think so... hopefully soon!
Good news, everybody! I have successfully acquired temp root on my Shift!
First, fre3vo has to be pointed at the right address. After copying it over to my phone, I did "adb shell" and then ran it like so:
/data/local/tmp/fre3vo -debug -start fbb58a00 -end FFFFFFFF
That printed out a message that it found an exploit and kicked me out of the shell. After doing "adb shell" again, I got a command prompt. I tried installing the 2.3.6.3 version of Superuser, but it complained about being unable to install "su"; I tried to find a separate su binary and copy it over manually, but it didn't work due to a linker error.
After searching around, I found a beta version of Superuser 3:
http://forum.xda-developers.com/showthread.php?p=14927732#post14927732
First I uninstalled the old version of Superuser and then used adb to install the new one from that thread. I ran it and it said it was unable to install su, so I downloaded the version of su provided there and installed it manually. The process went something like:
Code:
adb push su-3.0-alpha7 /data/local/tmp
adb shell
# cd /data/local/tmp
# chmod 4755 su-3.0-alpha7
# ./su-3.0-alpha7
# mount -o remount,rw -t ext3 /dev/block/mmcblk0p26 /system
# cat su-3.0-alpha7 > /system/bin/su
# chmod 4755 /system/bin/su
I don't know if explicitly running "./su-3.0-alpha7" is necessary, it just seemed like a good idea at the time. I don't know if everybody's block device will be named "mmcblk0p26", I used "mount" to figure out what was mounted at /system.
Anyway, after all that was done, I ran Superuser again and it didn't complain. To test it out, I started up Wireless Tether. It asked me for superuser permissions, which I granted it, and it's working fine.
Root successful!
Good job!!
Sent from my Speedy HTC EVO shift on XDA Premium app
I followed those steps exactly and got what I would call a partial root. Some of the 'you need root' errors are gone but "su" still results in 'not found' even though "mkdir su" results in 'file exists.'
mmcblk0p26 exists on this unit.
The weirdest part is that Adfree will accept the device as rooted and with superuser but says it can't find a partition to modify. And after a reboot root is definitely gone.
I think you're on to it but it isn't quite there yet.
It seems to be fully temprooted to me; I have to redo it if I reboot, but otherwise it's working perfectly. After following the steps I listed above, running "ls -l /system/bin/su" should produce this output:
Code:
# ls -l /system/bin/su
ls -l /system/bin/su
-rwsr-xr-x root root 22228 2011-07-25 19:14 su
If it says "No such file or directory" instead, then the su binary isn't in the right place.
Looking back over what I wrote, I think I left out a step -- if you were following what I listed exactly, it probably won't work, because I forgot to change to the /data/local/tmp directory. I'll update that...
Update: after playing around with it for a while, something is definitely not quite right. Everything works fine at first; I've tested Wireless Tether and Titanium Backup and they're both fine. After leaving my phone for a while and coming back, though, applications that try to get root access mysteriously fail. The dialog prompt doesn't even appear.
Going back into the adb shell, /system/bin/su is still there, but trying to run "su" causes this to happen:
Code:
# su
su
link_image[1935]: 3802 missing essential tablesCANNOT LINK EXECUTABLE
But if I use cat to overwrite su and then chmod it again, everything works. su must somehow be getting modified by something else and replaced with a bad version... but I'm not sure where to look.
I caught something like that.
I think there should be a chmod 777 su-3.0-alpha7 after cd /data/local/tmp
minneyar said:
It seems to be fully temprooted to me; I have to redo it if I reboot, but otherwise it's working perfectly. After following the steps I listed above, running "ls -l /system/bin/su" should produce this output:
Code:
# ls -l /system/bin/su
ls -l /system/bin/su
-rwsr-xr-x root root 22228 2011-07-25 19:14 su
If it says "No such file or directory" instead, then the su binary isn't in the right place.
Looking back over what I wrote, I think I left out a step -- if you were following what I listed exactly, it probably won't work, because I forgot to change to the /data/local/tmp directory. I'll update that...
Update: after playing around with it for a while, something is definitely not quite right. Everything works fine at first; I've tested Wireless Tether and Titanium Backup and they're both fine. After leaving my phone for a while and coming back, though, applications that try to get root access mysteriously fail. The dialog prompt doesn't even appear.
Going back into the adb shell, /system/bin/su is still there, but trying to run "su" causes this to happen:
Code:
# su
su
link_image[1935]: 3802 missing essential tablesCANNOT LINK EXECUTABLE
But if I use cat to overwrite su and then chmod it again, everything works. su must somehow be getting modified by something else and replaced with a bad version... but I'm not sure where to look.
Click to expand...
Click to collapse
YES! I have root! I was able to install a screenshot app and test it this is amazing progress! Thanks for that.
So now when I reboot, you have to do the entire thing again? SU and all?
Stuke00 said:
So now when I reboot, you have to do the entire thing again? SU and all?
Click to expand...
Click to collapse
Yes, every time you reboot you'll have to redo the whole process, including running fre3vo and then copying su into /system/bin. Hopefully somebody will figure out a permanent root soon.
Wow those SU binaries are disappearing before I even reboot! Already gone and I haven't rebooted the phone
I think I had that issue too. I just couldn't believe the files just disappeared and thought I did something wrong somewhere.
Would a logcat help anyone at all? Anything I should look for?
Can anyone help me with rooting U8800pro running the official 2.3.5 ?
I tried all the methods I was using for the U8800 but all of them doesn’t work... Any advice ?
i have the same problem, how to root???
linomaniac said:
i have the same problem, how to root???
Click to expand...
Click to collapse
i'm searching everywhere for 3 days now with nothing usefull
If automatic ways failed try this:
http://forum.xda-developers.com/showthread.php?t=1423422
dancer_69 said:
If automatic ways failed try this:
http://forum.xda-developers.com/showthread.php?t=1423422
Click to expand...
Click to collapse
i think its not that easy to me to do it manual
but thanks anyway for trying to help
Of course automatic ways are easier, but it' s not that difficult, just need a little more time and attention.
The other way is to find a prerooted boot.img and put it to .cust_backup/image folder(replacing the original). I haven't pro model, so my boot.img will not work
dancer_69 said:
Of course automatic ways are easier, but it' s not that difficult, just need a little more time and attention.
The other way is to find a prerooted boot.img and put it to .cust_backup/image folder(replacing the original). I haven't pro model, so my boot.img will not work
Click to expand...
Click to collapse
i tried this way but it didn't work too.. i found a prerooted boot.img.. replaced the original one but it didnt work
To just say didn't work doesn't help. Write where you get an error and which is. Then maybe I can help you(or someone with more knowledge).
dancer_69 said:
To just say didn't work doesn't help. Write where you get an error and which is. Then maybe I can help you(or someone with more knowledge).
Click to expand...
Click to collapse
i got the prerooted boot.img file for the U8800pro... replaced it with the original one.. But the phone is not booting.. It stuck on the huawie logo (the 1st logo before the one with the animation) so i had to put back the original one to make it work
I mean the error on manual rooting.
As fro prerooted boot.img file, are you sure that is compatible with ther rom you have? If is from a custom rom will not work. You need the boot.img of a phone with the same rom as yours, just rooted.
well, maybe it wasn't compatible with my stock rom.. do you have anywhere where i can find some prerooted imgs ?
and about the manual root.. i didnt got any errors coz i didnt know how to wirte those codes :s
Sorry I' don't know because I haven't a pro model and I don't know if there is a rooted boot.img uploaded fro pro mode. Maybe a member with pro read your thread and upload his img file.
-About manual rooting, you need to open DOS command prompt window. It' s in all progarms -> accessories
If you put the DoomLordRoot program in the root directory of your C drive and rename this folder to DoomLordRoot.v3(if have another name), you need to just put the commands one by one as given on the link I posted.
You just need to put first the command:
cd \DoomLordRoot.v3\files
to go to directory in which adb.exe is.
You can check if you are in the right path if you enter the command:
dir
afterwards. If you are in correct folder you'll see the files which are in c:\DoomLordRoot.v3\files directrory listed.
After that just start to follow the directions of the link. Just hit enter after every command you put. If you don' t see errors after every command you're ok. If you get an error on a command, write it here, for farther help. I don' t think that you' ll get an error, because I've done this proccess about 5 times and never get an error. But if you do, just put it here to see if we can help.
Thanks alot bro for the help.
well, i followed what u said but i think i got confused somewhere.. i'll type what i got.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\User>cd\
C:\>cd DoomLordRoot.v3
C:\DoomLordRoot.v3>cd files
C:\DoomLordRoot.v3\files>adb shell
$ chmod 777 /data/local/tmp/zergRush
chmod 777 /data/local/tmp/zergRush
$
$ ./data/local/tmp/zergRush
./data/local/tmp/zergRush
[**] 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 GingerBread ! 0x00000118
[*] Scooting ...
bugreport dir[/data/local/tmp] exist.
[*] Sending 149 zerglings ...
bugreport dir[/data/local/tmp] exist.
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
$
$ ^C
C:\DoomLordRoot.v3\files>adb shell
$ chmod 755 /data/local/tmp/busybox
chmod 755 /data/local/tmp/busybox
$
$ /data/local/tmp/busybox mount -o remount,rw /system
/data/local/tmp/busybox mount -o remount,rw /system
mount: permission denied (are you root?)
$
$ dd if=/data/local/tmp/busybox of=/system/xbin/busybox
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
/system/xbin/busybox: cannot open for write: Read-only file system
$
VaMpYMaSTeR said:
Thanks alot bro for the help.
well, i followed what u said but i think i got confused somewhere.. i'll type what i got.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\User>cd\
C:\>cd DoomLordRoot.v3
C:\DoomLordRoot.v3>cd files
C:\DoomLordRoot.v3\files>adb shell
$ chmod 777 /data/local/tmp/zergRush
chmod 777 /data/local/tmp/zergRush
$
$ ./data/local/tmp/zergRush
./data/local/tmp/zergRush
[**] 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 GingerBread ! 0x00000118
[*] Scooting ...
bugreport dir[/data/local/tmp] exist.
[*] Sending 149 zerglings ...
bugreport dir[/data/local/tmp] exist.
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
$
$ ^C
C:\DoomLordRoot.v3\files>adb shell
$ chmod 755 /data/local/tmp/busybox
chmod 755 /data/local/tmp/busybox
$
$ /data/local/tmp/busybox mount -o remount,rw /system
/data/local/tmp/busybox mount -o remount,rw /system
mount: permission denied (are you root?)
$
$ dd if=/data/local/tmp/busybox of=/system/xbin/busybox
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
/system/xbin/busybox: cannot open for write: Read-only file system
$
Click to expand...
Click to collapse
Put su or sudo before command. like this "su /data/local/tmp/busybox mount -o remount,rw /system"
Yes, seems that you didn' t give the su command before(I think I've include command su, on my tutorial but I' m not sure. I'll check it).
If you see the symbol $ this means that you haven't get root rights yet.
Seems that zergrush succeed, so everytime after adb shell command, first you need to give the command:
su
If device is rooted, you'll see that the symbol changes to #
I think that you' re in good way though.
when i put SU in the begining it give me this :
su: permission denied
if you rebooted the phone you must run zergrush again.
Zergrush is the hack that unlocks the root account temporary. If you didn' t success to put su program on the right place, rooting access loosed after rebooted. su makes root permanent, busybox is an advanced shell and superuser is the app which used to give or denied root rights to apps which asking for this.
First be sure that zergrush is copied to data/local/tmp and you give to it the right permissions(all commands are in tutorial)
These messages mean that zergrush running
[+] Found a GingerBread ! 0x00000118[*] Scooting ...
bugreport dir[/data/local/tmp] exist.[*] Sending 149 zerglings ...
bugreport dir[/data/local/tmp] exist.[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
Click to expand...
Click to collapse
after that check if root succeed by input su command. If you get the # sign you're good to go to continue(exit shell etc)
i'm so sorry, but what do you mean with "If you didn' t success to put su program on the right place" ???? what where is the right palce ?
Some of the commands on tutorial handle the su program.
Push it to /system/bin(this is the right place), change its ownership, permissions etc.
For these commands to succeed(and also the commands for busybox and superuser), first need to enter to root account, by command su:
adb shell (press enter)
su (press enter)
these give the # sign which means that you are root.
If you don' t do this all commands will fail with errors as:
permission denied or cannot write to...
now i'm getting this:
C:\DoomLordRoot.v3\files>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ chmod 777 /data/local/tmp/zergRush
chmod 777 /data/local/tmp/zergRush
Unable to chmod /data/local/tmp/zergRush: No such file or directory
$
i think i will give up
Hello everyone...
I have a Motorola RAZR 201M(XT902) in Japan and use Motofail2go to root it.But it doesn't work.
(follow http://forum.xda-developers.com/showthread.php?p=32889627)
I installed Sudoku.apk and push the motofail2go to the device(also su,Superuser.apk,busybox).
when
$ run-as com.motorola.bug2go /data/local/tmp/motofail2go prep2
Here is the error message:
"run-as: exec failed for /data/local/tmp/motofail2go Error: Operation not permitted"
and i try $ run-as com.motorola.bug2go
but error message : "run-as: exec failed"
Anyone help? Thanks...
Sorry buddy. Nothing works. We 201m users are SOL.
Have you tried this?
http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit/
Thanks Paul!
No luck with that either. Appreciate the feedback, however.
I hope somebody will study the XT902 root.
goodayoo said:
I hope somebody will study the XT902 root.
Click to expand...
Click to collapse
I really want this thing rooted. How do one go about figuring out how to root it? I assume because of it's lack of popularity, no one has done it, but I'm willing to do the grunt work if there's some sort of guide or assistance. I changed over to DoCoMo with the GS4 and now have this paperweight that I would want to actually use.
Thanks!
Almalieque said:
I really want this thing rooted. How do one go about figuring out how to root it? I assume because of it's lack of popularity, no one has done it, but I'm willing to do the grunt work if there's some sort of guide or assistance. I changed over to DoCoMo with the GS4 and now have this paperweight that I would want to actually use.
Thanks!
Click to expand...
Click to collapse
There some Japanese guys doing some things to try and get root. They are active. The site has a lot of rather unpleasant (read offensive) advertisements. PM if you are interested (its in Japanese)
root
help!!!
Root and Unlocked bootloaders!
Proceed at yor own risk
hungln03 said:
help!!!
Click to expand...
Click to collapse
1)Prep
Android SDKと各種ドライバを導入する。
以下の必要ファイルをC:\***（何でも良い）に配置する。
・XT902_SBMの中身(http://www1.axfc.net/uploader/so/2991543 >>125氏)
・su（http://www1.axfc.net/uploader/so/2918729 password：f10d）
・Superuser.apk（in the above downloaded）
・busybox（in the above downnloaded）
201M Plug the phone into the comp
any port will do
2)adb pushで必要ファイルを/data/local/tmp転送
コマンドプロンプトを開く
C:\Users\（ユーザー名） >cd C:\***
adb push su /data/local/tmp
adb push Superuser.apk /data/local/tmp
adb push busybox /data/local/tmp
adb push unlock_security_module /data/local/tmp
adb push break_setresuid /data/local/tmp/
adb push mole-plough-ccsecurity.so /data/local/tmp/
adb push mole-plough-lsm.so /data/local/tmp/
3)unlock_security_module（temp root）
adb shell
[email protected]:/ $ cd /data/local/tmp/
[email protected]:/data/local/tmp $ chmod 777 *
[email protected]:/data/local/tmp $ ./unlock_security_module
[email protected]:/data/local/tmp $ ./break_setresuid
（unlock_security_moduleが動いてMIYABIとNANDロック解除）
（色々表示されるので↓が出る間で待つ）
Unlocked LSM.
Do setresuid...
OK.
[email protected]:/data/local/tmp #
（#if done correctly temp root should be achieved）
271 ：270：2013/09/15(日) 23:31:42.67 ID:tIg7fkl6
4)system putting together su，Superuser.apk，busybox
[email protected]:/data/local/tmp # mount -o rw,remount /system /system
[email protected]:/data/local/tmp # cat /data/local/tmp/su > /system/xbin/su
[email protected]:/data/local/tmp # cat /data/local/tmp/busybox > /system/xbin/busybox
[email protected]:/data/local/tmp # cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
[email protected]:/data/local/tmp # chmod 644 /system/app/Superuser.apk
[email protected]:/data/local/tmp # cd /system/xbin
[email protected]:/system/xbin # chown root.root su
[email protected]:/system/xbin # chown root.root busybox
[email protected]:/system/xbin # chmod 6755 su
[email protected]:/system/xbin # chmod 755 busybox
[email protected]:/system/xbin # mount -o ro,remount /system /system
After the opperation is done it is ok to remove the cable from the pc。
check and see if「SuperSU」was installed if it wasn't download chainfire (su) from the play store
⇒SU --> update
Fro the play store download busybox。
⇒busybox -->update
Get the right CWM.img http://forum.xda-developers.com/showthread.php?t=2298521の201M
put the CWM.img you downloaded in motoapoc file you find here
adb push unlock /data/local/tmp/
adb shell chmod 755 /data/local/tmp/unlock
adb shell
cd /data/local/tmp/
chmod 777 *
./unlock_security_module
./break_setresuid
./unlock
New Command prompt
5)Inserting CWM(PC Operation)
adb shell "su -c 'mount -o remount,rw /system'"
adb shell "su -c 'mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak'"
adb shell "su -c 'mv /system/recovery-from-boot.p /system/recovery-from-boot.bak'"
adb push cwm.img /data/local/tmp/cwm.img > nul
adb shell "su -c 'dd if=/data/local/tmp/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery'"
adb shell "su -c 'rm /data/local/tmp/cwm.img'"
adb reboot recovery
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
I don't own the 902, but it's good to see this. I know quite a few people have been looking for this. You should start your own thread with the procedures, so it will get more publicity.
Thank u!
thank u so much.!1
sbeaber4 said:
Proceed at yor own risk
271 ：270：2013/09/15(日) 23:31:42.67 ID:tIg7fkl6
Get the right CWM.img http://forum.xda-developers.com/showthread.php?t=2298521の201M
put the CWM.img you downloaded in motoapoc file you find here
adb push unlock /data/local/tmp/
adb shell chmod 755 /data/local/tmp/unlock
adb shell
cd /data/local/tmp/
chmod 777 *
./unlock_security_module
./break_setresuid
./unlock
New Command prompt
5)Inserting CWM(PC Operation)
adb shell "su -c 'mount -o remount,rw /system'"
adb shell "su -c 'mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak'"
adb shell "su -c 'mv /system/recovery-from-boot.p /system/recovery-from-boot.bak'"
adb push cwm.img /data/local/tmp/cwm.img > nul
adb shell "su -c 'dd if=/data/local/tmp/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery'"
adb shell "su -c 'rm /data/local/tmp/cwm.img'"
adb reboot recovery
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
Click to expand...
Click to collapse
Can you tell me more about this step
Confirm?
Can confirm if the latest instructions have worked for your 201m?
That your rooted and bootloader unlock.
Thanks a bunch!
Boot loader is unlocked and CWM is installed. Initially I still
Had temp root so I flashed slim beans xt907 rom. It works. I'm unable to test data with it as I don't have a SoftBank sim. Also I still can't connect to the play store.
sbeaber4 said:
Boot loader is unlocked and CWM is installed. Initially I still
Had temp root so I flashed slim beans xt907 rom. It works. I'm unable to test data with it as I don't have a SoftBank sim. Also I still can't connect to the play store.
Click to expand...
Click to collapse
Thanks for the feedback.
Still awaiting more confirmation with others. It's a step forward though.
I've had my phone for almost a year now. If I cancel my softbank service or run the contract to the end I want an option to root and unlock the bootloader in the future.
could u provide more friendly filehost?
i can't find the download button there
Root! (temp root that is...)
I'm just posting to confirm I've rooted my 201m (xt902).
Props to sbeaber4!
From my limited knowledge since it's temp root if I restart my phone I lose root access...
Next step in the future unlock bootloader.
Peace y'all.
Quick Tip
zenstarlight said:
I'm just posting to confirm I've rooted my 201m (xt902).
Props to sbeaber4!
From my limited knowledge since it's temp root if I restart my phone I lose root access...
Next step in the future unlock bootloader.
Peace y'all.
Click to expand...
Click to collapse
Found that if I a did restart my phone root was lost but I found a quick fix without going through the whole process again.
Just do these steps
unlock_security_module（temp root）
adb shell
[email protected]:/ $ cd /data/local/tmp/
[email protected]:/data/local/tmp $ ./unlock_security_module
Just enter those three steps then you're back to temp root
Also you can just to a quick reboot with link2sd or any other app that just reboots the android ui. You don't have to enter commands every time you reboot unless it's a full reboot.
Help for Gaigin rooting 201M
sbeaber4 said:
Proceed at yor own risk
...
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
Click to expand...
Click to collapse
Noob on XDA, and rooted a MT4G in the past wth help from these forums.
Can someone help translate the kanji for rooting the 201M? Will rooting allow you to change the device location and prevent random all Japanese pop-up alerts/"are you sure" messages? Thanks for any help
kprower said:
Noob on XDA, and rooted a MT4G in the past wth help from these forums.
Can someone help translate the kanji for rooting the 201M? Will rooting allow you to change the device location and prevent random all Japanese pop-up alerts/"are you sure" messages? Thanks for any help
Click to expand...
Click to collapse
Once CWM is online you might be able to flash a VZW or Aussie stock ROM. Actually, you could probably flash CM... That'll fix the Japanese popups. Of course, it also could very possibly brick it. Proper precautions must be made... On my tablet at the moment, does anyone know if sbf.droid-developers has 902 images?
Sent from my Nexus 7 using Tapatalk 4
*****WARNING!!! All your actions with the phone is at your own risk. The author are not liable. This is just your choice. ******
You need an MX4 Android version and an PC with Ubuntu, phablet-tools and adb-fastboot installed.
$ adb devices
$ adb shell grep ro.product.name /system/build.prop
ro.product.name=arale
$ adb shell grep build.id /system/build.prop
ro.build.id=KOT49H
$ adb shell grep ro.product.device /system/build.prop
ro.product.device=arale
$ ubuntu-device-flash query --device=arale --list-channels
$ wget http://people.canonical.com/~alextu/tangxi/recovery/recovery.img
$ adb reboot-bootloader
$ fastboot flash recovery recovery.img
$ fastboot reboot
From recovery:
$ ubuntu-device-flash touch --device=arale --channel=ubuntu-touch/stable/meizu.en --developer-mode --password=1234 --wipe
You can change you build.prop from another way: Root Browser.
@empies
Recovery must be unlocked? Can I flash it on CM12.1 or must be only Flyme?
Shadoworion said:
Recovery must be unlocked? Can I flash it on CM12.1 or must be only Flyme?
Click to expand...
Click to collapse
I found this tutorial on channel official of developing. I care yes just flash the recovery.
Naphtha said:
I found this tutorial on channel official of developing. I care yes just flash the recovery.
Click to expand...
Click to collapse
Can you give me link of this original tutorial? Have you ever tried it?
Shadoworion said:
Can you give me link of this original tutorial? Have you ever tried it?
Click to expand...
Click to collapse
Nope. I can't give you the link. I have an Mx4 32 gb with ubuntu touch, if i flash it is useless
Hi,
my build.prop values are:
ro.product.name=cm_mx4
ro.build.id=LMY48Y
ro.product.device=mx4
Do I have to change these before flashing?
Thanks in advance.
Danj1 said:
Hi,
my build.prop values are:
ro.product.name=cm_mx4
ro.build.id=LMY48Y
ro.product.device=mx4
Do I have to change these before flashing?
Thanks in advance.
Click to expand...
Click to collapse
yes change it first
Code:
2015/11/24 18:21:33 Device is |arale|
2015/11/24 18:21:33 Flashing version 7 from ubuntu-touch/stable/meizu.en channel and server https://system-image.ubuntu.com to device arale
/home/david/.cache/ubuntuimages/ubuntu-touch/stable/meizu.en/arale/version-7.tar.xz
/home/david/.cache/ubuntuimages/pool/device-a8a0e27cb5670a0ccb9dacd2b12dc80b2df8fe776235cf9a0f7478ef7aa934a4.tar.xz
at this moment the terminal is in slowdown status. what do I need to do?
Shadoworion said:
Code:
2015/11/24 18:21:33 Device is |arale|
2015/11/24 18:21:33 Flashing version 7 from ubuntu-touch/stable/meizu.en channel and server https://system-image.ubuntu.com to device arale
/home/david/.cache/ubuntuimages/ubuntu-touch/stable/meizu.en/arale/version-7.tar.xz
/home/david/.cache/ubuntuimages/pool/device-a8a0e27cb5670a0ccb9dacd2b12dc80b2df8fe776235cf9a0f7478ef7aa934a4.tar.xz
at this moment the terminal is in slowdown status. what do I need to do?
Click to expand...
Click to collapse
only, wait
2015/11/24 20:49:43 error pushing: failed to copy '/home/user/.cache/ubuntuimages/pool/device-ABCDEF.tar.xz' to '/cache/recovery//device-ABCDEF.tar.xz': No space left on device
Click to expand...
Click to collapse
Any idea how to get more space. What can safely be deleted?
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 946.3M 128.0K 946.1M 0% /dev
/dev/block/platform/mtk-msdc.0/by-name/cache
106.2M 53.2M 50.8M 51% /cache
Click to expand...
Click to collapse
/cache # du -h
4.0K ./lost+found
53.1M ./recovery
4.0K ./backup/1/_full
4.0K ./backup/1/_delta
12.0K ./backup/1
16.0K ./backup
53.2M .
Click to expand...
Click to collapse
Danj1 said:
Any idea how to get more space. What can safely be deleted?
Click to expand...
Click to collapse
you do wipe? you insert "--wipe"?
Naphtha said:
you do wipe? you insert "--wipe"?
Click to expand...
Click to collapse
The command I used:
ubuntu-device-flash touch --device=arale --channel=ubuntu-touch/stable/meizu.en --wipe
Naphtha said:
*****WARNING!!! All your actions with the phone is at your own risk. The author are not liable. This is just your choice. ******
You need an MX4 Android version and an PC with Ubuntu, phablet-tools and adb-fastboot installed.
$ adb devices
$ adb shell grep ro.product.name /system/build.prop
ro.product.name=arale
$ adb shell grep build.id /system/build.prop
ro.build.id=KOT49H
$ adb shell grep ro.product.device /system/build.prop
ro.product.device=arale
$ ubuntu-device-flash query --device=arale --list-channels
$ wget http://people.canonical.com/~alextu/tangxi/recovery/recovery.img
$ adb reboot-bootloader
$ fastboot flash recovery recovery.img
$ fastboot reboot
From recovery:
$ ubuntu-device-flash touch --device=arale --channel=ubuntu-touch/stable/meizu.en --developer-mode --password=1234 --wipe
You can change you build.prop from another way: Root Browser.
Click to expand...
Click to collapse
Seriously? You said stupid and you make a tuto exactly same as i said ?? -_-
bobslesbricoleurs said:
Seriously? You said stupid and you make a tuto exactly same as i said ?? -_-
Click to expand...
Click to collapse
btw it's not same be changed something and he already tried without changing device name etc.
damn WHY always after i brick phone
---------- Post added at 02:47 PM ---------- Previous post was at 02:45 PM ----------
@Naphtha is after ubuntu installation preloader unlocked ?
Partition resize of mx4 for flash ubuntu touch : http://forum.xda-developers.com/meizu-mx/general/meizu-mx4-partitions-table-help-resize-t3256902
Well. This Tuto is not complete, right? No need to re-size or anything?
hi this ways woks ? any issue ?
makakiel said:
hi this ways woks ? any issue ?
Click to expand...
Click to collapse
Nope don't work. If you flash ubuntu touch with this tutorial is full brick.
actualy what is missing ?
I see a other on wit ubuntu desktop this one work ?
SOLUTION: post #18
Hello,
For some reason all of my sensors are gone. See attachment.
Due to some problems i've formatted my "persist" partition. And from what i read, that partition contains all sorts of sensor parameters. So i guess i shouldn't have.
I've checked all files on the forum and original OTA's from oneplus. None of them have (working) partition for me.
Therefor i would like to ask someone with an A2003 device who has working sensors and is running OOS 3.02 or CM13 to perform the following actions and share the file with me:
(root (adb and apps) needed)
Code:
adb shell
su
su
cd /sdcard
dd if=/dev/block/bootdevice/by-name/persist persist.dd.img
exit
exit
And share the file "persist.dd.img" with me. It's on your sdcard.
Thanks very much in advance!
_HugoBoss_ said:
Hello,
For some reason all of my sensors are gone. See attachment.
Due to some problems i've formatted my "persist" partition. And from what i read, that partition contains all sorts of sensor parameters. So i guess i shouldn't have.
I've checked all files on the forum and original OTA's from oneplus. None of them have (working) partition for me.
Therefor i would like to ask someone with an A2003 device who has working sensors and is running OOS 3.02 or CM13 to perform the following actions and share the file with me:
(root (adb and apps) needed)
Code:
adb shell
su
su
cd /sdcard
dd if=/dev/block/bootdevice/by-name/persist persist.dd.img
exit
exit
And share the file "persist.dd.img" with me. It's on your sdcard.
Thanks very much in advance!
Click to expand...
Click to collapse
I uploaded it to AFH a while back - it's the stock persist.img from the OnePlus 2.2.0 Qualcomm Recovery Package. AFAIK, it's not been updated since then.
persist.img
Spannaa said:
I uploaded it to AFH a while back - it's the stock persist.img from the OnePlus 2.2.0 Qualcomm Recovery Package. AFAIK, it's not been updated since then.
persist.img
Click to expand...
Click to collapse
Hi,
Yeah, google found it for me. But sadly, it didn't work for me.
I've tryed installing it
- trough fastboot (fastboot flash persist persist.img) and also
- dd'ing it and also
- creating a flashable zip package_extract_file("persist.img", "/dev/block/bootdevice/by-name/persist");
but none of it worked.. so i was kinda hoping for a newer version.
btw..
Code:
mount | grep persist
shows that the persist partition is mounted RW.
if someone could do the following:
Code:
adb shell
su
su
cd /sdcard
mkdir persist
cd persist
rsync -av /persist .
exit
exit
then zip the content of the folder persist on your sdcard.. would like to try that too.
_HugoBoss_ said:
btw..
Code:
mount | grep persist
shows that the persist partition is mounted RW.
if someone could do the following:
Code:
adb shell
su
su
cd /sdcard
mkdir persist
cd persist
rsync -av /persist .
exit
exit
then zip the content of the folder persist on your sdcard.. would like to try that too.
Click to expand...
Click to collapse
Code:
/system/bin/sh: rsync: not found
Spannaa said:
Code:
/system/bin/sh: rsync: not found
Click to expand...
Click to collapse
instead of
Code:
rsync -av /persist .
type
Code:
cp -r /persist .
Thanks
_HugoBoss_ said:
instead of
Code:
rsync -av /persist .
type
Code:
cp -r /persist .
Thanks
Click to expand...
Click to collapse
Code:
cp: No /persist: Permission denied
Spannaa said:
Code:
cp: No /persist: Permission denied
Click to expand...
Click to collapse
Are you root?
su
su
_HugoBoss_ said:
Are you root?
su
su
Click to expand...
Click to collapse
Yes
Code:
C:\Users\spannaa\Desktop>adb shell
[email protected]:/ $ su
1|[email protected]:/ $ su
1|[email protected]:/ $ cd /sdcard
[email protected]:/sdcard $ mkdir persist
[email protected]:/sdcard $ cd persist
[email protected]:/sdcard/persist $ cp -r /persist .
cp: No /persist: Permission denied
1|[email protected]:/sdcard/persist $
Spannaa said:
Yes
Code:
C:\Users\spannaa\Desktop>adb shell
[email protected]:/ $ su
1|[email protected]:/ $ su
1|[email protected]:/ $ cd /sdcard
[email protected]:/sdcard $ mkdir persist
[email protected]:/sdcard $ cd persist
[email protected]:/sdcard/persist $ cp -r /persist .
cp: No /persist: Permission denied
1|[email protected]:/sdcard/persist $
Click to expand...
Click to collapse
use "whoami" to check if you're really root..
Code:
su
[email protected]:/ # whoami
root
Spannaa said:
Yes
C:\Users\spannaa\Desktop>adb shell
[email protected]:/ $ su
1|[email protected]:/ $ su
1|[email protected]:/ $ cd /sdcard
[email protected]:/sdcard $ mkdir persist
[email protected]:/sdcard $ cd persist
[email protected]:/sdcard/persist $ cp -r /persist .
cp: No /persist: Permission denied
1|[email protected]:/sdcard/persist $
Click to expand...
Click to collapse
You don't have root access dude, the " 1| " means that an error occurred. Furthermore, check your prompt, still " $ " instead of " # " .
Got there in the end...
Code:
C:\Users\spannaa\Desktop>adb shell
[email protected]:/ $ su
[email protected]:/ # su
[email protected]:/ # cd /sdcard
[email protected]:/sdcard # mkdir persist
[email protected]:/sdcard # cd persist
[email protected]:/sdcard/persist # cp -r /persist .
cp: product_calib_ref1.dat: Function not implemented
cp: product_calib_ref2.dat: Function not implemented
cp: product_calib_ref3.dat: Function not implemented
cp: unit_calib_ref1.dat: Function not implemented
cp: unit_calib_ref2.dat: Function not implemented
cp: unit_calib_ref3.dat: Function not implemented
cp: mixer_paths.xml: Function not implemented
cp: sw_calib.dat: Function not implemented
1|[email protected]:/sdcard/persist #
Let me know when you've grabbed the attached zip and I'll delete it
Spannaa said:
Got there in the end...
Code:
C:\Users\spannaa\Desktop>adb shell
[email protected]:/ $ su
[email protected]:/ # su
[email protected]:/ # cd /sdcard
[email protected]:/sdcard # mkdir persist
[email protected]:/sdcard # cd persist
[email protected]:/sdcard/persist # cp -r /persist .
cp: product_calib_ref1.dat: Function not implemented
cp: product_calib_ref2.dat: Function not implemented
cp: product_calib_ref3.dat: Function not implemented
cp: unit_calib_ref1.dat: Function not implemented
cp: unit_calib_ref2.dat: Function not implemented
cp: unit_calib_ref3.dat: Function not implemented
cp: mixer_paths.xml: Function not implemented
cp: sw_calib.dat: Function not implemented
1|[email protected]:/sdcard/persist #
Let me know when you've grabbed the attached zip and I'll delete it
Click to expand...
Click to collapse
Yeah, downloaded it.. thanks!
Gonna play with it. Thanks!!
Spannaa said:
Got there in the end...
Code:
C:\Users\spannaa\Desktop>adb shell
[email protected]:/ $ su
[email protected]:/ # su
[email protected]:/ # cd /sdcard
[email protected]:/sdcard # mkdir persist
[email protected]:/sdcard # cd persist
[email protected]:/sdcard/persist # cp -r /persist .
cp: product_calib_ref1.dat: Function not implemented
cp: product_calib_ref2.dat: Function not implemented
cp: product_calib_ref3.dat: Function not implemented
cp: unit_calib_ref1.dat: Function not implemented
cp: unit_calib_ref2.dat: Function not implemented
cp: unit_calib_ref3.dat: Function not implemented
cp: mixer_paths.xml: Function not implemented
cp: sw_calib.dat: Function not implemented
1|[email protected]:/sdcard/persist #
Let me know when you've grabbed the attached zip and I'll delete it
Click to expand...
Click to collapse
At least it seems to contain more data, but i can't seem to get it fully working.
Could you perhaps do the following from TWRP:
advanced -> terminal
then type
Code:
cd /sdcard
dd if=/dev/block/bootdevice/by-name/persist of=persist.dd.img
exit
Then from android, grab the persist.dd.img and share it with me?
_HugoBoss_ said:
At least it seems to contain more data, but i can't seem to get it fully working.
Could you perhaps do the following from TWRP:
advanced -> terminal
then type
Code:
cd /sdcard
dd if=/dev/block/bootdevice/by-name/persist of=persist.dd.img
exit
Then from android, grab the persist.dd.img and share it with me?
Click to expand...
Click to collapse
Done.
Spannaa said:
Done.
Again, let me know when you've downloaded it.
Click to expand...
Click to collapse
Thanks A LOT.
SENSORS WORK...
but hold your horses.. Couple of things i find right away..
First boot: it doesn't recognize SIM cards anymore.. Second boot, they are recognized.
Then: when i switch to MTP (file transfer), phone reboots.
So have to see whether it's all stable or not.
Delete the attachment for now.. i'll work on it a couple of days and let you know.
Again, thanks a lot!!
Proof:
Ok, at this point i'm not sure what is related and what is not anymore.
One thing i know for sure: simply copying the persist partition from one phone to another IS working, however the partitions holds some device- (like mac addresses) and maybe even some user-specific information. So it would not be right to start sharing that in the wild.
But while experimenting with the data, i found myself in a pretty f*cked up situation where there was no booting OS anymore and the Oneplus told me the bootloader was unlocked but refused to flash files trough fastboot anymore. Basically a dead phone.
Thank god i created a nandroid (full TWRP) backup and copied it to my laptop.
Long story short: i needed to perform a full repair of my phone and started looking for brick-guides.
The following worked for me AND magically repaired my persist partition too.
Steps to take:
- perform a full TWRP backup of your phone and copy it to your computer (don't keep it ON the phone!)
- also backup everything on your internal memory (sdcard) that is worth keeping. This process will also wipe your internal memory.
- Download the files from this guide. I've used method 3. The others may work. 3 worked for me.
- shutdown your phone
- press volume up and then connect the usb cable. Only volume up!
- the phone won't really power on, but your computer will detect a device. Use the driver you downloaded from the page above.
- When the driver is installed, start the MSM8994DownloadTool.exe as administrator (right click: run as administrator!)
- It's chinese or some language i can't uderstand. But just hit the start button. Some green text will show the progress.
- In the end, your phone will ask you if it's OK to wipe all user data. I did.
- And then it boots to Oxygen OS.
From this point on it's back to normal business
- flash custom recovery trough fastboot
- copy your TWRP backup back to the phone
- restore the backup
- Oh and don't forget: all your firmwares are OLD now. So in order to run CM13 or some other marshmellow rom, you also need to flash that "Switch_tOS3_H2OSMMv3.zip" like you did before!
- restore any other data to your internal memory (sdcard)
There ya go. Fully working system with sensors and all
Good luck!
So after you did the Qualcomm recovery does cpuz still show the sensors as uncalibrated like the screenshot in post 17. I have some issues with my screen rotation as randomly it was not switch to landscape. My cpuz shows gyroscope calibrated and uncalibrated, any way to calibrate gyroscope without that Qualcomm recovery? I had to go through that process in March.
Dude_Virus said:
So after you did the Qualcomm recovery does cpuz still show the sensors as uncalibrated like the screenshot in post 17. I have some issues with my screen rotation as randomly it was not switch to landscape. My cpuz shows gyroscope calibrated and uncalibrated, any way to calibrate gyroscope without that Qualcomm recovery? I had to go through that process in March.
Click to expand...
Click to collapse
It still says so yes. Even now, after more than a month.
However, everything still works fantastic. No issues whatshowever.