[Q] Unable to Boot in Download Mode - Galaxy Grand Duos i9082 Q&A, Help & Troubleshootin

Dear Friends,
I am facing an interesting issue.
Due to rain my grand i9082 have a issue of volume down(-) so unable to use that.
I want to go to download mode.
I have philz CWM recovery.
I want to install latest CM11 App2sd ROM so whenever I install it by Philz CWM it gives status 7 error.
To resolve this i need to shift to earlier CWM with ODIN method but i am unable to boot in Download Mode.
Expecting interesting solutions from all of you masterminds.
Please let me know any tricks.

U can use the same Philz to flash whatever CWM u want.
If u still need ODIN then follow below procedure:
You will have to install Android Adb & Fastboot drivers.
Now open settings on your phone and in developer options enable USB debugging mode.
Connect your device to your PC and allow debugging when it prompts on your phone.
Open the Fastboot folder that you created using our ADB & Fastboot drivers guide.
Open the Fastboot folder and then hold the shift key on your keyboard and right click on any empty area within the Fasboot folder.
Click on “Open Command Window / Prompt Here”.
Type the following command: adb reboot download
As soon as you hit the Enter Key, your phone should boot into the download mode.

Trilochanaaya said:
U can use the same Philz to flash whatever CWM u want.
If u still need ODIN then follow below procedure:
You will have to install Android Adb & Fastboot drivers.
Now open settings on your phone and in developer options enable USB debugging mode.
Connect your device to your PC and allow debugging when it prompts on your phone.
Open the Fastboot folder that you created using our ADB & Fastboot drivers guide.
Open the Fastboot folder and then hold the shift key on your keyboard and right click on any empty area within the Fasboot folder.
Click on “Open Command Window / Prompt Here”.
Type the following command: adb reboot download
As soon as you hit the Enter Key, your phone should boot into the download mode.
Click to expand...
Click to collapse
Dear Friend,
Thanks for the instant reply.
My phone stuck on logo due to some bad flashing of ROM.
So now i am at the stage where i m unable to boot due to down volume key hardware error but i m on philz recovery but it gives status 7 error.

Trilochanaaya said:
U can use the same Philz to flash whatever CWM u want.
If u still need ODIN then follow below procedure:
You will have to install Android Adb & Fastboot drivers.
Now open settings on your phone and in developer options enable USB debugging mode.
Connect your device to your PC and allow debugging when it prompts on your phone.
Open the Fastboot folder that you created using our ADB & Fastboot drivers guide.
Open the Fastboot folder and then hold the shift key on your keyboard and right click on any empty area within the Fasboot folder.
Click on “Open Command Window / Prompt Here”.
Type the following command: adb reboot download
As soon as you hit the Enter Key, your phone should boot into the download mode.
Click to expand...
Click to collapse
can you provide me flash-able CWM old by Chotu. As if i will be on old CWM i can easily flash any ROM without status 7 error.:good:

hemant4409 said:
can you provide me flash-able CWM old by Chotu. As if i will be on old CWM i can easily flash any ROM without status 7 error.:good:
Click to expand...
Click to collapse
Now old CWM by Chotu cannot be used to flash these latest ROMs. Use the latest from here. Either Touch/Non-Touch.

Trilochanaaya said:
Now old CWM by Chotu cannot be used to flash these latest ROMs. Use the latest from here. Either Touch/Non-Touch.
Click to expand...
Click to collapse
Oh good.
I got flashable file for ClockWorkMiod.
Thanks Man, Thank you very much.:good::good::good::good::good:

Trilochanaaya said:
Now old CWM by Chotu cannot be used to flash these latest ROMs. Use the latest from here. Either Touch/Non-Touch.
Click to expand...
Click to collapse
I have installed old CWM but still facing Status 7 error.:crying::crying::crying::crying:
Please help me for this error.

hemant4409 said:
I have installed old CWM but still facing Status 7 error.:crying::crying::crying::crying:
Please help me for this error.
Click to expand...
Click to collapse
Use latest recovery!

Trilochanaaya said:
Use latest recovery!
Click to expand...
Click to collapse
Status 7 means often your recovery is outdated
Status 2 means in the script in the rom is to old, update the script or use older recovey
Personaly I always had problems with the Clockworkmod Touch & Non-Touch Recoveries, but never had any problem with the plain CWM V6.0.45 (recovery_20131210) and was able to flash all and never had problems or errors

RichyE said:
Status 7 means often your recovery is outdated
Status 2 means in the script in the rom is to old, update the script or use older recovey
Personaly I always had problems with the Clockworkmod Touch & Non-Touch Recoveries, but never had any problem with the plain CWM V6.0.45 (recovery_20131210) and was able to flash all and never had problems or errors
Click to expand...
Click to collapse
Thanks for the solution, but i want ""plain CWM V6.0.45 (recovery_20131210)"" in flashable zip as i am only having cwm running.
Please help.:crying::crying::crying::crying:

hemant4409 said:
Thanks for the solution, but i want ""plain CWM V6.0.45 (recovery_20131210)"" in flashable zip as i am only having cwm running.
Please help.:crying::crying::crying::crying:
Click to expand...
Click to collapse
Ì will try to make a flashable zip for you based on recovery_20131210
---------- Post added at 11:09 AM ---------- Previous post was at 10:44 AM ----------
Sorry,
It flashed without error, but didn't boot
Had to use Odin to get my recovery back

RichyE said:
Ì will try to make a flashable zip for you based on recovery_20131210
---------- Post added at 11:09 AM ---------- Previous post was at 10:44 AM ----------
Sorry,
It flashed without error, but didn't boot
Had to use Odin to get my recovery back
Click to expand...
Click to collapse
Ohhh :crying::crying::crying::crying:
I am not able to boot in Download mode that is the main issue.
But can anyone suggest me how to enter download mode without hard keys.
I have tried Philz Recovery but phone stuck up at logo.
Almost dead phone :crying::crying::crying::crying::crying::crying:

Did you see if you can use ADB from a computer??
adb reboot download

RichyE said:
Status 7 means often your recovery is outdated
Status 2 means in the script in the rom is to old, update the script or use older recovey
Personaly I always had problems with the Clockworkmod Touch & Non-Touch Recoveries, but never had any problem with the plain CWM V6.0.45 (recovery_20131210) and was able to flash all and never had problems or errors
Click to expand...
Click to collapse
ANyhow i entered in download mode but unable to flash the CWM
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

hemant4409 said:
ANyhow i entered in download mode but unable to flash the CWM
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Did you try to flash recovery_20131210.tar using the AP button?
What version of Odin and try other usb cable

RichyE said:
Did you try to flash recovery_20131210.tar using the AP button?
What version of Odin and try other usb cable
Click to expand...
Click to collapse
Odin 1.85
Anyhow odin was successful.
I have installed CWM but still getting the same issue i.e "status 7 " for any/every rom i flash

hemant4409 said:
Odin 1.85
Anyhow odin was successful.
I have installed CWM but still getting the same issue i.e "status 7 " for any/every rom i flash
Click to expand...
Click to collapse
Flash stock ROM

hemant4409 said:
Odin 1.85
Anyhow odin was successful.
I have installed CWM but still getting the same issue i.e "status 7 " for any/every rom i flash
Click to expand...
Click to collapse
Also the latest Odin version is 3.0.9 (At least that is my version )
Like Trilochanaaya said, but make sure to flash 4.2.2 otherwise you can't flash kitkat later

RichyE said:
Also the latest Odin version is 3.0.9 (At least that is my version )
Like Trilochanaaya said, but make sure to flash 4.2.2 otherwise you can't flash kitkat later
Click to expand...
Click to collapse
Ok , I will try to flash 4.2.2 Indian Original by Latest odin 3.0.9 and will update you the results.

hemant4409 said:
Ok , I will try to flash 4.2.2 Indian Original by Latest odin 3.0.9 and will update you the results.
Click to expand...
Click to collapse
Is rooting compulsory for installing custom rom???

Related

[Q] Need help with a soft brick

Alright, so i have a Galaxy s3 (sgh-i747) and i rooted it with philz bootloader
So i was going to install a custom rom, so i had to wipe.
I downloaded the rom, and wiped.
But then i realized i actually never put the ****ing rom on the phone and now my phone has no rom loaded.
I can still boot into download/recovery
I really need help with this, what are my option?
So my phone is not rooted any more i guess because the recovery/bootloader is the default one
I still really need help with this
Ozzie 45 said:
I still really need help with this
Click to expand...
Click to collapse
Do you remember what (stock) firmware or Android version you were on before the attempted installation? Your best option now would be a return to stock. If you were on anything earlier than 4.3 (e.g. 4.1.2 or 4.1.1) you could try using Odin to flash 4.1.1 since you can get into download mode. To do this take the following steps ..
1. Download the required files via the following link <http://fortedge.com/downgrade.html>and extract the Odin flashable file
2. Install Odin
3. Boot into download mode and flash via Odin
OR you could find the correct stock image via the following discussion thread and flash via Odin. This would be a complete stock file that will flash all partitions including bootloader, modem, kernel and system.
http://forum.xda-developers.com/showthread.php?t=1739426
If you were on Android 4.3, then you cannot use the above method or flash via Odin and any attempt to do this will create more bother for you. In this case, you would need to flash custom recovery via Odin and restore the stock recovery image via custom recovery. Please download the stock recovery file via the following the thread ...
http://forum.xda-developers.com/show....php?t=2658486
If you need any further detailed steps on how to complete this, please do not hesitate to holler.
Larry2999 said:
Do you remember what (stock) firmware or Android version you were on before the attempted installation? Your best option now would be a return to stock. If you were on anything earlier than 4.3 (e.g. 4.1.2 or 4.1.1) you could try using Odin to flash 4.1.1 since you can get into download mode. To do this take the following steps ..
1. Download the required files via the following link <http://fortedge.com/downgrade.html>and extract the Odin flashable file
2. Install Odin
3. Boot into download mode and flash via Odin
OR you could find the correct stock image via the following discussion thread and flash via Odin. This would be a complete stock file that will flash all partitions including bootloader, modem, kernel and system.
http://forum.xda-developers.com/showthread.php?t=1739426
If you were on Android 4.3, then you cannot use the above method or flash via Odin and any attempt to do this will create more bother for you. In this case, you would need to flash custom recovery via Odin and restore the stock recovery image via custom recovery. Please download the stock recovery file via the following the thread ...
http://forum.xda-developers.com/show....php?t=2658486
If you need any further detailed steps on how to complete this, please do not hesitate to holler.
Click to expand...
Click to collapse
Yes, i was on Android 4.3
Can you please re-link that? The URL is broke
Ozzie 45 said:
Yes, i was on Android 4.3
Can you please re-link that? The URL is broke
Click to expand...
Click to collapse
I'm also going to need guidance on flashing custom recovery via Odin and restore the stock recovery image via custom recovery
Ozzie 45 said:
I'm also going to need guidance on flashing custom recovery via Odin and restore the stock recovery image via custom recovery
Click to expand...
Click to collapse
You will find the full link here ...<http://forum.xda-developers.com/showthread.php?t=2658486>
Download Odin.
http://fortedge.com/downloads/Odin307.zip
Download the Odin flashable custom recovery file via the following link ...
<http://techerrata.com/browse/twrp2/d2att>. You need one of the more recent images ending in *.tar e.g. the one below
<http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.0-d2att.tar>
Install Samsung Kies on your PC if you don't have this already (this will be useful for the drivers)
Install the twrp tar file to an easily remembered location on your PC
Extract the Odin zip to get the executable file (*.exe)
Click on the exe file to run Odin
Now boot your phone into download mode by powering off completely then holding down the Power + Home + Volume Down buttons simultaneously until you see a warning message.
Press the Volume Up button to continue
Connect your phone to the computer with a good quality micro-USB cable
If everything has been done OK, Odin should immediately recognize your phone and you should see a message saying "Added" in Odin. If you don't see this, then you may need to check the drivers are properly installed.
Click on the PDA tab in Odin and navigate to the twrp tar file you earlier downloaded. Select this file and click OK.
You should have the Auto-Reboot and F-Reset Time boxes checked in Odin. Please do not check or uncheck any other boxes!
Click on the Start button at the bottom to start flashing TWRP and wait until you see PASS and a green (or blue) box fully displayed. Your phone will automatically reboot after this although it may not be able to boot since you don't have an OS installed. You may disconnect the cable and close Odin after you see the PASS message. If you see FAIL, then disconnect, remove the phone battery and try again.
If you successfully flash TWRP, then you may proceed to reinstalling your ROM.
1. Download the zip file in the thread below <<http://forum.xda-developers.com/showthread.php?t=2658486>>
2. Save to a recognizable location on your phone's SD card. If you can't install files to your phone via your PC, then you may save to a micro SDHC card using another micro-SDHC compatible device (camera, another phone, card reader/writer etc).
3. Boot into recovery mode
4. Select Install from the TWRP menu and navigate to the zip file you download. Swipe the arrow key to confirm installation and wait for installation to be complete
5. When installation is complete, clear your cache and dalvik and reboot system and you are good to go.
Hope this works for you. If it does, please remember to hit the thanks button and let me know.
Larry2999 said:
You will find the full link here ...<http://forum.xda-developers.com/showthread.php?t=2658486>
Download Odin.
http://fortedge.com/downloads/Odin307.zip
Download the Odin flashable custom recovery file via the following link ...
<http://techerrata.com/browse/twrp2/d2att>. You need one of the more recent images ending in *.tar e.g. the one below
<http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.0-d2att.tar>
Install Samsung Kies on your PC if you don't have this already (this will be useful for the drivers)
Install the twrp tar file to an easily remembered location on your PC
Extract the Odin zip to get the executable file (*.exe)
Click on the exe file to run Odin
Now boot your phone into download mode by powering off completely then holding down the Power + Home + Volume Down buttons simultaneously until you see a warning message.
Press the Volume Up button to continue
Connect your phone to the computer with a good quality micro-USB cable
If everything has been done OK, Odin should immediately recognize your phone and you should see a message saying "Added" in Odin. If you don't see this, then you may need to check the drivers are properly installed.
Click on the PDA tab in Odin and navigate to the twrp tar file you earlier downloaded. Select this file and click OK.
You should have the Auto-Reboot and F-Reset Time boxes checked in Odin. Please do not check or uncheck any other boxes!
Click on the Start button at the bottom to start flashing TWRP and wait until you see PASS and a green (or blue) box fully displayed. Your phone will automatically reboot after this although it may not be able to boot since you don't have an OS installed. You may disconnect the cable and close Odin after you see the PASS message. If you see FAIL, then disconnect, remove the phone battery and try again.
If you successfully flash TWRP, then you may proceed to reinstalling your ROM.
1. Download the zip file in the thread below <<http://forum.xda-developers.com/showthread.php?t=2658486>>
2. Save to a recognizable location on your phone's SD card. If you can't install files to your phone via your PC, then you may save to a micro SDHC card using another micro-SDHC compatible device (camera, another phone, card reader/writer etc).
3. Boot into recovery mode
4. Select Install from the TWRP menu and navigate to the zip file you download. Swipe the arrow key to confirm installation and wait for installation to be complete
5. When installation is complete, clear your cache and dalvik and reboot system and you are good to go.
Hope this works for you. If it does, please remember to hit the thanks button and let me know.
Click to expand...
Click to collapse
Odin seems to stop working and crashes when i try to flash TWRP.
Ozzie 45 said:
Odin seems to stop working and crashes when i try to flash TWRP.
Click to expand...
Click to collapse
How far did you get and what was the <error> message you got?
---------- Post added at 10:10 PM ---------- Previous post was at 10:03 PM ----------
Larry2999 said:
How far did you get and what was the <error> message you got?
Click to expand...
Click to collapse
You may also try Odin 3 v1.85 if the v 3.07 didn't work. I've been looking for a safe download link for that online but I've not been able to find one. You may try searching for it online.
Larry2999 said:
How far did you get and what was the <error> message you got?
---------- Post added at 10:10 PM ---------- Previous post was at 10:03 PM ----------
You may also try Odin 3 v1.85 if the v 3.07 didn't work. I've been looking for a safe download link for that online but I've not been able to find one. You may try searching for it online.
Click to expand...
Click to collapse
Here is Odin 1.85
Or you could try putting a room on an SD card. That's why I always check to see if a room is there before flashing
Sent from my SGH-I747 using Tapatalk

[Q] Please Help! Flashing errors

Samsung Galaxy s3 T-mobile SGH-T999 4.3 jellybean
I have been trying for a few days to flash my phone but no luck. All I want is to get cyangenmod but I encounter errors everywhere I go. I have tried the simple method provided by cyanogenmod themselves but at the end of the process it boots me up into recovery mode telling me that I might lose root and asking that if I want to fix it. No matter what I choose it decides to boot up into regular touchwiz with no apparent changes. I have tried the mobile odin method but it comes up with an error and boots up yet again. It came up with an error but the screen turned off before I could read any further. I have tried flashing the rom via rom manager but everytime I do it boots me up into recovery mode with an error and eventually asks me that same question regarding root just before returning me back to touchwiz. I have even tried using odin307(which I used to root my phone) but it no longer recognizes my phone. I have no idea what to do. My phone still works fine although I get more errors concerning google application after a factory reset but I can still use it no problem. Also, whenever I try to boot up into recovery mode it just shows up with that cyanogenmod icon and then it dissapears just before having it boot up normally so i can no longer boot up into recovery mode. I have downloaded clockworkmod recovery but no luck. I have done so many things that I wouldn't be surprised if my phone turned out to be broken now. whenever I boot up into download mode it now tells me that everything is custom. I have heard of problems concerning knox but when I rooted my phone it didn't it didn't seem to get rid of it. This is really driving me nuts and I now hate samsung for having it made so hard to tweak anything in this phone. Does anyone know of a way get passed all of this stuff and flashing the rom? is my phone broken now? Any help would be greatly appreciated.
It helps a lot if you included exactly what errors you saw. A recovery log, what exactly you're trying to flash, and any other related details goes a long way.
If odin doesn't see your phone its probably a driver issue. What does it say in device manager?
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
It helps a lot if you included exactly what errors you saw. A recovery log, what exactly you're trying to flash, and any other related details goes a long way.
If odin doesn't see your phone its probably a driver issue. What does it say in device manager?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
As you can see, I am a complete noob when it comes to this stuff so I apologize in advance if I don't answer your questions in the correct manner.
If you are talking about the phone drivers, I had already installed them some time ago. I have even installed kies and kies3. Odin recognized my phone before I did all of this since it was what I used to root my phone. I am still able to access the phone's files through my computer.
when I used rom manager it would give me an error right after the whole backup process and show me recovery mode. I would try to look up the same rom via the recovery directory but it would give me the same error message. If i clicked on the reboot option, it would boot me up to stock. If I clicked on the **go back** option a couple of times it would give me this message.
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
*Go back*
no matter what I clicked on, it would boot me up into stock yet again.
I tried doing this again just now and it turned off. it then showed that small strip of blue at the top left that it usually shows before booting up into recovery mode and the screen turned off shortly after. at this point I was unable to turn on the phone even with the charger on. I was only able to turn it on after booting it up into download mode.
This same root message appeared when I tried to flash using the cyanogenmod website method. the only difference was that it only showed this message and not the whole recovery menu.
The device manager reads it as "Samsung device"
Ok, first thing you should do is uninstall kies. Odin usually wont work if its installed. If it still fails to see it in odin, uninstall your drivers through device manager, then install the stand alone driver pkg from my sig. (Use the second or third newest to start, the latest should work, but its had a lot more changes for the S5 and Note3.)
Once you get Odin working, download TWRP and flash. (Put the file in PDA if using Odin v3.07, or put it in AP if v3.09). See my sig for everything you need. (Get the .tar or .tar.md5 file for flashing in Odin btw.)
Next boot recovery and flash your rom. A factory reset would probably a good idea at this point, but you can try without first if you want.
If you have any questions or problems feel free to ask. Most of us dont mind helping at all, so long as you are willing to make an effort to help yourself first.
Good luck!
Sent from my SGH-T999 using Tapatalk
---------- Post added at 02:16 AM ---------- Previous post was at 02:15 AM ----------
Oh, and Sammys devices wont turn on when plugged in. This is perfectly normal.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Ok, first thing you should do is uninstall kies. Odin usually wont work if its installed. If it still fails to see it in odin, uninstall your drivers through device manager, then install the stand alone driver pkg from my sig. (Use the second or third newest to start, the latest should work, but its had a lot more changes for the S5 and Note3.)
Once you get Odin working, download TWRP and flash. (Put the file in PDA if using Odin v3.07, or put it in AP if v3.09). See my sig for everything you need. (Get the .tar or .tar.md5 file for flashing in Odin btw.)
Next boot recovery and flash your rom. A factory reset would probably a good idea at this point, but you can try without first if you want.
If you have any questions or problems feel free to ask. Most of us dont mind helping at all, so long as you are willing to make an effort to help yourself first.
Good luck!
Sent from my SGH-T999 using Tapatalk
---------- Post added at 02:16 AM ---------- Previous post was at 02:15 AM ----------
Oh, and Sammys devices wont turn on when plugged in. This is perfectly normal.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thank you for the timely and thorough responses.
Okay so odin is now reading my device. It just isn't reading my device while on download mode though.
I tried the .tar version first and this is what came up:
C:\Users\Jerry\Desktop\openrecovery-twrp-2.4.0.0-d2tmo.tar
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I attempted this four times and they all ended with "fail" at the top
I then attempted the .tar.md5 and I received this.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> openrecovery-twrp-2.3.1.0-d2tmo.tar.md5 is invalid.
<OSM> End...
It seems like it is not even reading this file. This came up before even connecting my device. I tried a couple versions of this but they all had the same result.
My phone then asked to update clockworkmodrecovery and I did.( I actually installed the rom installer version) After doing so, I decided to try my luck and boot up into recovery mode. This time I was successful in booting up into recovery mode although it still showed me that cyanogenmod icon right before getting there. I then went on to install a zip from sd card only to receive the same message I have been receiving since the very beginning:
Installing: /sdcard/0/cm-11-20140217-NIGHTLY-d2tmo.zip
Finding update package...
Finding update package...
Opening update package...
Installing update...
assert failed: THEN A BUNCH OF THESE getprop(" ro.bootloader") =="T999VVLUVUBMK4" (WITH VARIATIONS AFTER T999)
E: Error in /data/media/0/cm-11-20140217-NIGHTLY-d2tmo.zip
(status 7)
Installation aborted.
After error I clicked on the "reboot now" option, only to come up with this message again:
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
This message is what seems(at least to me) to be the main problem. It has appeared after a successful cyanogenmod standard installation (the one from their website) only to restore everything to default after I click on it. Instead of rebooting normally like cyanogenmod said, it would bring me up to this screen. so it seems that even if i were to have a successful installation, this would keep it from going through
I also tried mobile odin but, once again, showed an error that disappeared before I could remember anything.
Thanks your help is really appreciated.
If odin isnt seeing it in download mode try reinstalling your drivers, maybe a different version. Also, check what version of odin you are using. If 3.07, try 3.09. If using 3.09, try 3.07.
Another thing I noticed is the twrp you were trying to use is quite old. Try 2.7.0.0. If you still cant do this from Odin, use the Goo Manager app from the store. (Press menu, then install openrecovery script)
Also, install Terminal Emulator, and enter this:
getprop ro.bootloader
Tell me what it returns. Finally, if you want, open the rom zip file and find the updater script. Open with Notepad++ and delete the assert lines at the top. Save then delete the sig files from the rom, rezip and flash. (There are 3 signature files, cert, manifest, and another. If found, delete, if not, ignore)
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
If odin isnt seeing it in download mode try reinstalling your drivers, maybe a different version. Also, check what version of odin you are using. If 3.07, try 3.09. If using 3.09, try 3.07.
Another thing I noticed is the twrp you were trying to use is quite old. Try 2.7.0.0. If you still cant do this from Odin, use the Goo Manager app from the store. (Press menu, then install openrecovery script)
Also, install Terminal Emulator, and enter this:
getprop ro.bootloader
Tell me what it returns. Finally, if you want, open the rom zip file and find the updater script. Open with Notepad++ and delete the assert lines at the top. Save then delete the sig files from the rom, rezip and flash. (There are 3 signature files, cert, manifest, and another. If found, delete, if not, ignore)
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Hey man I was finally able to flash my rom! I updated both the drivers and odin and was able to successfully install the recovery file. It still did not install cyanogenmod reading an md5 error and "error executing updater binary in zip" though. anyway I installed AOKP instead and it finally worked. I think the cyanogenmod files that I downloaded were just incompatible with my device or faulty (even though i tried like 10. maybe something wrong with my phone?). Anyway I am really grateful for all of your help. I was so happy after I was finally getting it. It seriously frustrated the heck out of me. I no longer hate my samsung and am quite liking this new rom. Thanks again!
Glad I could help and that you seem to be happy with it so far!
Sent from my SGH-T999 using Tapatalk

NO OS after wiping

I installed a Rom on my Sprint Galaxy Note 4 and when I installed it, it wanted me to wipe, so I did. The rom didn't take and now I can't get any rom, factory or otherwise to not fail in odin.
I have no phone an am freaking out. I have TWRP when I load into recovery, but no rom will take.
PLEASE help me.
My phone just updated to 5.1 lollypop and I rooted after. Root took, then installed rom, now i try to start and samsung comes up, the phone buzzes over and over again
What do you see on the screen when trying to boot up? Lollipop takes forever to start when you first flash. Give it 15 to 20 minutes at least.
There is no 5.1 u mean 5.01 hehe
w7excursion said:
What do you see on the screen when trying to boot up? Lollipop takes forever to start when you first flash. Give it 15 to 20 minutes at least.
Click to expand...
Click to collapse
Just Samsung...it buzzes, then samsung, then it buzzes.
It doesn't boot. I was able to get auto root to take, but any rom
N910PVPU1ANIE_N910PSPT1ANIE_SPR
N910PVPU1ANIE_N910PSPT1ANIE_N910PVPU1ANIE_HOME.tar.md5
N910PVPU1ANK2_N910PSPT1ANK2_XAS
N910PVPU1ANK2_N910PSPT1ANK2_N910PVPU1ANK2_HOME.tar.md5
N910PVPU1ABOB7_N910PSPT1BOB7_SPR
N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar.md5
I get this...
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Odin has a problem each time...
Any suggestions?
Ok, sounds like you took the OE1 update. You can fix this.
If in fact you are on OE1 the notarized rom by @SaintZ93 will get you up and running.
It's located here in the OP:
http://forum.xda-developers.com/showthread.php?t=3099382
Wipe the usual x 3 and flash it. You'll be good to go.
Quality rom by a quality guy.
jhill110 said:
Ok, sounds like you took the OE1 update. You can fix this.
If in fact you are on OE1 the notarized rom by @SaintZ93 will get you up and running.
It's located here in the OP:
http://forum.xda-developers.com/showthread.php?t=3099382
Wipe the usual x 3 and flash it. You'll be good to go.
Quality rom by a quality guy.
Click to expand...
Click to collapse
How do I get it over to my phone? I'm not sure how to flash it since the file is a zip and odin wants a tar file.
I removed the SD card and put the rom on that from my computer
I just pushed up on the volume, held the center button, and the power button, which pulled up dowload mode,but when I flashed the Noterized rom, it says:
install sd card
finding update package
opening update package verifying update package
E:footer is wrong
E:signature verification wrong
Thanks so much for trying to help
Dave
download the zip file to your pc then extract or unzip it, you will find the .tar file inclosed.
Sent from my SM-G920V
stealyourface1 said:
download the zip file to your pc then extract or unzip it, you will find the .tar file inclosed.
Sent from my SM-G920V
Click to expand...
Click to collapse
Extracting now..I'll update in a minute
Thanks so much
stealyourface1 said:
download the zip file to your pc then extract or unzip it, you will find the .tar file inclosed.
Sent from my SM-G920V
Click to expand...
Click to collapse
I see a META-INF
noterized
system
I don't see a tar file
wascapsfan said:
I see a META-INF
noterized
system
I don't see a tar file
Click to expand...
Click to collapse
That's because it's a recovery flashable zip.
You need to flash it in recovery. If you don't have custom recovery, google "Sprint Galaxy Note 4 TWRP" or see link below. Download 2.8.6, (latest as of this date) odin it then flash the rom.
How to :
Start TWRP (vol up & home & power) , goto wipe, factory reset x 3. Goto advanced wipe, tick dalvik, system, data and cache. Wipe those x 3
DO NOT WIPE EXTERNAL SD CARD!
Go to install and find the rom zip on your external sd card , install it and give it all the time it needs to install. 10 minutes or more... Maybe 15.
EDIT: Here's the link to TWRP :
https://dl.twrp.me/trltespr/
jhill110 said:
That's because it's a recovery flashable zip.
You need to flash it in recovery. If you don't have custom recovery, google "Sprint Galaxy Note 4 TWRP" or see link below. Download 2.8.6, odin it then flash the rom.
How to :
Start TWRP (vol up & home & power) , goto wipe, factory reset x 3. Goto advanced wipe, tick dalvik, system, data and cache. Wipe those x 3
DO NOT WIPE EX SD CARD!
Go to install and find the rom zip on your ex sd card , install it and give it all the time it needs to install. 10 minutes or more... Maybe 15.
EDIT: Here's the link to TWRP :
https://dl.twrp.me/trltespr/
Click to expand...
Click to collapse
I'm looking in the right direction here.... :good:
I'm still on the Yellow Sprint Spark page..
wascapsfan said:
I'm looking in the right direction here.... :good:
I'm still on the Yellow Sprint Spark page..
Click to expand...
Click to collapse
Patients...
SUCCESS!!!!!!! You guys are AWESOME!!!!!!
THANK YOU THANK YOU
wascapsfan said:
SUCCESS!!!!!!! You guys are AWESOME!!!!!!
THANK YOU THANK YOU
Click to expand...
Click to collapse
Congrats! A small piece of advice... When a new update is released, wait a little while and watch what is being said about it.
Again, congratulations on on bringing your phone back from the dead...
jhill110 said:
That's because it's a recovery flashable zip.
You need to flash it in recovery. If you don't have custom recovery, google "Sprint Galaxy Note 4 TWRP" or see link below. Download 2.8.6, odin it then flash the rom.
How to :
Start TWRP (vol up & home & power) , goto wipe, factory reset x 3. Goto advanced wipe, tick dalvik, system, data and cache. Wipe those x 3
DO NOT WIPE EX SD CARD!
Go to install and find the rom zip on your ex sd card , install it and give it all the time it needs to install. 10 minutes or more... Maybe 15.
EDIT: Here's the link to TWRP :
https://dl.twrp.me/trltespr/
Click to expand...
Click to collapse
I'm in the same boat too and am on my way to Following the instructions here, But my question is when you sat DO NOT WIPE EX SD CARD, we're talking about the micro SD card right? i can wipe out internal Storage without a problem?
HunterKiotori said:
I'm in the same boat too and am on my way to Following the instructions here, But my question is when you sat DO NOT WIPE EX SD CARD, we're talking about the micro SD card right? i can wipe out internal Storage without a problem?
Click to expand...
Click to collapse
Yes and yes. If you wipe internal storage you'll likely lose your pic's and media.
Imo, it isn't necessary to wipe internal storage.
jhill110 said:
Yes and yes. If you wipe internal storage you'll likely lose your pic's and media.
Imo, it isn't necessary to wipe internal storage.
Click to expand...
Click to collapse
I keep my stuff on my SD card mostly. I like having a clean sorage if i flash a rom
HunterKiotori said:
I keep my stuff on my SD card mostly. I like having a clean sorage if i flash a rom
Click to expand...
Click to collapse
Then your good.
Good for you.
---------- Post added at 02:49 PM ---------- Previous post was at 02:48 PM ----------
wascapsfan said:
SUCCESS!!!!!!! You guys are AWESOME!!!!!!
THANK YOU THANK YOU
Click to expand...
Click to collapse
Good for you.:good:
What next
After flashing OE1 the notarized rom i try to downgrade again to ob7 rom or nk2 so i could unlock it for international use but won't accept the downgrade any clue pls??????

S3 will only boot to Samsung logo. Please help.

I recently lost my S4. Loved that phone! Still hoping that some good samaritan will return it. This S3 was my son's phone. When power button is pressed, it freezes at the Samsung Galaxy SIII logo. It can only power on to recovery and download modes. Tried everything in recovery, but don't know what to do in download mode. It says ODIN MODE, PRODUCT NAME: SGH-I747, CURRENT BINARY and SYSTEM STATUS: Custom, QUALCOMM SECUREBOOT: ENABLE, Warranty Bit: 1, BOOTLOADER AP SWREV: 3 When plugged into charger, the phone powers on and a gray battery image appears before SAMSUNG and Samsung logo. The phone will only turn off when the battery is removed. He tried everything he could to get the phone to work. For my own satisfaction, I would like to learn more about the process and try to get this operational. I am not familiar with the technical language, but am eager to learn. Right now, I'm using my S2. Is there anyone who can help me with the S3?
Here's what I recommend:
1) download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=j...07763241,d.dmo
2) download the tar version of TWRP 2.8.7.0 from here: https://dl.twrp.me/d2att/
3) download the latest cm12.1 for the phone from here ( http://www.cmxlog.com/12.1/d2att/) and save it to a micro SD card;
4) download the version of cm12.1 gapps you want from here (https://wiki.cyanogenmod.org/w/Google_Apps) and save it to the same sd card where you saved CM12.1;
5) place the micro SD card into the phone;
6) boot the phone into download mode;
7) open Odin 3.07 and uncheck everything except f. reset time;
8) click on PDA and browse to the tar TWRP file and select it;
9) connect the phone and it should show up as a com port in Odin;
10) flash TWRP;
11) when you see the word RESET in the status window, remove the USB cable, remove the battery, replace the battery, use the button combination to get into recovery which should now be TWRP;
12) perform a full wipe of system, data, and cache;
13) flash CM12.1 and gapps from the micro SD card;
14) reboot.
If you cannot get a signal, you probably need to update the modem and bootloader.
The above is assuming that your bootloader is unlocked, if it is not then the above operation would be less than ideal, so the first thing you need to know is if indeed a previous unlocking procedure has been performed because if not you need to load a stock OS.
Sent from my SM-N910F using Tapatalk
The ATT s3 bootloader has never been locked.
There is no stock ATT ROM beyond 4.1.1 that can be flashed in Odin. The only way to flash a stock ROM beyond 4.1.1 would be via TWRP or CWM.
Thank you for your recommendation Audit 13.
On Step 1), I could not download the Odin 3.07. Do you have another link?
On Step 2), I downloaded twrp-2.8.7.0-d2att.img.tar to my computer.
On Step 3), I extracted the 20151230 Nightly files to my micro sd.
On Step 4), I thought my OS was Android 4.0 (Ice Cream Sandwich). I selected download from version CyanogenMod 12.1 (Android 5.1) Open GApps. On the Open GApps page, there are choices. Would I select ARM platform, 4.4 android, and stock variant? I am not sure.
Odin 3.07: http://forum.xda-developers.com/attachment.php?attachmentid=1168421
Files that are to be flashed from TWRP must not be unzipped. They are flashed by TWRP in their zipped format.
Your OS could not have been ICS because I see that warranty bit is mentioned in your posts which means the phone was running at least a JB bootloader and modem.
Gapps are optional at the moment as they are not required for the phone to boot CM. The important thing is to get your phone up and running so you can determine the bootloader and modem currently installed on the phone.
If you want to install gapps, choose ARM, 5.1, and nano: http://opengapps.org/?api=5.1&variant=nano
Thanks audit13! I have gone through step 10. In Odin, it says PASS! in the upper left. In the status window below it says:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/008> Removed!!
<ID:0/008> Added!!
Am I supposed to click on RESET in Odin? I have not seen the word RESET in the status window. The phone is still connected via USB. Should I continue to wait, or should I press EXIT?
Sorry, if I'm not understanding. I chose not to download the Gapps at this time. I just want this phone to boot to the home screen.
audit13 said:
Odin 3.07: http://forum.xda-developers.com/attachment.php?attachmentid=1168421
Files that are to be flashed from TWRP must not be unzipped. They are flashed by TWRP in their zipped format.
Your OS could not have been ICS because I see that warranty bit is mentioned in your posts which means the phone was running at least a JB bootloader and modem.
Gapps are optional at the moment as they are not required for the phone to boot CM. The important thing is to get your phone up and running so you can determine the bootloader and modem currently installed on the phone.
If you want to install gapps, choose ARM, 5.1, and nano: http://opengapps.org/?api=5.1&variant=nano
Click to expand...
Click to collapse
see step 7 and 11 of my post above.
Yay!! My phone works. Thank you Audit 13.
Great! Are you running CM or some other ROM?
It is running CM. But I would like to get it back to the android OS, when we first got the phone. Is that possible?
Also, somewhere during the process, it said my phone was unrooted and asked if I would like to root it. I declined, since I wasn't sure what that was. Sorry for my lack of knowledge.
audit13 said:
Great! Are you running CM or some other ROM?
Click to expand...
Click to collapse
I've been exploring the phone with the CM 12.1 and I am very satisfied. Thank you, Audit 13! Although at first, it looks so different, I am finding many positives. Most importantly, it's operational, which is what I wanted. It is running android 5.1.1, and I have so much storage. Over 11 gbs! Sorry for my ignorance, but a newer android OS is better, right?
I am planning to flash thru TWRP the Gapps you suggested. ARM, 5.1, and nano. I will make a backup before, in case something weird should happen. I copied the unzipped files to my micro sd. If I should succeed, I will go to At&t to get a sim card. Can't wait to use this phone!
I will let you know what happens.
karene said:
It is running CM. But I would like to get it back to the android OS, when we first got the phone. Is that possible?
Also, somewhere during the process, it said my phone was unrooted and asked if I would like to root it. I declined, since I wasn't sure what that was. Sorry for my lack of knowledge.
Click to expand...
Click to collapse
For root on cm13, you need to enable developer options and enable root access for apps, adb, or both.
For cm12.1, just flash supersu from twrp.
I installed gapps on cm 12.1, but did not flash supersu. I am so happy to have this phone working. Thank you Audit 13!!
audit13 said:
For root on cm13, you need to enable developer options and enable root access for apps, adb, or both.
For cm12.1, just flash supersu from twrp.
Click to expand...
Click to collapse
You're very welcome. We are all here to help.

Can't get out of ODIN mode

I tried to install TWRP, but I had some problem with that. After I tried couple of time I stack in Downloading mode.
Now I can't get out of odin mode, no mather what I do.
Make sure that the recovery is compatible with your phone
Or
Try to download ofw riginal firmware of s4 mini
And flash it
yahiahedna said:
Make sure that the recovery is compatible with your phone
Or
Try to download ofw riginal firmware of s4 mini
And flash it
Click to expand...
Click to collapse
I tried both but dosn't helped.
Sent from my HUAWEI G6-U10 using Tapatalk
Hold the power button it will end the download mode.
Have you flashed the right TWRP or FW to your phone The S4 mini are have different Versions.
9190 / 9192 / 9195 and the newer Device 9192 I and 9195 I.
bierma32 said:
Hold the power button it will end the download mode.
Have you flashed the right TWRP or FW to your phone The S4 mini are have different Versions.
9190 / 9192 / 9195 and the newer Device 9192 I and 9195 I.
Click to expand...
Click to collapse
Thanks.
I finaly find right TWRP for my device 9195I, and I finaly start TWRP but now I have new problem.
I tried to install LineageOS, but I get an error:
"could no detect filesystem for /dev/block/bootdevice/by-name/system, assuming ext4 mount: failed to mount /dev/block/bootdevice/by-name/system at /system: No such file or directory"
I tryed to add a photo but I don't know how??
Any idea where is the problem?
Try to reboot from TWRP to Recovery
Than install the ROM
Make a backup!
Reboot into recovery
Wipe data (You may get a "staus 7" error if you fail to wipe.)
Install the Current ROM
Optionally install Gapps
Boot phone into normal mode
bierma32 said:
Try to reboot from TWRP to Recovery
Than install the ROM
Make a backup!
Reboot into recovery
Wipe data (You may get a "staus 7" error if you fail to wipe.)
Install the Current ROM
Optionally install Gapps
Boot phone into normal mode
Click to expand...
Click to collapse
I tred but the problem is the same.
"could no detect filesystem for /dev/block/bootdevice/by-name/system, assuming ext4 mount: failed to mount /dev/block/bootdevice/by-name/system at /system: No such file or directory"
OK, go complete back to Stock, flash the ROM with Pit.file and than try again to flash TWRP and Los 14.1
bierma32 said:
OK, go complete back to Stock, flash the ROM with Pit.file and than try again to flash TWRP and Los 14.1
Click to expand...
Click to collapse
Pit file?
Where can I get it?
How to flash?
Thanks.
Sent from my HUAWEI G6-U10 using Tapatalk
Install samfirm https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Download a multiple firmware, in side of CSC.image you find the pit.file.
bierma32 said:
Install samfirm https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Download a multiple firmware, in side of CSC.image you find the pit.file.
Click to expand...
Click to collapse
As you sugested I downloaded stock firmware for my device" I9195IXXU1AQA7.....tar.md5", but I don't find any pit file.
Copy the CSC.img to a sperate Folder, unzip the image and than you have got the Pit.file.
https://www.pocketpc.ch/attachments...galaxy-s7-s7-edge-g930f-g935f-unbenannt5.jpg?
Under Pit you must select the the file and actived the Repartion Option.
Samfirm
https://www.pocketpc.ch/attachments...-galaxy-s7-s7-edge-g930f-g935f-unbenannt1.jpg
Odin
https://www.pocketpc.ch/attachments...amsung-galaxy-s7-s7-edge-g930f-g935f-odin.png
bierma32 said:
Copy the CSC.img to a sperate Folder, unzip the image and than you have got the Pit.file.
https://www.pocketpc.ch/attachments...galaxy-s7-s7-edge-g930f-g935f-unbenannt5.jpg?
Under Pit you must select the the file and actived the Repartion Option.
Samfirm
https://www.pocketpc.ch/attachments...-galaxy-s7-s7-edge-g930f-g935f-unbenannt1.jpg
Odin
https://www.pocketpc.ch/attachments...amsung-galaxy-s7-s7-edge-g930f-g935f-odin.png
Click to expand...
Click to collapse
Thank you for you help, but I finaly managed to install stock firmware, install TWRP recovery and lineageOS.
The problem was "hidden.img.ext4" file in stock firmware. After I delete this file, there was no more problem with installation.
Thanks again.
Best regards.

Categories

Resources