Related
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
Hey guys, I just went from 4.3 JDX to XenonHD (4.4.2) and everything's great with the exception of Gapps. I tried both the PA stock and the modular full images and both behave the same.
After wiping system/data/cache, I Installed Xenon in TWRP (newest) followed by the PA Gapps image. It went through just fine, no errors, congrats yadda yadda. After boot I notice quite a few Gapps missing, Hangouts and G+ being the ones that caught my attention. Trying to install from Play Store results in error "Insufficient storage available", and I have about 5GB left. I'm not sure how relevant the following check was, but I tried restoring a backup from Titanium...any Gapp I try to restore just hangs there at the restore screen with no progress or error. I was guessing that had something to do with the switch between 4.3 and 4.4.
Any ideas about how to get this worked out? Thanks.
kornesque said:
Hey guys, I just went from 4.3 JDX to XenonHD (4.4.2) and everything's great with the exception of Gapps. I tried both the PA stock and the modular full images and both behave the same.
After wiping system/data/cache, I Installed Xenon in TWRP (newest) followed by the PA Gapps image. It went through just fine, no errors, congrats yadda yadda. After boot I notice quite a few Gapps missing, Hangouts and G+ being the ones that caught my attention. Trying to install from Play Store results in error "Insufficient storage available", and I have about 5GB left. I'm not sure how relevant the following check was, but I tried restoring a backup from Titanium...any Gapp I try to restore just hangs there at the restore screen with no progress or error. I was guessing that had something to do with the switch between 4.3 and 4.4.
Any ideas about how to get this worked out? Thanks.
Click to expand...
Click to collapse
Had a similar problem with installing CM 11.1 and PA GApps 4.4.2 - don't know if it's the same for you, but I found out the problem was the /system partition is too small - as CM and GApps have gotten bigger and bigger the partition is now too small to handle them. I had to move over to AOKP and a different 4.4.2 GApps package. Might be time to upgrade to a Nexus 5....
crfrank said:
Had a similar problem with installing CM 11.1 and PA GApps 4.4.2 - don't know if it's the same for you, but I found out the problem was the /system partition is too small - as CM and GApps have gotten bigger and bigger the partition is now too small to handle them. I had to move over to AOKP and a different 4.4.2 GApps package. Might be time to upgrade to a Nexus 5....
Click to expand...
Click to collapse
Well I'll be...i figured with the unified SD card that would be a thing of the past, but it does make sense. I'll give it a whirl. Thanks man.
SOLVED
crfrank said:
Had a similar problem with installing CM 11.1 and PA GApps 4.4.2 - don't know if it's the same for you, but I found out the problem was the /system partition is too small - as CM and GApps have gotten bigger and bigger the partition is now too small to handle them. I had to move over to AOKP and a different 4.4.2 GApps package. Might be time to upgrade to a Nexus 5....
Click to expand...
Click to collapse
That was it. Titanium reported about 20MB system space left so I snagged the micro Gapps and that worked great. Thanks for the idea!
kornesque said:
That was it. Titanium reported about 20MB system space left so I snagged the micro Gapps and that worked great. Thanks for the idea!
Click to expand...
Click to collapse
You're welcome, glad I could help
Hi everyone,
Today I installed the new CM12 nightlies, after rebooting my HTC one m8 it showed me a popup message that google play services stopped working. I also couldnt launch particular apps. So after looking for a solution I tried reinstalling Gapps hoping this would solve the problem.
I downloaded the minimal Gapps ZIP file and flashed it using TWRP recovery, after I wiped the cache and dalvik cache. Once rebooted I started to get the anoying pop up notifications '' Gmail stopped working'' and ''youtube stopped working''. These two messages won't go away and makes my phone unusable. I think the reason why these messages keep popping up is because i flashed the minimal version of Gapps so I downloaded the normal version of Gapps on my computer since my phone isnt accesable because of the pop-up notifications that won't go away. What I did next was plug in my phone to my computer and moved Gapps L-3-14-15.zip to my SD card and installed it again. I also wiped the cache and dalvik cache. after I did a reboot and everything seemed fine for the first 20 seconds... It didnt last long. Im still having the same problem as before Gmail and youtube has stopped working. Do any of you know how to fix this without doing a system recovery?
Thanks in advance
HTC one m8
Cyanagonmod 12.1
Rooted
TWRP
S-on (don't know if this is relevant)
Copy important files to computer. Factory reset. Set it up as new device.
ikeny said:
Copy important files to computer. Factory reset. Set it up as new device.
Click to expand...
Click to collapse
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.
jcole20 said:
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.
Click to expand...
Click to collapse
I guess the minimal Gapps package that I first installed wasnt for 5.1
In order to get rid of the pop up notifications I started my phone in safe mode. This worked and I saw there was a new update for cm12.1 after the update finished and I booted up my phone the pop up notification werent there anymore but google play services was also uninstalled. What I did next was installing the newest google play services pack. After it was done I installed the 5.1 Gapps version on my phone and now everything seems working fine again. I did get some notifications that an app such as chrome stopped working but a simple reinstal of the app fixed the problem. Somehow the apps that I moved to my external SD card arent here anymore but im glad I didnt have to do a factory reset.
Thanks for your help
jcole20 said:
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.
Click to expand...
Click to collapse
every time i update my cm12 nightlies it has its own recovery (cyanogen recovery) but my zip files are not working with that recovery. (ex. cmzip.gapps, and kernels). for my device it works on PhilZ touch recovery. so the tendency is i have to flash fastboot boot.img(philz touch)again and again.
using Thunderzap kernel 4.15 im stock on bootloop.
running cm12.1 nightlies (4/20/15)
also gapps not compatible.
decoction said:
every time i update my cm12 nightlies it has its own recovery (cyanogen recovery) but my zip files are not working with that recovery. (ex. cmzip.gapps, and kernels). for my device it works on PhilZ touch recovery. so the tendency is i have to flash fastboot boot.img(philz touch)again and again.
using Thunderzap kernel 4.15 im stock on bootloop.
running cm12.1 nightlies (4/20/15)
also gapps not compatible.
Click to expand...
Click to collapse
I use twrp and I've not had any issues with a cm recovery replacing twrp. On the 420 nightly I don't even see a recovery.img in the cm zip so I'm assuming you're updating via cm itself. I think there's a setting in there to choose to update cm recovery or not.
To flash Phillz recovery you're syntax would be "fastboot flash recovery recoveryimgname.img" the boot.img is your kernel. I'm not sure how many aosp 5.1 kernels the m8 has but I've not really been able to find any so I just use the cm one.
To correct your issues I would flash twrp 2.8.6 via fastboot flash recovery. Wipe everything from recovery (cache data dalvik system) and reinstall. If it was me I'd update cm via zip from now on if it was causing me these issues. Good luck
HTC One (M8) ViperOne + Hypernova
Everything seemed working fine again until 30 min. ago...
I got the notification chrome has stopped working. (Haven't had this message all the morning and chrome worked just fine.)
I restarted my phone and the first thing I noticed was that some of my apps have disapeared from my home screen, they are still in the app tray tho. Also my keyboard input mode has been set back to AOSP while normaly I use Swiftkey keyboard as my standard input. Chrome was still pushing me not working notification so I reinstalled chrome and now it works fine again. Not sure for how many time...
Its kinda anoying but maybe tonights nightlies will solve the problem somehow. If not, do you have any sugestions how to fix this?
jcole20 said:
I use twrp and I've not had any issues with a cm recovery replacing twrp. On the 420 nightly I don't even see a recovery.img in the cm zip so I'm assuming you're updating via cm itself. I think there's a setting in there to choose to update cm recovery or not.
To flash Phillz recovery you're syntax would be "fastboot flash recovery recoveryimgname.img" the boot.img is your kernel. I'm not sure how many aosp 5.1 kernels the m8 has but I've not really been able to find any so I just use the cm one.
To correct your issues I would flash twrp 2.8.6 via fastboot flash recovery. Wipe everything from recovery (cache data dalvik system) and reinstall. If it was me I'd update cm via zip from now on if it was causing me these issues. Good luck
HTC One (M8) ViperOne + Hypernova
Click to expand...
Click to collapse
Thank you for that info. it really helps. by the way i got problems when i updated it to the cm12 4/21/15 update. got this message "trebuchet has stop working" so i decided to use cm resurrection remix.
decoction said:
Thank you for that info. it really helps. by the way i got problems when i updated it to the cm12 4/21/15 update. got this message "trebuchet has stop working" so i decided to use cm resurrection remix.
Click to expand...
Click to collapse
Yeah I mean nightlys merge with code that it's being worked on and may break or fix certain things. Nightly builds may be perfect or they may not even boot. You kind of have to just flash them and see. Cm is very generic coding and depending on your carrier may not have the non open source vendor blobs necessary to make, say, your speakers work properly. It really depends. I don't believe Verizon had released their kernel source for lollipop so sometimes downgrading firmware to known source (ie 4.4.4) may help alleviate connectivity issues with Wi-Fi and things of that sort. Team UBs build and lollipop dream 5.0.2 have been my go tos as of late. The lollipop dream build is the smoothest running cm build I've ever used even on nexus devices. Very well made.
HTC One (M8) ViperOne + Hypernova
My phone is a 4.3 official Samsung and is properly rooted. I have downloaded CM13 and Gapps onto my external SD card and went into CWM recovery mode. I firstly backed up everything (thankfully) and performed a wipe data/factory reset followed by installing CM13. However when I run CM13 almost immediately an error pops up saying "this package is not for device: this device is d2spr" along those lines. Any help would be appreciated; thanks!
BTW forgot to mention I completely removed Knox from my phone so that I could root it.
I had a similar issue, but with TWRP. As I have a Canadian S3, so I downloaded the "d2can" build of TWRP.
When I tried to flash the CM13 "d2tmo" package, it resulted to an error, saying that it cannot install the package as my device was a "d2can".
I did a quick search on Google to find out that, for TWRP at least, both recovery and package device must match. Maybe a wrong version of the recovery was installed in your case?
Did you use CyanogenMod app? From memory, it seems you can edit the device name. Try to change it to "d2tmo" as explained on the CyanogenMod SGS3 FAQ (search "SGS3FAQ" on Google).
The "d2can" is the moniker for the s3 from Rogers, Telus, and Bell and the d2att is the moniker for the AT&T version of the s3.
The s3 development for the d2can and d2att was unified into the d2lte.
The cm13 for the d2tmo is not installing because the updater script is looking for a particular model.
Did you try flashing twrp for d2tmo?
audit13 said:
The "d2can" is the moniker for the s3 from Rogers, Telus, and Bell and the d2att is the moniker for the AT&T version of the s3.
The s3 development for the d2can and d2att was unified into the d2lte.
The cm13 for the d2tmo is not installing because the updater script is looking for a particular model.
Did you try flashing twrp for d2tmo?
Click to expand...
Click to collapse
Actually, it seems (based on the page "Information: Samsung Galaxy S III LTE ("d2lte")" in the CyanogenMod Wiki) that S3 development was unified into "d2lte" only between CyanogenMod 11 M3 and M12 releases.
The SGS3FAQ page refers explicitly to the "d2tmo" build for the SGH-T999 and SGH-T999V for CM 12.1 and newer releases.
Hmm, seems that cyanogen has gone back to using d2att for newer releases as indicated here: https://download.cyanogenmod.org/?device=d2att
The i747 and i747m should work on d2att builds.
That wiki page was last updated in February, 2014?
I used to have an s3 from wind and I used twrp for the d2tmo to flash ROMs.
audit13 said:
The "d2can" is the moniker for the s3 from Rogers, Telus, and Bell and the d2att is the moniker for the AT&T version of the s3.
The s3 development for the d2can and d2att was unified into the d2lte.
The cm13 for the d2tmo is not installing because the updater script is looking for a particular model.
Did you try flashing twrp for d2tmo?
Click to expand...
Click to collapse
Yeah I just tried with d2tmo, same results. I went to download the d2spr and flash it onto my phone and it worked. Turns out my phone has misleading stickers saying that it is a T model brand; it turns out it is a sprint. So after wiping out my phone completely, including davlik cache and cache partition. After this I flashed Gapps 6.0 ARM and rebooted my phone. After this a bunch of errors start popping up in the setup phase that play store has crashed and google frameworks has crashed etc. The apps are not there in my applications so I can't mess around with the settings and also I am locked out of most of my applications which suddenly crash followed by a rude avalanche of google apps crashing messages. Further assistance is required <3 I am a newbie at this so please be gentle.
Oh and if it helps, I cannot access file manager at all without crashing. So... Yeah.
Does the sprint phone have a locked bootloader? Probably not if it took twrp.
Maybe flash back to stock if possible with Odin and start over?
audit13 said:
Does the sprint phone have a locked bootloader? Probably not if it took twrp.
Maybe flash back to stock if possible with Odin and start over?
Click to expand...
Click to collapse
I would try that thanks. Will tell you results bu tomorrow; kinda busy now
Ok it still doesn't work; after rebooting to the old stable os and then to CM13 is fine, but gapps is still screwing up big time. Any suggestions?
Have you tried different versions of the cm13 gapps?
audit13 said:
Have you tried different versions of the cm13 gapps?
Click to expand...
Click to collapse
Yeah I have, recovery mode just won't boot it at all saying that it is not compatible, and then it would abort then soft brick my phone in a never ending booting loop. So yeah, not fun. I tried installing the gapps of a different version; so far I have only used pico which resulted in the rom working, but all google applications would just crash continuously making it unbearably annoying to do anything with the popup screens.
I have tried micro however it would continuously reboot over and over for about 15 min so I can almost assume that it doesn't work so I reinstalled the stable 4.3 android version that I am at now.
Despite going through hell I have learnt a lot. However I want to get this done so I can enjoy the custom rom. Yet again any more suggestions please bring it up, thanks!
Try banks gapps?
audit13 said:
Try banks gapps?
Click to expand...
Click to collapse
I'll give that a go hang on....
It didn't work. While I was flashing it, it would say:
Finding update package...
Opening update package...
Installing update...
Installation aborted
Any more suggestions ?
This is my screen. The files have somewhat installed but are stored elsewhere?
http://imgur.com/a/v3cIW
http://imgur.com/jrVq6Nd
Hey guys thanks for everything. The problem was solved by installing a different twrp. The old one I was using was apparently corrupted and screwed up my current phone, heh the chances of that?? Lots of love <3<3<3
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