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
Related
Is a sad day for me...i didn't knew about the Hardware Lock of Vibrants and i rooted and applied lag fix to my phone. After this i just updated the phone via Kies to JI6 then when phone rebooted got stucked after the second stage of booting with a blank screen. I tried many methods of get into Recovery or Download to flash again but can't because of Hardware Lock. Anyone knows if my problem have a solution?? Im very sad plz help.
Have you tried holding volume down and power until it boots?
Sent from my T-Mobile G2 using XDA App
Yah....Nothing!!
Try all methods:
http://forum.xda-developers.com/showthread.php?t=771247
I think you may need to use ADB commands to force it to reboot into download.
You may need to do method #4.
You may want to keep adb up and keep typing 'adb devices' to see if it sees the device when you try these different methods. If so - reboot into recovery from that.
You should be able to get into DL mode. Do you have ADB on your computer? If not, get it. Put it on the root of your C:\ and than make sure you get the drivers installed on your PC. Get ODIN and have it open. When that is done, connect your phone to your PC and boot it up. Open a cmd prompt (if you are in windows 7 you may need to open as admin) and navigate to C:\ (or where ever you decided to put ADB). At the command prompt type this exactly minus the parenthesis: "adb reboot download" Should shoot you right into DL mode. At that point you will need to flash a new ROM via ODIN, so make sure you read up.
Hope this works/helps.
I tried all that but cant get into recovery or download mode, my phone is not stuked on vibrant logo it just go to the second logo and then blank screen. Fabrication date is 08-10.
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
Hi guys,
I have read all the other posts and they didn't seem to help my problem.
my phone started to bootloop, and i didn't enable ADB debug before. (Tried flashing, says device is locked, tried unlocking, says it needs adb to be on) =.=
i tried factory reset + clear cache in recovery mode => not working
Tried SDK tool -> doesn't recognize devce b/c adb is not on
I just want to know what can I do!?
Please help me! T.T:crying::crying::crying::crying:
Hello, yesterday i tried to install a custom rom on my smart II through recovery -> update.zip (i changed the rom.zip to update.zip, bc i can't access bootloader/fastboot) but i think i messed up , because after rom being succesful installed I factory resetd it :/ , after that i rebooted and got stuck in bootloop, i've tried some stuff, but i don't want to mess it up even more, I've tried using cmd with adb commands, trying to get some response from the device to the pc, but when my smart II is on loop if i do ("fastboot devices") it shows the id of my device, but when i tried to used toolkit to flash recovery it's stuck on this message (<waiting for device..>) something like that, and never recognizes it. i'm able to provide more information if needed,
thank you!
i recently got into playing with andorid , and kinda bootlooped my device,
its htc nexus 9 wifi , i rooted it with wrong version supersu
inject.img
patched.img
then it went into bootloop since im new , and panicked i factory reset it , now its stuck in bootloop and i cant enable developer mode.
can i use odin like solution that can get me in , or what are my options
thanks for reading
rohanzakie said:
i recently got into playing with andorid , and kinda bootlooped my device,
its htc nexus 9 wifi , i rooted it with wrong version supersu
inject.img
patched.img
then it went into bootloop since im new , and panicked i factory reset it , now its stuck in bootloop and i cant enable developer mode.
can i use odin like solution that can get me in , or what are my options
thanks for reading
Click to expand...
Click to collapse
If you can boot into bootloader, you can fastboot flash the images from https://developers.google.com/android/images (or just try running the entire N9F27N script) from your fastboot folder in cmd prompt or the Mac equivalent if you use Apple.
Sent from my Nexus 9 using Tapatalk
usb-debug is not enabled.
the thing is , when i rooted i got locked out then i factory reseted it , but it still is in bootloop,
i am unable to connect with device this is what i see when run the script ,
the cmd prompet say "<waiting for device >"
does it ever happened to anyone , getting locked without getting developer mode > usb-debug enabled , and then flashing factory rom ?
Can you still access TWRP, if it was already on the device.
Flash any custom rom, enable the option and flash stock again (if you want).
If it is stock recovery, sideload an OTA image instead.
https://developers.google.com/android/ota
Manually boot recovery and you shouldn't need usb-debug enabled, I hope.
A bit of research and it is required unfortunately
Edit: You don't need usb-debugging for fastboot flashing.
Also Nexus Root Toolkit might prove helpful to setup drivers on your pc and restore your device to working order.
^^^ It is out of date software, so hesitant to recommend it.
rohanzakie said:
the thing is , when i rooted i got locked out then i factory reseted it , but it still is in bootloop,
i am unable to connect with device this is what i see when run the script ,
the cmd prompet say "<waiting for device >"
does it ever happened to anyone , getting locked without getting developer mode > usb-debug enabled , and then flashing factory rom ?
Click to expand...
Click to collapse
Boot to bootloader and use fastboot commands. Fastboot flash system system.img
Etc.
Use the files extracted from factory image.
rohanzakie said:
the cmd prompet say ""
Click to expand...
Click to collapse
I've definitely had this experience. You can try disconnecting the cable then reconnecting. When that doesn't work, you have to remove all the drivers or at least run through "updating" the Android drivers in hardware settings. You won't actually be updating drivers just re-installing from the PC. Wug's toolkit mentioned above may be your best choice if you don't have TWRP. The toolkit will provide you with an exe called usbdeview which enables driver removal. I didn't mention an OTA sideload because I thought you did need ADB for that. If you can get PC to recognize the device in cmd, then you can fastboot flash images.
Sent from my Nexus 5X using Tapatalk