My Moto E Surnia (From US' Boost Mobile) has been running fine with TWRP and Lineage OS 7.1.x until last week, which it is stuck on Moto boot screen (before the Lineage OS logo kicks in), or stuck on "teamwin" screen when attempting to boot into recovery.
I was able to push Recover 3.2.3-0 from PC but still stuck on the teamwin screen when trying to boot into recovery.
I had Magisk and Swapper for Android installed previously, they both worked fine, but not sure if the Swapper messed up something causing the problem..
Any suggestion?
griffoun said:
My Moto E Surnia (From US' Boost Mobile) has been running fine with TWRP and Lineage OS 7.1.x until last week, which it is stuck on Moto boot screen (before the Lineage OS logo kicks in), or stuck on "teamwin" screen when attempting to boot into recovery.
I was able to push Recover 3.2.3-0 from PC but still stuck on the teamwin screen when trying to boot into recovery.
I had Magisk and Swapper for Android installed previously, they both worked fine, but not sure if the Swapper messed up something causing the problem..
Any suggestion?
Click to expand...
Click to collapse
Try a clean flash it will fix your device.
riyan65 said:
Try a clean flash it will fix your device.
Click to expand...
Click to collapse
I wanted to go down this road, but how do I clean flash it when the phone is stuck on the recovery bootup screen?
griffoun said:
I wanted to go down this road, but how do I clean flash it when the phone is stuck on the recovery bootup screen?
Click to expand...
Click to collapse
Flash the stock rom. Then go for custom roms
riyan65 said:
Flash the stock rom. Then go for custom roms
Click to expand...
Click to collapse
It failed at 2nd step...
Code:
C:\platform-tools\Moto_XT1526>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.363s
griffoun said:
It failed at 2nd step...
Click to expand...
Click to collapse
You are trying a older firmware than the device had, try to download a newer firmware or remove the bootloader and gpt codes while flashing. If you flash a old firmware it will brick your device.
riyan65 said:
You are trying a older firmware than the device had, try to download a newer firmware or remove the bootloader and gpt codes while flashing. If you flash a old firmware it will brick your device.
Click to expand...
Click to collapse
I read from other threads to skip the failed step and continue flashing the rest... now it's in bootloop, and going into recovery results in the "no command" screen.
Would you mind pointing out the thread for which you're referring to about gpt codes? Thanks for taking time to respond to this thread, really appreciated.
griffoun said:
I read from other threads to skip the failed step and continue flashing the rest... now it's in bootloop, and going into recovery results in the "no command" screen.
Would you mind pointing out the thread for which you're referring to about gpt codes? Thanks for taking time to respond to this thread, really appreciated.
Click to expand...
Click to collapse
You can prefer Moto g5 and g5+ thread, from there I have read all this. And first reboot always gets in bootloop so try holding power button for 10sec it will come out from bootloop.
riyan65 said:
You can prefer Moto g5 and g5+ thread, from there I have read all this. And first reboot always gets in bootloop so try holding power button for 10sec it will come out from bootloop.
Click to expand...
Click to collapse
While I appreciate your suggestion, would you mind provide a link to the exact thread(s) you're referring to?
I've been trying for a few days and still the same issue, and adb devices returns no device, even though I have installed the moto USB driver. I can only get to the boot menu that selects power off, going to recovery mode and so on, but still, selecting recovery would results in no command screen, and starting the device still results in bootloop, and holding the power button like you suggested did not resolve the problem.
griffoun said:
While I appreciate your suggestion, would you mind provide a link to the exact thread(s) you're referring to?
I've been trying for a few days and still the same issue, and adb devices returns no device, even though I have installed the moto USB driver. I can only get to the boot menu that selects power off, going to recovery mode and so on, but still, selecting recovery would results in no command screen, and starting the device still results in bootloop, and holding the power button like you suggested did not resolve the problem.
Click to expand...
Click to collapse
Here you can read that.
https://forum.xda-developers.com/g5...-run-morning-post-image-t3776012/post79232466
riyan65 said:
Here you can read that.
https://forum.xda-developers.com/g5...-run-morning-post-image-t3776012/post79232466
Click to expand...
Click to collapse
I got TWRP loaded finally; On the other hand, I discovered LineageOS for Moto E2 support is gone from the site... only managed to find the last CyanogenMod build in Dec 2016.
Anyway, now I just need to solve the last bit of inconvenience - the device enters fastboot mode everytime it starts/restarts, and I have to select "Start" so that it will continue booting to the OS. And when I power it off, whether it's from Fastboot menu or TWRP menu, it starts itself up again and pauses on Fastboot screen. Wonder what that is?
griffoun said:
I got TWRP loaded finally; On the other hand, I discovered LineageOS for Moto E2 support is gone from the site... only managed to find the last CyanogenMod build in Dec 2016.
Anyway, now I just need to solve the last bit of inconvenience - the device enters fastboot mode everytime it starts/restarts, and I have to select "Start" so that it will continue booting to the OS. Wonder why that is?
Click to expand...
Click to collapse
There is a solution for that in the forum I suggested, there is a command which is going to fix, as far as I remember it was 'fastboot continue'.
Related
Hi,
i woke up this morning and the CM updater offered me to update for CM 14.1, i thougt welll, why not. mistake :crying:
Now the phone is stuck on the flashing CM logo,
if i try to go to fastboot, than i see the fastboot screen and than black screen and the phone goes back to the flashing CM logo.
Any thoughts?
guytsur7 said:
Hi,
i woke up this morning and the CM updater offered me to update for CM 14.1, i thougt welll, why not. mistake :crying:
Now the phone is stuck on the flashing CM logo,
if i try to go to fastboot, than i see the fastboot screen and than black screen and the phone goes back to the flashing CM logo.
Any thoughts?
Click to expand...
Click to collapse
do u have access to recovery?? if u have, then u can just flash previous build without wiping data..
Think if you press vol+ vol- and power and then use the button combo to boot into TWRP you will be fine, takes abit of messing to get it right.
http://en.miui.com/thread-277276-1-1.html
TRY THIS
saikatmitra71 said:
do u have access to recovery?? if u have, then u can just flash previous build without wiping data..
Click to expand...
Click to collapse
Did you try this solution? Did it work? Did you lose your apps/data?
Solved
Eventually managed to get onto twrp using adb (it was a bit of a statistical process... Didn't always work)
From there I just flashed cm 14.1 again, and it looks OK now
Thanks you all for the help!
Like I said earlier failed flash by CMxx doesn't overwrite TWRP, you can boot back into recovery just have to try a few times. Happened to me pressing both volume buttons and power switched phone off then I used button combo and it booted into TWRP.
Might have to grab a usb cable and use ADB to boot into fastboot. It happened to me and that was the only way for me.
seos83 said:
Might have to grab a usb cable and use ADB to boot into fastboot. It happened to me and that was the only way for me.
Click to expand...
Click to collapse
Don't worry Follow This one No fastboot, no edl, no test point, best way to Recover Xiaomi Device, prepare by me and 100% working {tested}
Hi all,
I'm happy to share with you my new TWRP recovery 3.1.1-0 built from sources. It works for Single Sim XA only on Nougat.
As before decryption of /data doesn't work so if you want a full backup or explore files use an unencrypted data partition.
Download link:
https://mega.nz/#!Btg10D6L!-WX6Aa0Z6qpVSUcAiaF2W8fYl2UlM9fGDB0EVpkA4Tc
Flash it with fastboot.
Have a nice day
Can't flash boot and recovery
best thankx you
I does's have the recovery partition on Nougat.
so I always get the error:
C:\Flashtool\x10flasher_lib>fastboot flash recovery recoveryXASS-3.1.1-0.img
target reported max download size of 134217728 bytes
sending 'recovery' (17508 KB)...
OKAY [ 0.750s]
writing 'recovery'...
FAILED (remote: This partition doesn't exist)
finished. total time: 0.754s
Click to expand...
Click to collapse
I can use this to enter TWRP:
fastboot flash boot recoveryXASS-3.1.1-0.img
Click to expand...
Click to collapse
but when do this, I can't go back to Android.
How to make my recovery partition available?
Same problem
sending 'recovery' (17508 KB)...
OKAY [ 0.750s]
writing 'recovery'...
FAILED (remote: This partition doesn't exist)
finished. total time: 0.754s
Boot image goes in okay
but fastboot flash recovery recovery.img brings up the above:crying:
MAX download 134217728
I've now tried recovery 3.1 and recovery 3.1.1 and both times they have failed.
In the script it shows that the target reported MAX DOWNLOAD size of 134217728 bytes
Both recoveries are sent, 3.1 is 15814 KB and 3.1.1 is 17508 KB both fail
I had a recovery on my PC that's 12768 KB but don't know the recovery number this fails also as it's also looking for 134217728 KB.
Is there a recovery that's 134217728 bytes?
MisterPetje said:
I've now tried recovery 3.1 and recovery 3.1.1 and both times they have failed.
In the script it shows that the target reported MAX DOWNLOAD size of 134217728 bytes
Both recoveries are sent, 3.1 is 15814 KB and 3.1.1 is 17508 KB both fail
I had a recovery on my PC that's 12768 KB but don't know the recovery number this fails also as it's also looking for 134217728 KB.
Is there a recovery that's 134217728 bytes?
Click to expand...
Click to collapse
If it fails it's because you didn't followed the root guide, nothing to do with the size.
Thanks now sorted
Sorry I was following the Marshmallow root not the Nougat
same problem
MisterPetje said:
Sorry I was following the Marshmallow root not the Nougat
Click to expand...
Click to collapse
hey man, I have the same issue as you did but I don't know how to fix it.
Pl:ease help!!
Hi! sometimes when I boot to recovery I get a black screen and none of the buttons works even the force reboot. After a couple of minutes I'm able to boot the phone but I need to flash the recovery again to make it work. Why?
For dual?
So every time I boot into recovery using an app my phone gets a black screen and I can't turn it in useless the battery gets to 0%. When I open twrp from buttons every works well but when I use an app like xposed or terminal to reboot to recovery the phone just gets stuck. Why?
vraciu' said:
So every time I boot into recovery using an app my phone gets a black screen and I can't turn it in useless the battery gets to 0%. When I open twrp from buttons every works well but when I use an app like xposed or terminal to reboot to recovery the phone just gets stuck. Why?
Click to expand...
Click to collapse
So since yesterday at 8PM till now my phone didn't boot up. I tried every button trick and nothing. The phone is just death and I only get a red led when I charge it.
The problem only comes when I reboot to TWRP using:
Terminal emulator:
>su
>reboot recovery
Or when I reboot using an app that has reboot to recovery menu.
Help!! @rrvuhpg
vraciu' said:
So since yesterday at 8PM till now my phone didn't boot up. I tried every button trick and nothing. The phone is just death and I only get a red led when I charge it.
The problem only comes when I reboot to TWRP using:
Terminal emulator:
>su
>reboot recovery
Or when I reboot using an app that has reboot to recovery menu.
Help!! @rrvuhpg
Click to expand...
Click to collapse
I had the same problem as yours, I tried to reboot to recovery from an app and I got black screen I could not boot up, even turn to flash mode and fastboot mode, red light when I charged it. What did was I opened my phone, Unplug the battery for 30 seconds and then plug, and reboot. that solved my problem
pa7taloha said:
I had the same problem as yours, I tried to reboot to recovery from an app and I got black screen I could not boot up, even turn to flash mode and fastboot mode, red light when I charged it. What did was I opened my phone, Unplug the battery for 30 seconds and then plug, and reboot. that solved my problem
Click to expand...
Click to collapse
So? I need to open the phone since it doesn't has removable batery.. How? Do i need to pop up the back?
vraciu' said:
So? I need to open the phone since it doesn't has removable batery.. How? Do i need to pop up the back?
Click to expand...
Click to collapse
Yes, you have to pop up the back, you can find on youtube how to do that, unplug the battery connector(pull it from the upper side very slowly) wait for 30 seconds, plug the battery connector and power on the phone.
---------- Post added at 11:41 PM ---------- Previous post was at 11:21 PM ----------
vraciu' said:
So? I need to open the phone since it doesn't has removable batery.. How? Do i need to pop up the back?
Click to expand...
Click to collapse
Use this video to remove the backplate https://www.youtube.com/watch?v=2O5dAljOpR4
pa7taloha said:
Yes, you have to pop up the back, you can find on youtube how to do that, unplug the battery connector(pull it from the upper side very slowly) wait for 30 seconds, plug the battery connector and power on the phone.
---------- Post added at 11:41 PM ---------- Previous post was at 11:21 PM ----------
Use this video to remove the backplate https://www.youtube.com/watch?v=2O5dAljOpR4
Click to expand...
Click to collapse
Don't need the tutorial anymore.
Hell, thia was the scariest thing I ever done with my phone.. But I'm glad I fixed it. Thanks again!
Anyway.. The dev should check what's wrong. I don't want to make that mistake again and open my phone again. Or anyone else to make this mistake
vraciu' said:
Don't need the tutorial anymore.
Hell, thia was the scariest thing I ever done with my phone.. But I'm glad I fixed it. Thanks again!
Anyway.. The dev should check what's wrong. I don't want to make that mistake again and open my phone again. Or anyone else to make this mistake
Click to expand...
Click to collapse
Thank you for your feedback, I will check and try to solve this problem. If you have this problem again, try to hold "vol+" and power buttons for 9-10 seconds, it will force shutdown. Release buttons and power on normally.
vraciu' said:
Don't need the tutorial anymore.
Hell, thia was the scariest thing I ever done with my phone.. But I'm glad I fixed it. Thanks again!
Anyway.. The dev should check what's wrong. I don't want to make that mistake again and open my phone again. Or anyone else to make this mistake
Click to expand...
Click to collapse
Hi, I checked what's wrong but news are not good. As expected I have the same brick problem as you when I try to reboot to recovery from Android and I have to unplug the battery or wait until the battery die.
The problem comes from the preloader, if I flash the boot_delivery.xml from MM firmware I can reboot to recovery without brick. My theory is that the phone can't find the recovery partition (like when you try to flash recovery from fastboot) and bootloop when trying to reboot to TWRP. I hope that Sony will fix the preloader bug in a future update.
rrvuhpg said:
Hi, I checked what's wrong but news are not good. As expected I have the same brick problem as you when I try to reboot to recovery from Android and I have to unplug the battery or wait until the battery die.
The problem comes from the preloader, if I flash the boot_delivery.xml from MM firmware I can reboot to recovery without brick. My theory is that the phone can't find the recovery partition (like when you try to flash recovery from fastboot) and bootloop when trying to reboot to TWRP. I hope that Sony will fix the preloader bug in a future update.
Click to expand...
Click to collapse
You can't use the boot-delivery.xml from MM with TWRP version of nougat? I don't think Sony will fix this if it doesn't affect their recovery or maybe it does affect it. I don't really know. And beside that I see that XA models are getting low attention even from Sony.
Many of us are on custom OS and want to return back to stock Indian OS which was not possible till now. Below posted is a tried and tested method by me as well as my friend @ankan1993.
I assume you are unlocked BL and your device is atleast not bricked.
Please follow this guide step by step to get a stock working device. This is for Honor V10 Indian Version C675 and I'm not responsible for your loss if you make this worst by trying this on other variants/models or if you choose not to follow this guide properly.
I assume you are on Berkley TWRP with the latest version, unmodified one.
Downloads : (Keep both in your fastboot folder in PC)
Stock Recovery : https://drive.google.com/file/d/1WEUHRrba1dV3109e7h7b3Hp_aJhy0vM8/view?usp=sharing (stockrec.img)
Stock System Image : https://drive.google.com/file/d/1IABtk7HJ9ml6kOpytYHrnT6z3C1_9IfW/view
1. Enter TWRP and go to wipe -> Advanced -> Select system and data, and wipe them.
2. In TWRP, go back and Click Reboot button on main screen and reboot to Bootloader.
3. Connect you device and open cmd_here (open as administrator) from fastboot folder. ( I assume fastboot is installed and working in your system. You can check by the command "fastboot devices" . Device should show there. )
4. Type "fastboot flash recovery_ramdisk stockrec.img" (It should complete without error)
5. Once completes, Type "fastboot flash system system.img" (This may show error like "Invalid sparse file format". Ignore that and keep waiting for 10-12 minutes until the system gets flashed completely.)
6. Once it gets completed, disconnect your device and then press Vol up + power, until it screen shows stock recovery.
7. In stock recovery, use factory reset and cache wipe option one by one and then reboot.
Hit thanks if you think it helped :fingers-crossed:
Finally, after days, after being tormented by the bugs of custom Roms we have something to cheer about. Kudos Oreopie! Cheers to the long hours.
Kudo's bro.. appreciate your efforts :good:
Will this method also lock the Bootloader to stock?
vardaraju said:
Will this method also lock the Bootloader to stock?
Click to expand...
Click to collapse
No, It won't.
Im unable to access bootloader/recovery mode after unlocking bootloader with volume down+power button, used twrp option to reboot to bootloader, but now i flashed stock recovery and this system image, device bootlooped and im unable to access bootloader, i hold the keys but instantly that warning screen comes up, please help..started using android since 2010 with HTC desire HD and never in my life i stepped in service center because those devices were brick proof, looks like honor made me step into service center
didnt work for me, followed exact steps as mentioned above but stock recovery keeps giving error while factory resetting the device, device ends up in bootloop,, this device is crazy, i need to connect my device to pc and then press voldown+ power to access bootloader else it just jumps to warning screen
aditya desai said:
didnt work for me, followed exact steps as mentioned above but stock recovery keeps giving error while factory resetting the device, device ends up in bootloop,, this device is crazy, i need to connect my device to pc and then press voldown+ power to access bootloader else it just jumps to warning screen
Click to expand...
Click to collapse
Obviously warning screen will come up, but at the same moment you have to just leave power button and keep on pressing vol down button, until you get into bootloader mode. It takes time bro and let me tell you one thing, no matter which mode you boot, no matter what ROM it is, once the bootloader is unlocked it implies that the unlocked warning screen will show and then it will be allowed to get into whatever mode you wish.
Try it as I told, be patient and follow the same guide exactly if you do not wish to visit service centre. There is nothing wrong happening with you other than an improper method being followed in haste
aditya desai said:
Im unable to access bootloader/recovery mode after unlocking bootloader with volume down+power button, used twrp option to reboot to bootloader, but now i flashed stock recovery and this system image, device bootlooped and im unable to access bootloader, i hold the keys but instantly that warning screen comes up, please help..started using android since 2010 with HTC desire HD and never in my life i stepped in service center because those devices were brick proof, looks like honor made me step into service center
Click to expand...
Click to collapse
In cases of a bootloop, follow this- https://forum.xda-developers.com/ho...ustom-rom-to-stock-rom-honor-view-10-t3802872
will the system image work on honor 7x??
Can you share the screenshot of the about phone screen please
Anyone got it working? the stock recovery keeps showing error when factory resetting the device, error shows some where at 12%, it just shows exclamation mark, ROM doesn't boots up
Not working!
Rj_Param said:
Not working!
Click to expand...
Click to collapse
What is the issue and what you want to do.
shashank1320 said:
What is the issue and what you want to do.
Click to expand...
Click to collapse
I am on lineage and want to go back to the stock ROM. I also have backup of my system but i have tried many times after flashing the system image it is going in boot loop so i have followed all methods and it's not working..
Every time i have tried after flashing system whenever i go to recover to do factory reset it failed. Even i tried to lock the bootloader but nothing seems to be working.
Rj_Param said:
I am on lineage and want to go back to the stock ROM. I also have backup of my system but i have tried many times after flashing the system image it is going in boot loop so i have followed all methods and it's not working..
Every time i have tried after flashing system whenever i go to recover to do factory reset it failed. Even i tried to lock the bootloader but nothing seems to be working.
Click to expand...
Click to collapse
Because on custom you are on 8.1 and twrp doesn't support yet.
May be you can try dload the b161 version which is out on firmware finder now.
shashank1320 said:
Because on custom you are on 8.1 and twrp doesn't support yet.
May be you can try dload the b161 version which is out on firmware finder now.
Click to expand...
Click to collapse
I'll give it a try today...thanks
Invalid
as you mentioned, i m getting this error "invalid sprase file format". I waited more than 30 mins, still i couldn't see any message like compeleted or success. Still showing only that error "invalid spase file format". Help me with this.
Tamilarasan_Indian said:
as you mentioned, i m getting this error "invalid sprase file format". I waited more than 30 mins, still i couldn't see any message like compeleted or success. Still showing only that error "invalid spase file format". Help me with this.
Click to expand...
Click to collapse
Invalid sparse error happens when trying to flash .IMG files in Windows system.
It can be easily solved by using Linux system.
thanks for the reply
miststudent2011 said:
Invalid sparse error happens when trying to flash .IMG files in Windows system.
It can be easily solved by using Linux system.
Click to expand...
Click to collapse
I dont have Linux , and tried to flash other SYSTEM.img file for honor v10 from other threads. It completed flashing but still am not able to login into phone successfully. Still stuck at bootloop. Help me
Hello guys,
so I had installed RROS 8.1 on my Honor 9 STF-L09, but capacitive buttons and flashlight didn't work, so i decided to roll back to B120 via HWOTA in recovery, I think I chose a wrong stock recovery image so there went something wrong and the phone won't boot up..
It was stuck at the Bootloader unlocked - Your device is booting now... screen, I only can access fastboot mode.
I've already tried every unbrickng method I know. First I tried to unbrick it via Multitool and stock firmware and recovery but this didn't help, I did just get another screen where I was stuck(Error mode: func11: recovery , load failed or sth like that). I also tried flashing TWRP but it doesn't work, it says it was successfully installed, just like with multitool, but i am still stuck. Also tried flashing Stock recovery image and then using dload sd card method but it won't even go to Emui restoring screen.. I actually just tried to flash all the important image files from update.APP (which I know how to flash via fastboot), but it didn't do anything. After trying again via Multitool I am again stuck at the 'unlocked screen'.
If somebody could help i would be so thankful, I don't know what to do now.. THANK YOU
Sorry for my bad english I am a student from germany
Lord Juggelmann said:
Hello guys,
so I had installed RROS 8.1 on my Honor 9 STF-L09,
Click to expand...
Click to collapse
Which region ? C432 ?
Which version B36x ?
Lord Juggelmann said:
but capacitive buttons and flashlight didn't work, so i decided to roll back to B120 via HWOTA in recovery,
Click to expand...
Click to collapse
With which HWOTA ? 'HWOTA 8 to 7 rollback' ?
Lord Juggelmann said:
I think I chose a wrong stock recovery image
Click to expand...
Click to collapse
Which one ?
oslo83 said:
Which region ? C432 ?
Which version B36x ?
With which HWOTA ? 'HWOTA 8 to 7 rollback' ?
Which one ?
Click to expand...
Click to collapse
Yes, C432, i installed it on B363 bur don't know if it was the same at RROS.
Now that you ask I'm not that sure it could also have been the mistake that I maybe used HWOTA7 which I used to upgrade to Oreo B363. I tried to rollback to B130.
It was a STF_RECOVERY_NoCheck.img Recovery I think it actually was the Nougat version but could have also been oreo...
Thanks for replying btw
Try to install TWRP from this thread:
https://forum.xda-developers.com/showpost.php?p=75680308
Dpesnit install successfully ? Can you boot twrp now ?
oslo83 said:
Try to install TWRP from this thread:
https://forum.xda-developers.com/showpost.php?p=75680308
Dpesnit install successfully ? Can you boot twrp now ?
Click to expand...
Click to collapse
Installed successfully but still same result, can't boot into recovery..
You are trying with usb unplugged and with vol+ button ?
oslo83 said:
You are trying with usb unplugged and with vol+ button ?
Click to expand...
Click to collapse
Everytime I try to do without usb plugged I will get a red sign with a lightning that tells me battery is empty, this won't change if I charge it, could be an error but also could have to do something that it always stays on this booting now screen when plugged in and not in fastboot mode. Actually this Battery sign pops up everytime I shut it down when I try to boot(just not with fastboot), even if plugged in but then it works after a few seconds. I asked Multitool for Battery voltage in fastboot and got this answer: ...
(bootloader) 5298mv
OKAY [ 0.012s]
finished. total time: 0.020s
Btw I just noticed that in stuck screen red led lights up like every 2-3sec
Thank you for the fast answer
Leave the phone overnight (around 12 hours) to be charged with the original charger then try again on the computer
to restore it.
It happens to myself with a Motorola phone years ago.
mihaidenis said:
Leave the phone overnight (around 12 hours) to be charged with the original charger then try again on the computer
to restore it.
It happens to myself with a Motorola phone years ago.
Click to expand...
Click to collapse
I will try, what type of restoring do you mean?
Edit: Didn't work for me.. Still tells me battery is empty. I think it has to be a software issue or so:crying:
You can restore it using a paying software called DC-Phoenix.
I own a license, PM me if you need further help.
(this all happend 3 years ago and im asking now as i need a backup phone )
i flashed twrp and pixel experience well dum me clicked reset in pixel experience settings then it bootlooped into twrp for eternity now dum 2019 me thought that wiping twrp from fastboot would force it to boot into the system well it didnt work and even now whatever i try it does not boot (it just vibrates but will not boot i tried all combinations possible and also tried the miraclebox guide which didnt work)
Zainullahk1234 said:
(this all happend 3 years ago and im asking now as i need a backup phone )
i flashed twrp and pixel experience well dum me clicked reset in pixel experience settings then it bootlooped into twrp for eternity now dum 2019 me thought that wiping twrp from fastboot would force it to boot into the system well it didnt work and even now whatever i try it does not boot (it just vibrates but will not boot i tried all combinations possible and also tried the miraclebox guide which didnt work)
Click to expand...
Click to collapse
Try first charging the battery and installing the stock ROM (the latest) through SP Flash tool.
SubwayChamp said:
Try first charging the battery and installing the stock ROM (the latest) through SP Flash tool.
Click to expand...
Click to collapse
ill try that but i dont expect it to work due to it not booting
Zainullahk1234 said:
ill try that but i dont expect it to work due to it not booting
Click to expand...
Click to collapse
Well, this is the whole idea to flash a stock ROM, if it is an issue at software level it has to solve it. Check carefully some things that could help to diagnose the brick level, like device is vibrating, device can boot till bootanimation, logo is showing some letters and so on.
SubwayChamp said:
Well, this is the whole idea to flash a stock ROM, if it is an issue at software level it has to solve it. Check carefully some things that could help to diagnose the brick level, like device is vibrating, device can boot till bootanimation, logo is showing some letters and so on.
Click to expand...
Click to collapse
it wont do anything but vibrate when i hit the power button
Zainullahk1234 said:
it wont do anything but vibrate when i hit the power button
Click to expand...
Click to collapse
Try flashing the firmware and see what happens, and if, which modes are available for you, fastboot, recovery.