Stock Boot Img in TAR format Offerd for S7 SM-G930V - Verizon Samsung Galaxy S7 Guides, News, & Discussi

I tried the rooting method and ended up getting stuck on the Verizon Loading screen so I went and reset everything with the stock files in odin (G930VVRU2APE1_G930VVZW2APE1_VZW) and tried again, this time after resetting everything up and customizing my phone back the way I had it only again to be greeted by the blasted verizon white loading screen, so to save myself some time i took a look at the AP Tar in the stock files pulled out the boot.img and tared it in linux, then using the same odin tool to flash the engineering kernel, i flashed just the stock boot.img tar, and lo and behold no redoing everything for a second time, my phone came back up setting intact
So I am offering to link the stock boot.img that has been tared and ready to go at least for the Verizon Variant of the S7 PE1
next is a question, is their any way yet to manually build the modified engineering boot image so it will stop getting stuck on verizon, without having to reflash back the entire stock set, as boot does not affect the system partition directly anyway
let me know if the file will be helpful and ill edit and upload it
here is the link to the boot image
https://dl.dropboxusercontent.com/u/31367944/Galaxy%20S7%20Verizon%20PE1%20Stock%20Boot.tar

Wildcat2083 said:
I tried the rooting method and ended up getting stuck on the Verizon Loading screen so I went and reset everything with the stock files in odin (G930VVRU2APE1_G930VVZW2APE1_VZW) and tried again, this time after resetting everything up and customizing my phone back the way I had it only again to be greeted by the blasted verizon white loading screen, so to save myself some time i took a look at the AP Tar in the stock files pulled out the boot.img and tared it in linux, then using the same odin tool to flash the engineering kernel, i flashed just the stock boot.img tar, and lo and behold no redoing everything for a second time, my phone came back up setting intact
So I am offering to link the stock boot.img that has been tared and ready to go at least for the Verizon Variant of the S7 PE1
next is a question, is their any way yet to manually build the modified engineering boot image so it will stop getting stuck on verizon, without having to reflash back the entire stock set, as boot does not affect the system partition directly anyway
let me know if the file will be helpful and ill edit and upload it
here is the link to the boot image
https://dl.dropboxusercontent.com/u/31367944/Galaxy S7 Verizon PE1 Stock Boot.tar
Click to expand...
Click to collapse
Wrong thread. This is AT&T thread.
Sent from my SAMSUNG-SM-G930A using XDA-Developers mobile app

dirtydodge said:
Wrong thread. This is AT&T thread.
Sent from my SAMSUNG-SM-G930A using XDA-Developers mobile app
Click to expand...
Click to collapse
I noticed it right after I posted, i had multiple tabs up and pasted to the wrong one sorry

Related

Someone help me? Possibly bricked.

I have been trying to find an answer for the last several hours. But I can't seem to get anything to work.
I have the AT&T GS3 and I was able to flash AOKP but then I wanted to revert back to stock. I tried the toolkit and followed the steps and what might of happened is that AOKP did not get wiped completely when I flashed the stock image. Now after successfully flashing the stock image (I get the PASS! on Odin), my phone is stuck while booting. It goes past the AT&T boot image but gets stuck on "SAMSUNG". I tries flashing through ODIN, another downloaded version of the stock image but it didn't work. What am I doing wrong?
Another problem with being stuck in bootloop is that since I flashed the stock image; I think I no longer have CWM. I can't find a way to get to recovery.
I'm not really sure how to help but if you can get to the boot animations you aren't bricked. I know you're not on verizon but in this thread: http://forum.xda-developers.com/showthread.php?t=1759642 it says when coming from an AOSP rom back to the stock rom you have to flash a stock boot.img before flashing the stock rom. Hope you can get it working again
Did you make a nandroid backup before you flashed the Rom...if you did you can restore from cwm recovery...hold power, volume up, and home...after the screen goes black let go of the power...hope this helps
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
If you can get into download mode , just flash recovery from odin.
And how long have you waited at samsung logo , it might take few minutes to bootup.
I don't have CWM recovery. It got stuck on the Samsung logo for 20 minutes before I gave up and did a battery pull.
What do I flash through odin to get it working again. Which recovery file?
Ok, I just used the method described in this article and I am still stuck at the SAMSUNG logo.
http://www.androidegis.com/how-to/unbrcik-your-us-samsung-galaxy-s3-how-to/
http://forum.xda-developers.com/showthread.php?t=1727443
Tried that. Still same problem. Noticed that the boot-stock-att-sgh-i7.tar is only 10.5 mb. I don't know much about this, but is that tar file enough to get me unbricked?
usually the .tar file should be much larger than that. It's possible that the file you downloaded got corrupted. Try re downloading the file and than flashing it again.
Sent from my SCH-I535 using xda premium
If you look in the mediafire link inside ths artivle, you will notice that the download is only 10 mb
http://forum.xda-developers.com/showthread.php?t=1727443
try this
VJKotts said:
I have been trying to find an answer for the last several hours. But I can't seem to get anything to work.
I have the AT&T GS3 and I was able to flash AOKP but then I wanted to revert back to stock. I tried the toolkit and followed the steps and what might of happened is that AOKP did not get wiped completely when I flashed the stock image. Now after successfully flashing the stock image (I get the PASS! on Odin), my phone is stuck while booting. It goes past the AT&T boot image but gets stuck on "SAMSUNG". I tries flashing through ODIN, another downloaded version of the stock image but it didn't work. What am I doing wrong?
Click to expand...
Click to collapse
Get into download mode
clear cache option
factory reset phone option
That should fix it
CC
How do you factory reset/clear cache in download mode?
VJKotts said:
How do you factory reset/clear cache in download mode?
Click to expand...
Click to collapse
just re flash stock in odin flash Flash this file http://forum.xda-developers.com/showthread.php?t=1737848

[Q] Odin stock ROM file DIY (JB4.2.1) for Mobile ODIN?

Hi Folks,
sorry I'm having trouble finding instructions on how to do this, for maguro I was only able to find Odin 4.0.4 restore, which doesn't seem to be working for me, tried to flash 4.0.4 ODIN ROM img on rooted 4.2.1 GNEX - after flash 4.2.1 boots up, still rooted, also recovery doesn't work, surprise of the century
My question is following:
1. Can I simply go here: --->developers.google.com/android/nexus/images<---- and download what I need,
2. Then unpack the TGZ, put all the files in single TAR while renaming them to look like 4.0.4 ODIN files do,
3. upload the TAR to /mnt/sdcard
and flash it with Mobile ODIN?
background is I noticed this morning micro USB port in my GNEX/i9250 died completely, so looking on how to do this via Mobile ODIN... then I can bring the phone back to repair shop.
Rgds,
Y.
some success....
hmm, impatient but force is strong in me, so I just went for it. looks like the anwer is YES and NO
YES because it takes the prepped file and says it's going to flash it, reboots, saying flashing blahblah (quickscroll, tough to read) etc
NO because it doesn't do anything except bringing your boot ROM to factory defaults...
sort of YES because I tried flashing only one img at a time, for obvious reasons needed recovery restored, so clicked on recovery (partition) option in Mobile Odin and it allowed me to select the full TAR file, flashed it and I got my recovery back!
so all good, but the remaining question is:
which way/which order to flash the factory image (all img files in the TGZ) with Mobile Odin to have a "unrooted-stock-like" install and not to loose mobile Odin too early (during wipe/reinstall of img files)?
Thx for any responses!
Rgds,Y.
You don't need ODIN, just flash the factory image using fastboot
EddyOS said:
You don't need ODIN, just flash the factory image using fastboot
Click to expand...
Click to collapse
ahuh, great...how do I do that without USB?
btw. I think I figured out the problem why mobile odin didn't work. I will post the step-by-step/summary later
YogiCrusher said:
ahuh, great...how do I do that without USB?
btw. I think I figured out the problem why mobile odin didn't work. I will post the step-by-step/summary later
Click to expand...
Click to collapse
I'm having the same problem. How did you figure it out?
Tried pm'ing the developer?
sorry I only thought I did, but noooo.... anyway I used fastboot in the end
...but still learned a few interesting things...
yeah I guess PMing dev is the best...need to get my money back....or try to resuscitate your usb port like I did - similar to this yt video, needle method: -->www-you-tube-com/watch?v=R6p0Eg-yq3A<--- , it died again 2 mins after 'fastboot oem lock'
mobile odin...do note: I was able to flash single partition, done this for recovery partition, still it's quite risky or even impossible this way?
verified as much that state of the bootloader lock has no affect on odin, i.e it doesn't work whatever the setting and how you set it, I used bootunlocker, here on the forums there is a "dd method" which does exactly the same (flipping 1 bit in 1 place).
btw. flash/mix of different rom / boot / loader / recovery versions... in case sbd would get the idea to mix boot 4.0 with rom 4.2, might not always be a good idea I guess
one last thing: seems essentially the update files for mobile odin can be created exactly in the way described in the first post.

[Q] Soft Bricked my i747- HELP!

So I was able to root phone on w/o issue. I installed CWM via play store then proceeded to attempted to load Cyanogen mod via zip..and oh yeah I didn't wipe phone prior so....Now I have infinite loop issue at boot. I've searched the interwebs looking for any way to get back to stock or anything so I'll be able to use the phone again but have come up short every time. I've tried using ODIN to flash stock image but that fails. I've tried various .tar, .tz and anything else that odin will load w/o success. Will anyone take pity on my stupid ass and lens a hand?
exarkun631 said:
So I was able to root phone on w/o issue. I installed CWM via play store then proceeded to attempted to load Cyanogen mod via zip..and oh yeah I didn't wipe phone prior so....Now I have infinite loop issue at boot. I've searched the interwebs looking for any way to get back to stock or anything so I'll be able to use the phone again but have come up short every time. I've tried using ODIN to flash stock image but that fails. I've tried various .tar, .tz and anything else that odin will load w/o success. Will anyone take pity on my stupid ass and lens a hand?
Click to expand...
Click to collapse
Are you able to boot in recovery? (volume up + home + power). You could wipe and try flashing again (the first boot does take a while).
As for Odin, make sure you're using the right image (.tar) if recovery doesn't work.
Here's a little Odin guide: [ODIN] Desktop ODIN ver 3.07 for use with Samsung Galaxy S III
yeah I tried that
BWolf56 said:
Are you able to boot in recovery? (volume up + home + power). You could wipe and try flashing again (the first boot does take a while).
As for Odin, make sure you're using the right image (.tar) if recovery doesn't work.
Here's a little Odin guide: [ODIN] Desktop ODIN ver 3.07 for use with Samsung Galaxy S III
Click to expand...
Click to collapse
So I am able to boot into recovery but it's the stock recovery, not the one I intalled after root.
I've tried flashing stock images, custom images, CWM, TWRP, .TARs all w/o success. In ODIN I've flashed CWM and TWRP and it reports success but upon reboot it goes back to stock recovery and shows now 13 attempts to load custom firmware. I even tried to use Cyanogen,s windows app but even that gets stuck saying it can't communicate w/device. I've tried several driver, hiemdal, (which I can't figure out). What I'd like to do wipe EVERYTHING, like format the phone but I can't seem to remove the Samsung boot loader. Is my phone beyond repair? I'm super bummed, esp since I'm not a total noob when it comes to custom ROMs. I dropped greenpoison on my fist iPhone and had several ROMs on my old Moto Atrix. I think whatever evil Samsiung put on this device is totally screwing me.
exarkun631 said:
So I've tried flashing stock images, custom images, CWM, TWRP, .TARs all w/o success. In ODIN I've flashed CWM and TWRP and it reports success but upon reboot it goes back to stock recovery and shows now 13 attempts to load custom firmware. I even tried to use Cyanogen,s windows app but even that gets stuck saying it can't communicate w/device. I've tried several driver, hiemdal, (which I can't figure out). What I'd like to do wipe EVERYTHING, like format the phone but I can't seem to remove the Samsung boot loader. Is my phone beyond repair? I'm super bummed, esp since I'm not a total noob when it comes to custom ROMs. I dropped greenpoison on my fist iPhone and had several ROMs on my old Moto Atrix. I think whatever evil Samsiung put on this device is totally screwing me.
Click to expand...
Click to collapse
Try with a different stock image (debloated if you want a smaller download).
Also, Heimdall installs its own drivers, therefor Odin won't work on the same usb port you've installed Heimdall on.
Even in stock recovery, you should be able to do a factory reset (I think). Chances are that your ROM is corrupted atm though, you can try doing a factory reset and attempt boot. If that doesn't work, go the Odin way.
Bootloaders are not something to play with, it's the only way to hard-brick your phone (and you definitively don't wanna remove those nor stop Odin while it's flashing them, if the .tar contains them).
what about...
BWolf56 said:
Try with a different stock image (debloated if you want a smaller download).
Also, Heimdall installs its own drivers, therefor Odin won't work on the same usb port you've installed Heimdall on.
Even in stock recovery, you should be able to do a factory reset (I think). Chances are that your ROM is corrupted atm though, you can try doing a factory reset and attempt boot. If that doesn't work, go the Odin way.
Bootloaders are not something to play with, it's the only way to hard-brick your phone (and you definitively don't wanna remove those nor stop Odin while it's flashing them, if the .tar contains them).
Click to expand...
Click to collapse
I updated the phone via ota to latest android (4.3 ?). And I think the stock image I tried using was 4.1.x. Could it be I need to find a stock 4.3.x image from at&t? Any idea where to get this? I don't think AT&T provides ythis as that is where I got the previous stock image.
exarkun631 said:
I updated the phone via ota to latest android (4.3 ?). And I think the stock image I tried using was 4.1.x. Could it be I need to find a stock 4.3.x image from at&t? Any idea where to get this? I don't think AT&T provides ythis as that is where I got the previous stock image.
Click to expand...
Click to collapse
Can you check if the image you used had bootloaders? Cause if so, you might have bricked your phone. You can't downgrade bootloaders from 4.3.
The image can be found here or on sammobile.com
Strange
So after flashing my i747 30x via ODIN w/various .tar for boot and recoveries I was briefly able to boot into CWM. Stupidly, I selected the format option and foolishly restarted, intending to boot back into CWM and flash a .zip image. Once I restarted I was locked out of CWM again and can only boot into stock recovery once again. What am I doing wrong? I just can't wrap my head around why every time I flash a custom recovery like CWM or TWRP or Philz's_Touch in OdIn and it reports success, when I restart it just loads Samsung's ****ty stock recovery. I still can't flash a ROM via ODIN but I'm hoping if I can get back into CWM I'll be able to load a new ROM and use my phone again. Anyhelp would be great.
BWolf56 said:
Can you check if the image you used had bootloaders? Cause if so, you might have bricked your phone. You can't downgrade bootloaders from 4.3.
The image can be found here or on sammobile.com
Click to expand...
Click to collapse
lol
exarkun631 said:
So after flashing my i747 30x via ODIN w/various .tar for boot and recoveries I was briefly able to boot into CWM. Stupidly, I selected the format option and foolishly restarted, intending to boot back into CWM and flash a .zip image. Once I restarted I was locked out of CWM again and can only boot into stock recovery once again. What am I doing wrong? I just can't wrap my head around why every time I flash a custom recovery like CWM or TWRP or Philz's_Touch in OdIn and it reports success, when I restart it just loads Samsung's ****ty stock recovery. I still can't flash a ROM via ODIN but I'm hoping if I can get back into CWM I'll be able to load a new ROM and use my phone again. Anyhelp would be great.
Click to expand...
Click to collapse
So I think I figured out what I did wrong. Recovery mode = pwr+home+VolUp...Download mode = Pwr+home+VolDown. What an a$$hole I am, I thought Download mode and Recovery were one in the same and flashing TWRP or CWM would replace download mode. Once I figured out that one it was a simple matter to boot into recovery and wipe the drive then flash my rom (Omni 4.4.2 D2att) IDK if it's the rom or all the screwing around I did but it now takes no less than 10 min to boot into android from rom splash. Tried updating Kernel to latest but found it didn't fix problem.
exarkun631 said:
So I think I figured out what I did wrong. Recovery mode = pwr+home+VolUp...Download mode = Pwr+home+VolDown. What an a$$hole I am, I thought Download mode and Recovery were one in the same and flashing TWRP or CWM would replace download mode. Once I figured out that one it was a simple matter to boot into recovery and wipe the drive then flash my rom (Omni 4.4.2 D2att) IDK if it's the rom or all the screwing around I did but it now takes no less than 10 min to boot into android from rom splash. Tried updating Kernel to latest but found it didn't fix problem.
Click to expand...
Click to collapse
Did you do a clean flash? Sounds like you didn't factory reset.
Make sure you backup your apps before doing so if you wanna keep your app data.

Complete noob thinks he may have softbricked his phone

Hi guys. Brand new to this whole rooting thing. Long story short, I rooted my device (Galaxy S3 sgh-t999) a while back and was just living off stock touchwiz just with all the bloatware deleted. I had the most recent version of TWRP installed and my recovery was based on that. I then downgraded TWRP to 2.3.3.0. It asked me to reboot and I did so. Now I'm stuck at the Samsung logo screen but it doesn't get past that. The device seems to boots up, but the moment the little Samsung jingle starts to play (you know the swirly blue mist that encompasses the Samsung logo), it stops in the middle of the jingle and the phone won't get passed it.
I tried rebooting back into TWRP via up, home, power and was able to get into TWRP recovery good enough, I can access everything in the menu and tried wiping dalvik, cache, factory reset and system and restored from my backup, but upon trying to restore from my custom backup, it just stalls on the Samsung logo screen. Any ideas if this is fixable? Sorry if this is in the wrong forum guys.
Also, I should make mention that whenever I try to hard power off my phone by holding down the power button, it turns off for a moment then boots back on again. I actually have to remove the battery in order for the phone to turn off. Don't know if that helps.
That's normal when you hold the power button down. It's a hard reset so it's supposed to boot back up.
As for your other issues, why did you downgrade twrp? If your backup was made with another version I suggest using the same to restore it.
Most of the time a factory reset will fix this type of problem, but it sounds like we are beyond that now. If the restore and another reset don't work, go to my firmware thread (sticky in development) and download the same or newer firmware as what you had before. Flash via Odin and factory reset from the stock recovery. ( This will wipe the internal sd)
That should get you going again.
For the future, please do not ever manually wipe /system. You could end up with no O/S to boot into and a hell of a headache! There is simply no benefit to doing so. Only risk.
Let me know if you have any other questions.
Good luck!
Sent from my SGH-T999 using Tapatalk
I downgraded TWRP because I was having issues flashing a new ROM. Every ROM I tried flashing came up with an error and people said they were most successful with 2.3.3.0 so I tried it out. I suspected it might have screwed something up but stupid me always has to be sure. I would try and re-use an upgraded TWRP version if possible but I don't think I can access that from the TWRP menu itself and that's just about the only function my phone has at this point. Just booting into TWRP and playing around with the menu.
Do you have a link to your thread? Thanks for the time by the way.
The link should be in my sig. But it's stickied at the top of the development section. Can't miss it.
If you go to twrp's Web page you can download a newer one in .zip format and flash from your current version.
Or get the .tar.md5 one and flash from Odin.
In the newer versions you can actually flash the .img file itself. After choosing install and are browsing for the file, look for a button to use the .img.
I don't believe this is available in the older ones though.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
The link should be in my sig. But it's stickied at the top of the development section. Can't miss it.
If you go to twrp's Web page you can download a newer one in .zip format and flash from your current version.
Or get the .tar.md5 one and flash from Odin.
In the newer versions you can actually flash the .img file itself. After choosing install and are browsing for the file, look for a button to use the .img.
I don't believe this is available in the older ones though.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
You are a LIFESAVER! I was sure I messed something up permanently that would cause me to have to get a new phone. THANK YOU THANK YOU THANK YOU!
You're welcome! Glad I could help! So I take it you've got it up and running again?
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
You're welcome! Glad I could help! So I take it you've got it up and running again?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yup! It was really a simple matter of updating TWRP via Odin. I don't know why it never crossed my mind to use it. Maybe I'll have more luck using different ROMs through Odin instead of TWRP as well.
Odin is really only just for flashing full firmware for updates and returning to stock, and for flashing recovery. Pretty much everything else (all custom roms, for example) is meant to be flashed in a custom recovery like twrp. If you're ever unsure, reread the op of whatever you're flashing, and if your answer isn't there feel free to ask about it.
In a nutshell: Odin only flashes .tar and .tar.md5 files. Recovery flashes .zip.
I do highly recommend an app called Mobile Odin by chainfire. Search xda for his thread and make sure you read all the info if you're interested. It can make flashing super easy!
Sent from my SGH-T999 using Tapatalk
I am having a similar issue. I have never modified any of the original specs and this is a new issue as of 48 hours ago. In short, my device was on, auto shutdown and then froze on the Galaxy S3 load screen. Attempts to boot in recovery,safe, and soft/hard reset have not worked. I can access Odin mode. After reading the above thread I went to the link you suggested and went directly to the firmware my SGH-T999 started with(T999UVDLJA) and worked my way up the list to see if any of them would take. Unfortunately none achieved a 'PASS' via Odin. So, my question is, what do you do when all the steps have been followed and the firmware doesn't work. Any help would be greatly appreciated.
What error are you getting in Odin?
Do you see anything about warranty bit on the download screen? If you are, the flash is probably failing because you are trying to flash old firmware over new firmware. I suggest flashing the latest firmware for your T999 from here: http://www.sammobile.com/firmwares/database/SGH-T999/

Confused...

I am on 5.1.1- Software N910PVPU4COJ6 if it matters.
Any rom i download i use 7zip to make it a Tar to use in Odin but none of them work when i do that. What am i doing wrong?
I have a file/rom that has Md5 and it goes right on with Odin
I thought a tar file could be used with Odin?
Any sugestions please and thank you.
Sprint note 4
25 views and no suggestions. Dont be scared of my probably dumb questions, haha
why not just flash the rom in twrp?
not sure how to do that, i have always used odin. Cant use twrp on my phone because i am not rooted
Any directions doing it your way? Thanks
II was rooted then put this rom on and now i am not rooted. sucks
and i cant get tar files to work in Odin, just md5
mostly just want my hotspot back
You rooted before, shouldn't be that hard to do it right again: Odin TWRP and flash a stock OJ6 ROM with the mod you seek, following the OP did instructions. Done and done. You may find what you're looking for in post 3 of @tx_dbs_tx OJ6 stock thread.
Odin won't work because you can just convert Recovery flash zip to tar that Odin could use. As you suspect, you'd need a tar.md5 but 7-zip doesn't convert Recovery ROM zip to tar ball. They're completely different; tar.md5 AKA tar ball is more of a partition overwrite partition by order flash, whereas ROM zip has explicit instructions in the updater-script that Odin wouldn't follow. They have their purposes: typically, Odin would be a tool to update to current update and install custom recovery; recovery could be used to flash a ROM or mod compatible with installed update version.
I suspect Odin has done no harm if it's a recent one. It's just refusing to brick your phone.
Sent from my SM-N910P using Tapatalk
you say odin twrp, how do i get twrp onto odin. ? I downloaded twrp and did the zip thing but like before it has a tar and odin will not do it?
The file i rooted before i cant find,so i have to do something new
Odin this in AP mode
https://dl.twrp.me/trltespr/twrp-2.8.7.0-trltespr.img.tar
Sent from my SM-N910P using Tapatalk
i tried but said it failed about half way through,ugg
Does your phone boot to recovery or system? You may need to start over with full OJ6 tar. Find it in general forum and follow the OP instructions.
I'd recommend factory reset as well.
Sent from my SM-N910P using Tapatalk
Yes, i can get into that. My phone is working on the rom i posted. I just want to put another rooted rom on. Will putting that oj6 on let me do that? Will odin put that tar on my phone unlike the other tar files? Thanks
should i put the baseband oj6 on?
I finally got twrp on but when i reboot system from twrp i am just bootlooping. Any ideas what to do now?
volks71folk said:
I finally got twrp on but when i reboot system from twrp i am just bootlooping. Any ideas what to do now?
Click to expand...
Click to collapse
System was booting but you couldn't install TWRP. Now you have TWRP but system doesn't boot.
I suggested you start over with stock OJ6 tar. Did you do that? Sorry, I'm not following what you actually did. I'd say factory reset and flash the stock OJ6 ROM but it sounds like your partitions are messed up. If you agree, do the following:
1)Wipe everything but extSdCard in TWRP.
2)Power down, pull battery minimum 30 seconds.
3)Boot into download mode, using Odin 3.10.7, uncheck the default options, check AP box, click AP tab and select the OJ6 tar.md5 Start only when you have com:xx detected your phone (present).
4)Upon success, close Odin, pull USB and battery, boot intro stock recovery and factory reset.
5)Redo steps 2 and 3 but this time use both the Odin defaults to allow the auto reboot. Close Odin after success.
6)Go through setup wizard and make sure stock is fully functional.
7)Once verified, Odin TWRP with auto reboot unchecked, upon success, pull USB and battery for at least 30 seconds.
8)Boot into recovery and follow OP install instructions to flash custom ROM.
Edit: ROM zip should be on ext sdcard. You may be able to move some files from sdcard to extSdCard with TWRP file manager in advanced tab.
Sent from my SM-N910P using Tapatalk
I finally got twrp to flash on my phone, so now i am in twrp on my phone. Just not sure what to do know. I just hit reboot system in twrp and it wont get passed where it says android note 4. If i cant do anything from here i will re download the oj6 and do what you said.
I am doing what you had said but it takes me to twrp when i go to factory reset. So i did it through twrp and then flashed the oj6 baseband rom and it will not get passed the samsung galaxt note 4 image.
volks71folk said:
I am doing what you had said but it takes me to twrp when i go to factory reset. So i did it through twrp and then flashed the oj6 baseband rom and it will not get passed the samsung galaxt note 4 image.
Click to expand...
Click to collapse
There was a recent similar issue where the OP found a way out using some of the advice I gave.
Basically, Odin flashed the modem and recovery separately to get full Odin tar to flash after factory resetting in stock recovery. Sounds like your Odin flash isn't taking either. Once you have those tar files, flash them twice as suggested with battery pulls greater than 30 seconds where indicated.
I'd follow the guide using OJ6 tar to extract recovery from and the OJ6 modem tar you already have. I added one extra edit l found useful when I attempted to duplicate the OJ6 recovery tar flash myself; look for that too. Alternatively, you could use KIES to try recovery at any point that it recognizes the phone using its emergency recovery feature.
If that doesn't work, try the OG5 tar for files using the OG5 modem I linked in that thread.
You should read the whole thread to get the idea of the recovery theory starting with the summary the OP posted in this link below.
http://forum.xda-developers.com/showthread.php?p=63831716
Best wishes for success.
Sent from my SM-N910P using Tapatalk
you guys say OP?
The problem before was my phone was fine then i flashed twrp and then tried to restart it and all it did was boot loop sometimes to the yellow screen and sometimes to the android note 4. Why would it not get passed those screens after i zipped twrp? Thanks
volks71folk said:
you guys say OP?
The problem before was my phone was fine then i flashed twrp and then tried to restart it and all it did was boot loop sometimes to the yellow screen and sometimes to the android note 4. Why would it not get passed those screens after i zipped twrp? Thanks
Click to expand...
Click to collapse
OP is original poster. It could be 1st post or post quoted in some cases, although it could be the same user.
If your last post is truly the only obstacle, did you wipe following ROM OP instructions before you flashed and did you make sure the ROM flashed?
Often, custom ROMs will require more boot time on initial boot. Boot loop may suggest you didn't wipe the dalvik-cache partition. Usually, clean install is recommended. The updater-script may format system partition and others as well but without verifying specific ROM flashed, users may recommend wiping everything but extSdCard and formatting data partition multiple times each. If wiping system partition, you can expect the flash to fail with a binary failure in red when flashing unless you first rebooted recovery prior to flashing ROM. If you spot that failure, just reboot recovery with the reboot option menu and flash without wiping on second attempt.
If you've done all that and allowed time to boot, you may need to do the steps I've given in the suggestions above.
I hope you can find your way through it.
Sent from my SM-N910P using Tapatalk

Categories

Resources