Did I just hard brick my LG4 TMobile h811? - G4 Q&A, Help & Troubleshooting

Hello!
I think I did something exceptionally stupid. I already had a rooted phone, and was attempting to update the modem via the flashable to H811 20i files on TWRP; but had the bootloader also downloaded and accidentally flashed that in haste. Now the screen is black/nothing turns on/leds etc, and windows reads it as "QHSUSB__BULK" when connected. I do have the *kdz file if there is a way that can be managed to flash it (as LGUP will not recognize it).
Read around googling, but it seems a bit more on the LG 2/3 side of things in unbricking. Would anyone know a way to unbrick it, or am I proper screwed? (Am still reading what I find over, but am making sure I don't mess things up even more by making in post in case there is a way)
Thank you very much for any help!

[email protected] said:
Hello!
I think I did something exceptionally stupid. I already had a rooted phone, and was attempting to update the modem via the flashable to H811 20i files on TWRP; but had the bootloader also downloaded and accidentally flashed that in haste. Now the screen is black/nothing turns on/leds etc, and windows reads it as "QHSUSB__BULK" when connected. I do have the *kdz file if there is a way that can be managed to flash it (as LGUP will not recognize it).
Read around googling, but it seems a bit more on the LG 2/3 side of things in unbricking. Would anyone know a way to unbrick it, or am I proper screwed? (Am still reading what I find over, but am making sure I don't mess things up even more by making in post in case there is a way)
Thank you very much for any help!
Click to expand...
Click to collapse
It is hard bricked but fixable search the threads here and you should be able to find the fix

TheMadScientist said:
It is hard bricked but fixable search the threads here and you should be able to find the fix
Click to expand...
Click to collapse
Yup! Thanks! Just found the thread that I was going to attempt! (LG G4 H811 Complete Unbrick Guide - 100% Working) but before I could, it now lists the device from "QHSUSB__BULK" to "Unknown Device" (On both laptop and desktop), another new problem. Gonna try reinstalling the drivers and cleaning the contacts.
*edit*
Reinstalling the drivers at least went from "QHSUSB__BULK" to "Qualcomm HS-USB QDLoader 9008 (COM3)", so that's a good direction. Just waiting for the SD card to finish low-level formatting.
*edit #2*
Huzzah!! It worked!

Alrightly @madscientist! Not sure if I should make a new thread or not, but properly unbricked it now (which is darned great) now have a new strange issue w/ flashing custom roms.
>Have restored it to H81120o_00_0613
>For some odd reason, the bootloader was already unlocked after unbricking
>Did the normal process of flashing/booting into TWRP that worked fine (USB Debugging/OEM Unlock, then used ADB to fastboot to recovery)
>Flashing UPDATE-SuperSU-v2.48.zip is successful, but makes it bootloop on the T-Mobile logo.
>ANY custom roms I attempt to copy over to the internal memory gives me this error: "Cannot copy item: The device either stopped responding or has been disconnected" but copying over files like Gapps or Magisk work fine (anything but roms basically). If I copy custom roms to either a microsd or internal memory outside recovery, makes both not readable within TWRP, but if I delete them all files internal/in microsd can be read again.
Not sure what to do, because do not wanna brick it again by accident (so am being a bit extra cautious). Any help would be greatly appreciated!

Whi[email protected] said:
Alrightly @madscientist! Not sure if I should make a new thread or not, but properly unbricked it now (which is darned great) now have a new strange issue w/ flashing custom roms.
>Have restored it to H81120o_00_0613
>For some odd reason, the bootloader was already unlocked after unbricking
>Did the normal process of flashing/booting into TWRP that worked fine (USB Debugging/OEM Unlock, then used ADB to fastboot to recovery)
>Flashing UPDATE-SuperSU-v2.48.zip is successful, but makes it bootloop on the T-Mobile logo.
>ANY custom roms I attempt to copy over to the internal memory gives me this error: "Cannot copy item: The device either stopped responding or has been disconnected" but copying over files like Gapps or Magisk work fine (anything but roms basically). If I copy custom roms to either a microsd or internal memory outside recovery, makes both not readable within TWRP, but if I delete them all files internal/in microsd can be read again.
Not sure what to do, because do not wanna brick it again by accident (so am being a bit extra cautious). Any help would be greatly appreciated!
Click to expand...
Click to collapse
make sure the sd card is formatted fat 32

TheMadScientist said:
make sure the sd card is formatted fat 32
Click to expand...
Click to collapse
Yup! It is. I had to make sure it was FAT32 or else the unbrick wouldn't have worked.
Also, it let me flash "LG-G4-H811-20V-Stock-Debloated-Rooted" completely fine, but again, anything custom not at all.

[email protected] said:
Yup! It is. I had to make sure it was FAT32 or else the unbrick wouldn't have worked.
Also, it let me flash "LG-G4-H811-20V-Stock-Debloated-Rooted" completely fine, but again, anything custom not at all.
Click to expand...
Click to collapse
I had the sprint varient so I dont know there. Maybe flashing with wrong kernel or modem

Related

Please help - seemingly bricked M9 after attempting to restore to stock

Hi all,
I'm in desperate need of help here, I purchased an already modified HTC One M9 (which i wasn't aware of when purchased) and have attempted to flash it back to Stock.
well i've made a real mess of it and I really don't understand what to do now if someone could help it would be greatly appreciated. as the phone currently stands:
I've somehow removed the TWRP and it boots into standard recovery
Its been wiped as a pre-req of a guide i followed to install the stock image so it wont boot at all
I can't get my PC to see it when i boot into Download mode, so ADB and fastboot do not see it.
I'm tearing my hair out and really wondering where i can go from here.
Any help is greatly appreciated.
Many thanks.
Several things that would be helpful to know, if you can:
About your phone
- your phone's carrier variant (AT&T, T-Mobile, developer, et cetera)
- what you can boot into (recovery, bootloader, download)
- are you S-ON or S-OFF (boot into bootloader, see upper left hand corner)
About your computer
- what drivers have you installed on your PC
- whether or not HTC Sync is installed on your PC
Depending on what you can boot into, an RUU is your safest option - you'll need to download the RUU that corresponds to your phone's carrier variant. Barring that, if you can boot into download mode, you should be able to install TWRP - which may open up some other options.
The carrier is a UK model unlocked factory so i'd imagine just the standard EU model.
I can get into Recovery which is the standard Android one, Bootloader and Download mode
S-ON which is what confuses me, alot of these posts are regarding S-OFF devices
UPDATE: I managed to figure out i was running 2.10.401.1 so i downloaded the corresponding file for it. Formatted an SD Card to FAT32 and put the file on named 0PJAIMG.zip
It looked like it was working but failed on System.img, the device rebooted and now its stuck on white HTC screen with the Green HTC logo.
I can't turn it off, its just stuck there, any ideas?
andyobmonkey said:
I can't turn it off, its just stuck there, any ideas?
Click to expand...
Click to collapse
I'm sorry for the late reply. I hope you've had better luck in the meantime. If not, you can force a reboot by pushing and holding the power button & volume up.
If you can reboot, see what you can boot into. From what little research I've attempted on your carrier's software offerings, I'm not seeing an executable RUU (ie, installable from Windows). If there is one, that is by far the most dependable way to restore your phone to stock condition.
If you're intent on using the SD card install method (or it is the only way), you might consider ensuring that it is a reliable card. A read failure in the middle of a firmware update might explain the install issues you're having.
Beyond that, I'm afraid I don't have any further advice; I've reached the end of my experience! But if you still need help, please post an update and let us know what is going on.
Get a fresh SD card and pop TWRP or CWM on it along with the stock image. Automatic recovery and 3 wipe there we go. I only got boot loops when I was using a corrupted SD. Also, try both the ones with the underscores replacing spaces and regular names. One of them seem to be a decoy, as far as I can see.
andyobmonkey said:
UPDATE: I managed to figure out i was running 2.10.401.1 so i downloaded the corresponding file for it. Formatted an SD Card to FAT32 and put the file on named 0PJAIMG.zip
Click to expand...
Click to collapse
That file is corrupted and shouldn't be used. You can try reviving your phone by using this RUU service since there is no working 2.10.401.1 RUU you could use.

Can't find anything like it anywhere else (bootloop)

So I made a post in the general help thread and nobody has replied (although I've only waited a few days so I could probably wait a bit longer) but still I feel like my phone's issues are "unique" compared to other bootloops, I can't find anyone else having the same symptoms on their phone. I'll repost what I said in the general help thread and then give a brief overview of everything because I simply cannot comprehend why I'm unable to get out of bootloop with this damn phone.
So I just recently picked up an old Zenfone 2 (ZE500CL) off of my father who didn't really need it anymore and it was an upgrade from my old ****ty phone, so of course I wanted to root it and after using it for a few hours I wanted to install a custom rom by unlocking the bootloader. Well, I tried that, and something must have gone wrong because I got a bootloop and was only really able to boot into recovery mode.
Now, I didn't backup because I'm dumb for one and two I generally have a good idea of where to start if something does go wrong. The thing is, the methods I've looked up and tried have all failed. First, reflashing the stock rom of my ZE500CL (I've tried four different firmwares from the official website, and I know it's ZE500CL because that's what recovery mode is telling me) does not work. Adb hits 47% in the command prompt, the phone stays at 25% until then, and it goes:
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
Not sure why it doesn't work, I looked it up and tried various things and it just isn't resolving itself.
So I tried simply running commands like the following:
fastboot flash recovery recovery.img
Using files from the stock firmwares themselves, and that gives me a flash_cmds error. I've tried deleting all of the userdata, the system, the cache, and a factory reset through recovery mode but none of that works. I'd really appreciate any help anyone could offer, this is a pickle and I'd really like to get this phone back up so that I can just run it as a rooted phone.
Click to expand...
Click to collapse
Now, I'll go over the issues quickly:
I'm stuck in bootloop but I can get into recovery mode
Trying to flash any rom, including multiple stock roms from the asus website, results in an installation aborted message at 47% in either ADB or microSD attempt at flashing the rom.
Attempting to run commands like fastboot flash recovery recovery.img ends up giving me a flash_cmds error which I cannot find anywhere else for the Zenfone 2e
Deleting the cache, userdata, system, or factory resetting the phone does not remove the bootloop
Unlocking and relocking the bootloader does nothing
I would really appreciate any help, feels like my phone is a lost cause even when it's not hard bricked.
Try ASUS Flashtool with a .RAW Firmware...
Find on This Thread...
ponnuvelpandian said:
Try ASUS Flashtool with a .RAW Firmware...
Find on This Thread...
Click to expand...
Click to collapse
Thanks, I haven't seen this. I've got the Intel and xFSTK drivers all up and running but my phone isn't being recognized constantly by my computer under Intel Soc in my Driver Manager, and it's not being recognized as MOOREFIELD but rather as CLOVERVIEW PLUS, and only for a second in-between boots on my phone. Can't get the files to be downloaded through xFSTK, so I've hit a snag here unless someone knows the solution to this.
I'll try just running the flash tool and using a raw firmware, then, since I can't do any of the other stuff.
EDIT: Looks like the issue I was having before is stopping me from running the tool, seems that the computer needs to recognize my phone through the Intel drivers at all time (which it doesn't) in order to run the tool. Also I can't get the tool to view the raw file, it only seems to read zip files (so I put the raw into an empty zip, thinking that could maybe work but I don't know for sure). Damnit, I don't know why this is so difficult.
EDIT 2: All right! Looks like I got it working. The process was relatively simple, actually. It involved booting into TWRP but I wasn't able to most of the time for some reason, it would just never do it. But, I was able to using the CWM Zenfone 2 bat file located here: http://forum.xda-developers.com/zenfone2/help/ze500cl-rooting-related-stuff-t3163528/
Then, I needed the stock rom for my ZE550CL placed onto an external sd card which can be found here: http://forum.xda-developers.com/zenfone2/help/ze550cl-factory-reset-return-to-stock-t3141513
So I would download the CWM Zenfone 2, replace the recovery file as the post states, then run the file. After that, I would run T4 since T1 and T2 didn't work (never tried T3), only T4 would seem to boot me into TWRP. From there, I went to Install, left Zip Verification unchecked, and let the damn thing run. It was the only thing that would run for me, even when doing it with ADB it wouldn't work with the stock rom. Then, I just rebooted and now I'm back on my phone. Hopefully this helps anyone else having this troubling issue, it was terrible!

5x Hard Bricked??

I think I've done goofed my nexus.
Yesterday, I made a backup of my phone, and then booted it up. Everything was working fine prior to the backup, but as soon as I booted it after making the backup, it got stuck on the google logo. I tried restarting it several times, but it's just been stuck in a bootloop ever since. I've tried numerous things, like formatting it, flashing factory images, and so on, but it turns out fastboot won't detect my device. ADB detects my device fine, but only in recovery. As far as I know, I don't have usb debugging enabled (since I formatted it). It currently has no OS since I formatted it. I've tried installing stock android since formatting it but it still gets stuck in a bootloop.
All my drivers are correct (I've re-installed them probably 10 times by now), and the images aren't corrupted (as far as I know).
I've run out of ideas, as I've been trying to figure this out for the past 2 days with no success. Any help would be appreciated.
I've had a similar issue a couple times after doing something stupid (ADB or FASTBOOT could not detect the phone). The fix was to look in Windows Device Manager and make sure the phone really was detected and a driver installed. Windows would say that it could not find a driver but telling it to install manually did the trick..... as I recall there were a couple driver choices, so it might be trieal and error. Might not be the issue in your case since it does sound like the hardware has a problem, but worth looking into?
Paul
pgoelz said:
I've had a similar issue a couple times after doing something stupid (ADB or FASTBOOT could not detect the phone). The fix was to look in Windows Device Manager and make sure the phone really was detected and a driver installed. Windows would say that it could not find a driver but telling it to install manually did the trick..... as I recall there were a couple driver choices, so it might be trieal and error. Might not be the issue in your case since it does sound like the hardware has a problem, but worth looking into?
Paul
Click to expand...
Click to collapse
I've re-installed the drivers a couple of times now, and it doesn't seem to be fixing the problem.
I don't think it's a hardware problem, because I don't see what making a backup would do to the hardware of the phone (of course, I don't really know much about the hardware, so I might be wrong.) Thanks for the help, though!
ItsMason said:
I've re-installed the drivers a couple of times now, and it doesn't seem to be fixing the problem.
I don't think it's a hardware problem, because I don't see what making a backup would do to the hardware of the phone (of course, I don't really know much about the hardware, so I might be wrong.) Thanks for the help, though!
Click to expand...
Click to collapse
Hi, since you're communicating with the device via ADB and can boot to recovery, I'm pretty sure you can still do something about it. I've had this issue and I can recommend starting to read up on Ubuntu or some type of Linux with a decent user interface. It's easier for starters.
You see, if you don't detect the device via the 'fastboot devices' command, then you have one of two big problems:
a) drivers are messed up - it implies you uninstall everything from Device Manager related to ADB / Bootloader interface. After that, shut off the phone, connect your type-c usb cable, boot up the phone into bootloader and let it install the drivers again (I didn't have much success with this but I read others have. Worth a try)
b) something messed up deeper, as in device permissions. When I had the issue, I used Mint (a Debian distribution) and installed all the drivers via the command line there. After that, when I ran fastboot devices, I got something. It was my lost N5x showing with 'no permissions' and no serial ID. I ran 'sudo fastboot devices' and lo' and behold, I saw the device. After that, I just used sudo fastboot flash recovery/system/etc with it and that was it.
exige34 said:
Hi, since you're communicating with the device via ADB and can boot to recovery, I'm pretty sure you can still do something about it. I've had this issue and I can recommend starting to read up on Ubuntu or some type of Linux with a decent user interface. It's easier for starters.
You see, if you don't detect the device via the 'fastboot devices' command, then you have one of two big problems:
a) drivers are messed up - it implies you uninstall everything from Device Manager related to ADB / Bootloader interface. After that, shut off the phone, connect your type-c usb cable, boot up the phone into bootloader and let it install the drivers again (I didn't have much success with this but I read others have. Worth a try)
b) something messed up deeper, as in device permissions. When I had the issue, I used Mint (a Debian distribution) and installed all the drivers via the command line there. After that, when I ran fastboot devices, I got something. It was my lost N5x showing with 'no permissions' and no serial ID. I ran 'sudo fastboot devices' and lo' and behold, I saw the device. After that, I just used sudo fastboot flash recovery/system/etc with it and that was it.
Click to expand...
Click to collapse
I made some progress: my device is now detected in fastboot. I have literally absolutely no clue what happened. I guess it was a bit of randomness or luck or something (maybe wacky and goofy). I've done some flashing - I've flashed system, boot, recovery, cache, data, and radio, but it's still stuck in a bootloop. I don't know what's going on it with it now, but it seems like I haven't made any progress with fastboot.
ItsMason said:
I think I've done goofed my nexus.
Yesterday, I made a backup of my phone, and then booted it up. Everything was working fine prior to the backup, but as soon as I booted it after making the backup, it got stuck on the google logo. I tried restarting it several times, but it's just been stuck in a bootloop ever since. I've tried numerous things, like formatting it, flashing factory images, and so on, but it turns out fastboot won't detect my device. ADB detects my device fine, but only in recovery. As far as I know, I don't have usb debugging enabled (since I formatted it). It currently has no OS since I formatted it. I've tried installing stock android since formatting it but it still gets stuck in a bootloop.
All my drivers are correct (I've re-installed them probably 10 times by now), and the images aren't corrupted (as far as I know).
I've run out of ideas, as I've been trying to figure this out for the past 2 days with no success. Any help would be appreciated.
Click to expand...
Click to collapse
Do you use 3.02.1. Twrp
Since you mention ADB works fine from recovery, have you tried to adb push a rom zip, and then flash it from your recovery?
Code:
adb push "/path/to/rom.zip" /data/media
ItsMason said:
I made some progress: my device is now detected in fastboot. I have literally absolutely no clue what happened. I guess it was a bit of randomness or luck or something (maybe wacky and goofy). I've done some flashing - I've flashed system, boot, recovery, cache, data, and radio, but it's still stuck in a bootloop. I don't know what's going on it with it now, but it seems like I haven't made any progress with fastboot.
Click to expand...
Click to collapse
Good. I see you mention flashing system, boot, recovery, cache(?), data(?) and radio. What do you mean by flash cache&data? You mean you've cleaned it? Formatting data is not usually a thing you have to do to recover from a bootloop.
What ROM have you flashed? Are you flashing stock? It's important you give more details so I can help you.
Have you flashed vendor.img? If you have been on a ROM that had it's own vendor.img and you went back to stock, then the vendor.imgs are different enough to cause a bootloop.
If all and all fails, we just want to see your system running so I'd recommend drop everything you are doing and follow these steps:
1. Access recovery (make sure you're using v 3.0.2.2)
2. Tap Wipe - > Advanced Wipe - > And check:
Dalvik / ART Cache
System
Internal Storage
Cache
3. Go to -> Pixel ROM (7.1.1) Get V 3.0 which was just uploaded recently. Please note it comes preconfigured with Gapps so no need to get that
4. You have to unzip the archive and you will see all the necessary img files (includes boot/vendor which are critical for boot). I strongly recommend manually flashing them. You can open the flash-all.bat file with a .txt editor and just follow the steps there.
After you have finished these steps, you should be free of a bootloop. From there, it is your decision where you. Either stay on a stock ROM or flash safely and always remember that you can make a backup and flash that backup in case you bootloop.
Good luck.
EDIT
Decay3 said:
Since you mention ADB works fine from recovery, have you tried to adb push a rom zip, and then flash it from your recovery?
Click to expand...
Click to collapse
I think his problem is deeper than a /system error. I'm guessing the wrong boot/vendor is flashed for the ROM he is trying to install and trying to guess which ROM would work on his current config would take more time than just starting from a clean flash.
Thanks for the help guys, but I gave up. I contacted Google and they sent me a replacement. Sorry for kind of wasting time.

HTC M9 Stuck in loop after trying to root

So I followed this thread https://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
All was going fine, after finishing rooting and rebooting the phone went straight to download mode and at the bottom it says "File /mnt/media_rw\ext_sd\0PJAIMG.ZIP FILE NOT FOUND" and it is now stuck in the reboot loop with the screen only displaying the logo and the message "this build is for development purposes only...."
I then tried this thread https://forum.xda-developers.com/showthread.php?t=1996665 to recover from it, but the links needed were down.
So I went into the recovery mode and tried to restore, but found that there was nothing to restore from. Then I rebooted it and now I'm not able to go into the recovery mode "failed to boot to recovery mode". Also adb will no longer display my device after trying the command "adb devices".
Tried uninstalling and installing the drivers, but no luck.
Horagino said:
So I followed this thread https://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
All was going fine, after finishing rooting and rebooting the phone went straight to download mode and at the bottom it says "File /mnt/media_rw\ext_sd\0PJAIMG.ZIP FILE NOT FOUND" and it is now stuck in the reboot loop with the screen only displaying the logo and the message "this build is for development purposes only...."
I then tried this thread https://forum.xda-developers.com/showthread.php?t=1996665 to recover from it, but the links needed were down.
So I went into the recovery mode and tried to restore, but found that there was nothing to restore from. Then I rebooted it and now I'm not able to go into the recovery mode "failed to boot to recovery mode". Also adb will no longer display my device after trying the command "adb devices".
Tried uninstalling and installing the drivers, but no luck.
Click to expand...
Click to collapse
Okay, so first of all you're using old threads to guide you and in the latter case, a guide build for another model phone. Assuming you are using an HTC One M9, your one-stop resource is the readme thread in this forum.
It sounds like you're going to need a RUU for your device. Before you ask ANYTHING about that, read the readme thread. It answers most every common question (and many uncommon ones), provides guides, and has links.
Once you've read the thread, if you have questions, post them here. We're absolutely happy to help - the readme thread ensures that we all start from the same level of understanding.
computerslayer said:
Okay, so first of all you're using old threads to guide you and in the latter case, a guide build for another model phone. Assuming you are using an HTC One M9, your one-stop resource is the readme thread in this forum.
It sounds like you're going to need a RUU for your device. Before you ask ANYTHING about that, read the readme thread. It answers most every common question (and many uncommon ones), provides guides, and has links.
Once you've read the thread, if you have questions, post them here. We're absolutely happy to help - the readme thread ensures that we all start from the same level of understanding.
Click to expand...
Click to collapse
Hi there, thanks for the reply. I have checked out the thread and I'm trying to follow the instructions in the RUU section, however I'm bit stuck. The third step requires me to copy the file into the SD Card, but I unfortunately have no direct access to that sd card with my PC. And like I said I cannot really use my phone to copy that file, nor can I use adb to copy it, since it doesn't detect my phone, although fastboot does.
You will need a pc to recover your phone in any circumstances. No pc = no recovered phone.
Beamed in by telepathy.
shivadow said:
You will need a pc to recover your phone in any circumstances. No pc = no recovered phone.
Beamed in by telepathy.
Click to expand...
Click to collapse
Not quite sure what you mean by pc, or if I explained it poorly. I do have a computer, but my computer does not have slots for sd cards, hence why I can't put any files on there, and adb won't detect my phone any more.
@edit: I think I know why I goofed up, the sd card I was using is 2GB only, and so I can't even use the RUU provided in the link above, since it is 2.2GB. I will shortly get a new sd card and see how it goes from there. Although if there is a way of doing this without the sd card and just my PC, I'm happy to hear it.
Horagino said:
Not quite sure what you mean by pc, or if I explained it poorly. I do have a computer, but my computer does not have slots for sd cards, hence why I can't put any files on there, and adb won't detect my phone any more.
@edit: I think I know why I goofed up, the sd card I was using is 2GB only, and so I can't even use the RUU provided in the link above, since it is 2.2GB. I will shortly get a new sd card and see how it goes from there. Although if there is a way of doing this without the sd card and just my PC, I'm happy to hear it.
Click to expand...
Click to collapse
There is no easier way to move forward than using a computer (PC, not a Mac). Yes, you could use another device to copy the RUU file to a SD card, but the guides are written with a computer in mind.
Like I said I DO have a PC, it's what I'm using to view and write this thread. My question is, is there a way to execute the RUU file from the PC to the Phone via the usb cable? Since my SD card is too small for that file. The guide says that it is theoretically possible that do it through HTC_fastboot, however it warns that there have been to many problems, so I don't want to risk it, since my phone also has the security features on.
Horagino said:
Like I said I DO have a PC, it's what I'm using to view and write this thread. My question is, is there a way to execute the RUU file from the PC to the Phone via the usb cable? Since my SD card is too small for that file. The guide says that it is theoretically possible that do it through HTC_fastboot, however it warns that there have been to many problems, so I don't want to risk it, since my phone also has the security features on.
Click to expand...
Click to collapse
Yes it's possible. The readme thread doesn't explore how because there are so many different ways a PC-to-phone flash can fail, where as the SD card method is dead simple.
You need a pc to transfer any updates or files to internal memory.
As you said, your memory card is too small for that file. Your other choices are to flash from pc, copy files from pc to phone, copy files from internet to phone.
If the phone doesn't boot to os then your only option is adb. You need a pc to use adb. You will need to access the phones recovery for adb too.
You can get another memory card but if your phone wont boot to os you'll need a pc for adb as your pc doesn't have sd slots.
So basically, you need a pc unless you know some voodoo or something to magic the file onto the phone..
Beamed in by telepathy.
I got a new sd card, 16gb. I also put the file on it using adb commands "adb push C:\adb\0PJAIMG.zip /sdcard" and using the rather broken recovery mode of TWRP I was able to confirm that the file is on there. However, step 5 says that I should be asked if I want to flash the file after booting to download mode, well... That is not happening
Tried installing it via TWRP recovery, however it says that the ZIP file is corrupted somehow.
So I just redownloaded the RUU file, it still says it is corrupted. Any clues as to how to fix it?
Nevermind, fixed it by using another phone to format the sd card and download the file straight to the sd card, then I could follow the instructions without a problem.
I however have one more question, how can I root my phone without going through all this sh** again?
Horagino said:
I however have one more question, how can I root my phone without going through all this sh** again?
Click to expand...
Click to collapse
The readme thread has a section on rooting. Be sure you pay attention to the guide's directions about versions - some versions of SuperSU are incompatible with the M9 and certain versions of TWRP correspond to your firmware version.
Congratulations on getting your phone functioning. Always nice to hear a success story.
If you have marshmallow 6.0 and a gsm phone just:
1, unlock your bootloader via htcdev.com.
2, Flash twrp and mount as "read only" (seems to be version dependent, i used 2.9.0.1 for 6.0 and have no issues to date).
3, make a backup of everything except data (or just system, up to you), you WILL need it one day so make a copy and store it somewhere very, very safe as it is your only fallback.
4, in twrp mount system as read/write and flash chainfires supersu.zip (like twrp, it seems to be version dependent. I used supersu 2.65 for 6.0 and have no issues to date). (use systemless root if asked, not sure if an actual system root is any good for this phone?).
5, buy s-off via sunshine app for $25. This is essential if you want a reasonable chance of recovery should anything go drastically wrong later on. Being able to flash unsigned stuff gives an extra option towards recovery.
It's not too difficult once you get the hang of it, I was panicking too when I did mine. Rightly so, these things brick too easy!. I implore you to cross reference the steps against other material from other xda members just incase I missed something by accident. The last thing you need to do is bugger it up now but I'm confident I have it pretty damn close.
Beamed in by telepathy.
I decided to flash a different ROM; Android HD revolution. Everything went fine and everything works fine.
However, I do have one more question. Whenever I go into the download mode, I still get this message in yellow at the bottom of the screen "File /mnt/media_rw\ext_sd\0PJAIMG.ZIP FILE NOT FOUND", not sure if it's a left over from previous failures or if I'm missing something.

Unable to install ADB driver. Nexus locked to TWRP recovery

Good morning guys.
I'm not really new to this forum, I've known you for years and I've always followed you for small "mods" or particular problems that I had over time with my devices.
I apologize, but I would like to ask you for help because I have big problems with an ASUS Nexus WiFi 32GB Tablet
Unfortunately, I can in no way connect it to the PC in order to install any rom (I wanted to install the rom stock). I tried everything, I even formatted an old PC and installed windows XP hoping for more compatibility (nostalgic).
The first time, I managed to install a ROM from TWRP recovery 2.8, enabling the USB-OTG and buying the appropriate cable, but then unfortunately, I wanted to try to change ROM and already I was there I wanted to update the recovery to 3.3 .1.0, but I must have been wrong to click somewhere in the recovery. I was convinced that the USB-OTG could always be enabled, so I had the security that I would always be able to install a S.O.
Now the S.O is no longer present in the device and from recovery I can no longer enable USB-OTG, and obviously in the device, no image is present that can help me, probably because I have eliminated everything with different wipes.
The PC in no way manages to see the device, whatever driver I try to install, it tells me that they have no information regarding the connected device, so I can't even use adb.
Please, help me, if needed, format a PC and install Linux or anything else I can use to resurrect this damn device.
Thank you so much for existing ...
Hello, did you try to reboot your tab in bootloader mode, and then install stock factory image from Asus? Maybe After that you will be able to reinstall twrp and custom rom you want... Your tab is unlocked? Did you try the wugfresh tool? Good luck
Thanks for the reply ichi-nii, I tried to reboot the device in bootloader mode (The menu with the open heart robot, Fastboot Mode, right?), Even if it doesn't give me many options, I can only choose whether to Turn off the device, Start it in Recovery (TWRP) or restart the Bootloader, nothing more, and from here I can't install anything anyway.
I believe the device is unlocked, or at least it was, and Fastboot tells me that it is unlocked, so ...
To use the Wugfresh tool, if I didn't err I have to be able to connect this Nexus to the PC and make it see it, but as I said ... No driver allows me to recognize this device from the PC ...
I don't know what to do ...
Isn't there a TWRP terminal way to do something? Some commands that can re-enable the USB-OTG ...
I think I inadvertently (because I didn't know what I was going towards) SELinux enabled, it was after this that the USB-OTG didn't work anymore (I think) ...
Sorry for you bro, so you tell me even in bootloader mode , the tab is not recognized ? Maybe try to connect it when you are in twrp, And another one thing, maybe try another usb port or cable... About otg I can't help you , maybe your connector is broken? Did you try with windows 7 or linux( just to send files to sdcard)
edit: I just try to connect my tab (twrp mode on the screen) to my computer with kali Linux and I Can access to sdcard on the tab
ichi-nii said:
Sorry for you bro, so you tell me even in bootloader mode , the tab is not recognized ? Maybe try to connect it when you are in twrp, And another one thing, maybe try another usb port or cable... About otg I can't help you , maybe your connector is broken? Did you try with windows 7 or linux( just to send files to sdcard)
edit: I just try to connect my tab (twrp mode on the screen) to my computer with kali Linux and I Can access to sdcard on the tab
Click to expand...
Click to collapse
Thank you so much for your help!
I tried to connect the device, both from TWRP and from Fastoboot mode but it is not recognized by Windows ... (Both Windows XP, Windows 7 and Windows 10) I tried to change USB ports and I also tried to change the cable, but nothing ...
The OTG cable is new, I used it on this device and it worked perfectly, I tried it on another device and it works, so the cable is ok, I must have done some **** myself.
Sending any file to the device is just what I'm desperately trying to do, I don't care how, I'm interested in doing it and fixing the damn thing.
If you tell me that your computer with Kali Linux sees it and you can access the memory, I try immediately.
Thank you so much !!
I'm not at all an expert on Linux, how does it work in this case? From Linux terminal? do I have to send commands? Or is it seen as a folder? ....
Forgive my humble ignorance ...
? I'm not an expert too? just install any linux with graphic interface then open the file manager , I did this with kali just because I have it on an old computer.
Good luck
ichi-nii said:
I'm not an expert too just install any linux with graphic interface then open the file manager , I did this with kali just because I have it on an old computer.
Good luck
Click to expand...
Click to collapse
I have to thank you for the help, from Linux I can easily see the device, I managed to insert in the internal memory the rom that I had previously installed ... so I took a big step forward! Unfortunately the misfortune haunts me and the recovery doesn't want to know to install that damn rom. I had to fall back on a Slimroms that I found here on the forum, but I'm not exactly where I want to be. I would like to be able to install my ROM or at most something more complete and updated. Now I try to install the GApps so that I can install some apps that allow me to permanently disable SELinux, then try again to Flash my rom ...
I do not know how to thank you! You have been very helpful.
IgNuReNt said:
I have to thank you for the help, from Linux I can easily see the device, I managed to insert in the internal memory the rom that I had previously installed ... so I took a big step forward! Unfortunately the misfortune haunts me and the recovery doesn't want to know to install that damn rom. I had to fall back on a Slimroms that I found here on the forum, but I'm not exactly where I want to be. I would like to be able to install my ROM or at most something more complete and updated. Now I try to install the GApps so that I can install some apps that allow me to permanently disable SELinux, then try again to Flash my rom ...
I do not know how to thank you! You have been very helpful.
Click to expand...
Click to collapse
Congratulations, like you said it's a big step. Do you use the last twrp? Maybe the problem comes from that...
ichi-nii said:
Congratulations, like you said it's a big step. Do you use the last twrp? Maybe the problem comes from that...
Click to expand...
Click to collapse
I updated the TWRP to 3.3.1.0, I think it is quite up to date, but it is strange that this is so, because from OTG I installed it quietly without problems ... I am convinced that SELinux blocks something ...
I also tried to check the zip file before installation and it gives me an error, it can't install ...
I'm going crazy ... but at least now I have the chance to do tests!
IgNuReNt said:
I updated the TWRP to 3.3.1.0, I think it is quite up to date, but it is strange that this is so, because from OTG I installed it quietly without problems ... I am convinced that SELinux blocks something ...
I also tried to check the zip file before installation and it gives me an error, it can't install ...
I'm going crazy ... but at least now I have the chance to do tests!
Click to expand...
Click to collapse
And now Can you connect the tab to your computer (with windows this Time) If yes you can try install the rom you want from the wugfresh tool?
ichi-nii said:
And now Can you connect the tab to your computer (with windows this Time) If yes you can try install the rom you want from the wugfresh tool?
Click to expand...
Click to collapse
My dear friend! You are an ace, a beast! It was only thanks to you that I was able to solve my problem. Thank you very much, now there is a little 7-year-old who can come back and have fun with this Nexus 7, and of course he also thanks you very much.
I'll tell you briefly how I had to move and the problems I encountered and how I solved it step by step, so that if it happens to someone else, it may have a path to follow eventually.
I was screwed, after I managed to copy the stock image from flash to Kali-Linux inside the Nexus 7, because that damned TWRP crashed during installation without giving me a reason, I had to restart the tablet and that's it; from linux, same speech with ADB Sideload, did not complete the installation.
So I tried to Flashare a custom image, Slimrom that gave me only problems right away, I couldn't touch anything that gave error (but it was installed .. so I was still hoping).
So I tried to flash my damned stock rom directly from Fastboot, but it gave me a thousand mistakes of every kind, from there I suspected that there was something wrong with the file system or the partitions ... something must have messed up something , it was not possible that I could not install any roms anymore, not even the wipe worked, there was something strange, I thought of starting from the base.
So from recovery I found the function that allows you to change File System in the various partitions, so one by one I restored F2FS, the Wipe worked magically, the road was the right one.
I start with the installation of the Stock Rom ... but nothing, errors concerning the lack of files or information (now unfortunately I don't remember in detail)
Reading on the forum, I realized that it could be a common problem and that you could flash the individual files contained in the "stock.img" file that I had downloaded, even individually. So I extracted the archive of the downloaded stockrom, extracted the same .img file inside it, I found myself with all those files.img (boot.img / recovery.img / userdata.img etc etc) at that point I have them flash them one by one with the special fastboot commands.
eeeeeeeeeeeeeeeeeeeee
Taaaaaaaaaaakkkkk
Now it finally starts, it works !!!!!
All this, thanks to you, with that idea of ​​connecting it to linux you gave me hope and it worked !!
I am Italian, from Rimini, if you ever happen in Italy you have a paid fish dinner !!!!!
Thanks again!!!!
IgNuReNt said:
My dear friend! You are an ace, a beast! It was only thanks to you that I was able to solve my problem. Thank you very much, now there is a little 7-year-old who can come back and have fun with this Nexus 7, and of course he also thanks you very much.
I'll tell you briefly how I had to move and the problems I encountered and how I solved it step by step, so that if it happens to someone else, it may have a path to follow eventually.
I was screwed, after I managed to copy the stock image from flash to Kali-Linux inside the Nexus 7, because that damned TWRP crashed during installation without giving me a reason, I had to restart the tablet and that's it; from linux, same speech with ADB Sideload, did not complete the installation.
So I tried to Flashare a custom image, Slimrom that gave me only problems right away, I couldn't touch anything that gave error (but it was installed .. so I was still hoping).
So I tried to flash my damned stock rom directly from Fastboot, but it gave me a thousand mistakes of every kind, from there I suspected that there was something wrong with the file system or the partitions ... something must have messed up something , it was not possible that I could not install any roms anymore, not even the wipe worked, there was something strange, I thought of starting from the base.
So from recovery I found the function that allows you to change File System in the various partitions, so one by one I restored F2FS, the Wipe worked magically, the road was the right one.
I start with the installation of the Stock Rom ... but nothing, errors concerning the lack of files or information (now unfortunately I don't remember in detail)
Reading on the forum, I realized that it could be a common problem and that you could flash the individual files contained in the "stock.img" file that I had downloaded, even individually. So I extracted the archive of the downloaded stockrom, extracted the same .img file inside it, I found myself with all those files.img (boot.img / recovery.img / userdata.img etc etc) at that point I have them flash them one by one with the special fastboot commands.
eeeeeeeeeeeeeeeeeeeee
Taaaaaaaaaaakkkkk
Now it finally starts, it works !!!!!
All this, thanks to you, with that idea of ​​connecting it to linux you gave me hope and it worked !!
I am Italian, from Rimini, if you ever happen in Italy you have a paid fish dinner !!!!!
Thanks again!!!!
Click to expand...
Click to collapse
Yessssss! Congratulations bro ! That's a very good news ?
IgNuReNt said:
My dear friend! You are an ace, a beast! It was only thanks to you that I was able to solve my problem. Thank you very much, now there is a little 7-year-old who can come back and have fun with this Nexus 7, and of course he also thanks you very much.
I'll tell you briefly how I had to move and the problems I encountered and how I solved it step by step, so that if it happens to someone else, it may have a path to follow eventually.
I was screwed, after I managed to copy the stock image from flash to Kali-Linux inside the Nexus 7, because that damned TWRP crashed during installation without giving me a reason, I had to restart the tablet and that's it; from linux, same speech with ADB Sideload, did not complete the installation.
So I tried to Flashare a custom image, Slimrom that gave me only problems right away, I couldn't touch anything that gave error (but it was installed .. so I was still hoping).
So I tried to flash my damned stock rom directly from Fastboot, but it gave me a thousand mistakes of every kind, from there I suspected that there was something wrong with the file system or the partitions ... something must have messed up something , it was not possible that I could not install any roms anymore, not even the wipe worked, there was something strange, I thought of starting from the base.
So from recovery I found the function that allows you to change File System in the various partitions, so one by one I restored F2FS, the Wipe worked magically, the road was the right one.
I start with the installation of the Stock Rom ... but nothing, errors concerning the lack of files or information (now unfortunately I don't remember in detail)
Reading on the forum, I realized that it could be a common problem and that you could flash the individual files contained in the "stock.img" file that I had downloaded, even individually. So I extracted the archive of the downloaded stockrom, extracted the same .img file inside it, I found myself with all those files.img (boot.img / recovery.img / userdata.img etc etc) at that point I have them flash them one by one with the special fastboot commands.
eeeeeeeeeeeeeeeeeeeee
Taaaaaaaaaaakkkkk
Now it finally starts, it works !!!!!
All this, thanks to you, with that idea of ​​connecting it to linux you gave me hope and it worked !!
I am Italian, from Rimini, if you ever happen in Italy you have a paid fish dinner !!!!!
Thanks again!!!!
Click to expand...
Click to collapse
ichi-nii said:
Yessssss! Congratulations bro ! That's a very good news
Click to expand...
Click to collapse
Thanks guys, I stumbled across this thread and changed the file system of System & Data partitions to F2FS (from ext4) and everything seemed to work normally after that. Thank you!
[email protected] said:
Thanks guys, I stumbled across this thread and changed the file system of System & Data partitions to F2FS (from ext4) and everything seemed to work normally after that. Thank you!
Click to expand...
Click to collapse
Congrats

Categories

Resources