Thanks to everyone and all their post I was finally able to root my Incredible. Since I was having issues getting mine to root I tried pretty much everything that was said on these forums.
The secret to rooting is the timing of inserting your sdcard before the recovery screen is shown.
Here are the steps that I did to root 2 difficult incredibles.
1) Download the google SDK. You need the adb command for the rooting process.
2) Install HTC Sync or google SDK drivers. It doesn't matter which one you use. You just need the drivers installed and working.
3) Put your phone in USB Debugging mode under the applications config section.
4) Plug your usb in your phone while it is booted normally.
5) Select the disk drive option when prompted.
6) Make sure you can sucessfully connect to your phone using "adb shell" command. If this does not work you will not be able to go any further. This means drivers are not installed correctly.
7) Power off your phone. Doesn't matter how. Battery removal, press power off button etc...
8) Remove your SD card.
9) Press Volume down and power at the same time.
10) When the phone is at the Bootloader menu press Volume down and Highlight the Recovery option. Do not select it yet.
This is where the rooting process gets tricky.
11) Make sure your usb is plugged in.
12) Make sure you dont have your SD card in your phone.
You have to insert your SD card in your phone while the recovery mode is loading. There is a specific time window that you must do this. By using different SD cards they take certain time to initialize during the loading. This is why some SD cards work all the time and why others have to be inserted at a certain time
13) Go ahead and get your "adb shell" loop running. It should show "error: device not found"
14) Bring up a clock. You will need this to keep track of when you inserted your SD card during the recovery boot process.
15) Press the power button to select Recovery and start counting the second hand on the clock.
16) Start at 1 second and insert your SD card. You will wait until you hear windows beep when its loading the drivers for the USB device. After the 10 seconds your adb loop screen should show the following if it worked: "exec '/system/bin/sh' failed: No such file or directory (2)"
17) If it does NOT show this you will need to remove the battery and SD card and go back to step 14.
18) Increment your time by a second. So for the 2nd try insert the SD card after 2 seconds have past. So far on my walmart PNY 2gb SD card on 2 incredibles it takes around 5 to 6 seconds of waiting before I can insert my SD card. If you get to 10 seconds you need to restart and try again, but this time try half seconds increments.
When I select the Recovery option and the phone is loading I will see the white splash screen near the bottom kinda flicker a little bit and have a small horizontal line distort across the screen. That's about the same time I insert my SD card.
If you get the "exec '/system/bin/sh' failed: No such file or directory (2)" message looping in your shell prompt, Congrats you have access to the recovery shell. You will need to follow these steps to fully root your phone.
http://www.unrevoked.com/rootwiki/doku.php?id=public:adb_in_recovery
Thanks to everyone in these forums offering their input. Without your input I wouldn't be able to root my phone.
LOL
I guess great minds think alike:
http://forum.xda-developers.com/showthread.php?t=703589
^ I posted that this morning.
At first I thought it was you reposting or someone poking fun at these types of threads.
You guys say like the same thing. Hopefully that means this is a good "update" to the process and people will have a slightly easier time.
I have Froyo on my Droid so am not too eager to get my Incredble rooted, but I have been following along.
I'm going to get my timings down tonight and post a 3rd thread on this!!!1
dreamersipaq said:
I guess great minds think alike:
http://forum.xda-developers.com/showthread.php?t=703589
^ I posted that this morning.
Click to expand...
Click to collapse
lol yeah, I guess the method works
seanmcd72 said:
I'm going to get my timings down tonight and post a 3rd thread on this!!!1
Click to expand...
Click to collapse
I'm going to use an atomic clock to time and root my DI and report back on the decay rates of Polonium!
I appreciate users' attempts to refine this process, but I'm sticking with the old: insert the card right before white-switches-to-black . . . I tried timing and found myself slamming the sdcard card into the slot trying to make my targets, and that ain't not good for the DI.
rynosaur said:
I'm going to use an atomic clock to time and root my DI and report back on the decay rates of Polonium!
I appreciate users' attempts to refine this process, but I'm sticking with the old: insert the card right before white-switches-to-black . . . I tried timing and found myself slamming the sdcard card into the slot trying to make my targets, and that ain't not good for the DI.
Click to expand...
Click to collapse
LOL, well that's your own fault
Don't be so rough with her.... Abuser! Gentle, there is no reason to slam.
And it's still better then the click in and out method.
I just powered on the nook, and then it immediately told me that a new software update is being installed. This occurred before the rainbow nook logo. Since I already had 1.01, that doesn't make sense. As well, I hadn't had wifi on the last time I was using the nook. I very recently had 1.0 and was rooted, then updated to 1.01 and auto nootered. I had performed both /system and /data wipes. I can't help but think that somehow, the failed boot counter was incrementing each time I powered the nook on. Either that, or something along those lines. If I'm not using the nook, I generally power it off instead of leaving it in standby. Although not a definite, I would say it has been roughly 8 power offs since I had updated to 1.01. I'm tempted to try that out once I restore this back to they way it was.
I noticed a couple of other people in the forums have run into this.
Incriminified said:
I just powered on the nook, and then it immediately told me that a new software update is being installed. This occurred before the rainbow nook logo. Since I already had 1.01, that doesn't make sense. As well, I hadn't had wifi on the last time I was using the nook. I very recently had 1.0 and was rooted, then updated to 1.01 and auto nootered. I had performed both /system and /data wipes. I can't help but think that somehow, the failed boot counter was incrementing each time I powered the nook on. Either that, or something along those lines. If I'm not using the nook, I generally power it off instead of leaving it in standby. Although not a definite, I would say it has been roughly 8 power offs since I had updated to 1.01. I'm tempted to try that out once I restore this back to they way it was.
I noticed a couple of other people in the forums have run into this.
Click to expand...
Click to collapse
Easy way to find out. Power off/on a few time. Plug it into your pc and pull the file:
Code:
adb pull /rom/devconf/BootCnt
Open with notepad and see what the boot count is set to.
Or use a file explorer that can see system files (Root Explorer) and open that file on the NC and check the book count.
HotShotAzn said:
Easy way to find out. Power off/on a few time. Plug it into your pc and pull the file:
Code:
adb pull /rom/devconf/BootCnt
Open with notepad and see what the boot count is set to.
Or use a file explorer that can see system files (Root Explorer) and open that file on the NC and check the book count.
Click to expand...
Click to collapse
Thanks for that. I restored most of everything, powered off a few times, and checked it out with root explorer. It shows the count as 0. Hmmm, I guess it's not that.
Hey Folks,
I have been trying for days now to get my (semi) rooted Galaxy Tab, back to some assemblence of functionality.
I have heimdall and Odin, and have access to Clockwordmod Recovery v3.0.0.5; however I am unable to use the rom I want (spacemoose1-hc-cdma-A25-110610) because every action I select in recovery, that involved the SD Card, gives me the error message "E: unable to mount /sdcard" and such.
When not in this mode, the Tab bootloops between the Galaxy Tab opening and the Verizon Wireless splash.
I have tried to flash back to recovery, unsuccessfully, using the 1800_VZW_Stock_EC02 files. At the end of that process, I see 'Galaxy Tab - Samsung', then a fuzzy static-looking screen for a second or so, and then just black screen.
Just turned in circles at this point. Need some assistance.
I have the same error, i tried to install several rom and it is always the same, my internal sd card is not mounted......
If you find something please gives us the solution.
Good luck...
that makes three of us. I can mount USB but only view. I have SU and Root Explorer has SU rights but I cannot mount anything R/W.
-Alex
Ok, so I ran the SuperoneClick exploit and now Root Explorer shows the file system as being R/W but I cannot mount the SD card for copying over files.
do any of you have an external reader... I had this issue few weeks back then forgot I can plug the sd card into another reader .. copied the file and was back in action.
Thanks, I considered that and while it's a good work-around I would like it to work as designed.
I got a new tab today due to my accelerometer not working. Everything is ok so far. I will still need to root and add some other apps. I'll see if I can nail down the root cause during those tasks.
Its what i had todo when i was flashing my gt i9000 nothing worked but bring it back to factory then started a new then everything was fine...
Sent from my GT-I9000 using XDA App
Here, a link which could help you : http://forum.xda-developers.com/showthread.php?t=1117142
and this one to learning and doing previous link: http://forum.xda-
developers.com/showthread.php?t=537508
becarful with your tab because mine crash completly during an only flash of boot.bin with Odin (before i removed bootloader to apply a "fastboot devices" as described in the first link), i will have an other one today.
Good luck
editi guess sdcard is incorrect/confusing for my situation, it's the entire system up to root folders is stuck in a read-only type state.
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected]ost #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
plasticsoldier said:
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected] #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
Click to expand...
Click to collapse
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
plasticsoldier said:
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
Click to expand...
Click to collapse
I would suggest trying to restore down to WebOS 3.0. In that procedure you literally wipe EVERYTHING on the internal partitions in novaterm and start from absolute scratch. Therefore, if it a software issue you could solve the problem. However, if it is a hardware issue, you'd be kinda screwed.
Yeah, none of the methods I've ended up finding about this problem or other bricked problems are working at all.
i checked at work when i bought it, which of course the 11th was the year mark... but I do have android installed so even if i can get any chance of them honouring it so close they'll probably be like "oh you have android, that'll be $$$ for us to do anything. thanks!"
So I guess I now I have a paperweight with some features.
cdzo72 said:
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
There is a thread in the General forum about how to restore and downgrade. Have you tried that thread ? It is usually a great way to try and get that last restore before sending it back to HP.
73 de VE6AY
Sent from my HP Touchpad, running the latest CM9 nightly, from the XDA Premium App
how are you adding and deleting files when in android? which version of android do you have installed? have you tried different rom versions? have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to? it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard? are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android? have you run "fix permissions"? Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
sstar said:
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
Click to expand...
Click to collapse
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
cdzo72 said:
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the answer, this would tend to suggest that the problem is software based corrupted or otherwise. I am trying to find a program that will allow me to read/format the Android partition on my windows computer and will let you know if come up with anything.
Regards
i guess i should change the title slightly.. it's not sdcard, but basically the entire touchpad contents. go to root and delete whatever i want and it doesn't matter. connect it and format with windows and it doesn't actually matter.
haxin said:
how are you adding and deleting files when in android?
Click to expand...
Click to collapse
i've added and deleted just by using mtp. i've also deleted the files on the android side with the video player (vplayer) i've installed es file explorer (which after restart is gone) and deleted with that. i've also gone into webos and installed internalz pro and deleted files that way, which it then seems to work until i of course do anything related to restarting.
some of the files i've put on, i've had it recognize briefly. so for the video file, start it, then it gets really choppy/glitchy playing it. so stop it, go back into the vplayer and it's back to the old stuff
which version of android do you have installed? have you tried different rom versions?
Click to expand...
Click to collapse
android version 4.0.3. nothing else will install. if i add files while in android, when i boot into cwm they are gone. if i mount usb in cwm and add them they stay briefly but when i try to flash them they fail.
have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to?
Click to expand...
Click to collapse
i have not tried adb yet, just not as familiar using it properly, i will give it a try though.
i am using windows 7 on my laptop currently. i do have a pc upstairs that i barely use that has vista, but i don't know how that would make a difference to the touchpad
it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard?
Click to expand...
Click to collapse
yeah as i put above i guess saying sdcard was a bit confusing/misleading (my bad, sorry!), i didn't really know what else to call it at the time or how to explain myself properly at first.
are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android?
Click to expand...
Click to collapse
i can move/delete/modify anything which has absolutely no effect to the device. i've used es file explorer and gone up to root and deleted everything and the system runs fine. says the system is empty with lots of free space (its the 32gb model) but restart or even go into recovery and everything is once again there.
have you run "fix permissions"?
Click to expand...
Click to collapse
i've run it a few times. just acts likes it's working and then says done. i've even gone into the mounts and storage in cwm and formatted sdcard/cache/data/system. does nothing at all in the end of things
Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
Click to expand...
Click to collapse
it was just something to try to get somewhere right. it never gets past 12%. always fails to reboot.
I am currently letting the battery drain and see if it dying and then being charged will do anything. probably not. but who knows. i talked to a "tech" on the chat support (i never mentioned android) who told me that having preware installed in webos causing it to become corrupt and they "don't knowledge of preware installed devices" exact words. no idea what that means haha don't have knowledge, don't acknowledge...
anyhow. i've not quite given up. i just don't really see it turning out any differently from the previous times. i do appreciate all the feedback and help very much though
ok so heres what I would try. First try flashing a new fresh rom. download one that you want to your computer like cm9 nightly or aokp or whatever you feel like. then boot into CWM recovery connect the touchpad to the computer via usb. then connect to the touchpad with adb. I'm not sure how to do this in windows because it's been so long since I've done it on a windows box, I always use linux.
adb has alot of options, you can move files to and from the device, you can uninstall or install app packages, and more. this way you can adb push the rom .zip to the touchpad's sdcard while youre in cwm recovery. this way you dont have to reboot the touchpad and risk having the file disappear, you can just go to 'install zip from sdcard' and then 'choose zip from sdcard' in cwm recovery after you adb push the rom, you should see it in the folder you pushed it to on the sdcard.
If you arent familiar with how to use adb from the command line or the terminal this might not make alot of sense and i dont know how better to explain it than that. Also yes windows 7 vs windows vista does make a difference there are issues with novacom installing properly, that's why you would have problems running acmeuninstaller or acmeinstaller2. if you look around you should find some videos or how to's that can probably explain it better. Hope this helps.
http://www.webos-internals.org/wiki/Novacom_with_Windows_7
http://forums.webosnation.com/webos-internals/295881-webos-doctor-12-issue-fixed-5.html
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
ve6ay said:
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
Click to expand...
Click to collapse
Probably the best suggestion yet given that everything else has been tried.
Good luck.
****EDIT****
Before you attempt the step above I have just noticed a difference between between cwm and. TWRP2.2 which I have installed on my Touchpad via goo manager. If I open recovery via goo manager and then select wipe it gives me 4 options cache, davlik, factory reset AND system which i think says will remove your rom . I don't see the forth option available with the regular cwm/clockwork. Just a thought.
All the best with whatever you try next.
sstar said:
Probably the best suggestion yet given that everything else has been tried.
Good luck.
Click to expand...
Click to collapse
this would work, however you have to fix you novacom/novaterm issues on your windows machine before you'll be able to do any of this. the reason acmeuninstaller, acmeinstaller2 arent working is likely because youre on a windows7 64bit box and Palm-sdk, the novacomd.exe, noverm.exe, and javaruntime apps and drivers arent setup right. just make sure you have the proper javaupdates on your computer then you can install preware in webos, preware has some nice tools that will delete the entire android install partitions, one is called 'remove android' and the other is called 'tailor' you run them from within webos. after you do that then in webos you should do a full device reset. you'll find it in the "info" tab under settings in webos. this will delete and reformat the whole /media ,(aka sdcard) partition. so you will lose all the files you have stored on both webos and android. that format will take a long time probably like 30 min or more. after thats done. reboot the hp and run webosdoctor. now i know for sure this will work because ive done it on mine. remember to put the touchpad in developer mode in webos first to install preware. you can do that by typing webos20090606 into the webos search bar and hitting enter. I'll put links from my box.com accou t to everything you need.
https://www.box.com/s/479acdb6ef9c99fc7b92
https://www.box.com/s/1aed4722990aad251570
edit: also I'm not sure if youre on the 16gig 32gig or 64gig pad, the webosdoctor that i linked is for 32gig wifi only US version. if thats not what you have then youll need to get the doctor for for specific touchpad. or you could create a webosmetadoctor but thats a whole nother project.
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
plasticsoldier said:
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Click to expand...
Click to collapse
ok no one will be able to help you fix this issue unless you give complete details of the problems. when you say " novacom/novaterm stuff doesn't work" we cant really help specific error details is what i need. I dont mind helping you fix this but you have to be a little more specific on exactly what,where, and how youre installing and running and mounting apps and directories.
your problem IS fixable but you need to slow down and really do things exactly step by step.
Ok so back to ./adb. now when you boot in to CWM recovery on he touchpad DONT do anything in CWM just plug it into the computer. do not mount it as a usb storage and dont mount or unmount the sd partition LEAVE IT.
you can then use ./adb from the command line or terminal on the computer to move the files to the touchpad' or install apk's uninstall apk's you name it. This will require that you know some linux terminal commands. for example to move a new rom zip to the internal sd card or into any other folder you can use ./adb push command to run a root shell on the android device itself you can use ./adb shell and then change folder and file properties from readonly to rw. this can all be done while the touchpad is patiently waitng in CWM recovery. this way when youre done installing or uninstalling apps from the device and moving flash zips to it, you can disconnect the .adb connection with ./adb disconnect or just type exit from the terminal till it closes. unplug it then you will be able to pick up the touchpad and install zip from the sdcard, keep in mind you dont want to choose 'apply u[date from sdcard' you want to use the 'install zip from sdcard option' you can read up more on how adb works. it is probally the most important part of hacking android.
with that being said. novaterm is the palm webos version of .adb. this is why when you boot into webos recovery to do things like acmeinstaller and acmeuninstaller2 the novaterm novacom and novacomd apps have to be installed correctly on the computer or else you wont be going anywhere fast. some screenshot examples of how it should appear below.
https://www.box.com/s/432e63a83215f00eea6a
https://www.box.com/s/970bc29542a05f98f036
https://www.box.com/s/63c0f656e8354f7f2d6a
https://www.box.com/s/cbe3266467ae8e3ebabe
https://www.box.com/s/005e56a61a178dd17fa4 some better resolution images.
Plasticsoldier said
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Yes there is
Firstly tailor does exist, it is a beta and the facility to dl must be enabled.
Read this and scroll down to Enabling beta test feeds and follow the instructions , when you get as far as using the Linux command you CAN copy and paste thank God.
http://en.m.webos-internals.org/wiki/Testing_Feeds?wasRedirected=true . After that reboot into Webos and launch preware. Go into managed feeds as per the instructions in the link above and install Tailor. Reboot again and the app will work. It looks very good actually.
But before attempting to actually use Tailor please read the article I have posted below it is only 7 pages long but will explain how to use Taylor properly as it is a powerful tool.
http://forums.webosnation.com/webos...partition-filesystem-editor-beta-testing.html
I have done all of this , this morning so if you have any problems pm me or ask in this thread.
I sincerely hope that this helps, it should be the answer to your problems.
@haxin: sorry, wasn't trying to be unhelpful when everyone is being helpful to me. I shall be more detailed in future responses. I think i was getting frustrated and had had a busy exhausting day so it didn't help me come across clearly/properly.
OK, so I had preware installed already, so I removed it, went into developer mode, used the linux commands, reinstalled preware, added Tailor.
(i've done this a few times, because I didn't remove the cable after doing the linux commands for preware, then i accidentally hit the wrong buttons and it connected to 'usb drive' mode and wouldn't connect on the pc side and got stuck on the "ow disconnected me properly next time" screen).
So it gives me the following options
USB (media)
Android (system)
Android (cache)
Android (data)
Unused Space
the 'usb media' starts mounted and will mount again if unmounted. If I use 'check filesystem' it'll pass. So then I try 'delete partition' which pretends to delete, then it takes me to the unused partition which is still at 16mb. so i try to use "check filesystem' again and it fails. try repair and it fails as well
I've tried mounting the android parts just to see, they just sit there processing that they are trying to mount. trying to delete or anything else fails as well.
and now after trying things, any of the 'cards' will try to open and just sit there grey. and with my usb cable not plugged in it still is giving me the option to enter usb drive mode. and with this i have to restart and go through the steps again of adding Tailor which is getting tedious.
I restarted, went through the motions to get back to Tailor. trying out resizing just to see how that goes. So far 15%. not sure what will happen when done, but we will see.
This is getting long, so i'll end this part and update on anything and also try to familiarize myself with adb a tad more
Sorry for the novel, but I want to show the whole backstory to rule out quick fixes... I have an m7 a coworker asked me to take a look at. I don't know the full story, but apparantly he didn't do anything to the phone, he just woke up one day and it was suddenly broken. I'm not sure whether I believe him but I digress...
When I got it, about half the time the phone would just hang at the htc logo. If you power it off and back on, the other half of the time it would automatically bring itself to the bootloader. The bootloader said Tampered, locked, and security warning at the top.
I fought with it for a while, factory reset did nothing. I used htcdev to unlock the bootloader, and flashed twrp 2.8. Twrp was full of errors saying can't mount /data, can't mount /system, can't mount /cache etc. any time I tried to do anything it would keep complaining that it couldn't write to /cache/log/whatever.
Trying to format / wipe any of the partitions would fail. When I went to the mount screen, it showed "internal storage: 0mb" and clicking on that let me choose from internal storage 0mb and dgs USB 0mb.
Trying to adb side load in twrp failed as well, it would just say side load failed as soon as I entered the side load screen.
I installed twrp 2.3.6, and it did the exact same thing.
I then installed CWM touch 6.0.4.8, and it had basically the same errors about not being able to mount any partitions. The only difference with CWM was that the ADB side load would start, but trying to actually send any files to it fails. (Sending the file from the computer counts up and gets to 100%, but as soon as it gets to 100% it says the file is invalid (don't recall the exact error)
I finally found this link: (too new to port links, but google htc recover corrupted partitions, it's the first hit, from android revolution blog) and followed those steps, but when I run mkfs.ext4 for mmcblk0p36, 35 or 34 it complains that mmcblk0p36 is not a block special device.
I opened up adb shell, and ran ls /dev/block, it shows some mmcblk0, mmcblk0p1, mmcblk0p2, etc all the way up to p21, but there's nothing higher than 21. When I run that same command on my own m7 (running cm11) it has all the way up to p37.
I've tried to find more info about what's going on from there, but the only people I've found with similar problems all sent their phones back for warranty, and this one is out of warranty now.
So long story short, at this point am I right that it looks like a hardware fault and I'm sol? Or is there anything I'm missing about why half of those blocks would be missing? Do I stand a chance of remapping /data /system and /cache to lower numbered blocks or am I out to lunch?
This post was long enough without attaching logs or exact error messages, but if anyone thinks they might be of value let me know and I can include them.
Thanks!
joetomato said:
Sorry for the novel, but I want to show the whole backstory to rule out quick fixes... I have an m7 a coworker asked me to take a look at. I don't know the full story, but apparantly he didn't do anything to the phone, he just woke up one day and it was suddenly broken. I'm not sure whether I believe him but I digress...
When I got it, about half the time the phone would just hang at the htc logo. If you power it off and back on, the other half of the time it would automatically bring itself to the bootloader. The bootloader said Tampered, locked, and security warning at the top.
I fought with it for a while, factory reset did nothing. I used htcdev to unlock the bootloader, and flashed twrp 2.8. Twrp was full of errors saying can't mount /data, can't mount /system, can't mount /cache etc. any time I tried to do anything it would keep complaining that it couldn't write to /cache/log/whatever.
Trying to format / wipe any of the partitions would fail. When I went to the mount screen, it showed "internal storage: 0mb" and clicking on that let me choose from internal storage 0mb and dgs USB 0mb.
Trying to adb side load in twrp failed as well, it would just say side load failed as soon as I entered the side load screen.
I installed twrp 2.3.6, and it did the exact same thing.
I then installed CWM touch 6.0.4.8, and it had basically the same errors about not being able to mount any partitions. The only difference with CWM was that the ADB side load would start, but trying to actually send any files to it fails. (Sending the file from the computer counts up and gets to 100%, but as soon as it gets to 100% it says the file is invalid (don't recall the exact error)
I finally found this link: (too new to port links, but google htc recover corrupted partitions, it's the first hit, from android revolution blog) and followed those steps, but when I run mkfs.ext4 for mmcblk0p36, 35 or 34 it complains that mmcblk0p36 is not a block special device.
I opened up adb shell, and ran ls /dev/block, it shows some mmcblk0, mmcblk0p1, mmcblk0p2, etc all the way up to p21, but there's nothing higher than 21. When I run that same command on my own m7 (running cm11) it has all the way up to p37.
I've tried to find more info about what's going on from there, but the only people I've found with similar problems all sent their phones back for warranty, and this one is out of warranty now.
So long story short, at this point am I right that it looks like a hardware fault and I'm sol? Or is there anything I'm missing about why half of those blocks would be missing? Do I stand a chance of remapping /data /system and /cache to lower numbered blocks or am I out to lunch?
This post was long enough without attaching logs or exact error messages, but if anyone thinks they might be of value let me know and I can include them.
Thanks!
Click to expand...
Click to collapse
I don't know if the Unbrick Project would help or not. At least take a look at it to see if your situation might fit the criteria.