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

Root [Boost Mobile] Testers wanted

Because MrBobo was able to restore with CWM
does that mean we are able to flash apks with no problem?

I was able to find a stock camera mod which lets us record in widescreen and shoot in it as well in HD

I think until we narrow down what exactly it was that allowed me to get a good backup we can't call this working. I also am too much of a n00b to know if the backup was "good", but I did get it to say I had a successful backup and then that I had a successful restore and the phone worked. Beyond that I don't know what to test.

I will try and narrow down what it is that allows the backup to work today.

I started with a factory reset, wiped dalvik and formatted the sd card through cwm... one or all of those things allowed the backup to work... another question is whether you have to do the backup without allowing the system to boot or if it works either way after the first few steps.
 
Upvote 0
I have played with this off and on today, I was able to get the backup to work one other time after a factory reset and format of the sd card.

I tried adding applications after that to see if I could get a backup to work with non stock data on their but no joy after many attempts (also tried clearing cache and dalvik etc)

best I can see so far is for this to do a backup takes having a fresh phone with a clear sd card, but even that's buggy.

I will probably check out until we get another beta to test, too hard living without all my apps and phone set up how I like it... good to see it almost working though, great work to sebastian and woodstock for the efforts testing/building this so far.
 
Upvote 0
Could it be that it is having trouble with/data/app (or/data all together)
Try factory reset, install a app or 2, then using a file explorer with root access, copy/paste the apk (and odex, if applicable) from /data/app to /system/app.(changing the app to a system) then factory reset- backup/restore.
 
Upvote 0
I put a note out to a couple developers from other threads to see if we can get someone to take a look at the warp cwm while we wait for sebastian to get back, from what I was reading on porting the cwm it doesn't sound like it should be this difficult... probably just oversimplified in my n00b eyes though :)

It shouldn't be. The dev that was working on it didn't actually have a warp to test it on, and were relaying tests through this site.
 
Upvote 0
k I may be able to squeeze this in. Did the original dev have a github of his devices configs etc?

Do yall have root so you can get dumps? If so I need a dd dump of everything. I also will need the following from adb or terminal and saved to a txt file. If done from terminal add /sdcard/ for the destination and then copy to your pc n upload or attach em in a PM.

Code:
cat proc/mtd > warp-mtd.txt
Code:
cat proc/cpuinfo > warp-cpuinfo.txt
Code:
cat proc/partitions > warp-partitions.txt
Code:
cat proc/mounts > warp-mounts.txt

Once I get all those I can help with the dd cmds to get the dumps. If anyone already knows how to get the block mounts to get the dd dumps thats great too, just get get em, upload n PM me the link(s).
 
Upvote 0
k I may be able to squeeze this in. Did the original dev have a github of his devices configs etc?

Do yall have root so you can get dumps? If so I need a dd dump of everything. I also will need the following from adb or terminal and saved to a txt file. If done from terminal add /sdcard/ for the destination and then copy to your pc n upload or attach em in a PM.

Code:
cat proc/mtd > warp-mtd.txt
Code:
cat proc/cpuinfo > warp-cpuinfo.txt
Code:
cat proc/partitions > warp-partitions.txt
Code:
cat proc/mounts > warp-mounts.txt

Once I get all those I can help with the dd cmds to get the dumps. If anyone already knows how to get the block mounts to get the dd dumps thats great too, just get get em, upload n PM me the link(s).
I am at work and I work alot more than the average person but if nobody has helped by the time I get off of work I will get that info for you.
 
Upvote 0
I thought about it and since I cant use ADB here at work I decided to just use Root Explorer.

Here is Mounts.txt info
PHP:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,size=61748k,nr_inodes=15437,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,size=61748k,nr_inodes=15437,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,size=61748k,nr_inodes=15437,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p15 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p18 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p7 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p17 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,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=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Here is CPUINFO.txt
PHP:
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 681.57
Features : swp half thumb fastmult vfp edsp neon vfpv3 
CPU implementer : 0x51
CPU architecture: 7
CPU variant : 0x1
CPU part : 0x00f
CPU revision : 2
Hardware : arthur
Revision : 0000
Serial : 0000000000000000
Here is mtd.txt info
PHP:
dev: size erasesize name
And Here is partitions.txt info
PHP:
major minor #blocks name
179 0 3864576 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 8192 mmcblk0p8
179 9 32768 mmcblk0p9
179 10 32768 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 512000 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 307200 mmcblk0p17
179 18 2840576 mmcblk0p18
179 32 3872256 mmcblk1
179 33 3871232 mmcblk1p1
 

Attachments

  • Warp_info.zip
    1.2 KB · Views: 73
Upvote 0
Hi,
I'm Russian user of ZTE V9+ clone (Megafon V9+). On 4PDA forum we're trying to use this CWM port, and it looks like it can work on our device! The only problem, as you can see in above posts is a reboot during recovery/updating after about 2.5 minutes.
I have a rooted device, so I can provide any information you need. It will be great if we have this port, working on multiple ZTE devices :)
Thanks!
 
Upvote 0
I couldn't get romdump to work in terminal or adb, I got permissions issues in adb and illegal operation in terminal, if you point me in the right direction I will give it another try!

If you already root, you should be able to copy partition from inside /dev/block/platform/msm_sdcc.2 and put it in your sdcard. Be aware that some of the files here are extremely large.
Here are the partition list:
/dev/block/mmcblk0p1 dbl.mbn
/dev/block/mmcblk0p2 osbl.mbn
/dev/block/mmcblk0p3
/dev/block/mmcblk0p4
/dev/block/mmcblk0p5 cefs.bmn
/dev/block/mmcblk0p6
/dev/block/mmcblk0p7 /persist
/dev/block/mmcblk0p8 adsp.mbn
/dev/block/mmcblk0p9 amss.mbn
/dev/block/mmcblk0p10
/dev/block/mmcblk0p11 EMMCBOOT.MBN
/dev/block/mmcblk0p12 boot.img
/dev/block/mmcblk0p13 recovery.img
/dev/block/mmcblk0p14 splash.img
/dev/block/mmcblk0p15 /system
/dev/block/mmcblk0p16 /misc
/dev/block/mmcblk0p17 /cache
/dev/block/mmcblk0p18 /data

You can also use dd from rooted shell to copy partition to sdcard.

For example to copy boot patition to sdcard:
Code:
dd if=/dev/block/mmcblk0p12 of=/sdcard/mmcblk0p12 bs=4096
 
Upvote 0
If you already root, you should be able to copy partition from inside /dev/block/platform/msm_sdcc.2 and put it in your sdcard. Be aware that some of the files here are extremely large.
Here are the partition list:
/dev/block/mmcblk0p1 dbl.mbn
/dev/block/mmcblk0p2 osbl.mbn
/dev/block/mmcblk0p3
/dev/block/mmcblk0p4
/dev/block/mmcblk0p5 cefs.bmn
/dev/block/mmcblk0p6
/dev/block/mmcblk0p7 /persist
/dev/block/mmcblk0p8 adsp.mbn
/dev/block/mmcblk0p9 amss.mbn
/dev/block/mmcblk0p10
/dev/block/mmcblk0p11 EMMCBOOT.MBN
/dev/block/mmcblk0p12 boot.img
/dev/block/mmcblk0p13 recovery.img
/dev/block/mmcblk0p14 splash.img
/dev/block/mmcblk0p15 /system
/dev/block/mmcblk0p16 /misc
/dev/block/mmcblk0p17 /cache
/dev/block/mmcblk0p18 /data

You can also use dd from rooted shell to copy partition to sdcard.

For example to copy boot patition to sdcard:
Code:
dd if=/dev/block/mmcblk0p12 of=/sdcard/mmcblk0p12 bs=4096
Actually the directory on the Warp is /dev/block/platform/msm_sdcc.2/
I dont know if that makes a difference but I always thought that may be the reason for our errors. If the Custom recovery is directed to /dev/block/ instead of /dev/block/platform/msm_sdcc.2/ that is.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones