Related
First off, I have searched and performed a few different recovery processes and my Tab is partially functional (FC's on a lot of apps)
I used Z4Root.
Next I used the Verizon_zImage to install CWR (converted to Ext4)
I installed the Dodexed Verizon from this forum
Everything ran fine for about a month
I started getting FC's on a lot of apps
Decided to revert to stock via this post: http://www.droidforums.net/forum/sa...84-how-restore-vzw-galaxy-tab-stock-dj11.html
Used Heimdall to flash the Cache, Param, factory, Kernel and Recovery
Following the directions, I booked into recovery (stock)
When I tried to wipe Data and Cache, is where the problems started
I get a bunch of errors about not being able to mount /Data
I have tried to get back to where I was with flashing the Verizon_zImage and wiping data and cache that way (seemed to work but all my apps and data are still there)
If someone can tell me how to get the Data wiped, I think I can get ther rest working...
Help please as I'm going to visit my brother this month and he's an Apple guy so I was going to show off how much better Android is...
Did you repartition with a PIT file? If you've gone to EXT4, I believe you need to repartition the device before you can go back to an RFS ROM.
Regards,
Dave
Can't find anything telling me how to do this or a PIT file for Verizon, so no. Kind of was thinking the same thing.
Anyone have a PIT file for a verizon Tab?
I screwed my tab using Verizon Tab Boostrapper from the market, trying to get to EXT4, it was already rooted with SuperOneClick; it booted into recovery and did a nandroid backup but i think failed the first time then tried to do some flashing then rebooted back into a nandroid backup finally completeing after what i think was a successful backup and EXT format. It may not be successful because when i try either of the md5 in Odin they both fail and i dont think i did enough research to find out how to push these files to the device yet.
After not reading what i should have nor having found a suitable stock verizon rom i tried relfashing with a JMF rom using odin which i am not sure if i jacked it even more but got it to boot to a different samsung startup screen but just hang up there, no carrier logo. Point being i can finally get back to a verizon startup screen after reformatting with P1_add_hidden.pit, it boots to a verizon logo and does the single single vibrate followed by a double vibrate i notice this thing doing everytime it fails with an app or software in general.
After trying this method with heimdall and all files in their right places as instructed by the first post i can flash in download mode but heimdall never tells me that the flash is successful even after waiting a good 10-15 minutes after the progress bars stop. Should it take this long to complete the flash?
Also, i know you said not to use any other files in heimdall but if i try using a CWM zImage file from the forums or even one i found for verizon, i can get heimdall to flash and say successful completed flash but it still vibrates and loops on startup. Any suggestions? Or can someone point me in the direction of how to restore my backup with heimdall?
I can boot into stock recovery and download mode, ive also tried to just flash the CWM from the CWM beta post with heimdall and it says successful flash but it still has stock recovery after reboot.
SUCCESS! ok so my brother has a vzw tab also, i used roto's backup method and backed up his device thru adb, i then heimdall with my bros factory.rfs, kernel(zImage), param.lfs, boot.bin, cache.rfs, dbdata.rfs, modem.bin and recovery(zImage) but got black screen of death so reformatted with P1_add_hidden.pit to get back to looping verizon logo, then back to download mode and this time i removed the kernel and recovery files and tried again which got me back to a verizon logo loop but then i tried a wipe data and wipe cache and WALA! tab booted right up, only missing modem (i think its modem bc i cant get carrier service) and menu/home/search buttons dont respond in android. CWM 3.0 flashes on both tabs but doesnt boot up to it so i used the galaxytabandclockworkmod combo found in these forums to get CWM 2.5.1 on it and am trying to restore from my odin claimed mismatched( but md5summer tells me they are good) nandroid backup, will post findings soon
cooljo555 said:
SUCCESS! ok so my brother has a vzw tab also, i used roto's backup method and backed up his device thru adb, i then heimdall with my bros factory.rfs, kernel(zImage), param.lfs, boot.bin, cache.rfs, dbdata.rfs, modem.bin and recovery(zImage) but got black screen of death so reformatted with P1_add_hidden.pit to get back to looping verizon logo, then back to download mode and this time i removed the kernel and recovery files and tried again which got me back to a verizon logo loop but then i tried a wipe data and wipe cache and WALA! tab booted right up, only missing modem (i think its modem bc i cant get carrier service) and menu/home/search buttons dont respond in android. CWM 3.0 flashes on both tabs but doesnt boot up to it so i used the galaxytabandclockworkmod combo found in these forums to get CWM 2.5.1 on it and am trying to restore from my odin claimed mismatched( but md5summer tells me they are good) nandroid backup, will post findings soon
Click to expand...
Click to collapse
Any chance you could post the files, there are a lot of us stuck at verizon logos without other tabs to copy data from haha.
Thanks in advance!!!
After all the things I tried, I gave in and took it back to Verizon (still within the year Sansung warranty) . I'll have a new one either tomorrow or Monday. Once I get it, I'll preform Roto's backup via command line and get all the required files if they are not posted first. If I read Roto's command strings correctly, I can even get the .pit file so we should be covered.
Like I said, if cooljo555 doesn't post these I'll work on posting them when I get my new device...
MrCheetah said:
Any chance you could post the files, there are a lot of us stuck at verizon logos without other tabs to copy data from haha.
Thanks in advance!!!
Click to expand...
Click to collapse
rjansen110 said:
After all the things I tried, I gave in and took it back to Verizon (still within the year Sansung warranty) . I'll have a new one either tomorrow or Monday. Once I get it, I'll preform Roto's backup via command line and get all the required files if they are not posted first. If I read Roto's command strings correctly, I can even get the .pit file so we should be covered.
Like I said, if cooljo555 doesn't post these I'll work on posting them when I get my new device...
Click to expand...
Click to collapse
Please post these file when you get the chance! I would really appreciate it!
The stock files are posted here
Hello everyone,
All the files are here in the XDA-Developers, in advance I'll like to apologize if I am breaking any rules by adding the link:
http://forum.xda-developers.com/showthread.php?t=955342
I downloaded the files I just don't know how to flash them, including the pit.pit files, help please since my tab is severely broken and I need to flash all files to bring it back to factory.
I'll appreciate anybody helping me. I already tried with heimdall, but it will not do anything when I put the pit.pit file, I tried odin, but it does not work neither, since I don't have a tar file for this, I no matter what I do, if I created one it does not work. If the instructions to do this are included somewhere else, can you please point me in the right direction?
ok well installed the honeycomb rom just to mess around with it see what it looked like. then i went and wiped my tab and restored my backup. now when it starts up all it goes to is the cwm voodoo, nothing ive tried to do has fixed it. i'm sure i'm just dumb but could use the help after hours of looking for a answer with no luck
thanks
How are you trying to revert to stock? I installed the honeycomb alpha 2 release. I was able to go back to a stock rom using Heimdall.
I've tried just flashing my back up I've tried flashing other roms but everytime boots back up to the cwm menu. I haven't been able to try heimdall because I can't get into download mode
I've tried to get into it with no success
PM sent...You are actually experiencing an issue most likely with the GSM bootloaders. The VZW tab has it's own individual bootloaders compared to every other TAB variant. As of now, no VZW bootloaders for ODIN exist online anywhere. The few I found were actually corrupt and not complete for ODIN flashing.
Hey guys,
Alright so, I flashed RocketROM ICS v1 perfertly fine from a GB rom on my Galaxy Note N7000 the other day but I decided I wanted to try out a new modem for the phone. LA4 I think it was.
Flashed that fine and made nandroid backups beforehand just in case. Now I didn't like it all that much, signal was abit choppy etc etc so I decided to restore back to my old backup I made before.
However, during that restore process, my phone just kept restarting itself in the middle of the store, whilst it was restoring the system folder. So I was like ???, and the phone wouldn't start up again, so I kept trying to restore but no luck. The restarts only happened during restores. (and from what I know now, when I'm trying to flash something big (like a new ROM) via CMW)
So I thought, I'll just flash stock LPY ICS rom using Odin and start over again. But during the flashing, it gets stuck at "NAND write start" at about 80% repeatedly. Obviously by now the phone won't start so...
I was just wondering my options here?
(I still have download mode and recovery to use, however I'm all out of ideas )
therannie said:
Hey guys,
Alright so, I flashed RocketROM ICS v1 perfertly fine from a GB rom on my Galaxy Note N7000 the other day but I decided I wanted to try out a new modem for the phone. LA4 I think it was.
Flashed that fine and made nandroid backups beforehand just in case. Now I didn't like it all that much, signal was abit choppy etc etc so I decided to restore back to my old backup I made before.
However, during that restore process, my phone just kept restarting itself in the middle of the store, whilst it was restoring the system folder. So I was like ???, and the phone wouldn't start up again, so I kept trying to restore but no luck. The restarts only happened during restores. (and from what I know now, when I'm trying to flash something big (like a new ROM) via CMW)
So I thought, I'll just flash stock LPY ICS rom using Odin and start over again. But during the flashing, it gets stuck at "NAND write start" at about 80% repeatedly. Obviously by now the phone won't start so...
I was just wondering my options here?
(I still have download mode and recovery to use, however I'm all out of ideas )
Click to expand...
Click to collapse
You may be affected by the Superbrick bug, this may help
How did u flash rocket ics rom successfully from a GB rom? In my case, i am now stuck with a bootloop after flashing. Is there any way to solve the bootloop? I am really noob at this so please help me.
http://forum.xda-developers.com/showpost.php?p=26577489&postcount=5
So I updated the MIUI on my Cappy from whatever I had before to 2.3.30 that is GB 2.3.7 from this location:
http://miuiandroid.com/community/threads/archived-miui-versions-captivate-gb.16558/
I didnt care for it so I downloaded SlimICS. I downloaded the base and the cappy essentials. Put them both on my internal sd. I factory reset, wiped data, cache and system and dalvic, just as i do for every phone i work on. I ran the SlimICS base and now it keeps rebooting and going back into recovery and doing this:
Finding update package...
Opening update package...
Installing update...
Slim ICS
Once Slim ICS pops up, it reboots and does it all over. I can yank the battery and manually go into recovery, but if i try to boot it up normal, it goes back into the loop. I am on CWM 5.0.2.7 also.
So what did i miss?
GB bootloaders most likely missing - flash 'em using Heimdall. And SlimICS doesn't have modem. So. Flash my ROM for a change may be.
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
And you flashed the base and the cappy essentials right? Not just the base
Sent from my SGH-I897 using xda premium
korockinout13 said:
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
Click to expand...
Click to collapse
trying to flash again just put it back in the loop. And I read that that does happen alot going from GB to ICS on the Cappy. But for Slim it didnt work.
Wdustin1 said:
And you flashed the base and the cappy essentials right? Not just the base
Click to expand...
Click to collapse
I never could get that far because it was the base that I started to install and it got bootlooped on, everytime it restarted, it went back into recovery and started to run the base again, and repeated boot loop. I read somewhere that teamhacksung's rom would get me over the GB to ICS bridge. This one here:
http://forum.xda-developers.com/showthread.php?t=1363760
It did the bootloop to, but when i yanked the battery and went back in and installed it a 2nd time, it didnt restart and installed correctly. After that I installed SlimICS. But I dont like it as much as i thought i would and now when i try to reinstall teamhacksung ROM, it errors out during the beggining of the installation. The MD5 is still fine. I dont think it likes the version of CWM recovery that SlimICS installed. I know CWMR went to an older version when i went from teamhacksung to SlimICS.
Flash glitch kernel first. Also, don't use the builds from that thread, it is old. Just flash the latest CM9 nightly
Swyped from my ICS Samsung Captivate
Stuck in A boot loop after flashing paranoid rom to cappy i897
I downloaded all needed files to internal SD just as the (how to upgrade the captivate i897 to Paranoid ROM said to do )
wipe data factory reset,wipe cache,selected install zip zip>package (pa_captivatemtd-1.99-13AUGUST2012.zip, md5sum: cc03bacf0f07a94bf25b482d64b94e63) then it started boot looping / att screen twice then android guy ,, then falling over with exclamation point in the middle of him , let it go considering options of 3 button combo weren't working ,, beside guide said 5-10 min to install then it made it to devil kernel installed gapps >> (gapps-jb-20120726-signed.zip, md5sum: f62cfe4a827202899919fd932d5246d7) now back in the boot loop again>>
i did make a nandroid backup but cant seem to get into cwm recovery or download mode . I did follow that guide to a tee.
any help or suggestions on this i would greatly appreciated if this post in wrong spot sry im new.
Also stuck in bootloop reverting to Gingerbread
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Reply Back.
HG_User said:
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Click to expand...
Click to collapse
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out. ??
---------- Post added at 06:38 PM ---------- Previous post was at 06:27 PM ----------
321321wrick said:
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out.
There also Ginger Bread Boot loaders Needed for it to start up Correctly - i personally don't know that much bout gingerbread rom i didn't like it as much as froyo WiFi issues'' the the stock odin should erase all info on your part thou 'e use Is OCD 1 i897UCJF6>lowercase work every time for me.
cept now because my usb is not able to charge phone or enter download mode or recovery which leaves jig option .
Click to expand...
Click to collapse
HG_User,
U can't go back to GB (or froyo/eclair) from CM, MIUI, ICS, JB, AOSP etc., etc. without using Odin or Heimdall---because of the different partitions used---Stock firmware is bml/rfs and all the AOSP etc etc are mtd/yaffs(2).
And u can only restore a backup when u r back running the base rom where u made the back up.
Use this...Stock i897ucKK4 GB 2.3.5 with or without bootloaders... http://forum.xda-developers.com/showthread.php?p=18370912
This kk4 should get u going. Then u can use Odin to flash Corn Kernel to get a cwm back...:thumbup:
Sent from my SGH-I897 using xda premium
... one step on the way: Back to Eclair
thanks for the advice. Ultimately, I decided I should use Odin 3 1-click to revert back to original (2.1 Eclair) firmware that I found on the first post of thread titled
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY
This is a huge step forward because it makes my phone work, but it's also a step back in time to the early Eclair days.
Now my next step is to upgrade back to Gingerbread...
Edit: Thanks to all who pointed me in the right direction. I took the phone back to Eclair then used Samsung KiesMini (twice) to get it back to Gingerbread. After re-rooting and removing the AT&T Bloatware, it works fine again. I might try upgrading again to ICS or JB, but I didn't like Cyanogen 9 at all. Maybe I'm just used to the way AT&T polishes the UI, but Cyanogen didn't appeal at all. Now looking for a relatively polished but lightweight ICS or JB version... Also, it would be nice if when I upgrade it preserves the installed apps and what's on my home screens, but that seems unlikely going from AT&T-branded Gingerbread to an independent ICS or JB.
Apologies if this is answered elsewhere but I've been looking around the forums and a lot of information/posts from people seem to conflict or the information is only valid for X kernel or Y kernel etc and it can still be a little overwhelming even after lots of nice people have posted guides.
I bought a German Note about a month ago and upgraded to 4.0.3 through the devices own update method (I have not flashed any ROMs on this device), leaving me on XX-LPY. I have since rooted the device, and did not perform any kinds of wipes doing this, this was the only time I even used CWM, I havent booted into CWM since (or used any of the normal recovery features).
The device has been working fine for around a week, I've restarted it several times without issue. However today after restarting it gets stuck on the Samsung logo and will not boot properly. The only thing I have used root for is to uninstall Kies and the SNS Push stuff (which seemed to save me a lot of battery life) and install ad-free android. I also installed the Carbon Tweaks app and applied the Carbon Booster stuff along with the Beats Audio and Bravia Engine stuff (nothing else).
I am able to get into recovery mode however I seem to be unable to put it into download mode (Edit: finally got it to do it once, wont do it every time though) so I have a few questions:
Can anyone tell me if its ruined or why its doing this?
Is it safe to just factory reset/wipe cache through normal android recovery (not CWM?).
Is it safe to try to flash another ROM through CWM (I'm on XX-LPY) and if so which one is safe for me to flash?
Is it safe to try to flash through Odin and if so which ROM should I flash?
I really dont care about the data on it or wiping it w/e. I just dont want to turn it into a paperweight if I can help it.
Thanks
Edit: Also if it makes any difference, this is the method I used to root the device:
http://forum.xda-developers.com/showpost.php?p=20963730&postcount=3
Nope, don't go around flashing stuff with CWM on that device.Also, you can't wipe as that may trigger the MMC_CAP_ERASE causing superbrick.Judging by what you say you've done, I'd say I don't know why it happened but it isn't ruined.
You can try to flash a stock GB rom of your country by following dr.ketan's guide in the dev section and then rooting it (if you want).Alternatively,you could just take it to a Samsung service center as there is no yellow triangle.But I'd try to flash the GB rom as flashing a stock kernel via PC Odin doesn't increase the flash counter.