Develop Bugs

Bootloop after installing a rom.. please help!

So I've installed a JBesque 4.0.3 ROM via the x-tools CWD recovery. I did the system wipe and everything then iknstalled the rom, and all I get is the sony loop screen..I can't seem to get into recovery
L15i
bootloader locked
is there a way to solve the loop problem? How could I reflash?
Please help

Did you flash an kernel specified for the rom?
just flash an 4.0.3 firmware
next time do this when flashing an ROM
1. wipe data / factory reset
2. wipe cache partition
3. wipe dalvik cache
4. install from .zip (rom)
and you say you have a locked bootloader, you might wanna check if the rom requires an unlocked bootloader

MrModMan said:
Did you flash an kernel specified for the rom?
just flash an 4.0.3 firmware
next time do this when flashing an ROM
1. wipe data / factory reset
2. wipe cache partition
3. wipe dalvik cache
4. install from .zip (rom)
and you say you have a locked bootloader, you might wanna check if the rom requires an unlocked bootloader
Click to expand...
Click to collapse
no, i accidently forgot to flash the kernel acrually, lol.
would you mind telling me how to flash the firmware? I tried via flashtool but it didnt work..

First of all,switch off your mobile and press back button then connecting the usb cable..Now your mobile should connect in flash mode by which you can flash any firmwares using flashtool!
Cheers!

Don't forget - you need to unlock bootloader if you want to install custom kernel.

Cannot install 4.0.2 update

I was using 4.0.0 stock with twrp and root. Tried to install the 4.0.2 update but every boot just took me back to recovery. Tried wiping clean, no change. Tried installing stock recovery v2.0, recovery would hang. Tried using new twrp 3.0.3 and I could get back in, but any ROM, stock or not I installed, would not stick.. Even twrp would warn me "no os installed. reboot anyway?" even when I had just installed a ROM. So in the end I flashed OOS 3.2.8 with twrp and then flashed stock recovery. At this point I'm pretty much at factory stock at v3.2.8 with stock recovery v1.0. Now I'm trying to update to 4.0.2 via OTA and for the 3rd time already I have received a installation failed message and rebooted to system. The first time I thought it was because I disconnected VPN after starting the download, so I downloaded a second and a third time. I don't want to resort to sideloading again because I fear I might get the same no OS installed problem I got when I tried to install 4.0.2 in the first place. Does anyone have any insight on what is wrong?

Steps:
1. Install latest Official or Modified TWRP ( 3.0.3/ 3.0.3 version 14 by eng.stk)
2. Enter into recovery. Connect phone to PC and copy downloaded ROM file.
3. Wipe everything in the recovery- Data, System, cache and Dalvic. It will erase everything.
4. Flash ROM zip after completing, don't reboot phone. Reboot to recovery again, and then reboot phone.
If u reboot phone directly after flashing ROM, u will loose TWRP.

Even twrp would warn me "no os installed. reboot anyway?" even when I had just installed a ROM.
Click to expand...
Click to collapse
This is pretty normal for nougat OOS. I've faced it for all 3 ROMs i flashed. Don't worry, your ROM was flashed successfully. You can mount and check the /system partition, you can see your ROM files there.
So here's what worked for me. (considering you are on ext4 /data)
1. Flash latest official twrp recovert ext4 version or use the file system swapper zip if it doesn't decrypt your data in recovery. TWRP has some issues as of now and mounts f2fs as default, so you just need to flash the file system swapper zip in order to swap it to ext4 by default.
2. Wipe /system /cache and dalvik cache.
3. Flash full 4.0.2 ROM zip, should be 1.4 GB in size.
4. Flash TWRP image again just in case.
5. Reboot to recovery, not to system.
6. Flash stable 2.79 Super Su and you are good to go.

Thanks for the tip, however I don't mind losing twrp, I only want to get stock unaltered update and this procedure does not help in this

IonAphis said:
Thanks for the tip, however I don't mind losing twrp, I only want to get stock unaltered update and this procedure does not help in this
Click to expand...
Click to collapse
Have you tried this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
P.S. I think you did, but I'm just asking.

Thanks for the tip, but I fixed it. Ended up flashing v3.2.8 via twrp and installed OTA to 4.0.1 via sideload. Recovery would not boot unless first fully booted into the system. After that sideloaded 4.0.2 via OTA and now back to complete stock.
Thanks guys!

Update from 3.2.7 to 4.1

Hey guys. I am still on marshmallow on my op3. I am rooted and have twrp recovery. My question is what firmware/modem do I need to flash before I update to latest Nougat update and if my steps below are correct.
I would prefer not to do a clean install.
My steps would be:
Download full rom
Flash any firmware if required - this is what I need to know
Flash Magisk as I need root
Profit?

cd69 said:
Hey guys. I am still on marshmallow on my op3. I am rooted and have twrp recovery. My question is what firmware/modem do I need to flash before I update to latest Nougat update and if my steps below are correct.
I would prefer not to do a clean install.
My steps would be:
Download full rom
Flash any firmware if required - this is what I need to know
Flash Magisk as I need root
Profit?
Click to expand...
Click to collapse
this is stock rom, you don't need to flash any firmware...
if you're coming from MM, i would recommend sideloading the rom, wipe everything, then go back to stock recovery then sideload then before 1st boot fastboot TWRP again, then reboot to TWRP and flash Magisk...Profit.
if you want to flash from TWRP without going through this (which i don't recommend), make sure in TWRP to format data as f2fs, wipe everything then flash the rom, and then form TWRP flash TWRP again, then reboot to recovery (not system), then flash Magisk.

theduke7 said:
this is stock rom, you don't need to flash any firmware...
if you're coming from MM, i would recommend sideloading the rom, wipe everything, then go back to stock recovery then sideload then before 1st boot fastboot TWRP again, then reboot to TWRP and flash Magisk...Profit.
if you want to flash from TWRP without going through this (which i don't recommend), make sure in TWRP to format data as f2fs, wipe everything then flash the rom, and then form TWRP flash TWRP again, then reboot to recovery (not system), then flash Magisk.
Click to expand...
Click to collapse
Thanks a ton for replying. Another question for you. I get the OTA notification. I could just let that run and flash twrp after the installation right.

cd69 said:
Thanks a ton for replying. Another question for you. I get the OTA notification. I could just let that run and flash twrp after the installation right.
Click to expand...
Click to collapse
if you're already rooted it wont install..and you can't flash the small ota file from TWRP, you have to flash the Full rom (1.4 GB)...
how you download is up to you, but why download from the update when there's many links available around !

Thanks for all the help. I flashed the new update successfully.

cd69 said:
Thanks for all the help. I flashed the new update successfully.
Click to expand...
Click to collapse
what steps did you follow ? did you have to wipe internal memory fully ?

netcitizen said:
what steps did you follow ? did you have to wipe internal memory fully ?
Click to expand...
Click to collapse
I just flashed the full Rom with Magisk. Wiped dalvick cache and nothing else. So far so goos.

cd69 said:
I just flashed the full Rom with Magisk. Wiped dalvick cache and nothing else. So far so goos.
Click to expand...
Click to collapse
Oh ok. I just flashed full rom via twrp after wiping cache and Dalvik cache.it updated fine. I wasn't sure of magisk.

The terrible fate of refurbished N5X

Hi,
My Nexus 5X died some days ago, and Google shiped me another one. But this new device have the unbelievable "NO RPMB" message that locks the bootloader (this is a known issue where the bootloader is automatically re-locked after each reboot, making flashing factory images an harassing journey).
I installed TWRP to flash a custom rom but after each reboot on the system,TWRP was replaced by stock recovery !
Do anyone knows how resolve this problem ? I suppose if I can flash a custom rom it will solve a great part of the problem... I'm actually thinking of sell this new phone and get another device like oneplus.
Any help will be appreciated ! ?

Atok_fr said:
Hi,
My Nexus 5X died some days ago, and Google shiped me another one. But this new device have the unbelievable "NO RPMB" message that locks the bootloader (this is a known issue where the bootloader is automatically re-locked after each reboot, making flashing factory images an harassing journey).
I installed TWRP to flash a custom rom but after each reboot on the system,TWRP was replaced by stock recovery !
Do anyone knows how resolve this problem ? I suppose if I can flash a custom rom it will solve a great part of the problem... I'm actually thinking of sell this new phone and get another device like oneplus.
Any help will be appreciated !
Click to expand...
Click to collapse
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.

CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Thanks mate, it worked !

CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Quick question. As I just picked up a refurb N5X on the cheap and I plan to use it (fingers crossed it does have RPMB, not holding my breath though)- how viable are custom ROMs on this thing? The reddit thread that started this all states to leave /system unmodified but other comments say that they've flashed custom kernels.
So- if this is the case, would the order be unlock bootloader>flash stock images/noencrypt>flash TWRP>boot into TWRP> factory reset> boot into Oreo> unlock bootloader and boot into TWRP when modifications need to be made?
Thanks.

negusp said:
Quick question. As I just picked up a refurb N5X on the cheap and I plan to use it (fingers crossed it does have RPMB, not holding my breath though)- how viable are custom ROMs on this thing? The reddit thread that started this all states to leave /system unmodified but other comments say that they've flashed custom kernels.
So- if this is the case, would the order be unlock bootloader>flash stock images/noencrypt>flash TWRP>boot into TWRP> factory reset> boot into Oreo> unlock bootloader and boot into TWRP when modifications need to be made?
Thanks.
Click to expand...
Click to collapse
I use a custom kernel so that works just fine, haven't tried a custom ROM though. You don't have to unlock the bootloader every time to make changes as long as you have TWRP. I'm not entirely sure but I think rooting made the TWRP stick. If not, you can still install it from the TWRP app as you have root.
After you've installed the stock images, it should be enough to boot into TWRP, do a factory reset and flash the custom ROM.

CazeW said:
I use a custom kernel so that works just fine, haven't tried a custom ROM though. You don't have to unlock the bootloader every time to make changes as long as you have TWRP. I'm not entirely sure but I think rooting made the TWRP stick. If not, you can still install it from the TWRP app as you have root.
After you've installed the stock images, it should be enough to boot into TWRP, do a factory reset and flash the custom ROM.
Click to expand...
Click to collapse
So once TWRP is installed and "stuck", it can make modifications to traditionally "root" partitions (system, data, etc.?).
Also, did you flash the noforce encrypt boot image (and then wiping userdata)? Or does the stock image work?

negusp said:
So once TWRP is installed and "stuck", it can make modifications to traditionally "root" partitions (system, data, etc.?).
Also, did you flash the noforce encrypt boot image (and then wiping userdata)? Or does the stock image work?
Click to expand...
Click to collapse
Yes. I've for example installed all the OTAs from TWRP (except Oreo).
Stock image works.

CazeW said:
Yes. I've for example installed all the OTAs from TWRP (except Oreo).
Stock image works.
Click to expand...
Click to collapse
Thanks. Does DRM content work? I've also read conflicting reports as to apps like Netflix working on Oreo.

negusp said:
Thanks. Does DRM content work? I've also read conflicting reports as to apps like Netflix working on Oreo.
Click to expand...
Click to collapse
I don't use Netflix so can't say if that works but Play Movies worked on Nougat.

CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Hello, i have the same NO RPMB problem Im using latest stock rom 8.1 (December patch), radio, bootloader and vendor.
How can i boot straight into recovery without rebooting? Do i need to flash vendor.img too? (i would like flash latest AEX rom).
If im not wrong i should do this procedure as suggested right?
- unlock bootloader from fastboot
- flash latest twrp recovery from fastboot without rebooting (this will work? Because in the N5X root thread it's written to reboot first)
- get into twrp without rebooting (how do that?)
- install root (i will use latest Magisk)
- perform factory reset
- wipe system, data, cache, and dalvik cache
- install custom rom, gapps...
- wipe cache and dalvik, and reboot
Finally i will have a rooted device with custom rom and bootloader locked again right?
Or is preferred this solution of Reddit user?
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader

sigibian said:
Hello, i have the same NO RPMB problem Im using latest stock rom 8.1 (December patch), radio, bootloader and vendor.
How can i boot straight into recovery without rebooting? Do i need to flash vendor.img too? (i would like flash latest AEX rom).
If im not wrong i should do this procedure as suggested right?
- unlock bootloader from fastboot
- flash latest twrp recovery from fastboot without rebooting (this will work? Because in the N5X root thread it's written to reboot first)
- get into twrp without rebooting (how do that?)
- install root (i will use latest Magisk)
- perform factory reset
- wipe system, data, cache, and dalvik cache
- install custom rom, gapps...
- wipe cache and dalvik, and reboot
Finally i will have a rooted device with custom rom and bootloader locked again right?
Or is preferred this solution of Reddit user?
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader
Click to expand...
Click to collapse
I haven't tried this with a custom ROM but I would try it like this.
- Unlock bootloader from fastboot
- Flash TWRP from fastboot
- Select boot to recovery from the fastboot menu
- Do a factory reset
- Wipe system, cache, and dalvik cache
- Flash ROM, flash Gapps
- Flash Magisk
- Reboot

I cant install any custom rom on my P2

I unlocked the boot loader & installed TWRP
I tried to install official Lienage 7.1.2 after flashing & wipe cache then restarting screen went black with long vibration & blue notification led
the other 8.1 roms the TWRP Stopes when flashing after saying flashing img
may anyone tell me the problem

Arafa1994 said:
I unlocked the boot loader & installed TWRP
I tried to install official Lienage 7.1.2 after flashing & wipe cache then restarting screen went black with long vibration & blue notification led
the other 8.1 roms the TWRP Stopes when flashing after saying flashing img
may anyone tell me the problem
Click to expand...
Click to collapse
Flash twrp via fastboot.
Boot to twrp via
Fastboot boot twrp.img
Replace "twrp" with the file name of your twrp.
Once twrp booted, go into reboot menu. And reboot to recovery again. That will make your phone boot again into twrp, but this time with more rights.
Go into wipe. Advanced wipe
Change data partition file system to ext4.
Reboot again into twrp via the reboot menu ,just like before.
Now go into wipe again, and format system,data,dalvik and cache.
Flash your rom.
Flash gapps (if not otherwise stated by ROM thread)
Flash Magisk (optional, if you want root)
Wipe dalvik and cache.
Reboot. And enjoy
Sent from my Lenovo P2a42 using XDA Labs

sm00th4f3 said:
Flash twrp via fastboot.
Boot to twrp via
Fastboot boot twrp.img
Replace "twrp" with the file name of your twrp.
Once twrp booted, go into reboot menu. And reboot to recovery again. That will make your phone boot again into twrp, but this time with more rights.
Go into wipe. Advanced wipe
Change data partition file system to ext4.
Reboot again into twrp via the reboot menu ,just like before.
Now go into wipe again, and format system,data,dalvik and cache.
Flash your rom.
Flash gapps (if not otherwise stated by ROM thread)
Flash Magisk (optional, if you want root)
Wipe dalvik and cache.
Reboot. And enjoy
Click to expand...
Click to collapse
Thx alot
But I have one more question
Should the bootloader to be marshmallow or nougat?

Arafa1994 said:
Thx alot
But I have one more question
Should the bootloader to be marshmallow or nougat?
Click to expand...
Click to collapse
What do you mean The bootloader is the bootloader.

Danoz88 said:
What do you mean The bootloader is the bootloader.
Click to expand...
Click to collapse
In my moto Z Play some roms needs Nougat bootloader like xperince

So Iam asking If some roms needs nougat bootloader in Lenovo P2

Arafa1994 said:
So Iam asking If some roms needs nougat bootloader in Lenovo P2
Click to expand...
Click to collapse
We only have one bootloader.
We have different firmwares though like nougat and marshmallow.
You will need Firmwares S244 for nougat ROMs.
That firmware must be flashed through ota. Stockrom-feature. Simply using twrp does not count as doing otas.
Basic starter things: Have Firmware S244 or S251 installed through stock ota feature.
Then use my earlier stated instructions.

Thx alot it worked & no problems