I have previously installed TWRP and Cyanogenmod 13 on my Galaxy S4. I'm now attempting to port CyanogenMod to my brother's Galaxy J5. The recovery has built ok (i think) and I've compressed the image to a tar file using 7-zip. I then successfully flashed this recovery tar onto the phone using ODIN 3.07's PDA tab. The flash says PASS, but on attempting to boot to the recovery I get stuck at the "Samsung Galaxy J5" Splash screen, with the ODIN Download Mode text in the top-left, suggesting to me that the recovery has somehow crashed. The phone is not rooted so I cannot access the logs, and both Kingroot and Kingo Root failed to root the device. Has anyone encountered anything like this before? If so, can you help? I'm kind of stuck here - I created a forum account just to post this.
Thanks in advance.
PS: I can't post the link to the image because I haven't got 10 posts yet. If anyone can tell me how to attach it I'll be more than happy to.
Related
My phone can't bootup nor boot into recovery after flashing double cwm on my Samsung Galaxy SIII mini.
The first CWM was the officail one for my phone but because i can't install zip from my sd card with it (it shows: Error! Signature verification fails.) and it has no option to toggle between signature check off/on i decided to install another version of CWM which i google search and i got one at twrp site name CWM_6.0SG3.zip. I downloaded it and flash it into my galaxy s3 mini with flashify and when i reboot into recovery my phone could not bootup. It just show the Samsung Galaxy S3 mini logo and it hooks there till i remove the battery and place it back.
Please i need an expert help on how i can delete the CWM from the phone and unroot it with PC.
Please help a brother. I just bought the phone last week, i can't afford to loose it.
Thanks.
([email protected])
OkJEPHTAH said:
My phone can't bootup nor boot into recovery after flashing double cwm on my Samsung Galaxy SIII mini.
The first CWM was the officail one for my phone but because i can't install zip from my sd card with it (it shows: Error! Signature verification fails.) and it has no option to toggle between signature check off/on i decided to install another version of CWM which i google search and i got one at twrp site name CWM_6.0SG3.zip. I downloaded it and flash it into my galaxy s3 mini with flashify and when i reboot into recovery my phone could not bootup. It just show the Samsung Galaxy S3 mini logo and it hooks there till i remove the battery and place it back.
Please i need an expert help on how i can delete the CWM from the phone and unroot it with PC.
Please help a brother. I just bought the phone last week, i can't afford to loose it.
Thanks.
([email protected])
Click to expand...
Click to collapse
Do you have Odin? I'm not extremely familiar w/ Galaxy devices, but last time that I was on one, stock firmware was flashed w/ Odin via a computer. Do some searching on how to use Odin to flash stock images on Galaxy devices. Your answer will be there.
Solved
RobbieL811 said:
Do you have Odin? I'm not extremely familiar w/ Galaxy devices, but last time that I was on one, stock firmware was flashed w/ Odin via a computer. Do some searching on how to use Odin to flash stock images on Galaxy devices. Your answer will be there.
Click to expand...
Click to collapse
Thanks dear.
I successfully flashed another recovery into my phone. Now my phone can boot up. I first made the mistake of flashing galaxy s3 CWM recovery into my mini unaware, so when I found out, I downloaded the official recovery for s3 mini then reflashed it with Odin 3.9 using my lappy.
Moderators pls close this thread.
Hey guys, I dug out my old i605 the other day and wanted to update to the latest cm nightly for the device. Not realizing I was about to do something wrong, I downloaded an app called Flashify and installed the latest cm recovery through the app. Well this made my device boot loop. So now, I need to flash a working recovery to my device to fix it. After googling for a bit, I learned that I need Odin to do so. So I am now using Odin v3.10.7. But, I cannot get any recovery tars I've found to flash. They all come back as failed. I'm at a loss here and hope someone knows how to get this thing back up and running.
My PC is on Windows 10 and I do have the latest Samsung drivers installed. On my Note 2 in download mode, it says my current binary is Samsung Official and my system status is custom. What I do not know is what recovery and firmware my i605 was on previously.
Thanks guys
EDIT: I guess what I'd really like to do is get the device back to stock rooted.
Edit 2: Fixed the problem. Uninstalled the Samsung drivers and reinstalled them and changed to Odin 3.07. Ended up restoring the device with the unlocked bootloader restore here: http://forum.xda-developers.com/showthread.php?t=2040264
Hey
Some days ago I flashed my boot-logo (the picture what says Samsung Galaxy S6 edge + when I start my phone) on my SM-G928F via TWRP. I think the file was corrupted, because my phone doesn't start anymore. I can't boot in TWRP or system, because there's a never ending blackscreen. I can only boot into download-mode. I flashed samsung stock rom via Odin but that didn't help, because the logo.jpg won't be replaced.
I tried other stuff like adb sideload but it didn't worked.
I think the only possibility to get my phone alive is to flash the stock samsung boot picture via Odin but I don't know how... I need a tar or md5 file for this...
I hope somebody is able to help me in this f***ing situation :crying:
Best regards
DGB
Check the thread by me mentioned below.
Like my replies and threads, it encourages me ALOT.
https://forum.xda-developers.com/showthread.php?t=1936747&page=2
I recently purchased a Samsung Galaxy SII, GT-I9100 and have been trying to install LineageOS using this guide:
https://wiki.lineageos.org/devices/i9100/install
I'm at the point where I need to flash TWRP. I've downloaded TWRP 3.2.3.0 and using Heimdall, I'm able to successfully flash the image to my phone, Heimdall's output doesn't mention any errors. However, when I afterwards shut down the phone and then reboot to recovery mode, it's still the old stock recovery present.
I have spent the entire weekend trying to troubleshoot a ton of things and trying many suggested solutions, some not working, others throwing me further down the pit of despair. One of the things I've tried was to flash CF Root. My build number ends in KWMS2, so I've been trying to find a CF root build for that but the only thing I found was this post:
https://forum.xda-developers.com/galaxy-s2/help/cf-root-download-ms2-t2880023
Which then had a link to SuperSU which I sideloaded with adb, but that didn't do anything. I also found this post:
https://forum.xda-developers.com/showpost.php?p=35682278&postcount=4
And flash the CF Root image, but that also didn't help with TWRP. I've also looked at the CF Root site but it doesn't list the GT-I9100 and Firmware.Mobi lists all i9100 versions as incompatible with CF-Auto-Root (which I'm assuming is the same as CF Root).
So because of all the trouble I've had, I'm now stuck with a phone that can boot into download and recovery mode, but can't actually boot into Android and that won't install TWRP for some odd reason.
I hope someone can tell me, in detail, what I'm supposed to do to get TWRP to actually work and not just being flashed, because I'm at my wits end.
Follow this guide (the post literally one below yours!) and you will be up and running in no time.
https://forum.xda-developers.com/galaxy-s2/help/guide-tutorial-samsung-galaxy-s2-i9100-t3538601
I went to cf auto root to find a root file for my phone and like an idiot, downloaded a boot+recovery file instead of the rooting file So I accidentally flashed a recovery+boot tar file on my galaxy j5 prime (SM-G570F) and ever since that it keeps restarting after the very first (samsung galaxy j5 prime, Powered by android) page. I flashed twrp and that works, I can use downloading mode and flash other things, I've tried a number of different boot image files, the problem remains, so Ive decided to flash a copy of stock firmware (latest update) instead. Will that fix it? If not, can I fix it, and how? Also pls provide a stock boot image if you can, I want to try that again one last time. Also please reply fast, If my parents find out, they'll kill me