yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" Android Development] draxie:
Hmm... interesting.

Makes sense.

I cannot really say how much of this applies to your device,

but the two reasons changes were needed on the HDX for

booting the 4.x.y series of kernels with the older vulnerable

bootloader(s) [e.g. 3.2.3.2] are as follows:

the version of the device tree changed, the old bootloader

choked and wouldn't boot the newer (unmodified) kernels,

the video settings -apparently configured by aboot/lk-

don't work for the newer kernels (at least, not the way the

old bootloader goes about it), hence the right parameters

had to be passed in explicitly on the kernel command-line.

The kernels would boot and 'adb' access worked fine, but

the display wouldn't change after the gray Kindle logo..

You may not need any of this on the HD7, and then it's quite

possible that the original boot.img will just boot as expected.

BTW, you can pass the path to a boot.img explicitly on the

command-line to upHDX, and then it will just use that image

unchanged (i.e. without trying to fix the above issues and

re-signing), when generating your new TWRP-zip...
[Kindle Fire HDX 7" & 8.9" Android Development] bibikalka:
OK, that's good to know!!! Thanks! Apparently your bootloader is really old. The holy grail would be to replace the bootloader, but the bricking risk is massive :( Btw, does flashing an old Amazon bootloader to HDX makes it locked at first, or does it stay unlocked?

I finally tried to boot stock 4.5.4 on 4.5.3, and it went fine. However, when I let your pyboot modify boot.img a bit, and re-sign, that did not boot:

http://xdaforums.com/fire-hd/general/success-custom-kernel-4-5-3-t3134006

Without the ability to boot fully custom kernels, things are slightly less fun. I wonder how close to stock Android the kernels from Amazon are, and if one could re-cycle them with the new set of system files ...
[Kindle Fire HDX 7" & 8.9" Android Development] draxie:
Indeed.. but the vulnerability has been fixed in the newer ones;

in fact, I'm puzzled that the HD7 still has an LK implementation

with this mistake unpatched.

Right. I considered this myself, but without an obvious way to recover

from mistakes, I'm not too keen on pursuing this for now..

Unsure, as I've never tried; but I think I saw a post from [MENTION=438903]dpeddi[/MENTION] (somewhere),

which stated that you'd need to unlock again (i.e. it won't stay unlocked).

How about trying to **only** re-sign (i.e. without making the modifications you probably

don't need)? You could even try with a fully custom image, but testing with stock first

might make more sense.

BTW, since I haven't read all the HD7 info, I'm a bit confused. What does this bootloader unlock

get you? On the HDX, with the bootloader unlock, you can boot _any_ boot.img (or recovery);

and, without the unlock, you can only boot signed images, BUT: fake signatures also work,

provided your bootloader is old enough to be vulnerable. What's the status on the HD7?

My current (very limited) understanding is that without an unlocked bootloader, you cannot

boot anything unnsigned (neither boot, nor recovery[?]); and, with an unlocked bootloader,

you can boot unsigned recovery, but not unsigned boot.img. Do we know if _fake_ signatures

help in either case?

You should be able to get sources for your kernel from Amazon and check.

Based on the (apparent) amount of effort that's been going into CM11/CM12

on the HDX, I'd say the changes are likely non-trivial.
[Kindle Fire HDX 7" & 8.9" Android Development] bibikalka:
Those could be different Amazon teams, so little communication. They could have fixed it partially, leaving unlock.img operational, but not the fake signing bug.

OK, this makes sense. *jmz* in the Fire HD forum ended up with a non-working boot.img in boot, and an older bootloader that he flashed into UBOOT. This older bootloader came in locked, so it cannot boot unsigned TWRP, and cannot boot unsigned boot.img. Not sure how he can get into fastboot from this situation, in order to try to unlock the old bootloader. Which is not that old, just 4.5.1 at most.

Actually, last time the script did not change anything, just re-signed it (regex's did not match). Now I commented out the f.write lines before the signing, and the hash for the output image was identical to the previous unbootable kernel. So this signing method does not seem to work.

It seems that your understanding is mostly correct. Fire HD with 4.5.3 will accept unlock.img, and then can boot unsigned recovery partition, but not the unsigned boot partition. On the other hand, a fake signature does not seem to help, since boot.img does not boot when it's re-signed via your script.

I've peeked at the source code. It looks like Amazon had withheld the source code for the bootloader (LK), as well as for TEE1. So no easy way to understand what they changed. The kernel source looks messy, so it would need major motivation to create a custom ROM that is relying on Amazon's kernel.

I guess at most one could pull various pieces from the Fire OS ROMs, and carefully combine them into a new image.
[Kindle Fire HDX 7" & 8.9" Android Development] Reckerr:
You guys can laugh. I still haven't unlocked it. I downloaded Python version stated to work and the Android SDK tools. ..proceeding now...I really don't know what I'm to do...

Reading some more..

http://xdaforums.com/showpost.php?p=60186871&postcount=82

I was being ignorant. This guide is amazing. Follow it to a T. I'm unlocked. One thing which I was doing wrong I had the tab is fastboot mode from the start which wasnt correct. I left it at the TWRP screen and only went to fastboot when it told me to in the guide.
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Congrats! And no, I am not going to laugh. Bootloader unlocking is tricky business on HDX devices. Many people have contributed bits & pieces of information plus code. [MENTION=2476258]travanx[/MENTION] did a nice job summarizing his unlock experience which has been a help to others and you! Be sure to give him a 'thanks'.
[Kindle Fire HDX 7" & 8.9" Android Development] johim:
Im having issues using the upHDX tool for the latest apollo 4.5.4 image

$ ./upHDX update-kindle-14.4.5.4_user_454006020.bin extracting archive '/cygdrive/c/Users/Anatoli/Downloads/hdx_tools/update-kindle-14.4.5.4_user_454006020.bin'

replace system/media/audio/ringtones/Andromeda.ogg? [y]es, [n]o, [A]ll, [N]one, [r]ename: A

C:\Python27\python.exe: can't open file '/cygdrive/c/Users/Anatoli/Downloads/hdx_tools/cuboot.py': [Errno 2] No such file or directory

upHDX: exiting prematurely.

$ ls

cuberHDX.py examples.bat split.py

cuber.py cublock.py examples.sh unlock.img

cuber.pyc cuboot.py py.bat upHDX

$ python cuboot.py

Usage: cuboot.py [bits|boot.img]
[Kindle Fire HDX 7" & 8.9" Android Development] draxie:
Mismatched assumptions..

Hmm... it looks to me as if you were trying to use your "normal" python from within Cygwin,

which seems to fail, as it doesn't know how to deal with Cygwin paths...

There's different ways going about fixing this.

Follow my original suggestion for Cygwin users and use Cygwin's own python package.

Take the 'boot.img' from the archive and manually run 'python cuboot.py boot.img' (assuming that works);

then, pass in the name of the "fixed-up" 'boot.img' on the upHDX command-line. Then, upHDX will just use

your "fixed-up" 'boot.img' instead of trying to invoke python with 'cuboot.py' on the original 'boot.img'

it finds in the archive.

Let me know how it went (especially, if you're still having problems). ;)

BTW: 4.5.5 is out now...

The updater-script and all firmware except appsboot are identical to those in 4.5.4;

so, this should be safe. I'm just about to rehash the archive and take it for a test...
[Kindle Fire HDX 7" & 8.9" Android Development] johim:
yeah, i thought that its messing with my original python, even though i've installed python from within Cygwin.

Any chance you could upload the 4.5.5 image for Apollo somewhere (the tested one). I have unlocked bootloader and i want to flash 4.5.5 to test it on my Apollo. I assume its safe to flash and then I can flash CM or Nexus again?
[Kindle Fire HDX 7" & 8.9" Android Development] draxie:
I'm not entirely sure how to interpret the above.

From the path 'C:\Python27', it would seem that you're using standard "Windows python"

and NOT the python package from Cygwin (which you select and install using Cygwin's setup).

Of course, you may have both installed, but then your "PATH" must be configured to find the

Windows version before the Cygwin version...

Stackoverflow has a fairly detailed answer for a very similar problem here.

A very slim chance (as I'm not in the business of re-distributing hacked images): if you're willing to host it. :p

So do I, although I haven't flashed the other ROM:s; so, I cannot say for sure.
[Kindle Fire HDX 7" & 8.9" Android Development] johim:
creating archive '/tmp/update-kindle-14.4.5.4_user_454006020-upHDX.zip'

upHDX: success.

yey! :)

But as long as it doesnt flash recovery and bootloader it should be fine, right?
[Kindle Fire HDX 7" & 8.9" Android Development] draxie:
I'm glad it worked out in the end.

BTW, the 4.5.5 I flashed earlier today is working fine (so far ;-p).

Yes, it SHOULD be fine... ;)
[Kindle Fire HDX 7" & 8.9" Android Development] draxie:
New unlock tool

I've just posted my multi-platform '1-Click' unlock tool, in case someone out there still hasn't taken the jump...
[Kindle Fire HDX 7" & 8.9" Android Development] mrvogl:
How do i generate a .unlock file with the tools in this thread? It seems everyone in recent months have been using cuberHDX.py which has been removed and linked to this thread, however the information steps use cuberHDX.py and doesn't seem applicable to these tools. I was able to create an unlock.img using python.exe cublock.py 0x000015 0xff264bc1 but I don't know what to do with that, since the unlock guide uses a .unlock file.
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
I am reposting the original cuberHDX in this thread; check back in a few hours.
[Kindle Fire HDX 7" & 8.9" Android Development] draxie:
Oh my... Don't get hung up on the filename. It's the contents that matter.

Just flash that 'unlock.img' the same way you'd flash '0xmmsssssss.unlock'.

fastboot -i 0x1949 flash unlock unlock.img
[Kindle Fire HDX 7" & 8.9" Android Development] draxie:
Why would you do that?!?

There's a good reason I got rid of that. Just count the posts on

that thread where people ask others to generate the unlock code

for them because of all kinds of issues that had been fixed for years.

I'd very much appreciate if you removed you re-post at your earliest convenience?
[Kindle Fire HDX 7" & 8.9" Android Development] mrvogl:
I couldn't find much information using the unlock.img. I had no way of knowing if it was compatible with my bootloader, file structure or anything. I didn't want to brick the tablet. I considered flashing it, but I wanted to get more information first. Everyone in the unlock any thor bootloader thread was using cuberHDX.py/.unlock, which ultimately is what I used as well. My bootloader is now unlocked and cm14.1 is installed. Thanks for the reply though.

---------- Post added at 01:19 PM ---------- Previous post was at 01:10 PM ----------

In his defense your new tools are confusing. There is limited/no current information on how to properly use them for the latest bootloader. The current guide to unlock any thor bootloader point to using cuberHDX, people trying to follow that guide then get redirected to new tools with no information on how to use them or what the results might be. I had no problems following Davey's post with the old tools, I felt more comfortable doing that method then just stumbling my way through the new tools hoping I didn't break something in the process. The overall process to unlock was relatively easy, but it took me hours to find the information to do it, and when I did it pointed to tools that were no longer available.
[P3600 Software Upgrading] srsjason2040:
Hi I have a dopod D810 i would like to know how you get the gps working on this model, can someone please help me

I did upgrade rom to 1.23.707.6 and install a TomTom program but it still looks for gps device

does the D810 have a device built in

has anyone done this Thanks

cheers
[P3600 Software Upgrading] Speedn:
tomtom works on my aussie D810 with the same rom...

I set the GPS reciever to other NMEA GPS reciever.

coldstart it can take a minute or more to find the signal.

try standing outside in a area with a good wide view of the sky, or even driving round.

Speedn
[P3600 Software Upgrading] tdub:
Depending on the version of/locked files (Search forum) TOMTOM, you might need to configure it each time.

In 6.02 and below you need to select the NEMA (or whatever its called).

In 6.03 they have a selection of inbuilt GPS device. I Found 6.03 much less hassle to be honest.
[P3600 Software Upgrading] srsjason2040:
how do i get 6.03 please

how do i get 6.03 please
[P3600 Software Upgrading] brandonmm:
to get tomtom 6.03 update go to the following site and follow their instructions...

http://www.tomtom.com/support/solution.php?GID=3&PID=1401&SID=0&CID=215&Language=1&FID=6736

NOTE: you will need reactivation of your maps after this upgrade to 6.03
[P3600 Software Upgrading] srsjason2040:
please if anyone can help

i have a d810 have installed

rom 1.23.707.6

radio version 1.35.00.11

protocol 32.68.7020.10h

installed tomtom6

selected nmea gps

it asks baud rate

i left it at 4800

it then comes up with

com3:

gps in com9

com7:

ril on com6:

s2410 IRDA

usb Cable:

??????????? i have no idea which to pick i selected com3:

for instance and it says no gps device

i select gps in com9

it says waiting for vaild signal but never finds anything
[P3600 Software Upgrading] saminegm:
Are you outside with clear view to the sky? Wait 15 Minutes there! It WILL work.
[P3600 Software Upgrading] brandonmm:
You're on the right track with GPS on COM9 if you are not using version 6.03. If you get as far as "No valid GPS signal" message then that means your GPS receiver is tracking satellites ok and you're just not getting a GPS fix. I had the exact same problem as you.

1) Just restart your d810 (stylus into the small hole on the underside of your dopod :D)

2) Start your TomTom and use the same setup as you did before with NMEA.

3) Select GPS on COM9

4) When you get the "No valid GPS signal" message stand outside where there is lots of open sky (if you're in the city... tough luck it would be really hard to get a GPS fix there).

5) Be prepared to wait for up to 15 minutes until you get a GPS fix. Mine took more than 10 minutes.
[P3600 Software Upgrading] srsjason2040:
Got it working plus more

Thanks guys you have been a great help

i updated my tomtom software it was easy

as advised i went to here

http://www.tomtom.com/plus/service.php?ID=17

installed home software

then went to this site and followed its instructions

http://www.tomtom.com/support/index.php?FID=6736&Lid=1

and installed tomtom home plus on my computer

tomtom home is excellent for anyone that does not have it, its free and a must have.

tomtom home then updated all my software and gave me free some cool new stuff.

after this did as you said went outside three minutes it was up

thanks i hope this helps others

now if i can only try to see if i can modify my 838 to do this aswell

i know the 838's don't have gps connected inside unit but has anyone opened one up and connected it.

I currently have 4 brand new dopod 810s and 4 dopod 838's i will have to sell some as we just got given them and some people oready had them before we got given them.
[P3600 Software Upgrading] brandonmm:
they were given to you? wow! give them away too. throw one my way :D
[P3600 Software Upgrading] viperx:
Changing GPS

Can you change the GPS type once you have already installed it and it is running?
[P3600 Software Upgrading] viperx:
Are any of you guys with optus? I really want to wait for the official GPS rom from dopod but i dunno what these guys are doing, there has been all these claims of new roms coming out but no substance.

Which rom updates are you using? Any problems with the aussie networks?
[P3600 Software Upgrading] Speedn:
Viperx,

Im using this rom. its the offical rom, but it hasnt been released on the dopod asia site for autralian customers as yet. I think I downloaded it from this forum ftp, cant recall now. works great with 3 so far, haven found any bugs. The only thing I fixed since the update was the bass (again that was found on this forum).

RUU_Trinity_DOPODASIA_WWE_1.23.707.6_6275_1.35.00.11_108_Ship.exe

SpeedN
[P3600 Software Upgrading] TeamSpeedy:
i'm with optus

and i'm using the

RUU_Trinity_DOPODASIA_WWE_1.23.707.6_6275_1.35.00. 11_108_Ship.exe

ROM and it has been working fine
[P3600 Software Upgrading] brandonmm:
Where did you find the fix for the bass?
[P3600 Software Upgrading] brandonmm:
FOUND IT!!!
[P3600 Software Upgrading] Speedn:
bass fix

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

keywords: bass fix trinity

enjoy

Speedn

lol too slow
[P3600 Software Upgrading] viperx:
Yep i downloaded this already. i heard from some people that utms has really bad reception with this rom? also this is wm5 isn't it.

Also is this a straight install or does it need sspl/hard spl or things i don't understand? :D
[P3600 Software Upgrading] gavinlam:
hi everyone here, i got D810 with 3G, i just wondering any1 had it work with 3G, can some1 tell me how to update to a GPS ROMs, coz i hv not idea how to flash the device,

i had been reading alot of the posts but still dunno wat to do, wat is SSPL and how to backup the ROM, can i flash bak to orignal one if it doesnt work. sorry to ask so many question at once, some1 plz help.
[P3600 Software Upgrading] maulikk2000:
Hi

Hi,

I set GPs Program port COM9, hardware port COM 0.

I selected other NMEA GPS receiver and other bluetooth GPS receiver and selected GPS Device on COM9, but it says NO GPS device. What should I do. I'm really frustrated. any help will be appreciated.

cheers

Maulik.
[Nexus 4 Q&A, Help & Troubleshooting] brettzz:
having problems flashing a lollipop ROM. Ive never had any problems like these in the past, all other upgrades have gone smoothly

I am running into two problems. Either I will get stuck staring at a boot animation which never goes away, or I actually get through and all Google services go crazy and force close, with the google first time setup repeatedly trying to start and force closing itself so it is impossible to do anything on the phone.

The best I have done so far is flash a ROM without Gapps, but then for some reason I was not able to download any apks so there was no way to get the Play store on the phone.

If anyone could help me I'd appreciate it
[Nexus 4 Q&A, Help & Troubleshooting] ksavai:
I was under exact same position. downloaded 2-3 lollipop rom, different size of gapps from diff sites same place.

solution is to flash factory image and everything works. now I am waiting for 5.1 OTA update and later try again few roms.

So best flash factory image as of now.
[Nexus 4 Q&A, Help & Troubleshooting] brettzz:
just as an update I tried a different kitkat rom and it went smoothly

not sure why lollipop is not working, one difference is when I reboot from recovery after flashing lollipop it tells me root may have been lost, and I get an option for 'yes, fix root' and it reboots.. when flashing kitkat didnt see that message it just rebooted
[Nexus 4 Q&A, Help & Troubleshooting] jd1639:
What recovery and version are you using. You may have to update your recovery.
[Nexus 4 Q&A, Help & Troubleshooting] brettzz:
hm looks like I was on a slightly outdated one I have updated and will see if this works now
[Nexus 4 Q&A, Help & Troubleshooting] brettzz:
aha that did it

thank you very much!
[G2 Q&A, Help & Troubleshooting] atifsh:
i want to flash stock recovery on custom ROM, cloudy stock to be exact.

i pulled the stock recovery of D800 latest ROM, than flashed cloudy, but after i flash stock recovery, doing a wipe either from power button or from phone menu [backup/reset] it stuck at lg logo or white reset screen when you do recovery from power button.

though the wipe finishes, but phone doesn't get rebooted as normally it should.

[for people who are wondering why]

i want my phone to wipe everything when i do hard reset either manually or remote,

or if you know a way for twrp to do that let me know.

thanks
[G2 Q&A, Help & Troubleshooting] L0nelyE4rth:
meaning your wanna wipe your internal storage ?
[G2 Q&A, Help & Troubleshooting] atifsh:
I think i was pretty clear, yes i want recovery to wipe everything and boot as it usually does.
[Verizon LG G3] artrex654:
Update: It works fine now. All I had to do was start over after flashing back to the original stock ROM. Then I UPDATED twrp... Duh... Well yeah

Alright so here we go...

I've debated rooting my lg g3 VS985 for a while and finally decided to do it.... Although many problems insued. I'll start from the top just incase any prior steps lead to my current issue.

As you probably all know the Lg G3 Had an update that patched roots so I flashed it back using an XDA form to 10B. I then rooted using stump root which all went well. Then I used TWRP to go to recovery with the illusion ROM and a Gapps saved to my SDcard. Problem is they didn't show up... (Unable to mount sdcard unknown error 150) But we finally got it to work through ADP sideload. We didn't clear cache or factory reset though. After reboot and install it kept saying unfortunately YouTube has stopped so i did a factory reset from the settings menue. We then got it into recovery (though twrp was gone) and ADP Gapps but it failed with status 7. I tried installing twrp app from the web but it just crashes immediately after being opened and as stated before my sdcard wont mount in recovery due to unknown error 150. I've looked all over but found nothing. All help is appreciated.
[Verizon LG G3] Heisenberg:
Hi :)

Thanks for writing to us at XDA Assist. In order to direct you properly I need to know which variant of the G3 you have please. Is it a carrier (Sprint, at&t, etc) version or the unbranded version?

Transmitted via Bacon
[Verizon LG G3] artrex654:
The VS985 or the Verizon variant
[Verizon LG G3] Heisenberg:
Thanks for the extra information. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.

For future reference you can find your specific device forum here (bookmark/subscribe this):

Verizon LG G3

Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):

Verizon G3 Q&A, Help & Troubleshooting

Good luck!

Transmitted via Bacon