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!
Hello guys,
I have a problem, I hope you can help me with.
I used to have an EOS ROM. I decided to do factory reset and thats when my problems started. It didn't boot up anymore. After entering recovery I noticed it couldn't mount System partition. I tried reinstalling the ROM, but no success. Everytime I entered recovery, the System checkbox wasnt marked. So I decided to go back to stock, using http://androidforums.com/threads/return-your-xoom-to-stock.653230/. Now it is stuck at Logo screen and can't enter Recovery. (Goes to Reading ODM fuse, but not any further). I can still enter Fastboot and my laptop detects the tablet, when hooked up to it.
Please help me push the Recovery, cuz I'm getting "device not found" from ADB. I'm kinda lost here... Any help would be appreciated!
Update
I managed to install TWRP, but still can't mount System Partition. On wipe I get "Failed"when trying to clean the system part. I have tried Clockwork, it didn't help either.
Cmon guys! I don't want to JTAG it yet.
HexBox said:
Cmon guys! I don't want to JTAG it yet.
Click to expand...
Click to collapse
I am not very knowledgable about flashing, but one suggestion has come to my mind: if you can now get into TWRP (it wasn't clear whether you could based on your last post), try flashing a ROM without trying to clean the system partition. Just make sure the ROM matches the TWRP (i.e., big part ROM with big part TWRP).
Oh - another thought - folks in a number of threads have stated you need to explicitly follow both the recovery and ROM instructions for the XOOM. If you miss a step, people have had issues.
Hello
Really bad morning.
Woke up to find my OPO (was running COS 12.1 with TWRP), which I had plugged in to charge overnight, stuck on an android screen which said please enter your password. I entered my Google account password and then the next screen says, decryption unsuccessful. "Your password is correct but your data is corrupted. You need to factory reset your device and once you reboot you will have an opportunity to retrieve data backed up with your Google account".
I tried to reboot, just to make sure, and the same set of screens reappeared.
I tried to boot into recovery. The 'teamwin' screen kept flashing to no avail.
Entered fastboot. Flashed recovery, TWRP-2.8.7.0-bacon.
Tried to factory reset but the prompt flashed an error as follows:
'E: Could not mount /data and unable to find crypto footer' and then a series of others, but " could not mount '/data' " was repeated over and over
I'm still stuck here. How to get out of this situation?
PS: When I try to look at the mount options in recovery, the internal storage is labelled as 0 MB. This is scary.
I'm more screwed than you are. Twrp 2870 does not properly support encryption. Great to know an official release is that broken, right? Flash an older twrp, I believe 2860 or 61 are what you want. Try to reflash your cm zip. You're going to have to resetup your device but your internal sd should be fine, it says 0 mb because it's not decrypted so it can't read it. Then you should be okay... Well, except I've never seen that screen you described in the first paragraph. But that usually related to apps, not your internal sd. Good luck. I've accidentally erased all my system and data so I can't adb flash and can't flash from internal sd. My last hope before reformating everything and losing my pictures is to install via USB OTG. Which you could also do.
Good luck
Sent from my Nexus 5 using Tapatalk
Hey, I just found out that there is a way to flash a system image via fastboot! This is why I buy unlocked developer minded phones! If only OP hadn't dropped the ball on the OP2 (I actually got an invite which I didn't even use).
Anyway, go here: https://forums.oneplus.net/threads/...lashing-recovery-roms-kernels-rooting.291274/
and scroll down to "The Bad" In ORANGE text: 2. Recovering from no OS installed and no access to TWRP, fastboot does work.
Since TWRP is basically useless for us, I followed the instructions. I flashed everything EXCEPT the userdata img. AND, instead of flashing the extracted recovery, I just reflashed TWRP 2861 which I have on the PC.
Unfortunately! All my pics are gone. Pretty sure removing encryption with TWRP (before reading it was broken) did it. Try installing a good ROM via USB OTG and let me know if that saves your internal sd. I'd love to know for the future.
soo... i have a fully functional working samsung s7 rooted with the latest magisk and twrp recovery. after all the installation of apps and the root itself, i hopped into twrp recovery just to see if it was also working - turns out it's not reading any partition; leaving me with 0mb internal storage or unable to mount. i would also try rebooting but as soon as i enter "recovery" on twrp, it would automatically boot itself. i've tried researching for the problem but i don't think my research is good enough. i've looked out for multiple solutions, but i couldn't trust any. just wondering if any professionals on xda are able to fix this flaw. thanks!
tldr? working rooted s7, twrp recovery 0mb, automatically rebooting itself, couldn't find solution.
update: it's all gucci, i've managed to figure it out.
Have you tried the patched twrp version? There is a link in google camera port thread. I havent tried but that could work.
hype. said:
soo... i have a fully functional working samsung s7 rooted with the latest magisk and twrp recovery. after all the installation of apps and the root itself, i hopped into twrp recovery just to see if it was also working - turns out it's not reading any partition; leaving me with 0mb internal storage or unable to mount. i would also try rebooting but as soon as i enter "recovery" on twrp, it would automatically boot itself. i've tried researching for the problem but i don't think my research is good enough. i've looked out for multiple solutions, but i couldn't trust any. just wondering if any professionals on xda are able to fix this flaw. thanks!
tldr? working rooted s7, twrp recovery 0mb, automatically rebooting itself, couldn't find solution.
Click to expand...
Click to collapse
not a professional but coincidentally this happened to me today while rooting and installing twrp on my s7 sm-g930L 8.0, i installed twrp 1st and was just using a supersu.zip to root it, booted straight into twrp after flashing and had the same problem you have and couldnt install the zip as it wasnt showing up and also saying 0mb, i couldnt even send the zip to it from my computer either until i pressed format in the wipe menu next to advanced wipe button , it was in a bootloop so i hit format cause i was just gonna reinstall stock firmware but i noticed all the correct mb's appeared in system data etc and i could copy/paste n install the zip, flashed it rebooted and it all works, rooted and twrp on official fw 8.0, you might have to reinstall apps and stuff after but hopefully this helps, goodluck
hype. said:
soo... i have a fully functional working samsung s7 rooted with the latest magisk and twrp recovery. after all the installation of apps and the root itself, i hopped into twrp recovery just to see if it was also working - turns out it's not reading any partition; leaving me with 0mb internal storage or unable to mount. i would also try rebooting but as soon as i enter "recovery" on twrp, it would automatically boot itself. i've tried researching for the problem but i don't think my research is good enough. i've looked out for multiple solutions, but i couldn't trust any. just wondering if any professionals on xda are able to fix this flaw. thanks!
tldr? working rooted s7, twrp recovery 0mb, automatically rebooting itself, couldn't find solution.
Click to expand...
Click to collapse
INSTRUCTIONS BELOW WILL DESTROY ALL DATA ON PHONE GET BACKUPS IF YOU CAN'T IM NOT RESPONSIBLE
Get rid of encryption if you can then try
If you can't get rid of encryption or it didn't work then
Goto wipe and press format data
Type yes and press the tick at bottom left
Then once you see success or error messages go back to wipe
Swipe it to wipe internal memory
After success or error message shows you are most likely to be able to see and mount to internal storage.
ttuleyb said:
INSTRUCTIONS BELOW WILL DESTROY ALL DATA ON PHONE GET BACKUPS IF YOU CAN'T IM NOT RESPONSIBLE
Get rid of encryption if you can then try
If you can't get rid of encryption or it didn't work then
Goto wipe and press format data
Type yes and press the tick at bottom left
Then once you see success or error messages go back to wipe
Swipe it to wipe internal memory
After success or error message shows you are most likely to be able to see and mount to internal storage.
Click to expand...
Click to collapse
This is just temporary the next time you flash you will see 0mb again you will need to format again.
mkl.xda said:
This is just temporary the next time you flash you will see 0mb again you will need to format again.
Click to expand...
Click to collapse
Unless you flash decrypt zip before booting after flashing
ttuleyb said:
Unless you flash decrypt zip before booting after flashing
Click to expand...
Click to collapse
Still the same. Tried it many times.
mkl.xda said:
Still the same. Tried it many times.
Click to expand...
Click to collapse
Try using superman rom and use option called disable encryption that might work,
If you just wanna root then install magisk because it works with encryption
Hey,
Quick rundown: Stuck in a bootloop to some sort of empty bootloader screen which has the readout:
"Start/Restart Bootloader/Recovery Mode/Power Off"
"Press volume key to select, and press power key to select"[Regarding above options]
"FastBoot Mode
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [Gonna leave this out for now]
SECURE BOOT - yes
DEVICE STATE - unlocked" [this line is in red]
Every choice besides Power Off returns me to the same window. What can I do to recover from this?
Background:
So I was trying to update my OP6 to the current OxygenOS while keeping my root using TWRP and Magisk, which I've done in the past without any issue(i.e. go in recovery flash OS, flash current TWRP, reboot back to recovery, flash current Magisk as I understand it). However this time I was running into an issue flashing the Oxygen update getting an error that said it "failed to map file" for the zip. My first instinct was to update TWRP to see if the newest version didn't run into this issue so I flashed that followed by the current Magisk(no reboot in between). After booting back to standard operations everything seemed fine. I went back into recovery and tried the OS update again, but hit the same issue.
I couldn't find anything specific to OP6 with this issue, but similar questions with other devices suggested clearing the dalvik cache, which I tried to no useful effect. Then I came across this thread (forums.oneplus.com/threads/oxygen-os3-i-have-a-problem-please-help.440587/page-2 too new to hyperlink) and did what I think really messed me up which was boldly follow this guy's advice to do an advanced wipe of everything but internal storage(I also left USB storage intact) from TWRP. This failed to fix the issue with the file mapping error when I subsequently tried to flash the update, though I was able to flash TWRP and Magisk successfully again before rebooting and ending up in this loop.
Any assistance in fixing this or general tips on how to not be foolish when messing around with this stuff is greatly appreciated.
Update:
So I followed the advice gleaned from the resourceful person here(https://forum.xda-developers.com/oneplus-6t/help/bootloader-baseband-versions-blank-t3927565) to try working with the device from my computer with fastboot. At first it would recognize the device as "Android" but be unable to find a driver for it and adb/fastboot both failed to recognize it as a device. After installing MiniTool(more as a way to backup what was on the SD card) the proper device driver also got installed and I was able to access it with fastboot; I ran into similar issues as the linked thread above, solved it by switching to b(still failed) then back to a.
Currently I've got it booted into TWRP and I'm working on getting the current Oxygen .zip copied onto the phone storage but the transfer keeps failing after moving a negligible amount.
Update 2:
Via TWRP was able to sideload the current up-to-date standard OS onto it, however my Google backup seems to have decided to disappear on me and the only OP backup I have is ages old. Anyone have recommendations on data recovery tools?
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
NickTheHuy said:
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
Click to expand...
Click to collapse
Good to know, thanks for the info!
I assume that happened when I messed around with advanced wipe, do you know which of the folders I selected that would have been under? And just for future awareness, would that have not occurred had I just used TWRP's standard wipe instead?
You can run a program that will install 9.0.6 from scratch, running a batch file...
Save my life before yesterday....
Your device is bricked
If able to access the TWRP recovery then boot into twrp and try to get all the data stored in your computer.
Then use the Qualcomm flash tool to completely recover from your hard bricked OP6.
from here https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Then its easy, again unlock boot-loader flash TWRP and magisk.