As I sit here at work my mind start to think. There is a host file on the Nook Color that is used just as the host file on a Windows machine is used. The Nook Color can auto update itself with out knowledge of the user. Why not monitor the ip address the Nook Color downloads the Side Loader update zip file from and block that address in the host file? That is better then renaming the OTACert file and if the site isn't found by the device the device will not try and update its self.
I thought of it now one of you go figure it out....here is what you have to do;
1. Make sure your on 1.0.0 firmware on the B&N Nook
2. Run Monitoring program on your router to see incoming data and what IP's are being utilized.
3. Run WIFI on Nook
4. Look for new data (side loader being downloaded from B&N)
5. Block that IP address in the hosts file
6. Reboot nook and see if it still tries to update its self.
Post back results.
2nd Idea:
I also though of putting a empty Sideload_update.zip in the root of the device and giving it no access rights through adb or root explorer.
Nice though I heard it leads to authentication errors when you the store... which in turn leads to your nook reverting back to 1.0.0.
mtl171 said:
Nice though I heard it leads to authentication errors when you the store... which in turn leads to your nook reverting back to 1.0.0.
Click to expand...
Click to collapse
I thought that was renaming the OTACert file. I also though of putting a empty Sideload_update.zip in the root of the device and giving it no access through adb.
xboxexpert said:
I thought that was renaming the OTACert file. I also though of putting a empty Sideload_update.zip in the root of the device and giving it no access through adb.
Click to expand...
Click to collapse
Aparently you can not chmod anything in /media folder
I renamed the otacert file and have been on 1.0 for several weeks now without any update.
wvcachi said:
I renamed the otacert file and have been on 1.0 for several weeks now without any update.
Click to expand...
Click to collapse
That works good but what if i wanted to stay on 1.0.1 with out updating...
How come some people get the auto update and some don't? I've been on 1.0 since before Christmas and haven't been forced into an update. I've even been sitting in B&N for hours at a time.
xboxexpert said:
That works good but what if i wanted to stay on 1.0.1 with out updating...
Click to expand...
Click to collapse
1.0.1 is the newest update, so there's nothing to update at this point. Unless they changed something, I'm guessing the otacerts method would probably work for future updates as well.
wvcachi said:
1.0.1 is the newest update, so there's nothing to update at this point. Unless they changed something, I'm guessing the otacerts method would probably work for future updates as well.
Click to expand...
Click to collapse
If you rename OTA in 1.0.1 and try and use the BN Shop or what not it will knock you out and reformat your nook. I'm looking to just block the update site via host file.
xboxexpert said:
If you rename OTA in 1.0.1 and try and use the BN Shop or what not it will knock you out and reformat your nook. I'm looking to just block the update site via host file.
Click to expand...
Click to collapse
It looks like that was based on one post that the poster later attributed to something else (read thread http://forum.xda-developers.com/showthread.php?p=10390633#post10390633).
So I see no reason not to disable otacerts on any firmware right now.
Related
I went ahead and uploaded the doctor file for those that the OTA did not work.
this is the full file not the bs web start app hp has on their site. lol
http://www.multiupload.com/762XCTTMUX
Plug in your Touchpad to the PC before starting.
The webOS Doctor tool will guide you through the installation process.
The tool may autorun after you download it. If not, double-click the file in the location where you downloaded it.
Warning Do not disconnect your device from your computer during the recovery process. Disconnecting the device cancels the recovery process and may damage your personal information.
Note If the battery level is low, the recovery process first charges your battery. This can take up to one hour.
Tip If connection options appear on your device's screen when you plug it in, your device is not frozen and it is not in USB Update mode.
When the Reset Complete screen appears, click Done.
Wait a few minutes for your device to reset.
When prompted, enter your existing HP webOS Account email address and username. This restores any information backed up to your webOS Account (such as contacts, calendar events, and tasks) back to your device. It also restores information from any online accounts you synchronize with, such as Google or Microsoft Exchange ActiveSync.
Click to expand...
Click to collapse
note: this will reset your touchpad.
note: you will need to reinstall moboot / CM7/ CWM
once you do that though, your CM7 install will be just as you left it.
file is safe
Thanks Scrizz! You rock!
http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304wifi/webosdoctorp304hstnhwifi.jar
What is this then?
Nburnes said:
http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304wifi/webosdoctorp304hstnhwifi.jar
What is this then?
Click to expand...
Click to collapse
it's the same exact file. I just renamed mine
I pulled mine from the java web start app and renamed it.
and besides when I went to my account and got the doctor the web start app was the only option.
so idk how you got that one.
scrizz said:
it's the same exact file. I just renamed mine
I pulled mine from the java web start app and renamed it.
and besides when I went to my account and got the doctor the web start app was the only option.
so idk how you got that one.
Click to expand...
Click to collapse
Can you post an MD5 of your file? I downloaded both yours and the other one and the checksums don't match, I may have gotten a corrupted download somewhere though.
EDIT: File compare is going crazy, they are almost definitely not the same file. The webOS.tar file seems to be the same in both downloads, so I'm not sure where the actual difference exists.
Slack3r said:
Can you post an MD5 of your file? I downloaded both yours and the other one and the checksums don't match, I may have gotten a corrupted download somewhere though.
EDIT: File compare is going crazy, they are almost definitely not the same file. The webOS.tar file seems to be the same in both downloads, so I'm not sure where the actual difference exists.
Click to expand...
Click to collapse
I pulled mine from the java web start app from HP and renamed it.
It works and I got it before that other link was available.
you probably got a bad download.
I don't post anything without trying it first.
here are the checksums for the file I uploaded
ADLER32: 15c2b488
CRC32: ffd58914
MD2: 5f8ea5cccab823ada7f1ff3577ce60e8
MD4: 31b2e85462b3d44e11db01168010707c
MD5: 94c0b30798f062bcfe03db016e0aabd7
SHA1: 0696959061e1f9dc6a20040f866fd4f8ac80594e
SHA256: 500676bc4042b46d44a5eeb55ad01f92534772291c7aae2e4ea4f2c797ccecb5
SHA384: f534b6bd754981a9960c4610a65a43e11b41509bd05dd7da06efba7a69ad93d33be4a95f5fe4549d7628b0ccdd6ce8b4
SHA512: 84126373b66995294f2167862a8501b1d23fc2e647afc8508cff6c446e9539c7aada41c6a32b4b2aaaaffbe276f8af88f7ed3250158ac46b3f0dda349df4ae9c
RIPEMD128: 8ce6f8995cbee687b20f55ba0d904a8b
RIPEMD160: fddab786ac2cca2485a35a87420c094ef009d120
TIGER128: 296c5f3c2c3cf147ce2830275fdf3a98
TIGER160: 296c5f3c2c3cf147ce2830275fdf3a98b9bdea0e
TIGER192: 296c5f3c2c3cf147ce2830275fdf3a98b9bdea0e6559f28b
GOST: 2fe764762b8c6136387280879fca887c42d11c7b5ecd340106c63a02bf07a53b
Click to expand...
Click to collapse
Been trying to install android on my touchpad, but having an issue with the "boot cyanogenMod" option showing up. I'm wondering if I need to put the touchpad back to 100% stock before doing android? I had a different kernal plus a large amount of patches.
Do you recommend WebOS Doctor prior to doing CyanogenMod....or would I be wasting my time?
No it doesn't have to be stock. Just make sure you have all the necessary drivers installed. And the palm webos sdk.
Sent from my HD2 using XDA App
Thanks. Installed yesterday and now loving the android option on this.
NISMOFO said:
Thanks. Installed yesterday and now loving the android option on this.
Click to expand...
Click to collapse
glad to hear you're up and running.
I'm getting ready to put the Android Alpha V2 on my TP for kicks, and while researching it, I sometimes read about WebOS Doctor... yet after Googling it, I'm STILL not sure just what the heck it is or what you use it for? Thanks!
EDIT: I found a better link explaining it. It's a recovery tool in case you brick your TP. It will wipe and restore. I'm looking for a way to BACK UP everything on my TP... so I don't see why copying everything from the TP Hard Drive to a folder on my computer can hurt? I may not be able to technically restore it, but it'll be there. I also did a WeOS Dr backup too.
Thanks!
Jason
well, got stuck on 62% and now pc is not recognizing the pad.
(mindflash to "it aint broke dont fix it"... well... screen was popping out, so technically...)
looking for solutions.
stuck at 12% for hr and half , should unplug and restart?
From mobileread I found this amazing post:
the Nook Tablet is still bootable from SD. The rep said that while they think only 3% of sales of the NC go to people who want to root it, they are still sales they wouldnt otherwise have. And they aren't interested in removing the ability to root for those who want to do that. I was pleasantly surprised how ok they are with rooting. Plus, he said they have to keep the boot from SD option. When someone brings a messed up device into a B&N store, they can wipe the device clean and restore it to its original condition by booting the system from an SD card (by using the OS on the card to restore the system on the device).
Click to expand...
Click to collapse
OMG the monkey hitting my head XD
Edit - Not yet found the way to bypass bootloader.
Oh man, I'm really starting to like B&N management.
Smart, smart, smart.
Stuff like this is why I still bought B&N books on my rooted nook.
Perhaps wishful thinking on my part, but I thought I could take a bootable CM7 uSD from my NC and put it in the NT. No dice. It just boots up into the Nook OS. The same card works on my NC.
yeah i tested it out myself today with no luck. when i get mine i'm gonna try an install just to see what happens. maybe you need to run the installer on the device you want? i know that doesn't make sense but i'll have mine tomorrow so if it works i'll post back here. but the boot from sd was invaluable when i deleted the boot file on my nc. and i've seen people get sold on the tablet based on how easy the nc was to root and tinker with. but the stock experience is nice enough that i won't NEED to root it right away.
smatticus said:
yeah i tested it out myself today with no luck. when i get mine i'm gonna try an install just to see what happens. maybe you need to run the installer on the device you want? i know that doesn't make sense but i'll have mine tomorrow so if it works i'll post back here. but the boot from sd was invaluable when i deleted the boot file on my nc. and i've seen people get sold on the tablet based on how easy the nc was to root and tinker with. but the stock experience is nice enough that i won't NEED to root it right away.
Click to expand...
Click to collapse
Unfortunately it wouldn't even run the installer. I created a fresh bootable uSD using the image from here:
http://forum.xda-developers.com/showthread.php?t=1000957
Then dumped the latest CM7 NC nightly on it, put it in the NT, and turned it on. The NT just went straight into the Nook OS.
Just to make sure nothing was wrong with it, I put it in my NC. The installer started up, CM7 installed, and after a reboot I was in a fresh install of CM7. Next I took the uSD, put it in the NT, and restarted it. Still didn't work.
lionclaw said:
Unfortunately it wouldn't even run the installer. I created a fresh bootable uSD using the image from here:
http://forum.xda-developers.com/showthread.php?t=1000957
Then dumped the latest CM7 NC nightly on it, put it in the NT, and turned it on. The NT just went straight into the Nook OS.
Just to make sure nothing was wrong with it, I put it in my NC. The installer started up, CM7 installed, and after a reboot I was in a fresh install of CM7. Next I took the uSD, put it in the NT, and restarted it. Still didn't work.
Click to expand...
Click to collapse
This method can't simple directly used with NT, we need edit something like autonooter or supernooter to work with the new hardware.
Btw try the supernooter file please.http://forum.xda-developers.com/showthread.php?t=871940
lionclaw said:
Perhaps wishful thinking on my part, but I thought I could take a bootable CM7 uSD from my NC and put it in the NT. No dice. It just boots up into the Nook OS. The same card works on my NC.
Click to expand...
Click to collapse
smatticus said:
yeah i tested it out myself today with no luck. when i get mine i'm gonna try an install just to see what happens. maybe you need to run the installer on the device you want? i know that doesn't make sense but i'll have mine tomorrow so if it works i'll post back here. but the boot from sd was invaluable when i deleted the boot file on my nc. and i've seen people get sold on the tablet based on how easy the nc was to root and tinker with. but the stock experience is nice enough that i won't NEED to root it right away.
Click to expand...
Click to collapse
This won't work because each version of CM is tailored to work for the specific device in question, based on the hardware that device has. The NC does not have the same hardware as the NT, therefore you can't use the version of CM built for the NC on the NT. CM has drivers built-in in order to communicate with the device in question, and the drivers for communication with the NC cannot be used to communicate with dissimilar hardware on the NT.
We will just have to wait until the CM devs rebuild CM to include the drivers for the NT.
Solidsnake726 said:
Stuff like this is why I still bought B&N books on my rooted nook.
Click to expand...
Click to collapse
+1. They've bought my loyalty. The NT also just shot straight to the top of my Christmas list as a result of this.
I just got ahold of my Nook Tablet today. I can't wait until the developers get going on this. I definitely will still support B & N for allowing this to be done.
Honestly, B&N is way better off letting users hack away at it. It makes it a hot sales item, resulting in free advertising and better company image (good for shareholder confidence). Also, hopefully they learned from Sony on how NOT to provide an "open" system--giving freedom then taking it away.
It appears that it may only boot signed code..
also, I'm not able to open build.prop on the device using a file manager or when I transfer it to my local machine..
Hopefully some devs will pick it up soon and let us know where we stand
I don't have the machine yet, but why doesn't the superoneclick program work for the Nook tablet as well? Has anyone tried?
jamus28 said:
I don't have the machine yet, but why doesn't the superoneclick program work for the Nook tablet as well? Has anyone tried?
Click to expand...
Click to collapse
it don't work.
Don't panic people. Just because a bootable card does not boot up the Tablet does not mean it will not boot from a card. A whole new CWR will need to be created for the tablet.
Even without root right now, most everything is available.
Obviously we are still missing the android market, but almost all other gapps are currently working, home replacements as well.
I know this doesn't work as well as CM, but it is definitely a huge improvement over what we had yesterday morning.
diamond_lover said:
From mobileread I found this amazing post:
OMG the monkey hitting my head XD
Edit - Not yet found the way to bypass bootloader.
Click to expand...
Click to collapse
The problem with your quoted text: There's a difference between "booting from SD" and "booting ANYTHING from SD".
B&N can allow the former in order to permit unbricks at the store (signed B&N images) without allowing the latter (unsigned images).
need to look at the xft/mlo boot file on sdcard
hello. I think that the NT might boot from SD but is not seeing the right MLO file on the card. If I remember from the OMAP 3 boot sequence, the MLO has to be put on the sdcard first. The reason is that the MLO is the very low level boot code that get into the internal SRAM of the chip. TI provided a tool to convert the xft image to an MLO file and added some kind of magic number so that the chip accepted it as valid for execution. You do not want to use the NC MLO on a NT. that might kill the OMAP. The first thing to do is get the OMAP4 XFT source code and covert it to an MLO using the OMAP 4 TOOL and put it on an sdcard on the first sector to see if the NT will take it.
Just my 2 cents
Fifcic said:
hello. I think that the NT might boot from SD but is not seeing the right MLO file on the card. If I remember from the OMAP 3 boot sequence, the MLO has to be put on the sdcard first. The reason is that the MLO is the very low level boot code that get into the internal SRAM of the chip. TI provided a tool to convert the xft image to an MLO file and added some kind of magic number so that the chip accepted it as valid for execution. You do not want to use the NC MLO on a NT. that might kill the OMAP. The first thing to do is get the OMAP4 XFT source code and covert it to an MLO using the OMAP 4 TOOL and put it on an sdcard on the first sector to see if the NT will take it.
Just my 2 cents
Click to expand...
Click to collapse
If this is true, BN needs to follow Amazon and release the source code for NT.
discothan said:
If this is true, BN needs to follow Amazon and release the source code for NT.
Click to expand...
Click to collapse
I thought they did, there is a link in the NT developer forum I believe.
Hey all,
I posted this in wolf's thread as well as the thread here but not have not fixed yet so I thought I would post this problem in it's own thread.
I successfully downgraded my prime using the tool (batch file) to .15 with a US blob for my (what was) US .21 prime. I rooted with the tool and then voodoo OTA and protected root.
The prime sees the OTA to .21 and downloads it. Asks me to install it. When I say OK it boots into the android guy with the spinning wire mesh. The progress bar makes it up to around %25 and the android guy falls on his back and theres a triangle with a "!" in his open stomach. It sits there for 1 maybe 2 minutes and reboots back into .15 saying there was an error and I've been reverted back to .15.
In searching, I found a thread that detailed some steps that might prevent an update from installing. It started out by looking at the log located in /cache/ to find out what the problem is and fix it. However, my /cache/ folder is empty with no sub-folders.
I've been told it may be my build.prop. I don't think I have added or changed anything in it without changing it right back to the way it was. I change the model and manufacturer once to see if I could get a game from google play but changed them back to exactly what they were (including case).
Would anyone care to link me to a trustworthy .15 build.prop (trustworthy so I dont brick my device putting someone's practical joke in as build.prop). If thats the problem that might fix it.
I have a TB backup so if a complete wipe and factory reset is in order I'm up for that but not even sure how to go about that with the TFP. But I hope theres an easier way if anyone knows one. Would love to get back on the update path and also use the GPS dongle that came in yesterday.
PM'ed you.
Sorry, I get so busy being lazy and working at the same times that I get a little jumbled
buxtahuda said:
PM'ed you.
Sorry, I get so busy being lazy and working at the same times that I get a little jumbled
Click to expand...
Click to collapse
Thank you so much bux! First thing I learned is that just because a file explorer program says it can explore root doesn't mean it does a good job. Thanks for pointing me to root explorer app. There actually were folders in my cache folder with log files. Second thing I learned was editing ur build.prop even putting it back exactly the way it was messes with the update check. Thank u for all ur help. I'M NOW .21 ROOTED WOOWOO!!! The build.prop was in fact the culprit. If I could give thanks from this xda app I'd give u 20! (Actually 21!)
Edit-you can give thanks from this!
Sent from my Transformer Prime TF201 using XDA
Shinare said:
Thank you so much bux! First thing I learned is that just because a file explorer program says it can explore root doesn't mean it does a good job. Thanks for pointing me to root explorer app. There actually were folders in my cache folder with log files. Second thing I learned was editing ur build.prop even putting it back exactly the way it was messes with the update check. Thank u for all ur help. I'M NOW .21 ROOTED WOOWOO!!! The build.prop was in fact the culprit. If I could give thanks from this xda app I'd give u 20! (Actually 21!)
Edit-you can give thanks from this!
Sent from my Transformer Prime TF201 using XDA
Click to expand...
Click to collapse
Lol, yes, in the reply menu. Good stuff, glad it's worked out! I may edit this last post with a public link to the unmodified build.prop in my DB account, we'll see
*EDIT:
Just for other's reference if they face similar issues. Also never hurts to have yet another unmodified build.prop somewhere on the web lol
buxtahuda said:
Shinare said:
buxtahuda said:
Kind of forgot about you I know, I'm terrible lol
Install root explorer and again try to look at your /cache/recovery directory. Pretty sure you must have root access to see it, and root explorer will attempt to get just that when you start it the first time.
Let me know if this gets it so you can look at the recovery logs, if not then I hope more people have a look at your thread.
Click to expand...
Click to collapse
There are logs in there! Can u take a look and let me know?
Thank You!
Sent from my Transformer Prime TF201 using XDA
Click to expand...
Click to collapse
Ok, yeah, build.prop is definitely your problem.
Code:
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop", "6d6091deb35156e27166bfc8577483040d62c59f", "800e051d6445d0dfae5c04fcdb66dd1f0ce7a330")
assert failed: apply_patch_check("/system/build.prop", "6d6091deb35156e27166bfc8577483040d62c59f", "800e051d6445d0dfae5c04fcdb66dd1f0ce7a330")
I have a backup of my build.prop from .21, I'll get it to you and we'll see if that won't do the trick. If not, we'll have to take to the forums and hope some others will have a good build.prop or actual explanation for the issue.
http://db.tt/0tDq7Sih
Sent from my Transformer Prime TF201 using XDA Premium HD via my tethered HTC Vision
Click to expand...
Click to collapse
no FOTA
first sorry for my bad english.
i am i the same setuation BUT some kind difrent)
my prime was at the ARM(replace the main bourd) it came back witch US 9.4.2.21(my original was WW 9.4.2.21) no idea why thy do that, i use the moded vipermod to downgrade to 15 witch WW blob, all seems ok
then root+backroot and traying to see if there an FOTA update, NO FOTA update
"there is no update available for your device currently" i tray all the blobs(US,WW,DE,CN,TW) still no FOTA
i dont tray et your build.prop
MrCat226 said:
first sorry for my bad english.
i am i the same setuation BUT some kind difrent)
my prime was at the ARM(replace the main bourd) it came back witch US 9.4.2.21(my original was WW 9.4.2.21) no idea why thy do that, i use the moded vipermod to downgrade to 15 witch WW blob, all seems ok
then root+backroot and traying to see if there an FOTA update, NO FOTA update
"there is no update available for your device currently" i tray all the blobs(US,WW,DE,CN,TW) still no FOTA
i dont tray et your build.prop
Click to expand...
Click to collapse
Have you tried locating your DMClient in your apps and clearing its data/cache? Try that and see if maybe blob'ing between regions didn't just discombobulate it. The build.prop wouldn't help you there I don't think. I hate to say it, but try a factory reset?
hi
Have you tried locating your DMClient in your apps and clearing its data/cache?
Click to expand...
Click to collapse
yes. no efect
but try a factory reset?
Click to expand...
Click to collapse
the same
i iven tried to put the FOTA menuali
dlpkgfile in the terminal:dd if=/sdcard/dlpkgfile of=/dev/block/mmcblk0p4
it copy the file but dont see the update
MrCat226 said:
yes. no efect
the same
i iven tried to put the FOTA menuali
dlpkgfile in the terminal:dd if=/sdcard/dlpkgfile of=/dev/block/mmcblk0p4
it copy the file but dont see the update
Click to expand...
Click to collapse
Hmm. I haven't had a chance to collect all the different dlpkgfile files yet, I'm setting off on that adventure soon so hopefully I may run into your issue while I install all the different blobs.
I really don't know at this point. Have you also tried this route?
hi
now traing)
but 1 thing
Once downloaded, extract the zip. Inside, there's another file file.
Rename this one into EP201_SDUPDATE.zip and put it in the root of a microSD card.
Put the microSD card into the tf201.
Click to expand...
Click to collapse
can i put the FOTA update file(dlpkgfile) in the zip file or some how use the file?
MrCat226 said:
now traing)
but 1 thing
can i put the FOTA update file(dlpkgfile) in the zip file or some how use the file?
Click to expand...
Click to collapse
I'm not sure. I don't think so, if I'm understanding you correctly. Do you mean you'd like to put the dlpkgfile that you have into the ASUS update zip?
Sent from my Transformer Prime TF201 using XDA Premium HD via my tethered HTC Vision
hi
buxtahuda said:
I'm not sure. I don't think so, if I'm understanding you correctly. Do you mean you'd like to put the dlpkgfile that you have into the ASUS update zip?
Click to expand...
Click to collapse
yes.
when the device detect that ther is an update, it download the update as a ZIP? or this is what it download(dlpkgfile)?
MrCat226 said:
yes.
when the device detect that ther is an update, it download the update as a ZIP? or this is what it download(dlpkgfile)?
Click to expand...
Click to collapse
Yes, when your Prime detects an update it downloads dlpkgfile to your /cache/ directory, and upon reboot updates the Prime. So putting a .21 WW dlpkgfile in your cache directory should update you to .21 WW.
The last one I linked to involving the UPDATE.zip has you manually update your Prime from recovery, as a last resort kind of thing and should work.
Sent from my Transformer Prime TF201 using XDA Premium HD via my tethered HTC Vision
hi
i tried this. it dont see the update
after this trick in the cache folder i found 2 new files "last_log" "last_install"
No OTA after motherboard replacement
MrCat226 said:
first sorry for my bad english.
i am i the same setuation BUT some kind difrent)
my prime was at the ARM(replace the main bourd) it came back witch US 9.4.2.21(my original was WW 9.4.2.21) no idea why thy do that, i use the moded vipermod to downgrade to 15 witch WW blob, all seems ok
then root+backroot and traying to see if there an FOTA update, NO FOTA update
"there is no update available for your device currently" i tray all the blobs(US,WW,DE,CN,TW) still no FOTA
i dont tray et your build.prop
Click to expand...
Click to collapse
There is another post having a very similar complaint in:
http://forum.xda-developers.com/showpost.php?p=25890334&postcount=258
I have an extremely similar issue, that is:
Bought a TF201 on March 2012, updated OTA (several times) up to ICS .21
Sent to the local (Israel) lab complaining for WIFI and GPS issues.
Received back with the motherboard replaced.
Changes that were observed:
* MAC addresses (Bluetooth and WIFI) have changed - well... MB has been replaced...
* MAC of the BT does not appear under the about -> status menu
* S/N unknown under the same menu
* SKU is US (.21) instead of the original WW
I cannot say I feel any improvement with the WIFI or the GPS.
(BTW, the GPS dongle arrived a day after and that one makes miracles!
But only on .21! Furthermore, it is rather big [has the length of the TF201] so I guess I will not carry it with me daily)
Tried the wolf downgrade (US .15) - works fine.
Wiped as suggested on his page.
No OTA!
(rooted or unrooted)
Tried WW .15 and US .14 as well.
No OTA.
Waited over 24h (as suggested in some webpages).
Found the ratchet solution for S/N fixing - still no OTA (neither on WW nor US .15) - all wiped as well (long vol-down press while turning on + 2 x vol-up presses while wipe is flashing).
I've been through 3 factory resets in a row (As suggested in some sites) - both on .15 as well as .21
I'm just about to contact the seller and ask for a replacement (but I really don't feel like it).
I hope a solution is found in the next couple of days as I'm afraid I will have to deal with the seller by Sunday otherwise.
hi
Received back with the motherboard replaced.
Changes that were observed:
* MAC addresses (Bluetooth and WIFI) have changed - well... MB has been replaced...
* MAC of the BT does not appear under the about -> status menu
* S/N unknown under the same menu
* SKU is US (.21) instead of the original WW
Click to expand...
Click to collapse
Exactly the same problem!
BUT i put back the S/N(ratchet) witch no efect(
That sucks. Can't believe they're so sloppy they can't even make an annotation in the paperwork what firmware you were already on and give it back how they received it.
I'll keep looking around, but it's likely going to take someone more ingenious than I to come up with a solution since you're getting the SN Unknown issue. Does ASUS not even have properly working NVflash?
I have tried numerous things with the HDX to get it rooted again, SuperOneClick and numerous other one click root applications that failed, of course. The best way to get root, I figured, is to downgrade the OS. I have the .BIN file and, as the Amazon website states (for upgrade, of course) that we must stick it to internal storage, then do the usual upgrade business. However, the downgrade doesn't work. The is a file somewhere on the system that prevents it, and I wonder if we could find it and delete it, using the PC if necessary. Thanks for your cooperation.
ferrouskid said:
I have tried numerous things with the HDX to get it rooted again, SuperOneClick and numerous other one click root applications that failed, of course. The best way to get root, I figured, is to downgrade the OS. I have the .BIN file and, as the Amazon website states (for upgrade, of course) that we must stick it to internal storage, then do the usual upgrade business. However, the downgrade doesn't work. The is a file somewhere on the system that prevents it, and I wonder if we could find it and delete it, using the PC if necessary. Thanks for your cooperation.
Click to expand...
Click to collapse
I'm just curious as to if you never had root or lost root.
zXiC said:
I'm just curious as to if you never had root or lost root.
Click to expand...
Click to collapse
Yes I did have root, I used AOSP ROM, and made it almost pure android. I found a nice tool called "Android Commander" that has the ability to access the system files from the pc. I was attempting to flash the previous version of Mojito OS using the casebook utility but failed, and as far as I figured I might just be able to extract and maybe delete the file the check for automatic updates, and thus do a manual update on the kindle, which literally requires dropping in the .BIN file into internal storage and the lb upgrade it. Then use the old root method, so if you are interested you could help me locate that file
I'm on 13.3.1.0. But if I want to update to 13.3.2.2, do I need to update in order up to 13.3.2.2 or just update with the 13.3.2.2 bin?
I not a 100% sure but I want a correct answer.
Faznx92 said:
I'm on 13.3.1.0. But if I want to update to 13.3.2.2, do I need to update in order up to 13.3.2.2 or just update with the 13.3.2.2 bin?
I not a 100% sure but I want a correct answer.
Click to expand...
Click to collapse
If you put the 13.3.2.2 .bin file in the /storage partition of the kindle you can then swipe down to settings -> device -> software updates and it will be there. Then click update. If you switch on the internet and it will automatically do things for you, and rebooting and all that. I think that should answer your question.
ferrouskid said:
If you put the 13.3.2.2 .bin file in the /storage partition of the kindle you can then swipe down to settings -> device -> software updates and it will be there. Then click update. If you switch on the internet and it will automatically do things for you, and rebooting and all that. I think that should answer your question.
Click to expand...
Click to collapse
I know about manual updating and over the air updating (which I'll never use). I'm looking for a sure answer, is each update bin the full system update or is it upgraded in update steps (ex. On 13.3.1.0 --> 13.3.2.0 --> to upgrade to 13.3.3.0)? I think the bin file holds the full updated system but I'm not quite sure.
Faznx92 said:
I know about manual updating and over the air updating (which I'll never use). I'm looking for a sure answer, is each update bin the full system update or is it upgraded in update steps (ex. On 13.3.1.0 --> 13.3.2.0 --> to upgrade to 13.3.3.0)? I think the bin file holds the full updated system but I'm not quite sure.
Click to expand...
Click to collapse
I have opened one up before with 7zip archive manager, seemed to have absolutely everything, including all the preloaded apps (Silk, Camera & etc.). Based on that I made a little hunch, that the build.prop is the key to the update.I got it modified and put together back into a .bin, the kindle DID recognise it as an update but it failed to validate. Now I think that is because I didn't get it signed, and after some reasearch I found the Dalvik VM signature and and try to sign the "update" with that. If that fails, then I would like to use binwalk -a linux tool that allows people to analyse .bin files. With that I want to get the file signature from the new update- sign the 13.3.1 with that sginature and "update". I will attempt live booting ubuntu or something- and then use binwalk, but I'll try and see how it goes. Im telling you about this because I think that if I were to make a new thread Amazon would patch that sort of stuff.
I hope this might work- cuz if it does no waiting for ninety days, right?
If it works.
Which it might.
Faznx92 said:
I'm on 13.3.1.0. But if I want to update to 13.3.2.2, do I need to update in order up to 13.3.2.2 or just update with the 13.3.2.2 bin?
I not a 100% sure but I want a correct answer.
Click to expand...
Click to collapse
Just update to 13.3.2.2. The only differences between 13.3.2.1 and 13.3.2.2 are mainly with WhisperLink and WhisperPlay to support the release of Amazon's fireTV:
http://forum.xda-developers.com/showpost.php?p=51487613&postcount=12
FYI.