yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] motorbreath1:
I have d/l'd the latest image but I still cannot get anything to recognize my device in adb. I've tried several different driver configurations. The official drivers, samsung, pdanet. Nothing is allowing my device to be recognized. However, my pc recognizes it as "bootloader interface", but when I try to use a program to fix it, the programs will not recognize an adb device.

Thank you.
[Nexus 7 Q&A, Help & Troubleshooting] Erovia:
In bootloader mode you cant use adb, only fastboot.
[Nexus 7 Q&A, Help & Troubleshooting] motorbreath1:
Ok. You have been very helpful and I thank you immensely. One more question if you would oblige. What steps would you take to solve this problem?
[Nexus 7 Q&A, Help & Troubleshooting] Erovia:
All I can say is follow this guide.

It even says that there is something wrong with the JWR66Y bootloader.

So if you'd like to have 4.3 then proceed as the guide says, if you want 4.4 then simply use the latest (KOT49H) factory image with the same commands.
[Nexus 7 Q&A, Help & Troubleshooting] motorbreath1:
You, sir, are a life saver. A thousand thanks!

---------- Post added at 11:11 PM ---------- Previous post was at 10:56 PM ----------

To anyone with bootloop issues or needing to reflash stock images, don't bother with toolkits. The above link posted by Erovia to help me do it by hand was so much less nerve racking, quicker, and so much easier. I couldn't believe it. Once again, much thanks to Erovia for pointing me in the right direction to getting my Nexus back on track.
[Nexus 7 Q&A, Help & Troubleshooting] liljester:
Thanks a ton guys, my daughters nexus 7 tried to update today and crashed and burned. then i downloaded the latest image from google... and followed instructions to flash the newest from fastboot mode.. erased everything, tried to flash the bootloader back and it wouldnt take it with the "remote: invalidstate" error on the command line. i downloaded just the bootloader image posted here and its working like a charm now.
[Nexus 7 Q&A, Help & Troubleshooting] D-Trixxx:
I hate to revive older threads but I just wanted to thank everyone who worked on this issue. Saved me countless hours and fixed my issue right away.

Your work is appreciated.
[Nexus 7 Q&A, Help & Troubleshooting] kypeth:
Just wanted to make it clear, I still needed this to manually install the 4.4.3 image from Google's Factory Images page.
[Nexus 7 Q&A, Help & Troubleshooting] mrrtys:
Also thanks everyone.

I used the bootloader attached to update to 4.4.3... Spend all evening on this ****...couldn't have fixed it without y'all.
[Nexus 7 Q&A, Help & Troubleshooting] :
No changes in 4.4.4 (KTU84P) bootloader checksum compared to 4.4.3 (KTU84L). So it's still bugged, if anyone was curious.
[Nexus 7 Q&A, Help & Troubleshooting] klipper:
What to do now?

A few days ago I updated the Nexus7 of a friend of me from Jellybean 4.2.2 (Bootloader 4.18) to Kitkat 4.4.4 using Wugs Nexus Root Toolkit.

During flashing I got the error that bootloader 4.23 was required. Also I got the errors during flashing concerning invalid bootloader.

Finally I used the suggested "Force flash mode". Using this mode I succeeded to flash the factory image of Kitkat 4.4.4.

Everything looked OK..... But now I found that the bootloader is still version 4.18 :( Also I found that the Nexus7 changed from a 32GB to a 8GB WiFi Nexus 7. Tomorrow I will try to do a format of /data using TWRP to get the lost storage back, but what to do with the bootloader issue?

Will it be better to reflash back to Jellybean 4.2.2 (JDQ39) containing the current bootloader 4.18, then flash the alternative bootloader from JWR66V, then update to Jellybean 4.3 (JWR66Y) and then the last step update to Kitkat 4.4.4 (KTU84P)?

Or can I flash the boatloader from JWR66V into the current 4.4.4 (KTU84P) installation?

Any advice will be welcome!
[Nexus 7 Q&A, Help & Troubleshooting] :
Flash the 4.23 bootloader from the 1st post in this thread and perform a factory reset. Think that should fix the storage problem. If not, reflash the 4.4.4 factory image, except the bootloader, since it's bugged.
[Nexus 7 Q&A, Help & Troubleshooting] stas_:
Thank you!!!

I was trying to upgrade my Nexus 7 (2012) from JDQ39 to KTU84P using the Nexus Recovery Toolkit. I kept getting an InvalidState error when flashing the bootloader.

I ended up getting it to work by swapping in the bootloader image from JWR66V (bootloader-grouper-4.23.img) that you posted. Presumably the one that came with KTU84P is corrupted!

What a mess.
[Nexus 7 Q&A, Help & Troubleshooting] Marqus65:
Thanks! My Tilapia is alive again. I am just wondering that google still offers the factory image, containing not-working files. :/

Glad to have you guys here!:good:
[Nexus 7 Q&A, Help & Troubleshooting] shutin:
Thank you for the help everyone. Just to sum up for any new people, this is how to revert to the latest stock.

Download the latest factory image (4.4.4) from https://developers.google.com/android/nexus/images. It won't say grouper, it sasy nagasaki or whatever for 2012 nexus 7 wifi only.

unzip/tar/tgz components with 7-zip. replace the bootloader-.23.img file with one of the working versions from this thread. md5 = df53028033c9eccf4fe5ba7bc198ce24

boot into fastboot.

run flash-all.bat

done! you could relock the bootloader but i dont see the point if you are going to start customizing again. maybe for resell.

thanks again!
[Nexus 7 Q&A, Help & Troubleshooting] feelpt:
thank you so much for this... you have no idea how much time i spent looking to fix my nexus 7...

it's working!!!

thanks again
[Nexus 7 Q&A, Help & Troubleshooting] Uncleheff:
Been stuck here forever!!!! Like 30 minutes!!!! I don't know if its my slow computer or if I did something wrong.
[Nexus 7 Q&A, Help & Troubleshooting] organophosphate:
Thanks for the useful advice, Eregoth. I had a slightly different issue crop up that required flashing a 4.18 bootloader in order to be able to reapply the 4.23 bootloader.

I attempted to apply the factory image for 4.4.4 (obtained straight from Google) using the flash-all script. It ended up soft-bricked at the "coalescing blobs" stage. I then tried applying JWR66Y, with the same issue. I then flashed *successfully*, the correct JWR66V bootloader. However, even though I applied the full update, I found I ended up stuck in the same soft-bricked state.

My bootloader reported it was 4.23, but I could not "fastboot flash bootloader" reapply the correct df53028033c9eccf4fe5ba7bc198ce24 MD5 bootloader image—it gave a signature mismatch. This was bizarre, because the device was reporting a signature mismatch for the same bootloader it had previously applied.

I had to drop back to installing the 4.18 bootloader from a different factory image and *then* I could reapply the df53028033c9eccf4fe5ba7bc198ce24 4.23 bootloader. The device will now happily reflash the same bootloader image repeatedly. I can only conclude there was some form of corruption despite all the signing that is going on with bootloader updates.

After that, the 4.4.4 (ktu84p) update applied and booted. Of course, I made certain to excise the corrupt ktu48p bootloader image from the flash process.
[Nexus 7 Q&A, Help & Troubleshooting] osyadolgo:
thank very helpfull

I was looking for this for long time

Thanks man!
[Nexus 7 Q&A, Help & Troubleshooting] bigsee:
It is a known issue with the BL by Google but there is a solution:

http://xdaforums.com/showthread.php?t=1907796

BTW: the image name is nakasi/g (not nagasaki ;))
[Nexus 7 Q&A, Help & Troubleshooting] simonbove:
I just wanted to let people know it is the same problem with Android 5.0 (nakasi-lrx21p)

I replaced the bootloader with the one from jwr66v and then it installs perfectly :)
[Nexus 7 Q&A, Help & Troubleshooting] fvisagie:
5.0.2 (LRX22G) has the same problem, as does at least the JWR66Y from JDQ39 OTA for Nexus 7 3G. See http://xdaforums.com/nexus-7/general/info-nexus-7-3g-ota-bootloader-corrupt-t3033513
[Nexus 7 Q&A, Help & Troubleshooting] mxl180:
woohoo finally able to revert back using this!
[Nexus 7 Q&A, Help & Troubleshooting] Generalil:
Doesn't Nexus 7 use the same bootloader as most devices - The Qualcomm Little Kernel, which is available here : https://www.codeaurora.org/cgit/quic/la//kernel/lk/tree/?id=refs/heads/eclair ?

Just curious
[Nexus 7 Q&A, Help & Troubleshooting] genericfu:
possible fix

Haven't tested it, but looks like Google updated the bootloader in the factory images on April 2. Maybe someone finally noticed it was broken...:eek:

---------- Post added at 10:08 AM ---------- Previous post was at 09:51 AM ----------

[MENTION=5202125]s107ken[/MENTION] has confirmed the new bootloader fixes the problem on nakasi 3G. Promising.
[HTC Droid DNA] jko76:
Hello

I got HTC J Butterfly from Japan and have been trying to get it working in Finland since.

We tried first to change the phone to Taiwan version (x920d), but the result was no good 2G.

The next step was to try to change to phone into Droid DNA,

Starting point:

DELUXE_J PVT SHIP S-OFF

CID-KDDI_801

HBOOT-1.41.0000

RADIO-1.01.10.0201

OpenDSP-v6.120.274.0114

Original HTC J Butterfly ROM

What was done:

1. installed jdk1.7.0_25 and android sdk tools, platform tools and google usb driver (installer_r22.0.5)

2. installed ViperDNA 1.3.5 ROM (via CWM recovery from external sd card)

3. installed engineering HBOOT (see below)

fastboot oem rebootRUU

fastboot flash zip xxxxxx.zip

4. installed twrp recovery: twrp-htc-dlxj.img

5. modify (CID: 11111111 and IMEI and MEID according to my phone) in mmcblk0p5 block file and copy to /dev/block with dd:

dd if=/sdcard/mmcblk0p5 of=/dev/block/mmcblk0p5 (copied to /sdcard/ with adb push in recovery mode)

NOTE1: HERE ADB STILL OK

6. fastboot oem writemid PL8320000

NOTE2: HERE ADB CANNOT BE USED ANYMORE

NOTE3: phone was encrypted and asking for password (cleared by formatting internal SD)

7. flash firmware

fastboot oem rebootRUU

fastboot flash zip dna2.06firmware.zip

7.1 installed twrp recovery: twrp-htc-dlx.img

8. installed engineering HBOOT (see below)

fastboot oem rebootRUU

fastboot flash zip xxxxxx.zip

Current situation:

MONARUDO PVT ENG S-OFF

CID-11111111

HBOOT-1.39.2000 (PL8320000)

RADIO-1.01.04.0308

OpenDSP-v6.120.274.0114

No ROM currently

Fastboot USB (OK)

ADB (NOK)

USB connection (NOK)

- cannot connect to device from Windows 7 or Windows XP, because the phone/device is flashing as portable device called:

WPD FileSystem Volume Driver

What I would like to do is to flash ROM.

but since I cannot transfer any files to the system it seems to be impossible.

I can flash in fastboot, because that is working just fine.

Any ideas how to proceed are more than welcome !?

Thank you
[HTC Droid DNA] thehoovie:
Can you run the RUU ? Or if can not because windows does not see it, run the RUU to extract the files to temp folder, then flash the zips manually via fastboot?

You prolly have seen this thread;

http://xdaforums.com/showthread.php?t=2155334
[HTC Droid DNA] jko76:
Thanks for the reply.

What do you mean by running the RUU ? fastboot oem rebootRUU ? (that is working for me)

I was also thinking that I cannot flash anything for DELUXE_J since I changed the moid. Not sure if this is true ?

Thanks
[HTC Droid DNA] jko76:
Hello again

Currently I'm assuming there is no way to install ROM without working USB/ADB, because no replies.

If you know such method and needed files please let me know.

Thank you
[HTC Droid DNA] jko76:
Hello

Raised the topic since I have not received any replies.

Most probably someone knows how to get the phone working again (install ROM).

Please help. Thanks
[HTC Droid DNA] times_infinity:
Since you're S-OFF you could probably just change the model id back to the J Butterfly the same way you changed it to the DNA
[HTC Droid DNA] jko76:
For changing the model id I would need to copy a block file to the device. Currently i cannot do that.

Any other ideas ?
[HTC Droid DNA] times_infinity:
In the OP you said you changed the model id with fastboot oem writemid.

Since you're soff, you should just be able to do that again, back to the J Butterfly mid
[HTC Droid DNA] coachcrey:
Yeah why did you flash DNA files on a j butterfly anyways man you probably messed the phone up .
[HTC Droid DNA] jko76:
In the OP step 5 I copied Droid DNA block file into my phone and then changed the mid. I was thinking that without putting back my original

block HTC J blockfile I cannot change the mid back. Of course I could try the command but I'm worried that the incorrect block file mid combination will brick the phone totally.

Is there any RUU available for Droid DNA that could be flashed through fastboot ?

Thanks
[HTC Droid DNA] jko76:
The idea was to try to make the phone working in Finland (the phone was locked to AU network in Japan). It did not work with x920d SW (2G NOK) and therefore decided to give the DNA SW a go.

Yes, the phone might be messed up, but still I would like to think there is a way to recover since the fastboot and recovery are working.

Thanks
[HTC Droid DNA] coachcrey:
I guess the better question is who gave you the idea to try and flash dna files on a butterfly to my understanding they are similar phones not the same.
[HTC Droid DNA] jko76:
The idea was mine.

We tried x920d SW as well and that was working apart from the unstable 2G connection.
[HTC Droid DNA] jko76:
I can run the RUU*.exe until it checks the USB connectivity. In the temp files I can find the data1.cab file which most probably has the image files that I would need. The remaining problem is that I cannot extract the data1.cab file.

Does anyone know how to extract the cab file ?

Thank you
[HTC Droid DNA] jko76:
Actually I found the ROM.zip as well from temp directory. I cannot unzip the file.

How to use this ROM.zip file ?
[HTC Droid DNA] times_infinity:
Use ruuveal to decrypt the zip
[HTC Droid DNA] jko76:
Done and now I can open/extract the rom.zip. There are many .img files inside.

Now I need some help how to proceed ?

Please remember that the phone is S-OFF and engineering HBOOT is currently installed.

Do I need to change HBOOT ? What about S-ON ?

What is the best way of flashing the images ?

Thank you very much for your help.
[HTC Droid DNA] times_infinity:
You can try just flashing the whole zip. Do fastboot oem rebootRUU and then fastboot flash zip ruu.zip
[HTC Droid DNA] jko76:
AFTER fastboot flash zip rom.zip:

MONARUDO PVT SHIP S-OFF

CID-11111111

HBOOT-1.33.0001

RADIO-1.00.00.1023_3

OpenDSP-v4.120.240.0920

eMMC-boot

fastboot flash recovery twrp-htc-dlx.img

TWRP recovery installed

fastboot flash zip PL832.zip

MONARUDO PVT ENG S-OFF

HBOOT-1.39.2000 (PL8320000)

Unfortunately the USB/ADB is still unstable. Also it seems that the ROM does not boot up. The droid boot image can be seen. Then it goes away and I can see in the upper part of the screen USB debugging connected flashing...

Fastboot interface is ok, bootloader and recovery as well.

Let's see what could be the next step/try. Currently it seems that Droid SW cannot be used with HTC J Butterfly HW !?
[HTC Droid DNA] pio_masaki:
All I can offer is they obviously have differences or the kernels would be the same. Try using the proper kernel for it and see if it proceeds any further in booting the ROM. Making it think its a DNA doesn't change the hardware itself, at a minimum the kernel needs to be the correct one foe the device hardware, not name, and maybe the ROM just to eliminate drivers and libs being incompatible as well.

Or is the kernel the same? :confused:

Tapatalked from my HTC DNA - Carbon
[HTC Droid DNA] jko76:
I have no idea if the kernels are the same. Most probably those are different.

Is there any way to see the kernel version from the phone ?

I have no idea how to continue. The x920d SW was booting up and the only problem was the unstable 2G.

The problem is that I cannot change the model id anymore because file transfer is busted --> cannot go back to x920d or J butterfly SW !?

UPDATE: After factory reset the unlock bullet can be seen on the screen, but as soon as I unlock the device reboots.

All ideas are welcome
[HTC Droid DNA] pio_masaki:
I still suggest you use a proper ROM and kernel for that device before trying to diagnose anything else. Once that has you a working device, then play with kernels and roms or radios or whatever else, no use troubleshooting an unstable platform if its not necessary.

Tapatalked from my HTC DNA - Carbon
[HTC Droid DNA] daorderdillon:
Take out the sd card and use an adapter then plug the adapter with the sd card in it in the computer and transfer the Rom on it. When Ur done take sd card from out of the adapter then out it back in the phone and flash the Rom then attach the phone bk to the pc if your not s off and put it in fastboot then flash boot image extracted from Ur Rom
[HTC Droid DNA] jko76:
Ok, I understand.

The goal is to get the phone SIMFREE and working in Finland (3G and 2G)

If you have any ideas how I can flash the HTC J Butterfly stock back, please let me know.

I cannot change the model id currently. I have been thinking it is mandatory to change the model id before can flash back to stock J butterfly.

Thank you
[HTC Droid DNA] jko76:
The external sd card does not work with Droid SW (maybe because there is no slot for external sd card in the Droid HW at all?).
[HTC Droid DNA] pio_masaki:
Yeah it doesn't allot for an external SD card, you'd need one customized to run as a DNA on that hardware and use the slot. Nothing huge, a little touch up in init and vold fstab should do it.

Tapatalked from my A100 - Jellytime Sosei 4.3
[HTC Droid DNA] jko76:
Could you be more specific how to achieve this ?

Can you think of any way of changing the model id back to deluxe_j ?

Thank you for your help
[HTC Droid DNA] pio_masaki:
The model id stuff I have no idea, I've never done any of that. Init and vold and fstab will all need the proper entries for the external SD to pick it up. If you can link me the ROM you're using I can add those in for you. Recovery also, if its a DNA recovery.

Tapatalked from my HTC DNA - Carbon
[HTC Droid DNA] jko76:
Thank you for the kind offer. I have extracted the currently installed rom.zip from this:

RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed.exe

https://docs.google.com/file/d/0B32gqnbh2ZecSHM2VXJoY2tFUU0/edit?usp=sharing

Do you need the decrypted rom.zip ?

Based on this experiment I cannot use the Droid DNA ROMs with my HTC J Butterfly and therefore I need to find out a way to go back

to some other Butterfly ROM. For that I need to change the model id. It means that I need to able to copy one block file into the /dev/block.

If I get the external SD working that means that I can copy the block file into the external card, but I don't know if I can copy the file into /dev/block from the external SD. I don't have working ADB.
[HTC Droid DNA] thehoovie:
Can you post your edits or summarize what edits would need to be done to allow SD card for DNA ROMs ? What about the IR port ? Wouldn't we need custom kernel too that knows about these two additional HW components ?
[HTC Droid DNA] jko76:
Yes, it would be good to know how to get these extra HW components working if possible.

Any ways to fix the unstable ADB/USB ?

Is there any other way than ADB to copy files into the phone ? Fastboot ?

How to extract the .img files ?

Currently I'm stuck with this project :confused:
[HTC Droid DNA] jko76:
Hi all

My model ID is currently: PL8320000

What happens if I flash the HTC J Butterfly RUU ?

Currently:

MONARUDO PVT ENG S-OFF

CID-11111111

HBOOT-1.39.2000 (PL8320000)

RADIO-1.00.00.1023_3

OpenDSP-v4.120.240.0920

eMMC-boot

Thanks
[HTC Droid DNA] jko76:
REOPEN: how to recover ?

Hello everybody

Starting point:

DELUXE_J PVT SHIP S-OFF

CID-KDDI_801

HBOOT-1.41.0000

RADIO-1.01.10.0201

OpenDSP-v6.120.274.0114

Original HTC J Butterfly ROM

What was done:

1. installed jdk1.7.0_25 and android sdk tools, platform tools and google usb driver (installer_r22.0.5)

2. installed ViperDNA 1.3.5 ROM (via CWM recovery from external sd card)

3. installed engineering HBOOT (see below)

fastboot oem rebootRUU

fastboot flash zip xxxxxx.zip

4. installed twrp recovery: twrp-htc-dlxj.img

5. modify (CID: 11111111 and IMEI and MEID according to my phone) in mmcblk0p5 block file and copy to /dev/block with dd:

dd if=/sdcard/mmcblk0p5 of=/dev/block/mmcblk0p5 (copied to /sdcard/ with adb push in recovery mode)

NOTE1: HERE ADB STILL OK

6. fastboot oem writemid PL8320000

NOTE2: HERE ADB CANNOT BE USED ANYMORE

NOTE3: phone was encrypted and asking for password (cleared by formatting internal SD)

7. flash firmware

fastboot oem rebootRUU

fastboot flash zip dna2.06firmware.zip

7.1 installed twrp recovery: twrp-htc-dlx.img

8. installed engineering HBOOT (see below)

fastboot oem rebootRUU

fastboot flash zip xxxxxx.zip

Current situation:

MONARUDO PVT ENG S-OFF

CID-11111111

HBOOT-1.39.2000 (PL8320000)

RADIO-1.01.04.0308

OpenDSP-v6.120.274.0114

RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00 .00.1023_3_NV_VZW_1.98_002_release_290923_signed.exe (rom.zip installed from this exe file)

Fastboot USB (OK)

ADB (NOK)

USB connection (NOK)

- cannot connect to device from Windows 7 or Windows XP, because the phone/device is flashing as portable device called:

WPD FileSystem Volume Driver

What I would like to do is to flash back to stock !

The million dollar question is how to flash back to HTL21 stock, when the model id is DNA Droid and cannot be changed due

to non working ADB ?

Can I flash HTL21 stock sw anyway ? Is there any way to change the model id back to HTL21 ?

Any ideas are welcome !

Thank you
[HTC Droid DNA] .torrented:
You need to find your devices files in order to do that without your devices file there isn't much anybody can do

Basically you would need to find an butterfly J RUU or butterfly J .IMG files
[HTC Droid DNA] jko76:
Ok. This part I actually understood ; )

Lets say that I have the RUU or IMG files. What should I do next to be able to flash it ?

Thank you
[HTC Droid DNA] .torrented:
You will need to flash the J's bootloader back then I would run the RUU, you may need to change the mid back to its original id
[HTC Droid DNA] jko76:
I cannot change the mid because I dont have access via ADB. Due to nonworking ADB I cannot change the block file back to original HTL21 one.

Any idea what I can flash without changing the mid ?

Here is the zip file I have:

PL99IMG_DLX_WLJ_JB_45_KDDI_JP_1.15.970.1_R_Radio_1.00.10.1127_3_NV_2.28_01C_release_signed

Currently I have engineering HBOOT installed. If I flash J's bootloader the phone will not boot up anymore.

Is my understanding correct ?

Thanks a lot
[HTC Droid DNA] .torrented:
You cant even use adb in recovery? have you tried to fastboot flash the correct recovery first?

if not maybe try to extract the ROM.zip out of the ruu and fastboot flash it that may work, i really cant help a whole lot as it looks like you really done goofed, sorry not trying to be mean.

Extract Guide ----> http://xdaforums.com/showthread.php?t=2534428
[HTC Droid DNA] jko76:
That is correct. I cannot use ADB in recovery either. By correct recovery you mean recovery for HTL21 ? Currently my recovery is for the DROID.

Does flashing correct recovery help somehow to get the adb working on the recovery mode ?

Thank you for your time

Janne
[HTC Droid DNA] .torrented:
Yes, there is a good chance that it would because the recovery contains a kernel that is specific to your device, which would mean working usb/adb (90%) sure this would work