Database Users

not able to flash factory image!

hey guys,
after a long day og non-success i really need your help here.
i tried to do a factory image restore as described here: http://forum.xda-developers.com/showthread.php?t=1907796
Everything worked fine until it came to the point of flashing the image (fastboot -w update image-nakasi-jop40c.zip). as you can see on screenshot1 it stops working at step "sending system" (i´ve been waiting for 2 hours, nothing happened).
also tried the same procedure with nexus 7 toolkit and nexus root toolkit, but here the same problem mentioned above occurs when "sending bootloader" (see screenshot2).
all in all here is what i´ve got:
working unlocked bootloader (4.13), stock recovery and fastboot - but no system
i hope there´s all the information you need right now and anyone can help me out of this misery.
thanks!

Take a look at this video; it describes everything you need to learn how to use the Nexus 7 Root Toolkit: http://www.youtube.com/watch?v=sK9avekmA1c
Once you figure it out you will also be able to flash the stock ROM to your tablet.
boerni2k said:
hey guys,
after a long day og non-success i really need your help here.
i tried to do a factory image restore as described here: http://forum.xda-developers.com/showthread.php?t=1907796
Everything worked fine until it came to the point of flashing the image (fastboot -w update image-nakasi-jop40c.zip). as you can see on screenshot1 it stops working at step "sending system" (i´ve been waiting for 2 hours, nothing happened).
also tried the same procedure with nexus 7 toolkit and nexus root toolkit, but here the same problem mentioned above occurs when "sending bootloader" (see screenshot2).
all in all here is what i´ve got:
working unlocked bootloader (4.13), stock recovery and fastboot - but no system
i hope there´s all the information you need right now and anyone can help me out of this misery.
thanks!
Click to expand...
Click to collapse

thanks for your answer but this is not helpful. the problem is not that i dont know how to use the tools but somehow the flashing process stops at the points mentioned above and i cant explain why

Maybe your downloaded factory image is corrupted somehow? You could try re-downloading and/or flashing the system.img separately:
fastboot flash system system.img

i already tried that and also let the toolkits download the images themselves but still no success.
when flashing the system.img seperately it still just says sending system.img but nothing happens
trying to flash an older bootloader also failed due to the same problem

Try different cable/USB port/PC. Sounds unlikely but you'd be surprised.

Looks like the 4.13 bootloader has a serious issue with receiving and then flashing data, I keep reading about this....

dave_uk said:
Try different cable/USB port/PC. Sounds unlikely but you'd be surprised.
Click to expand...
Click to collapse
holy cow. it´s always the simple things in life that really matter right? although i already tried different usb ports, there were still others to try and finally it worked!
thanks man! problem solved

boerni2k said:
holy cow. it´s always the simple things in life that really matter right? although i already tried different usb ports, there were still others to try and finally it worked!
thanks man! problem solved
Click to expand...
Click to collapse
Had a very similar situation myself a couple of days where I thought I'd completely murdered by days-old Nexus 7 3G and switching flaming USB ports sorted it. Annoyance and relief in equal measure! Glad it worked for you.
D

flash write failure

Dear guys,
due to problems within this morning, i restarted my phone to wipe dalvik/cache.
But it occured that TWRP somehowe needs to have a password (which i didn't ever set though).
Didn't boot up at all now. Even with toolkit no chance to do anything with the device.
Any further suggestions/ideas?

Try flashing the factory image without using a tool kit. Google nexus 4 factory image. Download it to your pc and extract it. Run the flash-all.bat you'll find in there.
Sent from my Nexus 5

r4ff0r said:
Dear guys,
due to problems within this morning, i restarted my phone to wipe dalvik/cache.
But it occured that TWRP somehowe needs to have a password (which i didn't ever set though).
Didn't boot up at all now. Even with toolkit no chance to do anything with the device.
Any further suggestions/ideas?
Click to expand...
Click to collapse
Some Partitions of the phone have got some bad blocks causing it to act in such a way !! Seems RMA(if available) is the best recourse since there is no definative solution to this problem !! You can try hard reboot as well as someone once pointed out that his n4 magically restored during it but others dint have that much of luck !! Also u could give LGNPST a try but since that also writes the partition it is highly unlikely to get you through !! One Solution I know will surely work is Qualcomm PST using the HighSpeed USB Device . But unfortunately we need an expert help, probably a Qualcomm employee to get in touch with since the tool has still not been cracked by anyone for n4 though I read somewhere that someone was able to restore using QPST !! Also mostly a JTAG Repair can help you but thats a rip off !! I'll anyday prefer a official LG/Google Repair over a JTAG !!
Hope you find my post useful !!

THanks Guys,
JD5, it didn't work.
Corresponding to Nabendu's post i guess it is the issue mentioned here.
http://forum.xda-developers.com/nexus-4/help/dead-nexus-4-strange-advice-welcome-t2259334
So therefore i don't see any chance :-/

r4ff0r said:
THanks Guys,
JD5, it didn't work.
Corresponding to Nabendu's post i guess it is the issue mentioned here.
http://forum.xda-developers.com/nexus-4/help/dead-nexus-4-strange-advice-welcome-t2259334
So therefore i don't see any chance :-/
Click to expand...
Click to collapse
I was afraid of that. Try one thing. Relock the bootloader, fastboot oem lock, then re-boot and see if the bootloader locks. If it doesn't, and it probably won't, then rma is your option.
Edit, haha, I just read that thread you posted and they tried the same thing
Sent from my Nexus 5

i was already trying that. at first it seems that the bootloader got locked again but right after restart it is already unlocked again.
I guess RMA will cause problems due to the fact that it was a rooted Nexus, using a custom rom.

r4ff0r said:
i was already trying that. at first it seems that the bootloader got locked again but right after restart it is already unlocked again.
I guess RMA will cause problems due to the fact that it was a rooted Nexus, using a custom rom.
Click to expand...
Click to collapse
Google seems to have been pretty good with rma's when it's a hardware failure. Pretty sure your emmc is borked. But you never know until you send it in. Hopefully there won't be a problem.
Sent from my Nexus 5

Ok I'll give it a try on monday. But as far as i know, i'll need to call them first.
I could imagine that they'll try to let me wipe my data or give me any kind of instructions to see if they can resolve the problem right away? What do i tell them?
At latest when they'll lead me to the recovery i'll get stuck using TWRP at latest.
Any kind of conversation dialogue i can follow up?

Let's try one more thing, inside the factory image is a zip file, extract that. In there is recovery.img. Put that file in the same folder as fastboot.exe. In fastboot try fastboot flash recovery recovery.img
If it works it'll put the stock recovery on.
Sent from my Nexus 5

Nope, same issue " flash write failure"
I can't get any kind o access...
But don't leave any more thoughts on it. Won't work though, i won't want to bother you all the time

jd1639 said:
Let's try one more thing, inside the factory image is a zip file, extract that. In there is recovery.img. Put that file in the same folder as fastboot.exe. In fastboot try fastboot flash recovery recovery.img
If it works it'll put the stock recovery on.
Sent from my Nexus 5
Click to expand...
Click to collapse
It won't let you flash that either to the best of my knowledge !! Just don't tell those operators that you have unlocked your bootloader and have a custom recovery !! Basically they won't tell u to go into stock recovery !! They'll just ask you hard reset the phone using physical keys !! Bdw check my pm !!

r4ff0r said:
Nope, same issue " flash write failure"
I can't get any kind o access...
But don't leave any more thoughts on it. Won't work though, i won't want to bother you all the time
Click to expand...
Click to collapse
Np, not sure what to tell them. It still boots I assume so you can't tell them it won't boot. I guess just the truth, it is a developer phone after all so it should be flashable
Sent from my Nexus 5

Bootloop with google screen and corruption screen after factory image flash

After flashing a rom my phone got hot, and I didn't want to run any more roms for awhile. So i decided it was time for a fresh install of factory image. I read the guide lines closely to fastbooting the latest factory image. Now im in a boot loop with the google unlock icon and the corruption screen . I tried going to stock recovery and factory wipe and still bootlooping. It's been doing this for awhile. Please help!

Did you verify the checksum of the image prior to executing the flash-all script?

redduc900 said:
Did you verify the checksum of the image prior to executing the flash-all script?
Click to expand...
Click to collapse
I don't use flash all script. I flashed each img individually like it's posted in the guide

redduc900 said:
Did you verify the checksum of the image prior to executing the flash-all script?
Click to expand...
Click to collapse
Yes the checksum was verified

XMayhem2099 said:
After flashing a rom my phone got hot, and I didn't want to run any more roms for awhile. So i decided it was time for a fresh install of factory image. I read the guide lines closely to fastbooting the latest factory image. Now im in a boot loop with the google unlock icon and the corruption screen . I tried going to stock recovery and factory wipe and still bootlooping. It's been doing this for awhile. Please help!
Click to expand...
Click to collapse
Don't panic yet. Try formatting both userdata and cache and then flash all the image files again. Any errors?

v12xke said:
Don't panic yet. Try formatting both userdata and cache and then flash all the image files again. Any errors?
Click to expand...
Click to collapse
Did both still the same bootloop

XMayhem2099 said:
Did both still the same bootloop
Click to expand...
Click to collapse
1. Ok, so format, not erase. Exactly which img files did you flash... and you did not get any errors back from fastboot, meaning it always finished cleanly? Have you tried using the flashall.bat?
2. Do you have any saved backups to restore (even of the old custom rom).
3. May sound funny, but have you tried NRT? Wug has a flash to stock/unroot routine with the option for a bootlooping case. It will also allow you to "point" it to the Google image you are using, but you may try allowing NRT to re-download and hash check it again just in case.
You should be able to recover from this. Don't try lock/unlock the bootloader. Leave it unlocked.

v12xke said:
1. Ok, so format, not erase. Exactly which img files did you flash... and you did not get any errors back from fastboot, meaning it always finished cleanly? Have you tried using the flashall.bat?
2. Do you have any saved backups to restore (even of the old custom rom).
3. May sound funny, but have you tried NRT? Wug has a flash to stock/unroot routine with the option for a bootlooping case. It will also allow you to "point" it to the Google image you are using, but you may try allowing NRT to re-download and hash check it again just in case.
You should be able to recover from this. Don't try lock/unlock the bootloader. Leave it unlocked.
Click to expand...
Click to collapse
Absolutely no errors from fastboot which is weird. I'll try the fashall.bat . Nope no custom backups, i tried nexus toolkit and the hashcheck matched still in bootloop. I haven't messed with the bootloader it's always been unlocked

XMayhem2099 said:
Absolutely no errors from fastboot which is weird. I'll try the fashall.bat . Nope no custom backups, i tried nexus toolkit and the hashcheck matched still in bootloop. I haven't messed with the bootloader it's always been unlocked
Click to expand...
Click to collapse
Gotcha. Which partitions did you flash, and in what order? If you look at the flashall.bat in a text editor, there is a check/requirement for a certain bootloader version level to for system (at least, and maybe more) ....anyway when manually flashing, bootloader.img should be the first, and then fastboot reboot into that bootloader before proceeding with all the other partitions. Look for any errors during the flashall batch run.
Edit: You may also want to re-run NRT, confirming the "soft brick mode" is ticked, and check the log window for ANYTHING out of the ordinary. Could also try NRT to revert back to 7.0 release.

v12xke said:
Gotcha. Which partitions did you flash, and in what order? If you look at the flashall.bat in a text editor, there is a check/requirement for a certain bootloader version level to for system (at least, and maybe more) ....anyway when manually flashing, bootloader.img should be the first, and then fastboot reboot into that bootloader before proceeding with all the other partitions. Look for any errors during the flashall batch run.
Edit: You may also want to re-run NRT, confirming the "soft brick mode" is ticked, and check the log window for ANYTHING out of the ordinary. Could also try NRT to revert back to 7.0 release.
Click to expand...
Click to collapse
I did the flash all command it ran successfully. Looks like im still getting a bootloop. I'll let it sit for an hour or so. If it doesn't run ill flash an older factory image. Thanks for the help, Ill let you know what happens.

Mine started doing the same thing last night, so far nothing I have tried has worked. Wireless provider is no help maybe Huawei will replace.

I'm active in a couple threads myself over this exact scenario. What the hell is going on with these phones?
Sent from my Nexus 6 using XDA-Developers mobile app

CyberpodS2 said:
I'm active in a couple threads myself over this exact scenario. What the hell is going on with these phones?
Click to expand...
Click to collapse
Huawei seems to have done a crappy job manufacturing them. Mine bootloops every time I update to a new ROM build, every time I switch ROMs and every time I try to restore a backup. Thankfully I've been able to get out of it every time so far but I've owned a lot of phones and none went into bootloops as often as the 6P. I've resigned myself to the fact that this phone is a time bomb and that it likely won't have a very long life. Would never buy another phone made by Huawei.

Problem google and hawuei (hardware) RMA

People facing bootloop of death.
1. How long have you been using your phone?
2. What's your EMMC and RAM name in bootloader?
3. What's your manufacturing date in bootloader?
4. Do you play games on your phone?
5. Does your phone get hot often?

fapste said:
People facing bootloop of death.
1. How long have you been using your phone?
2. What's your EMMC and RAM name in bootloader?
3. What's your manufacturing date in bootloader?
4. Do you play games on your phone?
5. Does your phone get hot often?
Click to expand...
Click to collapse
1. In general or when it happened? Averaged 4 hours SOT in 14-16 hours total.
2. 128 Toshiba
3. 3-29-2016
4. No
5. No

Same issue on a buddies 6p.. Fastboot commands go through the script with no errors but no results.. Still stuck in this bootloop. Has to be hardware causing this bootloop.

I'm having the same issue
Sent the device to Huawei and they say they'll repair it but I'm not sure if that's possible

My question is when they replace them, is the defect still waiting to pop up again??
Sent from my Nexus 6 using XDA-Developers Legacy app

Bought 2nd hand phone, managed to coax original sales receipt from Google store out of seller. Sent it in for an RMA and they swapped out my motherboard. Was also out of warranty by 2 months

Messed up my phone's boot loader image, is retrieving at least my photos possible?

Hi all, I really messed up my 6T today, after messing with the new update and root, I ran the flash_all.bat file (from https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516) to restore images but didn't realize it would clear all my data, I stopped the process after it ran for a few seconds in a panic but now my phone only has the fastboot screen and fastboot.exe from my cmd shell is unable to do anything (just errors out for most commands), is there a way for me to at least retrieve my photos from my phone? I've tried 3rd party software and they all require usb debugging which I can't activate due to my phone not having a boot image. Any help would be a miracle, thanks.

I would try fastbooting a TWRP image. From there you may get access to your internal storage. You can then copy it off to a PC. I say may because you could encounter encryption issues when trying to first boot into TWRP.
If you do hit encryption issues, you could modify the "flash all" batch file to remove the -w command so it doesnt format. However, I thought that it gave you an option to wipe or not?
If it did wipe first, your a gonner my friend. You are too late.
Hope this gives you some insight on where to go from here.

Thanks, that's what some others have been telling me, I have tried to fastboot flash a few versions of TWRP and blu spark (I had the latest android version I believe, so even tried the Q version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482), but none of them are working, I get a failed to load/authenticate error when doing fastboot flash <img name> and fastboot flash boot <img> doesn't error out but I still can't get past the fastboot menu.
I see the flash_all script has the -w in it, but yeah it never prompted me about wiping all data. I managed to kill the process a few seconds in, so even if it was deleting, large files like my photos and videos should still be existent on the drive somewhere, right? Unless the -w command does a really fast purge of the files?

christmasdesparation said:
Thanks, that's what some others have been telling me, I have tried to fastboot flash a few versions of TWRP and blu spark (I had the latest android version I believe, so even tried the Q version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482), but none of them are working, I get a failed to load/authenticate error when doing fastboot flash <img name> and fastboot flash boot <img> doesn't error out but I still can't get past the fastboot menu.
I see the flash_all script has the -w in it, but yeah it never prompted me about wiping all data. I managed to kill the process a few seconds in, so even if it was deleting, large files like my photos and videos should still be existent on the drive somewhere, right? Unless the -w command does a really fast purge of the files?
Click to expand...
Click to collapse
THe -w command does a very fast wipe. So if it was at the beginning of the scrip that more than likely like your files are gone.
Run the script again, this time delete the -w command. This will be your best chance of finding any data.

I see, if the wipe has already happened, are there more low-level ways to retrieve the data? Since it couldn't have purged from the disk all 20 gigs of photos in such a short time span. Though I'm guessing even if there are fragments left like that they're most likely corrupted and unusable?
Anyway, I took it to a shop today since I couldn't do much else my self, we'll see what happens. Lesson learned to always back up before messing with the boot.
Thanks

christmasdesparation said:
Lesson learned to always back up before messing with the boot.
Click to expand...
Click to collapse
And to properly read and understand what it is you're attempting to do.

sssarg said:
And to properly read and understand what it is you're attempting to do.
Click to expand...
Click to collapse
lol yes but in my defense I was already kind of freaking out since the fastboot wasn't working like it did previous times and messed up my normal boot

christmasdesparation said:
I see, if the wipe has already happened, are there more low-level ways to retrieve the data? Since it couldn't have purged from the disk all 20 gigs of photos in such a short time span. Though I'm guessing even if there are fragments left like that they're most likely corrupted and unusable?
Click to expand...
Click to collapse
Probably not possible as user data are stored in a virtual filesystem, mounted over an encrypted partition.
That's the reason why police forces regularly ask phone makers to put a backdoor, it's very hard even for a high tech forensic specialist to find data on a phone

So I actually re-ran the flash_all.bat script without the -w flag and I was able to fast boot flash into twrp (twrp-3.3.1-30-fajita-Q-mauronofrio to be specific). I can see what i believe are my files in the internal storage, but encrypted, however twrp never prompted me for a password, also going to the twrp terminal and entering twrp decrypt <passcode> did not work. Anybody know how to get twrp to decrypt? For some reason flash_all.bat did not restore my original boot or anything so I am only able to boot into recovery mode or twrp from the fastboot on my PC. doing fastboot getvar all shows that my slot-unbootable:a is "yes" if anyone knows how to make sense of this, it would be appreciated, even if I just need to copy my phones internal storage on to my computer and run 3rd party software to decrypt it that is fine
Thank you

Final update: fixed my device completely, turns out I was using the flash all for update 41, all I had to do was use the same script for the 42 update without the -w flag and now my phone is back to normal, everything is where it originally was

christmasdesparation said:
Final update: fixed my device completely, turns out I was using the flash all for update 41, all I had to do was use the same script for the 42 update without the -w flag and now my phone is back to normal, everything is where it originally was
Click to expand...
Click to collapse
Could have used msm tool. You would have lost everything but at least phone would have worked

jamescable said:
Could have used msm tool. You would have lost everything but at least phone would have worked
Click to expand...
Click to collapse
Yeah, he was trying hard to avoid that.
christmasdesparation said:
Final update: fixed my device completely, turns out I was using the flash all for update 41, all I had to do was use the same script for the 42 update without the -w flag and now my phone is back to normal, everything is where it originally was
Click to expand...
Click to collapse
Im glad it did not wipe the phone the like I feared it may have. Glad you got it going.

Scott said:
Im glad it did not wipe the phone the like I feared it may have. Glad you got it going.
Click to expand...
Click to collapse
Thanks, I owe it to you, your original advice was spot on and all I failed to do was check the version number

jamescable said:
Could have used msm tool. You would have lost everything but at least phone would have worked
Click to expand...
Click to collapse
Well to me "everything" on my phone was worth more to me than the phone itself

**PERSIST REQUEST** Enrollment Problem

If you can help me fix this i will donate you for your time
Somehow deleted messed up Persists and need a backup.

We are in a similar situation, my adb wasn't fully working, couldn't root on 10.5.4, msm and went back to stock, realized my adb wasn't fully working, I did the OTA to 10.5.5 and then I rooted, lost fingerprint read. Personally, I value root far more than fingerprint function, already started customizing the phone so can't be bothered to wipe the phone. I am pretty sure you would regain the fingerprint function if you go back to fully stock. If you can't be bothered to do it yourself, I think it's just a matter of time until a toolkit that does it for you is updated for the 8 pro.

t-mizzle said:
We are in a similar situation, my adb wasn't fully working, couldn't root on 10.5.4, msm and went back to stock, realized my adb wasn't fully working, I did the OTA to 10.5.5 and then I rooted, lost fingerprint read. Personally, I value root far more than fingerprint function, already started customizing the phone so can't be bothered to wipe the phone. I am pretty sure you would regain the fingerprint function if you go back to fully stock. If you can't be bothered to do it yourself, I think it's just a matter of time until a toolkit that does it for you is updated for the 8 pro.
Click to expand...
Click to collapse
ive done used MSM Brick Fix along with just about every other stock. Nothing has worked only reason i am so panicky over it is being used for a project that im working on and really need all features to work

Is this for Global or EU? Have a look in my thread if you need an EU persist. I ended up bricking mine trying to fix it.
This seems quite a wide spread issue, MSM doesn’t fix it either

If no one can provide you with a fix, I would use adb to flash the stock boot image. If you are wiped and fully stock again, did you go through the setup again, if so, did the enrollment fail there or did it fail when you manually went there? I just don't see why it would fail when the phone is in the stock "first bootup" mode.

It fails during first setup, during any setup. Even after a full flash with msm tool. I think the persist partion somehow gets messed up.
All I had done is flashed stock boot img was then reset.

Interesting. Did you at any point have a working fingerprint scanner? I did, until I rooted.

Guitarfreak26 said:
It fails during first setup, during any setup. Even after a full flash with msm tool. I think the persist partion somehow gets messed up.
All I had done is flashed stock boot img was then reset.
Click to expand...
Click to collapse
you forgot to convert the persist image before flashing thats what caused your brick most likely.
---------- Post added at 09:56 AM ---------- Previous post was at 09:54 AM ----------
Dewaynelives said:
If you can help me fix this i will donate you for your time
Somehow deleted messed up Persists and need a backup.
Click to expand...
Click to collapse
If you on EU then there is a persist image on the Root thread. But remember you need to convert it to a raw img from sparse image before flashing.
Google simgtoimg tool

Yeah I didn’t convert it I think that was the issue.
And yes my fingerprint sensor worked perfectly up until a factory reset then nothing. On the other thread, Zige advised that Oneplus Finland are aware of the issue and said a fix will roll out ?

Guitarfreak26 said:
Yeah I didn’t convert it I think that was the issue.
And yes my fingerprint sensor worked perfectly up until a factory reset then nothing. On the other thread, Zige advised that Oneplus Finland are aware of the issue and said a fix will roll out ?
Click to expand...
Click to collapse
Ot..Oneplus Finland sound funny..Cause its a Chinese company and i am Finnish myself

Nekromantik said:
you forgot to convert the persist image before flashing thats what caused your brick most likely.
Click to expand...
Click to collapse
Is that something that should be common knowledge for users who are opting to root and have a tinker.
It's it easy enough to convert? It's there any way to save your device if this happens?
I know @guitarfreak has had a lot of issues and I think it's heading for RMA right Gfreak?
We need a thread about this.

dladz said:
Is that something that should be common knowledge for users who are opting to root and have a tinker.
It's it easy enough to convert? It's there any way to save your device if this happens?
I know @guitarfreak has had a lot of issues and I think it's heading for RMA right Gfreak?
We need a thread about this.
Click to expand...
Click to collapse
yes you just need the tool google simage2img
as long as you have a backup of the partition and can use the tool and have access to fastboot it can be saved as far as I know.
other user lost access to fastboot as he used MSMtool to revert back to stock so locked bootloader. If you want to flash the persist do not use msmtool

Nekromantik said:
yes you just need the tool google simage2img
as long as you have a backup of the partition and can use the tool and have access to fastboot it can be saved as far as I know.
other user lost access to fastboot as he used MSMtool to revert back to stock so locked bootloader. If you want to flash the persist do not use msmtool
Click to expand...
Click to collapse
Not that i have this happened to me but still. Witch is broken, msmtool or phones sofrware? I am using linux so msm would be pointless for me. Just out of coriousity and knoledge i am asking

dladz said:
Is that something that should be common knowledge for users who are opting to root and have a tinker.
It's it easy enough to convert? It's there any way to save your device if this happens?
I know @guitarfreak has had a lot of issues and I think it's heading for RMA right Gfreak?
We need a thread about this.
Click to expand...
Click to collapse
Yeah it’s in Poland now at the service centre. I asked for a refund for now as I’m not sure what’s happening with it. I hadn’t crossflashed anything prior to the sensor stopping. So I’m not sure what’s causing the fault.
---------- Post added at 01:24 PM ---------- Previous post was at 01:23 PM ----------
pyry666 said:
Not that i have this happened to me but still. Witch is broken, msmtool or phones sofrware? I am using linux so msm would be pointless for me. Just out of coriousity and knoledge i am asking
Click to expand...
Click to collapse
Previously with OP the MSMTOOL would fix anything. Even when moving over to AOSP ROMs. Now it seems the tool can not fix the partion. So when I flashed wrong partion then tried to fix again with the tool it locked the boot loader but wouldn’t boot into OS.

Guitarfreak26 said:
Yeah it’s in Poland now at the service centre. I asked for a refund for now as I’m not sure what’s happening with it. I hadn’t crossflashed anything prior to the sensor stopping. So I’m not sure what’s causing the fault.
---------- Post added at 01:24 PM ---------- Previous post was at 01:23 PM ----------
Previously with OP the MSMTOOL would fix anything. Even when moving over to AOSP ROMs. Now it seems the tool can not fix the partion. So when I flashed wrong partion then tried to fix again with the tool it locked the boot loader but wouldn’t boot into OS.
Click to expand...
Click to collapse
I know that. I am interested is it msmtool failure or something in os

From my understanding from looking across the forums the persist partion hasn’t been touched by MSM for a while. Which would mean it’s an OS fault.
Does the boot img even touch the persist partion as that’s the only thing that had been touched prior to the fault? I don’t have enough understanding on persist as I’d never seen the issue before lol

pyry666 said:
I know that. I am interested is it msmtool failure or something in os
Click to expand...
Click to collapse
this has nothing to do with msmtool.
msmtool was used by people to try and fix the fingerprint issue.
This only should happen if you flash wrong version boot img. If you do that then you will loose fingerprint.
Some people have lost fingerprint even if they said they used correct boot img.
only way to bring fingerprint back is to flash persist img back onto phone. but you need to use simg2img tool which converts the posted img from sparse to raw. you can only flash raw images.
when you extract the img from phone its in sparse format and not raw

Nekromantik said:
this has nothing to do with msmtool.
msmtool was used by people to try and fix the fingerprint issue.
This only should happen if you flash wrong version boot img. If you do that then you will loose fingerprint.
Some people have lost fingerprint even if they said they used correct boot img.
only way to bring fingerprint back is to flash persist img back onto phone. but you need to use simg2img tool which converts the posted img from sparse to raw. you can only flash raw images.
when you extract the img from phone its in sparse format and not raw
Click to expand...
Click to collapse
Im on Int version is there any way for me to fix it? i dont know anyone with the device myself so i have no way to get the file

Nekromantik said:
you forgot to convert the persist image before flashing thats what caused your brick most likely.
---------- Post added at 09:56 AM ---------- Previous post was at 09:54 AM ----------
If you on EU then there is a persist image on the Root thread. But remember you need to convert it to a raw img from sparse image before flashing.
Google simgtoimg tool
Click to expand...
Click to collapse
im on int myself . whats messed u is i have not flashed any files from other regions to cause this so i guess it has to do with root?

Dewaynelives said:
im on int myself . whats messed u is i have not flashed any files from other regions to cause this so i guess it has to do with root?
Click to expand...
Click to collapse
Well, in my case it has been caused by a factory reset. Yes, I was rooted before that, but everything worked fine - so maybe rooting was the cause and it became evident after the reset.
Oh, and I was only on EU ROM - so no cross-country flashing.
I'll wait for Oneplus fixing this, for me there is too little understanding what happens when flashing persist from a different phone.