Database Develop

[Q] Cannot install any custom roms. Phone acting weird

Hey guys. I've been using CyanogenMod on my Galaxy S for quite a long time. Few days ago my battery died and phone wouldn't pass the CyanogenMOD logo. I've decided to go back to stock rom and then upgrade to one of the new roms.
So I flashed the stock rom using Odin 3.07, rooted, went to recovery mode and tried to flash: Mackay ROM, Beast ROM ( black and white as well as beastxl), Avatar ROM, Slim Bean, Tsunami, CyanogenMOD but none of the above worked.
It starts the installation and after few seconds phone restarts itself and gets stuck on new boot logo.
The only thing that gets installed is the CWM which won't let me do the factory reset, wipe data, wipe dalvik cache etc. Keeps saying can't mount /data, /cache, /system.
The only time I can do factory reset is when I install stock rom.
I only succeeded installing Franzy ROM once but after reboot gets stuck on boot logo.
Sometimes even the stock ROM is giving me issues like process com.android.phone has stopped unexpectedly (does it for dialer, calculator, market, launcher)
Another weird thing is that even when I go back to stock rom and open up for instance a picture with bright background or web browser I can see transparent battery and CyanogemMod in the middle of the screen even tho phone's not charging and running on stock rom not CyanogenMod.
I think I've tried everything from fixing permissions, flash and re-partition using Odin and 512 pit file.
Even rang my Mom like advised in xda's video, didn't help either
Is there anything else I can try to get my phone in "shape"?
Any suggestions?

AllUsernamesAlreadyInUse said:
Hey guys. I've been using CyanogenMod on my Galaxy S for quite a long time. Few days ago my battery died and phone wouldn't pass the CyanogenMOD logo. I've decided to go back to stock rom and then upgrade to one of the new roms.
So I flashed the stock rom using Odin 3.07, rooted, went to recovery mode and tried to flash: Mackay ROM, Beast ROM ( black and white as well as beastxl), Avatar ROM, Slim Bean, Tsunami, CyanogenMOD but none of the above worked.
It starts the installation and after few seconds phone restarts itself and gets stuck on new boot logo.
The only thing that gets installed is the CWM which won't let me do the factory reset, wipe data, wipe dalvik cache etc. Keeps saying can't mount /data, /cache, /system.
The only time I can do factory reset is when I install stock rom.
I only succeeded installing Franzy ROM once but after reboot gets stuck on boot logo.
Sometimes even the stock ROM is giving me issues like process com.android.phone has stopped unexpectedly (does it for dialer, calculator, market, launcher)
Another weird thing is that even when I go back to stock rom and open up for instance a picture with bright background or web browser I can see transparent battery and CyanogemMod in the middle of the screen even tho phone's not charging and running on stock rom not CyanogenMod.
I think I've tried everything from fixing permissions, flash and re-partition using Odin and 512 pit file.
Even rang my Mom like advised in xda's video, didn't help either
Is there anything else I can try to get my phone in "shape"?
Any suggestions?
Click to expand...
Click to collapse
try to flash stock rom again via odin , root , then flash cm 9 ( to not loose you IMEI ) , then flash CM 10.1 stable from here : http://get.cm/?device=galaxysmtd&type=stable
then install any costum rom you want

The Tox said:
try to flash stock rom again via odin , root , then flash cm 9 ( to not loose you IMEI ) , then flash CM 10.1 stable
then install any costum rom you want
Click to expand...
Click to collapse
Thanks for your reply. Installing CM 9 worked but trying to install CM 10 throws up this error:
assert failed: run_program("tmp/updater.sh") == 0
E: Error in sdcard/cm-10.1.zip
(Status 7)
Installation aborted.

Flash this one :
http://get.cm/get/3Fb
then install this one :
http://get.cm/get/9aJ

Thanks for your help. CM 9.1.0 installs fine, same error for 10.1.2 :/

AllUsernamesAlreadyInUse said:
Thanks for your help. CM 9.1.0 installs fine, same error for 10.1.2 :/
Click to expand...
Click to collapse
did you tried to install other costum roms , like slimbean ?

There MIGHT be a problem with your internal SD card. Slight chance :/

did you tried to install other costum roms , like slimbean ?
Click to expand...
Click to collapse
Yes I did and only Franzys installed successfully but then stopped working after phone reboot.
There MIGHT be a problem with your internal SD card. Slight chance :/
Click to expand...
Click to collapse
I think that might be the case. I get encryption unsuccessful with my sdcard in and CWM doesn't see any files with sdcard out.
I found an article here on forum that explains how to use your external sdcard as the internal one. Will give it a try and see if it works.
For now I don't mind using CM 9.1.
Thanks for your help guys and let me know if you have any other suggestions.

Dialer not working on custom roms

short history, 5.1 from motorola everything was working, after having problems to get the OTA, flashed this rom to get the ota... after that, the phone went crazy, reboot after 10s with any custom rom when flashing stock/full gapps, then reboot when open whatsapp, and now when i try to make a call, the phone makes the call but i can't hear them and them can't hear me, i tried CM,NX,AOSP,RR with and without gapps and nothing is working... i need help if anyone can help me. i have two logs.

Yeah, the same happens to me when I flash a rom, and I never remember how I fix it every time, lol.
Try installing another dialer.apk and wiping cache and dalvik.

Problems with OctOS/TWRP... or maybe I'm the problem ;)

Update for the readers wh don't want to read the rest of the thread:
I solved 2 issues ("com.android.phone has stopped" was gone after wiping system, and the updating now works smoothly after i realized that the latest firmware is 4.0.3 and not 4.0.2)
The remaining problem is:
But i still get the welcome screen (like i wiped the data) everytime i reboot from twrp
It is not a ROM issue, because during the process i switched from OctOS to lineage and i still get the problem... what can that be???
quick info: TWRP is the most recent (3.0.3-1), firmware is the newest (4.0.3), Lineage is the nightly from Feb 14.
Original post:
Hello there fellow Oneplus users,
I've got some trouble with my 3T. I changed the OS to OctN some weeks ago. Everything was fine, i din't update the first 2 weeklys and when i wanted to update a few days ago (to OCT-N-WEEKLY-20170210-2251-oneplus3.zip) i tried but there was error 7... i don't remember exactly what i did then but when i booted i got the message "com.android.phone has stopped" and i couldn't get the message away (it appeared directly again after clicking ok) in the background the phone wanted to make a fresh setup. i tried a few things out, and the only thing that worked was wiping the cache, dalvik and data and then installing the rom, that was installed before (OCT-N-WEEKLY-20170121-0348-oneplus3.zip)
the next day i thought i could try it again (i hoped it was just coincidence), but make a backup via twrp before. but then same error... So i wanted to restore the backup. It went without errors in twrp, but the booting afterwards took about 15 minutes! After the boot: again the error message and in the background the "set up new phone" screen... even though i did a restore... so again wipe cache/dalvik/data via twrp and re install the old version of the OctOS
Next day after research: maybe i needed to update the firmware (4.0.2). downloaded it but i thought i would wait a little, because i don't have that much time to deal with those problem right now.
So today i decided to give it a try, rebooted to twrp, but then i thougt: "nah, i'll do it another day". So i really did NOTHING in TWRP -> reboot to system -> same old Error (com.android.phone has stopped) and data lost (new phone setup)
Ok: reboot to twrp, flashed the new firmware (no error) tried to flash the new OctOS -> error 7...
I also have the latest LineageOS rom (lineage-14.1-20170214-nightly-oneplus3-signed.zip) on the phone to try out: wiped Cache/Dalvik/Data install Lineage: same error 7...
same with the old OctOS: everything's fine...
Longstory short: what ever i do in twrp doesn't work expect a wiping and reinstalling the same OctOS that worked the last 3 or 4 weeks...
What am i missing? Or is there really something wrong with my phone?

Try to flash the new TWRP, firmware.

and flash the rom with full wipe

svandasek said:
Try to flash the new TWRP, firmware.
Click to expand...
Click to collapse
TWRP is the newest, and (as already mentioned in the text) firmware was renewed during the process without any success.
What do you mean by full wipe? More than Cache, Dalvik and Data?
But still, i have the feeling, that this error is something not very common... I think i might return to complete stock, if the problems continue.

So,
i solved 2 issues ("com.android.phone has stopped" was gone after wiping system, and the updating now works smoothly after i realized that the latest firmware is 4.0.3 and not 4.0.2)
But is Still get the Welcome Screen (like i wiped the data) everytime i reboot from twrp
It is not a ROM issue, because during the provess i switched from OctOS to lineage and i still get the problem... what can that be???

Nobody got any idea?

felixburk said:
Nobody got any idea?
Click to expand...
Click to collapse
It's a TWRP and f2fs problem. You either need to change your data partition to EXT4 and/or update your TWRP to 3.0.4-1
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391

GrandMasterB said:
It's a TWRP and f2fs problem. You either need to change your data partition to EXT4 and/or update your TWRP to 3.0.4-1
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
Click to expand...
Click to collapse
Thanks I'll try that out.
Might it help, if i don't set a password for the phone? Or is it not encryption related?

felixburk said:
Thanks I'll try that out.
Might it help, if i don't set a password for the phone? Or is it not encryption related?
Click to expand...
Click to collapse
It's filesystem driver related and nothing to do with the encryption.

[Solved] Rom setup blocked, Tab S2, T813 blocked!

Hi dear developers,
I just got my new Galaxy Tab S2, T813. Updated it to Nougat, firmware T813XXU2BQD1_T813OXA2BQD1_DBT. I rooted it via Chainfire's autoroot and worked perfectly fine. I installed the latest TWRP (twrp-3.1.1-1-gts210vewifi), advance wiped in twrp (like tens of times before with Galaxy S5, Galaxy S7, Redmi 4, ZUK Z2, Xiaomi Mi 5s, LG G2 etc.). I flashed Lineage 14.1 (Lineage-14.1-20170516-nightly-gts210vewifi) but when I rebooted the phone Lineage setup would not start. I went back and advance wiped again and installed an older Lineage version but again the same. I advance wiped again and installed Omni (Omni-7.1.2-20170521-gts210vewifi-weekly), but here again setup would not start. I reformatted the data in twrp and reinstalled Lineage 14.1 but again the same. So I went back and flashed via Odin3_v3.12.3 the stock firmware (for Germany) T813XXU2BQD1_T813OXA2BQD1_DBT. Odin command was pass and i though everything was fine. When the original firmware rebooted i have the same problem, the setup would not start and starting apps would crash. I entered recovery (of course stock recovery because twrp has been wiped by odin), but it says "no command".
Smart Switch would not support my device although it actually should.
I tried to flash via odin also on my second PC but again the same problem. Both PCs are running Windows 10.
I never faced something like this before. And after hours of search I found nothing. Please help me solve my problem so that i can install at least one firmware (no matter which one: Stock, Lineage, Omni etc.).

When you flashed lineageOS or omni rom, did you also flash gapps?

musashiken said:
When you flashed lineageOS or omni rom, did you also flash gapps?
Click to expand...
Click to collapse
First time flash:
+ clean advanced wipe
+ lineage
+ gapps (ARM64, Android 7.1, Pico)
+ addonSU
other times flash:
+ clean advanced wipe
+ lineage
or
+ clean advanced wipe
+ omni
I believe either flashing Chainfire Autoroot file or flashing TWRP might have caused the problem and might have deleted something or maybe i deleted something during first time wipe via twrp.
Is there a patch or aboot or something to flash via Odin prior to flashing the stock firmware to correct the problem with stock rom setup blockade?

Ok, I'm not sure what went wrong with how you did stuff but let's not use Chainfire's autoroot again. The best way to root is to do it manually.
Anyway, firstly you should be able to go back to stock samsung firmware by using Odin and flashing the full tar file. I'm not sure why that is not working for you as that's the only way to reset and fix your tablet.
Please check how to flash the full firmware via Odin again.
- ensure you downloaded the correct nougat firmware file. Latest LineageOS should require the EU version of the nougat firmware. I think it is T813XXU2BQD3. Not the firmware you used.
Once you are able to load a fresh samsung firmware, then come back again. I'll see if I can guide you through the TWRP and rooting process again.

musashiken said:
ensure you downloaded the correct nougat firmware file. Latest LineageOS should require the EU version of the nougat firmware. I think it is T813XXU2BQD3. Not the firmware you used.
Click to expand...
Click to collapse
Thanks fo the tip with the new version of firmware. I installed the firmware ...QD3 via Odin...

Closed per OP request

Custom ROMs Bootloop

hey guys so i couldnt think of a title which accurately describe my problem so there it is
For the past 2 months i have been on AOKP Nougat for my sm-g800f (UK) (EE) and it has been running perfectly fine except the odd random restarts but nothing more. Just 2 days ago it started freezing a lot, unresponsive screen, restarting more often keep in mind i did not install anything new or tweak anything. So i decided to do a fresh install and also try a new rom.
I have tried 3 custom roms:
1. First i tried beanstalk the nougat version and i managed to install it but 30 minutes into use i got constant reboots:crying:
2. Resurrection Remix was next this rom took many many tries to install as the phone kept constantly rebooting through the setup process and i ran into other problems such as 'setting has stopped' and 'setup wizard has stopped'. finally after many attempts and with perseverance which manifested from i dont know where i installed it:victory: along with Gapps but just like beanstalk after 30min the same problem, constant reboots
3. the third is what i just tried aokp nougat which is right now constantly rebooting not even allowing me to set it up.
(btw between each install i did factory resets and data wipes and even wiped internal and external storage)
i have twrp 3.1.1.0-0 installed which works perfectly fine but the latest version caused problems whcih is why i am not using it.
the kernel is default.
There was one fix.... after the millionth factory reset before installing kernel 3 but after trying kernel 2 i odin flashed a clean stock 6.0.1 which worked perfectly, no restarts or freezing or anything.
However i do not want that so i flashed twrp and installed AOKP along with Gapps and here i am in a bootloop.
(note i can still access recovery even now)
my preffered setup rn is resurrection remix nougat with spookcity 1.5ghz kernel if that can be done idk
thank you and i hope u can help me
edit: atm when im in twrp on my pc the phone is shown as SM-G800 (no f )

Hi, had the same problem for months.
Succeeded yesterday for G800F with :
- complete wipe except MicroSD
- Lineage OS 14.1 August build
- AddonSu from LOS extra
- OpenGApps Nano ARM 7.1
- Spookcity Kernel 1,5 GHz.
Keep in touch.
I'll update my tutorial once I'm back home.