Hi, I need help with a (possibly) soft bricked phone. It boots, yet it reboot itself once it tries to read the multimedia files in the internal storage. The owner is a co-worker so I really don't know how or what could possibly trigger this behavior (a virus perhaps?). The device is not rooted, even if I set usb debugging it just keep rebooting and losing all configuration. Uninstalled apps respawn again once it reboots. I tried to flash it with many Odin versions to a proper stock rom, but when the device reboots all the files remain the same, as if nothing were ever done. I tried wiping everything from recovery mode, didn't work either. Whenever I enter recovery mode it updates some files and says it can't gain access to CSC. I'm not an expert on repairing phones so I'm already out of options, any suggestion would be appreciated.
Edit: Android version is 2.3
Try this: http://forum.xda-developers.com/showthread.php?t=2100642
The guide is meant for Jelly Bean, but works even with Gingerbread and should repair the csc.
Cassiusss said:
Try this: http://forum.xda-developers.com/showthread.php?t=2100642
The guide is meant for Jelly Bean, but works even with Gingerbread and should repair the csc.
Click to expand...
Click to collapse
Didn't work either. All files are still there after rebooting. CSC still fails to load in recovery.
I saw some people with this issue in other android devices, it seems the problem is a corrupted internal memory (nothing can be erased or written). I may just give up
Try to perform this shell command:
mke2fs /dev/block/mmcblk0p3
It will force the format of system partition. You can do it with the Terminal included in TWRP recovery for Gingebread. Once done, you'll have to flash a firmware with Odin to rewrite the system partition.
Cassiusss said:
Try to perform this shell command:
mke2fs /dev/block/mmcblk0p3
It will force the format of system partition. You can do it with the Terminal included in TWRP recovery for Gingebread. Once done, you'll have to flash a firmware with Odin to rewrite the system partition.
Click to expand...
Click to collapse
I can't install custom recoveries, it doesn't recognize external storage and not even Odin can rewrite the recovery.
If you're sure that you can't install TWRP with Odin then I don't know how you could solve your problem, sorry. :/
@Cassiusss Hey Bro,
I have been using epirex cm13 builds
but later these days, i didnt used it much as i was flashing around on my 1+3.
Now, i cant boot in recovery and bootloader, whenever i reboot to recovery or bootloader it boots back to rom.
i try adb commands and flashing recoveries through app but didnt work.
Also I tried odin flash it but as it cant boot in bootloader, how can i revert back.
I am using 12 june build Cm13.
Please help.
Try to reboot to recovery or in download mode with this: https://play.google.com/store/apps/details?id=com.antaresone.quickreboot
Anyway, what error is shown when you try to flash a recovery?
Cassiusss said:
Try to reboot to recovery or in download mode with this: https://play.google.com/store/apps/details?id=com.antaresone.quickreboot
Anyway, what error is shown when you try to flash a recovery?
Click to expand...
Click to collapse
I tried ur mentioned app but it again takes 1-2 secs and boots to system.
I also extracted out boot.img from cm13 and flashed it through rashr but after flashing it again booted to system.
Also tried to factory reset from phone but surprisingly it again didnt show anything and booted to system.
Can You tell me any method to HARD RESET or format its system partition so i can odin it ezily.
I think that formatting system will not bring back recovery or download mode.
What's important is to gain access to download mode (because without it you can't use Odin).
Are you sure that booting your phone while pressing "Volume down" + "Home" + "Power ON" keys is ineffective?
Maybe you'll need an USB JIG to force the download mode...
I guess your device memory is broken. Because my friend's ace3 had the same problem with you, and the service center said that the emmc had been broken. So no hope at all
Related
My phone is almost bricked
I was trying to install sevenrov v3.2 while i was on v3.1 and i ****ed up everything while doing a fullwipe
Right now there is only fastboot&rescuemode available
twrp is not working, because it does no read the digitizer(i cannot press anything)
i can install cwm but should i ?
I believe that is best to flash images through fastboot.
But what images should i flash?
Where to find them?
How should i flash them?
revery0 said:
My phone is almost bricked
I was trying to install sevenrov v3.2 while i was on v3.1 and i ****ed up everything while doing a fullwipe
Right now there is only fastboot&rescuemode available
twrp is not working, because it does no read the digitizer(i cannot press anything)
i can install cwm but should i ?
I believe that is best to flash images through fastboot.
But what images should i flash?
Where to find them?
How should i flash them?
Click to expand...
Click to collapse
Oh dear! You are in a mess. All I can suggest is that you flash the stock recovery and then install a stock ROM for your phone using the force update (dload) method that has been described in other threads. Then you can return to a custom ROM of your choice. As far as I know CWM for this phone is only in Chinese so it may be of little value unless you understand the language.
arthios said:
Oh dear! You are in a mess. All I can suggest is that you flash the stock recovery and then install a stock ROM for your phone using the force update (dload) method that has been described in other threads. Then you can return to a custom ROM of your choice. As far as I know CWM for this phone is only in Chinese so it may be of little value unless you understand the language.
Click to expand...
Click to collapse
cwm has english also but it has no use for me
Only fastboot works
dload method does not complete, the blue progress bar goes up to to 85% and stays there forever...
I am looking for a mathod to create a flashable zip for fastboot
to use fastboot flash filename.zip command
or flash each partition seperatly , i tried the method with huawei extractor
extracted the images system,root,boot,cache,cust,userdata
flashed each one on their partitions
but without success
revery0 said:
cwm has english also but it has no use for me
Only fastboot works
dload method does not complete, the blue progress bar goes up to to 85% and stays there forever...
I am looking for a mathod to create a flashable zip for fastboot
to use fastboot flash filename.zip command
or flash each partition seperatly , i tried the method with huawei extractor
extracted the images system,root,boot,cache,cust,userdata
flashed each one on their partitions
but without success
Click to expand...
Click to collapse
Why you do not flash twrp recovery in fastboot mode and then install a flashable ZIP?
Edit:
In this thread, are the same probs:
http://forum.xda-developers.com/showthread.php?p=56634210
Short: install recovery and try to flash a rom again.
I See your post in this thraed that this not work for you but i think you have to try it again. In fastboot mode you can flash recovery and cust. Its that working?
Can you explain step by step what are you doing?
87insane said:
Why you do not flash twrp recovery in fastboot mode and then install a flashable ZIP?
Edit:
In this thread, are the same probs:
http://forum.xda-developers.com/showthread.php?p=56634210
Short: install recovery and try to flash a rom again.
I See your post in this thraed that this not work for you but i think you have to try it again. In fastboot mode you can flash recovery and cust. Its that working?
Can you explain step by step what are you doing?
Click to expand...
Click to collapse
First of all thank you,
Right now my phone is in a bootloop(not more than 6 sec duration, with short vibration)
3 buttons , power button tricks and combos don't seem to work
The only way to exit the bootloop is by sending the fastbbot reboot recovery command and wait for some loops while you are doing the vol+vol-power combo
Then the phone enters fastboot rescue mode
I get reply when sending the fastboot devices command,
And the phone has unlocked bootloader (OEM command)
I can flash images extracted from the official 135 ROM
I tried cust boot user data system cache recovey , and the are all flashed correctly
But I can't get into recovery mode aftethe reboot (yes I am doing the 3 buttons trick)
I tried different SD cards with different update.app each time, from b135 official and sevenrom3 (yes I put them in /dload folder)
I even tried flashing cwm and twrv recovery images in the recovery partition, but I got in a bootloop after the reboot again
So I am asking if there is anyway to flash the partitions correctly from fastboot or maybe send a kernel image with some offset and run it with the fastboot command
Of course adb does not work, not responding
Maybe reparation the storage?
I don't know
And I am desperare...
revery0 said:
First of all thank you,
Right now my phone is in a bootloop(not more than 6 sec duration, with short vibration)
3 buttons , power button tricks and combos don't seem to work
The only way to exit the bootloop is by sending the fastbbot reboot recovery command and wait for some loops while you are doing the vol+vol-power combo
Then the phone enters fastboot rescue mode
I get reply when sending the fastboot devices command,
And the phone has unlocked bootloader (OEM command)
I can flash images extracted from the official 135 ROM
I tried cust boot user data system cache recovey , and the are all flashed correctly
But I can't get into recovery mode aftethe reboot (yes I am doing the 3 buttons trick)
I tried different SD cards with different update.app each time, from b135 official and sevenrom3 (yes I put them in /dload folder)
I even tried flashing cwm and twrv recovery images in the recovery partition, but I got in a bootloop after the reboot again
So I am asking if there is anyway to flash the partitions correctly from fastboot or maybe send a kernel image with some offset and run it with the fastboot command
Of course adb does not work, not responding
Maybe reparation the storage?
I don't know
And I am desperare...
Click to expand...
Click to collapse
Okay...
your system is so messy. we must bring fully to factory condition first time.
Plesse try to flash stock recovery img. (In your post you write only that you have tryed twrp/cwm).
And then try update in recovery.
I not think your phone is broken. You can try my tool (http://forum.xda-developers.com/asc...eandadjust-t2941186/post56774286#post56774286). There is a stock recovery img in it. In your case you have to flash cust img to.
87insane said:
Okay...
your system is so messy. we must bring fully to factory condition first time.
Plesse try to flash stock recovery img. (In your post you write only that you have tryed twrp/cwm).
And then try update in recovery.
I not think your phone is broken. You can try my tool (http://forum.xda-developers.com/asc...eandadjust-t2941186/post56774286#post56774286). There is a stock recovery img in it. In your case you have to flash cust img to.
Click to expand...
Click to collapse
Thank you but I already did flash the official recovery image, both extracted from a factory update.app and your recovery.IMG also... None of them worked.... Iam still in the same bootloop.
I am starting to believe that the partitions have been ****ed up.
Any way to repartition?
Also is there a procedure to create a flashable zip with huawei software extractor? I edited the accompaning XML to add the p7 device on the list (copy data from p6 and changed the name) created the zip but fastboot doesn't flash the zip because its missing 2 XML files which I can't remember their name.
And at this point I would like to give my 2 cents of advice to everyone who might listen,
Before you flash anything from a microsd, first verify the card with h2testw, and always use high quality microsd and never ever stop a flashing procedure by any means. . i would like to make it more extreme and advise to use a software with copy verification (like richcopy) when you copy files that are going to be flashed.
I tend to believe that a faulty microsd is the cause of my problems... Even though I checked the microsd afterwards and didn't got any errors.
I would advise the ROM creators to append this on their posts!
I have SM-N920CD variant and on stock Android M 6.0.1, Region:THR CSC:N920COJV2BPBA
I tried to flash TWRP through Odin in order to root and flash SkyHigh kernel but got stuck on Samsung logo bootscreen after flashing, I re-flashed my stock firmware to revive my phone and got it back working. I tried two different versions of Odin "Odin3 v3.10.7 and Odin3_v3.10.6" but still same results, I also used different PCs and downloaded TWRP twice.
Am I doing anything wrong or it is just me?
Did you try booting back to recovery and cleaning cache and rebooting. Sounds a little too basic I know but it has worked for me often enough. Just a thought.
Sent from my SM-N920G using Tapatalk
MSAKK said:
I have SM-N920CD variant and on stock Android M 6.0.1, Region:THR CSC:N920COJV2BPBA
I tried to flash TWRP through Odin in order to root and flash SkyHigh kernel but got stuck on Samsung logo bootscreen after flashing, I re-flashed my stock firmware to revive my phone and got it back working. I tried two different versions of Odin "Odin3 v3.10.7 and Odin3_v3.10.6" but still same results, I also used different PCs and downloaded TWRP twice.
Am I doing anything wrong or it is just me?
Click to expand...
Click to collapse
Try flashing again - this time ensure keep system as "read-only" option when you first flash TWRP. Then in TWRP recovery mode (straight after flashing & before rebooting), ensure that "system" is ticked/selected in the "Mount" option in TWRP menu - now reboot to system (you will need to tick/select "system" in Mount option each time if you boot into TWRP recovery mode).
swarup.siddharth said:
Did you try booting back to recovery and cleaning cache and rebooting. Sounds a little too basic I know but it has worked for me often enough. Just a thought.
Sent from my SM-N920G using Tapatalk
Click to expand...
Click to collapse
I can't even get to recovery, I can either get to download mode or stuck on bootscreen. I think it is the recovery getting messed up.
elmor0 said:
Try flashing again - this time ensure keep system as "read-only" option when you first flash TWRP. Then in TWRP recovery mode (straight after flashing & before rebooting), ensure that "system" is ticked/selected in the "Mount" option in TWRP menu - now reboot to system (you will need to tick/select "system" in Mount option each time if you boot into TWRP recovery mode).
Click to expand...
Click to collapse
I tried to enter recovery before rebooting and after flashing but with no luck. I assume to use the typical method (power+up+home). Am I missing something?
MSAKK said:
I tried to enter recovery before rebooting and after flashing but with no luck. I assume to use the typical method (power+up+home). Am I missing something?
Click to expand...
Click to collapse
Start all over again by re-flashing back to stock ROM/stock recovery and try again via Odin to flash TWRP - Make sure to go into recovery (TWRP) mode away straight away by 'power+vol up+home' buttons rather than booting into system.
Then mount system on in TWRP before rebooting to system - This worked for me, no probs since.
Also, ensure you have the correct TWRP .tar for your model (and ??maybe try an older Odin version for flashing TWRP).
Flash this TWRP through Odin:
https://dl.twrp.me/noblelte/twrp-3.0.0-0-nobleltezt-nobleltezt.img.tar.html
elmor0 said:
Start all over again by re-flashing back to stock ROM/stock recovery and try again via Odin to flash TWRP - Make sure to go into recovery (TWRP) mode away straight away by 'power+vol up+home' buttons rather than booting into system.
Then mount system on in TWRP before rebooting to system - This worked for me, no probs since.
Also, ensure you have the correct TWRP .tar for your model (and ??maybe try an older Odin version for flashing TWRP).
Click to expand...
Click to collapse
I tried that but nothing happened, it kept me on download mode otherwise system is booting.
Is it possible to enter recovery directly from download mode without power off?
Battlehero said:
Flash this TWRP through Odin:
https://dl.twrp.me/noblelte/twrp-3.0.0-0-nobleltezt-nobleltezt.img.tar.html
Click to expand...
Click to collapse
That is the download link I have been using.
Sent from my SM-N920C using XDA Free mobile app
I don't think you can go from download mode directly to TWRP recovery mode without power off.......... Try re-booting from download mode but before it re-starts quickly hold 'power+vol up+home'.
Have you tried starting from scratch i.e back to stock recovery, and tried flashing with an older version of Odin?
elmor0 said:
I don't think you can go from download mode directly to TWRP recovery mode without power off.......... Try re-booting from download mode but before it re-starts quickly hold 'power+vol up+home'.
Have you tried starting from scratch i.e back to stock recovery, and tried flashing with an older version of Odin?
Click to expand...
Click to collapse
I tried from scratch but with same results. Could it be ROM related?
elmor0 said:
Start all over again by re-flashing back to stock ROM/stock recovery and try again via Odin to flash TWRP - Make sure to go into recovery (TWRP) mode away straight away by 'power+vol up+home' buttons rather than booting into system.
Then mount system on in TWRP before rebooting to system - This worked for me, no probs since.
Also, ensure you have the correct TWRP .tar for your model (and ??maybe try an older Odin version for flashing TWRP).
Click to expand...
Click to collapse
i have tried that, and got an issues related to mount the storage as well, but able to overcome all that
and now the phone went from stuck on "Samsung" logo, into a loopboot
all this with the Samsung Stock ROM
but at the moment i install Lineage ROM, it works immediately
tried my best to make it work with samsung stock rom, but i couldn't
Hello everyone,
so here is my configuration:
-latest TWRP (3.0.2) with F2S support
-bootloader unlocked
-the N6 is rooted
-ROM: AICP MM
2 days ago I tried to reboot to recovery to flash a more recent version of my AICP ROM. I just had the time to see the TWRP boot logo and then the phone rebooted to load the system. I can't access anymore to my recovery. I tried to rename the twrp directory on the internal SD but it does not change anything.
I reflashed TWRP with ADB and fastboot, but it didn't resolve the problem.
The only change I made recently was to flash a new radio to try to improve my connectivity.
I flashed 5.34 with the new bootloader in fastboot. Then I tried 5.32 without changing the bootloader and finally the 5.36 with the latest bootloader. So I don't know when the problem occured but now my phone even reboots randomly !
So if anyone has a solution you're welcome !
What happens when you connect the N6 to the PC and issue the fastboot boot recovery command?
Check your volume controls. They may be stuck.
Had this Problem on an other device . No recovery flash with fastboot . Dont no how , but Trwp manager APP from playstore did it .
you have to flash twrp right.. if you use a toolkit or flash the recovery with fastboot boot(instead of fastboot flash) then it will only boot into twrp 1 time, then you will need to flash it again if you want to use it again.
Strephon Alkhalikoi said:
What happens when you connect the N6 to the PC and issue the fastboot boot recovery command?
Check your volume controls. They may be stuck.
Click to expand...
Click to collapse
If I'm using "adb reboot recovery", the N6 is rebooting and load the recovery but I only see the TWRP boot logo. Then it's rebooting from the Google logo...
I've flashed the recovery with "fastboot flash recovery recovery.img", but I've also tried with flashify and still the same problem !
In fact I think that's a problem which is related to the upgrade of the bootloader or the radio. I'm with the 71.21 bootloader which came with the latest radio (from the Android N images). Even with the previous bootloader the problem occured. So until which bootloader can I downgrade without bricking my phone ?
Thanks in advance for your suggestions !
marcp39 said:
If I'm using "adb reboot recovery", the N6 is rebooting and load the recovery but I only see the TWRP boot logo. Then it's rebooting from the Google logo...
I've flashed the recovery with "fastboot flash recovery recovery.img", but I've also tried with flashify and still the same problem !
In fact I think that's a problem which is related to the upgrade of the bootloader or the radio. I'm with the 71.21 bootloader which came with the latest radio (from the Android N images). Even with the previous bootloader the problem occured. So until which bootloader can I downgrade without bricking my phone ?
Thanks in advance for your suggestions !
Click to expand...
Click to collapse
yea, you can downgrade, but why? and why are you doing adb reboot recovery? you know that you can use a terminal emulator app on your phone and then reboot recovery using it? every custom rom should also have a reboot recovery option when pressing the power button as well.
simms22 said:
yea, you can downgrade, but why? and why are you doing adb reboot recovery? you know that you can use a terminal emulator app on your phone and then reboot recovery using it? every custom rom should also have a reboot recovery option when pressing the power button as well.
Click to expand...
Click to collapse
I want to try to downgrade the bootloader because this problem occured just after changing it. I've not modified anything else.
I've tried with a terminal emulator, same symptoms.
If I'm using the reboot menu of AICP it's exactly the same behaviour. And that's the usual function I'm using to reboot to recovery. In fact all the commands are working, the N6 is rebooting to recovery but I just see the TWRP logo, then it reboots the phone to the google logo, then it starts the system...
Even if I'm launching recovery from the bootloader, I'm getting the same result.
marcp39 said:
I want to try to downgrade the bootloader because this problem occured just after changing it. I've not modified anything else.
I've tried with a terminal emulator, same symptoms.
If I'm using the reboot menu of AICP it's exactly the same behaviour. And that's the usual function I'm using to reboot to recovery. In fact all the commands are working, the N6 is rebooting to recovery but I just see the TWRP logo, then it reboots the phone to the google logo, then it starts the system...
Even if I'm launching recovery from the bootloader, I'm getting the same result.
Click to expand...
Click to collapse
sounds like you need to clear the recovery partition, then flash twrp again.
simms22 said:
sounds like you need to clear the recovery partition, then flash twrp again.
Click to expand...
Click to collapse
With "fastboot erase recovery" ?
marcp39 said:
With "fastboot erase recovery" ?
Click to expand...
Click to collapse
honestly, i dont remember how.
So here are my last attempts:
-I've tried to clean the cache with "fastboot erase cache", I thought it could be corrupted. BIG MISTAKE ! This time the phone is bootlooping when lauching the ROM...
And of course, I'm making some backups but they are on the "internal sd"... So I can't access my files anymore !
-I've also tried "fastboot erase recovery" and reflashed recovery. No improvement.
-I've downgraded the bootloader from 71.21 to 71.18. Nothing changed.
-I was asking myself if last time I didn't enter a wrong command in typing "fastboot flash boot bootloader.img" instead of "fastboot flash bootloader bootloader.img". So even if I've added benzocore on my AICP ROM, I decided to flash the boot.img from AICP zipfile on the boot partition (+ erase boot). So this time no more bootlooping of the ROM, because I'm stuck on the google logo :crying:...
I've never encounter such a desperate situation ! I don't even understand why I can't boot in recovery...
I could reflash a factory image on my phone, but this would erase all my datas !
Do you think I could reflash a factory image (except the data partition), just to be able to get a valid recovery, and access my files from the computer ? Then I could erase data partition, and reflash a new ROM ?
I don't want to precipitate the next actions because I don't have any joker... and with this stupid idea of not putting any µSD slot in most phones nowadays we're captive of the situation when the phone is bricked ! We can't recover data easily, even with adb pull (which does not work in my case of course).
So please share your ideas, they'll be welcome ! I've read A LOT of posts on XDA and others, but no solution until now....
TIBU to back up your data and then move the data on to PC. Use NRT WUG Fresh tool to flash MOB30M (stock, unroot) and then root/recovery and then start over. If you don't want encrypt then "format data" once in TWRP and then flash custom kernel like HellsCore to not force encrypt.
marcp39 said:
I could reflash a factory image on my phone, but this would erase all my datas !
Click to expand...
Click to collapse
Don't use FlashAll, it's usually broken, anyway. But rather unpack the zip, flash boot and system. And either flash cache or erase it. It does the same.
HueyT said:
TIBU to back up your data and then move the data on to PC. Use NRT WUG Fresh tool to flash MOB30M (stock, unroot) and then root/recovery and then start over. If you don't want encrypt then "format data" once in TWRP and then flash custom kernel like HellsCore to not force encrypt.
Click to expand...
Click to collapse
TIBU for Titanium Backup ? How do you want I use this app since I don't have access to android, only to the bootloader ? You want me to install MOB30M without wiping the datas from my current rom, export the result and then wipe everything to make a clean install ?
marcp39 said:
TIBU for Titanium Backup ? How do you want I use this app since I don't have access to android, only to the bootloader ? You want me to install MOB30M without wiping the datas from my current rom, export the result and then wipe everything to make a clean install ?
Click to expand...
Click to collapse
If you can't backup your data via an app, then you're stuck to flash back to stock losing your info. You can move stuff from your "internal sd" and "data" partitions to your laptop by using fastboot command but I don't remember the exact command
---------- Post added at 03:16 PM ---------- Previous post was at 03:12 PM ----------
HueyT said:
If you can't backup your data via an app, then you're stuck to flash back to stock losing your info. You can move stuff from your "internal sd" and "data" partitions to your laptop by using fastboot command but I don't remember the exact command
Click to expand...
Click to collapse
Just looked it up. You can't backup your data via fastboot but you can using "adb" command. The problem is getting "adb" to work requires "USB Debugging" to be on and android working Thus, you're likely stuck losing your data.
HueyT said:
If you can't backup your data via an app, then you're stuck to flash back to stock losing your info. You can move stuff from your "internal sd" and "data" partitions to your laptop by using fastboot command but I don't remember the exact command
---------- Post added at 03:16 PM ---------- Previous post was at 03:12 PM ----------
Just looked it up. You can't backup your data via fastboot but you can using "adb" command. The problem is getting "adb" to work requires "USB Debugging" to be on and android working Thus, you're likely stuck losing your data.
Click to expand...
Click to collapse
Yeah unfortunately we can do it with adb (like this http://stackoverflow.com/questions/8650407/how-to-copy-selected-files-from-android-with-adb-pull) but not with fastboot. Tomorrow I'll try to flash each *.img from MOB30M separately and see if I can recover a working recovery to access to my datas ! Thanks for your answer btw.
Hello everyone !
So here are the last news...
I've tried an older TWRP like 2.8.x.x same problem.
I've flashed all the *.img from MOB30M except data, but my recovery was still not accessible !!!
So I was resigned to format my data and flash the *.img on it.
This time it worked, my N6 was coming back to life !!! Then I had to root it, flash the recovery, remove encryption and format data with F2FS !
I still don't understand how a corrupted (?) data partition could block the running of recovery, that's strange !
So now I have to restore the data from a TWRP image dated 04-16 I had on my NAS...I can tell you that in the future I won't let my recent backups only on internal storage !
Will you believe me if I tell you that the same problem is occuring again :crying: ?
Several days ago, it started when the impossibility to enter the recovery but this time it does not reboot in bootloader, just stuck... Now I got random reboots and stange behaviour from applications !
I NEVER had a serious problem like that with my N6 before. So I don't understand how can I get data corruption like this ? Last time I was using Benzo kernel, now DeYuS kernel but with no exceptional settings, no overclocking.
I've just disabled "forceencrypt" and convert data to F2FS (no problem before).
So does anyone have a clue about this problem ?
I had an issue where my tablet would just reboot over and over. So I tried to reset it using factory reset. This has me now in a recovery reboot loop.
Hardware:
Galaxy Tab S2 (SM-T713) - wifi only
Software:
TWRP 3.1.0.1
Lineage OS 16
What I've tried:
Wiping cache and davalik cache several times
Formatting data
adb reboot fastboot
Wiping cache, davalik cache, and system (which made TWRP report no system of course)
adb sideload of lineage OS 16 - reported success but TWRP still said no system
re-flashing the lineage OS 16 ROM from SD card (this resolved the no system issue)
Reboot to system from TWRP and adb fastboot after the system re-flash
Odin won't respond and says it can't contact the tablet (multiple usb cords tried , etc) so no luck re-flashing OEM ROM
No matter what, it goes into recovery reboot and won't try to start the system. I can't find anything else to try through searches on XDA, google, etc. Any suggestions?
Not exactly the same, but I thought I had hard bricked my T713 about 9 months ago. I was on stock at the time (not even sure what build), and a bunch of wipes and formats later I was in a TWRP loop. I couldn't even power the machine down. Even that would loop me back to TWRP. I managed to back door my way into download mode by installing the boot.img from the external SD card. That didn't fix anything, but after that I was able to hold down power and volume down and spam the home button until I got to the download screen. After that I was able to get back into odin3_v3.12.5 and load the factory image. I am on LineageOS 16 official now, so I have no idea if this is of any help. I'm pretty sure the boot img came after drilling all the way into the XAR-T713XXU2BRB2_T713XAR2BRB2-20180206 file, since that is the one I eventually got to load.
Yes, I forgot to mention that symptom - it won't power down at all. Just goes back to TWRP.
I'll give that a try, thanks.
apollard said:
Yes, I forgot to mention that symptom - it won't power down at all. Just goes back to TWRP.
I'll give that a try, thanks.
Click to expand...
Click to collapse
Flashing the boot.img file did it! I was able to get in to download and use Odin to reflaah the stock ROM. Now to switch to LOS.
apollard said:
Flashing the boot.img file did it! I was able to get in to download and use Odin to reflaah the stock ROM. Now to switch to LOS.
Click to expand...
Click to collapse
I am so glad that worked for you.
Tried a bunch of things to make the TWRP installation persistent, but it just goes back to MIUI recovery when i reboot from the system.
I'm using TWRP 3.5.2 by Nebrassy.
USB debugging turned on
Correct drivers installed
fastboot devices work Using minimal ADB and fastboot
I have the file renamed as TWRP.img.
Steps i followed:
fastboot boot "TWRP.img" - Correctly boots into TWRP
install the TWRP image to the recovery partition - Happens with no errors
Reboot to system - No errors there as well
Reboot to recovery - Goes back to MIUI recovery.
Can someone please tell me what i should do?
PS: Tried with TWRP 3.6.0 as well just now. Same issue.
Helhound0 said:
Tried a bunch of things to make the TWRP installation persistent, but it just goes back to MIUI recovery when i reboot from the system.
I'm using TWRP 3.5.2 by Nebrassy.
USB debugging turned on
Correct drivers installed
fastboot devices work Using minimal ADB and fastboot
I have the file renamed as TWRP.img.
Steps i followed:
fastboot boot "TWRP.img" - Correctly boots into TWRP
install the TWRP image to the recovery partition - Happens with no errors
Reboot to system - No errors there as well
Reboot to recovery - Goes back to MIUI recovery.
Can someone please tell me what i should do?
PS: Tried with TWRP 3.6.0 as well just now. Same issue.
Click to expand...
Click to collapse
Try again to flash TWRP dirty and if it's started don't boot with software. You have to boot TWRP again by pressing volume + and power button until you'll get vibration , afterwards you'll be in TWRP again, clear dalvik and cache and restart system via TWRP menu
Laptapper said:
Try again to flash TWRP dirty and if it's started don't boot with software. You have to boot TWRP again by pressing volume + and power button until you'll get vibration , afterwards you'll be in TWRP again, clear dalvik and cache and restart system via TWRP menu
Click to expand...
Click to collapse
Sorry mate that didn't work. Still going back to stock recovery...
Since i didn't find a solution to make the installation presistant, i went ahead and flashed Elixir with the temporarily booted TWRP. Then wiped cache and dalvik, flashed the TWRP image, formatted data and then rebooted. Now it works.
Edit: This method did something to my recovery. I can boot to system and recovery fine but TWRP isn't able to mount the data partition. So i'm not able to flash anything or root the device anymore.
I tried formatting data, no luck.
Then tried repairing the data partition. No luck.
Changed the file system to EX2 and then EX4... Nothing.
Anyone know a solution for this?
Helhound0 said:
Sorry mate that didn't work. Still going back to stock recovery...
Click to expand...
Click to collapse
Then you've got to do a flash with stock ROM and miflash via pc
Laptapper said:
Then you've got to do a flash with stock ROM and miflash via pc
Click to expand...
Click to collapse
Would that re-lock the bootloader? And if so do i have to wait 7 more days for it to be unlocked?
I used the Disable-Dm-Verity-Zip directly in TWRP after installation. Worked without a problem.
romuser87 said:
I used the Disable-Dm-Verity-Zip directly in TWRP after installation. Worked without a problem.
Click to expand...
Click to collapse
I read that somewhere too but that didn't help me at all... Maybe i have a bad zip file..
Can you share the zip you flashed?
Also, any idea how i could get this fixed:
Helhound0 said:
Since i didn't find a solution to make the installation presistant, i went ahead and flashed Elixir with the temporarily booted TWRP. Then wiped cache and dalvik, flashed the TWRP image, formatted data and then rebooted. Now it works.
Edit: This method did something to my recovery. I can boot to system and recovery fine but TWRP isn't able to mount the data partition. So i'm not able to flash anything or root the device anymore.
I tried formatting data, no luck.
Then tried repairing the data partition. No luck.
Changed the file system to EX2 and then EX4... Nothing.
Anyone know a solution for this?
Click to expand...
Click to collapse
Helhound0 said:
I read that somewhere too but that didn't help me at all... Maybe i have a bad zip file..
Can you share the zip you flashed?
Also, any idea how i could get this fixed:
Click to expand...
Click to collapse
The attached file worked for me
Helhound0 said:
Would that re-lock the bootloader? And if so do i have to wait 7 more days for it to be unlocked?
Click to expand...
Click to collapse
1. With MiFlash there is an option at the bottom of the screen to lock bootloader. Just make sure it is NOT checked, and you will be safe to use MiFlash without relocking bootloader.
2. When installing TWRP for first time, it is essential that your first reboot is straight back to TWRP - then it becomes persistent, and future reboots to recovery will be to TWRP. If you do not do the first reboot back to TWRP, the stock MIUI ROM recovery reinstalls itself.
HiQual said:
1. With MiFlash there is an option at the bottom of the screen to lock bootloader. Just make sure it is NOT checked, and you will be safe to use MiFlash without relocking bootloader.
2. When installing TWRP for first time, it is essential that your first reboot is straight back to TWRP - then it becomes persistent, and future reboots to recovery will be to TWRP. If you do not do the first reboot back to TWRP, the stock MIUI ROM recovery reinstalls itself.
Click to expand...
Click to collapse
The first ever twrp install i did, i rebooted to system by mistake but i reflashed twrp and made sure to reboot to recovery.... That was the second try. I think i may have tried at least two dozen times since that but it just kept booting back to stock recovery...
I think I'll run with this until the end of Jan and then redo everything from scratch...
Helhound0 said:
Since i didn't find a solution to make the installation presistant, i went ahead and flashed Elixir with the temporarily booted TWRP. Then wiped cache and dalvik, flashed the TWRP image, formatted data and then rebooted. Now it works.
Edit: This method did something to my recovery. I can boot to system and recovery fine but TWRP isn't able to mount the data partition. So i'm not able to flash anything or root the device anymore.
I tried formatting data, no luck.
Then tried repairing the data partition. No luck.
Changed the file system to EX2 and then EX4... Nothing.
Anyone know a solution for this?
Click to expand...
Click to collapse
I'm stuck at this stage. Have you found any solution yet?