Related
I just bought this metro s3 and wanted to root it, well supersu was giving error everytime I tapped it so I decided to try an unroot with many of the methods on here and along the way ended up where my phone will not get past the galaxy siii sgh-t999n boot screen.
I used odin to do this, my phone is not being recognized under auto play but pc makes the connection sound when I plug usb in to my pc.
anyways I'm stuck at that screen and can only enter odin recovery on my phone and I have tried factory reset and still end up at the same boot screen and left it like that all night an woke up to the same screen.
I'm hoping this is not not a $300. brick.
I did download the files from a thread that described the files below were for the "T999l & T999n" and IF there was any difference int he files then the OP would point that out he said and I tripple checked to make sure in the section of the listed files to download did not mention the T999n was not for those specific files but there was nothing mentioned..
Please link the said thread.
You have not specified the firmware and android version you had before all this happened. Please specify that. Next Course of action depends on as much information you could provide about previous setup, Bootloader, Rom, Kernel & Baseband.
I think you only have a Non-Bootable Rom. I'd call that as a soft-Brick and not Hard-Brick. So there's no chance of you getting a $300 Paperweight. :laugh:
Having said that, given that all you want is Root, then
1. Flash Root66 version of your Firmware.
Perseus71 said:
Please link the said thread.
You have not specified the firmware and android version you had before all this happened. Please specify that. Next Course of action depends on as much information you could provide about previous setup, Bootloader, Rom, Kernel & Baseband.
I think you only have a Non-Bootable Rom. I'd call that as a soft-Brick and not Hard-Brick. So there's no chance of you getting a $300 Paperweight. :laugh:
Having said that, given that all you want is Root, then
1. Flash Root66 version of your Firmware.
Click to expand...
Click to collapse
Well I have solved my boot issues my installing CWM (which before would not stick after boot) and flashing 3 files from Docholiday on a thread but now the phone boots up as a T999L 4g LTE and has changed the model number under about phone. I have to unlock the phone as I only have a tmobile sim for this said Metropcs T999N device so I will see what happens after I try to unlock it.
thanks you for your prompt response!!
If Settings > About > Model is the only problem you have, then use Build.prop Editor from Playstore and change the value for RO.BUILD.DISPLAY.ID. Set it to what your device is.
Im not bothered by it myself as long as it wont effect my device?? also effect any future updates or when a program tries to sync with my device or anything other??
I don't believe there would be issues of this nature.
Does anyone have a stock firmware of their S6 Edge T-Moible? that's ODIN flashable. I bricked my S6 trying to root it and had the KNOX security on. Now it just boot loop.
Jjgh
Refer to this how-to article and read the 'Note' that is posted.
http://jtechd.net/2015/04/how-to-root-samsung-galaxy-s6-galaxy-s6-edge-downloads/
Protomize said:
Does anyone have a stock firmware of their S6 Edge T-Moible? that's ODIN flashable. I bricked my S6 trying to root it and had the KNOX security on. Now it just boot loop.
Click to expand...
Click to collapse
Did you try and flash the S6 file (non-edge file) to root your phone? For many that corrects what looks to be a bricked phone.
I did the same thing the OP had done, referring to enabling KNOX prior to rooting, and none of anyone's suggestions through the past multiple days have worked. Enabling "KNOX" under the "Security"
settings is a big no-no, or so it seems from the few that have done it. Might be worth somebody making a thread just letting people know NOT to do that if they don't wish for an expensive brick until a stock ODIN tar surfaces. It makes the phone bootloop and useless even when using the regular S6 autoroot tar. It's also interesting how nobody answered the OP's actually question, though. "Is there an actual stock ODIN tar for this phone yet?" I would like to know the same, even though my own research has come up negatory thus far. Focus on the dude's question rather than waste time with other suggestion(s) which they likely already know haven't worked.
Ker~Man said:
I did the same thing the OP had done, referring to enabling KNOX prior to rooting, and none of anyone's suggestions through the past multiple days have worked. Enabling "KNOX" under the "Security"
settings is a big no-no, or so it seems from the few that have done it. Might be worth somebody making a thread just letting people know NOT to do that if they don't wish for an expensive brick until a stock ODIN tar surfaces. It makes the phone bootloop and useless even when using the regular S6 autoroot tar. It's also interesting how nobody answered the OP's actually question, though. "Is there an actual stock ODIN tar for this phone yet?" I would like to know the same, even though my own research has come up negatory thus far. Focus on the dude's question rather than waste time with other suggestion(s) which they likely already know haven't worked.
Click to expand...
Click to collapse
Why would you enable KNOX when you are trying to root a phone tho ?
Ker~Man said:
I did the same thing the OP had done, referring to enabling KNOX prior to rooting, and none of anyone's suggestions through the past multiple days have worked. Enabling "KNOX" under the "Security"
settings is a big no-no, or so it seems from the few that have done it. Might be worth somebody making a thread just letting people know NOT to do that if they don't wish for an expensive brick until a stock ODIN tar surfaces. It makes the phone bootloop and useless even when using the regular S6 autoroot tar. It's also interesting how nobody answered the OP's actually question, though. "Is there an actual stock ODIN tar for this phone yet?" I would like to know the same, even though my own research has come up negatory thus far. Focus on the dude's question rather than waste time with other suggestion(s) which they likely already know haven't worked.
Click to expand...
Click to collapse
Hey, I fixed it it. Watch this: https://www.youtube.com/watch?v=qCh0QuEwAgY
Protomize said:
Hey, I fixed it it. Watch this: https://www.youtube.com/watch?v=qCh0QuEwAgY
Click to expand...
Click to collapse
Thank You soooooooo much. that actually worked. thank you thank you thank you.
Thank you all for this. I would also like to know if this deletes all the user data/apps/contacts as well? I'm trying to restore the phone to stock so I can return it but as others have said with the root performed I am unable to hard reset/restore to factory so I am looking for a work around. Thanks in advance.
Yes, it deletes all user data, but the phone will have root.
samanbabah said:
Thank You soooooooo much. that actually worked. thank you thank you thank you.
Click to expand...
Click to collapse
Glad it was able to work.
So when rooting a T-Mo Edge first time, we should use the std S6 (SM-G920T) autoroot file, and not the file listed for the edge?
SykesAT said:
So when rooting a T-Mo Edge first time, we should use the std S6 (SM-G920T) autoroot file, and not the file listed for the edge?
Click to expand...
Click to collapse
yes you use the G920T but that will mess up your recovery, so be aware.
After using galaxy s6 cf auto root file restore your recovery by following this:
http://zidroid.com/download-t-mobile-galaxy-s6-edge-g925t-stock-recovery
Zi.Droid said:
After using galaxy s6 cf auto root file restore your recovery by following this:
zidroid. com/download-t-mobile-galaxy-s6-edge-g925t-stock-recovery
Click to expand...
Click to collapse
I want to thank you for at least getting me back to a recovery mode screen that is readable and starts with the normal icon, that says updating system. I still need to wait for the stock SM-G925T firmware file for the S6 Edge to get back to a working phone. Deleting knox files as I stated in a few threads here is a big no no for now. Just get that bootloop on startup and this has nothing to do with rooting. Is the deleted files. Samsung support confirmed this too. I did try the factory reset which basically wiped the phone of info, which is no big deal. Plenty of backups. Just need the darn tar file for this model. I'm sure it will be out soon.
BTW, I was having issues getting on to any web link site Sammobile.
http://www.hidebux.com/unblock/sammobile.com
Uses a private web proxy to access. Open link, click on unblock and you are in :good:
Docmjldds said:
I still need to wait for the stock SM-G925T firmware file for the S6 Edge to get back to a working phone... Just need the darn tar file for this model. I'm sure it will be out soon.
Click to expand...
Click to collapse
You are still unable to get Kies to work? Did you watch my Video and follow those steps? If you are still having trouble, let me know. Might be a driver issue or something.
SuperSport said:
You are still unable to get Kies to work? Did you watch my Video and follow those steps? If you are still having trouble, let me know. Might be a driver issue or something.
Click to expand...
Click to collapse
ok...doing video. asks for my serial number. It's not the IME. Can't get to about phone settings. Tmobile has no clue how to find my serial number. Calling Samsung if they can match my IME. Maybe you can pm me a number for the Edge.
---------- Post added at 08:53 PM ---------- Previous post was at 08:02 PM ----------
SuperSport said:
You are still unable to get Kies to work? Did you watch my Video and follow those steps? If you are still having trouble, let me know. Might be a driver issue or something.
Click to expand...
Click to collapse
I want to publically thank you for your superb and timely help. What's funny is I'm on a MAC desktop and the Kies Mac version would not connect to my phone even though I have the drivers already on the computer. I use Parallels to boot to a Windows 8 virtual setup. Kies gave me the unsupported device message I think, but after going to the tools menu and following the instructions on the video, all went well. The only nit pick is I believe the Kies program called it the recovery mode to boot into, but they used the correct button combo to actually be in download mode for this to work.
Anyways....much thanks and for all those waiting for stock firmware for the Edge to magically appear, which I'm sure it will eventually, this method works. Word of advice to all.....go into your settings and about device and write down your serial number since it's required when inputting the model number. TMobile and Samsung incorrectly kept telling me the serial number is the same as the IME. IT'S NOT. And that number is NOT on the box labeling either. So without the serial number of your device KIES won't work for this firmware restore. A simple thank you to the person that know, for helping me with that aspect.
Docmjldds said:
I want to publically thank you for your superb and timely help.
Click to expand...
Click to collapse
Thank you for this, and thank you for letting others know about the correct serial number used.
For anyone in the same situation, you CAN borrow a serial number from another device to get the download started just as Docmjldds and I did here. I gave him mine, and the download proceeded as normal. After the phone is flashed, it still retains the correct factory serial that came with your phone.
SuperSport said:
Thank you for this, and thank you for letting others know about the correct serial number used.
For anyone in the same situation, you CAN borrow a serial number from another device to get the download started just as Docmjldds and I did here. I gave him mine, and the download proceeded as normal. After the phone is flashed, it still retains the correct factory serial that came with your phone.
Click to expand...
Click to collapse
You can also get the serial number from download mode. When you first boot into dl mode and you get the warning page press the home button and the IMEI and SN (serial number) are both there with a bar code.
jamcar said:
You can also get the serial number from download mode. When you first boot into dl mode and you get the warning page press the home button and the IMEI and SN (serial number) are both there with a bar code.
Click to expand...
Click to collapse
Great Tip! Thank you for this. I did run into that when I was messing around, but totally forgot about it. Just updated my Video to include this info with a thanks to you.
I have an ATT ZenFone 2E that I rooted successfully with this guide (http://forum.xda-developers.com/showthread.php?t=3116531). Due to an error on my part(fat finger) I accidentally started the OTA update. Now when I try to boot the phone all I get is the AT&T logo/splash screen. I can get it to go into recovery mode and it also will connect via ADB. I have tried flashing the UL-ASUS_Z00D-WW-12.16.5.30-user.zip firmware via ADB fastboot but I get an error saying firmware is wrong carrier ATT (WW). Am I using the wrong firmware for AT&T? I have searched all over and cannot find any ZenFone 2 firmware other than WW, TW, and CN. Any help or suggestions much appreciated.
JRSouth said:
I have an ATT ZenFone 2E that I rooted successfully with this guide (http://forum.xda-developers.com/showthread.php?t=3116531). Due to an error on my part(fat finger) I accidentally started the OTA update. Now when I try to boot the phone all I get is the AT&T logo/splash screen. I can get it to go into recovery mode and it also will connect via ADB. I have tried flashing the UL-ASUS_Z00D-WW-12.16.5.30-user.zip firmware via ADB fastboot but I get an error saying firmware is wrong carrier ATT (WW). Am I using the wrong firmware for AT&T? I have searched all over and cannot find any ZenFone 2 firmware other than WW, TW, and CN. Any help or suggestions much appreciated.
Click to expand...
Click to collapse
i have the exact problem since saturday, you have to use the ATT firmware but i couldnt find it anywhere
also
please pm me if u fixed yours
Lactaid said:
please pm me if u fixed yours
Click to expand...
Click to collapse
Still no luck. I'm sure if we could find the AT&T firmware we would be able to recover. Unfortunately it appears it is not available on ASUS support and AT&T doesn't even provide firmware. Our only hope may be from a backup of another device that isn't bricked.
Does anybody know if we could possibly use the temporary CWM recovery used in the root method to flash to another ROM that is compatible with this device? Any input would be greatly appreciated.
Are there any details I can provide that would be helpful in finding a solution to recover this device? I've seen a few other people are having the same issue as I am and I would like to help them as well if I can get mine fixed. Thanks
JRSouth said:
Are there any details I can provide that would be helpful in finding a solution to recover this device? I've seen a few other people are having the same issue as I am and I would like to help them as well if I can get mine fixed. Thanks
Click to expand...
Click to collapse
ive literally tried everything, my device has been bricked for like 3 weeks now
Lactaid said:
ive literally tried everything, my device has been bricked for like 3 weeks now
Click to expand...
Click to collapse
Just out of curiosity have you tried running the xoa_unroot.bat while your device is in recovery/fastboot mode? Im not sure if it will help but I've found in other threads that to avoid soft bricking your device you must run the unroot prior to applying the OTA update. I'm sure it's probably too late but maybe worth a shot. I'm going to try it when I get home from work today.
JRSouth said:
Just out of curiosity have you tried running the xoa_unroot.bat while your device is in recovery/fastboot mode? Im not sure if it will help but I've found in other threads that to avoid soft bricking your device you must run the unroot prior to applying the OTA update. I'm sure it's probably too late but maybe worth a shot. I'm going to try it when I get home from work today.
Click to expand...
Click to collapse
i havent tried it yet, do you have a tutorial of it?
The truth hurts, your screwd. This is a budget phone. At&t will not support it. Throw away device my their standards.
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
http://forum.xda-developers.com/showpost.php?p=63323103&postcount=118
^^^This worked for me successfully!
Make sure to only restore system and disable MD5 Checksum Verification.
I have the same problem, what do I do with that file? How do I apply it through the SD, so I can apply update from SD? I forgot pin code to phone so i need to restore
need help
Lactaid said:
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
Click to expand...
Click to collapse
how do I flash this?
Hola, alguien lo consiguió hacer..???
Lactaid said:
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
Click to expand...
Click to collapse
Im getting an error that day footer is wrong :/
m1chb3ltr3 said:
Im getting an error that day footer is wrong :/
Click to expand...
Click to collapse
Wait, are you bricked and tried using that as the fix? I cant post links but Check out Asus, They have Firmware, Kernel (havent checked but read it earlier today), and Boot Unlock that you can get right from (assuming you have an account) My Products.
Also... Has anyone used that method recently?
Cathaterfish said:
Sorry I will give credit to DavePmer for his guide in minute, but qouting him for some reason wouldnt let me post, even when I removed the links? anyways I'll edit and give credit I promise
So my phone is stuck on the Asus Logo, I downloaded all of this and followed the instructions all the way up to:
11) now the fun part. open your microsd card and check the folder TWRP\BACKUPS see if it has a folder named
01234567890123456789 if it does great if not, not a problem just copy all the system files from the folder
you extracted TWRP-zf2e-ATT_12.16.10.7 to your microsd card TWRP\BACKUP\01234567890123456789\ whatever folder you have next\ in other words, replace your system.ext4.win000 files with my system.ext4.win000 file.
Replace your system.ext4.win001 with mine, and replace system.ext4.win00.md5 with mine as well as system.ext4.win001.md5 when done safely dismount the microsd card.
It then occurred to me that i should be more careful this time around... This was from October and although I ran across links saying for the most part that this was a good shot for fixing my ZE500CL, Z00D or whatever. But things have changed since then and I was wondering if this is still the best/easiest/safe route. I learned pretty quick that over looking things like OTA/Root or in my case Making assumptions is a fast path to really doing a number on your phone. (Honestly I just started even giving thought to rooting my phone, just considered them back ups I kept in a box). I now have the itch to do this right so hoping to fix this and go about this the right way.
Thanks for any input.
Currently DLing RussaiNBeaR, went and bought a card reader/writer. I was going to Download the firmware, kernel and boot unlock tool but currently staying at a place where im getting 160kbs on my DL's. So if I can get away with davepmer's guide that would be great, or something other or smaller than downloading 4gbs on this Internet Connection.
EDIT: Forgot to add that I haven't completed this step yet because the wording kind of tripped me up. And I want to do this right. When he says "in other words replace your system.ext4.win000 files with my system.ext4.win000 file." and then goes on and 3 more to the list. Does that mean only copy and replace those 4? or does that include all system.(whatever).(extension) files? Im sure it sounds really dumb or noobish but the fact that the next step is using twrp to restore using system only makes me afraid to do this part wrong.
Click to expand...
Click to collapse
ayuda
ATT ZE500CL/Z00D rom
I want to UNroot my phone/restore my phone due to the fact that I believe I may have done something wrong in the process. I am on 5.0.1
When I turn my phone on, I do get the welcome screen saying my phone's unlocked and all but when I try to use xposed installer it says that my device is not properly rooted?
Specifically it says " The latest version of Xposed is currently not active. Did you install the framework and reboot?" When I try to do this, it says
"Xposed is not (yet) compatible with Android SDK version 21 or your processor architecture (armeabiv7a)
CANNOT LINK EXECUTABLE: could not load library "libdvm.so" needed by" /data/data/de.robv.android.xposed.installer/cache/app_process";
cause by library "libdvm.so" not found"
And I believe I had a very hard time (when rooting) copying and pasting the SuperSU to internal storage. Not all the files were actually being transferred over.
I pretty much want to restore my phone so that I can try to root it properly this time.
When the tutorial on how root our phones came out, I feel as though I rushed it from excitement without properly educating myself on what to watch out for.
Maybe I am only HALF rooted? lol sounds so stupid. but my greenify works and superSU grants access to everything. I just don't understand.
My last phone was iphone4 and jailbreaking that was easy. This is something else.
Can anyone help? Thank you for your time!
yungzhvo said:
I want to UNroot my phone/restore my phone due to the fact that I believe I may have done something wrong in the process. I am on 5.0.1
When I turn my phone on, I do get the welcome screen saying my phone's unlocked and all but when I try to use xposed installer it says that my device is not properly rooted?
Specifically it says " The latest version of Xposed is currently not active. Did you install the framework and reboot?" When I try to do this, it says
"Xposed is not (yet) compatible with Android SDK version 21 or your processor architecture (armeabiv7a)
CANNOT LINK EXECUTABLE: could not load library "libdvm.so" needed by" /data/data/de.robv.android.xposed.installer/cache/app_process";
cause by library "libdvm.so" not found"
And I believe I had a very hard time (when rooting) copying and pasting the SuperSU to internal storage. Not all the files were actually being transferred over.
I pretty much want to restore my phone so that I can try to root it properly this time.
When the tutorial on how root our phones came out, I feel as though I rushed it from excitement without properly educating myself on what to watch out for.
Maybe I am only HALF rooted? lol sounds so stupid. but my greenify works and superSU grants access to everything. I just don't understand.
My last phone was iphone4 and jailbreaking that was easy. This is something else.
Can anyone help? Thank you for your time!
Click to expand...
Click to collapse
This may be of some help.
kkretch said:
This may be of some help.
Click to expand...
Click to collapse
Thank you for replying so quickly! :good:
Do you happen to know if this will automatically upgrade me to the newest OTA upgrade?
I want to stay on 5.1.1 so I can try to root it properly. And I've been delaying the OTA upgrade since day 1 and still doing so even with the supposed root I have on my phone right now.
yungzhvo said:
Thank you for replying so quickly! :good:
Do you happen to know if this will automatically upgrade me to the newest OTA upgrade?
I want to stay on 5.1.1 so I can try to root it properly. And I've been delaying the OTA upgrade since day 1 and still doing so even with the supposed root I have on my phone right now.
Click to expand...
Click to collapse
If you're going to root your phone, you don't want to take the OTA. You'll just have to downgrade to Lollipop anyway.
Use ODIN and flash the full firmware. 5.1.1 should be good. @hsbadr has a thread in the Development forum with all of the firmware that's available. It'll save you the slow download speed of Sammobile.
If when you go into download mode and you see "mode: developer," you're pretty close to root. Flash SuperSU and TWRP and you'll be there.
douger1957 said:
If you're going to root your phone, you don't want to take the OTA. You'll just have to downgrade to Lollipop anyway.
Use ODIN and flash the full firmware. 5.1.1 should be good. @hsbadr has a thread in the Development forum with all of the firmware that's available. It'll save you the slow download speed of Sammobile.
If when you go into download mode and you see "mode: developer," you're pretty close to root. Flash SuperSU and TWRP and you'll be there.
Click to expand...
Click to collapse
"If when you go into download mode and you see "mode: developer," you're pretty close to root. Flash SuperSU and TWRP and you'll be there."
Can you elaborate a little more on this for me? Because when I first rooted I made sure to do EVERY step. Read the forums and watched youtube videos directly linked from the forum.
The thing I just didn't know how to do correctly was flashing the SuperSU and TWRP (I THINIK)
I sincerely just remember trying to copy and paste some files into system storage? something like that... and not EVERYTHING was transferring over.
When I turn on my phone I get the welcome screen with the picture of the unlocked lock with "custom" underneath. So I know I must have done SOMETHING correctly.
Im just sincerely lost. It's quite infuriating .
yungzhvo said:
"If when you go into download mode and you see "mode: developer," you're pretty close to root. Flash SuperSU and TWRP and you'll be there."
Can you elaborate a little more on this for me? Because when I first rooted I made sure to do EVERY step. Read the forums and watched youtube videos directly linked from the forum.
The thing I just didn't know how to do correctly was flashing the SuperSU and TWRP (I THINIK)
I sincerely just remember trying to copy and paste some files into system storage? something like that... and not EVERYTHING was transferring over.
When I turn on my phone I get the welcome screen with the picture of the unlocked lock with "custom" underneath. So I know I must have done SOMETHING correctly.
Im just sincerely lost. It's quite infuriating .
Click to expand...
Click to collapse
Go into download mode. From phone off, hold the volume down, power and home buttons together. If it says "mode: developer" in the upper left hand corner when you get it in developer mode, your bootloader is unlocked. At that point you can pick up the instructions for flashing SuperSU and TWRP. You may need to flash the Emotion kernel... it's been awhile since I unlocked Lollipop.
douger1957 said:
Go into download mode. From phone off, hold the volume down, power and home buttons together. If it says "mode: developer" in the upper left hand corner when you get it in developer mode, your bootloader is unlocked. At that point you can pick up the instructions for flashing SuperSU and TWRP. You may need to flash the Emotion kernel... it's been awhile since I unlocked Lollipop.
Click to expand...
Click to collapse
I'm about to head home to try this out. maybe I'm just a step away from getting this whole thing to work!
Thank you for your help!! I will respond if I have any issues!
yungzhvo said:
Thank you for replying so quickly! :good:
Do you happen to know if this will automatically upgrade me to the newest OTA upgrade?
I want to stay on 5.1.1 so I can try to root it properly. And I've been delaying the OTA upgrade since day 1 and still doing so even with the supposed root I have on my phone right now.
Click to expand...
Click to collapse
As long as you use the stock firmware from SamMobile and follow the directions in the video, EXACTLY ......... don't take any shortcuts. You will need to join SamMobile to get the download but its simple and free.
kkretch said:
As long as you use the stock firmware from SamMobile and follow the directions in the video, EXACTLY ......... don't take any shortcuts. You will need to join SamMobile to get the download but its simple and free.
Click to expand...
Click to collapse
Hey! Thank you for the advice!
I downloaded the firmware from @hsbadr ! Will that work? Or is it better for me to download it from SamMobile? I want to make sure I don't do anything incorrectly.
p.s. have you already rooted your phone?
yungzhvo said:
Hey! Thank you for the advice!
I downloaded the firmware from @hsbadr ! Will that work? Or is it better for me to download it from SamMobile? I want to make sure I don't do anything incorrectly.
p.s. have you already rooted your phone?
Click to expand...
Click to collapse
SamMobile is very reliable but if you trust your source then you should be OK. I have done the root thing many times years ago but I'm happy with stock firmware and I need my devices to work without issue so I leave well enough alone.
I rooted my a325m by patching the stock AP file with magisk, had to use FRP hijacker by hagard to be able to flash the patched file. I root uninstalled several apps for debloating. The phone worked fine for like a couple of weeks, and now, suddenly I find there's the no SIM indication, and in settings -> about phone it says IMEI: unknown, and in software information it says bandbase version: unknown.
The firmware version I used was exactly the same as when I bought it, A325MUBU2AUJ4, with the right csc (ARO in my case).
EDIT: after a couple reboots, the bandbase version now shows, but still no IMEI or SIM detected.
Can anyone help me? What happened? What can I do? Thanks in advance!
flash all the with odin the correct rom. the twrp unstable and more like shell and who knows what bugs have magisk. until why have a good recovery i would no root my phone reallly if you want to unisstall the software from samsung and google i would say to use the universal debload https://github.com/0x192/universal-android-debloater.
UPDATE: it got unknown baseband againI
I relocked the bootloader and now in download mode I have an option to "show barcodes" pressing the side button. The barcodes show the right IMEI and serial number. Maybe stuff wasn't erased, just inaccesible by the rom?
I was told by a technician to flash the original ROM (already did) then root again. Tried several versions but not an older bandbase because downgrade is forbidden by the bootloader, apparently, to no avail. Would try a newer baseband but i'm afraid it will not work and will be unable to go back to the origial baseband version.
Weird thing is, there is the EFS directory but no /data/nvram or /dev/nvram
Same happened to me.
I tried everything I could think of to get the IMEI back and couldn't.
It was still under warranty and I took it to Samsung.
Before taking it I unrooted it and locked it again.
They fixed it for me with no problem.
edukardo said:
Same happened to me.
I tried everything I could think of to get the IMEI back and couldn't.
It was still under warranty and I took it to Samsung.
Before taking it I unrooted it and locked it again.
They fixed it for me with no problem.
Click to expand...
Click to collapse
How did you root it?
as I understand, after rooting, warranty is void since it implies flashing a magisk patched boot image or AP tar. In my case I was indeed able to relock the bootloader and flash the original firmware but upon entering download mode, it shows "warranty void 0x01".
was it the same in your case?
Flashed original firmware, relocked phone, and then went to Samsung Office. I had no problem with it
edukardo said:
Flashed original firmware, relocked phone, and then went to Samsung Office. I had no problem with it
Click to expand...
Click to collapse
most likely the warranty vod bit was on (you can check it yoursef by entering odin mode) and they didn't notice
so you got it fixed for free?
did they mention what did the fix consist in? I heard they say they change the motherboard, which is a lie, they just write the nvram or efs with the right stuff
ah sos de argentina? lol where did you take it? to a samsung store? I'm from neuquen and got it at musimundo, but here's a samgung store too
myself i was thinking of waiting for an update which should be soon, lock bootloader, flash some official rom and pull off the cable so it gives an upgrade error and doesn't enter download mode, then take it to the store
Unroot before update and unlock
wipe the cache partition . then reset the phone using recovery mode . this is at you own risk .
did you fix it?
applesucksLmao said:
did you fix it?
Click to expand...
Click to collapse
nope, went to samsung, got rejected cause warranty bit on, no choice but take it to a service and I suppose they could do something with Chimera Tool, Z3X or something like that, which, as I've seen, claims to fix it in minutes (and the client gets charged handsomely, like 100 USD)
From Samsung I got the same bullsh*t I read in some threads: "this phone has been tampered with and it's a hardware problem, the board must be replaced"
For the technically savvy, I got a strange Magisk log which kind of looks like it may be the problem. It seems to try to "unlock"* some devices on bootup but gets "permission denied". One of them may be the nvram or something like that. I have an EFS directory but no NVRAM directory anywhere or /dev/nvram.
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
i saw that auh firmware causes empty imei in another thread and to flash aug, maybe you could try this? https://forum.xda-developers.com/t/has-anyone-successfully-rooted-this-a32-4g.4326193/post-85788523
applesucksLmao said:
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
Click to expand...
Click to collapse
or atleast use magisk with aug or even older firmware if you can... is your a32 A325M or A325F?
well, your firmware is A325MUB"U2"AUJ4 and that means u cant downgrade to older versions that have binary1 so maybe you could try using samsung's new version which was released past month
applesucksLmao said:
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
Click to expand...
Click to collapse
what's JTagged?
applesucksLmao said:
i saw that auh firmware causes empty imei in another thread and to flash aug, maybe you could try this? https://forum.xda-developers.com/t/has-anyone-successfully-rooted-this-a32-4g.4326193/post-85788523
Click to expand...
Click to collapse
I found it impossible to downgrade, download mode doesn't allow it. Couldn't find a tutorial to do it either.
applesucksLmao said:
well, your firmware is A325MUB"U2"AUJ4 and that means u cant downgrade to older versions that have binary1 so maybe you could try using samsung's new version which was released past month
Click to expand...
Click to collapse
I did, I tried all combinations rooting/unrooting with the new magisk 24.1 the new version, A325MUBS2AVA1
It's a 325m btw