Related
Hi there
I've unfortunately gotten a faulty devices and I'm suppose to get it switched with a new device. (another story about not being able to make calls, scrathing sound etc)
I've rooted my phone and it worked flawlessly, but today I wanted to un-root and would install the apps i've removed with root explorer. Therefore I downloaded a system/ dump and tried restoring the "app" directory in system/ with root explorer. This resulted in random force closes
Then I used "adb" su to copy all the app files from sdcard (where I copied the files from the dump) to the system/app directory. After a while it was done and I type reboot... [Bricked?]
Now the phone keeps rebooting. Getting the LG logo with sound and afterwards the LG logo with progress bar... then rebooting...
I need help
djkoch said:
Hi there
I've unfortunately gotten a faulty devices and I'm suppose to get it switched with a new device. (another story about not being able to make calls, scrathing sound etc)
I've rooted my phone and it worked flawlessly, but today I wanted to un-root and would install the apps i've removed with root explorer. Therefore I downloaded a system/ dump and tried restoring the "app" directory in system/ with root explorer. This resulted in random force closes
Then I used "adb" su to copy all the app files from sdcard (where I copied the files from the dump) to the system/app directory. After a while it was done and I type reboot...
Now the phone keeps rebooting. Getting the LG logo with sound and afterwards the LG logo with progress bar... then rebooting...
I need help
Click to expand...
Click to collapse
Try to hard reset, turn off your phone press volume - and power.
Thanks for the response... When I press power+volume down, the "unpacking box with android person" appears for a 20 seconds or so... the reboots and I'm back to rebooting constantly
When I try pressing volume down and home key/returnkey I can get in to S/W update mode, but I cant get the ADB to work?
Other suggestions?
That's why its a bad idea to delete stock apps in the first place when we don't have custom recovery yet.
gensplejs said:
That's why its a bad idea to delete stock apps in the first place when we don't have custom recovery yet.
Click to expand...
Click to collapse
It wasnt a problem when deleting them, and the phone was alright... it was when restoring through ADB it went wrong... I need a suggestion to get it fixed not an "I-told-you-so"
Yeah... sorry... i was kinda an ass.
But sadly I'm all out of ideas.
Maybe if we had a service manual (not user manual)
Sent from my LG-P990 using XDA Premium App
Can you connect to phone by adb?
You need to clear dalvik cache.
Hi Doc
No... unfortunately I cant get ADB to work....
I can get into S/W update mode, but ADB doesnt work. I can get the Factory reset to begin too, but it just gets into the reboot circle again.
If there was just a way to get into ADB mode I could push every single file again
Damn... I hope it isn't bricked for good
If HR doesn't work. Just return for warrenty.
Cause if it reboots that a corrupted boot.img
Try to see if you can get alist of apps installed on phone.
If superuser.apk is not in there, return it for warrenty.
In one of the reboots I think I had a glimse of a connection thru ADB acouple of times. I had approx. 10 seconds before rebooting again.
Did a list... and guess I saw a dir called "root" but didnt have time to get into the system/app directory...
If we can't find a solution I think I'll try to return the phone and hope for a new one without any question asked
Have you tried putting it in sw update mode and running the LG update tool?
http://www.lg.com/dk/support/mc-support/mobile-phone-support.jsp?countryCd=dk
Might do the trick
Yes I've tried the LG update tool. It says it has a new update, but the current firmware version doesn't show, and when I'm trying to do the update It aborts and says that the phone cannot be updated...
I just tried the Factory Reset and you can abort the reset when the "unpacking box" is showing by pressing the home key. Then you get into the 3e recovery menu... But there no way to select an option. Would have tried to wipe cache partition and data/factory reset. In the text it only says "formatting DATA:..., Formatting CACHE:..., Formatting MISC:..."
djkoch said:
Yes I've tried the LG update tool. It says it has a new update, but the current firmware version doesn't show, and when I'm trying to do the update It aborts and says that the phone cannot be updated...
I just tried the Factory Reset and you can abort the reset when the "unpacking box" is showing by pressing the home key. Then you get into the 3e recovery menu... But there no way to select an option. Would have tried to wipe cache partition and data/factory reset. In the text it only says "formatting DATA:..., Formatting CACHE:..., Formatting MISC:..."
Click to expand...
Click to collapse
There in no way to restore you phone now because we don't have any tools that's work with optimus 2x.
Bring it back to retailer and say that phone is just not booting and you want a replacement.
Edit: Well... discount the advice below for the time being... I've found myself in the same position and the commands below don't work.
My phone is also now useless...
I replied to your thread over at MoDoCo, and although the thread has gone off track it does have Paul's attention.
djkoch said:
Yes I've tried the LG update tool. It says it has a new update, but the current firmware version doesn't show, and when I'm trying to do the update It aborts and says that the phone cannot be updated...
I just tried the Factory Reset and you can abort the reset when the "unpacking box" is showing by pressing the home key. Then you get into the 3e recovery menu... But there no way to select an option. Would have tried to wipe cache partition and data/factory reset. In the text it only says "formatting DATA:..., Formatting CACHE:..., Formatting MISC:..."
Click to expand...
Click to collapse
Oh dear.
I tend to agree, whilst it will be recoverable it could be very time consuming.
A factory reset will wipe cache and dalvik cache, so that's not your problem.
Neither is boot.img your problem, that will be intact.
However, if you can't get a console (via adb or terminal) you're in a difficult position.
Try issuing the 'stop' command in your brief adb window to see if you can preserve the shell.
Code:
$ su
# stop
If you can then try and mount /system rw
If you can do that then you can possibly self recover... by carefully and selectively adding files to /system/app/, rebooting and trying, again and again.
Hey guys!
I've been having a lot of problems with a Samsung Galaxy S Plus recently. After my girlfriend entered the wrong picture password a number of times in a row, the phone locked down. I tried to activate data connection using the power menu (hold power button), which I had deactivated before it locked down. My attempts to log in failed when the device returned either 'invalid username' or 'invalid password' (they are - of course - neither). This is apparently a known problem. I then followed the following instructions to trick the device into thinking the google account had been verified: droidwiki .de/Muster_vergessen#Muster_l.C3.B6schen (warning, that site is in German). For this I successfully managed the following steps:
1.) Installation of ADB tools
2.) Installation of ClockwordMod using Odin in order to accomplish the ...
3.) Activation of USB debugging.
4.) Rooting the phone using these instructions: androiddrole .com/how-to/how-to-easily-root-samsung-galaxy-s-plus-i9001
All these steps worked as expected. Then however, the trouble started: When trying to set the number of failed pattern attempts to 0, the following command failed: "cd /data/data/com.android.providers.settings/databases" ("can't cd to /data/data/com.android.providers.settings/databases"). Additionally I could no longer boot into android as the phone kept booting directly into CWM (This is apparently also a known problem). I proceeded to install a newer version of ClockworkMod Touch (using zip on sd card) hoping this would allow me to break the loop. It didnt. So I replaced ClockwordMod with TeamWin Recovery Project (TWRP). This did finally allow me to exit the recovery mode only to get stuck in a full-out reboot loop: Samsung logo -> black screen -> Samsung logo -> black screen. In order to get out of this reboot loop I used Odin to flash boot_loader.tar and the original version of ClockwordMod onto the device. After a number of failed attempts this suddenly worked - kinda:
The current situation is this: The phone no longer boots directly into recovery mode (good). It doesnt boot into android either though. It just reboots over and over again - this can be stopped however by using 'Volume Down' + 'Home' + 'Power' to access ClockwordMod.
My hopes of getting my phone unlocked and working as before again are rather slim at this point. I would still like to save my substantial collection of photographs from the media folders on the device, before I wipe the entire thing (or buy a new phone).
Therefore my question to you:
Is it possible to extract the photos (stored in the standard media locations of android 2.3) to a PC using only USB-Debugging/Odin/ClockwordMod (being unable to boot into android)?
I tried to pull the media files using the 'adp pull' command, but I couldnt get it to work (maybe because I didnt get the command or the file-paths correctly). Any suggestions would be GREATLY appreciated.
Solution
Attention: If you want your media files, backup your current state first. Go to backup and restore -> backup. Then do steps written below. Backup will be in CWM folder on your sdcard.
This is called a soft-brick. It's good that you can access download and recovery mode using 3 button combinations. First, download a stock Gingerbread ROM for your device model and put it on your sdcard. Boot into CWM and select Wipe user data -> Yes. Wipe Cache Partition -> Yes. Go to Advanced menu and select Wipe Dalvik cache -> Yes. Now return to previous menu and select install zip from sdcard -> choose zip from sdcard -> select name.of.downloaded.rom.zip -> Yes -> Wait 1-2 minutes to flash -> Wipe user data -> Wipe Cache Partition -> Wipe Dalvik Cache. Then select Reboot system now from main menu, and wait 4-5 minutes for it to boot first time.
DaniTheMan said:
Hey guys!
I've been having a lot of problems with a Samsung Galaxy S Plus recently. After my girlfriend entered the wrong picture password a number of times in a row, the phone locked down. I tried to activate data connection using the power menu (hold power button), which I had deactivated before it locked down. My attempts to log in failed when the device returned either 'invalid username' or 'invalid password' (they are - of course - neither). This is apparently a known problem. I then followed the following instructions to trick the device into thinking the google account had been verified: droidwiki .de/Muster_vergessen#Muster_l.C3.B6schen (warning, that site is in German). For this I successfully managed the following steps:
1.) Installation of ADB tools
2.) Installation of ClockwordMod using Odin in order to accomplish the ...
3.) Activation of USB debugging.
4.) Rooting the phone using these instructions: androiddrole .com/how-to/how-to-easily-root-samsung-galaxy-s-plus-i9001
All these steps worked as expected. Then however, the trouble started: When trying to set the number of failed pattern attempts to 0, the following command failed: "cd /data/data/com.android.providers.settings/databases" ("can't cd to /data/data/com.android.providers.settings/databases"). Additionally I could no longer boot into android as the phone kept booting directly into CWM (This is apparently also a known problem). I proceeded to install a newer version of ClockworkMod Touch (using zip on sd card) hoping this would allow me to break the loop. It didnt. So I replaced ClockwordMod with TeamWin Recovery Project (TWRP). This did finally allow me to exit the recovery mode only to get stuck in a full-out reboot loop: Samsung logo -> black screen -> Samsung logo -> black screen. In order to get out of this reboot loop I used Odin to flash boot_loader.tar and the original version of ClockwordMod onto the device. After a number of failed attempts this suddenly worked - kinda:
The current situation is this: The phone no longer boots directly into recovery mode (good). It doesnt boot into android either though. It just reboots over and over again - this can be stopped however by using 'Volume Down' + 'Home' + 'Power' to access ClockwordMod.
My hopes of getting my phone unlocked and working as before again are rather slim at this point. I would still like to save my substantial collection of photographs from the media folders on the device, before I wipe the entire thing (or buy a new phone).
Therefore my question to you:
Is it possible to extract the photos (stored in the standard media locations of android 2.3) to a PC using only USB-Debugging/Odin/ClockwordMod (being unable to boot into android)?
I tried to pull the media files using the 'adp pull' command, but I couldnt get it to work (maybe because I didn't get the command or the file-paths correctly). Any suggestions would be GREATLY appreciated.
Click to expand...
Click to collapse
I use CM10.2 nightly on my Atrix HD and I stuck in chrome..so I did a powerdown with power and volume buttons. Now my phone boot into flash mode and says "connect USB Data Cable"...I have this screen even when I push volume down + power...how can I do a normal reboot? volume down + power is supposed to display the fastboot menu...I could do a normal reboot from that screen..but it does not appear somehow..plase help me people!
Thanks!
Try fastboot command with adb reboot recovery. Then,wiping cache n dalvik.
Sent from my XT890 using XDA Premium 4 mobile app
huatz84 said:
Try fastboot command with adb reboot recovery. Then,wiping cache n dalvik.
Sent from my XT890 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Will be everything lost (apps, settings, sms..etc.) if I do the wiping?
Only wiping cache/dalvik won't erase everything. Wipe data will be the last resort if wiping cache can't fix
Sent from my XT890 using XDA Premium 4 mobile app
You can hold volume up and down on power up and you'll access the bootmenu. From there you can factory reset, boot recovery, boot fastboot, or boot normally. Once in that menu, volume down scrolls the items and volume up selects crap.
This should also be under Q & A......
skeevydude said:
You can also hold volume up and down on power up and you'll access the bootmenu. From there you can factory reset, boot recovery, boot fastboot, or boot normally.
Click to expand...
Click to collapse
No I can't. And this is my problem. Yesterday I did this..but today..i can't. I push any button and this screen appears. ("connect USB Data Cabel")
Hmmm, that's how I normally access fastboot and recovery mode because my phone likes to be picky about when I press the power button when booting them.
Other than the above suggestion of wiping caches, you could also try to fix permissions (in recovery/advanced).
If nothing up to this point has worked then you'll probably have to lose all your userdata to continue.
Typing "fastboot -w" while on the fastboot screen (from a pc terminal/command prompt) will do a factory reset.
Still nothing, then flash a stock (JB) fastboot and start over.
For the future, you need to install something like Titanium Backup Pro and have it run full backup jobs of your user apps every night...also ensure you have it set to backup the apps external sd data as well (don't wanna lose save games or have to redownload the Real Racing 3/Final Fantasy/any big apps data now do we). That way if you ever have to do a full restart or just a factory reset you'll have all your user apps/data at least. With TB properly set up you can clean flash and be all set up within a half an hour...for me with PAC I clean flash, boot, google setup, navbar setup, stop play sync, TB restore, set up system settings, reboot, profit?
/I really can't give much more help than this with what you've mentioned is wrong. Need moar details.
skeevydude said:
Hmmm, that's how I normally access fastboot and recovery mode because my phone likes to be picky about when I press the power button when booting them.
Other than the above suggestion of wiping caches, you could also try to fix permissions (in recovery/advanced).
If nothing up to this point has worked then you'll probably have to lose all your userdata to continue.
Typing "fastboot -w" while on the fastboot screen (from a pc terminal/command prompt) will do a factory reset.
Still nothing, then flash a stock (JB) fastboot and start over.
For the future, you need to install something like Titanium Backup Pro and have it run full backup jobs of your user apps every night...also ensure you have it set to backup the apps external sd data as well (don't wanna lose save games or have to redownload the Real Racing 3/Final Fantasy/any big apps data now do we). That way if you ever have to do a full restart or just a factory reset you'll have all your user apps/data at least. With TB properly set up you can clean flash and be all set up within a half an hour...for me with PAC I clean flash, boot, google setup, navbar setup, stop play sync, TB restore, set up system settings, reboot, profit?
/I really can't give much more help than this with what you've mentioned is wrong. Need moar details.
Click to expand...
Click to collapse
Thanks man, I'll give it a try!
Hi,
I am really desperate! I turned on my rooted Asus MeMO Pad 7 ME176CX after several months of no use, but apps/services won't load (loads of error messages, all apps/services stopped etc.) like it was obsolete or screwed up. So I unrooted it and the issue got worse!
There is a Asus demo app in the notification bar that disables WIFI and software reset and says to plug in the power adapter (no difference, it won't go away).
1) I copied the necessary files to my memory card (to get rid of the Asus demo app as per other threads) but once I insert the memory card, even though it is recognized, it says no files present.
2) I did a hard reset with Vol - (or +, tried both) and Power but nothing happens (no recovery screen, it just stays black).
3) I removed the battery & waited 10 mins, no difference.
4) I formatted a card to FAT32 and copied the cleardata.zip unzipped files from Asus then rebooted pressing just Power but it just reboots normally like the card is not inserted.
Now basically the tablet shows a few apps (Calendar, Gallery etc.) and nothing else.
I cannot connect to wifi, bluetooth does not work, the memory card says no files present, vol + power does not work, cleardata trick did not work, I cannot send it back under warranty (ex-rooted) ... what else can I do??????
Many thanks!
Reboot into Droidboot (Volume Down + Power IIRC, could be up), boot the Temporary TWRP (http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096), flash ROM
After a few experiments gone wrong I have now bricked the tablet for good (erased all data).
I can ONLY go from the dead droid to 'Android system recovery' which shows:
- reboot
- apply update from ADB
- wipe data
- wide cache
After 'wiping' the only option available is 'Apply update from ADB', so I installed ADB on my Mac and downloaded a few ROMs from the Asus site (even though their page says ME176C not ME176CX, but there is no ME176CX page there).
If I run adb devices from the terminal I see nothing. Only if I select 'Apply update from ADB' on the tablet I see the device from terminal, I believe it opens a bridge to the computer only with this option running. The command 'fastboot devices' never shows anything regardless.
I run 'adb sideload update.zip' (tried with several ROMS) but it always fails AFTER the transfer (either with messages 'status 0' or 'end of footer not 0xFFFF' etc.).
So now I am stuck with adb sideload never working, is there anything else I can do????
boredfish said:
After a few experiments gone wrong I have now bricked the tablet for good (erased all data).
I can ONLY go from the dead droid to 'Android system recovery' which shows:
- reboot
- apply update from ADB
- wipe data
- wide cache
After 'wiping' the only option available is 'Apply update from ADB', so I installed ADB on my Mac and downloaded a few ROMs from the Asus site (even though their page says ME176C not ME176CX, but there is no ME176CX page there).
If I run adb devices from the terminal I see nothing. Only if I select 'Apply update from ADB' on the tablet I see the device from terminal, I believe it opens a bridge to the computer only with this option running. The command 'fastboot devices' never shows anything regardless.
I run 'adb sideload update.zip' (tried with several ROMS) but it always fails AFTER the transfer (either with messages 'status 0' or 'end of footer not 0xFFFF' etc.).
So now I am stuck with adb sideload never working, is there anything else I can do????
Click to expand...
Click to collapse
Well, theres quite a lot of options do recover your tablet, before doing anyhing, if you have access to adb, then you should do: download .17 rom and extract it, after extracting go to META-INF\com\google\android\updater-script and open it with notepad, and remove the first 2 lines, then save, and make the zip file (rename it to update.zip {careful not to make the file "update.zip.zip"}), then put the zip file in adb folder (for me its C:\\adb) and do adb push update.zip /sdcard/ (make sure adb is working) after it finishes pushing, go to bootloader (if not there already) and run temp recovery (twrp or cwm), and then install the zip, then clear dalvik and cache, and reboot, if first reboot doesnt work, reboot again, if it still doesnt work, install update.zip again. Hope i helped, if u have any questions tell me :3
=====
edit
=====
if you really cant get out of recovery theres still a way of fixing your tablet (same problem happend to me today and its fixed), if you already did all the steps above on the download .17 and extracting and changing the file of updater script then its already almost done, to access the bootloader you need to shutdown your tablet, press Power, Vol+ and Vol- at same time, it will go to fastboot, copy the file "droidboot.img" from the update.zip and place it in the adb folder (for me its c:\\adb), then do "fastboot boot droidboot.img" and it should download the img to the tab and boot to droidboot (you need to do this a few times, because 5/1 only 1 goes to bootloader), after booting to droidboot you can easily recover from there, on bootloader you have adb access, which means you can push the update.zip to the tablet (with update.zip in adb folder already, do on cmd, "adb push update.zip /sdcard/") after pushing go to temp recovery and install the update.zip normally after installing. format cache and dalvik, and reboot, if its stuck on logo, shutdown and reboot, if still doesnt work install the update once more by turning your device off and go to bootloader normally, (it works now, because it has the software now, (to enter bootloader press press power + vol-), and load temp recovery and reinstall). i hope i helped
So my Kindle Fire HD 7(2012) is bricked after trying to factory reset CM12.1. I took some advice and tried to run some ADB commands and then ADB says device unauthorized. Since my Kindle is stuck at the TWRP boot screen I cannot accept the RSA key. What should I do?
wizahh101 said:
So my Kindle Fire HD 7(2012) is bricked after trying to factory reset CM12.1. I took some advice and tried to run some ADB commands and then ADB says device unauthorized. Since my Kindle is stuck at the TWRP boot screen I cannot accept the RSA key. What should I do?
Click to expand...
Click to collapse
Reboot into TWRP, select Wipe -> Advanced Wipe, and then check all the boxes and swipe to wipe. At this point, all your system, data, and cache partitions will be completely empty, so you will need to reboot into TWRP again (ignore the warnings about not having an OS installed or root), copy a ROM zip from your PC to the kindle's internal storage, and flash it. Once you have it flashed, you'll be starting with a clean state (much like a factory reset), so you should have the ability to set up the device again once the ROM fully boots and get ADB to work.
monster1612 said:
Reboot into TWRP, select Wipe -> Advanced Wipe, and then check all the boxes and swipe to wipe. At this point, all your system, data, and cache partitions will be completely empty, so you will need to reboot into TWRP again (ignore the warnings about not having an OS installed or root), copy a ROM zip from your PC to the kindle's internal storage, and flash it. Once you have it flashed, you'll be starting with a clean state (much like a factory reset), so you should have the ability to set up the device again once the ROM fully boots and get ADB to work.
Click to expand...
Click to collapse
Device is stuck at the TWRP boot screen so I can't do any of that.