Second day my new A5 (2017) whent in bootloop. Without root or any modifications. I whent to recovery to do factory reset. It was desplaying error all the time. After 5 reboot's. It came back to normal. I dont know what trigerd bootloop on new phone, and why recovery dont work. If you expirience bootloop restart it for few time. It work for me. Im still not shure will i returne it.
mcvisster said:
Second day my new A5 (2017) whent in bootloop. Without root or any modifications. I whent to recovery to do factory reset. It was desplaying error all the time. After 5 reboot's. It came back to normal. I dont know what trigerd bootloop on new phone, and why recovery dont work. If you expirience bootloop restart ot for few time. It work for me. Im still not shure will i returne it.
Click to expand...
Click to collapse
Go to samsung center and tell them
huseein A5 said:
Go to samsung center and tell them
Click to expand...
Click to collapse
Did that
mcvisster said:
Did that
Click to expand...
Click to collapse
And?
huseein A5 said:
And?
Click to expand...
Click to collapse
I did that 3min. ago . Hope i will get answer soon.
mcvisster said:
I did that 3min. ago . Hope i will get answer soon.
Click to expand...
Click to collapse
Oh tell me when you get answer coz I'm interested to buy one
huseein A5 said:
Oh tell me when you get answer coz I'm interested to buy one
Click to expand...
Click to collapse
Np
mcvisster said:
Second day my new A5 (2017) whent in bootloop. Without root or any modifications. I whent to recovery to do factory reset. It was desplaying error all the time. After 5 reboot's. It came back to normal. I dont know what trigerd bootloop on new phone, and why recovery dont work. If you expirience bootloop restart ot for few time. It work for me. Im still not shure will i returne it.
Click to expand...
Click to collapse
Np
perfect2017 said:
Np
Click to expand...
Click to collapse
NP- no problem
huseein A5 said:
Oh tell me when you get answer coz I'm interested to buy one
Click to expand...
Click to collapse
I have send them error report 2 times. Still no answer from Samsung. If they ever response i will contact you. Now A5 works fine. No problem after that one time.
mcvisster said:
I have send them error report 2 times. Still no answer from Samsung. If they ever response i will contact you. Now A5 works fine. No problem after that one time.
Click to expand...
Click to collapse
Ok thanks
mcvisster said:
Second day my new A5 (2017) whent in bootloop. Without root or any modifications. I whent to recovery to do factory reset. It was desplaying error all the time. After 5 reboot's. It came back to normal. I dont know what trigerd bootloop on new phone, and why recovery dont work. If you expirience bootloop restart it for few time. It work for me. Im still not shure will i returne it.
Click to expand...
Click to collapse
This thing happened to me. Except for me having no luck solving it. It was bootlooping all the time after turning on the cellular data, after landing back home from vacation on the airplane. Phone was stuck in a Samsung Galaxy A5 logo through customs and during the drive all the way home. I tried factory resetting it on the phone but no luck, it gave me errors in red lines and cannot wipe data or cache for that matter.
Since I've only bought phone for about 1.5 month ago, I contacted my carrier (freedom mobile) about this and they send it to get it checked, only to tell me I tampered with it through a root. Lol. I don't know what's going on, and from what I have seen, I don't think there is a root for this device (A520W) yet...
The phone is still in the cellphone repair company contracted by Samsung (called Futuretel) and have yet to get it back and deal with it.
If anyone has any insights, help let me know. I will update if anything interesting happens.
KidSukiyaki said:
This thing happened to me.
After that isue mi phone did not conect on 4g and it was losing sim signal so i brought it to service. They change battery and motherboard but damegd mi screen. Now my phone is 4.time at repair and i ask them to give me new device. Im whaiting monday to see what hapens. If you are from eu they have to repare it , no mater if you have root or no.
Click to expand...
Click to collapse
mcvisster said:
KidSukiyaki said:
This thing happened to me.
After that isue mi phone did not conect on 4g and it was losing sim signal so i brought it to service. They change battery and motherboard but damegd mi screen. Now my phone is 4.time at repair and i ask them to give me new device. Im whaiting monday to see what hapens. If you are from eu they have to repare it , no mater if you have root or no.
Click to expand...
Click to collapse
I live in Canada, and unfortunately if you root it, it voids the warranty and they will not do anything unless you pay for it.
I did NOT root my phone. I kept it stock and I am sure of it.
For my issue, the company wants to charge me for replacing the mainboard too. I think they don't believe me when I say that I did not root it. I'm glad to find someone who experience this similar problem, maybe it can gain some traction.
I am also waiting for Monday to hear back from them. And hopefully you get your new device
Click to expand...
Click to collapse
KidSukiyaki said:
mcvisster said:
I think that they wjll have lot of isues like this on a5 2017. And its conected with motherboard. But it's look like that problem somehow trip's knox. Maby they want people to pay theare problems. Dont know.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
mcvisster said:
KidSukiyaki said:
mcvisster said:
I think that they wjll have lot of isues like this on a5 2017. And its conected with motherboard. But it's look like that problem somehow trip's knox. Maby they want people to pay theare problems. Dont know.
Click to expand...
Click to collapse
I was thinking that too, but when I booted up my phone before I sent it in, my knox was at 0x0 with warranty not void. Unless they did something...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
KidSukiyaki said:
mcvisster said:
KidSukiyaki said:
I was thinking that too, but when I booted up my phone before I sent it in, my knox was at 0x0 with warranty not void. Unless they did something...
Click to expand...
Click to collapse
I got my phone broken from service. So i don't thrust samsung service. I think they are not thraind enough.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
So this is the picture they sent me saying that I rooted my phone, even though I am sure I kept it stock.
Not sure why it's displaying custom, maybe something in the mainboard triggered that.
Also the knox didn't go off. The warranty void is at 0, shouldn't I qualify for the warranty?
KidSukiyaki said:
So this is the picture they sent me saying that I rooted my phone, even though I am sure I kept it stock.
Not sure why it's displaying custom, maybe something in the mainboard triggered that.
Also the knox didn't go off. The warranty void is at 0, shouldn't I qualify for the warranty?
Click to expand...
Click to collapse
Those engineers that sent that truly are idiots. They haven't even considered the fact that the issue was caused by corruption to the system partition which would not only quite possibly cause the bootloop, but it would also fail the hash check and trip the custom flag.
You haven't tripped Knox and therefore in my opinion have not voided the warranty. If they don't have faith in the knox flag then why are they so keen to deny warranty when it IS tripped.
Irrespective of the above have you actually just tried reflashing the stock firmware?
A modified system image, corrupt or otherwise will fail the hash check and fail dmverity causing the device not to boot.
ashyx said:
Those engineers that sent that truly are idiots. They haven't even considered the fact that the issue was caused by corruption to the system partition which would not only quite possibly cause the bootloop, but it would also fail the hash check and trip the custom flag.
You haven't tripped Knox and therefore in my opinion have not voided the warranty. If they don't have faith in the knox flag then why are they so keen to deny warranty when it IS tripped.
Irrespective of the above have you actually just tried reflashing the stock firmware?
A modified system image, corrupt or otherwise will fail the hash check and fail dmverity causing the device not to boot.
Click to expand...
Click to collapse
I haven't tried yet. The phone is still with the phone company, I was afraid of reflashing stock due to possible messups that could void the warranty. I just felt that it would be wise to deal with it the idiot-proof and "official" way since I had the phone for such a short time.
I didn't think they would accuse me of rooting my phone and voiding my warranty. I'll try to call Samsung with the picture they sent and see how can they resolve it.
Worse thing is that the phone company (freedom mobile) wants to charge me $35 to get my phone back since they determined "tampering". Not a steep fine, but I'm trying not to pay it mostly out of principle, hopefully I can work this out. It's been a rocky ride with Samsung and Freedom Mobile's costumer service.
Related
Hi
I have a question before sending my HTC back for the wifi repair to HTC.
If I make a nandroid backup of my existing custom rom, then unroot the phone, when I reroot the phone once i get it back, can I simply use the nandroid backup I had made to restore everything once I have re-rooted?
Thanks
Manny
mannysroot said:
Hi
I have a question before sending my HTC back for the wifi repair to HTC.
If I make a nandroid backup of my existing custom rom, then unroot the phone, when I reroot the phone once i get it back, can I simply use the nandroid backup I had made to restore everything once I have re-rooted?
Thanks
Manny
Click to expand...
Click to collapse
Yep, ofcourse you can.
To be honest you need to re-lock your bootloader also.
And hopefully your lucky enough to be one of the people that gets a warranty fix even though your unlocked and rooted.
As many people get turned away.
Wilks3y said:
Yep, ofcourse you can.
To be honest you need to re-lock your bootloader also.
And hopefully your lucky enough to be one of the people that gets a warranty fix even though your unlocked and rooted.
As many people get turned away.
Click to expand...
Click to collapse
Ok, thanks, its worth a try
I made a nandroid backup of my stock rom and also have the boot.img for the stock rom. I assume that if I flash these 2 first and then lock the bootloader? Is that correct?
if it is correct - is it simple to lock the bootloader?
mannysroot said:
Ok, thanks, its worth a try
I made a nandroid backup of my stock rom and also have the boot.img for the stock rom. I assume that if I flash these 2 first and then lock the bootloader? Is that correct?
if it is correct - is it simple to lock the bootloader?
Click to expand...
Click to collapse
Hi, yeah thats correct mate.
Easiest way is to flash the correct RUU for you phone. Im sorry but I don't know how to get the correct RUU perhaps someone else could help.
What I do know is that you can never fully "lock" the bootloader again, it will say "Re-Locked" and not "Locked" all you can do is hope they do not check the bootloader.
Hope this helps
Wilks3y said:
Hi, yeah thats correct mate.
Easiest way is to flash the correct RUU for you phone. Im sorry but I don't know how to get the correct RUU perhaps someone else could help.
What I do know is that you can never fully "lock" the bootloader again, it will say "Re-Locked" and not "Locked" all you can do is hope they do not check the bootloader.
Hope this helps
Click to expand...
Click to collapse
If they check it and see it says relocked and then refuse to repair it is the same as me leaving it unlocked?? So i may as well leave it as it is?
Thanks
Manny
mannysroot said:
If they check it and see it says relocked and then refuse to repair it is the same as me leaving it unlocked?? So i may as well leave it as it is?
Thanks
Manny
Click to expand...
Click to collapse
TO be honest yeah, your right you may as well leave it as unlocked.
But definately return it to stock as much as poss, using the RUU or flashing the stock images etc.
Hope this helps
Wilks3y said:
TO be honest yeah, your right you may as well leave it as unlocked.
But definately return it to stock as much as poss, using the RUU or flashing the stock images etc.
Hope this helps
Click to expand...
Click to collapse
ok cool, in that case will just flash the nandroid back up of the stock img and the boot.img and leaver the bootloader unlocked - should be sufficient. should i also uninstall the clockwork mod etc?
mannysroot said:
ok cool, in that case will just flash the nandroid back up of the stock img and the boot.img and leaver the bootloader unlocked - should be sufficient. should i also uninstall the clockwork mod etc?
Click to expand...
Click to collapse
Definately, if they boot the phone and see CWM, TWRP, Titanium, SuperSU/SuperUSer they'll know straight away you are rooted.
Remove anything you possibly can that will identify a rooted unit.
Wilks3y said:
Definately, if they boot the phone and see CWM, TWRP, Titanium, SuperSU/SuperUSer they'll know straight away you are rooted.
Remove anything you possibly can that will identify a rooted unit.
Click to expand...
Click to collapse
silly question - i know what the rest are but what is TWRP?
mannysroot said:
silly question - i know what the rest are but what is TWRP?
Click to expand...
Click to collapse
Just another CWM mate.
I sent mine off for repair yesterday. The bootloader is relocked but everything else is completely stock, we'll see how it goes
Michealtbh said:
I sent mine off for repair yesterday. The bootloader is relocked but everything else is completely stock, we'll see how it goes
Click to expand...
Click to collapse
hi
if you dont mind could you update to let me know how u got on?
also how long did they say before you should get it back etc?
thanks
manny
mannysroot said:
hi
if you dont mind could you update to let me know how u got on?
also how long did they say before you should get it back etc?
thanks
manny
Click to expand...
Click to collapse
Well they haven't even received it yet, since it was only sent on Thursday. I think they said it could take up to 7 working days
Michealtbh said:
Well they haven't even received it yet, since it was only sent on Thursday. I think they said it could take up to 7 working days
Click to expand...
Click to collapse
HI
Any news on your repair?
Thanks
Manny
mannysroot said:
HI
Any news on your repair?
Thanks
Manny
Click to expand...
Click to collapse
Using their repair tracking page, the current status is "in repair" so it's looking good. The status just changed an hour ago though so there's still plenty of time for them to call with bad news.
mannysroot said:
HI
Any news on your repair?
Thanks
Manny
Click to expand...
Click to collapse
Got my tracking number so it looks like it's been fixed
Warranty VOID?
I needed to send my phone in, but I don't have the sticker on the back, or the box, and there's no way for me to get to the settings on the phone, because the screen stopped working.
Will HTC still be able to service my phone, or is the warranty considered void?
gtmaster303 said:
I needed to send my phone in, but I don't have the sticker on the back, or the box, and there's no way for me to get to the settings on the phone, because the screen stopped working.
Will HTC still be able to service my phone, or is the warranty considered void?
Click to expand...
Click to collapse
if you are looking for your serial number i think its engraved on the micro-sim tray
HTC Repair SUCKS
mannysroot said:
hi
if you dont mind could you update to let me know how u got on?
also how long did they say before you should get it back etc?
thanks
manny
Click to expand...
Click to collapse
HTC repair is bull**** just for the record. I have 4G Slides on the rest of my lines, ALL of which had to be sent in.
2 of those phones took nearly 45 [FORTY FIVE] days to get back to me. Apparently there was a hold for parts coming in from Taiwan. They wouldn't tell me which parts. They wouldn't even give me an estimate time. HTC didn't apologize or update me on my repair. I found all this out after numerous calls day after day.
But if you thought that was bad service, you'll love this...
The third phone was sent out and came back fairly quickly. Within a week. I was so happy to get my phone back.
Opened the box and GUESS WHAT?
HTC SENT ME THE WRONG PHONE
They sent me a completely different phone for a different carrier (HTC Evo 4G for Sprint). It was very beat up as well.
I swear, if it wasn't for their designs (which I love dearly) I would've dropped the company by now...
Sorry for the rant/threadjack. Thought you guys would like to hear a horror story. I'm done
does anyone know how to remove the super su app and the clockwork recovery? everything else is now back to stock as i did a nandroid back up immediately after rooting initially
thanks
manny
guys, help me pls.
i was trying to unlock my s4 mini, i managed to rrot my phone and executed regionlock away, and after the phone booted i get a message saying my phone have no sim card...i removed card, tryed new one and still have the same error,,,any ideas?
anyone on this forum?
i installed fresh rom and still have the same problem...can it be a phisical isue?
cant even acess service menu... :S help pls
Flash a stock ROM with odin.
RoyaLKurTx3 said:
Flash a stock ROM with odin.
Click to expand...
Click to collapse
hello mate, tnks for reply
i did that but i still have the no sim message when i restart the phone.
2 things i have noticed , everytime i restar the phone my date resets to 1-1-2013 00:00 and i have full network bars even with the phone saying i have no sim :S
edit: i removed the sim and started the phone without sim and the network bars are still there :S
shaca said:
hello mate, tnks for reply
i did that but i still have the no sim message when i restart the phone.
2 things i have noticed , everytime i restar the phone my date resets to 1-1-2013 00:00 and i have full network bars even with the phone saying i have no sim :S
Click to expand...
Click to collapse
Ah, then that's a hardware problem. Give it to your support centre, they should help you.
RoyaLKurTx3 said:
Ah, then that's a hardware problem. Give it to your support centre, they should help you.
Click to expand...
Click to collapse
is there any way that i can confirm thats hardware?
shaca said:
is there any way that i can confirm thats hardware?
Click to expand...
Click to collapse
If the data resets to 1-1-2013 after you reboot, it is a hardware problem.
RoyaLKurTx3 said:
If the data resets to 1-1-2013 after you reboot, it is a hardware problem.
Click to expand...
Click to collapse
one last question, what should i do to take the phone to support without losing the waranty?
shaca said:
one last question, what should i do to take the phone to support without losing the waranty?
Click to expand...
Click to collapse
If you have the warranty, that ain't a problem.. show it to them and you will get everything for free, hopefully.
If you lost your warranty, you then have to pay.
RoyaLKurTx3 said:
If you have the warranty, that ain't a problem.. show it to them and you will get everything for free, hopefully.
If you lost your warranty, you then have to pay.
Click to expand...
Click to collapse
tnks mate, ill do it. ill come back with news when i have them
Hi guys,
Yesterday I got sweaty hand palms.
My EU 815 G4 is unlocked, the official way, and I had rooted it.
Then I tried to install xposed from twrp and I did something wrong, and ended up in bootloop...
I have just updated to v20b before, and forgot to connect the phone to the PC, and allow the PC debug access before installing xposed, so i could see the phone in ADB mode, but couldn't access it.
Of course I hadn't made a backup before this - I like to cry
Just as a desperate try, when everything else had failed, i thought about using the new tool provided by shakeyabooti LG UP to flash the factory KDZ all over
I put the phone in SW. update mode by:
1. Turning off the phone
2. connecting USB cable to the PC
3. Press and hold vol. up while connecting the USB cable to the phone
Then i downloaded the v20b KDZ file, provided by Autoprime (since this was what i where allready running)
Opened LG UP, loaded the H81520B_00.kdz, marked REFURBISH
Lastly i pressed "Start" and waited for about 15-20 minutes and "TADAAAA"
The phone where up and running again... only things lost where root and TWRP
- Sharing since I'm properly not the only one ending up in this kind of mess :laugh:
Just tried it no luck :/
So just to confirm...unlocking bootloader official way does void warranty and we can not send it in for repairs?
rakinisbat said:
Just tried it no luck :/
So just to confirm...unlocking bootloader official way does void warranty and we can not send it in for repairs?
Click to expand...
Click to collapse
Indeed. Maybe you'll find a cool employee at your vendor who will still do it, but your warranty is definately void and they don't need to do anything. Depends on how acommodating the employee is. If you're stuck in a bootloop @rakinisbat just follow the steps in this thread.
And please keep in mind that there's a way to get out of bootloops 99% of the time (in fact 100% if it's a software related problem), you just have to do a good search on xda. Furthermore there's an uninstaller app for xposed in the official rovo89 thread, which you can flash via recovery and it which undos the xposed installation and your phone will boot fine (if you can access TWRP - just flash it). If you have further questions you can PM me, always happy to help
Follow_and_Feel said:
Indeed. Maybe you'll find a cool employee at your vendor who will still do it, but your warranty is definately void and they don't need to do anything. Depends on how acommodating the employee is. If you're stuck in a bootloop @rakinisbat just follow the steps in this thread.
And please keep in mind that there's a way to get out of bootloops 99% of the time (in fact 100% if it's a software related problem), you just have to do a good search on xda. Furthermore there's an uninstaller app for xposed in the official rovo89 thread, which you can flash via recovery and it which undos the xposed installation and your phone will boot fine (if you can access TWRP - just flash it). If you have further questions you can PM me, always happy to help
Click to expand...
Click to collapse
Thanks Mate, I guess ill have to try my luck with LG,
I have that batch of H815 with the faulty motherboard, unfortunately I'm in that 1% *Sigh* :crying:
Tried literally everything i could with the software, pretty much confirmed it is the motherboard.
It looks like the KDZ is flashing properly, as LGUP shows whichever kdz i put on, but the actual hardware is not capable of booting into the OS.
rakinisbat said:
Thanks Mate, I guess ill have to try my luck with LG,
I have that batch of H815 with the faulty motherboard, unfortunately I'm in that 1% *Sigh* :crying:
Tried literally everything i could with the software, pretty much confirmed it is the motherboard.
It looks like the KDZ is flashing properly, as LGUP shows whichever kdz i put on, but the actual hardware is not capable of booting into the OS.
Click to expand...
Click to collapse
Ugh, okay that's bad luck. Sorry to hear. If it's a motherboard problem I can't help you unfortunately Sorry for that. What is exactly happening when you try to flash via LGUP? Just curious
Follow_and_Feel said:
Ugh, okay that's bad luck. Sorry to hear. If it's a motherboard problem I can't help you unfortunately Sorry for that. What is exactly happening when you try to flash via LGUP? Just curious
Click to expand...
Click to collapse
It flashed perfectly fine, once completed it reboots and just literally sits on the LG logo.....FOREVER or till the battery dies.
So much disappointment in LG
rakinisbat said:
It flashed perfectly fine, once completed it reboots and just literally sits on the LG logo.....FOREVER or till the battery dies.
So much disappointment in LG
Click to expand...
Click to collapse
Oh yeah that really sounds like a hardware problem. Damn it LG! But is your bootloader still locked? You might have a chance to get a new one if it is And if it's a hardware prob you still have your warranty, haven't you?
Follow_and_Feel said:
Oh yeah that really sounds like a hardware problem. Damn it LG! But is your bootloader still locked? You might have a chance to get a new one if it is And if it's a hardware prob you still have your warranty, haven't you?
Click to expand...
Click to collapse
Nope, my bootloader is unlocked, im a flash-a-holic, longest i have lasted without rooting or unlocking a bootloader is about 2 weeks. I would have never imagined such a massive hardware issue with a flagship phone. I'll probably get a nexus 6P atleast it has better support than a LG. I'm in Australia, I imported this phone when it was released, so i have to send this phone overseas if i want it repaired, which they will most likely deny.
Sooooo over LG now! There are like hundreds if not thousands that are effected they are not even acknowledging it or providing a viable solution.
rakinisbat said:
Nope, my bootloader is unlocked, im a flash-a-holic, longest i have lasted without rooting or unlocking a bootloader is about 2 weeks. I would have never imagined such a massive hardware issue with a flagship phone. I'll probably get a nexus 6P atleast it has better support than a LG. I'm in Australia, I imported this phone when it was released, so i have to send this phone overseas if i want it repaired, which they will most likely deny.
Sooooo over LG now! There are like hundreds if not thousands that are effected they are not even acknowledging it or providing a viable solution.
Click to expand...
Click to collapse
Haha! I can completely subscribe to the flash-a-holic :laugh: Well ok. So it's even worse than i thought Sorry for ya. At least you live on a continent everyone here desires to go to :laugh: Going to Australia is very popular in germany But sorry that you're experiencing trouble with your LG. Good luck with that nexus - it's an awesome phone, too. Bye bye
I've got the bootloop issue. Phone was turning on or not, just vibrating etc. I've dissassembled it, assembled again and it started working don't know why...Now I've flashed CM I was on Genisis ROM earlier maybe that was the issue
zwodziarz said:
I've got the bootloop issue. Phone was turning on or not, just vibrating etc. I've dissassembled it, assembled again and it started working don't know why...Now I've flashed CM I was on Genisis ROM earlier maybe that was the issue
Click to expand...
Click to collapse
Hi sir
I decide to buy lg g4.
If i flash cm ,bootloop not happend again?
Thank you
It doesn't matter what firmware you have got. Bootloop is happening because of hardware failure.
Odesláno z mého LG-H815 pomocí Tapatalk
My son wanted to root his brand new phone. i have rooted 8 phones from different phones before with success..... but this time i f***d up...
Accedently installed this on his phone.
http://wccftech.com/flash-and-root-nexus-5-on-android-6-0-1-mmb29k/
executed flash-all.bat and it flashed the bootloader.
For the wrong phone...
It should have been this one..
http://wccftech.com/flash-and-root-nexus-5x-android-6-0-1/
Missed the X......
Now the phone will not even boot any more at all....cant enter bootloader.......does not power up at all.!!!
Jesus...what have i done.......
It here any chance at all to fix this somehow?
Hello and thank you for using Q/A,
because you can't enter bootloader, you can't do anything. You can try to send the phone to Google. Say: It didn't boot after OTA Update.
Kind regards
Trafalgar Square
Yeah it's most likely a paperweight. Try sending it to Google. Flashing the wrong firmware destroys a phone as you probably already know
well
hopesrequiem said:
Yeah it's most likely a paperweight. Try sending it to Google. Flashing the wrong firmware destroys a phone as you probably already know
Click to expand...
Click to collapse
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Only thing I know to use is a riff box to jtag it. Not sure if they have one for 5x.
crowhater said:
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Click to expand...
Click to collapse
Your use of the period seems rather condescending. And no, you as the end user cannot fix that. You did one of the few things that is unrecoverable unless you manage to get the bootloader to accept adb commands somehow.
crowhater said:
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Click to expand...
Click to collapse
Didn't you say the phone won't turn on? The above scenario is not possible.
Well
bobby janow said:
Didn't you say the phone won't turn on? The above scenario is not possible.
Click to expand...
Click to collapse
Well. the bootloader is flashed into the phone from the beginning aswell during manufacturing. I work with electronics and software and i know there is always a way to reflash the bootloader. All the electronics comes in the beginning with no software at all, one only needs the proper software/hardware. Most probably by jtag....or if they have some other special tool for snapdragon 808.
Stupid of me not to see that the version i flashed was not for nexus 5X...and only for nexus 5
sight...
Good luck. Will Google not rma it?
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