My Samsung Galaxy Player was stuck at a blank screen(it would boot to the samsung logo then the screen would blank[With the backlight still on]) and I tried may things to fix it;
rebooting
reboot+remove SD card
hard reboot (power+vol up)
hard rebbot+clear cache
I was about to wipe the system when I decided to see if it was possible to backup my app data
with adb shell, [my device has usb debugging enabled] so I started up a adb shell and ran 'top'
looked at the stuff running had no idea what any of it was so, I closed 'top' then I found the command 'adb shell bmgr run' that looked like it might help with the backup, so I exited the adb shell so I could run the backup, and as soon as I closed adb shell, my device booted.
no idea why. anyway I'm running titanium backup now (it's been 3 weeks sine the last one)
If you device is having trouble booting try this before you wipe all the data!
BRICKED
HEy there.,
I have a samsung galaxy grand gti9082 and im facing the same problem..
there is a bootloop and i cant enter the recovery mode too.!! what do i do?
PLEASE HELP>>!!
Can you still enter download mode?
Sent from my YP-G1 using xda app-developers app
Related
i rooted my phone today everything was good, until i tried to reset the data usnig ADB, i installed ADB using a guid and after that i used a command like "reboot device" or something,... again after that phone wont turn on again , it stay with sscreen GT-I5800(phone model), phone was working before to use ADB reboot command.
PLZ help me. THank you1
I'm trying my hand at porting a ROM to my device (S4 HTC One X/XL, Evita) and I've gotten as far as the bootscreen, but it hangs there (with the bootanim still running). I'd like to take a look at what's happened on the device, but I can't seem to use adb with it at this point. I've made sure drivers are installed and used multiple USB ports. ADB works in recovery and fastboot works in fastboot, but adb returns Offline when I run adb devices while the phone is sitting at the bootscreen.
Found this on StackExchange: http://android.stackexchange.com/que...-for-debugging
According to some of the replies, it's possible to use adb at boot, so I'm not sure why adb returns offline. I tried running adb logcat while the phone is off and letting it boot, but adb never establishes a connection to the phone. Not sure why it can't. Hopefully it's not another adb driver issue. I've already spent a ton of time getting adb working with this phone while booted/in recovery.
Try this it should capture a logcat of the phone booting up, power off the phone while still connected to the usb and enter the following it should say - waiting for device -
Power on the phone then cross your fingers if all goes well you should capture the logcat to bootlog.txt file in your temp directory.
Code:
adb -d logcat>c:\temp\bootlog.txt
Sent from my PACman GT-i9100 using Xparent ICS Tapatalk 2
AuSSiELaMbChOpS said:
Try this it should capture a logcat of the phone booting up, power off the phone while still connected to the usb and enter the following it should say - waiting for device -
Click to expand...
Click to collapse
Protogon said:
I tried running adb logcat while the phone is off and letting it boot, but adb never establishes a connection to the phone. Not sure why it can't. Hopefully it's not another adb driver issue. I've already spent a ton of time getting adb working with this phone while booted/in recovery.
Click to expand...
Click to collapse
The ROM is 4.2.1-based, so if the USB Debug Whitelist was implemented in that version, that might be the problem. Running adb logcat from power off with a ROM that boots fine reveals that adb starts pretty much as soon as the bootscreen comes on and logcat should start spitting out data just as quickly.
If it's not a whitelist issue, something is preventing even adb from starting on the phone.
This is a problem I too have run into while porting a ROM to my GiONEE Dream D1 (MTK 6589) Device. Have you had any luck?
Wish there was a field in build.prop to say "boot with verbose remote logging"
RickyGoldsmith said:
This is a problem I too have run into while porting a ROM to my GiONEE Dream D1 (MTK 6589) Device. Have you had any luck?
Wish there was a field in build.prop to say "boot with verbose remote logging"
Click to expand...
Click to collapse
Replying to self.
You need to modify the init shipped on your OS and instruct it to start adbd asap.
Protogon said:
I've gotten as far as the bootscreen, but it hangs there (with the bootanim still running). I'd like to take a look at what's happened on the device, but I can't seem to use adb with it at this point.
Click to expand...
Click to collapse
You can try to reboot into a working system right after (e.g. the recovery) and retrieve the last kernel boot messages by:
adb shell cat /proc/last_kmsg > last_kmsg
and then see whether you can figure out what happens by reading this log file
My phone is from chinavasion it is galaxy i8550 WIN clone with lower specs it is mocor droid 2.0.5 with a fake jellybean speadtrum sc6820 it is rooted i connected the phone via adb and reboot into recovery i have stock recovery not cwm and i tried fixing it btw i meessed up my build.prop file but anyways i tried to fix it via adb and i got a permission error and i have a backup of my build.prop tho ...i just gave up and rebooted to recovery and wiped data/factory reset and ofcourse it didnt work but i lost my adb drivers i cant turn on usb debugging so i cant use adb and i dont know how to accesss recovery i keep ending up in the speadtrum factory test where u test phone hardware nothing else please help if u can altho i highly doubt it and also when i used adb to reboot in recovery and used a zip file it would say signature verification failed :crying::fingers-crossed: But i trust in xda please help even to give me the phone combination keys to recovery and that give me a zip that will be accepted PLEASE i only had the phone for a month
What exactly were you trying to fix in your stock recovery? Assuming I understand you correctly?
Sent from my K2_CL using Tapatalk
Fixing
Modding.MyMind said:
What exactly were you trying to fix in your stock recovery? Assuming I understand you correctly?
Sent from my K2_CL using Tapatalk[/QUOT
I just fugured out something the problem occured when i took a backup of my build.prop (original one) from my sd card and replaced it with the one in my system folder and forgot to add permissions to it and i restarted my phone and now its bootlooped. When it happened i tried to fix it before i factory reset my phone and lost access to recovery cuz i use to access it from adb i tried to flash a new one (build file) but i got signature verification failed so i just factory reset and lost my adb drivers so now i cant connect it to my computer to use adb commands to reboot into recovery and idk my combination for recovery it is speadtrum sc6820 .....ps. my phone is rooted and has mocor droid 2.3.5 with 4.2.2 jellybean so u know its a fake jellybean cuz its a cloned phone and i have no cwm :crying:
Click to expand...
Click to collapse
@BenDroid1
You can write the custom recovery to your recovery partition using dd in an android terminal emulator from the play store. You would need to know which partition holds your recovery.
For MY device (your partition is different) it would be as followed in the terminal emulator:
Code:
su
Code:
dd if=/sdcard/customrecovery.img of=/dev/block/mmcblk0p21
/dev/block/mmcblk0p20 is the partition that holds my recovery on my device - yours will be different!
You can also use this method for the boot.img towards the boot partition as well as data to data partition, and so forth.
If you have CWM and you were smart enough to create a backup of your device, then I would write the custom recovery to your recovery partition, boot in to CWM, and restore your device with your backup. Then, reboot, plug device in to your computer, allow the computer to reinstall the drivers and hopefully at this point you should be able to establish connection with adb/fastboot again.
Sent from my K2_CL using Tapatalk
Example 1
Sent from my K2_CL using Tapatalk
Example 2
Sent from my K2_CL using Tapatalk
Cant do that
How do uexpect me to do all of that when everytime i boot my phone the its stuck on the logo and i Dont have cwm ...my phone is bootlooped
BenDroid1 said:
Modding.MyMind said:
What exactly were you trying to fix in your stock recovery? Assuming I understand you correctly?
Sent from my K2_CL using Tapatalk
Click to expand...
Click to collapse
When it happened i tried to fix it before i factory reset my phone and lost access to recovery cuz i use to access it from adb i tried to flash a new one (build file) but i got signature verification failed so i just factory reset and lost my adb drivers so now i cant connect it to my computer to use adb commands to reboot into recovery and idk my combination for recovery it is speadtrum sc6820 .....
Click to expand...
Click to collapse
Because right here according to your quote you mentioned that you resetted your device, lost connection to your adb. Only time you can use ADB is when your phone is running. Only way you can confirm if you lost connection with ADB is if your phone is up and running, you open up command window on pc, then run 'adb devices' and if nothing returns then you have no connection. Otherwise, there is no way to confirm if you lost connection to it. So by your quote above, you made it sound like you got around your bootloop problem but could not connect with using ADB and no longer had CWM on your device.
Try to be more clear next time lol.
Have you tried using fastboot instead of ADB?
Sent from my K2_CL using Tapatalk
Modding.MyMind said:
Because right here according to your quote you mentioned that you resetted your device, lost connection to your adb. Only time you can use ADB is when your phone is running. Only way you can confirm if you lost connection with ADB is if your phone is up and running, you open up command window on pc, then run 'adb devices' and if nothing returns then you have no connection. Otherwise, there is no way to confirm if you lost connection to it. So by your quote above, you made it sound like you got around your bootloop problem but could not connect with using ADB and no longer had CWM on your device.
Try to be more clear next time lol.
Have you tried using fastboot instead of ADB?
Sent from my K2_CL using Tapatalk
Click to expand...
Click to collapse
no i havent and sorrry i ...i will be clearer when i press power plus volme up i get speadtrum factory test where u test phone hardware but no android recovery
Your phone has a bootloader. You need to access your bootloader, select fastboot, plug your device in your pc, open up command window, then type 'fastboot devices'.
If you get your device serial number returned back to you then you have connection. If it returns blank, then you do not have connection which at this point I will not be able to help you.
Sent from my K2_CL using Tapatalk
Modding.MyMind said:
Your phone has a bootloader. You need to access your bootloader, select fastboot, plug your device in your pc, open up command window, then type 'fastboot devices'.
If you get your device serial number returned back to you then you have connection. If it returns blank, then you do not have connection which at this point I will not be able to help you.
Sent from my K2_CL using Tapatalk
Click to expand...
Click to collapse
unfortunately looks like u cant help me cuz neither that wont showup
BenDroid1 said:
unfortunately looks like u cant help me cuz neither that wont showup
Click to expand...
Click to collapse
I'm sorry bro. Maybe someone else on here will pickup where I left off. Good luck friend.
Sent from my K2_CL using Tapatalk
Please HELP!
Yesterday I flashed my Odys Xelio (Allwinner A10) with CWM. After booting in a working state, I restarted in Recovery too full whipe and whipe dalvik, I installed gapps ans the compatibility.zip also from CWM.
After that I got stuck in a whitescreen. I can not access anything, not even CWM recovery anymore. In win 8 I only could see 1 to 2 undefined devices (should be a problem with the device AND a driver issue).
In Linux I could see a device in adb yesterday and could put it into "adb reboot recovery". Still whitescreen on the tablet, but I could push a recovery file with adb to the /sdcard/. Rebooting didn't bring me to another state.
Today I am not able to connect via adb. It always tells me "List of devices attached" and an empty list.
Display should be okay, no cable issue or sth. else. I really hope someone can help. Perhaps theres a way to JTAG the devices or there is a trick with pressing some buttons and using the USB cable...
BTW: While booting into CarbonRom the first time, the button-behaviour was strange or even totally not working. Perhaps that's a point?
THX in advance
EDIT: Now, after playing around with a needle into a "reset-hole" I finally found a way to see the device in adb. How do I go on!?
Today, when I was testing some application, that I develop, on my Z2 the phone freezes on a black screen after installing the app but still ON. the only thing that works was the shutdown/reboot screen when i press and hold the power key. So i reboot the phone but after the xperia logo and the boot screen logo, it freezes again and still on a black screen. i tried to do a soft reset by pressing and holding the little red button but that did nothing. My phone is on android v5.1.1 not rooted, I'm trying to find a solution for this problem without losing my data on the internal storage. I need your help please !!
Try to flash phone with flashtool and uncheck wipinig data in olptions before flashinfg.That sholud be enough.
Yh, exaclty what he said, thats the only way out
Thanks for the reply guys In fact I found another solution for that using ADB and I will explain it step by step :
First, I tried to copy all the data in the internal storage via ADB and I did it using the command line adb pull /sdcard/ C:\My_Data This method is only available when USB debugging mode is enabled.
Then, my second step was to do a hard reset and wipe all data and fix the problem but fortunately before doing that I thought to uninstall the application that caused all those problems, so simply I tried this command line adb shell pm list packages -f to list all installed packages in the phone and recognize the bad one then apply adb uninstall <package> Just after uninstall finished the phone returned to his normal state