Related
Hi!
I was trying to upgrade my Galaxy Captivate following the instructions on this thread http://forum.xda-developers.com/showthread.php?t=783403
First I tried the KIES option, but ended in the phone stuck on a black screen after 2 minutes of the S logo on it.
So, I then tried with ODIN using both package, first with the original, but ended getting an error "E:Can't mount /dev/block/stL10 (Invaild argument)"
And then with Richthofen's integrated package which seems like fixed that issue. indeed did it, but not fixed the original issue, after this one I ended in the same stage than with the KIES upgrade.
I can enter on recovery mode and move using the volume up and down button, however, the "power" button to select any of the option do nothing.
I tried to connect with adb and indeed see it (when is on recovery mode)
adb devices
List of devices attached
10004cb6cc04 recovery
But can't do anything on the phone, not even reboot it with adb, the process get's stuck and the phone is not rebooted.
Anyone have any idea of what I can do now? send it to Samsung is not an option since I bought this phone in USA and I live in Argentina, this phone is not available in the country yet.
Thanks in advance.
Thread moved to Captivate Q&A.
You used a rom with a kernel for Samsung Galaxy I-9000, I went through this also. The I-9000 has a "hard" home key and the kernel is telling your phone that it does also. Are you sensors acting backwards; up/down = left/right?; if so you need to flash back to stock with Odin 3 http://forum.xda-developers.com/showthread.php?t=731989
I was able to get into download mode by using the vol key like it says but I repeatedly tapped "menu" and "Home" when the little triangle kept popping up (I mean really fast tapping) and it worked. It's really hard to brick these, thought I did more than once myself.
Follow the instructions, it works great. I've had too use it more than once.
Lesson here, don't use any package that's based on a kernel for different hardware; especially the I-9000; unless specifically stated that it has been modified specifically for your phone.
http://forum.xda-developers.com/showthread.php?t=731989 saved my life! I was so angry with me for being such an idiot!. I lost all the contents on the phone, but at least got my phone working again.
By the way, to put it in download mode what I did was, remove the battery, put it back, press volume up + down and plug the phone to USB.
Thanks a lot Tazman171
No problem, just passing on info that was passed to me by helpful people at this sight. And yep, the way you did it was right, I was thinking of the recovery menu and selecting reinstall packages option, I actually was able to do it with the way I described above.
tazman171 said:
You used a rom with a kernel for Samsung Galaxy I-9000, I went through this also. The I-9000 has a "hard" home key and the kernel is telling your phone that it does also. Are you sensors acting backwards; up/down = left/right?; if so you need to flash back to stock with Odin 3 http://forum.xda-developers.com/showthread.php?t=731989
I was able to get into download mode by using the vol key like it says but I repeatedly tapped "menu" and "Home" when the little triangle kept popping up (I mean really fast tapping) and it worked. It's really hard to brick these, thought I did more than once myself.
Follow the instructions, it works great. I've had too use it more than once.
Lesson here, don't use any package that's based on a kernel for different hardware; especially the I-9000; unless specifically stated that it has been modified specifically for your phone.
Click to expand...
Click to collapse
Hey right now my phone is "bricked" because of a botched JPC Froyo ROM install and I have no way of getting it into download mode. None of the methods on the "One-Click Stock ROM" work, and a few other ones suggested don't either. I'm curious as to how you did it with tapping menu and home, etc. Would you mind posting up some instructions?
Sorry about the late reply, it was recovery mode that I got into, not download mode. You might have one of the phones that won't support the 3/2 button methods of getting to the download/recovery menus. It worked for me because my phone does support that method, it was just the I-9000 had switched my buttons around.
Save your dead/bricked device! Overall a straightforward process. Simple recovery using SD card to load correct bootloader and be able to ODIN stock firmware.
Successfully performed on a locked bootloader Note 4 from Verizon, using another locked bootloader Note 4 from Verizon. Should be equally possible with other devices as well as the T Flash function does not check the device model, and writes the entire firmware, according to the included or specified PIT file into the SD card.
Requirements:
Secondary Samsung device with working download mode and microSD slot
Odin version appropriate to the firmware version you are trying to install
16+ GB microSD card
Samsung drivers installed on your PC
Steps:
1) Find and download the correct FULL firmware for your device, of the same or newer version than was on the device previously. These are frequently available from AFH, amongst other sites. A "repair firmware" may be sufficient ONLY IF IT INCLUDES ABOOT and BOOT partitions.
2) Download the correct version of Odin for your firmware
3) Open Odin, set up your full firmware into the AP/PDA slot.
4) Tick the T Flash option in the settings.
5) Insert a 16+ GB card into the SD slot on your working Samsung device
6) Boot into download mode, and connect to computer. Ensure the device shows up in Odin. If not, check drivers and restart (and reconfigure) Odin.
7) Start flash. It may fail at a certain point but this is OKAY. As long as the ABOOT and BOOT partitions have flashed, the procedure will work.
8) Remove SD from the working device and insert it into the bricked device.
9) Hold VOLUME DOWN + HOME + POWER, or use a USB jig to enter into download mode on the dead device. It will now magically work, as it reads the partitions from the SD card.
10) Reflash the correct firmware in Odin to the bricked device.
Hope I was able to help. Do note that this will NOT solve issues with your device if it has PHYSICAL eMMC issues (cracked solder balls, bad chip, bad connections, etc, etc).
The "magic" SD card will only work on the device it was intended for. Don't attempt "miracles" by say, trying to boot firmware intended for a different model on your device. That may cause permanent damage, for which I will not be held responsible.
This tutorial should be equally acceptable for other devices. I am posting it here because it worked successfully on my Note 4, and I'm assuming other people here may have the same issue. Originally I tried this on an S5 with heavy motherboard damage, which would only render a download mode screen, but would not flash anything to the device.
Anyone with an interest in making a donation, please contact me for donation info or donate to your charity of choice
Most information presented here is publicly available but there was no simple/accurate way detailing the process, so I assumed it would be nice to have all info aggregated in one place.
Please, please, please - I have a hard bricked N910F (no recovery, no download, no power). Can you send me the files to unbrick it?
Thanks in advance
These guides are all well and good
The problem is most people don't have a secondary note 4.
It'd be best if people w/ different models of this phone (SM-N910W8 , SM-N910F, Etc.) could upload image files here & form a directory. There isn't a definitive hard brick solution guide on this site because people won't do that.
Exactly. If only someone with a working Note 4 could create a SDCard restore image and share it. The procedure is simple, safe and would take 30 minutes. It would help a LOT of people.
✔ Auto Reboot
✔ F.Reset Time
✔ T Flash
So I need to Tick those 3 or ONLY T Flash on Odin3 v3.09?
2 of my colleagues had hard brick their Note 4 SM-N910G and they have zero knowledge about rooting. The phone cannot :
➡ Switched ON
➡ No Red LED light while charging
➡ No battery icon when changing
➡ QHSUSB_BULK when connected to PC
Can your method solve the problem? I do have a few friends who are using Note 4 so I guess if this works, I can borrow one of the working phones to do the 'MAGIC' SD Card..
bietoff0728 said:
Auto Reboot
F.Reset Time
T Flash
So I need to Tick those 3 or ONLY T Flash on Odin3 v3.09?
2 of my colleagues had hard brick their Note 4 SM-N910G and they have zero knowledge about rooting. The phone cannot :
Switched ON
No Red LED light while charging
No battery icon when changing
QHSUSB_BULK when connected to PC
Can your method solve the problem? I do have a few friends who are using Note 4 so I guess if this works, I can borrow one of the working phones to do the 'MAGIC' SD Card..
Click to expand...
Click to collapse
Leave everything checked the way it is when Odin first opens. Then check off T Flash. Don't change anything else.
Symptoms sound identical to this Note 4. It should be possible to save it.
dwegiel said:
Save your dead/bricked device! Overall a straightforward process. Simple recovery using SD card to load correct bootloader and be able to ODIN stock firmware.
Successfully performed on a locked bootloader Note 4 from Verizon, using another locked bootloader Note 4 from Verizon. Should be equally possible with other devices as well as the T Flash function does not check the device model, and writes the entire firmware, according to the included or specified PIT file into the SD card.
Requirements:
Secondary Samsung device with working download mode and microSD slot
Odin version appropriate to the firmware version you are trying to install
16+ GB microSD card
Samsung drivers installed on your PC
Steps:
1) Find and download the correct FULL firmware for your device, of the same or newer version than was on the device previously. These are frequently available from AFH, amongst other sites. A "repair firmware" may be sufficient ONLY IF IT INCLUDES ABOOT and BOOT partitions.
2) Download the correct version of Odin for your firmware
3) Open Odin, set up your full firmware into the AP/PDA slot.
4) Tick the T Flash option in the settings.
5) Insert a 16+ GB card into the SD slot on your working Samsung device
6) Boot into download mode, and connect to computer. Ensure the device shows up in Odin. If not, check drivers and restart (and reconfigure) Odin.
7) Start flash. It may fail at a certain point but this is OKAY. As long as the ABOOT and BOOT partitions have flashed, the procedure will work.
8) Remove SD from the working device and insert it into the bricked device.
9) Hold VOLUME DOWN + HOME + POWER, or use a USB jig to enter into download mode on the dead device. It will now magically work, as it reads the partitions from the SD card.
10) Reflash the correct firmware in Odin to the bricked device.
Hope I was able to help. Do note that this will NOT solve issues with your device if it has PHYSICAL eMMC issues (cracked solder balls, bad chip, bad connections, etc, etc).
The "magic" SD card will only work on the device it was intended for. Don't attempt "miracles" by say, trying to boot firmware intended for a different model on your device. That may cause permanent damage, for which I will not be held responsible.
This tutorial should be equally acceptable for other devices. I am posting it here because it worked successfully on my Note 4, and I'm assuming other people here may have the same issue. Originally I tried this on an S5 with heavy motherboard damage, which would only render a download mode screen, but would not flash anything to the device.
Anyone with an interest in making a donation, please contact me for donation info or donate to your charity of choice
Most information presented here is publicly available but there was no simple/accurate way detailing the process, so I assumed it would be nice to have all info aggregated in one place.
Click to expand...
Click to collapse
did this method work
Wow this is very useful info, If it works.
So @dwegiel, your stating that by ticking T-flash, that tells Odin to flash the bootloader over to the sd card. Which you can then use to boot any note 4 of the model you flashed.
If this is so, then we should be able to make a disk image file to share for each model. That would be great!
Thanks for the info!
Samsung SM-G910S HArd Bricked
Samsung SM-G910S HArd Bricked
@dwegiel i can successfully say that your method work on my Note edge N915V @aaron74 you are also correct that can be done....................but we would of to create the debrick image for all the "OS" version are else it wont work an you cant do it with any Samsung phone it as to be done with the same phone.................meaning if you want to create one for a Note 5 you of to use a note 5 (carrier doesn't matter)
I'm in this situation with my N910G, I have a working one but I don't want to change it, will this alter the working device in any way?
no i wont
Is it possible to recover a hard bricked Note 4 when it won't stay on for more than a few minutes and/or freezes.? I got most of the way through rooting it but it shut down before completion. Reason I wanted to root it was because it got stuck in a bootloop following a recent OTA security upgrade. Running Marshmallow 6.0.1. Incidentally sometimes when it boots up it gets stuck at the Samsung screen but there is a yellow message top left - Set Warranty Bit Kernel. When I read up on this it said knox was tripped, but this was before I had even tried to root it. Thx
bietoff0728 said:
Auto Reboot
F.Reset Time
T Flash
So I need to Tick those 3 or ONLY T Flash on Odin3 v3.09?
2 of my colleagues had hard brick their Note 4 SM-N910G and they have zero knowledge about rooting. The phone cannot :
Switched ON
No Red LED light while charging
No battery icon when changing
QHSUSB_BULK when connected to PC
Can your method solve the problem? I do have a few friends who are using Note 4 so I guess if this works, I can borrow one of the working phones to do the 'MAGIC' SD Card..
Click to expand...
Click to collapse
My 910G is also in the same situation no download mode nothing complete dead phone
Have ypu found the solution plz let me know
I have an F variant (see screenshot for info) . If of any use dont mind uploading an SD backup if anyone up to say the steps needed to be taken..
Hi, i have the sm-n915fy, can anyone just send me a sd image of a stock rom for my phone
Bonez355555 said:
@dwegiel i can successfully say that your method work on my Note edge N915V @aaron74 you are also correct that can be done....................but we would of to create the debrick image for all the "OS" version are else it wont work an you cant do it with any Samsung phone it as to be done with the same phone.................meaning if you want to create one for a Note 5 you of to use a note 5 (carrier doesn't matter)
Click to expand...
Click to collapse
Is there anyway you could send me your image? I can't find anyone else with the Note edge, and I have family photos I want to restore
Has anything else been done with this? Is there a thread for downloading this SD card files?
"It will now magically work,"
As said it really worked for me today for my samsung galaxy note edge(SCL24 SM-915J) dead for 10 months.
At first it didn't worked because my current SCL24 has updated android version . Then I bought another SCL24(now,I have yes 3 working SCL24.)
What I did before trying this thread.
I tried Freeze method for 5 mins, 10 mins, 20,30 , 1 hr, 2,4,.....12 hours, 1 day too. But, it didn't work.(Last year like 5, 10, 20 min was workind for me)
Then I used the cardboard method to attach to my emmc for solving my error reading emmc yesterday, it didn't work either.
But, today this thread worked.Wow thank you so much.
Root SM-T707A on Lollipop with SuperSu - Xposed & Debloated - Part I
The purpose of this thread is to provide several guides (written by myself) to achieve the following on the SM-T707A tablet:
* Part I: Flash Stock Lollipop 5.0.2 <---- YOU ARE HERE!
* Part II: Gain Root access for Lollipop with SuperSU.
* Part III: Flash Xposed Framework thru Flashfire.
* Part IV: Debloat the tablet from both AT&T and most of Samsung stuff.
* Part V: Improve usability and aspect with Xposed Modules.
But first, some words of our sponsors: NO, I'm NOT resposible for any consequence originated from the use of this guide, being that the death of your tablet, your phone, North Korea launching a nuclear strike or the Sixers winning the Larry O'Brien Trophy. Whatever happens to your tablet, it's ON YOU.
Introduction (recommended reading - not mandatory):
Four weeks ago I managed to capture this tablet for a very decent price on eBay. After buying an HTC 10, my bank account was in ashes and I was growing impatient with my unstable iPad mini 2. I wanted to live the full android experience on a tablet, while spending a mere $ 150.00. Buying a Pixel C was clearly out of the question. So, after some research, the T707A had the 8 cores, 3gb of RAM and also the AWS LTE neeeded for my country (Uruguay). Perfect match!
I was already drooling about installing CM and all the stuff to take this beast to the next level. With the tablet in my hands, just 5 minutes of -late- XDA reading made me realize that...CM wasn't happening (Locked BL). The consolation prize was to root the tablet with the infamous kingoroot and use Xposed to eviscerate as much bloat and touchwiz as possible. Sadly, that same kingoroot paired with a not-so-good battery life and the inability to use xposed almost put me back on the market for another tablet.
But...(there's always one) last monday, after several weeks of failures, there was a breakthru. SuperSU was breathing. Minutes later, Xposed modules where flying off the shelves and suddenly, the T707A was back into the game with more speed and less touchwiz feel. Since most of my objectives were met on Monday, if AT&T releases MM and someone helps us pulling that, I would love to achieve the same over MM. But, what didn't worked in this case (updating a rooted device), will have to in MM to manage the same results. At least we can enjoy lollipop in the meantime.
Part I: Flashing Stock Lollipop
If you're standing on Kitkat or, in Lollipop but messed too much with the system and want a fresh start, over the following lines we'll comment on the process of flashing stock kitkat (with odin), and afterwards applying the OTA zip files to reach Lollipop. We can't flash straight to Lollipop because we don't have the firmware for that. So, if you're already on Lollipop and only want SuperSU root, you can use my next guide BUT I STRONGLY SUGGEST you to flash kitkat first and update to lollipop with this guide to raise your sucess chances. Remember that doing that you are going to lose all your files, the flashing process ERASES EVERYTHING. So please BACKUP!
You'll need to download the following files, have an external MicroSD card (on your tablet), a PC and a microUSB cable.
* Odin 3.09
* BL file
* AP file
* CP file
* CSC file
* Update.zip
* Update2.zip
For Odin to work properly, you might need the Samsung USB drivers. Chances are you already have them installed in place. You'll know that in a minute.
Flashing KitKat 4.4.2 with Odin
Extract the Odin.zip in some handy place. Also, move the BL,AP,CP and CSC files to the same folder where Odin was extracted. Last, copy the Update.zip and Update2.zip to your EXTERNAL MicroSD card that's mounted on your tablet.
With your tablet disconnected from the USB cable, open Odin3 v3.09.exe.
We have to put the tablet in Download Mode. Make sure the tablet was turned OFF first. Now press and mantain the HOME and VOL DOWN buttons and then press the POWER button. All 3 buttons at the same time until the screen turns on with a Warning!! message. Now release the 3 buttons and just press the VOL UP to access download mode.
The Android robot will appear with the legend "Downloading...Do not turn off target!!".
Connect the USB cable to your computer and tablet. If done correctly, the Odin screen will show this legend below ID:COM:
"0:[COM1]" (the numbers on this legend are not relevant, and may differ).
If 0:[COM1] appears below ID:COM, we are good! If not, you have to try installing the Samsung USB drivers, or changing the USB port on your computer (use rear ports please!).
The last part of this segment is to choose the 4 files we have copied to our Odin folder. You have to select them on the Odin screen on the right "Files (Download)".
Hit the BL button and select the BL file. Do the same for the other 3 files. BE PATIENT!. After selecting every file, do not touch anything else until Odin shows the route of the file to the right of the button you pressed. The AP button may take up to 20 seconds to display the route after choosing the AP file.
The 4 files are set, so you just hit START and wait for 6 minutes. By the end, you'll have stock KitKat, and your tablet will show you the Samsung first use wizard. PLEASE don't touch anything during those 6 minutes!!!. A green "PASS!" will show in ODIN when its finished.
Flashing the OTAs for Lollipop 5.0.2
The tablet will boot and show Samsung first use wizard. Disconnect your USB cable and power OFF the tablet. Now we have to access Recovery Mode. Hold the HOME and VOL UP buttons and press the POWER button. When the GALAXY TAB logo appears, release only the POWER button while maintaining the VOL UP and HOME buttons pressed.
You're faced with Recovery Mode. Using VOL DOWN, move the cursor and highlight "apply update from external storage" and press the POWER button. Now move the cursor again to highlight "Update.zip" and press the POWER button. This will flash the first update file. When finished, the tablet will reboot itself. That will take you again to the Samsung first use wizard, so once more power OFF the tablet.
We need to enter "Recovery Mode" again (HOME + VOL UP + POWER). And again we have to apply an "update from external storage" but this we do apply file Update2.zip. Now Lollipop is being flashed. Ignore any error that might appear in red letters on your tablet.
After yet another automatic reboot, the tablet will boot the Samsung Wizard but now in Lollipop. Before putting your fingers on the display, PLEASE don't conect to your WiFi or use Internet over your Data Plan. Remove your simcard and don't use your Wifi until I tell you.
Now that you know that, head to our second guide to continue (here).
Special Thanks:
* @frizzdizzle27 for providing both KitKat and Lollipop firmware/files. He was/is key for us SM-T707A users.
Part 4 and 5
I followed your tutorial and it worked perfectly for my Galaxy Tab S. I was hoping to see an update on the Xposed modules and debloating...do you have any updates you can share? thanks in advance.
Anyone able to find the marshmallow ota?
I goofed and updated my Verizon Galaxy S6 Edge (32gb) to Nougat. I'd like to attempt downgrading it back to 6.01 (Marshmellow?) I'm new to modifying my cell phone and would like to outline what I think I should do, and hopefully someone with experience will catch any goofs before they occur.
General Information:
G925V
Build # G925VVRS4DQD1
Hardware # G925V.04
1. Downloaded Samsung Switch, backup everything I can. This step should also place the samsung usb drivers on my pc? (window 10 64bit)
2. Prepare phone? Little foggy on this step, some guides recommended factory restore and erase cache partion first. Remove Sim card.
3. Download firmware from sammobile, I downloaded G925VVRS4CQA3, newest available 6.01. Does it matter that the last four digits don't match the last four of my Build #?
4. Put phone in download mode (reboot, home+power+volume down, volume up to accept)
5. Open Odin (v3.12.5) verify .tar file. I saw the AP file that needs pulled over, guessing there might be other files, firmware download still going.
6. Connect phone, check connection in upper left window of Odin hit start and don't unplug anything
7. When Odin finishes, reboot phone into Recovery mode, select factory reset all user data?
Am I overlooking anything major?
Thanks,
Cole
coleauden said:
I goofed and updated my Verizon Galaxy S6 Edge (32gb) to Nougat. I'd like to attempt downgrading it back to 6.01 (Marshmellow?) I'm new to modifying my cell phone and would like to outline what I think I should do, and hopefully someone with experience will catch any goofs before they occur.
General Information:
G925V
Build # G925VVRS4DQD1
Hardware # G925V.04
1. Downloaded Samsung Switch, backup everything I can. This step should also place the samsung usb drivers on my pc? (window 10 64bit)
2. Prepare phone? Little foggy on this step, some guides recommended factory restore and erase cache partion first. Remove Sim card.
3. Download firmware from sammobile, I downloaded G925VVRS4CQA3, newest available 6.01. Does it matter that the last four digits don't match the last four of my Build #?
4. Put phone in download mode (reboot, home+power+volume down, volume up to accept)
5. Open Odin (v3.12.5) verify .tar file. I saw the AP file that needs pulled over, guessing there might be other files, firmware download still going.
6. Connect phone, check connection in upper left window of Odin hit start and don't unplug anything
7. When Odin finishes, reboot phone into Recovery mode, select factory reset all user data?
Am I overlooking anything major?
Thanks,
Cole
Click to expand...
Click to collapse
1.) From http://www.samsung.com/us/support/smart-switch-support/#!/faqs "The first time you connect your Samsung device to your computer, it will automatically locate and install the necessary drivers. (This process can take a few minutes to complete.) After the drivers are installed, the device will appear in the Smart Switch application.
If the drivers do not install automatically, go to the Samsung Support site and visit your device's support page. Click Manuals & Downloads to download the drivers for your device."
2.) Yeah, I am guessing prepare phone means prepare for total data loss (lol) when you perform a wipe data/factory reset from the recovery mode/menu (which formats /data, /cache and /sbfs partitions).
3.) The last 4 digits are different because you are on the first build of Nougat now (DQD1).
I have no experience with Odin myself, but I do know there are checkboxes, options and such you should do research on beforehand. For example, on sammobile's download page there are instructions saying "Make sure re-partition is NOT ticked" so just saying as there may be special procedures involved specifically when downgrading.
Another potential problem: have you found confirmation that you can downgrade -directly to- the last Marshmallow 6.0.1 build available for this phone (CQA3) -from- Nougat 7.0 (DQD1) and are you sure about it? There is a chance you may need to downgrade to an earlier build first.
Also I've had a strange experience with sammobile, as I downloaded the Nougat firmware for this phone and it is -completely- different (name, size, hash, modified date far before the public release) from other Nougat firmware I downloaded.
I recommend for any firmware build you decide to use: download from multiple sources and compare/verify with HashMyFiles or similar software to make sure it is really what they say it is.
I am awaiting response from a question for this OP; you should check it out as he mentions downgrading and provides download links (note: CQA3 is -not- in the list). https://forum.xda-developers.com/ve...25vvrs4dqd1-odin-nougat-7-0-firmware-t3597591
Thank you for the information @blkt
coleauden said:
Thank you for the information @blkt
Click to expand...
Click to collapse
You can thank me with the "Thanks!" button on my post.
Dying to know if this worked??
SpyderPalo said:
Dying to know if this worked??
Click to expand...
Click to collapse
It worked. I did end up with a bootloop bouncing between the Verizon Screen and the Samsung screen that caused a few grey hairs. Eventually I was able to get into Recovery mode and performing data and cache resets allowed me to power on fully. I had performed a cache reset before starting the downgrade process, but not a data/factory reset. I also had the sim card removed. Either of those might have contributed to the bootloop. First action after google and Samsung account login was running BK Package Disabler and blocking the two sdm packages to hopefully prevent Nougat notifications (process contributed by @wolferno ).
Some information if it helps:
*Odin version was 3.12.5.
*Firmware version was G925VVRS4CQA3_G925VVZW4CQA3_VZW from sammobile (highest 6.01)
Backup was through Smart Switch, to get it running again I had to activate Developer options, enable USB Debugging, and under USB options enable MTP.
Hope this helps!
I have successfully downgraded from Nougat on my G925V 64gb
I used the stock software G925VVRS4CQA3_VZW4CQA3_VZW_USA_Verizon_6.0.1.
I downloaded from AndroidFileHost did the md5 check
It did boot-loop between Verizon and Samsung
Pressing and holding the Volume-down then Power button brought up the Factory reset (DOS-like) screen where I could do another factory reset to get the phone to boot up into setting up the phone starting with logging into the Samsung account.
I had activated another phone before this process so I could still get and make calls if it bricked, I've signed into my Gmail account that I have all apps and setting's saved.
I will be installing a Package Disabler as soon as the apps finish loading and before I activate the phone back onto Verizon.
Much thanks to coleauden for answering a PM and blkt for clarifying with coleauden earlier!!!
Enjoy the Day,
David
SpyderPalo said:
I have successfully downgraded from Nougat on my G925V 64gb
I used the stock software G925VVRS4CQA3_VZW4CQA3_VZW_USA_Verizon_6.0.1.
I downloaded from AndroidFileHost did the md5 check
It did boot-loop between Verizon and Samsung
Pressing and holding the Volume-down then Power button brought up the Factory reset (DOS-like) screen where I could do another factory reset to get the phone to boot up into setting up the phone starting with logging into the Samsung account.
I had activated another phone before this process so I could still get and make calls if it bricked, I've signed into my Gmail account that I have all apps and setting's saved.
I will be installing a Package Disabler as soon as the apps finish loading and before I activate the phone back onto Verizon.
Much thanks to coleauden for answering a PM and blkt for clarifying with coleauden earlier!!!
Enjoy the Day,
David
Click to expand...
Click to collapse
Nice, I didn't realize CQA3 was on AndroidFileHost as well. Which Odin version did you use? Did you remove your sim card? BTW, I think you meant Home/Volume Up/Power for recovery mode (the DOS-like menu) because volume down would put you into download mode. In recent months there have been reports (on google play reviews) of Package Disabler Pro removing the ability to disable certain packages at the request of Samsung (removed from package list, no changelog either). Maybe this has changed; I have not investigated further but there's also BK Package Disabler. Here is a helpful page with all Odin versions. http://www.droidviews.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/
blkt said:
Nice, I didn't realize CQA3 was on AndroidFileHost as well. Which Odin version did you use? Did you remove your sim card? BTW, I think you meant Home/Volume Up/Power for recovery mode (the DOS-like menu) because volume down would put you into download mode. In recent months there have been reports (on google play reviews) of Package Disabler Pro removing the ability to disable certain packages at the request of Samsung (removed from package list, no changelog either). Maybe this has changed; I have not investigated further but there's also BK Package Disabler. Here is a helpful page with all Odin versions. http://www.droidviews.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/
Click to expand...
Click to collapse
Maintenance Boot Mode is what I get into with holding Down volume and holding Power button.
Odin 3.12.5
De-activated SIM still in the phone (activated a iphone for calls)
I ended up buying BK Package Disabler to block the OS upgrade/update.
SpyderPalo said:
Maintenance Boot Mode is what I get into with holding Down volume and holding Power button.
Odin 3.12.5
De-activated SIM still in the phone (activated a iphone for calls)
I ended up buying BK Package Disabler to block the OS upgrade/update.
Click to expand...
Click to collapse
Oh wow, another mode I was not aware of. Thanks! This one is good to know because it is apparently accessed when the phone is still on. Confusing though, because I though volume down + power was to force reboot. The recovery mode I mentioned is done after the phone is off.
blkt said:
Oh wow, another mode I was not aware of. Thanks! This one is good to know because it is apparently accessed when the phone is still on. Confusing though, because I though volume down + power was to force reboot. The recovery mode I mentioned is done after the phone is off.
Click to expand...
Click to collapse
Sorry I didn't clarify......
I pressed the 2 buttons once the phone was off...
In all the times I have ever had to get into the lower (Root) areas of the phone , I've started with the phone off so I assumed this was a known practice.
Apologies
SpyderPalo said:
Sorry I didn't clarify......
I pressed the 2 buttons once the phone was off...
In all the times I have ever had to get into the lower (Root) areas of the phone , I've started with the phone off so I assumed this was a known practice.
Apologies
Click to expand...
Click to collapse
Oh, I thought you used it to get out of the boot loop. No worries, as this video put my brain through a boot loop. https://www.youtube.com/watch?v=9N5Q8RD5QPs
You should be able to downgrade to any firmware that is Revision/Binary 4.
You started with 4DQD1 right?
You should be able to downgrade to any firmware with like 4A, 4B, 4C, 4D, etc.
Code:
WARNING: Anything done wrong could result in a brick! Make sure you use the proper firmware, and really only do this if have skill with Odin, or absolutely have to due to a brick.
Code:
Following this guide will restore your phone to 'Samsung OFFICIAL' and reset your model to default. This will not reset your Knox counter.
Code:
Please note: I have no experience with Jodin3, and would advise you read or watch a couple guides before using it. I don't know whether or not it is stable, so I cannot take the blame if Jodin3 ruins your phone, It's just the only alternative for Mac OS X. (WineHQ does not have USB support on Mac OS.)
Edit:
Let me just clear something up. When I say PC I MEAN ANY COMPUTER!
What makes me more annoyed than anything is when people call Windows computers exclusively, and don't consider an iMac or Linux machine a PC. PC literally means Personal Computer!
https://www.collinsdictionary.com/us/dictionary/english/pc
Hello everybody! A couple days ago I was uninstalling Magisk and installing SuperSU instead, due to the fact that I couldn't change file permissions in root explorer. (I'm back on Magisk, because I found out ES would change the permissions with Magisk.) When I did it, the encryption breaker wouldn't work, due to already flashing it. (When fullofhell made his Pixel 2 rom.) I had reset my SD card, but forgot, so I didn't have a backup when it ended up boot looping. (Stuck on android logo forever.) I ended up having to use Odin and go to stock, however it wasn't as easy (or atleast not something that I knew how to do) to figure out how exactly to do it.
1.) The first thing you need to do is download the stock ROM from here or from Updato. (It doesn't matter what version you use, as long as it's for T or T1, meaning you could install Marshmallow if you wanted to.)
2.) Download and install Odin3 for your Windows PC. (I own a iMac, but I honestly don't feel like risking using it with Jodin3 because I don't know it's potential) or use WineHQ on Linux. After doing so open Odin3, Odin3 WineHQ, or Jodin3.
3.) Download and install the Samsung USB Drivers if you haven't already from here.
4.) Put your phone in Odin mode, via holding Volume Down + Home + Power or by entering recovery and then rebooting into Download mode, and pressing volume up when it prompts you.
5.) Plug your phone in via USB, and if everything done correctly you should see 'Added' in the dialouges, and see a box turn blue saying Com3.
6.) Select AP and then select your stock file. After selecting Odin might freeze or even get a dialouge saying "Odin3.exe has stopped working." When this happens don't close it.
7.) In settings disable Auto Reboot.
8.) Select flash and wait.
Do not unplug your USB, shutdown your phone, and do not shutdown your PC.
9.) When done shut down your phone. (Battery pull may be necessary, for people like me.)
10.) Boot into recovery mode, by holding Volume Up + Home + Power. You should not boot into TWRP or any custom recovery, if you do something went wrong.
11.) Use volume keys and power keys to select buttons:
Select Factory Reset phone
Select Reset Cache
12.) Boot up your phone. (You will be on the T-Mobile screen for 10 seconds to 1 minute.)
13.) Do not install any apps or important data after setup if you intend to root, as you will need to install TWRP via Odin, and then wipe /data when install Magisk or SuperSU to avoid a brick.
I hope I helped in any way.
Please note all I did was gather a bunch of links and put together a guide.
I do not take credit for stock ROM, TWRP, Odin, SuperSU, Magisk, or any other programs and files.
I would like to thank @fullofhell for giving this post a better website in replacement for sammobile.
Hey man thanks! I was really worried after I flashed Magisk due to the fact that I didn't know that I needed to make a backup. This thread works for the SM-J700F, you just need to get a different firmware file! :good:
Don't use sammobile. It's awful. Use updato.aka updates for android. See screenshot. 100x better.
fullofhell said:
Don't use sammobile. It's awful. Use updato.aka updates for android. See screenshot. 100x better.
Click to expand...
Click to collapse
Does it have a website, or do I have to download it from the app?
It doesn't really seem suitable for a brick, but I think it would be amazing for returning to stock without a brick.
TechNash said:
Does it have a website, or do I have to download it from the app?
It doesn't really seem suitable for a brick, but I think it would be amazing for returning to stock without a brick.
Click to expand...
Click to collapse
The app allows for direct download.its perfectly suitable for any type of brick. There hasn't been a brick I haven't been able to unbrick. As long as u can power on the device and boot to the bootloader or download mode, you are fine. Use the app to get the firmware, extract, and flash with odin or what have u
fullofhell said:
The app allows for direct download.its perfectly suitable for any type of brick. There hasn't been a brick I haven't been able to unbrick. As long as u can power on the device and boot to the bootloader or download mode, you are fine. Use the app to get the firmware, extract, and flash with odin or what have u
Click to expand...
Click to collapse
Okay I see. But lets say you are an utter idiot and have no idea what you are doing to your phone. (NOT CALLING ANYONE WHOM BRICKED THEIR PHONE AN IDIOT! EVERYONE WILL!) You managed to brick it, how do you access the app? How would you download the firmware from the app if your phone is bricked? (without pre-downloading the firmware)
TechNash said:
Okay I see. But lets say you are an utter idiot and have no idea what you are doing to your phone. (NOT CALLING ANYONE WHOM BRICKED THEIR PHONE AN IDIOT! EVERYONE WILL!) You managed to brick it, how do you access the app? How would you download the firmware from the app if your phone is bricked? (without pre-downloading the firmware)
Click to expand...
Click to collapse
Use another device. And if u are modding your device,.before doing so, one should already have stock firmware handy, along with any twrp(recovery IMG.), Encryption break zips,.and a hardcopy nandroid copied to a computer.these are things one should have learned and have ready just in case. To not do such things sells yourself short. Always be prepared. Do that and read and learn as much about the current task at hand BEFORE doing it
fullofhell said:
Use another device. And if u are modding your device,.before doing so, one should already have stock firmware handy, along with any twrp(recovery IMG.), Encryption break zips,.and a hardcopy nandroid copied to a computer.these are things one should have learned and have ready just in case. To not do such things sells yourself short. Always be prepared. Do that and read and learn as much about the current task at hand BEFORE doing it
Click to expand...
Click to collapse
Okay well I'll put that in the guide as a precaution or ANOTHER method of getting firmware, as not everyone has multiple Android devices.
Thanks for the suggestion and explaining @fullofhell
TechNash said:
Okay well I'll put that in the guide as a precaution or ANOTHER method of getting firmware, as not everyone has multiple Android devices.
Thanks for the suggestion and explaining @fullofhell
Click to expand...
Click to collapse
here is the website, which also offers much more stable firmware downloads as they are the same mirrors the mobile app uses. If you try to use sam mobile, you may download the firmware after a day or so, it used to take forever even on my 300mbps connection.
https://updato.com/
Thank you very much!
I said sammovile because I didn't know of anything else, and I figured if you are following this guide you could probably be desperate enough to sleep on the download.
I'll put that in the post.