yashsingh1/xdaforums huggingface dataset:
[8125, K-JAM, P4300, MDA Vario Software Upgrading] jcb:
Many users have been requesting the ROM for the production MDA's. I tried to upload it to the XDA-Developers FTP site but I could not upload it to the T-Mobile ROM directory so if a moderator can download this from the link I provided and move it to the FTP server for long term access.

Specs are as follows:

ROM Version 1.8.10.2 WWE

ROM Date 12/10/05

Radio Version 01.09.10

Protocol Version 4.0.13.20

This does not include the Extended ROM as that is already provided in the link below as this is where this request for the full rom was initiated.

http://d01.megashares.com/?d01=efbcdfc90bfae88ed9ac9ec8fcda5cc6

Scroll to the bottom of the page once you go to the megashares link and you will see the Download Now link.

If you need the Extended ROM follow this link: http://xdaforums.com/viewtopic.php?t=41348
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Genesis3:
Question - you can't just flash back the extended ROM, right?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] jcb:
Yes but it is not the same procedure as backing up or writing a new ROM as you need a utility which I mention below. What you need to do is first "Unlock/Unhide" the hidden Extended ROM partition on your MDA. Once you do this you can see the extended ROM files which are posted in the link above. (There is a utility called Unlock Ext Rom Wizard.cab) on the XDA FTP server. You copy this to your MDA and click on it and it should unlock the parition/folder. After running it I would do a soft reset.

You can then use ActiveSync's Remote File Explorer Utility to move the files around as you will see the new partition when you select change folder.

Basically you copy your original extended ROM files to a safe location for backup and then delete all the files in the extended ROM directory. Copy the Extended ROM files that you downloaded into the Extended ROM directory and once you do a hard reset it will automatically install the new files when it boots up.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Genesis3:
Ah, ok... thanks - I don't see the unlock tool for the Extended ROM though....

Nevermind... found it.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] msafi:
any changes, improvements or modifications worthy of mentioning in this ROM?

thanks,
[8125, K-JAM, P4300, MDA Vario Software Upgrading] bradleydick:
How do you change the boot screen. I only see the ability to restore the radio and OS...
[8125, K-JAM, P4300, MDA Vario Software Upgrading] bradleydick:
Extended rom is read only.. Please tell me that I am not going to have to reflash with an old rom to modify the extrom...
[8125, K-JAM, P4300, MDA Vario Software Upgrading] shdwphnx:
My Extended Rom is writable, but is still hidden. I think it may be due to the fact that I used aWizard 1.3b2 (from http://xdaforums.com/viewtopic.php?t=37386) to remove the CID lock from my phone and change the splash screen. I then also patched my radio to 01.13.10.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] snoslicer8:
Can the original poster explain how to restore the T-Mobile ROM? The utility that is in the folder did the CID unlock on my phone and all that successfully, but when I do option "w" (write OS ROM to device), it doesn't "find" the T-Mo ROM right there in the folder. I don't get it. =(
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Genesis3:
How do you find Radio 1.13.10 over the OEM delivered version? Any significant improvements?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] shdwphnx:
When disabling Flight Mode, the original radio took about 30 to 45 seconds to get a signal. The new radio takes closer to 2 minutes. However, the new radio gets 3 bars of signal in places the old radio only got 1. I consider a reasonable tradeoff, as I don't use Flight Mode very often.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] jthurs:
for updating the os rom and radio rom, it says please type the number, what number do i type?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] jcb:
I had that initial problem myself. I had to copy it to my C:\Flash since it didn't seem to work correctly off my g: drive under a few folders deep. I looked at the .cmd (batch) file at what it does is do a dir /s (directory listing including looking under subfolders) for *.nba files looking for radio or os in the filename. If you do not see a number then it is not finding the .nba files. When it does find them you will see the name of the rom file preceeded by a number. I would do what I did with the directories and if that doesn't work copy the .nba files into the root folder of the .cmd file folder.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] mashi:
i try to restore the rom with this flash.. the version on my phone is

rom : 1.8.10.2 WWE

rom date : 12/10/05

radio version 01.04.10

protocol version: 4.0.13.17

extrom version: 1.8.10.104
[8125, K-JAM, P4300, MDA Vario Software Upgrading] CRACING:
Hello,

Anyone has this rom ( Version : 1.8.10.2 )? If so, is it possible please upload. I'm searching for a wizard ROM which shows MM/DD/YY in device info ( i.e 12/10/05 ).

I request again, if you have please upload coz its urgently needed for me. :o

Best Regards
[8125, K-JAM, P4300, MDA Vario Software Upgrading] -MyHTC-:
This ROM should have what your looking for.

LINK
[8125, K-JAM, P4300, MDA Vario Software Upgrading] CRACING:
Thanks a lot. I was searching for this since from yesterday and there were no working links.

Anyway, thanks again. :)

Best Regards
[8125, K-JAM, P4300, MDA Vario Software Upgrading] -MyHTC-:
No problem. Glad I could help.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] poopassdoucher:
dont mean to intrude, but i needed a production cingular rom for my g4 version 2.25 can anyone help?:confused:
[8125, K-JAM, P4300, MDA Vario Software Upgrading] jcartland:
Wm os 5.1.195, rom 2.26.10.2wwe

TMO has moved things around, but you can find instructions and download links for Microsoft Windows Mobile Version 5.0 OS 5.1.195,

and ROM version 2.26.10.2WWE on their US website at

http://support.t-mobile.com/doc/tm23294.xml?&A2L.SERVICE=UpdateSoftware.
[HTC One Mini] CONdemmedNORmal:
i was updating to 4.3 using this thread http://xdaforums.com/showthread.php?t=2573479 but as i was rushing ive ended up locking my bootloader with twrp and now i cant enter recovery at all or even reunlock my bootloader to try and fix this, is there anyone that can help me with this "/
[HTC One Mini] CONdemmedNORmal:
no worries, i fixed this myself by re requesting an unlock_code.bin, worked like a charm :)
[HTC One Mini] abzboi:
You can just download the stock rooted version. Is way easier and you won't have problems.
[HTC One Mini] CONdemmedNORmal:
But that's the easy lazy way I wanted to do it the way I was doing it to push myself to learn :)
[HTC One Mini] abzboi:
I've tried myself and I ended up saying that I have something modded or something from the ota download. I finish downloading the ota for sense 5.5 and I've tried to lock the hboot and unlocked. Same results no matter what. I think it's the missing apps. The calculator and some others. Just download the stock rooted. You'll end up rooting the phone anyways. What is the point of that?
[Verizon Samsung Galaxy S III] tykalx:
What is the cause? I love these 4.3 roms but i notice at times i have to reset the phone to get my audio (ringtone and notifications) back. It's happened so much that at this point i just keep it on vibrate.

I notice that i flashed liquid 2.7 and have not set dsp, could it be that?
[Verizon Samsung Galaxy S III] tykalx:
anything?
[Verizon Samsung Galaxy S 4] ponzi314:
Hey im having problems with my phone on MJ7 and was wondering if there was a way to format my phone but keep the root?
[Verizon Samsung Galaxy S 4] k1mu:
Flash the no-wipe MJ7 rom from this thread.
[Verizon Samsung Galaxy S 4] ponzi314:
are you sure? Theres comments saying it doesnt keep root.
[Verizon Samsung Galaxy S 4] k1mu:
It doesn't. Once you're done, just re-root.

You can't "format", in other words wipe, a device and keep root without a pre-rooted ROM image. The GS4 bootloader won't allow you to flash such an image, so there's none available.
[Verizon Samsung Galaxy S 4] ponzi314:
Wow im an idiot. I didnt know they had a method or rooting the device again. last time i had to go from mi1 root there then update. Thank you.

Do you recommend just updating to MK2? When I open apps they just crash on me. Thats why I want to do this.
[Verizon Samsung Galaxy S 4] k1mu:
As far as I know, there's no MK2 stock ROM image out there yet.

I'd flash the MJ7 stock no-wipe that I pointed to, then root it. Once that's stable, you can update to MK2 if you want since you can flash back to MJ7 f rom MK2 if you need to.
[Android Apps and Games] moeburn:
Are there any apps that can show me a graph of my phone's CPU clock/frequency over time? I want to see how my governors affect my clock during games and such, what clock the CPU is set to and when. Now I know that apps like SetCPU give you a list of all the possible CPU clock steps and tell you how long the CPU spent in each clock, but that only gives you a vague idea of whether or not your clock settings are ideal.

The ONLY app I have found that comes close to doing this is CoolTool, which can graph ANYTHING over time, including CPU frequency. Unfortunately it's a tiny little 64 pixel graph meant to sit on the notification bar, and it stops graphing during a game, or when you turn the screen off, etc. Are there any alternatives?

This is a Windows version of what I am looking for, OpenHardwareMonitor. It can log your CPU clock over time, if you use CPU stepping like AMD Cool'n'Quiet. I'm looking for something like THIS for Android:
[Android Apps and Games] killoid:
[MENTION=4862334]moeburn[/MENTION] you can refer to this thread,maybe it's that what you want!

link: http://xdaforums.com/showthread.php?t=2302879
[One (M7) Q&A, Help & Troubleshooting] osmorgan:
Hi all. Has anyone had any luck in installing the new dialer with caller id over the "stock" dialer? I mean to have it working with incoming calls?

Thanks
[One (M7) Q&A, Help & Troubleshooting] Spoofy:
No apparently this is possible on some ROMs but I can confirm it does not with any of the CM based ROMs, try TripNdroid as his is built differently.

---------- Post added at 12:53 PM ---------- Previous post was at 12:52 PM ----------

By the way, what ROM are you using and what have your thoughts been so far?
[Thinkpad Tablet General] Kastella:
Hello Everyone ,

I got a Lenovo Ideapad k1 which previously had CWM 10 ( not sure which specific release ) , it was boot looping so i used khanning88's "K1_Stock_120109" in order to format everything and start over from stock , unfortunately i'm getting error on second partition (see picture in attachment for better explanation) . In terms of drivers , i got an unknown device named "Coprocessor" which doesn't accept any drivers to be installed , dont know if this has to do with our problem here or maybe not. APX driver original link from khanning88 is dead so i could be skeptical whether the files i got from googling arent the right ones. Finally i tried to change usb ports but it never made a difference. Thanks in advance and my apologies for writing too long post :angel: .

Regards

Kastella
[Thinkpad Tablet General] mantalamo:
I also am facing the same issue now but being optimistic that I can revive my K1. You will see if your device is being recognized by the PC under USB , thats the last part of the device manager just retract that part then if you see "NVIDIA usb something" you have the driver and the device has been recognized by the PC
[Thinkpad Tablet General] mantalamo:
[MENTION=3989405]Kastella[/MENTION], I already revived my K1 just yesterday. We have the same problem totally the same error result just execpt for SDRAM CHIP, mine got 1 but I read somewhere else that it should be 0, and yours is 0. I also have that STOCK HC.

you're using now and that didn't work for me but instead I got a reimage of STOCK HC and that ROM worked. Let me know if you still,need that reimage STOCK HC :)
[Thinkpad Tablet General] Kastella:
Thanks

[MENTION=5473581]johnwilliam_a_k_a_trash[/MENTION] , Thank you sir , would you please send me the files , i really appreciate the help . Thanks in advance.

Regards

Kastella
[Thinkpad Tablet General] mantalamo:
Here is the stock HC

https://drive.google.com/folderview?id=0BwP7NBy-L-ugdGdrQlA2MTJxYXM&usp=sharing

Here is the reimage stock HC which worked for me

https://drive.google.com/file/d/0BwP7NBy-L-ugN3R1QjJGM05oeVE/edit?usp=sharing

Any problems in downloading let me know soon. Don't forget to hit THANKS BUTTON if you appreciate the help :)
[Thinkpad Tablet General] Kastella:
steps

[MENTION=5473581]johnwilliam_a_k_a_trash[/MENTION] I downloaded the reimage , i tried to open all 3 flash files ; none opened except the old_flash which also failed . I'm not sure how to do it properly , would you kndly tell me the steps that anyone should follow , thanks again and hope to hear from u again:) .

Regards

Kastella
[Thinkpad Tablet General] mantalamo:
Just keep pushing hehehhe seriously that's how I think it is, be persistent. If you think you had for the day do it again tonight or tomorrow just don't give up and be optimistic :) Yes the "flash_old" also worked for me and the "flash" didn't work for me too. I will search some K1 STOCK HC for you.
[Thinkpad Tablet General] Ovecka_m2:
I have the same issue. Going from unsuccessfull JB flash I tried this reimage like 20 times. It went through the partition 2 formating once. But never again. Any tips?
[Thinkpad Tablet General] mantalamo:
Just keep pushing it soon K1 will give up. I already brick mine 6 or 7 times due to upgrading to CM10.1 but I akways ended up bricked. Right now I am on brick state and I am giving up on upgrading to CM10.1.
[Thinkpad Tablet General] Ovecka_m2:
was hederene

Thanks for a cheer-up :). How many tries at its worst did it take for you?
[Thinkpad Tablet General] mantalamo:
S

It depends. There are events w/in 10 attempts the worst is I have never counted. The problem with K1 is there are very very less developersworking, 3 to be exact who I know, to support this device. I also am hoping that someone would make an APX Flashtool like the one used for Acer A500 or attempting to manually flash each partition like the Lenovo TPT and other devices, for the worst case one I have seen in YouTube short circuit a chip. But none of those I mentioned nobody tried or worked on. Which really shows people, specially developers, are not that interested in Lenovo.

BTW, go to CM10.1 for Lenovo K1 thread ti-pich shared his HC rooted + CWM that ROM was created by Khanning just type on google search CM10.1 K1
[Thinkpad Tablet General] Ovecka_m2:
I've already downloaded and tried all the available roms Stock ICS, Stock HC, CM10.1, JB AOSP, .... they all end with the same error. I am now on 50+ tries with the reimage. :(
[Thinkpad Tablet General] Ovecka_m2:
After many more than hundred of tries I've given up all hope. The tablet goes to trash. I've tried three different computers, other USB slots and all the available ROMs with no progress whatsoever. Let's hope others will have better luck.
[Thinkpad Tablet General] Ameisentaetowierer:
Sounds like a HW problem to me.

Instead of flashing a whole Rom, you can verify parts of the sdram by reading/writing them "raw".

There's the option "rawdeviceread" for nvflash which gives you access to every single 4k block of the sdram.

And there's "getpartitiontable" to read the partitiontable to find out, where the partitions are located.

I do not own an original K1, but a slightly modified german variant (P9516). It's so similar to the K1, that l can use the same ROM (kaschemme's) as you. Just the flashing is a bit different (because of the sbk).

My friend YLG80 (www.avi-plus.com) has created a nice image to show, what the partitions on my device look like ( http://www.avi-plus.com/media/kunena/attachments/211/partitions_LT-P9516.png). I think that it is pretty the same on the K1.

You can read this thread ( http://www.avi-plus.com/repair-tips.../nvflash-with-the-medion-lt-p9516-tablet.html) to get more information on this stuff.

But don't just copy/paste the commands from the thread without understanding what you're doing!

For example: for flashing the K1 you will need a sbk, but for flashing the p9516, I need a special "blob"-file.

Maybe you can "rawread" the BCT partition to see, if the blocks are at least readable.

If it works,you can try to write some zeros to the bct, to see, if it is writeable.

If that works, you can maybe write a backup of someones BCT over yours.

If you're living in germany, you can send your bricked device to me ;)
[Thinkpad Tablet General] mantalamo:
Wow! How do you operate nvflash on CMD? I can't get the partitiontable.txt I always get an error. I also mentioned/quoted you on CM 10. 1 for K thanks
[Thinkpad Tablet General] Ovecka_m2:
In fact, there is a blob file for K1 as well. the nvflash version provided in your thread doesn't accept sbk parameter (just like all the new K1 nvflashes) but it works with the K1 blob.

Unfortunately, --getpartitiontable always ends up with "partition table is required".
[Thinkpad Tablet General] Ameisentaetowierer:
Unfortunately I can't see the first command on your screenshot.

It should be something like:

nvflash --getpartitiontable partitiontable.txt --bl flash.bct --go

Not sure, if your bootloaderfile really is named "flash.bct", as I currently haven't downloaded your nvflash toolset.
[Thinkpad Tablet General] Ovecka_m2:
bootloader file is "bootloader.bin". I moved flash.bct, flash.cfg and HC and JB bootloaders to my nvflash folder. First, I have to load the bootloader mode, then and only then can I use the --r parameter, otherwise it will freeze on [resume mode].
[Thinkpad Tablet General] gm2racer:
Looks like I'm in the same predicament as Ovecka_m2 & Kastella. My suspicion is that a bad block has developed on the tablet's internal storage (eMMC?). I've seen references to tools on better supported tablets such as the Acer A500 (search for BabSector.rar) and ASUS TF101. Has anyone considered trying to modify one of these tools to work with the K1? Otherwise, I fear that this tablet is a write-off.
[Thinkpad Tablet General] Ameisentaetowierer:
Hi ovecka,

yes, -r means "resume" which you only have to use for subsequent nvflash commands.

But the getpartitiontable should work on the first flash command.

Please try:

nvflash --getpartitiontable partitiontable.txt --blob blob_new.bin --bl bootloader.bin --go

On my device there's no need for --setbct and other parameters if I just want to read the partitiontable.

I'm even not sure, if you need the "--blob" parameter. I've seen other people using "--sbk 0x0d0a6f49 0x6c577634 0x4d634e55 0x47336d55" on their K1.

But this is -of course- only valid for the nvflash version that supports this parameter.

You may also try to use

nvflash --rawdeviceread S N <filename> --bl <bootloader> --go

Parameters

S - start block for reading (4096k blocks)

N - number of blocks to read

filename - output file

On Linux I was able to backup all the 32GB from the tablet in one big file by using rawdeviceread.

Yves told me, that this wasn't possible on Windows. It just stopped at some point.

Don't know, why. But maybe that's why I don't use Windows :p

Micky
[Thinkpad Tablet General] Ovecka_m2:
Thanks for trying to help us. :)

The --setbct is needed for K1 and if you use it, you are also asked for --configfile. If I remove --blob I get USB write failed.

I am able to read the BCT partition and store it in a file with rawdeviceread 0 1024 but I can neither format it with --format_partition (partition table needed) nor read it with --read 2 p.img. I've even tried the nvflash version that comes with the stock HC and accepts --sbk. It ends up with the same error. Also, the format_partition parameter doesn't work for any partition.

EDIT: Now, this is quite interesting. I tried to rawdevicewrite the BCT partition back immediately after exporting it and got stuck on 65534/4194304 bytes sent.
[Thinkpad Tablet General] Ovecka_m2:
Unfortunately, your blob gives me "unrecoverable bootloader errror 0x00000004".

But I have got userdata,boot,system and recovery img files from stock HC rom. I might try to flash them directly. I tried to --download and --rawdevicewrite recovery.img to SOS partition but it ended with "recovery.img too small" error. I am unable to enter either CWM or stock recovery and the tablet boots to APX mode automatically without the 3-button combo.

I'll try to send boot.img and system.img directly tomorrow after the tablet recharges.

Thanks again, your advices are a great help.
[Thinkpad Tablet General] :
[MENTION=5710454]Ovecka_m2[/MENTION], how is it going? Where you able to successfully revived your K1 by manually using and working Nvflash?
[Thinkpad Tablet General] Ovecka_m2:
Nah. I can't get the partitiontable so I am walking blind trying to rawdevicewrite my boot.img according to http://www.android-hilfe.de/root-cu...d-k1/274092-komplettbackup-mit-nvflash-2.html table. No joy so far (boot.img is too small). If I lower the rawwrite size to (boot.img size / 4096) and flash it, it will compelete but the tablet still boots to APX. :(

EDIT: Maybe, the only thing we need is a working raw BCT partition image. Try to ask for it in the DEV section. I am unable to write there.

Though, I still don't understand, why can't we use the --getpartitiontable properly. :(

EDIT: I think the BCT error can't be overrriden and if it is broken, the tablet simply won't boot despite everything we do with other partitions. Can that be correct, Ameisentaetowierer?

---------- Post added at 04:23 PM ---------- Previous post was at 03:51 PM ----------

Also, look at the picture. I can --rawdeviceread the BCT partiton but I can't write it back. That sounds like a HW problem to me. Maybe it's time to try the oven baking trick? :)
[Thinkpad Tablet General] Ovecka_m2:
Heureka!!!

In the end IT WAS a hardware error. The oven solved it and I am now successfully booting HC. I stripped the mainboard and put it in the oven at 200°C for 7 minutes. The BCT partition formatted on first try. It did work for my ye-olde GeForce 8800GTS card and it worked now!!!
[Thinkpad Tablet General] gm2racer:
Ovecka, keep us updated as to whether or not your tablet is able to continue working.
[Thinkpad Tablet General] Ovecka_m2:
Right now, everything is working. The tablet is fully operational on stock HC and I will return it to it's owner. I'll let you know if it breaks. I had to rebake my GeForce every 6 months to get it operational again. Let's see if the BCT partition holds or if it is even needed outside from flashing another ROM.
[Thinkpad Tablet General] :
I have feeling too that it is HW problem. The time I can successfully flash the HC is if the board is warm enough, usually I just let it sit while on nvflash recovery mode. Then it can flash the HC but still a hit and miss success. I remember when my K1 was still running on CM 10. 1.3 the back part of the tablet gets warm or really warm. I thought it was a natural phenomenon but then I realized I never encountered this while on HC and JB AOSP.
[Thinkpad Tablet General] Ameisentaetowierer:
Congratulations.

Never heard of that.

Btw: if the size of boot.img can't be divided by 4096, you have to pad it with zeros.

You can use Linux command "dd" for this.

this message has been checked by project PRISM
[Thinkpad Tablet General] gm2racer:
I tried baking the mainboard to reflow the solder of my K1 but the problem is still there. Does anyone know where I can pickup a working mainboard or possibly a tablet with a broken screen for not too much $$$? Google search came up with this, which is about 4x more than I'm willing to spend to resurrect this tablet.
[Thinkpad Tablet General] Ovecka_m2:
Did you take off the aluminium cover of the CPU before baking?
[Thinkpad Tablet General] gm2racer:
Yes I took all of the covers, tape, and foil off the board before I baked it...
[Thinkpad Tablet General] :
I don't have an oven that is sad. Do you still have the K1? is it ok if u can get/extract the raw BCT partition image you said before from your K1? thank