[Completed] [Q] IceFox Razor: Root shell but not Root permission - XDA Assist

Hi guys,
short backstory:
I was asked to look for a smartphone to use outdoor, I (unfortunately) picked the IceFox Razor and now we got a bunch of them. Unluckily, I later noticed that those phones come with malware (or something similar), they download and install apps on their own. I couldnt fix that by myself, even after hours of trying.
What I've tried so far:
I gained root access in the shell using the MTK Droid tool and SP flash tool, but guess what: neither the SuperSU nor any other app actually have root permissions. I even tried different SuperSU versions.
Since I am not a programmer and since I only have very little knowledge of Linux, I am stuck now. I dont even know what to actually search for in the webs.
Hardware and software:
Code:
Hardware : MT6582
Model : RAZOR
Build number : ICEFOX_RAZOR_20140919
Build date UTC : 20140919-115900
Android v : 4.4.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V39, 2014/08/06 02:14
Kernel v : 3.4.67 ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP Fri Sep 19 19:56:16 CST 2014
I appreciate any hint and help!

Hi, thank you for using XDA Assist. I can't find anything specific to your device. but I did find this for your chip set, http://forum.xda-developers.com/showthread.php?t=2574315 It may work on your device, but obviously, no guarantees.

Related

[VIDEO] First Look at Cincinnati Bell Official Froyo

Here it is:
http://www.youtube.com/watch?v=krAvfyQZX4o
Enjoy.
Thanks, we all love your videos. Looking forward to more!
Thanks man!
I looked over the internet and fount a msi file. Hopefully that's the official file.
I really appreciate your tutorial and letting us know such upgrade exist. By the time I have watched this tutorial, I have already installed KhalPower's SteelEpicBlueV4.
Thanks for sharing!
athlon866 said:
Is there a link to download?
Click to expand...
Click to collapse
It is in this thread back a few pages. Titled something like "It's Here...."
Stripped cbw.zip and current CinBell zip
Hi.
reverendkjr, did you modify the imgs in your stripped rom package? The cbw.zip linked in the youtube video isn't the same as the current cbw.zip found in Cincinnati Bell's xt720_files.zip. Or maybe they've updated their rom? I downloaded it today. md5sum successfully verifies both sets of files, but the sums are different between the zips.
*.md5 files from my cbw.zip:
Code:
3f28c64431c12075f8d1bcaae8f5ee51 boot.img
b54670747a8d8daeddc7eafee75c10f7 system.img
*.md5 files from reverendkjr's cbw.zip:
Code:
2c8a3b5452f9eddfa46217e61679d0d7 boot.img
7937a9c06a7d9794f3ba736ea21c7058 system.img
This is how I extract cbw.zip:
Code:
wget http :// www ultimobile net/XT720_Files/xt720_files.zip
7z e ACSetup.msi _883B25C497AFEB46BFAEB0A3A4F6A8FF
7z e _883B25C497AFEB46BFAEB0A3A4F6A8FF _BF775DB53FAC4E61B74E061A2095B331
mv _BF775DB53FAC4E61B74E061A2095B331 cbw.zip
I don't know how to open .img files, so I can't dig deeper.
Revs zip only contains nandroid image and a couple small things can't remember exactly, and the one from Cincinnati bell contains a whole bunch of crap, that's why theirs is like 3 times the size as revs.
pydave said:
I don't know how to open .img files, so I can't dig deeper.
Click to expand...
Click to collapse
That's quite interesting. FYI to extract .img files, use unyaffs. I think I saved the msi from the day they released it. If I can find it, I'll compare the sums.
pydave said:
Hi.
reverendkjr, did you modify the imgs in your stripped rom package? The cbw.zip linked in the youtube video isn't the same as the current cbw.zip found in Cincinnati Bell's xt720_files.zip. Or maybe they've updated their rom? I downloaded it today. md5sum successfully verifies both sets of files, but the sums are different between the zips.
*.md5 files from my cbw.zip:
Code:
3f28c64431c12075f8d1bcaae8f5ee51 boot.img
b54670747a8d8daeddc7eafee75c10f7 system.img
*.md5 files from reverendkjr's cbw.zip:
Code:
2c8a3b5452f9eddfa46217e61679d0d7 boot.img
7937a9c06a7d9794f3ba736ea21c7058 system.img
This is how I extract cbw.zip:
Code:
wget http :// www ultimobile net/XT720_Files/xt720_files.zip
7z e ACSetup.msi _883B25C497AFEB46BFAEB0A3A4F6A8FF
7z e _883B25C497AFEB46BFAEB0A3A4F6A8FF _BF775DB53FAC4E61B74E061A2095B331
mv _BF775DB53FAC4E61B74E061A2095B331 cbw.zip
I don't know how to open .img files, so I can't dig deeper.
Click to expand...
Click to collapse
CBW's has a flashing tool that makes it easier for someone who doesn't know what they are doing to flash it easier, it does the root and openrecovery steps automatic so that's why it's much bigger. We just use need the nandroid file here as we are mostly already rooted and have open recovery installed. In other words cbw package has training wheels lol
LibertyMonger said:
CBW's has a flashing tool that makes it easier for someone who doesn't know what they are doing to flash it easier, it does the root and openrecovery steps automatic so that's why it's much bigger. We just use need the nandroid file here as we are mostly already rooted and have open recovery installed. In other words cbw package has training wheels lol
Click to expand...
Click to collapse
pydave isn't saying the size is different. The files have changed.
md5sums compute identifying strings (i.e. 2c8a3b5452f9eddfa46217e61679d0d7) that can be used as fingerprints. If the md5sums are different, then the content of files is different. What pydave has found is that the nandroid files don't match what rev posted anymore. So, possibly ultimobile's modified or updated something. The md5sum of the system.img could easily have changed simply by rev making making a backup nandroid and posting it. But, there's no way we can change the boot.img because of the bootlock.
What's strange is that the md5 sum of the boot.img again doesn't match anything I've seen before and it's different from the first one that CBW shipped.
Code:
7e9aed3341102a79851d4d7a3286997b STR_U2_01.18.2/GAS_ASIA_USASHLSTBRTINT_P027/boot.img
eff22955e8e91eb19545a3af39973934 STR_U2_01.1E.0/GAS_EMEA_UCASHOTBRTLRTCEE_P001/boot.img
eff22955e8e91eb19545a3af39973934 STR_U2_01.1E.0/GAS_EMEA_UCASHOTBRTLRTGB_P021/boot.img
fb17ae0297d51862ca9804e22c6940f2 STR_U2_01.1E.2/GAS_ASIA_USASHLSTBSTARSG_P019/boot.img
e5b21dfe793c8116a02ec486fa867afc STR_U2_02.1E.0/GAS_EMEA_UCASHOTBRTLRTFR_P018/boot.img
e5b21dfe793c8116a02ec486fa867afc STR_U2_02.1E.0/GAS_EMEA_USASHOTBRTLRTIT_P001/boot.img
cc81052ecaac38c81e9c373806f8b6de STR_U2_03.20.1/GAS_ASIA_USASHLSTBRTRU_P012/boot.img
8e5d0e3b28d020dca7aed72d3811e8e9 STR_U2_04.1E.1/GAS_NA_NACBW_P011/boot.img
8e5d0e3b28d020dca7aed72d3811e8e9 STR_U2_04.1E.1/GAS_NA_NAREG_P011/boot.img
I'm going to see if I can find out some more about this kernel. I'm still looking for the msi I downloaded the day it was released by CBW to compare.
Mioze7Ae said:
pydave isn't saying the size is different. The files have changed.
md5sums compute identifying strings (i.e. 2c8a3b5452f9eddfa46217e61679d0d7) that can be used as fingerprints. If the md5sums are different, then the content of files is different. What pydave has found is that the nandroid files don't match what rev posted anymore. So, possibly ultimobile's modified or updated something. The md5sum of the system.img could easily have changed simply by rev making making a backup nandroid and posting it. But, there's no way we can change the boot.img because of the bootlock.
What's strange is that the md5 sum of the boot.img again doesn't match anything I've seen before and it's different from the first one that CBW shipped.
Code:
7e9aed3341102a79851d4d7a3286997b STR_U2_01.18.2/GAS_ASIA_USASHLSTBRTINT_P027/boot.img
eff22955e8e91eb19545a3af39973934 STR_U2_01.1E.0/GAS_EMEA_UCASHOTBRTLRTCEE_P001/boot.img
eff22955e8e91eb19545a3af39973934 STR_U2_01.1E.0/GAS_EMEA_UCASHOTBRTLRTGB_P021/boot.img
fb17ae0297d51862ca9804e22c6940f2 STR_U2_01.1E.2/GAS_ASIA_USASHLSTBSTARSG_P019/boot.img
e5b21dfe793c8116a02ec486fa867afc STR_U2_02.1E.0/GAS_EMEA_UCASHOTBRTLRTFR_P018/boot.img
e5b21dfe793c8116a02ec486fa867afc STR_U2_02.1E.0/GAS_EMEA_USASHOTBRTLRTIT_P001/boot.img
cc81052ecaac38c81e9c373806f8b6de STR_U2_03.20.1/GAS_ASIA_USASHLSTBRTRU_P012/boot.img
8e5d0e3b28d020dca7aed72d3811e8e9 STR_U2_04.1E.1/GAS_NA_NACBW_P011/boot.img
8e5d0e3b28d020dca7aed72d3811e8e9 STR_U2_04.1E.1/GAS_NA_NAREG_P011/boot.img
I'm going to see if I can find out some more about this kernel. I'm still looking for the msi I downloaded the day it was released by CBW to compare.
Click to expand...
Click to collapse
Are you looking fro CBs installation file (xt720_files.zip) or just the nandroid image?
3rdstring said:
Are you looking fro CBs installation file (xt720_files.zip) or just the nandroid image?
Click to expand...
Click to collapse
I was looking for xt720_files.zip. I found it. They are different, but I'm just starting to peel the skin. More soon.
Mioze7Ae said:
I was looking for xt720_files.zip. I found it. They are different, but I'm just starting to peel the skin. More soon.
Click to expand...
Click to collapse
Fudge. I just accidentally deleted it.
Anyway, the difference in the system.img is some new app called umFramework.apk (um presumably short for ultimobile).
The new kernel is:
3f28c64431c12075f8d1bcaae8f5ee51 boot.img
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Tue Jul 13 20:54:25 IST 2010
The previous one was:
2c8a3b5452f9eddfa46217e61679d0d7 boot.img
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Wed Jun 23 22:39:35 IST 2010
The other ones I've seen are:
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Thu May 27 16:17:00 IST 2010
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Tue Jul 13 17:19:35 IST 2010
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Tue Jul 13 17:19:35 IST 2010
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Thu Aug 5 16:27:41 IST 2010
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Tue Jul 13 20:54:25 IST 2010
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Tue Jul 13 20:54:25 IST 2010
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Wed Aug 4 22:22:08 IST 2010
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Tue Jul 20 01:36:37 IST 2010
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Tue Jul 20 01:36:37 IST 2010
So, the compile date and time matches the italian and french builds now but the md5sum doesn't.
Mioze7Ae said:
Anyway, the difference in the system.img is some new app called umFramework.apk (um presumably short for ultimobile).
Click to expand...
Click to collapse
Nobody install this attachment!
Now that's out of the way, can someone else look at the code (apktool) and tell me if it's doing what I think it's doing? My interpretation is it collects a bunch of information about the phone and SIM and uploads it to:
http://www.ultimobile.net/androidtracker/androidtracker/service1.asmx/Tracker
It may be harmless (or even beneficial for CBW users) so that CBW can do QA and monitor it's network quality. Dunno. See also:
http://www.ultimobile.net/androidtracker/androidtracker/default.aspx
In any case, I'm not sure I'd want this on my phone if I wasn't a CBW customer.
I decompiled with dex2jar and got the code from jd-gui.
Looks to me like it's doing what you described Mioze7Ae:
umFramework.apk contains a service that's started on boot. The service tries to upload some info and quits when upload completes (so it should only upload once per boot). Here's the Android documentation for what it's uploading.
getDeviceId: Returns the unique device ID, for example, the IMEI for GSM and the MEID or ESN for CDMA phones.
getDeviceSoftwareVersion: Returns the software version number for the device, for example, the IMEI/SV for GSM phones.
getSimOperator: Returns the MCC+MNC (mobile country code + mobile network code) of the provider of the SIM. 5 or 6 decimal digits.
Click to expand...
Click to collapse
I guess they watched reverendkjr's video and wanted to count the noncustomers who are flashing
My file was the original nandroid that they put out there with all of their crap added and instructions from the day it was released. I just yanked out the zip file and posted it elsewhere. It sounds to me like they have changed it after the fact.
Very interesting...
Hi Reverendkjr,
Thanks for all your videos. I have learned a lot from those videos.
I just want to know which ROM has a higher quandrant count: WanHu or CBW?
Thanks!
hermit_sim said:
Hi Reverendkjr,
Thanks for all your videos. I have learned a lot from those videos.
I just want to know which ROM has a higher quandrant count: WanHu or CBW?
Thanks!
Click to expand...
Click to collapse
+1 the videos from Rev help me a lot!
Same question for me, what is the best rom for XT720
Sorry for my bad english, I'm not English speaking
Hi all,
Same question for me, what is the best rom for XT720 in terms of stability?
Thank you
hermit_sim said:
Hi Reverendkjr,
Thanks for all your videos. I have learned a lot from those videos.
I just want to know which ROM has a higher quandrant count: WanHu or CBW?
Thanks!
Click to expand...
Click to collapse
I havent tried the CBW froyo but i am currently using the wanhu steelblue optimized and i have a quadrant score of around 1000 to 1100 when overclocked to 1000mhz 66vsel. But i have understood from other ppl in this forum that quadrant scores almost count for nothing and can be easily manupilated. (eg: increase read write speed of sd card, use memory optimizer for more RAM, etc...) hope that helps

[Q] Can't root, none of the methods worked.(4.0.4 ICS Tab)

Hello,
First of all I'd like to share you my device information:
Modell: M-Tech aTab 9.7 IPS
Android: 4.0.4
Kernel: 3.0.8+
SMP PREEMPT Wed Aug 29 00:54:17 CST 2012
Build: rk30_ics_v2.23.00
IMM76D.20120829.005419
That would be all about my Tab.
I recently bought it and I wanted to root it but none of the methods worked for me (Bin4ry's, SuperOneClick, and I can't even reboot inty recovery)
About adb shell.. Permissions are denied for "Reboot recovery" and I can't find any help for my device.
Please help. I'm kind of noob when it's time to do something with a device that is not known for many.
I've been researching and trying out different ways for 2 days now and nothing.
Thanks in advance. Coolby

[Q] Android Extreme Note ROM

My phone just crashed, it's restart the system several time when i try to start the phone. A month ago, i use root my phone to install some application but when i entering rooting explorer mode on file "System", accidentally i change the system folder attribut to rw-- r--- r--- the phone going freeze for several minute then restart..after that, the phone won't to start anymore.
I had enter the factory mode, restore user data from last backup, it's still not working. Clearing Flash not help me too, it's still fail to start. Please anybody can help me how to resolve this issue??:crying:
Here is the phone version from factory mode :
BB Chip : MT6573
MS Board. : e1108_v73_jbl1flash8p4_extreme
IMEI1 : 355333685002111
IMEI2 : 355333685002129
Modem Ver. : MAUI.11AMD.W11.37.SP.V17.F1. 2012/03/20 18:09
Bar code : 0417JL5-8_024237
Build Time : 2012 06 27 17:44:00 CST
UBoot Ver. : 2010.06
Kernel Ver. : 2.6.35.7 ([email protected]) (gcc version 4.4.3 (GCC) #1 PREEMPT Wed Jun 27 17:39:38 CST 2012
Android Ver. : 2.3.6
SW Ver. : ALPS.GB.FDD2.MP.V4.5
Custom Build Verno. : 1340789993
LcmCam Info : Camera Main : ov5640raw, Sub : hi704yuv Lcm : RX_50NT_323A
Touch Panel : FT5406

[Q] [HELP] Messed up My Droid After installing Busybox to system/lib

I'm a newbie to android platform. I came to know from a source that installing busy box upgrades kernel.
So i foolishly installed busybox to System/lib through smartintall. :crying: After that Accidentally i Unrooted my device (yeah it was rooted already wid rootgenius kingtool app). Now i'm not able to root itagain nor i'm able to restore it. if i try to restore sum of the sensors misbehave. :crying: (if i hdn't made a backup)
Pls expersts help me regain root access to my droid. And restore replaced system/lib files.
Here is my Device Details.
Hardware : MT6577
Model : B63
Build number : e1911_v77_mg_s05g_9p017_6628_20121229
Build date UTC : 20121229-054615
Android v : 4.1.1
Baseband v: MAUI.11AMD.W12.22.SP.V15, 2012/10/16 13:11
Kernel v : 3.4.0 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP Thu Dec 27 19:50:40 CST 2012
Kernel Version 3.4.0
Total ram 500mb.

[Completed] [Q] Mediatek tablet has watermark after flashing CWM backup

Hello, my device is a 10.1" Mediatek tablet, marketed as Jlinksz model D101. Tablet info from MTK Droid Root & Tools v2.5.3b:
Hardware : MT6572 (MT6582 is Fake!)
Model : D101
Build number : D101_vCC076_20140812
Build date UTC : 20140812-063145
Android v : 4.2.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V1.P5, 2014/04/21 14:41
Kernel v : 3.4.5 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP Wed Aug 13 10:58:17 CST 2014
Uboot build v : ----- should be root shell
LCD Driver IC : 1-d101_dpi_lvds
It is running the stock 4.2.2 rom. I rooted it with Framaroot then added CWM. I made & have a MTK Droid Root & Tools system & NAND backup (following the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2160490), & two CWM backups. My ultimate goal is to swap the SD to alleviate the limited internal storage. I edited the build.prop and rebooted to find that my SD card wasn't found. At that point I decided to flash my CWM backup for the first time. Since flashing my CWM backup I have a red watermark across all system screens "Copyright (c) Jlink Inc. All rights reserved!". When the device first boots the Mediatek logo appears briefly, then the word "Android", then the system. The Mediatek logo & Android screens aren't affected by the watermark. All other screens, regardless of an application running or not, have the watermark. I've searched the forums and haven't found people with the same problem. This watermark issue seems somewhat similar to http://forum.xda-developers.com/showthread.php?t=1917262, but I don't know that the solution would be applicable as the device is different. I've been searching "watermark", perhaps a different term is more appropriate? Please push me in the right direction as to how I might be able to remove this watermark. Thanks much!
Hi,
You could ask for thoughts in the similar watermark thread you linked, or try asking for help here,
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck!

Categories

Resources