Hi,
My SGT 7.7 seems brick after I took it out of my bag. It gets stuck and stays on the boot screen where says "Samsung Galaxy Tab 7.7" for a few seconds, and then just keep rebooting.
It is able to go into the Download Mode when I press "Power+Vol-", but no response when I press "Power+Vol+". I tried to flash all kinds of firmware with Odin, but nothing work.
I also tried to flash it with .pit, PDA, PHONE and CSC. I got this screen and then stopped and Odin says "Now Writing, Please wait about 2 minutes."
I appreciate your help!
same problem here, but caused from rom-manager! did nothing more than using the "reboot into recovery" option, i did NOT flash anything with rom-manager before!
download mode works, recovery works, but i can flash what i want, after turning the device on the "samsung 7.7" stays for about 30sec, then it reboots ad infinitum!
any ideas?
i'm within the one week were i can exchange the device without any problems, but i want to fix it myself if possible!
thx in advance!
TML1504 said:
same problem here, but caused from rom-manager! did nothing more than using the "reboot into recovery" option, i did NOT flash anything with rom-manager before!
download mode works, recovery works, but i can flash what i want, after turning the device on the "samsung 7.7" stays for about 30sec, then it reboots ad infinitum!
any ideas?
i'm within the one week were i can exchange the device without any problems, but i want to fix it myself if possible!
thx in advance!
Click to expand...
Click to collapse
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
(CWM could not fix this filesystem problem.)
(areyou sure rom manager is compatible with the different partitions on the 7.7)
Remember you will loose all user data !!!!!
davp said:
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
(CWM could not fix this filesystem problem.)
(areyou sure rom manager is compatible with the different partitions on the 7.7)
Remember you will loose all user data !!!!!
Click to expand...
Click to collapse
again thx,
but the problem is seems to be "deeper" than only a corrupt /data!
The tab doesnt boot further then "samsung 7.7", if data is corrupt then
at least android will load (bootanimation) and go into a bootloop in some stage!
Also, I didn't change or install or flash anything in rom-manager, I "only" used the reboot function!
After reflashing the device with repartition and HongKong.pit I think I messed up the partitions totally, so I would really need the PIT for 6810 (6800 has different partition layout) to repair this!
But as it seems no one has this PIT or is willing to provide it,
so I ordered an new tab which will arrive in the next hours, and return this one within the next days!
Where did you find the PIT file ? You may just destoried the partition. God bless you!
matth3w said:
Hi,
My SGT 7.7 seems brick after I took it out of my bag. It gets stuck and stays on the boot screen where says "Samsung Galaxy Tab 7.7" for a few seconds, and then just keep rebooting.
It is able to go into the Download Mode when I press "Power+Vol-", but no response when I press "Power+Vol+". I tried to flash all kinds of firmware with Odin, but nothing work.
Click to expand...
Click to collapse
I have a familiar problem....
I have not flashed or rooted my device - it is exactly how it came out of the box...
One morning while using it it froze - I did are reset by holding the power button down and then let it reboot but when it did it can not get past the "Samsung Galaxy Tab 7.7" screen.
Can get it into download mode, but if I go to recovery mode then all I get it a headline saying "Manual Mode" which grabs some manual .apk files and then just goes back into the boot mode with the "Samsung Galaxy Tab 7.7" screen.
Any ideas?
Had a Galaxy Tab Original and got the Galaxy SII and have mod them to death - just though for this one I would leave it original and enjoy the OTA updates as the were delievered - especially considering ICS in a matter of days
If you can boot into download mode you can call this a soft brick..
dont use ROM manager and install clockworkmod from that, incompatibility of cwm recovery will brick your phone..
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..
suwandiapr said:
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..
Click to expand...
Click to collapse
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....
Aspi914 said:
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....
Click to expand...
Click to collapse
yes, that is what he means.
Also, if you still have trouble after the first flash, you may need to go into samsung 3e recovery and do a data wipe/factory reset. Then flash again. Since these are non-wipe firmwares, simple flashing may not clear a corrupt filesystem.
Obviously you will lose all user data!
suwandiapr said:
If you can boot into download mode you can call this a soft brick..
dont use ROM manager and install clockworkmod from that, incompatibility of cwm recovery will brick your phone..
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..
Click to expand...
Click to collapse
thx, but as i said i DID NOT FLASH OR INSTALL ANYTHING with rom-manager, i only used the option "reboot into recovery"!
and i used odin to try to unbrick my device (i flashed a dozen roms as well as the sbl etc.), without any success. also, till now nobody has provided a 16GB PIT for 6810, therefore i returned the tab and grabbed a new one!
davp said:
Also, if you still have trouble after the first flash, you may need to go into samsung 3e recovery and do a data wipe/factory reset. Then flash again. Since these are non-wipe firmwares, simple flashing may not clear a corrupt filesystem!
Click to expand...
Click to collapse
Thank you Davp...
Ok...got the P6800ZSLA2 stock ROM and have managed to get it back...while I don't want to have to re-do all the data, I think I will take your advise and do a data wipe/reset.
Aspi914 said:
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....
Click to expand...
Click to collapse
Yes you right, thats what i mean..
TML1504 said:
thx, but as i said i DID NOT FLASH OR INSTALL ANYTHING with rom-manager, i only used the option "reboot into recovery"!
and i used odin to try to unbrick my device (i flashed a dozen roms as well as the sbl etc.), without any success. also, till now nobody has provided a 16GB PIT for 6810, therefore i returned the tab and grabbed a new one!
Click to expand...
Click to collapse
Im sorry , my answer cannot solve your problem.. You say your device "stuck on Samsung logo" right? your recovery and download mode seem ok, from my experience its because /data corrupt or something crash on your filesystem..
If you can go to recovery menu, do factory reset,..
I cannot help you with pit.file coz i actually dont have the device right now..
Aspi914 said:
Thank you Davp...
Ok...got the P6800ZSLA2 stock ROM and have managed to get it back...while I don't want to have to re-do all the data, I think I will take your advise and do a data wipe/reset.
Click to expand...
Click to collapse
Good luck..
davp said:
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
Click to expand...
Click to collapse
I've experienced a similar problem with corrupt /data and couldn't overcome it.
How did you use Samsung recovery when you had CWM recovery flashed?
白い熊 said:
I've experienced a similar problem with corrupt /data and couldn't overcome it.
How did you use Samsung recovery when you had CWM recovery flashed?
Click to expand...
Click to collapse
You either get it from a full flash of stock firmware, or make your own tar with just recovery.img in it (extracted from stock). And flash with odin in the pda.
It is handy to be able to switch recoveries. CWM doesn't seem to match the 3e data wipe/factory reset.
The problem was:
I was playing a game, in the middle of it the Tab reset, I've never had it reset. Then it rebooted to the Samsung Tab 7.7 logo.
I thought, I'm lucky, made a CWM backup. So tried to restore the CWM backup. When the restore got to /data the tab rebooted again, i.e. something was messed with it.
So got stock firmware, flashed it from PC odin, flashed with success. But rebooted to the logo again.
Tried to get into the stock recovery, but it would only show "Updating..." something, I don't remember anymore, but the stock recovery wouldn't boot. Flashed it a couple of times, same result. Had to take the Tab back to the store...
Am kinda afraid to mess with it now, since I don't want it to happen.
So am wondering what to do if the same happens, or just forget CWM and flash stock recovery.img just to be safe?
I had similar issues after hard power-off [long hold power button]. Confirmed with adb into insecure cwm recovery that /data was corrupt. It explained why my restores stopped at /data.
Cwm data wipe, or format data did not help.
I flashed the stock 3e recovery.img in a tar with odin.
3e data wipe/factory reset. Reflash whole stock firmware with odin.
Check system boots ok.
Reflash cwm, then do restore ok.
I have seen stock 3e recovery fail to start properly. It seemed to be related to files/directories on the external sd card. It came up and said something like 'manual mode', 'updating'.
I tried clearing cache and hidden.
I know I deleted at least tmp_sec_fota directory off the external sd card, maybe someting to do with fota is upsetting our tabs from time to time.
Yep, exactly, that's it, it was "Manual mode" and "Updating", same symptoms, I couldn't get past it.
So what you're saying, I had a MicroSD in it, and that's why it was stuck at this? Not sure if I had an SD in it, but I flashed stock like three times, and then still couldn't enter 3e recovery, all the time had this "manual mode" come up...
Thanks for the guide of what you did.
Am downloading the latest Thai firmware now, to extract the stock recovery, so that I'm ready just in case.
Do you just tar the recovery.img and use that for flashing if necessary? No special permissions, nothing?
Sorry, not as clear cut as that... I did three things, cleared cache, cleared hidden, and
then started deleting files on sd. It is possible the problems are in multiple locations,
It is also possible that multiple attempts have an effect.
I personally feel I need both stock 3e and insecure cwm [and odin and adb] to be able to recover this tab. The broken 3e/reboot was my worst experience on this so far.
Use linux tar or the tab's busybox tar, to create an uncompressed tar with recovery.img as the only file. Do not use 7zip to create the tar, it didn't work for me (although it works fine to extract from the stock).
davp said:
Sorry, not as clear cut as that... I did three things, cleared cache, cleared hidden, and
then started deleting files on sd.
Click to expand...
Click to collapse
You mean you did this in CWM recovery? Because I hastily flashed the stock ROM when it wouldn't boot, and then I couldn't get into the recovery anymore and there was no way to flash CWM recovery from PC Odin, or is there?
SD you mean internal? Since with external you just pull it out...
This was my worst experience as well, and want to be ready if it ever happens again.
So to sum it up. If the /data is messed up, should we do the following?
1. In CWM recovery clear cache, clear hidden.
2. Flash stock e3 recovery.
3. In stock recovery wipe everything.
4. Flash stock ROM.
5. Boot.
6. Flash CWM recovery.
7. Restore backup.
please i have the same problem,where i find the stock e3 recovery?
thanks Davp!
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
please,post a link for download the recovery.img tar for to flash with odin.this is my last hope!
My samsung GT S6102(galaxy y duos) is rooted and while modifying build.prop , my phone ended up getting into a boot loop. I have a backup of the original build.prop file but am unable to restore it. I am able to enter into recovery mode. Will i be able to install a custom ROM on my phone even though it is getting boot loops? or is there any way to fix the boot loops?
babai001 said:
My samsung GT S6102(galaxy y duos) is rooted and while modifying build.prop , my phone ended up getting into a boot loop. I have a backup of the original build.prop file but am unable to restore it. I am able to enter into recovery mode. Will i be able to install a custom ROM on my phone even though it is getting boot loops? or is there any way to fix the boot loops?
Click to expand...
Click to collapse
Yes you should be able to install a custom Rom if you have CWM installed and i think you could try to push your Build.prop Backup to your phone using ADB but i dont exactly know how to do that
@OP, if it's rooted then definitely. My HTC Explorer once stuck into boot loop too, I flashed with JaggyRom and it gave me a great experience.
For me, I had to take out the battery and reinsert and then was able to boot into recovery, and from there I flashed it with the custom ROM.
Thank you all
Thank you all who replied, i tried ADB but it was unable to recognize my phone. I am a complete newbie to android but i somehow modified an update.zip file to copy put the build.prop file back to system folder, flashed it in recovery mode and my phone started working again! I am going to be more careful next time, by the way how do i backup and restore using CWM?
babai001 said:
Thank you all who replied, i tried ADB but it was unable to recognize my phone. I am a complete newbie to android but i somehow modified an update.zip file to copy put the build.prop file back to system folder, flashed it in recovery mode and my phone started working again! I am going to be more careful next time, by the way how do i backup and restore using CWM?
Click to expand...
Click to collapse
Google is your friend.
Possiblw Solution
A possible solution is to flash back to your original Stock and try rooting again. the stock should get you out of boot loops
i have a galaxy j7 sm-J700P boost mobile it is stuck in boot loop at the boost mobile boot logo... i have tried:
flashing stock rom with odin.. it says pass ... still boot loops...
iv tried re installing cm auto root... still boot loops
installed twp custom recovery... made a img file b4 all this happend (boot loop was caused by trying to install a rom) try and restore the img file it says it was passes but still boot loops... i have tried wiping everything int the phone through twp wipe (everything but the ex sdcard) then restore and with/with out md5 checking.... still boot loops...
i know the phone is not done for or i would not be able to use oden or recovery but even though both programs say they are not failing at there jobs the phone still boot loops and i cant think of anything that im doing wrong is there any one out there that can pointing me in the right direction or lend me a hand please...
nathanful said:
i have a galaxy j7 sm-J700P boost mobile it is stuck in boot loop at the boost mobile boot logo... i have tried:
flashing stock rom with odin.. it says pass ... still boot loops...
iv tried re installing cm auto root... still boot loops
installed twp custom recovery... made a img file b4 all this happend (boot loop was caused by trying to install a rom) try and restore the img file it says it was passes but still boot loops... i have tried wiping everything int the phone through twp wipe (everything but the ex sdcard) then restore and with/with out md5 checking.... still boot loops...
i know the phone is not done for or i would not be able to use oden or recovery but even though both programs say they are not failing at there jobs the phone still boot loops and i cant think of anything that im doing wrong is there any one out there that can pointing me in the right direction or lend me a hand please...
Click to expand...
Click to collapse
factory reset ?
Hi once I faced same problem with my mobile j700F.
I used KIES pc sute
Use model no. (It is behind the battery in a sticker) u can install stock Rom latest version by using it I forgot steps please search YouTube for that all the best ?
messi2050 said:
factory reset ?
Click to expand...
Click to collapse
nope
cherry1991 said:
Hi once I faced same problem with my mobile j700F.
I used KIES pc sute
Use model no. (It is behind the battery in a sticker) u can install stock Rom latest version by using it I forgot steps please search YouTube for that all the best
Click to expand...
Click to collapse
I tried something like that with another program called smart switch and when I looked at the back of the phone for the (S/N there isn't one just the dex and the hex... so I called boost mobile to ask them to look up the S/N for me... they gave it to me and I put in what they told me it was and it said that it wasn't a valid S/N so I called them back relayed the S/N they told me and they said I had it correct.... so I don't know what to do...
Find the firmware for your phone online, download file (should have .md5 at end of file) then flash file with odin on windows.
Sent from my SM-J700P using Tapatalk
hbranha
messi2050 said:
factory reset ?
Click to expand...
Click to collapse
I have the same phone and carrier. Find and download the following 3 files once you have completed a wipe and factory reset with twrp. 1. Odin 3.12.3 2. Youe stock firmware: j700pvpu1apb7_j700pspt1apb7_j700rvpu1apb7_Home tar.md5---2.90gb. 3. cf-auto-root
j71techn-j71tezm-smj7008.zip found here I believe. 4. twrp 3.0.2-d-j71tespr.img.tar. You must be careful when you install twrp. You must go directly into recovery to prevent a boot loop! Do not use anything that you used to make a backup to restore your phone. Just start all over again!!!
Hi! I have lineage os 17.1 by ivanmeler installed on my S7 flat , I was using opera browser to download a 1GB file, As soon as the download started my phone shut down and got stuck in a bootloop, I booted to the TWRP recovery, And tried to restore a backup that I had done before, but I got an error that says (extractTar error 255), Then I decided to just wipe data and system and flash the rom again, the rom gets flashed, I reboot into system and the phone gets stuck in a bootloop again, what is going on withmy phone, Please someone help!
Thanks in advance.
zariouh said:
Hi! I have lineage os 17.1 by ivanmeler installed on my S7 flat , I was using opera browser to download a 1GB file, As soon as the download started my phone shut down and got stuck in a bootloop, I booted to the TWRP recovery, And tried to restore a backup that I had done before, but I got an error that says (extractTar error 255), Then I decided to just wipe data and system and flash the rom again, the rom gets flashed, I reboot into system and the phone gets stuck in a bootloop again, what is going on withmy phone, Please someone help!
Thanks in advance.
Click to expand...
Click to collapse
Wipe cache before reboot.
cooltt said:
Wipe cache before reboot.
Click to expand...
Click to collapse
I have already tried wipping cache and dalvik cache, I even wiped system and data and installed the ROM again but the phone's still stuck in a bootloop.
Now I'm about to flash through Odin back to stock and see if the phone turns on.
Hm... While I was downloading the stock firmware to flash the phone, I thought of checking the data folder inside the TWRP recovery, And turns out The data is still there, It never got wiped, that's why the phone is stuck in a bootloop, Now what could be preventing the data from getting wipped? I don't get any errors when I wipe the data partition, And this is also strange because usually you get a bootloop when you flash some kind of zip file through the recovery (mods or something like that), but I was just using the browser to download a file , And phone suddenly shutdown and got stuck in a bootloop, Could someone pls help me figure out what's causing the problem
zariouh said:
Hm... While I was downloading the stock firmware to flash the phone, I thought of checking the data folder inside the TWRP recovery, And turns out The data is still there, It never got wipped, that's why the phone is stuck in a bootloop, Now what could be preventing the data from getting wipped? I don't get any errors when I wipe the data partition, And this is also strange because usually you get a bootloop when you flash some kind of zip file through the recovery (mods or something like that), but I was just using the browser to download a file , And phone suddenly shutdown and got stuck in a bootloop, Could someone pls help me figure out what's causing the problem
Click to expand...
Click to collapse
That ROM is in BETA mode, which means it could be lost of things. Your question should be asked on the LOS 17 thread itself but when a ROM is in BETA mode it's very difficult to tell what the problem is. Ask the developer @ivanmeler he might be kind enough to answer you.
Help Me too !!!!
No Lineage based android Q roms booting on my S7 too. I restored stock but then also bootloop.
Pls Help
I'll try to help
Ayushskull said:
No Lineage based android Q roms booting on my S7 too. I restored stock but then also bootloop.
Pls Help
Click to expand...
Click to collapse
Hi! Can you describe the steps that you tried to revert back to stock? Did you use the repair firmware (5 files) or one file firmware?
zariouh said:
Hi! Can you describe the steps that you tried to revert back to stock? Did you use the repair firmware (5 files) or one file firmware?
Click to expand...
Click to collapse
Bro I used these files AP, BL, CP, CSC
Also when I try to boot rom (Aicp) with Cronos Kernel which is for Oneui 2.0 my phone somehow booted but wifi is not working. So can you tell me exact problem as a OneUI based kernel is booting AOSP while when I use morokernel no AOSP based rom boots
Ayushskull said:
No Lineage based android Q roms booting on my S7 too. I restored stock but then also bootloop.
Pls Help
Click to expand...
Click to collapse
Ayushskull said:
Bro I used these files AP, BL, CP, CSC
Also when I try to boot rom (Aicp) with Cronos Kernel which is for Oneui 2.0 my phone somehow booted but wifi is not working. So can you tell me exact problem as a OneUI based kernel is booting AOSP while when I use morokernel no AOSP based rom boots
Click to expand...
Click to collapse
Sorry but I don't have enough knowledge to help with kernels, Now from what I understand is that you tried flashing stock ROM and your phone got stuck in a bootloop, Right? And just to confirm could you mention the model of your s7?
Ayushskull said:
Bro I used these files AP, BL, CP, CSC
Also when I try to boot rom (Aicp) with Cronos Kernel which is for Oneui 2.0 my phone somehow booted but wifi is not working. So can you tell me exact problem as a OneUI based kernel is booting AOSP while when I use morokernel no AOSP based rom boots
Click to expand...
Click to collapse
Flashing stock rom will restore stock kernal. Firmware must be correct for device and region.
Bootloop after Odin Flash.
1. After flash boot into stock recovery
2. How to>>> In this sequence hold volume down+home+power. As soon as phone goes off move finger to volume up while still holding home and power. It may take several attempts as you have to time it just right when the screen goes black.
3. Once in stock recovery choose wipe data/ factory reset. Then choose reboot device
4. Can take 5-10 minutes on first boot. Updating and erasing screens are normal during this process as well as rebooting. Just leave it finish.
If this does not work Reflash stock with Odin but this time uncheck "auto reboot" in Odin options before you start.
Once Flash finish, disconnect from pc and follow 1-4 as above.
Kernel Problem
Pls help as I figured out that all the kernels after v3.18.140.5 are not booting on my phone. Can someone help me with this.
Model No: SM-G930FD
Device: Galaxy S7 Flat
BL: 8 (Latest)
File System: ext4
I have already restored stock many times and formatted my device many times. I used firmware from samfw to go to stock.
That is why no Aosp was booting on my phone
Pls Help