Greetings everyone,
today I purchased a new G950F S8. Immediately I wanted to root the device, and in order to do so - installed TWRP via Odin 3.13.3 (flashed the newest version for Exynos models downloaded from their web-site). The flashing process went through fine - everything checked out, at least seemingly.
When I first restarted my phone (followed the instruction), it booted up in it's default recovery, NOT TWRP recovery. That seemed strange, so I double checked the instruction - which claimed I need to quickly boot into recovery, as soon as the flashing process is done and the phone is first restarted. Maybe I was slow.. I re-flashed TWRP, and this time it booted into TWRP. Now, this is when the problem started.
I didn't touch anything within TWRP, I was just satisfied to see it installed. When I tried to restart into System, I got the Samsung logo bootloop. I couldn't power off the phone, nor could I boot it up. I could, however, alternate between download mode and TWRP. I tried changing System format and then changing it back to original (saw that somewhere), but it didn't help. Tried factory reset without results.
Finally I downloaded official stock ROM for Italy, flashed via Odin and everything works fine.
Thing is - I really want to root my phone. Had no issues with my Note 3 previously. I wouldn't want to get into more trouble, so I'm kindly asking for some advice, or a useful link (I searched all over but didn't find anything that would make me feel confident enough not to screw it up again) to how I can do this safely.
I'm using Android 9, official stock ROM for Italy.
Misce said:
Greetings everyone,
today I purchased a new G950F S8. Immediately I wanted to root the device, and in order to do so - installed TWRP via Odin 3.13.3 (flashed the newest version for Exynos models downloaded from their web-site). The flashing process went through fine - everything checked out, at least seemingly.
When I first restarted my phone (followed the instruction), it booted up in it's default recovery, NOT TWRP recovery. That seemed strange, so I double checked the instruction - which claimed I need to quickly boot into recovery, as soon as the flashing process is done and the phone is first restarted. Maybe I was slow.. I re-flashed TWRP, and this time it booted into TWRP. Now, this is when the problem started.
I didn't touch anything within TWRP, I was just satisfied to see it installed. When I tried to restart into System, I got the Samsung logo bootloop. I couldn't power off the phone, nor could I boot it up. I could, however, alternate between download mode and TWRP. I tried changing System format and then changing it back to original (saw that somewhere), but it didn't help. Tried factory reset without results.
Finally I downloaded official stock ROM for Italy, flashed via Odin and everything works fine.
Thing is - I really want to root my phone. Had no issues with my Note 3 previously. I wouldn't want to get into more trouble, so I'm kindly asking for some advice, or a useful link (I searched all over but didn't find anything that would make me feel confident enough not to screw it up again) to how I can do this safely.
I'm using Android 9, official stock ROM for Italy.
Click to expand...
Click to collapse
Bro stick with stock you got a nice expensive phone you don't need to chance messing it up
Thot Conqueror
Misce said:
Greetings everyone,
today I purchased a new G950F S8. Immediately I wanted to root the device, and in order to do so - installed TWRP via Odin 3.13.3 (flashed the newest version for Exynos models downloaded from their web-site). The flashing process went through fine - everything checked out, at least seemingly.
When I first restarted my phone (followed the instruction), it booted up in it's default recovery, NOT TWRP recovery. That seemed strange, so I double checked the instruction - which claimed I need to quickly boot into recovery, as soon as the flashing process is done and the phone is first restarted. Maybe I was slow.. I re-flashed TWRP, and this time it booted into TWRP. Now, this is when the problem started.
I didn't touch anything within TWRP, I was just satisfied to see it installed. When I tried to restart into System, I got the Samsung logo bootloop. I couldn't power off the phone, nor could I boot it up. I could, however, alternate between download mode and TWRP. I tried changing System format and then changing it back to original (saw that somewhere), but it didn't help. Tried factory reset without results.
Finally I downloaded official stock ROM for Italy, flashed via Odin and everything works fine.
Thing is - I really want to root my phone. Had no issues with my Note 3 previously. I wouldn't want to get into more trouble, so I'm kindly asking for some advice, or a useful link (I searched all over but didn't find anything that would make me feel confident enough not to screw it up again) to how I can do this safely.
I'm using Android 9, official stock ROM for Italy.
Click to expand...
Click to collapse
When you first flash twrp and boot into twrp you have to format phone from within twrp, then flash no Verity zip and rmm bypass zip. If you reboot system before you format then you get bootloop. There is full instructions in a thread here on XDA.
Related
Phone: Samsung Galaxy Core Prime
MetroPCS
Model: SM-G360T1
ROM and Kernal: Stock
Issue: Touchscreen doesn't work in TWRP.
Links:
Where I got TWRP: https://dl.twrp.me/coreprimelte/
The guide I followed: http://www.android.gs/install-twrp-recovery-v3-0-0-on-samsung-galaxy-core-prime/
I got this phone from a friend. I tried to install TWRP via ODIN, but I've had some trouble. Initially, when I installed TWRP it didn't appear after I rebooted the phone. After doing some research, I found that this is normal for stock ROM's, and that they tend to replace any custom recovery with the stock one. I learned that in order to access TWRP, I need to remove the batter before rebooting, and then reboot directly into TWRP without letting the OS see the light of day. But when I get to TWRP, the touchscreen breaks. I can't interact with anything. I can still boot into the operating system just fine, but doing so removes the recovery, and I can't interact with TWRP outside of locking it by using the power button. I think this issue could be solved by installing a custom ROM, but I don't know if that's even possible without TWRP. This seems to be a loop of nothing, never going anywhere.
All I need is for the touchscreen to work in TWRP, I can handle the rest from there. Thank you for any help, and Happy Holidays!
Edit: After further research, I've discovered that the problem could lay in the recovery I'm using. I'm trying to install the latest TWRP version found in the link above, but I've tried almost all of them. Is there any information on any specific version of TWRP I should use?
Hi,
as the title says, my phone is not booting anymore, after I transplanted the motherboard from a frame with a broken screen into a new frame (from china).
Abbreviations used:
RR => Resurrection Remix 5.8.5
CWM => ClockWorkMod Recovery 6.0.4.6-kitkat
TWRP => TeamWinRecoveryProject 3.2.1-1
I was using RR from the Rock Stable Setup on it before and it worked beautifully.
What happened:
I performed the mainboard-transplantation according to the iFixit guide
I held the power button to boot the phone:
It vibrated
It showed this screen for a couple of seconds
It vibrated
Back to step 1
And that until I removed power.
Then I tried to boot into recovery mode by holding the key combination on boot:
Same as above, but with this bootscreen
Then I tried to boot into download mode by holding the key combination on boot:
The warning to confirm download mode poped up and I got to see this screen.
I connected it to my PC and opened odin 3.09 and it recognized the device.
I tried to get adb and fastboot to see the device, but nothing worked. (In the old frame and before I broke the screen, it would be recognized at this stage)
I flashed TWRP with odin, odin showed the green "PASS!", but booting to recovery still failed.
I proceeded to flash a stock ROM, which had worked when I had issues with RR.
It worked, I went through the Android 5 setup process, enabled debug and connected adb.
adb saw the phone.
I rebooted to recovery and stock recovery booted correctly.
Sideloading anything with adb failed due to signature verification.
I then went back to download mode and flashed CWM successfully.
It now boots into recovery, but whenever I try to flash anything with CWM, it fails showing this screen
Or something similar (the photo comes from flashing RR 5.8.5)
I have both linux and windows properly setup and used both with adb, fastboot and odin (only windows)/heimdal (only linux).
I checked drivers and usb cables.
I opened the phone back up and checked all connections.
But I can't get any version of RR, CyanogenMod or LineageOS on there.
I've searched the internet, but people that have these kinds of problems after replacing parts of their phones, seem to only have driver issues or skipped steps in the manuals of custom ROM installations.
If you have any idea on what I could try or what I'm doing wrong or not doing, please leave an answer.
I'll keep this post updated below here:
(no updates, yet)
Thanks so much in advance
Simon
Your picture shows stock recovery not CWM .
Try flashing TWRP recovery through Odin .
I did flash TWRP and afterwards there was no recovery anymore.
When I flash CWM, I get the recovery shown in the photo.
The stock recovery has a black background and no touch controls for me.
What you saw must have been CWM.
Update: I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS.
The only working OS I have at the moment is a stock android 5.0, which is not all that useful...
If anyone has an idea, why I can't or how I can find out what is causing it, please say so.
I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS. )
What do you mean by ANY ??
Well, exactly that.
Regardless of what zip I flash, I end up with a bootloop.
If I flash a recovery zip, the recovery bootloops, but the OS still boots.
If I flash a custom ROM, I can still boot into recovery fine, but booting normally results in a bootloop.
The only way to get software onto my phone has been via odin and only an old CWM, Philz Touch, TWRP (Version 2.8.7.0 and below) and STOCK Android (Versions 4.3, 4.4.2, 5).
Anything else I have tried so far did not result in an error, but I couldn't boot into it either.
If you have ideas for software I can try flashing, please tell. I really have no idea how to get the damn thing to work again...
What happens when you flash correct stock rom via Odin ??
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
AnyTimeTraveler said:
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
Click to expand...
Click to collapse
In that case phone is OK .
Usual is that user is failing to follow instructions .
Not sure what you mean by fastboot on a N9005 .sounds like not a N9005 .
Personally with TWRP 2.8.70 i would be flashing something like .
https://forum.xda-developers.com/galaxy-note-3/development/rom-magma-nx-rom-t3508672
as its correct TWRP .
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
AnyTimeTraveler said:
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
Click to expand...
Click to collapse
Dear Mate..
Have you solved your problem? I have same problem after transplating N900 frame.
Sorry, I gave up, since I dearly needed a working phone and bought a OnePlus 3 cheaply from ebay second hand. It's been working like a charm and I threw the note into my museum after I softbricked it for the n-th time and couldn't get it out of a bootloop that didn't leave me time to go into Fastboot.
Sorry friend, but I can't help with this.
after reading a lot of similar threads, seems like the hardware is the cause of us not able to update to higher versions of twrp(& custom roms)
It's been a while since I unlocked my mobile's bootloader, following the steps of a you tube video specifically from the Tecnocat channel. Everything was going well until I thought I did not have any system because whenever I started it it went straight to recovery. Install roms and the same. Until I decided to go directly to the bootloader and start it from there. Of surprise it worked, there was no problem with the system. Everything works fine, but every time I turn off the phone and turn it on it starts in recovery and I have to boot it in fasboot mode and from there start the system. It's tedious, and for example I can not do restarts. I already reprimand the recovery from different sources, and I can not find a solution. Please help
Similar issue
I'm having a similar issue except mine started after mistakenly installing a OTA update (Sept. I think) on a xt1687. Rooted (magisk) with TWRP recovery on stock ROM. Every time I boot it goes into recovery mode, and the only way to get into the phone is through TWRP Reboot > Bootloader, then Start.
I tried flashing the latest stock ROM I could find, but still have the same issue. Only now I'm getting nagged with Install System Update New Version NPNS25.137-93-18. I know better now to follow the OTA update guides, but how do I get the phone back to the way it was before the update? Any help is greatly appreciated. Thanks in advance!
Hi, so here's the background. I got my Moto X Pure Edition back when Motorola was selling it on their website, I used MotoMaker and everything. I had the phone for a few months and I decided to unlock the bootloader, with success. Afterwards, I couldn't get the 6.0 update, my phone would restart with failing to update after downloading the OTA. I now know why that was happening, but didn't know then.
Two Days Ago: I had my Moto XPE sitting in a drawer and wanted to try to rescue it. I found the stock factory image for Marshmallow on Moto's dev website and found a guide to restore it back to factory, still with an unlocked bootloader, but that was fine. I knew 7.0 came out for it and found the OTA zip online and attempted to flash it with the stock recovery, it didn't work and I know why. It had something to do with the bootloader version or something.
Yesterday: I did some research and I ended up flashing TWRP twrp-3.2.3-1-clark.img for my recovery. I've had previous experience with TWRP and thought it would be a good fit. After doing that, I did some looking around for ROMs that would get me up to 7.0. I found one called crDroid and it worked very well. It was very smooth. I went to bed last night with that on the phone and made a backup of it.
Today: While on my way to work this morning, I looked up Oreo roms, and I found an unofficial version of LineageOS and flashed that. Everything went well, it booted up fine but it was very slow. I powered off the phone (to save battery) for a few hours and decided that I wanted to go back to the previous ROM, crDroid. Before I restored, I wanted to wipe everything. When I went to wipe, TWRP ended up crashing. I had looked away from my phone before it crashed, so I thought it just rebooted. I went to restore from my backup and it crashed again. I did some Googling and tried different version of TWRP for the XPE, but every I try to wipe or restore or flash, it keeps crashing. One post said to "Fix Contexts", and now when I go to do a regular wipe (not advanced), the phone vibrates for about 7 seconds and then crashes TWRP.
Can anything be done to save the phone, or am I dead in the water here? At what point did I go wrong? My main device is a OP6T so I'm not too worried if this can't be resurrected, but I would like to try. I know this was a long post, but I wanted to be as detailed as possible. Thanks in advance for the help and thanks for reading.
You can restore it to stock through fastboot, I made a post with a mfastboot folder and it has a command prompt in the folder and you can launch that and should work if you have the xt1575, or try the custom recovery from the twrp website or the nuclearom post on here
LGAGaming said:
You can restore it to stock through fastboot, I made a post with a mfastboot folder and it has a command prompt in the folder and you can launch that and should work if you have the xt1575, or try the custom recovery from the twrp website or the nuclearom post on here
Click to expand...
Click to collapse
I did that after I wrote this post and I forgot to update that I did that. Thanks!
Side note: I'm new to the forums, where do I find the threads that I'm subscribed to? I've looked for a "subscribed" or "my subscriptions" link, but haven't had luck.
After failing with installing different versions of TWRP om my tablet (There is no working version on TWRP for my model- system revert itself to the Stock recovery mode), at some point I noticed, that I can power on tablet and get to Welcome screen and start tablet configuration, but right after 20th seconds system freezes for few seconds and reboots over and over. If I just power on system and let it stay without touching screen it will reboots after 20 second.
If I go to the Recovery mode, there is not reboots. I did system hard reset in Recovery mode no help.
I thought it is problem with ROM, and flashed Stock Rom with Lenovo MOTO Smart Assistant. Same issue with reboots, then I tried some other ROM’s regions with same issue. Before I got this issue, other ROM’s used to work just fine.
QUALCOMM flash utility did not help as well.
I am just interesting is this issue with System board or it is software issue and I can fix this.
I have the same issue. I have been able to root through a patched boot image, but cannot get recovery to flash no matter what. It says all went successfully, but then always reboots. I have the 2GB version.
I just want to install an updated ROM since lenovo abandoned our devices.
BlinkySneaky said:
I have the same issue. I have been able to root through a patched boot image, but cannot get recovery to flash no matter what. It says all went successfully, but then always reboots. I have the 2GB version.
I just want to install an updated ROM since lenovo abandoned our devices.
Click to expand...
Click to collapse
I've just spent days trying to get my TB-X704V to flash. I finally found out how. The issue I ran into is the recovery mode never worked. I found one that did. Big caveat here. Once I flashed the recovery image, I could no longer boot the stock rom.
I found the recovery image looking for X704A, and ended up with the files at https://drive.google.com/file/d/1QyUGBPi-KZrhSVFLOCs3lHUZ59fpe9KL/view (not my files). This is Chinese/English version. You can change language in the menu.
Follow the directions on flashing it at the quick boot menu and unplug and go into recovery mode.
Download the latest lineage OS: https://androidfilehost.com/?fid=6006931924117916469
Install the OS. The initial boot will take a few minutes, but it will boot.
Most of what I found was in the thread https://forum.xda-developers.com/thinkpad-tablet/general/twrp-root-tab-4-plus-tb-x704l-f-tb-t3664407
Thanks @yener90 for your work!
imrambi said:
I've just spent days trying to get my TB-X704V to flash. I finally found out how. The issue I ran into is the recovery mode never worked. I found one that did. Big caveat here. Once I flashed the recovery image, I could no longer boot the stock rom.
I found the recovery image looking for X704A.
Click to expand...
Click to collapse
Thank you so much, I was able to boot straight into TWRP using that Chinese/English image. I spent days last week unsuccessfully trying to boot my TB-X704V into the twrp-3.2.3-0-tb_x704l.img recovery image, but it never took no matter what I tried.
imrambi said:
I've just spent days trying to get my TB-X704V to flash. I finally found out how. The issue I ran into is the recovery mode never worked. I found one that did. Big caveat here. Once I flashed the recovery image, I could no longer boot the stock rom.
I found the recovery image looking for X704A, and ended up with the files at https://drive.google.com/file/d/1QyUGBPi-KZrhSVFLOCs3lHUZ59fpe9KL/view (not my files). This is Chinese/English version. You can change language in the menu.
Follow the directions on flashing it at the quick boot menu and unplug and go into recovery mode.
Download the latest lineage OS: https://androidfilehost.com/?fid=6006931924117916469
Install the OS. The initial boot will take a few minutes, but it will boot.
Most of what I found was in the thread https://forum.xda-developers.com/thinkpad-tablet/general/twrp-root-tab-4-plus-tb-x704l-f-tb-t3664407
Thanks @yener90 for your work!
Click to expand...
Click to collapse
Thank you for all your help mate. This is exactly what I needed. You two are gentlemen and scholars.