Hi, this is my first post so please be patient with me
Today I finally decided to update my Nexus from 4.0.4 to 4.1.1 up till now I have been running ARHD.
I decided to flash the new MinCo ROM, everything went smooth, I did a Nandroid backup and used Superwipe Light.
Then flashed the ROM via CW, the phone booted fine and I restored my apps and I thought everything was fine till I checked the system information. There it says I am running 4.1 and no mention of MinCo ??? It shows Francos Kernel though
Did I just out myself as a noob or what went wrong ?
Help is much appreciated
PS. Love XDA :fingers-crossed:
I just looked at the build.prop file of my minco download and it shows 4.1.1. in the ro.build.version.release which would dictate what shows up under version. Maybe you downloaded a different rom?
Sent from my Galaxy Nexus using xda premium
I downloaded the ROM from the official source.
Here are my steps.
1. Downloaded ROM, Gapps
2. Backed up the phone using CW
3. Wiped the phone using Super Wipe Lite Nexus
4. Flashed ROM using CW
5. Flashed Gapps using CW
6. Rebooted the phone
7. Restored Apps via Titanium Backup
Should I have done a full wipe? I didn't want to loose all my stuff.
Thanks for the help by the way.
Whenever you are flashing a new base you want to do a full wipe. I'm not sure what happened with your download and why it says 4.1 instead of 4.1.1. Probably not worth losing sleep over though.
Sent from my Galaxy Nexus using Tapatalk 2
Ok seems like I have to wipe the whole thing then.
Will post the results later.
Thanks.
So I did a full wipe and flashed the ROM again. This time the System UI kept crashing.
This kept happening over and over again. I wiped and re installed 4-5 times with the same result.
Then I downloaded the the ROM and the bootloader again and flashed it again. This time it worked and it stopped crashing.
The ROM then showed 4.1.1.
I then flashed Gapps and MinCo+ Stock Mod and after reboot it was showing Android 4.1 again!
I really have no idea what is going on ???
Related
I have tried to flash a new ROM, but cmw were never able to flash it always being aborted. Yesterday tried to flash Darkside evo 3. Flash super wipe success, flash new baseband good, comes the rom itself aborted package not good. I thought it was just bad messages from cmw.Reboot the phone wouldnt reboot just hung,i tried cache wiped still not reboot, hung again. Any idea why? I just flashed the cmw again so i will try again. In the mean time any idea will be appreaciated
JugMod V 5.0,
2.3.6, 2.3.14
Possible bad download of the rom. Definitely won't boot after a superwipe. Did you make a nandroid?
Sent from my SGH-T989 using xda app-developers app
Yes, i did make a backup. Funny thing is, i am only able to install a new baseband, anything else is fail.
JugMod V 5.0,
2.3.6, 2.3.14
FwaZ said:
Yes, i did make a backup. Funny thing is, i am only able to install a new baseband, anything else is fail.
JugMod V 5.0,
2.3.6, 2.3.14
Click to expand...
Click to collapse
*my opinion*
your running gb, some of the newer roms are ics created, will cause conflict between the 2 hence why the non flash capable. i would recommend to update to ics and try again, make sure u nandro first in the event you wanna revert back to prior os and maybe that will solve your probs. hope this helps
sgs2:chimera bitten/ herculoid stout
3.0. perfection
I had this problem too both on My Vibrant and Galaxy Tab 10.1. I say odin to stock and do a clean install of the rom. that always seemed to fix it for me
Check the md5sum and see if it matches before flashing any rom thats very important.... Or what cwm version u using??? Cause the touch cwm has some issues so i changed to the non touch cwm its more secure
Sent from my SGH-T989 using xda premium
if you want, do what i did, i restored stock ics and cleaned up my phone fully as from factory. started from root to flashing all the stuff all over, now im on a clean sd card( backedup all the external sd on my pc) so i have tons of room to play with. hope this helps
Hi, I've decided to go back to stock so I flashed the 2.3.6 MD5 file via odin. The flash was successful but when the phone booted up, all i get is FCs and cannot go any further. tried flashing 2.3.5 and 4.0.3 and both ended up with the same results.
does anybody know whats going on?
Not sure what you did wrong or why it's acting up, but odin this one instead
http://forum.xda-developers.com/showthread.php?t=1705565
It's the official ICS and I Odin back to stock using this yesterday and haven't had any problems with this.
If you want to go back to GB let me know and I'll post some files I have for that, but I'm not sure why you would want to.
Powered by the SGSII soon the SGSIII
Finally I got it to work. I flashed the stock ROM and flashed clockwork recovery immediately afterwards. Then I wiped the data, cache, davlik cache, and fixed permissions.
Sent from my SGH-T989 using Tapatalk 2
Hi. I tried installing the latest CM9 nightly and when my phone rebooted it was stuck at the FreeXperia logo. I rebooted the phone and tried to get into CWM recovery but couldn't. So I booted into fastboot and installed the boot image from this (I can't like to the rom but it is called cm-9.1.0-zeus.zip) rom. Now I can get into CWM recovery. When ever I try to install the rom I get an error message Status 7. This happens after it says "assert failed: getprop("ro.product.device") == "R800i" etc.
It looks like either my device name on my phone is wrong or the device name for the rom is wrong. I'm pretty sure the rom I downloaded is the right one though. I've installed roms before but never ran into an issue like this so I'm lost. Seeing as I can get in to CWM recovery I reckon I should be able to get it back working again. Would really appreciate some help here.
Cheers.
re flash stock
CyberScopes said:
re flash stock
Click to expand...
Click to collapse
Downloading flashtool now. Will report back if it works or not. Hopefully it does.
I'm back on stock SE 2.3.3 rom now. Thanks a million, CyberScopes.
I guess I spoke too soon. It seemed like it was working fine with the stock rom. I went to put CM9 on it and everything worked fine apart from it not recognising the baseband. I put on the stock rom again and now it just keeps rebooting. *sigh*
AlmightyCushion said:
I guess I spoke too soon. It seemed like it was working fine with the stock rom. I went to put CM9 on it and everything worked fine apart from it not recognising the baseband. I put on the stock rom again and now it just keeps rebooting. *sigh*
Click to expand...
Click to collapse
Make sure you now have a compatible kernel and ROM.
Also make sure you have the recommended basebrand. I use .64
Sent from my Xperia Play using xda app-developers app
OK, I'm back on stock and the baseband is recognised. The guide I have been using for installing CM9 is this one (http://forum.xda-developers.com/showthread.php?t=1600833&highlight=cm9+guide). Is there something missing from that guide. I've never had to check if the kernel and rom were compatible. When using fastboot, I use the boot.img from the rom I download.
Flash kernel using flashtool.
Remember to do complete internal wipe and cache wipe.
I figured out why baseband wasn't working on CM the first time. It turns out that the stock rom I was using was an old one and the baseband for that wasn't working on CyanogenMod. I downloaded a newer one, installed that and then stuck CM9 on it and everything is working fine. Phew. Thanks again for the help. Really appreciate it.
Ure welcome. Im glad i helped u.
Sent from my R800i using xda app-developers app
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.
captican said:
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.
Click to expand...
Click to collapse
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?
danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
I had the same problem since 4.3 came out. It has to do with partition tables... What i've done to correct the problem:
- Odin back to stock
- Format entire phone. (Complete wipe) + Dalvik and cache
- Odin stock with root
- Replaced TWRP recovery for CWM
- Flashed 4.3 ROM and VOILA
- I have tried every 4.3 rom ever since with no problems
Don't (Complete wipe) with Twrp recovery, it seems to mess up the partitions.
Hope this works for you
Cheers
danielhep said:
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?
Click to expand...
Click to collapse
It loaded the first time and then rebooted, freezing on the kernel screen. I could get into recovery, and restore a previous ROM but it would hang up on 4.3. I described the steps I had taken when someone suggested reformatting data. I tried again and it is working now.
The method described in the other post may also solve your problem. I say that because I cannot update twrp to 2.6.1, at least via goo manager. I have not tried using Odin to update (yet).
I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app
I managed to load a stock rom back to the phone but again, it hung on the SAMSUNG screen. Took it to "a guy" and he did a
key sequence and got it to boot. Woulnd't tell me what it was........
ANy one know???
Apocalypse487 said:
I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This happened to me after I flashed back but formatting data got it to work (but I have had more problems with apps not installing properly but I learned how to deal with that...still cannot update TWRP via goo manager; waiting on trying it with Odin).
Hey guys=)
So yesterday i installed (after an EFS Backup) a 4.3 Custom Rom (JoelDroid) on my Galaxy NOte 2 N7100. It was on a rooted 4.1.2.
The rom booted everythign looked fine. I also wiped Data/factory resetted my device before i install the rom. But when i have to configure it the first time, it always crashed. So i made a full wipe and flashed the rom again (Philz touch btw the newst version). But the same thing again.
So i decided to flash a new ROM. Full reset, resetted caches and so on and the same problem again. My device boots up correctly but after 1minute or so it freezes completly. Cant press any buttons and so on.
The last try for me was to install a CM 10.2 (Asylum) version. This one is working properly. Had 1 or 2 crashes, but now its working fine.
But i dont want to lose the stock features.
Can anybody help me pls? What did i wrong? what do i have to do to get a proper functional MI6 4.3 rom on my N7100?
Thank you very much
Greets Marco
Have tried any other 4.3 rom? Steps u are following are absolutely correct btw..
If u using philz then u should choose the option "clean install befire a new rom" and manually format system,data,cahe and preload..this is a clean install.
Sent from my AweSoMe ?♥Note2♥?
Thanks for your reply!
Yes i used the option clean for New installation and i used 2 other 4.3 Roms too AS i mentioned. But at least i know now that my procedure was correct. Should i try another Rom? Or should i flash back to stock 4.2.2 (if its possible) via Odin?
Sent from my GT-N7100 using xda app-developers app
ok it looks like that the Asylum CM 10.2 is also not working. Crashes after some time too (every 1-2 hours) :/ really need help guys!
EDIT:
Ok i installed Stock 4.1.2 ROM via ODIN and now everything's working fine again. I think i will stick to this for some time now (have a prerooted version so root still there)