Database Users

[Q] Help me please....Hotspot problems

I recently tried using my hotspot on my mt4g and it keeps giving me an error....also my wifi will reboot my phone every time i turn it on.. please for the love of god help

808DDP said:
I recently tried using my hotspot on my mt4g and it keeps giving me an error....also my wifi will reboot my phone every time i turn it on.. please for the love of god help
Click to expand...
Click to collapse
Rooted?
S-Off?
What ROM...
More information please
Sent from my Streak7 Honeycomb using xda premium

Saranhai is right. It sounds like a kernel issue. If you give us more info we can recommend kernels that you can flash.

sorry guys
rooted? yes
s off? yes
[ROM]OFFICIAL MIUI.us 2.2.17 and OFFICIAL MIUIAndroid 2.2.17 - AndroidInsomnia
Any ideas???

808DDP said:
sorry guys
rooted? yes
s off? yes
[ROM]OFFICIAL MIUI.us 2.2.17 and OFFICIAL MIUIAndroid 2.2.17 - AndroidInsomnia
Any ideas???
Click to expand...
Click to collapse
Ok. MIUI is an alteration of AOSP. So, an AOSP compatible kernel is what you would want. However, LanternsLight puts out good MIUI ROMs. Unless its a known issue, I doubt its the ROM. Did you format your system partition before flashing?
Edit: Just spent a few minutes reading through the thread. No one else has reported this as far as I can tell. If you didn't format /system before you flashed, reflash using the instructions in the OP of the thread in the dev section. If you did, wipe cache and dalvik cache and reflash. If neither of those works, try TDJ's AOSP kernel, but there is nothing wrong with the Tiamat kernel, so I doubt that's it.

OK update i dont have any idea why this isnt working but i cleared the sd card,ran the rom install again followed the directions completely and my hotspot and wifi will bootloop my phone im at a loss of swear words already. should i take a hammer to it or not

Did you try a fresh download?

yes as stated i completely cleaned the sd card and redownloaded multiple roms and none will allow me to use wifi or hotspot the hotspot will error and the wifi will bootloop every single time

What Roms did you try?

what you can find in the recent rom section i tried i think it has to do with the phone or something im lost im frustrated im gonna flip out and smash this phone soon

Well, if you'be tried multiple ROMs with different kernels and did FULL wipes between them all, its probably hardware. I can't think of anything else it would be.

well all i did was change sd cards and thats it no more wifi and hotspot.....should i partition the sdcard i do remember seeing that in recovery does that affect the wifi n hotspot? if so what should it be partitioned at

Eeerm, partitioning the sd card is for moving apps over to external storage the pre-froyo way. It has nothing to do with hotspot functions. So your hotspot worked before, but crapped out when you changed as cards? That's really weird...
Does anyone else have any insight into this, because I'm at a loss?

Anyone out there?????? ANYONE

Try flashing the stock 2.2.1 or 2.3.4 rooted. Try if that works. If not, I too am at a loss. Maybe Jack_R1 is around lol

ok last day to try and fix this phone before i throw this phone in the microwave
nothing has helped

808DDP said:
ok last day to try and fix this phone before i throw this phone in the microwave
nothing has helped
Click to expand...
Click to collapse
You tried stock?

808DDP said:
ok last day to try and fix this phone before i throw this phone in the microwave
nothing has helped
Click to expand...
Click to collapse
have you tried flashing the froyo pd15img to unroot and see if the problem persists? if not then i would do so and then report back... if the problem is still there then it seems to be a hw problem... if it is gone then it will be easy to reroot and be back in the game! just a little fyi though, if you want help then next time i would recommend providing us all the information! bootloader version, root method, rom, kernel, etc, etc, etc... you will more than likely get a more informed response and it shows that you actually put forth a bit of effort in helping us help you, rather than being the guy in my signature video! and as for your comment of this is the last day you are going to try to fix the phone, well it is your money that was spent on it, so by all means nuke the damn thing! but dont get angry cause we cant fix your device, we did nothing to it or you... take it to the store and let them mess with it or pay the deductible and get a new one... good luck on any note!

[Q] [Defy+] Downgraded To CM7 from CM9 & Battery Shows Question Mark

Last night I rooted my Defy+ with CM7(latest nightlies from defy-cm.net), applied battery and camera fix, everything worked perfectly and I enjoyed it.
I tried little experimenting then installed CM9(usedEpsylon builds) and flashed the kernel mentioned here(http://forum.xda-developers.com/showthread.php?t=1432100&page=3) but then I noticed it had lot of bugs and my phone started having a lot of weird reboots.
So I thought of reverting back to CM7 and then problem of the battery popped up. Battery now shows a question mark and I dont know whether it could charge or not. After reading a lot I thought it would be better to revert to CM9 just incase if the battery isn't charging and I'd have to find a workaround for charging.
Although I love CM9 very much but I can't stick to it because of the camera and a lot of instability.
After studying forums I realised it may be because of the incompatible kernel for CM7. So the only way I could get teh original kernel is by flashing the original SBF. But the problem arises is that I cant find the same build for my device and I am little skeptical about flashing with different SBF. Also I have no nandroid backup as such. Nearest I could find a SBF was with 4.5.1-134_DFP-1321. Also I have gone through all the Walter79 posts and his SBF collection too and it doesnt have the SBF for my DEFY+.
Can somebody guide me with the workaround?
My DEFY+ specifications:
system version - 45.0.891.MB526,AsiaRetail.en.03
model number - mb526
android version - 2.3.4
baseband version - epu93_u_00.60.00
kernel version - 2.6.32.9-gbdd614e [email protected]#1
build number - 4.5.1-134_DFP-891

I am having the same problem, even after resoring to the original the battery keeps giving me a question mark and the phone shuts down.
I can boot it into recovery by plugging it in but whatever rom I flas the battery keeps going to question mark.
I am becoming a little sacred I killed my phone now..

Same problem with me. flashing my stock nandroid backup did not solve the problem..
http://forum.xda-developers.com/showthread.php?t=1569336
I put everything back to stock, because without the mcguyver trick I am not able to charge my battery..
I am sending it RMA this monday

So you say that even if I flash a SBF, the battery problem won't solve?? I thought it was just because of a kernel incompatibility otherwise why would the battery charge while I'm using CM9?
Sent from my MB526 using XDA

Oh!!! It seems there are two threads of the same name!!!! I replied here
You may find a solution
---------- Post added at 01:09 AM ---------- Previous post was at 01:08 AM ----------
Hi,
My Defy+ also came with the same SBF version however I updated it to another one and now service center updated it to another one(which is unrootable!!) So be careful while choosing the SBF(Don't worry I will tell you which one should be safe! ). First:
There are issues with battery charging with CM9. moreover you should have tried Quarx's build CM9 for Defy+. Both CM7 and CM9_Defy+ of quarx are more stable!! however, as per memory serves I remember flashing CM7 for Defy when I had the version of SBF you have, so I believe even CM9 for Defy should work(No need to flash extra kernels if you flash the Defy versions of CM).
Now coming to the SBF part you may go for this SBF(from my dropbox). It is 4.5.1-134_DFP-1321 version SBF. That will update your phone to 2.3.6 and BL6. Thus you won't be able to downgrade to any Froyo kernels and will have to use CM7 and CM9 for Defy+ builds(use Quarx's build this time). However NEVER flash the version with DFP-231!!! It has BL7 and is still not rootable!!! ( Thanks to dumb service center people I am stuck with this!!)

It happened because of some network problem here and I don't see any option to delete the other post.
I'm downloading the SBF right now and wish that the problem gets solved and I can use CM7 again with no battery issue.
Sent from my MB526 using XDA

I did flash Quarks new nightly that was just posted. All worked fine at first and then I rebooted and since then it will no longer boot. If I plug it in I can get into recovery but if I let it try to start up I get a big battery with a question mark in it. I will try this sbf and thank you so much for helping

Also I notice that your sbf file is quite huge compared to the same file by walter79.. Is it just that he zipped it and you didn't?
Sent from my MB526 using XDA

Puckying said:
I did flash Quarks new nightly that was just posted. All worked fine at first and then I rebooted and since then it will no longer boot. If I plug it in I can get into recovery but if I let it try to start up I get a big battery with a question mark in it. I will try this sbf and thank you so much for helping
Click to expand...
Click to collapse
Welcome Make sure you don't drain your battery much. I have seen many users using CM9 with this prob. However there is a battery fix if you want to try. Search it in Q&A also someone posted recently. Sorry don't have time now to search!
meherranjan said:
Also I notice that your sbf file is quite huge compared to the same file by walter79.. Is it just that he zipped it and you didn't?
Sent from my MB526 using XDA
Click to expand...
Click to collapse
Its of big size because:
1.) I didn't zip it.
2.) Its a full SBF not fixed. A fixed SBF has its cmg39 deleted which contains BL version and also all system image! Dis is done to maintain downgradability and thus needs a nandroid backup too!

pranks1989 said:
Welcome Make sure you don't drain your battery much. I have seen many users using CM9 with this prob. However there is a battery fix if you want to try. Search it in Q&A also someone posted recently. Sorry don't have time now to search!
Its of big size because:
1.) I didn't zip it.
2.) Its a full SBF not fixed. A fixed SBF has its cmg39 deleted which contains BL version and also all system image! Dis is done to maintain downgradability and thus needs a nandroid backup too!
Click to expand...
Click to collapse
I added the battery fix as well but then the battery had already drained. It went really fast from 90% to completely dead.
I shall try the McGyver trick today and see if it will respond again after that.

Puckying said:
I added the battery fix as well but then the battery had already drained. It went really fast from 90% to completely dead.
I shall try the McGyver trick today and see if it will respond again after that.
Click to expand...
Click to collapse
Oh okay..!! Ya then try the McGyver trick.. But be careful at it or you may end up frying your battery!!

I am a bit worried about that too so it is still laying there, ready to try but my courage lacks.
My husband is an elctro man and will be home tomorrow so I think I will wait till then.
I wonder after flashing the new sbf it will again recognise the battery..

I reflashed cm 9 and now everything is up and running again. Battery is charging.
I will see how it holds up over time , if all else fails I can still flash the full sbf

Puckying said:
I reflashed cm 9 and now everything is up and running again. Battery is charging.
I will see how it holds up over time , if all else fails I can still flash the full sbf
Click to expand...
Click to collapse
My problems are solved as well I did not want to work on CM9 anymore. To much problems and instability.
http://forum.xda-developers.com/showthread.php?p=24340090#post24340090

fokkeh said:
My problems are solved as well I did not want to work on CM9 anymore. To much problems and instability.
http://forum.xda-developers.com/showthread.php?p=24340090#post24340090
Click to expand...
Click to collapse
Puckying said:
I reflashed cm 9 and now everything is up and running again. Battery is charging.
I will see how it holds up over time , if all else fails I can still flash the full sbf
Click to expand...
Click to collapse
Good to know the problem is solved! Probably you should wait till a stable CM9 (Defy+) comes out

I flashed a full sbf, the one that was posted but now can no longer receive calls or texts.
I can ring out so there is a connection. but nothing comes through. I have saerched all over the place , installed the baseband changer. But no incoming calls...

Puckying said:
I flashed a full sbf, the one that was posted but now can no longer receive calls or texts.
I can ring out so there is a connection. but nothing comes through. I have saerched all over the place , installed the baseband changer. But no incoming calls...
Click to expand...
Click to collapse
The SBF I posted is for India. You should flash an SBF that suits your region. You said you installed baseband switcher but baseband switcher works only after rooting and you need to make correct changes. So, since you are flashing full SBF I suggest flash the one for your region. There should not be any prob then!

Yes I am doing so now Thanks again. Steep learning curve here
And I rooted at once with super one click
---------- Post added at 03:52 PM ---------- Previous post was at 03:03 PM ----------
No difference, still no incoming calls..
Phew! Fixed. No more modding for a bit..well not today anyway

pranks1989 said:
The SBF I posted is for India. You should flash an SBF that suits your region. You said you installed baseband switcher but baseband switcher works only after rooting and you need to make correct changes. So, since you are flashing full SBF I suggest flash the one for your region. There should not be any prob then!
Click to expand...
Click to collapse
No problems here (In the Netherlands) with your ROM (asia version).

Thanks guys for the answers. I'm now running CM9(quartz build) with no kernel flashing. Camera works fine and everything as well. I think I'll stick to this for sometime. Although I see little lag in the homescreen animation and drawers stack animation. But as it is a nightly and still under development, it is quite expected. Also I'll keep using it anyway so that I can help in the development of CM9 by bug and automatic reports submissions.
This was all possible because of the SBF mentioned here..
Sent from my MB526 using XDA

Kernel issue - Bricked By a Stunner Rom version

Hi everyone, I was one of the people who bricked their phone by flashing the ICS Stunner Rom. I thought it would nice if there was a place where we could discuss how to go about solving this. I'm aware that we'll probably just have to send our phones in for repair but I thought it would be best to look at all the options first.

I've ran many versions of the stunner rom without issues. I find it hard to believe you are bricked.
Describe your situation. If the display turns on, you are not bricked. Have you tried connecting to a PC and see if Odin can see your phone?

gedster314 said:
I've ran many versions of the stunner rom without issues. I find it hard to believe you are bricked.
Describe your situation. If the display turns on, you are not bricked. Have you tried connecting to a PC and see if Odin can see your phone?
Click to expand...
Click to collapse
Uninformed fail.
Sent from my GT-N7000 using Tapatalk 2

octavian90 said:
Uninformed fail.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Your right. Why don't you just give the guy razor blades and sleeping tablets even before he explains his issue.
Yes I'm new to the Note but I have brought back many phones back from the "BRICK".

Nothing works, I can't boot into download or recovery

Any ICS kernel based on the leaks seems to carry a danger of permanent damage to the eMMC.
So far the only safe Samsung ICS kernels seem to be those based on the I9100 update4 source base.

Well what would you recommend I do from here though? I want to get this fixed as soon as possible.

Check the end of stunner thread... Send it to mobile video review for jtag
Sent from my GT-N7000 using Tapatalk 2

every time i consider bumping to a Custom ICS I see a thread like this or some issue that is a showstopper for me.
I'm glad I haven't yet had ICS.

I'm also in the same boat as you. I flashed it and it turned into a brick thinking it was the battery being drained. Plugged the phone in and the the phone didn't respond so I knew something went really wrong. Then the bricked news followed on the thread. There is pretty much nothing we can do right now but to send it out to get a JTAG, which is not a guaranteed fix either according to some folks in the thread. The very last resort is to replace the mainboard.

sutekidane said:
I'm also in the same boat as you. I flashed it and it turned into a brick thinking it was the battery being drained. Plugged the phone in and the the phone didn't respond so I knew something went really wrong. Then the bricked news followed on the thread. There is pretty much nothing we can do right now but to send it out to get a JTAG, which is not a guaranteed fix either according to some folks in the thread. The very last resort is to replace the mainboard.
Click to expand...
Click to collapse
don't lower your hopes down, I've seen countless and numerous times of Bricked Notes being revived and restored thru JTAG. This process is the much low level process you can get of restoring your Note into it's normal process. I don't see why your Note can't be restored if it's done thru JTAG.
(Not unless you have a broken ICs or chipsets already, which contitutes a hardware failure and that's the time you may have to replace it.)
JTAG is trusted already and proven to restore almost all bricked Notes.
Just from my own experiences..
Cheers

Its not coz of stunner from... its coz of lp5 kernel with a malfunctioned recovery during system partition format... so please change your title
Sent from my GT-N7000 using xda premium

sorry to hear that guys i was very reluctant to switch from stunner 5 to any other version....im staying with 5 until it gets stable.....i heard about the bricking earlier today....thats ****ed ...i know they figured it out already...and lp5 is part of the problem as well....good luck

MrSlippyFist said:
sorry to hear that guys i was very reluctant to switch from stunner 5 to any other version....im staying with 5 until it gets stable.....i heard about the bricking earlier today....thats ****ed ...i know they figured it out already...and lp5 is part of the problem as well....good luck
Click to expand...
Click to collapse
Just installed 1 4.26... I would recommend you to try it...its on another level than beta 5 ...very smooth n stable
Sent from my GT-N7000 using xda premium

thebz1 said:
Hi everyone, I was one of the people who bricked their phone by flashing the ICS Stunner Rom. I thought it would nice if there was a place where we could discuss how to go about solving this. I'm aware that we'll probably just have to send our phones in for repair but I thought it would be best to look at all the options first.
Click to expand...
Click to collapse
try to use jig bro maybe it will solve the gnote

Oh no...not another CWM touch recovery-esque fiasco. I thought we were over that? And, damn that sucks dude. I've been in your exact shoes. This is my second phone, and I currently use Stunner as my daily driver...so I'm a bit worried now!

androidindian said:
Its not coz of stunner from... its coz of lp5 kernel with a malfunctioned recovery during system partition format... so please change your title
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
so why aren't the other roms running lp5 bricking the phone?

androidindian said:
Its not coz of stunner from... its coz of lp5 kernel with a malfunctioned recovery during system partition format... so please change your title
No it's a specific problème of stunner... It happens...
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Envoyé depuis mon GT-N7000 avec Tapatalk

thebz1 said:
Well what would you recommend I do from here though? I want to get this fixed as soon as possible.
Click to expand...
Click to collapse
do you have a JIG or the tools to create one by yourself ? this seems your only solution for now, anyway does your phone enter to boot animation or it just doesn't flick ?!

there isnt much any of us who had our phones bricked can do about, and yes it was a version of ics stunner that did the damage, i have a feeling its gonna be a motherboard replacement

[Q] MyTouch 4G boot loop

hi
ill been searching for weeks on the internet and here and i cannot find an answer to what is really causing the boot loop problem when i connect the charger or disconnect the charger.
to get the phone to work again i have to do the twist fix to get it to boot but as soon i connect the charger it restart it self and bootloop i have to twist again to boot, then when i disconnect the charger the same thing.
my question is do anyone ever find out what is causing this or where on the motherboard lies the problem?im assuming is probably close to the charging port. anyone have an idea where exactly the problem is?sorry if this been answered before but honestly i did not find it.
i know is an old phone but i like it is a good backup phone.thanks for taking the time to read this...

anyone?

What recovery do you have.
What rom are you running.
What is your emmc chip.

N_otori0us_ said:
What recovery do you have.
What rom are you running.
What is your emmc chip.
Click to expand...
Click to collapse
thanks for answering well im not 100% what recovery version is on i factory reset the phone then rooted unlock with gfree and if i remember well i use rom manager to install the recovery.
the rom im running now is Android_Revolution_HD-Glacier_7.0.4
and my emmc chip is SEM04G

Switch roms. Try out cyanogen 7 nightly.
If it still bootloops there then its a hardware issue
Sent from my HTC Glacier using Tapatalk now Free

N_otori0us_ said:
Switch roms. Try out cyanogen 7 nightly.
If it still bootloops there then its a hardware issue
Sent from my HTC Glacier using Tapatalk now Free
Click to expand...
Click to collapse
ill give that a try and report back thanks for your help.

N_otori0us_ said:
Switch roms. Try out cyanogen 7 nightly.
If it still bootloops there then its a hardware issue
Sent from my HTC Glacier using Tapatalk now Free
Click to expand...
Click to collapse
well i did install cm7 nightly the latest and still when i connect the charger it reboot and bootloops i still have to do the twist fix to boot completly
i guess is hardware problem and im assuming is around the charging port because with the twist fix thats where most of the pressure is put on.
anyone knows exactly where it is so i can do a permanent fix and not twisting the phone every time to boot, i know it works now but for how long before something get damage inside by doing this.any help will be appreciated or i might have to give up on this phone.
i know for sure the emmc chip is fine because a few days ago i flash stock rom successfully. . thanks everyone

Ive never actually heard of that problem but it might be a loose flax cable that signals something and causes it to bootloop.
Do a logcat and then.show us the output.
Also instead of saying thanks press the thanks button.
Sent from my HTC Glacier using Tapatalk now Free

Red and green led not working

Friends,
I have a N9005 and some days ago, I saw that when I put it to charge, the red led didn´t turn on. The same when the batery was low.
In hardware test only the blue led works..
Do you thik this is a hardware fail or it can be a software glitch ?
I have root and custom rom (arya 2.1 marsmellow) with lss 3.9 kernel, but this failure didn´t happen after flash anything new.
Thanks

Flash stock rom and test .

JJEgan said:
Flash stock rom and test .
Click to expand...
Click to collapse
Thanks,
But I prefer to miss the leds to flash all the things again.
And the LED problem happens a lot of time after I flash arya ROM

You have answered your question .

JJEgan said:
You have answered your question .
Click to expand...
Click to collapse
By your answer I think that my english isn´t very good kkk
I try to say that the problem with the LED didn´t happen SEVERAL times after a flash custom ROM/Kernel, but that I flash ROM/kernel later in January, and the problem begins only 1 or 2 week ago..
OK, this not exclude the problem be related with ROM, but, if there is a low level hardware test that can be done with LEDs to eliminate a hardware problem, I think is better to try this before have to flash old ROM and have the conclusion that this didn´t solve the problem..
As I said, I use the phone hardware test *#0*# and the blue color works. But I don´t know if this test is realy low level or can have some influence of ROM/kernel.
Thanks

mangaba said:
Thanks,
But I prefer to miss the leds to flash all the things again.
And the LED problem happens a lot of time after I flash arya ROM
Click to expand...
Click to collapse
You don't HAVE to re-flash everything again. Create a backup with nandroid, factory reset, flash stock and then test. If it is a software glitch, you will know and will have to make a decision on if you want to keep your ROM. If it is a hardware malfunction, you can go back and restore your nandroid backup without any harm but you will know for sure that it is hardware related and not software.