Database Users

[Q] Rooted Mytouch 3g with bricked recovery. How to fix?

I tried uploading Froyo to my mytouch 3g. I rooted the phone using the one click method and backed up and flashed the new rom. Upon reboot, the rom wouldn't start up so I recovered and restored all previous settings. I found a new rom and went into recovery but i see the dreaded white triangle, but if I turn it on normal it starts up into the original rom fine and is still rooted. How do I get my recovery back? I am also running ROM manager.

Just reflash the recovery from ROM Manager.
Sent from my LG-P500 using Tapatalk

i reflashed 3 time and it didnt work i really need this. my phone has become very slow. any other way to fix it?

mk94 said:
i reflashed 3 time and it didnt work i really need this. my phone has become very slow. any other way to fix it?
Click to expand...
Click to collapse
Slowness is not problem of recovery. What do you want exactly?
Sent from my A7-040 using Tapatalk

mk94 said:
i reflashed 3 time and it didnt work i really need this. my phone has become very slow. any other way to fix it?
Click to expand...
Click to collapse
5[Strogino] said:
Slowness is not problem of recovery. What do you want exactly?
Sent from my A7-040 using Tapatalk
Click to expand...
Click to collapse
Seems to me like his phone keeps reinstalling the stock recovery upon reboot or rom manager isn't flashing properly, and probably needs to do it manually with "flash_image". . .
( I posted a way to fix the flashing recovery issue before: http://forum.xda-developers.com/showthread.php?t=1428838 )

First of all, u didnt described ur problem clearly. then, i think your recovery mode is ok, the thing is you couldn't go through that. did you tried to go to the recovery by holding home+power down key together? then the picture of a phone and a triangle with (!) mark comes up, release the keys and then press them together, hope you will solve ur problem through that.and for making ur phone faster, try bananabread 3.1 , right now i am using that. good luck

Help Me please!!! Atrix wont boot!!!!!

So here is what happened. I made a backup of a stock atrix firmware and copied the backup to my atrix on deodexed 2.3.4. I tried to install the backup but it stops somewhere along the line and says error formatting data.
now the phone wont connect to the computer. when i opened rsdlite however it shows that the device is connected.the phone bootloops and I cant copy anything to the phone cause i cant connect to the phone except through rsd sorry if i posted in the wrong section cause this is the only one i can post in. and i searched for solutions but no one has this same problem. PLEASE HELP

then if you CAN use rsd lite place phone in rds lite mode then use "stock sdk from motorola and flash it back i went all the way ro 1.26 then over rhe air updated to 1.83
but i also continued on to unlocked bootloader and flashed gigerbread build (alien ) after installing cwm
im also on usa at&t fyi

ltdanno360 said:
then if you CAN use rsd lite place phone in rds lite mode then use "stock sdk from motorola and flash it back i went all the way ro 1.26 then over rhe air updated to 1.83
but i also continued on to unlocked bootloader and flashed gigerbread build (alien ) after installing cwm
im also on usa at&t fyi
Click to expand...
Click to collapse
I tried to flash the official 2.3.4 found here http://forum.xda-developers.com/showthread.php?t=1181932 but now i just have a locked bl. and it still bootloops. Can you give me little more detailed instructions on what you did. I'm not too experienced.

Morpheaous said:
I tried to flash the official 2.3.4 found here http://forum.xda-developers.com/showthread.php?t=1181932 but now i just have a locked bl. and it still bootloops. Can you give me little more detailed instructions on what you did. I'm not too experienced.
Click to expand...
Click to collapse
Did u do factory reset after the flash
Sent from my MB860 using xda premium

My atrix wont even boot to the RSD etc selection screen
So i had my phone rooted and wanted to unlock the bootloader so i followed the steps from pudding but it did not work. everyone has a NS version of the phone in RSD Lite but mine was SE not sure why. So i tried a few times to flash the new image and clear everything out to no avail. now i don't even get to the menu that gives me 5 seconds to select what method i want to use to fix it.
all i get is a flash of this on the screen before it goes black again
SVF:105:1:2
Failed to boot 0x1000
(stays for a second)
Entering NWFlash Recovery Mode
(Flashes under the other text but really fast before the screen goes blank)
windows wont even recognize that its plugged in. but what else is odd is that while plugged in it seems to be charging as the green notification light stays on.
any help would be great. thank you

voidlogik said:
Failed to boot 0x1000
Click to expand...
Click to collapse
isnt that a hard brick? it's over.

sanriver12 said:
isnt that a hard brick? it's over.
Click to expand...
Click to collapse
really?? no way to unbrick it?

Morpheaous said:
I tried to flash the official 2.3.4 found here http://forum.xda-developers.com/showthread.php?t=1181932 but now i just have a locked bl. and it still bootloops. Can you give me little more detailed instructions on what you did. I'm not too experienced.
Click to expand...
Click to collapse
Bootloops means soft bricks which is not really a problem. When your phone Boots up, press the down key along worth the power button. Then keep pressing down button until you see Android Recovery. Do a factory reset or flash another room once in there.
Sent from my MB860 using XDA App

voidlogik said:
really?? no way to unbrick it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1165154

voidlogik said:
really?? no way to unbrick it?
Click to expand...
Click to collapse
Sounds like a hard brick indeed. At this moment in time hard bricks are incurable but some people said that taking their battery out and putting it back into their phones solved their problem. You might want to give it a shot.
A guy also claimed thay its possible to unhardbrick your phone using the jtag technique. You might want to read up on it.
Sent from my MB860 using XDA App

aIf it says failed to boot x1 its real bad but i got a failed to boot x2 and got it fixed but x1 tragic
Sent from my MB860 using xda premium

ltdanno360 said:
aIf it says failed to boot x1 its real bad but i got a failed to boot x2 and got it fixed but x1 tragic
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
English plz.
Sent from my MB860 using Tapatalk

me too
There's soo many forums and different avenues to go down! after about 9 hours trying various things to make my atrix (running normal 2.3.4 rooted with no other cm7 or rom or any other mod) i am left with my atrix at the boot screen OR if i leave it to boot it just makes the logging on noises then shows the white screen, then nothing.
I stupidly followed the list to freeze using bloatfreezer. Not the updated list where it reads next to HOME (make sure you have another launcher) so i have frozen 'home' and i am stuck.
i cannot do a recovery because it has that fail message x2 everytime i do the power volume - and + on the android recov.
I am completely lost. i do not understand what hard/soft/adw/ push email/ or other jargon means. If you have any solutions i'd be more than grateful.
I hope i haven't bricked my phone, cos a 2year contract and no new phone is gonna push me near that ledge lol

atrixuk said:
There's soo many forums and different avenues to go down! after about 9 hours trying various things to make my atrix (running normal 2.3.4 rooted with no other cm7 or rom or any other mod) i am left with my atrix at the boot screen OR if i leave it to boot it just makes the logging on noises then shows the white screen, then nothing.
I stupidly followed the list to freeze using bloatfreezer. Not the updated list where it reads next to HOME (make sure you have another launcher) so i have frozen 'home' and i am stuck.
i cannot do a recovery because it has that fail message x2 everytime i do the power volume - and + on the android recov.
I am completely lost. i do not understand what hard/soft/adw/ push email/ or other jargon means. If you have any solutions i'd be more than grateful.
I hope i haven't bricked my phone, cos a 2year contract and no new phone is gonna push me near that ledge lol
Click to expand...
Click to collapse
I'd recommend starting a new thread w/ your issue. It's more likely to be seen and answered by someone who could help.

atrixuk said:
There's soo many forums and different avenues to go down! after about 9 hours trying various things to make my atrix (running normal 2.3.4 rooted with no other cm7 or rom or any other mod) i am left with my atrix at the boot screen OR if i leave it to boot it just makes the logging on noises then shows the white screen, then nothing.
I stupidly followed the list to freeze using bloatfreezer. Not the updated list where it reads next to HOME (make sure you have another launcher) so i have frozen 'home' and i am stuck.
i cannot do a recovery because it has that fail message x2 everytime i do the power volume - and + on the android recov.
I am completely lost. i do not understand what hard/soft/adw/ push email/ or other jargon means. If you have any solutions i'd be more than grateful.
I hope i haven't bricked my phone, cos a 2year contract and no new phone is gonna push me near that ledge lol
Click to expand...
Click to collapse
If you're on AT&T - get RSD lite and find the proper sbf file and flash it. If you were using Gingerbread, make SURE you have a GINGERBREAD sbf file - or else you'll permanently brick your phone. If you're on Bell - you'll need the appropriate file for Bell to flash, same rules apply - If your on gingerbread, make SURE its a gingerbread file you're flashing.

atrixuk said:
There's soo many forums and different avenues to go down! after about 9 hours trying various things to make my atrix (running normal 2.3.4 rooted with no other cm7 or rom or any other mod) i am left with my atrix at the boot screen OR if i leave it to boot it just makes the logging on noises then shows the white screen, then nothing.
I stupidly followed the list to freeze using bloatfreezer. Not the updated list where it reads next to HOME (make sure you have another launcher) so i have frozen 'home' and i am stuck.
i cannot do a recovery because it has that fail message x2 everytime i do the power volume - and + on the android recov.
I am completely lost. i do not understand what hard/soft/adw/ push email/ or other jargon means. If you have any solutions i'd be more than grateful.
I hope i haven't bricked my phone, cos a 2year contract and no new phone is gonna push me near that ledge lol
Click to expand...
Click to collapse
you need to have an unlocked bootloader to flash Any custom rom PM me ill show ya how its not too hard
a pc a atrix and a few files and you will
be up n running in no time at all
Sent from my MB860 using Tapatalk

[Q] Nexus 7 wont boot

I was playing a game on my nexus 7, it froze then when rebooted it it just got stuck on google screen. Read a bunch of stuff, went into recovery and tried to recover, it would say erasing but never go any further, just sits there. got toolkit tried to restore factory with that, now when it boots I still just get google screen but I get the menu in corner for start/boot/recover/power off. still never boots, when I try to run recovery now it doesnt even go to erasing. Ive read everything I can find to restore it, got 2 toolkits, unfortunatly everything tells me to put it in debug mode, which is funny cause if I could boot up and go into settings to turn on bebug mode then I wouldnt be having these problems... Can someone please help, Im good with computers but dont know much of tablets. I did no messing with tablet besides downloading updates when they came out.

unlock bootloader
wcorey1974 said:
I was playing a game on my nexus 7, it froze then when rebooted it it just got stuck on google screen. Read a bunch of stuff, went into recovery and tried to recover, it would say erasing but never go any further, just sits there. got toolkit tried to restore factory with that, now when it boots I still just get google screen but I get the menu in corner for start/boot/recover/power off. still never boots, when I try to run recovery now it doesnt even go to erasing. Ive read everything I can find to restore it, got 2 toolkits, unfortunatly everything tells me to put it in debug mode, which is funny cause if I could boot up and go into settings to turn on bebug mode then I wouldnt be having these problems... Can someone please help, Im good with computers but dont know much of tablets. I did no messing with tablet besides downloading updates when they came out.
Click to expand...
Click to collapse
Also forgot to add, hen I try and run recovery from toolkit it tells me to unlock bootloader, when I try to unlock bootloadermy nexus asks me if I want to then when I hit yes, unlock it gives me neither usp nor cac partitions found.

Are you rooted?
Sent from my Nexus 7 using Tapatalk HD

Dark Jedi said:
Are you rooted?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
My guess is no, I never messed with any of my system stuff. Everything was factory except for the updates it had me do as they came out.

How long you let it sit in recovery erasing before you rebooted it? Is there an option in boot loader or recovery for a factory reset? Beings you're not rooted I doubt those one click tool kits will work for you.
Sent from my Nexus 7 using Tapatalk HD

Dark Jedi said:
How long you let it sit in recovery erasing before you rebooted it? Is there an option in boot loader or recovery for a factory reset? Beings you're not rooted I doubt those one click tool kits will work for you.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
It sat in erasing for 1 hour and didnt do anything. I was doing factory reset in recovery.

As long as the boot loader starts you can recover your Nexus. Check this guide: http://forum.xda-developers.com/showthread.php?t=1907796

If he can't unlock the bootloader then there's not a whole lot he can do. Run "fastboot getvar all" while in bootloader and tell us what it says please. If adb is seeing your phone in recovery, then run an adb shell and do "ls -l /dev/block/platform/sdhci-tegra.3/by-name/" please.

Sorry I can't help further but I just got this and don't know much. I am glad others came in to give you more help.
Sent from my Nexus 7 using Tapatalk HD

Damn... I didn't see he can't unlock the bootloader. This is going to be difficult.

wcorey1974 said:
My guess is no, I never messed with any of my system stuff. Everything was factory except for the updates it had me do as they came out.
Click to expand...
Click to collapse
Im exact in the same situation. No rooted phone, nexus wont boot anymore, cant dont anything in the bootloader section ...
I would be extremley thankfull for hints how to fix this issue.
Cheers
Papa

Just sayin, I think you guys need to pull the back cover and disconnect the battery for at least one hour.
I am really new at this but it helped me save mine twice. I think?
After you plug the battery back in try fast boot.
Sent from my Nexus 7 using XDA Premium HD app

tnt0303 said:
Just sayin, I think you guys need to pull the back cover and disconnect the battery for at least one hour.
I am really new at this but it helped me save mine twice. I think?
After you plug the battery back in try fast boot.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
But this will void my warranty right ?

They have no way in knowing you pulled your back cover off. Just be careful so not to leave pry marks. Only way they will know is if you tell them you did it.
Sent from my Nexus 7 using Tapatalk HD

[Q] Flashed ROM - it rebooted and died?

Hi,
Sorry if this has been covered but search is down and I am panicking! I have an i-337 ATT Galaxy S4 that was unlocked for Tmobile. I just bought it 2 days ago and tonight I rooted it via motochopper and installed TWRP.
I downloaded Liquidsmooth and Gapps and flashed them via recovery. I did a factory reset and a nandroid backup. After the flash I selected reboot, and the phone turned off like it was rebooting, but never came back on!
I did a battery pull and nothing! I also tried holding down + home + power!
I accidentally forgot to wipe cache/dalvik cache after the install.
Help! I hope this isn't a brick. I've been rooting phones for a while and haven't ran into a problem.
No response when I plug it into the computer, and no charging light (the battery probably has 95% charge)
Thanks

re: download/recovery modes
Nurmi_CEO said:
Hi,
Sorry if this has been covered but search is down and I am panicking! I have an i-337 ATT Galaxy S4 that was unlocked for Tmobile. I just bought it 2 days ago and tonight I rooted it via motochopper and installed TWRP.
I downloaded Liquidsmooth and Gapps and flashed them via recovery. I did a factory reset and a nandroid backup. After the flash I selected reboot, and the phone turned off like it was rebooting, but never came back on!
I did a battery pull and nothing! I also tried holding down + home + power!
I accidentally forgot to wipe cache/dalvik cache after the install.
Help! I hope this isn't a brick. I've been rooting phones for a while and haven't ran into a problem.
No response when I plug it into the computer, and no charging light (the battery probably has 95% charge)
Thanks
Click to expand...
Click to collapse
You were holding down the wrong buttons.
Press and hold the VOL-UP button then press and hold the POWER button until
you see tiny blue text on upper left side of screen to go into "Recovery Mode".
If you want download mode do it the same way except instead of the VOL-UP
you need to press and hold the VOL-DOWN.
Good luck with it.
Remember it;s faster to click the "THANKS" button than it takes to type "thank you"!

Misterjunky said:
You were holding down the wrong buttons.
Press and hold the VOL-UP button then press and hold the POWER button until
you see tiny blue text on upper left side of screen to go into "Recovery Mode".
If you want download mode do it the same way except instead of the VOL-UP
you need to press and hold the VOL-DOWN.
Good luck with it.
Remember it;s faster to click the "THANKS" button than it takes to type "thank you"!
Click to expand...
Click to collapse
Tried....no go still nothing

Nurmi_CEO said:
Tried....no go still nothing
Click to expand...
Click to collapse
Can you link to the specific rom you flashed. It's sounds to me like you might have flashed a bad or wrong rom.

Yes....I went to original android development and got liquidsmooth...http://goo.gl/jvdfwT. I clicked on the latest version and it's the third from the bottom . says att at the end . sorry I'm on my phone browser.

Nurmi_CEO said:
Yes....I went to original android development and got liquidsmooth...http://goo.gl/jvdfwT. I clicked on the latest version and it's the third from the bottom . says att at the end . sorry I'm on my phone browser.
Click to expand...
Click to collapse
I can't tell if the t01teatt is for your specific device. I haven't seen the t01te before. I would have expected something different. The symptoms you describe sounds like a bricked device caused by flashing a rom not for your specific device.

I assume your MDL cause you have a custom recovery.
Did you use Auto Loki recovery?
If you didn't use Auto Loki recovery did you flash the Loki doki zip ?
We need all steps you took from start to end before you rebooted your phone.
Sent from my SPH-L720 using XDA Premium 4 mobile app

the phone was bone stock locked att i337. I unlocked it via the service hidden menu on YouTube. it worked fine.
next I rooted it with the motochopper, flashed twrp with goo manager and rebooted to recovery. my first load with twrp seemed to hang up and freeze, so I pulled the battery and rebooted into twrp.
I loaded the liquidsmooth to1att and gapps to be flashed. both seemed to flash successfully, and then I hit restart. forgot to wipe cache and dalvik, planned on rebooting back into recovery to wipe/maybe reflash and wipe cache.
the phone turned off and never turned back on.
I had a T-Mobile sim card in the entire time.
thanks and please help. sending this from my crappy evo lte

Did a little searching and I think the t01te is the note ii. Check out mobiletechvideos.com. they might be able to jtag it.

after root the phone was working fine on the stock ROM.

Nurmi_CEO said:
after root the phone was working fine on the stock ROM.
Click to expand...
Click to collapse
It's the rom you flashed after that which is causing the problem. Like I said I think it was for the note II and not the i337

Yup we only have liquidsmooth 2.10. Tolteatt is not this phone. This phone is jflteatt. Your only option is JTAG as jd1639 said
Sent from my SGH-I337 using Tapatalk

rushi.1986 said:
Yup we only have liquidsmooth 2.10. Tolteatt is not this phone. This phone is jflteatt. Your only option is JTAG as jd1639 said
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
send in for repair? only option? thanks for help

Nurmi_CEO said:
send in for repair? only option? thanks for help
Click to expand...
Click to collapse
If Odin doesn't recognize it, and I think you said it doesn't, then yea I think that's your only hope. But I'd keep trying to get it into download mode and have Odin recognize it. I haven't seen a hard brick of the i337.
Use the original usb cable, the usb ports in the back of the computer, and if that doesn't work try a different computer.

The build.prop in that ROM you flashed says it is for the SAMSUNG-SGH-I317 which is the Galaxy Note II. That's why it is bricked. Make sure you don't try to flash that one again. If you do get it to come up in download mode make sure you have the correct file before trying to flash again.
Good luck!

Nurmi_CEO said:
send in for repair? only option? thanks for help
Click to expand...
Click to collapse
Well that, or if its in warranty, send it off to samsung and play dumb! Just say something like "it turned off during firmware upgrade and never turned back on"

rushi.1986 said:
Well that, or if its in warranty, send it off to samsung and play dumb! Just say something like "it turned off during firmware upgrade and never turned back on"
Click to expand...
Click to collapse
...and end up with an MF3 phone?
It's better to send it off for Jtag like JD said. If it never had the MF3 bootloader on it, there shouldn't be a problem with them putting MDL back on it (as long as there isn't a hardware issue). To me, the cost is well worth it.

scott14719 said:
...and end up with an MF3 phone?
Click to expand...
Click to collapse
Good point! I didn't think of that..

Help: hard bricked?

I was trying to unlock my Nexus 10 with 4.4.2 through fastboot. First I booted into fastboot mode, and then issued the following command:
fastboot oem unlock
I saw on the tablet the status showed 'unlocked'. After that I just pushed the power button to try to reboot, but it keeps spinning. Even if I pushed the power button again, spinning remains. And I can't shut it down either. Is it hard bricked? What should I do now? Should I have waited for the tablet to reboot itself?

mj56gt said:
I was trying to unlock my Nexus 10 with 4.4.2 through fastboot. First I booted into fastboot mode, and then issued the following command:
fastboot oem unlock
I saw on the tablet the status showed 'unlocked'. After that I just pushed the power button to try to reboot, but it keeps spinning. Even if I pushed the power button again, spinning remains. And I can't shut it down either. Is it hard bricked? What should I do now? Should I have waited for the tablet to reboot itself?
Click to expand...
Click to collapse
You should be fine. Hold down the power button and both volume buttons until it restarts into the bootloader. Go into the Recovery Mode. Then, you'll see the little android on his back with a red exclamation mark over him. Don't panic. You need to hit power + volume down at the same time (no need to hold). It may take a few tries, but when successful, you'll see the recovery menu pop up. Do a factory data wipe. Then, after it does it's thing. Select reboot system and you're good to go.

charesa39 said:
You should be fine. Hold down the power button and both volume buttons until it restarts into the bootloader. Go into the Recovery Mode. Then, you'll see the little android on his back with a red exclamation mark over him. Don't panic. You need to hit power + volume down at the same time (no need to hold). It may take a few tries, but when successful, you'll see the recovery menu pop up. Do a factory data wipe. Then, after it does it's thing. Select reboot system and you're good to go.
Click to expand...
Click to collapse
Thanks a lot! Those steps fixed the problem... I really appreciate your help!!!

mj56gt said:
Thanks a lot! Those steps fixed the problem... I really appreciate your help!!!
Click to expand...
Click to collapse
No problem. Same thing happened to me on my N10 (and also my Nexus 5). Has something to do with it not properly wiping/formatting the data partition after unlock like it's supposed to, so you have to do it manually.

It was quite a scary experience for me! Thanks again for the kind help...
Also I just flashed TWRP 2.7.0.1, and then flashed SuperSU-v1.80 in TWRP. It said successful, but both Root Checker and Busybox indicate that it's not rooted. What did I do it wrong?

mj56gt said:
It was quite a scary experience for me! Thanks again for the kind help...
Also I just flashed TWRP 2.7.0.1, and then flashed SuperSU-v1.80 in TWRP. It said successful, but both Root Checker and Busybox indicate that it's not rooted. What did I do it wrong?
Click to expand...
Click to collapse
Hmm. That's odd. Unfortunately, I don't use TWRP, so probably couldn't help much there as I prefer Philz Recovery. I do know that SuperSU v1.80 is a pretty old version (may be some compatibility issues with 4.4.2). Have you tried downloading and flashing the latest SuperSU in TWRP? I believe it's v1.94. I would try that first.

charesa39 said:
I do know that SuperSU v1.80 is a pretty old version (may be some compatibility issues with 4.4.2). Have you tried downloading and flashing the latest SuperSU in TWRP? I believe it's v1.94. I would try that first.
Click to expand...
Click to collapse
You're absolutely right. Previously when I googled SuperSU, it came out with the version 1.80 for some reason. This time I used Google Play, sure enough it installed v1.94! And everything looks good now!
You made my day! Thanks a lot...
Sent from my Nexus 10 using xda app-developers app

mj56gt said:
You're absolutely right. Previously when I googled SuperSU, it came out with the version 1.80 for some reason. This time I used Google Play, sure enough it installed v1.94! And everything looks good now!
You made my day! Thanks a lot...
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
No problem. I, too, am familiar with that feeling you get in the pit of your stomach when you start to think you just ruined your not-so-cheap toy. Just glad I could help you get through it. Regards.
Sent from my Nexus 7 using xda app-developers app