Related
C6603 Stuck in bootloop! [Last update: 24/1/14]
UPDATE 24/01/14
This issue has been SOLVED.
I replaced the battery with one from eBay and the phone is working flawlessly, all the ROM flashing I went through was not the problem at all. Remember that if you are going to try to replace the battery you may as well buy a new rear glass piece as it is almost guaranteed that the glass will break in the removal process. You will also require new a adhesive piece. The entire procedure cost me $51AUD (battery, glass, adhesive).
All the content below is irrelevant, if your phone randomly shuts off (instantaneously) on boot or soon after, try to replace your battery!
Thanks for your help.
I've got quite a story to tell and if you have the patience to read it, I will greatly appreciate your assistance. TL;DR BELOW
In the beginning I was running 4.2.2, on a stock Australian 10.3.A.0.423 Unbranded ftf. It had been working flawlessly for a month or so until quite recently. It had developed a problem where it would only remain switched on whilst being plugged into the wall socket. As soon as (or thereafter) I removed the plug out of the phone, with one touch, one action, BAM! The display was off and I had to restart the phone again. I spent a few hours browsing for solutions to this problem, most of them said to hold the power and vol+ buttons until the handset vibrated 3 times. That turned it off alright, but I'm looking to go in the other direction.
After a stressful while scrounging old forum posts, I came to the conclusion that the fault is in my ROM, after all, I had flashed from 4.1.2 (I think) to 4.2.2 just a month prior (I flashed a ROM instead of waiting until the snail-like carriers here in Australia decided to dribble out the release). So now being convinced that I ROM is at fault I browse XDA for a newer stock one. Hey! Look! 4.3 it being rolled out in Aust, I check whether it's available to me yet, and obviously, no, it is not. I stumble upon this thread in my travels. I spend a while working to meet it's requirements. Get flashtool, get unlocked bootloader, get root, install cwm, and attempt to install XzDualRecovery 2.6. I've placed the XDR.zip on the sdcard in the XZ, I run the zip using CWM, it seems successful, I then go to reboot and check whether my 4.3 works, after I select reboot I'm asked whether I wish to root the phone. Why yes! that seems easy enough, and just as I select 'ok' the screen goes blank. The bloody phone has switched off in the middle of my work! I try to boot and it hangs on the Sony logo then reboots, creating a cycle. I decide to plug it back in to the wall socket (as this is the only way to get it to boot and remain on), huzzah, it runs. But the root had failed. The rest of my rant is insignificant until now (around 7 hours of failed attempts later)
So in an attempt to keep this wall of text down, I try my best to summarize, If I am not clear enough, just say.
I tried reflashing my old 4.2.2 ROM back, this makes the whole thing worse, now the phone won't even get past the Sony logo (even when plugged to a socket), I flash a different 4.3 ftf, nothing, I restore with PCC, I restore with SUS, I create a ftf from the SUS files and attempt to flash that. Nothing, nothing works. So where am I at now?
The phone still has battery, although, I'm not sure how much, I can no longer get it to charge as it hangs on the Sony logo. The phone should be flashed with 10.3.A.0.423, but when I check the baseband version in Fastboot cmd prompt, it still says 10.4.B.0.569, I feel as though flashtool isn't flashing properly, but I've read that this is usually a non-issue. I can boot into flashmode and fastboot mode. I can unlock and lock the bootloader. I can use ADB and Fastboot CMD (Minimal version) to read values and run commands. Actually, I managed to use the phone in fastboot mode, in conjunction with ADB and Fastboot CMD, I ran the command "fastboot continue" and the phone went on to charge off the usb power, It didn't seem to charge very fast, or at all, and I haven't been able to get it to do it again. So a TL;DR:
-C6603 stuck in bootloop.
-Possibly has a 4.2.2 ROM installed (10.3.A.0.423 Unbranded AU)
-Cannot Charge
-Can run flashmode and fastboot mode
-Can use ADB and Fastboot
-Can use SUS, PCC, and Flashtool to flash stock roms
-Can't figure this out for the life of me!
UPDATE 01/01/14
Currently I have a kernel installed that allows me to use cwm twrp (doomkernel v19, maybe), I have flashed a 'flashable' stock 4.3 rom using cwm and the phone didn't manage to get past the kernel logo. HOWEVER, using fastboot mode, I run the command "fastboot continue", and if I allow the phone to go past the kernel logo it vibrates, the LED turns green as opposed to showing a purple one, and it will begin charging (The LED isn't green as a result of the battery level). EDIT [1/1/14 3:01AM]: I tried to launch the phone whilst it was charging, the charging symbol went away and the phone remained on a black screen (lcd is on, but nothing is displayed) for a few seconds before shutting off automatically.
I must mention, I cannot get into recovery unless I boot the phone into fastboot mode, run the command in fastboot: "fastboot continue". If I don't do this, it simply crashes (shuts off) when showing the kernel logo.
If you need to know more I will provide as much information as I can, as succinct as I can, as fast as I can. I am in this for the long run. Thank you for your time,
UPDATE 08/01/14
I've come to the conclusion that my issue is battery related. After repeated from flashes and fastboot attempts, I managed to get the phone charging a few times, I witnessed the level was sporadic upon infrequent viewings. I have come across a few other very similar threads and feel that it is necessary to try replacing the battery, I try and post a youtube clip that details what happens currently.
Keringkien
keringkien said:
C6603 Stuck in bootloop!
I've got quite a story to tell and if you have the patience to read it, I will greatly appreciate your assistance. TL;DR BELOW
In the beginning I was running 4.2.2, on a stock Australian 10.3.A.0.423 Unbranded ftf. It had been working flawlessly for a month or so until quite recently. It had developed a problem where it would only remain switched on whilst being plugged into the wall socket. As soon as (or thereafter) I removed the plug out of the phone, with one touch, one action, BAM! The display was off and I had to restart the phone again. I spent a few hours browsing for solutions to this problem, most of them said to hold the power and vol+ buttons until the handset vibrated 3 times. That turned it off alright, but I'm looking to go in the other direction.
After a stressful while scrounging old forum posts, I came to the conclusion that the fault is in my ROM, after all, I had flashed from 4.1.2 (I think) to 4.2.2 just a month prior (I flashed a ROM instead of waiting until the snail-like carriers here in Australia decided to dribble out the release). So now being convinced that I ROM is at fault I browse XDA for a newer stock one. Hey! Look! 4.3 it being rolled out in Aust, I check whether it's available to me yet, and obviously, no, it is not. I stumble upon this thread in my travels. I spend a while working to meet it's requirements. Get flashtool, get unlocked bootloader, get root, install cwm, and attempt to install XzDualRecovery 2.6. I've placed the XDR.zip on the sdcard in the XZ, I run the zip using CWM, it seems successful, I then go to reboot and check whether my 4.3 works, after I select reboot I'm asked whether I wish to root the phone. Why yes! that seems easy enough, and just as I select 'ok' the screen goes blank. The bloody phone has switched off in the middle of my work! I try to boot and it hangs on the Sony logo then reboots, creating a cycle. I decide to plug it back in to the wall socket (as this is the only way to get it to boot and remain on), huzzah, it runs. But the root had failed. The rest of my rant is insignificant until now (around 7 hours of failed attempts later)
So in an attempt to keep this wall of text down, I try my best to summarize, If I am not clear enough, just say.
I tried reflashing my old 4.2.2 ROM back, this makes the whole thing worse, now the phone won't even get past the Sony logo (even when plugged to a socket), I flash a different 4.3 ftf, nothing, I restore with PCC, I restore with SUS, I create a ftf from the SUS files and attempt to flash that. Nothing, nothing works. So where am I at now?
The phone still has battery, although, I'm not sure how much, I can no longer get it to charge as it hangs on the Sony logo. The phone should be flashed with 10.3.A.0.423, but when I check the baseband version in Fastboot cmd prompt, it still says 10.4.B.0.569, I feel as though flashtool isn't flashing properly, but I've read that this is usually a non-issue. I can boot into flashmode and fastboot mode. I can unlock and lock the bootloader. I can use ADB and Fastboot CMD (Minimal version) to read values and run commands. Actually, I managed to use the phone in fastboot mode, in conjunction with ADB and Fastboot CMD, I ran the command "fastboot continue" and the phone went on to charge off the usb power, It didn't seem to charge very fast, or at all, and I haven't been able to get it to do it again. So a TL;DR:
-C6603 stuck in bootloop.
-Possibly has a 4.2.2 ROM installed (10.3.A.0.423 Unbranded AU)
-Cannot Charge
-Can run flashmode and fastboot mode
-Can use ADB and Fastboot
-Can use SUS, PCC, and Flashtool to flash stock roms
-Can't figure this out for the life of me!
If you need to know more I will provide as much information as I can, as succinct as I can, as fast as I can. I am in this for the long run. Thank you for your time,
Keringkien
Click to expand...
Click to collapse
download any FTF , 4.2.2 or 4.3 , connect your device to flash tool as flashmode , and select to flash the ftf , when you are selecting the ftf in the flash tool , at the right side check all at the wipe section , and uncheck all at the exclude section
but your internal storage might get also wiped , but i assume it already happened when you unlocked your boot loader
elias234 said:
download any FTF , 4.2.2 or 4.3 , connect your device to flash tool as flashmode , and select to flash the ftf , when you are selecting the ftf in the flash tool , at the right side check all at the wipe section , and uncheck all at the exclude section
but your internal storage might get also wiped , but i assume it already happened when you unlocked your boot loader
Click to expand...
Click to collapse
Alrighty then, I'll give that a go later. I have just found a 4.3 for Australia, perhaps it will be different. Thanks for the quick reply.
keringkien said:
Alrighty then, I'll give that a go later. I have just found a 4.3 for Australia, perhaps it will be different. Thanks for the quick reply.
Click to expand...
Click to collapse
this thread could be helpful : http://forum.xda-developers.com/showthread.php?t=2229250
i'm not sure if that problem could be solve, but it was, like you said, different. never saw anything like that either.
Anyway:
Can it boot into custom recovery in its state now?( for mounting storage for something else in case you have cwm or twrp installed)
Jambu95 said:
this thread could be helpful : http://forum.xda-developers.com/showthread.php?t=2229250
i'm not sure if that problem could be solve, but it was, like you said, different. never saw anything like that either.
Anyway:
Can it boot into custom recovery in its state now?( for mounting storage for something else in case you have cwm or twrp installed)
Click to expand...
Click to collapse
Thanks so much for the reply. The thread has something I can try, if this new rom fails (I expect it will). What is custom recovery? I cannot access the storage, only fastboot and flashmode. no cwm and xdr was never completed.
ROM just failed, trying SUS now.
keringkien said:
Thanks so much for the reply. The thread has something I can try, if this new rom fails (I expect it will). What is custom recovery? I cannot access the storage, only fastboot and flashmode. no cwm and xdr was never completed.
ROM just failed, trying SUS now.
Click to expand...
Click to collapse
oh dear, custom recovery is cwm (clockworkmod recovery) or twrp (team win recovery project), it means, it allows you to do something important just before it boot into system, which is bootstall or bootloop as you call it. you cannot boot into system, then try to boot into recovery ( which is before it boot the system), that might help.
both recoveries will allow you to mount storage to copy things to sd cards from pc.
you can try unlock bootloader and flash custom kernel with recoveries, maybe you "could" boot into one of those recoveries.
I also got the same problem, but mine is a C6602. I was trying to setup a mail exchange, then it asked for some permission. I push enter, then after an hour, it start the bootloop.
The phone boot till the main screen, i could swipe and play around for 10 second, then it reboot.
I have tried everything from hard reset, to FlashTool to SUS, relock, unlock, flash stock, from old stock to new stock, it just won't work :|
Jambu95 said:
oh dear, custom recovery is cwm (clockworkmod recovery) or twrp (team win recovery project), it means, it allows you to do something important just before it boot into system, which is bootstall or bootloop as you call it. you cannot boot into system, then try to boot into recovery ( which is before it boot the system), that might help.
both recoveries will allow you to mount storage to copy things to sd cards from pc.
you can try unlock bootloader and flash custom kernel with recoveries, maybe you "could" boot into one of those recoveries.
Click to expand...
Click to collapse
I'm well aware what cwm is, I just assumed that because you said 'custom' that it might possibly be different, as recovery is always custom anyway, sorry for the misunderstanding.
I am able to flash a 'boot.img' that enables me to use cwm and twrp, HOWEVER, the only way I can access it (as in cause the phone to remain on long enough for it to parse the boot.img) is to connect the phone to my computer in fastboot mode, then using the Fastboot command: "fastboot continue", it will run the 'img' and allow me to enter twrp or cwm. It still won't begin charging or even show the Xperia logo if I allow it to continue without accessing the recovery options.
Thanks for your help.
keringkien said:
I'm well aware what cwm is, I just assumed that because you said 'custom' that it might possibly be different, as recovery is always custom anyway, sorry for the misunderstanding.
I am able to flash a 'boot.img' that enables me to use cwm and twrp, HOWEVER, the only way I can access it (as in cause the phone to remain on long enough for it to parse the boot.img) is to connect the phone to my computer in fastboot mode, then using the Fastboot command: "fastboot continue", it will run the 'img' and allow me to enter twrp or cwm. It still won't begin charging or even show the Xperia logo if I allow it to continue without accessing the recovery options.
Thanks for your help.
Click to expand...
Click to collapse
if you can mount the storage, you could copy the flashable stock rom (4.3) and copy it into your sd card, and maybe you can flash through there by following instructions from that thread.
---------- Post added at 11:21 PM ---------- Previous post was at 11:20 PM ----------
billhainh said:
I also got the same problem, but mine is a C6602. I was trying to setup a mail exchange, then it asked for some permission. I push enter, then after an hour, it start the bootloop.
The phone boot till the main screen, i could swipe and play around for 10 second, then it reboot.
I have tried everything from hard reset, to FlashTool to SUS, relock, unlock, flash stock, from old stock to new stock, it just won't work :|
Click to expand...
Click to collapse
look for the disaster recovery thread i posted above
Jambu95 said:
if you can mount the storage, you could copy the flashable stock rom (4.3) and copy it into your sd card, and maybe you can flash through there by following instructions from that thread.
---------- Post added at 11:21 PM ---------- Previous post was at 11:20 PM ----------
Click to expand...
Click to collapse
I tried to mount the storage, my pc wouldn't detect the phones storage, I managed to push the stock rom zip to the sd card using ADB. I still had cwm recovery and could flash the zip using it. Still, however, the phone shuts down before it gets past the kernel logo. Again, I used the phone in Fastboot mode and forced it to continue using "fastboot continue", I left it go past the kernel logo and it is charging at the moment. I may try to start the phone now, yet expect it to crash again.
EDIT: I tried to launch the phone whilst it was charging, the charging symbol went away and the phone remained on a black screen (lcd is on, but nothing is displayed) for a few seconds before shutting off automatically.
EDIT: Happy New Year!
Thank you.
keringkien said:
I tried to mount the storage, my pc wouldn't detect the phones storage, I managed to push the stock rom zip to the sd card using ADB. I still had cwm recovery and could flash the zip using it. Still, however, the phone shuts down before it gets past the kernel logo. Again, I used the phone in Fastboot mode and forced it to continue using "fastboot continue", I left it go past the kernel logo and it is charging at the moment. I may try to start the phone now, yet expect it to crash again.
EDIT: I tried to launch the phone whilst it was charging, the charging symbol went away and the phone remained on a black screen (lcd is on, but nothing is displayed) for a few seconds before shutting off automatically.
EDIT: Happy New Year!
Thank you.
Click to expand...
Click to collapse
this problem occurs with every kernel you've used (including stock and custom kernels)?
Jambu95 said:
this problem occurs with every kernel you've used (including stock and custom kernels)?
Click to expand...
Click to collapse
Yes that is correct, it's current issue (turning off sponanteously) occurred when I was running stock 4.2.2 (no root, no bootloader unlock).
keringkien said:
Yes that is correct, it's current issue (turning off sponanteously) occurred when I was running stock 4.2.2 (no root, no bootloader unlock).
Click to expand...
Click to collapse
lol, you should unlock the bootloader before you flash a custom boot.img. the primary solution now is to flash any rom to see if it boots up normally , then you can still find a way to revert back to stock.
Jambu95 said:
lol, you should unlock the bootloader before you flash a custom boot.img. the primary solution now is to flash any rom to see if it boots up normally , then you can still find a way to revert back to stock.
Click to expand...
Click to collapse
I never said that I flashed a custom boot.img whilst on a locked bootloader. The reason I tried all the things that I have is because the phone was spontaneously shutting down (on stock, unedited). Perhaps once I made the mistake of flashing a boot.img before unlocking, but I have since unlocked and flashed many roms and kernels. Thanks for your reply.
keringkien said:
I never said that I flashed a custom boot.img whilst on a locked bootloader. The reason I tried all the things that I have is because the phone was spontaneously shutting down (on stock, unedited). Perhaps once I made the mistake of flashing a boot.img before unlocking, but I have since unlocked and flashed many roms and kernels. Thanks for your reply.
Click to expand...
Click to collapse
the device can't get pass the sony logo?
edNHour consum
Jambu95 said:
the device can't get pass the sony logo?
Click to expand...
Click to collapse
That is correct, it doesn't hang but suddenly turns off, the only way I can use recovery tools in the kernel is if I plug the phone into my pc in Fastboot mode, then issue the command "fastboot continue" from cmd.
keringkien said:
That is correct, it doesn't hang but suddenly turns off, the only way I can use recovery tools in the kernel is if I plug the phone into my pc in Fastboot mode, then issue the command "fastboot continue" from cmd.
Click to expand...
Click to collapse
i think there is something wrong with your motherboard or the battery connection, i'm not sure, because my pc got that problem before, it just boot up to starting windows... and then reboot, in the end i found out the capacitor got swelled in the power supply.
Jambu95 said:
i think there is something wrong with your motherboard or the battery connection, i'm not sure, because my pc got that problem before, it just boot up to starting windows... and then reboot, in the end i found out the capacitor got swelled in the power supply.
Click to expand...
Click to collapse
That is certainly possible, I have had to replace the back glass and during that operation it is possible that the battery got too hot and is now lower in voltage or something. Thanks for the suggestion, I would appreciate a second opinion with this...
Thank you.
keringkien said:
That is certainly possible, I have had to replace the back glass and during that operation it is possible that the battery got too hot and is now lower in voltage or something. Thanks for the suggestion, I would appreciate a second opinion with this...
Thank you.
Click to expand...
Click to collapse
if you still have your warranty, you can go to the center and request for a replacement, the best solution now is to revert to as stock as possible, if can get the bootloader locked again then it's good,
Jambu95 said:
if you still have your warranty, you can go to the center and request for a replacement, the best solution now is to revert to as stock as possible, if can get the bootloader locked again then it's good,
Click to expand...
Click to collapse
I imagine it is still under warranty, however I have read that unlocking the bootloader permanently voids warranty. And I have replaced the back of my white phone with a black glass, perhaps if I get a new white rear glass it will be ok, but then I might as well just replace the battery $40AUD isn't too expensive IMO.
Q&A for [RECOVERY] TWP 2.7.1.0 for One Mini 2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY] TWP 2.7.1.0 for One Mini 2. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
new twrp's won't work
Hi there,
I just tried to root my htc mini 2 with and it says that it is tampered now and I can't reboot my recovery. So I tried the newest twrp and some in between because I've read in this forum that somebody had the same problem and he just got the newest twrp but that didn't work for me at all.
Is there any way to undo the whole thing by replacing the twrp with the original one or do I have to wait till there is gonna be a root for the htc mini 2?
When I try to recover everything it says that this build is for development purpose only...
Does somebody have an idea?
I would appreciate it a lot if somebody has an idea.
Hornochse7958 said:
Hi there,
I just tried to root my htc mini 2 with and it says that it is tampered now and I can't reboot my recovery. So I tried the newest twrp and some in between because I've read in this forum that somebody had the same problem and he just got the newest twrp but that didn't work for me at all.
Is there any way to undo the whole thing by replacing the twrp with the original one or do I have to wait till there is gonna be a root for the htc mini 2?
When I try to recover everything it says that this build is for development purpose only...
Does somebody have an idea?
I would appreciate it a lot if somebody has an idea.
Click to expand...
Click to collapse
When the bootloader says "tempered" means that it was unlocked. when you see " this build is for development purpose only" its referring to TWRP because you now using a custom recovery. Not sure the nature of your problem but to undo, simply boot into boot loader and flash original recovery.img you can find in the forum.
I can't you open TWRP?
kativiti said:
When the bootloader says "tempered" means that it was unlocked. when you see " this build is for development purpose only" its referring to TWRP because you now using a custom recovery. Not sure the nature of your problem but to undo, simply boot into boot loader and flash original recovery.img you can find in the forum.
I can't you open TWRP?
Click to expand...
Click to collapse
Thank you for the quick respond and I wanted to try and undo everything but no my problem is that my phone completely froze in the twrp screen. I can't do anything, I can't unlock it nor shut down my phone or start the bootloader... that kind of sucks. Any suggestions now? Is it possible to open the htc one mini 2 and take out the battery? or do I have to wait till it runs out by it self and than start it again?
Hornochse7958 said:
Thank you for the quick respond and I wanted to try and undo everything but no my problem is that my phone completely froze in the twrp screen. I can't do anything, I can't unlock it nor shut down my phone or start the bootloader... that kind of sucks. Any suggestions now? Is it possible to open the htc one mini 2 and take out the battery? or do I have to wait till it runs out by it self and than start it again?
Click to expand...
Click to collapse
Read this tread. Someone had the same problem
http://forum.xda-developers.com/one-mini-2/help/rooting-htc-one-mini-2-t2880936
Unresponsive after boot up from dead battery
THanks to U-ra I get the enjoy my fav DSP Viper!!!
Cheers Man,
I have a small niggling problem that I can't work out, My battery tends to die alot, once I place the phone on charge after a flat battery, the phone auto boots to Twp, I am really cool with that but the annoying thing is buttons and screen are unresponsive? I can't do a thing, just have the Twp menu. The power of button does turn the screen off/on but thats its. Tried doing factory resets, reboots holding down power, vol buttons. Just nothing.
only way around it is to use adb and reboot command.
Is anyone else experiencing this problem.
http://forum.xda-developers.com/one...recovery-twp-2-7-1-0-one-mini-2-t2801370/page 4 here's the answer, so far
@u-ra is there any clue about getting official twrp support? (I was thinking about that problem of the self-booting recovery when phone is off and plugged in)
gibihr said:
@u-ra is there any clue about getting official twrp support? (I was thinking about that problem of the self-booting recovery when phone is off and plugged in)
Click to expand...
Click to collapse
I'll try to get to it this weekend.
HELP TWRP stuck at swipe to unlock
Hello all,
for unknown reason the phone restarded and now is stuck at swipe to unlock but it is not working. I try to hold power+volume down, but no way to turn it off. What can I do?
Thanks in advance
PS: well, it restarted... I don't know what happend but now it's ok
sorry for sounding like a newb
i have the verizon htc one remix, which i believe is the same as the one mini 2 . will this work on it?
akubenz said:
i have the verizon htc one remix, which i believe is the same as the one mini 2 . will this work on it?
Click to expand...
Click to collapse
you can try but i think someone here couldn't unlock bootloader trough HTC Dev.
Help: Stock rom updated between boots, TWRP non responsive, fastboot doesnt recognise
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
snorglamp said:
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
Click to expand...
Click to collapse
A kind member replied to me in another post indicating that fastboot commands only work in the bootloader, and that adb commands only work in TWRP which is why I am having problems re-flashing TWRP (requiring the "fastboot flash recovery TWRP.img" command). However I thought TWRP replaced the bootloader, so I seem to be locked out of re-flashing TWRP because i have TWRP. This seems not to make a lot of sense, can anyone else confirm or otherwise explain what I have misunderstood about that? As stated neither adb nor fastboot recognises the device is attached to the computer any more, so commands are not executing...
snorglamp said:
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
Click to expand...
Click to collapse
I think I have found the solution for myself: I went back into the stock rom and did a factory reset (from within android booted up as normal), which after completion rebooted me into TWRP which now works fine (is responding to touch again, and i can flash the Cyanogen image now). Hopefully this helps someone else in this situation one day, or maybe I am the only idiot that needed to ask hehe. I should clarify that after flashing TWRP I lost access to the fastboot screen and could not push anything over ADB or fastboot commands from windows (plugged in via USB). Holding down volume down and power booted directly into TWRP, and i had no way to get to fastboot screen. After doing factory resent from within the Android OS, holding volume down and power booted me to the fastboot screen, and only when I selected "Recovery" did it take me to TWRP, and I was again able to run fastboot and ADB commands from PC. Weird (or maybe not if you know more than me), but there it is...
snorglamp said:
A kind member replied to me in another post indicating that fastboot commands only work in the bootloader, and that adb commands only work in TWRP which is why I am having problems re-flashing TWRP (requiring the "fastboot flash recovery TWRP.img" command). However I thought TWRP replaced the bootloader, so I seem to be locked out of re-flashing TWRP because i have TWRP. This seems not to make a lot of sense, can anyone else confirm or otherwise explain what I have misunderstood about that? As stated neither adb nor fastboot recognises the device is attached to the computer any more, so commands are not executing...
Click to expand...
Click to collapse
Sorry, but it seems to me that you don't know the difference between bootloader and recovery. I apologize if you do. If not, search in CM wikis or ask here for explanations.
corbeau56 said:
Sorry, but it seems to me that you don't know the difference between bootloader and recovery. I apologize if you do. If not, search in CM wikis or ask here for explanations.
Click to expand...
Click to collapse
I do indeed know the difference between the bootloader and recovery, its just that the bootloader (Hboot) was not longer accessible in my situation and TWRP (the recovery) was imposing itself when you would normally expect to find the bootloader (i.e. my bootloader was for all intents and purposes replaced by my recovery, while I am sure this is not true in fact, it was in effect). As I say, doing a factory reset from within the OS restored the bootloader (HBoot) and I was able to continue modding. I am today extremely happy with my fully secured cyanogenmodded HTC One Mini 2 via TWRP recovery method. I hope that is somewhat clearer.
Can you enter bootliader now? I got stuck in a bootloop once and couldn't enter bootloader because I continued pressing power and Volume down like I did on my One S. For Mini 2, we have to hold the Volume UP and Power buttons until HBOOT appears, then release the buttons.
corbeau56 said:
Can you enter bootliader now? I got stuck in a bootloop once and couldn't enter bootloader because I continued pressing power and Volume down like I did on my One S. For Mini 2, we have to hold the Volume UP and Power buttons until HBOOT appears, then release the buttons.
Click to expand...
Click to collapse
That may well have been an alternative solution to my problem, however it was fixed by the factory reset and volume down and power then took me to HBoot (this would appear to contradict what you have said above, but maybe volume down and power does different things depending on how what you have done to the phone, not sure), so I cannot confirm whether or not that also would have worked for me. Good suggestion though, especially if you are not in a position to do a factory reset. and it would certainly be easier if it worked...I am convinced my problem was the result of a conflict between the TWRP version i installed (downloaded from here) and the android update that occurred between boots.
I am indeed able to get into bootloader/hboot and successfully flashed cyanogenmod from TWRP. I can confirm post flashing TWRP and Cyanogenmod, holding volume down and power takes me to HBoot (and then the option to go to fastboot or recovery).
Holding power up and power just loads cyanogenmod for me now as if I had just pressed power.
I thought I should confirm whether or not holding volume up vs volume down with power results in bootloader vs recovery loading. For me, they both took me to TWRP.
Also, TWRP doesnt seem to work on HTC One Mini 2 after you do anything to set up your phone. It just doesnt recognise touch input any more so you cant do anything with it. However the fix i noted earlier (factory reset) even works with other roms installed, confirmed for cyanogenmod 11 and 12 nightlies as at the date of this post. After factory reset TWRP works again, but if you go through the setup steps and start installing apps, TWRP goes unresponsive again. I hope we might get an official TWRP update soon!
I currently am trying to install CM12.1 onto my Amazon Fire 7, but unfortunately, it looks like I may have messed up in the process (I am stuck with the Amazon logo re-looping every ~15-20 seconds). I am able to go into the safe recovery mode, so I assume I haven't bricked the device completely, but I was wondering, what exactly is the best way to flash CM12.1 onto this device?
There seems to be an excessive amount of information, but very little organization, so would love to hear what the "best" steps would be to get CM12.1 on this bad boy.
I don't have the device yet but from what i read you need to tell us more info like what was your amazon v. 5.0.1 or 5.1.1 and how you install cm by TWRP or flash fire
Sent from my iPhone using Tapatalk
it will all depend on the version you have, but here you will find most info.
http://forum.xda-developers.com/amazon-fire/general/videos-tutorials-how-to-root-flash-roms-t3254268
shabuboy said:
it will all depend on the version you have, but here you will find most info.
http://forum.xda-developers.com/amazon-fire/general/videos-tutorials-how-to-root-flash-roms-t3254268
Click to expand...
Click to collapse
So I went ahead and installed the original firmware (5.1.1), but now am wondering where do I go from here. I have the device rooted and installed Flashify, but I am not sure how to install TWRP for 5.1.1, as I was using Rootjunky's .bat file.
darkgiant said:
So I went ahead and installed the original firmware (5.1.1), but now am wondering where do I go from here. I have the device rooted and installed Flashify, but I am not sure how to install TWRP for 5.1.1, as I was using Rootjunky's .bat file.
Click to expand...
Click to collapse
You can't install TWRP on 5.11, if you want to flash roms you have to use FlashFire now.
This is due to the 5.11 ota update including a bootloader update which removes the ability to fastboot boot.
Just follow the instructions to install CM 12.1 and wait for it to boot.
Ownster said:
You can't install TWRP on 5.11, if you want to flash roms you have to use FlashFire now.
This is due to the 5.11 ota update including a bootloader update which removes the ability to fastboot boot.
Click to expand...
Click to collapse
Yeah, so I just found that out few seconds ago. I tried to flash and install CM, but after the reboot, it just goes back to the FireOS "Optimizing system storage and applications..." screen, no idea what I am doing wrong...
I am also wiping everything too before I flash the CM and GAPPS zip files
darkgiant said:
I am also wiping everything too before I flash the CM and GAPPS zip files
Click to expand...
Click to collapse
I would be very careful using flashfire if your coming from fire os 5.1.1, we cannot use TWRP and a few people(myself included) have lost access to Amazon recovery, if you get stuck in a boot loop you have no way to recover your device, your best bet is to wait to see if a more secure way appears of flashing a device that has been using fire os 5.1.1.
abacabie said:
I would be very careful using flashfire if your coming from fire os 5.1.1, we cannot use TWRP and a few people(myself included) have lost access to Amazon recovery, if you get stuck in a boot loop you have no way to recover your device, your best bet is to wait to see if a more secure way appears of flashing a device that has been using fire os 5.1.1.
Click to expand...
Click to collapse
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
I have already went ahead and Flashed SlimLP, and so far so good, it seems fine to me, I guess I'll have to wait and see how stable it is.
darkgiant said:
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
Click to expand...
Click to collapse
Glad it worked well for you. Not everyone has been so fortunate. One persons favorable experience does not equate to everyone. Some of those impacted are veteran users who 'lost' devices testing out code and techniques that you are now benefiting from.
darkgiant said:
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
I have already went ahead and Flashed SlimLP, and so far so good, it seems fine to me, I guess I'll have to wait and see how stable it is.
Click to expand...
Click to collapse
If you read my post properly i said " lost access to Amazon recovery" , there is no way to transfer the file from ADB as ADB is not there, due to the fact that there is no Amazon recovery, holding volume down + power does nothing, if you look around the forum you will see this has happened to a few people myself included .
darkgiant said:
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
I have already went ahead and Flashed SlimLP, and so far so good, it seems fine to me, I guess I'll have to wait and see how stable it is.
Click to expand...
Click to collapse
He's talking about how his device got buggered from a dirty Rom load. In his case and for a few others, they've lost the option to sideload back to stock.
Anyway here's the bare minimum process, since it sounds like you've gone through the details parts of Rom loading before.
#1 restore to stock rom 5.1.1
#2 install SuperSU/Root
#3 install flashfire
#4 install CM/SlimLP and Gapps (pico, micro, mini) of your choice, and your done.
When I put CM on my 5.1.1 Fire device, I installed flashfire.apk manually, used open Gapps pico, and the CM 12-30-2015 image.
abacabie said:
If you read my post properly i said " lost access to Amazon recovery" , there is no way to transfer the file from ADB as ADB is not there, due to the fact that there is no Amazon recovery, holding volume down + power does nothing, if you look around the forum you will see this has happened to a few people myself included .
Click to expand...
Click to collapse
Gotcha, didn't know there was level of increments the relooping represented. Well either way, hopefully something gets developed to all the "hard-bricked" users.
Been on a custom Loli rom since a year or so ago when I first got the Z3c.
Lately too many things stopped working on it so I figured it was time to upgrade to a Marshmallow one.
Went with this: http://forum.xda-developers.com/z3-compact/orig-development/rom-t3435264
got the latest flashtool and flashed the latest stock rom 23.5.A.1.291 for USA as per the instructions
but none of the root options worked , so I started using adb and did some command line stuff and now nothing works except fastboot.
Flashmode doesn't even register anymore as upon inserting the usb with device off and vol.down held, the led blinks to red for bout half a second, then flashes to green for about a nano second before turning off.
Is there a combination of boot.img/recovery.img that'll bring this back into working order?
I haven't touched this stuff in over a year so forgive me for my ignorance~
Update:
I flashed TWRP via command line and was able to boot into it!
But /system, /cache, and /data are all broken (failed to mount & invalid argument?)
Also, the command I used was
HTML:
fastboot flash recovery twrp.img
but I remember using
HTML:
fastboot flash FOTAKernel twrp.img
before, when I did this for the first time. Is there any difference between FOTAKernel and recovery?
Update 2:
Managed to fix the partitions errors, just kept doing formats and wipes and reformats while flashing random ROMs in between.
So I can install ROMs now but Flashmode still doesn't work????
Additionally, I don't think it's charging while powered off either.
Update 3:
Flashed latest TWRP, a MM ROM, and GApps. Seems to be working fine.
Phone is also now charging when powered off again, completely with battery icon animation.
There's a hard reset button under the sim flap (tiny red red square, you need a pin to push it)
Try that.
Hey there,
Follow this LINK
It may help in fixing your problem
nzzane said:
Hey there,
Follow this LINK
It may help in fixing your problem
Click to expand...
Click to collapse
Nah mate, Flashmode doesn't work at all.
All I have or had, was fastboot mode.
nzzane said:
Hey there,
Follow this LINK
It may help in fixing your problem
Click to expand...
Click to collapse
Nah mate, Flashmode doesn't work at all.
All I have or had, was fastboot mode.
Hi all,
I have a big problem with my phone.
I wanted to try out Resurrection Remix on my phone.
I installed twrp-3.0.2-0-dogo.img with fastboot.
After reboot i saw the Teamwin logo and then i did a full wipe of everything, except SD Card (like i always do when i install a custom rom)
Then i installed Resurrection Remix M v.5.7.3.zip from sd and gapps, then wiped cache and pressed reboot.
No error with flashing, when the phone booted and i saw some logo's, took like 2-3 minutes and then the phone went off and started to reboot and reboot, had to take the battery off to let it stop.
Since then my phone isn't working properly, i tried to flash different kinds of stock roms with flash tool including wipe options.
No errors with flashing, but the phone still doesn't boot or it goes off after Sony logo then i leave the battery out for 10 mins or so then it starts and it looks normal, i can install aps, i can call, but the first time when i reboot my phone with this new install it's back to rebooting. I tried to leave my battery out for 10 hours but it doesn't help.
I tried to relock my bootloader and then unlock it again.
If i tried to install twrp-3.0.2-0-dogo.img it's going to reboot also, i tried airless or evomix kernel, then recovery starts but when i try to install a custom rom zip, and try to flash it my phone reboots after 5 seconds.
And now i don't know what to do anymore, so please anyone? help?
Thanks in advance!
did you try installing stock rom with flashtool ?
What was your android version when you first flash TWRP 3.0.2 recovery?If you are coming from stock lollipop then you should flash TWRP 3.0.2 (.228).Make sure you unlocked phone bootloader.Use advance clean in the recovery,select all except sd card and clean all.Then try flashing RR Rom again.Do wipe cache/Delvik after flashing RR Rom and before flashing GAPPS.
falptekin said:
did you try installing stock rom with flashtool ?
Click to expand...
Click to collapse
Yes, i tried atleast :
C5503_10.1.1.A.1.310_GLOBAL-LTE.ftf
C5503_10.6.A.0.454_HK.ftf
C5503_10.7.A.0.228_TR.ftf
And used all wipe options.
I used Emma tool, after that i removed the battery from the phone for 48 hours, then it booted the second time. I charged the battery and i left it like this for a few hours, then i tried to reboot but it went off after 20 seconds, tried to boot again but it goes off after Sony logo.
Røbin said:
What was your android version when you first flash TWRP 3.0.2 recovery?If you are coming from stock lollipop then you should flash TWRP 3.0.2 (.228).Make sure you unlocked phone bootloader.Use advance clean in the recovery,select all except sd card and clean all.Then try flashing RR Rom again.Do wipe cache/Delvik after flashing RR Rom and before flashing GAPPS.
Click to expand...
Click to collapse
My version was CM 13 (cm-13.0-20160801-UNOFFICIAL-dogo.zip) that was working very well, but before i flashed RR i did advanced cleaning and i checked everything except SD Card and USB OTG and a factory reset and after flashing pressed wipe cache/dalvik and then i rebooted.
The phone is off now without battery. This Sony doesn't have recovery, buttons aren't working and they never did, i can only flash twrp with fastboot wich makes it only boot into recovery and then i used this to flash custom roms.
I only started to flash custom roms about a month ago because someone gave me this Sony ZR, i bought a new original battery for it but when i call on speaker there is some underwater bubbling sound and i also wanted marshmallow and i hoped this may fix the bubbling sound, with CM 13 the sound was already better but didn't fix it completely.
TWRP won't let me flash anything anymore, it's starting to flash but after 5 seconds it reboots back into recovery.
Edit: Is it possible that there is still stuff in the RAM that is causing problems?
Edit: I thought i'm going to this phone another try. I installed twrp-3.0.2-0-dogo.img and it boots, also this version didn't want to boot anymore but now it does. I wiped everything, also SD Card, i checked everything is empty. Before i couldn't wipe my SD Card anymore and in Windows all files showed double and i couldn't copy files. Going to charge it first and think about what i want try to flash. Wipe cache/dalvik and then flash gapps is a good idea.
Edit: it almost charged now, when it charged i will remove the battery again for the night, i will decide later what i'm going to do.
Fuchsia said:
My version was CM 13 (cm-13.0-20160801-UNOFFICIAL-dogo.zip) that was working very well, but before i flashed RR i did advanced cleaning and i checked everything except SD Card and USB OTG and a factory reset and after flashing pressed wipe cache/dalvik and then i rebooted.
The phone is off now without battery. This Sony doesn't have recovery, buttons aren't working and they never did, i can only flash twrp with fastboot wich makes it only boot into recovery and then i used this to flash custom roms.
I only started to flash custom roms about a month ago because someone gave me this Sony ZR, i bought a new original battery for it but when i call on speaker there is some underwater bubbling sound and i also wanted marshmallow and i hoped this may fix the bubbling sound, with CM 13 the sound was already better but didn't fix it completely.
TWRP won't let me flash anything anymore, it's starting to flash but after 5 seconds it reboots back into recovery.
Edit: Is it possible that there is still stuff in the RAM that is causing problems?
Edit: I thought i'm going to this phone another try. I installed twrp-3.0.2-0-dogo.img and it boots, also this version didn't want to boot anymore but now it does. I wiped everything, also SD Card, i checked everything is empty. Before i couldn't wipe my SD Card anymore and in Windows all files showed double and i couldn't copy files. Going to charge it first and think about what i want try to flash. Wipe cache/dalvik and then flash gapps is a good idea.
Edit: it almost charged now, when it charged i will remove the battery again for the night, i will decide later what i'm going to do.
Click to expand...
Click to collapse
Someone maybe played with your phone in underwater to cause bubbling sound.I don't see any hardware problem in your phone.You maybe did something wrong or anything else that your phone behaving like this.Listen,You first flash a stock rom.Lollipop would be better because you can flash flashable twrp 3.0.2(.228) via flash fire or flashify app.I once tried flashing twrp img through fastboot and it caused bootloop.So I always use flashable zip.Fastboot for emergency.And try to reformatting your system pertition.I hope this will work or you'll need expert developer to help you.Maybe Daedroza can help you if my sugg. don't work.
Røbin said:
Someone maybe played with your phone in underwater to cause bubbling sound.I don't see any hardware problem in your phone.You maybe did something wrong or anything else that your phone behaving like this.Listen,You first flash a stock rom.Lollipop would be better because you can flash flashable twrp 3.0.2(.228) via flash fire or flashify app.I once tried flashing twrp img through fastboot and it caused bootloop.So I always use flashable zip.Fastboot for emergency.And try to reformatting your system pertition.I hope this will work or you'll need expert developer to help you.Maybe Daedroza can help you if my sugg. don't work.
Click to expand...
Click to collapse
The bubbling sound is a known issue with some Sony smartphones, on google i have read more stories about this problem, not only zr but also other Z models. The problem is caused by the second mic i think, if i use loudspeaker when calling and i lay the phone on the back the sound is much better. I saw on other thread about this, http://forum.xda-developers.com/xperia-zr/help/disable-mic-t3434997
On YouTube you can find many movies about this, for example https://www.youtube.com/watch?v=fC6JbuQJ_gg
It's really annoying for the other person to hear these sounds when you are calling. They need to listen very carefully to understand you, but it's only when you call on speaker.
When i wanted to flash a custom rom for the first time i wanted to do this with apps on my phone. I rooted my phone with kingroot and used an app to check if the phone was really rooted. I installed twrp app and tried to install recovery but it gave an error. I tried to install recovery with Flashify but then it says that the recovery partition is not present. When i try to flash with Flashify it says it's going to reboot into recovery but then the the phone boots like normal. The only way for me to get a recovery on the phone is just flashing with fastboot or using flashtool. Doomlord kernel and XZDualrecovery don't boot, only twrp is working.
Fuchsia said:
The bubbling sound is a known issue with some Sony smartphones, on google i have read more stories about this problem, not only zr but also other Z models. The problem is caused by the second mic i think, if i use loudspeaker when calling and i lay the phone on the back the sound is much better. I saw on other thread about this, http://forum.xda-developers.com/xperia-zr/help/disable-mic-t3434997
On YouTube you can find many movies about this, for example https://www.youtube.com/watch?v=fC6JbuQJ_gg
It's really annoying for the other person to hear these sounds when you are calling. They need to listen very carefully to understand you, but it's only when you call on speaker.
When i wanted to flash a custom rom for the first time i wanted to do this with apps on my phone. I rooted my phone with kingroot and used an app to check if the phone was really rooted. I installed twrp app and tried to install recovery but it gave an error. I tried to install recovery with Flashify but then it says that the recovery partition is not present. When i try to flash with Flashify it says it's going to reboot into recovery but then the the phone boots like normal. The only way for me to get a recovery on the phone is just flashing with fastboot or using flashtool. Doomlord kernel and XZDualrecovery don't boot, only twrp is working.
Click to expand...
Click to collapse
First of all change the kingroot with supersu.Kingroot root access control not so stable.Download selinux mode changer to set in permissive mode.If you are at LP version,twrp app won't install recovery or support it.flash twrp3.0.2(.228) via flashify or different flashing app.selinux permissive mode will let you to go to recovery mode.By the way,xzdualrecovery is for locked bootloader and should boot without any problem.I don't know it will work on unlocked bootloader or not.So try your best what I have told and this is all I have to share from my own experience.
Røbin said:
First of all change the kingroot with supersu.Kingroot root access control not so stable.Download selinux mode changer to set in permissive mode.If you are at LP version,twrp app won't install recovery or support it.flash twrp3.0.2(.228) via flashify or different flashing app.selinux permissive mode will let you to go to recovery mode.By the way,xzdualrecovery is for locked bootloader and should boot without any problem.I don't know it will work on unlocked bootloader or not.So try your best what I have told and this is all I have to share from my own experience.
Click to expand...
Click to collapse
I flashed the latest Lollipop and it's back to rebooting, i see the sony logo and before it says powered by android it goes off. I removed the battery again, i will try to root the phone and use selinux mode changer when it's booting. It wil take atleast 12 hours without battery before it boots.
Fuchsia said:
I flashed the latest Lollipop and it's back to rebooting, i see the sony logo and before it says powered by android it goes off. I removed the battery again, i will try to root the phone and use selinux mode changer when it's booting. It wil take atleast 12 hours without battery before it boots.
Click to expand...
Click to collapse
Is there any problem with your phone?Did you experiment your phone too much?I don't get it,why after flashing stock rom via flashtool gives you bootloops if no error showed up while flashing!!Is this your battery problem?And I think so because few months ago my phone battery heavily damaged and therefor It don't charge and my phone didn't bootup but bootlooping.I first thought it was my mistake to flash rom incorrectly.So i had to flash stock rom via flashtool to go back to normal but unfortunetly PC don't recoznige my phone not even fastboot.I was worried and couldn't do anything and went to service center,they changed the battery with new one and my phone comes to life again.Mainly this was for my local charger fault.it also damaged in that day too.SO brought a orginal sony charger.But you said you brought a new battery too then how come you face bootloops.well if there is no error message shows up I can't help you with anything.Only better expert member can help you.By the way you can collect log via adeb fastboot if your phone fastboot mod work.
Here is the inst:
1. Install the Android Debug Bridge using http://developer.android.com/tools/help/adb.html
2. Instructions on installing Android Debug Bridge are located here:
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android- debug-bridge-utility
3. Run the following commands:
“adb logcat -c" (This clears the logs.)
4. Reproduce the issue.
5. Then, run the following command to capture the logs in a file:
“adb logcat -d > Name_of_Log_File.txt"
maybe it will gives some clues what is happening.
Røbin said:
Is there any problem with your phone?Did you experiment your phone too much?I don't get it,why after flashing stock rom via flashtool gives you bootloops if no error showed up while flashing!!Is this your battery problem?And I think so because few months ago my phone battery heavily damaged and therefor It don't charge and my phone didn't bootup but bootlooping.I first thought it was my mistake to flash rom incorrectly.So i had to flash stock rom via flashtool to go back to normal but unfortunetly PC don't recoznige my phone not even fastboot.I was worried and couldn't do anything and went to service center,they changed the battery with new one and my phone comes to life again.Mainly this was for my local charger fault.it also damaged in that day too.SO brought a orginal sony charger.But you said you brought a new battery too then how come you face bootloops.well if there is no error message shows up I can't help you with anything.Only better expert member can help you.By the way you can collect log via adeb fastboot if your phone fastboot mod work.
Here is the inst:
1. Install the Android Debug Bridge using http://developer.android.com/tools/help/adb.html
2. Instructions on installing Android Debug Bridge are located here:
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android- debug-bridge-utility
3. Run the following commands:
“adb logcat -c" (This clears the logs.)
4. Reproduce the issue.
5. Then, run the following command to capture the logs in a file:
“adb logcat -d > Name_of_Log_File.txt"
maybe it will gives some clues what is happening.
Click to expand...
Click to collapse
I tried my old battery and it boots, already booted up 3x times. I never thought it maybe the battery because it's only 2 months old. Thanks so much for your help.
I tried to install recovery with selinux permissive mode and flashify but i stil can't install recovery.
It says: Partition not found, your recovery partition couldn't be found. You won't be able to flash recovery images. You can stil flash zip files.
I don't think it's possible to have recovery on this phone, atleast not the normal way.
Edit: I flashed RR and it's working fine. I'm so happy it's working again, i never really used this old battery but i think it's not so bad at all. I only lost 8% battery with flashing and booting RR. I never really thought it was the battery because it was charging normal, i used it for 2 months or something without problems.
Fuchsia said:
I tried my old battery and it boots, already booted up 3x times. I never thought it maybe the battery because it's only 2 months old. Thanks so much for your help.
I tried to install recovery with selinux permissive mode and flashify but i stil can't install recovery.
It says: Partition not found, your recovery partition couldn't be found. You won't be able to flash recovery images. You can stil flash zip files.
I don't think it's possible to have recovery on this phone, atleast not the normal way.
Edit: I flashed RR and it's working fine. I'm so happy it's working again, i never really used this old battery but i think it's not so bad at all. I only lost 8% battery with flashing and booting RR. I never really thought it was the battery because it was charging normal, i used it for 2 months or something without problems.
Click to expand...
Click to collapse
If it was a battery problem then change it or carefully use it.And the error you are facing is because the latest flashify has some bugs.But now as you are already using RR MM rom.You can download twrp app and use this app to install recovery.
Røbin said:
If it was a battery problem then change it or carefully use it.And the error you are facing is because the latest flashify has some bugs.But now as you are already using RR MM rom.You can download twrp app and use this app to install recovery.
Click to expand...
Click to collapse
I tried to install recovery, flashify hangs all the time, twrp app gives an error when i try to install recovery and flashfire says there is no partition for this image. I thought i'll do a factory reset in RR and when the phone rebooted i saw twrp. I tried with pressing the buttons when booting but no luck. I used reboot into recovery option and it worked. This is the first custom rom that gave my phone recovery.
I will throw the battery away and use the old battery, i can always buy a new one later.
Fuchsia said:
I tried to install recovery, flashify hangs all the time, twrp app gives an error when i try to install recovery and flashfire says there is no partition for this image. I thought i'll do a factory reset in RR and when the phone rebooted i saw twrp. I tried with pressing the buttons when booting but no luck. I used reboot into recovery option and it worked. This is the first custom rom that gave my phone recovery.
I will throw the battery away and use the old battery, i can always buy a new one later.
Click to expand...
Click to collapse
OH!So that the old recovery occupied all the recovery partition space that you are unable to install twrp recovery.But old recovery should be replaced by new recovery,that's strange.well I don't know how did this happen but don't use fastboot to install recovery or anything else,It's for emergency.I'm not fully familiar with fastboot though,I tried once before and caused trouble. I hope your troubles are gone now.
Røbin said:
OH!So that the old recovery occupied all the recovery partition space that you are unable to install twrp recovery.But old recovery should be replaced by new recovery,that's strange.well I don't know how did this happen but don't use fastboot to install recovery or anything else,It's for emergency.I'm not fully familiar with fastboot though,I tried once before and caused trouble. I hope your troubles are gone now.
Click to expand...
Click to collapse
My phone don't have any partition recovery, i tried 100x times with stock rom to boot recovery, with buttons, with apps that boot in recovery. I do have recovery with RR rom, but it's not in the recovery partition. I tried Tesla, CM 13, XOSP but still no recovery. I tried to boot recovery with all roms, but it doesn't matter. It's fine now, been playing a bit with RR and it's a nice rom. Thank you for helping.