Title. Unlocked my bootloader Saturday, that went smoothly, but then I greedily tried to root via unofficial TWRP which caused my device to give the error boot/recovery destroyed. I managed to get back to fastboot eventually and flashed stock recovery. Tried formatting everything, wiping data and then flashing stock rom. It won't let me flash however, it just states that my version is newer. Tried flashing via TWRP as well, but that gives me error 7 and something about some partitions not being mounted correctly (product and two others.)
I am looking for someone who could upload their Firehose/rawprogram0.xml/patch0.xml and/or their gpt file.
I am also accepting tips on how to proceed with fixing this as my retailer told me that they won't cover this under warranty.
Did u ask how much would be to pay for the fix? If it's not expensive it's worth it cause seems nobody here knows how to fix it.
Did u ask much would be to pay for the fix? If it's not expensive it's worth it cause seems nobody here knows how to fix it.
Update on this one;
Contacted oppo UK on a whim, they told me that due to it being a find x2 pro it would be covered by international warranty. I had to pay for shipping by myself and return shipping to me, total cost of ~50£ (I don't live in the UK)
The phone has been repaired and i am currently waiting for it to arrive back.
They successfully repaired it and now I'm eager to see if they managed to get global firmware on it, because in the repair statement the model got listed as CPH2025 instead of PDEM30 which is the model i have.
Update#2;
Got the phone back today (finally).
It's still a PDEM30 model, bootloader still unlocked but fails safetynet checks.
Otherwise good as new, thank fck for global warranty.
Related
Can anyone help me? I have an ASUS Zenfone 6, I checked my device settings and everything from the 'about' menu at settings and it says I have a 1.16 WW firmware. When I downloaded the newest 1.18 WW firmware from support.asus.com and tried to flash it says:
Device image SKU: CUCC
OTA image SKU: WW
And the update fails
I am honestly confused to what's going on here. I thought I have WW with gapps and everything working but suddenly when I try to update I have CUCC? Oh and what's weird is that when I just got the phone SuperSU was synced from my previous phone and I just wanted to check out what happens if I open SuperSU without rooting but when SuperSU opened it asks me whether I want to update the binary normally or from CWM/TWRP! This mind you only happens if you had rooted the phone and ran SuperSU for the first time, surprisingly according to root checker I have root! JUST BY INSTALLING SUPERSU! So I was wondering if my phone was tampered before I bought it? I legally bought it new from a nearby mall with it still complete with the packaging and warranty card, so I'm really confused to what is going on.
Can anyone please please help me, do anyone else who has the WW firmware has anything like this happen when you want to flash the firmware update? I tried to force the firmware update using fastboot, nothing changed, but now my phone won't detect my SD Card and every time I open settings the phone would restart. The only way I can think of to fix this is by flashing a fresh ROM but so far I cannot find a link that has Zenfone 6 stock ROM, only the firmware. I've thought of returning the phone with the reason that I got tricked into buying a CUCC Zenfone instead of the WW that is sold on my region.
Note: I bought the phone in Indonesia and basically there are 2 warranty. One from the official ASUS and another from 'distributor', because the distributor is cheaper I bought that one thinking I'm only having a different warranty and a lack of support from ASUS officials but is it possible this distributor actually sell a modified CUCC SKU that is changed to WW? I've seen some articles/video to switch from TW/CN to WW and it kind of raised my suspicion.
S8 plus stuck in recovery with following message:
"Support SINGLE-SKU
Supported API: 3
dm-verity error
failed code : 0x02"
Is there a fix for this yet?
cheers
Matt
...? Elaborate?
What did you flash that lead to this?
dm-verity is what you usually get when you flash something incompatible, or when some insecure fw image is rejected.
Reflash the firmware using ODIN, and the latest FW package for your model / region. (in the AP box)
If you end up with DRK error afterwards, then you're boned. You need Samsung to help you out.
TL;DR: Careful when flashing stuff next time, always verify what you're flashing is for your device's model.
OP, did you found a solution to your problem? i'm asking because now i have the exact same problem as you do so i would really appreciate if you could tell me what you've done.
Comarrid92 said:
OP, did you found a solution to your problem? i'm asking because now i have the exact same problem as you do so i would really appreciate if you could tell me what you've done.
Click to expand...
Click to collapse
Took it back to Samsung and had to pay them £290 to fit a brand new board.
Out of warranty coz i rooted it.
only way out.
Gutted.
Matt
Guess the problem was that you didn't flash dm-verity bypass when u tried to root.
CoreyHUN said:
Guess the problem was that you didn't flash dm-verity bypass when u tried to root.
Click to expand...
Click to collapse
Wrong.
I did flash it, and it was rooted for about a week, but for some reason, i was bored, just potching around with my phone and decided to uncheck 'allow OEM' unlock, but forgot to re-check it before i restarted the phone...too late though...as Samsungs awesome security basically said...NO WAY...he's tinkering about with root triggered the efuse on the board and the ONLY way to fix that was a brand new board.
I'm not a newbie (hence my 371 thanks meter) when it comes to rooting phones....i've been on here since 2011 and rooted stacks of phones....HTC HD2, HTC Sensation, Desire HD, LG G2, LG G3, LG G4, HTC One-X, HTC One-x Plus, HTC Desire eye and a LOT more...Just made a silly mistake a week AFTER I rooted the phone.
I gotta be hnonest, I thought i'd miss root, but can hand on heart say....i'm not missing it one single bit.
My lovely Samsung still has 20 months warranty and i'm keeping it that way by not rooting.
LOVE my S8 Plus and to be honest, with Knox etc....I'd advise everyone not to root this EXPENSIVE beast of a phone!:good:
Matt
In some countries (like the EU ones) it is legal to modify the software on your phone, without voiding HW warranty, so if ur phone dies, and they can't prove that it is because the modification, they have to replace / repair it.
CoreyHUN said:
In some countries (like the EU ones) it is legal to modify the software on your phone, without voiding HW warranty, so if ur phone dies, and they can't prove that it is because the modification, they have to replace / repair it.
Click to expand...
Click to collapse
WRONG!
Hardware problems -> YES
Problems due to wrong use of your phone (i.e. root and phone won't do anything anymore): NO
And I do agree with Samsung: if you temper with the FW, and your phone doesn't do anything anymore -> IT'S YOUR OWN F...... FAULT ! ! !
Here's the nice big fat bill I got for repairing it.
Eeeuuurrreekkaaaaaa!
So after being presented with this error due to my own stupidity (trying to diagnose why MTP wasn't working on windows 10 and disabling Developer Options and not re-enabling OEM Unlock), I managed to get around it quite simply although at the cost of my data... BUT at least its not bricked.
The solution is simple;
1. Use SamFirm and download the latest firmware
2. Using Odin Load all the firmware options (BL, AP, CP and CSC) and in the options tab select all the checkboxes except "Flash Lock" and "T-Flash".
3. Press start and hold your breath.
Upon completion the phone may not reboot automatically so you will have to manually reboot using the Bixby, Volume Down and Power Buttons. Once rebooted you'll see it erasing the remaining userdata and finalising the re-partitioning process but a few minutes later you'll see the samsung logo and the welcome screen.
I hope this helps someone. Good Luck Peeps
I have the same problem guys but my odin isn't working the ID thing specifically the computer isn't recognising the phone.
good guys, I need a lot of help, two days ago, I had the bootloader unlocked, since it came with a firmware from last year and the operator, I installed the latest firmware to get the operator logo and installed twrp , when i went to install the sabor rom, my phone crashed, and i came across samsung's message that i can't install unofficial binaries, i was forced to reinstall the stock and get stuck in it, without telling twrp. i wanted to know, how I exceed or circumvent the kg state: prenormal. this kg state stay in download mode and never comes out again. How do I overcome this and reinstall twrp? I really need your help!
if someone has a program or charges for the service, I pay, no problem, as long as it's cheap!
DJSZPILMAN said:
good guys, I need a lot of help, two days ago, I had the bootloader unlocked, since it came with a firmware from last year and the operator, I installed the latest firmware to get the operator logo and installed twrp , when i went to install the sabor rom, my phone crashed, and i came across samsung's message that i can't install unofficial binaries, i was forced to reinstall the stock and get stuck in it, without telling twrp. i wanted to know, how I exceed or circumvent the kg state: prenormal. this kg state stay in download mode and never comes out again. How do I overcome this and reinstall twrp? I really need your help!
if someone has a program or charges for the service, I pay, no problem, as long as it's cheap!
Click to expand...
Click to collapse
there are many guides in this thread describing how to do this. please thumb thru the previous posts and im sure you will find your answer. if you dont have any luck, feel free to reply to bump this thread to the top
Apparently the only way is by paid service but I don't know which...
In case I get another phone with the latest RETUS OTA and run into the same problem where the phone will not accept the Unlock Code sent by Motorola. "FAILED (remote error)" every time. I don't know if this new OTA is the problem, or if the phone I received had a hardware or firmware problem. I posted here about that problem 2 days ago, so the history is in that thread. TIA . . .
= = = = = = = = =
SOLVED. Rollback from 40-95-9 to 40-95-6 --CANNOT-- be done. Anti-rollback "protection" prevents the 95-6 version of bootloader.img from being flashed.
NOTE: Trying to flash older firmware wipes the existing firmware, so attempting to do this will leave you with a systemless phone. If you insist on trying it yourself, BE SURE TO HAVE A COPY OF YOUR CURRENT (OR NEWER) FIRMWARE on hand.
According to my notes, at some point when I was doing OTA updates I did end up with 40-95-9; however, I suspect this update occurred after I unlocked the device. Hence, when I rolled back to the Feb version, I did not run into issues.
That said, I would NOT attempt to roll back with a stock bootloader locked device. You (likely) may run into motorola's implementation of Androids roll back protection which will prevent the device from booting. Without the 40-95-9 firmware file, I don't think it will be easy to get back to a working device. i.e. some form of blank flashing will be necessary. You might be able to recover from this, but I think it will be a headache.
Hopefully someone else will respond with some better advice/info for you.
HTH
EDIT you wrote in your other thread:
I should probably stress, I flashed the entire firmware with no problems at all.
Click to expand...
Click to collapse
but I'm not sure what you flashed. I doubt it was an older version. If you have the 40-95-9 firmware file, you might be ok to try. Just be aware you could end up with a device that is at best difficult if not impossible to unbrick.
Before flashing anything, be sure to allow OEM unlocking from developer options and get your unlock code from motorola's www site as you did previously.
Even tho it will soft brick the device, I'd flash everything from an older version. Reboot to the now hopefully older bootloader (you can check what bootloader is running with `fastboot getvar all`). If you end up with the red "No valid operating system" screen, just simultaneously hold down the power and volume down buttons until you get back to the bootloader. Assuming you can get into the bootloader (I'm not 100% cerntain that you can) from there you may be able to unlock or at least re-flash the 40-95-9 firmware to recover.
Note I have not attempted this so I can't say this will work. It's just what I would try in this situation if I didn't care about the time spent trying to recover or permanently bricking the device.
Good luck and I hope you don't have to try it.
It's just too hard to guess what might happen with the new arrangement of partitions in Android 10. I've rescued a couple of soft-bricks (Moto and Samsung believe it or not) but they were cheaper or just older. I'd rather not risk hard-bricking a phone after just shelling out $170-200 for it. (That's Swappa prices, everywere else is another $100 or so.) On older partitioning an unlocked bootloader wouldn't have made any difference in whether rollback worked or not. It was (pretty much) all about matching up bootloader versions (or digital signing for locked bootloader etc). Rollback would either work or it wouldn't.
Right now I'm trying to find a phone with something prior to 95-9 firmware. If I can't find that, I think I'll just try to talk my lady into a slightly smaller phone. She's been spoiled by the newer 6.7-6.8" phablets. I hate them myself, but this is not for me.
Thanks a bunch for trying to help.
notmyrealhandle said:
. . . in your other thread:
. . . I'm not sure what you flashed. I doubt it was an older version. If you have the 40-95-9 firmware file, you might be ok to try. Just be aware you could end up with a device that is at best difficult if not impossible to unbrick.
. . .
Click to expand...
Click to collapse
Forgot to say, I was explaining in the other thread that I had downloaded 95-9 via Lenovo's Rescue and Smart Assistant right off the bat, so I would have that for backup just in case. I did end up flashing it (the old-fashioned way, with a couple dozen fastboot commands) to see if maybe that would fix any possible glitch in the firmware. Also after trying to unlock a few more times, I reconnected to Rescue and Smart Assistant and actually ran the whole rescue deal, thus flashing 95-9 one more time.
I had also downloaded 95-6 from lolinet but didn't get the nerve to try flashing it. Android 10 on this phone is just too weird. Last year I unlocked and Magisk-rooted a Moto G Stylus 2021 on Android 10 with never a hint of a problem anywhere.
NOPE, this cannot be done. See bottom of my first post.
Hello all,
While using my S22 Ultra a few days ago, the phone locked up and automatically restarted. Upon restart, the security error message attached shows up. I attempted to flash Samsung official firmware using Odin with no luck (this phone has never had a custom OS installed). I sent the phone to a Samsung repair center and they are trying to charge me $600 to replace the PBA since the phone is out of warranty.
My question is, is this really a defective motherboard issue? I may be completely wrong but the diagnosis of a bad PBA just seems to be a cash grab.
If anyone could provide some insight, or even let me know of some other potential fixes to try, I would be very appreciative.
Thanks!
Hi, could you please provide some more details? What is the exact phone version? Did you root your phone before this happened? Were you running a custom ROM? A custom recovery?