Hi all,
I currently facing boot looping on all 2.1 roms.
I.ve done a full wipe.
I've tried re partition my sd card but it's useless.
I've tried remove sd card & reboot (checking is my card cause the prob)
I was only able to flash those 1.5 rom.
My sd info @ siggy below.
go in recovery wipe phone then flash rom?
flash to the googlebits after flashing the rom?
Do a FULL wipe.
If you're using an 2.0+ ROM, you NEED a 2.6.29+ kernel.
i have done all the wipe. i have try to flash gbit after the rom or after reboot & flash. & kernal is in a rom which made by dev right?
You probably do something wrong
1. Wipe data/dalvik/ext
2. Flash ROM
3. Reboot
and now should work...
Maybe Radio issue??
Which ROM did You tried?
Sustanon said:
You probably do something wrong
1. Wipe data/dalvik/ext
2. Flash ROM
3. Reboot
and now should work...
Maybe Radio issue??
Which ROM did You tried?
Click to expand...
Click to collapse
im a flashaholic i know how to flash a rom as u see i able to flash 1.5 rom but not 2.1 rom. but previously i could flash 2.1 rom till recently i can't. & radio is lastest if im not wrong... i've try those current 2.1 on xda now.
and what does logcat say about the bootloop?
Was trying to flash aHerov0.3
i do run
adb logcat
./sbin/sh: exec: line 1: logcat: not found
Click to expand...
Click to collapse
so i use the move recovery log to sd & got this:
Starting recovery on Mon Mar 1 14:42:19 2010
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
Build : RA-hero-v1.5.3.1
Fixing execute permissions for /cache
I:Set boot command "boot-recovery"
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.ril.ecc.HTC-WWE=999
ro.build.id=CUPCAKE
ro.build.display.id=CUPCAKE.eng.u70000.20090827.103405
ro.build.version.incremental=eng.u70000.20090827.103405
ro.build.version.sdk=3
ro.build.version.release=1.5
ro.build.date=Thu Aug 27 10:35:04 CST 2009
ro.build.date.utc=1251340504
ro.build.type=user
ro.build.user=u70000
ro.build.host=Android-X02
ro.build.tags=test-keys
ro.product.model=HTC Hero
ro.product.brand=htc_wwe
ro.product.name=htc_hero
ro.product.device=hero
ro.product.board=hero
ro.product.manufacturer=HTC
ro.product.locale.language=
ro.product.locale.region=
ro.board.platform=msm7k
ro.build.product=hero
ro.build.description=2.73.405.5 146733 CL#61267 release-keys
ro.build.changelist=61267
ro.product.ua=
ro.build.fingerprint=htc_wwe/htc_hero/hero/hero:1.5/2.73.405.5/61267:user/test-keys
keyguard.no_require_sim=1
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.hep=1
wifi.interface=tiwlan0
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
wifi.supplicant_scan_interval=45
ro.sf.lcd_density=160
ro.com.google.locationfeatures=1
persist.service.mount.playsnd=0
settings.display.autobacklight=1
settings.display.brightness=102
ro.ril.def.agps.mode=2
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.networklocation=1
ro.config.ringtone=Innovation.mp3
ro.config.notification_sound=Color.mp3
ro.config.alarm_sound=Light.mp3
ro.config.cal_notification=Vector.mp3
ro.config.msg_notification=Ascend.mp3
ro.setupwizard.mode=DISABLED
ro.com.google.clientidbase=android-htc
ro.config.sync=yes
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.modversion=RA-hero-v1.5.3.1
ro.factorytest=0
ro.serialno=HT99CL900166
ro.bootmode=recovery_manual
ro.baseband=6.35.09.26
ro.carrier=HTC-Australia
ro.bootloader=1.76.2007
ro.hardware=hero
ro.revision=128
ro.cid=HTC__023
init.svc.recovery=running
init.svc.adbd=running
I:Set boot command ""
I:Set boot command ""
Move recovery.log to SD
Press HOME to confirm,
any other key to abort.
Moving : .
Click to expand...
Click to collapse
help help
recovery.log only helps if you have problems with with the recovery. either add adb to ahero or get another rom where it works...
what do you mean add adb to ahero? i though adb on my pc work on android device?
i'v tried
kagudroid
ahero
vanillain
ckdroid
openeclair
chpoubs
hero21
villain
but none is working for me...
sorry i meant add logcat to ahero, not adb. of course adb is on the pc.
Code:
[email protected]:~$ adb shell ls -l /system/bin/logcat
-rwxr-xr-x 1 0 2000 9736 Aug 1 2008 /system/bin/logcat
kendong2 said:
sorry i meant add logcat to ahero, not adb. of course adb is on the pc.
Code:
[email protected]:~$ adb shell ls -l /system/bin/logcat
-rwxr-xr-x 1 0 2000 9736 Aug 1 2008 /system/bin/logcat
Click to expand...
Click to collapse
adb shell ls -l/system/bin/logcat-rwxr-xr-x <<< likdis?
that should show you how it *should* look...
i downloaded ahero (took forever...). it actually contains logcat (would be stupid to leave it out anyway), not sure why you get that error. here is what you do, make sure to follow the steps exactly:
0: obviously boot to recovery.
1: make sure your update.zip is correct, redownload when in doubt.
2: go through wipes 1&3 (data and ext), reboot again to recovery.
3: flash the rom.
4. "adb pull /tmp/recovery.log ."
5. reboot and start logcat. you can do this: "adb logcat > logcat.txt", then the output will be redirected to logcat.txt. if it loops and you recognise the loop (i.e. the bootanimation starting from the beginning) let it loop twice, then cancel logcat with ctrl-c. if you don't see the loop wait 3 to 5 minutes, then cancel.
6. zip that recovery.log and logcat.txt and put it here.
let's hope that works.
still dont understand from step 4 onward =.=" sorry for being a dumb
Code:
adb pull <remote> <local>
copies a file from your phone to your pc. the file on your phone is obviously /tmp/recovery.log, the period "." at the end stands for the current directory (probably something like c:\androidsdk\tools if you are on win). you can also use
Code:
adb pull /tmp/recovery.log c:\recovery.log
same goes for pushing
Code:
adb push <local> <remote>
local is your pc, remote your phone.
adb logcat gives you the log output of your phone. there is a lot of data going through, so might wanna redirect that into a file with the ">" sign:
Code:
adb logcat > file.xyz
again pay attention for the path, if you don't specify it the current directory is used. when in doubt use the full path:
Code:
adb logcat > c:\file.xyz
now try again, and if you still have problems please be more specific what your problem is. say what works and what doesn't, and if there are error messages quote them here. and what operating system are you using on your pc?
Here: logcat&recovery.rar
e.japonica said:
Here: logcat&recovery.rar
Click to expand...
Click to collapse
do you have an ext4 partition on your sdcard? if so repartition to ext2 or ext3 (ext2 if you ask me), since we don't have the kernel sources we can not add ext4 support to the kernel used in 2.1.
if you don't have an ext4 partition then repartition aswell, the problem is with the ext partition:
Code:
I//system/bin/sh( 44): mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: Invalid argument
edit: saw your signature now... could've thought of that earlier
but now you see how easy it is once you supply the correct information. if you had attached that logcat to your first post you've had the answer in the second post...
edit2: you might wanna leave out that swap partition. not sure how different roms react to that, and it wasn't there in the original setup (as in when it left htc's factory).
so i should make my ext partition to 2/3?
and swap = 0?
actually i didn't know the use of swap as i just following guide. as for ext partition i only know is for the a2sd
Thanks Kendong you help me out again! you'r very nice
Related
If you ...
find a bug or problem on 2.2, post here
find a solution on how to fix the bug, post here
want to get help on how to fix the bug, post here
anything else, goes here
This thread are meant for bug/problem solution and reported bug list of 2.2 custom ROM which i will try to manage, so people are not posting same bug, and asking for same solution all over again in X10 Custom ROM AOSP thread.
Limitation
Cannot Mount via USB
2.2 Custom ROM put the SYSTEM partition on your phone memory and the DATA partition in your SD card. That is why you cannot dismount the SD card from Android to mount to your PC.
No App2SD
2.2 Custom ROM is still running on 2.1 Custom Kernel which not supporting this.
Bug list
#0001 - WiFi not working - Fixed on 2.2
#0002 - Random android.process.media force close - Fixed on 2.2
#0003 - Home button not working, and no Lock Screen - Fixed on 2.2
#0004 - Cannot install certain APK (Angry Bird)
#0005 - No radio, no network and flashing Home - New on 0.0.2
#0006 - ADB shell have SU access, but Titanium Backup cannot work - New on 0.0.2
#0007 - SD Card non-ascii folder show as ???
#0008 - Facebook Contact Sync not available
#0009 - CPU Governor set to performance by default
Solutions for bugs
#0001 - How to enable WiFi on 2.2 Custom ROM
1. Try to enable WiFi, of course it will not work.. just do it.
2. WiFi will goes off automatically
3. Run
Code:
adb shell /system/bin/wlan_tool
4. If the adb stucks, just press CTRL+C
5. Repeat step 4 until you crash the phone
6. After reboot, your WiFi will work.
or
Code:
adb shell killall servicemanager
Post Reference
#0002 - android.process.media FC solution
0.0.1 compiled with prefilled databases which invalid for your phone
Code:
adb shell
cd /data/data/com.android.providers.media/databases
rm *
reboot
or this will ensure no invalid data anymore but will remove fixes for bug #0003
Code:
adb shell
cd /data/
rm -r data
mkdir data
reboot
Post Reference
#0003 - Fix Home Button & Lock Screen
Download sqlite here
First pull the db file first.
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
Then add value to its content
Code:
sqlite3.exe settings.db
sqlite> INSERT INTO "secure" VALUES(67,'device_provisioned','1');
sqlite> .exit
Then push back the db
Code:
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
Then reboot.
Post Reference
#0004 - Solving installing APK problems
Currently the 2.2 Custom ROM does not support app2sd, and some APK may configure it self to be installed in sdcard.
So we force it to install on internal with code below
Code:
adb shell pm setInstallLocation 1
adb install -l com.rovio.angrybirds.apk
Post Reference
#0005 - Fixing radio, wifi and home screen flashing problem
Run this command
Code:
adb shell killall servicemanager
Post Reference
#0006 - Fixing SU access for Titanium Backup
Run this command
Code:
adb shell chmod 4755 /system/bin/su
Post Reference
#0007 - Fixing SD card mount command to show unicode letters
Modify your chargemon file so its enables utf8 for non ascii letter.
You need to do this on 2.1 ROM, not 2.2 ROM. The file is located in /system/bin
look for this
Code:
mount -t vfat -o rw,noatime,nodiratime /dev/block/mmcblk0p1 /sd
and change into this
Code:
mount -t vfat -o rw,noatime,nodiratime,utf8 /dev/block/mmcblk0p1 /sd
Notes:
You must use a Unix/Linux format capable text editor for this. Notepad will not work.
You can try ultraedit for it.
Post Reference
#0008 - Fix Facebook Sync
Download the ContactsProvider.apk here, then install to your Android using push command
Code:
adb push ContactsProvider.apk /system/app/ContactsProvider.apk
adb reboot
Post Reference
#0009 - Using SetCPU
By default is Performance, fast but wasting too much battery.
Use SetCPU and set to OnDemand.
Post Reference
2.2 Custom ROM FAQ
How and what happened if upgrade from 0.0.1 to 0.0.2?
Just copy data.img and system.img replacing your current one in FreeX10 folder.
This will replace all your 0.0.1 data, be sure to back up first with Titanium Backup
WiFi is running and connected, but cannot browser
This problem seems to be occurring on selected few.. You can set static IP to your android.
Go to Settings -> Wireless ... -> WiFi, then press menu button. From there you can se static IP
Is there a possibility of Timescape and Mediascape for 2.2 Custom ROM
The answer is yes, its possible.
I managed to install Mediascape.apk into 2.2 Custom ROM, but cannot run.
The reason it cannot run is because UX is using a lot of things in Framework-res.apk, images, layout, styles, and etc which cannot be copied directly from SE 2.1 into 2.2 AOSP. It requires someone to properly put all values, resolving conflicts inside Framework-res.apk before the UX can run, which will take months or at least weeks if someone dedicated his or her day job for it. Then after that we still need to deal with external files. So in conclusion, while it still possible, i don't think anyone will do it because of the time demanding process.
I want to help devs solving bugs, i found one but i don't know what actually happend.
While usb connected, from command prompt, type
Code:
adb logcat > logcat.txt
This will output a lot of debugging info into logcat.txt file, later if you find bug, you take a look inside the file.
See anything error or info related to the bug, and post here.. When writing the logcat.txt output, but them inside
Code:
brackets.
Do not post everything.. post few lines related to the bugs.
2.2 Custom ROM Testing Tools
Service Menu
WARNING: DO NOT INSTALL THIS UNLESS YOU DO DEVS, END USER DO NOT INSTALL
PURPOSE: MAYBE FOR TESTING DEVICE FEATURE, MIGHT BREAK SYSTEM APPS
Enable SE Service Menu for device testing. For devs only. You need to put adb stuff in the directory for install.bat to run.
Install framework
Code:
adb push permissions /system/etc/permissions
adb push lib /system/framework
adb reboot
Install applications
Code:
adb install app\bootinfo3.apk
adb install app\ServiceMenu2.apk
adb install app\com.laac.launcher.servicemenu.apk
Nice work. THis is handy
As i posted in the Main thread!
I think some of the force closes, (mainly acore and google framework) and the fact that the market crashes, come down to importing a vcard!
I imported vcard, get many force closes, market stops working, I clean install and don't install the vcard. Everything functions fine.
I do believe this is the reason!
Greeet ~~!! but can u tell me the seloution of this proplem :
i was run 2.2 001 ok ? then i back to to SE 2.1 to change old system.img & data.img by the new on FreeX10_alpha-release_0.0.2-UPDATE , ok ? then i reboot my phone into 2.2 , it run but like u make a refresh on computer ! evry 3 second !
thnx
Ahmed radi said:
Greeet ~~!! but can u tell me the seloution of this proplem :
i was run 2.2 001 ok ? then i back to to SE 2.1 to change old system.img & data.img by the new on FreeX10_alpha-release_0.0.2-UPDATE , ok ? then i reboot my phone into 2.2 , it run but like u make a refresh on computer ! evry 3 second !
thnx
Click to expand...
Click to collapse
Please read the main post!
sorry but no one answer me there
Thanks
Thanks for this ,hopefully a post like this is made for the 1st post on 2.1
http://forum.xda-developers.com/showpost.php?p=9134882&postcount=1
awesome thread, very helpful. Hopefully more people will read this rather than constantly posting the same bugs in the main thread.
Ahmed radi said:
sorry but no one answer me there
Click to expand...
Click to collapse
hey ahmed
grb el solution da
#0005 - Fixing radio, wifi and home screen flashing problem
Run this command
Code:
adb shell killall servicemanager
i think en da el 7l
bye
bsthost said:
hey ahmed
grb el solution da
#0005 - Fixing radio, wifi and home screen flashing problem
Run this command
Code:
adb shell killall servicemanager
i think en da el 7l
bye
Click to expand...
Click to collapse
i dont know how to use adb shell is there anythread for newbie user how to use adb ?
angry birds on my x10 is working well....i take it from a previous backup and restrored on 2.2 with mybackup pro
Please post to http://forum.xda-developers.com/showthread.php?t=835308&page=9999 thread instead.
We don't need to create two discussion thread.
i fixed the wifi and flashing problem and i have connected to wifi but i cant access internet or market any it seems i have connected to my modem netwok still cant access to internet any idea how to fix this?
17mayis said:
i fixed the wifi and flashing problem and i have connected to wifi but i cant access internet or market any it seems i have connected to my modem netwok still cant access to internet any idea how to fix this?
Click to expand...
Click to collapse
Code:
setprop ro.kernel.android.ndns 2
setprop net.eth0.dns1 8.8.8.8
setprop net.eth0.dns2 8.8.4.4
New crash this morning : i tried to connect my BT headphone after that i've activated BT => BT has desactivated itself then the phone reboots.
zephyrix said:
Code:
setprop ro.kernel.android.ndns 2
setprop net.eth0.dns1 8.8.8.8
setprop net.eth0.dns2 8.8.4.4
Click to expand...
Click to collapse
i appreciate your answer man if you could tell me how to do this ? through adb shell or something else?
17mayis said:
i dont know how to use adb shell is there anythread for newbie user how to use adb ?
Click to expand...
Click to collapse
Google is your friend!
i have flashPlayer10.1 problem it,s to slow when i play on any website any solution what might be ?
I'm sorry it took so long, I got lots of stuff to deal with. Good things are worth waiting for (i heard)
First off: You are responsible for any of your actions! Changes that are needed to boot Ubuntu on your folio will void your warranty!
Special Thanks goes to DerArtem for posting his Kernels, Weeds2000 for eMail support, topogigi for wifi hacking and last but not least the Ubuntu-Touch Team on IRC that made it possible for me to tweak the touchscreen driver.
However, the system you are about to create is not fully functional, there are still things missing (a working sound driver for example). Its nice to play with it anyway
Heres a quick walk-through:
We will flash a kernel to the toshiba folio tablet which makes it possible to boot from an sdcard or USB-stick (You have to choose one, we need at least 2GB, I'd recommend 4GB so you can install fancy stuff like OpenOffice etc.).
We will then create a root filesystem with rootstock, which will hold our Ubuntu system (similar to your hard drive-Ubuntu).
Finally, we have to tweak that filesystem and change passwords, copy wifi driver etc.
Then we're able to boot a beautiful Ubuntu.
Things you will need:
- A Computer running Linux (Debian / Ubuntu would be great. If you're not running Linux on your computer, running it on the folio would make absolutely no sense. Please don't ask, I don't know how to install it in Windows.)
- The files i added to this post
- A SD-Card, 2-4 GB should be fine.
- optional: A second SD-card, 128MB would be enough (for flashing)
- A USB hub (If you want to boot from USB AND use a keyboard.
- Some time... =)
The first thing you should do is flash one of the update.zip files; choose update-sdmmc.zip (this will boot your folio from sdcard) or update-usb.zip (this will boot from a usb pen drive), open it and unpack the content to a sdcard (This has to be a SDcard, we're gonna flash our device from there.)
Backup all your data on your folio (I'm serious! It'll be gone!) and turn it off.
Put the SDcard in its slot and turn the folio back on. Press + hold both power and volume up.
Follow instructions to do a system update (If you've never done this before you shouldn't start now =) )
When it reboots, your folio will show some funny black and white linux text stuff and hang somewhere. Congratulations! You just bricked your tablet. Now lets see how we can fix it... Turn it off (Keep power pressed for about 5 seconds) and take out the sdcard, put it in your PC.
It's getting messy now, so grab a beer and let's go:
Open a Terminal on your linux computer.
Code:
#echo "Hello world!"
If your console says "Hello World" you got it. Awesome! =)
Code:
#sudo apt-get install rootstock gparted
This will install rootstock, the tool we're gonna need to create our filesystem, as well as gparted, a tool for partitioning our flash drive. You can also install rootstock-gtk, the graphical version. Try it if you like:
Code:
#sudo apt-get install rootstock-gtk
I heard that ubuntu-netbook won't work because there are drivers missing, would somebody try that and report please?
If your beer is already empty when this is done, you need a faster computer. Tell your wife the guys at xda-developers told you so
Back to the terminal:
Code:
#sudo rootstock -f MyCoolHostName -l myCoolUserName -p myCoolPassword --seed xubuntu-desktop -i 2G --notarball
This will create our filesystem with a user called "myCoolUserName" and (theoretically) his password "myCoolPassword" and install a basic xubuntu-desktop. I had to change the password manually because it didn't work this way... We'll do that later.
Rootstock will download lots of packages (You could also set it up with "--seed ubuntu-desktop", then youll download even more packages or "--seed ubuntu-minimal" or kubuntu... I still didnt find a list of seeds online :-/
The creating will take quite some time, get another beer.
When this is done, you'll get a file like this : "qemu-armel-201104112120.img". We will now mount this image: (make sure the directory /mnt/ does exist and is empty:
Code:
#ls -la /mnt )
Code:
#sudo su
(its simpler to be root for now)
Code:
#mount -o loop qemu-armel-201104112120.img /mnt/
(You are aware that your filename is different, are you? Try this:
Code:
# mount -o loop qemu-armel-*TAB*
and your terminal will automatically fill in your filename. Awesome linux, huh? =)
)
Code:
#cd /mnt/etc/
#mv fstab fstab.bak
#echo "proc /proc proc defaults 0 0" > fstab
#echo "dev /dev tmpfs rw 0 0" >> fstab
Note that the first time we create a file called fstab (echo asdf > fstab), then we add one line to this file (echo asdfasdf >> fstab)
Now we need to copy our wifi-driver over. Remember I told you to write down the directory you put them in? =)
Code:
#cp /home/YourUserName/Desktop/FolioStuff/firmware /mnt/lib/firmware
We will now do something stupid: We chroot into our arm-based system from an intel-system. But since we're only changing passwords, we should be OK.
Code:
#cd /
#chroot /mnt/
#passwd myCoolUserName
#passwd
#exit
That's it, we're out of the chroot.
It's now time to prepare the SDcard (The steps are the same for a USB Flash drive, I think you'll figure them out.)
Find out how your SDcard can be accessed (You should still be root):
Code:
# fdisk -l
In my card reader, it's "/dev/mmcblk0", it could also be "/dev/sdb1" in your computer.
Now there are two possibilities:
1. You know what youre doing. Then it's easy: You wipe the only partition (or, if there are more than one, the first partition) on your sdcard and format it with ext3:
Code:
#mkfs.ext3 /dev/mmcblk0p1
Note: The device is called /dev/mmcblk0, the partition itself /dev/mmcblk0p1 (Partition 1)
2. You are not sure about this. No problem, start gparted: (as root!)
Code:
#gparted
In the upper right corner, select your flash drive, delete all partitions and create one formatted with ext3. Close gparted.
Mount your freshly created partition somewhere (i chose /mnt2/):
Code:
#mkdir /mnt2/
Code:
#mount /dev/mmcblk0p1 /mnt2
We can now copy our filesystem over. Make sure you use exactly the same flags (rfp for recursive, force, preserve (attributes))
Code:
#cp -rfp /mnt/* /mnt2/
OK, that could work. Unmount the sdcard:
Code:
#umount /mnt2/
Put it in your folio and cross your fingers.
Wifi drivers will be up soon...
It's recommend to add build-essentials to your rootstock image too..
Because then you can easily build the wireless lan drivers on your devices..
Maybe I'll post a howto this afternoon!
Is this Ubuntu really usable (for daily work) with the folio 100 (touch, response speed, ecc.)?
Thanks.
Yup, it's usable for everyday work. It's quite fast on the Folio 100, I've been pretty impressed when I tested it a few weeks ago.
Thanks ph84
It seems most difficult than expected but, great job !
Only i have 1 question, bricking the tablet sounds dangerous... is possible break out the tablet and get a rock?
Thanksss!!!!!
if ubuntu is installed on sd, does that mean that we can dual boot foliomod from nand and ubuntu from sd/usb?
Hm... I'm using Ubuntu 11.04 and I'm getting this error at the end of the rootfs creation :
E: Sub-process /usr/bin/dpkg returned an error code (1)
E: Second stage build in chroot failed !
E: Please see the log to see what went wrong.
I: Cleaning up...
.....
I: Umounting temporary Image
umount2: Dispositivo o risorsa occupata
umount: /tmp/tmp.zaZ1j1Tgt6/tmpmount/proc: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
umount2: Dispositivo o risorsa occupata
Click to expand...
Click to collapse
Do you have any idea where I can find the log?
And this procedure will build in the tablet a dual boot? Or dualboot is another procedure?
what is the *.rar????
No it's for singleboot only...
You can only start Ubuntu installed on SD-Card/USB-Stick with this procedure...
I don't know wether the boot-partition is locked when you are booting ubuntu/android..
If not it should be possible to build some applications to flash the boot-partition on the running system to change from ubuntu to android
When I do the rootstock step,I got this error!!!Please help!!!
I: Base system installed successfully.
I: First stage install done
I: Using Chroot for installer
Adding 'local diversion of /usr/sbin/invoke-rc.d to /usr/sbin/invoke-rc.d.rootstock'
Generating locales...
en_GB.UTF-8... done
Generation complete.
Generating locales...
en_US.UTF-8... done
Generation complete.
/bin/installer: line 53: syntax error near unexpected token `+'
E: Second stage build in chroot failed !
E: Please see the log to see what went wrong.
I: Cleaning up...
.....
I: Umounting temporary Image
I: A logfile was saved as //rootstock-201104140706.log
I: Done
Click to expand...
Click to collapse
Could you upload an *.img for us in this forum?
or a databank,etc?
mhmm it always hangs in the xulrunner configuration.. bahh someone know a solution for this? or does i realy have to chroot the rootfst and install everything manualy =(? Cant find any solution on google for this bug =/
sony_tornado said:
what is the *.rar????
Click to expand...
Click to collapse
Nvm, I was talking crap...
schnudergof said:
mhmm it always hangs in the xulrunner configuration.. bahh someone know a solution for this? or does i realy have to chroot the rootfst and install everything manualy =(? Cant find any solution on google for this bug =/
Click to expand...
Click to collapse
Just try rootstock without the parameters on --seed..
Maybe it will work..
You wont have a Desktop Enviroment like Gnome or something but you wont need that for installing the wireless drivers...
And after installing wireless drivers you can install ubuntu-desktop or something with apt-get!
Ok, I have been looking at rootstock, and if you install rootstock-gtk and than click on tasksel there is a whole list of seeds to chose from. I Think im going to try build the netbook build.
On a side note:
We will now do something stupid: We chroot into our arm-based system from an intel-system. But since we're only changing passwords, we should be OK
Click to expand...
Click to collapse
with chroot your only changing the root of your file system, your not running anything from there.
But its its in no way a complaint to your awesome guide! Thanks and keep up the good work!
shidima_101 said:
with chroot your only changing the root of your file system, your not running anything from there.
Click to expand...
Click to collapse
Thats right but when you change your root shell to the rootstock-fs you can also use sudo apt-get update/install and install it into the rootfs!
ph84 said:
Meanwhile, open another terminal. (This is linux! We're gonna multitask since our computer is capable of handling that!) Go to where you stored the attached files, for example
Code:
#cd /home/YourUserName/Desktop/FolioStuff
and unpack them:
Code:
#rar x *.rar
Click to expand...
Click to collapse
Where/what is the "attached files"?
Thanks
Just go to the first page, press STRG+F and type attached into the search window...
I hope you will find the attached files.. Else you dont have to try installing ubuntu on your folio >_<
°EraZoR° said:
Just go to the first page, press STRG+F and type attached into the search window...
I hope you will find the attached files.. Else you dont have to try installing ubuntu on your folio >_<
Click to expand...
Click to collapse
The files I found are only *.zip for update bootloader. Where is *.rar file?
Thanks
Ok I have been searching for the latest answers to the problem and Im not Linux techy , but I been rooting for a while now and recently did everything right, download the zip file, nandroid back up, vr super wipe, flash zip file, and reboot. Didnt like the ROM, into recovery i went, vr super wipe, backup and restore, nandroid restore.... then got the oops something went wrong! check recovery log! I dont know how to read the reovery log. can anyone help; so my naggin woman can stop buggin me that i cant get the files to restore. its there but not restoring. Here is the recovery log:
Starting recovery on Sat Oct 29 19:45:22 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
Build : RA-supersonic-v2.2.1
I:Set boot command "boot-recovery"
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.config.ringtone=Windchimer.mp3
ro.config.notification_sound=Little.mp3
ro.build.id=ERE27
ro.build.display.id=1.32.651.1
ro.build.version.incremental=171253
ro.build.version.sdk=7
ro.build.version.codename=REL
ro.build.version.release=2.1-update1
ro.build.date=Wed Apr 28 21:39:52 CST 2010
ro.build.date.utc=1272461992
ro.build.type=userdebug
ro.build.user=lala-01
ro.build.host=lala-01-desktop
ro.build.tags=test-keys
ro.product.model=PC36100
ro.product.brand=sprint
ro.product.name=htc_supersonic
ro.product.device=supersonic
ro.product.board=supersonic
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=qsd8k
ro.build.product=supersonic
ro.build.description=1.32.651.1 CL171253 test-keys
ro.build.changelist=171253
ro.product.ua=
ro.build.fingerprint=sprint/htc_supersonic/supersonic/supersonic:2.1-update1/ERE27/171253:userdebug/test-keys
ro.product.version=1.32.651.1
keyguard.no_require_sim=1
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.def.preferred.network=4
ro.telephony.default_network=4
wifi.interface=eth0
wifi.supplicant_scan_interval=15
ro.com.android.dataroaming=true
ro.com.google.locationfeatures=1
ro.sf.lcd_density=240
ro.com.google.clientidbase=android-sprint-us
persist.service.mount.playsnd=0
ro.ril.def.agps.mode=2
settings.display.autobacklight=1
settings.display.brightness=143
dalvik.vm.heapsize=24m
ro.media.enc.file.format=3gp,mp4
ro.media.enc.vid.codec=m4v,h263
ro.media.enc.vid.h263.width=176,1280
ro.media.enc.vid.h263.height=144,720
ro.media.enc.vid.h263.bps=64000,6000000
ro.media.enc.vid.h263.fps=1,30
ro.media.enc.vid.m4v.width=176,1280
ro.media.enc.vid.m4v.height=144,720
ro.media.enc.vid.m4v.bps=64000,6000000
ro.media.enc.vid.m4v.fps=1,30
ro.media.dec.jpeg.memcap=20000000
ro.bt.chipset=Broadcom BCM4329-B1
ro.bt.version=Bluetooth 2.1 + EDR
ro.bt.stack=Broadcom BTL-A
ro.bt.stack.version=2.0.47.005
ro.bt.profiles=4270339
ro.cdma.home.operator.numeric=310120
ro.cdma.home.operator.alpha=Sprint
gsm.sim.operator.numeric=0
gsm.sim.operator.alpha=0
gsm.sim.operator.iso-country=0
ro.config.alarm_alert=Light.mp3
ro.config.cal_notification=Vector.mp3
ro.config.msg_notification=Ascend.mp3
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=2.1_r3
media.a1026.nsForVoiceRec=0
htc.audio.alt.enable=1
htc.audio.hac.enable=1
net.bt.name=Android
net.change=net.bt.name
ro.config.sync=yes
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.modversion=RA-supersonic-v2.2.1
ro.factorytest=0
ro.serialno=HT0CFHL14956
ro.bootmode=recovery
ro.baseband=2.15.00.11.19
ro.carrier=COMMON
ro.bootloader=2.10.0001
ro.hardware=supersonic
ro.revision=3
ro.cid=SPCS_001
init.svc.recovery=running
init.svc.adbd=running
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
Restore BCDS-20111025-0514 ?
Press Power to confirm,
any other key to abort.
Restoring : .
nandroid-mobile v2.2.1
Searching for backup directories, matching BCDS-20111025-0514, to delete or restore
or compress
Looking for the latest backup, will display other choices!
Default backup is the latest: /sdcard/nandroid/HT0CFHL14956/BCDS-20111025-0514
Other available backups are:
Using G1 keyboard, enter a unique name substring to change it and <CR>
or just <CR> to accept: Accepting default.
Restore path: /sdcard/nandroid/HT0CFHL14956/BCDS-20111025-0514
...Verifying backup images...
.................................................................................................................................................boot.img: OK
cache.img: OK
data.img: OK
system.img: FAILED
md5sum: WARNING: 1 of 4 computed checksums did NOT match
Error: md5sum mismatch, aborting
Oops... something went wrong!
Please check the recovery log!
I:Set boot command ""
Restore Google proprietary system files?
Press Power to confirm,
any other key to abort.
Performing restore : .
Restore complete!
I:Set boot command ""
I:Set boot command ""
E:Couldn't open directory /sdcard/nandroid/RSA-PR-I:Set boot command ""
I:Set boot command ""
E:No nandroid-backup files found
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
Fix package uid mismatches
Press Power to confirm,
any other key to abort.
Fixing package uid mismatches : ./sbin/fix_permissions 2.03 started at 10-29-2011 19:49:36
cat: can't open '/data/system/packages.xml': No such file or directory
cat: can't open '/data/system/packages.xml': No such file or directory
/sbin/fix_permissions 2.03 ended at 10-29-2011 19:49:36 (Runtime:0m0s)
Uid mismatches fixed!
I:Set boot command ""
Move recovery.log to SD
Press Power to confirm,
any other key to abort.
Moving : .unmounting /system
unmounting /sdcard
unmounting /data
Any help would be appreciated!
Obviously there is an error with the system.img. First of all, did you check to see if it is there?
yes the file is there, I even took the file off the 16gb sd card and put it on her spare 8gb sd card, after i formatted it, then tried to restore it. No luck got error again. I'm starting to feel its a loss, she asked me if i could restore it on my evo 3d, lol I dont think so, I guess in hoping to get important information off there. I'm doing what I can to learn as this is part of my future degree Im pursuing in mobile development
MWaV said:
yes the file is there, I even took the file off the 16gb sd card and put it on her spare 8gb sd card, after i formatted it, then tried to restore it. No luck got error again. I'm starting to feel its a loss, she asked me if i could restore it on my evo 3d, lol I dont think so, I guess in hoping to get important information off there. I'm doing what I can to learn as this is part of my future degree Im pursuing in mobile development
Click to expand...
Click to collapse
Sometimes an error with the system.img isn't really critical (although it sounds like it is). It could be the md5sum which caused it not to restore (judging by the log, it is). Have you checked them to see if they match?
If you dont mind could you please explain how can I check to see if they match?
MWaV said:
If you dont mind could you please explain how can I check to see if they match?
Click to expand...
Click to collapse
The easiest way would be to go back to where you downloaded the rom from and check if the md5sum was placed there (Many times devs place the md5sum next to the rom download or somewhere in their post). If you see it, check the one generated in the nandroid to see if they are the same.
ok will try and let you know what I find out. Thanks!!
this is where I got the download from: http://downloadandroidrom.com/file/HTCEvo3D/roms/MIUIROM
MWaV said:
this is where I got the download from: http://downloadandroidrom.com/file/HTCEvo3D/roms/MIUIROM
Click to expand...
Click to collapse
Perfect. The md5sum is there, so now you just have to check the generated one to see if they match.
I wound up giving this error up with my lady 's phone as you know women can be very impatient in as we call it experimental stages. She just wanted it back and I eventually sent in bcak to before and redid every thing and this time took everything off her sd card ran check disk and repaired some issues with the file on the computer and then swapped sd cards and seemed to wrk fine from there, thanks for your time and having me recheck the that info because it helped out alot which i made sure I looked for this time.
Hi guys,
I used CWM to backup my AT&T 4.5.141 stock ROM.
I installed a few custom ROMs and now decided to go back to stock.
When I try to restore the stock ROM, I get the error 'Error while restoring /system!'.
The recovery.log:
Code:
Starting recovery on Wed Aug 14 20:15:44 2013
framebuffer: fd 4 (540 x 960)
ClockworkMod Recovery v5.0.2.0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/mmcblk0p11 (null)
2 /cache ext3 /dev/block/mmcblk0p15 (null)
3 /data ext3 /dev/block/mmcblk0p16 (null)
4 /sdcard vfat /dev/block/mmcblk1p1 (null)
5 /emmc vfat /dev/block/mmcblk0p18 (null)
6 /system ext3 /dev/block/mmcblk0p12 (null)
7 /recovery emmc /dev/block/mmcblk0p10 (null)
8 /osh ext3 /dev/block/mmcblk0p13 (null)
9 /preinstall ext3 /dev/block/mmcblk0p17 (null)
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GINGERBREAD
ro.build.display.id=generic_olympus-eng 2.3.5 GINGERBREAD eng.koush.20110905.113
702 test-keys
ro.build.version.incremental=eng.koush.20110905.113702
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Mon Sep 5 11:37:24 PDT 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=test-keys
ro.product.model=MB860
ro.product.brand=generic
ro.product.name=generic_olympus
ro.product.device=olympus
ro.product.board=olympus
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=olympus
ro.build.description=generic_olympus-eng 2.3.5 GINGERBREAD eng.koush.20110905.11
3702 test-keys
ro.build.fingerprint=generic/generic_olympus/olympus:2.3.5/GINGERBREAD/eng.koush
.20110905.113702:eng/test-keys
ro.sf.lcd_density=240
dalvik.vm.heapsize=42m
rild.libpath=/system/lib/libmoto_ril.so
persist.ril.mux.noofchannels=9
persist.ril.mux.ttydevice=/dev/ttyHS3
ro.telephony.call_ring.multiple=false
persist.ril.modem.ttydevice=/dev/ttySPI0
persist.ril.modem.mode=2
persist.ril.features=0x24
persist.ril.mux.retries=500
persist.ril.mux.sleep=2
ro.kernel.android.ril=yes
persist.ril.pppd.start.fail.max=16
mobiledata.interfaces=ppp0
ro.telephony.default_network=3
ro.additionalmounts=/mnt/emmc
ro.usb.use_custom_service=1
wifi.supplicant_scan_interval=60
ro.wifi-ap.fw-path=/system/etc/wl/sdio-g-cdc-roml-reclaim-wme-apsta-idauth-minio
ctl.bin
ro.bt.bdaddr_path=/pds/bt/bt_bdaddr
ro.product.use_charge_counter=1
ro.opengles.version=131072
ro.cwm.forbid_format=/misc,/radio,/pds,/bootloader,/recovery,/efs
ro.battery_light=true
ro.vold.switchablepair=/mnt/sdcard,/mnt/emmc
keyguard.no_require_sim=true
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=TA2070LZG5
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=olympus
ro.revision=33776
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
SD Card marker not found...
Checking Internal SD Card marker...
45934351c58d252bdc39bf625201e0dc
45934351c58d252bdc39bf625201e0dc
I:Running script:
I:
run_program("/sbin/cp", "-R", "/cache/recovery", "/tmp/recovery");
ui_print("ROM Manager Version 5.5.3.0");
ui_print("August 14, 2013");
assert(restore_rom("/sdcard/clockworkmod/backup/2013-05-18.17.48.49", "boot", "s
ystem", "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.0
August 14, 2013
Checking MD5 sums...
boot.img: OK
cache.ext3.tar: OK
data.ext3.tar: OK
recovery.img: OK
system.ext3.tar: OK
.android_secure.vfat.tar: OK
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/2013-05-18.17.48.49/system.e
xt3.tar
Restoring system...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p12: 11/81920 files (0.0% non-contiguous), 20633/327680 blocks
default.prophciconfigdrm1_func_testrun_restorebackupdexdumprun_backuphcitooll2pi
ngatt_power_opt.oggDock.oggKeypressStandard.oggKeypressReturn.oggVideoRecord.ogg
KeypressDelete.oggLock.oggKeypressSpacebar.oggEffect_Tick.oggUnlock.oggLowBatter
y.oggUndock.oggcamera_click.oggBells.oggWooden_Percussion_alert.oggGlam_alert.og
gDark_Alley_alert.oggPure_Tone_alert.oggGrass_Meadow_alert.oggChrome_Alert.oggHe
y_Hey.oggKinetic_Bell.oggUrget_alert.oggAlarm_Beep_01.oggAlarm_Classic.oggAlarm_
Beep_02.oggAlarm_Buzzer.oggAlarm_Beep_03.oggAlarm_Rooster_02.oggUrgent.oggRock_S
tar.oggRings.oggStandard.oggChrome_Ring.oggMagenta.oggDramatic_Piano.oggOrganic.
oggDrum_Roll.oggPure_Tone.oggATT_Tone.oggGrass_Meadow.oggDark_Alley.oggGlam.oggR
isk.oggClear_Sky.oggbootanimation.zipbuild.propDeviceStatistics.odexblur_email.a
pkMessaging.odexCertInstaller.odexSetupSettings.apkblur_linkedin.apkVpnServices.
odexFastDormancy.apkPicoTts.apkApplicationsProvider.apkWapPushSI.apkBlurEmailEng
ine.apkBlurCalendar.odexMagicSmokeWallpapers.odexPortalApp.odexBlurCalendar.apkF
ileManager.odexDataCollectorProvider.apkGlobalUnplug.apkArcVideoEditorLite.odexF
akeBlurXmppApp.odexTelephonyProvider.odexBlurMusic.apkblur_photobucket.odexQuick
office.apkSocialShare.odexHTMLViewer.apkSuggestionsProvider.odexSetupProvider.ap
kGlobalUnplug.odexDock.apkGoogleServicesFramework.apkblur-services.odexDataColle
ctorService.apkAudioEffectSettings.odexStatusWidget.odexContactsProvider2_0.odex
PerformanceManager.odexMotorolaSettingsProvider.apkPackageInstaller.odexDataColl
ection.apkMediaUploader.apkBlurContacts.apkVpnClient.apkBlurTasks.apkentitlement
service.odexMarketUpdater.odexCertificateManager.odexRichLocation.odexblur_twitt
er.apkBrowser.odexProtips.apkVending.apkblur_lastfm.odexContactsData.odexBlurEma
ilEngine.odexTalk2.apkDefaultContainerService.odexCarDock.apkBlurDialer.odexAtCm
d.apkOverlaySettingsProvider.apkVpnServices.apkCarDock.odexBlurAlarmClock.odexMe
diaProvider.apkQuickContactWidget.odexVSuiteApp.odexMessagesWidget.odexFlashPlay
er.apkLocationProxyDmPlugin.odexExtDispService.apkSwype.apkOMAProvisioning.odexG
oogleServicesFramework.odexTtsService.apkMagicSmokeWallpapers.apkFastDormancy.od
exClockWidget.odexOMAProvisioning.apkHTMLViewer.odexCertificateProvider.odexTele
phonyProvider.apkGmail.odexSimManagerATT.odexMediaUploader.odexArcVideoEditorLit
e.apkphoneportal.apkSetup.odexDefaultContainerService.apkAdService.apkDrmProvide
r.odexVoiceReadoutService.odexCalculator.odexMediaProvider.odexYouTube.odexCompa
ssCalibrate.odexBlurChooser.odexBlurContactsSync.apkLiveWallpapersPicker.odexAcc
ountAndSyncSettings.odexSimManagerATT.apkblur_youtube.apkSimContactAdapter.odexT
erm.apkPreloaded.odexZoomService.apkBlurContactsSync.odexLiveWallpapers.odexBlur
Phone.apkNewsWidget.apkDlnaSystemService.apkFingerprintSensor.odexGoogleQuickSea
rchBox.odexSpellingCheckService.apkMediaCenter.apkToggleWidgets.apkAtCmd.odexDev
iceStatistics.apkDataCollectorProvider.odexEncryptionSettings.apkBlurUpdater.ode
xAdminFeedNotifier.odexBlurCamera.apkblur_orkut.apkDockService.apkblur_myspace.o
dexMotoPhonePortal.apkOverlaySettingsProvider.odexPolicyMgrService.apkPortalApp.
apkGoogleBackupTransport.apkForestWallpaper.apkZoomService.odexDownloadProviderU
i.apkBlurCamera.odexSettings.apkblur_picasa.odexGoogleContactsSyncAdapter.apkWor
ldClockWidget.apkBlurContacts.odexBlurEmail.odexblur_youtube.odexContactsProvide
r2_0.apkModemCutback.odexStk.apkLiveWallpapers.apkHomeSyncWizard.apkBlurPhone.od
exAdService.odexForestWallpaper.odexFakeBlurXmppApp.apkPhotoWidget.odexDownloadP
roviderUi.odexPolicyMgrProvider.apkDock.odexMediaCenter.odexDataCollection.odexb
lur_orkut.odexSimContactAdapter.apkFriendFeed.odexCalculator.apkBlurSNMessagingE
ngine.apkMasterClearErrorReport.apkQuickSms.apkBluetooth.apkblur_activesync.odex
blur_email.odexblur_flickr.apkBlurCalendarProvider.apkKpiLogger.apkEncryptionSet
tings.odexSystemUI.odexUpgrader.apkDLNA.odexGfxEngine.odexVideoPlayer.odexphonep
ortal.odexVlingo.apkPolicyMgrProvider.odexSetup.apkGooglePartnerSetup.apkVSuiteA
pp.apkYahooContacts.odexYahooContacts.apkCompassCalibrate.apkRichTextCommon.odex
Protips.odexClockWidget.apkWebtopSession.apkblur_yahoo.apkFingerprintSensor.apkC
onversations.odexMSExchangeService.apkPhotoEditor.odexMotoPhonePortal.odexSoundR
ecorder.odexBatteryReport.apkBlurTasks.odexMasterClearErrorReport.odexblur_linke
din.odexBatteryManager.apkWorkContacts.apkAttDrmContent.apkMarketUpdater.apkMoto
AtCmdQcPlugin.apkBooksPhone.odexGooglePartnerSetup.odexBlurHome.apkGenieWidget.o
dexMSExchangeService.odexPNI-Moto.apkStatusWidget.apkMotorolaSettingsProvider.od
exPerformanceManager.apkAccountAndSyncSettings.apkCertificateProvider.apkMessage
sWidget.apkMessaging.apkFota.apkMaps.apkblur_myspace.apkblur_activesync.apkUserD
ictionaryProvider.odexDataCollectorService.odexHelpCenter.apkblur_skyrock.apkVis
ualizationWallpapers.apkBluetooth.odexFriendFeed.apkCalendarSync.odexSpellingChe
ckService.odexSuggestionsProvider.apkDatamanagerApp.apkSetupWizard.apkInPocketSe
rvice.apkblur_facebook.odexVending.odexQuickSms.odexOMADownload.apkLocationProxy
DmPlugin.apkGoogleQuickSearchBox.apkExtDispService.odexblur_skyrock.odexTalk2.od
exPhotoWidget.apkMaps.odexMediaSync.odexSoundRecorder.apkWorldClockWidget.odexFo
ta.odexStickyNoteWidget.odexDMService.odexNetworkLocation.apkblur_photobucket.ap
kIndexingService.odexConversations.apkPhoneAddons.apkGoogleFeedback.odexBlurGall
ery.apkNewsWidget.odexVpnClient.odexSystemUI.apkToggleWidgets.odexGoogleFeedback
.apkUpgrader.odexStorageMonitorService.apkDataManagerService.odexNetworkLocation
.odexCertInstaller.apkBatteryReport.odexTtsService.odexWorkContacts.odexMotoAtCm
dPlugin.apkblur_yahoo.odexBookmarksWidget.odexInPocketService.odexUniversalInbox
.apkblur_facebook.apkBlurChooser.apkQuickContactWidget.apkPreloaded.apkMediaSync
.apkSetupWizard.odexSocialMessaging.odexVoiceSearch.odexAudioEffectSettings.apkB
lurSNMessagingEngine.odexAdminFeedNotifier.apkBlurUpdater.apkChargeOnlyMode.apkY
ouTube.apkVideoPlayer.apkSettings.odexUsb.odexTerm.odexVisualizationWallpapers.o
dexLatinIME.apkChargeOnlyMode.odexGenieWidget.apkDlnaSystemService.odexDownloadP
rovider.odexStreet.apkBlurHome.odexKpiLogger.odexBlurEmail.apkPicoTts.odexQuickT
utorial.apkWeatherWidget.apkVoiceReadoutService.apkStorageMonitorService.odexApp
licationsProvider.odexSocialMessaging.apkBlurMusic.odexMotoAtCmdPlugin.odexIndex
ingService.apkBooksPhone.apkPolicyMgrService.odexLatinIME.odexPhoneAddons.odexBl
urCalendarProvider.odexFileManager.apkWeatherWidget.odexBlurDialer.apkblur_lastf
m.apkGoogleBackupTransport.odexPhotoEditor.apkPackageInstaller.apkMotoAtCmdQcPlu
gin.odexCertificateManager.apkMotHstcmd.apkCalendarSync.apkDownloadProvider.apkD
LNA.apkGmail.apkUserDictionaryProvider.apkModemCutback.apkBrowser.apkDrmProvider
.apkGfxEngine.apkRichLocation.apkDatamanagerApp.odexQuickoffice.odexDockService.
odexHomeSyncWizard.odexSetupSettings.odexSocialShare.apkMotHstcmd.odexBookmarksW
idget.apkblur_twitter.odexblur-services.apkDMService.apkUniversalInbox.odexUsb.a
pkBluetoothMot.apkBlurGallery.odexentitlementservice.apkBluetoothMot.odexStreet.
odexLiveWallpapersPicker.apkVoiceSearch.apkBatteryManager.odexVlingo.odexWapPush
SI.odexSetupProvider.odexAttDrmContent.odexQuickTutorial.odexBlurAlarmClock.apkO
MADownload.odexHelpCenter.odexblur_picasa.apkblur_flickr.odexRichTextCommon.apkW
ebtopSession.odexContactsData.apkGoogleCalendarSyncAdapter.apkStk.odexStickyNote
Widget.apkDataManagerService.apkSuperuser.apkDroidSansArabic.ttfHandsetCond-Bold
.ttfDroidSansMono.ttfDroidSans.ttfClockopia.ttfDroidSerif-BoldItalic.ttfDroidSer
if-Bold.ttfDroidSansThai.ttfDroidSansHebrew.ttfDroidSansFallback.ttfHandsetCond.
ttfDroidSerif-Regular.ttfDroidSans-Bold.ttfDroidSerif-Italic.ttflsmkdirdumpe2fsn
dcmotoboxrun-asbatchnetcfgsleepapplypatchrildfsck_msdosroutesmdchownformatmount_
ext3.shmountamsystem_serverdumpstatenvmm_mpeg4dec.axftune2fsload_pia.sham2server
touchpadresize2fsservicenvmm_service.axfbugtogo.shbmgrnvmm_vc1dec.axfnvrm_daemon
masterclearbluetoothdnvmm_wmaprodec.axfschedtestpingnvmm_wavdec.axftundcharge_on
ly_moderemountpdsnvmm_mp3dec.axfinstalldsurfaceflingeraes1750detecttestsdptoolnv
mm_aacdec.axfnvddk_audiofx_core.axfshlogcatnv_hciattachnvmm_sw_mp3dec.axfinsmodt
opdbus-daemonioniceencryption_testnvmm_mp2dec.axfhciattachlsofdexoptgkilogdmd5su
mpmsetpropnvmm_audiomixer.axfbugreportkeystorenvmm_adtsdec.axfifconfigaes1750tes
tdundlnbrcm_patchram_plusapp_processdateinputloggzipdfomx_testsnandreadfbreadnew
fs_msdosvmstattstmetainfomvuptimeHostapdimemediaserverdebuggerdrebootdbvc_atvc_p
roperty_setiftoprmdirnvmm_wmadec.axfipnvmm_sorensondec.axfumountdvztestap_gain.b
innvmm_jpegdec.axfnvddk_audiofx_transport.axfmountoshlogwrappernvrm_avp.axfprint
env[mdm_panicdtdctestpppdstopsecclkdbt_initgetpropservicemanagerwhisperdwatchpro
pspppdsendeventakmd2tuncfgstart_enc_mgt_tool.shnvmm_jpegenc.axfwipedmesgiptables
ddkillap_gain_mmul.binlsmodrmmodgeteventtegrastatscatnetdioctlpsftmipcde2fsckbt_
test_exectcmdmount_pia.shstartcmpsetconsolepppd-riltty2ttydloadpreinstalls.shwpa
_supplicantchmoddumpsysbattddhcpcdenc_mgt_toolnotifybootanimationvoldnvmm_manage
r.axfnvmm_reference.axfmonkeytcnapics.shsdcardptfcpsyncmot_boot_modemtpdnvmm_h26
4dec.axffdiskdalvikvmmke2fsaudio_ecns_param.binrmdlnasrvdnsmasqmemtest_modeidhdv
pnclientpmschedtoptcmdhelpvdcchat-rilracoonlinkerrenicebt_downloadertoolboxdmtne
tstatusbdaes1750selftestpandcheck_sdc.shsvcsubouncycastle.odexcore.odexext.odexc
om.motorola.app.admin.jarcom.scalado.caps.jarinput.odexpm.jaram.odexjcifs-krb5-1
.3.12.jarpm.odexcom.motorola.android.mime.jarcom.blockbuster.lib.moto.jarime.ode
xservices.jarguava.jarandroid.test.runner.odexdmt.odexcore-junit.odexcom.motorol
a.atcmd.base.odexcore.jarcom.motorola.tiltscroll.odexbmgr.jarservices.odexsvc.ja
rcom.motorola.android.dlna.jarmonkey.jarbouncycastle.jarsqlite-jdbc.jarmonkey.od
exblur-res.apkbmgr.odexcom.motorola.android.drm1.jarandroid.test.runner.jarframe
work.jarandroid.policy.odexjavax.obex.jarmoto-res.apkcom.motorola.atcmd.base.jar
am.jarjcifs-krb5-1.3.12.odexext.jarandroid.policy.jardmt.jarsvc.odexcom.nvidia.d
isplay.odexjavax.obex.odexguava.odexframework.odexcom.google.android.maps.jarfra
mework-res.apkinput.jarcom.motorola.tiltscroll.jarcom.nvidia.display.jarcore-jun
it.jarcom.motorola.app.admin.odexsqlite-jdbc.odexime.jarcpcap-key.klevfwd.klAVRC
P.klqwerty.kltegra-kbc.klusb_keyboard_102_en_us.klenroll.okcmu6plus.ok.zipbasic.
okboolean.g2gphone_type_choice.g2gVoiceDialer.g2gen-US-ttp.databaseline8k.pargen
eric11.ldageneric11_m.swimdlgeneric8.ldageneric8_f.swimdlgeneric11_f.swimdlgener
ic.swiarbgeneric8_m.swimdlbaseline.parbaseline11k.parzoneinfo.datzoneinfo.idxzon
einfo.versionRFFstd_501.bmdRFFspeed_501.bmdicudt44l.datevfwd.kcm.binqwerty2.kcm.
binqwerty.kcm.bintegra-kbc.kcm.binpreinstalllibsurfaceflinger_client.soaudio.soi
nput.solibhardware.solibsoundpool.solibjni_pinyinime.solibnvodm_query.solibdbus.
solibmtp_jni.sovpnclient.kolibmot_atcmd.solibstagefright_avc_common.soliblog.sol
ibreference-ril.solibmot_atcmd_mflex.solibnvrm_graphics.solibogg.sodummy.kolibex
t2_profile.solibcrypto.solibkpilogger.solibdmjavaplugin.solibsystem_server.solib
mot_bthid_jni.solibhwmediarecorder.solibstagefright.solibrtp_jni.solibmediaplaye
rservice.solibandroid.solibsqlite.solibnvmm_videorenderer.solibopencore_mp4local
.sogps.olympus.sosensors.olympus.sogralloc.tegra.sooverlay.tegra.sogralloc.defau
lt.solights.tegra.solibjanus.solibdlnasysjni.solibGLESv2_tegra.solibGLES_android
.solibGLESv1_CM_tegra.soegl.cfglibEGL_tegra.solibext2_uuid.solibnmea.solibbcbmsg
.solibcgdrv.solibjni_latinime.solibnvwinsys.solibspellingcheckengine.solibcutils
.solibaudio.solibnvwsi.solibext2fs.solibEGL.solibjpeg.solibopencore_player.solib
arcsoft.solibpagemap.solibipsec.solibAuthUDMDrv_1750A100.solibsysutils.solibaudi
opolicy.solibnvodm_misc.solibSR_AudioIn.solibicuuc.solibGLESv2.solibrs_jni.solib
webcore.solibnvmm_audio.solibimage_jni.solibnvrm_channel.solibscalado.solibnativ
edrm1.solibnvmm_manager.solibcfaplugin_mc.solibexempi.solibssl.solibmotdrm1.soli
bomx_sharedlibrary.solibtalk_jni.solibcapsjava.solibOpenSLES.solibnvmm_writer.so
liblibcfaB-1.5.7-GO1.solibGLESv1_CM.solibbattd.solibext2_e2p.solibRS.solibwhash.
solibhostapd_client.solibext2_com_err.solibdl.solibnvomxilclient.solibmedia.soli
bnvmm_utils.solibcamera.solibvideoeditorlite.solibbluedroid.solibprojectM.solibh
dmi.solibc.solibdmengine.solibam2app.solibvsuite_mot_vs32_cmb103.solibETC1.solib
ctest.solibopencore_rtsp.solibnvodm_dtvtuner.solibdlnaprofileparser.solibnetlink
.solibicui18n.solibmot_bluetooth_jni.solibSwypeCore.solibopencore_download.solib
nvmm.solibui.solibSpeexJNI.solibbluetooth.solibphotoflow.solibkbdict.solibpanora
ma_jni.solibtpa.solibvisualizer.solibreverbwrapper.solibbundlewrapper.solibnvsm.
solibandroid_runtime.solibnvddk_aes_user.solibtpa_core.solibvoicesearch.solibsta
gefright_enc_common.solibstagefright_foundation.solibgui.soliba2dp.solibspeex.so
libexpat.solibnvodm_imager.solibopencore_rtspreg.solibnvmm_video.solibmot_btpan_
jni.solibsurfaceflinger.solibsonivox.solibmotodbgutils.solibttssynthproxy.solibn
fc_ndef.solibcfa-1.5.7-GO1.solibnvmm_image.solibui3d.solibnvmm_camera.solibsenso
rservice.solibjni_nwp.solibmoto_netutil.solibam2server.solibnvmm_vp6_video.solib
opencore_downloadreg.solibnvidia_display_jni.solibstagefrighthw.solibnativehelpe
r.solibandroid_servers.solibhwmediaplugin.solibopencore_common.solibmot_led.soli
bnvmm_parser.sodhd.kolibpppd_plugin.solibsensory.solibmtpstack.solibpkip.solibut
ils.solibnvomx.solibFFTEm.solibstlport.solibdrm1_jni.solibopencore_author.solibs
ensortest.solibskiagl.solibprovlib.solibnvec.solibwbxmlparser.solibthread_db.sol
ibdlnahttpjni.solibvpnclient_jni.solibopencore_mp4localreg.solibstdc++.solibnvmm
_contentpipe.solibrds_util.solibdiskconfig.solibextdisp.solibskia.solibz.solibnv
mm_service.solibeffects.solibpppd_plugin-ril.solibnvddk_audiofx.solibacc.solibca
meraservice.solibmoto_ril.solibxmpcore.solibnetutils.solibpixelflinger.solibmedi
a_jni.solibbinder.solibmediaext.solibsrec_jni.solibvorbisidec.solibaudioeffect_j
ni.solibreference-cdma-sms.solibttspico.solibjnigraphics.solibwpa_client.solibPh
otoEditor.solibnvmm_tracklist.solibnvmm_misc.solibnvrm.solibWifiAPHardware.solib
ril.solibdvm.solibnvddk_2d_v2.solibnvdispmgr_d.solibquicksec.solibnvdispatch_hel
per.solibaudioflinger.solibbluetoothd.solibstagefright_omx.solibiprouteutil.soli
bsqlite_jni.solibglwtanijni.solibcamera_client.solibpanorama.solibril_rds.solibo
pencore_net_support.solibnvddk_2d.solibdlnajni.solibXmp_jni.solibm.solibdrm1.sol
ibext2_blkid.solibcfaB-1.5.7-GO1.solibmetainfo.solibcaps.solibysshared.solibflas
hplayer.solibstagefright_honeycomb.solibstagefright_froyo.solibmotdrm1_jni.solib
emoji.solibmirror.solibhardware_legacy.solibexif.solibnvos.solvr_esmx.binlvr_enu
s.binimg_enus.binprm_esmx.binimg_esmx.binstr_enus.binstr_esmx.binprm_enus.binde-
DE_ta.binde-DE_gl0_sg.binfr-FR_nk0_sg.bines-ES_ta.binit-IT_cm0_sg.binit-IT_ta.bi
n
[B][COLOR="Red"]tar: write error: No space left on device[/COLOR][/B]
en-GB_kh0_sg.bines-ES_zl0_sg.binen-US_lh0_sg.binen-US_ta.binfr-FR_ta.binen-GB_ta
.binhostsvsuite_config.xmlhdmiSolDefLg.gifecryptfs.tab12m_files_copy.shlocation.
cfgfmc_init_6450.2.btscom.nvidia.display.xmlcom.google.android.maps.xmlplatform.
xmlhandheld_core_hardware.xmlcom.scalado.caps.xmlcom.motorola.android.tcmd.xmlco
m.blockbuster.lib.moto.xmljcifs-krb5-1.3.12.xmlandroid.hardware.wifi.xmltouchpad
.cfgtouchpad.cfgtouchpad.cfgexcluded-input-devices.xmlapns-conf.xmlgoogle_generi
c_update.txtblacklist.confauto_pairing.confinput.confaudio.confmain.confevent-lo
g-tagshdmiSolDefSm.gifam2server.pubkeymve.inibt_init.configpvplayer.cfgde_DE_fra
mi.affpt_BR.dic
Error while restoring /system!
result was NULL, message is: assert failed: restore_rom("/sdcard/clockworkmod/ba
ckup/2013-05-18.17.48.49", "boot", "system", "data", "cache", "sd-ext")
Is it possible that the system partition doesn't have enough space?
Seems strange because the backup was made from this exact device with same system partition size, am I right?
I'm using the same CWM recovery version that I used when I did the backup.
I tried formatting the \system partition before starting the restore, but still no luck.
Any help would be greatly appreciated!
Thanks!
Unfortunately, it most likely means the system tar file got damaged somehow.
You should be able to recover from this though. Here's what I would do. First connect the phone in USB mode (so that the content of the SD card(s) is visible on the computer). Next, copy system.ext3.tar from the backup dir to the computer (just in case) and then delete it from the phone. Also make a copy of nandroid.md5 and then use a text editor (make sure you use one that understands UNIX line endings) to edit the file (it's just a text file) and delete the "system" line. Then download a fruitcake ZIP of .141 and flash it, and then restore your backup.
ravilov said:
Unfortunately, it most likely means the system tar file got damaged somehow.
You should be able to recover from this though. Here's what I would do. First connect the phone in USB mode (so that the content of the SD card(s) is visible on the computer). Next, copy system.ext3.tar from the backup dir to the computer (just in case) and then delete it from the phone. Also make a copy of nandroid.md5 and then use a text editor (make sure you use one that understands UNIX line endings) to edit the file (it's just a text file) and delete the "system" line. Then download a fruitcake ZIP of .141 and flash it, and then restore your backup.
Click to expand...
Click to collapse
Oops, I used an old backup, my bad!
Thanks anyway!
I get different error with the correct backup - the OP was edited.
Thanks again
This is actually a fairly common error since I've seen a number of people have this exact same issue. Unfortunately I don't know of a fix, or even an explanation why it happens like this...
You could still try the procedure from my last post.
ravilov said:
This is actually a fairly common error since I've seen a number of people have this exact same issue. Unfortunately I don't know of a fix, or even an explanation why it happens like this...
You could still try the procedure from my last post.
Click to expand...
Click to collapse
Thanks, I'll try your procedure.
In this thread, how can I preform the procedure suggested by danilocps87, i.e. creating a flashable zip from the system.ext3.tar file?
Well why don't you ask him that, in that thread that you pointed out?
Let's keep each thread to its own purpose.
ravilov said:
Well why don't you ask him that, in that thread that you pointed out?
Let's keep each thread to its own purpose.
Click to expand...
Click to collapse
ok.
Regarding your procedure - after I flash the fruitcake ZIP of .141, I need to restore my backup without the system.ext3.tar ?
That's the idea.
Or, if you want to be extra safe, you could do advanced restore and then restore partitions one by one.
The idea is that you flash /system from fruitcake and the rest from your backup.
ravilov said:
That's the idea.
Or, if you want to be extra safe, you could do advanced restore and then restore partitions one by one.
The idea is that you flash /system from fruitcake and the rest from your backup.
Click to expand...
Click to collapse
But, I need the system from my backup, because I had Russian in system languages (locale) and the fruitcake doesn't have Russian option available.
Is there a AT&T 4.5.141 stock ROM that has Russian support?
Thanks!
I figured you'd rather have at least some sort of system than one you cannot restore. Something is better than nothing. Or not?
Anyway, I don't know what all fruitcakes are available. You'll have to research that yourself. This was just an idea.
Hello all. After bricking my Xperia tablet S by the next method: rooted it, then install a soft called as I remember PLay help, or something like that, a soft that helped you make your device look like any other in Google play sao you can install all apps even if they aren't made for your device. everything was ok but when i restarted my tablet it wouldnt pass the sony logo and than black screen.
So I tryed all methods provided within this forum, but nothing worked.
So I decided to sent it to service. they realized it was a soft problem and charged me about 40 $ to repair.
every thing is great now, BUT I have found in the box when I have picked up my tablet from service a 2 gb sd card
i thought that was the sd card used to resoft my tablet, so I inserted the sd card in my tablet and rebooted while holding the vol plus button and it started to say something like: cold-boot linux kernel from sd card. i didnt want to break it again because i didnt have enough power and I restarted my tablet. it works ok.
I want to see what it is on that sd card and share this tool with you, but for this I need help from you to create an image or something like that of this sd card. I have an macbook pro with os x maverick.
Any Ideeas?
Can you upload the files in a zip file?
Sent from my Nexus 4 using Tapatalk
CoolApps said:
Can you upload the files in a zip file?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
my macbook sees the sd card, but it tells me that is not in a recognisable format and wants to format it.
deltaztek said:
my macbook sees the sd card, but it tells me that is not in a recognisable format and wants to format it.
Click to expand...
Click to collapse
If you can, try puting ubuntu on a cd and live boot it on the computer then put in the sdcard and see if it recognizes it
Sent from my C6603 using xda app-developers app
Oh damn, dd it to a file. If you can't do this, I can connect to your computer with teamviewer.
Sony Tablet S cihazımdan Tapatalk kullanılarak gönderildi
I have created a raw copy with Hdd raw copy tool
the image is here. please download until 22 jan 2014
www wetransfer com/downloads/0bf376dc203efb9020b16ad377e5e47820140115102753/0734314e80d6048007785b2d3448fd3020140115102753/8c53e2
replace the spaces in the we transfer link with dots because i have received this error: The following errors occurred with your submission:
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
deltaztek said:
I have created a raw copy with Hdd raw copy tool
the image is here. please download until 22 jan 2014
www wetransfer com/downloads/0bf376dc203efb9020b16ad377e5e47820140115102753/0734314e80d6048007785b2d3448fd3020140115102753/8c53e2
replace the spaces in the we transfer link with dots because i have received this error: The following errors occurred with your submission:
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
Click to expand...
Click to collapse
I wrote the image to my sd card and it is containing 3 partitions. But it is not working for tablet s. Can you explain how can you able to boot the tablet from that card?
Sony Tablet S cihazımdan Tapatalk kullanılarak gönderildi
smgdev said:
I wrote the image to my sd card and it is containing 3 partitions. But it is not working for tablet s. Can you explain how can you able to boot the tablet from that card?
Sony Tablet S cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
I have Sony Xperia Tablet S, which is the next generation of Sony Tablet S.
I have inserted the sd card and tried to boot but nothing happens. I can no longer acces the menu with Power+Vol UP or with Power +Vol UP+Vol Down, which I could before the service did the firmware upgrade. that is why is important this sd card, to see what it contains and how it works.
I apparently can't do nothing with it besides being stuck on screen with this text: Cold-boot Linux.kernel from sd-card.
Wow !
deltaztek thanks for sharing this with us , i think this maybe will be the solution to many bricked devices.
Cheers
Vatis
Damn, this is cool stuff! Just what we needed, service to forgot recovery SD card inside debricked device! Let's see if we can learn how to use this, too bad I am having so little time nowadays.
Btw. what do you mean "I can no longer acces the menu with Power+Vol UP or with Power +Vol UP+Vol Down, which I could before the service did the firmware upgrade. that is why is important this sd card, to see what it contains and how it works." ?
Do you mean that you cannot anymore access recovery, with or without recovery SD-card?
- What happens without SD-card, does your tablet boot normally
- Without SD-card, what happens if you try to go to recovery when booting by Power+Vol?
- With SD-card what happens when you boot normally?
- With SD-card what happens when you try to get to recovery?
I will download image, but my tab is not with me this weekend, damn...
Do NOT let your OSX format the card This is great great stuff.
---------- Post added at 02:24 PM ---------- Previous post was at 02:10 PM ----------
Oh and is the SD card itself ordinary generic SD card or is it some kind of Sony's special card or something?
jappaj said:
Damn, this is cool stuff! Just what we needed, service to forgot recovery SD card inside debricked device! Let's see if we can learn how to use this, too bad I am having so little time nowadays.
Btw. what do you mean "I can no longer acces the menu with Power+Vol UP or with Power +Vol UP+Vol Down, which I could before the service did the firmware upgrade. that is why is important this sd card, to see what it contains and how it works." ?
Do you mean that you cannot anymore access recovery, with or without recovery SD-card?
- What happens without SD-card, does your tablet boot normally
- Without SD-card, what happens if you try to go to recovery when booting by Power+Vol?
- With SD-card what happens when you boot normally?
- With SD-card what happens when you try to get to recovery?
I will download image, but my tab is not with me this weekend, damn...
Do NOT let your OSX format the card This is great great stuff.
---------- Post added at 02:24 PM ---------- Previous post was at 02:10 PM ----------
Oh and is the SD card itself ordinary generic SD card or is it some kind of Sony's special card or something?
Click to expand...
Click to collapse
Ok here is the strange thing...
When i connect the tab on my pc inside recovery i can not connect with ADB , BUT when i am on cold-boot and connect the tab on pc then showing that discovered a sony device then i dont have drivers but i install ADB test drive 2013 , then i can connect with ADB, any ideas? i try to shell but i am getting error :
C:\adb>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
- exec '/system/bin/sh' failed: Permission denied (13) -
anything else i can try?
Cheers
Please explain how device works when this SD card is inside What happens when you boot normally this SD card inside, what happens if you boot Power-Vol ? When this cold boot appears, what did you do?
Next week I can get my tab back and can try this by myself...
jappaj said:
Please explain how device works when this SD card is inside What happens when you boot normally this SD card inside, what happens if you boot Power-Vol ? When this cold boot appears, what did you do?
Next week I can get my tab back and can try this by myself...
Click to expand...
Click to collapse
Ok here is the deal :
After you burn the .img on the sd card the windows stops see the sd card due to the format , so i have to boot linux to see whats is inside sd card, but some people reported 3 partitions .... on uper posts.
Anyway when you boot the tablet with the SD card inside either you try to go to recovery automatically booting from sd card and writing on tablet : Cold-booting linux. kernel from sd card , but nothing happens , now if you remove the sd card and try to boot to recovery wokring as before. If you boot to recovery and after put the sd card can read the sd card from recovery but there is nothing to flash.
Any ideas?
Edit : Can you see mate whats on sd card after burning the .img ? Whats so big for 1.8 gb ?
Hmh. Sound like me that said SD do not contain zip file to flash from the recovery, instead tablet recognizes it as some kind of special Sony's maintenance card an boots directly Linux kernel from the card. If I am correct, this way you can recover device even if recovery itself has been corrupted.
But if there is nothing happening after "Cold-booting linux. kernel from sd card", it could be that some extra gear is required. In example serial cable through which you can run shell commands or perhaps ordinary USB cable but some kind of special software would be needed to upload new images to the device. This is just a quess though.
Need to check out that img and what's inside after I have some time. Let's hope it is not encrypted and all files inside can be read...
jappaj said:
Hmh. Sound like me that said SD do not contain zip file to flash from the recovery, instead tablet recognizes it as some kind of special Sony's maintenance card an boots directly Linux kernel from the card. If I am correct, this way you can recover device even if recovery itself has been corrupted.
But if there is nothing happening after "Cold-booting linux. kernel from sd card", it could be that some extra gear is required. In example serial cable through which you can run shell commands or perhaps ordinary USB cable but some kind of special software would be needed to upload new images to the device. This is just a quess though.
Need to check out that img and what's inside after I have some time. Let's hope it is not encrypted and all files inside can be read...
Click to expand...
Click to collapse
Filer are not encrypted and image contains 3 partitions, one of them contains a full system rot filesystem, and second one contains something similiar to first and third is empty.
Sony Tablet S cihazımdan Tapatalk kullanılarak gönderildi
deltaztek said:
Hello all. After bricking my Xperia tablet S by the next method: rooted it, then install a soft called as I remember PLay help, or something like that, a soft that helped you make your device look like any other in Google play sao you can install all apps even if they aren't made for your device. everything was ok but when i restarted my tablet it wouldnt pass the sony logo and than black screen.
So I tryed all methods provided within this forum, but nothing worked.
So I decided to sent it to service. they realized it was a soft problem and charged me about 40 $ to repair.
every thing is great now, BUT I have found in the box when I have picked up my tablet from service a 2 gb sd card
i thought that was the sd card used to resoft my tablet, so I inserted the sd card in my tablet and rebooted while holding the vol plus button and it started to say something like: cold-boot linux kernel from sd card. i didnt want to break it again because i didnt have enough power and I restarted my tablet. it works ok.
I want to see what it is on that sd card and share this tool with you, but for this I need help from you to create an image or something like that of this sd card. I have an macbook pro with os x maverick.
Any Ideeas?
Click to expand...
Click to collapse
Very very interesting Thank you very much deltaztek for sharing!
It might bring some capabilities, downloading, will take a look
Shame I've got only Tab S, maybe it could be modded to work on 1st Tab S also?
Unfortunately I suspect, that it will work only on Xperia Tab, because of other boot maybe etc.
br
condi
------------------------------
ok, everybody who wants to take a look into partitions in windows,
there is an easy way.
1) download win32diskimager, write img to some SD card.
2) download linux reader, run it
3) voila - all the files accessible
-------------------------------
guys? some maybe stupid idea, but I havent seen that diagnostic card running on device.
if its native linux runned, with adb shell not accessible, but with svold.fstab content:
## SVold 1.0
#######################
## Regular device mount
##
## Format: edev_mount <label> <mount_point> <dtype> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## dtype - Device type
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
dev_monitor sdcard2 /mnt/sdcard2 sd auto /devices/platform/sdhci-tegra.2/mmc_host/mmc1
edev_mount usbdisk1 /mnt/usbdisk1 usb auto /devices/platform/tegra-ehci
edev_mount usbdisk2 /mnt/usbdisk2 usb auto /devices/platform/tegra-ehci
edev_mount usbdisk3 /mnt/usbdisk3 usb auto /devices/platform/tegra-ehci
edev_mount usbdisk4 /mnt/usbdisk4 usb auto /devices/platform/tegra-ehci
edev_mount usbdisk5 /mnt/usbdisk5 usb auto /devices/platform/tegra-ehci
edev_mount usbdisk6 /mnt/usbdisk6 usb auto /devices/platform/tegra-ehci
edev_mount usbdisk7 /mnt/usbdisk7 usb auto /devices/platform/tegra-ehci
edev_mount usbdisk8 /mnt/usbdisk8 usb auto /devices/platform/tegra-ehci
Click to expand...
Click to collapse
where all the usb devices should be mounted,
so you could connect usb keyboard via otg host cable,
and with it have access and control on linux command prompt?
anybody here could try?
------------------------
build.prop content:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.display.id=txs03_351-eng 4.0.3 IML74K eng.t-yanagawa.20120618.223335 test-keys
ro.build.version.incremental=txs03servicediag.eng.t-yanagawa.20120618.223335
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=2012ĺą´ 6ćśˆ 18ć—Ą ćśˆć›ść—Ą 22:36:32 JST
ro.build.date.utc=1340026592
ro.build.type=eng
ro.build.user=t-yanagawa
ro.build.host=t-yanagawa-laptop
ro.build.tags=test-keys
ro.product.model=Sony Tablet S_2
ro.product.brand=Sony
ro.product.name=txs03_351
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 is obsolete; use ro.product.device
ro.build.product=txs03
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=txs03_351-eng 4.0.3 IML74K eng.t-yanagawa.20120618.223335 test-keys
ro.build.fingerprint=Sony/txs03_351/txs03:4.0.3/IML74K/eng.t-yanagawa.20120618.223335:eng/test-keys
ro.build.characteristics=tablet
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
wifi.wpa_supp_ready=0
persist.tegra.nvmmlite = 1
##NFC
#debug.nfc.fw_download=false
#debug.nfc.se=false
windowsmgr.max_events_per_sec=135
ro.tether.denied=true
ro.sony.sound.enabled=true
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.product-res-path=vendor/framework/SemcGenericUxpRes.apk
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.sony.update.service_id=txs03_351
ro.sony.sku.base=txs03_351
ro.sony.build.id=TID0010000
ro.sony.build.incremental=120618223
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
drm.service.enabled=true
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
keyguard.no_require_sim=1
ro.sony.wan.dispMenuNwTyp=true
rild.libpath=/system/lib/libhuawei-ril.so
ro.kernel.gps.data=/dev/ttyUSB3
ro.kernel.gps.ctl=/dev/ttyUSB4
ro.sony.wan.sar.enable=yes
ro.sony.wifisleep=0
ro.com.google.gmsversion=4.0_r1
ro.com.google.clientidbase=android-sony
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
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.irremote.protocol_type=2
ro.sony.ols.eula=1
Click to expand...
Click to collapse
incremental value looks nice
ro.build.version.incremental=txs03servicediag.eng.t-yanagawa.20120618.223335
condi said:
Very very interesting Thank you very much deltaztek for sharing!
It might bring some capabilities, downloading, will take a look
Shame I've got only Tab S, maybe it could be modded to work on 1st Tab S also?
Unfortunately I suspect, that it will work only on Xperia Tab, because of other boot maybe etc.
br
condi
------------------------------
ok, everybody who wants to take a look into partitions in windows,
there is an easy way.
1) download win32diskimager, write img to some SD card.
2) download linux reader, run it
3) voila - all the files accessible
-------------------------------
guys? some maybe stupid idea, but I havent seen that diagnostic card running on device.
if its native linux runned, with adb shell not accessible, but with svold.fstab content:
where all the usb devices should be mounted,
so you could connect usb keyboard via otg host cable,
and with it have access and control on linux command prompt?
anybody here could try?
Click to expand...
Click to collapse
Amazing idea, i have the cable and i can try it tommorow, i will let you know
Cheers
Vatis
vatis24 said:
Amazing idea, i have the cable and i can try it tommorow, i will let you know
Cheers
Vatis
Click to expand...
Click to collapse
Waiting for results
-------------------------
interesting .sh files inside /xbin/..
chkbootloader.sh:
Code:
#!/system/xbin/busyboxbin/sh
if [ "$1" == "" ]; then
echo COMMAND NOT FOUND
echo Result:NG
exit 1
else
hd -c 4200 /dev/block/mmcblk0p8 | /system/xbin/busyboxbin/grep "5f 42 4c" >/dev/null
if [ $? -ne 0 ]; then
echo Cannot get Bootloader version
echo Result:NG
exit 1
fi
BL_1=`hd -c 4200 /dev/block/mmcblk0p8 | /system/xbin/busyboxbin/grep "5f 42 4c" | /system/xbin/busyboxbin/cut -d " " -f6`
BL_2=`hd -c 4200 /dev/block/mmcblk0p8 | /system/xbin/busyboxbin/grep "5f 42 4c" | /system/xbin/busyboxbin/cut -d " " -f7`
BL_3=`hd -c 4200 /dev/block/mmcblk0p8 | /system/xbin/busyboxbin/grep "5f 42 4c" | /system/xbin/busyboxbin/cut -d " " -f8`
BL_4=`hd -c 4200 /dev/block/mmcblk0p8 | /system/xbin/busyboxbin/grep "5f 42 4c" | /system/xbin/busyboxbin/cut -d " " -f9`
BOOTLOADER=$BL_1$BL_2$BL_3$BL_4
echo Value, 0x$BOOTLOADER
if [ $BOOTLOADER -eq $1 ]; then
echo Result:eek:K
exit 0
else
echo Result:NG
exit 1
fi
fi
exit 0
diaginit.sh:
Code:
#!/system/xbin/busyboxbin/ash
/system/xbin/busyboxbin/awk '/^[a-z]/{sub(/=/," "); print "setprop "$1" \""$2"\""}' /system/build.prop > /tmp/setprop.sh
/system/bin/sh /tmp/setprop.sh
rm /tmp/setprop.sh
mount -r -w -t ext2 /dev/block/mmcblk0p1 /configs
mount -r -w -t ext4 /dev/block/mmcblk0p5 /cache
mount -r -t ext4 /dev/block/mmcblk0p10 /log
/system/xbin/busyboxbin/awk '/^[a-z]/{sub(/=/," "); print "setprop "$1" \""$2"\""}' /configs/local.prop | /system/xbin/busyboxbin/grep "bdaddr" > /tmp/setlocalprop.sh
/system/bin/sh /tmp/setlocalprop.sh
rm /tmp/setlocalprop.sh
setprop vold.decrypt trigger_restart_framework
export PS1="# "
That diag.init probably is being started on boot with service mode,
or should be initiated manually via running with shell.
Oh and there is SU binary already there
-----------------------
im thinking is it worth to replace system partition with nbx03 1st gen Tab S,
maybe we could use it on our devices also
-------------------------
there are some parametrs set in /property/ <<<<<<<<<< we could try to add "persist.service.adb.enable"
in order to get adb working
My wife going to sleep now i will test now the keyboard via usb on tablet i will revert very soon!!!
---------- Post added at 11:21 PM ---------- Previous post was at 11:11 PM ----------
vatis24 said:
My wife going to sleep now i will test now the keyboard via usb on tablet i will revert very soon!!!
Click to expand...
Click to collapse
Keyboard not working , i mean getting power but nothing happens, maybe a usb drive to usb port? with update zip ? just saying , any ideas?
Vatis
vatis24 said:
My wife going to sleep now i will test now the keyboard via usb on tablet i will revert very soon!!!
---------- Post added at 11:21 PM ---------- Previous post was at 11:11 PM ----------
Keyboard not working , i mean getting power but nothing happens, maybe a usb drive to usb port? with update zip ? just saying , any ideas?
Vatis
Click to expand...
Click to collapse
could you make a short video how this service mode looks?