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 ?.
Related
I was trying to clean install Oxygen OS 4.0 onto my OnePlus 3. I did a huge mistake of formatting my entire data off of my OnePlus 3 using Wipe > Format Data > Yes in TWRP and now I cannot use my phone.
I don't know how to install the OS on the phone again and I am stuck. I don't even have a spare phone right now.
Can someone please help me? I tried checking the other forums, but they were confusing and I didn't understand anything. Please help me.
I tried downloading the software from OnePlus's website, but I couldn't install it through ADB cause the file is for some odd reason corrupt.
Please, somebody help me. I can't even send it back to OnePlus cause I am in a different country ATM.
I had trouble with OB10 and adb. Said it couldn't read the file. I instead flashed TWRP and enabled mtp from there. I then pushed the full ROM to internal storage. Fastboot flashed the stock recovery and used 'upgrade from internal'. That flashed it fine. Then I reinstalled TWRP and SuperSU.
yasinmys said:
I was trying to clean install Oxygen OS 4.0 onto my OnePlus 3. I did a huge mistake of formatting my entire data off of my OnePlus 3 using Wipe > Format Data > Yes in TWRP and now I cannot use my phone.
I don't know how to install the OS on the phone again and I am stuck. I don't even have a spare phone right now.
Can someone please help me? I tried checking the other forums, but they were confusing and I didn't understand anything. Please help me.
I tried downloading the software from OnePlus's website, but I couldn't install it through ADB cause the file is for some odd reason corrupt.
Please, somebody help me. I can't even send it back to OnePlus cause I am in a different country ATM.
Click to expand...
Click to collapse
Have you downloaded the full ROM? Make sure you download the full rom from oneplus's website or any of the mirrors available on various forums on xda. Flash it normally like you flash a custom rom. It will work as I have done it a lot of times. Your file must have been corrupt.
yasinmys said:
I was trying to clean install Oxygen OS 4.0 onto my OnePlus 3. I did a huge mistake of formatting my entire data off of my OnePlus 3 using Wipe > Format Data > Yes in TWRP and now I cannot use my phone.
I don't know how to install the OS on the phone again and I am stuck. I don't even have a spare phone right now.
Can someone please help me? I tried checking the other forums, but they were confusing and I didn't understand anything. Please help me.
I tried downloading the software from OnePlus's website, but I couldn't install it through ADB cause the file is for some odd reason corrupt.
Please, somebody help me. I can't even send it back to OnePlus cause I am in a different country ATM.
Click to expand...
Click to collapse
Go to: h*t*t*p*://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.8/ (REMOVE STARS) download both stock recovery and rom of OOS v3.2.8 (located at the bottom of the page). Flash stock recovery via fastboot (I hope you know how to). After it was flashed, disconnect the cable, turn off the device in fastboot (power off). Then hold power and volume down keys down to boot into recovery. From there ADB sideload the stock OOS v3.2.8. Let it boot up and update to OOS 4.0 via OTA.
P.s. If you need the actual steps, let me know. I'll update it in this post.
nine5raptor said:
I had trouble with OB10 and adb. Said it couldn't read the file. I instead flashed TWRP and enabled mtp from there. I then pushed the full ROM to internal storage. Fastboot flashed the stock recovery and used 'upgrade from internal'. That flashed it fine. Then I reinstalled TWRP and SuperSU.
Click to expand...
Click to collapse
I had an issue with custom twrp + Freedom OS v2.0 (OOS v4.0). No xposed, a lot of battery issues with performance and toggling settings issues too. So I decided to stick with Freedom OS 1.7 (OOS v3.2.8) until OnePlus fixes the issues, with xposed available for Nougat and official twrp being released to support Nougat. Also, whenever I flashed custom twrp, which was recommended by the dev, it always asked me for a password. I did have PIN code with fingerprint option, a pattern option or none at all. All of which did not help bypass it, even using "default_password". I was stuck with OOS v4.0, somehow, with no twrp to work with as it locked my data. I backed my files before flashing from OOS v3.2.8 to OOS v4.0, lucky me. I managed to do what I have explained in the first response.
So i got my pixel xl today from verizon and thankfully it was on 7.1 and not 7.1.1 however when i tried installing RR it kept going into a bootloop/twrp then back into a bootloop. I looked some stuff up and people say i need to flash a vendor img onto the device but I do not know how. Can anyone explain what the problem is, also I am having trouble because when i try to load into the os it says their is no os... Please help
stevieshae said:
So i got my pixel xl today from verizon and thankfully it was on 7.1 and not 7.1.1 however when i tried installing RR it kept going into a bootloop/twrp then back into a bootloop. I looked some stuff up and people say i need to flash a vendor img onto the device but I do not know how. Can anyone explain what the problem is, also I am having trouble because when i try to load into the os it says their is no os... Please help
Click to expand...
Click to collapse
Tell us the exact steps you used, step by step, and make sure to include full filenames of TWRP and RR, etc.
If you wipe /system before installing the ROM then TWRP will say there is no OS installed but you can bypass that because there is.
I suspect that's not your issue though.
I downloaded the Resurrection Remix ROM from the XDA forums straight off of the creators post I got TWRP from the TWRP website and downloaded the zip file and transferred both of them via USB to my phone. After transferring the files over to the phone and setting up TWRP so it would permanently stay on my phone. I installed Resurrection Remix then I installed TWRP and then I rebooted the system when I was installing Resurrection Remix I wipe the Dalvik and before that I did a factory reset through TWRP.
Hello all,
I recently tried to flash the latest LineageOS (lineage-14.1-20170717-nightly-crackling-signed), but without any luck (stuck in bootloader/recovery mode). I had no backup so I tried a bunch of old CM ROMs until I found a working one (an unofficial CM14 release found on cyanogenmods.org, can't post links yet).
Now I wonder why this particular ROM is the only one I can install.
So far the only difference I found is that it only targets armeabi-v7a and armeabi ABIs, and not arm64-v8a as the LOS ROM does.
So I checked with Droid Hardware Info and it tells me I have indeed an ARMv7 architecture.
But everything I read about the Swift tells me it's a 64 bits architecture.
Could someone tell me what I am missing here? Is it all normal or did I buy a fake Chinese copy of a Swift?
Thanks
Welcome. I doubt anyone would fake a swift. Most likely you didn't flashed a compatible fastboot image and baseband. Unlock your bootloader and fastboot flash https://www.androidfilehost.com/?fid=457095661767123627 then flash twrp 3.1.1.0. https://forum.xda-developers.com/wi...ent/recovery-unofficial-twrp-3-0-1-0-t3350351
Hello Dmitriy.WZR, thanks for the reply.
Indeed I don't really believe I have a bad phone It has to be something I did.
But so far I only flashed a recovery image (twrp-3.1.1-0-crackling), after unlocking the bootloader, as explained in the LineageOS wiki Install LineageOS on crackling. Then I installed LineageOS, GAPPS and the LineageOS addonsu. Then bootloop.
Not sure I know what is a "fastboot image and baseband".
thomas.gillet said:
Hello Dmitriy.WZR, thanks for the reply.
Indeed I don't really believe I have a bad phone It has to be something I did.
But so far I only flashed a recovery image (twrp-3.1.1-0-crackling), after unlocking the bootloader, as explained in the LineageOS wiki Install LineageOS on crackling. Then I installed LineageOS, GAPPS and the LineageOS addonsu. Then bootloop.
Not sure I know what is a "fastboot image and baseband".
Click to expand...
Click to collapse
Same happened to me a few months ago. The solution that worked for me was:
1. Remove the battery and reinsert it.
2.Go to recovery mode.
3.Wipe everything including internal storage.
4.Download a fresh copy of Lineage os and gapps and flash. Try avoiding su.
5.Reboot
Hello nsa02,
I did that several times and it didn't help. Did it again to be sure, but nothing new. Thanks anyway.
I hope I'll have better luck with @Dmitriy.WZR answer, I'll try to figure out what is this radio-20161215-crackling file and what I can do with it.
Ok, got it!
Seems I had an old bootloader (an ugly one with a terminal-like style and a big green START on the top), very different from the Cyanogen one.
Used radio-20161215-crackling file to flash my firmware (or bootloader, no sure what is what yet), as explain in the [RECOVERY][crackling] TWRP 3.1.1-0 [OFFICIAL] thread by @beroid.
Then latest LineageOS and GAPPS installed without problem (didn't try the su addon), and Droid Hardware Info tells me I have an arm64-v8a indeed!
Many thanks to @Dmitriy.WZR
thomas.gillet said:
Seems I had an old bootloader (an ugly one with a terminal-like style and a big green START on the top), very different from the Cyanogen one.
Click to expand...
Click to collapse
That's actually the newest one (the one, that come with Android 7-based firmwares). Sadly enough this one is incompatible with custom ROMs, so you need a cyanogen-besed bootloader, yes.
Glad you make it, wishing you a rock-stable working device
I have a little experience flashing roms but I'm far from an expert,
My Shield has had poor performance for over 2 yrs now and I thought I would give a new rom a try.
I've been trying to use Lineage OS 14.1, I think I followed the install guide but the tablet just stays on the boot animation of Lineage OS and has never booted past it. I'd post a link to the lineage os wiki but I'm new around here and the XDA forum won't let me.
I was running Nvidia's stock 5.4 rom until earlier today.
I was able to flash TWRP, 3.2.3-0 and it seems to be installed properly.
- it will flash roms and install zips etc.
I have good access to ADB, Fastboot, and recovery. I can access the Tablet through USB and transfer files from my Laptop. It's running ubuntu 16.04.
I just can't figure out what I've done wrong. Please can someone pass along some pointers?
Thanks
I was trying to update the OS on my Nexus 7 2013. I was able to connect it to my PC and unlock it and erase user data using adb commands. But after that it will not go past the Google logo in Recovery or regular Start mode. When I run "adb devices" it does not show up, though my computer does see it since I can run the lock/unlock adb commands and they work. I have uninstalled/reinstalled different adb drivers for the devices. I've tried using 2 different PCs. I can not get adb to fully recognize the device. I tried the Skipsoft Android Toolkit, and it too reports "no device detected".
Have I completed bricked the device? Or is there some way out of this that I haven't though of/found on the internet yet?
I hope someone here can help me!
Thanks!
Assuming you're on stock, try flashing a factory image from Google themselves. This reflashes everything, like stock OS, recovery, bootloader, etc. I'd choose the latest version found here: https://developers.google.com/android/images#razor As long as you understand that this wipes data, then give this a shot and let us know the results!
I found the "Nexus Root Toolkit" windows app. It was able to communicate with the Nexus 7 and restore the factory ROM and I could get it to boot! Now, I've tried about a dozen times to install LIneage, but it keeps getting an error the point of trying to install the ROM, and I haven't figured out what the error means or how to correct it. I've tried multiple TWRP versions and Lineage OS versions. It's driving me nuts!
adamwsh said:
I found the "Nexus Root Toolkit" windows app. It was able to communicate with the Nexus 7 and restore the factory ROM and I could get it to boot! Now, I've tried about a dozen times to install LIneage, but it keeps getting an error the point of trying to install the ROM, and I haven't figured out what the error means or how to correct it. I've tried multiple TWRP versions and Lineage OS versions. It's driving me nuts!
Click to expand...
Click to collapse
Are you trying to install the official version of 17.1? If so, you'll need to look at the install guide on the LineageOS website here: https://wiki.lineageos.org/devices/flox/install
As far as I can tell, you cannot use TWRP, or at least the official TWRP, with this image. You'll need to use the LOS 17.1 Recovery found on the downloads page. If you haven't already, you're going to need to repartition the device with the instructions found on the install guide that I linked.
If this isn't the ROM in question check out the thread for that ROM and see if anyone else has any issues with installation.
NTGDeveloper said:
Are you trying to install the official version of 17.1? If so, you'll need to look at the install guide on the LineageOS website here: https://wiki.lineageos.org/devices/flox/install
As far as I can tell, you cannot use TWRP, or at least the official TWRP, with this image. You'll need to use the LOS 17.1 Recovery found on the downloads page. If you haven't already, you're going to need to repartition the device with the instructions found on the install guide that I linked.
If this isn't the ROM in question check out the thread for that ROM and see if anyone else has any issues with installation.
Click to expand...
Click to collapse
Thank you! I did manage to get 18.1 to flash and load, after using a repartiion tool I found. However, I can't get GAspps to load, saying there isn't enough room on the partition. Now, I'm trying to use NRT to get back to stock (like I was able to do earlier) but now it is getting stuck at the Android 6 startup animation (4 round icons). I'm wondering if it is because I ran the partition update and somehow have to put that back to get the stock ROM to work.
The only suggestion that I would have is to flash the smallest GApps package possible, and before flashing LOS 18.1, wiping pretty much everything, then flashing LOS and GApps. Since OpenGApps doesn't make an Android 11 package yet, I don't know much about the other package providers, but that's all that I can think of. Hope this helps!
NTGDeveloper said:
The only suggestion that I would have is to flash the smallest GApps package possible, and before flashing LOS 18.1, wiping pretty much everything, then flashing LOS and GApps. Since OpenGApps doesn't make an Android 11 package yet, I don't know much about the other package providers, but that's all that I can think of. Hope this helps!
Click to expand...
Click to collapse
I wound up flashing Stock Android 5.0 and it worked. Now I'm updating to 6 via the software upgrade in the OS itself. I feel like this thing is just too old and not large enough memory to handle a custom OS.