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

Root [Boost Mobile] Testers wanted

no joy on rc9, same screen

hrk1 worked, it's upside down but appears to walk through the menu at least and I am seeing about doing a backup right now, it seems to be working
 
what did everyone go to bed?

I dont like doing it this way, I like to be able to test on my own device before I put anything out


me too man, Quicker testing on ur own device... Im too broke atm, waiting on the insurance dough from my car accident to come in before I upgrade to the warp.. cant wait either. gonna pass my prevail on to my bro with your sexy cm7 on it... lol After the recovery is done, Im going to work on porting cm to the zte warp.
 
no joy on rc9, same screen

hrk1 worked, it's upside down but appears to walk through the menu at least and I am seeing about doing a backup right now, it seems to be working


besides the screen being upside down, does the display otherwise look normal?

do all the keys work?
 
If it does work lets leave the screen upside down. I mean the thing is named Warp right. J/K


lmao yeh ikr... :D sooo did use your own kernel hroark? What arch did you set it to? Im curious....reason is cuz just looking at the extracted ramdisk from your cwm, It looks almost exactly like my own, init.rc and default.prop is diff, but everything else looks the same... i cant seem to figure it out
 
besides the screen being upside down, does the display otherwise look normal?

do all the keys work?
recovery is hanging on backing up system I think, it's been on libra.ko for several minutes now...

I noticed you are using 5.0.2.7, the two other devs were working with 4...

it looks good and the volume and camera button work so it feels good so far. I will reboot and try out some functions
 
lmao yeh ikr... :D sooo did use your own kernel hroark? What arch did you set it to? Im curious....reason is cuz just looking at the extracted ramdisk from your cwm, It looks almost exactly like my own, init.rc and default.prop is diff, but everything else looks the same... i cant seem to figure it out


i will either make a github, or just give you a zip file

here is the current boardconfig

# inherit from the proprietary version -include device/zte/warp/BoardConfigVend - Pastebin.com
 
it did freeze up after a few minutes...

dalvik catch cleared no problem...

reboot recovery didn't seem to go anywhere

reboot system now works
 
it did freeze up after a few minutes...

dalvik catch cleared no problem...

reboot recovery didn't seem to go anywhere

reboot system now hangs and doesn't reboot


does it freeze when it is just sitting there doing nothing

if it is

interdpth is having a similar problem with his CWM port for the samsung transform
 
interesting, on the sd card after attempting the backup the only file was a zero meg one named system.ext4.tar
 
that sounds like the same problem interdpth and PlayfulGod were having with the transform and some other phone

playfulgod did step in here for a sec at my invitation, I sent him some dd dumps from my phone but haven't seen any cwm builds yet from him or heard back in a couple days... I know the golden rule is not to ask for eta's though and I know it was a favor to step over here, so no pressure :)

Great to have you around hroark, love all your work on the prevail, that was my first phone and it has new life with your mods!

this phone is already pretty nice so I am really excited to see what it would look like after you gents get ahold of it...
 
still upside down

reboot recovery doesn't work, just goes back a screen in the menu

I have to hit the hay in a few, I can test a bit tomorrow morning, hopefully some of you night owls can keep the good things flowing till the wee hours:)
 
still upside down

reboot recovery doesn't work, just goes back a screen in the menu

I have to hit the hay in a few, I can test a bit tomorrow morning, hopefully some of you night owls can keep the good things flowing till the wee hours:)
3 more hours before I can test.
 
just messing around some more in there with backup...

I am making a guess that it times out during the backup because if I wait a couple minutes and start it it doesn't get very far, but if I jump straight into backup it makes it past backing up system and gets into bbacking up date before it freezes.

I did also run the error log or whatever that is in the advanced menu with these results:


Starting recovery on Wed Jan 25 04:36:51 2012
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v5.0.2.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /system ext4 /dev/block/mmcblk0p15 (null)
2 /cache ext4 /dev/block/mmcblk0p17 (null)
3 /data ext4 /dev/block/mmcblk0p18 (null)
4 /sdcard vfat /dev/block/mmcblk1p1 (null)
5 /sd-ext ext4 /dev/block/mmcblk0p2 (null)

W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc 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=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GINGERBREAD
ro.build.display.id=full_warp-eng 2.3.7 GINGERBREAD eng.hroark13.20120124.215832 test-keys
ro.build.version.incremental=eng.hroark13.20120124.215832
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Tue Jan 24 21:59:06 EST 2012
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=hroark13
ro.build.host=hroark13-d
ro.build.tags=test-keys
ro.product.model=N860
ro.product.brand=zte
ro.product.name=full_warp
ro.product.device=warp
ro.product.board=warp
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=
ro.build.product=warp
ro.build.description=full_warp-eng 2.3.7 GINGERBREAD eng.hroark13.20120124.215832 test-keys
ro.build.fingerprint=zte/full_warp/warp:2.3.7/GINGERBREAD/eng.hroark13.20120124.215832:eng/test-keys
ro.cm.device=warp
keyguard.no_require_sim=true
ro.rommanager.developerid=cyanogenmod
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.sf.lcd_density=160
qemu.sf.lcd_density=160
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.sf.hwrotation=180
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
ro.emmc=1
init.svc.recovery=running
init.svc.adbd=running

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
 
Back
Top Bottom