Related
Hi.
I don't know much about details about root/room/recovery, but know some about
ODIN, CWM and other ROM to use.
I've been using Humble 5.0 for a while and my phone got unstable recently, so I ODIN the same Humble rom again, but that is how the problem started.
The main problem is, I can't wipe userdata or cache at all.
CWM says it wiped, but I always get Force close, so many that I can't even use the phone normally.
I tried to go back to stock ROM or any other, but all failed.
Stock ROM with stock recovery says, E:Can't mount /dev/block/mmcblk0p1 (Invalid argument). and most of the time, Bootloops.
Humble is the only option I can go into, and actually use the phone, but it has all the apps and data from the past, even though I wipe data/cache thousand times.
I even erased all SD data, formatted in FAT32, and nothing works.
Finalizing my status,
Can't mount...error with Stock ROM.
Bootloop with other ROM.
Constant Force Close with Humble 5.0 (Can't wipe data/cache).
Please help.
So stock, you used ODIN EE4 and PIT file to go back to stock and took the newest update and still have problems?
Thank you for the reply.
Yes. I tried ED1 and EE4, and even with PIT(repartition) and I get "Can't mount..." error.
I went back to Humble 5.0 which has all kind of force close (still showing all app names I had, mysterious), and formatted SD, factory reset, and tried ODIN ED1/PIT, but result is same.
I have a feeling my internal SD partition got screwed.
I am no pro myself.. But I am running GummyCharge Froyo 2.0 which comes with Imoseyon's Kernel and its rock stable even overclocked to 1,200 mhz for me.. You may want to try getting a copy of that as well as flashing with your SIM Card out and Battery in after booting into recovery.. Let me know if this helps at all!
jiehooni said:
Thank you for the reply.
Yes. I tried ED1 and EE4, and even with PIT(repartition) and I get "Can't mount..." error.
I went back to Humble 5.0 which has all kind of force close (still showing all app names I had, mysterious), and formatted SD, factory reset, and tried ODIN ED1/PIT, but result is same.
I have a feeling my internal SD partition got screwed.
Click to expand...
Click to collapse
I had a similar problem but dont remember what I did to fix lol like that helps you. Did you format your sd card on a computer or with your phone? If not try using an adapter and format on computer. Going back to stock has always solved my problems. There is a new cwm that came out. Just throwing stuff out there. Have you tried re downloading images of the stock ee4 and pit? It is loading so shouldnt be a problem , hmm. Maybe someone with more knowledge will pop in.
I tried GummyCharge 2.0.zip from SD but it didn't help.
I tried CWM 5.0, with many ROMs to wipe cache/data, no use.
I formatted my SD on PC, and from phone, same result.
What I don't understand is, even after I flashed Humble 5.0 ROM which I used right before, and only ROM it works now, it shows all apps I had even after many times of Wipe Data/cache/dalvic.
Even funnier, I delete some apps causing Force Close, and I reboot my phone, it always goes back to where I start. Same Home, the app is still there.
It is just weird.
Im getting FC now all of a sudden. It's you fault damn it lol. Said I was gonna reload anyhow. Just didnt want to do it twice in one night. Oh it is past 12pm so I guess it is another day.
It's been now 3 days, and I found this thread hopelessly.
Same problem I think.
http://forum.xda-developers.com/showthread.php?t=1191650&page=2
I hope somebody can help me fix it.
Now I can't even flash Humble, can't even get through recovery(stock or CWM).
I can't do anything now.
I will Odin back to stock and take it to the verizon tomorrow.
Thank you all of you for the help.
Tried a different usb cable, how did you flash the new cwm? So everytime it says pass through ODIN? Are you checking the right selections through ODIN and using PDA? Man just trying to think of everything and thats about it. Get another phone lol. Superuser and busybox?
I tried different USB cable, PC, installed Samsung driver again.
I took the phone to Verizon today, and they can't hard reset it either at that place.
I dropped the phone 3 month ago and it has a little dent, so that they refuse to repair it under warranty. I am sending it to MobileTechVideo tomorrow.
Thank you.
I'm having the same issues. I was on Humble 5.0 and had been using it without a problem for about 2 weeks and yesterday I noticed my phone reboot on it's own. After the reboot it was stuck in the boot loop. I've also tried reflashing Humble 5.0, tried the instructions on the fix your phone thread, tried flashing to stock and also tried the all in one Gingerbread 2.3.6 W/Root/CWR/IMO Kernel 4.0 to see if CWM would help any.
All successfully pass according to Odin, but they all still boot loop and all give error messages in their recovery modes if I try to do anything involving /cache or /data stating that they fail to mount.
Any thoughts would be greatly appreciated.
Okay, I started this thread with the issue of not being able to root. I bit the bullet and wiped it all and ended up being able to root. Now I have a much bigger issue... My phone wont go into storage mode. Not in the OS, not in CWM, not in download mode. It just can't be recognized by a computer. Yes I have the drivers installed, and the phone knows it's plugged in, it will charge and everything, it just wont give me the option to go into storage mode. This will be an issue if I ever need to flash it for any reason since download mode can't be recognized in ODIN. It was working a day ago... Think it's a hardware issue?
JoeVsFox said:
Okay, I started this thread with the issue of not being able to root. I bit the bullet and wiped it all and ended up being able to root. Now I have a much bigger issue... My phone wont go into storage mode. Not in the OS, not in CWM, not in download mode. It just can't be recognized by a computer. Yes I have the drivers installed, and the phone knows it's plugged in, it will charge and everything, it just wont give me the option to go into storage mode. This will be an issue if I ever need to flash it for any reason since download mode can't be recognized in ODIN. It was working a day ago... Think it's a hardware issue?
Click to expand...
Click to collapse
Storage mode and download mode are different to me atleast.
Have you tried settings/usb settings/ask on connection.
When you connect your usb cable from your computer to your phone it should beep and then ask what you want to do. Is your sd card good? Have you checked it maybe on your computer with an adapter?
Or are you talking about getting into ODIN?
Have you usb cable connected to the main usb port. Pull the battery,put it back in, connect the usb cable , hold the volume down button and power key. Worked every time for me. Not sure what else to say from me atleast. Someone else might chime in. Ive done it both with the battery and with out. Try a different usb port.
ODIN Flash Stock
blueis300 said:
So stock, you used ODIN EE4 and PIT file to go back to stock and took the newest update and still have problems?
Click to expand...
Click to collapse
If you have the charge pit file and EE4 you should be able to wipe everything on your phone. If I am correct, this bypasses all permissions and partitions and basically supercedes any roms or data you have. This should work. try another cable on a different usb port or another computer. I have hard brocked my phone numerous times and this was the only workable method. (if you want you can do a little solder job and have phone by fixed with the unbrickable mod here
I already sent my phone to the repair shop.
Btw, it is the normal case you described, but I tried different PCs, drivers, cables, USB slot, nothing works.
Thank you anyway.
blueis300 said:
Storage mode and download mode are different to me atleast.
Have you tried settings/usb settings/ask on connection.
When you connect your usb cable from your computer to your phone it should beep and then ask what you want to do. Is your sd card good? Have you checked it maybe on your computer with an adapter?
Or are you talking about getting into ODIN?
Have you usb cable connected to the main usb port. Pull the battery,put it back in, connect the usb cable , hold the volume down button and power key. Worked every time for me. Not sure what else to say from me atleast. Someone else might chime in. Ive done it both with the battery and with out. Try a different usb port.
Click to expand...
Click to collapse
Tried it with 2 different computers, different cables, different ports. Ask on connection is on. The SD card works fine when I put in in an adapter. The phone just doesn't data connect via usb. ODIN can't find it. Nothing. Pretty sure this is a hardware issue...
My phone just got back from the repair shop and they say they can't fix it. They think NAND got corrupted. Now I am really stuck...Man...
So I have an interesting little problem.
A few days ago after flashing Infinity ROM i noticed that when I plug my phone into my computer by USB, instead of reading the device correctly and matching/installing drivers I get an error message that says "USB device has malfunctioned" and is not recognized. This is a problem because I can no longer use ODIN to flash anything, it simply does not recognize my phone.
I have attempted to troubleshoot the problem myself by replacing the usb cable, uninstalling / reinstalling the drivers, resetting data and caches on my phone, using different computers etc.. So far nothing as helped. I would go so far as to guess that the USB controller in my phone is malfunctioning, but I can still charge my phone.
So I called verizon because my phone is still under warranty and they are going to ship me a replacement, so now my problem becomes how do I get back to stock or anything resembling stock so I don't void my warranty when I send this one back in.. remember I cannot use ODIN, and I am currently on the ext4 file system. Someone even suggested purposely bricking my phone, although I'm not sure how i would even pull that off. Thoughts? I'm still open to troubleshooting if anybody has any ideas.
Any ideas or help would be GREATLY appreciated!! Thanks!
In Summary:
Summary for those who think the first post was tfltr..
--Computer won't recognize phone through USB; device not recognized
--Phone will still charge but only with certain cords??
--Have troubleshooted through XDA boardsn
--Waiting on a replacement from Verizon
--Need to get phone to stock or close to stock for when I send it back in so i do not void warranty
--Is there a way to zip flash stock, even though I am on ext4 ow??
--If not, should I just brick my phone and then send it in?
Thanks bros!
If you get into download mode, your phone should be fine. If you get into download mode, go ahead and make sure everything else works. Use USB ports on the back of the computer, and try different ports. Try different cables. Try reinstalling drivers.
Sent from my SCH-I510 using XDA App
Also, try cleaning out phone USB port and inspect for damage. Keep in mind that many cables don't work. I have several crummy cables that I can't get data through on the Charge
Sent from my SCH-I510 using XDA App
Bleh..
xdadevnube said:
Also, try cleaning out phone USB port and inspect for damage. Keep in mind that many cables don't work. I have several crummy cables that I can't get data through on the Charge
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Thanks for the response, but I have tried several official verizon USB cables to no avail. I just received the replacement charge which works on the same computer port and with the same cable that was definitely not working with the old phone. I will try compressed air when I get home later.
Does anybody know what would happen if I attempted to flash a stock recovery image with RFS as a filesystem through CWM, on the phone which is currently running an EXT4 filesystem? Would I brick it?
I'm not sure, but that seems like a poor way to going back to stock.
Just use the stock ODIN images. They will take care of all your needs. I've used them on multiple occassions.
Format your SD card first so that Verizon doesn't know you were rooted, etc. I usually do this through USB mass storage when its connected to the computer, but since you probably can't get it through the computer, either pop in your SD card into your other phone and do it through mass storage or simply use a memory card reader. I format with FAT32 /w 32KB block size.
Then just ODIN the stock recovery image and there you go.
*EDIT* der, I just realized you can't get the USB to work. This is a question for somebody who knows more than I do!
I'm not sure if this is possible with that rom(doubtful) but try disabling lagfix by creating a file on your sdcard inside the Voodoo folder, named "disable-lagfix"(may not even be a folder for this). Reboot. If you hear the voice again maybe it worked.
Does Imo kernal support reverting? If the above doesn't work(or try this first) flash the Imo 4.0 Kernel and try reverting. NOT sure if that kernel is compatible. Try all this at your own risk.
then cwm flash this:
http://forum.xda-developers.com/showthread.php?t=1108115&highlight=cwm
I recently picked up a Pantech Burst phone from At&t, and upgraded to ICS. I then proceeded to root the phone using the prestoroot.img method and it worked. Everything was running dandy until I got the VM Heap tool app and(stupidly) set the vm heap to 52m and attempted to reboot... It failed and all I got was a loop of boot up animations. I tried several times to reboot, and then tried to boot to recovery mode and factory reset. That worked, but it STILL didnt reboot..! I dont have a backup, and whenever i try to " Install update from external storage", it just fails over and over again. I found thestock firmware and downloaded it to my external sd card and install(still to no success). Im only 13 and cant afford a new phone! PLEASE SOMEONE HEEEELLLLPPPPPP!!!!!!!!!!!!!
Use P9070_Download_Tool_v3.3.zip and flash PRESTO_BIN_JUUS09032012_TP20_user using this method http://forum.xda-developers.com/showthread.php?p=28602800#post28602800. You might find other answers in that same thread Pantech Burst Essentials.
I love you!!!!!!!
dvinelord said:
use p9070_download_tool_v3.3.zip and flash presto_bin_juus09032012_tp20_user using this method http://forum.xda-developers.com/showthread.php?p=28602800#post28602800. You might find other answers in that same thread pantech burst essentials.
Click to expand...
Click to collapse
it workkeed!!!!!:d
DvineLord said:
Use P9070_Download_Tool_v3.3.zip and flash PRESTO_BIN_JUUS09032012_TP20_user using this method http://forum.xda-developers.com/showthread.php?p=28602800#post28602800. You might find other answers in that same thread Pantech Burst Essentials.
Click to expand...
Click to collapse
I bricked my phone few days back doing restore from CWM 6 downloeded online from ROM manager,
I wiped cache dalvik etc & rebooted, I could see the Tap the android screen then suddenly blank now it wont start
I get QHSUSB_dload in PC device manager any way out
I tried this method but I dont get the download button to click it remains greyed out.
Is there any driver for QHSUSB_dload?
Or do I have no hope at the moment or in near future?
just don`t use ROM manager for installing recovery . usually the result is bricked phone
Yah, i remember a fastboot brick i got from rom manager (LG Optimud ME)
Sent from a 2.8 inch screen
I also just bricked my Pantech Burst the same way...using ROM Manager. Is there a way to fix this or am I out of luck? I did try the method posted at the top of this thread. It just gets locked in the S/W Upgrading screen. Any help will be greatly appreciated.
I'm too in same situation.....i tried it updating via Pantech OS Upgrade tool......it updates successfully but doesnot bootup....
and now it shows some S/W Upgrading with red colour background
plz help me out:crying::crying::crying::crying::crying:
coolamjadkhan said:
I'm too in same situation.....i tried it updating via Pantech OS Upgrade tool......it updates successfully but doesnot bootup....
and now it shows some S/W Upgrading with red colour background
plz help me out:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Mine did not upgrade successfully, but I have the exact same problem. On day three of waiting for a callback from Pantech on the issue. They are supposedly talking to the techs in Korea about it.
Maybe solved!
tajlund said:
Mine did not upgrade successfully, but I have the exact same problem. On day three of waiting for a callback from Pantech on the issue. They are supposedly talking to the techs in Korea about it.
Click to expand...
Click to collapse
Don't know if this is going to help, but I had the problem (as I described) red S/W Upgrading and couldn't do anything. Well, after about two weeks of sitting with the battery out, I decided to redownload and rerun the Pantech update app, and lo and behold, it fixed my phone. It also installed a more up to date version of Android 4.0, I went from 4.01 to 4.04.
This is after running the updater a good 30 or so times the past two weeks hoping for anything to work, now today, bam, it works fine.
I would recommend anyone in this situation give the most recent updater a try, it may solve your problem.
need help with my burst!!!!!
Hey! i have a pantech burst and i love it! but i had to reset it and now it wont work. my exhusband root it a few months ago....and he deleted the keyboard and the launcher..... so.... when i turn it on i cant do anything cause i cant write .... and if i skip the android start menu i cant see anything cause i dont have a launcher.... please someone help! what can i do?
:crying: Bricked my phone total unable start. any hardware diagnostic tool or manual reset button.
please help urgently
needhelppantech said:
Hey! i have a pantech burst and i love it! but i had to reset it and now it wont work. my exhusband root it a few months ago....and he deleted the keyboard and the launcher..... so.... when i turn it on i cant do anything cause i cant write .... and if i skip the android start menu i cant see anything cause i dont have a launcher.... please someone help! what can i do?
Click to expand...
Click to collapse
would you like to sell it cheaper rate???
Bricked Pantech Burst Stuck in S/W Downloading Mode and completely wiped ...
Ok I am having a similar issue guys. Last night I had to wipe my phone because it was overly full and I switched providers and the phone had become unusable. I tried using clockworkmod to do this and it wiped everything ( including clockworkmod. ) Now I only get a S/W Upgrading screen with a red box. I tried using the pantech download tool and the PANTECH_PRESTO_BIN_JUUS03122012.pdl file. It did appear that it was installing it but then it became stuck at the very very very end of things. I basically had to take the battery out to do anything at all as I had left the phone on all night to download the pdl file but without any luck.
When I reboot the phone it had the S/W Upgrading mode with the red screen. I've tried all of the different key combinations on the pantech burst etc volume up + volume down and power, volume down + power, volume up + power. None of these things will reboot the phone.
I am hoping I can use the pantech download tool to install a different pdl instead and possibly get it working that way. I know that when the phone is off if I plug it into usb then the screen lights up on it with the S/W Upgrading screen and the red box. If I press the power button or any other combinations of buttons + the power button it also does this. It literally will not do anything else.
I cannot use pantech pc suite because the phone originally was so unusable I could not put the android apk file on the phone even though I have it on my laptop.
I tried using adb and fastboot and it will not even find my device through ANY usb port on the laptop. I've tried deleting and reinstalling the drivers over and over. The only thing I know to do is reboot afterward and hopefully it will find my phone on usb with adb. If I can just get to a bootloader or flash functional firmware onto this phone I think I could get it working but I do not know enough about the pantech burst to try physically jumping anything on it in order to hard reset it.
So my only options right now look like maybe get a different pdl, possibly reboot and the drivers may find my phone, or JTAG this thing.
I can't put it in usb debugging mode because it won't boot. Since adb does not even find the device as being attached it seems as if this phone should be operating in a different port mode or something to make it visible. I could be wrong but I am hoping that rebooting fixes the driver issue and makes the phone visible.
I tried PDAnet also and once again it does not work because it cannot find the device. This could be a usb cable issue I suppose but I only have this particular cable I am pretty sure
I might try another cable as well...
Any other ideas ? Am I going to have to JTAG this thing or should it be fixable using the download tool and a different pdl ? Or do I need to find another way to completely wipe the phone first and THEN use the download tool with the pdl file ?
It does get a bit confusing with so many mods, roms, and methods to recover android phones. If I can get the phone to boot then I can reload my backups and all should be well. I do need this phone for business purposes also. Any ideas guys ?
PS> I am also pretty decent with linux distros like arch or ubuntu so I would like to also know if it would just be better to do this in linux and possibly use linux to manually switch the phone to a different device mode to make it visible in the instance of there being nothing wrong with the drivers.
Thanks for any ideas or suggestions ...
UPDATE - progress ???
dsull1981 said:
Ok I am having a similar issue guys. Last night I had to wipe my phone because it was overly full and I switched providers and the phone had become unusable. I tried using clockworkmod to do this and it wiped everything ( including clockworkmod. ) Now I only get a S/W Upgrading screen with a red box. I tried using the pantech download tool and the PANTECH_PRESTO_BIN_JUUS03122012.pdl file. It did appear that it was installing it but then it became stuck at the very very very end of things. I basically had to take the battery out to do anything at all as I had left the phone on all night to download the pdl file but without any luck.
When I reboot the phone it had the S/W Upgrading mode with the red screen. I've tried all of the different key combinations on the pantech burst etc volume up + volume down and power, volume down + power, volume up + power. None of these things will reboot the phone.
I am hoping I can use the pantech download tool to install a different pdl instead and possibly get it working that way. I know that when the phone is off if I plug it into usb then the screen lights up on it with the S/W Upgrading screen and the red box. If I press the power button or any other combinations of buttons + the power button it also does this. It literally will not do anything else.
I cannot use pantech pc suite because the phone originally was so unusable I could not put the android apk file on the phone even though I have it on my laptop.
I tried using adb and fastboot and it will not even find my device through ANY usb port on the laptop. I've tried deleting and reinstalling the drivers over and over. The only thing I know to do is reboot afterward and hopefully it will find my phone on usb with adb. If I can just get to a bootloader or flash functional firmware onto this phone I think I could get it working but I do not know enough about the pantech burst to try physically jumping anything on it in order to hard reset it.
So my only options right now look like maybe get a different pdl, possibly reboot and the drivers may find my phone, or JTAG this thing.
I can't put it in usb debugging mode because it won't boot. Since adb does not even find the device as being attached it seems as if this phone should be operating in a different port mode or something to make it visible. I could be wrong but I am hoping that rebooting fixes the driver issue and makes the phone visible.
I tried PDAnet also and once again it does not work because it cannot find the device. This could be a usb cable issue I suppose but I only have this particular cable I am pretty sure
I might try another cable as well...
Any other ideas ? Am I going to have to JTAG this thing or should it be fixable using the download tool and a different pdl ? Or do I need to find another way to completely wipe the phone first and THEN use the download tool with the pdl file ?
It does get a bit confusing with so many mods, roms, and methods to recover android phones. If I can get the phone to boot then I can reload my backups and all should be well. I do need this phone for business purposes also. Any ideas guys ?
PS> I am also pretty decent with linux distros like arch or ubuntu so I would like to also know if it would just be better to do this in linux and possibly use linux to manually switch the phone to a different device mode to make it visible in the instance of there being nothing wrong with the drivers.
Thanks for any ideas or suggestions ...
Click to expand...
Click to collapse
--------------------------------------------------------------------------
OK quick update, I found the pantech burst upgrade tool and the burst-hack.cmd script
I managed to successfully find my phone with the upgrade tool and it completely ran its course and I am guessing it installed Ice Cream Sandwich.
My new problem is that the phone goes to the pantech logo boot screen if I plug the phone into usb but that is all it will do. If I unplug the phone and try to get into S/W Upgrade mode again or power it on it will not do anything at all. Basically the display only comes on when plugged in at this point so I am wondering if the battery is even charged or if it will charge. I read somewhere ( in the gizmolord forum ) that a guy had the same issue as me and he ran this tool for his pantech burst and then left the battery out for 2 weeks and tried to power it back on and it worked for him.
Is it possible that I just need to power the device down completely and let it completely discharge before it will reboot or is this thing bricked ?
I am thinking that either the battery needs to charge, or the phone needs to discharge and power down completely, or the phone could be bricked. I have a feeling it is not bricked because the update tool said everything was successful and no errors or anything.
I will try leaving the battery out for awhile and letting the phone discharge on its own and see what kind of results I get. I would think that 16 - 24 hours would be sufficient. Any ideas ?
---------------------------------------------------------------------------------------------------------------------
Ok so I did a bit more digging and research and found out that the culprit is most likely the poorly designed charging circuit in the pantech phones. I found a tech blog called Mikes Techblog where he shows how to solve this on a pantech jest phone with the same issue. The problem is that the battery is 3.7v and is currently reading 2.8v on the volt meter. The phone will not even attempt to charge until 3.7v is available on the battery because of how the charge circuit is designed. I am going to try the usb cable trick and usb adapter and see if I can monitor its progress with the voltmeter and get it back up to 3.7 volts. After this it should allow me to charge it normally and should boot just fine. It is showing the pantech logo which tells me that the firmware is there and isn't buzzing or doing anything else weird so more than likely this is related to the battery and not having enough of a charge when running the official upgrade tool. This problem probably had already existed prior running the update tool and is why the S/W Upgrading screen only would come up AFTER being plugged into a power source and would disappear immediately. If the battery had any charge whatsoever and if the phone could see it then I would see a screen that tells me to plug my phone in and charge it. I am thinking this is solved but will only know after I charge the battery. From what I've been reading in comments from others the battery issue is prevalent on many different pantech phones including the burst model. Other people with the pantech burst have said in comments on Mike's blog that this made their phone boot right up and said that this was EXACTLY the issue. Perhaps the best way to use these pantech phones is to never ever let them fully discharge the battery.
So here's a doozy. First, some background. During a routine update to a new version of my favorite rom, IMEI data got borked. My backup was apparently incomplete, so couldn't restore it that way. My phone has been unable to connect a computer via usb in more than a charging capacity for a few months, so any pc-based tools like ODIN or QPST were out of the question. Only hope was to go back to a rooted stock rom and try the dialer solution. So I try flashing root66 via Mobile ODIN. Note that this overwrites CWM to the stock recovery, in addition to overwriting pretty much everything else. For whatever reason, the OS is now borked. Can't get past the Samsung GSIII screen. I can still reach Download Mode and Recovery, though. However, as mentioned before, ODIN is not an option because no computer can see my device over USB. The recovery is now the stock recovery, so the only thing it will recognize is a signed update.zip from Verizon herself. Anything else I try to flash from external SD gets the whole signature verification error.
To sum:
The Problem
Need to get to a working OS. This likely needs to be stock.
Complications and Constraints
ODIN is not an option, nor is any other pc-based or usb-based tool.
I'm stuck with the stock recovery, which requires signature verification.
Theorized Solutions
I could either somehow flash CWM via signed zip file from stock recovery (don't know if this exists, if it does I haven't been able to find it), or,
I could flash a signed OTA zip, like what would arrive on the phone from Verizon. I've been having a lot of trouble finding one of these, since everyone and their grandmother seems to want to use ODIN to flash leaked OTAs. I'm thinking that of the OTAs, the initial upgrade to JB is probably my best bet, since it likely replaced more of the system than the other OTAs. I'm more than open to suggestions, though.
Thoughts?
Boot into recovery and do a factory reset. That typically is recommended if you're stuck on the boot logo after an Odin flash.
How did you lose usb to pc access? When you install the Samsung drivers from their website, what does your computer do? Which usb cable have you been using?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Boot into recovery and do a factory reset. That typically is recommended if you're stuck on the boot logo after an Odin flash.
How did you lose usb to pc access? When you install the Samsung drivers from their website, what does your computer do? Which usb cable have you been using?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Factory reset was the first thing I tried. No go. I've tried every option available in the stock recovery, with no success. Gotta say, not really fond of this whole stock recovery thing. Fairly useless.
I haven't had usb to pc access ever since I played Ingress in a snowstorm a few months ago and some moisture got into the charging port, and I didn't properly dry it out. There's a little bit of corrosion in there now. It still charges fine most of the time (I'm sure not as well or as consistently as when it was new), but it can't connect to the computer in more than a charging capacity. I've tested a large variety of usb cables, most of which worked before the snowstorm, and none give me pc access. Some give me pc access for a few seconds, but none give a connection that's stable enough to run ODIN or QPST or the like.
I should note that I have a microSD to SD adapter, so I can still move files to and from my external SD card. Anything available on the internet can make its way onto my SD card so long as it's 7.96 Gb or smaller.
EDIT: I should clarify that I *did* have usb to pc access before the snowstorm. Samsung drivers worked fine, etc, the typical file transfers over usb worked fine, adb worked fine, etc.
I had the same problem a few months ago when I used mobile odin. I was lucky enough to be able to use the regular ODIN to start from the beginning flash stock everything. You need to get regular ODIN to work. Take the phone to a repair place have them clean the rust and re-soter the connections. That is what I would try. Sorry I wasn't of any more help.
Sent from my SCH-I535 using xda app-developers app
Lehocki said:
I had the same problem a few months ago when I used mobile odin. I was lucky enough to be able to use the regular ODIN to start from the beginning flash stock everything. You need to get regular ODIN to work. Take the phone to a repair place have them clean the rust and re-soter the connections. That is what I would try. Sorry I wasn't of any more help.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I took a closer look at the microUSB port on the phone. On closer inspection, with a bright light, I really don't see any corrosion, and I checked the water damage indicators, and none have been tripped. Which makes me question whether or not the port starting to fail really was related to the snowstorm, or if that was a coincidence. I've decided to just go ahead and get it replaced under warranty--even if I could rescue the system, that faulty port is actually a really huge problem, more so than I had realized. Not being able to use ODIN to un-brick is bad, I've decided. Now the big question is going to be, will they be able to tell the phone's been messed with, and if so, how can I cover my tracks with a bootlooped phone, stock recovery, and no possibility of Odin or Heimdall? I'm thinking it should mostly be okay--in Download mode, everything checks out as normal, except for system status, which says custom. I'm betting that if it came down to it, I could probably argue that it could fail to recognize a borked but otherwise stock system, and therefore call a normal system custom.
If not, though, then I better get started on cracking Samsung's update.zip encryption so I can sign my own injection package with their signature...
adiv.paradise said:
I took a closer look at the microUSB port on the phone. On closer inspection, with a bright light, I really don't see any corrosion, and I checked the water damage indicators, and none have been tripped. Which makes me question whether or not the port starting to fail really was related to the snowstorm, or if that was a coincidence. I've decided to just go ahead and get it replaced under warranty--even if I could rescue the system, that faulty port is actually a really huge problem, more so than I had realized. Not being able to use ODIN to un-brick is bad, I've decided. Now the big question is going to be, will they be able to tell the phone's been messed with, and if so, how can I cover my tracks with a bootlooped phone, stock recovery, and no possibility of Odin or Heimdall? I'm thinking it should mostly be okay--in Download mode, everything checks out as normal, except for system status, which says custom. I'm betting that if it came down to it, I could probably argue that it could fail to recognize a borked but otherwise stock system, and therefore call a normal system custom.
If not, though, then I better get started on cracking Samsung's update.zip encryption so I can sign my own injection package with their signature...
Click to expand...
Click to collapse
If using Windows the USB will act like there are no drivers at times. The fix I found was to connect to PC in charge mode. Then go to download mode while connected to PC. It will reactivate drivers from phone side. Have done this many times on Win8. Worth a shot.
prdog1 said:
If using Windows the USB will act like there are no drivers at times. The fix I found was to connect to PC in charge mode. Then go to download mode while connected to PC. It will reactivate drivers from phone side. Have done this many times on Win8. Worth a shot.
Click to expand...
Click to collapse
Some phone is bricked that not recognize the phone on device manager and won't charge too.
tomy1986.nt said:
Some phone is bricked that not recognize the phone on device manager and won't charge too.
Click to expand...
Click to collapse
His charges.That is not a brick. A brick is black screen with no access to recovery, download mode. A bricked phone will be seen by USB but just as a device and not as an S3. If you have the screens that is a soft brick and need to find what the problem is. Could just be a bad USB port on phone or PC or an operator problem. If have any screen the device is not bricked. Ok I see now. You are looking for JTag work and are in Texas. I would still say send to Josh at Mobile Tech in College Station, Tx cause we know he knows what he is doing. You don't have video of unbricking S3? S2 is old and obsolete and no where near the same device. Also must have RIFF for the device. I can make it pass warranty for free over PM.
prdog1 said:
His charges.That is not a brick. A brick is black screen with no access to recovery, download mode. A bricked phone will be seen by USB but just as a device and not as an S3. If you have the screens that is a soft brick and need to find what the problem is. Could just be a bad USB port on phone or PC or an operator problem. If have any screen the device is not bricked. Ok I see now. You are looking for JTag work and are in Texas. I would still say send to Josh at Mobile Tech in College Station, Tx cause we know he knows what he is doing. You don't have video of unbricking S3? S2 is old and obsolete and no where near the same device. Also must have RIFF for the device. I can make it pass warranty for free over PM.
Click to expand...
Click to collapse
You do not know how the bricked phone look like, some bricked like no power, some like download mode but can not flash firmware, some phone is bricked like wont recognize on device manager.
Please check my video for knowing what kind of device I have already done, and see my feed back on ebay.
tomy1986.nt said:
You do not know how the bricked phone look like, some bricked like no power, some like download mode but can not flash firmware, some phone is bricked like wont recognize on device manager.
Please check my video for knowing what kind of device I have already done, and see my feed back on ebay.
Click to expand...
Click to collapse
If a device can boot to recovery or download or if it charges or is detected when connected to PC then it isn't truly bricked, it's only softbricked. A truly bricked device will not charge, has no LED when connected to PC, can't be detected by PC in any kind of way, will not boot to recovery or download mode and will not power on in any way. This is actually called a "hardbrick".
Sent from my SM-S903VL using Tapatalk
Hi all, bit of a strange problem here.
I've recently updated TWRP from the official app and installed the latest recovery for my phone.. Problem is my TWRP screen is now green, and I cant touch any on screen buttons when in recovery. Because the recovery flag was set last time I rebooted the phone it keeps going into recovery and just freezing
To add insult to injury my USB port seems to be faulty (has been for a while) so I can't even connect with ODIN to reflash the recovery.. So I seem to be stuck in a predicament here. Windows advises the machine has malfunctioned and will not recognise the device. I wish this was a driver issue but after testing with a number of cables / machines I can safely say it's a hardware issue.
Is there anyway to reset the recovery flag so I can at least get back on my phone? Or any other options?
The Windows errors occur even when the phone is in Download Mode?
*Detection* said:
The Windows errors occur even when the phone is in Download Mode?
Click to expand...
Click to collapse
Yep. Got a new USB port coming in the post which should hopefully fix that.
I think it's looping into recovery because the recovery flag was set when I rebooted the phone (I selected reboot into recovery from my rom) Wondering if this flag will be reset if the battery is drained to 0%?
Because really, the phone itself should be functional, just getting past this recovery loop is the real problem
Interesting...
So I've replaced the USB port on the phone and STILL get the same error. Tried another laptop, same error. Tried removing samsung drivers from the windows driver store and reinstalling using smart switch... same error!
Pulling my hair out here guys!
clownstyle said:
Hi all, bit of a strange problem here.
I've recently updated TWRP from the official app and installed the latest recovery for my phone.. Problem is my TWRP screen is now green, and I cant touch any on screen buttons when in recovery. Because the recovery flag was set last time I rebooted the phone it keeps going into recovery and just freezing
To add insult to injury my USB port seems to be faulty (has been for a while) so I can't even connect with ODIN to reflash the recovery.. So I seem to be stuck in a predicament here. Windows advises the machine has malfunctioned and will not recognise the device. I wish this was a driver issue but after testing with a number of cables / machines I can safely say it's a hardware issue.
Is there anyway to reset the recovery flag so I can at least get back on my phone? Or any other options?
Click to expand...
Click to collapse
Did you manage to fix this? Mine is doing the exact same thing, it's green and uninteractable... I don't get any windows errors tho.
clownstyle said:
Interesting...
So I've replaced the USB port on the phone and STILL get the same error. Tried another laptop, same error. Tried removing samsung drivers from the windows driver store and reinstalling using smart switch... same error!
Pulling my hair out here guys!
Click to expand...
Click to collapse
Did you ffix this? I've the same prob
And guess what, you guys can't use fast charging ability..
https://forum.xda-developers.com/galaxy-s7/help/galaxy-s7-fast-charge-mtp-computers-t3694866
Take a look at my post. This is a growing problem I think.