I have been getting this phone up to date with out any computer at all ant have just been doing the ota updates so I can then root wit towelroot and the world I need opens from there
Look mm y phone downloads 4.3 goes to install restarts ans simply says install failed ummmmm.... what this is about I have no clue a little guidance would be great ppoint blank I will never have the option for computer for a long ass time
cmjester6421 said:
I have been getting this phone up to date with out any computer at all ant have just been doing the ota updates so I can then root wit towelroot and the world I need opens from there
Look mm y phone downloads 4.3 goes to install restarts ans simply says install failed ummmmm.... what this is about I have no clue a little guidance would be great ppoint blank I will never have the option for computer for a long ass time
Click to expand...
Click to collapse
Try using FlashFire, it's basically Odin for your phone. I think you have to join the Google+ Community to download it, but it works great.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Without root or anything that will work.... I kinda feel like that may not be the case another thing at one point a long time ago I changed my modstrings would that impede on the install with ota
Edit: ya flash fire won't work need root
Edit2: nvm the modsring is stock so I'm still at a total stop here
cmjester6421 said:
Without root or anything that will work.... I kinda feel like that may not be the case another thing at one point a long time ago I changed my modstrings would that impede on the install with ota
Edit: ya flash fire won't work need root
Edit2: nvm the modsring is stock so I'm still at a total stop here
Click to expand...
Click to collapse
Modstrings? What are you talking about?
cmjester6421 said:
I have been getting this phone up to date with out any computer at all ant have just been doing the ota updates so I can then root wit towelroot and the world I need opens from there
Look mm y phone downloads 4.3 goes to install restarts ans simply says install failed ummmmm.... what this is about I have no clue a little guidance would be great ppoint blank I will never have the option for computer for a long ass time
Click to expand...
Click to collapse
Once you update to the latest firmware, towelroot will not work. The exploit towelroot uses has been patched. And no one knows what you mean by "modstrings"
Well it don't work now anyway and forget the modstrings part I just need a way at this point to root and I cab roll with what I need to do worst case I have to go buy a new computer but I would rather not
cmjester6421 said:
I have been getting this phone up to date with out any computer at all ant have just been doing the ota updates so I can then root wit towelroot and the world I need opens from there
Look mm y phone downloads 4.3 goes to install restarts ans simply says install failed ummmmm.... what this is about I have no clue a little guidance would be great ppoint blank I will never have the option for computer for a long ass time
Click to expand...
Click to collapse
bilgerryan said:
Modstrings? What are you talking about?
Click to expand...
Click to collapse
madbat99 said:
Once you update to the latest firmware, towelroot will not work. The exploit towelroot uses has been patched. And no one knows what you mean by "modstrings"
Click to expand...
Click to collapse
This will help everyone understand what he means by modstrings...
https://towelroot.com/modstrings.html
This would make a great t-shirt!..."Modstrings? What are you talking about?"
Yes he is right the latest update patches the towelroot exploit. But you can still use another method without computer. But basically if you want your whole world to open up then you will not need that update. For example im running 5.1 lollipop on my gs3 so that ota update is not helping me at all. Rooting your stock rom opens a couple door in an old phone. But installing a custom rom, kernel, mod, framework, etc. will open every door. My gs3 outperforms my sisters gs6 in many ways and i had 5.1 update before she did. Amd i can always put my phone back to stock rom, unroot, and make it under warranty terms again because i made backup. But if you want slight upgrade i can help you troubleshoot the ota installation. But if not its ok because my wife has same phone and didnt update and she is running same custom rom, kernel, mod, framework, etc that i am with no problems.
Check out this thread i started last night as its related and has more info...
http://forum.xda-developers.com/galaxy-s3-sprint/help/samsung-galaxy-s3-lollipop-5-1-custom-t3162496
Let me know what u decide to do
I'm doing full mods to this phone I had a s6 I really don't like it look as I said I don't have a computer I need the fastest path to getting cwm once I have the rom I want I can go fron there howevrr the fine tuning help would be a big plus from you if I evrr get this done lol the plan is to get cm 12.1 and go as far as I can to make this bettrr then the s6 please let me jnow where I need to go fron here
cmjester6421 said:
I'm doing full mods to this phone I had a s6 I really don't like it look as I said I don't have a computer I need the fastest path to getting cwm once I have the rom I want I can go fron there howevrr the fine tuning help would be a big plus from you if I evrr get this done lol the plan is to get cm 12.1 and go as far as I can to make this bettrr then the s6 please let me jnow where I need to go fron here
Click to expand...
Click to collapse
Fastest path to cwm is rooting your phone using towelroot or cf autoroot then install root checker app to verify root and then install app supersu and then install app called rommanager from app store and update the recovery in the app. Should only take a few minutes plus reboot time. No computer needed. Forget about the ota upgrade for now since you want cm12.1. Once cwm running do a nandroid backup so you have a stock rom image before doing anything else. Later you can revert back to the moment after you rooted if you run into any problems and try again, try ota update again, or unroot and get it back to warrantied state. Before updating to custom rom check out my new thread to get some ideas on what to back up to save your important data and other ideas. Yes i can help you furthur just message me anytime or ask in my thread..
http://forum.xda-developers.com/galaxy-s3-sprint/help/samsung-galaxy-s3-lollipop-5-1-custom-t3162496
Cf needs a computer right? And as for towel root I have ran it many times it says it worjed but su won't install....
cmjester6421 said:
Cf needs a computer right? And as for towel root I have ran it many times it says it worjed but su won't install....
Click to expand...
Click to collapse
My fault. I meant framaroot. Try this i think this is what i had to use from xda..
http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
The towelroot saying success is throwing me off. I will try to find out info on that. Did you use root checker app to verify root or no root? My first root i thought nothing happened at first. Let me know
Error 7 first exploit and error 9 secong exploit.... as for towel root years ago I paid for root checker advanced I know better its not rooted I have done factory resets and tried again I'm running 4.1.2 this is stock from a ota a long time ago I know you have no reason to hekp but if you can get me in the right place to make this work you save me a grand plus if I'm getting a new pc its asus gaming level what I had was 6k I won't take much less please let me know what you find I have been reserching for the last six hours.... no luck
Thanks to zip addict he found me king root and I looked in to it the 4.5 version I git root no pc all is needed after that is super sume from what he told me so that you can install the right super user and move on to a recovery now at this time I'm trying to find a dl for super sume that is not the play store as it says not compatible
Related
There seems to be an OTA update, and it's 10h.
Still ICS but comes with some bug fixes.
Anyone get their updates yet?
gbssengo said:
There seems to be an OTA update, and it's 10h.
Still ICS but comes with some bug fixes.
Anyone get their updates yet?
Click to expand...
Click to collapse
Bell/rogers/telus?
E971, E970, E973?
Unlocked with freegee?
did you update?
edit: im on rogers e971 and i also disabled/froze the LG update software
Nothing for Telus's E973...
Nothing here....Sastel E973
Have a Rogers E971, woke up to a software update.
Tried to update and was told that I could not due to root, removed root via SuperSU. Ran update again, update seemed to run but then rebooted and got a security error, Boot Certificate (I had unlocked boot loader via FreeGee, couldn't restore the FreeGee backup so decided to give it a go and see what happened).
Anyways, managed to recover via the "How to unbrick your optimus G" thread (http://forum.xda-developers.com/showthread.php?t=2010624), the software update now appears to be applied (at least it's no longer detecting an update but I'm not sure what version the update changed it to so I'm not sure how to check).
Obviously my bootloader is no longer unlocked and my device is no longer rooted. Tried to root again with the same method as before (Korean Batch File) and it no longer works. The device gets to the first reboot and then when it comes back up the cmd window says something about "access denied, is your device rooted?" and "Press any key to continue", at which point it exits.
Just my experience.
jpom18 said:
Have a Rogers E971, woke up to a software update.
Tried to update and was told that I could not due to root, removed root via SuperSU. Ran update again, update seemed to run but then rebooted and got a security error, Boot Certificate (I had unlocked boot loader via FreeGee, couldn't restore the FreeGee backup so decided to give it a go and see what happened).
Anyways, managed to recover via the "How to unbrick your optimus G" thread (http://forum.xda-developers.com/showthread.php?t=2010624), the software update now appears to be applied (at least it's no longer detecting an update but I'm not sure what version the update changed it to so I'm not sure how to check).
Obviously my bootloader is no longer unlocked and my device is no longer rooted. Tried to root again with the same method as before (Korean Batch File) and it no longer works. The device gets to the first reboot and then when it comes back up the cmd window says something about "access denied, is your device rooted?" and "Press any key to continue", at which point it exits.
Just my experience.
Click to expand...
Click to collapse
thanks for the heads-up man
in my opinion:
nope nope nope
also maybe try the latest version of Bin4ry's
http://forum.xda-developers.com/showthread.php?t=1886460
might help
---------- Post added at 11:06 AM ---------- Previous post was at 10:58 AM ----------
http://mobilesyrup.com/2012/12/18/s...rings-stability-and-performance-improvements/
seems this is the update they are talking about
for bell and rogers atm
jpom18 said:
Have a Rogers E971, woke up to a software update.
Tried to update and was told that I could not due to root, removed root via SuperSU. Ran update again, update seemed to run but then rebooted and got a security error, Boot Certificate (I had unlocked boot loader via FreeGee, couldn't restore the FreeGee backup so decided to give it a go and see what happened).
Anyways, managed to recover via the "How to unbrick your optimus G" thread (http://forum.xda-developers.com/showthread.php?t=2010624), the software update now appears to be applied (at least it's no longer detecting an update but I'm not sure what version the update changed it to so I'm not sure how to check).
Obviously my bootloader is no longer unlocked and my device is no longer rooted. Tried to root again with the same method as before (Korean Batch File) and it no longer works. The device gets to the first reboot and then when it comes back up the cmd window says something about "access denied, is your device rooted?" and "Press any key to continue", at which point it exits.
Just my experience.
Click to expand...
Click to collapse
Can you take a couple of pictures with ISO @ Auto to see if they fixed it?
Thanks!
t1mman said:
Can you take a couple of pictures with ISO @ Auto to see if they fixed it?
Thanks!
Click to expand...
Click to collapse
I can do that, is there anything specific that I should be looking for or that you would like to see? I almost never take pictures and have never used the camera on here, I didn't even know that there was an issue.
t1mman said:
Can you take a couple of pictures with ISO @ Auto to see if they fixed it?
Thanks!
Click to expand...
Click to collapse
any work around if we dont want to update yet
I got fed up for I cannot restore the KDZ (Not responding stuff). I tried the hard mode method of using LG's support tool and it downloads a whole ROM! Will keep you posted.
EDIT: Yes you cannot root ATM.
BloodBaron said:
any work around if we dont want to update yet
Click to expand...
Click to collapse
I used Titanium Backup pro to freeze the Software Update app. Seems to take away the notification and no problems thus far.
If you don't have TBpro, you can just slip into the app info in the settings menu and disable it from there. (Settings > Apps > List All, find Software Update, disable.
Freezing is the same as disabling as far as I can tell.
yes and you cannot root atm....LOL!
So its safe to say disable the lg update software?
Sent from my LG-E971 using xda premium
BloodBaron said:
So its safe to say disable the lg update software?
Sent from my LG-E971 using xda premium
Click to expand...
Click to collapse
yes just "Disable" via Settings > Apps > Software Update > Tap Disable.
Not Freeze via any root apps.
So I am gonna suffer from being unrooted ATM but no biggy. Good thing LG (and most manufacturers) has a stock app back-up tool in place of TB.
Absolutely nothing for TELUS OGs.. -_-
For those that are wondering what is in the update (for Bell at least):
Code:
Short description
A software update is now available for the LG Optimus G, and Bell strongly recommends that customers update their device to ensure the best possible experience.
Dates
Start date: Tuesday, December 18, 2012
Description
Software update version [V10h] includes device improvements to stability and performance including:
•Google security patch
•Improved touch response while charging
•Fixed exchange email setup to avoid customer confusion
Procedure
Has anyone successfully backed up su by copying it to various directories before updating?
I've put a copy in /system/etc, /system/bin, /data, /data/data, & /cache. I'm hoping one of those will still be there after the update.
Problem for me right now is no update is showing up when I check.
Anyone wanting to try doing this backup make sure you copy the su binary with the - p flag to keep setuid/setgid. I'd also recommend renaming the backup to something other than 'su'.
xxbeanxx said:
Has anyone successfully backed up su by copying it to various directories before updating?
I've put a copy in /system/etc, /system/bin, /data, /data/data, & /cache. I'm hoping one of those will still be there after the update.
Problem for me right now is no update is showing up when I check.
Anyone wanting to try doing this backup make sure you copy the su binary with the - p flag to keep setuid/setgid. I'd also recommend renaming the backup to something other than 'su'.
Click to expand...
Click to collapse
IMHO, the software update wipes /system and /cache (not /data in my experience) so everything you put in those directories will be wiped out. Those SU files though are in the zip if you used Bin4ry's rooting tool, and you can download it from androidsu.com (just unzip these files and you should be able to see them).
jpom18 said:
I can do that, is there anything specific that I should be looking for or that you would like to see? I almost never take pictures and have never used the camera on here, I didn't even know that there was an issue.
Click to expand...
Click to collapse
Something collorfull with not much lights, to see if it gets a grainy feel like this (with AutoISO)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
or colourfull clean image like this (with Manual Iso)
Thanks!
gabby131 said:
IMHO, the software update wipes /system and /cache (not /data in my experience) so everything you put in those directories will be wiped out. Those SU files though are in the zip if you used Bin4ry's rooting tool, and you can download it from androidsu.com (just unzip these files and you should be able to see them).
Click to expand...
Click to collapse
The problem is that some people are reporting that Bin4ry's recovery exploit is no longer working after the update.
I cannot root it, I cannot install any recovery besides the stock one that comes with it, I cannot get it to connect to the computer as mass storage, only as a media device.
Im thinking I just blew $215 on a paperweight.
I CANNOT EVEN INSTALL TITANIUM BACKUP TO GET RID OF THE FREAKING ATT CRAP!
What have I did wrong?
I have CWM v5.5.0.3!
Ive tried countless number of rooting programs including some poplular ones:
1. Casual - http://forum.xda-developers.com/showthread.php?t=2189536
2. Kingo Android ROOT - http://www.kingoapp.com/android-root.htm
3. Towelroot - https://towelroot.com/
4. CF Root (Flashed SU but does not work) - http://download.chainfire.eu/269/CF-Root/CF-Auto-Root/CF-Auto-Root-d2can-d2vl-sghi747m.zip
CF Root flashed Superuser but it says unfortunately Superuser has stopped.
Im about to take this back to the store I got it from....
Tell us your phone's specifics (firmware, modem, bootloader, is it AT&T or some other carrier). Does the phone work OK otherwise?
Do you have a ROM you want to try?
How are you flashing the recovery? Do you have Knox on your phone?
Model Number: Samsung-SGH-I747
OKAstro said:
Tell us your phone's specifics (firmware, modem, bootloader, is it AT&T or some other carrier). Does the phone work OK otherwise?
Do you have a ROM you want to try?
Click to expand...
Click to collapse
Its an [email protected] Phone with a new [email protected] sim card in it. The phone works on stock stuff. It will boot up just fine with CWM installed but I cannot actually go into CWM. It just gives me a black screen.
Android Version: 4.4.2
Baseband Version: I747UCUFNE4
Kernel Version
3.4.0-1514807
[email protected] #1
Mon May 19 21:00:05 KST 2014
Build number: KOT49H.I747UCUFNE4
SE for Android Status:
Enforcing
SEPF_SAMSUNG-SGH-I747_4.4.2_0016
Mon May 19 20:59:50 2014
It doesn't matter if I got a ROM or not. I cannot install a custom recovery.
audit13 said:
How are you flashing the recovery? Do you have Knox on your phone?
Click to expand...
Click to collapse
I am flashing Recovery thru Odin. Ive even tried different versions of Odin from 1.7 to 3.09. I prefer to use Odin 1.85.
And I have no clue what knox is or even if its installed.
Have you tried this thread?
http://forum.xda-developers.com/showthread.php?t=2789917
OKAstro said:
Have you tried this thread?
http://forum.xda-developers.com/showthread.php?t=2789917
Click to expand...
Click to collapse
Im not able to flash a working custom recovery.
mrnapolean1 said:
Im not able to flash a working custom recovery.
Click to expand...
Click to collapse
Well - maybe try flashing the stock 4.42 ROM again through Odin and then if that sticks, try the steps in the thread I linked
Good luck
OKAstro said:
Well - maybe try flashing the stock 4.42 ROM again through Odin and then if that sticks, try the steps in the thread I linked
Good luck
Click to expand...
Click to collapse
I had booted into download mode being about to flash CWM to my phone via Odin (Again) and I noticed this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(If you cannot see it it says):
Factory Mode
Product Name: SGH-I727
Current Binary: Custom
System Status: Custom
Qualcomm Secureboot: Enable
Warranty Bit 1
Bootloader AP Swrev: 3
Is this bad?
Am I still able to root?
Am I able to install custom Recovery?
Am I able to install ROMS like CM 11?
mrnapolean1 said:
I had booted into download mode being about to flash CWM to my phone via Odin (Again) and I noticed this:
(If you cannot see it it says):
Factory Mode
Product Name: SGH-I727
Current Binary: Custom
System Status: Custom
Qualcomm Secureboot: Enable
Warranty Bit 1
Bootloader AP Swrev: 3
Is this bad?
Am I still able to root?
Am I able to install custom Recovery?
Am I able to install ROMS like CM 11?
Click to expand...
Click to collapse
The fact that you can get to download mode is good. But sorry, what this means is out of my league. Try PM'ing "DocHoliday77". He seems to be a great resource for all things SGS3. He's in numerous threads in the Development forum
EDIT: I booted into download and mine says the exact same thing
You have Knox on your phone. You tripped the knox counter and changed the warranty bit to 1 which means the warranty on your phone has been voided.
When flashing a custom recovery phone in Odin, do not check auto reboot. When you see the word reset appear in the status window, remove the usb cable, pull the battery, and use the button combo to boot inter recovery.
audit13 said:
You have Knox on your phone. You tripped the knox counter and changed the warranty bit to 1 which means the warranty on your phone has been voided.
When flashing a custom recovery phone in Odin, do not check auto reboot. When you see the word reset appear in the status window, remove the usb cable, pull the battery, and use the button combo to boot inter recovery.
Click to expand...
Click to collapse
No still nothing.
It vibrates when you first start it up and then the Samsung logo comes up with Recovery is starting in blue at the top for about a second and then goes to a black screen and nothing never happens afterwards.
What is Knox by the way? Is this keeping my phone from being rooted?
Figured id post here now rather than having two threads going for the same problem.
The more this goes on though, the more i am suspecting some sort of hardware problem.
I want to suggest using the PIT file to repartition the device, but theres no firmware to use along side it. Theres a program here on xda called PIT Magic i think. I dont know much about it, but maybe it could help you to somehow repartition....?
As for knox, there is tons of info out there on it already,so i wont get into it here. It wont block you from rooting, but it can deny root access when an app requests it.
Will the pit wipe it?
Will installing cm 11 using the installer work? Does it work?
Yes, repartitioning will wipe your data.
I dont use CM roms so im not familiar with the installer. Sorry.
DocHoliday77 said:
Yes, repartitioning will wipe your data.
I dont use CM roms so im not familiar with the installer. Sorry.
Click to expand...
Click to collapse
My main thing is I want to root my unrootable SGS3 so I can remove the ATT crap.
Im out of ideas for you...sorry. I kinda think its probably a hardware issue. It sounds like youve done everything you can to get root or recovery. Might be wise to start looking into a motherboard replacement...and keep your backups up to date!
DocHoliday77 said:
Im out of ideas for you...sorry. I kinda think its probably a hardware issue. It sounds like youve done everything you can to get root or recovery. Might be wise to start looking into a motherboard replacement...and keep your backups up to date!
Click to expand...
Click to collapse
I just spent $215 on this. I don't think the place where I bought it from will ever take it back.
I wish i had something better for you to try. Sorry.
If you are willing and able to consider it, i saw several motherboards and devices with broken screens (but otherwise functional) go for less than $65 today. Its the best option i can think of now.
Where at?
Sorry. It was on ebay. They often will go for a bit more than that, but if you are patient you should be able to get one relatively cheap.
Just do not buy any that say no power. Just look at ones that are a good motherboard, or a device with a broken screen where they say it powers on, just with no display. Also make sure the IMEI is clean.
Good luck!
Would anyone happen to know where I can get the firmware for the Sprint variant of the Galaxy tab S 10.5? I have the "Firmware Upgrade Encountered an Error issue" after attempting to root with CF Auto Root. Kies 3 says it doesn't support the tablet, Sammobile doesn't have it and im pretty sure I don't want to contact Samsung quite yet. Thanks in advance.
Yes sammobile doesnt have firmware yet for snapdragon version
I just found out this tablet just came out to sprint. Which caused cf auto root to fail. Which could also mean it isn't on Sam mobile yet.
Is this a common thing? Does sammobile rarely get them for the Snapdragon variants?
Not sure, when the tab s wifi one came out there was already roms for them.
BDA_Rival said:
Would anyone happen to know where I can get the firmware for the Sprint variant of the Galaxy tab S 10.5? I have the "Firmware Upgrade Encountered an Error issue" after attempting to root with CF Auto Root. Kies 3 says it doesn't support the tablet, Sammobile doesn't have it and im pretty sure I don't want to contact Samsung quite yet. Thanks in advance.
Click to expand...
Click to collapse
well...since u have already tried the worse thing possible which is to flash a fule meant for an exynos device on a qualcom chipset then u might as well try this suggestion since it cant really make things worse at this point & just MIGHT actually work. Instead of using the our cfautoroot attempt to use the tab pro SM-T525 cfautoroot (link below)...i just saw that someone suggested that in another thread but dont know if u have had chance to try it yet. Also....as @edan1979 suggested chainfire is pretty good about creating new root packages if u can get him the files that he requests. If u do get this thing rooted with the file below then please pos back because i have a few files i need from your device if its not too much trouble...thx in advacnce
http://download.chainfire.eu/393/CF-Root/CF-Auto-Root/CF-Auto-Root-picassolte-picassoltexx-smt525.zip
^TAB 10.1 LTE SM-T525 CFAUTOROOT (same chipset except for screen...just might be the magic fix)
on a related note....i have aso been searching for the new qualcom/carrier branded firmware files & culdnt find them on sammobile either so if someone finds the one for sprint or the att/verizon version (SM-T707) then please let me know.
@DUHAsianSKILLZ
Just to be clear...i saw in the other thread that u said the wifi root method worked so i'm wondering what version of the device do u actually own?
@BDA_Rival
Thats actually why i suggested trying the other method...at this point your tablet could POTENTIALLY already be bricked & flashing the file i suggested is not only harmless but COULD even bring your tab back from the dead because theres no telling how long it will be before the firmware files are available. Worse case u can return it to sprint & say it failed during an over the air upgrade...i would definitely try the link i added NOT for the root but as an attempt to revive the tablet
I dont even care about root at this point, id rather have my tablet boot up to the stock OS. And I'd rather not fully brick it.
@THEDEVIOUS1 in the other thread I didn't know he had a sprint LTE tab s. I own a WiFi version of the tab s 10.5 inch. Sorry for any confusion.
THEDEVIOUS1 said:
Thats actually why i suggested trying the other method...at this point your tablet could POTENTIALLY already be bricked & flashing the file i suggested is not only harmless but COULD even bring your tab back from the dead because theres no telling how long it will be before the firmware files are available. Worse case u can return it to sprint & say it failed during an over the air upgrade...i would definitely try the link i added NOT for the root but as an attempt to revive the tablet
Click to expand...
Click to collapse
so i tried this because why not, already went to a service center and they acted like theyve never seen my issue. before i tried this, i had the binary status saying custom and the kox counter said 0. i flashed this, it was successful finally and my knox counter is at 1 which is fine. it tries to boot up unlike before but restarts saying "Could not normal boot" but i atleast see the splash screen. one question i guess i have is what would happen if i flashed the firmware for th the sm-t525? not that im seriously contemplating but if its the closest, chipset wise, would it work? i dont really care about cellular signal and if i brick it, im probably better off calling sprint with a completely bricked tablet that they wouldnt know was once rooted than one that says custom binary and the knox counter set off.
Well at least that's an improvement...the Odin firmware file will most likely NOT flash due to security checks so the only real hope u have right now is to try the 525 cwm or twrp and & see if it will boot into recovery. If it actually works then u could attempt one of their custom roms (would probably remove the boot.mg first) or maybe even cm11 for the tab pro (would have to delete the assert lines in the updater script so it would even flash). U can also try the a qualcom note 3 custom recovery (if they work will probably have resolution issues) or the 10.1 note 2014 ones which has the same chipset and resolution also
THEDEVIOUS1 said:
Well at least that's an improvement...the Odin firmware file will most likely NOT flash due to security checks so the only real hope u have right now is to try the 525 cwm or twrp and & see if it will boot into recovery. If it actually works then u could attempt one of their custom roms (would probably remove the boot.mg first) or maybe even cm11 for the tab pro (would have to delete the assert lines in the updater script so it would even flash). U can also try the a qualcom note 3 custom recovery (if they work will probably have resolution issues) or the 10.1 note 2014 ones which has the same chipset and resolution also
Click to expand...
Click to collapse
do radios matter though? would it brick because im flashing a verizon rom and those use different radios, or would it be better to flash a wifi rom? i dont really care if i have mobile data, i only use wifi. if i flash a 525 twrp, it wouldnt disable odin mode, would it?
BDA_Rival said:
do radios matter though? would it brick because im flashing a verizon rom and those use different radios, or would it be better to flash a wifi rom? i dont really care if i have mobile data, i only use wifi. if i flash a 525 twrp, it wouldnt disable odin mode, would it?
Click to expand...
Click to collapse
I'm assuming Odin mode & download mode are the same thing so the answer is yes IF it works u would be able to do the key combination and boot directly into recovery from Odin mode...I would NOT flash the radio although it shouldn't harm anything but what we really want right now is to leave as much of the original file system in place as possible & the only thing that technically should be different at this point is the recovery partition. The wifi versions are exynos devices so NO do NOT flash those because that's how we ended up here in the first place...just follow my last reply & since I don't like to waste posts if u respond needing more help just check back here for a mention of your username
THEDEVIOUS1 said:
I'm assuming Odin mode & download mode are the same thing so the answer is yes IF it works u would be able to do the key combination and boot directly into recovery from Odin mode...I would NOT flash the radio although it shouldn't harm anything but what we really want right now is to leave as much of the original file system in place as possible & the only thing that technically should be different at this point is the recovery partition. The wifi versions are exynos devices so NO do NOT flash those because that's how we ended up here in the first place...just follow my last reply & since I don't like to waste posts if u respond needing more help just check back here for a mention of your username
Click to expand...
Click to collapse
so im not sure i understood the last part of your message about wasting posts but i figured youd want to hear this. So i download the TWRP for the SM-P905 (note pro 12.2) and after i flashed it through odin, the tablet restarted and booted all the way up. I dont get how the hell this worked but flashing TWRP fixed my OS not booting. I also went to settings to check my device status and it says custom. i want to install super su but i dont know if TWRP stuck for sure or not and i cant get TWRP to boot, it keeps taking me to download mode. any ideas? id like to make a back up in case something dumb happens.
Edit: Got into recovery by holding home button, volume up button, and power but it says "Recovery booting, Recovery is not SEANDROID ENFORCING", not too sure what that means. heres the weird part. after it shows that, the screen starts turning gold within a matter of 15 seconds.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ever seen that before?
BDA_Rival said:
so im not sure i understood the last part of your message about wasting posts but i figured youd want to hear this. So i download the TWRP for the SM-P905 (note pro 12.2) and after i flashed it through odin, the tablet restarted and booted all the way up. I dont get how the hell this worked but flashing TWRP fixed my OS not booting. I also went to settings to check my device status and it says custom. i want to install super su but i dont know if TWRP stuck for sure or not and i cant get TWRP to boot, it keeps taking me to download mode. any ideas? id like to make a back up in case something dumb happens.
Click to expand...
Click to collapse
Sorry but the last part wasn't that serious...I just don't like to run my post count up. ok...that's great news which confirms what I thought since all the cf root really does is flash an altered stock recovery, install root then flash stock back. So...what I would try at this point is to go ahead & install supersu & hope that it detects the su file (it technically should) & if/when it requests u to upgrade the file choose NORMAL method NOT twrp/cwm which will attempt to finalize the root WITHOUT needing to boot into twrp. I would try to avoid that because even if it stuck there may be problems with the fact that it is from another device and will potentially screw the partitions up worse.....I know this is not the best bet for a backup but I would avoid recovery until u can find the proper Sprint Odin firmware for your device & instead just useb titanium to backup up your apps, system settings, & whatever else u can with it for the time being. At this point I would just be satisfied with the fact that u now have a working device & wait to do anything further until u get the correct software to fully fix it...well I'm glad u were able to get it going and IF u in fact have real root then can i get a HUGE favor? I need the keyguard.apk as well the framework-res.apk & twframework-res.apk with the corresponding odex files of course (i wouldn't mind having systemui & both framework jars if possible also)...if u can't do it , don't know how or it's just too much trouble then don't worry about it but i just thought I'd ask since I've been trying to find snap versions these files
@BDA_Rival
U edited your post before I could finish my reply but long story short just leave recovery alone for right now...what u are seeing is most likely due to the different types of screens between the 12.2 & 10.5 so the display driver is causing that problem. No problem on the assistance...that's were all supposed to be here for
Just thought I'd throw this out there since u seem to be able to find your way back home now but maybe if u try the cfautoroot for the P905 12.2 note pro then MAYBE that will root it...just thinking out loud though
http://forum.xda-developers.com/showthread.php?t=1980683&page=24
^NOTE PRO 12.2 LTE P905 CFAUTOROOT (see post #235...just in case u get the guts to try it again good luck)
THEDEVIOUS1 said:
Sorry but the last part wasn't that serious...I just don't like to run my post count up. ok...that's great news which confirms what I thought since all the cf root really does is flash an altered stock recovery, install root then flash stock back. So...what I would try at this point is to go ahead & install supersu & hope that it detects the su file (it technically should) & if/when it requests u to upgrade the file choose NORMAL method NOT twrp/cwm which will attempt to finalize the root WITHOUT needing to boot into twrp. I would try to avoid that because even if it stuck there may be problems with the fact that it is from another device and will potentially screw the partitions up worse.....I know this is not the best bet for a backup but I would avoid recovery until u can find the proper Sprint Odin firmware for your device & instead just useb titanium to backup up your apps, system settings, & whatever else u can with it for the time being. At this point I would just be satisfied with the fact that u now have a working device & wait to do anything further until u get the correct software to fully fix it...well I'm glad u were able to get it going and IF u in fact have real root then can i get a HUGE favor? I need the keyguard.apk as well the framework-res.apk & twframework-res.apk with the corresponding odex files of course (i wouldn't mind having systemui & both framework jars if possible also)...if u can't do it , don't know how or it's just too much trouble then don't worry about it but i just thought I'd ask since I've been trying to find snap versions these files
Click to expand...
Click to collapse
so i tried root checker, it said no root, i tried installing super su, said no root as well. i guess even though my device status says custom, im not actually rooted i went ahead and tried that CF Autoroot you suggested earlier in Odin and it gave me a boot loop so i flashed TWRP again and now its booting all the way. still says im not rooted so i just dont think its gonna work. If it did, i would have gotten that stuff for you for all your help. thanks for helping out.
Hello. I'm just making this post to clear up some things and rumors about the posts going around about root firmware etc for newer ATT Galaxy phones like the s6, s6 edge, s6 edge + and the Note 5...
First of all these files have been around for some time now and only very few people in the unlocking/imei repair scene had them (including me) and just a few days ago someone decided to leak them and well they are now being offered for sale etc etc...Anyways these are what is called "engineering" kernel boot images with insecure adbd enabled meaning that it gives you root shell access.
Now the software that we use for our "unlocking" purposes only require this access to perform the operations that we want. However with all the new security Samsung has implemented, these kernels are by no means full root options. For example trying to use apps that require root (Titanium, Root checker) won't work and updating the SU binary under supersu app will send the phone on a bootloop because of SELINUX etc etc and as you know the only way to get around that is by flashing a custom kernel but ATT models having a locked bootloader this is not an option.
TL,DR : These files will only grant you "half assed" root that most people won't be able to take advantage of because it is all run over adb shell..maybe kernel wizards like @arter97 would like to take a look at them and see if he can find something useful
Any questions feel free to ask
Sunderwear said:
Hello. I'm just making this post to clear up some things and rumors about the posts going around about root firmware etc for newer ATT Galaxy phones like the s6, s6 edge, s6 edge + and the Note 5...
First of all these files have been around for some time now and only very few people in the unlocking/imei repair scene had them (including me) and just a few days ago someone decided to leak them and well they are now being offered for sale etc etc...Anyways these are what is called "engineering" kernel boot images with insecure adbd enabled meaning that it gives you root shell access.
Now the software that we use for our "unlocking" purposes only require this access to perform the operations that we want. However with all the new security Samsung has implemented, these kernels are by no means full root options. For example trying to use apps that require root (Titanium, Root checker) won't work and updating the SU binary under supersu app will send the phone on a bootloop because of SELINUX etc etc and as you know the only way to get around that is by flashing a custom kernel but ATT models having a locked bootloader this is not an option.
TL,DR : These files will only grant you "half assed" root that most people won't be able to take advantage of because it is all run over adb shell.
Any questions feel free to ask
Click to expand...
Click to collapse
Very informative, pretty much everything I needed to know. If you can't use root apps then I'm sure a lot of users will disregard the files, myself included as I only would like to use said apps. Thanks for the info?
all root files https://www.dropbox.com/s/gkxk32f778odlxu/AT&T_Root_Files.rar?dl=0
ohap said:
all root files https://www.dropbox.com/s/gkxk32f778odlxu/AT&T_Root_Files.rar?dl=0
Click to expand...
Click to collapse
how can we use that boot img with is associated with the N920AUCE2APB2 firmware, which no one has.
edit: turns out that the N920AUCE2APB2 firmware is based on the MashMallow (6.0.1) link below for proof . so i guess it wouldn't work on 5.1.1
img link
http://www.phone-probe.com/wp-conte...63_10205787832278168_2060735319_n-169x300.jpg
Would it be possible to use the ENG kernel to manually install the superuser binary and push the superuser apk to system? Or would that cause the same bootloops also?
We need a working recovery odin file first.
jellybear456 said:
Very informative, pretty much everything I needed to know. If you can't use root apps then I'm sure a lot of users will disregard the files, myself included as I only would like to use said apps. Thanks for the info?
Click to expand...
Click to collapse
As not much has been said in the thread, yes after Odin flashing the ENG kernel for our device and flashing a root script we can use rooted apps. @metalcated posted a script that does push SuperSU into system/. This was originally posted in the atat GS6 forum. It's a potentially complicated process and if your phone shuts off, battery dies or you hard reboot you will be stuck in a bootloop, hotbooting works fine for Xposed. Will this method be practical for everyone probably not, but considering we were told the device was unrootable........
Read thru his thread, then read it again, seriously do this. And if you still want to try, backup everything you can just in case you need to reflash via Odin to recover from a bootloop. Here were my steps.
1.Updated to newest firmware @Sunderwear posted PB2 (BL/AP/CP/CSC) this will wipe your device. In the pics provided I did try a couple firmware combinations after flashing PB2. I wouldn't suggest this but to each their own.
2.Metalcateds thread is here:
http://forum.xda-developers.com/att-galaxy-s6/general/root-5-1-1-qa-oj7-root-snag-t3334546
3. The only file I downloaded and used was this one:
https://www.androidfilehost.com/?fid=24438995911977129
(G920a5.1.1.root.metalcated-v4.zip)
4.Save it and extract it on your PC
5. Verify Samsung drivers and adb are installed
6.***ENABLE USB DEBUGGING*** this is an important step.
7. Plug device into PC open file and run root script. It'll prompt you to press enter a couple of times and reboot the phone. Just follow the on-screen instructions.
8. After it reboots you have root access.
Root apps that work for me: Titanium backup/root explorer/build.prop editor/no frills.
I was able to delete all Knox apps and debloat the heck of the stock ROM. At no point did my device freeze, reboot on its own.
None of this is my work, I just figured out how to get it going on our device. If you want to try it out and your successful thank @metalcated and everyone listed in the thread as they did all the work..
A couple people reported their Knox warranty tripped to 1. So i felt I needed to check if this tripped my own Knox counter. So I'm bootlooped for now but my Knox is 0 !!!! @TechNyne66 and @jrtran I'm posting the instructions on how to do this if you decide to try this method I originally pm'd to you both.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6P using XDA-Developers mobile app
Michael3214 said:
As not much has been said in the thread, yes after Odin flashing the ENG kernel for our device and flashing a root script we can use rooted apps. @metalcated posted a script that does push SuperSU into system/. This was originally posted in the atat GS6 forum. It's a potentially complicated process and if your phone shuts off, battery dies or you hard reboot you will be stuck in a bootloop, hotbooting works fine for Xposed. Will this method be practical for everyone probably not, but considering we were told the device was unrootable........
Read thru his thread, then read it again, seriously do this. And if you still want to try, backup everything you can just in case you need to reflash via Odin to recover from a bootloop. Here were my steps.
1.Updated to newest firmware @Sunderwear posted PB2 (BL/AP/CP/CSC) this will wipe your device. In the pics provided I did try a couple firmware combinations after flashing PB2. I wouldn't suggest this but to each their own.
2.Metalcateds thread is here:
http://forum.xda-developers.com/att-galaxy-s6/general/root-5-1-1-qa-oj7-root-snag-t3334546
3. The only file I downloaded and used was this one:
https://www.androidfilehost.com/?fid=24438995911977129
(G920a5.1.1.root.metalcated-v4.zip)
4.Save it and extract it on your PC
5. Verify Samsung drivers and adb are installed
6.***ENABLE USB DEBUGGING*** this is an important step.
7. Plug device into PC open file and run root script. It'll prompt you to press enter a couple of times and reboot the phone. Just follow the on-screen instructions.
8. After it reboots you have root access.
Root apps that work for me: Titanium backup/root explorer/build.prop editor/no frills.
I was able to delete all Knox apps and debloat the heck of the stock ROM. At no point did my device freeze, reboot on its own.
None of this is my work, I just figured out how to get it going on our device. If you want to try it out and your successful thank @metalcated and everyone listed in the thread as they did all the work..
A couple people reported their Knox warranty tripped to 1. So i felt I needed to check if this tripped my own Knox counter. So I'm bootlooped for now but my Knox is 0 !!!! @TechNyne66 and @jrtran I'm posting the instructions on how to do this if you decide to try this method I originally pm'd to you both. View attachment 3705507
View attachment 3705513View attachment 3705514View attachment 3705515
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Wow that's great information and great news. Thanks! I'm going to give this all a few reads and possibly give it a shot. I'll be sure to inform anyone if I try it and have success. A long process, but I don't mind if I can successfully gain root access and use root apps that may make my battery life a bit better. Thanks again!
@Michael3214 I tried and it works good on G920A, G925A, G928A and N920A. If you have stock firmware for N920A (PB2), please post it. Thanks
If it goes in boot loop. Do u think it's really worth the effort. Personally I think it needs little more work. Least it's going in right direction. Maybe they get boot loop fixed. Even if it trips Knox it . That be fine with me.
Rocking Samsung Galaxy Universal Park Themes.
I'm sure somebody much smarter than me has tried already, but could we push a script to set SELinux to permissive upon boot?
http://forum.xda-developers.com/ver...ipt-permissive-selinux-stock-kernels-t2854364
XRange said:
If it goes in boot loop. Do u think it's really worth the effort. Personally I think it needs little more work. Least it's going in right direction. Maybe they get boot loop fixed. Even if it trips Knox it . That be fine with me.
Rocking Samsung Galaxy Universal Park Themes.
Click to expand...
Click to collapse
Without access to a pc its a bad spot to be caught in. I ran the "root-Boot.cmd" to recover from the bootloop. The phone hangs on the splash screen for 45 seconds then finishes booting back into android.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
---------- Post added 4th April 2016 at 12:05 AM ---------- Previous post was 3rd April 2016 at 11:57 PM ----------
jrtran said:
@Michael3214 I tried and it works good on G920A, G925A, G928A and N920A. If you have stock firmware for N920A (PB2), please post it. Thanks
Click to expand...
Click to collapse
Here's the link to the firmware.
http://forum.xda-developers.com/showthread.php?t=3331843
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
I have OGG firmware restore and can try different methods if needed. I've tried a few with no success. But am able to recover from bad flashes. Willing to test anything that doesn't flash recovery or kernel.
XRange said:
If it goes in boot loop. Do u think it's really worth the effort. Personally I think it needs little more work. Least it's going in right direction. Maybe they get boot loop fixed. Even if it trips Knox it . That be fine with me.
Rocking Samsung Galaxy Universal Park Themes.
Click to expand...
Click to collapse
Excuse my ignorance if this strikes anyone as a noob question... If my device bootloops I obviously cannot go into download mode... My question is twofold: 1: Is my only recourse to flash firmware via Odin?.. And if so... 2: Will my computer/Odin recognize my phone while it is in bootloop?
2Tone23 said:
Excuse my ignorance if this strikes anyone as a noob question... If my device bootloops I obviously cannot go into download mode... My question is twofold: 1: Is my only recourse to flash firmware via Odin?.. And if so... 2: Will my computer/Odin recognize my phone while it is in bootloop?
Click to expand...
Click to collapse
Hold volume up and down + power + home tell your phone resets, then volume down + power + home to boot download mode.
TechNyne66 said:
Hold volume up and down + power + home tell your phone resets, then volume down + power + home to boot download mode.
Click to expand...
Click to collapse
And this works if you're caught in a bootloop, correct? Also, the I have the files for AOJ1 not APB2. there shouldn't be an issue restoring through odin from APB2 to the older AOJ1 because it's still lollipop, right?
can we use this just to debloat and be good?
blane3298 said:
can we use this just to debloat and be good?
Click to expand...
Click to collapse
Yes about all root is good for anyways.
---------- Post added at 06:08 PM ---------- Previous post was at 06:07 PM ----------
jellybear456 said:
And this works if you're caught in a bootloop, correct? Also, the I have the files for AOJ1 not APB2. there shouldn't be an issue restoring through odin from APB2 to the older AOJ1 because it's still lollipop, right?
Click to expand...
Click to collapse
Doesn't matter just don't downgrade firmware or flash anything but AP in odin.
have you tried this yet?
TechNyne66 said:
Hold volume up and down + power + home tell your phone resets, then volume down + power + home to boot download mode.
Click to expand...
Click to collapse
Thanks for your response... I just want to be clear, while in bootloop I can put my phone into download mode by the usual means?
Gidday
As the thread title says, I can't access recovery on my ZE551ML...
I recently wiped the custom ROM (SuperZen) and installed LP and then MM...all working good, no problems...then rooted and unlocked the bootloader and attempted to install TWRP and now can't access recovery mode...this means that I am unable to install TWRP....have tried to install using the TWRP app but no go...
Also, another issue I am having is trying to copy files to the SDCard...I get a permission problem that I can't get access when I have installed SUPERSU and have rooted the phone and X-plore has root access and so has ES file explorer...
cbrokey said:
Gidday
As the thread title says, I can't access recovery on my ZE551ML...
I recently wiped the custom ROM (SuperZen) and installed LP and then MM...all working good, no problems...then rooted and unlocked the bootloader and attempted to install TWRP and now can't access recovery mode...this means that I am unable to install TWRP....have tried to install using the TWRP app but no go...
Also, another issue I am having is trying to copy files to the SDCard...I get a permission problem that I can't get access when I have installed SUPERSU and have rooted the phone and X-plore has root access and so has ES file explorer...
Click to expand...
Click to collapse
in the general section above , there is a bl unlock modder tool by giovix specifically works only on M , set it up ..use return to stock option, flash boot.img ,then flash recovery.
Then , re unlock the boot loader option ,just in case
Then flash twrp option
Then root option.
You will be fine
timbernot said:
in the general section above , there is a bl unlock modder tool by giovix specifically works only on M , set it up ..use return to stock option, flash boot.img ,then flash recovery.
Then , re unlock the boot loader option ,just in case
Then flash twrp option
Then root option.
You will be fine
Click to expand...
Click to collapse
Thanks for the reply...went through the steps again (did this a couple of times yesterday but musta did sumptin wrong)...anyway, TWRP is up and running...now just have to get Xposed installed...
As I said in the OP I am having problems copying files to my SDcard on the phone...its rooted and X-plore and ES file manager have access to root but each time I try to transfer a file I get an annoying message saying that I cant
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/showpost.php?p=70079801&postcount=126
^^^
When you say you mighta did sumfink wrong , yup -- you should`ve flashed stock recovery back in the link first ^^^ .
Just thought i`d give you that hint to prevent future probs
The sd card prob i have too but i know mine is driver conflicts which i have to live with , on my spare un-updated lappy with windows 10 , all is fine. Plus share link app allows to and thro to any sd from pc and vice versa ok.
Maybe ,you flash back stock boot.img - recovery with the modder tool . Return to complete MM stock.
See if anything you did was a little something wrong
timbernot said:
http://forum.xda-developers.com/showpost.php?p=70079801&postcount=126
^^^
When you say you mighta did sumfink wrong , yup -- you should`ve flashed stock recovery back in the link first ^^^ .
Just thought i`d give you that hint to prevent future probs
Click to expand...
Click to collapse
Ta :good:
The sd card prob i have too but i know mine is driver conflicts which i have to live with , on my spare un-updated lappy with windows 10 , all is fine. Plus share link app allows to and thro to any sd from pc and vice versa ok.
Maybe ,you flash back stock boot.img - recovery with the modder tool . Return to complete MM stock.
See if anything you did was a little something wrong
Click to expand...
Click to collapse
I have had this problem before but this was months ago when I initially installed SuperZen the custom ROM...I got around it somehow but I am flummoxed if I can remember how now
I need to be able to transfer the Xposed installer to the SDCard so I can flash it...
Ok try the info in ASUS file manager
open file manger , 3 dots , about , help and feedback , 2nd box down
Share link stock ASUS app is a great tool too
timbernot said:
Ok try the info in ASUS file manager
open file manger , 3 dots , about , help and feedback , 2nd box down
Click to expand...
Click to collapse
Tried that but no go...I was able to try it a couple of times and now when I go to the 3 dots menu the 2nd option down has changed and wont allow me to change the settings...
Share link stock ASUS app is a great tool too
Click to expand...
Click to collapse
It looks okay but I have X-plore...does the same thing and works well over the network but still won't let me copy to the SD card...despite trying many things
You really have borked it up, return to stock
timbernot said:
You really have borked it up, return to stock
Click to expand...
Click to collapse
Think I will...seems the easiest way to go...should get this uni assignment out of the way first though :silly:
cbrokey said:
Think I will...seems the easiest way to go...should get this uni assignment out of the way first though :silly:
Click to expand...
Click to collapse
Yup, stop playing with ya phone
timbernot said:
Yup, stop playing with ya phone
Click to expand...
Click to collapse
But its fun
Since the last posts regarding access problem to the SDCard I have since installed the update via sideload and thought that it would get around the problem of access but it hasnt (the FM Radio now works which is a bonus )...my phone is now not rooted and I havent done anything else to it...any help appreciated...
cheers
col
Im facing same recovery problem, unable to install it on my ZE550ML (6.0.1), it flashes fine but it wont go to recovery from bootloader, i can only go into recovery from android using adb command but that too takes me to stock recovery, i dont know why stock recovery comes back lol
EDIT: i found out what i was doing wrong, my bootloader got locked during something nd i didnt knew, unlocked it again nd everything works fine now!
I have now gone beyond the meagre problem of not being able to copy to the SD Card...I attempted to root the phone and now have soft bricked it...I am able to get to a recovery menu of sorts but when I try and sideload using ADB I get "device not found"...have been trawling the web for hours looking for a fix