Develop Bugs

[Q] Bootloop with TWRP but not with Philz ??

Hello all,
I found a workaround to my issue but cannot get any explanations so i ask
Each time i install TWRP recovery, my phone is stuck in a bootloop : Note 2 logo, Teamwin logo and note 2 logo, etc etc...
To get my phone boots i need to flash Philz recovery via Odin and that's all...
little issue is that i prefer twrp recovery (for some options missing in philz) and planned to test DN3 rom and according to the FAQ, install via philz needs to format ext SD and i do not want to do this
i am under XXDMG1 Bootloader and this rom http://forum.xda-developers.com/showthread.php?t=2531989, yes it is a non wipe odex rom and yes i was to lazy to do a proper install so this one was good to test first leaks of 4.3 so yes i sometime experience some random reboots (that's why i wanted to test another rom) !
if i rememer well, issue with bootloop whan using twrp happened the first time i tested it when i attempted to root my phone with stock rom...
thank you in advance for answers or suggestions

tarassor said:
Hello all,
I found a workaround to my issue but cannot get any explanations so i ask
Each time i install TWRP recovery, my phone is stuck in a bootloop : Note 2 logo, Teamwin logo and note 2 logo, etc etc...
To get my phone boots i need to flash Philz recovery via Odin and that's all...
little issue is that i prefer twrp recovery (for some options missing in philz) and planned to test DN3 rom and according to the FAQ, install via philz needs to format ext SD and i do not want to do this
i am under XXDMG1 Bootloader and this rom http://forum.xda-developers.com/showthread.php?t=2531989, yes it is a non wipe odex rom and yes i was to lazy to do a proper install so this one was good to test first leaks of 4.3 so yes i sometime experience some random reboots (that's why i wanted to test another rom) !
if i rememer well, issue with bootloop whan using twrp happened the first time i tested it when i attempted to root my phone with stock rom...
thank you in advance for answers or suggestions
Click to expand...
Click to collapse
The FAQ never stated to wipe "ext SD card" ,it advised you wipe your internal/phone memory and what you can do is install the ROM via latest philz 6.25 or 6.26.0 let the ROM boot go through the set up screen and then you can switch recoveries to twrp ,and reboot.The phone shouldn't bootloop anymore

singhpratik87 said:
The FAQ never stated to wipe "ext SD card" ,it advised you wipe your internal/phone memory and what you can do is install the ROM via latest philz 6.25 or 6.26.0 let the ROM boot go through the set up screen and then you can switch recoveries to twrp ,and reboot.The phone shouldn't bootloop anymore
Click to expand...
Click to collapse
you are right, i did not read well, faq said :
5: Format Internal SDCard (in mounts and storage) and do Factory reset (I will install a new ROM option in PhilZ)
so i do not matter format internal sd caus i did a backup... i installed latest philz recovery, i may update boot loader XXDMG1 to MJ5 before flash DN3 ?

tarassor said:
you are right, i did not read well, faq said :
5: Format Internal SDCard (in mounts and storage) and do Factory reset (I will install a new ROM option in PhilZ)
so i do not matter format internal sd caus i did a backup... i installed latest philz recovery, i may update boot loader XXDMG1 to MJ5 before flash DN3 ?
Click to expand...
Click to collapse
Yes if you have any contents on your internal sd card make a back up and then wipe it clean using the options in philz, and after flashing your ROM upgrade to MJ5 bootloader for working wifi but let me tell you that none of the 4.3 Bootloaders would charge your phone when running 4.4.2 when turned off so if that's of importance to you ,you would want to upgrade to KitKat bootloader which is ND3 but it's knoxed meaning you cannot downgrade to 4.1.2 only 4.3 is possible plus warranty is void. I'll link you up with ND3 bootloader incase you decide to switch later but MJ5 is a must to have.
How to flash bootloader
MJ5 BL
ND3 BL

singhpratik87 said:
Yes if you have any contents on your internal sd card make a back up and then wipe it clean using the options in philz, and after flashing your ROM upgrade to MJ5 bootloader for working wifi but let me tell you that none of the 4.3 Bootloaders would charge your phone when running 4.4.2 when turned off so if that's of importance to you ,you would want to upgrade to KitKat bootloader which is ND3 but it's knoxed meaning you cannot downgrade to 4.1.2 only 4.3 is possible plus warranty is void. I'll link you up with ND3 bootloader incase you decide to switch later but MJ5 is a must to have.
How to flash bootloader
MJ5 BL
ND3 BL
Click to expand...
Click to collapse
Thank for helpfull advice, i just finish install rom and let the rom finish to boot i tried to connect to wifi and it connect without flash new bootloader.. maybbe it will go like previous rom, somtime switch wifi does not work and need to reboot, so let me go flash mj5 bootloader via Odin and restore some datas and apps
thank you again !

tarassor said:
Thank for helpfull advice, i just finish install rom and let the rom finish to boot i tried to connect to wifi and it connect without flash new bootloader.. maybbe it will go like previous rom, somtime switch wifi does not work and need to reboot, so let me go flash mj5 bootloader via Odin and restore some datas and apps
thank you again !
Click to expand...
Click to collapse
mj5 is a must for any ROM over 4.1.2 some people used the wifi patch from dr.ketan's thread but it seems the wifi patch is not enough when being on bootloader older than mj5 while running 4.4 ROM so mj5 is the minimum bootloader requirement to have properly working wifi connection and then upgrade to ND3 bootloader later if you feel the need.Enjoy the ROM

singhpratik87 said:
mj5 is a must for any ROM over 4.1.2 some people used the wifi patch from dr.ketan's thread but it seems the wifi patch is not enough when being on bootloader older than mj5 while running 4.4 ROM so mj5 is the minimum bootloader requirement to have properly working wifi connection and then upgrade to ND3 bootloader later if you feel the need.Enjoy the ROM
Click to expand...
Click to collapse
flashed mj5 but something went wrong, after flashing phone rebooted to recovery and after a reboot i got a message tells me that "firmware upgrade encountered an issue..." black screen with a phone and a screen and a yellow excllamation dot between
i installed this one :
BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar
found in the trhead, i dl your link and give another try
edit : same thing after reflash the bootloader, i am trying to flash rom again now...
edit 2 : it seems to boot after re-flash of entire rom (without wipe again, it is the same rom)

tarassor said:
flashed mj5 but something went wrong, after flashing phone rebooted to recovery and after a reboot i got a message tells me that "firmware upgrade encountered an issue..." black screen with a phone and a screen and a yellow excllamation dot between
i installed this one :
BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar
found in the trhead, i dl your link and give another try
edit : same thing after reflash the bootloader, i am trying to flash rom again now...
edit 2 : it seems to boot after re-flash of entire rom (without wipe again, it is the same rom)
Click to expand...
Click to collapse
I had that issue twice when i was flashing system fonts on my phone using philz recovery but luckily for me just pulling the battery out for sometime and restarting the font solved the issue. If you still get error try this Method if that fails then try this other Method One of them should help you out but let's pray reflashing the ROM again and properly flashing the BL again solves your issue.
---------- Post added at 08:59 PM ---------- Previous post was at 08:57 PM ----------
tarassor said:
flashed mj5 but something went wrong, after flashing phone rebooted to recovery and after a reboot i got a message tells me that "firmware upgrade encountered an issue..." black screen with a phone and a screen and a yellow excllamation dot between
i installed this one :
BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar
found in the trhead, i dl your link and give another try
edit : same thing after reflash the bootloader, i am trying to flash rom again now...
edit 2 : it seems to boot after re-flash of entire rom (without wipe again, it is the same rom)
Click to expand...
Click to collapse
Okay download phone info app for samsung from playstore and see which bootloader version you got.Make sure your root access is not lost

singhpratik87 said:
Okay download phone info app for samsung from playstore and see which bootloader version you got.Make sure your root access is not lost
Click to expand...
Click to collapse
that's what i did and bootloader is mj5 as well !
i installed super SU and a root checker app and device is rooted, so let's titanium restore some apps :laugh:

tarassor said:
that's what i did and bootloader is mj5 as well !
i installed super SU and a root checker app and device is rooted, so let's titanium restore some apps :laugh:
Click to expand...
Click to collapse
Have fun

singhpratik87 said:
Have fun
Click to expand...
Click to collapse
Thank you again for helping me

Help- stuck on TWRP after cm14 update

***SOLVED***
Hello, I had cm14 installed and I was trying to update it. after the update, the device always boots to recovery(TWRP).
I tried the full wipe and flash again the rom, again boot to recovery. what is the solution for it?

lsdream said:
Hello, I had cm14 installed and I was trying to update it. after the update, the device always boots to recovery(TWRP).
I tried the full wipe and flash again the rom, again boot to recovery. what is the solution for it?
Click to expand...
Click to collapse
what version of twrp are you running? do you have a nandroid backup that you could restore? sometimes the partitions can get messed up during an update. if nothing helps, just follow this unbrick guide which will revert your phone completely back to stock, with all the storage partitions intact.

3.0.2-1

lsdream said:
3.0.2-1
Click to expand...
Click to collapse
yeah, everyone's got that one, but there are many versions of it usually a number, like 3.0.2-1 (22) for example, and each one build for specific cases. except you got it from the official twrp web, then there shouldn't really be problems with cm14.1
what about nandroid? can you restore one?

do you have any idea how to boot it?

lsdream said:
do you have any idea how to boot it?
Click to expand...
Click to collapse
please use the quote function so i get a notification when you reply.
i do, right in my first post here is a link to an unbrick guide which will help you because clearly something in your phone's storage is messed up. just follow it and you'll be back at stock with a fully functional phone

bombaglad said:
please use the quote function so i get a notification when you reply.
i do, right in my first post here is a link to an unbrick guide which will help you because clearly something in your phone's storage is messed up. just follow it and you'll be back at stock with a fully functional phone
Click to expand...
Click to collapse
Thanks, I just flash the stock rom and it boot normally.

lsdream said:
Hello, I had cm14 installed and I was trying to update it. after the update, the device always boots to recovery(TWRP).
I tried the full wipe and flash again the rom, again boot to recovery. what is the solution for it?
Click to expand...
Click to collapse
I had the same situation. You get out of this by fastboot flashing cm recovery, booting to it, then flash twrp back in fastboot. I think the ota doesnt fully work with twrp.

Flash the modified twrp from the second post in this forum
http://forum.xda-developers.com/oneplus-3/how-to/rom-community-build-3-5-5-t3490939

Strange EFS/smth else error? (P1a42)

Flashed my phone and forgot to do the EFS backup, so now I'm stuck I don't even know what without any way of removing it. Can't flash any custom ROMs (which was the only purpose of flashing in the first place) because of it. Photo of the problem: https://forum.xda-developers.com/picture.php?albumid=14115&pictureid=55427

hgfweri said:
Flashed my phone and forgot to do the EFS backup, so now I'm stuck I don't even know what without any way of removing it. Can't flash any custom ROMs (which was the only purpose of flashing in the first place) because of it. Photo of the problem: https://forum.xda-developers.com/picture.php?albumid=14115&pictureid=55427
Click to expand...
Click to collapse
Flash newest 3.1.0.0 recovery by firelord.

Starchm said:
Flash newest 3.1.0.0 recovery by firelord.
Click to expand...
Click to collapse
Thank you! Works perfectly.

Hi, I flashed 3.1.0.0 TWRP and then AOSP ROM but now I have no SIM card detected. Any ideas?

ferchorama said:
Hi, I flashed 3.1.0.0 TWRP and then AOSP ROM but now I have no SIM card detected. Any ideas?
Click to expand...
Click to collapse
aosp rom? u mean aex los or rr or which? do u have baseband and imei?

Sorry, yes, it is AospExtended version v4.5-OFFICIAL, no baseband nor IMEIs.

ferchorama said:
Sorry, yes, it is Extended version v4.5-OFFICIAL, no baseband nor IMEIs.
Click to expand...
Click to collapse
U deleted your efs partition, go back to stock and if u have imei on stock then save it with qcn backup

Starchm said:
U deleted your efs partition, go back to stock and if u have imei on stock then save it with qcn backup
Click to expand...
Click to collapse
I did QFIL stock restore and got bootloop from static lenovo logo. I've done this quite a few times now. Is there a way to flash radio or something different?

ferchorama said:
I did QFIL stock restore and got bootloop from static lenovo logo. I've done this quite a few times now. Is there a way to flash radio or something different?
Click to expand...
Click to collapse
U can ask qcn backup from anyone and restore it.( I cant make it cuz no time) then change imei back to your.

ferchorama said:
I did QFIL stock restore and got bootloop from static lenovo logo. I've done this quite a few times now. Is there a way to flash radio or something different?
Click to expand...
Click to collapse
I think I saw a post about other flashing tool like MiFlash?

Starchm said:
U can ask qcn backup from anyone and restore it.( I cant make it cuz no time) then change imei back to your.
Click to expand...
Click to collapse
Thanks for your help, this is what I tried:
I flashed TWRP 3.1.0.0
Flashed AospExtended (No sim or baseband detected)
Rooted
Downloaded the qcn file lenovoP1c58.qcn
Tried with the qcn restore option in QFIL but now it seems there is an issue with the connection. I followed the steps:
adb shell
su
setprop sys.usb.config diag
Click to expand...
Click to collapse
I think I'm almost there but don't know what I'm missing, please help.

Updates fail to install

I have a Sprint Moto Z2F, BL unlocked, rooted running the stock ROM
I've tried to return back to stock, recovery and not rooted but bootloader is still unlocked and tried to take the update but it always fails to install. What am I doing wrong?

hello....Bueller, .Bueller

Well reading other threads, if you unlock your bootloader and root, then go back to stock you can't get OTA updates

TwoBuells said:
Well reading other threads, if you unlock your bootloader and root, then go back to stock you can't get OTA updates
Click to expand...
Click to collapse
From another post I read from @Uzephi just recently there are some users who have been able to return to stock and receive the updates but IIRC there is a certain procedure to follow for it to work. Search @Uzephi's post and you'll be able to find it.
Sent from my Moto Z2 Force using XDA Labs

To add to what @fast69mopar said, here is the thread you should check out.

thanks

Yes, follow that thread. I have never had an issue getting updates on my sprint variant.

Uzephi said:
Yes, follow that thread. I have never had an issue getting updates on my sprint variant.
Click to expand...
Click to collapse
I've tried three times, I'm not wiping or formatting data, mounting the right way or order, when I get some time I'll try again. phone is running fine now, I just have updates frozen now so the notifications don't bug me.
Flashall works great,
I fastboot boot the TWRP.img file
then boot into TWRP, flash the TWRP zip and Magisk zip files.
I get a " can't mount system error", I'm not sure what to have checked when I wipe after installing TWRP
I tried to install the TWRP 3.2.2.0 but could never get the phone to boot after installing twrp zip
TWRP 3.2.1.0 is the only TWRP I can get to install and boot.
I have something overwriiten or not installed correctly \
I have to do some more reading of these threads and see where I'm doing wrong.
this slot a and b is confusing, maybe I did something wrong there. ( I really have not done anything with slot a or b, just installed files like those slots are not there. maybe one of them is corrupt

I tried a few more times but still can't get the OTA update to install.
I put my phone in the fastboot mode
I run Flashall
Flashall does its thing then when I reboot I sign in to my Google account, the phone is activated to my carrier. I get a notification for the system update, then it fails.
I go back to fastboot, flash and setup TWRP then root and restore my data and I'm back to normal
after Flashall my phone is back to stock, I tried to let the OTA update install and it fails everytime.
Maybe I should try some different ROM's since its so easy to get back to stock if something goes wrong.

[solved] help!!!

I installed Lineage OS 17.1 and when I turn on my phone he asks me for a password but I've never had

FranGAMER321 said:
I installed Lineage OS 17.1 and when I turn on my phone he asks me for a password but I've never had
Click to expand...
Click to collapse
Funny, i had the same problem yesterday, was told i should wipe the decryption on the phone in twrp, i lost my IMEI and can't flash roms anymore, be carefull.

maserati2011 said:
Funny, i had the same problem yesterday, was told i should wipe the decryption on the phone in twrp, i lost my IMEI and can't flash roms anymore, be carefull.
Click to expand...
Click to collapse
In TWRP to skip the password requirement I touched cancel and touched wipe (without a custom wipe), and after doing so I made an error, but after trying a couple of hours later the same thing came out, until I tried 3 more times in a row and he left me, after that I could finally use LineageOS 17.1

maserati2011 said:
Funny, i had the same problem yesterday, was told i should wipe the decryption on the phone in twrp, i lost my IMEI and can't flash roms anymore, be carefull.
Click to expand...
Click to collapse
Your loss of imei had nothing to do with formatting data and more to do with flashing rom
Make sure you're on oero firmware & reflash that firmware fully via fastboot
Flash a custom rom that gives you imei (you will have to try them - try the oero twrp flashable stock rom too) and then back up efs so you can restore it if problem happens again
---------- Post added at 02:05 PM ---------- Previous post was at 02:03 PM ----------
FranGAMER321 said:
I installed Lineage OS 17.1 and when I turn on my phone he asks me for a password but I've never had
Click to expand...
Click to collapse
You need to format data
TWRP - wipe - format data (option on the right)
Reboot to recovery & flash rom again
Or in fastboot do
fastboot erase userdata
Either way backup anything on internal storage (pics docs music etc) first as this will be deleted

TheFixItMan said:
Your loss of imei had nothing to do with formatting data and more to do with flashing rom
Make sure you're on oero firmware & reflash that firmware fully via fastboot
Flash a custom rom that gives you imei (you will have to try them - try the oero twrp flashable stock rom too) and then back up efs so you can restore it if problem happens again
Click to expand...
Click to collapse
would you be kind enough to help me through it on messenger?

TheFixItMan said:
Your loss of imei had nothing to do with formatting data and more to do with flashing rom
Make sure you're on oero firmware & reflash that firmware fully via fastboot
Flash a custom rom that gives you imei (you will have to try them - try the oero twrp flashable stock rom too) and then back up efs so you can restore it if problem happens again
Click to expand...
Click to collapse
I managed to re flash the stock Oreo 8.1 firmware through Lenovo Moto Smart Assistant hoping to get the IMEI back and automatically re-lock the boot-loader but neither happened, still no IMEI and Boot-loader is still unlocked, what to do now?

maserati2011 said:
I managed to re flash the stock Oreo 8.1 firmware through Lenovo Moto Smart Assistant hoping to get the IMEI back and automatically re-lock the boot-loader but neither happened, still no IMEI and Boot-loader is still unlocked, what to do now?
Click to expand...
Click to collapse
If running
fastboot erase modemst1
fastboot erase modemst2
Doesn't bring your imei back like I said - try different custom roms (especially the last where imei worked)
Else you will need a motherboard replacement if you can't work out a way to restore it
And never re-lock the bootloader 'if you hard brick your device again due to ota update because the firmware you flashed was wrong you will never be able to re-flash the device

TheFixItMan said:
If running
fastboot erase modemst1
fastboot erase modemst2
Doesn't bring your imei back like I said - try different custom roms (especially the last where imei worked)
Else you will need a motherboard replacement if you can't work out a way to restore it
And never re-lock the bootloader 'if you hard brick your device again due to ota update because the firmware you flashed was wrong you will never be able to re-flash the device
Click to expand...
Click to collapse
So basically your advice is to find a stable custom rom where the IMEI shows and just stick with it correct?

maserati2011 said:
So basically your advice is to find a stable custom rom where the IMEI shows and just stick with it correct?
Click to expand...
Click to collapse
Please read my past responses carefully
I said once you have found a custom rom that gives you imei you can then back up efs partition using a 64bit twrp to restore it if you loose it in future (or using other roms)