yashsingh1/xdaforums huggingface dataset:
[8125, K-JAM, P4300, MDA Vario Software Upgrading] joihan777:
Is it possible that somehow it got re-locked????

Also, evrytime I try to upgrade out of 1.05 ROM the RUU process stops at 85% and then says nk.nbf not for this PDA.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] starkwong:
No, except you didn't have a successful CID-unlock (e.g. Unlock when IPL and SPL is 2.xx, and flashed to WM6 using ShellTool, then you think that you have been unlocked, which is actually not)
[8125, K-JAM, P4300, MDA Vario Software Upgrading] joihan777:
Update: Even though I haven't been able to load the official Cingular ROM or

the T-Mobile 2.26 ROM, I HAVE been successful in loading NBD 8.0.

I DON'T GET IT!!!!! Why would NBD load but official carrier ROMs get stuck at 85%?

Although my G3 is is currently working again, I'll still do some more experimenting.

I don't know what an extended ROM is, but I wonder if mine was corrupted

during the power failure when attempting to downgrade last week from NBD to Cingular?

I'll post my results hoping this will help others.

Edit: An hour later- I tried another official WM5 ROM form HTC, no dice. Froze @ 85%

just like the other WM5 Official ROMs. On a hunch, I tried to install the newest NBD 9.2.

IT WORKED! WHY can I install NBD ROMS but not Official WM5 ROMs?

Now the first splash screen is the *dated* green stepped graduated green from 1.05. The current info:

IPL- 2.25

SPL- 2.25

GSM- 02.25.11

OS- 6.0.0.0

Itai! This is tough!

EDIT: OK, it's now 4am and I'm seeing double....

Tried Wizard Service Tool, a very efficient program by mestrini.

Apparantly, my extended ROM was hidden. So the WST unhid it. Now we'll see what this does.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] joihan777:
According to WST, there was no pagepool found in WM6 or WM5 location.

Could this be why WM5 updates didn't work?

4:22am, even cat gave up on me...
[8125, K-JAM, P4300, MDA Vario Software Upgrading] mfrazzz:
Sorry if I missed something here, but if you have a CID Unlocked phone and you downgrade back to a 1.xx IPL/SPL, then you will be CID Locked again when you upgrade. Anytime you downgrade to 1.xx you have to redo the CID Unlock process while you are down there before going back to IPL/SPL 2.xx or higher.

So redo going back to the Button rom, do the lokiwiz unlock, make sure both IPL/SPL are 1.xx (so you may have to flash button a couple of times) then upgrade to Cingular, T-Mo or whatever official 2.xx rom.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] starkwong:
Page Pool is set in ROM image, not hard-coded in hardware.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] joihan777:
Didn't work. I'm certain I'm unlocked, both by lokiwiz program saying so and

Wizard Service Tool saying so. After the unlock I was successfully able to

load NBD 8.0 & NBD 9.2 ROMs, but not the official T-Mo/Cingular WM5 ROMs.

WST found the pagepool completely missing in both WM5 & WM6 sectors.

The extended ROM was also hidden. Both of those items have been corrected

so later today I'll redo the entire process just to make sure all is well.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] joihan777:
Thanks. More clues to this puzzle!
[8125, K-JAM, P4300, MDA Vario Software Upgrading] goofeyass:
Try flashing the empty extented rom. Most new roms don't have extended roms, so if your extended rom is corrupt it may be keeping wm5 to load. Which explains why NBD roms work.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] joihan777:
Thanks, I just now tried this approach. I used mestrini's Wizard Service Tool to 'format' the extended rom. As of this moment I've just downgraded to Button 1.05 ROM and going to use lokiwiz's unlocker.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] goofeyass:
There is a rom out that will flash an empty extended rom without changing anything else.

http://xdaforums.com/attachment.php?attachmentid=42076&d=1182515673
[8125, K-JAM, P4300, MDA Vario Software Upgrading] joihan777:
I have formatted the extended rom.

Then I tried to redo the Button-->Unlock-->T-Mo 2.26.

Still process stops at 85% when installing T-Mo ROM!!!

Also, the splash screen doesn't seem to be working?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] goofeyass:
How long are you waiting when its at 85%. I've had them stay at 85 % for over 5 minutes before.

I would recommend flashing ---->http://xdaforums.com/attachment.php?attachmentid=42076&d=1182515673
[8125, K-JAM, P4300, MDA Vario Software Upgrading] BA_Flash_GOD:
???

in my opinion it is a waste of time to downgrade to flash a new/original rom...i've flashed about 100 or so roms since late 2005, multiple devices, jumping from carrier rom to latest wm5/6 builds..never had an error.

Do what you like of course, im just saying save 10 mins and flash straight to whatever you're wanting to try. goodluck and happy flashing

BTW like I said before... for those of you with dual/quad core procs, try putting the romupdateutility.exe on real-time priority and check it, I flash in roms in less than 3 mins, everytime, no errors
[8125, K-JAM, P4300, MDA Vario Software Upgrading] joihan777:
Is there a correct method for using those files? I installed them to the Wizard's Windows/ Startup directory & rebooted. They sorta ran, but when I checked the extended ROM with WST, it reported the extended ROM was empty =)

Now I'll go around again Button 1.04-->Lokiwiz Unlock-->T-Mo 2.26
[8125, K-JAM, P4300, MDA Vario Software Upgrading] mfrazzz:
Good point... HOW long are you waiting. If you are doing an RUU, you should just let it run. Official roms will "Hang" at 85%, and I've had them hang for over 5mins before also, but they always finish.

As someone used to post, you should start the RUu, then head to the kitchen, go get coffee, a snack, whatever. Just ignore the flashing process until its done...
[8125, K-JAM, P4300, MDA Vario Software Upgrading] dharvey4651:
Very well said. Lol. It's true though. If you just ignore it, it will seem to go faster. I noticed the same thing too. If you are flashing an official rom, it will almost always stop at 85%, sometimes for a long time... Just let it go and it should eventually finish.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] joihan777:
Thanks. I actually have waited, until the RUU says "this nb file is not for your PDA." Funny thing is, the Wizard's screen will still say 85%.

I want to try the SD card method (or look for MTTY), anyone ever see an Cing/T-Mo image floating around this site (I'll also look myself of course)?

This problem "feels" like a ROM chip that hasn't been thoroughly flushed or the chip itself has developed a flaw.

Oy.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] joihan777:
Is it possible the bootloader is corrupted, and if so how to repair it?

Or maybe the memory address for the splash screen is corrupted?

It loads Button 1.05 fine. But the official Cingular ROM 2.25 fails at 85%everytime.

I have thus managed to install NBD 9.2 & XDA6r3 on top of Button 1.05 but

the official Cingular/T-Mo/HTC ROMs don't load!!

I think it has something to do with the splash screen memory area, as

Wizard Service Tool can't read that section of the ROM (hangs @ 66% read)

and everytime I bootup I still get the Button Splash Screen.

I even tried the Splash Page miniROMs, that work for screen 1 & 3, but screen 2 never updates! I'm still stuck with the Button 1.05 splash screen.

All the splash scrrens I have seen are about 192Kb, but WST reports the splash screen should be 153kb. Arrgghhhh!

Unless Button ROM & XDA1 ROM are defective (unlikely).

Hardware problem? Oh gurus please help me out!
[8125, K-JAM, P4300, MDA Vario Software Upgrading] dharvey4651:
Give this a try. Just run it like any other rom. It will change the splash screens. They're pretty plain and you may not like them but if it works and fixes the problem then I'd say it was worth it...
[8125, K-JAM, P4300, MDA Vario Software Upgrading] joihan777:
Only the HTC Logo Screen (1st one) comes up. 2 & 3 remain the stepped, graduated green from Button ROM.

And still when I try to install Cing/T-Mo/HTC WM5 official ROM... always gets stuck @ 85%, then:

"Error 326: Invalid Command" "This NBF file cannot be used for your PDA."....everytime!

BTW, nonetheless thanks for your help & suggestions.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] geckoquiver:
I think that message should only appear even before the actual flash process begins because it should detect it first if that's the right file.

I experienced this problem few days ago. Everytime I would flash Official T-Mobile 2.26 it will hang on 85%. (At least for about 3 times) Then, I just discovered that I just did not wait too long. I also tried to use a different usb cable and it worked (it paused at 85% for about 6-8minutes). The only odd thing in my case is that before I will spend few minutes at 99% but now it will be on 85%. Btw, have you tried re-downloading the Official T-Mobile ROM?

Good luck!
[8125, K-JAM, P4300, MDA Vario Software Upgrading] deviusdragger:
Hey bro thanks for posting this up, it saved my friends semi bricked g4 8125. Thank you. And everyone else for the info they posted
[8125, K-JAM, P4300, MDA Vario Software Upgrading] joihan777:
Thanks anyways,

Well, I gave up on trying to flash/repair the DOC chip. Every install of

WM5 official ROM stops dead @ 85% (On XP-PC & on Wizard) then the RUU

states "This nb...not for your PDA..."

Well WTH, I managed to install the Button ROM 100%, official WM5 ROMs 85%

and then I just install the various WM6 ROMs floating around here 100%,

although the 2nd splash screen NEVER udates. The 1st screen-->nice,

3rd screen--> nice. The 2nd screen? Still that tore-up 1970s Atari-looking

green screen with the red SPL etc.info.

Wizard Service Tool can't read the "Splash Screen" addresses either, it just hangs.

I can't even load another splash screen into that memory range, WST always

reports I need a smaller sized Splash screen than whatever one I choose.

I'm still afraid of my Wizard of crapping out when I least expect it. At least

I can use the phone & all the PDA features. Although theLoon's upcoming

ROM looks pretty 'tasty', I'm trying out NBD 9.2 at the moment and so-far

it works flawlessly. If anyone ever reads this and wants to shoot me an

SD Image of the official Cingular 8125 ROM, please PM me.

Thanks to all you tried to lend a hand, it's still appreciated!
[8125, K-JAM, P4300, MDA Vario Software Upgrading] cgigate:
flash memory chip corrupt. it needs a new chip!

Donate it!
[8125, K-JAM, P4300, MDA Vario Software Upgrading] parlato_edoardo:
same identical issues...

After a year and a hundred reflash in a week, searched and read thousand of posts i have same identical symptoms.

Did any solution come out in this last year? I'd like my wizard have all splashes and to be fully rom customizable...

If some guru read these line please drop a line.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] joihan777:
Well, I never got my second splash screen to work. BUT, I've had no problems using the ROMs floating around here. I'm currently trying out WM6.1 Slim Edition with absolutely no probs. Whenever I reboot I always get the first and third splash screen, but never the second.

Oh well, as long as my phone sees me through college I'm satisfied.

Whenever I get a good paying job I'll probably be looking at the Tilt's successor.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] parlato_edoardo:
So sad to hear about that bro.. I tought in a year maybe some new tool or procedure came out.

I love my wizard and i must say this green gradient would be its scar to be almost bricked.

I'm not sure i will change it because except for Herald, all wizard successors lack of something i consider important and wizard has.

As you see on my signature i got back to TNT 19199 WM6.1, best rom for my purposes...

Anyway I'll keep my 2nd spalsh SOS in my signature as in future someone knows how to solve this issue.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] musclendabx:
SPL Won't Donwgrade

Hey eveyrone. I've been trying to flash my G3 to button but just the IPL downgrades to 1.xx. The SPL stays at 2.xx I have reflashed it several times without any luck. I did manage to upgrade it to 3.08 but that did not help the downgrading process. Every other rom that I tried to install has failed despite multiple attempts. Can anyone help. I thought I did properly CID unlock by following the instructions to the letter. HELP PLEASE
[G4 Q&A, Help & Troubleshooting] dbzgoku:
Sorted it
[Android Q&A, Help & Troubleshooting] Depr2:
Hello

I have Lg P710 II phone rooted. Yesterday I deleted probably settings.apk. I knew that I have to be aware when I'm using rooted Android, but it happend.

I can't enter into settings, I was trying to do factory reset but I'm stuck at the "Unfortunately, settings has stopped". I can't even run my phone in download mode.

I hope you can handle this issue.
[Fire TV Q&A, Help & Troubleshooting] slackbladder:
Hi all,

I've decided to get out another firetv box that i initially purchased over a year ago and wanted to set it up with a bogus amazon account.

So far so good, ... sorted out the account, followed the instructions from aftvnews to pull the lan when required to bypass the initial setup.

email & password and all done.

Now I have just a couple of things i need help with please chaps.....

I know that 51.1.4.0 is not compatible with kodi (in any form).... although I believe that spmc may work on it.

Would it be possible to update a firetv with an original firmware from http://www.aftvnews.com/software/ to the first version that allowed kodi to run.

The reason I ask is that, that first fix by amazon still showed no advertising.

It would be much better if i could root it but as far as I know root is not available for my unit, I tested the serial number over at http://www.aftvnews.com/amazon-fire-tv-serial-number-decoder/

and this is what it said:

Rootable: No

Likely Software Version: 51.1.4.0

Manufactured: By Foxconn on 10/7/2014

Hardware Revision: 03

Unit Revision: 09

Condition (New or Refurbished): New

So seeing as I cannot root is there a way to install somehow just the firmware update that i need without removing my opendns blocks.

What would be my best choice please chaps...
[Fire TV Q&A, Help & Troubleshooting] mezdev:
Kodi worked fine on my fire tv1 without root and works fine after update and the after root.

Why dont you let it update ( it wiill update if connected and not blocked) and root it ?
[Fire TV Q&A, Help & Troubleshooting] Ludacrisvp:
wouldn't it make sense to update it to 5.0.5 and root it with kingroot?

Then it would work with Kodi.

I don't think there would be a way to update it other than to have it communicate with amazon and pull the update from them as you don't currently have root access.
[Fire TV Q&A, Help & Troubleshooting] bula1ca:
Why do you think KODI does not work under 51.1.4?

Kodi works with all s/w versions rooted or un-rooted. BTW if you update to OS5 you will not be able to use DNS within the box. Will need to use set-up DNS through your router as one option.
[Fire TV Q&A, Help & Troubleshooting] slackbladder:
Thanks for the replies chaps.... but i'm sure that kodi/variants will not work on 51.1.4.0_user_514005520,...

You can sideload it but it will never work.

That is the same firmware I had on my first box I got over a year ago,...

http://www.aftvnews.com/xbmc-kodi-incompatible-with-fire-tv-software-version-51-1-40_user_514005520/

http://xdaforums.com/fire-tv/help/xmbc-fc-uk-aftv-t2917248

---------------

Routers out of the question to block updates... that's why I'm using opendns to block updates.

So it's obvious that trying to somehow install an update of my choice is out of the question.... it's either 5.0.5 or nothing. that's fair enough.

But I'm curious about kingroot.... especially as when and if I update then I have the problem of “Self destruct” eFuse added to kernel which gets triggered if an older bootloader is used".

I haven't found anyone yet who couldn't get root due to there particular model of firetv and have used kingroot. Surely kingroot will brick a firetv due to the efuse problem.

(I thought that's where the hardwired method of root came in).

I read that one cannot replace kingroot with supersu as that would also be a major faux par.

Also read that Rbox is working on a "custom recovery" but that still leaves me wondering,.... If the Efuse is triggered then that means one cannot unlock the bootloader... leaving one with a bricked firetv wouldn't it.?

Or does kingroot work in a totally different way to towelroot.

Thanks again for the replies chaps.... the more info I get the clearer it becomes.

One last thing.. I've also notices a lot of talk about firestarter no longer working under 5.0.5... and that adbfire will no longer communicate with a firetv to sideload,... and that ES file explorer is the only way to go.

But then again, maybe that's just chitchat from amazon.... cos you can bet your life they read every single post put on the net.
[Fire TV Q&A, Help & Troubleshooting] bula1ca:
Well somehow I missed that. Sorry to say but you have a lot of misunderstood info here:

- firestarter works with 5.0.5 however some other apps do not i.e. Lama

- ADB works as well

- the process of rooting with kingroot does not brick your unit, removing it by instlling supersu-me does

- Updating to 5.0.5 and rooting using kingroot method will not trigger eFuse.
[Fire TV Q&A, Help & Troubleshooting] slackbladder:
Thanks for the reply bula1ca,

Only just finished reading about the update to firestarter.... But what about the EFuse? I cannot seem to find anything about the Efuse which stopped a lot of users rooting in the first place.

Does anyone know if kingroot has somehow managed to solve the Efuse problem.

Has anyone here used kingroot on what was a previously unrootable firetv box because of the Efuse problem?

thanks chaps

slackbladder..
[Fire TV Q&A, Help & Troubleshooting] bula1ca:
Many including myself.....and no worry recovery will be available as well, from what I know rbox will release it soon. Whatever you decide to do just do not try to remove kingroot with supersu-me.

BTW eFuse did not stop rooting, Amazon updates blocked rooting method available at the time.
[Fire TV Q&A, Help & Troubleshooting] slackbladder:
So I don't need to worry about this info here: http://www.aftvnews.com/amazon-fire-tvs-efuse-explained-rooted-devices-not-at-risk-of-bricking/

Because it seems that its only about boxes that were able to be rooted...

And I was sure that my uk unit was not rootable...

Hence my posting of aftvnews serial decoder information:

Rootable: No

Likely Software Version: 51.1.4.0

Manufactured: By Foxconn on 10/7/2014

Hardware Revision: 03

Unit Revision: 09

Condition (New or Refurbished): New

I'm finding this very confusing....

Strangely enough, I had an upgrade from my service provider.. I stupidly forgot to turn off my working firetv box and it got updated to 51.1.6.3,.... I thought that was OS5,...

If you look on http://www.aftvnews.com/software/ and then look at the second part down it says this:

Fire OS 5.0 Developer Preview – First Version (Which I believe to be Lollypop 5.1)

but when I used firestarter and looked at my settings it says the unit is running 51.1.6.3 and that I'm still on 4.2.2 (Which I do believe is Jellybean).

I really thought that my working unit was on OS5 when it got updated but obviously I was wrong, or the website at aftvnews is wrong.... unlikely.

So if I do update the new box, and it does take the 5.0.5 update... I sideload kingroot (I don't really want to use the PC version of kingroot) and then run it..

Hope that last bit makes sense...
[Fire TV Q&A, Help & Troubleshooting] bula1ca:
You are very confused.

Your box is still on OS3 @ latest s/w revision released (http://www.aftvnews.com/software/). and in this stage it is not rootable yet. You have two options: either let it upgrade to OS5 by itself and root it with kingroot or block updates and wait for rbox to release recovery and a way to upgrade to OS5 manually.
[Fire TV Q&A, Help & Troubleshooting] slackbladder:
Well I removed the opendns block, waited a couple of minutes and checked for updates... nothing happened at first, tried again, still nothing,.. third time lucky, box reads that there is an update available.

First update went to 51.1.6.3 user 516012020,.... it took about 15 minutes to update, then rebooted, took a further 5 minutes.

I then checked again and this time an update to OS 5.0.5 (537174420)... after another reboot it took about another 10 minutes going through "optimizing system storage and applications"... I would think if I had kodi or anything else sideloaded that's where it might have caused a problem, (I'm guessing).

Then had an update come through for the remote.

So now I'm wondering what to do, because it feels like "toss a coin in the air, and hope I'm lucky with kingroot". Can anyone tell me what would be the worst case scenario that could happen when using kingroot.

Thanks for reading chaps..

slackbladder.

---

Sorry bula1ca, I never knew you replied.

I'm just thinking about sideloading kodi now,.... I'm sure I read somewhere that with the new update sideloaded apps appear on the homescreen,... So would I still need firestarter or not.?
[Fire TV Q&A, Help & Troubleshooting] Ludacrisvp:
You don't "need" firestarter with 5.0.5 it shows side loaded apps on the home screen in the apps section.
[Fire TV Q&A, Help & Troubleshooting] slackbladder:
Thanks for that Ludacrisvp...

I was about to use "Install APK" with adbfire,.... To Install isengard 15.2,.... But I remember reading somewhere that one could use the "ADB Shell" and a command to clean up (remove the apk) once it has been run. I may be getting this mixed up with installing to an ipad, as I'm trying to remember something from months ago...
[Fire TV Q&A, Help & Troubleshooting] Ludacrisvp:
Kodi Jarvis 16.0 is the latest stable version that should be what you are using.

You can push the APK to the device then install it using File Explorer, or similar but then you'll have apk files floating about to clean up later.

Best idea would be to use adb to install the APK in a single step, it will transfer the APK and install it and clean up the data too.

ADBFire is handy if you're new to using ADB.
[Fire TV Q&A, Help & Troubleshooting] slackbladder:
Thanks for the advice Ludacrisvp....

hhmmm not to sure about Jarvis yet.. maybe in a month or two. At the moment my Isengard isn't broken so there's no need to fix it.

Anyway I used adbfire and installed the apk for isengard. and ran it to go threw the setup procedure.

I then replaced the box running 5.0.5 with my box running 51.1.6.3 and using adbfire again did a backup. This took about 45 minutes.

A total of 1.24gb.

I then replaced that with the 5.0.5 box and did a restore, this was a painfully long experience... another 45 minutes.

I then ran Isengard under 5.0.5 and all was well, my setup was exactly the same,... Initially I was expecting problems due to the OS upgrade but it was fine,.. only thing missing was my personal wallpaper, so I pushed it to "SDcard", came out of settings on kodi and wallpaper appeared.

Now I don't know if this is my imagination but I tested iplayer and youtube and the video replay quality seemed grainy.... even though i had iplayer on best quality. And I tried a few videos that I've watched previously on youtube so I knew they were HD quality.

I'd like to test this 5.0.5 on a new TV to see if this would make any difference.

also when I rebooted the 5.0.5 box I had a short message appear saying something about reconfiguring installed software.... I've never seen that before and a loud crackle noise as the box was booting.

I'm just wondering about updating my unit that I've been using all the time with the old firmware on it,.... If I did would it be best to reset the unit to factory settings,... I'm just thinking because of kodi and firestarter and llama being on there would they cause a problem to the upgrade.