Related
Hello, I am MrGovernor.
I have recently purchased a Galaxy Note 3 N9005 and decided to root it earlier today. The device is running on 4.3 because my carrier decide to delay their releases (O2).
About 2 hours ago I then decided to put a custom recovery on it before installing Omega ROM...
Now, me being a newb, I was following about 3 different tutorials at once; I managed to get to the final stage of using ODIN to flash CWM onto the phone (n9005-cwm-recovery-6.0.4.7-kk). Now, I did this and when my phone rebooted it got the initial loading screen and this message appeared:
RECOVERY BOOTING....
Click to expand...
Click to collapse
Set Warranty Bit : recovery
Click to expand...
Click to collapse
This happens when I go into Recovery Mode and when I boot normally. I can still go into download mode.
I am a newb, have I bricked my new phone or is there any way to salvage it?
Thanks a load!
MrGovernor.
MrGovernor said:
Hello, I am MrGovernor.
I have recently purchased a Galaxy Note 3 N9005 and decided to root it earlier today. The device is running on 4.3 because my carrier decide to delay their releases (O2).
About 2 hours ago I then decided to put a custom recovery on it before installing Omega ROM...
Now, me being a newb, I was following about 3 different tutorials at once; I managed to get to the final stage of using ODIN to flash CWM onto the phone (n9005-cwm-recovery-6.0.4.7-kk). Now, I did this and when my phone rebooted it got the initial loading screen and this message appeared:
This happens when I go into Recovery Mode and when I boot normally. I can still go into download mode.
I am a newb, have I bricked my new phone or is there any way to salvage it?
Thanks a load!
MrGovernor.
Click to expand...
Click to collapse
no its fine all n3 rooted will have that when and if you go back to stock it will go
jaythenut said:
no its fine all n3 rooted will have that when and if you go back to stock it will go
Click to expand...
Click to collapse
Thanks a load!
MrGovernor said:
Hello, I am MrGovernor.
I have recently purchased a Galaxy Note 3 N9005 and decided to root it earlier today. The device is running on 4.3 because my carrier decide to delay their releases (O2).
About 2 hours ago I then decided to put a custom recovery on it before installing Omega ROM...
Now, me being a newb, I was following about 3 different tutorials at once; I managed to get to the final stage of using ODIN to flash CWM onto the phone (n9005-cwm-recovery-6.0.4.7-kk). Now, I did this and when my phone rebooted it got the initial loading screen and this message appeared:
This happens when I go into Recovery Mode and when I boot normally. I can still go into download mode.
I am a newb, have I bricked my new phone or is there any way to salvage it?
Thanks a load!
MrGovernor.
Click to expand...
Click to collapse
it's normal
hhai2pth said:
it's normal
Click to expand...
Click to collapse
Now... Another issue...
I installed PhilZ Touch Recovery and that has worked fine...
However, I went full retard and 'Wiped System for a New ROM' before I made a backup...
I then tried to flash FoxHound ROM, I managed to get through the install process flawlessly, BUT, when the device rebooted it stays on the boot screen...
What can be done to fix this? As I failed to make a backup of my original 4.3 firmware...
Thanks Again!
MrGovernor said:
Now... Another issue...
I installed PhilZ Touch Recovery and that has worked fine...
However, I went full and 'Wiped System for a New ROM' before I made a backup...
I then tried to flash FoxHound ROM, I managed to get through the install process flawlessly, BUT, when the device rebooted it stays on the boot screen...
What can be done to fix this? As I failed to make a backup of my original 4.3 firmware...
Thanks Again!
Click to expand...
Click to collapse
Did u use correct ROM for 4.3? Did u tried flash stock rom again?
hhai2pth said:
Did u use correct ROM for 4.3? Did u tried flash stock rom again?
Click to expand...
Click to collapse
I can't find the 4.3 firmare... Only the 4.4.2 firmare...
I just realized I may have to flash with O2's stock firmare as it is an O2 device...
MrGovernor said:
Hello, I am MrGovernor.
I have recently purchased a Galaxy Note 3 N9005 and decided to root it earlier today. The device is running on 4.3 because my carrier decide to delay their releases (O2).
About 2 hours ago I then decided to put a custom recovery on it before installing Omega ROM...
Now, me being a newb, I was following about 3 different tutorials at once; I managed to get to the final stage of using ODIN to flash CWM onto the phone (n9005-cwm-recovery-6.0.4.7-kk). Now, I did this and when my phone rebooted it got the initial loading screen and this message appeared:
This happens when I go into Recovery Mode and when I boot normally. I can still go into download mode.
I am a newb, have I bricked my new phone or is there any way to salvage it?
Thanks a load!
MrGovernor.
Click to expand...
Click to collapse
oh man...
You are running 4.3, but you flash cwm for KK (4.4.2) ?
You should flash cwm for 4.3 instead.
Try to find the stock firmware, and reflash it.
Cheers!
---------- Post added at 05:29 PM ---------- Previous post was at 05:26 PM ----------
MrGovernor said:
Now... Another issue...
I installed PhilZ Touch Recovery and that has worked fine...
However, I went full retard and 'Wiped System for a New ROM' before I made a backup...
I then tried to flash FoxHound ROM, I managed to get through the install process flawlessly, BUT, when the device rebooted it stays on the boot screen...
What can be done to fix this? As I failed to make a backup of my original 4.3 firmware...
Thanks Again!
Click to expand...
Click to collapse
if you have installed the ROM flawlessly and stuck at the boot screen, try go into recovery again and make a full wipe (but not the wipe for new rom). Then reboot.
But the custom ROM you are flashing is 4.3 also right ?
Because very simple, if you were on stock 4.3, and you flash custom ROM 4.4.2 without update your bootloader first to 4.4.2, the custom ROM won't run.
---------- Post added at 05:31 PM ---------- Previous post was at 05:29 PM ----------
MrGovernor said:
I can't find the 4.3 firmare... Only the 4.4.2 firmare...
I just realized I may have to flash with O2's stock firmare as it is an O2 device...
Click to expand...
Click to collapse
if your device N9005, you may use any other firmware so long as for N9005.
You can try to flash 4.4.2, but you have to tick "update bootloader" at ODIN. Please note, once you are on 4.4.2, you are not able to go back to 4.3, due to different bootloader.
antique_sonic said:
oh man...
You are running 4.3, but you flash cwm for KK (4.4.2) ?
You should flash cwm for 4.3 instead.
Try to find the stock firmware, and reflash it.
Cheers!
---------- Post added at 05:29 PM ---------- Previous post was at 05:26 PM ----------
if you have installed the ROM flawlessly and stuck at the boot screen, try go into recovery again and make a full wipe (but not the wipe for new rom). Then reboot.
But the custom ROM you are flashing is 4.3 also right ?
Because very simple, if you were on stock 4.3, and you flash custom ROM 4.4.2 without update your bootloader first to 4.4.2, the custom ROM won't run.
---------- Post added at 05:31 PM ---------- Previous post was at 05:29 PM ----------
if your device N9005, you may use any other firmware so long as for N9005.
You can try to flash 4.4.2, but you have to tick "update bootloader" at ODIN. Please note, once you are on 4.4.2, you are not able to go back to 4.3, due to different bootloader.
Click to expand...
Click to collapse
That's cleared a load up! I'll install the 4.3 firmware and get back to you (Samsung's Firmware Download Servers are incredibly slow <,<)
yeah. good luck
Thanks for all the help!
I used ODIN to flash this file:
N9005XXUENB4_N9005O2UENB1_N9005XXUENB1_HOME.tar.md5
From SamMobile's Firmware.
It's all working now, and it on the 4.4.2 KitKat Built.
Does this mean the bootload has updated and I can install the 4.4 Omega ROM?
This time I will make a restore point on PhilZ Custom Recovery!
MrGovernor said:
Thanks for all the help!
I used ODIN to flash this file:
N9005XXUENB4_N9005O2UENB1_N9005XXUENB1_HOME.tar.md5
From SamMobile's Firmware.
It's all working now, and it on the 4.4.2 KitKat Built.
Does this mean the bootload has updated and I can install the 4.4 Omega ROM?
This time I will make a restore point on PhilZ Custom Recovery!
Click to expand...
Click to collapse
when you flash it, u did tick the update bootloader right ?
If yes, means you are now on the 4.4.2 bootloader, and you can install the 4.4 custom ROM (but please read the respective thread on how to flash that custom ROM of your choice)
And when you want to flash Philz CWM, do choose the one for 4.4.2. Try to use the latest one.
Good luck!
antique_sonic said:
when you flash it, u did tick the update bootloader right ?
If yes, means you are now on the 4.4.2 bootloader, and you can install the 4.4 custom ROM (but please read the respective thread on how to flash that custom ROM of your choice)
And when you want to flash Philz CWM, do choose the one for 4.4.2. Try to use the latest one.
Good luck!
Click to expand...
Click to collapse
Thanks!
But... On last problem...
I've downloaded and used ODIN to install PhillZ Recovery ("philz_touch_6.08.9-hltexx.tar.md5").
It passes in ODIN, and boots straight to android.
However, when I try to boot into recovery mode, I get the normal 3 lines of text, but after a few seconds it reboots back to android...
What do?
P.S: I tried holding down all 3 buttons through the whole process (that just reboots), holding down only the Home and Volume + buttons once the text appears (still reboots)... I've also tried to Re-Flash the same version twice.
I just want to make a backup for this ROM in-case I f*ck up with other ROMs. Sorry for being such a scrub!
------NOTE----------
Installed Latest Version of PhillZ, all works A-OK!
MrGovernor said:
Thanks!
But... On last problem...
I've downloaded and used ODIN to install PhillZ Recovery ("philz_touch_6.08.9-hltexx.tar.md5").
It passes in ODIN, and boots straight to android.
However, when I try to boot into recovery mode, I get the normal 3 lines of text, but after a few seconds it reboots back to android...
What do?
P.S: I tried holding down all 3 buttons through the whole process (that just reboots), holding down only the Home and Volume + buttons once the text appears (still reboots)... I've also tried to Re-Flash the same version twice.
I just want to make a backup for this ROM in-case I f*ck up with other ROMs. Sorry for being such a scrub!
------NOTE----------
Installed Latest Version of PhillZ, all works A-OK!
Click to expand...
Click to collapse
Sorry was bit busy.
But if you do read my last post... I did mentioned you have to use the latest one better
Cheers, mate!
btw :
why do you like to use KK recovery on 4.3, and when you are on KK, you use 4.3 recovery ?
Set warranty bit is different than set warranty kernel
jerryspring said:
Set warranty bit is different than set warranty kernel
Click to expand...
Click to collapse
And what exactly is the point of posting this in a 4.5 years old thread ?
Dejan Sathanas said:
And what exactly is the point of posting this in a 4.5 years old thread ?
Click to expand...
Click to collapse
Cuz I asked a question and no one answered me. What would be causing the bootloop on my phone? With stock and custom ROMs, it is bootlooping in and out of recovery and saying set warranty bit recovery ...
But no user has to answer you .
Post and if somebody sees it and has the answer they will .
But on the Q&A board as very few read it now and a day is not long enough.
JJEgan said:
But no user has to answer you .
Post and if somebody sees it and has the answer they will .
But on the Q&A board as very few read it now and a day is not long enough.
Click to expand...
Click to collapse
The o.p is different than my question! So, instead of making a duplicate thread with basically same issue, I posted in here.
hello guys, i have a Samsung galaxy S5 (SM-G900F)
i installed the latest OTA updates,but today i tried to root my device with CF-auto root file,odin did successfully but the phone didn't restart,it keep saying
recovery rooting,
recovery is not standadid enforcing or something like that
set warranty bit : recovery
it keep saying for like 10min but nothing showed up,then i flashed phiztouch recovery file,then the device reboot successfully but after i went to the recovery mode,there is no phiztouch recovery,its the stock recovery
can anyone help me to root the device n to install a phiztouch recovery
CF Auto Root should have worked, I'd try that again
Make sure you use the G900F version
Run ODIN as Admin
Only have F.Reset Time and Auto Reboot ticked in ODIN
Obviously phone in download mode
--
Other alternatives are to flash TWRP with ODIN, then SuperSU from TWRP
*Detection* said:
CF Auto Root should have worked, I'd try that again
Make sure you use the G900F version
Run ODIN as Admin
Only have F.Reset Time and Auto Reboot ticked in ODIN
Obviously phone in download mode
--
Other alternatives are to flash TWRP with ODIN, then SuperSU from TWRP
Click to expand...
Click to collapse
No luck bro,i installed Cf auto root file like 3 times,still it keep saying the same thing,then i installed TWRP
its successfully boots up,but when i go to the recovery still i have the stock recovery :'( :'(
Are you using a native PC to flash with ODIN?
Got the Samsung drivers installed?
Mine is the G900F and CF auto root works fine with all firmwares to date, wonder if your bootloader is locked?
*Detection* said:
Are you using a native PC to flash with ODIN?
Got the Samsung drivers installed?
Mine is the G900F and CF auto root works fine with all firmwares to date, wonder if your bootloader is locked?
Click to expand...
Click to collapse
I dont know how to check the bootloader locked or not
i dont know bro,i did everything correctly
yeah i have installed samsung drivers
but no luck
and now the device keep saying my device is modified
but no root access
I tried to install supersu from playstore
but still no luck
I have the same problem....
""recovery rooting,
recovery is not standadid enforcing
set warranty bit : recovery""
I use:
Odin3_v3.10.6
CF-Auto-Root-klte-kltedx-smg900f (5.0.0)
Rom: Baltic (SEB) - SEB-G900FXXU1BOD3-20150527145300 (2015.04.09)
vinura kithmal said:
I dont know how to check the bootloader locked or not
i dont know bro,i did everything correctly
yeah i have installed samsung drivers
but no luck
and now the device keep saying my device is modified
but no root access
I tried to install supersu from playstore
but still no luck
Click to expand...
Click to collapse
Try flashing TWRP from ODIN, then SuperSU from TWRP
[email protected] said:
I have the same problem....
""recovery rooting,
recovery is not standadid enforcing
set warranty bit : recovery""
I use:
Odin3_v3.10.6
CF-Auto-Root-klte-kltedx-smg900f (5.0.0)
Rom: Baltic (SEB) - SEB-G900FXXU1BOD3-20150527145300 (2015.04.09)
Click to expand...
Click to collapse
Yeah,i used odin 3.07 n 3.09 and 3.10.6
but no luck with
i did it with the CF-Auto-Root-klte-kltedx-smg900f (5.0.0) too
*Detection* said:
Try flashing TWRP from ODIN, then SuperSU from TWRP
Click to expand...
Click to collapse
thanx for your suport, i did flash TWRP ,same problem,no luck, um unable to set a custom recovery,odin isdoing a great job,the deices boots up,but when go to the recovery still i have the stock recovery
vinura kithmal said:
thanx for your suport, i did flash TWRP ,same problem,no luck, um unable to set a custom recovery,odin isdoing a great job,the deices boots up,but when go to the recovery still i have the stock recovery
Click to expand...
Click to collapse
Same problem here
Odin 3 V1.85 does everthing correctly, then phone boots correctly, but when I go to recovery, still stock:crying:
Could it be that it has something to do with lollipop 5.0?
Please advice
So long as your bootloader is unlocked, CF Auto Root works fine with the G900F and all Android versions up to the latest
*Detection* said:
So long as your bootloader is unlocked, CF Auto Root works fine with the G900F and all Android versions up to the latest
Click to expand...
Click to collapse
How can I check if my bootloader is locked ord unlocked? Sorry for my noob question.
Did you wipe data before flashing?
Ditomasso said:
Same problem here
Odin 3 V1.85 does everthing correctly, then phone boots correctly, but when I go to recovery, still stock:crying:
Could it be that it has something to do with lollipop 5.0?
Please advice
Click to expand...
Click to collapse
Um not sure too
it cant be
Cz i saw so many videos and tutorials,
they are installing the custom recovery successfully in lolipop
Akalsemann said:
Did you wipe data before flashing?
Click to expand...
Click to collapse
You mean before flashing the custom recovery,
i nvr wiped data before flashing a recovery or a CF auto root file in my earlier devices
but now i did
But still no success bro
Can u tell me the process how to check the bootloader locked or unlocked ??
Akalsemann said:
Did you wipe data before flashing?
Click to expand...
Click to collapse
Yes I did.
This is what I did step by step:
I have odin 3V1.85 installed on my pc and from there I followed all instructions
I put following file in PDA. philz_touch_6.26.6-klte.tar.md5
After that phone rebooted succesfully. But when I want to enter recovery it gives me a warning sign and it enters stock recovery
Android system recovery <3e>
LRX21T.G900FXXU1BNL9
I have flashed alot of roms with my previous phone but this is new for me.
So again appolize for all the "stupid"questions!
I hope someone knows the solution.
Hmm odd, i had the exact same problem when rooting about 3 days ago, now it works but i can't for the life of me figure out how i managed to get it to work. Ill get back to you.
---------- Post added at 07:29 PM ---------- Previous post was at 07:23 PM ----------
vinura kithmal said:
You mean before flashing the custom recovery,
i nvr wiped data before flashing a recovery or a CF auto root file in my earlier devices
but now i did
But still no success bro
Can u tell me the process how to check the bootloader locked or unlocked ??
Click to expand...
Click to collapse
Ditomasso said:
Yes I did.
This is what I did step by step:
I have odin 3V1.85 installed on my pc and from there I followed all instructions
I put following file in PDA. philz_touch_6.26.6-klte.tar.md5
After that phone rebooted succesfully. But when I want to enter recovery it gives me a warning sign and it enters stock recovery
Android system recovery <3e>
LRX21T.G900FXXU1BNL9
I have flashed alot of roms with my previous phone but this is new for me.
So again appolize for all the "stupid"questions!
I hope someone knows the solution.
Click to expand...
Click to collapse
Ok guys, try this.
1. Download philz kernel that matches your modem number. I think philz_touch_6.26.6-klte.tar.md5 works good.
2. Put it in ODIN on PDA/AP
3. Uncheck "Auto Reboot" and make sure Re-Partition is NOT CHECKED (keep F. Reset time)
4. Flash
5. It will say RESET on Odin and nothing further when it is done so just wait 2-3 minutes when RESET appears to be entirely sure that the procedure is done.
6. Pull out phones battery.
7. Put it back in and now go into Recovery directly (Vol up+home+power)
8. ???
9. Profit
Hopefully this might work, i think i did the same
Akalsemann said:
Hmm odd, i had the exact same problem when rooting about 3 days ago, now it works but i can't for the life of me figure out how i managed to get it to work. Ill get back to you.
---------- Post added at 07:29 PM ---------- Previous post was at 07:23 PM ----------
Ok guys, try this.
1. Download philz kernel that matches your modem number. I think philz_touch_6.26.6-klte.tar.md5 works good.
2. Put it in ODIN on PDA/AP
3. Uncheck "Auto Reboot" and make sure Re-Partition is NOT CHECKED (keep F. Reset time)
4. Flash
5. It will say RESET on Odin and nothing further when it is done so just wait 2-3 minutes when RESET appears to be entirely sure that the procedure is done.
6. Pull out phones battery.
7. Put it back in and now go into Recovery directly (Vol up+home+power)
8. ???
9. Profit
Hopefully this might work, i think i did the same
Click to expand...
Click to collapse
Ok thank you! I'll try this ad soon as I get home. I'll come back to you guys when I have the change
Akalsemann said:
1. Download philz kernel that matches your modem number. I think philz_touch_6.26.6-klte.tar.md5 works good.
2. Put it in ODIN on PDA/AP
3. Uncheck "Auto Reboot" and make sure Re-Partition is NOT CHECKED (keep F. Reset time)
4. Flash
5. It will say RESET on Odin and nothing further when it is done so just wait 2-3 minutes when RESET appears to be entirely sure that the procedure is done.
6. Pull out phones battery.
7. Put it back in and now go into Recovery directly (Vol up+home+power)
8. ???
9. Profit
Hopefully this might work, i think i did the same
Click to expand...
Click to collapse
This worked superbly,thank you very much man,thanx alot,it so annoying to use an android without root,once again thanx alot longlive
Akalsemann said:
Hmm odd, i had the exact same problem when rooting about 3 days ago, now it works but i can't for the life of me figure out how i managed to get it to work. Ill get back to you.
---------- Post added at 07:29 PM ---------- Previous post was at 07:23 PM ----------
Ok guys, try this.
1. Download philz kernel that matches your modem number. I think philz_touch_6.26.6-klte.tar.md5 works good.
2. Put it in ODIN on PDA/AP
3. Uncheck "Auto Reboot" and make sure Re-Partition is NOT CHECKED (keep F. Reset time)
4. Flash
5. It will say RESET on Odin and nothing further when it is done so just wait 2-3 minutes when RESET appears to be entirely sure that the procedure is done.
6. Pull out phones battery.
7. Put it back in and now go into Recovery directly (Vol up+home+power)
8. ???
9. Profit
Hopefully this might work, i think i did the same
Click to expand...
Click to collapse
Mr.Akalsemann you're a wizzard!
It works! Thank you very much! I'll now finally root my phone and put some awesome rom on it!
Any suggestions anyone?
Using Flashfire, I installed the zipped file UPDATE-SuperSU-v1.99r4.zip on my Verizon G900V, which is a towelroot rooted Lollipop. My phone ultimately rebooted, but goes no further than the initial screen. It will not fully reboot, it is not recognized via USB by my PC, it cannot be turned off except by removing the battery, and seems totally bricked. I obviously can’t even odin. I have no other data, such as build, etc., about it since it is no longer accessible. What can I do now? Any help will be most appreciated!
Everhopefull said:
Using Flashfire, I installed the zipped file UPDATE-SuperSU-v1.99r4.zip on my Verizon G900V, which is a towelroot rooted Lollipop. My phone ultimately rebooted, but goes no further than the initial screen. It will not fully reboot, it is not recognized via USB by my PC, it cannot be turned off except by removing the battery, and seems totally bricked. I obviously can’t even odin. I have no other data, such as build, etc., about it since it is no longer accessible. What can I do now? Any help will be most appreciated!
Click to expand...
Click to collapse
That is not totally bricked :victory:
You are just softbricked. First, did you have safestrap installed?
If you don't care about any of the internal data and just want the OS fixed, just put it in download mode (Power+Home+VolDown) then Vol Up to confirm, and get the .tar of the stock image. Flash it with Odin- bam done.
Be warned, because you were towelrooted this would ultimately flash the latest LOCKED bootloader- so to stay on your UNLOCKED bootloader you need to find a tar with NO bootloader (there is a PB1 no bootloader stock tar)
If you had safestrap- all you have to do is flash the NK2 kernel and it will boot into safestrap- allowing for recovery of internal data and flashing of a new ROM.
If he's on any of the Firmwares below OD5, he can safely Odin back to NCG and start from scratch using Towelroot. All of our bootloaders are locked no matter which firmware version you're on. It's the versions OE1 and up that are more locked down from rooting
smokerbond said:
That is not totally bricked :victory:
You are just softbricked. First, did you have safestrap installed?
If you don't care about any of the internal data and just want the OS fixed, just put it in download mode (Power+Home+VolDown) then Vol Up to confirm, and get the .tar of the stock image. Flash it with Odin- bam done.
Be warned, because you were towelrooted this would ultimately flash the latest LOCKED bootloader- so to stay on your UNLOCKED bootloader you need to find a tar with NO bootloader (there is a PB1 no bootloader stock tar)
If you had safestrap- all you have to do is flash the NK2 kernel and it will boot into safestrap- allowing for recovery of internal data and flashing of a new ROM.
Click to expand...
Click to collapse
Many thanks, Smokerbond. I do wish I had waited for your reply, but, as usual, I was impatient (and somewhat concerned). I found part of what you knew elsewhere, downloaded from Sammobile, and flashed. Unfortunately, as you noted, that didn’t keep root. My question now is, can I start over? I flashed G900VVRU1BOA8-G900VVZW1BOA8 which, of course, is filled with bloatware. I have all my files I used originally, but no instructions and, as we say at my age, (77), I have slept since then.
You can Odin flash the PB1.tar with no bootloader, then use @jrkruse root method. That is the simplest way. You can also Odin back to NCG and use Towelroot, but it makes it a PITA with enabling advanced calling.
---------- Post added at 01:14 PM ---------- Previous post was at 01:13 PM ----------
Also, I'm not familiar with that SuperSU version. That is probably what caused the bootloop. I'm currently running SuperSU 2.71 on my S5 and it works great, but you can go with the latest stable version if you prefer.
Shouldn't be trying to flash SuperSU from 2014. Here's the latest version once you get everything up and running again.
Thanks for all the suggestions. I am now up and running, using Chainfire's SU 2.65. Since I was familiar with the path, I did go back to NCG and use towelroot, but since I have no need for the advanced calling (with which I was not familiar), I am happy with my setup.
Hello all,
Today I updated a custom ROM on my rooted Phone (android 7) . In the aroma installer i select no root. After a good restart i though i root my Phone true Odin. I was thinking it went all good till it was stuck on te Galaxy s7 edge black screen. I couldnt do nothing. After that i was thinking to flash to stock. Every time i try to flash true Odin it give me fail.
Please help me.
Best regards Sidi
Hi there, I have same issue, have s7 edge sm-G935F stuck at logo. I downloaded 2 different firmware from z3x box(shell) and if keep failing when using odin (latest) and also getting error when using Samsung tool.Also I can't get in the phone menu to check the baseband..can only get model from download model.any advice to this?
Same issue as well on my sm-g985v Verizon variant
Flashed an update to work out minor lagging bugs and soft bricked my S7. Can access bootloader and recovery. Beyond that, the phone gets there but with black screen and it is sputtering off and on. Tried reflashing stock firmware with odin, and its not taking. Running into a permission error while trying to write the image. Anyone here have any ideas?
sidi adam said:
Hello all,
Today I updated a custom ROM on my rooted Phone (android 7) . In the aroma installer i select no root. After a good restart i though i root my Phone true Odin. I was thinking it went all good till it was stuck on te Galaxy s7 edge black screen. I couldnt do nothing. After that i was thinking to flash to stock. Every time i try to flash true Odin it give me fail.
Please help me.
Best regards Sidi
Click to expand...
Click to collapse
Is this a 935F? Where did you download the orginal firmware from and what version of Odin u use?
When I root my phone I always use the steps from this thread.
http://forum.xda-developers.com/s7-e...0-0-0-t3334084
Have never run into issues.
Flash twrp trough Odin first, let the phone start
Boot into TWRP, format phone with the options you have to type YES, then install dm-verity force encryption disabler
Now restart TWRP
Then flash the Supersu file from the thread.
Now restart phone
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Feyaad said:
Hi there, I have same issue, have s7 edge sm-G935F stuck at logo. I downloaded 2 different firmware from z3x box(shell) and if keep failing when using odin (latest) and also getting error when using Samsung tool.Also I can't get in the phone menu to check the baseband..can only get model from download model.any advice to this?
Click to expand...
Click to collapse
Download orginal firmware fro sammobile, unpack and flash with Odin 3.12.3.
Download the firmware from your area, the one that comes with your phone.
Use the right regional code and everything when you download firmware.
Also, have you guys flashed the right bootloader and modem beforehand?
LyLu said:
Is this a 935F? Where did you download the orginal firmware from and what version of Odin u use?
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Download orginal firmware fro sammobile, unpack and flash with Odin 3.12.3.
Download the firmware from your area, the one that comes with your phone.
Use the right regional code and everything when you download firmware.
When I root my phone I always use the steps from this thread.
http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
Have never run into issues.
Flash twrp trough Odin first, let the phone start
Boot into TWRP, format phone with the options you have to type YES, then install dm-verity force encryption disabler
Now restart TWRP
Then flash the Supersu file from the thread.
Now restart phone
Click to expand...
Click to collapse
Hello,
Thanks for your message. I tried everything you said exept that i used odin 3.12.5
But still the black screen...
sidi adam said:
Hello,
Thanks for your message. I tried everything you said exept that i used odin 3.12.5
But still the black screen...
Click to expand...
Click to collapse
What rom you tried to flash?
Are you on the right bootloader and modem?
Well I have the Odin latest version already..but I can't know which is the correct baseband or county..only the model I know when it's in download mode..
sidi adam said:
Hello all,
Today I updated a custom ROM on my rooted Phone (android 7) . In the aroma installer i select no root. After a good restart i though i root my Phone true Odin. I was thinking it went all good till it was stuck on te Galaxy s7 edge black screen. I couldnt do nothing. After that i was thinking to flash to stock. Every time i try to flash true Odin it give me fail.
Please help me.
Best regards Sidi
Click to expand...
Click to collapse
So you flashed a beta firmware, the name of which you don't feel is necessary information.
OK. Shame I hate popcorn. How about INFORMATION instead?!
LyLu said:
Is this a 935F? Where did you download the orginal firmware from and what version of Odin u use?
When I root my phone I always use the steps from this thread.
http://forum.xda-developers.com/s7-e...0-0-0-t3334084
Have never run into issues.
Flash twrp trough Odin first, let the phone start
Boot into TWRP, format phone with the options you have to type YES, then install dm-verity force encryption disabler
Now restart TWRP
Then flash the Supersu file from the thread.
Now restart phone
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Download orginal firmware fro sammobile, unpack and flash with Odin 3.12.3.
Download the firmware from your area, the one that comes with your phone.
Use the right regional code and everything when you download firmware.
Also, have you guys flashed the right bootloader and modem beforehand?
Click to expand...
Click to collapse
It was my understanding it was already in the package. Questioning that one now. Where do i look for that? And thank you for responding back. Downloading your first suggestions as i type this...
I have downloaded two non branded firmware for the Netherlands from samdroid. I had unpacked the zip and flashed the files. For the csc selection I put the one named home csc
Moodruid said:
It was my understanding it was already in the package. Questioning that one now. Where do i look for that? And thank you for responding back. Downloading your first suggestions as i type this...
Click to expand...
Click to collapse
When downloading original firmware there should be 4 files when unzip.
1 for each of the options in Odin, without the last one named home.
Some of the custom roms comes with bootloader and modem, but NOT ALL.
Most times you have to flash the right bootloader and modem in Odin beforehand to get the phone to boot.
Im unsure of what has happened because I have never run into issues myself.
If you can not get the phone to boot with firmware from Sammobile and Odin flash I am out of options.
If I do experience a problem like this I would:
-install bootloader and modem according to the custom rom used. Try and flash these with odin more than ones, if not working.
-if no recovery, try flash recovery again
-try flash another custom rom then another custom rom
-return to stock firmware downloaded trough Sammobile
If none of these options work im out of things to do, sorry
The times I have experienced phone stuck on Samsung logo, it has been because of bootloader and/or modem.
Flashing the right ones have always fixed the problem.
That said, I have never experienced problems with returning to stock firmware trough Odin, maybe one time.
And this time my firmware download was corrupted.
---------- Post added at 06:13 AM ---------- Previous post was at 06:00 AM ----------
sidi adam said:
I have downloaded two non branded firmware for the Netherlands from samdroid. I had unpacked the zip and flashed the files. For the csc selection I put the one named home csc
Click to expand...
Click to collapse
This is wrong, you should use the file named only CSC.
Home_CSC, is to keep your setup on phone as is.
I also remember that you have to remove the meta data directory, and then repack firmware or the install will stop.
And this is also NOT a good option if you use another firmware than the original on phone.
Installing firmware with Odin, always use BL, AP, CP and CSC.
Try this and forget about the Home_CSC.
I don't have anymore info, sorry
Thank you very much. I will try it. I will let you know.
Gentlemen, my appreciations and thanks. Was able to finally get the stock firmware to grab. After more time disecting the problem i learned about and was able to uncover the maintenance boot screen. There it had the option to do usb debug . Once i hit that, next flash finished fully. It must of reser in the dev options after the initial root. Damn, i was sweating balls for a bit thinking i must of hard bricked it somehow. I will take it throufh the toot process later today glitch free i imagine. Thanks again for assisting,
Moodruid said:
Gentlemen, my appreciations and thanks. Was able to finally get the stock firmware to grab. After more time disecting the problem i learned about and was able to uncover the maintenance boot screen. There it had the option to do usb debug . Once i hit that, next flash finished fully. It must of reser in the dev options after the initial root. Damn, i was sweating balls for a bit thinking i must of hard bricked it somehow. I will take it throufh the toot process later today glitch free i imagine. Thanks again for assisting,
Click to expand...
Click to collapse
Usb debugging should always be turned ON when flashing..........!
Tis is like common knowledge in here.
Anyway glad things work
LyLu said:
Usb debugging should always be turned ON when flashing..........!
Tis is like common knowledge in here.
Anyway glad things work
Click to expand...
Click to collapse
How will you get to turn on USB debugging when the phone can only booth into download model?
Feyaad said:
How will you get to turn on USB debugging when the phone can only booth into download model?
Click to expand...
Click to collapse
Buy pressing and holding power and volume down key, until you get to the screen.
Same procedure as download mode, but without the big button
LyLu said:
Buy pressing and holding power and volume down key, until you get to the screen.
Same procedure as download mode, but without the big button
Click to expand...
Click to collapse
OK great..will try it..thank you
luly said:
Is this a 935F? Where did you download the orginal firmware from and what version of Odin u use?
When I root my phone I always use the steps from this thread.
http://forum.xda-developers.com/s7-e...0-0-0-t3334084
Have never run into issues.
Flash twrp trough Odin first, let the phone start
Boot into TWRP, format phone with the options you have to type YES, then install dm-verity force encryption disabler
Now restart TWRP
Then flash the Supersu file from the thread.
Now restart phone
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Download orginal firmware fro sammobile, unpack and flash with Odin 3.12.3.
Download the firmware from your area, the one that comes with your phone.
Use the right regional code and everything when you download firmware.
Also, have you guys flashed the right bootloader and modem beforehand?
Click to expand...
Click to collapse
Even this thread is old:
Thank you so much, bricked my phone unknowingly flashing custom recovery using a defektive usb port struggling to get it working again. This worked like a charm.
Don´t understand why the orthers did struggle with that method.
Please help
Im stuck. I wanted to flash with odin when my house blow a fuse..... im "so"lucky...
After that my phone boots showing the "samsung s5 powered..." for a fraction of a second and then download mode. It does the same thing regardless what i do with the buttons. eg not able to reach recovery.
So i tried to flash twrp with odin= stuck at the recovery.img
Tried with stock rom =stuck at aboot.
Tried different versions of files and odin.
It seems that regardless what file i try to flash odin stops at the firs file.
Only thing i managed to do is flash a pit file.
Is my phone bricked. Thanks in advance
pilboff said:
Please help
Im stuck. I wanted to flash with odin when my house blow a fuse..... im "so"lucky...
After that my phone boots showing the "samsung s5 powered..." for a fraction of a second and then download mode. It does the same thing regardless what i do with the buttons. eg not able to reach recovery.
So i tried to flash twrp with odin= stuck at the recovery.img
Tried with stock rom =stuck at aboot.
Tried different versions of files and odin.
It seems that regardless what file i try to flash odin stops at the firs file.
Only thing i managed to flash is pit file.
Is my phone bricked. Thanks in advance
Click to expand...
Click to collapse
I have the same problem with the download mode, but i couldn't do anything because my charging port is broken
sorry to hear that...
i hope there is a "guru" here who is able to help us...
pilboff said:
sorry to hear that...
i hope there is a "guru" here who is able to help us...
Click to expand...
Click to collapse
i hope it too
What were you flashing with Odin when your fuse blew? I need much greater detail. We're you stock flashing custom? Other way around? Flashing kernel? Bootloader? Going from lollipop to marshmallow or nougat? I can't really try to piece it together unless I'm able to visualize what's going on.
---------- Post added at 06:59 AM ---------- Previous post was at 06:48 AM ----------
Also in my experience if odin flashes a rom to your device and your device freezes at boot you flashed the wrong stock ROM. Get it from sammobile. You can't just flash any rom for your device. It needs to match. Carrier and firmware. If you were say on 6.0 you can't just go flash 4.4 or 5.0. it might not boot because 6.0 updated the bootloader. Mm and nougat use the same bootloader. You can however upgrade to 6.0 from an earlier version. I've got a feeling you were never installing the rom your phone was looking for to begin with. You probably wouldn't have been able to boot even if the fuse didn't blow. I say this because if it stopped mid way during a flash it would simply corrupt the install and another flash would fix the issue. If I wipe the rom from my s5 or it fails to boot my primary rom it boots right into recovery.
---------- Post added at 07:02 AM ---------- Previous post was at 06:59 AM ----------
Arabix.Sword said:
I have the same problem with the download mode, but i couldn't do anything because my charging port is broken
Click to expand...
Click to collapse
You will absolutely need your usb port if you can't get into recovery.
godkingofcanada said:
You will absolutely need your usb port if you can't get into recovery.
Click to expand...
Click to collapse
I know:good:, ill give it to a shop to replace the port
We'll, try to get in the Download Mode using the POWER+HOME+DOWN VOL. and not by the stuck Download Mode, i know you can, then try to flash a rom, preferably exact same or newer Android version.