Related
Okay, so I have everything flashed and Cyanogen's mod is working. However I decided to flash the radio as well. On entering recovery, it is now stuck at the loading screen (with the 4 color X's). Is this normal after flashing radio? I read that you are supposed to be patient and not remove the battery after flashing radio. How long does it usually take? It has been on this screen for about 20 minutes now.
How did u flash the radio? Did u do it from recovery? Normally after initiating flashing radio through recovery, it will extract the package, then reboot and install the new radio, THEN reboot again.
It's hard to say where u might have gone wrong without more info.
I flashed from fastboot using "fastboot flash radio radio.img". It said done on the two lines (Flashing and writing?). Anywho, I decided to go ahead and boot to the recovery to install my gapps. This is when it got stuck on the 4 color logo X. It is still there.
Can you go into the bootloader, or the recovery console? I just want to know if you have bricked your phone or not, if you haven't - then I recommend you just try wiping everything (as usual) and reflashing the ROM. If that doesn't work, at least I tried to be helpful.
Well I haven't removed the battery and tried rebooting yet. Should I?
Okay... I can get into the bootloader. So I just redo everything from step 1? Interesting... After removing the battery and trying again, it seems to boot into recovery mode fine. Just finished installing gapps. Boots fine now. I guess it was just a one time flaw. Phew... The radio doesn't seem to have been flashed. Under settings, baseband version has not changed.
cicrockets said:
Okay... I can get into the bootloader. So I just redo everything from step 1? Interesting... After removing the battery and trying again, it seems to boot into recovery mode fine. Just finished installing gapps. Boots fine now. I guess it was just a one time flaw. Phew... The radio doesn't seem to have been flashed. Under settings, baseband version has not changed.
Click to expand...
Click to collapse
I would recommend downloading the radio in a .zip format made to flash through recovery... that's the most reliable in my experience...
Thanks, I might try that next time. Too much suspense in one day pour moi.
I modified this post to recap the whole story. You can find the timeline development from the second post on.
My TAB is now bricked, it does not give any sign of life even after letting it charging for hours.
Not Odin or heimdall would recognize it to I cannot flash anything.
Samsung Mexico (where I am now) told me they cannot fix it because the mexican version has a different hardware configuration.
I also called Samsung US and they told me they cannot accept it, I should go back to china and repair it there (??).
I decided not to waste my time anymore on this, as it become anti economic.
(if anyone is interested in buying it as spare-parts, please let me know!)
what happened, for reference:
Chinese unicom GST p1000, previously flashed (and running) with success roto-JME.
I tried to flash JQ1 with bootloaders but ODIN failed at hidden.rfs. Since then I never manage to boot the tab anymore.
I then couldnt flash any ROM containing either hidden.rfs or movinand.mst, it would always FAIL. In order to PASS I had to remove these two from the flash, but TAB will hang at Samsung logo during boot (not sure if the reason for not booting is because of the missing files, or these 2 problems have the same cause, but are not related with eachother).
I tried a huge number of different ROMs, all give same results (even JME will fail at movinand.mst now)
in case you are wondering I already tried different computers, win and ubuntu, Odin and heimdall, changed USB cables, always the same problem.
Given the above situation (base ROM not complete and not booting + /data unmountable) I managed anyway to install Overcome and AF974, but they both hung at GALAXY TAB boot screen (the very first one) and keep rebooting every few seconds. (This is different from when it hangs at samsung logo - see above)
After this recovery started to report partition errors:
I cannot mount /DATA in either CWM or ADB , it says:
mounting /dev/block/mmcblk0p2 on /data failed: No such file or directory
indeed /dev/block/mmcblk0p2 does not exist.
I tried the flashing routine again, and new different partition errors came up
now the internal sd-card was not mountable anymore, instead it would read ext-sd as internal
I tried the flashing routine again, and it bricked completely to death
What I DIND'T do (learned about it too late!) prior to flash JQ1 was to neither ROOT or patch bootloaders before flashing, but I belive I should be ok:
I flashed JME successfully in the past and should be pre-rooted.
I also have reasons to think my bootloaders are not protected as:
I tried chainfire's SGTBootloaderCheck-1.0,it says I am clean.
I can flash CF-root, which is supposed to fail on protected bootloader.
I was brave and stupid enough to format /boot from recovery. Tab would not boot but I could flash it back from Odin with no problems (still, flashed an incomplete ROM without hidden.rfs)
i also tried other ROMS, but have the same problem with all of them
I tried chainfire's SGTBootloaderCheck-1.0 while on recovery mode, but it says I am clean
I cannot get out of this brick, can anyone point me in the right direction?
I'm not the one with the answers, but I casually saw these two posts hours ago:
How to unbrick tabs:
http://forum.xda-developers.com/show....php?t=1133590
This unlocks bootloaders so your SamFirmware.com rom won't brick you:
http://forum.xda-developers.com/showthread.php?t=888071
thanks but I have already seen and tried all of these.
The most commune solution to a soft brick in the forum is: "flash again".
but in my case it seems I just cannot flash anything.
Perhaps what I am looking for is a method/checklist to diagnostic the source of my problem?
or should I just keep trying flashing every possible rom? (i already tried at least 9)
2 cents
Hi,
First of all, get AF974's ROM and also his kernel and the modem for your region. Put these zips on your external SD.
Get into recovery : mount every single thing you can mount, then format every thing (use ext4 if possible). Without leaving recovery, flash the kernel , then the ROM and finally the modem. Reboot and wait ...
thank you but I'd need more directions..
dirlan2001 said:
First of all, get AF974's ROM and also his kernel and the modem for your region. Put these zips on your external SD.
Get into recovery : mount every single thing you can mount, then format every thing (use ext4 if possible). Without leaving recovery, flash the kernel , then the ROM and finally the modem. Reboot and wait ...
Click to expand...
Click to collapse
Thank you. this is a new approach and definitively worth trying it.
I would need more directions thou, as I only can flash roms using odin.
Are you saying I can flash this ROM from the recovery mode, I don't need Odin?
I am a bit confusing about the process: you are saying: 1) mount everything 2) format 3) flash.
1. What do you mean my 'mounting'?
when I go to my recovery mode i can see the option 'apply update from sdcard'. Is this what you mean by mounting?
2. Then format everything. what and how? you mean the SDcard? I am not aware of anything else I could be formatting. Please precise.
3. then flash everything.
how is flash different by Mounting, in this case? havent I already 'applyed' these files in step 1?
I am sorry if all these questions sounds idiot, I probably miss a lot of basic knowledge. I swear I did my homework, I spent DAYS reading all the forums. It's just hard to catch up everything from stratch without help.
thank you!!
i think i got it
I think I got why I dindt understand your previous post:
I dont have thoese options in Recovery.
The only things I see are:
Reboot, apply update from sdcard, wipe data, wipe cache.
This phone was originally working with Roto-JME and then bricked while flashing JQ1. I am not sure which version does this recovery belongs to.
Can I still do anything with this version of recovery?
jacopo3001 said:
I think I got why I dindt understand your previous post:
I dont have thoese options in Recovery.
The only things I see are:
Reboot, apply update from sdcard, wipe data, wipe cache.
This phone was originally working with Roto-JME and then bricked while flashing JQ1. I am not sure which version does this recovery belongs to.
Can I still do anything with this version of recovery?
Click to expand...
Click to collapse
Hi,
Seems you got a old CWM (probably 3.x) that came with Roto"s ROM. Anyway, if you got the files I previously mentioned, make a copy of the kernel.zip and rename it into update.zip, put that 'new' update zip on your SD (eventually replacing the old one) and fire up CWM, running the 'update from SD'.
After reboot you should have a newer CWM that has more options to it. Note that the reboot may take some time... Then you can use the 'mount' to get all partitions mounted r/w... Then you run the kernel.zip and the ROM.zip from 'install zip from SD | go to external SD | choose the kernel.zip // redo the same for the ROM.zip without rebooting in between'
jacopo3001 said:
I think I got why I dindt understand your previous post:
I dont have thoese options in Recovery.
The only things I see are:
Reboot, apply update from sdcard, wipe data, wipe cache.
This phone was originally working with Roto-JME and then bricked while flashing JQ1. I am not sure which version does this recovery belongs to.
Can I still do anything with this version of recovery?
Click to expand...
Click to collapse
This sounds like you are in stock recovery and need cwm installed again.
________________________
Sent from my DROIDX X
dirlan2001 said:
Seems you got a old CWM (probably 3.x) that came with Roto"s ROM. Anyway, if you got the files I previously mentioned, make a copy of the kernel.zip and rename it into update.zip, put that 'new' update zip on your SD (eventually replacing the old one) and fire up CWM, running the 'update from SD'.
Click to expand...
Click to collapse
thank you I will try later tonight.
yesterday I was quite desperate and sent the tab in to the local samsung assistance center, and they just called me they couldnt fix it!
Tonight as I get it back I will try this approach and will let you know.
thanks
jacopo3001 said:
thank you I will try later tonight.
yesterday I was quite desperate and sent the tab in to the local samsung assistance center, and they just called me they couldnt fix it!
Tonight as I get it back I will try this approach and will let you know.
thanks
Click to expand...
Click to collapse
On second thought, it may even be better to install the Overcome kernel first. That has the most recent version of CWM build in, and it makes your device ext4 instead of the old RFS. After that you easily can flash AF974's combo via CWM, whitout need to rename/copy anything. The link provides the guide to the mirror of OC, as their website isn't working anymore...
dirlan2001 said:
it may even be better to install the Overcome kernel
Click to expand...
Click to collapse
I have tried to flash GB-Stock-Safe-v5 (as for Overcome's docs) with Odin but it fails, just like all the other flashes I tried.
Btw, I just discovered that on the back of my TAB (chinese unicom) is written WCDMA. As I always used GSM cards with it I always assumed it was a GSM version, but now I am getting the doubt.
can you confirm I am on GSM version?
the full specs written on the back case are:
WCDMA无线数据终端 (wireless data terminal)
Model：GT-P1000
CMIIT 10 2010CP4950
jacopo3001 said:
I have tried to flash Overcome with Odin before but it fails, just like all the other flashes I tried in this period.
Btw, I just discovered that on the back of my TAB (chinese unicom) is written WCDMA. As I always used GSM cards with it I always assumed it was a GSM version, but now I am getting the doubt.
can you confirm I am on GSM version?
the full specs written on the back case are:
WCDMA无线数据终端 (wireless data terminal)
Model：GT-P1000
CMIIT 10 2010CP4950
Click to expand...
Click to collapse
Hi,
WCDMA is the 3.5G data-line : this means, it's NOT the WiFi alone version. If it's marked as P1000 just as is, then it's the GSM version. That means, you have EDGE/GPRS quadband @ 850/900/1800/1900 Mhz and HSDPA 7.2Mb/s=HSUPA 5.7 Mb/s triband @ 900/1900/2100 Mhz ...
Hmmm, what error did Odin give out when the flash failed ?
BTW, happy newyear etc ...
dirlan2001 said:
BTW, happy newyear etc ...
Click to expand...
Click to collapse
Happy new year to you, and that you very much for your help!
dirlan2001 said:
Hmmm, what error did Odin give out when the flash failed ?
Click to expand...
Click to collapse
Basically it's always the same error, no matter which ROM i flash.
it always fails at either Hidden.rfs or Movinand.mst, depending on the ROM.
here is how it looks like when I try GB-Stock-Safe (recommended by Overcome) for example:
Code:
<ID:0/018> Firmware update start..
<ID:0/018> boot.bin
<ID:0/018> cache.rfs
<ID:0/018> dbdata.rfs
<ID:0/018> factoryfs.rfs
<ID:0/018> movinand.mst
<ID:0/018>
<ID:0/018> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
If I remove these files (Hidden.rfs or Movinand.mst) from the TAR i can flash with no errors, but the tablet wouldn't boot.
This apply to EVERY Roms i tried so far, with no exclusion.
I am making up a new theory: the first bricking error happened after I flashed JQ1, which has bootloaders. Could it be that those bootloaders go in conflicts with the chinese version of hardware, and thefore the brick?
I am keep trying flashing different combinations of ROM's, I am just afraid to get worst... :S
jacopo3001 said:
Happy new year to you, and that you very much for your help!
Basically it's always the same error, no matter which ROM i flash.
it always fails at either Hidden.rfs or Movinand.mst, depending on the ROM.
I am keep trying flashing different combinations of ROM's, I am just afraid to get worst... :S
Click to expand...
Click to collapse
Hi,
No thanks, you're welcome LOL
The problem seems indeed the bootloaders playing up. I guess you'll need to try repair them with this thread from the same guy that made this thread
I suggest you try to repair the lot via the guides he gives to get a up and running again. After that you can retry to install AF974's latest...
Cheers, and good luck
dirlan2001 said:
The problem seems indeed the bootloaders playing up. I guess you'll need to try repair them with this thread from the same guy that made this thread.
I suggest you try to repair the lot via the guides he gives to get a up and running again. After that you can retry to install AF974's latest...
Click to expand...
Click to collapse
thanks, I know those threads already (read them all!)
the main problem I don't get about the bootloader fix is that chainfire released a APK, which assume you can boot the phone!
He starts the thread saying his phone was bricked and cannot flash anything on it, then he fixes it with a APK! that got me lost, how to get out of the brick first?
regarding AF974, that's not my priority, I am just trying to have this thing working again..
jacopo3001 said:
He starts the thread saying his phone was bricked and cannot flash anything on it, then he fixes it with a APK! that got me lost, how to get out of the brick first?
Click to expand...
Click to collapse
Hi,
He did a 200 mile trip to have the MoBo changed .. LOL That doesn't help you any further I guess...
Did you try to put the renamed kernel.zip and flash that through CWM as I previously proposed ? What is the outcome ? Or eventual errors ?
PS : as long as you can get it in download mode (odin) or CWM it's not a brick, it just not booting completely...
dirlan2001 said:
Hi,
Did you try to put the renamed kernel.zip and flash that through CWM as I previously proposed ? What is the outcome ? Or eventual errors ?
Click to expand...
Click to collapse
I chickened out last minute!
I could upgrade to a latest version of CWM by simply flashing CF-ROOT with odin.
but I was not sure about proceeding mounting Overcome's kernel:
OC's documentation raccomends to mount on a clean and functioning install of JQ1 (which i dont have) and says that its kernel will automatically convert the formatting to ext4.
I am not sure it's a good idea to convert formatting while at this situation.
Would I be able to revert in case something goes wrong?
What do you think?
jacopo3001 said:
I chickened out last minute!
I could upgrade to a latest version of CWM by simply flashing CF-ROOT with odin.
but I was not sure about proceeding mounting Overcome's kernel:
OC's documentation raccomends to mount on a clean and functioning install of JQ1 (which i dont have) and says that its kernel will automatically convert the formatting to ext4.
I am not sure it's a good idea to convert formatting while at this situation.
Would I be able to revert in case something goes wrong?
What do you think?
Click to expand...
Click to collapse
Hi,
Do I understand correctly your system is up and running again ? In that case I would certainly recommend to run the complete guide to make it first stock again. The kernel indeed does a conversion to ext4, which is a way better filesystem as the rfs from Samsung. Look in the Overcome thread for the mirrors as OC seems still to have serious problems with their serversystem.
And if you take courage (and the habit) you might start looking for a more recent kernel and ROM...
dirlan2001 said:
Do I understand correctly your system is up and running again ?
Click to expand...
Click to collapse
The system is NOT up and running.
It's hanging at the Samsung logo.
But I can at least get to both download and recovery mode.
What happens is that, regardless which ROM I try, I cannot flash neither hidden.rfs nor movinand.mst (depending on Rom's content), they always FAIL on ODIN.
If I flash a ROM removing those 2 it Odin would success, but the tab will not Boot and hang at Samsung logo.
That's why I say the system is not stable now, I am not sure whether it's a good idea to go into changing FS now or would it screw up things even worst...
Was running looper just fine on my 920t when system started fc/ing . Flashed latest kt kernal. Still f/c . Wiped chash nothing. Odin back to stock, STILL system F/C! Wiped / Factory reset , retried odin stock , still F/Cing.. Is there ANYTHING else that I can try? I can get into Download ,
Cummins4 said:
Was running looper just fine on my 920t when system started fc/ing . Flashed latest kt kernal. Still f/c . Wiped chash nothing. Odin back to stock, STILL system F/C! Wiped / Factory reset , retried odin stock , still F/Cing.. Is there ANYTHING else that I can try? I can get into Download ,
Click to expand...
Click to collapse
If it's still happening after two Odin flashes something is seriously wrong with your phone. It started force closing out of the blue? Your sure you weren't poking around in partitions other than system and data?
No, everything was working fine on looper. I flashed Alliance in the 925t thread. Let it boot, went back twrp then flashed latest kt kernel. That's when I started to get the fc. Figured I did something wrong, so Odin stock tar. Still getting the fc. Sorry for the miss post. Just frantic..
So it turns out by dirty flashing a 925t rom with a 920t kernel over a 920t rom some how caused a system wide fc loop from hell. Completely wiped everything in Stock recovery, also tried twrp. Odin stock tar several times.... I finally threw in the flag and ordered a replacement.. Just thought I'd share,
Cummins4 said:
So it turns out by dirty flashing a 925t rom with a 920t kernel over a 920t rom some how caused a system wide fc loop from hell. Completely wiped everything in Stock recovery, also tried twrp. Odin stock tar several times.... I finally threw in the flag and ordered a replacement.. Just thought I'd share,
Click to expand...
Click to collapse
The weird part is odin *should* have fixed any problems a rom could cause. Good luck with your next phone, really sucks you had to replace it.
ThePagel said:
The weird part is odin *should* have fixed any problems a rom could cause. Good luck with your next phone, really sucks you had to replace it.
Click to expand...
Click to collapse
Thanks, lesson learned.. Been flash dozens of ROMS since my s2, first-time ever I couldn't save a device. Just so weird. Tried stock tar right from Sammy with everything wiped. Wish someone had an idea what would've caused it. Right Odin, right tar, Samsung cable, different computers... Just think I'll leave it alone from now on. Too expensive to mess around with this device, especially without a reliable fall back.
Just wondering if anyone had any idea on how to fix a force close loop after stock Odin flash? I bought a new device. Obviously my warranty is void. I didn't have insurance. I'm left with a really shiny paperweight. I'm willing to try anything, thanks in advance.
1.) I decided to install Franco Kernel to see what positive effects if any it had on Light Flow.
2.) Before hand I did a full Backup in TWRP checked everything Boot, Recovery, System, System Image, Data, and Cache.
3.) I installed Franco Kernel No problem, but didn't see any advantages so I Decided to revert back
4.) I ran a TWRP Restore with all the same Items Checked, it finished and Now I stand on the Google screen with the unlocked bootloader Icon and nothing else happening.
I cant even figure out how to connect it to ADB or Wug's Nexus Root Toolkit since it won't show on USB...How do I reboot into a safe mode, nothing seems to work.
Follow UP...
I managed to boot into TWRP recovery again...and it said no OS installed...So I decided perhaps I had checked too many and just re-ran System Image only. It now boots but I still have Franco Kernel..I don't mind it but would rather go stock.
I thought System Image included the Kernel.. Is there an easy way to go back to the original kernel?
flipper44 said:
I managed to boot into TWRP recovery again...and it said no OS installed...So I decided perhaps I had checked too many and just re-ran System Image only. It now boots but I still have Franco Kernel..I don't mind it but would rather go stock.
I thought System Image included the Kernel.. Is there an easy way to go back to the original kernel?
Click to expand...
Click to collapse
Go back to TWRP Restore and check the box for boot only. If you backed up boot it should flash the stock kernel.
flipper44 said:
I managed to boot into TWRP recovery again...and it said no OS installed...So I decided perhaps I had checked too many and just re-ran System Image only. It now boots but I still have Franco Kernel..I don't mind it but would rather go stock.
I thought System Image included the Kernel.. Is there an easy way to go back to the original kernel?
Click to expand...
Click to collapse
There is a thread called:
'How to flash a new boot.img via Fastboot'
But... Franco's kernel is better for your battery.
NLBeev said:
There is a thread called:
'How to flash a new boot.img via Fastboot'
But... Franco's kernel is better for your battery.
Click to expand...
Click to collapse
Probably will Go back to Franco, But since I just got this I should probably monitor what I do and don't like over the weekend before choosing my daily Driver Kernel and Rom. Thanks to you both.
prdog1 said:
Go back to TWRP Restore and check the box for boot only. If you backed up boot it should flash the stock kernel.
Click to expand...
Click to collapse
That was Brain Freeze, and minor panic LOL...for some reason I wasn't processing Boot = Kernel..Thanks to both people who answered.
Hello guardians of the Android Phones. I ran into a major issue while updating from 5.1.1 custom ROM to 6.0.1 that I found on this thread : http://forum.xda-developers.com/tmo...20t-android-6-0-1-marshmallow-update-t3356838
Steps I took:
1) Upgraded TWRP to 3.0.2.0 (3.0.2.1 doesn't work properly on my device. it flashes the TWRP 3 logo and then goes black) ... So I ended up re-installing TWRP 2.8.7.2 and then flashed TWRP 3.0.2.0
2) Copied the ROMS of choice to the SDCARD
3) Using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM (which didn't work correctly due to the bootloader not being Marshmallow 6.0.1 compatible) from my understanding of what i've read through these threads.
4) Flashed the AP using G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_HOME.tar.md5
Now i'm 100% locked out from downgrading Stock or Custom ROMS. TWRP can no longer be installed.
Having a feeling I used a Bear Trap ROM.
What do I do? Feeling like throwing this out the window. *sigh*.
Thanks ahead of time... anything to point me in the right direction would be greatly appreciated.
I am not a dev... but I tried smartswitch, perhaps it can help you. Hopefully you didn't do factory reset.
Try that and then if it doesn't work, again, wait for the experts.
What is SmartSwitch? Do you have a URL or THREAD with information and download links?
Thanks for the tip.
britchel said:
I am not a dev... but I tried smartswitch, perhaps it can help you. Hopefully you didn't do factory reset.
Try that and then if it doesn't work, again, wait for the experts.
Click to expand...
Click to collapse
I did an Odin flash of EPF1 and didn't lose the ability to flash recovery. I have not yet tried downgrading. I would take a deep breath, drink a beer or two, and go back through things step by step. At this point I would suggest using Odin to flash a complete image, perhaps of a different version, and go from there.
ninjadroids said:
What is SmartSwitch? Do you have a URL or THREAD with information and download links?
Thanks for the tip.
Click to expand...
Click to collapse
http://www.samsung.com/us/smart-switch/assets/downloads/Smart_Switch-PC_setup.exe
Hey can u reboot to recovery and to download mode?
You need to be in download mode to use smart-switch
Here's another tread alike to yours....
http://forum.xda-developers.com/tmo...rick-wont-boot-successful-odin-flash-t3435751
Smiles on the beer or two!
Are you using the G920T also? Which image did you Odin flash with? Do you have the direct link? I do like your idea of flashing with a different 6.x image variant as opposed to downgrading.
socal87 said:
I did an Odin flash of EPF1 and didn't lose the ability to flash recovery. I have not yet tried downgrading. I would take a deep breath, drink a beer or two, and go back through things step by step. At this point I would suggest using Odin to flash a complete image, perhaps of a different version, and go from there.
Click to expand...
Click to collapse
Yes I can reboot into recovery and to download mode. Thank you for the link.
britchel said:
http://www.samsung.com/us/smart-switch/assets/downloads/Smart_Switch-PC_setup.exe
Hey can u reboot to recovery and to download mode?
You need to be in download mode to use smart-switch
Here's another tread alike to yours....
http://forum.xda-developers.com/tmo...rick-wont-boot-successful-odin-flash-t3435751
Click to expand...
Click to collapse
ninjadroids said:
Smiles on the beer or two!
Are you using the G920T also? Which image did you Odin flash with? Do you have the direct link? I do like your idea of flashing with a different 6.x image variant as opposed to downgrading.
Click to expand...
Click to collapse
I don't unfortunately - Google is your friend. Some firmwares that come to mind are DOJ7, DOJC, and COF6.
But first: Is your bootloader locked? If you have not yet unlocked it, that may be a problem. I unlocked mine as soon as I got my phone (and yes I'm on a G920T). A locked bootloader may prevent downgrading although it should not prevent a rescue Odin of the same or newer firmware.
Yes it's locked.
Is there a way to unlock it while maintaining my current image?
All those firmware are 5.x
I'm stuck on unlocked Marshmallow 6.0.1
And according to Smart Switch. I'm one version down from latest with it prompting to upgrade.
I'm going to hold off on that for the moment...
If you flashed edp1, you are far from latest.
Lemme know if i am wrong at anything
If you can access download and recovery, that means the phone is in a bootloop when booting up..
Since you flashed the edp1 firmware, your bootloader must have been updated so now you can only use mm roms.
As for recovery, is it stock or twrp?
Also when in download modex whats your system status - stock or custom?
Well if EDP1 is far from latest, then that is great news. I can boot into my firmware. It's for sure stock as far as I can tell.
Download mode output:
RED: ODIN MODE
PRODUCT NAME: SM-G920T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
FAP LOCK: OFF
BLUE: Secure Download: Enabled
Knox Warranty Void: 1 (I tripped it when rooting it in 5.x)
AP SWREV: B:3 K:2 S:2
It won't let me get into TWRP after flashing it... when I try it says the following:
RED: "RECOVERY IS NOT SEANDROID ENFORCING"
It doesn't matter which version of TWRP I attempt to flash with.
Thanks!
danveer said:
If you flashed edp1, you are far from latest.
Lemme know if i am wrong at anything
If you can access download and recovery, that means the phone is in a bootloop when booting up..
Since you flashed the edp1 firmware, your bootloader must have been updated so now you can only use mm roms.
As for recovery, is it stock or twrp?
Also when in download modex whats your system status - stock or custom?
Click to expand...
Click to collapse
Did you flashed root or anything after you tried to flash recovery via odin?
Also when you flashed edp1, phone still didnt boot?
Edp1 is about the march or april update i think
The next main update is epf1 because it restricts going back futher
Then there came a update 5 days ago.. just a security update... havent flashed that coz i am rooted..
Anyways lets concentrate on edp1
Since its a mm rom, going back to 5.1 roms means a bootloop, so ill suggest not doing that
Also after flashing the mm rom, if you flash anything over it, you wont be able to boot a system because a new dm verity check mm has introduced.. to bypass it, you either need to flash a mm root file or a kernel that can disable the check.
I was stuck at the same thing since i Flashed recovery and that failed the checks so was getting bootloops..
I was able to go in recovery and download mode but not boot up..
Since you have a custom status, it can be a reason for bootloops
http://forum.xda-developers.com/gal...y-official-twrp-galaxy-s6-edge-t3354508/page8
The phone boots. I just cannot get root. I guess I don't understand the terminology regarding "bootloops" or "MM" ... I attempted a APK root... which failed. And still using my previous kernel unless flashing the custom ROM overwrote that.
So I can login to the phone and connect it to USB and sideload APK files, no problem. I just cannot TWRP flash properly and enter it using the UP recovery mode. And when I tried flashing other ROMS in Download recovery mode either ODIN crashes or it gives me a NAND WRITE error.
Which root and / or kernel files would you suggest to me to flash in ODIN to break this protection that's preventing a full root on this image? Or would it be preferable in my situation to find a different ROM and resolving the ODIN crash problem to achieve a full 6.x marshmallow root?
Thanks again! Greatly appreciated Sir.
danveer said:
Did you flashed root or anything after you tried to flash recovery via odin?
Also when you flashed edp1, phone still didnt boot?
Edp1 is about the march or april update i think
The next main update is epf1 because it restricts going back futher
Then there came a update 5 days ago.. just a security update... havent flashed that coz i am rooted..
Anyways lets concentrate on edp1
Since its a mm rom, going back to 5.1 roms means a bootloop, so ill suggest not doing that
Also after flashing the mm rom, if you flash anything over it, you wont be able to boot a system because a new dm verity check mm has introduced.. to bypass it, you either need to flash a mm root file or a kernel that can disable the check.
I was stuck at the same thing since i Flashed recovery and that failed the checks so was getting bootloops..
I was able to go in recovery and download mode but not boot up..
Since you have a custom status, it can be a reason for bootloops
http://forum.xda-developers.com/gal...y-official-twrp-galaxy-s6-edge-t3354508/page8
Click to expand...
Click to collapse
ninjadroids said:
The phone boots. I just cannot get root. I guess I don't understand the terminology regarding "bootloops" or "MM" ... I attempted a APK root... which failed. And still using my previous kernel unless flashing the custom ROM overwrote that.
So I can login to the phone and connect it to USB and sideload APK files, no problem. I just cannot TWRP flash properly and enter it using the UP recovery mode. And when I tried flashing other ROMS in Download recovery mode either ODIN crashes or it gives me a NAND WRITE error.
Which root and / or kernel files would you suggest to me to flash in ODIN to break this protection that's preventing a full root on this image? Or would it be preferable in my situation to find a different ROM and resolving the ODIN crash problem to achieve a full 6.x marshmallow root?
Thanks again! Greatly appreciated Sir.
Click to expand...
Click to collapse
Which odin are you using?
Try 3.10.7 because using older odin on mm gives that nand write error...
That could explain a lot of things
I'm using 3.10.7 latest.
danveer said:
Which odin are you using?
Try 3.10.7 because using older odin on mm gives that nand write error...
That could explain a lot of things
Click to expand...
Click to collapse
http://forum.xda-developers.com/che...rite-start-fail-odin-soluction-t2851096/page5
Try this thread..
It has solutions when nand write fails...
Also trying a different verion pf odin might work like 3.10.6 or another maybe
ninjadroids said:
Yes it's locked.
Is there a way to unlock it while maintaining my current image?
All those firmware are 5.x
I'm stuck on unlocked Marshmallow 6.0.1
And according to Smart Switch. I'm one version down from latest with it prompting to upgrade.
I'm going to hold off on that for the moment...
Click to expand...
Click to collapse
EPD1 and EPF1 are 6.0.1 Marshmallow.
@ninjadroids:
Take this as you will but reading back through this thread gives me the impression that you lack the necessary know-how to customize your phone. I highly suggest you leave it stock for the time being until you know EXACTLY what you are doing.
My reasons for saying this:
-In your first post you state that "using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM". To my knowledge there are NO custom ROMs designed to be flashed via Odin. They are in .zip files, to be installed via recovery ONLY.
-This is actually my mistake - the G920T bootloader does not have a lock function; flashing a custom recovery will simply trip the e-fuse and render it Knox 0x1 warranty void.
-You are not familiar with what Odin images are for the G920T, or what version they are. You should NEVER flash ANYTHING via Odin unless you are absolutely sure it is intended for your specific device.
-In the 9th post you state your bootloader is unlocked (again I apologize for the confusion) but in the 3rd line you say you're on unlocked Marshmallow. I'm going to assume you have limited knowledge of what the bootloader, the recovery, download mode, and system are.
-You mention seeing the red "RECOVERY IS NOT SE ANDROID ENFORCING". This is an error message generated by the bootloader saying the recovery is custom and did not pass the security check...but it is also completely normal. I get it every single time I go into TWRP...which works just fine.
-You do not understand what "MM" means when all of us including you are talking about Marshmallow.
-You do not understand what a "bootloop" is. For the sake of education, a bootloop is exactly what it sounds like - your device gets stuck in a loop while booting. This is generally mentioned when it is persistent - the device does not complete the boot process, coming to a stable useable Android interface. This is indicative of several possible problems; most likely you did something incorrectly, causing the boot process to halt, in which case the phone restarts itself to attempt to boot again, hence the loop.
-You do seem to understand sideloading via ADB and I'll give you credit for that. But when using the button combo (Vol Up+Home+Pwr) to boot into recovery, you WILL boot into recovery...whether that is stock recovery or TWRP. Some reboots may prevent this; if in doubt, hold Vol Down+Home+PWR until the screen shuts off; immediately go to Vol UP while still holding Home and Power.
-In the 13th post you ask about flashing kernels via Odin. Firstly: custom ROM .zips contain the kernel intended to work with that ROM. There is no need to flash anything separately. I am a little fuzzy on how root is accomplished on stock Marshmallow; it used to be we could flash SuperSu via recovery, but now there is talk about systemless...Anyway, I will reiterate what I was saying about Odin: DO NOT USE IT unless you know EXACTLY what you are doing. You have the potential to turn your phone into an expensive paperweight.
I am not trying to put you on blast or criticize you; I'm trying to help you avoid bricking your phone. There are a lot of things that could go wrong; you shouldn't be messing with something you don't understand, especially if you don't know how to fix it if something goes wrong.
For now even i am confused as to what is causing error.
Its probably that his storage is not curropt causing namd write fail..
I would recommend doing a backup. since you can turn on a phone, connect it to pc and move the important files and contacts to it.
Then download stock rom via sam mobile and do a clean install..
Ill prefer pf1 because, if memory serves right, edp1 had that notorious auto brightness bug.. If odin is not helping then try smart switch.
Boot up system, see if everything is working..it should be fresh as new.
After that follow the instructions as to flash twrp from the link i gave in one of my previous posts.. twrp should now flash...( i dont see any reason it shouldnt )
Flash root via recovery, or a custom rom you wanna flash but make sure its a 6.0.1 one ( xtre sto lite or alexis recommended )
That should root your phone too...
P.s. mm -> short for MarshMallow
Bootloop, when all you see is samsung logo which comes during boot... it wont go past that.. you never reach your lock screen or are able to unlock your phone... as mentioned in detail by -> socal
Flashing any rom overwrites kernel so if you flashed edp1, you are now on stock kernel...
P.p.s when you said sideload apk.. was it via adb shell or simply installing apk from internal memory of phone?
You answered a lot of my questions in that last post. Thank you kindly.
socal87 said:
EPD1 and EPF1 are 6.0.1 Marshmallow.
@ninjadroids:
Take this as you will but reading back through this thread gives me the impression that you lack the necessary know-how to customize your phone. I highly suggest you leave it stock for the time being until you know EXACTLY what you are doing.
My reasons for saying this:
-In your first post you state that "using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM". To my knowledge there are NO custom ROMs designed to be flashed via Odin. They are in .zip files, to be installed via recovery ONLY.
-This is actually my mistake - the G920T bootloader does not have a lock function; flashing a custom recovery will simply trip the e-fuse and render it Knox 0x1 warranty void.
-You are not familiar with what Odin images are for the G920T, or what version they are. You should NEVER flash ANYTHING via Odin unless you are absolutely sure it is intended for your specific device.
-In the 9th post you state your bootloader is unlocked (again I apologize for the confusion) but in the 3rd line you say you're on unlocked Marshmallow. I'm going to assume you have limited knowledge of what the bootloader, the recovery, download mode, and system are.
-You mention seeing the red "RECOVERY IS NOT SE ANDROID ENFORCING". This is an error message generated by the bootloader saying the recovery is custom and did not pass the security check...but it is also completely normal. I get it every single time I go into TWRP...which works just fine.
-You do not understand what "MM" means when all of us including you are talking about Marshmallow.
-You do not understand what a "bootloop" is. For the sake of education, a bootloop is exactly what it sounds like - your device gets stuck in a loop while booting. This is generally mentioned when it is persistent - the device does not complete the boot process, coming to a stable useable Android interface. This is indicative of several possible problems; most likely you did something incorrectly, causing the boot process to halt, in which case the phone restarts itself to attempt to boot again, hence the loop.
-You do seem to understand sideloading via ADB and I'll give you credit for that. But when using the button combo (Vol Up+Home+Pwr) to boot into recovery, you WILL boot into recovery...whether that is stock recovery or TWRP. Some reboots may prevent this; if in doubt, hold Vol Down+Home+PWR until the screen shuts off; immediately go to Vol UP while still holding Home and Power.
-In the 13th post you ask about flashing kernels via Odin. Firstly: custom ROM .zips contain the kernel intended to work with that ROM. There is no need to flash anything separately. I am a little fuzzy on how root is accomplished on stock Marshmallow; it used to be we could flash SuperSu via recovery, but now there is talk about systemless...Anyway, I will reiterate what I was saying about Odin: DO NOT USE IT unless you know EXACTLY what you are doing. You have the potential to turn your phone into an expensive paperweight.
I am not trying to put you on blast or criticize you; I'm trying to help you avoid bricking your phone. There are a lot of things that could go wrong; you shouldn't be messing with something you don't understand, especially if you don't know how to fix it if something goes wrong.
Click to expand...
Click to collapse
Wonderful. Thanks man. I will be attempting a Stock ROM Odin flash and go from there. I will update my progress. Thank you all very much for the answered questions and pointing me in the right direction. Hopefully this thread will prove useful for anyone who is attempting to deal with a G920-T and attaining root the proper way for Marshmallow 6.x
danveer said:
For now even i am confused as to what is causing error.
Its probably that his storage is not curropt causing namd write fail..
I would recommend doing a backup since you can turn on a phone
Then downloading stock rom via sam mobile and do a clean install...if odin is not helping doing that then try smart switch.
Boot up system, see if everything is working..
After that follow the instructions as to flash twrp from the link i gave in one of my previous posts.. twrp should now flash...( i dont see any reason it shouldnt )
Flash root via recovery, or a custom rom you wanna flash vut make sure its a 6.0.1 one ( xtre sto lite or alexis recommended )
That should root your phone too...
Click to expand...
Click to collapse