T-mobile Prism II (U8686)
Android 4.1.1 (rooted)
Custom Recovery CWM 6
I just setup swap with swappy2 following this guide.
I just rebooted and now my phone shows the T-Mobile logo and then directly to BLUE SCREEN
Turning on with no buttons pressed / pwr & v+ / pwr v-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Turning on with both v+/v- pressed
adb/fastboot wont recognize device
any ideas on what is wrong i hope its not bricked?
Diehardshorty said:
T-mobile Prism II (U8686)
Android 4.1.1 (rooted)
Custom Recovery CWM 6
I just setup swap with swappy2 following this guide.
I just rebooted and now my phone shows the T-Mobile logo and then directly to BLUE SCREEN
adb/fastboot wont recognize device
any ideas on what is wrong i hope its not bricked?
Click to expand...
Click to collapse
Try to again flash, and make sure scatter file is correct according to your device.
I have no access to recovery menu, just getting this blue screen each time it powers up.
Diehardshorty said:
T-mobile Prism II (U8686)
Android 4.1.1 (rooted)
Custom Recovery CWM 6
I just setup swap with swappy2 following this guide.
I just rebooted and now my phone shows the T-Mobile logo and then directly to BLUE SCREEN
adb/fastboot wont recognize device
any ideas on what is wrong i hope its not bricked?
Click to expand...
Click to collapse
To use ADB you also need the device Drivers installed.
christoph.gasser said:
To use ADB you also need the device Drivers installed.
Click to expand...
Click to collapse
Did you even read the thread? Go spam else where
Diehardshorty said:
I know how adb and fastboot work the drivers are installed.
Did you even read the thread?
Click to expand...
Click to collapse
Yes I read your thread.
But you don't only need the ADB drivers you also need the device specified drivers.
For example for my HTC One:
I need: the HTC One drivers
the ADB drivers
I had the same problem some time ago.
christoph.gasser said:
Yes I read your thread.
But you don't only need the ADB drivers you also need the device specified drivers.
For example for my HTC One:
I need: the HTC One drivers
the ADB drivers
I had the same problem some time ago.
Click to expand...
Click to collapse
Well the phone came with an autorun cd that mounted with it when you connected it to the computer. It had adb drivers and the device drivers, i installed them both and used the fastboot and adb to flash CWM recovery before this happened to get it rooted. Was working great before i tried to get swap working with the guide i followed above.
Im thinking its bricked possibly bcause this thread. My devices is doing the same thing he is describing.
Just a few images to show you what is happening
Turning on with no buttons pressed / pwr & v+ / pwr v-
Turning on with both v+/v- pressed
bump
I have the same problem and have not found a solution
Related
i booted into recovery, made a full backup, wiped everything but internal storage, flashed to lollipop 5.1 but decided to go back to my backup. so rebooted into recovery again and restored the backup. everything seemed to work correctly but after rebooting phoned stuck at lg logo. so i rebooted into recovery by holding "volume - and power" and the factory data reset screen came up and i confirmed that i wanted to reset phone, expecting it to boot into twrp but it went to the the black screen with the android on his side (or something like that), which i assume it did do a factory reset.
so still stuck at lg logo with no custom recovery anymore apparently. among other things, i used srktool to nuke download mode, so phone immediatly goes into fastboot mode. now im trying to use the "fix fastboot mode" but it just sits there saying waiting for device even though i have phone connected to computer in fastboot mode.
is it likely that if/when it did the factory reset, that would disable the usb debugging setting and that's why srktool just shows "waiting for device"?
im betting that your OS got corrupted. You can try to reflash your ROM, or you might be relegated to going into download mode and reflashing the OS back to stock. I have a link for the LG recovery tool and the stock 4.4.2. All youll need from there is towel root and the recovery i have in a separate post
hi i have same problem con you explein how can i do this
hi i have same problem con you explein how can i do this
l.musaj said:
hi i have same problem con you explein how can i do this
Click to expand...
Click to collapse
try this
http://forum.xda-developers.com/att-g2/development/twrp-5-0-d800-g2s-t3247754
youdoofus said:
try this
http://forum.xda-developers.com/att-g2/development/twrp-5-0-d800-g2s-t3247754
Click to expand...
Click to collapse
thank you but my lg d800 dosnt entry in download mode it stuck
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
he stuck here in ports dosnt show nothink but in USB controllers its unknown device
l.musaj said:
thank you but my lg d800 dosnt entry in download mode it stuck
he stuck here in ports dosnt show nothink but in USB controllers its unknown device
Click to expand...
Click to collapse
uninstall the usb driver and let windows find the correct driver for it and follow the stuff in the link i provided after the computer recognizes the device. If that doesnt work do the stuff in the link on another computer or try a different cable. If you can get to download mode, youre likely ok. The issue is either the computer or the cable, not the phone.
Hello,
My Samsung Galaxy Note 10.1 (GT-N8000) Suddenly got stuck at Samsung logo screen
When I tried to restart it it did not work, So I tried to make a hard reset but it also did not work
So I tried getting into the Download Mode and I got stuck there and cannot do anything
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried flashing it through ODIN through computer but also nothing happened
And when I try to make a hardreset I get the below screen :
Would you kindly help .. I cannot even turn it off .. what can I do ?
Masry said:
Hello,
So I tried getting into the Download Mode and I got stuck there and cannot do anything
That is correct for download mode .
Open Odin flash correct stock rom .
See multiple identical threads on the forum .
Click to expand...
Click to collapse
JJEgan said:
That is correct for download mode .
Open Odin flash correct stock rom .
Click to expand...
Click to collapse
I already tried doing this but it did not work, ODIN could not connect to the device.
Usual reasons .
User has no drivers installed on PC .
User not using Samsung USB cable .
Faulty USB ports .
User not using mainboard PC usb port .
Friend I have same problem for my ZTE v9a tab.I can not get download mode and recovery mode.And I can't boot my tab.boot loop.plz help me
Sent from my SM-N920C using Tapatalk
madushancs said:
Friend I have same problem for my ZTE v9a tab.I can not get download mode and recovery mode.And I can't boot my tab.boot loop.plz help me
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Wrong forum .
Don't want to hijack this thread but I'm having this same issue on my SCH-I925 (Verizon version). Every time I go to push anything in Odin I get NAND write fail. Has anyone figured out what to do?
I have the exactly same problem as you mate with my n8000. i have tried 3 different odins all usb ports and 2 different computers with samsung kies drivers installed. odin and computer dosent reconize
OK not exactly the same. by me when i hold the powerbutton it will turnoff and turn back again in the same download mode. I dont get such bars like in the second picture. But it dosent stay off
Please someone help us :crying::crying::crying::crying:
If I find a sollution i will come back and tell you
FIXED IT!
:victory::victory::victory:SUPER NEWS GUYS!!! I did it i got it working again! It was the offical cables fault. I ordered a new cable from ebay (link below)
Computer recognized it and i could use odin to flash the offical rom from sammobile. everything is fine now:victory::victory::victory:
http://www.ebay.com/itm/USB-Data-Charger-Cable-For-Samsung-Galaxy-Note-10-1-GT-N8000-N8010/271040779330?_trksid=p3693.c100102.m2452&_trkparms=ao%3D1%26asc%3D20140212121249%26meid%3D07aa2892f3e94b109b58b515fde41c77%26pid%3D100102%26
Yes one of the very basics of flashing fail .Cable or usb port or drivers .
Sent from my SM-N930F using XDA-Developers mobile app
Hey, my friend has a Pixel 2 that seems to have gotten bricked today. His phone was working fine all day but when he tried to unlock it to check the time, it was suddenly in fastboot mode. He was running stock android, and has never flashed any custom ROM/software to it, nor unlocked it:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't open recovery mode or boot the OS from fastboot. The only option I can access is the "barcode" one. I've been trying to flash a factory image from google(as I've done several time for my Nexus 5 and Nexus 7 using the fastboot/ADB from CMD), but currently ADB won't recognize the device(probably because USB debugging and other developer settings are off/have never been accessed at all), and Fastboot recognizes the device but can't perform any flashing to it because it's locked. I also tried deuces script from a folder with all the factory .img files unzipped etc. I also updated the USB drivers in windows, but basically every step I can find here, on reddit or on stack overflow mention enabling USB-debugging and OEM unlock in the settings, which I can't access. Is there anything I can try or is it per definition bricked?
Marhan93 said:
Hey, my friend has a Pixel 2 that seems to have gotten bricked today. His phone was working fine all day but when he tried to unlock it to check the time, it was suddenly in fastboot mode. He was running stock android, and has never flashed any custom ROM/software to it, nor unlocked it:
I can't open recovery mode or boot the OS from fastboot. The only option I can access is the "barcode" one. I've been trying to flash a factory image from google(as I've done several time for my Nexus 5 and Nexus 7 using the fastboot/ADB from CMD), but currently ADB won't recognize the device(probably because USB debugging and other developer settings are off/have never been accessed at all), and Fastboot recognizes the device but can't perform any flashing to it because it's locked. I also tried deuces script from a folder with all the factory .img files unzipped etc. I also updated the USB drivers in windows, but basically every step I can find here, on reddit or on stack overflow mention enabling USB-debugging and OEM unlock in the settings, which I can't access. Is there anything I can try or is it per definition bricked?
Click to expand...
Click to collapse
Have you tried using the OTA instead of the factory image? That might give you a workaround to get it functioning again.
Sent from my Pixel 2 using Tapatalk
Have you tried changing your usb cable and the port its plugged into? Its stupidly simple, but has solved nuuuuuumerous problems I've had with manually flashing.
Other that that, I think you've covered a lot of bases. Are you sure you can't get into recovery mode tho? I was only able to get in by unplugging, full power off, then using power + vol dn for bootloader mode, then selecting recovery mode. You might be able to do some flashes from there.
Also, adb only works in the OS and maybe recovery mode. Fastboot only works in bootloader mode. I'm not exactly sure if fastboot needs to be authorized. Adb does though.
I have a t mobile variant that is sim unlocked and bootloader unlocked.
I wanted to convert to a Global version however it failed because I apparently had the wrong oem software.
I used all in one tool which worked great for everything else I needed but here is the problem; I can only boot into fastboot mode and crashdump mode. When using all in one tool I chose to wipe the device before installing the new software
I also cannot get into EDL Mode to use the Msmdownload tool even though the correct drivers are installed to use this tool.
Anyway out of this? Thanks...
Aslo; I have tried fastboot commands with no luck...
You need to msm using edl. If you are bl unlocked, flash a custom ROM to get booted and maybe try again using proper tool?
Also, try different USB ports, cables, etc. You should be able to boot into edl with hw keys and connect to msmtool
As I stated I can not get into edl, I tried all the the other things also, cables, ports. I did not know I could have flashed a custom rom at this point, phone was not rooted either...
Oneplus has it now for repair, they are about 300 miles from me, or the service center is?
Gabriel51 said:
As I stated I can not get into edl, I tried all the the other things also, cables, ports. I did not know I could have flashed a custom rom at this point, phone was not rooted either...
Oneplus has it now for repair, they are about 300 miles from me, or the service center is?
Click to expand...
Click to collapse
Not sure if you got this fixed but boot into fastboot, the use "fastboot boot" to boot into AICP Recovery. Within recovery eanble ADB, then "adb reboot edl". EDL mode is just a black screen and your phone will exit it and try to boot after a few seconds if the drivers are not installed so its easy to miss. If your phone can boot into fastboot it can boot into EDL.
I do not see that feature listed? Phone would not boot into normal recovery, it went right back into fastboot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also if you had read through the posts you would know that I already sent it to 1+ for repair, they have had it a couple of days...
OnePlus repaired my device for nothing which is nice however It's now sim locked and at first try T-mobile says this device does not qualify for unlock!!! T-mobile also said they are looking into it because it was previously unlocked and it may take a week to get a reply.
I called OnePlus and their response was it's not our problem (more or less) I sent them a unlocked phone and they completely ignored my request to load the global software on this device, they did what they wanted to, they could have contacted me at any time..THANK YOU OnePlus.
So i was trying to install twrp and it failed and the phone displayed this "the current image(boot/recovery) have been destroyed" and keeps turning on and off. Later it restarts and got stuck in the logo "Realme with powered by Android". I don't know what happened. I can't press volume up and power button. So I waited till it drains its battery. So I tried charging it back and it shows charging red. Then when it reaches to a point where it can turn on, It got stuck in the charging white logo thingy and it wont let me do anything.
But after a few tries it finally wont turn on.
I tried connecting it to the computer and somehow it shows an unknown driver.
QUSB_BULK_CID:0411_SN:B3336417
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have no idea what that is but I know that "B3336417" is the ID of the phone.
Can anyone help me how to fix this phone?
Assuming you've correctly installed ADB driver on Windows 10 then if USB Debugging didn't get enabled on phone you'll NOT see the phone in Windows' Device Manager under Portable Devices - where it should be shown.
Try installing MTK Drivers, it should fix the problem
EDIT: Then flash Stock ROM using SP Flash Tool V5
jwoegerbauer said:
Assuming you've correctly installed ADB driver on Windows 10 then if USB Debugging didn't get enabled on phone you'll NOT see the phone in Windows' Device Manager under Portable Devices - where it should be shown.
Click to expand...
Click to collapse
I pressed volume up + volume down + power button and it takes me to fastboot mode. Do you know how to restore back the phone? where can I find the stock rom for realme 5i?
NoveNoki said:
Try installing MTK Drivers, it should fix the problem
EDIT: Then flash Stock ROM using SP Flash Tool V5
Click to expand...
Click to collapse
I pressed volume up + volume down + power button and it takes me to fastboot mode. Do you know how to restore back the phone? where can I find the stock rom for realme 5i?
Grim Face said:
I pressed volume up + volume down + power button and it takes me to fastboot mode. Do you know how to restore back the phone? where can I find the stock rom for realme 5i?
Click to expand...
Click to collapse
Here are official ROM files from all Realme phones: https://www.realme.com/eu/support/software-update just search for your phone and you should find it, tho you will need a computer so you can flash the files
EDIT: Do you know if your device uses MediaTek chip?
NoveNoki said:
Here are official ROM files from all Realme phones: https://www.realme.com/eu/support/software-update just search for your phone and you should find it, tho you will need a computer so you can flash the files
EDIT: Do you know if your device uses MediaTek chip?
Click to expand...
Click to collapse
My phone uses Snapdragon but I finally have OrangeFox recovery
NoveNoki said:
Here are official ROM files from all Realme phones: https://www.realme.com/eu/support/software-update just search for your phone and you should find it, tho you will need a computer so you can flash the files
EDIT: Do you know if your device uses MediaTek chip?
Click to expand...
Click to collapse
Can I flash my rom to the Orange Fox Recovery mode? It seems that my OS is gone.
Grim Face said:
Can I flash my rom to the Orange Fox Recovery mode? It seems that my OS is gone.
Click to expand...
Click to collapse
I think you should be able to, i am not too sure. But i whould recommend you to flash it manually using the fastboot mode, tho if you can try flashing it from the recovery