Related
I was trying to odin back to the stock JI6. I had forgotten to turn off the oclf lag fix. I managed to get out of the "Phone ! PC" mode to download mode. I proceeded to odin Eugene's froyo that doesn't brick. At this point my phone proceeded to boot into recovery mode. It stays there. THe power button does not allow me to select any options. I have also been unable to get into download mode again.
I have filed a warranty claim with tmobile for a new phone.
My questions are as follows:
1. Will T-Mobile be able to tell if my phone has been rooted, custom modded, etc?
2. How am I able fix this problem and flash back to stock?
3. Is there anyway to wipe the phone at the current time?
I am not worried about losing any information, I just would like to completely wipe the phone so that nothing can be taken off the phone.
Thanks for your help, and thanks to all the awesome devs out there helping us make our phones even more awesome.
EDIT: Solved! Thanks everyone.
On the eugene's that doesn't brick thread aren't there instructions for using adb to reboot the device after flashing it? And if you type "reboot download" without quotations your phone should reboot into dl mode and be odin ready for stock or whatever.
I usually just pull the battery, manually reboot to dl mode after flashing froyo that doesn't brick and flash stock from there.
Sent from my Vibrant running Macnut R10
hold the vol up and down keys, (with the phone off) and plug into computer. This should get it into download mode
To answer your question, no. The moment you rooted & flashed a custom ROM you voided your warranty.
I need to thank all three of you, I have learned three very important things;
1. Read all of the directions.
2. Don't hit the power button when trying to go to download.
3. T-Mobile will not cancel a warranty exchange request but they don't care if you don't actually exchange the phones.
Again thanks anyone,
Abe
Not that it matters anymore... but at the point you got to the GS stock recovery where the power key wouldn't respond, you should if done "adb reboot". Then continued.
I had tried to flash the stock webtop on my atrix 4g, after i had done the webtop mod(due to the screen presses from the phone would not work, and it also would not allow me to have the normal functionality and so i wanted to go back to stock for webtop). Not too sure if I'm able to post the link to where i found the instructions, but i did get it from atrix forums.
But pretty much now, when i turn my phone on, it gets stuck on the Motorola screen with text saying...
Failed to boot 4
Starting RSD Mode
I did read up and saw that from my POV, the best thing would be to get the stock sbf and use RSD Lite and flash it back to the beginning. But a few things do come up,
I found a thread in XDA where it had all the sbf i could want, but they were uploaded into filesonic which will not let me download it.
Would this be the only option for me to go?
Also some background into phone, AT&T Atrix 4g, was running 2.3.4, firmware 4.5.91 and was rooted. Any enlightenment on my pridicament would be much appreciated. Thank you for your time in reading.
First, did you have an unlocked bootloader?
If not, that's your problem.
Second, is there an option to get into recovery?
If so, try to perform a "Factory Reset" within the recovery before trying to use RSD lite (not recommended).
Dilphat said:
I had tried to flash the stock webtop on my atrix 4g, after i had done the webtop mod(due to the screen presses from the phone would not work, and it also would not allow me to have the normal functionality and so i wanted to go back to stock for webtop). Not too sure if I'm able to post the link to where i found the instructions, but i did get it from atrix forums.
But pretty much now, when i turn my phone on, it gets stuck on the Motorola screen with text saying...
Failed to boot 4
Starting RSD Mode
I did read up and saw that from my POV, the best thing would be to get the stock sbf and use RSD Lite and flash it back to the beginning. But a few things do come up,
I found a thread in XDA where it had all the sbf i could want, but they were uploaded into filesonic which will not let me download it.
Would this be the only option for me to go?
Also some background into phone, AT&T Atrix 4g, was running 2.3.4, firmware 4.5.91 and was rooted. Any enlightenment on my pridicament would be much appreciated. Thank you for your time in reading.
Click to expand...
Click to collapse
unlocked bootloader, that would be a negative. I guess that was what happened as to why i'm in this situation. But trying to get it back to factory settings, when i turn on the phone and hold down power button and vol down, it shows the Motorolla screen, i keep holding it down...it never shows the option for fast boot or the menu to change to be able to get it back to factory. Unless I'm doing it wrong, but it goes to Motorola screen then waits a bit and then screen turns off. Any ideas? If RSD Lite is not recommended, what's a good try to take? thanks for replying back quite fast.
Just to confirm the steps:
1. Press and hold the volume down button
2. Then press the power button (note: you don't need to continue holding the power button when doing this)
3. Continue holding the volume down button until it says "Fastboot"
If that's what you did then that would be correct. Actually, try just booting it normally and see if it gives you any options while booting.
Dilphat said:
unlocked bootloader, that would be a negative. I guess that was what happened as to why i'm in this situation. But trying to get it back to factory settings, when i turn on the phone and hold down power button and vol down, it shows the Motorolla screen, i keep holding it down...it never shows the option for fast boot or the menu to change to be able to get it back to factory. Unless I'm doing it wrong, but it goes to Motorola screen then waits a bit and then screen turns off. Any ideas? If RSD Lite is not recommended, what's a good try to take? thanks for replying back quite fast.
Click to expand...
Click to collapse
When I let it boot up without pressing anything, it just says
"Failed to boot 4"
"Starting RSD mode"
When i hold down vol down button for a bit nothing. I did notice though if i press the vol down button directly after i get "failed to boot 4" it blinks something real quick and then the screen goes black(which then i would have to take out the battery and put the batter back in). ...but what flashes, i believes says nvflash.
If i press volume up button after it says "Failed to boot 4" it gives me..
"Starting Fastboot protocal support"
So with no touch, "Starting RSD mode".
Vol down, I think it says nvflash
Vol up, Starting fastboot protocal support.
Well, when it says "Starting Fastboot protocol support" it means it is in fastboot but I don't know for sure what you could do from other than "fastboot -w" which would erase userdata and cache. Do you have the fastboot files? Have you thought about trying to flash Pudding if you can get it into RSD mode? You could then flash a custom recovery in fastboot from that point and either try to factory reset or flash a custom rom/fruitcake.
Dilphat said:
When I let it boot up without pressing anything, it just says
"Failed to boot 4"
"Starting RSD mode"
When i hold down vol down button for a bit nothing. I did notice though if i press the vol down button directly after i get "failed to boot 4" it blinks something real quick and then the screen goes black(which then i would have to take out the battery and put the batter back in). ...but what flashes, i believes says nvflash.
If i press volume up button after it says "Failed to boot 4" it gives me..
"Starting Fastboot protocal support"
So with no touch, "Starting RSD mode".
Vol down, I think it says nvflash
Vol up, Starting fastboot protocal support.
Click to expand...
Click to collapse
So what are the chances of me getting a hard brick if i did the RSD Lite as what was proposed in other occurences?
Also with pudding, do I need anything done special on the phone...unlock bootloader or anything else? just want to make sure, since i don't want to be in this situation again or worse lol.
Also, what do you mean by if i have the fastboot files? such as the ones i used to root the phone?
There's really no measurement of risk for using RSD lite. If used properly it should go without a hitch but there have been "rare" occurrences of things going wrong. If you can find the correct sbf(2.3.4-4.5.91 signed) and download the current RSD then you should be fine
Pudding is the unlocked bootloader.
Fastboot files is what is needed to give commands in fastboot mode. (eg. "fastboot.exe")
Dilphat said:
So what are the chances of me getting a hard brick if i did the RSD Lite as what was proposed in other occurences?
Also with pudding, do I need anything done special on the phone...unlock bootloader or anything else? just want to make sure, since i don't want to be in this situation again or worse lol.
Also, what do you mean by if i have the fastboot files? such as the ones i used to root the phone?
Click to expand...
Click to collapse
is it that hard to find a signed sbf for 2.3.4 4.5.91 at&t?
Also, what would be the benefits of going the pudding way versus if i just attempt the rsd way?
which one is safer? lol
Pudding, in a sense, is safer as it will unlock your bootloader and you can flash ROMs all day with a custom recovery but it would help to have the appropriate knowledge before diving in. You mentioned you had rooted your phone but what else, as far as modding, are you familiar with?
I actually tried to find an sbf to link to for you but couldn't find one.
Dilphat said:
is it that hard to find a signed sbf for 2.3.4 4.5.91 at&t?
Also, what would be the benefits of going the pudding way versus if i just attempt the rsd way?
which one is safer? lol
Click to expand...
Click to collapse
well this atrix 4g is my first android based phone. As far as modding, i came from the winmo scene. from a fuze to tilt 2 to this atrix. thanks for actually trying to look for a sbf, i was able to find one not on filesonic...
http://www.4shared.com/archive/viniGE9x/1FF-olympus-user-234-4591-1106.html
but just not sure if it is the appropriate one needed. also, while i was at work, i did try and see what i could find on pudding and found a thread in regards to it, but nothing too much in detail about it. except for a if you don't understand any of the top 3 reasons then do this lol.
live4nyy said:
Pudding, in a sense, is safer as it will unlock your bootloader and you can flash ROMs all day with a custom recovery but it would help to have the appropriate knowledge before diving in. You mentioned you had rooted your phone but what else, as far as modding, are you familiar with?
I actually tried to find an sbf to link to for you but couldn't find one.
Click to expand...
Click to collapse
And what i'm getting when looking up pudding is this...
http://forum.xda-developers.com/showthread.php?t=1136261
and it looks like i still have to run rsd lite o_0, i'm so confused lol
Dilphat said:
well this atrix 4g is my first android based phone. As far as modding, i came from the winmo scene. from a fuze to tilt 2 to this atrix. thanks for actually trying to look for a sbf, i was able to find one not on filesonic...
http://www.4shared.com/archive/viniGE9x/1FF-olympus-user-234-4591-1106.html
but just not sure if it is the appropriate one needed. also, while i was at work, i did try and see what i could find on pudding and found a thread in regards to it, but nothing too much in detail about it. except for a if you don't understand any of the top 3 reasons then do this lol.
Click to expand...
Click to collapse
Failed to boot 4
Just in case someone else get's this error.
I used this sbf. at&t signed 2.3.4 4.5.91
http://www.4shared.com/archive/viniGE9x/1FF-olympus-user-234-4591-1106.html
and RSD Lite v5.6
From there when phone got to the motorola screen and said
"Failed to boot 4"
"Starting RSD Mode"
ran RSD with the sbf, it went through it's thing and it worked. it did revert everything that was done when the phone was rooted, and there is no root.
BTW, thanks for the help live4nyy!
live4nyy said:
There's really no measurement of risk for using RSD lite. If used properly it should go without a hitch but there have been "rare" occurrences of things going wrong. If you can find the correct sbf(2.3.4-4.5.91 signed) and download the current RSD then you should be fine
Pudding is the unlocked bootloader.
Fastboot files is what is needed to give commands in fastboot mode. (eg. "fastboot.exe")
Click to expand...
Click to collapse
edit* got the phone rooted again. now my problem is, webtop is gone lol. any thoughts on how to reinstall it?
Weird, the SBF file should of had that included. How big(MB) was the SBF file?
Dilphat said:
edit* got the phone rooted again. now my problem is, webtop is gone lol. any thoughts on how to reinstall it?
Click to expand...
Click to collapse
after extracted it is 1.46gb
live4nyy said:
Weird, the SBF file should of had that included. How big(MB) was the SBF file?
Click to expand...
Click to collapse
That sounds about right. How are you trying to access webtop? Do you have a lapdock or are you trying to just plug it into a monitor with the HDMI cable?
Dilphat said:
after extracted it is 1.46gb
Click to expand...
Click to collapse
I just figured out what i did wrong, i didn't have my hd multimedia dock plugged in lol
live4nyy said:
That sounds about right. How are you trying to access webtop? Do you have a lapdock or are you trying to just plug it into a monitor with the HDMI cable?
Click to expand...
Click to collapse
Major "derpage"...
Glad you got it working.
Dilphat said:
I just figured out what i did wrong, i didn't have my hd multimedia dock plugged in lol
Click to expand...
Click to collapse
I know right, and yup...I'm glad I got it working as well. but yup, in case it happens to anyone else, i put up the link to the sbf. just in case lol.
Now this gives me time to read up into unlocking the bootloader and flashing roms
live4nyy said:
Major "derpage"...
Glad you got it working.
Click to expand...
Click to collapse
I'm pretty new to the whole flashing business, so if whatever I asked does not make sense, please be patient. Thanks!
I recently flashed the Neutrino Rom V2.6 from V2.5p2. Got lazy and didn't do a full wipe before flashing (also my battery was at ~5% ) After the installation, I successfully booted into Android, but realized that the fresh ROM didn't have multilingual or sync support (since the Neutrino Rom is a stripped down CM7), so I booted back into recovery (still with low battery)
I subsequently flashed the addons provided by the dev for multilingual and sync support, and when I selected "Go back" in CWM recovery, it displayed a long string of error messages, I believe starting with E:\"........."
Ignoring the error messages, I selected "reboot system", hoping luck would be on my side, but it wasn't
the result of all this is is that I can only "turn on" the phone with it plugged, and it will go through loops at the Moto bootscreen...also if I try to enter recovery by pressing "power+vol down", the screen goes blank and does not enter CWM recovery. Further, I am also unable to charge the battery for some reason, because as soon as I plug the phone into the wall charger, it will go through the Moto bootloop
My question is, is this a hardbrick or softbrick?
If it's a softbrick, is there any way of fixing it, or has somebody else ran into a similar problem?
Please help me out here, like I said, I'm new to the whole world of flashing stuff, so much advice is needed, and any help would be appreciated!
Thanks a lot ahead of time
pkvlover004 said:
I'm pretty new to the whole flashing business, so if whatever I asked does not make sense, please be patient. Thanks!
I recently flashed the Neutrino Rom V2.6 from V2.5p2. Got lazy and didn't do a full wipe before flashing (also my battery was at ~5% ) After the installation, I successfully booted into Android, but realized that the fresh ROM didn't have multilingual or sync support (since the Neutrino Rom is a stripped down CM7), so I booted back into recovery (still with low battery)
I subsequently flashed the addons provided by the dev for multilingual and sync support, and when I selected "Go back" in CWM recovery, it displayed a long string of error messages, I believe starting with E:\"........."
Ignoring the error messages, I selected "reboot system", hoping luck would be on my side, but it wasn't
the result of all this is is that I can only "turn on" the phone with it plugged, and it will go through loops at the Moto bootscreen...also if I try to enter recovery by pressing "power+vol down", the screen goes blank and does not enter CWM recovery. Further, I am also unable to charge the battery for some reason, because as soon as I plug the phone into the wall charger, it will go through the Moto bootloop
My question is, is this a hardbrick or softbrick?
If it's a softbrick, is there any way of fixing it, or has somebody else ran into a similar problem?
Please help me out here, like I said, I'm new to the whole world of flashing stuff, so much advice is needed, and any help would be appreciated!
Thanks a lot ahead of time
Click to expand...
Click to collapse
Before you begin, turn OFF phone, remove battery, and connect to wall charger charger. When ? appears, install your battery and let it charge for a long time. NEVER FLASH WITH LOW BATTERY!
You need to reflash your recovery. Before you start, perform a proper WIPE. SKIP THE FIRST 4 STEPS, read this:
CaelanT said:
boot to recovery (DISREGARD)
Wipe Dalvik (DISREGARD)
wipe cache (DISREGARD)
factory reset/data (DISREGARD)
boot into fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot
flash ROM in recovery
wipe Dalvik
wipe cache
reboot
Click to expand...
Click to collapse
This is the Recovery you should be using: http://forum.xda-developers.com/showthread.php?t=1204500
Make sure you fully understand before proceeding! If you do not know about fastboot, read up on it.
NOTE: I believe your device is soft bricked.
i have the same problem i was trying to connect my wifi it showed ..error...flashing 1-cm7 rc 1 ....neurtrino ee....darkside.....then neutrino gt in that order i flashed........i get the same thing u get the phone just continues to turn on n off on boot animation screen.....no cwm i just shows a black screeen ............anyone can assist us with are problem
wsxyz said:
i have the same problem i was trying to connect my wifi it showed ..error...flashing 1-cm7 rc 1 ....neurtrino ee....darkside.....then neutrino gt in that order i flashed........i get the same thing u get the phone just continues to turn on n off on boot animation screen.....no cwm i just shows a black screeen ............anyone can assist us with are problem
Click to expand...
Click to collapse
Are you able to select Fastboot from the menu?
Soldier-2Point0 said:
Before you begin, turn OFF phone, remove battery, and connect to wall charger charger. When ? appears, install your battery and let it charge for a long time. NEVER FLASH WITH LOW BATTERY!
You need to reflash your recovery. Before you start, perform a proper WIPE read this:
This is the Recovery you should be using: http://forum.xda-developers.com/showthread.php?t=1204500
Make sure you fully understand before proceeding! If you do not know about fastboot, read up on it.
NOTE: I believe your device is soft bricked.
Click to expand...
Click to collapse
Thanks for the reply!
When I plug in the phone without battery, it just goes to the Moto boot screen, and starts the loop again...the usual "?" symbol doesn't appear at all
I've done battery calibration before, where it was required to plug phone into wall charger without battery, and the "?" has always appeared
Soldier-2Point0 said:
Are you able to select Fastboot from the menu?
Click to expand...
Click to collapse
I CAN select Fastboot from the menu, but it says "battery too low to flash"
pkvlover004 said:
Thanks for the reply!
When I plug in the phone without battery, it just goes to the Moto boot screen, and starts the loop again...the usual "?" symbol doesn't appear at all
I've done battery calibration before, where it was required to plug phone into wall charger without battery, and the "?" has always appeared
Click to expand...
Click to collapse
Can you plug in your phone, with the battery in, to your pc and get to the fastboot, recovery, etc menu???
---------- Post added at 03:04 PM ---------- Previous post was at 03:03 PM ----------
pkvlover004 said:
I CAN select Fastboot from the menu, but it says "battery too low to flash"
Click to expand...
Click to collapse
Try getting to that menu and let it charge for a while? Have you tried that? ANd I mean, let it charge for about an hour. Charging might take longer than usual because your screen will be on.
Soldier-2Point0 said:
Are you able to select Fastboot from the menu?
Click to expand...
Click to collapse
Soldier-2Point0 said:
Can you plug in your phone, with the battery in, to your pc and get to the fastboot, recovery, etc menu???
---------- Post added at 03:04 PM ---------- Previous post was at 03:03 PM ----------
Try getting to that menu and let it charge for a while? Have you tried that?
Click to expand...
Click to collapse
trying to charge at fastboot menu now
will try fastboot/recovery via USB soon
pkvlover004 said:
trying to charge at fastboot menu now
will try fastboot/recovery via USB soon
Click to expand...
Click to collapse
Good luck!
update: charging on the fastboot screen now - the battery is a little warm, that means it's getting charged up?
pkvlover004 said:
update: charging on the fastboot screen now - the battery is a little warm, that means it's getting charged up?
Click to expand...
Click to collapse
It is possible, but remember your screen is on.
I guess you're good now?
Sent from my MB860 CM7 olympus latest nightly 30p Radio. Leave your charger at home!
sorry for the late reply...and thanks for all the help
no actually am not, I still can't get the battery charged up, which is the biggest issue right now...
I think if I can find someway to charge the battery without plugging in the phone, it's possible to enter fastboot with a charged battery
otherwise, even if I get to the bootloader menu (fastboot, nvflash, recovery etc etc), when I plug the phone into the computer and select fastboot, it'll still say "battery too low to flash"
Just a suggestion...trying to help. What if you find out a fresh charged battery before starting the recover procedure? I dunno if it will work because I dunno if there is some kind of serial number checking at this low level in the phone....I see that under no circunstances could you charge your battery again...
Marcelocohenarg said:
Just a suggestion...trying to help. What if you find out a fresh charged battery before starting the recover procedure? I dunno if it will work because I dunno if there is some kind of serial number checking at this low level in the phone....I see that under no circunstances could you charge your battery again...
Click to expand...
Click to collapse
pkvlover004 said:
sorry for the late reply...and thanks for all the help
no actually am not, I still can't get the battery charged up, which is the biggest issue right now...
I think if I can find someway to charge the battery without plugging in the phone, it's possible to enter fastboot with a charged battery
otherwise, even if I get to the bootloader menu (fastboot, nvflash, recovery etc etc), when I plug the phone into the computer and select fastboot, it'll still say "battery too low to flash"
Click to expand...
Click to collapse
Borrow or buy a battery. Or make a new thread asking how to charge battery. Title on the thread is misleading.
thanks
Soldier-2Point0 said:
Before you begin, turn OFF phone, remove battery, and connect to wall charger charger. When ? appears, install your battery and let it charge for a long time. NEVER FLASH WITH LOW BATTERY!
You need to reflash your recovery. Before you start, perform a proper WIPE. SKIP THE FIRST 4 STEPS, read this:
This is the Recovery you should be using: http://forum.xda-developers.com/showthread.php?t=1204500
Make sure you fully understand before proceeding! If you do not know about fastboot, read up on it.
NOTE: I believe your device is soft bricked.
Click to expand...
Click to collapse
i use this method n it worked thanks..to bad my wifi still shows up error after i attempt to connect it it doesn't reboot thats good i think
low battery
Even i am stuck in recovery. No matter how many times i flash a ROM after wipe data/ cache partition and dalvik and then install the ROM i still boot into recovery when the ROM asks to reboot the device.
Here's what happened
1. Had a nandroid backup of older version of CWM mostly 5.0.2.x
2. Based on Nottachtrix thread installed the romracer recovery(updated flashable zip)
3. Updated to Nottachtrix 1.3.1 and successfully booted
4. Figured out that contacts everything weren't synced. So wanted to go back to older CM7 rom using restore ROM
5. Something went wrong during restoration. Data and other wern't restored and i guess only boot had been restored
6. Endless loop into recovery thereafter.
Trying out different things like flashing boot.img, recovery etc battery drained and couldn't flash.
Fasbtoot and other options triggered by using volume buttons and power button works fine. RDS also detects the device but bootloader unknown and other info all were unknown.
Since battery drained i was searching on methods to charge the battery. Had figured out that custom method for charging the phone needs to be implemented.
While playing around again with phone i powered it through directly through charger and opted for linux cold-booting which gave me the battery icon with the question mark on screen. Popped in the battery and it started to charge. So now i know i can charge the battery using this method.
I am yet to make progress on flashing ROM successfully again. Is my backup lost ? Did the error happen because i backed up using an older version of CWM or flashing to Nottachtrix changed something
I even restored successfully to my previous ROM after deleting .android secure from ext SDcard but still it threw me to CWM only :|
Help appreciated.
Hi! Can someone guide me into removing or getting access to the battery of this unit. I think the kernel is corrupted coz I think I flashed the wrong one. The battery drained out. So without a working kernel, I cant charge the phone. Even in USB to PC or directly to wall charger. I want to re-insert t the battery to see if that fixes the issue.
Can someone tell me if removing the battery then plugging in the usb without the battery if I can enter flash mode or flash boot to be able to flash the correct kernel or go back to stok room for the phone? Would that work?
Or I just need to reinsert the battery then try to enter flash mode?
SITUATION:
- cant enter flash mode or fast boot.
- can hard reset (Power + volume+)
- Cant turn on the phone
-just red led when plugged in then disapperas after a few minutes (not charging)
- the phone never got wet or never been dropped. (so im hoping this is a software issue)
- phone is rooted, unlocked BL with CWM.
-started when I flashed a flshable version of CWM touch version to upgrade from version 5 to 6.
Help please. Im thinking of opening the phone to access the battery.
The idea of removing non-removable battery is not the best one, unless you really know what are you doing - and i don't think you know it.
And i think this won't help you, really not.
eclpsues said:
SITUATION:
- the battery drained out
- can hard reset (Power + volume+)
Click to expand...
Click to collapse
You can hard reset - but battery is drained?
Once, i had problem like this one, but i managed to get into fastboot and re-flashed right kernel.
What were you exactly doing? Rooted and BL unlocked Go? What and how were you flashing (which rom and kernel were you flashing)?
Sent from my XGO using fingers
MyWnm said:
The idea of removing non-removable battery is not the best one, unless you really know what are you doing - and i don't think you know it.
And i think this won't help you, really not.
You can hard reset - but battery is drained?
Once, i had problem like this one, but i managed to get into fastboot and re-flashed right kernel.
What were you exactly doing? Rooted and BL unlocked Go? What and how were you flashing (which rom and kernel were you flashing)?
Sent from my XGO using fingers
Click to expand...
Click to collapse
sorry just a typo error, i mean i cant hard reset. I know how to access an embedded bat, tried it before with Xperia S. but I was hoping if can flash without doing that anymore?
Managed to disconnect and reconnect the battery; however I still cant turn it on, or even hard reset, or flash mode or fast boot. Crappppp! help. What can I do to bring this phone's life back. I flashed an update for CWM on recovery. Thats when this problem started.
any help out there?
Same problem
eclpsues said:
any help out there?
Click to expand...
Click to collapse
Hi, i am having the same problem. I flashed the kernel for another model out of noobness. So removing the battery did not help at all?
OMG right as i was typing this, the rubber band trick worked and i accessed fastboot and flashed another kernel. It wont start for now, but maybe the battery needs to be charged for a while (red led). In case you dont know (if you still have this problem), i will explain what i did (the computer just detected the device, so i think im in the clear):
1) get a rubber band and put it around vol up button (this is for fastboot; for flash it would be vol down)
2) plug the phone to your computer
3) get the fastboot.exe file (google)
4) put the correct boot.img file (or kernel, i flashed the wron boot.img, so i did it this way. I dont know what the difference is) in the same folder as fastboot.exe
4) open command prompt, go to the fastboot folder (look up commands)
5) type in "fastboot flash boot boot.img"
6) the cmd will say "waiting for device..."
leave it like that; i got purple (i guess blue plus red) led after awhile and fastboot flashed the kernel.
I will keep you informed on success or failure.
EDIT
It worked, i have a running phone.
Hey! Thanks for the post and reply, would have done that. However, i sent my phone to a repair center, and they havent got bakc at me until now, its been 3 weeks.
Was your phone unable to go fastboot and flashmode too before? And when you charge it red led appears then goes away after a few minutes? My PC cant recognize the phone, the only indicator i had was the red led when plugged in which goes away after a couple of minutes.
How long did it take for the phone to enter fastboot? Coz, I've tried holding the button (Vol+) for almost 5 minutes and nothing happens.
Can you provide me the exact situation you had? and the clear cut steps you took to fix it? Especially how many minutes for it to go to fastboot with the rubber band on?
TIA!
@ madismet
your rubber band technique actually worked!! thanks a lot!
I was just about to give up on my xperia go, when I came across your post...
thanks!! :good:
how long did it take to enter fastboot?
eclpsues said:
Hi! Can someone guide me into removing or getting access to the battery of this unit. I think the kernel is corrupted coz I think I flashed the wrong one. The battery drained out. So without a working kernel, I cant charge the phone. Even in USB to PC or directly to wall charger. I want to re-insert t the battery to see if that fixes the issue.
Can someone tell me if removing the battery then plugging in the usb without the battery if I can enter flash mode or flash boot to be able to flash the correct kernel or go back to stok room for the phone? Would that work?
Or I just need to reinsert the battery then try to enter flash mode?
SITUATION:
- cant enter flash mode or fast boot.
- can hard reset (Power + volume+)
- Cant turn on the phone
-just red led when plugged in then disapperas after a few minutes (not charging)
- the phone never got wet or never been dropped. (so im hoping this is a software issue)
- phone is rooted, unlocked BL with CWM.
-started when I flashed a flshable version of CWM touch version to upgrade from version 5 to 6.
Help please. Im thinking of opening the phone to access the battery.
Click to expand...
Click to collapse
Check this out. It's explained in pretty detail here.
hxxp://xperiagobattery.blogspot.in/2014/11/how-to-change-xperia-go-st27i-battery.html
Hello,
I'm rooting/installing a custom rom on a friends phone. I'm on 2.3.5, .418. I successfully rooted using the self-extracting method. I've been trying to flash CWM/bootstrap to no avail. I was wondering if anyone had any ideas on what to do?
I've tried droid2bootstrap v1.0.5 and This .apk method. Neither seem to work. When I tell the phone to boot into recovery via the application is just reboots normally, if I select booting into recovery via vol- + pwr once I select android recovery it goes into a screen similar to that of cwm recovery, but there are no options and I have to perform a battery pull to reboot the phone.
Any help/ideas would be fantastic.
Thanks!
I'm special
bdpope88 said:
Hello,
I'm rooting/installing a custom rom on a friends phone. I'm on 2.3.5, .418. I successfully rooted using the self-extracting method. I've been trying to flash CWM/bootstrap to no avail. I was wondering if anyone had any ideas on what to do?
I've tried droid2bootstrap v1.0.5 and This .apk method. Neither seem to work. When I tell the phone to boot into recovery via the application is just reboots normally, if I select booting into recovery via vol- + pwr once I select android recovery it goes into a screen similar to that of cwm recovery, but there are no options and I have to perform a battery pull to reboot the phone.
Any help/ideas would be fantastic.
Thanks!
Click to expand...
Click to collapse
Well, found out what the issue was. The .apk method linked above asked that you plug in your phone to an AC outlet. I thought this was to ensure that your battery is high enough. With the battery at 100%, I ignored the warning. Going over the issue one last time, I tried plugging in the phone and it worked like a charm.
I'll leave this up just in case someone in the future is as special as I am.
bdpope88 said:
Well, found out what the issue was. The .apk method linked above asked that you plug in your phone to an AC outlet. I thought this was a, to ensure that your battery is high enough. With the battery at 100%, I ignored the warning. Going over the issue one last time, I tried plugging in the phone and it worked like a charm.
I'll leave this up just in case someone in the future is as special as I am.
Click to expand...
Click to collapse
LOL. Well done sir.