So I successfully rooted my note 10.1 and wanted to try some custom roms out. Cm, Paranoid Android, etc. I've flashed 3 different roms only to come to a dead end with this issue. Rom flashes correctly, ,when it comes time to connect to wifi, it scans, tries to connect and then just says saved. Never actually connecting.i revert back to factory rooted TW and all is good. Can't figure this out. ?..
Sent from my GT-N8013 using XDA Premium HD app
Related
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
Call me crazy but maybe I'm missing something.
I have a t-mobile Samaung Blaze 4G. I was running stock+root rom and everything was fine. I downloaded Goomanager to check it out and it had an update (pa_t769-ota-eng.thomas.zip) so like a total noob I flashed it (yes I made a back-up) From that I got Paranoid Android 4.1 and its ok if you download the GApps but now it wont take any flashes for 4.0.4 including the back-up. It gets stuck on bootlogo. It seems like anything with a factory stock bootlogo will get stuck and I want to go back to 4.0.4 because the 4.1 is unstable and reboots randomly alot throught the day. any help would be greatly thanked.
EDIT: I am now running Paranoid Android 254v4 and it is working flawless. Goomanager is also running great. People should check it out.
I had that same problem with paranoid. I even did a fresh install just to make sure I didn't forget something. I ended up just flashing a new rom
Sent from my SGH-T679 using xda app-developers app
Hello Everyone,
I am a new user of XDA and did much reading. I must be honest here, I have been reading quite a bit and love to do some crazy stuff with my Sony Xperia1
I actually had the stock rom for Xperia S which was really slow and problematic. I then loaded the Cyanogenmod 9.1 to try an resolve performance issues. Unfortunately, that was not to be and the system is very slow, unresponsive, and heats the phone up quite significantly even when it is not in use.
Now, when I was loading the Cyanogenmod, I had to copy over the boot.img file along with CWM. I noticed that the boot splash screen now showed "FreeXperia" instead of the regular SONY logo. Also, I was able to get into CWM by tapping the screen upon boot.
Anyhow, due to the poor performance of Cyanogenmod, I decided that I would try MIUI and when I installed, I tried to boot and the phone eventually showed the MIUI splash screen and got stuck on that.
Now, I am trying to get into CWM but that is no longer possible. I want to load another rom and is not working because i can not get into CWM.
Can someone advise to a work around to get back to stock rom so that i can start my hacks again??
Anyone!!??
Not sure if this works on a Sony but you can get it into download mode and flash stock through odin or hemidal
Sent from my YP-G70 using xda app-developers app
Nope that doesn't work on Sony!
Just Samsung recognizes Odin!
And as for the guy, did you flash the boot.img of cm while using cm Rom
But while you switched to miui
Did you flash back stock or stock based kernel?
As the cm kernel won't work on Miui Rom
Sent from my MT11i using xda premium
Alright guys so im on HBOOT 1.14 tried several roms all cant connect to wifi, I tried flashing the partions with no luck. I want to know what you other guys have done to fix this issues.
adolfo778 said:
Alright guys so im on HBOOT 1.14 tried several roms all cant connect to wifi, I tried flashing the partions with no luck. I want to know what you other guys have done to fix this issues.
Click to expand...
Click to collapse
The only fix is update with OTA or downgrade the Hboot.
I ran into the same issue with 3 other ROMs today. Finally used TWRP recovery (instead of the CWM I had been using) and installed JellyBam 4.0.0 (and flashed the boot.img with fastboot.)
I can't say that's what fixed it because I can't honestly say the other ROMs were the cause of the problem. All I can tell you is that within minutes of rebooting after the install, my phone connected to wifi.
Good luck with it - I'm sure others who actually know what they're talking about will offer more than I can.
Thanks guys just wanted to see what my solutions were.
Sent from my HTC One S using xda app-developers app
david251 said:
I ran into the same issue with 3 other ROMs today. Finally used TWRP recovery (instead of the CWM I had been using) and installed JellyBam 4.0.0 (and flashed the boot.img with fastboot.)
I can't say that's what fixed it because I can't honestly say the other ROMs were the cause of the problem. All I can tell you is that within minutes of rebooting after the install, my phone connected to wifi.
Good luck with it - I'm sure others who actually know what they're talking about will offer more than I can.
Click to expand...
Click to collapse
Don't help with Sense based roms.
Any guides or links on how to update? I'm on my phone atm.
Seems every HTC device is different when it comes to this stuff lol
Sent from my HTC One S using xda app-developers app
Never had wifi issues on my 1.14. Although the only sense-based roms Ive used have been ICS ones. Maybe the wifi wouldnt work on JB sense roms.
Wifi works fine on JB AOSP roms though.
Similar problems with wifi. I've tried several ROM's, lastly Jellybam 4.0.0, came from CM10, before that some other custom rom, now stock 3.16.401.8. I think my wifi hardware is broken. Going tomorrow to warranty service. I'm not expecting the warranty to cover this since I tried several ROM's, but I will try and see what happens.
lukevader said:
Similar problems with wifi. I've tried several ROM's, lastly Jellybam 4.0.0, came from CM10, before that some other custom rom, now stock 3.16.401.8. I think my wifi hardware is broken. Going tomorrow to warranty service. I'm not expecting the warranty to cover this since I tried several ROM's, but I will try and see what happens.
Click to expand...
Click to collapse
Downgrade your hboot man worked like a charm. If you need any help with the process just lmk
Sent from my HTC One S using xda app-developers app
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