Related
Hey everyone I'm quite new to android, and I'm currently stuck in Download Mode after trying and failing to install Twrp
I was previously Rooted, tried to install Twrp via Autorec, however when I ran the app it soft-bricked my phone and put me into Fastboot mode.
I followed http://forum.xda-developers.com/show....php?t=2476972 method, and got back to Download Mode.
I am currently in the middle of returning to stock through http://forum.xda-developers.com/show....php?t=2432476 using the .TOT method.
I'm fairly close to repairing it but my only issue is that I cannot get my computer to recognize my phone. Neither in Device management nor adb devices anymore.
Therefore I cannot change the port to COM 41 to flash the .TOT file.
I constantly tried installing drivers for the phone both 3.10 and 3.08 but still no recognition can anybody help?
Some more info about the phone:
it's the D801 variant but its on Wind (Canada) not T-mobile
it was previously Rooted
it did not have any recovery software installed
no roms had been flashed previously.
Rogybear said:
Hey everyone I'm quite new to android, and I'm currently stuck in Download Mode after trying and failing to install Twrp
I was previously Rooted, tried to install Twrp via Autorec, however when I ran the app it soft-bricked my phone and put me into Fastboot mode.
I followed http://forum.xda-developers.com/show....php?t=2476972 method, and got back to Download Mode.
I am currently in the middle of returning to stock through http://forum.xda-developers.com/show....php?t=2432476 using the .TOT method.
I'm fairly close to repairing it but my only issue is that I cannot get my computer to recognize my phone. Neither in Device management nor adb devices anymore.
Therefore I cannot change the port to COM 41 to flash the .TOT file.
I constantly tried installing drivers for the phone both 3.10 and 3.08 but still no recognition can anybody help?
Some more info about the phone:
it's the D801 variant but its on Wind (Canada) not T-mobile
it was previously Rooted
it did not have any recovery software installed
no roms had been flashed previously.
Click to expand...
Click to collapse
Try to restore your phone using the official LGMobile Support Tool. Just switch on normally the phone, plug it to your PC and wait for your kdz to be downloaded. Once it done, it should install the kdz by itself. Then factory reset your phone (if needed) as it should ask you some pin/password.
Hope it'll help you as it did for me!
I want to install any other modem but my note 3 does not let me do anything
I use Tweaked S5 Base Note 4 Style rom Android 4.4.2 Version 7.0
Modem is: XXUENB1
Build: KOT49H.G900SKSU1ANI1
I disabled already the reactivation protection, USB DEBUGGING is also enabled.
I use the original USB cable from note 3. KIES is not installed on my pc and I used ODIN as admin.
I got another modem, put my phone into download mode connected of course, and used another modem and put it into (CP/PHONE) in Odin3.10
It says, the flash is successfull but after reboot, the MODEM is NOT changed :"(
I tried several other modems but I can not seem to install any modem! HELP!
I tried to install stock rom via ODIN but it failed as the modem installation...
PS: Safestrap is on my device, my device is of course rooted and I also use PHILZ TOUCH 6
Did you follow this steps?:
1. Download the modem.
2. Unpack the rar file to anywhere on your computer, as long as you can access it.
3. Open up the included Odin and uncheck auto reboot.
4. Click on phone/CP, select the modem.bin, and press start.
5. When you finish the flash, manually reboot your phone back to download mode and flash the modem.bin one more time.
6. When the flash is complete, reboot and you're finished!
It's because you did not power off your phone, or remove the battery before doing the button combo for download mode, let it stay off for 15 seconds then try again.
Should work fine.
Okay, I will try to do the dual Flash and tell you if it works!
Hello,
I have installed a custom rom (Marshmallow) for my SM-A500FU through the adb. Now when I want to install a different rom I have to either boot into TWRP and I can't do that because booting into recovery simply restarts a phone, or I have to boot into Download mode and install it with the adb. The problem is that when the system is running, the phone simply charges, no Windows notifications or devices appear and when the phone is in Download mode Windows detects that a device is plugged in but can't recognize it. I have all the adb drivers, KIES and all that so it's not a problem. Can I somehow boot into TWRP or make Windows recognize my phone so I can use adb?
Thanks.
before installing a rom, have you wiped system, cache, dalvik and data? If yes try with a hard reset and if it doesn't work, too flash stock firmware
Hey,
yes, I wiped everything, I have flashed many roms earlier and I believe I have flashed it properly. I have managed to get into TWRP so I can actually flash FWs. I have only updated my rom to the newest CW13 build there is for my A5. Is there any way to flash a stock FW (for example a XEO KitKat) without ODIN? I can only use ADB through TCPIP and TWRP, so there is no way for me to flash it through ODIN.
Thanks.
so, if you press power+home+vol- it doesn't reboot in download mode, right?
It does boot into the Download mode. The problem is that when I plug the phone into my PC in Download mode it says that the USB Device is not recognized in Windows with 'A request for the USB device descriptor failed' error. When I plug it in when the phone is booted normally into android, it just charges, Windows doesn't see it at all.
whzq said:
It does boot into the Download mode. The problem is that when I plug the phone into my PC in Download mode it says that the USB Device is not recognized in Windows with 'A request for the USB device descriptor failed' error. When I plug it in when the phone is booted normally into android, it just charges, Windows doesn't see it at all.
Click to expand...
Click to collapse
Well, you can't flash samsung firmwares with twrp. Try flashing another rom through twrp
Alright, I have tried to flash multiple ROMs. Currently sitting on a Lollipop. Nothing changed, though. On every single ROM the problem still persists. It's not a problem with the PC as I've tried to connect my A5 to a laptop with freshly installed Windows and KIES and it behaved the same way as on my PC. The cable is fine as well, I have tested it with my old SGS3, it worked just fine on both my PC and laptop. Frankly, I have no idea what to do next, I'm starting to think that the port is physically broken. It's weird though, as I can still charge my phone and there is a response when the phone is in Download mode, just that Windows can't recognize it.
Try with adb command "adb reboot recovery" if it doesn't work you can downlaod odin mobile from play store and flash stock firmware!
Do you have odin for windows ?
zyxw-androidiani said:
Try with adb command "adb reboot recovery" if it doesn't work you can downlaod odin mobile from play store and flash stock firmware!
Do you have odin for windows ?
Click to expand...
Click to collapse
Yes, ihlf his device can boot he can use mobile odin. Have you tried with other PCs, just to see it isn't a problem of your pc?
In my experience usb device descriptor errors are related to the specific PC the error occurs on due to device driver conflicts, but if you get the same error on another pc then it could be the hardware.
I'd certainly be trying another cable first on a fresh PC.
Anyway regardless of all that you can flash the stock firmware with FLASHFIRE available on play as long as you have root.
Sent from my SM-T280 using XDA-Developers mobile app
Today i was trying to install the Android Marshmallow 6.0.1 on my Galaxy S5 Snapdragon via Odin, i downloaded the firmware from Sammobile, i verified that the phone model was exactly the same as named on the firmware, i place the .md5 file in the AP slot and everything was ready to go! (The phone was already plugged and in Bootloader mode, and drivers were up to date) then when finishing the flash Odin FAILS to complete the flash and the phone is left with nothing than the Download mode, i panic and try to access recovery mode but realize that there´s no recovery....I proceed to install the recovery.tar into my phone and it works, i start the phone and Samsung logo comes up, finally it loads and does al the process after you flash a Samsung phone.
Everything works just fine!...except for one thing, THERE´S NO RECOVERY!!!. The phone works perfectly but when i try to enter recovery mode, it sends me to Odin mode as it displays a message saying that failed to boot into recovery.
Please help me i don´t know what to do.
Thanks!
Just flash a custom recovery like twrp or cwm
Already did...same problem, recovery won't boot
adavicco said:
Already did...same problem, recovery won't boot
Click to expand...
Click to collapse
You need to flash a pit file to complete the install correctly.
Hi Guys,
today I wanted to flash the latest Stock ROM for my device via ODIN. I've done this many times before and (thought) I knew what I was doing. It is my third Phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly I wasn't aware that this particular device was locked.
After downloading the international firmware I tried to install it and ODIN got stuck while writing the system.img. After that my phone did not boot up (of course). After that I downloaded and tried to isntall the firmware of the carrier, but I had the exact same issue. When I turn my device on I get to an error screen which tells me to execute an "emergency recovery" via the Samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
FRP hinders me to install a custom recovery and the stock one does not allow any isntallations via ADB or SD card.
My qustion is: Does anyone know how I can install a rom from here?
I know that I had to have made some changes prior to the flashing, but as I said I was not aware and an Idiot for not double checking.
Since it is not bricked yet I suppose there must be an answer but I can't find anything.
Thanks in advance
Edit:
After only installing the stock bootloader, I am autmaticly entering it when I boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Fix
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
fabivons said:
hi guys,
today i wanted to flash the latest stock rom for my device via odin. I've done this many times before and (thought) i knew what i was doing. It is my third phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly i wasn't aware that this particular device was locked.
After downloading the international firmware i tried to install it and odin got stuck while writing the system.img. After that my phone did not boot up (of course). After that i downloaded and tried to isntall the firmware of the carrier, but i had the exact same issue. When i turn my device on i get to an error screen which tells me to execute an "emergency recovery" via the samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
Frp hinders me to install a custom recovery and the stock one does not allow any isntallations via adb or sd card.
My qustion is: Does anyone know how i can install a rom from here?
I know that i had to have made some changes prior to the flashing, but as i said i was not aware and an idiot for not double checking.
Since it is not bricked yet i suppose there must be an answer but i can't find anything.
Thanks in advance
edit:
After only installing the stock bootloader, i am autmaticly entering it when i boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Click to expand...
Click to collapse
have u solved your problem ? This problem i am facing on the s7edge nougat ? Plz help ?
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might be worth a try!
Good luck!
Fabivons said:
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might me worth a try!
Good luck!
Click to expand...
Click to collapse
y i have done that and the device boots up but some applications force close and when i insert the memory card , the phone gets restarted everytime
Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Tell us in detail now.
SjDU said:
Tell us in detail now.
Click to expand...
Click to collapse
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
suhaibahmad said:
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
Click to expand...
Click to collapse
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Fabivons said:
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Click to expand...
Click to collapse
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
suhaibahmad said:
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
Click to expand...
Click to collapse
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Fabivons said:
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Click to expand...
Click to collapse
thats your kindness , yes i have performed the factory reset several times from recovery , but when i trying to reset it from settings , it goes after restart to recovery with dm-verity error , then i wipe and factory reset from there
Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
SjDU said:
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
Click to expand...
Click to collapse
Well FRP has to be turned off (the button in the menu is called "OEM unlock, the button has to be set to on which deactivates FRP). You don't mention using a PIT file - did you use one?