Related
im in need of urgent help..i think i soft bricked my s4 when trying to restore my efs backup.
i tried downgrading my firmware to mf8..and the modem was flashed as well.
When i checked the imei it was null.
so i went on to restore it using method 2 on this thread http://forum.xda-developers.com/showthread.php?t=2392632&page=6
After i put everything into the terminal and it was restored, i rebooted my phone.
Now my phone is stuck at samsung boot logo!!
i tried restoring from my nandroid backup but it didnt work..still stuck at boot logo, i tried restoring the rom to stock, still stuck at boot logo.
Basically no matter what i do, its not booting and its stuck at boot logo.
I can access download mode and cwm recovery. On stock recover i get the error message "failed to mount /efs (Invalid argument)"
is there anything i can do at all?
i still have multiple backups of my efs folder..i just dont know how to restore it
please help
I'd suggest doing a flash of the stock firmware via ODIN.
xyzulu said:
I'd suggest doing a flash of the stock firmware via ODIN.
Click to expand...
Click to collapse
Tried that, still no luck
You can try via kies. Do not connect the phone yet. Pull the battery out and use the information you can see there. Ooen kies Go to upgrade settings and find the one that ask you for your model. Fill the blank, then enter your s/n. A window will show up asking you again. Accept. And kies is suppose to start dowloading the firmware. Make sure to conect the device in dowload mode before it finishs dowloading.
Im not saying it gonna work 100% for you but i had restore a couple samsung devices using this method.
I prefer odin btw.
Sent from my GT-I9505G using xda premium
ToledoG28 said:
You can try via kies. Do not connect the phone yet. Pull the battery out and use the information you can see there. Ooen kies Go to upgrade settings and find the one that ask you for your model. Fill the blank, then enter your s/n. A window will show up asking you again. Accept. And kies is suppose to start dowloading the firmware. Make sure to conect the device in dowload mode before it finishs dowloading.
Im not saying it gonna work 100% for you but i had restore a couple samsung devices using this method.
I prefer odin btw.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
i downloaded latest software version for my phone (MG9) and flashed it but it didnt work (still stuck at boot screen).
I then tried flashing it with adonis.pit and that still didnt work (stuck at boot screen)
however the boot sound cuts out at the boot screen and im not sure what could cause that, and in stock recovery im getting failed to mount /efs (Invalid argument)
bump?
any more suggestions guys..im still stuck in boot
flashing firmware from this thread http://forum.gsmhosting.com/vbb/f777/galaxy-s4-gt-i9500-repair-imei-null-null-1685562/ solved my imei Null/Null problem
remember to back up your imei first before flashing any upgrade.. cek this http://forum.xda-developers.com/showthread.php?p=41559366
blue-line said:
flashing firmware from this thread http://forum.gsmhosting.com/vbb/f777/galaxy-s4-gt-i9500-repair-imei-null-null-1685562/ solved my imei Null/Null problem
remember to back up your imei first before flashing any upgrade.. cek this http://forum.xda-developers.com/showthread.php?p=41559366
Click to expand...
Click to collapse
Tried this, didnt work.
I've had the issue with being stuck on the boot screen before - and it was because I wasn't deleting my cache before flashing the new firmware. Do this from within recovery :good:
starscream0 said:
im in need of urgent help..i think i soft bricked my s4 when trying to restore my efs backup.
i tried downgrading my firmware to mf8..and the modem was flashed as well.
When i checked the imei it was null.
so i went on to restore it using method 2 on this thread http://forum.xda-developers.com/showthread.php?t=2392632&page=6
After i put everything into the terminal and it was restored, i rebooted my phone.
Now my phone is stuck at samsung boot logo!!
i tried restoring from my nandroid backup but it didnt work..still stuck at boot logo, i tried restoring the rom to stock, still stuck at boot logo.
Basically no matter what i do, its not booting and its stuck at boot logo.
I can access download mode and cwm recovery. On stock recover i get the error message "failed to mount /efs (Invalid argument)"
is there anything i can do at all?
i still have multiple backups of my efs folder..i just dont know how to restore it
please help
Click to expand...
Click to collapse
I hope this guide will help :http://forum.xda-developers.com/showthread.php?t=2403292
starscream0 said:
im in need of urgent help..i think i soft bricked my s4 when trying to restore my efs backup.
i tried downgrading my firmware to mf8..and the modem was flashed as well.
When i checked the imei it was null.
so i went on to restore it using method 2 on this thread http://forum.xda-developers.com/showthread.php?t=2392632&page=6
After i put everything into the terminal and it was restored, i rebooted my phone.
Now my phone is stuck at samsung boot logo!!
i tried restoring from my nandroid backup but it didnt work..still stuck at boot logo, i tried restoring the rom to stock, still stuck at boot logo.
Basically no matter what i do, its not booting and its stuck at boot logo.
I can access download mode and cwm recovery. On stock recover i get the error message "failed to mount /efs (Invalid argument)"
is there anything i can do at all?
i still have multiple backups of my efs folder..i just dont know how to restore it
please help
Click to expand...
Click to collapse
Flash an older modem with Odin, that should solve your poblem, look in my signature for available modems.
gee2012 said:
Flash an older modem with Odin, that should solve your poblem, look in my signature for available modems.
Click to expand...
Click to collapse
thanks for trying to assist. i was able to revive my phone using this method
http://forum.xda-developers.com/showpost.php?p=39523753&postcount=4
I dunno what went wrong here...
1) I have GT-I9505 (SSN: -I9505GSMH). I installed Galaxy S4 toolkit
2) Reboot into download mode. Used toolkit/Odin to root phone. Boots up. See SU.
3) Reboot into download mode. Used toolkit/Odin. Flashed TWRP Recovery
4) Phone boots up normal. Reboot into TWRP recovery. Did a factory Reset. Format.
5) Installed Zip (Latest Omega 9.0 ROM), unchecked the things I didn't want to install. Completed install, no errors reported. Rebooted.
6) Phone stuck on Samsung boot screen. I left it overnight thinking sometimes it may take 15 mins to boot system after new install.
7) Woke up, battery dead. Tried to charge phone. No charging indicators when plugged in. With whatever juice I had left I booted into TWRP recovery, it starts to charge again as I see the % batter increase after 5 mins.
-=-=-=-=- Did the Following to try to repair
a) Reinstalled Omega, this time leaving alll options on. Rebooted, stuck in Samsung boot
b) Flashed Phil CWM touch recovery, did complete wipe to install new ROM. Rebooted into Phil recovery. Flashed OMEGA. Reboot, stuck in Samsung boot.
c) Rebooted into Phil recovery, installed echo ROM, rebooted. Black screen. Rebooted into Phil. This time cannot get into recovery.
d) Started panicking, used Odin flashed TWRP. Would not flash. Something displayed about PIT error. Flashed Phil again. Reboot into recovery, WORKS! (recovery only). Went back into Download mode flashed TWRP. Rebooted, also WORKS!. Did a factory wipe. During wipe there was an error. Format, factory reset, error during wipe. Flashed OMEGA. Reboot. Stuck on samsung boot loop.
e) Downloaded official Samsung kernal for i9505 thinking it was the full flash rom. Flashed with ODIN (hoping to put everything back to factory). Completed flash, phone boots. I get OMEGA ANIMATION!!! Waited for 15 mins. Stuck on Animation. Reflashed TWRP. Rebooted, installed OMEGA...again. Stuck on samsung boot screen.
-=-=-= Kinda frustrated. What did I do wrong in the beginning?
There are so many official roms for the S4 based on region. What can I do to put it back to factory again? I purchased phone in Australia @ Samsung store. I figured download the Australia ROM but there are like 5 of them 4 being network branded roms I think. THe other one XSA is unbranded?
I tried searching for help but so far nothing works.
omega ROM or any other custom ROM uses single CSC so before booting into system you must boot into stock recovery to apply CSC of that ROM, download stock recovery of that firmware the ROM was built from
after applying CSC it will work if not flash Omega 9.0 again , it will work :good::good:
arnob_xperia said:
omega ROM or any other custom ROM uses single CSC so before booting into system you must boot into stock recovery to apply CSC of that ROM, download stock recovery of that firmware the ROM was built from
after applying CSC it will work if not flash Omega 9.0 again , it will work :good::good:
Click to expand...
Click to collapse
Thanks for responding
So I take it when I did the full factory wipe and FORMAT the formatting part erased the CSC?
The steps are:
1) Find stock recovery of the original ROM OMEGA was built on. Use odin, flash that specific recovery. ( I might as well do a complete flash of the original stock firmware)
2) Use odin, replace recovery with TWRP, flash Omega this time no formatting
Reboot should be ok?
kabloomz said:
Thanks for responding
So I take it when I did the full factory wipe and FORMAT the formatting part erased the CSC?
The steps are:
1) Find stock recovery of the original ROM OMEGA was built on. Use odin, flash that specific recovery. ( I might as well do a complete flash of the original stock firmware)
2) Use odin, replace recovery with TWRP, flash Omega this time no formatting
Reboot should be ok?
Click to expand...
Click to collapse
first use CWM or TWRP or whatever you want and format everthing
flash a fresh firmware(latest i prefer)
then flash stock recovery via odin of the built version what v9 was used, simply reboot to recovery and it will say MULTI CSC APPLIED from fresh frimware you used
then flash TWRP/CWM and flash v9
again simply reboot to recovery and it will say MULTI CSC APPLIED from V9
it will reboot, you must need to apply CSC to boot your phone
I can confirm this!
I was trying to flash Omega 9 on top of jamal's 4.3 and my phone always booted to recovery. So I restored my stock touchwiz (no custom recovery or even root) nandroid backup and applied Omega 9: it worked!
douglascamata said:
I was trying to flash Omega 9 on top of jamal's 4.3 and my phone always booted to recovery. So I restored my stock touchwiz (no custom recovery or even root) nandroid backup and applied Omega 9: it worked!
Click to expand...
Click to collapse
thats right stock recovery boot is needed to apply CSC
problem
I need help. I am on stock build i9505XXUBMG5. then I rooted it using CF-autoroot. and i used the 1.85 version of ODIN. (Does the version of ODIN affect how the phone is rooted?) Anyways, After that, it is rooted. then after some time, my Wifi is not working or not turning on. I checked google and found the *#0011# method and turned off the Wifi power saving. Then, at first, it worked. After a while, the problem insists. but randomly turns on. I observed that in the *#0011# -> wifi window, the state is power off. but when it is completely not turning on, the state is now disconnected. How can I fix this?
I tried flashing Omega ROM, because there was a wifi fix on that ROM. But when I finished flashing it and continue to reboot, it's stuck on the boot animation. It is not even the Omega robot animation, just the original animation. (Another problem) i tried wiping cache, delvik cache and data but nothing happens.
macoy_412 said:
I need help. I am on stock build i9505XXUBMG5. then I rooted it using CF-autoroot. and i used the 1.85 version of ODIN. (Does the version of ODIN affect how the phone is rooted?) Anyways, After that, it is rooted. then after some time, my Wifi is not working or not turning on. I checked google and found the *#0011# method and turned off the Wifi power saving. Then, at first, it worked. After a while, the problem insists. but randomly turns on. I observed that in the *#0011# -> wifi window, the state is power off. but when it is completely not turning on, the state is now disconnected. How can I fix this?
I tried flashing Omega ROM, because there was a wifi fix on that ROM. But when I finished flashing it and continue to reboot, it's stuck on the boot animation. It is not even the Omega robot animation, just the original animation. (Another problem) i tried wiping cache, delvik cache and data but nothing happens.
Click to expand...
Click to collapse
Do you have an IMEI showing on your phone? What recovery did you use to flash Omega?
It matters, because some recoveries will screw it up.
Do you try to install with Philz recovery?
Sent from my GT-I9505 using xda premium
macoy_412 said:
I need help. I am on stock build i9505XXUBMG5. then I rooted it using CF-autoroot. and i used the 1.85 version of ODIN. (Does the version of ODIN affect how the phone is rooted?) Anyways, After that, it is rooted. then after some time, my Wifi is not working or not turning on. I checked google and found the *#0011# method and turned off the Wifi power saving. Then, at first, it worked. After a while, the problem insists. but randomly turns on. I observed that in the *#0011# -> wifi window, the state is power off. but when it is completely not turning on, the state is now disconnected. How can I fix this?
I tried flashing Omega ROM, because there was a wifi fix on that ROM. But when I finished flashing it and continue to reboot, it's stuck on the boot animation. It is not even the Omega robot animation, just the original animation. (Another problem) i tried wiping cache, delvik cache and data but nothing happens.
Click to expand...
Click to collapse
At this point I think it is the CSC issue arnob-xperia mentioned.
This is how I corrected my issue.
1) Omega v10 uses newer base FW. In their description it tells u. (ex: ver 9 uses XUBMG5). Search on the i9505 forums here. I can't link for some reason I can't see any of the stickied threads, especially the one listing all avail stock firmwares.
Flash into Philz or TWRP do a complete wipe of everything including data. etc.
You MUST download the full firmware, Not just the smaller kernel and recovery or csc. The full stock fw is usually over 1.6 GB. Anything around that range and u got the right one for Odin flash with the md5. Use Odin to flash. I used 1.85 and it was fine.
2) Once done it will reboot and in theory you are stock everything. At this point, for me somehow the phone got stuck in fricken boot loop. I pulled out battery, reboot into stock recovery and made sure I saw the multicsc. Rebooted. Still boot loop.
After hours of doing all sorts of things and putting the phone aside for a day. Came back, flashed the stock fw again using Odin. Reboot into recovery. Check the multi csc. Reboot. Stuck in boot loop. Reboot to download mode. Then I decided to ROOT the phone for ****s and giggles. This worked!
Phone booted.
3) Now you have stock (for that specific OMEGA fw) w/ the matching CSC. From here on follow OMEGA flash instructions for the specific things it tells u to wipe. DO NOT DO A FULL WIPE/FORMAT like I did (what got me in the mess to begin with).
** For Galaxy S3s, S4s, for some reason I've always had problems with TWRP. I had better luck using Philz. Everyone's personal experience varies on this one.
** I think the problem has to do with the CSC which handles specific region phone and carrier modes. This doesn't mean that it won't work if you use a diff region CSC. Just that it has to match the FW base you are using otherwise you have all sorts of problems. After that you can go in android and setup your APNs etc if you have probs with data. I didn't have this problem and was testing using the UK fw base on AU network sim.
*** Why does Samsung make things so damn complicated. I remember way back in 2k3 using fricken ODIN (samsung flashing utitility) to flash **** and it was the same setup as now. This whole crap about CSC pairing is a bit annoying. It is bad enough there are 6+ variations of S4s lol...
Hope this helps.
wifi problem
kabloomz said:
At this point I think it is the CSC issue arnob-xperia mentioned.
This is how I corrected my issue.
1) Omega v10 uses newer base FW. In their description it tells u. (ex: ver 9 uses XUBMG5). Search on the i9505 forums here. I can't link for some reason I can't see any of the stickied threads, especially the one listing all avail stock firmwares.
Flash into Philz or TWRP do a complete wipe of everything including data. etc.
You MUST download the full firmware, Not just the smaller kernel and recovery or csc. The full stock fw is usually over 1.6 GB. Anything around that range and u got the right one for Odin flash with the md5. Use Odin to flash. I used 1.85 and it was fine.
2) Once done it will reboot and in theory you are stock everything. At this point, for me somehow the phone got stuck in fricken boot loop. I pulled out battery, reboot into stock recovery and made sure I saw the multicsc. Rebooted. Still boot loop.
After hours of doing all sorts of things and putting the phone aside for a day. Came back, flashed the stock fw again using Odin. Reboot into recovery. Check the multi csc. Reboot. Stuck in boot loop. Reboot to download mode. Then I decided to ROOT the phone for ****s and giggles. This worked!
Phone booted.
3) Now you have stock (for that specific OMEGA fw) w/ the matching CSC. From here on follow OMEGA flash instructions for the specific things it tells u to wipe. DO NOT DO A FULL WIPE/FORMAT like I did (what got me in the mess to begin with).
** For Galaxy S3s, S4s, for some reason I've always had problems with TWRP. I had better luck using Philz. Everyone's personal experience varies on this one.
** I think the problem has to do with the CSC which handles specific region phone and carrier modes. This doesn't mean that it won't work if you use a diff region CSC. Just that it has to match the FW base you are using otherwise you have all sorts of problems. After that you can go in android and setup your APNs etc if you have probs with data. I didn't have this problem and was testing using the UK fw base on AU network sim.
*** Why does Samsung make things so damn complicated. I remember way back in 2k3 using fricken ODIN (samsung flashing utitility) to flash **** and it was the same setup as now. This whole crap about CSC pairing is a bit annoying. It is bad enough there are 6+ variations of S4s lol...
Hope this helps.
Click to expand...
Click to collapse
I did flash the Omega v9.1 and applied the wifi fix but the wifi is still broken. I tried unrooting it by flashing the original rom and formatting the data but the wifi is still broken. I can't turn it on. Thanks for the instructions anyways. ))
no pit partition
also, when i tried to root it again, it fails and says there is no PIT partition..
Where is the csc in TWRP so I can so what ones on the phone..??
What stock firmware can I use for a Orange Network in the UK.
GT-i9505 stuck on boot when upgraded from omega v16 to v21
Hello guys,
Well, I followed all the instructions and flashed new bootloader and new modem and after that I installed omega v21 with Full swipe. After that I ended up stuck in boot animation. :s What to do? I already tried to re-flash modem and bootloader, updated CWM and tried to re-install that v21 and after that I flashed twrp over cwm and tried to re-install v21 but always I ended up stuck in that boot animation. :S All installs were successful, but it just wont boot.
What to do?
Hopefully you understand my problem.
Cheers from Finland!
Nico
EDIT:
Ok, I flashed omega rom v19 with full wipe and tried to boot. Didnt work, but then I installed Kies to my computer, opened Kies, Plugged USB in and started my phone and then Kaboom! It booted. What exactly happened there?
BizK1d said:
Hello guys,
Well, I followed all the instructions and flashed new bootloader and new modem and after that I installed omega v21 with Full swipe. After that I ended up stuck in boot animation. :s What to do? I already tried to re-flash modem and bootloader, updated CWM and tried to re-install that v21 and after that I flashed twrp over cwm and tried to re-install v21 but always I ended up stuck in that boot animation. :S All installs were successful, but it just wont boot.
What to do?
Hopefully you understand my problem.
Cheers from Finland!
Nico
EDIT:
Ok, I flashed omega rom v19 with full wipe and tried to boot. Didnt work, but then I installed Kies to my computer, opened Kies, Plugged USB in and started my phone and then Kaboom! It booted. What exactly happened there?
Click to expand...
Click to collapse
Hi, I am having the same problem. First I installed the new firmware (NA5) and modem, tested it with the Omega ROM v21 and boot caught on so now tested the rom Fox Hound 4.1 and am having the same problem.
Kies tested this option but have not had the same luck as you. = /
Anyone know the reason? The rom Google Edition Jamal runs on my phone.
i9505
Dear XDA Members
I have a Galaxy s4 GT-I9505 i had an old version of Omega Rom on my galaxy and everything was workin smooth. But i decided to flash a new rom and do a factory reset and delete all data then i flashed A modifyed stockrom with TWRP it was working fine until i restarted the phone and it stuck on the galaxy s4 Boot logo so i went to recovery and flashed it again with wipe/dalvik etc. I saw in TWRM the system was unmounted so i mounted it again. and flashed the same rom again. it was booting and after i was able to us the rom again until i restarted the phone and it stuck again
I then downloaded the Google stock rom for s4 and flashed it via TWRP after i could start the rom and could use it but when i restarted the phone it was stuck again on s4 boot logo. After dath i wiped and factory reseted many times and tried 3...4 other roms but i allways had the same problem.. i also tried an original stock rom via ODIN but this wont start at all. One thing i mentioned in TWRP under Mount it allways kiks out the System mount.
I tried to fix it for 8h now and cant find a way.. so i need Your help have you got any Idea what is wrong with my galaxy ?
thanks in afford
So, today i've tried to flas PAC on top of my omega 4.3 rom, after changing recovery and flashing this rom i noticed i had lost signal.. i decided to get back to omega but maybe changing recovery had deleted my backups, so i installed it from full wipe (only after many try, beacouse i didn't pass bootanimation) and now i still don't have 3g or any type of signal, any ideas?
no problem
noooooo said:
So, today i've tried to flas PAC on top of my omega 4.3 rom, after changing recovery and flashing this rom i noticed i had lost signal.. i decided to get back to omega but maybe changing recovery had deleted my backups, so i installed it from full wipe (only after many try, beacouse i didn't pass bootanimation) and now i still don't have 3g or any type of signal, any ideas?
Click to expand...
Click to collapse
Go to the phone setting and see your imei, if is is not what was before then you can do the following.
Getting no signals means you have corrupted imei.
If you previously haved saved any backup of efs flash it. It may solve your problem of no signals.
flash latest modem through odin.you can flash modem from your phone but flash it through pc.
Pc Odin*- open extracted file ".tar.(md5)" as*PHONE-
Phone Custom Recovery*- flash*modem.zip*from SDCard*
There is some problem with the recoveries that when you flash any aosp 4.3 rom you might not get boot animation this is normal.you can try twrp recovery you will get boot animation.Happened same with me.
alifarrukhsss said:
Go to the phone setting and see your imei, if is is not what was before then you can do the following.
Getting no signals means you have corrupted imei.
If you previously haved saved any backup of efs flash it. It may solve your problem of no signals.
flash latest modem through odin.you can flash modem from your phone but flash it through pc.
Pc Odin*- open extracted file ".tar.(md5)" as*PHONE-
Phone Custom Recovery*- flash*modem.zip*from SDCard*
There is some problem with the recoveries that when you flash any aosp 4.3 rom you might not get boot animation this is normal.you can try twrp recovery you will get boot animation.Happened same with me.
Click to expand...
Click to collapse
Yeah, i didn't check imei but falshing modem again solved my problem, thanks anyway, a lot
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Boot and recovery partitions
Sounds like you messed up boot and recovery sections. Since you can boot up successfully, you may try to flash back to ZUI which changes these two sections completely. If it's not a solution for you, I think the only way to repair is completely format including kernel, system and partitions. You can find the tutorial on Website.
...
you can fix it just use TOOL_ZUK_Z1_ENG_0.0.6
Try flashing COS 12.1 via fastboot.
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
Hi!! I've flashed the NucleaRom too and for a couple of weeks it worked just fine. However one day, out of nowhere, the phone, while still on and working, restarted itself and entered a bootloop. After a few days it restarted normally and lasted a couple of hours but then it all started again. The BIG issue here is that when the phone enters in this bootloop where it remains on for about 15 seconds, it does it either in the system or the recovery/fastboot. I've managed to install two other ROMs via TWRP, when it miraculously remained turned on, but the problem persisted.
Is there a chance your problem was similar? How did you manage to flash via QFIL? I can't enter into that "emergency" or "download mode" in order to flash.
Many thanks in advance
i think that the problem is in the bootloader itself you should try flashing the latest os u have used and instal ordinary unofical lineage nightly (you can find everywhere) by this way your bootloader will be updated to 7.1 after that you can install any software i was having same problem when trying to migrate to lineage os
unable to install Custom ROM's
hi ,,
even i had the same problem like recovery was not accepting any ROMS... if we flash it ll go to recovery again and again,
and later i have flashed CM 13 with image file,, it worked and gone to recovery and updated the update to lineage OS 14.1 with Gapps..
hope it might help u...
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
i am continuously on the boot loop! how to get rid of it?
plz help its been 4 hrs, i think i am in trouble! any possible solutions!!!!
U can try one thing.... Install cm13 with flash file and then restart - - & go to recovery select install update and select lineage 14 and G apps... I did like this . And it worked....