[Q] Possible bricked phone after root attempt - myTouch 3G Slide Q&A, Help & Troubleshooting

Hi guys,
After trying to root my phone by using the rollback to 2.1 method (mt3srooter and superoneclick), my phone is stuck.
To elaborate, my phone is rolled back to 2.1 but I cannot for the life of me get it back to the 2.2.1 stock rom. I tried to do a factory reset and soft reset it but it either
1. Starts up showing an exclamation point inside of a triangle in front of a phone, after pressing power and the volume up button, I clear the cache, factory reset it and initiate system reboot which is when the phone does start up but vibrates 5 times while lighting up the notification light.
or 2. Boots regularly to 2.1 but is unstable and shuts off occasionally vibrating 5 times again
During the rooting process in mt3srooter I didn't turn on the wi-fi (due to the fact that I did not transfer the zip files beforehand and panicked) as instructed which I think caused the problem.
I already flashed esprimg but it's the same.
Also, my phone does not recognize that there is an SD card inside (I used two different microSD cards with no avail and formatted them). It does not register on my computer as a device it's just labled as "Unkown device" and the driver software fails to install.
Is there any way to get my phone back to the way it was?
Any help is appreciated!
Edit: The phone has no warranty, I bought it from a 3rd party unlocked.

Kaop said:
Hi guys,
After trying to root my phone by using the rollback to 2.1 method (mt3srooter and superoneclick), my phone is stuck.
To elaborate, my phone is rolled back to 2.1 but I cannot for the life of me get it back to the 2.2.1 stock rom. I tried to do a factory reset and soft reset it but it either
1. Starts up showing an exclamation point inside of a triangle in front of a phone, after pressing power and the volume up button, I clear the cache, factory reset it and initiate system reboot which is when the phone does start up but vibrates 5 times while lighting up the notification light.
or 2. Boots regularly to 2.1 but is unstable and shuts off occasionally vibrating 5 times again
During the rooting process in mt3srooter I didn't turn on the wi-fi (due to the fact that I did not transfer the zip files beforehand and panicked) as instructed which I think caused the problem.
I already flashed esprimg but it's the same.
Also, my phone does not recognize that there is an SD card inside (I used two different microSD cards with no avail and formatted them). It does not register on my computer as a device it's just labled as "Unkown device" and the driver software fails to install.
Is there any way to get my phone back to the way it was?
Any help is appreciated!
Edit: The phone has no warranty, I bought it from a 3rd party unlocked.
Click to expand...
Click to collapse
humm so the esprimg didnt work through the hboot and did you try to root again

Related

Please Help Me

So after an unsuccessful ROM flash my phone was stuck at bootloader for quite sometime...i had a micro SD card reader and inserted it into multiple computers running XP, vista and ubuntu...they all registered that i had plugged something in but wouldn't show it as a disk drive...now i've already figured out how to access it but i put a new ROM image on it and tried to reflash but after the flash when my phone booted up it simply switched itself off... when i switched it back on it went back to the bootloader and tried to reflash the ROM. mid flash it just switches itself off... I realize that this is probably due to the charge level of the phone so i plugged it it but it will be off and charging then it will suddenly decide its got enough battery power and boot up to the bootloader screen until it dies again...how do i stop this vicious loop
tlglegacy said:
So after an unsuccessful ROM flash my phone was stuck at bootloader for quite sometime...i had a micro SD card reader and inserted it into multiple computers running XP, vista and ubuntu...they all registered that i had plugged something in but wouldn't show it as a disk drive...now i've already figured out how to access it but i put a new ROM image on it and tried to reflash but after the flash when my phone booted up it simply switched itself off... when i switched it back on it went back to the bootloader and tried to reflash the ROM. mid flash it just switches itself off... I realize that this is probably due to the charge level of the phone so i plugged it it but it will be off and charging then it will suddenly decide its got enough battery power and boot up to the bootloader screen until it dies again...how do i stop this vicious loop
Click to expand...
Click to collapse
Something worth trying:
1.You could take out the battery for one minute or longer.
2.Now put the ROM's .nbh on your SD card [Make sure it is named "RHODIMG.nbh" (no quotes)].
3.Put the SD card and battery in and press/hold Power button and the Volume Down button at the same time.
4.That'll put you in Bootloader Mode, and it should ask you if you want to update your phone's image (something like that).
5.Follow the prompts and it should start flashing (you'll see the bar).
6.Soft reset after the flash says it's complete.
I once went through that and this is what I did. I was able to unbrick my phone.
However, (back in September/October) there was another instance of the same thing happening to someone, but he never got it fixed; he did get the stock ROM and SPL back on it, but had to return it to HTC because it still kept cycling into Bootloader.
Good luck!

[Q] ROM update fail, cannot flash with Odin

Hi,
My brother's SGH-T989D phone (Koodo / Telus) crashed during an android update. Now, the phone boots to a black screen with the taskbar on top. There is no menu screen anymore. No apps at all. Doing a factory reset via the recovery mode does not change anything.
My PC does not detect the phone. Therefore, I am unable to install a new ROM with Odin. Here are all the infos I have :
1. The phone boots, but there is absolutely nothing except the task bar (I can toggle the wifi and bluetooth on and off, thats it...). There phone says preparing SD storage upon booting. There are no SD card and SIM card.
2. The phone is able to go into recovery and download modes.
3. My PC does not detect the phone. I know the Samsung drivers, Odin v3.07 and USB cable are working properly because I am able to connect my own phone which is also a SGH-T989D.
4. In recovery mode, there is a dead android with a red triangle with an "!" in the background.
5. It used to have the stock gingerbread Koodo ROM, and was probably updated over the air to the newest ICS from Koodo.
6. The phone was never rooted or messed with. I don't think it was ever connected to a computer before.
7. It is not under warranty anymore.
I've spent hours trying to get it recognized by the computer. I've tried putting the ROM on the SD card and applying the update via external storage in recovery mode. I get a message about Signature verification failure.
I've tried cleaning the micro-usb slot. Blowing in it resulted in the computer saying "Unknown device malfunctioned" a single time, which leads me to believe it only did that because some saliva created a short somewhere in there. The connections look clean.
I'm about to throw this phone off the building. What is wrong with it?
**EDIT**
Forgot to mention...the phone does charge when connected to the usb cable.
kamikazee1989 said:
Hi,
My brother's SGH-T989D phone (Koodo / Telus) crashed during an android update. Now, the phone boots to a black screen with the taskbar on top. There is no menu screen anymore. No apps at all. Doing a factory reset via the recovery mode does not change anything.
My PC does not detect the phone. Therefore, I am unable to install a new ROM with Odin. Here are all the infos I have :
1. The phone boots, but there is absolutely nothing except the task bar (I can toggle the wifi and bluetooth on and off, thats it...). There phone says preparing SD storage upon booting. There are no SD card and SIM card.
2. The phone is able to go into recovery and download modes.
3. My PC does not detect the phone. I know the Samsung drivers, Odin v3.07 and USB cable are working properly because I am able to connect my own phone which is also a SGH-T989D.
4. In recovery mode, there is a dead android with a red triangle with an "!" in the background.
5. It used to have the stock gingerbread Koodo ROM, and was probably updated over the air to the newest ICS from Koodo.
6. The phone was never rooted or messed with. I don't think it was ever connected to a computer before.
7. It is not under warranty anymore.
I've spent hours trying to get it recognized by the computer. I've tried putting the ROM on the SD card and applying the update via external storage in recovery mode. I get a message about Signature verification failure.
I've tried cleaning the micro-usb slot. Blowing in it resulted in the computer saying "Unknown device malfunctioned" a single time, which leads me to believe it only did that because some saliva created a short somewhere in there. The connections look clean.
I'm about to throw this phone off the building. What is wrong with it?
**EDIT**
Forgot to mention...the phone does charge when connected to the usb cable.
Click to expand...
Click to collapse
IDK if this will help you. IF the phone isn't rooted or a custom recovery installed I don't believe you can reinstall the ROM. It does say 'signature verification error' so you might be able to turn off MD5 checking before install. It will be in the settings menu if TWRP is used. I don't believe its an option to do if on stock recovery.

[Q] Deleted my OS... HELP!!!

Ok so first, let me say I know I done goofed. What happened was my phone (Note 2 GT-N7100) started to choke up a lot, battery life was ridiculously low and then suddenly my phone's language was constantly being switched to Italian.
I thought it might be a virus but a scan couldn't find anything. I deleted almost all apps in hopes it would stop but the phone went on with these weird glitches. In an act of desperation, I decided to wipe out everything and go back to factory settings.
Thing is my phone is rooted and I had the X Note Rom installed. When I tried the factory reset on TWRP, it still went back to the X Note Rom. That's when I dun goofed. I deleted EVERY ****ING THING in a desperate and stupid move.
Now when I press Volume Up + Home + Power I can get to Recovery Mode but I ain't got **** to install. If I press Volume Down + Home + Power I get into Odin mode but get a "Downloading... Do not turn off target!!" message that just hangs there forever.
To top it off, my computer won't recognize the damn phone anymore. Am I ****ed? Can I get myself out of this mess?! Please HELP!!!
Take it easy, download a custom rom, transfer it to the SD card, enter recovery and Flash it.
Since you can't connect the phone via USB, you need a SD card reader (if you have a laptop you 100% have it)
OR
You could flash the stock ROM through Odin, but it's more risky in my opinion. I would go with the 1st method
Mashed_Potatoes said:
Take it easy, download a custom rom, transfer it to the SD card, enter recovery and Flash it.
Since you can't connect the phone via USB, you need a SD card reader (if you have a laptop you 100% have it)
OR
You could flash the stock ROM through Odin, but it's more risky in my opinion. I would go with the 1st method
Click to expand...
Click to collapse
thanks... i'll try that when i get home (my SD card is there).

OPPO Keyboard has stopped working, leading me to stuck on a fastboot loop.

Please help. This is a serious matter for me.
Started having this problem at February 14th, 02.10 AM.
Have been looking for the answers in the Oppo Forums too but still got no answers.
Okay, I have a habit, which is moving all of my applications from my internal storage to my external SD card, after I let those applications doing their functions and programs and features and so on for a while. It's not a big deal for me to set up my phone again after I restarted it, and usually it works perfectly. Just restart and I would get to operate my phone again. However, this time, I got a bad luck. The worst one, considering the fact that I'm all-around-gadget.
Here's the results I got from reading a lot of threads (not only from this forum and OPPO forums):
OPPO Swype Keyboard has stopped working? Really?
After restarting my un-rooted Find 7 (9076), I cannot type the password on my lock screen. Like any other Android devices, it would always come back to it's system or default applications, I knew that fact. But this time, when I touched the blank space to type my password, nothing came out. No OPPO Keyboard, which happened to be OPPO's default keyboard. No other keyboards. None at all.
So, I cannot do one single thing to my phone except just turn it on and stared at it like a complete idiot.
Then I decided to turn my phone off and turn it on again after a while.
But still, the same thing happened. No keyboards.
That time, I decided to turn off my phone again and pulled out the battery and my external SD card.
After putting the battery back (External SD Card was still outside), and turned it on again, the same thing still happened.
Sliding my fingers up and down, nothing happened. The touchscreen was still there, showing me my date and time even though I was sliding my fingertips up and down.
Not too long after, I felt my phone got warmer and warmer. I tried double-clicking the home button, which I already set to unlock the lock screen, was also useless. The screen was still black and locked. When it got over-heating, automatically I pulled out the battery without even turning off the phone.
That one was my fault. I knew, and well, honestly speaking, this is the first time I'm in this kind of situation. In the past, my Find 7 would just suddenly restarted itself then everything went back to normal, but not this time.
And here's the beginning of my Fastboot Loop.
Fastboot Loop on un-rooted device
After pressing the Power button and the Volume Up button at the same time, it would bring you to the Recovery Mode. When I did that to my Find 7, it brought me to a black backgrounded screen with cute OPPO mascot and some Hanzi (Chinese handwritings). Picture attached.
I tried to wait for 2-3 hours and found nothing happened.
Pulling the batter out and putting the batter back would do the same.
In other words, I am not able to gain access to my Recovery Mode.
Why didn't bring the phone to the service centre?
I thought about this already.
When I tried to connect my phone to my pc, it can detect the phone but cannot access the files because the phone was still locked with the password.
Usually, the service centre requires us to unlock the phone if there's a problem with it, right? In my cases, yes.
I was searching all night to find out the answers.
I found some threads about the Fastboot Loop thing and etc, but they are only for rooted devices.
I'm using:
OPPO Find 7 (9076)
Color OS 2.0.5i Beta
Android KitKat 4.4.2
Device is not rooted, still original.
Still dealing with the same problem until now (the time I post this thread).
Anyone has solved this problem and guide me step by step to finish this?
daiichi said:
Please help. This is a serious matter for me.
Started having this problem at February 14th, 02.10 AM.
Have been looking for the answers in the Oppo Forums too but still got no answers.
Okay, I have a habit, which is moving all of my applications from my internal storage to my external SD card, after I let those applications doing their functions and programs and features and so on for a while. It's not a big deal for me to set up my phone again after I restarted it, and usually it works perfectly. Just restart and I would get to operate my phone again. However, this time, I got a bad luck. The worst one, considering the fact that I'm all-around-gadget.
Here's the results I got from reading a lot of threads (not only from this forum and OPPO forums):
OPPO Swype Keyboard has stopped working? Really?
After restarting my un-rooted Find 7 (9076), I cannot type the password on my lock screen. Like any other Android devices, it would always come back to it's system or default applications, I knew that fact. But this time, when I touched the blank space to type my password, nothing came out. No OPPO Keyboard, which happened to be OPPO's default keyboard. No other keyboards. None at all.
So, I cannot do one single thing to my phone except just turn it on and stared at it like a complete idiot.
Then I decided to turn my phone off and turn it on again after a while.
But still, the same thing happened. No keyboards.
That time, I decided to turn off my phone again and pulled out the battery and my external SD card.
After putting the battery back (External SD Card was still outside), and turned it on again, the same thing still happened.
Sliding my fingers up and down, nothing happened. The touchscreen was still there, showing me my date and time even though I was sliding my fingertips up and down.
Not too long after, I felt my phone got warmer and warmer. I tried double-clicking the home button, which I already set to unlock the lock screen, was also useless. The screen was still black and locked. When it got over-heating, automatically I pulled out the battery without even turning off the phone.
That one was my fault. I knew, and well, honestly speaking, this is the first time I'm in this kind of situation. In the past, my Find 7 would just suddenly restarted itself then everything went back to normal, but not this time.
And here's the beginning of my Fastboot Loop.
Fastboot Loop on un-rooted device
After pressing the Power button and the Volume Up button at the same time, it would bring you to the Recovery Mode. When I did that to my Find 7, it brought me to a black backgrounded screen with cute OPPO mascot and some Hanzi (Chinese handwritings). Picture attached.
I tried to wait for 2-3 hours and found nothing happened.
Pulling the batter out and putting the batter back would do the same.
In other words, I am not able to gain access to my Recovery Mode.
Why didn't bring the phone to the service centre?
I thought about this already.
When I tried to connect my phone to my pc, it can detect the phone but cannot access the files because the phone was still locked with the password.
Usually, the service centre requires us to unlock the phone if there's a problem with it, right? In my cases, yes.
I was searching all night to find out the answers.
I found some threads about the Fastboot Loop thing and etc, but they are only for rooted devices.
I'm using:
OPPO Find 7 (9076)
Color OS 2.0.5i Beta
Android KitKat 4.4.2
Device is not rooted, still original.
Still dealing with the same problem until now (the time I post this thread).
Anyone has solved this problem and guide me step by step to finish this?
Click to expand...
Click to collapse
boot into recovery and format the phone, this should fix it. If you want to backup your data, just boot into fastboot, connect phone to pc, run fastboot command from sdk tool, push custom recovery, flash twrp, make nandroid backup, fomat phone along with all the storage and then flash oppo stock rom (you need to download) or any other custom rom with gapps. To restore use nandroid manager, do not restore system files if you are flashing custom rom.
treacherous_hawk said:
boot into recovery and format the phone, this should fix it. If you want to backup your data, just boot into fastboot, connect phone to pc, run fastboot command from sdk tool, push custom recovery, flash twrp, make nandroid backup, fomat phone along with all the storage and then flash oppo stock rom (you need to download) or any other custom rom with gapps. To restore use nandroid manager, do not restore system files if you are flashing custom rom.
Click to expand...
Click to collapse
Thank you for your help Sir.
But, my Find 7 already operated normally again since I left it for a few days uncharged and off.
Then I got into Recovery Mode by pressing Power button and Volume Down button (not Volume Up button) while in the middle of my fast-boot loop.
It worked. I could gain access to ColorOS Recovery Mode.
So, I reset my Find 7, then re-installed my applications and everything again.
Thank you for answering!

Help with bricked phone

The phone when trying to boot is stuck on the samsung logo. it doesnt progress past this. pressing and holding the power button makes screen go black and then it just returns to the samsung logo again when power button released.
Originally factory
reset phone... no difference,
wiped cache... no difference.
Got it to register in Odin. Odin crashed and hung part way through.
Now... computer doesn't recognise phone (drivers all installed)
Phone still stuck on samsung logo
Can't put in a file on SD card as it doesn't have option to install from zip from SD (think it was standard ROM and not rooted so doesn't have this ability from what I understand.)
Can get into recovery menus and download mode, however as PC can't recognize the phone can't do anything with it.
Anyone have any idea how I can make the computer recognize the phone so I can attempt to reflash it?
Many thanks
I have just gotten a new cable. The phone has been accepted by my computer with this new cable and I've now used the files on this forum to help flash the phone. This site is fantastic. I know noone has mentioned a response to this yet, however the ROM files accessible make it so easy from here. Thanks so much.

Categories

Resources