Database Users

Reverted from CM 10.2 to stock 4.4, Stuck in a bootloop

Hey, I had CM10.2 which for some reason caused me a lot of troubles with battery and wifi so I Decided to revert to stock 4.4. I downloaded the stock from google and I installed it with the fastboot through the command prompt. But for some reason, the phone just won't turn on, it goes into the KitKat boot animation and just gets stuck there forever. What should I do?
I already tried wiping cache and it didnt really help...
Thanks!

Try a factory reset from the stock recovery.
All of the images flashed successfully without any problems?
Sent using xda-developers app

Chromium_ said:
Try a factory reset from the stock recovery.
All of the images flashed successfully without any problems?
Sent using xda-developers app
Click to expand...
Click to collapse
All of the images were flashed successfully, but if I do a factory reset, what will it exactly do? won't it erase litterally anything I Have and then I will stay out of options? I have never done a factory reset so I dont really know. If I have a CM 10.2 flashable ZIP on my storage, will it stay there after the Factory reset? Because every time I have a problem with a certain rom I just flash back to the CM 10.2

PriStol said:
All of the images were flashed successfully, but if I do a factory reset, what will it exactly do? won't it erase litterally anything I Have and then I will stay out of options? I have never done a factory reset so I dont really know. If I have a CM 10.2 flashable ZIP on my storage, will it stay there after the Factory reset? Because every time I have a problem with a certain rom I just flash back to the CM 10.2
Click to expand...
Click to collapse
It will wipe all user data including the internal storage. Basically the phone will be exactly how it was from the factory. So yes, the cm10.2 that you have will be gone after the factory reset.
But I'm pretty confident that doing a factory reset will get the phone to boot.
Sent using xda-developers app

PriStol said:
All of the images were flashed successfully, but if I do a factory reset, what will it exactly do? won't it erase litterally anything I Have and then I will stay out of options? I have never done a factory reset so I dont really know. If I have a CM 10.2 flashable ZIP on my storage, will it stay there after the Factory reset? Because every time I have a problem with a certain rom I just flash back to the CM 10.2
Click to expand...
Click to collapse
A factory reset does indeed wipe everything on your phone. You're learning the hard way why it is a good idea to periodically back up your phone.
The best thing about doing a factory image reset is that you start from a know good point. If the ROM you want to use is based on 4.4, then use the 4.4 factory image. Likewise if the ROM is based on 4.4.2 then use that factory image.
Sent from my Nexus 4 using Tapatalk

Maybe you've got the same issue that I just described here : http://forum.xda-developers.com/showthread.php?t=2595057
edit : apparently nothing to do with the radio afterall

Guys Thanks you so much I did a factory reset and my phone is now working all good with 4.4.2
Just a question, Is my phone still rooted after a factory reset?

PriStol said:
Guys Thanks you so much I did a factory reset and my phone is now working all good with 4.4.2
Just a question, Is my phone still rooted after a factory reset?
Click to expand...
Click to collapse
No. It was no longer rooted after flashing the stock images.
But getting root back isn't that hard. Just install a custom recovery and flash the latest supersu.
Sent using xda-developers app

Chromium_ said:
No. It was no longer rooted after flashing the stock images.
But getting root back isn't that hard. Just install a custom recovery and flash the latest supersu.
Sent using xda-developers app
Click to expand...
Click to collapse
Ok thanks

I need your help guys. (bricked nexus 6p)

Okay, so I've been reading XDA for a while now to root my devices and install custom ROMs and its been incredibly helpful. However I have a huge issue with my nexus 6p and can't find a way to solve it.
Here goes....
I bought it of eBay a few months ago and unlocked the boot loader and rooted the phone plus i also installed twrp and made a nandroid backup. I then installed pure nexus rom and the phone was working incredibly well.
Fast forward to this week, I decided I wanted to upgrade to cm13, since I missed the cm theme engine. So I Wiped my device clean using twrp. And installed cm 13 and the gapps then rebooted.
The phone booted perfectly but on the optimising apps screen it would reboot and tell me to enter the password that I originally had on the pure nexus ROM. After doing so it would re optimise the apps but would crash and reboot. It was doing this continuously.
Twrp also asked for this password on every boot before it let me see the main recovery menu.
So then I took the logical next step and decided to wipe the phone clean again using twrp. Seeing as my password seemed to not clear the first time.
After the wipe, I decided to use the original nandroid backup to restore my device as the password thing was still showing up. And cm 13 was still not installing. Neither was pure nexus.
Okay this is where it went downhill. I hit restore and had everything checked. The process was going well but instead of the restore completing and twrp saying it was successful. It crashed halfway and rebooted.
Since then its stuck in a bootloop. Its on the google splash screen and then reboots to the google splash screen continuously. And does not boot to the os.
On another note. The bootloader is still unlocked. The recovery works. And so does adb/fastboot. So I wouldn't consider it hard bricked.
Here's what I've tried so far:
I've used the wugfresh root toolkit to flash stock and unroot the phone. With softbrick checked. Still nothing. Phone boots to the splash screen and then reboots to the splash screen.
I then reflashed twrp 3.0.2-1 . which worked And its not asking for my password anymore.
Again I tried restoring from my nandroid and it crashed midway which makes me think the nandroid backup is/was corrupted causing the issue in the first place?
I've also tried to just restore and Flash twrp again and then install pure nexus ROM. And still nothing?
I can also still mount my phone to the PC and copy and remove files.
On another note I find it interesting that although the ROM is installed. And the storage bar on my PC is partially filled showing that it clearly has a ROM installed. The phone does not have the standard android file system. Just the twrp backup folder and that's it.
I would be honoured if you could help me out here. And get my 6p up and running again.
Thank you . [emoji45]

I would suggest you flash the factory stock system image using fastboot to get your 6P back up and running.
If you don't have the factory image they can be downloaded from here
Extract the factory image then use fastboot to flash
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Check out this guide which has all the information you need, especially around device encryption and flashing roms. Lastly gaining root is as simple as flashing SuperSU or Phh's SuperUser in TWRP.
I hope that helps, let me know if you get stuck.

Yea just flash stock image I had this happen to me before and flashing stock image fixed it.

Thanks guys. I'm going to read the guide and try it out. Then let you know how it all goes. Fingers crossed it all works
Sent from my ONE A2003 using Tapatalk

im_Zak said:
Thanks guys. I'm going to read the guide and try it out. Then let you know how it all goes. Fingers crossed it all works
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
FYI don't backup efs partition with that version of twrp. It's a known issue.

i did not realize that twrp had that issue
And guys, I followed the fastboot process by the letter and although everything worked well. The nexus 6p is still bootlooping on the google splash screen and not going any further. :crying:
What should I do? i've added the cmd window screenshot so you guys can have a look.

Try this thread:
http://forum.xda-developers.com/and...r-bootloop-t3454938/post68872362#post68872362
I worked for me when I was having issues. If it worked for you, please make sure to thank the OP in the thread.

this looks promising. thank you. i'll have a go now. might need your help if i get stuck somewhere though :good:

pctechdroid said:
Try this thread:
http://forum.xda-developers.com/and...r-bootloop-t3454938/post68872362#post68872362
I worked for me when I was having issues. If it worked for you, please make sure to thank the OP in the thread.
Click to expand...
Click to collapse
Thank you so so much dude. After countless hours trying everything to get my nexus 6p up and running to no avail this post did the trick.
Respect!!?✌✌??

im_Zak said:
Thank you so so much dude. After countless hours trying everything to get my nexus 6p up and running to no avail this post did the trick.
Respect!!
Click to expand...
Click to collapse
Upgrade to TWRP 3.0.2-2 real quick. You didn't need that guide(in terms of his nandroid) but I am glad it worked. Just need to wipe efs partition using adb commands.

I see. And I have upgraded to the latest twrp so hopefully it doesn't not happen again
Sent from my ONE A2003 using Tapatalk

im_Zak said:
I see. And I have upgraded to the latest twrp so hopefully it doesn't not happen again
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Good deal!!! There's a build that's unofficial of 3.0.2-3 that you can also jump onto. The current version 3.0.2-2 has a bug with backups on Android N. There was a comprehensive post that someone made about the issues with the different versions but I cannot find it for the life of me.

Jammol said:
Good deal!!! There's a build that's unofficial of 3.0.2-3 that you can also jump onto. The current version 3.0.2-2 has a bug with backups on Android N. There was a comprehensive post that someone made about the issues with the different versions but I cannot find it for the life of me.
Click to expand...
Click to collapse
Thanks for the heads up!

Moto x pure XT1575 What am i doing wrong?!

I bought this phone used and the person who had it before me it rooted and installed some of different ROMs on it. After getting my used moto x pure 2015 running android 6.0. I booted it up and tested all the functions (including downloading a few apps) Wi-Fi, camera, audio/charging jacks ext. Everything worked fine. So did normal factory reset (not using TWRP) just to make sure everything was clean before using it as my daily. Then, (BUM BUM BUM!) when I tried to start downloading all my apps. None of them would download even though the Wi-Fi was working. Error 492 I think.
I started trying custom ROMs because I was having two big issues (apps not downloading and incoming call not bringing up accept/decline screen) with my stock rom. and wanted to fix those issues with a fresh stock image.
This is all new to me and has not been as easy as anticipated. If anyone knows a clean factory image I could flash or a fail proof fix to error 492 that would be helpful. I really just want to return to fully working Motorola stock android, but the files I have used haven’t fixed the issue. I have searched for a factory image without finding one…
Is there a way to flash the Motorola image through TRWP?
Otherwise, maybe you can help me with my flashing method, and maybe tell me what I am doing wrong. I tried to flash multiple stock images all with the same issue. I have also tried to flash Resurrection Remix, and Brocken OS, both having resulted in a bootloop. I am starting to think I have done something wrong. The steps I have taken so far have been these:
My bootloader is unlocked status code 3.
My phone is not rooted. Do I need root?
First I downloaded adb and fastboot.
Then I flashed TWRP (3.0.2).
I never installed the official Motorola stock image because flashing it from fast boot wouldn’t work and it couldn’t be flashed with TWRP because it is a .gz not a .zip. (I knew a .gz needs to be flashed with fastboot but I knew TWRP was easer so I didn’t fuss with it)
After flashing TWRP to my phone, I downloaded (yes, I checked the md5) the various ROMs to my computer then transfered them to my phone via micro SD card.
Here are the file’s names if that matters:
moto_x_pure_edition_stock_x1575_mphs24.49-18-3_v1-odexed
(booted and Wi-Fi but play store won’t download apps)
moto_x_pure_edition_stock_x1575_mph24.49-18_v1-odexed
(booted but no Wi-Fi)
Broken-v4.9.1-clark-6.0.1-OFFICIAL-20160824 (with Broken_gapps_lp5.1.x_09172015)
(Brocken was the only non-stock that got past boot, but I still couldn’t get past set up without an error and never made it to the system.)
ResurrectionRemix-N-v5.8.0-20161220-clark (7.1 gapps failed to flash but I booted it anyway.)
(boot loop after both of my tries)
I got Wi-Fi working on one of the above stock ROMs (so I KNOW it works) but couldn’t even turn Wi-Fi on in all the others.
The method I used to flash all of the above files in TWRP was:
Wipe
Full wipe (davlik cache, data, system, cache)
(used for RR and Brocken)
Factory reset (using TWRP) (davlik cache, data , cache)
Used for the stock ROMs or even after flashing .zip file I got the error: no OS installed.
Install
Select file of ROM flash (gapps if needed) and flash
I can’t remember which ones but on some of them after flashing I again did a factory reset.
Then I rebooted
Thanks for reading. Sorry it was so long. I tried to add as much useful information as possible. Hopefully someone smarter than me will see my error(s) and help me get my phone into fully working order.

cont.
I really just want to return to fully working Motorola stock android, but the files I have used haven’t fixed the issue. I have searched for a factory image without finding one…
Is there a way to flash the Motorola image through TRWP?
Otherwise maybe you can help me out with my flashing method and maybe tell me what I am doing wrong. I tried to flash multiple stock images all with the same issue. I have also tried to flash Resurrection Remix, and Brocken OS, both having resulted in a bootloop. I am starting to think I have done something wrong. The steps I have taken so far have been these:
My bootloader is unlocked status code 3.
My phone is not rooted. Do I need root?
First I downloaded adb and fastboot.
Then I flashed TWRP (3.0.2).
I never installed the official Motorola stock image because flashing it from fast boot wouldn’t work and it couldn’t be flashed with TWRP because it is a .gz not a .zip. (I knew a .gz needs to be flashed with fastboot but I knew TWRP was easer so I didn’t fuss with it)
After flashing TWRP to my phone, I downloaded (yes, I checked the md5) the various ROMs to my computer then transfered them to my phone via micro SD card.
Here are the file’s names if that matters:
moto_x_pure_edition_stock_x1575_mphs24.49-18-3_v1-odexed
(booted and Wi-Fi but play store won’t download apps)
moto_x_pure_edition_stock_x1575_mph24.49-18_v1-odexed
(booted but no Wi-Fi)
Broken-v4.9.1-clark-6.0.1-OFFICIAL-20160824 (with Broken_gapps_lp5.1.x_09172015)
(Brocken was the only non-stock that got past boot, but I still couldn’t get past set up without an error and never made it to the system.)
ResurrectionRemix-N-v5.8.0-20161220-clark (7.1 gapps failed to flash but I booted it anyway.)
(boot loop after both of my tries)
I got Wi-Fi working on one of the above stock ROMs (so I KNOW it works) but couldn’t even turn Wi-Fi on in all the others.
The method I used to flash all of the above files in TWRP was:
Wipe
Full wipe (davlik cache, data, system, cache)
(used for RR and Brocken)
Factory reset (using TWRP) (davlik cache, data , cache)
Used for the stock ROMs or even after flashing .zip file I got the error: no OS installed.
Install
Select file of ROM flash (gapps if needed) and flash
I can’t remember which ones but on some of them after flashing I again did a factory reset.
Then I rebooted
Thanks for reading. Sorry it was so long. I tried to add as much useful information as possible. Hopefully someone smarter than me will see my error(s) and help me get my phone into fully working order.

I think this thread will help you: https://forum.xda-developers.com/showthread.php?t=3489110
Sent from my XT1572 using Tapatalk

Install stock firmware via fastboot... if that dont fix the issue, install TWRP make a full wipe, FULL, and install the stock firmware again, eventualy that sould fix the issue.

RK2116 said:
Install stock firmware via fastboot... if that dont fix the issue, install TWRP make a full wipe, FULL, and install the stock firmware again, eventualy that sould fix the issue.
Click to expand...
Click to collapse
I'm having a similar issue. Tried the TruPure rom but I want to switch back to stock. If I do a full wipe, would I be able to use the files that Motorola provides on their website and flash those throught fastboot? Or through TWRP? Any chance you have a link to a guide on how to do the latter option (installing through TWRP)? I'm just trying to get my device back to 100% stock so that I can receive OTA.

cdiaz8 said:
I'm having a similar issue. Tried the TruPure rom but I want to switch back to stock. If I do a full wipe, would I be able to use the files that Motorola provides on their website and flash those throught fastboot? Or through TWRP? Any chance you have a link to a guide on how to do the latter option (installing through TWRP)? I'm just trying to get my device back to 100% stock so that I can receive OTA.
Click to expand...
Click to collapse
Odexed one, install with TWRP, full wipe before doing that, no GApps, just ROM, them, install stock recovery vía fastboot. After that you Will be stock with OTAs.
https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120

RK2116 said:
Odexed one, install with TWRP, full wipe before doing that, no GApps, just ROM, them, install stock recovery vía fastboot. After that you Will be stock with OTAs.
https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
Click to expand...
Click to collapse
Thank you for sharing that link. I think I get it but it seems too easy considering what I've tried so far. Just to make sure I get it:
I should download the odexed rom, go to twrp and wipe data, cache and dalvik then flash the odexed rom through the install function? And thats it? I've literally tried a ton of stuff so if this takes care of it, this is great!

cdiaz8 said:
Thank you for sharing that link. I think I get it but it seems too easy considering what I've tried so far. Just to make sure I get it:
I should download the odexed rom, go to twrp and wipe data, cache and dalvik then flash the odexed rom through the install function? And thats it? I've literally tried a ton of stuff so if this takes care of it, this is great!
Click to expand...
Click to collapse
Yes, also wipe system, make a backup before If you want, but remember, for the OTAs support you need yo flash the stock recovery via fastboot. Good luck.

RK2116 said:
Yes, also wipe system, make a backup before If you want, but remember, for the OTAs support you need yo flash the stock recovery via fastboot. Good luck.
Click to expand...
Click to collapse
This got me back to stock! You are the real MVP.
So I remember seeing a recovery.img file in the factory image that motorola posted on its site. Does it have to be a specific stock recovery or do I need a specific one to match with the file I just installed?
thanks again

cdiaz8 said:
This got me back to stock! You are the real MVP.
So I remember seeing a recovery.img file in the factory image that motorola posted on its site. Does it have to be a specific stock recovery or do I need a specific one to match with the file I just installed?
thanks again
Click to expand...
Click to collapse
Just a stock one, if Motorola have one use that.

RK2116 said:
Just a stock one, if Motorola have one use that.
Click to expand...
Click to collapse
So I'm on stock build 49-18-8 and flashed the recovery from 49-18-3. I went into fastboot and selected recovery. I got the android character with an !
I then did the power button and volume up and got into stock android recovery. Am I supposed to see the android character with ! each time I try to reach the recovery menu? Just wondering if I did this correctly.
Thanks again for pointing me to these resources!

cdiaz8 said:
So I'm on stock build 49-18-8 and flashed the recovery from 49-18-3. I went into fastboot and selected recovery. I got the android character with an !
I then did the power button and volume up and got into stock android recovery. Am I supposed to see the android character with ! each time I try to reach the recovery menu? Just wondering if I did this correctly.
Thanks again for pointing me to these resources!
Click to expand...
Click to collapse
Yes.

Nexus 6p bootloop (NOT same as Infamous BLOD)

Hi! Guys I have a problem, which doesn't resemble the BLOD, so here is what has happened. I was running stock android June build on 6p, rooted. And my phone started random reboots. I thought it could be fixed with either stock or custom rom. So I decided to flash AOSPA. I went into twrp but could not flash it, phone rebooted each time. I tried stock images via flash all command as well as manual. No rom worked although I could flash kernel etc. I used The Flash's custom twrp and fixed data and was able to flash rom easily, but it bootlooped on google logo, and rebooted. Now I can flash roms etc but it bootloops. Although Tesla rom did go into bootanimation before bootlooping.
So what can I do? Is it software related? What do you guys say!
PS. I did look into other threads, nothing was similar, although I did try a few mentioned fixes.

osamaasif786 said:
So what can I do? Is it software related? What do you guys say!
Click to expand...
Click to collapse
Use fastboot to FORMAT system, userdata and cache. Note any errors during the FORMAT process.... and then try flashing a full image from Google using flash-all.bat

v12xke said:
Use fastboot to FORMAT system, userdata and cache. Note any errors during the FORMAT process.... and then try flashing a full image from Google using flash-all.bat
Click to expand...
Click to collapse
It gives no error and did try the flash-all.bat method no luck.

osamaasif786 said:
It gives no error and did try the flash-all.bat method no luck.
Click to expand...
Click to collapse
I'd say you were squarely in a small group of people who are able to access and fully use Recovery but still boot loop after formatting and installing a clean image. If you've already tried a factory reset from the stock recovery I think you are done. Hardware issue. Replacing the motherboard is a fix, but not economically viable.

I had the same issue formatting data and cache to Ext4 and flashing modified stock ROM fixed. It would boot to Google logo freeze reboot and sometimes get to boot animation freeze and reboot.

Exodusche said:
I had the same issue formatting data and cache to Ext4 and flashing modified stock ROM fixed. It would boot to Google logo freeze reboot and sometimes get to boot animation freeze and reboot.
Click to expand...
Click to collapse
Which modified one, can you share the link?

osamaasif786 said:
Which modified one, can you share the link?
Click to expand...
Click to collapse
Cortex ROM it's flashable stock firmware with extras . Though my symptoms where the same I hope I'm not giving you false hope. Worth a shot though.

The only was I recover my phone without replacing is using https://forum.xda-developers.com/nexus-6p/general/boot-images-bootloop-t3633723 < method from here... but the phone is lag af as it is only running 1 core on stock july build. Good luck for that.

I have the same issue going on. i was trying to flash magisx and suddenly it is stuck in bootloop. i tried flashing stock images and everything. i can access twrp and flash eveything and they are getting flashed fine but still it is stuck on the bootloop.

TheTickReborn said:
I have the same issue going on. i was trying to flash magisx and suddenly it is stuck in bootloop. i tried flashing stock images and everything. i can access twrp and flash eveything and they are getting flashed fine but still it is stuck on the bootloop.
Click to expand...
Click to collapse
So have you used fastboot to FORMAT system, userdata and cache? Did each format command complete with no errors?

Rom and recovery not booting

Hi everyone,
I hope that you all had/are having a lovely christmas. Unfortunately for my S4 christmas has been terrible. The phone has had low storage for a week now and was crashing as a result and I didn't have time to fix it. Yesterday the phone was running horribly and wasn't doing anything that I touched. So I rebooted which took way too long and when I did it again the phone now does not pass the galaxy s4 screen and also TWRP recovery will not pass its boot screen either.
I have attempted flashing stock recovery which said error mounting all partitions, afterwards a reboot allowed me to wipe cache thinking it would allow the phone to boot, but no change.
I am thinking to flash stock samsung rom through download mode since it is still functional so I can recover my data before moving to my new phone. Will this be a good idea considering that the Lineage OS rom is significantly smaller than the stock samsung rom or will it not worsen the situation?
Thanks for your help!

Flashing a stock ROM may not allow you to recover the data.
Did you try re-flashing the same version of TWRP or a different version to see if that helps to mount the data partition?

audit13 said:
Flashing a stock ROM may not allow you to recover the data.
Did you try re-flashing the same version of TWRP or a different version to see if that helps to mount the data partition?
Click to expand...
Click to collapse
Thank you for your response! I have tried flashing flashing both the same TWRP and different version which was in fact smaller. This saw no improvement in the condition and I still can not pass the TWRP boot screen.
What else do you suggest I try?
Thanks for your time!

Tried re-flashing the same ROM that was on the phone before the issue started?
Flashing a stock ROM may allow the phone to boot to its desktop without a factory reset. You may want to use this method as a last resort to get the phone into working condition.
It's also possible that the internal memory has failed which means there is no economical way to recover the data.

audit13 said:
Tried re-flashing the same ROM that was on the phone before the issue started?
Flashing a stock ROM may allow the phone to boot to its desktop without a factory reset. You may want to use this method as a last resort to get the phone into working condition.
It's also possible that the internal memory has failed which means there is no economical way to recover the data.
Click to expand...
Click to collapse
I am actually unable to flash anything without odin because I can't boot into my recovery which hangs on its twrp screen. Also if I have set my partitions to f2fs will this interfere with flashing the stock rom?

I am not sure if the file system will interfere with Odin flashing the ROM. Sounds like you may have to try flashing with Odin which will probably result in data loss.

audit13 said:
I am not sure if the file system will interfere with Odin flashing the ROM. Sounds like you may have to try flashing with Odin which will probably result in data loss.
Click to expand...
Click to collapse
Do you think it could possibly be a bootloader or kernel issue? Perhaps I could try flashing those first before a full factory firmware?

I don't think it is a bootloader issue as the phone will boot. The bootloader is similar to a computer bios. The computer bios checks to make sure the basic hardware is present and functioning. If the basics are met, the bios hands control of the device to the OS. In this case, the bootloader is handing control of the device to the OS but the OS can't boot.
I doubt that it is a kernel problem because the phone worked before so the kernel is compatible with the phone.

audit13 said:
I don't think it is a bootloader issue as the phone will boot. The bootloader is similar to a computer bios. The computer bios checks to make sure the basic hardware is present and functioning. If the basics are met, the bios hands control of the device to the OS. In this case, the bootloader is handing control of the device to the OS but the OS can't boot.
I doubt that it is a kernel problem because the phone worked before so the kernel is compatible with the phone.
Click to expand...
Click to collapse
So I took the plunge and installed the stock firmware now the phone boots and I'm greeted with a message asking to factory reset because encryption failed. I reinstalled TWRP and for some reason that still can't fully boot. I want to get it working so I can access the storage to remove the important files through either mtp or adb. There is some form of adb working whilst TWRP is booting but it can't access or see anything in the partitions or mount them even running as root.
Any ideas to get TWRP or any other recovery working on the phone? (The stock recovery booted just fine before I flashed TWRP)
Any help is much appreciated!
Kind Regards,
Crapping_Bricks

I think the stock Rom doesn't recognise the file system and thinks the encryption failed.
I'm not sure what else to suggest other than a factory reset since twrp doesn't allow pulling the data via adb or mounting the data partition.