Develop Bugs

root error - aborted. now arc won't start anymore, nor flash. help me plz

I was trying to root my xperia arc.
i started flashtool, everything went alright. then error -aborted.
now phone can't start anymore, I can't do anything with it.
plz help me

You have to tell a little more to get the right help.
Bootloader locker or unlocked?
What firmware did you use when rooting the device?
What did you use to root, Gingerbreak?

i'm sorry
bootloader locked, never touched that
i never touched anything. I'm on 2.3.3, so I was trying to get back to rootable version.
its when i was trying to flash it to previous version that flashtool aborted. saying : power on go to settings and turn on ressources and debugging.
but i can't do anything with. It doesn't even start up.
thx

no prob, can imagine you're upset
did you try to flash it again?
How was your battery when starting in the first place?
Did you try to start up with power cable plugged in?

wow i just tried sony ericsson update service, and now the phone seems to start up.
the mistake i did i think is that i forgot to reinstall the sd card before starting to flash it.
as i'm writing this the phone is correctly working. so now was the sd card remove the mistake ?

1st option
I would say unlock the bootloader and reflash with the newest firmware, or you could just try this
2nd option
http://forum.xda-developers.com/showthread.php?t=1126358
I had the same problem (but my boot loader was unlocked) and it sorted it out, I thought it was just flashtool but it isnt theres special files in the firmware folder that unbrick the arc, let us know how you get on. try the 2nd option first
If its working now then it was a semi brick, option 2 fixes them no problem, try reflashing if you get the same problem just use the 2nd option afterwards and it will work fine

@grat_master
dunno bout the sd card, but glad SEUS did the trick for you.
@yusuo
can you unlock your bootloader when the device won't even start?
anyways, things worked out, no need to do more i think

ok so now the phone is working correctly.
but i tried it a second time to flash with flashtool, and it did the same thing. flash aborted, power on go to settings and turn on ressources and debugging.
what am i doing wrong ? i'm following namaste guide http://forum.xda-developers.com/showthread.php?t=1133650
but it just doesn't work.

yes you can, you put it in fast boot mode (turn phone off, then hold back button and plug usb in while still holding back button)
If is still doesnt turn on after use the brick fix (option 2)

Seemingly others have had problems too..
Common reasons:
http://forum.xda-developers.com/showthread.php?t=1162492&page=2
And try running flashtool as administrator and make sure you have the lt15.sin in loaders directory..
Unlocking bootloader is good if you want to install a custom ROM.. But u void your warranty and loose DRM (If you care bout those that is..)

LT15.sin is already in loader directory
and I'm also running it as admin, I also disabled user control.

Which firmware are you trying to flash, the UK or HK version? Maybe it's a corrupt file?
Sent from my LT15i using xda premium

i live in canada, and i'm using a rogers branded phone, samething as in the video of namaste guide.
i am trying to flash north america generic and world generic, neither worked.

Have you tried removing the battery after flashing, and then putting it back and then boot up?
Sent from my LT15i

it can't flash !
i am not able to flash anything, it stops before end and the phone remains in flash mode even if I deconnect usb cable. I can connect it back to pc without pressing back button and the green light is on again. that's after the flashing crash.
now the phone is ok, I can go internet, receive give calls, but I still have my sms problem that I have since beginning. I'm sending it back again to sony for repairs. HAHA I received it from repairs yesterday, and I got exactly same problem as before. I hope they change it. I think my phone is broken /end of story. Broken from beginning.
Anyway, I'm heading back to my Rogers detailer now to see what they can do again.
Thx for help. I'll try to root again when I get it back.

Okay, good luck, hope you get a replacement!

my service provider Rogers Canada is sending me a new Xperia Arc, should receive it in 3-4 days. As soon as I receive it, I'm gonna try root.
I'll let you know if it's working or not.

ok so i received my new xperia arc. now my sms problems are solved ! hourra
but i still can't flash it to root. It just don't want to do it.
what am I doing wrong ? I'll try a new ftf file. Can it be related to a bad sd card ?

Flashed System Partition with Boot Image - Help I'm Stupid

I would be so greatful if someone could help me, I think I have really messed up.
Coles Notes: I flashed the 4.0.4 image to my System partition which I am pretty sure should have gone to the boot partition now... Holy **** I'm dumb.
Anyways now my phone is just stuck saying Google. Anyone who can point me in the right direction of even a System image I can flash over top I would be so greatful.

Ok. I'm a dumb newbie, but what happens if you pull the battery, put it back in, then hold down the Up/Down buttons and turn the phone on?

Moleculor said:
Ok. I'm a dumb newbie, but what happens if you pull the battery, put it back in, then hold down the Up/Down buttons and turn the phone on?
Click to expand...
Click to collapse
Not a dumb newbie, checking if bootloader still works is a good idea
@OP: If you can get in the bootloader, your best bet would be unlocking, installing CWM and then flash a ROM through it.
You can also flash the stock ROM via the GNex toolkit.
Just read the guides and information here in the forums, it seems confusing at first but is really simple once you get used to it.
Good luck!

Thank-you for your quick response. I have CWM installed and can get into the bootloader. the problem now seems to be I cant get the device to show up in windows I always get <waiting for device> when going to flash it. Any ideas? I have been searching the forums trying to find an answer but nothing so far seems to have worked.

Another dumb newbie thing, but when you plug the phone in to the USB port on your computer, does your computer show the phone as having connected (ala the ADB driver in your Device Manager in Windows)?
If not, double check to make sure your ADB drivers are installed. I doubt they aren't, seeing as how you were flashing stuff earlier (from your computer, right?), but it's a wild guess anyway.

Thanks to everyone for the advise. Yes I could see the drivers and they were working perfectly according to device manager. However I guess it was stuck outside of debug mode?
Anyways from the boot menu the program was able to detect it, flash 4.0.4 to the phone, and then I was able to install the canadian radio without issue (hence the reason why I did this in the first place, we are stuck on yakjuux with 4.0.1).
Thanks again to everyone, great learning experience.

Sure thing!
Glad it worked
As a future reference, the "Boot Menu" is actually where you need to be for flashing via PC. The commands won't come through if you're in recovery.
Make sure to make an Android right now!
You enter CWM Recovery, go to backup and restore and then hit backup.
In case your phone ever messes up while you're not close to a computer, you can just boot into CWM and hit "restore", it's as easy as that.
I always have 2 recoveries on my phone just in case.

[Q] Need help / Advice possible Brick :D

So, hey guys, i've used this site a lot in the past, but now i need some help / advice, so i've registered. The following isn't going to be pretty but i'll explain it as best as i can.... infact, i can paste the email i sent to Sony asking for advice, it was this morning, i don't know if they operate or care
Hello people at Sony, my stupid head appears to have bricked my Xperia Arc S Android phone, it was still under warranty until i decided to unlock the bootloader, then i was having trouble restoring it back to stock android, this resulted in me trying to lock the bootloader. But alas, nothing now happens except a lonely green light flashing every so often, if i hold down menu, a blue light appears, which is charming, but then it dissipates and im left lonely again. With just a bricked phone and little dignity.
What are my options, by rules, it's void of warranty, can it be fixed? Can i pay for it to be fixed? Will my Natwest Insurance cover it on the grounds of Accidental damage (My stupidity) and Breakdown due to electrical fault, that being, no electrical softwareness is been transitorized.
I decided to go custom due to the wait for the Xperia update for my phone, out of the 273 S-I variant versions of the Arc S, 246 have gotten the update, but not mine, months had gone by, day turned to night, night turned to day, and i got desperate, i decided to root... for the first time. (And now last)
What i did learn, apart from technology will rise up and defeat us all, is JellyBean works very well to some degree on this phone, HOWEVER, the lack of Flash player caused bad results when playing content, im not sure what piece of code on the JellyBean CM10/Paranoid Android release was rendering it, but if you can get past the lack of flash for this and render images in its mobile bravia engineness then it will work a treat, and i mean it, it really did run well, obviously it was customness, but i digress...
Can anything be done? I do so love my Arc S, and just so you know, if it can't be repaired and I have to change phones, it will still wear the brand logo... Sony Ericsson... and if its your newer phones, that lack Eric's Son, i shall scribe his name proudly across the top with a sharp implement with pride. (With the care of an Adult, or someone equally minded)
Thank you lovely people over at Sony.
Stuart Herrington
Click to expand...
Click to collapse
So, basically it doesnt boot, apart from it does vibrate with button holds and the LED flashes. I tried flashing it with flashtool and stock ROM, but flashtool came back saying it needed unknown sources and debugging mode activated, which makes me think, it could be salvagable and not bricked, however how can i change those settings if i can't get into the phone itself, is there a bypass?
On a side note, i can Hold Menu, plug the phone into my computer and it goes into blue light mode, i cant remember the term for this
but its what i was using for flashboot, you reckon i could flashboot out of this? I was trying so many different methods to try and custom rom my phone that everything got confusing, which was best to use etc, and on another note the phone never booted when i tried to relock it, so im unaware if it finished, it didnt boot at all, and this is the point im at now.
Fortunately i picked up a Xperia U for £135, second hand, actually cheaper than my Arc S second hand, crazy really, but you can see why with the size difference and a couple of small spec differences.
Any help would be appreciated. This isn't obviously the best situation but i'm wondering if anyone has encountered this stupid mistake i've cast upon myself XD
Thanks in advance.

Wait...
I've checked the fastboot status of my phone using Flashtools, and it says my phone needs to be rooted first... hmmm it was rooted, maybe it got undone with the bootloader thing, i guess i can try but i can't access the phone to debugg or allow unknown sources.

Hi Stu15,
The fact that you can boot holding down the menu button is good.
You can probably flash a custom kernel onto your phone this way using the following command.
Code:
fastboot flash boot boot.img
If you have a rom that you want to use, then it usually comes with a custom kernel (called boot.img most of the time) inside the rom's zip file.
Most custom kernels have CWM recovery built-in, and here's the trick to enter recovery -
After you turn on the phone, wait for the hardware keys to light up.
Just in case you miss this, the coloured led will light up purple at the same time
When this happens, press (and release) the "volume down" button once or twice.
Then you should see CWM recovery in a few seconds.
So what you do is copy the rom to your sd card (just plug the card into your computer to do this).
Then flash the custom kernel that came with the rom.
Then boot into CWM and flash the rom (you should clear the cache and the dalvik cache before flashing the rom).
If you don't have a preferred rom, then have a look at this thread - http://forum.xda-developers.com/showthread.php?t=1653188
It has lotd of helpful links, near the bottom of the 1st post are a few roms you can try.
I hope that you come right.
Take care,
Hotfingers

Thanks for the info, ive tried this and apparently my phone isnt rooted anymore, it must've locked itself why i tried to undo the rom install, my recovery wasnt working so i was left with little choice. I can try and root the phone but i dont think it will be possible without accessing debugging mode, which is in the phone.. doh
im going to try adb commands to try and work something, then insurance claim. woop :/ lol
[EDIT] IM BACK, im in lol, i managed to find the command to unlock the bootloader, so now im back into CWM, the problem is the recovery doesnt work, so im reinstalling the original package, go into the phone, usb debugging and unknown sources, then i will flash it with stock ROM, should work. best work, i dont know why i did this in the first place... guess i had to learn XD

stu15 said:
Thanks for the info, ive tried this and apparently my phone isnt rooted anymore, it must've locked itself why i tried to undo the rom install, my recovery wasnt working so i was left with little choice. I can try and root the phone but i dont think it will be possible without accessing debugging mode, which is in the phone.. doh
im going to try adb commands to try and work something, then insurance claim. woop :/ lol
[EDIT] IM BACK, im in lol, i managed to find the command to unlock the bootloader, so now im back into CWM, the problem is the recovery doesnt work, so im reinstalling the original package, go into the phone, usb debugging and unknown sources, then i will flash it with stock ROM, should work. best work, i dont know why i did this in the first place... guess i had to learn XD
Click to expand...
Click to collapse
cool, well done. :good:

[Q] Stuck at Unlock Bootloader screen

My soft brick Verizon gnex is giving me a bit of trouble. It was stock, locked, and all those other things that you all probably frown upon, but worked fine for me and I had not reason to change this. It got stuck in a boot loop and a hard reset and wipe didn't do anything. I found efrant's guide and got everything set up. fastboot devices results in a correct read of my device and I can run fastboot reboot-bootloader, which I did as a check to make sure computer to phone commands were working fine.
The problem is that when I run fastboot oem unlock, I get the unlock bootloader?, can scroll to "Yes" and then my phone gets stuck there...indefinitely. I've let it go for up to two hours and don't get anywhere. If I terminate with a battery pull/ unplug, I get a "too many links" error. Running wug's toolkit does the same thing. Rebooting into fastboot works, but the phone is still locked. If I select "No" on the unlock screen, I get the Google splash forever. Any suggestions?

i hate to ask this question... but...
when you scrolled to yes, did you press the power button to accept the selection?

Zepius said:
i hate to ask this question... but...
when you scrolled to yes, did you press the power button to accept the selection?
Click to expand...
Click to collapse
I wish the solution were that easy (though if I were that stupid....yikes). I did hit the power button and cannot scroll to No. The device is really just stuck there. My cmd prompt is just hanging (...) too. I suppose it could be that the communication is only going one way (computer to phone) but somehow isn't going phone-to-computer. I've tried different drivers/cords/USB ports, but (right now) don't have another computer that I can play around on.
I may give it one last driver reinstall try, but it's looking like Odin is the way to go?

molgator24 said:
My soft brick Verizon gnex is giving me a bit of trouble. It was stock, locked, and all those other things that you all probably frown upon, but worked fine for me and I had not reason to change this. It got stuck in a boot loop and a hard reset and wipe didn't do anything. I found efrant's guide and got everything set up. fastboot devices results in a correct read of my device and I can run fastboot reboot-bootloader, which I did as a check to make sure computer to phone commands were working fine.
The problem is that when I run fastboot oem unlock, I get the unlock bootloader?, can scroll to "Yes" and then my phone gets stuck there...indefinitely. I've let it go for up to two hours and don't get anywhere. If I terminate with a battery pull/ unplug, I get a "too many links" error. Running wug's toolkit does the same thing. Rebooting into fastboot works, but the phone is still locked. If I select "No" on the unlock screen, I get the Google splash forever. Any suggestions?
Click to expand...
Click to collapse
I aint a grave digger , I can see the post date but Have you found Solution yet ?? I am myself stuck there ?

herecomesmaggi said:
I aint a grave digger , I can see the post date but Have you found Solution yet ?? I am myself stuck there ?
Click to expand...
Click to collapse
No dice. Samsung offered to let me send it back, but I never got around to it. If you send yours in and/or figure it out, let me know and I may turn my current paperweight into something usable. Best of luck, and sorry I don't have more to offer!

OK thanks for clearing that out. I have tried everything, it seems that memory is corrupted and that's why bootloader can't format it and is stuck at unlocking... I will update if I found anything.
Avoid Spells!!! "Auto correct : ON"

[Q] Will warranty service knows if my device is rooted and unlocked?

Hi guys! I want to send my Nexus 7 (2013) to warranty service because it's bricked and I think the motherboard is destroyed. Will the service understand that the device is unlocked (bootloader) and rooted?

I could be wrong so wait for confirmation from someone else but if it won't even power on I don't think they would know, however if it powers on as far as the white Google logo you can see it is unlocked by the white padlock that is opened at the bottom, or closed lock for locked boot loader.
Sounds like it won't power on though if the main board is dead so I doubt they could know...

If it helps i had an iphone 4 that i jailbroke and it ended up bricked. It wouldnt connect to the computer or anything else. I had the same worry you have and when it was sent off i thought theyd find out. They didnt, and i got a replacement. If it doesnt connect to a computer they just dismantle them for parts. A repair engineer is more expensive to employ than a few idiots with screw drivers.

May be I am wrong about the mainboard. Yeah, I can turn it on, but I can go only to boatloader. It can be connected to computer (only fastboot mode) and there is unlocked padlock.
I guess need to lock the bootloader. But the device does not see any space (free or used) - I was connected it to computer and used a recovery mode with Skipsoft application. May be the memory is dead. It shows that cannot mount any partition. I don't know. Is there any way to lock the bootloader?

I am guessing you used Wug's root toolkit to unlock. I have seen others relock there's when there has been problems similar to yours, maybe check his thread out and ask in there.

Yep, I used his toolkit. But I tried every button in the application but nothing worked. I'll try to search deeper. I'm so afraid because I bought the device 1 month ago.

ryderbg said:
Yep, I used his toolkit. But I tried every button in the application but nothing worked. I'll try to search deeper. I'm so afraid because I bought the device 1 month ago.
Click to expand...
Click to collapse
Yeah I know the feeling
I am always worried about devices failing but after I have had it for about a year I wont be so scared and will take more risks with it usually. Only had mine for around 2 weeks and am also worried it could go off at anytime as mine is unlocked and rooted. Lots of people seem to have had problems with this device, my Xperia S never had problems

ryderbg said:
Yep, I used his toolkit. But I tried every button in the application but nothing worked. I'll try to search deeper. I'm so afraid because I bought the device 1 month ago.
Click to expand...
Click to collapse
Try this... http://www.android.gs/restore-un-br...4-3-jelly-bean-twrp-and-root-guides-included/
It might at least get it locked for you....

Thank you! I will try that as soon as I go home...

This is pretty much what danvee posted but still..
If you can use fastboot that's a good sign. You probably don't even need to send it in. Try this: http://forum.xda-developers.com/showthread.php?t=2469508&highlight=stock
You say something about no space? If the above link doesn't get you running again try this first: http://forum.xda-developers.com/showthread.php?t=2380913 Worked for me.
You can just flash twrp with "fastboot flash recovery recoveryname.img"(without quotes), wipe, then use the steps in the first link.
If that doesn't work it probably is some kind of hardware problem.

I just locked the bootloader. I used the command fastboot oem lock and there is no padlock now. Also Lock state changed to locked. I think now I can return the tablet in the shop.

ryderbg said:
I just locked the bootloader. I used the command fastboot oem lock and there is no padlock now. Also Lock state changed to locked. I think now I can return the tablet in the shop.
Click to expand...
Click to collapse
heres a funny story but what it resulted in and how i fixed it seem to apply to the problem you have.
i have a cracked screen on my nexus and it was registering a touch at intermittent intervals making the device unusable. i posted in here about the same time you did for help. while i was waiting to see if anyone knew if i could just disconnect the screen and use a bluetooth mouse with a hdmi adapter (slimport not mhl, thanks meekrawb) i connected a usb mouse with an otg cable. the mouse worked but i couldnt see how to turn off touch screen as an imput. as kitkat has been release and i hadnt updated i thought i would give it a try and see if that would reset the screen and stop the touch. It downloaded the update and when it rebooted it opened up a mod recovery screen (i forgot that i had rooted it). it asked me to slide a bar on the bootloader screen to continue. The usb mouse cursor was not present on this screen and the touch screen doesnt work so i couldnt get past it. i turned the device off and on again (what else do you do when your stuck) and it would open the google screen with the unlocked padlock but then just stay on a completely black screen. same as yours. I connected it to the computer and it recognised it. i opened wugfresh's root tool kit (old apple jb's sometimes had recovery abilities built into them so i thought this may aswell) i clicked on flash stock and unroot with the radial button on soft bricked and followed the instructions. now my device is unbricked and even the touch has stopped. Happy days hey. you'll need to unlock your boot loader again but its worth a try before going to the store, you can always lock the bootloader again if it doesnt work.
i know it didnt need all this to say "connect it to the root tool kit and try that" but i thought you would enjoy a laugh

Funny story. But my issue is hardware. The device doesn't show any space in it. No free nor used. I think the memory is dead. Also I relocked the bootloader, but now I cannot unlock it again because there is no space
Now when the tablet is with locked bootloader, it is unrooted, right?
Tommorow I will visit the warranty service and hope they don't understand about rooting and unlocking.

according to an email from "google play support India" , the device will be accepted under warranty as long as it has a stock firmware installed when you send in the device to claim the warranty.