Related
hi all.
like so many others, Xiaomi forced update 6.1.14 on to my phone which locked the bootloader. i even thought i had stopped the phone from auto updating, but it seems i was wrong. since then, i have been put on to the latest 2 updates. i want to get off of the rom i am on but cant do anything now with the phone in the installing rom dept because regardless of whether i try to use the 'Updater' to put a Chinese dev rom on the phone or any other rom, or if i rename a rom and put it on the root of the phone, i cannot update. i always get a message saying Unable to verify rom and the phone simply stops. when trying to go into recovery mode, as i am unable to get to TWRP, i have even been locked out of that. i applied for an unlock code, but haven't received anything and with Chinese New Year fast approaching, bringing a holiday, i can see Xiaomu ignoring those who asked for a code even longer than they have. i haven't read of a single person being sent the code at all, which is very bad on Xiaomi's part.
i was really pleased with this phone. it worked well for me and did all i wanted but now i have a door stop, to all intents and purpose. such a shame as the way things have gone, i wont be buying from them again.
does anyone have any solution to this problem?
many TIA,
Prettygrim
Download stable ROM - http://bigota.d.miui.com/V7.0.16.0.LXKCNCI/miui_MI4c_V7.0.16.0.LXKCNCI_cba5b6c4a8_5.1.zip
Update your phone to that ROM
You will lost all data and setting (/sdcard is safe)
Bootloader unlocked
Flash CM13
cowithgun said:
Download stable ROM - http://bigota.d.miui.com/V7.0.16.0.LXKCNCI/miui_MI4c_V7.0.16.0.LXKCNCI_cba5b6c4a8_5.1.zip
Update your phone to that ROM
You will lost all data and setting (/sdcard is safe)
Bootloader unlocked
Flash CM13
Click to expand...
Click to collapse
And stay away from dev ROMs unless you have an unlock code.
hi and tnx for the replies.
to cowithgun:
unfortunately, i cannot update to that or any other rom, as i stated above. trying to do so via the 'Updater' and all i get is 'Unable to verify rom', that is after being told i must connect to the WLAN. the speed of that is almost non-existent.
if i try to do so by putting the rom in the root of the drive, renaming it 'update.zip' i again get told 'unable to verify rom'. because of the failure to be able to do anything 'conventional' was the reason i asked for help. i have even tried Kingroot and Kingoroot but both have failed.
to qtotter:
one of the methods i was asked to try was to try to use a Chinese dev rom, but i cant even get one of those on the phone (my wife is Chinese, so no language issues).
with the upcoming Chinese New Year, i can see Xiaomi using that as an excuse to delay giving out unlock codes, if it intends doing so at all. i am extremely p****d off at what they have done and in my case, they have turned a phone that i really liked into half a phone. such i stupid stunt to pull when the 'unlocked' was a feature used to actually make the phone a more attractive sale. really disappointed
should have asked guys, what method would you suggest i try to get this rom, (if the blasted phone doesn't give me the same message as before about cant verify it) installed on the phone? bear in mind i have no official recovery and obviously no TWRP.
TIA
Prettygrim said:
hi and tnx for the replies.
to cowithgun:
unfortunately, i cannot update to that or any other rom, as i stated above. trying to do so via the 'Updater' and all i get is 'Unable to verify rom', that is after being told i must connect to the WLAN. the speed of that is almost non-existent.
if i try to do so by putting the rom in the root of the drive, renaming it 'update.zip' i again get told 'unable to verify rom'. because of the failure to be able to do anything 'conventional' was the reason i asked for help. i have even tried Kingroot and Kingoroot but both have failed.
to qtotter:
one of the methods i was asked to try was to try to use a Chinese dev rom, but i cant even get one of those on the phone (my wife is Chinese, so no language issues).
with the upcoming Chinese New Year, i can see Xiaomi using that as an excuse to delay giving out unlock codes, if it intends doing so at all. i am extremely p****d off at what they have done and in my case, they have turned a phone that i really liked into half a phone. such i stupid stunt to pull when the 'unlocked' was a feature used to actually make the phone a more attractive sale. really disappointed
should have asked guys, what method would you suggest i try to get this rom, (if the blasted phone doesn't give me the same message as before about cant verify it) installed on the phone? bear in mind i have no official recovery and obviously no TWRP.
TIA
Click to expand...
Click to collapse
I tested it myself, it should work. More precisely, I did this:
1. Download this into your computer: http://bigota.d.miui.com/V7.0.16.0.LXKCNCI/miui_MI4c_V7.0.16.0.LXKCNCI_cba5b6c4a8_5.1.zip
2. Connect phone to computer via USB, copy the zip into your phone, say /sdcard/downloaded_rom/miui_MI4c_V7.0.16.0.LXKCNCI_cba5b6c4a8_5.1.zip
3. Start Updater, press the "..." on upper right and select "Choose update package", select the ROM.
4. Installing older developer ROM will causes the error you mentioned, but if you have 6.1.14, installing stable 7.0.16 is OK and tested working. Not sure what is changed but if it still wont work, try the latest 7.1.6 stable instead.
5. It will warn you of losing setting. Please YES.
6. When it's done, you will have a MIUI ROM but bootloader no longer lock.
7. Install CM13 as soon as you can!
Sounds like the problem is your recovery. You said you have no official recovery.
Sent from my Mi-4c using Tapatalk
just tried it and no luck, i'm afraid. still getting the message 'Cant verify update'. also tried moving the file to root of phone, renaming it to 'update.zip' and still no luck, still getting the same message. it seems that the phone is well and truly locked down so it wont even take one of Xiaomi's own official updates, unless it is a progression from the present rom. that in my view is well over the top!!
tnx for trying and if you or anyone has another idea, please let me know. it appears that the thing to turn off is the verification of the rom. is that possible, and if so, how?
one thing i have noticed in the settings -->developer options is 'verify apps over USB. could this be anything to do with the rom verification failure? the txt for that is greyed out with the button on (redish) but i cant see how to change the setting. worth a try maybe? anyone know how to change it?
Ulver said:
Sounds like the problem is your recovery. You said you have no official recovery.
Sent from my Mi-4c using Tapatalk
Click to expand...
Click to collapse
you may well be right, but if that's the case, it was done by Xiaomi. is there a way of getting it to work? how do i actually check it isn't working? as stated before, when 'booting into recovery', i get an image of the phone on screen with the USB cable either connected or disconnected, depending on the actual state and nothing else happens. i have to do a reboot holding the start button to achieve this
Prettygrim said:
bear in mind i have no official recovery and obviously no TWRP.
Click to expand...
Click to collapse
I'm still waiting for my mi4c to come from China, and this is the reason why I'm gonna flash the latest (unlocked) official "stable" ROM first only to update the recovery and radio partitions right after I receive the phone. Resellers in China sometimes put their custom ROMs, recovery images or malware in the phones.
I don't think I'd flash twrp right away. I'd install cm12.1 or cm13 by "fastboot boot recovery.img" leaving the official recovery left in the phone so that I could go back to the official ROMs in the official way, and confirm if everything works as expected before flashing twrp.
What I don't understand is why people flash the dev (locked) ROMs as they are downloaded. What they need is just boot.img and /system, isn't it?? I'd replace "firmware-update" folder, where bootloader, radio and recovery images are located, in the dev ROM with the one from the stable ROM if I wanna try dev ROMs. Or I'd replace boot.img and system.* in the stable ROM with the ones in the dev ROM. Those modded ROMs should be able to be flashed with twrp...
the main reason for using the Chinese dev roms is because they are supposed to bee already rooted. once any of these roms is on the phone, according to what else i read, any rom going over the top would keep root. personally, i didn't find any rom that had root already and had to root my phone, following instructions i found on the MIUI and other sites. the built in recovery on my phone does nothing.
i had issues with TWRP when first using it, but put that down to being a novice. i found the files needed and the procedure to get out of the constant TWRP loop, which meant the phone was basically soft bricked and all was good. however, even that method fails now with the message something like 'phone is locked, cannot continue.
i have put an official complaint into Xiaomi about the bootloader locking and also about the time being taken to issue unlock codes, which is much longer than 3-21 days in some cases.
if i get anywhere, i'll post what i'm told
Since the latest miui ROMs are all based on Android 5.1.1, it's really easy to root mi4c yourself even on official standard ROMs. You don't have to flash dev ROMs or flash custom recovery like twrp. You can just run twrp on the fly like "fastboot boot twrp.img" to flash SuperSU.zip as long as bootloader is unlocked.
I'd say it's more dangerous to flash dev ROMs only for rooting especially if it's for your wife, not for yourself... Dev ROMs are for people who want to try new functions and designs still under development.
Anyway, I hope you will get an unlock SMS from xiaomi soon!
Had same Problem
search for miui_MI4c_V7.1.6.0.LXKCNCK_1debc127a9_5.1.zip
Hope it helps
So if the bootloader is locked, you can unlock it by flashing an older dev rom?
ermacwins said:
So if the bootloader is locked, you can unlock it by flashing an older dev rom?
Click to expand...
Click to collapse
No. Older Developer ROM will not work. Updater will refuse to update it. I tested a few of them back then, only by flashing the latest stable ROM back then (7.0.16) work.
cowithgun said:
No. Older Developer ROM will not work. Updater will refuse to update it. I tested a few of them back then, only by flashing the latest stable ROM back then (7.0.16) work.
Click to expand...
Click to collapse
And now flash the lastest developer and try roll back one o two a time (this work for my with the original recovery) and later use one rom from xiaomi.eu that one has not locked bootloader .
Sorry for my bad english.
i'm probably being real thick here guys. please bear with me. i am, as i said before, new to all this stuff with phones.
remember too that i have an unlocked bootloader now, courtesy of Xiaomi.
so, just to be clear, i am using miui_MI4c_5.12.31_5d6537a0b8_5.1.zip. to remove the possibility of Xiaomi doing something else to the phone that i dont want, i would like to get on to the xiaomi.eu_multi_libra roms. how do i go about doing this in idiot-proof steps, please? also, if i manage to achieve what i want, how do i stop the phone taking official updates? there must be a setting in the phone somewhere that can be disabled and prevent it updating to what i dont want. i found the one in the 'updater settings' but am of the opinion there is another somewhere that i cant find.
hope someone will be gentle with me
TIA
If you're already on Xiaomi.EU ROMs, you won't get OTA updates directly from Xiaomi that will lock your bootloader.
Sent from my Mi-4c using Tapatalk
i am on
miui_MI4c_5.12.31_5d6537a0b8_5.1.zip
which is an official rom, i believe. hence the questions in my former posts. i want to get on to the libre eu roms but am unsure how to go about it. i have read about using various roms first but i believe doing so is under certain circumstances, ie, bootloader locked, phone not rooted. my phone has the bootloader unlocked now by Xiaomi and i have rooted the phone. this is where my confusion comes in that i was hoping someone could clarify
You have unlock permission from xiaomi now, which means you don't need to worry about updates. You can unlock your phone again anytime you want. It's not one time only thing.
well that's a relief! tnx, qtotter! i didn't want to have to go through all this again, just because the maker decided i hadn't actually bought the phone, i had just bought permission to use it, as long as it was how he wanted me to use it!
bloody USA judge who decided that must have been paid a small fortune to rule in favour of this! just what the entertainment industries and others wanted!! didn't care what the implications were or ow the industries would take the p**s out of customers!!
So, my wife decided to buy this phone, and I am to stay away from her phones. She smashed the screen one day, and that was a door open for me. I hastily get some version of TWRP to boot on it and grab a backup, and also do an adb backup (which was crap). Then, I did a full wipe before taking it in to get repaired.
SO, what I want to walk through here boys and girls, is never, never, never, never, put Smartisan OS 2.5.3 on this phone. When my wife got her phone back I harmlessly believed that updating would not disallow me from TWRP again to recover. What this version does to the device is completely disable recovery altogether. You are always pushed to fastboot, and fastboot cannot flash anything After this realization, I borked the phone, I dd'ed out the aboot and the sbl. She had insurance, we live in China it is cheap, and after the difficulties I realized this was happening to lots of people. I figured the local service center could re-write the partitions I had pooped on and they would re-write it with an earlier firmware. My gamble paid off.
Got the phone back with 2.5.0. I immediately followed the guide here http://tinyurl.com/z7ekyxp , Russian site, to revert back. I then, deviating from the guide to be careful, fastboot boot "twrp.img". I used commands the whole way, no flashify or anything (I love flashify on my nexus 5 but I had already borked this phone once. It booted TWRP, I copied all the old SD files over to the phone. Then, the moment of truth, would a restore from my previous backup work. Yes, it did. I even followed the guide through and flashed the 2.3.5 modified update. It worked, the SuperSU and open gapps flashed without issue also.
Not a horrible phone for being extremely cheap, but they messed up an update. For those fooling around with the device, remember the partition table has a bak for all boot related things. I also see on Chinese forums that they use the headphone jack for diagnostics (My Chinese isn't great, but I looked around when I bricked my wife's phone).
One thing of note with this device is there are three versions that appear in build.prop 32, 32_younger, 306_younger, I think, but Smartisan has confirmed they are all the same, just different production batches. If you get errors in the update process, modify this to match.
Don't drink and post children, I was editing to say I ran with what smartlinux on that site said, nothing here is my idea except for running the commands yourself.
Another good dev on the device but Chinese http://blog.cofface.com/archives/1139.html. He has an app that will boot into either (stock or custom) recovery, but like I said, do not take that 2.3.5 thing. I see they have 2.5, so let's see what happens.
wangdaning said:
Another good dev on the device but Chinese http://blog.cofface.com/archives/1139.html. He has an app that will boot into either (stock or custom) recovery, but like I said, do not take that 2.3.5 thing. I see they have 2.5, so let's see what happens.
Click to expand...
Click to collapse
Hey bro, you're a native American working in Chengdu?
xcjchandler said:
Hey bro, you're a native American working in Chengdu?
Click to expand...
Click to collapse
Yep.
Hi!
I'd like to get rid of the HTC original firmware on my U12+.
I just tried to flash GSIs of LineageOS 17 by AndyYan then AOSP 10.0 by phhusson, without luck.
I have a factory unlocked HTC U12+ (fastboot mode showing Secure Boot : Development, Secure State : S-Off, Device State : Unlocked(U)) so I went straight to the "flash GSI without TWRP" part of the official XDA tutorial: I factory reset the phone, rebooted in bootloader, then erased system and successfully flashed lineage-17.0-20191117-UNOFFICIAL-treble_arm64_avN.img.
But after reboot, I got a bootloop.
I've wanted to try the TWRP method, but upon launch it asked my password for decryption. While I'm sure of the code I've used and typed, decryption doesn't work, so TWRP didn't help.
Then I've flashed the AOSP GSI via fastboot, but then I got a "This device is corrupt. It can't be trusted and will not boot" error message.
So as suggested on another thread I've used the SD card method to flash a RUU, specifically 2Q55IMG_IMAGINE_DUGL_O80_SENSE10GP_HTC_Europe_1.30.401.2_Radio_sdm845-000201b-1807311356_release_528103_signed_2_4.zip. It flashed successfully, but then it booted to the static white HTC logo on black background and stayed there for 20 min.
I can still boot to fastboot mode/download mode, but I don't know what to do.
I can't figure what I'm doing wrong, can you help me, please?
After another attempt I've managed to go back full stock using the microSD card method.
Then I've been able to boot TWRP, which first showed a "Mount" "Decrypt data" screen, asking for a password. The 6 digits code I've used previously doesn't work. So TWRP "failed to decrypt data", also was "unable to mount storage" and "failed to unmount /system_root (device or resource busy)". As suggested, I formatted/wiped data to remove encryption.
Then I performed a factory reset, adb pushed system-quack-arm64-ab-vanilla.img to /data, then flashed it successfully to the system partition, as requested in the afore mentioned official tutorial. On reboot I get another bootloop. Bootscreens shows the HTC and Powered by Android wordmarks and also "** ORANGE **" on the top left corner of the screen.
What am I missing?! :-/
After first boot of flashed RUU at the HTC logo reboot the device. Got there myself, rebooted(using power button) and the OS booted up perfectly.
TWRP doesn't decrypt latest Pie with July Patch. So you will not decrypt it. (Wiping does not decrypt).
I used temporary TWRP, flashed permanent (with touchscreen patch), installed Magisk, Rooted, installed LeeDroid from Magisk for example.
Make sure you have a correct RUU for your CID version.
I am not sure how a project treble ROM will work on this device. You still need signed HTC drivers. I don't think we are ready now for 10 on this device for daily use. HTC did quite awful with the Pie update and many bugs are still not fixed after 6 months.
GSI tutorials advise against rooting before flashing. They advise to keep the phone full stock. What do you think about this?
I was unable to determine CID and MID yesterday from fastboot mode or TWRP, so I've downloaded the latest RUU for dual SIM and EMEA model, as my U12+ is dual SIM and I live in Europe.
Now that the phone is back to full stock, I just installed a terminal app right on the phone and executed the following:
getprop ro.cid : 11111111
getprop ro.boot.mid : empty
I understand that the phone is "SuperCID", but I don't really understand what that implies.
Regarding Treble, Treble Info by Hackintosh Five reports (translated from French by me): "Your device supports the old Project Treble version, using VNDK version 26.0."
But the U12+ is listed as supported on phhusson's wiki. A few issues are listed, but I'm fine with them.
I've read a tutorial that asks to "extract the GSI and vendor+boot zips", but then doesn't what to do with the vendor+boot zips. Do you know?
Lastly, do you know what the **GREEN** or **ORANGE** overlay means on the boot screen?
Thank you for your help!
Romano2K said:
GSI tutorials advise against rooting before flashing. They advise to keep the phone full stock. What do you think about this?
Thank you for your help!
Click to expand...
Click to collapse
SuperCID implies you can install any RUU (not specific CID). So you can "transform" your US version into european or asian... for a specific reason. No need to do that. Usually there was a specific base that was needed to install a custom ROM or Custom Recovery or people just wanted a different version because they lived in a different part of the world from where the phone was purposed.
I am guessing the **GREEN*** overlay has smth to do with the RUU (if it's embedded in the Boot animation zip (basically pictures+ sound)) or has smth to do with the nature of your tempering (S-OFF/SuperCid etc.)
with this device and serves as a warning for users/devs/internal testing.
You should find your answers on a different section. More active. I see no activity here. And it's HTC's fault for dying" on us. I myself bought the U12 just to own (probably) the last flaghsip device they make. Here's to the comeback.... but I am not sure it will be real. HTC was one of the fastest to update, for example.. until 2019. We are still with bugs and on the July patch. Right not, in reality I am just hoping for one last Pie update to fix bugs and that's it. Will give this device a 1 year run and buy something better.
So go to the Android general section where you can ask how can you compile your ROM on this device. They should help. I can not offer sufficient knowhow on this topic.
Thank you for these clarifications
The **GREEN** or **ORANGE** overlay is shown for a few seconds on the vendor logo, before boot animation. It wasn't showing before I started messing with firmwares, but nevermind
Yes unfortunately HTC is kind of dead on the smartphone front. They deserved it at the end, U12 Plus' firmware is badly translated and full of bloatware. I've been a long fan, I've had four Orange branded Windows Mobile phones and PDA phones from 2002 (17 years ago!) to 2007, then a few Android smartphones (HTC Desire <3), so I think it's sad.
Anyway I've been able to flash AOSP 10.0 GSI by phhusson with his help.
So I've just shared a quick tutorial:
https://forum.xda-developers.com/u12-plus/how-to/guide-how-to-install-generic-image-gsi-t4019151
Thank you for your help Deonix!
Romano2K said:
Thank you for these clarifications
The **GREEN** or **ORANGE** overlay is shown for a few seconds on the vendor logo, before boot animation. It wasn't showing before I started messing with firmwares, but nevermind
Yes unfortunately HTC is kind of dead on the smartphone front. They deserved it at the end, U12 Plus' firmware is badly translated and full of bloatware. I've been a long fan, I've had four Orange branded Windows Mobile phones and PDA phones from 2002 (17 years ago!) to 2007, then a few Android smartphones (HTC Desire <3), so I think it's sad.
Anyway I've been able to flash AOSP 10.0 GSI by phhusson with his help.
So I've just shared a quick tutorial:
https://forum.xda-developers.com/u12-plus/how-to/guide-how-to-install-generic-image-gsi-t4019151
Thank you for your help Deonix!
Click to expand...
Click to collapse
Interesting. Will look into your tutorial. So thank you. If the boot animation.zip was modified you will find in in root/system/[search for it] -you can lookup up each image that forms the animation to check. I myself modified the ZIP to not include the annoying audio, so i deleted it. )
So is the GSI good for daily use? I would mess around with it until i sell my HTC U11. Still using the U11 as a daily driver for the past 2 weeks. And by selling it i mean practically giving a perfectly good phone away for scrap... because it's old.
Deonix said:
I myself modified the ZIP to not include the annoying audio, so i deleted it.
Click to expand...
Click to collapse
That's clever! The HTC boot sound was annoying when I had trouble booting the bootloader, because of the tactile buttons.
Deonix said:
So is the GSI good for daily use?
Click to expand...
Click to collapse
At this point I have a big problem with AOSP 10.0: brightness is blocked at 100%. There's a workaround involving adb, but for some reason adb isn't working with this firmware, even though I've activated developer options and USB debugging. I haven't had the time to tinker yet, I'll give it a try asap and I'll report back!
Thank you again for your help
Romano2K said:
Thank you for these clarifications
The **GREEN** or **ORANGE** overlay is shown for a few seconds on the vendor logo, before boot animation. It wasn't showing before I started messing with firmwares, but nevermind
Yes unfortunately HTC is kind of dead on the smartphone front. They deserved it at the end, U12 Plus' firmware is badly translated and full of bloatware. I've been a long fan, I've had four Orange branded Windows Mobile phones and PDA phones from 2002 (17 years ago!) to 2007, then a few Android smartphones (HTC Desire <3), so I think it's sad.
Anyway I've been able to flash AOSP 10.0 GSI by phhusson with his help.
So I've just shared a quick tutorial:
https://forum.xda-developers.com/u12-plus/how-to/guide-how-to-install-generic-image-gsi-t4019151
Thank you for your help Deonix!
Click to expand...
Click to collapse
Did Bluetooth work for you on AOSP? Tried to install a few GSIs over the last couple of days but I cannot get Bluetooth working for calls or media. Apparently it's a known issue but none of the fixes I can find here on the forums seem to work for me. Just wondered what your experience was on another U12. I even tried your guide but still no Bluetooth for me.
Useful post about the GREEN message.
After several days reading into topic, many tries, (including bricking and unbricking my P20 two times down to fastboot access only..), I still not at my goal: Taking full ownership aka. get root of slick & clean device.
Thanks to @OldDroid and his crew (THX!) now I have a working AOSP 10 Preview 2. It was flashed over a fully working EML-L29 9.0.0.293 (C432E7R1P11), bootloader & FRP unlocked, installed from eRecovery internal download(after second brick..) Thankfully I refused to update to 9.1 before due to /system read-only problems i red about. So everything, including recovery should be genuine. I will try to keep all the Google inside an Island and restrict it as far as possible with firewall.
Now I question myself how I can obtain root without bricking this wonderful machine again. I guess I will need Canary Magisk Manager from this link:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Switching channel to canary too, going the recovery_ramdisk patching route. (TWRP I already miss you!!)
I already downloaded EML-LGRP2-OVS 9.0.0.293 (FullOTA-MF) via Firmwarefinder to extract recovery_ramdisk from it. As I only flashed system I guess this should be the version I need to patch with Magisk?
I know, this is pretty unknown territory, but on OmniROM 5 beta I the non working touchscreen bug. Would give it a second try if there is no other way, maybe starting from a lower EMUI 9 version? If anybody could confirm my plan, or tell me its rubbish, I would be thankful.
@mods: This whole Treble thing makes it quite confusing, if you believe this post would get more attention in another place, feel free to move it. thx!
Hi all,
My op6 is stuck, unable to reboot normally with the famous Qualcomm Crashdump mode message.
The phone has the bootloader unlocked, with TWRP recovery.
1 day ago I could access the recovery even reboot with the power+volume buttons, but it got to a point where it crashes all the time, unable to do anything.
Currently is only able to enter fastboot mode.
I have heard about the MSMDownload Tool.
- Does this tool keep the files/data in the internal memory?
For me the most important thing is to be able to recover the data.
The qualcom dumpcrash mode returns several different messages like:
- stack-protector kernel stack is corrupted in:--schedule*0xB90/OXOd0 (not exact numbers)
- fatal exceptinforece_signalinject.isra.8
Is there any chance of trying something?
I am extremely anxious and worried about the situation
Please help.
Ganapatya said:
Hi all,
My op6 is stuck, unable to reboot normally with the famous Qualcomm Crashdump mode message.
The phone has the bootloader unlocked, with TWRP recovery.
1 day ago I could access the recovery even reboot with the power+volume buttons, but it got to a point where it crashes all the time, unable to do anything.
Currently is only able to enter fastboot mode.
I have heard about the MSMDownload Tool.
- Does this tool keep the files/data in the internal memory?
For me the most important thing is to be able to recover the data.
The qualcom dumpcrash mode returns several different messages like:
- stack-protector kernel stack is corrupted in:--schedule*0xB90/OXOd0 (not exact numbers)
- fatal exceptinforece_signalinject.isra.8
Is there any chance of trying something?
I am extremely anxious and worried about the situation
Please help.
Click to expand...
Click to collapse
to start: it's good thing that you can get into fastboot mode. From there you should be able to do a complete re-install of your device, e.g. using the official LineageOS instructions.
Now to your situation: unfortunately you don't write too much about it like, is your phone running stock OOS or some custom ROM? If it's a custom ROM I'd say you open a topic in the according thread. Then: how much do you know about flashing recoveries, ROMs etc.
Regarding your data: in your current situation it may be extremely difficult if not impossible to secure any personal data now. How I understand it you cannot access the crucial partitions from the bootloader, at least I never heard of methods to get there. Although, people more knowledgeable than me may know of ways. So I do hope you are having recent backups at hand, on your PC or where-ever.
In that case I would start all over (and that's how I got out of a similar situation several months ago): flash recovery, flash latest OOS to both slots, factory reset / wipe everything (to remove any encrypted data you won't be able to access anyways), flash you ROM of choice incl. other part like GAPPS, if needed, do basic setup and then finally try to recover anything that is in you backups.
I wish you a lot of patience and good luck, you'll need it, I'm afraid.
lm089 said:
to start: it's good thing that you can get into fastboot mode. From there you should be able to do a complete re-install of your device, e.g. using the official LineageOS instructions.
Now to your situation: unfortunately you don't write too much about it like, is your phone running stock OOS or some custom ROM? If it's a custom ROM I'd say you open a topic in the according thread. Then: how much do you know about flashing recoveries, ROMs etc.
Regarding your data: in your current situation it may be extremely difficult if not impossible to secure any personal data now. How I understand it you cannot access the crucial partitions from the bootloader, at least I never heard of methods to get there. Although, people more knowledgeable than me may know of ways. So I do hope you are having recent backups at hand, on your PC or where-ever.
In that case I would start all over (and that's how I got out of a similar situation several months ago): flash recovery, flash latest OOS to both slots, factory reset / wipe everything (to remove any encrypted data you won't be able to access anyways), flash you ROM of choice incl. other part like GAPPS, if needed, do basic setup and then finally try to recover anything that is in you backups.
I wish you a lot of patience and good luck, you'll need it, I'm afraid.
Click to expand...
Click to collapse
Thank you for your reply.
is your phone running stock OOS or some custom ROM?
Click to expand...
Click to collapse
Stock OOS, android 10, last release.
Then: how much do you know about flashing recoveries, ROMs etc.
Click to expand...
Click to collapse
I have basic experience installing customs roms, rooting, twrp, unlock fastboot...following tutorials, of course.
Regarding your data: in your current situation it may be extremely difficult if not impossible to secure any personal data now. How I understand it you cannot access the crucial partitions from the bootloader, at least I never heard of methods to get there. Although, people more knowledgeable than me may know of ways. So I do hope you are having recent backups at hand, on your PC or where-ever.
Click to expand...
Click to collapse
here someone says that in theory it would be possible if you have the usb debugging enable, but silly me I had it open but I deactivated it I think, so I'm not sure if I have access or not.
OnePlus 6 Stuck At "Qualcomm Crashdump" Screen All A Sudden | Data Retrieval Critical
Hi good people at XDA. This is my first post on this website and I am absolutely hoping to receive help from you all to find a way out of the depressing and extremely anxious situation I'm in. I was using my OP6 normally today and while I was...
forum.xda-developers.com
Code:
adb devices
mkdir "C:\RECOVERED_DATA"
adb pull /sdcard C:\RECOVERED_DATA
and then finally try to recover anything that is in you backups.
Click to expand...
Click to collapse
but if I do all that flashing process any backups that are in the internal memory will be erased, right?
I had photos, files, whatsapp chat history, documents...etc and they were all in the internal memory. It is not a great loss but it is important for me to be able to recover it.
in your current situation it may be extremely difficult if not impossible to secure any personal data now
Click to expand...
Click to collapse
for me it is more important to recover the files than to recover the phone. your words are discouraging
I have read other posts and maybe being able to install on top (dirty install) the same rom I have, would leave the system as it, is being able to access my files. Not even installing the whole rom but extracting the boot image from the rom and then installing it. but I don't know if I can install a rom or boot image from fastboot, or if I need to have a working TWRP first.
It is said here:
- https://forum.xda-developers.com/t/...over-without-data-loss.4080725/#post-82257413
- https://forum.xda-developers.com/t/...over-without-data-loss.4080725/#post-82261087
Ganapatya said:
your words are discouraging
Click to expand...
Click to collapse
of course that is not my intention. I just try to be realistic
As I wrote in my post, my knowledge is quite basic. I know what I read , and what I experienced with my different devices. So again: you may find instructions and real-life stories showing you ways out of there.
My experience is that you cannot connect your OP6 phone to your PC via ADB while in bootloader / fastboot mode.
a) It's either one or the other: bootloader <=> fastboot or recovery / system <=> adb. Other devices may have different options but we're not talking about Samsung but about OP.
b) I did some additional research last night but I couldn't find a single source talking about *read* access to user data from fastboot. All you can do there is flash i.e. overwrite partitions
c) keep in mind that most probably your personal data are encrypted. So even if you find a way to access your personal data from bootloader / fastboot you may not be able to read it
d) I never used MSMtool, never had to. But I did some more research about it. It looks as if you could re-flash stock ROM using that tool but to the cost of wiping everything. At least that is what the tutorials I found are saying
That said I'd say you don't have much to lose and can go trying out some things.
From my experience the qualcomm crashdump error can have it's source in a malfunctioning recovery solution; I had that when flashing a wrong TWRP version that would not be in harmony with the previously flashed OOS firmware.
From what I read our devices don't have a separate recovery partition, instead it somehow lives somewhere/somehow in the boot partition (experts: please don't crucify me if that is wrong ). So if that is the case one idea would be to extract the boot image from the stock ROM image then flash that to /boot/ from fastboot. Don't know whether that really works and helps, but in theory you would have a default boot partition and kernel *without* a conflicting recovery solution.
In case you're successful you may be able to boot into system and make backups of everything that's valuable to you.
Again: this is extremely wild guessing here, and you'll have to read in a bit on how to properly extract parts of the ROM image.
I also would *strongly* recommend that you continue asking for help in a more technical thread like the LOS19.1 one or Funk Wizard's thread about unlocking and flashing our OP6.
I wish you all luck you need!
I think your best bet it a HW solution, get someone to:
1. replace the modem IC, it's the possible cause of the qualcomm crash
2. solder a direct connection to the internal memory so you can recover your data