Database Users

How to flash and root new 4.0.4 ICS stock rom

NOT MY CREDITS
Perhaps scryshark should made this post
(This applies both 7500 7510 and was writen when we didn't had the wifi only version, so for 7510 ignore the mention steps)
On step 1, you can use also:
--------------------------------
ODIN->PDA->SELECT FIRMWARE AND AFTER PUT TAB IN FLASH MODE CLICK START
--------------------------------
scaryshark said:
Here's a definitive guide for P7510 owners on how to install stock ICS on their tabs with root. How do I know it's definitive? Well, I'm running it right now with no problems!
NOTE: Obviously I shouln't have to say this but... WiFi only guys may run into a bug of some sort if trying to apply this. I haven't had any prblems yet. Everything works: WiFi, GPS, Camera, Auto-brightness, G-Sensor etc. If something wrong happens, then it's not my fault!
That said there are a few things going on because of running a P7500 ROM on a P7510. Like there is a signal indicator in the status bar showing no signal. There are mobile data options in the settings menu. The device is recognised as a P7510, i think you get the point.
Now to the actual instructions.
Step 1: Putting ICS on
- Create a Nandroid backup!
- Download & install Mobile Odin by Chainfire. [Redistrubution is not allowed so I've linked to his thread] <- Read that properly before you go onto the next step so it's istalled properly!
- Download the firmware and unzip
- Move the file P7500XXLQ8_P7500OXALQ8_P7500XXLQ8_HOME.tar.md5 to the root of your Tab.
- Open Mobile Odin
- Select the .md5 firmware you just put onto your Tab
- *IMPORTANT FOR WIFI TABS* Select Modem and press Clear
(there's no need to select the option of auto root or odin insall 'cos it wont work! )
- Select the 2 wipe options
- Plug your tab into the power supply
- Press the fflash firmware button
---------------------------------------------------
LET IT DO IT'S OWN THING. LEAVE IT AND WAIT FOR IT TO RESTART TO THE SETUP SCREEN
---------------------------------------------------
Done now your running ICS, but wait - you don't have root! or CWM recovery for that matter! :crying: Don't worry, keep reading!
CWM Recovery and Rooting:
- Download this update.zip for rooting your tab and move it to the root of your tab
- Put your tab into download mode
- Plug it into the computer
- Let the computer install the drivers (Automatic on Win 7 - unsure about other OS's)
- Download and unzip Odin 1.85
- Download CWM Touch Recovery & save to same folder as Odin 1.85
- Open up odin
- Click PDA and select the file named recovery.tar.md5
- Click start
-------------------------------------------------------------------------------
LET ODIN DO IT'S THING & WAIT FOR TAB TO RESTART
-------------------------------------------------------------------------------
- Put the tab into recovery mode.
- Select install from sd card and select Samsung_Galaxy_Tab_10.1_root.zip
---------------------------------------------------------------------------------
LET RECOVERY DO IT'S THING
-----------------------------------------------------------------------------------
- Tap go back and then reboot now
There you have it stock ICS for P7500 & P7510 rooted.
Click to expand...
Click to collapse

It works for me. I restored my apps + data using Mybackup Pro. Thanks for your work!

jpl69 said:
NOT MY CREDITS
Perhaps scryshark should made this post
(This applies both 7500 7510 and was writen when we didn't had the wifi only version, so for 7510 ignore the mention steps)
On step 1, you can use also:
--------------------------------
ODIN->PDA->SELECT FIRMWARE AND AFTER PUT TAB IN FLASH MODE CLICK START
--------------------------------
Click to expand...
Click to collapse
Cool! It may be possible to install the CWM recovery during the ROM install by downloading it from the Cwm website and using that recovery . I'm under the recovery option in mobile odin and skipping straight from initial reboot to putting it into recovery mode and installing the root update.zip. However I forgot to do that so I'm not sure if it'll work or not!
Sent from my GT-P7510 using XDA Premium HD app

So the firmware is for the UK. What happens if I flash this on my US tab?

9xnine said:
So the firmware is for the UK. What happens if I flash this on my US tab?
Click to expand...
Click to collapse
nothing. just flash it it will be OK

real77055 said:
nothing. just flash it it will be OK
Click to expand...
Click to collapse
If anyone has the issue where it just sits at the Samsung logo just reboot into recovery and do a data/cache wipe.

I assume the camera works?

awwilson21 said:
I assume the camera works?
Click to expand...
Click to collapse
Everything works.

After pressing flash firmware, I have the odin logo on my tab for 10 mins now.
Is this normal?
If not, what should I do now?

Thanks for bringing this nice guide.
So do I get this right that there is no way to flash the rom without wiping?

Im a little nervous here. Did I just brick my device?
Why is the odin logo still on my tab? Wasnt there supposed to be a restart?

tomerstern said:
After pressing flash firmware, I have the odin logo on my tab for 10 mins now.
Is this normal?
If not, what should I do now?
Click to expand...
Click to collapse
I used Normal ODIN on my PC. When it finished it rebooted and hung at the Samsung logo. I rebooted into recovery and wiped data/cache and it fixed it. You could attempt to reboot into recovery. If Mobile ODIN did it's thing you will be back to stock recovery. If that's the case then wipe data/cache and reboot.
---------- Post added at 12:58 PM ---------- Previous post was at 12:57 PM ----------
tomerstern said:
Im a little nervous here. Did I just brick my device?
Why is the odin logo still on my tab? Wasnt there supposed to be a restart?
Click to expand...
Click to collapse
I doubt you bricked it. Hold power and volume down to reboot into recovery or download mode again. If you can get to recovery and download mode you are fine.

OK, I rebooted, I have the following options:
1. reboot system now
2. apply update from external storage
3. wipe data / factory reset
3. wipe cache partition
4. apply update from cache.
Which one should I choose?

tomerstern said:
OK, I rebooted, I have the following options:
1. reboot system now
2. apply update from external storage
3. wipe data / factory reset
3. wipe cache partition
4. apply update from cache.
Which one should I choose?
Click to expand...
Click to collapse
OK so you have the stock recovery. Thats good. first wipe data/factory reset. Then wipe cache partition, then reboot.

Thanks so much!
I now have ICS running!!
That was a tough 30 mins

tomerstern said:
Thanks so much!
I now have ICS running!!
That was a tough 30 mins
Click to expand...
Click to collapse
We've all been there. Just remember before you start flashing make sure you know which buttons will get you into recovery and Download mode. If you can get to recovery or download mode there is no reason to freak out. Also, ODIN is your friend. I recommend having a copy of the PC version installed on your PC just in case something goes wrong with a flash or Mobile ODIN. Glad it's up and running for you!

I can get the Rom running alright. My problem is that I get the rolling recovery issue. With the a 5.0.... recovery I get rolling recovery, but the Rom runs fine. If I install the recovery from Pershoots page which is 5.5.0.4, then I get no Rolling recovery, but I get a rolling Rom instead! Frustrating!
Edit: Installed Pershoots recovery v6.0.1.0, didn't solve the issue, but flashing the bootloader method from here: http://forum.xda-developers.com/showthread.php?t=1555984 fixed things. The bootloader change didn't work for me on the older recovery's.
Edit 2: Scrap that, I hadn't turned the screen off yet, that's when it happens lol.

9xnine said:
Everything works.
Click to expand...
Click to collapse
Awesome! So CM10 should be fully functional soon!

Yeah, I tried the bootloader thing as well with the rolling recovery here. Wasn't a great idea anyhow, I guess we need to flash the bootloader from the 4.0.4 ROM, I just don't know how or how to make such a tar on Windows...
Sent from my GT-P7510 using XDA Premium HD app

Yeh I'm not sure either. I managed to get the recovery and rom working for honeycomb and then on to ICS AOSP, but not sure what to do to get this rooted etc!
Sent from my GT-P7510 using xda app-developers app

[Q] Galaxy S4 GE no root after motochopper

Ok, I'm total noob but not complete idiot. Just want to get that out of the way
I have have the Galaxy S4 Google Edition running Android 4.3.
I unlocked the bootloader before the Android 4.3 update, but have never had root access. I've tried motochopper program, but keep getting failure errors and continued no root.
What I'd like to do is restore my device to stock and run it over again. I'm sure I did something wrong at somepoint.
Can someone please help me?
Thanks

nhlfan14 said:
Ok, I'm total noob but not complete idiot. Just want to get that out of the way
I have have the Galaxy S4 Google Edition running Android 4.3.
I unlocked the bootloader before the Android 4.3 update, but have never had root access. I've tried motochopper program, but keep getting failure errors and continued no root.
What I'd like to do is restore my device to stock and run it over again. I'm sure I did something wrong at somepoint.
Can someone please help me?
Thanks
Click to expand...
Click to collapse
1. Go here and download the CWM / TWRP / MobileODIN installable ZIP
http://forum.xda-developers.com/showthread.php?t=1538053
Place the installable zip on your INTERNAL SD Card.
2. Get CWM:
http://www.clockworkmod.com/rommanager
Go here and grab CWM 6.0.3.6 for the INTERNATIONAL I9505 - yes, it works on the I9505G
Put your phone in fastboot mode by turning off the phone completely. Hold down Vol-Up Vol-Down and power simultaneously.
Since you already seem to have adb, you probably have the fastboot executable.
From your computer's command line type "fastboot boot recovery-clockwork-6.0.3.6-jfltexx.img"
This will boot recovery - temporarily - it will not overwrite the recovery on your phone.
Choose install zip from sdcard. Navigate to the installable zip that you placed on you sdcard in a prior step.
Reboot. When CWM asks to fix "this may overwrite your recovery" SAY NO. Just let it reboot.
You will be rooted. Download and install busybox from the market to complete the process.

bleez99 said:
1. Go here and download the CWM / TWRP / MobileODIN installable ZIP
http://forum.xda-developers.com/showthread.php?t=1538053
Place the installable zip on your INTERNAL SD Card.
2. Get CWM:
http://www.clockworkmod.com/rommanager
Go here and grab CWM 6.0.3.6 for the INTERNATIONAL I9505 - yes, it works on the I9505G
Put your phone in fastboot mode by turning off the phone completely. Hold down Vol-Up Vol-Down and power simultaneously.
Since you already seem to have adb, you probably have the fastboot executable.
From your computer's command line type "fastboot boot recovery-clockwork-6.0.3.6-jfltexx.img"
This will boot recovery - temporarily - it will not overwrite the recovery on your phone.
Choose install zip from sdcard. Navigate to the installable zip that you placed on you sdcard in a prior step.
Reboot. When CWM asks to fix "this may overwrite your recovery" SAY NO. Just let it reboot.
You will be rooted. Download and install busybox from the market to complete the process.
Click to expand...
Click to collapse
Worked like a charm! Only hiccup I had was it wouldn't let me access the file from the SD card, only internal memory.
2nd question is, IF i needed to restore everything to stock again at some point in the future, what steps would I need to take?

nhlfan14 said:
Worked like a charm! Only hiccup I had was it wouldn't let me access the file from the SD card, only internal memory.
2nd question is, IF i needed to restore everything to stock again at some point in the future, what steps would I need to take?
Click to expand...
Click to collapse
Since you have the stock recovery, all you need to do is unroot and you're done. Triangle Away works fine for the I9505G just in case you've bumped you flash counter. Ah yes, search the forums for busybox uninstaller. It's also a flashable zip.
Please hit the thanks button if this helped.
When dialog fails, it's time for violence.

Can someone help me again. I'd like to restore the phone to complete stock. I followed the instuctions here:
http://forum.xda-developers.com/showthread.php?t=2265477
But i get a SECURE CHECK FAIL : SBL2 error.
I just want to start fresh.
thanks.

nhlfan14 said:
Can someone help me again. I'd like to restore the phone to complete stock. I followed the instuctions here:
http://forum.xda-developers.com/showthread.php?t=2265477
But i get a SECURE CHECK FAIL : SBL2 error.
I just want to start fresh.
thanks.
Click to expand...
Click to collapse
Anybody?

nhlfan14 said:
Anybody?
Click to expand...
Click to collapse
U can try follow this guide: HERE

TWRP Boot Loop after OTA

I hit the update tonight not thinking and before I had disabled Xposed.. Now my phone is stuck in a boot loop to TWRP. I have tried to wipe dalvik and cache, tried the adb shell commands that work for most people, tried to restore a backup, but none have worked so far.
I am trying to download the stock file to revert back to stock, but it says it will take 2 hours. Any help for the weary?
Is this the only way to get it working again?

I had a similar issue a couple days ago, problem I think was due to TWRP not having "RT -RM" (? - sorry I'm not looking at the exact text right now or have it memorized) option checked in Settings in TWRP, or possibly due to issue of older TWRP version, .2 and the newer .3 works better. My System directory was unmounted and couldn't come back, stuck in boot-loop until I followed the revert-to-stock directions. I had to download the 2 gig file, taking about 2 hours, and it contained readme.txt w/ instructions and all files needed to revert, but it was very tricky. A .DLL must be overwritten in Windows to get the LG firmware flashing software to work right, and you need the .TOT file. It will work if you are diligent, so don't give up hope. I thought my bada$$ new phone was bricked but finally got it to flash back to stock using that method, possibly similar to the quote in this thread, http://forum.xda-developers.com/showpost.php?p=48434571&postcount=1150, using Verizon instructions / sprint files. You can get it back. Mod will probably lock this thread as it is not development so follow that post I just linked, along with the OP. I am in Windows 8.1 x64 so I think it can work on any version of Windows.

Oh and this thread should probably get locked as it shouldn't go in dev section, mod will probably move or lock it. Hope you figured it out.
Sent from my LG-LS980 using Tapatalk

Thread Moved as it does not belong in the Development Section.

What I did ti fix diwnload mode
I took the rom I last flashed. Opened it. went to the system folder and extracted the build.prop (opened it with notepad). Press the find button in one of the drop down menus and find the model number your g2 thinks it is and change it to what it actually is.( in my cause mines had a d801 rom so it thought was one instead of an ls980) I changed mine from d801 to ls980. Saved it (make sure its saved as build.prop). Now go into the rom you originally got the build.prop from and replace it with the new one adb push the rom to the phone in twrp then flash it. Then boot into download mode and flash away

viper42391 said:
I hit the update tonight not thinking and before I had disabled Xposed.. Now my phone is stuck in a boot loop to TWRP. I have tried to wipe dalvik and cache, tried the adb shell commands that work for most people, tried to restore a backup, but none have worked so far.
I am trying to download the stock file to revert back to stock, but it says it will take 2 hours. Any help for the weary?
Is this the only way to get it working again?
Click to expand...
Click to collapse
Go into twrp, Go to advanced, Go to terminal, Click the arrow,in bottom right.
Enter
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Hit enter then enter this dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Hit enter and reboot
Sent from my VS980 4G using XDA Free mobile app

NBreunig3 said:
Go into twrp, Go to advanced, Go to terminal, Click the arrow,in bottom right.
Enter
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Hit enter then enter this dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Hit enter and reboot
Sent from my VS980 4G using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much! Work great!

I am dealing with the same issue,
i've had the Optimus ROM installed
and decided to try out cloudy, the phone was rooted and unlocked.
after wiping in TWRP and installing the new rom phone fails to boot to system and goes to recovery automaticly.
i know i could fix this by installing everything from scratch (STOCK).
NBreunig3's solution doesnt work for me either.
what am i doing wrong in the process?

Mortred said:
I am dealing with the same issue,
i've had the Optimus ROM installed
and decided to try out cloudy, the phone was rooted and unlocked.
after wiping in TWRP and installing the new rom phone fails to boot to system and goes to recovery automaticly.
i know i could fix this by installing everything from scratch (STOCK).
NBreunig3's solution doesnt work for me either.
what am i doing wrong in the process?
Click to expand...
Click to collapse
Save the headache, flash stock 4.4.2, towelroot, autorec and start over.

vPro97 said:
Save the headache, flash stock 4.4.2, towelroot, autorec and start over.
Click to expand...
Click to collapse
Yeah that is exactly what i did (used ioroot25, and the autorec app is amazing!!), but since i didnt have anything installed on my pc i had to download everything from scratch
and a simple 20 min process became a multiple hours one (trying to avoid that in the future).
anyway i've got the cloudy ROM now and it seems that it is already unlocked so i got that going for me which is nice .

Return to Stock? (B20_Boot)

Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.

tele_jas said:
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
Click to expand...
Click to collapse
Yes you can via Rczrider 's TWRP backup

tele_jas said:
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
Click to expand...
Click to collapse
XblackdemonX said:
Yes you can via Rczrider 's TWRP backup
Click to expand...
Click to collapse
Yeah, it looks like @tenfar updated their tool to use the stock files from my untouched B20: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204

rczrider said:
Yeah, it looks like @tenfar updated their tool to use the stock files from my untouched B20: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Click to expand...
Click to collapse
if someone can make a guide on HOW-TO (Steps + FIles + Images needed) i can give it a shot...
just send me a PM if you know the HOW-TO :good:

Mmmmm, noone yet?.... I guess I'll start gathering info.
One thing I wanna make sure flashing @tenfar boot. Img = need Data wipe right?

DrakenFX said:
Mmmmm, noone yet?.... I guess I'll start gathering info.
One thing I wanna make sure flashing @tenfar boot. Img = need Data wipe right?
Click to expand...
Click to collapse
I've been flashing custom ROM's for several years, but I've bricked one too many phones over the years "not knowing" the correct way to do certain things... So I started this thread to see what those steps were because I'm too scared to attempt it myself. :silly:
So, I know I'd appreciate your efforts in this!

tele_jas said:
I've been flashing custom ROM's for several years, but I've bricked one too many phones over the years "not knowing" the correct way to do certain things... So I started this thread to see what those steps were because I'm too scared to attempt it myself. :silly:
So, I know I'd appreciate your efforts in this!
Click to expand...
Click to collapse
I'm curious too and I wanna give it shot,
P. S. Any way to use terminal or adb to pull the partition list with their Extension?
Like for sample. " ext4 system /dev/block/sde13 " or something similar with extension?

Has anyone got a step-by-step for this yet? I searched, but don't see a "Back to Stock" thread

tele_jas said:
Has anyone got a step-by-step for this yet? I searched, but don't see a "Back to Stock" thread
Click to expand...
Click to collapse
i created a Thread for users who have run into the No Boot issues and those problems , so i can gather more info of the causes of their problems but nobody had reply yet,
just waiting so i can test things and get back to Stock B20 with Root + TWRP and lock bootloader

It is still not clear where the unlock bootloader state is recorder. I have checked a couple of partitions but they are identical to locked B20 (aboot, devinfo were my prime suspects)
So assuming that this is not a permanent thing for the bootloader state and can be reversed, steps would be something like this
1. lock bootloader
2a. flash Stock B20 image and signed(tenfars) TWRP via axon7root
3. Reboot in TWRP (read only mode), full factory wipe (wipe plus /data format), flash original system image via twrp, wipe data again
4. turn off phone, don't reboot (no system start)
5. flash stock recovery via axon7root
6. Reboot to Stock Recovery direct (do not boot)
7. Factory reset from stock recovery
8. Reboot
But there are a few unknowns yet, even with stock system, boot and recovery we still have stuck loops unless using modded boot. My guess is that TWRP mods /system on exit, that's why i put read only mode but not sure if you can restore it if it's not rw. Since it's image to device it should work, RW is for mounting partition
And big one is if unlock state is permanent or not, not sure anyone tried yet

peramikic said:
It is still not clear where the unlock bootloader state is recorder. I have checked a couple of partitions but they are identical to locked B20 (aboot, devinfo were my prime suspects)
So assuming that this is not a permanent thing for the bootloader state and can be reversed, steps would be something like this
1. lock bootloader
2a. flash Stock B20 image and signed(tenfars) TWRP via axon7root
3. Reboot in TWRP (read only mode), full factory wipe (wipe plus /data format), flash original system image via twrp, wipe data again
4. turn off phone, don't reboot (no system start)
5. flash stock recovery via axon7root
6. Reboot to Stock Recovery direct (do not boot)
7. Factory reset from stock recovery
8. Reboot
But there are a few unknowns yet, even with stock system, boot and recovery we still have stuck loops unless using modded boot. My guess is that TWRP mods /system on exit, that's why i put read only mode but not sure if you can restore it if it's not rw. Since it's image to device it should work, RW is for mounting partition
And big one is if unlock state is permanent or not, not sure anyone tried yet
Click to expand...
Click to collapse
those steps were the same i was planning to do plus flashing something else, but seems like i may be not doing the other flashing file now......well still gathering more info and will see.
P.S. Thanks for the info. @peramikic

DrakenFX said:
i created a Thread for users who have run into the No Boot issues and those problems , so i can gather more info of the causes of their problems but nobody had reply yet,
just waiting so i can test things and get back to Stock B20 with Root + TWRP and lock bootloader
Click to expand...
Click to collapse
Gottcha.... I was just curious, because I'm starting to have a few random issues (reboots, apps opening without tapping them, google voice commands not working like they did just a few days ago) I'd like to get back to stock and maybe start over. Of course, I didn't make a backup up until after I flashed SuperSU and my apps downloaded so I have no "stock" TWRP backup. **But, this all could be "theme" related too, since I'm running a dark theme that isn't quite compatible with the A7 yet.
I may try removing the theme and let it run a day or two and see how it does?

Stuck On bootanimation

No matter what custom firmware i flash it always is stuck on the boot animation, Ive left it booting for 5 hours today and it never reached the setup screen, just constant booting, I erase EVERYTHING everytime I go to twrp, except for my internal and external storage. Aswell as If i flash/restore my stock rooted and unrooted firmware, it does boot, but NO wifi or data works, even with the removal and reinsertion of the simcard. Please help. If i didnt explain it well enough i can reply and add more detail.

DeliriousHD said:
No matter what custom firmware i flash it always is stuck on the boot animation, Ive left it booting for 5 hours today and it never reached the setup screen, just constant booting, I erase EVERYTHING everytime I go to twrp, except for my internal and external storage. Aswell as If i flash/restore my stock rooted and unrooted firmware, it does boot, but NO wifi or data works, even with the removal and reinsertion of the simcard. Please help. If i didnt explain it well enough i can reply and add more detail.
Click to expand...
Click to collapse
You may have to follow this https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110 to get back to stock. There's a section about returning to stock without relocking the bootloader.

ccic2491 said:
You may have to follow this https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110 to get back to stock. There's a section about returning to stock without relocking the bootloader.
Click to expand...
Click to collapse
Ill try that. Ill report back if it works or fails.

ccic2491 said:
You may have to follow this https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110 to get back to stock. There's a section about returning to stock without relocking the bootloader.
Click to expand...
Click to collapse
It did not work, Keeps saying "Could not find 'meta-inf/com/google/android/update-binary' in zip file.

DeliriousHD said:
It did not work, Keeps saying "Could not find 'meta-inf/com/google/android/update-binary' in zip file.
Click to expand...
Click to collapse
One thing to try is formatting the internal storage to make sure you have a clean start. TWRP wipes /data without wiping userdata by default; to completely wipe the internal storage you have to go into the format data wipe where you must type "yes" to confirm instead of a slider. Sometimes leftover files can cause permissions problems and roms fail to boot. It is more common on other phones than this one, but I've seen some people report your problem before here too.
If you do this, obviously make sure you back up all the files you care about on internal storage to a microSD or off device. Also make sure you have rom/gapps to flash and a working TWRP backup stored on a microSD, or you've verified you can USB copy with MTP or adb push files from a computer to your phone before formatting. Don't find out after wiping and formatting that your computer is missing something it needs to copy files to your phone properly when your phone is booted into TWRP, test it first if you're going this route. Otherwise you could be stuck with a blank phone and nothing to flash on it.
I do this every once in a while just to keep internal storage from getting too cluttered from chronic flashing; just be careful about how you go about it.

Okay, I can try that.

jason2678 said:
One thing to try is formatting the internal storage to make sure you have a clean start. TWRP wipes /data without wiping userdata by default; to completely wipe the internal storage you have to go into the format data wipe where you must type "yes" to confirm instead of a slider. Sometimes leftover files can cause permissions problems and roms fail to boot. It is more common on other phones than this one, but I've seen some people report your problem before here too.
If you do this, obviously make sure you back up all the files you care about on internal storage to a microSD or off device. Also make sure you have rom/gapps to flash and a working TWRP backup stored on a microSD, or you've verified you can USB copy with MTP or adb push files from a computer to your phone before formatting. Don't find out after wiping and formatting that your computer is missing something it needs to copy files to your phone properly when your phone is booted into TWRP, test it first if you're going this route. Otherwise you could be stuck with a blank phone and nothing to flash on it.
I do this every once in a while just to keep internal storage from getting too cluttered from chronic flashing; just be careful about how you go about it.
Click to expand...
Click to collapse
I did this and its still stuck on boot. Im trying to flash AICP

DeliriousHD said:
I did this and its still stuck on boot. Im trying to flash AICP
Click to expand...
Click to collapse
It was worth a try. What bootloader and twrp version are you using?

jason2678 said:
It was worth a try. What bootloader and twrp version are you using?
Click to expand...
Click to collapse
regular bootloader for the xt1575 I havent chnged it, and twrp 3.0.2-0

DeliriousHD said:
regular bootloader for the xt1575 I havent chnged it, and twrp 3.0.2-0
Click to expand...
Click to collapse
TWRP 3.1 is out. I doubt that's your problem since you're flashing successfully and failing to boot, but updating recovery is something else to check off the list.
Are you on the L or M bootloader? It changed. Just looking for anything that might be causing the trouble.
Code:
getprop ro.bootloader
returns 0xA04C for me, and aicp is working good.

jason2678 said:
TWRP 3.1 is out. I doubt that's your problem since you're flashing successfully and failing to boot, but updating recovery is something else to check off the list.
Are you on the L or M bootloader? It changed. Just looking for anything that might be causing the trouble.
Code:
getprop to.bootloader
returns 0xA04C for me, and aicp is working good.
Click to expand...
Click to collapse
I think im on L but do i just put that in cmd when in bootloader? I also just updated twrp to 3.1 just now.
EDIT: I actually cant even do that in cmd.

DeliriousHD said:
I think im on L but do i just put that in cmd when in bootloader? I also just updated twrp to 3.1 just now.
Click to expand...
Click to collapse
Fastboot says what bootloader version you're on close to the little reclining robot, but I think it displays it a bit differently. A0.4C trailed by a date if I recall correctly.
You could enter that command in TWRP's built-in terminal. I think the terminal is under the Advanced menu. That should get you the same output.

jason2678 said:
Fastboot says what bootloader version you're on close to the little reclining robot, but I think it displays it a bit differently. A0.4C trailed by a date if I recall correctly.
You could enter that command in TWRP's built-in terminal. I think the terminal is under the Advanced menu. That should get you the same output.
Click to expand...
Click to collapse
I just tried putting that into terminal and it does nothing.

jason2678 said:
Fastboot says what bootloader version you're on close to the little reclining robot, but I think it displays it a bit differently. A0.4C trailed by a date if I recall correctly.
You could enter that command in TWRP's built-in terminal. I think the terminal is under the Advanced menu. That should get you the same output.
Click to expand...
Click to collapse
also BL: A0.1C (SHA-E29F91E, 2015-7-28 16;16;36)

DeliriousHD said:
I just tried putting that into terminal and it does nothing.
Click to expand...
Click to collapse
Well that's odd

jason2678 said:
Well that's odd
Click to expand...
Click to collapse
In your code you put to not ro XD

jason2678 said:
Well that's odd
Click to expand...
Click to collapse
Mine is 0xa01C

DeliriousHD said:
also BL: A0.1C (SHA-E29F91E, 2015-7-28 16;16;36)
Click to expand...
Click to collapse
2015-7-28 date is definitely from lollipop. I'd suggest heading over to the firmware thread and grabbing the newest marshmallow full firmware update (I think the sept patch is the newest out there), fastboot flash all of that, then try again.

jason2678 said:
2015-7-28 date is definitely from lollipop. I'd suggest heading over to the firmware thread and grabbing the newest marshmallow full firmware update (I think the sept patch is the newest out there), fastboot flash all of that, then try again.
Click to expand...
Click to collapse
Which thread? I can go looking but ive been to so many its confusing how to use the files.

jason2678 said:
2015-7-28 date is definitely from lollipop. I'd suggest heading over to the firmware thread and grabbing the newest marshmallow full firmware update (I think the sept patch is the newest out there), fastboot flash all of that, then try again.
Click to expand...
Click to collapse
This thread https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833 Shows a couple firmwares. but idk if i should get MPH24.49-18 , MPH24.49-18-3 or MPH24.49-18-4