Installed cm via directions. No problems. Decided to try installing a new Android kernel. Flashed via recovery.
Moboot, but couldn't get into any os, not even recovery. Eventually got into Android. Was able after many attempts to get to webos. Decided to try and reinstall cm9 and such. Plugged into computer while in webos to move files over and got a need to format window. Hit yes (i know, I know).
Now can't even get moboot. Decide to Dr it. Gets to 12% and doesn't move. Google it and follow some novaterm/cmd directions.
Now Dr gets to 8% and says unable to reset device. Have a hard time getting into HP recovery (usb symbol). Mostly get an exclamation point in a triangle and the url for Dr.
What r my options, HP warranty? Thx
Sent from my PG86100 using XDA App
The cm team can help you on IRC here's info I copied from the cm thread go here and they should get you right http://webchat.freenode.net?channels=cyanogenmod-touchpad
The reason the doctor is failing is because Android messes with your partitions and at 12% the webOS doctor is verifying partitions. Have you attempted ACMEUninstaller? When at the webOS screen go ahead and run ACMEUinstaller. Then if uoi can boot into webOS do the complete wipe to wipe the entire SD section. Then doctor it and then reflash Android with ACMEinstaller2
Sent from T the Touchpad
Eat it iPhone said:
Installed cm via directions. No problems. Decided to try installing a new Android kernel. Flashed via recovery.
Moboot, but couldn't get into any os, not even recovery. Eventually got into Android. Was able after many attempts to get to webos. Decided to try and reinstall cm9 and such. Plugged into computer while in webos to move files over and got a need to format window. Hit yes (i know, I know).
Now can't even get moboot. Decide to Dr it. Gets to 12% and doesn't move. Google it and follow some novaterm/cmd directions.
Now Dr gets to 8% and says unable to reset device. Have a hard time getting into HP recovery (usb symbol). Mostly get an exclamation point in a triangle and the url for Dr.
What r my options, HP warranty? Thx
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
lucky for us, the TP can never be bricked unless you start to manually edit partition tables (and even then, its fixable with much hair pulling, ive personally troubleshooted this with a friend before )
maybe these threads can help you out:
http://forum.xda-developers.com/showthread.php?t=1236727&page=2.
http://forum.xda-developers.com/showthread.php?t=1379579
it really helps to have a grasp on how novaterm works, and ALWAYS ALWAYS re read your commmands to ensure you typed it correctly (upper/lower case espicially ;P)
Thx guys ill look into it, but I'ma be busy so ill have to chk this out tomorrow
Sent from my PG86100 using XDA App
http://forum.xda-developers.com/showthread.php?t=1426244
Try it. It may just work.
rr5678 said:
http://forum.xda-developers.com/showthread.php?t=1426244
Try it. It may just work.
Click to expand...
Click to collapse
oh god, that brings back terrible memories of "unbricking" my buddies TP from scratch using mine as a reference
and yes, Eat it iPhone, this is the best last alternative for repair, you will be restored to 100% BNIB (or LNIB as the case would be )
Solidus_n313 said:
oh god, that brings back terrible memories of "unbricking" my buddies TP from scratch using mine as a reference
and yes, Eat it iPhone, this is the best last alternative for repair, you will be restored to 100% BNIB (or LNIB as the case would be )
Click to expand...
Click to collapse
It may be horrible but in the end it's worth it
P.S.: I read that link in your signature (The TRUTH: XDA: Then and Now), and all I have to say is.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
im still wating for a complete recovery without bootie... which doesnt evn turn on the screen.heh
as said before more likely than not its a currupted partition that its stoping on...
darkassain said:
im still wating for a complete recovery without bootie... which doesnt evn turn on the screen.heh
as said before more likely than not its a currupted partition that its stoping on...
Click to expand...
Click to collapse
There is no recovery from a missing bootie (not that I know of). A missing bootie is like a missing hboot.
rr5678 said:
There is no recovery from a missing bootie (not that I know of). A missing bootie is like a missing hboot.
Click to expand...
Click to collapse
yep there is a way, you just havent heard of it (the pre has a way to boot from a corrupted bootie too)...
you can boot directly from the usb into the cpu bypasing bootie (instead of power + vol-up to enter bootie try it with vol-down while connected to a pc , and you will get what i mean..)
work has been done on this but a working product hasnt...
also is the hboot in nand or rom (im gueasing the nand /boot partiton just as with the few android devices i have worked on)
darkassain said:
yep there is a way, you just havent heard of it (the pre has a way to boot from a corrupted bootie too)...
you can boot directly from the usb into the cpu bypasing bootie (instead of power + vol-up to enter bootie try it with vol-down while connected to a pc , and you will get what i mean..)
work has been done on this but a working product hasnt...
also is the hboot in nand or rom (im gueasing the nand /boot partiton just as with the few android devices i have worked on)
Click to expand...
Click to collapse
No, the Pre is a completely different device. The Pre has an OMAP3430, while the TouchPad has your typical (non-USB bootable) Qualcomm processor.
And hboot is in the nand. (but still erasable)
rr5678 said:
No, the Pre is a completely different device. The Pre has an OMAP3430, while the TouchPad has your typical (non-USB bootable) Qualcomm processor.
And hboot is in the nand. (but still erasable)
Click to expand...
Click to collapse
doesnt matter boot with power+voldown and you enter qualcomm recovery which can boot from usb....
ps should have said that this only works on the TP
pps should mention that other qualcomm devices can boot from usb too...
darkassain said:
doesnt matter boot with power+voldown and you enter qualcomm recovery which can boot from usb....
ps should have said that this only works on the TP
pps should mention that other qualcomm devices can boot from usb too...
Click to expand...
Click to collapse
If you're talking about QHSUSB_DLOAD, there is no known way to use that. No image files, nothing.
rr5678 said:
If you're talking about QHSUSB_DLOAD, there is no known way to use that. No image files, nothing.
Click to expand...
Click to collapse
which is why i mentioned in two different posts that that its "not working" and why "im waiting" for something like this...
it works on some phones though which means it will communicate
darkassain said:
which is why i mentioned in two different posts that that its "not working" and why "im waiting" for something like this...
it works on some phones though which means it will communicate
Click to expand...
Click to collapse
I wish it was known what to do though. That's a super low level function.
Related
UPDATED. This will put you to STOCK 2.2! Using ODIN thanks to eugene373.
If you want stock and are able to get in to recovery and want a flashable rom. click here
This started as a thread asking for help, with the little help I got... and a little searching NOW this thread is to help other people who are having the same problem
ALSO its to show that a little searching on this forum, you will pry find the answers you are looking for.
EVERYTHING in here I found in the Bible, that is located in the development section.
This guide is for non hardware locked vibrants... if you are hardware locked check out this threadhere
First off you will need to get odin and the correct files.
I have packaged eugenes 2.2 pit and tar(md5) files in a zip along with odin. these are all the files you will need and you can download them here
(remember this is for unofficial 2.2 if you want Official 2.1 files click here )
s15274n (thread here) has everything you will need in his [Tips & Tricks] thread AND MORE!
so make sure to check that out and read the "EASY WAY TO GET THE JI6 UPDATE" before you go any further with my thread.
Georgegreco86(thread here) made this awesome image (below) and it works perfectly....
HOWEVER some times there are some complications that happen that i cover below.
TO GET IN TO DOWNLOAD MODE
I have found the EASIEST WAY to do this is:
1.pull the battery out of the phone.
2.plug usb into computer
3.put the battery back in the phone
4.hold in the volume up and down
5.plug usb in to phone
it should bring you to the download mode in seconds.
now you should unplug the usb From the phone..
make sure the battery stays in, and open odin.
now follow the instructions below.
1. Open Odin3_v1.0
2. Load .512 into the PIT placeholder
(In this case s1_odin_20100512)
3. Load *FILE.tar* into PDA placeholder
(In this case Eugene_2E_JK2_Froyo.tar.md5)
4. Make sure COM port has a number in it
This means your phone is connected, if your phone is not connected make sure you have the correct drivers)
5. Press Start!
6. If you it all works your done... if not keep reading!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IF YOU RUN IN TO PROBLEMS!
If your phone is not connecting to odin.It might be because you need the correct drivers, thanks to TGA_Gunnman they are located here http://forum.xda-developers.com/showthread.php?t=728929.
I was able to just let the computer search for them and with a few clicks, had the drivers installed.
To install the Android USB driver on Windows Vista for the first time:
1. Connect your Android-powered device to your computer's USB port. Windows will detect the device and launch the Found New Hardware wizard.
2. Select "Locate and install driver software."
3. Click "Next." Vista may prompt you to confirm the privilege elevation required for driver installation. Confirm it.
Freezing on "cache.rfs"
searching on google i found a website called fractionalphones.com, the post was about this and it said what i had to do was reboot my computer and hit F8 (just keep touching it) and when it gets to the "safemode screen" arrow down to "Disable Digital Signature Verification"
Also a problem Some people had was the usb port used...
So if it does not work try a new port!
Use oclf. Remove the lag fix first, then ant other optimizations you may have clicked, then ext 2 and finally root. I had to do this to send back my phone. Now the ext2 takes awhile so be patient.
Sent from my SGH-T959 using XDA App
ipeench said:
So if I have rooted the phone and have installed the OCLF from the market. But I wasn't the phone back as if I just took it ot the box.. What's the best way to do that.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
The easiest and cleanest way to do it is to Odin the phone back to stock.
Odin Visual Guide
Stock Firmware
tjhart85 said:
The easiest and cleanest way to do it is to Odin the phone back to stock.
Click to expand...
Click to collapse
Sweet, you even put in links to reading material! In a day of being flamed for asking questions like this..words can not express the kindness you have shown, thank you.
Sent from my SGH-T959 using XDA App
creglenn said:
Use oclf. Remove the lag fix first, then ant other optimizations you may have clicked, then ext 2 and finally root. I had to do this to send back my phone. Now the ext2 takes awhile so be patient.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
It wont let me remove the lag fix, v2 says i dont have the lag fix installed
and v1 says "you only have 346MB free on RFS, but 364MB used on EXT2. You must free up some space"
and then it tells me i dont have enough to install either v1 or v2 of the lag fix
BUT my quadrant is 2000+ so i know its installed.
i saw the other tread about this but it didnt really tell me much.
ipeench said:
It wont let me remove the lag fix, v2 says i dont have the lag fix installed
and v1 says "you only have 346MB free on RFS, but 364MB used on EXT2. You must free up some space"
and then it tells me i dont have enough to install either v1 or v2 of the lag fix
BUT my quadrant is 2000+ so i know its installed.
i saw the other tread about this but it didnt really tell me much.
Click to expand...
Click to collapse
LOL, One of the reasons I suggested Odin. It'll "just work" even if you have the lagfix (at least it did for me). Make sure you backup everything on the SD card that you want & tell it to repartition. If all goes well, everything down to the internal SD card has been put back to stock.
I know when I did the lagfix, I had a PC app that just ran ADB commands in a batch file (basically). After a week or so it got unbearably slow and even the remove lag fix that came with it wouldn't work, so I used Odin to go back to stock.
--------
But, I think what it's complaining about is you need to free up ~20MB of space in order to remove the lag fix. Since it needs to move the files that it put on the ext2 partition back to the RFS partition, it needs at least that much space before it can move the files & then delete the ext2 partition.
bumping because I figured out what I was doing and I think this can help a lot of other people.
I'm trying to do the "Odin back to stock" process but I'm having a little trouble. I've got all the files and opened Odin etc. I entered the .pit file and the .tar file. Auto-reboot and f. reset time are checked. I click start and I get "<OSM> All threads completed. (succeed 0 / failed 0)"
What am I doing wrong?
trunkstar1 said:
I'm trying to do the "Odin back to stock" process but I'm having a little trouble. I've got all the files and opened Odin etc. I entered the .pit file and the .tar file. Auto-reboot and f. reset time are checked. I click start and I get " All threads completed. (succeed 0 / failed 0)"
What am I doing wrong?
Click to expand...
Click to collapse
Odin isn't recognizing your phone. You should double check that the drivers are properly installed. Then, make sure Odin is on and click Reset if need be. Put phone into Download Mode and then plug it into computer.. A yellow box should appear at top of Odin, which let's you know you're successfully connected.
Hope that helps!
.:|Sent from my Super AWESOME Vibrant using XDA App|:.
That did help, thanks. And, with some help from other XDA forumers I got the right drivers installed and I'm in motion now. Thanks again.
trunkstar1 said:
That did help, thanks. And, with some help from other XDA forumers I got the right drivers installed and I'm in motion now. Thanks again.
Click to expand...
Click to collapse
With all that i have taken from this forum..I'm glad i can finally give back!
ipeench said:
This started as a thread asking for help, I got a little help(thank you for pointing me in the right direction tjhart85)
NOW this thread is to help other people who are having the same problem
ALSO to show that a little searching on this forum, you will pry find the answers you are looking for.
pretty much everything in here i found in the Bible, that is located in the development section.
This is for non hardware locked vibrants... i dunno what to tell you if yours is hardware locked because honestly i have no clue what that even means :-/ I'm just as new to this as you are!
First off you will need to get odin and the correct files.
and rhcp0112345(thread here) found the "true stock 2.1 firmware for vibrant" and all the files you will need,including odin are bundled in a nice little zip file for you.
http://tinyurl.com/2bc5b6r
Georgegreco86(thread here) made this awesome image (below) and it works perfectly.... but some times there are some complications that happen that i cover below.
TO GET IN TO DOWNLOAD MODE
I have found the EASIEST WAY to do this (IMO) is
1.pull the battery out of the phone.
2.plug usb into computer
3.put the battery back in the phone
4.hold in the volume up and down
5.plug usb in to phone
it should bring you to the download mode in seconds.
now you should unplug the usb.. make sure the battery stays in, and open odin.
now follow georgegrecos instructions.
Some people have said to load the files (PIT and TAR) before reconnecting the phone to the computer so that is how I did it and it worked perfect.
IF YOU RUN IN TO PROBLEMS!
If your phone is not connecting to odin.It might be because you need the correct drivers, thanks to TGA_Gunnman they are located here http://forum.xda-developers.com/showthread.php?t=728929.
I was able to just let the computer search for them and with a few clicks, had the drivers installed.
To install the Android USB driver on Windows Vista for the first time:
1. Connect your Android-powered device to your computer's USB port. Windows will detect the device and launch the Found New Hardware wizard.
2. Select "Locate and install driver software."
3. Click "Next." Vista may prompt you to confirm the privilege elevation required for driver installation. Confirm it.
Freezing on "cache.rfs"
searching on google i found a website called fractionalphones.com, the post was about this and it said what i had to do was reboot my computer and hit F8 (just keep touching it) and when it gets to the "safemode screen" arrow down to "Disable Digital Signature Verification"
Also a problem i had was the usb port i was using... so if it does not work try a new port!
Click to expand...
Click to collapse
Perfect,thanks.Previous to the J16 OTA update,I just held volume down/power.
I flashed back to stock to make sure I'd get the update without a hitch,which I did.
trunkstar1 said:
That did help, thanks. And, with some help from other XDA forumers I got the right drivers installed and I'm in motion now. Thanks again.
Click to expand...
Click to collapse
Coolness! Pass on the knowledge!
This is the same method I tried last night. Mine wont get past the bootup sequence. any help?
wicked1lbc said:
This is the same method I tried last night. Mine wont get past the bootup sequence. any help?
Click to expand...
Click to collapse
Try re-downloading the files and doing it again, maybe you got a bad file or something? This should work and if it does not... like I said I'm brand new to this, I had a problem figured out how to fix it and figured share the info, if it does not work for you, hopefully someone with more knowledge will chime in.
The tinyurl link you posted is bad. Looks like too many people have downloaded and the account is suspended :/ can someone upload them to somewhere else? I really need them
hiddengopher said:
The tinyurl link you posted is bad. Looks like too many people have downloaded and the account is suspended :/ can someone upload them to somewhere else? I really need them
Click to expand...
Click to collapse
this is correct, i do not need this right now but it would be nice to have
Hey guys, I am new at this My status stays at file analysis. My phone is in download mode as well.
SORRY! i have been away from the computer for a few days :-/
go to this thread
http://forum.xda-developers.com/showthread.php?t=732458
it has all the info you will need AND THEN SOME! it has the proper files and a little instruction spot with it... plus that one gives your the update.
if you still have trouble come back and i will try to help!
rcanela1 said:
Hey guys, I am new at this My status stays at file analysis. My phone is in download mode as well.
Click to expand...
Click to collapse
try switching usb ports.. i remember that happening to me.. i dont remember what i did tho haha.
im sure a google search will help with that one thats what i did
I have searched for a topic, but they didn't give me any answers. I have tried EVERYTHING, buying a new cable, turning off USB Debugging, hell I even did a hard reset on the tablet.
When I connect the two devices, "MTP initialisation" comes up on the Tab sometimes, and when I say that I have to keep unplugging and pugging in the damn thing. SO, it says connected on the Tab, but my PC will not recognize it at all. There is nothing under Device Manager, and nothing under Computer.
And Yes, all my drivers have been installed. I really wanted that ICS rom and this is making me frustrated. If I can;t get this resolved, I'm getting an iPad 3 lol. Please help!
galaxytabevo said:
I have searched for a topic, but they didn't give me any answers. I have tried EVERYTHING, buying a new cable, turning off USB Debugging, hell I even did a hard reset on the tablet.
When I connect the two devices, "MTP initialisation" comes up on the Tab sometimes, and when I say that I have to keep unplugging and pugging in the damn thing. SO, it says connected on the Tab, but my PC will not recognize it at all. There is nothing under Device Manager, and nothing under Computer.
And Yes, all my drivers have been installed. I really wanted that ICS rom and this is making me frustrated. If I can;t get this resolved, I'm getting an iPad 3 lol. Please help!
Click to expand...
Click to collapse
Had a similar problem myself and it ended up being the PC usb drivers. Used a program on the PC to remove all the drivers for the tab off the PC and reinstalling them and everything went great from there.
I thought the program was called Dev view or something, but can't find it right now, but anyway google how to remove drivers from your win version and you should be able to manually remove the usb drivers pretty easily. I ended up removing every usb driver except my mouse and keyboard from Windows 7, installing the drivers for the tab downloaded from Samsung directly and haven't any problems since.
This may be a bit of overkill so you might want to wait for other fixes to be suggested too.
Good luck.
Edit: just noticed this in two other recent threads "MTP selected under settings/storage/USB computer connection" don't know if it's only related to ics, cause I don't have this option on my tab running Task 14 slim. So may be of no help what so ever.
Sent from my GT-P7510 using XDA Premium HD app
Benzoman said:
Had a similar problem myself and it ended up being the PC usb drivers. Used a program on the PC to remove all the drivers for the tab off the PC and reinstalling them and everything went great from there.
I thought the program was called Dev view or something, but can't find it right now, but anyway google how to remove drivers from your win version and you should be able to manually remove the usb drivers pretty easily. I ended up removing every usb driver except my mouse and keyboard from Windows 7, installing the drivers for the tab downloaded from Samsung directly and haven't any problems since.
This may be a bit of overkill so you might want to wait for other fixes to be suggested to.
Good luck.
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
How can you tell which driver is which though? I can't seem to find the Dev view thing, even though you're not sure about it lol
galaxytabevo said:
How can you tell which driver is which though? I can't seem to find the Dev view thing, even though you're not sure about it lol
Click to expand...
Click to collapse
I don't remember, sorry I'm old and can't get to my PC right now. Hopefully someone will jump in here soon or I can get to my PC to figure out what I did exactly.
Sent from my GT-P7510 using XDA Premium HD app
Benzoman said:
I don't remember, sorry I'm old and can't get to my PC right now. Hopefully someone will jump in here soon or I can get to my PC to figure out what I did exactly.
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah, it would be a favor whenever you use your PC again to remember to check back lol, hopefully someone will remember
I just checked again, and the tablet is charging through the USB, which I'm not sure why. Every once in a while when plug it in to the USB, the battery gets a small red x on it, and it says MTP initialisation, but nothing on the computer
galaxytabevo said:
I just checked again, and the tablet is charging through the USB, which I'm not sure why. Every once in a while when plug it in to the USB, the battery gets a small red x on it, and it says MTP initialisation, but nothing on the computer
Click to expand...
Click to collapse
I think Misledz just dealt with a tab with the red x on it. Please pm him if you would and tell him I sent you to point out this thread. I'm dealing with a lot of other things and may not be much help with my mind going a hundred different directions. I'm sure he can help get you on the right track quickly. one of his posts should be easy to find in general or q&a sections.
Don't tell him I said this but he's a great help.
Sent from my GT-P7510 using XDA Premium HD app
Benzoman said:
I think Misledz just dealt with a tab with the red x on it. Please pm him if you would and tell him I sent you to point out this thread. I'm dealing with a lot of other things and may not be much help with my mind going a hundred different directions. I'm sure he can help get you on the right track quickly. one of his posts should be easy to find in general or q&a sections.
Don't tell him I said this but he's a great help.
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
lol, I will do that thanks.
Well, yeah sorry that I didn't reply via the PM as it tends to get flooded at times and I lose track of where and who sent the original Do forgive me for that.
The problem is the red X appears when you had the USB charge from the Overcome series, I'm pretty sure it's a lib file that conflicts with other ROM's and such, and they said there was a way to remove it, but it's dug somewhere underneath their thread, the best bet would be to attempt a factory reset, I do hope that your data is backed up via Titanium or something before you attempt this, because doing a factory reset via device *Not CWM* tends to reset all sorts of mods applied to the phone, and the user applications.
If you do attempt a factory reset do let me know You'd be surprised what a clean swipe can do (Problem is there isn't an external sd slot) so things tend to get left behind from other ROM's (The ones that aren't replaced anyway during installation)
Misledz said:
Well, yeah sorry that I didn't reply via the PM as it tends to get flooded at times and I lose track of where and who sent the original Do forgive me for that.
The problem is the red X appears when you had the USB charge from the Overcome series, I'm pretty sure it's a lib file that conflicts with other ROM's and such, and they said there was a way to remove it, but it's dug somewhere underneath their thread, the best bet would be to attempt a factory reset, I do hope that your data is backed up via Titanium or something before you attempt this, because doing a factory reset via device *Not CWM* tends to reset all sorts of mods applied to the phone, and the user applications.
If you do attempt a factory reset do let me know You'd be surprised what a clean swipe can do (Problem is there isn't an external sd slot) so things tend to get left behind from other ROM's (The ones that aren't replaced anyway during installation)
Click to expand...
Click to collapse
Thanks for your reply but the problem is that I'm not rooted and I have done a factory reset. The problem still persists.
Sent from my SPH-D710 using XDA
Have you tried manually mounting the internal drive via CWM? CWM->Mount? It's different from MTP
Misledz said:
Have you tried manually mounting the internal drive via CWM? CWM->Mount? It's different from MTP
Click to expand...
Click to collapse
How do you do that? Is that Clockwork, because I thought you needed to be rooted for that
Basically CFRoot is CWM+Root, CWM is just a custom recovery module made for flashing mods.
You need to select these options as shown, Ignore the pink walls
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Misledz said:
Basically CFRoot is CWM+Root, CWM is just a custom recovery module made for flashing mods.
You need to select these options as shown, Ignore the pink walls
Click to expand...
Click to collapse
I appreciate your pictures and help, but I have no idea of getting to this point. Everywhere I read it says that I need to be rooted to have CWM, I am completely stock, no root.
Good sir, you don't need root to get to this point. Just flash CWM from the Overcome thread or anywhere, It's all over the Development section, Just flash it via Odin, I assume by this point you know how to use Odin? If you don't it's all good, I'm willing to help you with that too
I took the liberty of uploading CWM recovery for you,
http://www.mediafire.com/?6c5tdmds927npdv
Cheers,
Fitz
Edit: Oh good lord, I just realized since you don't have CWM you can't get the PC to recognize the tab itself, silly me. Have you tried putting it into download mode and seeing if the tablet is detected in Odin?
PS: Do you know what Odin is?
Misledz said:
Good sir, you don't need root to get to this point. Just flash CWM from the Overcome thread or anywhere, It's all over the Development section, Just flash it via Odin, I assume by this point you know how to use Odin? If you don't it's all good, I'm willing to help you with that too
I took the liberty of uploading CWM recovery for you,
http://www.mediafire.com/?6c5tdmds927npdv
Cheers,
Fitz
Edit: Oh good lord, I just realized since you don't have CWM you can't get the PC to recognize the tab itself, silly me. Have you tried putting it into download mode and seeing if the tablet is detected in Odin?
PS: Do you know what Odin is?
Click to expand...
Click to collapse
I will definitely try this when I get home, I really appreciate your help on this issue. Last time I tried using Odin in download mode, the PC would not connect but I will retry it later with these directions.
Sent from my SPH-D710 using XDA
Ah no worries mate, it's all good I gain user knowledge like this Experience being the wisest mans weapon, they say
I think a combo of sdk/ADB and samsung drivers are enough to see odin. (if i remember right) Connected to odin without cwm many times before development. Uninstall any samsung applications and drivers(if applicable and separate from apps) Reinstall samsung drivers via installing "Kies", then install SDK... this combo should allow Odin to see your device. Odin is a samsung program licensed to samsung and therefor should not require root access or CWM.
If i remember correctly... sorry been quite a while
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
Yeah guys it didn't work. Even when in download mode and the SDK thing, nothing is recognized.
I chatted with a Samsung service rep for like an hour, I swear this guy must have been a robot. He told me to do what everyone else on this forum told me to do and it didn't work. He just told me to file a service request....yeah no.
I called this guy a magnificent bastard and my homeboy, and he didn't even give back the slightest emotion
Well, unless someone else can help me, I'm getting an iPad 3....I'll stick to Androids for my phone but going all Apple for my tablets. Getting sick of the sluggishness of Honeycomb, didn't even get to try ICS because of this issue.
Hi xda. I have a atrix 4g which is a at&t model and while flashing a rom it bricked. when i try to open it says failed to boot then it says entering ...... recovery so quickly that i hardly caught what it says. and then screen goes black, nothing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(this is from google, the problem is same)
the phone doesnt enter recovery or anything else. i know usb jig method but i failed to do it. if you may help me i will really appreciate that
mike4peace said:
Hi xda. I have a atrix 4g which is a at&t model and while flashing a rom it bricked. when i try to open it says failed to boot then it says entering ...... recovery so quickly that i hardly caught what it says. and then screen goes black, nothing.
(this is from google, the problem is same)
the phone doesnt enter recovery or anything else. i know usb jig method but i failed to do it. if you may help me i will really appreciate that
Click to expand...
Click to collapse
So if the message on the screen matches your problem, that must mean that you are like other members of recent. it means you don't know how to use this wonderful creation called a search and need to create pointless threads.
took me all of 5 seconds to do what you didn't do. I mean even if you had typed what you think the screen showed, the auto fill feature would have pointed you in the right direction too
http://forum.xda-developers.com/showthread.php?t=1490903
palmbeach05 said:
So if the message on the screen matches your problem, that must mean that you are like other members of recent. it means you don't know how to use this wonderful creation called a search and need to create pointless threads.
took me all of 5 seconds to do what you didn't do. I mean even if you had typed what you think the screen showed, the auto fill feature would have pointed you in the right direction too
http://forum.xda-developers.com/showthread.php?t=1490903
Click to expand...
Click to collapse
thank you for responding, but i have been searching for days but i hadnt found this thread thanks a lot. and here is another problem: i have a folder named fastbood in c:/ which contains fastboot.exe, adbwinapi and adbwinusbapi.dll but in the cmd screen i failed to do what im supposed to do.
2: Located in the folder where the files are.
i dont know what that means
i guess i did it but it says waiting for device, so the computer doesnt recognize my device
You also need drivers.
All of that has been covered already. Did you search?
ravilov said:
You also need drivers.
All of that has been covered already. Did you search?
Click to expand...
Click to collapse
yes mate i have motorola device manager, as far as i know this the same thing right? just like samsung's kies
i really did tons of search but im almost hopeless. guys who have the same problem did solved it by just taking device to fastboot but mine is not going in that mode. when i plug the device its charger it says same problem and also says battery too low to flash. so im just gonna go and buy a new battery
mike4peace said:
thank you for responding, but i have been searching for days but i hadnt found this thread thanks a lot. and here is another problem: i have a folder named fastbood in c:/ which contains fastboot.exe, adbwinapi and adbwinusbapi.dll but in the cmd screen i failed to do what im supposed to do.
2: Located in the folder where the files are.
i dont know what that means
i guess i did it but it says waiting for device, so the computer doesnt recognize my device
Click to expand...
Click to collapse
yes you do. you just told us where you have the files. navigate via cmd to the folder that has fastboot in it
palmbeach05 said:
yes you do. you just told us where you have the files. navigate via cmd to the folder that has fastboot in it
Click to expand...
Click to collapse
now even if i have the necessary drivers (which come with motorola device manager) pc doesnt recognize my phone
also now my phone now says svf.... failed to boot... entering nflash recovery.... battery too low to flash and screen stays like this and phone gets heat (so we can say it's alive?)
The phone has been alive this whole time. I don't know why you said "hard brick" in the title, this has nothing to do with a hard brick. (Do you even know what a hardbrick is?)
You will need to charge the battery using another phone or an external charger. If you feel confident enough, you could try the trick where you strip a USB cable and connect the wires directly to the battery. (No idea what I'm talking about? Time to use search again.)
mike4peace said:
now even if i have the necessary drivers (which come with motorola device manager) pc doesnt recognize my phone
also now my phone now says svf.... failed to boot... entering nflash recovery.... battery too low to flash and screen stays like this and phone gets heat (so we can say it's alive?)
Click to expand...
Click to collapse
That's rsd mode, I think. From there you can flash an full sbf and start over
Enviado desde mi MB860
ravilov said:
The phone has been alive this whole time. I don't know why you said "hard brick" in the title, this has nothing to do with a hard brick. (Do you even know what a hardbrick is?)
You will need to charge the battery using another phone or an external charger. If you feel confident enough, you could try the trick where you strip a USB cable and connect the wires directly to the battery. (No idea what I'm talking about? Time to use search again.)
Click to expand...
Click to collapse
not hard brick? oh thank god, i said so because the phone does nothing
yeah i searched it before and its calldd factory cable, i havent done it yet but i tried usb jig which was a failure. no one owns an atrix around me, so i just need a external charger and right now im onto it
guys, i really appreciate your helps, im very glad to have you here thanks a lot. i will post here the results
man i told you, it's hard brick i guess.. because i charged the battery a bit then i opened the phone and the problem is the same again, it says entering nvflash recovery in about half a second screen goes black
mike4peace said:
man i told you, it's hard brick i guess.. because i charged the battery a bit then i opened the phone and the problem is the same again, it says entering nvflash recovery in about half a second screen goes black
Click to expand...
Click to collapse
What version of Ginerbread were you on and what did you flash via rsd? exact version and exact file please.
mike4peace said:
man i told you, it's hard brick i guess.. because i charged the battery a bit then i opened the phone and the problem is the same again, it says entering nvflash recovery in about half a second screen goes black
Click to expand...
Click to collapse
Here is short explanation what hard brick is:
Hard bricks are more or likely that you won’t be able to fix it. If you get a hard brick, your phone will not be repaired, there will be absolutely no way to without sending it to the manufacturer. This could be from wiping the entire system without flashing a rom, no way into recovery and no way to get it back. This could be also caused from bad installation files, or turning off/removing the battery from your device during the first installation or boot up sequence. Sometimes you can fix a hard brick, but more often than not your device is going to be broken. This is a fix that is required by the manufacturer of the device. Honestly if you get this, it may just be simpler to go get the device replaced instead of even trying to fix it. HOWEVER make sure you go out and read about it, typing in the exact problem and doing lots of research for your specific device as there may be some hope for the device somewhere.
Click to expand...
Click to collapse
Source: "Soft Brick Vs Hard Brick vs Broken" from Techychat.com by Anthony Burkett
Your phone doesn't get recognized by the p c? On linux you can check dmesg after you plug it to see anything, not sure about windows
Enviado desde mi MB860
palmbeach05 said:
What version of Ginerbread were you on and what did you flash via rsd? exact version and exact file please.
Click to expand...
Click to collapse
im not quite sure cause i bought this phone intentionally via ebay-like web site
yanick76 said:
Here is short explanation what hard brick is:
Source: "Soft Brick Vs Hard Brick vs Broken" from Techychat.com by Anthony Burkett
Click to expand...
Click to collapse
okay soft brick it is, but my phone doesnt do anything but show an error screen (and goes)
andresrivas said:
Your phone doesn't get recognized by the p c? On linux you can check dmesg after you plug it to see anything, not sure about windows
Enviado desde mi MB860
Click to expand...
Click to collapse
oh that is a good news, can you please tell this with a bit more detail? but here's what i understood: on linux ( i have ubuntu ) open terminal, after you plug your phone to usb port type "dmesg" and see something
i really appreciate all of your efforts thank you millions times
mike4peace said:
[...]
oh that is a good news, can you please tell this with a bit more detail? but here's what i understood: on linux ( i have ubuntu ) open terminal, after you plug your phone to usb port type "dmesg" and see something
i really appreciate all of your efforts thank you millions times
Click to expand...
Click to collapse
Exactly. try it with sudo, just in case (sudo is for run the command as root, with full privileges).
From there, you can go several ways
andresrivas said:
Exactly. try it with sudo, just in case (sudo is for run the command as root, with full privileges).
From there, you can go several ways
Click to expand...
Click to collapse
i typed just dmesg and there were several lines with words but nothing about the phone. lets say i found a jtag machine or whatever, can it recover my phone?
mike4peace said:
i typed just dmesg and there were several lines with words but nothing about the phone. lets say i found a jtag machine or whatever, can it recover my phone?
Click to expand...
Click to collapse
JTAG depends heavily on your ability to solder tiny surface mount components. Good luck.
Alright. My current phone I was using broke (screen cracked) and I decided to use my old phone, the Droid Razr to get me by until I get a new phone. My Razr was previously rooted on JB when I left it a few years back. It works fine, except it was running slow. It had bootstrap and Safestrap installed. I'm pretty sure at the original time of getting JB on the razr, you had to use bootstrap first and then switch to Safestrap since its safer? However, I forgot this at the time. I wanted to try clearing the cache on the phone to see if it sped it up. However, I guess I uninstalled safestrap and switched it to bootstrap because i used the bootstrap recovery out of ignorance. When I turn on the phone, I get the "Encryption Unsuccessful" message.
I've tried doing the format option it gives but it just restarts the same every time. I've done some researching and it appears I've soft bricked it. I've been reading that the only way to fix it is by using fastboot to wipe the phone to factory settings. I have all the necessary files to do so. I've been working on this for about two days now. However, fastboot does not seem to recognize my phone. I have the drivers installed. When I plug it in normally when it is not in fastboot mode, my PC shows the XT912 under hardware plugged in via USB. But when I put it in fastboot mode, it does not recognize it and it isn't shown in my ADB devices list. What do I do here? I really need this phone to work and I am willing to do whatever it takes to it. I don't care if I have to wipe it/lose root any of that. Please help me. Im not one to make threads of issues that others have but no one elses thread has helped me.
MeltingHolster said:
Alright. My current phone I was using broke (screen cracked) and I decided to use my old phone, the Droid Razr to get me by until I get a new phone. My Razr was previously rooted on JB when I left it a few years back. It works fine, except it was running slow. It had bootstrap and Safestrap installed. I'm pretty sure at the original time of getting JB on the razr, you had to use bootstrap first and then switch to Safestrap since its safer? However, I forgot this at the time. I wanted to try clearing the cache on the phone to see if it sped it up. However, I guess I uninstalled safestrap and switched it to bootstrap because i used the bootstrap recovery out of ignorance. When I turn on the phone, I get the "Encryption Unsuccessful" message.
I've tried doing the format option it gives but it just restarts the same every time. I've done some researching and it appears I've soft bricked it. I've been reading that the only way to fix it is by using fastboot to wipe the phone to factory settings. I have all the necessary files to do so. I've been working on this for about two days now. However, fastboot does not seem to recognize my phone. I have the drivers installed. When I plug it in normally when it is not in fastboot mode, my PC shows the XT912 under hardware plugged in via USB. But when I put it in fastboot mode, it does not recognize it and it isn't shown in my ADB devices list. What do I do here? I really need this phone to work and I am willing to do whatever it takes to it. I don't care if I have to wipe it/lose root any of that. Please help me. Im not one to make threads of issues that others have but no one elses thread has helped me.
Click to expand...
Click to collapse
Windows 7? 8? 10?
Did you tried all usb ports?
Uninstall all moto drivers,reboot computer,install them again.
Here are the newest moto drivers
http://forum.xda-developers.com/showthread.php?p=59139823
Sent from my Razr XT910
Thanks for the quick reply. I'm using Windows 8.1. I did what you asked, and when I turned my phone on after re-installing the drivers, it installed the device normally. It shows this in device manager.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It still wont recognize it in ADB.
MeltingHolster said:
Thanks for the quick reply. I'm using Windows 8.1. I did what you asked, and when I turned my phone on after re-installing the drivers, it installed the device normally. It shows this in device manager.
It still wont recognize it in ADB.
Click to expand...
Click to collapse
That's a common problem with Windows 8,on Windows 7 everything is ok
Sent from my Razr XT910
So that means i cant fix it?
Sent from my SM-T217S using XDA Free mobile app
MeltingHolster said:
So that means i cant fix it?
Sent from my SM-T217S using XDA Free mobile app
Click to expand...
Click to collapse
You can fix it with Windows 7
Sent from my Razr XT910
MeltingHolster said:
So that means i cant fix it?
Sent from my SM-T217S using XDA Free mobile app
Click to expand...
Click to collapse
What is on AP Fastboot screen, complete text?
sd_shadow said:
What is on AP Fastboot screen, complete text?
Click to expand...
Click to collapse
It says AP Fastboot Flash Mode (S)
0A.77
eMMC Info: Size 16GB
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Transfer Mode:
USB Connected
So tried downloading the 6.0 ota. after it installed it, it got stuck in a bootloop. tried doing factor reset and deleting cache and data.
nothing has worked so far.
heres the rub, i never unlocked my bootloader and i cant get into the OS to set the developer options. it seems my only solution is to RMA it. but im hoping maybe there is a hack of some sort.
heres to hoping.
My N9 wouldnt allow me to even attempt to flash anything when it was locked. One of the first things I had to do was a fastboot oem unlock (which also required me to boot into the OS to toggle that developer option). When you flashed 6.0 did you use the "flash-all" script?
WoodroweBones said:
My N9 wouldnt allow me to even attempt to flash anything when it was locked. One of the first things I had to do was a fastboot oem unlock (which also required me to boot into the OS to toggle that developer option). When you flashed 6.0 did you use the "flash-all" script?
Click to expand...
Click to collapse
No it was an OTA update. got the notification this morning and had it install the update. it obviously didnt take. i have not rooted my tablet or done anything like that. its actually the first device ive ever not rooted....
I had the exact same problem. I installed the OTA last night, and now it sits at the boot animation for hours. I tried to wipe cache, but I got an error saying it couldn't mount the partition. I tried to sideload it, and it failed, saying it couldn't mount it. I just (reluctantly) performed a wipe and hopefully that will work, but I'm not optimistic.
Update: no luck. So I permanently deleted a lot of stuff for no reason. =/
Yeah my problem is I can't sideload because my computer doesn't recognize it . I mean this whole unlocking the boot loader from within the OS thing is the stupidest design I've ever seen.....
since i can still get into hboot and fastboot can i side load the OTA? adb isnt seeing it in recovery but it sees it in fastboot.
I was not able to sideload anything. I could see the device, I could start the process, but it would fail every time. I talked to HTC last night and they are going to replace it.
Weirdly, when I was talking with them, they had me try to clear the cache and it actually worked, so I'm going to try and sideload it one more time tonight and if it doesn't work, just swap it out.
I'm caught in the boot loop as well after having downloaded the OTA... I must say, over the past couple weeks I was stuck in boot loops on several occasions, and only after a bunch of restarts would it load fully (and "update apps").
When this device works properly, I have no qualms. But it's incredibly irritating for a $600 tablet to be so shoddy...
stevesmithis said:
I was not able to sideload anything. I could see the device, I could start the process, but it would fail every time. I talked to HTC last night and they are going to replace it.
Weirdly, when I was talking with them, they had me try to clear the cache and it actually worked, so I'm going to try and sideload it one more time tonight and if it doesn't work, just swap it out.
Click to expand...
Click to collapse
Yeah I was able to clear the cache I was even able to format the user data the problem is is there is no OS loaded. At least with the fastboot says under os it says N/A.
HTC said they'll replace it I just have to send it in to them problem is I'm a truck driver so I'm never at home.
-Wes-
Sent from my SM-N910T using Tapatalk
wesmagyar said:
Yeah I was able to clear the cache I was even able to format the user data the problem is is there is no OS loaded. At least with the fastboot says under os it says N/A.
HTC said they'll replace it I just have to send it in to them problem is I'm a truck driver so I'm never at home.
-Wes-
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I had the same problem: even after wiping the cache and formatting the user data, the tablet wouldn't boot, and fastboot said "OS: N/A". However, I went into recovery and sideloaded the OTA file with adb. The update went fine and now my Nexus 9 works again. If you are using Windows and the computer doesn't recognize the tablet you should install the appropriate drivers, I guess (look up "Google USB Driver"). I use a Mac so drivers weren't a problem for me.
xworld21 said:
I had the same problem: even after wiping the cache and formatting the user data, the tablet wouldn't boot, and fastboot said "OS: N/A". However, I went into recovery and sideloaded the OTA file with adb. The update went fine and now my Nexus 9 works again. If you are using Windows and the computer doesn't recognize the tablet you should install the appropriate drivers, I guess (look up "Google USB Driver"). I use a Mac so drivers weren't a problem for me.
Click to expand...
Click to collapse
Will I'll be a mother effer I was able to get it to recognize my device by installing the Samsung ADB driver and from there I was able to sideload the OTA and it is now working.......
The very first thing I'm doing as soon as I actually get it start it is I am going to enable OEM unlock. Everybody who has one of these devices should do that immediately.
Thank you so much man you are awesome
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N910T using Tapatalk
I tried again and it failed. Sadness. Guess I'll just have to swap it out.
I can't figure out how have my device appear when entering "adb devices" ... when i'm in fastboot, i "fastboot devices" and it shows with the serial number. when i'm in recovery, though, "adb devices" shows nada. When I'm in TWRP after selecting "ADB Sideload", my device appears in my Device Manager under Nexus 9, but I can't update driver info to anything that seems to work.
I've got the most up to date drivers via SDK.
Any ideas how I can get my device to be recognized by my PC so that I can sideload the OS?
Thank you all.
thegeneralfamily said:
I can't figure out how have my device appear when entering "adb devices" ... when i'm in fastboot, i "fastboot devices" and it shows with the serial number. when i'm in recovery, though, "adb devices" shows nada. When I'm in TWRP after selecting "ADB Sideload", my device appears in my Device Manager under Nexus 9, but I can't update driver info to anything that seems to work.
I've got the most up to date drivers via SDK.
Any ideas how I can get my device to be recognized by my PC so that I can sideload the OS?
Thank you all.
Click to expand...
Click to collapse
I was having the same problem I installed the Samsung ADB driver, , and all of a sudden my computer recognized my Nexus 9 in a adb mode
Sent from my SM-N910T using Tapatalk
Mine wouldn't show up until I was in recovery and actually picked the "install from adb" or whatever from the menu.
yeah it doesn't actually go into adb mode until you select the sideload option. just as it doesn't go into fastboot untill you are in fastboot.
I was able to download the OTA from android authority. just made sure that the upgrade matched the one that i was upgrading from, i have a galaxy note so when i couldnt get windows to recognize the nexus 9 in adb mode i selected search my computer for the drivers and selected select from installed drivers and out of sheer desperation selected the Samsung ADB driver and sure enough the worked. from there i was able to adb sideload the update and install it and it rebooted into beatiful android 6.0 tablet has been working fine so far with no issues.
First thing i did however was allow unlocking of the bootloader in the developer options.
Edit: nvm
stevesmithis said:
Edit: nvm
Click to expand...
Click to collapse
Yeah I was going to say because I'm the op, I had no access to the operating system either but I was able to accomplish two steps I laid out above and it fixed my problem.
Sent from my SM-N910T using Tapatalk
Also also misread your post. I thought you were saying that unlocked the bootloader before you fixed it. Lol