Hello guys!
Is it possible to get out recovery.img from a official rom.zip file for OneX+?
I have a half bricked OneX+ Vodafone UK and it doesn't show the IMEI number. I want to flash it via Y Cable or via fastboot with latest official rom: PM35IMG_ENRC2B_U_JB_50_S_Vodafone_UK_2.17.161.2_Radio_3.1204.169D3.33_release_329050_signed.zip (got it from a friend,who works in the authorized HTC service center).
I tried relocking bootloader and flashing it with this rom,but it always fails at signature verification. This is the official latest rom for this exact phone,cid and product code, downloaded specially for this phone from official servers.
I can extract the main zip file and then I get 4 files from it.
When I try to extract the largest zip file from archive, it doesn't open with winrar,but does open with 7z. But,I can't extract those files with 7z.
So now I'm looking for stock recovery from this exact rom or for someone,who can help me extract it from this rom. This is the only option I have left and I can't find any info on how to do it. Or any other way,how can I install this rom to phone?
Please help!
I am surprised that the signature verification fails given that it is an official file and you have relocked the bootloader. What command are you using to flash it?
If you want to extract the zip on your PC then you might need to use https://github.com/kmdm/ruuveal to decrypt it first.
Okay,so after a few hours repeating the same procedure again and again, somehow I finally managed to reflash it via the Y Cable. But,only via the Y Cable, fastboot still didn't flash it.
Anyway, the problem is not solved and I still don't have the IMEI number back. Tried a lot of stuff, to get it back, but no results.
Anyway,I talked with my friend at the authorised service center. He said,that these problems may happen even with OTA or official RUU updates. They don't have any options to repair them other than reflasing it or changing the main board. But since this device is not from our region,but from UK Vodafone, he's not allowed to change the board. So, guess I'm out of luck and unfortunately this piece of cr*p is on Nvidia, so I cannot repair it via JTAG. :crying:
Anyway,thanks!
ReeLT said:
Okay,so after a few hours repeating the same procedure again and again, somehow I finally managed to reflash it via the Y Cable. But,only via the Y Cable, fastboot still didn't flash it.
Anyway, the problem is not solved and I still don't have the IMEI number back. Tried a lot of stuff, to get it back, but no results.
Anyway,I talked with my friend at the authorised service center. He said,that these problems may happen even with OTA or official RUU updates. They don't have any options to repair them other than reflasing it or changing the main board. But since this device is not from our region,but from UK Vodafone, he's not allowed to change the board. So, guess I'm out of luck and unfortunately this piece of cr*p is on Nvidia, so I cannot repair it via JTAG. :crying:
Anyway,thanks!
Click to expand...
Click to collapse
Hi ReeLT,
Is your phone stuck in airplane mode? Hence no IMEI?
I have the same issue with my O2 HOX+.
Am looking to either revert to stock HTC or to O2_001 stock.
patela20 said:
Hi ReeLT,
Is your phone stuck in airplane mode? Hence no IMEI?
I have the same issue with my O2 HOX+.
Am looking to either revert to stock HTC or to O2_001 stock.
Click to expand...
Click to collapse
No,it's not stuck in airplane mode. It just doesn't have IMEI number,so phone does not see SIM card.
Anyway,I can try to get the official latest ROM for you, I'll need to see all the barcodes that can be found in the Show Barcode option in bootloader. Make a picture of it and send it to me. I'll try to get it next week.
Maybe you'll need a Y Cable to flash it, because in my case I couldn't flash the Rom.zip file via fastboot.
Related
Disclaimer
Code:
Neither Me Nor XDA Are Responsible If You Lose Your Job/Break Your Device.
Your Warranty Is Now Void
Downloads :
WIP
Instructions :
Extract The .rar
Open The Setup File And Install LG Flashtool
Right Click On The Shortcut Created On Your Desktop And Open File Location.
Copy The .dll Files From The DLL Folder To The Previously Opened Location And Replace The .dll In Flash Tool Folder If Any.
Open The Flashtool,Select The .dll Then The .tot/.bin File And You Are Ready To Flash The Firmware,Connect The Phone In Download Mode When Asked.
Note :
I Don't Know Whether It Works For N4 Converted Devices.I Had Successfully Flashed Stock .20 .bin File With It.But I Suggest To Use This Only When LGNPST Does Not Work/Fails To Flash The FW As For Me.Please Don't Perform Unwanted Experiments With Your Device Or It Will Result In A Hard Brick.
This Guide Was Originally Created By madmack @ Optimus G Pro Section So Thanks To Him.
I was Searching For The .dll File For Our Device And Found It So Decided To Create A Thread.And Those Who Are Thinking That The Required .dll Is The Same That We Use For LGNPST,NO,This Is A Different .dll
It Did Not Ask For Unlock Code When I Flashed The Stock JB FW.But As Posted By madmack there is A Possibility That It Can Ask For Your Unlock Code.So Proceed With Caution.
Again This Is A Alternate To LGNPST And Only I Have Successfully Flashed The Stock FW.It Is Recommended That Unless It Is Tested By 4-5 Experienced Users,Its A No Go For Noobs/New Users.
And Be Advised That This Process Will Wipe Your Internal Storage.
Enjoy!
Regards,
acervenky,
XPT
reserved
Thanks for sharing.
Edit: There are many more things to do in his (madmack) thread... Did u follow them all? Or for us we do not need all those steps? Let us know before someone bricks.. I use LGNPST but if anyone tries this.. at least they have a better understanding. thanks again for sharing.
just a heads up.. TeenyBin does not work in LG Flash. There are extra CRC checks which I haven't been able to bypass yet. This may change in the future.
also, not sure if this version of LG Flash is same as the newer one I use but I have to set the COM port to 40+ for LG flash to see my device.. altho maybe I'm missing something. I have to go into windows device manager and manually change the COM port used for the phone ( its in properties ).
LG Flash is no better or worse than LGNPST in my opinion. On the plus side.. there's no dll to register... and options are good
Googler_1976 said:
Thanks for sharing.
Edit: There are many more things to do in his (madmack) thread... Did u follow them all? Or for us we do not need all those steps? Let us know before someone bricks.. I use LGNPST but if anyone tries this.. at least they have a better understanding. thanks again for sharing.
Click to expand...
Click to collapse
Changed The Status To WIP.
Will Search For The Info And Update The Thread Soon
Regards,
acervenky,
XPT
autoprime said:
just a heads up.. TeenyBin does not work in LG Flash. There are extra CRC checks which I haven't been able to bypass yet. This may change in the future.
also, not sure if this version of LG Flash is same as the newer one I use but I have to set the COM port to 40+ for LG flash to see my device.. altho maybe I'm missing something. I have to go into windows device manager and manually change the COM port used for the phone ( its in properties ).
LG Flash is no better or worse than LGNPST in my opinion. On the plus side.. there's no dll to register... and options are good
Click to expand...
Click to collapse
Yup.
Regards,
acervenky,
XPT
Download link is missing.
I've try to found the download link for the Lg Flash tool on this page, but i haven't. Can you fix it or explain? Thanks anyway.
Which .TOT and .DLL files will you be providing? I need the .DLL and .TOT file for, of course, the AT&T Optimus G E-970 US version! I flashed my wifes phone cause it boot looped and the .TOT used was SUPPOSED to be this file but it is the Korean FW. Now my wifes phone will not update via OTA because it changed her IMEI number. I need to get her phone back to stock 4.1.2 US VERSION!
cougar214 said:
Which .TOT and .DLL files will you be providing? I need the .DLL and .TOT file for, of course, the AT&T Optimus G E-970 US version! I flashed my wifes phone cause it boot looped and the .TOT used was SUPPOSED to be this file but it is the Korean FW. Now my wifes phone will not update via OTA because it changed her IMEI number. I need to get her phone back to stock 4.1.2 US VERSION!
Click to expand...
Click to collapse
Here is the file you need to get her phone back to STOCK U.S: http://downloads.codefi.re/g33k3r/LGE970AT-01-V20j-310-410-MAR-08-2013.zip I'm not sure on the DLL file, I use LGNPST so not sure if they are the same but attached it also just incase you can use it.. stock firmware file above is a .tot file so if you need to you can just change it to .bin if you need to.
Thank you blake but no. That is the fw file that turned her phone Korean. So may people are under the impression this is the stock US fw but it isn't. I even had another person here check their phone and his too in fact says "Lg Electronics Korea".
cougar214 said:
Thank you blake but no. That is the fw file that turned her phone Korean. So may people are under the impression this is the stock US fw but it isn't. I even had another person here check their phone and his too in fact says "Lg Electronics Korea".
Click to expand...
Click to collapse
Where do you go check to see if its U.S or Korean?
All settings--> about phone -->phone Identity.
It's under settings-->about phone-->phone identity.
I had another person tell me that's normal because it's only the "manufacturer" info. Which im told this phone is manufactured in Korea. I don't know. All I do know is everyone is saying this is the stock fw for this phone but my wifes phone has changed. The start up screen is different and so is the shut down screen. Example, when her phone would shut down, she would get the AT&T logo and sound. After flashing this file she gets the blue circle and no sound. I do know that 4.1.2 is different depending on the region the phone is in. I don't know anything else that would explain this. Maybe this FW file WAS a different region but it was stripped out and converted somehow?
cougar214 said:
It's under settings-->about phone-->phone identity.
I had another person tell me that's normal because it's only the "manufacturer" info. Which im told this phone is manufactured in Korea. I don't know. All I do know is everyone is saying this is the stock fw for this phone but my wifes phone has changed. The start up screen is different and so is the shut down screen. Example, when her phone would shut down, she would get the AT&T logo and sound. After flashing this file she gets the blue circle and no sound. I do know that 4.1.2 is different depending on the region the phone is in. I don't know anything else that would explain this. Maybe this FW file WAS a different region but it was stripped out and converted somehow?
Click to expand...
Click to collapse
After a little checking I found out the same thing, It was normal as it was the place of manufacturer. I'm not sure what the problem might be but as far as I know that's the stock firmware for the phone.. You might try this one out http://www.androidfilehost.com/?fid=22901594685177912 you just boot into recovery do the normal wipes and flash through recovery, its supposed to be stock except for being rooted and as far as I know those are the only two stock files floating around for the phone...
Thanks Blake. Can you confirm for me that this phone will NOT get OTA updates if it's changed in any way, including rooting? It's what I was told by someone else. If that's the case then I guess there really is nothing wrong with the phone except those weird unexplained small changes.
I've got all the correct files download and I made it so far as to try to actually flash the phone, but it fails and gives me a wrong model number message because it's detecting my phone as a E960 (it's an E970). Any ideas? I had installed the latest CM11 ROM over some encrypted data and now I'm locked out (old encryption PIN doesn't work) and I can't restore it to stock.
can someone help me with a .tot or .bin stock for lg l70 d320n? cuz i"ve looked for it everywhere but couldn"t find anything
need help bad.
i got this phone from a friend and it originally had cm11 on it. the phone in question is the lg e970. i wanted to get back to stock. so i downloaded the correct firmware and added it to my external sd card. using twrp before i proceeded to wipe the phone via twrp. when it was finished i restarted the phone into twrp and went to install the stock firmware and i could not find my exsd card. twrp does not recognize it at all. so now im stuck with a phone with no os on it. i can ge into twrp and download mode, and when i just boot the phone it goes to lg logo and stays there. i need help in trying to figure out how to get stock firmware back on phone. i am used to samsung phones and odin. so im a noob when it comes to lg. i am very tech savy when it comes to computers. plzzzzzz any help would be great!!!!!!!! and appreciated
I can not add .tot file in LG flash tool
I have unrooted my lg g3 before on another computer. But i can't add the .tot file with my new computer. I am doing everything the same.
Does anyone have any ideas?
I have to upgrade my My Samsung Galaxy S-II from Gingerbread to Jellybean
my but mobile does not connect with PC as USB connector is broken.
So, up-gradation with Odin or Kii does not support.
Alternatively, I have to update over OTA but mobile says that the latest updates have already been installed.
So i found an option in Boot Menu which says "Update from SD Card"
Now my question is that:
If I place official jellybean file in Phone Memory or Memory Card
Will it be update from there?
if Yes, kindly guide me.
If not then kindly also guide me how to update my Galaxy-S2.
Regards.
The very first thing you have to do is get the USB port fixed.
Modifying the software on a phone will *ALWAYS* carry an element of risk......
Sometimes, if things go wrong, the only way to put them right is to flash a firmware with odin.......
How do you use odin?
You install it on your PC and connect your phone to your PC via a cable and the USB port.....If your USB port is broken, you have a device you can't fix.
I personally would advise you NOT to modify your device until you have the port repaired.....
If you want to try it yourself, I wrote a guide which explains exactly how to do it.....
http://forum.xda-developers.com/showthread.php?t=2335961
Read the first post IN FULL before attempting to do it and pay particular attention to the section concerning 'REV VERSIONS'.....it is critical to successfully repairing your phone.
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
The very first thing you have to do is get the USB port fixed.
Modifying the software on a phone will *ALWAYS* carry an element of risk......
Sometimes, if things go wrong, the only way to put them right is to flash a firmware with odin.......
How do you use odin?
You install it on your PC and connect your phone to your PC via a cable and the USB port.....If your USB port is broken, you have a device you can't fix.
I personally would advise you NOT to modify your device until you have the port repaired.....
If you want to try it yourself, I wrote a guide which explains exactly how to do it.....
http://forum.xda-developers.com/showthread.php?t=2335961
Read the first post IN FULL before attempting to do it and pay particular attention to the section concerning 'REV VERSIONS'.....it is critical to successfully repairing your phone.
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Ok thanks, brother, i will do as you advised. but only tell me one thing.
What will happen if I place official jellybean file into Sdcard and then from boot menu i choose "Update from SD Card"???
Will it be updated ?
Afaik it won't work.......
I think you use the stock recovery to flash only zip files.......
Firmwares come as .tar files which recovery can't deal with......
http://i.imgur.com/rVnFwJM.jpg
You can try using mobile ODIN: http://forum.xda-developers.com/showthread.php?t=1347899
I think you are not receiving OTA updates because probably your phone carrier stopped shipping updates ages ago.
Of course you will need a rooted phone to do this. You will need to download the latest firmware onto your phone (you can download from sammobile.com), unzip it with es file explorer or alternative file manager, then select the files according to the corresponding categories.
Alternatively (and I think this is a much safer option, but can be tedious for new users), root your phone with a custom gingerbread kernel or cf-auto-root, install a jellybean compatible recovery or jelly bean kernel such as apolo kernel, then install a stock based rom such as neatrom (I will give instructions if you decide to do this way). This way, you still have a newer version of android minus all of the bloatware from samsung.
In other words, without root and OTA updates from phone carrier, you pretty much left with no option but to fix the usb port on your phone.
regards, gsstudios.
Hey guys,
Sorry in advance for what is no doubt something that's came up a few times in the past (as is clearly evident by the posts). I've spent a long time trying to get around the issues with this thing so hopefully I can explain what I've done so far which might help.
So, basically -
My brother had an S3. The screen broke (glass only) and he asked me to repair it. This was a few months ago. Inbetween he moved to using a Windows phone and had the S3 sitting around until he eventually decided to hand me it to repair a couple of days ago.
Now, the phone was working flawlessly prior to him turning it off and switching over to the Windows phone. The S3 sat dormant for a few months, battery out.
When I went to turn it on to test the screen and buttons to ensure that's the only fault, it wouldn't get past the boot screen.
No huge deal there.
Upon checking in recovery it was unable to mount the EFS partition. I managed to get round that.
It still wouldn't boot, so I flashed a new ROM and it booted up fine however was in "Factory mode" with IMEI starting 0049.
I've done a fair amount of searching and came to a few conclusions but essentially :
How I don't know but his EFS folder was competely corrupt and essentially contained few files, none of which were IMEI related. I have no clue how this has happened but it has.
I've managed to get the phone working ALMOST flawlessly by restoring a stock EFS backup IMG using kTool, I HAVE the phone's IMEI and serial which are printed on the phone itself. Only issue now is that the phone can't connect to any networks - because the IMEI is a default.
So, I've dug around in the stock EFS backup IMG that I was able to find (which has got the phone working great, minus mobile networks) and found that the IMEI folder contained a file "mps_code.dat". Upon opening this file it's basically empty. I assume this is because it's a stock EFS I located.
Does anyone have any clue how I can input the IMEI into this file? I tried to decompile the IMG, type it into the file and save, then recompile the IMG however kTool doesn't recognise the newly created IMG file and crashes, then restores the phone. Is there a specific tool I should be using to make the IMG and can someone root into their "mpd_code.dat" and tell me the format that it needs to be in? (I don't need or want any IMEI numbers, just the format that the file is. Just open it in a text editor through Root Explorer (root\efs\imei) and star out the IMEI if you can).
Just to clarify before anyone jumps on it - I'm NOT looking for the file(s) OR the IMEI numbers on anyones phone with that request. Simply the format in which it should be in. I'm simply trying to put the IMEI for the phone ONTO the phone so it'll recognise networks and work as it should. Everything else is absolutely fine now.
So just to clarify the options I've boiled down to :
Recompile the efs.img with the correct IMEI within - if someone can tell me how that'd be great - then restore it on kTool.
OR
Edit the on-phone mps_code.dat with the correct IMEI but I need the format (if someone could peek at theirs that'd be great).
Thank you in advance all and sorry for the story! If I manage to get this to work I'll upload a tutorial with all the relevent files required which I know will help a lot of people.
Cheers
Mine mps_code.dat have 3 letters in it i-e 'TNL' which is csc i think. And imei is in efs1 and efs2 partition you can see in pit analysis thread google it if you don't know anout this thread.
Only thing which you can do is give phone to repair shop they have boxes and tools which can write imei. Or take backup of efs1 efs2 and efs of other phone and restore it in your phone.you do backup/restore using partition backup app in playstore by wanam.
Thanks for your reply. I will try to locate someone else I know with an S3 and pull their EFS - hopefully something will happen that's of benefit.
In the meantime, I'll focus on this as hard as I can to get it sorted. I've managed to go from having the IMEI reading as a random 0049 one, to "Null/Null" which means it HAS been written to (or does in my mind), just with nothing rather than the correct number.
If I get anywhere I'll update this thread, and if im successful in the repair I'll create a How-To based on what I did.
Cheers
I can repair your device. Had the same problem with my mothers phone.
The problem is that samsung changed the style of the efs format years ago and the S3 was falling in this time.
So if you need help, i can help.
konsolen said:
I can repair your device. Had the same problem with my mothers phone.
The problem is that samsung changed the style of the efs format years ago and the S3 was falling in this time.
So if you need help, i can help.
Click to expand...
Click to collapse
Hey mate,
Want me to PM you?
Thanks
I had the same problem days ago and I couldn't connect to sim network.
What I did was flash stock rom using odin and then a custom modem and a custom kernel I found in the internet. At the end it gave me a normal imei number (not the [email protected]%) but it wasn't my original imei... nevertheless it can connect now without any issues .
jairolas said:
I had the same problem days ago and I couldn't connect to sim network.
What I did was flash stock rom using odin and then a custom modem and a custom kernel I found in the internet. At the end it gave me a normal imei number (not the [email protected]%) but it wasn't my original imei... nevertheless it can connect now without any issues .
Click to expand...
Click to collapse
Hey bro,
Do you remember specifically what ROM, kernel and modem you flashed? Ive tried this with no luck so interested in trying your combination.
Cheers
Ok guys this is exactly what I did:
1- backup all your data.
2- download a stock 4.3 jellybean rom from sammobile (I used the Trinidad and Tobago version because I live in Mexico but that shouldn't matter), autoroot cf for i9300 4.3 from their website and twrp 2.8 recovery, again from their website.
3- download this especial kernel and this modem:
https://www.dropbox.com/s/4cawyqzg8zo1vot/Patched_XXUGMK6_kernel.zip.zip?dl=0
https://www.dropbox.com/s/tky93zds14kt1hz/Patched_XXUGMK6_modem.zip.zip?dl=0
4- Proceed to flash stock 4.3 rom using odin 3.07.
5- After stock rom is installed flash the root cf file and recovery tar using odin.
6- Now that you have a rooted stock rom with custom recovery proceed to flash both the especial kernel zip and the modem zip using twrp recovery.
7- You should now be able to connect network.
Good luck.
jairolas said:
Ok guys this is exactly what I did:
1- backup all your data.
2- download a stock 4.3 jellybean rom from sammobile (I used the Trinidad and Tobago version because I live in Mexico but that shouldn't matter), autoroot cf for i9300 4.3 from their website and twrp 2.8 recovery, again from their website.
3- download this especial kernel and this modem:
https://www.dropbox.com/s/4cawyqzg8zo1vot/Patched_XXUGMK6_kernel.zip.zip?dl=0
https://www.dropbox.com/s/tky93zds14kt1hz/Patched_XXUGMK6_modem.zip.zip?dl=0
4- Proceed to flash stock 4.3 rom using odin 3.07.
5- After stock rom is installed flash the root cf file and recovery tar using odin.
6- Now that you have a rooted stock rom with custom recovery proceed to flash both the especial kernel zip and the modem zip using twrp recovery.
7- You should now be able to connect network.
Good luck.
Click to expand...
Click to collapse
Thanks bro, will try that in the morning!
Hey mate,
I started the process of this today, using a stock samsung FW that I updated to using Kies.
Unfortunately the end result is the same, 0049 IMEI number.
What I'll do is I'll download the T&T 4.3 from Sammobile and see if that makes any difference.
Thanks again,
jairolas said:
Ok guys this is exactly what I did:
1- backup all your data.
2- download a stock 4.3 jellybean rom from sammobile (I used the Trinidad and Tobago version because I live in Mexico but that shouldn't matter), autoroot cf for i9300 4.3 from their website and twrp 2.8 recovery, again from their website.
3- download this especial kernel and this modem:
https://www.dropbox.com/s/4cawyqzg8zo1vot/Patched_XXUGMK6_kernel.zip.zip?dl=0
https://www.dropbox.com/s/tky93zds14kt1hz/Patched_XXUGMK6_modem.zip.zip?dl=0
4- Proceed to flash stock 4.3 rom using odin 3.07.
5- After stock rom is installed flash the root cf file and recovery tar using odin.
6- Now that you have a rooted stock rom with custom recovery proceed to flash both the especial kernel zip and the modem zip using twrp recovery.
7- You should now be able to connect network.
Good luck.
Click to expand...
Click to collapse
yetep said:
Hey mate,
I started the process of this today, using a stock samsung FW that I updated to using Kies.
Unfortunately the end result is the same, 0049 IMEI number.
What I'll do is I'll download the T&T 4.3 from Sammobile and see if that makes any difference.
Thanks again,
Click to expand...
Click to collapse
Hey hey,
Right unfortunately all of the above doesnt solve any issues im having with the IMEI.
What I'm ultimately trying to do is find out a way to fix this, without having to use third-party hardware or a samsung service station.
The real reason is that I don't think the average user should have to go that extent to fix this - it's ultimately Samsung's fault.
Android is designed to be customisable allowing users to go up/down versions as they please (provided it's compatible with the hardware of their phone).
Just a thought -
is there any possible way to "bake" the old style EFS into a newer rom?
yetep said:
Hey mate,
I started the process of this today, using a stock samsung FW that I updated to using Kies.
Unfortunately the end result is the same, 0049 IMEI number.
What I'll do is I'll download the T&T 4.3 from Sammobile and see if that makes any difference.
Thanks again,
Click to expand...
Click to collapse
Hey All (that are viewing this).
The above procedure didn't work. I have managed to get the IMEI to change from 0049 to NULL/NULL and back again at will using a blank EFS restore file that I've got, however can't figure out what and how to change the files WITHIN the EFS restore to the correct IMEI etc.
I'll continue my search and if I come across anything, I'll let you all know on here and create a How-To.
Cheers
Hey all - just a quick question on this.
Does anyone know how to modify the server to which a program points to check for user credits etc? There's clear reason I'm asking for this, however for obvious reasons I won't elaborate further right now.
Cheers
Hello there! Is the problem fixed? Couple of days ago i fixed someones i9300 whos having this kind of error. Pm me ill help
lyxtian said:
Hello there! Is the problem fixed? Couple of days ago i fixed someones i9300 whos having this kind of error. Pm me ill help
Click to expand...
Click to collapse
I have sent you a pm.
konsolen said:
I can repair your device. Had the same problem with my mothers phone.
The problem is that samsung changed the style of the efs format years ago and the S3 was falling in this time.
So if you need help, i can help.
Click to expand...
Click to collapse
I have a samsung galaxy s7 sm-G930F which is bricked. no imei anymore and no efs backup. can u help me fix it?
I have a brand new Galaxy A21 (SM-S215DL). In Developer Options, there is NO OEM Unlock toggle (not even a grayed out one; it simply does NOT exist anywhere in settings). I have tried several different variants of the date/time trick to try to get it to appear, and none of them worked. But while in Download Mode, KG Status is shown as `CHECKING`, so doesn't that mean it should at least be visible? Do I even need to unlock my bootloader? Is it even possible?
Using Frija, I managed to get what I believe to be the correct stock firmware for my device. I also grabbed both of the latest official and patched versions of Odin. Flashing the stock firmware works, but flashing the patched Magisk AP fails with an AUTH error for file `vbmeta.img`, which leads me to believe that I actually DO need to unlock my bootloader... but if that's the case, I'm having trouble figuring out how to do so without the OEM toggle.
Is there anything else can I try?
SpectreCular said:
I have a brand new Galaxy A21 (SM-S215DL). In Developer Options, there is NO OEM Unlock toggle (not even a grayed out one; it simply does NOT exist anywhere in settings). I have tried several different variants of the date/time trick to try to get it to appear, and none of them worked. But while in Download Mode, KG Status is shown as `CHECKING`, so doesn't that mean it should at least be visible? Do I even need to unlock my bootloader? Is it even possible?
Using Frija, I managed to get what I believe to be the correct stock firmware for my device. I also grabbed both of the latest official and patched versions of Odin. Flashing the stock firmware works, but flashing the patched Magisk AP fails with an AUTH error for file `vbmeta.img`, which leads me to believe that I actually DO need to unlock my bootloader... but if that's the case, I'm having trouble figuring out how to do so without the OEM toggle.
Is there anything else can I try?
Click to expand...
Click to collapse
I also have the Samsung A21 from T Mobile (SM-A21UZKATMB). The phone is unlocked by T Mobile but there is no OEM bootloader unlock button under the Developer mode. Changing the date (forward and backward in time), then run the software update did not solve the OEM bootloader unlock button problem. I suspect the carrier (T Mobile) has disabled this function. You will need to unlock the bootloader to install the stock firmware.
To those who have enabled the OEM bootloader in the A21. Is your phone locked to a carrier in the USA like Verizon or T Mobile?
I also have the SM215DL, using straight talk utilizing verizon service, I also cannot unlock the bootloader. Everything you guys did, I did. Nothing worked.
samsung has done this to all A series phones intended for the U.S. from what i understand
Where there's a will, there's a way... someone has messed with my phone too do doesn't that mean that they're altering the data/data partition to r/w. Did you guys try fastboot flashing unlock vs. fastboot oem unlock. I'm going to contact Samsung about this and let u all know what's up.
And also why would there be a usb debugging port if this phone can't be modded? Idon't know the answer but maybe someone more expediency could come in and help us out. I also wonder if the flash_image command or just dd it would bypass it?
... there is NO way, to root the A21(s), see here: https://forum.xda-developers.com/t/root-possibility.4130739/page-12#post-84944589
MaBo2020 said:
... there is NO way, to root the A21(s), see here: https://forum.xda-developers.com/t/root-possibility.4130739/page-12#post-84944589
Click to expand...
Click to collapse
I confirm that I have rooted my A21S sucessfully using this modified magisk (U3 Rom). No need to patch the whole AP.tar file, just patch boot.img file only. I upload my patched boot.img for those who need it. Just flash it via odin in AP slot. Thank you very much @grccorps.
https://forum.xda-developers.com/attachments/boot-tar.5299081/
thatha said:
I confirm that I have rooted my A21S sucessfully using this modified magisk (U3 Rom). No need to patch the whole AP.tar file, just patch boot.img file only. I upload my patched boot.img for those who need it. Just flash it via odin in AP slot. Thank you very much @grccorps.
https://forum.xda-developers.com/attachments/boot-tar.5299081/
Click to expand...
Click to collapse
... exactly Step-by-Step, how u do it with downloadlinks of all Software, what u used !
Many Peoples writes, that they have rooted the A21s, but no one shows, how ! With the newest Firmware u cant rooted the Phone, because there is no working TWRP, SuperSU or MAGISK - Version out for this Phone !
MaBo2020 said:
... exactly Step-by-Step, how u do it with downloadlinks of all Software, what u used !
Many Peoples writes, that they have rooted the A21s, but no one shows, how ! With the newest Firmware u cant rooted the Phone, because there is no working TWRP, SuperSU or MAGISK - Version out for this Phone !
Click to expand...
Click to collapse
Extract boot.img from AP.tar, then use modified-magisk to patched it
... this Methode is not working, i try it many Times, no RootAcess ! Again: if u have newer Firmware on this Phone (End 2020 - until now) u cant root this Phone ! Maybe on ure Phone an older Firmware ...
And this is my U5 patched boot.img
MaBo2020 said:
... this Methode is not working, i try it many Times, no RootAcess ! Again: if u have newer Firmware on this Phone (End 2020 - until now) u cant root this Phone ! Maybe on ure Phone an older Firmware ...
Click to expand...
Click to collapse
I have just made a post here, you can try it
[SHARING] HOW TO ROOT A21S STOCK ROM WITH MAGISK
Hello friends I just want to share how to root A21S stock rom in case anybody needs it: 1. Unlock bootloader 2. (On PC) Extract boot.img.lz4 from AP...tar file, then copy it to phone 3. (On phone) Install ZArchiver to extract boot.img from...
forum.xda-developers.com
... and u shure, it its for the A21s or for A21 ?
The only hope of getting root on this phone is if you find a Dev who's interested enough to build a bootstrap recovery. I've not looked at the firmware & have no idea if there's an exploit that would work for that purpose.
Bootstrap recovery was the only way of getting root/custom recovery back in the days of Motorola D2 & Droid X, the original Droid X. Motorola was THE phone for development... Liberty ROM, Gummy ROM, Simply Stunning, etc.
I would not hold out hopes for that to happen here.
Peace - MS
Seriousfreedom said:
samsung has done this to all A series phones intended for the U.S. from what i understand
Click to expand...
Click to collapse
No, Samsung has done this to ALL North American models ever since the Galaxy S8. The bootloaders are not user-unlockable, like they are on international models. However, some models can be rooted via a software exploit if they're running very old firmware, or some models can even be bootloader unlocked via special files, if their firmware version is old enough
SpectreCular said:
I have a brand new Galaxy A21 (SM-S215DL). In Developer Options, there is NO OEM Unlock toggle (not even a grayed out one; it simply does NOT exist anywhere in settings). I have tried several different variants of the date/time trick to try to get it to appear, and none of them worked. But while in Download Mode, KG Status is shown as `CHECKING`, so doesn't that mean it should at least be visible? Do I even need to unlock my bootloader? Is it even possible?
Using Frija, I managed to get what I believe to be the correct stock firmware for my device. I also grabbed both of the latest official and patched versions of Odin. Flashing the stock firmware works, but flashing the patched Magisk AP fails with an AUTH error for file `vbmeta.img`, which leads me to believe that I actually DO need to unlock my bootloader... but if that's the case, I'm having trouble figuring out how to do so without the OEM toggle.
Is there anything else can I try?
Click to expand...
Click to collapse
Mine is rooted. But you have to buy a token.
o.class.jav said:
Mine is rooted. But you have to buy a token.
Click to expand...
Click to collapse
what token??
[email protected] said:
what token??
Click to expand...
Click to collapse
The one generated by the SamPwns steady.bin flash.
{Mod edit: Quoted post removed}
and where does one get 'TWRP' for the Samsung Galaxy A21S?? Thanks for the post its very detailed with very clear instructions, and i agree with you this is the tried and tested and perfect way of rooting your phone, only problem is that this is an unperect world a world where 'TWRP' for the SM-A217F does not exist
I just received a refurbished SM-S215DL (A21,) not as my provider's solution to the VoLTE soon to be required for 4G devices thing and right now it's a pretty severe downgrade for me since it lacks a lot of basic functionality I'm used to from my 2017 phone running LineageOS. Obviously it's pretty unlikely or probably outright impossible to ever see a real LineageOS ROM for this thing (and even if someone ever does it probably would be insanely unstable or incomplete,) but if I could at least root it (even if I have to manually patch or something) it would really help me out a lot. Has just nothing really been found short of sending some unknown person online some very very key device details and money (which I don't have or I'd be buying something else anyway)? (Also kind of suspicious that whatever method they're using isn't something available to the public anyway...)
Hello,
I was installing different custom ROMS for this phone, then reverted back to Stock ROM. It updated itself, and IMEI got erased somehow.
Is there any way possible to flash a custom ROM, or even custom recovery using MSMDownloadTool? I had a global version N10, so it was sim unlocked and bootloader unlockable, and I do actually have my IMEI on the back of my box, but can't put it into my phone as I have to root it. But I can't root it because the bootloader is now locked, and the bootloader is now locked because there is no IMEI......
This leaves me locked out of fastboot, so the only option is edl, which works just fine. However, only MSMDownloadTool is compatible with this mode, and it only installs Stock ROMs.
I tried extracting the .OPS files, replacing the stock recovery with twrp (and then renaming it to recovery.img), repacking the .ops then installing it. It installs, but then never boots and is just stuck in edl mode until I reflash the normal stock rom with the stock recovery.
What Do I do?
Thanks
CrustyBurger33 said:
Hello,
I was installing different custom ROMS for this phone, then reverted back to Stock ROM. It updated itself, and IMEI got erased somehow.
Is there any way possible to flash a custom ROM, or even custom recovery using MSMDownloadTool? I had a global version N10, so it was sim unlocked and bootloader unlockable, and I do actually have my IMEI on the back of my box, but can't put it into my phone as I have to root it. But I can't root it because the bootloader is now locked, and the bootloader is now locked because there is no IMEI......
This leaves me locked out of fastboot, so the only option is edl, which works just fine. However, only MSMDownloadTool is compatible with this mode, and it only installs Stock ROMs.
I tried extracting the .OPS files, replacing the stock recovery with twrp (and then renaming it to recovery.img), repacking the .ops then installing it. It installs, but then never boots and is just stuck in edl mode until I reflash the normal stock rom with the stock recovery.
What Do I do?
Thanks
Click to expand...
Click to collapse
If your bootloader was relocked, encryption and partition checking were enabled again.
TWRP would only cause your phone to register as modified and lock itself...and due to streamlining of a lot of functions, you can't even use the dialer to enter the menu needed.
Best you can do is totally wipe everything on your phone and generate a new android ID. (You have to do this from the actual OS instead of recovery though. Recovery format uses predetermined instructions. The format option from the android settings panel has a different set of instructions and one of them is to generate a new android ID, which includes IMEI)
Thanks for the reply, although im kinda confused by your answer. How do I generate a new android ID? (what does that even mean lol). I checked in my settings and I can't find any "format option"
CrustyBurger33 said:
Thanks for the reply, although im kinda confused by your answer. How do I generate a new android ID? (what does that even mean lol). I checked in my settings and I can't find any "format option"
Click to expand...
Click to collapse
Android ID is what determines your phone is the phone it claims to be when pinging google services.
Move any files you want to keep to somewhere safe. Format your phone, android will push you a new id number. It won't fix your IMEI, but it'll keep your phone from being absolutely useless in the process.
After your phone is formated and has booted back into the OS, you can enable adb. Adb into fastboot, use fastboot to determine if your device is still bootloader unlocked using the fastboot oem device-info command
ninjasinabag said:
After your phone is formated and has booted back into the OS, you can enable adb. Adb into fastboot, use fastboot to determine if your device is still bootloader unlocked using the fastboot oem device-info command
Click to expand...
Click to collapse
I tried everything you said, reset everything, still no IMEI, and even if the Android ID is different it hasn't really changed anything. Just to be clear, when I flashed the stock ROM earlier, everything worked as intended apart from the SIM card (which doesnt work at all) and the WiFi (which keeps dropping after 5 seconds of connection). Those problems persist even now.
Guess I'll be messing around with the SMT mode in MSMDownloadTool since I've already lost my IMEI, see what I can do from that. If there's anything I do actually end up finding out, I'll post it on xda.
Update
I installed an update by download a zip, installed update via settings. System rebooted to complete update, and somehow the oem unlock option opened!!
From this point, fixing it will be pretty straight forward I think
Thanks for your help
CrustyBurger33 said:
Update
I installed an update by download a zip, installed update via settings. System rebooted to complete update, and somehow the oem unlock option opened!!
From this point, fixing it will be pretty straight forward I think
Thanks for your help
Click to expand...
Click to collapse
Nice! If everything is working properly besides the IMEI at this point, there's a couple of PC applications you can use.
I'd recommend write dual imei, not gonna post a link since IMEI fudging is against the rules (even if you're just trying to repair your IMEI)
Use the IMEI that's on your device sticker or on your phone packaging specifically.
Either way, hoping you get your phone back up to 100%.
As it turns out, it's not easy at all. My WiFi has exactly the same issue... keeps dropping, No SIM card, no baseband version. What's crazy is that I have rooted, and even repaired the IMEI via a tool. If I read the IMEI via the tool (and different ones just to be sure), they will all show the IMEI the same as the one that I wrote (which were the original ones).
But for some reason the phone still doesnt recognize it. I reboot it. Same story. The tool recognizes, the phone doesn't. I know for a fact that the issue cannot be hardware, at least for WiFi. If it was, it wouldn't connect to any network, but it does, and then disconnects after a few seconds. I think I have been all over every post on the internet regarding this issue, but still no luck.
Honestly, check with OnePlus if you're under the 1 year warranty window. This sounds like an issue that can really only be fixed with a replacement device.
CrustyBurger33 said:
As it turns out, it's not easy at all. My WiFi has exactly the same issue... keeps dropping, No SIM card, no baseband version. What's crazy is that I have rooted, and even repaired the IMEI via a tool. If I read the IMEI via the tool (and different ones just to be sure), they will all show the IMEI the same as the one that I wrote (which were the original ones).
But for some reason the phone still doesnt recognize it. I reboot it. Same story. The tool recognizes, the phone doesn't. I know for a fact that the issue cannot be hardware, at least for WiFi. If it was, it wouldn't connect to any network, but it does, and then disconnects after a few seconds. I think I have been all over every post on the internet regarding this issue, but still no luck.
Click to expand...
Click to collapse
Hi I have a similar problem.. My phone oneplus 8t is stuck in 'SMT Download failed error' mode. I was tryimg out custom roms which has caused this. My phone says can only be fixed via SMT Download mode. Can you help me out using the SMT download mode? I have tried MSM Tool normally to unbrick my phone but it doesn't work.
hello @nightfury04
If you have a Oneplus 8T you have to download the appropriate MSMDownloadTool (specifically for it) and make sure the version is correct too. Is your phone global/ locked to a carrier?