[Q] Stuck on boot loop and cannot flash other ROM - Galaxy Tab 2 Q&A, Help & Troubleshooting

Hello i recently use SlimLP rom until suddenly it was stuck on boot loop . I thought that it must be the problem of the custom ROM and i try to flash other ROM but it seems that i can't proceed to the procedure of wipe data/factory reset because it kept restarting after i checked that option . wiping dalvik cache is fine though . I also did format/data on my solo attempt to fix it but still it won't work.After reading some forum I decided to flash stock firmware but it kept failing on Odin . anyone know what might be the problem of this ? Did I just hardbricked my tab to the point of can't be repaired ? thanks in advance

Try to delete everything in data manually through twrp file manager (Advanced->File Manager)

john99ap said:
Try to delete everything in data manually through twrp file manager (Advanced->File Manager)
Click to expand...
Click to collapse
Im using CWM recovery T.T

iqbaladeee said:
Im using CWM recovery T.T
Click to expand...
Click to collapse
Then, install the latest common twrp by Andi from here: http://andi34.github.io/recoveries_tab2.html
and try it (first try also to wipe data with twrp)

iqbaladeee said:
Hello i recently use SlimLP rom until suddenly it was stuck on boot loop . I thought that it must be the problem of the custom ROM and i try to flash other ROM but it seems that i can't proceed to the procedure of wipe data/factory reset because it kept restarting after i checked that option . wiping dalvik cache is fine though . I also did format/data on my solo attempt to fix it but still it won't work.After reading some forum I decided to flash stock firmware but it kept failing on Odin . anyone know what might be the problem of this ? Did I just hardbricked my tab to the point of can't be repaired ? thanks in advance
Click to expand...
Click to collapse
I can't change my rom, wipe / format doesn't work. Nothing changed after flashing with Odin.
16 GB Tab 2 have a known faulty EMMC (MAG2GA). It can happen, that your EMMC get “read only”, so you can’t perform any write actions (also you can’t format) anymore.
From the EMMC data sheet:
5.1.7 End of Life Management:
The end of device life time is defined when there is no more available reserved block for bad block management in the device. When the device reaches to end of its life time, device shall change its state to permanent write protection state. In this case, write operation is not allowed any more but read operation are still allowed.
But, reliability of the operation can not be guaranteed after end of life.
On a faulty EMMC firmware it happens a lot faster.
What are the symptoms?
Uninstalled apps and deleted files are back after a rebootFormating the storage doesn’t work (after reboot the old rom and apps are back)You can flash whatever you like via Odin - it showes “passed” but after reboot nothing changed (e.g. still no StockRom or still the old Recovery you had previously installed)… there might be some more, but only to mention some …
In most cases, the issue can be fixed by a EMMC firmware update, but you need someone who’s able to do it (possible via ISP, nothing you can do esylie at home yourself). In some bad cases you need to find someone who can replace your EMMC.
source: http://andi34.github.io/faq.html

Related

Stuck in Recovery twrp (can't wipe or install ROM)

First things first, I'm a newbie when it comes to all these.
I installed CM11 after much effort, but some things didn't work out well so afterwards, I installed CM12.1* (FXP-cm-11-20150301-UNOFFICIAL-taoshan).* But then I decided that I wanted to change my Gapps Package, so I went to recovery mode once again to wipe my phone and install CM12 all over again.
The thing is that for some reason I just couldn't wipe it (no error message) but I was able to log in back to the system (CM12).
I messed around with a few settings and finally I decided to install twrp 2.8.7.0 through the flashify app. I rebooted to recovery, tried to wipe again my phone and then, all hell broke loose.
I realized that I cannot wipe internal memory of all things, and cannot install any new ROM. Can't flash another recovery either through windows flashtool like CWM 6.0 Philz touch, for example. Well, it does flash but my phone keeps on logging into the twrp recovery. I also can't flash my original fft (obviously). I can't do really anything besides messing around with twrp options (and I've messed a lot with them). I'm all out of ideas, so please someone help. When trying to wipe internal storage, the following message appears:
E:mkdosfs /dev/block/mmcblk0p32 process ended with ERROR=1
E:Unable to wipe '/sdcard'.
E:Unknown MTP message type: 1
E:Unable to wipe '/sdcard'
I have the whole log, for anyone interested.
Please help and remember, I'm a newbie.
Thank you.
immortalwind said:
First things first, I'm a newbie when it comes to all these.
I installed CM11 after much effort, but some things didn't work out well so afterwards, I installed CM12.1*(FXP-cm-11-20150301-UNOFFICIAL-taoshan).* But then I decided that I wanted to change my Gapps Package, so I went to recovery mode once again to wipe my phone and install CM12 all over again.
The thing is that for some reason I just couldn't wipe it (no error message) but I was able to log in back to the system (CM12).
I messed around with a few settings and finally I decided to install twrp 2.8.7.0 through the flashify app. I rebooted to recovery, tried to wipe again my phone and then, all hell broke loose.
I realized that I cannot wipe internal memory of all things, and cannot install any new ROM. Can't flash another recovery either through windows flashtool like CWM 6.0 Philz touch, for example. Well, it does flash but my phone keeps on logging into the twrp recovery. I also can't flash my original fft (obviously). I can't do really anything besides messing around with twrp options (and I've messed a lot with them). I'm all out of ideas, so please someone help. When trying to wipe internal storage, the following message appears:
E:mkdosfs /dev/block/mmcblk0p32 process ended with ERROR=1
E:Unable to wipe '/sdcard'.
E:Unknown MTP message type: 1
E:Unable to wipe '/sdcard'
I have the whole log, for anyone interested.
Please help and remember, I'm a newbie.
Thank you.
Click to expand...
Click to collapse
try wipe->advanced wipe -> change fs -> ext4
SdtBarbarossa said:
try wipe->advanced wipe -> change fs -> ext4
Click to expand...
Click to collapse
Thank you for your answer my friend, but I actually managed to fix my problem just moments before you posted your answer! What I did was to flash the cm12.1 recovery nightly which logged me into this recovery (although it seemed all messed up and.. broken). Nevertheless, I managed to flash the CM12.1 ROM from there and everything worked fine!
Bro #immortalwind.. I'm having the same problem exactly what you had. Seriously fu***d up with all with boot loop @ recovery. Could not able to hard reset / factory reset at neither CWM nor TWRP. Tried all knows possible ways. Please could you help me here. Any1 who can halp me here pls...
P.S: literally not moving from the boot load, so flashing a ROM could not be possible i think. any other suggestions please.....
RaamXperiaL said:
Bro #immortalwind.. I'm having the same problem exactly what you had. Seriously fu***d up with all with boot loop @ recovery. Could not able to hard reset / factory reset at neither CWM nor TWRP. Tried all knows possible ways. Please could you help me here. Any1 who can halp me here pls...
P.S: literally not moving from the boot load, so flashing a ROM could not be possible i think. any other suggestions please.....
Click to expand...
Click to collapse
Try this out
RaamXperiaL said:
Bro #immortalwind.. I'm having the same problem exactly what you had. Seriously fu***d up with all with boot loop @ recovery. Could not able to hard reset / factory reset at neither CWM nor TWRP. Tried all knows possible ways. Please could you help me here. Any1 who can halp me here pls...
P.S: literally not moving from the boot load, so flashing a ROM could not be possible i think. any other suggestions please.....
Click to expand...
Click to collapse
Just reflash stock ftf. You'll be good to go. If that fails, check drivers and downgrade flashtool. After that, normally, install a boot image with a recovery, install your rom gapps, reboot.
Managed to flash.ftf... Thanks for the help friends.
Sent from my C2104 using XDA Free mobile app

CM13 accidental brick

First of all: I made a thread about bricking my Moto G earlier, but since this is a new issue (and a new Android version) I thought it would be better to make a new thread
So as some of you might have noticed yesterday there was the first release of CM13 for the Moto G and if you had nightlies enabled (like me) you'd just get it as a normal update, except for having to install the new Gapps of course. The problem is I didn't notice that it was CM13 until it was too late... First thing that happened was of course that my Google Play Services we're not working anymore. I tired flashing Gapps for 5.1 but it said that I used the Gapps for the wrong Android version. So I looked in the settings and noticed that I had Android 6.0 . Now I tried flashing OpenGapps for Android 6.0, which worked, but as soon as I booted Android it told me something like "Setup Assistant stopped working" over and over again, so I tried reverting to my latest CM12.1 backup I had, which was a bad idea... My phone was stuck in a bootloop and everytime I tried wiping my phone (except for internal storage) it rebooted when wiping data. Reflashing TWRP didn't help, so I tried flashing stock Android with mfastboot and it got to the point where it was optimizing apps but after that it just did the same thing again (classic boot loop).
Here's my question: How can I get TWRP working again and install CM13 (again if possible without wiping my internal storage or at least being able to back some files up) ?
Can u access TWRP?
Andus1988 said:
Can u access TWRP?
Click to expand...
Click to collapse
Yes I can, flashing and wiping works, except when trying to wipe data
Then don't wipe data?! Wiping data isn't necessary every time!
Andus1988 said:
Then don't wipe data?! Wiping data isn't necessary every time!
Click to expand...
Click to collapse
I know but if I only wipe dalvik, cache and system it didn't work.
Now I tried booting into TWRP and it shows the "no command" screen :'(
I'll write u a PM
I have the same problem would be nice if someone have a solution.
Guys i have a similar problem here, i got the latest update downloaded (cm-13.0-20151207-NIGHTLY-peregrine.zip) and when i clicked on update, the phone went black and nothing work now, i cannot get into fastboot or anything else, it only show "qhsusb_bulk" when I plugged in to the computer, any help??? i would really appreciate it .

Recovery of J700T from "Device storage corrupt you must factory reset" error

Recovery of J700T from "Device storage corrupt you must factory reset" error
Time to talk to the XDA brain trust before I make matters worse. I had rooted my J700T and all was well, also using link2sd. Unfortunately, I made a fatal error by attempting to use FolderMount (rather than creating the links myself), ending up in the Samsung "/data corrupt you must factory reset" error. Also unfortunately, when I earlier flashed TWRP (and then flashed SuperSU via TWRP) I did not choose to wipe the phone at that point to give /data & /system access, so I can't access them through TWRP's adb access. The "reset phone" option on the "you must factory reset" page fails of course, since it tries to boot into recovery which is TWRP not stock. I tried to do a typical TWRP wipe (I can still boot into TWRP of course, and into the download screen), but the result is that when the phone is started normally it continuously loops with the Galaxy J7 splash screen on and off at about seven second intervals (only stopped by pulling the battery).
So the question is, what's the best way to proceed? I saw another page here with the four ODIN files to flash back to stock, but the dropbox account is suspended due to overuse. Ideally, something I could do through TWRP would be even better, and this time I'd like to do the full reset and turn off the crypto so that in the future TWRP has full access to the internal phone data, not just the SD card.
Any guidance would be much appreciated. Thanks!
Can I Restore the Samsung 700t1 withowithout pc
Jersto said:
Can I Restore the Samsung 700t1 withowithout pc
Click to expand...
Click to collapse
If you mean completely back to stock (day one out of box), no.
sent from this device on this app....
So you had twrp as your recovery, you decided to mess with your system partition, you don't have free access to a PC yet it seems you neglected to do the one thing that would have got you out of this mess in a pinch?
That is spending literally 2 minutes to make a nandroid backup?
The main reason really for having a custom recovery. ?
Your only option now is to flash the stock firmware and FORMAT DATA.
Okay guys. Now we got that out of our systems, let's work on some solutions.
All good?
sent from this device using this app....
Thread cleaned up. Please stay on topic.
Regards
Vatsal,
Forum Moderator.

[Completed] [Bricked] Android One [Sprout]

My Current Model is Google Android One Sprout 4.
Hey. My phone started getting system app crashes. So I used Philz Recovery to wipe cache and dalvik cache.
so I got error in wipe cache.
I tried rebooting and it booted by now all the apps just keep crashing . So I went into Recovery again and Tried Format Cache.
Thing is that my cache did format yet the error can't mount cache/logs persisted.
Earlier I had fix such problem by just using SP tool to reinstall stock rom.
I have SP Tool. So I used it to flash stock rom again with scatter files all ok.
But it did not turn on nor did the charging screen came on.
So I tried Lollipop version scatter of sprout4 and both kitkat version using sp tool.
sprout_reference_pack_1379542-KPW53_ALPS.KK2.AOSP.SPROUT.SP.p52-mmx
sprout_reference_pack_1783956-LMY47O_ALPS.L1.SPROUT.SP.p76_user_4g-mmx
Karbonn_Sparkle_V_1783956_Lollipop
Now here is the problem. Sp Tool detects the phone, it flashes using download only. Gets 100% done. But the phone does not saves the rom inside even after it said it wrote successfully.
Tried Format, Format + download. and Download only. But Nothing works even after it's successfully completes.
The Phone does not start except When i plug in my phone even with battery I keep hearing the Connecting and Disconnecting sound constantly every 2 seconds. Do you guys have any idea what could be the cause?
Has Internal memory failed? Or Reading section of motherboard is failed.
Jexboxer said:
My Current Model is Google Android One Sprout 4.
Hey. My phone started getting system app crashes. So I used Philz Recovery to wipe cache and dalvik cache.
so I got error in wipe cache.
I tried rebooting and it booted by now all the apps just keep crashing . So I went into Recovery again and Tried Format Cache.
Thing is that my cache did format yet the error can't mount cache/logs persisted.
Earlier I had fix such problem by just using SP tool to reinstall stock rom.
I have SP Tool. So I used it to flash stock rom again with scatter files all ok.
But it did not turn on nor did the charging screen came on.
So I tried Lollipop version scatter of sprout4 and both kitkat version using sp tool.
sprout_reference_pack_1379542-KPW53_ALPS.KK2.AOSP.SPROUT.SP.p52-mmx
sprout_reference_pack_1783956-LMY47O_ALPS.L1.SPROUT.SP.p76_user_4g-mmx
Karbonn_Sparkle_V_1783956_Lollipop
Now here is the problem. Sp Tool detects the phone, it flashes using download only. Gets 100% done. But the phone does not saves the rom inside even after it said it wrote successfully.
Tried Format, Format + download. and Download only. But Nothing works even after it's successfully completes.
The Phone does not start except When i plug in my phone even with battery I keep hearing the Connecting and Disconnecting sound constantly every 2 seconds. Do you guys have any idea what could be the cause?
Has Internal memory failed? Or Reading section of motherboard is failed.
Click to expand...
Click to collapse
Greetings and welcome to assist. It may be a hardware issue but is your bootloader locked ? I found this useful thread of guides
https://forum.xda-developers.com/cr...ser-roms-recoveries-kernels-mods-how-t2908298
and this thread of firmwares if it helps
https://forum.xda-developers.com/cr...wnload-links-sprout-4-android-m-otas-t3219057
Good Luck
Sawdoctor

SM-920F stuck in bootloop when trying to restore in TWRP

1.Your bootloader status if applicable
2. Rom name with complete baseband/date/version
3. Kernel name
4. Any Mods you are using
5.If you are using Custom Rom, your flashing style i.e dirty/clean or you wiped anything else in specific
6. If you used any guide, link to the guide
7. Root status
8. Your exact problem
9. Any method you tried that failed
10.Any other detail you think would be necessary
1. Unlocked
2.Nemesis [ROM][7.0][DQB7][06/03] Link here!
3. Linux 3.10.x
4. Installed S7 edge battery. guide here!
5. Clean wiped (dalvik, cache, data, system)
6. No particular guide, just random posts through search.
7. Rooted
8. I restore a backup in TWRP and after restore, I get stuck in boot screen (Samsung logo).
9. I've tried wiping several times and restoring different backups. The only way to bypass this boot loop is to do a clean install with no restore. This means flashing everything from the beginning again. I flashed latest TWRP to 10.1.1-0 thinking it might be a issue with bad TWRP. No results.
10. This issue began when I installed S7 edge battery into S6. I would get stuck in bootloop and in TWRP cannot restore my backups so I had to clean install a rom to bypass bootloop. Today I fully discharged and recharged it to calibrate my battery and when booting got stuck in bootloop again. Still can't restore backup in TWRP, so looks like I'll have to do clean install again. Its frustrating cause it feels the slightest change will corrupt my rom and I have no choice but to reflash everything and spend hrs setting everything up. Searched for hours and still couldn't find a answer.
rifek4 said:
ROM releated issue, you cannot pass that if you don't know which files corrupt... Only you can try wipe dalvik then cache and maybe data... But I don't wish good future to working that XD
Click to expand...
Click to collapse
I came from a Lineage 14.1 build before this and I couldn't even restore backup without hanging in boot screen

Categories

Resources