Tried to restore from a backup, flash failed. TWRP asking for password? - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

I cant reinstall my ROM or flash anything, i cant even boot into anything but recovery and download.
I did not set a password, i tried restoring hyperdrive from a backup.
Is there a default password to TWRP recovery?
If not, can i flash recovery without booting into my phone.
EDIT:
I'm following this guide here:
http://forum.xda-developers.com/showthread.php?t=2301259&highlight=stock
and here:
http://androidfirmwares.net/Guide/Details/9
To flash via ODIN.

I've seen that with a bad download of twrp. Download load it again and then reflash it.
Edit, at this point you might be better off using Odin to flash the stock rom and starting over. I'm not sure if an odin flashable version of twrp exists.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Went through the Odin process and now i'm stuck at the Samsung custom screen, wont go any farther.
Any suggestions?
EDIT
WOAH Looks like i have stock recovery now. Trying to factory reset etc...
EDIT 2:
Alright so the process i took was to flash the stock factory image using Odin, then reboot into recovery and factory wipe/reset phone.
It's booting up into the stock rom now..... Woot!

Yep, that's what it all should be.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Related

ROOTED 4.2.2 won't boot recovery

Just rooted my N7 on 4.2.2 but can't boot into recovery. I just get the "no command" screen. I flashed twrp with the Nexus Root Toolkit and everything seemed to go fine but I can't boot into recovery. Is there another way to flash a custom recover?
Thanks!
Sent from my Nexus 7 using xda app-developers app
fastboot flash recovery recovery-image-file-name.img
while in boot loader mode.
Please use the forum search capability.
christanya99 said:
Just rooted my N7 on 4.2.2 but can't boot into recovery. I just get the "no command" screen. I flashed twrp with the Nexus Root Toolkit and everything seemed to go fine but I can't boot into recovery. Is there another way to flash a custom recover?
Thanks!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
you probably booted, not flashed the recovery. fastboot flash it via fastboot with the instructions above. or, to make it even easier, download the goo manager app. you can flash twrp recovery with the app. open the app, press the settings option, press install openrecoveryscript, press yes, then let it do its thing.
simms22 said:
you probably booted, not flashed the recovery. fastboot flash it via fastboot with the instructions above. or, to make it even easier, download the goo manager app. you can flash twrp recovery with the app. open the app, press the settings option, press install openrecoveryscript, press yes, then let it do its thing.
Click to expand...
Click to collapse
I have the same problem as the 1st poster, an i did what you said, in regards to letting goomanager do the work but it still didn't work
Sent from my rOot3d Samsung Galaxy S3
http://teamw.in/project/twrp2/103
Read the download instructions at the bottom. Have you done that step?
The stock recovery will be restored on boot otherwise. It's the same procedure for any recovery (CWM) not just TWRP.
Sent from my Desire HD using xda premium
sashank said:
http://teamw.in/project/twrp2/103
Read the download instructions at the bottom. Have you done that step?
The stock recovery will be restored on boot otherwise. It's the same procedure for any recovery (CWM) not just TWRP.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
No I haven't did that. I'm away from my computer on a trip, an will do this when I get home
Sent from my rOot3d Samsung Galaxy S3

[Q] Problems with stock rooted rom when flashed from recovery.

Let me give you the timeline. A few days ago I rooted the device using the method outlined in this video. I verified my root status with Root Checker and my device was indeed successfully rooted. I installed BusyBox (basic) and TitaniumBackup Pro. Made a backup of my user apps+data to the external SD. I then downloaded Goomanager and used it to install the latest version of TWRP.
All of this was successful. I went into TWRP and created a NAND backup. I backed up: Boot, System, and Data. I did not back up EFS, Preload, Cache, or Recovery.
I performed a wipe and format of user data. Flashed to SlimBean, had some issues. Wiped. Flashed CM10.1. Again, some issues. I decided I'm going to wait a while for these roms to stabilize a bit before I try using any of them on a regular basis. I wiped and restored my original NAND backup of my stock rooted ROM. The restore appeared to go fine. I don't know if this will have anything to do with anything but I went ahead and ran a PRL and Profile update. The device was functioning okay until...
I noticed that the time was off. The lockscreen time was correct but the time in the upper right status bar was stuck at about an hour before. I decided I'd just try restarting the device to see if that fixed anything. Well when I did it wouldn't boot. I'd get stuck on the first Samsung Galaxy S4 logo screen. Took the battery out, waited, put it back in, restarted. Still... stuck on the logo screen. I tried booting into recovery (Vol. Up + Power). The black SGS4 logo would come up with a tiny blue notification in the upper left corner (Recovery Boot). Then the device would restart and get stuck at the SGS4 logo screen again.
Eventually I was able to get it to boot to TWRP (maybe I was just holding the power button too long?)
I wiped. It failed. I tried again. It worked. I recovered my CM10.1 setup and it's been working "okay" on CM10.1 ever since.
I want to get back to my stock rooted rom but I want to understand what happened first.
Anyone? Please?
Stu_Gots said:
Anyone? Please?
Click to expand...
Click to collapse
What version of TWRP were you on? If it was 2.5.0.3 then there's your culprit. That version of TWRP is known to have issues. You need to flash version 2.5.0.2 found here.......http://forum.xda-developers.com/showthread.php?t=2277480. Scroll down to install Alternate recovery and download the 2.5.0.2 .img file.
Once you've downloaded the file, go to your Goo Manager folder and delete the file there. Then paste the file you downloaded from the above link into that same folder. After that, open Goo Manager and go to Install Recovery Script. It should see the file you have in your folder and then download it from their server. Make SURE it says you are downloading 2.5.0.2. Once Goo does its thing, reboot into Recovery and make sure you're running the 2.5.0.2 version of TWRP. Now you can flash all you want because it will function properly. I would first download a stock rom and clear out any skeletons in the closet. Then go into TWRP and wipe EVERYTHING. This includes data, dalvik cache, cache, system and then factory reset as well 3 times each. MAKE SURE you don't delete the internal or external sd cards. Flash the stock rom, set it up how you wish, make a nand of that file( Include EFS and Preload because it can't hurt to be safe) and then flash whatever you like. You should be good to go.
---------- Post added at 01:20 PM ---------- Previous post was at 01:17 PM ----------
Stu_Gots said:
Anyone? Please?
Click to expand...
Click to collapse
Another question I have is what version of software/firmware are you on? Go to Settings/More/About Phone and check what your software and baseband versions are? If its MDC, then rooting via MotoChopper was a good method to use. If it says MDL, that could also be the reason why the phone was acting so quirky. There is a new method to rooting if you are on MDL and it's also found in Mudavo's thread found here...http://forum.xda-developers.com/showthread.php?t=2277480
For the record. I was using the phone stock rooted for a week or so without any problems. I hadn't had any issues until after restoring the backup I made in TWRP. When I wiped prior to installing SlimBean/CM10.1 I did the standard auto-wipe AND I wiped data
Oh yeah. To answer your questions.
TWRP Version: 2.5.0.2
Software/Baseband versions: L720VPUAMDL
Earlier today I just tried wiping (default TWRP 2.5.0.2). Then restoring the backup again. This was so I could get you the information on what software/baseband version I was on. When the restore completed I went to reboot. The phone stuck on the SGS4 logo screen. I then rebooted in recovery and wiped as before and then I wiped data. The phone was then able to boot into the stock rooted rom. I have so far noticed the times being out of sync from the lock screen and the status bar. I reset the phone again. Stuck at SGS4 logo again.
My trouble getting back into TWRP was my own fault. I was holding the buttons down too long. I can get back into TWRP no problem.
So. What are my options at this point? I would like to be on the latest stock everything... with root and stock wireless tether enabled. The way I was. If I can't restore my backup then I'm going to have to reflash the stock rom. I can't seem to find a comprehensive index of information. Every time I think I've got something figured out I stumble on new bits of information.
Stu_Gots said:
For the record. I was using the phone stock rooted for a week or so without any problems. I hadn't had any issues until after restoring the backup I made in TWRP. When I wiped prior to installing SlimBean/CM10.1 I did the standard auto-wipe AND I wiped data
Oh yeah. To answer your questions.
TWRP Version: 2.5.0.2
Software/Baseband versions: L720VPUAMDL
Earlier today I just tried wiping (default TWRP 2.5.0.2). Then restoring the backup again. This was so I could get you the information on what software/baseband version I was on. When the restore completed I went to reboot. The phone stuck on the SGS4 logo screen. I then rebooted in recovery and wiped as before and then I wiped data. The phone was then able to boot into the stock rooted rom. I have so far noticed the times being out of sync from the lock screen and the status bar. I reset the phone again. Stuck at SGS4 logo again.
My trouble getting back into TWRP was my own fault. I was holding the buttons down too long. I can get back into TWRP no problem.
So. What are my options at this point? I would like to be on the latest stock everything... with root and stock wireless tether enabled. The way I was. If I can't restore my backup then I'm going to have to reflash the stock rom. I can't seem to find a comprehensive index of information. Every time I think I've got something figured out I stumble on new bits of information.
Click to expand...
Click to collapse
Honestly, at this point, you need to unroot and reroot again using the method in Mudavo's post. You used the wrong method to root with motochopper. Motochopper was only for the MDC version. That could be why you are having the issues that you are. That's all I can suggest at this point. Start with a clean slate and try it again. Trust me you aren't the only one to do this. I've done it a few times myself. It sucks but at least you know you did everything right. You're going to have to flash a stock MDC rom that came shipped with the phone via Odin. Then take the OTA to update your phone to MDL and then just follow Mudavo's post to root the proper way when you're on the MDL version.
What about the TWRP recovery I have installed? Am I going to have to deal with that in some way?
What are the advantages of Odin over TWRP? I'm not trying to question your judgment btw. I'm legit curious because I've only ever used TWRP to
Flash roms.
Sorry for all the dumb questions.
Btw . While I was waiting for your reply I tried trouble shooting a bit myself. To see if I could fix my own problem. I found a thread with MDL stock rooted and a bunch of firmware and kernel files. I flashed to it in TWRP and it's working reasonably well so far. I'm still dtf for other methods if mine is somehow flawed.
My method didn't work. When I restarted from TWRP (after no other issues) the phone for stuck.
The phone was restarted several times and booted fine. It wasn't until I restarted into TWRP then and then back into normal boot that I had issues
this time. So I'm going to do what you suggested. I just have a couple questions.
If my rom/recovery is corrupted how do I fix my problem. I would need a working rom AND recovery to flash stock rom. I'm not sure where to start since everything is all messed up.
Thank you so much for your help. You're the best!
You should do a Full Odin restore to Stock and start from scratch if you continue to have issues.
http://forum.xda-developers.com/showthread.php?t=2270065
You can also try this thread to ensure a full wipe before flash
http://forum.xda-developers.com/showthread.php?t=2277261
gharlane00 said:
You should do a Full Odin restore to Stock and start from scratch if you continue to have issues.
http://forum.xda-developers.com/showthread.php?t=2270065
You can also try this thread to ensure a full wipe before flash
http://forum.xda-developers.com/showthread.php?t=2277261
Click to expand...
Click to collapse
Installed Mobile ODIN Pro from the play store for $5... I hope that's the right Odin!
Stu_Gots said:
Installed Mobile ODIN Pro from the play store for $5... I hope that's the right Odin!
Click to expand...
Click to collapse
download Odin 1.85 or 3.07 on your PC don't use mobile version for something like this
Sent from my SPH-L720 using xda premium
Do I need to flash the stock kernal too? Will this eliminate my TWRP recovery installation as well?
If you odin back to stock it also has the kernel and stock recovery this will start you all over. Also of it doesnt boot past galaxy s4 screen then boot into recovery and wipe data after you odin back.
Sent from my SPH-L720 using xda premium
devoureddreams said:
If you odin back to stock it also has the kernel and stock recovery this will start you all over. Also of it doesnt boot past galaxy s4 screen then boot into recovery and wipe data after you odin back.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Alright... so another problem. I need the latest Samsung USB driver right? Unfortunately...
1.5.25.0 as linked to in this thread cannot be downloaded because uploaded.com or whatever says I've exceeded my allowance. Trouble is... I haven't downloaded anything from them ever. I have this problem all the time because of my ISP (Satellite Internet).
Is there a rehost? Do these drivers not install themselves automatically when the device is plugged into the PC?
http://downloadcenter.samsung.com/c...ng_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
Sent from my SPH-L720 using xda premium
I'm so freaking frustrated by this whole process. It looks like by all accounts there are a dozen different ways to do everything and I just know i'm going to mess it up.
I'm following the directions in this video.
http://www.youtube.com/watch?v=ZD5CHlrPQJQ&feature=youtu.be
When I extract the file I downloaded I get an MD5 file not an ODIN file.
Stu_Gots said:
I'm so freaking frustrated by this whole process. It looks like by all accounts there are a dozen different ways to do everything and I just know i'm going to mess it up.
I'm following the directions in this video.
http://www.youtube.com/watch?v=ZD5CHlrPQJQ&feature=youtu.be
When I extract the file I downloaded I get an MD5 file not an ODIN file.
Click to expand...
Click to collapse
Follow this tutorial here
http://www.sxtpdevelopers.com/showthread.php?p=2599
Sent from my SPH-L720 using xda premium
Alright guys. I got it done a while back. Phone is back to normal stock.
Perusing the internet I found this video.
http://www.youtube.com/watch?v=s_hXUJ-u-cw
As it happens I linked to the wrong video in my OP. The method in that video is exactly what I did to root in the first place. The proper way. I installed TWRP from GooManager.
So if I rooted correctly and I installed TWRP correctly what do you suppose caused my problem? I want to root and install custom recovery again!
If I root using the CF-Auto-Root method will I then be able to install custom recovery in goomanager or does custom recovery need to be installed in some other special way?
Stu_Gots said:
If I root using the CF-Auto-Root method will I then be able to install custom recovery in goomanager or does custom recovery need to be installed in some other special way?
Click to expand...
Click to collapse
thats all there is to it.

[Q] SoftBrick used Kies- CWM can't get recovery mode

Hi all,
Had a number of issues with my SGS4, decided it's time to wipe it out and start fresh. Thankfuly I have everything on my SD card.
Long story short, I softbricked it, none of my backups are working. I read that if I launch KIES and follow instructions it loads a new firmware and OS (factory). The problem is, I can't get it into "download" or recovery mode. I have Clockworkmod recovery on this phone.
How do I get the CWM removed in order to reboot into the default download mode that came from factory? The phones will reboot and sit at the AT&T logo. I've done everything I could think of, been 4 hours and not making progress. Please help me remove CWM and or boot into download mode so I can try and restore my SGS4. Thank you all:crying:
Did you make backups in cwm? Can you restore any of them?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Yes I tried to recover via my back ups. Some say md5 mismatch which I can't fix until I get into the OS. Other ones restore, however upon reboot it gets stuck at the ATT logo.
I am downloading the stock ROM onto a SD card as we speak, hoping to flash to it using CWM. Ultimately I would like to remove CWM and use KIES to restore/reinstall my firmware. I'm told this is considered a soft brick.
Manic9803 said:
Yes I tried to recover via my back ups. Some say md5 mismatch which I can't fix until I get into the OS. Other ones restore, however upon reboot it gets stuck at the ATT logo.
I am downloading the stock ROM onto a SD card as we speak, hoping to flash to it using CWM. Ultimately I would like to remove CWM and use KIES to restore/reinstall my firmware. I'm told this is considered a soft brick.
Click to expand...
Click to collapse
What stock rom did you download? Stock roms are generally flashed thru Odin. You don't need to get rid of cwm.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
stockroms.net/ file/ GalaxyS4/SGH-I337/I337UCUAMDL I337ATTAMDL_ATT .zip
Looks like the stock rom? Figured I'd load it onto my SD card, then use CWM to flash to it. Think it'll work? It's downloading as we speak.
In an ideal word, I'd use KIES to do the firmware restore and upgrade but CWM is blocking me from my standard/stock download recovery (power button home button and volume up button)
Manic9803 said:
stockroms.net/ file/ GalaxyS4/SGH-I337/I337UCUAMDL I337ATTAMDL_ATT .zip
Looks like the stock rom? Figured I'd load it onto my SD card, then use CWM to flash to it. Think it'll work? It's downloading as we speak.
In an ideal word, I'd use KIES to do the firmware restore and upgrade but CWM is blocking me from my standard/stock download recovery (power button home button and volume up button)
Click to expand...
Click to collapse
Don't know stock roms.net. Next time use sammobile.com. my guess is the zip won't flash thru cwm. Most of them you need to extract the .tar.md5 file out of the zip and use that in Odin. You'll need 7-zip to extract it.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
Don't know stock roms.net. Next time use sammobile.com. my guess is the zip won't flash thru cwm. Most of them you need to extract the .tar.md5 file out of the zip and use that in Odin. You'll need 7-zip to extract it.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Well, long story short I wasn't able to mount the external SD card from CWM. Thankfully after wiping the device and cache over and over and reloading my backups over and over it finally loaded and by passed the software loop.
I am happy it's no longer a $600 piece of plastic.So, I am hoping to do a fresh image install (downloading firmware now) and doing better backups. Any recommendations on a new boot manager outside of CWM?
Any ideas for a bullet proof (or close as possible) plan to keep this from happening again? Thanks all
Bump- anyone
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Soft-Bricked SPH-L720

I was running CyanFox this weekend, and decided I wanted a newer rom. I installed a stock mk2 rooted rom, and it was encrypted. A forum post suggested that I wipe the device, so from my recovery I formatted the internal drive. I then loaded Odin, loaded a stock mk2 rom, and flashed it. The device started up, but only goes to a black screen. When I try to root it through Odin, it won't root.
Now whenever I flash a firmware through Odin, it fails. What's going on with my device? Is there anyway to save it?
When I turn it on now, or boot to recovery, it tells me a firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I would find odin 1.85 and a copy of Philz recovery. .tar.....flash this via odon..using PDA option....this will at least bring u back into recovery so u can flash anything you may have on your sd card... if you dont bave anything. Just use a pc and grad a rom... then drag it over to the sdcard.. then flash away.... this should work ... i almkst sure its a go...
Sent from my SPH-L720 using xda app-developers app

[Q] SGH-I337m soft bricked with faulty usb

A few days ago my USB port on my Telus SGH-I337m gave out, leaving me with no data connectivity and extremely limited charging capabilities.
I rooted the phone using ODIN and TWRP when I originally got it last summer, but i forgot all about that and brought it over to best buy for an exchange. We did a factory reset before the guy noticed it was rooted and told me to un root and come back. However, after the factory reset, I'm now stuck on the samsung galaxy s4 splash logo, but I do still have access to recovery booting. I've tried downloading stock and custom roms and flashing those to no avail. I switched my recovery manager from TWRP 2.5.0.0 to CWM 6.0.4.4, but still nothing. ODIN flashing is impossible because the USB port isn't working. Any suggestions?
Are you using super SU? There's an unroot option in it
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
jd1639 said:
Are you using super SU? There's an unroot option in it
Can you flash a rom in recovery using adb side load or pushing a rom to it
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Sent from my Nexus 5 using XDA Free mobile app
I don't have access to super SU at the moment. The phone hangs during boot at the Samsung galaxy s4 splash logo
SgtBuzzkilll said:
I don't have access to super SU at the moment. The phone hangs during boot at the Samsung galaxy s4 splash logo
Click to expand...
Click to collapse
You said you flashed cwm over twrp, if you did so you must be able to flash a rom too.
The bright side, if it's not booting you could take it to a best buy and they couldn't tell it's rooted
Edit, when you boot into recovery is it the stock recovery now, or cwm?
Sent from my Nexus 5 using XDA Free mobile app
Any custom roms I've tried to flash have still left me stuck at the splash logo. Any chance you could point me to a stock ROM download? None of the stock roms i've found will install. And since it does still boot into recovery mode the guys at bestbuy will still know i have it rooted though right? worst case i might just drain the battery and bring it in since it takes about 20 mins to charge 1%.
edit: it recovery boots into CWM 6.0.4.4 only, hangs on normal startup with any rom
SgtBuzzkilll said:
Any custom roms I've tried to flash have still left me stuck at the splash logo. Any chance you could point me to a stock ROM download? None of the stock roms i've found will install. And since it does still boot into recovery mode the guys at bestbuy will still know i have it rooted though right? worst case i might just drain the battery and bring it in since it takes about 20 mins to charge 1%.
Click to expand...
Click to collapse
If it boots into a custom recovery, twrp or cwm, yes they're going to know you modified the device. But you're not going to be able to get rid of that without Odin.
Sent from my Nexus 5 using XDA Free mobile app
If I'm able to fix the boot error, would I be able to use mobile odin or super SU to unroot it?
Either way any other suggestions for getting past the splash screen?
What I've tried exactly is:
-boot into CWM recovery
-wipe data/factory reset
-wipe cache partition
-wipe dalvik cache
-install ROM from zip
-reboot
custom ROMS install ok but give me the boot error
stock roms don't install at all
And thanks for the help i do appreciate it
SgtBuzzkilll said:
If I'm able to fix the boot error, would I be able to use mobile odin or super SU to unroot it?
Either way any other suggestions for getting past the splash screen?
What I've tried exactly is:
-boot into CWM recovery
-wipe data/factory reset
-wipe cache partition
-wipe dalvik cache
-install ROM from zip
-reboot
custom ROMS install ok but give me the boot error
stock roms don't install at all
And thanks for the help i do appreciate it
Click to expand...
Click to collapse
I'm not sure what to tell you. First, you're flashing the custom roms correctly and I'm not sure why they're not booting. I don't know what stock rom you're trying to flash.
Having the custom recovery is going to kill you at best buy. They'll try to boot into recovery to do a factory reset and they'll see you modified the device.
I don't know if mobile Odin works on the s4, I don't think so, but you'd have to boot into something first. And that's a problem right now.
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 09:07 PM ---------- Previous post was at 08:48 PM ----------
@SgtBuzzkill I'm not at a pc tonight but tomorrow I'll make you a stock recovery zip that you can flash in cwm. That will take care of the custom recovery issue
Sent from my Nexus 5 using XDA Free mobile app
I managed to get past the splash logo. Turn out i needed to format all the partitions as well as clear them before installing a rom.
The stock roms i was (mistakenly) trying were the odin tar.md5 files. But now I've got mobile odin running and I found a couple videos with mobile odin and the gs4 so im going to give it a shot. The procedure recommends >50% battery though so I'm going to have to let it charge overnight.
We'll see if it works in the morning
Reflash lastest 4.4.2 (Colombia) Firmware from Sammobile, Tick "NAND Erase All", "Re-partition" & "Phone EFS Clear", also put the unziped attached file on the PIT section.
This will completely wipe your NAND, this means a complete Full wipe of the whole phone, I also have a i337M from Telus & deleted all the remains of previus modifications that normal recoveries can't wipe. thus reformatting Boot, Cache, System, EFS & all other partitions to their correct state.
Make sure your Odin window looks as the attached image.
It will stuck at samsung logo after flashing, boot to recovery & perform a factory reset, and you are good to go.
King regards.
Starnel said:
Reflash lastest 4.4.2 (Colombia) Firmware from Sammobile, Tick "NAND Erase All", "Re-partition" & "Phone EFS Clear", also put the unziped attached file on the PIT section.
This will completely wipe your NAND, this means a complete Full wipe of the whole phone, I also have a i337M from Telus & deleted all the remains of previus modifications that normal recoveries can't wipe. thus reformatting Boot, Cache, System, EFS & all other partitions to their correct state.
Make sure your Odin window looks as the attached image.
Click to expand...
Click to collapse
Read the op. His usb port doesn't work. No Odin
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Read the op. His usb port doesn't work. No Odin
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Boot partition most likely to be damaged, Only Odin can repair it afaik.
Starnel said:
Boot partition most likely to be damaged, Only Odin can repair it afaik.
Click to expand...
Click to collapse
It's a broken usb port. It's hardware, not software.
Sent from my Nexus 5 using XDA Free mobile app

Categories

Resources