Related
Added xtskit.zip to this post which contains various scripts which can be used to debug various situations! Please use always latest version from this post and AT YOUR OWN RISK!
Decided to start new thread if anybody would still get any adeas for debricking my Xperia Tablet S before I call it unpossible... So, what has happened:
- Tried to upgrade my FI XTS from rooted 6b to rooted JB. Flashing apparently went fine but after reboot I got just Sony logo. Was able to boot to recovery and tried to recover by flashing firmware version 6, but got this error:
Installing update...
Write images to system0...
Write files to vendor0...
Random offset: 0x384
read_mod_link: failed to readlink "/system1/vendor": No such file or directory
E:Error in /tmp/desklunvr/desklunvr.zip
(Status 7)
Installation aborted.
Don't know what went wrong when flashing, but my analysis of current state:
* /blflags is set to 1 (because recovery starts to flash system0).
* /system0 contains valid image of that firmware what I use to recover (since it was flashed properly)
* /datapp/vendor0 contains correct data from the same firmware (since files were written properly)
* /system1 is totally corrupted
* /datapp/vendor1 state is unknown
* /staging state is unknown but propably contains valid data from SOME firmware because recovery works, right?
Because of that /system1 corrupted state, recovering won't work as Sonys updater-script will try to read it before flashing /staging.
No, why my XTS does not boot? For me, it seems that /staging contains valid image (because I can get to recovery), doesn't it then contain also valid kernel for system0, right? Does my XTS not boot because:
* /blflags is set to 1. System tries to boot from /system1 and FAILS since it's corrupted. However bootloader does not recognize this and wont flip blfalgs.
OT
* /staging is corrupted
In both cases, I could boot if I could just flip /blflags flag! In first case system would boot using /system0 and everything ok if /staging would have the right kernel for /system0 and since I can flash /system0 no problem. Also if flag would be flipped I could flash /system1 afterwards.
Now, any ideas? How to flip /blflags? I've been trying to poweroff in the middle of booting process but no luck. It just seems bootloader won't flip it no matter what.
Thanks!
- J
ignore post, cant delete
Could somebody confirm, that does hidden.img contain recovery and kernel? Further, could somebody with JB go to recovery and paste the version? I am trying to trace what version my /staging (hidden.img) is, JB or 6b.
My recovery says:
System utility(Rev.39, BL: 0x00000006, EC: 0.21, master)
I think it said the same when I was on 6b so unless JB has the same recovery, my /staging is probably from 6b.
Thanks!
Edit: And please, if anybody have european r6b firmware signed-txs03_300-ota-121116002.zip please share with me! I think my current hidden.img is from that firmware, just perhaps if I flash it, I could recover if the reason I cannot boot is that r6b bootloader won't allow loding r6 or JB system... Heh, I just tried, I can download r6b firmware for EVERY OTHER region but for my own region. Probably download link I got was wrong, but what would be the right link?
One kind soul replied and it seems JB's recovery is Rev.44. So my recovery/bootloader/kernel is from r6b and that's why my JB did not boot. I flashed hidden.img but for some reason it did not work (or I mistyped since I was a bit sleepy when upgrading).
I could try flashing r6b system0 and it could work, but Sony has removed it from their site. Please, anybody, do you have signed-txs03_300-ota-121116002.zip ??? I have r6, but it does not boot.
Just out of curiosity, when I poweron my tablet, kernel probably boots OK since my computer can see SGPT12 device after a while. However, adb does not work as expected so that wont help at all.
Wait what... I just found out, that when I am in recovery console, my computer sees SGPT121 device but does not have driver for it. When device worked, I had drivers. I used "Sony Tablet ADB Driver Automated Installer" to install drivers and when I explored android_winusb.inf I found out that this automated installer installed drivers only for composite adbdev interface, not for single adb interface. So I manually added correct pids etc. and was then able to install drivers and now I can actually see my device booted to recovery:
List of devices attached
0123456789ABCDEF recovery
Shell wont work however as expected so probably still impossible to unbrick, but at least I was able to pull recovery.log:
Starting recovery on Sun Apr 21 10:29:00 2013
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /hwconfigs ext2 /dev/block/mmcblk0p1 (null) 0
2 /configs ext4 /dev/block/mmcblk0p2 (null) 0
3 /system0 ext4 /dev/block/mmcblk0p3 (null) 0
4 /system1 ext4 /dev/block/mmcblk0p4 (null) 0
5 /cache ext4 /dev/block/mmcblk0p5 (null) 0
6 /misc emmc /dev/block/mmcblk0p6 (null) 0
7 /staging ext4 /dev/block/mmcblk0p7 (null) 0
8 /blflags ext4 /dev/block/mmcblk0p8 (null) 0
9 /datapp ext4 /dev/block/mmcblk0p9 (null) 0
10 /log ext4 /dev/block/mmcblk0p10 (null) 0
11 /data ext4 /dev/block/mmcblk0p11 (null) -32768
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
16 /vendor0 ext4 vendor0.img (null) 0
17 /vendor1 ext4 vendor1.img (null) 0
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
ro.build.id=TID0142
ro.build.display.id=TID0142
ro.build.version.incremental=121116001
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Nov 16 01:16:55 JST 2012
ro.build.date.utc=1352996215
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build8
ro.build.tags=test-keys
ro.product.model=SGPT12
ro.product.brand=Sony
ro.product.name=SYS_052
ro.product.device=txs03
ro.product.board=txs03
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=txs03
ro.build.description=SYS_052-user 4.0.3 TID0142 121116001 test-keys
ro.build.fingerprint=Sony/SYS_052/txs03:4.0.3/TID0142/121116001:user/test-keys
ro.build.characteristics=tablet
ro.opengles.version=131072
wifi.interface=wlan0
wifi.wpa_supp_ready=0
persist.tegra.nvmmlite=1
windowsmgr.max_events_per_sec=135
ro.tether.denied=true
ro.sony.sound.enabled=true
ro.sony.display.release=release6b
ro.product-res-path=vendor/framework/SemcGenericUxpRes.apk
ro.sony.autovolume.threshold=10
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.config.alarm_alert=Alarm.ogg
ro.config.notification_sound=Notification.ogg
ro.config.ringtone=Ringtone_XPERIA.ogg
drm.service.enabled=true
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.sony.wifisleep=0
ro.semc.enhance.supported=true
ro.semc.clearaudio.supported=true
ro.somc.dmnorm.supported=true
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.0_r6
ro.com.google.clientidbase=android-sony
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
ro.sony.wan.ipv6.enable=false
persist.sys.sony.cabc.disable=0
persist.sys.sony.hdmi.disable=0
ro.sony.dlna_dms.enabled=false
ro.somc.social_product_model=PRODUCT_MODEL_TABLET
ro.sony.irremote.protocol_type=2
ro.sony.ols.eula=1
ro.pss.ps1content_disable=1
ro.factorytest=0
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=0x00000006
ro.hardware=txs03
ro.revision=0
init.svc.recovery=running
init.svc.nfx_daemon=running
init.svc.radbd=running
jappaj said:
Wait what... I just found out, that when I am in recovery console, my computer sees SGPT121 device but does not have driver for it. When device worked, I had drivers. I used "Sony Tablet ADB Driver Automated Installer" to install drivers and when I explored android_winusb.inf I found out that this automated installer installed drivers only for composite adbdev interface, not for single adb interface. So I manually added correct pids etc. and was then able to install drivers and now I can actually see my device booted to recovery:
Click to expand...
Click to collapse
I have exactly the same problem.
What do you modify on the android_winusb.inf to install drivers?
Thanks
hui666 said:
I have exactly the same problem.
What do you modify on the android_winusb.inf to install drivers?
Thanks
Click to expand...
Click to collapse
You mean you bricked your XTS like me while trying to flash JB? The we should warn people, it's something related to region, config or something like that.
About your question; edit android_winusb.inf and find rows like this:
;SONY Sony Tablet S
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_05B4&MI_01
Then add row like this just after that:
%SingleAdbInterface% = USB_Install, USB\VID_054C&PID_05B4
So it becomes:
;SONY Sony Tablet S
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_05B4&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_054C&PID_05B4
There two places where you will find rows likje this, onw for x85 and one for amd64.
After this, boot to recovery and wait that you can see your XTS in device manager. It should shay that there are no drivers etc. Click update driver and browse manuaklly files and find directory which contains that modified file. Install and it should work.
But Sony has locked us out of the shell and effectively nothing can be done to fix anything (thanks sony, lock bootloader, f**k recovery scripts, f**k automatic swtiching between system images, lock recovery adb... what next, you need to be in jail to use next Xperia device?) unless somebody finds exploit. But then we could root also...
Wait, has anybody ever actually tried that would Xperia Tablet S accept upate.zip which is signed with test key just like you sign packages for Tablet S, but ALSO encrypted?
Because error message I get when trying to use such zip is something like cannot desklunvr package... So it is trying to decrypt package and as it is already decrypted, it fails. What happens if we encrypt it? It should be possible since we know how to decrypt!
jappaj said:
Wait, has anybody ever actually tried that would Xperia Tablet S accept upate.zip which is signed with test key just like you sign packages for Tablet S, but ALSO encrypted?
Because error message I get when trying to use such zip is something like cannot desklunvr package... So it is trying to decrypt package and as it is already decrypted, it fails. What happens if we encrypt it? It should be possible since we know how to decrypt!
Click to expand...
Click to collapse
Had jb boot up but no root access so flashed the jb update official and it works fine lost root it takes ages for it to boot and also took a couple of goes with the flasher no big deal only reason for root is custom ROM and until boot loader is unlocked not much need for root
S
Sent from my Wildfire using xda app-developers app
dex9mm said:
Had jb boot up but no root access so flashed the jb update official and it works fine lost root it takes ages for it to boot and also took a couple of goes with the flasher no big deal only reason for root is custom ROM and until boot loader is unlocked not much need for root
S
Sent from my Wildfire using xda app-developers app
Click to expand...
Click to collapse
Oh dear I've just joined the Bricked club tooo......
I tried updated from rooted 6b to Rooted Jelly Bean with condi flasher and I'm now stuck on the Sony screen.
Anyyyy possible fix?
Hi everyone, we are on the same boat. I've tried to flash using S.T.S.Flasher 3.0v the prerooted 4.1.1 rom on my root 4.0.3 R6B tab. My Xperia is US version. It seems that everything worked fine, but at the end I got black screen. On another post I read that a hard reset was needed. Nothing happened. After reboot i got freez on sony's logo. I've done with recovery a factory reset, wiping data etc, but without success.
Now I've downloaded a stock r5 version and flash it but i've seen after first boot that the fw that my dev. is running now is 4.1.1, without root and recovey. Strange but true. Why? i don't really know.
I think that i've done a big mistake flashing it but i think that it was the right thing to do for not using my tab as a coaster for the future.
sfex3best said:
Oh dear I've just joined the Bricked club tooo......
I tried updated from rooted 6b to Rooted Jelly Bean with condi flasher and I'm now stuck on the Sony screen.
Anyyyy possible fix?
Click to expand...
Click to collapse
Can you get to recovery? Try to flash firmware version 6 (not a not b) for your region from there. You are not bricked until you cannot flash from recovery like me...
sfex3best said:
Oh dear I've just joined the Bricked club tooo......
I tried updated from rooted 6b to Rooted Jelly Bean with condi flasher and I'm now stuck on the Sony screen.
Anyyyy possible fix?
Click to expand...
Click to collapse
flashing the stock jb from sony sight and losing root might be best if cant wait to hear back from condi......
not the best solution but from reading others at least shouldnt risk bricking.
Tried installing release 6 from recovery but no luck with that. Tried a few different versions too release 6b and jelly bean but the same error on all of them
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Need help
Sent from my R800i using xda premium
sfex3best said:
Tried installing release 6 from recovery but no luck with that. Tried a few different versions too release 6b and jelly bean but the same error on all of them
View attachment 1903761
Need help
Sent from my R800i using xda premium
Click to expand...
Click to collapse
I've flashed one of this stock rom . http://forum.xda-developers.com/showpost.php?p=26882762&postcount=3
because when i tried to flash it using recovery i got this error similar to yours:
"Desklunvr update package...
E:Can't desklunvr /sdcard/customs_prerooted_"........".zip
Installation aborted"
I think you'll lose root and recovery, but now should be the only way that i found to skip that error and brings back your tab to life.
I've tried those already I think.
Which one is stock rom out of those tho?
Sent from my R800i using xda premium
I have a US device, so i've downloaded and flashed the ICS r6b for US tablet. Should be both stock rom. If you see the links, are all of sony's web site.
Guys, if you get that "read_mod_link: failed to readlink "/system1/vendor": No such file or directory" error you currently are bricked. There's no way to recover until:
a) Sony releases an update which does not suck and is actually able to recover something (I doubt it since they haven't done it before)
b) Somebody from Sony leaks private key used to sign updates so we can sign our own update.zip (highly unlikely...)
c) Somebody finds a way to crack recovery from recovery itself (possible but I doubt it since it has not happened before)
d) Somebody finds out how to flip /blflags (possible, but I haven't been able to figure out how)
So we are screwed, there's no way to recover for now.
Ps. If anybody from Sony is reading this, please give us update.zip or something else which will flip blflags which would allow us to reover using standard firmware. Otherway you risk receiving bricked tablets to your sevice centers even though they are not really bricked, we just do not have proper update.zip. Highly unlikely though that anybody from Sony is reading this, at least anybody who can make the decision...
jappaj said:
Guys, if you get that "read_mod_link: failed to readlink "/system1/vendor": No such file or directory" error you currently are bricked. There's no way to recover until:
a) Sony releases an update which does not suck and is actually able to recover something (I doubt it since they haven't done it before)
b) Somebody from Sony leaks private key used to sign updates so we can sign our own update.zip (highly unlikely...)
c) Somebody finds a way to crack recovery from recovery itself (possible but I doubt it since it has not happened before)
d) Somebody finds out how to flip /blflags (possible, but I haven't been able to figure out how)
So we are screwed, there's no way to recover for now.
Ps. If anybody from Sony is reading this, please give us update.zip or something else which will flip blflags which would allow us to reover using standard firmware. Otherway you risk receiving bricked tablets to your sevice centers even though they are not really bricked, we just do not have proper update.zip. Highly unlikely though that anybody from Sony is reading this, at least anybody who can make the decision...
Click to expand...
Click to collapse
Man im roight there with you ok evey one who has used the flasher STOP FLASHING
If your stuck on sony screen during flashing But can flash back to ics do and saty there
If it is not booting then I dont have an answer just a warning
I was the first to post about the flsaher giving trouble but nobody checks these fourms till there is a prioblem and thats why people strat at step three and then ask where did I go wrong ive been posting since the twentith so its not like the warning signs wernt there
However if your realy want the update download it via ics then root with condis tool and flasdh
and you boot in to jb there is no root acknowledgement by 3rd party apps there is root due to the kernal condi provides but it is rooted
If
And why is the chager cable so short
Pm me if you need help
Sent from my SGPT12 using xda app-developers app
dont ask for condi by the way hes just got married
Hi All,
first of all, I'm very sorry should ask dump questions but I am totally lost here. Have been trying for two months to get my tablet to work and tried thorugh all of your helpful tipps but nothing seems to work, so I would very very much appreciate any help!!
The situation: I have a Xperia Tablet S from the US, SGPT1211, which just shows the Sony Logo when turned on. I can access the Android recovery menu and have tried (several times) to install the JB R2 and R3 files from SD card (i used the US versions from here: http://forum.xda-developers.com/showthread.php?p=26882207).
The Updates start but at about 20%, they would just stop and says "Installation Aborted"
Also, I have tried to use @condi Unbricker (http://forum.xda-developers.com/showthread.php?t=2642436). It does install on my SD Card, but if I start the device using the SD card, it still hangs and the Sony Logo and does not show booting cold.
If there is anyone here, please please please help! @stifilz
(I bought the tablet while studying in the US and living in Europe now. Sony Europe won't look at it - not even for money...)
davhenry said:
Hi All,
first of all, I'm very sorry should ask dump questions but I am totally lost here. Have been trying for two months to get my tablet to work and tried thorugh all of your helpful tipps but nothing seems to work, so I would very very much appreciate any help!!
The situation: I have a Xperia Tablet S from the US, SGPT1211, which just shows the Sony Logo when turned on. I can access the Android recovery menu and have tried (several times) to install the JB R2 and R3 files from SD card (i used the US versions from here: http://forum.xda-developers.com/showthread.php?p=26882207).
The Updates start but at about 20%, they would just stop and says "Installation Aborted"
Also, I have tried to use @condi Unbricker (http://forum.xda-developers.com/showthread.php?t=2642436). It does install on my SD Card, but if I start the device using the SD card, it still hangs and the Sony Logo and does not show booting cold.
If there is anyone here, please please please help! @stifilz
(I bought the tablet while studying in the US and living in Europe now. Sony Europe won't look at it - not even for money...)
Click to expand...
Click to collapse
Hi, i am in the same situation that you and the same tablet, i tried too with Sony Unbricker program but never work for me even with 3 different SD Cards 2, 8, 16 GB and differents class 4, 6, 10 respective.
I found the original post about unbrick the tablet http://forum.xda-developers.com/showthread.php?t=2610791 but doesnt have any idea what to do because i am not a linux advanced user and low level's programming :crying:
Recovery log
Hi again @davhenry, i am posting the recovery log of my tablet maybe we are having the same problem that me. You could post your recovery log for compare, thanks
I would appreciate any help or any clue @condi, @stifilz
Starting recovery on Mon Apr 21 01:42:48 2014
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /hwconfigs ext2 /dev/block/mmcblk0p1 (null) 0
2 /configs ext4 /dev/block/mmcblk0p2 (null) 0
3 /system0 ext4 /dev/block/mmcblk0p3 (null) 0
4 /system1 ext4 /dev/block/mmcblk0p4 (null) 0
5 /cache ext4 /dev/block/mmcblk0p5 (null) 0
6 /misc emmc /dev/block/mmcblk0p6 (null) 0
7 /staging ext4 /dev/block/mmcblk0p7 (null) 0
8 /blflags ext4 /dev/block/mmcblk0p8 (null) 0
9 /datapp ext4 /dev/block/mmcblk0p9 (null) 0
10 /log ext4 /dev/block/mmcblk0p10 (null) 0
11 /data ext4 /dev/block/mmcblk0p11 (null) -32768
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
16 /vendor0 ext4 vendor0.img (null) 0
17 /vendor1 ext4 vendor1.img (null) 0
Command: "/sbin/recovery"
ro.boot.serialno=015d3b65d827f602
ro.boot.commchip_id=0
ro.boot.bootloader=0x00000009
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=0x00000009
ro.hardware=txs03
ro.revision=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
ro.build.id=TJDSU0177
ro.build.display.id=TJDSU0177
ro.build.version.incremental=131023017
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Wed Oct 23 08:43:49 JST 2013
ro.build.date.utc=1382485429
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build9
ro.build.tags=test-keys
ro.product.model=SGPT12
ro.product.brand=Sony
ro.product.name=SYS_052
ro.product.device=txs03
ro.product.board=txs03
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=txs03
ro.build.description=SYS_052-user 4.1.1 TJDSU0177 131023017 test-keys
ro.build.fingerprint=Sony/SYS_052/txs03:4.1.1/TJDSU0177/131023017:user/test-keys
ro.build.characteristics=tablet,nosdcard
ro.opengles.version=131072
wifi.interface=wlan0
wifi.wpa_supp_ready=0
persist.tegra.nvmmlite=1
ro.sf.override_null_lcd_density=1
keyguard.no_require_sim=true
debug.nfc.fw_download=false
debug.nfc.se=false
ro.ril.wake_lock_timeout=200000
ro.streaming.video.drs=true
ro.tether.denied=true
ro.sony.sound.enabled=true
ro.sony.irremote.devicefile=/dev/ttySIR0
ro.sony.display.release=release3
ro.sony.autovolume.threshold=10
ro.product-res-path=vendor/framework/SemcGenericUxpRes.apk
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.config.alarm_alert=Alarm.ogg
ro.config.notification_sound=Notification.ogg
ro.config.ringtone=Ringtone_XPERIA.ogg
ro.carrier=unknown
drm.service.enabled=true
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=384m
ro.semc.enhance.supported=true
ro.semc.clearaudio.supported=true
ro.somc.dmnorm.supported=true
ro.sony.wifisleep=0
ro.sf.lcd_density=160
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.1_r4
ro.com.google.clientidbase=android-sony
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
ro.sony.wan.ipv6.enable=false
persist.sys.sony.cabc.disable=0
persist.sys.sony.hdmi.disable=0
ro.sony.cradle.settings=true
ro.sony.hdmi.settings=true
ro.sony.cabc.settings=true
ro.sony.dlna_dms.enabled=false
ro.somc.social_product_model=PRODUCT_MODEL_TABLET
ro.sony.irremote.protocol_type=2
ro.sony.ols.eula=1
ro.pss.ps1content_disable=1
init.svc.ueventd=running
init.svc.recovery=running
init.svc.nfx_daemon=running
init.svc.radbd=running
rassegan said:
Hi again @davhenry, i am posting the recovery log of my tablet maybe we are having the same problem that me. You could post your recovery log for compare, thanks
I would appreciate any help or any clue @condi, @stifilz
Starting recovery on Mon Apr 21 01:42:48 2014
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /hwconfigs ext2 /dev/block/mmcblk0p1 (null) 0
2 /configs ext4 /dev/block/mmcblk0p2 (null) 0
3 /system0 ext4 /dev/block/mmcblk0p3 (null) 0
4 /system1 ext4 /dev/block/mmcblk0p4 (null) 0
5 /cache ext4 /dev/block/mmcblk0p5 (null) 0
6 /misc emmc /dev/block/mmcblk0p6 (null) 0
7 /staging ext4 /dev/block/mmcblk0p7 (null) 0
8 /blflags ext4 /dev/block/mmcblk0p8 (null) 0
9 /datapp ext4 /dev/block/mmcblk0p9 (null) 0
10 /log ext4 /dev/block/mmcblk0p10 (null) 0
11 /data ext4 /dev/block/mmcblk0p11 (null) -32768
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
16 /vendor0 ext4 vendor0.img (null) 0
17 /vendor1 ext4 vendor1.img (null) 0
Command: "/sbin/recovery"
ro.boot.serialno=015d3b65d827f602
ro.boot.commchip_id=0
ro.boot.bootloader=0x00000009
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=0x00000009
ro.hardware=txs03
ro.revision=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
ro.build.id=TJDSU0177
ro.build.display.id=TJDSU0177
ro.build.version.incremental=131023017
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Wed Oct 23 08:43:49 JST 2013
ro.build.date.utc=1382485429
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build9
ro.build.tags=test-keys
ro.product.model=SGPT12
ro.product.brand=Sony
ro.product.name=SYS_052
ro.product.device=txs03
ro.product.board=txs03
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=txs03
ro.build.description=SYS_052-user 4.1.1 TJDSU0177 131023017 test-keys
ro.build.fingerprint=Sony/SYS_052/txs03:4.1.1/TJDSU0177/131023017:user/test-keys
ro.build.characteristics=tablet,nosdcard
ro.opengles.version=131072
wifi.interface=wlan0
wifi.wpa_supp_ready=0
persist.tegra.nvmmlite=1
ro.sf.override_null_lcd_density=1
keyguard.no_require_sim=true
debug.nfc.fw_download=false
debug.nfc.se=false
ro.ril.wake_lock_timeout=200000
ro.streaming.video.drs=true
ro.tether.denied=true
ro.sony.sound.enabled=true
ro.sony.irremote.devicefile=/dev/ttySIR0
ro.sony.display.release=release3
ro.sony.autovolume.threshold=10
ro.product-res-path=vendor/framework/SemcGenericUxpRes.apk
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.config.alarm_alert=Alarm.ogg
ro.config.notification_sound=Notification.ogg
ro.config.ringtone=Ringtone_XPERIA.ogg
ro.carrier=unknown
drm.service.enabled=true
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=384m
ro.semc.enhance.supported=true
ro.semc.clearaudio.supported=true
ro.somc.dmnorm.supported=true
ro.sony.wifisleep=0
ro.sf.lcd_density=160
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.1_r4
ro.com.google.clientidbase=android-sony
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
ro.sony.wan.ipv6.enable=false
persist.sys.sony.cabc.disable=0
persist.sys.sony.hdmi.disable=0
ro.sony.cradle.settings=true
ro.sony.hdmi.settings=true
ro.sony.cabc.settings=true
ro.sony.dlna_dms.enabled=false
ro.somc.social_product_model=PRODUCT_MODEL_TABLET
ro.sony.irremote.protocol_type=2
ro.sony.ols.eula=1
ro.pss.ps1content_disable=1
init.svc.ueventd=running
init.svc.recovery=running
init.svc.nfx_daemon=running
init.svc.radbd=running
Click to expand...
Click to collapse
Unbricker is only for Xperia Tablet S not Sony Tablet S. I am partly in the same boat, although my one does run (honeycomb) lol. Anyway can you both please try the install your original update (i.e. to suit your region) twice in a row and then pull the recovery log. If you need help with this please see my FAQ thread in my signature.
Thanks
Its Works!!!
Hey guys @davhenry @stifilz i could finally recover my Sony Xperia Tablet S following these steps and the Sony's Unbricker Software 1.0 by @condi
1) Unzip the software and make a new folder called "UNBRICK_DATA"
2) Download manually the files unbrick.zip and the correct OTA Software of your tablet
3) Unzip the unbrick.zip file and copy in the SD Card with Win32DiskImager
4) Rename your OTA Software ( Example: signed-txs03_201-ota-131023018.zip) to update.zip
5) Copy this file in the folder "files" in the program
6) Open and DOS Console in Windows and descrypt the file using desklunvr.exe. Example : desklunvr.exe update.zip
7) Make 2 image files with the recently file generate (update_deslunvr)
7za.exe x update_desklunvr.zip system.img
7za.exe x update_desklunvr.zip hidden.img
8) Copy the new images files and update_desklunvr in UNBRICK_DATA (these last file i did just in case )
9) Run Condi´s Program and make sure you go to the step 6 and just follow the instructions
The tablet reboot 2 times at the beginning looks like not working because get stuck in sony logo but turn off and turn on again and then ITS WORKSS !!! :laugh:
Good luck guys
rassegan said:
Hey guys @davhenry @stifilz i could finally recover my Sony Xperia Tablet S following these steps and the Sony's Unbricker Software 1.0 by @condi
1) Unzip the software and make a new folder called "UNBRICK_DATA"
2) Download manually the files unbrick.zip and the correct OTA Software of your tablet
3) Unzip the unbrick.zip file and copy in the SD Card with Win32DiskImager
4) Rename your OTA Software ( Example: signed-txs03_201-ota-131023018.zip) to update.zip
5) Copy this file in the folder "files" in the program
6) Open and DOS Console in Windows and descrypt the file using desklunvr.exe. Example : desklunvr.exe update.zip
7) Make 2 image files with the recently file generate (update_deslunvr)
7za.exe x update_desklunvr.zip system.img
7za.exe x update_desklunvr.zip hidden.img
8) Copy the new images files and update_desklunvr in UNBRICK_DATA (these last file i did just in case )
9) Run Condi´s Program and make sure you go to the step 6 and just follow the instructions
The tablet reboot 2 times at the beginning looks like not working because get stuck in sony logo but turn off and turn on again and then ITS WORKSS !!! :laugh:
Good luck guys
Click to expand...
Click to collapse
@rassegan
Thanks for your tips! However, I'm having some trouble following your advice: when using WIN32DiskImager to unpack the unbrick.zip onto my SD Card, I can no longer access the SD Card as it says it uses an unknown Data System.
Additionally, where did you unpack the OTA Software? directly onto the SD Card or rather on my desktop and then the SD Card? And could you detail the DOS unpacking using desklunvr.exe?
Sorry for asking so many questions, it would be so so so great if you had some additional comments!
@stifilz Thanks for your help, was abroad for a cpl of days and will try to pull the log file which I couldn't work out so far
@stifilz I'm having trouble to actually access my XTS via ADB. I follwed all your steps here (http://forum.xda-developers.com/showthread.php?p=30099315#post30099315) and installed a billion of drivers. I do see my tablet in the device manager als Android Device, however, it won't show if I enter "adb devices". Instead, the list is empty.
Anyone an indea what I'm doing wrong here?
Many thanks!!
davhenry said:
@rassegan
Thanks for your tips! However, I'm having some trouble following your advice: when using WIN32DiskImager to unpack the unbrick.zip onto my SD Card, I can no longer access the SD Card as it says it uses an unknown Data System.
Additionally, where did you unpack the OTA Software? directly onto the SD Card or rather on my desktop and then the SD Card? And could you detail the DOS unpacking using desklunvr.exe?
Sorry for asking so many questions, it would be so so so great if you had some additional comments!
@stifilz Thanks for your help, was abroad for a cpl of days and will try to pull the log file which I couldn't work out so far
Click to expand...
Click to collapse
Hi @davhenry, well i unzipped the file unbrick.zip in the same folder UNBRICK_DATA so you should be have a image file of 1.5 or 1.6 GB this image you would use at moment to copy in the SD CARD with the WIN32DiskImager
---------- Post added at 08:11 PM ---------- Previous post was at 07:51 PM ----------
davhenry said:
@stifilz I'm having trouble to actually access my XTS via ADB. I follwed all your steps here (http://forum.xda-developers.com/showthread.php?p=30099315#post30099315) and installed a billion of drivers. I do see my tablet in the device manager als Android Device, however, it won't show if I enter "adb devices". Instead, the list is empty.
Anyone an indea what I'm doing wrong here?
Many thanks!!
Click to expand...
Click to collapse
Hey again, i had the same problem, follow this thread i use the method A in my Windows 8.1 and download the zip file and unzip
Once time you unzipped the folder find the file android_winusb.inf and add this lines under the sony products
;SONY Sony Xperia Tablet S
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_06AC&MI_01 (Verify if your PID is same as me )
Copy this line in GoogleNT_X86 and GoogleNT_amd64 and save the file
Update the drivers manually in the device manager
OMG guys, it worked!!!
I didnt do anything differet, for some reason it worked though. I am so grateful, thank you so so muc @stifilz and @rassegan!!
rassegan said:
Hey guys @davhenry @stifilz i could finally recover my Sony Xperia Tablet S following these steps and the Sony's Unbricker Software 1.0 by @condi
1) Unzip the software and make a new folder called "UNBRICK_DATA"
2) Download manually the files unbrick.zip and the correct OTA Software of your tablet
3) Unzip the unbrick.zip file and copy in the SD Card with Win32DiskImager
4) Rename your OTA Software ( Example: signed-txs03_201-ota-131023018.zip) to update.zip
5) Copy this file in the folder "files" in the program
6) Open and DOS Console in Windows and descrypt the file using desklunvr.exe. Example : desklunvr.exe update.zip
7) Make 2 image files with the recently file generate (update_deslunvr)
7za.exe x update_desklunvr.zip system.img
7za.exe x update_desklunvr.zip hidden.img
8) Copy the new images files and update_desklunvr in UNBRICK_DATA (these last file i did just in case )
9) Run Condi´s Program and make sure you go to the step 6 and just follow the instructions
The tablet reboot 2 times at the beginning looks like not working because get stuck in sony logo but turn off and turn on again and then ITS WORKSS !!! :laugh:
Good luck guys
Click to expand...
Click to collapse
Hi..
Firstly, I'd like to apologize in advance for my bad english..
My Xperia Tablet S is an SGPT131A1 (Asia model)
Rooted and got it bricked few weeks ago..
Got panicked and recklessly did a full wipe..
Still stuck on Sony logo..
Thanks God I found Condi's post..
Gave it a try, and still did not work..
Still stuck on Sony logo..
There are several questions I'd like to ask you @rassegan
1. How do you copy the unbrick.img to the SD card? I tried using the Win32DiskImager as you mentioned above, but my SD card ended up having 0 byte of free space. Thus, the unbricker program cannot copy the rest of the file.
2. Eventually I formatted my SD card and skip part 3 instead. Followed Condi's unbricker program, chose option 6, and followed the instruction, but it did not succeeded to copy the files onto my SD card. Here's the screen capture of @condi 's program showing the error.
View attachment 2844352
Is there something wrong? Or did I miss some step?
Any help will be much appreciated..
Thanks in advance
If I do step 3 Unzip the unbrick.zip file and copy in the SD Card with Win32DiskImager
how I can use S.onyXT.S [UNBRICKER] v1.0 after and does step 6 again if first partition have ony 71 MB????
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
all time is there error
but when I tried automatic process with S.onyXT.S [UNBRICKER] v1.0 fr4om 1 - 7 not works I never had ''COLD -booting '' message
I have only if I manually use Win32DiskImager and add unbrick.zip to sd card ( 8GB )
but how long will this process take?
I running long time and no change
PLEASE HELP HOW To recover back
davhenry said:
OMG guys, it worked!!!
I didnt do anything differet, for some reason it worked though. I am so grateful, thank you so so muc @stifilz and @rassegan!!
Click to expand...
Click to collapse
What you did MR can you help me please
I cant have cold boot anyhow from
S.onyXT.S [UNBRICKER] v1.0
ON the end I have xperia tablet S SGPT1211 back to live btw is R6A for all who will experiment as I did
on the beginning I Have 2 tablets SGPT1211 and will be using as multi -functional remote control
because I set up already first tablet to fully remote control functionality a I want copy data from one to second tablet
but I delete APPDATA from second one and whole unit after factory restore doesn't have all APP
and manually installed remote control APP crashed all time
I decide to recovery by sony tablet Flasher but I choose R5A which was for first tablet S gen - STUPID BOY
tablet has been unresponsive etc
I tried UNBRICER but not work!!!
on the end I copied UNBRICK DATA by win32diskimg to 8GB SD
after cold boot I run @condi's unbricker program from point 7 and after 30 min approx xperia tablet S SGPT1211 (R6A) return back to live
BUT not all APP installed
now I using Sony tablet flasher 3 @condi and choosing fw 4.0.3 1a for R6B and will see what happens.
hopefully this info will help someone to unbrick his device
after update 4.0.3 by @condi still missing some application
when install app ''remote control'' manually not working crashes all time
tabled cant see external SD card!!! as well dock USB !!!
I going to try 1b 4.1.1 and I hope will be back with all APK from factory
can anyone tell me how reinstall back to factory SGPT 1211US/S
urgas said:
I going to try 1b 4.1.1 and I hope will be back with all APK from factoryS
Click to expand...
Click to collapse
than with trouble reinstalled finally back to factory
how to:
use @condi S.onyXT.S [UNBRICKER] v1.0 and download all 2 files by choosing 1 for US(use for you correct version)
-unbrick data.zip
-update.zip
this program will unpack to the 3 files:
-image.img
-hiden.img
-unbrick.img
after download Win32DiskImager from here http://sourceforge.net/projects/win32diskimager/files/latest/download
take any SD card and upload unbrick.img to SD card by Win32DiskImager
when is done be sure all ABD driver installed and tablet is visible in device manager OK!!! when install drivers disable Microsoft signing driver enforcement!!!
add SD card to tablet and start tablet
cold boot info have show at top left corner
start @condi S.onyXT.S [UNBRICKER] v1.0 and choose 7
press enter and connect tablet to PC
!!!process will take approx 30min!!! be patience
-on the end error appears in @condi program don't worry
-restart tablet manually by holding power button
-boot to android
-some APP will missing
after do full restore by recovery console :
-off tablet by holding power button
-push and hold volume + and pres power button once
-count to 9 and release volume button
-recovery console appears and do factory restore
after is tablet finally back and working jeeeeeee :laugh::laugh::laugh:
what simple process I panicking last week haha
urgas said:
than with trouble reinstalled finally back to factory
how to:
use @condi S.onyXT.S [UNBRICKER] v1.0 and download all 2 files by choosing 1 for US(use for you correct version)
-unbrick data.zip
-update.zip
this program will unpack to the 3 files:
-image.img
-hiden.img
-unbrick.img
after download Win32DiskImager from here http://sourceforge.net/projects/win32diskimager/files/latest/download
take any SD card and upload unbrick.img to SD card by Win32DiskImager
when is done be sure all ABD driver installed and tablet is visible in device manager OK!!! when install drivers disable Microsoft signing driver enforcement!!!
add SD cart to tablet and start tablet
cold boot info have show at top left corner
start @condi S.onyXT.S [UNBRICKER] v1.0 and choose 7
press enter and connect tablet to PC
!!!process will take approx 30min!!! be patience
on the end error appears in program dont worry
restart tablet manually
let the boot to android
some APP will missing
after do full restore by recovery console :
off tablet
push and hold volume + and one power button once
count to 9 and release volume button
recovery console appears and do factory restore
after is tablet finally back and working jeeeeeee :laugh::laugh::laugh:
what simple process I did panicking last week haha
Click to expand...
Click to collapse
Ok regarding your english "restore" =reset
What generation tab do you have
Your english is just terrible if your going to do a guide like you have plz correct your grammer and your confusing words
I appreciate that english might not be your first language but your posts are confusing and will not be much help to people
Sent from my SGPT12 using XDA Free mobile app
xts unbrick
rassegan said:
Hey guys @davhenry @stifilz i could finally recover my Sony Xperia Tablet S following these steps and the Sony's Unbricker Software 1.0 by @condi
1) Unzip the software and make a new folder called "UNBRICK_DATA"
2) Download manually the files unbrick.zip and the correct OTA Software of your tablet
3) Unzip the unbrick.zip file and copy in the SD Card with Win32DiskImager
4) Rename your OTA Software ( Example: signed-txs03_201-ota-131023018.zip) to update.zip
5) Copy this file in the folder "files" in the program
6) Open and DOS Console in Windows and descrypt the file using desklunvr.exe. Example : desklunvr.exe update.zip
7) Make 2 image files with the recently file generate (update_deslunvr)
7za.exe x update_desklunvr.zip system.img
7za.exe x update_desklunvr.zip hidden.img
8) Copy the new images files and update_desklunvr in UNBRICK_DATA (these last file i did just in case )
9) Run Condi´s Program and make sure you go to the step 6 and just follow the instructions
The tablet reboot 2 times at the beginning looks like not working because get stuck in sony logo but turn off and turn on again and then ITS WORKSS !!! :laugh:
Good luck guys
Click to expand...
Click to collapse
Hi everybody thanks for this great topic
i try to follow this procedure but cannot find the files "unbrick.zip" you mentioned.
searched for a while with no success.
thanks for your help. :good:
Where the heck did you find all those files you mention?
Yes it works again
My Sony xperia s tablet sgpt1211 works again, thanks @condi
It wasn't easy but this is how it worked for me
1. download @condi unbricker program
@condi Unbricker (http://forum.xda-developers.com/show....php?t=2642436)
2. Run using option 3 (I have an eu no 3g tablet)
it will create all the files you need in a folder named unbrick_data
the software will probably fail at the step to create the sd card - no worries
3. dowload Win32DiskImager and write a copy of the unbrick.img file to the SD Card with the Win32DiskImager software.
4. Run @condi unbricker program and use option 7
after you put the sd card in the tablet just press the start button only and it should display the cold booting text on the sony logo page so you know something is working.
5. be patient and let the @condi software work through each step - some take up to one hour to complete.
6. If you get an error message from the @condi software you have to resolve the problem it won't work if an error occurs. You need to stop and go back through the steps again.
Keep trying it does work if you can solve all the hiccups.
Thanks again @condi
gordo588 said:
My Sony xperia s tablet sgpt1211 works again, thanks @condi
It wasn't easy but this is how it worked for me
1. download @condi unbricker program
@condi Unbricker (http://forum.xda-developers.com/show....php?t=2642436)
2. Run using option 3 (I have an eu no 3g tablet)
it will create all the files you need in a folder named unbrick_data
the software will probably fail at the step to create the sd card - no worries
3. dowload Win32DiskImager and write a copy of the unbrick.img file to the SD Card with the Win32DiskImager software.
4. Run @condi unbricker program and use option 7
after you put the sd card in the tablet just press the start button only and it should display the cold booting text on the sony logo page so you know something is working.
5. be patient and let the @condi software work through each step - some take up to one hour to complete.
6. If you get an error message from the @condi software you have to resolve the problem it won't work if an error occurs. You need to stop and go back through the steps again.
Keep trying it does work if you can solve all the hiccups.
Thanks again @condi
Click to expand...
Click to collapse
after root
Now my sony xperia tablet s open in this screen
ples. help my
Q&A for [Z2][TWRP][PhilZ Touch][CWM] XZDualRecovery Q&A
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
failed to backup in cwm/twrp
Hi my dual boot cant bakup anything i think sometjing blocking me, sorry i just finished rooting then installed the dualboot. The only problem is i cant backup or flash anything.. Tia
I was wondering if after using the installer to get recovery, when I flash my first rom do I need to flash the dual recovery flashable zip before rebooting from new rom install to keep rexovery in case install fails?
Sent from my D6503 using XDA Free mobile app
benjmiester said:
I was wondering if after using the installer to get recovery, when I flash my first rom do I need to flash the dual recovery flashable zip before rebooting from new rom install to keep rexovery in case install fails?
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
Yep, that is the safest root to go.
Sent from my SGP311 using XDA Free mobile app
Xperia Z2 Dual recovery (NUT) : questions
Good morning,
I have a new Xperia Z2, and I want to change my recovery and root my phone.
I have few questions on this recovery (http://forum.xda-developers.com/showthread.php?t=2785598).
1/ With a bootloader locked, it is possible to add a recovery like TWRP. So, is it a risk with this action on the DRM ? (I think that no but the bootloader stay locked but i prefer to ask)
2/ I don't see a firmware compatibility, I have a .304 firmware, it is compatabile ?
3/ When I install with dual recovery on my phone, I can root like any phone since recovery ?
4/ With this dual recovery (or whit root), i can install the ota update or not ?
Thank you for the time spent to reading me,
Have a nice day,
After encrypting phone (enable encryption from Settings -> Security menu), I can't make nandroid backups. Using custom ROM (AICP). Does anyone have this working?
I installed XZDualRecovery, but CWM doesn't seem to support encryption, and TWRP (2.7.x) fails to decrypt the partition.
I tried to install TWRP 2.8.0.1, but after copying to the FOTAKernel partition, can't boot into the recovery. LED turns orange, USB disconnects, and screen stays black.
i try unrooted way on 4.4.4 and didnt work .i try flashtools eroot vroot tower root and so goes on ......
can u release update so we can install recovery and root in locked bootloader??
in our forum every one is waiting for root 4.4.4!!!!!
Hi guys ..is there a flashable zip to change my current recovery to this one?and does this recovery show my sdcard ?
Sent from my D6503 using XDA Free mobile app
---------------
Admin Note: this thread has a dedicated questions and answers section which you can access here -->.
Sent from my D6503 using XDA Free mobile app
Oh yes!!! thank you Sir!!!
Not working on z2 4.4.4
is there anyother way to flash recovery in z2 4.4.4
Hello,
I have the same error in Twrp: failed to decrypt data.
On my Xperia Z with 4.4.4 and same Twrp version (2.7.1.0 I believe) decryption of data works.
So I guess it has to do with the specific version for the Z2?
I have no idea how to fix this. Any suggestions?
Sent from my D6503 using XDA Free mobile app
Is it safe to update via ota even i have custom recovery installed? And im trying to remove the recover but there is no charge file to delete
can i use philz touch to flash a new rom in my m919 s4?
can i use philz touch to flash a new rom in my m919 s4? please reply thanks in advance
Hi,
i rooted my stock 4.4.2 and made a CWM / Philz backup.
When the official Update came out, i flashed this prerooted 4.4.4 ROM
Includung the 5) fix and the deodex patch.
Now that the battery drain is too high for me, i want to restore my old backup from 4.4.2
But the recovery can't find any files.
+ I already tried to copy the backup to /data/media/clockworkmod/backup/
+ And i also tried to delete the nandroid.md5
+ And i unchecked the "check md5" box in philz settings
Log file:
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on (UTC) Sun May 31 15:12:24 1970
framebuffer: fd 4 (1080 x 1920)
PhilZ Touch 6.48.4
ClockworkMod v6.0.5.0
Ievice target: Xperia Z
I:Touch GUI revision: 1.30
No /etc/extra.fstab
recovery filesystem table
=========================
0 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot 0
1 /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system 0
2 /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache 0
3 /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata -16384
4 /storage/sdcard1 auto /devices/platform/msm_sdcc.3/mmc_host/mmc1 0
5 /storage/usbdisk auto /devices/platform/msm_hsusb_host/usb 0
6 /tmp ramdisk ramdisk 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 /preload during fstab generation!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
W:Unable to get recovery.fstab info for /external_sd during fstab generation!
I:Completed outputting fstab.
I:Connected to Vold..
I:110 0 sdcard1 /storage/sdcard1 0
I:110 0 usbdisk /storage/usbdisk 0
I:200 0 Volumes listed.
Irocessing arguments.
I:Cannot load volume /misc.
I:Cannot load volume /misc.
I:Checking arguments.
stage is []
I:device_recovery_start()
I:auto_restore_settings set to default (true)
I:check_root_and_recovery set to default (true)
I:compression_value set to default (low)
I:twrp_backup_mode set to default (false)
I:enable_md5sum=1
I:show_nandroid_size_progress set to default (1)
I:use_nandroid_simple_logging set to default (1)
I:nand_prompt_on_low_space set to default (1)
I:signature_check_enabled set to default (0)
I:install_zip_verify_md5 set to default (0)
I:set_brightness set to default (160)
E:Unable to create brightness sys file!
I:menu_height_increase=40
I:show_virtual_keys=1
I:min_log_rows set to default (3)
I:background_image set to default (default)
I:background_image set to default
Iefault stitch background loaded.
I:show_background_icon set to default (false)
I:show_battery set to default (true)
I:show_clock set to default (true)
I:menu_text_color set to default (8)
I:menu_background_color set to default (1)
I:menu_highlight_color set to default (7)
I:normal_text_color set to default (0)
I:menu_separator_color set to default (6)
I:header_text_color set to default (8)
I:batt_clock_color set to default (2)
I:menu_background_transparency set to default (102)
I:menu_highlight_transparency set to default (102)
I:menu_separator_transparency set to default (102)
I:show_menu_separation set to default (true)
I:dim_timeout set to default (60)
I:blank_timeout set to default (180)
I:scroll_sensitivity=80
I:touch_accuracy set to default (7)
I:touch_to_validate=1
I:enable_vibrator=0
I:boardEnableKeyRepeat set to default (true)
I:wait_after_install set to default (true)
I:slide_left_action set to default (5)
I:slide_right_action set to default (3)
I:double_tap_action set to default (2)
Iress_lift_action set to default (4)
Iress_move_action set to default (1)
I:t_zone=1
I:t_zone_offset=0
I:use_dst_time=1
__bionic_open_tzdata: couldn't find any tzdata when looking for NFT-1DFT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
I:Current time: 1970-05-31 17:12:25 (UTC +1:00) DST
I:use_qcom_time_daemon set to default (0)
I:use_qcom_time_offset set to default (1)
I:use_qcom_time_data_files set to default (0)
I:applying rtc time offset...
I:Current time: 1970-05-31 17:12:26 (UTC +1:00) DST
I:Using since_epoch to correct time failed!
Iarse_t_daemon_data_files: Setting time offset from file /data/time/ats_2, offset 1403918478334
I:Current time: 2014-11-25 17:33:44 (UTC +1:00) DST
Command: "/sbin/recovery"
af.resampler.quality=255
ro.cm.device=yuga
ro.cm.display.version=11-20140718-UNOFFICIAL-yuga
ro.cm.version=11-20140718-UNOFFICIAL-yuga
ro.cm.releasetype=UNOFFICIAL
ro.qc.sdk.audio.fluencetype=none
ro.sf.lcd_density=480
ro.com.google.clientidbase=android-google
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.com.android.wifi-watchlist=GoogleGuest
ro.cwm.enable_key_repeat=true
ro.ril.transmitpower=true
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.boot.emmc=true
ro.boot.baseband=msm
ro.boot.hardware=qcom
ro.boot.serialno=CB5A1ZDKED
ro.boot.bootloader=s1
ro.emmc=0
ro.hwui.path_cache_size=32
ro.hwui.layer_cache_size=48
ro.hwui.texture_cache_size=72
ro.hwui.gradient_cache_size=1
ro.hwui.r_buffer_cache_size=8
ro.hwui.drop_shadow_cache_size=6
ro.hwui.text_large_cache_width=2048
ro.hwui.text_small_cache_width=1024
ro.hwui.text_large_cache_height=1024
ro.hwui.text_small_cache_height=1024
ro.hwui.texture_cache_flushrate=0.4
ro.wifi.channels=
ro.allow.mock.location=0
ro.board.platform=msm8960
ro.build.id=KTU84Q
ro.build.date=Fri Jul 18 15:49:47 CEST 2014
ro.build.date.utc=0
ro.build.host=venus
ro.build.tags=test-keys
ro.build.type=userdebug
ro.build.user=nut
ro.build.display.id=cm_yuga-userdebug 4.4.4 KTU84Q 7ed5c22dac test-keys
ro.build.product=yuga
ro.build.selinux=1
ro.build.version.sdk=19
ro.build.version.release=4.4.4
ro.build.version.codename=REL
ro.build.version.incremental=7ed5c22dac
ro.build.description=C6603-user 4.2.2 10.3.A.0.423 WP5_rg test-keys
ro.build.fingerprint=Sony/C6603_1270-6697/C6603:4.2.2/10.3.A.0.423/WP5_rg:user/release-keys
ro.build.characteristics=default
ro.input.noresample=1
ro.config.ringtone=Orion.ogg
ro.config.alarm_alert=Hassium.ogg
ro.config.notification_sound=Argon.ogg
ro.secure=1
ro.vendor.extension_library=/system/lib/libqc-opt.so
ro.carrier=unknown
ro.cmlegal.url=http://www.cyanogenmod.org/docs/privacy
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.name=C6603
ro.product.board=MSM8960
ro.product.brand=Sony
ro.product.model=Xperia Z
ro.product.device=yuga
ro.product.locale.region=US
ro.product.locale.language=en
ro.product.manufacturer=Sony
ro.baseband=msm
ro.bootmode=unknown
ro.hardware=qcom
ro.opengles.version=196608
ro.qualcomm.bt.hci_transport=smd
ro.revision=0
ro.serialno=CB5A1ZDKED
ro.telephony.call_ring.multiple=0
ro.telephony.default_network=9
ro.bootloader=s1
ro.debuggable=1
ro.modversion=11-20140718-UNOFFICIAL-yuga
ro.rommanager.developerid=cyanogenmod
ro.factorytest=0
ro.setupwizard.enterprise_mode=1
com.qc.hardware=true
lpa.decode=true
net.bt.name=Android
net.change=net.bt.name
init.svc.adbd=running
init.svc.vold=running
init.svc.healthd=running
init.svc.ueventd=running
init.svc.recovery=running
init.svc.setup_adbd=stopped
init.svc.xzdualrecovery=stopped
rild.libpath=/system/lib/libril-qc-qmi-1.so
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
debug.composition.type=dyn
dalvik.vm.heapsize=512m
dalvik.vm.lockprof.threshold=500
dalvik.vm.heapmaxfree=8m
dalvik.vm.heapminfree=2m
dalvik.vm.dexopt-flags=m=y
dalvik.vm.heapstartsize=16m
dalvik.vm.heapgrowthlimit=192m
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.heaptargetutilization=0.75
persist.gps.qmienabled=true
persist.hwc.mdpcomp.enable=true
persist.sys.dun.override=0
persist.sys.usb.config=mtp,adb
persist.sys.dalvik.vm.lib=libdvm.so
persist.sys.root_access=1
persist.sys.recovery_update=false
persist.audio.fluence.mode=endfire
persist.audio.handset.mic=analog
persist.audio.lowlatency.rec=false
persist.radio.add_power_save=1
persist.radio.apm_sim_not_pwdn=1
service.adb.root=1
keyguard.no_require_sim=true
telephony.lteOnGsmDevice=1
telephony.lteOnCdmaDevice=0
I:Checking for extendedcommand & OpenRecoveryScript...
I:Script file found: '/cache/recovery/extendedcommand'
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
I:setting up /data/media(/0) for /sdcard.
SD Card mounted...
Verifying SD Card marker...
I:Running script:
I:
run_program("/sbin/cp", "-R", "/cache/recovery", "/tmp/recovery");
ui_print("ROM Manager Version 5.5.3.7");
ui_print("25. November 2014");
assert(restore_rom("/sdcard/clockworkmod/backup/Backup4.4.2-TOP-Nov", "boot", "system", "data", "cache", "sd-ext"));
parse returned 0; 0 errors encountered
about to run program [/sbin/cp] with 4 args
ROM Manager Version 5.5.3.7
25. November 2014
I:setting up /data/media(/0) for /sdcard/clockworkmod/backup/Backup4.4.2-TOP-Nov.
>> Checking MD5 sums...
I:setting up /data/media(/0) for /sdcard/clockworkmod/backup/Backup4.4.2-TOP-Nov.
E:cannot open md5file
E:MD5 verification failed!
result was NULL, message is: assert failed: restore_rom("/sdcard/clockworkmod/backup/Backup4.4.2-TOP-Nov", "boot", "system", "data", "cache", "sd-ext")
I:setting up /data/media(/0) for /sdcard.
= Tapatalk @ Xperia Z2 =
just hangs...
i have the adb drivers installed and i have unknown sources checked, debugging enabled..
but when i try the towelroot metod, it just hangs when it gets to libdvm opened
just hangs...
i cant find any log files but
model d6503
my firmware is 23.0.1.a.0.167
when it starts to say doing the magic...
it just hangs and nothing completes
anyone?
using this on cm
Hi! Is it possible to use this fantastic dual recovery with cm11?
I prefer twrp, so.... If there's any way please help me out.
Thanks
Shakib Haris said:
Hi! Is it possible to use this fantastic dual recovery with cm11?
I prefer twrp, so.... If there's any way please help me out.
Thanks
Click to expand...
Click to collapse
No but you can try at your own risk !
Sent From Somewhere On Earth With My Z2 ^^
Thanks for Reply
i tried. but no good.
SD card issues
I hope my question is not unrelated but I started experiencing some problems after installing the dual recovery:
1)I had a 4.4.4 stock ROM, unlocked bootloader, tried some flashing via flashtool, got bootloop, successfully flashed 4.4.2 via flashtool and installed this dual recovery
2)After installing I saw the SONY logo for about 30 seconds, considered it „stuck“ and powered off (power+UP)
3)NEW ISSUE: Then I found out that the booting only „takes ages“ (about 1 minute to enter recovery) which does not happen when I take my SD card out – everything is fast then. As far as I read a full wipe before installing a new ROM should solve it (I want to install rooted 4.4.4 stock zip including the dual recovery).
4)OLD ISSUE: Copying anything from PC to SD card inserted in phone via USB is unusable, takes eons. SD card in card reader works well. Copying to the internal storage from PC works well, too.
5)ISSUE: When I copy a ZIP onto the SD card inserted in my computer, put it back into Z2, wait the mentioned minute for booting into recovery and try to install the zip, the file is not there. I tried it several times, used different folders but the phone always finds and deletes the file before entering the recovery.
EDIT: Now, this is strange and it seems it is not related to the phone - when copy the filed via cardreader, remove the card and insert it again into the cardreader, the files are gone...
I would really appreciate any tips/hints/links. Thanks in advance for your time.
EDIT: So the problem was a bad sector on the SD (TestDisk reported...), the SD claiming itself to be write protected... I will ask for a replacement. With my old 16 GB card everything is smooth...
[Q&A] [ROM][ROOT][CWMv6CTRv2.5/TWRPv2.7.1.0][MT6589 - 4GB - KK 4.4.2] BLU Life Play
Q&A for [ROM][ROOT][CWMv6CTRv2.5/TWRPv2.7.1.0][MT6589 - 4GB - KK 4.4.2] BLU Life Play L100
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][ROOT][CWMv6CTRv2.5/TWRPv2.7.1.0][MT6589 - 4GB - KK 4.4.2] BLU Life Play L100. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Life play won't update
Hi all,
I have Blu Life with Android 4.2.1, software V18 and CWM installed.
I'm trying to update to the latest software version (V31), but it doesn't work: CWM says a generic "installation aborted".
I attach the log below.
Please help!
Starting recovery on Sat Oct 25 18:52:20 2014
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (720 x 1280)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
Carliv Touch Recovery
MTK CWM-based v6.0.4.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/bootimg (null) 0
2 /cache ext4 /dev/block/mmcblk0p6 (null) 0
3 /data ext4 /dev/block/mmcblk0p7 (null) 0
4 /misc emmc /dev/misc (null) 0
5 /recovery emmc /dev/recovery (null) 0
6 /emmc vfat /dev/block/mmcblk0p8 (null) 0
7 /system ext4 /dev/block/mmcblk0p5 (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!
W:Unable to get recovery.fstab info for /external_sd during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
Warning: No file_contexts
I:device_recovery_start()
Command: "/sbin/recovery"
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=mt6589
ro.revision=0
ro.emmc=0
ro.boot.emmc=0
ro.factorytest=0
ro.secure=0
ro.allow.mock.location=1
persist.mtk.aee.aed=on
ro.debuggable=1
persist.service.adb.enable=1
persist.sys.usb.config=mass_storage,adb
persist.service.acm.enable=0
ro.mount.fs=EXT4
ro.build.id=JOP40D
ro.build.version.incremental=eng.znsj_bianyi5.1369448473
ro.custom.build.version=1369448473
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.1
ro.build.date=Sat May 25 10:22:52 CST 2013
ro.build.date.utc=1369448572
ro.build.type=user
ro.build.user=znsj_bianyi5
ro.build.host=znsj-ian5
ro.build.tags=test-keys
ro.product.board=gionee89_dwe_jb2
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
ro.build.product=gionee89_dwe_jb2
ro.build.description=gionee89_dwe_jb2-user 4.2.1 JOP40D eng.znsj_bianyi5.1369448473 test-keys
ro.build.fingerprint=alps/gionee89_dwe_jb2/gionee89_dwe_jb2:4.2.1/JOP40D/1369448473:user/test-keys
ro.build.flavor=
ro.build.characteristics=default
ro.mediatek.version.release=ALPS.JB2.MP.V1.2
ro.mediatek.platform=MT6589
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=ALPS.JB2.MP
ro.mediatek.version.sdk=1
ro.gn.theme.prop=yes
ro.gn.theme.default=/system/app/Android.gnz
ro.gn.extmodel=LIFE
ro.gn.extvernumber=WBWX192BR_0101_V5578
ro.gn.extHWvernumber=Mainboard_P1
ro.gn.gnznvernumber=WBWX192BR_0101_T5578
ro.gn.gnromvernumber=ROM4.2.a
ro.gn.gnvernumber=WBWX192BR_0101_V5578
ro.gn.gnprojectid=WBWX192
ro.gn.gnproductid=WBWX192BR_0101
ro.gn.phone=yes
ro.gn.contacts.support=yes
ro.gn.oversea.music.offline.ver=yes
ro.gn.msgbox.prop=yes
ro.gn.msgsdring.prop=yes
ro.gn.phone.vibrateOnConnect=yes
ro.gn.statusbar.gionee.style=2
ro.gn.settings.OnOffAirplane=yes
ro.gn.phone.overturnMute=yes
ro.gn.phone.powerOnRing=yes
ro.gn.menu.cancel=yes
ro.gn.optrspecsegdef=NONE
persist.sys.timezone=America/Mexico_City
ro.build.display.id=BLU_L100i_V07_GENERIC
ro.product.model=LIFE PLAY
ro.product.brand=BLU
ro.product.name=BLU
ro.product.device=BLU
ro.product.manufacturer=BLU
ro.cta.support=no
ro.gn.match.numberlength=7
ro.gn.default.videocall=TelephoneRing.mp3
ro.config.notification_sound=Msgtone.mp3
ro.config.alarm_alert=AlarmClock2.mp3
ro.config.ringtone=TelephoneRing.mp3
ro.gn.default.ringtone2=TelephoneRing.mp3
ro.gn.default.mmstone=Msgtone.mp3
ro.gn.default.mmstone2=Msgtone.mp3
ro.gn.display.single.imei=no
ro.gn.operator.showslot=no
ro.gn.shutdown=yes
ro.gn.mmi.test=yes
ro.gn.gnvernumberrel=01W
ro.gn.customerservice=no
ro.gn.shutdown.noconfirm=yes
ro.gn.contacts.newfeature=yes
ro.gn.contacts.gndialersearch=yes
ro.gn.music.srs=no
ro.gn.music.effect=no
ro.gn.email.prop=yes
ro.gn.oversea.product=yes
ro.gn.oversea.custom=SOUTH_AMERICA_BLU
ro.gn.popupmsg.prop=no
ro.gn.encryption.prop=yes
ro.gn.transparent.prop=yes
ro.gn.settings.prop=yes
gn.mmi.mic2=no
gn.mmi.keytest.menu=yes
gn.mmi.keytest.app=no
gn.mmi.receiver2=yes
ro.gn.theme.style=0
ro.gn.soundrecorder.support=yes
ro.gn.zoomclipview.prop=yes
ro.gn.operator.showdigitalslot=yes
ro.gn.delayupdateSignalStrength=no
ro.gn.export.import.support=yes
ro.gn.popdefaultvalue.prop=no
ro.gn.email.cn.support=yes
ro.gn.powersaving.support=yes
ro.gn.singlescreen.support=yes
ro.gn.screenshot.prop=yes
ro.gn.haptic.vibrator.prop=yes
ro.gn.oversea.odm=yes
ro.gn.phone.nowallpaper=no
ro.gn.usb.ui.support=yes
ro.gn.gemini.ringtone.support=yes
ro.gn.mtk.poweroff.alarm.prop=yes
ro.gn.switchstorage.prop=yes
ro.gn.check.autotime.prop=yes
ro.gn.systemui.theme.support=yes
ro.gn.newfeature.v3=yes
ro.gn.theme.net.support=no
ro.gn.theme.combinpkg=com.android.camera&com.android.gallery3d
ro.gn.gallery=yes
ro.gn.cell.conn.platform.4.1=yes
ro.gn.audioprofile.support=yes
ro.gn.sms.recipient.limit=200
ro.gn.wifidirect.support=yes
ro.gn.android.4.1=no
ro.gn.changer.online.support=no
ro.gn.remove.custom.theme=yes
ro.gn.hide.theme.entrance=yes
ro.gn.changer.removefont=yes
ro.gn.remove.calendar.lunar=yes
ro.gn.salesstatistic.support=
ro.gn.rootstatistic.support=
ro.mtk.vt3g324m.support=yes
ro.gn.hardware=P1
ro.gn.widget.support=yes
ro.gn.action.reboot.support=yes
ro.gn.music.dts=yes
ro.gn.gemini.support=yes
ro.mtk.gemini.3gswitch=no
ro.gn.adups.fota.support=yes
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
wifi.interface=wlan0
ro.mediatek.wlan.wsc=1
ro.mediatek.wlan.p2p=1
mediatek.wlan.ctia=0
wifi.tethering.interface=ap0
ro.opengles.version=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
ro.sys.usb.mtp.whql.enable=0
sys.ipo.pwrdncap=2
ro.sys.usb.storage.type=mtp,mass_storage
ro.sys.usb.bicr=yes
ro.sys.usb.charging.only=yes
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
ril.specific.sm_cause=0
gps.solution.combo.chip=1
ril.external.md=0
fmradio.driver.chip=3
ro.sf.hwrotation=0
ril.current.share_modem=2
launcherplus.allappsgrid=2d
launcher2.allappsgrid=3d_20
curlockscreen=1
ro.mediatek.gemini_support=true
persist.radio.fd.counter=15
persist.radio.fd.off.counter=5
persist.radio.fd.r8.counter=15
persist.radio.fd.off.r8.counter=5
persist.mtk.wcn.combo.chipid=-1
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=1
ril.radiooff.poweroffMD=1
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
mediatek.wlan.chip=MT6628
mediatek.wlan.module.postfix=_mt6628
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.adups.fota.oem=gionee
ro.adups.fota.device=LIFE PLAY
ro.adups.fota.version=BLU_L100i_V07_GENERIC
init.svc.ueventd=running
init.svc.recovery=running
init.svc.adbd=running
service.adb.root=1
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
W:failed to mount /dev/block/mmcblk1p1 (No such file or directory)
SD Card mounted...
Verifying SD Card marker...
I:Running script:
I:
run_program("/sbin/cp", "-R", "/cache/recovery", "/tmp/recovery");
ui_print("ROM Manager Version 5.5.3.7");
ui_print("October 25, 2014");
ui_print("Preparing to install ROM...");
run_program("/cache/dowipedalvikcache.sh");
mount("/system");
run_program("/sbin/chmod", "+x", "/tmp/recovery/11-rommanager.sh");
run_program("/tmp/recovery/11-rommanager.sh", "place");
run_program("/sbin/umount", "/system");
assert(install_zip("/sdcard/adupsfota/update.zip"));
parse returned 0; 0 errors encountered
about to run program [/sbin/cp] with 4 args
ROM Manager Version 5.5.3.7
October 25, 2014
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/mmcblk0p6 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk1p2 on /sd-ext failed: No such file or directory
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/chmod] with 3 args
about to run program [/tmp/recovery/11-rommanager.sh] with 2 args
mount: mounting /dev/block/mmcblk0p5 on /system failed: Device or resource busy
about to run program [/sbin/umount] with 2 args
-- Installing: /sdcard/adupsfota/update.zip
Finding update package...
I:Update location: /sdcard/adupsfota/update.zip
Opening update package...
Installing update...
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/adupsfota/update.zip")
p137 said:
Hi all,
I have Blu Life with Android 4.2.1, software V18 and CWM installed.
I'm trying to update to the latest software version (V31), but it doesn't work: CWM says a generic "installation aborted".
[/FONT][/SIZE]
Click to expand...
Click to collapse
Flash the TWRP KK ROM in post#1 and retry. You can flash CWMv6CTRv2.5 too if you want.
But the update process has some details:
- new firmware: flash recovery original KK ROM in post#1
- if you deleted any application by system ROM you not can update because script stop that's
So...reflash ROM original.
You can make the backup of the your ROM and after update can restore it...
I'm trying upload 2 files zip to flash with CWM or TWRP for update ROM based on v31 with ROOT...but let me time to put links for L100i and L100a.
*please don't use Rom manager apk. Use the flashfy or mobileuncletools to flash recovery original, CWM or TWRP and with this flash update
Sent from my LIFE PLAY X KK using XDA Free mobile app
I found out I in fact removed a couple of stock apps, so I restored them (I had a backup) and tried again... Same error.
I also tried with CWM 2.5 and the original KK, but no luck again. It just says "Installation aborted" without any detail.
I guess flashing the original ROM should work for sure, but it needs a bit more time...
Thank you anyway for the advice
p137 said:
I found out I in fact removed a couple of stock apps, so I restored them (I had a backup) and tried again... Same error.
I also tried with CWM 2.5 and the original KK, but no luck again. It just says "Installation aborted" without any detail.
I guess flashing the original ROM should work for sure, but it needs a bit more time...
Thank you anyway for the advice
Click to expand...
Click to collapse
Hmmmm... Im understand now.
So..flash recovery original JB and try..
This errors happen because you remove apps...
The second option is: flash file unzipped clockworkmod...(the last version)...zip with CWMv2.2 or CWMv2.4 ....
Look to spoiler option: BLPv15 Anatel backups
Restore it and try update with recovery original.....
Sent from my LIFE PLAY X KK using XDA Free mobile app
The run.bat script is not rooting my Blu Life Play L100 running 4.4.2. See attached photo.
sapa243 said:
The run.bat script is not rooting my Blu Life Play L100 running 4.4.2. See attached photo.
Click to expand...
Click to collapse
Since v13 this method not work in JB ROM!!
To ROOT device with KK ROM is need use other methods. Look to VRoot or put CWM/TWRP and use my patch ROOT...
http://forum.xda-developers.com/showthread.php?p=56689819
If you want a ROM total ROOT see on the post#4....
http://forum.xda-developers.com/showthread.php?p=43809212
Sent from my LIFE PLAY X KK using XDA Free mobile app
If it makes a difference I have L100a_V31. I tried iRoot aka vRoot and many other one click root apps with no sucess. I have never had so much difficulty rooting an android phone before. I guess it's a problem with little known phones.
I would love to use your patch or flash a rom but I can't use TWRP or CWM because I'm not root. Unless I'm missing something.
lopestom said:
So..flash recovery original JB and try..
Click to expand...
Click to collapse
It worked!
Thank you for the help.
Unfortunately now I have the same problem as sapa243: I don't know how to root as I no longer have CWM (I had to remove it to upgrade), and neither framaroot nor the software in the first post work anymore.
I haven't tried vRoot yet but as I have the same configuration as sapa243 I suppose it wouldn't work for me too...
:crying:
sapa243 said:
If it makes a difference I have L100a_V31. I tried iRoot aka vRoot and many other one click root apps with no sucess. I have never had so much difficulty rooting an android phone before. I guess it's a problem with little known phones.
I would love to use your patch or flash a rom but I can't use TWRP or CWM because I'm not root. Unless I'm missing something.
Click to expand...
Click to collapse
Very users BLU device with KK has make ROOT with VRoot or KingoRoot:
http://forum.xda-developers.com/android/development/root-blu-vivo-iv-kitkat-4-4-2-t2854480
https://plus.google.com/103692731781849525983/posts/78o13j3vb35
http://forum.xda-developers.com/sitesearch.php?q=vroot
*ENABLE USB DEBUGGING is need
Settings- About device - Click 5 times on version of the firmware (build number)- go back and you see DEVELOPER OPTIONS.
But if this options not work search something here:
https://plus.google.com/communities/117846429749085694805
Another method to put CWM or TWRP is use SPFT. This is explained in the first post.
Sent from my LIFE PLAY X KK using XDA Free mobile app
lopestom said:
Very users BLU device with KK has make ROOT with VRoot or KingoRoot:
http://forum.xda-developers.com/android/development/root-blu-vivo-iv-kitkat-4-4-2-t2854480
https://plus.google.com/103692731781849525983/posts/78o13j3vb35
http://forum.xda-developers.com/sitesearch.php?q=vroot
*ENABLE USB DEBUGGING is need
Settings- About device - Click 5 times on version of the firmware (build number)- go back and you see DEVELOPER OPTIONS.
But if this options not work search something here:
https://plus.google.com/communities/117846429749085694805
Another method to put CWM or TWRP is use SPFT. This is explained in the first post.
Sent from my LIFE PLAY X KK using XDA Free mobile app
Click to expand...
Click to collapse
I finally got root and flashed a recovery. Thank you!!!
The Kingo Root below worked for me.
https://plus.google.com/103692731781...ts/78o13j3vb35
lopestom said:
Very users BLU device with KK has make ROOT with VRoot or KingoRoot:
http://forum.xda-developers.com/android/development/root-blu-vivo-iv-kitkat-4-4-2-t2854480
https://plus.google.com/103692731781849525983/posts/78o13j3vb35
http://forum.xda-developers.com/sitesearch.php?q=vroot
*ENABLE USB DEBUGGING is need
Settings- About device - Click 5 times on version of the firmware (build number)- go back and you see DEVELOPER OPTIONS.
But if this options not work search something here:
https://plus.google.com/communities/117846429749085694805
Another method to put CWM or TWRP is use SPFT. This is explained in the first post.
Sent from my LIFE PLAY X KK using XDA Free mobile app
Click to expand...
Click to collapse
I tried Kingo root but it didn't work for me, as I understood by the text running on the phone, because I don't have the original recovery (I installed original_JB to do the update).
I didn't install vRoot as soon I saw it wat completely full of malware and bloatware (still removing some of them )
Finally I tried with SP flash tool but it seems I cannot get the MTK driver installed properly (it gives some code 10 error after the installation completes).
So, can I flash the patch you were mentioning with original_JB recovery, or I risk to do some damage?
Otherwise in a couple of days I'll have access to a Vista pc ane try again with SP tool...
Thanks again for the support
p137 said:
I tried Kingo root but it didn't work for me, as I understood by the text running on the phone, because I don't have the original recovery (I installed original_JB to do the update).
I didn't install vRoot as soon I saw it wat completely full of malware and bloatware (still removing some of them )
Finally I tried with SP flash tool but it seems I cannot get the MTK driver installed properly (it gives some code 10 error after the installation completes).
So, can I flash the patch you were mentioning with original_JB recovery, or I risk to do some damage?
Otherwise in a couple of days I'll have access to a Vista pc ane try again with SP tool...
Thanks again for the support
Click to expand...
Click to collapse
If you has CWM or TWRP yes you can install the patch...
If you are with JB ROM try FRAMAROOT mentioned in post#1.
The problem to ROOT in device is virus suppose and this in not true. On the PC is same problem and you should disable OS security and disable antivirus.
But for me is the same process with patch or application. But for Framaroot application have success on the JB ROM is need enable USB DEBUGGING and enable settings-security-Unknown sources! Set ROOT in FRAMAROOT anf Reboot manually....
If you have the original recovery I think this patch not work...is your choose!
If you have CWM/TWRP my suggest to you is that install the KK ROM LT20 localized in post#7. This is a v31 KK ROM and little modified... If have update future by BLU this will updating normally.
http://forum.xda-developers.com/showthread.php?p=43809212
Sent from my LIFE PLAY X KK using XDA Free mobile app
lopestom said:
If you has CWM or TWRP yes you can install the patch...
If you are with JB ROM try FRAMAROOT mentioned in post#1.
The problem to ROOT in device is virus suppose and this in not true. On the PC is same problem and you should disable OS security and disable antivirus.
But for me is the same process with patch or application. But for Framaroot application have success on the JB ROM is need enable USB DEBUGGING and enable settings-security-Unknown sources! Set ROOT in FRAMAROOT anf Reboot manually....
If you have the original recovery I think this patch not work...is your choose!
If you have CWM/TWRP my suggest to you is that install the KK ROM LT20 localized in post#7. This is a v31 KK ROM and little modified... If have update future by BLU this will updating normally.
http://forum.xda-developers.com/showthread.php?p=43809212
Sent from my LIFE PLAY X KK using XDA Free mobile app
Click to expand...
Click to collapse
I now have CWM (flashed with SPFT), and I installed your patch.
After reboot SuperSU asks to install the binaries, but the normal install fails and using CWM it doeesn't work: it downsn't reboot into recovery automatically and when I do it manually nothing happens...
What can I do?
I'm beginning to thing I will have to install the complete rom from http://forum.xda-developers.com/showthread.php?p=43809212#post43809212
But I have a question: I backup with CWM and then install the rom; after this, to recover all my data and apps, do I have to do an advanced (selective) restore? If I do a plain restore of the backup do I loose the root again?
p137 said:
I now have CWM (flashed with SPFT), and I installed your patch.
After reboot SuperSU asks to install the binaries, but the normal install fails and using CWM it doeesn't work: it downsn't reboot into recovery automatically and when I do it manually nothing happens...
What can I do?
I'm beginning to thing I will have to install the complete rom from http://forum.xda-developers.com/showthread.php?p=43809212#post43809212
But I have a question: I backup with CWM and then install the rom; after this, to recover all my data and apps, do I have to do an advanced (selective) restore? If I do a plain restore of the backup do I loose the root again?
Click to expand...
Click to collapse
I see other user with more partition patch happen this error to update binaries...
You should apply this...option Normal and reboot manually... If this not work is need look something that you made or changed in your device.
You can install LT20 and if this has error or bootloop... Is because your device has very modification as change partition!! You should changing to original ROM and options by factory.....
When you flash the LT20 yes you can restore your data (not data JB ROM) and not for lost ROOT because it's on the other folders....
Sent from my LIFE PLAY X KK using XDA Free mobile app
Hi lopestorm. I wanted to root my Blu Life Play. In the last posts of the thread, you gave two files, claiming they are the same and needed to be flashed through cwm or twrp. But their content is different. Can you check the files please. Like i said, they are not the same.
android_künefe said:
Hi lopestorm. I wanted to root my Blu Life Play. In the last posts of the thread, you gave two files, claiming they are the same and needed to be flashed through cwm or twrp. But their content is different. Can you check the files please. Like i said, they are not the same.
Click to expand...
Click to collapse
Sorry guy... I not use any software or application to ROOT KK ROM.
I flash the CWM or TWRP on the post#1 with SPFT and flash zipfile by SuperSU... Its this...
Post#242
http://forum.xda-developers.com/showthread.php?p=54478286
[ROM][ROOT][CWMv6CTRv2.5/TWRPv2.7.1.0][MT6589 - 4GB - KK 4.4.2] BLU Life Play L100
But others users wrote that Vroot or Kingoroot apk ROOT KK ROM...
Look: https://plus.google.com/105638313908320121488/posts/Sisn7XcsC9H
Sent from my LIFE PLAY X KK using XDA Free mobile app
It's Blu life play mini L190 kitkat 4.4.2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you help me please, i can't root it with famaroot and other popular root methods aren't working please help
Call_Me_Hudson said:
It's Blu life play mini L190 kitkat 4.4.2
Can you help me please, i can't root it with famaroot and other popular root methods aren't working please help
Click to expand...
Click to collapse
You need more knowledge for remove two files (recovery.img and boot.img) of the your device for create custom recoveries.
Has too more information with MTK DROID TOOLS for create scatter file to flash with SPFT that's custom recoveries.
All this is if you cannot Root!
Sent from my LIFE PLAY X KK using XDA Free mobile app
Can anyone tell me how to merge internal and phone storage on BLU Life Play L100i? "Phone "SD" storage" Is useless and i would like to have all storage for system apps. I tried some app ( i forgot name), and bricked the phone Now i am back to stock unrooted ROM. And I am trying to find out what to do. Will flashing this rom help? Thanks
[Q&A] [GUIDE] How to build CWM-based Recovery from source in Ubuntu 12.04 with CM-11
Q&A for [GUIDE] How to build CWM-based Recovery from source in Ubuntu 12.04 with CM-11.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE] How to build CWM-based Recovery from source in Ubuntu 12.04 with CM-11.0. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
My phone has 16mb recovery part but the recovery.img I made is 25 mb so I can't flash it In BoardConfig.mk, I can wrote at least 24.936.448 at the line of BOARD_RECOVERYIMAGE_SIZE to compile the recovery image. How can I solve this problem? Can I reduce the size of the .img file to 16 mb?
denizyildizi345 said:
My phone has 16mb recovery part but the recovery.img I made is 25 mb so I can't flash it In BoardConfig.mk, I can wrote at least 24.936.448 at the line of BOARD_RECOVERYIMAGE_SIZE to compile the recovery image. How can I solve this problem? Can I reduce the size of the .img file to 16 mb?
Click to expand...
Click to collapse
I don't understand how you ended up with such a big recovery... The biggest ramdisk I saw (in TWRP) is not more than 4-5 Mb. Do you have a kernel over 20Mb? It can't be, otherwise the stock recovery will be oversized too. Somewhere you made a mistake probably.
And to answer your question, no you can't reduce the size of recovery that big; if you have a kernel compressed in xz, you may try to compress the ramdisk in xz too, and the size will be smaller, but not enough... you need to downsize it with 9Mb, which is not possible.
So check again, to see if there isn't a mistake somewhere.
carliv said:
I don't understand how you ended up with such a big recovery... The biggest ramdisk I saw (in TWRP) is not more than 4-5 Mb. Do you have a kernel over 20Mb? It can't be, otherwise the stock recovery will be oversized too. Somewhere you made a mistake probably.
And to answer your question, no you can't reduce the size of recovery that big; if you have a kernel compressed in xz, you may try to compress the ramdisk in xz too, and the size will be smaller, but not enough... you need to downsize it with 9Mb, which is not possible.
So check again, to see if there isn't a mistake somewhere.
Click to expand...
Click to collapse
I took a screenshot of my CM11-0/out/target/product/msm8226/root folder which is 25 mb. There is a boot.img file. I think the problem is that file. I unpacked a few recovery.img files but none of them included that file. If problem is this, how can I remove that file from my ramdisk?
I removed that file and flashed new recovery.img but now my phone isn't booting in recovery mode.
denizyildizi345 said:
I took a screenshot of my CM11-0/out/target/product/msm8226/root folder which is 25 mb. There is a boot.img file. I think the problem is that file. I unpacked a few recovery.img files but none of them included that file. If problem is this, how can I remove that file from my ramdisk?
I removed that file and flashed new recovery.img but now my phone isn't booting in recovery mode.
Click to expand...
Click to collapse
No, for checking recovery root you need to look here: CM11-0/out/target/product/msm8226/recovery/root . But anyway that folder looks strange (I see a perl script there)....
Check my screenshot below.
And type a
Code:
make clobber
before stating a new build, or
Code:
make clean
between repetitive builds.
im getting this error each time i try to compile:
make: *** No rule to make target `/etc/init.rc'
please any suggestions
george676 said:
im getting this error each time i try to compile:
make: *** No rule to make target `/etc/init.rc'
please any suggestions
Click to expand...
Click to collapse
You need to be more specific: what recovery you try to build, in what environment (if it's not cm-11), and post a link to your device folder tree. That error means that the compiler can't find an init.rc file to add in ramdisk.
Compiler stops after a few segments
This is shown in my terminal:
Code:
cp: cannot stat ‘/home/paul/cm-10.2/out/target/product/Ultra/root/init.recovery.*.rc’: No such file or directory
make: [/home/paul/cm-10.2/out/target/product/Ultra/recovery/root.ts] Error 1 (ignored)
mkdir -p /home/paul/cm-10.2/out/target/product/Ultra/recovery/root/system/bin
cp -rf device/CherryMobile/Ultra/recovery/root /home/paul/cm-10.2/out/target/product/Ultra/recovery/
cp: omitting directory ‘device/CherryMobile/Ultra’
make: *** [/home/paul/cm-10.2/out/target/product/Ultra/recovery/root.ts] Error 1
[email protected] ~/cm-10.2 $ make clobber
And you wrote about the problem:
During the build process you may encounter some errors or warnings.
*********************
Code:
Code:
cp: cannot stat `/home/carliv/CM11-0/out/target/product/P780/root/init.recovery.*.rc': No such file or directory
make: [/home/carliv/CM11-0/out/target/product/P780/recovery/root.ts] Error 1 (ignored)
This will not stop the build, and it appears if you don't use a init.recovery.{hardware}.rc file. Can be ignored, as the build process does.
Though in my terminal it just stopped at that part so I had to rename mine which was originally init.recovery.qcom.rc to init.recovery.*.rc
--edit--
And yet it still would not continue ... Any ideas on how to fix this?
--edit # 2--
Here's the pastebin link just in case ->biQ7kjV8 add that to pastebin...(I can't post links)
--edit # 3--
I fixed it... Turns out that it was just a BoardConfig.mk parameter that I forgot to complete
Calculate proper BoardConfig.mk partition sizes
I have this log:
Code:
----- Making recovery image ------
/home/paul/cm-10.2/out/target/product/Ultra/recovery.img maxsize=8380416 blocksize=135168 total=8409088 reserve=270336
error: /home/paul/cm-10.2/out/target/product/Ultra/recovery.img too large (8409088 > [8650752 - 270336])
make: *** [/home/paul/cm-10.2/out/target/product/Ultra/recovery.img] Error 1
make: *** Deleting file `/home/paul/cm-10.2/out/target/product/Ultra/recovery.img'
Meaning I have wrong sizes for the partitions so I need help on it...
When I ran the following:
cat /proc/mtd
cat /proc/emmc
they both return: No such file or directory...
Now If I run the command: cat /proc/partitions
it comes up with this:
As far as I know.... mmcblk1p1 is my external sd card which is about 32 GB...
My system image is about 1 GB and more(confirmed) when I used the dd command(to dump it) and is located at mmcblk0p16
Userdata reaches more than 4 GB as reported by the dd command(file size too large) and is located at mmbblk0p25
here(recovery.fstab):
/boot mtd /dev/block/mmcblk0p10
/cache yaffs2 /dev/block/mmcblk0p18
/data yaffs2 /dev/block/mmcblk0p25
/misc mtd /dev/block/mmcblk0p20
/recovery mtd /dev/block/mmcblk0p19
/system yaffs2 /dev/block/mmcblk0p16
-- edit --
I solved this already
Help required for compiling CWM for android 4.4.2 version only?
I am on Ubuntu 14.0.4 and I am trying to build a CWM recovery for Celkon Q 5009android 4.4.2, Broadcom processor). I have set up build environment and currently working on syncing repo. I have heard that it takes too much time and disk space to complete this process. I am interested to know in the following particular scenario : want to build only CWM recovery from source for an android running on version 4.4.2. So do I have to download all repositories or is there any shortcut that would enable me to not download all, but a certain part that is required for android 4.4.2? If yes, how to go about it? please help.
Please help. I do not undertstand why 'repo sync' always fails at a particular stage, though I have 30+ GB of disk space available in my working folder named 'cm12'. Following is the last screen message :
Fetching project platform/external/ant-glob
Fetching projects: 8% (40/495) Receiving objects: 86% (2389/2771), 26.68 MiBerror: RPC failed; result=56, HTTP code = 200iB | 124.00 KiB/s
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
remote: Sending approximately 1.94 GiB ...
remote: Counting objects: 85, done
remote: Finding sources: 100% (85/85)
error: RPC failed; result=56, HTTP code = 200iB | 88.00 KiB/s
fatal: The remote end hung up unexpectedly
Now should I run 'repo sync' again or should I use 'repo sync -j1' ?
fatal: early EOF
fatal: index-pack failed
error: Cannot fetch device/lge/mako-kernel
error: Exited sync due to fetch errors
Hey,
In which size are the values in BoardConfig.mk at BOARD_BOOTIMAGE_PARTITION_ZISE? bit?
And how I can convert blocks to this size because my lge only print out the partition sizes in blocks.
LG Noel
Black Manta said:
Hey,
In which size are the values in BoardConfig.mk at BOARD_BOOTIMAGE_PARTITION_ZISE? bit?
And how I can convert blocks to this size because my lge only print out the partition sizes in blocks.
LG Noel
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=60297989&postcount=51
Somewhere around that post you will find your answer.
Hi. Your guide is the most useful I found on the net. Much more than the official cyanogenmod wiki's porting one. Thanks a lot.
I'm trying to use it to build a cm 12.1 (lollipop) cwm on a mediatek device.
1) My stock rom (also Android 5.1) already ships a fstab.mt6795 file into the ramdisk. I moved it inside /recovery/root, and copied its content in /recovery/recovery.fstab
This is its content, should I make any change inside it?
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,resize,encryptable=footer
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#please add cip or persist on project fstab
#/dev/block/platform/mtk-msdc.0/by-name/persist /persist ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#/dev/block/platform/mtk-msdc.0/by-name/custom /custom ext4 ro wait
/devices/mtk-msdc.0/11230000.MSDC0 auto vfat defaults voldmanaged=sdcard0:[email protected],noemulatedsd
/devices/mtk-msdc.0/11240000.MSDC1 auto vfat defaults voldmanaged=sdcard1:auto
/devices/bus.2/11270000.USB3_XHCI auto vfat defaults voldmanaged=usbotg:auto
/dev/block/platform/mtk-msdc.0/by-name/frp /persistent emmc defaults
2) How can I find out which of the .rc files available in stock ramdisk include in my recovery, besides the renamed init.rc copied from /bootable/recovery/etc ?
3) My stock rom obviously already ships a init.mt6795.rc. Should I merge any of its lines to the one I copied from /bootable/recovery/etc in my /recovery folder?
Thanks in advance for your time and your efforts.
4javier said:
Hi. Your guide is the most useful I found on the net. Much more than the official cyanogenmod wiki's porting one. Thanks a lot.
I'm trying to use it to build a cm 12.1 (lollipop) cwm on a mediatek device.
1) My stock rom (also Android 5.1) already ships a fstab.mt6795 file into the ramdisk. I moved it inside /recovery/root, and copied its content in /recovery/recovery.fstab
This is its content, should I make any change inside it?
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,resize,encryptable=footer
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#please add cip or persist on project fstab
#/dev/block/platform/mtk-msdc.0/by-name/persist /persist ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#/dev/block/platform/mtk-msdc.0/by-name/custom /custom ext4 ro wait
/devices/mtk-msdc.0/11230000.MSDC0 auto vfat defaults voldmanaged=sdcard0:[email protected],noemulatedsd
/devices/mtk-msdc.0/11240000.MSDC1 auto vfat defaults voldmanaged=sdcard1:auto
/devices/bus.2/11270000.USB3_XHCI auto vfat defaults voldmanaged=usbotg:auto
/dev/block/platform/mtk-msdc.0/by-name/frp /persistent emmc defaults
2) How can I find out which of the .rc files available in stock ramdisk include in my recovery, besides the renamed init.rc copied from /bootable/recovery/etc ?
3) My stock rom obviously already ships a init.mt6795.rc. Should I merge any of its lines to the one I copied from /bootable/recovery/etc in my /recovery folder?
Thanks in advance for your time and your efforts.
Click to expand...
Click to collapse
First let me ask you where did you find a cwm for lollipop to build it? I'm interested to see that.
Second in recovery fstab you may want to add emmc partitions like boot, recovery... Check my github and look at elephone p6000 device folder (it's close enough to understand). If internal sdcard is on data/media you don't have to add it at all in fstab (at least that was the rule for kitkat... again I need to see the source for that lollipop cwm to tell you exactly). In elephone device recovery fstab you can see that usb and external sdcard are defined as auto for type not vfat because it is better to let minivold manage that.
Normaly for cm12.1 ther is no need to copy any rc file in root, only the fstab. {hardware}, which you said you did.
Again I can tell more if I will see the source code for the recovery, and last thing my guide is quite old now but I'm glad you found it useful.
Thanks for your quick reply.
I think I've not been so clear explaining what I'm doing: when I talk about "Lollipo CWM" I just mean that I'm working on 12.1 branch of cyanogenmod source tree, that as you know is based on the same sources of Lollipop, instead of the one the guide was originally aimed to.
1) I feel really dumb at this moment. I don't know exactly how many time I read that fstab file, and I never noticed that it lacks entries for partitions not managed by stock recovery. Sorry if I wasted your time with a stupid question.
2)For sdcards, then it's better to leave untouched the voldmanaged options, but change the filesystem type to auto?
3) I don't need to copy any other .rc file (init.mt6795.usb.rc, init.xlog.rc, etc...), nor to merge anything from init.mt6795.rc of the stock rom. Right?
Thanks again.
4javier said:
Thanks for your quick reply.
I think I've not been so clear explaining what I'm doing: when I talk about "Lollipo CWM" I just mean that I'm working on 12.1 branch of cyanogenmod source tree, that as you know is based on the same sources of Lollipop, instead of the one the guide was originally aimed to.
1) I feel really dumb at this moment. I don't know exactly how many time I read that fstab file, and I never noticed that it lacks entries for partitions not managed by stock recovery. Sorry if I wasted your time with a stupid question.
2)For sdcards, then it's better to leave untouched the voldmanaged options, but change the filesystem type to auto?
3) I don't need to copy any other .rc file (init.mt6795.usb.rc, init.xlog.rc, etc...), nor to merge anything from init.mt6795.rc of the stock rom. Right?
Thanks again.
Click to expand...
Click to collapse
I did understand it's cm12.1, but that was my question since there is no cwm for cm12.1 only cyanogenmod recovery which is different. At the moment I only recommend twrp for cm12.1+ and for that you have to use a different fstab, easy to find on github or here on xda in twrp threads.
Then, if I'm not too much confused:
- since CM12, Clockworkmod isn't anymore included in its source tree
- if I don't set any RECOVERY_VARIANT it defaults to CyanogenMod Recovery, not CWM anymore
- the recovery.img I built is, at its best, a Cyanogenmod recovery
- the recovery.fstab I used (the one i posted before, but now with /boot, /recovery and /nvram entries added) is in version 2 format, that twrp doesn't understand. So I have to find out how to convert in the old fstab format.
Am I right?
Another question: I used the last version of your CarlivKitchen. That doesn't offer anymore the choice to re/pack for standard android or for mtk images, because it automatically detect the format. But when it repacks, it adds the mtk header if the original image had it? Or am I forced to use a custom boot image maker?
4javier said:
Then, if I'm not too much confused:
- since CM12, Clockworkmod isn't anymore included in its source tree
- if I don't set any RECOVERY_VARIANT it defaults to CyanogenMod Recovery, not CWM anymore
- the recovery.img I built is, at its best, a Cyanogenmod recovery
- the recovery.fstab I used (the one i posted before, but now with /boot, /recovery and /nvram entries added) is in version 2 format, that twrp doesn't understand. So I have to find out how to convert in the old fstab format.
Am I right?
Another question: I used the last version of your CarlivKitchen. That doesn't offer anymore the choice to re/pack for standard android or for mtk images, because it automatically detect the format. But when it repacks, it adds the mtk header if the original image had it? Or am I forced to use a custom boot image maker?
Click to expand...
Click to collapse
Yes for all and for twrp fstab I think you can study device folders from twrp github (few are mediatek).
My kitchen now detects if image has mtk header and will repack it the same way (it stores a variable in unpacked folder which will tell that it must add a mtk header).
I decided to follow this guide to integrate the changes needed to build twrp instead of cwm: http://forum.xda-developers.com/showthread.php?t=1943625
It doesn't cover all the preparation steps like yours do. Do you think there are changes to be made to make your guide suitable for cm12 and twrp, or I can follow it until the " Build a CWM-based Recovery " paragraph?