[Q] After Schzoid 22Jul2013, cannot boot to recovery. - TouchPad Q&A, Help & Troubleshooting

I first installed Schizoid 2.10_jb-22Jul2013 and then reverted to skz_tenderloin-2.10_jb_4.2.2-29JUN2013-130837.zip. This is probably my error in installing so I can't blame the ROM. This screwup resulted in wiping out all other boot options so that I could only reboot to Cyangen Mod. Reboot to recovery or bootloader from Schizoid all resulted in a boot back to Schizoid. I've tried using GooManager and Rom Manager but it appears that they cannot get Superuser authority.
SYMPTOMS:
a) In Terminal Emulator, the 'su' command gets '/system/bin/sh: su not found'.
b) GooManager issues 'Preparing to Flash' message but never does the command.
c) Rom Manager issues "You must root your phone fo ROM Manager to function. Superuser was not found at "/system/bin/su" or "system/xbin/su" Use Google Search on you computer to find instructions to root your phone.'
d) Tried installing CWM recovery from ROM Manager but get 'Unspported Device'.
d) I tried pressing down both the Power and Home buttons but I get 'Please release keys'.
While it appears that the ROM works OK for most apps and I have a USB device driver that works, I'd like to be able to backup and update when improvements are made.
SOLUTION:
I first tried holding the HOME and POWER buttons but that did nothing. I then tried holding down both the Power and Volume Up buttons at startup. This brings up the USB logo on the screen. I have it tethered to my computer running Windows 7. This failed to install the Palm device driver. I had to download WebOS Docter 3.0.5 to go back to Web OS stock.
The following link walks you through the re-install process.
http://theunlockr.com/2011/10/18/how...e-hp-touchpad/
You need an account with HP WebOS. Here's the link for the download of WebOS.
http://ws.hpwebos.com/webosdoctor/webosdoctor.htm?
The process took over an hour but I was able to boot to the stock HP WebOS. I did not lose my data files but it wiped out all my boot-loader and Android entries.
After the return to stock, I followed the very detailed instructions to install CWM recovery (Great stuff!):
http://forum.xda-developers.com/wiki/HP_Touchpad
The only thing different I would suggest is to download ACMEInstaller3 instead of ACMEInstaller2. I had a problem later that caused me to repeat the process again which I think is a result of the way ACMEInstaller2 divides the partitions.
My process came up with CWM recovery, WEB OS, and WEB OS recovery on the boot menu. From here I installed Cyanagenmod 9. After booting to CM 9, I installed GooManager and the latest TWRP. A boot to TWRP allowed a restore of my good backup and a return to my setup prior to the screwup and brought me back to my regular setup.

Get USB sign with Power and Volume UP
See main text above.

Re-install WebOS
See main text above.

Restoring Multiboot with CM9
See main text above.

Related

[Q] Warning sign with exclamation mark on boot

Hi,
I installed CM7 months ago, updated to WebOS 3.0.4, re-installed moboot via ACMEInstaller and am now running XRONified 2.9.1 odex and I was a happy geek until now.
Yesterday I booted into WebOS (as every day to video chat with my gf) and this morning I rebooted the device to load Android (again, as every day).
Then after shutting down and coming up again instead of loading moboot and booting into Android it showed me a nice warning sign with an exclamation mark and the text "www . palm . com / ROM".
Following that link on my computer leads to the Meta Doctor page so I think something got messed up mysteriously.
A few days ago WebOS showed up a notification for the WebOS 3.0.5 update which I didn't install.
I guess maybe it auto-updated over night and something went wrong ... ?!
Whatever, my question is:
Is it safe to simply doctor the device or do I first have to uninstall Android via ACMEUninstaller because of the partitions or such (read about some partition problems with the doctor ...) or do I need to do other preparations for doctoring?
EDIT
For a way to fix this without doctoring see post 5
real_sl4cker said:
Hi,
I installed CM7 months ago, updated to WebOS 3.0.4, re-installed moboot via ACMEInstaller and am now running XRONified 2.9.1 odex and I was a happy geek until now.
Yesterday I booted into WebOS (as every day to video chat with my gf) and this morning I rebooted the device to load Android (again, as every day).
Then after shutting down and coming up again instead of loading moboot and booting into Android it showed me a nice warning sign with an exclamation mark and the text "www . palm . com / ROM".
Following that link on my computer leads to the Meta Doctor page so I think something got messed up mysteriously.
A few days ago WebOS showed up a notification for the WebOS 3.0.5 update which I didn't install.
I guess maybe it auto-updated over night and something went wrong ... ?!
Whatever, my question is:
Is it safe to simply doctor the device or do I first have to uninstall Android via ACMEUninstaller because of the partitions or such (read about some partition problems with the doctor ...) or do I need to do other preparations for doctoring?
Click to expand...
Click to collapse
Firstly try a reinstall of moboot and recover your android settings and apps. I use backup everything with everything "ticked".
Then docter and start a fresh total reinstall of everything.
Boot into Android.
Restore your apps first, check they all run OK and then restore your settings.
Would love to re-install moboot but I can't boot at all, neither into WebOS nor into Android, no sign of moboot, just the mentioned warning sign when turning the device on.
So I don't need to uninstall Android (remove the android partitions) before using WebOS Doctor?
real_sl4cker said:
Would love to re-install moboot but I can't boot at all, neither into WebOS nor into Android, no sign of moboot, just the mentioned warning sign when turning the device on.
So I don't need to uninstall Android (remove the android partitions) before using WebOS Doctor?
Click to expand...
Click to collapse
I had to doctor my TP also. I didn't remove android (the files were still there). After doctoring, I reinstalled moboot using acmeinstall and restored a backup with cwm. Everything is working fine (so far).
Fixed it!
For reference:
Follow the steps from RootzWiki:
Still nothing? Or maybe you have a dreaded triangle-with-an-exclamation-mark on the screen?
Another "emergency" idea (for advanced folks only) is to boot ClockWorkMod Recovery *directly* from your computer via USB cable rather than from the TouchPad's internal storage. To try this, find an "update...zip" file that contains ClockWorkMod. Inside this zip file is a file called something like "uImage.ClockWorkMod". Extract/unzip that file to your computer, then use novacom (which you used with ACME installer) to "inject" ClockworkMod into your TouchPad.
This process should be familiar to you-- very similar in fact to using ACME Installer. It's done by starting the tablet with the up-volume key held down. When you see the USB icon, connect your computer to the TouchPad via USB, then, in a Terminal, navigate on your computer to where the uImage.ClockWorkmod file is, and type:
novacom boot mem:// < uImage.ClockworkMod
Assuming everything went well and ClockworkMod did start up, you may now use CWM to re-install "update...zip" files, restore from backups, format partitions, or reset everything to factory settings.
Click to expand...
Click to collapse
Then ...
In CWM mount USB storage
If not exist create "cminstall" dir and put the moboot file into it from your computer
Reboot System and hold VOL UP again to get into recovery mode
Launch ACMEInstaller and let it install moboot
I'm now able to boot into WebOS via moboot but Android ends up in a boot loop so I will use ACMEUninstaller and setup everything again (just to be sure) ...
Sure reflashing and clearing caches will do as well but it's not bad to start fresh (see EDIT 2 for confirmation)
EDIT
Seems a failed update for UberKernel causes the problem. When trying to update UberKernel via Preware (I'm still on WebOS 3.0.4) it says something like "only xxxx of xxxx mb" extracted. When I reboot after that moboot is gone and the triangle is back and I have to repeat the process.
EDIT 2
Just for the sake of completeness (for those who don't want to start fresh): Clearing Cache and Dalvik cache and re-flashing XRONified 2.9.1 again solved the boot loop. All Data, Apps and stuff are still there. I will do a Titanium backup now, uninstall via ACMEUninstaller, Wipe the whole thing, setup WebOS and re-install Android. Spring Cleaning
chicle_11 said:
I had to doctor my TP also. I didn't remove android (the files were still there). After doctoring, I reinstalled moboot using acmeinstall and restored a backup with cwm. Everything is working fine (so far).
Click to expand...
Click to collapse
Maybe it's version-related. Which version of WebOS-Doctor did you use?

Clockwork mod missing

Hi everybody I had a question, I tried installing TWRP from goomanager for the touchpad the other day. When it installed I went in to moboot and tried opening it it gave me the error invalid size. Also, after installing TWRP to option for clockwork mod disappeared on my moboot. So through intrernalz pro on web os I was able to remove the uimage of twrp from the boot folder, but that left me with only the option to boot into cyanogenmod and no type of recovery option available. I tried using acmeinstaller2, to just install CWM but after restarting there was nothing added to my moboot. I am sort of at a stand still since with out a recovery i cant update, nor can i recover from a back up. Any help would be appreciated. Thanks guys.
- Zero
zeroman9121 said:
Hi everybody I had a question, I tried installing TWRP from goomanager for the touchpad the other day. When it installed I went in to moboot and tried opening it it gave me the error invalid size. Also, after installing TWRP to option for clockwork mod disappeared on my moboot. So through intrernalz pro on web os I was able to remove the uimage of twrp from the boot folder, but that left me with only the option to boot into cyanogenmod and no type of recovery option available. I tried using acmeinstaller2, to just install CWM but after restarting there was nothing added to my moboot. I am sort of at a stand still since with out a recovery i cant update, nor can i recover from a back up. Any help would be appreciated. Thanks guys.
- Zero
Click to expand...
Click to collapse
Do you still have "ulmage.ClockworkMod" in the boot folder, it sounds like it must be gone or it should show up as an option in moboot? With mine when I installed TWRP it didn't change the options in moboot, moboot still says ClockworkMod but when that is selected it goes into TWRP and there is no "ulmage.TWRP" in my boot folder. I thought that was how TWRP was meant to install on the TP. I'm not sure if there is another way to install CWM other than with the ACME2installer, might be worth a search.
Did you make sure "update-cwm_tenderloin-1012" was in the "cminstall" folder when you ran ACME2?
You could move your backup to comp, run ACMEuninstaller and webos doctor and start from scratch and install CM9. Then just restore from your backup. I've done that a few times for other reasons.
Good Luck
Thanks for the help man, the CWM i was using was called recovery_cwm and i just had to change the name to update_cwm and let acmeinstaller do the rest. Saved me alot of time by avoiding uninstalling everything and restoring.
- Zero
CWM gone while installing TWRP through gooMan
Hi Zero,
Sorry but I am totally new to android and on how to install it in my TP. But, I was successfully running Cyanogenmod for sometime now until I thought of installing TWRP in my TP instead of CWM as installing nightly updates was becoming difficult for me.
I tried to install twrp through gooManager so that I would have both the option of Clockworkmod and twrp. SInce twrp is a better ui, I thought of using it instead of ClockworkMod.
So, I went to their site: teamw.in/project/twrp2/75
and followed the following:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will reboot and install the recovery automatically.
By doing so, it did not reboot but while I tried to reboot myself, I saw that the ClockWorkMod menu is gone from moboot and I have no recovery option left. The menu has 'Boot TWRP' but when selecting that, it says corrupt data and my TP hangs.
Please guide me in getting CWM back or get the TWRP.
Please help!!! Thanks in anticipation.
avisekhg said:
Hi Zero,
Sorry but I am totally new to android and on how to install it in my TP. But, I was successfully running Cyanogenmod for sometime now until I thought of installing TWRP in my TP instead of CWM as installing nightly updates was becoming difficult for me.
I tried to install twrp through gooManager so that I would have both the option of Clockworkmod and twrp. SInce twrp is a better ui, I thought of using it instead of ClockworkMod.
So, I went to their site: teamw.in/project/twrp2/75
and followed the following:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will reboot and install the recovery automatically.
By doing so, it did not reboot but while I tried to reboot myself, I saw that the ClockWorkMod menu is gone from moboot and I have no recovery option left. The menu has 'Boot TWRP' but when selecting that, it says corrupt data and my TP hangs.
Please guide me in getting CWM back or get the TWRP.
Please help!!! Thanks in anticipation.
Click to expand...
Click to collapse
If you have the install zip from sd card option, then flash jcsullins' recovery. Use the 12/15 version.
You can also install the same recovery using acmeinstaller 3.
There's a moboot cleaning utility, on the classic nerds' site (use it if you need to get rid of 'ghost' uimages).
Edit : here's the link to jcsullins' recovery : http://goo.im/devs/jcsullins/cmtouchpad/recovery
Edit 2 : here's another link that would be useful : http://forum.xda-developers.com/showthread.php?t=2030675&page=4

Boot loop problem

Hello,
I tried installing a custom ROM on my 7310 and it had issues. I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop. I think I need to repartition, but when I click the repartition checkbox in ODIN I get an error.
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Thanks.
A few questions:
spazlon said:
I tried installing a custom ROM on my 7310 and it had issues.
Click to expand...
Click to collapse
What did you try to flash and how did you try doing it (CWM, ODIN, ...)?
What 'issues'?
I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop.
Click to expand...
Click to collapse
How far into the boot sequence does it get?
Are you able to get into recovery?
If so, what recovery do you have (Stock vs CWM)?
Have you tried seeing what is causing the boot-loop using adb?
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Click to expand...
Click to collapse
This is an action of last resort. Exhaust all other avenues first.
boscorama said:
What did you try to flash and how did you try doing it (CWM, ODIN, ...)?
What 'issues'?
Click to expand...
Click to collapse
I used CWM to flash AOSP 4.1.2. It seemed to work fine for a day or two, but then it needed charging (as normal). I let it charge over night and in the morning it had less battery. I figured the charger or cable were flaky so I tried another set on another outlet and same thing. Then it finally ran out of battery. I let it charge again over night and when I tried to turn it on it was really slow. The boot animation was only 1 frame every couple seconds. It would eventually boot all the way up, but it was still REALLY slow. So I went into CWM and reflashed the same ROM. Then I got a boot loop of the boot animation. I couldn't get into CWM any more, so then I went into download mode and flashed the official firmware and flashed it with ODIN.
boscorama said:
How far into the boot sequence does it get?
Click to expand...
Click to collapse
Now when I turn it on it just says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I can flash again with ODIN and it will get to the Samsung boot animation and just pulse SAMSUNG.
boscorama said:
Are you able to get into recovery?
If so, what recovery do you have (Stock vs CWM)?
Click to expand...
Click to collapse
If I hold power and volume down I can get into download mode or Samsung recovery, not CWM, and power with volume up doesn't do anything.
boscorama said:
Have you tried seeing what is causing the boot-loop using adb?
Click to expand...
Click to collapse
I don't know anything about adb and I'm not sure what I would be looking for. Is there a tutorial I can follow somewhere?
Thanks for any help!
This worked for me with similar problem
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Thanks! I'll give this a try when I get home. I'll let you know how it works out.
Don't ever try to 'repartion unless you really know what you're doing. You're soft bricked. Repartion and you'll hard brick.
I'd go back and get hc from sammobile and flash that with Odin. Ics has had some problems.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
Don't ever try to 'repartion unless you really know what you're doing. You're soft bricked. Repartion and you'll hard brick.
I'd go back and get hc from sammobile and flash that with Odin. Ics has had some problems.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Agreed - my procedure avoids manual repartitioning - I tried lots of other procedures but none worked. I think my data partition had become corrupt because I kept getting error messages. My first try was to recover with my cwm recovery file I made originally but I kept getting back to the boot loop .
spazlon said:
Hello,
I tried installing a custom ROM on my 7310 and it had issues. I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop. I think I need to repartition, but when I click the repartition checkbox in ODIN I get an error.
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Thanks.
Click to expand...
Click to collapse
I always got something like that ...
After bootloop just go to recrovery mode then factory riset ... its 100% WORK
Sent from my GT-P7300 using xda premium
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
spazlon said:
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
Click to expand...
Click to collapse
Sorry - being a newbie myself I'm at a loss. It worked a charm for me.
spazlon said:
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
Click to expand...
Click to collapse
did a format /system before installing the custom roms? This is an important step.
prince93 said:
did a format /system before installing the custom roms? This is an important step.
Click to expand...
Click to collapse
This fixed it. Never had to do it with any of my other devices. CM10 loaded quickly after that. Loving how fast JB is!
Thanks!
Sent from my GT-P7310 using Tapatalk HD
It worked
mobjunky said:
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Click to expand...
Click to collapse
WOw! This fixed my Tablet! thank you ever so much!!
mjramos15 said:
WOw! This fixed my Tablet! thank you ever so much!!
Click to expand...
Click to collapse
mobjunky said:
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Click to expand...
Click to collapse
Gee thanks. This saved my tab. I'd almost given up on it and then voila.

[Q] Can I ADB pull media files from device? Help please!

Hey guys!
I've been having a lot of problems with a Samsung Galaxy S Plus recently. After my girlfriend entered the wrong picture password a number of times in a row, the phone locked down. I tried to activate data connection using the power menu (hold power button), which I had deactivated before it locked down. My attempts to log in failed when the device returned either 'invalid username' or 'invalid password' (they are - of course - neither). This is apparently a known problem. I then followed the following instructions to trick the device into thinking the google account had been verified: droidwiki .de/Muster_vergessen#Muster_l.C3.B6schen (warning, that site is in German). For this I successfully managed the following steps:
1.) Installation of ADB tools
2.) Installation of ClockwordMod using Odin in order to accomplish the ...
3.) Activation of USB debugging.
4.) Rooting the phone using these instructions: androiddrole .com/how-to/how-to-easily-root-samsung-galaxy-s-plus-i9001
All these steps worked as expected. Then however, the trouble started: When trying to set the number of failed pattern attempts to 0, the following command failed: "cd /data/data/com.android.providers.settings/databases" ("can't cd to /data/data/com.android.providers.settings/databases"). Additionally I could no longer boot into android as the phone kept booting directly into CWM (This is apparently also a known problem). I proceeded to install a newer version of ClockworkMod Touch (using zip on sd card) hoping this would allow me to break the loop. It didnt. So I replaced ClockwordMod with TeamWin Recovery Project (TWRP). This did finally allow me to exit the recovery mode only to get stuck in a full-out reboot loop: Samsung logo -> black screen -> Samsung logo -> black screen. In order to get out of this reboot loop I used Odin to flash boot_loader.tar and the original version of ClockwordMod onto the device. After a number of failed attempts this suddenly worked - kinda:
The current situation is this: The phone no longer boots directly into recovery mode (good). It doesnt boot into android either though. It just reboots over and over again - this can be stopped however by using 'Volume Down' + 'Home' + 'Power' to access ClockwordMod.
My hopes of getting my phone unlocked and working as before again are rather slim at this point. I would still like to save my substantial collection of photographs from the media folders on the device, before I wipe the entire thing (or buy a new phone).
Therefore my question to you:
Is it possible to extract the photos (stored in the standard media locations of android 2.3) to a PC using only USB-Debugging/Odin/ClockwordMod (being unable to boot into android)?
I tried to pull the media files using the 'adp pull' command, but I couldnt get it to work (maybe because I didnt get the command or the file-paths correctly). Any suggestions would be GREATLY appreciated.
Solution
Attention: If you want your media files, backup your current state first. Go to backup and restore -> backup. Then do steps written below. Backup will be in CWM folder on your sdcard.
This is called a soft-brick. It's good that you can access download and recovery mode using 3 button combinations. First, download a stock Gingerbread ROM for your device model and put it on your sdcard. Boot into CWM and select Wipe user data -> Yes. Wipe Cache Partition -> Yes. Go to Advanced menu and select Wipe Dalvik cache -> Yes. Now return to previous menu and select install zip from sdcard -> choose zip from sdcard -> select name.of.downloaded.rom.zip -> Yes -> Wait 1-2 minutes to flash -> Wipe user data -> Wipe Cache Partition -> Wipe Dalvik Cache. Then select Reboot system now from main menu, and wait 4-5 minutes for it to boot first time.
DaniTheMan said:
Hey guys!
I've been having a lot of problems with a Samsung Galaxy S Plus recently. After my girlfriend entered the wrong picture password a number of times in a row, the phone locked down. I tried to activate data connection using the power menu (hold power button), which I had deactivated before it locked down. My attempts to log in failed when the device returned either 'invalid username' or 'invalid password' (they are - of course - neither). This is apparently a known problem. I then followed the following instructions to trick the device into thinking the google account had been verified: droidwiki .de/Muster_vergessen#Muster_l.C3.B6schen (warning, that site is in German). For this I successfully managed the following steps:
1.) Installation of ADB tools
2.) Installation of ClockwordMod using Odin in order to accomplish the ...
3.) Activation of USB debugging.
4.) Rooting the phone using these instructions: androiddrole .com/how-to/how-to-easily-root-samsung-galaxy-s-plus-i9001
All these steps worked as expected. Then however, the trouble started: When trying to set the number of failed pattern attempts to 0, the following command failed: "cd /data/data/com.android.providers.settings/databases" ("can't cd to /data/data/com.android.providers.settings/databases"). Additionally I could no longer boot into android as the phone kept booting directly into CWM (This is apparently also a known problem). I proceeded to install a newer version of ClockworkMod Touch (using zip on sd card) hoping this would allow me to break the loop. It didnt. So I replaced ClockwordMod with TeamWin Recovery Project (TWRP). This did finally allow me to exit the recovery mode only to get stuck in a full-out reboot loop: Samsung logo -> black screen -> Samsung logo -> black screen. In order to get out of this reboot loop I used Odin to flash boot_loader.tar and the original version of ClockwordMod onto the device. After a number of failed attempts this suddenly worked - kinda:
The current situation is this: The phone no longer boots directly into recovery mode (good). It doesnt boot into android either though. It just reboots over and over again - this can be stopped however by using 'Volume Down' + 'Home' + 'Power' to access ClockwordMod.
My hopes of getting my phone unlocked and working as before again are rather slim at this point. I would still like to save my substantial collection of photographs from the media folders on the device, before I wipe the entire thing (or buy a new phone).
Therefore my question to you:
Is it possible to extract the photos (stored in the standard media locations of android 2.3) to a PC using only USB-Debugging/Odin/ClockwordMod (being unable to boot into android)?
I tried to pull the media files using the 'adp pull' command, but I couldnt get it to work (maybe because I didn't get the command or the file-paths correctly). Any suggestions would be GREATLY appreciated.
Click to expand...
Click to collapse

"Big" troble with moboot and firmware

Greetings!
If this question was early on this forum please forgive for double it, because my search gives no result.
Today wanted update my old CM7 for a new CM9, because last update was about 2 years ago. So I went to thematic forums and remind myself how to do this, i guided this and some of this
So I download palm drivers, then moboot 0.3.5, then ACMEInstaller3 and ACMEUninstaller and last CM9 (cm-9-20130714-NIGHTLY-tenderloin.zip )
Then,I uninstall old android with ACMEUninstaller (operation was succes) after I login In webOS and use Full erase.
After Install moboot and CM9, BUT I forget to add a Clockworckmod.zip in cminstall folder. So I use an ACMEUninstaller, but nothing happened, all uninstall process was very fast (about 2-5 sec, and table goes to reboot)
So I load in CM9, add clockworcmode.zip in cminstall directory, reboot in Recovery mode to use ACMEInstaller3 with Clockworckmode.
But again - nothing only 4menu was available . So I load webOS and use Secure Erase.
After reboot in moboot menu I was not able to load webOS.And I decide to use webOSDoctor (3.0.5) then check tablet and start to instal some files and stuck at 4% then touchpad reboot.
When table powered on moboot loaded again... I was surprised... when I use load webOS option - table goes in reboot and doctor don't answered, then I choose Recovery, doctor progress bar down to 1% and all starts over and over.
I decided to close doctor with task manager.
CM9 loads every 1 of 3 try's (when I choose load CyanogenMod)so I used it to update/renew files incminstall I was confuseed...
Then I uninstall from my PC palm/webdoctor/acme and install older or this same programs again, but it reinstalling wasn't helps.Older versions of moboot3.4/acme2/CM was useless.
I try to folow this instruction (Factory condition restoration / Downgrade to webOS 3.0.0), after step 5) In that command prompt, run ( novacom boot mem:// < nova-installer-image-topaz.uImage )
When table start a reboot process it was failed, because of moboot that load after table powered.
So at this moment I have a working moboot without clockwockmod, and recover mode.
I don't know what to do, please help some advice. Iam in desper
Even without moboot's "boot webOS recovery" option working [which I have never had the misfortune of experiencing], you can still enter that mode by powering on the TP with the Volume Up button held down.
If that doesn't work, try using tpdebrick... but follow the instructions exactly, and if you have ANY questions - do not proceed. Ask on this forum post.
castrwilliam said:
Even without moboot's "boot webOS recovery" option working [which I have never had the misfortune of experiencing], you can still enter that mode by powering on the TP with the Volume Up button held down.
If that doesn't work, try using tpdebrick... but follow the instructions exactly, and if you have ANY questions - do not proceed. Ask on this forum post.
Click to expand...
Click to collapse
Yeah, i still can load webos recovery mode, but all what i use in that mode is not helping, webosdoctor and other commands like ACME. Just when touchap restart, he still load that same bugged moboot menu
FreeDooMF1 said:
Greetings!
If this question was early on this forum please forgive for double it, because my search gives no result.
Today wanted update my old CM7 for a new CM9, because last update was about 2 years ago. So I went to thematic forums and remind myself how to do this, i guided this and some of this
So I download palm drivers, then moboot 0.3.5, then ACMEInstaller3 and ACMEUninstaller and last CM9 (cm-9-20130714-NIGHTLY-tenderloin.zip )
Then,I uninstall old android with ACMEUninstaller (operation was succes) after I login In webOS and use Full erase.
After Install moboot and CM9, BUT I forget to add a Clockworckmod.zip in cminstall folder. So I use an ACMEUninstaller, but nothing happened, all uninstall process was very fast (about 2-5 sec, and table goes to reboot)
So I load in CM9, add clockworcmode.zip in cminstall directory, reboot in Recovery mode to use ACMEInstaller3 with Clockworckmode.
But again - nothing only 4menu was available . So I load webOS and use Secure Erase.
After reboot in moboot menu I was not able to load webOS.And I decide to use webOSDoctor (3.0.5) then check tablet and start to instal some files and stuck at 4% then touchpad reboot.
When table powered on moboot loaded again... I was surprised... when I use load webOS option - table goes in reboot and doctor don't answered, then I choose Recovery, doctor progress bar down to 1% and all starts over and over.
I decided to close doctor with task manager.
CM9 loads every 1 of 3 try's (when I choose load CyanogenMod)so I used it to update/renew files incminstall I was confuseed...
Then I uninstall from my PC palm/webdoctor/acme and install older or this same programs again, but it reinstalling wasn't helps.Older versions of moboot3.4/acme2/CM was useless.
I try to folow this instruction (Factory condition restoration / Downgrade to webOS 3.0.0), after step 5) In that command prompt, run ( novacom boot mem:// < nova-installer-image-topaz.uImage )
When table start a reboot process it was failed, because of moboot that load after table powered.
So at this moment I have a working moboot without clockwockmod, and recover mode.
I don't know what to do, please help some advice. Iam in desper
Click to expand...
Click to collapse
You should probably stick with the most recent and updated Install guide. Did you happen to read this note?
3)Note: When using the acmeinstaller2/3, the Rom and Gapps files must begin with update-xxxx. If update- is not present the Rom and gapps may not install. You can add update- to the Rom & Gapps file names if it is missing.
I noticed you didn't use gapps, are you sure you read my guide?
RolandDeschain79 said:
You should probably stick with the most recent and updated Install guide. Did you happen to read this note?
3)Note: When using the acmeinstaller2/3, the Rom and Gapps files must begin with update-xxxx. If update- is not present the Rom and gapps may not install. You can add update- to the Rom & Gapps file names if it is missing.
I noticed you didn't use gapps, are you sure you read my guide?
Click to expand...
Click to collapse
yes i forget about gapps at all. I didnt add it in cminstall folder on my tablet when i use acminstaller...
so what to do now? how erase all data and load webos again?
Problem solved
FreeDooMF1 said:
ok, topic can be close.
it's all about that i inattentive fool.
I dont reneme install files in cminstall folder that i added on table, and because of it ACME dont work right.
now all ok, i have full functional moboot and newest CM9 with play market.
Click to expand...
Click to collapse
Glad to hear you got it all working (@ RootzWiki), you just needed the right info to get started Time to enjoy all that Android goodness on your TouchPad! Don't forget to make a Nandroid backup and transfer it to your computer. If anything goes wrong in the future, you will be fully prepared

Categories

Resources