Ok.
first off, Hii!! this is my first ever time writing on XDA.
Any way, i know this is not a new issue.. but my ATIV S is rebooting every 5 seconds after the 8.1 update via preview for developers.....
i did a lot of digging before writing here and found this thread : http://forum.xda-developers.com/showthread.php?t=2718023
I followed the instructions and flashed the GT-I8750_DXBMJ1_R_signed ROM along side the GT-I8750_VJALL3_P csc (this is the only combination that gave me some results.
After flashing, my phone did manage to boot up finally but with a twist. Trying to restart the phone sends me back to the boot loop forcing me to reflash everything again.
i tried the tip from the thread to download the preview for developers app and try to update the phone again (claiming it will resolve the issue) but as soon as the phone goes to reboot before the update the boot loop comes back and we're back to squire one.... so i'm kinda stuck.... is there any kind of FIX i can try to help me sad situation? :crying::crying::crying::crying:
I've had a lot of issues with my Ativ S as well.
Your rebooting issue seems recognizable, maybe this thread will help : https://social.msdn.microsoft.com/F...ime-after-wp-81-update?forum=winphoneosissues
Anyway, I'm on the latest Developer Preview update, my Firmware version is : 2424.14.9.3
It seems the phone is much more stable now, however i'm only using this phone for development, there is no sim card present anymore.
Switched to a new Nokia for my main device.
Advice : If you want a decent Windows Phone, buy a Nokia, not a Samsung or HTC.
Thank you for the reply!
i did some more digging and found that flashing the GDR2 FW 2424 actually helps. after that the is a need to update the phone to the official GDR3 update in the phone updater in settings. i am trying that as we speak and really hope it will work
BTW this ATIV S is my backup phone and not my daily driver (i use a Galaxy s4) i just wanna fix it up to use as my work phone. my trust in windows phone is gone for now XD
EDIT: OK, so i followed the thread and applied the instructions...
at first, i flashed the GDR2 official ROM with the instructed csc file and everything booted up well. at this point they say that if the phone is to be restarted the boot loop will come back (it did when i tested it)
afterwards, i installed the preview for developers app and started updating to the official GDR3 update as instructed. it finished up and booted up well. the next step was to update to 8.1... i did and at first it worked well but as soon as i disconnected the USB cable, the loop returned again. (if i connect the USB cable back it's booting up normally)
BTW i tried doing it all from scratch and noticed that in every step of the process, if i disconnect the cable the loop come's back and disappears as soon as i plug it back in... anyone has any idea what to do next?
Related
Hello,
I received an XDA Mini II and am having a few issues. Firstly the person who had it 'attempted' installing Windows Mobile 6 that is available on torrent and ran the file 'EnterBL' and it went into boot loader (and goes into it nearly always). However now I have it was able to 'hard reboot' it and get the normal screen to come up and it seems to have reset it since it is taking me through all the welcome stuff.
But it goes to install all the programs and then reboots back into bootloader and cycles through all of that again.
What would be the best option. I am happy putting Windows Mobile 2003 back on but what files do I need to do this? is it possible to put WM6 (from torrent) on it with what comes in that torrent?
I am sorry if this is in the wrong section.
Thank you for any help...
UPDATE: I managed to get back into the phone by removing the battery before it did the 'customising' and then when it booted it came up okay. However when ever I reboot it it goes back into 'Serial' bootloader mode and then I have to do the setup all over again.
How can I stop this?
MattJ1989 said:
Hello,
I received an XDA Mini II and am having a few issues. Firstly the person who had it 'attempted' installing Windows Mobile 6 that is available on torrent and ran the file 'EnterBL' and it went into boot loader (and goes into it nearly always). However now I have it was able to 'hard reboot' it and get the normal screen to come up and it seems to have reset it since it is taking me through all the welcome stuff.
But it goes to install all the programs and then reboots back into bootloader and cycles through all of that again.
What would be the best option. I am happy putting Windows Mobile 2003 back on but what files do I need to do this? is it possible to put WM6 (from torrent) on it with what comes in that torrent?
I am sorry if this is in the wrong section.
Thank you for any help...
UPDATE: I managed to get back into the phone by removing the battery before it did the 'customising' and then when it booted it came up okay. However when ever I reboot it it goes back into 'Serial' bootloader mode and then I have to do the setup all over again.
How can I stop this?
Click to expand...
Click to collapse
Its a bad flash,extended rom has got corrupted,download the official carrier's rom from its official website for the make & model of your phone and reflash it.It'll srart working to default status.After that if you wish you can upgrade to any wm6 latest rom by following the correct unlocking and upgrading method as per your device.
Secondly,don't download Roms from Torrents,as they usually are corrupt or virus infected.Always get Roms from here from xda-developers forum or from the official carrier's website.
Good luck
Now just had a little problem. I updated to Darky's 8.1 no wipe version. It updated fine but the first time it booted, it froze. Now it keeps doing a boot cycle over and over again. I see the i9000m screen but I do not get to the S logo screen or in this case the transformer screen because it reboots. Can you help me plz? Thanks.
Zink6 said:
Now just had a little problem. I updated to Darky's 8.1 no wipe version. It updated fine but the first time it booted, it froze. Now it keeps doing a boot cycle over and over again. I see the i9000m screen but I do not get to the S logo screen or in this case the transformer screen because it reboots. Can you help me plz? Thanks.
Click to expand...
Click to collapse
try a re flash of another ROM preferably a stock ROM then start all over again, similar thing happened to me earlier, i am quite new to all this but i dont know if its the kernel or lagfix i had what caused this...
i re flashed back to froyo and then installed darkys ROM then re installed my kernel last.. all is good (for now)
worked for me first time but when i went to sgs tools to upgrade your apps ie gallery, camera, it said no busybox installed but went ahead and done fine in v8.0 and i see that cwm changed from red to green too went to market for busybox to download it but when it goes to install phone just reboots all the time mmmm...
Easiest way out of cycling boot:
pull battery
place it in
bring phone in download mode (not recovery!)
prepare Odin with a stock ROM
connect the phone to your PC and give it a kick thru Odin
When done feel free to switch again to Darkys (8.0) with wipe (you will loose data) and afterwards upgrade to 8.1.
stepsch said:
Easiest way out of cycling boot:
pull battery
place it in
bring phone in download mode (not recovery!)
prepare Odin with a stock ROM
connect the phone to your PC and give it a kick thru Odin
When done feel free to switch again to Darkys (8.0) with wipe (you will loose data) and afterwards upgrade to 8.1.
Click to expand...
Click to collapse
YES !!! i agree, it is a pain.. but we love our phones and we would do anything for them its always best to flash back to standard FW if you ever get a problem...
I myself experienced this. Whenever I installed a new software, it would just boot. I got fed up because darky's forums are also down and there is no discussion. flashed doc's rom. Now everything is fine.
...mh... but it's not caused by Darkys ROM. This cycling boot feature may appear at all ROM, at all lag fix actions and so on. It depends how proper you interact with phone- and ROM-features while configuring. A lil disturbance during your session (by you or battery issue or whatelse) or a not so well prepared basic from where you start and your unlimited-feature-wishlist-and-paint-it-golden-one-click-action is enough to interrupt the whole thing and run into trouble.
It was and is all the same - since DOS or C64. And it will be the same, even when iPhone is on level 12.x or Android will be able to beam you elsewhere thru the barcode scanner.
It's a game. Nothing more. And game means lot of fun - and in the beginning a certain thrill when your phone stuck first time and you are thinking: "... f*ck... bricked..."
yup same for me
cycle boot thing
didnt enable download mode before that....
can get into debug screen thou but wiping it doesnt help
anyone with a suggestion on what i can try? warrenty = off so im screwed otherwise
anyone with a suggestion on what i can try? warrenty = off so im screwed otherwise
Just tell the warranty guy darky screwed it .
OR
http://forum.xda-developers.com/showthread.php?t=853950
jje
cant even boot the phone mate
so ehm i dont get it....how can odin help me ?
is there any way of getting it into download mode still when it doesnt boot up? i heard about that JIG thing they made themself...isnt that just like the microusb cable that comes with it to the pc? i dont get it sorry if im trippin but im maddd at myself for even trying this lockscreen thing
http://forum.xda-developers.com/showthread.php?t=819551
jje
Thanks guys for all the replies. Now I did try flashing a stock rom but with no results. Was still having the same thing happening to me. If you guys can give me the link to the files you used to solve this problem, that would be great. Also just for your information I have a Bell i9000m unlocked running on fido. And NO its not an sd card failure lol.
As for DarelSteilz85, I did make one of those JIG usb for myself. It easy, just get the micro usb and strip it bare to the point you can see the pins on the usb which usually are connected to the wires and get a resister to connect one pin to another. Now for which pins, I remember it was 4 and 5 that you had to connect through the resistor but double check as I am not sure. Also the resistor has to be a certain level which I forgot so double check that also. Good luck.
http://forum.xda-developers.com/showthread.php?t=853950
What i use for problems .
jje
Hi guys,
Gone through about 100 threads these last couple of days, but nothing helps, so have to start a new one.
What happened was that the other day my phone started ringing.
The screen however was black, so I could neither see who was calling nor answer the call.
I let it ring out, then I held the power button so it would shutdown.
Tried to restart it, and that's when the fun started.
The phone got stuck in a boot-loop, only showing the Galaxy S logo (not getting to the animated one).
Left it in this loop for several hours, since I've had problems recently with the phone needing to do this cycle 5-10 times before booting up.
This time it wouldn't boot, however.
I've tried putting the phone in a bag of rice for 18 hours, in case of any moisture inside, not helping.
Then I tried recovery-mode, formatting the whole thing, but I got the following error:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
Found this thread to try to fix the format error.
Got into download mode, but Odin does not recognize the phone, and I started believing all hope for fixing it without sending it in was gone.
I've also tried applying a couple of update.zip's from the SD-card, just to have tried it, but every package got Signature verifcation-error.
Anyway, when I headed to bed last night I left the phone in the boot-loop, and to my surprice, 8 hours later it had booted into first-time configuration.
YES!!!
Configured the phone with language etc., then all of a sudden the animated Galaxy S logo appeared...
And it appeared again, and again, and again for about 15 min., until I unplugged the battery.
And now I'm back at square one, stuck in the boot-loop (not getting to the animated logo)...
I have the latest versjon of KIES, not that it probably matters.
Does anyone have an idea of what the problem might be?
What rom were you using? stock or custom? Maybe it has something to do with lagfix if it was activated... im guesing, im not dev just normal user... Maybe try to reinstal usb drivers.
Just use odin 1.3 reflash official rom , everything would be OK.
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
mortenlm said:
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
Click to expand...
Click to collapse
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
porkapple said:
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
Click to expand...
Click to collapse
Well, I would have if I knew... But stupid me thought that a phone was a phone.
How wrong was I?
Anyway, a little update here (the problem is kind of solved now):
Flashed the phone with 2.3.3 Gingerbread I found on dkszone, after running the steps in the previous mentioned thread.
And the phone started like a charm.
But after a few hours of configuring etc, I managed to insert the SD-card again, and all hell broke loose again...
Come to think about it, thats what I did yesterday too, so I've come to the conclusion that the SD-card is the main problem...
However, now the phone is slow... REAL slow... Kind of like my 1.5 year old HTC Touch Diamond 2 with WP6.5...
It takes up to 2 seconds to open menu items, keyboard etc.
Is there any way to fix that?
Or should I flash it with another ROM?
You mean the external sdcard? Maybe try to format it...
OK, so this is what I've now figured out:
The phone is damaged...
It seems that the internal SD has gone AWAL, and internal storage has somehow created itself on the external SD-card, thus the phone crashed when I switched cards...
When trying to format the USB-storage, I receive error: SD-card has been removed
So I guess I have to ship the phone off to Samsung ASAP...
Hi everyone,
I have in the past switched roms on my Galaxy S before, therefore the issue of bricking my phone is something that doesn't intimidate me too much. However, this time i'm really stumped, and I turn to the gurus here at the forums, hoping a solution can be found.
I had just gotten my phone back from getting its screen repaired (which makes this especially irritating), and my carriers had flashed my phone back to their stock version of android, meaning gingerbread with a lot of bloatware. I decided straight away that I wanted to root my phone today, although I was away from my PC. I had my laptop with me (Macbook Air), but I had never done any flashing from it before, not to mention ever using Heimdall before (I had always flashed with Odin). I downloaded everything, and then I made my first mistake: I flashed a speed mod kernel (I believe it was a froyo kernel), and after reboot my phone wouldn't go past the splash screen. I could still get into recovery and download mode. Then I decided to try playing it safe, and I downloaded stock firmware packages for Heimdall fro the forums here. I tried flashing JVS on my phone, going exactly by the instructions written in that same thread that I found the packages, but the flash didn't succeed. Instead, I got an error message saying the PIT file didn't reach the end of the transfer (or something like that...) and the phone rebooted. After that attempt, the phone went black. Nothing works anymore except for download mode. Now I thought that as long as download mode works, I'll be ok, so I tried flashing different packages through Heimdall, and eventually when I got home I tried using Odin on my PC. The problem is, my PC doesn't recognize my phone anymore (even though the drivers are installed and I never had an issue with that before), so I'm pretty much stuck with a brick for now.
I really don't want to go back to my carrier again, and hope to get my phone back in working order without paying too much. I still think there's hope as long as download mode works.
Does anybody have any suggestions what I might be able to do? Since my PC doesn't recognize my phone (and therefore Odin doesn't either), the only semi-working option left is using Heimdall somehow, but as to how to use it, I'm in the dark.
I would really appreciate any help you guys can give me. Thanks a lot!
Aaron
first try reinstalling the drivers and try again. if you can get download mode, should be repaired.
Thank you very much!!!
I knew that download mode was a good sign, but I started freaking out as soon as Odin wouldn't recognize my phone, since it never has had that problem. Reinstalling the drivers did the trick, and flashing worked.
Sometimes the simplest solution is the best. Again, thanks a lot!
commandozzz said:
Thank you very much!!!
I knew that download mode was a good sign, but I started freaking out as soon as Odin wouldn't recognize my phone, since it never has had that problem. Reinstalling the drivers did the trick, and flashing worked.
Sometimes the simplest solution is the best. Again, thanks a lot!
Click to expand...
Click to collapse
We are here to help.
Hey guys,
as I did not find any matching solutions to my problem (and due to the fact that I can't post within developer forums yet), I opened a new thread. If there has been similar questions like mine with working solutions, then I am sorry to doublepost the problem.
I have a Sony Xperia Z1, model number C6903. I rooted it today, following this method
http://www.youtube.com/watch?v=1aq9YTlfCgc
taken from this original post
http://forum.xda-developers.com/showthread.php?t=2572988
I followed the tutorial step by step, rooted the device properly (worked fine, checked with the root basic app checker or whatever its called), and then wiped all data from it using dualrecovery. After that, i put the .290 software onto my sd card and flashed my phone using dualrecovery - as the tutorial said. Finally, I used Flashtool to flash the C6903_14.2.A.0.290_Stripped.ftf onto my phone.
After this process finished, I wanted to boot my phone.
That was when things got weird: The sony logo appeared for a short time, and then it powered off / rebooted itself. Sony logo appeared again, switched off again and rebooted for another time. But it would not do any more than that... seems like its catched within an endless loop or something.
What I tried to solve this problem:
- enter dual recovery: this worked at the beginning, I could switch my phone off and get it out of the loop
- flashed it again (first with dualrecovery, then with flashtool)
- after that I could not even get into dual recovery mode
- then I tried to flash the .534 ftf firmware onto my device, because with that it worked properly after root. But every time I connected my phone within flashmode to my pc and started the flashprocess, my phone disconnected after a short time and booted into the endless loop again
I don't know what else to try, so I ask you guys for help. Should I leave the phone within the loop for a couple of hours hoping that it starts eventually? Should I try to flash again? Is there any other possibility to enter dual recovery? Should I maybe flash an original sony firmware on it?
Thanks in advantage for your help and time,
flamingo
It sound slike you did everything right, I would repair using pccompanion and start again. Make sure you do every step correctly and in order and don't miss anything
Let us know how you get on
gregbradley said:
It sound slike you did everything right, I would repair using pccompanion and start again. Make sure you do every step correctly and in order and don't miss anything
Let us know how you get on
Click to expand...
Click to collapse
Thanks for the very quick reply. I've just done that, and all went properly! I am now back on .136, and the device works perfect. Think I'll continue with the 4.4 Kitkat instead of the .290, as this did not work out all to well...
Thanks again for your quick and very good advice!
flamingo