Hey guys, I am here because I was incredibly stupid. I have no idea how this could have happened.
I tried updating the TWRP to the latest version with Goo manager, unfortunatly, it deleted my old one without flashing a new one. The ADB drivers didn't really work, so I tried flashing the twrp.img via the app "flashify". Problem is, I flashed the .img as a boot image and not as a recovery image, no idea how I could overlook that.
So now my Touchpad only boots into the webOS download mode and shows an error if I try to boot regularly (obviously). palm.com/ROM it says.
So my question is, how do I flash the correct boot image again? Last time I have flashed the boot image of the touchpad was when Ice cream sandwich wasn't even announced, I have no idea how to fix my mums tablet.
So it would be so great if you could help me, I'm feeling so stupid and quite helpless. Thanks so much
Axe Homeless said:
Hey guys, I am here because I was incredibly stupid. I have no idea how this could have happened.
I tried updating the TWRP to the latest version with Goo manager, unfortunatly, it deleted my old one without flashing a new one. The ADB drivers didn't really work, so I tried flashing the twrp.img via the app "flashify". Problem is, I flashed the .img as a boot image and not as a recovery image, no idea how I could overlook that.
So now my Touchpad only boots into the webOS download mode and shows an error if I try to boot regularly (obviously). palm.com/ROM it says.
So my question is, how do I flash the correct boot image again? Last time I have flashed the boot image of the touchpad was when Ice cream sandwich wasn't even announced, I have no idea how to fix my mums tablet.
So it would be so great if you could help me, I'm feeling so stupid and quite helpless. Thanks so much
Click to expand...
Click to collapse
You will want to run acmeuninstaller
followed by WebOS Doctor
and then moboot, CWM, CM10.2
some help with fixing a situation like yours is here http://forum.xda-developers.com/showthread.php?t=1426244
latest files can be found here: invisiblek.org/tenderloin/
Holy ****, so I do have to uninstall everything, delete the partitions and then repartition and reinstall everything? Isn't there a way just to flash moboot again or something?
Axe Homeless said:
Holy ****, so I do have to uninstall everything, delete the partitions and then repartition and reinstall everything? Isn't there a way just to flash moboot again or something?
Click to expand...
Click to collapse
to install moboot you need to get a copy of it on the touchpad in the cminstall folder and then run
novacom boot mem:// < ACMEInstaller3
to get moboot there you need to see if you can boot into CWM.
Get a copy of update-CWM6_tenderloin-20121215.zip and extract uImage.ClockworkMod
on your Windows PC in command window:
cd C:\Program Files\Palm, Inc
novacom boot mem:// < uImage.ClockworkMod
go to mounts and storage
mount /boot
mount /sdcard
mount USB storage
create a directory cminstall
you can copy CWM, moboot and then try ACMEinstaller3
E:
Well, I can get into CWM, but I can't mount anything, error mounting /boot and /everything else, and it doesn't do anything when I'm mounting USB storage. damn. Any other tipps? I'm really grateful for your help, but I would rather first exhaust the options before killing everthing and then rebuilding it.
Axe Homeless said:
E:
Well, I can get into CWM, but I can't mount anything, error mounting /boot and /everything else, and it doesn't do anything when I'm mounting USB storage. damn. Any other tipps? I'm really grateful for your help, but I would rather first exhaust the options before killing everthing and then rebuilding it.
Click to expand...
Click to collapse
If you are getting mount errors then my guess is your partitions are messed up and should rebuild from scratch. Only other think I would try is just acmeuninstaller and see if you can get webos to boot after that.
Related
SO i was running nook color version 1.1.0 and i used the autonooter to get clockwork installed. I then tried to use the monster rootpack to install phiremod but after it says install is complete i rebooted but now every time i reboot it goes directly to clockwork and i cant get it to boot up normally. is there anything i can do besides a restore to stock to install phiremod/cm7 or exit recovery? BTW i did remove the monster sd card so thats not the reason its booting that way....
When booted to CWR, use adb:
adb shell
Check that rom is mounted with:
mount
You should see /rom somewhere in the returned result.
If it's mounted, do:
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
If not:
mkdir /rom
mount /dev/block/mmcblk0p2 /rom
Then use previous command.
If that doesn't help, you can always flash my cwr remover .zip, found on my nook color restore to stock thread.
Sent from my HTC Desire using XDA App
thanks im going to try that right now.
So i am trying to run adb but it says device not found and i cant figure out how to get the device to mount
I had the same thing happen. In recovery, install the zip file in this post to remove recovery and keep it rooted. You will then be able to reboot normally.
http://forum.xda-developers.com/showthread.php?t=914690
I read that it does that with autonooter 3.0. What you need to do is reboot normally after flashing recovery (don't reboot into recovery immediately after flashing). Afterwards you can reboot into recovery.
Hello guys,
I had the same problem, but with Team Win Recovery
I tried to remove TWR folder in sdcard, wipe Cache, Dalvik cache and even factory reset.
I installed a new rom, and as last attempt i tried to wipe all system tree, but nothing happen.
I tried to fix following the list showed in this post, but I'm not able to mount "mmcblk0p2".
Any ideas? There is a TWR remover ?
Advance thank for helps.
krisslake said:
Hello guys,
I had the same problem, but with Team Win Recovery
I tried to remove TWR folder in sdcard, wipe Cache, Dalvik cache and even factory reset.
I installed a new rom, and as last attempt i tried to wipe all system tree, but nothing happen.
I tried to fix following the list showed in this post, but I'm not able to mount "mmcblk0p2".
Any ideas? There is a TWR remover ?
Advance thank for helps.
Click to expand...
Click to collapse
Not really sure what you are saying was your problem. But I have a lot of solutions to booting problems in my nook color tips thread linked in my signature. See items A8 and A12. And there is my partition repair thread.
Sent from my BNTV400 using Tapatalk
Hey guys, I posted this over at Rootz but it's not getting any action. I really appreciate the help...
Hey Gents,
I couldn't wait any longer so I installed Alpha2 on my Touchpad and was happy as a pig in sh*t after spending about two days on it. Then I got curious about the Nightly builds and came across a problem that is killing me. I can not boot into Recovery mode. I've tried everything, I've searched up and down on the forums but it seems like everyone can at least get into recovery. Moboot has "boot webOS Recovery" option but no "boot clockworkmod". I've tried through ROM Manager, I've tried through ROM Toolbox, etc. Nothing. I uninstalled the Alpha2 through ACMEUninstaller and then reinstalled the latest Nighty Build through ACMEIntstaller2 with the other files needed for Android. Nothing. I tried booting into recovery on my S2 Skyrocket, no problem. I'm pulling my hair out here.
Any ideas?
here's exactly what I did:
1- installed novacom driver
2- copied ACMEInstaller2 over to the Palm, Inc folder in Program Files
3- plugged in Touchpad via USB and copied the gapps, Cyanogenmod9, recovery_update_tenderloin and moboot zipped files to my folder I created "cminstall"
4- unplugged TP, put it in USB recovery mode, reattached it via USB and ran the command prompt
5- Ran perfectly smooth, played with Android for a few days.
- ROM Manager is installed, Google apps work perfectly, dual boot is alive and well, etc.
everything works great but RECOVERY. When I reboot and hit recovery or when I go straight into ROM Manager and hit recovery, I end up at the boot screen.
another weird thing... when I checked out my files in "cminstall" via Astro, the recovery one was still there as a zipped file. All the other files were gone. Not sure if this means anything but I figure the more info the better.
I am not totally sure on this so may get blasted, but check the filename of the zip in the cminstall folder. I had this impression that the zip files needed to start 'update-' for AcmeInstaller to handle them. I think some of the cwm zips have other filenames, but it doesn't hurt to rename and try AcmeInstaller2 again.
You probably need to clear up some room in the boot partition. I had the same issue with initial install of cm7. Recovery wouldn't flash properly because there was not enough room. Make enough room in your /boot and flash through ACMEinstaller.
Sent from my PG06100 using Tapatalk 2
Ok, so you mean on the Touchpad I need to get rid of a bunch of data? Like where I store music and movies and all that? I have a HUGE amount of free space on there. Easily 60% of the 32GB is free.
on a side note, would I be able to flash continuously through ACMEInstaller2 rather than CWM Recovery? Like say an official beta comes out, could I just run the command lines without all the other zip folders right over the version installed??
copene said:
Ok, so you mean on the Touchpad I need to get rid of a bunch of data? Like where I store music and movies and all that? I have a HUGE amount of free space on there. Easily 60% of the 32GB is free.
Click to expand...
Click to collapse
in your /boot folder you may have too much stuff... do some reading and delete everything that shouldnt be there
copene said:
on a side note, would I be able to flash continuously through ACMEInstaller2 rather than CWM Recovery? Like say an official beta comes out, could I just run the command lines without all the other zip folders right over the version installed??
Click to expand...
Click to collapse
you could but why would you want to
yup, that was the problem! the CWM file I DL'd from precentral didn't start with "update". I grabbed the file directly from Rootz and it installed perfectly. Thank you so much, everything is working as it should now.
Thanks a lot guys.
In your /boot, if you wanna just have the stuff for WebOS and Alpha2, you should have the following in your /boot:
Folders:
bin/
dev/
etc/
lib/
lost+found/
proc/
realroot/
sbin/
sys/
usr/
Files:
boot-genesis.tar.gz
boot-images.tar.gz
boot.bin
config-2.6.35-palm-tenderloin
genesis-update.xml
image-update.xml
moboot.default
moboot.splash.CyanogenMod.tga
moboot.splash.webOS.tga
moboot.timeout <== You might not have this.
System.map-2.6.35-palm-tenderloin
uImage
uImage-2.6.35-palm-tenderloin
uImage.ClockworkMod <== You apparently don't have this
uImage.CyanogenMod
uImage.moboot
uImage.webOS
updatefs-info
If you have other files in there aside from those listed, feel free to delete the extras. Your /boot partition is only 30 MB, so you need to have some room left in there. The uImage.ClockworkMod is about 5 megs, and if you have nothing BUT WebOS and CM9 installed (I have the last official nightly), you should have 22 megs or so used.
Hope that helps, mate.
Hi,
My new HTC One's vibrate isn't very strong, so the vendor is sending me a new one. I'm rooted though, so thought I'd better start looking at ways to "undo" the root. When looking at options on the HTC One Toolkit, I "somehow" did something to my phone. All I "Thought" I was doing was getting the version information off it, so I could find the correct RUU, but when trying to reboot after that, it just kept going back to the bootloader with some error like "re-locked" and "security warning".
After extensive searches, I learnt I could flash the unlock.bin file again to unlock it. Done...but then it just sat at the "Slim" logo [ROM I was running]. I could still boot into Recovery (CWM) and tried clearing cache and dalvik - but still sat at the "Slim" logo. So I started digging in. I tried to mount the SDcard in CWM, but wouldn't mount. So flashed TWRP, but same thing there. When I try to mount anything, the only folder it will let me select is "System" - nothing else mounts and my "Storage" reads "0 bytes".
So I thought maybe I'd lost root, everything was Read Only and that's why I couldn't write to anything. So using the HTC One toolkit, flashed SuperSu. Still same thing.
I did manage to adb the slim ROM and the gapps to /sdcard, but when I tried to install, nothing would "mount" in order to install it...so all I got was errors saying install failed, and a bunch of directories that couldn't be "mounted". In summary I've done the following with Fastboot:
Flashed Unlock file
Flashed boot.img (from Slim Rom)
flashed Recovery (CWM first, but now TWRP)
Fastboot Clear cache
But after all that, when I boot into Recovery, nothing mounts and I can't get past this. Any help you could provide would be MOST welcome!
Thanks in advance.
-- Edit --
Disregard - got it finally. Using TWRP, I formatted the data directory, and it was writeable again. Not sure if it helped, but I then resubmitted everything I did in the list above, booted to Recovery, and was then able to adb the ROM and Gapps over and it installed fine. Phew.... Still need to figure out how to get it all back to stock though. That's my next task.
Hi developers. I am sorry for posting this. I spent the last week trying to solve it by myself with no hope. This is my second time installing something on a phone, but it is my only phone, so I beg anyone for a help...
-What I did:
Some days ago I downgraded to this ROM C5503_10.1.1.A.1.310_GLOBAL-LTE.ftf to use DoomLord rooting script. I did it with flashtool for linux and I applied his .bat step by step in the terminal since windows would not detect my phone.
It worked. I had root for some days, but I was still annoyed by sony default android. So I decided to install Cyanogenmod.
I unlocked the device with sony official system and wen't straight to this instructions, before the first reboot
wiki.cyanogenmod.org/w/Install_CM_for_yuga
I booted succesfully in CWM, followed everything as it says there. But that's where weird things happened:
-The problems:
-The backup
I tried, it wouldn't mount /sdcard. Since I don't understand much about this, I thought it was normal. The next choice was sdcard1, I backed up there. Or so I thought...
-The factory reset
I factory reset, again, not mounting sdcard. Here is the message that shows when I try this now:
can't mount /data!
Error mounting /sdcard.android_secure
Skipping format...
Data wipe complete.
Since it said it is complete, I went on installing the zip file from my sdcard1. Both CM 10.2.1 (dogo, the right one for my phone) and the appropriate GAPPS.
Now it loops on the CM loop animation and I have to remove the battery...
-The restore problem
It still boots on the recovery mode. So I tried recovering my backup from sdcard1. But the image name is 1970.01.01.00.03.16. And it says "md5 mismatch"
I tried flashing again the stock rom with flashtool. The proccess goes on but nothing happens. I still have CWM and the boot loop.
I read elsewhere someone with a similar problem who solved using sony "emma" software. I installed it, it won't even recocnize my phone.
It recocnizes that there is a phone, but don't know which one.
But that has alway been the case with windows. I haven't been able to do anything in windows other then accessing the sdcard (when the phone worked).
Is there something I can do? I imagine that somehow, for some reason, the /data and /sdcard partitions got corrupted. I imagine I would need to repartition this and install again, but I have no idea how this happens on phones...
I can mount /system /cache and /storage/sdcard1. just /data I canĀ“t. Says "error mounting /data"
This is my only phone and a vey recent $400 thing. I was very stupid to do that withouth a replacement and really need this phone. I greatly appreciate any help...
I found this post forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ searching the internet. Is it possible that this would solve my problem? or would it finish bricking the phone?
Here's what you'll need:
Working recovery, basic knowledge of adb & the shell
Parted (download here)
stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Click to expand...
Click to collapse
Yes, I know, I should have backed up...but did not. So, this TP, I cannot go into usb mode or recovery mode. For some reason, I get a weird 4 block pattern. Before I messed up, I was able to use TWRP 2.8.3 to load different gapps and roms in the ttinstall file by mounting. Well, I decided Lollipop was not quite what I wanted and wanted to go back to KitKat. Anyway, in my zeal of trying to fix what may be causing the recovery mode issue, I wiped everything and formatted everything...including the ttinstall file. I can still boot to twrp 2.8.3, but honestly, the sequence of invents I have tried to create a new folder called ttinstall and place in there rom and gapps, it will not load. In fact, I'm not sure where the twrp file is located. So, I would appreciate it if someone has detailed instructions beginning with opening twrp 2.8.3. What sd card to use and folder to create where, and so forth. I can mount the TP and load files via the pc, but I don't quite know where they actually go on the tablet. The device shows up as 1gb on the pc and this is a 32gb TP so I know I messed it up. I was spoiled by the TPToolbox when I was able to use the usb recovery mode and make all changes there.
Any help would be appreciated. I did do a search, but I have not found clear instructions for me. I even saw a youtube, but again, it was more confusing. Thanks.
golfnut22 said:
Yes, I know, I should have backed up...but did not. So, this TP, I cannot go into usb mode or recovery mode. For some reason, I get a weird 4 block pattern. Before I messed up, I was able to use TWRP 2.8.3 to load different gapps and roms in the ttinstall file by mounting. Well, I decided Lollipop was not quite what I wanted and wanted to go back to KitKat. Anyway, in my zeal of trying to fix what may be causing the recovery mode issue, I wiped everything and formatted everything...including the ttinstall file. I can still boot to twrp 2.8.3, but honestly, the sequence of invents I have tried to create a new folder called ttinstall and place in there rom and gapps, it will not load. In fact, I'm not sure where the twrp file is located. So, I would appreciate it if someone has detailed instructions beginning with opening twrp 2.8.3. What sd card to use and folder to create where, and so forth. I can mount the TP and load files via the pc, but I don't quite know where they actually go on the tablet. The device shows up as 1gb on the pc and this is a 32gb TP so I know I messed it up. I was spoiled by the TPToolbox when I was able to use the usb recovery mode and make all changes there.
Any help would be appreciated. I did do a search, but I have not found clear instructions for me. I even saw a youtube, but again, it was more confusing. Thanks.
Click to expand...
Click to collapse
Edit: Well, that was easy. I just set up the ttinstall folder, then copied the rom and gapps zip files there, unmounted, then selected install from the twrp menu (rom first then gapps), rebooted and presto...running again.