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.
Related
Here is what I have I can not get Odin to find the phone to do a master clear. My phone has a charging issue in that it thinks it is charging all the time even with the charging cable unhooked from the phone and that stays whether I am running 2.1 or 2.2. All of my computers are Windows 7 and will only find the phone if it is download mode?????
I am hoping against hope it is a software issue but I am thinking it is a hardware issue. But want to try everything possible to fix it before I buy replacement parts or a new phone.
I have tried the instructions from other threads without any success.
Could someone give me a step by step process that goes from starting fresh by deleting current drivers and reinstalling everything. I may be missing something from the instructions I have followed so far.
Also if you know something else to try I am all ears.
After you one click odin to reinstal Jf6 you have to set the phone to mass storage and USB debugging again ( found in settings-aplications ). Then plug the phone back into your comp while Odin is up and running ahead of time and the phone booted and running. It should recognise it ( you'll hear that dreaded sound ), click master clear and wait for the phone to do it's thing.
Well I finally got odin to find the phone and done the master clear and it did not help.
So unless anyone has any suggestions I will assume it is a hardware issue.
bigcountry said:
Well I finally got odin to find the phone and done the master clear and it did not help.
So unless anyone has any suggestions I will assume it is a hardware issue.
Click to expand...
Click to collapse
Since you're having problems with the phone being recognized maybe it's hardware. But, my phone is recognized just fine and I have an extremely hard time getting it to master clear.
I would guess I've only gotten it to master clear twice out of probably 40 or so attempts. About 10 of those times was in download mode, but after I found out it had to be booted up it still only master cleared twice. What I do to increase the odds is manually clearing everything I can, after backing up. Factory data reset, then I go into Clockwork and clear everything I can in there by digging into the menus - cache, data, Dalvik, etc. Then I go back to stock, then just hope it'll master clear on that flash attempt.
When it takes, it goes fast, but I've let it try for 15 to 20 minutes before and had nothing happen. No progress showing, just the start announced in Odin and then the disconnection announced when I get bored of nothing happening and pull it.
So my point is, maybe try it a few more times before you write it off as hardware. I don't recall the exact conditions when I got it to work, since it takes so many tries. But I believe it's been flash to stock Eclair, rooted, USB debugging on, and sd card mounted. Maybe not mounted. I reboot the phone after every time I try.
Edit: I did another update today and master clear worked fine. Un-rooted Eclair booted normally, usb debugging enabled, and usb mounted.
Have you had the phone not turn on while it wasn't plugged in?
My Xoom refuses to turn off completely. Every time I do anything related to shutting it down, it simply restarts. CWM restarts it, holding the button restarts it, QuickBoot restarts it. It hasn't always been like this, but soon after I started to root it and such, it stopped shutting down.
It might also be of help to note that I cannot install any OTA update or relock my bootloader. OTA updates simply fail at a screen with an android logo with an exclamation point, and if I relock the bootloader, the Xoom simply won't boot until I unlock it again. I have no idea if any of these problems are related to one another.
I'm currently using the Tiamat Xoom ROM 2.0.1, but it's done this for almost as long as I can remember (probably ever since I rooted the first time). It might also be worth noting that I flashed the wrong images the very first time I rooted it, but I've since flashed all of the appropriate images, so it should theoretically not be an issue.
Athenon87 said:
My Xoom refuses to turn off completely. Every time I do anything related to shutting it down, it simply restarts. CWM restarts it, holding the button restarts it, QuickBoot restarts it. It hasn't always been like this, but soon after I started to root it and such, it stopped shutting down.
It might also be of help to note that I cannot install any OTA update or relock my bootloader. OTA updates simply fail at a screen with an android logo with an exclamation point, and if I relock the bootloader, the Xoom simply won't boot until I unlock it again. I have no idea if any of these problems are related to one another.
I'm currently using the Tiamat Xoom ROM 2.0.1, but it's done this for almost as long as I can remember (probably ever since I rooted the first time). It might also be worth noting that I flashed the wrong images the very first time I rooted it, but I've since flashed all of the appropriate images, so it should theoretically not be an issue.
Click to expand...
Click to collapse
Question, Have you cleared your Dalvik Cache and/or trying another ROM to see if maybe it was not the Tiamat Xoom ROM that could have been corrupted in the flashing process? I am also curious if you have attempted to stock flash and then retry the ROM? You also should know that doing OTA Updates to the android devices that do not have stock ROMs (aka the ROM that you bought with the phone/tablet, no super user and so on) should not be updated with the OTA updates because it can corrupt the ROM that you have. I would suggest, that because Tiamat Xoom Rom 2.0.1 is now labled as [ROM][OMG] Team Tiamat Xoom Rom 2.0.1 Manta Ray [OBSOLETE] (as gotten from the link -- http://forum.xda-developers.com/showthread.php?t=1146153 ) you might want to try a newer version or different rom, OR try to redownload the rom and start over. I would also suggest that if you are going to do that, please clear cache
If I was unable to help you, please let me know and I will try and help you till the issue is solved or someone else has a better answer to help
I've restored to stock and then to the Tiamat rom 2 or 3 different times now, none of which resulted in the Xoom being able to shut off. If memory serves, the Xoom won't even shut off when I'm on completely stock images.
Have you cleared the Devlik Cache and other Cache before each install and as well as after install of the roms? because flashing rom after rom without actually clearing the files could result in residue of older files and corrupting a ROM. I would also look into a different kernal or maybe that your battery/charging cable is bad.
I know with my Ally dev phone it likes to just turn on (with or without a charge/hard boot off) when the phone is plugged into the wall socket (as it is not the normal wall adapter cause I bought the phone off ebay) so the adapter likes to force it online... can you turn off the Xoom when it is or is not plugged in?
Cranvis said:
Have you cleared the Devlik Cache and other Cache before each install and as well as after install of the roms? because flashing rom after rom without actually clearing the files could result in residue of older files and corrupting a ROM. I would also look into a different kernal or maybe that your battery/charging cable is bad.
I know with my Ally dev phone it likes to just turn on (with or without a charge/hard boot off) when the phone is plugged into the wall socket (as it is not the normal wall adapter cause I bought the phone off ebay) so the adapter likes to force it online... can you turn off the Xoom when it is or is not plugged in?
Click to expand...
Click to collapse
The rom install automatically wipes the two caches, so I haven't worried about it. There is no case in which my Xoom has been able to turn off for months, plugged in, not plugged in, or ANY other case. I asked solarnz on IRC about the problem, but he had no idea :/
Athenon87 said:
The rom install automatically wipes the two caches, so I haven't worried about it. There is no case in which my Xoom has been able to turn off for months, plugged in, not plugged in, or ANY other case. I asked solarnz on IRC about the problem, but he had no idea :/
Click to expand...
Click to collapse
You could, in all and all, have a bad device that has a power surge/fault/something where two wires are jumping/something else and just need to contact Motorola and ask them for help (after of course you make sure you reflashed back to 100% stock). These tablets, heck any computer like device, are so fickle to power that they will do anything if there is a right charge... good example is my Dev Phone I mentioned earlier... Plug it in off, and it boots up... you just might have had a bad tablet to start with and it took it a tiny bit to show it's ugly bug filled head... I am sorry that I can't help you any more on this, but I really do think you need to contact Motorola before your warranty is up... it takes only one wire to be solder incorrectly to mess up a whole system... trust me, I have had computers burn up on me and friends because of exposed wires, incorrectly soldered wires, and let alone, DUST of all things...
I hope you can get Motorola to help you out, because I am suspecting that it is a hardware issue... not a software...
My sony xperia M2 suddenly start blocking on boot. It comes to blue waves animation and it is stuck there.
I used flashtool software to flash new firmware hoping that it will solve the problem, but even after flashing device the problem still occurs.
Please help
TeslaNikola said:
My sony xperia M2 suddenly start blocking on boot. It comes to blue waves animation and it is stuck there.
I used flashtool software to flash new firmware hoping that it will solve the problem, but even after flashing device the problem still occurs.
Please help
Click to expand...
Click to collapse
Best to ask in the Xperia M2 Q&A, Help & Troubleshooting forum.
There you will get quick and proper help.
Good luck !
If it boots to the blue waves that means the Linux kernel is running, but something gets stuck at Java level. As fast attempts you may try to boot the phone without SIM card, or reboot in safe mode (not sure about the key combination, though. I'm a bit new to this phone). The other option is to do an hard reset to factory mode (again, I don't know the boot key combination): Otherwise repair the FW from the PC companion/ Bridge for Mac, I wouldn't use flashtool.
Miche1asso said:
If it boots to the blue waves that means the Linux kernel is running, but something gets stuck at Java level. As fast attempts you may try to boot the phone without SIM card, or reboot in safe mode (not sure about the key combination, though. I'm a bit new to this phone). The other option is to do an hard reset to factory mode (again, I don't know the boot key combination): Otherwise repair the FW from the PC companion/ Bridge for Mac, I wouldn't use flashtool.
Click to expand...
Click to collapse
I've done all of that...I updated software with PC Companion.. I can't get into safe mode, and I did hard reset several time...
But still, same thing is happening, It's still blocked on blue waves animation on boot.
TeslaNikola said:
I've done all of that...I updated software with PC Companion.. I can't get into safe mode, and I did hard reset several time...
But still, same thing is happening, It's still blocked on blue waves animation on boot.
Click to expand...
Click to collapse
Same here i have tried everything you have tried but no luck i hope someome can help !!!! cause i am at a lost....
Unless there is some malfunctioning piece of HW breaking up the boot process I am running out of ideas. After repairing the FW the ROM is like brand new. It should boot. To get more info one would need to run
Code:
adb logcat
From the PC/Mac with the phone connected via USB. But the USB debugging must be enabled. You may give it a try, but I doubt adb would connect.
PS: Wait, unless you guys unlocked the bootloader and restored the wrong TA partition. That would mess up things quite heavily.
Hello, after flashing the ftf it takes a very long term for it too boot up. For me it too about 20mins first time and about 1 hour for one time that I messed up really bad. I just left it on charge. (best charge on pc with adb running) and it should be fine. Also try sticking a pin/paperclip/pen into the hole next to the sim and sd slots. This will force the phone to shut down. Try rebooting. Also while flashing the ftf you need to UNTICK the data and cache (this WILL wipe all your data) AND TICK all the others. This will flash everything else. Also after flashing don't just unplug your phone. Eject it first (no one does that but do it) My current best guess is that. You've installed an app that runs at boot and is poorly written and cause error that stops the phone booting.
Additional to that. The is a chance very slight that one of your files is currupted try doing a md5hash and matching it. Secondly and most likely is that you packaged the ftf wrong if you just downloaded it and popped it inside the flash tools installations folder then it probably won't be this. But if you downloaded with the app, you get to choose what aspect of the ftf to include. So at this stage you might be miss out the kernal or whatever else as you spam next. Try reading my guide if you already haven't. Sorry for the very long post. I hope I helped
Sent from my D2305 using XDA Free mobile app
BlazingBullets said:
Hello, after flashing the ftf it takes a very long term for it too boot up. For me it too about 20mins first time and about 1 hour for one time that I messed up really bad. I just left it on charge. (best charge on pc with adb running) and it should be fine. Also try sticking a pin/paperclip/pen into the hole next to the sim and sd slots. This will force the phone to shut down. Try rebooting. Also while flashing the ftf you need to UNTICK the data and cache (this WILL wipe all your data) AND TICK all the others. This will flash everything else. Also after flashing don't just unplug your phone. Eject it first (no one does that but do it) My current best guess is that. You've installed an app that runs at boot and is poorly written and cause error that stops the phone booting.
Additional to that. The is a chance very slight that one of your files is currupted try doing a md5hash and matching it. Secondly and most likely is that you packaged the ftf wrong if you just downloaded it and popped it inside the flash tools installations folder then it probably won't be this. But if you downloaded with the app, you get to choose what aspect of the ftf to include. So at this stage you might be miss out the kernal or whatever else as you spam next. Try reading my guide if you already haven't. Sorry for the very long post. I hope I helped
Sent from my D2305 using XDA Free mobile app
Click to expand...
Click to collapse
I can see that flashing was successful because icon that shows when phone is turned off and charging has changed. But regardless of new firmware, the problem stays the same. I've left it for hours to boot but nothing.
I also don't think that installing bad application is a reason for this, because I haven't installed anything for days before this happened.
TeslaNikola said:
I can see that flashing was successful because icon that shows when phone is turned off and charging has changed. But regardless of new firmware, the problem stays the same. I've left it for hours to boot but nothing.
I also don't think that installing bad application is a reason for this, because I haven't installed anything for days before this happened.
Click to expand...
Click to collapse
Sorry for the super late reply and your problem is probably fixed by now. The FTF should flash everything. if you have them all ticked (except data and cache, they need to be UNTICKED for it to be flashed). If it doesn't solve your problem then its a bootloader problem and i personally cannot help you. You'll have to call into Sony.
Hi guys,
Sorry, I guess I have f*cked up my moms tab 2 (model GT-P5110)
I guess it's hard bricked, because it doesn't power up, but I'm not 100% sure maybe you guys can help me out or provide me with some tools which I can try to get life back into it.
- I can't access recovery mode via the normal way
- I can't access download mode via the normal way
There is a battery sign, but it's not rotating or anything else, just there... (kept it already 24hr in wall charger but without effect)
On the other hand if I try to connect it with USB to laptop, then it's saying " USB device not recognized" (and this " error" is coming every 5 seconds)
(sorry can't post pictures, because I'm a new user to this forum)
Hope you guys can help me.
Thank you in advance
Angerfistt said:
Hi guys,
Sorry, I guess I have f*cked up my moms tab 2 (model GT-P5110)
I guess it's hard bricked, because it doesn't power up, but I'm not 100% sure maybe you guys can help me out or provide me with some tools which I can try to get life back into it.
- I can't access recovery mode via the normal way
- I can't access download mode via the normal way
There is a battery sign, but it's not rotating or anything else, just there... (kept it already 24hr in wall charger but without effect)
On the other hand if I try to connect it with USB to laptop, then it's saying " USB device not recognized" (and this " error" is coming every 5 seconds)
(sorry can't post pictures, because I'm a new user to this forum)
Hope you guys can help me.
Thank you in advance
Click to expand...
Click to collapse
Hard brick won't even show a battery sign, have you tried using a new cable? Perhaps the cable ia at fault? What exactly did you do?
billysam said:
Hard brick won't even show a battery sign, have you tried using a new cable? Perhaps the cable ia at fault? What exactly did you do?
Click to expand...
Click to collapse
Thank you for your reply.
I haven't tried a new cable, because I don't have one, but to be honest I don't think that could be the solution, because if I put it inside my laptop to gives some sign of life "USB device not recognized".
I can't post pictures or link parts..., but the ring inside the batterij doesn't rotate. It's just there sometimes and frozen.
Looking forward to your response or any other responses
Angerfistt said:
Thank you for your reply.
I haven't tried a new cable, because I don't have one, but to be honest I don't think that could be the solution, because if I put it inside my laptop to gives some sign of life "USB device not recognized".
I can't post pictures or link parts..., but the ring inside the batterij doesn't rotate. It's just there sometimes and frozen.
Looking forward to your response or any other responses
Click to expand...
Click to collapse
I had the same error on my pc everytime i tried and the only way i get over it is by, proper drivers, trying different usb ports and changing my data cable.
And i have seen hard brick as well, it won't show anything, not even a unrecognized usb cable msg.
And there is not much you can do without a recovery or download mode. So the first thing that you can rule out is your cable is not at fault.
billysam said:
I had the same error on my pc everytime i tried and the only way i get over it is by, proper drivers, trying different usb ports and changing my data cable.
And i have seen hard brick as well, it won't show anything, not even a unrecognized usb cable msg.
And there is not much you can do without a recovery or download mode. So the first thing that you can rule out is your cable is not at fault.
Click to expand...
Click to collapse
Thank you for your reply.
I used the original USB cable with an not origional USB adaptor or the USB directly into my laptop but neither worked.., but yesterday I collected the original USB adaptor at my parents house and put it in a wall charger over night. I pressed the buttoms to access download mode and suddenly it works this morning ..... really really strange, so I guess that this is the problem.
Mom told me: Yes, sometimes there is a red cross inside the battery, but it will charge if you wait or try to unplug and plug it a couple of times.
My guess what happened:
- (sunday) Tab was very low battery with flashing around 10%
- (sunday) Stopped with flashing at 5%, because it was too late
- (monday morning) did nothing, battery empty and charging failed over the day.
- So I guess during the flash the battery broke down completely....
I directly switched on my laptop after I could acces download mode and downloaded stock rom. Unfortunately have to go to work and the download will take one hour , so hopefully it will stay in download mode the hole day, because I don't want to take the risk to turn it off
Guys,
I have another issue.
It connects to odin, but it failed to setupconnection if i try to flash a standard rom + pit..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone help?
Solved:
Solution, go to CWM and wipe data, mount and storage and so on.
Reconnect to download mode and flash stock rom
Tablet is working fine on origigional software right now...
If all else fails..what i did for clients was open tablet and charge the battery externally with 5v usb for 2 hours,then reinsert and do necessary fixes
Angerfistt said:
Thank you for your reply.
I used the original USB cable with an not origional USB adaptor or the USB directly into my laptop but neither worked.., but yesterday I collected the original USB adaptor at my parents house and put it in a wall charger over night. I pressed the buttoms to access download mode and suddenly it works this morning ..... really really strange, so I guess that this is the problem.
Mom told me: Yes, sometimes there is a red cross inside the battery, but it will charge if you wait or try to unplug and plug it a couple of times.
My guess what happened:
- (sunday) Tab was very low battery with flashing around 10%
- (sunday) Stopped with flashing at 5%, because it was too late
- (monday morning) did nothing, battery empty and charging failed over the day.
- So I guess during the flash the battery broke down completely....
I directly switched on my laptop after I could acces download mode and downloaded stock rom. Unfortunately have to go to work and the download will take one hour , so hopefully it will stay in download mode the hole day, because I don't want to take the risk to turn it off
Click to expand...
Click to collapse
Angerfistt said:
Hi guys,
Sorry, I guess I have f*cked up my moms tab 2 (model GT-P5110)
I guess it's hard bricked, because it doesn't power up, but I'm not 100% sure maybe you guys can help me out or provide me with some tools which I can try to get life back into it.
- I can't access recovery mode via the normal way
- I can't access download mode via the normal way
There is a battery sign, but it's not rotating or anything else, just there... (kept it already 24hr in wall charger but without effect)
On the other hand if I try to connect it with USB to laptop, then it's saying " USB device not recognized" (and this " error" is coming every 5 seconds)
(sorry can't post pictures, because I'm a new user to this forum)
Hope you guys can help me.
Thank you in advance
Click to expand...
Click to collapse
Greetings;
Like others already said: Get a Good USB Cable, and try other USB Ports when such thing Happens.
When Computer fails to Install the Device: Get Device Drivers (Kies).
A "Red Cross" at the Battery: Means your Charger does not have enough power to charge your device. Also Happens with USB on Computer.
When a Device Boots to Recovery, that ususlly means 97% of Times you can Fix it Totally or Partially. Depending on the " Damage " / "Mistskes" done previously.
Note: Mistakes happen to everyone,specially when learning or messing with Android Devices.
TIPs:
1) Before you proceed with any customization, always make backups (ROM Backup, EFS Backup and Personal Data).
2) Always Make Sure Whatever you Flash is for your Exact Device Model.
3) Have a Stock Rom and Recovery files close, just in case something goes bad.
Finally: Read a Lot, and Make questions when you dont Understand something, etc..
You will learn a lot, save lots of time and you will let yourself stay out of trouble.
x)
Let us know if you experience " Duplicated Data " or other Errors.
Judging by the steps mentioned here I assume you are.
Hopefully your Device Runs Ok Now.
Best Regards,
Richard
Please Press Thanks if itnHelped you, as this will keep me motivated to continue supporting this forum.
rgxHost said:
Greetings;
Like others already said: Get a Good USB Cable, and try other USB Ports when such thing Happens.
When Computer fails to Install the Device: Get Device Drivers (Kies).
A "Red Cross" at the Battery: Means your Charger does not have enough power to charge your device. Also Happens with USB on Computer.
When a Device Boots to Recovery, that ususlly means 97% of Times you can Fix it Totally or Partially. Depending on the " Damage " / "Mistskes" done previously.
Note: Mistakes happen to everyone,specially when learning or messing with Android Devices.
TIPs:
1) Before you proceed with any customization, always make backups (ROM Backup, EFS Backup and Personal Data).
2) Always Make Sure Whatever you Flash is for your Exact Device Model.
3) Have a Stock Rom and Recovery files close, just in case something goes bad.
Finally: Read a Lot, and Make questions when you dont Understand something, etc..
You will learn a lot, save lots of time and you will let yourself stay out of trouble.
x)
Let us know if you experience " Duplicated Data " or other Errors.
Judging by the steps mentioned here I assume you are.
Hopefully your Device Runs Ok Now.
Best Regards,
Richard
Click to expand...
Click to collapse
Hi Richard,
Thank you for your reply , I learned indeed.
Did a lot of flashing (around 20times before on my Galaxy S1 and Note 2) without a lot of trouble
This was the first time I tried to flash a custom rom on a Tablet, but failed
It's currently running on stock rom without issues.
Will Root and flash custom rom this evening again, but this time with full battery instead of <10%
Will update the post afterwards .
Greetings;
Ok.
Please proceed with caution now. xD
Before Flashing Remember to:
- Have a Backup of your Device Saved on Your SDCard (Made with CWM).
- Never Delete Battery Stats.
- Never Mess with Odin Checkboxes. Specially " EFS Clear"
If you do so you may end up in Losing your Imei, Wifi and Bluetooth Mac Adress and make then unavailable or not working. Consider yourself warned. As most people wont tell you this small tremendous problem.
- Try to get someminfo about the Custom Rom you're about to Install. Specially if it will change your partitions.
It is good to know that in case you need to revert the process. If it chamges your partitions, then reverting to stock may require you to select "Re-Partition" under Odin. Yet please double check with the Rom author.
1) Go Recovery, Erase Cache, and Dalvik (If you Have Dalvik Option under Advanced Tab under ClockWorkMod Recovety)
2) Proceed to your Flashing Method.
3) Install CF-Root / Kernel (If Custom Rom Doesnt Include It)
If your Device Goes into Bootloops or Kernel Panic after Flashing:
Take your Battery out, Press Power Button to Discharge the Memory Components, Place your Battery Back.
You're Most Likely Good to Go.
After putting the Battery Back I prefer to:
Boot into Recovery, Clean Cache and Dalvik. Then perform a Factory Reset (Yes Factory Reset Also Cleans Cache - But I find this method effective to prevent further errors).
After this I think you're good to go.
Although I wouldnt go for Custom Roms. There's just no need.. =)
If your goal is Performance, Battery Duration and Storage Space you don't need Custom Roms.
If your goal is having something different, (usually Buggy) and low Battery Duration... Well go for Custom!
Sounds Crazy, but thats the way it is.. Good Luck
Please Press Thanks if this Helped you, as this will keep me motivated to continue supporting this Forum.
rgxHost said:
Greetings;
Ok.
Please proceed with caution now. xD
Before Flashing Remember to:
- Have a Backup of your Device Saved on Your SDCard (Made with CWM).
- Never Delete Battery Stats.
- Never Mess with Odin Checkboxes. Specially " EFS Clear"
If you do so you may end up in Losing your Imei, Wifi and Bluetooth Mac Adress and make then unavailable or not working. Consider yourself warned. As most people wont tell you this small tremendous problem.
- Try to get someminfo about the Custom Rom you're about to Install. Specially if it will change your partitions.
It is good to know that in case you need to revert the process. If it chamges your partitions, then reverting to stock may require you to select "Re-Partition" under Odin. Yet please double check with the Rom author.
1) Go Recovery, Erase Cache, and Dalvik (If you Have Dalvik Option under Advanced Tab under ClockWorkMod Recovety)
2) Proceed to your Flashing Method.
3) Install CF-Root / Kernel (If Custom Rom Doesnt Include It)
If your Device Goes into Bootloops or Kernel Panic after Flashing:
Take your Battery out, Press Power Button to Discharge the Memory Components, Place your Battery Back.
You're Most Likely Good to Go.
After putting the Battery Back I prefer to:
Boot into Recovery, Clean Cache and Dalvik. Then perform a Factory Reset (Yes Factory Reset Also Cleans Cache - But I find this method effective to prevent further errors).
After this I think you're good to go.
Although I wouldnt go for Custom Roms. There's just no need.. =)
If your goal is Performance, Battery Duration and Storage Space you don't need Custom Roms.
If your goal is having something different, (usually Buggy) and low Battery Duration... Well go for Custom!
Sounds Crazy, but thats the way it is.. Good Luck
Click to expand...
Click to collapse
Hi,
You can't remove a battery out of a tab2.
In your opinion there is no benefit to flash a custom rom, because they are worse than stock?
You can. Try searching YouTube for:
"Removing Samsung Galaxy Tab Battery"
Custom ROMs are good:
- To have Nice visual themes;
- To simplify some operations like (Deodexing and Removing Bloatware, Install Custom Kernel, Add or Remove Funtions)
- To have a upgraded Firmware. (when brand wont release more updated Stock ROMs)
- Maybe some more (but I dont recall everything at this moment).
But on the other hand, expect:
- Bugs;
- Maybe Device Brick or Component Damage;
- Lots of time fixing your device.
- Sometimes Device may not work properly;
- For sure: Less Battery Duration;
Everything will depend on what's the purpose for your device.
Please Press Thanks if this Helped you, as this will keep me motivated to continue supporting this Forum.
Hi,
Rooting and flashing a custom ROM worked perfectly, without having issues.
Now running CyanogenMod 12.1 Android 5.1.1
Verstuurd vanaf mijn GT-N7100 met Tapatalk
Hello Angerfistt;
Glad to know.
Tip: Install Greenify and Set it up properly.
You will see some improvement in your battery duration.
Let me start off by saying that I just got this phone and decided to install a custom recovery and rom on it. As I do with all my phones that allow me to do so. I got the phone with android 4.4.4 on it, rooted it with Kingroot, and proceeded to use the XZDualrecovery tool to install TWRP. After that was all done, I downloaded the Z5 Expierience Rom, and I'm going to take a long shot here and say that I must have majorly missed something. Because after flashing that Rom in TWRP, my phone will do next to nothing. All went fine with the install of the ROM itself. Wiped Dalvik/Cache before restart.
If i hold down the power button I get a single vibration and then the phone does nothing (Does not even turn on backlight). If I plug the phone into my computer the phone will start a sequence of Red (LED), Green (LED), Vibrate. It does this aobut once every second. I can access Fastboot if I hold the volume + button, the LED then goes solid blue and the phone stops the LED - Vibration sequence. The only problem I have, as far as just not being able to Flashtool it back to life is, not being able to get the phone to go into Flashmode. No matter what I do, the phone will not let me get it into Flashmode. Im sure there is a good reason for this, I am just not sure what it is.
I've been flashing Roms and Recoveries since G1 days. I'm usually pretty decent at figuring this kind of thing out, but this thing has got me puzzled. I clearly went terribly wrong somewhere here, hopefully someone who knows this phone much better than I can point me in the right direction and hopefully get my less than 10 hour phone working again.
P.S. - If the phone is plugged into the wallcharger is does something similar to when it is plugged into my computer, but instead of a Sequence of Red - Green - Vibrate, I just get a steady red blink folled by a vibration. The phone will continue to do so until unplugged from the charger.
All help is very appreaciated!
I'm having the same issue. Anyone with the fix would be appreciated
Not sure what to try at this point!
I've been looking non-stop in my free time for a fix for this thing, and no matter what I do I keep getting the same results. Not really sure where to go from here, I have tried Flashtool, Emma, and PC Compainion out of desperaity. I tried all three options on teo seperate computers (One Windows 10 and the other Windows 7.) I have also tried multiple cables. No matter what I do all this thing will do is blink at me and vibrate. Is this thing hard bricked? I read its close to impossible to hard brick one of these phones. I'm wiling to accept that I have if that is the case. Just would like an opinion from someone who has some knowledge with these.
Same here, someone plz help.
If is only a change of batery or the phone is dead completly, an the stop trying to revive it.
Thanks .
Nick1801 said:
Let me start off by saying that I just got this phone and decided to install a custom recovery and rom on it. As I do with all my phones that allow me to do so. I got the phone with android 4.4.4 on it, rooted it with Kingroot, and proceeded to use the XZDualrecovery tool to install TWRP. After that was all done, I downloaded the Z5 Expierience Rom, and I'm going to take a long shot here and say that I must have majorly missed something. Because after flashing that Rom in TWRP, my phone will do next to nothing. All went fine with the install of the ROM itself. Wiped Dalvik/Cache before restart.
If i hold down the power button I get a single vibration and then the phone does nothing (Does not even turn on backlight). If I plug the phone into my computer the phone will start a sequence of Red (LED), Green (LED), Vibrate. It does this aobut once every second. I can access Fastboot if I hold the volume + button, the LED then goes solid blue and the phone stops the LED - Vibration sequence. The only problem I have, as far as just not being able to Flashtool it back to life is, not being able to get the phone to go into Flashmode. No matter what I do, the phone will not let me get it into Flashmode. Im sure there is a good reason for this, I am just not sure what it is.
I've been flashing Roms and Recoveries since G1 days. I'm usually pretty decent at figuring this kind of thing out, but this thing has got me puzzled. I clearly went terribly wrong somewhere here, hopefully someone who knows this phone much better than I can point me in the right direction and hopefully get my less than 10 hour phone working again.
P.S. - If the phone is plugged into the wallcharger is does something similar to when it is plugged into my computer, but instead of a Sequence of Red - Green - Vibrate, I just get a steady red blink folled by a vibration. The phone will continue to do so until unplugged from the charger.
All help is very appreaciated![/QUOTE
!st question is did you flash the correct rom for your device?
If you can go to recovery, then try to flash another rom,
Or use adb/fastboot to try and flash recovery img and use fastboot to reboot recovery.
Alternatively you may have to flash a kernel relevant to your rom.
Click to expand...
Click to collapse
Try this and see if it helps.........
If your phone is unbranded, i.e. not locked to a carrier, download a any generic(customized) firmware for your device through Xperifirm and flash it through Flashtool. It will wipe all your data (excluding your microSD, of course) but you don't have any other choice. This is most probably unbrick it...... So, try it and all the best.:good:
EDIT: If you've tried it, then go for this. Luckily you've fastboot still working, right? So, go to fastboot mode and flash a recovery image through it. It may take a lot of time but if recovery works, you can install a stock based rom for your device and then go back to stock firmware through Xperifirm and Flashtool.....
The phone is a Verizon model. I've tried to unlock the bootloader using command prompt following the sony instructions, after recieving my unlock key. I am able to connect to the phone and all of the fastboot commands work until I try and run the one to actually unlock the bootlaoder. That says the it is "not allowed." I think that is because I never enabled OEM Unlocking in the developers menu though. Not sure if there is a stock kernel I should try an flash through fastboot. Or if there is a stock recovery file that is flashbable through fastboot with a locked bootloader. The phone is definetley working in fastboot and somehow still knows how to charge. Im pretty sure at this point the problem is that the phone has a custom rom on it but the bootloader is still locked. I cannot unlock the bootloader because I can't get in Android to enable the proper options. Have also tried Flashtool for unlock the bootloader, along with extracting kernel sins from a stock 4.4.4 and a stock 5.0.1 FTF and trying to flash them. Since the begining I have still seen no change in the phone behavior.
Nick1801 said:
The phone is a Verizon model. I've tried to unlock the bootloader using command prompt following the sony instructions, after recieving my unlock key. I am able to connect to the phone and all of the fastboot commands work until I try and run the one to actually unlock the bootlaoder. That says the it is "not allowed." I think that is because I never enabled OEM Unlocking in the developers menu though. Not sure if there is a stock kernel I should try an flash through fastboot. Or if there is a stock recovery file that is flashbable through fastboot with a locked bootloader. The phone is definetley working in fastboot and somehow still knows how to charge. Im pretty sure at this point the problem is that the phone has a custom rom on it but the bootloader is still locked. I cannot unlock the bootloader because I can't get in Android to enable the proper options. Have also tried Flashtool for unlock the bootloader, along with extracting kernel sins from a stock 4.4.4 and a stock 5.0.1 FTF and trying to flash them. Since the begining I have still seen no change in the phone behavior.
Click to expand...
Click to collapse
dude I'm from the Verizon side yea like you have an bootloader status unlock no so your not going to change that and you can only flash Verizon z3v stuff you are really lucky if you can still get to fastboot after doing this. Use flashtool and flash a Verizon ROM from the z3v section only and pray it works.