hi all,
Ok, I'm new to this stuff.
1. used the simple root and it worked great.
2. I then flashed CM7 and it worked great except market was not on it.
3. I downloaded and flashed gapps-hdpi-20101114-signed.zip by mistake, not realizing I had to use another gapps.
4. After I flashed it, the cm7 and android setup screens kept cycling between each other.
5. I restored to clockworkmod (sp) and then deleted the gapps and tried to then flash cm7. It didn't cycle between cm7 and android setup, but the cm7 screens kept cycling and never got past that.
6. I thought perhaps it was just cm7 now, so I tried miui and it's doing the same thing. It's cycling between the gingerbread man and MIUI with the status bar and won't do anything else.
Very frustrated. what have I done and how do I fix it?
Thanks folks,
Brett
You could flash the stock ruu and start over.. or, wipe everything flash cm7 and then flash gapps.
Sent from my Desire HD using XDA Premium App
bdws1975 said:
hi all,
Ok, I'm new to this stuff.
1. used the simple root and it worked great.
2. I then flashed CM7 and it worked great except market was not on it.
3. I downloaded and flashed gapps-hdpi-20101114-signed.zip by mistake, not realizing I had to use another gapps.
4. After I flashed it, the cm7 and android setup screens kept cycling between each other.
5. I restored to clockworkmod (sp) and then deleted the gapps and tried to then flash cm7. It didn't cycle between cm7 and android setup, but the cm7 screens kept cycling and never got past that.
6. I thought perhaps it was just cm7 now, so I tried miui and it's doing the same thing. It's cycling between the gingerbread man and MIUI with the status bar and won't do anything else.
Very frustrated. what have I done and how do I fix it?
Thanks folks,
Brett
Click to expand...
Click to collapse
Follow the instructions here step by step and it will have you up and running in MIUI:
http://forum.xda-developers.com/showpost.php?p=11643155&postcount=1
Read forum rules about where to post. Closed.
Related
I've noticed other people seem to be having this same problem and there hasn't really been a distinct solution that I can see, so hopefully this question will be helpful in the future and not repeatative.
I've been trying to update to CM7 from CM 6.1.2 on my Evo. I followed instructions from here http://forum.xda-developers.com/showthread.php?t=902051 and downloaded all the recommended software. First I tried to just flash the rom, then the kernal, then the gapps. All seemed well at first, and I got past the Evo 4G screen, but it got stuck booting on the Cyanogen animation (the arrow just keeps going!)
Then I tried to wipe the Davlik-Cache, and rebooted again. I left the phone alone for about 45 minutes, and it still got stuck on the Cyanogen animation.
Finaly, after searching through the forums, I found another post which suggested I do a hard reset then flash the rom, kernal and gaaps then clear the cache and davlik-cache. Still, I'm stuck on the animation. I have a nandroid backup, so I can get back to 6.1.2, but I'd really like to get CM7 working, anything else I should try?
You should't have to do the kernel separately unless you have a specific reason for doing so the ROM comes with a kernel for you. I had a similar problem with my HTC however I was able to get it resolved by installing gapps. Here's what I did -->
Used ROM Manager to go back to working ROM
From working ROM, accessd ROM Manager and chose rebooted into recovery mode
Once in recovery cleared/wiped everything (cache, data, delvik) installed gapps then cm7
Restarted
It did take awhile after restart to get going however once it did it worked marvelously!
Hope this helps and good luck!
Reboot
Similar Problem, Defy CM7 Bootloop
The first time i tried installing CM7 I got a boot-loop. I have tried at least 7 different tutorials all with different variations of flashing this and wiping that yet none yield results. Still stuck at boot-loop.
The most recent thing i have done was used RSD Lite to flash
"JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P016_A016_HWp3_Service1FF.sbf"
this got my phone running again, i then pulled off some magic by rooting using a combination of super1click, Z4 and installing superuser myself. after that i copied the files for a bootmenu into my /data/ folder. using CWM Recovery v2.5.1 flashed
"freq_F_US_342_107-850-1700-2100-signed.zip"
to get my 3G running again, and gave up of CM7.
If anyone has anything that could help id appreciate it.
(ps. i've tried many variations of wiping things and re-flashing things)
Appologies for not replying to the original MIUI thread. I am not a new user and i am very experienced in flashing roms etc, especially on samsung devices. I have been around for a while now but this is my first post so i cannot post in the dev section yet.
Last night i flashed MIUI to my infuse. I followed the instructions in the op here exactly.
http://forum.xda-developers.com/showthread.php?t=1278053
I had no problems flashing and everything was successfull, however there were 2 major issues. First being the soft keys. The four buttons menu, home, back, and search buttons did not function at all. They werent even backlit. The volume rocker and power buttons functioned fine. I reflashed from blue cwm twice and still nothing.
This is where i ran into my second issue. There were no posts about anyone having the soft key issue however i did notice alot of people losing their recover and being stuck on the samsung boot screen. This eventually happened to me.
I went to samfirmware and downloaded 2.1 and odin'd it, then odin'd the community kernel to get ext4 and red cwm then restored my nandroid so i am back to normal. I wanted to post about my soft key issue but as i said i had to post in q&a due to my lack of posts.
Any suggestions? if not, i at least wanted to inform the dev of the issue.
Thanks
have you tired CM7, just asking cuz they have almost the same bugs....so i would curious to see if your softkey issue transfers to that rom as well. and if not........
i would try loading up CM7, wiping from the orange CWM and flashing MiUi from there. it Should have worked the way you did itk if you were coming from stock. but who knows maybe seeing if it happens on Cm7 will lead to your answer.
just an idea though
no i havent been able to try cm7 yet as i dont have a build environment set up anymore and havent seen a release yet, would love to give it a shot if someone wants to send me a zip.
i really hope it doesnt have the same issue or ill have to donate this thing to my fiance and get a gs2 or something lol.
Check your mail, you seem to know what your doing so test it out see what happens.
Happy Flashing
Happy flashing indeed, thanks for this im going to give it a go right now, bbl with results.
Hell the only reason i was flashing miui to begin with is b/c i am currently unable to build cm7 so hope this works..
Thanks a ton!!
Ok so heres how it went down.
After my fail last night with the softkeys i did a little research and flashed serendipity s7. So with the cm7 zip you sent me i started out flashing over this since they are both ext4 i didnt think there would be a prob.
Followed your instructions, wipe, flash, pull battery, wipe, flash. After the first flash i was in orange cwm. I didnt give it a chance to boot until after the second flash obviously, but it would boot directly into orange cwm everytime.
From there i decided to odin to stock and flash the community kernel again.
Now that i was back in red cwm and formatted to ext4 i repeated your original instructions and everything flashed just fine.
As far as the soft keys, i have no issues at all. Everything is working just fine.
I was flashing from 2.1 uke3 last night, and thats also what i flashed with tonight and was successfull with.
Anyways thanks for the help glad to say im not having the issue with cm7. much appreciated
--forgot to add i am going to try to reflash miui coming from cm7 and see how that goes if i still get the same issue
--Okay, booted to orange cwm, wiped and flashed the same miui zip as before. Only one wipe and one flash no battery pull or anything. Everything flashed perfectly and my soft keys are functional. Not quite sure what the deal was before but miui is booting just fine. I'm afraid to boot recovery to many times as everyone seems to lose it after a few uses. We'll see how it goes for now, never been an miui fan to iphoneish for my taste but until i can build a recent cm7 rom i need something, was getting bored with rooted stock.
Thanks again for your help!
powdered_donuts said:
Ok so heres how it went down.
After my fail last night with the softkeys i did a little research and flashed serendipity s7. So with the cm7 zip you sent me i started out flashing over this since they are both ext4 i didnt think there would be a prob.
Followed your instructions, wipe, flash, pull battery, wipe, flash. After the first flash i was in orange cwm. I didnt give it a chance to boot until after the second flash obviously, but it would boot directly into orange cwm everytime.
From there i decided to odin to stock and flash the community kernel again.
Now that i was back in red cwm and formatted to ext4 i repeated your original instructions and everything flashed just fine.
As far as the soft keys, i have no issues at all. Everything is working just fine.
I was flashing from 2.1 uke3 last night, and thats also what i flashed with tonight and was successfull with.
Anyways thanks for the help glad to say im not having the issue with cm7. much appreciated
--forgot to add i am going to try to reflash miui coming from cm7 and see how that goes if i still get the same issue
--Okay, booted to orange cwm, wiped and flashed the same miui zip as before. Only one wipe and one flash no battery pull or anything. Everything flashed perfectly and my soft keys are functional. Not quite sure what the deal was before but miui is booting just fine. I'm afraid to boot recovery to many times as everyone seems to lose it after a few uses. We'll see how it goes for now, never been an miui fan to iphoneish for my taste but until i can build a recent cm7 rom i need something, was getting bored with rooted stock.
Thanks again for your help!
Click to expand...
Click to collapse
Glad it all worked out.....
Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.
I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk
I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA
Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.
Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.
I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though
I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).
I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.
Ive looked just like the rules stated. Yet i can not find out a reason to my problem. Im no noob whenit comes to flashing kernels and roms. with that being said here goes. I have jst aquired a Nexus S. I traded it for my old iphone 4 felt good to be back to android. anyways I have Kangy-U loaded up and ready to go just flashed it yesterday. today I figured after some resarch I would flash Air kernel. after I flashed it through recovery (CM) it goes through the proces and says it s flashed. I boot back into kangy and look under settings and find Its still stock. I tried again, same problem. by this point I figured bad download redownloded same problem. so I then figured ok they are just not playing nice together. I trie a different one. this time cyans stock universal still same problem.
Is there a step Im missing?
Have you posted over in the thread for the ROM? Never heard of a kernel not flashing like that with the recovery saying the flash was successful.
Sent by pocket technology
Try reflash the rom, just a guess.
Sent from a sandwich using my Nexus S
ya i reflashed everything wiped data system cache boot. then it worked. I do know CM can be weird sometimes. all is figured out. thanks guys.
It kood just be the kernel
Sent from my Nexus S 4G using xda premium
I keep running into problems after flashing any ICS custom ROM. (Maybe I should try going to an ICS Stock ROM first).
Most times it just loops on the loading screen.
- Phone is rooted of course.
- I usually have the Emancipation GB custom rom before flashing to this one or a Stock GB with root and red CWM.
- I follow instructions to a 'tee'
- When I do reboot, it loops at Samsung logo.
The last time I tried (Dark Knight ICS Rom), just recently, I flashed then rebooted into recovery (from advance-boot to recovery), and it didn't go to recovery mode, it just looped.
So currently I'm on Stock GB with root and red CWM.
What am I doing wrong?
What are some things I should consider?
Some of the GB custom roms are nice yes, but I rooted mainly so I could get ICS.
Thanks for any help anyone can offer/
http://forum.xda-developers.com/showthread.php?t=1610374
Wipe cache/Wipe dalvick/factory restore
You flash the rom
Then Gapps
Restart....Then it bootloops?
omansteveo said:
http://forum.xda-developers.com/showthread.php?t=1610374
Wipe cache/Wipe dalvick/factory restore
You flash the rom
Then Gapps
Restart....Then it bootloops?
Click to expand...
Click to collapse
Yeah pretty much.
Only happens for ICS ROMs. Well the ones I've tried.
Still new at this, so I'll keep trying and that link you posted is one of my most visited links.
Skebodan said:
Yeah pretty much.
Only happens for ICS ROMs. Well the ones I've tried.
Still new at this, so I'll keep trying and that link you posted is one of my most visited links.
Click to expand...
Click to collapse
Ive been at it for about 5 months now and have bricked my phone like 20 times ha ha...so Ill do what I can to help. I've been successful going from GB to ICS to JB and vice versa. Try this also....When you phone starts to boot loop pull the battery and boot into recovery. Then wipe everything again and reflash the rom and gapps
omansteveo said:
Ive been at it for about 5 months now and have bricked my phone like 20 times ha ha...so Ill do what I can to help. I've been successful going from GB to ICS to JB and vice versa. Try this also....When you phone starts to boot loop pull the battery and boot into recovery. Then wipe everything again and reflash the rom and gapps
Click to expand...
Click to collapse
lol alright thanks man. I've bricked mine about twice now. Just started about a week lol.
I'll give you an update in about 2 hours. Got to get ready for work
I have gone from Emancipation to this in the past with no prob... just follow his instructions for install and you are good to go - credit and thanks to Entropy512.
http://forum.xda-developers.com/showthread.php?t=1601844
Pony Express said:
I have gone from Emancipation to this in the past with no prob... just follow his instructions for install and you are good to go - credit and thanks to Entropy512.
http://forum.xda-developers.com/showthread.php?t=1601844
Click to expand...
Click to collapse
To be honest I was running from using Entropy's build.
Fear of it being too technical (It's actually the first thread I saw when I was thinking of going to ICS). So I used it and my phone is up and running now on ICS.
Won't be able to play around with it as much until I get home from work but thanks for mentioning it again.
Now to go and read the thread all the way through (kidding) well see if the problems he had are still occurring.
Thanks again guys.
For me, using Entropy's build made it easy to go to any other ICS rom for the Infuse- it is great as is or as a "stepping-stone" to other ICS builds. Glad it worked for you.
Yea man it was nice. I don't even need the other custom roms, this has everything I wanted.
And since it has a theme chooser, I'm good for life on the look of it.
I might try and customize my own stuff in the future but for now, all is right with my Infuse. I was going to get the Note but I got a brand new phone right here.