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:
Related
my verizon xperia is not recognized by either pc companion or seus. I am trying to do a hard reset due to the fact the lockscreen doesnt work. I have read that I can press and hold the back and search keys on front while powering on to factory reset the phone, however that does not seem to be the case. Can anyone give me some suggestions if the two button factory reset does work and that maybe I am just doing it wrong. And any suggestions as to how to get my phone to connect with seus so I can reset if teh 2 button trick is indeed not an option. Thank you to all in advance.
Doesnt anyone have an idea? I follow seus instructions. Power off wait 30 seconds, then plug in the usb cord to the pc, then press and hold the back button then inserting the usb cable into the phone... and then I wait for it to connect which it doesnt.
have you tried removing the battery wait a bit and put it back and then try again. I had something similar happen when I first got mine.
yes.... I waited beyond the 30 seconds it suggests. I eve waited about 2 hours once. Still nothing......I really want to get this device working.....it does power up. Everything seems like its supposed to work but it isn't. Thank you for helping me... I really really appreciate it.
hey, if youre comfortable, we can unlock the bootloader on it. if we do that, then you can just use fastboot and the files you can get off of my State of Development thread to return you back to stock. You could also root it. If that interests you, send me a pm with your ESN and Ill get you an unlock code.
Or do you still wanna try to figure out the **** fest that is SEUS?
I would love to unlock the bootloader. I have always had motorola android phones so even though i have never unlocked the bootloader I would love to.
Where would I find the ESN #? I am not able to get past the lock screen....so all I can do it make emergency calls
I have PM'd you my phones info. Thank you for your assistance
What is preventing you from passing the lock screen exactly? Programming?
the phone says that the pattern lock attempts has been exceeded... and the only way to unlock is to enter either a gmail info or answer the question. Neither of which I know.
Ahh! phew i thought it was more serious than that. Were you able to have the phone activated on your Verizon account okay? The esn wasnt blacklisted or anything?
And the funny thing is, even if you HAD got seus working, it would not have fixed that problem. SUES doesnt wipe the device as far as I know.
the *#06# in the emergency dialer doesnt show anything?
also the MEID is under the battery.
I have not activated the phone as I cant really use it in its current state. I did check with Verizon and the phone can be activated no problems.
I do have the MEID #, is it safe to list it here?
Also, the phone does not take the #* code, says its not an emergency number
K, i have successfully unlocked my bootloader on my phone..... I am trying to make sense of what to do next
YAY!!!!!. I unplugged and rebooted the phone after unlocking the bootloader and now my phone is back... I can sign into google now
you should use this command and reflash the stock system
fastboot flash system system.sin -w
this will erase usersettings and reinstall the stock rom.
make sure you have the rom downloaded.
edit- Never mind.
jgregoryj1 said:
YAY!!!!!. I unplugged and rebooted the phone after unlocking the bootloader and now my phone is back... I can sign into google now
Click to expand...
Click to collapse
Thats great! totally forgot that actually unlocking the bootloader performs a factory reset. So awesome! Go get you some root!
now that I have it restored, the screens touch sensitivity is all over, it keeps thinking I am trying to load up voice commands. I would like to flash a rooted ROM, and from what I have read on kernals for the r800x theres nothing worth flashing just yet. Can anyone point me in the right direction on how to flash a rooted stock rom?
Also, I am still not able to enter Flash mode with the whole back button while inserting usb cable. the light is still blue.... any suggestions?
You shouls be holding the search key.
sent from the original unlocked R800X.
i will try the search button instead. Also I flashed a kernal and now the phone is super slow. How do I flash the stock ROM and stock kernal. I am doing some reading but I am still lost. seems like I get routed to xperia arc pages...... can anyone give me some guidance. sorry to be a pain, but I am excited to learn
jgregoryj1 said:
i will try the search button instead. Also I flashed a kernal and now the phone is super slow. How do I flash the stock ROM and stock kernal. I am doing some reading but I am still lost. seems like I get routed to xperia arc pages...... can anyone give me some guidance. sorry to be a pain, but I am excited to learn
Click to expand...
Click to collapse
Hey, everything you need to know is in the many pages (and the initial post which is constantly updated) on my State of Development thread. Read through there and you will see that everyone else is also having problems with the kernels and roms making the phone unresponsively slow. The first post also has links for stock files that you might need.
Basically if you get your phone into fastboot mode (turn off, hold search key, plug in USB line, solid blue light turns on) you can do two commands to get you back to stock, and then follow the rooting instructions that I have on the R800x Rooting thread. Its linked in the state of development thread. Second item, i believe, below the link to Bin4rys.
The two commands would be "fastboot flash system system.sin" and "fastboot flash boot kernel.sin". the first command might not be necessary even, just the kernel one might fix you.
Alright. For starters, xda has been VERY VERY helpful to me over the past few months and I thank everyone who has ever contributed to a question or a discussion I have read. That being said, this is my first post. I watched the newb video, read many forums (both xda and others), google searched, read some more threads, kept reading threads, tried some methods described in some threads, bookmarked some interesting threads for if my phone ever works again, and read some more threads.
I am not saying the answer is not already out there, I am saying I have reached my resourcefulness cap.
Anyway, to the root of the problem: I'm not entirely new to rooting, and am comfortable using recovery and hboot to flash roms. I also had a nandroid backup! for SOME SILLY reason, while in my clockworkmod recovery this morning (maybe slightly due to being half asleep which is why I now recommend being fully awake before entering hboot or recovery or rom manager....etc) I formatted the system on my phone. I THINK.
My phone will now load up to display the bootloader, and go into recovery mode, and flash roms, but when I flash a rom, nothing changes. If I boot my phone up, it will show a notification bar at the top like usual, a stock wallpaper, and that is IT! it will show a message notification and missed call icon since I have them, but the touch screen will not work. The rosie buttons at the bottom do not show up (i.e. phone button or all aps button) no apps appear, no clocks except for in the notification bar... hardkeys have no effect (home button search button menu or back) and volume keys will not work. The lock button will only lock and unlock the screen, not power off or reboot or anything. If plugged in at this point, it is charger only.
So, I can take the micro sd card out and put files on it from my PC via a microsd-usb converter thing...
I have tried putting new roms on the sd and flashing them from recovery, no effect. Tried the RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe program, it always says that my phone has below 30% battery and will not continue (this is not the case as I have two batteries both have been fully charged because the phone will still charge them...)
And I have tried putting PC36IMG.zip files on my sd card to no avail.
I am thinking that the system was wiped because it seems like there is no boot image on the phones internal memory itself. I am currently looking for a way to place a boot image on the sd card to possibly flash it or some sort of update.zip so that my bootloader will ask me to update upon reading it.
Sorry for the long post, and ask any questions I will answer as best I can.
I am posting preemptively to the boot image adventure so that if it does not work, maybe I can have some help finding a solution by then.
I was going to take my evo to the sprint store since it is under warranty but if they go into recovery they will see clockworkmod recovery.
Thanks to all for any form of guidance!
I did just notice in my Bootloader menu (HBOOT-2.10.0001) that it says Supersonice evt2-3 **** S-ON
I don't know how because I thought it was a requirement that it says S-OFF to be rooted and flash roms, but I have definitely flashed roms before and gained su access to applications and such. BUT since it says S-ON would it then be covered by the warranty if it is not rooted?
Thanks again.
I you want to flash a boot image, you can take the boot.img from an RUU for the firmware you are, place it in your adb tools folder, then flash it using the commands:
fastboot flash boot boot.img
fastboot reboot
I'm not sure how to identify what firmware I am. Unless your talking about the Hboot version? and also, I can't place anything in any folder except onto my sd card. I have no access other than that to the phone. On the sd card there are no files except for what I put on there.
...aaand not to mention I don't know what adb is exactly...
Does your phone still go to clockwork when you go to recovery?
Am going to try it right now, but will that work if I cannot tell my phone to allow usb debugging? i remember something about unrevoked needing that to root the phone in the first place. will update as soon as I try it. May not have time right now as I have to leave in about 15 mins. If no reply by 9:45, then I will be back online tomorrow morning. and thanks!
Timeconsumer10 said:
Am going to try it right now, but will that work if I cannot tell my phone to allow usb debugging? i remember something about unrevoked needing that to root the phone in the first place. will update as soon as I try it. May not have time right now as I have to leave in about 15 mins. If no reply by 9:45, then I will be back online tomorrow morning. and thanks!
Click to expand...
Click to collapse
Welcome, but yes, you do need to have had usb debugging enabled, so we'll see how that goes.
SUPER THANKS! S-OFF tool worked perfectly just flashed a rom and now so far so good. Will post tomorrow to let you know if everything works well. So much appreciated =) I would thanks a million times if i could don't know what to do without my evo.
Timeconsumer10 said:
SUPER THANKS! S-OFF tool worked perfectly just flashed a rom and now so far so good. Will post tomorrow to let you know if everything works well. So much appreciated =) I would thanks a million times if i could don't know what to do without my evo.
Click to expand...
Click to collapse
Lol, it'd take you 200,000 days since you can only thank 5 times a day Though glad you're rooted now.
shortydoggg said:
Does your phone still go to clockwork when you go to recovery?
Click to expand...
Click to collapse
Yes it still goes to clockwork because its rooted.. now my screen legitimately does not work in certain areas of the screen (not responding to touch) so I'm going to try and get it stock stock stock unrooted and go for warranty replacement. Any ideas please let me know. Currently trying RUU Supersonic...
So, I got an ERROR [110] message from the RUU package its a file open error... :/ now i dont know what is up. Says I need a complete RUU package. Looking for another one or another option now.
If i boot phone normally now it just goes to a black screen with "htc" in the middle and "!" in a triangle in all four corners. Can't do anything from that screen.
If I boot into bootloader once where it says SHIP S-OFF at the top and instead of recovery and all those options it just says RUU but you cant do anything there... :/ I now, however cannot even get to the bootloader screen.
Could they tell it is rooted?
Maybe I could say I finally decided to do sprints OTA update that I've been denying for a while and this is the result.
Anyone agree disagree?
COCLUSION!
So. Since it has just the HTC logo and four error icons one in each corner... I took it into a sprint repair store. It would not boot into bootloader as a hard reset, so the guys at the store were stumped. They had actually never seen this before =). They asked me if I rooted it and all so I just played dumb. I told em I didn't know what that really was. They kinna explained it and I told em I didn't even have a computer (not a lie actually I sold mine and now use my dads or gfs lol). The logo on the screen was an oooold htc logo from like hero or so. So they just put it in the system as a wont even turn on type of thing and gave me a new phone since I was under warranty =) gonna see if I can live without root juuust for a little bit because work and school are gonna keep me busy for a while. I am certain to return though!
Can't wait to see what the devs can do by then!
Thanks to all for the help!
So today I was minding my own business, riding the subway and listening to some music when my Galaxy Nexus decides to reboot itself. After this, it gets into a reboot loop (never getting past the Google logo).
I tried restarting the phone into fastboot mode and using the recovery option, but I end up getting the icon of the android on its back, chest plate open and a red exclamation triangle thing coming out of it. I assume this is bad
A little back story... this is the GSM/Euro Galaxy Nexus. I've been using it for close to 6 months most likely and have never rooted/unlocked it. In actuality, I don't think I've ever done anything with it out of the ordinary (like I have in the past with other android devices). In fact, I don't know if I ever even plugged it into my PC via USB before (thus no drivers, may have never set it to USB debugging enabled).
Is there anything I can do here? I tried looking at a few options (Such as the WugFresh Galaxy Nexus Root Toolkit, which has a Stock resetting option), but since I never enabled USB debugging and installed drivers before the phone decided to go and brick itself, I don't know if I'm actually stuck...
What do you think? Is there an option I have not yet considered? Or am I going to try and convince Samsung to honor my warranty or something?
Moved to Q&A, please pay attention next time where you are opening a new discussion
When you see the android on its back you have to hold vol. up + power to enter the options.
There you can wipe data and reboot to see if it will boot up again.
If that doesn't work you can try flashing the stock images. Those will require you setting up fastboot on your computer. There are many guides on how to do all of that.
Good luck.
If you can get into Fastboot mode just fine, then hook it up to your computer and flash the stock images. It'll revert you back to stock fresh and you can go from there.
We also need to teach people how to debug at basic level at least. If we just teach them how to solve it without caring about what went wrong... they've got the phone might as well learn a few things more.
And yea, i know most couldn't care less. Also, this is no brick - this word very much starts to annoy me when it is incorrectly used and that seems to be getting typical around here. Most likely wiping data/factory reset from stock recovery will allow op to boot up again.
i had the same happening to me under stock. after quite some time it went into a bootloop out of the blue.
this:
bk201doesntexist said:
Most likely wiping data/factory reset from stock recovery will allow op to boot up again.
Click to expand...
Click to collapse
solved it. my data was gone, but at least the phone worked.
then i decided to root and use a custom rom and it never ever happened again.
bk201doesntexist said:
We also need to teach people how to debug at basic level at least. If we just teach them how to solve it without caring about what went wrong... they've got the phone might as well learn a few things more.
And yea, i know most couldn't care less. Also, this is no brick - this word very much starts to annoy me when it is incorrectly used and that seems to be getting typical around here. Most likely wiping data/factory reset from stock recovery will allow op to boot up again.
Click to expand...
Click to collapse
Sure we do but as long as :
1. people start threads that suggest they bricked their phone and
2. all they had to do is Google some around to discover that what they see is a stock recovery and
3. discover what they can do to solve their problems (like most of us do to solve our problems)
I think they couldn't care less about debugging... How sad as it may be.
If you discover problems with a device that is sold as much as the GN it is highly unlikely that you were the first to have that problem. If you are: just post away.
Long story short my friend gave me a T mobile HTC G2 because it didn't turn on. I opened the phone to find the part where the battery connects to the phone came off the mother board so i solder it back on put the phone back together and turned it on. It booted up normal and came to the lock screen nothing worked the touch wasn't responding so i push power button to turn screen off and then again to turn it back on and the screen worked. I tried guessing his pattern five time and it didnt work it asked me to sign in to my Google account when the screen came up the phone rebooted and it kept doing it every time i turned it on. So i looked on xda how to restore it tried it and im not sure if it restored or not but it strated boot looping. I tried the flashing the pc10img.zip from the root of the sd card it usually says something like version to new or to old or something it didn't work. My phone is not rooted and i don't think usb debugging is on. Any info you guys want just ask. What can i do? How can i fix it? Please help
I'm going to take a guess, that if the battery connection to the motherboard 'broke off', then it's possible you have other physical issues such as the ribbon cable connecting the screen/digitizer to the rest of the phone.
If it were me I would have sent the phone into HTC for hardware warranty (which you can't do now since you soldered it.).
Can you provide some specific information about the phone, can you get into the boot loader, and if so what exact information do you have there? (USB debugging would be easily turned on under system settings, if you can get into it via the screen).
kbeezie said:
I'm going to take a guess, that if the battery connection to the motherboard 'broke off', then it's possible you have other physical issues such as the ribbon cable connecting the screen/digitizer to the rest of the phone.
If it were me I would have sent the phone into HTC for hardware warranty (which you can't do now since you soldered it.).
Can you provide some specific information about the phone, can you get into the boot loader, and if so what exact information do you have there? (USB debugging would be easily turned on under system settings, if you can get into it via the screen).
Click to expand...
Click to collapse
Thanks for replying i don't think anything else is wrong with the phone all the cables were fine. To begin with warranty was already finished. "Yes", i can get into the boot loader/H boot. I can turn on usb debugging because the phone doesn't boot all the way in to android. When you say information what exactly are you looking for?
helstonrampersad said:
Thanks for replying i don't think anything else is wrong with the phone all the cables were fine. To begin with warranty was already finished. "Yes", i can get into the boot loader/H boot. I can turn on usb debugging because the phone doesn't boot all the way in to android. When you say information what exactly are you looking for?
Click to expand...
Click to collapse
Mainly the info that shows up on hboot, and which recovery you have (or 'had') so that might be able to advise some additional steps.
helstonrampersad said:
Long story short my friend gave me a T mobile HTC G2 because it didn't turn on. I opened the phone to find the part where the battery connects to the phone came off the mother board so i solder it back on put the phone back together and turned it on. It booted up normal and came to the lock screen nothing worked the touch wasn't responding so i push power button to turn screen off and then again to turn it back on and the screen worked. I tried guessing his pattern five time and it didnt work it asked me to sign in to my Google account when the screen came up the phone rebooted and it kept doing it every time i turned it on. So i looked on xda how to restore it tried it and im not sure if it restored or not but it strated boot looping. I tried the flashing the pc10img.zip from the root of the sd card it usually says something like version to new or to old or something it didn't work. My phone is not rooted and i don't think usb debugging is on. Any info you guys want just ask. What can i do? How can i fix it? Please help
Click to expand...
Click to collapse
when you first had the phone it won't boot right? but when you tried fixing the battery connection thingy (sorry I don't know whats it called )
it booted and ran again?
have you tried doing a factory reset?
Power button+volume rocker down (volume down button) to boot into bootloader mode then do a factory reset maybe that would work ?
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
OR
or sending the phone to HTC would help bud but you have to pay them for that if they get to fix it you got yourself a new toy!
kbeezie said:
Mainly the info that shows up on hboot, and which recovery you have (or 'had') so that might be able to advise some additional steps.
Click to expand...
Click to collapse
This is the boot loader screen that i see
VISION PVT SHIP S-ON
HBOOT-0.82.0000
MICROP-26.13.04.19_M
eMMC-boot
Apr 13 211, 14:51:54
Im pretty sure the phone was never rootded before
The Android Manual said:
when you first had the phone it won't boot right? but when you tried fixing the battery connection thingy (sorry I don't know whats it called )
it booted and ran again?
have you tried doing a factory reset?
Power button+volume rocker down (volume down button) to boot into bootloader mode then do a factory reset maybe that would work ?
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
OR
or sending the phone to HTC would help bud but you have to pay them for that if they get to fix it you got yourself a new toy!
Click to expand...
Click to collapse
Its ok im not certain of what its called either but just to be sure its the part where the battery touches and it has metal prongs like. As for trying to restore it, i already tried didnt work it boot loops when i try that.
I don;t know what to do
helstonrampersad said:
Its ok im not certain of what its called either but just to be sure its the part where the battery touches and it has metal prongs like. As for trying to restore it, i already tried didnt work it boot loops when i try that.
Click to expand...
Click to collapse
ryin
sorry bro I'm no dev so I don't know that much when you were tryin to flash the "stock rom" did you flash the one for the G2 or the Desire Z?
The Android Manual said:
ryin
sorry bro I'm no dev so I don't know that much when you were tryin to flash the "stock rom" did you flash the one for the G2 or the Desire Z?
Click to expand...
Click to collapse
I still appreciate your help bro and i was trying to flash the stock rom for the g2, i made sure of it.
helstonrampersad said:
I still appreciate your help bro and i was trying to flash the stock rom for the g2, i made sure of it.
Click to expand...
Click to collapse
Would probably have to stick to the original Stock RUU update since you're S-ON (would need S-OFF for any kind of custom recovery, kernel, unsigned packages, etc), so would have to use a signed full package from T-Mobile, I don't know much bout that because I usually have my phones rooted and away from stock as fast as I can.
What stock rom did you find before? links?
kbeezie said:
Would probably have to stick to the original Stock RUU update since you're S-ON (would need S-OFF for any kind of custom recovery, kernel, unsigned packages, etc), so would have to use a signed full package from T-Mobile, I don't know much bout that because I usually have my phones rooted and away from stock as fast as I can.
What stock rom did you find before? links?
Click to expand...
Click to collapse
http://shipped-roms.com/index.php?category=android&model=Vision
Thats is the above link i used and i used all the ones that start with "PC10" I rename them to PC10IMG.zip so the phone can recognize it and it did. The only problem is that after it tries to install is say something along the lines of version is older or newer since i tried multiple packages. One package was going through the process and after that it didn't do anything, it didnt say failed or reboot or anything like that. Ive been trying to fix this for like a week and a half now. Ive even flashed custom PC10IMG.zip to see if it could help but nothing the furthest ive gotten is the phone boots for like 2 seconds the screen is blurry and the shuts off and there is an orange light in top right that wasn't lighting up before. Here are the links for the custom packages
http://forum.xda-developers.com/showpost.php?p=10583834&postcount=33
http://forum.xda-developers.com/showpost.php?p=10966727&postcount=63
Cant thank you enough for helping me this is really frustrating
kbeezie said:
Would probably have to stick to the original Stock RUU update since you're S-ON (would need S-OFF for any kind of custom recovery, kernel, unsigned packages, etc), so would have to use a signed full package from T-Mobile, I don't know much bout that because I usually have my phones rooted and away from stock as fast as I can.
What stock rom did you find before? links?
Click to expand...
Click to collapse
If what i explained above is not what you were referring to then let me know your way
helstonrampersad said:
If what i explained above is not what you were referring to then let me know your way
Click to expand...
Click to collapse
You would have to much it to your exact carrier/phone, Just flashing whatever you get your hands on can be very very risky.
For example for me being on T-Mobile with a T-Mobile branded G2, I would grab PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from http://forum.xda-developers.com/showthread.php?t=971109
(noting the *.15 is the original radio my device was shipped with, though I've upgraded to the newer *.19)
I of course have no intention to returning to complete stock, but it's usually the only course of action for most people stuck with S-ON (and then would look into exploiting/unlocking/rooting again from there).
kbeezie said:
You would have to much it to your exact carrier/phone, Just flashing whatever you get your hands on can be very very risky.
For example for me being on T-Mobile with a T-Mobile branded G2, I would grab PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from http://forum.xda-developers.com/showthread.php?t=971109
(noting the *.15 is the original radio my device was shipped with, though I've upgraded to the newer *.19)
I of course have no intention to returning to complete stock, but it's usually the only course of action for most people stuck with S-ON (and then would look into exploiting/unlocking/rooting again from there).
Click to expand...
Click to collapse
I know it can be risky but im desperate for a fix. Ill try the package you linked. I download it and rename it to PC10IMG.zip? Ill get back after im done if you have any other suggestion please let me know.
kbeezie said:
You would have to much it to your exact carrier/phone, Just flashing whatever you get your hands on can be very very risky.
For example for me being on T-Mobile with a T-Mobile branded G2, I would grab PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from http://forum.xda-developers.com/showthread.php?t=971109
(noting the *.15 is the original radio my device was shipped with, though I've upgraded to the newer *.19)
I of course have no intention to returning to complete stock, but it's usually the only course of action for most people stuck with S-ON (and then would look into exploiting/unlocking/rooting again from there).
Click to expand...
Click to collapse
Im confused on which one to flash I have a T-Mobile HTC G2 which one will i flash?
choose the latest one for the g2, reading your thread I feel you will have little luck with this. try logging onto freenode #g2root, you'll get real time help here
Sent from my HTC Vision using xda premium
demkantor said:
choose the latest one for the g2, reading your thread I feel you will have little luck with this. try logging onto freenode #g2root, you'll get real time help here
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I am new to XDA how can i do that?
helstonrampersad said:
I am new to XDA how can i do that?
Click to expand...
Click to collapse
I'm new so I can't post links, but copy and paste this url: http://webchat.freenode.net/?channels=g2root
EDIT - Oh, I can post links.
eboy_gb said:
I'm new so I can't post links, but copy and paste this url: http://webchat.freenode.net/?channels=g2root
EDIT - Oh, I can post links.
Click to expand...
Click to collapse
Though ideally using an actual IRC client will work much nicer than a web chat one.
Same problem, but desire z S-ON
Hey guys.
I have the same problem with the boot loop /semi brick. Expect I never had any problem before, with the phone. I have tried taking out the sd card, starting it agian. I have tried without simcard. I have tried to flash the ROM with RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed
via Hboot Fastboot USB PLUG mode (which was the only mode the aplication was progressing in until it want to restart the phone in bootloader), but the phone frezzes and the aplication on the computer just keep working, without progress.
The factory reset just frezzes the phone.
The only thing reali seem to not frezze the phone is the revocery option. Here the phone react with restart showing a image of a phone with two green arrows bent around, over the phone. then it turns off the display and vibrate 4-5 times, og stays turn off not reacting to anything other then taking out the battery and you can start the phone once again.
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-26.10.04.19_M
eMMC-boot
Apr 11 2011, 23:36:27
Have no idea but the version of android. I know that usb debugging is NOT on Any hjelp is a big help. I'm a noob, And I have been searching for 3 days for a solution, so I just hope you can help my, otherwise it is going for a repair at the place I bought it.
Thanks
Hey people, got this cute little phone from my wife, was delighted initially because it seemed like custom rom haven and it really is cute little piece of functional white plastic (I meant, it was), but didn't last a day in my "new to Xperia" overconfident hands.
Anyway, I couldn't find any page that was foolproof and really explaining all the details step by step, so it kindaaa seeeems that I forgot the "unlock bootloader" part. I did several unsuccessful attempts at flashing official last version TWRP via terminal emulator and recommended app (can't remember name) - both seemed to do the work but couldn't boot into recovery, just regular reset. Then I tried Rushr app and flashed that TWRP image I had on SD card. I ran Reboot to recovery option - the thing just turned off. Now, what happens is that it vibrates for a second if I hold power button, but no go from there. If I connect it to PC blue light is on and PC says something like SP1FastBoot device connected or something like that.
So the big question is, is this soft or hard brick? What should poor bastard do in any case?
EDIT: Now I realized I get blue indicator light ONLY if I hold volume up before connecting to pc. If not, nothing lights. If I hold volume DOWN, I initially got "SEMC flash device connected", something like that.
your phone is completely alright, just install flashtool,its drives unlock the bootloader(there will be an option) and install recovery, after that flash a rom or stock backup
Thanks a lot, that's great news So in order to minimize risk of such noob mistakes I made (although still not sure what went wrong), I can use Flashtool for all my custom rom needs? Also, where can I download it, the links I found on XDA are dead, and googling brings out Sony's flashtool Emma. I really have no idea if it's the same thing or not, but from description it sounds like a tool for flashing stock roms, not customs. I need to be sure this time
EDIT: On XDA page dealing with TWRP installation: http://forum.xda-developers.com/xperia-m/orig-development/recovery-twrp-xpe it is specifically mentioned NOT to use Flashtool for flashing TWRP. Now it all gets confusing What does it mean, better chose CWM recovery or what?
ojas12345 said:
your phone is completely alright, just install flashtool,its drives unlock the bootloader(there will be an option) and install recovery, after that flash a rom or stock backup
Click to expand...
Click to collapse
Would you by any chance have some specific recommendations regarding recovery and rom combination? I prefer CM, but for instance, they say new CM 13 is for specific version of firmware (4.x, not sure which), and since my device is bricked, I have no way of checking what I have. Is there some combination of recovery/rom that's basically fool/brick proof? I found Flashtool, but I have to put roms in its folder, it doesn't come with or doesn't download firmwares from server or anything right?
I'm running in circles here, I'm stuck with Flashtool, and flashing Fota TWRP via Flashtool isn't recommended so... you see my problem
EDIT: I tried to unlock bootloader via Flashtool, I got middle finger: 08/042/2016 21:42:25 - INFO - Your phone bootloader cannot be officially unlocked
What does it mean? Am I doomed with stock firmware (even if I knew how to recover it) with "no custom roms" diet forever, or is there some "unofficial" solution?
C64Ever said:
EDIT: I tried to unlock bootloader via Flashtool, I got middle finger: 08/042/2016 21:42:25 - INFO - Your phone bootloader cannot be officially unlocked
What does it mean? Am I doomed with stock firmware (even if I knew how to recover it) with "no custom roms" diet forever, or is there some "unofficial" solution?
Click to expand...
Click to collapse
I have tried it with my device and i unlocked my bootloader successfully , just bootloop once , donno why is this happening with you maybe flashtool cannot recognise properly so try reinstalling the drivers from the flashtool folder!
ojas12345 said:
I have tried it with my device and i unlocked my bootloader successfully , just bootloop once , donno why is this happening with you maybe flashtool cannot recognise properly so try reinstalling the drivers from the flashtool folder!
Click to expand...
Click to collapse
There's nothing in .flashtool folder or subfolders, just a basic empty tree Seems Flashtool is a no go in my case, I think I'll try Sony's PC Companion, I think it's intended to recover stuck rom. And it requires 5 gigs of space on hard disk, so I guess it comes with everything already in the package
Fixed! Sony's Xperia tool is nothing short of miracle. Did the whole job, completely recovered device. Good job, Sony!