Related
hello everybody anyone can help me to put my phone back on service i will donate,i brought my phone from singapore via internet but after i update via OTA my phone died and it not reboot anymore then i read in here and download the Bin4ry file for flashtool, after flashing my phone come back and its booting now but the problem is it show no sevice and insert sim card even the sim was inserted
You should also say that you had UNLOCKED the bootloader and then tried to do some other kinds of flashing with fastboot, only then you tried later to update FOTA, then it bricked your phone.
Anyway, I think you should read this http://forum.xda-developers.com/showthread.php?t=1126358
And I think that since you have mentioned you tried everything, you have to read the above thread and follow the instructions therein very carefully and correctly - hopefully you will get it working and buy me and the creator of the process coffees too.
Appended edit:
Hey, I had got Bin4ry's attention for you here, so please follow up with him or others if you really really want people to help you - help yourself too.
http://forum.xda-developers.com/showthread.php?p=14902255#post14902255
Good luck
I ask you again, which pacakge did you try?
Please give me a link to the post where you downloaded the package.
Regards
http://forum.xda-developers.com/showthread.php?t=1126358, here is the link that i tried but still my neo wont work.
Okay, have you done any additional steps BEFORE you did that?
Regards
no until now im just waiting again and reading any solution here with same problem,by the way before i did that i try this link also and come from your side http://forum.xda-developers.com/showthread.php?t=1056094&page=6
and im voluntarily my device will be your experiment to try any files that will test
Bin4ry said:
Okay, have you done any additional steps BEFORE you did that?
Regards
Click to expand...
Click to collapse
Bin4ry,
You wrote this in some other thread, you said:
"
If you do the trick with flashin simlock.ta as preset.ta you completely damage your Simlock Partiton! You now need to resign it for getting it working again, this can only be done @ SE or by pay Servers on the internet.
So sorry, no way for you to recover in this forums.
The OP is just for people who do not used other recovery tries to get the phone working. It will fix phone completely from dead state, if you already got it working without sim-detection you messed too much. :/"
Is this still true? Meaning, if this is done, there is no hope with any kind of procedure?
better reflash it with stock rom via flashtool
Hi,
I've been reading and reading and reading and I probably havn't read enough, but
I am just straight down curious now.
Is it possible to install kernals and other tweak patches such as http://forum.xda-developers.com/showthread.php?t=1249, or install recovery?
I have a rogers sony xperia arc, rooted 2.3.4 with gingerbreak 1.2
Thank you for your time
See the links in my sig.
I have seen your links, however everytime i try to go into fastboot mode, it just charges and the led light stays green, i can never seen to go into fast boot for some odd reason
if your bootloader is locked you cant get into fastboot i have a rogers phone as well and you need to unlock the bootloader first which costs money. or you can wait and see if someone comes up with another way to enable fastboot withough paying
So there is no way of me installing clockwork mod at all? or installing any patches via flashing? how about the flashtool? would that work?
by the way thank you all for taking your time upon looking at this thread and helping me out
Nope. You can currently only use Flashtool for flashing firmware.
Ah, okay hopefully something works out, thank you so much!
My nexus is rooted and unlocked running stock 4.0.2, no custom ROMs. Received the 4.0.4 ota update this morning. Will it install if I let it, or do I need to follow the instructions that others used to do the early install of the update?
Sent from my Galaxy Nexus using XDA
I am just like you. I have the stock 4.0.2 that came with my phone but I've unlocked and rooted it. Received the upgrade notice this morning and said, "yes", but during reboot all I get is the android lying on its back with a red triangle and exclamation point. I have to pull the battery to reboot but then it only comes back in 4.0.2.
Ok, that's what I expected. Sounds like we need to run the manual update. I'm in the process of packing and moving this weekend so I was hoping for an easy fix. Thx for your reply.
Sent from my Galaxy Nexus using XDA
hey there guys i once had the same problem when i was on stockrom with root:
It is simple : Do not do it!
Either U will get what is described above but atleast you will loose your root rights/ unlockes status.
To upate properly use ClockworkMod (App RomManager) and download an already unlocked version of the current update.
I recommend you to switch to a non stock rom hence u will not get these OTA notifications anymore which you may accept "by accident". Good ROms are CM9, Trickster, Paranoid, just haver a look in the dev section.
cryptiq said:
My nexus is rooted and unlocked running stock 4.0.2, no custom ROMs. Received the 4.0.4 ota update this morning. Will it install if I let it, or do I need to follow the instructions that others used to do the early install of the update?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
If you did not change anything (other than root), you can install it no issue. However, if you have changed your radio, kernel, recovery, or any system file, then the update will not work.
Not however, that you need to install something like OTA Rootkeeper BEFORE you go through the update process, as you will lose root otherwise.
dogunter said:
I am just like you. I have the stock 4.0.2 that came with my phone but I've unlocked and rooted it. Received the upgrade notice this morning and said, "yes", but during reboot all I get is the android lying on its back with a red triangle and exclamation point. I have to pull the battery to reboot but then it only comes back in 4.0.2.
Click to expand...
Click to collapse
That is because you have something that is not stock 4.0.2, be it a kernel, radio, modified system file, recovery, etc.
FellX said:
hey there guys i once had the same problem when i was on stockrom with root:
It is simple : Do not do it!
Either U will get what is described above but atleast you will loose your root rights/ unlockes status.
To upate properly use ClockworkMod (App RomManager) and download an already unlocked version of the current update.
I recommend you to switch to a non stock rom hence u will not get these OTA notifications anymore which you may accept "by accident". Good ROms are CM9, Trickster, Paranoid, just haver a look in the dev section.
Click to expand...
Click to collapse
An update does not affect the "unlocked status" as you say.
See my comments above about root.
You comments about switching to a non-stock ROM don't really make sense for someone who likes stock ROMs and wants to update...
Here you go, a rooted 4.0.4...
http://www.droid-life.com/2012/05/3...6k-build-for-galaxy-nexus-flash-over-any-rom/
efrant said:
That is because you have something that is not stock 4.0.2, be it a kernel, radio, modified system file, recovery, etc.
Click to expand...
Click to collapse
He is right, once upon a time I had flashed a rom and then wanted to go back to stock. I used someones method first (I dont remember whose it was) and I thought I was on stock but I got the android guy on his back and it wasnt working properly (I think the radio was the wrong one) so I then flashed the stock image from Google to 4.0.4 and I was able to get the 4.0.4 OTA no problem and I didnt see the android guy on his back at all during the process.
So more than likely there is something that isnt stock on your phones.
WiredPirate said:
Here you go, a rooted 4.0.4...
http://www.droid-life.com/2012/05/3...6k-build-for-galaxy-nexus-flash-over-any-rom/
Click to expand...
Click to collapse
That is NOT an update. The guy wants to update his build, not flash a brand new one...
same issue
first time poster here. stumbled upon this thread earlier this morning while searching for a solution to what appears to be the same problem that "dogunter" is experiencing. i have a stock 4.0.2 verizon galaxy nexus that i purchased through eBay a few months back. it was listed as brand new but when it arrived it had already been unlocked. from what ive gathered thus far, im assuming that the seller not only unlocked it, but also modified a system file(s), as i am getting the "android on its back with a red triangle" whenever i attempt to update to 4.0.4 via OTA push.
what steps should i take in order to correctly install 4.0.4? i see that "jonnyg1097" claims he "flashed the stock image from Google to 4.0.4 and I was able to get the 4.0.4 OTA no problem and I didnt see the android guy on his back at all during the process. " how would i go about doing this, and is this the best/only method to install the update? thanks in advance!
galaxy_sexus said:
first time poster here. stumbled upon this thread earlier this morning while searching for a solution to what appears to be the same problem that "dogunter" is experiencing. i have a stock 4.0.2 verizon galaxy nexus that i purchased through eBay a few months back. it was listed as brand new but when it arrived it had already been unlocked. from what ive gathered thus far, im assuming that the seller not only unlocked it, but also modified a system file(s), as i am getting the "android on its back with a red triangle" whenever i attempt to update to 4.0.4 via OTA push.
what steps should i take in order to correctly install 4.0.4? i see that "jonnyg1097" claims he "flashed the stock image from Google to 4.0.4 and I was able to get the 4.0.4 OTA no problem and I didnt see the android guy on his back at all during the process. " how would i go about doing this, and is this the best/only method to install the update? thanks in advance!
Click to expand...
Click to collapse
I would follow the instructions here, which takes you through the whole process set-by-step (make sure you do the optional steps in part D). That way you can be certain that you are fully stock. (Leave the bootloader unlocked.) Once you do that, then you can have a look here for how to use the OTA update file to update.
hmm
thanks for that, efrant. im currently in the process of getting it back to stock so i can receive the 4.0.4 OTA update. i am, however, running into a slight issue. in step D, number 2, you say to unlock the bootloader by typing "fastboot oem unlock". upon doing that, the cmd prompt gives me "...FAILED <remote: Already Unlocked>" i suspected it would say that as my phone was already unlocked by the seller. however, im not getting the prompt on my nexus about the device being wiped...do you know why that is and what i need to to in order to continue?
...by the way, a blue line of text appeared at the bottom of the phone's screen that reads "FASTBOOT STATUS - FAILALready Unlocked".
again, thanks in advance for all of the help.
galaxy_sexus said:
thanks for that, efrant. im currently in the process of getting it back to stock so i can receive the 4.0.4 OTA update. i am, however, running into a slight issue. in step D, number 2, you say to unlock the bootloader by typing "fastboot oem unlock". upon doing that, the cmd prompt gives me "...FAILED <remote: Already Unlocked>" i suspected it would say that as my phone was already unlocked by the seller. however, im not getting the prompt on my nexus about the device being wiped...do you know why that is and what i need to to in order to continue?
...by the way, a blue line of text appeared at the bottom of the phone's screen that reads "FASTBOOT STATUS - FAILALready Unlocked".
again, thanks in advance for all of the help.
Click to expand...
Click to collapse
You are good to proceed. You won't get the wipe prompt if your bootloader is already unlocked. No worries, just keep going with the steps.
Sent from my Galaxy Nexus using Tapatalk 2
thanks
thanks for the quick responses! you are quite helpful. everything appeared to install successfully, but upon the first reboot after finishing, im unable to get any service! it reads "Searching for service...", sits there for about 2 minutes, then tells me it cannot find service and thus cant activate. i skipped instead of restarting, and checked the settings to see if anything looked suspicious. im seeing that under "Baseband version" it says "Unknown". did i screw something up?!
sorry to keep troubling you with such noobish problems, but although im an experienced PC user im fairly new to smartphones and android. please have mercy on me.
galaxy_sexus said:
thanks for the quick responses! you are quite helpful. everything appeared to install successfully, but upon the first reboot after finishing, im unable to get any service! it reads "Searching for service...", sits there for about 2 minutes, then tells me it cannot find service and thus cant activate. i skipped instead of restarting, and checked the settings to see if anything looked suspicious. im seeing that under "Baseband version" it says "Unknown". did i screw something up?!
sorry to keep troubling you with such noobish problems, but although im an experienced PC user im fairly new to smartphones and android. please have mercy on me.
Click to expand...
Click to collapse
The first thing i would do is reboot. If that doesn't work, then I would just flash the images one more time. (Just in case one of them messed up.) Make sure both radios flash successfully.
Sent from my Galaxy Nexus using Tapatalk 2
got it
figured it out! when i did the cmda radio install i accidentally typed "fastboot flash radio" instead of "fastboot flash radio-cdma". doh! worked perfectly the second time around. thanks again, man. youve been a fantastic help.
galaxy_sexus said:
figured it out! when i did the cmda radio install i accidentally typed "fastboot flash radio" instead of "fastboot flash radio-cdma". doh! worked perfectly the second time around. thanks again, man. youve been a fantastic help.
Click to expand...
Click to collapse
useful thread
So folks.
Just reached home with my new phone, an Xperia Arc S LT18a, I believe.
I'm stuck with this firmware 4.0.2.A.0.62 which doesn't seem to have an easy way to get a custom ROM on it yet. Sucks that I didn't read about this before heading out to buy a phone.
I went through one of the guides here and had the bootloader unlocked via Sony's website. However, the rooting instructions didn't work. So searched further and realised the issue.
I've seen people say that they've done it by downgrading to a lower firmware, rooting it and then upgrading the firmware OTA again. Then I read that upgrading firmware OTA with an unlocked bootloader will brick my phone. So I'm not trying that.
Any help on how I could go about this? Simple step by step instructions would be very welcomed, since I don't really know much about flashing various bootloaders and ROMs considering I just bought the phone.
Thanks for reading!
there are many threads relating to this problem....plz read & search before posting....
Well i believe the answer to your questions lie in this Thread ...
'
Hope i was helpful ....
Flash the zip I attached to this post through CWM. That's it, you're rooted
Thanks!
I used the above zip file, but from a different thread and got it working. Cheers to both of you!
RamEsRock said:
Flash the zip I attached to this post through CWM. That's it, you're rooted
Click to expand...
Click to collapse
How can I have CWM on my phone? If I will flash phone I will do it with rooted ROM not stock. For me it's closed circle because I need root'ed device to load CWM on it, and I need CWM to make root.
Can someone explain me it?
szaebb said:
How can I have CWM on my phone? If I will flash phone I will do it with rooted ROM not stock. For me it's closed circle because I need root'ed device to load CWM on it, and I need CWM to make root.
Can someone explain me it?
Click to expand...
Click to collapse
With unlocked bootloader, one can easily flash a custom kernel with CWM, then flash the zip file.
Try reading this http://forum.xda-developers.com/showthread.php?t=1304634
jason statham said:
So folks.
Just reached home with my new phone, an Xperia Arc S LT18a, I believe.
I'm stuck with this firmware 4.0.2.A.0.62 which doesn't seem to have an easy way to get a custom ROM on it yet. Sucks that I didn't read about this before heading out to buy a phone.
I went through one of the guides here and had the bootloader unlocked via Sony's website. However, the rooting instructions didn't work. So searched further and realised the issue.
I've seen people say that they've done it by downgrading to a lower firmware, rooting it and then upgrading the firmware OTA again. Then I read that upgrading firmware OTA with an unlocked bootloader will brick my phone. So I'm not trying that.
Any help on how I could go about this? Simple step by step instructions would be very welcomed, since I don't really know much about flashing various bootloaders and ROMs considering I just bought the phone.
Thanks for reading!
Click to expand...
Click to collapse
I when I rooted my locked bootloader ARC S, I read "The Nutshell Arc Guide" at http://forum.xda-developers.com/showthread.php?t=1304634
Before you start messing with the phone, please see the entire guide first.
Hope I can helped.
Cheers
My buddy gave me his soft-bricked Sony z1c, and I'm having a really hard time figuring out exactly what to do to fix it. I'm sure I sound like an idiot, but I'm just feeling very confused here about what instructions are relevant to me. I've spent several hours trying to figure it out from several threads. This general Xperia recovery thread and This stickied Z1c thread, felt pretty helpful, but they weren't idiot-proof enough for me.
I'm just desperate for some straightforward, idiot-proof instructions for my situation
Phone Details:
At the time of the bricking, It had Sony's installed kitkat ROM.
It boots up to the sony screen and then goes dark again. Or will sometimes show the battery charging screen. (Apparently a textbook "soft brick?" )
It IS rooted, but i don't know if it had supersu or superuser.
I don't know if the bootloader was unlocked, but it wasn't bought from a carrier, so it might be. I'm pretty sure the bootloader IS unlocked, but am unsure. (this lack of information is probably the biggest source uncertainty and anxiety)
So far I've:
Downloaded, installed Flashtool. Haven't downloaded the suggested Firmware through it yet, because it's a pretty big download.
I did download the CandyRoms Kitkat zip as linked here, because I would like to keep Kitkat.
Main Questions: (for now)
Can I figure out whether the bootloader is unlocked before jumping into the instructions i'm going to commit to following? If the Bootloader is unlocked, that means I can follow the more straightforward instructions from the z1c specific thread mentioned above (but that thread still does leave me feeling iffy).
If I can't figure it out before jumping in, and it turns out that the bootloader is locked, will it damage things if I followed instructions as if it were unlocked? I'm like 85% certain it's unlocked but... I've read horror stories about other phones like Galaxies, and I'm paranoid.
If I install the firmware using the xperifirm tool in flashtool, will that upgrade me to Lolipop or higher? Can/should I use Flashtool to just straight up install the CandyRoms ROM? Do I even need to flash new firmware?
What exactly do they mean when they say "boot into recovery"?
Thanks for you help, and forgive me for any faults with this thread.
Leostaley said:
My buddy gave me his soft-bricked Sony z1c, and I'm having a really hard time figuring out exactly what to do to fix it. I'm sure I sound like an idiot, but I'm just feeling very confused here about what instructions are relevant to me. I've spent several hours trying to figure it out from several threads. This general Xperia recovery thread and This stickied Z1c thread, felt pretty helpful, but they weren't idiot-proof enough for me.
I'm just desperate for some straightforward, idiot-proof instructions for my situation
Phone Details:
At the time of the bricking, It had Sony's installed kitkat ROM.
It boots up to the sony screen and then goes dark again. Or will sometimes show the battery charging screen. (Apparently a textbook "soft brick?" )
It IS rooted, but i don't know if it had supersu or superuser.
I don't know if the bootloader was unlocked, but it wasn't bought from a carrier, so it might be. I'm pretty sure the bootloader IS unlocked, but am unsure. (this lack of information is probably the biggest source uncertainty and anxiety)
So far I've:
Downloaded, installed Flashtool. Haven't downloaded the suggested Firmware through it yet, because it's a pretty big download.
I did download the CandyRoms Kitkat zip as linked here, because I would like to keep Kitkat.
Main Questions: (for now)
Can I figure out whether the bootloader is unlocked before jumping into the instructions i'm going to commit to following? If the Bootloader is unlocked, that means I can follow the more straightforward instructions from the z1c specific thread mentioned above (but that thread still does leave me feeling iffy).
If I can't figure it out before jumping in, and it turns out that the bootloader is locked, will it damage things if I followed instructions as if it were unlocked? I'm like 85% certain it's unlocked but... I've read horror stories about other phones like Galaxies, and I'm paranoid.
If I install the firmware using the xperifirm tool in flashtool, will that upgrade me to Lolipop or higher? Can/should I use Flashtool to just straight up install the CandyRoms ROM? Do I even need to flash new firmware?
What exactly do they mean when they say "boot into recovery"?
Thanks for you help, and forgive me for any faults with this thread.
Click to expand...
Click to collapse
When you boot, do you see a colored led light flash on the ttop of the phone? If so, press volume up or down buttons when you see it, and you might get into recovery. Besides that, your best bet is definitely Flashtool. If you don't want Lollipop, download a KK ftf file. There's one here - https://forum.xda-developers.com/so...f-xperia-z1-compact-d5503-14-4-0-157-t3118047. Once that's fflashed, you can move on to rooting, etc