so my phone got the bootloop problem, a few days ago and after hours of research i found a thread here with a kernl to solve the problem, so i went ahead with the guide and had to unlock the bootloader, i tried LG's site but it seems the site is faulty and i cant get past the log in screen, so i found another guide using fastboot, but fastboot wont show the device, i tried "adb devices" showed nothing, "fastboot devices" also yielded the same result, even though i hear a sound when i connect the phone in fastboot mode, some other research lead me to believe that there is a conflict in drivers because in the device manager it shows android with a triangle next to it, i tried different drivers, nothing, i tried using Microsoft update online but it found nothing, can anyone provide help? cant go to lg bcause i got the phone used, and done have the money to get a new one, so if i could this one back up and running it would be a dream, thanks for any help in advance!
Related
I've read around on the forums trying many different things, but my problem is still here. ADB finds my phone when I am in normal phone mode, but once I go into fastboot mode it shows an empty list of attached devices. I've tried multiple different drivers and I've yet to have it show up. I tried on three different computers so far to no avail.
My friend got it working on his laptop once and flashed a kenel onto the phone that broke my wifi.. and we can't get ADB to load again to flash back the original. Sigh.
Can someone please help me?
So far I've tried HTC's drivers and the Universal drivers found on the Nexus forums. My Device Manager says Android USB Devices -> HTC, Corporation when my phone is in fastboot mode. the adb command shows List of devices attached and a black line after that. I'd show images if XDA didn't block me.
ICruentusI said:
I've read around on the forums trying many different things, but my problem is still here. ADB finds my phone when I am in normal phone mode, but once I go into fastboot mode it shows an empty list of attached devices. I've tried multiple different drivers and I've yet to have it show up. I tried on three different computers so far to no avail.
My friend got it working on his laptop once and flashed a kenel onto the phone that broke my wifi.. and we can't get ADB to load again to flash back the original. Sigh.
Can someone please help me?
So far I've tried HTC's drivers and the Universal drivers found on the Nexus forums. My Device Manager says Android USB Devices -> HTC, Corporation when my phone is in fastboot mode. the adb command shows List of devices attached and a black line after that. I'd show images if XDA didn't block me.
Click to expand...
Click to collapse
Adb doesnt work in fastboot. Use fastboot flash boot boot.img then flash the kernel modules in recovery.
Sent from my HTC6435LVW using xda app-developers app
Wow
Thank you very much. Complete noob at playing with Android devices .
When you flash a kernel, you have to make sure to also flash the kernel modules in recovery. That's what caused the wifi to stop working. Same thing happened to me haha.
Sent from my (Viped out)³ DROID DNA
Hi!
First off let me say thanks to R_a_z_v_a_n for redirecting me and hope that I'll find my answer here ^^
So I Have this device called HP 7 VoiceTab 1321RA (not with Slate just HP 7 Voicetab), wanting to have a custom recovery then I tried to flash a CWM Custom Recovery for HP Slate 7 VoiceTab because I thought it was the same and ends up bricking my phone. It ends up in a bootloop which only shows HP sign for a few seconds and dead. But I managed to find out that I can access the recovery menu (or so I thought it is), but the options was choosing between Fastboot Mode, Normal Boot, Recovery Mode, and VART Mode.
I tried to enter Fastboot Mode before and tried to access it via PC but somehow I can't find the device by entering adb devices and fastboot devices. Anyways, I have downloaded a stock update.zip for it but not the original KitKat one which I get from the first time I bought it but rather the JB ones. I think by flashing this would help me recover the device but the only problem is I don't know which method should I use to Flash it. Since I don't have the Stock Recovery or ANY kind of recovery at all, I guess I'm stuck. And it won't start to the home page so I can't set the USB debugging options. Please guide me through this >.<
Thanks a lot!
Been fighting with it for 2 days now and still no result came.
So here's the update so far....
I tried on my other device in order to understand how my PC reads ADB and now I kinda gets it. But the problem is now can't get the device to enable USB Debugging because I can't access options at all.
Secondly, since I left it on for the night because charging seems to trigger the bootloop too, now I can't access the fastboot mode like I was last night. And it constantly repeating this sequence: [battery scene with the "charging battery" symbol] > [HP Powered by Android screen] repeated for 2-3 times > [low battery need charging screen] > repeat. And once I tried to connect to the PC, it goes to the same sequence too. When I tried to access the boot options (the screen which displays Fastboot Mode, Normal Boot, Recovery Mode, and UART Mode which I mention in Thread Starting post), it shows the low battery need charging scene and then repeating the same sequence as mentioned above.
I seem to figure out how to fix this but I still can't manage to access the fastboot mode yet. Will give update once I can try to.
Anyone can help me on this?
Thanks a lot!
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
I found my self in a deadlock!
PLEASE HELP :crying:
Could you unbrick yours
What service centre says about that problem i also ran in this problrm but i m trying to go to service centre for that
first off install drivers in your PC as admin
then use the official flashtool to flash ur stock firmware by entering fastboot or flashmode simple as that
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
Dude urs is a mtk device so sp flash tool should do the trick.... Just don't forget to install correct drivers....run both drivers and flash tool as admin..... Tell me when it's solved k
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
That is what im trying. To tell you urs is a mediatek device the official flashtool is sp flashtool
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
try to push the update.zip via adb sideload (Choose "update via ADB sideload" on recovery mode)using adb terminal on PC,as long as your tab can access the recovery mode.remember to backup all your data before u do it.
have a try it's 100% work on me
where I can download update.zip file? anyone can help?
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
can you explain how did you managed to charge the device??? please its a request......jst help me out :crying::crying:
Hello everyone,
So today I tried installing lineageos and after some stupid moves on my part I´m currently stuck at a screen saying Reset failed. with a red exclamation point and the only option is reboot system now( which I cant select). I can´t access fastboot nor twrp, the phone has FRP and Bootloader Unlocked at least the last time I was on the fastboot screen. My model is RNE-L21 europe, do you have any ideas? I have seen somewhere, cant find the post now but the guy waited the phone to reach 0% and then he was able to put it in fastboot. Any help is appreciated.
crassus96 said:
Hello everyone,
So today I tried installing lineageos and after some stupid moves on my part I´m currently stuck at a screen saying Reset failed. with a red exclamation point and the only option is reboot system now( which I cant select). I can´t access fastboot nor twrp, the phone has FRP and Bootloader Unlocked at least the last time I was on the fastboot screen. My model is RNE-L21 europe, do you have any ideas? I have seen somewhere, cant find the post now but the guy waited the phone to reach 0% and then he was able to put it in fastboot. Any help is appreciated.
Click to expand...
Click to collapse
What were the "stupid moves"?
I can´t tell precisely but I tried using HWOTA which ended in an error I thought the error came from the oemfile being damaged, because on the HOWTA the model only appeared RNE-L21 so I installed oemfile tried the HOWTA again with no success reinstalled the TWRP version which I used to do my backup, restored and here I am.
If I connect to pc Hisuite opens and on device manager it appears as: "linux file-cd gadget usb device"
Solved the issue, wait for the battery to die. After that connected to pc booted in fastboot and used HuRupdater.
i managed to delete twrp and when i did then it shows that the system has been destroyed and after restart it is stuck on
fastboot windows. i tried to connect it with my pc so i could install flash rom but it doesnt show up on pc after connecting to usb.
i dont understand what to do next... helppppppppppppppppppppppppp
I have been in this situation before but I'm not sure how exactly i got into it but I was also doing something to do with twrp. Anyway, whenever you encounter such a problem you need to provide as much information as you possibly can to help us help you. This way people are able to narrow down to what causes a particular problem. One question I have is how did you "delete" twrp?
Now for how I got out of that "system has been destroyed" problem. First off, I had already successfully unlocked my bootloader (don't know if you had). Also, the adb drivers were properly installed on my pc. What I did (at the "system has been destroyed" screen) was to let it sit there while connected to the charger for what seemed to be around 10 minutes and kept doing what I was doing and out of the corner of my eye I saw it rebooting and unexpectedly it went into fastboot. I connected it to my pc and it showed up in device manager and "fastboot devices" command detected it. I proceeded to successfully flash recovery with fastboot and then used "fastboot boot recovery.img (or whatever you have renamed your recovery to)" command. It went into recovery mode after which I copied rom via mtp and flashed it and it agreed to boot into system after the flashing was successful.
These may not be the exact steps I took but as close to them as I can recall (because I was bewildered at the thought that my phone was dead). I think the key turning point was to let it sit at the "system has been destroyed" screen for a while.
twistyplain said:
I have been in this situation before but I'm not sure how exactly i got into it but I was also doing something to do with twrp. Anyway, whenever you encounter such a problem you need to provide as much information as you possibly can to help us help you. This way people are able to narrow down to what causes a particular problem. One question I have is how did you "delete" twrp?
Now for how I got out of that "system has been destroyed" problem. First off, I had already successfully unlocked my bootloader (don't know if you had). Also, the adb drivers were properly installed on my pc. What I did (at the "system has been destroyed" screen) was to let it sit there while connected to the charger for what seemed to be around 10 minutes and kept doing what I was doing and out of the corner of my eye I saw it rebooting and unexpectedly it went into fastboot. I connected it to my pc and it showed up in device manager and "fastboot devices" command detected it. I proceeded to successfully flash recovery with fastboot and then used "fastboot boot recovery.img (or whatever you have renamed your recovery to)" command. It went into recovery mode after which I copied rom via mtp and flashed it and it agreed to boot into system after the flashing was successful.
These may not be the exact steps I took but as close to them as I can recall (because I was bewildered at the thought that my phone was dead). I think the key turning point was to let it sit at the "system has been destroyed" screen for a while.
Click to expand...
Click to collapse
Hey thanks for replying to be honest ..i thought people will help but seems like nobody cares here..
The thing is i dont remember actually exact process but i somehow managed to delete the twrp ..
the main problem is you said after ur phone got onto fastboot you connected it to ur pc and flashed official rom but in my case in the device manger or anywhere ... when my phone is in fastboot mode and i connect it to my pc it doesnt show up as connected not in device manager or any other place...this is the main problem....if only my device shows up connected i wouldve flashed rom way before anything...its been 1 week since my phone died ...i need help...i tried everything from youtube ...seems it doesnt work for me
AjTheKiller1 said:
Hey thanks for replying to be honest ..i thought people will help but seems like nobody cares here..
The thing is i dont remember actually exact process but i somehow managed to delete the twrp ..
the main problem is you said after ur phone got onto fastboot you connected it to ur pc and flashed official rom but in my case in the device manger or anywhere ... when my phone is in fastboot mode and i connect it to my pc it doesnt show up as connected not in device manager or any other place...this is the main problem....if only my device shows up connected i wouldve flashed rom way before anything...its been 1 week since my phone died ...i need help...i tried everything from youtube ...seems it doesnt work for me
Click to expand...
Click to collapse
Have you ever had your phone detected by your pc in fastboot mode? And if you connect it to the pc, does the computer play the hardware detected sound?
You need to rule out a driver issue. I'm not the only other person to get the "system has been destroyed" message and people usually get out of it. I don't know why yours is so problematic.
Had you successfully unlocked bootloader?
The Good old "System has been destroyed" Message. Well, This is terrible This should not happen in the first place. I assume it happened Because you wiped data and then deleted twrp. But If you want help you have to specify how exactly did you " Delete TWRP" What steps did you follow to Delete it. None the less the best bet on getting your device back would be to go to the nearest service center. Pretend you did nothing and maybe they will say you got a bad update.
Hey, sorry if i bother or im posting where im not supposed to.
I have an amazfit stratos that has worked perfectly for years, but suddenly it got brick two weeks ago, I've trying to fix it lately, but I have no clue on what shpul I do.
I have installed the Adb libraries, Minimal Adb and fastboot and followed tutorial of some threads but I always get the same error, when I put the watch in fastboot mode it is recognized by the computer on the device manager, but whenever I try to execute the adb commands, it says that theres no device attached, I dont think I have a problem with adb libraries because it can recognize my other devices.
I've installed the "TOOL ALL IN ONE" and Huami AMAZFIT Tool of mauronofrio to try to install a ROM or at least get an idea of what could be happening, both of the Apps say that the device is in fastboot mode, but none of them can recognize the device, also when i click on check bootloader status it says its locked and whenever I try to unlock it the watch would restart getting stuck into the logo so the app throws an error.
I dont know if my problem is that the bootloader is locked or if Im doing something wrong.
Id take whatever advice, thanks