Related
Hi all.
On Saturday night my Arc (debranded Rogers, locked BL, rooted with zergrush, running 2.3.4 on firmware .42) was running just fine. We were out at a friend's place and I was calling up photos, doing Web searches, no problem. Then yesterday when I turned the beast on it went into in a bootloop - SE logo, blank screen, SE logo, blank screen ...
I managed to boot into CWM to be able to turn it off, but that was as far as I got (and after a wasted afternoon trying to reflash I can't even get to CWM now).
PCC/SEUS are no help at all - after going through the 'Repair phone' process PCC says there's 'no software available for your phone yet'. I've tried reflashing generic f/ware with both Wotanserver and Flashtool 0.6.8.0; with Flashtool I get the same "Final data verification failed" error as reported recently here with an X10 after 99% complete. And this message from the bottom of the log makes me suspicious Flashtool wants me to change mode, which is just a little tricky when I can't start the phone:
INFO - For 2011 devices line, be sure you are not in MTP mode
Current status is the phone boots to the SE logo, then displays an image of an exclamation mark over a phone - one of the least informative images I've seen, unless it represents a tombstone, which seems very possible! - then dies again.
I've looked at a couple of other XDA threads about bricks; the most promising-sounding one was talking about unlocked bootloaders, though, so I didn't try to flash the file they were talking about.
I might feel slightly better if I'd done something - anything! - like an OTA update or whatever to cause this, but all I did was turn the thing off for the night, as I always do.
Please, somebody: help!!
Thanks, in great anticipation.
Didcha tr y reflashing rom or kernel? Also factory reset might help.
Sent from LT18i @ Xda Premium
Thanks, ArmorD.
Just ROM - I can't do anything with the kernel with a locked bootloader, can I?
I'd try a factory reset if I could get into CWM, but I can't. I tried the reset method from here, but the phone still just goes to the SE logo, then the 'tombstone'.
Open to pretty much anything at this stage!
Well, what you can do is i think re-flash it with Update service, it might work than.
Here is the link to update service since you wont find it in SE website.
http://www.mediafire.com/?mkk2w0os8ak1dzf
:S Nvm. You already have tried update service. didn't saw it when i read it first..
Bro, just reflash the system
I have just ended up with a boot loop on my arc.. I reflashed and it worked well!
-cheers
untouchable123 said:
... I reflashed and it worked well! ...
Click to expand...
Click to collapse
So did I, and it didn't! But thanks anyway.
Further news: trying to eliminate possible causes, I've had the SD card checked (by inserting it in another device). It's quite readable. I didn't really think this problem would have anything to do with the card, but it seemed worth trying.
Well, idk. Sorry bro! Try to flash stock firmware with flashtool! And it might work! Also bricked=phone is not turning on at all! Like u press the power button and nothing is happening. Cheer up man u finally gonna fix it. ;-)
Sent from my LT18i using XDA
i have encounter tha triangle with ! inside and a phone beside it, it happens when i tried flashing my phone using wotanserver,i want to root my phone and tried to downgrade to .42 taiwan ftf,but the file in wotanserver is maybe damage and did not finish flashing,then i got that "tombstone" icon.
what i did was flash it with uk tft .42,and it restored my arc s,after that i flash it again with .62 taiwan ftf since i live in taiwan, i dont know if this will work on your phone. or maybe you already tried doing it. i just want to share what i happen to encounter. hope you fix your phone.
Untouchable: thanks - I wish I shared your faith!
asderth8000: thanks also. I tried a different firmware version tonight (US generic; previously World; also tried Australian) but same result - Wotan dies with 'ERROR: File write failed' while writing userdata.s08. It feels like that's close to the end of the process, which suggests Wotan and Flashtool are both getting hung up at the same place. Screenshot of Wotan error atatched - hope it gives somebody some ideas.
I appreciate your help, people. Keep them thoughts coming!
lol bro stop using Wotan use Flashtool!!!!!!! lol my faith is beyond the limit. I have bricked & ubricked my cell a couple of times;-)
Sent from my LT18i using XDA
I got that same error using .42 Taiwan ftf, maybe try UK, it works fine with me although I don't live in UK.
I remember mine was on userdata.07 when an error occured,I thought at first that it was my connection then I tried doing it again and it failed, then I tried the UK version and it goes well. Save your apn settings too.
Anicane said:
Well, what you can do is i think re-flash it with Update service, it might work than.
Here is the link to update service since you wont find it in SE website.
http://www.mediafire.com/?mkk2w0os8ak1dzf
:S Nvm. You already have tried update service. didn't saw it when i read it first..
Click to expand...
Click to collapse
Update service is available again for some time!
http://www.sonymobile.com/gb/tools/update-service/
---------- Post added at 05:15 PM ---------- Previous post was at 05:13 PM ----------
This package has saved me before, even for things it isn't meant for. Worth trying, won't do any more damage I think.
http://forum.xda-developers.com/showpost.php?p=14774499&postcount=1
It's BAAAACK!
First, and most importantly: I have a phone again.
The eventual answer was this thread, suggested by sdk16420. I hadn't tried it before because it was talking about unlocked bootloaders, but I fired it up this morning and ... guess what? I've spent most of the day restoring things, but I'm pretty much there - even rooted again (lost that along the way). The phone says there's an OTA update for .62 ready, but that failed and PCC doesn't believe it exists. Ah well, there's always something ...
Secondly: huge thanks to the XDA community for your support and suggestions. You guys are OK!
Loosely said:
First, and most importantly: I have a phone again.
The eventual answer was this thread, suggested by sdk16420. I hadn't tried it before because it was talking about unlocked bootloaders, but I fired it up this morning and ... guess what? I've spent most of the day restoring things, but I'm pretty much there - even rooted again (lost that along the way). The phone says there's an OTA update for .62 ready, but that failed and PCC doesn't believe it exists. Ah well, there's always something ...
Secondly: huge thanks to the XDA community for your support and suggestions. You guys are OK!
Click to expand...
Click to collapse
No prob bro;-) ask anything u want and we will try to help;-)
Sent from my LT18i using XDA
PLEASE HELP - Potentially bricked LT18i
slightly different similar problem:
LT18i, 2.3.4 build .62.. or it was!
Wares used: SE Bootloader Lock/Unlocker, Flashtool
Flashtool really should come with a lot more documentation and user guide: I'm a software person, but C++ is my confortable realm!
Managed to flash CWM on there and got it stuck in a bootloop of CWM (trying to install RootXperia.zip): tried many other images, the best I can get is a Sony Ericsson Logo looping.. I guess my SD card is okay.
Can't find an up to date, stock, 2.3.4 build .62 to repair my phone..
Help! A Walkthrough of my problem helps me rinse my degree and this equates to thanks and donations, I am a desperate man right now!
Please hassle me for info, help me help you help me!!
My Arc is Crying too!
PS that r800i ROM didn't work for me!
WHAT I NEED FROM YOU LOVELY PEOPLES:
-A link to the stock ROM or LT18i .62
-noobproof couple of steps to explain flashtool 0.6.8.0
-noobproof steps of how to flash the stock ROM/Kernel back in place
Hope you can help me.. my first flash went entirely squiffy!
Thanks in advance!
Omg plz ignore my noob self, except massive props to doomlord.
Sent from my LT18i using XDA
OK so we got a SE Experia Arc S LT18i with 1253-8238_4.0.1.A.0.165 ('prototype' model on loan from a friend = prehistoric!) and looking into upgrading the thing if at all possible.
So if I am correct it's a case of: 1st: Root, 2nd: Unlock bootloader, 3rd: Install recovery, 4th: Flash ROM of choice
Bootloader is locked and phone not rooted.
Tried using Flashtool to root phone but it is greyed out so tried Tools > Root > Force zergRush = fail, (not tried Force psneuter/Emulator ?)
Tried unlocking bootloader using Flashtool, but this also failed (SE unlock website wanted IMEI code one digit less than the phone reports?!! got a code by ditching the first 0 of the IMEI, but didn't work anyway - crashed phone)
Attempted to root using command line ADB method to push zergRush and execute the script, but this too doesn't work (phone crashes and reboots).
Fastboot? I have it installed but not yet come across any how-to's that use this (did I say yet? )
The apps available on Play Store seem to be automations of above methods for one-click users.
Further exhaustive reading/searching here and on talk.sonymobile.com leads me to believe that the first step might be to flash a different kernel version before it's possible to root, after which everything else should fall into place...I'm up for trying this but of course don't want to risk bricking the phone, so backing up first would be a good plan, *but* I need root to be able to install recovery! I know enough about booting operating systems to know that changing kernel version with a locked boot loader might just result in bork! This is where the expertise of you guys comes in!! Maybe you know that flashing another (similar?) kernel will be fine with Fashtool even without unlocking bootloader and rooting phone? Perhaps I missed a simple and easy way of rooting? Any suggestions very welcome - thanks in advance!
FYI: *I only run Linux* so pointing me at any of the windows tools on offer is of no help to me
Oh and PS: yes I have searched and found a ton of helpful info, well actually *way too much* info to the point of saturation and confusion!! :laugh:
There can never be too much information, yours and others problem is that you try rushing through it, because if you didn't you'd find the answers you were looking for.
Sent from my CM9'd Arc
XperienceD said:
There can never be too much information, yours and others problem is that you try rushing through it, because if you didn't you'd find the answers you were looking for.
Sent from my CM9'd Arc
Click to expand...
Click to collapse
Well it's not the quantity of info, but the quality of info! Failing that the filtration system used to distill the good stuff out!
Anyroads, I was still hoping for someone to chip in with something like "Yeah go for it, that will work fine"! or "Don't do it, try this instead"!
I'm believing from my readings so far, that short of flashing an incorrect radio, or interrupting a flash process, it isn't easily possible to brick an Arc?
acesabe said:
Anyroads, I was still hoping for someone to chip in with something like "Yeah go for it, that will work fine"!
Click to expand...
Click to collapse
I would have just tried it instead of starting a thread to ask, failing that I would have then read the stickys/guides explaining how to unlock and root.
acesabe said:
it isn't easily possible to brick an Arc?
Click to expand...
Click to collapse
No, you would just use the flashtool to flash a stock ROM.
XperienceD said:
I would have just tried it instead of starting a thread to ask, failing that I would have then read the stickys/guides explaining how to unlock and root.
Click to expand...
Click to collapse
Well, that's because you are XperienceD!
No, you would just use the flashtool to flash a stock ROM.
Click to expand...
Click to collapse
Ok cool, so Flashtool can be used to save an unbootable device too then...
acesabe said:
Well, that's because you are XperienceD!
Click to expand...
Click to collapse
It's how I got to be experienced. :silly:
acesabe said:
Ok cool, so Flashtool can be used to save an unbootable device too then...
Click to expand...
Click to collapse
Yep, you just need to flash a stock ROM.
XperienceD said:
I would have just tried it instead of starting a thread to ask, failing that I would have then read the stickys/guides explaining how to unlock and root.
Click to expand...
Click to collapse
Me too.
Thread closed.
Hi all!
Okay so I'm ready to bash my face off something till I die... lol I've been up all night screwing with my xperia play from rogers. First I did the touchpoint method to unlock the bootloader and s1tool confirms that it's unlocked. However, no fastboot and when I punch in the code provided by SE to see the value of "bootloader unlock allowed"... it's still "no". From what I understand the touchpoint method shouldn't change this value. However because this value is still set, I have a feeling that this is why I can't enable fastboot.
I'm trying to flash a custom jellybean rom using flashtool and because of the aforementioned situation, I can't. I'm wondering if anyone can point me in the right direction to get fastboot working. I hate that I've paid through the nose for all the android devices I own and I yet I still don't technically own them. Anyway I won't rant....
P.S. Just to be verbose, when I do fastboot.exe devices... just hangs saying waiting for device. Device shows up in Device Manager but is code 31 cannot start. Also if I hold search and plug in USB or any of those combos I absolutely cannot get a blue light. I can also assure anyone that I've spent probably 8 hours straight googling the bleep out of this issue and working on it so I'm not being lazy I've just reached the limits of what I can do on my own and am begging for any help that is available!
Thanks in advance!
Also just more info, I've got the devices rooted if that makes anything simpler or opens up options. I'm also wondering if this might be a driver issue because I was doing this on my windows 8 machine and from 7 up you have to do a bunch of stupid temporary system configurations to allow unsigned drivers plus wondering if it's a driver incompatibility issue. If that's the case can I use flashtool on my linux machine? Something I'll look in to... just wanted to post as much info as I can. Thanks again!
So no one in this forum has any idea?
No one here has absolutely any idea about what I can or can't do with this bootloader situation? Wow....
You dont have fastboot thats why but you can flash. Ftf custom kernels
Sent from my LT28i using xda app-developers app
psxpetey said:
You dont have fastboot thats why but you can flash. Ftf custom kernels
Sent from my LT28i using xda app-developers app
Click to expand...
Click to collapse
Pardon my ignorance.... but you mean I can flash a custom kernel on my rogers r800a that will have fastboot? I'm asking basically because theres a working jellybean rom it but without fastboot I can't use flashtool to flash this custom rom. I'm a bit of a noob sorry and I ought not to be with what I do for a living. lol
Furinax said:
Pardon my ignorance.... but you mean I can flash a custom kernel on my rogers r800a that will have fastboot? I'm asking basically because theres a working jellybean rom it but without fastboot I can't use flashtool to flash this custom rom. I'm a bit of a noob sorry and I ought not to be with what I do for a living. lol
Click to expand...
Click to collapse
When you do test point unlock you don't get fast boot you have to use flash mode and .ft kernel and whatnot go into flash tool and press boot loader unlock it should fail and say its already unlocked
Sent from my R800i using xda app-developers app
Got it!
After much struggle.. I've got it all working and running slimbean. It's quite a huge pain in the rear to get set up so I'll post a complete guide on this thread afterward... especially considering that this thread comes up in top google search results for me when I look up "unlock bootloader R800a" and other such similar phrases.
Furinax said:
After much struggle.. I've got it all working and running slimbean. It's quite a huge pain in the rear to get set up so I'll post a complete guide on this thread afterward... especially considering that this thread comes up in top google search results for me when I look up "unlock bootloader R800a" and other such similar phrases.
Click to expand...
Click to collapse
So uh... what happened to the guide?
someguymartin said:
So uh... what happened to the guide?
Click to expand...
Click to collapse
Honestly this was almost a year ago and I ended up chucking that damn phone out and getting my wife a new one. I barely remember the whole process I just remember it being about 3-4 days of me being intensely angry and frustrated lol. I do recall it involved ripping apart the phone and shorting out certain pins that are covered by the sticker under the battery, but I believe that portion was for unlocking the sim, I really can't remember. I'll see if I can dust off those brain cells and get the whole thing back and post nfo if successful.
someguymartin said:
So uh... what happened to the guide?
Click to expand...
Click to collapse
This I used as for part of the process:
https://www.youtube.com/watch?v=zM8lWE4Layc
However I don't believe this tutorial includes unlocking the bootloader. I believe sony provides a utility or something to unlock the bootloader but you're missing fastboot. I think the process involved flashing a custom kernel, not sure. I'll keep digging into my memory and post more nfo back later. Kernel was Lupus kernel I recall that much.
Edit:
Here is complete guide with bootloader unlock process explained as well.
http://forum.xda-developers.com/showthread.php?t=2187172
More links http://unlockbootloader.sonymobile.com - but as I recall this doesn't work for rogers branded r800a.
Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. I have been trying to unlock this phone for 2 days now!
Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well my code is 16 numbers long. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same.
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.
Tread3r said:
Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. For purposes of convenience and time (I have been trying to unlock this phone for 2 days now!) I will post my IMEI code here ( 3529000059203526 ) and the unlock code given to me by sony through email (61CAA387DC11C4CF).
I hope this doesnt break any rules or anything.
I am doing this to see if anyone here can help me. Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well as you can see my code is 16 numbers long, so in effect I only entered up to number "5". I would like to know if anyone is willing to test my IMEI and see if they get the same code. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key, this is why I am posting. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same (as above).
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.
Click to expand...
Click to collapse
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Thanks for the advice, I will edit it ASAP.
abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Hey he removed the imei number from his original message but that's pointless unless u remove it from your quote
Sent from my Xperia S using xda app-developers app
I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967
Chriszo said:
I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967
Click to expand...
Click to collapse
Glad to hear im not alone . No I still haven't found a way to unlock it. Sorry for asking but what does "PN" mean? Just so we are clear.
Ok thanks for your answer. No problem, but its just a mistake. Correctly it should be "PM" for personal message. I thought you would write on this way so I cant read any reasults
UPDATE:
I have tried other processes that all have the same steps, be it they were simplified programs with GUI's. I have come to the conclusion that my fastboot driver was installed incorrectly, because the first time I installed it on my phone I was able to see the S1 bootloader icon on device manager and I was able to click on it fast enough to enable it to install the driver. And correct me if im wrong but when we press UP on the volume rocker on our XS's and connect it to the USB we should see a blue right light? Well that is what happens when I do it so I assume I installed it correctly then.
Now after these first few failed attempts at unlocking I got frustrated and just factory reset my phone, completely ( I made back ups of course). This time however I used a program which is suppose to install all the drivers and simplify the whole unlocking process, I dont remember what program exactly, i'll check my files and get back to you guys on that.
Again it failed, showing the FAILED ("oem" error message) so I checked the steps from Doomlords guide and re checked my device manager. This time when I connect my phone it doesnt show the S1 bootloader icon on Dev manager, instead it shows "android phone ADB Interface". BUT I still get the blue LED when I connect my phone via USB, so does that mean I have fastboot on my phone again? ( I assume I do because the program I used says it did install it correctly and it even showed the "install anyway" window)
I am almost loosing all hope to unlock my XS , maybe I got a lemon phone or did something wrong again. I am willing to do another factory reset and restart the whole process again. This time I will follow every single step on the official website and see what happens.
But before I do that I want to ask, does anyone know of any news or whereabouts for an unofficial unlock bootloader process? I know its a long shot because we already have an official way but as from recent experience it doesnt work 100% of the time.
Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/
Chriszo said:
Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/
Click to expand...
Click to collapse
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.
Tread3r said:
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.
Click to expand...
Click to collapse
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).
It was AOKP, the advanced project for this device.
I think your right, but in how far is the bootloader linked to the needed kernel? And why cant the bootloader be unlocked several times...?
Of course the kernel is a main part of the rom, but without an unlocked bootloader even the kernel would not be accepted by the bootloader. Thats the problem with other firmwares/ roms why you have to unlock it
I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?
razormc said:
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).
Click to expand...
Click to collapse
I am using Windows 7 and I have used flashtool. I believe the drivers are correct because,as you said, the blue LED does show and stay while I fastboot my phone. Same goes for the green LED when I go to flashboot.
Chriszo said:
I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?
Click to expand...
Click to collapse
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve
Tread3r said:
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve
Click to expand...
Click to collapse
First, unlock your bl. Then root. I done that on my old Arc S and it works great.
Sent from my LT26i using xda developers-app
@ Tread3r:
Yes the drivers are installed correctly, because the phone starts into fastboot and flashboot with each the right light.
Thats the great problem with our devices. I did it nearly the same way and Ive got a similar problem, as the first answers describe in this post. Actual the original stock rom is installed on my Sony and all works correctly, but its just a short-term workaround
The bootloader unlockind process still end in an error message and that is my problem.
@ Vatih:
Nice try, but this is our problem... :/
---------- Post added at 11:41 AM ---------- Previous post was at 10:57 AM ----------
I cant believe it myself, but the alternative way works, althought I cant read anythink in the tool because of the language...
I've got the superuser app and root permissions and all works.
This link helped me: http://forum.xda-developers.com/showthread.php?p=39498268
It's the tool for the "new" firmware, .55, the latest from sony.
Hope, its also succesfully with your devices
I solved our problem. My bootloader is now open
I did it with the unlock, flashtool tool of this forum that helps you to open the bootloader and flash kernels and roms.
http://forum.xda-developers.com/showthread.php?t=2087337
Seems like just the code was wrong.
It worked with the first try
But be careful, although its just the bootloader, all data will be deleted. My phone is empty again :/ Of course I've got some backups...
trying to get twrp on this but ive tried every method possible on here anyone had any luck with Australian variant ?
maybe google?
https://www.youtube.com/watch?v=RT6CjJj-0L0
InFam0us-1985 said:
maybe google?
i cannot find the ash2 firmware for the sm-a505yn ? , if i had the whole build number it might be a bit easier to google..
if anyone has twrp running on sm-a505yn please be kind enough to chime in on what build number etc stock rom ?
ive tried all the methods on here listed.
still no luck what so ever .
i get a message on the download screen after odin flash saying only official binarys are allowed to be flashed.
has anyone had any luck flashing a combination firmware and then trying to install twrp ?
i am on sm-a505yn... if anyone can help me i would be happy to donate 50$ bucks into your account lol bashing my head aagainst a wall here this is day 3 of trying ahrhghghghghgh
Click to expand...
Click to collapse
so after another day of attempting to get twrp on this ive tryed every method on here even flashing different firmware etc, and none of these methods work for the Australian varient. just a warning to anyone in oz thinking of getting this phone for root purposes...
i have wasted over 60 hours trying to do this :|
username1100 said:
InFam0us-1985 said:
maybe google?
i cannot find the ash2 firmware for the sm-a505yn ? , if i had the whole build number it might be a bit easier to google..
if anyone has twrp running on sm-a505yn please be kind enough to chime in on what build number etc stock rom ?
ive tried all the methods on here listed.
still no luck what so ever .
i get a message on the download screen after odin flash saying only official binarys are allowed to be flashed.
has anyone had any luck flashing a combination firmware and then trying to install twrp ?
i am on sm-a505yn... if anyone can help me i would be happy to donate 50$ bucks into your account lol bashing my head aagainst a wall here this is day 3 of trying ahrhghghghghgh
Click to expand...
Click to collapse
"only official binarys are allowed to be flashed" because the bootloader locked. you must unlock the bootloader first.
Unlock Bootloader https://youtu.be/8j6WkOOA3f4
Click to expand...
Click to collapse
mate my bootloader was unlocked.
i have 4 rooted phones i know how to unlock a bootloader.........................
it wasnt the BL it was the method provided that didnt work.
this a50 drove me to the point of being psychotic.
the phone is now gone due to almost being thrown at a brick wall.....
anyways in future someone should do a guide for the australian varient as none of these methods worked for it.... and believe me i tried all these methods even with overseas firmware etc. :good: