So ive been rooted since this phone came out like 2 years ago, but without recovery. Its my first android without twrp lol and it sucks bc if i ever bootloop i just have to factory reset. Thats the reason why i haven't been using xposed. When i try to install twrp in the rom flashing process its frustrating bc you cant get into recovery without a usb connected or some dumb issue. And its hard after the phone restarts, i cant get into recovery. Is there another way to install Twrp on N9860? Like this is the only phone like this, where you need a usb connected to enter recovery, they messed it up on a bootloader update i think. Anyway helping me is much appreciated. Also if i can get twrp on my phone, whats the best way to installing edxposed, or lsposed. Taichi is kind of a hassle
Related
As the title of this suggests, I messed up BIG TIME when attempting to get Cyanogenmod on my Verizon Galaxy S3.
Long story short, I tried putting CWM on my phone without looking up things about it, like whether or not the bootloader was locked for 4.4.2 Kitkat, which it was, and has been since 4.3 Jellybean, which I did not know at the time I tried screwing with my device (which was around a week ago), and I started trying to mess with the phone without knowing what the hell I was doing, since the last time I tried modding a GS3 was over two years ago.
Long story, well, long, I tried installing CWM via the ROM Manager app, and, upon installing it, I screwed up the recovery mode on the phone. It wasn't a big deal, until I decided I wanted to put the latest version of Cyanogenmod on it, instead of using the stock Touchwiz interface.
Well, a couple days ago, I stuck Safestrap on it, and was able to use that as a recovery mode, since the normal recovery mode was locked off, entirely.
I figured that, tonight, I would look up ways to stick Cyanogenmod on my GS3.
I found a couple ways to do so, downloaded the gapps file I needed, the SU binary update, as well as an unofficial version of Cyanogenmod to let me use 5.1 Lolipop.
Well, I wiped the cache on the phone, as well as the dalvik cache, and factory reset the thing, ad went to the folder I put the gapps, SU binary update, and CM files in, and tried installing them.
Well, the SU update went fine.
gapps won't install.
The CM file I'm using SAYS it's installed, but the phone doesn't have an OS, which is confusing me.
I don't know if the phone is bricked, I just know that I did something stupid, and I don't know how to put an operating system back on the phone, either through Kies or Odin (I can't install anything from the SD card in the phone, because now I can't access it, since when I boot it up, there's no OS, and I need one to access the files on the device).
Whenever I try using Odin to put either a stock firmware version on it, it fails.
My phone, in DL mode, says: "SECURE CHECK FAIL : RECOVERY"
I don't know what this means, but I think it means I'm pretty well screwed.
I need to get rid of CWM and Safestrap via my computer, THEN reinstall the stock recovery mode on my computer, too.
I NEED to know how to do this.
If there is ANYONE out there who can help me out, or direct me to some other thread, that would be amazing, and GREATLY appreciated.
Here's a basic rundown of what happened. I completely rooted my Galaxy S III i535 on 4.4.2, and i installed SafeStrap (A Version of TWRP) since the Verizon S3 has a locked bootloader.
So here's what I tried to do. Using SafeStrap, I backed up my stock rom. And i selected another ROM slot. Using this, i tried experimenting by installing a ROM for another Carrier (They say not to do this, but i have in the past with success, so i thought it mightve worked)
(KEEP IN MIND, THE STOCK OS WAS STILL INSTALLED AND I EVEN HAD A BACKUP)
So, it didnt work and stopped halfway. I rebooted the phone, and Hard bricked.
Doesnt boot up, does not turn on, will not boot recovery or download, or any sign of some boot at all.
And, i get the qhsusb_dload sign on my pc.
Can anyone point me in the right direction, or at least tell me the cause of this problem? Thanks.
CrimsonKatsuro said:
Here's a basic rundown of what happened. I completely rooted my Galaxy S III i535 on 4.4.2, and i installed SafeStrap (A Version of TWRP) since the Verizon S3 has a locked bootloader.
So here's what I tried to do. Using SafeStrap, I backed up my stock rom. And i selected another ROM slot. Using this, i tried experimenting by installing a ROM for another Carrier (They say not to do this, but i have in the past with success, so i thought it mightve worked)
(KEEP IN MIND, THE STOCK OS WAS STILL INSTALLED AND I EVEN HAD A BACKUP)
So, it didnt work and stopped halfway. I rebooted the phone, and Hard bricked.
Doesnt boot up, does not turn on, will not boot recovery or download, or any sign of some boot at all.
And, i get the qhsusb_dload sign on my pc.
Can anyone point me in the right direction, or at least tell me the cause of this problem? Thanks.
Click to expand...
Click to collapse
The solution may be a debrick image. They are designed to boot the phone from an external sdcard and from there reinstall the stock rom/firmware. I haven't searched yet, but check the general and development threads, possibly the stickied summary thread.
Check this thread
Hi folks,
just posting this writeup thinking maybe it might be of help to some people.
Started with a clean S6 Edge straight from Samsung repair for broken screen. Factory wipe, KNOX reset. It had the PD2 update. Tried using Skipsoft's Toolkit and ponied up a donation to get the Pro version with the S6 Edge 6.0.1 update, but it didn't work: it got stuck at the "SEANDROID NOT ENFORCING" screen after flashing TWRP 3.0.2. I know there are issues with 3.0.2, but it's what's optioned in Toolkit now.
Flashing TWRP 2.8.7.0 results in normal boot, but I could not enter recovery mode for some reason. 3.0.0-0 didn't work, either.
What I ended up doing is forcing phone into download mode (Power+Volume Down+Home), ODINing TWRP 3.0.2-1. This resulted in a bootloop (somewhat expected). But I could get into recovery easily. From recovery, I flashed Renegade's PD2-Aroma V3.0 Full ROM via ADB sideload. After a very long first boot, everything works 100%! Root, SuperSU, etc., all taken care of. Hotspot works.
Notes and tips:
- While I didn't use Skipsoft's Toolkit in the end, it's still worth supporting. Might work smoothly using 3.0.2-1 instead of 3.0.2.0, but I'm comfortable with adb/fastboot/etc. so just ended up using that. If you don't already have Android SDK and tools/platform-tools, Skipsoft conveniently includes those commands in its directory under C:\Unified_Android_Toolkit (they're named adb-toolkit and fastboot-toolkit. You can copy and rename them as "adb" and "fastboot" for convenience).
- Make sure you get the right TWRP 3.0.2-1 device version. You want to use twrp-3.0.2-1-zeroltespr.tar.md5 for Sprint S6 Edge. Remove the .md5 part and set it to use the .tar extension (stupid Windows asks you to confirm file extension type change).
- In TWRP you can either push your custom ROM or sideload it. To push a file, move the custom ROM into the same directory you've got adb/fastboot for convenience. Open a terminal window in that directory, and either "adb push customromfilenamehere.zip /sdcard/" or in TWRP, click Advanced/ADB Sideload, and enter "adb sideload customromfilenamehere.zip".
- If you're sideloading it, it's gonna take a while, and will start flashing even while the transfer percentage is creeping up. Example: at around 9%, it started AROMA, around 14%, it went through some of the installation options. It was done flashing everything and ready for reboot even though the terminal window said only 76% was transferred. That's ok. Click "finish" in AROMA on phone, reboot. Unplug phone. Wait a long time for first boot (this took around 20 minutes for me). ENJOY.
Remember: all is not lost as long as you can get into download mode! Power-Volume Down-Home until you get to screen prompting to get to download mode. Volume up to select that mode. You can ODIN from here.
Additionally: if you find yourself for whatever reason stuck at the initial S6 Edge boot screen with "SEANDROID NOT ENFORCING," you might be in some kinda of boot limbo. I was able to issue some adb commands here, even with recovery was borked and the phone didn't boot all the way. Doing an "adb reboot-bootloader" would let me do a complete boot to ROM while I was trying to get the different TWRP versions working (until 3.0.2-1).
Hope this helps someone.
tl;dr: For PD2/6.0.1 Sprint S6 Edge, manual flash TWRP 3.0.2-1. Push custom ROM through Recovery. Reboot, wait a long time. Success!
Just to Clarify (and mostly for myself), I think this is the simplest and most foolproof way to get yourself fully update and on a custom rom with root.
1. ODIN Stock PD2 Image. Reboot, make sure dev options + USB debugging is enabled.
2. ODIN latest TWRP 3.0.2.1 - HERE.
3. Obtain root by going into TWRP immediately after you install it and flashing the root kernel Ram did for this device - HERE
4. Then after wiping cache, dalvik and data in TWRP, flash Renegade ROM 3.0 PD2.
Using CFauto root method is known to cause issues. This is the type of approach I took and it was flawless. The initial boot of the Renegade ROM can seriously take like 20min though, I thought I was looping for a second.
If anyone disagrees with this method or sees where it can be done better, please advise. This seems to prevent the instance of any loops or issues. The Renegade ROM has a rooted kernel so flashing the root kernel is likely a redundant step. You could omit Step 3 if you are flashing a custom ROM, probably, but it seems to prevent any hangups. But if you plan to stay stock, you still have to flash a rooted kernel after TWRP.
Alpine- said:
Just to Clarify (and mostly for myself), I think this is the simplest and most foolproof way to get yourself fully update and on a custom rom with root.
1. ODIN Stock PD2 Image. Reboot, make sure dev options + USB debugging is enabled.
2. ODIN Ram's TWRP 3.0.2 - HERE I'm assuming the other guy's 3.0.2 works fine too, I am not sure why you hung and had to revert to a 2.x TWRP build.
3. Obtain root by going into TWRP immediately after you install it and flashing the root kernel Ram did for this device - HERE
4. Then after wiping cache, dalvik and data in TWRP, flash Renegade ROM 3.0 PD2.
Using CFauto root method is known to cause issues. This is the type of approach I took and it was flawless. The initial boot of the Renegade ROM can seriously take like 20min though, I thought I was looping for a second.
If anyone disagrees with this method or sees where it can be done better, please advise. This seems to prevent the instance of any loops or issues. The Renegade ROM has a rooted kernel so flashing the root kernel is likely a redundant step. You could omit Step 3 if you are flashing a custom ROM, probably, but it seems to prevent any hangups. But if you plan to stay stock, you still have to flash a rooted kernel after TWRP.
Click to expand...
Click to collapse
I noticed chainfire now has a CF-autoroot for the 925P 6.01 and people were having success using the one for the 925F. Any verification on this? Haven't seen anyone on this forum say anything about it. I just bought a new S6 edge for sprint. I always am about year behind on phones because of the high cost of the latest and greatest. I picked the edge because my wife has had one a year and it gets a lot better reception than my N5. But, I gots to have root and don't wanna screw up a new phone. I know the first thing I need to do is check which software it's running. Should I do this before I activate it or can i stop any system upgrades before they install?
baknblack said:
I noticed chainfire now has a CF-autoroot for the 925P 6.01 and people were having success using the one for the 925F. Any verification on this? Haven't seen anyone on this forum say anything about it. I just bought a new S6 edge for sprint. I always am about year behind on phones because of the high cost of the latest and greatest. I picked the edge because my wife has had one a year and it gets a lot better reception than my N5. But, I gots to have root and don't wanna screw up a new phone. I know the first thing I need to do is check which software it's running. Should I do this before I activate it or can i stop any system upgrades before they install?
Click to expand...
Click to collapse
I have not attempted to use CF-autoroot just because of reported issues and the general recommendation being to use the standard method. It may work fine now that its been updated, but I have not personally tested it.
Alpine- said:
I have not attempted to use CF-autoroot just because of reported issues and the general recommendation being to use the standard method. It may work fine now that its been updated, but I have not personally tested it.
Click to expand...
Click to collapse
I just bought my phone new off ebay it updated to PF4 just as soon as I activated it. I couldn't stop it. Anyway I used the CF autoroot on it and it worked perfectly. I tried to do it manually a couple times first and never could get TWRP to flash. It would say it was successful but, stock recovery stayed. Anyways, I got er done and running Renegade wich btw is an awesome ROM. This is my first samsung device and had I done a bit more research I'd of known the majority of development is on the regular S6. I just picked the edge because my wife has one and it worked so much better in the boonies than my N5 did.
baknblack said:
I just bought my phone new off ebay it updated to PF4 just as soon as I activated it. I couldn't stop it. Anyway I used the CF autoroot on it and it worked perfectly. I tried to do it manually a couple times first and never could get TWRP to flash. It would say it was successful but, stock recovery stayed. Anyways, I got er done and running Renegade wich btw is an awesome ROM. This is my first samsung device and had I done a bit more research I'd of known the majority of development is on the regular S6. I just picked the edge because my wife has one and it worked so much better in the boonies than my N5 did.
Click to expand...
Click to collapse
Edge is better imo, certainly looks better. All you need is Renegade rom anyway. May be a few more roms in active dev for s6 but nothing better per se. Renegade rom dev is alive and well.
Would these root methods trip knox?
chen69chuck said:
Would these root methods trip knox?
Click to expand...
Click to collapse
Yes
Thanks.
Working for g920v 6.0.1?
freaking thank you been struggling with twrp on and off for two days trying to bring this phone back from the dead! YOU the man
I have an HTC One M9 (Sprint) software version 2.11.651.19 (OPJA2) with Android v5.1
Within the last couple months I unlocked the devices bootloader, and rooted it. Last night I left the phone under my laptop and I'm thinking it got way way way too hot, somehow the thing is still alive, however when I went to turn it on in the morning, I had no wifi or cellular capabilities. At first I assumed this was a hardware issue, however I then unrooted the device on a whim, and this fixed it (Until I turned it off again, to my dismay).
I'm thinking somehow my phone overheated (Which explains why my battery life won't go over 47%) and somehow my flash memory must have been corrupted because I can no longer boot into recovery mode, which is my serious catch 22. Since I figure this is some issue related to my firmware, which I would LIKE to reflash (This is my goal here). To my dismay, in order to flash a stock RUU or firmware to the device, you must have your bootloader relocked. However in order to relock your bootloader you must have root, and like an idiot I unrooted it. I can't reinstall SuperSU through my TWRP recovery because my phone refuses to boot into recovery mode. I attempted to re-flash TWRP to the device through download mode, the flashing is completed successfully, however I still cannot boot into my recovery. To break it down simply:
-Want to reflash stock firmware
-Must have root to reflash stock firmware/RUU
-Don't have root because I uninstalled it
-Can't re-root because my recovery is corrupted
-Can't re-flash TWRP (Already tried and it's not working)
-Can't re-root because I can't flash TWRP
-Can't reflash stock firmware because I can't disable it with root
Regardless of this I attempted to use adb and echo to relock the bootloader however instead of getting # I get $, so I'm not really able to do this either. Is there ANY way I can repair my recovery, has anyone ever run into an issue like this before? Or am I just completely screwed, hahaha.
Do you think I might be able to reflash Android V5.1 to try and fix the corruption and then maybe that would allow me to get into recovery mode so I can flash Super SU so I can at least factory reset my device with TWRP, or possible reload stock firmware and factory reset from there?
Thanks guys for any help you can provide.
*EDIT
If anyone wants to provide any advice great, but for now I'm going to try using HTC Sync Manager to load Marshmallow (v6.0) onto the HTC and see if this may allow me to actually get into recovery mode. Downloading the file from here: *nevermind can't post links yet, under 10 posts, you can find it on HTC's website* (This is for the HTC One M9, Sprint) in case anyone else EVER has to run into this awful issue, lol.
Moderators please feel free to update the thread to SOLVED status, I was able to update my phone to marshmallow to resolve the issue. This time around I WILL be backing up my phone, probably not going to root it this time around either, I have like 3 other phones so I'll just root them instead, lol. If you would like the download link I am happy to provide it VIA PM so you can update my OP with the link for the full fix. My phone is able to get wifi and texts now without an issue, unfortunately all my data is wiped but honestly I don't really care!!
Thanks everyone!
Good job on solving your issue.
If you have further questions or want to help out others, you can do so here
http://forum.xda-developers.com/sprint-one-m9/help
http://forum.xda-developers.com/sprint-one-m9
Thread closed
I have asked on a few threads including the TWRP thread but no one seems to be answering for some reason so I thought I'd risk putting up a separate post to try and get an answer.
I followed the instructions to the letter on how to install TWRP from the thread and it installed all ok, the only problem is that the screen is totally frozen and there is nothing I can do to get it to work. I have now gone back to Oreo via Odin until I can get help on what's gone wrong. Would it make a difference if I tried from Nougut 7.0?
I have rooted and installed roms, TWRP's pretty often last year with my M10, M8 etc so I'm not that new to this but it's got me foxed this time.
Good question. I had an issue after installing CarHDROM, v9 for a bit where I could get into TWRP, but the phone would boot loop getting out of TWRP and I had a hard time getting back into recovery or download mode.
I re-flashed the phone and TWRP as well, and after that all was well. I did not change anything on the re-flash.
Sometimes things just get mux'ed.