Hi there,
I got a working S7 Edge with cracked display (cannot see anything) but working touch. At the moment it is running Stock Firmware and no Custom Recovery.
I can control it via TeamViewer Host and Samsung SideSync.. With these tools I can control the device from PC..
Now is there any possible way to get at the same point again after flashing a custom ROM?
I think TWRP flashing with Odin should not be the problem, also flashing ROM via ADB Sideload..
But what about installing and configuring Remote Control of Device?
I'm hoping for some good ideas
Related
Hi all
Thanks for taking the time to read this.
I have access to a 2nd Jiayu s3 3GB on android 4.4.4
I've never been able to connect my Jiayu s3 3GB using SP Flash Tools (some driver issues?)
My Jiayu s3 was running android 4.4.4 and when ever it felt like it, it would freeze and then reboot.
So, like a bull in a china shop.....i factory reseted (included format storage option) which now doesn't allow the phone to boot..
The phone won't boot - it starts and just sticks on the Jiayu (white logo)
Thankfully...
if i start the phone with volume up i see
Recovery Mode
Fastboot Mode
Normal boot
I've just tried Recovery mode... and i remember i set my Recovery mode to be TWRP (4pda version)
..and thankfully i can now access the recovery module!
I can also access the phone via fast boot.
i can now access the phone via ADB also - via the recovery mode - i can launch the shell and query the phone
what i would like to do :
change all the partition tables to accept android 5.1.x
flash via adb all the sections needed to install 5.1
After you're all done laughing at me .. can i please have some help?
Cheers
AndyC76 said:
Hi all
Thanks for taking the time to read this.
I have access to a 2nd Jiayu s3 3GB on android 4.4.4
I've never been able to connect my Jiayu s3 3GB using SP Flash Tools (some driver issues?)
My Jiayu s3 was running android 4.4.4 and when ever it felt like it, it would freeze and then reboot.
So, like a bull in a china shop.....i factory reseted (included format storage option) which now doesn't allow the phone to boot..
The phone won't boot - it starts and just sticks on the Jiayu (white logo)
Thankfully...
if i start the phone with volume up i see
Recovery Mode
Fastboot Mode
Normal boot
I've just tried Recovery mode... and i remember i set my Recovery mode to be TWRP (4pda version)
..and thankfully i can now access the recovery module!
I can also access the phone via fast boot.
i can now access the phone via ADB also - via the recovery mode - i can launch the shell and query the phone
what i would like to do :
change all the partition tables to accept android 5.1.x
flash via adb all the sections needed to install 5.1
After you're all done laughing at me .. can i please have some help?
Cheers
Click to expand...
Click to collapse
Nothing to laugh here, hapens to all of us. Did you try to falsh a custom 4.4 rom through recovery. You can find them on needrom. Flash that and see what happens.
Regarding flashing 5.1.x you need to atleast once flash 5.1 rom through sp tools, without that its really hard to get 5.1 running on this phone due to changed partition layout from 4.4 to 5.1
Regarding the driver problem, every problem has a solution, try to google how to properly install mtk drivers on your pc, and its fairly very easy to install them. Cheers
adilrenzu said:
Nothing to laugh here, hapens to all of us. Did you try to falsh a custom 4.4 rom through recovery. You can find them on needrom. Flash that and see what happens.
Regarding flashing 5.1.x you need to atleast once flash 5.1 rom through sp tools, without that its really hard to get 5.1 running on this phone due to changed partition layout from 4.4 to 5.1
Regarding the driver problem, every problem has a solution, try to google how to properly install mtk drivers on your pc, and its fairly very easy to install them. Cheers
Click to expand...
Click to collapse
Hi
Some jiayu revisions need both Volume buttons to be pressed when connecting to PC
Install spflashtools
Install drivers
Download sptf Rom
Open flashtools
Press download ( choose upgrade mode if you are on KitKat and want to go to lollipop / future MM )
Turn off phone
Press and keep pressed both volume buttons
Connect cable pc-phone
Cheers
adilrenzu said:
Nothing to laugh here, hapens to all of us. Did you try to falsh a custom 4.4 rom through recovery. You can find them on needrom. Flash that and see what happens.
Regarding flashing 5.1.x you need to atleast once flash 5.1 rom through sp tools, without that its really hard to get 5.1 running on this phone due to changed partition layout from 4.4 to 5.1
Regarding the driver problem, every problem has a solution, try to google how to properly install mtk drivers on your pc, and its fairly very easy to install them. Cheers
Click to expand...
Click to collapse
Thank you so very much!
I've downloaded and installed the :
JIAYU S3 ADVANCED (3GB version)
XPOSED version
JY-S3_Basic_20150813-Xposed.zip
JY-S3_Advanced_PatchXposed_ For_20150813_Basic_Mod_By_Gab.zip
from needrom, so good to have the phone functional again!
Hello everyone,
I am posting today to bring up the subject of the SM-G360P variant of the Samsung Galaxy Core Prime.
I am having issues with getting TWRP custom recovery to work properly on my device. I am able to flash twrp-3.0.2-0-coreprimelte.img onto my device and it works except for 2 things that i have noticed that makes me very upset and i cant figure out what to do. When i enter recovery mode the back light does not function so i have to use a bright flashlight to see any of the options and the second problem is the GUI is upside down but the button mapping is in the proper place so i have to guess on where to tap on my screen. This makes it very frustrating to use especially when i want to wipe dalvik cache and the regular cache. I accidentally factory reset my device once by tapping the wrong spot. If anyone would be willing to help me out with my problem i am willing to be a guinea pig with anything you can try for the custom recovery to make the GUI reflect the proper button mapping and the back light to work. I can re-flash my device as many times as necessary to get a working custom recovery. I have included the recovery.fstab and the stock recovery along with the version of TWRP custom recovery i have been utilizing to an extent.
I am using the BST Australian variant of SM-G360P which can be rooted with Kingo Root and KingRoot. I used Kingo Root so i could use the SuperUser app rather than just using KingRoot. I have used CROM Service to unlock my bootloader. I have also tried to use CWM custom recovery on my device but it does not register the CWM custom recovery that is available for my device it just goes to a "fake" Odin mode screen. I would really love to get TWRP custom recovery working properly. I have tried to port both TWRP and CWM custom recoveries by using Android Image Kitchen but have not had any success at creating a recovery that works without the same issues i have with TWRP custom recovery. I am running 4.4.4 KitKat OS which is the latest update for SM-G360P and have full root permissions. If you need any other dump files or any other information i will gladly give it to you. I may need directions on how to do some things though.
I will be greatly appreciative if someone would have a look at what the problem may be with TWRP custom recovery and my Variant of SM-G360P. Please help. Thank you for your time and contribution.
Hello @sosthenisRR. I just got this device, the Boost Prevail LTE American version. I was wondering if you've made any headway finding a TWRP for it. I will be trying some things myself... Gotta have TWRP... And I wanted to let you know that if you root with kingroot, super-sume (free version) works to get you supersu.
Odin TWRP 2.8.7.0 for the SM-S820L...it works, i tried V3 as well with no favorable results.
https://forum.xda-developers.com/galaxy-core-prime/development/twrp-2-8-7-0-sm-g360p-t3462592
eeriikk said:
Odin TWRP 2.8.7.0 for the SM-S820L...it works, i tried V3 as well with no favorable results.
https://forum.xda-developers.com/galaxy-core-prime/development/twrp-2-8-7-0-sm-g360p-t3462592
Click to expand...
Click to collapse
If that doesn't work, install and run this apk, this is what finally allowed me to Odin TWRP to my G360P without errors. Now if only we could get a custom ROM for this variant...
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?
Hello dear Community!
It is depressing that my first appearance here is to ask for help, but I am going crazy.
So, I tried to Root my phone via Odin + CF Autoroot klte and it seemed to have been a success.
The root checker also said, that my device was rooted so I went on and installed TWRP to be able to install Lineage OS.
After getting Lineage to work I got a few error messages suddenly popping up, telling me that either "Music had stopped" or other android operation were closed because they didn't work properly.
I tried to install Gapps, it seemed to have worked but I was only able to open and enter the store once, afterwards the store never managed to load and then the app closed itself after starting it.
So I checked again with Root Checker, but this time it gave me an error message, too. It said, that my device was not rooted properly.
I guess this is were I made it worse by deciding to just root the phone again. Obviously, it didn't work either.
Afterwards I thought that maybe installing The Original Android OS and then unrooting the phone would be the best solution to be able to start anew.
First I tried to flah Lineage again and that made it impossible for me to boot the phone. The farthest I got was the setup page, were it tells you Hello and were you can choose a Language, but clicking the arrow key didn't do anything at all.
The recovery mode was also not the TWRP one anymore, but the original Android one and that was a huge problem for me.
Then I tried to flash the 6.1 OS for the S5 (I made sure it was the correct version), but now it is stuck at the "Samsung" screen while it boots.
It never boots though.
I don't know what to do anymore.
Please, I beg you, could anyone help me out?
Don't flash the latest Lineage OS ROM
Hello AsylumAlice u shouldn't have flashed the latest Lineage OS ROM because now u will need a new motherboard for your S5 since the ROM corrupts the MMC chip now u will need to get a new MMC chip or a new Motherboard sorry that your s5 is now hard bricked but when u get it fixed flash the DreamUX S8 Rom it works flawless on my S5 SM-G900i
Yours Sincely
Matty Bourke
mattybourke1994 said:
Hello AsylumAlice u shouldn't have flashed the latest Lineage OS ROM because now u will need a new motherboard for your S5 since the ROM corrupts the MMC chip now u will need to get a new MMC chip or a new Motherboard sorry that your s5 is now hard bricked but when u get it fixed flash the DreamUX S8 Rom it works flawless on my S5 SM-G900i
Yours Sincely
Matty Bourke
Click to expand...
Click to collapse
What are the grounds for your claims?
You needn't root via CF-autoroot if your end goal was to flash lineage. CF autoroot was intended to root stock roms with ease and less effort.
Flash The LATEST, official TWRP via odin then do a FULL WIPE. Wipe system, data, cache and dalvik cache.
From here on, you have two options:
1.) Sideload the LineageOS rom via ADB
2.) Transfer it to the phone's storage via MTP and flash it from TWRP.
As for how to accomplish this, the forum search bar and Google has your back. You need only choose one procedure.
If you need the Play Store, flash gapps AFTER flashing LINEAGE AND BEFORE REBOOTING.
Since you were under the idea that utilizing CF-autoroot was a necessity, I suggest that you re-read this post thoroughly before actually putting it into practice.
Kinloch said:
What are the grounds for your claims?
You needn't root via CF-autoroot if your end goal was to flash lineage. CF autoroot was intended to root stock roms with ease and less effort.
Flash The LATEST, official TWRP via odin then do a FULL WIPE. Wipe system, data, cache and dalvik cache.
From here on, you have two options:
1.) Sideload the LineageOS rom via ADB
2.) Transfer it to the phone's storage via MTP and flash it from TWRP.
As for how to accomplish this, the forum search bar and Google has your back. You need only choose one procedure.
If you need the Play Store, flash gapps AFTER flashing LINEAGE AND BEFORE REBOOTING.
Since you were under the idea that utilizing CF-autoroot was a necessity, I suggest that you re-read this post thoroughly before actually putting it into practice.
Click to expand...
Click to collapse
Thank you so much for your fast reply!
-> I flashed the newest Version for klte via Odin, but I can't get into the boot mode.
I only am able to enter the download mode. What can I do now?
Flash TWRP via odin again, untick the Auto-Reset option of Odin first. Then try booting to recovery via long holding the power, home and volume up button simultaneously without releasing any of the buttons until you successfully see the TWRP splash screen.
If that still doesn't work, reboot to recovery via adb from download mode. You need the adb and the usb drivers for your device.
If that still doesn't work, you might have flashed an incompatible version of TWRP.
Kinloch said:
Flash TWRP via odin again, untick the Auto-Reset option of Odin first. Then try booting to recovery via long holding the power, home and volume up button simultaneously without releasing any of the buttons until you successfully see the TWRP splash screen.
If that still doesn't work, reboot to recovery via adb from download mode. You need the adb and the usb drivers for your device.
If that still doesn't work, you might have flashed an incompatible version of TWRP.
Click to expand...
Click to collapse
Thank you so much, it worked perfectly!
I can now start my phone and use it normally.
But the Root Checker still says:
"Sorry! Root access is not properly installed on this device.
Device: SM-G900M
Android version: 7.1.2"
What should I do from now on?
Thank you so much for your help (agaiN).
And as for why I used the auto-root, well I just followed a guide that I found, it only had positive reviews so I assumed it was a correct tutorial.
AsylumAlice said:
Thank you so much, it worked perfectly!
I can now start my phone and use it normally.
But the Root Checker still says:
"Sorry! Root access is not properly installed on this device.
Device: SM-G900M
Android version: 7.1.2"
What should I do from now on?
Thank you so much for your help (agaiN).
And as for why I used the auto-root, well I just followed a guide that I found, it only had positive reviews so I assumed it was a correct tutorial.
Click to expand...
Click to collapse
just flash supersu in twrp
AronFerr said:
just flash supersu in twrp
Click to expand...
Click to collapse
I thought about doing that, but wasn't sure how exactly to proceed and what Version to install.
I downloaded SuperSU v.2.82 and put it on my internal storage.
Just install over TWRP the same way that I Installed Lineage and Gapps I suppose?
I guess if it doesn't work out, I just follow the steps from above again and retry?
Thank you so much. I feel like in idiot in this situation.
AsylumAlice said:
I thought about doing that, but wasn't sure how exactly to proceed and what Version to install.
I downloaded SuperSU v.2.82 and put it on my internal storage.
Just install over TWRP the same way that I Installed Lineage and Gapps I suppose?
I guess if it doesn't work out, I just follow the steps from above again and retry?
Thank you so much. I feel like in idiot in this situation.
Click to expand...
Click to collapse
yes just flash it but no wipes
Hi! My old phone broke and I'm trying to root another phone so I can flash a Verizon ROM to it so my SIM card will be compatible. I've tried my hand at one click root programs (which either don't support my phone or fail to fully root) and different tutorials (yet the TWRP screen never shows up when I enter Android Recovery). I have a SM-J700T1 running on Android version 7.1.1. Any advice, pointers, or guides would be greatly appreciated! Thank you!
To flash a Custom ROM on phone it's NOT required that phone's Android got rooted beforehand: All what's needed is phone's bootloader gets unlocked ( keyword: FASTBOOT ) and a working Custom Recovery like TWRP to flash the Custom ROM.