Related
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
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
hi guys,
Just messed up with my device.
I inslalled beat audion on my device and it get stuck ech time on starting apps...
Allreadydone a total wipe but still dont boot.
Like a ****ing retard i delet all the backups and install image that i had on my phone (i know it's stupid but i wanted winning some space)
I cat use toolkit cause its saying that my phone isnt on USB debuging.
Got TWR installed nothing but to flash.
Any idea for uploading a ROM install in my device? or other ideas for starting the os?
Im on AOKP build 5 btw
Thanks a lot guys
Fastboot, flash factory image.
fye85 said:
hi guys,
Just messed up with my device.
I inslalled beat audion on my device and it get stuck ech time on starting apps...
Allreadydone a total wipe but still dont boot.
Like a ****ing retard i delet all the backups and install image that i had on my phone (i know it's stupid but i wanted winning some space)
I cat use toolkit cause its saying that my phone isnt on USB debuging.
Got TWR installed nothing but to flash.
Any idea for uploading a ROM install in my device? or other ideas for starting the os?
Im on AOKP build 5 btw
Thanks a lot guys
Click to expand...
Click to collapse
If your phone is recognized try to push a rom that you can flash with TWRP through adb. Look here for how to do that http://forum.xda-developers.com/showthread.php?t=1667929.
snapper.fishes said:
Fastboot, flash factory image.
Click to expand...
Click to collapse
How flash the factory image in fast boot?
gee2012 said:
If your phone is recognized try to push a rom that you can flash with TWRP through adb. Look here for how to do that http://forum.xda-developers.com/showthread.php?t=1667929.
Click to expand...
Click to collapse
it's not possible to mount internal storage in TWRP????
Was possible on my HTC dedie 2 years ago
fye85 said:
How flash the factory image in fast boot?
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/showthread.php?t=2010312.
gee2012 said:
Look here http://forum.xda-developers.com/showthread.php?t=2010312.
Click to expand...
Click to collapse
Like i said i cant enable bebuging mod so im stuck in step one 'install drivers'
fye85 said:
Like i said i cant enable bebuging mod so im stuck in step one 'install drivers'
Click to expand...
Click to collapse
Yep nothing, when i typing fastboot devices in command prompt i cant see nothing;
My devices isnt reconise
Probleme solved.
It came from windows 8 (like always).
Have to change windows boot seetings befor installing drivers tuto is here :
http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109
please update thread title, it would be helpful for others...
Sent from my Nexus 4 using xda premium
Hey Guy,
Need some quick advise. So I bought my N10 back when it launched and its been pretty great! I use it for watching videos, playing games, and teaching (Im a science teacher). Anyways, I use my tablet Daily... a lot... and its never given me any issues at all really. Well about a month ago I noticed it responding a little slow and really laggy for about 2-3 minutes, then it restarted itself. I figured it was no big deal cuz its done that before. Well this time it never turned back on and it just stayed at the Google boot up screen. So I restarted it manually and then it just stayed on the "X" screen forever... Never left either of these screens until the battery would die.
I reinstalled android using the Nexus Root Toolkit and it does the job every time. It works GREAT...but.... only for about 10 minutes, then it starts to get really laggy and then restarts again and gets stuck in the bootloop.
I have it under warranty through staples and they are telling me since its a software issue they want me to send it back to Samsung. If it was a physical issue like broken screen, they would have replaced it by now.
The Tablet isnt rooted. I always root my devices, but since this was a nexus I didnt think it was necessary...for me at least.
Thanks
socjdqcer said:
Hey Guy,
Need some quick advise. So I bought my N10 back when it launched and its been pretty great! I use it for watching videos, playing games, and teaching (Im a science teacher). Anyways, I use my tablet Daily... a lot... and its never given me any issues at all really. Well about a month ago I noticed it responding a little slow and really laggy for about 2-3 minutes, then it restarted itself. I figured it was no big deal cuz its done that before. Well this time it never turned back on and it just stayed at the Google boot up screen. So I restarted it manually and then it just stayed on the "X" screen forever... Never left either of these screens until the battery would die.
I reinstalled android using the Nexus Root Toolkit and it does the job every time. It works GREAT...but.... only for about 10 minutes, then it starts to get really laggy and then restarts again and gets stuck in the bootloop.
I have it under warranty through staples and they are telling me since its a software issue they want me to send it back to Samsung. If it was a physical issue like broken screen, they would have replaced it by now.
The Tablet isnt rooted. I always root my devices, but since this was a nexus I didnt think it was necessary...for me at least.
Thanks
Click to expand...
Click to collapse
Smash the screen and get the replacement lol. Anyways I don't see now its a software issue when you flashed the factory image and nothing changed. Try downloading the new 4.3 factory image from Google and flash it manually instead of with the toolkit. If you still have the problem then I'm pretty sure its something to do with the hardware though I don't know how the hardware would affect it getting stuck at boot screen. This is a confusing problem. Anyways according to most people Samsung won't be much of a help and you'll get you're tablet back a week or two later in the same condition. Some people have had good luck with them and got a fixed device back so I guess if your out of options you might as well give it a shot
Sent from my Nexus 10 using xda app-developers app
abdel12345 said:
Smash the screen and get the replacement lol. Anyways I don't see now its a software issue when you flashed the factory image and nothing changed. Try downloading the new 4.3 factory image from Google and flash it manually instead of with the toolkit. If you still have the problem then I'm pretty sure its something to do with the hardware though I don't know how the hardware would affect it getting stuck at boot screen. This is a confusing problem. Anyways according to most people Samsung won't be much of a help and you'll get you're tablet back a week or two later in the same condition. Some people have had good luck with them and got a fixed device back so I guess if your out of options you might as well give it a shot
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot man. I just finished downloading the factory image now,but .... Noobie Question of the Day ... drum roll please ... how do I flash it manually? I transferred it to the device manually and then I opened up the bootloader then went to recovery mode then got into the stock recovery and the only options were Clear Cache...Clear Data... and ADB. Do I use ADB, If so Ill have to look that process up, I have never done that before. Sorry, Im not new to android or flashing or rooting, just new to Nexus I guess. My Samsung phones have corrupted me haha.
socjdqcer said:
Thanks a lot man. I just finished downloading the factory image now,but .... Noobie Question of the Day ... drum roll please ... how do I flash it manually? I transferred it to the device manually and then I opened up the bootloader then went to recovery mode then got into the stock recovery and the only options were Clear Cache...Clear Data... and ADB. Do I use ADB, If so Ill have to look that process up, I have never done that before. Sorry, Im not new to android or flashing or rooting, just new to Nexus I guess. My Samsung phones have corrupted me haha.
Click to expand...
Click to collapse
No, you don't use ADB to flash image files. Stay in bootloader where you see it say "Fastboot enabled". Extract the system, userdata, recovery and boot image from the package to C:\Program Files\WugFresh Development\data.
Username invalid said:
No, you don't use ADB to flash image files. Stay in bootloader where you see it say "Fastboot enabled". Extract the system, userdata, recovery and boot image from the package to C:\Program Files\WugFresh Development\data.
Click to expand...
Click to collapse
Thanks man, Ill give it a shot!
socjdqcer said:
Thanks man, Ill give it a shot!
Click to expand...
Click to collapse
After that open the toolkit > Advanced Options > Launch CMD.
Your computer should recognize your device by entering
Code:
fastboot devices
Username invalid said:
After that open the toolkit > Advanced Options > Launch CMD.
Your computer should recognize your device by entering
Code:
fastboot devices
Click to expand...
Click to collapse
Well, I manually updated and it worked like a charm...for about 10 minutes. Then it restarted and is stuck at the boot "Google" page! This blows!!!!!!!!!
socjdqcer said:
Well, I manually updated and it worked like a charm...for about 10 minutes. Then it restarted and is stuck at the boot "Google" page! This blows!!!!!!!!!
Click to expand...
Click to collapse
Rebooting into recovery and wiping the cache/dalvik cache usually works for me when it hangs on the loading screen.
Username invalid said:
Rebooting into recovery and wiping the cache/dalvik cache usually works for me when it hangs on the loading screen.
Click to expand...
Click to collapse
Yeah man, thats what I thought, so I have tried it a few times and whenever I go to wipe cache....The tablet doesnt really do anything and then all of a sudden it restarts. What would cause that?
try to use the toolkit to flash a factory image of 4.2.2 (mind it formats all data, files, music etc). See if it works fine. then unlock, root the device and install a custom recovery (all with the toolkit). If everything works you will have a rooted 4.2.2. Try the tablet and the recovery to see if everything works. If it does you can upgrade to 4.3
Well if your still having issues then just send it to Samsung and when it comes back if its still not working take it to staples and tell them Samsung said its a hardware issue or something. I'm pretty sure they'll replace it. I've always had good support with staples
Sent from my Nexus 10 using xda app-developers app
abdel12345 said:
Well if your still having issues then just send it to Samsung and when it comes back if its still not working take it to staples and tell them Samsung said its a hardware issue or something. I'm pretty sure they'll replace it. I've always had good support with staples
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Sounds good man! Thanks for the help!
Thanks EVERYONE! I tried everyone of your suggestions and the original issue still keeps happening. I can get the tablet to work for a little while, but the its back to bootloop.
Thanks
[Resolved]
Help, I downgraded from 2.3 to 2.2 for various reasons,but now when I try to upgrade again I just get the pink screen ,if I try using the option from settings/storage,it says key data couldn't be backed up , the installation will stop. Also if I boot into the system it runs fine for about a minute then locks up completely so I can't even continue to use it in 2.2 can anyone advise ?
Sent from my Nexus 7 using XDA Free mobile app
Try to put the 2.3 dload folder to a sd card, then remove the battery, plug in a USB cable to the computer and the phone, volume up+down+power (if I remember right lol). See if it will update that way.
no, that's the usual way I've been flashing it, I can get to the image folder ,but it won't boot into recovery either
Sent from my Nexus 7 using XDA Free mobile app
totsy1972 said:
no, that's the usual way I've been flashing it, I can get to the image folder ,but it won't boot into recovery either
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Odd. Maybe try to flash the ICS pink screen unlocker? I had weird issues at some point too, then I flashed that and the problems went away. Afterwards flash ICS.
Just tried that,still no luck,it doesn't even get to the unpacking screen,it just stays pink. beginning to think its beyond repair
Sent from my Nexus 7 using XDA Free mobile app
totsy1972 said:
Just tried that,still no luck,it doesn't even get to the unpacking screen,it just stays pink. beginning to think its beyond repair
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
I think it's still possible to fix it. I was loosing hopes too, but I messed around with it anyway and got it working. Just try different dload's, different methods and maybe you'll get it running. Maybe other users will have some ideas too.
CrysisLTU said:
I think it's still possible to fix it. I was loosing hopes too, but I messed around with it anyway and got it working. Just try different dload's, different methods and maybe you'll get it running. Maybe other users will have some ideas too.
Click to expand...
Click to collapse
I've been trying all different ways, this is what I get when trying it from storage menu
Sent from my ST15i using XDA Free mobile app
@Moihack maybe you have any ideas? You've written this to me before:
Moihack said:
As long as your phone still gets power and pink/blue screen shows there is nothing to be afraid of yet,since this isn't a hardbrick.
Contact me on hangouts telling me what you have done resulting in the above issue.
I have bricked my u8800pro in every possible way both soft and hard brick (thank god warranty was still active back then).
Click to expand...
Click to collapse
Hi there!
I think when you upgrade from software menu there is an option for data back-up.
Uncheck this option and the error should go away.
Also what do you mean with this: "Also if I boot into the system it runs fine for about a minute then locks up" ?
What do you mean it locks up? Touchscreen is not responsive for example?
My suggestions:
1) Do a factory reset and then check if you can upgrade
2) Try re-installing your recovery(use cwm 5.0.27 by geno for best compatibility) or even replace the whole image folder with the froyo one from here: http://forum.xda-developers.com/showthread.php?t=2146856
Your phone is not beyond repair that's for sure. Since it boots fine.
Moihack said:
Hi there!
I think when you upgrade from software menu there is an option for data back-up.
Uncheck this option and the error should go away.
Also what do you mean with this: "Also if I boot into the system it runs fine for about a minute then locks up" ?
What do you mean it locks up? Touchscreen is not responsive for example?
Click to expand...
Click to collapse
I haven't noticed an option for data backup,will check again later on. And yes when it locks up touch screen becomes unresponsive and none of the buttons respond either. Also when I try to enter recovery ,both custom and stock, it displays the kernel logo then vibrates with a black screen for a second then back to kernel logo and continues to boot.
Sent from my Nexus 7 using XDA Free mobile app
Ok guys,I copied over the stock image folder and now it works ok, however I still can't upgrade from froyo. At least I can use it again though so thanks for your help, its much appreciated. Incidentally, there wasn't an option to back up data when upgrading, but that error has now gone, except it now just reboots instead, so I will just keep trying.
Sent from my U8800Pro using XDA Free mobile app
[Edit] Finally I've managed to upgrade to GB , had to put both step 1 and step 2 in the same dload folder and it worked. So cheers for the tips
You've put all steps in one folder?
DarkSkyGhost said:
You've put all steps in one folder?
Click to expand...
Click to collapse
Steps 1&2 in dload folder ,step 2 renamed to UPDATE_G.APP.
Didn't use step 3 as I was updating to ICS after that
Sent from my Nexus 7 using xda app-developers app