Dear all,
Desperately need help and deeply appreciate if anyone could shed some light.
I recently upgrade my rom. The rom upgrade without problem, after I installed couple of applications, the phone was hang after restart.
I tried re-flashing the rom couple times and it seems everytime restart, the rom will hang.
After several re-flashing, my phone now stuck at the screen where, it stated, system is being configure and stuck on this screen forever.
I tried reset the rom by Vol-down & back key as well as vol-down & center key, Rom upgrade completed successfully but upon phone restart, my phone keep stuck at the same screen.
I do noticed that, by resetting the phone into bootloader mode (reset with Vol-Down, back key) with USB cable attached to my phone, the bootloader detected USB connection but time out.
Is there any software which I should install on my laptop which allow me to transfer another diamimg.nbh to this phone?
Thank you
decent_devil said:
Dear all,
Desperately need help and deeply appreciate if anyone could shed some light.
I recently upgrade my rom. The rom upgrade without problem, after I installed couple of applications, the phone was hang after restart.
I tried re-flashing the rom couple times and it seems everytime restart, the rom will hang.
After several re-flashing, my phone now stuck at the screen where, it stated, system is being configure and stuck on this screen forever.
I tried reset the rom by Vol-down & back key as well as vol-down & center key, Rom upgrade completed successfully but upon phone restart, my phone keep stuck at the same screen.
I do noticed that, by resetting the phone into bootloader mode (reset with Vol-Down, back key) with USB cable attached to my phone, the bootloader detected USB connection but time out.
Is there any software which I should install on my laptop which allow me to transfer another diamimg.nbh to this phone?
Thank you
Click to expand...
Click to collapse
you should try mtty...it formats your phone and solves all the problem like the yours..a guide to use it is in a sticky thread
or you can try downloading any rom and usually the chef includes a file called customRUU.exe..put your phone in bootloader mode then flash trough customRUU.exe
HELICOPTER88 said:
you should try mtty...it formats your phone and solves all the problem like the yours..a guide to use it is in a sticky thread
or you can try downloading any rom and usually the chef includes a file called customRUU.exe..put your phone in bootloader mode then flash trough customRUU.exe
Click to expand...
Click to collapse
Thanks, Managed to extract one Rom and restore my phone via customRUU.exe.
Hey!
Im new to this forum but there seems to be a lot of experts here so i thought i'd try and see if anyone could help me!
Yesterday i put my desire to charge and after one hour i came back and it was showing the boot screen! The white background with the 3 green letters HTC! so i took out the battery and put it in again and restarted the phone but it only gets to that screen vibrates like 10 times and then hangs there! tried waiting for it for 30 min but nothing...
So then i tried to hard reset it and cleared the storage! but afterwards still the same!
Also when in "recovery mode" i sometimes see some green text flashing by for just a sec saying something like "warning...no image...."
Everything is in its original state, i havent rooted or reflashed it or anything... but i am willing to do so if it can solve my problems since warranty matters in my case will take ages!
The phones language is Swedish btw!
Can anyone help me?? its first now that u realize how much the phone means to you Miss my desire!
it sounds like the firmware is somehow corrupted. If you can boot the phone by pressing power and volume down, this will take you to the bootloader. From here you should be able to root the handset by following any number of threads here or on modaco!
Then I'd go Here and install this recovery. From then on you can choose a custom or stock rom to install.
You need to know though that rooting will void your warranty.
Have you also tried booting the phone normally with the SD card removed?
Hi guys, let me preface this by saying I am not a total noob so I have tried the usual tricks to get into the damn bootloader.
I rebooted my phone and when it was restarting it goes to the HTC boot logo, after a few minutes of waiting I realised that this situation was not changing anytime soon so held power button and allowed the device to reboot. As it did this I hold down the volume key as normal - vibrate, big white screen with the HTC boot logo again.
I have tried this a few times, always with the same result, the phone does not want to go into the bootloader for some reason I cannot figure.
Now I am looking for either a brute force way to get in or a nifty trick one of you might have found, as my phone is just sat on the HTC boot screen I need to get this dealt with ASAP so swift responses are REALLY appreciated.
thanks
Just to add, I am trying to use adb, so far I can use the reboot-bootloader command and the phone will reboot, flash up the bootloader and then back to the htc boot screen again. I am trying a fast fingers way to get into recovery (hoping I can select it quickly before it decides otherwise)
I think I may have a way in although would still love a bit of guidance.
I can now get to the bootloader, any attempts to get to CWM leads me to see the very first hint of the CWM logo but then it goes straight back into bootloop again at the HTC screen. I can send adb commands but get an error message when I try anything via fastboot or just waiting for device.
Right now I dont really mind if I have to flash each of the boot.img, CWM, rom - any of it from scratch, as long as I can resurrect the thing and most importantly get it done before I fall asleep - I doubt that the screen on constantly is going to do the phone any good
**edit, I can get into fastboot. I tried the fastboot reboot-bootloader command and it worked
My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.
I would fastboot latest factory image.
Just hold vol- when a reboot comes it will go into bootloader.
piz333 said:
My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.
Click to expand...
Click to collapse
Sounds like you were coming from the April 2017 update to the May 2017 OTA update. The May update included a new bootloader which performs additional verification on the boot image. I suspect that when you installed TWRP and rebooted, the May bootloader detects the changes TWRP installation made to your boot image and aborts the boot process resulting in your bootloop. Additional detail and information can be found in the linked thread and solution should be towards the end of the thread. You have a few options I think (assuming you can get into fastboot/recovery mode) - you can temporarily resolve by reverting back to the April 2017 bootloader which does not have the additional boot verification procedure or you can follow the steps to flash Chainfire's VerifiedBootSigner.zip if you prefer to get fully on the May update (including the May bootloader). Details are in the thread below. Good luck!
https://forum.xda-developers.com/pixel-xl/how-to/images-t3599709
piz333 said:
My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.
Click to expand...
Click to collapse
Just started with me today too.
I cannot get into recovery or boot loader
rebooting using the hard button just brings up this Dump to EXT4 and then into the ROM that is havnig a ish ton of force closes.
My plan is to back up some stuff I need to copy off the phone and then start factory reset from within settings.
EDIT:
I was rooted running stock
All i did was run a backup in TWRP
issues started after reooting.
Once i factory reset and re Root i will see if I can restore backup, maybe
sb1893 said:
Sounds like you were coming from the April 2017 update to the May 2017 OTA update. The May update included a new bootloader which performs additional verification on the boot image. I suspect that when you installed TWRP and rebooted, the May bootloader detects the changes TWRP installation made to your boot image and aborts the boot process resulting in your bootloop. Additional detail and information can be found in the linked thread and solution should be towards the end of the thread. You have a few options I think (assuming you can get into fastboot/recovery mode) - you can temporarily resolve by reverting back to the April 2017 bootloader which does not have the additional boot verification procedure or you can follow the steps to flash Chainfire's VerifiedBootSigner.zip if you prefer to get fully on the May update (including the May bootloader). Details are in the thread below. Good luck!
https://forum.xda-developers.com/pixel-xl/how-to/images-t3599709
Click to expand...
Click to collapse
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April.
I ran this:
Code:
fastboot set_active a
because I noticed that flashing the bootloader was always going to b. After flashing the bootloader again and seeing it go to a, the phone boots normally. I'm going to let the May update happen and wait to root again until after that.
One thing, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful. You and @mikaole got me through this. Thanks!
piz333 said:
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April. How do I revert the bootloader?
Also, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful so far. Thanks!
Click to expand...
Click to collapse
They flashing all the parts of the image manually. Something like this happened to a buddy of mine and using the flash all wouldn't fix. He couldn't get the device to boot until he did all the images manually.
piz333 said:
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April.
I ran this:
Code:
fastboot set_active a
because I noticed that flashing the bootloader was always going to b. After flashing the bootloader again and seeing it go to a, the phone boots normally. I'm going to let the May update happen and wait to root again until after that.
One thing, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful. You and @mikaole got me through this. Thanks!
Click to expand...
Click to collapse
Glad you got it working. I checked and I did link the thread I intended to. Starting at post #57 onward from that thread has the information on how to update to the May update and leverage Chainfire's VerifiedBootSigner.zip.
Thx,
S
Pixel bootloop
Hey guys, this is the only thread thqt i found here on XDA about pixel and pixel XL bootloop issue.
I'm about to buy a used Pixel 1st gen phone for really great deal, because it is in this bootloop. As the owner sad, it was on the Oreo upgrade. I'm wondering if its possible to fix it... What you guys say?
Thanks!!
rosendomurilo said:
Hey guys, this is the only thread thqt i found here on XDA about pixel and pixel XL bootloop issue.
I'm about to buy a used Pixel 1st gen phone for really great deal, because it is in this bootloop. As the owner sad, it was on the Oreo upgrade. I'm wondering if its possible to fix it... What you guys say?
Thanks!!
Click to expand...
Click to collapse
Well that depends. If the owner unlock the bootloader and then relocked it it could have screwed it up depending on what he was doing with it at the time resulting in a bootloop that cannot be fixed because it's hard brick now. I say can't be fixed only because the only way to get it fixed as far as I know is to contact someone here on the forums I'm not exactly sure who it is but they do fix hard bricked pixels for money. If I were you I would try and figure out if that's the case before buying it.
Phalanx7621 said:
Well that depends. If the owner unlock the bootloader and then relocked it it could have screwed it up depending on what he was doing with it at the time resulting in a bootloop that cannot be fixed because it's hard brick now. I say can't be fixed only because the only way to get it fixed as far as I know is to contact someone here on the forums I'm not exactly sure who it is but they do fix hard bricked pixels for money. If I were you I would try and figure out if that's the case before buying it.
Click to expand...
Click to collapse
Yes, that's my biggest fear right now... He sad he never had done anything like root or custom rom, he just had done a system update and the phone never boot correctly again.
I have a little bit of knowledge in android, i was thinking if just putting a custom rom it wouldn't solve, because i had other devices that i had put in bootloop and i was able to fix it just putting a custom rom...
rosendomurilo said:
Yes, that's my biggest fear right now... He sad he never had done anything like root or custom rom, he just had done a system update and the phone never boot correctly again.
I have a little bit of knowledge in android, i was thinking if just putting a custom rom it wouldn't solve, because i had other devices that i had put in bootloop and i was able to fix it just putting a custom rom...
Click to expand...
Click to collapse
Can you get to recovery ?
Phalanx7621 said:
Can you get to recovery ?
Click to expand...
Click to collapse
I'm not with the phone right now, I'm going to buy it next week... Correct if I am wrong, but if i can get to recovery or bootloader i can fix it, right?
I think he had tried to unlock the bootloader but without experience had bricked...
rosendomurilo said:
I'm not with the phone right now, I'm going to buy it next week... Correct if I am wrong, but if i can get to recovery or bootloader i can fix it, right?
I think he had tried to unlock the bootloader but without experience had bricked...
Click to expand...
Click to collapse
Yeah if you can get into recovery you can side load things. And if you can get to the boot loader screen you're fine.
Phalanx7621 said:
Yeah if you can get into recovery you can side load things. And if you can get to the boot loader screen you're fine.
Click to expand...
Click to collapse
Perfect! Just as I expected... Probably i will do an youtube guide if it works... Thanks bro!
Hey, so I bought a new Zenfone 2 which arrived yesterday.
But it had only Android 5.0 on it with no option to update the system.
After some googling I found out, that I have got an CN phone, but have/need WW software.
So I tried to get Android M via this tutorial:
https://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
I followed along, until point 4. I had no idea how to get the Firmware OTA on the phone now, as I had no option to access the phone storgae via PC?
So I thought, let's go into recovery mode, recover the system, put the OTA on the device first, and then follow the tutorial again.
But now, when I want to start the phone, this screen appears: https://i.ytimg.com/vi/T5GlOGbL4Lc/maxresdefault.jpg , then after 1-2 minutes it vibrates two times, and this screen appears again.
I think it's some kind of a bootloop, so I want to access the fastboot-mode to restore the phone somehow with a original firmware, but I can't access the fastboot mode anymore.
If I hold down [Power]+[Volume Up], the phone just vibrates two times and boots normally. If I hold down both, and release [Power] or [Volume Up] earlier (after around 5 seconds), it revolves in the same screen again.
So any idea how to save my phone?
Okay, with "xFSTK-Downlaoder" I managed to get my phone back into Fastboot Mode. Here is how to do it.
Then, post number 8 in this thread solved the problem.
I flashed a totally new Android 6.0 Marshmallow WW on my CN-Zenfone by erasing the whole memory of the phone, including recovery partition and boot table, and creating it new. Now everything works great.
If anyone needs help with this problem, feel free to contact me. (I hope I get email-notification if someone pm's me haha)