about: Samsung S5 G901F
I don't know what i am doing wrong, but I cannot install the xposed framework for Android 6.0.1
What I did so far:
1) installed a new stock rom
2) installed CF auto root, I have a confirmed SU.
3) in Recovery mode I try to install all Xposed framework zips from my SD card, but I always get an error message that the file check was not good.
Please give advice .
you can't install xposed framework on samsung devices on lollipop or marshmallow if its had a stock rom,if you try to..
the phone will get bootloop, if you want to install it,i suggest you install a custom rom,
it WILL NOT work on stock samsung devices.
After installing any custom rom,go here
You can install Xposed on stock Samsung roms. You just need the Touchwiz version.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
I succeeded installing CWM (Clockwork mod recovery).
In short what I did:
1a) Download kies 3 from samsung for the USB drivers to connect to your phone.
1b) Download Odin latest version, or older which comes with a specific software you want to install, usually latest works.
http://forum.xda-developers.com/showthread.php?t=2711451
1c) Shutdown phone completely. Press volume down + power button + home button at the same time, to enter ODIN download mode.
1d) connect phone by USB and you should see a blue light and COMX, where X can be any number like COM5, etc. If you see this then
the connection between ODIN and mobile is ok. Please don't touch the USB cable as you can easily loose connection. In worst case
you need to Flash any Android stock rom with ODIN again , which can be found at Sammobile for instance. I had to do this because
my phone lost connection and the flash operation failed. When I boot my phone I only saw ODIN screen. Thankfully you can always
flash stock rom back. In my case, I read something about a locked boot loader etc etc... that would be a bit more work....
Unpack until you see a MD5 file. In Odin you click "Phone" or "AP". The file will be checked, that takes about 10 seconds, after that you can press
"start". After flashing you should clear cache and user data, otherwise you will see the Samsung screen for endless time.
1) I have android 6.01 and the CF auto root works perfectly http://forum.xda-developers.com/showthread.php?t=1980683
Use Odin to flash, put file into phone or AP.
2) downlad CWM from http://forum.xda-developers.com/galaxy-s5/help/sm-g901f-to-s5-how-to-root-t2882104
Put the file, leave it zipped/packed, dont unpack it, put it into phone or AP again and start the ODIN flashing.
3) download Xposed framework, the right version. I am so far. I downloaded version SDK23, because that is the version for Android 6.0.X, but I got a message that it was for android 5.0 SDK 21, I am puzzled. Will try again.....
@es0tericcha0s, thank you will have a look at that.
Ah, i forgot I got sooo frustrated that I downgraded to 5.x to test the power consumption, if its better than 6.01, that I thought I still have 6.01 installed. But my stock rom is 5.x. downloading again, but now 5.x version ARM. Should work now.....
Edit: Flashed 6.01 android and Xposed ARM SDK23 installs fine...
Also installing Amplify, I read it about it that it works well with Greenify...
Amplify seems to be an impressive piece of software. Ir permits me to limit alarms and wakelocks! I can set the period of time it has to wait until it's alarm or is permitted to wake up. Wow....nice.
es0tericcha0s said:
You can install Xposed on stock Samsung roms. You just need the Touchwiz version.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Click to expand...
Click to collapse
ooh,thx for correcting me up
Related
This worked for me.
Took out battery for about 5 minutes, insert batt, Hold vol up + power to get into download mode. Use a $5 jig from ebay/amazon if you want to force download mode. This phone is almost impossible to brick. Only physical damage can brick.Since this is an old phone the issue for recovering from a soft brick is really non availability of required files.
When you have a soft brick like this ..ie., stuck in 3e recovery. Even if you odin back to stock you cannot get into recovery (stock or cwm). You are permanently hardware locked out of recovery. Once stock odin'd to eclair or froyo phone will boot up into that rom fine but you cannot get into recovery and you cannot root. At this stage odin Darky resurrection which is available in tar/pit format. It is a rooted kernel/rom combo. Since iam a new user forum did not allow me to paste any external links here. Google for "Install Darky ROM 10.2 Resurrection" and pick first link.
Now you have rooted kernel and nice rom but still no recovery. From market download some apk installer that works with darky. I just searched for apk installer and picked the first one. Just downloading rom manager may not work since rom manager does not support older versions like eclair/froyo anymore.... Google for "com.koushikdutta.rommanager.apk" and download this apk from some cyber graveyard..Install this apk, open installed rom manager and select reboot into recovery. Now finally i had working recovery and could flash any zip , wipe format etc.. Good luck.
tip: odin must be setup (select files, uncheck boxes..) before getting phone into download mode. Otherwise odin will get stuck. Just re-start all over if this happens.
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
William31 said:
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
Click to expand...
Click to collapse
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
mattnmag said:
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
Click to expand...
Click to collapse
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
William31 said:
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
Click to expand...
Click to collapse
Cool. Glad you got it fixed.
As you know, you can root with GhettoRoot from this thread: http://forum.xda-developers.com/showthread.php?p=57238246
Then can install Safestrap from this thread: http://forum.xda-developers.com/showthread.php?p=51616723
I've never used Safestrap because I can use regular custom recoveries like CWM and TWRP. I'm still on a 4.1.2 unlocked bootloader and currently running TrentsKKRom, Build #2...which is 4.4.2 based with stock kernel, so I think it would work with Safestrap.
I'd recommend reading through the Safestrap thread thoroughly and asking questions there to make sure you get everything installed correctly. I've read that with Safestrap, you need to make a backup of your Stock ROM first and save it somewhere safe, like to your computer and on your external sd card...so you can easily restore it if needed. (I'd also make a backup of the ESF in Safestrap if it lets you, then save it somewhere safe).
After you are rooted with Safestrap, you'll have to flash custom ROM's over the stock slot in Safestrap, as the other slots apparently don't work. Again, you're limited to only using Touchwiz ROM's with the stock kernel because of the bootloader still being locked.
Check out TrentsKKRom and Alliance build 30 . (I personally like Trent's build 2 best with the S5 clean theme). I've also found Trent's ROM to be really smooth without UI lagging, the Bluetooth works good with no stuttering, and it pairs well with my Sony Smartwatch 3. (Edit: If you do try Trent's ROM, you may need to install a couple apps.... Chainfire's Supersu app to control your root permissions (at least I needed to), and the FolderMount app to fix a KitKat internal storage mounting issue).
Have fun!!
I have a Sprint Galaxy Note 3.
As of yesterday it was functioning perfectly with a rooted stock Android 5.0 I tried to put a custom rom on it so I could use xposed and it has been borked ever since, I will list the steps I took and everything I've tried and their results below:
(I did full wipes in between each different flash)
1. Flashed TWRP with Odin (worked)
2. Flashed CyanogenMod with TWRP (worked)
3. Booted into CM to discover I could not get any data connection (could still make calls)
3. Booted to TWRP and flashed DarkLord rom (said there were errors [writing symlinks], caused boot loop)
4. Tried step 3 with Norma rom, CivZ rom, and a Stock Rooted rom (all same results of boot loop)
5. Booted to download mode and tried to flash samsung stock kitkat (just said failed)
6. Booted to download mode and tried to flash samsung stock lolipop (failed)
7. Booted back to TWRP and flashed CM again (this time not only no data, but no calls either)
Seems like maybe one of the issues may be the abundance of region codes and whatnot for all of these roms (including samsung official) and none of them seem to be for USA.
Does anyone have any suggestions or help to offer that I haven't already tried? I don't care what the rom is at this point, I just need a working phone that makes calls and has data as I'm out of town away from family and need to be in touch.
That said, obviously my preference would be to have a rooted KitKat rom so I can install xposed, or a rooted lolipop that isn't a samsung ART (for the same reason), but I'll genuinely be happy with anything that works.
I could be wrong, but is it maybe best to stick with CM simply because it's the only thing that will boot right now? If so how would I go about solving the non existence of a network connection.
I am also using Ting as a provider and they hop off Sprint networks. I had full bars of signal in this location the entire time when I was stock. Thanks in advance!
HunterNIU said:
I have a Sprint Galaxy Note 3.
As of yesterday it was functioning perfectly with a rooted stock Android 5.0 I tried to put a custom rom on it so I could use xposed and it has been borked ever since, I will list the steps I took and everything I've tried and their results below:
(I did full wipes in between each different flash)
1. Flashed TWRP with Odin (worked)
2. Flashed CyanogenMod with TWRP (worked)
3. Booted into CM to discover I could not get any data connection (could still make calls)
3. Booted to TWRP and flashed DarkLord rom (said there were errors, caused boot loop)
4. Tried step 3 with Norma rom, CivZ rom, and a Stock Rooted rom (all same results of boot loop)
5. Booted to download mode and tried to flash samsung stock kitkat (just said failed)
6. Booted to download mode and tried to flash samsung stock lolipop (failed)
7. Booted back to TWRP and flashed CM again (this time not only no data, but no calls either)
Seems like maybe one of the issues may be the abundance of region codes and whatnot for all of these roms (including samsung official) and none of them seem to be for USA.
Does anyone have any suggestions or help to offer that I haven't already tried? I don't care what the rom is at this point, I just need a working phone that makes calls and has data as I'm out of town away from family and need to be in touch.
That said, obviously my preference would be to have a rooted KitKat rom so I can install xposed, or a rooted lolipop that isn't a samsung ART (for the same reason), but I'll genuinely be happy with anything that works.
I could be wrong, but is it maybe best to stick with CM simply because it's the only thing that will boot right now? If so how would I go about solving the non existence of a network connection.
I am also using Ting as a provider and they hop off Sprint networks. I had full bars of signal in this location the entire time when I was stock. Thanks in advance!
Click to expand...
Click to collapse
1. Power off your phone completely
2. Boot into download mode (power + volume down button - then press volume up button to get into download)
3. Use Odin to flash this, which is the tar for OC5 - http://forum.xda-developers.com/note-3-sprint/development/romodin-t3095540
4. Reboot into STOCK recovery and factory default reset. If you skip this step, you will have issues
5. Once booted into OS, power off again and re-do step # 2 to get into download mode
6. Use Odin to flash TWRP
7. Once complete, immediately reboot into TWRP, or you will be dumped into stock recovery next time you try to get into recovery. I've done it this way since MJ4 and never had an issue.
8. Wipe everything including internal storage - NOT your external SD
9. Install ROM of your choice; I would recommend this one which is deodex and will allow you to install Xposed - http://forum.xda-developers.com/note-3-sprint/development/rom-t3132662
10. Profit
Good luck!
rpenrod23 said:
1. Power off your phone completely
2. Boot into download mode (power + volume down button - then press volume up button to get into download)
3. Use Odin to flash this, which is the tar for OC5 - http://forum.xda-developers.com/note-3-sprint/development/romodin-t3095540
4. Reboot into STOCK recovery and factory default reset. If you skip this step, you will have issues
5. Once booted into OS, power off again and re-do step # 2 to get into download mode
6. Use Odin to flash TWRP
7. Once complete, immediately reboot into TWRP, or you will be dumped into stock recovery next time you try to get into recovery. I've done it this way since MJ4 and never had an issue.
8. Wipe everything including internal storage - NOT your external SD
9. Install ROM of your choice; I would recommend this one which is deodex and will allow you to install Xposed - http://forum.xda-developers.com/note-3-sprint/development/rom-t3132662
10. Profit
Good luck!
Click to expand...
Click to collapse
Thank you so much for such a quick response! I'm downloading the file now and will be trying this as soon as it's completed. Also the rom you recommended was one I tried that failed, but hopefully with your extra steps it will work because it looks exactly like what I'm looking for.
UPDATE:
That worked fantastic @rpenrod23 thank you so much! Where is your donate button?
Hello XDA,
Unlike you, (probably) I am relatively new to rooting and flashing. I rooted my Samsung Galaxy Tab A 9.7 (SM-T550) and flashed TWRP recovery (thankfully). I have attempted to flash Xposed framework to my device and was horribly unsuccessful. My device entered a bootloop and I went into TWRP recovery and stupidly, somehow, wiped my device of its OS. Now TWRP says "No OS Installed! Are you sure you wish to reboot?" and puts me into another bootloop each time I do. My device is no longer recognized by Odin, Samsung Kies, but is somewhat recognized by my Mac Pro ( I also have windows in case it is necessary ). Thanks In advance for your help in making my device more than an ( very expensive!) brick.
Sincerely,
davidrazd
I'd start with just putting a rom zip on an SD card and flashing in TWRP. Just a heads up for later, you want to make sure you get Xposed for Touchwiz as it is different than the standard Xposed. Also, if you run into Xposed issues, there is a zip to flash that will just uninstall Xposed so you don't need to wipe anything.
If you do not have an SD card, then you should be able to push files via ADB in recovery from a computer, even a Mac.
As far as Odin or Kies not working, generally this is a driver issue. I would use Windows for Odin and look in the Device Manager to check the driver status.
As long as you have Download Mode and Recovery then your issues are minor and is just a matter of time before you fix it.
Could you send me a rom flashable via SD card by TWRP? Android 5.0.2 rom preferred but any will do, I really look forward to my device being more than just a brick.
Since there is not a forum here for your tablet, looks like you'll need to look over here: http://galaxy-tab-a.boards.net/thread/8/deodexed-rooted-debloated-deknoxed-xposed
Hello,
I come for you, because I am trying to install android 4.4 on my phone, because android 4.3 isn't compatible with pokemongo.
I have a galaxy s3 GT-I9300 from a few years, I've never rooted it and it runs on android 4.3.
I've been looking for guides that say that I need to install CWM recovery to then be able to install CyanogenMod.
So I've downloaded Odin, and CWM recovery, added the CWM recovery .tar in the AP box of Odin, put my phone on download mod, plugged it, and run Odin.
It appears that it works succesfully, but when I reboot my phone in recovery mode, I still have Android Recovery System <e3>, and I can't install zip from sdcards (if I understood correctly, <e3> doesn't support zip, whereas <e2> does, and CWM is supposed to put it to <e2>), so I can't install CyanogenMod.
Here is a screenshot of my Odin after running it: (I can't post the link since I'm a new user, so it's on imgur)
/87oPm2l
I can't think of any more information to provide for now.
Thanks for your help.
chocolote4444 said:
It could be permission issues. But try using a different cable.
Also, the recovery you are flashing has to support the model of the phone, otherwise, Odin will refuse to install it.
Click to expand...
Click to collapse
Thanks for the answer, I was not in root mode.
I fixed it and it now works, I have been able to install CyanogenMod from the zip in recovery.
Now I tried restarting my phone, and it's stuck in "Android is starting".
I have a little blue alien popping on my screen, then the screen turns off, then the screen turns on and says things like "starting applications, preparing settings, optimizing applications". But it seems to be doing it on repeat and it's been an hour. Is it normal that it takes so long? I haven't seen it mentionned anywhere from what I checked.