Develop Bugs

Need some help

SOO, I may have broken my find 7a, I was running on DU 8.2 with LVM, decided it was time to switch the the DU lolipop build, so I did everything right, backed up all my apps, did a TWRP backup. DU loli doesn't support LVM, so I flashed the remove LVM zip, rebooted recovery, tried to install DU loli and it failed, restarted recovery, tried it again and it failed, decided I would try the remove LVM zip once more and flash loli again, no go. So then I decide that I'm not brave enough for lolipop and flash the Setup LVM zip and try to restore my backup, it fails on restoring data (over and over, even on my older backups). This isn't good, because I need my phone, so I download 2 more roms, DU 8.2 and Nameless lolipop, They install in probably under a second, but then don't boot with or without LVM. So then I decide that maybe If I flash Remove lvm, Wipe everything, then use Coldbirds method twice (unsplit then split) that might reset everything. That didn't work, neither did flashing nameless with coldbirds unified, I've been trying everything I can think of, and I'm at my wits end, I don't know what I'm on coldbirds wise, it's probably my 8 or 9th time using that tool today. I have fastboot working, and recovery working (Used twrp 2.8.0.1, 2.7.1.0 entropy, 2.x.x.x coldbirds). Is there a way to just reset everything back to stock? All my partitions and such? Would flashing Oppo recovery and a color OS rom do that? Is there anything else I can try? Thanks for any responses or advice
-e

[Solved]Nexus won't boot after ROM and other things

Hello guys, I've searched a little and didn't find any posts that could help me specifically for the Galaxy Nexus.
I've flashed my phone a long time ago and have been using Paranoid Android for probably over a year.
The problem is, my cellphone was really really slow. So I decided to try a new ROM and re-flash it. And So I did.
I've tried flashing this Full_Auto R11 kernel then the CyanogenMod 12 and finally GAPPS.
I was getting error status 6 on Clockwork mod on gapps, but eventually got around it. But it didn't install play store, I've tried manually adding but it didn't work.
So I went for another 5.0 ROM (I'm really interested in getting android 5.0). Wiped all the data, all the cache, installed everything and rebooted.
Bam! Infinite booting screen.
No, I didn't create a nandroid backup because I'm really dumb.
So, I need your help. What I want to do is to get my phone working again with a 5.0 ROM (if possible).
I can boot into ClockWork Recovery just fine, if that helps.
Thank you for the attention.

I would recommend to install latest full factory package from Google.
Then you will start with everything stock, so flash latest TWRP recovery via fastboot (CWM is no longer supported, so error 6 when installing new Lollipop Google Apps appears).
Then in TWRP, do a factory reset, wipe /cache and /system partitions.
Then you can install your Lollipop ROM (over ADB or by pushing ROM package to emulated sdcard).
After this, install latest Full_Auto kernel.
At the end, install Pico Google Apps.
You must install the Pico version, because our /system parition is too small to handle Lollipop with all Google Apps included.
This should work for you, and you will have fully working Lollipop on your Galaxy Nexus
P.S: If you intall the AOSP Lollipop ROM by @freshgiammi and you miss root access, install latest SuperSU flashable zip.

Thank you!
Thank you man!
I've ran into some troubles but managed to do everythings correctly =)
This post can be locked up now.
Thanks again for the reply, LamarrCZ!!

ANY custom recovery/rom kills IMEI/BASEBAND!!!!

Was on 4.4.2 stock NJ2...Odin'ed a custom recovery like TWRP...rebooted.....NO IMEI and BASEBAND. That's about as simple, yet complex it gets. Tried reverting back to stock recovery in Odin, only to find that NO IMEI and BASEBAND still shows up. THE ONLY way I've successfully kept the IMEI/BASEBAND....is by keeping everything stock, from recovery to rom. Why would this be? I've even tried restoring the EFS folder....to no avail!!!! I'M FRUSTRATED!!!! My end goal is to be able to flash a rom, use TWRP/CWM, and KEEP the IMEI/BASEBAND!!!
ANY HELP? ANYONE having the same issue or fix?
THANKS!!!!!!:good:

Possible fix...
Make sure you have not used device encryption on the rom prior to your desired rom...
If you have then a device full wipe script is needed to clean up the phone prior to flashing the new rom...
(don't forget to check your SD card for encryption or data files that may be affected)...
Flash TWRP version 2.8.6.0 and flash your new rom....
Higher TWRP versions have been buggy for me...
Best I've got atm....g

It's because you are using TWRP 3.0.0.1, that one is broken

How backup current android 7 rom and install new android 10 rom?

Hi, I need your help to backup my current ROM and to update to some Android 10 custom ROM.
I am currently on a very old OOS based custom ROM with a rooted android version 7.1.1 (encrypted) and TWRP 3.2.1-0.
From what I remember, this TWRP version I have is bugged so that I cannot restore backups with it. However, since everything worked in the last years I didn't touch anything.
So, I want to..
1. backup my whole system and
2. install new custom ROM
Can someone tell me the steps I have to do?
I guess I have to..
1. Flash new TWRP (which one?)
2. Backup my partitions (does this work with a new TWRP for Android 7? Or would I need to use an older version?)
3. Install recent OOS firmware (which one and how? just flash it in TWRP?)
4. Wipe cache and data
5. Install new custom ROM
6. Install Magisk
7. Install Xposed
Is this correct?

I recently did the same thing. Your steps are correct, although I would add a couple more.
TWRP backup, TIBU backup, SMS backup, Then move all of those backups to your computer. Plus any contents of [Download, Documents, Pictures, Videos, DCIM, etc. ]
Download OOS from here, https://www.oneplus.com/support/softwareupgrade/details?code=PM1574156155944
This will completely reset you to factory. so you will need to set up the phone just enough to get developer mode on*, enable ADB*, & Unlock Bl
** I forgot this part and tried going to fastboot and directly flashing TWRP and got strange errors bc ADB wasn't enabled.
> Flashboot install recovery TWRP
Then I struggled with a few ROMS, but finally got CR Droid to install.
I flashed each file listed here, https://forum.xda-developers.com/oneplus-5t/development/rom-crdroid-android-6-t3972533

Hey there, thanks so far.
But would you install newest TWRP first before backing up, right? Or Will the newest version of TWRP not work anymore with android 7.1.1?
And do you use normal TWRP or Bluspark version?
Edit: I think I would prefer to just install the OOS firmware because I don't have a windows system anymore so I can't do the ADB stuff via command line. Or I guess I would have to setup a VM with windows installed.. O_x

Simplest way to get back to stock

I know there are several threads that will show me how to get back to stock but theyre all at least a few years old. Currently my 5T is running a custom rom based on Android 11 with TWRP bluspark 3.3.1x. Can I just put a full stock zip on my sdcard and flash it in Twrp? Then by via adb or twrp, flash the stock recovery?
My main concern is getting stuck in a place it's hard to recover from. Based on my reading (and from memory) I believe the above will work but I'm not sure which recovery to flash nor am I certain which rom because its been updated. I don't believe I can flash an android 10 rom or recovery to it at this time. That would be for me the simplest solution. Once I get it back to stock I can just do the OTA updates.
The phone isn't for me. I'm giving it to a kid who needs it currently and the rom it's currently running has terrible battery drain. Any help would be greatly appreciated. Thanks

I had heavily modified my phone where my sdcard(internal storage) itself was not getting recognised and has tried custom os like Ubuntu touch and sailfish OS installed. But recently flashed OOS 10.0.1 back on my oneplus5t device. What I did was to wipe partition system, data, cache/dalvik and format data. Then I flashed the rom. When the device started. I did a factory reset again. This worked for me.