Develop Bugs

[Q] Can you unroot without using a PC?

I'm new and I hope I'm not posting this in the wrong place or re-posting an old question, but I have been searching on this and other sites for days and haven't been able to find anything pertaining to my question, so sorry in advance If I'm not posting this correctly.
I have a rooted epic touch with rogue boot loader installed and UnNamed rom installed. I really liked the way it was running until I had some kind of malfunction happened and now the battery charge light won't shut off and the battery drains within a couple hours of standby time. the phone is only a couple months old and would like to take it to the sprint store as I'm assuming this is an obvious hardware issue. My problem is that my pc doesn't recognize my phone anymore so I can't flash back to stock and get rid of root, voiding my warranty. I have tried uninstalling and reinstalling kies and stand alone drivers multiple times with no avail. I've tried with the battery and sd card removed and have also tried on multiple pc's (2 win7 and and xp machine). every time it says the drivers weren't installed successfully and to replace the device being connected.
My question: Is there a way to revert to stock off of the internal memory of the phone? I know there are zip roms you can flash from the boot loader but I was wondering if there was a way to flash a rom from zip and install the original boot loader as well as get rid of root? Any help I can get would be extremely appreciated and again I apologize if I am wasting anyone's time by asking in the wrong place or re-asking a question.

Ok so I downloaded the Calkin's_Stock_Rooted_EK02_ROM_v1.0 and got it on my sd card via dropbox. Flashed and now have a stock rom on it which I think is a step in the right direction.
The only thing is now I have clockwork boot loader and still rooted. and still not recognizing on pc. anyone know of an unrooted zip with original boot loader?

I couldn't get my PC to recognize either of my 2 E4GT's, each due to a different reason, both issues were resolved by going through each step in sfhub's debugging checklist:
sfhub said:
This post is for the FAQ section:
Why is the install stuck waiting for device to be connected?
Your phone isn't being recognized by your PC as an Android device.
When the drivers are installed and the phone is properly recognized, you should see the following in start->run->devmgmt.msc
Code:
Android Phone
SAMSUNG Android ADB Interface
Modem
SAMSUNG Mobile USB Modem
Until you get the SAMSUNG Android ADB Interface to show up, neither ADB nor this script will work.
Here is a debugging checklist:
1) dial ##UPST# (##8778#) in the dialer and verify AP (or ALL) is checked (if CP is checked, phone won't be recognized as an Android device)
2) restart the ADB server (choose Option G to stop the server, it'll get started automatically by the script)
3) verify USB Debugging is ENABLED
4) verify USB drivers are installed (Win7-64bit see below)
5) try a different usb cable
If you are in Win7-64bit try changing the default install location for the drivers:
If you see an error like this:
Try running the CMD prompt (or e4gtauto-sfx.exe) as Administrator. Right-click on the CMD icon (or e4gtauto-sfx.exe) and select "Run As", then select Administrator.
If that doesn't work, try disabling windows firewall.
Click to expand...
Click to collapse

I went down that list and everything seemed to be in order but still no recognition by pc. I kept uninstalling and reinstalling the drivers and switching usb ports and it finally installed the drivers successfully long enough for odin to recognize it and to flash back to stock. As soon as it was done the machine stopped recognizing it again. Lucky break I guess. So I can now return it to sprint and deal with the hardware issue.
I would still like to find a zip file like the tar that I flashed that installs stock recovery and non rooted ek02 rom and kernel from cwm, if that's even possible.
Thanks Godswrath, for helping me out.

You could use wifi explorer to get files on to sd card and mobile Odin to flash the tar file back to stock....
Sent from my SPH-D710 using xda premium

Lol....I am a noob.
They make a mobile Odin? That would have saved my like 4 hours....

Stuck in Download Mode

Hello,
I wanted to install a non-official lollipop rom on my brand new s4 mini, so at first i rooted it, so i followed that tutorial : android.stackexchange.com/questions/54074/how-to-root-samsung-galaxy-s4-mini-lte-gt-i9195.
Everything goes right until i discovered that i didn't have the recovery mode on...(number 8 of the tutorial)
Everytime i try to put my s4 in Recovery Mode, the Download Mode was starting, i don't understand why.
I tried in an another laptop with Kies 3, same problem.
Now i come back to my own laptop, but there is an other issue, the cellphone only start in download mode (even if I want to start it normally), here is the screenshot : img11.hostingpics.net/pics/757584galaxys4.jpg (sorry, i don't have the right to put some external links on my messages for now)
Plus windows doesn't recognize him, even if i delete and install samsung usb devices drivers, there is no way that windows dectects my cellphone.
Is there a way to put the original ROM from the factory or a way to avoid this "Download mode issue" ?
Thanks a lot

You must flash stock firmware. It seems the recovery on ur phone is messed up. Try using another pc. Also do not use files or instructions posted outside xda. They are not reliable.

sasank360 said:
You must flash stock firmware. It seems the recovery on ur phone is messed up. Try using another pc. Also do not use files or instructions posted outside xda. They are not reliable.
Click to expand...
Click to collapse
Ok, thanks.I'm brand new in Samsung's world. Do you have any links or so to guide me please ?

How to root Samsung Galaxy S4 Mini LTE GT-I9195T
USB driver
CF Auto Root for Samsung Galaxy S4 mini LTE
Credits :XDA, Rajesh Patel, Chainfire

Thanks a lot for the links, but the problem is that my S4 mini isn't recognized on my laptop, and like i said, it's stuck in Download Mode and Odin doesn't give a **** about my phone, so i cannot access to step 5.
The screen is fixed and it's written in red :
"Could not do normal boot. ODIN MODE"
[...]
In blue : "SECURE DOWNLOAD : ENABLE"
DOWNLOADING... DO NOT TURN OFF TARGET !!
I really don't know what can i do

Repeat the procedure of uninstallung and reinstalling usb drivers. But reboot ur pc in between. Then remove battery from phone..wait for one or two minutes and reinsert. Now boot to download mode using button combo. Vol down+ home + Power. Connect to pc at different usb port and start odin as administrator.
Hopefully it should recognise.

It doesn't change a thing unfortunatly...I seriously have a strange behaviour...I don't understand why windows doesn't recognize my cellphone, specially when i'll do all what you told me
There is no way to make my PC recognizes my phone ? I don't understand why, by default, he's starting in download mode...

krovomi said:
It doesn't change a thing unfortunatly...I seriously have a strange behaviour...I don't understand why windows doesn't recognize my cellphone, specially when i'll do all what you told me
There is no way to make my PC recognizes my phone ? I don't understand why, by default, he's starting in download mode...
Click to expand...
Click to collapse
What else does the download mode say ? Does it say something like " KNOX WARRANTY VOID 0X1 "
Do you have warranty ? If so then take ur phone to service centre and tell them there was power failure while samsung kies was updating ur phone to latest software.
Hopefully they will fix it free of cost [if u have warranty]

I made a link on my first message (but i have less than 10 messages so the link policy tell me that i cannot post a link with the link tag, anyway here is a snapshot of my phone : img11.hostingpics.net/pics/757584galaxys4.jpg

I know this is an old thread, but still, did you ever fix this problem? I'm having the same issue. The device is not seen at all by my pc when connected, with or without drivers. Therefore no way of flashing or installing anything from the computer.

[Solved] Bricked while downgrading

Hi,
I tried to downgrade my i9000 and now it's only showing the soft brick sign.
I used to run CM11 with CWM before I decided to downgrade to stock.
I connected the USB cable then used Odin with the same PIT file that I initially used to install CWM. I guess so far so good as it recognizes something on the COM port associated with my USB entry and the background turns yellow.
I have picked the 3 stock files that match my model (GT-I9000M), went in downloading mode and hit Start.
Odin reports that successfully checks the files, then right after "SetupConnection" it ends with Success 0 / Failed 1.
I just do not get farther than that. There is no action in the square above the COM port and there is no other message. The phone remains in Downloading mode and there is no progress bar displayed. at any time.
Anybody can make any suggestion on how to fix it?
When do I know it's totally bricked?
Many thanks.

Until it still goes to downloading mode it is not bricked. This has happened to me once when i tried to go back to stock using odin and odin said it was connected but will say failure after setting up connection my problem was that Virtual box for ubuntu was preventing the phone from being fully connected.
The main problem is that maybe your usb connection in your computer might not be fully recognizing the phone
so try different usb port, open odin in administrator mode, and continue trying it until it works
usually when i use odin i keep the computer as still as possible until flashing has been done completely.
Also are you using the right files because that could be a problem.
Here is the video I originally used to teach me to odin back to stock but its for the samsung vibrant but the procedure is the same
https://www.youtube.com/watch?v=l3K9my9kAvI
Hope i helped

Thank you for your message. You were right, the problem came from USB, specifically from the driver and OS, I guess.
I failed to flash it on Win7 and Win10, as described above, then I told myself I will give it a try on a XP machine (32 bit). It worked like a charm, first attempt.
Regards.

SM-P607T charges but will not connect to any PC - won't even try

I have an SM-P607T with an active T-Mobile plan - though I bought it from a third party then added it to my account. Previously everything worked fine, as I tried CM and a few ROMs on it, but ultimately went back to stock TMo ROM, 4.4.2, and just rooted it. Hadn't used it in awhile, grabbed it and thought I'd update to official Lollipop build.
First off, I disabled SuperSU and tried to apply the 4.4.4 update, assuming after that it'd offer me 5.1.1. Applying the 4.4.4 update failed. I factory reset the device in recovery mode (stock recovery), which of course fully removed SuperSU. Still fails updating. I downloaded the Lollipop ODIN tar, and that's where I started running into showstopper issues.
When I plug in a USB cable from a PC, the tablet starts charging, and that's it. There is no sign in windows that a device has been connected, no ding that something has been attached, no driver search. I tried this on 3 Win10 PCs. On all of them I installed Samsung Drivers, and even installed Samsung Easy Switch (new KIES). It would never register that it was plugged into a PC. I tried plugging my Note 4 in, registers and works fine (I read a thread on here by someone saying Win10 wouldn't recognize Samsung devices - not the case for me, phones work fine, just the tablet that won't show up). There is NO driver issue because the system never acknowledges anything is connected at all. I tried 3 PCs and 4 USB cables. I tried Samsung Easy Switch/KIES device recovery - tried putting tablet in download mode and tried putting it in recovery mode; neither ever shows up on PC. I tried using ADB, does not show up in devices (I have USB Debugging checked, Unknown Sources checked, etc etc).
I downloaded the Lollipop ODIN tar.md5 and put it on the microSD card. I loaded stock recovery, chose to flash from external storage, selected the .tar.md5, it said it was flashing it, said it flashed successfully even. Rebooted and it hadn't flashed at all.
Does ANYONE have ANY idea how to get my tablet updated? I can handle not being able to connect to PC, but I want to at least get OTA updates working. Factory reset, apply 4.4.4 OTA, fails after reboot every time.
Help?!

I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.

Hi i have a similar problem as you, my Note is the SM-P600 that I rooted and has TWRP v2.8.7.0 and last time I went into recovery, the thing came up with a stock red upper left hand side text say "recovery in not seandroind enforcing" then ended up with the "Firmware upgrade encountered an issue please select recovery mode in kies and try again" but the damn thing will not connect. 2 usb 3 ports and 2 usb 2 ports multiplecables- anker, samsung you name it-musical ports, tried right clicking the 4 usb port hubs and unchecking power saving in power mgnt- nothing- yet my the usb drivers see my note 4 just fine, in device mngr, the note tablet shows up in usb at the bottom as samsung device, I am just perplexed as to how to un**** this thing. If you have any suggestions and can let me know I'd appreciate it.
bigillz said:
I have an SM-P607T with an active T-Mobile plan - though I bought it from a third party then added it to my account. Previously everything worked fine, as I tried CM and a few ROMs on it, but ultimately went back to stock TMo ROM, 4.4.2, and just rooted it. Hadn't used it in awhile, grabbed it and thought I'd update to official Lollipop build.
First off, I disabled SuperSU and tried to apply the 4.4.4 update, assuming after that it'd offer me 5.1.1. Applying the 4.4.4 update failed. I factory reset the device in recovery mode (stock recovery), which of course fully removed SuperSU. Still fails updating. I downloaded the Lollipop ODIN tar, and that's where I started running into showstopper issues.
When I plug in a USB cable from a PC, the tablet starts charging, and that's it. There is no sign in windows that a device has been connected, no ding that something has been attached, no driver search. I tried this on 3 Win10 PCs. On all of them I installed Samsung Drivers, and even installed Samsung Easy Switch (new KIES). It would never register that it was plugged into a PC. I tried plugging my Note 4 in, registers and works fine (I read a thread on here by someone saying Win10 wouldn't recognize Samsung devices - not the case for me, phones work fine, just the tablet that won't show up). There is NO driver issue because the system never acknowledges anything is connected at all. I tried 3 PCs and 4 USB cables. I tried Samsung Easy Switch/KIES device recovery - tried putting tablet in download mode and tried putting it in recovery mode; neither ever shows up on PC. I tried using ADB, does not show up in devices (I have USB Debugging checked, Unknown Sources checked, etc etc).
I downloaded the Lollipop ODIN tar.md5 and put it on the microSD card. I loaded stock recovery, chose to flash from external storage, selected the .tar.md5, it said it was flashing it, said it flashed successfully even. Rebooted and it hadn't flashed at all.
Does ANYONE have ANY idea how to get my tablet updated? I can handle not being able to connect to PC, but I want to at least get OTA updates working. Factory reset, apply 4.4.4 OTA, fails after reboot every time.
Help?!
Click to expand...
Click to collapse
---------- Post added at 11:04 AM ---------- Previous post was at 11:02 AM ----------
I am confused what you mean by calculator, I am on Win 10 and have a similar problem, my Note is the SM-P600 that I rooted and has TWRP v2.8.7.0 and last time I went into recovery, the thing came up with a stock red upper left hand side text say "recovery in not seandroind enforcing" then ended up with the "Firmware upgrade encountered an issue please select recovery mode in kies and try again" but the damn thing will not connect. 2 usb 3 ports and 2 usb 2 ports multiplecables- anker, samsung you name it-musical ports, tried right clicking the 4 usb port hubs and unchecking power saving in power mgnt- nothing- yet my the usb drivers see my note 4 just fine, in device mngr, the note tablet shows up in usb at the bottom as samsung device, I am just perplexed as to how to un**** this thing. If you have any suggestions and can let me know I'd appreciate it.
shineliu said:
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Click to expand...
Click to collapse

shineliu said:
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Click to expand...
Click to collapse
thank you very much. it worked.

Dead SM-605??

Hi All, sorry this is a fairly long post.
i recently "Upgraded" my SM-P605 to Android 9 and it has been working fine.
i have, however, been experiencing connectivity issue with file transfer via USB.
i have tried several cables (3 Genuine) including a brand new "Generic" cable and keep getting the "device descriptor request failed" error.
i have also tried multiple PC's, loaded all recommended Samsung drivers and finally relented and replaced the USB port in the tablet itself, which still did not fix the problem.
Convinced after all of this it must be software related, i then decided to re-install and earlier version of Android which i copied over to the Tablets internal memory.
i logged into TWRP and wiped the tablet ready to reinstall Android 7. and when i tried it says the zip file is corrupted.
i now have a tablet that wont load the zip file i have, wont read from an SD card in the tablet or OTG (via TWRP) and is unable to connect to a PC via a usb cable..
if anyone could offer any suggestions i would be extremely grateful as i dont want to "Dump" this tablet as i use it daily for work..

Why it does not read the SD card? I would expect that should work and should be the safest bet here...

-Maybe the zip file really is corrupt, which can be easily told by unpacking via pc.
-If the tablet can still charge the battery usb is most likely okay.
-Sdcards can fail by becoming read-only. Most easy to tell by unsuccessfully trying to format them in the tablet or pc , but e. g. under Windows you seemingly can successfully delete and copy stuff, everything as it should even after forced refresh via F5. But after reinserting the card or rebooting the previous state is back.
-ADB has been enabled in developer settings? Then you normally get a notification where you can modify usb mode. Charge-only won't work, but most of the rest should do (Dcim/mtp/msp...) .
-And all the time Windows has to recognize the device via PnP and auto-install drivers for the current usb mode. Besides the aforementioned storage drivers for flashing and communication a modem driver and virtual COM ports must be auto-installed.
In this department i had lots of trouble with a phone based on an old TI OMAP SoC under any Windows newer than seven. Only Download mode invoked on the phone itself was still working and only zseful to restore stock rom, while in the more flexible Fastboot mode the phone wasn't recognized by Windows.
Samsung devices seem to support Fastboot only, but call it Download mode.
To come to an end, if everything fails i'd recommend to install stock rom in "download recovery" (Fastboot?) mode via Kies. If this also fails try to put the P605 manually into Download mode (Power and Volume minus or plus), no need to press home button, as often advised. After this, work your way back to Twrp, custom rom and root.

@crwzar80
Try connecting the tablet to a Windows 7 PC/laptop, making sure it's on an Administrator account (so it can autoload/download needed stuff). Not Windows 10 or even 8.1, but Windows 7.
I had the same problem a while back ago; if your attempt with this method succeeds then report back; I had an unconfirmed hypothesis about this issue.