Database Develop

[Q] always get bootloop after formate in custom rom and custom recovery

hello frnds
i have vry strange issue with my ace.
custom roms work perfect on my phone but whenever i formate my phone from phone settings or wips from cwm i always get bootloop.
so i have to flash again rom every time.
stock rom + stock recovry formating works well.
but why in custom roms i get bootloop after formate.

arshad522 said:
hello frnds
i have vry strange issue with my ace.
custom roms work perfect on my phone but whenever i formate my phone from phone settings or wips from cwm i always get bootloop.
so i have to flash again rom every time.
stock rom + stock recovry formating works well.
but why in custom roms i get bootloop after formate.
Click to expand...
Click to collapse
That it's normal, there're custom roms that come pre-configured (necessary for booting)... when you do the wipes you break that initial configuration (necessary for booting) and that's end in bootloop

Viper The Ripper said:
That it's normal, there're custom roms that come pre-configured (necessary for booting)... when you do the wipes you break that initial configuration (necessary for booting) and that's end in bootloop
Click to expand...
Click to collapse
does this loop happen to every ace user after wipes.
why intial configure break in just wipes.
i have to reflash the rom or restrore nandroid all the time after wipes.
is there any other permanent solution for this.

arshad522 said:
does this loop happen to every ace user after wipes.
why intial configure break in just wipes.
i have to reflash the rom or restrore nandroid all the time after wipes.
is there any other permanent solution for this.
Click to expand...
Click to collapse
Yes... about this, could @Mardon inform you in a better way
Our ace hasn't much internal memory, neither official Samsung 4.x versions, also when you do a "wipe", you format partitions as; /system, /data... they contain important information for the boot, these information isn't permanent and is deleted after that so, then our Ace can't boot

Viper The Ripper said:
Yes... about this, could @Mardon inform you in a better way
Our ace hasn't much internal memory, neither official Samsung 4.x versions, also when you do a "wipe", you format partitions as; /system, /data... they contain important information for the boot, these information isn't permanent and is deleted after that so, then our Ace can't boot
Click to expand...
Click to collapse
when i do wipes, it just erase user data and cache. then how it erase any thing( any partition) that is neccrsry for boot.
i could not find any solution on google.

could not find any solution
no one is replying :crying:

arshad522 said:
could not find any solution
no one is replying :crying:
Click to expand...
Click to collapse
I completely agree with what @Viper The Ripper said. Most custom roms comes with preconfigured boot settings some of which are installed in the data part too. These preconfigured boot files are usually installed during your first boot which is why the first boot of any custom rom takes some time. So as long as you do a Wipe Cache Partition, you will have no problems. But if you do a Wipe Data/ Factory Reset or Wipe Dalvik Cache, then it will delete the preconfigured boot setting files. So next time when you restart, your phone cannot complete the booting because of the missing files and hence your phone gets in a bootloop. You can still solve this by reinstalling the same rom again from the recoverymod so that it can again reinstall the preconfigued boot setting or restore a nandroid backup to restore the boot settings. Hope I helped

mahithm said:
I completely agree with what @Viper The Ripper said. Most custom roms comes with preconfigured boot settings some of which are installed in the data part too. These preconfigured boot files are usually installed during your first boot which is why the first boot of any custom rom takes some time. So as long as you do a Wipe Cache Partition, you will have no problems. But if you do a Wipe Data/ Factory Reset or Wipe Dalvik Cache, then it will delete the preconfigured boot setting files. So next time when you restart, your phone cannot complete the booting because of the missing files and hence your phone gets in a bootloop. You can still solve this by reinstalling the same rom again from the recoverymod so that it can again reinstall the preconfigued boot setting or restore a nandroid backup to restore the boot settings. Hope I helped
Click to expand...
Click to collapse
i completly agree with you both.
this is realy frustating that we cant factory data reset in custom roms.
i was looking some alternative but the only solution is reflash or restore nandroid.
anyway thnks for reply

arshad522 said:
i completly agree with you both.
this is realy frustating that we cant factory data reset in custom roms.
i was looking some alternative but the only solution is reflash or restore nandroid.
anyway thnks for reply
Click to expand...
Click to collapse
No problem buddy

[PLEASE HELP] Xperia Z 4.4.2 goes to bootloop after restart & power off

Hi all,
that's my first post, sorry about my bad english
I have problem with my Xperia Z. I flashed android 4.4.2 by Rajeev from this thread http://forum.xda-developers.com/xperia-z/development/rom-rooted-deodexed-zipaligned-stock-0-t2759467 . I folowed instruction but i had problem with flashing ROM with mounted /system (no matter TWRP or CWM) (I haven't FULL root on my 4.3 ROM, just half rooted)...i solved that this way: went to CWM and fixed permissions in advanced menu, then went to CWM and wiped /data, /cahce, /dalvik AND /SYSTEM, then flash ROM and SuperSu fix. After that I rebooted to system. Everything's fine but when i turned off phone or reboot to system or recovery it goes to bootloop, tried reset by pressing vol up+power - still bootloop.
My specyfication:
Xperia Z C6603,
Android 4.3 [10.4.B.0.569] - half rooted with SuperSu (but apps with root permissions works fine),
PhilZ Touch CWM & TWRP v2.7.62-BETA (newer version didn't work-not boot to recovery)
I tried a few times,lost many hours but still don't works...please help me because this ROM is awesome

Nobody helps me?

merque said:
Nobody helps me?
Click to expand...
Click to collapse
Bro do this
boot to recovery
Format system
format cache
format dalvik cache
format data(not internal sd)
Install rajeevs rom
flash kernel
flash SU
your problem will be solved :highfive:

androidtweaker1 said:
Bro do this
boot to recovery
Format system
format cache
format dalvik cache
format data(not internal sd)
Install rajeevs rom
flash kernel
flash SU
your problem will be solved :highfive:
Click to expand...
Click to collapse
Thx Bro, that was very helpful, now everything's fine

merque said:
Thx Bro, that was very helpful, now everything's fine
Click to expand...
Click to collapse
:good::highfive:

[Q] [HELP] Revocery It presents problems with GAPPS (MM)

Hi guys!!
They could help me knoww that RECOVERY is right for Marshmallow ; I tried with different ROMS and the problem arises when installing Gapps because after installing the Gapps, not start, the warning "unfortunately has stopped setup wizard " appears , or ocacionan "bootloops" .
I researched and apparently is the RECOVERY , could you please help me?.
ROMS Tested :
CM13
Xperience
BeanStealk
Gapps Tested :
OpenGAPPS
( open_gapps-arm-6.0-nano-20160124.zip , open_gapps-arm-6.0-pico-20160124.zip )
BANK_GAPPS
Dynamic BANK_GAPPS
Tested RECOVERY :
philz touch
TWRP
XT1064
PLEASE HELP!
I'm desperate

Using TWRP
clean flash cm 13 ( wipe everything except internal storage and ext SD) and flash zip and gapps , wipe dalvik and cache and reboot .
Its got to work since there is no problem at all with any ROM or gapps.
If that doesn't work restore to stock and start the process again (root and stuff)

sagar846 said:
Using TWRP
clean flash cm 13 ( wipe everything except internal storage and ext SD) and flash zip and gapps , wipe dalvik and cache and reboot .
Its got to work since there is no problem at all with any ROM or gapps.
If that doesn't work restore to stock and start the process again (root and stuff)
Click to expand...
Click to collapse
Thank you !
Let me try and comment .

Solved
sagar846 said:
Using TWRP
clean flash cm 13 ( wipe everything except internal storage and ext SD) and flash zip and gapps , wipe dalvik and cache and reboot .
Its got to work since there is no problem at all with any ROM or gapps.
If that doesn't work restore to stock and start the process again (root and stuff)
Click to expand...
Click to collapse
Thank you
I commented that worked perfectly . :good: :laugh: :laugh:

Most stable ROM for Galaxy S5 mini

Hi
I'm searching for a custom ROM for my mom's gamaxy s5 mini. Touchwize is very buggy on her devices, so i'm looking for a stable ROM.
I'm not specific looking for a ROM that has a lot of features but they are always welcome.
What ROM do you guys suggest?
Thanks

stock rom with custom kernel

Dev!n said:
stock rom with custom kernel
Click to expand...
Click to collapse
+1
Custom roms for the S5 Mini are still on BETA stage. They have some bugs, an higher battery drain and some features are unsopported. Stock rom with a custom kernel and ROOT os the best way. Also, don't forget to format the Data and Cache partitions into the F2FS filesystem.

Andrea224 said:
+1
Custom roms for the S5 Mini are still on BETA stage. They have some bugs, an higher battery drain and some features are unsopported. Stock rom with a custom kernel and ROOT os the best way. Also, don't forget to format the Data and Cache partitions into the F2FS filesystem.
Click to expand...
Click to collapse
What kernel do you suggest?
And how do I format data and cache partition into F2FS filesystem? And before I do that, in what filesystem are they formated originally?

titan1655 said:
What kernel do you suggest?
And how do I format data and cache partition into F2FS filesystem? And before I do that, in what filesystem are they formated originally?
Click to expand...
Click to collapse
I suggest this kernel: http://forum.xda-developers.com/galaxy-s5-mini/orig-development/kernel-custom-kernel-t3130662
You can format the two partitions into the TWRP 3.0.0 recovery. Normally, on every phone, they are formatted into the ext4 filesystem (you can also read it before formatting)

Andrea224 said:
I suggest this kernel: http://forum.xda-developers.com/galaxy-s5-mini/orig-development/kernel-custom-kernel-t3130662
You can format the two partitions into the TWRP 3.0.0 recovery. Normally, on every phone, they are formatted into the ext4 filesystem (you can also read it before formatting)
Click to expand...
Click to collapse
Last question.
Why only format the Data and Cache partitions into the F2FS filesystem? And not the other partitions?

titan1655 said:
Last question.
Why only format the Data and Cache partitions into the F2FS filesystem? And not the other partitions?
Click to expand...
Click to collapse
Because only these two partitions have this possibility.

What custom kernel would you recommend for G800H? And what is the advantage of formatting the partitions into F2FS?

morcio said:
And what is the advantage of formatting the partitions into F2FS?
Click to expand...
Click to collapse
https://en.wikipedia.org/wiki/F2FS should tell you why you want this (It's a FS designed especially for mobile devices that use flash memory for storage).

Sm-g800h or sm-g800f???

Info: model SM-G800F, baseband G800FXXU1BPC4
I had the same question as TS and listened to the advice of @Andrea224 by flashing the custom kernel mentioned in this thread.
I started with the stock 5.1.1 ROM.
- First I flashed the kernel using Odin3.
- Then I flashed TWRP 3.0.0 recovery using Odin3.
- Then I re-formatted \data and \cache F2FS booting in TWRP.
All went well.
When I boot in Recovery I got the question to mount read/write and the warning about not able to receive OTA updates.
When I exit Recovery I get the question to install SuperSU.
Coming from a long line of HTC devices the above questions are new to me.
What do they mean? I once did choose to install SuperSU. Is my phone rooted now? Or should I still flash the CF-Auto-Root-kminilte-kminiltexx-smg800f.tar.md5 file?
Also in TW I get the questions about not having an original software installed. Is this about Knox? How can I disable this?
Concluded: Have I done all the correct steps to have a stable system?

bakmanhans said:
Info: model SM-G800F, baseband G800FXXU1BPC4
I had the same question as TS and listened to the advice of @Andrea224 by flashing the custom kernel mentioned in this thread.
I started with the stock 5.1.1 ROM.
- First I flashed the kernel using Odin3.
- Then I flashed TWRP 3.0.0 recovery using Odin3.
- Then I re-formatted \data and \cache F2FS booting in TWRP.
All went well.
When I boot in Recovery I got the question to mount read/write and the warning about not able to receive OTA updates.
When I exit Recovery I get the question to install SuperSU.
Coming from a long line of HTC devices the above questions are new to me.
What do they mean? I once did choose to install SuperSU. Is my phone rooted now? Or should I still flash the CF-Auto-Root-kminilte-kminiltexx-smg800f.tar.md5 file?
Also in TW I get the questions about not having an original software installed. Is this about Knox? How can I disable this?
Concluded: Have I done all the correct steps to have a stable system?
Click to expand...
Click to collapse
Now, I will explain to you how to get it work properly:
- Boot your phone in download mode and flash the latest update of the TouchWiz for your country with Odin. (If you are on CM13, into TWRP: 1- Do a backup of your data; 2- In Wipe -> Advanced Wipe select Dalvik, Cache, System, Data and wipe these partitions; then select Cache and Data and format both to ext4; 3- After all, flash TWwith Odin)
- Boot your phone in download mode and flash SuperSU with CF-Auto-root.
- Boot your phone in download mode and flash the TWRP 3.0.0 with Odin.
- When you are into recovery: 1- Tick the option for never show this message on every reboot into recovery and then swipe to allow modification; 2- Do a backup of your Data; 3- Flash the custom kernel; 4- Format Data and Cache to F2FS; 5- Restore the backup of your Data; 6- Reboot the phone and DO NOT allow to install SuperSU if it ask to you. (If after the reboot, the phone says that your device isn't rooted, flash another time CF-Auto-root)
- With the kernel and root installed, now is time to delete some apps: 1- Download and install RootExplorer; 2- Go into "system" -> search SecurityLogAgent.apk into the folder called "app" or "priv-app" (I don't remember in which folder is it) and delete it. Naturally, you have to grant root access to the app.
Now you have a good and stable rom. Also, if you want to debloat the stock rom, you can use this ZIP -> http://forum.xda-developers.com/galaxy-s5/development/mod-urwsoft-barebone-cleaner-t3043479 (this is for the S5, but it's compatible with the S5 Mini) or you can delete manually some apps through RootExplorer. If you have some problems, contacts me.

With Root Explorer you mean the payed version?
Verstuurd vanaf mijn SM-G800F met Tapatalk

bakmanhans said:
With Root Explorer you mean the payed version?
Verstuurd vanaf mijn SM-G800F met Tapatalk
Click to expand...
Click to collapse
Yes, just search on Google the apk.

Did all the steps above except for the URWsoft BareBone Cleaner. I had to reflash both Autoroot and TWRP through Odin twice. Weird. By removing SecurityLogAgent.apk I was finally able to enjoy my device without being warned all the time. Nice!
I have noticed that after every reboot my Wifi connection settings are lost. Anybody else experienced this?

bakmanhans said:
Did all the steps above except for the URWsoft BareBone Cleaner. I had to reflash both Autoroot and TWRP through Odin twice. Weird. By removing SecurityLogAgent.apk I was finally able to enjoy my device without being warned all the time. Nice!
I have noticed that after every reboot my Wifi connection settings are lost. Anybody else experienced this?
Click to expand...
Click to collapse
It's a bug, it appears when you flash a custom kernel. To fix it, go here -> http://forum.xda-developers.com/showpost.php?p=65568464&postcount=10

I'm sorry for restoring such an old thread but my question is the same.
Which is the best rom for G800F?
Custom roms I see that have still many known bugs
Stock rom ok, but how about debloating it? I haven't found a debloated version, nor a guide/script to debloat it automatically.
And what about the kernel? Which is the best kernel for stock rom? And for custom roms?
Thank you

Alefello said:
Stock rom ok, but how about debloating it? I haven't found a debloated version, nor a guide/script to debloat it automatically.
Click to expand...
Click to collapse
I use Root Package Disabler from play store, it has in-built bloatware list that you can disable/freeze.
Very convenient and effective.

How about Resurrection Remix MM? It's marked as stable and it seems that everything is working in the changelog and comments.
Or LOS 13 too seems everything is working (but I can't find confirmation in comments)

I'm using this one
https://forum.xda-developers.com/galaxy-s5-mini/development/rom-resurrection-remix-n-5-8-2-t3562523
It's 7.1.2 RR. It's perfection. I'm not even kidding I've used it for 3 months and it's stable as hell. On top of that it has million features that come with RR roms. Battery life is really good too.

Question My Redmi Note 10 pro not showing System and Vendor

Hi guys i am facing a liitle bit of a problem i unlocked my bootloader and flash some custom roms but after flashing lineage os the battery went down hill and tried to flash other roms to fix the problem also flashed the stock rom no luck.So i was trying to make a clean flash as last possible fix but the system and vendor options in advance wipe are not showing i mounted them but nothing show in advance wipe.I tried to flash different Twrp version old and new and still no luck also tried to flash Orangefox Recovery when i go to mount options and tried to ticked system and vendor it didnt ticked.I remember first time flashing Twrp after i reboot in recovery there was option (read only i guess) and i ignore it and it seems that's it become write only. (i tried to reflash the orangefox recovery and then the twrp to reset it but still no option for read only to untick it).Any idea to fix that issue?!Thanks.

Newbie2022 said:
Hi guys i am facing a liitle bit of a problem i unlocked my bootloader and flash some custom roms but after flashing lineage os the battery went down hill and tried to flash other roms to fix the problem also flashed the stock rom no luck.So i was trying to make a clean flash as last possible fix but the system and vendor options in advance wipe are not showing i mounted them but nothing show in advance wipe.I tried to flash different Twrp version old and new and still no luck also tried to flash Orangefox Recovery when i go to mount options and tried to ticked system and vendor it didnt ticked.I remember first time flashing Twrp after i reboot in recovery there was option (read only i guess) and i ignore it and it seems that's it become write only. (i tried to reflash the orangefox recovery and then the twrp to reset it but still no option for read only to untick it).Any idea to fix that issue?!Thanks.
Click to expand...
Click to collapse
Don't try to format or delete other partitions as data dalvik and cache! Risk of brick! And not necessary!
Only follow exactly step by step the ROM installation instructions
E.g.
👍 [SHARED][ROM] [ANDROID 13] [OSS] PULKITS lineage os 20 19.02.23/ checked by myself
Update on page 14 Update latest los 20 on page 7 I'm on pulkits android 13 for testing. Quiet good! Soon you'll get a beta! Thanks a lot to @Pulkit Agarwal Please donate him, thanks Update see post Post in thread '👍 [SHARED][ROM] [ANDROID...
forum.xda-developers.com

Newbie2022 said:
.... i was trying to make a clean flash as last possible fix but the system and vendor options in advance wipe are not showing i mounted them but nothing show in advance wipe......
Click to expand...
Click to collapse
I'm always surprised if someone want to do these kind of actions to resolve such relative simple problems. While imho nowhere such actions are described by flashing instructions.
"Simple" because the rom itself does work without issues, so the real reason for battery drain must be found, (wakelocks, sensors, updateproblems, running services etc.) which could be very time consuming,
By starting without Gapps to see what happens with battery, you find if the reason is rom or Google.
Other reasons could be VOlte, pocket detection, proximitysensor, hanging updates.
Flashing a new rom does replace the system and vendor partition, so everything what was on it is gone.
The data partitition needs to be formatted, because it is locked by encryption of the old rom.
Startup the new flashed rom after format data partition, does encrypt the new data again.

Laptapper said:
Don't try to format or delete other partitions as data dalvik and cache! Risk of brick! And not necessary!
Only follow exactly step by step the ROM installation instructions
E.g.
👍 [SHARED][ROM] [ANDROID 13] [OSS] PULKITS lineage os 20 19.02.23/ checked by myself
Update on page 14 Update latest los 20 on page 7 I'm on pulkits android 13 for testing. Quiet good! Soon you'll get a beta! Thanks a lot to @Pulkit Agarwal Please donate him, thanks Update see post Post in thread '👍 [SHARED][ROM] [ANDROID...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks man yes i know the risk but it seems to be the only option i have i tried to dirty flash Roms following instructions, but the battery drain issue persist so i was trying as last resort to clean flash and then stock rom in a hope to resolve the issue. Thank you very much really appreciated

Elinx said:
I'm always surprised if someone want to do these kind of actions to resolve such relative simple problems. While imho nowhere such actions are described by flashing instructions.
"Simple" because the rom itself does work without issues, so the real reason for battery drain must be found, (wakelocks, sensors, updateproblems, running services etc.) which could be very time consuming.
Flashing a new rom does replace the system and vendor partition, so everything what was on it is gone.
The data partitition needs to be formatted, because it is locked by encryption of the old rom.
Startup the new flashed rom after format data partition, does encrypt the new data again.
Click to expand...
Click to collapse
Yeah the issue was after flashing the rom something happened i don't know exactly what it is but the screen battery consumption hit the roof altouth i capped the refresh rate at 60 and use dark mode and brightness to 35 max . Before flashing the rom(lineage) i didnt had this issue with older other roms i flashed before the issue (pixel experience and pixel os)...I dirty flash other roms and even stock rom through Miflash tool but the same issue continued so i was hoping if i can clean flash the stock rom. Thanks alot man.

Newbie2022 said:
... i tried to dirty flash Roms following instructions, but the battery drain issue persist ....
Click to expand...
Click to collapse
"Dirty flash" means system and vendor partition will be replaced with the same files as before, but the data stays untouched. So this will have no impact on solving your problems.
"Clean flash" means the data is gone too for a new rom encryption.
With enabled encryption it is only possible to flash a new rom or stock rom by clean flash.
FYI: I solved huge battery drain what was caused by Pixel spoofing on a non Pixel.
Before I found this I was weeks further.
Only if everyone with the same rom has such drain too, there is something wrong with a rom.
If this is the case i can assure you this will be picked up by the developer of that rom.
If you have the same issue with different roms it could be directed to the hardware of the phone.
With RN10P the proximity sensor has known issues with some devices.

Elinx said:
"Dirty flash" means system and vendor partition will be replaced with the same files as before, but the data stays untouched. So this will have no impact on solving your problems.
"Clean flash" means the data is gone too for a new rom encryption.
With enabled encryption it is only possible to flash a new rom or stock rom by clean flash.
FYI: I solved huge battery drain what was caused by Pixel spoofing on a non Pixel.
Before I found this I was weeks further.
Only if everyone with the same rom has such drain too, there is something wrong with a rom.
If this is the case i can assure you this will be picked up by the developer of that rom.
If you have the same issue with different roms it could be directed to the hardware of the phone.
With RN10P the proximity sensor has known issues with some devices.
Click to expand...
Click to collapse
Ok i will check the spoof issue and try to flash stock rom again via Miflash tool hopefully the issue will be solved. Thanks a lot for the tips and insight