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

Root Public Mobile

Already tried, didn't work for automatic root. It probably requires a password while a command is being issued or something. Last year there was a backdoor root exploit that zte accidentally left in a phone and it require a special permission upon entering the command to execute.
 
Even when rooted, the unroot option does not work. So that's why I think its using a different root method. Or maybe it just plain doesn't work with b11
 
its interesting though, why would that even be in the updater tools package for b09? wonder if it'll do the same for b11
 
Can you post the one you modified? I'm curious to see if it works on the public ics Rom...

EDIT: oh you tweaked your build.prop?
 
Got these two lists in the recovery fstabs
this one:
# mount point fstype device [device2]

/dbl emmc /dev/block/mmcblk0p1
/osbl emmc /dev/block/mmcblk0p2
/cefs emmc /dev/block/mmcblk0p5
/adsp emmc /dev/block/mmcblk0p8
/amss emmc /dev/block/mmcblk0p9
/emmcboot emmc /dev/block/mmcblk0p11
/boot emmc /dev/block/mmcblk0p12
/recovery emmc /dev/block/mmcblk0p13
/splash emmc /dev/block/mmcblk0p14
/system ext4 /dev/block/mmcblk0p15
/misc emmc /dev/block/mmcblk0p16 (mmcblk0p17)
 /cache ext4 /dev/block/mmcblk0p17 (mmcblk0p18)
/data ext4 /dev/block/mmcblk0p18 (mmcblk0p19)
/carrier ext4 /dev/block/mmcblk0p19 (mmcblk0p16)
/sdcard vfat /dev/block/mmcblk1p1

and this one:

/dbl emmc /dev/block/mmcblk0p1
/osbl emmc /dev/block/mmcblk0p2

/cefs emmc /dev/block/mmcblk0p5
/adsp emmc /dev/block/mmcblk0p8
/amss emmc /dev/block/mmcblk0p9
/emmcboot emmc /dev/block/mmcblk0p11

/boot emmc /dev/block/mmcblk0p12
/recovery emmc /dev/block/mmcblk0p13
/splash emmc /dev/block/mmcblk0p14
/system ext4 /dev/block/mmcblk0p15
/misc emmc /dev/block/mmcblk0p16 (mmcblk0p17)

/cache ext4 /dev/block/mmcblk0p17 (mmcblk0p18)
/data ext4 /dev/block/mmcblk0p18 (mmcblk0p19)
/carrier ext4 /dev/block/mmcblk0p19 (mmcblk0p16)

/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1


# /cefs emmc /dev/block/mmcblk0p5
# /cefs_alt emmc /dev/block/mmcblk0p6
# /dev/block/mmcblk0p7 persist

# /dev/block/mmcblk0p13 recovery.img
# /dev/block/mmcblk0p14 splash.img
# /dev/block/mmcblk0p15 system.img.ext4
# /dev/block/mmcblk0p16 MISC (this is a mistake is actually mmcblk0p17)
# /dev/block/mmcblk0p17 CACHE (this is a mistake is actually mmcblk0p18)
# /dev/block/mmcblk0p18 userdata.img.ext4 (this is a mistake and is actually mmcblk0p19)
# /dev/block/mmcblk0p19 carrier.img.ext4 (this is a mistake and is actually mmcblk0p16)

# /dev/block/mmcblk0p10 FOTA


So the files go a such:

adsp.mbn - mmcblk0p8
amss.mbn - mmcblk0p9
boot.img - mmcblk0p12
carrier.img.ext4 - mmcblk0p16
cefs.mbn - mmcblk0p5 **
cefs_null.mbn - mmcblk0p6 **
dbl.mbn - mmcblk0p1
emmc_appsboot.mbn - mmcblk0p11
EMMCBOOT.MBN - mmcblk0p11
fat.bin - *
fsbl.mbn - mmcblk0p3 **
osbl.mbn - mmcblk0p2
partition.bin - *
partition.mbn - mmcblk0p7 **
recovery.img - mmcblk0p13
splash.img - mmcblk0p14
system.img.ext4 - mmcblk0p15

* I think these are for the online updating tool but I'm not sure
** I'm speculating on these
 
Wouldn't it be for both OTA and online updating tool? They would still update the same partitions and call for the same block #
 
Something doesn't make sense here... can one of you post up your results for "cat /proc/partitions" I think are user data partitions are not in the same place...
 
That is weird... we have the same parttions.. but if you look at the fstabs, the userdata partition is marked as mmcblk0p18 but if you look at the block size, it is clearly mmcblk0p19 marked as carrier in the fstabs...???

The CWM you guys have is built from source?... Whoever made it, made it right... the Stock 3e recovery has a mistake in it... that why you get and error when you do a factory reset.. the mistake was rectified with the CWM...

Check the list I made yesterday.. I edited it...
 
smartmanvartan said:
That is weird... we have the same parttions.. but if you look at the fstabs, the userdata partition is marked as mmcblk0p18 but if you look at the block size, it is clearly mmcblk0p19 marked as carrier in the fstabs...???

The CWM you guys have is built from source?... Whoever made it, made it right... the Stock 3e recovery has a mistake in it... that why you get and error when you do a factory reset.. the mistake was rectified with the CWM...

Check the list I made yesterday.. I edited it...
Click to expand...

thats ZTE for ya, full of bullsh*t and mistakes lol
 
pretty much. that was confusing at first but they used some weird way of implementing the crypto program or something, it cycles 16-19 up one when the rom boots sending 19 back around to 16 and pushing the others up one if i remember correctly. if you ever get confused about it though, this is how i figured it out

go into cwm
adb shell
make a directory called testing or whatever
mount any partition in question to that folder
then browse it using cd and ls commands
if you cant tell kuz its carrier or cache or whatever go back into rom and put a blank file named cache in cache and a blank file named carrier in carrier, that way if things change outside of the rom they will be flagged appropriately

if you use that method and dont do anything else in cwm all you need is a bootable version of cwm with working adb, even if the partitions arent set up correctly in the fstab as long as you are only mounting manually for testing purposes it wont matter at all
 
junkie2100 said:
pretty much. that was confusing at first but they used some weird way of implementing the crypto program or something, it cycles 16-19 up one when the rom boots sending 19 back around to 16 and pushing the others up one if i remember correctly. if you ever get confused about it though, this is how i figured it out

go into cwm
adb shell
make a directory called testing or whatever
mount any partition in question to that folder
then browse it using cd and ls commands
if you cant tell kuz its carrier or cache or whatever go back into rom and put a blank file named cache in cache and a blank file named carrier in carrier, that way if things change outside of the rom they will be flagged appropriately

if you use that method and dont do anything else in cwm all you need is a bootable version of cwm with working adb, even if the partitions arent set up correctly in the fstab as long as you are only mounting manually for testing purposes it wont matter at all
Click to expand...

Thanks Junkie that's some good stuff! :)
 
smartmanvartan said:
End of month..No jb for now tho...
Click to expand...

Oh end of this month that.s good
Right now im public mobile customer useing zte n860
But how about wrap sequent is it also we can root and change rom same as zte n860
Bcz im useing boost mobile rom in public mobile which is really well
What about if we have boost mobile zte wrap sequent phone can we use on public mobile?
Bcz for sure public mobile when they bring phone on public gonna be over 200 dollar so im thinking buy online boost mobile cheep use on public what u think its gonna work
 
chand690 said:
Oh end of this month that.s good
Right now im public mobile customer useing zte n860
But how about wrap sequent is it also we can root and change rom same as zte n860
Bcz im useing boost mobile rom in public mobile which is really well
What about if we have boost mobile zte wrap sequent phone can we use on public mobile?
Bcz for sure public mobile when they bring phone on public gonna be over 200 dollar so im thinking buy online boost mobile cheep use on public what u think its gonna work
Click to expand...


No you won't be able to buy a boost mobile warp sequent and activate it on the public network...public only activates phones that they sold. They have all their devices registered and that's it. Y veules rien savoir... but the n861 will be 199 as far as I know... which room are you using on your n860? Are you using it with unification portal?
 
smartmanvartan said:
No you won't be able to buy a boost mobile warp sequent and activate it on the public network...public only activates phones that they sold. They have all their devices registered and that's it. Y veules rien savoir... but the n861 will be 199 as far as I know... which room are you using on your n860? Are you using it with unification portal?
Click to expand...

Hi again
I.m useing holo jelly 4.3 its work perfect i just only delete vdmc.apk and then i flash on phone work great i did not touch any prl or something bcz i dont know what prl?
What about n861 its also easy root same as 860 or we can change rom also bcz i really waiting front face cam
 
You must log in or register to reply here.
Back
Top Bottom