Hi guys. I decided to update to XtreStoLite DeoMod Edition 3.0 MM RC1 last night from the latest Lollipop version of the same ROM, I first flashed the new bootloader and modem, along with TWRP 3.0.0 and the arter97 kernel, all through Odin.
Upon reboot, my phone would just keep trying to load TWRP and then turning off, before continuously looping.
Not to be disheartened, I downloaded a stock 6.0.1 rom, specifically G920FXXU3DPBG_G920FBTU3DPB1_BTU_FULL. I used Odin to flash only the AP section from this firmware. I know the bootloader and modem differ from the firmware XtreStoLite uses, but my intention was just to allow the recovery to boot. Once this was done I reinstalled TWRP as it was of course replaced during flashing the firmware.
This bit worked and I was finally able to enter TWRP and flash the custom ROM, after doing a full wipe/factory reset via the options presented.
I thought all had gone well but I've just noticed that my storage now states that the internal memory is 16GB, but this is a 64GB model.
Any advice on how I can fix this please? Much appreciated.
SOLVED
Couldn't find anything on this through numerous searches so I went poking through the TWRP options. Under Wipe - > Advanced Wipe I was able to select the Data partition, hit Repair or Change File System and then Resize File System, this got my full 64GB back. My partitions seem to have been changed to ext4 from f2fs somewhere along the way but I know how to sort that out
Del
Related
Hi,
I was trying to flash the stock ROM on my N915G ROM earlier today however it was the wrong one. It turns out it was for the Singapore version of the N915G (5.1.1) not the Taiwan version which is the one i wanted (5.0.1 is the latest version for the Taiwan version).
Odin shown the failed message when i tried to flash it (which nearly gave me a heart attack).
I installed the CWM recovery and tried to restore my backup that i taken however i just get the Samsung logo boot loop.
I then wiped cache and dalvic cache and reset the ROM. I managed to get as far as the "android is optimizing apps" box but i just get a boot loop when its finished optimizing the 23 applications.
I am thinking i should probably just try and flash the stock ROM with odin but i really dont know what to do!
Any help would be much appreciated !
Alex
EDIT: Flashed the stock ROM and seems to be working now. Can close thread.
Hi all. I'm a bit of a noob who just really started digging into custom roms and rooting this month. A friend helped me root Lollipop when I first got this phone and I've been putting off updating to marshmallow for 6 months, but learned how over the past weekend and I'm loving it! Small problem, though, and I don't know if it's even a real one, but here it is. After all is said and done flashing the XstreStoLite 3.3.1 rom and Aroma add on pack, everything works fine, but the arter97 kernel is no longer listed as the active kernel, even though in XstreStoLite's settings when presented with the overwrite kernel option I always selected No. Is there a reason this is happening? Can I just reflash the kernel now, and is it safe to do so without brick in the phone? Does this rom or any other necessary apps/root features require the custom kernel? Thanks! This was my process in getting my phone up and running:
Factory reset
Flash stock 6.0.1 with Odin
Flash arter97 recovery with Odin
Recovery mode to flash arter97 kernel and superSU
Flash XstreStoLite in recovery, factory reset
Flash aroma addon
Additional random question I had: at what point, if any, should I be flashing the custom bootloader and modem, and does a factory reset/cache wipe delete those or is it one and done? Thank you!
The bootloader and modem flashing is needed if you want to move from 5.x lollipop to 6.x marshmallow.
If you are allready on 6.x there is no need.
If you lost your custom kernel you can reflash it in twrp and after wipe cache/dalvik cache.
If you flash the corect version of kernel the is no problem of softbrick.
Flash a 6.x kernel on a 6.x rom
Hi guys,
Not sure if anyone else has had this issue, but I've only got a Moto G 4G fairly recently (my Nexus 5 died) and have been attempting ROM flashing (never had an issue with multiple Nexus phones & tablets) I was flashing the rom OK but the sim card wasn't recognised - so went back to rooted stock Kitkat & Xposed.
Today I thought I'd give it another go, got into TWRP, advanced wipe as usual...but it didn't complete and the phone suddenly booted back into the system (with the Android upgrading/optimizing message you usually get when starting a new phone)
System is untouched, still rooted/xposed etc. Does anyone have an idea why this has suddenly happened? Never encountered anything like this before. TWRP is the latest version 3.1.1.0
Any suggestions welcome, cheers.
Just thinking....would flashing with adb be a solution?
Just flash lollipop stock ROM using mfastboot
later you can flash twrp recovery and then proceed with the nougat or oreo based ROM.. Bootloader should be updated so my suggestion is flash lollipop stock ROM
Hey there.
So, my 6045 was on that awful MM update filled with ads, so I changed the firmware to the Panasonic one in order to be able to install TWRP and next flash either Lineage or RR.
I have no problem installing TWRP using the Idol 3 suite (Here), however, whenever I try to flash the Lineage zip, or the RR zip, it gets stuck on the Powered by Android screen.
I always wipe everything before flashing the zips.
I have tried wiping cache/dalvik after flashing them, and also not wiping. Either way, and with both roms, the phone gets stuck, and I need to use the Panasonic tool again to restore the phone to a functioning state.
Please help, I've been repeating this process about 10 times, and it's getting very frustrating.
Thanks.
EDIT: Is the version of TWRP somehow relevant for this? The latest version I can install is 3.0, from the link provided. If I try to install this one I get a bootloop. Please help.
Hi, u need to flash the MM partitons zip first then the rom . Look on AlekDev customs roms threads, he usualy has the MM partition file.
Hey there,
I found a J7 2015 (the Exynos variant) sitting in my dad's drawer. I decided to come here after a full day of trying to get Centaurus OS (from here) up and running but in vain. The reason why I am here and not on its official thread is that the official thread is closed.
After powering on the device and seeing the Samsung Logo, it is just a black screen from that point onwards. I am able to go into download mode or recovery and restore another OS, which is good, but Centaurus OS seemed fairly stable based on the feedback on the thread. I am able to get other ROMs running, including ones that are based on Android 7.1+.
Here is a summary of my attempts. I will try to not keep it long.
Method 1: Starting from Android 5.1.1 stock
Flashed TWRP 3.0.2
Factory Reset + Delete Data
Flash ROM and go through setup
Stuck on that black screen after restart
Method 2: Flashed Android 6.0.1 stock from SamFirmware.
Tried with either TWRP 3.0.2 or 3.3.1
Factory Reset
Flashed a ROM with Android 7.1
Factory Reset again
Flashed Centarius ROM
Stuck again on Boot
I have done variants of those methods multiple multiple times but nothing really worked out. I am certain I am using flashable files that are 100% designed for my phone model.
So here's what I am asking for:
Could anyone help me fix the issue? OR...
May I know of another fairly stable ROM for the J7 2015 that is based on Android 7 or higher?
Thanks a ton for passing by
Oops, this was too ridiculous on my side. It actually worked finally. Here's my setup and what I have done:
Setup:
TWRP 3.3.1 tar file Flashed via Odin
Boot into Recovery
Go to Wipe > Advanced Wipe
Check Data, Cache, SYSTEM, etc, but not External MicroSD Card and USB OTG
Back to TWRP main screen, Reboot > Recovery, ignore warning
Flash the Centarius ROM from the external MicroSD Card
Should work after reboot
After trying quite a bunch of ROMs, there's actually nothing that matches the stock ROM for our J7. Other ROMs, whether LineageOS based or based on some other ROM from another phone, are half done with minor, but annoying issues.
This is the stock ROM I used. He got a more recent version of Android Security Patches, but still quite old now. Use that one, or if you are security-paranoid, then consider switching to another phone.
https://forum.xda-developers.com/ga...-stock-custom-rom-debloated-deodexed-t3339816