Related
Ok, I want to leave a message on here for future noobs like me with a Galaxy S
i9000 but it might work for others too.
My issue when flashing custom roms is that I have not been able to access my galaxy from my computer via usb since literally day 1 (when it did work once).
I spent a week trying to connect to Kies on multiple computers (vista and Windows 7). Tried via Android SDK, even tried hiemdall. I almost tried in ubuntu also but I never did get that working as I really don't know linux well enough. I've now given up...
So then I saw that you can do flashing all on the phone with the clockwork mod. With clockwork, my first rom flashed, well, like clockwork! But then I had some issues with lag and hang ups and reception and I decided to switch to another rom (seearms jl2 based rom - good stuff so far).
However this rom install went sideways... It said that it had installed ok but on reboot it stalled on the Galaxy I9000 screen and froze. Luckily I could still use the 3 button recovery to boot to clockworks but the hitch was that I HAD NO OTHER ROM to flash back to.
I had done a backup through clockworks but when I tried to restore it said the systems.img file was missing so it skipped it and the end result was the same freeze.
Normally everone says to reflash at this point with odin but that was not an option for me. So this is where I got lucky. The SeeARMs rom included Steam recovery module (though I thought it was the stock 3 button recovery menu for a while - I was panicking a little). I highly recommend seeing if you can get steam because it allows access to the External SD card for flashing which can be a lifesaver. Ahh, finally I could get the old rom on that, reflash it and go one with my life. My theory being that at least the issues would be aligned with the this rom and it worked.
So the lessons I learned:
1) Always have your new rom and your old rom on the interanal SD card in case of issues.
2) check your nandroid backup - even try testing it? - they don't always work perfectly with every device.
3)I highly recommend finding out if Steam or similar will work if you cannot access the USB connection and load things on when things go wrong.
Some tips I saw that also worked for me
1) flash a new kernel before you flash a new whole rom.
2) if things go sideways, try redownloading or retransferring the file to make sure there were no errors.
I did both and then reflashed (with my old rom Voodoo Doctor, SeeArms Rom and Darky's 8.1 rom on the card just to have options) and all was good!
PS: the steam recovery knocked off the first letter of the file when executing for some reason so I had to make 2 copy's of each rom I wanted access to ie Darkysrom.zip and arkysrom.zip just look for that error when you are doing this.
Good post - hopefully it'll help someone out who's stuck.
Hopefully
I'd like to stick some of that in on the thread for your rom but I need put another 7 half relevent messages out there before I am worthy... I understand the rule but I'd rather only post where it is meaningful...
GF
tl;dr: Interrupted update. cant do jack. tried acer tech support. failed
I grew bored with waiting the two minutes for my tablet to install the new update. so i stood up and hit the power button to put it to sleep like a boss. then i cam back later, the lock screen was unresponsive
i figured out be double tapping the pwr button i was able to unlock the tablet to see the powering down screen (see attachment). I can get to the setting menu, but evrytime i try to mess around in it, the window closes itself.
an interesting note is that the time is wrong, and the battery suddenly went from 100% to 15%
I called acer tech support, and with ther guidance...
pressed the reset button to no effect
powered on holding the pwr & vol- buttons down to get an error (see attachment). then the tablet turns off.
Ive dled some "update.zip" files i found online that are supposedly used to unbrick the tab... but i just got the same error picture(see attachment)
one other thing i tried was to hold the power and vol+ buttons. this cleared a chache, but had no other effect.
I am a noob at droid, but not to tech. i would like to avoid perma bricking, and im unsure about mailing this in. waiting is gay. I would like to restore it to factory settings w/o rooting it etc. as ive never done that before. but im not opposed to installing a CFW if it somes to that...
Im looking for ideas guys here guys. wtf is wrong with this thing?
Haha
Lmao "hit the power button to put it to sleep like a boss", funny ****.
Can't help you though sorry
ive been around he web, and have seen this exact series of symptoms happen to a handful of other guys... i haven figured out a solution yet, and it is looking more and more like ill be sending it in via warranty
my best guess at this point is i have corrupted a crucial system file. as to why i can do jack in the factorys recovery mode... idk. but then again, idk what the factorys recovery mode should look like or how it would function. youtube only shows CWR... which i dont have
if i believed i could anything reasonably withing my abilities, i would... but voiding the warranty on a long shot seems dumb.
still ANY ideas would be great
I too faced exactly the same problem today.. Dunno why this is happening... I am too worried now... Kindly post the solution as you find them...
Am sure calling tech-support is just waste of time..
Thanks in advance..
IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.
npena said:
IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.
Click to expand...
Click to collapse
How to put this file on the root folder when am not able to switchon the Tablet itself... and how reliable is this file??
stuck on same screen also!
My friend and i who both purchased this Acer Iconia tab are both having the same problem. We both received a message on the tablets to do the update. We both got stuck and have gone thru tech line and there is no remedy. She was able to return hers within the 15 day period; I on the other hand am a week over that so have to mail it to Acer for repair. I'm thinking this is more than a cooincidence and there is a problem more spread... Acer would neither verify or confirm....
buntzmehta said:
How to put this file on the root folder when am not able to switchon the Tablet itself... and how reliable is this file??
Click to expand...
Click to collapse
He said the root of his SDCARD. You can take out the sdcard and put it in a sd cardreader on a computer and copy the file to it then put it back in the tablet. The file worked for him so it might be worth trying. Just have patience while it is loading as some of these updates take a while to load and sometimes you may not see anything happening but it is. The more patches and roms you load on Android the more you'll learn to just leave it alone and let the updates finish. Its pretty rare for updates to be messed up. Its usually people getting anxious and clicking on stuff.
Good luck
Sent from my A501 using Tapatalk
still stuck on shutdown screen any updates?
Anyone had any luck with a fix? If not --sending it to Acer for warranty repair after the hurricane hits..Sure hope this isn't a wide spreasd Acer issue do to the new download. Wish I could just return the thing all together. Worked well while I had it a whole 3 weeks...... Thanks in advance for any information.
npena said:
IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.
Click to expand...
Click to collapse
Thanks a lot dear npena.. you are simply great.. i was very anxious initially to try your method as no other member here who face the same problem thanked or recommended your suggestion...
I tried it and it worked... I am really very thankful to you...
Cheers..
you are my hero indeed.. thank once again..
BuntZ
Friends, who face this problem you must try it... it just takes few mins b4 you can get your acer tab to work again beautifully without loosing any settings or installed apps... they remain intact...
Yay!
Glad you got it running again - had a similar problem when doing a ota update myself, was so worried I bricked the tab, went thru about 7 update.zip files until I found one that magically worked, letting me get back into the system and flash the correct rom for my region
hi! i have the same problem with my a500. I write a guide to solve this problem. Problem in firmware. here is the gude http://forum.xda-developers.com/showthread.php?t=1572622
Well... Seems like we've got ourselves a new bootloader, after flashing the BETA1 Gingerbread for U8800. Not cool...
I tried it and didn't like it.
Furthermore, I wanted to keep my device in that zen condition which allows me to return it to my carrier under warranty.
I've tried to revert to my carrier stock ROM, but to no avail. I can run froyo alright, but the carrier costumizations are simply ignored, courtesy of the new bits that came with Huawei's beta.
Some time ago, and antecipating something like this, I connected the mobile, while in pink screen mode, to a linux box and dd'ed the entire volume to a dump file. I can mount this dumpfile through /dev/loop and confirm it carries the same partition schema that is present in the mobile. I'm tempted to dd it back to the mobile, to restore it, but affraid of bricking it for good. If bootloader gets invalid then nothing short of a factory j-tag flash will solve it, for sure.
Has anyone done this before?
Thanks in advance.
EDIT: It worked. The whole volume was restored (bootloader included, naturally).
Greetings,
Everything else aside, claiming that the installation of a manufacturer released upgrade (yes, even one labeled Beta) automatically voids your device's warranty pretty wild. That's not to say that someone somewhere won't make that argument, but there are plenty of crazy people in the world.
That said, good luck.
bonowax said:
Well... Seems like we've got ourselves a new bootloader, after flashing the BETA1 Gingerbread for U8800. Not cool...
I tried it and didn't like it.
Furthermore, I wanted to keep my device in that zen condition which allows me to return it to my carrier under warranty.
I've tried to revert to my carrier stock ROM, but to no avail. I can run froyo alright, but the carrier costumizations are simply ignored, courtesy of the new bits that came with Huawei's beta.
Some time ago, and antecipating something like this, I connected the mobile, while in pink screen mode, to a linux box and dd'ed the entire volume to a dump file. I can mount this dumpfile through /dev/loop and confirm it carries the same partition schema that is present in the mobile. I'm tempted to dd it back to the mobile, to restore it, but affraid of bricking it for good. If bootloader gets invalid then nothing short of a factory j-tag flash will solve it, for sure.
Has anyone done this before?
Thanks in advance.
Click to expand...
Click to collapse
is the dump file around 4gb then yes it will work I did it my self through restoring raw sd image
Sent from my u8800 using xda premium
By the time I red your reply, my mobile was already back to Zen state. Thank you nevertheless.
On a side note: the battery was very low by the time I initiated the restore, but since it was connected through USB, I assumed it wouldn't be an issue.
It took around 45 minutes to restore the image and when finished, the battery was exhausted to the point that I couldn't turn the mobile on. Thought I had bricked it for good...
Charged overnight and everything was fine and dandy.
Cheers
mine took 25min
I managed to downgrade to 2.2:
Get some 2.2 update, mine was b136.
First tried to update from sd card, it failed. Then tried from the internal SD and it worked (Take off the external SD first). But the update was too fast and it only booted to original recovery (with some warnings). So i did the update again and now it toke the usual time. But it it still only booted to original recovery (with some warnings). Then i did a factory reset from the original recovery, and voila, it booted to 2.2!
Once the 2.2 was booted, i copied CWM recovery in the pink screen and it works now too. Then i was able to install Miui again.
straight restore did not work for some reason, maybe needs to format everything first?
sanpsa said:
i managed to downgrade to 2.2:
Get some 2.2 update, mine was b136.
First tried to update from sd card, it failed. Then tried from the internal sd and it worked (take off the external sd first). But the update was too fast and it only booted to original recovery (with some warnings). So i did the update again and now it toke the usual time. But it it still only booted to original recovery (with some warnings). Then i did a factory reset from the original recovery, and voila, it booted to 2.2!
Once the 2.2 was booted, i copied cwm recovery in the pink screen and it works now too. Then i was able to install miui again.
Straight restore did not work for some reason, maybe needs to format everything first?
Click to expand...
Click to collapse
man you are the king!!!!!!!!!!!!!
Thanks you
sanpsa said:
I managed to downgrade to 2.2:
Get some 2.2 update, mine was b136.
First tried to update from sd card, it failed. Then tried from the internal SD and it worked (Take off the external SD first). But the update was too fast and it only booted to original recovery (with some warnings). So i did the update again and now it toke the usual time. But it it still only booted to original recovery (with some warnings). Then i did a factory reset from the original recovery, and voila, it booted to 2.2!
Once the 2.2 was booted, i copied CWM recovery in the pink screen and it works now too. Then i was able to install Miui again.
straight restore did not work for some reason, maybe needs to format everything first?
Click to expand...
Click to collapse
Yes, I had it running FROYO back too, but the phone's condition wasn't the same as before.
If I understood it correctly, the 2.3.5BETA rewrites de boot partition - the 2nd primary parition on the device, marked bootable. This becomes obvious when the "IDEOS" logo is replaced by the "HUAWEI" one during device boot-up.
The partition scheme is the same as before, however, as I had the chance to confirm.
Flashing a 2.2.1 ROM from Huawei did not write the old bootloader back, furthermore this might not be the only change.
I was able to revert to an overseas 2.2.1, both through CWM restore and "dload" method, but carrier customizations were always absent.
Along with the regular system, my carrier's ROM adds a batch of apps, ringtone, wallpaper, binaries and libs, under "cust_data/tmn/pt". These were all ignored. Not that I cared much for them, but as I stated in the original post, I wanted it back in the original condition, as TMN will consider warranty void if the device has been tampered with.
Since I had a raw dump of the volume I restored it back and got my mobile as it was some 3 weeks ago... To my relief...
Can you please make a tutorial to make and restore raw backups?
1. Step : Download a official 2.2.2 rom
2. Step : Put the dload folder at the root of your sd-card
3. Step : Power your device of and boot into bootloader by pressing volume +, volume - and power (before you do that, you can do a titanium backup)
4. Step : Wait till the prozess is done. When your device doesn't reboot by itself, reboot it manually. (if there are any problems with the rom, wipe cache and date with the original recovery)
5. Step : Download a CWM recovery. Boot your device like the same way above into the bootloader. Rename the CWM recovery you've downloaded before into recovery.img
(6. Step : Rename the recovery of your device in the folder (device):/image into recovery.img.orig, to do a backup of the original recovery)
7. Step : Put the new recovery.img in the folder from above. Unplug your phone from the PC and put the battery out to turn it off. Boot it into recovery by pressing volume + and power.
Congratulation, you've restored your Ideos X5 to 2.2.2.
Now you can download a custom rom and install it by the normal way.
FabioAreia said:
Can you please make a tutorial to make and restore raw backups?
Click to expand...
Click to collapse
Good sugestion... Will start a new thread for it.
IDEOS X5 - Update dead drives bootloader - help me
4. Use the English language.
We understand that with all the different nationalities not everyone speaks English well, but please try. If you're really unable to post in English use an online translator, You're free to include your original message in your own language below the English translation.
Click to expand...
Click to collapse
MOD EDIT: Please read the forum rules.
how can we restore a raw dump?
dd if=[image filename] of=/dev/[block device allocated to the U8800] bs=512
Search the forums for the complete tutorial...
Flashing the official gingerbread in u8800 its irreversivel process, at least for now.
If you flash it you have to keep it as no way of going back.
If you root it using the only available method, bye bye!
Everytime you reboot the endless bootlooping starts and the only way to stop it is formatting data.
Which means everytime you reboot = bye bye all data and apps etc.
I think is something that its major importance and no one is mentioning this!!!!
I don't know, maybe I've been preaching to deaf ears or something...but...you can re-install the old ROM back, the CWM recovery won't work with the official GB - that much is true - but you will be able to downgrade to an official 2.2.2 (I used the B162) version with the regular update method (at least I was and everything is working just as normal as it used to).
So, irreversible - I don't think so
with the current CWM recovery - it's a no-go
edit: that being said, what works for me, doesn't necessarily work for everyone, so be careful and blame the guy in the mirror -not me, if it doesn't work for you. =)
I think Huawei says wrong here. I flashed 2.3 yesterday. After that, because of the haptic issue I flashed back to official 2.2. Only problem after the 2.2, recovery console had opened. I did factory reset there and phone started without a problem. Then, I had upgraded to 2.3 again. Still haptic don't vibrate. Other than, no problem here. Maybe, I will go back again to 2.2.
Well you are lucky then because you are the only one.
Perhaps what is saying in the official intructions that will be impossible to dowgread after this upgrade won't apply to you.
I have try it with at least 8/9 versions of official release and nothing works!!!!
what 2.2 version is that and you did it after or before rooting?
Have you tried with internal sd? I copied dload folder to internal and started the upgrade process from Storage-Upgrade Firmware. Where did your phone stuck?
Edit: I didn't root my phone. Waiting proper solution. I had used B138.
no, I'm using external SD.
now I'm downloading another official release to try to downgrade using another one...
this time is U8800 V100R001C17B162CUSTC17D001
Druida69 said:
Well you are lucky then because you are the only one.
Perhaps what is saying in the official intructions that will be impossible to dowgread after this upgrade won't apply to you.
I have try it with at least 8/9 versions of official release and nothing works!!!!
Click to expand...
Click to collapse
Well, like I said, what works for me doesn't necessarily work for you.
Anyway, this is what I did and it worked, maybe it can help others.
0. Copy the original B162 ROM ("dload"-folder which has two files, UPDATE.APP AND UPDATE_CUST.APP) to the root of your SDCARD
1. Update to B162 by holding down +- keys while turning on the phone
2. After the first reboot, it's giving error messages for not being able to mount this and that...just ignore it and...
--> Wipe data / factory reset --> remove battery
3. Update the B162 again --> this time everything should go OK, if so, your phone is back to stock B162 and you're ready to use it or update a custom rom (just install Clockwork recovery like you used to and start from there)
The last point (3) may be unnecessary, but I did so just to make sure everything's ok.
Edit: OK, and I meant b162, not b160...
Druida69 said:
no, I'm using external SD.
now I'm downloading another official release to try to downgrade using another one...
this time is U8800 V100R001C17B162CUSTC17D001
Click to expand...
Click to collapse
For me it also works. I have downgrade without any problem and I use to the b 162 version. Now Ian back to oxygen
Sent from my u8800 using XDA App
yes I made it with this B162.
**** this **** I'm going back to custom rom.
No point of using this official release if future customs will use the libs from this one.
Druida69 said:
yes I made it with this B162.
**** this **** I'm going back to custom rom.
No point of using this official release if future customs will use the libs from this one.
Click to expand...
Click to collapse
And then there's the fact that the official gb is still beta, it's not supposed to work perfectly. But as long as the dev team here stays active, I think that I'm gonna stick with custom roms too.
ho my god.
didn't work.
is always booting into recovery
I am stuck here also (
Nothing worked
I tried clockwork recovery - it doesnt get to. It is just rebooting.
I tried with various dload UPDATE.IMG's (GB Overseas, GB orig chinese,B162,B138) nothing is working - stucked in "Step 1/2 Unpacking" window forever.
Anyone has solution for this ?
Two weeks ago I've flashed the U8800Pro version - real mistake
I've started a topic here:
http://forum.xda-developers.com/showthread.php?t=1327715
katu2006 and on the second page flibblesan gave me a method to start my phone working well.
Post #4, #11 and #13.
Maybe this will help you,too?
sbasil said:
Anyway, this is what I did and it worked, maybe it can help others. (...)
Click to expand...
Click to collapse
You sir are a LEGEND. My phone "lives" again! On CM7 again...
manage to install miui.
several versions now up to the newest one.
I noticed on all of them that it mount the SD card when connected to USB but only shows the system files and not allow writing, copy, cut, etc.
Saying that I dont have permission to change the SD
Druida69 said:
Flashing the official gingerbread in u8800 its irreversivel process, at least for now.
If you flash it you have to keep it as no way of going back.
If you root it using the only available method, bye bye!
Everytime you reboot the endless bootlooping starts and the only way to stop it is formatting data.
Which means everytime you reboot = bye bye all data and apps etc.
I think is something that its major importance and no one is mentioning this!!!!
Click to expand...
Click to collapse
I have just flashed with new U8800V100R001C00B517G001(Beta1.0)(Overseas Normal)(Gingerbread) but after flashing I kept waiting for start my phone. I restasted many times but same, then I format data its worked and when restarted again it goes in same condition any help ?
until flash disk is writable and it is - there will always be way to go back to old versions it just files.. like reinstalling windows on your pc.
Since the new Rom is public I have read all posts about it here. Maybe I had lucky, or simple due it without messing with the files.
Yesterday I made the upgrade to the new rom, directly from the last Oxigen version, without downgrade to 2.2. I simply create the dload folder on SD card, put there de update file, boot with +- Power, and chose upgrade from SD card.
After step 2 I reboot the phone a install step 3 upgrade. Everything as installed fine, no boot loops, nothing...
Also the root method decribed in this forum as work on first time.
24 hours after the upgrade, and some reboots to test, I never se the boot loops, and the phone is working well.
The new ROM, even in beta stage, to me is a great improvement.
Well either you were lucky or me and the majority were unlucky.
But issues only start to happens when rooting.
So that you can see it fried me the 1 USB cable. This cable is only good to charge the battery now....
Also, ****ed the device USB storage MOUNT.
I connect it to the computer and the computer sees it as a CD drive not allowing any changes.
Also when press the button to mount the USB on the device it never gets mounted and gives the messages that the SD can now be removed.
So I have put this issue many times but up to the moment no one even reply to help.
ok so heres the rundown. i have my hd2 and have in the past put a different rom on, so it is not stock(just for a reference point). Now i want android, I have multiple verions n builds which were using paranoid android and cm9 for ice cream sandwhich. Every build i throw on there i always boot thru the sd card thru the clrcad.exe. Every build i try the wifi is never able to find any sources, it just keeps turning on n off.
That is my problem and didnt know how to go about it. Just for Reference 1. I have looked thru all the developer threads and did see others had problems and they got no solutions. 2. i just joined so i cannot post in the developer threads to ask them for help. 3. i did search the forums for similar problems but nothing related to the same problem they were using different build or os. If i missed somthing please tell me.
I thought maybe since i dont have a stock rom on the hd2 it might be interfering with ics. The wifi works fine while using windows. A second thogut was maybe i should just install the magldr which from what i read would wipe the internal mem, but once the first time putting that on there i could was done i could boot thru that instaed of using clrcab.exe.
Here you go:
http://forum.xda-developers.com/showthread.php?t=1445766
You are welcome.
Marvlesz said:
Here you go:
http://forum.xda-developers.com/showthread.php?t=1445766
You are welcome.
Click to expand...
Click to collapse
i would just hit te thanks! button but it said i didnt have permission so Thanks! i will try thatright now
ok so i applied the apk and installed with superuser permission without a problem. i then reset the phone, but it didnt work. So i made sure that under advavance configuration it said US, tghen proceeded to input the *#94349# and it said that wifix was enabled, but still the same problem it just turns on n off all the while giving me the unending message of "turning on wifi..."
but now here is the things i have tried since yesterday i have made to installer hardspl 2.08 and radio 20.15.50.14 and then magldr. With little trouble i was able to get android to run stright from bootup now instaed of going thru windows. Everything runs great except for wifi, i technicly not sure if data works as to i dont have it on yet, soon tho.... soon...
Any ideas would be much thanks. BTW im trying PARANOIDANDROID HD2 [v1.5b][TABLET/HYBRID][CM9][tytung HWA R3] from the thread [26-Aug-12][sd/mag] paranoid jellybean hd2 Beta v1.992.
You said you tried the same apn under windows and it worked. Now you're on ICS and it doesn't work.
I had this problem a while ago when I went on a vacation, it just used to say "truning wifi on", but nothing shows up. It's a regional wifi problem. OK, try this: flash a rom without a simcard inserted, and check if the wifi is working. IF, it works, then WiFix SHOULD fix your issue, otherwise report back.
(Btw, there is another way to fix the regional wifi by replacing the wireless modules, but I can't find the link, sorry )
Marvlesz said:
You said you tried the same apn under windows and it worked. Now you're on ICS and it doesn't work.
I had this problem a while ago when I went on a vacation, it just used to say "truning wifi on", but nothing shows up. It's a regional wifi problem. OK, try this: flash a rom without a simcard inserted, and check if the wifi is working. IF, it works, then WiFix SHOULD fix your issue, otherwise report back.
(Btw, there is another way to fix the regional wifi by replacing the wireless modules, but I can't find the link, sorry )
Click to expand...
Click to collapse
ok so my next step is is flashing it to the internal, got it. Afraid to do but willing. I tried the wifix and according tothe phone the country code is US right now and currently im trying different kernals from the thread. Once i burn thru those with no success which hopefully ill find a good one i will try your method Thank you for your assistance.
deus_diabolus said:
ok so my next step is is flashing it to the internal, got it. Afraid to do but willing. I tried the wifix and according tothe phone the country code is US right now and currently im trying different kernals from the thread. Once i burn thru those with no success which hopefully ill find a good one i will try your method Thank you for your assistance.
Click to expand...
Click to collapse
ok so i have burn thru most of those kernals not seem to work except some were laggier. Reverted back to original kernal the dev was using and removed sim card. It didnt help still had same problem. Still want to stay with this build but i am looking into a similar build for rom to flash to internal.
deus_diabolus said:
ok so my next step is is flashing it to the internal, got it. Afraid to do but willing. I tried the wifix and according tothe phone the country code is US right now and currently im trying different kernals from the thread. Once i burn thru those with no success which hopefully ill find a good one i will try your method Thank you for your assistance.
Click to expand...
Click to collapse
deus_diabolus said:
ok so i have burn thru most of those kernals not seem to work except some were laggier. Reverted back to original kernal the dev was using and removed sim card. It didnt help still had same problem. Still want to stay with this build but i am looking into a similar build for rom to flash to internal.
Click to expand...
Click to collapse
Oh, you're using an sdrom, sorry I forgot that !
No, it doesn't have to be to the internal, just a fresh install (whether nand or sd, and in your case it's SD)
And you totally misread my answer, I didn't mean Kernels and I didn't mean remove the sim while still on the same rom x)
Maybe it's my fault for writing such an answer, let me paraphrase my answer for you:
1- Remove your current build from the SD card (better if you backup your whole sd to pc and format it)
2- Remove simcard. (BEFORE INSTALLING)
3- Put totally fresh and new rom on sd.
4- Boot up ROM and test wifi.
5- Report back Read the edit
Edit:
OK, first of all, I'm sorry for not reading the whole thread. I just read it again, and will answer your questions.
You wanted to try android so you went for Icecream (which has the regional Wifi issue)
As long as the radio is correct, the stock ROM should not interfere with android.
No, if it is (truly) the regional issue, installing android through MAGLDR will not solve your issue. it will persist.
And btw, instead of doing all the steps, just try a GingerBread ROM, if wifi works there then it is the regional issue.
Marvlesz said:
Oh, you're using an sdrom, sorry I forgot that !
No, it doesn't have to be to the internal, just a fresh install (whether nand or sd, and in your case it's SD)
And you totally misread my answer, I didn't mean Kernels and I didn't mean remove the sim while still on the same rom x)
Maybe it's my fault for writing such an answer, let me paraphrase my answer for you:
1- Remove your current build from the SD card (better if you backup your whole sd to pc and format it)
2- Remove simcard. (BEFORE INSTALLING)
3- Put totally fresh and new rom on sd.
4- Boot up ROM and test wifi.
5- Report back Read the edit
Edit:
OK, first of all, I'm sorry for not reading the whole thread. I just read it again, and will answer your questions.
You wanted to try android so you went for Icecream (which has the regional Wifi issue)
As long as the radio is correct, the stock ROM should not interfere with android.
No, if it is (truly) the regional issue, installing android through MAGLDR will not solve your issue. it will persist.
And btw, instead of doing all the steps, just try a GingerBread ROM, if wifi works there then it is the regional issue.
Click to expand...
Click to collapse
ok so i took sim card, formated the sd card, put fresh build on and started it. Loaded in and still same exact problem. ok so will try gingerbread.
ok so put gingerbread on phone and loaded it up and gave it a reboot just because. Loaded up, turned on wifi hit settings for it, it just said scanning. Backed out installed wifix, and dialed *#93439# it engaged and still nothing changed. Now on both this and ics i input my ssid and wep key for my home router just to try and help out but just said not in range. If i dont put that in, ice just says turning wifi on... then off then on etc..., on gigerbread it says scanning. So im stuck on what to do the only thing i havent tried far as i know (which is very little) is to flash to the interal mem.
On gingerbread you don't need the WiFix.. uninstall it.
if it says scanning, that means it's working.