[Q] twlauncher crash loop error / factory reset? - Galaxy S II Q&A, Help & Troubleshooting

1) I have twlauncher crash loop error (i caused this while using swiftkey 3 typing an email in skyfire then i pressed home key to bring back to home, phone crashed, took out battery, put it back it, hey presto twlauncher crash loop error plus every other crash loop error. I did not recently install any apps etc)
2) i cannot do the "normal fix" of remote install alternative launcher on google play store on pc then push to mobile because due to twlauncher crash loop error, i cannot turn on wifi or mobile 3g so phone cannot connec to internet
3) what's left is power + vol up + home = factory reset? But will that brick my phone?
I ask because a long time ago, I flashed the firmware using Odin and rooted the phone, so when it starts up there is yellow triangle. If I use the stock Android recovery program to factory reset, is that going to break my phone because I installed a different firmware / rom on it? PS i don't remember what i installed, or even how because it was a long time ago and i have forgotten.
I also found this website, http://knowledge-republic.com/CRM/2...alled-process-com-sec-android-app-twlauncher/
seeme interesting, but i can't check it out yet because my smartphone broke while travelling and i don't get back home for a few days yet. anyone confirm the above link? It seems to be written in bad english.
thanks

jeanclaudevandamme said:
1) I have twlauncher crash loop error (i caused this while using swiftkey 3 typing an email in skyfire then i pressed home key to bring back to home, phone crashed, took out battery, put it back it, hey presto twlauncher crash loop error plus every other crash loop error. I did not recently install any apps etc)
2) i cannot do the "normal fix" of remote install alternative launcher on google play store on pc then push to mobile because due to twlauncher crash loop error, i cannot turn on wifi or mobile 3g so phone cannot connec to internet
3) what's left is power + vol up + home = factory reset? But will that brick my phone?
I ask because a long time ago, I flashed the firmware using Odin and rooted the phone, so when it starts up there is yellow triangle. If I use the stock Android recovery program to factory reset, is that going to break my phone because I installed a different firmware / rom on it? PS i don't remember what i installed, or even how because it was a long time ago and i have forgotten.
I also found this website, http://knowledge-republic.com/CRM/2...alled-process-com-sec-android-app-twlauncher/
seeme interesting, but i can't check it out yet because my smartphone broke while travelling and i don't get back home for a few days yet. anyone confirm the above link? It seems to be written in bad english.
thanks
Click to expand...
Click to collapse
can you confirm if Usb debug is enabled on your phone?

Jokesy said:
can you confirm if Usb debug is enabled on your phone?
Click to expand...
Click to collapse
yes it is enabled. What does that affect exactly, if the method in the last link will work?
I still don't have access to my own laptop yet as I'm travelling.

jeanclaudevandamme said:
yes it is enabled. What does that affect exactly, if the method in the last link will work?
I still don't have access to my own laptop yet as I'm travelling.
Click to expand...
Click to collapse
When you have access to your laptop, let me know. You are going to install another launcher via ADB, so there won't be any need to factory reset

Jokesy said:
When you have access to your laptop, let me know. You are going to install another launcher via ADB, so there won't be any need to factory reset
Click to expand...
Click to collapse
I will be reunited with my laptop in a few hours. So what are the steps for this fix? Life without my smartphone is difficult :crying:

jeanclaudevandamme said:
I will be reunited with my laptop in a few hours. So what are the steps for this fix? Life without my smartphone is difficult :crying:
Click to expand...
Click to collapse
1. Download ADB.zip here: www.mediafire.com/?18k1mi04lpg75y2
2. Extract the zip on your computer. (Please note this location)
3. Ensure Samsung USB drivers is installed on your laptop. Just install kies if you are not sure.
4. Download Go launcher Ex here: www.iapktop.com/go-launcher-ex-3-16.html
You can also download any launcher of your choice.
5. Copy the launcher .apk you just downloaded to the extracted ADB folder. Rename the launcher to launcher.apk
When you are done let me know

Jokesy said:
1. Download ADB.zip here: www.mediafire.com/?18k1mi04lpg75y2
2. Extract the zip on your computer. (Please note this location)
3. Ensure Samsung USB drivers is installed on your laptop. Just install kies if you are not sure.
4. Download Go launcher Ex here: www.iapktop.com/go-launcher-ex-3-16.html
You can also download any launcher of your choice.
5. Copy the launcher .apk you just downloaded to the extracted ADB folder. Rename the launcher to launcher.apk
When you are done let me know
Click to expand...
Click to collapse
you mean whatever the apk for the launcher is originally called, rename to launcher.apk?
and also, i'm just setting off now for the journey ahead, by the time i have my laptop, i think you'll be in bed and i will have to wait until tomorrow. so pls just all the steps so i try asap when i have laptop? much appreciated btw!

jeanclaudevandamme said:
you mean whatever the apk for the launcher is originally called, rename to launcher.apk?
Click to expand...
Click to collapse
Yes. Rename it to launcher.apk
After finishing with the steps in my previous post, you can move to the following steps:
1. Connect your device to pc (power it on) and wait for the drivers to install
2. Open the extracted ADB folder,
- hold the SHIFT key, and RIGHT CLICK on a blank area in the folder,
- select OPEN COMMAND PROMPT HERE, from the right click options,
- command window will open
3. In command window, type as follows
- adb devices
#this will confirm if your device is connected
- adb install launcher.apk
- adb reboot
Wait for your phone to reboot, then disconnect it from your Pc.
You should now have the option to choose another launcher.
Done.

it's not working. I think it's because the twlauncher error has somehow caused my phone to be unrooted, or at least making all applications requring superuser access disabled. because the adb install command fails because it says an folder (/data/local/tmp/) is read / only and when I go into Root Explorer to try making it r/w, the first message i get is the Superuser application stopping unexpectedly.
but when i check for root access using adb, ie "adb shell", I get "#", which means I still have root access?
I don't understand.
-------------------------------
Upon further investigation, it seems that the entire /data folder and subfolders are locked to r/o by the twlauncher failure (logprovider as well as every other crash loop error) caused initially by Swiftkey 3 when i pressed the home key while typing in Skyfire.
I have managed to regain some minor amount of utility by following a series of frustrated attempts,
*when there are 10 different crash loop errors, try pressing as fast as I can go to into task manager, the crash loop errors will now be reduced to about 3, then clear ram. This takes something like 25 attemps
*when there 2 crash loop errors remaining, try pressing as fast as i can "force close -> options (button left of home key) -> setting in the pop up panel. This will take something like 50 attempts to get the timing right so I am able to fast press everything in sequence before the next force error makes me start again.
*once into settings, there is just one crash loop error (logprovider), go into applications, all, twlauncher and press force end (obviously there'll be crash loop errors so you have to be quick in pressing keys)
*now there are no crash loop errors until you press the homekey or try and access all your applications (twlauncher error remains, logprovider will come up again and i have to repeat all these steps if i try to use contact/message function)
What the above has essentially enabled me to do is to access a few applications that was on my 1st or 2nd homescreen by chance (not all will work) , i still can't access any on my app screen as twlauncher crashes too fast.
This is how I have been able to simultaenously mess around with Root Explorer and ADB on my PC in USB debugging mode.
This is how i have discovered that when I use Rootexplorer, initially it says Superuser application has stopped and I have to force close it.
However, I am still able to use Rootexplorer to mount r/w or r/o on a few folders, such as /system , so this implies that I do still have root access. However, there is no options to make /data r/w, even in root explorer, attempts using adb to make /data r/w also fails.
What this means is that I can't clear the cache / dalvik-cache as they are sub folders of /data. It means that adb install launcher.apk fails because /data/local/tmp, the folder where you're copying the apk to is r/o. It means that I can't install or uninstall any applications because /data/apps is read only.
For eg, I have used adb push launcher.apk successfully to put go ex launcher in the /system/apps folder, but it just stays there as an apk file (from previous experiences, putting an apk in the /system/apps file doesn't make that apk install on boot, because you need an odex file for that apk). So when I manually select to install that apk, phone crashes and reboots because /data/apps is r/o. This is also how I can't uninstall or clear the cache of the application that caused this in the first place (swiftkey 3)

Model Number: GT-I9100
Android Version: 2.3.3.
Baseband version: I9100XXKDH
Kernel Version: 2.6.35.7-I9100XWKDD-CL161513
[email protected] #2
Build Number: GINGERBREAD.XWKDD
--------------
Oh and I found how to get contacts and messages.
Using ADB
adb pull /data/data/com.android.providers.contacts/databases/contacts2.db
adb pull /data/data/com.android.providers.telephony/databses/mmssms.db
Then I installed SQ Lite Manager add on for Firefox and opened the 2 .db files.
Well, I'm making progress now on how to read the information from a database, it's like pieces of a jigsaw puzzle. I feel confident in putting them together via extensive cross referencing and recovering all text messages and phone numbers, even if I have to type them out by hand into Word.
Thanks Jokesy for helping me with this damn Twlauncher problem. If the worst comes to worst, I think I can recover all personal data from the device before wiping everything.

jeanclaudevandamme said:
Model Number: GT-I9100
Android Version: 2.3.3.
Baseband version: I9100XXKDH
Kernel Version: 2.6.35.7-I9100XWKDD-CL161513
[email protected] #2
Build Number: GINGERBREAD.XWKDD
--------------
Oh and I found how to get contacts and messages.
Using ADB
adb pull /data/data/com.android.providers.contacts/databases/contacts2.db
adb pull /data/data/com.android.providers.telephony/databses/mmssms.db
Then I installed SQ Lite Manager add on for Firefox and opened the 2 .db files.
Unfornately, having never seen a database file before in my life, haven't found way to convert the information into a useful display format, et all telephone numbers corresponding to contact name, and all messages in their own threads.
Thanks Jokesy for helping me with this damn Twlauncher problem.
Click to expand...
Click to collapse
don't worry.
1. You need to flash a ROOT kernel with CWM recovery. You can flash CF-ROOT kernel or Siyah kernel via Odin
2. We need this so that adb can gain root access, and also to probably flash another launcher at worst via CWM recovery. We can also disable Touchwiz launcher temporarily via ADB.
3. Do you have CWM zip template?
---------- Post added at 03:27 AM ---------- Previous post was at 03:10 AM ----------
1. Download Siyah kernel 2.6.6 : www.gokhanmoral.com/public/files/siyahkernel/Siyah-v2.6.6.tar
2. Download CF-ROOT kernel
3. Flash Siyah kernel via Odin
When you are done, let me know

Jokesy said:
don't worry.
1. You need to flash a ROOT kernel with CWM recovery. You can flash CF-ROOT kernel or Siyah kernel via Odin
2. We need this so that adb can gain root access, and also to probably flash another launcher at worst via CWM recovery. We can also disable Touchwiz launcher temporarily via ADB.
3. Do you have CWM zip template?
---------- Post added at 03:27 AM ---------- Previous post was at 03:10 AM ----------
1. Download Siyah kernel 2.6.6 : www.gokhanmoral.com/public/files/siyahkernel/Siyah-v2.6.6.tar
2. Download CF-ROOT kernel
3. Flash Siyah kernel via Odin
When you are done, let me know
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1056334
I originally rooted my phone following the instructions in that thread. So I assume the kernels you're referring to are compatible with the ROM I flashed?
No I do not have CWM zip template, what is it and where/how can i get it/make it?
I basically rooted my phone as soon as I got it, didn't change a thing after the initial messing about.
Why do you want me to download the CF-Root Kernel but flash the Siyah kernel?
I will redownload Odin and see about the flashing the kernel as you have said. It's been a while.. I also need to sleep now for a while, when I wake up tomorrow morning, I will read a bit more about the stuff you have to me to do, then try to do it. Thx.

Ok.
That means you rooted your phone using insecure kernel, right?
I want you to download and flash a kernel that has CWM recovery. We really need it to flash another launcher and rename Touchwiz launcher via CWM recovery.
What's your time there?
---------- Post added at 04:04 AM ---------- Previous post was at 04:02 AM ----------
Yes, the Siyah kernel is compatible with gingerbread.
I couldn't find a compatible CF-ROOT kernel, so i guess you will have to flash Siyah kernel

Jokesy said:
Ok.
That means you rooted your phone using insecure kernel, right?
I want you to download and flash a kernel that has CWM recovery. We really need it to flash another launcher and rename Touchwiz launcher via CWM recovery.
What's your time there?
---------- Post added at 04:04 AM ---------- Previous post was at 04:02 AM ----------
Yes, the Siyah kernel is compatible with gingerbread.
I couldn't find a compatible CF-ROOT kernel, so i guess you will have to flash Siyah kernel
Click to expand...
Click to collapse
UK Time. I will be here now for a several hours.
Well, I think it's insecure because when I start my phone there is a yellow triangle with ! inside.
So, I've downloaded Odin 3.04. The Siyah Kernal as you said, after extracting from zip, I get "zImage", type of file is "File."
So how to flash? I really have forgotten all of this. So I start my SGS2 in Download Mode, go to Odin, select PDA, select zImage, the press Start?
What then? Thx

You don't need to extraxt it from .tar select PDA then selexct unzipped Kernel and then start

Paulius7 said:
You don't need to extraxt it from .tar select PDA then selexct unzipped Kernel and then start
Click to expand...
Click to collapse
Odin ID:COM is is not turning yellow, it is a sort of light blue colour. Is this to do with odin v3.04 rather than v1.85?
------------------------
OK I've flashed it. Odin shows in green PASS!
----------------------
Ok, phone boots as normal, still yellow warning triangle. Still Twlauncher error.
-----------------------
Now The recovery mode has changed from default Android to CW-based Recovery v5.0.2.7 with the following options:
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
install zip from sdcard
backup and restore
mounts and storage
advanced
power off
+++++Go Back+++++

jeanclaudevandamme said:
Odin ID:COM is is not turning yellow, it is a sort of light blue colour. Is this to do with odin v3.04 rather than v1.85?
------------------------
OK I've flashed it. Odin shows in green PASS!
----------------------
Ok, phone boots as normal, still yellow warning triangle. Still Twlauncher error.
Click to expand...
Click to collapse
Ok. All now if you want to remove triangle search on this forum "triangle away" in play is paid in this forum free.
But with crashing twlauncher I can't help...
Send form Galaxy S2. Using XDA Premium

jeanclaudevandamme said:
Odin ID:COM is is not turning yellow, it is a sort of light blue colour. Is this to do with odin v3.04 rather than v1.85?
------------------------
OK I've flashed it. Odin shows in green PASS!
----------------------
Ok, phone boots as normal, still yellow warning triangle. Still Twlauncher error.
-----------------------
Now The recovery mode has changed from default Android to CW-based Recovery v5.0.2.7 with the following options:
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
install zip from sdcard
backup and restore
mounts and storage
advanced
power off
+++++Go Back+++++
Click to expand...
Click to collapse
Good.
Download CWM.zip template
follow these steps:
1. Rename Go launcher.apk to com.gau.go.launcherex-1.apk
2 Open CWM.zip with 7zip, WinRar or similar apps (Don't Extract)
3. Copy com.gau.go.launcherex-1.apk to data/app
4. Close CWM.zip
5. Boot to Recovery
- Select Mounts and Storage
- Connect your phone to PC
- Turn on USB storage
- Copy CWM.zip to your phone
- Safely remove you phone from pc
- Unmount usb storage from recovery
- Disconnect phone from PC
- Press back button, select flash zip from Sd card
- Flash CWM.zip
- reboot phone

Jokesy said:
Good.
Download CWM.zip template
follow these steps:
1. Rename Go launcher.apk to com.gau.go.launcherex-1.apk
2 Open CWM.zip with 7zip, WinRar or similar apps (Don't Extract)
3. Copy com.gau.go.launcherex-1.apk to data/app
4. Close CWM.zip
5. Boot to Recovery
- Select Mounts and Storage
- Connect your phone to PC
- Turn on USB storage
- Copy CWM.zip to your phone
- Safely remove you phone from pc
- Unmount usb storage from recovery
- Disconnect phone from PC
- Press back button, select flash zip from Sd card
- Flash CWM.zip
- reboot phone
Click to expand...
Click to collapse
OK. Done of all that.
Phone reboots ok.
Still Twlauncher error, there is no option to use another launcher?
-------------------------
Just checked /data/apps no sign of the com.gau.go.launcherex-1.apk that should have been flashed.
Rebooting phone now because some other previous installed apps were greyed out, meaning error with sd card reading.

jeanclaudevandamme said:
OK. Done of all that.
Phone reboots ok.
Still Twlauncher error, there is no option to use another launcher?
-------------------------
Just checked /data/apps no sign of the com.gau.go.launcherex-1.apk that should have been flashed.
Rebooting phone now because some other previous installed apps were greyed out, meaning error with sd card reading.
Click to expand...
Click to collapse
have rebooted the phone, anything?

Related

Agh! what am i doing wrong!??

Hi everyone.
I'm really sick of this phone (X10 mini pro). right now no matter what i try and flash to it using xrecovery and update.zip, i reboot and always find that i'm running the same old system - like as if i've done NOTHING TO IT AT ALL!
I tried flashing this (which is what i really wanted):
http://forum.xda-developers.com/showthread.php?t=1041099
Nothing, reboots into stock.
I then tried this:
http://forum.xda-developers.com/showthread.php?t=1059361
Also no luck.
What am i doing wrong!? I download the rom, extract (System, META-INF and/or any other folder) and then i install any hotfixes by dragging and dropping/replacing files.
I then zip up the system and meta folders (plus anything else ie: Data folder) to update.zip, then install via xrecovery -- which does so fine, no warning messages -- then i CLEAR cache or format data (if instructed) and reboot.
As far as i can tell, i'm doing NOTHING wrong and it's extremely frustrating. Everytime i reboot i'm greeted with the same old setup wizard, same old theme, same stock "About Phone" details, as listed below:
Model Number:
U20i
Firmware Version:
2.1-update1
Baseband Version:
M76XX-TSNCJOLYM-53404015
Kernal Version:
2.6.29
[email protected] #1
Build Number:
2.1.1.A.0.6
What is going on???
Have you tried not renaming the zip file and flash it as it is, then flash the hotfixes next?
Maybe what you added or replaced caused the flashing to not work at all. For me when I flash a big rom it'll take about a minute. If it was flashed and you don't even see it copying files then it must have failed.
Sent from my U20i using XDA App
Choose custom zip, navigate to the zip file location in your sd card and confirm flashing it. Must work. I bet you flashed the "update.zip" which doesn't exist.
Sent from my U20i using XDA App
Thanks for the quick reply guys.
Unfortunately i've tried both these methods and i still get the same problem. (I just tried both methods again to be sure) Xrecovery just states "Copying files..." then within about a minute or so, it tells me it's "Completed"
Just for the record, i did buy this phone used (and "unlocked" to any network) would that somehow have something to do with this?
I've also tried a factory reset using the PC companion from Sony (then installing a rom) even after that i still get this problem.
Frustrating, very frustrating.
Ok, so i did this all over again:
Step 1.
Reset phone using PC Companion
Step 2
Setup Wifi using the wizard
Step 3
enable usb debugging and Unknown Sources (both under Applications)
Step 4
Connect phone via usb, transfer over Xrecovery, update.zip, etc. Then UNMOUNT SDCARD.
Root phone using S1C, install busybox during then reboot.
Step 5:
Setup marketplace account & Download (provided i get past that rediculous "downloading.." hang bug):
Busybox Installer, once downloaded, double click icon and install
Download and install Root Explorer
Step 6:
install Xrecovery manually using Root Explorer, placing it's 3 files in \system\bin
step 7:
Connect usb, transfer over update.zip, reboot and enter xrecovery
Now, guess what? XRECOVERY won't even start when i hit the back button when the SE logo appears!
One problem after another, about to give up. Really not impressed.
Do the following at your own risk
> Before you start make sure you have
- Root access
- Busy box and terminal emulator (you can get this from the market) installed
1. Download this script http://www.mediafire.com/?yw2a3r2didpb51t
2. Extract the folder called AAIS and rename it to "aais" (without the quotations)
3. Copy the aais folder to sdcard
4. Open up terminal emulator and type in the following commands
Code:
su
Click on allow when superuser dialog pops up and then type
Code:
cd sdcard/aais
Code:
sh install.sh
A list will appear, type the number which installs xrecovery and press enter
Once the phone has rebooted
1. Copy the zip of the rom which you want to install straight to the sd card (Do not rename it, extract it or do anything to it)
2. Copy the zip of the hotfixes straight to the sd card (again do not rename, extract or do anything)
3. Reboot phone, when it reaches "Sony Ericsson" press back a few times to boot into xrecovery
4. Using xrecovery do this
- Wipe cache partition
- Advanced option > wipe dalvik cache and wipe battery stats
- Go back to xrecovery main menu and then click on factory reset (full wipe)
4. Then goto install custom zip > choose custom zip from sdcard > and then choose the rom zip. Let it install
5. Once rom is installed click on choose custom zip from sdcard > and then choose the hotfix zip.
6. Once installed go back to xrecovery main menu and reboot phone
Hopefully should work
K><A said:
Do the following at your own risk
*snip*
Click to expand...
Click to collapse
Thanks for this post, exactly what i needed. Tis much appreciated.
I did what you said, word for word, and everything went smoothly. Xrecovery booted up fine and installed everything fine.
Unfortunately, this has failed to resolve the problem. I'm totally clueless as i'm sure most of you are. All i can say is it's not user error - i've not done anything wrong or missed a THING. I've really followed as you instructed word for word (as i did with previous attempts) and i still got nowhere. I've now spent all day trying to resolve this and still with no luck.
The only difference all of this ever seems to make is i'm constantly bothered by popups saying "X application has failed" etc etc now. It still just boots into the regular OS like as if nothing has happend.
Download this file, do not extract it, copy it straight to your sd card:
https://rapidshare.com/#!download|7...zip|121614|R~E38D143E052C271F51D9FBCAF24427E1
Download this file, do not extract it, copy it straight to your sd card
https://rapidshare.com/#!download|3...ight.zip|1|R~11A42E8D7D5D2FAE74791CC0D9911BE7
Go into xrecovery then
Wipe cache partition
Wipe dalvick cache
Wipe battery stats
Factory reset (full wipe)
Goto install custom zip from sd card and flash the first file
then flash the second file. Reboot phone. Hope it works.
1- Download Sony Ericsson Update Service from here -> http://www.sonyericsson.com/cws/sup...ed/updateservice/xperiax10minipro?cc=gb&lc=en
2- Install it !
3- Run it !
5- Click on "I agree all..." and then next.
4- On the home page of the software, select "X10 mini pro" and click on next !
5- Turn off your phone and remove your battery.
6- Wait 30 seconds x)
7- Plug your usb cable in your computer but not yet in your phone !
8- Replace your battery !
9- Press and hold "Back" button (the 3rd physic button) !
10- Plug your usb cable into your phone !
11- Let's SEUS doing his work !
12- When it says "Finiiiiish !!!", unplug your usb cable and boot your phone !
13- Go to Settings -> About the phone and check if your Firmware is : 2.1.1.A.0.6 !
14- Root your phone.
15- Install xRecovery with K><A method !
16- After, download the ROM you want, place it at the root of your SD card.
17- Reboot into xRecovery and choose "install a custom.zip"
18- Select the .zip of your ROM and apply
That would fix your problem if you follw my instructions
This worked
Why is that? is the version you linked an older one?
Thingamajig said:
This worked
Why is that? is the version you linked an older one?
Click to expand...
Click to collapse
I am pretty sure you didnt have right baseband and xrecovery.
Please sticky this thread mods. Its one of the best tutorials i have seen so far.
Thanks guys for helping him
Sent from my U20i using XDA Premium App
No worries
I linked the latest version.

[TUT] Install CWM Recovery and a Rom in x10 mini pro

PLEASE CORRECT ME IF ANYTHING IS WRONG
I do not take any responsibility if you break your device, ask sony to make them easier to update.
Suggestions about roms and kernels are welcome.
1- REQUIREMENTS
Check in Settings -> About phone
there should be
Baseband: M76XX-TSNCJOLYM-53404015
Android: 2.1.1.A.0.6
- Check out if you are root with Root Checker
https://market.android.com/details?id=com.joeykrim.rootcheck&feature=related_apps
- If not, to root you can use this
[APP]SuperOneClick (Root, Unroot, Enable Non-Market App)
http://forum.xda-developers.com/showthread.php?t=803682
Before using it, in android start Settings from the app-menu. Tap Applications > Development > USB debugging. Accept warning-popup by tapping OK.
- Make backups of your things with some app like Titanium Backup or mybackup
- Install Busybox Installer from market and open it
https://market.android.com/details?id=com.jrummy.busybox.installer&feature=search_result
- Install a root file manager (so you can see and modify system files) like
Root Explorer
- Check if your hardware keyboard language layout is supported
Hardware Keyboards | Sony Ericsson Keyboards
http://forum.xda-developers.com/showthread.php?t=982341
- if not, you will need to copy and send to that forum your language files
"I need to the following from you guys so we can make the hardware keyboard work:
your qwerty.kcm.bin and your qwerty.kl from your old Sony Ericsson Firmware (in /system/usr/) i need the entire folder with keyboard-config, keyboard-chars etc..
List your buttons and which button should have which character on blue/sym button and if you need capital letters as well which key should appear on blue/sym and shift button press
List you special signs, like underscore, plus,minus, etc .. even if you need a key frequently which is not on the default keyboard layout from sony we can still place it on a different button suitable for you
and last but not least any special requests, like numbers or so in the wrong place.
If you want to have an exact copy of your hardware keyboard as it is on your device (like the blue letters and number) please post a picture
As for many of you having troubles with "shift" key not working. Touch the text input window and hold you finger on it until a menu appears, choose android keyboard and NOT the HTC one I don't know why but "shift" key will work again"
2 Install a RECOVERY
[RECOVERY] ClockWorkMod Installer
Get it here: http://forum.xda-developers.com/showthread.php?t=1257701
Usage from a Windows computer:
You need to set your phone in Debugging Mode.
Connect your phone to your computer
Open up install.bat and follow the instructions inside that.
Usage from a Linux computer:
Requires your phone to be ROOTed but there is now a ROOTer for Linux that can ROOT your phone if not already done. Can be found in this forum.
You need to set your phone in Debugging Mode
Connect your phone to your computer
Open up terminal
Go to the directory it is extracted to
Start the installer by typing "sh cwm-x10minipro.sh"
3 USE CWM to make a backup of everything:
-Power off phone
-When booting your phone and when the 'Sony Ericsson' letters appear, press and release continuously the 'back' button.
Once you are in the CW recovery, use the volume keys to navigate upwards / downwards, the 'home' or camera button key to select, the 'back' key to go back.
- Make a backup of everything
- Reboot normally, connect the phone to the pc, and copy everything inside the sd card to the pc
4 WITH FULL BATTERY DELETE EVERYTHING AND INSTALL A NEW ROM USING CWM:
DO THE THINGS MARKED WITH *RED
When booting your phone and when the 'Sony Ericsson' letters appear, press and release continuously the 'back' button.
Once you are in the CW recovery, use the volume keys to navigate upwards / downwards, the 'home' or camera button key to select, the 'back' key to go back.
We need to make a full wipe:
ADB root shell
reboot system now
apply update from sdcard
*wipe data / factory reset
*wipe cache partition
install zip from sdcard
backup and restore
backup (also backs up ext partition and installed apps to sdcard)
restore (also restores ext partition and installed apps to sdcard)
restore from xRecovery (Use this in case you want to restore backups done with xRecovery)
advanced restore
mounts and storage
*UNMOUNT ALL OF THESE:
*mount / unmount /cache
*mount / unmount /data
*mount / unmount /sdcard
*mount / unmount /system
*mount / unmount /sd-ext
*mount / unmount /cache
*FORMAT ALL OF THESE:
*format /cache
*format /data
*format /sdcard (not really needed)
*format /system
*format /sd-ext
mount USB storage
advanced
reboot recovery
*wipe Dalvik Cache
wipe Battery Stats
report Error
key Test
*partition SD Card
*Ext Size 512MB (formatting as ext4)
*Swap Size (Set this to 0)
*Rest Size is for vfat
fix permissions
validate recovery
restore recovery
*power off
- After you power off, take the microsd card and put it in a card reader, and connect it to your computer.
(Or you could connect the phone by usb and from CWM go to mounts and storage -> mount sdcard)
- Put inside the big FAT32 partition, the rom-u-want-to-install.zip, it must be CWM compatible
Here you can get some info about some of the latests roms:
http://xperiaminicyanogen.wordpress.com
- go to CWM and do install zip from sdcard
leave it finish and reboot after a bit
SOME OTHER USEFUL LINKS
- Once you finish installing a new rom, you can use this app in Window$ to set up your Hardware Keyboard to your preferred supported language:
[APP] Hardware Keyboard Language Setter KeyboardSwitcher.zip
program so you can switch your Phone's Hardware Keyboard with just two clicks on the PC.
http://forum.xda-developers.com/showthread.php?t=1113863
Compilation of useful links
http://forum.xda-developers.com/showthread.php?p=9219329
[FAQ] CUSTOM Cyanogen Froyo General F.A.Q.
http://forum.xda-developers.com/showthread.php?t=1066824
[GUIDE] Unlock bootloader & relock bootloader | X8 | W8 | X10 mini | X10 mini pro
http://forum.xda-developers.com/showthread.php?t=1254225
Apps Sony
Xperia Arc Timescape (Retail Dump)
http://forum.xda-developers.com/showpost.php?p=11904220&postcount=3
SE Backup & Restore
http://forum.xda-developers.com/showpost.php?p=11908011&postcount=4
[TUT] From stock ROM to custom ROM for n00bs (X10 mini pro) by Emperor.dk
http://forum.xda-developers.com/showthread.php?t=1194499
Awesome and mostly right!
But there is one thing I don't understand: if you managed to install xrecovery and know how to use it, why do you need cwm??? Either install that rom with xrec, or with cwm.
Anyway it's really good!
I read somewhere that clockwork recovery was better and more complete, and that it seems the way to go. Is that right? I wish there was an easier way to instal it. In other phones you can instal it from rom manager app, maybe in the future they support this phone also.
devrruti said:
I read somewhere that clockwork recovery was better and more complete, and that it seems the way to go. Is that right? I wish there was an easier way to instal it. In other phones you can instal it from rom manager app, maybe in the future they support this phone also.
Click to expand...
Click to collapse
i think you should make a video and post it up on youtube; i cant seem to find a in depth tutorial on how to do it (in english anyways). Id like to make sure the complete process before beginning because im afraid of what may happen (people referring it to bricking the phone)
@nilseby: here an answer from slade giving the reasons:
http://forum.xda-developers.com/showpost.php?p=14600846&postcount=1978
tranced_ said:
@nilseby: here an answer from slade giving the reasons:
http://forum.xda-developers.com/showpost.php?p=14600846&postcount=1978
Click to expand...
Click to collapse
Oh, yea? Well thx, now i realized xrec is even better than I thought! So I have no reason why to install cwm ( i never did )
So theres not any benefit of running cwm over xrec?
If anything is wrong please correct it.
It works perfect for my taste is better than Xrecovery.
Who comes to Xrecovery that delete xrecovery.tar in system / bin
aLeex10 said:
It works perfect for my taste is better than Xrecovery.
Who comes to xrecovery that delete xrecovery.tar in system / bin
Click to expand...
Click to collapse
Thanks, that is a problem that both conflict. Best way would be to use cwm only, but I could not find an easier method. I will update the instructions. Maybe installing rom manager app by slade darkness and co?. it is not finished, but it lets you instal cwm
Finally, there is a new app to instal the recovery you want with just a click, seek it on the dev thread
Every recovery you want , check my signature
D4rKn3sSyS said:
Every recovery you want , check my signature
Click to expand...
Click to collapse
Just bought a SE X10 mini pro. Rooted via the one click app.
Want to install CM7
tried all the apps (Rom manager(appstore and here from the forums), d4 recovery installer)
The auto-install apps don't really seem to do anything.
The 'Install xrecovery' options don't actually install it. Clockwork installs the old version 3.0.0.8 if anything (from the market rom manager).
The rom manager app from xda downloads and seemingly installs clockworkrecovery mod / says so in the notifications, but doesn't seem like it really does. I can't boot into it by pressing the back button at the SE writing (before or during)
I did manage to install xrecovery-mini 0.11 via a root file manager and boot into it, but the options didn't match the FAQ for http://forum.xda-developers.com/showthread.php?t=1117713, so I ended up screwing up and reflashing via SEUS.
Could someone please point out what I was doing wrong (or how to flash the CM7 image and then the hotfixes via xrecovery-mini), or maybe if there's really point and click app that works to do the xrecovery/cm mod parts without me screwing things up.
gaah... Installed clockwork recovery mod 3.2.0.0 but when I try to install the CM7 rom it tells me off saying Amend scripting is no longer supported/switch back to edify scripting etc.
What exactly should I do to install the rom ?
(oooh wait, it says to use xrec , fail )
but it is old, the new cwm is with apk install! C:
sure, much more easy now. I updated it, I will try to post the links to rom manager and recovery installer apps
cwm recovery vs xrecovery
I tried installing xrecovery. I should say I succeeded in installing xrecovery, it installed, and worked fine except no bootscreen when I turn the phone on. All 3 green checks showed up, but nothing happens.
Phone is rooted
busybox installed via busybox installer which shows the phone is rooted and the version of busybox.
All files (changemon, busybox and the tar files) in /system/bin with permissions set to rwxrwxrwx.
Am trying to figure out how to instal cmw recovery instead of xrecovery... not much luck so far.
Advice appreciated!
Hello, 1st post criticize me! LOL
I'm trying to figure out the same...
I'm totally new here and I'm trying to install the CWM Recovery.
it says: "Download and instal the recovery installer apk by darknessys"
when I look the installer it is not compatible with stock roms.
which method should I use to install the CWM recovery?
Ummm download this http://www.4shared.com/file/KQf9bym2/AAIS.html
Extract aais.zip to /sdcard
goto terminal emulator and give following commands
su
cd /sdcard/aais
sh install.sh
Click to expand...
Click to collapse
choose ur option and enter the number of the option
only for mini pro as of now!
So recovery installer apk by darknessys or rom manager apk, both can not be used on stock eclair rom? can anyone confirm this?
Edit- it seems that those apps don't support stock rom, that is weird, I thought they would work, try at least with darknessys recovery installer.
if not, the easiest way for now I guess would be to install xrecovery and then cwm.
So if someone knows how to easily install cwm on stock rom, please advise.
I don't know if what galvic suggests works or what it does, but you can take a look to the script.
Getting crazy
I tried now several things from here and Google to get this CWM recovery to work... no success!! Got a new x10 mini with latest SE Update...
Please does anybody know a working way to get this thing to work???
Frustrating

[CWM] Nexus Q Factory Image

For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
EDIT 1: REUP'D CWM mod
EDIT 2: reordered process to make more sense
Method:
1. Download the Beta CWM mod from rootzwikis credit to birdman EDIT:REUP'ED http://d-h.st/Fdp
2. Using fastboot, DO NOT FLASH Clockwork mod just use the syntax
"fastboot boot 'File path of clockwork mod image'
Note* this will boot directly into the recovery without permanently writing to the recovery and boot partition on the eMMC on the Nexus Qs board
3. Download the posted CWM factory backup posted
4. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup while in CWM recovery
*The device should show up in "adb devices" while in the CWM recovery*
5. *TEXT WILL BE REALLY SMALL! Now navigate with the Scroll wheel to backups and restore and tap the mute button to select.
*IF SOMETHING IS SELECTED IN ERROR THERE IS NO BACK BUTTON JUST REBOOT AND REDO FASTBOOT BOOT*
6. Now select restore and select the image folder
7.blah blah CWM Freaking MAGIC
8. Your Q is back to factory state
If someone wants to PM me or show me how to package this in a nicer CWM zip to install with a script let me know
http://d-h.st/yeo
*Note* I am NOT responsible if you brick your already bricked Nexus Q*
You sir get a beer, since my 2nd (dev) Q won't arrive until later this week, and mine was a shot put until this post.
If you happen to be in NYC before I move to SF, you get three beers.
Hoppy ones.
I am moving to SF
Did the reflash go smoothly?
fiveipads said:
I am moving to SF
Did the reflash go smoothly?
Click to expand...
Click to collapse
No unfortunately it didn't--I blew away all partitions other than bootloader so I can't, to my knowledge at least, push the zip since I can't adb.
I've got factory recovery, boot, system imgs but the system img won't push out because of fastboot's apparent inability to handle files that large (1GB exactly I believe).
...I guess I have to patiently await my second Q but the point of having two was to *use* one and have one for dev... rather than have one as a heavy reminder of my overzealous endeavors...
Hopefully I can give it more time while on this SF trip...
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Does our Q's have internal memory.. if not wouldn't it be possible to run back up of off otg memory stick if recovery would support it
Sent from my Galaxy Nexus using xda premium
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The problem I'm having is that ADB is not responding from CWM... at least not on a Windows machine. The drivers are fine as ADB was working in normal mode before my issue sprung up.
EDIT: As suspected Virtual Ubuntu on a Win host didn't see the device, Physical Ubuntu had no issue. NQ reloaded.
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Can we do this by say pushing the file to the download folder and then installing from zip?
And i know slightly off topic but once we've installed some apks for example, what's currently the best interface to use to navigate through the apps and use them?
How do I make a directory on Nexus Q
fiveipads said:
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
Method:
1. Download the posted CWM factory backup posted
2. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup
http://d-h.st/yeo
Click to expand...
Click to collapse
In step 2 you say make a directory for the file that is posted below. How do I create a directory on the Nexus Q? Currently my Q is stuck in a bootloop after trying to launch CWM from a Galaxy Nexus. If you could post command codes that would be awesome!
I figured it out. You can just follow step #4 and in CWM you can push the CWM Factory img to the /sdcard/Download/ folder and use CWM to unzip and launch.
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
discoltk said:
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
Click to expand...
Click to collapse
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
WildSatchmo said:
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
Click to expand...
Click to collapse
Me as well...not sure why I got this damn thing...lol
The edit didn't prompt an email to me even though I'm following the thread, so those of you looking for the clockworkmod beta image please take note that OP was kind enough to provide a working link to the image.
Thanks fiveipads!
Can someone post full backup please?
caioketo said:
Can someone post full backup please?
Click to expand...
Click to collapse
The link at the bottom still works for me...
http://d-h.st/yeo
..
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
UKROB86 said:
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
Click to expand...
Click to collapse
BUMP.. stuck in CWM unable to get a restorable file.. no idea why...
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Lokifish Marz said:
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Click to expand...
Click to collapse
The problem with putting Quantum singularity project on is that I can't turn on ADB debug, because i use a bluetooth mouse and keyboard, don't have an OTG mouse/keyboard, so somehow I need to be able to connect with adb to setup a bluetooth connected mouse/keyboard
I was thinking to install stock image, and then without wiping install Quantum SIngularity Project over top to preserve the settings for usb debug, on.
what's confusing to me is that i've restored the stock image many times before, and never had a problem.. that's why im wondering what the problem is.. if im typing something wrong.
I used the OneClickRestore as you said, and im just booting it up now
EDIT: didn't get past boot logo, i'll try again
So just to confirm this OneClickRestore is loading the stock nexus Q img right? I've never used it before I usually manually do it
EDIT: still stuck at the nexus q logo before home screen
do you see any error in my commands of trying to push the stock img folder (original post) to "/sdcard/clockworkmod/backup" ? I've done it many times before never had a problem

can not access to play store

something strange just happened
on my rooted nook tablet i can't access to google play store
it say "you must add an account to the device to continue. do u want to add an account now"
and when i click on YES it closes everything and goes back on the main screen
and also Gallery - Email - Talk have the same icons with the android logo
is this related to the fact that the software has been updated to the new version 1.4.3?
should i root it again?
thanks a lot
WhiterabbitITA said:
is this related to the fact that the software has been updated to the new version 1.4.3?
Click to expand...
Click to collapse
Yep. Reroot using the sdcard method and everything should go back to normal. A system update breaks root as it modifies the /system/apps/ directory which is where superuser/google play are stored when rooting.
helpppppp
i was trying to reboot using that method
http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14
i need help because something went wrong
Instructions:
Download the packages listed in the download folder, and extract them to your desktop.
extract ALL the files from the single zip.
NOTE: Do not extract the .zip with superuser and su.
Open the image flasher .exe, and browse for the .img that you extracted from the same zip
Put your SD Card into your nook or reader, and select the drive letter from the drop down on the right.
Press write, and wait
Once it has completed open the SD Card from the Windows browser and place the .zip in the root of the SD card.
Turn your Nook off.
Turn your Nook on while holding both the N+Power button. Your device will turn on, and then turn off after holding it.
NOTE: Do not let go of either button until your device has powered on and off again.
Put the SD Card into your nook.
NOTE: If it is already in there eject it and then put it back in.
Power your Nook on normally.
You will see a picture of N on the screen followed by a box with a white background followed by CWM booting up.
Select flash update.zip.nothing like that on the menu
i have rebbot system, install zip from sd card and selecting YES goes to Installation aborted
what to do?
Select Select from SD card.
Select your .zip
Reboot device
NOTE: Remove the SD card after your device reboots as if you don't it will continue to boot from the SD card.
I think I'm having this same problem.
WhiterabbitITA said:
i was trying to reboot using that method
http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14
i need help because something went wrong
Instructions:
Download the packages listed in the download folder, and extract them to your desktop.
extract ALL the files from the single zip.
NOTE: Do not extract the .zip with superuser and su.
Open the image flasher .exe, and browse for the .img that you extracted from the same zip
Put your SD Card into your nook or reader, and select the drive letter from the drop down on the right.
Press write, and wait
Once it has completed open the SD Card from the Windows browser and place the .zip in the root of the SD card.
Turn your Nook off.
Turn your Nook on while holding both the N+Power button. Your device will turn on, and then turn off after holding it.
NOTE: Do not let go of either button until your device has powered on and off again.
Put the SD Card into your nook.
NOTE: If it is already in there eject it and then put it back in.
Power your Nook on normally.
You will see a picture of N on the screen followed by a box with a white background followed by CWM booting up.
Select flash update.zip.nothing like that on the menu
i have rebbot system, install zip from sd card and selecting YES goes to Installation aborted
what to do?
Select Select from SD card.
Select your .zip
Reboot device
NOTE: Remove the SD card after your device reboots as if you don't it will continue to boot from the SD card.
Click to expand...
Click to collapse
Hopefully, someone can help me with this, as I seem to be having a similar problem. I am familiar with how to root the nook tablet, and have done so already, but since then, I believe the firmware updated, breaking my root. I am afraid to do it again, because when I first rooted the tablet, a game on it didn't work properly, and only worked properly after the update. Will this new root process cause any existing games to stop working? And how do I then prevent future firmware updates from breaking my root, again?
RooterBooter said:
Hopefully, someone can help me with this, as I seem to be having a similar problem. I am familiar with how to root the nook tablet, and have done so already, but since then, I believe the firmware updated, breaking my root. I am afraid to do it again, because when I first rooted the tablet, a game on it didn't work properly, and only worked properly after the update. Will this new root process cause any existing games to stop working? And how do I then prevent future firmware updates from breaking my root, again?
Click to expand...
Click to collapse
simple answer for avoising breaking root is to install a custom rom
Sent from my Nook Tablet CM7 BETA using xda premium app
RooterBooter said:
Hopefully, someone can help me with this, as I seem to be having a similar problem. I am familiar with how to root the nook tablet, and have done so already, but since then, I believe the firmware updated, breaking my root. I am afraid to do it again, because when I first rooted the tablet, a game on it didn't work properly, and only worked properly after the update. Will this new root process cause any existing games to stop working? And how do I then prevent future firmware updates from breaking my root, again?
Click to expand...
Click to collapse
or install custom recovery (cwm) if you wish to continue to use stock
without stock recovery B&N can't send you updates
How do I tell if I'm using stock recovery or custom recovery?
tobdaryl said:
or install custom recovery (cwm) if you wish to continue to use stock
without stock recovery B&N can't send you updates
Click to expand...
Click to collapse
I used Albert Wertz's method for rooting using an sd card, and had no problems, except that I didn't go as far as to block the OTA updates. Is it possible to have a custom recovery and stock recovery on the same device? How do I tell, and how do I safely install cwm, without being able to use Titanium Backup (since my root is now broken)?
deleted because of multiple posts linked.
I have now booted into mac instead of ubuntu in an attempt to fix.
Looks as if I got caught in xda update!
It's still not correct but better now.
WhiterabbitITA said:
i was trying to reboot using that method
http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14
i need help because something went wrong
Instructions:
Download the packages listed in the download folder, and extract them to your desktop.
extract ALL the files from the single zip.
NOTE: Do not extract the .zip with superuser and su.
Open the image flasher .exe, and browse for the .img that you extracted from the same zip
Put your SD Card into your nook or reader, and select the drive letter from the drop down on the right.
Press write, and wait
Once it has completed open the SD Card from the Windows browser and place the .zip in the root of the SD card.
Turn your Nook off.
Turn your Nook on while holding both the N+Power button. Your device will turn on, and then turn off after holding it.
NOTE: Do not let go of either button until your device has powered on and off again.
Put the SD Card into your nook.
NOTE: If it is already in there eject it and then put it back in.
Power your Nook on normally.
You will see a picture of N on the screen followed by a box with a white background followed by CWM booting up.
Select flash update.zip.nothing like that on the menu
i have rebbot system, install zip from sd card and selecting YES goes to Installation aborted
what to do?
Select Select from SD card.
Select your .zip
Reboot device
NOTE: Remove the SD card after your device reboots as if you don't it will continue to boot from the SD card.
Click to expand...
Click to collapse
From main menu (first screen after cardboard box)
select - install zip from sdcard
next -
select - apply /sdcard/update.zip
next -
N down and select YES
---------- Post added 15th August 2012 at 12:16 AM ---------- Previous post was 14th August 2012 at 11:36 PM ----------
RooterBooter said:
I used Albert Wertz's method for rooting using an sd card, and had no problems, except that I didn't go as far as to block the OTA updates. Is it possible to have a custom recovery and stock recovery on the same device? How do I tell, and how do I safely install cwm, without being able to use Titanium Backup (since my root is now broken)?
Click to expand...
Click to collapse
No, there is one partition designated for recovery. You can run cwm from sdcard when you wish and keep stock recovery internal, but custom recovery is the only way I have seen that absolutely blocks otas (otas are blocked with custom rom also) if that is your concern. To tell about your recovery the only thing I can think of is the power and N key into recovery. If you read what is presented on the screen when it appears and refuse a reset you are safe, that takes care of stock, if you are nervous reread and take your time. For cwm if that is installed you will see a cardboard box flash and then a menu with the first item to reboot, that is also safe.
To get into either recovery (for looking) from power off press and hold power and N, after two seconds release power, after one or two more seconds release N also. That should do it.
If you wish to have absolutely what to click when you get stock recovery just wait a while and I'll come back and edit this post to reflect that info. At the moment have something else going on (NT) I can't stop.
Stock recovery shows Factory reset
do you want to reset your device to the factory default?
Press POWER key to exit
Press Home key to continue
press power and you are out and safe
Installing CWM recovery! There are now two apps(they require root) here on xda for that purpose, one is 16gig only (Nook Tab Recovery Flasher) by indirect the other is 8gig and I don't know who did it.
There are also flash zips for each and a flash zip that is both 8gig and 16gig. If you are 8gig make sure you choose one for 8gig
CWM sdcard with a flash zip does not require root.

[Q] [Help] build.prop editing caused bootloop, no usb cable, stock recovery

Hi folks
I hope I am not breaking any rules. I tried my best to read up on the problem and see if it's already been fixed. So far I haven't encountered anything which is specific to my needs, but I learned enough to pose a well-formed question.
Phone: Samsung Galaxy SIII International (GT-I9300)
ROM: Stock Samsung, version 4.1.2, the update with Multi-window. Do not have the exact build number unfortunately.
Root status: Rooted
Recovery: Stock recovery. (I JUST rooted the phone, nothing else.)
So the problem is:
1. I used ES File Explorer in root mode, mounted /system as writable, and made an edit to build.prop (added "qemu.hw.mainkeys=0" to the end of the file to enable navbar) and saved the file. I rebooted the phone and now it is stuck with a looping Samsung logo.
2. I have made a backup of build.prop and placed it in /sdcard/ but unfortunately I haven't made a copy on my PC. Also note that I don't have an external SD card, I am using the 16GB space that came with the phone. So the build.prop backup is on the phone.
3. I do not have a USB cable (I have one that has a loose connection somewhere and my phone is not detected 99% of the times I've used that cable)
What I have found after 2 hours of searching online:
1. Factory Reset through recovery (I am able to boot into stock recovery by doing Vol Up + Home + Power) will not restore /system partition so that won't fix this.
2. ES File Explorer might have messed up the file permissions of the build.prop file.
3. I can use PC ODIN to flash the stock firmware (I might lose data but at least the phone would be back to normal).
4. I can use adb to push a good build.prop file and set the correct permissions (my most fav. set of instructions are from here: http://forum.xda-developers.com/showthread.php?t=1660596 Of course I got the idea from several other threads)
5. I can sideload a good build.prop file that someone might be generous to provide me using adb.
I don't have a data cable, so you can see how that Might be a problem. What I DO have is a USB OTG cable and a pen drive. Now, in the stock recovery, I noticed an option "apply update from external storage". Assuming I have an update.zip with the proper build.prop in it, can I load the update.zip into a usb pen drive (formatted to fat32)? Does "apply update" here work for such zip files or is it only meant to be used for full firmware images? If so, can I just download the latest stock firmware and apply it from here without wiping the /data partition?
If I can get this resolved tonight I can get my phone up and running before tomorrow's work week. I will buy an USB cable ASAP (it's 12 AM here so going out to get it is not an option now). But even if I do, I still have 5 months worth warranty left and I'd like to stick with the stock recovery and avoid incrementing the flash counter altogether, despite Triangle Away.
Thank you very much for the help in advance.
Adb pull your backup» then push it back?
slaphead20 said:
Adb pull your backup» then push it back?
Click to expand...
Click to collapse
I don't have a working data cable, so I cannot connect to the PC. That was my first idea, though, thanks! I am currently reading about making an Update.zip. It's very unfortunate that I didn't note my firmware details after the OTA...
Just set permissions - use Properties in ES FE in root mode. RW. R.. R.. should work.
LenAsh said:
Just set permissions - use Properties in ES FE in root mode. RW. R.. R.. should work. If not try 777 for giggles.
Click to expand...
Click to collapse
I am unable to boot into the phone, it is stuck in a bootloop
I don't have a USB cable to use ADB. I don't even have a custom recovery. All I have is the stock recovery and the option to "apply update from external storage". I now remembered that I also have an SD card on which I can put an update.zip or the stock firmware. Unfortunately I didn't note down the firmware details after the last OTA from 4.1.1 to 4.1.2, so I don't know which one to download.
Can I use the option "apply update from external storage" to flash an update.zip or is that only meant for full firmwares? Thanks!
Oops - silly me.
You are running stock recovery - never use it but does it have a fix permissions option?
Failing that you may have to reflash the ROM. Stock recovery is very restrictive on what you can flash.
LenAsh said:
Oops - silly me.
You are running stock recovery - never use it but does it have a fix permissions option?
Failing that you may have to reflash the ROM. Stock recovery is very restrictive on what you can flash.
Click to expand...
Click to collapse
Fix permission option on the stock recovery? I don't think so, haven't been able to find it. Here are the options I have:
reboot system now
apply update from adb
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Interestingly, when I selected the last option, it had these 3 folders:
fota/
lost+found/
recovery/
I was hoping fota/ had the files from my last OTA update but nope.
I guess you are not sure whether I can flash an update.zip through stock recovery... so I just have to wait till I get my USB cable and try out some adb magic?
EDIT: I'm retiring for the day. Thanks for the suggestions @LenAsh and @slaphead20. I'm gonna buy a cable next week and try to set the permission to 644 (RW-R-R) using this thread as my reference (http://forum.xda-developers.com/showthread.php?t=1660596). Thanks for your suggestions, I will post back when this is all resolved.
In the meanwhile, please keep the ideas coming
PS: Oh wait, I am still curious. What is the worst thing that could happen if I try to flash an update.zip through stock recovery? I am very curious to see if it will work.
You could flash a later custom recovery (this one works well http://forum.xda-developers.com/showthread.php?t=2002953) via Odin and then fix permissions that way. Even if that doesn't work, you could then flash anything you like without having issues that the stock recovery presents.
EDit: still need a cable though...
Trouble is he hasn't got a cable, I had same thinking, that he could use the aroma file manager in philz but he's stuffed without a cable!
Possible to make an update.zip with just the build.prop in it. Copy it to a memory card and use recovery to flash it?
I would try that first.
Edit: i just remembered i have done that a few times with my htc desire. Was running clockwork mod though.
Its really easy, find a small flashable mod in zip format and delete all the mod files and copy your build prop in. Edit the updater script to just write your /system/build.prop.
Copy the zip to you mem card. Use a usb adapter in a pc, stick it in your phone and use recovery to flash from external sd.
And after typing all that i reread your post and your running stock recovery and i think you would need a signature or something on the zip so it would not work. Ooops.
Sent from my GT-I9300 using xda premium
Stock recovery won't let you flash anything much... so perhaps his only option is Odin. When he has a cable.
On a side-note, how can someone not have a USB cable of any kind kicking around??
LenAsh said:
Stock recovery won't let you flash anything much... so perhaps his only option is Odin. When he has a cable.
On a side-note, how can someone not have a USB cable of any kind kicking around??
Click to expand...
Click to collapse
Just edited my post
Sent from my GT-I9300 using xda premium
@LenAsh, @slaphead20, @ficti0n851
Hehe, yeah, I'm stuffed without a cable I lost it recently and I'm the only one with a recent phone. All my family members' phones use different cables.
Anyway, I managed to borrow a friend's cable and am currently downloading drivers for the S3. Once that's done I will use ADB to set the file permission and try rebooting my phone, failing which I will restore the backup build.prop, set permissions and reboot the phone. Failing which... well, maybe I'll reflash the stock firmware (I managed to find out the exact build details btw! )
I'll keep you posted, thanks for taking the time guys
--
EDIT:
ADB was a success! I got in and changed the permission to 644 and rebooted, done! Funny thing was that /system/build.prop file was not even there, there was only /system/build.prop.bak. I was not able to find my original backup on the sd card, but I copied the .bak file (probably generated by ES FE) and set its permissions and that worked. And now I have also have the software keys!
Thanks for your comments guys. This was fun!
----
EDIT 2:
For anybody else who has the same problem, I did it using the commands in these great ADB guides:
http://forum.xda-developers.com/showthread.php?t=1660596
and
http://forum.xda-developers.com/showthread.php?t=879701
Also, how do I edit the title of the topic? Want to add a [Solved] tag.
ficti0n851 said:
Possible to make an update.zip with just the build.prop in it. Copy it to a memory card and use recovery to flash it?
I would try that first.
Edit: i just remembered i have done that a few times with my htc desire. Was running clockwork mod though.
Its really easy, find a small flashable mod in zip format and delete all the mod files and copy your build prop in. Edit the updater script to just write your /system/build.prop.
Copy the zip to you mem card. Use a usb adapter in a pc, stick it in your phone and use recovery to flash from external sd.
And after typing all that i reread your post and your running stock recovery and i think you would need a signature or something on the zip so it would not work. Ooops.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hey, I know this post is from forever ago, but is there a chance you could explain this step by step for a noob?
I have got my phone stuck in a bootloop by fiddling with build.prop, and I have the original file before playing with it. I have a rooted device with custom recovery, so how I could I use minimal ADB to push the original build.prop located on my device (sdcard) to root/system??
---------- Post added at 11:11 PM ---------- Previous post was at 11:06 PM ----------
gautham_y said:
@LenAsh, @slaphead20, @ficti0n851
Hehe, yeah, I'm stuffed without a cable I lost it recently and I'm the only one with a recent phone. All my family members' phones use different cables.
Anyway, I managed to borrow a friend's cable and am currently downloading drivers for the S3. Once that's done I will use ADB to set the file permission and try rebooting my phone, failing which I will restore the backup build.prop, set permissions and reboot the phone. Failing which... well, maybe I'll reflash the stock firmware (I managed to find out the exact build details btw! )
I'll keep you posted, thanks for taking the time guys
--
EDIT:
ADB was a success! I got in and changed the permission to 644 and rebooted, done! Funny thing was that /system/build.prop file was not even there, there was only /system/build.prop.bak. I was not able to find my original backup on the sd card, but I copied the .bak file (probably generated by ES FE) and set its permissions and that worked. And now I have also have the software keys!
Thanks for your comments guys. This was fun!
----
EDIT 2:
For anybody else who has the same problem, I did it using the commands in these great ADB guides:
http://forum.xda-developers.com/showthread.php?t=1660596
and
http://forum.xda-developers.com/showthread.php?t=879701
Also, how do I edit the title of the topic? Want to add a [Solved] tag.
Click to expand...
Click to collapse
Bro, I got the same problem as you had, except that I have a custom recovery, and the original build.prop file, and a USB cable, but I still haven't figured out what to do completly. Can you please take a minute to explain this for a complete noob? You have probably forgot all about this, but I am shooting for this chance. :/
black_hawk1990 said:
Hey, I know this post is from forever ago, but is there a chance you could explain this step by step for a noob?
I have got my phone stuck in a bootloop by fiddling with build.prop, and I have the original file before playing with it. I have a rooted device with custom recovery, so how I could I use minimal ADB to push the original build.prop located on my device (sdcard) to root/system??
---------- Post added at 11:11 PM ---------- Previous post was at 11:06 PM ----------
Bro, I got the same problem as you had, except that I have a custom recovery, and the original build.prop file, and a USB cable, but I still haven't figured out what to do completly. Can you please take a minute to explain this for a complete noob? You have probably forgot all about this, but I am shooting for this chance. :/
Click to expand...
Click to collapse
Hey, are you still having problems or did you solve it yourself? Anyway... If you still don't know what to do, describe best what you did to end up in a bootloop. As far as I understand what your problem is, you should use your recovery to move the backup of the original build.prop file to the system folder.
I changed my phones build.prop and when rebooted it does not started and ended up in bootloop and when I searched for how to fix this problem it showed that clear all the data from the phone but nothing happened and when I tried to install custom ROM in my phone my pc is not detecteing my phone .so what should i do ?
@Rajsh90: pull out battery for some minutes, put it in, reboot into downloadmode. Connect with PC, start Odin and hope that a COM-flag colours. Flash latest firmware.

Categories

Resources