Related
Hello guys, i need serious help with my Samsung Galaxy S3, I just rooted today, and everything was working fine.
I decided to download chainfire 3d, thought i'd enable some unstable games to run, but quite the opposite my phone is now BRICKED.
I tried re-flashing my rom with ODIN, but to no help, the phone remains bricked.
I read some tutorials how to flash using the 'transfer to sd card from PC' rom. But there is another problem..
My pc doens't recognize my phone completely(icon doesn't show in My computer - winows 732bit).
Now im stuck at the Samsung logo, with no other options but hope someone here can help.. ..
Ps; I tried cleaning the cache and dalvik cache from CW mode. Anything else im missing out??..
When you Odin did you wipe data / factory reset after or before? Usually when you Odin and didn't wipe data in recovery mode you will get stuck at the Samsung boot up. So try going back to recovery and do a factory reset /wipe data and see if it boots up pass samsung logo.
teambestyrandy said:
When you Odin did you wipe data / factory reset after or before? Usually when you Odin and didn't wipe data in recovery mode you will get stuck at the Samsung boot up. So try going back to recovery and do a factory reset /wipe data and see if it boots up pass samsung logo.
Click to expand...
Click to collapse
In fact i dont even know if I'm doing it correctly, i only flash one file, the one i ROOTED with. its in the PDA location. I will try to wipe before and after..
Edit: I used ODIN and then i wiped data/factory reset from CW, and still stuck at the boot logo
I also got this error on my PC, MTP USB device did not install correctly. I downloaded the drivers from the official t-mobile support page, so i don't think its the Pc's fault. .
Any ideas?
knight26 said:
In fact i dont even know if I'm doing it correctly, i only flash one file, the one i ROOTED with. its in the PDA location. I will try to wipe before and after..
Click to expand...
Click to collapse
Try wiping data and see if it works. I it should pass the Samsung logo boot up.
teambestyrandy said:
Try wiping data and see if it works. I it should pass the Samsung logo boot up.
Click to expand...
Click to collapse
Doesn't work.
Should i try to format my /data, /sdcard, etc, from the CW menu?.
Is there a risk in doing that?, I dont mind losing my data as long i get the phone back running.
EDIT: I flashed Odin, and it seems to be working now, I'm only left to wait for the phone to pass the bootloop.
what I had forgotten was to flash the stock firmware after i do the CW mode. Lets hope for best, I'll edit this post if it works.
EDIT 2: IT WORKS!. I'd post links to the stock firmwares, but not sure if that is allowed on the site. Anyway just google galaxy s3 stock firmware download.
writing this response to the other people in need of the same help
Hi there all, I need your help.
I decided to sell my Note 2 and as I tried to factory reset the phone for the new owner- it lead to bootloop witch I don't know how to get out of.
Basically it's N7105 model, unlocked and rooted. TWRP recovery and CyanogenMod 13. Was working totaly fine.
Before factory reseting I've read that to completely clean the data you should encrypt the phone and that will scramble the data. So I went and did that.
After I went to factory reset ,but it did nothing and just rebooted. Apparently it's some known bug in CM13, it's not working -many people experience it. And also there is no way to decrypt the data.
So now where I've made a mistake: I went to TWRP and saw one backup from the times I've installed TWRP and rom, and without thinking I pressed to restore.
But that backup was made when I've installed TWRP but OS was stock.
So now it goes through TWRP saying unable to mount data partition and then boots (not fully) to original Samsung OS but with an error: "Encryption failed. Unable to complete encryption due to interuption. Perform factory data reset (erasing all your data) before use. After resetting, try encrypting device again".
And one button to reset the device. If I press that it will go through the TWRP again as above. I can charge the phone and I can press Vol buttons.
I tried to connect with pc through ADB but looks like no devices are found. And in my Device Manager threre is an Yellow Exclamation mark on the phone line saying "The device cannot start". So that's the situation. Is there I can try before canceling sale?
Thanks for your help!
Paul
Did you try to flash the phone with a stock ROM in Odin?
Big thanks!
I did and it's all good!
What a wonderful program Odin- who created it?
Do you know if I lost root after flashing it?
Thanks!
Yes, flashing a stock ROM will remove root.
Odin is a Samsung product: https://en.wikipedia.org/wiki/Odin_(firmware_flashing_software)
I unlocked an H812 (2017 version... serial starts with 702) several months ago and successfully flashed a stock Nougat ROM. Everything was working great until now. This past week, it randomly started shutting down. Yesterday, it got to the point where I could no longer boot into the OS. I think I got to the unlock screen once, and then it shut off. Now it simply boot loops. There is no SD card in the phone. I couldn't figure out how to get into Safe Mode from TWRP, so I did a factory reset. Still boot loop. I then did a factory reset + wiped the internal drive, and then reinstalled Stock N ROM. Still boot looped. Tried reinstalling the ROM again. Still in a boot loop. I know LG G4 has hardware issues. However, I can boot into TWRP just fine, the temperature doesn't look crazy at all, and it can stay in TWRP indefinitely without shutting down.
Something I noticed after wiping the internal drive is that when I'm finished installing N stock, it says it's successful, but when I checked the File Manager to look in the internal SD card, it still shows it as blank (with the exception of a TWRP folder). Is this normal? Isn't the operating system supposed to be installed on this? Why is it telling me that it's finished installing, and yet nothing is there. For fun, I tried booting up, and I'm still in a boot loop. But I assume it's because I have no OS? Or does the internal sd populate with files upon bootup?
I also used used fastboot and flashed the 4 core image (H811 because GPT compatibility said H811). And I also flashed the 4 core TWRP. I tried installing the stock N again, and file manager still shows no files or folders on internal sd except for TWRP folder. Phone still stuck in boot loop (no OS)?
Please, someone help!
I spoke with LG in case it is a motherboard issue, and they said they only replace the 2015 and 2016 model motherboards for free.
threehappypenguins said:
I unlocked an H812 (2017 version... serial starts with 702) several months ago and successfully flashed a stock Nougat ROM. Everything was working great until now. This past week, it randomly started shutting down. Yesterday, it got to the point where I could no longer boot into the OS. I think I got to the unlock screen once, and then it shut off. Now it simply boot loops. There is no SD card in the phone. I couldn't figure out how to get into Safe Mode from TWRP, so I did a factory reset. Still boot loop. I then did a factory reset + wiped the internal drive, and then reinstalled Stock N ROM. Still boot looped. Tried reinstalling the ROM again. Still in a boot loop. I know LG G4 has hardware issues. However, I can boot into TWRP just fine, the temperature doesn't look crazy at all, and it can stay in TWRP indefinitely without shutting down.
Something I noticed after wiping the internal drive is that when I'm finished installing N stock, it says it's successful, but when I checked the File Manager to look in the internal SD card, it still shows it as blank (with the exception of a TWRP folder). Is this normal? Isn't the operating system supposed to be installed on this? Why is it telling me that it's finished installing, and yet nothing is there. For fun, I tried booting up, and I'm still in a boot loop. But I assume it's because I have no OS? Or does the internal sd populate with files upon bootup?
I also used used fastboot and flashed the 4 core image (H811 because GPT compatibility said H811). And I also flashed the 4 core TWRP. I tried installing the stock N again, and file manager still shows no files or folders on internal sd except for TWRP folder. Phone still stuck in boot loop (no OS)?
Please, someone help!
I spoke with LG in case it is a motherboard issue, and they said they only replace the 2015 and 2016 model motherboards for free.
Click to expand...
Click to collapse
Refer to FAQ # 5a in the UsU unlock thread.
Did you do a clean flash of the rom? If not, wipe cache, dalvik cache, system and most important, format data, before installing the rom again.
I note you did not mention flashing the appropriate gapps for the rom version you're trying to boot up. Maybe an idea if you didn't.
If all else fails, go to IRC (Support / IRC Channel paragraph in the UsU unlock thread OP) and get help directly from steadfasterX.
sdembiske said:
Refer to FAQ # 5a in the UsU unlock thread.
Did you do a clean flash of the rom? If not, wipe cache, dalvik cache, system and most important, format data, before installing the rom again.
I note you did not mention flashing the appropriate gapps for the rom version you're trying to boot up. Maybe an idea if you didn't.
If all else fails, go to IRC (Support / IRC Channel paragraph in the UsU unlock thread OP) and get help directly from steadfasterX.
Click to expand...
Click to collapse
Yes, I did a clean flash. wiped cache, dalvik cache, system, and also formatted data (yes, formatted, not just wipe). I did not flash gapps because I flashed a stock Nougat ROM (the same one that has been working for months).
I'm really hoping to know whether it's normal for file manager to be blank and not show the Android, data, folders and all that. I want to know if those folders populate upon a successful bootup, or if they're supposed to be there right after the ROM says it's successfully flashed. That way I can tell if there is an issue with the ROM not installing (which if that is the case, of course I can't boot up).
I have been posting on the UsU thread, but steadfasterX said to flash 4 core boot rom and 4 core TWRP. I did that, but still no boot up. And I *think* there is no boot up because I have no operating system? Again, what is supposed to be in file manager after a ROM flash? I asked steadfasterX but have not gotten an answer.
threehappypenguins said:
Yes, I did a clean flash. wiped cache, dalvik cache, system, and also formatted data (yes, formatted, not just wipe). I did not flash gapps because I flashed a stock Nougat ROM (the same one that has been working for months).
I'm really hoping to know whether it's normal for file manager to be blank and not show the Android, data, folders and all that. I want to know if those folders populate upon a successful bootup, or if they're supposed to be there right after the ROM says it's successfully flashed. That way I can tell if there is an issue with the ROM not installing (which if that is the case, of course I can't boot up).
I have been posting on the UsU thread, but steadfasterX said to flash 4 core boot rom and 4 core TWRP. I did that, but still no boot up. And I *think* there is no boot up because I have no operating system? Again, what is supposed to be in file manager after a ROM flash? I asked steadfasterX but have not gotten an answer.
Click to expand...
Click to collapse
I know when I've clean flashed a rom in TWRP, I show no files in Internal in the USB connection screen. If you didn't get an error indicating no OS installed, I wouldn't worry about that for now.
Again, refer to FAQ #5a. Did you immediately flash the baseband file after the rom flash? Did you re-install the N modem? etc, etc. You may have to re-install the bootloader stack etc. Go through all the steps.
And again, go to IRC if all else fails.
Note: Please learn to use the Thanks button (bottom right of post), when members answer your questions or provide useful information when trying to help. It's an XDA courtesy - please learn to use it.
sdembiske said:
I know when I've clean flashed a rom in TWRP, I show no files in Internal in the USB connection screen. If you didn't get an error indicating no OS installed, I wouldn't worry about that for now.
Again, refer to FAQ #5a. Did you immediately flash the baseband file after the rom flash? Did you re-install the N modem? etc, etc. You may have to re-install the bootloader stack etc. Go through all the steps.
And again, go to IRC if all else fails.
Note: Please learn to use the Thanks button (bottom right of post), when members answer your questions or provide useful information when trying to help. It's an XDA courtesy - please learn to use it.
Click to expand...
Click to collapse
Here's what I've done now at this point. I tried creating and flashing a 2 core boot image via fastboot, and then flashing the 2 core TWRP. Still bootloop.
I flashed the v29a N modem and UsU kernel for my device (H812), then went to TWRP and flashed stock N ROM again. Still bootloop.
I flashed N stock modem again, then baseband package for my model. Still bootloop.
I'm about to extract my MM modem and flash that.
Beyond that, I don't know what to do. I had zero issues with the UsU method originally and everything went fine and has been fine for the last couple of months since I did it.
Well, roadblock again. I attempted to extract modem from the kdz with SALT in FWUL, and after a while, I get a popup window that says: "This KDZ has an ARB of: arb-detect-error" and then it says "Select partition(s) to EXTRACT:"
Except there are no partitions to select. And my only options are "Deselect All" "Extract" and "Abort." If I try "Extract," I get the error, "No partition selected or abortioned by user."
I did make sure I had the latest version of SALT.
Gave up on salt to extract the kdz and turned to Windows. I didn't know what else to do. I was able to extract the .dz, and then extract the modem_32768.bin file. Transferred it to FWUL, renamed it modem_32768.img, and then typed
Code:
fastboot flash modem modem_32768.img
Rebooted, and still have boot loop.
I'm going to investigate this bootloader stack thing (I don't even know what that is). But again, I really don't understand why this all worked fine for a couple of months.
threehappypenguins said:
Gave up on salt to extract the kdz and turned to Windows. I didn't know what else to do. I was able to extract the .dz, and then extract the modem_32768.bin file. Transferred it to FWUL, renamed it modem_32768.img, and then typed
Rebooted, and still have boot loop.
I'm going to investigate this bootloader stack thing (I don't even know what that is). But again, I really don't understand why this all worked fine for a couple of months.
Click to expand...
Click to collapse
Read about the ilapo it can't be fixed by software it may just help to enlenghten life.
Sent from my OnePlus 6T using XDA Labs
Hello everyone sorry to bother. So I was flashing a custom rom for my op5t and followed the usual steps : wipe system data cache and flashed the rom+gapps+magisk. And when I tried to boot the device it got stuck at the oneplus logo it didn't even got into bootloop. So I decided to flash rom again and wiped the data again but there I saw all the files were encrypted. I don't know how did it happen I wasn't encrypted in the beginning and now I can't install anything, the phone does not have any OS so it can't boot up. I don't want to lose my data is there anything I can do without locking the bootloader?
Moderator action: locked. Please only post your inquiry once. Stick with this thread. Thanks.
Hi everyone
After some research, I can't find a succeful way to install TWRP recovery instead of Lineage stock recovery.
It's really embarasing because I'm currently setting up my brand new XZ2c compact to run the way I want it to on Lineage OS 17.1 with Magisk and Xposed modules, and I experienced 3 or 4 endless bootloop that led me to fully format my phone after bunch of hours setting it and tailoring it up... Huge waste of time, frustration overload, as you could expect. So, I really miss tremendous TWRP backup fonctionnality I used to run frequently on my old Z5c... :crying:
Does anyone here as figured out how to replace Lineage stock recovery on this device? Is so, I'd really to hear him out
Have a good week-end!
tomboudiboudi said:
Hi everyone
After some research, I can't find a succeful way to install TWRP recovery instead of Lineage stock recovery.
It's really embarasing because I'm currently setting up my brand new XZ2c compact to run the way I want it to on Lineage OS 17.1 with Magisk and Xposed modules, and I experienced 3 or 4 endless bootloop that led me to fully format my phone after bunch of hours setting it and tailoring it up... Huge waste of time, frustration overload, as you could expect. So, I really miss tremendous TWRP backup fonctionnality I used to run frequently on my old Z5c... :crying:
Does anyone here as figured out how to replace Lineage stock recovery on this device? Is so, I'd really to hear him out
Have a good week-end!
Click to expand...
Click to collapse
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
kurtn said:
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
Click to expand...
Click to collapse
Thanks for replying!
Ok, but if I want this recovery bootable permently away from my computer?
kurtn said:
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
Click to expand...
Click to collapse
Thanks for your (minimalist) advice. Literally just lost 1 hour fixing the bootloop it just caused by following it, I'm delighted.
Behind my post, I was hoping to find someone who could explain a bit more the process of replacing/flashing/booting/(wateveryouwanti'mnotanexpert) a recovery, and at the same time avoiding me wasting more hours in bootlooping/formating/reinstalling. Hopefully, this time I succeed to came out of the bootloop without formating and reseting eveything, but I almost lost my nerves.
All of this is a bit cloudy for me, could you (or someone else that would give me a little of his time to) be pedagogue and explain clearly the whole proccess (and especially what you should avoid if you don't want to get stuck in a bootloop/getting scarying corrupted device message) ?
No one?
tomboudiboudi said:
No one?
Click to expand...
Click to collapse
Wrong forum. Search in you device section.
Hi guys!
Today I tried again to install TWRP on my Sonyh Xperia XZ2C because LineageOS Recovery doesn't provide Nandroid backup, which is a shame.
I tried many ways described over the web, none of those worked, and I ended up with a boot loop at startup with that naughty message "your device is corrupted it cannot be trusted and will not boot". I can't boot to Lineage, neither to recovery. I'm stuck.
With device turned off, I can eventually press volume down, plug it to computer, access fastboot mode (blue led), flash+boot the LineageOSrecovery.img, then the device restart, Sony logo appears... and that's all, I'm stuck with logo in boot loop, and I can't go anywhere further.
I tried to change boot slot (without knowing if it could help with this problem at all) but I alway get "unknown option".
I'm panicking right now, I can't find any way out to this bootloop, if someone could help it will be sooo appreciated!
I tried hard to find a solution for 4 hours now, I'm completly stuck and I can't even sleep. That's why I finally reached out here.
tomboudiboudi said:
Hi guys!
Today I tried again to install TWRP on my Sonyh Xperia XZ2C because LineageOS Recovery doesn't provide Nandroid backup, which is a shame.
I tried many ways described over the web, none of those worked, and I ended up with a boot loop at startup with that naughty message "your device is corrupted it cannot be trusted and will not boot". I can't boot to Lineage, neither to recovery. I'm stuck.
With device turned off, I can eventually press volume down, plug it to computer, access fastboot mode (blue led), flash+boot the LineageOSrecovery.img, then the device restart, Sony logo appears... and that's all, I'm stuck with logo in boot loop, and I can't go anywhere further.
I tried to change boot slot (without knowing if it could help with this problem at all) but I alway get "unknown option".
I'm panicking right now, I can't find any way out to this bootloop, if someone could help it will be sooo appreciated!
I tried hard to find a solution for 4 hours now, I'm completly stuck and I can't even sleep. That's why I finally reached out here.
Click to expand...
Click to collapse
In fastboot mode you should be able to flash stock rom
Is there any way to make the device boot on the Lineage partition without wiping everything?
For an unknown reason, I succed to boot on Lineage Recovery (not TWRP) this morning. I flashed LineageOs rom.zip using adb sideload. After rebooting, the recovery tolds me that I had to wipe everything because the system partition seems to be corrupted, so I did.
I'm a bit tired to lost everything since I made all of this to do Nandroid backups with TWRP........ but I have a fresh new install, my phone works again so it's fine.
But I still need to make Nandroid backups.
Kurtn, you seem to have skills and knowledge. As you can see, I didn't succeed to boot Twrp since october 2020. I don't see why it would be impossible with my device, I'm probably messing something somewhere.
Would you share your knowledge and help me booting/flashing TWRP without bricking everything again?
Could you make an answer instead of a single smiley?
tomboudiboudi said:
Could you make an answer instead of a single smiley?
Click to expand...
Click to collapse
Sorry, i cant. I don't backup and I don't have an a/b device.
Ok, thanks anyway!
tomboudiboudi said:
I didn't succeed to boot Twrp since october 2020. I don't see why it would be impossible with my device, I'm probably messing something somewhere.
Would you share your knowledge and help me booting/flashing TWRP without bricking everything again?
Click to expand...
Click to collapse
Btw.
Code:
fastboot flash boot recovery.img
DOES install the recovery, since it's permanently flashed. Don't know why they (lineage) didn't change that.
kurtn said:
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
Click to expand...
Click to collapse
However @tomboudiboudi , you could boot twrp manually using
Code:
fastboot boot twrp.img
With that, twrp should appear and ask for a password to decrypt your userdata partition.
If that works, you could try to flash boot this very same twrp.img. Maybe you need an additional twrp.zip too which will be sideloaded within twrp itself.
A note for you which might help: I wanted to update my lineage recovery manually using fastboot (older lineage recovery to newer one) and found that nothing (except fastboot) was booting at all after flashing this.
However, after dirty flashing lineageOS.zip, everything worked fine again.
Keep in mind that flashing a recovery will modify your boot.img. If this one doesn't work / is corrupt etc., your os won't boot up.
User699 said:
Btw.
Code:
fastboot flash boot recovery.img
DOES install the recovery, since it's permanently flashed. Don't know why they (lineage) didn't change that.
However @tomboudiboudi , you could boot twrp manually using
Code:
fastboot boot twrp.img
With that, twrp should appear and ask for a password to decrypt your userdata partition.
If that works, you could try to flash boot this very same twrp.img. Maybe you need an additional twrp.zip too which will be sideloaded within twrp itself.
A note for you which might help: I wanted to update my lineage recovery manually using fastboot (older lineage recovery to newer one) and found that nothing (except fastboot) was booting at all after flashing this.
However, after dirty flashing lineageOS.zip, everything worked fine again.
Keep in mind that flashing a recovery will modify your boot.img. If this one doesn't work / is corrupt etc., your os won't boot up.
Click to expand...
Click to collapse
I fear you still haven't realized, what a/b means. The classic concept of having a recovery partition, where you can boot twrp at any time - doesn't apply.
kurtn said:
I fear you still haven't realized, what a/b means. The classic concept of having a recovery partition, where you can boot twrp at any time - doesn't apply.
Click to expand...
Click to collapse
You're right, there is no recovery partition.
As I said: Flashing a recovery.img will modify the boot.img.