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
Related
Hey there,
I have an interesting problem, and it has completely stumped me for the past couple days. I recently S-Off'd my Sensation, put cwm recovery on it, and set my CID to 11111111.
I haven't had any problems with that (except that I had to change computers to do it, Revolution didn't want to run right on my laptop or set the CID, so I had to use my desktop).
Now the problem comes when I try to flash a custom ROM. The first one I tried flashing was CM7. When it booted, I got a bootloop problem of the CM7 mod logo over and over. I decided maybe it was a problem with CM7 still being in alpha. Then I tried flashing HyperSensation 1.8, and got the same error (bootloop) on the loading screen. After trying various other ROMS, I realized that it was a common problem with all custom ROMS. Luckily I had backed up the stock setup, and was able to get into that. So it's not a problem with the hardware. I have only tried flashing gingerbread ROMS. I know that ICS ROMS need a new firmware, but I dont want to mess with that unless I can actually get a gingerbread ROM working first...
Any ideas? There was a thread or two about this (on other phones) but didn't have any solutions listed..
Thanks for any ideas people can give me!
TheLastGringo said:
Hey there,
I have an interesting problem, and it has completely stumped me for the past couple days. I recently S-Off'd my Sensation, put cwm recovery on it, and set my CID to 11111111.
I haven't had any problems with that (except that I had to change computers to do it, Revolution didn't want to run right on my laptop or set the CID, so I had to use my desktop).
Now the problem comes when I try to flash a custom ROM. The first one I tried flashing was CM7. When it booted, I got a bootloop problem of the CM7 mod logo over and over. I decided maybe it was a problem with CM7 still being in alpha. Then I tried flashing HyperSensation 1.8, and got the same error (bootloop) on the loading screen. After trying various other ROMS, I realized that it was a common problem with all custom ROMS. Luckily I had backed up the stock setup, and was able to get into that. So it's not a problem with the hardware. I have only tried flashing gingerbread ROMS. I know that ICS ROMS need a new firmware, but I dont want to mess with that unless I can actually get a gingerbread ROM working first...
Any ideas? There was a thread or two about this (on other phones) but didn't have any solutions listed..
Thanks for any ideas people can give me!
Click to expand...
Click to collapse
Hi,
Did you root your phone?
Did you flash the superwipe zip first?
Also are you getting full reboots with HTC splash screen then animation or just the animation looping? Sometimes I have to let mine loop for 5 minutes after first boot of new rom before it settles.
Sent from my Sensation XE using XDA App
I guess I hadn't done everything.. I didn't factory reset before flashing the new ROM... As soon as I did that it boot right in. That's a bit odd to me, as I didn't have to do that with my last phone.
Anywho, solved.
Sent from my Sensation using XDA App
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.
I just installed UCLD2 Smooth ICE 5.0 followed his instructions and I like the Rom, but I have an issue. My home button and search button do not work at all. I've gone into the settings to see if there is anything to change what the buttons do, but I've found nothing.
Does anyone know what could be causing this? Or what I can do to fix it.
I had the same issue with flashing sky is. I did a nandroid recovery, then reflashed the whole thing and allowed the system to settle longer than the suggested 5 minutes. It works great now. Buttons are fine.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Well as it turns out that was only one of a myriad of problems, I may or may not have permanantly bricked my phone. I let the system settle, but now the screen isn't very responsive when I try to do anything on it. I also tried returning to stock, and have had the same problems.
I don't have any idea what happened, but it seems to be like a kernel problem.
CrazyLineman777 said:
Well as it turns out that was only one of a myriad of problems, I may or may not have permanantly bricked my phone. I let the system settle, but now the screen isn't very responsive when I try to do anything on it. I also tried returning to stock, and have had the same problems.
I don't have any idea what happened, but it seems to be like a kernel problem.
Click to expand...
Click to collapse
If it turns on then its far from bricked. What was your method of returning to stock?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
There's been way too much of this nonsense recently. You don't even know what a brick is. All the new guys need to stop flashing everything they can get their hands on. Stop and read before you do this stuff to your phone. I read for almost a whole month, everything I could find before doing anything. Before I even flashed anything, I had everything needed to fix and return to stock, and made sure I completely understood what I was doing. Read and understand before you break stuff so you can fix it!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I...I....I give up Congrats noobs not just op you have killed my faith in humanity you all have won and destroyed my spirits
Sent from my SGH-T989 using Tapatalk 2
When most of us first installed the leak the fix was to install it again with the 1 click or factory reset.... Are you coming from stock gb or stock ics leak?
Edit: nrm and dx you guys crack me up
CM9 Skyrocket
I didn't flash whatever I could get my hands on thank you. I flashed NexusMod 4.3 Nexus UI first about a week and a half ago. Then I wanted to try and get something a little more like stock, but still ICS so after READING ALL THE INFORMATION on the post for ICS Smoothie v2 I flashed it after wiping data, cache, and dalvik and following the instructions regarding an ICS radio which I had not followed previously with Nexus Mod when I flashed it. Then the problems started.
There is no lockscreen even when the phone decides to work. When I start up the phone. Process.google.acore force closes as does process.google.gapps
Also when I unlock the phone the screen will respond to 1 maybe 2 swipes to find a homescreen then it'll hang.
I used ODIN to return to stock following the instructions on the Stickied post about doing so in the Development section. Also I'm sorry if some of what I said comes off rude I've just been trying to fix this for about 4 days with no luck and I really need some help.
Also I would've responded sooner, but it's finals week at my college so I've only got so much time.
Also I apologize for calling it a brick even though it was not. I do know what a brick is. It's when your device is unresponsive and will not turn on or do anything. It'a a paperweight or a brick.
I was freaking out my bad. I am sort of seasoned I was rooting my HTC Inspire when I got it almost a year ago, and I put ICS on it when the first leaks started coming out. I'm sorry I'm new to this phone. I will be getting better trust me. I just need some time to get used to the different quirks involved in this phone compared to my last one.
CrazyLineman777 said:
Also I apologize for calling it a brick even though it was not. I do know what a brick is. It's when your device is unresponsive and will not turn on or do anything. It'a a paperweight or a brick.
I was freaking out my bad. I am sort of seasoned I was rooting my HTC Inspire when I got it almost a year ago, and I put ICS on it when the first leaks started coming out. I'm sorry I'm new to this phone. I will be getting better trust me. I just need some time to get used to the different quirks involved in this phone compared to my last one.
Click to expand...
Click to collapse
My suggestion still stands use the ics leak 1 click then root see how you like stock ics twiz if you want a more custom rom then goto cwm and wipe cache , factory reset, then in mounts wipe sys, wipe cache and wipe data do all of these 3 times before installing rom and kernel always let.it sit a few minutes to settle....
CM9 Skyrocket
Ok I'm sorry for causing all of these issues I think I found a solution. In the General section and since I can't post links it is entitled:
[FIX] No Power Menu, No Lockscreen, Corrupt Efs FIX! Skyrocket and T989
Sorry I didn't look in General before posting this in Q&A the General section in the HTC Inspire forum wasn't usually gonna have fixes in it maybe root methods, but not fixes for stuff like this.
CrazyLineman777 said:
Ok I'm sorry for causing all of these issues I think I found a solution. In the General section and since I can't post links it is entitled:
[FIX] No Power Menu, No Lockscreen, Corrupt Efs FIX! Skyrocket and T989
Sorry I didn't look in General before posting this in Q&A the General section in the HTC Inspire forum wasn't usually gonna have fixes in it maybe root methods, but not fixes for stuff like this.
Click to expand...
Click to collapse
What radio did you flash?
I did realize I had done it wrong I flashed this: ATT-GALAXY-NOTE UCLC5 radio
but it was the one located in the post for Embryo 2.2 and I didn't flash the embryo rom, so the radio file which Mohan made specifically for his rom didn't go over well with the rom I flashed.
I did get back to stock eventually. It just took a few tries and the efs fix. I'm now putting CWM touch back on my phone and flashing a Gingerbread Rom because ICS on our phone is still a little too iffy for my likeing. I'll probably just wait till Samsung releases source for the kernel and cook my own rom.
CrazyLineman777 said:
I did realize I had done it wrong I flashed this: ATT-GALAXY-NOTE UCLC5 radio
but it was the one located in the post for Embryo 2.2 and I didn't flash the embryo rom, so the radio file which Mohan made specifically for his rom didn't go over well with the rom I flashed.
I did get back to stock eventually. It just took a few tries and the efs fix. I'm now putting CWM touch back on my phone and flashing a Gingerbread Rom because ICS on our phone is still a little too iffy for my likeing. I'll probably just wait till Samsung releases source for the kernel and cook my own rom.
Click to expand...
Click to collapse
I see, the note modem corrupts the efs partition. Glad you read some things and got it fixed!
Okay so I call myself scouring the net for anyone who has had the same issue as me. I am stock with BeastMod kernel on 2.20. Also WiFi tether tweak installed. Whenever I restart phone bookshops three or four times then eventually boots. Everything I have found had been for infinite bootlooping. All I really ask for is a point in the right direction. This is my first HTC phone since I was loading android from SD card on HTC Pure. I have done a little bit with the Inspire and have unbricke Evos for friends but just can't figure this situation out. Any help would be appreciated.
Update: Fixed by flashing boot.IMG from stock then refreshing kernel and boot.IMG created by kernel. Now I am experiencing WiFi error so it looks like I will be starting from scratch again.
Sent from my HTC One X using xda premium
change kernel settings or try another kernel
Tried that. Went to stock kernel and experienced the same issue. I noticed that there was no need to fastboot flash the beastmod kernel. I used flashgui to flash stock kernel and sure enough on restart a fee bootloops then boom it starts. So I reinstalled beastmod because it's just an awesome kernel and the problem persist. Another question I tried flashing a Rom which led to my internal not being read. Fixed that problem and the bootloops have been happening ever since. Guess I just need to start from scratch. Just did that a week ago when I trade my Skyrocket for this phone (got lucky there).
Sent from my HTC One X using xda premium
don't factory reset in bootloader or it will corrupt your sdcard. have you tried flashing a custom rom?
Haven't flashed a custom yet. Just can't really find one I like well enough to flash.
Sent from my HTC One X using xda premium
Alrighty, this is one of the weirdest things I've had happen with a phone since I started doing this on the original Droid. Lately I've been using Jellybeans Rom, its been great and my longest running ROM so far, but like a lot of people here I have to try out new stuff quite often just to try it. Well anymore I cant seem to try much else, I wanted to run the newest Liquid Smooth 2.3 ROM that just hit and it wont work at all really, before I redid the whole phone every time I flashed LS 2.3 I couldnt even hit the start button when the ROM first installed, when I did it wouldnt do anything and then the screen would go black and I would have to hard reset or battery pull. Next boot up seemed to go fine, got my gmail up and running and titanium downloaded and then after that, hitting settings options would lock up the phone in just about any app I had, never even got around to trying to restore anything with titanium.
Re-flashed LS 2.3 three or four times and nothing changed, tried fixing permissions, fully wiping, etc. didnt matter. So naturally I figured it was simply the ROM on my phone (mind you LS 2.2 worked fine before) so I went and decided I would try out Avatar ROM, CM based with MIUI themes, this ROM did pretty much the same thing. No idea why...
Next I figured something maybe was wrong with my phone so I went back to the drawing board and started from factory with ODIN, I redid my ROM with stock/root, unlocked the boot loader again and redid custom recovery and all the same thing with LS 2.3 happened all over again, Stock ROM worked great for the bit of time I used it before I tried to reflash LS 2.3 again, Now I'm back running Jellybeans v.15 and it runs perfectly fine as well.
I really have no idea what the problem is, both of those ROMs I've tried are CM based original development, so I'm wondering if its something in there thats causing an issue over the TW ROMs I've used. I've used other TW ROMs with decent success, but I've had some issues with those too that you wouldnt think should happen but it wasnt anything worth noting, just like Jellybeans the best, but even some of those would give me slow down problems and occasional lock ups when Jellybeans doesnt.
Anyone have any clue as to what could be causing this? I used to be able to run non TW roms just fine and its only been in the past month that this has started happening that I've noticed, I've had the phone since January and have been flashing away this whole time and now I cant seem to try out any more ROMs without having major issues......ugh
Your situation is a very random situation but I have something similar happened to me involving TW ROMs in that some of them froze on me. I had to flash the stock ROM.
Bump, anyone having any kind of similar problems?
Sent from my SCH-I535 using xda premium
Vidfreek said:
Bump, anyone having any kind of similar problems?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
If you've only had these issues in the last month, it could be attributed to the Linux 3.4 kernel that every AOSP rom has moved to. I wouldn't let that stop you though. Are you downloading these rom zips over WiFi or mobile data? Were your downloads taking awhile as well? I know either GOO or AFH was having server issues recently which may have coincided with your downloads. I'd suggest using WiFi if you aren't already and trying again?
Sent from my SCH-I535 using xda app-developers app
Yeah its only been fairly recent and all roms I've tried have been updated since the very end of april, if my phone has major problems with that linux kernal am I going to be able to flash anything again? Everything I downloaded was over wifi but I can try all the downloads again but I'm thinking that won't fix anything, just weird stuff
Sent from my SCH-I535 using xda premium