I did a factory reload of a rooted phone with CWM.
Now for the CWM issue the Moto G loaded OK and then said there was an update for android to fix some bugs. This was 4.4.3. I loaded it and it gets half way and it then says
"Signature verification fail"
at the bottom of the screen and
" Install Untrusted Package"
The options are yes, no or go back
at the top....
whichever one I try it then tries to boot shows the Android / Motorola screen and starts up gets a txt message for 2-3 seconds... it then goes back to Android CWM recovery with the same options as above and repeats the process. again and again and again. No function keys will stop this cycle which just repeats again. This continues until the battery dies.
any ideas ? how can I override this action in CWM v6.0.4.6 and force it to do a factory reload ? any help or advice much appreciated.
The following thread had a similar problem and was fixed... http://forum.xda-developers.com/showthread.php?p=53404637
NerdNoob1210 suggested...
"If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose."
unfortunately I can't get into bootloader. I can connect usb and it makes no difference. therefore adb commands dont work. it just goes straight into screen described with those three options. I'm hoping that there is an override action in CWM which isn't power and volume down which do nothing.
If not how can I force it into bootloader instead please ? any suggestions appreciated.
Hello.
Today my oneplus one was suddenly stuck in bootloop. This happened in the middle of the day when I rebooted my phone. My phone was running the latest update that came OTA (stock lollipop). Whenever I boot my phone it starts loading and suddenly a Chrome (browser) window appears for 1 second and tries to load a website. Afterwards my lock screen pop ups for 1 seconds and it starts to reboot. During the lockscreen I tried to unlock my phone as soon as possible, but it just reboots. (Any ideas about this weird problem?)
I CAN boot it in recovery mode by holding volume-down button and power button.
I CAN boot it in fastboot mode by holding volume-up button and power button.
Perhaps a factory reset will do the trick, but I don't have a backup of my files (because this happened so suddenly without me trying to flash/customize my phone). My first priority is recovering my files, because most solutions will end up in me losing every file. Unfortunately I've found little possibility to do this during the bootloop problem. I've tried to flash TWRP because it could make backups of my phone. I tried it through ADB/Fastboot, but it failed because my device is not unlocked (I can't go to settings and put my phone in developer mode and debugging mode). So I've read somewhere that unlocking my phone (bootloader?) through ADB will wipe my phone, which is exactly what I don't want.
Also I've tried this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
But It also failed because my device was not unlocked.
Did I miss some steps somewhere or did I read something wrong?
Hopefully anybody has an idea to either fix the bootloop without losing my data, or finding a way to recover my files before wiping the phone.
Thank you.
RightHanded said:
Hello.
Today my oneplus one was suddenly stuck in bootloop. This happened in the middle of the day when I rebooted my phone. My phone was running the latest update that came OTA (stock lollipop). Whenever I boot my phone it starts loading and suddenly a Chrome (browser) window appears for 1 second and tries to load a website. Afterwards my lock screen pop ups for 1 seconds and it starts to reboot. During the lockscreen I tried to unlock my phone as soon as possible, but it just reboots. (Any ideas about this weird problem?)
I CAN boot it in recovery mode by holding volume-down button and power button.
I CAN boot it in fastboot mode by holding volume-up button and power button.
Perhaps a factory reset will do the trick, but I don't have a backup of my files (because this happened so suddenly without me trying to flash/customize my phone). My first priority is recovering my files, because most solutions will end up in me losing every file. Unfortunately I've found little possibility to do this during the bootloop problem. I've tried to flash TWRP because it could make backups of my phone. I tried it through ADB/Fastboot, but it failed because my device is not unlocked (I can't go to settings and put my phone in developer mode and debugging mode). So I've read somewhere that unlocking my phone (bootloader?) through ADB will wipe my phone, which is exactly what I don't want.
Also I've tried this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
But It also failed because my device was not unlocked.
Did I miss some steps somewhere or did I read something wrong?
Hopefully anybody has an idea to either fix the bootloop without losing my data, or finding a way to recover my files before wiping the phone.
Thank you.
Click to expand...
Click to collapse
Unfortunately you might be stuck in a catch-22 situation here. In order to access the files you'd need to unlock the bootloader, but in doing so you'd lose those files. Without usb debugging already enabled I can't see a way out of this.
Decided to unlock the bootloader through ADB. (bye bye data)
After I've unlocked it, I've tried installing TWRP.
Some minor problems occured but I can finally boot into TWRP through volume-down button + power button.
I've decided to download the stock ROM i've found on the OPO forums.
Couldn't acces my phone through normal methods, so I had to use ADB to push the files into my phone.
Installing the file through TWRP, wiped cache/dalvik and installed super user before rebooting.
After rebooting my phone is stuck on the boot screen now. (This also happened before I installed TWRP on my phone)
I've also tried this method: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Also no succes. I'm stuck in the bootscreen where it says 'cyanogen'.
EDIT: Managed to fix it eventually through: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061 (part 2) writing the command in TWRP.
Phone finally boots normally again.
RightHanded said:
Decided to unlock the bootloader through ADB. (bye bye data)
After I've unlocked it, I've tried installing TWRP.
Some minor problems occured but I can finally boot into TWRP through volume-down button + power button.
I've decided to download the stock ROM i've found on the OPO forums.
Couldn't acces my phone through normal methods, so I had to use ADB to push the files into my phone.
Installing the file through TWRP, wiped cache/dalvik and installed super user before rebooting.
After rebooting my phone is stuck on the boot screen now. (This also happened before I installed TWRP on my phone)
I've also tried this method: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Also no succes. I'm stuck in the bootscreen where it says 'cyanogen'.
Any other way to fix this problem?
Click to expand...
Click to collapse
Exactly what did you flash? Full filename please. No errors occurred?
Heisenberg said:
Exactly what did you flash? Full filename please. No errors occurred?
Click to expand...
Click to collapse
Hopefully the stock cyanogen OS.
First I've tried to flash cyanogenmod 12 through TWRP (file is found here: https://forums.oneplus.net/threads/cm12s-yng1tas17l-installation-guide-review-change-log.304615/)
Afterwards I was still stuck in bootscreen, so I've looked for another solution.
Which made me find this guide: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
After flashing this file (probably the same thing) the problem still remained.
Eventually after multiple wipes/factory resets (which did not solve the problem) I've entered the command in TWRP and after reboot it finally worked again.
So I basically flashed my phone twice, once through TWRPS and the other through the batch file (perhaps ADB?).
Also no errors occured which stopped the flashing and commands. Did have to reinstall TWRP and reboot instantly in it by holding the volume down button multiple times. This doesnt happen anymore though.
Only had to install google apps for CM12 (gapps), for which I used TWRP in recovery mode.
Currently reinstalling most apps on my phone and no problems yet.
Hello everyone
I own the Motorola Moto G ( 1st gen) xt1033 model. I had cm 13(latest release) flashed on it and my custom recovery is TWRP 2.8.4.0 and it was working fine until today after using it for around 2 months.
So what happened today is that while running an application, my Moto G shut down randomly( I don't know the reason for that),and it got stuck in bootloop ( Everytime I start it, the cm logo will appear and then it sometimes even shows my lock screen but instantly becomes black after that and most of the time its stuck only on the cm logo). After this I thought of restoring it back to the original firmware using this link: http://forum.xda-developers.com/showthread.php?t=2700502
I can get into fastboot mode but can't access the ADB as USB debugging mode was not enabled ( that's the main problem )
So following the procedures of that post, everything worked well on the log of the fastboot (no errors) but after that when I reboot my phone, again the cm logo appears (Even when I flashed it to stock 5.0.2 Lollipop!) and I can even get to my old lock screen sometimes and then instantly it goes black. Even if I try flashing a custom image like stock or some other ROM , it gives no effect as again the cm logo would appear.
I think this has to do with the fact that USB debugging mode was not enabled on it.
Also, I can't enter my recovery. When I use the standard procedure to get into fastboot (power button + volume (-) ) and select recovery, the TWRP splash screen comes then the screen turns black and normal reboot takes place( stuck on the cm head). I tried flashing different recoveries using fastboot (also tried mfastboot) like CWM and even TWRP again but still that bugged TWRP recovery remains.
I can't get to recovery neither can I boot up my phone. I can flash recovery or image files(It shows no errors flashing things, but no effect takes place :/ )
Can someone please help me in finding the solution for this problem? Thanks in advance
Just clear the data, cache and dalvik cache. Phone should boot
Hi all,
I thought it be good to warn all Alcatel Pixi 4 (4) owners. The current version of the stock rom of the 4034N, which is sold here in the NL has what I think is a terrible bug.
If you enable unlocking in the development options, go to the fastboot, all it takes is to unlock the flash and your phone will get stuck in the boot animation.
I tried to recover by formatting /data (/data is destroyed as could be expected to protect the userdata), but it does not solve the problem.
Flashing a custom ROM like CM13 solves this problem, but I bet this is the reason why I see so many calls on the Internet for Stock ROMs for the 4034N. Have not found a good stock ROM for it and also Alcatels Mobile Upgrade site does not seems to support the 4034N (probably still one software version for it, so no upgrade required yet?).
So better know what you are doing when messing with this phone.
Anybody got the same experience (I can confirm that this was tested by me and my friends with three different Pixi 4's)...
Best regards,
Peter
Good news!
I found out that there is a global site from Alcatel where you can find an update of Alcatels Mobile_Upgrade_S_4.5.9 which DOES support the 4043N.
The good news is not only that this software can bring your phone back to stock ROM, but also that if your Flash is unlocked before you recover, it is still unlocked after the recovery. So rooting is very simple then. Cost me 2 minutes to do it:
adb boot recovery.img (you can boot the twrp bootimage from ADB, no need to flash it) and then directly install the superuser.zip
Presto!
I think I'm seeing the same problem with a 4034X (UK variant, as sold by Tesco Mobile). Unfortunately, the mobile update software isn't working for me as it's detecting that I've already got the latest version of the ROM installed already and won't let me install it again. AIUI, the CM13 system has a few issues, so I'd rather not go that root, so would still like a stock ROM if at all possible. Anyone have any pointers?
Hmm. Have managed to get beyond the resetting user data boot loop with the following procedure:
* boot to recovery (power + vol up)
* from recovery menu, choose "boot to bootloader"
* at bootloader, connect via USB to PC
* run "fastboot -w"
* run "fastboot boot <filename for twrp recovery image>"
* at twrp recovery menu, run the standard "wipe" options
* reboot
Haven't yet finished booting, but it's gone to the standard boot animation, which I never succeeded in getting to before.
Update: 8 minutes and counting into the boot process. Doesn't look like it's going to work.
One question worth asking: does this mean that *all* operations that cause a factory reset on an affected 4034 cause a boot loop? Or is it only unlocking the boot loader?
I managed to soft brick my 4034X simply by allowing my email program to encrypt the device. The encryption apparently failed and now it's stuck on boot animation. As @jh3141 said, the Acatel upgrade tool doesn't work. I guess I need to find a stock ROM, but my Googling hasn't found one yet. Can anyone help?
palbeda said:
I found out that there is a global site from Alcatel where you can find an update of Alcatels Mobile_Upgrade_S_4.5.9 which DOES support the 4043N.
The good news is not only that this software can bring your phone back to stock ROM, but also that if your Flash is unlocked before you recover, it is still unlocked after the recovery. So rooting is very simple then. Cost me 2 minutes to do it:
adb boot recovery.img (you can boot the twrp bootimage from ADB, no need to flash it) and then directly install the superuser.zip
Presto!
Click to expand...
Click to collapse
Same here with a 4034D - got my phone back alive and still a unlocked bootloader. rooted it, works great.
Thanks!! :good:
i need help
Tampopo said:
Same here with a 4034D - got my phone back alive and still a unlocked bootloader. rooted it, works great.
Thanks!! :good:
Click to expand...
Click to collapse
Can you brake this down for me? am kind of new to all this but i really need to root my device
jh3141 said:
Hmm. Have managed to get beyond the resetting user data boot loop with the following procedure:
* boot to recovery (power + vol up)
* from recovery menu, choose "boot to bootloader"
* at bootloader, connect via USB to PC
* run "fastboot -w"
* run "fastboot boot <filename for twrp recovery image>"
* at twrp recovery menu, run the standard "wipe" options
* reboot
Haven't yet finished booting, but it's gone to the standard boot animation, which I never succeeded in getting to before.
Update: 8 minutes and counting into the boot process. Doesn't look like it's going to work.
Click to expand...
Click to collapse
Any luck with the UK version 4034X?
I'm stuck in the booting process just like you were.
me too - Pixi 4(4) chaos on unlocking.
Absolutely the same experience here.
I have nuked 2 of these trying to unlock. It is a brilliant phone, but this is a painful feature - as you describe.
My history is in one of the threads on this site. - I agree, I would love a stock ROM for it.
palbeda said:
Hi all,
I thought it be good to warn all Alcatel Pixi 4 (4) owners. The current version of the stock rom of the 4034N, which is sold here in the NL has what I think is a terrible bug.
If you enable unlocking in the development options, go to the fastboot, all it takes is to unlock the flash and your phone will get stuck in the boot animation.
I tried to recover by formatting /data (/data is destroyed as could be expected to protect the userdata), but it does not solve the problem.
Flashing a custom ROM like CM13 solves this problem, but I bet this is the reason why I see so many calls on the Internet for Stock ROMs for the 4034N. Have not found a good stock ROM for it and also Alcatels Mobile Upgrade site does not seems to support the 4034N (probably still one software version for it, so no upgrade required yet?).
So better know what you are doing when messing with this phone.
Anybody got the same experience (I can confirm that this was tested by me and my friends with three different Pixi 4's)...
Best regards,
Peter
Click to expand...
Click to collapse
I also softbricked my 4034X after unlocking the bootloader and couldn't get the phone to boot into recovery or the bootloader. I eventually managed to flash a stock ROM with SP Flashtool as described here https://www.getdroidtips.com/install-official-stock-rom-on-alcatel-pixi-4-4/ - this restored the ability to boot into recovery or bootloader but the ROM wouldn't boot so I couldn't enable developer settings to allow OEM unlocking. I then tried flashing the ROM for the dual-SIM version of the 4034X (risky!) and this booted and I was able to unlock the bootloader and flash TWRP recovery. The next problem was when & flashed CM13 and got an error message saying that TWRP couldn't access /data. It then got stuck in a recovery bootloop. Next I used TWRP to format all the partitions but it still couldn't access /data and broke the ability of the Mobile Upgrade Tool to read the phone. My next step is to try flashing a different custom recovery but I'm rapidly losing the will to live and would be very interested in any suggestions.
UPDATE - got it sorted by re-flashing the dual-SIM 4034X ROM (even though I have the single SIM version!), flashing ctr-6.6-4034 recovery, doing a normal wipe then formatting the /data partition then flashed CM13. I guess the data partition must have got corrupted.
I have exactly the same problem with pixi 4 4043f. I unlocked bootloader and then flashed following your instructions on that link you shared. But I see is a white screen frozen no options shown just booting voice behind.... I have flashed it several times but same results I still cant entry fastboot or recovery... Volume down + power or volume up + power dn take me anywhere just that frozen white screen with booting ring tone in the back and thats it... Kindly guide me
i had a similar problem, but i always wanted to flash cm13, so i was fine.
There is an amazing thread here for our device.
For those of you with the 4034X, i have ported cm13 to it specifically, bu there are too many bugs, but if anyone wants it, just tell me!
also, can i just say, softbrick if you oem lock aswell :,(
i wanted to test something, but after fastboot oem lock, and then fastboot reboot, i get an android being repaired? key combo's not working, adb/fastboot not responding, can't remember how i fixed it when i oem unlocked ...
edit-
got into recovery with key combo, now it's just to fix it!
Can any of you guys with the 4034N try this method of rooting? Without unlocking the bootloader?
Masgisk Rooting
kirito9 said:
Can any of you guys with the 4034N try this method of rooting? Without unlocking the bootloader?
Masgisk Rooting
Click to expand...
Click to collapse
For reference: I tried this on a stock 4034X and it failed (couldn't persuade it to boot the custom recovery without going through the full unlock process). Fortunately, there are now copies of the stock ROM available for download (e.g. https://androidfrog.com/a3nr9) so with any luck I won't need to go back to the dodgy CM13 port that constantly runs out of memory and soft-reboots...
Update: I've installed the stock ROM I linked to above, and it seems to be working pretty well. Only issue was that the scatter file that came with it was apparently broken. Fortunately, one that I had hanging around from attempts to fix this problem last time seemed to work with it. I've attached that to this message in case anyone else needs it.
jh3141 said:
For reference: I tried this on a stock 4034X and it failed (couldn't persuade it to boot the custom recovery without going through the full unlock process). Fortunately, there are now copies of the stock ROM available for download (e.g. https://androidfrog.com/a3nr9) so with any luck I won't need to go back to the dodgy CM13 port that constantly runs out of memory and soft-reboots...
Click to expand...
Click to collapse
Thanks, I'll be sure to add a notice for 4034X users in the Magisk guide. I have yet to see a stable CM13 ROM for MT6580 with 3.18.19 kernel. There seems to be an issue with this device chip and ROMs.
Finally got root on the Pixi4-4034
Hi everyone,
yeah I finally managed to root the alcatel Pixi 4-4 (4034) (3G MODEL). It was really tricky and there are quite some issues you have to deal with.
Therefore please read carefully my instructions and remember I am not responsible for any inconvenience, do it at your own risk.
First of all you have to unlock the bootloader and here comes the first problem. On the Pixi4 this operation leads to a sotfbick because the unlocking process deletes completely the data-partition. The phone can't boot anymore and ends in a bootloop.
To resolve this problem you must reflash the phone with SP-Flash-Tool. After reflashing the bootloader remains unlocked so that you should be able to continue with the rooting process. The second problem is that I could find only one working ROM for flashing. It is for the 4034X, my phone was a 4034D (dual SIM), after flashing I had an 4034X what means that my Pixi became a single-SIM phone, I can live with that.
Here are the necessary steps to obtain root on the Pixi4
1. UNLOCKING BOOTLOADER
- Go to settings -> about phone -> hit many times on "build number" till developer message appears
- Enable "OEM unlocking" located in developer options.
- Switch also "USB debugging" on
- Open the command prompt window (cmd)
- Connect the phone to the PC
- Boot into fastboot-mode by typing "adb reboot bootloader"
- Confirm the debug authorization window on the phone, check "always allow from this computer" (afterwards phone should boot into fastboot, otherwise retype the command above)
- Unlock bootloader by typing "fastboot oem unlock"
WARNING: this deletes the data-partition leading in a softbrick and bootloop,
you have to reflash the phone afterwards to continue rooting!
- Confirm the unlocking with the volume-up key
2. REFLASHING THE PHONE
- I found only this working firmware for the 4034X on this page like described by jh3141:
https://forum.xda-developers.com/android/general/warning-current-pixi-4-4-4034n-t3463154/page2
- You have also to use the scatter file described by jh3141
- After loading the scatter-file in SP-Flash-Tool you have to link the missing img-files in the SP-Flash-Tool-Window
- If you flash the 4034X firmware over an 4034D you will end in a single-SIM phone instead of a dual-SIM.
- After flashing the phone will boot again so that you can continue with flashing the twrp-img.
3. ROOTING THE PHONE
- To root the phone you have to install the twrp-image, the one for the Pixi 4034 you find it here:
https://forum.xda-developers.com/showpost.php?p=68049551&postcount=97
- Download and untar the file at the bottom of the page: twrp-3.1.0-0-4034.tar
- Open the command prompt window (cmd)
- Connect the phone to the PC
- Boot into fastboot-mode by typing "adb reboot bootloader"
- Flash twrp by typing "fastboot flash recovery twrp-3.1.0-0-4034.img"
- Download Super-SU "SR1-SuperSU-v2.78-SR1-20160915123031.zip" from
https://download.chainfire.eu/1003/SuperSU/
and put the zip-file on the phone (external or internal storage)
- With the phone switched off boot into twrp by holding power and volume-up keys togehter
- In twrp go to "Advanced" -> "Terminal" -> Type the following code:
echo "SYSTEMLESS=true" > /data/.supersu
- Go back and choose "Install" -> flash the Super-Su-file (SR1-SuperSU-v2.78-SR1-20160915123031.zip)
- Reboot and you’re done, you have root and super-su on the PIXI4
- If you want to uninstall system-apps proceed to the next step.
4. UNINSTALLING BLOADWARE APPS
- You can’t uninstall system-apps directly from the Android-OS,
if you delete the apps with some uninstall-tools it’s strange but the phone will reinstall them after a reboot.
- To succeed you must uninstall the apps in twrp
- Be careful, uninstalling the wrong apps will end in a bootloop or bootfreeze and you will have to reflash the phone starting at step 2.
- Boot into twrp -> go to "Mount" -> check "System" -> go back and choose "Advanced" -> "File Manager"
- In file-manager navigate to the appropriate app-folders and delete the .apk-files
- IMPORTANT: before rebooting you have to wipe the dalvik-cache
- Go to "Wipe" -> "Advanced Wipe" -> CHECK ONLY "Dalvik / ART Cache"
- Confirm wipe and reboot
I personally like the Pixi4-4034, it’s a very small one that is very useful as second phone especially on holidays .
Have fun.
i bricked my alcatel
i have an alcatel pixi 4 (4) 4034x and when i unlocked the bootloader it softbricked my alcatel, the only solution i did was relflash it using spflashtools
same problem
palbeda said:
I found out that there is a global site from Alcatel where you can find an update of Alcatels Mobile_Upgrade_S_4.5.9 which DOES support the 4043N.
The good news is not only that this software can bring your phone back to stock ROM, but also that if your Flash is unlocked before you recover, it is still unlocked after the recovery. So rooting is very simple then. Cost me 2 minutes to do it:
adb boot recovery.img (you can boot the twrp bootimage from ADB, no need to flash it) and then directly install the superuser.zip
Presto!
Click to expand...
Click to collapse
I have exactly the same problem. But I haven't been able to find this Mobile_Upgrade_S_4.5.9. Any help will be greatly appreciated,
thnx,
Herman
update: i found the mobile upgrade tool. But it says the latest firmware is already installed. Earlier i tried spft, flashing seemed to go well but the phone stays in animation/bootloop.
Can anybody help?
Hi, I have a Verizon variant of the OG Pixel, and decided to try to unlock the bootloader when I found this guide recently.
https://www.xda-developers.com/how-to-unlock-bootloader-verizon-google-pixel-xl-running-android-10/
So my phone was working properly before I did anything following this guide, it did not bootloop or had any problem whatsoever.
I'm not sure what version of the OS I had before I wipe/factory reset and sideload ota image, but when I did the first factory reset, it boot into the system and through all the setup process without any problem, so I decided to factory reset again through the settings menu.
This time I did not let it boot into system but going straight into recovery, factory reset through recovery, sideload OTA image, then factory reset again through recovery like the guide said, then reboot.
Now I got a constantly bootloop device. It stuck in Google logo for longer then I think it needs, then reboot; sometimes it get to the G logo but freezes then reboot; sometimes it couldn't finish the G logo animation and freezes there then reboot; sometimes it goes through Google logo, G logo animation, Android logo on the bottom, then freezes and reboot; the furthest it make so far was the progress bar animation under the G logo but freezes after all and reboot with no luck.
Since this is a locked devices, I could not:
-Wipe anything through fastboot
-Flash anything through fastboot
-Boot into a custom recovery image through fastboot
-Downgrade through adb sideload
-Push files through adb (I have no usable system or custom recovery, no listed adb devices in recovery, push command in adb sideload mode was not permitted.)
Things I've tried:
-Factory reset through recovery
-Sideload OTA image with different USB cables or computers (It only allows me to sideload the latest OTA image, no downgrade premitted, and the result was always success with status 0 without any error message using any combination.)
-Smashed the power button to make sure it is not the case that my power button was stucked
-Make sure it has enough power in the battery (Charge while powered off did shows the charging animation though.)
-Tap on the phone/massage the phone like some Youtube video siad
-Put it into a freezer like some article said
I think I've done anything I could. I thought it was software problem since I had a properly working device just not a long time ago, and have no problem booting into bootloader or recovery, had no error message when I sideload OTA image and factory reset, but now I begin thinking that this could be caused by faulty hardware maybe a non-wetting joint or something (similar symptom did happened on my Nexus 7 2013 which will not boot unless I apply some pressure on the back where motherboard underlies.) But before I did all these factory reset and OTA thing it has no problem at all, so I still not fully convinced that my beloved phone becomes a paperweight just because the hardware suddenly decides to loose a solder point or something.
Did this happened to you guys? Is there something I can do that I missed? Or any way I can get my phone back alive again?