Develop Bugs

AOSP roms will NOT run! Driving me crazy...

So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?

I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app

iamdofus said:
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.

Do you by chance have a refurbished s2?

The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?

es0tericcha0s said:
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
Click to expand...
Click to collapse
OK thanks for reply, I have one more solution give me. Some time I will give try that it worked for me.
Sent from my SGH-T989 using XDA Premium 4 mobile app

es0tericcha0s said:
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Click to expand...
Click to collapse
ok lets stat it with this
1) download both the scripts of infamous wipe cache and infamous super wipe.
2) format your both SD card with PC (FAT32)
2) put both these wipe files and and your rom file ( i prefer try slimbean rom first)
3) Now in twrp 2.6.0.0- follow the steps
i) format your phone with twrp options
ii) again format your phone with infamous super file. (by going in to INSTALL ZIP file option in TWRP)
iii) than format with infamouse cache file (by going in to INSTALL ZIP file option in TWRP)
iv) install your rom and compatiable GAPPS zip file.
v) after installing or somewhere between procedure if twrp says something about supersu birnaries are not correct than click on DO . NOT FIX
vi) again format infamouse cache wipe.
vii) now FINALLY reboot the rom.
it should work, and it worked for me. if u sucessfully run the rom than you can eailsy run all the AOSP roms in this forum. Again If you try this please do tell me what happend.

Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!

es0tericcha0s said:
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
Click to expand...
Click to collapse
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?

UltimaniumX said:
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
Click to expand...
Click to collapse
Yep, very much phone specific. Used same recovery, same rom zip and gapps off the same external SD card, to be certain. That one updated just like every other S2 I've done. And it's the Tmo version. The At&t models are i777 S2 or i727 S2 Skyrocket. The i9100 is international and has a physical home button. But the phone was not modified at all. No root, custom recovery, etc. I was only able to resolve it by first starting with an AOSP 4.1.2 rom and working my way up to 4.4. One of the weirder issues I've come across.

es0tericcha0s said:
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
Click to expand...
Click to collapse
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?

tpag02 said:
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
Click to expand...
Click to collapse
Sorry, I don't pay attention to the notifications on XDA very often. I don't usually browse the S2 forums unless needed because I have an N5, but anyway... The 4.1.2 rom you used, was it TW or AOSP type? I used 2.6.0 to wipe everything, then used cache and superwipe zips then 4.1.2 AOSP type rom then cache wipe zip again then after that booted, I was able to go back to 2.6.1 and flash a 4.3 via wiping, wipe zips, installing rom then cache wipe again. After that, repeated with a KK rom and now it loads roms just like it should. If you want more precise help, feel free to hit me up on Hangouts with my username: es0tericcha0s. Good luck! I know how frustrating it can be when it gets a little out of whack like this...

I'm in the same boat
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.

DennyTek said:
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
Click to expand...
Click to collapse
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?

TMO 4.1.2
es0tericcha0s said:
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
Click to expand...
Click to collapse
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/

Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk

yep
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
ya, well at least I am anyways

wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I had tried with and without and did not make any difference.

DennyTek said:
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Click to expand...
Click to collapse
I just started working on a VZW S3 on T-Mobile service that has this issue. Happens on stock VZW 4.1.2, stock T-Mobile 4.1.2 rom, custom 4.1.2 T-Mobile rom, and stable CM 10.2. Weirdest thing... full wipes including /system inbetween each flash. Changed the modem too. Nothing helps. Pretty sure it's a bad board at this stage.

Cool beans, 0! Having this exact problem, will try your method for my s2, btw which aosp 4.1.2 did u use? Can I get a link? Thanks been having the problem for a few months now and just gave up haha, been super thirsty for that beanstalk kk build
One last thing can u also provide a link to the 4.3 that u used? I really want it to work and want to follow what u did to the , megabyte

[Q] Fingerprint scanner gone and keyboard lag so bad its painful (Developer Edition)

So I took all precautions and still ended up with an unresponsive fingerprint scanner do to I'm assuming a ROM flash. Damn. Wiped everything and restored stock backup to no avail. Losing the scanner stinks but what's worse is now I'm experiencing huge lag on stock keyboard and even Google keyboard along with occasional lag throughout the system. Anyone know how to remedy this?

dirtyjersey856 said:
So I took all precautions and still ended up with an unresponsive fingerprint scanner do to I'm assuming a ROM flash. Damn. Wiped everything and restored stock backup to no avail. Losing the scanner stinks but what's worse is now I'm experiencing huge lag on stock keyboard and even Google keyboard along with occasional lag throughout the system. Anyone know how to remedy this?
Click to expand...
Click to collapse
Out of curiosity what ROM did you flash?
Here is a recommendations: Power off the phone, enter TWRP, wipe cache, wipe data, wipe delvik, do a factory reset and flash your backup. Power off the phone, pull battery and let it sit for about 30 seconds. Put the battery back in and boot. See if that works.

jpcalhoun said:
Out of curiosity what ROM did you flash?
Here is a recommendations: Power off the phone, enter TWRP, wipe cache, wipe data, wipe delvik, do a factory reset and flash your backup. Power off the phone, pull battery and let it sit for about 30 seconds. Put the battery back in and boot. See if that works.
Click to expand...
Click to collapse
I initially flashed Definitive 1.1 since I'm still on old stuff but that was fine..then I tried flashing an unofficial CM12 that I got to boot up but no data even with Verizon Rils. But I think what killed it was Infamous for n910t. After that it was unresponsive with error dialogue box pop-up. I'll try the exact method you mentioned and respond back. I have completely wiped and restored stock through twrp but no Odin yet since my friends WiFi connection is ridiculous at like 150kbps.

No luck. Tried it 3 times.

dirtyjersey856 said:
No luck. Tried it 3 times.
Click to expand...
Click to collapse
If I remember correctly CM has its own kernel. Try flashing the stock Note 4 kernel. You can find the stock kernel in the firmware thread under Android Development.
Sent from my SM-N910V using Tapatalk

jpcalhoun said:
If I remember correctly CM has its own kernel. Try flashing the stock Note 4 kernel. You can find the stock kernel in the firmware thread under Android Development.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
I'm on stock kernel as we speak.

If all else fails, you can flash stock system, modem and kernel found in the Android Development section. That gives you a clean start. Then ODIN TWRP and flash SuperSU. If you do that just make sure you use the files designated for the Developer Edition.
Sent from my SM-N910V using Tapatalk

jpcalhoun said:
If all else fails, you can flash stock system, modem and kernel found in the Android Development section. That gives you a clean start. Then ODIN TWRP and flash SuperSU. If you do that just make sure you use the files designated for the Developer Edition.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
You think that would help? From what I've found so far the only thing that could potentially help would be a complete fresh stock Odin flash INCLUDING a bootloader but we don't have a flashable bootloader for DE.

I don't think you have a bootloader problem, I think you have a system issue or a kernel issue. If you're backup doesn't make things better then the only answer I have is to flash a stock (clean) system firmware and kernel which is available. Then re flash recovery and root. By the way, I wouldn't flash anything that had not been tested and passed for the Note 4, the Verizon Note 4. Just a recommendation.
Sent from my SM-N910V using Tapatalk

Endless Bootloop when using LineageOS and AOKP ROMs

Hello,
Since I got my XT1635-02 in April I have tried to use LineageOS and/ or AOKP. The problem is, when I flash either, I get an endless bootloop.
When I got the phone I:
Unlocked the bootloader
Flashed TWRP - the latest 3.1.1-0
Flashed Lineage ROM
I don't use Gapps - or I'd rather not - but at this stage I have flashed the Pico package
Then flash su-addon.
I've tried different combinations; only flashing LineageOS/AOKP but got the same result.
Stock images work fine for me. I even got to the point where I had to write a little bash script to flash all of the components in the correct order for the RETUS Nougat image.
Last month, by some fluke I got LineageOS to boot. However, I have no idea what I did differently, it just seemed to work that one time. However, I have been living off of that install for about 3 weeks and the OTAs even worked perfectly.
Today I got bored and decided to flash AOKP.
Booted in to TWRP
Wiped Dalvik, Sys, Data, Cache
Flash AOKP
Reboot
Bootloop.
Is there something wrong with my phone or is there something wrong with my process?
Any suggestions welcome. Thank you.

I remember​ that problem with Razr. Some custom roms were booting fine, some bootlooping.
The first workaround was to flash working one then without reboot flash desired one.
Later we figured out that wiping/formating partitions was the problem. Bootlooping rom couldn't read the file system. Solution was to not wipe or to wipe to the correct file system.
Sent from my XT1635-02 using Tapatalk

I think you may be on to something because I had flashed LineageOS after flashing the stock Nougat image. Still, would like a surefire way to just run a ROM. I've never had this issue on any other device.

I had it on Razr and just started to happen after one CM nightly build. Turned out that devs changed FS.

AOSP, RR Resurrection Remix, ArrowOS and others

I just wanted to point out that I have been able to boot some treble GSI on my device from different roms like AOSP, RR, ArrowOS in the treble section of XDA and some of them boot fine, but I have found some issues:
PHH PIE GSI doesn't like magisk it breaks wifi and mobile data once magisk is flashed
PHH Oreo AOSP GSI I do not remember any issues besides being too stock for my liking
RR GSI It has so many options almost comparable to what a Venom Rom would be for HTC devices
TWRP it is not able to read encryption on any of this GSIs
AOSP Oreo I don't remember if the other variants GSIs does not read exFAT formatted MicroSD (works on PIE GSI)
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
I would like more users to share their experience here with GSIs
the steps I took to flash this
1. make sure you download an arm64 AB GSI image from your favorite ROM
2. go to TWRP wipe section wipe system, Dalvik cache data & internal
3. go to TWRP wipe section format data, type yes
5. restore stock Vendor.img and stock Boot.img
6. flash GSI
7. reboot & enjoy
first boot might take awhile it encrypts the device, thi is the part that makes TWRP not being able to decrypt data since TWRP decrypts Qualcomm Encryption on our device but no stock android encryption this part it is possible to fix by TWRP team and it will probably come in later

Thanks for sharing. I was planning on trying out a GSI this weekend and see how it goes. Glad it works!

I forgot to save the stock vendor and stock boot file I need these two files Can you help

emrince said:
I forgot to save the stock vendor and stock boot file I need these two files Can you help
Click to expand...
Click to collapse
https://forum.xda-developers.com/u12-plus/how-to/collection-htcu-u12-ruu-firmware-t3794664/page24
Read the OP there

I tried to boot the RR img, no dice.
Backed up modified rom on slot b
Switched to slot a in TWRP, supposedly empty
Wiped system, data, cache, dalvik
Flashed prior stock vendor img and boot img
Flashed RR ab arm64 su gapps Img
Rebooted slot a
Bootloop
Interestingly, after looking 3 times, my phone booted back to slot b by itself back to stock, back up restored just fine
I realize I didn't wipe factory reset with yes

Finally got RR to to boot! It's a very finicky process. I think my problem was I kept trying to "dual" boot, Viper in one slot and the GSI in the other. Turns out it just has to be in the active slot, regardless of which slot you switch to in TWRP. Maybe that's obvious for some. This a/b partition business sure has a learning curve.
Anyway, things I noticed on RR: Lots of customization as usual for RR, very fast and smooth, screen brightness is on max all the time regardless of slider or auto brightness, and I couldn't make phone calls but texting worked. Everything else seemed to work fairly well. I love the fling navbar....on to the next one.

I'm not sure if anyone else is trying the GSI's, this doesn't seem to be a very active thread. So far I have only been able to boot RR 8.1 GSI. I have tried multiple other images without any success. I think the reason I didn't get data and calls didn't work on RR is that I am on Verizon and the HTC u12 does not have CDMA radios. Volte calling was not available on the rom. Oh well. I'm excited for the upcoming developments in the Viper forum. If anyone knows a fix for data on verizon with the GSI's, I'm all ears. Thanks

Anybody successful in making one of this ROMs a daily driver?
Sent from my HTC U12+ using XDA Labs

Resurrection Remix 8.1 is pretty stable if you are on a gsm network. I popped in a Tmobile sim card and it was pretty solid. There are some minor annoyances like the inability to adjust the brightness (always on full), though decreasing screen pixels makes it more dim, vendor mismatch message on boot, and no volte or wifi calling. There may be some other small things like with the camera and bluetooth but I didn't keep it for long as I am on Verizon and don't get data. I could see using it as a DD though. There are probably ways to fix the annoyances I mentioned.

Have any of you tested this version of RR on U12+?
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
For example, face recognition, 4k camera mode, slow motion recording, 3D sound, AudioFocus, bokeh mode etc.?
regards
q

@JEANRIVERA Is i't there any working Android P GSI rom?
Just can't wait anymore HTC for P update =)

nomaj said:
@JEANRIVERA Is i't there any working Android P GSI rom?
Just can't wait anymore HTC for P update =)
Click to expand...
Click to collapse
Original PHH, ArrowOS & DescendantOS all work fine, the only problem is no Magisk support yet

JEANRIVERA said:
Original PHH, ArrowOS & DescendantOS all work fine, the only problem is no Magisk support yet
Click to expand...
Click to collapse
So.. i will missing root? and fixes for google sotre etc ?

JEANRIVERA said:
Original PHH, ArrowOS & DescendantOS all work fine, the only problem is no Magisk support yet
Click to expand...
Click to collapse
I have problem with install ArrowsOS, i have still bootlops.. It's probably related to a / b boot, how to fix this? Twrp say "No OS installed", i set wipe system,data,cache next i flash vendor, boot and system file, i made a mistake?

JEANRIVERA said:
Original PHH, ArrowOS & DescendantOS all work fine, the only problem is no Magisk support yet
Click to expand...
Click to collapse
@JEANRIVERA
Is't this update helpping us?
2019.3.28 Magisk v19.0
https://forum.xda-developers.com/showpost.php?p=79216305&postcount=50https://forum.xda-developers.com/showpost.php?p=79216305&postcount=50

mientus25 said:
I have problem with install ArrowsOS, i have still bootlops.. It's probably related to a / b boot, how to fix this? Twrp say "No OS installed", i set wipe system,data,cache next i flash vendor, boot and system file, i made a mistake?
Click to expand...
Click to collapse
Hey, I'm having the same problem. Did you work out a solution to get any GSI to boot on your U12?

SilentAchiever said:
Hey, I'm having the same problem. Did you work out a solution to get any GSI to boot on your U12?
Click to expand...
Click to collapse
I tried to find a solution for 12 hours and nothing came of it

I's dual sim working on GSI roms?
---------- Post added at 10:38 AM ---------- Previous post was at 10:36 AM ----------
mientus25 said:
I tried to find a solution for 12 hours and nothing came of it
Click to expand...
Click to collapse
1. make sure you download an arm64 AB GSI image from your favorite ROM
2. go to TWRP wipe section wipe system, Dalvik cache data & internal
3. go to TWRP wipe section format data, type yes
5. restore stock Vendor.img and stock Boot.img
6. flash GSI
Did you flashed GSI rom from point 6?

Yes, i follow this instruction and twrp say "OS no installed".

mientus25 said:
Yes, i follow this instruction and twrp say "OS no installed".
Click to expand...
Click to collapse
Check this... wiping
"for GSI it is better to wipe from stock recovery "

Nexus 7: Old CM builds won't install

For quite awhile now, I have had a nexus 7 (2013) wifi 16GB (flo). CM13 was my first custom rom. Since then, I have upgraded to the latest official Lineage 14.1 build. Now, I never use my old nexus.
Yesterday, I wanted to put together a little game station with it, centering around Wii remote support. I've read that the last android version to support the WiiMotes was 4.1. Unfortunately the N7 was launched with 4.3, so there is no official 4.1 build for the phone. I then read that CM used to have their own support for the controller. Can anyone verify if this is true? From the wayback machine, I downloaded and installed CM13, which worked fine, but while the WiiMote would "connect", it didn't actually do anything, and all for lights on the controller flashed indefinitely. Next, I went to the oldest stable build of CM available: CM10.2 (android 4.3). When I went into the latest version of TWRP to install it, I wiped everything except internal storage, and flashed the zip. I've tried this several times, and it always leads to one of 2 outcomes: either succeeds with the following output:
Code:
updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Installing zip file '/sdcard/cm-10.2.1-flo.zip'
Checking for digest file...
Skipping digest check: no Digest file found
updating partition details...
...done
This results in an unbootable system.
Usually successful OS flashes have a lot more output than this, right?
Other times it fails. (Using the exact same file)
I'm having trouble reproducing this error wile I write this, but it was something along the lines of
Checking symlinks...
some symlinks failed.
I know the file was downloaded correctly, because it matches the checksum on the backup of the site.
I would post a wayback machine link but XDA won't let me.
LineageOS and CM13 install just fine, so the tablet isn't bricked.
So, can anyone
-help me install this old build of CM10
-Tell me a way to use wiimotes with a newer OS
-direct me to some obscure build of android 4.1 or older (WiiMotes used to work perfectly in 4.1 for all devices) for flo (I doubt this exists but maybe)
Remember, my N7 is otherwise useless to me, so I don't really care what it takes to make this work.

rondnelson99 said:
For quite awhile now, I have had a nexus 7 (2013) wifi 16GB (flo). CM13 was my first custom rom. Since then, I have upgraded to the latest official Lineage 14.1 build. Now, I never use my old nexus.
Yesterday, I wanted to put together a little game station with it, centering around Wii remote support. I've read that the last android version to support the WiiMotes was 4.1. Unfortunately the N7 was launched with 4.3, so there is no official 4.1 build for the phone. I then read that CM used to have their own support for the controller. Can anyone verify if this is true? From the wayback machine, I downloaded and installed CM13, which worked fine, but while the WiiMote would "connect", it didn't actually do anything, and all for lights on the controller flashed indefinitely. Next, I went to the oldest stable build of CM available: CM10.2 (android 4.3). When I went into the latest version of TWRP to install it, I wiped everything except internal storage, and flashed the zip. I've tried this several times, and it always leads to one of 2 outcomes: either succeeds with the following output:
This results in an unbootable system.
Usually successful OS flashes have a lot more output than this, right?
Other times it fails. (Using the exact same file)
I'm having trouble reproducing this error wile I write this, but it was something along the lines of
Checking symlinks...
some symlinks failed.
I know the file was downloaded correctly, because it matches the checksum on the backup of the site.
I would post a wayback machine link but XDA won't let me.
LineageOS and CM13 install just fine, so the tablet isn't bricked.
So, can anyone
-help me install this old build of CM10
-Tell me a way to use wiimotes with a newer OS
-direct me to some obscure build of android 4.1 or older (WiiMotes used to work perfectly in 4.1 for all devices) for flo (I doubt this exists but maybe)
Remember, my N7 is otherwise useless to me, so I don't really care what it takes to make this work.
Click to expand...
Click to collapse
You have to wipe internal storage. To go back from anything 5.0 and up to anything lower.
Format data along with wiping internal storage.
So it looks like you tried everything except the actual solution... LoL.
Good luck

madbat99 said:
You have to wipe internal storage. To go back from anything 5.0 and up to anything lower.
Format data along with wiping internal storage.
So it looks like you tried everything except the actual solution... LoL.
Good luck
Click to expand...
Click to collapse
I didn't mention it, but I actually did wipe internal storage, and then transferred the zip from the computer via twrp.

rondnelson99 said:
I didn't mention it, but I actually did wipe internal storage, and then transferred the zip from the computer via twrp.
Click to expand...
Click to collapse
Format data (simple wipe usually isn't enough) and type yes in TWRP

madbat99 said:
Format data (simple wipe usually isn't enough) and type yes in TWRP
Click to expand...
Click to collapse
OK so I tried that, but it still doesn't work. Gets stuck on the Google screen when I reboot. I am supposed to wipe system first, right? Do I need to flash a 4.3 system image as well or something like that?
Thanks for all your help!

rondnelson99 said:
OK so I tried that, but it still doesn't work. Gets stuck on the Google screen when I reboot. I am supposed to wipe system first, right? Do I need to flash a 4.3 system image as well or something like that?
Thanks for all your help!
Click to expand...
Click to collapse
Wipe everything. Format data, and flash the ROM of choice. If it sits for a while on Google, force a reboot by holding power.
If that doesn't work try flashing a 4.3 factory image and then Boot it up then flash to CM10 ROM you want to use
make sure you haven't resized your partitions or anything crazy like that make sure your data is formatted to ext4 not f2fs. basically undo any changes you've done as you've been flashing ROMs for the life of this tablet

madbat99 said:
Wipe everything. Format data, and flash the ROM of choice. If it sits for a while on Google, force a reboot by holding power.
If that doesn't work try flashing a 4.3 factory image and then Boot it up then flash to CM10 ROM you want to use
make sure you haven't resized your partitions or anything crazy like that make sure your data is formatted to ext4 not f2fs. basically undo any changes you've done as you've been flashing ROMs for the life of this tablet
Click to expand...
Click to collapse
where can i get a copy of a 4.3 factory image ?

https://developers.google.com/android/images
Sent from my Asus P027 using XDA Labs