Related
So yesterday i flashed Cognition 2.2 Beta 6 on my Cappy, and then a friend flashed 2.1 Voodoo. So now i have Ryan's OCLF running and Voodoo 2.1. Whenever i start my phone up it just goes straight to recovery mode, then when i click reboot now it still goes to recovery. Tried using the 1 Click Return to Stock thing but my phone doesn't go into Download mode either. People this is my only phone... Please help... Oh and if you can't help me do you guys think ATT will return my phone?
timur525 said:
So yesterday i flashed Cognition 2.2 Beta 6 on my Cappy, and then a friend flashed 2.1 Voodoo. So now i have Ryan's OCLF running and Voodoo 2.1. Whenever i start my phone up it just goes straight to recovery mode, then when i click reboot now it still goes to recovery. Tried using the 1 Click Return to Stock thing but my phone doesn't go into Download mode either. People this is my only phone... Please help... Oh and if you can't help me do you guys think ATT will return my phone?
Click to expand...
Click to collapse
while in recovery, your phone will still respond to adb. simply "adb reboot download" will get you there.
NEVER EVER flash a 2.1 kernel when you a running a 2.2 firmware.
Where do i download ADB? and how exactly do i use this command line?
It's part of the Android SDK.
h t t p://developer.android.com/sdk/index.html (take the spaces out, I can't link yet).
You install the software, connect your phone by USB, open a command prompt, CD to <install folder>\tools, then type "adb reboot download".
If you can't get ADB to work.. you might want to try this trick,
Pull your Battery, Sim, External SDCard.
Hold down both Volume Buttons at the same time.
While holding down the button - put in your USB Cable
Jam the battery back in and the yellow triangle "should" pop-up.
Might take a few times to do it, but if you have your buddy with you (you know the guy who tried bricking your phone?) it should go into d/l mode.
timur525 said:
So yesterday i flashed Cognition 2.2 Beta 6 on my Cappy, and then a friend flashed 2.1 Voodoo. So now i have Ryan's OCLF running and Voodoo 2.1. Whenever i start my phone up it just goes straight to recovery mode, then when i click reboot now it still goes to recovery. Tried using the 1 Click Return to Stock thing but my phone doesn't go into Download mode either. People this is my only phone... Please help... Oh and if you can't help me do you guys think ATT will return my phone?
Click to expand...
Click to collapse
I don't think AT&T would replace your phone because you messed up flashing it. This voids your warranty.
There are a few ways to force download mode. Try avgjoegeek's method, it should work.
If the 3-button method doesn't work, you may be SOL. I had to return my phone that did not allow the 3-button method to work. It is a pretty common issue. Everyone should check to make sure their phone will go into recovery and download mode before flashing ROMs. This issue should be stated more in the ROM sections.
Good luck!
so yeah i got my first replacement after the first time this happened... i tried flashing krylon360's rom with odin but got a fail at factory.rfs. keep in mind i am in no way shape or form a noob with odin, i have brought many of my buddies' devices back to life, but for some reason even though i use a USB jig ( which works in my captivate and personally tested and working on the SGS4g before the unrecoverable soft brick) any help please i dont want to have to send it back to t-mobile again... they already charge 10bucks just for shipping.
muleman said:
so yeah i got my first replacement after the first time this happened... i tried flashing krylon360's rom with odin but got a fail at factory.rfs. keep in mind i am in no way shape or form a noob with odin, i have brought many of my buddies' devices back to life, but for some reason even though i use a USB jig ( which works in my captivate and personally tested and working on the SGS4g before the unrecoverable soft brick) any help please i dont want to have to send it back to t-mobile again... they already charge 10bucks just for shipping.
Click to expand...
Click to collapse
Hmm I'd say if the USB jig didn't work, you're not soft bricked. That's a hard brick.
What kind of USB jig are you using?
Was it a ROM or a kernel you flashed? which one, version etc.?
Jig - verified WORKING before the flash attempt
tried to flash [ROM-ODIN]T959VUVKB5 Stock + Root By: krylon360
new sgs4g
new USB cable
opened Odin first, set file
plugged in phone got a good port connection
clicked "Start"
failed at factory.rfs
phone--!--comp screen
unresponsive to JIG
donation rewards for anybody that can help! lol this is depressing, my old captivate isnt this sensitive and has been through hell and back, but this SGS4g.... im dissappointed in.
Uninstall all the drivers for the phone make sure you have the right ones also, and try plugging it into a usb 2.0 slot then run it again, this seemed to work for me. I ran into the same issue I plugged in my jig but it gave me a black screen, but odin recognized it and I flashedthe kd1 update and it was fixed. Hope this helps
muleman said:
Jig - verified WORKING before the flash attempt
tried to flash [ROM-ODIN]T959VUVKB5 Stock + Root By: krylon360
new sgs4g
new USB cable
opened Odin first, set file
plugged in phone got a good port connection
clicked "Start"
failed at factory.rfs
phone--!--comp screen
unresponsive to JIG
Click to expand...
Click to collapse
hold your horses... I got some news for you.
you can flash at that screen
try flashing mine again, or try white's ODIN image.
Along with what krylon said, maybe a bad download, try download file again
Sent from my SGH-T959V using XDA Premium App
will do thanks guys, ill try it tonight and let ya know how it goes for me.
i still dont get how odin gets a connection but the phone itself cannot with the jig... not logical but hey in the process of flashing now
krylon360 said:
hold your horses... I got some news for you.
you can flash at that screen
try flashing mine again, or try white's ODIN image.
Click to expand...
Click to collapse
youre the man.... Thanks much
muleman said:
i still dont get how odin gets a connection but the phone itself cannot with the jig... not logical but hey in the process of flashing now
Click to expand...
Click to collapse
Heimdall works at that same warning screen too. I've done it on my SGS4G.
I am confused..
sgyee said:
Heimdall works at that same warning screen too. I've done it on my SGS4G.
Click to expand...
Click to collapse
If the computer is not recognizing the phone being plugged in, how is ODIN going to be able to process? I don't know if mine SGS4G is irrepairable but when I plug it in to the computer, it will not even show up on device manager. The drivers have been installed in the past and I have used ODIN before.
When I try using ODIN now it won't work since it won't recognize the phone.
I have used JIG and simply will not buzz. It's pretty much as dead as if the phone is not even on.
Any help guys??
amishraa said:
If the computer is not recognizing the phone being plugged in, how is ODIN going to be able to process? I don't know if mine SGS4G is irrepairable but when I plug it in to the computer, it will not even show up on device manager. The drivers have been installed in the past and I have used ODIN before.
When I try using ODIN now it won't work since it won't recognize the phone.
I have used JIG and simply will not buzz. It's pretty much as dead as if the phone is not even on.
Any help guys??
Click to expand...
Click to collapse
If its currently in the state which I'm assuming..
-won't turn on, no sign of life period...
-plugging it in the wall charger won't even show the green battery status...
-won't get recognized when plugged into pc (or odin)...
-all combinations of buttons and battery pulling+usb cable plugging does nothing...
Yea I think its safe to say it went to a land far far away just like my friend's phone and only Samsung can revive it now.. Because I remember reading all the stories how everyone brought theres back to life so easily with the button combos or the jig usage, but those phones all at least showed a sign of life with that cable screen. But if its pitch black like I'm assuming then...
Same here. The jig didn't seem to work - I still got the cell + comp but odin worked anyway and reflashed stock. It's probably better to run Odin off a desktop if you have one.
That screen scared the holy hell out of me a couple of days ago. I ended up having to re-install the samsung drivers for windows 7 and then odin picked the phone right up. The reason I *knew* the phone was recoverable from that screen was simple, though:
I read the screen. It wouldn't be telling you to try something in Kies if you couldn't do anything at that screen. So, I just kept ****ing around trying different things until it worked.
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
That screen scared the holy hell out of me a couple of days ago. I ended up having to re-install the samsung drivers for windows 7 and then odin picked the phone right up. The reason I *knew* the phone was recoverable from that screen was simple, though:
I read the screen. It wouldn't be telling you to try something in Kies if you couldn't do anything at that screen. So, I just kept ****ing around trying different things until it worked.
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
Click to expand...
Click to collapse
I second this. I have been running into this screen while trying to install root from the 2.3.4 leak. I have had black screen, fuzzy screen, random pixel screen. In most cases I have been able recognize the phone using odin. A few of the key steps that I have used to get the phone recognizable in odin are:
1. If the computer says "usb not recognized" when initially plugging in the phone, uplug it and plug it back in. Most of the time when I do this the phone is recognized as samsung device.
1b: If odin now recognizes the phone after running through step 1 I will try to flash the files again. it will usually fail after trying to load the flash files on the first try. I have to mess around with this process a few times and I can usually get a successful flash.
2. I had an case when having to deal with this problem yesterday. I was running through steps 1,1b and not having success. Odin was hanging, (I forget which step). I let it sit for about 10 minutes and was still hanging. I unplugged the phone with odin still hanging pulled battery, powered on, plugged back in. Odin, which was still open and still trying to connect, continued its already started process after plugging it back in!!! This was an accident to still have the odin running and trying to connect, but after reconnecting the phone it successfully flashed!
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
Click to expand...
Click to collapse
These kind of observations are especially helpful! I can concur that I get the same <phone..!..pc> error, when odin tries to flash and gets a write fail, however, I do not have the "re-partition" option set. I then have to run through my previously mentioned steps to try to get a successful flash.
My question is what can i do to keep odin from failing to write when flashing?? I have only been using PDA packages, with the exception of using discrete packages (pit,csc,phone,pda) when loading the 2.3.4 rom leak.
It seems like the flashing write error in odin in causing the <phone..!..pc> error quite often with different flash processes. Does anyone have a solution to what might be causing this write error and what can be done to prevent this whole cycle? If so I sticky or new thread might be useful for other users. It has caused to have to warranty my first phone, urrrg!
Scariest feeling ever........ Not seeing your phone come up on Odin.
Sent from my SGH-T959V using XDA Premium App
Woops ahahahha. Was talkin to my friend. SOrry!
fvnktion said:
I second this. I have been running into this screen while trying to install root from the 2.3.4 leak. I have had black screen, fuzzy screen, random pixel screen. ..... [cut] ......
Click to expand...
Click to collapse
I had the same issue yesterday, when I tried to flash KD1 vanilla (stock) ROM
using ODIN, it failed the first 4 seconds, it boots into fuzzy looking screen and
that's it, every time I tried to boot it the fuzzy screen fades away to pitch black.
there is 2 possibilities that messed up the whole thing for me:
1) Bad ROM.. (i.e, can't be used with ODIN) although some members said it works
but don't know if there anything special to do before hand, if I want to downgrade.
2) Samsung Kies' fault, I installed just right before I used ODIN, and told me my
device is not registered.. hmm.
It could be both cases, but I suspect Kies the culprit, I had to uninstall it, and
uninstall the drivers came with it, installed the drivers found here in these forums,
and Odin recognized a COM port, although black screen on the phone, flashed
to KH1 and I am back to business. phew..
GB is awesome, but I can't stand the weak WIFI issue even with the latest KH1
I have to stand 3 feet away from my router to get a solid signal, with froyo
vanilla rom, I was able to connect like 50 feet away. but that's another problem
not for this thread.
Heh funny thing I read today in some thread, there is a conflict between Kies and
Odin after the incident happened. my fault for not reading a lot, jumping the gun
almost cost me the phone :/
Well, Ive been flashing roms for a while now and I have an issue with my captivate.
Lets start in the beginning. I had my captivate on THS ICS rom and It was going great. But my captivate isn't that great anymore. The power button is broken, but I was able to go around that. (Sidenote: It turns on when I plug in the battery.) Anyway, I wanted to go back to stock because I did have the right bootloaders. (I couldnt get into download mode with the button combination. I thought it was the bootloaders fault. Im I wrong?) I wanted to switch to I9000 bootloaders but I had to start fresh. But before all that, I noticed that while I was on ICS rom, I was unable to go to download mode. I used to before, but it magically disappeared (I know it didnt, I know I did something to it but I don't quite remember when it happened.) So I was unable to flash a new rom, if I wanted to.
A couple of days ago, I bought a jig and it worked! It took me straight to download mode. So I decided to get my Captivate and make it go back to stock. So I opened Odin, it found my Cappy and I clicked start. But, it stopped at factoryfs.rfs. I waited a half hour and nothing. So I unplugged it and now it won't turn on. But it can still go into Download Mode and be seen by Odin but it just wont finish. I tried both odin one click and the regular odin. I looked everywhere for more than six hours and nothing came up. Please guys, if anyone knows what I can do to fix it, please reply.
I might have missed something, but just ask if you need any more info. Please help me.
Edit: I forgot to add this:
While I was on the ICS rom, I switched over to CM7 to see if the process of going back to stock would be easier. Thats when I tried to flash stock. It didnt work as well as I thought it would.
And I knew that I didnt have I9000 bootloaders because I installed the Icy Glitch kernel and each time I tried to have DIDDLE on it would go to deep sleep mode and I was unable to wake it back up.
As long as you can get to download mode you are fine. Try flashing a different stock from. Or using Hiemdell
I've tried both odin and Hiemdell. But with Hiemdell, it would always tell me that I dont have the drivers installed. So, it installs it for me. Even with the drivers installed, it keeps telling me that I dont have the proper drivers installed.
I have had this exact problem, where a bricked captivate can get into download mode but when restored to stock through a one-click, it freezes on the factoryfs.rfs. However, in my case after freezing at this stage, the phone was completely inoperable, and could not even enter download mode, so I am suprised yours could.
What works for me is to remove the battery, wait for a few seconds, put the battery back in, use the usb jig to enter download mode, and then WITHOUT the phone plugged into the pc, download and open this one-click file http://http://forum.xda-developers.com/showthread.php?t=731989.
Once the odin one click is open, plug the usb cable into the pc, and then into the phone. This one-click has never failed me. Hope this helps.
Ok, now it passed. I don't know what I did but now its back up and running. But now it boots up into recovery. I can't select anything because my phone's power button is broken. What do I do?
Juiceboy125 said:
Ok, now it passed. I don't know what I did but now its back up and running. But now it boots up into recovery. I can't select anything because my phone's power button is broken. What do I do?
Click to expand...
Click to collapse
Depending on the CWM recovery you're in, you can sometimes use the search capacitive key to do the same thing as the power button will do.
I had the same problem you had with Odin stopping on flashing a file, turns out I was using a third party USB cable. I switched to the USB cable provided by Samsung when I bought my cappy and problem solved. Hope that helps.
Sent from my SGH-I897 using XDA
Finally!
Well, I got my Cappy up and running again. While I was stuck in the CWM I just decided to install Gingerbread using a One click and it worked. Now I'm back to CM9. Thanks guys for the suggestions. I guess I just needed to wait and double check everything.
So... I have a Nexus S And it was fine, Rooted, had Cynogen mod 9 everything was glorious.
Then Jellybean came out. before it was released on my phone with my carrier (Mobilicity, Vancouver), I got a nightly, of Cynogen, Jellybean. Bit laggy. Stock was released the next day. So I reverted to a back up file of Stock (gingerbread) then did the Google update from the device until I had jellybean. It was fine for a while, initially put on all my music... Etc.
Now i plug it in to my computer. it says USB device not recognized. tried uninstalling drivers, it says the drivers did not install properly. Tried manual install, it says i already have the best drivers. tried turning off device, and on, same, tried using on a friends computer, same thing.
Then I tried booting in bootloader (Which it still didnt mount although it said usb init ended) and tried going in to Recovery (maybe i could go back to the stock gingerbread. all I got was the little green android man with the red triangle exclamation point thing. tried resetting phone, same stuff.
Any help would be appreciated. all the places I looked i couldnt find anything.
Nexus S is meant to be rooted. I am literally STUCK on Jellybean stock, Unrooted.
Please Help!!!!! I have no developer powers (plus, I tried clicking USB debugging on/off)
Anyway to mount via command prompt or something?:crying:
jesusroks said:
So... I have a Nexus S And it was fine, Rooted, had Cynogen mod 9 everything was glorious.
Then Jellybean came out. before it was released on my phone with my carrier (Mobilicity, Vancouver), I got a nightly, of Cynogen, Jellybean. Bit laggy. Stock was released the next day. So I reverted to a back up file of Stock (gingerbread) then did the Google update from the device until I had jellybean. It was fine for a while, initially put on all my music... Etc.
Now i plug it in to my computer. it says USB device not recognized. tried uninstalling drivers, it says the drivers did not install properly. Tried manual install, it says i already have the best drivers. tried turning off device, and on, same, tried using on a friends computer, same thing.
Then I tried booting in bootloader (Which it still didnt mount although it said usb init ended) and tried going in to Recovery (maybe i could go back to the stock gingerbread. all I got was the little green android man with the red triangle exclamation point thing. tried resetting phone, same stuff.
Any help would be appreciated. all the places I looked i couldnt find anything.
Nexus S is meant to be rooted. I am literally STUCK on Jellybean stock, Unrooted.
Please Help!!!!! I have no developer powers (plus, I tried clicking USB debugging on/off)
Anyway to mount via command prompt or something?:crying:
Click to expand...
Click to collapse
First of all look for drivers u can try this:
http://junefabrics.com/android/download.php
When the drivers are installed, flash cmw recovery image via fastboot, then install the simple root zip in cmw.
You have jelly bean and you are rooted.
Also you can restore your backup....or flash any other ROM..
root.zip:
http://android.kcomputerzone.com/extras/Simple-Root-v1.0.zip
shivasrage said:
First of all look for drivers u can try this:
When the drivers are installed, flash cmw recovery image via fastboot, then install the simple root zip in cmw.
You have jelly bean and you are rooted.
Also you can restore your backup....or flash any other ROM..
root.zip:
Click to expand...
Click to collapse
Well, actually I already tried reinstalling drivers. Think it's a problem with my device, as it won't work on another computer as well. My phone was rooted, but when I did stock update I lost root and cwm. Everything is stock. I'm not sure what fastboot is or how to get in to it.
jesusroks said:
Well, actually I already tried reinstalling drivers. Think it's a problem with my device, as it won't work on another computer as well. My phone was rooted, but when I did stock update I lost root and cwm. Everything is stock. I'm not sure what fastboot is or how to get in to it.
Click to expand...
Click to collapse
OK i don´t think its a hardware/device problem....you could fix it yourself for sure...but its some work to do...
the question is would you like to do this ?
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
read this ...install it....http://dottech.org/downloads/adb_fastboot_and_other_tools.zip
and then flash a clean jelly bean image, then cmw, then root if you have any question i´l help you if you want...
S.R.
shivasrage said:
OK i don´t think its a hardware/device problem....you could fix it yourself for sure...but its some work to do...
the question is would you like to do this
read this ...install it....
and then flash a clean jelly bean image, then cmw, then root if you have any question i´l help you if you want...
S.R.
Click to expand...
Click to collapse
Hmm I'll try it. It does say that it has an error for installing the drivers. Then when I try to install manually it says I currently have the best drivers for the device 'unknown'
jesusroks said:
Hmm I'll try it. It does say that it has an error for installing the drivers. Then when I try to install manually it says I currently have the best drivers for the device 'unknown'
Click to expand...
Click to collapse
Also, where would I find a fresh jellybean image. How can I get cm on it
jesusroks said:
Also, where would I find a fresh jellybean image. How can I get cm on it
Click to expand...
Click to collapse
Her is a link for the JB images from google:
https://developers.google.com/android/nexus/images
for cm search the forum..
shivasrage said:
Her is a link for the JB images from google:
for cm search the forum..
Click to expand...
Click to collapse
Ok, well, I tried opening it up via command Prompt. It still doesnt recognize my phone is even hooked up. I tried manually installing the drivers, using have disk, and it said i should make sure those drivers are compatable for a 64 bit computer (which they ARE, because they were the ones I used before. Essentially, My issue is this. when i hook up my android device, when I go to (on my computer) Start> computer>Manage> Device manager... I should see android Device, Instead I see... Unknown device. I cant enter my phone via command prompt or anything. Its literally like my phone is only charging and not connected in anyway to my computer. This... really... sucks.... this is almost how i first rooted my phone. Except, then it worked.
Dont know if this is relevant, but in my bootloader it says at the bottom USB control Init and right underneath on the bottom left it says... USB control init End
jesusroks said:
Dont know if this is relevant, but in my bootloader it says at the bottom USB control Init and right underneath on the bottom left it says... USB control init End
Click to expand...
Click to collapse
Last thing you can try....
http://hotfile.com/dl/142977444/8d38a89/Downloader_v1.81.rar.html
download this....then push vol- and vol+ and power together then you are entering download mode....
run odin exe (the other file you can erase)....connect your phone to your pc then ...
if you had right connection a yellow sign appears at left side of the window...please report
shivasrage said:
Last thing you can try....
download this....then push vol- and vol+ and power together then you are entering download mode....
run odin exe (the other file you can erase)....connect your phone to your pc then ...
if you had right connection a yellow sign appears at left side of the window...please report
Click to expand...
Click to collapse
So I tried.
Maybe Im retarded. Not sure when i push the volume up plus Vol Down key. In the bootloader? before i turn on phone, On the home screen?
Anyways. Tried it while on, the phone registered me as pressing the volume keys and thats it, not the power key, not much happened. all that happened is the smae thing, it said USB device not recognized. which sucks.
jesusroks said:
So I tried.
Maybe Im retarded. Not sure when i push the volume up plus Vol Down key. In the bootloader? before i turn on phone, On the home screen?
Anyways. Tried it while on, the phone registered me as pressing the volume keys and thats it, not the power key, not much happened. all that happened is the smae thing, it said USB device not recognized. which sucks.
Click to expand...
Click to collapse
So my solution, in the end.
I bought a Galaxy nexus!!!!!
Such a sweet phone...........
My external speaker broke. Can you fix mine like you did yours?
Need new Android!
Sent from my Nexus S using xda app-developers app
Hello guys,
It is my first time yesterday to flash and root my Xperia Z5 since the camera app always says that it is currently in use.
I used this guide by sceryavuz . And it turned out great, I have used my phone for a day without any errors or problems encountered. But the thing is, I still cannot use the camera app and it has the same currently used by other application message so I decided to downgrade it to Marshmallow this morning. So I went to the same routine, downloaded an FTF file and loaded it into the flashtool.
After clicking Flash device in the flashtool and waited for the flashmode, I connected and pressed the volume down button of my phone but the flashtool is not reading and recognizing my phone. So I decided to open the TWRP and assumed that factory resetting my phone will do the work and it turns out that it just removed the /system folder and now I have a bigger problem with my phone.
When I'm connecting in flashmode the LED is turning to red, green, then will turn off, and then will do the same cycle if left unattended.
Could you guys please help me out with this. You'll be greatly appreciated guys. Thanks!
My phone is E6653 Xperia Z5
Well, you should reflash the system, by a custom rom of your choice or even the stock rom if you want to.
I'm using a custom rom and I highly recommend you to do so if you already lost your data, give it a try.
You don't need to downgrade to MM, it not an android version issue, I would recommend you carbon rom. Go to it's thread and figure out how to flash it, if you need help ask over there or quote me back in this thread.
Another option could be restoring your phone with xperia companion but you will need to relock the bootloader and get flashmode to work again. You can also try flashtool from your computer. Anyway I recommend you to do so ONLY and ONLY if you want your phone to run stock again as it was when you bought it.
Otherwise yep, figure out what's a customrom and how to flash it, you find tons of custom roms in xda threads. having already TWRP is an advantage, less sketchy stuff to do.
Hope it helped, as I said, quote me back if you need help
Edit: if you need the files we're running the exact same device, if you don't find em (and only if you can't find em) i could send them to you.
ofmoll said:
Well, you should reflash the system, by a custom rom of your choice or even the stock rom if you want to.
I'm using a custom rom and I highly recommend you to do so if you already lost your data, give it a try.
You don't need to downgrade to MM, it not an android version issue, I would recommend you carbon rom. Go to it's thread and figure out how to flash it, if you need help ask over there or quote me back in this thread.
Another option could be restoring your phone with xperia companion but you will need to relock the bootloader and get flashmode to work again. You can also try flashtool from your computer. Anyway I recommend you to do so ONLY and ONLY if you want your phone to run stock again as it was when you bought it.
Otherwise yep, figure out what's a customrom and how to flash it, you find tons of custom roms in xda threads. having already TWRP is an advantage, less sketchy stuff to do.
Hope it helped, as I said, quote me back if you need help
Edit: if you need the files we're running the exact same device, if you don't find em (and only if you can't find em) i could send them to you.
Click to expand...
Click to collapse
Hi ofmoll,
I'm sorry for the very late response, I had an internet connection issue this past week. I have tried your suggestion by using Carbon Rom, it works perfectly fine but I have one problem. It is not charging and the battery keeps saying that it is on 100% even if it is not. I'm trying to reflash other ROMs and I'll get back to you as soon as I finish flashing. Happy new year! Thanks!
Hi,
I tried to flash my phone a carbon rom and a crdroid rom and it was successful, my problem was it wasn't charging, and whenever I try to use flashtool, and I am entering flashmode, the phone turns red then green then after a minute it turns red again and then green after I press volume down and connect the phone to my PC. And the PC seems cannot recognize my device since no sounds are going off my computer when I connect it. I hope you can share your expertise regarding this.
Toshiiiiiiii said:
Hi,
I tried to flash my phone a carbon rom and a crdroid rom and it was successful, my problem was it wasn't charging, and whenever I try to use flashtool, and I am entering flashmode, the phone turns red then green then after a minute it turns red again and then green after I press volume down and connect the phone to my PC. And the PC seems cannot recognize my device since no sounds are going off my computer when I connect it. I hope you can share your expertise regarding this.
Click to expand...
Click to collapse
So you say it's not charging? Or did you manage to solve that? You don't really need flashtool at this point (unless you want to relock the bootloader, but I guess there are backdoors for that as well)
If it's not charging, well, the options are this: either it's a hardware problem, for example charger or charge port, or a software problem, because some files are needed for the phone to detect a charger source plugged in.
1. If the software is crashing you can try going into TWRP and wipe cache and dalvik cache, may help may not, try. If you get it yo work remember to calibrate the battery after it, it might be important because after flahsing roms and having this kind of issues the battery could not be showing the actual percentage of battery. So just calibrate, it's easy, Google it.
2. It could happen that the phone is charging but the battery status icon won't show it, I'm not too sure about this but I heard that could happen, might not be the case.
3. In none of that works, search, make a lot of research of people with your same problem and try amd try and try, If nothing works a clean reflash should solve it, usually does, if not try another rom, another kernel or go back to stock. It's your choice, but anyway I guess a clean reflash should get it working. I had the same issue with LineageOS and wiping Dalvik Cache solved it.
If you wipe dalvik expect a long reboot time, I don't suggest you to turn the phone off while it boots up. Wiping Dalvik means all cache files have to be built again the next time you reboot your phone, so yeah, expect some battery drain and a hot device while it boots up, but don't panic, it's totally normal.
Happy new year, hope you get it working again
Remember to hit thanks, cheers!
ofmoll said:
So you say it's not charging? Or did you manage to solve that? You don't really need flashtool at this point (unless you want to relock the bootloader, but I guess there are backdoors for that as well)
If it's not charging, well, the options are this: either it's a hardware problem, for example charger or charge port, or a software problem, because some files are needed for the phone to detect a charger source plugged in.
1. If the software is crashing you can try going into TWRP and wipe cache and dalvik cache, may help may not, try. If you get it yo work remember to calibrate the battery after it, it might be important because after flahsing roms and having this kind of issues the battery could not be showing the actual percentage of battery. So just calibrate, it's easy, Google it.
2. It could happen that the phone is charging but the battery status icon won't show it, I'm not too sure about this but I heard that could happen, might not be the case.
3. In none of that works, search, make a lot of research of people with your same problem and try amd try and try, If nothing works a clean reflash should solve it, usually does, if not try another rom, another kernel or go back to stock. It's your choice, but anyway I guess a clean reflash should get it working. I had the same issue with LineageOS and wiping Dalvik Cache solved it.
If you wipe dalvik expect a long reboot time, I don't suggest you to turn the phone off while it boots up. Wiping Dalvik means all cache files have to be built again the next time you reboot your phone, so yeah, expect some battery drain and a hot device while it boots up, but don't panic, it's totally normal.
Happy new year, hope you get it working again
Remember to hit thanks, cheers!
Click to expand...
Click to collapse
Hi Sir,
Happy new year! Thanks for your reply and I really appreciated it. When I connect the phone to my charger when it's off, it turns on then shows the screen of charging 0% by carbon rom then immediately dies after 2 bars being filled. I hope that it is not a hardware problem since when I connect my phone to my computer via the usb, it lights on but the computer can't recognize it. I am suspecting that this is a rom problem with my phone since the phone shows that it's charging connected to AC and 100% even if it is not connected to a charger. I am trying to get the flashmode to work again so I can flash a stock rom to it because the stock rom works perfectly fine but the camera. I will try all your suggestions tomorrow and I'll research harder to solve this. Will post an update once done. Cheers!
Toshiiiiiiii said:
Hi Sir,
Happy new year! Thanks for your reply and I really appreciated it. When I connect the phone to my charger when it's off, it turns on then shows the screen of charging 0% by carbon rom then immediately dies after 2 bars being filled. I hope that it is not a hardware problem since when I connect my phone to my computer via the usb, it lights on but the computer can't recognize it. I am suspecting that this is a rom problem with my phone since the phone shows that it's charging connected to AC and 100% even if it is not connected to a charger. I am trying to get the flashmode to work again so I can flash a stock rom to it because the stock rom works perfectly fine but the camera. I will try all your suggestions tomorrow and I'll research harder to solve this. Will post an update once done. Cheers!
Click to expand...
Click to collapse
As said, first of all try what I said. It nothing of that solves it, I suggest you 3 options
1. Either go stock, try using XPeria Companion, but I think since you flashed custom it doesn't work, at least for me. For Companion you'll need to relock bootloader. Or go stock by flashing a stock rom via TWRP. Note that after flashing a custom rom you'll never go back to the "real" stock if you don't have a backup, but you can always flash a stock rom.
2. You can also try to reflash the rom and see if that works.
3. Download a Custom kernel, then go to TWRP, wipe everything, then first of all flash the Kernel (remember to ensure that's a kernel for your device). Then reflash the ROM. This could look stupid because the ROM comes with a built-in kernel itself, but it solved an issue I had with random reboots. I didn't read this anywhere, I tried and for me it solved a problem I had which everybody was telling me that was caused by hardware, then it came out to be a Kernel issue. Try to if you want.
Try what I said before as well. This is all I know
Cheers
Edit: I forgot to tell you that PC Companion won't recognize your phone if it's running a customROM. Use Android File Transfer instead. You also need to check "use usb to transfer files" on the notifications pannel. Enable USB debugging as well, I guess you know how to do it, in case: you need to go to "about phone" in settings, hit 8 times Build Number, then the developer options should appear and check Android Debugging. That's it.