Related
★ [ROM] ICS alpha ★ Latest update: 14/01/12 ★ [TUT] Unbrick ★ Kernel sources ★
Instructions, as given by NotionInk via support mail, to bring your Adam back to life.
For the latest official rom-update & kernel source refer to the second post.
(Advanced users can directly jump to its last paragraph!)
How to flash your Adam and get it working again
WARNING
This fix is recommended only if your Adam has stopped booting up after installing the over-theair
system update on 24 January. Please don't use the method indicated to flash your Adam
with any ROM not from Notion Ink, as it would probably damage your Adam irreparably.
Please read this whole document before proceeding.
PRE-REQUISITES
You need to have the following items
1. A Windows or Linux PC
2. The Notion Ink Adam you wish to flash
3. A mini-USB to USB cable for connecting the two
(It's not included in the Adam package, but you
might have one lying around. If not, it's readily
available in any electronics shop)
4. The appropriate Adam Recovery Kit which you
can download from the URLs below. (About
80MB)
DOWNLOADS
1. Windows PC, LCD Adam http://api.notionink.com/fix/windows/LCD.zip
2. Windows PC, Pixel Qi Adam http://api.notionink.com/fix/windows/PixelQi.zip
3. Linux PC, LCD Adam http://api.notionink.com/fix/linux/LCD.zip
4. Linux PC, Pixel Qi Adam http://api.notionink.com/fix/linux/PixelQi.zip
OVERVIEW
Here's a summary of what you'll be doing:
1. On your PC, extract the Adam Recovery Kit.
2. Restart your Adam in “Force Recovery” mode and connect it to the PC.
3. If you're on Windows, install the USB drivers from the Recovery Kit.
4. Run the ROM flash utility from your PC, and wait for it to complete.
1. EXTRACT
Using your favourite ZIP extraction tool, uncompress all the files in the Adam Recovery Kit to
any folder on the hard drive of your computer.
2. RECOVERY MODE
Before proceeding, ensure that your Adam has at least 50% battery charge or is connected to
power and charging. Also make sure that your computer will not turn off during the flashing
process.
Turn off your Adam and enter force recovery mode by pressing and holding both the Volume
Down (-) and Power buttons for two seconds. The orange (charge) and red (CPU) indicators on
the right side of your device will light up, indicating that your Adam is in force recovery mode.
Release both buttons, and connect the mini-USB port on your Adam to any free USB port on the
PC using your cable.
3. INSTALL DRIVERS (Windows only)
Your Windows PC will show a notification that a device “APX” has been detected. If you get a
“Found new hardware” dialog box asking where to install drivers from - choose “list or specific
location”. If you don't get this dialog, open the Device Manager via System in the Control
Panel, find and double-click the “APX” device, and click the update driver button.
Select the “usbpcdriver” folder inside the extracted Adam Recovery Kit as the driver location.
You may receive a warning that the driver is not certified or signed by Windows – choose to
install it anyway.
4. FLASH
You're now ready to flash your Adam. Make sure that the USB cable is connected securely. To
begin the process under Windows, run the “download.bat” batch file from the folder where you
extracted the Recovery Kit. If you're using Linux, open a console window at the folder
containing the extracted Recovery Kit, and run ./download.sh. Your device screen will show that
it is being updated, and the console window will show the progress.
IMPORTANT: Do not close the console window or stop the update before it is complete. If the
update is interrupted mid-way, your Adam will be damaged irreparably.
Hopefully all goes well, and in a couple of minutes your Adam will boot up with the new
software. Congratulations! If at any point you find that things aren't going according to plan,
please send an email to [email protected] rightaway.
Thanks for your continued support
Team Notion Ink
Click to expand...
Click to collapse
Latest official rom update & instructions as given by NotionInk support:
Greetings from Notion Ink!
We are glad to inform you that an update for your Adam is now available.
Please click on the appropriate link provided below, based on your Adam variant and your current Operating System to download the update file.
LINUX
http://notionink.com/45-flash/flash_3gAUO.zip For LCD WiFi 3G
http://notionink.com/45-flash/flash_wifiAUO.zip For LCD WiFi
http://notionink.com/45-flash/flash_wifiPQ.zip For Pixel Qi WiFi
http://notionink.com/45-flash/flash_3gPQ.zip For Pixel Qi WiFi 3G
WINDOWS:
http://notionink.com/windows/flash_3gAUO-W.zip For LCD WiFi 3G
http://notionink.com/windows/flash_wifiAUO-W.zip For LCD WiFi
http://notionink.com/windows/flash_wifiPQ-W.zip For Pixel Qi WiFi
http://notionink.com/windows/flash_3gPQ-W.zip For Pixel Qi WiFi 3G
In order to update your Adam, you would have to follow a few simple steps detailed in the manual below.
You can download the manual here http://notionink.com/45-flash/Instruction-Manual.pdf.
All the necessary information required to update your Adam are present in these files.
Please note, that after this update, you would be able to install all subsequent updates using the 'Update Adam' feature under Settings.
A summary of the fixes in this update can be found here http://notionink.com/45-flash/Update-Summary.pdf.
In case you need any assistance, please contact us at [email protected]
Warm Regards
Notion Ink
Click to expand...
Click to collapse
The above update will enable the inbuilt Adam update feature.
From here onwards all coming updates can be done directly by Adam OTA (Over The Air).
Just follow the instructions below.
Dear Customer,
Greetings from Notion Ink!
We are glad to inform you that an update for your Adam is now available.
In order to update your Adam, you would have to follow a few simple steps detailed below.
Your Adam will need to be connected to a wi-fi network in order to download your update.
CHECK! Navigate to Settings > About Adam, and check the 'Build Number. Is it NIA20270111 / NIA20040211 / NIP20270111 / NIP20040211 (or higher)
If yes, then proceed.
If no, please install the previous update we had made available.
IMPORTANT! Please back up all your data on the Adam before attempting this update. We also recommend that you connect your Adam to the mains power supply during the update process.
CHECK! Please make sure that you have set the correct date and time on your Adam before your proceed with this update. (Settings > Set Date & Time)
Please follow these steps to update your Adam.
1. Restart your Adam.
2. Navigate to Settings > Update Adam and tap on it.
3. Now, a dialog box will open saying there is an update available for download. You can choose whether to start the download or cancel it.
4. Once you tap on 'Start' in the dialog box, your Adam will start downloading the update file. You can view the progress of this download in the notification bar.
5. Once the download is finished, a message will appear in the notification bar saying that your update is ready for installation. You can either choose to apply this update or choose to install it at a later time, in which case you can do so following the same steps above.
6. The update will now install and your Adam will restart.
You can also pause / resume your download by tapping on the download progress bar under notifications.
In case you need any assistance, please contact us at [email protected]
Warm Regards
Notion Ink
Click to expand...
Click to collapse
Latest official rom (NIxx20080611):
http://notionink.com/updates1/a0/update.zip For LCD WiFi
http://notionink.com/updates1/auo/update.zip For LCD WIFI & 3G
http://notionink.com/updates1/update.zip For Pixel Qi WiFi
http://notionink.com/updates1/PQ/update.zip For Pixel Qi WiFi & 3G
Kernel Source:
https://github.com/notionink
Gingerbread pre-alpha ROM (nvflash only):
http://developers.notionink.com/testimage23/2.3prealpha/nvflash.zip
UPDATE:
ICS Android 4.0 Alpha:
https://github.com/rrathi/adamICSImage
Gapps (flash after ROM for market access, gmail etc.):
http://www.multiupload.com/A2M9OB4FSS
Kernel:
https://github.com/EnJens/android-tegra-nv-2.6.39
Adam ICS Source:
https://github.com/rrathi/adamICS
It probably makes more sense to keep the first post up to date with the latest links... in case someone comes here from a Google search, you wouldn't want them flashing their Adam with old firmware if they were just quickly reading through the thread.
There is a file called "microboot.bin", which is only present in the "fix-rom" and not in the "update-rom".
I don´t know about its importance to properly revieve a semi-bricked adam, but that´s why i was hesitant to just update the links and made a second post instead.
If someone could maybe clarify it´s importance in the "fix-rom"?!
THX ;-)
Good stuff, thanks for your work in gathering this info.
Need help... Recovery may be borked
Got my adam yesterday... booted it up, connected to wifi, and installed the OTA update. Played around a bit, everything working ok, then copied some files over via usb to see if I could side load some apps.
Adam did not recognize my new microsd card, so I removed the microsd and powered down, then booted into recovery.
I got an error message in recovery:
E:Can't mount /dev/block/mmcblk3p1
(no such file or directory)
E:Can't mount SDCARD:recovery/command
Then, put the new sd card back in, rebooted to recovery again, got the same messages, and an additional "Can't mount SDCARD2".
Took the sdcard out, rebooted, surfed the net, etc... Then rebooted to recovery again and got:
E:Bad boot image
"ions"
E:Can't mount /dev/block/mmcblk3p1
(no such file or directory)
E:Can't mount SDCARD:recovery/command
So... I find this thread, followed the directions to a tee. Saw all the right things on the computer and on Adam.
Adam rebooted at the end and went back to the home screen. Surprise! Nothing was overwritten... same bookmarks in browser, same wifi connection, etc...
So I boot into recovery and get the same error as the top one above.
Did NI change / lock the recovery? ...it says (3e) and/or did something get sideways here that I don't know about? Why did I not get a clean install after following the steps above?
Is there a way to just re-push the stock recovery (or clockworkmod) via adb or nvflash?
Any help would be appreciated...
ssmithri said:
Is there a way to just re-push the stock recovery (or clockworkmod) via adb or nvflash?
Any help would be appreciated...
Click to expand...
Click to collapse
You should be able to update to ClockworkMod even with those error messages. You can either copy the update.zip to your SD card or copy it directly to the root of the Adam memory. Then run the update using the stock recovery via Volume + and Power.
joshua.lyon said:
You should be able to update to ClockworkMod even with those error messages. You can either copy the update.zip to your SD card or copy it directly to the root of the Adam memory. Then run the update using the stock recovery via Volume + and Power.
Click to expand...
Click to collapse
Agreed... but I have tried that.
When I do apply internal sdcard:update.zip, a little droid just sits there staring at me... forever...
ssmithri said:
Agreed... but I have tried that.
When I do apply internal sdcard:update.zip, a little droid just sits there staring at me... forever...
Click to expand...
Click to collapse
I had the same thing happen to me. If I remember correctly, I actually had to use the power button as the "select" button. Using the menu button would just give me the blank screen with just the droid staring back.
Additionally, after doing the update to ClockworkMod (and subsequently installing EdenX), I had to use the Clear Cache feature of ClockworkMod to get the tablet to boot into the regular OS. Before clearing the cache, each time I would power on the device it would just boot into recovery mode.
PS. I was in the latest batch that was shipped -- just got mine yesterday. In the original Dec 9 order and "shipped" Feb 14.
joshua.lyon said:
If I remember correctly, I actually had to use the power button as the "select" button. Using the menu button would just give me the blank screen with just the droid staring back.
Click to expand...
Click to collapse
That was it!!!
Thank you so much
I tried unbricking but after the formatting part I get the following error.
sending file: bootloader.bin
| 941356/941356 bytes sent
bootloader.bin sent successfully
sending file: mbtdata.img
- 1024/1024 bytes sent
mbtdata.img sent successfully
sending file: recovery.img
| 3860480/3860480 bytes sent
recovery.img sent successfully
sending file: boot.img
- 3184640/3184640 bytes sent
boot.img sent successfully
sending file: system.img
| 458752/128154048 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
Any idea what this means? Any help anyone?
Sounds like your image is corrupted. Would try to redownload the files. ;-)
halcyon13 said:
I tried unbricking but after the formatting part I get the following error.
sending file: bootloader.bin
| 941356/941356 bytes sent
bootloader.bin sent successfully
sending file: mbtdata.img
- 1024/1024 bytes sent
mbtdata.img sent successfully
sending file: recovery.img
| 3860480/3860480 bytes sent
recovery.img sent successfully
sending file: boot.img
- 3184640/3184640 bytes sent
boot.img sent successfully
sending file: system.img
| 458752/128154048 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
Any idea what this means? Any help anyone?
Click to expand...
Click to collapse
Happen to have links to the update.zip files for each?
when trying to run download.sh in ubuntu, i get this error...
./nvflash: command not found
Internal SD card
joshua.lyon said:
You should be able to update to ClockworkMod even with those error messages. You can either copy the update.zip to your SD card or copy it directly to the root of the Adam memory. Then run the update using the stock recovery via Volume + and Power.
Click to expand...
Click to collapse
Mine did the same until I had Win 7 repair the internal SDcard. Others had told me to wipe it. After that no problemos.
First post updated with Ice Cream Sandwich pre-alpha ROM incl. kernel & source
Post 1, as seen on here as well http://notioninkhacks.com/forums/viewtopic.php?f=63&t=327&hilit=unbrick does what you want. The bin file in here has nvflash. I did roughly the same as you, hadn't turned on the Adam for ages, had to nvflash it before doing the ICS update. Make sure you put the ICS files on the internal SDCARD, I got those mount errors as well all the way through
as topic, i just flash SBF and got error applying the update due to previous OTA.
so i follow the command: rm -f /system/etc/install-recovery.sh
but where do i enter this command when im only suppose to boot into recovery with only the 4 options available?
You can enter commands like these either on your phone through an app like "Terminal Emulator", or via an adb shell through your computer.
sorry for being noob, do i need to install anything?
What are you trying to achieve? Flash custom Rom?
Sent from my GT-I9100 using Tapatalk
im trying to install OR.
As i read from the dev forum, i will need to write that command if i ever did a OTA on my phone before..
Dowload and extract OR to your sdcard.
Install vulnerable recovery sbf using rsdlite. Google for it and use the correct version based on your bootloader, 90.78 or 90.74
Once the phone switches off and before it shows the moto logo, press and hold the X button. It should show you triangle with exclamation mark. Press volume key and camera button. It should show you recovery menu. Choose the second option APPLY SDCARD UPDATE.ZIP.
OR will load now. Type the command after choosing console from menu.
Sent from my GT-I9100 using Tapatalk
yes i did everything until the OR part, installation of OR failed due to signature verification failed.
from what i read i need to insert the command to remove some system file due to previous OTA.
ok i got it, i thought the vulnerably recovery is the SBF 2.1.
sorry my mistake and thanks!
immortal283 said:
ok i got it, i thought the vulnerably recovery is the SBF 2.1.
sorry my mistake and thanks!
Click to expand...
Click to collapse
http://android.doshaska.net/rootable
yea got it thanks!
anyway 1 quick question, do i get any confirmation message after i type in that command at the console?
No, you won't get a confirmation. As with most linux commands, you'll only be notified in case something goes wrong. So no notification generally means that you're good to go
When doing the flash using nvflash from Restore dell streak 7 (wifi only) using nvflash at:
http://forum.xda-developers.com/showthread.php?t=1252840
It starts out good but dies on p11.img. I am getting the below error on my DS7 (wifi), unrooted, when it gets to p11.img:
sending file: p10.img
/ 16777216/16777216 bytes sent
p10.img sent successfully
sending file: p11.img
- 30474240/352321536 bytes sentdata send failed NvError 0x120002
command failure: writedeviceraw failed (bad data)
Click to expand...
Click to collapse
Any advice how to get the process to finish?
Thank you!
Try to redownload p11, and then flash again. You might have gotten a bad file download.
Xi2wiked said:
Try to redownload p11, and then flash again. You might have gotten a bad file download.
Click to expand...
Click to collapse
I did unzip p11 from the master zip file I had downloaded (got the same error), I could try the download again...
Xi2wiked said:
Try to redownload p11, and then flash again. You might have gotten a bad file download.
Click to expand...
Click to collapse
Hey, it WORKED! Thank you!
I never would have thought it was a corrupted download. I was convinced I was doing it wrong. But, now I am back to Android 2.2 Froyo and am happy as can be!
Hi. Wanted to install enigma rom, but I had some problems. When wanted to flash the system using fastboot - there was an error, not enough space. Then I tried with clockwork, didn't work either.
After that I noticed that I have to change size of partitions, went to this thread - http://forum.xda-developers.com/showpost.php?p=15901109&postcount=23 , downloaded System: 250 Data: 134, tried to flash it. But again a f**king error -writing appsbl failed (remote: unknown partition).
Googled it, but didn't found nothing useful. Would be very glad, if someone here would help.
ejnahuj said:
Hi. Wanted to install enigma rom, but I had some problems. When wanted to flash the system using fastboot - there was an error, not enough space. Then I tried with clockwork, didn't work either.
After that I noticed that I have to change size of partitions, went to this thread - http://forum.xda-developers.com/showpost.php?p=15901109&postcount=23 , downloaded System: 250 Data: 134, tried to flash it. But again a f**king error -writing appsbl failed (remote: unknown partition).
Googled it, but didn't found nothing useful. Would be very glad, if someone here would help.
Click to expand...
Click to collapse
Hi there glad your interested in enigma we have a nice release comming very soon
What are you using windows or linux?
If its linux remember sudo or su before the commands and to restart you terminal check permissions and do a clean wipe ex sudo ./fastboot -w
If using windows download mur4iks custom boot loader it works better than the pre made files for windows the pre mades where more for linux.
Sent from my tf101 using xda premium 1.54Ghz
Maybe I can't google it correctly, but I can't find mur4iks custom boot loader.
ejnahuj said:
Maybe I can't google it correctly, but I can't find mur4iks custom boot loader.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1171531
Ty for the link, did it 250;134. Now the system is sending, but after 3-4mins. It's failure again -data transfer failure (Too many links).
ejnahuj said:
Ty for the link, did it 250;134. Now the system is sending, but after 3-4mins. It's failure again -data transfer failure (Too many links).
Click to expand...
Click to collapse
Did you read the instructions carefully and are you running everything as administrator or root?
Sent from my tf101 using xda premium 1.54Ghz
ejnahuj said:
Ty for the link, did it 250;134. Now the system is sending, but after 3-4mins. It's failure again -data transfer failure (Too many links).
Click to expand...
Click to collapse
i Think your USB Port have something wrong and disconnect every 5 secs like mine
try another
cccb010 said:
i Think your USB Port have something wrong and disconnect every 5 secs like mine
try another
Click to expand...
Click to collapse
Nope, can flash any other roms without problems.
Danzano said:
Did you read the instructions carefully and are you running everything as administrator or root?
Sent from my tf101 using xda premium 1.54Ghz
Click to expand...
Click to collapse
There wasn't much to do, and yes I did everything correct. Cause if there wasn't enough space, there would be that error again, that there isn't enough space.
ejnahuj said:
Hi. Wanted to install enigma rom, but I had some problems. When wanted to flash the system using fastboot - there was an error, not enough space. Then I tried with clockwork, didn't work either.
After that I noticed that I have to change size of partitions, went to this thread - http://forum.xda-developers.com/showpost.php?p=15901109&postcount=23 , downloaded System: 250 Data: 134, tried to flash it. But again a f**king error -writing appsbl failed (remote: unknown partition).
Googled it, but didn't found nothing useful. Would be very glad, if someone here would help.
Click to expand...
Click to collapse
Download Mur4iks custom bootloader and then put ur phone into fastboot.
Connect phone to pc and check that all the fastboot driver has been installed.
Then open the bootloader and select ur system partition.. (data partition will
change auto) then click wipe data and then click flash partition..
Click reboot and then go into recovery and then flash enigma !!
Hey i think you should use the bootloadertool not the predefined one's maybe that works.
http://kulkoff.com/swift/ and then download the swiftbootloaderbuilder.zip.
extract into one folder ! it needs some additional files.
make backup with clockworkmod!
put the gt540 via usb , restart into fastboot mode before starting the bootloaderbuilder!
run the bootloaderbuilder.exe as administrator if using 7 / vista.
select partition sizes, flash bootloader. wipe & reboot.
restore an backup of your rom, flashable zips work too.
mur4ik said:
Mur4ik said:
Hi. Thats should be added in header that this "tool" has a requirements MS .NET frameworks 3.5 SP1 and adove.
Click to expand...
Click to collapse
SO THAT MIGHT BE THE PROBLEM TOO
I have 4.0 , but I did change the sizes correctly , the problem is now this - data transfer failure, too many links.
ejnahuj said:
I have 4.0 , but I did change the sizes correctly , the problem is now this - data transfer failure, too many links.
Click to expand...
Click to collapse
What is the problem causing? Can't you remove USB cable and u are done?
Sent from my GT540
The error is in fastboot, so I can't remove the usb. Can't install with recovery, cause there's always. - Installation aborted.
ejnahuj said:
The error is in fastboot, so I can't remove the usb. Can't install with recovery, cause there's always. - Installation aborted.
Click to expand...
Click to collapse
Recovery says always aborted ?
Sent from my GT540
andreas__ said:
Recovery says always aborted ?
Sent from my GT540
Click to expand...
Click to collapse
With enigma rom yes, with others no. I'm using 5.2.0.7.
ejnahuj said:
With enigma rom yes, with others no. I'm using 5.2.0.7.
Click to expand...
Click to collapse
Maybe dan knows which recovery to use?
Sent from my GT540
andreas__ said:
Maybe dan knows which recovery to use?
Sent from my GT540
Click to expand...
Click to collapse
Im using the same bro but i have been looking into these issues and think ive solved most of them
Sent from my tf101 using xda premium 1.54Ghz
I think I have done something quite stupid. I have a T Mobile Galaxy Tab (SGH-T849) running Froyo. It was completely stock and I had not rooted it.
I was curious to try Cyanogenmod, so I followed the instructions under "Installing the ClockworkMod Recovery" here:
wiki.cyanogenmod.com/wiki/Samsung_Galaxy_Tab_(GSM):_Full_Update_Guide
Even though the directions said it was for a Galaxy Tab on the stock 2.3 release, I forged ahead installed the ClockworkMod recovery image using Heimdall.
The tablet now does not get past the T-Mobile boot screen. I did not backup the original kernel.
I am not normally this stupid! I don't know if I can go to stock Gingerbread using the overcome.net guide as my tablet was not rooted.
Is there any way to restore my original kernel and start again?
I don't think you need to root.
You can use overcome method.
I believe Overcome only ask you to root first to make sure you don't have protected bootloader and to backup using Titanium Backup.
You don't need all that now.
Just go ahead and flash GB Stock Safe
using heimdall will be:
1) naturally unpack the GB_Stock_Safe_v5.tar
2) go to download mode
3) heimdall flash --repartition --pit ./gt-p1000_mr.pit --factoryfs ./factoryfs.rfs --cache ./cache.rfs --dbdata ./hidden.rfs --primary-boot ./boot.bin --secondary-boot ./Sbl.bin --param ./param.lfs --kernel ./zImage
4) at this point you can reboot to the stock rom.
I like heimdall a lot compared to Odin.
Unfortunately, that did not work. I get this error:
Uploading PIT
ERROR: Failed to confirm end of PIT file transfer!
PIT upload failed!
Ending session...
Rebooting device...
And then the tablet just displays the T-Mobile screen. Is there something else I can try?
what if you do it without pit ?
Doing this with the --verbose flag gives this:
Uploading PIT
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet.
ERROR: Failed to confirm end of PIT file transfer!
PIT upload failed!
Ending session...
Rebooting device...
I am doing this on a Mac and I see that this is a problem with the OS X version of Heimdall. I have an old Windows XP machine I can try to use.
Let me try that before omitting the PIT file.
Thanks!
The PIT file loads on Linux, but the kernel doesn't:
98%
File Part #59... Response: 0 0 0 0 3B 0 0 0
100%
ERROR: Failed to confirm end of file transfer sequence!
KERNEL upload failed!
Ending session...
Rebooting device...
Re-attaching kernel driver...
I'll boot up the old windows box and try that next.
BTW, don't use latest heimdall (1.3.2?)
use 1.3.1 I think
Edit: sorry, at in Mac use 1.3.0
http://forum.xda-developers.com/showthread.php?t=1655689&page=6
my ubuntu I have 1.3.1
This looks promising! I installed heimdall 1.3.0 on my Mac and was able to install everything successfully, then the tablet rebooted. It went to the recovery screen and I selected the reboot option.
It's been on the Samsung logo for about 20 minutes now. I don't know how long it will take but I'll let it sit overnight.
Thanks so much for your advice!
Not quite right.
Mine reboot to setup wizard upon flashing.
You did the complete parameters like I put there?
Do wipe all cache and data.
If still no go, reflash.
Sent from my GT-P1000 using xda app-developers app
Okay, I think that did the trick! I wiped the data and cache, and now it looks like everything is working! I will have to flash the T-Mobile modem file as well.
priyana said:
Not quite right.
Mine reboot to setup wizard upon flashing.
You did the complete parameters like I put there?
Do wipe all cache and data.
If still no go, reflash.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Seriously, I think you should be paid by Samsung Customer Service (Or Technical Support). You beat most of us on attending these problems! we P1000 users can't thank you enough!
just helping others
imagine if we don't help them out. The SGT7 will be collecting dust.
Priyana, if it hadn't been for you, my next step would have been shipping my Tab off to Samsung to be reset! As yappoe said, I can't thank you enough!
Something odd - even though I wiped the caches, and did a data/factory reset, much of my user data was on the tablet, such as pictures and some books I had downloaded. This was fortunate as I hadn't backed anything up, but it was curious.
I will make a backup before I work up the courage to flash ICS! Thanks again!
Hmm, I have never seen data survived a format.
However, having said that, I have proven to myself that when I did restock from AOKP mtd from, back to gb-stock safe using heimdall with pit file, and my internal SD intact.
People told me flashing with pit file ensure everything on internal SD is wiped out because it was repartitioned, but definitely not mine.
But, I heimdall flash and immediately flash overcome kernel without booting into the gb rom.
Sent from my GT-P1000 using xda app-developers app