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.
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
HELLO EVERYONE!
This is how to UnBrick the T-Mobile Samsung Galaxy S II.
Make Sure you Never UnPlug the USB Cable While Flashing!
YOU WILL NEED:
Odin 1.85
USB Drivers
T-Mobile Stock 2.3.6
T-Mobile Stock 4.0.3
You must be really nervous right now. DON'T WORRY! THE MORE YOU STRESS, THE MOST LIKELY YOU WILL MESS UP!
Let's get down to business!
1. Relax, and focus on what you are doing.
2. Now try to put your phone to Download Mode.
A. Take out and put back in the battery. Then, hold Vol + and Vol - , now plug in USB and you will get to this screen.
{
"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"
}
Then, you must press Vol +, and your in Download Mode!
B. Find a G2x USB and check if it puts in download mode while its off. If it doesn't, you will need to use a USB JIG.
IF NON OF THIS OPTIONS WORK, AND YOUR PHONE DOESN'T BOOT, YOU HAVE HARD BRICKED YOUR DEVICE. TO PROVE THIS HAPPENED, PLUG IN YOUR DEVICE AND SEE WHAT THE DEVICE NAME IS ON YOUR PC. SHOULD SAY SOMETHING ABOUT QUALCOMM BOOTLOADERS.
2. Once your in Download Mode, open up Odin 1.85 (Make sure you installed the drivers!) Once in Odin 1.85, Check PDA and look for the downloaded:
T989UVKL1_HOME_SGH-T989user_CL799405_REV00.tar.md5 for 2.3.6.
Tmobile LE1 ICS FULL ROM for 4.0.3.
3. Press Start!
4. Once it's done, it should look like this.
Now, it should reboot to recovery and delete cache and data. Then, it will boot.
Your now on stock, if this didn't work for you, write in the comments, What device you have (T989D or T989) if it went to Download Mode, and what didn't work!
HOW TO ROOT YOUR PHONE
1) Download This Recovery : ClockworkMod TOUCH 5.5.0.4
2) Download The SU Files : SU Files + Superuser
3) Flash SU Files In Recovery.
4) ENJOY
Thanks for your time, this useful. Maybe they could check the battery, before anything. For a real noob guide, add in download links for drivers, odin, and files, etc.
Thanks for this good job.If I can suggest also putting 2.3.5 stock zip up.It is easy to root with superonclick.Then flash a 2.3.6 ROM of your choosing.thanks again.
Edit:Or I guess you can just flash recovery then flash a 2.3.6 rooted ROM to get your root.
From a glaxay better than yours.
asapelectric said:
Thanks for your time, this useful. Maybe they could check the battery, before anything. For a real noob guide, add in download links for drivers, odin, and files, etc.
Click to expand...
Click to collapse
ummmmm... check the download links ! xD
This should be stickied.
Sent from my SGH-T989 using XDA App
jordanishere said:
This should be stickied.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Yay!
10 char
Unfortunately none of these methods here work if you are unfortunate enough to have the black screen and it won't go into download mode, recovery or boot. That my friends is a true brick.
raycaster3 said:
Unfortunately none of these methods here work if you are unfortunate enough to have the black screen and it won't go into download mode, recovery or boot. That my friends is a true brick.
Click to expand...
Click to collapse
That happened to me, somehow the G2x USB saved my phone.
alphadog32 said:
That happened to me, somehow the G2x USB saved my phone.
Click to expand...
Click to collapse
Know of where to buy a real oem usb cable?
——————————
Deebo took your bike too?
The odin pix you have is Odin 3. (Android+SLP) but the the odin 1.85 that is in OP is not the same, after downloading, it shows EPIC 4G and not the same on the op. the pix in the op is the odin i use for vibrant. did i dl the the right odin 1.85?
jay661972 said:
The odin pix you have is Odin 3. (Android+SLP) but the the odin 1.85 that is in OP is not the same, after downloading, it shows EPIC 4G and not the same on the op. the pix in the op is the odin i use for vibrant. did i dl the the right odin 1.85?
Click to expand...
Click to collapse
Its not supposed to look the same, just to show you how it kinda lloks
Exactly what I was thinking...this just fixes a "soft" brick
Did you guys not already have "soft" brick how to in the Dev section
..
raycaster3 said:
Unfortunately none of these methods here work if you are unfortunate enough to have the black screen and it won't go into download mode, recovery or boot. That my friends is a true brick.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I727 using XDA App
what are my options for hard bricked device ?
it hangs on black screen, no download mode no CWM no nothing.
Only when i connect it to the pc in device manager shows qualcomm HS-USB QDLoader9008 ?
Thanks this really helped me.
This worked great after the damn forced OTA locked my phone on the white loading screen. I was so worried I had lost all my xmas pics I just took of my 1 and 2 year old daughters. I followed these instructions exactly and after a reboot all of my data, pics, video are still there. Nothing was lost
Now I just have to reroot, remove readded bloat, etc and can enjoy my phone again. Thanks sooo much.
You welcome!
Sent from my SGH-T989 using XDA App
eniac325ix said:
This worked great after the damn forced OTA locked my phone on the white loading screen. I was so worried I had lost all my xmas pics I just took of my 1 and 2 year old daughters. I followed these instructions exactly and after a reboot all of my data, pics, video are still there. Nothing was lost
Now I just have to reroot, remove readded bloat, etc and can enjoy my phone again. Thanks sooo much.
Click to expand...
Click to collapse
BTW, Try to save your photos on your EXTERNAL SDCard, not your internal. It would save you from important things like this!!
Sent from my SGH-T989 using XDA App
omegaart said:
what are my options for hard bricked device ?
it hangs on black screen, no download mode no CWM no nothing.
Only when i connect it to the pc in device manager shows qualcomm HS-USB QDLoader9008 ?
Click to expand...
Click to collapse
You can call tmobile and see if they'll replace it, and/or buy a new one?
I called T-Mobile meself.
omegaart said:
what are my options for hard bricked device ?
it hangs on black screen, no download mode no CWM no nothing.
Only when i connect it to the pc in device manager shows qualcomm HS-USB QDLoader9008 ?
Click to expand...
Click to collapse
Try to connect my device with no battery with both volume buttons pressed
Sent from my SGH-T989 using XDA App
alphadog32 said:
Try to connect my device with no battery with both volume buttons pressed
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
im stuck at setupconnection..
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.
Long story. I downloaded the Nexus rootkit and unlocked my bootloader in an attempt to root my device. I installed TWRP and erased all my device information without making a backup. During intallation something happened with the toolkit(I believe the program froze or I just got too impatient, so I disconnected the USB). Mind you at this point I had not installed any third party roms yet resides TWRP which I don't even know if it installed completely because after I disconnected the screen turned into bright static.
So after mindlessly disconnecting my phone the entire screen went blank or was static. I could not see anything, so I sent it to LG for repair. They fixed the screen, but the phone is still without an operating system because I wiped it when I had TWRP and I now see this after it loads https://goo.gl/photos/pNZz2XgpQ2oA3SMN6 I don't know what else they did over there because I no longer have TWRP. I also have a locked bootloader now. I attached some screen shots of what options I get when I turn on the phone and the other options I see. which include the bootloader and recovery screen.
https://goo.gl/photos/w7QnfuqtbNGirQuE9
https://goo.gl/photos/58XmdAiMwmdvGfr29
I have tried using the rootkit to install stock rom, but that requires an unlocked bootloader which I don't have. I also tried fastboot oem unlock, but it says failed. Also, I have tried installing the right drivers... It's hard to tell whether or not I have the correct drivers. Under device manager. I am seeing; Android Device--- LG Android Interface. I don't think these drivers work though because I can't pull up my device details in ADB (I am now able to do this thanks to some help in the forum)
EDIT: I fixed the driver issues, This involved manually assigning drivers TWICE through device manager. I had to assign them when I was in the bootloader and again when I went into recovery on my android device. Windows 8.1 recognized the device as 2 different devices based on what screen (bootloader vs recovery). Thus make sure to manually update your drivers twice. Once in bootloader and again in recovery. I am also using the latest android SDK platform tools.
I am now having trouble doing "adb sideload file.zip"... My device keeps rejecting googles OTA files saying signature verification failed https://goo.gl/photos/9UURn9To33YdZM7B7
I also get this error in CMD https://goo.gl/photos/dRvUS3bB5saGehX1A
EDIT: added more details
Last edit: Solved!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
So none of the OTA roms from google worked in ADB sideload etc, but for whatever reason when I sideloaded a custom ROM it installed just fine... No sig verifications errors in recovery mode... I used http://forum.xda-developers.com/nexus-5x/development/rom-pure-nexus-layers-fi-wifi-calling-t3244601 <---- After downloading this custom rom file, I moved it over to my SDK platform tools folder (you could also use the adb folder in your C drive if you went about installing those adb drivers)
Next, I started bootloader on my android device by pressing power and volume down buttons. I then navigated to recovery by using the volume keys. once in recovery, I selected apply update from ADB. I am now done with the phone.
I opened up command prompt from my PC using shift/right click from the appropriate folder (c/adb or platform tools folder). further, I opened command prompt and typed in "adb sideload pure_nexus_bullhead-6.0-20151109.zip" the flash was successful.
The first boot was not perfect. I recieved a error in regards to something about a manufacture error, but it was enough for me to get into the OS and enable OEM unlocking. I am now able to move forward and unlock the bootloader with rootkit or fastboot. After unlocking the boot loader I went back to a factory ROM which now installed with no problem.
Holly crap. Anyways huge thanks to everyone on this thread you guys are awesome I could not have done it without you.
XDA 4 life
Can you be a little more specific? what were you flashing and what steps did you follow?
Bootloader
metpage said:
Can you be a little more specific? what were you flashing and what steps did you follow?
Click to expand...
Click to collapse
ideaman924 said:
Please include:
Details of what you were doing
A screenshot (or a camera shot from another phone)
What things you flashed
What the phone was running prior to flashing
Your device model (just in case we need to recommend tot files)
If possible, a recent backup from TWRP
We cannot help without these things. Thanks!
Click to expand...
Click to collapse
Ok so here is the long story. I downloaded the Nexus rootkit and unlocked my bootloader in an attempt to root my device. I got half way through installing TWRP and erasing all my device information when my computer froze or something happened with the toolkit(I believe the program froze, so I disconnected). Mind you at this point I had not installed any third party roms or etc besides TWRP.
So after disconnecting my phone the entire screen went blank and was static. I could not see anything, so I sent it to LG for repair. They fixed the screen, but the phone is still without a operating system. I don't know what else they did over there because I no longer have TWRP. I have a locked bootloader now and no OS. I attached some screen shots of what options I get when I turn on the phone and the other options I see.
{
"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 tried using the rootkit to install stock rom, but that requires an unlocked bootloader which I don't have. Also, I have tried installing the right drivers... It's hard to tell whether or not I have the correct drivers. Under device manager. I am Android Device--- LG Android Interface. I don't think these drivers work though because I can't pull up my device details in ADB, but that could also be because everything is wiped on the device...
I also have the latest SDK installed from google.
For the most part I am a noob, I know, but I ain't going down without a fight.
more pics
Nebula666 said:
Ok so here is the long story. I downloaded the Nexus rootkit and unlocked my bootloader in an attempt to root my device. I got half way through installing TWRP and erasing all my device information when my computer froze or something happened with the toolkit(I believe the program froze, so I disconnected). Mind you at this point I had not installed any third party roms or etc besides TWRP.
So after disconnecting my phone the entire screen went blank and was static. I could not see anything, so I sent it to LG for repair. They fixed the screen, but the phone is still without a operating system. I don't know what else they did over there because I no longer have TWRP. I have a locked bootloader now and no OS. I attached some screen shots of what options I get when I turn on the phone and the other options I see.
I have tried using the rootkit to install stock rom, but that requires an unlocked bootloader which I don't have. Also, I have tried installing the right drivers... It's hard to tell whether or not I have the correct drivers. Under device manager. I am Android Device--- LG Android Interface. I don't think these drivers work though because I can't pull up my device details in ADB, but that could also be because everything is wiped on the device...
I also have the latest SDK installed from google.
For the most part I am a noob, I know, but I ain't going down without a fight.
Click to expand...
Click to collapse
I do get these options by holding down the power key and volume down
Nebula666 said:
I do get these options by holding down the power key and volume down
Click to expand...
Click to collapse
You're booting into the bootloader which is a good start. Using the vol keys can you go to recovery? Is it the stock recovery. Also,I think your drivers are correct. When booted into the boot loader you need to use fastboot commands, not adb, i.e. fastboot devices
Edit, I see from your second image it's the stock recovery. Try loading the ota from here, https://developers.google.com/android/nexus/ota#bullhead
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You're booting into the bootloader which is a good start. Using the vol keys can you go to recovery? Is it the stock recovery. Also,I think your drivers are correct. When booted into the boot loader you need to use fastboot commands, not adb, i.e. fastboot devices
Edit, I see from your second image it's the stock recovery. Try loading the ota from here, https://developers.google.com/android/nexus/ota#bullhead
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
So I tried using fastboot devices and nothing comes up.. I am going to try reinstalling all the SDK/drivers on a different computer. Maybe that will help.
Are you booted into the bootloader when you run fastboot devices? Power and vol down keys then stay on the screen with Start on it.
Sent from my Nexus 9 using XDA Free mobile app
Ok I think I am connected now...
Device manager is showing my device as
Android Devices
---Android Bootloader Interface
It is also now recognized in CMD.. before it would not show up.
jd1639 said:
Are you booted into the bootloader when you run fastboot devices? Power and vol down keys then stay on the screen with Start on it.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Ok I am not sure what to do now as the google directions advise me to use ADB reboot recovery and that doesnt work...
Just boot into the bootloader then use the vol keys to go to recovery
It's the same screen as the second image you posted.
Sent from my Nexus 5X using XDA Free mobile app
Ok so I tried running in recovery mode... I selected apply update from from ADB.... Than I ran the following command adb sideload (ota file.zip) from CMD and I got this error
"ERROR: DEVICE '(NULL)' NOT FOUND"
jd1639 said:
Just boot into the bootloader then use the vol keys to go to recovery
It's the same screen as the second image you posted.
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
See above, I get this message "ERROR: DEVICE '(NULL)' NOT FOUND"
You get that error on your pc? I'm not sure what to tell you.
You got the device back from being repaired in this condition?
Sent from my Nexus 5X using XDA Free mobile app
jd1639 said:
You get that error on your pc? I'm not sure what to tell you.
You got the device back from being repaired in this condition?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
I get that error message from cmd after imputing adb sideload "ota file"
Nebula666 said:
I get that error message from cmd after imputing adb sideload "ota file"
Click to expand...
Click to collapse
You can't side load the ota if you don't have an OS installed. Download the the stock image from Android site and flash those images to get your device working. You need to be on the bootloader to flash them.
Sent from my Nexus 5X using Tapatalk
Nebula666 said:
I get that error message from cmd after imputing adb sideload "ota file"
Click to expand...
Click to collapse
While your phone is in the stock recovery and plugged into your computer type:
adb devices
What is the output?
Sent from my SM-G930V using Tapatalk
---------- Post added at 06:01 PM ---------- Previous post was at 05:43 PM ----------
metpage said:
You can't side load the ota if you don't have an OS installed. Download the the stock image from Android site and flash those images to get your device working. You need to be on the bootloader to flash them.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
The OTA updates Google is supplying us are not simply delta updates. They are the full package. Google is doing it this way because the developer preview OTA was borking locked devices. The OP indicated that he is still locked. Oddly since he was flashing TWRP when this ****uation started. But that's the info we were given.
Sent from my SM-G930V using Tapatalk
Half way solved
metpage said:
You can't side load the ota if you don't have an OS installed. Download the the stock image from Android site and flash those images to get your device working. You need to be on the bootloader to flash them.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
PiousInquisitor said:
While your phone is in the stock recovery and plugged into your computer type:
adb devices
What is the output?
Sent from my SM-G930V using Tapatalk
Click to expand...
Click to collapse
Ok here is what is going on.... It was definitely a driver issue. I had the drivers successfully installed when I was in bootloader, but as soon as I went to recovery mode on android my computer would no longer recognize the drivers, so I had to manually reinstall them again for recovery mode. Now I have access... I did another attempt at adb sideload "ota.zip" that I downloaded from googles OTA site , but I am getting a signature error on my android and abort message on android here
Am i suppose to unzip this file or leave it zip? When I unzip all I see is a bunch of .img files not zny zips so maybe I am missing something here.
So google has two download links for the OTA, I am trying the other one now without unzipping it.
Alright so the second file I downloaded is giving me the same verification errors in recovery... I am going to try one last thing before I try blending the phone.
There is hope ahead! i think I downloaded the wrong OTA from the google website. The nexus 5x and 6p have the same descriptions. Hopefully this solves the problem. I am literally ready to throw this phone in the blender and call it a day
I have been searching and reading quite a bit here on the forums trying to find an answer to this problem. I haven't found a thread that answers my question, though I've seen many threads with different things I can try. I explain the problem and what I've tried to do to fix the problem here.
The problem:
I decided to give IronRom a try on my tablet. I installed the following:
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
Everything worked great for about 2 weeks. However, one day I went to turn on the tablet and I was stuck in a boot loop. I could get to the Samsung Galaxy Tab S screen but no further before the tablet would reboot.
Here is what I've tried to fix the problem:
1. First I tried going into TWRP to do a full wipe. I cannot get the tablet to enter recovery mode. Power/Home/Volume Up does nothing. I can get the tablet to enter download mode through Power/Home/Volume Down.
2. Using Odin I tried reflashing TWRP but no matter what I did, I couldn't get into recovery.
3. Using Odin I went over to SamMobile and got my stock rom. I flashed it and according to Odin, it was a success. But when it auto rebooted, it brought up the Samsung screen once, rebooted and now I'm stuck with the logo screen on all the time. Holding the power button does not turn the tablet off. I can still get into download mode though.
Pic of Odin:
{
"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"
}
Video of what the tablet is doing:
https://youtu.be/_hFiEhtQtZs
At this point I need suggestions. I'm not seeing any .pit errors but am not sure that would be worth pursuing. If I do, I'll need a little help learning how to do that.
QUOTE=Drschplatt;69922876]I have been searching and reading quite a bit here on the forums trying to find an answer to this problem. I haven't found a thread that answers my question, though I've seen many threads with different things I can try. I explain the problem and what I've tried to do to fix the problem here.
The problem:
I decided to give IronRom a try on my tablet. I installed the following:
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
Everything worked great for about 2 weeks. However, one day I went to turn on the tablet and I was stuck in a boot loop. I could get to the Samsung Galaxy Tab S screen but no further before the tablet would reboot.
Here is what I've tried to fix the problem:
1. First I tried going into TWRP to do a full wipe. I cannot get the tablet to enter recovery mode. Power/Home/Volume Up does nothing. I can get the tablet to enter download mode through Power/Home/Volume Down.
2. Using Odin I tried reflashing TWRP but no matter what I did, I couldn't get into recovery.
3. Using Odin I went over to SamMobile and got my stock rom. I flashed it and according to Odin, it was a success. But when it auto rebooted, it brought up the Samsung screen once, rebooted and now I'm stuck with the logo screen on all the time. Holding the power button does not turn the tablet off. I can still get into download mode though.
Pic of Odin:
Video of what the tablet is doing:
https://youtu.be/_hFiEhtQtZs
At this point I need suggestions. I'm not seeing any .pit errors but am not sure that would be worth pursuing. If I do, I'll need a little help learning how to do that.[/QUOTE]
hi, just buy a micro USB JIG on eBay and you will get into the download mode to flash a stock rom with Odin... I did have the same problem and I solve it with the JIG !:good:
http://www.ebay.de/itm/151703102753
sorry for my English
---------- Post added at 06:22 PM ---------- Previous post was at 06:09 PM ----------
I have been searching and reading quite a bit here on the forums trying to find an answer to this problem. I haven't found a thread that answers my question, though I've seen many threads with different things I can try. I explain the problem and what I've tried to do to fix the problem here.
The problem:
I decided to give IronRom a try on my tablet. I installed the following:
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
Everything worked great for about 2 weeks. However, one day I went to turn on the tablet and I was stuck in a boot loop. I could get to the Samsung Galaxy Tab S screen but no further before the tablet would reboot.
Here is what I've tried to fix the problem:
1. First I tried going into TWRP to do a full wipe. I cannot get the tablet to enter recovery mode. Power/Home/Volume Up does nothing. I can get the tablet to enter download mode through Power/Home/Volume Down.
2. Using Odin I tried reflashing TWRP but no matter what I did, I couldn't get into recovery.
3. Using Odin I went over to SamMobile and got my stock rom. I flashed it and according to Odin, it was a success. But when it auto rebooted, it brought up the Samsung screen once, rebooted and now I'm stuck with the logo screen on all the time. Holding the power button does not turn the tablet off. I can still get into download mode though.
Pic of Odin:
Video of what the tablet is doing:
https://youtu.be/_hFiEhtQtZs
At this point I need suggestions. I'm not seeing any .pit errors but am not sure that would be worth pursuing. If I do, I'll need a little help learning how to do that.
Click to expand...
Click to collapse
hi, just buy a micro USB JIG on eBay and you will get into the download mode to flash a stock rom with Odin... I did have the same problem and I solve it with the JIG !:good:
http://www.ebay.de/itm/151703102753
sorry for my English
I appreciate the reply, but I am already able to get into download mode and can connect my tablet using Odin. I was even able to flash the stock rom as the photo in my post showed. So I'm a little confused. How is a jig going to help me? Isn't that just for accessing download mode?
What I cannot access is recovery.
Drschplatt said:
I have been searching and reading quite a bit here on the forums trying to find an answer to this problem. I haven't found a thread that answers my question, though I've seen many threads with different things I can try. I explain the problem and what I've tried to do to fix the problem here.
Click to expand...
Click to collapse
Do you have android SDK tools installed on your PC? If you do you can connect your tablet to your PC via USB and enter in the command prompt, "adb reboot recovery". If it reboots to recovery you can try doing a factory reset.
Sent from my SM-T800 using XDA-Developers mobile app
Eddie Hicks said:
Do you have android SDK tools installed on your PC? If you do you can connect your tablet to your PC via USB and enter in the command prompt, "adb reboot recovery". If it reboots to recovery you can try doing a factory reset.
Sent from my SM-T800 using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't, but I'd be very happy for a little info on how that process works. Do you know of a guide for that off hand? I can google it course .
Drschplatt said:
I don't, but I'd be very happy for a little info on how that process works. Do you know of a guide for that off hand? I can google it course .
Click to expand...
Click to collapse
If you're new to it, it may seem a little complicated at first but really isn't. Here is a good start on XDA that explains a lot. http://forum.xda-developers.com/showthread.php?t=2317790 There are links there for the software. One tip, if you know how to add a folder to your Window's path, add the folder with the sdk files to it. That way you can run the command anywhere on your PC. If not, open the folder with the files, hold the shift key and right click in the folder and choose "open command window here" I was able to fix an ASUS tablet that I almost threw away because of a similar issue. Good luck.
Eddie Hicks said:
If you're new to it, it may seem a little complicated at first but really isn't. Here is a good start on XDA that explains a lot. http://forum.xda-developers.com/showthread.php?t=2317790 There are links there for the software. One tip, if you know how to add a folder to your Window's path, add the folder with the sdk files to it. That way you can run the command anywhere on your PC. If not, open the folder with the files, hold the shift key and right click in the folder and choose "open command window here" I was able to fix an ASUS tablet that I almost threw away because of a similar issue. Good luck.
Click to expand...
Click to collapse
Just a question. If I cannot get the device to boot past the samsung screen, and I can only get into download mode on the device, how am I supposed to get the SDK tools to connect to my device?
Odin will connect, but my computer doesn't recognize the tablet as a storage device or anything. Maybe I'm just not understanding how SDK works. All I'm getting are errors saying no device was found.
Drschplatt said:
Just a question. If I cannot get the device to boot past the samsung screen, and I can only get into download mode on the device, how am I supposed to get the SDK tools to connect to my device?
Odin will connect, but my computer doesn't recognize the tablet as a storage device or anything. Maybe I'm just not understanding how SDK works. All I'm getting are errors saying no device was found.
Click to expand...
Click to collapse
I haven't been using ADB for awhile and I forgot the particulars. I just tried ADB rebooting to recovery from download mode and it doesn't work. Did you enable USB debugging in Developers options? If not in setting go to about device, tap on build number about 7 times and it will let you access Developers options, there you can enable USB debugging. You may also need to install drivers for your tablet if you already haven't. I forgot did you say your tablet reboots to download mode or you use your buttons? If you can get to any screen besides download you can try ADB reboot to recovery from there. There is a lot of things you can do like install recoveries if you can only get ADB and fastboot to recognize your tablet. There are other people who are way more knowledgeable with ADB than I am. Maybe you can search around for advice. Sorry if I got your hopes up and it doesn't work but I guess it never hurts to try.