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

Root [Boost Mobile] Testers wanted

Sebastian404 said:
Cool, can you try a backup and restore see if there's any problems with that?

its possible the device does not have a /misc partition, from looking at the mount list normally, it seems it does not.

the sd-ext mount will only appear if you partition your SDcard, some people like to create a 2nd parition on there for swap, but I dont think you really need that with this device.

if you cant find anything wrong with it, I'll fix the /misc partion and promote it to final :)
Click to expand...
No I dont see a misc partition. I'll try backup.
During backup the progress bar doesnt work so its hard to tell if its actually working. I dont remember any of my old phones taking this long. Still at Backing up data......waiting
 
After 30 minutes I pulled the battery. I went to restore and checked to see if anything showed up there and there was something but when i tried restore it said md5 mismatch and wouldnt do anything. So I booted to android and checked the clockworkmod/backup folder and opened the backup and the data image is 0b. So for some reason the data.img is not backing up.

Tried it again. Will not create data.img.
 
Woodstock77 said:
After 30 minutes I pulled the battery. I went to restore and checked to see if anything showed up there and there was something but when i tried restore it said md5 mismatch and wouldnt do anything. So I booted to android and checked the clockworkmod/backup folder and opened the backup and the data image is 0b. So for some reason the data.img is not backing up.

Tried it again. Will not create data.img.
Click to expand...

did it create any other files? and can you grab the recovery log from /cache?
 
Sebastian404 said:
did it create any other files? and can you grab the recovery log from /cache?
Click to expand...
Yes it created all the other files (cache, system, and recovery) but when it got to backing up data it didnt do anything. The log file doesnt show much but here it is.
PHP: 
Starting recovery on Wed Dec 14 18:16:22 2011
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v4.0.1.5
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/mmcblk0p12 (null)
2 /recovery emmc /dev/block/mmcblk0p13 (null)
3 /splash emmc /dev/block/mmcblk0p14 (null)
4 /system ext4 /dev/block/mmcblk0p15 (null)
5 /misc emmc /dev/block/mmcblk0p16 (null)
6 /cache ext4 /dev/block/mmcblk0p17 (null)
7 /data ext4 /dev/block/mmcblk0p18 (null)
8 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
9 /sd-ext auto /dev/block/mmcblk1p2 (null)
I:Completed outputting fstab.
I:Processing arguments.
E:Can't open /dev/block/mmcblk0p16
(No such file or directory)
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.modversion=clockwork-4.0.1.5-arthur
ro.product.device=arthur
ro.product.name=N860
usb.default.pid=0x1354
persist.usb.default.pid=0x1354
ro.build.date=Wed Dec 14 05:35:47 PST 2011
ro.build.datei.utc=1323645223
ro.build.owner=sebastian404
ro.build.url=http://android.podtwo.com/
ro.factorytest=0
ro.serialno=
ro.bootmode=recovery
ro.baseband=msm
ro.carrier=unknown
ro.bootloader=0.85.0000
ro.hardware=arthur
ro.revision=0
init.svc.usbconfig=stopped
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
BTW Im at work again :confused: so I cant help much for the next 10 hours or so.
 
Woodstock77 said:
Yes it created all the other files (cache, system, and recovery) but when it got to backing up data it didnt do anything. The log file doesnt show much but here it is.
PHP: 
Starting recovery on Wed Dec 14 18:16:22 2011
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v4.0.1.5
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/mmcblk0p12 (null)
2 /recovery emmc /dev/block/mmcblk0p13 (null)
3 /splash emmc /dev/block/mmcblk0p14 (null)
4 /system ext4 /dev/block/mmcblk0p15 (null)
5 /misc emmc /dev/block/mmcblk0p16 (null)
6 /cache ext4 /dev/block/mmcblk0p17 (null)
7 /data ext4 /dev/block/mmcblk0p18 (null)
8 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
9 /sd-ext auto /dev/block/mmcblk1p2 (null)
I:Completed outputting fstab.
I:Processing arguments.
E:Can't open /dev/block/mmcblk0p16
(No such file or directory)
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.modversion=clockwork-4.0.1.5-arthur
ro.product.device=arthur
ro.product.name=N860
usb.default.pid=0x1354
persist.usb.default.pid=0x1354
ro.build.date=Wed Dec 14 05:35:47 PST 2011
ro.build.datei.utc=1323645223
ro.build.owner=sebastian404
ro.build.url=http://android.podtwo.com/
ro.factorytest=0
ro.serialno=
ro.bootmode=recovery
ro.baseband=msm
ro.carrier=unknown
ro.bootloader=0.85.0000
ro.hardware=arthur
ro.revision=0
init.svc.usbconfig=stopped
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
BTW Im at work again :confused: so I cant help much for the next 10 hours or so.
Click to expand...


I think part of the problem is that /data is huge, and possibly bigger than your SDcard..

can someone boot into android and from the adb console do a 'df' and let me know the results? looking at what I've got it thinks its 1073741824
bytes, or 1Gig...
 
Sebastian404 said:
I think part of the problem is that /data is huge, and possibly bigger than your SDcard..

can someone boot into android and from the adb console do a 'df' and let me know the results? looking at what I've got it thinks its 1073741824
bytes, or 1Gig...
Click to expand...
Using root explorer it shows to be only 175.84mb. And that seems on par with some of the other phones Ive messed with. My sd card shows having 1604mb free.

Ok so permissions are different on data. I will change it to be like system and try to do a backup again.
 
  • Sytem is 183.79mb and system.img backup comes out as 192mb
  • recovery.img is backed up as 16mb
  • boot.img comes out at 16mb
  • Data is 175.84mb and data.img backup comes out as 0mb It never starts backing up data or errors out.
 
Woodstock77 said:
  • Sytem is 183.79mb and system.img backup comes out as 192mb
  • recovery.img is backed up as 16mb
  • boot.img comes out at 16mb
  • Data is 175.84mb and data.img backup comes out as 0mb It never starts backing up data or errors out.
Click to expand...

can you do a 'df' from adb and let me know the results?
 
Sebastian404 said:
No problem, but thinking about it, can you boot into recovery, then go into Mounts and Storage Menu, then mount /data

after you've done that do a

df -B 1 -a

from the ADB
Click to expand...
Well earlier adb wouldnt work in recovery but I will try again later. It showed in windows as unkown device while phone was in cwm. I will try anything you throw at me though. But would you take my word for it that data is 175mb? I dont know what the issue is but maybe it isnt being mounted. So I will try Mounts and Storage Menu, then mount /data then try backup right now.
 
Woodstock77 said:
Well earlier adb wouldnt work in recovery but I will try again later. It showed in windows as unkown device while phone was in cwm. I will try anything you throw at me though. But would you take my word for it that data is 175mb? I dont know what the issue is but maybe it isnt being mounted. So I will try Mounts and Storage Menu, then mount /data then try backup right now.
Click to expand...

Im happy to take your word, I'm more interested in what clockwork mod thinks about it :)

I've made a new build with the data partition at 175mb incase it makes a difference.

http://android.podtwo.com/beta/ztewarp/b9_recovery-clockwork-4.0.1.5-arthur.img


btw if you already have a working clockwork mod you can use this update file:

http://android.podtwo.com/beta/ztewarp/b9_recovery-clockwork-4.0.1.5-arthur-update_signed.zip

put it on your SDCard and then 'install zip from sdcard' / 'choose zip from sdcard'.

once its installed you can use 'Advanced' and 'Reboot Recovery' to restart the new version
 
Sebastian404 said:
Im happy to take your word, I'm more interested in what clockwork mod thinks about it :)

I've made a new build with the data partition at 175mb incase it makes a difference.

http://android.podtwo.com/beta/ztewarp/b9_recovery-clockwork-4.0.1.5-arthur.img


btw if you already have a working clockwork mod you can use this update file:

http://android.podtwo.com/beta/ztewarp/b9_recovery-clockwork-4.0.1.5-arthur-update_signed.zip

put it on your SDCard and then 'install zip from sdcard' / 'choose zip from sdcard'.

once its installed you can use 'Advanced' and 'Reboot Recovery' to restart the new version
Click to expand...
After reading and searching Ive found that its probably some file in data on my phone that is corrupted that wont allow it to be backed up. I wish someone else could try so we could verify this though. Every other instance I could find of this same problem has been a corrupted file. I might be needing somebody elses backup just so i can do a backup lol. I dont know where to look for a corupted file in data. I know its not in lost+found. I will try the b9 when I get home.
 
So I decided to try one more thing. I wiped dalvik cache and cache and then ran backup and this time it hung up on backing up system. So I rebooted into recovery and tried backup again. Now its hung in data again. Its almost like its running out of memory or a buffer over run or something like that. I have no idea how it makes the img files but I would think it uses some kind of buffer type system corect?
 
Woodstock77 said:
After reading and searching Ive found that its probably some file in data on my phone that is corrupted that wont allow it to be backed up. I wish someone else could try so we could verify this though. Every other instance I could find of this same problem has been a corrupted file. I might be needing somebody elses backup just so i can do a backup lol. I dont know where to look for a corupted file in data. I know its not in lost+found. I will try the b9 when I get home.
Click to expand...

there is a fix permissions option in advanced.. I think it looks at your data partition too...
 
Im going to try a different SD card when I get home and of course b9. Its probably working. Just problems on my end.
 
hi,
Thanks for your work Sebastian...
I just flashed the recovery and I'm doing a nandroid backup.
Seems like is stuck backing up Data as Woodstock77 mentioned.

I flashed b9 version.

Edit: yes, it froze. I can't even do adb shell. Tells me:
error: device offline

Edit 2: Seems like the recovery freezes after a while. I was messing with it looking at all the options, mounted the sdcards and look at the contents in my pc and suddenly froze. and same error device offline.
 
dkeruza said:
hi,
Thanks for your work Sebastian...
I just flashed the recovery and I'm doing a nandroid backup.
Seems like is stuck backing up Data as Woodstock77 mentioned.

I flashed b9 version.

Edit: yes, it froze. I can't even do adb shell. Tells me:
error: device offline

Edit 2: Seems like the recovery freezes after a while. I was messing with it looking at all the options, mounted the sdcards and look at the contents in my pc and suddenly froze. and same error device offline.
Click to expand...
If you have a spare sd card could you try it? Ive been reading where people have had similar problems with certain sdcards in cwm. Could be the ones that came with the warp are junk.
 
hmm, Im not aware of anything that is time sensitive in the code... I made a build for a the ZTE Skate at the same time (to prove that the build process/code is ok) and its still sat on the first screen after about 12 hours... still working fine...

I also made a build for the V9PLUS and the guy testing that has come back with the similar issues...

So I guess the problem is either in the new 32bit graphics code, or ZTE's new snap dragon kernel...

I'll take a look at the graphics code... but as an experiment, can you reflash the stock recovery and leave it alone for 10 minutes and see if its doing the same thing?
 
Sebastian404 said:
hmm, Im not aware of anything that is time sensitive in the code... I made a build for a the ZTE Skate at the same time (to prove that the build process/code is ok) and its still sat on the first screen after about 12 hours... still working fine...

I also made a build for the V9PLUS and the guy testing that has come back with the similar issues...

So I guess the problem is either in the new 32bit graphics code, or ZTE's new snap dragon kernel...

I'll take a look at the graphics code... but as an experiment, can you reflash the stock recovery and leave it alone for 10 minutes and see if its doing the same thing?
Click to expand...

Sure, I will do it and post the results.
 
Sebastian404 said:
hmm, Im not aware of anything that is time sensitive in the code... I made a build for a the ZTE Skate at the same time (to prove that the build process/code is ok) and its still sat on the first screen after about 12 hours... still working fine...

I also made a build for the V9PLUS and the guy testing that has come back with the similar issues...

So I guess the problem is either in the new 32bit graphics code, or ZTE's new snap dragon kernel...

I'll take a look at the graphics code... but as an experiment, can you reflash the stock recovery and leave it alone for 10 minutes and see if its doing the same thing?
Click to expand...
No problems after 30+ minutes here.
 
Hey sebastion I want to help out, I have a factory fresh Warp, Thanks to the Update tool (Check my other Posts) This thread is such a mess I have no idea what the latest build you want tested is :confused:
 
You must log in or register to reply here.
Back
Top Bottom