Database Info

[I9003] DEODEXING Method If Every Other Method Fails (Without Busybox)

This Method Is The method Used By Me For deodexing Gingerbread XXKPE .I used This Method Because I was Not able to install BusyBox (ie The cp command didn't Work.so I was not able to copy the deodexed files to phone .So That the phone did not boot,stuck at the booting time).
Use This Method If Every Method For Deodexing Fails.
Steps
1.) flash to new XXKPE gingerbread Rom
2.) Root Your Phone
3.) download xUltimate-v2.2.8 xUltimate-v2.2.8
Note: You can use the already deodexed files by downloading this link Download Deodexed System Files [COMPLETE] then Goto step 11
4.) Unzip xUltimate v2.2, and launch "Main.exe"
5.) If everything goes well xUlt should recognize the phone and make a connection. You now should see a list of options.
6.) Run option 1. After option 1 is done, run option 2.
7.) Now these well take a while. Run option 3.
8.) IMPORTANT: After you have run option 3
9.) Now run option 4, and wait.
10.) Exit xUltimate, and put the phone in USB debugging Mode
11.) Download QtADB_0.8.0_windows_with_libs.zip
QtADB_0.8.0_windows_with_libs.zip
12.) Open It QtADB (left side - Browse to the xultimate folder, Right Side System folder)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
13.) copy all the in the done_app folder to the app folder in the phone side
14.) type odex in the filter textbox (phone side) and you will see all the odex files.select all and delete them
15.) copy all the files in done_frame to framework folder in the phone side
16.) type odex in the filter textbox (phone side) and you will see all the odex files.select all and delete them
17.) Reboot
Note 1: Rebooting Will take some time .its due to the new caching of files
Note 2: If Copying Get Stuck At somewere ,NO PROBLEM just Recopy The files Until all files are copied

Forget deodoxed process, and thank you brother for This explorer for windows, and I searched a lot for something like this but didn't find any application.
Thanks....
Recycled comment.
Sent from my GT-I9003 using Tapatalk

Changed The Thread
Comments Starts From HERE
Recycling Threads

with this no need of busybox right ... good one thanks

kchdeepak said:
with this no need of busybox right ... good one thanks
Click to expand...
Click to collapse
Busy box is needed. But the busybox needed will be 1.16.2 (which will be installed automatically when you Root with SuperOneClick).this busybox version do not contain cp commands.But still you can Deodex

Unrecognized option: -splash:./jar/1.png
i get this error after selecting the 3rd option :-/

bajju123 said:
Unrecognized option: -splash:./jar/1.png
i get this error after selecting the 3rd option :-/
Click to expand...
Click to collapse
If you can't deodex the files the you can use the already deodexed files uploaded by Misledz
Download Deodexed System Files [COMPLETE]

checking....

@vivek... *waiting for phone___*
what to do?

xultimate procedure donr... bt when m going to open QtADB .. it ask for path.. when i place the xultimatum folder path... it repleis "There is no adb binaries here"...
what to do?

Aaditya2 said:
@vivek... *waiting for phone___*
what to do?
Click to expand...
Click to collapse
Flashed & Rooted ???
remove usb cable & connect again in debugging mode ??
Or it may be error in driver files
install kies or update it

Aaditya2 said:
xultimate procedure donr... bt when m going to open QtADB .. it ask for path.. when i place the xultimatum folder path... it repleis "There is no adb binaries here"...
what to do?
Click to expand...
Click to collapse
I think you havent even set up the ADB which is used for develpment & othe management of Android phones
I will provide the link
install the adb and the use Qtadb.exe
How To Set Up ADB/USB Drivers for Android Devices
So most people won’t have to use ADB (Android Debug Bridge) ever, but if you want to learn how or want to get a little more technical with your Android phone, here’s how to get it set up.
I. Setting Up The SDK
1. Download the Latest Android SDK from Google
Android SDK
2. Extract the Android SDK .Zip file to C:\AndroidSDK (this should name the new folder created AndroidSDK in the C directory.
3. On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
4. Plug your phone into your computer via USB cable (it needs to be on). It should say installing drivers if using Windows.
!UPDATE 12.01.09 – If using Windows 7 skip steps 4 and 5 and use this procedure instead.
5. After it installs the drivers, goto the Start menu and type cmd into the search bar (Vista or higher) or click Run then type in cmd (XP) to open the command prompt.
6. Type the following into the command prompt window (hitting enter at the end of every line):
cd\
cd AndroidSDK\tools\
adb devices
browse the C:\AndroidSDK\tools\ as the path whe QtADB asks

up to the 17th step all procedure done succesfully.... bt after rebooting my phone just blinked and stuck on startup screen..... what to do?... reply

Aaditya2 said:
up to the 17th step all procedure done succesfully.... bt after rebooting my phone just blinked and stuck on startup screen..... what to do?... reply
Click to expand...
Click to collapse
samsung galaxy SL screen Or the Boot Screen( Glowing SAMSUNG)??

samsung galaxy SL screen

Aaditya2 said:
samsung galaxy SL screen
Click to expand...
Click to collapse
have you tried the new method for deodexing
the recovery CWM method
try it using the zip file

hmmm... ok... thanx... trying dat one!!!!!!!

Thanks dude. Easy method for deodexing

vivekkalady said:
have you tried the new method for deodexing
the recovery CWM method
try it using the zip file
Click to expand...
Click to collapse
dat also not worked.... i want to deodexing with your method... plz help me....

my phone wont reboot. its boot loop i think. what should i do?

[MOD] Utter Chaos Kernel Boot Screens

Hello, Everyone.
I am just sharing my UC-Kernel Boot Screens! Please hit thanks if you like them
Instructions on how to put on your phone at the bottom. Credits to some guy in zedge that uploaded this wallpaper, i just did minor photoshopping.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
From akashsgpogi
First, you have to have UC-Kernel on your phone. Do not flash anything below if you are on different kernel.
UC-Kernel can be found here.
Read below on "how to have your own custom boot logo"
DooMLoRD said:
How to change bootlogo/bootscreen
Our kernel (v03 onwards) comes with its own bootlogo/bootscreen... but to enable that bootlogo/bootscreen u need to separately flash a file via ODIN...
This basically is based on what Skin1980 had posted to modify bootlogo...
[ how to enable loading custom bootlogo ]
first download modifier-XXKPQ-bootlogo.tar
check the md5hash of the file to ensure file integrity
reboot device into Download mode
connect to PC via USB cable
start ODIN
make sure that device is detected
click on PDA and select the file u downloaded
now click start
after flashing is successful the device will reboot
now flash our kernel!
[ how to have ur own custom bootlogo ]
this can be done ONLY after u flash the modifier
u need a 480x800 image and it has to be in JPEG format
the file should be called as logo.jpg and has to be saved in /mnt/.lfs/
thats it reboot device to see ur own logo
[ how to disable loading custom bootlogo ]
first download stock-XXKPQ-bootlogo.tar
check the md5hash of the file to ensure file integrity
reboot device into Download mode
connect to PC via USB cable
start ODIN
make sure that device is detected
click on PDA and select the file u downloaded
now click start
after flashing is successful the device will reboot
now custom bootlogo will be disabled!
[ download links ]
Modifier XXKPQ
MD5HASH: fd95a5097ec37911023b23df08f53fa4
Stock XXKPQ
MD5HASH: 0a2a8a45c4b44cbbf170e3b85ff748dd
[ troubleshooting ]
at first u may need to reboot 2 or 3 times to see our custom bootlogo
if even after flashing the modifier u are unable to see our custom bootlogo OR if u want to revert back to our bootlogo; then:
once device boots start RootExplorer
go to the folder /data/local/tmp/
delete the file uckernelbootlogo
reboot device
this will force the kernel to push our logo to /mnt/.lfs/
Click to expand...
Click to collapse
Tips:
1. its /mnt/.lfs/ not /mnt/.ifs/
2. You can use the move command in terminal emulator since .lfs is hidden
3. Save any .jpg to sdcard as "logo.jpg"
4. mv /sdcard/logo.jpg /mnt/.lfs/logo.jpg
5. Once logo.jpg is in .lfs, it seems it cannot be overwritten, you need to flash the modification again if you want to change boot screens.

Sir wheres the DL link..

nice work man

You can right click and save the pics above directly and use them as logo.jpg

STEP 1: Save the images and put them /mnt/.lfs/logo.jpg
STEP 2: Thanks inciongd for the awesome screens!!

superb buddy...

Added Reaper Themed Bootscreens in Tribute to DooM

inciongd said:
Added Reaper Themed Bootscreens in Tribute to DooM
Click to expand...
Click to collapse
Reaper creeps me out. Sticking to the grey droid. .

Nice work dude

pls add this also one to the op
i kept it simple

^^ Done man

@inciongd
sorry man i uploaded a png
this one is the jpg so pls reupload
http://i1223.photobucket.com/albums/dd504/Akash_Gupta/CM7/logo.jpg

No problem man

thanks, I picked the composite of the sgl screen and uc toon style reaper. using it on cm7 now

To change bootlogo again without flashing,
Delete the file /data/local/tmp/uckernelbootlogo
Reboot (a few times, till stock boot logo is pushed by kernel)
Then place the new boot logo.jpg to /mnt/.lfs/
Reboot

inciongd said:
Added Reaper Themed Bootscreens in Tribute to DooM
Click to expand...
Click to collapse
hahhahah...
thanks!

when I copy to there and it say no space!!! i have make it to 17kb also say no space pls help me

I impressed..
Nice Work)

leongwenjun said:
when I copy to there and it say no space!!! i have make it to 17kb also say no space pls help me
Click to expand...
Click to collapse
are you trying to do this on cm7 like me? if so, it's a bit of work to do it 'cause you have to flash other fw to do this and go back to cm7. if you're not, are you flashing the "extra" cfroot from the universal thread? if so, are you getting the image noise like you're supposed to?
---------- Post added at 10:19 PM ---------- Previous post was at 10:16 PM ----------
amit864 said:
To change bootlogo again without flashing,
Delete the file /data/local/tmp/uckernelbootlogo
Reboot (a few times, till stock boot logo is pushed by kernel)
Then place the new boot logo.jpg to /mnt/.lfs/
Reboot
Click to expand...
Click to collapse
this must only work on stock fw, since on cm7 all I see in that folder is immvibed.lck

leongwenjun said:
when I copy to there and it say no space!!! i have make it to 17kb also say no space pls help me
Click to expand...
Click to collapse
I have the xenoxmod rom 2.0 and it gives me the same error...
EDIT: i didn't flash the modifier first...
Sent from my GT-I9003 using XDA App

F350 838 recovery V2.1

This recovery work on f350 & d838
Install instruction :
1. recovery, f350 and 838 support the. premise is to root first
2.*Computer installed drivers
3. There are two ways to enter a temporary recovery
1. Boot the computer is turned on usb debugging, media synchronization MTP mode, the computer side run into recovery and run recovery.bat
2. Press the volume off state (not connected to the computer) + Connecting a computer to run a power fastboot screen after entering the recovery run recovery.bat
Download link :
https://www.dropbox.com/s/dtglfl6eutkpuv1/Pro2 Recovery V2.1.rar?dl=0
Mirror link special tanks @letschky :
https://www.androidfilehost.com/?fid=95864024717072173
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If the card does not move and the emergence of Android device manager to set unrecognized, load the driver on the link:
https://www.dropbox.com/s/aoyln91pnniqvrj/andorid driver.rar?dl=0

meshk said:
This recovery work on f350 & d838
Install instruction :
1. recovery, f350 and 838 support the. premise is to root first
2.*Computer installed drivers
3. There are two ways to enter a temporary recovery
1. Boot the computer is turned on usb debugging, media synchronization MTP mode, the computer side run into recovery and run recovery.bat
2. Press the volume off state (not connected to the computer) + Connecting a computer to run a power fastboot screen after entering the recovery run recovery.bat
Download link :
http://bbs.sonyue.com/forum.php?mod...YjZ8MTQxOTg3NzI0OHwyNDgwMjN8OTYxMTE=&mobile=2
If the card does not move and the emergence of Android device manager to set unrecognized, load the driver on the link:
http://bbs.sonyue.com/forum.php?mod...NTZkfDE0MTk4NzgxNzh8MjQ4MDIzfDk2MTEx&mobile=2
Click to expand...
Click to collapse
Hi,thanks for your work,but i found no Downloadlink!

letschky said:
Hi,thanks for your work,but i found no Downloadlink!
Click to expand...
Click to collapse
I tested not problem when download.what error when you download it?
I try upload in other host but you should wait because my speed internet is very low

You are the best my friend.

meshk said:
I tested not problem when download.what error when you download it?
I try upload in other host but you should wait because my speed internet is very low
Click to expand...
Click to collapse
I found not downloadlink,my chinese Language is bad hehe.
Thanks for the Answer.
---------- Post added at 03:02 AM ---------- Previous post was at 02:52 AM ----------
Ok,i download it with my Smartphone,this works.Thank you very much!

letschky said:
I found not downloadlink,my chinese Language is bad hehe.
Thanks for the Answer.
---------- Post added at 03:02 AM ---------- Previous post was at 02:52 AM ----------
Ok,i download it with my Smartphone,this works.Thank you very much!
Click to expand...
Click to collapse
Ok good luck
I upload in other host after upload i put the link in first post

meshk said:
Ok good luck
I upload in other host after upload i put the link in first post
Click to expand...
Click to collapse
I can upload for you and send the Download Link to you

letschky said:
I can upload for you and send the Download Link to you
Click to expand...
Click to collapse
Thanks please send me

I updates download link in dropbox.you use the new link download
And mirror link special tanks @letschky

I click the link but can't download.

I hope it works it can only test when I am at home
---------- Post added at 09:52 AM ---------- Previous post was at 09:50 AM ----------
yplim2300 said:
I click the link but can't download.
Click to expand...
Click to collapse
All Downloadlinks are working,i have testet!

Is it APK file?

yplim2300 said:
Is it APK file?
Click to expand...
Click to collapse
No you can read first post

Hi there, and thanks for the Recovery !
However, I wasn't able to install it (I could'nt understand the instructions, they are non readable in the .bat file).
Even though I have ADB and drivers installed on my PC, and USB debugging on, when I run the .bat file and click "1", it will boot in fastmode but then will be stuck at "wiating for device".
Am I doing something wrong ?
How did you manage to installl it guys ?
Thanks !

After pressing Enter I get the attached screen.
Unreadable.

liljom said:
After pressing Enter I get the attached screen.
Unreadable.
Click to expand...
Click to collapse
Can you connect the Phone with your Computer as normally?(MTP Mode)
This Recovery works fine for me.(D83810b Taiwan Version 466-92 and D83810f Taiwan Version)
Test a another Usb Port?

haw to enter in recovery mode? wath butons have to press? tnx
---------- Post added at 12:23 AM ---------- Previous post was at 12:18 AM ----------
liljom said:
After pressing Enter I get the attached screen.
Unreadable.
Click to expand...
Click to collapse
the same problem.... haw to enter in recovery?

ciobaneasca said:
haw to enter in recovery mode? wath butons have to press? tnx
---------- Post added at 12:23 AM ---------- Previous post was at 12:18 AM ----------
the same problem.... haw to enter in recovery?
Click to expand...
Click to collapse
Press number 3,this boot in recovery

so i can back up on my micro sd??

number 3 is ok . But if i want recovery again , i must connect PC and chosses number 2 ? Because when restart the phone need something : FASTBOOT....

[GUIDE] Enable Multi-Window Mode on Android 6.0 Marshmallow

There's a hidden feature in Android 6.0, multi window. It has its warnings:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So decide if this is actually for you before following these steps
It's not shown in user builds, so we have to do some messing. You'll either need root or a custom recovery to do this, but as not everyone wants root, here's how you do it with TWRP, a USB cable, and a PC with ADB:
1. Boot your device into recovery
2. Mount your system by going to Mounts > Tick System
3. On your PC open a command line, somewhere like your desktop is useful
4. Type the following command:
HTML:
adb pull /system/build.prop
5. Open the build.prop file with your favourite (decent) editor, I recommend using Notepad++ on Windows
6. Find the "ro.build.type" line
7. Change the text after = to "userdebug" from "user"
BONUS: If you want a nicer DPI here, change the line "ro.sf.lcd_density" to your preferred DPI
8. Save the file
9. Go back to the command line and enter the following command:
HTML:
adb push build.prop /system/
10. Now open a shell doing:
HTML:
adb shell
11. Now a adb shell will open, enter these commands:
HTML:
cd system
chmod 644 build.prop
12. Reboot the device as normal
13. When the device has booted, go to the developer options
14. Scroll down to the bottom of the "Drawing" category
15. Enable multi-window and have some fun!
If you're rooted...
1. Download "Build.prop editor"
2. Find "ro.build.type"
3. Edit it to have the value "userdebug" from "user"
4. Reboot when prompted
5. When the device has booted, go to the developer options
6. Scroll down to the bottom of the "Drawing" category
7. Enable multi-window and have some fun!

Worked ! Thanks
Such a shame the Keynote didn't introduce such feature, it's stable enough. Just think of the use of the feature on a 10" tablet.

works perfect thank you !

How do you use it after enabling?

Chahk said:
How do you use it after enabling?
Click to expand...
Click to collapse
Go recent menu, on the apps beside the x there's a button to choose the top half or second half.
Multirom users can go /data/media/multirom/roms/ and edit the build prop directly there, no need to use adb. I did it without using a PC

I flashed the latest hammerhead twrp with fastboot command, it was successful, but when I reboot bootloader and choose recovery, it keeps loads forever and sometimes the screen flashes black. I tried CWM after that, it said root needed. How do you guys got recovery on M?

Chahk said:
How do you use it after enabling?
Click to expand...
Click to collapse
I get how to use it, but how do you consistently pick the two apps that you want to appear?
---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------
elreydenj said:
I get how to use it, but how do you consistently pick the two apps that you want to appear?
Click to expand...
Click to collapse
It seems to be all over the place. I cant figure out how to always get the two apps that i want in multiwindow to show....

prwnd said:
I flashed the latest hammerhead twrp with fastboot command, it was successful, but when I reboot bootloader and choose recovery, it keeps loads forever and sometimes the screen flashes black. I tried CWM after that, it said root needed. How do you guys got recovery on M?
Click to expand...
Click to collapse
This is the wrong place to ask this question . Check your pm i have given you the solution and please ask your questions in the right thread next time onwards

is it possible to do that with Wugfresh Nexus Root Toolkit?

jonathanxx1 said:
is it possible to do that with Wugfresh Nexus Root Toolkit?
Click to expand...
Click to collapse
Nope. I tried doing the "push/pull files" and it didn't work. You can install custom Recovery with WugFresh then follow these instructions.

drgonzo712 said:
Nope. I tried doing the "push/pull files" and it didn't work. You can install custom Recovery with WugFresh then follow these instructions.
Click to expand...
Click to collapse
I tried also ,,and it doesn't work.

Adr990 said:
I got this message from ADB:
Anything?
Click to expand...
Click to collapse
Open terminal, type
su
cd system
chmod 644 build.prop
exit
and do stages again

Adr990 said:
When I do that, in adb shell:
Click to expand...
Click to collapse
Ow, i forgot ,my mistake sorry can you try this ?
cd system
chmod 777 build.prop
exit

damn.. is there a way to do it if it is a secondary rom on multiboot?

Adr990 said:
Oh and I also tried this:
Kinda wierd how it is not working for some, while we all flashed according to Google's adb flashing method.
Click to expand...
Click to collapse
Can you send your build.prop to me via pm. I can make a flashable zip for you

Hello people, I have multirom installed on my nexus 5, the primary rom is 5.1.1 (LMY48B), and my secondary rom is the developer preview MPZ44Q. I want to know if it's possible to enable multi-window mode since the M preview is installed as secondary rom.

I did it. Reboot into recovery. Swap the Roms. Don't reboot . reboot into recovery again from the reboot tab. Select multiboot tab just to ensure you are OK and the M ROM is the internal.. Mount system and do what the op says. Reboot into recovery again swap Roms again . reboot system and you should be OK. Takes like a half an hour to do though
PS. NEVER FIX SU. ALWAYS SKIP

I understood that if i try to install su on the M rom, it will result in bootloop. And my internal rom is stock ROOTED. So do you think it will work ?
When i will swap the roms, the fact that my primary rom is rooted, will it cause any problem ? Thanks in advance.

Nope my primary is still rooted. And I an typing this from my secondary M ROM with multi window enabled. All you have to do is never fix su for either ROM and never boot the system with M as your primary ROM and you are ok

Help me too
hsay said:
This is the wrong place to ask this question . Check your pm i have given you the solution and please ask your questions in the right thread next time onwards
Click to expand...
Click to collapse
This is the worst thing to do here but could u please guide me too to the recovery as i searched all i could but still got no answer. Even the Guys in the Discussion group had no answer. Please Help ME,.

Stuck in TWRP, cant connect via ADB, SDCard unavailable = Phone bricked?

Hello experts!
I followed this tut here https://www.youtube.com/watch?v=dTlosea6SJE to root my Sony Xperia Z5 phone and to use a costum ROM. Everthing worked, but after (~09:00 min.)
Code:
adb reboot bootloader
fastboot flash boot boot.img
[I]Okay[/I]
fastboot flash revovery recovery.img
[I]Okay[/I]
fastboot reboot
and entering TWRP (2.8.7.0) by pressing ON + VOL DOWN
I am stuck here.
- I cant get a connection from my PC to the phone, its not recongnized anymore in ADB (result blank) after
Code:
adb devices
- the extra SD card (in SD card slot) is not mounted and the TWRP-mount option dont let me select "Micro SDcard" or "USB OTG".
- I cant copy images or zips or any files to the phone plus I cant read data from the ext. sd card (fat32, 4096 bytes) when inserted in the phone.
Asking for help:
How can I mount the SD card via TWRP-Teminal ?
How can I adb connect the phone to my PC again ?
Any suggestions to reflash the phone ?
I really appreciate any help!
Thans a lot !
Superblond
P.S. sorry for my poor english ...

hold Vol Up and power button to soft reset, then flash your phone using flashtool and thats it
---------- Post added at 09:13 PM ---------- Previous post was at 09:06 PM ----------
i PMed you. if you need any help send me a message. Cheers

Power on + Vol up dosent work for me...nothing , black screen no vibration
L33Tgod said:
hold Vol Up and power button to soft reset, then flash your phone using flashtool and thats it
---------- Post added at 09:13 PM ---------- Previous post was at 09:06 PM ----------
i PMed you. if you need any help send me a message. Cheers
Click to expand...
Click to collapse
Hi & thx,
Power on + Vol up dosent work for me...nothing , black screen no vibration.
I will pm you...

Blue led on = not bricked !?
Connecting the phone to my PC via USB, with holding Volume up, brings up the blue LED.
But with
Code:
adb devices
the phone is still not recognized.
Dont know what to do next...
SB

[SOLVED] Re-flashing a ROM with TWRP only on phone
After failing to manually mount the SD-Card or a USB-Stick via OTG-cable through the Terminal with command line function, the xda-user L33Tgod gave me the (simple) tip via pm to use the flashtool and flash the phone with a valid ROM (again)... THX a lot L33tgod!
As a result, I can access my phone & my SD-Card again. Now I have a working ROM on my phone and I am no longer stuck in a TWRP-Menue only, without the chance to communicate with the phone via ADB etc.
So I followed the below how-to (nothing new, I know, but the solution for my problem)
Flash your FTF firmware file
This section details the steps needed in order to flash new firmware onto your Sony Xperia device.
First of all, open Flashtool and then click on the lightning bolt in the top left of Flashtool as highlighted below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Select “Flashmode” and click “OK”.
You should already be in the source folder where the FTF firmware files are located. If not, navigate to: “C:\Users\[Your PC Name]\.flashTool\firmwares”
Select the firmware build version that you want to flash from the “Firmware” pane. Ensure the device variant is the same as the model number of your Sony Xperia device.
If you want to retain your apps, data and media (photos, videos, music), then ensure that the “USERDATA” option within the “Wipe” pane is unticked. However, we recommend that when upgrading a major new Android version, a clean install is the way to go. In this case, tick all options under the “Wipe” pane. This will wipe all of your data though including your photos and videos, so please ensure you have these backed up elsewhere.
IMPORTANT – For FlashTool 0.9.19.10 and older: If you skipped Part 2 of the guide as you already had your own FTF firmware file, then you may see the following ‘SIMLOCK’ option ticked under the “MiscTA Exclude” pane. DO NOT untick SIMLOCK as it could lead to problems with the network lock on your device.
IMPORTANT – For FlashTool versions 0.9.22.0 to 0.9.22.2: The developer has changed the meaning of the tick box in newer versions of Flashtool, which means ticking the box includes “SIMLOCK”. Either way, you want to ensure you are NOT including SIMLOCK when flashing firmware. So to be clear, when presented with the “SIMLOCK” option below, you must NOT tick the box.
NOTE – For FlashTool 0.9.22.3 onwards: The developer has disabled “SIMLOCK”, which means you no longer have to worry about accidentally including it in your firmware flashing. The option is only enabled by entering ‘Pro’ mode. Unless you know what you are doing, then stay well away from Pro mode.
Click “Flash”. Flashtool will then indicate that it is “preparing files for flashing”.
You may have to wait around 60 seconds for the pop-up below to appear. Once it does, you should now connect your Sony Xperia device. Make sure the device is powered off and then hold the ‘volume down’ button whilst connecting the USB cable. Once the pop-up disappears and flashing has started, you can let go of the ‘volume down’ button.
Flashtool will then start flashing your Xperia device.
Once you see “Flashing finished” as indicated below, your Sony Xperia has been successfully flashed.
Congratulations you have just installed Android Marshmallow! Now disconnect your Xperia device and power on the handset. Don’t worry if it takes a while for the handset to boot, this is to be expected.
To confirm that you have upgraded the phone software, click on ‘Settings > About phone’, which will reveal your new Android version and firmware build number.
If you would also like to confirm the region firmware that you have downloaded, you will need to access the service menu option. To do this, open the dialler and enter the following: *#*#7378423#*#*
Then click ‘Service info > Software info’. The CDF is an eight digit number under the “Customization Version” that should tie in with the firmware you downloaded from XperiFirm. For example, you will notice below that the CDF (software customisation version) of 1298-7362 matches the same firmware that we downloaded in the XperiFirm screenshots above.
Thx to all the helpers !
SB