• 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...

mainefungi said:
/data and /cache are both present, but neither show any sub-directories.
Click to expand...

okay one more time,

what all is listed under the by-num folders of each sdcc.1 and 3???

if only a few are listed under each one, then i can narrow down the system's actual mount point
 
/dev/block/platform/msm_sdcc.1/by-num/

p1

/dev/block/platform/msm_sdcc.3/by-num/

p1
p11
p12
p13
p14
p15
p16
p17
p18
p19
p2
p20
p21
p22
p23
p3
p4
p5
p6
p7
p8
p9
 
tell me what happens when you try to install this.

delete all other the other files. then rename this to update.zip and tell me the result

one of three commands has to work for mounting the system in recovery. all this update does is mount the system and unmount. i need to know if it was the mount commands making it fail or what followed it.
 

Attachments

run

mount|grep /system

i'm sure i already know the output but just humor me please.

this is the last thing i can do tonight. i may go buy one anyway tomorrow so i've got one to work with...
 
mount|grep /system

returns

/system/bin/sh: grep: not found
[1] + Stopped (signal) mount |
Done (127) grep /system
127|shell@android:/ $
 
mainefungi said:
mount|grep /system

returns

/system/bin/sh: grep: not found
[1] + Stopped (signal) mount |
Done (127) grep /system
127|shell@android:/ $
Click to expand...

try this root method here:

Root MANY ANDROID! [Upd: 20.11.2013] - Added Z1 Root - xda-developers

it uses an adb restore exploit that might work for this phone.

when you run the script choose the first option.

this is just something else to humor me for the night. there's a chance it could very well work with this device though. it was going to be the first thing i tried for rooting the phone besides what all you've been doing for me.
 
Save you the time waiting... I already gave that method a whirl at someone else's suggestion... Sadly, it did not work.

Would you like me to PM you my email address so you can send several files files I can try? I will be in and out all day tomorrow.
 
If I had to guess..

179 22 2490368 mmcblk0p22

or one of these

179 32 3813376 mmcblk1
179 33 3812352 mmcblk1p1

would be the system partition... based on size...

Want to try p22 for giggles before saying good night?
 
mainefungi said:
If I had to guess..

179 22 2490368 mmcblk0p22

or one of these

179 32 3813376 mmcblk1
179 33 3812352 mmcblk1p1

would be the system partition... based on size...

Want to try p22 for giggles before saying good night?
Click to expand...

p22 is data, that's obvious from the output of the mount command

p19 should be system, which is obvious from the mount command as well

for some reason, it's just not working. something is preventing this command from completing, i just can't figure out what. there is a possibility that it's another one other than p19, but i don't have any doubts that p22 is data

yeah, pm me an email address and i'll give you mine in return.

thanks for all the help. i'll be back at it soon enough
 
/dev/block/platform/msm_sdcc.1/

255kg7a.png


and

/dev/block/platform/msm_sdcc.3/

in69v9.png

2yu0rdh.png

2moe8zn.png
 
Cool - I will be watching/testing.... I have been using the valet for a couple of weeks now - although under-powered - it does everything I need it to do.

thanks
sam
 
samcoinc said:
Cool - I will be watching/testing.... I have been using the valet for a couple of weeks now - although under-powered - it does everything I need it to do.

thanks
sam
Click to expand...

I think it is a bit under powered, but not too bad. If we can get it rooted we can look "under the hood" and see what can be done to tune it up a bit...
 
Agreed! (I meant 'a bit underpowered'..) I have been running the nook color rooted with the latest jelly bean. It actually runs faster than the previous versions on that hardware - which is quite old. So rooting - and then maybe some rom options would be cool.

sam

mainefungi said:
I think it is a bit under powered, but not too bad. If we can get it rooted we can look "under the hood" and see what can be done to tune it up a bit...
Click to expand...
 
Hey Stayboogy... I have been looking at various updater scripts, and I came accross the following mount command....

mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system", "/system");

Now, we do not have a by-name directory, but we do have a by-num directory (and we know p19 is /system... Of course, that device had an Ti Omap processor, while the Valet has a SDCC compatible qualcomm processor...

I was wondering if it would be worth while to try it again using the following mount format?

mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.3/by-num/p19", "/system");

Thoughts?
 
mainefungi said:
Hey Stayboogy... I have been looking at various updater scripts, and I came accross the following mount command....

mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system", "/system");

Now, we do not have a by-name directory, but we do have a by-num directory (and we know p19 is /system... Of course, that device had an Ti Omap processor, while the Valet has a SDCC compatible qualcomm processor...

I was wondering if it would be worth while to try it again using the following mount format?

mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.3/by-num/p19", "/system");

Thoughts?
Click to expand...

if you look at the updater scripts in my update packages its already been done.

trust me i know whats up

theres a hitch thats keeping the recovery from accepting the package.
 
I tried Framaroot yesterday, and that failed also. I even tried OneClickRoot and Motochopper (which works on the Qualcomm version of the Galaxy S4.

I need to run back out to pick up a friend, then I will be home. Like 30 minutes... So 9:30 PM EST.

Is it possible they use a non-standard signature for their updates? And if so, is there a way to fish out the signing key?
 
mainefungi said:
I am back... Will be up for a bit. If you have any ideas we can give them a try.
Click to expand...

rename to update.zip and try to install this from recovery

let me know what happens.

if it works, check to see if there is a file named boot.img on your sdcard afterward, and if so, upload it please
 

Attachments

stayboogy said:
rename to update.zip and try to install this from recovery

let me know what happens.

if it works, check to see if there is a file named boot.img on your sdcard afterward, and if so, upload it please
Click to expand...



No go, still get the "Installation Aborted" immediately after verify.
 
mainefungi said:
No go, still get the "Installation Aborted" immediately after verify.
Click to expand...

try this one.

signed with platform keys this time.

i'm positive it's not the mount command that's preventing it working. it's something to do with the signature or update-binary

rename to update.zip--maybe give it some time before rebooting into recovery to make sure it gets renamed

let's see what happens
 

Attachments

stayboogy said:
try this one.

signed with platform keys this time.

i'm positive it's not the mount command that's preventing it working. it's something to do with the signature or update-binary

rename to update.zip--maybe give it some time before rebooting into recovery to make sure it gets renamed

let's see what happens
Click to expand...

Yeah I always give it a couple of minutes to finish the rename. This one was the same way. Its not a name issue... It finds and opens and begins to verify the package... Then just aborts...

What gets me is there are no status errors, which would give us more clues to what is going on. I would think if it was a signature issue it would give an error of some sort.

Anyway, I am headed to bed. I will be in and out all day tomorrow if you want to try anything else.

Thanks
 
You must log in or register to reply here.
Back
Top Bottom