• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root i'll help find a root method if...

stayboogy

stayboogy

Android Expert
i'll be glad to help find a root method if someone can give me some info on the phone.

i'm wanting to buy one, but i don't want to buy it if i can't root it. so let's get root.

info i need:

1. is there a locked bootloader???

--to find out, make sure usb debugging is enabled in your phone settings; ie, settings, system, developer options, usb debugging
--then download this file sdk-tools, unzip it, open a command window from within this folder and type adb reboot-bootloader
--if all you get is <waiting for device> then just close the command window
--if the phone does reboot into the bootloader, then in the same command window type fastboot oem unlock
--if a warning comes up, just accept it, and now your bootloader is unlocked--there is a chance you could lose all your data, so back it up first


2. is there a recovery, and if so what is it???

--to find out, download the zip from above, open a command window within that folder, then type adb reboot recovery
--give me some info on what type of recovery comes up--even a picture would be better


Then we'll go from here. someone please do this that has this phone. the quicker i get this info, the quicker a root can be found. it's quite possible one of the many jelly bean root processes could work. i assume the reason no one has found a working one is because of an incompatible su file maybe, but i'm not sure.
 
Hi, thank you for offering your help...

Fortunately I already have sdk-tools set up.

1. adb reboot-bootloader does not hang at <waiting for device>, but it does not bring it to the bootloader screen. Instead, it simply reboots the phone as a normal reboot. Because of this, I am unable to properly test the fastboot oem unlock command.

2. Recovery comes up with the standard "android system recovery <3e>" screen. Below is a picture of my recovery screen.
a3wg2ffwl
 
mainefungi said:
Hi, thank you for offering your help...

Fortunately I already have sdk-tools set up.

1. adb reboot-bootloader does not hang at <waiting for device>, but it does not bring it to the bootloader screen. Instead, it simply reboots the phone as a normal reboot. Because of this, I am unable to properly test the fastboot oem unlock command.

2. Recovery comes up with the standard "android system recovery <3e>" screen. Below is a picture of my recovery screen.
a3wg2ffwl
Click to expand...


this means there is not a standard bootloader and the system can be easily modified and new .img flashed after root

any standard jelly bean root should work for this phone then.

but if not, then there are other ways.

i need some info about the /dev partition
--download this and install it on the phone com.lonelycatgames.Xplore-1
--go to the /dev partition and take a screenshot and post it

with the proper information i can create a root update.zip for this phone

other things to try as well

--get into an adb shell on the phone with your pc
--type cat proc/partitions and paste the output here; if nothing move on
--if above doesn't work, type cat proc/mtd and paste the output here
--regardless if either of these work, run mount from terminal and paste the output here--this is the most important because with it i might get all the info i need to make an update.zip

and thank you for replying to my post. with your help rooting might be easier than i thought...
 
mainefungi said:
This is a large list, but here is the pic that shows all the folders. If you need more let me know...

View image: Screenshot 2013 11 26 22 09 21
Click to expand...

sorry about that, i remembered there are better ways to get the info i need

run these three commands separately from an adb shell

mount
--and paste the results--this is most important and may be all i need

cat proc/partitions
--and paste the results if any

cat proc/mtd
--and paste results if any

we're almost there dude!!!!!!!!!!
 
shell@android:/ $ cat proc/partitions
cat proc/partitions
major minor #blocks name

7 0 5229 loop0
179 0 3817472 mmcblk0
179 1 8192 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 1 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 32768 mmcblk0p9
179 10 16384 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 65536 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 16384 mmcblk0p17
179 18 16384 mmcblk0p18
179 19 524288 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 307200 mmcblk0p21
179 22 2490368 mmcblk0p22
179 23 204800 mmcblk0p23
179 32 3813376 mmcblk1
179 33 3812352 mmcblk1p1
254 0 5229 dm-0
 
shell@android:/ $ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p19 /system ext4 ro,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.3/by-num/p22 /data ext4 rw,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p10 /persist ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p21 /cache ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /mnt/asec/com.doodle.main-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/vold/179:33 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
shell@android:/ $
 
There, sorry... I had to fix the window size for the last one... LOL...

Guess I should just be happy windows 8 has a command prompt still.
 
stayboogy said:
okay i'll have you zips to test in the stock recovery shortly, hang tight
Click to expand...

Okay, If I recall, the chances of a brick should be zip for that method...

It only adds the su binary and superuser.apk to the system and if it doesn't work it will be because the of the signing of the zip. Am I right?
 
mainefungi said:
Okay, If I recall, the chances of a brick should be zip for that method...

It only adds the su binary and superuser.apk to the system and if it doesn't work it will be because the of the signing of the zip. Am I right?
Click to expand...

no.

proper mount command in updater-script, first

the proper updater-binary in the update, second

the right su binary in the update, third

i'll explain it all after we test these and get root. it'll happen one way or another.

should be no chance of brick. might lose your userdata, so backup contacts--but i say i think the chances of this are nill too cause zte doesn't add all that nonsense to the standard google code
 
It says...

-- Install /sdcard ...
Finding updage package...
Opening update package...
Verifying update package...
Installation aborted.

No other errors.
 
mainefungi said:
It says...

-- Install /sdcard ...
Finding updage package...
Opening update package...
Verifying update package...
Installation aborted.

No other errors.
Click to expand...

on the right track at least.

try this and post error if any. if no error and it installs, we need to verify the su file works

always rename to update.zip and verify it gets copied completely


valet-root-update2
 
Yes, update.zip method has not changed since I used to run cyanogenmod on the motorola droid.

Attempt number 2 got the same message as before.
 
mainefungi said:
Easy...

/dev/block/platform/msm_sdcc.1
/dev/block/platform/msm_sdcc.3
Click to expand...

list even further as well then. this info will help me figure out which is right for mounting the /system partition

/dev/block/platform/msm_sdcc.1/

and

/dev/block/platform/msm_sdcc.3/
 
also, go to /cache/recovery/last_log and paste it's contents if it exists at all

if not there, then go to /data/local/tmp/last_log
 
You must log in or register to reply here.
Back
Top Bottom