Database Users

Bootloop after 4.3 OTA, USB and thus Fastboot not working!

I got a serious problem with the N4 of a friend.
First thing to know: his display was broken and he got it repaired. Afterwards, his phone was running fine. Then, he got the Android 4.3 OTA. He accepted the update, but since then in keeps bootlooping (I won't go past the Nexus-X). As far as I know, everything was stock!
Here are the things I tried:
- first I checked the recovery. Indeed it was the stock one, so nothing to do here.
- I wanted to wipe or flash the stock rom using fastboot but i wasn't able to get a connection. First I thought of driver issues, but my N4 works fine (adb & fastboot) on the same computer.
- Establishing a connection failed on two other computers too (my N4 worked)
- Even the device manager in Windows 7 dosen't even recognize anything when plugging in the usb cable (normally you see the ADB whatever device listed in the device manager)
- Right now I tried to get a connection using Ubuntu. Again, no usb device was recognized when plugging in the cable.
So right now, I'm a bit lost. It seems, that the usb port is broken since I can not establish a connection. And without that, I won't be able to wipe or flash anything using fastboot.
Does anyone have an idea what could have gone wrong? I'm still able to boot into the bootloader and see the information:
Bootloader version: MakoZ20i
Radio: .84
HW Version 11
16GB version
According to these information, it seems that the 4.3 Update finished at least the bootloader and radio. But it won't boot into the rom. Could the download mode be of any help?
I appreciate any help.
Thanks.

Since you are in the bootloader scroll up to recovery and select it.
Now you will see a android opened up with "No command." written below the android.
Press volume up and power until it unlocks the recovery and try to wipe the data and cache partition followed by dalvik cache.
Sent from my Nexus 4 using Tapatalk 4

Thanks for your idea, but it turned out to be hardware problem!
I took the device to the lab and had a look at the usb connector. The contact in the middle was teared of the carrier and was stuck to the back and thus no data connection could be established! I was able to to bend it back (more ore less) to its initial position and now its working. Though I'm wondering how long it will last until its pushed back again.
Fact is, that i was able to connect via fastboot. I tried to flash 4.3 again but it still didn't boot. Its back to 4.2.2 and its working now.
Again - thanks for your idea.
Thread can be closed!

[Q][SOLVED] A500 bricked, stuck in bootloader. Won't boot kernel or recovery.

I am sorry to start a new thread but I have been reading threads and trying things now for over 7 hours straight. I have bricked my mothers A500.
I installed Skrillex V8 bootloader to my own tablet with Thor 1.7.3 recovery and a CM10.2 rom, everything worked fine. My mother liked how my tablet had way more battery and seemed faster then her own so she asked me to do it to hers.
I did everything the same except I had deleted the files and had to find a different bootloader so I found the "lightspeed" version of Skrilex V8 and as it seemed to just be a re-skin figured it was fine.
I downgraded to the unstable 3.0.2 build then installed iconia root and a Thor recovery via acer recovery. I then installed the lightspeed bootloader via thor with intentions of then installing the newer thor and rom after.
This is where im stuffed, after installing the new bootloader it is screwed. I cannot enter recovery or boot the primary kernal. I attempt to enter fastboot and although the tablet goes into fastboot it outputs errors and has random lockups and freezing on the tablet which the computer identifies as it being disconnected.
I have tried searching the forums for an answer and have tried everything I can understand but I am truely boned. As I am writing this I am installing packages to my Ubuntu laptop so that I can obtain the UID through the terminal in hopes it will work with APX and blackthunders tools.
If I cannot get it working I will simply wipe and give my mother my tablet, But I would really like to try and get this son of a ***** working again. I am currently incredibly annoyed at it and am probably missing something obvious. Please help me.
[UPDATE 1]
I have managed to obtain my CPUID and thus my SBK through the method described here -> http://forum.xda-developers.com/showthread.php?t=1751978
I am still unable to use any tools as my PC will not recognize it in APX mode, I have reinstalled the drivers, restarted, tried multiple USB ports, uninstalled the failed unrecognized device and started from scratch a few times and I just cant seem to get it to detect them. Also tried other USB cables incase it was iffy, checked contacts on ports. There also cannot be any env variable or reg conflicts as I used my diagnostic machine to check it and it booted into its clean OS.
the APX seems to work with my linux unit though, but the blackthunder tools are for windows...
[UPDATE 2]
Using the tutorial here ->http://forum.xda-developers.com/showthread.php?t=2444187
I made it boot into the APX mode with the yellow acer logo and the APX mode text at the top, however I left it for a while and it didnt seem to finish flashing, using lsusb I can see its still connected to the linux box but it is clearly not flashing properly.
I am going to leave it for a bit then try unplugging from linux and plugging into windows while in the yellow acer logo screen with verbose output and see if blackthunders tool detects it.
[UPDATE 3]
DO NOT try what i did in update 2, I believe i removed it when it was formatting the partition, it wont even boot to the bootloader now. black screen with white light on power button and cannot be detected as APX.
[UPDATE 4]
I treid a few more times at getting it into APX mode and it turns out its just being dicky and freezing randomly, however, by trying a few times (this is dangerous but i had nothing to lose at this point) to run the Nvflash script on my linux box eventually it run through and installed the v9 bootloader. This bootloader allowed me to go into Fastboot without the freezing or crashing or loss of communications i was experiencing before. I then using fastboot flashed a recovery appropriate to the v9 bootloader and am now using that to flash a 4.3 rom. This should completely fix all the problems.
I am now sure (as previously I could only guess that the problem was caused by a dicky install of the lightspeed bootloader (a custom variant of skrilex v8 designed to match the theme of the lightspeed rom).
[UPDATE 5]
Working
Adding solved to title as I know the feeling when you come across an old thread that talks about your problem and has no replies or help.
-V0L4T1LE
Been using XDA for years never bothered to post as have never had to spend more then a few hours to solve a problem, this one took me a long time though so I decided to ask for help. Nevermind, didnt need it.

Awsum and well done getting yrself sorted, thanx for posting
rgds dibb
Sent from my GT-I9300 using Tapatalk 4

Can you extract the partition 4 using nvflash --rawdeviceread to a file and share to me? My A500 is bricked and cannot download to it. only --rawdevicewrite works.
Thanks!

stuck in apx, no ADB or Fastboot

hi,
before updating to 4.3 via OTA i was rooted via chinese method and had problems with my wifi, i decided to wipe my note using fastboot -w, to see if it would fix the wifi issue, afterwards it booted up and i installed the 4.3 OTA, i think it installed but my device went into a bootloop and i can not get ADB or Fastboot to recognise it (I know the drivers work, they recognise my LG G2), the only device showing up in device manager is APX. I did some googling and found that its Nvidia low level recovery system. Is there any way to get my TN7 out of APX or do I wait until Nvidia release the relevant blobs? (Am I right in saying that Nvflash doesnt support Tegra 4 yet?) Can you guys think of any solutions? I am happy to try experimental, pre-alpha stuff!
Thanks in advance,
Aliaksei

aliaksei said:
hi,
before updating to 4.3 via OTA i was rooted via chinese method and had problems with my wifi, i decided to wipe my note using fastboot -w, to see if it would fix the wifi issue, afterwards it booted up and i installed the 4.3 OTA, i think it installed but my device went into a bootloop and i can not get ADB or Fastboot to recognise it (I know the drivers work, they recognise my LG G2), the only device showing up in device manager is APX. I did some googling and found that its Nvidia low level recovery system. Is there any way to get my TN7 out of APX or do I wait until Nvidia release the relevant blobs? (Am I right in saying that Nvflash doesnt support Tegra 4 yet?) Can you guys think of any solutions? I am happy to try experimental, pre-alpha stuff!
Thanks in advance,
Aliaksei
Click to expand...
Click to collapse
Sorry to say that no one has yet got NvFlash working with Tegra 4 SoC, bar in-house developers and wholesalers.
If you can't get the device into fastboot then your only alternative is to return the tablet on warranty since you are not getting a proper bootloader which is a sign of an early released unlocked tablet where legally there was no hindrance to tinkering. To get fastboot try;
Starting up the device with the POWER-BUTTON + TOP VOLUME-BUTTON held down at same time. The device will boot and as soon as you see the logo, then release only the POWER-BUTTON so that the device doesn't do a unwanted restart on you. What you should be trying to archive with this is get to a menu based bootloader if you have one. There, you should be able to toogle on fastboot and recover the device.
I hope that helps.

If I return it on warranty, will they be able to see that it was rooted, invalidating my warranty?
Sent from my LG-D802 using xda app-developers app

[i9505] Odin not working Windows 10 x64

So I am trying to install a custom recovery for my i9505, but Odin does not recognize the phone which was put in download mode before. Please help me! Here are some details:
I got proper USB Drivers installed (1.5.55.0), tried even with Kies/smart switch installed
Using Odin 3.09-3.10.7
Different usb-cables
Completly UNROOTED i9505 with STOCK recovery and 80% charge
In device manager the phone does not appear properly. It has two listings:
1. Other Devices\ MSM8960
2. USB-Controller \ Unknown USB Device (Error trying to get device description //translated from German
Windows 10 Home 64bit
Personally I think it should be a problem with Windows 10 but I am not sure...
To the phone itself because it could be hardware-wise broken:
The phone itself is a completly meltdown. Before I tried repairing it the speaker were broken (no sound). The phone ran an official lollipop rom. I think 5.0.1. Then I thought I could just hit a software update to fix maybe some problems. I updated to I9505XXUHOJ2 [5.0.1] DBT
And now the software experience is completly broken. The phone gets a lot of soft-reboots, the booting takes like 5 minutes and yes the phone is factory reseted. BUT HEY THE SPEAKER WORK AGAIN?!
I really dont know what is happening but there can be only 2 solutions:
1. Re-Install stock software via odin and then switch to cm and hope it works
2. or throw this piece of sh*t away because the cr*ppy hardware is brokanus sarus rekt
or is there any other solution? Tell me
Otherwise I would also ask if there is any solution to install cm12.1 or a custom recovery without root and odin access. (thinking of sideloading in recovery or something like this)
Thanks for reading and replying. I am gratefull for everything I hope the best ^.^

Try running Odin in compatibility mode, set for Windows 7.

fabsau said:
So I am trying to install a custom recovery for my i9505, but Odin does not recognize the phone which was put in download mode before. Please help me! Here are some details:
I got proper USB Drivers installed (1.5.55.0), tried even with Kies/smart switch installed
Using Odin 3.09-3.10.7
Different usb-cables
Completly UNROOTED i9505 with STOCK recovery and 80% charge
In device manager the phone does not appear properly. It has two listings:
1. Other Devices\ MSM8960
2. USB-Controller \ Unknown USB Device (Error trying to get device description //translated from German
Windows 10 Home 64bit
Personally I think it should be a problem with Windows 10 but I am not sure...
To the phone itself because it could be hardware-wise broken:
The phone itself is a completly meltdown. Before I tried repairing it the speaker were broken (no sound). The phone ran an official lollipop rom. I think 5.0.1. Then I thought I could just hit a software update to fix maybe some problems. I updated to I9505XXUHOJ2 [5.0.1] DBT
And now the software experience is completly broken. The phone gets a lot of soft-reboots, the booting takes like 5 minutes and yes the phone is factory reseted. BUT HEY THE SPEAKER WORK AGAIN?!
I really dont know what is happening but there can be only 2 solutions:
1. Re-Install stock software via odin and then switch to cm and hope it works
2. or throw this piece of sh*t away because the cr*ppy hardware is brokanus sarus rekt
or is there any other solution? Tell me
Otherwise I would also ask if there is any solution to install cm12.1 or a custom recovery without root and odin access. (thinking of sideloading in recovery or something like this)
Thanks for reading and replying. I am gratefull for everything I hope the best ^.^
Click to expand...
Click to collapse
Windows 10 x64 works fine. I used it myself.
Try all the different usb ports and reinstall the drivers. Use the drivers from here:
http://developer.samsung.com/technical-doc/view.do?v=T000000117

Hi,
As the addition, make sure Kies isn't running when Odin is executed as it could cause the device being not detected properly in Odin.
PS Note: I used Windows 10 Home x64 too and working fine as it should.
Sent from my GT-I9500

LG G2 D802 United Kingdom Open - unbrick?

Hey everyone,
I'm very new to Android development and XDA, but a few years ago I bricked this LG G2 and I don't really remember how, except that I rooted it and tried to install a custom ROM, which obviously didn't work.
I have tried a number of different guides on these forums, but somewhere or another I get stuck on them.
[HOW TO] Fix your soft-bricked LG G2 (All Variants)
I'll be very specific, something most people lack of. Okay lets get to it, I recently bricked my LG G2 (D801) by installing a ROM that wasn't compatible with my model. I fixed it by doing the following steps. This worked for me using Windows 8.1...
forum.xda-developers.com
With this one, although the device shows up in Devices and Printers, neither Fastboot nor the LG Flash Tool detect it. I have installed both the LG Mobile Driver and the LG United Mobile Driver.
“./fastboot devices” is empty.
I have the TOT file and the DLL that the (patched version of the) LG Flash Tool requires.
I have an Ubuntu 20.04 install as well as Windows 11. I can get into Firmware Update with a USB icon ("Do not unplug the USB connection until the process is complete. 0%." ...etc), when I turn it on normally it shows a battery made out of grey and white bars and a percentage, and sometimes the LG logo.
If you need to know anything else don't hesitate to ask \
Much appreciated,
ninjadev64

use a usb 2.0 port, update adb/fastboot, update drivers, remove previous related devices using nirsoft usbdeview. try using a windows 7 or earlier system. can you manually get into recovery? if so update to latest blastagator twrp which should be 3.3.1.

DvineLord said:
use a usb 2.0 port, update adb/fastboot, update drivers, remove previous related devices using nirsoft usbdeview. try using a windows 7 or earlier system. can you manually get into recovery? if so update to latest blastagator twrp which should be 3.3.1.
Click to expand...
Click to collapse
- I was using a 3.0 port, although it still showed up in Control Panel - I’ll try with a 2.0 port today
- I installed “Minimal ADB and Fastboot” and the drivers yesterday, so they should be up to date
- I’ll use usbdeview too
- I can’t use an older system unfortunately
- How do I get into recovery?

Recovery: With the device powered off and usb unplugged, hold Volume Down + Power. When the LG logo appears, release both buttons and hold Volume Up + Volume Down.

Ok, so I got into a factory reset screen that way, I said yes to factory reset, is that the right thing to do? (@DvineLord)

ADB recognises the device, but it's unauthorised. And I obviously can't boot it up to authorise it.
Factory reset just got me back to the LG screen for a long time, so I powered it off again.

Also, when I try to change the COM port to 41, when I click Advanced in Port Settings, it just stops me with "You must have write privileges in the registry for this device in order to modify the device's advanced settings".
I can't find the right path for the device in regedit to follow these steps: https://forums.techguy.org/threads/need-write-permission-for-com1-port.577543/#post-4756991

Were you able to get into Recovery? or did you get into Bootloader/Fastboot/Download?
Bootloader/Fastboot/Download: With the device powered off, hold Volume Up and connect the USB cable.
You want to be in Recovery like I posted above. Do you have TWRP on your device?

DvineLord said:
Were you able to get into Recovery? or did you get into Bootloader/Fastboot/Download?
Bootloader/Fastboot/Download: With the device powered off, hold Volume Up and connect the USB cable.
You want to be in Recovery like I posted above. Do you have TWRP on your device?
Click to expand...
Click to collapse
The recovery method you said to try got me into a factory reset screen, as I stated. All the other recovery methods I saw online didn’t work, so maybe I have no recovery?
I said in the original post that I can obtain download mode. I recognise “TWRP” but I’m pretty sure I botched it up while installing it, because I didn’t know how any of this worked, 4 years ago.
Thank you!

Unfortunate you can't get ADB/Fastboot working.

DvineLord said:
Unfortunate you can't get ADB/Fastboot working.
Click to expand...
Click to collapse
Soo... what can I do?

Try to recall as closely as possible the exact steps you used to modify your device. autorec, ioroot, stump root, avicohh, stock build you were on, custom rom you tried to flash, custom recovery, bootstacks, custom kernel, etc.
Odds are you'll have to try again to flash back to stock, something which I haven't done yet.

Unfortunately all I know is that I tried to install a custom ROM, scuffed up when I was installing twrp, the ROM didn't work and now I have no recovery to fix it. Flash back to stock *is* what I'm trying to do (that's your third question/point which I've already explained in the original post).
If anyone with the same problem visits this in the future, please save this post and share your solution if you find one, cause I'm still stuck!

hope you get it flashed back to stock. make sure to do the first 5 things i listed in my initial post to see if that helps you flash back to stock. the data cable can also make a difference sometimes too.