Develop Bugs

[Q] need help please

hi everybody
i am new here and i want ask some question so hope i cen get answer with details because i dont have god idea about android.
i've got HTC desire HD and i gave it to someone to install for me an other rom with arabic support because the original one did not support arabic, the rom he installed is ok it supports arabic fine but it's older version than the one i had before many features are not.
so please can someone help me to give me links of a custom rom where i can download an other rom with arabic support and with HTC sense and step by step how to install and flash the phone. i searched in the forum but i cant find anything i dont know how
thank you for your help

hi
nihedbf said:
hi everybody
i am new here and i want ask some question so hope i cen get answer with details because i dont have god idea about android.
i've got HTC desire HD and i gave it to someone to install for me an other rom with arabic support because the original one did not support arabic, the rom he installed is ok it supports arabic fine but it's older version than the one i had before many features are not.
so please can someone help me to give me links of a custom rom where i can download an other rom with arabic support and with HTC sense and step by step how to install and flash the phone. i searched in the forum but i cant find anything i dont know how
thank you for your help
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=18812266&postcount=9698
here is ur arabic rom buddy.....
to instal a rom u have to download rom manager in ur dhd
then go in the rom manager and check if the FLASH CLOCKWORKMOD RECOVERY IS 5.0.2.0
if not then just click on the first option in rom manager and u will see a pop up select desire hd and wait till another pop up says FLASH CLOCKWORKMOD RECOVERY IS UP TO DATE OR 5.0.2.0( make sure u have internet connection on ur dhd)
then go to option INSTAL ROM FROM SD CARD( make sure the rom u want to instal is in ur sd card an u know where u have place it)
then select ur rom and a pop up window will ask some options select all of
them and click ok
there u go it will reboot into recovery and start instaling ur rom
MAKE SURE U BACK UP UR ALL DATA , WHICH IS ON PHONE MEMORY. DONT WORRY ABOUT SDCARD DATA ITS SAFE UNLESS U FORMAT IT.

thank you very much for your fast answer. i will try that but before i will do it i want to ask an other questionto make sure...
what if i do it and something goes wrong do i will damage the phone??or nothing will happenen

Since somebody already installed another ROM for you, ClockworkMod or 4EXT recovery will be there already.
First turn off the phone, remove the battery and then reinsert. That way you know the phone is completely off.
Hold down the volume DOWN button, and then hold down the power button. You will get to a white screen with some options. It takes a while to load so be patient.
When it loads, use the volume keys to select Recovery and then press the Power button to select Recovery.
When that loads, please tell us if it is ClockworkMod or 4EXT Recovery that is installed. It will say at the top.
After you tell us this we will be able to help you further
If you follow our instructions nothing will go wrong. And if for some reason it does, it will definitely be recoverable.

raze599 said:
Since somebody already installed another ROM for you, ClockworkMod or 4EXT recovery will be there already.
First turn off the phone, remove the battery and then reinsert. That way you know the phone is completely off.
Hold down the volume DOWN button, and then hold down the power button. You will get to a white screen with some options. It takes a while to load so be patient.
When it loads, use the volume keys to select Recovery and then press the Power button to select Recovery.
When that loads, please tell us if it is ClockworkMod or 4EXT Recovery that is installed. It will say at the top.
After you tell us this we will be able to help you further
If you follow our instructions nothing will go wrong. And if for some reason it does, it will definitely be recoverable.
Click to expand...
Click to collapse
hi . thank you a lot for your fast answer i did like you said i switch off the phone after i took off the battery and i turn it on hold the button and recovery i did but when i press the power button to select recovey it come something like a mobile pictures with red symbol like on the picture down
so what i have to do please. i call the man who did my phone he said that my phone is not rooted.. so how can i rooted please??
{
"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"
}

Ah ok, I'm not so sure what that person actually did to change the ROM in the first place then.
Anyway, to root first we will need your software number (a number that is in the format x.xx.xxx, such as 2.50.405)
Go to Settings -> About Phone -> Software Information.
There are currently 2 ways to root it, one is quick and easy but (personally) I think it is more unreliable. The other way takes longer and is a bit more work but is guaranteed to work (depending on the software version). I will explain more about this when you can show me your software number

raze599 said:
Ah ok, I'm not so sure what that person actually did to change the ROM in the first place then.
Anyway, to root first we will need your software number (a number that is in the format x.xx.xxx, such as 2.50.405)
Go to Settings -> About Phone -> Software Information.
There are currently 2 ways to root it, one is quick and easy but (personally) I think it is more unreliable. The other way takes longer and is a bit more work but is guaranteed to work (depending on the software version). I will explain more about this when you can show me your software number
Click to expand...
Click to collapse
softaware number is 1.83.415.4 you can give me the two ways and i will see which better and easy to me thanks a lot

hi
nihedbf said:
softaware number is 1.83.415.4 you can give me the two ways and i will see which better and easy to me thanks a lot
Click to expand...
Click to collapse
First u have to downgrade ur phone software here is the link try this very carefully plz....
http://forum.xda-developers.com/showthread.php?t=905003
After that u have to root ur phone
BE CAREFUL THIS MIGHT BRICK UR PHONE
This is complete guide for all HTC Desire HD owners who want's to root their devices and install custom recovery image.
FLASH THIS AT YOUR OWN RISK, I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG
I have collected and summarize few guides on this forum in order to collect all informations on one place. Check following threads for additional informations. Please post all bug's and issues related to DHD scripts to sfjuocekr thread below. http://forum.xda-developers.com/showthread.php?t=835746
http://forum.xda-developers.com/show....php?p=9183483
Summary: 1) Download Paul's Visionary+ tool (I have used version r12) (google removed this app from market) so You will have to download it from Paul's website. This tools enables root and removes new HTC protection. 2) Install engineering version of HBOOT to get S-Off (HTC bootloader, something like BIOS for Your PC) This step is optional and it's not required in order to flash custom ROM's on Your DHD but gives You more freedom with Your device. 3) Install custom recovery image (recovery is special program which is invoked from HBOOT in order to flash ROM onto Your device.
Detailed description: 1) Download Paul's Visionary+ tool 1.1) Click here to download http://android.modaco.com/content/ht...ne-click-root/ or download it from here http://forum.xda-developers.com/atta...3&d=1290501865 1.2) Install Visionary+ on Your DHD 1.3) Run it, enable "Set system r/w after root 1.4) Click "Temproot Now!" - Wait until it's finished 1.5) Click Attempt Permroot Now! 1.6) DHD automatically reboot's To test that everything went fine download from market application "terminal emulator" run it, type su If You get after that sign # it mean's that everything went fine.
Time for next step!
2) Install engineering version of HBOOT to get S-Off 2.1) Download sfjuocekr DHD script for flashing HBOOT from here http://forum.xda-developers.com/showthread.php?t=835746 2.2) Unzip it and copy it to Your SDCard (It's important that You have on Your SDCard root directory with name DHD and all files inside this directory. Rename DHD-smart folder on Your SDCARD to DHD. 2.3) Run Terminal Emulator 2.4) Type su 2.5) Type "sh /sdcard/DHD/check (Please be aware that You have to type "sh" in front of command) 2.6) If everything went OK type sh /sdcard/DHD/backup 2.7) If this also went OK proceed with sh /sdcard/DHD/hboot This command will install engineering hboot which have S-Off turned off.
3) Install custom recovery image 3.1) Since ROM manager now officially support's Desire HD, we will use it to download and install custom clockwork image. 3.2) Run android market app on Your DHD and download and install ROM Manager app from market. 3.3) Download and install ROM manager. 3.4) Run ROM manager and select first option (Flash ClockWorkMod Recovery). 3.5) Wait until ROM Manager say's that installation went successfully (Current version of ClockWorkMod is 2.5.1.3) 3.6) After installation tap in Rom manager option Reboot into Recovery to test that everything went well. 3.7) DHD should reboot in clockwork recovery manager.
Enjoy.
---------- Post added at 02:53 PM ---------- Previous post was at 02:41 PM ----------
BEFORE DOING ANYTHING U MUST WATCH SOME VIDEOS THIS VIDEO IT WILL GIVE U SOME IDEA ON ROOTING ......
Part 1. http://www.youtube.com/watch?v=AkbmKLCkDWg
Part 2. http://www.youtube.com/watch?v=Lah6BD_krjc&feature=fvwrel
Part 3. http://www.youtube.com/watch?v=bUgxRA2LEEo&feature=related

thanks you very much for all who help me

nihedbf said:
thanks you very much for all who help me
Click to expand...
Click to collapse
That means u have rooted ur phone
Nice..........

yes i have rooted my phone and i install a custom rom and i want to give my thanks for all members of this forum and special thanks for one member who spend a lot of time to help me step by step till i get it done.

How do i find out if the phone is rooted or not?

Hey everyone i have a telus samsung s3 and it wouldnt accept the unlock code so the guy who i bought the unlock code from said my phone might be rooted and i need to unroot it?
Heres the information from about device:
{
"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"
}
I also installed this app called "Root Checker" which shows if the device is rooted or not and heres the result:
According to this website: http://www.mobile-spy.com/blog/is-my-phone-rooted/. I downloaded an app called "Terminal" and followed the instructions:
Another simple way to find out is to download and install a “terminal” client on the phone. A “terminal” is a text-based window that allows us to run commands on Linux devices such as an Android phone or tablet. It is the command line interface for Linux, similar to DOS.
Upon opening the terminal, if you see a “#”, then the phone has root access and is in superuser mode.
If when opening the terminal you see a “$” then the phone is not in superuser mode, but that doesn’t mean that it has not been rooted.
Type “date” and press enter. It should display the date and time. If the date does not display, then the terminal doesn’t work, try downloading another terminal client.
Otherwise, type “su” without the quotes. If the device has been rooted, the next line will display a “#” signifying that you have root access and the device is ready for superuser commands. If it has not been rooted, then the terminal will not recognize the “su” command.
- See more at: http://www.mobile-spy.com/blog/is-my-phone-rooted/#sthash.kulPOwDL.dpuf
Click to expand...
Click to collapse
Here are the results:
As you can see it verifies that the phone isnt rooted so please tell me if there is some other way to verify or just those apps?

try another root checking app?
install an app that requires root and see if it works/asks for super user permission?

Never had a problem using root checker or the su command. Your phone is not rooted (unless someone tried to and then half-assed it maybe).

x0ne215 said:
Never had a problem using root checker or the su command. Your phone is not rooted (unless someone tried to and then half-assed it maybe).
Click to expand...
Click to collapse
if i factory reset the phone would it unroot the phone if it was rooted?

kaboose786 said:
if i factory reset the phone would it unroot the phone if it was rooted?
Click to expand...
Click to collapse
No, but your best bet to get the phone completely back to stock is to use Odin. Search "Odin back to stock". Pretty easy to do just need a computer and about 5 minutes.

x0ne215 said:
No, but your best bet to get the phone completely back to stock is to use Odin. Search "Odin back to stock". Pretty easy to do just need a computer and about 5 minutes.
Click to expand...
Click to collapse
how do i knw what was stock? right now its running android 4.3. I dont wanna brick my phone

Hey guys i am trying to use odin to flash to Android 4.1.1 but for some reason it keeps on failing in odin. And now i am stuck in "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". How do i know if i have the correct stock file? I downloaded 4.1.1 from here: http://www.sammobile.com/firmwares/1/?model=SGH-I747M&pcode=TLS#firmware.. why is it keep on failing? i have kies off should i just uninstall kies? i am really worried

kaboose786 said:
how do i knw what was stock? right now its running android 4.3. I dont wanna brick my phone
Click to expand...
Click to collapse
Did you download the correct firmware for your device? ex.SGH-I717
Sent from my Nexus 4 using Tapatalk

kaboose786 said:
Hey guys i am trying to use odin to flash to Android 4.1.1 but for some reason it keeps on failing in odin. And now i am stuck in "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". How do i know if i have the correct stock file? I downloaded 4.1.1 from here: http://www.sammobile.com/firmwares/1/?model=SGH-I747M&pcode=TLS#firmware.. why is it keep on failing? i have kies off should i just uninstall kies? i am really worried
Click to expand...
Click to collapse
That should be the right rom. Have you gone into recovery, wipe the phone and retry flash the stock rom? A reformat? i was having lots of trouble with mine but seen this today and tried method 2 with the exception of gapps to get it back to stock.
http://forum.xda-developers.com/showthread.php?t=2661345

kaboose786 said:
Hey guys i am trying to use odin to flash to Android 4.1.1 but for some reason it keeps on failing in odin. And now i am stuck in "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". How do i know if i have the correct stock file? I downloaded 4.1.1 from here: http://www.sammobile.com/firmwares/1/?model=SGH-I747M&pcode=TLS#firmware.. why is it keep on failing? i have kies off should i just uninstall kies? i am really worried
Click to expand...
Click to collapse
You running a 4.3 bootloader? Is your phone an i747 or i747m?

Firmware for SM-T807P

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.

Ota to won't take

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

Question Now I have a new issue regarding the boot.img file.

So I got my phone fixed by flashing some random files I got off a quick Google search and got my phone back up and everything.
Now I have a brand new issue and it's stressing me the hell out that I feel like throwing my phone at the wall because that's how much stress this piece of garbage called a phone is causing me. I have been at this for hours to no proper fix from countless google searches going through websites and other xda threads.
The issue I'm experincing is I'm patching the boot.img file with Magisk and I then flash the img file with adb fastboot. There's 4 things going on when I do this
1 - The phone boots up normally but my touchscreen doesn't work to where I can't click or navigate my entire phone.
2 - The phone ends up in a boot loop where I see the Motorola Logo and that's it it restarts over and over and over and never properly boots.
3 - The phone keeps booting into bootloader on it's own.
4 - When I am able to get through my phone normally after flashing a patched magisk boot file an android update ends up restarting my phone and completely removes my root and I'm back to square one...
All this because I got sick of being bugged by these (BEEP)ing Motorola update pop ups which I made a thread about it on here asking for a way to disable it but never got any responses so I've taken this into my own hands and have made it even MORE worse and it's stressing me out so much.
I need to know how to I extract the boot.img file from my phone myself? I'm finding so many tutorials telling me to just download some boot.img file off the internet but that's what's causing me these issues above because I'm patching something that's probably not even compatible with my phone to begin with so i want to know how do I get the boot.img file directly off my phone so I can patch that with magisk?
I'm at a breaking point with this phone...

jake7901 said:
So I got my phone fixed by flashing some random files I got off a quick Google search and got my phone back up and everything.
Now I have a brand new issue and it's stressing me the hell out that I feel like throwing my phone at the wall because that's how much stress this piece of garbage called a phone is causing me. I have been at this for hours to no proper fix from countless google searches going through websites and other xda threads.
The issue I'm experincing is I'm patching the boot.img file with Magisk and I then flash the img file with adb fastboot. There's 4 things going on when I do this
1 - The phone boots up normally but my touchscreen doesn't work to where I can't click or navigate my entire phone.
2 - The phone ends up in a boot loop where I see the Motorola Logo and that's it it restarts over and over and over and never properly boots.
3 - The phone keeps booting into bootloader on it's own.
4 - When I am able to get through my phone normally after flashing a patched magisk boot file an android update ends up restarting my phone and completely removes my root and I'm back to square one...
All this because I got sick of being bugged by these (BEEP)ing Motorola update pop ups which I made a thread about it on here asking for a way to disable it but never got any responses so I've taken this into my own hands and have made it even MORE worse and it's stressing me out so much.
I need to know how to I extract the boot.img file from my phone myself? I'm finding so many tutorials telling me to just download some boot.img file off the internet but that's what's causing me these issues above because I'm patching something that's probably not even compatible with my phone to begin with so i want to know how do I get the boot.img file directly off my phone so I can patch that with magisk?
I'm at a breaking point with this phone...
Click to expand...
Click to collapse
Most likely you have a mis-matched boot.img.
Use LMSA's flash rescue to reflash the firmware.
Then use that boot.img to patch with magisk.
Stop using random guides that offer no support.
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com

sd_shadow said:
Most likely you have a mis-matched boot.img.
Use LMSA's flash rescue to reflash the firmware.
Then use that boot.img to patch with magisk.
Stop using random guides that offer no support.
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
Forgot to include LSMA is not working for me at all probably due to the firmware that I used several weeks ago when I first rooted the phone.
{
"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"
}
I had a similar issue to this several weeks ago but it was some other error that I forgot and thinking this was a long time ago I thought by now the program would finally work for me today but nope it never works.
App thinks I'm not in fastboot when I am right now.
So sadly I have to depend on these confusing builds from here and there and who knows where pretty much trial and error...
I wouldn't be in this position if it wasn't for those annoying (BEEP)ing Motorola update pop ups ruining my phone.
Maybe I should just throw the phone at the wall there's no hope.

jake7901 said:
Forgot to include LSMA is not working for me at all probably due to the firmware that I used several weeks ago when I first rooted the phone.
View attachment 5577727
View attachment 5577731
I had a similar issue to this several weeks ago but it was some other error that I forgot and thinking this was a long time ago I thought by now the program would finally work for me today but nope it never works.
App thinks I'm not in fastboot when I am right now.
So sadly I have to depend on these confusing builds from here and there and who knows where pretty much trial and error...
I wouldn't be in this position if it wasn't for those annoying (BEEP)ing Motorola update pop ups ruining my phone.
Maybe I should just throw the phone at the wall there's no hope.
Click to expand...
Click to collapse
Could also be a usb issue, Motos have had some issues like this for a while.
Try a different USB port, Cable or PC

I had the same problem. After patching the boot.img with Magisk and fastboot flashing it, I got no touchscreen.
The problem was the wrong boot.img.
I downloaded Stock ROMs from several sources, all saying that my phone uses a particular Stock ROM. They were all wrong!
I used the Lenovo Rescue and Smart Assistant v6.4.2.13. With genuine Motorola USB drivers.
It found my phone via the IMEI and I downloaded the stock ROM it suggested, it was a different one from all the other ones I had previously downloaded.
TIP, when downloading from the Rescue and Assistant program change where you want it to download to, as it's a pain to try and find it later when you need the boot.img!
After patching with Magisk and fastboot flashing, I'm now rooted and EVERYTHING works!