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.....
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)
so my sgs4g was rooted and got on gb with the gb starter pack thread, after which i jumped around between a few roms and am currently running octaneGB.
however, it has always had stability problems, and i can't figure out why. possibly because i messed up bootloaders? i'm pretty sure it can't be the fault of the roms i flashed.
from here, all I want is a stable phone.
can i wipe the phone as it is and then use the oneclick heimdall SMS kj6? would this put me on rooted GB with CWM and good bootloaders? could i simply cwm flash a rom like valhalla after that?
any advice would be appreciated, thanks!
nvertigo said:
so my sgs4g was rooted and got on gb with the gb starter pack thread, after which i jumped around between a few roms and am currently running octaneGB.
however, it has always had stability problems, and i can't figure out why. possibly because i messed up bootloaders? i'm pretty sure it can't be the fault of the roms i flashed.
from here, all I want is a stable phone.
can i wipe the phone as it is and then use the oneclick heimdall SMS kj6? would this put me on rooted GB with CWM and good bootloaders? could i simply cwm flash a rom like valhalla after that?
any advice would be appreciated, thanks!
Click to expand...
Click to collapse
Yes, you can use the one-click to put KJ6 on there then flash a different ROM via CWM.
Personally I've had the best experience with Valhalla ROMs. Last night I just flashed RAVERX3X latest Valhalla Black build. Its low profile so it's quick and responsive, and even better, not a single instability issue.
Sent from my SGH-T959V using XDA App
thanks for the advice guys!
I did the first flash step, which worked successfully and rebooted my phone. then i tried to flash the bootloaders that came with it, but uploading PIT 1/10 failed, and it froze trying to end session. i pulled the battery and the phone seemed bricked, but i connected the cable and oneclick said it was connected (no download mode screen, no lights at all). so i did the initial one-click flash and let it reboot again, then flashed valhalla black.
nothing SEEMS to be wrong, but i'm a little scared. can anyone weigh in on what happened?
You're ok. I can't explain what happened but people have reported similar issues, nothing on the screen but it can be seen in ODIN, and were able to recover (as you did) just fine.
Sent from my SGH-T959V using XDA App
This section of XDA is small, but good in terms of quality.
I just flashed Raver's Cyanogenmod/Valhalla hybrid and it is smooth and stable.
One-Click...
At the beginning of the week, I still had Froyo on my device.
I used Bryan's one-click (SMS-KJ6-beta2d_Stock-Rom_with_Bootloaders-One-Click.jar)...
(I had a scare, too... which involved the so-called "Rainbow screen" -- but FB suggested I run the one-click, again and also to do the Bootloaders -- and everything turned out ok).
But, I needed to get CWM 5 (and, that particular one-click had CWM 3.0.2.8x)
So, I flashed an update of Bryan's kernel (sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip)
And, because I was feeling overjoyed at all the goodness that I'd seen so far, I flashed RaverX3X's rc3.zip (from Team Acid's Source Forge site)...
And, life is really, really, really... good.
yep
+1 Valhalla black edition! Installed today and love love love.
ok... my phone is now crashing and rebooting all over the place after flashing valhalla black. it seemed fine for the first hour. should i try the one-click again? or did i not wait 10 minutes after flashing the rom, maybe?
anyone know what could be the problem?
thanks in advance!
nvertigo said:
ok... my phone is now crashing and rebooting all over the place after flashing valhalla black. it seemed fine for the first hour. should i try the one-click again? or did i not wait 10 minutes after flashing the rom, maybe?
anyone know what could be the problem?
thanks in advance!
Click to expand...
Click to collapse
Not sure about the crashing but I experienced reboots because of the kernel Valhalla Black uses. There are fixes out there for that part of the problem but what you should really is perform a factory data reset, do the one to get a ROM with CWM on it, then use CWM to install Valhalla Black per the instructions on the page for it. I've a feeling you'll be much more stable after that.
As for the 10 minutes, that's basically to allow your phone to rebuild the Davlik cache (cache with optimizations for your apps). Definitely let it sit while it does that just to be safe.
thanks yet again. will try this asap!
can i assume that my bootloaders are correct after the weird issues from the last page? you mentioned that it happened to several people, but it still bothers me that technically it never got past 1/10 uploading PIT file :x
also, regarding the problems with the kernel, can anyone point me to a kernel that works with valhalla final and is known to be fully stable? i want to try to do everything to get the phone usable.
nvertigo said:
thanks yet again. will try this asap!
can i assume that my bootloaders are correct after the weird issues from the last page? you mentioned that it happened to several people, but it still bothers me that technically it never got past 1/10 uploading PIT file :x
also, regarding the problems with the kernel, can anyone point me to a kernel that works with valhalla final and is known to be fully stable? i want to try to do everything to get the phone usable.
Click to expand...
Click to collapse
If it was fully booting and you weren't getting the "rainbow" screen, then your boot loaders are fine. If in doubt, go check out bhundven's one-clicks, and run one of them - twice. The first time it doesn't let you check the boot loader box but the 2nd time it does.
Valhalla Final comes with bundven's beta 2c kernel. I believe people are running that without issue. Keep in mind Valhalla Final and Valhalla Black are two different ROMs with two different kernels.
I did a one-click back to stock (factory reset, cache wipes, etc.) & am running bhundven's latest beta kernel with no problems (thus far).
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.
ok so i rooted a few weeks ago and downloaded the usual apps. super user titanium back up and clock work mod. tried to flash a rom with clock work mod and got the e:signature verification failure message. found a post for a kernal that made clock work mod actually work so i tried to flash a rom. zSimplyAOKPV5_Dark to be exact. now it sticks on boot screen. i have searched for hours and cannot find a way to fix my problem. its my first rooted android and first attempted rom flash and i botched it right off the rip. please help?
Depending on what you did beforehand, you have some options.
If you have backed everything up previously, just flash back to stock with one of the one-click stock roms in the Development section (they're in a sticky).
If you haven't backed everything up, try holding V+/V-/power until it reboots. If it doesn't take you to recovery, you can try to flash a kernel (most likely one that would match the version of android/rom you were running prior to this flash) and see if it lets you into recovery. You'll have to flash it with either Odin or Heimdall, after rebooting into download mode (power off, hold V+/V-, insert USB).
If that doesn't work, though, the stock flashing would probably be your best and/or only bet.
it wont allow me into recovery though i can get to download mode by pulling the battery and pressing just the volume +- and plugging in the usb. i was trying to flash an ics slim rom. thanks for your very speedy response.
i have now tried to flash a stock rom however it is not working from there even with the stock kernal. now it is hanging on the at&t screen.
ok i got it. seems the kernal i flashed to help cwd work properly was the culprit. now i dont know how im going to flash this ics rom im looking at without it.
phoenixfriend said:
it wont allow me into recovery though i can get to download mode by pulling the battery and pressing just the volume +- and plugging in the usb. i was trying to flash an ics slim rom. thanks for your very speedy response.
i have now tried to flash a stock rom however it is not working from there even with the stock kernal. now it is hanging on the at&t screen.
ok i got it. seems the kernal i flashed to help cwd work properly was the culprit. now i dont know how im going to flash this ics rom im looking at without it.
Click to expand...
Click to collapse
Flash corn kernel if you have stock gingerbread
Sent from my SGH-I897
The utility in my signature can help you flash the Corn Kernel so that you will have CWM.
I have corn kernal and odin 3 on the computer at home. Ill do that tonight. Any suggestions on a good stable rom for a noob? Preferably ics. I hated posting for fear of being flamed as a noob. My wife keeps making fun of me for it so I kinda have to get it done. I want to fix hers also. Its a great little phone it just seem a bit buggy to me. Very laggy. Thanks for all the help.
Sent from my SAMSUNG-SGH-I897 using XDA
Maybe start with a KK4 based rom such as Legend and then move up to ICS after that. I only say that because there is a bug in ICS that could render your internal SD unusable. It's rare, but when it happens you will not be happy.
Still unable to get corn kernal to flash. I've tried a few of your guys fixes but I'm gonna have to get some other updates to my computer first.
Sent from my SAMSUNG-SGH-I897 using XDA
I don't know what to do next, and I need my phone. I can answer any questions, but I wouldn't know what to start with. Can someone help??
Quick questions to answer:
1. What Rom were you on prior to flashing?
2. What Rom were you flashing to?
3. What do you see on your screen?
4. Do button presses give any reaction?
1. http://forum.xda-developers.com/showthread.php?t=1136128 v5.0, it's Gingerbread.
2. I was flashing to CM7, but it didn't flash, so I did what was probably a mistake and went straight for http://forum.xda-developers.com/showthread.php?t=1625619&page=1.
3. I see "DevilKernel" Samsung Galaxy S.
4. If I hold down the volume and power buttons, the DevilKernal boot screen will flash. If I keep the power button held down it resets, if I don't it just flashes and nothing else.
By the way, thanks.
Ok, here's what happened:
The first bootloop you were seeing with CM7 is actually a normal occurrence. You usually have to flash CM-based roms twice to get them to "take" (the first time sets up MTD over BML, the second time installs the rom).
What you're seeing now is the devil kernel trying to load up the CM9-based system, but not having all the parts in place.
Thankfully, you're not in that bad of a place. The easiest thing to do right now is to grab an Odin- or Heimdall-based one click Gingerbread stock package without bootloaders. There's a sticky in the Development section that has them, or you can grab the one in my signature.
Flash the one-click, go to recovery, and flash either CM7 twice or TWICS twice.
That should fix you up.
When I tried flashing the CM7, it said it failed. I'm not sure what went wrong. The TWICS I planned on flashing twice, but it got stuck.
Hard to say - it could be something as simple as a bad download of the flash file.
But you think if I Odin it and try TWICS again it'll work?
It should. Doing the Odin one-click will reset everything back to a factory state, which should remove all the obstacles that would normally stand in the way of a successful installation.
Hey man, for that ROM, this theme will work, right?
http://forum.xda-developers.com/showthread.php?t=1095911
I don't know anything about themes. Or this, apparently. I also got into Recovery and installed it twice, I don't really know what's going on.
So you're now fully set up with TWICS, or you're saying that it's still misbehaving?
Also, that theme should work - I had a CM7 theme that I was able to use with a CM9 rom's theme chooser. Wasn't 100%, but it generally worked.
I'm not sure WHAT is going on. The ROM seems to be working fine, I am reinstalling my apps from Titanium Backup and a "Low on space" popup is here, but that makes no sense since it's the same phone, it's a smaller ROM, and a 32gig SD Card. I also just got a text message that was "rejected due to low space".
What is going on??
It seems my phone always is unable to continue once Super Monkey Ball 2 tries to be backed up.
Look around in the cm7 thread for the dbdata full issue. I think there were some suggestions for how to deal with it in there.