Hi XDA friends,
Have a note 7 on PK1 with 60% warning on screen.
I'm hoping to get a clear answer on:
1. Can I downgrade to stock release and charge to 100% no warning messages?
2. If I cannot downgrade, can I remove the 60% charge limit and messages?
3. Is root possible as I would think using root explorer or root uninstaller would rid the updates?
4. Would a custom rom flash be preferred that eliminates the forced updates?
I have searched the forums and there's no clear answer on downgrading from PK1 60% to stock and charge to 100% then killing the forced updates.
Thank you all!
And I know this is a Herculean effort to keep the phone from updates and working as a stock phone, however it's highly coveted!
Hey man it is possible. Sorry I can't give more info at this point but it involves a new break through with a temporary root method with the Dirty Cow exploit I found on Alliance X forums (Untethered Note 7 root it's called), a lot of downloads that may not be necessary for average users, and whole lot of ADB (but doable). It's not full root as I am aware but it's enough to reset the battery to 100% and remove the recall messages as if it were to never get to that point. I would like to make a tutorial for you but don't hold your breath as I don't have the time. A lot of info was gathered from bits and pieces via XDA and Alliance X forums. I'll try to share when I can. Oh and I'm currently on P14 with a v2 Note 7.
Hey,
I own a Tmobile Note 7 and unfortunately my phone is now on the kill stage where i cannot charge my phone due to Tmobile's latest update. Is there nay way to fix this?
its blocked ,
mine blocked too
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1205)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> emmc_appsboot.mbn
<ID:0/007> lksecapp.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
all i got ! ..
I have a 0% t mobile but can get battery to 100%.
Is there a way to downgrade to 30% or 60% update then install a kernel or custom Rom to enable 100% charge. I can charge battery on note fe then reinstall battery in note7. I can get dead note7 into download mode. Is it possible to fix this variant? I see other variants being resurrected.
Thank you. The note 7 is a V 1. With kill update. I can enable USB debugging and OEM unlock and get device into download mode. It is a t mobile variant. Thanks for reading my post. Any help is appreciated.
Karcus said:
Hey man it is possible. Sorry I can't give more info at this point but it involves a new break through with a temporary root method with the Dirty Cow exploit I found on Alliance X forums (Untethered Note 7 root it's called), a lot of downloads that may not be necessary for average users, and whole lot of ADB (but doable). It's not full root as I am aware but it's enough to reset the battery to 100% and remove the recall messages as if it were to never get to that point. I would like to make a tutorial for you but don't hold your breath as I don't have the time. A lot of info was gathered from bits and pieces via XDA and Alliance X forums. I'll try to share when I can. Oh and I'm currently on P14 with a v2 Note 7.
Click to expand...
Click to collapse
Any help on this would be appreciated. Thanks
Asking a question
Mine's SM-N930T now in MMB29M.N930TUVU3TPL1 ,has a green battery icon and able to charge to 100% ,but unable to receive any cellular signal ,is there a possible way to downgrade to N930TUVU1APGC?
Sayuri_zhang said:
Asking a question
Mine's SM-N930T now in MMB29M.N930TUVU3TPL1 ,has a green battery icon and able to charge to 100% ,but unable to receive any cellular signal ,is there a possible way to downgrade to N930TUVU1APGC?
Click to expand...
Click to collapse
I have the same phone as yours... N930T with software version N930TUVU3TPL1, has a green battery icon and could charge to 100%. The only difference is that everything with my phone works just fine (even including water resistance)... Since there is basically 0 thing that I can do to the phone, I want to downgrade it as well but I don't know how...
If you figured out how to downgrade that, let me know by replying to this thread.
Thank you (in advance).
Related
Hello,
Now I am sure this forum gets it's fair share people completely oblivious to rooting and such. The issue is I have bought a Galaxy note and have had it for 4 wonderful months so far. It's unlocked, i.e not bound to a network.
2 months in I tried rooting my phone, and well it was very clear and simple (through the youtube video, linking to here). A month later I also got Kies to finally work and updated my phone kernel, unfortunately I had no idea that with that the root disappears. I went to try and get my apps to work in the university which have their own proxy setting to access the net (which I have finally gotten used to), the apps however do not work and thus the need for me to root my phone.
The query (I apologize for the long winded post):
I currently have the kernel version
2.6.35.7-N7000XXLC1-CL1003701
Ok so I am aware that I will be looking for kernels portraying the LC1 version when rooting, however it seems that there is no easy way of rooting (as the youtube video I watched) for my current specific kernel.
I just would like someone if possible to guide me exactly with what to do, do I really need to root my phone or is there a way to get apps to go through proxy without rooting again?
Also, how would I root my phone this time? What files would I be loooking for and how simple >.> are they.
Thank you again for your time,
I would appreciate any help, but I beg of you please keep it as simple as possible xD
You have updated your note with Kies, so you lost Root. Kies/OTa update erases root.
Anyway, now you have option is to downgrade
You can find any older directly rootable ROM from here N Root as you did it earlier.
After rooting, dont use kies/OTA to update.
just use same thread (as shown above) to find latest ROM, N update using CWM OR Moble Odin Pro.
wheres cwm?
Hey doc. I followed all your instructions and all is well but i was just wondering how do i get cwm back? I have updated the kernal and the phone is still rooted but no cwn (mobile odin latest update states that they have removed the inject cwm) so i was wondering if theres anyway to get it back? Thanks in advance
Flash cf root kernel with pc odin
Sent from my GT-N7000 using xda premium
Re cwm
Ok so i have used pc odin before but how do i flash the cf kernal? I thought the lc1 update could not be rooted directly.
BillyGuitar said:
Ok so i have used pc odin before but how do i flash the cf kernal? I thought the lc1 update could not be rooted directly.
Click to expand...
Click to collapse
Flash a rootable rom say kk9 through PC Odin once done flash the cwm root for it (kk9) from chainfires post then flash that via Odin the same way as you would a rom
Re cwm
Awsome dude, took me 2 mins. Thank you very much
BillyGuitar said:
Awsome dude, took me 2 mins. Thank you very much
Click to expand...
Click to collapse
No problem mate glad it worked
So how long does the flashing take?
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKK9_N7000OXAKK9_N7000XXKK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> factoryfs.img
Has been stuck on this 800 mb file for quite some time now, the Samsung galaxy note has the Android robot and Downloading "Do not turn off target" display atm. Just curious how long it often takes, getting kind of worried >.> Looking at ~1hour or so now
Recently I used ODIN 3.0.7 to try and root my Samsung Galaxy S3 (Telia) 4G with a so-called "CF-Root-SGS3-v6.4".
It is the 16 GB, 2 GB RAM 4G/LTE version, and it was running at Android 4.1.2 when I tried to do the root.
The phone booted up fine and ODIN claimed it was a success, I immediately noticed that the phone had stopped recognizing my SIM card, and the Root Checker also stated that something was wrong and it wasn't rooted. so I download a stock ROM and try to install that, however when I choose the SD card to try and install it, it says no files are found.I had made it to the CWM Recovery tool on the phone, and I could start the phone that way ("Reboot Phone Now", but it still didn't recognize my stuff, so I tried following the stock ROM instructions I was given, and I wiped all data, cache and stuff after backing it up on my PC in the CWM recovery tool.
Now, at this point, the phone is stuck at "Downloading - Do not turn off target!". When I try turning it off, the screen goes black for 2 seconds, and then the screen appears again. If I am quick, I can get into the "ODIN" mode, where I can once again try and root it. It fails again, but now I get to the CWM Recovery Tool again, but no files are found at all, and if I reboot the phone, it just goes back to the Downloading screen (I left it on overnight and it stayed on that screen, by the way. I doubt it is ACTUALLY downloading anything).
I do not know the Kernel or ROM version. The phone was bought in the start of February, though, so I could imagine it's rather new.
What do I do now? I just wish to get my phone back to normal Android, normal everything even if it means a factory reset.
You need to goto the NV backup sticky thread in the dev section that I put together, look near the bottom.
Download the param binary and flash with odin to revive your device.
Sent from my GT-I9305 using Tapatalk 2
Hello, I followed the guide and flashed the phone with the param with ODIN, however, the phone is still stuck on its "Downloading - Do Not Turn Off Target!" screen (though it is not showing the ODIN mode at the corner anymore.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Param_Bin_I9305.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> param.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... *0*
<OSM> All threads completed. (succeed 1 / failed 0)
The box is green and says "PASS!", but the phone is unresponsive.
Did I do something wrong?
Right now you need to read then run this via odin from you PC...
http://forum.xda-developers.com/showthread.php?t=1942150
You probably corrupted your efs partition by flashing a CF Root not intended for your phone. The CF Root is for SGS3 not I9305 LTE.
Sent from my GT-I9305 using XDA Premium HD app
Raistlin1158 said:
Right now you need to read then run this via odin from you PC...
http://forum.xda-developers.com/showthread.php?t=1942150
Click to expand...
Click to collapse
This did it, thank you!
Time to reinstall a lot of apps, and be more careful with the root I pick.. ;_;
You already have root with this rom
Hello again, sorry for sort of necroing.
So I got it running again, there is one nasty problem, though - The phone won't recognize my SIM card, meaning that it simply doesn't register that there is one.
I'd guess the phone warranty is void at this point, so what do I do? Is there any DIY fix?
Azortharion said:
Hello again, sorry for sort of necroing.
So I got it running again, there is one nasty problem, though - The phone won't recognize my SIM card, meaning that it simply doesn't register that there is one.
I'd guess the phone warranty is void at this point, so what do I do? Is there any DIY fix?
Click to expand...
Click to collapse
Did you check your IMEI??? After messing with your phone you could simply lost it.
Sent from my GT-I9305 using xda app-developers app
How do you check IMEAI
DjeMBeY said:
Did you check your IMEI??? After messing with your phone you could simply lost it.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
hard bricked galaxy sIII I9305
guys i got a much worse situation, my device is a galaxy I9305, and i turned my phone off during the flash of a firmware where it was saying "FAIL" for a long time. I'm desperate at the moment and i'm not finding out any way how to debrick it, any help would be greately appreciated! My device is stuck on "Downloading... Do not turn off target!!" it's only this text in the center, with nothing more
UPDATE: Up until yesterday, my phone was stuck on the Samsung logo. I used Odin to flash the original Carphone Warehouse Gingerbread Rom. The phone then became stuck in a loop of unresponsive processes and wouldn't boot up. I decided that this was due to the Google Apps on the phone being a newer version than the O/S (I have not factory reset). Kies would not connect to the device in this state, so i used Odin again to flash the stock UK Jellybean Vodafone Rom. My phone now boots, and most settings/apps appear to have been kept. However, some system apps, i.e. messaging, force close. I think this may be because the APN's etc are now on Voda settings. Unfortunately, 'settings' is also a process which force closes!
Basically, at the minute, I'm looking for a way to a) stop the force closes to manually change settings, or b) flash the UK unlocked JB Rom - I can't find this Rom anywhere.
Hi all. Hope somebody can help me.
I have an unlocked Galaxy Note, which has always run stock, up-to-date, Samsung firmware. Yesterday, I was attempting to use the satnav, and had the phone plugged in via car charger. The battery was low, and the satnav wouldn't connect to GPS. In the end, it became unresponsive, and I reset it. Now, the phone will only boot as far as the Samsung logo. Additionally, when it is charging, it doesn't show the bar climbing the battery - only the status (currently over half full).
I can get into recovery and download modes, but I'm really wanting to avoid a full reset/wipe, as I have some texts which have great sentimental value (yes, I know, I should have backed these up).
Other threads which are similar seem to point to Odin and an earlier stock ROM - I've downloaded the original ROM my phone would have had and Odin, but want to know 1) is this the best way to go and 2) what do I do next?
Thanks.
Flash the stock ROM again with ODIN.
fact fbarro
Varad297 said:
Flash the stock ROM again with ODIN.
Click to expand...
Click to collapse
Have now tried this. Odin reports a fail...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKKA_N7000CPWKK3_N7000XXKK5_HOME.tar.md5 is valid.
<OSM> N7000XXKKA_N7000CPWKK3_N7000XXKK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> zImage
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response form LOKE
<ID:0/004> boot.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004>
<ID:0/004> Receive Response form LOKE
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
...and now, when I have rebooted, I get a yellow triangle with 'Firmware upgrade encountered an issue...'
Have retried Odin and received a pass.
Now, the phone is trying to run setup wizard, but is crashing/force closing a number of processes. Might this be because the stock Rom is too old?
fivegoldstars said:
Have retried Odin and received a pass.
Now, the phone is trying to run setup wizard, but is crashing/force closing a number of processes. Might this be because the stock Rom is too old?
Click to expand...
Click to collapse
Further update. I have reflashed again, this time with the JB Vodafone Rom. Previously I was on the unlocked UK Rom, but I can't find this anywhere. I'm now able to get into the phone, and the majority of things work, but some functionality is missing. I've tried to force an OTA update, but now the phone says its running the most up to date software. Any ideas how I can go back to the proper Rom for this phone?
This is the proper ROM mate, may not be the one you got with your phone but still the stock ROM. Or else you can search for the ROM you need on sammobile.com
Do hit thanks if this helps!
Varad297 said:
This is the proper ROM mate, may not be the one you got with your phone but still the stock ROM. Or else you can search for the ROM you need on sammobile.com
Do hit thanks if this helps!
Click to expand...
Click to collapse
Well, as per update in O/P, I'm back in the majority of things, but certain system processes force close when I open. The phone registers on the network, and will make voice calls, but I can't access messaging (force closes) or APN's (force closes). So cannot text or connect to mobile internet. Have tried wiping cache, but I'm now running out of ideas.
Did you check sammobile.com? Or dr.ketan's thread in the original Android Development forum? Try flashing some other stock after a full wipe..
I used the only UK JB Rom in Dr Ketans thread. Have not checked sammobile yet - need to do this later.
I'm not wanting to do a full wipe until I can access and backup my texts - trying to install without wiping first.
fivegoldstars said:
I used the only UK JB Rom in Dr Ketans thread. Have not checked sammobile yet - need to do this later.
I'm not wanting to do a full wipe until I can access and backup my texts - trying to install without wiping first.
Click to expand...
Click to collapse
Good news/bad news.
Firstly, the original problem of my phone stuck on the Samsung logo is fixed. My full sequence of events was 1) flash stock Gingerbread rom using Odin. This gave me a phone which would not boot due to Google processes force closing. 2) flash stock JB rom from Dr Ketans thread. This gave me a phone which booted, but could not access APNs/messaging, although all other settings/apps/files were still intact 3) flash stock JB rom from Sammobile (CPW). This gave the same problem. 4) Perform full factory reset and reflash JB CPW rom. Phone now has full functionality, but has lost all files, messages, apps etc.
Thanks for everyone's input - thread can be closed.
A full wipe mostly does it. And always backup the important stuff. If you're gonna root, Titanium backup is the best. And mate do click the 'Thanks' button if i helped!
Don't forget. do a backup of your current rom! if ever there might be a problem at least you can still jump back to it!!!
TL;DR DON'T try to install a custom recovery yet. As of 5/12/15, the bootloader prevents you from doing that. At the moment, you can only root, which you can do through Ping Pong Root (google it). And if for some reason you goofed up and installed a custom recovery, go to AT&T and just say the bare minimum, that you "tried to update your phone" and it keeps telling you "this error message." If they prod more, you can say you "updated the firmware," but obviously withhold the words "flash," "recovery," etc.
So I greatly REGRET that I installed a custom recovery. I'd appreciate any help. I'm bricked in the "System software not authorized by AT&T has been found on your phone." Here's what I did leading up to it:
1. Installed Ping Pong Root party_beta5.7z. Unzipped, installed, rooted.
2. Root Checker verified root!
3. Determined my my phone is: G920AUCU1AOCE.
4. Downloaded TWRP 2.8.6.2 through Flashify for Samsung Galaxy S6 (zeroflte).
5. Flashed it through Flashify
6. Bricked (light blue screen with text) and bootloop.
Help!
EDIT: Steps I've taken so far:
1. Download Odin Tar files from http://forum.xda-developers.com/att-...g920a-t3103835
2. Connected phone to PC in download mode after installing USB drivers and ODIN 3.10.6
3. Put all 4 tar files into their corresponding spots.
EDIT2: No luck. Tried multiple ports, multiple computers, and used the official cable. Also Ran as administrator. After making sure my device is recognized as COM3 (blue box), and the tar files are plugged in, I keep getting the below error:
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT3: Played dumb, took it to at&t store with a tech support center, and they re-flashed a clean install for me. Whew.
I don't think u can use custom recoveries yet buddy..
Yeah, I goofed bigtime. I'm really regretting it.
It's telling me this:
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Let it be known root does not equel unlocked bootloader. I'd of wait or am for something like safestra to make it's way over.
aznkenshin said:
I'd appreciate any help. I'm bricked in the "System software not authorized by AT&T has been found on your phone." Here's what I did leading up to it:
1. Installed Ping Pong Root party_beta5.7z. Unzipped, installed, rooted.
2. Root Checker verified root!
3. Determined my my phone is: G920AUCU1AOCE.
4. Downloaded TWRP 2.8.6.2 through Flashify for Samsung Galaxy S6 (zeroflte).
5. Flashed it through Flashify
6. Bricked (light blue screen with text) and bootloop.
Help!
EDIT: Steps I've taken so far:
1. Download Odin Tar files from http://forum.xda-developers.com/att-...g920a-t3103835
2. Connected phone to PC in download mode after installing USB drivers and ODIN 3.10.6
3. Put Firmware into AP.
Praying this will work...
EDIT2: No luck. It tells me "Can't open the serial(COM) port." I'm thinking it's the drivers fault? Looking into it...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2711451
download odin 3.10.6 and just use all the tar files....MINE IS FINALLY ALIVE
plaxy+ said:
Let it be known root does not equel unlocked bootloader. I'd of wait or am for something like safestra to make it's way over.
Click to expand...
Click to collapse
So in the meantime, what should I do to at least have an operable phone? (
skylinegtr116 said:
http://forum.xda-developers.com/showthread.php?t=2711451
download odin 3.10.6 and just use all the tar files....MINE IS FINALLY ALIVE
Click to expand...
Click to collapse
OH! I was only using the "AP_****" files. I should plug in the CSC, CP, and BL too???????
aznkenshin said:
oh! I was only using the "ap_****" files. I should plug in the csc, cp, and bl too???????
Click to expand...
Click to collapse
yes all the files
skylinegtr116 said:
yes all the files
Click to expand...
Click to collapse
No luck
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_G920AUCU1AOCE_CL4351102_QB4488924_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_G920AUCU1AOCE_CL4351102_QB4488924_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_G920AUCU1AOCE_CL4351102_QB4488924_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_G920AATT1AOCE_CL4351102_QB4488924_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The link above is broken, where can I get these files?
PS: Why do they provide a custom recovery if it straight "bricks" your phone? How is that even considered a working release and why don't they (TWRP) post a damn warning about it?
plaxy+ said:
Let it be known root does not equel unlocked bootloader.
Click to expand...
Click to collapse
Just joined last month, this was their third post currently, and knew this :good:
OP joined late 2011 and thought that just by gaining root, we could install custom recoveries on a still locked bootloader...........
LEARN FROM THIS, people! Don't want to go through this? Follow instructions!
That being said, from what I know of soft bricks, you are doing the right steps to fix it, I just don't have any experience with them to be able to tell you what you're doing wrong. People who have unlocked bootloader phones and installed custom recoveries, tripping KNOX, were able to flash back to stock and get KNOX back to 0x0, but again, they have the unlocked bootloader to be able to do that.... don't know what else to tell you other than to bring it to an ATT service center, play dumb, and see if they'll swap you into a new one
hayateyoshida said:
The link above is broken, where can I get these files?
PS: Why do they provide a custom recovery if it straight "bricks" your phone? How is that even considered a working release and why don't they (TWRP) post a damn warning about it?
Click to expand...
Click to collapse
They do post a warning about it - they post what phones this IS for, and our phone is NOT listed! People, please learn how to read if you're going to screw around with your phones! You can't just say "I have an S6 Edge" and think they're all the same! TWRP clearly states the following two devices have recoveries available:
Samsung Galaxy S6 (zeroflte)
Samsung Galaxy S6 (Sprint) (zerofltespr)
Do you see zeroflteatt on that list? Do you think zeroflte = zeroflteatt? If you don't know what model phone you have and flash away, you're gonna have a bad day......
aznkenshin said:
So I greatly REGRET that I installed a custom recovery. I'd appreciate any help. I'm bricked in the "System software not authorized by AT&T has been found on your phone." Here's what I did leading up to it:
1. Installed Ping Pong Root party_beta5.7z. Unzipped, installed, rooted.
2. Root Checker verified root!
)
Click to expand...
Click to collapse
what??
ATT galaxy s6 has root ?
Have you tried recovery through smart switch
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
netnerd said:
what??
ATT galaxy s6 has root ?
Click to expand...
Click to collapse
yep. pingpong root
LeKtRiCzzz said:
Have you tried recovery through smart switch
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Click to expand...
Click to collapse
Yes, after going to update and software emergency setup, I plugged in Model and Serial number on the sticker of my phone, and it auto-closes.
Sent from my GT-I9505G using XDA Free mobile app
Agree 500%
KryptosXLayer2 said:
Just joined last month, this was their third post currently, and knew this :good:
OP joined late 2011 and thought that just by gaining root, we could install custom recoveries on a still locked bootloader...........
LEARN FROM THIS, people! Don't want to go through this? Follow instructions!
That being said, from what I know of soft bricks, you are doing the right steps to fix it, I just don't have any experience with them to be able to tell you what you're doing wrong. People who have unlocked bootloader phones and installed custom recoveries, tripping KNOX, were able to flash back to stock and get KNOX back to 0x0, but again, they have the unlocked bootloader to be able to do that.... don't know what else to tell you other than to bring it to an ATT service center, play dumb, and see if they'll swap you into a new one
They do post a warning about it - they post what phones this IS for, and our phone is NOT listed! People, please learn how to read if you're going to screw around with your phones! You can't just say "I have an S6 Edge" and think they're all the same! TWRP clearly states the following two devices have recoveries available:
Samsung Galaxy S6 (zeroflte)
Samsung Galaxy S6 (Sprint) (zerofltespr)
Do you see zeroflteatt on that list? Do you think zeroflte = zeroflteatt? If you don't know what model phone you have and flash away, you're gonna have a bad day......
Click to expand...
Click to collapse
---------- Post added at 11:25 AM ---------- Previous post was at 11:24 AM ----------
Smart Switch does NOT work in the AT&T version of the S6.
LeKtRiCzzz said:
Have you tried recovery through smart switch
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Click to expand...
Click to collapse
aznkenshin said:
EDIT3: Played dumb, took it to at&t store with a tech support center, and they re-flashed a clean install for me. Whew.
Click to expand...
Click to collapse
Great, I have just booked an appointment. But buddy, is it possible for you to upload Odin Tar?
Thanks!
nagnrik said:
Great, I have just booked an appointment. But buddy, is it possible for you to upload Odin Tar?
Thanks!
Click to expand...
Click to collapse
Read my OP
aznkenshin said:
Read my OP
Click to expand...
Click to collapse
ATT re-flashed the firmware, it is fine now. Thanks!
Hi folks,
I friend of mine have this phone that is stuck in Odin mode. The problem is that none of the "press and hold keys" commands work and the phone just reboots into Odin every time. She has "tons" of Pictures of her first born Child on the device, without any cloud backup! :crying:
Any suggestions what to try next?
What i have done so far:
Trying all the "press and hold keys"
Letting the battery drain out and the hook up the Power to it... When connecting Power the screen turns White for 15-20 minutes and then if i reboot it, it goes back to Odin/download mode...
Is it possible that opening the phone and removing the battery could work?
Jeppe_77 said:
Hi folks,
I friend of mine have this phone that is stuck in Odin mode. The problem is that none of the "press and hold keys" commands work and the phone just reboots into Odin every time. She has "tons" of Pictures of her first born Child on the device, without any cloud backup! :crying:
Any suggestions what to try next?
What i have done so far:
Trying all the "press and hold keys"
Letting the battery drain out and the hook up the Power to it... When connecting Power the screen turns White for 15-20 minutes and then if i reboot it, it goes back to Odin/download mode...
Is it possible that opening the phone and removing the battery could work?
Click to expand...
Click to collapse
I am no expert, just going to suggest what I would try, hopefully someone may know what to do exactly.
You could try downloading stock filmware from Sammobile or updato (making sure to at least flash the same filmware build or higher, or Odin won't flash it) if you use the "home csc" csc file, it should not wipe the data on the phone, and what I hope may fix the phone not booting.
First of all you should have mentioned the model no. Second, you can try flashing the stock firmware from sammobile. Now, the tricky part is, if prior to this soft brick the phone was on a custom rom or had been rooted, then flashing the firmware alone won't bring the device back to life, a factory reset will be needed after flashing stock firmware, which doesnt seems like a favorable option considering that the data on device is important. There can be other ways to fix this without losing the data but for that illl need to know the device details.
Oh and btw, opening the device and messing with the battery won't help at all. Don't do that.
Sent from my SM-N950F using Tapatalk
Get a pit file and flash it though oden may work or not.......
yashthemw said:
First of all you should have mentioned the model no. Second, you can try flashing the stock firmware from sammobile. Now, the tricky part is, if prior to this soft brick the phone was on a custom rom or had been rooted, then flashing the firmware alone won't bring the device back to life, a factory reset will be needed after flashing stock firmware, which doesnt seems like a favorable option considering that the data on device is important. There can be other ways to fix this without losing the data but for that illl need to know the device details.
Oh and btw, opening the device and messing with the battery won't help at all. Don't do that.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
Its an Galaxy Note 8 (SM-N950F)
The only thing i can see in the display is
https:// imgshare.io/image/odin-2.U7KCu
We dont know what firmware was beeing used Before this, it´s not custom or rooted tho. I assume its the latest official tho
I grabbed the latest from Sammobile, N950FXXU7DSJ1_N950FCKH7DSJ1_HTS
I could try the above suggestions but what about trying to flash the BL? Could it not be the BL that is cuppupt somehow?
I did try and flash the BL now but Odin software says:
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 7 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So it seems the partitions are gone, @stinka318. Next, where do i find PIT-files?
Found PIT file but it failed.
Also tried CSC flash but it fails (looks like Odin might not cennect to the device (ID:COM 0: [COM4])
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 179 M
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Driver related? i have the Samsung USB drivers installed….
https://zfirmware.com/download-samsung-galaxy-note-8-pit-file/
Seems like it's a kernel problem, or maybe the phone IMEI reported stolen?
Have you tried installing custom binaries? TWRP maybe?
Or messing with OEM unlock found in Developer Options?
Most of the for solving such problem, you have to flash the exact same firmware found on phone before the problem.
Try rooting using odin and then twrp and thenflashing a custom firmware..... That could help..... Just a thought.... Wipe everything except internal storage
https://mega.nz/#!Lk8RiKQR!FiH50HLQp1aijVkRARSPtBN6M6wFphShHsm7i6u23lw
Try flashing this via odin through AP.
Sent from my SM-N950F using Tapatalk