Bricked samsung galaxy 7.7 lte verizon i815 please help!!!! - Galaxy Tab 7.7 General

HELP PLEASE!!!! I have the Samsung galaxy tab 7.7 verizon LTE sch - i815 version and im losing hope quickly. Im not sure which way to take to get a working tablet again. Im kind of a noob but have rooted and flashed many devices. Sorry if my thoughts are rambling or all over, but its been a long three days trying to get this to function and im not there yet so id appreciate any help I can get!
Here is what my sch i815 can do:
1) Get into recovery
2) Get into download mode
3) Restore backups that end up getting bootlooped with splash page
4) Install roms that end up in blootloop with the splash page.
5) Flash recoveries with odin
6) Charge tablet battery
One issue is when im trying to wipe before I install cm9 for the i815. When im in recovery and ive tried the p6800 and the i815 with same results, when I try to WIPE data / factory reset the tablet gets to “FORMATTING / DATA” AND THE TABLET REBOOTS TO THE SPASH SCREEN AND GETS STUCK THERE.
My problem is I tried to put the p6800 ics on my tablet and didn’t realize it wasn’t compatible with the sch i815. At first some of the p6800 roms would at least get past the Samsung galaxy tab 7.7 screen, but now its basically stuck there. The only rom or anything that boots past that is the cm9 for the i815. But that just boot loops from Samsung flash screen to start of cm9 and then back to flash screen. I had a backup that worked fine but now it installs the backup and get stuck at the flash screen only. I don’t know if I should try to get cm9 to load past the splash screen boot cycle or find a file to flash with odin which I see there really isn’t any for this model. I did find some posts about a cwm backup file 2012-05-06.22.48.58 and I cant get that to restore either.
When I try to do the zip that is floating around for cwm backup, I try to apply the backup 2012-05-06.22.48.58 and it says checking md5 sums… for a few minutes, then it says md5 mismatch!
I guess any help would be greatly appreciated. I see that I could try to get back to 3e recovery but I cant get anything on the internal sd card because I cant get anything to boot. Thanks for everyones time!!

Have nothing else in the subdirectory that has the recovery. Only the recovery. Nothing else.

me too
Same issue almost exactly with mine.
Got ICS installed OK and it was working fine then started to spontaneously reboot
I cannot restore nandroid backups that worked yesterday
Also interesting that when I try to format data in cwm it reboots
Now I can get an install of cm9 to complete but I'm left with a boot loop
This is an i815
I'm thinking partition table got jacked up
Any ideas out there ?
Thanks
schillaj said:
HELP PLEASE!!!! I have the Samsung galaxy tab 7.7 verizon LTE sch - i815 version and im losing hope quickly. Im not sure which way to take to get a working tablet again. Im kind of a noob but have rooted and flashed many devices. Sorry if my thoughts are rambling or all over, but its been a long three days trying to get this to function and im not there yet so id appreciate any help I can get!
Here is what my sch i815 can do:
1) Get into recovery
2) Get into download mode
3) Restore backups that end up getting bootlooped with splash page
4) Install roms that end up in blootloop with the splash page.
5) Flash recoveries with odin
6) Charge tablet battery
One issue is when im trying to wipe before I install cm9 for the i815. When im in recovery and ive tried the p6800 and the i815 with same results, when I try to WIPE data / factory reset the tablet gets to “FORMATTING / DATA” AND THE TABLET REBOOTS TO THE SPASH SCREEN AND GETS STUCK THERE.
My problem is I tried to put the p6800 ics on my tablet and didn’t realize it wasn’t compatible with the sch i815. At first some of the p6800 roms would at least get past the Samsung galaxy tab 7.7 screen, but now its basically stuck there. The only rom or anything that boots past that is the cm9 for the i815. But that just boot loops from Samsung flash screen to start of cm9 and then back to flash screen. I had a backup that worked fine but now it installs the backup and get stuck at the flash screen only. I don’t know if I should try to get cm9 to load past the splash screen boot cycle or find a file to flash with odin which I see there really isn’t any for this model. I did find some posts about a cwm backup file 2012-05-06.22.48.58 and I cant get that to restore either.
When I try to do the zip that is floating around for cwm backup, I try to apply the backup 2012-05-06.22.48.58 and it says checking md5 sums… for a few minutes, then it says md5 mismatch!
I guess any help would be greatly appreciated. I see that I could try to get back to 3e recovery but I cant get anything on the internal sd card because I cant get anything to boot. Thanks for everyones time!!
Click to expand...
Click to collapse

fixed
OK Fixed!
how to:
Download android sdk to get adb.
Once you get adb ( adb is an executable program ).
Put tab in recovery mode ( I'm using CWM recovery ). If in CWM goto mounts and storage but dont mount anything.
then ( with tab connected via usb to computer with adb ) run this command:
adb shell e2fsck -yfDC0 /dev/block/mmcblk0p10
For me this fixed some jacked up inodes
Once this was complete I was able to do a full wipe without reboot, reinstall ics and it came back up all good
Hope this helps
tr2ride said:
Same issue almost exactly with mine.
Got ICS installed OK and it was working fine then started to spontaneously reboot
I cannot restore nandroid backups that worked yesterday
Also interesting that when I try to format data in cwm it reboots
Now I can get an install of cm9 to complete but I'm left with a boot loop
This is an i815
I'm thinking partition table got jacked up
Any ideas out there ?
Thanks
Click to expand...
Click to collapse

tr2ride said:
OK Fixed!
how to:
Download android sdk to get adb.
Once you get adb ( adb is an executable program ).
Put tab in recovery mode ( I'm using CWM recovery ). If in CWM goto mounts and storage but dont mount anything.
then ( with tab connected via usb to computer with adb ) run this command:
adb shell e2fsck -yfDC0 /dev/block/mmcblk0p10
For me this fixed some jacked up inodes
Once this was complete I was able to do a full wipe without reboot, reinstall ics and it came back up all good
Hope this helps
Click to expand...
Click to collapse
OK. Great to hear. I'll try tonight after work. Which ics are I running by the way? Cm9 or the i815?

I'm running the cm9 for i815 from this thread:
http://forum.xda-developers.com/showthread.php?t=1542911
works great except for the lack of GPS and LTE, I can live without LTE by tethering but GPS is a show stopper for me so I'm likely going to revert to Honeycomb

tr2ride said:
I'm running the cm9 for i815 from this thread:
http://forum.xda-developers.com/showthread.php?t=1542911
works great except for the lack of GPS and LTE, I can live without LTE by tethering but GPS is a show stopper for me so I'm likely going to revert to Honeycomb
Click to expand...
Click to collapse
ok, yeah does hdmi work on cm9? if not i will want honeycomb also. Do you havea rom for that? or how would i revert back to that? Thanks for all your time and help!~

i keep getting bootloop from cm9 and i dont know why.....

i got it to work with your command, but i installed cm9 for the i815 and i get a bootloop and now im back to where i was again with the rebooting in cwm and cant restore my backups...

Related

[Q] Stuck on recovery screen after flashing

Hi all,
I recently decided to upgrade my 1 year old Samsung GT-P1000 tablet from its stock Froyo to a newer Gingerbread-based ROM. The tablet is not SIM-locked.
I tried using Heimdall to flash Technomancer's CM7 beta but I ended un in the CWM 5.0.27 recovery screen every time. I tried rebooting a couple of times, repartitioning and not, formatting EVERYTHING (/system, /data, both SD cards, etc) and I always end up in the recovery screen.
I also tried installing MIUI from the available CWM and again I ended up in the recovery screen. The only visible effect was that it downgraded my CWM version to 4.x (which I can upgrade with Heimdall flashing CM7 again).
While in the recovery screen I can connect from my computer using ADB and get a root shell (at least whoami replies with root).
I'm probably missing something really basic but I've been looking at many other posts and haven't been able to figure out what. Is there any extra step that I need to take in order to get a bootable system?
Thank you!
Wipe data in recovery
Sent from my SCH-I800 using XDA App
Already did that :-( I tried wiping data, cache, and still it goes back to recovery after rebooting.
Try flashing again with a different rom and telk me what happens
Sent from my SCH-I800 using XDA App
Press two times on the home button if you are in recovery
Sent from my GT-P1000 using XDA App
Frank2623: I tried doing that and the home button only moves the cursor. I tried other buttons as well but to the same effect, they only act as cursors and OK/back, no other effect observed.
YoshiFan501: After flashing CM7 for GT-P1000 I did try with MIUI 1.11.4 (Final Update), only I didn't know how to flash it from Heimdall and I just ran the update from recovery. I am also trying to locate other ROMs for Galaxy Tab. Any suggestion?
I did the exact same thing this guy did and have the same problem. Stuck in a recovery boot loop.
Did the same things, wiped everything, flashed different roms, miui etc, can't get out.
Can anyone provide a solution to this or tell me how to flash back to my old T-Mobile stock rom? I didn't brick my device did I?
Solution
Ok so I managed to get at least a stock 2.3 ROM, which is better than 2.2 and much better than not booting!
Here's what I did, in case someone else like Lucifus comes here with the same problem:
* Google for a stock GT-P1000 ROM like 001001-GB-Stock-Safe-v5.zip. Unzip it in a directory and untar the bundled GB_Stock_Safe_v5.tar as well.
* Install Heimdall v1.1, NOT v1.3 and open Heimdall Frontend (on 1.3 it wouldn't let me perform the following steps, maybe you get luckier)
* Turn on the tablet in download mode (with VolDown + Power)
* In Heimdall, select the PIT file from the 001001-GB-Stock-Safe-v5 and also the rest of components: primary boot (boot.bin), secondary (sbl.bin), factory FS, ...
* Choose a modem file (the Start button will remain disabled until you do). A quick google showed JPZ being the correct one for Android 2.3 and I for me it actually works.
* Recovery can be left blank
* Flash the whole thing
* It will reboot in recovery and output text on screen, including some errors
* Select factory reset, otherwise when you reboot again it will be stuck in the blinking Samsung logo (but you can power off, reboot in recovery and select factory reset then).
* Finally the Android OS boots
Not Detecting in ODIN/ How to use Heimdall
Hello xda users,
I need HELP !
I have a galaxy tab P1000
currently froyo 2.2
wanted to upgrade to GB
Tried the Odin way from another link on this site (MANUAL updation for galaxy tab(p1000) into 2.3.3 gingerbread ), it failed and the Tab got soft bricked,
somehow managed to unbrick it, now its back to its original fw, but it keeps restarting in a loop until i swith the damn thing off completely
I have tried to go in download mode. odin doesnt reognise it , tried differnt computers too, no use.
I have gone in recovery mode, hard reset, wipe cache , still when i switch it on, it goes in a reboot loop.
tried to use heimdall. cant get sucess as i might not understand how to use it properly
Please help.
Sincere thanks to you if you can help me get my tab up and running., if not in GB atleast back in froyo.
(PS i im not worried about my data , and i have not backed up the rom etc before doing any of these)
blizzard_boy said:
Hello xda users,
I need HELP !
I have a galaxy tab P1000
currently froyo 2.2
wanted to upgrade to GB
Tried the Odin way from another link on this site (MANUAL updation for galaxy tab(p1000) into 2.3.3 gingerbread ), it failed and the Tab got soft bricked,
somehow managed to unbrick it, now its back to its original fw, but it keeps restarting in a loop until i swith the damn thing off completely
I have tried to go in download mode. odin doesnt reognise it , tried differnt computers too, no use.
I have gone in recovery mode, hard reset, wipe cache , still when i switch it on, it goes in a reboot loop.
tried to use heimdall. cant get sucess as i might not understand how to use it properly
Please help.
Sincere thanks to you if you can help me get my tab up and running., if not in GB atleast back in froyo.
(PS i im not worried about my data , and i have not backed up the rom etc before doing any of these)
Click to expand...
Click to collapse
Hmmm... did you READ the post just above yours ?
yes
i read , nothing helped
anyway i managed to get it detected in odin and flashed it through a proper walkthru process from another site.
now my tab works with GB
Libon

Stuck in the CW recovery screen, tried everything.

I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Had you flashed CmWR into eMMC?
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
@Dizzyden, thanks for the tip.
I did repartition to 1g/5g awhile back. I am not sure where to start. 12paq tried many things, which one was the solution? Your rombackup.zip?
Many thanks....
@votinh
what do you mean? I am not using the N&O apps or OS. Pure CM9, therefore I guess it is flashed in eMMC. If not, please advice.
DizzyDen said:
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
Click to expand...
Click to collapse
how can I check this"Check the ROM information on /dev/block/mmcblk0p2"?
please advice.
I tried to adb shell the nook, but not devices found? please help.
Finally, with the help from the good people of this forum, I was able to restore back to B&N, and reflash CM9 from there.
Thank to you all.
Yesterday my nook color was working great. Today I turned the screen on and it hung. Now I'm having the above problem with it hanging at clockwork recovery.
I've got CM7.1 stable on there running from emmc.
can't get adb to recognize the device since it is in cwr... how did you do it?
chilimac02 said:
can't get adb to recognize the device since it is in cwr... how did you do it?
Click to expand...
Click to collapse
Install the google drivers for adb... if you are in CWR adb is enabled... just have to get the drivers loaded on your computer.
try this:
http://forum.xda-developers.com/showthread.php?t=958748
dumper1234 said:
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Click to expand...
Click to collapse
It may be that your "boot to recovery" flag is set, and if so, it will always boot to that until it is cleared. When the cyanogenmod logo comes up hold the n button until the boot menu comes up. Then choose boot to emmc. If it works, go to ROM Manager and flash a new CWM Recovery to emmc.
Welcome to the nightmare I lived last week. Don't worry I woke up, was able to fully recover and forget the dream ever occurred.
I to tried to reformat to 1gb/5gb and ended up in the same boot loop.. If you are in the same spot I was, your boot partition got wiped out. And you may notice EMMC is gone.
After much searching I came across a file... Looking....Looking...Looking...
..........................Ah yes here it is. Here is what worked for me.
1. Boot to recovery (Should be easy at this point)
2. Format System, Data, and Cache.
3. Install the attached Zip file. (RecoveryFix.zip), this should recreate the Boot partition and fix the EMMC.
4. Reboot to recovery
5. Install favorite Rom or restore from backup.
6. Reboot to test.
Again this is what finally worked for me, and I went through a lot of trial and error to get there. I am guessing at your situation being exactly the same as mine.
PS. Ignore my since of humor if you need to.

Cant get Vibrant to start help plz!

Ok i was on ICS passion then all of a sudden my phone said something about encryption an that it had failed an only option was to reset phone so i hit reset then it went to recovery mode an green android came up with chest open then error message happened an so i booted in to recovery then i try to go in sd an it would not allow me to so i then tried to odin an flashed then i powered on it gies to vibrant screen then it just shuts off so i then flashed Eugene froyo that does not brick then it takes me to stock recovery an says an i cant click on anything in recovery can only move -- movi_checking done!...
update media, please wait
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet, please use UI me
nu for format and reboot actions.
Here are instructions i have followed an no luck http://forum.xda-developers.com/showthread.php?t=1043892
Ok I think you got some extra cache or some other piece of data that did not get wiped. either way, do this in this sequence and you should be ok
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Load the JFD rom for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine!
15. Then, root the phone and you can flash your new Rom.
doing this method will get everything back to normal and the phone will work just like it did right out of the box
It is #7 that is important when it reboots into recovery after froyo that does not brick then pull the battery and go back into download mode and flash the JFD, This will clear everything out and put you back into stock
Good luck
Got it started
I got it booted though a very hard process an now i cant get my sd card to mount it says when i go into anything media related it says "Your phone does not have a SD card inserted" an Externel dont mount either
Which sd card isnt working... internal sd, or external sd?
kf7strng said:
Which sd card isnt working... internal sd, or external sd?
Click to expand...
Click to collapse
Both of them aren't working
Jasonhunterx said:
Both of them aren't working
Click to expand...
Click to collapse
Don't use eugene's rom, since you were using an ICS rom follow these steps
flash froyo bootloaders
flash regular jfd and TICK REPARTITION ( ICS/CM7/CM9 change the partition layout and you need to flash correct partition table for stock rom to work )
back in bussiness.
http://forum.xda-developers.com/showthread.php?t=848737
jrafael said:
Don't use eugene's rom, since you were using an ICS rom follow these steps
flash froyo bootloaders
flash regular jfd and TICK REPARTITION ( ICS/CM7/CM9 change the partition layout and you need to flash correct partition table for stock rom to work )
back in bussiness.
http://forum.xda-developers.com/showthread.php?t=848737
Click to expand...
Click to collapse
it never booted on Eugene rom it just went to recovery an gave me an error the one time i got it booted was on 2.1 Stock all the phone does is go to vibrant screen then shut down an no boot loop just off it has done this before an i fixed but Sd was not working an first time apps worked but then 2nd time no apps worked besides browser messenger
Jasonhunterx said:
it never booted on Eugene rom it just went to recovery an gave me an error the one time i got it booted was on 2.1 Stock all the phone does is go to vibrant screen then shut down an no boot loop just off it has done this before an i fixed but Sd was not working an first time apps worked but then 2nd time no apps worked besides browser messenger
Click to expand...
Click to collapse
Hey Jason. I'm in the exact situation you're in. Loaded Passion for about 1 week, got the encryption screen and was forced to reset. Now my SD cards (internal and external) won't load. Have you found a work around for it yet? Cheers Mate.
nope nothing
either of you find a solution? Im having same issue
In the same boat
I am in the same boat. I was using the Euphoria ROM. Yesterday things slowed down on the phone. I rebooted a few times and it crashed. The last couple of times it told me about the encrypted data. That was when I tried to take it back to stock and it won't do anything now other than boot to the vibrant logo and shutdown. Searching for a way to odin a ROM/Kernel that has a CWM recovery so I can go in and manually format the SDcard.
Do what I did, sell it to someone as a wifi hotspot and buy yourself a hercules. You'll never look back
Sent from my SAMSUNG-SGH-T989 using XDA
BUMP
BUMP!
I have had a paper weight for three weeks now because of this partition issue.
there has to be a way to fix this.
webstas said:
BUMP!
I have had a paper weight for three weeks now because of this partition issue.
there has to be a way to fix this.
Click to expand...
Click to collapse
Try this one.
http://forum.xda-developers.com/showthread.php?t=1580902
Sent from my Vibrant using Tapatalk 2
Webstas- Just out of curiousity, were you trying to mount your phone to your computer while on ICs when this happened? I have a theory that I believe I know why this is happening. Just need you to see if you remember a few weeks ago and if you had any problems mounting to your PC and then your next reboot you got the Ecnryption Error.
Woodrube said:
Webstas- Just out of curiousity, were you trying to mount your phone to your computer while on ICs when this happened? I have a theory that I believe I know why this is happening. Just need you to see if you remember a few weeks ago and if you had any problems mounting to your PC and then your next reboot you got the Ecnryption Error.
Click to expand...
Click to collapse
no i got up an took a shower then came back it gave me an encryption error then i odin back an more trouble odined a couple more times an now it boot loop an also wont start with eugenes froyo
I know it has been awhile but think back. Were you mounted to your PC at anytime between your last reboot and the Encryption Error? Doesn't have to be right before, the error gets throw on your "next" reboot. And as you know, reboots can happen manually or for something as simple as wrong UV settings.
Looking back in this thread, I saw that you got it to boot up. See if you can do that again and then mount your External via ADB and you should to push the proper commands then. Pretty much your internal is hosed, but me and a few others are working on that too.
Can't get it to boot it makes it to Vibrant screen an shut off an on Eugene"s froyo it gives me a couple of errors an I just can't get it to start anymore it there anyone who has encountered this an got it fixed like I really need this fix I am using a blackberry please save me
YAY
I got it fixed but now im on step 13 of that guide where you have to use ADB an i cant get the phone to show up on my PC what drivers do i need i already have Vibrant drivers but still nothing an the usb works its a samsung USB so can anyone help me with ADB
I am having a similar problem. Was running ICS 4.0.3 w/Euphoria without issue until this morning. Got a couple of errors after a normal recharge. Pulled battery and rebooted, but is stuck in boot loop. Cannot access either recovery or fastboot screen. Vibrant logo flashes and release buttons, but never enters mode. Then cycles to Android screen and would likely stay there until battery died. This is primary phone and need to put back into service quickly. Any assistance will be greatly appreciated. Thanks.
JIM in FLA
Go back to stock 2.1
Sent from my SGH-T959 using XDA

Galaxy Tab 2 10.1 Recovery Post Mortem

A story you might find some useful morsels in . If you are impatient, yes, a happy ending.
Monday night I opened the case on my tablet and it was booting. I figured that was strange and after a few minutes realized it was just stuck booting. So I rebooted it. Came up... and then suddenly during the everything loading up phase, rebooted. This repeated several more times.
Uh oh. Working quickly between boots I unset the default on Apex launcher (since it updates frequently) and turned off the live wallpaper. I also shut off Wifi. No effect.
Next stop recovery. Cleared caches, etc. Nope. I had a fairly recent backup but took another one and it worked (whew). Decided that I would do a data wipe from recovery. Uh oh. Any attempt to format /data causes a crash.
I go to Odin to see if I can repartition flash. I can't find a PIT file for the P5113 but did find one for a 16K 7 inch model. Odin repartitioned it but still no joy. Wiping data causes a reboot. So does trying to restore a backup to /data.
Next stop Kies. You can tell it to reload firmware but you need your serial number which is written on the back of your tab (yes it is, it is about the height of a carbon atom). However, it asks you to enter "recovery" mode by pressing buttons that aren't on the tablet. I tried Odin mode but it couldn't connect. Using CWM recovery didn't work either.
So I decided I needed stock recovery. I could not find a P5113 stock recovery that wasn't bundled with an entire update package. So I unpacked an update package to get recovery.img. Flash_image didn't work (seems like it never works on this tablet, and now that I think about it, I think I wrote a thread on how to do it with dd that I forgot about last night! Duh: http://forum.xda-developers.com/showpost.php?p=31293383&postcount=32). Instead, I repacked just recovery.img with tar. Odin was able to flash this and I was back in the ugly stock recovery.
I never did try Kies though because I asked the stock recovery to reformat /data and it worked! Back to Odin to reflash CWM and then the backup I made Monday night rolled back on and I was back in business.
Restore my screen saver, redefault (is that a word?) Apex, and turn Wifi back on. Oh yeah, and run Triangle Away
So I'm not sure what to make of all this. Open questions:
1) Did I need to repartition? What's the right PIT file to use? I sure wish Odin could dump a clean image, but if it can, I don't know how.
2) What mode does Kies want? This could have been a VirtualBox problem but I got it to work before I got Kies installed on my wife's real Windows box (man Kies is slow!).
3) Why could stock recovery reformat /data but CWM could not?
4) Would it have been sufficient to just reflash the stock recovery, do the data wipe? I suspect so, but don't know.
Anyway.... things are back to normal. Love the tab, but sure wish these big companies wouldn't assume we don't know how to fix our own stuff and muck things up with "simplified" tools. By the way, this is the "touch" CWM that seemed to fail to fix /data. I did not try the normal one.
wd5gnr said:
A story you might find some useful morsels in . If you are impatient, yes, a happy ending.
Monday night I opened the case on my tablet and it was booting. I figured that was strange and after a few minutes realized it was just stuck booting. So I rebooted it. Came up... and then suddenly during the everything loading up phase, rebooted. This repeated several more times.
Click to expand...
Click to collapse
Here we go again. Same problem but I'm not even getting into the boot. Does anyone know how to actually reformat and rescan flash for bad blocks? I have a feeling I have a bad flash block that is doing something evil.
Sigh.
Tried a different approach this time.
Booted to recovery and did an fsck on /data since it seemed to have the problem.
It did a lot of clean up and now I'm back up. Not sure what got damaged if anything though. Time will tell.
Good to hear that it is a happy ending, bro!
Sent from my AT1S0 using xda app-developers app

[Q] Semi bricked i9505 - fresh ideas required , i'm out

This may humor some of you as to the stupidity I have displayed in messing around with rooting\rom'ing my i9505.
Sadly tho it's resulted in me bricking/semi-bricking the phone and I am tearing my hair out trying to fix it.
What I did to get me here:
- Within TWRP (existing recovery/root at the time) I wiped all my data from the internal storage. This in effect meant that I had no roms nor any backups to recover from. Super Doh! *facepalm* moment of the centuary... :S
- For one reason or another the existing rom i was on would not boot. I was effectively stuck in a boot loop on the Samsung Logo
What I have tried doing to fix it (and failed miserably):
- I thought that by at least getting a rom onto the device and flashing it I would be back in business however this proved to be a challenge as the samsung USB drivers do not work with TWRP so I cannot adb push or sideload as I have no rom/backup locally.
- So I rooted with CWM which worked a treat with sideload. So I rom'd the phone...however...the following now happens
- I cannot get into existing/current ROM. Boot loop
- I cannot get into CWM (frozen with blue text in the top left) and have re-downloaded ODIN, CWM several times and tried to flash several times. No joy...
- I can flash with TWRP however as mentioned above the drivers do not work so I cannot sideload.
Any ideas how to fix - very very very much appreciated.
Don't need comments how dumb I have been - I am kicking myself more than you ever will.
r34l1ty7 said:
This may humor some of you as to the stupidity I have displayed in messing around with rooting\rom'ing my i9505.
Sadly tho it's resulted in me bricking/semi-bricking the phone and I am tearing my hair out trying to fix it.
What I did to get me here:
- Within TWRP (existing recovery/root at the time) I wiped all my data from the internal storage. This in effect meant that I had no roms nor any backups to recover from. Super Doh! *facepalm* moment of the centuary... :S
- For one reason or another the existing rom i was on would not boot. I was effectively stuck in a boot loop on the Samsung Logo
What I have tried doing to fix it (and failed miserably):
- I thought that by at least getting a rom onto the device and flashing it I would be back in business however this proved to be a challenge as the samsung USB drivers do not work with TWRP so I cannot adb push or sideload as I have no rom/backup locally.
- So I rooted with CWM which worked a treat with sideload. So I rom'd the phone...however...the following now happens
- I cannot get into existing/current ROM. Boot loop
- I cannot get into CWM (frozen with blue text in the top left) and have re-downloaded ODIN, CWM several times and tried to flash several times. No joy...
- I can flash with TWRP however as mentioned above the drivers do not work so I cannot sideload.
Any ideas how to fix - very very very much appreciated.
Don't need comments how dumb I have been - I am kicking myself more than you ever will.
Click to expand...
Click to collapse
Can u try flashing Stock firmware using Odin it should work and incase after flashing it does not boot go to stock recovery and wipe cache reboot
123hiten said:
Can u try flashing Stock firmware using Odin it should work and incase after flashing it does not boot go to stock recovery and wipe cache reboot
Click to expand...
Click to collapse
Just wanted to say a big thanks. Your solution worked a treat. :good:
I take it I can now root as usual? Nothing else needed? ...apart from not trying to be stupid again

Categories

Resources