Related
hey guys, im trying to flash the miui 1.6.24 rom onto my 2.2 fascinate. ive tried twice now and everytime i i try and flash, it starts the download for about 5 seconds, then just keeps rebooting the phone and says cant mount and does a countdown from 20 then reboots and repeats. i have had to odin back to stock 3 times already from this. any ideas why this is not working? and how can i get it to work? Thanks in advance
Have you read how to flsh to the cm7 & miui thread. Make sure you have the correct kernal, gapps and recovery. I think that is why you maybe getting stuck. Be sure to read how to get back to other roms if you choose to go back.
gotsflat4love said:
Have you read how to flsh to the cm7 & miui thread. Make sure you have the correct kernal, gapps and recovery. I think that is why you maybe getting stuck. Be sure to read how to get back to other roms if you choose to go back.
Click to expand...
Click to collapse
no i cant find that thread. the only one i can find is the how to go from cm7 or miui to another rom. but im trying to do the opposite
it just keeps saying "waiting for SD Card to mount" and counts down. then just keeps repeating
Can anybody help me?
I came from Nameless v4.1 and have a thread in Q and A that answers this but I'll tell ya how, it's basically the same steps since I odined back to stock.
Make sure that you have Andmer's latest miui build on the root of your SD card. Then assuming you already use the latest recovery (I had time's blue recovery) , wipe the big 3 (data, cache, delvik) > install from SD card > choose the miui rom > have a little patience > profit.
For me it did the count down 4 times before it actually mounted and finished the install. I don't know if the size of the SD card effects it in any way, concidering I'm only using a 4g, but it may take awhile. Again these are the steps I took and I haven't had any problems other than the one's already stated.
Sent from my miui fascinate using XDA Premium App
Yeah when it was doing the countdown I let it go before for about a half hour and it still list kept doing it and I had to Odin back to stock again. I didn't have the rom on the root of the SD card, I had it in a folder entitled root that I put all my roms on. I don't know if that would really make a difference
To be honest I'm not entirely sure. I've always put it on the root of the sd card. I guess at this point it wouldn't hurt to try. And again I'm not sure if the size of the card comes into play considering I'm using just a 4g card and not my stock 16g. Maybe someone else with more experience and overall know how can chime in to help. Sorry if I couldn't be of any help.
Sent from my miui fascinate using XDA Premium App
Maybe a bad d/l ?
I just switched to cm7 from miui then back and had no issues
Try redownloading
Sent from my MIUI Fascinate XDA App
Yeah I'm not using the stock card either. I'm using a 2gb Samsung and a 8gb sandisk. And I don't think its a bad download cuz I've tried doing it with all 3 versions of miui and it did it to all of them and the new cm7 and the cm7/miui kernel. I could get the old cm7 but when trying to flash the new one I get the countdown
I just tried again and let it do the countdown for a half hour so it tried about 40 times to mount the card. Any other suggestions?
I'm also needing a bit of advice on how to install MIUI on my Fascinate...
http://forum.xda-developers.com/showthread.php?t=1139400&highlight=AOSP+Gingerbread
Trying to install that. Downloaded the packages, but not sure what to do from there. I was going to load them into ODIN, but realized they aren't regular tar.gz packages...can I just load it with ROM Manager or what? I'm currently on 2.2.1, "Super Clean version 2.9 - EB01/EC16 Froyo leak root+Froyo Clockworkmodwith MALWARE protection".
Not to hijack, but seems we have similar questions.
You need to load in CWM, ROM manager is not compatible with the newer roms
MIUI 1.7.1 error 7
GuitarrassDeAmor said:
I'm also needing a bit of advice on how to install MIUI on my Fascinate...
http://forum.xda-developers.com/showthread.php?t=1139400&highlight=AOSP+Gingerbread
Trying to install that. Downloaded the packages, but not sure what to do from there. I was going to load them into ODIN, but realized they aren't regular tar.gz packages...can I just load it with ROM Manager or what? I'm currently on 2.2.1, "Super Clean version 2.9 - EB01/EC16 Froyo leak root+Froyo Clockworkmodwith MALWARE protection".
Not to hijack, but seems we have similar questions.
Click to expand...
Click to collapse
Yeah trying to load MIUI 1.7.1 also and keep getting the error 7. Do we have to do it through odin?! cleared data, cache and dalvik, still no go. Did putting it in root make a difference? why cant it just work like the other roms lol! Sorry for taking your Thread away kendall316!
Thanks in advance if anyone figures it out! if i do, will post it.
i am stuck. i tried to flash super charged hatka 320 dpi and i have gone in the wrong direction because my dna doesnt boot up properly. after super hatka gets past the boot i am able to get to the lock screen and once i swipe to unlock, it says unfortunately settings have stopped working. my launcher doesnt work. i cant operate the phone what so ever except for looking at the settings. when i get a text message i can reply, but thats pretty much it. i have experience in rooting and flashing the htc g2, gs2, and the gnexus. but this htc dna is something different and i am having extreme difficulties. i can go into much more detail if someone has the moment to help me out
Maybe if you try to re-install the Rom will all be ok....it might solve the problem...did you do a proper wipe before flashing...and did you create a nandroid backup if so restore it in Recovery and then flash the Rom again...if. not first do a proper wipe and then reflash the Rom....I use viperdna so I don't know if you have after the install to flash any kernel,fix or something???check it first and then procceed with the other things..hope to helped yiu
Sent from my HTC Droid DNA
If you came from another ROM or Stock, Factory Data Reset from recovery is advised ... you could also try flashing another custom ROM to get moving
Djmk4 said:
Maybe if you try to re-install the Rom will all be ok....it might solve the problem...did you do a proper wipe before flashing...and did you create a nandroid backup if so restore it in Recovery and then flash the Rom again...if. not first do a proper wipe and then reflash the Rom....I use viperdna so I don't know if you have after the install to flash any kernel,fix or something???check it first and then procceed with the other things..hope to helped yiu
Sent from my HTC Droid DNA
Click to expand...
Click to collapse
i have tried to reinstall it, same problem. this happenes when aroma was finishing the install of the rom
<..simmer down..>
.
..
removing old init.d files...
sqlite3 exists
set_perm:some changes failed
installation failed
error
senseless slim super charged hatka dna v2.1.0
install failed
installer status: 7
i want to install a different rom, idc what rom, but i cant download anything, i tried chrome and iE but none of them will download any roms. does anyone have an alternate link to a rom that isnt linked here on xda?
and i was coming from stock. i certainly wiped cache and factory reset before flashing the rom. i used flash image gui to flash the bootimg and then wiped everything in cwm, the flashed module zip and then flashed the rom. thats pretty much what i did, i do appreciate your replies
dj2muchxx said:
i have tried to reinstall it, same problem. this happenes when aroma was finishing the install of the rom
<..simmer down..>
.
..
removing old init.d files...
sqlite3 exists
set_perm:some changes failed
installation failed
error
senseless slim super charged hatka dna v2.1.0
install failed
installer status: 7
i want to install a different rom, idc what rom, but i cant download anything, i tried chrome and iE but none of them will download any roms. does anyone have an alternate link to a rom that isnt linked here on xda?
Click to expand...
Click to collapse
What's happening mate...really can't help you...the only thing I suggest to write exactly what you wrote here in hatka's Rom thread...maybe the dev that made the Rom....can help you or someone might had the same issue
Sent from my HTC Droid DNA
What recovery are you using? I had an issue with twrp at first and switched to cwm touch. And no issues. I've had issues though by going back after getting stuck at boot and wiped then installed Rom with full wipe. But if its an error not installing might try fastboot flashing a different recovery
Sent from my HTC6435LVW using xda premium
dj2muchxx said:
and i was coming from stock. i certainly wiped cache and factory reset before flashing the rom. i used flash image gui to flash the bootimg and then wiped everything in cwm, the flashed module zip and then flashed the rom. thats pretty much what i did, i do appreciate your replies
Click to expand...
Click to collapse
I think it might be a problem with the download I will fix it later today
Sent from my HTC6435LVW using xda app-developers app
fixed
i may have had a bad download. i was using the 320 dpi senseless rom, my phone was unusable like i had stated, but i managed to get it running.
here is what i did to fix it:
in the settings, i linked my dna with my google account, and as i expected, i received play store notifications about updates, so i chose the notification and it took me to a fully functioning play store.
i downloaded apex launcher and it installed properly. pressed the home button and it automatically set itself as the default launcher and bam! my dna was beginning to function.
downloaded xda app and went to the super charged thread and downloaded the slim version of the rom instead of the senseless rom.
flashed the boot.img, flashed the modules, then flashed the slim rom and i didnt get any errors or failed messages this time.
i dont want to point fingers and i would never do that here on a fantastic community, but the senseless rom was giving me issues, maybe it just needs some more work. anyways phone is functioning like normal now, everything works and the battery is outstanding so far.
thank you to those for the advice. i was getting ready to call it quits and send this thing back to amazon wireless.
MustafaHadaKing said:
I think it might be a problem with the download I will fix it later today
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
i think it was just the rom, if u need a guinea pig to test out your rom or anything, im in. i am enjoying super charged hatka very much:good:
Anyone have an idea why every time I install an aosp rom it glitches at the Samsung boot screen then just goes black and I have to pull the battery? I've installed clean, jelly beans and jedi Rom without issue. Any help is appreciated.
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
dudeicles said:
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
Click to expand...
Click to collapse
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
dudeicles said:
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
Click to expand...
Click to collapse
Odin to stock then re unlock and try this all again? I'm not sure what else you can try. I flip between aosp and tw almost daily
Sent from my SCH-I605 using Tapatalk 2
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
1ManWolfePack said:
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Heh I think I can I think I can...I was thinken are you trying to flash the file that the post links to because thats not the right one you need to get the note 2 lte one tolte..just a though I downloaded the wrong one first but caught it
http://changelog.bbqdroid.org/#t0lte/cm10.1/next
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Yeah it can't hurt even if they don't say that
Sent from my SCH-I605 using Tapatalk 2
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Would it help in any way to change to CWM when flashing my AOSP roms?
dudeicles said:
Would it help in any way to change to CWM when flashing my AOSP roms?
Click to expand...
Click to collapse
I would try cwm, I had a gs3 that couodnt flash anything with cwm but could with twrp, my note was the opposite, cwm was awful on it.
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
dudeicles said:
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
Click to expand...
Click to collapse
I've heard too many issues with cwm to even try it. Twrp has been flawless for me so why switch? If it ain't broke, don't fix it.
Sent from my SCH-I605 using Tapatalk 2
Ok, so update - Odin'd back to stock and re-rooted using the Casual method. I have the most recent TWRP installed and when i install the AOSP rom it does the exact same thing. I'm thinking about videotaping what the boot animation does and maybe someone can look at it and see what the cause may possibly be.
If anyone has any other suggestions i'm all ears. Again, any rom based on STOCK works without issue (Clean Rom, Jelly Beans and Jedi), but only AOSP roms (And CWM) crash the phone at "Samsung Galaxy Note II" screen on startup.
Thanks for the suggestions so far, just weird it's not working. I may have the single note 2 to never run AOSP roms. LOL
so... oddly enough i still have trouble installing AOSP roms. the only AOSP rom i have been able to install so far is Paranoid Droid. I am slowly trying each one just to see which one i can force to work. Am I the only person who can't just flash whichever rom I want whenever?
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Follow the advice to Odin back to stock and start over. Otherwise, get a replacement and tell them it's acting weird and slow haha.
Sent from my SCH-I605 using xda app-developers app
Same here!!
spydersilk said:
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Click to expand...
Click to collapse
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
slinky42 said:
I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
This is standard on 4.2.2 ROMs. It is related to the multi-user implementation.
slinky42 said:
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
Did you ever get your phone to install the AOSP Roms? Mine worked when l just let the phone sit. Now it works fine all the time.
Sent from my SCH-I605 using xda app-developers app
What have I done wrong. I rooted a friends note as I did mine. Followed Canadian rooting guide. Went to install new cm10.1 and got a error. Blah blah blah error "bad". Redownloaded 4 times withe the same result.
What's my deal?
Sent from my SGH-I717R using xda app-developers app
thutchinson85 said:
What have I done wrong. I rooted a friends note as I did mine. Followed Canadian rooting guide. Went to install new cm10.1 and got a error. Blah blah blah error "bad". Redownloaded 4 times withe the same result.
What's my deal?
Sent from my SGH-I717R using xda app-developers app
Click to expand...
Click to collapse
Perhaps give TWRP2 a try as the recovery. I've had more success with it over CWM with newer ROMs and never went back to CWM.
When reporting an issue... it's a fantastic idea to describe your problem as clearly as you can.
"Error blah blah blah Bad ... blah blah blah" doesn't really help anyone to help you.
Cwm gave your an error, now I can only assume it was a status 7 error.
That means your recovery is older than the type of script used in the zip to flash the rom.
To fix this, do as the poster above said and get the latest twrp, or find an updated version of cwm.
I personally use twrp so I'm not 100% sure where to find the latest cwm if it's not here on xda.
Now... if this isn't the error you're getting. Do yourself a favor and just flash that rom and
POST EVERY SINGLE THING CWM SAYS.
LETTER FOR LETTER.
Hey Folks, The error I am seeing is on both TWRP and CWM. E:Can't open /sdcard/cm-10.1-20130303-NIGHTLY-quincyatt.zip(Bad) Installation Aborted.
studacris said:
When reporting an issue... it's a fantastic idea to describe your problem as clearly as you can.
"Error blah blah blah Bad ... blah blah blah" doesn't really help anyone to help you.
Cwm gave your an error, now I can only assume it was a status 7 error.
That means your recovery is older than the type of script used in the zip to flash the rom.
To fix this, do as the poster above said and get the latest twrp, or find an updated version of cwm.
I personally use twrp so I'm not 100% sure where to find the latest cwm if it's not here on xda.
Now... if this isn't the error you're getting. Do yourself a favor and just flash that rom and
POST EVERY SINGLE THING CWM SAYS.
LETTER FOR LETTER.
Click to expand...
Click to collapse
Your file is incomplete or corrupted. Redownload it.
I have redownloaded at least 4 times on both computer and transfered it over and on the phone via browser
Sent from my SGH-I717R using xda app-developers app
Download it from here: http://get.cm/get/jenkins/21559/cm-10.1-20130303-NIGHTLY-quincyatt.zip
And transfer to your phone/sd card via USB cable or SD card adapter on PC.
You did install CWM properly and aren't still using stock recovery?
Problem has been solved. I used the USSD code for reset, went to stock and re did everything and a way I go. Everything works no. What I did before is beyond me. Thanks alot to everyone who has offered their help! Greatly appreciated...
Agoattamer said:
Download it from here: http://get.cm/get/jenkins/21559/cm-10.1-20130303-NIGHTLY-quincyatt.zip
And transfer to your phone/sd card via USB cable or SD card adapter on PC.
You did install CWM properly and aren't still using stock recovery?
Click to expand...
Click to collapse
Help in 10.1 CM install
thutchinson85 said:
Problem has been solved. I used the USSD code for reset, went to stock and re did everything and a way I go. Everything works no. What I did before is beyond me. Thanks alot to everyone who has offered their help! Greatly appreciated...
Click to expand...
Click to collapse
Hi,
what did you mean you went back to stock? and what is USSD?
here are my issues:
Hi, I really love this CM 10.1 ROM I am running the 10.1 201330209-unofficfial-quinctatt. Everything works fine except when I reboot the phone it loads the boost screen starts up and then freeze once done with the boot screen.
SO I need to restart the phone a few times to be able to get it back on.
---also I have 5.8.4.3 CWM in stalled and try to use ROM manager when it works even got the paid version but booting into CWM works best.
I am unable to install the latest cm-10.1-20130306-EXPERIMENTAL-quincyatt-M2.zip. I get a.
--- "zip status 7 aborted message.
Also when I try to install cm-10.1-20130304-EXPERIMENTAL-quincyatt-M2.zip. it installs fine,
But when I try to place calls.
---there is no sound on the speaker or external or internal.
I would like to stay current on the nightlies but are these just some of the glitches that come with it?
---Also I tried installing the GB-modem because my GPS wont lock, I think that is when the phone quit allowing me to make calls(no sound on speakers) which help the gps a little I guess? not really.
I am now back on the i717UCLF6 baseband.
If it wasnt for my nandroid back up I would be totally LOST!
I mostly use liquid Mod it works best, love it! but would like to be on 10.1 CM. Still no gps lock though. I REALLY NEED GPS, i drive a lot for work.
I know there is a lot going on here buy ANY! help is very much appreciated!
Install the latest TWRP recovery ...IMHO And although I might get flames thrown for this, use recovery to flash directly, and not through the rom manager app.
It has caused users some grief...
Regarding your sound and boot errors, boot into recovery and wipe all caches ....cache/dalvik cache .....then reboot too test. It sounds as if your flash may be dirty somehow. And if restoring apps to your new roms by using titanium backup or other apps, restore only the APK and not the associated data stored by those apps.
CM nightly builds are buggy yes, and will have errors not found in stable builds. But having used the same build you are referring too only a day ago, I can tell you that my sound was okay with the M2 rom.
And I commend you on the creation of a proper nandroid backup. It seems all too often we find users in real trouble with no backup in their pocket to save them.
Call me anal retentive, but I flash bleeding edge tweaks every day, and I keep backups compatible to all 3 recoveries we have for the note just for this type of emergency.
The latest TWRP and a cache cleaning should help you with both the current build, and future builds to come.
Good luck, and happy flashing ...g
Sent from my SAMSUNG-SGH-I717 using XDA Premium HD app
So I was pretty determined to get Cm 10.1 running on my Galaxy Note 2 for Verizon. Before hand, I was using TWRP to do all my ROM flashings but when I tried to use CM 10.1, I was told I must use CWM for it to work properly.
Here's my issue, I tried using CWM but it kept on giving me an error and after searching for awhile, it said its because I'm trying to use TWRP instead of CWM. So I flashed CWM and it gave me the same error. Tried both Touch and regular, downgraded and upgraded to the latest CWM but still same error. So I said **** it and installed the lastest TWRP. Then all the ROMs that were giving me issues started to install flawlessly. Then I went to CWM and it gave me the same error.
Am I doing something wrong when I flash CWM? I tried both Odin and APP Update way and both with same results. After using TWRP for awhile, I actually am starting to like the CWM Touch a lot better and I want to switch but not if its going to be giving me problems every flash.
Any insight would be helpful,
and as always to everyone on this forum, thanks
Just make sure you are using the latest version of TWRP 2.5 and you will be fine. You also may need to re-download your ROM file.
Well I am, in a way, stuck using the TWRP right now but I would like to know if I can actually change it to CWM. And if so, how would I go about doing that? because flashing the CWM alone isn't doing anything for me.
wythyntime said:
Well I am, in a way, stuck using the TWRP right now but I would like to know if I can actually change it to CWM. And if so, how would I go about doing that? because flashing the CWM alone isn't doing anything for me.
Click to expand...
Click to collapse
That is the way I have always gone about getting CWM on my phone back when I wanted it. I would just flash over TWRP in TWRP and then reboot system and then reboot back into recovery and it would always be CWM. If it doesnt work for you that way then see if they have a Odin tar and if so follow the instructions to flash it in Odin. They may not have an Odin flashable though, its been a long time since I have used it and on a different phone so....
Sent from my SCH-I605 using XDA Premium HD app
Let me actually rephrase this. (My bad for any confusion)
So if I try to flash a rom using TWRP, it goes through without any issues, even the CM rom. But when I flash CWM and try flashing, it gives me the getdevice-"(t0vzwte)"-not exact".. When researching, I was kept on told its because it is running TWRP. I tell them its CWM and they told me to update my CWM. I actually like CWM a bit better, idk why. but I was just trying to get my phone 100% the way I want it.