Alright. My current phone I was using broke (screen cracked) and I decided to use my old phone, the Droid Razr to get me by until I get a new phone. My Razr was previously rooted on JB when I left it a few years back. It works fine, except it was running slow. It had bootstrap and Safestrap installed. I'm pretty sure at the original time of getting JB on the razr, you had to use bootstrap first and then switch to Safestrap since its safer? However, I forgot this at the time. I wanted to try clearing the cache on the phone to see if it sped it up. However, I guess I uninstalled safestrap and switched it to bootstrap because i used the bootstrap recovery out of ignorance. When I turn on the phone, I get the "Encryption Unsuccessful" message.
I've tried doing the format option it gives but it just restarts the same every time. I've done some researching and it appears I've soft bricked it. I've been reading that the only way to fix it is by using fastboot to wipe the phone to factory settings. I have all the necessary files to do so. I've been working on this for about two days now. However, fastboot does not seem to recognize my phone. I have the drivers installed. When I plug it in normally when it is not in fastboot mode, my PC shows the XT912 under hardware plugged in via USB. But when I put it in fastboot mode, it does not recognize it and it isn't shown in my ADB devices list. What do I do here? I really need this phone to work and I am willing to do whatever it takes to it. I don't care if I have to wipe it/lose root any of that. Please help me. Im not one to make threads of issues that others have but no one elses thread has helped me.
MeltingHolster said:
Alright. My current phone I was using broke (screen cracked) and I decided to use my old phone, the Droid Razr to get me by until I get a new phone. My Razr was previously rooted on JB when I left it a few years back. It works fine, except it was running slow. It had bootstrap and Safestrap installed. I'm pretty sure at the original time of getting JB on the razr, you had to use bootstrap first and then switch to Safestrap since its safer? However, I forgot this at the time. I wanted to try clearing the cache on the phone to see if it sped it up. However, I guess I uninstalled safestrap and switched it to bootstrap because i used the bootstrap recovery out of ignorance. When I turn on the phone, I get the "Encryption Unsuccessful" message.
I've tried doing the format option it gives but it just restarts the same every time. I've done some researching and it appears I've soft bricked it. I've been reading that the only way to fix it is by using fastboot to wipe the phone to factory settings. I have all the necessary files to do so. I've been working on this for about two days now. However, fastboot does not seem to recognize my phone. I have the drivers installed. When I plug it in normally when it is not in fastboot mode, my PC shows the XT912 under hardware plugged in via USB. But when I put it in fastboot mode, it does not recognize it and it isn't shown in my ADB devices list. What do I do here? I really need this phone to work and I am willing to do whatever it takes to it. I don't care if I have to wipe it/lose root any of that. Please help me. Im not one to make threads of issues that others have but no one elses thread has helped me.
Click to expand...
Click to collapse
Windows 7? 8? 10?
Did you tried all usb ports?
Uninstall all moto drivers,reboot computer,install them again.
Here are the newest moto drivers
http://forum.xda-developers.com/showthread.php?p=59139823
Sent from my Razr XT910
Thanks for the quick reply. I'm using Windows 8.1. I did what you asked, and when I turned my phone on after re-installing the drivers, it installed the device normally. It shows this in device manager.
{
"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"
}
It still wont recognize it in ADB.
MeltingHolster said:
Thanks for the quick reply. I'm using Windows 8.1. I did what you asked, and when I turned my phone on after re-installing the drivers, it installed the device normally. It shows this in device manager.
It still wont recognize it in ADB.
Click to expand...
Click to collapse
That's a common problem with Windows 8,on Windows 7 everything is ok
Sent from my Razr XT910
So that means i cant fix it?
Sent from my SM-T217S using XDA Free mobile app
MeltingHolster said:
So that means i cant fix it?
Sent from my SM-T217S using XDA Free mobile app
Click to expand...
Click to collapse
You can fix it with Windows 7
Sent from my Razr XT910
MeltingHolster said:
So that means i cant fix it?
Sent from my SM-T217S using XDA Free mobile app
Click to expand...
Click to collapse
What is on AP Fastboot screen, complete text?
sd_shadow said:
What is on AP Fastboot screen, complete text?
Click to expand...
Click to collapse
It says AP Fastboot Flash Mode (S)
0A.77
eMMC Info: Size 16GB
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Transfer Mode:
USB Connected
Related
Installed cm via directions. No problems. Decided to try installing a new Android kernel. Flashed via recovery.
Moboot, but couldn't get into any os, not even recovery. Eventually got into Android. Was able after many attempts to get to webos. Decided to try and reinstall cm9 and such. Plugged into computer while in webos to move files over and got a need to format window. Hit yes (i know, I know).
Now can't even get moboot. Decide to Dr it. Gets to 12% and doesn't move. Google it and follow some novaterm/cmd directions.
Now Dr gets to 8% and says unable to reset device. Have a hard time getting into HP recovery (usb symbol). Mostly get an exclamation point in a triangle and the url for Dr.
What r my options, HP warranty? Thx
Sent from my PG86100 using XDA App
The cm team can help you on IRC here's info I copied from the cm thread go here and they should get you right http://webchat.freenode.net?channels=cyanogenmod-touchpad
The reason the doctor is failing is because Android messes with your partitions and at 12% the webOS doctor is verifying partitions. Have you attempted ACMEUninstaller? When at the webOS screen go ahead and run ACMEUinstaller. Then if uoi can boot into webOS do the complete wipe to wipe the entire SD section. Then doctor it and then reflash Android with ACMEinstaller2
Sent from T the Touchpad
Eat it iPhone said:
Installed cm via directions. No problems. Decided to try installing a new Android kernel. Flashed via recovery.
Moboot, but couldn't get into any os, not even recovery. Eventually got into Android. Was able after many attempts to get to webos. Decided to try and reinstall cm9 and such. Plugged into computer while in webos to move files over and got a need to format window. Hit yes (i know, I know).
Now can't even get moboot. Decide to Dr it. Gets to 12% and doesn't move. Google it and follow some novaterm/cmd directions.
Now Dr gets to 8% and says unable to reset device. Have a hard time getting into HP recovery (usb symbol). Mostly get an exclamation point in a triangle and the url for Dr.
What r my options, HP warranty? Thx
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
lucky for us, the TP can never be bricked unless you start to manually edit partition tables (and even then, its fixable with much hair pulling, ive personally troubleshooted this with a friend before )
maybe these threads can help you out:
http://forum.xda-developers.com/showthread.php?t=1236727&page=2.
http://forum.xda-developers.com/showthread.php?t=1379579
it really helps to have a grasp on how novaterm works, and ALWAYS ALWAYS re read your commmands to ensure you typed it correctly (upper/lower case espicially ;P)
Thx guys ill look into it, but I'ma be busy so ill have to chk this out tomorrow
Sent from my PG86100 using XDA App
http://forum.xda-developers.com/showthread.php?t=1426244
Try it. It may just work.
rr5678 said:
http://forum.xda-developers.com/showthread.php?t=1426244
Try it. It may just work.
Click to expand...
Click to collapse
oh god, that brings back terrible memories of "unbricking" my buddies TP from scratch using mine as a reference
and yes, Eat it iPhone, this is the best last alternative for repair, you will be restored to 100% BNIB (or LNIB as the case would be )
Solidus_n313 said:
oh god, that brings back terrible memories of "unbricking" my buddies TP from scratch using mine as a reference
and yes, Eat it iPhone, this is the best last alternative for repair, you will be restored to 100% BNIB (or LNIB as the case would be )
Click to expand...
Click to collapse
It may be horrible but in the end it's worth it
P.S.: I read that link in your signature (The TRUTH: XDA: Then and Now), and all I have to say is.....
{
"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"
}
im still wating for a complete recovery without bootie... which doesnt evn turn on the screen.heh
as said before more likely than not its a currupted partition that its stoping on...
darkassain said:
im still wating for a complete recovery without bootie... which doesnt evn turn on the screen.heh
as said before more likely than not its a currupted partition that its stoping on...
Click to expand...
Click to collapse
There is no recovery from a missing bootie (not that I know of). A missing bootie is like a missing hboot.
rr5678 said:
There is no recovery from a missing bootie (not that I know of). A missing bootie is like a missing hboot.
Click to expand...
Click to collapse
yep there is a way, you just havent heard of it (the pre has a way to boot from a corrupted bootie too)...
you can boot directly from the usb into the cpu bypasing bootie (instead of power + vol-up to enter bootie try it with vol-down while connected to a pc , and you will get what i mean..)
work has been done on this but a working product hasnt...
also is the hboot in nand or rom (im gueasing the nand /boot partiton just as with the few android devices i have worked on)
darkassain said:
yep there is a way, you just havent heard of it (the pre has a way to boot from a corrupted bootie too)...
you can boot directly from the usb into the cpu bypasing bootie (instead of power + vol-up to enter bootie try it with vol-down while connected to a pc , and you will get what i mean..)
work has been done on this but a working product hasnt...
also is the hboot in nand or rom (im gueasing the nand /boot partiton just as with the few android devices i have worked on)
Click to expand...
Click to collapse
No, the Pre is a completely different device. The Pre has an OMAP3430, while the TouchPad has your typical (non-USB bootable) Qualcomm processor.
And hboot is in the nand. (but still erasable)
rr5678 said:
No, the Pre is a completely different device. The Pre has an OMAP3430, while the TouchPad has your typical (non-USB bootable) Qualcomm processor.
And hboot is in the nand. (but still erasable)
Click to expand...
Click to collapse
doesnt matter boot with power+voldown and you enter qualcomm recovery which can boot from usb....
ps should have said that this only works on the TP
pps should mention that other qualcomm devices can boot from usb too...
darkassain said:
doesnt matter boot with power+voldown and you enter qualcomm recovery which can boot from usb....
ps should have said that this only works on the TP
pps should mention that other qualcomm devices can boot from usb too...
Click to expand...
Click to collapse
If you're talking about QHSUSB_DLOAD, there is no known way to use that. No image files, nothing.
rr5678 said:
If you're talking about QHSUSB_DLOAD, there is no known way to use that. No image files, nothing.
Click to expand...
Click to collapse
which is why i mentioned in two different posts that that its "not working" and why "im waiting" for something like this...
it works on some phones though which means it will communicate
darkassain said:
which is why i mentioned in two different posts that that its "not working" and why "im waiting" for something like this...
it works on some phones though which means it will communicate
Click to expand...
Click to collapse
I wish it was known what to do though. That's a super low level function.
Last year i tried to disassembly the phone to fix a probably broken audio conector, then i decided to flash a new rom; since then, i'm facing bootloop. I tried to enter into recovery and simply doesn't go there. Download Mode works just fine, so i decided to flash a new stock rom and a TWRM (latest) and the system almost worked. I could enter Recovery Mode, but when i was about to try a factory reset, the touch stopped working. So i rebooted again, then a white screen (that first one that appears, with AT&T logo on it) appeared my phone rebooted.
I flashed a stock recovery but didn't had any sucess either...
Now i'm with a galaxy note 3 (n900) and my phone is in the shelter, completely useless.
Try an emergency recovery with kies.
440bro said:
Try an emergency recovery with kies.
Click to expand...
Click to collapse
Thanks for answering, but it was no use for me.
I can only enter download mode now and my device didn't shown on that list.
Thanks, though.
You only need to be in download mode for kies to work.
Don't use kies 3 that the note 3 uses. Use the original one. Make sure it's up to date. Reinstall the i717 drivers from Samsung. Put phone on download mode and plug into pc. Open kies and click "emergency firmware recovery" type in all caps SGH-I717. Then type in serial number and let it do it's thing!
440bro said:
You only need to be in download mode for kies to work.
Don't use kies 3 that the note 3 uses. Use the original one. Make sure it's up to date. Reinstall the i717 drivers from Samsung. Put phone on download mode and plug into pc. Open kies and click "emergency firmware recovery" type in all caps SHG-I717. Then type in serial number and let it do it's thing!
Click to expand...
Click to collapse
{
"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"
}
Here's a screenshot of what it looks like when i do EXACTLY as you told me to.
Also, it's a recently formatted computer, so isn't any driver conflict or thinks like that.
Here's a screenshot of what it looks like when i do EXACTLY as you told me to.
Also, it's a recently formatted computer, so isn't any driver conflict or thinks like that.[/QUOTE]
Try clicking "Firmware upgrade and initialisation" instead of "emergency recovery". I might of told you wrong. I apologize. It's been awhile since I've needed to fix my i717. I moved on to note 3.
440bro said:
Here's a screenshot of what it looks like when i do EXACTLY as you told me to.
Also, it's a recently formatted computer, so isn't any driver conflict or thinks like that.
Try clicking "Firmware upgrade and initialisation" instead of "emergency recovery". I might of told you wrong. I apologize. It's been awhile since I've needed to fix my i717. I moved on to note 3.
Click to expand...
Click to collapse
Firmware upgrade is what you want. The only problem I had was Kies didn't like my serial number. Luckily my wife has a OG Note and I used her sn with no problems Good luck!
Here's a screenshot of what it looks like when i do EXACTLY as you told me to.
Also said:
440bro said:
Here's a screenshot of what it looks like when i do EXACTLY as you told me to.
Also, it's a recently formatted computer, so isn't any driver conflict or thinks like that.
Click to expand...
Click to collapse
Try clicking "Firmware upgrade and initialisation" instead of "emergency recovery". I might of told you wrong. I apologize. It's been awhile since I've needed to fix my i717. I moved on to note 3.
Click to expand...
Click to collapse
Just did that and still the same problem.
Type in SGH-I717 not SHG-I717. Hopefully you caught that typo.
Agoattamer said:
Type in SGH-I717 not SHG-I717. Hopefully you caught that typo.
Click to expand...
Click to collapse
Whoops! Good eye!!
i am also having same issue .. kies says SGH-I717 not support initializing
Agoattamer said:
Type in SGH-I717 not SHG-I717. Hopefully you caught that typo.
Click to expand...
Click to collapse
Unfortunately, it wasn't the case. I double check it before installing.
Maybe it's soft bricked.
Using odin to get you into download mode (not recovery), and flash a stock .tar file to get up and running again. Unless you have a hardware issue inside the phone.
If you want a decent tutorial on doing this, YouTube search "unbrick i717 odin" and the first video listed (for me anyway) is a video by Qbking77 on how to do this step by step. He gives links to odin files and .tar stock files for the i717.
hello guys
sorry for my bad English.
i have a LG P760 for about 6 months, bought it second hand from a friend. the phone had troubles from the beginning with starting up. every time when you started the phone, it couldn't get any furder than the lg logo, so i had to take out the battery, and start the phone again, this happened several times before the lg started.
last time i had this problem, it took me forever, placed the battery like 30 times in and out, so i did a factory reset, but while resetting, the phone died, and i wasn't able to get it back on.. not even with the special key combinations. so i searched around the net for a solution and found one. but when i tried and connected the phone to the pc with a usb cabel holding the up button, i got errors of coprocessor and omap4430, so i installed them both, and tried again. so now the omap4430 keeps connecting and disconnecting, so i can't connect my lg to the pc..
plz help me..
cheerz
pc:
windows 7 ultimate 64-bit
AMD Phenom II X4 955 3.2GHz
Radeon HD 7790 Direct CU II OC 1GB
4GB RAM
Ok. This can probably be fixed with a recovery update. Make sure you have the latest lg mobile support tool installed on your pc. Then, power your phone off. I should say that after doing this, it WILL wipe EVERYTHING off your phone... so back up your contacts somehow. So, once youve got the support thing on your pc, open that up. Now plug the usb end of your charging cable to your pc. While holding the UP volume button on your l9, plug in the phone end. Don't do anything until the software upgrade screen pops up on your phone. Then let go of VOL +. Your pc should be installing drivers now, wait till those are done if any. Once the lg support tool says your phone is connected, there should be a drop down in the top right. Click that and click the recovery update option. (I think thats what its called, you should figure it out) then let it work its magic and once your phone reboots you should be set. What this did is wiped the phone COMPLETELY, and reinstalls the OS. Good luck!
Sent from my LG-P769 using XDA Free mobile app
Bacon_Noodles said:
Ok. This can probably be fixed with a recovery update. Make sure you have the latest lg mobile support tool installed on your pc. Then, power your phone off. I should say that after doing this, it WILL wipe EVERYTHING off your phone... so back up your contacts somehow. So, once youve got the support thing on your pc, open that up. Now plug the usb end of your charging cable to your pc. While holding the UP volume button on your l9, plug in the phone end. Don't do anything until the software upgrade screen pops up on your phone. Then let go of VOL +. Your pc should be installing drivers now, wait till those are done if any. Once the lg support tool says your phone is connected, there should be a drop down in the top right. Click that and click the recovery update option. (I think thats what its called, you should figure it out) then let it work its magic and once your phone reboots you should be set. What this did is wiped the phone COMPLETELY, and reinstalls the OS. Good luck!
Sent from my LG-P769 using XDA Free mobile app
Click to expand...
Click to collapse
first of all, thanks for the reply! but i think you miss understood the problem here. since the phone died, it does not respond on anything.. could it be that the phone fully bricked? when i open lg mobile support tool, and plug it into usb, with the up botton to get in to SW mode like you say, the phone keeps connecting and disconnecting.. on lg support tool, there is nothing happening.. just connecting and disconnecting like 10-12 times...
You might want to look into what installing fastboot drivers imply, if I recall correctly they include drivers for the omap4430 device, once you can get into fastboot and hopefully have your device show up there in your PC screen, you might be able to push a custom recovery or try to reboot the phone via commands.
Its one of those issues you need to be there to try and fix, sorry if I'm not helping much.
Sent from my LG-P768 using XDA Premium 4 mobile app
plz, someone help me
Xkore16 said:
plz, someone help me
Click to expand...
Click to collapse
Hi Xkore16, you could try this way http://forum.xda-developers.com/showthread.php?p=53709440
Cheers. Good luck.
Sent from my LG P76020p-EUR-XX unlocked and rooted
BajoPrimate said:
Hi Xkore16, you could try this way http://forum.xda-developers.com/showthread.php?p=53709440
Cheers. Good luck.
Sent from my LG P76020p-EUR-XX unlocked and rooted
Click to expand...
Click to collapse
Hi, thanx for the replie, but it didn't work either
Omap keeps connecting and disconnecting
help plz..
Xkore16 said:
Hi, thanx for the replie, but it didn't work either
Omap keeps connecting and disconnecting
help plz..
Click to expand...
Click to collapse
You're welcome, Xkore16, but you don't need omap with the method provided by me,
?you need LGE CDMA USB Serial Port (COM#). ?
{
"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"
}
Cheers. Good luck.
Sent from my LG P76020p-EUR-XX unlocked and rooted
thanx, and indeed, i haven't.
does it mather wich (COM) version it is?
Xkore16 said:
thanx, and indeed, i haven't.
does it mather wich (COM) version it is?
Click to expand...
Click to collapse
You're welcome, Xkore16;
I'm not sure, but I think it depends on your computer and your used ports, anyway, the important thing is to change it to 41.
Cheers. Good luck.
Sent from my LG P76020p-EUR-XX unlocked and rooted
BajoPrimate said:
You're welcome, Xkore16;
I'm not sure, but I think it depends on your computer and your used ports, anyway, the important thing is to change it to 41.
Cheers. Good luck.
Sent from my LG P76020p-EUR-XX unlocked and rooted
Click to expand...
Click to collapse
I don't have LGE CDMA USB Serial Port.. it is not there under device manager/ports
is there any way to install this port manually?
Xkore16 said:
I don't have LGE CDMA USB Serial Port.. it is not there under device manager/ports
is there any way to install this port manually?
Click to expand...
Click to collapse
Hi Xkore16, you have a link in the OP https://m.app.box.com/view_shared/32c5t7fj2w8xcwr0krjo
Cheers. Good luck.
Sent from my LG P76020p-EUR-XX unlocked and rooted
So tried downloading the 6.0 ota. after it installed it, it got stuck in a bootloop. tried doing factor reset and deleting cache and data.
nothing has worked so far.
heres the rub, i never unlocked my bootloader and i cant get into the OS to set the developer options. it seems my only solution is to RMA it. but im hoping maybe there is a hack of some sort.
heres to hoping.
My N9 wouldnt allow me to even attempt to flash anything when it was locked. One of the first things I had to do was a fastboot oem unlock (which also required me to boot into the OS to toggle that developer option). When you flashed 6.0 did you use the "flash-all" script?
WoodroweBones said:
My N9 wouldnt allow me to even attempt to flash anything when it was locked. One of the first things I had to do was a fastboot oem unlock (which also required me to boot into the OS to toggle that developer option). When you flashed 6.0 did you use the "flash-all" script?
Click to expand...
Click to collapse
No it was an OTA update. got the notification this morning and had it install the update. it obviously didnt take. i have not rooted my tablet or done anything like that. its actually the first device ive ever not rooted....
I had the exact same problem. I installed the OTA last night, and now it sits at the boot animation for hours. I tried to wipe cache, but I got an error saying it couldn't mount the partition. I tried to sideload it, and it failed, saying it couldn't mount it. I just (reluctantly) performed a wipe and hopefully that will work, but I'm not optimistic.
Update: no luck. So I permanently deleted a lot of stuff for no reason. =/
Yeah my problem is I can't sideload because my computer doesn't recognize it . I mean this whole unlocking the boot loader from within the OS thing is the stupidest design I've ever seen.....
since i can still get into hboot and fastboot can i side load the OTA? adb isnt seeing it in recovery but it sees it in fastboot.
I was not able to sideload anything. I could see the device, I could start the process, but it would fail every time. I talked to HTC last night and they are going to replace it.
Weirdly, when I was talking with them, they had me try to clear the cache and it actually worked, so I'm going to try and sideload it one more time tonight and if it doesn't work, just swap it out.
I'm caught in the boot loop as well after having downloaded the OTA... I must say, over the past couple weeks I was stuck in boot loops on several occasions, and only after a bunch of restarts would it load fully (and "update apps").
When this device works properly, I have no qualms. But it's incredibly irritating for a $600 tablet to be so shoddy...
stevesmithis said:
I was not able to sideload anything. I could see the device, I could start the process, but it would fail every time. I talked to HTC last night and they are going to replace it.
Weirdly, when I was talking with them, they had me try to clear the cache and it actually worked, so I'm going to try and sideload it one more time tonight and if it doesn't work, just swap it out.
Click to expand...
Click to collapse
Yeah I was able to clear the cache I was even able to format the user data the problem is is there is no OS loaded. At least with the fastboot says under os it says N/A.
HTC said they'll replace it I just have to send it in to them problem is I'm a truck driver so I'm never at home.
-Wes-
Sent from my SM-N910T using Tapatalk
wesmagyar said:
Yeah I was able to clear the cache I was even able to format the user data the problem is is there is no OS loaded. At least with the fastboot says under os it says N/A.
HTC said they'll replace it I just have to send it in to them problem is I'm a truck driver so I'm never at home.
-Wes-
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I had the same problem: even after wiping the cache and formatting the user data, the tablet wouldn't boot, and fastboot said "OS: N/A". However, I went into recovery and sideloaded the OTA file with adb. The update went fine and now my Nexus 9 works again. If you are using Windows and the computer doesn't recognize the tablet you should install the appropriate drivers, I guess (look up "Google USB Driver"). I use a Mac so drivers weren't a problem for me.
xworld21 said:
I had the same problem: even after wiping the cache and formatting the user data, the tablet wouldn't boot, and fastboot said "OS: N/A". However, I went into recovery and sideloaded the OTA file with adb. The update went fine and now my Nexus 9 works again. If you are using Windows and the computer doesn't recognize the tablet you should install the appropriate drivers, I guess (look up "Google USB Driver"). I use a Mac so drivers weren't a problem for me.
Click to expand...
Click to collapse
Will I'll be a mother effer I was able to get it to recognize my device by installing the Samsung ADB driver and from there I was able to sideload the OTA and it is now working.......
The very first thing I'm doing as soon as I actually get it start it is I am going to enable OEM unlock. Everybody who has one of these devices should do that immediately.
Thank you so much man you are awesome
{
"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 SM-N910T using Tapatalk
I tried again and it failed. Sadness. Guess I'll just have to swap it out.
I can't figure out how have my device appear when entering "adb devices" ... when i'm in fastboot, i "fastboot devices" and it shows with the serial number. when i'm in recovery, though, "adb devices" shows nada. When I'm in TWRP after selecting "ADB Sideload", my device appears in my Device Manager under Nexus 9, but I can't update driver info to anything that seems to work.
I've got the most up to date drivers via SDK.
Any ideas how I can get my device to be recognized by my PC so that I can sideload the OS?
Thank you all.
thegeneralfamily said:
I can't figure out how have my device appear when entering "adb devices" ... when i'm in fastboot, i "fastboot devices" and it shows with the serial number. when i'm in recovery, though, "adb devices" shows nada. When I'm in TWRP after selecting "ADB Sideload", my device appears in my Device Manager under Nexus 9, but I can't update driver info to anything that seems to work.
I've got the most up to date drivers via SDK.
Any ideas how I can get my device to be recognized by my PC so that I can sideload the OS?
Thank you all.
Click to expand...
Click to collapse
I was having the same problem I installed the Samsung ADB driver, , and all of a sudden my computer recognized my Nexus 9 in a adb mode
Sent from my SM-N910T using Tapatalk
Mine wouldn't show up until I was in recovery and actually picked the "install from adb" or whatever from the menu.
yeah it doesn't actually go into adb mode until you select the sideload option. just as it doesn't go into fastboot untill you are in fastboot.
I was able to download the OTA from android authority. just made sure that the upgrade matched the one that i was upgrading from, i have a galaxy note so when i couldnt get windows to recognize the nexus 9 in adb mode i selected search my computer for the drivers and selected select from installed drivers and out of sheer desperation selected the Samsung ADB driver and sure enough the worked. from there i was able to adb sideload the update and install it and it rebooted into beatiful android 6.0 tablet has been working fine so far with no issues.
First thing i did however was allow unlocking of the bootloader in the developer options.
Edit: nvm
stevesmithis said:
Edit: nvm
Click to expand...
Click to collapse
Yeah I was going to say because I'm the op, I had no access to the operating system either but I was able to accomplish two steps I laid out above and it fixed my problem.
Sent from my SM-N910T using Tapatalk
Also also misread your post. I thought you were saying that unlocked the bootloader before you fixed it. Lol
I got the Motorola update to android 11 and successfully installed it. When I tried to install magisk after patching my boot.img, I think I've hard bricked the phone.
I'm unable to turn on the screen.. tried just the power button, vol- and power, vol+ and power.. no dice.
anyone know of other things I can try to get in to fastboot and reset the device? or is it a lost cause?
I flashed the patched boot.img from fastboot. when the phone screen was stuck at the motorola logo. I went back to fastboot and flashed the stock boot.img. It boot looped a couple of time and now it won't turn on at all.
Using the rescue tool is of no help because the tool requires the device to boot into fastboot
Help!
Try this. Hopefully you can get to the bootloader. If yes, continue with my suggestion below.
I guess you go up to android 11 via OTA. In this case, you need to download the android 11 firmware matching your phone, then extract the boot.img which you will flash back to your device. Hopefully, you can reboot to your phone as normal.
When patching the boot.img using the latest magisk, remember not to change the patched file name given by magisk. Just keep it as is as provided by magisk. To be safe, you should test a single boot with the patched image before flashing it.
Hope that'll help.
tinbilly said:
Try this. Hopefully you can get to the bootloader. If yes, continue with my suggestion below.
I guess you go up to android 11 via OTA. In this case, you need to download the android 11 firmware matching your phone, then extract the boot.img which you will flash back to your device. Hopefully, you can reboot to your phone as normal.
When patching the boot.img using the latest magisk, remember not to change the patched file name given by magisk. Just keep it as is as provided by magisk. To be safe, you should test a single boot with the patched image before flashing it.
Hope that'll help.
Click to expand...
Click to collapse
Thanks.. I cannot get the phone to power on at all.. so, no bootloader/fastboot. Tried power cycle while plugged in.. didn't change anything. Will keep trying.. Strangely, the rescue software's 3rd option is "power-off mode", but that option also asks me to be in fastboot.
smvsmv said:
Thanks.. I cannot get the phone to power on at all.. so, no bootloader/fastboot. Tried power cycle while plugged in.. didn't change anything. Will keep trying.. Strangely, the rescue software's 3rd option is "power-off mode", but that option also asks me to be in fastboot.
Click to expand...
Click to collapse
is it listed in Device manager like this?
Is my device in EDL Mode?
sd_shadow said:
is it listed in Device manager like this?
Is my device in EDL Mode?
Click to expand...
Click to collapse
No. I tried reinstalling the Qualcomm usb drivers. That didn't help either. Possibly that's why the rescue tool is unable to help with the power off option. Any other ideas? What ever happened, it has to do with the boot.img.
I wish phones had a reset hardware button.
Are you sure the phone is fully charged? Did you try plugging in the power for several hours?
Did your try https://support.lenovo.com/vn/en/downloads/ds101291-rescue-and-smart-assistant-lmsa?
tinbilly said:
Did your try https://support.lenovo.com/vn/en/downloads/ds101291-rescue-and-smart-assistant-lmsa?
Click to expand...
Click to collapse
Yes, that's the rescue tool that I've been referencing. Also, the phone had full charge when I screwed it up. Will try plugging it again.
smvsmv said:
No. I tried reinstalling the Qualcomm usb drivers. That didn't help either. Possibly that's why the rescue tool is unable to help with the power off option. Any other ideas? What ever happened, it has to do with the boot.img.
I wish phones had a reset hardware button.
Click to expand...
Click to collapse
How is it listed in Device Manager?
sd_shadow said:
How is it listed in Device Manager?
Click to expand...
Click to collapse
It's not at all listed.. there are no "other devices" and it's not listed under ports either
{
"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"
}
smvsmv said:
It's not at all listed.. there are no "other devices" and it's not listed under ports either
View attachment 5311913
Click to expand...
Click to collapse
If windows is making the device connected sound will connecting to USB, it's there somewhere.
Otherwise, it's not fixable because there is no device to send commands to.
sd_shadow said:
If windows is making the device connected sound will connecting to USB, it's there somewhere.
Otherwise, it's not fixable because there is no device to send commands to.
Click to expand...
Click to collapse
Yep.. that's what I'm afraid it is. Unless the device decides to boot to something, I'm guessing it's done. Thanks for your help!
Did you try Motorola Moto G 3rd Generation Troubleshooting or Moto G Power: Black Screen or Screen Won't Turn On? 6 Easy Fixes!?
tinbilly said:
Did you try Motorola Moto G 3rd Generation Troubleshooting or Moto G Power: Black Screen or Screen Won't Turn On? 6 Easy Fixes!?
Click to expand...
Click to collapse
yeah.. been googling and this was the first video that I came across. didn't help though.
EDIT - ignore the below. Just remembered that is a snapdragon and not Mediatek.
When I leave the phone connected to my windows 10 laptop, the device shows up occasionally under networks. Double clicking the device pulls up the properties.
Looks like there's still some "life" on my phone. Anyone have ideas on how to get into it?
smvsmv said:
EDIT - ignore the below. Just remembered that is a snapdragon and not Mediatek.
When I leave the phone connected to my windows 10 laptop, the device shows up occasionally under networks. Double clicking the device pulls up the properties.
Looks like there's still some "life" on my phone. Anyone have ideas on how to get into it?
View attachment 5314927
Click to expand...
Click to collapse
do you what Model # you have?
sd_shadow said:
do you what Model # you have?
Click to expand...
Click to collapse
Not sure.. but before upgrade, the rescue tool downloaded the file SOFIA_RETAIL_QPMS30.80_63_6_8_5_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml Not sure if that shows model
smvsmv said:
Not sure.. but before upgrade, the rescue tool downloaded the file SOFIA_RETAIL_QPMS30.80_63_6_8_5_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml Not sure if that shows model
Click to expand...
Click to collapse
open that folder, does it have a
preloader.bin file?
sd_shadow said:
open that folder, does it have a
preloader.bin file?
Click to expand...
Click to collapse
No. these are only 4 bin files
The info file has the below. Couldn't find anything that status with a XT
BUILD REQUEST INFO:
SW Version: sofia_retail-user 10 QPMS30.80-63-6-8-5 a1e5d release-keysM6125_39.36.03.39R
Modem Version: M6125_39.36.03.39R
FSG Version: FSG-6125-03.87
MBM Version: MBM-3.0-sofia_retail-37f1d8316-201231
Build Fingerprint: motorola/sofia_retail/sofia:10/QPMS30.80-63-6-8-5/a1e5d:user/release-keys