Develop Bugs

Resetting and turned into a hard reset?

any time now on any rom, i'll soft reset my phone and all of a sudden it goes to the windows mobile start screen with the screen calibration.. (basically a hard reset to a clean os)
how do i fix this, i been trying to find a solution to this problem for some time now but haven't got a concrete find for it

ezsoulja said:
any time now on any rom, i'll soft reset my phone and all of a sudden it goes to the windows mobile start screen with the screen calibration.. (basically a hard reset to a clean os)
how do i fix this, i been trying to find a solution to this problem for some time now but haven't got a concrete find for it
Click to expand...
Click to collapse
I am sure I have advised this when you wrote on one of the threads. Try flashing a shipped rom first, it is in my 4shared, doesn't matter if you have AT&T 8525 or not as it works for my jasjam. Flashing too many radios may kill your phone. So ... flash that and then flash the one you want ..
I have not in my time flashing my phone and my customer's phone that a soft reset causes a hard reset after following the doctors instructions

i will try that but what does the regular att rom have that customs dont to stop this from occuring

ezsoulja said:
i will try that but what does the regular att rom have that customs dont to stop this from occuring
Click to expand...
Click to collapse
As I mentioned no issues for me yet touch wood/knock on wood as your part of the world probably accustom to.

ok so far so good, no more hard resets but i just wondered what the original att stripped rom is actually doing to stop this from happening and how much more to reflashing the roms before it happens again..

it has something to do with the big storage/non big storage flashings etc and that shipped rom sorta resets it all to an acceptable state to the phone's brain so to speak .. the doc's never wrong

ezsoulja said:
ok so far so good, no more hard resets but i just wondered what the original att stripped rom is actually doing to stop this from happening and how much more to reflashing the roms before it happens again..
Click to expand...
Click to collapse
In a normal rom, the flash rom is split into two pices, ext rom and storage rom.
In a bigstorage rom, this boundery is removed.
Now, over time, this causes instability in the way windows access and manages the rom, leading to data loss (random hard resets).
Flashing a OEM rom with a OS partition and a Ext rom parition acts as a spring clean on the memmory layout, thus, stability.
As with windows, most things are solved by formating your HDD and starting again, its the same kinda thing!

Great.. Thanks guys, im back to normal now with no hard resetting.

Semi Bricked phone

I think I've managed to semi brick my phone. I was playing around with flashing my phone with some roms and also tested out Android. I've had my phone for months now, and have flashed many times with no problems.
My problem - after using the phone somehow the phone storage gets corrupted and I can't run any programs. The start button and settings don't work. This is fixed by a hard reset.
Anyone else had this??

Now hat are you finally have and after this problem happened, did you try a different ROM?

yep, tried a different rom. first I had udK's beta 5 ROM. i thought it was that so I tried AZTOR v7. but the same thing happens. The phone storage seems to eventually get ocrrupted and the phone won't boot up or randomly boots up as If I did a hard reset but then touchflo won't install properly and only a proper har reset will cure this (for a short while)

benssson said:
yep, tried a different rom. first I had udK's beta 5 ROM. i thought it was that so I tried AZTOR v7. but the same thing happens. The phone storage seems to eventually get ocrrupted and the phone won't boot up or randomly boots up as If I did a hard reset but then touchflo won't install properly and only a proper har reset will cure this (for a short while)
Click to expand...
Click to collapse
i had a similar problem in udk beta 3 or 4, then i went back to stock rom and its all good now (but after that i change the rom every couple of days - rom junkie)
and also, as far as i know, the phone is not bricked as long as it can enter in boot loader mode.
its eather bricked or not.

nblakqori said:
i had a similar problem in udk beta 3 or 4, then i went back to stock rom and its all good now (but after that i change the rom every couple of days - rom junkie)
and also, as far as i know, the phone is not bricked as long as it can enter in boot loader mode.
its eather bricked or not.
Click to expand...
Click to collapse
Thanks. Seems your right. I've flashed the stock Orange ROM and it all seems to be okay now. seems you can't semi brick you phone

benssson said:
Thanks. Seems your right. I've flashed the stock Orange ROM and it all seems to be okay now. seems you can't semi brick you phone
Click to expand...
Click to collapse
Furthermore I suggest you the complete hard reset, including the internal memory. It solved me a problem with stability of the operative system.

paolo the doctor said:
Furthermore I suggest you the complete hard reset, including the internal memory. It solved me a problem with stability of the operative system.
Click to expand...
Click to collapse
Thanks, The stock rom seems to be working well anyway but I'll give that a go.

[Q] Screen becomes unresponsive

Hello and good afternoon,
I received this Xperia Arc (LT15a) from my dad to fix and I can't get it worked out so here it is
When you unlock the phone the screen responds to touch, I can swipe back and forth as one would expect. If you keep your finger on the screen or touch it atleast every second the screen stays responsive. If however you stop using the screen, sometimes for 10 seconds most the time just 1 second and the screen will no longer respond. In order to get the screen to respond you have to lock the device and unlock it again, as if refreshing it or restarting the touch screen service in the phone is the fix... temporarily.
I saw a thread somewhat like this and the fix was to downgrade to make sure no bad firmware had been put on so I downgraded to the 4.0.2.A.0.42 that the phone shipped with. This didn't solve the issue. I tried all sorts of firmwares thinking perhaps one would work. My dad tells me that this started happening when he updated the phone to 4.0.4 through the Sony upgrade software.
Has anyone run into this or do you guys believe this is more likely to be a hardware problem (which seems strange because I would think the screen should either work or not)
Thank in advance.

Hi @Laydas,
This is a weird one, for sure.
I've seen something similar on my phone, and for me the problem was definitely linked to an "upgrade / downgrade" kind of thing.
My solution was to install another rom.
So now I guess your bootloader is locked (because the phone is not rooted).
So the best thing to do is to try flashing a stock rom using "flashtool".
Here's some pointers to help you on your way...
Try this thread - http://forum.xda-developers.com/showthread.php?t=1304634
you're looking for info on flashtool, and on stock roms (I think that some stock roms are available in post 2 of the thread)
On top of that, there is an older thread (so a bit outdated) here - http://forum.xda-developers.com/showthread.php?t=1133650
It has good background reading thread to get a grip on all the ideas involved.
Good luck

I forgot to mention that I had already rooted the phone
I have used flashtool to restore the stock rom which didn't solve the issue either.
I have now taken the phone apart to check for loose connections, everything looked good.
I put the phone back together, tried it out, I still have the same screen issue.

Laydas said:
I forgot to mention that I had already rooted the phone
I have used flashtool to restore the stock rom which didn't solve the issue either.
I have now taken the phone apart to check for loose connections, everything looked good.
I put the phone back together, tried it out, I still have the same screen issue.
Click to expand...
Click to collapse
OK, wow. This problem is really sticking around.
So my next question is: - Do you have an unlocked bootloader?
If yes, then try flashing a custom kernel and a custom rom.
My favourite ICS based rom is JJ's Hybrid - http://forum.xda-developers.com/showthread.php?t=1537717&highlight=jj+hybrid
It works 100% with the ArcKnight kernel.
If your bootloader is locked, then you cannot flash a custom kernel. You can still try try the JJ Hybrid rom to see if it sorts out the problem.
At this point I'm running out of ideas. For me this issue was software related, so flashing a different kernel and rom fixed my problem.
It seems like your issue is software related too (because it popped up after an upgrade), but if you flash a rom and a kernel, then there's not much else that you can try flashing,,,
OK, maybe there's also a base-band you can try flashing - There's a base-band thread here - http://forum.xda-developers.com/showthread.php?t=1688049
So try a custom rom and a custom kernel, and if that fails try updating your baseband to 72 or 77.
That's all I can think of to completely overhaul your phone's software.
Please let me know how it goes...
Take care,
Hotfingers

The bootloader is locked on this phone unfortunately.
This phone is not like my other phones, even trying to get a custom rom onto it is a hassle as installs from zips in CWM almost always fail.
Pushing roms from flashtool works but I couldn't find the JJ hybrid rom in a ftf format for flashtool.
At this point I will continue trying to get a custom rom onto this phone when I have time but it has dropped off my priority list as it is being so difficult haha.
Thanks for the help, hopefully sometime next week I will be able to go through some of these steps and get back to this post on what helped

Laydas said:
The bootloader is locked on this phone unfortunately.
This phone is not like my other phones, even trying to get a custom rom onto it is a hassle as installs from zips in CWM almost always fail.
Pushing roms from flashtool works but I couldn't find the JJ hybrid rom in a ftf format for flashtool.
At this point I will continue trying to get a custom rom onto this phone when I have time but it has dropped off my priority list as it is being so difficult haha.
Thanks for the help, hopefully sometime next week I will be able to go through some of these steps and get back to this post on what helped
Click to expand...
Click to collapse
OK, thanks for the feedback. This isdefinitely weird...

[Q] Serious (BIG) problem with DHD. No GUI, can't even finish setup.

So 2 days ago a friend bought an HTC Desire HD. It was working fine, but since it was second hand he wanted to hard reset it, and so he did. After he did that it started doing what I am showing in the video below(but it was with an older version, gingerbread I think). It was also going in CWM 10 sec after it was put into a charger. After I tried installing custom roms and roots, I installed what is said to be a stock ruu:
RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed
Click to expand...
Click to collapse
It is obviously(visually) a newer version of the software the phone uses, than the one it had when he first gave the phone to me.
Nothing seems to have worked at this point, I'm desperate. After that 4th option of the setup(scheduled sync) it just goes black screen with a status bar and nothing. When he first gave it to me it used to display an error that said something like setup couldn't load, and with options to close it, wait for it, or tell HTC about it. It CAN receive SMS and calls, but there just isn't any GUI(menu, or whatever it's called).
I'm also providing a picture of the bootloader below.
I don't need the phone to be rooted or with any particular ROM or version, I just need it working normally.
Any help/assistance will be welcome! Thanks in advance
VIDEO:
youtube.com/watch?v=aNI1t4KjY-0&feature=youtu.be

youtube.com/watch?v=aNI1t4KjY-0&feature=youtu.be
Just makes it easier to click on it. :beer:
Edit: Try booting without the sd card, but aside from that, no idea.
You can also try flashing a stable gb rom see if you get the same issue.
Sent from a dream.

<-------- new user here. cant post links thanks

iLoveAlkohola said:
<-------- new user here. cant post links thanks
Click to expand...
Click to collapse
If you already have s-off and cwm, why not just flash rooted stock rom? It should work fine if the rom can be flashed successfully.
If it is not, it is most probably hardware issues, although i am not so sure myself.

yumm91 said:
If you already have s-off and cwm, why not just flash rooted stock rom? It should work fine if the rom can be flashed successfully.
If it is not, it is most probably hardware issues, although i am not so sure myself.
Click to expand...
Click to collapse
As I said, before installing the newest stock ruu(with which I lost cwm and can''t seem to get it back), I installed some custom roms, all of them with the same effect. But thanks for the suggestion.

iLoveAlkohola said:
As I said, before installing the newest stock ruu(with which I lost cwm and can''t seem to get it back), I installed some custom roms, all of them with the same effect. But thanks for the suggestion.
Click to expand...
Click to collapse
Make a full wipe before flashing the Ruu. Flash a custom recovery in fastboot, do a full wipe, then flash a ROM (stock or custom) To see what happens

Already did all that. When I first got the phone I used the full wipe function of cwm(and of the stock recovery) a couple of times, but every time it was stuck at that point of the initial setup with the error showing up.
Is there a file SPECIFICALLY for the initial setup that I can flash to the phone, because I flashed different recoveries, roms, boots and even radios manually before installing the stock ruu. I haven't set up a phone before, so I'm not sure, but as I can see there are still 2 or 3 options left to select ,after that scheduled sync option, before the phone could run the main menu(gui or whatever).
Oh, and btw, when I updated it with that ruu, the setup visually changed and by that I figure out it gets flashed as part of the ruu, but still with the same problem. Can it be some kind of hardware problem of the internal memory? No matter how much I searched and where I looked I never found someone with a problem even close to this one.
Teichopsia said:
Edit: Try booting without the sd card, but aside from that, no idea.
You can also try flashing a stable gb rom see if you get the same issue.
Sent from a dream.
Click to expand...
Click to collapse
Whatever I was doing to the phone it didn't usually have an sdcard in it and was booting without an sd card, tried with and without, no changes.
After I installed that sense ruu i can't seem to get back to gb, any ideas how to do it? I also can't get cwm to work now, even though it flashes without any error or problem I can only ge the htcdev root(already did) with this ruu, I think but I don't get any changes except that there is a watermark on the first line of bootloader.

Help!! Phone constantly freezing!!

Hello,
Got an S9 wich has been smoothly running SoLdierR ROM for a couple of weeks. Until two days ago, when my phone decided otherwise. If I restart the phone, the freezing stops for a bit and isn´t noticeable until I start opening apps and that´s when it starts getting really annoying. After that the freezing starts occuring in intervals every 10sec for 3-4 sec. This is making me miss messages/voice calls if these occur during freezing intervals. If I remembers correctly, this started right after I cleared phone memory a couple of days ago. Is there any way to resolve this without me having to backup data and restoring phone?
What I've tried doing so far:
Restarts, shutting down phone for longer periods of time, booting in safe mode (still freezing), booting in recovery mode and deleteing cache/dalvik, deleting apps recently installed, inactivating google apps (google, google play, google services) and deleting cache then unstalling update and then reactivating them, removed root.

yarmannen said:
Hello,
Got an S9 wich has been smoothly running SoLdierR ROM for a couple of weeks. Until two days ago, when my phone decided otherwise. If I restart the phone, the freezing stops for a bit and isn´t noticeable until I start opening apps and that´s when it starts getting really annoying. After that the freezing starts occuring in intervals every 10sec for 3-4 sec. This is making me miss messages/voice calls if these occur during freezing intervals. If I remembers correctly, this started right after I cleared phone memory a couple of days ago. Is there any way to resolve this without me having to backup data and restoring phone?
What I've tried doing so far:
Restarts, shutting down phone for longer periods of time, booting in safe mode (still freezing), booting in recovery mode and deleteing cache/dalvik, deleting apps recently installed, inactivating google apps (google, google play, google services) and deleting cache then unstalling update and then reactivating them, removed root.
Click to expand...
Click to collapse
when you installed your custom ROM, did you delete the folder on internal storage named "android"?

youdoofus said:
when you installed your custom ROM, did you delete the folder on internal storage named "android"?
Click to expand...
Click to collapse
I believe I did, used TWRP and wiped everything before installing my custom ROM. I'am starting to think about doing a clean install all over again however, that won't mean that this issue won't come back later?

yarmannen said:
I believe I did, used TWRP and wiped everything before installing my custom ROM. I'am starting to think about doing a clean install all over again however, that won't mean that this issue won't come back later?
Click to expand...
Click to collapse
considering there arent that many variables that go into ROM installation, its likely just some one-off situation. If it wasnt, there would be a ton of folks reporting the same issue. Sometimes dropping fat man or little boy and starting over is all thats left. Been there so many times with the S3 and S5, i cant even begin to tell you.

youdoofus said:
considering there arent that many variables that go into ROM installation, its likely just some one-off situation. If it wasnt, there would be a ton of folks reporting the same issue. Sometimes dropping fat man or little boy and starting over is all thats left. Been there so many times with the S3 and S5, i cant even begin to tell you.
Click to expand...
Click to collapse
Yepp! I doing a clean install atm. Got another question wich is a bit off-topic. I'am using soliders latest ROM, I noticed he did release a new firmware update. Is it enough flashing the ROM or do I have to flash firmware by itself later? Or do I simply do nothing after flashing the ROM? Sorry if I'am asking obvious question but this a all still new to me.

yarmannen said:
Yepp! I doing a clean install atm. Got another question wich is a bit off-topic. I'am using soliders latest ROM, I noticed he did release a new firmware update. Is it enough flashing the ROM or do I have to flash firmware by itself later? Or do I simply do nothing after flashing the ROM? Sorry if I'am asking obvious question but this a all still new to me.
Click to expand...
Click to collapse
no worries mate, we all try to take a look at members post count before casting judgement on them for the question they asked. For that matter, we try to avoid casting judgement period, and im saying that as a member, not a moderator.
im not directly familiar with the soldier run of ROMs, but if the firmware version has changed, it is wise to install the full firmware.
Also, i wouldnt consider what you asked to be off topic at all.

youdoofus said:
no worries mate, we all try to take a look at members post count before casting judgement on them for the question they asked. For that matter, we try to avoid casting judgement period, and im saying that as a member, not a moderator.
im not directly familiar with the soldier run of ROMs, but if the firmware version has changed, it is wise to install the full firmware.
Also, i wouldnt consider what you asked to be off topic at all.
Click to expand...
Click to collapse
Good to know
I've run into a problem after flashing the custom ROM. I'am stuck on the Samsung logo, what should I do? Would appreciate a step by step explanation.

yarmannen said:
Good to know
I've run into a problem after flashing the custom ROM. I'am stuck on the Samsung logo, what should I do? Would appreciate a step by step explanation.
Click to expand...
Click to collapse
well, you have TWRP and magisk installed, i assume. Correct?

youdoofus said:
well, you have TWRP and magisk installed, i assume. Correct?
Click to expand...
Click to collapse
Yes! TWRP is installed. Magisk got installed with the ROM.

yarmannen said:
Yes! TWRP is installed. Magisk got installed with the ROM.
Click to expand...
Click to collapse
to be perfectly honest, if youve done all the things in the OP and its still doing that, its time to drop fat man or little boy and start from stock tar.md5. Boot to DL mode and flash the stock firmware. Obviously something is awry and the usual tricks didnt help so far. Mushroom cloud time