Related
I was told to post here so:
Hi,
Yesterday I flashed a custom ROM , the rom somehow messed up my IMEI number.
Then i went back to the forum and found out that everyone who flashed the rom got his IMEI messed up and we all got the same IMEI now, i still have calls working but im afraid they will stop working soon, i know what was my original IMEI, can anyone help us please. (Heres the rom i flashed: http://forum.xda-developers.com/showthread.php?t=1034130)
I saw that the devs on samsung captivate managed to restore their imeis, there should be a way to do that to the nexus s.
Same Problem with my phone...
same here
I'm restore my backup .. and nothing change
and imei still changed :S
Same here, i think the phone is as good as network dead.
Hi all, I also was unfortunate to flash this rom resulting in the changed imei issue. My Phone was displaying emergency calls only and i was unable to connect to data services. I used Odin to flash back to stock GRH 78 ticking the phone efs clear box . After rebooting i checked my imei number but it still displays the wrong number. However my phone now connects to the network and i can make and recieve calls and data is enabled. Not a full fix and i am not sure for how long it will work but definately an improvement on the very expensive paperweight i had. Hopefully a full fix will come soon.
Trying that~!
UPDATE :
Nope Odin again didn't help.
Isn't it kinda stupid to discuss this in not only one or two but four threads? I get it, you guys want a fix and I feel with you, but having four threads will only cause confusion.
How about you all agree on one and work together to fix it instead of dividing your efforts?
Sent from my Nexus S using Tapatalk
bloodhawk said:
Trying that~!
UPDATE :
Nope Odin again didn't help.
Click to expand...
Click to collapse
Sorry to hear that worked for me. I'm in UK on vodafone network. Lets hope a solution is found real soon.
james7dean said:
Sorry to hear that worked for me. I'm in UK on vodafone network. Lets hope a solution is found real soon.
Click to expand...
Click to collapse
Can you explain what version of Odin you used - Odin3 v1.8 ??
What rom did you flash stock GRH78 ??
Did you use a .pit file and if yes which one ??
What boxes were ticked and de-ticked in Odin ??
Cheers mate
Hi,
I used odin 3v1.8 and the stock GRH 78 rom. I opened odin and loaded the
bootloader, Pda and scs files and ticked the phone efs clear box ,this was the only box i manually ticked all other boxes were left in their default state. i did not have a pit. file. Previous to using odin I had just unlocked my bootloader as it was locked. Odin won't work with bootloader locked all atempts to access download mode were met with a unlock bootloader screen.
After flashing I checked my emei no. but was disappointed to find no change. I then checked for system updates and clicked on the update which started to download. It then suddenly dawned on me that i had not linked my phone to my router and that data was enabled. I cancelled the Gingerbread update and went into notifications and saw my network instead of the previous Emergency Calls Only. A quick phone call verified that my phone was now connecting to the network. I then connected to wifi and installed the update.
I am still stuck with the wrong emei but can now connect to the network and
have restored my favourite rom from a nandroid. The only issue i now have is the
wrong emei but for now my phone functions perfectly
RisinT96 said:
Yesterday I flashed a custom ROM , the rom somehow messed up my IMEI number.
Click to expand...
Click to collapse
Probably something messed with your /efs partition.
james7dean said:
I used odin 3v1.8 and the stock GRH 78 rom. I opened odin and loaded the bootloader, Pda and scs files and ticked the phone efs clear box ...
Click to expand...
Click to collapse
Why did you have to do that? I don't assume you have a backup of /efs, do you?
james7dean said:
The only issue i now have is the wrong emei but for now my phone functions perfectly
Click to expand...
Click to collapse
I wonder how long it'll work ...
Y'all could try to look in the forums of the various Samsung Galaxy S variants, AFAIK there are ways to restore your IMEI on this kind of Samsung phone, maybe they apply to the Nexus S as well.
I have the Razr HD running stock 4.1.2, rooted, today i started getting the OTA update install requests, well i accidentally hit install, so now my phone will boot up just fine for a minute, i can even unlock it an navigate for about 20 seconds, then it automatically powers back off, an boots up into
AP Fastboot Flash Mode
device is locked, Status Code: 0
Battery OK
Connect USB data cable
failed to hab check for recovery: 0x56
Fastboot Reason: Boot Failure
Tried to boot it back up in recovery through fastboot, an get the same message. I'm not sure where to go from here, any help would be greatly appreciated. Thanks.
pintyguy said:
I have the Razr HD running stock 4.1.2, rooted, today i started getting the OTA update install requests, well i accidentally hit install, so now my phone will boot up just fine for a minute, i can even unlock it an navigate for about 20 seconds, then it automatically powers back off, an boots up into
AP Fastboot Flash Mode
device is locked, Status Code: 0
Battery OK
Connect USB data cable
failed to hab check for recovery: 0x56
Fastboot Reason: Boot Failure
Tried to boot it back up in recovery through fastboot, an get the same message. I'm not sure where to go from here, any help would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Because you installed it over a rooted phone (which is strange, as it shouldn't work) you're best bet is to flash it back to stock KK, especially if it already applied the trusted zone updates.
Of course, updating to KK 4.4.2 will then allow you to unlock your bootloader.
So, the first step is to flash to KK 4.4.2. Go here and follow the steps (it should keep your data so you won't lose what is on your internal SD card but you WILL lose all other app settings) -> http://www.droidrzr.com/index.php/topic/45494-fxz-442-1834610/
Once you have followed all the directions (read, read and read again BEFORE you attempt to do anything), then go here to root and unlock your bootloader -> http://www.droidrzr.com/index.php/topic/46155-info-status-of-root-for-kitkat-build-182183/
Hopefully, you didn't get the latest OTA, If so, you might be hosed as far as getting your bootloader unlocked, but I don't think they've pushed out the latest patch to KK for the XT926.
That should get you back up and running. Again, you will lose your app data (that is not stored on the internal SD card), but your internal and external SD cards will be left alone and intact.
I'm going to try, only problem i foresee is that i need to boot into AP Fastboot to be able to flash, but everytime I try it brings me back to the same error screen. Since that screen is technically AP Fastboot Flash Mode, Im going to try an flash it from there, but Im not sure. Will let you know what happens.
update
So I flashed the new KK as suggested, which was a process in itself, but I got it working anyways. Now I cannot get connected to the mobile network though. It shows my phone number and everything, it just says mobile network disconnected, so I can't make calls or text at all. I'm attempting to connect to T-Mobile BTW, if it makes any difference. Any ideas? Does it have anything to do with the fact that I haven't unlocked the bootloader yet? Not sure why it would, just curious.
pintyguy said:
So I flashed the new KK as suggested, which was a process in itself, but I got it working anyways. Now I cannot get connected to the mobile network though. It shows my phone number and everything, it just says mobile network disconnected, so I can't make calls or text at all. I'm attempting to connect to T-Mobile BTW, if it makes any difference. Any ideas? Does it have anything to do with the fact that I haven't unlocked the bootloader yet? Not sure why it would, just curious.
Click to expand...
Click to collapse
do you have xt926 or xt925
Sorry, but what's the difference?
1 :angel:
pintyguy said:
Sorry, but what's the difference?
Click to expand...
Click to collapse
one is a Verizon phone the other is for other carriers
does your phone have Verizon branding on it?
Yes it does
pintyguy said:
Yes it does
Click to expand...
Click to collapse
then you must have previously done the modem unlock you will need to redo it that is all
---------- Post added at 10:57 PM ---------- Previous post was at 10:54 PM ----------
pintyguy said:
Yes it does
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2389740
that should be the thread for how to do it tell us how it goes, i have no experience with this i am still on Verizon but others say after writing to the phone wait 5 minutes not seconds sorry i rembered wrong before rebooting other wise the settings will not stay
Awesome I was just about to ask for a link, thank you. And I actually got this phone pre-rooted and everything, so the guy before me must have flashed the modem. When I got it I just dropped T-Mobile sim in and it worked just fine. Luckily I'm not new to any of this, I just had a Galaxy s3 running CM11 I believe, but got rid of it and got this. Again, appreciate all the help. Gonna give it a go now and I'll report back soon.
billycar11 said:
one is a Verizon phone the other is for other carriers
does your phone have Verizon branding on it?
Click to expand...
Click to collapse
Well I'm about at my wits end on this one. I couldn't get the Moto Diag driver to correctly install to port, so I went with the RadioComm method instead. I followed a tutorial off this site, which I can't link to just yet asbi do not have enough posts. But followed it to a tee, and it seemingly was successful. But after reboot I only showed bars for about a minute, then right back to no service, T-Mobile could not be registered at this time. Nowhere in the comments or in the guide did they mention to wait the 5 minutes after writing with this method, could that possibly be why? I'm really starting to get frustrated at this point...
Alright, so after 3 days of tirelessly pouring over the forums and two different laptops, I'm finally back up and running. I couldn't get the Moto Diag drivers to correctly install to the port, on either computer, (one was running Windows XP SP3, the other Windows 7x64)so using CDMA WS was out of the question all together. I ended up following the tutorial on using RadioComm to flash the modem instead. First attempt was successful, but I immediately rebooted when it was finished writing, and apparently it didn't stick. So I went back, checked first, and it had reverted back from "00" back to "01",meaning it was locked again. So I rewrote it, and this time left it plugged in after if finished for about 10 minutes, then rebooted, and voila, back up and running, no problems since. I repeat, if you are flashing the modem, whether it be with CDMA WS, or RadioComm, YOU MUST WAIT AT LEAST 5 MINUTES AFTER FLASHING BEFORE REBOOT, otherwise it will not stick and your wasting your time. Thank you for all the help, it is very much appreciated.
Link for the RadioComm tutorial I ended up using:
http://forum.xda-developers.com/showthread.php?t=2166542
On a side note, is it really worth unlocking my bootloader? I realize I'm right at the list version where is possible, and all over the forums it's threatened "UNLOCK NOW OR STAY LOCKED FOREVER!", just curious if it's really worth the time and effort. But again, thanks to everyone who helped, and if I may assist anyone else in a similar situation feel free to ask.
pintyguy said:
Alright, so after 3 days of tirelessly pouring over the forums and two different laptops, I'm finally back up and running. I couldn't get the Moto Diag drivers to correctly install to the port, on either computer, (one was running Windows XP SP3, the other Windows 7x64)so using CDMA WS was out of the question all together. I ended up following the tutorial on using RadioComm to flash the modem instead. First attempt was successful, but I immediately rebooted when it was finished writing, and apparently it didn't stick. So I went back, checked first, and it had reverted back from "00" back to "01",meaning it was locked again. So I rewrote it, and this time left it plugged in after if finished for about 10 minutes, then rebooted, and voila, back up and running, no problems since. I repeat, if you are flashing the modem, whether it be with CDMA WS, or RadioComm, YOU MUST WAIT AT LEAST 5 MINUTES AFTER FLASHING BEFORE REBOOT, otherwise it will not stick and your wasting your time. Thank you for all the help, it is very much appreciated.
Link for the RadioComm tutorial I ended up using:
http://forum.xda-developers.com/showthread.php?t=2166542
On a side note, is it really worth unlocking my bootloader? I realize I'm right at the list version where is possible, and all over the forums it's threatened "UNLOCK NOW OR STAY LOCKED FOREVER!", just curious if it's really worth the time and effort. But again, thanks to everyone who helped, and if I may assist anyone else in a similar situation feel free to ask.
Click to expand...
Click to collapse
it is worth it also i told you about the 5 minute thing
billycar11 said:
it is worth it
Click to expand...
Click to collapse
I thought I was going to lose my data, didn't realize motopoc would do it without losing everything, so I figured might as well.
I want to flash my Cricket Moto G (xt1045) 4.4.4 to the retail 4.4.4 version for a few reasons. Mainly to get access to tethering and the chance that I will be able to update to Lollipop since my hope of cricket releasing the update is fading.
I've been searching around and cannot find a definite answer to this. Lots of people say it should work but I have yet to find anyone who successfully did so. Some say to flash all files but the bootloader and it should be good while others say being the official Motorola firmware everything will flash without a problem.
Has anyone took the plunge and tried it? I would, but I really don't want to be stuck with my Lumia 520 backup phone if I screw something up. Thanks!
macgi77 said:
I want to flash my Cricket Moto G (xt1045) 4.4.4 to the retail 4.4.4 version for a few reasons. Mainly to get access to tethering and the chance that I will be able to update to Lollipop since my hope of cricket releasing the update is fading.
I've been searching around and cannot find a definite answer to this. Lots of people say it should work but I have yet to find anyone who successfully did so. Some say to flash all files but the bootloader and it should be good while others say being the official Motorola firmware everything will flash without a problem.
Has anyone took the plunge and tried it? I would, but I really don't want to be stuck with my Lumia 520 backup phone if I screw something up. Thanks!
Click to expand...
Click to collapse
Anyone? I found a link with instructions but I can't post it until I have 10 posts. If anyone wants to try it, search for "viraj's flash stock rom lock bootloader moto g"
macgi77 said:
Anyone? I found a link with instructions but I can't post it until I have 10 posts. If anyone wants to try it, search for "viraj's flash stock rom lock bootloader moto g"
Click to expand...
Click to collapse
http://dev-viraj.blogspot.in/2015/01/flash-stock-rom-firmware-lock.html
Is that the page? His instructions and ROM download seem to be for a XT1068, not a XT1045. Did you find the ROM files for a 1045 somewhere? I'd like to get access to wifi tethering, too...
Yes, that is the page. I'm assuming the software install would be the same for all models in the Moto G group. The ROM files are located in a thread on here titled "Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)"
Would post a link, but I'm still not allowed.
macgi77 said:
Yes, that is the page. I'm assuming the software install would be the same for all models in the Moto G group. The ROM files are located in a thread on here titled "Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)"
Would post a link, but I'm still not allowed.
Click to expand...
Click to collapse
Link for those looking for it.
Thanks for the link. Maybe I will give this a try, I'm buying an android stereo for my car and need wifi tethering to run the GPS.
If you wind up trying it before I do, let us know! This would theoretically only update the ROM, we'd still be stuck with a locked bootloader, right? If we could find a 4.4.2 ROM, then the Sunshine S-off unlock would work, and we'd be set.
RonnieTheBear said:
Link for those looking for it.
Thanks for the link. Maybe I will give this a try, I'm buying an android stereo for my car and need wifi tethering to run the GPS.
If you wind up trying it before I do, let us know! This would theoretically only update the ROM, we'd still be stuck with a locked bootloader, right? If we could find a 4.4.2 ROM, then the Sunshine S-off unlock would work, and we'd be set.
Click to expand...
Click to collapse
No problem. I will report back if I try, you do the same if you beat me to it! Yes, the bootloader would still be locked, but the software should install since it is an official Motorola signed software. I think I recall reading somewhere that flashing to 4.4.2 would not allow unlocking through sunshine though.
macgi77 said:
No problem. I will report back if I try, you do the same if you beat me to it! Yes, the bootloader would still be locked, but the software should install since it is an official Motorola signed software. I think I recall reading somewhere that flashing to 4.4.2 would not allow unlocking through sunshine though.
Click to expand...
Click to collapse
macgi , I gave this a try last night and the results were extremely not good. Wasn't able to flash the retail firmware, got a bunch of "prevalidation flash failed" on some items, but not others, and then it wouldn't boot. Tried to reflash the cricket firmware to revert back, and got the same prevalidation error for the boot image and the partition gpt.bat file, and now I can't get past the fastboot screen.
RonnieTheBear said:
macgi , I gave this a try last night and the results were extremely not good. Wasn't able to flash the retail firmware, got a bunch of "prevalidation flash failed" on some items, but not others, and then it wouldn't boot. Tried to reflash the cricket firmware to revert back, and got the same prevalidation error for the boot image and the partition gpt.bat file, and now I can't get past the fastboot screen.
Click to expand...
Click to collapse
That sucks. That was the only thing keeping me from trying, the process of fixing it if something screwed up. Hopefully someone has an idea how to fix it since I'm not quite and expert in recoveries.
Thanks for reporting back though!
macgi77 said:
That sucks. That was the only thing keeping me from trying, the process of fixing it if something screwed up. Hopefully someone has an idea how to fix it since I'm not quite and expert in recoveries.
Thanks for reporting back though!
Click to expand...
Click to collapse
Yeah, no problem - it's possible I messed something up in the flashing operation, but I thought you'd want to know.
RonnieTheBear said:
Yeah, no problem - it's possible I messed something up in the flashing operation, but I thought you'd want to know.
Click to expand...
Click to collapse
I'm assuming you tried using the link above? Or did you try flashing each individual file and skipping the bootloader file which was talked about in the firmware thread? (I believe it was around pages 20-30 if I recall)
Found it
@JoeSyr, maybe I'm missing something here specific to Moto G LTE, but flashing a firmware image does not require an unlocked Bootloader. I would do it manually, skip most of the steps, and only flash the system.img initially.
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
The only way you can get into serious trouble would by flashing the motoboot.img (Bootloader) and phone no longer loads fastboot mode. But even then, is there not a hardbrick mbm-ci recovery option for Moto G 4G
Click to expand...
Click to collapse
macgi77 said:
I'm assuming you tried using the link above? Or did you try flashing each individual file and skipping the bootloader file which was talked about in the firmware thread? (I believe it was around pages 20-30 if I recall)
Found it
Click to expand...
Click to collapse
I tried running the ROM Install.bat file the guy put together in the first page you/I linked to, which did attempt to flash the bootloader. It sounds like this person you're quoting is saying the flash should be operational even just flashing those three chunks of the system image file? I think those files wrote okay, but it still didn't boot. Problem might be with this other partition file i mentioned.
RonnieTheBear said:
I tried running the ROM Install.bat file the guy put together in the first page you/I linked to, which did attempt to flash the bootloader. It sounds like this person you're quoting is saying the flash should be operational even just flashing those three chunks of the system image file? I think those files wrote okay, but it still didn't boot. Problem might be with this other partition file i mentioned.
Click to expand...
Click to collapse
That's what it sounds like. Any luck restoring the phone yet?
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
RonnieTheBear said:
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
Click to expand...
Click to collapse
Good luck, let us know how you make out.
RonnieTheBear said:
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
Click to expand...
Click to collapse
Any update?
macgi77 said:
Any update?
Click to expand...
Click to collapse
I tried flashing with some more tools, different firmwares, and different combinations of commands, no luck.
I found a guy in the stock firmware thread that had the exact same problem as me, and has the same cid as my phone, cid 10, which no one else seems to have. They think it might be why the preflash validation failed.
Other users suggested that if a cricket lollipop firmware image is developed at some point in the future, that would be able to flash without error. I reached out to the user to see if he ever resolved it, but didn't get a response.
Anyway, the sense that I got is that my problems were because my cid didn't match. Is yours cid 10 as well? you can check from adb. If it's not, you might be fine attempting it.
It's been a while since I checked, but I believe it is cid 10 as well. Now just hoping cricket releases Lollipop soon.....
The lollipop release for the retail (non carrier) version just came out OTA yesterday, apparently, so hopefully Cricket is not too far behind...Though it will probably take a while to go from an OTA update to a downloadable firmware image.
I contacted Motorola tech support today, they said they would replace the phone for $75 + taxes (flashing firmware via adb fastboot voids the warranty, of course), and told me it wouldn't have the Cricket firmware on it, so worst case, i would be gaining tethering ability, best case, they might send me a variant (xt1039?) that is capable of being rooted and installing a custom ROM in addition to tether. I'll probably take this option if I'm not able to get it working once the lollipop xt1045 firmware file shows up.
That's not a bad deal. Hopefully you can get it working when lollipop comes out though. Thanks for the update!
Hi,
So I was trying to root my phone and it all went wrong. I have rooted tons of phones before, but never a Samsung (never again).
The phone will show the Samsung Boot screen, but then it either goes black, with a flashing blue LED, or it boots itself into recovery.
When I use ODIN, the flash fails at "system.img.ext4" whenever I use just the AP field. If I load all the fields in, it fails at "xbl.elf"
I got the firmware file from SamMobile, so I don't think that is the issue, but who knows. It's as if the phone no longer has an OS on it. I also tried using SmartSwitch as well, but I have no idea what the S/N on this phone is. It was originally a Sprint phone and was working fine, but I could never find the S/N. It is nowhere on the phone itself, and was not listed when I typed #*06#. All I have is the IMEI.
Finally, when it is in recovery, there is a message at the bottom that reads, "dm-verity verification failed".
Sorry for the bullet point style here, I am on mobile. If anyone can assist, I would be very grateful!
ebercon said:
Hi,
So I was trying to root my phone and it all went wrong. I have rooted tons of phones before, but never a Samsung (never again).
The phone will show the Samsung Boot screen, but then it either goes black, with a flashing blue LED, or it boots itself into recovery.
When I use ODIN, the flash fails at "system.img.ext4" whenever I use just the AP field. If I load all the fields in, it fails at "xbl.elf"
I got the firmware file from SamMobile, so I don't think that is the issue, but who knows. It's as if the phone no longer has an OS on it. I also tried using SmartSwitch as well, but I have no idea what the S/N on this phone is. It was originally a Sprint phone and was working fine, but I could never find the S/N. It is nowhere on the phone itself, and was not listed when I typed #*06#. All I have is the IMEI.
Finally, when it is in recovery, there is a message at the bottom that reads, "dm-verity verification failed".
Sorry for the bullet point style here, I am on mobile. If anyone can assist, I would be very grateful!
Click to expand...
Click to collapse
I'm new to the s7. long time lg man
on lg ussally means either ure trying to flash a non signed image or downgrade a qfused bootloader anti rollback which sprint is good for.
in dl mode after fail its not showing anything about binary and stuff in red is it
TheMadScientist420 said:
I'm new to the s7. long time lg man
on lg ussally means either ure trying to flash a non signed image or downgrade a qfused bootloader anti rollback which sprint is good for.
in dl mode after fail its not showing anything about binary and stuff in red is it
Click to expand...
Click to collapse
It does say something about binary in there. Binary 3 I believe. I'll have to try again to get the error.
ebercon said:
It does say something about binary in there. Binary 3 I believe. I'll have to try again to get the error.
Click to expand...
Click to collapse
sounds the firmware u are flashing is older than what you have on the device hence the fail
try to find newer firmware and try flashing it
download
Download official nougat from sam mobile then flash with Odin. It will definitely solve your problem
amol6630 said:
Download official nougat from sam mobile then flash with Odin. It will definitely solve your problem
Click to expand...
Click to collapse
I may try this as well. I flashed the newest firmware I could find other than Nougat and I now have it booting all the way up and then after about a minute, it loops again. It is at least further along than before.
I just remembered one detail: The original issue began when I flashed a modified boot.img to the phone during a rooting attempt. Could this be what is still causing the issue and preventing a reformatting of the phone from solving the issue? So lost with this thing...
Try with latest firmware + pit file + tick re-partition
ebercon said:
I may try this as well. I flashed the newest firmware I could find other than Nougat and I now have it booting all the way up and then after about a minute, it loops again. It is at least further along than before.
I just remembered one detail: The original issue began when I flashed a modified boot.img to the phone during a rooting attempt. Could this be what is still causing the issue and preventing a reformatting of the phone from solving the issue? So lost with this thing...
Click to expand...
Click to collapse
Sorry to revive this thread but did this work cause its currently happening to me
If your phone is an original, S/N may be engraved in the back... it's a little bit hard to note but put a spotlight near it so that you can identify it better.
hhh ^^
Hello everyone, I desperately need assistance because I think I may have soft bricked my work provided SM-A536B/DS.
What I tried to do initially is to install TWRP so I unlocked the bootloader successfully. Then, I saw different posts here on XDA where people have successfully installed cust ROMs so i tried to do that. This is when the problems started...
Right now my phone is bricked, I assume it is a soft brick because I can still get it to download mode. I did some research prior writing here, and everyone is mentioning to flash the stock ROM. That does not work.
Right now, the phone has bootloader unlocked: (Screen1)
It is asking me to lock it, so that means it's already unlocked.
Tried to access TWRP but I cannot since I get this screen when I do vol up + power: (Screen 2)
My phone was bought in Europe. I am not entirely sure whick ROM is the right one. Is there a way to check which is the right one to download? There are multiple ROMs I can download for Europe: (Screen3)
My country is not in the list so i downloaded the 2 generic for Europe. I put my phone in download mode: (Screen4)
However Odin fails everytime, no matter what files I add: (Screen5), (Screen6)
Since TWRP is not working, I locked the bootloader again to see if I could get Samsung bootloader to show up. I think i might have deleted it somehow, because I get the same thing as before when i do vol up + power. And as you can see, the bootloader is not locked: (Screen7)
I am now stuck and screwed, because this is my work phone. Any help is greatly appreciated.
psorincatalin87 said:
Hello everyone, I desperately need assistance because I think I may have soft bricked my work provided SM-A536B/DS.
What I tried to do initially is to install TWRP so I unlocked the bootloader successfully. Then, I saw different posts here on XDA where people have successfully installed cust ROMs so i tried to do that. This is when the problems started...
Right now my phone is bricked, I assume it is a soft brick because I can still get it to download mode. I did some research prior writing here, and everyone is mentioning to flash the stock ROM. That does not work.
Right now, the phone has bootloader unlocked: (Screen1)
It is asking me to lock it, so that means it's already unlocked.
Tried to access TWRP but I cannot since I get this screen when I do vol up + power: (Screen 2)
My phone was bought in Europe. I am not entirely sure whick ROM is the right one. Is there a way to check which is the right one to download? There are multiple ROMs I can download for Europe: (Screen3)
My country is not in the list so i downloaded the 2 generic for Europe. I put my phone in download mode: (Screen4)
However Odin fails everytime, no matter what files I add: (Screen5), (Screen6)
Since TWRP is not working, I locked the bootloader again to see if I could get Samsung bootloader to show up. I think i might have deleted it somehow, because I get the same thing as before when i do vol up + power. And as you can see, the bootloader is not locked: (Screen7)
I am now stuck and screwed, because this is my work phone. Any help is greatly appreciated.
Click to expand...
Click to collapse
This is why it's a bad idea to screw with work provided devices. You don't own the phone, and you will be held financially responsible for it if it's damaged or broken.
You're trying to flash the wrong firmware. You have G925F selected; your device is an A536B. The latest firmware for your device is A536BXXU4BVL2. Use Frija to download the latest firmware.
Since this is a work owned device, the only advice I will offer is this: Return the phone to stock with the correct software, re-lock the bootloader, and do not attempt to modify it as it is most likely in violation of your company's technology acceptable use policy.
V0latyle said:
This is why it's a bad idea to screw with work provided devices. You don't own the phone, and you will be held financially responsible for it if it's damaged or broken.
You're trying to flash the wrong firmware. You have G925F selected; your device is an A536B. The latest firmware for your device is A536BXXU4BVL2. Use Frija to download the latest firmware.
Since this is a work owned device, the only advice I will offer is this: Return the phone to stock with the correct software, re-lock the bootloader, and do not attempt to modify it as it is most likely in violation of your company's technology acceptable use policy.
Click to expand...
Click to collapse
Yes, this is what I am trying to do, to return to stock ROM. I downloaded A536BXXU4BVL2 for my phone, not G925F (this is what Odin uses as an example).
psorincatalin87 said:
Yes, this is what I am trying to do, to return to stock ROM. I downloaded A536BXXU4BVL2 for my phone, not G925F (this is what Odin uses as an example).
Click to expand...
Click to collapse
What version of Odin are you using?
Your bootloader is still unlocked, correct?
If you're unable to reflash the OEM firmware in Odin, I don't think there's anything else that can be done.
To be completely honest with you, I'm not sure trying to help you is worth the effort, because you did something you shouldn't be doing anyway, and any consequences you may face are entirely of your own doing.
V0latyle said:
What version of Odin are you using?
Your bootloader is still unlocked, correct?
If you're unable to reflash the OEM firmware in Odin, I don't think there's anything else that can be done.
To be completely honest with you, I'm not sure trying to help you is worth the effort, because you did something you shouldn't be doing anyway, and any consequences you may face are entirely of your own doing.
Click to expand...
Click to collapse
Yes, i know I did something bad and I learned my lesson.
I'm using Odin 3.14 and indeed, bootloader is still unlocked. I really appreciate the help!
psorincatalin87 said:
Yes, i know I did something bad and I learned my lesson.
I'm using Odin 3.14 and indeed, bootloader is still unlocked. I really appreciate the help!
Click to expand...
Click to collapse
I downloaded the firmware with Frija and I get the same issue with Odin.
psorincatalin87 said:
I downloaded the firmware with Frija and I get the same issue with Odin.
Click to expand...
Click to collapse
What options do you have checked in Odin?
V0latyle said:
What options do you have checked in Odin?
Click to expand...
Click to collapse
I haven't touched any of the options, everything is on default.
While reading this post something popped in my head.
I dont have this phone, but a Xiaomi Mi8.
When I want to adb push or sideload stuff into phone while it is in recovery or download mode, certain usb ports will work and others wont. And there is not a clear error when it's plugged to non-working usb port, just fails in the middle of a transfer with a generic error message.
Maybe totally irrelevant, just wanted to share.
nsfnd said:
While reading this post something popped in my head.
I dont have this phone, but a Xiaomi Mi8.
When I want to adb push or sideload stuff into phone while it is in recovery or download mode, certain usb ports will work and others wont. And there is not a clear error when it's plugged to non-working usb port, just fails in the middle of a transfer with a generic error message.
Maybe totally irrelevant, just wanted to share.
Click to expand...
Click to collapse
OH.MY.GOD! Thank you very much, man! I love you! I could kiss you right now, stranger!
Haha I'm glad it worked.
Hope you get better luck on your future rom adventures.
nsfnd said:
Haha I'm glad it worked.
Hope you get better luck on your future rom adventures.
Click to expand...
Click to collapse
Nah, this is my last one.
psorincatalin87 said:
Nah, this is my last one.
Click to expand...
Click to collapse
don't be that way lol, it's fun, just do it on hardware you own. get a cheap phone off ebay to play with