Database Develop

[Q] Sprint P100 can not wipe

Hi All:
My Sprint Tab P100 got some strange problems.
It's a second hand P100, Once i turn on the tab, it will warning with 3 Beebee, and nook & Amaza Mp3 & Market will report error.
Below warning will show up:
Amazon MP3_nook
“The application XXX has stopped unexpectedly, pls try again”
Market
"Attention:
An Error has occured, Please try again later."
After check, i found the original usr information still there.
(Gmail/Facebook account will try to sync with previous owner's ID. and i can not remove the account.)
What i have tried:
1) I have tried to WIPE using system recovery, after WIPE both data & Cache partition, issue still exist.
2) Perform the Samsung factory reset by enter *2767*3855# in the Memo, problem still there.
3)Format the SD card with Phone & Windows, still got problem
4) Flashed with the stock EA24 Rom from XDA(with Modem,using Odin), the problem still remain the same.
5)Flashed with DJ30, the problem still exist(Base/Fireware EA24).
6)Tried to install CWM, failed to boot up(Rooted before install CWM, after flash the Zimage to Kernal or recovery, some strings flush in the screen, then the tab hung at Samsung logo and reboot.)
I guess those problem was caused by some program information still remain in the internal storage, even after factory reset or flash with other ROM.
Can somebody help on this? Also prefer someone can help on how to install CWM
I am interesting that the OVERcome 2.01 Rom got a version to WIPE the internal storage, but the OVERcome rom are designed for GSMer. Can i tried to use it to clear my internal storage?

just installed Astro, the program will crashed when launch it

Can some one help on this topic?
I am suspecting my internal storage was locked to Non-Writable.
This might result CWM can not access the internal memory caused the failure of the installation.
Is it related to the Flash lock option in the Odin?

Check this thread..
http://forum.xda-developers.com/showthread.php?t=1133053
That has the stock files, and instructions to get root and CWM installed with the stock software. Using Odin to put the stock firmware (EA24) should wipe anything and everything off the tab and restore it to as if it were new out of the box. You also might want to wipe your sd card as it can cause issues with the CWM ext4 conversion.

Hi pvtjoker42 & All:
During the process of Kernel with CWM Recovery, i has been stopped @ step7
1) Download the zip file here
2) Unzip the file. You will need the file named zimage only.
3) Open Heimdall Frontend
4) Select Browse under Kernel and navigate to the file you downloaded in step 1 and select it
5) Press Start
6) The Tab will reboot, but will freeze on the Samsung logo. Turn it off and boot into recovery (Vol Up + Power)
~~~~~~~~~~~~~~~~~~~~
my tab failed here, no matter what you pressed, it doesn't go to CWM. Do u have any idea?
~~~~~~~~~~~~~~~~~~~~
7) CWM Recovery will attempt to back your tab up, but will fail. Don't fret.
8) Do a factory reset in CWM Recovery and reboot
9) You'll freeze on the Samsung logo again Turn it off and boot into recovery.
10) CWM Recovery will back your Tab up successfully.
11) You now have a CWM backup. Reboot.
12) Your auto rotate is broken.
13) Download the rotation file
14) Put it in /system/lib/hw and change the permissions to match the other items.

Can someone helps?
Today i tried 1 more things, Use a update.zip to update the tab from EA24 to EB28,before try this, i have tried OTA to EB28, it never success.
i download the update.zip from <forum.sdx-developers.com/index.php?PHPSESSID=99sdnmh5pm4rtuv39hk80f7du6&topic=13104.0;nowap> it seems to be official one, and the recovery is the stock version, but it failed again.
I start to believe that my internal storage has been locked, and data can not write in.
Is it possible to due to Fstab issue?
Pls helps to save my tab....

There is only one thing to do : return to stock. Carefully follow the guide. Don't do anything else to your tab, until you go through the restock steps :
http://forum.xda-developers.com/showthread.php?t=1133053
[SPRINT] Sprint Tablet Owners Thread (Root, ROM, Flash to stock, CWM Recovery)
The process reformats/repartitions your internal sd card, and sets the correct permissions. If this process fails, there is probably something wrong with the tab.

you might also try to select the option to repartition in Odin when going back to EA24. Then try the steps to get EB28 OTA update, and once you've got that up and running, you can try the update.zip to get to EF17 (gingerbread, as long as you don't need root)

I wouldn't. Try a different sd card
Sent from my Nexus S 4G using Tapatalk

Hi All:
Thanks for the advice.
I have tried to back to stock EA24 using odin, but the situation still ramain the same.
And it fail to OTA to EB28, the EB28 upgrade program will reboot the machine, and enter recovery model. but it will complete the program. also i have tried to put EB28 update.zip in the SD card, but also fail to upgrade to EB28.
I have repartition the phone by P100 serveral time using odin, also tried update Pit file. All failed.
I have format the SD card in Windows & then in Android, useless.
Now i have some clues:
In P1000 rom Roto-JME, there is Movinand.bin, this one got same name as the internal storage IC from samsung. i am thinking that file could be a file similar to partition table.
Can someone help to dump a "movinand.bin" for me from P100?
steps:
1)Get back to stock EA 24
2)Wipe Cache & factory data
3) Root it (Using superone click , you can find it here http://forum.xda-developers.com/showthread.php?t=803682)
4)Install terminal (i use better terminal) or using a ADB to connect to shell.
5)Type "su", check whether "$" change to "#" in the shell
6) Type “dd if=/dev/block/mmcblk0p2 of=/sdcard/movinand.bin bs=4096”
7) Find the Movinand.bin in the SD card
You can sent it to me by drop a email to [email protected]
If there is anything wrong, pls help to correct me
Thanks in advance

as some people is asking how did i fix the issue, just publish the information here.
I fixed the issue by replaced the internal storage (the chip), cost about US$ 30(RMB 200)
If anyone have better solution, just post here to share

How to root wellcom a99 without usb cable?

because usb port of my phone not working, its only charging. How to root my phone without connect it to pc? (like z4root.apk, I've try z4root and gingerbreak but it doesnt work) Anything help?
I think a preroot rom which can be flash with stock recovery does it so anybody make for me a preroot rom like firmware.nb0 so i can try it by stock recovery pleasezz!

dtbang721 said:
because usb port of my phone not working, its only charging. How to root my phone without connect it to pc? (like z4root.apk, I've try z4root and gingerbreak but it doesnt work) Anything help?
I think a preroot rom which can be flash with stock recovery does it so anybody make for me a preroot rom like firmware.nb0 so i can try it by stock recovery pleasezz!
Click to expand...
Click to collapse
hi
if u have CWM then down load the RC2 put it on root of ur SD
and flash it via CWM RC2 is pre rooted

dtbang721 said:
because usb port of my phone not working, its only charging. How to root my phone without connect it to pc? (like z4root.apk, I've try z4root and gingerbreak but it doesnt work) Anything help?
I think a preroot rom which can be flash with stock recovery does it so anybody make for me a preroot rom like firmware.nb0 so i can try it by stock recovery pleasezz!
Click to expand...
Click to collapse
refer to this thread
http://forum.xda-developers.com/showthread.php?t=1268695
parrkhi had explaind it well
or else go to this thread directly
http://forum.lowyat.net/topic/1985476
here loock down for the clockwork mode method
u can download these zip files directly to ur phone jst keep them in root folder
Always click thankx if u find it useful
here is the mediafire link for .zip files that u need for all this work.
http://www.mediafire.com/?evfo2dlq9m92w
go to this link download file ( i consider u have cwm already installed on your phone) if u dont have cwm dont worry give it a try in this link u will find a .zip file named as recovery,..zip jst rename it to update.zip and install it from recovery menu// u can also give this update thing a try with the su.zip files file are main for rooting

Thanks for reponse. But I mention that my phone cant connect to pc, I've tried it alot, I cant connect my phone to pc in download mode so I cant instant cwm. everything I can try is self root apk or flash a rooted rom with base stock recovery.

okk if u cant flash cwm then its quite troubling
if ur usb dosn't work why don't u rush to the service center they will solve this problem in say 15 to 20 mins... better go there and get it serviced ...

Not possible yet without getting it in download mode...

dtbang721 said:
Thanks for reponse. But I mention that my phone cant connect to pc, I've tried it alot, I cant connect my phone to pc in download mode so I cant instant cwm. everything I can try is self root apk or flash a rooted rom with base stock recovery.
Click to expand...
Click to collapse
vibhor15 said:
Not possible yet without getting it in download mode...
Click to expand...
Click to collapse
Well you can do that. I mean you can install CWM recovery without connecting your device via USB.
If you can download CWM recovery or Recovery menu directly on your device, follow these instructions.
Extract recovery.img file from downloaded zip file.
Keep it in sdcard's root directory. (/sdcard/recovery.img)
Now copy following commands and save it as Install_recovery.sh in your sdcard's root directory
Code:
#!/system/bin/sh
mkdir /sdcard/fih
mount -t vfat /dev/block/mmcblk0p1 /sdcard/fih/
cd /sdcard/fih/image/
mv /sdcard/fih/image/recovery.img ./recovery.img
cd /
umount /sdcard/fih
rm -r /sdcard/fih/
And use any script manager or Terminal emulator to run this file.
Using terminal emulator:
Code:
cd /sdcard/
sh Install_recovery.sh
Now boot into recovery. You should boot into new recovery.
P.S. Similar How-To is also posted in a thread: Restoring stock recovery: (without Download mode). I have just modified it a bit.

Thanks! I'll give it a try. But does Script manager and terminal emulator is a apk that i can install and use to run the command saved in Install_recovery.sh?
So that I run terminal emulator apk and type
"cd /sdcard/
sh Install_recovery.sh" ?

ok. I've tried but the emulator report errors. I think I must have rooted phone to install cwr with your solution. The error is
$ export PATH=/data/local/bin:$PATH
$ cd /sdcard/sh install_recovery.sh
cd: bad substitution
$ cd /sdcard/
$ sh install_recovery.sh
, Invalid argumentsdcard/fih
mount: No such file or directory
cd: can't cd to /sdcard/fih/image/
failed on '/sdcard/fih/image/recovery.img' - No such file or directory
cd: can't cd to /
failed.
rm failed for /sdcard/fih/, No such file or directory
$
So how do I get cwr on my phone to root it via cwr method?

dtbang721 said:
ok. I've tried but the emulator report errors. I think I must have rooted phone to install cwr with your solution. The error is
$ export PATH=/data/local/bin:$PATH
$ cd /sdcard/sh install_recovery.sh
cd: bad substitution
$ cd /sdcard/
$ sh install_recovery.sh
, Invalid argumentsdcard/fih
mount: No such file or directory
cd: can't cd to /sdcard/fih/image/
failed on '/sdcard/fih/image/recovery.img' - No such file or directory
cd: can't cd to /
failed.
rm failed for /sdcard/fih/, No such file or directory
$
So how do I get cwr on my phone to root it via cwr method?
Click to expand...
Click to collapse
Oh yes! I forgot.
Will try to come up with an answer as soon as possible.
Sent from my CSL-MI410 using XDA App

dude ... do you have a memory card reader ...???
if u have a card reader then jst remove ur card from phone plug into pc copy all the files i.e cwm recovery update.zip and su.zip
[Installation Instructions]
[Using CWM recovery]​
Copy CWM recovery-fb0-v5_signed.zipin sdcard
Boot into recovery (Steps are given below for how-to-boot-into-recovery)
Use "install zip from sdcard" option
Locate and choose CWM recovery-fb0-v5_signed.zip from sdcard for instllation
After installation reboot into recovery (advanced > Reboot recovery)
i suggest rename the .zip file to update.zip
and then follow rooting instruction

I mean that I've got a stock rom without root. So I havent CWM recovery installed on my phone.
My usb hub on my phone has broken and the phone waranty service not avainable in my country so I need a root solution without usb connecting.
As I know I need rooted phone first to install CWM recovery. Or I need a method to install CWM recovery by stock recovery.
I also try to flash back to 2.2 froyo version to root my phone by gingerbreak apk but not successed. When I try to flash any stock rom 2.2 or 2.3.4 the stock recovery allways report error and didnt worked. The error that stock recovery say is:
Enter lauch_image_update
Prepare failed rc= -209
PID doesnt match!
You cant download this nb0
Some error during preparing
So now I cant do anything with stock recovery only hardreset can done. No flash firmware.nb0 rom no update the update.zip
And when I try to flashing update.zip (CWM recovery-fb0-v5_signed_2.zip I renamed it to update.zip) stock recovery say error that:
verifying update package
E:signature verification failed

dtbang721 said:
I mean that I've got a stock rom without root. So I havent CWM recovery installed on my phone.
My usb hub on my phone has broken and the phone waranty service not avainable in my country so I need a root solution without usb connecting.
As I know I need rooted phone first to install CWM recovery. Or I need a method to install CWM recovery by stock recovery.
I also try to flash back to 2.2 froyo version to root my phone by gingerbreak apk but not successed. When I try to flash any stock rom 2.2 or 2.3.4 the stock recovery allways report error and didnt worked. The error that stock recovery say is:
Enter lauch_image_update
Prepare failed rc= -209
PID doesnt match!
You cant download this nb0
Some error during preparing
So now I cant do anything with stock recovery only hardreset can done. No flash firmware.nb0 rom no update the update.zip
And when I try to flashing update.zip (CWM recovery-fb0-v5_signed_2.zip I renamed it to update.zip) stock recovery say error that:
verifying update package
E:signature verification failed
Click to expand...
Click to collapse
There is still one option left.
You can create your own nb0 file (since thats the only option working), which has cwm recovery and rooted ROM.
Right now i am away from my work place so cant help you till next monday.
Sent from my CSL-MI410 using XDA App

I'm right here waitting!

dtbang721 said:
I'm right here waitting!
Click to expand...
Click to collapse
napstar is right make ur own .nb0 i m working on it too still no success having boot loops with usb when i flash it ... dont know why nd don't have plenty of time to log cat the problem ...

kshitij_bhatt said:
napstar is right make ur own .nb0 i m working on it too still no success having boot loops with usb when i flash it ... dont know why nd don't have plenty of time to log cat the problem ...
Click to expand...
Click to collapse
I have another android ( x10 mini pro) and I know that we can make a backup by stock recovery or cook a rom for flashing by stock recovery. But before public the rom the deverloper have to tested it because bootloop is the problem of flashing rom. So before flashing new rom we need do a hardreset and after flashing rom we also need a hard reset to solve boot looping problem.
because of brocken usb hub on my phone. I need tested before flashing. :'(
the test is:
1 make a nb0 file from a phone that working good.
2 try to flash nb0 by stock recovery to another phone to confirm that nb0 work good for all phone.
3 Note that some rom is working realy good for some phone but can make bootloop for another phone because of different keynell they are ussing or we dont make factory reset and do a wipe data and cache also get bootloop problem

nanana its not beautyfull life.

My First post...
dtbang721 said:
nanana its not beautyfull life.
Click to expand...
Click to collapse
Hi...
Are you sure that your phone has this usb problem? Not the usb cable?
I've an experienced with usb cable which has problem to connect, then I use blackberry usb data cable, then it works. My problem is the cable can't powered enough the phone to make data connection.
OR... you can flash Andro-ID RC1 first before other ROMs, which Andro-ID RC1 is the nb0 file (may be you can flashed it using stock recovery) and this RC1 is pre rooted and it has CWM recovery in it. Then you can use CWM to flash other zip based ROMs, including to update CWM it self to a newer version.
Hope it help....
Sorry if I missed understood of your problem! If you want to stay on WellCom 2.3.4 and rooted unwired, someone has to make update.zip with the su+superuser.apk and signed with appropriate key (FIH)

CacingKalung said:
Hi...
Are you sure that your phone has this usb problem? Not the usb cable?
I've an experienced with usb cable which has problem to connect, then I use blackberry usb data cable, then it works. My problem is the cable can't powered enough the phone to make data connection.
OR... you can flash Andro-ID RC1 first before other ROMs, which Andro-ID RC1 is the nb0 file (may be you can flashed it using stock recovery) and this RC1 is pre rooted and it has CWM recovery in it. Then you can use CWM to flash other zip based ROMs, including to update CWM it self to a newer version.
Hope it help....
Sorry if I missed understood of your problem! If you want to stay on WellCom 2.3.4 and rooted unwired, someone has to make update.zip with the su+superuser.apk and signed with appropriate key (FIH)
Click to expand...
Click to collapse
yes. that's my problems. Ill try to flash rc1. may be the problem is my usb cable. but i have not got any blackberry cable. I just have a stock cable and a sony erricson cable and a nokia cable. but none of them work.

CacingKalung said:
Hi...
Are you sure that your phone has this usb problem? Not the usb cable?
I've an experienced with usb cable which has problem to connect, then I use blackberry usb data cable, then it works. My problem is the cable can't powered enough the phone to make data connection.
OR... you can flash Andro-ID RC1 first before other ROMs, which Andro-ID RC1 is the nb0 file (may be you can flashed it using stock recovery) and this RC1 is pre rooted and it has CWM recovery in it. Then you can use CWM to flash other zip based ROMs, including to update CWM it self to a newer version.
Hope it help....
Sorry if I missed understood of your problem! If you want to stay on WellCom 2.3.4 and rooted unwired, someone has to make update.zip with the su+superuser.apk and signed with appropriate key (FIH)
Click to expand...
Click to collapse
dtbang721 said:
yes. that's my problems. Ill try to flash rc1. may be the problem is my usb cable. but i have not got any blackberry cable. I just have a stock cable and a sony erricson cable and a nokia cable. but none of them work.
Click to expand...
Click to collapse
Thats a good option. I thought you have already tried it and received an error saying "### ID mismatch"
Anyway if you have not downloaded it yet, then I have one other option for you. I have created an nb0 file which contains only CWM recovery and nothing else.
This file will install Recovery menu v2 which includes both CWM and stock recovery and no system files/data files.
To install, download attached file to your device and extract firmware.nb0 file from it. (For zip file extraction, you can use ES_explorer).
And then install it using your stock recovery.
After installation system will boot in your current ROM. Reboot into recovery and you will find recovery menu instead of stock.
Disclaimer: I am not an expert in creating nb0 file. Here I have just deleted all unnecessary files from stock nb0 file and replaced recovery image with recovery menu's image. So far this works on my device. I have tried it installing when I am on stock ROM. (Though it was not necessary)
I am not to be held liable/responsible if you damage your phone by following / not following this post.
MD5SUM hash code:
0b72eea3bc419bc66d64173df193a915 firmware.nb0

Compiled ROW CWR image and ROW diff discussion

UPDATE(Feb 07, 2012): Updating this with most recent info and installation instructions:
ROW 16GB with /data/sdcard fix
http://everyrandom.com/files/download.php?file=381ventana_recovery_row_16.img
ROW 32GB with /data/sdcard fix
http://everyrandom.com/files/download.php?file=165ventana_recovery_row_32.img
ROW 64GB with /data/sdcard fix
http://everyrandom.com/files/download.php?file=656ventana_recovery_row_64.img
Again, use at your own risk. 32GB and 64GB versions have not been tested.
NOTE: Backup has been tested, but recovery hasn't, though I'd be surprised if it didn't. This is a USE AT YOUR OWN RISK image. Also, I noticed my tablet rebooted once or twice while attempting to backup. This was likely due to the 9% battery indicator, but I figure I'd warn you just in case. If you leave your tablet to backup and you get back to it and you see your launcher unlock screen, it rebooted and likely didn't finish so you'll have to try again(again, I'm pretty sure this was just due to me having run down my battery).
WARNING: The following assumes you haven't installed any CWR image yet. If you've already installed CWR successfully, follow the 'Update Steps'.
Installation Steps:
Code:
adb push recovery_ventana_row16.img /data/local/
adb shell
su
mount -o rw,remount /system
cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.backup
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
dd if=/data/local/recovery_ventana_row16.img of=/dev/block/mmcblk0p1
Uninstallation Steps:
Code:
adb shell
su
mount -o rw,remount /system
cat /system/etc/install-recovery.sh.backup > /system/etc/install-recovery.sh
dd if=/system/recovery-from-boot.p of=/dev/block/mmcblk0p1
Update Steps:
Code:
adb push recovery_ventana_row16.img /data/local/
adb shell
su
mount -o rw,remount /system
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
dd if=/dev/block/mmcblk0p1 of=/data/local/recovery_backup_image.img
dd if=/data/local/recovery_ventana_row16.img of=/dev/block/mmcblk0p1
If CWR randomly reboots on you when you either try to do a backup or simply stay on the menu too long, try the following(thanks stewarta):
Boot into CWR. Then select to reboot the device(not "Reboot recovery", just the normal reboot).
Allow it to boot into full Android.
Reboot the device again and re-enter CWR. It should no longer be rebooting.
I don't know why the above happens or fixes it. If it doesn't work for you, please do the following:
Boot into CWR. Either wait at the menu screen or attempt a backup(we want to provoke a reboot)
On reboot, hit Vol+ to enter CWR again.
Select 'Advanced'.
Select 'report recovery'. It will tell you at the bottom where the log is stored. Make a note of it.
Boot into full Android and use your favourite file manager to get the log. Paste its contents in this thread.
And once again thanks to Koshu, logxen and jcase and everyone else involved. They did most of the work. I mostly just hit "make".
____________________________________
So with that out of the way:
The kernel is the only change between jcase's port and the ROW version. The BuildConfig and such are untouched.
So why does it work? I would imagine a recovery image would be beyond caring about region of even the kernel version of the main OS. I can't imagine they'd have altered the hardware between builds, especially as ROW merits as much attention as bundling Canada and Berlin...
So, any ideas as to what could cause the difference? Could it be the nvflash signing keys? Could there be a driver inconsistency? Anyone have any ideas on how to troubleshoot at that level seeing as it doesn't look like Android even logs anything that early in the boot process.

Many thanks to realyst2k and every one made this work.
Just wondering can we replace the ROW rom with the US rom in CWR? The lenovo ftp already has a US image.

fhing said:
Many thanks to realyst2k and every one made this work.
Just wondering can we replace the ROW rom with the US rom in CWR? The lenovo ftp already has a US image.
Click to expand...
Click to collapse
I didn't do anything but make using the ROW kernel extracted from my tablet. Koshu and jcase deserve those thanks more than I.
As far as a US image, go to the following post. Koshu has US CWR images for all models.
http://forum.xda-developers.com/showpost.php?p=21992089&postcount=106

Once again thank you realyst2k for compiling CWR for ROW.
I have TPT ROW 16GB. I backuped with no problem. Only one question, when backuping /data folder it skips /data/media folder which is internal memory same as /mnt/sdcard. From one side it's OK because it can contain up to 10G data and it would be hard to backup it, but from other side resetting to factory defaults also deletes /mnt/sdcard and so you need backup it also. I am little confused?!?!?! What is the situation in other tablets with internal storage?

It skips that mountpoint on purpose. I believe this is how the Transformer does it too. The reasoning aside from potentially gigantic backups and recoveries, is that it can also prevent a proper backup since it could easily overpower the filesystem on some SD cards(especially if you consider the 32GB model).
It's not needed in any case. CWR is made to do a NAND backup, which are your OS files and such. You can use Titanium Backup if you need to backup your media.

@realyst2k:
(SOLVED)

stewarta said:
@realyst2k:
I couldn't get this to work:
I followed the UPDATE steps but even though the file permissions are okay (rw-rw-rw) it could not read the file at the last step. Probably something simply ....
Click to expand...
Click to collapse
Make sure the image file actually is in your /data/local directory(you can use a file manager like root explorer).
If it's named differently(remember, it's case sensitive), adjust the name in the dd command accordingly.
If it isn't there, put it there(again, you can use root explorer if you have trouble using the the adb push command).

realyst2k said:
Make sure the image file actually is in your /data/local directory(you can use a file manager like root explorer).
If it's named differently(remember, it's case sensitive), adjust the name in the dd command accordingly.
If it isn't there, put it there(again, you can use root explorer if you have trouble using the the adb push command).
Click to expand...
Click to collapse
Thanks for the speedy reply. That was the first thing I checked .... the second was that I can still do Nand backups ... and I can. I'll copy it into the directory and try that command line again.
---------- Post added at 03:31 AM ---------- Previous post was at 02:54 AM ----------
realyst2k said:
Make sure the image file actually is in your /data/local directory(you can use a file manager like root explorer).
If it's named differently(remember, it's case sensitive), adjust the name in the dd command accordingly.
If it isn't there, put it there(again, you can use root explorer if you have trouble using the the adb push command).
Click to expand...
Click to collapse
@realyst2k: Guess what it was .... the download file name is ventana_recovery_row_32.img. Compare that with the command line below ...
dd if=/data/local/recovery_ventana_row_32.img of=/dev/block/mmcblk0p1
So that was never going to work until I renamed the file. Duh! Boots into CWR, so I did my usual trick of booting into CWR, doing nothing and booting back into Android OS. Now back in CWR and doing a Nandroid backup without any issues at all. So thank you once again.
Might uninstall CWR over Easter and get OTA2. Perhaps not ... might just wait for ICS in May/June.

OTA 2 and Root with CWR
@realyst2k Being impatient, I decided to rename the install-recovery.sh and the install-recovery.sh.forrecovery and install the OTA and see what was what.
It installed fine. I've lost root, so I will have a go at using the original method of rooting the TPT. Oddly, Root Explorer works, but SuperUser (chainsdd) is not logging this fact. NSTools seems to work as well (reports the scheduler is Noop).
Anyway, long story short, I will report more tomorrow. When I have more time.
Happy Easter.

OTA2 = No Root
(SOLVED)

OTA 2.5 + Root + CWR
Yay! I am back in business with root after installing OTA 2.5. For the low down, use this new exploit. But make sure you have the right drivers and lines in the android_winusb.inf file (Do a check using adb devices in a command window while the TPT is connected and in recovery mode. If no device is reported go into Win Device Manager and check out if you have Android phone showing or Portable device with a MTP driver--the latter is WRONG and you need to get the correct driver loaded otherwise you get the errors being reported by many others):
Code:
[Google.NTamd64]
;
;NVIDIATegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
;
;NVIDIA Tegra %SingleAdbInterface% = USB_Install, USB\VID_17EF&PID_741C
%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_741C&MI_01
;
;Lenovo Think Tablet
;%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_741B&MI_01
;%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_741C&MI_01
;%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_741D&MI_02
;%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_741E&MI_02
His script does work. Even without a factory reset. So now I have 0089_ROW with root. And yes, I am now using 'Root Keeper' from Play Store.
And before you ask, realyst2k's method of gaining CWR works. Just make sure your first boot in CWR is only to reboot back into the OS. Then on your next boot into CWR, you can do a Nandroid backup without any unintended boots and the like. This means boot into CWR from shutdown using Vol+ and Pwr, then Vol+ after the vibration (do not use such as Rom Manager). Enjoy!

Doesn't work for my TPT 64GB.
I'm ready to trace/play/debug/... to get it work

I'm still working on it but for some reason I have the MTP USB and the Android Phone listed in Device Manager, I thought it was suppose to be one or the other.
Also, if I'm reading your post right I should check in windows device manager while the tablet is in recovery, correct? That is when I see Android Phone > Lenovo ThinkPad Tablet ADB Interface and farther down Portable Devices > MTP USB Device. The MTP USB Device always tries to install whenver I plug or unplug the tablet and always fails, but the Android Phone part always does fine.
For what it's worth it didn't matter that I had both devices that ended up working.

josh451 said:
I'm still working on it but for some reason I have the MTP USB and the Android Phone listed in Device Manager, I thought it was suppose to be one or the other.
Also, if I'm reading your post right I should check in windows device manager while the tablet is in recovery, correct? That is when I see Android Phone > Lenovo ThinkPad Tablet ADB Interface and farther down Portable Devices > MTP USB Device. The MTP USB Device always tries to install whenver I plug or unplug the tablet and always fails, but the Android Phone part always does fine.
For what it's worth it didn't matter that I had both devices that ended up working.
Click to expand...
Click to collapse
Yes, I think that as long as the Android phone driver from Lenovo is there it will work. But if it is Portable Devices > MTP USB Device on its own, it will not. Well done!

I'm an idiot !
Links are not dead, for those looking for files you need to wait for a reservation ticket. Too impatient

Great work, thx!
As a TPT 32Gb user, had to rename files on cmdline then all went well.
Just one question: any way to activate emmc instead of using external SD to work with recovery?
I do know it is achieving by patching recovery.fstab, but don't know what exactly should be added..

As for differencies:
My try was to install WE system image on ROW, I succeed. After trying to install also boot image it loops at first lenovo logo.. and as kernel source is common the remainig thing is ramdisk oO

i have CWM-based Recovery v5.0.2.7
trying to load firmware:
ThinkPadTablet_A310_03_0069_0121_ROW.zip
or
ThinkPadTablet_A310_02_0039_0089_ROW.zip
- install zip from sdcard
- toggle signature verification
- choose zip from sdcard
Choose any of the
ThinkPadTablet_A310_03_0069_0121_ROW.zip
ThinkPadTablet_A310_02_0039_0089_ROW.zip
and get a 20-30%% check the exact same error:
E:failed to veryfy whole-file signature
E:signature verification failed
Installation aborted
if you try to upgrade without checking the signature, I get this error:
assert failed: getprop ("ro.producrt.devices") == "Indigo" || getprop ("ro.producrt.product") == "Indigo"
E: Error in sdcard/ThinkPadTablet_A310_.................
(Status7)
Installation aborted
anyone have any ideas what? to upgrade
recovery of stock recovery (Uninstallation Step) it does not help
TPT refuses to respond to the button VOL+ and continue to load.

the problem was resolved. need to recover after the stock bootloader
adb shell
$ su
dd if=/system/recovery-from-boot.p of=/dev/block/mmcblk0p1
Click to expand...
Click to collapse
TWICE TPT reboot, reboot, and the second is already possible to enter the recovery boot (Vol+)
---------- Post added at 05:05 PM ---------- Previous post was at 05:02 PM ----------
new problem: how to install the CWM on 0121_ROW firmware. instruction from the first post does not fit.

CWM Recovery and ICS 4.0.3
Anyone got a CWM Recovery for ICS 4.0.3. ICS sure brings the TPT alive ... but I'd like to be able to do a Nandroid backup so I can stay that way. OTARootkeeper ensured I have root access, so that is a big help.
---------- Post added at 08:16 AM ---------- Previous post was at 08:03 AM ----------
Driver'z said:
i have CWM-based Recovery v5.0.2.7
trying to load firmware:
ThinkPadTablet_A310_03_0069_0121_ROW.zip
or
ThinkPadTablet_A310_02_0039_0089_ROW.zip
- install zip from sdcard
- toggle signature verification
- choose zip from sdcard
Choose any of the
ThinkPadTablet_A310_03_0069_0121_ROW.zip
ThinkPadTablet_A310_02_0039_0089_ROW.zip
and get a 20-30%% check the exact same error:
E:failed to veryfy whole-file signature
E:signature verification failed
Installation aborted
if you try to upgrade without checking the signature, I get this error:
assert failed: getprop ("ro.producrt.devices") == "Indigo" || getprop ("ro.producrt.product") == "Indigo"
E: Error in sdcard/ThinkPadTablet_A310_.................
(Status7)
Installation aborted
anyone have any ideas what? to upgrade
recovery of stock recovery (Uninstallation Step) it does not help
TPT refuses to respond to the button VOL+ and continue to load.
Click to expand...
Click to collapse
Slip across here as there may be quite a few reasons for this.

[Q] HELP! :( Semi Bricked. Tried EVERYTHING

Ok
Please forgive me I have spent up to 7 hours today searching and trying but to no luck.
So I didnt realise what i was doing and Semi Bricked my Phone. I edited build.prop and saved it in MyExplorer(name?) to try and turn off the camera sounds and when I rebooted, it just gets stuck on the galaxy S 2 screen, boot loop.
I'm on SGSII (Australia) Stock Vodafone's ICS 4.0.3 Rooted.
I have CWM installed but tried a few things:
- I can get into Download MOde (no idea what to do here)
- I can get into CWM mode 5.0.2.7 Recovery mode but cant do anything still.
- I tried various Edify script builders to try and put the original build.prop back in but get multiple Status 0 errors whenever I try update.zip from the SD card.
- I tried rebuilding the backup on there and changing the build.prop file on there and trying to restore but MD5 check fails. Even tried rebuilding the MD5 file with the modified files and still no luck. MD5 files fails.
Would anyone have any suggestions and how to resolve this without a flash or wipe? I didnt back recent backup and will lose everything.
I am coming to a point where I really am wanting to back to Apple
There are 2 build.props attached. One is the bad one that stopped me from booting up and I found another one that was named .bak (extension taken off) I found in the same directory (/SYSTEM)
If anyone can help me build an update.zip to push in via CVM I would greatly be in your debt (I tried for 4 hours with no luck)

If you have recovery and download mode yet nothing is lost.
In first, do saved your apps ?
If you had saved them or if it doesn't matter to you, reflash a rom via recovery
LINK HERE:
http://download.cyanogenmod.com/get/jenkins/2773/cm-9-20120615-NIGHTLY-galaxys2.zip
Flash it GoogleApps folder
http://goo.im/gapps/gapps-ics-20120317-signed.zip
The rom that I attached to the reply is a CM9 ICS version, it's quitly stable and we can have some settings on it.
If it doesn't work reflash with Odin (it's with software who use the Download Mode)
http://hotfile.com/dl/149514867/aea2f22/I9100XXLPQ_I9100OXALPQ_XEO.zip.html
Instructions
-Unzip the Rom Folder ( I9100XXLPQ..........)
-Open the included Odin
-Put your phone on Download Mode
-Click PDA and select I9100_CODE_I9100XXKP*_CL*_REV02_user_low_ship.tar.md5
-Click PHONE and select MODEM_I9100XX*_REV_02_CL*.tar.md5
-Click CSC and GT-I9100-MULTI-CSC-OXA*.tar.md5
-Click Start and don't touch anything still the colored case become green
-And now your phone resurrects
Reply me of results

thanks for your reply
unfortunately i didnt save my apps and havent got backups of my data either
i cant reach the file via ADB either, when i run ADB (have KIES installed and worked before) - adb devices.
nothing shows up when the phone is stuck on "Samsung GS2" screen.
do you have any recommendations around keeping my data there?

If you find the exact same software your on now to download you could try flashing that in cwm without wipes I think that would work i think it replaces all system stuff so it will work, worth a try
Sent from my GT-I9000 using xda premium

understood thanks
what if i just want to flash build.prop via update.zip?
i tried so many methods but it always fails. is anyone able to create a update.zip for me?

i used a GUI script creator to try and update it via CWM recovery mode but it doesnt seem to like it.
If i turn off signature verification, it gives me a (status 0) error saying : E: Error in /sdcard/update.zip
and if i turn on verification toggle, it says E: signature verification failed
can anyone help?

calum96 said:
If you find the exact same software your on now to download you could try flashing that in cwm without wipes I think that would work i think it replaces all system stuff so it will work, worth a try
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
i know there are 2 types of ROMS right? the nonwipes and wipes. i really dont want the wipe versions.
the one i downloaded is 1G which i'd imagine is the wipe version if i were to upgrade via odin?
http://www.androidaddicted.com/firm...-vodafone-australia-firmware-update-1267.html

Can you mount any sd on your pc, because you can the recovery mount trick to access to your data.
When you are in the recovery menu, go to mount and storage and click on "mount usb storage" and the internal and external sd will appear on your pc.

you are posting in galaxy s thread....repost in galaxy s2 thread

I don't think so but then again I don't own a s2 but you can select advanced restore: restore data then flash a compatible ROM, then restore the data if you worried but as I said before flashing the same ROM shouldn't remove user data
Sent from my GT-I9000 using xda premium

S5830 wont boot after I fiddled with the software

Hi,
I have a S5830 which was running CWM - not sure exactly what version but worked perfectly, and had CFW CyanogenMod (I think 7.2.0 if I remember correctly)
I did something stupid, I had a few bugs which were annoying me so thought I'd go back to OFW, I downloaded a couple from Tsar3000 which I tried flashing through Odin but It would just go for ages and not seem to progress. I can get in download mode but I dont know toe process to take to now get me back on official fw with original recovery. I have downloaded the stock recovery image zip file from this website but when ever I try and flash anything Odin just seems to not progress. I can no longer boot into recovery mode.
What shall I do from here please?
Thanks

Seems weird, are you sure you did flash it correctly?
How to flash with odin.
Flashing the newest firmware:
1) Turn off your phone
2) Remove your SIM Card and SD Card
3) Extract previously downloaded firmware
4) Open ODIN 4.38 on your PC
5) Select from extracted archive: OPS-OPS, Boot-APBOOT, Phone-MODEM, PDA-CODE, CSC-CSC (leave EFS and One Package empty)
6) Connect your phone via USB into PC
7) When the screen is turned on hold POWER+VOLUME DOWN+HOME and wait until the phone enters the Download Mode
8) If ODIN detected and recognised your phone should light up the first square to the left side
9) Press "Start" button and wait, the process should take ~5 minutes
10) If all goes well your phone should reboot automatically
11) Square should change the color to blue and display "PASS" it means that flashing process was successful and we have the newest firmware
12) Disconnect your phone
13) Turn off your phone
14) Insert your SIM Card and SD Card again
15) Turn on your phone
16) Now you have the newest firmware!
If you did try, pushing CWM with Odin.
Flash Custom Recovery:
1) Push recovery-clockwork-5.0.2.6-galaxyace.img to your device using Android Debugging Brige push recovery-clockwork-5.0.2.3-galaxyace.img /tmp/" command
2) Turn off your phone
3) Press POWER+HOME BUTTON
4) Login to your device over "adb shell"
5) Mount /system using "mount /dev/block/stl12 /system" command
6) Flash CWM recovery using "flash_image recoveryonly /tmp/recovery-clockwork-5.0.2.3-galaxyace.img" command
7) Umount /system using "umount /system" command
8) Reboot your device using "reboot recovery" command to test your new CWM recovery
9) Reboot your device[/QUOTE]
Then flash Stock Recovery, from CWM. - Download it Here. Use the version appropriate to your Android version.

reply
Hi,
Thanks for the reply. I tried everything you said except flashing the custom recovery with the method you said. The download link you provided for the recovery unfortunatly doesn't work So I downloaded from another link on the forum, but when I try and push the file ADB just doesnt find the device. Note: I can only get in download mode.
Do you know another way I can do this?
Thanks for your help

reply
Hi,
I tried what I did th efirst time, Odin + Ops + Custom Recovery - One package etc and its worked this time, only difference is did it on another PC, Still 7 x64. Dont kno whats different but phone now boots again so i can start from the beginning.
Thanks