Related
any ideas how to get out of it? did i brick my phone? D: (my first android phone) HELP PLEASE!
Have you tried pulling the battery, and start over?
yeah i did.
i also tried doing a wipe/factory reset ...which didnt work.
everytime i try to reboot the phone it takes me to the bootloading screeen. ;/
What were you trying to do? Unlock the bootloader?
uhm i was trying to root my phone, and was in the process of unlocking the bootloader.. so i did unlock it but now when i try to restart my phone or do anything it just takes me back to the bootloader screen. D:
I saw this happened to someone else on the development section.
He solved this by flashing a wiped nandroid backup...
can't seem to find the thread but look for it, it should be there.
My Nexus S is (was) doing the same thing this morning as well.
I had not done anything to it, hadn't even unlocked the boot loader. I plugged it in to charge overnight and when I woke up it was bootlooping on the animation. Battery pull - nothing. Pulled SIM - nothing.
The only way I was able to fix it was to go into recovery and go ahead and unlock the bootloader which forced a wipe. (How does one hard reset this thing anyhow?)
I'm a little concerned that this might happen again....
hrm, i tried locking and then relocking and doing a wipe but that doesnt work ;/ still takes me through the bootlooop. any other suggestions? D: thanks for tryinggg.
ilsynnhoj said:
hrm, i tried locking and then relocking and doing a wipe but that doesnt work ;/ still takes me through the bootlooop. any other suggestions? D: thanks for tryinggg.
Click to expand...
Click to collapse
Sorry....mine was a little different problem. I hadn't even tried to root my phone and it decided to boot loop.
also, another question.
how do we flash something if i can't mount my phone on my computer to put the files into the main directory? D: ...
ilsynnhoj said:
also, another question.
how do we flash something if i can't mount my phone on my computer to put the files into the main directory? D: ...
Click to expand...
Click to collapse
your problem is that it doesn't have a boot.img installed so it can't boot.
download koush's rootboot.img and..
Code:
./fastboot flash boot rootboot.img
it will boot after that.
My phone also has the same problem
My phone has the same problem, can someone copy all the phones files for me please.
please help me
how do can i flash the phone if i can't mount my phone on my computer to put the files into the main directory? i need help please!!!! Someone with instructions?
Everything you need should be in these two threads:
http://forum.xda-developers.com/showthread.php?t=878786
http://forum.xda-developers.com/showthread.php?t=895545
The second one has pictures and is very easy to follow.
================================
Solution: http://forum.xda-developers.com/one...bootloader-locked-t3212187/page2#post63494201
================================
Hello,
This afternoon, I was preparing to flash Oxygen OS 2.1 through twrp but I wanted to make a backup first. Attempting to load up twrp by holding Vol- and Power, my OPT flashed the starting frame of the boot animation for half a second before turning off. This repeated every 5 seconds. I could still boot OOS normally at this stage.
I decided to reflash twrp so as to make the backups, but on attempting to flash it, I saw that my bootloader was locked. So into fastboot mode I went, but trying to unlock it, it did the same as trying to get into recovery. As soon as I sent the command, "fastboot oem unlock", the screen went dark, flashed the starting frame for the boot animation, and promptly when dark again.
I now can't boot up normally, nor can I enter recovery. I can access fastboot mode, but I can't seem to make any changes.
I've attempted to use this solution as well as several other similar ones with no success.
I've had my OPT since 17th of August with absolutely no signs of trouble until this afternoon.
To me, it seems like it could be a hardware issue, but I'd hope it would last more than 40 days.
Any suggestions?
Thanks.
----
x-post: whirlpool, reddit
The same just happened to me, wtf
Makrilli said:
The same just happened to me, wtf
Click to expand...
Click to collapse
What were you doing before it occurred? Perhaps we can work out the cause.
GusGold said:
What were you doing before it occurred? Perhaps we can work out the cause.
Click to expand...
Click to collapse
I'm not sure what I was doing, I was going to flash different ak kernel as my wifi didn't work.
HOWEVER
I read someone suggesting if you still have bootloop after trying the qualcomm recovery tool, try booting to fastboot and use: fastboot continue
my opt booted nicely to hydrogen os and after I shut it down it no longer bootlooped and I was able to get to recovery.
I'll post this to your reddit thread too, maybe it might help somebody one day, hopefully this works for you too
Makrilli said:
use: fastboot continue
Click to expand...
Click to collapse
Mate! that worked for me too!
However... It only seems to skip the bootloop for that power on. After power off, it returns to the boot loop. I also still can't unlock the bootloader and can't access recovery.
But at least it can boot into OS with fastboot continue!
Thank you.
Weird, after the first successful boot I rebooted and a chinese menu prompted me if I wanted to unlock the bootloader, and I did.
Maybe you should try different recovery packages.
But I'm glad to hear you at least got past the boot loop
Makrilli said:
Maybe you should try different recovery packages.
Click to expand...
Click to collapse
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
GusGold said:
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
Click to expand...
Click to collapse
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Makrilli said:
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Click to expand...
Click to collapse
Ahh, do you mind linking me to the one you used?
I think I used this: https://mega.nz/#!EsNQHKab!ifATzg4rxxBniPad0iyxANqlN8cZpUx2MVWaZgEhrD4
but it might have also been this: https://drive.google.com/file/d/0B14IjYN3PtxcSlJ5aGQxX3JERHM/view?usp=sharing
It's also worth mentioning I flashed both a few times before I tried the fastboot continue command so try both a few times and see if that helps, also I replaced the stock recovery with twrp in both recovery packages before flashing.
Edit: And best of luck, I'm rather confident your OPT is going to work properly again.
Boot Loop
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
p3wb said:
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
Click to expand...
Click to collapse
And I'm guessing you have tried the qualcomm recovery tool?
And I'm guessing you have tried the qualcomm recovery tool?[/QUOTE]
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
p3wb said:
And I'm guessing you have tried the qualcomm recovery tool?
Click to expand...
Click to collapse
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.[/QUOTE]
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT
Makrilli said:
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
Click to expand...
Click to collapse
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT[/QUOTE]
I finally got my OPT working again, tried Qualcomm recovery tool, wasn't able to complete the "MSM8994DownloadTool"
So i downloaded "A2001_14_A.03_150805" in a guide from technobuzz.net/unbrick-oneplus-2/
A similar but it does a entire wipe of the phone, nothing left at all. WARNING!
But i was okey with it.
Well the phone was in Chinese when it was all done but to change language was no problem.
I finally managed to solve it on mine. I had been cautious over the past weeks to not let it run out of battery or get turned off while away from my computer as
Code:
fastboot continue
was the only way I could get past the boot loop.
My core issue to solve was that I couldn't get it recognised as the USB Diagnostic 9006 under Ports in Device Manager. I installed the driver from here manually by right clicking the /qcser/x64/qcser.inf file and selecting install from the context menu. Then, I powered off my OP2. While only holding Vol+ (not power or Vol-), I plugged in my OP2 to the computer and it was finally recognised as the 9006. Then using the recovery tool from the prior link, it installed and rebooted my OP2. The moment of truth was when it rebooted and didn't enter a boot loop!
Then with the Chinese recovery prompt, I selected the top/first option and it brought me to the welcome/first setup screen of OOS.
It wiped the internal memory, and installed OSS 2.0.2 (don't know if coincidence or not as that was my prior OS as well). Now to install twrp and update to the latest OOS hopefully without a hitch.
Happy to finally know it wasn't a hardware issue like a failed eeprom or a dud nand controller as my prior phone (Samsung Note 10.1) died to a failed nand controller as well.
Will update with news of twrp and OOS, but I feel that should go smoothly now. Thanks to the others that helped in this thread too!
Yeap, all good!
Flashed official twrp through fastboot and batch installed OOS2 through 2.1.1 patches and SuperSU. Everything working like new!
Phew.
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
gamdiiii said:
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
Click to expand...
Click to collapse
Is it recognised as a USB Diagnostic 9006 in your device manager?
Hi GusGold No its 9008
Hi
Yesterday I got my axon 7 and it worked perfect.
Now I was wanted to change the language
So I downloaded as file that in my language
And I tried to install him .
And it worked by the adb software when the axon connected to the computer
So I went to the application in my phone and changed it to my language after USB debugging and developer option is worked
Then the phone was changed to my language and crashed
Now the axon just show the start logo and stuck in restart loop. so I tried to do few thing through your forum , but nothing helped ..
I also cleared the cache through recovery mode but it also didn't help
Its like the axon can't upload the operating system
Thanks a lot for who will help me here.
Also if it possible to send money through PayPal
And if it's legal I will send 30$ to the first that will help me solve this problem
Can you share the link to the file you downloaded ?
Is it compatible with the version of your phone ?
If you can enter in recovery it's enough to save it.
billy_boolean said:
Can you share the link to the file you downloaded ?
Is it compatible with the version of your phone ?
If you can enter in recovery it's enough to save it.
Click to expand...
Click to collapse
Yea the reason it happened is because I installed wrong adb language on my axon through USB debugging and external app
Now it possible to get into recovery
I just don't know what to do next
I tried few things but I always keep getting errors
You can try to install TWRP.
You will have a lot of option.
There is no option to restor the phone in the official recovery ?
billy_boolean said:
You can try to install TWRP.
You will have a lot of option.
There is no option to restor the phone in the official recovery ?
Click to expand...
Click to collapse
I tried to use twrp but the computer doesn't recognize My axon
You need to install driver first...
billy_boolean said:
You need to install driver first...
Click to expand...
Click to collapse
I tried but after the install the drivers and cheak them in the device manager in my computer
The name of the driver was London marshesll something
And not what I saw in the guide - adb something
And it didn't recognize my device
I wrote also adb reboot bootloader
And it gives me error massage
I would be more then happy to give someone 30$ now..
Just that my axon will work
Did you root your phone, or just use ADB to sideload a file? If it's wasn't rooted/unlocked, then a factory reset should take care of it, as nothing done via ADB in that setup would impact the system partitions.
If you used the unofficial bootloader unlocking, then you'll have to follow other people's restore guides.
As @TeutonJon78 mention, a factory reset will do the job youan boot to stock recovery using adb
Code:
adb reboot recovery
Or doing it manually,
- Completely Power off your device
- Press and HOLD Volume UP and Power button.
- once you boot to recovery just use your volume buttons to navigate FACTORY RESET.
- Reboot System
holding up and down at the same time. get to fastboot mode it says secure boot: enabled and device state: locked. then i entered to recovery mode, and press on "wipe data/factory reset" (said it was successfully finished). then i pressed on "reboot system now". still its stuck on the zte logo
liron lev said:
holding up and down at the same time. get to fastboot mode it says secure boot: enabled and device state: locked. then i entered to recovery mode, and press on "wipe data/factory reset" (said it was successfully finished). then i pressed on "reboot system now". still its stuck on the zte logo
Click to expand...
Click to collapse
I will be honest man. I bricked mine too. Everybody has a step by step guide that they say works. I followed them step by step. They did not work. I have an RMA open on my phone and fedex is taking it to ZTE. Use the warranty. Until Zte puts online the full factory images for us to use there is no real way to fix these things.
liron lev said:
holding up and down at the same time. get to fastboot mode it says secure boot: enabled and device state: locked. then i entered to recovery mode, and press on "wipe data/factory reset" (said it was successfully finished). then i pressed on "reboot system now". still its stuck on the zte logo
Click to expand...
Click to collapse
Are you from Israel?
---------- Post added at 11:40 PM ---------- Previous post was at 11:38 PM ----------
I know how to help you if you can tell me which bootloader version you have? Did you unlocked it? did you use Tenfar's method to root it?
tabletalker7 said:
I will be honest man. I bricked mine too. Everybody has a step by step guide that they say works. I followed them step by step. They did not work. I have an RMA open on my phone and fedex is taking it to ZTE. Use the warranty. Until Zte puts online the full factory images for us to use there is no real way to fix these things.
Click to expand...
Click to collapse
Were you playing around with the rooting/unofficial bootloader? It should be very hard to actually brick the device without doing those things, and nothing a factory reset shouldn't fix.
If one's playing around with unofficial modifications, then they should take all precautions to make sure to know how to recover the device before hand. There's still a lot of moving pieces between potentially faulty TWRP bugs and no image file.
liron lev said:
holding up and down at the same time. get to fastboot mode it says secure boot: enabled and device state: locked. then i entered to recovery mode, and press on "wipe data/factory reset" (said it was successfully finished). then i pressed on "reboot system now". still its stuck on the zte logo
Click to expand...
Click to collapse
Did you let it sit for awhile? First runs after a factory reset can take up to even 10 minutes to boot fully. If it still doesn't work again, check if the recovery menu has another option like wipe cache/davlik, which maybe also needs to run if they have a bug in the recovery code about resetting data. If you hadn't touch anything using the tools on this forum, and none of the factory reset/wipe data/wipe cache stuff helps, then you probably have a faulty phone. Just sideloading an app shouldn't be able to corrupt a locked system partition.
The OP of this thread hasn't yet clarified if he was just sideloading files on a normal system (which should be totally fixable unless his phone has an actual flash problem) or if he had been tinkering with other things first.
TeutonJon78 said:
Were you playing around with the rooting/unofficial bootloader? It should be very hard to actually brick the device without doing those things, and nothing a factory reset shouldn't fix.
If one's playing around with unofficial modifications, then they should take all precautions to make sure to know how to recover the device before hand. There's still a lot of moving pieces between potentially faulty TWRP bugs and no image file.
Did you let it sit for awhile? First runs after a factory reset can take up to even 10 minutes to boot fully. If it still doesn't work again, check if the recovery menu has another option like wipe cache/davlik, which maybe also needs to run if they have a bug in the recovery code about resetting data. If you hadn't touch anything using the tools on this forum, and none of the factory reset/wipe data/wipe cache stuff helps, then you probably have a faulty phone. Just sideloading an app shouldn't be able to corrupt a locked system partition.
The OP of this thread hasn't yet clarified if he was just sideloading files on a normal system (which should be totally fixable unless his phone has an actual flash problem) or if he had been tinkering with other things first.
Click to expand...
Click to collapse
The factory reset made my phone lose it's IMEI. Everyone said follow this certain guide. After following that guide and getting more help after that I had an AXON 7 that wouldn't turn on at all. Without full factory images from ZTE I won't touch the software. ZTE can fix it.
tabletalker7 said:
The factory reset made my phone lose it's IMEI. Everyone said follow this certain guide. After following that guide and getting more help after that I had an AXON 7 that wouldn't turn on at all. Without full factory images from ZTE I won't touch the software. ZTE can fix it.
Click to expand...
Click to collapse
Which guide did you follow? A Factory reset form within the stock software or stock recovery shouldn't cause that problem at all, as it should only be wiping data, cache, Davlik, and potentially the "media" portion of the internal storage.
TeutonJon78 said:
Which guide did you follow? A Factory reset form within the stock software or stock recovery shouldn't cause that problem at all, as it should only be wiping data, cache, Davlik, and potentially the "media" portion of the internal storage.
Click to expand...
Click to collapse
The factory reset that made it lose the IMEI - it was completely stock then!
liron lev said:
Hi
Yesterday I got my axon 7 and it worked perfect.
Now I was wanted to change the language
So I downloaded as file that in my language
And I tried to install him .
And it worked by the adb software when the axon connected to the computer
So I went to the application in my phone and changed it to my language after USB debugging and developer option is worked
Then the phone was changed to my language and crashed
Now the axon just show the start logo and stuck in restart loop. so I tried to do few thing through your forum , but nothing helped ..
I also cleared the cache through recovery mode but it also didn't help
Its like the axon can't upload the operating system
Thanks a lot for who will help me here.
Also if it possible to send money through PayPal
And if it's legal I will send 30$ to the first that will help me solve this problem
Click to expand...
Click to collapse
I could help you, please pm.
i tried to use the appliction "morelocale2" to chnge my phone language.
i did turn on the usb debugging option through Developer Options.
it all went good until i tried to choose my language from the app (morelocale2) it change to my language got stucked and start looping over and over. (start up and shut dowm).
after that i cleand evrything such as: wipe data/factory and cache data, and then i restart the phone. it is stoped looping but got stucked on logo zte. and after i cleaned the data i waited few houres.
i also think i used an old version of "morelocale2".
and yes im from israel...
liron lev said:
i tried to use the appliction "morelocale2" to chnge my phone language.
i did turn on the usb debugging option through Developer Options.
it all went good until i tried to choose my language from the app (morelocale2) it change to my language got stucked and start looping over and over. (start up and shut dowm).
after that i cleand evrything such as: wipe data/factory and cache data, and then i restart the phone. it is stoped looping but got stucked on logo zte. and after i cleaned the data i waited few houres.
i also think i used an old version of "morelocale2".
and yes im from israel...
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.wanam
download this app
install it
search hebrew in hebrew
choose hebrew (iw)
accept the root prompt
reboot your phone
everything will be fine
If you have bootloop issues these are not related to the app!
if you need help with this contact me!
you have my info in pm.
hi guys,
so the nexus 6p i had got the oreo ota update and after a couple of day it restarted and since then stuck on google logo(bootloop).
it only goes to fastboot mode,
download mode is disabled,
recovery is not there of any kind, meaning i cant boot to recovery mode.
every things gone on it can i do something to get it back, oem unlocking was not turned on in it. developer option was never turned on. bootloader is also locked.
i am in a big trouble guys please help me if there is a way.
alijaved154 said:
hi guys,
so the nexus 6p i had got the oreo ota update and after a couple of day it restarted and since then stuck on google logo(bootloop).
it only goes to fastboot mode,
download mode is disabled,
recovery is not there of any kind, meaning i cant boot to recovery mode.
every things gone on it can i do something to get it back, oem unlocking was not turned on in it. developer option was never turned on. bootloader is also locked.
i am in a big trouble guys please help me if there is a way.
Click to expand...
Click to collapse
Tried factory reset and reboot?
tropical cactus said:
Tried factory reset and reboot?
Click to expand...
Click to collapse
as i mentioned there is no recovery mode on it. its red and i cant boot to it. it returns back to fast boot mode dude
alijaved154 said:
as i mentioned there is no recovery mode on it. its red and i cant boot to it. it returns back to fast boot mode dude
Click to expand...
Click to collapse
You can select factory reset by pressing the volume button . Factory reset will come up. Select by pressing power button and press again to wipe.
tropical cactus said:
You can select factory reset by pressing the volume button . Factory reset will come up. Select and wipe.
Click to expand...
Click to collapse
in fastboot only the options are:
start
barcodes
recovery
bootloader
alijaved154 said:
in fastboot only the options are:
start
barcodes
recovery
bootloader
Click to expand...
Click to collapse
I have factory reset as an option. Not sure why you don't.
tropical cactus said:
I have factory reset as an option. Not sure why you don't.
Click to expand...
Click to collapse
in fastboot? i dont have it i dont know what hapoened to it
alijaved154 said:
in fastboot? i dont have it i dont know what hapoened to it
Click to expand...
Click to collapse
Try reboot bootloader and scroll through options again.
tropical cactus said:
Try reboot bootloader and scroll through options again.
Click to expand...
Click to collapse
comes back to the same screen but will still try today
alijaved154 said:
comes back to the same screen but will still try today
Click to expand...
Click to collapse
Very strange, unless it only shows up if you enable developer options before.
Same problem after update
Exactly same problem after update, no way to factory reset phone, developer option was unlocked
Erroras said:
Exactly same problem after update, no way to factory reset phone, developer option was unlocked
Click to expand...
Click to collapse
you are not alone...?
Same issue on one I have my hands on. This could get interesting.
From fastboot can anything be pushed/flashed like a previous actually functional firmware? Is there other specific software to do so? Only got my hands on the defective non functional device today but I'm planning and scheming a fix if possible.
One thing is really interesting. Why only after this update???? Why not after update from 6 to 7 then 7 to 7.1 and after 7.1 to 8.0. I think Google or Huawei is cheating us and forcing us to buy Google pixel.
I also have this issue (I'm using a nexus 5x, but this thread is the closest to my issue I've found), but it came incrementally. First, I started getting reboots every 20m or so, while doing normal phone things (reading, mostly). Then it started getting into bootloops that were 2-3 boots long, and would then work normally for the 20m mentioned above. I tried a factory reset, but it just got worse, and now either reboots on the Google logo or during the Android animation. My fastboot menu only has the regular "Start" as green. The only other options are Restart Bootloader, in red, and Recovery mode, also in red. Power off is there, obviously, but that's it. It started happening yesterday, and worsened to its current point within only a few hours.
Well. I have just joined the club. What is going on with that?
Happened to me today and I was using the latest build of SuperXE 6P.
Guys! lol
1. Dev options in ROM is same old. Settings/about and tap build 10 times to see count down to developer. Back to settings. In there for OEM unlock
2. Factory reset can be done any number of ways.
a. In ROM. Settings/backup and reset/factory reset.
b. From anywhere, hold power+volume down until you see the bootloader. There are 2 possible screens in there. One of them has factory reset. Beware! From here it will likely wipe your sdcard!
c. From recovery. You can get there from bootloader. You can also flash an up to date recovery image from bootloader.
The rest of your recovery process should be provided by the ROM thread by which you will get your choice of ROM.
Make sure you have access to a PC with adb. You will likely need to flash a vendor image
My device is only recognized in fastboot mode. No ADB, no recovery. Tried to uninstall and manually install latest USB drivers, it didn't work. My Nexus is now just stucked in a bootloop. I even tried to flash factory images to no avail. Really don't know what to do...
FYI I have no screen in bootloader allowing me to factory reset: only Start/Reboot/Reboot bootloader/Barcodes, as others stated above.
I do not have a great track record when flashing ROMS etc on LG devices..
Today I decided to flash my device back to total stock in prep for the incoming Oreo update and also the dreadful battery life i've been experiencing.
I tried using LGUP first but found that once the device completed it's boot, it got to the 'Android is starting' screen before rebooting.. It did this a few times before I turned it off and booted it into download mode.
I then used LG bridge and flashed everything directly through the Bridge software - This was successful however when it boots it is now doing the same thing.
It will show the boot animation, flash very quick the 'Android is updating/booting/upgrading' white screen before rebooting, showing 'erasing' very quickly then showing the boot animation again.
What am I missing here? Why is this happening?
For some reason flashing stock bricks the phone just factory reset it though the recovery. Tell me did you succeed...
ZinX09 said:
For some reason flashing stock bricks the phone just factory reset it though the recovery. Tell me did you succeed...
Click to expand...
Click to collapse
So yes, I managed to resolve this somehow.
As I managed to get into fastboot mode, reflashed TWRP and formatted the data partition - reflashing via bridge tool causes the same issue again and I only managed to get eh device to boot after I accidentally booting into safemode and allowing the device to finish optimising. Rebooting into normal mode then worked just fine.
adaimespechip said:
So yes, I managed to resolve this somehow.
As I managed to get into fastboot mode, reflashed TWRP and formatted the data partition - reflashing via bridge tool causes the same issue again and I only managed to get eh device to boot after I accidentally booting into safemode and allowing the device to finish optimising. Rebooting into normal mode then worked just fine.
Click to expand...
Click to collapse
I meant for you to reset through the stock recovery but i guess that works as well.
ZinX09 said:
I meant for you to reset through the stock recovery but i guess that works as well.
Click to expand...
Click to collapse
Oh I see, sorry.. I couldn't get into stock recovery - it would simply erase the device and reboot each time. That was part of the problem..
adaimespechip said:
Oh I see, sorry.. I couldn't get into stock recovery - it would simply erase the device and reboot each time. That was part of the problem..
Click to expand...
Click to collapse
Hello i have the same problem how to fix it showing erarsing for sek and that's it.
Mercz23 said:
Hello i have the same problem how to fix it showing erarsing for sek and that's it.
Click to expand...
Click to collapse
Have you tried to boot to the stock recovery and factory reset it the phone.
same problem here, how did you boot safe mode??