Question [repair] Persist partition - OnePlus Nord 2 5G

Hello, After a failed update from .11 to .12 (stock), the phone did not start anymore, I did a mtk repair, the phone works perfectly except for the fingerprint reader (infinite vibration). I think this is due to a corruption of the "persist" partition, but I cannot find a solution to fix it on the Nord 2. Thanks in advance.

The Persist partition contains the unique calibration settings for the sensors on your phone. It cannot be recovered. If it's really corrupted, the only way is to send the phone back for warranty.
What do you mean by "mtk repair"?

deceirem said:
Hello, After a failed update from .11 to .12 (stock), the phone did not start anymore, I did a mtk repair, the phone works perfectly except for the fingerprint reader (infinite vibration). I think this is due to a corruption of the "persist" partition, but I cannot find a solution to fix it on the Nord 2. Thanks in advance.
Click to expand...
Click to collapse
You need to find a backup of your OWN device's persist image. If you took a TWRP backup of your phone (which you hopefully did) it will be called "persist_image.emmc.win". You should also notice that your camera won't work either.
You can use fastboot to flash it back with the command "fastboot flash persist persist_image.emmc.win"
As Raygen mentioned, if you do not have a backup of the persist partition from your own device, you need to RMA your phone.

I haven't backup, my camera work but no fingerprint :/
I wait onePlus support so, thanks a lot for help and answers

Raygen said:
The Persist partition contains the unique calibration settings for the sensors on your phone. It cannot be recovered. If it's really corrupted, the only way is to send the phone back for warranty.
What do you mean by "mtk repair"?
Click to expand...
Click to collapse
sry, I meant by flashing in "mediatek usb" mode with python.

Raygen said:
The Persist partition contains the unique calibration settings for the sensors on your phone. It cannot be recovered. If it's really corrupted, the only way is to send the phone back for warranty.
What do you mean by "mtk repair"?
Click to expand...
Click to collapse
if another user shares their persist partition, can't we just flash that?

adi1993 said:
if another user shares their persist partition, can't we just flash that?
Click to expand...
Click to collapse
Nope. The sensors would just work bad or straight not work

Related

Have IMEI, don't have mobile signal, please help...

Hello dear fellow mido users. I am trying to solve a problem here and I would very much appreciate your help on this:
I am running latest MIUI Stable Global flashed from fastboot, I have IMEI, but I don't have mobile signal. WiFi & BT works fine.
How I got here:
Bricked the phone about half a year ago
Ressurected it a week ago via connecting the pins in the back and flashing via edl.
I have unlocked it officially, as I had it unlocked before.
I have flashed TWRP & latest official RR, but it bootlooped, because my /persist partition was freaked out, so I reflashed it from the extracted fastboot ROM and I booted.
However, both my IMEIs dissappeared, and I only had the first IMEI from the back of my phone. So I calculated the second IMEI per a tutorial (from a Czech site) and restored both IMEIs via the Qualcomm QPST xqcn file, verified both IMEIs are showing up on my phone and are valid as per online IMEI checkers.
However, the signal didn't work, so I reflashed another mido device's IMEI (I have my original IMEIs backed-up) and flashed latest MIUI fastboot ROM, still no signal.
And here I am, and I am asking you for help..
If anyone can help me or at least point me in the right direction I will be eternally grateful :angel:
Bump, offering $5 PayPal to anyone who helps me restore my mobile signal.
JouzaCZ said:
Bump, offering $5 PayPal to anyone who helps me restore my mobile signal.
Click to expand...
Click to collapse
"Ressurected it a week ago via connecting the pins in the back and flashing via edl." - are you sure you didn't accidently disconnect the antenna cable from the motherboard end or from the USB board end while doing the tespoint connection to get into EDL mode?
crok.bic said:
"Ressurected it a week ago via connecting the pins in the back and flashing via edl." - are you sure you didn't accidently disconnect the antenna cable from the motherboard end or from the USB board end while doing the tespoint connection to get into EDL mode?
Click to expand...
Click to collapse
Thank you so much for your reply. I just checked, the cable wasn't disconnected, but I dis-and-reconnected it just to make sure. Still no signal.
I should mention I reflashed my original IMEI and verified that its valid once again. I am attaching links to pictures of the back of my phone disassembled if anyone can spot something wrong: PHOTOS.
Still hoping for a solution.
JouzaCZ said:
Still hoping for a solution.
Click to expand...
Click to collapse
Okay, starts to be interesting. Did you play with the band selection? Probably the band has been changed to US?
Hope you have Magisk (root) - if not please flash Magisk.
I presume ADB is already installed.
Put the phone to airplane mode.
From a PC open a cmd and issue adb shell
or start a terminal emulator on your phone
Then issue these commands in the shell
su
pm clear com.android.providers.telephony
settings put global preferred_network_mode 10
settings put global preferred_network_mode1 10
settings put global preferred_network_mode2 10
Remove airplane mode.
Restart.
Check again.
If still not works:
Start phone in fastboot mode
Issue these commands from PC cmd:
fastboot devices << just to make sure you phone is recognised
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
It will restart.
Check again.
Anyway, if you issue *#*#INFO#*#* or better known as *#*#4636#*#* in the dialer then selecting Phone 1 or Phone 2 (according to the SIM slot you want to check) in the top right or lower left there is a band-select menu (not in MIUI but in other custom ROMs) so there you are able to select the correct band if you want (that would mean you flash any custom ROM from TWRP or any custom recovery for a couple of minutes, go to dialer and look around)
crok.bic said:
Ping
Click to expand...
Click to collapse
Tried everything you said in order, still doesn't work. In normal fastboot, fastboot erase modemst1 results in this image isn't allow download. So I used mfastboot and it worked, however still no signal. When I try to switch the band in the options menu, there are two options: Automatic and United States. When clicked, both result in: Set [United States/Automatic] Unsuccessful.
And I just noticed it erased my IMEI again... Maybe the IMEI wasn't really there the whole time?
What is the proper way to flash both IMEIs? (I know them both)
JouzaCZ said:
Maybe the IMEI wasn't really there the whole time?
What is the proper way to flash both IMEIs? (I know them both)
Click to expand...
Click to collapse
I have the impression that the IMEI wasn't even there..
Flashing it is not possible.
The partition called EFS - in TWRP - is the one storing these kind of IDs.
If you have a backup of EFS you are good to go.
I used to tell people that before doing anyhing (before even unlocking the bootloader)
just do QCN info backup so in case of IMEI / Wifi MAC / Bluetooth MAC issues it's easy to restore..
Your case is a bit more advanced since you have no backup - so you have only one way to get out from this situation:
re-generate the QCN info. I advise you to use >>this<< tutorial (files are attached to the post) to properly re-generate and push back the correct info.
And here's the ultimate guide as well: part 1 and part 2
crok.bic said:
I have the impression that the IMEI wasn't even there..
Flashing it is not possible.
The partition called EFS - in TWRP - is the one storing these kind of IDs.
If you have a backup of EFS you are good to go.
I used to tell people that before doing anyhing (before even unlocking the bootloader)
just do QCN info backup so in case of IMEI / Wifi MAC / Bluetooth MAC issues it's easy to restore..
Your case is a bit more advanced since you have no backup - so you have only one way to get out from this situation:
re-generate the QCN info. I advise you to use >>this<< tutorial (files are attached to the post) to properly re-generate and push back the correct info.
And here's the ultimate guide as well: part 1 and part 2
Click to expand...
Click to collapse
Okay, I have already followed the first tutorial you linked before, so I have the xQCN files ready. I will follow the second tutorial and report back. Thank you for taking the time to help me.
JouzaCZ said:
Okay, I have already followed the first tutorial you linked before, so I have the xQCN files ready. I will follow the second tutorial and report back. Thank you for taking the time to help me.
Click to expand...
Click to collapse
After that I advise you to use MiFlash and flash a recent fastboot ROM.
Report back when you finished. There should be a way..
crok.bic said:
After that I advise you to use MiFlash and flash a recent fastboot ROM.
Report back when you finished. There should be a way..
Click to expand...
Click to collapse
Okay, I followed the first tutorial and successfully restored both IMEIs, still not working. I noticed, while flashing the xQCN file, it gives me a message about the model number of the phone not matching the model number of the xqcn file. Is that normal?
Last resort is to follow the second tutorial and redo everything.
JouzaCZ said:
gives me a message about the model number of the phone not matching the model number of the xqcn file
Click to expand...
Click to collapse
Waitaminute.. What is the error message exactly? This is odd, I used that file many times without any glitch, issue or error message.
crok.bic said:
Waitaminute.. What is the error message exactly? This is odd, I used that file many times without any glitch, issue or error message.
Click to expand...
Click to collapse
"The model number in the QCN file and the phone do not match. Do you still want to restore the phone with this file?"
JouzaCZ said:
"The model number in the QCN file and the phone do not match. Do you still want to restore the phone with this file?"
Click to expand...
Click to collapse
In fastboot mode what is the answer of the phone to the command adb devices and fastboot getvar product? I don't care about the serial but all the rest.
crok.bic said:
In fastboot mode what is the answer of the phone to the command adb devices and fastboot getvar product? I don't care about the serial but all the rest.
Click to expand...
Click to collapse
fastboot getvar product: mido
adb devices: 7e03cac30903 device
JouzaCZ said:
fastboot getvar product: mido
Click to expand...
Click to collapse
Something is not quite straight here - the QCN file there is for Mido, that's 100% sure.
You started the thread with this statemenet: "Bricked the phone about half a year ago"
What did you do exactly? Once I had a phone - remotely resurrected - that has been flashed with a markw ROM (Redmi 4X) instead of Redmi Note 4X (mido) and the guy experienced something similar.
crok.bic said:
Something is not quite straight here - the QCN file there is for Mido, that's 100% sure.
You started the thread with this statemenet: "Bricked the phone about half a year ago"
What did you do exactly? Once I had a phone - remotely resurrected - that has been flashed with a markw ROM (Redmi 4X) instead of Redmi Note 4X (mido) and the guy experienced something similar.
Click to expand...
Click to collapse
Pasting from a thread I made back when I bricked the phone:
Here's the situation:
Was on stock MIUI Global 9.5.8.0 with RedWolf Recovery.
Did a backup and flashed LineageOS
Wasnt happy with it and flashed back the backup, including the Firmware and EFS partitions, basically every partition
Bootloop, WiFi and BT driver prolly messed up, cant connect and restarts upon trying to connect to WIFI/BT.
Tried flashing other firmware, various combinations of wipes, flashes, MiFlashTool fastboot rom, nothing helped.
Tried flashing with EDL, the newest ROM gives me "Too many lines in XML file", old ROM flashed fine, but then couldn't even get to fastboot.
Now: Can't get to fastboot nor recovery, phone goes to EDL mode w/ red LED blinking when connected to PC.
QFIL gives me "Cannot read packet header, read 0 bytes", same with MiFlash.
Click to expand...
Click to collapse
JouzaCZ said:
Was on stock MIUI Global 9.5.8.0 with RedWolf Recovery.
Did a backup and flashed LineageOS
Click to expand...
Click to collapse
Do you have this backup you made with RedWolf?
JouzaCZ said:
including the Firmware and EFS partitions, basically every partition
Click to expand...
Click to collapse
Not a good move. System is up and running, tho, right?
If you go to Settings - About phone - Baseband - what is the baseband version?
Does it looks like a decent version info or say "unknown"?
crok.bic said:
Do you have this backup you made with RedWolf?
Not a good move. System is up and running, tho, right?
If you go to Settings - About phone - Baseband - what is the baseband version?
Does it looks like a decent version info or say "unknown"?
Click to expand...
Click to collapse
Don't have the backup.
Sorry for confusing you, the Now section is from the old post, I haven't done anything since my last post.
JouzaCZ said:
Pasting from a thread I made back when I bricked the phone:
Click to expand...
Click to collapse
JouzaCZ said:
Don't have the backup.
Sorry for confusing you, the Now section is from the old post, I haven't done anything since my last post.
Click to expand...
Click to collapse
No worries - but still:
If you go to Settings - About phone - Baseband - what is the baseband version?
Does it looks like a decent version info or say "unknown"?
crok.bic said:
No worries - but still:
If you go to Settings - About phone - Baseband - what is the baseband version?
Does it looks like a decent version info or say "unknown"?
Click to expand...
Click to collapse
Decent version. Specifically: 953_GEN_PACK-1.148143.1.163979.1
Also can we switch to some IM like WhatsApp so we don't have to keep pinging each other via quotes? I will post the solution/result in the thread.

Question Lost IMEI after root

Hello all, I was asking if you can help me with an issue here.
While trying to root my Nord 2, I flashed the wrong boot.img version (A.10, while I was already update at the A.11), losing my WiFi and Bluetooth. So to recover them, I flashed the Full A.07 firmware and went back up to A.11 flashing the various OTAs. After flashing the A.07 firmware though, I've lost IMEI and Cellular functionality, and was never able to recover them.
I've done a backup of my nvram, nvdata, and nvcfg partitions before flashing, but restoring them didn't solve the issue.
I've use this guide for root: https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/
And this guide to flash A.07 and OTAs: https://forum.xda-developers.com/t/oneplus-nord-2-oxygen-11-3-dn2103-eea-rom.4331695/
Does someone have any hints? Or should I send it back to Oneplus?
Raygen said:
Hello all, I was asking if you can help me with an issue here.
While trying to root my Nord 2, I flashed the wrong boot.img version (A.10, while I was already update at the A.11), losing my WiFi and Bluetooth. So to recover them, I flashed the Full A.07 firmware and went back up to A.11 flashing the various OTAs. After flashing the A.07 firmware though, I've lost IMEI and Cellular functionality, and was never able to recover them.
I've done a backup of my nvram, nvdata, and nvcfg partitions before flashing, but restoring them didn't solve the issue.
I've use this guide for root: https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/
And this guide to flash A.07 and OTAs: https://forum.xda-developers.com/t/oneplus-nord-2-oxygen-11-3-dn2103-eea-rom.4331695/
Does someone have any hints? Or should I send it back to Oneplus?
Click to expand...
Click to collapse
You done the mess even I creted simple twrp and root method you choosed the patched boot.img way and This happened.
Try to restore your full backup of nandroid using twrp. Or fist install twrp and flash non patched boot images using twrp itself
pankspoo said:
You done the mess even I creted simple twrp and root method you choosed the patched boot.img way and This happened.
Try to restore your full backup of nandroid using twrp. Or fist install twrp and flash non patched boot images using twrp itself
Click to expand...
Click to collapse
Yeah I saw there was 2 different guides, I went with the newer one but it wasn't the right choice.
Already tried flashing a stock boot image, no change. Didn't do a Nandroid backup before hand, that's my bad.
Raygen said:
Yeah I saw there was 2 different guides, I went with the newer one but it wasn't the right choice.
Already tried flashing a stock boot image, no change. Didn't do a Nandroid backup before hand, that's my bad.
Click to expand...
Click to collapse
Try all boot images and test it
File folder on MEGA
mega.nz
Must work with anyone
sakarya1980 said:
Try all boot images and test it
File folder on MEGA
mega.nz
Must work with anyone
Click to expand...
Click to collapse
Those images are the first I've tried. I've then tried with the stock boot image linked in @pankspoo post, but with still no result. My guess is that flashing V.07 on top of V.11 rewrited some others partitions that should have not be touched
Well i am not happy to tell you, but if its true that partitions containing IMEI and WiFi connections got overwritten with nonsense information then the only thing that could save your phone is full nandroid backup which you do not have. And unfortunetly dont expect anyone else to provide it as that would mean that those 2 phones would have the same IMEI and MAC address.
I would suggest that you flash stock image, lock your bootloader and send it for RMA saying that you dont know what happened. You will have like 50/50 chance that they will just replace your motherboard without much of an investigation.
Raygen said:
Those images are the first I've tried. I've then tried with the stock boot image linked in @pankspoo post, but with still no result. My guess is that flashing V.07 on top of V.11 rewrited some others partitions that should have not be touched
Click to expand...
Click to collapse
If you have europe Version of nord2, flash Version v07, then update with otas to v09, v10, v11 with twrp
@Raygen did you get through with your imei repair? i have a similar issue.
BusterCZ said:
Well i am not happy to tell you, but if its true that partitions containing IMEI and WiFi connections got overwritten with nonsense information then the only thing that could save your phone is full nandroid backup which you do not have. And unfortunetly dont expect anyone else to provide it as that would mean that those 2 phones would have the same IMEI and MAC address.
I would suggest that you flash stock image, lock your bootloader and send it for RMA saying that you dont know what happened. You will have like 50/50 chance that they will just replace your motherboard without much of an investigation.
Click to expand...
Click to collapse
Yeah, I've already contacted OnePlus and I'm waiting for an RMA.
There's just a catch: I'm not able to re-lock the bootloader without getting the "boot image is corruptd" error. But I hope it's not an issue if I send it back all stock, with just the bootloader unlocked.
sakarya1980 said:
If you have europe Version of nord2, flash Version v07, then update with otas to v09, v10, v11 with twrp
Click to expand...
Click to collapse
Tried two times already, no change.
Keden said:
@Raygen did you get through with your imei repair? i have a similar issue.
Click to expand...
Click to collapse
Send it back to OnePlus sadly.
Raygen said:
Yeah, I've already contacted OnePlus and I'm waiting for an RMA.
There's just a catch: I'm not able to re-lock the bootloader without getting the "boot image is corruptd" error. But I hope it's not an issue if I send it back all stock, with just the bootloader unlocked.
Tried two times already, no change.
Send it back to OnePlus sadly.
Click to expand...
Click to collapse
Did any way you can flash stock. Firmware using sp flash tool of mediatek just like qualcoms MSM tool used for hardbricked devices
Raygen said:
Yeah, I've already contacted OnePlus and I'm waiting for an RMA.
There's just a catch: I'm not able to re-lock the bootloader without getting the "boot image is corruptd" error. But I hope it's not an issue if I send it back all stock, with just the bootloader unlocked.
Click to expand...
Click to collapse
Well my guess is that if they take a look at it and the bootloader will be unlocked they will send it back to you rejacted. Atleast that was my expirience once with my old Xiaomi phone. So probably try flashing original firmware using some kind of recovery utility such as Sp flash to help get rid of this message?
pankspoo said:
Did any way you can flash stock. Firmware using sp flash tool of mediatek just like qualcoms MSM tool used for hardbricked devices
Click to expand...
Click to collapse
BusterCZ said:
Well my guess is that if they take a look at it and the bootloader will be unlocked they will send it back to you rejacted. Atleast that was my expirience once with my old Xiaomi phone. So probably try flashing original firmware using some kind of recovery utility such as Sp flash to help get rid of this message?
Click to expand...
Click to collapse
I would like to use Sp flash but I don't know where I could find the files for the Nord 2 to use with it. Like the scatter file and the firmware in Raw format
Keden said:
@Raygen did you get through with your imei repair? i have a similar issue.
Click to expand...
Click to collapse
Might help ! Check,.
U need to get UMT dongle , Ultimate Multi tool software.

Question Persist 2101

Guy's, i need persist from 2101. Give me please. I have broken fingerprint, camera work perfectly. Try flash persist from 2103, EVERYTHING work excluding fingerprint. I think i can fix that, but i need persist from DN2101. Help please...
I have the same problem, OP does not want to provide the rom 100%. They offered me instead to send the phone in after-sales service.
persist img is uniqe if not backed-up you're screwed. you cant use someone elses persist back-up.
try contact OP aftersales in most cases when unlocked bootloader you still have warranty at oneplus
kkdamion said:
persist img is uniqe if not backed-up you're screwed. you cant use someone elses persist back-up.
try contact OP aftersales in most cases when unlocked bootloader you still have warranty at oneplus
Click to expand...
Click to collapse
Maybe we can re-calibrate fingerprint scanner via RL-071?
The engineer code not available on nord 2. I search how to enable it, no engineermode_config in vendor
D3ATHL355 said:
Maybe we can re-calibrate fingerprint scanner via RL-071?
Click to expand...
Click to collapse
I bought the calibrator, on the other hand it would be possible to have the persist partition of another to have a test base? Mine is empty.
deceirem said:
I bought the calibrator, on the other hand it would be possible to have the persist partition of another to have a test base? Mine is empty.
Click to expand...
Click to collapse
If i right understand you, take that. That from 2101.Just unzip.
deceirem said:
I bought the calibrator, on the other hand it would be possible to have the persist partition of another to have a test base? Mine is empty.
Click to expand...
Click to collapse
Ohhh, man that just *#899#)))
What is the difference between persist partition and persist image (emmc)? is one a backup or is it complementary? (they have the same files)
deceirem said:
I bought the calibrator, on the other hand it would be possible to have the persist partition of another to have a test base? Mine is empty.
Click to expand...
Click to collapse
deceirem said:
What is the difference between persist partition and persist image (emmc)? is one a backup or is it complementary? (they have the same files)
Click to expand...
Click to collapse
Man, i don't know, but persist flash via command "fastboot flash persist persist_image.emmc.win". Or persist.img, of you want rename it.
when you backup you can clearly distinguish between persist.img(sda16) and persist_image.emmc.win. I find that strange. Both have basically the same content, different weights, with a slightly different structure.
D3ATHL355 said:
Guy's, i need persist from 2101. Give me please. I have broken fingerprint, camera work perfectly. Try flash persist from 2103, EVERYTHING work excluding fingerprint. I think i can fix that, but i need persist from DN2101. Help please...
Click to expand...
Click to collapse
Hello brother can you please provide me persist image from DN 2103 .. i have issues with camera, fingerprint
Gpsinh677 said:
Hello brother can you please provide me persist image from DN 2103 .. i have issues with camera, fingerprint
Click to expand...
Click to collapse
I dont think, that it works with the persist from another phone but if you want to try: (better make a backup of your own broken persist before flashing)
Fingerprint calibrator working?

Sprint Luns Full Backup with Last Update

Here's a full LUNS backup for the Sprint LG G8x with the last update that was pushed OTA.Enjoy!
LG V60 AT&T 30a - Google Drive
drive.google.com
Bro with this I can restore to functional a10 sprint? can this fix the problem of NTcode error?
mclarenf195 said:
Bro with this I can restore to functional a10 sprint? can this fix the problem of NTcode error?
Click to expand...
Click to collapse
Yes,and if I remember correctly that backup is A11.
thanks, I'm going to try, I imagine that it is restored with QFIL, I've tried a thousand things with several KDZ but I can't solve the ntcode error, network and fingerprint sensor error.
mclarenf195 said:
thanks, I'm going to try, I imagine that it is restored with QFIL, I've tried a thousand things with several KDZ but I can't solve the ntcode error, network and fingerprint sensor error.
Click to expand...
Click to collapse
That's stock Sprint.That will fix it all.Just copy the LUNS files in to the Qualcomm folder.
Surgemanxx said:
That's stock Sprint.That will fix it all.Just copy the LUNS files in to the Qualcomm folder.
Click to expand...
Click to collapse
Friend I have a question, should I restore the LUNS files with fh_loader how in the netmsm guide?
[Tutorial] Rescue From HARD BRICK
Don't worry! Everything's gonna be alright ;) You may accidentally erase all partitions and GPT on your phone. Nothing is shown in "Partition Manager". Since there's no Rawprogram XML file we need an alternative method to get the phone back on...
forum.xda-developers.com
I don't delete anything? I leave the partitions how are they? Thanks for the help.
Yes,restore them with fh_loader like netmsm's guide says.No,leave everything as is and just flash away!Make sure you make a back up first just in case anything goes wrong.
Surgemanxx said:
Yes,restore them with fh_loader like netmsm's guide says.No,leave everything as is and just flash away!Make sure you make a back up first just in case anything goes wrong.
Click to expand...
Click to collapse
I can install the backup without problems, I perfectly restore the imei and stop giving the NTCODE error, I also restore the serial as before. Unfortunately, the network error continues, apparently the solution for now is only with box, thank you very much for your help and patience, let me know if you have any news.
mclarenf195 said:
I can install the backup without problems, I perfectly restore the imei and stop giving the NTCODE error, I also restore the serial as before. Unfortunately, the network error continues, apparently the solution for now is only with box, thank you very much for your help and patience, let me know if you have any news.
Click to expand...
Click to collapse
Even with a Medusa box,the G8x as of now can't repair the network permalock issue after IMEI repair.V60 yes from what I was told,but I would still need to see proof of that myself because I sure haven't seen it..lol...But,glad I could help you partially with the backup!
mclarenf195 said:
Friend I have a question, should I restore the LUNS files with fh_loader how in the netmsm guide?
[Tutorial] Rescue From HARD BRICK
Don't worry! Everything's gonna be alright ;) You may accidentally erase all partitions and GPT on your phone. Nothing is shown in "Partition Manager". Since there's no Rawprogram XML file we need an alternative method to get the phone back on...
forum.xda-developers.com
I don't delete anything? I leave the partitions how are they? Thanks for the help.
Click to expand...
Click to collapse
Did you have any luck with restoring? I flash LUNs to my g8x but still have no network (flashed native modem and modemst)
N
St.Noigel said:
Did you have any luck with restoring? I flash LUNs to my g8x but still have no network (flashed native modem and modemst)
Click to expand...
Click to collapse
No luck still with ntcode and network blocked problem
mclarenf195 said:
N
No luck still with ntcode and network blocked problem
Click to expand...
Click to collapse
You'll need your original LUNS 5 backup most definitely for it work.

[Solved] Need help with SDMC DV8519 (bootloop)

Hello, I'm fairly new here. I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again. How do i fix that? How do i access the recovery mode?
TV Box: https://www.androidtv-guide.com/pay-tv-provider/united-group-eon-ott-smart-box/
Fzloop said:
Hello, I'm fairly new here.
Click to expand...
Click to collapse
Fairly? You joined yesterday. You could hardly be fairer.
Fzloop said:
I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again.
Click to expand...
Click to collapse
The good news is that since it is bootlooping, the bootloader is probably okay.
For this model device running android 9, neither of the bootable partitions can be modified (while still running the original bootloader), even if the bootloader is unlocked, without causing a signature check failure. Since flashing some twrp version has modified the recovery partition, which is a bootable partition, the signature check is failing.
Fzloop said:
How do i fix that?
Click to expand...
Click to collapse
One way is to flash the original recovery partition back to the device using burn mode.
Fzloop said:
How do i access the recovery mode?
Click to expand...
Click to collapse
By holding the button on the device. You'll need the worldcup drivers and command line "update" burn mode tool (not the GUI burning tool).
If you have a copy of the original recovery partition, you'd just flash that with the update tool and be done.
If you don't have a copy of the original recovery partition, you can use the update tool to dump a different partition, like system, in order to learn which version of the firmware is installed on your box. Report the version here, and maybe some member will have the matching recovery partition that you can flash to your device using the update tool.
goapy said:
Fairly? You joined yesterday. You could hardly be fairer.
The good news is that since it is bootlooping, the bootloader is probably okay.
For this model device running android 9, neither of the bootable partitions can be modified (while still running the original bootloader), even if the bootloader is unlocked, without causing a signature check failure. Since flashing some twrp version has modified the recovery partition, which is a bootable partition, the signature check is failing.
One way is to flash the original recovery partition back to the device using burn mode.
By holding the button on the device. You'll need the worldcup drivers and command line "update" burn mode tool (not the GUI burning tool).
If you have a copy of the original recovery partition, you'd just flash that with the update tool and be done.
If you don't have a copy of the original recovery partition, you can use the update tool to dump a different partition, like system, in order to learn which version of the firmware is installed on your box. Report the version here, and maybe some member will have the matching recovery partition that you can flash to your device using the update tool.
Click to expand...
Click to collapse
I did join yesterday, but I've been using this forum for a while without posting.
I managed to fix the box on my own, turns out all i needed was an SD card and a ROM.
Fzloop said:
I managed to fix the box on my own, turns out all i needed was an SD card and a ROM.
Click to expand...
Click to collapse
An alternative ROM, or the original ROM?
If you installed an alternative ROM, you may have "fixed" your box, but you've also blown away your drm keys forever.
If you're happy with the result, that's all that matters.
Although you could have posted that your issue had been resolved. That would have saved me from wasting my time. I always regret replying to posts about the dv8519. This is the last one for me.
goapy said:
An alternative ROM, or the original ROM?
If you installed an alternative ROM, you may have "fixed" your box, but you've also blown away your drm keys forever.
If you're happy with the result, that's all that matters.
Although you could have posted that your issue had been resolved. That would have saved me from wasting my time. I always regret replying to posts about the dv8519. This is the last one for me.
Click to expand...
Click to collapse
Unfortunately, alternative. I'm still looking for the original.
My apologies for wasting your time. Have a great day.
Fzloop said:
Unfortunately, alternative. I'm still looking for the original.
My apologies for wasting your time. Have a great day.
Click to expand...
Click to collapse
Hi @Fzloop,
can you share the ROM?
xfenixxx said:
Hi @Fzloop,
can you share the ROM?
Click to expand...
Click to collapse
BoskoWifiBT
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Worked fine at first, but after playing with it a bit more the box just wouldn't boot, so be careful.
Fzloop said:
BoskoWifiBT
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Worked fine at first, but after playing with it a bit more the box just wouldn't boot, so be careful.
Click to expand...
Click to collapse
Thank you very much, I'll still give it a try.
Hello, I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again. How do i fix that? How do i access the recovery mode?
TV BOX https://www.androidtv-guide.com/pay-tv-provider/dhiraagu-tv-joybox/
box connected AMLOGIC usb burn tool. but error uboot/getresult/Diskinitial error

Categories

Resources