I was trying to unbrick my Xiaomi redmi note 8 pro, i have bricked it twice before and both times had to pay someone with an authorized Xiaomi Service Account, well this time i figured id wait for someone to come out with a method that works and id just use my samsung phone until then, well i waited and waited , and eventually i see the mega tread with the anti-brick in it. I was happy but for the few poor schmucks out there that never had a chance to flash that beautiful set of files i found a way out without paying someone to fix your screw ups.
Anyway I've tried lots of things to unbrick it, removing the battery , replacing the battery anything to get my back to fast boot. I've attempted flashing stock a countless amount of times in different ways and today i needed money very bad to pay some bills so i figured id try to fix it one last time so i could sell my note 10 +. I never had a chance to install the antibrick or whatever it is so theres no way this is just a fluke. I would like to give myself no credit anything here besides finding the files and making the guide. I feel bad because people are charging 35 bucks to practically login for you, and id really be a bad guy if i didnt post what ive found today. Well enough of the backstory here's a guide and ill link what worked.
I will provide the download for all the files you will need here.
https://drive.google.com/file/d/1RWwwUEZJnxmSzZMbFj5_zJaGQ1OJAFo5/view?usp=sharing
This guide is for the Global Version but its the same on all your just sub out the global ROM I've provided with my other files for the one in your region
After you have the zip file containing the files needed do as follows.
1. Uninstall your Current Mi-flash / MiFlashpro
2. Extract the .zip folder
3.Install The Miflashpro that i have in the zipped folder
4. Launch Miflashpro and login.
5.After your are logged in launch Spflash.
6. Inside SpFlashTool click the options tab in the top bar, second column from the left , then click options to open the settings , click general, then in the general tab you want to make sure check lib da match is unticked.
7. Now to begin flashing, Match up the .da file and the .auth file with the ones in the special sauce folder of the zip folder you downloaded , after thats its like installing stock "normally", if you are on global the scatter file is in globalromfiles/images directory.
8. When everything is setup simply click download.
9. As a few disclaimers I tried 6 or 7 times before it worked, i dont remember if i had spflashtool set to firmware upgrade or download download only, i will also state that it failed ounce or twice in both, i just held power and volume up until it cycled i head the ding on my pc letting me know windows picked it up and i had device manager open so i could see the mtk preloader and com ports, i was very surprised when it worked but it did. Anyway if this helped anyone please spread the work so people can know that there phones are not at the mercy of someone else's login. If you have any questions or issues please reply to the post ill respond as quick as i can. I'm not a developer just a modder if anything. I know basic python and how to screw up my phone stumbling upon a fix took me weeks or months even of on and off boredom spikes but this worked for me.
Anyway if this helped at all spread the work , and feel free to donate to me on cash app $KaozCash
hi
works with 64gb and 6gb ram version?
Rebellion747 said:
works with 64gb and 6gb ram version?
Click to expand...
Click to collapse
Yes That is what i originally did it on , the begonia model
It Doesn't Work For Me!
I Followed The Steps But Once Again Keeps Having Authorization Problem With The Account!
angrypandagr said:
It Doesn't Work For Me!
I Followed The Steps But Once Again Keeps Having Authorization Problem With The Account!
Click to expand...
Click to collapse
What code is it giving you, I don't have an authorized account and never flashed preloaded in fact I bricked it before that was released
sawclan22 said:
What code is it giving you, I don't have an authorized account and never flashed preloaded in fact I bricked it before that was released
Click to expand...
Click to collapse
This Error "BROM error status_brom_cmd_send_da_fail (0xC0060005)"
Which Is The Error For Not Authorized Account!
angrypandagr said:
This Error "BROM error status_brom_cmd_send_da_fail (0xC0060005)"
Which Is The Error For Not Authorized Account!
Click to expand...
Click to collapse
Okay like I said I revived that error three or 4 times before it worked give me a second to look at the files and see what I did, if I may ask you followed all the steps exactly, for example you clicked firmware upgrade instead of download
sawclan22 said:
Okay like I said I revived that error three or 4 times before it worked give me a second to look at the files and see what I did, if I may ask you followed all the steps exactly, for example you clicked firmware upgrade instead of download
Click to expand...
Click to collapse
I hate to ask but I need a test subject this worked for me but I may have left something out in my steps I could just brick my phone again a try it again myself, but it probably wouldn't be the same because the first the I did after making this thread flash the abtibrick lk and preloader, if you have some alternate way I can talk to you without using this thread I would love to fix it for you if I can, I want this guide the be revised to be a simple but highly detailed guide on how to fix this issue, it worked for me when I did it and I want to be able to help others. I just need someone else with a bricked device to test it too and for me to make sure that it's exactly what I did.
Thanks from my heart
bro your method if it works thank you very much, you saved me
Rebellion747 said:
bro your method if it works thank you very much, you saved me
Click to expand...
Click to collapse
Did you end up fixing your device? I figure if people report back success than more people will see it
Not working
I followed your instructions and did it several times but nothing seems to work for me
.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please find a alternate way or help me.
Thanks for the thread .
RanaDARK said:
I followed your instructions and did it several times but nothing seems to work for me
.
Please find a alternate way or help me.
Thanks for the thread .
Click to expand...
Click to collapse
Odd two people reported no success there's no way it was some kind of fluke for me , I don't believe in that kind of technical luck, is there anyway I could talk to you in real time I would lik to see first hand what's going on
It would be great if someone could confirm that this works, or would talk with OP and they would try to sort it out together. OP clearly wants to help others, and I am curious if there really is a solution to bricking this phone.
Lajbymester said:
It would be great if someone could confirm that this works, or would talk with OP and they would try to sort it out together. OP clearly wants to help others, and I am curious if there really is a solution to bricking this phone.
Click to expand...
Click to collapse
have you guys tried to use edl? if not, try doing edl mode
Please
Hello, could you tell me the contact privately if you need who unlocked it for you? Although this is being advanced, I need the mobile quickly and I would appreciate it very much.
not work for me, the sp tools keep show up notification to login mi account
my phone brick because I downgrade from android 10 to android 9
need help asap guys
sawclan22 said:
Odd two people reported no success there's no way it was some kind of fluke for me , I don't believe in that kind of technical luck, is there anyway I could talk to you in real time I would lik to see first hand what's going on
Click to expand...
Click to collapse
Thing is there is step where the flash tool gets authorisation if it fails to get it it throws a initiation error cmd_failed something like this. Also , this flash tool works normally without account if the phone is not hard bricked.
So I say maybe your phone wasn't hard bricked that's why tools you had worked.
can u please upload only flash tool files
I had already downloaded the rom ...im in my village (due to lockdown) with slow internet /nowifi so can u please upload flash tool only so I can test it
Not Work for Me :/
After trying the method with your files, the problem is still the same, the authentication window comes out every time and I can not flash my phone, for information (without Flash Tools) my phone displays only the LED light and when I connect it on my PC my computer recognizes it for a few seconds and this disconnection, maybe we don't have the same Hard Bricked of the phone
if you have any other information to suggest to me I will be grateful, thank you
(by google translate)
RanaDARK said:
Thing is there is step where the flash tool gets authorisation if it fails to get it it throws a initiation error cmd_failed something like this. Also , this flash tool works normally without account if the phone is not hard bricked.
So I say maybe your phone wasn't hard bricked that's why tools you had worked.
Click to expand...
Click to collapse
No it was definetey hatdbricked, stuck in a brick state after flashing an improper boot.IMG I was getting the error for authorization myself , then the window popped up with that specific set of tools and files , I then logged into my personal account and it worked, I tried flashing a good bunch of times, I removed my battery I couldn't get back to fastboot mode eventually I downloaded that mi flash tool from cynagenmods website , they called it a preauthorized flash tool or a flaehtool that wouldn't require authorization , well it didn't work I found the files in the special sauce folder in somones github , it would let me use them so I unticked something in the settings of sp flash tool , I can refer to the guide to see what it was after that I was super surprised to see it flash , maybe every other time I tried to flash it was a driver issue , if multiple people answer this the same let me know so I can close this thread, when u flash your hardbricked device does it even attempt to flash at all , do u see the loading bar move , usually it would fail for me on the first file it tried flash and I want to know the specific error it gave , this was my second time doing something idiotic and hardbricking this phone , if anyone can download teamveiwer and let me make sure all drivers are the same all files are exactly what I have etc , spflashtool has a good bit of different errors , I can't retest myself , not accurately atleast, the first thing I did after unbricking my phone was flashing the antibrick lk.IMG and bootloader
Related
Okay, here's the story:
1. my phone was running WM6 and I wanted to upgrade to WM6.1 with Kavanna
2. I was installing it, but then i got error 270 (even when i did the unlocking program)
3. So Now when i turn on my phone, it flashes this white screen "Searching for SD card" then it quickly shoots to the bootloader screen.
4. I've searched probably over 10 threads, reading through 3-24 pages of information and still, nothing works.
5. When i try installing the original ROM, i get this message "the contents of this file cannot be unpacked. The executable you are attempting to run has been corrupted. Please obtain another copy of the file, verify its integrity, and try again."
6. I tried getting the software from my CD that came with it, and it didn't work cause it needed Activesync to sync it
7. I tried the website, and i need the MEI-Address/code, but in order to get that, i need the phone to work, which isn't working right now.
8. IM A NOOB! I don't really know the vocabulary/slang that's being used here on the forums, but I'm trying to learn.
9. I would get a new phone, but i LOVE this phone, i don't want to give it up.
10. Any help?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Guy I Feel For You!
nv_lao93 said:
Okay, here's the story:
1. my phone was running WM6 and I wanted to upgrade to WM6.1 with Kavanna
2. I was installing it, but then i got error 270 (even when i did the unlocking program)
3. So Now when i turn on my phone, it flashes this white screen "Searching for SD card" then it quickly shoots to the bootloader screen.
4. I've searched probably over 10 threads, reading through 3-24 pages of information and still, nothing works.
5. When i try installing the original ROM, i get this message "the contents of this file cannot be unpacked. The executable you are attempting to run has been corrupted. Please obtain another copy of the file, verify its integrity, and try again."
6. I tried getting the software from my CD that came with it, and it didn't work cause it needed Activesync to sync it
7. I tried the website, and i need the MEI-Address/code, but in order to get that, i need the phone to work, which isn't working right now.
8. IM A NOOB! I don't really know the vocabulary/slang that's being used here on the forums, but I'm trying to learn.
9. I would get a new phone, but i LOVE this phone, i don't want to give it up.
10. Any help?
Click to expand...
Click to collapse
We all know about the 270 error, guy I would never ever be rude to you. All that error is telling you that you are installing the software incorrectly. Did you take out your SD Card out of your device, before installing the software? I know the software will tell you it will automatically unlock you device, but I want you to do a SDA unlock on your phone before installing the software, then it will work, just keep a eye on your device screen and your PC screen and follow on screens instructions....................!
Now with the boot loader color screen that's another story, just because you see the color screen does not mean anything is wrong with you device, as matter of fact it's good that you seee the color screen, it's still alive, don't panic. Connect you device to you PC via active sync, it will look like it is not connect to your PC via active sync but it is, just run a old 5.0 or 6.0 software on your device, before trying to install a 6.1 ROM back on your device, it will work, been there done that...............!
I did
I didn't have a memory card in the phone, and also i did the SDAUnlock before the software
Technology said:
We all know about the 270 error, guy I would never ever be rude to you. All that error is telling you that you are installing the software incorrectly. Did you take out your SD Card out of your device, before installing the software? I know the software will tell you it will automatically unlock you device, but I want you to do a SDA unlock on your phone before installing the software, then it will work, just keep a eye on your device screen and your PC screen and follow on screens instructions....................!
Now with the boot loader color screen that's another story, just because you see the color screen does not mean anything is wrong with you device, it's still alive don't panic.
Click to expand...
Click to collapse
Follow The Above Instructions
nv_lao93 said:
I didn't have a memory card in the phone, and also i did the SDAUnlock before the software
Click to expand...
Click to collapse
The only way to get out of the color boot loader screen mode is to run a old version 5.0 or 6.0 ROM back on your device before installing a 6.1 ROM back on your device, don't panic, you are still in the game..............!
Okay, so i went to the "Official ROMS" thread, and downloaded it, When i try installing the original ROM, i get this message "the contents of this file cannot be unpacked. The executable you are attempting to run has been corrupted. Please obtain another copy of the file, verify its integrity, and try again."
Technology said:
The only way to get out of the color boot loader screen mode is to run a old version 5.0 or 6.0 ROM back on your device before installing a 6.1 ROM back on your device, don't panic, you are still in the game..............!
Click to expand...
Click to collapse
Who Is Your Carrier
nv_lao93 said:
Okay, so i went to the "Official ROMS" thread, and downloaded it, When i try installing the original ROM, i get this message "the contents of this file cannot be unpacked. The executable you are attempting to run has been corrupted. Please obtain another copy of the file, verify its integrity, and try again."
Click to expand...
Click to collapse
Who is your carrier and what is the brand name of your mobile device...............?
It is....
T-Mobile/T-Mobile
Technology said:
Who is your carrier and what is the brand name of your mobile device...............?
Click to expand...
Click to collapse
You Must Remove 2 Locks
nv_lao93 said:
T-Mobile/T-Mobile
Click to expand...
Click to collapse
Do the SDA unlock first again, next do a Application unlock on your mobile device, now install the old software 5.0 or 6.0, do not install the 6.1 software yet......!
Aren't those the same thing? From the "6.0 to 6.1 with pics" thread?
Technology said:
Do the SDA unlock first again, next do a Application unlock on your mobile device, now install the old software 5.0 or 6.0, do not install the 6.1 software yet......!
Click to expand...
Click to collapse
Another Thing
Explain how and what you are doing step by step when opening the RUU file?
AFTER i got the bootloader screen (red/green/blue), i went and tried to install the original ROM, and it said "the contents of this file cannot be unpacked. The executable you are attempting to run has been corrupted. Please obtain another copy of the file, verify its integrity, and try again.". Basically it failed.
And btw, when i tried the SDAApplicationUnlock, it says my phone isnt connected, when it is.
Technology said:
Explain how and what you are doing step by step when opening the RUU file?
Click to expand...
Click to collapse
OK I See What You Are Saying
nv_lao93 said:
Aren't those the same thing? From the "6.0 to 6.1 with pics" thread?
Click to expand...
Click to collapse
No that is not true, I will send you the other unlock file, ok!
Thanks for your help so far! =)
SDAapplication didn't work btw.
Technology said:
No that is not true, I will send you the other unlock file, ok!
Click to expand...
Click to collapse
No You Will Do 2 Unlocks
nv_lao93 said:
SDAapplication didn't work btw.
Click to expand...
Click to collapse
Wait, You don't have the other unlock app yet! I will send it to you now!
okay then.
Technology said:
Wait, You don't have the other unlock app yet! I will send it to you now!
Click to expand...
Click to collapse
In Post # 10
In post # 10 I asked you 2 questions, please explan, concerning the RUU file!
RUU Info.
Well, i'm a noob, and don't know what RUU is, BUT the only time I've encountered that problem was when i was trying to install my original ROM back on. That's all. And also it says "RUU" on the top right of the screen on my dash
ALSO: the step by steps are on post 1
Technology said:
In post # 10 I asked you 2 questions, please explan, concerning the RUU file!
Click to expand...
Click to collapse
OK
nv_lao93 said:
Well, i'm a noob, and don't know what RUU is, BUT the only time I've encountered that problem was when i was trying to install my original ROM back on. That's all. And also it says "RUU" on the top right of the screen on my dash
ALSO: the step by steps are on post 1
Click to expand...
Click to collapse
Check you PM and follow the instructions to the utmost..............!
Definitions please? Sorry
Check you PM and follow the instructions to the utmost..............!
Technology said:
Check you PM and follow the instructions to the utmost..............!
Click to expand...
Click to collapse
Personal Message(PM)
nv_lao93 said:
Check you PM and follow the instructions to the utmost..............!
Click to expand...
Click to collapse
PM (personal message) (Utmost) follow instructions to the highest degree.
Edit Nov 28 2013: GN3 Owners PLEASE READ!
As of the new update the ATT Galaxy note 3(possibly all carriers) IS NOT compatable with KIES EFR!
This includes KIES 2.XX and KIES 3! What does this mean?
If you took the MJ5 update you will no longer be able to use the KIES Emergency Firmware Updater.
Please complain to Samsung, locking the bootloader is one thing but no EFR??
Would you get on ship with no life boats or life preservers??
Seriously uncool of Samsung to do this.
-end of edit
/rant
So its come to my attention a lot of new guys are getting stuck soft brick, bootloop, borked recovery etc.
So .... I made this tutorial for everyone.
Please: dont flame or post useless comments.
Its great for you Odin is easy, but I made this for people who want a hassle free easy way to recover their phone.
This is also imo the fastest and easiest way back to true stock w/o a "modified"
Some people have reported a flash count of 1 but idk I always went back to 0.
If you are new, have no rooting, rom flashing or w/e experience, imo you should NOT be using odin until you have completely read up on it. I mean hey some of you super geniuses have no probs but when I see posters who have no clue about usb drivers or even how to use kies, im confused why you would want to venture to odin? 500 $ is a very expensive brick.
Ok so unsure about odin or just new and now you just borked your brand new phone?
First things first:
Can you get into dl mode.
Dont worry about recovery mode because it doesnt matter for this. This works with corrupted recovery as well.
For now lets just say download mode is achieved one way only:
Press : vol down power and home key all at the same time. Release quickly when you see the screen come up. Takes practice some times.
:thumbup: This method will remove "modified" status from your phone! :thumbup:
:beer:
Ok ready? You want step by step you got it.
If this doesnt work you are doing it wrong, so try again. Even with Odin you may have to try several times, its the nature of android.
If you can get into DL mode you CAN 100% recover your device.
If it doesnt work or you get an error, you are doing this wrong. I am pretty sure this is for ALL Samsung phones but I can only confirm this for my gs3 and note2.
Keep in mind: I corrupted my recovery on my gs3 several times and this still worked. I will assume the same for my note 2.
Download kies from samsung.com
Follow the prompts but no need to install the stupid codecs.
When you are done, (dont forget hit "yes" to dl current usb drivers)
ON your computer "run as administrator" the kies icon.
make sure you are connected to the internet.
Kies will automatically check for updates and proper usb drivers.
No need to install "myfree codecs" hit no on that.
every thing else hit yes
Step one:
Run kies as administrator as I said And do all the usb updates, kies updates
but leave the codec thing alone.
Step by step instructions just follow the pics in order:
1.Kies opens asks about update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2.
3.Dont worry about this
4. Now in top left corner hit "tools" tab. Ignore everything else
5. After clicking tools tab click the emergency fimrware recover choice as described below
6. For now ignore this button. YOu might need it later but ignore it for now
7.
8.Well last step. Hit emergency recovery ( the "ok" button wont be there )
this will probably take 20 to 30 min total. The EFR will let you know if its succesfull or fail.
IF it fails try using the method I said to ignore. Its the same thing just an extra step of in putting your phones exact model number.
Heres some xtra links: (Thanks to Bajanman for finding these btw!)
http://www.sammobile.com/firmwares/1/
http://www.sammobile.com/kies/
http://m.samsung.com/us/support/
Nice help guide for noobs.
Good guide freak :thumbup:
Might want to go back and check some of your words tho. Lot of them misspelled... lol
Side note: All my years with Sammy I've never used Kies with any of my phone's!!
Sent from my SAMSUNG-SGH-I317 using Xparent SkyBlue Tapatalk 2
yeah yeah yeah
Nice tut freakboy i just hope I dont need to use it someday I subscribed anyways who know flashing games always full of surprises.
Sent from my SAMSUNG-SGH-I317 using xda premium
Please HELP
i have an at&t galaxy note 2 was rooted got OTA update now no signal and when i go to mobile networks (under settings) it says insert sim card so i am trying to do it your way and i have updated everything (drivers and kies) and when i try to connect to kies it says my device isn't supported by kies and there is no phone model in the white box to use the "emergency recovery using recovery code" is there a place to get this code?
Please help
Well first off there shouldnt be a need to use the kies efr with just an ota.
You can select your phone model manually.
Can I ask...did you install a recovery and make a bu after you rooted ?
im not familiar with these newer ota probs, I remember on my dx ota was no biggie due to rootkeeper. Its strange that a stock rooted phone gets borked with an ota.
Can you get into recovery?
Can you get into dl mode?
Im subscribed to this thread so ill try n help out
Edit: are you using this method because you are unfamiliar with odin?
i did install CWM recovery
i don't remember making a back up but i am sure i did
i can NOT get to recovery
i can get to dl mode
i am familiar with odin but i am on my work computer as i don't have internet at home at the moment so i cant run searches as it trips the big brother software here and i would get in trouble the phone seems to work fine other then it doesn't recognize the sim card and no recovery mode
but if i could find a stock rom i could just flash with odin
That may also be your problem.
Are you running kies as admin?
Sorry if these sound like stupid questions.
But 8f you dont have admin privies kies may not work.
Regardless there is a drop down for you to manually choose your phone.
You do have usb debugging?
A corrupted recovery should not affect your ability to use kies.
Your jobs software could be blocking it.
Also you do realise you cannot take ota with custom recovery?
Thats why your phone is borked.
i do realize it now lol but i didnt even think about it when it happened
yes running kies as admin
no to usb debugging don't event remember how to get to usb debugging but if it is in settings under mobile networks i cant get there it just says insert sim card
Justvto be sure this is an sgh-i317 correct?
Try doing the upgrade first that may give you the code.
First make sure you have usb debugging
Home>Settings> developers options> make sure usb debugging is checked.
Also since it sounds like your recovery is corrupted do not do a factory reset.
Ok so try this:
Make sure you have latest drivers from samsung for YOUR device.
Make sure kies is the latest version.
Make sure antivirus is off orvput kies in the whitelist/allowed.
Turning off is better.
Go to dl mode on phone .
Sincevkies is already running go to thetop menu :
tools> emergency firmware recovery
You should get a drop down list of devices. If this is an att phone and not another carrier model ported to att, you should choose sgh-i317 (att galaxy note 2). You shouldnt need a number thats only if you try to upgrade and it fails ( as I mentioned you may want to try upgrade first to trick the que to give you a number)
Post back.
+1
Sent from my SGH-I317M using xda premium
freakboy13 said:
Ok so try this:
Make sure you have latest drivers from samsung for YOUR device.
Make sure kies is the latest version.
Make sure antivirus is off orvput kies in the whitelist/allowed.
Turning off is better.
Go to dl mode on phone .
Sincevkies is already running go to thetop menu :
tools> emergency firmware recovery
You should get a drop down list of devices. If this is an att phone and not another carrier model ported to att, you should choose sgh-i317 (att galaxy note 2). You shouldnt need a number thats only if you try to upgrade and it fails ( as I mentioned you may want to try upgrade first to trick the que to give you a number)
Post back.
Click to expand...
Click to collapse
thanks so much for all your help there is no drop down box on my version of kies however i found stock firmware some where else and it is working now again thanks so much
mrnewspaper said:
thanks so much for all your help there is no drop down box on my version of kies however i found stock firmware some where else and it is working now again thanks so much
Click to expand...
Click to collapse
Nice job! Isnt it great figuring things out yourself?
Love hearing happy endings!
Now... go into recovery and :
Make a backup/boot img .
:thumbup:
Hello,
I am trying to fix my Korean Note 1. It is not being listed in the list of devices. I have it in D/L mode but it isn't listed. Can I use the code and, if so, what is the right code?
activepassive said:
Hello,
I am trying to fix my Korean Note 1. It is not being listed in the list of devices. I have it in D/L mode but it isn't listed. Can I use the code and, if so, what is the right code?
Click to expand...
Click to collapse
Hmmm not that familiar with note 1 or international version but ill assume its the same?
If you are not listed in the database you may want to try using odin.
The code needs to be generated by kies.
Is kies recognizing your phone?
I may be mistakwn but isnt their a kies for your country or some thing like that?
Have you submited this question in your forum?
Edit: I found this I hope it helps you!
http://forum.xda-developers.com/showthread.php?t=1740367
sent from my T.A.R.T.I.S
(Time And Relative Tarts In Space)
so this will restore my phone to stock and will instal stock recovery and reset my flash counter and modified status? no need for tiangle away and unroot??
i tried doing exactly what was in the OP and it's now stuck at 0% at restoring. It's given me an error message a few times before and i tried again but it still stays at 0%. I tried doing it with the button you said not to click and running as admin.
Now i've got two problems, one is the phone not getting out of this mode and 2 is it not even giving me an error message meaning i can't try again since it's still busy restoring.
What can i do now? Should i just pull the plug out of it and try again? Will this not break anything?
What should i do now OP?
further info:
model: galaxy S3 GT-19300
i've had it rooted using CF-root and i did a firmware update to trigger emergency recovery mode.
I got into emergency recovery mode on purpose but expected to get out of it...
---------- Post added at 08:03 PM ---------- Previous post was at 07:10 PM ----------
Hooray! it's now actually installing it and i didn't mistake it for downloading this time. I switched USB ports and now it works apparently.
Also something people that do this in the future should know: if you unplug the cable, it just gives you the error message saying that it couldn't find it which shouldn't cause any trouble. BUT only do this once it is stuck at 0%.
Possibly stupid question..
Having rooted the Note 2 att with mr skips toolbox, I then noticed a few days later the modified status.. So due to concern for warranty being voided, I'd like to return to stock: ( Heres the stupid question part).. I did install stock recovery via same toolbox, But How do I tell if it is stock vs twrp? I dont see where/how to check if it succeeded. Next- Why wont factory reset work to clear the flash counter, modified status to normal with full wipe? and as much as I admire mr Cortex method to full wipe ( 10 min process..) is that repetitive process of wiping, triangle away,unroot, reroot etc..necessary? I had a rooted samsung epic 4g touch before this note 2 and All I did to return phone to stock firmware for trade in was factory reset! yes- it was Not jellybean, was Gingerbread android.
Perhaps someone or some devs can explain this bit of mystery to me, and perhaps others... who are in search of a more direct and straightforward reset without complicating the steps. I will probably reroot and run a custom rom after warranty runs out.. but for now..stock again.
Would anyone happen to know where I can get the firmware for the Sprint variant of the Galaxy tab S 10.5? I have the "Firmware Upgrade Encountered an Error issue" after attempting to root with CF Auto Root. Kies 3 says it doesn't support the tablet, Sammobile doesn't have it and im pretty sure I don't want to contact Samsung quite yet. Thanks in advance.
Yes sammobile doesnt have firmware yet for snapdragon version
I just found out this tablet just came out to sprint. Which caused cf auto root to fail. Which could also mean it isn't on Sam mobile yet.
Is this a common thing? Does sammobile rarely get them for the Snapdragon variants?
Not sure, when the tab s wifi one came out there was already roms for them.
BDA_Rival said:
Would anyone happen to know where I can get the firmware for the Sprint variant of the Galaxy tab S 10.5? I have the "Firmware Upgrade Encountered an Error issue" after attempting to root with CF Auto Root. Kies 3 says it doesn't support the tablet, Sammobile doesn't have it and im pretty sure I don't want to contact Samsung quite yet. Thanks in advance.
Click to expand...
Click to collapse
well...since u have already tried the worse thing possible which is to flash a fule meant for an exynos device on a qualcom chipset then u might as well try this suggestion since it cant really make things worse at this point & just MIGHT actually work. Instead of using the our cfautoroot attempt to use the tab pro SM-T525 cfautoroot (link below)...i just saw that someone suggested that in another thread but dont know if u have had chance to try it yet. Also....as @edan1979 suggested chainfire is pretty good about creating new root packages if u can get him the files that he requests. If u do get this thing rooted with the file below then please pos back because i have a few files i need from your device if its not too much trouble...thx in advacnce
http://download.chainfire.eu/393/CF-Root/CF-Auto-Root/CF-Auto-Root-picassolte-picassoltexx-smt525.zip
^TAB 10.1 LTE SM-T525 CFAUTOROOT (same chipset except for screen...just might be the magic fix)
on a related note....i have aso been searching for the new qualcom/carrier branded firmware files & culdnt find them on sammobile either so if someone finds the one for sprint or the att/verizon version (SM-T707) then please let me know.
@DUHAsianSKILLZ
Just to be clear...i saw in the other thread that u said the wifi root method worked so i'm wondering what version of the device do u actually own?
@BDA_Rival
Thats actually why i suggested trying the other method...at this point your tablet could POTENTIALLY already be bricked & flashing the file i suggested is not only harmless but COULD even bring your tab back from the dead because theres no telling how long it will be before the firmware files are available. Worse case u can return it to sprint & say it failed during an over the air upgrade...i would definitely try the link i added NOT for the root but as an attempt to revive the tablet
I dont even care about root at this point, id rather have my tablet boot up to the stock OS. And I'd rather not fully brick it.
@THEDEVIOUS1 in the other thread I didn't know he had a sprint LTE tab s. I own a WiFi version of the tab s 10.5 inch. Sorry for any confusion.
THEDEVIOUS1 said:
Thats actually why i suggested trying the other method...at this point your tablet could POTENTIALLY already be bricked & flashing the file i suggested is not only harmless but COULD even bring your tab back from the dead because theres no telling how long it will be before the firmware files are available. Worse case u can return it to sprint & say it failed during an over the air upgrade...i would definitely try the link i added NOT for the root but as an attempt to revive the tablet
Click to expand...
Click to collapse
so i tried this because why not, already went to a service center and they acted like theyve never seen my issue. before i tried this, i had the binary status saying custom and the kox counter said 0. i flashed this, it was successful finally and my knox counter is at 1 which is fine. it tries to boot up unlike before but restarts saying "Could not normal boot" but i atleast see the splash screen. one question i guess i have is what would happen if i flashed the firmware for th the sm-t525? not that im seriously contemplating but if its the closest, chipset wise, would it work? i dont really care about cellular signal and if i brick it, im probably better off calling sprint with a completely bricked tablet that they wouldnt know was once rooted than one that says custom binary and the knox counter set off.
Well at least that's an improvement...the Odin firmware file will most likely NOT flash due to security checks so the only real hope u have right now is to try the 525 cwm or twrp and & see if it will boot into recovery. If it actually works then u could attempt one of their custom roms (would probably remove the boot.mg first) or maybe even cm11 for the tab pro (would have to delete the assert lines in the updater script so it would even flash). U can also try the a qualcom note 3 custom recovery (if they work will probably have resolution issues) or the 10.1 note 2014 ones which has the same chipset and resolution also
THEDEVIOUS1 said:
Well at least that's an improvement...the Odin firmware file will most likely NOT flash due to security checks so the only real hope u have right now is to try the 525 cwm or twrp and & see if it will boot into recovery. If it actually works then u could attempt one of their custom roms (would probably remove the boot.mg first) or maybe even cm11 for the tab pro (would have to delete the assert lines in the updater script so it would even flash). U can also try the a qualcom note 3 custom recovery (if they work will probably have resolution issues) or the 10.1 note 2014 ones which has the same chipset and resolution also
Click to expand...
Click to collapse
do radios matter though? would it brick because im flashing a verizon rom and those use different radios, or would it be better to flash a wifi rom? i dont really care if i have mobile data, i only use wifi. if i flash a 525 twrp, it wouldnt disable odin mode, would it?
BDA_Rival said:
do radios matter though? would it brick because im flashing a verizon rom and those use different radios, or would it be better to flash a wifi rom? i dont really care if i have mobile data, i only use wifi. if i flash a 525 twrp, it wouldnt disable odin mode, would it?
Click to expand...
Click to collapse
I'm assuming Odin mode & download mode are the same thing so the answer is yes IF it works u would be able to do the key combination and boot directly into recovery from Odin mode...I would NOT flash the radio although it shouldn't harm anything but what we really want right now is to leave as much of the original file system in place as possible & the only thing that technically should be different at this point is the recovery partition. The wifi versions are exynos devices so NO do NOT flash those because that's how we ended up here in the first place...just follow my last reply & since I don't like to waste posts if u respond needing more help just check back here for a mention of your username
THEDEVIOUS1 said:
I'm assuming Odin mode & download mode are the same thing so the answer is yes IF it works u would be able to do the key combination and boot directly into recovery from Odin mode...I would NOT flash the radio although it shouldn't harm anything but what we really want right now is to leave as much of the original file system in place as possible & the only thing that technically should be different at this point is the recovery partition. The wifi versions are exynos devices so NO do NOT flash those because that's how we ended up here in the first place...just follow my last reply & since I don't like to waste posts if u respond needing more help just check back here for a mention of your username
Click to expand...
Click to collapse
so im not sure i understood the last part of your message about wasting posts but i figured youd want to hear this. So i download the TWRP for the SM-P905 (note pro 12.2) and after i flashed it through odin, the tablet restarted and booted all the way up. I dont get how the hell this worked but flashing TWRP fixed my OS not booting. I also went to settings to check my device status and it says custom. i want to install super su but i dont know if TWRP stuck for sure or not and i cant get TWRP to boot, it keeps taking me to download mode. any ideas? id like to make a back up in case something dumb happens.
Edit: Got into recovery by holding home button, volume up button, and power but it says "Recovery booting, Recovery is not SEANDROID ENFORCING", not too sure what that means. heres the weird part. after it shows that, the screen starts turning gold within a matter of 15 seconds.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ever seen that before?
BDA_Rival said:
so im not sure i understood the last part of your message about wasting posts but i figured youd want to hear this. So i download the TWRP for the SM-P905 (note pro 12.2) and after i flashed it through odin, the tablet restarted and booted all the way up. I dont get how the hell this worked but flashing TWRP fixed my OS not booting. I also went to settings to check my device status and it says custom. i want to install super su but i dont know if TWRP stuck for sure or not and i cant get TWRP to boot, it keeps taking me to download mode. any ideas? id like to make a back up in case something dumb happens.
Click to expand...
Click to collapse
Sorry but the last part wasn't that serious...I just don't like to run my post count up. ok...that's great news which confirms what I thought since all the cf root really does is flash an altered stock recovery, install root then flash stock back. So...what I would try at this point is to go ahead & install supersu & hope that it detects the su file (it technically should) & if/when it requests u to upgrade the file choose NORMAL method NOT twrp/cwm which will attempt to finalize the root WITHOUT needing to boot into twrp. I would try to avoid that because even if it stuck there may be problems with the fact that it is from another device and will potentially screw the partitions up worse.....I know this is not the best bet for a backup but I would avoid recovery until u can find the proper Sprint Odin firmware for your device & instead just useb titanium to backup up your apps, system settings, & whatever else u can with it for the time being. At this point I would just be satisfied with the fact that u now have a working device & wait to do anything further until u get the correct software to fully fix it...well I'm glad u were able to get it going and IF u in fact have real root then can i get a HUGE favor? I need the keyguard.apk as well the framework-res.apk & twframework-res.apk with the corresponding odex files of course (i wouldn't mind having systemui & both framework jars if possible also)...if u can't do it , don't know how or it's just too much trouble then don't worry about it but i just thought I'd ask since I've been trying to find snap versions these files
@BDA_Rival
U edited your post before I could finish my reply but long story short just leave recovery alone for right now...what u are seeing is most likely due to the different types of screens between the 12.2 & 10.5 so the display driver is causing that problem. No problem on the assistance...that's were all supposed to be here for
Just thought I'd throw this out there since u seem to be able to find your way back home now but maybe if u try the cfautoroot for the P905 12.2 note pro then MAYBE that will root it...just thinking out loud though
http://forum.xda-developers.com/showthread.php?t=1980683&page=24
^NOTE PRO 12.2 LTE P905 CFAUTOROOT (see post #235...just in case u get the guts to try it again good luck)
THEDEVIOUS1 said:
Sorry but the last part wasn't that serious...I just don't like to run my post count up. ok...that's great news which confirms what I thought since all the cf root really does is flash an altered stock recovery, install root then flash stock back. So...what I would try at this point is to go ahead & install supersu & hope that it detects the su file (it technically should) & if/when it requests u to upgrade the file choose NORMAL method NOT twrp/cwm which will attempt to finalize the root WITHOUT needing to boot into twrp. I would try to avoid that because even if it stuck there may be problems with the fact that it is from another device and will potentially screw the partitions up worse.....I know this is not the best bet for a backup but I would avoid recovery until u can find the proper Sprint Odin firmware for your device & instead just useb titanium to backup up your apps, system settings, & whatever else u can with it for the time being. At this point I would just be satisfied with the fact that u now have a working device & wait to do anything further until u get the correct software to fully fix it...well I'm glad u were able to get it going and IF u in fact have real root then can i get a HUGE favor? I need the keyguard.apk as well the framework-res.apk & twframework-res.apk with the corresponding odex files of course (i wouldn't mind having systemui & both framework jars if possible also)...if u can't do it , don't know how or it's just too much trouble then don't worry about it but i just thought I'd ask since I've been trying to find snap versions these files
Click to expand...
Click to collapse
so i tried root checker, it said no root, i tried installing super su, said no root as well. i guess even though my device status says custom, im not actually rooted i went ahead and tried that CF Autoroot you suggested earlier in Odin and it gave me a boot loop so i flashed TWRP again and now its booting all the way. still says im not rooted so i just dont think its gonna work. If it did, i would have gotten that stuff for you for all your help. thanks for helping out.
Hi, I was on my way to root my z5p Australian version, I repaired with PC companion that also updated to Android 6 I suppose. But after update, I wanted to use my old gmail ID that I use in my other phones; however, after putting id and password it was asking for the id I've created temporarily for z5p to put that was previously synced with z5p. Unfortunately, as it was temporarily created I can't recall anything. I tried google recovery option with no luck.... can't even remember with id I used for recovery....
I've also reset it with flash tool guided through this forum, no luck.... tried to unlock boot loader from sonymobile forum by installing Android sdk. But it's failing when I put the command with the unlock code...
Is there any way that I can root my z5p or at least I can get to the phone...? Thanks in advance.....
That doesn't make a great deal of sense - did you encrypt the storage before doing any of this? If you factory reset the phone then it should 'forget' all of the Google account association and be like an 'out of the box' phone again...?
NJ72 said:
That doesn't make a great deal of sense - did you encrypt the storage before doing any of this? If you factory reset the phone then it should 'forget' all of the Google account association and be like an 'out of the box' phone again...?
Click to expand...
Click to collapse
Hi,
What do you mean by storage encryption...? I didn't do anything just updated the to Android 6 with Xperia companion. Since than I couldn't access to it without gmail account that i forgot. I read in one blog that from google has made a new security feature from Android 5 (google support for Android-one site). In that case, I've bricked my Z5P....
If none of you are able to help me, I need to through it away. I'm also ready to donate/pay for the service, if necessary. Thanks in advance.....
Hi,
Just got an idea, if Android 5 and onwards have more robust security features; is it possible to downgrade to kitkat or less, then unlocking the bootloader for rooting....? How about that...?
You won't be able to downgrade below 5.0 as that's what the device shipped with (I also doubt any devs are working on KK builds for the Z5P )
If you connect the device to your PC does it show within PC Companion? If so then try and wipe the device from there.
Can you take a picture of the screen you are presented with on boot as that should help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes, it is showing on PC companion and Xperia companion. However, I don't know how to wipe off. Please let me know. Thanks
sazzadhasan said:
Hi, I was on my way to root my z5p Australian version, I repaired with PC companion that also updated to Android 6 I suppose. But after update, I wanted to use my old gmail ID that I use in my other phones; however, after putting id and password it was asking for the id I've created temporarily for z5p to put that was previously synced with z5p. Unfortunately, as it was temporarily created I can't recall anything. I tried google recovery option with no luck.... can't even remember with id I used for recovery....
I've also reset it with flash tool guided through this forum, no luck.... tried to unlock boot loader from sonymobile forum by installing Android sdk. But it's failing when I put the command with the unlock code...
Is there any way that I can root my z5p or at least I can get to the phone...? Thanks in advance.....
Click to expand...
Click to collapse
The only way to continue past this is to "remember" the Google email (and password)
Sent from my E6653 using Tapatalk
Hmm... the only wipe method using PC companion is the 'repair' option that will almost certainly still require the use of your credentials. Can you show me how far in to the system you can get? Do you have another device you can use to take a photo?
Edit: I imagine you have as you mention flashtool, but have you tried flashing a new FTF with all of the options along the right hand side ticked?
NJ72 said:
Hmm... the only wipe method using PC companion is the 'repair' option that will almost certainly still require the use of your credentials. Can you show me how far in to the system you can get? Do you have another device you can use to take a photo?
Edit: I imagine you have as you mention flashtool, but have you tried flashing a new FTF with all of the options along the right hand side ticked?
Click to expand...
Click to collapse
I'll do it again today.
Yes, I used flashtool and ticked those 4 wipe options and did it twice; till same result. Yes, I've iPhone 6s Plus and the pic I sent was taken with that....
Hi, just thinking how about formatting the phone drive a put the new rom again...! Any ideas...?
sazzadhasan said:
Hi, just thinking how about formatting the phone drive a put the new rom again...! Any ideas...?
Click to expand...
Click to collapse
I think it might be the my xperia theft protection. Google it for more information
kamalaggi said:
I think it might be the my xperia theft protection. Google it for more information
Click to expand...
Click to collapse
Yeah, it is. Google has introduced it from Android 5.0 and onwards. If it continues, some people like me has to chuck the android phones away....
Just thinking, if I use a Different stock ROM other than AU, what would happen..!! Anyone have idea...?
I don;t think moving to a different region ROM would change anything. I doubt it's the Xperia theft protection, more like Google's built in stuff.
Random-ass question, but have you actually contacted Sony support about it? I appreciate you're likely to get a faster answer out of us here at XDA, but so far our ideas haven't turned up much...
Likewise I wouldn't blatt the whole storage just to try and get in to the phone, if you can't install a ROM back on it you'll be more than buggered.
Is there any way to at least find the email address you used as your Google ID? Did you get an email confirmation to your other Google account which would at least tell you the email address?
EDIT: perhaps have a look at this page: Google Account Recovery
sazzadhasan said:
Yeah, it is. Google has introduced it from Android 5.0 and onwards. If it continues, some people like me has to chuck the android phones away....
Click to expand...
Click to collapse
If you don't mind losing data, download an Ftf for your phone and flash through flashtools. When that happens, I think you can wipe data. Thus making your phone look " out of the box"
Not sure if anyone has told this already, didn't read through the pages.
As per my knowledge, it should ask you if you want to create a new account or use an existing one, when the phone boots up.
Ashray_Vk said:
If you don't mind losing data, download an Ftf for your phone and flash through flashtools. When that happens, I think you can wipe data. Thus making your phone look " out of the box"
Not sure if anyone has told this already, didn't read through the pages.
As per my knowledge, it should ask you if you want to create a new account or use an existing one, when the phone boots up.
Click to expand...
Click to collapse
Hi, just a quick question, what is a 'ftf'..? Yes, I did flash through flashtool with 4 things checked on the top right corner. After booting it asked me to sign in and I've signed in with a new gmail ID, well new in a sense that I used it with my old Samsung S2 4G, Sony tablet and so. After putting it through I got the notification in my iPhone gmail that my ID is used to sign in to Sony Xperia z5 premium...blah...blah....On the other hand, on z5p another screen came over which was asking to put my old temporary ID that I was created at the beginning; however, I forgot the ID. I've posted that picture at the beginning if you wanna look at it. Thanks
NJ72 said:
I don;t think moving to a different region ROM would change anything. I doubt it's the Xperia theft protection, more like Google's built in stuff.
Random-ass question, but have you actually contacted Sony support about it? I appreciate you're likely to get a faster answer out of us here at XDA, but so far our ideas haven't turned up much...
Likewise I wouldn't blatt the whole storage just to try and get in to the phone, if you can't install a ROM back on it you'll be more than buggered.
Is there any way to at least find the email address you used as your Google ID? Did you get an email confirmation to your other Google account which would at least tell you the email address?
EDIT: perhaps have a look at this page: Google Account Recovery
Click to expand...
Click to collapse
Thank you so much for all those ideas, but nothing helped me. I think it is a good time to throw it away....
sazzadhasan said:
Hi, just a quick question, what is a 'ftf'..? Yes, I did flash through flashtool with 4 things checked on the top right corner. After booting it asked me to sign in and I've signed in with a new gmail ID, well new in a sense that I used it with my old Samsung S2 4G, Sony tablet and so. After putting it through I got the notification in my iPhone gmail that my ID is used to sign in to Sony Xperia z5 premium...blah...blah....On the other hand, on z5p another screen came over which was asking to put my old temporary ID that I was created at the beginning; however, I forgot the ID. I've posted that picture at the beginning if you wanna look at it. Thanks
Click to expand...
Click to collapse
I tried. But I am not able to see that image, like it's broken or something. Maybe it's just me. Could you please upload that image again?
https://mega.nz/#!c9lRjRpD!8JQWyaqzEUj9wU7d5ic3MEO_zrfpTBhekwKCTmlPy6I
Here used to be a bad guide please don't follow it I learned that people where rightfully pissed at me and I have decided to replace it with this Im gonna flash lineage again and document my exact procedure and try to make a better guide than the garbage I posted here.
error : can't load losq-v
hey man,
Thanks for the effort but I only got one problem that whenever I enter this command "fastboot flash system losq-v lineage.img" I get the error saying "can't load losq-v" so what should I do.
Thanks in advance
KFC99 said:
hey man,
Thanks for the effort but I only got one problem that whenever I enter this command "fastboot flash system losq-v lineage.img" I get the error saying "can't load losq-v" so what should I do.
Thanks in advance
Click to expand...
Click to collapse
The reason is losq-v is the start of the filename pretty sure you can just press tab and it will autocomplete so the command would be "fastboot flash system losq-v"(after losq-v type rest of your filename or press tab to autocomplete (do not add a space in between losq-v and rest of filename))
Sry for forgetting that I did it like that to future proof the guide
camera not working
kamilkamjy said:
camera not working
Click to expand...
Click to collapse
Well it should. Ask the guys in the a71 group
Can it flash on U3 ui2.5 or 2.1?
Blocklisted said:
Well it should. Ask the guys in the a71 group
Click to expand...
Click to collapse
LoL
Posting "tutorials" in XDA is something else than copy and paste things you expect to work but never tested yourself.
Two persons get in trouble by the crap you copy and pasted here, and instead of take responsibility when things go bad, the only crap you can say is: ask THE GUYS in telegram rofl
What age are you? 12?
I hope no one follow this crappy " tutorial" here...
Odin Recovery Fails
I go step by step but when I hit start on Odin to flash recovery I get two error messages
1. one in Odin in the log section with the following message "failed (auth)"
2. the other on the phone in the download mode in red something along the lines "you can only install official binaries"
I searched the forums and found a few suggestions, turning on USB debugging, applying magisk patches etc.... I never saw anyone confirming any method that would have worked. Whatever I tried to do it either didn't work or I couldn't do it because of lack of skills or it wasn't possible. For example when I tried to use magisk in the descriptions I had install buttons in the manger but I'm missing these on my phone so I suspect that recovery is required first to make those patches or there's something that I don't know how to do it. Either way following the instructions doesn't work for me and I tried a bunch of things and none worked. Different versions of Odin 3.14.1, 3.14.4. If anyone has any idea please help. I reset the whole phone to factory hoping it would help, there's no data on it right now but I still get the same error.
Thanks
rb1979 said:
I go step by step but when I hit start on Odin to flash recovery I get two error messages
1. one in Odin in the log section with the following message "failed (auth)"
2. the other on the phone in the download mode in red something along the lines "you can only install official binaries"
I searched the forums and found a few suggestions, turning on USB debugging, applying
《Cutting》
Either way following the instructions doesn't work for me and I tried a bunch of things and none worked. Different versions of Odin 3.14.1, 3.14.4. If anyone has any idea please help. I reset the whole phone to factory hoping it would help, there's no data on it right now but I still get the same error.
Thanks
Click to expand...
Click to collapse
To back to original Android:
-Odindownload.com last Odin
- https://github.com/ivanmeler/SamFirm_Reborn/releases download samfirm reborn and use it to get latest original Samsung firmware
Unzip it with 7-ZIP !!!!!! www.7-zip.org
On the Odin website there is a YouTube video how to proceed. But do NOT use any PIT file you find somewhere like the vid shows in example, you will almost for sure brick it if you don't know exact exactly what you r doing! Be warned!
After unzipping you see files beginning with AP BL CP CSC , put them in Odin where they should be.
Under options ONLY mark AutoReboot and F reset time and nothing else.
I hope you get your phone back to working state with this, remember you will not be able to get updates OTA any more since you broke the Efuse.
From there on if I were you I only would root the phone and wait till official TWRP is out, or hopefully some day an official LineageOS.
So far nothing official means lack of maintanance after a while, no updates, bugs, bad assistance and more crap, just like this thread is written by someone who gathered info from just here and there and made this "tutorial" with copy and paste and added b.s. for trying to become a star on Telegram-ish group and look populair there.
Just Root it, debloat it and live with it.
andreoide said:
To back to original Android:
-Odindownload.com last Odin
- https://github.com/ivanmeler/SamFirm_Reborn/releases download samfirm reborn and use it to get latest original Samsung firmware
Unzip it with 7-ZIP !!!!!! www.7-zip.org
On the Odin website there is a YouTube video how to proceed. But do NOT use any PIT file you find somewhere like the vid shows in example, you will almost for sure brick it if you don't know exact exactly what you r doing! Be warned!
After unzipping you see files beginning with AP BL CP CSC , put them in Odin where they should be.
Under options ONLY mark AutoReboot and F reset time and nothing else.
I hope you get your phone back to working state with this, remember you will not be able to get updates OTA any more since you broke the Efuse.
From there on if I were you I only would root the phone and wait till official TWRP is out, or hopefully some day an official LineageOS.
So far nothing official means lack of maintanance after a while, no updates, bugs, bad assistance and more crap, just like this thread is written by someone who gathered info from just here and there and made this "tutorial" with copy and paste and added b.s. for trying to become a star on Telegram-ish group and look populair there.
Just Root it, debloat it and live with it.
Click to expand...
Click to collapse
Thanks andreoide for your honest answer :good:
My phone's working, I didn't get far with it, never broke it, just unlocked it. I guess the installation failed during the validation before actually doing any physical changes because my Samsung stock system still runs. The phone is given to me by my company. I just took out the sim card and put it in my private dual-sim phone. So this phone is on the shelf, it's been there for the last few months. I wish I could use it it's higher end than my personal but can't deal with Samsung stock system. I had two phones with lineage (and whatever the name was before) and loved it so I'm hoping I can use it again.
Anyway, it was just explaining my situation, I guess I'll be checking this forum and hoping for more positive news. Meanwhile the phone goes back on the shelf and waits for better times, thanks again for straitening things up for me. :good:
Blocklisted said:
Here used to be a bad guide please don't follow it I learned that people where rightfully pissed at me and I have decided to replace it with this Im gonna flash lineage again and document my exact procedure and try to make a better guide than the garbage I posted here.
Click to expand...
Click to collapse
Well, since you come clear and admit the guide you posted before was pure crap, i have to rise my thumbs up to you.
I think this is a mature respond.
:good: