So my girlfriend installed a wallpaper app (not sure which) on her Vodafone branded Arc, ever since then the phone freezes at the lock screen after booting. The unlock controls don't work and nothing else seems to either. If the screen times out or power button is pressed, screen goes off but won't come on again.
Would be happy to reset the phone but nothing works for hard reset (tried side buttons plus power and volume down or up and power) and we cannot get to the menus to do a soft reset.
Have also tried the SE PC companion software to update the phone but this requires you to change some things in the phone's menu after connecting too- which we can't...
Help!
Use Update Service form SE.
Power off
Then plug your usb while pressing Back Button.
It will works.
or
Use Flash tool.
Related
Ok so lets start from the beginning. I dropped my phone and although no visible physical damage is visible my volume up button stopped working. When i used to turn on my phone the volume display wouldnt quit showing unless i pressed the volume down button, but volume up would not respond (im guessing vol up is constantly pressed)
I decided to flash my phone, but i also decided to perform Task29 (format internal storage) (From Here)because i have been flashing quite a bit. While doing this i completely forgot that my vol up button isnt working... so i was stuck on the first boot screen, with no internal memory, and since my vol up button is broken no way to get into the bootloader.
I decided to turn it off and leave my phone of the charger and go to sleep (because thats just what i do at night)
In the morning my phone would not turn on at all
Any ideas? I cant send it for repair to T-Mo because its HardSPL and i cant really return it to stock if it wouldnt turn on :/
Edit: Ok i think the non powering issue is battery, the main concern however is, how to enter bootloader without the use of the volume buttons... or flash a rom in any way so that the phone is actually usable.
Thanks in advance
Ok somehow on the millionth's time of trying to get into the bootloader (holding the vol down button) it finally worked =]
Hello all,
I've searched and found some things, but nothing that matches my problem.
HTC Kaiser, branded Swisscom. HardSPL, I don't remember the version. Trying to get to tricolor screen, no key combo works. Camera+reset w/stylus, camera+power, even the two soft keys to reinstall the rom in memory.
After pulling the battery (and waiting more than 5 minutes) and inserting again, pushing the power button turns on the green LED, but goes no further, even after waiting up to 10 minutes. Pulling the battery, then plugging in the USB charger (without presses the power button) will flash a white screen after 7 seconds, then a pause of another 10 seconds, then the phone boots in to Android (again, without pushing the power button, just plugging in the USB cable.
Once in Android, everything works (except the factory reset, it just hangs forever). I need to install WM 6.5 ROM.
Tried the KAISDIAG.NBH and the 329 HardSPL recovery, but no reaction and still can't get to the tricolor.
One last piece of information, when I plug in the USB data cable, the phone flashes the "USB connected" message, and then repeatedly flashes it again every 3 seconds. The computer makes the USB connected sound, but no communication and the KaiserCustomRUU.exe can't see the phone.
Any suggestions to get to the tricolor? It unusual to turn on the phone by just plugging in the USB cable.
Thank you and great work.
Try power+camera+stylus pressing the reset.
A while back the charging behaviour was changed, so that now plugging in a charger, or usb, boots the phone, ( previously we could not charge if it was switched off).
Your problem of `losing` the bootloader has been seen before, but is rare, and seems to have no definite cause, the last time I remember seeing it turned out to be a faulty camera button.
Sent from my HTC Dream using Tapatalk
Thanks and one more question
Thanks Zenity.
I'll continue working on it. One quick question, is there a command in Android to force a hard reset or to the boot loader?
Camera Button
Ok, after searching more (due to Zenity's suggestion) and reading other threads, I don't think it's a faulty (Fawlty?) camera button.
Somehow, the phone takes along time to boot, and must use some info from the bootloader, as it loads Android.
But all attempts to get into the bootloader fail. I can't establish communication by USB, but I think I will focus my efforts there. I've pushed and help all the buttons in different combinations for too long.
I'll let you know, and thanks again!
Ok, done some research into way to detect that the camera button is functioning, ( since this button is vital in getting the bootloader), no luck yet, but research continues, looking at remapping the camera button using atools, just so i can get a response of some sort, ( normally the camera button does nothing in android, it's unmapped).
Edit: nope, atools won't help, won't let me remap the camera button.
Atools-keymapper remap the key only in the android GUI not in kernel so any change doesn't effect directly the kernel.
Yeah, realised that, just thought there might have been an easy way of diagnosing the camera button, to see if it was at least functioning, but if it's not enabled at kernel level then it will be difficult to test without disassembly and getting a meter on it.
Sent from my HTC Dream using Tapatalk
Update - Android.process.acore
Hey all, still trying to connect by USB to use the CustomRUU tool. Now when I plug in the USB, I get a repeating 'Process android.process.acore has stopped etc".
when I click force close, it pops up again and again.
Pulled the battery, and rebooted. Now it boots repeatedly, it shows the splash screen, right when it should go to the Android home screen, it reboots.
Any ideas? Thank you!
probable that the FC and subsequent reboot corrupted the data partition, which is known to happen when the device shuts down unexpectedly.
You can try a 'fix permissions', and 'clear dalvik cache', but normally it takes a wipe and re-install of the system, you may get away with not clearing data, but it's often safer to go for the full wipe of system and data.
Hi there
I have succesfully installed some different romes, and i did the preformed Hard SPL.
but then i downloaded jackos s2 rom, witch contained a folder named Recommended tool (task29). I thourght, if it's recommended, why not. But after the successful installation. it tried to reboot, but it does not go further than the first htc intro / loading screen.
I have read other similair problems, where thay, press the volume button and power, and then enter bootloader, but i doesnt seem to work with me, also. thay do it while the phone is off... as soon as i put the battery in, it starts.
But i am able to do a hard reset, with power button+call+hangup+reset. But it leads to no good.
Can i buy an SD card, and do some magic there, without needing to pull down bootloader, or is it bricket?
hope you can help
I accually just tried entering the bootloade, by holding the buttons down while inserting the battery, that worked, i guess i can find my way from here.
In the Task29 instructions (the thread is pinned to the top of the ROM Development forum) it says:
When phone boots to "Touch Pro 2" screen (or whatever your splash screen happens to be), I hold down the volume down button while hitting the reset button
Where it says "reset button" I think he means the soft reset button (that you press with the stylus) under the battery cover, not the power button (which to me is not a "reset button" - but its a matter of semantics and I can see the confusion). The combination of volume down and power button (on top of phone) only works when the phone is off, which of course does not apply in this case. Holding down the Volume Down button while hitting the soft reset works, and this is what I have done for the past upteenth ROM flashes. Although I think the first time I flashed a custom ROM, I got confused and pulled the battery like you did. Pulling the battery works. But the soft reset button does the same thing, and according to some, is safer.
Hello all
I tried to software reset my phone as I wanted to give it to another family member. However after factory reset (though software) it asks for a PIN, and no PIN's I have used on the phone actually works?!?
I want to get into recovery menu to do wipe data / factory reset to remove the pin code issue (I hope).
However I cannot even turn off the phone without the PIN..
I tried Power + Volume down (restart), and as soon as it turns off the screen try to switch to Power + Volume Up, however it seems to continue doing normal bootup. I tried multiple times, cannot seems to get the sweet spot.
Any tips to what I can do?
I could try PC connection and ADB? Else I need to wait until battery is drained, then try to start it with power + Volume Up when charging / turning it on again?
So I am normally using my phone scrolling through social media but it suddenly froze so I tried to hard reset it, but it goes in to a bootloop without any display on the screen. I could tell it is on a bootloop because of the repeating vibration everytime the phone boots up.
My device is Poco F3 (alioth) Running stock MIUI 12.5 bootloader unlocked and rooted with Magisk.
Things I have tried:
Long pressing power button, long pressing both power button and volume down button, long pressing power and volume up button, then long pressing all of them.
Plugging it on my PC but it doesn't even detect it. Tried inputting
Code:
adb devices
and
Code:
fastboot devices
Still doesn't work. I even made sure that my drivers are working so I tried it on my brothers Poco F3 and the PC can detect his phone through ADB commands.
Waiting for a day if it magically turns on again. Nope.
Charging it up because maybe the battery is low. Nope.
At this point my only two choices is opening up the back panel then replugging the battery so it completely turns off and hopefully boots up. But its a risky task since I don't have special tools to open up my phone, and my another choice is just bring it on a service center.
rururi said:
So I am normally using my phone scrolling through social media but it suddenly froze so I tried to hard reset it, but it goes in to a bootloop without any display on the screen. I could tell it is on a bootloop because of the repeating vibration everytime the phone boots up.
My device is Poco F3 (alioth) Running stock MIUI 12.5 bootloader unlocked and rooted with Magisk.
Things I have tried:
Long pressing power button, long pressing both power button and volume down button, long pressing power and volume up button, then long pressing all of them.
Plugging it on my PC but it doesn't even detect it. Tried inputting
Code:
adb devices
and
Code:
fastboot devices
Still doesn't work. I even made sure that my drivers are working so I tried it on my brothers Poco F3 and the PC can detect his phone through ADB commands.
Waiting for a day if it magically turns on again. Nope.
Charging it up because maybe the battery is low. Nope.
At this point my only two choices is opening up the back panel then replugging the battery so it completely turns off and hopefully boots up. But its a risky task since I don't have special tools to open up my phone, and my another choice is just bring it on a service center.
Click to expand...
Click to collapse
If the phone is bootloader locked don't do anything, take it to service center it's out of your hands.
If service center intends to charge you something well you could find some people online with edl accounts to do flashing for you but this sounds like hardware issue if you don't see poco logo ...
Edit: Sry didn't read the post fully - did u try fastboot devices when in fastboot mode - volume down and power ? If it is recognized and bootloader unlocked you can try flashing - go with xiaomi firmware, last thing you want is to be stuck on custom firmware when you take it in for repair - again only if bootloader is unlocked
since your brother pc can recognize, tried fastboot miui.eu on his pc
but I had this problem before and the only solution is to change mainboard on the xiaomi service center.
rururi said:
So I am normally using my phone scrolling through social media but it suddenly froze so I tried to hard reset it, but it goes in to a bootloop without any display on the screen. I could tell it is on a bootloop because of the repeating vibration everytime the phone boots up.
My device is Poco F3 (alioth) Running stock MIUI 12.5 bootloader unlocked and rooted with Magisk.
Things I have tried:
Long pressing power button, long pressing both power button and volume down button, long pressing power and volume up button, then long pressing all of them.
Plugging it on my PC but it doesn't even detect it. Tried inputting
Code:
adb devices
and
Code:
fastboot devices
Still doesn't work. I even made sure that my drivers are working so I tried it on my brothers Poco F3 and the PC can detect his phone through ADB commands.
Waiting for a day if it magically turns on again. Nope.
Charging it up because maybe the battery is low. Nope.
At this point my only two choices is opening up the back panel then replugging the battery so it completely turns off and hopefully boots up. But its a risky task since I don't have special tools to open up my phone, and my another choice is just bring it on a service center.
Click to expand...
Click to collapse
Do you have any clue as to why this happened? Any mods done besides applying Magisk?
If the software got damaged, you could try the EDL Mode but that's difficult. Should be your last resort.
If hardware, then I don't know unfortunately...but then how?
rururi said:
So I am normally using my phone scrolling through social media but it suddenly froze so I tried to hard reset it, but it goes in to a bootloop without any display on the screen. I could tell it is on a bootloop because of the repeating vibration everytime the phone boots up.
My device is Poco F3 (alioth) Running stock MIUI 12.5 bootloader unlocked and rooted with Magisk.
Things I have tried:
Long pressing power button, long pressing both power button and volume down button, long pressing power and volume up button, then long pressing all of them.
Plugging it on my PC but it doesn't even detect it. Tried inputting
Code:
adb devices
and
Code:
fastboot devices
Still doesn't work. I even made sure that my drivers are working so I tried it on my brothers Poco F3 and the PC can detect his phone through ADB commands.
Waiting for a day if it magically turns on again. Nope.
Charging it up because maybe the battery is low. Nope.
At this point my only two choices is opening up the back panel then replugging the battery so it completely turns off and hopefully boots up. But its a risky task since I don't have special tools to open up my phone, and my another choice is just bring it on a service center.
Click to expand...
Click to collapse
If it's recognised by your brothers pc, try that pc for flashing stock fastboot rom using miflash, and don't forget to choose 'flash and wipe' instead of 'flash and lock' in bottom right corner of miflash. Let us know how you get on
Happened today. Random bootloop while under normal use. Also occasionally attempted to trigger the emergency SOS call when power BTN clicks 5 times.
Saved by a solution in poco x3 thread.
The failure mode I experienced was possibly a "sticky" power button.unsure if it's an electrical short or something mechanical in nature tho since it's intermittent triggering of the power button.
Temp fix was some quick clicks of the power button a bunch of times(20-30 clicks?).
Also shut off the emergency sos function.
jowaii89 said:
Happened today. Random bootloop while under normal use. Also occasionally attempted to trigger the emergency SOS call when power BTN clicks 5 times.
Saved by a solution in poco x3 thread.
The failure mode I experienced was possibly a "sticky" power button.unsure if it's an electrical short or something mechanical in nature tho since it's intermittent triggering of the power button.
Temp fix was some quick clicks of the power button a bunch of times(20-30 clicks?).
Also shut off the emergency sos function.
Click to expand...
Click to collapse
Same... it started calling emergency number and wouldn't shut off by holding power button.
Worst device ever
{Mod edit: Inappropriate language edited. Oswald Boelcke}