Develop Bugs

Rom DESIRE HD?

Hi
I am trying to install '4EXTRecovery v2.1.3' however it wont work.
Do I need to root my phone before doing this.
The major problem I am facing is that everytime try to run a cmd file it
says
'error: device not found'
I have tried using visionary that doesnt work either, it doesnt temporary root so I cant to the perm root afterwards.
I have android 2.3.
Software no: 2.37.61.11
Visionary+
rooting phone please wait> then comes a black screen and if you click back on visionary it doesnt open, so I cant perm root after temproot
I am not trying to install any rom right now, what I do want to do is format the whole phone so it has nothing on it, except the '4EXTRecovery v2.1.3 loader so I can install my own rom later on.
{
"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"
}
Please tell me what is it that I have to do.
Thanks

this tool obviously seems to need s-off as well as root rights, so you'd need to downgrade.
but the device not found issue may be caused by missing adb drivers, so install HTC sync and try again, and don't forget to choose "Charge only" and enable USB-Debugging!

Alskarl is right.
You need to downgrade using a goldcard before you can use visionary.
Once you have downgraded you can use it.
once you have root you must eng-off/s-off to install a rom.
Also the other problem is due to missing drivers as alskarl said. =)
Sent from my Desire HD using XDA Premium App

Alskarl said:
this tool obviously seems to need s-off as well as root rights, so you'd need to downgrade.
but the device not found issue may be caused by missing adb drivers, so install HTC sync and try again, and don't forget to choose "Charge only" and enable USB-Debugging!
Click to expand...
Click to collapse
thanks, you two have put a smile on my face, i tried everything, hopefully it should work

Dont forget to hit thanks for us both
Sent from my Desire HD using XDA Premium App

thisisuzair said:
thanks, you two have put a smile on my face, i tried everything, hopefully it should work
Click to expand...
Click to collapse
the phone seems to cant find htc sync installed on my pc. what should I do, I have re installed it and yet I see the same issue

thisisuzair said:
the phone seems to cant find htc sync installed on my pc. what should I do, I have re installed it and yet I see the same issue
Click to expand...
Click to collapse
its because the adb drivers are not installed properly. i had this problem but never solved it and gave up. i re-installed numerous times with no luck, i tried everything and even installed drivers maually. still doesnt work now. my advice is try another pc. if you cant do that then start a new thread. sorry i cant help any more.

I had this same problem recently when attempting to root my wife's phone. After I rebooted my PC and deleted the USB devices from Device Manager it seemed to find it on the next hardware search and it configured it as a Android 1.0 device. Don't know how much help this will be but just thought I'd throw my personal experience out there.

adb server is out of date: killing
Could you please tell me what that means and how I can fix it.
Can you please tell me If I have been successful in installing 4extrecovery.
if i have then how do I access it on my phone.
Thanks

that "out of date" message is normal, I get that as well and android is just working fine for me

Power down. Hold the volume button down and press power. Keep holding the volume button until you enter hboot then select recovery. If it was flashed properly it should load into the recovery console.
Sent from my Inspire 4G using XDA Premium App

Need help with unroot

I need to send my phone in for warranty repairs and need to make sure it will be good to go. USB input is not working without holding the cable in a certain position.
This is where I am at right now.
Phone was rooted with ODIN on EL29 stock rom (http://forum.xda-developers.com/showthread.php?t=1433101) never used a custom rom or changed anything else
Deleted all Superuser files with explorer
Uninstalled all apps that were root related
After this process my 5 year old nephew was playing with my phone and clicked the Android update taking me to ICS 4.0.4
Did a factory reset in Privacy>Factory Reset Data
I believe it is not rooted anymore which is fine, but what else would I have to do to not void my warranty? Was reading about resetting the counter and needing to go back to stock recovery.
Any advice will help me greatly. Not sure what i should/need to do next.

Do nothing the update killed your phone. Take it back and explain what happened (minus the fact that it was rooted). The OTA kills root and puts on ICS stock.

I'm not a developer but I'd think that just deleting superuser files is not removing all traces of root. Try Odining an unrooted stock ROM, holding the USB cable in that specific way that works. And then remove the superuser files if you still have them.

Since I did the OTA ICS update, does that mean root is now gone and all I need to do is get rid of the Superuser files?
Any more help would be excellent. Trying to get this shipped out today.

If you did the ota update you no longer have root
Sent from my SPH-D710 using xda premium

Ok I followed this tutorial exactly to go back to stock EL29.
http://forum.xda-developers.com/showthread.php?t=1433101&highlight=yellow+triangle
This should have gotten me back to stock everything like the day it was shipped to me. Should I just update it to ICS and then ship it out to Samsung?
Is this the yellow triangle of death? I noticed that peoples yellow triangles are on the splash screen, mine is ont he screen prior to the downloader.
{
"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 used that method you will have root. Just use root explorer or something along those lines and delete the SU apk and SU binary in the Xbin folder. if you don't delete the binary file it will still be rooted.

g_ding84 said:
If you used that method you will have root. Just use root explorer or something along those lines and delete the SU apk and SU binary in the Xbin folder. if you don't delete the binary file it will still be rooted.
Click to expand...
Click to collapse
Uhoh lol. I thought doing this would put everything back to stock unrooted. Now how do I unroot from here after I get rid of those superuser files? I already turned off the service on this phone and hooked up my old one so I upgrade it to ICS.

ams30gts said:
Uhoh lol. I thought doing this would put everything back to stock unrooted. Now how do I unroot from here after I get rid of those superuser files? I already turned off the service on this phone and hooked up my old one so I upgrade it to ICS.
Click to expand...
Click to collapse
once the SU apk and Xbin binary file is deleted run root checker App (market) and you should be unrooted. Yes you can upgrade to ICS the official OTA that will also remove root.

g_ding84 said:
once the SU apk and Xbin binary file is deleted run root checker App (market) and you should be unrooted. Yes you can upgrade to ICS the official OTA that will also remove root.
Click to expand...
Click to collapse
Thank you very much. I deleted the SU files and then did a factory wipe for good measure. I then used root checker and it said i didn't have root.
I would have upped to ICS but my phone doesn't have service right now and it can't be downloaded via wifi.

no problem.

You still had root because the newer stock Odins that sfhub made started coming with root. If you did EK02 then you would've had a completely stock ROM.

Is this the dreaded Yellow Triangle that I should get rid of? Or is this one there by default? I do not have on on my splash screen and never did either.

The dreaded yellow triangle is on the Samsung splash screen(before boot animation). It will say Samsung galaxy S2 and i9000 with a yellow triangle.
Sent from my SPH-D710 using XDA

g_ding84 said:
The dreaded yellow triangle is on the Samsung splash screen(before boot animation). It will say Samsung galaxy S2 and i9000 with a yellow triangle.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
ok got it thanks

[Q] GT-N7105T - Telstra (Australia) Note 2, stalled during CF-Auto-Root

Hi All,
Just trying to find some people who've managed to root the Australian version of the Note 2 successfully? I have the Telstra Galaxy Note 2 (GT-N7105T) and sat down this afternoon to root using CF-Auto-Root.
I got to the part where the phone is in download mode after pressing the volume up to proceed (other option is to press volume down for exit & reboot). I did not change any settings in Odin, plugged the Note 2 into USB and hit Start in Odin (after selecting the CF-Auto-Root package... everything exactly as the instructions state), then it took a few minutes before it gave the "<ID:0/003> Added!" message. Since then it's been sitting for about an hour at the same screen both on the Note 2 and in Odin... getting a bit worried because Chainfire said this should only take 30 seconds..?!
Current Odin screenshot, it's been about 1 and a half hours now on this screen:
{
"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"
}
Hoping some others with rooting experience can help out – did I miss a step? In any case I don't think it's going to progress, so how should I exit out? Hit Reset in Odin? Just unplug the USB cable and try to reboot? Or a hard reset?
Cheers for any advice!

you have used the tar for normal lte version not telstra version.
if you have a nandroid then restore it.
i am not sure if you should or shouldn't disconnect cable of your phone...

Cheers for the reply UtkarshGupta.
I did a bit more research and found that I needn't have been so worried... I thought that maybe it had froze part way through flashing, but the ID:COM shows that it had only just connected with the device and hadn't done anything else! (Of course I only knew this after doing more research on Odin.) Probably because I plugged in the USB then clicked Start in Odin - the PC was still installing drivers and ID:COM wasn't lit up yellow at that stage, soo... it was okay to pull the USB cable, then I just held the power button to exit download mode.
But now the experience has me spooked - not sure if I should try again, or whether I should wait for a Telstra-specific root method that's been tested. After all this variant phone was only released two days ago here in Australia...

mugget said:
Cheers for the reply UtkarshGupta.
But now the experience has me spooked - not sure if I should try again, or whether I should wait for a Telstra-specific root method that's been tested. After all this variant phone was only released two days ago here in Australia...
Click to expand...
Click to collapse
I don't believe you have a problem with the ROM. Your problem is that you're running an old version of Odin3.
I received my N7105T the same day as you did and performed the root procedure first thing, using the same ROM as you have but Odin3 v3.04. No problem.
Two things though:
1) Be sure that you've installed the latest Kies to ensure the latest and greatest drivers are running.
2) Make sure after you've installed Kies that it's not running as it will otherwise not allow connection to the COM port established through the USB lead.
You shouldn't have any problems performing the procedure based on this information.

Hey Artstar,
Thanks for the info. After you mentioned the process you used (the same CF Auto Root package) I was more confident that wasn't the problem.
I have just successfully rooted using the same process as previously, except for waiting to be sure that COM was established (yellow COM box), and I also did install Kies for the USB drivers just to be sure (then uninstalled Kies).
The only thing now is that I get a message when trying to use Triangle Away (Play store version), it says "Could not find hidden partition. Are you not using ICS?" How did you get around that? I have not upgraded or done anything to the phone, it's still running Android 4.1.1.

How did you go?
I just got the note 2 LTE as well and want to root it.

Hey shawn, everything is a-okay now as far as the binary count goes... There have since been a couple of updates to Triangle Away and one of them was for compatibility with GT-N7105T (which is the model I have). So I ran Triangle Away and there were no problems there since the update. Although I haven't actually checked the binary count myself... but I got to the stage where I would rather have root, I didn't really care about the counter.
Depending how badly you want to root, you may just want to go ahead. There shouldn't be any problems there (just make sure you use a compatible package/method for your phone). However if you want to still get back to warranty you might want to double-check your exact phone model with some others who've rooted the same phone. (I'm not sure how many different models of LTE Note 2's are out there.)
Hope that helps!

[Q] Bricked, and Broken (mentally)

Hello internet, I'm a noob, so excuse my noobiness. Basically, I've managed to "brick" my SGH-T989D, also known as a Samsung Galaxy S2X, or Hercules; I'm on the Koodo network, and using 4.1.2 which I acquired from Kies. I was attempting to flash TWRP to achieve root using Odin as suggested by this website:
http://www.androidayos.com/2013/04/29/root-t989dtlumc4-samsung-galaxy-sii-sgh-t989d-teluskoodo-jelly-bean-4-1-2/
I followed the instructions, but Odin failed in the middle of the flashing. Now I'm stuck with this screen (not my picture):
{
"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"
}
One of the attachments is a screen shot of my "About Device" information from before I was bricked. I've tried flashing multiple stock ROMs through Odin, typically with a name similar to "T989DTLUMC4_T989DOYBMC4_KDO", but it consistently fails. The point at which it fails varies, and I'm not confident about what's causing the failure, but I've noticed it tends to hang up on "<ID:0/003> SetupConnection..", or fails at "<ID:0/003> Complete(Write) operation failed.". I'll attach a screenshot of what Odin looks like upon failure with the message box clearly visible. I don't have any recovery files, because, ironically, I was bricked while flashing a recovery to prevent bricking. Also, I'm open to trying things other than Odin.
I'd like assistance to get my phone back to a usable state (at least able to make calls, and text). I would be especially grateful if it ended up rooted, and/or with a safe method of flashing, and trying custom ROMs (I eventually wanted to have Cyanogen mod 10.1, and Clockworkmod Recovery). However, any help is appreciated; Thank you for your time.

TRY
You need to search for ODIN version 1.85... hard to tell what you're using but it looks very different from mine. ill try to attach a good copy of it. The one i used was nice.
In the mean time... have you gone into Kies and at the top select "tools" and "emergency recovery" or somethign similar to those words? that WILL restore your device to a usable state... that's guaranteed.

Droid8Apple said:
You need to search for ODIN version 1.85... hard to tell what you're using but it looks very different from mine. ill try to attach a good copy of it. The one i used was nice.
In the mean time... have you gone into Kies and at the top select "tools" and "emergency recovery" or somethign similar to those words? that WILL restore your device to a usable state... that's guaranteed.
Click to expand...
Click to collapse
Hey! thanks for the reply. I was using Odin v3.07. I have a couple of screenshots for you. Kies wants me to provide a recovery code (screenshot), which is not given to me. I believe that option only works if your phone was bricked while updating using Kies. Also, Kies doesn't seem to be connecting to my phone. It never advances from the connecting screen (screenshot), and seems to give up when I navigate to different menus. This is probably due to the current state of my phone. Lastly, I downloaded Odin v1.85, but the flashing failed with a similar error (screenshot). I hope you have more ideas.

IT WORKED!! (screenshot) I don't know what's changed since the last time I tried it; why is Odin so inconsistent? Regardless, thank you to Droid8Apple, and XDA forums. There is a lot for me to learn in unlocking the potential of my android device.

Coltonkoop said:
IT WORKED!! (screenshot) I don't know what's changed since the last time I tried it; why is Odin so inconsistent? Regardless, thank you to Droid8Apple, and XDA forums. There is a lot for me to learn in unlocking the potential of my android device.
Click to expand...
Click to collapse
You have to make sure Kies is disabled before using Odin, it'll cause Odin to either not recognise or fail.
T989D
latest CM10.1
latest Uber nightly

noob41 said:
You have to make sure Kies is disabled before using Odin, it'll cause Odin to either not recognise or fail.
T989D
latest CM10.1
latest Uber nightly
Click to expand...
Click to collapse
Thank you for the advice; I'll certainly remember that. By disabled do you mean simply closed (clicking the red "X" at the top right), or is there something further I need to do like kill processes in the task manager, for example?

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?