I went ##786# then PRI cheksum and i got 00000000 . I s any thing wrong with it?
I unroot to stock rom 132.651.1 then i did automatically download with 3G up to 147.651.1. My PRI still in 134.003 and doesnt change to 140.003
Anyway to fix that to get 140.003 and 00000 checksum is normal?
cocobongo77 said:
I went ##786# then PRI cheksum and i got 00000000 . I s any thing wrong with it?
I unroot to stock rom 132.651.1 then i did automatically download with 3G up to 147.651.1. My PRI still in 134.003 and doesnt change to 140.003
Anyway to fix that to get 140.003 and 00000 checksum is normal?
Click to expand...
Click to collapse
once you've rooted your phone, the PRI will be 134.xxx the stock one is 140.xxx
campchi said:
once you've rooted your phone, the PRI will be 134.xxx the stock one is 140.xxx
Click to expand...
Click to collapse
I unrooted my phone to factory stock 132.651.1 and automatically download by 3G up to 147.651.1 and still in 134.003 doesnt change to 1.40
If the phone do automatically download by 3g , obviously is unrooted.
cocobongo77 said:
I unrooted my phone to factory stock 132.651.1 and automatically download by 3G up to 147.651.1 and still in 134.003 doesnt change to 1.40
If the phone do automatically download by 3g , obviously is unrooted.
Click to expand...
Click to collapse
this has been covered numerous times. It appears that if you have rooted in the past, you can not ever get pri 1.40 even if you go back to unrooted shipped rom which you did. I would be curious to know if anyone has started with the first shipped rom (RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_rele ase_171253.exe), unrooting their device, then instead of accepting the ota, flashed the second shipped rom (RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_rele ase_171253_signed.exe) to see if anything would change, then flashed the 3rd and most up to date shipped (RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_rele ase_CL195459.exe). I bet its been done already but figured I would ask.
rileyd5 said:
this has been covered numerous times. It appears that if you have rooted in the past, you can not ever get pri 1.40 even if you go back to unrooted shipped rom which you did. I would be curious to know if anyone has started with the first shipped rom (RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_rele ase_171253.exe), unrooting their device, then instead of accepting the ota, flashed the second shipped rom (RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_rele ase_171253_signed.exe) to see if anything would change, then flashed the 3rd and most up to date shipped (RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_rele ase_CL195459.exe). I bet its been done already but figured I would ask.
Click to expand...
Click to collapse
I called Sprint and explain the situation, and they give me with them a hard full reset by AIR as new and reactivate the phone and nothing. They told me go tomorow to a store tecnician and they do by wires. I dont think will be a fix, wil be same issue
I gonna do is flash the seccond 132.651.6 manually then the third one if it fixe it as you said, Let you know
cocobongo77 said:
I called Sprint and explain the situation, and they give me with them a hard full reset by AIR as new and reactivate the phone and nothing. They told me go tomorow to a store tecnician and they do by wires. I dont think will be a fix, wil be same issue
I gonna do is flash the seccond 132.651.6 manually then the third one if it fixe it as you said, Let you know
Click to expand...
Click to collapse
thanks for doing this. I guess we will see if what happens.
rileyd5 said:
thanks for doing this. I guess we will see if what happens.
Click to expand...
Click to collapse
Dammm, still same 134.003
cocobongo77 said:
Dammm, still same 134.003
Click to expand...
Click to collapse
crap... how are you flashing the shipped roms if you dont mind me asking. just running the ruu.exe? or some other method. thanks for trying man!
rileyd5 said:
crap... how are you flashing the shipped roms if you dont mind me asking. just running the ruu.exe? or some other method. thanks for trying man!
Click to expand...
Click to collapse
First i went to the bootloader page then fastboot 2) connect the usb cable 3) press fastboot until show up fastboot usb and then run the RUU.exe
Other option is using ht sync until connect then run the RUU.exe
evo4
any fix for this i have same problem
badboy22 said:
any fix for this i have same problem
Click to expand...
Click to collapse
Why not just flash 1.77 zip? It is located on the development forums.
My EVO checksum is 00000000 and it's now updated to V1.90_03.
Is this okay?
Thanks!
Related
Hey all, I originally had Damage 3.2.2 installed, had wimax update, and the new radio, everything was fine, I am now trying to restore everything back to factory with the HTC Android ROM update utility, v1.0.2.10. I plug it in, go through the steps, it starts to wipe everything, then when it starts copying files it gives me this error. So when it canceled and the phone rebooted, it was just stuck on the white evo screen and loops. I figured it was just because of the new update and all, so I was still able, (thanks god) to flash over Bugless V03. Tryed to use the utility again, and still gives the error. Can anyone help get me back to factory please? thanks for the help I would like to go get my new EVO with out any worry.
So you still have root and access to the recovery console? Odd that you are having problems restoring. Instead of using the exe file, I believe you can flash the zip file using the phones built in hboot menu instead. I don't think it will check the software version first, it's worth a shot. I think you have to name it PC36IMG.zip I think. I would find the exact info but I'm not on a pc at the moment.
Edit:
Check here too, but it's not good:
http://forum.xda-developers.com/showthread.php?t=714157
Sirchuk said:
So you still have root and access to the recovery console? Odd that you are having problems restoring. Instead of using the exe file, I believe you can flash the zip file using the phones built in hboot menu instead. I don't think it will check the software version first, it's worth a shot. I think you have to name it PC36IMG.zip I think. I would find the exact info but I'm not on a pc at the moment.
Edit:
Check here too, but it's not good:
http://forum.xda-developers.com/showthread.php?t=714157
Click to expand...
Click to collapse
I didnt use the OTA update, I flashed Damage 3.2.2, it never effected my ROOT or NAND, I just need to get it back to factory so I can return my phone for a new one. They got one waitin on me to pick up tomorrow afternoon. I have to work all day so I have to either stay up, and figure this out or, if I cant figure something out then I will have to cross my fingers when I go up there tomorrow. I have already spoke with a rep in person, he seemed cool. He looked at my phone for a good minute, scrolled through a few things, I couldnt see what it was, but he just handed it back to me and told me to just come back tomorrow at the same time, and hell swap it. I didnt realize it but I was already on a list for the phone, so Im gettin it either way I guess. I just dont want anything to happen when I go up there. Even if I could just flash over something updated or not just looked "stock" maybe I can just slip in and out.
Ahh okay. Well, look around for the zip format of the exe file in the "how to go back to stock" thread a few posts down.
Sirchuk said:
Ahh okay. Well, look around for the zip format of the exe file in the "how to go back to stock" thread a few posts down.
Click to expand...
Click to collapse
I see that thread, but all I do see is just the .exe files, no zip. There isnt just a installer like with the old version, I have the older exe, before I flashed damage3.2.2 I could easily go back to factory by running that exe and goin through the steps
Alright, this is what I was talking about, I posted it in another thread:
I think he can try restoring to factory.
Download this:
http://www.joeyconway.me/evo/stock/R...253_signed.zip
Rename it PC36IMG.zip and put it on the root of the SD card.
Turn off the phone, hold volume down and turn it on, it should boot into hboot, sort of a factory recovery
It will automatically detect the zip file and ask if you want to apply it. Select yes, and it should restore to factory.
If you continue to have problems, then there is probably something wrong with the phone and it'll need to be returned.
Click to expand...
Click to collapse
You can give that a shot I guess. There are quite a few posts today in the Q&A section with problems, and they all have one thing in common: Damage Control ROM.
Sirchuk said:
Alright, this is what I was talking about, I posted it in another thread:
You can give that a shot I guess. There are quite a few posts today in the Q&A section with problems, and they all have one thing in common: Damage Control ROM.
Click to expand...
Click to collapse
Oops! The Page Can Not Be Found!
Well sorry if I am cluttering I didnt even know that the bootloader was changed which I guess is what the problem is. I guess this is what I get for being impatient. Thanks for the help chuk. If all ells fails cross your fingers for me.
Sirchuk said:
Alright, this is what I was talking about, I posted it in another thread:
You can give that a shot I guess. There are quite a few posts today in the Q&A section with problems, and they all have one thing in common: Damage Control ROM.
Click to expand...
Click to collapse
This guy is atroll
Bootloader was updated with nw ota. Ur applying an old ruu and getting an errir, that's 100% normal you can't roll.back with ruu. Search the board for ducks sake, look at all the threads about rooting nw ota. This is there problem. Just flash another update zip first then u can ruu back.
Yup, that would do it. Hope you can get it worked out before you take it back.
fallentimm said:
This guy is atroll
Bootloader was updated with nw ota. Ur applying an old ruu and getting an errir, that's 100% normal you can't roll.back with ruu. Search the board for ducks sake, look at all the threads about rooting nw ota. This is there problem. Just flash another update zip first then u can ruu back.
Click to expand...
Click to collapse
I still have the the PCIMG zip from when I nand rooted, would that work? flash that then run the exe?
BAleR said:
I still have the the PCIMG zip from when I nand rooted, would that work? flash that then run the exe?
Click to expand...
Click to collapse
If you still have recovery flash dc 3.2. This should rest you bootlegger.
Then run a ruu.
Nooo, I think that is a different file. You can try searching for the link i tried go link that doesn't work, but I doubt it will work if you updated the boot loader. The method I was suggesting would have restored to stock, but with a newer bootloader I'm not sure what to do exactly.
Edit:
If damage control 3.2 has an older bootloader it should work, give it a go.
fallentimm said:
If you still have recovery flash dc 3.2. This should rest you bootlegger.
Then run a ruu.
Click to expand...
Click to collapse
I had a nan backup of 3.2 but I erased it like a dumbo after I was comfy with 3.2.2
If you still have NAND unlock, then try this starting at step 2. This will enable you to downgrade.
http://forum.xda-developers.com/showthread.php?t=701835 <---link
Yeeeah.... Flashed 3.2 and sent me into boot loops. I dont understand why bugless v3 would work, but not this one?
Your not nand unlocked anymore mostlikely.
Did u wipe between newer and older rom
nunyabiziz said:
If you still have NAND unlock, then try this starting at step 2. This will enable you to downgrade.
http://forum.xda-developers.com/showthread.php?t=701835 <---link
Click to expand...
Click to collapse
I dont know how to use adb, I used terminal to nand root, are you basically telling me to re-nand root?
BAleR said:
I dont know how to use adb, I used terminal to nand root, are you basically telling me to re-nand root?
Click to expand...
Click to collapse
most important part is to enable downgrade
nunyabiziz said:
most important part is to enable downgrade
Click to expand...
Click to collapse
well I am re rooting it is updating now.
BAleR said:
well I am re rooting it is updating now.
Click to expand...
Click to collapse
If it started the update without failing then you are in great shape.
Beautifully working VU2.39. Then decided to add new lock ring. Totally messed up phone.
Restored with ROM Manager to prior situation, but have totally lost phone radio (and therefore phone, 3g etc.) Have tried restoring many times, tried airplane mode, wiped cache...all with no solution.
Shows no service, no CDMA or other option exists in settings, phone info shows:
Signal Strength =0
Mobile Network Type unknown
Service state= out of service
What did I do here??? How to fix???
Have now done factory reset and called Verizon. They tried to change manual codes but to no avail. Seems my radio got fried by applying the Captain America launch ring. Is this possible that that was the cause. Worked perfectly before I patched this today.
Help! I don't want a new phone as it will come with 2.3.4 not rootable.
lair12 said:
Have now done factory reset and called Verizon. They tried to change manual codes but to no avail. Seems my radio got fried by applying the Captain America launch ring. Is this possible that that was the cause. Worked perfectly before I patched this today.
Help! I don't want a new phone as it will come with 2.3.4 not rootable.
Click to expand...
Click to collapse
2.3.4 is definitely rootable. And I don't think a ring would change that much. Have you tried flashing a New radio?
Sent from my Incredible 2 HD using XDA App
I tried flashing new radio. No difference.
I just can't believe that the sense link patch would have actually physically damaged the radio and killed the system, but I cannot get anything to "activate" the radio. In manual program mode ##778, the display settings say "radio version 1.09.01.0622", so the software should be there. But it cannot find the hardware.
I have matched my NAM settings and Home SID to the same as my wife (her phone is fine).
lair12 said:
I tried flashing new radio. No difference.
I just can't believe that the sense link patch would have actually physically damaged the radio and killed the system, but I cannot get anything to "activate" the radio. In manual program mode ##778, the display settings say "radio version 1.09.01.0622", so the software should be there. But it cannot find the hardware.
I have matched my NAM settings and Home SID to the same as my wife (her phone is fine).
Click to expand...
Click to collapse
Try flashing this Radio. It's the last one on the list.
No difference whatsoever! So what do you think has happened and how and why? How could flashing the Captain America htc unlock ring have caused such destruction?
Any how could it fry or totally immobilize the radio? I really do not want to replace the phone, but am giving up hope for a solution. It's got to be either something very simple, or the radio did get fried.
And I still don't see where I can unlock and root 2.3.4 on this forum or at the Revolutionary site.
lair12 said:
No difference whatsoever! So what do you think has happened and how and why? How could flashing the Captain America htc unlock ring have caused such destruction?
Any how could it fry or totally immobilize the radio? I really do not want to replace the phone, but am giving up hope for a solution. It's got to be either something very simple, or the radio did get fried.
And I still don't see where I can unlock and root 2.3.4 on this forum or at the Revolutionary site.
Click to expand...
Click to collapse
Well...... Was the lockring made for your specific ROM and phone? If not, that may be why.
Have you tried any other ROMs to make sure it's not just something interfering in the ROM itself?
To root 2.3.4, you have to downgrade the hboot v.98 to v.97 following these steps found here.
Link came from here: http://forum.xda-developers.com/archive/index.php/t-1135020.html
SHould this have bricked the radio??
Can you resend root 2.3.4 link, as the one above goes back to the radio instructions.
Many thanks.
lair12 said:
Link came from here: http://forum.xda-developers.com/archive/index.php/t-1135020.html
SHould this have bricked the radio??
Can you resend root 2.3.4 link, as the one above goes back to the radio instructions.
Many thanks.
Click to expand...
Click to collapse
Post edited so the link for 2.3.4 root should work. But, yeah, that's for Thunderbolt, not the DINC2. Try flashing another ROM or full wipe/reflash of VU 2.39. Don't apply any mods until you find out if it works, and see if someone can port the lockring to the DINC2.
Wiped twice regular and dalvik, installed the clean ROM for phone I had saved. DEAD Radio. Bummer, but thanks for you help.
Mobile Network Type= unknown
Service State= out of service
This has not changed with any fixes I have tried.
lair12 said:
Wiped twice regular and dalvik, installed the clean ROM for phone I had saved. DEAD Radio. Bummer, but thanks for you help.
Mobile Network Type= unknown
Service State= out of service
This has not changed with any fixes I have tried.
Click to expand...
Click to collapse
What about the .722 radio?? Earlier you said you had the .622 radio which is an older one. If that doesn't work, boot into hboot and factory reset (I think this works). Then you'll probably have to re-root. Otherwise, you can get a new phone, and root via the downgrade.
Absolutely no solutions anywhere. Tried everything twice! New phone on the way. Very frustrating situation.
lair12 said:
Absolutely no solutions anywhere. Tried everything twice! New phone on the way. Very frustrating situation.
Click to expand...
Click to collapse
Sorry to hear that.... Let us know how the rooting goes.
Sent from my Incredible 2 HD using XDA App
hey everyone ive been a long time forum lurker.. but this morning i woke up and have had major issues with my Dinc im s-off rooted and running cm7.2 all was well till this morning i have full bars of service and data but cant sms/mms or make or receive calls but i have full data access. im running the newest radio. whenever i try to call out i get a verizon message saying to turn the phone on and off again.. if the problem still exists dial #8899. HELP ME???
Thread moved. Please post in the correct section of the forum going forward as all questions belong here in Q&A.
I've just seen you also posted here in Q&A so I've deleted that post as this has more details. Please don't cross post across multiple sections, once is enough.
Thanks
AvRS
Ejames991 said:
hey everyone ive been a long time forum lurker.. but this morning i woke up and have had major issues with my Dinc im s-off rooted and running cm7.2 all was well till this morning i have full bars of service and data but cant sms/mms or make or receive calls but i have full data access. im running the newest radio. whenever i try to call out i get a verizon message saying to turn the phone on and off again.. if the problem still exists dial #8899. HELP ME???
Click to expand...
Click to collapse
Dial *228 and select option 1.
cmlusco said:
Dial *228 and select option 1.
Click to expand...
Click to collapse
Tried this a hand full of times with factory resets too nothing seems to work.. it did a weird reboot with vibrates afterwards maybe the 3 vibe brick?
Ejames991 said:
Tried this a hand full of times with factory resets too nothing seems to work.. it did a weird reboot with vibrates afterwards maybe the 3 vibe brick?
Click to expand...
Click to collapse
Have you tried restoring a known good backup, flashing a rom fresh, or doing an ruu?
cmlusco said:
Have you tried restoring a known good backup, flashing a rom fresh, or doing an ruu?
Click to expand...
Click to collapse
tried everything but an ruu.. not sure of the most current
Ejames991 said:
tried everything but an ruu.. not sure of the most current
Click to expand...
Click to collapse
Here you go, latest officially signed ruu. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip Or since your s-off, you can really do any of the ruu's found here http://dinc.does-it.net/Stock_Images/
alright thank you much hopefully this bring results.. ooh is there any benefit over the newest ruu to the others because eventually ill want to root again
Ejames991 said:
alright thank you much hopefully this bring results.. ooh is there any benefit over the newest ruu to the others because eventually ill want to root again
Click to expand...
Click to collapse
Since your s-off it dosent really matter. With s-off rooting is as easy as flashing cwm thru hboot, and then superuser thru recovery.
cmlusco said:
Since your s-off it dosent really matter. With s-off rooting is as easy as flashing cwm thru hboot, and then superuser thru recovery.
Click to expand...
Click to collapse
Thank you! you saved my phone the ruu worked... dont know why i didnt try that before. one more question for you, whats your take on custom ROMS i've been a fan of CM7 but is there anything with more stability im trying to keep this phone alive for me.
Ejames991 said:
Thank you! you saved my phone the ruu worked... dont know why i didnt try that before. one more question for you, whats your take on custom ROMS i've been a fan of CM7 but is there anything with more stability im trying to keep this phone alive for me.
Click to expand...
Click to collapse
Well not even the latest ota is 100% stable, it even has the 2am bootloop issue. However in my opinion any stock or stock based rom is going to be the most stable. I feel stock 4.06.605.2 rooted with the ota notifications stopped is the stablest you can get. But I'm sure ten other people would have 10 different opinions.
hi everyone im facing some big troubles with my bby
i made a full conversation from a HTC 10 sprint for an europe RUU
cid, mid all great but i dont have Radio..
doesnot even recognize my sim card once inserted,
cant change the network mode and dont have no imei.
i traid flashing Radios and nothing.
im runing android 7 now
can someone help me..
sorry for my bad english im from mexico.
garowl said:
hi everyone im facing some big troubles with my bby
i made a full conversation from a HTC 10 sprint for an europe RUU
cid, mid all great but i dont have Radio..
doesnot even recognize my sim card once inserted,
cant change the network mode and dont have no imei.
i traid flashing Radios and nothing.
im runing android 7 now
can someone help me..
sorry for my bad english im from mexico.
Click to expand...
Click to collapse
Probably a mismatch of boot image, firmware, ROM.
Flash Sprint N RUU to restore your radio and IMEI, then start over by installing your other new RUU and make sure to restore the Sprint radio again.
jblparisi said:
Probably a mismatch of boot image, firmware, ROM.
Flash Sprint N RUU to restore your radio and IMEI, then start over by installing your other new RUU and make sure to restore the Sprint radio again.
Click to expand...
Click to collapse
iv done almost everything, i cant find the SPRINT RADIO, do you have it?
maybe thats causing all the trouble here
Did you install 2.41.401.3 or 2.41.401.4?
The 2.41.401.3 caused some issues for Netherlands, maybe some other countries also, where IMEI disappeared. 2.41.401.4 fixed it.
garowl said:
iv done almost everything, i cant find the SPRINT RADIO, do you have it?
maybe thats causing all the trouble here
Click to expand...
Click to collapse
You didn't do what I told you. Run STROCK SPRINT RUU NOUGAT.
Then load beta TWRP and ROM of your choice.
Also, you didn't search the sprint radio, a quick search would have led to it, it's posted several places.
jblparisi said:
You didn't do what I told you. Run STROCK SPRINT RUU NOUGAT.
Then load beta TWRP and ROM of your choice.
Also, you didn't even bother searching for the sprint radio, a quick search would have led to it, it's posted several different places.
Click to expand...
Click to collapse
thankyou, yes i did a search and find it, im downloading the SPRINT RUU NOUGAT.
omar302 said:
Did you install 2.41.401.3 or 2.41.401.4?
The 2.41.401.3 caused some issues for Netherlands, maybe some other countries also, where IMEI disappeared. 2.41.401.4 fixed it.
Click to expand...
Click to collapse
im running 2.42.651.6 and imei came back but i cant get back singal, radio off.
no service, cant do any network search i noticed that airplane mode is saying turning off but never turns off
garowl said:
im running 2.42.651.6 and imei came back but i cant get back singal, radio off.
no service, cant do any network search i noticed that airplane mode is saying turning off but never turns off
Click to expand...
Click to collapse
Sorry, I don't know how to help. Maybe it is a hardware issue? If nothing else works, return to stock & send it to HTC for repair.
garowl said:
im running 2.42.651.6 and imei came back but i cant get back singal, radio off.
no service, cant do any network search i noticed that airplane mode is saying turning off but never turns off
Click to expand...
Click to collapse
After you installed the Nougat RUU, erase the modem1 and modem2 partition manually via fastboot and flash the sprint radio again. See if that helps.
jblparisi said:
After you installed the Nougat RUU, erase the modem1 and modem2 partition manually via fastboot and flash the sprint radio again. See if that helps.
Click to expand...
Click to collapse
did that to, and not worked for me
i still have my legendary m8 but im really missing my 10
Change you MID back to Sprint and run the Sprint RUU again...should fix it.
how to change mid
Sloth said:
Change you MID back to Sprint and run the Sprint RUU again...should fix it.
Click to expand...
Click to collapse
with due respect...can you kindly guide me to change MID
xperiafath said:
with due respect...can you kindly guide me to change MID
Click to expand...
Click to collapse
fastboot oem writemid ....
Fix ok if Vietnam user contact me.
Tried everything. Searched through the webs for past couple of days. Everything failed.
Majority of articles are from times of Ancient Rome. None work and are outdated.
Reflashed stock with nand erase and pit file. Checked and failed.
Tried root related solutions? Checked and failed.
Searched modem file. Failed.
Downgrade to prev version? No longer plausible. Due to BIT.
I flashed and reflashed with odin numerious of times. Nothing. Useless. Absolutely useless.
did u solve it?
Did you guys find anything? I think I'm gonna go check at a repair shop for someone with the z3x box and hope for the best.
Mighty_Rearranger said:
Did you guys find anything? I think I'm gonna go check at a repair shop for someone with the z3x box and hope for the best.
Click to expand...
Click to collapse
any luck?
dronkit said:
any luck?
Click to expand...
Click to collapse
Nope, he said no matter what rom he flashed it was always unknown IMEI.
However I found something interesting, turns out my IMEI and baseband numbers are intact when I check them from recovery. Maybe downgrading this phone should fix that, although I'm not sure if it is possible.
Mighty_Rearranger said:
Nope, he said no matter what rom he flashed it was always unknown IMEI.
However I found something interesting, turns out my IMEI and baseband numbers are intact when I check them from recovery. Maybe downgrading this phone should fix that, although I'm not sure if it is possible.
Click to expand...
Click to collapse
no, its not possible because of the bit.... can you try using an old modem to see if it solves the problem?
applesucksLmao said:
no, its not possible because of the bit.... can you try using an old modem to see if it solves the problem?
Click to expand...
Click to collapse
You mean like flashing an older modem? How can I do that?
Mighty_Rearranger said:
You mean like flashing an older modem? How can I do that?
Click to expand...
Click to collapse
its the CP file in odin
try flashing one from may or august.. don't try november or newer
You need to download an older firmware (older than november, never try that ****ty november update!) of your country's a32 and use just the cp file
applesucksLmao said:
You need to download an older firmware (older than november, never try that ****ty november update!) of your country's a32 and use just the cp file
Click to expand...
Click to collapse
I'll get an older firmware from sammobile and get back to you if anything different happens. Just as a note, someone here on XDA said they were able to downgrade when using a Magisk altered ROM.
Edit: I found something similar on another samsung phone here on XDA: thread here.
Mighty_Rearranger said:
I'll get an older firmware from sammobile and get back to you if anything different happens. Just as a note, someone here on XDA said they were able to downgrade when using a Magisk altered ROM.
Edit: I found something similar on another samsung phone here on XDA: thread here.
Click to expand...
Click to collapse
Could you flash it with a magisk modified rom?
@Mighty_Rearranger maybe you could try flashing an android 12 gsi? https://forum.xda-developers.com/t/...sing-odin-without-twrp-phh-lineageos.4114435/ I don't have the phone with me right now so I can't test it
applesucksLmao said:
You need to download an older firmware (older than november, never try that ****ty november update!) of your country's a32 and use just the cp file
Click to expand...
Click to collapse
OK I tried doing that and now phone is bootlooping with secure check fail md1img error, that's the anti-downgrade thing complaining. No luck down the downgrade hallway.
I think the only option is to wait for a possible solution from the Magisk people or check if a future update somehow fixes the problem.
Mighty_Rearranger said:
Nope, he said no matter what rom he flashed it was always unknown IMEI.
However I found something interesting, turns out my IMEI and baseband numbers are intact when I check them from recovery. Maybe downgrading this phone should fix that, although I'm not sure if it is possible.
Click to expand...
Click to collapse
how do you check them from recovery? I was able to see them once after a botched flashing, entering download mode, there was a "show barcode" option or something like that.
I have read in an older thread in this forum, some guy solved it by downgrading, but to a version which is impossible to downgrade to for us, because our phones already came with the AUJ4 firm, and acannot go back.
applesucksLmao said:
@Mighty_Rearranger maybe you could try flashing an android 12 gsi? https://forum.xda-developers.com/t/...sing-odin-without-twrp-phh-lineageos.4114435/ I don't have the phone with me right now so I can't test it
Click to expand...
Click to collapse
what's the idea? there aren't any custom roms, are there?
or you mean this way it could be possible to downgrade?
dronkit said:
what's the idea? there aren't any custom roms, are there?
or you mean this way it could be possible to downgrade?
Click to expand...
Click to collapse
if someone manages to create twrp for a32 4g maybe there's a way back
applesucksLmao said:
if someone manages to create twrp for a32 4g maybe there's a way back
Click to expand...
Click to collapse
TWRP lets you bypass the binary version check?
Mighty_Rearranger said:
TWRP lets you bypass the binary version check?
Click to expand...
Click to collapse
i don't know probably, and we could get a backup from someone with a not fricked phone and edit it to our imeis