I was trying to install Lineage OS on my Nextbit Robin. I have never done this before, which is why I messed it up. I install TWRP and unlocked my bootloader, but I did not put the Lineage OS ROM.zip file into my internal memory. Sideloading isn't working, and since Nextbit has been bought by Razer, the official stock ROMs don't work, etc. I need help in installing an OS (stock is fine). If you could also guide me through installing Lineage OS, that would also be appreciated.
Thanks!
Let me know if you need more info.
MyerFire said:
I was trying to install Lineage OS on my Nextbit Robin. I have never done this before, which is why I messed it up. I install TWRP and unlocked my bootloader, but I did not put the Lineage OS ROM.zip file into my internal memory. Sideloading isn't working, and since Nextbit has been bought by Razer, the official stock ROMs don't work, etc. I need help in installing an OS (stock is fine). If you could also guide me through installing Lineage OS, that would also be appreciated.
Thanks!
Let me know if you need more info.
Click to expand...
Click to collapse
Why do you use sideloading ?
Just boot into TWRP , go to mount and select enable MTP.
Then connect your phone to your PC and transfer the lineage os zip file ?.
This info is for people who are finding it difficult to install a custom ROM or who are just waiting for the right time to experiment. This method is fail-safe. Any support needed, I am here to help .
To start with:
I unlocked my RM5P bootloader was able to install custom recovery and even root my phone, but I was not able to install a custom ROM ----- till yesterday night (I am on EVO X now).
Failed attempts:
I was able to downgrade to RMX1971EX_11_OTA_0170 with stock recovery but after loading the ROM, I cannot load into FASTBOOT.. Again to get into fastboot, I needed to upgrade to CO1 (Android 10).
Then from fastboot mode, I tried installing ROM (very old version) thus maintaining the TWRP and Fastboot.
I tried to install custom ROM, it gave me error 7. This error is because the Firmware was too old for the custom ROM to be installed.
Success:
I then installed color os V 170 from TWRP (it can decrypt OZIP files-it will covert that to zip and install). Used just common sense, as all custom ROMs at present need color os (specifically version ...170), so after installing ROM using TWRP and staying in the recovery (because if I load ROM now, I will lose FB and TWRP), I Dirty Flashed (just to be on the safe side) custom ROM (EVO X) , and then format data (might still give you error, there is a workaround) and restart. That's it.
I am in Evolution X latest build.
ADVICE:
Whatever experiments you want to do on your mobile, do it while you are in WARRANTY (after confirming you have your service center nearby and working). If your phone ends up bricked (like me-before) get it fixed free of cost. BECOME A PRO WITHIN THE WARRANTY PERIOD.
Oh well that's extremely nice of you and useful. You're helping the community of this device a great deal with your informational and technical guides. I can safely thank you in the name of all users.
Though I'm feeling kind of sorry and bad for you. You really weren't able to use custom ROMs till 14th of May? Geez... That must've been horrible. I'm a fan of pure and stock like, simple, well modable/shapeable Android since I was a kid and got my Samsung Galaxy phone with Android 2.1 back in 2009. Since then I can't stand any limitation brought by Android skins like Miui or Color OS. I was on GSI ROM on the third day of having my Realme Q back in October of 2019. Not like warranty did count anything since there's no Realme in Hungary and it was an import device from AliExpress. So many testing and experience, lots of adventure. Can't even imagine what would I have done if I couldn't get rid of COS till now. Even the thought is maddening to me ? You've got my respect.
greenys' said:
Oh well that's extremely nice of you and useful. You're helping the community of this device a great deal with your informational and technical guides. I can safely thank you in the name of all users.
Though I'm feeling kind of sorry and bad for you. You really weren't able to use custom ROMs till 14th of May? Geez... That must've been horrible. I'm a fan of pure and stock like, simple, well modable/shapeable Android since I was a kid and got my Samsung Galaxy phone with Android 2.1 back in 2009. Since then I can't stand any limitation brought by Android skins like Miui or Color OS. I was on GSI ROM on the third day of having my Realme Q back in October of 2019. Not like warranty did count anything since there's no Realme in Hungary and it was an import device from AliExpress. So many testing and experience, lots of adventure. Can't even imagine what would I have done if I couldn't get rid of COS till now. Even the thought is maddening to me You've got my respect.
Click to expand...
Click to collapse
I appreciate your time and message.
I have only dared once in my lifetime to experiment on a tablet i bought online on the first day, that time i restored it with another rom, and even replaced that gadget after 2 days for another one because it didn't have multi touch, many years ago.
With realme, i was kind of scared to experiment till some months back and i even had to visit service centre thrice to restore. Now i have learned a bit on how we can BRICK our phone.
One important thing i learned is, STOCK rom is the best, and i am back on it.
Thank you.
jijojamie said:
I appreciate your time and message.
I have only dared once in my lifetime to experiment on a tablet i bought online on the first day, that time i restored it with another rom, and even replaced that gadget after 2 days for another one because it didn't have multi touch, many years ago.
With realme, i was kind of scared to experiment till some months back and i even had to visit service centre thrice to restore. Now i have learned a bit on how we can BRICK our phone.
One important thing i learned is, STOCK rom is the best, and i am back on it.
Thank you.
Click to expand...
Click to collapse
Ah I see! That's indeed a whole adventure. Thank you for sharing. It was worth reading
jijojamie said:
This info is for people who are finding it difficult to install a custom ROM or who are just waiting for the right time to experiment. This method is fail-safe. Any support needed, I am here to help .
To start with:
I unlocked my RM5P bootloader was able to install custom recovery and even root my phone, but I was not able to install a custom ROM ----- till yesterday night (I am on EVO X now).
Failed attempts:
I was able to downgrade to RMX1971EX_11_OTA_0170 with stock recovery but after loading the ROM, I cannot load into FASTBOOT.. Again to get into fastboot, I needed to upgrade to CO1 (Android 10).
Then from fastboot mode, I tried installing ROM (very old version) thus maintaining the TWRP and Fastboot.
I tried to install custom ROM, it gave me error 7. This error is because the Firmware was too old for the custom ROM to be installed.
Success:
I then installed color os V 170 from TWRP (it can decrypt OZIP files-it will covert that to zip and install). Used just common sense, as all custom ROMs at present need color os (specifically version ...170), so after installing ROM using TWRP and staying in the recovery (because if I load ROM now, I will lose FB and TWRP), I Dirty Flashed (just to be on the safe side) custom ROM (EVO X) , and then format data (might still give you error, there is a workaround) and restart. That's it.
I am in Evolution X latest build.
ADVICE:
Whatever experiments you want to do on your mobile, do it while you are in WARRANTY (after confirming you have your service center nearby and working). If your phone ends up bricked (like me-before) get it fixed free of cost. BECOME A PRO WITHIN THE WARRANTY PERIOD.
Click to expand...
Click to collapse
Can you guide me please , currently i am on realme ui c.04 latest update , wanna go back to color os ( for flashing custom roms ) how can i safely downgrade without loosing fastboot and custom recovery ( as of now bl is locked and everything is stock )
Here's the step i am thinking to follow
Unlocking bl and flashing twrp while in realme ui and from twrp flashing color os 6 zip file and and without booting , flashing the custom rom and then wipe data and then reboot
Will j have bootloader and recovery accessible then ?
grand2SD said:
Can you guide me please , currently i am on realme ui c.04 latest update , wanna go back to color os ( for flashing custom roms ) how can i safely downgrade without loosing fastboot and custom recovery ( as of now bl is locked and everything is stock )
Here's the step i am thinking to follow
Unlocking bl and flashing twrp while in realme ui and from twrp flashing color os 6 zip file and and without booting , flashing the custom rom and then wipe data and then reboot
Will j have bootloader and recovery accessible then ?
Click to expand...
Click to collapse
Correct. I had only twrp and no bootloader after installing custom ROM. Please avoid DIRTY FLASHING.
Gud luck.
jijojamie said:
Correct. I had only twrp and no bootloader after installing custom ROM. Please avoid DIRTY FLASHING.
Gud luck.
Click to expand...
Click to collapse
You saying avoid dirty flash then how to flash custom after color os ( assuming not booting into color os , staying in recovery )
Please help with steps after flashing color os through recovery
Andyou had no bootloader after custom rom , then how did you managed to get bootloader back
grand2SD said:
You saying avoid dirty flash then how to flash custom after color os ( assuming not booting into color os , staying in recovery )
Please help with steps after flashing color os through recovery
Andyou had no bootloader after custom rom , then how did you managed to get bootloader back
Click to expand...
Click to collapse
Avoid installing custom roms using duty flash, i mean the second custom rom should be done as clean install. I said that specifically because, i tried three roms in a span of 1 hour, the third duty flash (derpfest rom) gave me indefinite boot. Had to go to service centre because phone was not bootng to twrp.
I went back to custom rom, Android 10 to get BL back. Anyways, i was not that satisfied with the present custom roms available.
But that's me, you can go ahead and try roms.
jijojamie said:
Avoid installing custom roms using duty flash, i mean the second custom rom should be done as clean install. I said that specifically because, i tried three roms in a span of 1 hour, the third duty flash (derpfest rom) gave me indefinite boot. Had to go to service centre because phone was not bootng to twrp.
I went back to custom rom, Android 10 to get BL back. Anyways, i was not that satisfied with the present custom roms available.
But that's me, you can go ahead and try roms.
Click to expand...
Click to collapse
Thanks for help , but in any case , I don't wanna mess up to such extent that i have to go service center ,
Can scenario get that bad ?
I mean fastboot gone , twrp not booting up
Also you just flashed custom 10 rom from twrp n got bootloader
And one more thing i wanna try derpfest rom android 10 version
So please have a look at these steps
Color os zip flash by twrp , then wipe data without booting and flashing derpfest 10.0
How will that go , i mean will i have bootloader
grand2SD said:
Thanks for help , but in any case , I don't wanna mess up to such extent that i have to go service center ,
Can scenario get that bad ?
I mean fastboot gone , twrp not booting up
Also you just flashed custom 10 rom from twrp n got bootloader
And one more thing i wanna try derpfest rom android 10 version
So please have a look at these steps
Color os zip flash by twrp , then wipe data without booting and flashing derpfest 10.0
How will that go , i mean will i have bootloader
Click to expand...
Click to collapse
I suggest you check this with another derpfest user, please. I never got to boot to derpfest.
I downloaded Evolution X 4.7 Rom zip file and followed the instructions given in thread to flash zip file. But after flashing when I tried to reboot in system, it gave me a message on swipe screen that OS is not installed but still I swiped to boot in system. My device tried to boot a couple of time and ended up in fastboot again. Fortunately I had already made backup so I restored my backup.
As per your post I should have flashed color os 6 ozip file with twrp before flashing evox rom.
Every thing ok.i think you are not flash Vebeta after flash recovery.
Hello,
I can't install any custom ROM on my Samsung S9: once the ROM is installed and the /data, /cache etc. partitions are formatted, it goes back to the greenish download mode screen… But when I use the Windows /e/ installer (which apparently runs some additional scripts), I can successfully install the /e/ OS on my phone. There must be something I'm missing but I can't figure out what, can someone help me with this please?
Here's some context:
I bought this Samsung S9 from the /e/ phone store and I realized I can't run my bank app or any app that needs Google Apps, which is a problem for me. Therefore, I tried installing Lineage, Sakura, dotOS, etc. on my phone, but every time, after flashing and rebooting, I get back to this "Downloading… Do not turn off target" screen.
icoste said:
Hello,
I can't install any custom ROM on my Samsung S9: once the ROM is installed and the /data, /cache etc. partitions are formatted, it goes back to the greenish download mode screen… But when I use the Windows /e/ installer (which apparently runs some additional scripts), I can successfully install the /e/ OS on my phone. There must be something I'm missing but I can't figure out what, can someone help me with this please?
Here's some context:
I bought this Samsung S9 from the /e/ phone store and I realized I can't run my bank app or any app that needs Google Apps, which is a problem for me. Therefore, I tried installing Lineage, Sakura, dotOS, etc. on my phone, but every time, after flashing and rebooting, I get back to this "Downloading… Do not turn off target" screen.
Click to expand...
Click to collapse
They dont want you to install any roms on your e phone
hainguyenthao gave me a lot of help yesterday and I could install a stock rom using Odin This seems to have done the trick, since now I can install custom roms! I was apparently missing that intermediate step…
This is really a wonderful community!
Upgrading from 11.0.9.1(Android 11) to Android 12 using HD1901_11_F.22 update from system upgrades bricks my phone. I live in India and decided to upgrade my phone to Android 12 just to find my phone bricked after rebooting(a white screen flash/blink followed by black screen) and reverted back to oos 11 and did the install again but same result. Is there any way I can install oos 12. P.S I am currently using a oos 11 based custom rom and I had replaced my phone screen with an unoriginal one(because I broke my original screen) if that makes a difference
Model:HD1901
Variant:India
Can somebody help me please
My best guess is that you need to be completely stock OOS11 to properly update to OOS12.
You say that your on a custom ROM that's Andriod 11 and you want a stock Andriod 12.
Therefore, I suggest that it's possible that you must be on stock Andriod 11 to update to stock Andriod 12.
I think that their is incompatibilities between the custom and the stock ROM causing the bootloop issue.
Which would mean the fill wipe of device and loss of all data I would assume. So save a back up what's needed.
So search for the MSM TOOL which will restore your device to it's wiped/stock state (might be only Andriod 11 at this point - not sure is MSM for Andriod 12 is available). Full update from 11 to 12 at that point should work. (I always utilize the full rom update - not the incremental update but not sure if that even matters).
Bottom line is that stock and custom ROMs irrespective of the Andriod base usually involve a complete device wipe and reset when switching from what little I know.
But, I believe I've been able to point you in the correct direction.
wugga3 said:
My best guess is that you need to be completely stock OOS11 to properly update to OOS12.
You say that your on a custom ROM that's Andriod 11 and you want a stock Andriod 12.
Therefore, I suggest that it's possible that you must be on stock Andriod 11 to update to stock Andriod 12.
I think that their is incompatibilities between the custom and the stock ROM causing the bootloop issue.
Which would mean the fill wipe of device and loss of all data I would assume. So save a back up what's needed.
So search for the MSM TOOL which will restore your device to it's wiped/stock state (might be only Andriod 11 at this point - not sure is MSM for Andriod 12 is available). Full update from 11 to 12 at that point should work. (I always utilize the full rom update - not the incremental update but not sure if that even matters).
Bottom line is that stock and custom ROMs irrespective of the Andriod base usually involve a complete device wipe and reset when switching from what little I know.
But, I believe I've been able to point you in the correct direction.
Click to expand...
Click to collapse
I was on stock oos 11 11.0.9.1 when I updated my phone through the oos system updates
Arnavgr said:
. P.S I am currently using a oos 11 based custom rom and I had replaced my phone screen with an unoriginal one(because I broke my original screen) if that makes a difference
Model:HD1901
Variant:India
Click to expand...
Click to collapse