anyone know how reset all ?
it is possible ?
yes it is !
I solved my problem
If your TouchPad blocked on hp logo..
you must download WebOs Doctor for reinit your TP
choose version for you HP here: http://www.webosbuzz.com/webos-info...webos-doctors-touchpad-pre-pixi-veer-etc.html
install webos doctor and follow setup for reinit you TP
power on your TP in developer mode with hold volup and press power
like usb icon appears you can start flash
if your flash stuck at 12%
you must do it
download novaterm here http://www.webos-internals.org/wiki/Accessing_Linux_Using_Novaterm and unzip in folder \palm\sdk\bin
restart webos doctor
when it block at 12% launch "novaterm"
connect at host
tape this command: dosfsck -r /dev/mapper/store-media (as mentioned below there is a space between -r /dev/mapper)
choose option 2
and valid size
when it finish close Webos doctor
and restart Webos doctor and flash again
after setup your TP and reboot go to settings and device information
it is possible missed space disk
in this case you must go settings in webos -> reset all and erase
after this operation go again to settings -> device information and check size
sorry for my bad english
for info:
WebOS Doctor begins
At 3%, a ramdisk is transferred to the phone, and the phone is rebooted
At 4%, the screen changes to the HP logo
At 9%, the screen changes to a big arrow pointing down to an integrated circuit
Novaterm access is available from 12% onwards
The progress bar advances by 2% increments every 20 seconds or so
If it gets stuck at 52% for more than 30 seconds, it's not going to progress further and you will need to try again.
Around 54% the filesystems are being partitioned
Around 64% the modem firmware is being reflashed
Around 72% the carrier apps are being installed
Around 82% the ROM is being verified
If the process fails at 84% or later, the flash and modem have actually been written, so if you reboot you will get what you were flashing.
i move up the solution in fisrt post
Excellent work...yes it works
one small thing....there is a space between -r /dev/mapper
it got me confused so there maybe other people like me
cheers
cynosure4sure said:
Excellent work...yes it works
one small thing....there is a space between -r /dev/mapper
it got me confused so there maybe other people like me
cheers
Click to expand...
Click to collapse
Thanks for your feedback
Sent from my Touchpad using xda premium
ankorez said:
i've installed CM7 alpha 2.1
and i have used acmeunisntaller
but now i've hold on hp logo
don't understand
anyone know how reset all ?
it is possible ?
yes it is !
I solved my problem
If your TouchPad blocked on hp logo..
you must download WebOs Doctor for reinit your TP
choose version for you HP here: http://www.webosbuzz.com/webos-info...webos-doctors-touchpad-pre-pixi-veer-etc.html
install webos doctor and follow setup for reinit you TP
power on your TP in developer mode with hold volup and press power
like usb icon appears you can start flash
if your flash block at 12%
you must do this
download novaterm here http://www.webos-internals.org/wiki/Accessing_Linux_Using_Novatermand and unzip in folder \palm\sdk\bin
restart webos doctor
when it block at 12% launch "novaterm"
connect at host
tape this command: dosfsck -r /dev/mapper/store-media
choose option 2
and valid size
when it finish close Webos doctor
and restart Webos doctor and flash again
after setup your TP and reboot go to settings and device information
it is possible missed space disk
in this case you must go settings in webos -> reset all and erase
after this operation go again to settings -> device information and check size
sorry for my bad english
for info:
WebOS Doctor begins
At 3%, a ramdisk is transferred to the phone, and the phone is rebooted
At 4%, the screen changes to the HP logo
At 9%, the screen changes to a big arrow pointing down to an integrated circuit
Novaterm access is available from 12% onwards
The progress bar advances by 2% increments every 20 seconds or so
If it gets stuck at 52% for more than 30 seconds, it's not going to progress further and you will need to try again.
Around 54% the filesystems are being partitioned
Around 64% the modem firmware is being reflashed
Around 72% the carrier apps are being installed
Around 82% the ROM is being verified
If the process fails at 84% or later, the flash and modem have actually been written, so if you reboot you will get what you were flashing.
Click to expand...
Click to collapse
appreciate it bro! This helped a bunch
Leoisright said:
appreciate it bro! This helped a bunch
Click to expand...
Click to collapse
I am flattered
mayhem69 said:
i did install java, and palm sdk , i talked to a 3rd level HP tech, and he stated this fix is for something else, not my problem. I am sending back, getting a replacement, and selling this piece of ****!
ankorez said:
ok you must install java sdk and palm os sdk
before...
but i think is assumate it...
mayhem69 said:
ankorez said:
mayhem69 said:
Hi, my files musta gotten corrupted. I can get into webos recovery no problem with the bootmod. I try to run Webos Doctor and stuck at 12%.
The link you gave for the novaterm.zip is a dead link, i don't know what to do.
Can you please help me, this is driving me crazy. You can call me if you wish.
My cell is 484-366-****.
After 1:00 eastern time at 484-372-****
Can you PLEASE HELP?
Click to expand...
Click to collapse
yes
but link is ok..
http://www.webos-internals.org/wiki/Accessing_Linux_Using_Novaterm
Click to expand...
Click to collapse
I still can't get this working with your directions, first off i do not have a palm/sdk/bin folder.
I just put the novaterm files in the root of the palm folder.
When i open novaterm, every time i type a letter i get an unhandled exception error and i can continue or close.
after i type in what you say, i am assuming there is no spaces also? your directions aren't very clear.
i get a bunch of letters like, -a, -A, -d path, -f...etc.
Gonna talk to a 3rd level HP tech today, maybe he can help.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
there is a space between -r /dev/mapper
look at my profile and my thread with hp touchpad
http://forum.xda-developers.com/showthread.php?t=1303056
maybe you ram is corrupted, then you can do nothing, i shipped mine to hp, ad they repaired it without any problems. i had many test ipk on it and run preware and messed up pretty much everthing. they still repaired it, without paying a penny.
Steps in OP worked for me.
Thanked and thanks!
many thx mate, it actually worked just fine for me
cheers
cannot get past the option2 please be more specific
Leoisright said:
appreciate it bro! This helped a bunch
Click to expand...
Click to collapse
i have got as far as the option2 but I;m not sure that option 2 is -a or -A can you please be more specific as I;m losing it keep trying this
Related
Hey Guys, i just got my new transformer prime last week and while installing the new firmware versions this morning i ran into a problem. The first firmware update installed fine but while the camera firmware update was downloading, the screen locked up and wouldn't detect any touch input (taps or swipes).
I did the usual reboot a few times and the first time i tried it i was returned to the unlock screen but it still wouldn't register any touch input. I rebooted again and this time i was greeted with an error page containing three gears in a circle with and orange triangle in the middle and an exclamation mark in the triangle (no text describing what this means). This takes up the entire screen in landscape-mode and in portrait-mode it takes up the top half while the bottom half shows the bottom of the portrait-mode unlock screen and the system bar along the bottom.
Android is still functioning as i can see notifications come and go on the bottom (gmail popped up and i checked it on my laptop and the notification went away) but when the tablet is connected to my PC it doesn't show thing on the device. The device comes up but the computer shows it as empty.
If anyone knows anything about this or any possible fixes i'd appreciate them greatly.
Thanks people
Edit: Problem Resolved - Let the tablet die, recharge it, turn it back on and it should be working again
Probably same problem as described here -> http://forum.xda-developers.com/showthread.php?t=1423503&page=12
Hope you resolve this.....
I would try rebooting again. then manually install or reapply the update though PC and Asus website where they have the firmware/system updates to manually install into prime. or you could even try the reset hole on the side or bringing up the bootloader menu to do a factory reset. good luck. post results or anything else you might have encountered.
How can i get to the bootloader menu to do the factory reset without the touch screen. the tablet isn't rooted if that matters
Mine did the same thing. I called up Asus and they are wanting me to send mine in and let them fix it, i decided i might want to check here and see if this was just me or if it was a problem shared by others....
---------- Post added at 04:13 PM ---------- Previous post was at 04:06 PM ----------
demandarin said:
I would try rebooting again. then manually install or reapply the update though PC and Asus website where they have the firmware/system updates to manually install into prime. or you could even try the reset hole on the side or bringing up the bootloader menu to do a factory reset. good luck. post results or anything else you might have encountered.
Click to expand...
Click to collapse
you can't manually install the updates without using the touchscreen which doesn't work.... i thought about that and tried to find some way of remotely doing this with some sort of software but Asus doesn't give a way of doing this...
Jordan.t said:
How can i get to the bootloader menu to do the factory reset without the touch screen. the tablet isn't rooted if that matters
Click to expand...
Click to collapse
its some combination of holding volume down and power button at the same time for a couple secs. it could be the opposite though, hold volume up and power down. can't exactly remember which one. it is here within the threads though. or you could even call Asus for the right combo on how to factory reset device back to like it was in the box. if manually installing software won't work since touchscreen unresponsive, factory reset may be only option. since you use the hardware keys to initiate actions. cuz once in menu, you use volume down to scroll to factory reset. then pressing volume up confirms actions. double check which combo is the one to initiate the menu. good luck and hope you can bring back the prime to its normal working state.
I called Asus Earlier and they went through the Factory reset process, but even that won't work. they ended up asking me to send it in to them to be fixed. its the same for others in this thread.
I called ASUS, they told me that there were numerous reports of this error and that they would email me or call me within 24-48 hours with a report on my "case". So apparently they know and there trying to do something about it whether or not that's an OTA software fix or if we have to send them all in to get them reset remains to be seen.
thats helpful to know
Jordan.t said:
How can i get to the bootloader menu to do the factory reset without the touch screen. the tablet isn't rooted if that matters
Click to expand...
Click to collapse
You will lose all your data if you do this...you are warned.
Hold down the Vol-down and power button. After the vibration of it restarting release both buttons. You will see some writing on the screen...don't tuch anything. After about 5 secs, you will be taken to a screen with 2 pictures: one saying "WIPE DATA" and the other a picture of the android mascot. Use the vol down to navigate between options and the vol up to select options. You will be asked to confirm your selection before it actually kicks off. Hope this helps.
Hi, the device is still usable by connecting the prime to a dock and using a USB mouse.
I've described this in the "New Firmware..." thread as well.
From the other threads it does seem like Factory Reseting makes no difference, and I will not do it because right now I have full root access (adb shell - su)
I believe with it, we could try and figure out how to fix the situation.
So if anyone has any ideas, please let me know.
Also, is this the "official" My transformer prime is bricked thread now?
thanks for the tip, but it didn't work. oh well... this is where Asus's locked bootloaders come back to get them. they could easily push out a recovery image and tell how to boot into the bootloader and flash it. but because they went with locked, they ended up screwing us over.....
Hi,
so by killing this process I am now able to get into the System via USB Mouse and use my prime, without getting the "orange gears" screen. That makes my prime at least partially usable again.
PID PR CPU% S #THR VSS RSS PCY UID Name
109 2 3% S 7 16920K 6796K fg system /system/bin/surfaceflinger
Lets see what else I can find.
Tried to reboot mine again using the vol-down and power button combo but it won't bring me to the menu with the option to factory reset anyway when i tired to turn it back on it wouldn't the device seems to have actually bricked this time
Jordan.t said:
Tried to reboot mine again using the vol-down and power button combo but it won't bring me to the menu with the option to factory reset anyway when i tired to turn it back on it wouldn't the device seems to have actually bricked this time
Click to expand...
Click to collapse
how much battery life was in it before it acted up? it might be time to call it quits and just exchange it. seems like you did and tried everything you could.
demandarin said:
how much battery life was in it before it acted up? it might be time to call it quits and just exchange it. seems like you did and tried everything you could.
Click to expand...
Click to collapse
For those of you with mouse access to the device
go to this address
ASUS Support
Select ANDROID as OS > Click FIRMWARE > Click your device US/WW (probably most of you are US)
Download the firmware file. Push it to you SD Card through any method.
A Triangle [!] will appear in your status bar.
Click on it
It will ask you to install the update, install it
Wait a few
The firmware should be reset (hopefully)
tell me how it goes!
A person on the transformers forum said he drained his tablet by rebooting it till it ran out of battery. Then charged it and did a factory wipe and now it functioning.
Sent from my PC36100 using xda premium
biggem001 said:
For those of you with mouse access to the device
go to this address
ASUS Support
Select ANDROID as OS > Click FIRMWARE > Click your device US/WW (probably most of you are US)
Download the firmware file. Push it to you SD Card through any method.
A Triangle [!] will appear in your status bar.
Click on it
It will ask you to install the update, install it
Wait a few
The firmware should be reset (hopefully)
tell me how it goes!
Click to expand...
Click to collapse
This has not worked for me so far, probably because it is a "downgrade" from the current system.
BTW this is what I get with dmsg
Code:
<3>[ 285.082630] asuspec: [asuspec_dockram_read_battery] Fail to read dockram b
attery, status -110
<3>[ 285.082960] asuspec: [asuspec_battery_monitor] Fail to access battery info
.
<3>[ 285.083548] pad-battery 4-000b: pad_get_psp: i2c read for 7 failed
<3>[ 285.084134] power_supply battery: driver failed to report `status' propert
y
Seems pretty obvious there is something wrong with the battery service.
ThrasherSC2K2 said:
This has not worked for me so far, probably because it is a "downgrade" from the current system.
BTW this is what I get with dmsg
Code:
<3>[ 285.082630] asuspec: [asuspec_dockram_read_battery] Fail to read dockram b
attery, status -110
<3>[ 285.082960] asuspec: [asuspec_battery_monitor] Fail to access battery info
.
<3>[ 285.083548] pad-battery 4-000b: pad_get_psp: i2c read for 7 failed
<3>[ 285.084134] power_supply battery: driver failed to report `status' propert
y
Seems pretty obvious there is something wrong with the battery service.
Click to expand...
Click to collapse
and this is why we need an unlocked BL, this way, i would just extract my firmware, zip it, sign it, and give it to you, and BAM your device would be fixed
biggem001 said:
and this is why we need an unlocked BL, this way, i would just extract my firmware, zip it, sign it, and give it to you, and BAM your device would be fixed
Click to expand...
Click to collapse
Yeah I technically COULD push it, since I have root. But seems risky.
Hello people, thanks for reading and trying to help in advance hehe
ok here it goes ....
i bought a galaxy tab 10.1v "Australian Vodafone Version" a while back, and since me and other users that own this pices of **** didn't get updates and stuff i decided to "unlock+Root+rom". I did that successfully after following guieds:
unlock :http://forum.xda-developers.com/showthread.php?t=1064793
root+room: http://forum.xda-developers.com/showthread.php?t=1079781
Everything wsa fine and i had the super user and everything, but in the second guide it says it is recomended or something like that to download ROM Manager from the market which i did, and i started the app and and did a backup. My Tab rebooted to a blank screen , i waited for a while but with no luck so i turned off and tried to go to DW mode or recovery mood so i can at least connecte it to odin3 and do something. When press V- + Power theres no DW nor recovery mode all i see is one smmall line on the left top corner that says "Booting Recovery Kernal Image#"
When i plug the usb into my computer nothing happenes no sound , no new device installing no nothin. but since i have been reading alot regarding this issue, i read something about APX mode and NVflash here and many other websites but i followed this guide :
http://forum.xda-developers.com/showthread.php?t=1130574
i got my tab connected but i couldn't do NVflash because whenever i do
"--sync" or "nvflash --bl bootloader.bin --go"
i get this :
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
some say that that means the device is locked eventho i pretty sure it not because i had the lock logo. anyway ...
just to answer every possible question in advnce and give more info :
*its a 10.1v "Vodafone Australia Version"
*was working fine after root/rom
*stoped working after using the app "ROM Manager" (i think its not compactible)
* the device on somekinda boot loop, the screen would turn on and off "blank screen with nothing in it no sound also"
* pressing Volum down + Pwer will taking me to a blank screen with one little line that says "Booting Recovery Kernal Image#"
*when i plug the usb to the computer nothing hapenes
* in APX mod is working but i cannot do anytning since the NVflash won't work.
* I followed everything step by step
Does that mean my device is useless ? is there anyway to get it back to life ?
Thank you and sorry for the spilling mistakes as im using a F'ed up keyboard
one more thing i did :
I let the battery drain overnight and pluged charged it again hopeing that will help, the battery logo won't even show up, just a blank screen
thanks
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A
lufc said:
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A
Click to expand...
Click to collapse
ops sorry about that, my bad
Hi Barry. Welcome to XDA. One quick suggestion: If you want to get help in an enthusiasts forum, don't call the object of everyone's affections a "pices [sic] of ****."
We all understand the stress of having non-responsive electronics; but you'll catch more flies with honey...
***edit. Wrote some stuff for you only to realize that you're on a 10.1v. Not sure how I missed that in your title (and thus, I suppose I can't comment on whether or not it really is a POS!). Until just now I never realized how different your tab is from the regular 10.1 (guides are much more difficult to follow!) Anyways, I found these threads that might be useful to you:
http://forum.xda-developers.com/showthread.php?t=1083517
and
http://forum.xda-developers.com/showthread.php?t=1232664
Good luck!
slack04 said:
Hi Barry. Welcome to XDA. One quick suggestion: If you want to get help in an enthusiasts forum, don't call the object of everyone's affections a "pices [sic] of ****."
We all understand the stress of having non-responsive electronics; but you'll catch more flies with honey...
***edit. Wrote some stuff for you only to realize that you're on a 10.1v. Not sure how I missed that in your title (and thus, I suppose I can't comment on whether or not it really is a POS!). Until just now I never realized how different your tab is from the regular 10.1 (guides are much more difficult to follow!) Anyways, I found these threads that might be useful to you:
http://forum.xda-developers.com/showthread.php?t=1083517
and
http://forum.xda-developers.com/showthread.php?t=1232664
Good luck!
Click to expand...
Click to collapse
i apologize for that, but i was referring to my tab only ... anyways
thanks for your reply and for the links you gave me .. but still the biggest problem is i'm unable to connect my tab to odin, and downloading mode and recovery mode are not even there .. theyre all gone, only APX mode is working and even with that, NVflash won't work and i would give me this error
"Nvflash started
rcm version 0X4
Command send failed (usb write failed)"
if i could connect to odin i could actually do something, or even NVflash i could run bootloader and it would install image files and all.
i'm not sure if i can do anything with APX other than NVflash .. or if i could somehow bypass Nvflash error ..
i just have a feeling that my tab won't make it
Just an idea... did you try to do the work with another pc?
For example a fresh XP 32bit install on another pc.
This "usb write error" seems strange.
Max
gfreeman86 said:
Just an idea... did you try to do the work with another pc?
For example a fresh XP 32bit install on another pc.
This "usb write error" seems strange.
Max
Click to expand...
Click to collapse
Thanks for replying. .. Yes i tried with anither pc. . I have read in this forum and others that this error means that the tablet is somehow locked even tho it wasnt before i root/rom it
Its like not writable, ill install a freah xp pro and givr it another try since i tried only win win 7
Did you try to drain completely the battery and then charge?
http://forum.xda-developers.com/showpost.php?p=19519586&postcount=15
seems it worked for someone
gfreeman86 said:
Did you try to drain completely the battery and then charge?
http://forum.xda-developers.com/showpost.php?p=19519586&postcount=15
seems it worked for someone
Click to expand...
Click to collapse
Yes i did as i metioned in my post, didnt help
When i charged it after i drained the battery, the screen light will turn on but no battery logo or anything.. The only thing that would show up on the screen is when i try to enter downloading mod/recovery mod by pressing power+volume is a little line on the top right corner which says : " booting recovery image# "
thank you for your reply, what do you guys recommend since i can access APX mod, will i be able to do anthing other than nvflash in APX mod?
Since you are getting a usb write error as well as no charge indicator, is it possible that your USB cable is bad?
sgip2000 said:
Since you are getting a usb write error as well as no charge indicator, is it possible that your USB cable is bad?
Click to expand...
Click to collapse
thanks for your reply
when i charge, the tablet does charge but no Battery logo, i can tell its charging because the screen lights will go on.
what i have tried so far :
* installed APX but when i try to nvflash it says something like writing failed
* tried both windows XP and windows 7
* drained the battery twice for 2 days
* changed USB cable
* tried to connect it to different versions on odin but computer only recognise the device in APX mode
* device still showing ( booting recovery kernel image#) when a try to access DW mod.
it all started when i used a backup program after rooting it, i don't get .. is its a backup it shouldn't delete everything (the system) and brick the tablet...
whats Kernel ? << noob
any new ideas guys ? is there any other programs/methods out there ?
anyone have the same problem ?
thanks
-Bazza
When it says booting recovery kernel image, did you try to just wait for about 15 to 20 minutes to find out if it boots again, or try logcat command?
djden said:
When it says booting recovery kernel image, did you try to just wait for about 15 to 20 minutes to find out if it boots again, or try logcat command?
Click to expand...
Click to collapse
yes, i left it like that till the next morning
** update **
Today i disassembled my tab after i read somewhere in this forum that i might get it back if i take the battery out or unplug the screen cables. Some claim that the touch screen could cause the tab to go into a boot loop; however that didn't work
i decided anyway to buy a new tab either Asus Transformer or Galaxy 8.9, even tho I'm kinda worried that this thing could happen to my new tab when i try to root it and install roms. I don't want to spend that much money until i figure out the problem, so i'm making this tablet "A testing Device" i'm gonna test every possible way to revive it for me and and others. I'll do my best with your help guys to solve this so we can provide help for others.
There was a Guide here in this forum about JTAGing that tablet along with a software that some company use to unbrick devices but i cold not find it, my cousin owns a hardware store and i could use everything i need .. i just need someone to guide me.
Thanks
Sounds like a cool project, sorry it cost so much.
zBarry, You should try this while you can, It sounds simple as it is but it worked for both my tablets that had the 0x4 aka locked bootloader. Sorry if you had already "Lego" lized your tablet into pieces but this may help. :]
http://forum.xda-developers.com/showthread.php?t=1478361
bumb!
im still looking with no luck ... please help ?
can i do anything with linux ?
zBarry said:
bumb!
im still looking with no luck ... please help ?
can i do anything with linux ?
Click to expand...
Click to collapse
As far as I know linux won't help, what % is your tablet charge at? Since you've opened it already why not just de-attach the battery and reattach it back and try to power it directly into fastboot. Normally draining is the same as stopping the flow of current into the tablet. Unlike phones where you can pop out the battery you can't do it to the tab unless you've opened it.
Can you please let me know what steps have you tried so far? Would be nice to know in detailed So I can help you out at best.
Misledz said:
As far as I know linux won't help, what % is your tablet charge at? Since you've opened it already why not just de-attach the battery and reattach it back and try to power it directly into fastboot. Normally draining is the same as stopping the flow of current into the tablet. Unlike phones where you can pop out the battery you can't do it to the tab unless you've opened it.
Can you please let me know what steps have you tried so far? Would be nice to know in detailed So I can help you out at best.
Click to expand...
Click to collapse
i think i have third every possible way out there... and the steps that i did to revive the device your way was :
i taped the power button and left it for like 2 days, then i plugged it to the computer in APX mode to check if its drained or not, but i think it was charging off the computer. So i repeated the first step and left it for 3 days, then plugged it into the socket. after couple of mins the screen turned on, but no logo or anything, just black screen (same issue). i decided to disassemble the device to take the battery out which i did and yet same result. i had hope so i re-did the battery drain thing and left it for a week and when i plugged it i pressed pwr+ vlo + and something.
my tab turns on, but just a black screen it won't that up, and power + volume up will show me a kernel message.
thanks so much, i aprreciate your trying to help any other way you think i should try ?
What sort of kernel message do you get? As far as I know maybe perhaps the contact's arent touching properly? Seems to me you did everything right but when it turns on you don't get the charging icon.
The good part is the display works and atleast you can boot up *Somehow* the bad part is you can't get it into Fastboot mode.
As far as I know the tablet is supposed to light up but have you checked if you get the offline charge icon (That green battery that sits in the middle of the screen and charges?) once you get it to drain/disconnect you should leave it to charge via wall socket for about 5-10secs for that icon to pop up. If you get that icon atleast then you know you are getting somewhere
I wish I had the tablet in hand so I could see what's going on. The whole oceans away solution makes it hard to guess what's happening
i have been trying to fix my nook for a couple of days, and i have tried:
http://forum.xda-developers.com/showthread.php?t=1470910
and all i get is white lines on the top of the screen, and then it becomes black.
Thanks in advance
LeCommuniste said:
i have been trying to fix my nook for a couple of days, and i have tried:
http://forum.xda-developers.com/showthread.php?t=1470910
and all i get is white lines on the top of the screen, and then it becomes black.
Thanks in advance
Click to expand...
Click to collapse
One and only one thing comes to mind. You must continue to charge when you boot this even if your battery is 100%. Use power cord to turn on NT and keep it powered for the entire time. It (ubuntu) freaks without power and shuts down!
I hope this is your problem if not please tell more including which NT 8 or 16 gig, etc.
Good luck!
LeCommuniste said:
and all i get is white lines on the top of the screen, and then it becomes black.
Click to expand...
Click to collapse
um, i know you're all stressed out, we've all been there ( me too ), but the guy above me is right. . . plz give us more information. . if it won't boot internal, will it boot boot something up on the external sd card ?
at some point, my nook just didnt start up, it went into the "restart your nook" scree
it boots from sd. and after i installed cyanogenmod 9 again, it didnt boot into it
i tried something else and i got this:
booti: bad boot image magic (in memory)
are you a 8GB or a 16 GB unit ?
is it true you are installing cm9 internal ?
you try to fix and now the internal is corrupt ?
16, and i dont know what happend, the onlything i know is i tried to reinstall cm9 back on
LeCommuniste said:
at some point, my nook just didnt start up, it went into the "restart your nook" screen
Click to expand...
Click to collapse
ah, the the senior devs in the dev area who created this cm9 -- made it a 'Cinderella rom', ie. it flat quits working on purpose. . they did it because some evil guys were selling the alpha code as a finished product. . so all people who run the cm9 rom have to go back and install the next cm9 version from their post...
installed alpha 3. didnt do anything. still "please restart your device"
i wiped all of the data on every partion, then installed cyanogenmod 9
still does it
LeCommuniste said:
i wiped all of the data on every partion, then installed cyanogenmod 9
still does it
Click to expand...
Click to collapse
if ( and a very big "if", ie. do not assume ) your partitions are corrupt ( from a past step gone bad ) then you have to go thru the partition re-build step ( in the dev area ) . . but can you boot up in ubuntu and examine your partitions first - see what shape they're in ?
LeCommuniste said:
i wiped all of the data on every partion, then installed cyanogenmod 9
still does it
Click to expand...
Click to collapse
Sorry I missed the above post follow that and report back
erm. how do i do that?
and thanks for the patience, guys
Please Help
old_fart said:
if ( and a very big "if", ie. do not assume ) your partitions are corrupt ( from a past step gone bad ) then you have to go thru the partition re-build step ( in the dev area ) . . but can you boot up in ubuntu and examine your partitions first - see what shape they're in ?
Click to expand...
Click to collapse
OF if you can help this person then please do. I have had another stroke and am very scrambled. I tried to put it together several times but as you have seen I just can't finish what I started.
I had a friend send this message for me.
Thanks!
tobdaryl said:
OF if you can help this person then please do. I have had another stroke and am very scrambled. I tried to put it together several times but as you have seen I just can't finish what I started.
I had a friend send this message for me.
Thanks!
Click to expand...
Click to collapse
i do not have the experience to help with a corrupt partition. ( if it is a corrupt one ) . i have not had to fix / repair a corruption on my unit . . i was lucky that the adam outler restore ( http://forum.xda-developers.com/showthread.php?t=1470910 ) fixed mine and it went back to a factory boot-up . . my thought is that your NT is not corrupted because the boot is working . . the boot just fails to load the next piece . . ( i took some time and read over the 'partition repair' posts and they scared the hell out of me ! . http://forum.xda-developers.com/showthread.php?t=1605664&highlight=damaged+partition+table ) my advice is to not re-format. do not re-partition. the senior people see the new people dive into un-necessary ( wrong ) steps way too early / often. . the senior people say they see 'relatively easy' fixes turned into a mess. . http://forum.xda-developers.com/showthread.php?t=1635116
.
if the steps seem too much or are going nowhere... . do you have a large B&N store in your area ?
LeCommuniste said:
erm. how do i do that?
and thanks for the patience, guys
Click to expand...
Click to collapse
from notes – safe nt recovery with cm7 sdcard:
http://forum.xda-developers.com/showthread.php?t=1481826
make cm7 sdcard boot and setup.
install http://forum.xda-developers.com/showthread.php?t=1458630
Nook Recovery Flasher.apk
Run Nook Tab Recovery Flasher and select Install Stock Recovery, exit program.
Power off. Remove sdcard.
Press power and n key and hold 2 seconds after screen is lit. Release power.
After 1 second longer release n and you should get data reset. Press n key twice to accept.
If lucky your trouble will be cleared if not then hard reset.
Power off. Remove sdcard if installed. Hold power and n till screen lit and continue to hold till screen goes black. Do this eight times. Ninth time use power as normal and when you see recovery press n key twice to accept full factory reset.
Good Luck!
My NT used to work beautifully. It was rooted and was a great device. Then it started to randomly shutdown.
Now, after factory resets and just about everything else imaginable, it boots normally, gets to the woman on the video screen, then just shuts off. If I hold the power button only, it stays on but only for a few seconds as the power button, oddly enough keeping it on, shuts it down.
Also, the only way it turns on is to connect to PC via USB. Power button will not turn it on unless connected.
Any one have ANY ideas what could be the issue?
Thanks a ton!
HW
Try Formating your external sdcard if any, make a wipe data factory reset. Leave it on CWM then Put it to charge full with original charger and USB cable. Leave it for 3-4 hours. After that unplug from power, reboot device in CWM and report back
~ V
Sent from my Cappy powered with Jelly Bean using Tapatalk 2
lavero.burgos said:
Try Formating your external sdcard if any, make a wipe data factory reset. Leave it on CWM then Put it to charge full with original charger and USB cable. Leave it for 3-4 hours. After that unplug from power, reboot device in CWM and report back
~ V
Sent from my Cappy powered with Jelly Bean using Tapatalk 2
Click to expand...
Click to collapse
Thanks. The problem is, when I boot to CWM, it flickers and will only stabilize by holding the power button in. I've tried several cards with fresh CWM and it always flickers and is nearly impossible to make a selection.
HarryWanger said:
Thanks. The problem is, when I boot to CWM, it flickers and will only stabilize by holding the power button in. I've tried several cards with fresh CWM and it always flickers and is nearly impossible to make a selection.
Click to expand...
Click to collapse
Hmmm that's odd. What model is your nook tablet 8 or 16 GB?
Sent from my Cappy powered with Jelly Bean using Tapatalk 2
lavero.burgos said:
Hmmm that's odd. What model is your nook tablet 8 or 16 GB?
Sent from my Cappy powered with Jelly Bean using Tapatalk 2
Click to expand...
Click to collapse
It's a 16GB model purchased 12/25/11. I've tried everything and have no idea what it could be. The CWM issue is really odd too. It's just a very fast flicker that won't let me select anything unless the power button is held down which then defeats the purpose since it'll shut down.
Also, if I ever am able to get it to do a data wipe through the flickering, I get a message as it goes through that states, "E:format_volume: make_ext4fs failed on /dev/block/mmcblk1p2"
Then it says "Data wipe complete" while still flickering and continues to do the same on any restart
HarryWanger said:
It's a 16GB model purchased 12/25/11. I've tried everything and have no idea what it could be. The CWM issue is really odd too. It's just a very fast flicker that won't let me select anything unless the power button is held down which then defeats the purpose since it'll shut down.
Also, if I ever am able to get it to do a data wipe through the flickering, I get a message as it goes through that states, "E:format_volume: make_ext4fs failed on /dev/block/mmcblk1p2"
Then it says "Data wipe complete" while still flickering and continues to do the same on any restart
Click to expand...
Click to collapse
Ok, tell me if at list when you boot into CWM (internal or sdcard) your device remains on and doesn't shutdown after few minutes. This is important in order to perform unbrick methods. Also let me know what unbrick method(s) have you tried so far, if any.
~ Veronica
lavero.burgos said:
Ok, tell me if at list when you boot into CWM (internal or sdcard) your device remains on and doesn't shutdown after few minutes. This is important in order to perform unbrick methods. Also let me know what unbrick method(s) have you tried so far, if any.
~ Veronica
Click to expand...
Click to collapse
When I boot into CWM it will remain on the CWM screen flickering forever until I shut it down.
I have tried everything on the forum to unbrick, including the ubuntu method several time. The only one I haven't been able to try is the internal partition restore since the files don't exist any longer to try that method.
Hope this info leads to something. Thank you for your help. I've spent endless hours on this and am now just trying to get it working again to donate it to a charity in a working condition. I have a new Nexus 7 which blows this away regardless but would like to donate a functioning tablet to a kid who would really appreciate it.
HarryWanger said:
When I boot into CWM it will remain on the CWM screen flickering forever until I shut it down.
I have tried everything on the forum to unbrick, including the ubuntu method several time. The only one I haven't been able to try is the internal partition restore since the files don't exist any longer to try that method.
Hope this info leads to something. Thank you for your help. I've spent endless hours on this and am now just trying to get it working again to donate it to a charity in a working condition. I have a new Nexus 7 which blows this away regardless but would like to donate a functioning tablet to a kid who would really appreciate it.
Click to expand...
Click to collapse
OK i think the unbrick method you're referring is @soshite's thread? that is the one i was going to suggest you, so what you need to follow that tutorial is meghd00t's cwm recovery sdcard which you can find here (it already have the gdisk and sgdisk built in), the scripts.zip (not sure if those scripts are built in the cwm sdcard aswell) and the 16gb partition images.
All the tools mentioned above and more can be found in my FTP Nook Tablet folder so i recommend you to bookmark it.
~ Veronica
lavero.burgos said:
OK i think the unbrick method you're referring is @soshite's thread? that is the one i was going to suggest you, so what you need to follow that tutorial is meghd00t's cwm recovery sdcard which you can find here (it already have the gdisk and sgdisk built in), the scripts.zip (not sure if those scripts are built in the cwm sdcard aswell) and the 16gb partition images.
All the tools mentioned above and more can be found in my FTP Nook Tablet folder so i recommend you to bookmark it.
~ Veronica
Click to expand...
Click to collapse
Thanks. I will try this and report back.
HarryWanger said:
Thanks. I will try this and report back.
Click to expand...
Click to collapse
No luck. The instructions make no sense. How can I get "to a terminal" when the NT turns off so quickly.
I'm afraid this it fried.
Frustrating since it boots to the stock woman in the video and just quits.
Maybe someone else wants to take a shot.
Make me an offer for this POS. My goal was to donate it to a children's charity here but it's useless in this state its in. Anyone want it?
Let me know. I have no more time to mess around with something that's about a year behind the latest technology now.
Thanks for all your help everyone but it's time to let this go.
I have downloaded REMIX OS beta version today and when I was installing it I was getting this error " failed to find cpu0 device node" after it it's get stuck at boot nothing happens after it!!
So please members help to do it....
i got the error too but it booted and installed. no other issues. saw the same error on Liliputing's video for beta. so most likely something else is causing the freeze
kantelia parth said:
I have downloaded REMIX OS beta version today and when I was installing it I was getting this error " failed to find cpu0 device node" after it it's get stuck at boot nothing happens after it!!
So please members help to do it....
Click to expand...
Click to collapse
I have same bug... anyone can help?
Yes this error line show when booting, don't known what's it mean
But my remix was booted and running fine no issue
Maromi said:
i got the error too but it booted and installed. no other issues. saw the same error on Liliputing's video for beta. so most likely something else is causing the freeze
Click to expand...
Click to collapse
Which bit is your PC??
I mean 32bit or 64bit???
And you have installed with PENDERIVE or hard drive ??
kantelia parth said:
I have downloaded REMIX OS beta version today and when I was installing it I was getting this error " failed to find cpu0 device node" after it it's get stuck at boot nothing happens after it!!
So please members help to do it....
Click to expand...
Click to collapse
it's not an error, it's a warning that can be ignored
https://bugzilla.redhat.com/show_bug.cgi?id=1254210
When I was installing it got to around 45% and then my screen went black and was getting no video signal for about 8 minutes. I just let it keep running and it came back on and finished and booted. Maybe that's what is happening?
fgdn17 said:
it's not an error, it's a warning that can be ignored
https://bugzilla.redhat.com/show_bug.cgi?id=1254210
Click to expand...
Click to collapse
So what will be the problem while installing REMIX OS BETA version ..!! According to u???
rcgamer said:
When I was installing it got to around 45% and then my screen went black and was getting no video signal for about 8 minutes. I just let it keep running and it came back on and finished and booted. Maybe that's what is happening?
Click to expand...
Click to collapse
I think that was the screen going to sleep. I toutched my kepboard and it came back on again. (mouse won't do anything as it's still command line)
kantelia parth said:
So what will be the problem while installing REMIX OS BETA version ..!! According to u???
Click to expand...
Click to collapse
I wouldn't know, and you can keep guessing forever BUT if you learn how to read the error logs like
logcat / dmesg / bugreport you may get some indication of why it's not working for you yet working
for many others.
fgdn17 said:
I wouldn't know, and you can keep guessing forever BUT if you learn how to read the error logs like
logcat / dmesg / bugreport you may get some indication of why it's not working for you yet working
for many others.
Click to expand...
Click to collapse
Can u find in favour of us!!!?
kantelia parth said:
I have downloaded REMIX OS beta version today and when I was installing it I was getting this error " failed to find cpu0 device node" after it it's get stuck at boot nothing happens after it!!
So please members help to do it....
Click to expand...
Click to collapse
I got that error on every device i've put remix on, all of them boot and install just fine. You may want to try the install again.
I had the same error. I had not disabled secure boot. After I did that it worked fine. On first boot it did take about 10 minutes. Not sure if it was checking the disk or formatting it. Anyway, make sure you disable secure boot. (hold down F2 then press power on for my lenovo Y410p which was totally obliterated and made useless by Windows 10)
fsuinnc said:
I had the same error. I had not disabled secure boot. After I did that it worked fine. On first boot it did take about 10 minutes. Not sure if it was checking the disk or formatting it. Anyway, make sure you disable secure boot. (hold down F2 then press power on for my lenovo Y410p which was totally obliterated and made useless by Windows 10)
Click to expand...
Click to collapse
How do I do it please help me bro!!!
✌✌✌
kantelia parth said:
I have downloaded REMIX OS beta version today and when I was installing it I was getting this error " failed to find cpu0 device node" after it it's get stuck at boot nothing happens after it!!
So please members help to do it....
Click to expand...
Click to collapse
Try to switch display port to onboard may be it doesn't support the gpu
For Legacy only: put nouveau.modeset=1 i915.modeset=0 in the grub if you have a Nvidia GPU
kantelia parth said:
How do I do it please help me bro!!!
Click to expand...
Click to collapse
It depends on what kind of system you have. Google search how to get to the boot menu for your particular system. Usually you shut down the system then press and hold down a particular button while you turn on the power. Usually you hold esc or F1 or F2 but different systems use different buttons. When you get to the boot menu it looks very old school. use left and right arrows to get to boot tab. arrow down to Secure boot and (I think) F5 or F6 to switch from enabled to disabled. follow instructions on screen to exit and save.
AmoraRei said:
For Legacy only: put nouveau.modeset=1 i915.modeset=0 in the grub if you have a Nvidia GPU
Click to expand...
Click to collapse
Where should I put this ????
fsuinnc said:
It depends on what kind of system you have. Google search how to get to the boot menu for your particular system. Usually you shut down the system then press and hold down a particular button while you turn on the power. Usually you hold esc or F1 or F2 but different systems use different buttons. When you get to the boot menu it looks very old school. use left and right arrows to get to boot tab. arrow down to Secure boot and (I think) F5 or F6 to switch from enabled to disabled. follow instructions on screen to exit and save.
Click to expand...
Click to collapse
OK !!
I will try this ..
Same Problem
Stuck black screen on PC1 (32bit) and similar on new PC2 (64bit UEFI)... This OS just doesn't work at all.