idk if posted some same thread but my problem is my phone suddenly reboots.
screen went off, twice vibration, then went to samsung galaxy s5 logo.
current setup: android 6.0.1 running no limits rom. all stock
sometimes it reboots then it is stock on the bootloader. i need to remove the battery and turn it on manually. using bootloader and modem of the latest recommended bootloader from the no limits rom.
(it also random reboots on stock firmware using spain which i downloaded from sam mobile firmwares)
is this a hardware issue?
edit: what i did was i upgraded my stock rom from 5.0.1 russia to 6.0.1 spain, does this affect anything? should i stick with russia?
rusherrrx said:
idk if posted some same thread but my problem is my phone suddenly reboots.
screen went off, twice vibration, then went to samsung galaxy s5 logo.
current setup: android 6.0.1 running no limits rom. all stock
sometimes it reboots then it is stock on the bootloader. i need to remove the battery and turn it on manually. using bootloader and modem of the latest recommended bootloader from the no limits rom.
(it also random reboots on stock firmware using spain which i downloaded from sam mobile firmwares)
is this a hardware issue?
Click to expand...
Click to collapse
Since you mentioned Hardware, Check if all the cores are working
Arabix.Sword said:
Since you mentioned Hardware, Check if all the cores are working
Click to expand...
Click to collapse
cores are all working my guess is the battery that is somehow related right??????
rusherrrx said:
cores are all working my guess is the battery that is somehow related right??????
Click to expand...
Click to collapse
i don't think it has to do with the battery because as long as you have power cores will work,
Do your phone gets too hot then?
I know what's going on I think. Something modified your kernel or something in the ROM is unstable. I had one that did that same thing when I used the camera. You need a better ROM. I recommend ressurection remix 5.8.3 nougat 7.1.2. No reason to be on marshmallow. And get this kernel. It fixed the camera issue and improves battery life. It's a unified klte rom.
godkingofcanada said:
I know what's going on I think. Something modified your kernel or something in the ROM is unstable. I had one that did that same thing when I used the camera. You need a better ROM. I recommend ressurection remix 5.8.3 nougat 7.1.2. No reason to be on marshmallow. And get this kernel. It fixed the camera issue and improves battery life. It's a unified klte rom.
Click to expand...
Click to collapse
i am currently on 6.0.1 mm stock firmware. and still i experience this issues
That does not guarantee there's no bugs in your phone. Have you ever flashed a ROM or anything to your device?
godkingofcanada said:
That does not guarantee there's no bugs in your phone. Have you ever flashed a ROM or anything to your device?
Click to expand...
Click to collapse
oh okay. well as soon as i got the device it was on android 5, flashed twrp. then flashed no limits rom didnt work (cause all i thought i can boot it to mm but no) so wiped again installed xstolite rom rather, ticked reactivation locked. [i think this was the time it started]so i updraded it to 6.0.1 but i didnt know the account cos this phone is a used phone so i did was to downgrade it to 4.4 then bypass it and it worked (still experiencing issues tho). so upgraded again to stock 6.0.1 and here i am. (
edit: im on phoenix rom latest version also using recommended bootloader and everything works tho it still reboots randomly halp plz
rusherrrx said:
oh okay. well as soon as i got the device it was on android 5, flashed twrp. then flashed no limits rom didnt work (cause all i thought i can boot it to mm but no) so wiped again installed xstolite rom rather, ticked reactivation locked. [i think this was the time it started]so i updraded it to 6.0.1 but i didnt know the account cos this phone is a used phone so i did was to downgrade it to 4.4 then bypass it and it worked (still experiencing issues tho). so upgraded again to stock 6.0.1 and here i am. (
edit: im on phoenix rom latest version also using recommended bootloader and everything works tho it still reboots randomly halp plz
Click to expand...
Click to collapse
Upgrade to a nougat ROM. It uses the same bootloader of mm so you only need to flash a ROM. Get ressurection remix or lineage is 14.1. Nougat fixes a lot of bugs and security issues. And xtrestolite isn't the most stable ROM. I had it in my s4.
---------- Post added at 06:47 AM ---------- Previous post was at 06:45 AM ----------
And then if you use rr get the kernel I showed you and flash that too. Please note these Roms don't come with gapps. Google open gapps and it comes up. You want arm 7.0 or 7.1. Stock if you don't mind waiting a while for it to download. I get nano to save time as it still installs the framework and playstore. It saves space and if you want something it didn't install play store will have it anyway.
godkingofcanada said:
Upgrade to a nougat ROM. It uses the same bootloader of mm so you only need to flash a ROM. Get ressurection remix or lineage is 14.1. Nougat fixes a lot of bugs and security issues. And xtrestolite isn't the most stable ROM. I had it in my s4.
---------- Post added at 06:47 AM ---------- Previous post was at 06:45 AM ----------
And then if you use rr get the kernel I showed you and flash that too. Please note these Roms don't come with gapps. Google open gapps and it comes up. You want arm 7.0 or 7.1. Stock if you don't mind waiting a while for it to download. I get nano to save time as it still installs the framework and playstore. It saves space and if you want something it didn't install play store will have it anyway.
Click to expand...
Click to collapse
so you mean cyanogenmod?
Cyanogen mod is now lineage os team. Don't use cyanogen. Get lineage 14.1
If none of the software fixes work, it's your battery. Personal experiance from my S3 Mini and my S5. Don't rage over it going nuts (been there, done that) but just get a new battery.
koragg97 said:
If none of the software fixes work, it's your battery. Personal experiance from my S3 Mini and my S5. Don't rage over it going nuts (been there, done that) but just get a new battery.
Click to expand...
Click to collapse
i dont see any pops or physical damage to it.. anyway, but ill update you as soon as I buy a new one. thanks!
Related
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
aytida4 said:
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
Click to expand...
Click to collapse
It's because you are flashing MM rom (except cm13) and you are on Lollipop or vice versa.
#Henkate said:
It's because you are flashing MM rom (except cm13) and you are on Lollipop or vice versa.
Click to expand...
Click to collapse
No friend actually I m using marshmallomarshmallow stock
Rom and I'm installing ressurction Rom 6.0 but still it is showing green screen. Is it the problem of BOOTLOADER?
aytida4 said:
No friend actually I m using marshmallomarshmallow stock
Rom and I'm installing ressurction Rom 6.0 but still it is showing green screen. Is it the problem of BOOTLOADER?
Click to expand...
Click to collapse
I have the same problem …
aytida4 said:
No friend actually I m using marshmallomarshmallow stock
Rom and I'm installing ressurction Rom 6.0 but still it is showing green screen. Is it the problem of BOOTLOADER?
Click to expand...
Click to collapse
SiiXFX said:
I have the same problem …
Click to expand...
Click to collapse
You must be on Lollipop to flash RR 6.0.1, just like CM13.
#Henkate said:
You must be on Lollipop to flash RR 6.0.1, just like CM13.
Click to expand...
Click to collapse
Thanks friend I will try.
Same Green Screen
I have a same problem and i try the first 5.1.1 rom and after it i install the cyanogenmod 13 which i found in the rom article anybody can help me ? skype or somthing call service ?
Vityy said:
I have a same problem and i try the first 5.1.1 rom and after it i install the cyanogenmod 13 which i found in the rom article anybody can help me ? skype or somthing call service ?
Click to expand...
Click to collapse
Friend i had that problem then i installed stock 5.1.1 rom and
Then tried this and then it is working good. U can also
Try this.
aytida4 said:
Friend i had that problem then i installed stock 5.1.1 rom and
Then tried this and then it is working good. U can also
Try this.
Click to expand...
Click to collapse
I flashed the 5.1.1 rom but still i get the green screen/lines at the boot. I always get bootloops when i flash any zip. Plz help
aytida4 said:
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
Click to expand...
Click to collapse
Possible problems,
- the rom is not for your device or variant
- The bootloader is for another version of Android
- Twrp was compiled with a different version of Android so are you going to get an error.
- Your bad luck exceeds an acceptable level ... ???
I have the same problem on my j500h too its turn to yellow color until the logo cant see because of that color i flashed custom kernel properly step by step 2 custom kernel i flashed they have already problem with that im running on 5.1.1 lollipop and my build number is LMY48B.J500HXXU1APA5
Keancarl said:
I have the same problem on my j500h too its turn to yellow color until the logo cant see because of that color i flashed custom kernel properly step by step 2 custom kernel i flashed they have already problem with that im running on 5.1.1 lollipop and my build number is LMY48B.J500HXXU1APA5
Click to expand...
Click to collapse
Which Custom Rom did you flash?
Keancarl said:
I have the same problem on my j500h too its turn to yellow color until the logo cant see because of that color i flashed custom kernel properly step by step 2 custom kernel i flashed they have already problem with that im running on 5.1.1 lollipop and my build number is LMY48B.J500HXXU1APA5
Click to expand...
Click to collapse
You get green screen when:
1) You flash MM ROMs (based on stock Touchwiz MM) over Lollipop and vice versa.
2) You flash MM/N ROMs (based on AOSP/CM such as LOS13, AOSIP, Mokee etc.) over Lollipop and vice versa.
3) I can't confirm this, but based on your comment, you get green screen when you flash a MM kernel over Lollipop and of course, vice versa too.
AndroiDTechi said:
Which Custom Rom did you flash?
Click to expand...
Click to collapse
not custom rom but kernel idk what the problem is so now i decided to have android backup in order to back again to my current system
---------- Post added at 06:46 AM ---------- Previous post was at 06:31 AM ----------
#Henkate said:
You get green screen when:
1) You flash MM ROMs (based on stock Touchwiz MM) over Lollipop and vice versa.
2) You flash MM/N ROMs (based on AOSP/CM such as LOS13, AOSIP, Mokee etc.) over Lollipop and vice versa.
3) I can't confirm this, but based on your comment, you get green screen when you flash a MM kernel over Lollipop and of course, vice versa too.
Click to expand...
Click to collapse
:good: i back to its current system now what i want is stock rom with customize and rooted system
aytida4 said:
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
Click to expand...
Click to collapse
Flash 5.1.1 cynogenmod rom then install RR remix
Demicro said:
Possible problems,
- the rom is not for your device or variant
- The bootloader is for another version of Android
- Twrp was compiled with a different version of Android so are you going to get an error.
- Your bad luck exceeds an acceptable level ...
Click to expand...
Click to collapse
For those, who -as I did - don't really understand this (see the quote)...
I had the same issue when I wanted to install a custom Marshmallow ROM (6.0.1) over my stock Lollipop (5.1.1). The solution was to download and flash a new Bootloader and Modem with Odin. See tis:
https://forum.xda-developers.com/galaxy-j5/how-to/6-0-1-5-1-1-bootloader-modem-j500xx-t3566801
I just ran into this error while trying to install a custom ROM for my J500H.
My phone was running latest 6.0.1. I installed TWRP from This thread, then installed followed the instructions to install Resurrection Remix (7.1.2), but on first boot i got the green screen with the error (set warranty bit: kernel). Also tried Lineage 14.0 but doesn't work. I can still enter TWRP and download mode after getting this error.
This is my first time flashing a Samsung device. Could someone tell me what i did wrong?
https://forum.xda-developers.com/galaxy-j5/development/rom-resurrectionremix-v5-8-1-t3566035
iH8Ecchi said:
I just ran into this error while trying to install a custom ROM for my J500H.
My phone was running latest 6.0.1. I installed TWRP from This thread, then installed followed the instructions to install Resurrection Remix (7.1.2), but on first boot i got the green screen with the error (set warranty bit: kernel). Also tried Lineage 14.0 but doesn't work. I can still enter TWRP and download mode after getting this error.
This is my first time flashing a Samsung device. Could someone tell me what i did wrong?
Click to expand...
Click to collapse
Sorry, first time i didn't your post till the end.
First of all.
Restore firmware with "Samsung smart switch".
You can downgrade to 5.1.1 by this instruction.
1.Flash this firmware by Odin
https://drive.google.com/file/d/0B-pt1IG7T4hmVzhuMnRyeTBjTGM/view?usp=drivesdk
(Before flashing, wipe all storages(all except internal, external in advanced wipe. If you have stock recovery, you must do both wipes)
2. After first boot flash recovery from Vince
(for both bootloaders)
3. Before flashing RR5.8.4 wipe all storages too( all, except extrnl and intrlnl)
4. Flash RR and gapps.
5. Wipe data and cache.
wrongwriter3 said:
Sorry, first time i didn't your post till the end.
First of all.
Restore firmware with "Samsung smart switch".
You can downgrade to 5.1.1 by this instruction.
1.Flash this firmware by Odin
https://drive.google.com/file/d/0B-pt1IG7T4hmVzhuMnRyeTBjTGM/view?usp=drivesdk
(Before flashing, wipe all storages(all except internal, external in advanced wipe. If you have stock recovery, you must do both wipes)
2. After first boot flash recovery from Vince
(for both bootloaders)
3. Before flashing RR5.8.4 wipe all storages too( all, except extrnl and intrlnl)
4. Flash RR and gapps.
5. Wipe data and cache.
Click to expand...
Click to collapse
Did you mean i have to flash RR over 5.1.1? Last time i ran into this error i was flashing it over 6.0.1, and I did full wipes within TWRP.
iH8Ecchi said:
Did you mean i have to flash RR over 5.1.1? Last time i ran into this error i was flashing it over 6.0.1, and I did full wipes within TWRP.
Click to expand...
Click to collapse
Yes.
Because it work only with 5.1.1 bootloader.
Hi, i'm starting this thread to figure out why some moto g4 and g4 plus randomly reboots and when it happes the battery percentaje changes.
For example it is on 95% and it reboots, it changes to 65%
It often happens when a notification cames and after the vibration it reboots.
Do it happens to you??
How can we fix it?
You should mention what device, rom+version, gapps+version, baseband, kernel etc. you are using. Otherwise you cannot figure out where's the problem if everyone has different setups.
It happens only in stock (marshmallow and nougat)
Xt1621 unlocked bootloader
And if I relock the bootloader it still happens
I didnt find a 100% stable ROM to be there so I don't have that bug
ivan290 said:
It happens only in stock (marshmallow and nougat)
Xt1621 unlocked bootloader
And if I relock the bootloader it still happens
I didnt find a 100% stable ROM to be there so I don't have that bug
Click to expand...
Click to collapse
If I understand correctly(if I don't get it, please explain): the problem is only on stock roms? So why not using a custom rom?
That's Right, I don't use Roms because there isn't any stable ROM, or at least I don't know. Would you recommend me a stable ROM?
ivan290 said:
That's Right, I don't use Roms because there isn't any stable ROM, or at least I don't know. Would you recommend me a stable ROM?
Click to expand...
Click to collapse
This one http://forum.xda-developers.com/moto-g4-plus/development/xt16xx-cyanogenmod-14-1-alpha-t3492274 latest build or before the 0502 ist running without any reboot/freeze. RR is also a good choice!
BTT: as your problem is on stock roms only or you have not tested any custom rom it's hard to help you. You can try another kernel, that's all. Bug fixing a stock rom isn't possible, as the source isn't available,you understand?
So try another rom and see if you're facing same problem.
Maybe I am not clear.
Yes I tried Roms that's why I know that the bug is only in stock Roms.
Thank you!
OK< this is the issue I am having with the phone, which is a Galaxy Note 3 SM-N900P (Sprint). I originally rootted it about 2 and a hal years ago, and I THINK, not absolutely sure, but think I used KingoRoot when I did, only because no matter what I couldnt get it to root otherwise. I originally installed slimkat, then in January 2016 I installed Resurrection Remix 5.1 . The phone runs great, but the rub is, it wont let me install ANY other ROMs, olde or newer. Also, when I rooted it, I had to use Flashify to install the Recovery while I was still on the original Samsung ROM. That version is 3.0.2-0. All the other info I can think of that may help anyone who is willing to give me an idea is listed below.
I would REALLY like to try a NOTE 7 rom, seems they are really really good from what I have read, or at least RR 6.0
Build Number Resurrection Remix Lollipop 5.1.1-f26-LMY48Y
Sprint Note 3 (SM-N900P) Running Resurrection Remix LP v5.5.9, rooted,
Kernal version 3.4.0-g7db381d
[email protected] #1
Baseband Version
N900pVPUEOK2
ANY help would be fantastically appreciated, have been a big fan of this site since WAY back (AT&T Pocket PC PHONE and Samsung BlackJack years.)
Thanks in advance.
I would also ask in the SPRINT forum .
JJEgan said:
I would also ask in the SPRINT forum .
Click to expand...
Click to collapse
Good idea, thanks.
jdd1960 said:
OK< this is the issue I am having with the phone, which is a Galaxy Note 3 SM-N900P (Sprint). I originally rootted it about 2 and a hal years ago, and I THINK, not absolutely sure, but think I used KingoRoot when I did, only because no matter what I couldnt get it to root otherwise. I originally installed slimkat, then in January 2016 I installed Resurrection Remix 5.1 . The phone runs great, but the rub is, it wont let me install ANY other ROMs, olde or newer. Also, when I rooted it, I had to use Flashify to install the Recovery while I was still on the original Samsung ROM. That version is 3.0.2-0. All the other info I can think of that may help anyone who is willing to give me an idea is listed below.
I would REALLY like to try a NOTE 7 rom, seems they are really really good from what I have read, or at least RR 6.0
Build Number Resurrection Remix Lollipop 5.1.1-f26-LMY48Y
Sprint Note 3 (SM-N900P) Running Resurrection Remix LP v5.5.9, rooted,
Kernal version 3.4.0-g7db381d
[email protected] #1
Baseband Version
N900pVPUEOK2
ANY help would be fantastically appreciated, have been a big fan of this site since WAY back (AT&T Pocket PC PHONE and Samsung BlackJack years.)
Thanks in advance.
Click to expand...
Click to collapse
I would risk it and factory wipe, install stock ROM and try to root using the newest methods available and proceed to flash a custom recovery (TWRP 2.8.7 recommended) since it appears to be the most compatible with the newer ROMs
Your choice though
ShaDisNX255 said:
I would risk it and factory wipe, install stock ROM and try to root using the newest methods available and proceed to flash a custom recovery (TWRP 2.8.7 recommended) since it appears to be the most compatible with the newer ROMs
Your choice though
Click to expand...
Click to collapse
That was the best idea. I did a factory wipe, didnt install a stock rom, and as you suggested flashed TWRP 2.8.7, and now works just fine, hell it even fixed some other issues I had been having. Thanks, much appreciated.
jdd1960 said:
That was the best idea. I did a factory wipe, didnt install a stock rom, and as you suggested flashed TWRP 2.8.7, and now works just fine, hell it even fixed some other issues I had been having. Thanks, much appreciated.
Click to expand...
Click to collapse
You're welcome. Happy flashing!
Hi guys,
Everything was working great with LineageOS 15.1 (Android 8.1), but they have discontinued the support for this version and switched to 16.0, and a FOTA update of Lineage from 15 to 16 isn't possible, so I had to download the zip manually, and flashed it using TWRP, around the end of April. Since then the Wi-Fi does not work.
I should explain what this "does not work" mean: I turn it on (either from the pull-down curtain, or from the Settings -> Network -> Wi-Fi menu), it pretends to switch on for 1-2 seconds, and then the switch turns off by itself, so it doesn't even have time to scan the available networks.
I have tried to burn a newer image again, around the beginning of May, but it didn't fix the Wi-Fi problem. I was googling a lot, but seems like nobody reports such a problem.
Any ideas how to fix it, other than going back to Android 8.1? Preferably I'd like to stay with LOS, but if I have no choice, I can consider moving to RR, or AOSP Extended or whatever.
Thanks!
I think its a boot.img problem. I have seen this error in stock too. The wifi/bluetooth used to turn off immediately after i turned them on and the error was because i flashed the wrong boot.img . If i were you i would clean flash the rom again
What do you mean by "wrong boot.img"? I don't flash any boot.img separately, I just flash the whole LineageOS rom (and then Gapps) from TWRP. Should I flash anything else? I don't think so...
Well, in my case at least the Bluetooth works properly (with both headphones and smart watch).
SOLVED!
Surprisingly, the problem seems to be solved now.
After flashing lineage-16.0-20190426 and later lineage-16.0-20190530 versions, where the Wi-Fi didn't work - today I have flashed lineage-16.0-20190704, and guess what? It is back now!
Thought it should be important to update the thread here.
xdauseril said:
Surprisingly, the problem seems to be solved now.
After flashing lineage-16.0-20190426 and later lineage-16.0-20190530 versions, where the Wi-Fi didn't work - today I have flashed lineage-16.0-20190704, and guess what? It is back now!
Thought it should be important to update the thread here.
Click to expand...
Click to collapse
It would be safer to update to stock pie first then flash custom pie roms..
Jt380p said:
It would be safer to update to stock pie first then flash custom pie roms..
Click to expand...
Click to collapse
You mean, even if I upgrade from Lineage 15.1 to 16 I need to flash the stock rom first? Why?
BTW I saw some reports on Wi-Fi problem while going back from custom to stock rom too, and there was some patch suggested to fix it.
xdauseril said:
You mean, even if I upgrade from Lineage 15.1 to 16 I need to flash the stock rom first? Why?
BTW I saw some reports on Wi-Fi problem while going back from custom to stock rom too, and there was some patch suggested to fix it.
Click to expand...
Click to collapse
Because its a prerequisite on Lineage 16, it depends on parts of stock Pie rom being installed.
The LO16 thread also listed a migration step if you didn't flash the stock Pie rom beforehand.
barrack1 said:
Because its a prerequisite on Lineage 16, it depends on parts of stock Pie rom being installed.
The LO16 thread also listed a migration step if you didn't flash the stock Pie rom beforehand.
Click to expand...
Click to collapse
Probably I have missed it.
Still can't find it neither on "install" nor "update" page:
https://wiki.lineageos.org/devices/tissot/install
https://wiki.lineageos.org/devices/tissot/update
xdauseril said:
Probably I have missed it.
Still can't find it neither on "install" nor "update" page:
https://wiki.lineageos.org/devices/tissot/install
https://wiki.lineageos.org/devices/tissot/update
Click to expand...
Click to collapse
Its on the xda thread, not on the lineageos website.
Xiaomi made some changes during the upgrade from Oreo->Pie and introduced ARB. Now you cannot downgrade back to Oreo easily. Just flashing back to Oreo(stock or custom rom) will cause the phone to bootloop. For the same reason your phone probably faced issues when you flashed (Pie) LO16 without the Pie firmware.
barrack1 said:
Its on the xda thread, not on the lineageos website.
Xiaomi made some changes during the upgrade from Oreo->Pie and introduced ARB. Now you cannot downgrade back to Oreo easily. Just flashing back to Oreo(stock or custom rom) will cause the phone to bootloop. For the same reason your phone probably faced issues when you flashed (Pie) LO16 without the Pie firmware.
Click to expand...
Click to collapse
Well, I did not try to downgrade from Pie to Oreo. All I tried to do was an upgrade from LOS 15.1 to LOS 16 (15.1 worked excellent). And I had no idea I needed to flash the stock rom in between, so I just flashed 16 over 15.1, without wiping the data partition (only wiped dalvik cache).
Can you please point me to the XDA thread you mention, where it says I had to flash the stock rom first?
Anyway, since everything works OK now (or, at least, I don't find any malfunctioning, probably except for the native camera app, so I use an external app), I don't think I should play around with it again, right?
xdauseril said:
Well, I did not try to downgrade from Pie to Oreo. All I tried to do was an upgrade from LOS 15.1 to LOS 16 (15.1 worked excellent). And I had no idea I needed to flash the stock rom in between, so I just flashed 16 over 15.1, without wiping the data partition (only wiped dalvik cache).
Can you please point me to the XDA thread you mention, where it says I had to flash the stock rom first?
Anyway, since everything works OK now (or, at least, I don't find any malfunctioning, probably except for the native camera app, so I use an external app), I don't think I should play around with it again, right?
Click to expand...
Click to collapse
Some parts of the firmware might not be overwritten by LOS/stock depending on the version. The original LO16 used Oreo firmware iirc. The thread is not hard to find, just look for it.
my phone works stable with the official rom but all the custom roms are crashing.
aospextended v6.7 and resurrection remix pie 7.0.2 are bootlooping, i can't even complete the first setup. rebooted over 20 times. during the first setup or at the boot logo. i couldn't even complete my setup and see the launcher.
groovy works better, but randomly reboots here and there. sometimes in minutes sometimes in few hours... got 5 crashes so far, it's the only rom that's "kinda usable" but google play services and setup wizard crashed during the first setup
https://imgur.com/drxsurP
https://imgur.com/9h4O6Iz
also tried changing my kernel, installed icey, nothing changes...
what might be the problem here?
phone is zenfone selfie zd551kl (z00t)
installing gapps pico but tried without gapps as well... same problems.
bootloader is unlocked.
using twrp 3.3.1-0, 3.4.0-0 gives me error 7 and can't install roms.
my battery is new, it can last over a week with the stock rom. without any crashes... completely stable. i don't thing it has any hardware issues.
can i even log the errors if it can't even boot properly? if so, how?
what can i try to solve this problem?
Flash twrp latest version.. reboot to twrp..wipe everything...then power off your phone..then again reboot to twrp.. now install your rom from sd card.. hopefully you won't get any errors
nhASIF said:
Flash twrp latest version.. reboot to twrp..wipe everything...then power off your phone..then again reboot to twrp.. now install your rom from sd card.. hopefully you won't get any errors
Click to expand...
Click to collapse
okay, restarting after the wipe helped with twrp 3.4.0-0, i could install without error 7 this time.
but the phone still rebooted at the "hi there" screen, a few seconds after the first boot... then did it again. now booting for the third time... still not stable.
edit:4th reboot...
8 reboots so far... yeah same bootloop again. not fixed the problem.
can i take logs from a bootlooping phone? i can't enable debugging from the settings...
edit2: tried again without gapps, aospextended booted. and apparently developer options and debugging are enabled by default. guess i can take logs after all... now waiting to see if it'll crash again without gapps.
edit3: tried nikgapps instead of opengapps since it doesnt have that first google setup process, rebooted 3 times at first but now the uptime is 30 minutes.
edit4: crashed when i tried to signin google play store.
here's a logcat
logcat - Pastebin
Pastebin.pl is a website where you can store code/text online for a set period of time and share to anybody on earth
pastebin.pl
took a few of them ranges from 126kb to 681kb. this is the shortest one.
zenfone selfie said:
here's a logcat
logcat - Pastebin
Pastebin.pl is a website where you can store code/text online for a set period of time and share to anybody on earth
pastebin.pl
took a few of them ranges from 126kb to 681kb. this is the shortest one.
Click to expand...
Click to collapse
Flash the latest stock rom..then flash twrp and custom rom...if it doesn't work you should give up
nhASIF said:
Flash the latest stock rom..then flash twrp and custom rom...if it doesn't work you should give up
Click to expand...
Click to collapse
i did. but why give up? if i have a working device and stable custom rom i should be able to make it work? what else can i try?
nhASIF said:
Flash the latest stock rom..then flash twrp and custom rom...if it doesn't work you should give up
Click to expand...
Click to collapse
tried resurrection remix marshmallow from 2016, looks stable so far... so, my phone is not compatible with nougat and above? does it make any sense? am i missing some other factory software? is it update-able?
edit: rr mm wasn't stable either. a bit better and not bootlooping but crashes as random points...
now i'm flashing all the stock roms sequentially from the release of this phone. then i'll try one more time...
if it doesn't work i might try flashing latest lollipop and install custom roms over it.
i went back to stock lollipop and installed rr marshmallow on it, no restarts or bootloops so far... looks stable. but it's from 2016.
if i install mm firmware and a newer version of mm nougat oreo or pie roms it won't run stable.
so, my phone is not stable with the custom roms that are using mm firmware for some reason... any ideas?
also what's the best rom i can use with lollipop firmware?
zenfone selfie said:
i went back to stock lollipop and installed rr marshmallow on it, no restarts or bootloops so far... looks stable. but it's from 2016.
if i install mm firmware and a newer version of mm nougat oreo or pie roms it won't run stable.
so, my phone is not stable with the custom roms that are using mm firmware for some reason... any ideas?
also what's the best rom i can use with lollipop firmware?
Click to expand...
Click to collapse
I've had an idea needed to test it first, I got back to latest stock w.w version after booted up completely flashed twrp using adb and wiped cache system and data without wiping ASDF Partition then flashed AEX pie rom( I had problem with my handsfree last I checked) with ICEYS_C kernel and and gapps nano 2020/12/19
After booting up completely my handsfree worked perfectly!
So 2 changes:
1-Stock kernel with w.w version
2-not wiping ASDF Partition
You can try that maybe your problem with custom roms would solve!
Check this thread
[GUIDE][ZD551KL] Zenfone Selfie bootloop, brick, firmware upgrade errors fix etc.
I had to fix a couple of bricked selfie phones (z00ud and z00udb but i assume this works on any selfie zd551kl model), that were probably bricked by autoflashing wrong firmware, so after spending a few days going thru many different tutorials...
forum.xda-developers.com
m.amin.bayat said:
I've had an idea needed to test it first, I got back to latest stock w.w version after booted up completely flashed twrp using adb and wiped cache system and data without wiping ASDF Partition then flashed AEX pie rom( I had problem with my handsfree last I checked) with ICEYS_C kernel and and gapps nano 2020/12/19
After booting up completely my handsfree worked perfectly!
So 2 changes:
1-Stock kernel with w.w version
2-not wiping ASDF Partition
You can try that maybe your problem with custom roms would solve!
Check this thread
[GUIDE][ZD551KL] Zenfone Selfie bootloop, brick, firmware upgrade errors fix etc.
I had to fix a couple of bricked selfie phones (z00ud and z00udb but i assume this works on any selfie zd551kl model), that were probably bricked by autoflashing wrong firmware, so after spending a few days going thru many different tutorials...
forum.xda-developers.com
Click to expand...
Click to collapse
i already did install latest stock ww and flashed custom roms over it if that's what ur saying. i tried without wiping adsf as well...
anything else?
that guide is instucting how to flash cn firmware then back to ww. would that help?
can i flash custom roms on the cn firmware? would that work?
zenfone selfie said:
i already did install latest stock ww and flashed custom roms over it if that's what ur saying. i tried without wiping adsf as well...
anything else?
that guide is instucting how to flash cn firmware then back to ww. would that help?
can i flash custom roms on the cn firmware? would that work?
Click to expand...
Click to collapse
First I have no other ideas yet.. and second it worth a try cause what causes your problem is unknown!
If any ideas comes to mind, I'll tell you
m.amin.bayat said:
First I have no other ideas yet.. and second it worth a try cause what causes your problem is unknown!
If any ideas comes to mind, I'll tell you
Click to expand...
Click to collapse
i can't fine stock mm rom for cn tho... latest rom available is CN_1.15.40.1548
m.amin.bayat said:
First I have no other ideas yet.. and second it worth a try cause what causes your problem is unknown!
If any ideas comes to mind, I'll tell you
Click to expand...
Click to collapse
didn't work...
flashed chinese lollipop, updated to the latest version, flashed japanese marshmallow firmware over it etc. its the same.
only stable custom roms are the ones that using lollipop firmware . with marshmallow firmware only the stock rom is stable.
zenfone selfie said:
didn't work...
flashed chinese lollipop, updated to the latest version, flashed japanese marshmallow firmware over it etc. its the same.
only stable custom roms are the ones that using lollipop firmware . with marshmallow firmware only the stock rom is stable.
Click to expand...
Click to collapse
The only thing you did different than the others is unofficial way of bootloader unlocking maybe this is the issue maybe not...I don't know really
I did it officially 3 years ago!
I think you should consider buying a new phone or use it with stock Rom...sorry I couldn't help you much!
m.amin.bayat said:
The only thing you did different than the others is unofficial way of bootloader unlocking maybe this is the issue maybe not...I don't know really
I did it officially 3 years ago!
I think you should consider buying a new phone or use it with stock Rom...sorry I couldn't help you much!
Click to expand...
Click to collapse
there are others with unofficially unlocked bootloaders, using custom roms...
i might use "ResurrectionRemix-M-v5.6.9-20160607-Z00T-OFFICIAL"
went back to it after my last attempt with japanese firmware+pie roms. never crashed, so far looks stable enough. and definitely cleaner than crappy bloated zenui
its my secondary phone btw.
@m.amin.bayat
today i found that zenfone 2 laser had a more up to date stock rom, tried it on my selfie and installed custom rom over it. didn't work either.
Version WW-21.40.1220.2181 2019/08/07
emmc_appsboot_8939.mbn file from the firmware update was different so i had a hope for a few minutes
btw how's ur performance? am i losing optimization and performance with the cyanogen nightly based rom from 2016?
https://imgur.com/a/vAq3Gle
my performance is pretty bad compared to this one for example https://browser.geekbench.com/v4/cpu/13132264
zenfone selfie said:
@m.amin.bayat
today i found that zenfone 2 laser had a more up to date stock rom, tried it on my selfie and installed custom rom over it. didn't work either.
Version WW-21.40.1220.2181 2019/08/07
emmc_appsboot_8939.mbn file from the firmware update was different so i had a hope for a few minutes
btw how's ur performance? am i losing optimization and performance with the cyanogen nightly based rom from 2016?
https://imgur.com/a/vAq3Gle
my performance is pretty bad compared to this one for example https://browser.geekbench.com/v4/cpu/13132264
Click to expand...
Click to collapse
Embarrassing score for me!!!
But I don't have lack of performance, why this score?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mine is geekbench4, yours geekbench5.
marshmallow is not compatible with 5 so i couldn't bench it. you can install 4 tho. to compare...
what about 3dmark slingshot? that should be the same
wish i could at least run nougat roms tho. groovy android is more than enough for me.
marshmallow doesn't even have the double tap to switch gesture for last 2 apps its annoying. it doesn't support google dialer's recent versions so no dark mode... last security patch is from 2016...
why am i so unlucky?
edit:damn geekbench5 is much harder i guess...
even my main phone with snapdragon835 can't beat zenfone selfie's geekbench4 single core score
https://imgur.com/iWHuiIH
also roughly 1/3 the performance of nokia8 looks great for such an old mid range phone. wish i could use pie on it too
and since my main phone is pie, that would be easier for me. now they're just too different to switch between. i'm swiping recent apps up to close them or double tapping the recent apps button on my asus etc.
zenfone selfie said:
mine is geekbench4, yours geekbench5.
marshmallow is not compatible with 5 so i couldn't bench it. you can install 4 tho. to compare...
what about 3dmark slingshot? that should be the same
wish i could at least run nougat roms tho. groovy android is more than enough for me.
marshmallow doesn't even have the double tap to switch gesture for last 2 apps its annoying. it doesn't support google dialer's recent versions so no dark mode... last security patch is from 2016...
why am i so unlucky?
edit:damn geekbench5 is much harder i guess...
even my main phone with snapdragon835 can't beat zenfone selfie's geekbench4 single core score
https://imgur.com/iWHuiIH
also roughly 1/3 the performance of nokia8 looks great for such an old mid range phone. wish i could use pie on it too
and since my main phone is pie, that would be easier for me. now they're just too different to switch between. i'm swiping recent apps up to close them or double tapping the recent apps button on my asus etc.
Click to expand...
Click to collapse
Not so embarrassing this time
m.amin.bayat said:
Not so embarrassing this timeView attachment 5172013
Click to expand...
Click to collapse
physics score is much higher wow.
so i'm losing performance, security, usability, new features and better design... great! same hardware and i'm not being able to utilize its potential.
meanwhile i had to install xposed and n-ify module for switching between last 2 apps by double tapping recents button gesture and a better quicksettings/notification panel. its not perfect, maybe because my rom is not stock cyanogen and instead resurrection remix with extra customizations... but its not bad, definitely an improvement.
can't properly hide my root with xposed installed tho.