Develop Bugs

[Q] Just rooted el29 but cant connect to wifi?

What i did:
I updated my phone a week ago with the ota EL29 then the next day i rooted my phone using the tools in this link:
http://forum.xda-developers.com/showthread.php?t=1433101
Then i installed clock work from:
http://forum.xda-developers.com/showthread.php?t=1342728
The wifi problem is when I try to connect:
I type in my PW as allways, and then its trying to obtain IP and then it disables and keeps doing the same thing over and over.i flashed the blazer rom following the directions countless times wiped everything and used the Calkulin's Format All before installing but no luck.
Any one know what i could be doing wrong?

Whats funny is that i did this for someone else and everything is 100% lol.
-update-
-i did a factory reset but still no luck,then i restored el29 stock rooted but sill nothing

Try flashing a ROM. Any ROM will do, but when you do:
wipe data, cache, dalvik and format system (under mounts and storage). Flash new ROM, check to see if wifi works on the new ROM. if yes, then go find a stock EL29 ROM (Do NOT restore your old one) and flash it after wiping data, cache, dalvik and formatting system again.
That should do it

Have you tried rebooting your wireless ap/router? Have you tried configuring a different channel on your ap/router? Have you tried ##72786# reset?

going to try both of these now,thanks for the replys.

Are you sure your not typing in the wrong router password?
Nah just messin with ya!

k everythings working now flashed a stock rom then wifi worked,then i wiped everything and installed blazer again but wifi did not work so i downloaded blazer again wiped everything again then it worked?maybe the first was a bad download but im good now thanks guys for the help.

my wireless router likes to do this to me, i just reboot the router and it gives my phone an ip

Problems Flashing

I am on FC14 STOCK rom ICS with rogue CWM flashed with odin. I am trying to flash to VeNuM's new rom but when I try I keep getting installation aborted. I have tried multiple ways ( flashing from internal and external sd), have redownloaded many times, and it also happens with other roms. I perform a wipe cache, dalvik, format system, and then factory reset. Then try to install from zip and i get.
finding update package..
opening update package..
installing update...
installation aborted.
any ideas?

Odin stock el26 recovery/kernel then go straight into recovery mode once it reboot. Wipe and flash from there
Sent from my SPH-D710 using Tapatalk

wwoodrum said:
I am on FC14 STOCK rom ICS with rogue CWM flashed with odin. I am trying to flash to VeNuM's new rom but when I try I keep getting installation aborted. I have tried multiple ways ( flashing from internal and external sd), have redownloaded many times, and it also happens with other roms. I perform a wipe cache, dalvik, format system, and then factory reset. Then try to install from zip and i get.
finding update package..
opening update package..
installing update...
installation aborted.
any ideas?
Click to expand...
Click to collapse
Have you used Calkulin format all zip? seems to work better for me when flashing then doing it manually.

yes i have used format all.
Im going to that odin method ill let you guys know what happens

Just to make you aware:
You mentioned before that you did some wipes and clears using CWM while on ICS. I suspect you're already in trouble but ODIN will confirm. If you run into problems specifically on data.img you will know for certain that you are bricked.
Since ODIN is your only bet right now I hope that I am wrong. Best of luck to you!

Odin sucessfully flashed, but then I used CWM to restore to ICS stock caulk. I haven't had many problems with wiping on ICS with CWM, but idk if I am just getting lucky or what. My primary goal is to just get custom roms on this thing, but it seems I can only flash stock. Prior to ICS I was able to flash blazer. IDK if im just getting bad downloads or what.

*Clarification*
As it has been reminded to me today, CWM/CWMT being the culprit of the hard bricks lately is speculation only and has not been proven definitively. I think several posts that I have made today perhaps did not make that clear enough.
When you have time you may want to read the following threads for more background:
How Not To Brick Your E4GT

got it working,
1) reflash EL26 in ODIN.
2) restored to stock CFW
3) wipes & install
ty guys

Blazer 4.0 to another rom stuck on boot screen

I've been trying to install a new rom on my epic 4g touch and I'm currently running blazer rom 4.0 and trying to try out new roms like calks new 3.0 gb rom but it gets stuck on the boot screen and I tried a fresh Odin from stock and rooted and cwmd but it gets stuck on cwm and even in worst case, it's got rid of my cwm to where I had no choice but to Odin back to stock

Which recovery are you using to flash? If you are using hitman that is your problem. When I tried to flash Blazer 4.0 SAME thing happened to me. Try a different recovery. I have had excellent luck with gunslinger 1.41.

Which ever version rouge 5.0.2.7 is
Sent using my E4GT Blazer rom 1.7ghz d-core

Alright so you Odin'd back to stock now what I would do is reinstall CWM then flash the Gunslinger kernal then retry. Also when you flash the rom make sure you wipe Cache, delvic cache, wipe data factory reset. Then go to mounts and storage and wipe system. Then flash.

rbtrucking said:
Alright so you Odin'd back to stock now what I would do is reinstall CWM then flash the Gunslinger kernal then retry. Also when you flash the rom make sure you wipe Cache, delvic cache, wipe data factory reset. Then go to mounts and storage and wipe system. Then flash.
Click to expand...
Click to collapse
I've done all the above and still nothing.. Im just steadily stuck on the galaxy s ii boot screen.. I had troubles when first installing blazer but I had to clean install after Odin stock el29 with cwm but not working in this case
Sent using my E4GT Blazer rom 1.7ghz d-core

I usually just wipe cache and dalvik reboot and I am all good to go.
Sent from my SPH-D710 using xda premium

I had the same issue when trying to install blazer 4.1 coming from calks 3.0. The flash would go thru with no errors but wouldn't boot. Then I had to Odin to restore the phone. What worked for me was downloading the blazer from on my pc then sending it over to my phone. Flashed then no problems. Maybe it was a bad download?

ezsoulja said:
I've been trying to install a new rom on my epic 4g touch and I'm currently running blazer rom 4.0 and trying to try out new roms like calks new 3.0 gb rom but it gets stuck on the boot screen and I tried a fresh Odin from stock and rooted and cwmd but it gets stuck on cwm and even in worst case, it's got rid of my cwm to where I had no choice but to Odin back to stock
Click to expand...
Click to collapse
Use sfhub's one-click to Oding to Stock EL29 (full reset!) http://forum.xda-developers.com/showthread.php?t=1433101. Then use his AutoRoot [ http://forum.xda-developers.com/showthread.php?t=1342728 ]and add CWM+Rogue.
After downloading (and before extracting the zip of course) check the MD5 and make sure you got the full downloads!
This will give a full stock AND a good CWM. Trying to do it any other way is silly in my opinion. Especially with all the bricks.
Then you can boot into recovery and flash away.

crazybliss said:
I had the same issue when trying to install blazer 4.1 coming from calks 3.0. Maybe it was a bad download?
Click to expand...
Click to collapse
This is to both of you, you did do a format all between installs right?

RainMotorsports said:
This is to both of you, you did do a format all between installs right?
Click to expand...
Click to collapse
Second that! Blazer 4.0 had some new frame work baked in... So a full wipe is needed when switching to and from blazer 4.x
I've used calks format all and haven't had any problems
Sent from my SPH-D710 using XDA

leaderbuilder said:
Use sfhub's one-click to Oding to Stock EL29 (full reset!) http://forum.xda-developers.com/showthread.php?t=1433101. Then use his AutoRoot [ http://forum.xda-developers.com/showthread.php?t=1342728 ]and add CWM+Rogue.
After downloading (and before extracting the zip of course) check the MD5 and make sure you got the full downloads!
This will give a full stock AND a good CWM. Trying to do it any other way is silly in my opinion. Especially with all the bricks.
Then you can boot into recovery and flash away.
Click to expand...
Click to collapse
Actually that's exactly how I do in and still nothing.. Even tried instant a ics build and same result.. Never only way to get ics is Odin to the stick fd05 rooted tar but I cannot get past the boot screen flashing from cwm and I wipe and use calks format all..
Sent using my E4GT Blazer rom 1.7ghz d-core

Originally Posted by leaderbuilder
Use sfhub's one-click to Oding to Stock EL29
(full reset!) http://forum.xda-developers.com/
show....php?t=1433101 . Then use his AutoRoot
[ http://forum.xda-developers.com/show....php?
t=1342728 ]and add CWM+Rogue.
After downloading (and before extracting the
zip of course) check the MD5 and make sure
you got the full downloads!
This will give a full stock AND a good CWM.
Trying to do it any other way is silly in my
opinion. Especially with all the bricks.
Then you can boot into recovery and flash
away.
*do all that then download Calkulins format all zip. go into CWM WIPE EVERYTHING. Run format all. Then flash. You should be good.

HELP!;Wifi problem with cm9 rc1

I am currently running cm9 rc1 with the original kernel(the one dat comes in the folder)
heres my problem wifi turns on but wont scan or detect a network
This is what i didi in cwm;
wipe data
wipe cache
wipe dalvik cache
wipe battery stats
any sugesstions? if any one has cm9 rc 1 how did the set it up?

xperiaplayicsuser2013 said:
I am currently running cm9 rc1 with the original kernel(the one dat comes in the folder)
heres my problem wifi turns on but wont scan or detect a network
This is what i didi in cwm;
wipe data
wipe cache
wipe dalvik cache
wipe battery stats
any sugesstions? if any one has cm9 rc 1 how did the set it up?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=27535011&postcount=1801 This is a workaround, I'd use a different kernel to be honest. My signature has the kernel I currently use for cm9 if you want to try it out

agraceful said:
http://forum.xda-developers.com/showpost.php?p=27535011&postcount=1801 This is a workaround, I'd use a different kernel to be honest. My signature has the kernel I currently use for cm9 if you want to try it out
Click to expand...
Click to collapse
Thanks for the reply:laugh
but the roblem is it cant see networks
and if i were to use mjolnir kernel do i need to flash his modules or just flash and wipe everything

xperiaplayicsuser2013 said:
Thanks for the reply:laugh
but the roblem is it cant see networks
and if i were to use mjolnir kernel do i need to flash his modules or just flash and wipe everything
Click to expand...
Click to collapse
Doh! I read that part too haha my bad. Are you 100% sure it's not a problem with your network? If it's not then yes, flash the wifi modules through cwm and wipe cache. If that doesn't work then you may need to wipe everything and start fresh

agraceful said:
Doh! I read that part too haha my bad. Are you 100% sure it's not a problem with your network? If it's not then yes, flash the wifi modules through cwm and wipe cache. If that doesn't work then you may need to wipe everything and start fresh
Click to expand...
Click to collapse
Im sure its with the network beacuse it worked fine on gb and ill try and tell you
thanks

agraceful said:
Doh! I read that part too haha my bad. Are you 100% sure it's not a problem with your network? If it's not then yes, flash the wifi modules through cwm and wipe cache. If that doesn't work then you may need to wipe everything and start fresh
Click to expand...
Click to collapse
Still not recognizing how did you do it?

xperiaplayicsuser2013 said:
Still not recognizing how did you do it?
Click to expand...
Click to collapse
Well when I installed cm9 I flashed back to stock then went to cm9 and flashed everything, wiped everything about three times (better safe then sorry) and booted up. Have you tried fxp 129 with the Mjolnir kernel? It may be that the cm release is giving the issues..The bots on cyanogenmod go crazy sometimes.. You can also try re-downloading the ROM in case it's a corrupt download

agraceful said:
Well when I installed cm9 I flashed back to stock then went to cm9 and flashed everything, wiped everything about three times (better safe then sorry) and booted up. Have you tried fxp 129 with the Mjolnir kernel? It may be that the cm release is giving the issues..The bots on cyanogenmod go crazy sometimes.. You can also try re-downloading the ROM in case it's a corrupt download
Click to expand...
Click to collapse
thanks so much
wiping everything three times worked

USB Debugging not accessible

Hi
I was flashing back to Stock from task650 to fix my gps. Well something blew up and when the phone reboots the screen goes black but I hear the AT&T start-up tune. Essentially I can't get to enable USB debugging to reflash. I can get to download or recovery, but there are no files to recover<?> and busybox never got installed.
What do I do now?

Do you have the stock recovery now? If so, try going in there and resetting to defaults. That helps sometimes.
Otherwise, you may need to Odin back to stock if you still want to go stock.

CZ Eddie said:
Do you have the stock recovery now? If so, try going in there and resetting to defaults. That helps sometimes.
Otherwise, you may need to Odin back to stock if you still want to go stock.
Click to expand...
Click to collapse
Yes I have stock recovery. Odin is of no use because it hangs waiting for the USB debug to respond. And i can't turn it on because the screen is black and I can't navigate

Do you have a micro sd card? If so, throw a rom on there. If you want to go back to stock, there' a flashable stock zip at the bottom of post #2 in the link in my signature. Under the emergency toolkit section. Flash that, turn on use debugging, do your gps fix and continue on with the task release

xBeerdroiDx said:
Do you have a micro sd card? If so, throw a rom on there. If you want to go back to stock, there' a flashable stock zip at the bottom of post #2 in the link in my signature. Under the emergency toolkit section. Flash that, turn on use debugging, do your gps fix and continue on with the task release
Click to expand...
Click to collapse
Thanks. I created an emergency tool kit on an SD, I wiped data, wiped cache and Davlik and formated system. Flashed the stock rom. When I rebooted it now hung at the Samsung Galaxy S III screen.
How do I get out of this mess?

Try wiping data and cache again in recovery

xBeerdroiDx said:
Try wiping data and cache again in recovery
Click to expand...
Click to collapse
I've wiped data and cache several times, and format/system. I've even tried to flash CWM 6.0.3.1 and I get a status 7 error. Nothing is taking.I get signature failures.
I re downloaded all the files figuring they were corrupted. Nothing doing. I need some real help, because this is beyond my abilities to figure out.,
Now I've got a red triangle showing up in recovery.

BertMor said:
I've wiped data and cache several times, and format/system. I've even tried to flash CWM 6.0.3.1 and I get a status 7 error. Nothing is taking.I get signature failures.
I re downloaded all the files figuring they were corrupted. Nothing doing. I need some real help, because this is beyond my abilities to figure out.,
Now I've got a red triangle showing up in recovery.
Click to expand...
Click to collapse
i dont know why some of these things are not working correctly for you. you're seeing the red triangle because you have stock recovery now from the stock firmware zip. you cannot flash anything in stock recovery nor can you format /system. what happens when you boot up after a factory reset and cache wipe?
a couple of your options include either using odin to flash the stock firmware back onto your device or to use odin to flash a custom recovery back and make a move from there.

xBeerdroiDx said:
i dont know why some of these things are not working correctly for you. you're seeing the red triangle because you have stock recovery now from the stock firmware zip. you cannot flash anything in stock recovery nor can you format /system. what happens when you boot up after a factory reset and cache wipe?
a couple of your options include either using odin to flash the stock firmware back onto your device or to use odin to flash a custom recovery back and make a move from there.
Click to expand...
Click to collapse
When it rains it pours. Now I can't get into recovery. I get the empty battery graphic cycling on and off, and its very warm to the touch. I think the battery is not charging.
I tried using Odin and flashed a stock rom but I kept getting verification errors and status 7 errors. Things just are not taking. I fear I've got a hard brick and I don't know what to do to fix it.
I appreciate your help

aaaaand let the questions roll:
you got verification errors in odin? and after flashing the firmware, i'm assuming you then flashed cwm and that's where you were getting the status 7 errors?
at what point did it all go off? i need to know what order you did all of these things.
can you still get into download mode?

xBeerdroiDx said:
aaaaand let the questions roll:
you got verification errors in odin? and after flashing the firmware, i'm assuming you then flashed cwm and that's where you were getting the status 7 errors?
at what point did it all go off? i need to know what order you did all of these things.
can you still get into download mode?
Click to expand...
Click to collapse
No, it won't go into download. I initially flashed stock rom, but I don't think I wiped anything. That was probably the big mistake. I used something called Samsung S3 QCom tool kit to do an initial flash. It never failed me before. And I also flashed a CWM.
I followed your advice and made a emergency SD kit and flashed from there. I did a clean flash several times. Things just never worked and I kept getting those error messages. Then it just got more difficult to get into download. Now it just flashes a drained battery

it might indeed be drained. leave it plugged in for a while and report back.
you were getting the error/status 7 messages after you flashed cwm back on it likely because the cwm wasnt up-to-date.
what was the last thing you tried before it stopped working altogether?

It gets really hot if I leave it plugged in. But it seems like I can get into recovery again. The last thing I flashed was CMW 6.0.3.1. But what is on it now is CMW 5.5.0.4

actually, what you're saying is the last thing you flashed was cwm 5.5.0.4, just via odin not cwm.
if the phone was in my hands, i would:
flash the cwm 6.0.3.1 zip, select advanced and reboot recovery. now you will be in the updated cwm recovery.
perform a full wipe: wipe data, cache, dalvik, format /system, format /data
flash rom and gapps. if you're going to stick with tasks, use the 4/23 release. i'm on that with no feature or stability issues.
wipe data, wipe cache, reboot.
give it a few minutes to boot up.

BertMor said:
No, it won't go into download. I initially flashed stock rom, but I don't think I wiped anything. That was probably the big mistake. I used something called Samsung S3 QCom tool kit to do an initial flash. It never failed me before. And I also flashed a CWM.
I followed your advice and made a emergency SD kit and flashed from there. I did a clean flash several times. Things just never worked and I kept getting those error messages. Then it just got more difficult to get into download. Now it just flashes a drained battery
Click to expand...
Click to collapse
xBeerdroiDx said:
actually, what you're saying is the last thing you flashed was cwm 5.5.0.4, just via odin not cwm.
if the phone was in my hands, i would:
flash the cwm 6.0.3.1 zip, select advanced and reboot recovery. now you will be in the updated cwm recovery.
perform a full wipe: wipe data, cache, dalvik, format /system, format /data
flash rom and gapps. if you're going to stick with tasks, use the 4/23 release. i'm on that with no feature or stability issues.
wipe data, wipe cache, reboot.
give it a few minutes to boot up.
Click to expand...
Click to collapse
Nope. When I try to flash CWM 6.0.3.1 I get an assert failed error. I came across this fix, I wonder if it is safe to try http://mobotechie.com/tips-tricks/how-to-fix-android-custom-rom-status-7-installation-abort-assert-failed-error-in-recovery-easily-ultimate-guide

BertMor said:
Nope. When I try to flash CWM 6.0.3.1 I get an assert failed error. I came across this fix, I wonder if it is safe to try http://mobotechie.com/tips-tricks/how-to-fix-android-custom-rom-status-7-installation-abort-assert-failed-error-in-recovery-easily-ultimate-guide
Click to expand...
Click to collapse
Well I think I managed it!. First I tried to install an update d/l'ed from Dropbox and that did nothing. Then I flashed an old .tar that was a rooted stock and it rebooted!
I tried editing the updater-script but I couldn't getit to save the changes properly.
Well I will now re flash the RM and CWM and hope for the best
Thanks for all your help, greatly appreciated