Root Boost mobile One SV (warning about clockworkmod)

[shinru2004]

It seems the clockworkmod posted for other One Sv owners will not work for the boost mobile variant. Our partitions are different then all the other models. Their system partition is dev/block/mmcblk0p33 where ours is dev/block/mmcblk0p34 not sure what other partitions are different at this time but will post more info. And a build for our device later.

 

[Rally 517]

It's on page 220 of that thread. I'm on boost been running a week now and everything works

 

[shinru2004]

I will try it out thank you

 

[Rally 517]

I've been seeing people are on jb. But I can't find anything

 

[Rally 517]

It's post 220 not page sorry

 

[Guspeed]

Have you had time to look the recovery from xda?
I see the flicker thingy and also for some reason I can't mount USB storage.

 

[shinru2004]

I'm going to go ahead and make a new recovery. Will see if playfulgod is interested in helping.

 

[Guspeed]

Fingers x!!! lol thanks!!!

 

[junkie2100]

if you can adb with root privledges figuring out partitions isnt all that difficult even if they are incorrectly labeled, check the /proc/partitions file and judge by size, then to double check you can use a mount command to a test folder like i did with the sequent

 

[shinru2004]

half the time adb doesnt work in the CWM recovery we have lol

 

[ODGeek]

if you can adb with root privledges figuring out partitions isnt all that difficult even if they are incorrectly labeled, check the /proc/partitions file and judge by size, then to double check you can use a mount command to a test folder like i did with the sequent

On my phone, the partitions are shown by the following:

$ cat /proc/emmc
dev:        size     erasesize name
mmcblk0p22: 000ffa00 00000200 "misc"
mmcblk0p21: 00fffe00 00000200 "recovery"
mmcblk0p20: 01000000 00000200 "boot"
mmcblk0p35: 54fffc00 00000200 "system"
mmcblk0p29: 00140200 00000200 "local"
mmcblk0p36: 0dfffe00 00000200 "cache"
mmcblk0p37: 49fffe00 00000200 "userdata"
mmcblk0p25: 01400000 00000200 "devlog"
mmcblk0p27: 00040000 00000200 "pdata"
mmcblk0p38: 1097fe000 00000200 "fat"
mmcblk0p30: 00010000 00000200 "extra"
mmcblk0p32: 01900000 00000200 "carrier"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p23: 00400000 00000200 "modem_st1"
mmcblk0p24: 00400000 00000200 "modem_st2"
mmcblk0p31: 00040000 00000200 "skylink"
mmcblk0p33: 00100000 00000200 "cdma_record"
$

Found this by poking around in /proc...

 

[Bocephus87]

Where might I find the CWM that worked for you? I settled in tonight and finally rooted my device. I'm having difficulties finding the thread your talking about though.


EDIT: Scratch that. Havent had enough Coffee. Have to figure out the permanent method of installation though

 

[enzopreme]

Where might I find the CWM that worked for you? I settled in tonight and finally rooted my device. I'm having difficulties finding the thread your talking about though.


EDIT: Scratch that. Havent had enough Coffee. Have to figure out the permanent method of installation though

rename the file to recovery.img instead of recovery_test.img, and instead of doing fastboot boot recovery recovery_test.img just do fastboot flash recovery recovery.img and vuala.... you have perm recovery....

 

[Bocephus87]

Thanks for the help!