Go Back   Android Forums > Android Phones > ZTE Warp (N860) > (Boost Mobile) Warp - All Things Root

Get excited for the Samsung Galaxy S5! Find everything you need and discuss it in our Galaxy S5 Forum!

Like Tree2Likes

test: Reply
 
LinkBack Thread Tools
Old December 11th, 2011, 07:21 PM   #51 (permalink)
New Member
 
Join Date: Oct 2011
Posts: 7
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

Quote:
Originally Posted by Sebastian404 View Post
Is there now a log file in cache/recovery/log ?

It sounds like its working but the screen is not working... If so nearly there..
Yeah I don't have a log either.

attrapp is offline  
Reply With Quote
sponsored links
Old December 12th, 2011, 06:20 AM   #52 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Dec 2011
Posts: 92
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 27 Times in 15 Posts
Default

Ok, another day another build...

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

I'm starting to run out of ideas tho
Sebastian404 is offline  
Reply With Quote
Old December 12th, 2011, 09:32 AM   #53 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

Quote:
Originally Posted by Sebastian404 View Post
Ok, another day another build...

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

I'm starting to run out of ideas tho
Same as b4
Woodstock77 is offline  
Reply With Quote
Old December 12th, 2011, 01:31 PM   #54 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Dec 2011
Posts: 92
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 27 Times in 15 Posts
Default

Quote:
Originally Posted by Woodstock77 View Post
Same as b4
hmmm

Can you do a dmesg again? see if I can see anything different.


A guy has contacted me about the V9PLUS which is ZTE's latest Tablet, it seems to have the same hardware, I'm just building a recovery for him. it will be interesting to see if it has the same issues :!
Sebastian404 is offline  
Reply With Quote
Old December 12th, 2011, 03:24 PM   #55 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

Quote:
Originally Posted by Sebastian404 View Post
hmmm

Can you do a dmesg again? see if I can see anything different.


A guy has contacted me about the V9PLUS which is ZTE's latest Tablet, it seems to have the same hardware, I'm just building a recovery for him. it will be interesting to see if it has the same issues :!
I just went to work. It will be late tonight before I can do it.
Woodstock77 is offline  
Reply With Quote
Old December 12th, 2011, 04:48 PM   #56 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Dec 2011
Posts: 92
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 27 Times in 15 Posts
Default

Quote:
Originally Posted by Woodstock77 View Post
I just went to work. It will be late tonight before I can do it.
ok, I've made another build:

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

I'm not expecting it to be any different, but I've added in code that should mount /cache can you check it and see there anything in there at all? there should be a /cache/recovery/log file.


The other thing you could try doing is re-flash the stock recovery, then reboot into it, pick the reboot option and when you end up in android have a look in the /cache/ directory then...
Sebastian404 is offline  
Last edited by Sebastian404; December 12th, 2011 at 07:39 PM.
Reply With Quote
Old December 12th, 2011, 08:02 PM   #57 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

Quote:
Originally Posted by Sebastian404 View Post
ok, I've made another build:

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

I'm not expecting it to be any different, but I've added in code that should mount /cache can you check it and see there anything in there at all? there should be a /cache/recovery/log file.


The other thing you could try doing is re-flash the stock recovery, then reboot into it, pick the reboot option and when you end up in android have a look in the /cache/ directory then...
Should I pull a dmesg and mount from stock as well just to see whats different? I was hoping someone else might step in and help here since Im stuck at work until 2am (about 6 more hrs).
Woodstock77 is offline  
Reply With Quote
Old December 13th, 2011, 01:46 AM   #58 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

With b6 it boot loops in recovery. Every time it gets to the hardware buttons lighting up it restarts. What now?
Woodstock77 is offline  
Reply With Quote
Old December 13th, 2011, 11:02 AM   #59 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Dec 2011
Posts: 92
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 27 Times in 15 Posts
Default

Quote:
Originally Posted by Woodstock77 View Post
With b6 it boot loops in recovery. Every time it gets to the hardware buttons lighting up it restarts. What now?
argh! sorry thats my fault, typo.

can you try this verison :

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

Im going to assume that the screen still wont work, but it hopefully should create a log file in /cache


once you've done that, can you then reflash the original stock recovery:

http://android.podtwo.com/beta/ztewarp/stock_recovery.img

reboot into recovery, then reboot back to normal and then see if it created a recovery log in /cache


and the post the log files (if any exist)
Sebastian404 is offline  
Reply With Quote
The Following User Says Thank You to Sebastian404 For This Useful Post:
kijangaaja (December 14th, 2011)
Old December 13th, 2011, 11:49 AM   #60 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

Quote:
Originally Posted by Sebastian404 View Post
argh! sorry thats my fault, typo.

can you try this verison :

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

Im going to assume that the screen still wont work, but it hopefully should create a log file in /cache


once you've done that, can you then reflash the original stock recovery:

http://android.podtwo.com/beta/ztewarp/stock_recovery.img

reboot into recovery, then reboot back to normal and then see if it created a recovery log in /cache


and the post the log files (if any exist)
Ok in b6 there is still no recovery log found.
In stock the device is not found and there is no unknown devices in the system. For some reason it doesnt use diag drivers in stock recovery.
Woodstock77 is offline  
Reply With Quote
sponsored links
Old December 13th, 2011, 12:54 PM   #61 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Dec 2011
Posts: 92
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 27 Times in 15 Posts
Default

Quote:
Originally Posted by Woodstock77 View Post
Ok in b6 there is still no recovery log found.
In stock the device is not found and there is no unknown devices in the system. For some reason it doesnt use diag drivers in stock recovery.
if you reboot the device back into android is there anything in the /cache/recovery dir?
Sebastian404 is offline  
Reply With Quote
Old December 13th, 2011, 01:00 PM   #62 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

Quote:
Originally Posted by Sebastian404 View Post
if you reboot the device back into android is there anything in the /cache/recovery dir?
No nothing
Woodstock77 is offline  
Reply With Quote
Old December 13th, 2011, 01:14 PM   #63 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

I decided to look for it using root explorer. What I found was a file called last_log. Here is what is in it. I need to try using it with b6 next but this is after stock.
PHP Code:
Starting recovery on Tue Dec 13 17:43:49 2011
framebuffer
fd 4 (480 x 800)
recovery filesystem table
=========================
  
/tmp ramdisk (null) (null)
  
/dbl emmc /dev/block/mmcblk0p1 (null)
  
/osbl emmc /dev/block/mmcblk0p2 (null)
  
/cefs emmc /dev/block/mmcblk0p5 (null)
  
/adsp emmc /dev/block/mmcblk0p8 (null)
  
/amss emmc /dev/block/mmcblk0p9 (null)
  
/emmcboot emmc /dev/block/mmcblk0p11 (null)
  
/boot emmc /dev/block/mmcblk0p12 (null)
  
/recovery emmc /dev/block/mmcblk0p13 (null)
  
/splash emmc /dev/block/mmcblk0p14 (null)
  
10 /system ext4 /dev/block/mmcblk0p15 (null)
  
11 /misc emmc /dev/block/mmcblk0p16 (null)
  
12 /cache ext4 /dev/block/mmcblk0p17 (null)
  
13 /data ext4 /dev/block/mmcblk0p18 (null)
  
14 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1

Command
"/sbin/recovery"

ro.secure=1
ro
.allow.mock.location=0
ro
.debuggable=0
persist
.service.adb.enable=0
ro
.build.id=GINGERBREAD
ro
.build.display.id=N860V1.0.0B06
ro
.build.version.incremental=eng.tanbaihua.20110926.163948
ro
.build.version.sdk=10
ro
.build.version.codename=REL
ro
.build.version.release=2.3.5
ro
.build.date=Mon Sep 26 16:48:06 CST 2011
ro
.build.date.utc=1317026886
ro
.build.type=user
ro
.build.user=tanbaihua
ro
.build.host=zhangchun-desktop
ro
.build.tags=release-keys
ro
.product.model=N860
ro
.product.brand=ZTE
ro
.product.name=ZTE_Warp
ro
.product.device=arthur
ro
.product.board=arthur
ro
.product.cpu.abi=armeabi-v7a
ro
.product.cpu.abi2=armeabi
ro
.product.manufacturer=ZTE
ro
.product.locale.language=en
ro
.product.locale.region=US
ro
.wifi.channels=
ro.board.platform=msm7k
ro
.build.product=arthur
ro
.build.description=ZTE_Warp-user 2.3.5 GINGERBREAD eng.tanbaihua.20110926.163948 release-keys
ro
.build.fingerprint=ZTE/ZTE_Warp/arthur:2.3.5/GINGERBREAD/eng.tanbaihua.20110926.163948:user/release-keys
ro
.setupwizard.mode=DISABLED
ro
.product.board_name=arthur
rild
.libpath=/system/lib/libril-qc-1.so
rild
.libargs=-/dev/smd0
persist
.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV
DEVICE_PROVISIONED
=1
debug
.egl.hw=1
debug
.sf.hw=1
dalvik
.vm.heapsize=32m
ro
.dev.dmm=1
dev
.dmm.dpd.trigger_delay=30
ro
.sf.lcd_density=240
ro
.sf.hwrotation=180
persist
.cne.UseCne=false
persist
.cne.loadVendorCne=true
persist
.cne.bat.range.low.med=30
persist
.cne.bat.range.med.high=60
persist
.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist
.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist
.cne.bwbased.rat.sel=true
persist
.cne.snsr.based.rat.mgt=true
persist
.cne.bat.based.rat.mgt=true
persist
.cne.rat.acq.time.out=30000
persist
.cne.rat.acq.retry.tout=0
lpa
.decode=true
ro
.use_data_netmgrd=true
ro
.emmc.sdcard.partition=16
media
.stagefright.enable-player=true
media
.stagefright.enable-meta=false
media
.stagefright.enable-scan=false
media
.stagefright.enable-http=true
ro
.opengles.version=131072
ro
.qualcomm.bluetooth.dun=true
ro
.build.baseband_version=N860B01
ro
.build.software_version=N860V1.0.0B06
ro
.build.sw_internal_version=N860V1.0.0B12
ro
.camera.video.size.mms=1048576
ro
.camera.video.duaration.mms=40
ro
.config.ringtone=Ring_Synth_04.ogg
ro
.com.google.clientidbase=android-zte
ro
.com.google.clientidbase.yt=android-zte
ro
.com.google.clientidbase.am=android-boost-us
ro
.com.google.clientidbase.ms=android-boost-us
ro
.com.google.clientidbase.gmm=android-zte
ro
.build.hardware_version=c4tB
ro
.build.pri.version=61007
ro
.config.notification_sound=F1_New_SMS.ogg
ro
.config.alarm_alert=Alarm_Classic.ogg
ro
.com.google.gmsversion=2.3_r6
persist
.sys.usb.enable_switch=1
persist
.sys.usb.linux_switch=1
persist
.sys.usb.switch_pid=0x1351
persist
.sys.usb.linux_pid=0x1350
persist
.sys.usb.default.pid=0x83
persist
.sys.sdcard.mount=1
persist
.sys.usb.unique_sn=1
persist
.sys.usb.enable_cdrom=0x5656
net
.bt.name=Android
net
.change=net.bt.name
dalvik
.vm.stack-trace-file=/data/anr/traces.txt
ro
.factorytest=0
ro
.serialno=
ro.bootmode=recovery
ro
.baseband=msm
ro
.bootloader=0.85.0000
ro
.hardware=arthur
ro
.revision=0
ro
.emmc=1
ro
.gcftest=0
init
.svc.rmt_storage=running
init
.svc.recovery=running
init
.svc.diagtest=running
init
.svc.adbd=stopped 
Woodstock77 is offline  
Reply With Quote
Old December 13th, 2011, 01:20 PM   #64 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default we have a log

This is the b6 last_log
PHP Code:
Starting recovery on Tue Dec 13 17:43:49 2011
framebuffer
fd 4 (480 x 800)
recovery filesystem table
=========================
  
/tmp ramdisk (null) (null)
  
/dbl emmc /dev/block/mmcblk0p1 (null)
  
/osbl emmc /dev/block/mmcblk0p2 (null)
  
/cefs emmc /dev/block/mmcblk0p5 (null)
  
/adsp emmc /dev/block/mmcblk0p8 (null)
  
/amss emmc /dev/block/mmcblk0p9 (null)
  
/emmcboot emmc /dev/block/mmcblk0p11 (null)
  
/boot emmc /dev/block/mmcblk0p12 (null)
  
/recovery emmc /dev/block/mmcblk0p13 (null)
  
/splash emmc /dev/block/mmcblk0p14 (null)
  
10 /system ext4 /dev/block/mmcblk0p15 (null)
  
11 /misc emmc /dev/block/mmcblk0p16 (null)
  
12 /cache ext4 /dev/block/mmcblk0p17 (null)
  
13 /data ext4 /dev/block/mmcblk0p18 (null)
  
14 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1

Command
"/sbin/recovery"

ro.secure=1
ro
.allow.mock.location=0
ro
.debuggable=0
persist
.service.adb.enable=0
ro
.build.id=GINGERBREAD
ro
.build.display.id=N860V1.0.0B06
ro
.build.version.incremental=eng.tanbaihua.20110926.163948
ro
.build.version.sdk=10
ro
.build.version.codename=REL
ro
.build.version.release=2.3.5
ro
.build.date=Mon Sep 26 16:48:06 CST 2011
ro
.build.date.utc=1317026886
ro
.build.type=user
ro
.build.user=tanbaihua
ro
.build.host=zhangchun-desktop
ro
.build.tags=release-keys
ro
.product.model=N860
ro
.product.brand=ZTE
ro
.product.name=ZTE_Warp
ro
.product.device=arthur
ro
.product.board=arthur
ro
.product.cpu.abi=armeabi-v7a
ro
.product.cpu.abi2=armeabi
ro
.product.manufacturer=ZTE
ro
.product.locale.language=en
ro
.product.locale.region=US
ro
.wifi.channels=
ro.board.platform=msm7k
ro
.build.product=arthur
ro
.build.description=ZTE_Warp-user 2.3.5 GINGERBREAD eng.tanbaihua.20110926.163948 release-keys
ro
.build.fingerprint=ZTE/ZTE_Warp/arthur:2.3.5/GINGERBREAD/eng.tanbaihua.20110926.163948:user/release-keys
ro
.setupwizard.mode=DISABLED
ro
.product.board_name=arthur
rild
.libpath=/system/lib/libril-qc-1.so
rild
.libargs=-/dev/smd0
persist
.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV
DEVICE_PROVISIONED
=1
debug
.egl.hw=1
debug
.sf.hw=1
dalvik
.vm.heapsize=32m
ro
.dev.dmm=1
dev
.dmm.dpd.trigger_delay=30
ro
.sf.lcd_density=240
ro
.sf.hwrotation=180
persist
.cne.UseCne=false
persist
.cne.loadVendorCne=true
persist
.cne.bat.range.low.med=30
persist
.cne.bat.range.med.high=60
persist
.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist
.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist
.cne.bwbased.rat.sel=true
persist
.cne.snsr.based.rat.mgt=true
persist
.cne.bat.based.rat.mgt=true
persist
.cne.rat.acq.time.out=30000
persist
.cne.rat.acq.retry.tout=0
lpa
.decode=true
ro
.use_data_netmgrd=true
ro
.emmc.sdcard.partition=16
media
.stagefright.enable-player=true
media
.stagefright.enable-meta=false
media
.stagefright.enable-scan=false
media
.stagefright.enable-http=true
ro
.opengles.version=131072
ro
.qualcomm.bluetooth.dun=true
ro
.build.baseband_version=N860B01
ro
.build.software_version=N860V1.0.0B06
ro
.build.sw_internal_version=N860V1.0.0B12
ro
.camera.video.size.mms=1048576
ro
.camera.video.duaration.mms=40
ro
.config.ringtone=Ring_Synth_04.ogg
ro
.com.google.clientidbase=android-zte
ro
.com.google.clientidbase.yt=android-zte
ro
.com.google.clientidbase.am=android-boost-us
ro
.com.google.clientidbase.ms=android-boost-us
ro
.com.google.clientidbase.gmm=android-zte
ro
.build.hardware_version=c4tB
ro
.build.pri.version=61007
ro
.config.notification_sound=F1_New_SMS.ogg
ro
.config.alarm_alert=Alarm_Classic.ogg
ro
.com.google.gmsversion=2.3_r6
persist
.sys.usb.enable_switch=1
persist
.sys.usb.linux_switch=1
persist
.sys.usb.switch_pid=0x1351
persist
.sys.usb.linux_pid=0x1350
persist
.sys.usb.default.pid=0x83
persist
.sys.sdcard.mount=1
persist
.sys.usb.unique_sn=1
persist
.sys.usb.enable_cdrom=0x5656
net
.bt.name=Android
net
.change=net.bt.name
dalvik
.vm.stack-trace-file=/data/anr/traces.txt
ro
.factorytest=0
ro
.serialno=
ro.bootmode=recovery
ro
.baseband=msm
ro
.bootloader=0.85.0000
ro
.hardware=arthur
ro
.revision=0
ro
.emmc=1
ro
.gcftest=0
init
.svc.rmt_storage=running
init
.svc.recovery=running
init
.svc.diagtest=running
init
.svc.adbd=stopped 
They are the same so I assume from stock and not b6
I have to go to work now.
Attached Files
File Type: zip log.zip (1.7 KB, 1 views)
Woodstock77 is offline  
Last edited by Woodstock77; December 13th, 2011 at 01:23 PM.
Reply With Quote
Old December 13th, 2011, 05:54 PM   #65 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

If anyone else wants to get in on the fun and see whats happenning try these things. Some of the instruction here is assuming that you have a little more understanding so I kind of want to clarify it a little. When you download the support files unzip them to a an easy location on you hard drive. Lets say your HD is C:\ make a folder there called zte or something easy (c:\zte\) then unzip the support files into it. Then put your recovery image in there as well http://android.podtwo.com/beta/ztewarp/stock_recovery.img
. Go to the start menu and run type cmd and enter and the command prompt window will open. Type "cd c:\zte" or whatever you named the file and press enter. Then enter these commands (WAIT FOR EACH TO COMPLETE) After bootloader you will just see the green andoid, After flashing recovery you will see when its done. After reboot you will be back in android. After reboot recovery you will see the recovery console.
PHP Code:
adb-windows.exe reboot bootloader
fastboot
-windows.exe flash recovery stock_recovery.img
fastboot
-windows.exe reboot
adb
-windows.exe reboot recovery 
That should get you into the stock recovery. You wont be able to copy any files from here because for some reason the diag comms dont work with the stock recovery. But if you did one of the other stock recovery files you could do a few more things. This is just to get you familiar with what we're doing. Just reboot into android from here.
Now once android starts back up type
PHP Code:
adb-windows.exe pull /cache/recovery/last_log recovery_log.txt 
It should make a text file called recovery_log.txt in your folder where you put the support files. You can name it anything you want for example if you wanted pink_elephants.txt type in
PHP Code:
adb-windows.exe pull /cache/recovery/last_log pink_elephants.txt 
.

I didnt get into drivers and all that but I wanted to give you some ideas of what to do.
Woodstock77 is offline  
Last edited by Woodstock77; December 13th, 2011 at 06:03 PM.
Reply With Quote
The Following 2 Users Say Thank You to Woodstock77 For This Useful Post:
kijangaaja (December 14th, 2011), Snake X (January 25th, 2012)
Old December 13th, 2011, 06:25 PM   #66 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Dec 2011
Posts: 92
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 27 Times in 15 Posts
Default

Ok, I've been doing some looking around and I found some mention of a fix for a 'blank screen' that I've now applied the recovery source...

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

maybe 7th time lucky?
Sebastian404 is offline  
Reply With Quote
The Following User Says Thank You to Sebastian404 For This Useful Post:
kijangaaja (December 14th, 2011)
Old December 13th, 2011, 06:43 PM   #67 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

Quote:
Originally Posted by Sebastian404 View Post
Ok, I've been doing some looking around and I found some mention of a fix for a 'blank screen' that I've now applied the recovery source...

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

maybe 7th time lucky?
I cant wait to test it out. But I have to wait until I get off work. 7 more hours. I work too much.
Woodstock77 is offline  
Reply With Quote
Old December 13th, 2011, 07:35 PM   #68 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Dec 2011
Posts: 92
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 27 Times in 15 Posts
Default

Quote:
Originally Posted by Woodstock77 View Post
I cant wait to test it out. But I have to wait until I get off work. 7 more hours. I work too much.
it seems that way

Im hoping to be back in the US for Christmas, I might look into picking one up for myself, the hardware seems to be the way forward for ZTE since I'm now aware that other devices in their range use the same hardware..
Sebastian404 is offline  
Reply With Quote
Old December 13th, 2011, 09:17 PM   #69 (permalink)
Junior Member
 
Join Date: Dec 2011
Posts: 28
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 0 Times in 0 Posts
Thumbs up

First time posting been lurking since the prevail was rooted. Shabby interdpth you guys are that ish. Lil question Sebastian, my basband is n860b01 kernel 2.6.35.7-perf+ zte-kernel@zdroid-smt build b07 hardware version c4tb . Is that the same as yours? If not would that even make a difference? Great job so far muchos gracias can't wait to see the cwm up and running on the warp.
jessesigmon is offline  
Last edited by jessesigmon; December 13th, 2011 at 09:37 PM.
Reply With Quote
Old December 13th, 2011, 09:26 PM   #70 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

Quote:
Originally Posted by jessesigmon View Post
First time posting been lurking since the prevail was rooted. Shabby interdpth you guys are that ish. Like question Sebastian, my baseman is n860b01 kernel 2.6.35.7-perf+ zte-kernel@zdroid-smt build b07 hardware version c4tb . Is that the same as yours? If not would that even make a difference? Great job so far muchos gracias can't wait to see the Candice up and running on the warp.
My build is b06 everything else is the same. Sebastian doesnt have a warp thats why all this back and forth here. I wouldnt think there would be a difference when it comes to this.
Woodstock77 is offline  
Reply With Quote
sponsored links
Old December 14th, 2011, 01:45 AM   #71 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

Quote:
Originally Posted by Sebastian404 View Post
it seems that way

Im hoping to be back in the US for Christmas, I might look into picking one up for myself, the hardware seems to be the way forward for ZTE since I'm now aware that other devices in their range use the same hardware..
Well. Custom recovery shows up. But iys tiny and shows up 4 times. I can only see 2 whole and two halves though. Also I cannot move up and down or make a selection.
Getting closer. Ohh also it showed up as unknown device and wouldnt take any drivers.
Woodstock77 is offline  
Last edited by Woodstock77; December 14th, 2011 at 01:53 AM.
Reply With Quote
The Following User Says Thank You to Woodstock77 For This Useful Post:
kijangaaja (December 14th, 2011)
Old December 14th, 2011, 01:58 AM   #72 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

Also it did create a last_log and here is whats in it.

PHP Code:
Starting recovery on Wed Dec 14 07:41:09 2011
framebuffer
fd 4 (480 x 800)
active fb swap failedInvalid argument
CWM
-based Recovery v4.0.1.5
active fb swap failed
Invalid argument
recovery filesystem table
=========================
  
/tmp ramdisk (null) (null)
  
/boot emmc /dev/block/mmcblk0p12 (null)
  
/recovery emmc /dev/block/mmcblk0p13 (null)
  
/splash emmc /dev/block/mmcblk0p14 (null)
  
/system ext4 /dev/block/mmcblk0p15 (null)
  
/misc emmc /dev/block/mmcblk0p16 (null)
  
/cache ext4 /dev/block/mmcblk0p17 (null)
  
/data ext4 /dev/block/mmcblk0p18 (null)
  
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1

W
:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
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=Tue Dec 13 16:20:32 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...
active fb swap failedInvalid argument
I
:Skipping execution of extendedcommandfile not found... 
Woodstock77 is offline  
Reply With Quote
The Following User Says Thank You to Woodstock77 For This Useful Post:
kijangaaja (December 14th, 2011)
Old December 14th, 2011, 07:42 AM   #73 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Dec 2011
Posts: 92
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 27 Times in 15 Posts
Default

Quote:
Originally Posted by Woodstock77 View Post
Well. Custom recovery shows up. But iys tiny and shows up 4 times. I can only see 2 whole and two halves though. Also I cannot move up and down or make a selection.
Getting closer. Ohh also it showed up as unknown device and wouldnt take any drivers.
interesting, from the sound of it, the Kernel only supports a 32bit Framebuffer... not come across one of those before, been looking around other devices that have those and I've 'borrowed' some code from there...

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

8th time lucky?
Sebastian404 is offline  
Reply With Quote
Old December 14th, 2011, 10:28 AM   #74 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

Quote:
Originally Posted by Sebastian404 View Post
interesting, from the sound of it, the Kernel only supports a 32bit Framebuffer... not come across one of those before, been looking around other devices that have those and I've 'borrowed' some code from there...

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

8th time lucky?
It works as far as I can tell. One screen and you can select things. I did see an error message at the bottom and I'm posting the log.
PHP Code:
Starting recovery on Wed Dec 14 16:22:00 2011
framebuffer
fd 4 (480 x 800)
CWM-based Recovery v4.0.1.5
recovery filesystem table
=========================
  
/tmp ramdisk (null) (null)
  
/boot emmc /dev/block/mmcblk0p12 (null)
  
/recovery emmc /dev/block/mmcblk0p13 (null)
  
/splash emmc /dev/block/mmcblk0p14 (null)
  
/system ext4 /dev/block/mmcblk0p15 (null)
  
/misc emmc /dev/block/mmcblk0p16 (null)
  
/cache ext4 /dev/block/mmcblk0p17 (null)
  
/data ext4 /dev/block/mmcblk0p18 (null)
  
/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=running
init.svc.recovery=running

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found... 
So I looked for E:Cant open /dev/block/mmcblk0p16 and found mmcblk0p16 at dev/block/platform/msm_sdcc2/mmcblk0p16. All files of that type are in that directory (dev/block/platform/msm_sdcc2/).
So I think all these should be looking in that directory like
0 /tmp ramdisk (null) (null)
1 /boot emmc /
dev/block/platform/msm_sdcc2/mmcblk0p12 (null)
2 /recovery emmc /
dev/block/platform/msm_sdcc2/mmcblk0p13 (null)
3 /splash emmc /
dev/block/platform/msm_sdcc2/mmcblk0p14 (null)
4 /system ext4 /
dev/block/platform/msm_sdcc2/mmcblk0p15 (null)
5 /misc emmc /
dev/block/platform/msm_sdcc2/mmcblk0p16 (null)
6 /cache ext4 /
dev/block/platform/msm_sdcc2/mmcblk0p17 (null)
7 /data ext4 /
dev/block/platform/msm_sdcc2/mmcblk0p18 (null)
8 /sdcard vfat /
dev/block/platform/msm_sdcc4/mmcblk1p1 /dev/block/platform/msm_sdcc4/mmcblk1
9
/sd-ext auto /dev/block/mmcblk1p2 (null)
<<cannot find!
Woodstock77 is offline  
Last edited by Woodstock77; December 14th, 2011 at 10:58 AM.
Reply With Quote
Old December 14th, 2011, 11:17 AM   #75 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Dec 2011
Posts: 92
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 27 Times in 15 Posts
Default

Quote:
Originally Posted by Woodstock77 View Post
It works as far as I can tell. One screen and you can select things. I did see an error message at the bottom and I'm posting the log.
PHP Code:
Starting recovery on Wed Dec 14 16:22:00 2011
framebuffer
fd 4 (480 x 800)
CWM-based Recovery v4.0.1.5
recovery filesystem table
=========================
  
/tmp ramdisk (null) (null)
  
/boot emmc /dev/block/mmcblk0p12 (null)
  
/recovery emmc /dev/block/mmcblk0p13 (null)
  
/splash emmc /dev/block/mmcblk0p14 (null)
  
/system ext4 /dev/block/mmcblk0p15 (null)
  
/misc emmc /dev/block/mmcblk0p16 (null)
  
/cache ext4 /dev/block/mmcblk0p17 (null)
  
/data ext4 /dev/block/mmcblk0p18 (null)
  
/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=running
init.svc.recovery=running

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found... 
So I looked for E:Cant open /dev/block/mmcblk0p16 and found mmcblk0p16 at dev/block/platform/msm_sdcc2/mmcblk0p16. All files of that type are in that directory (dev/block/platform/msm_sdcc2/).
So I think all these should be looking in that directory like
0 /tmp ramdisk (null) (null)
1 /boot emmc /
dev/block/platform/msm_sdcc2/mmcblk0p12 (null)
2 /recovery emmc /
dev/block/platform/msm_sdcc2/mmcblk0p13 (null)
3 /splash emmc /
dev/block/platform/msm_sdcc2/mmcblk0p14 (null)
4 /system ext4 /
dev/block/platform/msm_sdcc2/mmcblk0p15 (null)
5 /misc emmc /
dev/block/platform/msm_sdcc2/mmcblk0p16 (null)
6 /cache ext4 /
dev/block/platform/msm_sdcc2/mmcblk0p17 (null)
7 /data ext4 /
dev/block/platform/msm_sdcc2/mmcblk0p18 (null)
8 /sdcard vfat /
dev/block/platform/msm_sdcc4/mmcblk1p1 /dev/block/platform/msm_sdcc4/mmcblk1
9
/sd-ext auto /dev/block/mmcblk1p2 (null)
<<cannot find!

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
Sebastian404 is offline  
Reply With Quote
Old December 14th, 2011, 11:20 AM   #76 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

Quote:
Originally Posted by Sebastian404 View Post
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
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
Woodstock77 is offline  
Last edited by Woodstock77; December 14th, 2011 at 11:29 AM.
Reply With Quote
Old December 14th, 2011, 11:59 AM   #77 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

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 is offline  
Last edited by Woodstock77; December 14th, 2011 at 12:58 PM.
Reply With Quote
Old December 14th, 2011, 01:25 PM   #78 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Dec 2011
Posts: 92
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 27 Times in 15 Posts
Default

Quote:
Originally Posted by Woodstock77 View Post
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.
did it create any other files? and can you grab the recovery log from /cache?
Sebastian404 is offline  
Last edited by Sebastian404; December 14th, 2011 at 01:31 PM.
Reply With Quote
Old December 14th, 2011, 03:21 PM   #79 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

Quote:
Originally Posted by Sebastian404 View Post
did it create any other files? and can you grab the recovery log from /cache?
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 Code:
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
=========================
/tmp ramdisk (null) (null)
/boot emmc /dev/block/mmcblk0p12 (null)
/recovery emmc /dev/block/mmcblk0p13 (null)
/splash emmc /dev/block/mmcblk0p14 (null)
/system ext4 /dev/block/mmcblk0p15 (null)
/misc emmc /dev/block/mmcblk0p16 (null)
/cache ext4 /dev/block/mmcblk0p17 (null)
/data ext4 /dev/block/mmcblk0p18 (null)
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/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 so I cant help much for the next 10 hours or so.
Woodstock77 is offline  
Last edited by Woodstock77; December 14th, 2011 at 03:23 PM.
Reply With Quote
The Following User Says Thank You to Woodstock77 For This Useful Post:
kijangaaja (December 14th, 2011)
Old December 14th, 2011, 03:54 PM   #80 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Dec 2011
Posts: 92
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 27 Times in 15 Posts
Default

Quote:
Originally Posted by Woodstock77 View Post
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 Code:
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
=========================
/tmp ramdisk (null) (null)
/boot emmc /dev/block/mmcblk0p12 (null)
/recovery emmc /dev/block/mmcblk0p13 (null)
/splash emmc /dev/block/mmcblk0p14 (null)
/system ext4 /dev/block/mmcblk0p15 (null)
/misc emmc /dev/block/mmcblk0p16 (null)
/cache ext4 /dev/block/mmcblk0p17 (null)
/data ext4 /dev/block/mmcblk0p18 (null)
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/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 so I cant help much for the next 10 hours or so.

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 is offline  
Reply With Quote
sponsored links
Old December 14th, 2011, 05:20 PM   #81 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

Quote:
Originally Posted by Sebastian404 View Post
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...
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.
Woodstock77 is offline  
Last edited by Woodstock77; December 14th, 2011 at 05:28 PM.
Reply With Quote
Old December 14th, 2011, 05:43 PM   #82 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

  • 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 is offline  
Reply With Quote
The Following User Says Thank You to Woodstock77 For This Useful Post:
kijangaaja (December 14th, 2011)
Old December 14th, 2011, 06:04 PM   #83 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Dec 2011
Posts: 92
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 27 Times in 15 Posts
Default

Quote:
Originally Posted by Woodstock77 View Post
  • 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.
can you do a 'df' from adb and let me know the results?
Sebastian404 is offline  
Reply With Quote
Old December 14th, 2011, 06:28 PM   #84 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

Quote:
Originally Posted by Sebastian404 View Post
can you do a 'df' from adb and let me know the results?
Im at work so I cant do it for about 7 more hours.
Woodstock77 is offline  
Reply With Quote
Old December 14th, 2011, 06:44 PM   #85 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Dec 2011
Posts: 92
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 27 Times in 15 Posts
Default

Quote:
Originally Posted by Woodstock77 View Post
Im at work so I cant do it for about 7 more hours.
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
Sebastian404 is offline  
Reply With Quote
Old December 14th, 2011, 07:02 PM   #86 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

Quote:
Originally Posted by Sebastian404 View Post
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
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 is offline  
Reply With Quote
Old December 14th, 2011, 07:31 PM   #87 (permalink)
Member
 
Join Date: Jul 2011
Location: TheATL
Posts: 208
 
Device(s): EVO V 4G
Carrier: Not Provided

Thanks: 43
Thanked 38 Times in 30 Posts
Default

I will give this a try later when I get off if it is not to late . I have a 16gig card installed.
aladdin99 is offline  
Reply With Quote
Old December 14th, 2011, 07:48 PM   #88 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Dec 2011
Posts: 92
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 27 Times in 15 Posts
Default

Quote:
Originally Posted by Woodstock77 View Post
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.
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 is offline  
Reply With Quote
The Following User Says Thank You to Sebastian404 For This Useful Post:
kijangaaja (December 14th, 2011)
Old December 14th, 2011, 08:08 PM   #89 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

Quote:
Originally Posted by Sebastian404 View Post
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
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.
Woodstock77 is offline  
Reply With Quote
Old December 14th, 2011, 08:28 PM   #90 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

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 is offline  
Reply With Quote
sponsored links
Old December 14th, 2011, 09:18 PM   #91 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Dec 2011
Posts: 92
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 27 Times in 15 Posts
Default

Quote:
Originally Posted by Woodstock77 View Post
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.
there is a fix permissions option in advanced.. I think it looks at your data partition too...
Sebastian404 is offline  
Reply With Quote
Old December 14th, 2011, 09:27 PM   #92 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

Im going to try a different SD card when I get home and of course b9. Its probably working. Just problems on my end.
Woodstock77 is offline  
Reply With Quote
Old December 14th, 2011, 10:43 PM   #93 (permalink)
New Member
 
Join Date: Nov 2011
Posts: 5
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 3 Times in 2 Posts
Default

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 is offline  
Last edited by dkeruza; December 14th, 2011 at 10:51 PM.
Reply With Quote
The Following 2 Users Say Thank You to dkeruza For This Useful Post:
kijangaaja (December 15th, 2011), Woodstock77 (December 14th, 2011)
Old December 14th, 2011, 11:07 PM   #94 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

Quote:
Originally Posted by dkeruza View Post
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.
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.
Woodstock77 is offline  
Reply With Quote
Old December 14th, 2011, 11:47 PM   #95 (permalink)
New Member
 
Join Date: Nov 2011
Posts: 5
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 3 Times in 2 Posts
Default

Quote:
Originally Posted by Woodstock77 View Post
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.
I tried with 3 already. The recovery just freezes.
dkeruza is offline  
Reply With Quote
The Following User Says Thank You to dkeruza For This Useful Post:
Woodstock77 (December 15th, 2011)
Old December 15th, 2011, 12:13 AM   #96 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

Quote:
Originally Posted by dkeruza View Post
I tried with 3 already. The recovery just freezes.
Thanks man. Good to know its not me.
Woodstock77 is offline  
Reply With Quote
Old December 15th, 2011, 05:22 AM   #97 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Dec 2011
Posts: 92
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 27 Times in 15 Posts
Default

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 is offline  
Reply With Quote
Old December 15th, 2011, 08:54 AM   #98 (permalink)
New Member
 
Join Date: Nov 2011
Posts: 5
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 3 Times in 2 Posts
Default

Quote:
Originally Posted by Sebastian404 View Post
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?
Sure, I will do it and post the results.
dkeruza is offline  
Reply With Quote
Old December 15th, 2011, 10:43 AM   #99 (permalink)
Member
 
Woodstock77's Avatar
 
Join Date: Sep 2011
Posts: 382
 
Device(s):
Carrier: Not Provided

Thanks: 55
Thanked 260 Times in 89 Posts
Default

Quote:
Originally Posted by Sebastian404 View Post
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?
No problems after 30+ minutes here.
Woodstock77 is offline  
Reply With Quote
Old December 15th, 2011, 12:10 PM   #100 (permalink)
Junior Member
 
Join Date: Nov 2011
Posts: 16
 
Device(s):
Carrier: Not Provided

Thanks: 2
Thanked 6 Times in 5 Posts
Default

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
SyntaxError is offline  
Reply With Quote
Reply


Go Back   Android Forums > Android Phones > ZTE Warp (N860) > (Boost Mobile) Warp - All Things Root
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 03:14 PM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.