My wife installed the April update on her phone a few nights ago while I was asleep. After installation, she can't get past the boot lock screen. The screen doesn't recognize any input. I am able to reboot into recovery and would like to try a factory reset, but she has two months of baby photos on there that have not been backed up. I have tried mounting the phone from recovery but none of the computers I have tried will recognize the phone. Any suggestions on how to get the photos off of the device?
Thanks!
boomer13 said:
My wife installed the April update on her phone a few nights ago while I was asleep. After installation, she can't get past the boot lock screen. The screen doesn't recognize any input. I am able to reboot into recovery and would like to try a factory reset, but she has two months of baby photos on there that have not been backed up. I have tried mounting the phone from recovery but none of the computers I have tried will recognize the phone. Any suggestions on how to get the photos off of the device?
Thanks!
Click to expand...
Click to collapse
Perhaps I can use ADB to access the internal storage?
Try all the combinations of usb ports and cables you have. Aren't Microsoft and device drivers magical? There are other things you can try before you factory reset. BTW, was the phone rooted, encrypted or anything else before the update was applied?
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
Try all the combinations of usb ports and cables you have. Aren't Microsoft and device drivers magical? There are other things you can try before you factory reset. BTW, was the phone rooted, encrypted or anything else before the update was applied?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
It was stock. She received her replacement today. I never hooked up her bricked phone to my computer pre-brick... Maybe I can hook up the new one, install the drivers on my computer, and then mount the bricked one via Recovery.
boomer13 said:
It was stock. She received her replacement today. I never hooked up her bricked phone to my computer pre-brick... Maybe I can hook up the new one, install the drivers on my computer, and then mount the bricked one via Recovery.
Click to expand...
Click to collapse
That sounds like a plan. You could also try and mount the old phone to the new one with the included c to c cable. You are definitely in an interesting situation.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
That sounds like a plan. You could also try and mount the old phone to the new one with the included c to c cable. You are definitely in an interesting situation.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
That's worth a shot. I've never done that before.
Now I don't know if I'll be able to even get into Recovery. The screen has started doing some weird stuff and I can't get it to shut down.
{
"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"
}
The phone comes encrypted. That might make things difficult. You said that the phone won't boot past the boot lock screen, so assume that you mean that the pin is required to fully boot the phone. Is that right? If so, adb pull won't do squat.
Another option is to buy an OTG cable and connect the phone to a mouse and/or keyboard and see if you can poke around and get things transferred.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
The phone comes encrypted. That might make things difficult. You said that the phone won't boot past the boot lock screen, so assume that you mean that the pin is required to fully boot the phone. Is that right? If so, adb pull won't do squat.
Another option is to buy an OTG cable and connect the phone to a mouse and/or keyboard and see if you can poke around and get things transferred.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Correct, it requires a pattern to fully boot. I think it might be completely fubared now anyway.
boomer13 said:
Correct, it requires a pattern to fully boot. I think it might be completely fubared now anyway.
Click to expand...
Click to collapse
It looks like a faulty screen. The data inside may still be there.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
It looks like a faulty screen. The data inside may still be there.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yeah, but it's looking like I'll have no way to access it. Maybe once the battery dies I'll be able to reboot and the screen will work well enough to get into recovery again.
Related
Okay long story short, I was flashing Kang's Bullet kernel to my phone without the battery cover on (I know, I'm a dumb ass) and go figure, the battery pops out. I put the battery back in, and the phone doesn't boot as I sorta expected.
When I plug my phone into the computer it shows up as a qhs_usb device but it didn't have drivers. I searched around, found the drivers I needed here - http://forum.xda-developers.com/showpost.php?p=14909282&postcount=19 . So now my computer and Odin recognize my phone, but when I try to flash the stock kernel back on the phone it gets stuck on "Setup Connection". I'm having the exact same issue as this guy - http://forum.xda-developers.com/showpost.php?p=19091572&postcount=7
Does anyone have any insight as to how to get around this problem? While doing some more searching, I read that a USB jig may work. Will that work with our phones or is that only for the first gen Galaxy phones? Thanks in advance for any help.
ghettoc401 said:
Okay long story short, I was flashing Kang's Bullet kernel to my phone without the battery cover on (I know, I'm a dumb ass) and go figure, the battery pops out. I put the battery back in, and the phone doesn't boot as I sorta expected.
When I plug my phone into the computer it shows up as a qhs_usb device but it didn't have drivers. I searched around, found the drivers I needed here - http://forum.xda-developers.com/showpost.php?p=14909282&postcount=19 . So now my computer and Odin recognize my phone, but when I try to flash the stock kernel back on the phone it gets stuck on "Setup Connection". I'm having the exact same issue as this guy - http://forum.xda-developers.com/showpost.php?p=19091572&postcount=7
Does anyone have any insight as to how to get around this problem? While doing some more searching, I read that a USB jig may work. Will that work with our phones or is that only for the first gen Galaxy phones? Thanks in advance for any help.
Click to expand...
Click to collapse
Ha. Don't worry. I bricked my phone on my first try too. What I did was connect my phone to odin again, but just rooted it all over again. It worked too. Download the files you need and use odin to root it again. It should work.
yup, just boot into the Download mode, and flash back to stock via ODIN, then you can go from there
a USB jig will definitely make it easier
Thanks for the help so far guys. Okay unfortunately I can't get into download mode. My phone doesn't show anything on the display, make any sounds or anything. I've tried different combinations of pressing the volume up/down key and inserting the USB cable, but Odin still freezes at the "Setup Connection" step. I think its fully bricked because even when I don't press any keys when plugging in my phone my computer still recognizes it as the same device and Odin still freezes. I've attached a pic to show what I mean. The "Qualcomm HS-USB QDLoader device I have expanded in device manager is what my computer sees the phone as, no matter what I do.
{
"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"
}
*Take the battery out and place it back
*Hold both Vol up + Vol down, and plug the USB cable in.
That will bring you to download mode
or leave the batt. out for a min. or 2. Also try a different port see if that helps.
Thanks for all the help guys. Unfortunately I can't get it into download mode. I even tried with my friends jig - http://www.youtube.com/watch?v=Rdn5GoRjhn0&noredirect=1 but it doesn't work. I'm just going to consider this a loss and see if I can get another phone used on CraigsList or eBay.
How I unbricked mine....
I was having a hard time as well after bricking my phone. In desperation, this is what I did....
I went to another pc, my work laptop, and installed the drivers and installed odin on it. Simply plugged the phone in and flashed via Odin back to stock firmware. All it took was swapping pc's. I was having the same issue............
My guess is that somehow since the original pc "knew" the phone, it couldn't decipher the phone in a different state, but it did prove to work on another pc.
I hope this helps you!
wait until unbrickable mod comes out..lol
You can also trya different usb on your PC. I could always find Odin. Good luck
Sent from my G Sexy II using XDA App
take it to tmobile and say u dont know what happened and get another one??? just dont say you were rooting/flashing/anything to it. im sure they'll take it back if there's no sign of any modding on it.
clemsonboyz said:
I was having a hard time as well after bricking my phone. In desperation, this is what I did....
I went to another pc, my work laptop, and installed the drivers and installed odin on it. Simply plugged the phone in and flashed via Odin back to stock firmware. All it took was swapping pc's. I was having the same issue............
My guess is that somehow since the original pc "knew" the phone, it couldn't decipher the phone in a different state, but it did prove to work on another pc.
I hope this helps you!
Click to expand...
Click to collapse
Thanks, I did try this one last time, but it didn't work :\ . I've already given up hope because I did some more reading and when the phone gets in this mode, it means the eMMC (or something like that) needs to be re-flashed and that's something they have to do at the factory.
unknownnoob said:
take it to tmobile and say u dont know what happened and get another one??? just dont say you were rooting/flashing/anything to it. im sure they'll take it back if there's no sign of any modding on it.
Click to expand...
Click to collapse
Yea but I bought it the first day it came out, not sure they would take it back if I tried to return it. Also it's 100% my fault, so I would feel bad trying to return it. But thanks for the advice though.
I know that it's been a while since your last post, but you might want to take up this service;
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-skyrocket-jtag-brick-repair/
I had my Galaxy S2 i777 revived not too long ago by these guys after an accidental repartition with an incorrect .pit.
ghettoc401 said:
Thanks, I did try this one last time, but it didn't work :\ . I've already given up hope because I did some more reading and when the phone gets in this mode, it means the eMMC (or something like that) needs to be re-flashed and that's something they have to do at the factory.
Yea but I bought it the first day it came out, not sure they would take it back if I tried to return it. Also it's 100% my fault, so I would feel bad trying to return it. But thanks for the advice though.
Click to expand...
Click to collapse
Edit
Sent from my HTC One S using xda premium
hi
i dont know how to install the driver. please help me
First of all, forgive me for my language for I am upset with myself and hope someone can help me. I did not know where to post this, so I figured this was best place. There was not a Dumb ### (edited by VeNuM) Thread or I would have posted there.
I did some dumb stuff and used the Galaxy S2 GT-9100 forums to alter my phone. CWM, KERNEL, and Reset whole phone to GT-9100 cause things were not working lol. I did not realize there are so many versions of the Galaxy s2. Well after all the garbage I did. I am still able to go into ODIN, but I am not able to get my computer to recognize my phone now. There is no ping/notification nothing, no prompt about wrong drivers. After all of this I looked under battery and it was model Model SPH-D710, now in Odin it shows samsung gt-i9100.
Anyone have any advice?
I should have slept before doing all this...
2ndComing said:
I should have slept before doing all this...
Click to expand...
Click to collapse
If you do have a SGS2 Epic 4G Touch this is the right place to be but Q n A would be the right place...... http://forum.xda-developers.com/showthread.php?t=1953783I Download a one click of any of the roms for your version of phone, SGS2 epic 4g touch if thats what you have. If you can get into download mode, hold power and volume down. Once in Dl mode connect to pc via usb and see if one of the com ports light up in the one click. If it does you are in luck and press start. If it doesnt, try downloading the drivers. You can get them and all one clicks here........ http://forum.xda-developers.com/showthread.php?t=1903252. Hope you get it fixed.
ty
cerj said:
Q n A would be the right place...... http://forum.xda-developers.com/showthread.php?t=1953783
Click to expand...
Click to collapse
ty
cerj said:
If you do have a SGS2 Epic 4G Touch this is the right place to be but Q n A would be the right place...... http://forum.xda-developers.com/showthread.php?t=1953783I Download a one click of any of the roms for your version of phone, SGS2 epic 4g touch if thats what you have. If you can get into download mode, hold power and volume down. Once in Dl mode connect to pc via usb and see if one of the com ports light up in the one click. If it does you are in luck and press start. If it doesnt, try downloading the drivers. You can get them and all one clicks here........ http://forum.xda-developers.com/showthread.php?t=1903252. Hope you get it fixed.
Click to expand...
Click to collapse
thank you I will try the one click. I have redone the drivers so many times. The computer is not recognizing my phone at all now, like its a dead usb lol. I will see if a com will open up. It used to in ODIN but wont anymore
2ndComing said:
thank you I will try the one click. I have redone the drivers so many times. The computer is not recognizing my phone at all now, like its a dead usb lol. I will see if a com will open up. It used to in ODIN but wont anymore
Click to expand...
Click to collapse
Try different usb port in your PC and a Different cable. The stock usb cable is good, aBlackBerry one is good too. Bad cables cause probs
cerj said:
Try different usb port in your PC and a Different cable. The stock usb cable is good, aBlackBerry one is good too. Bad cables cause probs
Click to expand...
Click to collapse
I plug my atrix 4g in with the same cable adn it works fine. I do not have another cable I will have to get one and try.
Thank you all for trying to help me I really appreciate it. I will keep trying.
Uninstall all your phone drivers through the device manager or add/remove software. REBOOT. Then start from scratch. It's sometimes easier to put the phone in download mode. I'm not sure why but when I have problems connecting to my phone that always works. And yes... This should have been in q&a.
Sent from my SPH-D710 using xda premium
abadasstanker69 said:
Uninstall all your phone drivers through the device manager or add/remove software. REBOOT. Then start from scratch. It's sometimes easier to put the phone in download mode. I'm not sure why but when I have problems connecting to my phone that always works. And yes... This should have been in q&a.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Agreed. Move this thread! :banghead:
Sent from my SPH-D710 using xda premium
I'm sorry to tell you this buddy, and it looks like people here do not have enough experience with bricks either. If you've flashed a rom from the international GS2, the only way to fix it is J-TAG. Flashing international GS2 Roms, disable your usb port regardless of Odin functionality.
Thanks for the input xstatik, think a whole group of people moved on to newer phones.Dont know if there are many that know, Thanks for bringing your knowledge
In before the lock.
{
"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"
}
Sent from my Galaxy Nexus LTE using Tapatalk pro
Jtag service can be found here http://mobiletechvideos.mybigcommerce.com/samsung-epic-4g-touch-jtag-brick-repair/
Ok, I know your computer has the drivers, now, download a one click ROM and a kernel tar. Make sure you have a good USB Cable.. Ive had this exact same problem. With a new USB Cable...
open ODIN and find your kernel.Tar for this device. Have it loaded in ODIN BUT the phone disconnected.
Pop out the battery and put it back in
Now put it in DL mode holding power and vol dwn, press vol up to go into Odin mode
With the new cable connect your device
Look at the odin window and you should have a yellow COM port.
Flash the kernel. After it passes, and reboots, follow the same steps above and now flash your stock ROM
Reason being, if you don't have the proper kernel for this device, the ONE CLICK ROM will most likely fail. If you follow this exactly it should work. Good luck.
Yes the phone is bricked (when I developed for this phone I bricked it so I know). Either try the jtag or get another phone. This isssue has been covered in the q and a (where this SHOULD have been. NOT development. I am moving it though...). Also, theres no reason for the language you used. Please read the rules again and follow them. Good luck.
Closed.
My friend from Korea bought a kfhd 8.9 here in the US and rooted it, but an OTA installed and bricked it. It keeps booting to the stock recovery. I tried getting fastboot to work, but the computer won't detect it, as well as the unbrick utility. Anything I can do?
It keeps booting to this
{
"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"
}
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
What attempts did you make to access fastboot?
Powering off, running cmd and typing fastboot -i 0x1949 getvar product, plugging it in. It doesn't detect my device.
I noticed that when I plug it in, Windows makes the beeping sound that tells you something is connected, and something briefly shows up in the hardware and devices section, but then disappears.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Nothing shows up in the device manager when plugged in as well. And I did install the drivers.
You never know with Windows...Have you tried SoupKit?
rha_december said:
Nothing shows up in the device manager when plugged in as well. And I did install the drivers.
Click to expand...
Click to collapse
I would try to remove all the drivers you have now and install the non signed drivers from the first aid perferd drivers and that should go without any problems once that is done you should have a working drivers. Depending if you have windows 7 or 8 on how to disable driver signature.
Alrighty, thanks guys. I give it a shot.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
I tried again on a different computer, and followed the instructions for KF First Aide package up until I had to plug it in. A driver installation window popped up and driver not found I can't go beyond that. I pressed 12 to install the Amazon ADB driver.
rha_december said:
I tried again on a different computer, and followed the instructions for KF First Aide package up until I had to plug it in. A driver installation window popped up and driver not found I can't go beyond that. I pressed 12 to install the Amazon ADB driver.
Click to expand...
Click to collapse
I think the step your missing is to disable driver signature enforcement Search in google for disable driver signature enforcement Windows (then whatever version you have) and should find a way to do it, then connect kindle to the computer remove any drivers you see in device manager (and click delete driver if it gives you a check box) Then try the same thing and it should work! (cross all your fingers:fingers-crossed::fingers-crossed
lizzord30 said:
I think the step your missing is to disable driver signature enforcement Search in google for disable driver signature enforcement Windows (then whatever version you have) and should find a way to do it, then connect kindle to the computer remove any drivers you see in device manager (and click delete driver if it gives you a check box) Then try the same thing and it should work! (cross all your fingers:fingers-crossed::fingers-crossed
Click to expand...
Click to collapse
I gave it a shot, but nothing is being picked up. Note that I can't even fully boot up the Kindle. It always goes straight to the stock recovery. Would an OTA disable ADB in the kindle?
UPDATE: Wow... I hit 9 to check fastboot status and it just happened to work, haha. Thanks a lot for your help!
rha_december said:
I gave it a shot, but nothing is being picked up. Note that I can't even fully boot up the Kindle. It always goes straight to the stock recovery. Would an OTA disable ADB in the kindle?
UPDATE: Wow... I hit 9 to check fastboot status and it just happened to work, haha.
Click to expand...
Click to collapse
:good::good: Great now that your in fastboot do you know what to do?
If you like could try my Rom but it will wipe your whole device(nothing on SDcard will be left)
here is the link if you like
It has some glitches still but it is automated from when your in fastboot. And dont forget to letup LMT on first boot.
lizzord30 said:
:good::good: Great now that your in fastboot do you know what to do?
If you like could try my Rom but it will wipe your whole device(nothing on SDcard will be left)
here is the link if you like
It has some glitches still but it is automated from when your in fastboot. And dont forget to letup LMT on first boot.
Click to expand...
Click to collapse
Hm, I actually tried to do a complete restore through fastboot, since it's the only thing working, but when it finishes and the kindle reboots, it still goes back to the stock recovery screen. I can't run the unbrick utility or use anything that requires ADB, since it's not being detected through that ><; damn it. I thought I was on to something.
rha_december said:
Hm, I actually tried to do a complete restore through fastboot, since it's the only thing working, but when it finishes and the kindle reboots, it still goes back to the stock recovery screen. I can't run the unbrick utility or use anything that requires ADB, since it's not being detected through that ><; damn it. I thought I was on to something.
Click to expand...
Click to collapse
I was sending you that link because you don't need ADB to use what I linked, it goes right from fastboot.
lizzord30 said:
I was sending you that link because you don't need ADB to use what I linked, it goes right from fastboot.
Click to expand...
Click to collapse
Gotcha. Do you think I'll be able to boot up normally if I flash this?
rha_december said:
Gotcha. Do you think I'll be able to boot up normally if I flash this?
Click to expand...
Click to collapse
Maybe, hard to tell since like you said you tried to go back to completely stock and it didn't work.
Alrighty, I flashed yours but I ended up with a red screen, but I figured out how to actually fix it. This kindle now run perfectly haha. awesome.
rha_december said:
Alrighty, I flashed yours but I ended up with a red screen, but I figured out how to actually fix it. This kindle now run perfectly haha. awesome.
Click to expand...
Click to collapse
Please post what you did so for the next person that has this problem can get it fixed!
Happy you got it working.
lizzord30 said:
Please post what you did so for the next person that has this problem can get it fixed!
Happy you got it working.
Click to expand...
Click to collapse
I'll do that as soon as I have time to take screenshots and stuff. Just ran through the rain and jumped over a flooded road to get home >< soaking wet.
rha_december said:
I'll do that as soon as I have time to take screenshots and stuff. Just ran through the rain and jumped over a flooded road to get home >< soaking wet.
Click to expand...
Click to collapse
Ok thanks! I want to make a script to fix the red screen problem! I had it once but I forgot how I fixed it lol and I dont want to get it again to try to learn again how to fix
Pretty much all I did was get into fastboot via cmd, and flashed boot, system, and recovery individually; they were for 8.1.4. I was at work when I did it, so I can't remember where I got the files, but you get the idea.
However, I had to type: flashboot -i 0x1949 flash (whatever here) (dragged the file here)
Because putting the file in the same folder as my fastboot didn't work.
After that I just rebooted and it worked.
So, basically I downloaded cm10.1 nightly and it was rebooting every some hour, this morning when i turned it on it immediately started rebooting and it kept rebooting until i pulled the battery.
so i went to the cwm recovery and tried to flash a backup, but whenever i tried to flash the backup it also rebooted..
then i downloaded the google nexus toolkit and thought i could restore my nexus with it, but since i can't boot into android, i can't get adb access...
i'm really lost right now, does anyone know what i can do?
thanks in advance :crying:
error i get in the toolkit
{
"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"
}
Too many links I believe is usually a USB issue, either port on PC, port on phone, USB cable, or even drivers issues on your PC (as in USB driver issues). I could be mistaken on this, but I seem to remember reading that was the solution to this problem a while back.
cupfulloflol said:
Too many links I believe is usually a USB issue, either port on PC, port on phone, USB cable, or even drivers issues on your PC (as in USB driver issues). I could be mistaken on this, but I seem to remember reading that was the solution to this problem a while back.
Click to expand...
Click to collapse
drivers are fine i guess, since i used the toolkit some days ago and everything worked fine..
also i tried to use this guide to start my gnex : http://rootzwiki.com/topic/12069-gu...able-bootloopingpseudo-brickedbricked-phones/
but i get this error again...
Toxina said:
drivers are fine i guess, since i used the toolkit some days ago and everything worked fine..
also i tried to use this guide to start my gnex : http://rootzwiki.com/topic/12069-gu...able-bootloopingpseudo-brickedbricked-phones/
but i get this error again...
Click to expand...
Click to collapse
just change your usb cable or usb port
samersh72 said:
just change your usb cable or usb port
Click to expand...
Click to collapse
doesnt help at all x.x
Do you have kies installed? Just probing an idea.
a manta wrote this.
beekay201 said:
Do you have kies installed? Just probing an idea.
a manta wrote this.
Click to expand...
Click to collapse
i dont, also now i have a weird symbol, its like "phone then two dots then a big yellow exclamation mark followed by two dots and then a computer"
edit : got a picture for the symbol i get upon start.. : http://i.imgur.com/RI9lxWO.jpg
can't boot into fastboot anymore..
edit :
kay tried to do it with odin and odin hangs at system too..
Try my odin package (see my sig) and use odin 1.85
sent from my Galaxy
samersh72 said:
Try my odin package (see my sig) and use odin 1.85
sent from my Galaxy
Click to expand...
Click to collapse
didn't help in any way :/
ugh im getting frustrated :crying:
any ideas are welcome at this point ._.!
Toxina said:
any ideas are welcome at this point ._.!
Click to expand...
Click to collapse
"Odin flashing is like taking a lottery ticket! U never know when u hit the jackpot!"
retry with odin + pit file
samersh72 said:
"Odin flashing is like taking a lottery ticket! U never know when u hit the jackpot!"
retry with odin + pit file
Click to expand...
Click to collapse
tried it but im still stuck at system..
ugh push ;-;
Toxina said:
ugh push ;-;
Click to expand...
Click to collapse
Don't "push" threads, take it easy. It's not going to help if you're stressing about it, believe me. What's your platform-tools version? R16?
http://forum.xda-developers.com/showthread.php?t=1760787
beekay201 said:
Don't "push" threads, take it easy. It's not going to help if you're stressing about it, believe me. What's your platform-tools version? R16?
http://forum.xda-developers.com/showthread.php?t=1760787
Click to expand...
Click to collapse
dont know what version but the date is : 2013 05 22
btw i got my nexus to boot to stock with a sideloaded zip BUT every time i wanna take a photo it freezes and reboots, and when i try to record a video it'll also freeze and reboot, it'll also freeze and reboot if i try to put something into the sd-card through usb, it also makes a loud popping voice everytime it reboots..
edit : it also sometimes freezes on reboot, i think there's something wrong when writing/reading/deleting/saving data with my gnex...
pushing this cause i still need help v.v
still need help.
so i bricked my fire tv 2 and for the life of me can not get windows 10 to detect it. keeping getting message in adbfire no devices detected. is was detecting it yesterday. any ideas peeps?
You're going to have to give us more information. What did you do to it? Is it rooted? Do you have TWRP installed? Is it stuck on the white amazon logo? Does it get to the colorful Fire TV logo? The more information you give, the more likely someone will be able to help.
AFTVnews.com said:
You're going to have to give us more information. What did you do to it? Is it rooted? Do you have TWRP installed? Is it stuck on the white amazon logo? Does it get to the colorful Fire TV logo? The more information you give, the more likely someone will be able to help.
Click to expand...
Click to collapse
sorry, i was trying to install a backup and wiped dalvik cache and cache then got some cache error. will only boot to white logo. no twrp. yes to everything accept getting to the colourful fire tv logo. was on 5.0.5.
thks
mandroid717 said:
sorry, i was trying to install a backup and wiped dalvik cache and cache then got some cache error. will only boot to white logo. no twrp. yes to everything accept getting to the colourful fire tv logo. was on 5.0.5.
thks
Click to expand...
Click to collapse
WIthout access to recovery, your only option is rbox's unbrick image here: http://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349
You'll need an A-to-A USB cable.
AFTVnews.com said:
WIthout access to recovery, your only option is rbox's unbrick image here: http://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349
You'll need an A-to-A USB cable.
Click to expand...
Click to collapse
yes i have tried that but adb does not detect device or should i say windows does not see it. it saw it yesterday. i have tried different ports. the cable is new.
mandroid717 said:
yes i have tried that but adb does not detect device or should i say windows does not see it. it saw it yesterday. i have tried different ports. the cable is new.
Click to expand...
Click to collapse
Sounds like it's an issue with your PC and/or drivers. Try a different PC if you have access to one, or try deleting all the relevant drivers and start from scratch. Sorry I don't have any other suggestions.
AFTVnews.com said:
Sounds like it's an issue with your PC and/or drivers. Try a different PC if you have access to one, or try deleting all the relevant drivers and start from scratch. Sorry I don't have any other suggestions.
Click to expand...
Click to collapse
thx
AFTVnews.com said:
Sounds like it's an issue with your PC and/or drivers. Try a different PC if you have access to one, or try deleting all the relevant drivers and start from scratch. Sorry I don't have any other suggestions.
Click to expand...
Click to collapse
So using different pc worked. Now recovery looks like this when trying to install rom.
{
"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"
}
Delivered by my Silver S7.
mandroid717 said:
yes i have tried that but adb does not detect device or should i say windows does not see it. it saw it yesterday. i have tried different ports. the cable is new.
Click to expand...
Click to collapse
I eventually was able to get backup installed woohoo
AFTVnews.com said:
Sounds like it's an issue with your PC and/or drivers. Try a different PC if you have access to one, or try deleting all the relevant drivers and start from scratch. Sorry I don't have any other suggestions.
Click to expand...
Click to collapse
Delivered by my Silver S7.
mandroid717 said:
I eventually was able to get backup installed woohooView attachment 3961265
Click to expand...
Click to collapse
Awesome, congrats! Remember to thank (and donate to) @rbox. Without him you would have been hosed and out $90.
AFTVnews.com said:
You're going to have to give us more information. What did you do to it? Is it rooted? Do you have TWRP installed? Is it stuck on the white amazon logo? Does it get to the colorful Fire TV logo? The more information you give, the more likely someone will be able to help.
Click to expand...
Click to collapse
I have a FIRE TV STICK stuck on the white amazon logo, no rooted, How can i solve this?
Is new and never worked.