8 failed boots - Nook Color General

I just powered on the nook, and then it immediately told me that a new software update is being installed. This occurred before the rainbow nook logo. Since I already had 1.01, that doesn't make sense. As well, I hadn't had wifi on the last time I was using the nook. I very recently had 1.0 and was rooted, then updated to 1.01 and auto nootered. I had performed both /system and /data wipes. I can't help but think that somehow, the failed boot counter was incrementing each time I powered the nook on. Either that, or something along those lines. If I'm not using the nook, I generally power it off instead of leaving it in standby. Although not a definite, I would say it has been roughly 8 power offs since I had updated to 1.01. I'm tempted to try that out once I restore this back to they way it was.
I noticed a couple of other people in the forums have run into this.

Incriminified said:
I just powered on the nook, and then it immediately told me that a new software update is being installed. This occurred before the rainbow nook logo. Since I already had 1.01, that doesn't make sense. As well, I hadn't had wifi on the last time I was using the nook. I very recently had 1.0 and was rooted, then updated to 1.01 and auto nootered. I had performed both /system and /data wipes. I can't help but think that somehow, the failed boot counter was incrementing each time I powered the nook on. Either that, or something along those lines. If I'm not using the nook, I generally power it off instead of leaving it in standby. Although not a definite, I would say it has been roughly 8 power offs since I had updated to 1.01. I'm tempted to try that out once I restore this back to they way it was.
I noticed a couple of other people in the forums have run into this.
Click to expand...
Click to collapse
Easy way to find out. Power off/on a few time. Plug it into your pc and pull the file:
Code:
adb pull /rom/devconf/BootCnt
Open with notepad and see what the boot count is set to.
Or use a file explorer that can see system files (Root Explorer) and open that file on the NC and check the book count.

HotShotAzn said:
Easy way to find out. Power off/on a few time. Plug it into your pc and pull the file:
Code:
adb pull /rom/devconf/BootCnt
Open with notepad and see what the boot count is set to.
Or use a file explorer that can see system files (Root Explorer) and open that file on the NC and check the book count.
Click to expand...
Click to collapse
Thanks for that. I restored most of everything, powered off a few times, and checked it out with root explorer. It shows the count as 0. Hmmm, I guess it's not that.

Related

How to FORCE stop phone from showing up as USB drives in Recovery, still no root :(

Okay I don't know if this will help anyone, but I figured out how to stop Windows from detecting the phone as two USB drives when the phone goes into Recovery mode, and to make it show up as Android Composite ADB device.
I do NOT have HTC installed, rather, I'm using the USB 3 drivers that come down through the SDK, so I'm not sure how to do this if you are using the HTC Sync drivers intead.
At any rate, start with the phone off and disconnected. Open the Device Manager. Boot with your prefered method into Recovery mode, then connect the phone. It should detect as USB Mass Storage Device under Universal Serial Bus Controllers. Right click on USB Mass Storage Device and click Uninstall and then OK. Once this is done, disconnect the phone (you can leave it running in Recovery).
Open My Computer and navigate to C:\Windows\inf. Copy the files usbstor.inf and usbstor.pnf to your desktop or wherever, it doesn't matter, just make sure you put them somewhere you can get them later. Then delete them from the C:\Windows\inf folder. These are the drivers that Windows automatically uses for USB storage devices.
Ok, now bring Device Manager back to the foreground and plug the phone back in in Recovery. It should show up as Android Phone with an exclamation mark. If Device Wizard pops up cancel out of it. Now right click on the Android Phone and click update driver. Click Browse my computer for driver software. Click Let me pick from a list... Click Android Phone and Next. Click Have Disk. Browse to your SDK folder into the USB Drivers folder and you should see android_winusb.inf, select that then click OK. You should now have a list of three items to select, this part I am not sure if there is a 'right' or a 'wrong' but I go with Android Composite ADB Interface.
Select that or whichever one you think and this is what it will install as. Bingo, now whenever you connect the phone into Recovery or boot into Recovery with it already connect it correctly detects as the Composite ADB Interface or whichever you selected, but does NOT show up as any USB drives.
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
At any rate, to get everything back to normal as far as your computer being able to use USB storage devices just copy those two files back to the inf folder before you connect them and you should be fine.
bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
.
Click to expand...
Click to collapse
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.
Or you could try what I've done 7 times and achieved ADB Shell 7 times...
1. Turn the phone off.
2. Start running Loop.bat
3. Unplug USB cable.
4. Turn device on in Fastboot by holding in the optical joystick and power.
5. Plug USB in.
6. Hit power button once to get to HBOOT.
7. Wait two seconds for it to do it's thing.
8. Pull off the back of the phone.
9. Hit Vol - to Recovery then hit power.
10. Immediately after doing this continuously push the sd card in and out (about every .5 - .75 seconds)
11. ?????
12. Profit
@DigitalDementia--
How is what you said relevant in this thread?
bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
Click to expand...
Click to collapse
drtrmiller said:
@DigitalDementia--
How is what you said relevant in this thread?
Click to expand...
Click to collapse
Pretty positive it had everything to do with that section of the first post, he said he still couldn't achieve root I attempted to help him. Why don't you explain to me exactly what it doesn't have to do with this thread?
rynosaur said:
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.
Click to expand...
Click to collapse
The real bummer here - and I should have known better, really - is that this wipes your phone.
I suppose it should be obvious, but take it from someone who's pretty new to Android phones and just wiped their entire phone after following your steps: Please add a warning to your original post.
It's late, I'm tired and irritated, but I'm sort of bummed to know I went from hero to zero in trying to enter shell (again) during recovery all in an effort to get proper perm. root. Sort of ****ty to know that I just lost everything.
still no root
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App
USB drives are ok in recovery
When I am in recovery with adb and working correctly it still shows the 2 USB drives so this is normal and ok, what you have done is fool yourself into thinking that your phone is in correct mode but it really is not, this is why it still does not work, sorry.
rynosaur said:
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Now that I've scorched the earth, I'm hitting this thing hard with every trick I can think of to get the shell in recovery again.
Thankfully, I at least have my app list on appbrain.
After researching around the different forums, I think this maybe my issue. I will have to make this attempt when I get home.
This is what I posted on a different forum. I am not sure if this is a similar experience you were having:
So, for a little a bit I was having issues with finding and modding the usb.inf file. I got that finally resolved... Now as I go to one of the first parts of the procedure, executing the adb shell command. Well at first it said the 2 lines, about the daemon and whatever the second line was. Anyways, the third line did not say "no device found" it went straight to a shell prompt "$" . The instructions made a point in the instructions for it to say " no device found" .
I went ahead with the rest of the instructions. No Luck. And I did both methods. A co-worker of mine told to run adb devices to see if my phone is recognized. I will also make that attempt tonight.
I wanted to know if any of you had some insight. I made sure I was in the right directory.
I will make another attempt on a different machine tonight.
Thanks. Oh yeah, I do have some UNIX experience if that makes a difference.
I had the same problem, used this method here
addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
Click to expand...
Click to collapse
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!
kentoe said:
I had the same problem, used this method here
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!
Click to expand...
Click to collapse
I rooted in Windows, rather than linux, simply because I like the look of MejDam's procedure better than the linux script posted here on XDA--and his windows procedure is accompanied by his YouTube video
Long story short: I had ADB Composite Device AND the two storage volumes mounted together, as I got shell, and did the other steps in recovery. NB: they were mounted as Generic Storage Volumes, not writeable partitions. The stock recovery on DI does not allow host to mount either partions, although I'd like to see if
Code:
mount /dev/block/mmcblk0p1
worked for the SDcard on the sdcard, cuz then it would be a cinch to mount sdcard/emnc partition into host OS--windows, linux, Atari 2600, etc Worth a try.
Anyhow, my conclusion: a bad driver setup could be a barrier to catching adb shell, but it is certain not the prevailing problem for most, IMHO.
Was wondering if bast525(the creator of the thread) was ever able to adb shell while in recovery, and if so what did you do thanks.
Heh, I wish.... I've tried just about every method posted on these forums, and five different SD cards from Sandisk, PNY, and Kingston. The only thing I haven't tried is rolling back to the pre OTA update, because I don't want to wipe the phone at this point.

Stupid noob questions on NC rooting

My kids received Nook Color readers for Christmas, and like everything, they look to Dad to optimize them.
I was going to try rooting, but a couple of things remain unclear:
- Do I have to 'auto-noot' to root the Noot, or are there other options (other tools, manual rooting, etc.)
- Should I upgrade the software to 1.0.1 prior to rooting or not?
I tried to give auto-noot for 1.0.0 a quick run, but I couldn't get the SD card to boot (and a check revealed that I had two FAT16 partitions, one with the appropriate images and the other with the files needed). I'm assuming it's because the card I have might be too slow (portal recommends Class 6 or greater, and the card I'm using is a cheapo card I got with an earlier phone that I'm not too sure of).
Thoughts? Tips?
I upgraded mine to 1.0.1 first then rooted.
What OS is on your PC?
If Windows, did you use Win32DiskImager to write the image to microSD card?
Take a look at here for different ways of rooting here http://www.nookdevs.com/Portal:NookColor#Rooting
The easiest and the way I rooted is below which I borrowed from http://blogkindle.com/2010/12/read-kindle-books-on-nook-color/
Here’s what you need to do:
1. Before rooting make sure that you’ve registered the device with B&N as it might not work after rooting.
2. Download nooter that corresponds to you Nook version. You can check your Nook version by pressing Nook button, selecting “Settings” >> “Device Info” >> “About your NOOKcolor” >> Software version:
--- for 1.0.0 – GabrialDestruir’s auto nooter 2.12.15 file 15 Dec 2010
--- for 1.0.1 – GabrialDestruir’s auto nooter 2.12.25 file 25 Dec 2010
3. Unpack the file
4. On Windows use Win32DiskImager to write the image to microSD card (please note that all data on the card will be lost). For Linux or Mac, check out NookDevs.com for detailed microSD imaging instructions.
5. Completely power off NOOKcolor by holding the power button until the screen blurs and “Power off NOOKColor” dialog appears. Select “Power Off” and wait for the device to shut down completely.
6. Turn device face down and open the microSD card container in the lower right corner. Push the card in with metal contacts facing down.
7. Connect the device to your computer via USB cable. The device will power up and book from the SD card but the screen will not turn on. This is normal.
8. After about a minute your computer show detect the new device. This means that the rooting is complete. Your Windows computer will complain about missing drivers. This is normal.
9. Disconnect the USB cable and remove the card from the reader.
10. Power cycle it by holding the power button for 20 seconds and then releasing it. The press the power button briefly to power the reader on.
11. As the reader boots you will see a red splash screen.
12. Once the reader boots, you will be prompted for you Gmail account (as usually with Android) and some initial settings. This will only happen once.
13. As you open the extras folder you will see that it now contains Android market icon and some extras (Youtube, Gmail, etc)
14. You can now start the market app and download other apps that you like. You will need to reboot the device for apps to appear on the extras page. The apps themselves can be used right away just as with usual Android apps.
I would look for the thread in the android development section for auto nook 1.01. Update the OS to 1.01, then do the nook-ing process. Its all laid out there in the opening post.
I would definitely root your nooks to get the most out of them.
I'm guessing he meant Auto-Nooter 2.12.25 (1.0.1 Only), which the thread can be found here
I was looking for a manual method because I didn't have my card reader at work yesterday, and I couldn't get the card I wrote in my Incredible to boot Auto-Noot in 1.0.0.
Oddly enough, after deciding to upgrade to 1.0.1 first, when I tried to root the second time it worked just fine. I did the second one after upgrading, also went without a hitch. Think it just makes sense to upgrade first, seeing as they're both exploitable.
giantcrazy said:
I was looking for a manual method because I didn't have my card reader at work yesterday, and I couldn't get the card I wrote in my Incredible to boot Auto-Noot in 1.0.0.
Oddly enough, after deciding to upgrade to 1.0.1 first, when I tried to root the second time it worked just fine. I did the second one after upgrading, also went without a hitch. Think it just makes sense to upgrade first, seeing as they're both exploitable.
Click to expand...
Click to collapse
How can you write an image from your Incredible? You need to use a computer to write the "image" not just the files to the sdcard, to make it bootable.
-CC
clockcycle said:
How can you write an image from your Incredible? You need to use a computer to write the "image" not just the files to the sdcard, to make it bootable.
-CC
Click to expand...
Click to collapse
I spent some time re-inventing the wheel before I realized someone had documented the method on XDA (my fault for being search lazy):
http://forum.xda-developers.com/showthread.php?t=889001
You use the Linux DD command to write the image to the SD card, which renders it with the correct partitions and files needed to complete root. I did it yesterday, and assumed that I had either too slow a card or it didn't work, until I upgraded to 1.0.1 first and it worked at first crack. Just take care to write the card with the correct device name, mmcblk1.
I used GParted on Linux to double-check after doing my fdisk, everything looked kosher to me and it worked flawlessly.
giantcrazy said:
I spent some time re-inventing the wheel before I realized someone had documented the method on XDA (my fault for being search lazy):
http://forum.xda-developers.com/showthread.php?t=889001
You use the Linux DD command to write the image to the SD card, which renders it with the correct partitions and files needed to complete root. I did it yesterday, and assumed that I had either too slow a card or it didn't work, until I upgraded to 1.0.1 first and it worked at first crack. Just take care to write the card with the correct device name, mmcblk1.
I used GParted on Linux to double-check after doing my fdisk, everything looked kosher to me and it worked flawlessly.
Click to expand...
Click to collapse
Ah, totally forgot about that.. Well glad you got it sorted.
-CC

[Q] I really screwed it up, please help me fix it!

I used ManualNooter 4-5-18 and then 4-6-16 and then did the permissions fix that they said to do.
Everything worked fine for about 3 days. I went to turn it on it showed the Nook Color logo and froze. Now it won't do anything.
The only thing I can do is boot from SD with ClockWork Mod but it won't read it correctly, can't mount, can restore zip's etc.
Tried to push the Boot.img which seemed to have worked, but when I try to push the System.img it dies with a protocol error and the Nook powers off.
Please please someone tell me they know how to fix this! I can even give access to the machine it's hooked up to and let you have at it!
shieldsit said:
I used ManualNooter 4-5-18 and then 4-6-16 and then did the permissions fix that they said to do.
Everything worked fine for about 3 days. I went to turn it on it showed the Nook Color logo and froze. Now it won't do anything.
The only thing I can do is boot from SD with ClockWork Mod but it won't read it correctly, can't mount, can restore zip's etc.
Tried to push the Boot.img which seemed to have worked, but when I try to push the System.img it dies with a protocol error and the Nook powers off.
Please please someone tell me they know how to fix this! I can even give access to the machine it's hooked up to and let you have at it!
Click to expand...
Click to collapse
I found that the automatic updates in Market screw up the latest manual nooter. Here's how I fixed the problem.
*IMPORTANT* You have to do this before the Market first updates itself resulting in an endless boot cycle. This procedure will unfortunately also stop automatic updates to the Market. However, it also stops the Nook Color going into the endless boot cycle after the first Market update.
1. Wipe the device (8 failed boots) and clean the memory (press and hold n while booting and keeping the power key depressed).
2. Complete the B&N registration process.
3. Upgrade to the latest B&N firmware (I tried 1.2 manually)
4. Use CMW and manual nooter by following this http://forum.xda-developers.com/showthread.php?t=1054027&page=1 to root your Nook Color.
5. Use the Market to download Terminal Emulator (see https://market.android.com/details?id=jackpal.androidterm&hl=en for details)
6. type
$ su -
# pm disable com.android.vending.updater
Check out
http://forum.oxygen.im/viewtopic.php?id=919 for more on this.
You have to do this before the Market first updates itself resulting in an endless boot cycle. This procedure will unfortunately also stop automatic updates to the Market. However, it also stops the Nook Color going into the endless boot cycle after the first Market update.
I'll go through these and see what happens, but I wouldn't call what's happening to mine a boot loop. Nothing shows on the screen at all unless I boot from SD card.
And thank you for replying and trying to help me. I'm lost without my Nook. If I get it working I'm not risking rooting it again.

[Q] Any changes to the sdcard files will not take

editi guess sdcard is incorrect/confusing for my situation, it's the entire system up to root folders is stuck in a read-only type state.
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected]ost #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
plasticsoldier said:
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected] #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
Click to expand...
Click to collapse
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
plasticsoldier said:
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
Click to expand...
Click to collapse
I would suggest trying to restore down to WebOS 3.0. In that procedure you literally wipe EVERYTHING on the internal partitions in novaterm and start from absolute scratch. Therefore, if it a software issue you could solve the problem. However, if it is a hardware issue, you'd be kinda screwed.
Yeah, none of the methods I've ended up finding about this problem or other bricked problems are working at all.
i checked at work when i bought it, which of course the 11th was the year mark... but I do have android installed so even if i can get any chance of them honouring it so close they'll probably be like "oh you have android, that'll be $$$ for us to do anything. thanks!"
So I guess I now I have a paperweight with some features.
cdzo72 said:
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
There is a thread in the General forum about how to restore and downgrade. Have you tried that thread ? It is usually a great way to try and get that last restore before sending it back to HP.
73 de VE6AY
Sent from my HP Touchpad, running the latest CM9 nightly, from the XDA Premium App
how are you adding and deleting files when in android? which version of android do you have installed? have you tried different rom versions? have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to? it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard? are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android? have you run "fix permissions"? Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
sstar said:
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
Click to expand...
Click to collapse
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
cdzo72 said:
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the answer, this would tend to suggest that the problem is software based corrupted or otherwise. I am trying to find a program that will allow me to read/format the Android partition on my windows computer and will let you know if come up with anything.
Regards
i guess i should change the title slightly.. it's not sdcard, but basically the entire touchpad contents. go to root and delete whatever i want and it doesn't matter. connect it and format with windows and it doesn't actually matter.
haxin said:
how are you adding and deleting files when in android?
Click to expand...
Click to collapse
i've added and deleted just by using mtp. i've also deleted the files on the android side with the video player (vplayer) i've installed es file explorer (which after restart is gone) and deleted with that. i've also gone into webos and installed internalz pro and deleted files that way, which it then seems to work until i of course do anything related to restarting.
some of the files i've put on, i've had it recognize briefly. so for the video file, start it, then it gets really choppy/glitchy playing it. so stop it, go back into the vplayer and it's back to the old stuff
which version of android do you have installed? have you tried different rom versions?
Click to expand...
Click to collapse
android version 4.0.3. nothing else will install. if i add files while in android, when i boot into cwm they are gone. if i mount usb in cwm and add them they stay briefly but when i try to flash them they fail.
have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to?
Click to expand...
Click to collapse
i have not tried adb yet, just not as familiar using it properly, i will give it a try though.
i am using windows 7 on my laptop currently. i do have a pc upstairs that i barely use that has vista, but i don't know how that would make a difference to the touchpad
it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard?
Click to expand...
Click to collapse
yeah as i put above i guess saying sdcard was a bit confusing/misleading (my bad, sorry!), i didn't really know what else to call it at the time or how to explain myself properly at first.
are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android?
Click to expand...
Click to collapse
i can move/delete/modify anything which has absolutely no effect to the device. i've used es file explorer and gone up to root and deleted everything and the system runs fine. says the system is empty with lots of free space (its the 32gb model) but restart or even go into recovery and everything is once again there.
have you run "fix permissions"?
Click to expand...
Click to collapse
i've run it a few times. just acts likes it's working and then says done. i've even gone into the mounts and storage in cwm and formatted sdcard/cache/data/system. does nothing at all in the end of things
Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
Click to expand...
Click to collapse
it was just something to try to get somewhere right. it never gets past 12%. always fails to reboot.
I am currently letting the battery drain and see if it dying and then being charged will do anything. probably not. but who knows. i talked to a "tech" on the chat support (i never mentioned android) who told me that having preware installed in webos causing it to become corrupt and they "don't knowledge of preware installed devices" exact words. no idea what that means haha don't have knowledge, don't acknowledge...
anyhow. i've not quite given up. i just don't really see it turning out any differently from the previous times. i do appreciate all the feedback and help very much though
ok so heres what I would try. First try flashing a new fresh rom. download one that you want to your computer like cm9 nightly or aokp or whatever you feel like. then boot into CWM recovery connect the touchpad to the computer via usb. then connect to the touchpad with adb. I'm not sure how to do this in windows because it's been so long since I've done it on a windows box, I always use linux.
adb has alot of options, you can move files to and from the device, you can uninstall or install app packages, and more. this way you can adb push the rom .zip to the touchpad's sdcard while youre in cwm recovery. this way you dont have to reboot the touchpad and risk having the file disappear, you can just go to 'install zip from sdcard' and then 'choose zip from sdcard' in cwm recovery after you adb push the rom, you should see it in the folder you pushed it to on the sdcard.
If you arent familiar with how to use adb from the command line or the terminal this might not make alot of sense and i dont know how better to explain it than that. Also yes windows 7 vs windows vista does make a difference there are issues with novacom installing properly, that's why you would have problems running acmeuninstaller or acmeinstaller2. if you look around you should find some videos or how to's that can probably explain it better. Hope this helps.
http://www.webos-internals.org/wiki/Novacom_with_Windows_7
http://forums.webosnation.com/webos-internals/295881-webos-doctor-12-issue-fixed-5.html
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
ve6ay said:
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
Click to expand...
Click to collapse
Probably the best suggestion yet given that everything else has been tried.
Good luck.
****EDIT****
Before you attempt the step above I have just noticed a difference between between cwm and. TWRP2.2 which I have installed on my Touchpad via goo manager. If I open recovery via goo manager and then select wipe it gives me 4 options cache, davlik, factory reset AND system which i think says will remove your rom . I don't see the forth option available with the regular cwm/clockwork. Just a thought.
All the best with whatever you try next.
sstar said:
Probably the best suggestion yet given that everything else has been tried.
Good luck.
Click to expand...
Click to collapse
this would work, however you have to fix you novacom/novaterm issues on your windows machine before you'll be able to do any of this. the reason acmeuninstaller, acmeinstaller2 arent working is likely because youre on a windows7 64bit box and Palm-sdk, the novacomd.exe, noverm.exe, and javaruntime apps and drivers arent setup right. just make sure you have the proper javaupdates on your computer then you can install preware in webos, preware has some nice tools that will delete the entire android install partitions, one is called 'remove android' and the other is called 'tailor' you run them from within webos. after you do that then in webos you should do a full device reset. you'll find it in the "info" tab under settings in webos. this will delete and reformat the whole /media ,(aka sdcard) partition. so you will lose all the files you have stored on both webos and android. that format will take a long time probably like 30 min or more. after thats done. reboot the hp and run webosdoctor. now i know for sure this will work because ive done it on mine. remember to put the touchpad in developer mode in webos first to install preware. you can do that by typing webos20090606 into the webos search bar and hitting enter. I'll put links from my box.com accou t to everything you need.
https://www.box.com/s/479acdb6ef9c99fc7b92
https://www.box.com/s/1aed4722990aad251570
edit: also I'm not sure if youre on the 16gig 32gig or 64gig pad, the webosdoctor that i linked is for 32gig wifi only US version. if thats not what you have then youll need to get the doctor for for specific touchpad. or you could create a webosmetadoctor but thats a whole nother project.
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
plasticsoldier said:
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Click to expand...
Click to collapse
ok no one will be able to help you fix this issue unless you give complete details of the problems. when you say " novacom/novaterm stuff doesn't work" we cant really help specific error details is what i need. I dont mind helping you fix this but you have to be a little more specific on exactly what,where, and how youre installing and running and mounting apps and directories.
your problem IS fixable but you need to slow down and really do things exactly step by step.
Ok so back to ./adb. now when you boot in to CWM recovery on he touchpad DONT do anything in CWM just plug it into the computer. do not mount it as a usb storage and dont mount or unmount the sd partition LEAVE IT.
you can then use ./adb from the command line or terminal on the computer to move the files to the touchpad' or install apk's uninstall apk's you name it. This will require that you know some linux terminal commands. for example to move a new rom zip to the internal sd card or into any other folder you can use ./adb push command to run a root shell on the android device itself you can use ./adb shell and then change folder and file properties from readonly to rw. this can all be done while the touchpad is patiently waitng in CWM recovery. this way when youre done installing or uninstalling apps from the device and moving flash zips to it, you can disconnect the .adb connection with ./adb disconnect or just type exit from the terminal till it closes. unplug it then you will be able to pick up the touchpad and install zip from the sdcard, keep in mind you dont want to choose 'apply u[date from sdcard' you want to use the 'install zip from sdcard option' you can read up more on how adb works. it is probally the most important part of hacking android.
with that being said. novaterm is the palm webos version of .adb. this is why when you boot into webos recovery to do things like acmeinstaller and acmeuninstaller2 the novaterm novacom and novacomd apps have to be installed correctly on the computer or else you wont be going anywhere fast. some screenshot examples of how it should appear below.
https://www.box.com/s/432e63a83215f00eea6a
https://www.box.com/s/970bc29542a05f98f036
https://www.box.com/s/63c0f656e8354f7f2d6a
https://www.box.com/s/cbe3266467ae8e3ebabe
https://www.box.com/s/005e56a61a178dd17fa4 some better resolution images.
Plasticsoldier said
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Yes there is
Firstly tailor does exist, it is a beta and the facility to dl must be enabled.
Read this and scroll down to Enabling beta test feeds and follow the instructions , when you get as far as using the Linux command you CAN copy and paste thank God.
http://en.m.webos-internals.org/wiki/Testing_Feeds?wasRedirected=true . After that reboot into Webos and launch preware. Go into managed feeds as per the instructions in the link above and install Tailor. Reboot again and the app will work. It looks very good actually.
But before attempting to actually use Tailor please read the article I have posted below it is only 7 pages long but will explain how to use Taylor properly as it is a powerful tool.
http://forums.webosnation.com/webos...partition-filesystem-editor-beta-testing.html
I have done all of this , this morning so if you have any problems pm me or ask in this thread.
I sincerely hope that this helps, it should be the answer to your problems.
@haxin: sorry, wasn't trying to be unhelpful when everyone is being helpful to me. I shall be more detailed in future responses. I think i was getting frustrated and had had a busy exhausting day so it didn't help me come across clearly/properly.
OK, so I had preware installed already, so I removed it, went into developer mode, used the linux commands, reinstalled preware, added Tailor.
(i've done this a few times, because I didn't remove the cable after doing the linux commands for preware, then i accidentally hit the wrong buttons and it connected to 'usb drive' mode and wouldn't connect on the pc side and got stuck on the "ow disconnected me properly next time" screen).
So it gives me the following options
USB (media)
Android (system)
Android (cache)
Android (data)
Unused Space
the 'usb media' starts mounted and will mount again if unmounted. If I use 'check filesystem' it'll pass. So then I try 'delete partition' which pretends to delete, then it takes me to the unused partition which is still at 16mb. so i try to use "check filesystem' again and it fails. try repair and it fails as well
I've tried mounting the android parts just to see, they just sit there processing that they are trying to mount. trying to delete or anything else fails as well.
and now after trying things, any of the 'cards' will try to open and just sit there grey. and with my usb cable not plugged in it still is giving me the option to enter usb drive mode. and with this i have to restart and go through the steps again of adding Tailor which is getting tedious.
I restarted, went through the motions to get back to Tailor. trying out resizing just to see how that goes. So far 15%. not sure what will happen when done, but we will see.
This is getting long, so i'll end this part and update on anything and also try to familiarize myself with adb a tad more

[Q] Kindle Fire HD 7 2012 rooted with cyanogenmod 11 keeps restarting

Hi, I have two Kindle Fire HD 7 inch, I think both are the older model. Until recently, one was bricked after i rooted but it started getting random restarts after being fine for months. I decided to try flashing a custom ROM, but due to following a YouTube video and not loading the ROM first before flashing, my fault as I mid heard the instructions, it died and I didn't know enough to reliase it could be fixed with a factory cable. I got a replacement and due to a **** up at Amazon, I managed to keep the broken one also.
I decided to root the newer one a few weeks in but months later it started having issues with dolphin browser constantly restarting, so I decided to buy a factory cable as a precusion and flash it to cyanogenmod. Everything went well so i dawned on me that I could fix the first one with my cable. I managed to fix with instructions from here and then flashed as well. Everything seemed to work fine until it started randomly restarting. Then it would get stuck at the blue kindle logo, would still allow me into twrp, so cleared dalvik and everything else and reflashed, it would load as newly flashed, but end up restarting again and eventually getting stuck at the blue logo again. I've seen a few threads with similar problems but couldn't find one that matched the circumstance.
So, my question, it this likely a hardware issue as it did get dropped once or twice in its short working life, or is it a software issue and something I could fix ???
damofitz said:
Hi, I have two Kindle Fire HD 7 inch, I think both are the older model. Until recently, one was bricked after i rooted but it started getting random restarts after being fine for months. I decided to try flashing a custom ROM, but due to following a YouTube video and not loading the ROM first before flashing, my fault as I mid heard the instructions, it died and I didn't know enough to reliase it could be fixed with a factory cable. I got a replacement and due to a **** up at Amazon, I managed to keep the broken one also.
I decided to root the newer one a few weeks in but months later it started having issues with dolphin browser constantly restarting, so I decided to buy a factory cable as a precusion and flash it to cyanogenmod. Everything went well so i dawned on me that I could fix the first one with my cable. I managed to fix with instructions from here and then flashed as well. Everything seemed to work fine until it started randomly restarting. Then it would get stuck at the blue kindle logo, would still allow me into twrp, so cleared dalvik and everything else and reflashed, it would load as newly flashed, but end up restarting again and eventually getting stuck at the blue logo again. I've seen a few threads with similar problems but couldn't find one that matched the circumstance.
So, my question, it this likely a hardware issue as it did get dropped once or twice in its short working life, or is it a software issue and something I could fix ???
Click to expand...
Click to collapse
i can take a few guesses at what would be causing a random reboot, i know dolphin can, i don't know why you would need to reflash to fix it though, thats very unusual unless maybe a filesystem error was causing it but it shouldnt have the same error everytime, i could suggest scanning the system partition for errors from recovery, i'd have to grab the command you'd need to run through adb. you dmesg would tell you if there were filesystem errors probably, mine was telling me about them so i finally got around to fixing them. i will mention i know dolphin can cause it to reboot randomly, i have had it happen before, i think it draws too much power trying to run it and causes the crash, not positive though.
On a side note you may want to rename the thread to 2012 kindle, the 2013 one is not rom-able, only rootable.
Did you overclock the processor?
stunts513 said:
i can take a few guesses at what would be causing a random reboot, i know dolphin can, i don't know why you would need to reflash to fix it though, thats very unusual unless maybe a filesystem error was causing it but it shouldnt have the same error everytime, i could suggest scanning the system partition for errors from recovery, i'd have to grab the command you'd need to run through adb. you dmesg would tell you if there were filesystem errors probably, mine was telling me about them so i finally got around to fixing them. i will mention i know dolphin can cause it to reboot randomly, i have had it happen before, i think it draws too much power trying to run it and causes the crash, not positive though.
On a side note you may want to rename the thread to 2012 kindle, the 2013 one is not rom-able, only rootable.
Click to expand...
Click to collapse
Sorry, your right, its the 2012, I just noticed that the 2013 doesn't have a front camera. As for dolphin, I uninstalled a bunch of times with the same result, but I like it because the flash player works well once set up properly. It always starts off fine then gets progressively more unstable on my working kindle. I don't know much about adb, just the basics but have KindleFireFirstAid and other programs that used the fix permission errors. I haven't got round to trying them get though as the kindle normally wont stay on long enough.
When it was just rooted, the kindle would still restart so I was hoping that flashing might fix it in case it was something I had done wrong.
Oh, and I haven't over clocked, I signed into play store and allowed it to download all my girlfriends crap so she could use it for a while while her galaxy tab goes into the shop as it has the red charging cross issue.
damofitz said:
Sorry, your right, its the 2012, I just noticed that the 2013 doesn't have a front camera. As for dolphin, I uninstalled a bunch of times with the same result, but I like it because the flash player works well once set up properly. It always starts off fine then gets progressively more unstable on my working kindle. I don't know much about adb, just the basics but have KindleFireFirstAid and other programs that used the fix permission errors. I haven't got round to trying them get though as the kindle normally wont stay on long enough.
When it was just rooted, the kindle would still restart so I was hoping that flashing might fix it in case it was something I had done wrong.
Click to expand...
Click to collapse
you mind booting it up into a os and running this from a command prompt?
Code:
adb shell dmesg > log.txt
you will need to have a command prompt cd'd into the directory of adb, so either in a kffa folder or srt folder will do, anything that came with adb really. if you don't know much about command prompt then do this: shift + right click the folder with adb, hit "open command window here", then run that command.
stunts513 said:
you mind booting it up into a os and running this from a command prompt?
Code:
adb shell dmesg > log.txt
you will need to have a command prompt cd'd into the directory of adb, so either in a kffa folder or srt folder will do, anything that came with adb really. if you don't know much about command prompt then do this: shift + right click the folder with adb, hit "open command window here", then run that command.
Click to expand...
Click to collapse
I normally go from the SDK platform tools folder to check the device is coming up, does that work?
damofitz said:
I normally go from the SDK platform tools folder to check the device is coming up, does that work?
Click to expand...
Click to collapse
Ok, i tried and it and it just shows the command line again. Have killed and restarted server but no difference
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>adb devices
List of devices attached
D025A0A024060MRL device
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>adb shell dmesg > log.txt
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>
update: I have noticed that when plugged into my laptop, the Kindle will stay on indefinitely, but when I unplug or not long after, the Kindle then restarts, especially when im doing something like searching the web or opening apps, so could it be a power source problem?
damofitz said:
Ok, i tried and it and it just shows the command line again. Have killed and restarted server but no difference
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>adb devices
List of devices attached
D025A0A024060MRL device
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>adb shell dmesg > log.txt
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>
update: I have noticed that when plugged into my laptop, the Kindle will stay on indefinitely, but when I unplug or not long after, the Kindle then restarts, especially when im doing something like searching the web or opening apps, so could it be a power source problem?
Click to expand...
Click to collapse
i probably should have mentioned that the commadn i asked you to run was outputting the text into a file called log.txt in the same folder you ran the commadn in... plz post it as a attatchment. sorry for my stupidity.
stunts513 said:
i probably should have mentioned that the commadn i asked you to run was outputting the text into a file called log.txt in the same folder you ran the commadn in... plz post it as a attatchment. sorry for my stupidity.
Click to expand...
Click to collapse
No need to apologize. I left the table on all night and its still on this morning. The log is attached
damofitz said:
No need to apologize. I left the table on all night and its still on this morning. The log is attached
Click to expand...
Click to collapse
think the filesystem is ok not seeing any errors...another thing you could do is leave the device plugged into the pc with this running
Code:
adb shell "su -c 'cat /proc/kmsg'"
and whenever it reboots just copy and paste the last lines it outputted.

Categories

Resources