I dont think the 3 button recovery mode "fix" that samsung released for Bell Canada i9000m and that was ported to work for other models is really a "Fix".
As dicussed in other threads, the original bug is on the PCB. It's a timing issue on the motherboard. The "fix" installs a software hook in the 4th level bootloader to the 3 buttons in order to trigger the recovery mode.
If you brick your phone such that it does not get to the 4BL stage ...
OR
If your phone freezes even after the 4BL stage ...
then you are **** out of luck.
Only a phone that had the 3BR working before the fix or a phone that gets a MB changed will be able to recover from being bricked.
This fix is only slightly better than installing a software that triggers recovery or using adb to force recovery mode. Basically it only works in conditions where you would not need recovery in the first place.
thats an assumption, but where is the proof and source?
I don't know about you but for me the recovery menu fix works great. I rooted my phone after I used that fix with the update.zip method so unless you have proves I think is better to not scary users.
I thought three limit was cause by the telco not Samsung? Read it from a post where the telco confirm they disable it.
Sent from my GT-I9000 using XDA App
The idea is I don't think Samsung replaced the motherboard of the mobile phones and the prove is that Samsung Canada or something posted a method to enable recovery mode back.
bigl666 said:
thats an assumption, but where is the proof and source?
Click to expand...
Click to collapse
I did say "I think".... but added an ? to the title.
Based my opinion on these posts:
http://forum.xda-developers.com/showpost.php?p=8217641&postcount=390
and the serious part of this one:
http://forum.xda-developers.com/showpost.php?p=8156981&postcount=287
My reply from another thread: http://forum.xda-developers.com/showthread.php?p=8230653
That was my first hypothetis when Samsung released the fix.
That's why I asked technical details and get some after contacting Samsung technical department, to finally speak with a tech, instead of those clueless helpdesk first and secondline helpdesk coworkers. But he couldn't give me more pointers, other than the original working 3br devices do not use the spl at all.
My hypothetis seems right if the bootloader gets overwritten by other firmware who's using spl on the respective partition.
My assumption, like I said before in this thread, is that the original 3br working devices gets triggered via the pcb, which loads the pbl with the safemode, if not on a dedicated module, maybe... That way, the users of such device can always be assured they can flash every firmware. This is how it's done with other many devices too. And that's exactly why I don't buy the story of 'not'-controlled batches by another guy here on the forums in another thread. I can understand why and that's why I'm so disappointed they continue to ship the phone with Android.
If you are like me, you need to test new firmware releases in order to test your own written code in Eclipse. Plus, I want the latest releases...
That's why I suggested to get your mobo replaced now you have the change, before Samsung goes with the spl fix as a standard procedure for future bricked phones.
But, for now, we will not know, unless somebody is disassembling a working 3br and a non working 3br device and have the electronic skills to confirm this.
Click to expand...
Click to collapse
blackdeath09 said:
I don't know about you but for me the recovery menu fix works great. I rooted my phone after I used that fix with the update.zip method so unless you have proves I think is better to not scary users.
Click to expand...
Click to collapse
There is no proof, if there was, there was probably a fix already or at least the technical details published.
xtrememorph said:
I thought three limit was cause by the telco not Samsung? Read it from a post where the telco confirm they disable it.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
No, I got my phone from a Samsung distro, not from any provider and it has 3br disabled.
blackdeath09 said:
The idea is I don't think Samsung replaced the motherboard of the mobile phones and the prove is that Samsung Canada or something posted a method to enable recovery mode back.
Click to expand...
Click to collapse
That could be, then if you have 3br enabled with a firmware without the integrated fix back, it's probably a new phone without replacement.
The prove that a temporary fix exist doesn't mean it's permanent, which is for the original 3br enabled devices.
So then someone should brick his phone after installed the fix and see if he can repair it back (as a user said in the original thread)
blackdeath09 said:
So then someone should brick his phone after installed the fix and see if he can repair it back (as a user said in the original thread)
Click to expand...
Click to collapse
Under what kind of circumstances?
That doesn't prove anything, other than the fix works if the sbl isn't overwritten.
Then flash back to a firmware who does without the fix and tell me the results.
I've read in http://forum.xda-developers.com/showthread.php?p=8230653 that someone flashed back and the fix is gone. Now you have your proof this fix isn't permanent, like I already said a bunch of times. I believe it was firmware JM1 if I can remember correctly. It was tested one time though. Try it and please report your results back.
Proof will come when someone bricks a phone other than by flashing firmware and can not use the 3BR combo even though the "fix" was applied.
Prroving that the "Fix" works is just about impossible. No reports of the condition described above will constitute proof that it works.
I do have an idea for a test:
- With battery fully charged, USB unplugged and phone off,
- Initiate 3BR.
- Calculate time to reach recovery screen.
Compare "fixed" phone with originally working one.
If different assume that fix is not as good as a real working 3BR phone.
My Buddy just had a bad flash and and bricked the phone.. and the recovery saved him so yes it does work....
he did not have the 3 buttons working before but did the update and started flashing roms.. and it saved him... its not a hardware issue.. its always been software.
so it does work.. if this fix didn't come out he would have a good door stop.
TriC_101 said:
My Buddy just had a bad flash and and bricked the phone.. and the recovery saved him so yes it does work....
Click to expand...
Click to collapse
Like I said, proof comes when someone recovers from a brick OTHER than because of a bad flash.
Because, in general, that doesnt touch the BL.
davidke said:
Like I said, proof comes when someone recovers from a brick OTHER than because of a bad flash.
Because, in general, that doesnt touch the BL.
Click to expand...
Click to collapse
why does it really matter? isn't that normally the problem anywayz, bricking from a bad flash?
but then again, this appears to be one of those you can't prove anything to be true, but only to be false scenarios...
TriC_101 said:
My Buddy just had a bad flash and and bricked the phone.. and the recovery saved him so yes it does work....
he did not have the 3 buttons working before but did the update and started flashing roms.. and it saved him... its not a hardware issue.. its always been software.
so it does work.. if this fix didn't come out he would have a good door stop.
Click to expand...
Click to collapse
I disagree.
Without pcb, rom and human-machine-interaction, there is no way the bootloader will load. So you are telling me it's not a hardware issue that 3br isn't working? I fully disagree. IT IS. Why? Because Android already have the recovery / download mode adressesed... Please study mobile phone architecture or at least computer architecture and how the android kernel and os works.
No one knows the exact architecture of sgs here, but one thing is for sure. 3br isn't working, because it doesn't get handled BEFORE spl... And if it is, it's disabled on purpose in bml1 and otherwise there is probably another rom, handling all 3 buttons first, before launching ipl.
Please tell your buddy to flash back to JM1 and let his phone brick and post back your results...
I hope Richthofen and / or some other members can exclude this theory by hexcomparing bml1 from working and not working 3br devices and analyze that, so we can exclude that. If it matches, then it's probably a hardware issue. Like I told you before... Android already adressed the safemode space. So the parameters must come via the 3 buttons by pcb. You are happy now?
Casio1987 said:
I hope Richthofen and / or some other members can exclude this theory by hexcomparing bml1 from working and not working 3br devices and analyze that, so we can exclude that. If it matches, then it's probably a hardware issue. Like I told you before... Android already adressed the safemode space. So the parameters must come via the 3 buttons by pcb. You are happy now?
Click to expand...
Click to collapse
It seems BML1 to BML4 that triggers 3BR recovery mode are differents between countries and could be related to CSC version.
So it seems to be a software problem.
Until you dont flash BLM/SPL everything will be fine, just check before flashing.
I find it hard to believe that it would be a hardware issue.
The first retail European I9000 phones had I9000XXJF3 factory firmware version.
As far as I know all of them had a functional 3-button "wake" function for download and recovery modes.
When Samsung started using I9000XXJM1 as a factory firmware, I have seen only one phone with a functional "3-button wake". And even with that one I could not tell if it was a brand new one or a factory refurbished one.
For some odd reason the first release using the new secondary bootloader was I9000XXJM1. All of the previous versions (from I9000XXJE2 thru I9000XWJFF) have been using the same bootloader. As far as I know none of these phones ever had problems.
Also there is no indication that Samsung would have modified the hardware.
Samsung always makes bulletin about the changes in hardware and I have not seen any. Also the hardware revision has remained the same from the start.
Richthofen said:
I find it hard to believe that it would be a hardware issue.
The first retail European I9000 phones had I9000XXJF3 factory firmware version.
As far as I know all of them had a functional 3-button "wake" function for download and recovery modes.
When Samsung started using I9000XXJM1 as a factory firmware, I have seen only one phone with a functional "3-button wake". And even with that one I could not tell if it was a brand new one or a factory refurbished one.
For some odd reason the first release using the new secondary bootloader was I9000XXJM1. All of the previous versions (from I9000XXJE2 thru I9000XWJFF) have been using the same bootloader. As far as I know none of these phones ever had problems.
Also there is no indication that Samsung would have modified the hardware.
Samsung always makes bulletin about the changes in hardware and I have not seen any. Also the hardware revision has remained the same from the start.
Click to expand...
Click to collapse
Very odd indeed, because how is it possible that some have working 3br and others not with the same firmware jm1, coming from the same csc, coming from the same batch? Maybe the 8gb differs from the 16gb (I don't think so). Maybe asked too much, but it would be great if people can start publishing all their bml's, with the exception of the containing imei.
Because the safemode must be somewhere and it isn't in bml4.
Maybe there is a special ic for it, but it's locked for the 3br disabled phones and it's overridden by the sbl.
Are you sure there isn't a special module with the safemode in it?
That would clarify why the hw still preserves the same revision.
Casio1987 said:
I disagree.
Without pcb, rom and human-machine-interaction, there is no way the bootloader will load. So you are telling me it's not a hardware issue that 3br isn't working? I fully disagree. IT IS. Why? Because Android already have the recovery / download mode adressesed... Please study mobile phone architecture or at least computer architecture and how the android kernel and os works.
No one knows the exact architecture of sgs here, but one thing is for sure. 3br isn't working, because it doesn't get handled BEFORE spl... And if it is, it's disabled on purpose in bml1 and otherwise there is probably another rom, handling all 3 buttons first, before launching ipl.
Please tell your buddy to flash back to JM1 and let his phone brick and post back your results...
Click to expand...
Click to collapse
I do know how phone architecture works and computer architecture as well....... in the end its very simple... it works its saved lots of people from having a bricked phone.. and the recovery mode is different between countries. besides you should not be flashing the SPL/BLM in the 1st place. and like you said your self you don't know how the exact architecture works on the SGS so how can you say its not a software issue. if you fully don't understand it.
Related
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
from what i have read from other forums i see that device rootkey causes the problem of stuck at logo. this is due to efs wipe or imei repair. So i am just wondering what is DRK (device rootkey) and how can it be repaired, so we can go back to fully stock ? Thanks
The only way to fix the rootkeys is to use the engineering software and serial cable. You have to send it somewhere to get fixed or if you know someone that has those those things.
Hopefully this is a lesson to you guys for flashing things you shouldn't flash. All devices can be sim unlocked from the original carrier. In the US it is the law. If you fully purchased your device then the carrier has to give you the unlock code by law. So if you guys are doing this then you are either not very informed and you went with flashing when it wasn't needed. Or you guys are trying to steal your devices without finishing the financing. Either way it is on you guys and deserve a broken device.
Same thing with trying to root bypassing knox. For those of us not in a security or government job, Knox only affects Samsung Pay. It it really worth messing up your phone just so you can use Samsung Pay? What is wrong with Android pay? It has been around for a long time. Samsung is throwing in little gimmicks. But not really worth it for me to put my banking info on yet another companies server farm. The more places you have your info the more likely you are to run into problems with data theft. All of us were already affected by this when Experian was hacked and got our T-Mobile info. Start using the brains that we were born with.
jmc302005 said:
The only way to fix the rootkeys is to use the engineering software and serial cable. You have to send it somewhere to get fixed or if you know someone that has those those things.
Click to expand...
Click to collapse
You are not right, DRK keys can be fixed without eng soft and serial cable. Keys are located in EFS partition and can be copied from other device with same model, after copy/chmod/chown - reboot and it works again.
magix01 said:
You are not right, DRK keys can be fixed without eng soft and serial cable. Keys are located in EFS partition and can be copied from other device with same model, after copy/chmod/chown - reboot and it works again.
Click to expand...
Click to collapse
I also posted that info last year. Things may have changed since then. I also don't have the S6 anymore so I am not current. So at the time my info was correct. Instead you can inform us that a new way has been found. Thanks for the info.
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
Follow and complain here.
Let ASUS know their bootloader implementation is VERY NOT FRIENDLY to us. I've been modding my Android devices since the Android 2 era and this is the first time I encountered an UNOFFICIALLY UNRECOVERABLE state which is a HORRIBLE experience.
Me? Have played with
Samsung(S5 to S9 and Tab/Odin is a good thing)
XiaomiRedmiPoco(Main device for me today, very modder friendly and robust)
Huawei(Remember when they allow applying for BL unlock?)
Apple(LOL jailbreak from A4 SoC until iPhone X(meantime Samsung S8 looks gorgeous) lost my interest)
And various small brands or exited market big brands(honorable mention Lenovo LePhone C101. My first smart device/Android and received big community support at the good old time)
ASUS. Fix your buggy BL. Fix your policy. Release everything we need to fix OUR DEVICES of OURSELVES. Just ONE step closer to perfect.
Just imagine how stupid is this:
Everytime you want to update you operating system, your UEFI/BIOS firmware might break.
And worse, that you don't have free official resources to fix it?
And can it be worse? Yes! Your Warranty is maybe void because you may unlocked bootloader, now supposedly only ASUS service center have the file to fix it.
Ha now it's interesting. That's the era of ANTITRUST. Even Apple won't do it(Worst case DFU, easily fixable using OFFICIAL iTunes).
WT*?
yeah dude i'm bricked up rn
Paid here, paid there.
Yeah sure.
Exploit people.
Perhaps instead of ranting about asus, you could tell us what you have done exactly to brick your device, and someone might be able to help you ? can you get into fastboot at all?
EDIT: quoted content removed.
Never use this firmware, because it has not been modified, 100% of fingerprints and IMEI will be lost after use. You need to modify the firmware before you can flash it.
mahdibassam said:
Perhaps instead of ranting about asus, you could tell us what you have done exactly to brick your device, and someone might be able to help you ? can you get into fastboot at all?
Click to expand...
Click to collapse
Trying to flash img unpacked from update zip. Which you should NOT do. Because Android 12 dynamic partition.
iMoc said:
Trying to flash img unpacked from update zip. Which you should NOT do. Because Android 12 dynamic partition.
Click to expand...
Click to collapse
Ok, yes you definitely should not do that
So just wondering, you went and grabbed some img files and made the decision to flash them, why is this any fault of asus?
mahdibassam said:
Ok, yes you definitely should not do that
So just wondering, you went and grabbed some img files and made the decision to flash them, why is this any fault of asus?
Click to expand...
Click to collapse
1\ The fastboot code in their bootloader have bugs, any CORRECT command you type can easily break bootloader then stuck you in 9008.
2\ The normal update method failed because THEIR UPDATER did do things wrong.
3\ They refuse to provide official ROM to let yourself fix it. SEND IT TO ME TO FIX IT, AND I MIGHT CHARGE YOU SOME.
....\
N\ You go talk to Apple about it because they are experts about saying YOU USED IT WRONG.
Anyone asked for help gets it for free so far.
All devs on my chat group agree at least fastboot flashable should be available on the official download page.
MOD EDIT: off topic content removed
Did you manage to unbrick your phone?
I managed to semi hard brick my phone. Can get into fastboot but unable to start recovery mode from fast boot and phone doesn't show up from adb devices.
I guess I'll start a new thread but any tips?
insideoft said:
Did you manage to unbrick your phone?
I managed to semi hard brick my phone. Can get into fastboot but unable to start recovery mode from fast boot and phone doesn't show up from adb devices.
I guess I'll start a new thread but any tips?
Click to expand...
Click to collapse
If you can boot into fastboot you can just flash the RAW ROM file available a few days ago. It's not bricked in this case.
Moderator Information
Hello everyone,
I have cleaned the thread from off topic contents and posts. Please focus on problem solving related discussion, not finger pointing or flaming each other. We all come here to solve the issues and learn some new stuffs.
Thanks.
iMoc said:
If you can boot into fastboot you can just flash the RAW ROM file available a few days ago. It's not bricked in this case.
Click to expand...
Click to collapse
Sorry long time ago since I was into this stuff previosly.
That fixed it, thanks for the help!
same here