Please urgently require cwm or twrp for karbonn A8
Sent from my Karbonn A8 using xda premium
kkbs4u said:
Please urgently require cwm or twrp for karbonn A8
Sent from my Karbonn A8 using xda premium
Click to expand...
Click to collapse
Is your device rooted? If you can provide me with a copy of your devices stock recovery.img file I can try and compile CWMR for you. Let me know if you still have questions.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Recovey Image for Karbonn A8
shimp208 said:
Is your device rooted? If you can provide me with a copy of your devices stock recovery.img file I can try and compile CWMR for you. Let me know if you still have questions.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes sir my device is rooted but i have no stock rom for my device beacuse karbaonn A8 is a new launch device
please tell me how can i grab recovery.img from my device
kkbs4u said:
Yes sir my device is rooted but i have no stock rom for my device beacuse karbaonn A8 is a new launch device
please tell me how can i grab recovery.img from my device
Click to expand...
Click to collapse
If you can use a root file browser to navigate to /cache/recovery/log and then post the output of the log file here I can determine which partition is your recovery partition that you will need to dump.
How to root Karbonn A8
---------- Post added at 01:40 PM ---------- Previous post was at 01:30 PM ----------
[/COLOR]
shimp208 said:
If you can use a root file browser to navigate to /cache/recovery/log and then post the output of the log file here I can determine which partition is your recovery partition that you will need to dump.
Click to expand...
Click to collapse
I think this is the file you needed to find recovery partition
[/COLOR]
7 /recovery emmc /dev/block/platform/sdhci.1/by-name/recovery (null) 0
Click to expand...
Click to collapse
Though This complete output of log file.
[/COLOR]
Starting recovery on Fri Sep 20 17:34:52 2013
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
2 /system ext4 /dev/block/platform/sdhci.1/by-name/system (null) 0
3 /data ext4 /dev/block/platform/sdhci.1/by-name/userdata (null) -16384
4 /cache ext4 /dev/block/platform/sdhci.1/by-name/cache (null) 0
5 /misc emmc /dev/block/platform/sdhci.1/by-name/misc (null) 0
6 /boot emmc /dev/block/platform/sdhci.1/by-name/boot (null) 0
7 /recovery emmc /dev/block/platform/sdhci.1/by-name/recovery (null) 0
8 /u-boot emmc /dev/block/platform/sdhci.1/by-name/u-boot (null) 0
9 /dt-blob emmc /dev/block/platform/sdhci.1/by-name/dt-blob (null) 0
10 /cp-boot emmc /dev/block/platform/sdhci.1/by-name/cp-boot (null) 0
11 /cp-image emmc /dev/block/platform/sdhci.1/by-name/cp-image (null) 0
12 /dsp-dram emmc /dev/block/platform/sdhci.1/by-name/dsp-dram (null) 0
13 /dsp-pram emmc /dev/block/platform/sdhci.1/by-name/dsp-pram (null) 0
14 /sys-parm-ind emmc /dev/block/platform/sdhci.1/by-name/sys-parm-ind (null) 0
15 /parm-spml-ind emmc /dev/block/platform/sdhci.1/by-name/parm-spml-ind (null) 0
16 /kernel-dtb emmc /dev/block/platform/sdhci.1/by-name/kernel-dtb (null) 0
locale is [en_US]
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
installing_text: en (324 x 38 @ 411)
erasing_text: en (109 x 38 @ 312)
no_command_text: en (172 x 38 @ 312)
error_text: en (64 x 38 @ 312)
Command: "/sbin/recovery"
ro.boot.console=ttyS0
ro.boot.mode=recovery
ro.boot.serialno=F0068A1880601039
ro.serialno=F0068A1880601039
ro.bootmode=recovery
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=w68_mb_p1
ro.revision=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp,adb
persist.brcm.log=auto
persist.brcm.cp_crash=auto
persist.brcm.ap_crash=auto
persist.brcm.force_ramdump=0
ro.build.id=JDQ39
ro.build.display.id=JDQ39.TBW680018_8884_V000082
ro.build.version.incremental=TBW680018_8884_V000082
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Wed Aug 14 15:33:21 CST 2013
ro.build.date.utc=1376465601
ro.build.type=user
ro.build.user=ccadmin
ro.build.host=BUILD12
ro.build.tags=release-keys
ro.product.model=Karbonn A8
ro.product.brand=Karbonn
ro.product.name=hawaii_garnet_c_w68tk
ro.product.device=hawaii_garnet_c_w68tk
ro.product.board=hawaii
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Karbonn
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=hawaii
ro.build.product=hawaii_garnet_c_w68tk
ro.build.description=hawaii_garnet_c_w68tk-user 4.2.2 JDQ39 TBW680018_8884_V000082 release-keys
ro.build.characteristics=default
ro.max_fb_resolution=1280x720
rild.libpath=/system/lib/libbrcm_ril.so
ro.sf.lcd_density=240
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
awesome.lateness=200
gralloc.use_sync_mode=true
nuplayer.eos.timeout=3
drm.service.enabled=true
sf.metadata_use_plat_sw_codecs=1
sf.metadata_retrv_hw_codecs=1
persist.audio.pcmout1.sweq=ON
persist.audio.pcmout2.sweq=ON
init.svc.adbd=running
persist.sys.panic.dump.debug=0
ro.config.builtin_cdrom=false
persist.sys.timezone=Asia/Calcutta
ro.config.ringtone_standby=Karbonn.mp3
ro.config.ringtone_2=Karbonn.mp3
ro.config.ringtone=Karbonn.mp3
ro.config.notification_sound=F1_New_SMS.ogg
persist.sys.language=en
ro.storage.internal.reserved.mb=50
ro.config.fontscale=1
persist.sys.country=US
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.2_r2
dalvik.vm.jniopts=warnonly
ro.bt.bdaddr_path=/data/misc/bluetooth/btmac.txt
ro.opengles.version=131072
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.com.android.dataroaming=false
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
ro.wap.push=1
persist.sys.cmas.enable=0
ro.dual.sim.phone=1
persist.sys.bpmsetting.enable=1
persist.sys.pt.factory_test=11111111111110111111111
init.svc.recovery=running
I:Saving locale "en_US"
/res/string_utf8.txt
num:33
count1
count2
count3
count4
count5
count6
count7
count8
count9
count10
count11
count12
count13
count14
count15
count16
count17
count18
count19
count20
count21
count22
count23
count24
count25
count26
count27
count28
count29
count30
count31
count32
/res/string_utf8.txt
num:2
count1
I:Saving locale "en_US"
I:Saving locale "en_US"
Click to expand...
Click to collapse
technicure said:
I think this is the file you needed to find recovery partition
Though This complete output of log file.
Click to expand...
Click to collapse
Great if you can then run this command from ADB shell (Make sure to run the command as root) and upload the recovery.img that the command outputs I can try and compile CWMR for you :
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
Here the Recovery Log Karbonn A8
shimp208 said:
Great if you can then run this command from ADB shell (Make sure to run the command as root) and upload the recovery.img that the command outputs I can try and compile CWMR for you :
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
Click to expand...
Click to collapse
tarting recovery on Thu Oct 3 07:10:02 2013
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
2 /system ext4 /dev/block/platform/sdhci.1/by-name/system (null) 0
3 /data ext4 /dev/block/platform/sdhci.1/by-name/userdata (null) -16384
4 /cache ext4 /dev/block/platform/sdhci.1/by-name/cache (null) 0
5 /misc emmc /dev/block/platform/sdhci.1/by-name/misc (null) 0
6 /boot emmc /dev/block/platform/sdhci.1/by-name/boot (null) 0
7 /recovery emmc /dev/block/platform/sdhci.1/by-name/recovery (null) 0
8 /u-boot emmc /dev/block/platform/sdhci.1/by-name/u-boot (null) 0
9 /dt-blob emmc /dev/block/platform/sdhci.1/by-name/dt-blob (null) 0
10 /cp-boot emmc /dev/block/platform/sdhci.1/by-name/cp-boot (null) 0
11 /cp-image emmc /dev/block/platform/sdhci.1/by-name/cp-image (null) 0
12 /dsp-dram emmc /dev/block/platform/sdhci.1/by-name/dsp-dram (null) 0
13 /dsp-pram emmc /dev/block/platform/sdhci.1/by-name/dsp-pram (null) 0
14 /sys-parm-ind emmc /dev/block/platform/sdhci.1/by-name/sys-parm-ind (null) 0
15 /parm-spml-ind emmc /dev/block/platform/sdhci.1/by-name/parm-spml-ind (null) 0
16 /kernel-dtb emmc /dev/block/platform/sdhci.1/by-name/kernel-dtb (null) 0
locale is [en_US]
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
installing_text: en (324 x 38 @ 411)
erasing_text: en (109 x 38 @ 312)
no_command_text: en (172 x 38 @ 312)
error_text: en (64 x 38 @ 312)
Command: "/sbin/recovery"
ro.boot.console=ttyS0
ro.boot.mode=recovery
ro.boot.serialno=F0068A1880601977
ro.serialno=F0068A1880601977
ro.bootmode=recovery
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=w68_mb_p1
ro.revision=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp,adb
persist.brcm.log=auto
persist.brcm.cp_crash=auto
persist.brcm.ap_crash=auto
persist.brcm.force_ramdump=0
ro.build.id=JDQ39
ro.build.display.id=JDQ39.TBW680018_8884_V000082
ro.build.version.incremental=TBW680018_8884_V000082
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Wed Aug 14 15:33:21 CST 2013
ro.build.date.utc=1376465601
ro.build.type=user
ro.build.user=ccadmin
ro.build.host=BUILD12
ro.build.tags=release-keys
ro.product.model=Karbonn A8
ro.product.brand=Karbonn
ro.product.name=hawaii_garnet_c_w68tk
ro.product.device=hawaii_garnet_c_w68tk
ro.product.board=hawaii
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Karbonn
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=hawaii
ro.build.product=hawaii_garnet_c_w68tk
ro.build.description=hawaii_garnet_c_w68tk-user 4.2.2 JDQ39 TBW680018_8884_V000082 release-keys
ro.build.characteristics=default
ro.max_fb_resolution=1280x720
rild.libpath=/system/lib/libbrcm_ril.so
ro.sf.lcd_density=240
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
awesome.lateness=200
gralloc.use_sync_mode=true
nuplayer.eos.timeout=3
drm.service.enabled=true
sf.metadata_use_plat_sw_codecs=1
sf.metadata_retrv_hw_codecs=1
persist.audio.pcmout1.sweq=ON
persist.audio.pcmout2.sweq=ON
init.svc.adbd=running
persist.sys.panic.dump.debug=0
ro.config.builtin_cdrom=false
persist.sys.timezone=Asia/Calcutta
ro.config.ringtone_standby=Karbonn.mp3
ro.config.ringtone_2=Karbonn.mp3
ro.config.ringtone=Karbonn.mp3
ro.config.notification_sound=F1_New_SMS.ogg
persist.sys.language=en
ro.storage.internal.reserved.mb=50
ro.config.fontscale=1
persist.sys.country=US
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.2_r2
dalvik.vm.jniopts=warnonly
ro.bt.bdaddr_path=/data/misc/bluetooth/btmac.txt
ro.opengles.version=131072
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.com.android.dataroaming=false
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
ro.wap.push=1
persist.sys.cmas.enable=0
ro.dual.sim.phone=1
persist.sys.bpmsetting.enable=1
persist.sys.pt.factory_test=11111111111111111111111
init.svc.recovery=running
I:Saving locale "en_US"
/res/string_utf8.txt
num:33
count1
count2
count3
count4
count5
count6
count7
count8
count9
count10
count11
count12
count13
count14
count15
count16
count17
count18
count19
count20
count21
count22
count23
count24
count25
count26
count27
count28
count29
count30
count31
count32
/res/string_utf8.txt
num:2
count1
I:Saving locale "en_US"
I:Saving locale "en_US"
kkbs4u said:
tarting recovery on Thu Oct 3 07:10:02 2013
recovery filesystem table
Click to expand...
Click to collapse
Thanks, now that you have posted the recovery.log file please run the following command as root from ADB shell and upload the recovery.img file that results:
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
This command will dump a copy of your stock recovery.img file to your phones storage which if you then upload here I can try and compile CWMR for.
Recovery Karbonn A8
shimp208 said:
Thanks, now that you have posted the recovery.log file please run the following command as root from ADB shell and upload the recovery.img file that results:
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
This command will dump a copy of your stock recovery.img file to your phones storage which if you then upload here I can try and compile CWMR for.
Click to expand...
Click to collapse
Sir i am facing a problem in this command error is "Permission denied"
Solve "Permission Denied" when running cat command
kkbs4u said:
Sir i am facing a problem in this command error is "Permission denied"
Click to expand...
Click to collapse
You will need root access to run this command.
As shimp208 said as root from ADB shell
Connect phone USB debugging enabled
Run
Code:
adb shell
then run
Code:
su
and then
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
Or you can even run it from phone install terminal emulator from play store
Run
Code:
su
And then
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
Karbonn A8 Stock Recovery
shimp208 said:
Great if you can then run this command from ADB shell (Make sure to run the command as root) and upload the recovery.img that the command outputs I can try and compile CWMR for you :
Click to expand...
Click to collapse
filefactory.com/file/4csn0f3x0hvz/recovery.img Karbonn A8 Stock Recovery
I am not allowed to post link please add www before address above
Thank You.
My phone currently have Stock Android 4.2.2
Can you compile or port AOSP or cyanogenmod for my device
Or guide me to do so
I can provide any files(Hardware specific, libries) needed from my phone
Because it is slightly modified from AOSP
In notification insted of toggling wifi/bluetooth/data on/off it opens selected menu in setting
And there is no option in notification for gps, screen timeout and brightness
And there is also some problem with camera and flash
Photos taken in bright light and daylight are great.
But in dark when clicked shows photo on display is as it should be but saved photo has either dark from one side or too bright or it looks like Black&White photo.
And android system uses ~70% battery I don't think that is normal. After turning of wifi & mobile network location Android OS consumes ~23% and Android System ~13% of battery. Still phone has 24 hours of battery backup.
Otherwise phone is great. Can play 1080p Videos smoothly with s/w or h/w decoding. Good at multitasking. Antutu Benchmark score is same as Samsung Galaxy S2. Operating system is stable not crashed yet in 1 month of use
It would be better if I can get Android 4.3 for it If not possible due to binary unavailability or buggy Android 4.2.2 will fine with notification toggle and camera problem solved.
Thanks for attention.
technicure said:
filefactory.com/file/4csn0f3x0hvz/recovery.img Karbonn A8 Stock Recovery
I am not allowed to post link please add www before address above
Thank You.
My phone currently have Stock Android 4.2.2
Can you compile or port AOSP or cyanogenmod for my device
Or guide me to do so
I can provide any files(Hardware specific, libries) needed from my phone
Because it is slightly modified from AOSP
In notification insted of toggling wifi/bluetooth/data on/off it opens selected menu in setting
And there is no option in notification for gps, screen timeout and brightness
And there is also some problem with camera and flash
Photos taken in bright light and daylight are great.
But in dark when clicked shows photo on display is as it should be but saved photo has either dark from one side or too bright or it looks like Black&White photo.
And android system uses ~70% battery I don't think that is normal. After turning of wifi & mobile network location Android OS consumes ~23% and Android System ~13% of battery. Still phone has 24 hours of battery backup.
Otherwise phone is great. Can play 1080p Videos smoothly with s/w or h/w decoding. Good at multitasking. Antutu Benchmark score is same as Samsung Galaxy S2. Operating system is stable not crashed yet in 1 month of use
It would be better if I can get Android 4.3 for it If not possible due to binary unavailability or buggy Android 4.2.2 will fine with notification toggle and camera problem solved.
Thanks for attention.
Click to expand...
Click to collapse
Attached to this post is the Clockworkmod Recovery I compiled for your Karbonn A8. To test the recovery image I would recommend booting into fastboot mode on your device and then running the following command:
Code:
fastboot boot cwm-a8-test.img
And then see if everything works correctly (Can make backup, restore backup, etc.). If everything works correctly you can then flash the recovery using the command:
Code:
fastboot flash recovery cwm-a8-test.img
As far as compiling AOSP or Cyanogenmod for your device I can try and guide you through that process but I am by no means an expert in porting ROM's. Let me know if the recovery correctly for you .
Recovery is working
shimp208 said:
Attached to this post is the Clockworkmod Recovery I compiled for your Karbonn A8. To test the recovery image I would recommend booting into fastboot mode on your device and then running the following command:
Click to expand...
Click to collapse
It was showing error
Code:
[email protected]:~> fastboot boot cwm-a8-test.img
downloading 'boot.img'...
OKAY [ 0.316s]
booting...
FAILED (remote: boot command not supported)
finished. total time: 0.316s
That's why I directly flashed recovery. It is working I tried backup, restore, data wipe, mount/unmount and format.
No performance issues,
But everything shown on display is shrunk to left half of display another half is blank.
Selected option shows white on pink but others are pink on pink. (background is texture with most of the pink color)
technicure said:
It was showing error
Code:
[email protected]:~> fastboot boot cwm-a8-test.img
downloading 'boot.img'...
OKAY [ 0.316s]
booting...
FAILED (remote: boot command not supported)
finished. total time: 0.316s
That's why I directly flashed recovery. It is working I tried backup, restore, data wipe, mount/unmount and format.
No performance issues,
But everything shown on display is shrunk to left half of display another half is blank.
Selected option shows white on pink but others are pink on pink. (background is texture with most of the pink color)
Click to expand...
Click to collapse
This is likely a graphics farmebuffer issue, if you could take a picture of what the recovery is showing (With the graphic errors) and upload it here I can try and take a look at it for you. Overall, I'm glad apart from the messed up graphics it's working correctly.
shimp208 said:
This is likely a graphics farmebuffer issue, if you could take a picture of what the recovery is showing (With the graphic errors) and upload it here I can try and take a look at it for you. Overall, I'm glad apart from the messed up graphics it's working correctly.
Click to expand...
Click to collapse
I don't have another device at this time to take picture I'll take picture after some time and upload.
I don't get what you said Picture with graphics errors It isn't showing any error.
technicure said:
I don't have another device at this time to take picture I'll take picture after some time and upload.
I don't get what you said Picture with graphics errors It isn't showing any error.
Click to expand...
Click to collapse
I apologize for any confusion. What I meant was if whenever you have a chance if you can take a picture of your device in recovery mode and then upload it. This way I can see what's wrong with the recoverys graphics.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Recovery messy graphics photos
shimp208 said:
I apologize for any confusion. What I meant was if whenever you have a chance if you can take a picture of your device in recovery mode and then upload it. This way I can see what's wrong with the recoverys graphics.
Click to expand...
Click to collapse
I have attached photos of my phone in recovery mode.
Please take a look.
Thank you.
Karbonn A8 CWM OR TWRP Recovery
technicure said:
You will need root access to run this command.
As shimp208 said as root from ADB shell
Connect phone USB debugging enabled
Run
Code:
adb shell
then run
Code:
su
and then
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
Or you can even run it from phone install terminal emulator from play store
Run
Code:
su
And then
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
Click to expand...
Click to collapse
Thank You Sir
I will try for this
Working recovery for Karbonn
kkbs4u said:
Thank You Sir
I will try for this
Click to expand...
Click to collapse
You don't need to upload stock recovery.
I have uploaded it. and clockworkmod recovery is available complied by shimp208
Here is download link for cwm-a8-test
It has some graphics rendering issues but apart from that it works correctly and usable.
If you have any issues regarding to installation feel free to ask.
Karbonn A8 CWM & TWRP recovery
technicure said:
You will need root access to run this command.
As shimp208 said as root from ADB shell
Connect phone USB debugging enabled
Run
Code:
adb shell
then run
Code:
su
and then
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
Or you can even run it from phone install terminal emulator from play store
Run
Code:
su
And then
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
Click to expand...
Click to collapse
here is Karbonn A8 stock Recovery
Related
Hello
this morning i try to install ics with S.onyTablet.S v2.7 [ALLinONE]
i go in region changer i modified my FR tablet to US
after i restart and since my tablet show sony logo at start and shutdown
i try factory reset in recovery mode but no success
i would try update from sdcard but
with some update ota but i have
"Erohibit update as a result of checking version or base sku"
i need the good update
signed-nbx03_005-ota-0042.002.zip
i think because french ro.sony.sku.base is nbx03_005
hdi-95 said:
Hello
this morning i try to install ics with S.onyTablet.S v2.7 [ALLinONE]
i go in region changer i modified my FR tablet to US
after i restart and since my tablet show sony logo at start and shutdown
i try factory reset in recovery mode but no success
i would try update from sdcard but
with some upadate ota but i have
"Erohibit update as a result of checking version or base sku"
i need the good update
signed-nbx03_005-ota-0042.002.zip
i think because french ro.sony.sku.base is nbx03_005
Click to expand...
Click to collapse
i didnt bother changing my region from uk to us as the tool does it anyway, reset it to france and try again
thanks for your answer
how i can reset it ?
the tool work only with device in USB debugging mode and i have only recovery mode access
hdi-95 said:
Hello
this morning i try to install ics with S.onyTablet.S v2.7 [ALLinONE]
i go in region changer i modified my FR tablet to US
after i restart and since my tablet show sony logo at start and shutdown
i try factory reset in recovery mode but no success
i would try update from sdcard but
with some upadate ota but i have
"Erohibit update as a result of checking version or base sku"
i need the good update
signed-nbx03_005-ota-0042.002.zip
i think because french ro.sony.sku.base is nbx03_005
Click to expand...
Click to collapse
Read all steps carefully. You need to run "disable recovery update.zip signature check" option
sebarkh said:
Read all steps carefully. You need to run "disable recovery update.zip signature check" option
Click to expand...
Click to collapse
Hello !
I've got the same problem, (reboot and ... nothing) , I have try with my tablet on the recovery mode (because me too, i just have this choice) and select "disable recovery.... but nothing. It told me something like that :
" ' su ' binary not found. You need root to use this function. Press any key to exit."
What can we do?
hdi-95 said:
Hello
this morning i try to install ics with S.onyTablet.S v2.7 [ALLinONE]
i go in region changer i modified my FR tablet to US
after i restart and since my tablet show sony logo at start and shutdown
i try factory reset in recovery mode but no success
i would try update from sdcard but
with some upadate ota but i have
"Erohibit update as a result of checking version or base sku"
i need the good update
signed-nbx03_005-ota-0042.002.zip
i think because french ro.sony.sku.base is nbx03_005
Click to expand...
Click to collapse
I have the same problem. I've tried to get condi to help but that doesn't seem to be working either. I've tried everything. Tablet is still bricked.
hey !
i think the candi's tool canot detecte my device because it is not realy in usb debugging
when i am in recovery mode i have this
Code:
M:\Dev\android-sdk-windows\platform-tools>adb devices
List of devices attached
42890c7433f72d7 recovery
here my recovery.log
Code:
Starting recovery on Sat Apr 28 05:47:13 2012
framebuffer: fd 4 (1280 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /configs ext2 /dev/block/mmcblk0p1 (null) 0
2 /system0 ext4 /dev/block/mmcblk0p2 (null) 0
3 /system1 ext4 /dev/block/mmcblk0p3 (null) 0
4 /cache ext4 /dev/block/mmcblk0p4 (null) 0
5 /misc emmc /dev/block/mmcblk0p5 (null) 0
6 /staging ext4 /dev/block/mmcblk0p6 (null) 0
7 /blflags ext4 /dev/block/mmcblk0p7 (null) 0
8 /datapp ext4 /dev/block/mmcblk0p8 (null) 0
9 /log ext4 /dev/block/mmcblk0p9 (null) 0
10 /data ext4 /dev/block/mmcblk0p10 (null) 0
11 /vsd ext4 /dev/block/mmcblk0p11 (null) 0
12 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
13 /boot emmc boot (null) 0
14 /recovery emmc recovery (null) 0
15 /system ext4 system (null) 0
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.build.id=THMAS0042
ro.build.display.id=THMAS0042
ro.build.version.incremental=0042.002
ro.build.version.sdk=13
ro.build.version.codename=REL
ro.build.version.release=3.2.1
ro.build.date=Thu Dec 1 02:57:47 JST 2011
ro.build.date.utc=1322675867
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build8
ro.build.tags=test-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
ro.product.name=nbx03_002
ro.product.device=nbx03
ro.product.board=nbx03
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=nbx03
ro.build.description=nbx03_005-user 3.2.1 THMAS0042 0042.002 test-keys
ro.build.fingerprint=Sony/nbx03_002/nbx03:3.2.1/THMAS0042/0042.002:user/test-keys
ro.build.characteristics=tablet,nosdcard
ro.opengles.version=131072
wifi.interface=wlan0
ro.ethernet.interface=eth0
ro.ethernet.autoEnable=yes
rild.libargs=-d /dev/ttyACM1 -i rmnet0
ro.sony.sound.enabled=true
ro.separated.external.storage=true
ro.external.storage.removable=false
ro.tether.denied=true
windowsmgr.max_events_per_sec=120
ro.sony.display.release=release2
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=3.2_r4
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.com.google.clientidbase=android-sony
ro.sony.wifisleep=0
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.sony.update.service_id=nbx03_005
ro.sony.sku.base=nbx03_005
ro.sony.build.id=THMAS0052400
ro.sony.build.incremental=111201023
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.sony.wan.ipv6.enable=false
ro.sony.stayawake.hidden=false
ro.sony.wan.fixed_apns=0
ro.factorytest=0
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=wifi-only
ro.bootloader=0x00000008
ro.hardware=nbx03
ro.revision=0
init.svc.recovery=running
init.svc.nfx_daemon=running
init.svc.adbd=running
i think in my state the only option I have is that someone give me an update with the right "ro.sony.sku.base" : nbx03_005
thanks you
may be it can be recoverd
hdi-95 said:
hey !
i think the candi's tool canot detecte my device because it is not realy in usb debugging
when i am in recovery mode i have this
Code:
M:\Dev\android-sdk-windows\platform-tools>adb devices
List of devices attached
42890c7433f72d7 recovery
did u have root before? if it was there, may be there is a chance to unbrick your device..
Click to expand...
Click to collapse
yes my device was rooted but
a tried factory reset yesterday
get one more file from recovery! /tmp dir:
region.prop
i think you are confused with Download mode and debugging mode,
Just enable debugging mode is enough Settings > development section
Mahaco :
i cant go to android settings because my tablet run only in recovery mode
when i want start android device shutdown after sony logo screen
condi :
Code:
M:\Dev\android-sdk-windows\platform-tools>adb pull tmp
pull: building file list...
pull: tmp/recovery.log -> ./recovery.log
pull: tmp/nfx_daemon_flash.txt -> ./nfx_daemon_flash.txt
pull: tmp/random -> ./random
pull: tmp/metadata -> ./metadata
4 files pulled. 0 files skipped.
184 KB/s (8827 bytes in 0.046s)
i dont have any region.prop file
but here the end of my recovery.log when i try to instal an update
Code:
-- Install /sdcard ...
Finding update package...
I:Update location: /sdcard/signed-nbx03_001-ota-120410004.zip
Desklunvr update package...
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1465 bytes; signature 1447 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Checking version is passed, 111201023 -> 120410004
minzip: file is empty
minzip: Map of '/configs/region.zip' failed
Fail to open /configs/region.zip
E:Prohibit update as a result of checking version or base sku
Installation aborted.
excusez-moi didn't saw that.
i had something similair but i did not deleted my region file,
but i think it was deleted back then by condi's tool and that you did it by yourself you made the same problem i think i had my tab repaired by Sony.
Br
Mahaco
I'm afraid to send it to sony and answer me "violation of terms of use" product warranty lost
is there another solution ?
hdi-95 said:
I'm afraid to send it to sony and answer me "violation of terms of use" product warranty lost
is there another solution ?
Click to expand...
Click to collapse
I am affraid there isn't any further options, mine was bricked too and they replaced a MTB chip which is very important, if all values are zero like mine were you could say like i did: I did a factory reset and it restarted then it didn't do anything anymore you must seek for a company in your envirement who are Sony certified they will send it to sony you only have to pay the sending costs, i did a recovery.log pull too and i sended it to Condi maby you could compare those to recovery logs
and see what are the difference.
I hope that condi might find a sollution, but i am still affraid that you will have to send it back,
Sorry for my english
YF.
Mahaco
ok thanks you for your information
i wait condi's response and i hope he could find a solution otherwise i will contact sony center to send it back
hdi-95 said:
ok thanks you for your information
i wait condi's response and i hope he could find a solution otherwise i will contact sony center to send it back
Click to expand...
Click to collapse
how were you able to get adb to recognize your device in recovery?
Edit: Forget it I got it. I don't have a region.prop either!
MSmith1 said:
how were you able to get adb to recognize your device in recovery?
Edit: Forget it I got it. I don't have a region.prop either!
Click to expand...
Click to collapse
So you are saying that you also have an bricked device?
if so can you do a recovery.log pull with adb and compare it with the one from Hdi-95
Maby you can see a difference and then there could be a solution for you, because i think Hdi-95 his device is not repaiable for now i think sadly.
First flash an update on you device and after it fails connect your tablet and pull recovery:
adb pull /tmp/recovery.log
maby its something for condi to look at it or just like i said compare
or if i said something stupid dont react.
yf,
Mahaco
so if i get the good update like
"signed-nbx03_005-ota-0042.002.zip"
i will try install from sdcard
no body have a links like
http://info.update.sony.net/ST002/nbx03_001/contents/0014/signed-nbx03_001-ota-120410004.zip
i try
http://info.update.sony.net/ST001/nbx03_005/contents/0014/signed-nbx03_005-ota-0042.002.zip
but file not found
hdi-95 said:
so if i get the good update like
"signed-nbx03_005-ota-0042.002.zip"
i will try install from sdcard
no body have a links like
http://info.update.sony.net/ST002/nbx03_001/contents/0014/signed-nbx03_001-ota-120410004.zip
i try
http://info.update.sony.net/ST001/nbx03_005/contents/0014/signed-nbx03_005-ota-0042.002.zip
but file not found
Click to expand...
Click to collapse
But you did everything on your external SD right?. can you use _Hack zip and then if that failes use the ****om Signed zip?. ( ICS )
Hey guys,
today i want to upgrade my tablet s to ics. I tried to use condis AiO Tool, but several times i doesnt work. Then I think **ck of i upgrade without root and tried to install the ota update.
my tablet download it but i can´t install (view description below // can´t post links under 10 posts sorry). Open the AiO tool again and close the rescue backdoor and unroot my device.
after that the i got the same failure :S
can u say me how to get ics? I think the tablet isn´t bricked, because i can start it normaly and it boots normaly.
Now I can´t root and install ics
greetz
//
Erohibit update as a result of checking version or base sku
//
in the prop was something like verion: nbx03_007
What version of AiO you're using?
meowz said:
Hey guys,
today i want to upgrade my tablet s to ics. I tried to use condis AiO Tool, but several times i doesnt work. Then I think **ck of i upgrade without root and tried to install the ota update.
my tablet download it but i can´t install (view description below // can´t post links under 10 posts sorry). Open the AiO tool again and close the rescue backdoor and unroot my device.
after that the i got the same failure :S
can u say me how to get ics? I think the tablet isn´t bricked, because i can start it normaly and it boots normaly.
Now I can´t root and install ics
greetz
//
Erohibit update as a result of checking version or base sku
//
in the prop was something like verion: nbx03_007
Click to expand...
Click to collapse
So what version OS you have?? HC?
Can you please try the install and use 'adb pull /tmp' and post the recover.log here
Stifilz
stifilz said:
So what version OS you have?? HC?
Can you please try the install and use 'adb pull /tmp' and post the recover.log here
Stifilz
Click to expand...
Click to collapse
Got an "adb: permission denied" Error.
Im using the newest Version of AiO Tool, 4.1.
Android Version: 3.2.1 (r2)
Kernel: 2.6.36.3 [email protected] #1
edit: When I use this ADB ( http://forum.xda-developers.com/showthread.php?t=1488822 ) auto installer and go into the cmd it says pull /tmp is a wrong command
meowz said:
Got an "adb: permission denied" Error.
Im using the newest Version of AiO Tool, 4.1.
Android Version: 3.2.1 (r2)
Kernel: 2.6.36.3 [email protected] #1
edit: When I use this ADB ( http://forum.xda-developers.com/showthread.php?t=1488822 ) auto installer and go into the cmd it says pull /tmp is a wrong command
Click to expand...
Click to collapse
Sorry try adb pull tmp
stifilz said:
Sorry try adb pull tmp
Click to expand...
Click to collapse
In AiO tool he can´t find my tablet "error: device not found"
And in the Sony ADB from the post bevor he says "remote object 'tmp' does not exist"
Maybe this information ist helpful:
In AiO tool at the rooting option after a few reboots he says that he only has read permisson.
meowz said:
In AiO tool he can´t find my tablet "error: device not found"
And in the Sony ADB from the post bevor he says "remote object 'tmp' does not exist"
Maybe this information ist helpful:
In AiO tool at the rooting option after a few reboots he says that he only has read permisson.
Click to expand...
Click to collapse
Please follow my FAQ in signature to correctly set up adb and make sure it is working in both recovery and normal modes.
stifilz said:
Please follow my FAQ in signature to correctly set up adb and make sure it is working in both recovery and normal modes.
Click to expand...
Click to collapse
Finally got it.
In recovery and normal mode, he finds my tablet.
meowz said:
Finally got it.
In recovery and normal mode, he finds my tablet.
Click to expand...
Click to collapse
Okey dokey, can you pull the recovery.log now and I will have a peek
Stifilz
Im gonna freak out here
Can´t open condis tool for the shell. Can´t pass the update check with the _Offupdate file and the tool says that "findstr" is a wrong command.
I have downloaded it again and again. Everytime the same error. Don´t know what to to (
I have adb installed like in your tut
The new Java SDK from the Java Website
The new Android SDK from their website
USB debugging mode on tablet s
In the command promt i can find my tab in normal and recovery mode, but still can´t pull tmp
meowz said:
Im gonna freak out here
Can´t open condis tool for the shell. Can´t pass the update check with the _Offupdate file and the tool says that "findstr" is a wrong command.
I have downloaded it again and again. Everytime the same error. Don´t know what to to (
I have adb installed like in your tut
The new Java SDK from the Java Website
The new Android SDK from their website
USB debugging mode on tablet s
In the command promt i can find my tab in normal and recovery mode, but still can´t pull tmp
Click to expand...
Click to collapse
Can you pull anything? Have you tried adb pull /
That will pull everything... use Ctrl + C to stop it.
You are trying to pull in recovery? What sort of error you getting?
It should be working if ADB is :|
Ok, don´t know what i does, but now I can pull the recovery.log. But where is it saved?
meowz said:
Ok, don´t know what i does, but now I can pull the recovery.log. But where is it saved?
Click to expand...
Click to collapse
Your current working directory. Normally C:\Users\(UserName). I normally cd to Desktop and 'pull' it to there.
ptippre turns
Ok, don`t know what to post, but here is everything from the relog file. Thanks a lot for your help, hope i can get ICS and root on my Tablet S
Code:
Starting recovery on Tue Oct 9 11:32:27 2012
framebuffer: fd 4 (1280 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /configs ext2 /dev/block/mmcblk0p1 (null) 0
2 /system0 ext4 /dev/block/mmcblk0p2 (null) 0
3 /system1 ext4 /dev/block/mmcblk0p3 (null) 0
4 /cache ext4 /dev/block/mmcblk0p4 (null) 0
5 /misc emmc /dev/block/mmcblk0p5 (null) 0
6 /staging ext4 /dev/block/mmcblk0p6 (null) 0
7 /blflags ext4 /dev/block/mmcblk0p7 (null) 0
8 /datapp ext4 /dev/block/mmcblk0p8 (null) 0
9 /log ext4 /dev/block/mmcblk0p9 (null) 0
10 /data ext4 /dev/block/mmcblk0p10 (null) 0
11 /vsd ext4 /dev/block/mmcblk0p11 (null) 0
12 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
13 /boot emmc boot (null) 0
14 /recovery emmc recovery (null) 0
15 /system ext4 system (null) 0
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.build.id=THMASU0035
ro.build.display.id=THMASU0035
ro.build.version.incremental=0035.014
ro.build.version.sdk=13
ro.build.version.codename=REL
ro.build.version.release=3.2.1
ro.build.date=Fri Nov 4 15:38:24 JST 2011
ro.build.date.utc=1320388704
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build5
ro.build.tags=test-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
ro.product.name=nbx03_014
ro.product.device=nbx03
ro.product.board=nbx03
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=nbx03
ro.build.description=nbx03_007-user 3.2.1 THMASU0035 0035.014 test-keys
ro.build.fingerprint=Sony/nbx03_014/nbx03:3.2.1/THMASU0035/0035.014:user/test-keys
ro.build.characteristics=tablet,nosdcard
ro.opengles.version=131072
wifi.interface=wlan0
ro.ethernet.interface=eth0
ro.ethernet.autoEnable=yes
rild.libargs=-d /dev/ttyACM1 -i rmnet0
ro.sony.sound.enabled=true
ro.separated.external.storage=true
ro.external.storage.removable=false
ro.tether.denied=true
windowsmgr.max_events_per_sec=120
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=3.2_r3
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.com.google.clientidbase=android-sony
ro.sony.wifisleep=0
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.sony.update.service_id=nbx03_007
ro.sony.sku.base=nbx03_007
ro.sony.build.id=THMASU0075300
ro.sony.build.incremental=111104011
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.factorytest=0
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=wifi-only
ro.bootloader=0x00000008
ro.hardware=nbx03
ro.revision=0
init.svc.recovery=running
init.svc.nfx_daemon=running
init.svc.adbd=running
meowz said:
Ok, don`t know what to post, but here is everything from the relog file. Thanks a lot for your help, hope i can get ICS and root on my Tablet S
Code:
Starting recovery on Tue Oct 9 11:32:27 2012
framebuffer: fd 4 (1280 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /configs ext2 /dev/block/mmcblk0p1 (null) 0
2 /system0 ext4 /dev/block/mmcblk0p2 (null) 0
3 /system1 ext4 /dev/block/mmcblk0p3 (null) 0
4 /cache ext4 /dev/block/mmcblk0p4 (null) 0
5 /misc emmc /dev/block/mmcblk0p5 (null) 0
6 /staging ext4 /dev/block/mmcblk0p6 (null) 0
7 /blflags ext4 /dev/block/mmcblk0p7 (null) 0
8 /datapp ext4 /dev/block/mmcblk0p8 (null) 0
9 /log ext4 /dev/block/mmcblk0p9 (null) 0
10 /data ext4 /dev/block/mmcblk0p10 (null) 0
11 /vsd ext4 /dev/block/mmcblk0p11 (null) 0
12 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
13 /boot emmc boot (null) 0
14 /recovery emmc recovery (null) 0
15 /system ext4 system (null) 0
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.build.id=THMASU0035
ro.build.display.id=THMASU0035
ro.build.version.incremental=0035.014
ro.build.version.sdk=13
ro.build.version.codename=REL
ro.build.version.release=3.2.1
ro.build.date=Fri Nov 4 15:38:24 JST 2011
ro.build.date.utc=1320388704
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build5
ro.build.tags=test-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
[B]ro.product.name=nbx03_014[/B]
ro.product.device=nbx03
ro.product.board=nbx03
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=nbx03
ro.build.description=nbx03_007-user 3.2.1 THMASU0035 0035.014 test-keys
ro.build.fingerprint=Sony/nbx03_014/nbx03:3.2.1/THMASU0035/0035.014:user/test-keys
ro.build.characteristics=tablet,nosdcard
ro.opengles.version=131072
wifi.interface=wlan0
ro.ethernet.interface=eth0
ro.ethernet.autoEnable=yes
rild.libargs=-d /dev/ttyACM1 -i rmnet0
ro.sony.sound.enabled=true
ro.separated.external.storage=true
ro.external.storage.removable=false
ro.tether.denied=true
windowsmgr.max_events_per_sec=120
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=3.2_r3
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.com.google.clientidbase=android-sony
ro.sony.wifisleep=0
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
[B]ro.sony.update.service_id=nbx03_007[/B]
ro.sony.sku.base=nbx03_007
ro.sony.build.id=THMASU0075300
ro.sony.build.incremental=111104011
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.factorytest=0
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=wifi-only
ro.bootloader=0x00000008
ro.hardware=nbx03
ro.revision=0
init.svc.recovery=running
init.svc.nfx_daemon=running
init.svc.adbd=running
Click to expand...
Click to collapse
Weird nbx03_014 is Netherlands, Norway, Portugal, and Sweden
adn nbx03_007 is Germany
Do you have root at the moment? You can not use AIO to change region? Correct???
This is messed up
Try both nbx03_007 and nbx03_015 files, have a look in my signature for OTA links.
Good Luck
Stifilz
They don´t work, both ;(
Everytime the same error from my first post.
Do you have root at the moment? You can not use AIO to change region? Correct???
This is messed up
Good Luck
Stifilz
I can´t get root, first of all, i can´t use condis tool, becauce of the "findstr" failure. Secondly the AiO tools can´t write on the system path.
Can't anyone else help me? :S
Dunno what to do know cuz no update works and i can't get root
Alright so I'm starting out by saying I'm relativity new to this. So I'm in the dark on this issue.
Also If I posted this in the wrong section of the forum, please let me know so I don't do it again
The issue is that Whenever I try to back-up my ROM through ROM Manager it gives me some error
it boots into Clockworkmod and it gives me this
ClockworkMod Recovery v5.8.3.5
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
SD Card marker not found...
Error processing ROM Manager script. Please verify that you are performing the backup, restore, or ROM installation from ROM Manager v4.4.0.0 or higher.
Click to expand...
Click to collapse
It says to check the log file
Now before anything, I already uninstalled ROM Manager, reinstalled, reflashed Clockworkmod, and confirmed that everything is up to date.
Can anyone shed some light on this?
here's my LOG file:
Starting recovery on Tue Nov 13 18:08:31 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (720 x 1280)
ClockworkMod Recovery v5.8.3.5
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p21 (null) 0
2 /cache ext4 /dev/block/mmcblk0p36 (null) 0
3 /data ext4 /dev/block/mmcblk0p37 (null) 0
4 /misc emmc /dev/block/mmcblk0p23 (null) 0
5 /recovery emmc /dev/block/mmcblk0p22 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
7 /sd-ext ext4 /dev/block/mmcblk1p2 /dev/block/mmcblk1 0
8 /system ext4 /dev/block/mmcblk0p35 (null) 0
9 /devlog ext4 /dev/block/mmcblk0p26 (null) 0
10 /internal_sdcard vfat /dev/block/mmcblk0p38 (null) 0
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.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb
ro.build.id=IMM76I
ro.build.display.id=cm_jewel-userdebug 4.0.4 IMM76I eng.koush.20120602.132403 test-keys
ro.build.version.incremental=eng.koush.20120602.132403
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Sat Jun 2 13:24:31 PDT 2012
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=test-keys
ro.product.model=jewel
ro.product.brand=htc
ro.product.name=cm_jewel
ro.product.device=jewel
ro.product.board=jewel
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=htc
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8660
ro.build.product=jewel
ro.build.description=cm_jewel-userdebug 4.0.4 IMM76I eng.koush.20120602.132403 test-keys
ro.build.fingerprint=htc/cm_jewel/jewel:4.0.4/IMM76I/eng.koush.20120602.132403:userdebug/test-keys
ro.build.characteristics=default
ro.cm.device=jewel
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=
ro.url.legal.android_privacy=
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.cm.version=9.0.0-RC0-jewel-UNOFFICIAL
ro.modversion=9.0.0-RC0-jewel-UNOFFICIAL
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT25YS403492
ro.bootmode=recovery
ro.baseband=1.02.12.0427
ro.carrier=COMMON
ro.bootloader=1.12.0000
ro.hardware=jet
ro.revision=128
ro.emmc=1
init.svc.choice_fn=stopped
init.svc.adbd=running
init.svc.recovery=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
SD Card marker not found...
6a71c31c436f8231e32c8de389c24e24
Error processing ROM Manager script. Please verify that you are performing the backup, restore, or ROM installation from ROM Manager v4.4.0.0 or higher.
Click to expand...
Click to collapse
In case you ask (doubt you will) I erased the privacy and legal links in the LOG file due to the site blocking me from posting since I'm new.
That's because clockwork has issues with the EVO LTE.
install twrp (team win recovery project). Search on google or xda for download. Also, don't use Rom manager anymore, it is pretty much dead. Use goo manager.
Or download goo manager from market and install twrp as recovery. U will lose any backups u did on cwm, but they won't work anyways.
Sent from my EVO using xda app-developers app
Log70 said:
Alright so I'm starting out by saying I'm relativity new to this. So I'm in the dark on this issue.
Also If I posted this in the wrong section of the forum, please let me know so I don't do it again
The issue is that Whenever I try to back-up my ROM through ROM Manager it gives me some error
it boots into Clockworkmod and it gives me this
It says to check the log file
Now before anything, I already uninstalled ROM Manager, reinstalled, reflashed Clockworkmod, and confirmed that everything is up to date.
Can anyone shed some light on this?
here's my LOG file:
In case you ask (doubt you will) I erased the privacy and legal links in the LOG file due to the site blocking me from posting since I'm new.
Click to expand...
Click to collapse
bro DO NOT USE clockwork recovery on this phone.. it ***ks up ya misc partition.. flash teamwin recovery.. aka twrp.. its the only recovery that works on the LTE at this moment..
evo401 said:
bro DO NOT USE clockwork recovery on this phone.. it ***ks up ya misc partition.. flash teamwin recovery.. aka twrp.. its the only recovery that works on the LTE at this moment..
Click to expand...
Click to collapse
^^^^^ he said
bigdaddy619 said:
^^^^^ he said
Click to expand...
Click to collapse
Or what I said first? Why am I always invisible on here?
Sent from my EVO using xda app-developers app
Anthonicia said:
Or what I said first? Why am I always invisible on here?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
He said first^^^^^^^ My bad
Didn't realize. A friend recommended clockwork since he had used it on his original EVO 4G.
I already flashed the new recovery and wiped all trace of clockwork and rom manager.
Thanks for the help guys. If you ha e anything else to add then please do.
Sent from my EVO using xda premium
HELLO.
Am new here...so i request your help..advice..i dnt knw where this thread to post.......pls 4give me..
i rooted my micromax bolt A27 by unlock root...by following the thread 'how to root micromax a27 ' here
and i installed cwm recovery by following the thread
http://forum.xda-developers.com/showthread.php?t=2191285
succesfully installed....
BUT FIRST PROBLEM IS....
I cant enter cwm recovery by pressing volume+ && power button
i try to re flash recovery.img by adb folder method 3 or 4 times
it cannot solve my problem
then i erase recovery and flash again....by command erase flash recovery
hell.... it cant solve problem...............NO SUCCESS IT GOES TO FACTORY MODE WHEN PRESS VOLUME+ && POWER BUTTON
A TEMP SOLUTION I FOUND BY USE BOOT INTO RECOVERY MODE BY ROM MANAGER OR MOBILEUNCLE TOOLS....
PLEASE HELP ME A TRUE SOLUTION... TO GET CWM WITHOUT ROM MANNAGER OR MOBILE UNCLE , BRICK BOOT..........NLY BY BOOT KEYS
SECOND PROBLEM
Its the important problem nw i faced.... pls help meee.....................also i attach a report.log file
I got a error when i select 'UPDATE TOOL' in mobileuncle.......
i select 'check start safe flash update .zip(null package)-' - click next- click start test.....
phone reboot into recovery mode....
" sd card marker not fount
error proccesing ROM mannager script
please verify that you are performing the back uo,restore from rom mannager v4.4.0.0 or higher
please open rom mannager to report issue
before i run mobileuncle i install rom mannager and take a backup by boot into recovery by rom mannager...
i got this error by run mobile uncle and select update tool...and click check test.....
then i delete backup...i uninstall rom mannager.... bt cannot solve this problem
the report log file is here
Starting recovery on Wed May 25 16:49:49 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
ClockworkMod Recovery v6.0.2.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /sdcard vfat /dev/block/platform/sprd-sdhci.0/mmcblk0p1 (null) 0
2 /system yaffs2 system (null) 0
3 /cache yaffs2 cache (null) 0
4 /data yaffs2 userdata (null) 0
5 /misc mtd misc (null) 0
6 /boot mtd boot (null) 0
7 /recovery mtd recovery (null) 0
8 /fixnv yaffs2 fixnv (null) 0
9 /runtimenv yaffs2 runtimenv (null) 0
10 /backupfixnv yaffs2 backupfixnv (null) 0
11 /productinfo yaffs2 productinfo (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
Fixing execute permissions for /cache
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
persist.msms.phone_count=2
persist.sys.sprd.modemreset=1
ro.device.support.wifi=true
ro.device.support.bt=true
ro.device.support.gps=false
ro.device.support.fm=true
ro.device.support.gsensor=false
ro.device.support.lsensor=false
ro.device.support.msensor=false
ro.device.support.cmmb=false
ro.device.support.vt=false
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=MocorDroid2.3.5
ro.build.display.id=TD206B_HTO_H06A_V1.5
ro.build.version.incremental=W12.20_P20_20120926.181054
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=2012.09.26 18:16:25 CST
ro.build.date.utc=1348654585
ro.build.type=user
ro.build.user=jsm
ro.build.host=jsm-desktop
ro.build.tags=test-keys
ro.product.model=H06A
ro.product.brand=HTO
ro.product.name=H06A
ro.product.device=hsdroid
ro.product.board=sp8810ga
ro.ctl_baseband_ver=ctl_kernel_td206b_hto
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=CELLTEL
ro.wifi.channels=
ro.board.platform=sprdbp
ro.build.product=hsdroid
ro.build.description=sprdroid_base-user 2.3.5 MocorDroid2.3.5 W12.20_P20_20120926.181054 test-keys
ro.build.fingerprint=sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P20_20120926.181054:user/test-keys
persist.sys.timezone=Asia/Yekaterinburg
ro.product.carrier=
ro.product.locale.language=ru
ro.product.locale.region=RU
ro.msms.phone_count=2sim
wifi.supplicant_scan_interval=48
android.keylayout.sprd-keypad=/system/usr/keylayout/sprd-keypad.kl
android.keychar.sprd-keypad=/system/usr/keychars/sprd-keypad.kcm
ro.hardware=mtk6515
ro.telephony.default_network=2
ro.sprd.volume_control_icon=1
ro.sf.lcd_density=160
dalvik.vm.heapsize=32m
ro.opengles.version=131072
ro.internalstorage.threshold=95
persist.sys.language=ru
persist.sys.country=RU
ro.com.android.dateformat=yyyy-MM-dd
ro.com.android.dataroaming=true
net.bt.name=Android
net.change=net.tcp.buffersize.edge
ro.calibration=0
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.revision=0
ro.recvkeys=115,114,116,212
ro.recvkey.up=115
ro.recvkey.down=114
ro.recvkey.enter=116
ro.recvkey.home=212
ro.recvkey.power=116
ro.gpu=mali
net.tcp.buffersize.edge=4093,48000,64000,4096,10240,14336
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
SD Card marker not found...
4ae096ee66868ef0541608427b75d756
Error processing ROM Manager script. Please verify that you are performing the backup, restore, or ROM installation from ROM Manager v4.4.0.0 or higher.
please help meeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
dnt know
Hey dude me too having same problem with same phone... I know getting into recovery partition with hardware combination is little dif as compair to other phones.. i have searched all over google but cant find how to change or view key combination.... fastboot is working with power+vol- but dont know to access recovery by hardware combination.....
Same problem here. As the purpose of the recovery is to be able to restore a nandroid backup when something goes horribly wrong, we need to be able to boot into recovery without the Android GUI.
There is a workaround for this problem, when you can boot into recovery when the phone is turned off.
Connect your Bricked or Turned Off phone to your pc via USB cable. Open ADB. Send this command
Code:
[FONT="Courier New"]adb reboot recovery[/FONT]
And boom! Your phone will boot into CWM recovery. I am still looking into the issue of hardware buttons....and getting rid of the stock recovery altogether. I post soon.
Is "adb reboot recovery" will work when my phone is bricked or switched off? Pls help, I badly need this answer.
Sent from my Micromax A27 using xda app-developers app
for first problem (flashing CWM), use mtk droid tools (video below)
Hi.. (This was first posted in here -> http://forum.xda-developers.com/general/xda-assist/bee-9500-android-phone-mt6589-dead-t2830724 )
So to start off, I'm really desperate right now...
I had a BEE 9500 Phone with an MT6589 board, it was all working fine, until I accidently formatted the system partition, and I have no backup even... I only have a system folder backup, but is that even useful ?
When it was working, this is what MtkDroidTools showed :
i.imgur.com/hNBv1a7.png < I cant post link normally since I'm new.
Now it shows this, and mind you, the phone is stuck in boot loop and it will only show this when I'm mounting USB via CWM Recovery ONLY, It won't detect the phone normally when in boot loop (driver issue maybe) :
i.imgur.com/wY3yPFy.png
IMEI is blank ... everything is wrong... I don't know ...
(I have no idea why, but its showing the android L stuff, I have no idea whats going on...)
And I tried going into fastboot mode and using fastboot.exe to flash a system.img I created but it will keep saying <waiting for device> the whole time...
-----------
I'm wondering if anyone could kinda tell me where I can find the stock firmware for my BEE 9500 if there is any one, please.
Any idea ? I think my phone is dead at this rate....
Reserved, Any idea ? any help ? would it be possible to use the system folder backup I have to restore it ? I would have gladly uploaded the phones stock rom but I had no idea how that works then.
Ok guys, good news maybe, MTKDroidTools made a backup of my bootimage early on, it has my phone's name model and all and its the first one and most accurate, I think its the stock one.
I was able to pack it along with system into a zip file, but when I install it on my phone it gives this error...
Here is the recovery dumped on Sd Card using "Report Error" function in CWM :
Starting recovery on Wed Jan 2 14:38:16 2013
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (540 x 960)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
CWM automade 27.07.2014 23:05:40
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/misc (null) 0
2 /data ext4 /dev/block/mmcblk0p7 (null) 0
3 /system ext4 /dev/block/mmcblk0p5 (null) 0
4 /cache ext4 /dev/block/mmcblk0p6 (null) 0
5 /boot emmc /dev/bootimg (null) 0
6 /recovery emmc /dev/recovery (null) 0
7 /emmc vfat /dev/block/mmcblk0p8 (null) 0
8 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
9 /sd-ext auto /dev/block/mmcblk1p2 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=mass_storage,adb
ro.build.id=IMM76L
ro.build.display.id=full_MTK-eng 4.0.4 IMM76L eng.rua1.20130129.114933 test-keys
ro.build.version.incremental=eng.rua1.20130129.114933
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Вто Янв 29 11:51:46 MSK 2013
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=rua1
ro.build.host=rua1-desktop
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_MTK
ro.product.device=MTK
ro.product.board=MTK
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=MTK
ro.build.description=full_MTK-eng 4.0.4 IMM76L eng.rua1.20130129.114933 test-keys
ro.build.fingerprint=Android/full_MTK/MTK:4.0.4/IMM76L/eng.rua1.20130129.114933:eng/test-keys
ro.build.characteristics=default
ro.cm.device=MTK
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
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=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=mt6589
ro.revision=0
ro.emmc=0
sys.usb.vid=0BB4
init.svc.recovery=running
sys.usb.config=mass_storage,adb
service.adb.root=1
init.svc.adbd=restarting
sys.usb.state=mass_storage,adb
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
Script Asserts: Enabled
No files found.
No files found.
-- Installing: /sdcard/Download/StockRomUpdate.zip
Finding update package...
I:Update location: /sdcard/Download/StockRomUpdate.zip
Opening update package...
Installing update...
about to run program [/sbin/mount] with 3 args
minzip: Error writing 32768 bytes from zip file from 0xbeec7c84: No space left on device
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
minzip: Error extracting "/system/app/AccidentBiological.gnz"
about to run program [/sbin/unmount] with 3 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1
script result was [Enjoy!]
Enjoy!
Install from sdcard complete.
Click to expand...
Click to collapse
minzip: Error writing 32768 bytes from zip file from 0xbeec7c84: No space left on device ???
there is no other way too, and I can't flash boot.img using MTKDroidTools during recovery mode either.
I think boot installs fine ? using 's recovery flasher from here -> http://forum.xda-developers.com/showthread.php?t=2245724
and clicking "show log" in CWM shows no error at all.
I'm not really sure how??
and why does MTKDroidTools detects my phone as nexus or another phone ? is it because of build.prop ? what determines that ?
And I'm using the following Binary files btw for install ... http://forum.xda-developers.com/showthread.php?t=1721680
Another question, can it be possibly that there is not enough space on the SD Card instead ? where is it extracted ?
Apparently not though, I just cleared my SD Card and I'm getting the same error.