[Completed] lg volt ls740zv5 sort of bricked - XDA Assist

Can someone help me please?
I rooted my phone and got a little carried away with debloating. Now the phone boots up but it's sort of a black screen. I can see the clock and stuff and I can swipe top down to view the notifications. I can also push the power button and push it again to use call and messaging. Other than that it's just total darkness.
I think something went horribly wrong during debloating because the system app remover crashed while it uninstall some apps.
I held the volume down key and power button to do a factory reset and that didn't help.
Help meeee!

Hi there,
You could try to adb sideload a rom and flash it. Or fastboot flash a working recovery onto your device, and then sideload a rom and flash it. Or you may have to reflash stock firmware onto your device to get it to work. Here is a guide as to how to flash roms: http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android.
To sideload, the command is simply "adb sideload name of file" without the quotation marks.
For further help regarding your problem, you can post your questions in the XDA help forum: http://forum.xda-developers.com/general/help.
Good luck

Related

[Q] LG MyTouch Bricked! Please help...

I went to clockworkmod's website and downloaded a cyanogen mod rom that they claimed was compatible with my device... Now the thing is bricked and I can't seem to recover the original rom... Anyone have any suggestions?
What do you see when you try to boot?Please explain little bit more. I have E739 too and CM7 works good for me.
go to the telephone service
When I turn the phone on the android on the skateboard shows up and that is all you see. It stays at that screen for about give minutes and then the system crashes.
I've tried every key combo I can think of to get it to go into recovery mode and or into clockwork mode, and nothing...
I've had that problem before. You didn't wipe data,cache and dalvik cache before installing CM7..you need to get into CWM recovery.. *From T-mobile website* To perform a master reset using hardware keys, follow these steps:
Turn off the phone.
Press and hold the Volume Down and Power keys.
Wait 3 seconds and press the Back and Menu keys.
Note: If you see the LG logo before pressing the Back and Menu keys, the reset hasnt been completed and you will need to restart.
Release the Power/Lock key after you see the LG logo.
Release the remaining keys after the LG logo flashes (blinks once).
The Android Unpacking screen appears.
The phone will restart and complete the factory reset.
Note: If you unintentionally press the Volume Down, Volume Up and Power keys simultaneously, the phone will display a circle icon with two arrows and 'S/W Upgrade, Please wait while upgrading...' message. You will need to pull the battery and restart
Click to expand...
Click to collapse
Hopefully you backed up your ROM before installing CM7..in CWM recovery use volume keys and power button to go to Backup/restore and then restore to most recent backup.
---------- Post added at 12:45 PM ---------- Previous post was at 12:29 PM ----------
or when in CWM try following in this link http://forum.xda-developers.com/showthread.php?t=1484673
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
@DarkLP: Already tried that, and it doesn't work on this model phone. I did wipe all the caches before restarting too. Not quite sure what to do next...
Timing is precise in getting into recovery, keep trying eventually you will get there, I have the same phone.
I bricked my phone too yesterday, I am really sad now. I was panicking and trying to save my phone but all it does is go into the LG logo, blinks once, and shows a half cut-off LG logo.. I tried doing that master reset thing.. are you sure it works? I'd dedicate all my time just to unbrick my phone

			
				
I was able to unbrick my phone the other day using Android SDK and the command prompt. What you need to do is have a backup of your ROM saved on your sd card. Use the command prompt to put the phone into CWM recovery mode and then choose the backup/restore option on your phone.
If the backup is stirred in the correct file on your sd card then the recovery program will automatically detect it. From there choose the file you want to install and then activate the restore process.
You should be good to go after that.
That is what i was going to say.
Ahaha I couldn't be any more happy, I went into recovery using that button combo trick, flashed C7 and a Kernel and Google Apps (you have to flash google apps if you want them) go to cyanogen mod wiki and find g-apps there. To get your cyanogen rom just google "lg mytouch roms" and you should click the android central link and then scroll down and someone posted the files for it. Only thing that went wrong is the Camera doesn't work..
It should be same as Dream G1, download a .pnh and Fastboot
Low end cheap bro.....
Tmobile Customer Service
TMO's customer service is pretty good. Call them and tell them you were installing a non market piece of software (true enough) and that your phone won't power on. They will walk you through some steps that might get you going and if not they will offer to replace your phone if it is still under warranty. I sent my defy back several times whaen I was learning to flash ROM's. Then, remember to wipe everything before you flash anything.
OK that doesn't make sense. once you root your phone, warranty gets voided.
yes i'm sure, I've had the same problem as you did. you need to keep trying.
so did you fix it?
If you are talking to me, yes I did manage to fix it and flash C7. But I want stock ROM back, anyone have the files and directions?
Now the phone wont boot into S/W mode and wont power unless powered on after my pc froze during the update

[Q] Atrix 2 won't boot past "M" Motorola logo

Hey guys,
Forgive me for being frantic and (probably) not taking the steps needed to research this issue, or not taking the time to do so, but I'm sure you can all presumably imagine -if you've not been in this situation before- that it SUCKS not having a phone in this day in age...
My problem: Atrix 2 (Rooted + CWM Recovery) now won't boot passed the "M" Motorola logo upon start up. It won't even allow me to access the factory Android Recovery by holding down Volume Up, Volume Down, and Power. I think I inadvertently bricked the phone? (Hope not!)
Further, the "M" Motorola logo is skewed in appearance, like its not even loading correctly. I'm not sure what to do. This is my first time rooting and getting experienced with custom ROMS.
Anyone able to help this helpless sap?
Thanks is advance to your replies...
Step 1 is where you tell what you did to get into the state you are in. You wouldn't believe how far it goes toward fixing something if you know how it got broken.
Sent from my MB865 using XDA
If you have CWM recovery on boot can't you just do a battery pull? You do NOT want to let that thing bootloop forever until the battery dies.
The End.
KEB64 said:
If you have CWM recovery on boot can't you just do a battery pull? You do NOT want to let that thing bootloop forever until the battery dies.
The End.
Click to expand...
Click to collapse
Agreed pull the battery. If you run out of juice you'll be in some serious trouble.
Did you try to flash the fkz? Unless you have CWM on Boot it's the only way you can get your phone working.
Okay, sorry for not giving a full rundown on what stupidity on my part cause all of this. Let me start by saying that (sadly) I am a great big n00b when it comes to Linux, and I thought that despite my research online I would sort of explore the CWM Recovery 'Advanced' sections.
I downloaded ROM Toolbox from the Play Store, and installed a custom boot animation, and replaced -or thought I was- the startup "M" logo with something else. This is what concerned me: After re-booting, the "M" logo was all crazy looking, with a "stretched" "M" logo over the top of the "regular" logo.
So, I uninstalled the app, but the logo was still all messed up. So, I used Root Uninstaller to get rid of the ROM Toolbox files, still no resolve to the crazy boot logo.
So, I went into CWM Recovery Advanced, and wiped everything. The Dalvik, cache, System, Data, etc... didn't think that it would -what appears to have happened- wipe out the OS on the phone.
I tried pulling the battery, and re-booting, won't boot passed the skewed "M" logo still. Tried getting into Android Recovery, and it looks to go through the recovery goes through its thing, but never boots normally afterward.
Sorry for being such an idiot, I really shouldn't have messed with this while half asleep, and again I can't apologize enough for being such a stupid n00b.
I can attach an image of the boot logo if that helps, but I'm worried I am just S.O.L. at this point...
Also, not sure what an FKZ is. I tried to install a 2.3.6 apk file to my wife's SD card on her phone and booting from the file after putting the SD card into mine. Still nothing.
pull the battery, put it back in, and hold vol up and down while turning on. choose ap fastboot at the menu. go to the thread in my signature and under the mirrors there is also a download of the return to stock script. run it while in fastboot and plugged in with usb. DO NOT pull the chord until it is done. when it is you should be good.
Apex_Strider said:
Okay, sorry for not giving a full rundown on what stupidity on my part cause all of this. Let me start by saying that (sadly) I am a great big n00b when it comes to Linux, and I thought that despite my research online I would sort of explore the CWM Recovery 'Advanced' sections.
I downloaded ROM Toolbox from the Play Store, and installed a custom boot animation, and replaced -or thought I was- the startup "M" logo with something else. This is what concerned me: After re-booting, the "M" logo was all crazy looking, with a "stretched" "M" logo over the top of the "regular" logo.
So, I uninstalled the app, but the logo was still all messed up. So, I used Root Uninstaller to get rid of the ROM Toolbox files, still no resolve to the crazy boot logo.
So, I went into CWM Recovery Advanced, and wiped everything. The Dalvik, cache, System, Data, etc... didn't think that it would -what appears to have happened- wipe out the OS on the phone.
I tried pulling the battery, and re-booting, won't boot passed the skewed "M" logo still. Tried getting into Android Recovery, and it looks to go through the recovery goes through its thing, but never boots normally afterward.
Sorry for being such an idiot, I really shouldn't have messed with this while half asleep, and again I can't apologize enough for being such a stupid n00b.
I can attach an image of the boot logo if that helps, but I'm worried I am just S.O.L. at this point...
Also, not sure what an FKZ is. I tried to install a 2.3.6 apk file to my wife's SD card on her phone and booting from the file after putting the SD card into mine. Still nothing.
Click to expand...
Click to collapse
Yeah wiping the system partition is a no no unless you flash another rom afterwards. Do like ikrasner says and you should be back to normal.
Sent from my MB865 using XDA
Thanks for all the help guys, I really hope that something positive comes about this... though, to go without mention, I certainly need more knowledge on WTH I am doing to my phone: understanding flashing ROMS, what dangers come with rooting, and a vast array of other "all things root" that I need to learn up on.
I will try to install from SD card the 2.3.5 zip tonight, but will it (the phone) look for the newest 2.3.6 OTA update and try to ask me to install? How does that work after rooting, will I re-brick my clearly bricked phone all over again?
As always, thanks for all your replies in advance -you guys really know what's going on here!
can you read chinese?
Maybe I can solve your question,but poor of my english.
and what is your phone type?
at&t hktw or china ?
Sent from my ME865 using xda premium
Apex_Strider said:
Thanks for all the help guys, I really hope that something positive comes about this... though, to go without mention, I certainly need more knowledge on WTH I am doing to my phone: understanding flashing ROMS, what dangers come with rooting, and a vast array of other "all things root" that I need to learn up on.
I will try to install from SD card the 2.3.5 zip tonight, but will it (the phone) look for the newest 2.3.6 OTA update and try to ask me to install? How does that work after rooting, will I re-brick my clearly bricked phone all over again?
As always, thanks for all your replies in advance -you guys really know what's going on here!
Click to expand...
Click to collapse
It should ask you to install 2.3.6. Just go into setting>about phone>check for updates. Or you could go and install one of the roms that are based on 2.3.6 such as Lithium Sonya or SCv5.
Okay gang, perhaps I'm just certifiably dumb, or I am simply just not doing this correctly. I downloaded the "Returntostock2.3.5.script" zip file and copied it to my wife's SD card to 'apply update from sdcard' option from the Android Recovery area by holding Vol Up, Vol Down, & Power buttons. What I got was this:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
I tried to just plug the USB into the phone and run the 2.3.5. script from there. but again- I'm stuck in the crazy skewed "M" logo startup screen with nothing following. That's all the phone will do at this point, other than my getting into Android Recovery.
I'm not sure how or what fastboot is, or how it works. If the phone is plugged into the USB, it will only boot the stupid screwed up "M" logo screen. Noting else.
Apex_Strider said:
Okay gang, perhaps I'm just certifiably dumb, or I am simply just not doing this correctly. I downloaded the "Returntostock2.3.5.script" zip file and copied it to my wife's SD card to 'apply update from sdcard' option from the Android Recovery area by holding Vol Up, Vol Down, & Power buttons. What I got was this:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
I tried to just plug the USB into the phone and run the 2.3.5. script from there. but again- I'm stuck in the crazy skewed "M" logo startup screen with nothing following. That's all the phone will do at this point, other than my getting into Android Recovery.
I'm not sure how or what fastboot is, or how it works. If the phone is plugged into the USB, it will only boot the stupid screwed up "M" logo screen. Noting else.
Click to expand...
Click to collapse
do not flash this. unzip it on your computer, choose to boot into fast boot in the same place you chose recovery, then run the .bat file that was in the zip.
Sent from my MB865 using XDA
What that file does is reflash your system.img, basically restoring your phone to factory default. And just as a sidenote you cannot flash things with the standard Android Recovery. You need CWM.
did you try apboot mode and ise fastboot to flash system.img ?
Sent from my ME865 using xda premium
Still not working... not sure how to flash from fastboot. I don't have any options to run a file from there, or at least not sure ow to go about that.
Fastboot sample, hope will help you.
http://bbs.gfan.com/mobile/android-3701449-1-1.html
Sent from my ME865 using xda premium
dickluo said:
Fastboot sample, hope will help you.
http://bbs.gfan.com/mobile/android-3701449-1-1.html
Sent from my ME865 using xda premium
Click to expand...
Click to collapse
So, if I'm looking at this correctly, I need to open command prompt from my computer, and type the commands in from there?
I don't think my computer is recogzining the phone in any way, as I cannot get into the 'manage usb connections' options.
If I have the 2.3.5.script downloaded on my desktop, and l plug my phone in after launching AP Fastboot on the phone, will the computer know where to flash the file to?
I know, I'm a dolt... please bear with me, I really need to get this thing working again -I feel naked without my phone!
Apex_Strider said:
So, if I'm looking at this correctly, I need to open command prompt from my computer, and type the commands in from there?
I don't think my computer is recogzining the phone in any way, as I cannot get into the 'manage usb connections' options.
If I have the 2.3.5.script downloaded on my desktop, and l plug my phone in after launching AP Fastboot on the phone, will the computer know where to flash the file to?
I know, I'm a dolt... please bear with me, I really need to get this thing working again -I feel naked without my phone!
Click to expand...
Click to collapse
Before using the restore script you need to install the usb drivers for your mb865, you can get those from here: http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/MotoHelper_2.1.40_Driver_5.5.0.exe
Next unzip the Return to Stock 2.3.5 Fastboot SCRIPT.zip to anywhere you like in your pc (example: C:\RestoreScript\ )
Next connect your phone with the usb cable to the pc and get into fastboot mode for this in your phone press volume down + volume up + power it should appear a screen with some options, use the volume down key of your phone to navigate through the menu until you see the Fastboot option, then enter by pressing the volume up key, this will show you some messages and the finally it should said usb connected.
Then open the folder where you extracted the Return to Stock 2.3.5 Fastboot SCRIPT files and search a .bat file call "Stock Restore" then run the file (double click on it) and it should open a command promt screen with some instructions if the phone is connected correctly and you installed the drivers correctly then in some point the screen will show you the id of your device and it will wait you to press the enter key to start the proccess, press key enter wait all the proccess until the program said to you its finished, after that it will reboot your phone and install the stock 2.3.5 when it boots up you should see the android logo and a progress bar filling up.
when it's done wait the reboot and your phone should be ok.
hope this helps.
jfrank1485 said:
Before using the restore script you need to install the usb drivers for your mb865, you can get those from here: http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/MotoHelper_2.1.40_Driver_5.5.0.exe
Next unzip the Return to Stock 2.3.5 Fastboot SCRIPT.zip to anywhere you like in your pc (example: C:\RestoreScript\ )
Next connect your phone with the usb cable to the pc and get into fastboot mode for this in your phone press volume down + volume up + power it should appear a screen with some options, use the volume down key of your phone to navigate through the menu until you see the Fastboot option, then enter by pressing the volume up key, this will show you some messages and the finally it should said usb connected.
Then open the folder where you extracted the Return to Stock 2.3.5 Fastboot SCRIPT files and search a .bat file call "Stock Restore" then run the file (double click on it) and it should open a command promt screen with some instructions if the phone is connected correctly and you installed the drivers correctly then in some point the screen will show you the id of your device and it will wait you to press the enter key to start the proccess, press key enter wait all the proccess until the program said to you its finished, after that it will reboot your phone and install the stock 2.3.5 when it boots up you should see the android logo and a progress bar filling up.
when it's done wait the reboot and your phone should be ok.
hope this helps.
Click to expand...
Click to collapse
jfrank1485,
This stepped me through the entire process without any confusion! Everything is back to normal! Hooray and three Huzzahs!
Also, many many thanks to dickluo, farshad525hou, lkrasner, mtnlion, and KEB64!
You guys really saved my stupid (you know what) on this deal! Next order of business: figure out what the heck I am doing before doing ANYTHING!
Problem solved, my world has regained sanity, and my phone is back to life!
You guys are the best, thank you all so much!!!
Apex_Strider said:
jfrank1485,
This stepped me through the entire process without any confusion! Everything is back to normal! Hooray and three Huzzahs!
Also, many many thanks to dickluo, farshad525hou, lkrasner, mtnlion, and KEB64!
You guys really saved my stupid (you know what) on this deal! Next order of business: figure out what the heck I am doing before doing ANYTHING!
Problem solved, my world has regained sanity, and my phone is back to life!
You guys are the best, thank you all so much!!!
Click to expand...
Click to collapse
I'm glad it work , keep it at hand before doing anything to your phone, it really helps

[Q] Cannot get out of recovery menu

I've gone through all the old posts, tried various suggestions using Odin and the SDK but without success.
My son got his Samsung GT-i5800 locked because he forgot the swipe code. I tried suggestions on forums but no good. So I put the phone into the recovery mode and selected "wipe data factory reset" then selected "system reboot now". The phone then rebooted and arrived back into the recovery menu. Everything I've done has brought me back to "Samsung Recovery Utils for BML"
I've downloaded the SDK manager and tried typing "abd" into the command line but it is not recognised. I've pointed the command line at the tools folder, then the platform-tools folder found the abd application but cannot run any commands. Not that it would do much good anyway as the phone doesn't connect to the PC via USB when in the recovery menu.
I know this problem has been mentioned before but all the suggestions from those posts have not worked. I have now run out of ideas.
I've spent too many hours on this, so before I go buy another phone, does anyone have any other suggestions, please?
thanks.
itsar1 said:
I've gone through all the old posts, tried various suggestions using Odin and the SDK but without success.
My son got his Samsung GT-i5800 locked because he forgot the swipe code. I tried suggestions on forums but no good. So I put the phone into the recovery mode and selected "wipe data factory reset" then selected "system reboot now". The phone then rebooted and arrived back into the recovery menu. Everything I've done has brought me back to "Samsung Recovery Utils for BML"
I've downloaded the SDK manager and tried typing "abd" into the command line but it is not recognised. I've pointed the command line at the tools folder, then the platform-tools folder found the abd application but cannot run any commands. Not that it would do much good anyway as the phone doesn't connect to the PC via USB when in the recovery menu.
I know this problem has been mentioned before but all the suggestions from those posts have not worked. I have now run out of ideas.
I've spent too many hours on this, so before I go buy another phone, does anyone have any other suggestions, please?
thanks.
Click to expand...
Click to collapse
^First of all, there's no such command called as "abd". Also, I'm pretty sure that you probably haven't installed adb properly. Just follow the steps given in the following tut to make it work:
[How To] Setup ADB for Windows/ Mac
And secondy, there's no need to go through all that hassle. Simply pull out your battery. Insert it back and then press the following key combo:
"Vol Down + Home + Power Key". This would take you to the Download mode, now simply flash any stock or custom ROM via Odin. Here's a list of Stock ROMs available for our device:
Galaxy GT-15801 ROM/KERNEL List
h4r5h said:
First of all, there's no such command called as "abd". Also, I'm pretty sure that you probably haven't installed adb properly. Just follow the steps given in the following tut to make it work:
[How To] Setup ADB for Windows/ Mac
Click to expand...
Click to collapse
Thanks for your suggestion. I will give it a go when I get some more time. I was following quite carefully what others had written in posts. I can only assume they missed out a detail that they thought was obvious.
h4r5h said:
And secondy, there's no need to go through all that hassle. Simply pull out your battery. Insert it back and then press the following key combo:
"Vol Down + Home + Power Key". This would take you to the Download mode, now simply flash any stock or custom ROM via Odin. Here's a list of Stock ROMs available for our device:
Galaxy GT-15801 ROM/KERNEL List
Click to expand...
Click to collapse
Sadly I've gone through all that. You are not the first to suggest this. I flashed the rom to the phone, Odin says "PASS" but the phone just reboots back in recovery mode.
It feels like that the phone's equivalent to the bios is telling it to go into recovery mode and not boot up the operating system. So regardless of what ROM is flashed onto the phone, I get the recovery menu. :crying:
Delete boot partition
And reflash...
Hope it will ... or else try purumod ..
Sent from my GT-I5800 using xda premium
If u were on stock rom initially then u can always get help from Samsung service center
Secondly if u have cwm recovery u can install rom or update.zip through cwm itself
Also
Its surprising that after data wipe such problem appeared did u miss out something
Sent from my GT-I5800 using xda app-developers app

help- bricked it, no recovery, what now?

Hey yall. I had the phone for 6 days before I bricked it. I am wondering if there is any stock recovery mode or anything or what I shsould do? I think something went wrong due to using the root toolbox pro app. I have done some backups within the ap as well as Titanium Backup but now the phone will not boot up and I dont know if/how to put it in factory recovery mode. Soft reset does nothing. The Motorola logo will show on startup but then the screen just blacks out forever, not off, just colored black.
A few details, the phone was rooted with Motofail2go, with no recovery and bootloader still locked as far as I know.
Should I take it to Sprint for a factory reset? Is this even an option? What are my other options?
Next time I will probably use the Moto unlock key so I can open the bootloader all legit like and have a recovery mode...
Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Once unlocked flash the custom recovery of your choice (I like twrp). You can boot into custom recovery by holding volume up and the power button from a powered down state. Here is the link for instructions on how to flash twrp:
http://forum.xda-developers.com/showthread.php?t=1887070
Then you can download one of the stock backups for the Q posted in the development section and restore them using the custom recovery. Most of the ones I have seen have been compatible with twrp.
The only way to download the stock rom backups is to remove the sd card from your phone, plug your sd card into a PC or other device with a card reader, download the stock backups, and place the stock backup rom files on your sd card. Finally place the sd card with the stock backup downloads into your phone.
These backups and information on how to go through this process can be found in this thread on page 2: http://forum.xda-developers.com/showthread.php?t=2001226
The key is to make a backup of your existing rom with twrp and then move the stock backups from your sd card to the twrp/backups/yourdeiceserial/ directory. That creates a backup directory which twrp knows to look for backups in.
Don't feel bad, I've been in that state several times since getting the Q, live and learn.
Sent from my XT897 using xda app-developers app
UnicronAlpha99 said:
Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Once unlocked flash the custom recovery of your choice (I like twrp). You can boot into custom recovery by holding volume up and the power button from a powered down state. Here is the link for instructions on how to flash twrp:
http://forum.xda-developers.com/showthread.php?t=1887070
Then you can download one of the stock backups for the Q posted in the development section and restore them using the custom recovery. Most of the ones I have seen have been compatible with twrp.
Don't feel bad, I've been in that state several times since getting the Q, live and learn.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
If that does not work you could drop it in water or something. You have not officially unlocked boot loader so you still have warranty. Or you could just tell sprint it quit working and act completely clueless. At least its bricked with warranty still intact.
matt2k12 said:
Hey yall. I had the phone for 6 days before I bricked it. I am wondering if there is any stock recovery mode or anything or what I shsould do? I think something went wrong due to using the root toolbox pro app. I have done some backups within the ap as well as Titanium Backup but now the phone will not boot up and I dont know if/how to put it in factory recovery mode. Soft reset does nothing. The Motorola logo will show on startup but then the screen just blacks out forever, not off, just colored black.
A few details, the phone was rooted with Motofail2go, with no recovery and bootloader still locked as far as I know.
Should I take it to Sprint for a factory reset? Is this even an option? What are my other options?
Next time I will probably use the Moto unlock key so I can open the bootloader all legit like and have a recovery mode...
Click to expand...
Click to collapse
Both of the methods above are very effective. When I had the first photon I bricked it and just dropped it in water and did a claim. Depending on the insurance you have that way may cost you $100. The other method should work. When I first got this phone I did the exact same thing and to go back and unlock then flash twrp and in stall a stock backup someone had posted.
Sent from my XT897 using Tapatalk 2
UnicronAlpha99 said:
Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Click to expand...
Click to collapse
Thanks for the response. Is there anything extra extra special about getting into factory fastboot mode? I can't seem to get it done. Is there an official set of instructions anywhere? Does the phone need to be plugged into the PC? It was always my understanding (for the last week) that Power and Vol Down was the soft reset mode which reboots the phone. Therefore it always tries to reboot in normal mode. This is what keeps happening. It never powers completely down using this method.
Anyhow, once I follow your instructions, the Moto logo appears, no Sprint logo appears, the phone "powers on" but the screen is blacked out (not off). After waiting for a while at the blank/black screen, or holding down several buttons like vol or camera I get the first attachment: "Process system is not responding. Would you like to close it?" When I wait nothing happens. When I push OK nothing happens. By chance, I held down power during the notification and the power menu came up behind the ANR notice (second/third attachments). So obviously there are some things working but the main system isn't booting up. And either factory fastboot is nuked or I can't figure it out. When I power down from this accessible power menu and try to do the fastboot (Power / Vol Down) I still havent gotten it to work.
Any other ideas before I take drastic measures?
Since I bought it from Amazon would that be my best route for return or should I go thru a Sprint store?
Thanks in advance.
Hi again yall. You know once I got to thinking about it, I decided to check out the return policy on Amazon Wireless. They will accept any device under warranty for the first 30 days and it is up to Moto for the next 11 months of warranty coverage. They email me a packing label and it ships out 1 day and they ship out the new phone 1 day shipping. Hard to beat, just takes 2 days of shipping and some more fun times with my Epic, 10.1CM style, in the meantime.
Who's to say it wasnt some sort of hardware or software glitch that bricked the phone rather than my screwing around? Nobody knows and it isn't up to the consumer to prove his innocence. I bought everything legally, all the apps at the app store, and only ran the motofail2go root method. Wasn't running any custom Roms, Mods, or anything. I don't feel bad after they got me for another 2 grand for 24 months, and since I have been with Sprint for 10 years;l I have spent well over 10k or 15k with them lifetime.
If any other method pops up between now and when I ship it out I may give it a shot but if not, ah well, capitalism.
matt2k12 said:
Thanks for the response. Is there anything extra extra special about getting into factory fastboot mode? I can't seem to get it done. Is there an official set of instructions anywhere? Does the phone need to be plugged into the PC? It was always my understanding (for the last week) that Power and Vol Down was the soft reset mode which reboots the phone. Therefore it always tries to reboot in normal mode. This is what keeps happening. It never powers completely down using this method.
Anyhow, once I follow your instructions, the Moto logo appears, no Sprint logo appears, the phone "powers on" but the screen is blacked out (not off). After waiting for a while at the blank/black screen, or holding down several buttons like vol or camera I get the first attachment: "Process system is not responding. Would you like to close it?" When I wait nothing happens. When I push OK nothing happens. By chance, I held down power during the notification and the power menu came up behind the ANR notice (second/third attachments). So obviously there are some things working but the main system isn't booting up. And either factory fastboot is nuked or I can't figure it out. When I power down from this accessible power menu and try to do the fastboot (Power / Vol Down) I still havent gotten it to work.
Any other ideas before I take drastic measures?
Since I bought it from Amazon would that be my best route for return or should I go thru a Sprint store?
Thanks in advance.
Click to expand...
Click to collapse
Try using adb. If your computer has drivers on it for phone you might able to get into fast boot. If that does not work I would try Sprint store first. Have locked my phone up several times while hacking wife off in progress and have used adb every time. Only time i have been truely scared is when i soft bricked my nexus 7. had to stay at work for two hours after i got off to get it to recover because i was scared of her lol.
---------- Post added at 02:05 PM ---------- Previous post was at 01:57 PM ----------
If you get adb to recognize device you could take chance and officially unlock boot loader. Then flash twrp. There is a thread in general section about having trouble getting official update. It has a stock recovery in it. Trick would be moving files to recovery section of twrp
I have gotten the phone to soft power down and get into fast boot and custom recovery. It's a bit tricky with timing, I usually wait for the screen to go black after soft reset, let go, and immediately hold power and volume down. If you can not boot into fastboot I honestly don't know what you can do either than return the phone.
Sent from my XT897 using xda app-developers app
UnicronAlpha99 said:
I have gotten the phone to soft power down and get into fast boot and custom recovery. It's a bit tricky with timing, I usually wait for the screen to go black after soft reset, let go, and immediately hold power and volume down. If you can not boot into fastboot I honestly don't know what you can do either than return the phone.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help Unicron. I think Brandons method might be my only alternative... but you know what? I already have the box packed up to ship back to Amazon! I am still a noob; I dunno if I could go the distance on this one. I have been updating my Android SDK files since I got the phone but I never got it to recognize boot up thru ADB fastboot. disclaimer* I havent tried it in a couple days since all teh SDK updates completed.
I dunno though I am a big time DIYer when possible. If it werent for the massive amount of tape I put on the box and packing label I would already be trying this method. I can't convince myself just yet. Amazon makes it too easy. I could have the *new* phone by Friday. Then I wouldn't be wasting my remaining work week trying to hack into my personal Christmas present in order to make it function...........................................
Edit - Yes I'm impatient. My job is too demanding and I am trying to set a good precedent for 2013. Wasting the first 3 work days on a phone is not how I intend to start off the year. There is probably a valuable lesson to be learned from this as far as hacking experience and to be honest with the responses here I think I could get it to boot up from PC in SDK/ADB mode and go from there. I just didnt know if that was possible until after I made the claim with Amazon. I still have an entire day today and tomorrow if I want to indulge myself. It doesnt matter if I mail the package today or Wednesday, I can still get it by Friday. I believe this thread is still valuable because we have patterns of repeating past failures and I may find use of it when I recieve my new phone and, darn it, it mysteriously bricks as well. in the same fashion.... the only thing I was really trying to do was get all my apps on my SD card... sad huh?
Edit 2 - Opened up the box, tried fastboot and adb, nothing. Off she goes.
I don't blame you, it sounds easier to exchange in your case any way. The main suggestion I have is if you are getting into any type of build.prop or operating system tweaks that have potential to lead to boot loops or cause the phone not to boot, then unlock the bootloader and install custom recovery.
The Moto-fail method seems limited to only be able to run apps that require root. For me this has no use as I want to be able to have complete control over all aspects of the Android OS. There is not a huge mod community for the Q as yet but I believe Cyanogen will be a reality as Interloper continues working on it. I came from an Epic with Cyanogen and soft-bricked it a minimum of 50 times. CWM was very forgiving on that phone, the Q is a lot more finicky and frustrating.
If you have insurance through the carrier then you are going to pay $150 for a refurb if something goes wrong and you hard brick the phone. If you unlock bootloader and install custom recovery then you have a fail-safe in the form of nandroid backups and restores. Then you can mod away with little fear.
Good luck on the new phone and I hope you don't give up after six days of modding with the Q!
Sent from my XT897 using xda app-developers app
matt2k12 said:
Thanks for the help Unicron. I think Brandons method might be my only alternative... but you know what? I already have the box packed up to ship back to Amazon! I am still a noob; I dunno if I could go the distance on this one. I have been updating my Android SDK files since I got the phone but I never got it to recognize boot up thru ADB fastboot. disclaimer* I havent tried it in a couple days since all teh SDK updates completed.
I dunno though I am a big time DIYer when possible. If it werent for the massive amount of tape I put on the box and packing label I would already be trying this method. I can't convince myself just yet. Amazon makes it too easy. I could have the *new* phone by Friday. Then I wouldn't be wasting my remaining work week trying to hack into my personal Christmas present in order to make it function...........................................
Edit - Yes I'm impatient. My job is too demanding and I am trying to set a good precedent for 2013. Wasting the first 3 work days on a phone is not how I intend to start off the year. There is probably a valuable lesson to be learned from this as far as hacking experience and to be honest with the responses here I think I could get it to boot up from PC in SDK/ADB mode and go from there. I just didnt know if that was possible until after I made the claim with Amazon. I still have an entire day today and tomorrow if I want to indulge myself. It doesnt matter if I mail the package today or Wednesday, I can still get it by Friday. I believe this thread is still valuable because we have patterns of repeating past failures and I may find use of it when I recieve my new phone and, darn it, it mysteriously bricks as well. in the same fashion.... the only thing I was really trying to do was get all my apps on my SD card... sad huh?
Edit 2 - Opened up the box, tried fastboot and adb, nothing. Off she goes.
Click to expand...
Click to collapse
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.
befrosty8612 said:
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.
Click to expand...
Click to collapse
Sure wish I would have known that ahead of time. Does this work without any recovery mode and with the bootloader still locked?
matt2k12 said:
Sure wish I would have known that ahead of time. Does this work without any recovery mode and with the bootloader still locked?
Click to expand...
Click to collapse
It does work without any recovery mode and I believe it still works without the bootloader being unlocked, I didn't know about this myself until after I had already unlocked it. Sorry I couldn't help out sooner.
befrosty8612 said:
It does work without any recovery mode and I believe it still works without the bootloader being unlocked, I didn't know about this myself until after I had already unlocked it. Sorry I couldn't help out sooner.
Click to expand...
Click to collapse
Awesome, I am wanting to do the backdoor root method again but, of course, may brick it. I dont think Amazon will keep sending me new ones.... but maybe!
befrosty8612 said:
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.
Click to expand...
Click to collapse
For anyone concerned, I knew it would only be a matter of time until bricking my new device. This damn Root Toolbox Pro did it to me again, and on a simple, menial task. I am going to be working thru the motions on getting this to work.
Using the instructions quoted I did get stock recovery to work or at least flash on the screen for a split second. Seems like there is a timer on the recovery screen. I am having trouble with the fastboot prompt though on the PC. Do I do it in the "platform-tools" folder which contains fastboot or in the "tools" folder of the main SDK directory? I am really a noob, can you give me the cliff notes of how to get into ADB, fastboot, etc on the Photon Q in order to do a factory reset? I already have Android SDK installed and completely up to date so that is done. And Fastboot is installed. I'm just having trouble crossing the finish line here... I can get the fastboot page opened in the stock recovery but from there I'm lost. I dont know what to type into the command prompt, in what directory, or what.... Also when I open the command prompt in the SDK folder on the PC with fastboot in the directory and type "adb reboot bootloader" it says "device not found". Maybe (surely) that is the wrong prompt?
FWIW my phone is showing the dead android guy. I didnt do anything besides try and clear up my Play Store download list which required a reboot. The phone never started back up. I dont know how much damage was done or info was lost or whatever, but seeing as how I was rooted but still locked, I had no custom recovery. So no back ups. Is there anything to restore or am I looking at a full wipe and restore?
matt2k12 said:
For anyone concerned, I knew it would only be a matter of time until bricking my new device. This damn Root Toolbox Pro did it to me again, and on a simple, menial task. I am going to be working thru the motions on getting this to work.
Using the instructions quoted I did get stock recovery to work or at least flash on the screen for a split second. Seems like there is a timer on the recovery screen. I am having trouble with the fastboot prompt though on the PC. Do I do it in the "platform-tools" folder which contains fastboot or in the "tools" folder of the main SDK directory? I am really a noob, can you give me the cliff notes of how to get into ADB, fastboot, etc on the Photon Q in order to do a factory reset? I already have Android SDK installed and completely up to date so that is done. And Fastboot is installed. I'm just having trouble crossing the finish line here... I can get the fastboot page opened in the stock recovery but from there I'm lost. I dont know what to type into the command prompt, in what directory, or what.... Also when I open the command prompt in the SDK folder on the PC with fastboot in the directory and type "adb reboot bootloader" it says "device not found". Maybe (surely) that is the wrong prompt?
FWIW my phone is showing the dead android guy. I didnt do anything besides try and clear up my Play Store download list which required a reboot. The phone never started back up. I dont know how much damage was done or info was lost or whatever, but seeing as how I was rooted but still locked, I had no custom recovery. So no back ups. Is there anything to restore or am I looking at a full wipe and restore?
Click to expand...
Click to collapse
As abnormal as it seems, your situation seems pretty normal... at least from my shoes. I went through the same scenario... I didn't know what adb was, or fastboot, etc. So, here's what I know
the fastboot commands work even if adb doesnt see it in the list of devices attached. Somehow it just works (as long as the phone is in fastboot mode).
If you're able to get to the fastboot mode, things should be okay. Just open a windows explorer window to the Platform-Tools, hold the shift key and right click on a blank space within the window, then click open command window here.
you should be able to pass any adb (if the phone is on and recognized) or fastboot (if phone is in fastboot mode) commands from that command prompt.
Also, if you have a stock recovery, CMW, or TWRP image, this is the folder to copy those .img files to. Once you get your phone into fastboot mode and its plugged into the computer, just type into the command prompt:
Code:
fastboot flash recovery recovery.img
If you're just looking to reboot the phone into recovery
If you have a CWM or TWRP recovery just replace the recovery.img with whatever the .img file that you have. Also, as a tip instead of writing the entire file name, just press the first couple letters then press the tab key within the command prompt, it should fill in the rest. keep pressing tab until you get to the .img file name you want.
To avoid doing this again, maybe I can help... what were you trying to do to begin with? From the sound of it, you were trying to root the phone with the Root Toolbox Pro but it bricked, and then you tried to reboot into recovery and then got the red android... ?
befrosty8612 said:
As abnormal as it seems, your situation seems pretty normal... at least from my shoes. I went through the same scenario... I didn't know what adb was, or fastboot, etc. So, here's what I know
the fastboot commands work even if adb doesnt see it in the list of devices attached. Somehow it just works (as long as the phone is in fastboot mode).
If you're able to get to the fastboot mode, things should be okay. Just open a windows explorer window to the Platform-Tools, hold the shift key and right click on a blank space within the window, then click open command window here.
you should be able to pass any adb (if the phone is on and recognized) or fastboot (if phone is in fastboot mode) commands from that command prompt.
Also, if you have a stock recovery, CMW, or TWRP image, this is the folder to copy those .img files to. Once you get your phone into fastboot mode and its plugged into the computer, just type into the command prompt:
Code:
fastboot flash recovery recovery.img
If you're just looking to reboot the phone into recovery
If you have a CWM or TWRP recovery just replace the recovery.img with whatever the .img file that you have. Also, as a tip instead of writing the entire file name, just press the first couple letters then press the tab key within the command prompt, it should fill in the rest. keep pressing tab until you get to the .img file name you want.
To avoid doing this again, maybe I can help... what were you trying to do to begin with? From the sound of it, you were trying to root the phone with the Root Toolbox Pro but it bricked, and then you tried to reboot into recovery and then got the red android... ?
Click to expand...
Click to collapse
Thanks for the response. So, all I have to do is: go to fastboot and flash a stock recovery image file and it will automatically wipe the phone, cache, everything, and restore the operating system? Sounds awfully easy! I found some stock files in this post : http://forum.xda-developers.com/showthread.php?t=2001226&page=2 Are these the ones you used before?
Last question: I can flash CWM or TWRP but wont be able to access them if my bootloader is locked, correct? So flashing a stock recovery will allow me to have my stock phone back again, locked and un-rooted? I guess if I cant get it to work with the stock recovery then I can unlock the bootloader and do a CWM or TWRP recovery and then flash the stock .img files?
Thanks again for your help. I already had root with the motofail2go method which I like using but seems like when I try and use some generic root feature from apps from the app store that it will crash/brick the phone cuz obviously those apps are generalized and likely to brick certain percentage of devices....
Ok what does this mean? Something with the bootlaoder obviously. Does it need to be unlocked?
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
y qrecovery1.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (5962 KB)...
OKAY [ 0.479s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.755s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
And on the phone screen it says "invalid image size for partition recovery" twice for both times I tried this method.
You will need to flash the system image as well if you want those, as the recovery image will only flash the recovery. The files in that link are for twrp only... so you'll have to be able to get there first.
With the custom recoveries, I'm not 100% sure whether or not you will be able to use them without being unlocked. I would wait to see if anyone else can answer that question for you, but if you did try it without an unlocked bootloader, you at least have the stock recovery to fall back on if needed.
Sent from my XT897 using xda app-developers app
---------- Post added at 09:16 PM ---------- Previous post was at 09:12 PM ----------
I'm thinking it could either be that your phone is full and the image you're flashing is too large to fit on the space available...
Or you're trying to flash custom software on a locked phone.
Hopefully someone is able to answer that a little better...
Sent from my XT897 using xda app-developers app
You can't alter the stock recovery (flash a custom recovery like twrp or cwm) in fastboot without having the bootloader unlocked. Your options are to unlock your bootloader, flash custom recovery, create a backup of your current setup, download one of the stock working backups, place it in the backups folder for twrp on your external sd card, and restore one of the known working backups in the development section (befrosty linked to one). Or you could use RSD lite to return to stock using a stock factory firmware flash. That involves connecting your phone to your PC and flashing the phone back to factory stock. Information on RSD Lite and links to the FXZ's can be found here.
http://forum.xda-developers.com/showthread.php?t=2095536
Sent from my XT897 using xda app-developers app

[Completed] trying to put CWM on a p500

hello all, I'm really new to rooting and I'd like it if you could help me out here, this is about trying to get a CWM working on the smartphone p500. It's a new phone, I just put in the battery out of the package.
okay, so I've just rooted my p500 (root checker said it was indeed rooted), and I'm at a loss here. no matter what I try, I can't get CWM working. the first step I took was to try it via Rom manager. It got stuck at 100 % download, roughly the same problem as in this post
So I tried to get twrp, and got to this tutorial. I tried to put in the command "adb reboot bootloader". It appears as though this just shut down my phone, which would then display a "charging" symbole, since it's still charching via the USB. After putting in the next command; "fastboot flash recovery twrp.img", the command prompt returns "waiting for device", leading me to believe the phone has just shut down.
I tried to search the internet for another way to get in fastboot mode, but all I could find were threads about unbricking the p500 *after* booting in to fastboot mode. which should help, once I get there. This appears not to be an option, either.
After some more searching, I came across this post, detailing how to flash a custom recovery mod. Since I'm already rooted, I got as far as part III, step 5. step 6 is rebooting in recovery mode by pressing and holding volume down + home + power button. I've tried this while the phone is off and while it is on, but all it does is rebooting. Then, in this post, I read you need a custom recovery in order to boot in recovery mode.
Having come full circle, I've exhausted all my options. l've probable misunderstood several directions, or I have overlooked something fairly obvious. Can anyone help me?
Hi there,
You'd be best served asking for help from the experts who own your device here:
Optimus One, P500, V Q&A, Help & Troubleshooting
[FAQ] General FAQs + Quick guide to rooting/flashing roms [20 JAN 13]
Good luck

Categories

Resources