Related
Hi everybody,
Yesterday I was using my beloved(!) Vivo Nex S (Chinese 256GB version, no root, removed some bloatware some months ago, Nova launcher, rest original) in a normal way, put it away and wanted to use it again about 1 minute later again. When I tried to access the fingerprint reader, I recognized, that the fingerprint reader didn't get green when approaching my finger. After about 2 seconds of trying, my Nex made a reset.
I could only turn it on by pressing the power button for more than 10 seconds begining from there. Until then, I just see the Nex Logo, then the stars flying, then the Nex Logo again. It changes colors, again and again, and after about 2 minutes it shuts down and vibrates twice.
Starting the phone while pressing down the volume up button at the same time, brings me to the chinese Fastboot mode menu. I've the desicion between reboot (no other effect than described above) and Recovery. Chosing recovery, it shows the Vivo Logo again and after about 2 seconds "Your device is corrupt. It can't be trusted and will not boot. Visit this link on another device: g.co/ABH". After 30 seconds it shuts down. No access to the recovery menu!
I contacted the (Indian) chat from Vivo support. The Vivo support doesn't want to be responsible, because I bought my phone in China. Sending it back would probably mean, that I definitely lose my data and that it will take a long time until it's back.
So I tried to get access over USB. I can see "Qualcomm HS-USB Diagnostics 900E" [SIC, it's NOT 9008!] on COM7. I then tried to get access using ADB, where I'm really unfamiliar with. Didn't get any connection. So I tried QFIL, where I could see my phone in the top line of the program, but didn't get any access. (Neither I'm a pro there...)
So, now my biggest hope at the moment: Is there a possibility to get access to my phone using ASTool? I read about it, that it should be a great helper in such problems, and that there could be some hope, that I could even save my data by just flashing some "sectors" of the original system. But there's another problem: This software seems to be not freeware, and all the hacks around have trojans inside.
What do you think about it? Does anybody of you pros have a clue, how to get into the phone, flash a new boot there and how to save my data (about 220GB, desoldering of the memory is not (yet) an option)?
Thanks A LOT in advance to everyone!
Edimahler said:
Hi everybody,
Yesterday I was using my beloved(!) Vivo Nex S (Chinese 256GB version, no root, removed some bloatware some months ago, Nova launcher, rest original) in a normal way, put it away and wanted to use it again about 1 minute later again. When I tried to access the fingerprint reader, I recognized, that the fingerprint reader didn't get green when approaching my finger. After about 2 seconds of trying, my Nex made a reset.
I could only turn it on by pressing the power button for more than 10 seconds begining from there. Until then, I just see the Nex Logo, then the stars flying, then the Nex Logo again. It changes colors, again and again, and after about 2 minutes it shuts down and vibrates twice.
Starting the phone while pressing down the volume up button at the same time, brings me to the chinese Fastboot mode menu. I've the desicion between reboot (no other effect than described above) and Recovery. Chosing recovery, it shows the Vivo Logo again and after about 2 seconds "Your device is corrupt. It can't be trusted and will not boot. Visit this link on another device: g.co/ABH". After 30 seconds it shuts down. No access to the recovery menu!
I contacted the (Indian) chat from Vivo support. The Vivo support doesn't want to be responsible, because I bought my phone in China. Sending it back would probably mean, that I definitely lose my data and that it will take a long time until it's back.
So I tried to get access over USB. I can see "Qualcomm HS-USB Diagnostics 900E" [SIC, it's NOT 9008!] on COM7. I then tried to get access using ADB, where I'm really unfamiliar with. Didn't get any connection. So I tried QFIL, where I could see my phone in the top line of the program, but didn't get any access. (Neither I'm a pro there...)
So, now my biggest hope at the moment: Is there a possibility to get access to my phone using ASTool? I read about it, that it should be a great helper in such problems, and that there could be some hope, that I could even save my data by just flashing some "sectors" of the original system. But there's another problem: This software seems to be not freeware, and all the hacks around have trojans inside.
What do you think about it? Does anybody of you pros have a clue, how to get into the phone, flash a new boot there and how to save my data (about 220GB, desoldering of the memory is not (yet) an option)?
Thanks A LOT in advance to everyone!
Click to expand...
Click to collapse
That sucks. I don't have a solution but I'm curious as to what is taking up 220GB on your phone?
I suggest rescuing the phone first and forgetting about the data.
Twotems said:
That sucks. I don't have a solution but I'm curious as to what is taking up 220GB on your phone?
I suggest rescuing the phone first and forgetting about the data.
Click to expand...
Click to collapse
Well... As long as there is some free flash space, it will be used, right? There are especially 4K movies from our trip to Australia and from my construction works at home (I'm building a pretty special smart home), because the picture quality of the phone was much better than the one of the Lumix TZ81. Some of them luckily have been backuped already.
Well, I could also try to wipe the whole memory first, but I thought I could try to just flash the boot area and get back my data as well and then afterwards make a proper installation again.
But how to enter the phone now again? Any ideas? And should I try the global ROM then (would be my favourite) or just the Chinese again?
Thanks for any comments...
Edimahler said:
Well... As long as there is some free flash space, it will be used, right? There are especially 4K movies from our trip to Australia and from my construction works at home (I'm building a pretty special smart home), because the picture quality of the phone was much better than the one of the Lumix TZ81. Some of them luckily have been backuped already.
Well, I could also try to wipe the whole memory first, but I thought I could try to just flash the boot area and get back my data as well and then afterwards make a proper installation again.
But how to enter the phone now again? Any ideas? And should I try the global ROM then (would be my favourite) or just the Chinese again?
Thanks for any comments...
Click to expand...
Click to collapse
I can't help you unfortunately. But I know you can't flash the global rom to the Chinese version and vice versa.
The only alternative solution is find experience third-party service in your country.
Otherwise you must send it to China and local Vivo service point.
And always take backup your staff on phone to pc or external drive now you wouldn't have worry if you had taken backup.
No 1 rule owning any kind electronic devices is to have backup because you never know with electronics device they're always a chance for hardware failure.
You don't leave this thing to luck.
Sent from my iPad using Tapatalk
Yes, I read a lot about the global ROM on Chinese Vivo Nex in the according thread in the meantime. I'm even thinking in opening my phone and bridge the contacts to get into the 9008 mode forballvofbyou (and for me of course ) instead of sending it back to China. But I'm afraid that I wouldn't even recognize, if I was successful there...
And yes, of course I learned that a (recent) backup would have been nice...
Now, for the moment I plan to flash the chinese ROM first again, in order to maybe being able to savevsome of my data first. Is AFT the right way? There's some kind of a "hack" needed in order to use it, and this one seems to have a Trojan inside! Isvthere a "trojanfree" solution somewhere?
Best regards and thanks a lot for your replies!
Disable Windows defender and run the tool.
That's what I did myself when tried last summer flash global rom to Chinese version.
There's instructions and video tutorial here at Vivo Nex thread a member who upload about how to flash using AFTool
https://forum.xda-developers.com/nex/how-to/rom-vivo-nex-global-rom-1-7-18-service-t3831866/page2
Post 15.
But in order to flash Chinese rom you need having the full zip file and I don't know if there's a indipended source of downloaded.
Easy firmware site has only global rom but not Chinese one last time check.
And doubt Vivo support will provide you that file you'll need in order re flashing you existing Chinese rom version.
Sent from my iPad using Tapatalk
paatha13 said:
Disable Windows defender and run the tool.
Click to expand...
Click to collapse
Well, there's a Trojan in the authorisation tool in the version I got. Did you have to activate yours using this activation tool under your link, or is it usable without this activation as well?
paatha13 said:
But in order to flash Chinese rom you need having the full zip file and I don't know if there's a indipended source of downloaded.
Easy firmware site has only global rom but not Chinese one last time check.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I think, I would even need the Flashfile itself, as I'm not able to transfer the files from a ZIP-file into the internal memory anymore. And yes, you're right. Have been searching the Chinese ROM now for hours, but didn't find it anywhere... :crying:
Found the Chinese (official!) download of the ROM, just for those, who are interested:
http://sysupwrdl.vivo.com.cn/upgrad...es/PD1805_A_1.21.3-update-full_1541422501.zip
It's not even needed to have a stupid Baidu account (which is just registerable using a chinese phone number, which again is just possible to use a Russian phone number creater, which again is not so easy because most of the numbers are already bloked, which...). No, it's just a normal, direct download link!
And hey guys: This evening my Vivo Nex just started to be able to enter the Fastboot menu again!!! Why ever, but that's partial good news (for me at least).
And again for all of them, who want to have an English translation of the menu structure; Here it is !
- Reboot System
- Wipe Data
---- Clear Cache
---- Restore all settings
---- Clear all data
---- Return
- Install Update
---- Mobile phone storage
---- SD card
---- Return
- System repair mode
---- Enter system repair mode
--------- Restart
--------- Download latest version and installation (using WLAN)
--------- Shutdown
---- Cancel
- Power down
- Advanced options
---- Upgrade via USB
---- Upgrade Systems & 3rd party applications
--------- Mobile phone storage
--------- SD card
--------- Return
---- Verify system file integrity
---- Open ADB restart
---- View the upgrade log
---- Return
Some words, what I've seen on my soft bricked phone this evening:
- Wipe data -- Clear Cache: Tried this, but without any changes in behaviour
- Install Update -- Mobile phone storage: Didn't find any backup from Vivo in all the folders and subfolders on my phone. Even though, I could see the whole folder structure from my phone, so theoretically all the data are still there!
- Install Update -- SD card: Just trying this, as soon as the download of the Chinese ROM finished. Maybe with a dirty Flash I would be able to reboot?
BTW: IS THERE A WAY TO JUST FLASH SOME SINGLE FILES INSTEAD OF THE WHOLE ZIP FILE?
- System repair mode -- Download latest version and installation: A message pops up, that nearby WLANs are being searched. But after about 10 seconds it turns back to the previous menu, whithout any success.
- Advanced options -- Verify system file integrity: I get a pass here!!! Unbelievable... Don't know what's still hindering my phone to boot up just in a normal way...
- Advanced options -- Open ADB restart: Could this maybe help to enter the 9008 mode, which many of you out there are trying to reach? Don't understand this in detail, so please don't be mad about me, if this is a silly question...
Thanks for your patience with me, and hope, that some of the information could maybe also help someone of you out there...?
Edimahler said:
Well, there's a Trojan in the authorisation tool in the version I got. Did you have to activate yours using this activation tool under your link, or is it usable without this activation as well?
Click to expand...
Click to collapse
Use this and check for Trojan without extracking the zip file.
virustotal.com
Windows defender its not that trustable and it's full of **** many times when detect something that's not harmful actually.
Yes you need to activate via username and password given on instructions.
Sent from my iPad using Tapatalk
paatha13 said:
Yes you need to activate via username and password given on instructions.
Click to expand...
Click to collapse
Seems as I found an already patched version now, which also seems to be free of malware (at least on my PC, using the Windows defender):
https://mega.nz/#!zrohlSBL!5geOCXwSFHMPCACKjOqLNVF_V8t1jFvZc6FrZj63xOM
Next problem: Can I use AFTool (which is up now) to flash the Chinese ROM to my Vivo Nex again, without having the 9008 mode? And how to do it? Most videos showing solutions in the internet are about cracking the software and not how to use it afterwards...
Well, I tried to find the "fastboot_flash_all" file in my downloaded version of the firmware. But can't find it there (see below).
Because of this I tried using QFIL, but can't find the MBN file again... Boah, it's a really hard puzzle this time...
Unfortunately I can't help you further as my knowledge and only experience was when tried last summer to flash global to Chinese version but it failed and dropped any further examination and leave it as it is.
I haven't tried re flashing existing rom wearing Chinese version device using AFTOOL.
Vivo tools really sucks on those aspect and they're not helping either but just saying to anyone has problem visit Vivo official service.
All the info you can get here xda is the specific topic only provide you above.
Maybe you can try sent pm to member who gave all the information and idea of how using AFTOOL.
Sent from my iPad using Tapatalk
paatha13 said:
Unfortunately I can't help you further as my knowledge and only experience was when tried last summer to flash global to Chinese version but it failed and dropped any further examination and leave it as it is.
Click to expand...
Click to collapse
Dear paatha13, Thanks anyway for your support and your ideas! In the meantime I maybe "accidentially" unlocked the boatloader. Being desperate, I tried everything. Hope it didn't really happen or at least, that it won't have an influence on the warranty of the device... Yes, maybe it's just better to give up there and send it back for "Mainboard exchange", as they call it.
If you're still interested in trying to change to the global version (for me it's really in the background at the moment), maybe this "Unlocking-tool" could help you somehow. I posted the link in the according thread here:
https://forum.xda-developers.com/nex/how-to/guide-vivo-nex-s-apps-safe-to-uninstall-t3813308/page17#post79131637
(in Message #165)
paatha13 said:
Vivo tools really sucks on those aspect and they're not helping either but just saying to anyone has problem visit Vivo official service.
Click to expand...
Click to collapse
Completely agree, it really sucks, that they aren't interested in helping in an easy way by blocking everything.
Well, thanks again, hope I'll be able to help also once. Even if it's only in a "mental supporting" way.
Hi Everyone,
Living in Japan, we have no official channel to purchase a OnePlus handset here.
Really wanted to get a OnePlus 7 Pro as I felt it is the best model on the market as of today.
Knowing that, I got mine on Amazon Japan from a HK online shop which had very good reputation.
Now, the problem is these phones always come already opened as they say they need to confirm operation before sending it.
I have been reading news and article about this where we see more third party companies flash their roms with malware/ransomeware already built in...
In these situation, the best way to clean the phone is to do a full re-install of the OS.
I did review a bunch of article on XDA and it seems that now, due to the A/B partition setup, we can't just use official OnePlus image to load from the fastboot easily.
We have to rely on community provided too and stock rom to be able to do so....
When I raised the question to OnePlus and Oneplus forums, they mentioned to me that installed the updated like here (Page: support.oneplus.com/app/answers/detail/a_id/4312/~/oxygen-os-for-oneplus-7-pro)would do the trick using the local update function.
What I was directed to do is use the recovery boot to delete system settings/cache and everything data user and then, run the local update. Doing so, that would do it while not using community tools.
Here are my questions and which I would hope to get your experience:
1 Is the process I did really does use a brand new clean OS and do not rely/integrate part of the OS that came with the handset originally (that was the target).
2 Is there a way for me using OnePlus only provided tools and image to fully delete the phone and install the OS (maybe I am thinking this too much like a PC which I have more experience with...)
3 The OS looks fine and no strange apps shows up at all but how can I be sure nothing dodgy is running? Is there tools I could use to confirm this?
Sorry if I sound paranoid. Ideally, I understand the best thing to do was to buy directly from Oneplus and work a way to have it shipped to Japan but thought it would be interesting for me to learn more about android.
With previous Oneplus, it was easier as they were provided this type of official file for recovery but they stopped...
Thank you again for your time and hopping to learn more about how new android setup works.
Is the bootloader locked? Is Widevine (Netflix HD) certification still there? You can check these things to see if the phone has been tampered with.
brissoukun said:
Hi Everyone,
When I raised the question to OnePlus and Oneplus forums, they mentioned to me that installed the updated like here (Page: support.oneplus.com/app/answers/detail/a_id/4312/~/oxygen-os-for-oneplus-7-pro)would do the trick using the local update function.
What I was directed to do is use the recovery boot to delete system settings/cache and everything data user and then, run the local update. Doing so, that would do it while not using community tools.
Here are my questions and which I would hope to get your experience:
1 Is the process I did really does use a brand new clean OS and do not rely/integrate part of the OS that came with the handset originally (that was the target).
2 Is there a way for me using OnePlus only provided tools and image to fully delete the phone and install the OS (maybe I am thinking this too much like a PC which I have more experience with...)
3 The OS looks fine and no strange apps shows up at all but how can I be sure nothing dodgy is running? Is there tools I could use to confirm this?
Thank you again for your time and hopping to learn more about how new android setup works.
Click to expand...
Click to collapse
Good questions. Before you start, check the model number of your device through Settings > About. I'm assuming it's the international/global/unlocked version (GM1917).
With regard to question 1, a full build downloaded from the link you provided should contain every part of the OS, and flashing it through local update should overwrite anything that was there before. Before flashing, I would perform a full data wipe through recovery like you mentioned.
Q2: There is an MSM tool that will completely flash a system image for the OP7 Pro. I don't think they're generally intended for public use but they always get leaked anyways. They write an image (in the case of OnePlus, a .ops file) to the phone using a PC and USB connection. Here is a link to a thread which contains the MSM tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Download the tool for the model of your phone (probably the international, firmware GM21AA), and extract its contents into a directory. In order for the tool to work, you need the OnePlus USB drivers installed on your PC. Plug the phone into your PC with it on, and enable USB file transfer. Open File Explorer and you should see a drive labeled "OnePlus drivers" or similar. Open it and run the driver setup executable file. You'll also need ADB to make your phone reboot into a mode that will allow the tool to perform its tasks. Here is a guide to installing ADB:
https://www.xda-developers.com/what-is-adb/
Once you've set that up, make sure the phone is plugged into the PC and the MSM tool is open. Make the phone boot into edl mode by typing
Code:
adb reboot edl
and once it says Connected next to a COM port in the tool, press start. Don't interrupt the process until it completes the download and the status message turns green. The phone should automatically reboot. This method is arguably more risky than using the local upgrade option, so do it at your own risk.
Q3: Make sure that OEM unlocking is turned off in developer settings and that the bootloader is locked (if the bootloader is unlocked, you'll see a yellow warning message after you power on the device from a power off state). Without an unlocked bootloader it would be pretty difficult to make any deep modifications to the device.
Hi @Zocker1304 and @TManchu,
Please let me thank you very much first for your kind and detailed reply, this is really welcome.
@Zocker1304:
I checked using the ADB/Fastboot connection that indeed, the Bootloader is locked so, that looks good.
Also installed (using a separate Google account) DRM Info app to confirm that the Widevine is properly installed and at L1 level which indeed again, looks good.
@TManchu
Thank you again for your very detailed reply! This was exactly what I needed as information.
I did already exactly as mentioned for the #1 so, it looks I should be good now with a proper rom from OnePlus (and did a full wipe in the Recovery boot mode)
For #2, I think I will skip that since as you rightly said, with #1, it should be fine so, prefer to keep with the recommended step.
For #3, we are covering what Zocker1304 mentioned too and I could confirm it.
My only concern about #3 was that you can actually relock the bootloader but (and please correct me If I am wrong), you can only do so if you are using stock OnePlus images (to date...seems like dev teams are working to have this changed? Bootloader locked with custom firmware?) which then means the image is safe.
I suppose the last item was my only open query for your thoughts but so far, the handset looks fine.
Thanks to you and the community, I have learned about the A/B partition scheme, msm tool, Fastboot/Recovery mode and Bootloader and ADB tools.
It is always good to learn more about the tech we use (especially phones, we have so many sensitive information stored into them today).
Not being careful could potentially means quite a lot of troubles down the road with Ransomeware/data leak tools.
Of course again, I could have simply purchased a JP phone from a brick and mortar shop next to my place and be fine with it. :silly:
brissoukun said:
.
For #3, we are covering what Zocker1304 mentioned too and I could confirm it.
My only concern about #3 was that you can actually relock the bootloader but (and please correct me If I am wrong), you can only do so if you are using stock OnePlus images (to date...seems like dev teams are working to have this changed? Bootloader locked with custom firmware?) which then means the image is safe.
I suppose the last item was my only open query for your thoughts but so far, the handset looks fine.
Thanks to you and the community, I have learned about the A/B partition scheme, msm tool, Fastboot/Recovery mode and Bootloader and ADB tools.
It is always good to learn more about the tech we use (especially phones, we have so many sensitive information stored into them today).
Not being careful could potentially means quite a lot of troubles down the road with Ransomeware/data leak tools.
Of course again, I could have simply purchased a JP phone from a brick and mortar shop next to my place and be fine with it. :silly:
Click to expand...
Click to collapse
No problem! I’ve just done some reading and from what I understand, re-locking the bootloader on anything other than a completely stock ROM will result in a bricked phone. I believe this is due to the way Android handles data encryption. If what you’ve heard is true, being able to lock your bootloader on a custom ROM would be great for device security. However, should something go wrong with the ROM having a locked bootloader might make it more difficult to fix.
I know that there are ways to sign system and boot images so that you can lock the bootloader with them installed, but I think that would still show a warning though I'm not sure.
Anyways, if all the build dates and numbers in the system info are correct, the firmware should be stock and as long as the bootloader is locked too, I don't believe you can tamper with that.
Hi Gents,
Thank you very much for the answer to the thread and much appreciated.
Apologies for not getting back to you all earlier as yesterday was family day...haha!
Well, since things looked good on the OS and the build, I went ahead and started to use the phone properly setting up my accounts. It did give me some incentive to get all my sensitive accounts setup with 2FA so that in case I get hacked with my passwords in the future...they would still need the 2fa (using Google Authenticator).
I did check also all system apps/running process and didn't see anything shady.
Just for reference, here were the type of articles I was refering too for the OS being plagued with malware even out of the box:
Page_theverge.com/2019/6/6/18655755/google-android-malware-triada-ota-rom-ads-spam-oem (sorry gents, new account, cannot put links yet)
However here, it seems it is due to lax review from the maker to third party tools which were including malware...
To have the same level on the oneplus I bought from the HK shop, they would have needed access to OnePlus Dev team to inject the malware in official image (knowing anyway I have re-installed a new image from the local update).
Otherwise, I was reading on the web about the fact to relock the bootloader with a custom roam and there seems to have a lot of messages but not concrete steps. It seems it depends a lot on phone model and brand.
When you are checking
Page_gizmochina.com/2019/06/10/relock-bootloader-oneplus-7-pro/
This is where you can read at the end:
"The above method only works if OnePlus 7 Pro is running on stock recovery and stock firmware. The ability to relock devices running custom recovery is expected in the next few weeks. "
That was published last month so, not sure if they got this to work on the OnePlus 7 pro yet.
So that's it, I am now using my new device which looks to work great and hopefully, won't get any bugs down the road.
I appreciate you taking the time to get back to me and will continue to learn about android.:good:
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.
Hi everyone,
I seriously need some advices since I can't manage to solve my problem.
BEFORE YOU READ:
A month has passed, and I couldn't manage to recover my phone. I decided to buy a brand new phone for my brother.
The thread is going to stay there, since I hope it could be useful for people luckier than myself
The Problem:
My brother found his phone (the Redmi Note 6 Pro) turned off.
He wasn't able to turn it on.
I could manage to wake it up by pressing volume-up + power
very strangely, it directly turned into the OS (and not into the TWRP)
"but ok, at least it turned on" I thought
After only a few minutes, the phone suddenly turned off and from there my journey started to became a p**p
I'm not able to enter into recovery, and I'm not able to enter into fastboot neither.
I realized that the phone is fu--- ehmm I mean bricked. The funny thing is that we haven't done anything strange.
Some useful informations:
latest TWRP was installed
I was on the latest Pixel Experience Extended ROM (Android 11)
No custom kernel (I kept the kernel included in the PEE ROM)
No Root
What I tried:
Since it was impossible to do anything, I followed some guides (found here and on Youtube as well) and I opened my phone (if I'm lucky, I haven't destroyed anything ---- YET ).
I managed to enter in EDL mode
my Windows PC is able to recognize it on the COM / LPT ports as Qualcomm HS-USB QDLoader 9008
I downloaded the Mi Flash Tool
I downloaded the Boot Firmware and the two special files (prog_emmc_firehose_Sdm660_ddr.elf and prog_emmc_firehose_Sdm660_lite.elf) following this video link (please don't blame me, but I haven't found anything here)
I put the files inside the image folder
I tried to flash the firmware via Mi Flash but I got a funny error: "cannot receive hello packet"
Thinking that I was doing something wrong, I downloaded the latest Mi Flash Tool but nothing
I downloaded the latest tulip global image but nothing
I authenticated with the mi account into the tool (technically it shouldn't be needed) and... guess what? nothing.
I'm totally out of ideas. Of course I tried to reconnect the phone multiple times (shortening the two pins every time). I also tried to disconnect the battery and going USB-power-only.
Every time I get the "cannot receive hello packet" error, and suddenly the procedure fails saying "Riferimento ad un oggetto non impostato su un'istanza di un oggetto" (italian, that means "Object reference not set to an instance of an object").
EDIT: this error is also listed as "Null Reference Exception" (since it seems to be caused by the following exception: "System.NullReferenceException" - as you can read in the log I included)
Any ideas? What else can I try? Have I done anything wrong?
This never happened me before in almost 10 years of flashing. And, you know what? I just learned how to destr--- ehm open a phone! (...I used the little metal tab inside a Monster Energy can as tool *coff coff* -- C Y B E R P U N K)
Thanks to everyone that will try to help me. Every suggestion is appreciated*
*but please don't suggest me a trash can
Mi Flash Log:
Spoiler: Mi Flash Log
[15:18:15 COM6]:MiFlash 2020.3.14.0
[15:18:15 COM6]:vboytest index:6
[15:18:15 COM6]:flash in thread name:COM6,id:15
[15:18:15 COM6]:sw in images
[15:18:15 COM6]:flash in thread name:COM6,id:15
[15:18:15 COM6]:vboytest do open :
[15:18:15 COM6]: serial port COM6 opend successfully
[15:18:15 COM6]:[COM6]:start flash.
[15:18:16 COM6]:cannot receive hello packet,MiFlash is trying to reset status!
[15:18:17 COM6]:try to reset status.
[15:18:17 COM6]:Switch mode back
[15:18:17 COM6]:cannot receive hello packet,MiFlash is trying to reset status!
[15:18:17 COM6]:System.NullReferenceException: Riferimento a un oggetto non impostato su un'istanza di oggetto.
in XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer(Int32 programmertype)
in XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash() in XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer(Int32 programmertype)
in XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash()
[15:18:17 COM6]:no provision exit:COM6
[15:18:17 COM6]:flashSuccess False
[15:18:17 COM6]:isFactory False CheckCPUID False
[15:18:18 COM6]:before:flashSuccess is False set IsUpdate:True set IsDone True
[15:18:18 COM6]:after:flashSuccess is False set IsUpdate:false set IsDone true
Little Update:
tried to disable windows' driver signature: same issue
tried to disconnect the phone display (seems weird, but why not giving it a chance): same issue.
I also downloaded Mi Flash Pro, which should work even without an authorized Mi account. But I get the same damn error.
Disperate up. You guys are my last hope.
Hello @Gh_Racer I got the exact same problem. Found my phone turned off 2 days ago, when I tried to turn it on the miui logo appeared. turned off and that was it. Not been able to turn it on after that. Did u by any chance fix the problem? Thanks!
fawziX said:
Hello @Gh_Racer I got the exact same problem. Found my phone turned off 2 days ago, when I tried to turn it on the miui logo appeared. turned off and that was it. Not been able to turn it on after that. Did u by any chance fix the problem? Thanks!
Click to expand...
Click to collapse
Damn, really? That's pretty disappointing. These cases are becoming suspicious... maybe that could be some kind of programmed obsolescence(?)
Just for curiosity: were you on stock MIUI or did you have any kind of modifications?
Unfortunately, I couldn't manage to do anything so far.
I loaned my old OnePlus 5T to my brother for now and I think that we'll buy a Redmi Note 10 as soon it will became available in our country. Of course I'm still here for any kind of suggestion until then.
Gh_Racer said:
Damn, really? That's pretty disappointing. These cases are becoming suspicious... maybe that could be some kind of programmed obsolescence(?)
Just for curiosity: were you on stock MIUI or did you have any kind of modifications?
Unfortunately, I couldn't manage to do anything so far.
I loaned my old OnePlus 5T to my brother for now and I think that we'll buy a Redmi Note 10 as soon it will became available in our country. Of course I'm still here for any kind of suggestion until then.
Click to expand...
Click to collapse
I was on the official MIUI, I didn't do any kind of modifications to the phone. I found it also weird that we have the same problem around the same time. Maybe it's related to an automatic update? mine was like that when I woke up in the morning the day before it was in perfect condition. Let me know if u manage to somehow fix it and I'll let u know if i get it working. (btw I also ordered a new XIAOMI phone red note 9 pro lol)
fawziX said:
I was on the official MIUI, I didn't do any kind of modifications to the phone. I found it also weird that we have the same problem around the same time. Maybe it's related to an automatic update? mine was like that when I woke up in the morning the day before it was in perfect condition. Let me know if u manage to somehow fix it and I'll let u know if i get it working. (btw I also ordered a new XIAOMI phone red note 9 pro lol)
Click to expand...
Click to collapse
I was on a custom ROM, as I said in my original post, so I won't point my finger to an automatic update. Maybe, maybe, some google-thing update? But I'm really sceptical that it would even be possible to hard brick a device in this way.
That's really weird, anyway.
Ps. Have you tried to open the phone and flash the fastboot + ROM in EDL mode?
I have not tried it yet. Do u have some links or tutorials on how to do this? I just received the kit to open the phone. I thought at first it might be a battery problem since the phone doesn't seem to charge at all when I plug it in electricity.
fawziX said:
I have not tried it yet. Do u have some links or tutorials on how to do this? I just received the kit to open the phone. I thought at first it might be a battery problem since the phone doesn't seem to charge at all when I plug it in electricity.
Click to expand...
Click to collapse
Here are some videos I followed. Do it at your own risk.
Phone Open + EDL Test Points *
Mi Flash Procedure in EDL Mode**
if the phone is not recognized as Qualcomm HS-USB QDLoader 9008, you need to install the drivers
This should work for both locked and unlocked bootloader devices, if I'm not wrong.
Here's another useful and complete guide.
This guide is not for the Redmi Note 6 Pro, so don't use the provided ROM and fastboot. Just follow the procedure, that it's the same for every Xiaomi phone.
* I don't know what kind of nails that guy has lol Keep in mind that you have to heat the phone up with an hair dryer in order to be able to work with the tools (the body is pretty tight).
In the video is not clear, but the phone has two slots: the first one is made for replacing the screen, and the second is made for taking apart the back cover. Pay attention to this (I didn't know this detail, and I took apart my screen during the first attempt).
** During the flash procedure, I get the error I mentioned in my original post. I'm not sure if it's related to having an un-authorized Mi account or whatsoever, I haven't found any clear confirmation about that.
Gh_Racer said:
Here are some videos I followed. Do it at your own risk.
Phone Open + EDL Test Points *
Mi Flash Procedure in EDL Mode**
if the phone is not recognized as Qualcomm HS-USB QDLoader 9008, you need to install the drivers
This should work for both locked and unlocked bootloader devices, if I'm not wrong.
Here's another useful and complete guide.
This guide is not for the Redmi Note 6 Pro, so don't use the provided ROM and fastboot. Just follow the procedure, that it's the same for every Xiaomi phone.
* I don't know what kind of nails that guy has lol Keep in mind that you have to heat the phone up with an hair dryer in order to be able to work with the tools (the body is pretty tight).
In the video is not clear, but the phone has two slots: the first one is made for replacing the screen, and the second is made for taking apart the back cover. Pay attention to this (I didn't know this detail, and I took apart my screen during the first attempt).
** During the flash procedure, I get the error I mentioned in my original post. I'm not sure if it's related to having an un-authorized Mi account or whatsoever, I haven't found any clear confirmation about that.
Click to expand...
Click to collapse
Thank you for the infos! I'll try to do this when I have some free time in the coming days and I'll let you know if I have any success.
fawziX said:
Thank you for the infos! I'll try to do this when I have some free time in the coming days and I'll let you know if I have any success.
Click to expand...
Click to collapse
I hope you'll be able to do something. Please update me in that case! Good luck.
Gh_Racer said:
I hope you'll be able to do something. Please update me in that case! Good luck.
Click to expand...
Click to collapse
Hello here I'm again. Maybe you can help me with one more thing. I'm trying to flash it but i get a weird xml error when trying.
Can u link to me the .elf files you used? The link in the video is broken. Thanks again!
fawziX said:
Hello here I'm again. Maybe you can help me with one more thing. I'm trying to flash it but i get a weird xml error when trying.
Can u link to me the .elf files you used? The link in the video is broken. Thanks again!
Click to expand...
Click to collapse
Btw I also had the hello packet problem. But if u remove the usb cable from PC and then attach it again and refresh it dissapears but then after some time I have the weird xml error (resdump: <?xmlversion="1.0".........)
fawziX said:
Hello here I'm again. Maybe you can help me with one more thing. I'm trying to flash it but i get a weird xml error when trying.
Can u link to me the .elf files you used? The link in the video is broken. Thanks again!
Click to expand...
Click to collapse
I need to search for them, since I downloaded things from a lot of different sources (I also deleted the one I downloade, since I did lost my hopes). I’ll update you in case I’ll be able to find them.
fawziX said:
Btw I also had the hello packet problem. But if u remove the usb cable from PC and then attach it again and refresh it dissapears but then after some time I have the weird xml error (resdump: <?xmlversion="1.0".........)
Click to expand...
Click to collapse
So, exactly, what did you do? You unplugged the cable and attached it again shortening the two test pins? Or you simply attached it without doing anything special?
I wasn’t able to solve the hello packet error.
I don’t know what the xml error is related to, since I couldn’t manage to communicate with the phone. I have no suggestions for this, I’m sorry.
Hi everyone...
Two days ago my Note 6 Pro woke up the same and after doing everything described above and even being able to successfully flash via EDL,
it remains the same and without changes.
I explain...
It turns on and stays in the MI logo, when trying to enter the recovery it stays in the TWRP home screen and only allows to enter the FASTBOOT that is unlocked but when trying to flash from MiFlash it gives an error as when I try directly from. bat file so I decided to try for EDL and it threw the xml error (resdump: <? xmlversion = "1.0" .........), I did some research and it turns out due to "prog_emmc_firehose_Sdm660_ddr.elf" and "prog_emmc_firehose_Sdm660_lite.elf" in "images folder" to firmware uncompress files, and I replaced them with others that allowed the flash to continue and finish successfully, but to my surprise, when restarting the device, everything continued without any change...
Until this moment I do not find any information that can help with this unfortunately.
I just hope that some of the "Great GURUS" in the forum can help and provide some solution... If it exists.
fawziX said:
Hello here I'm again. Maybe you can help me with one more thing. I'm trying to flash it but i get a weird xml error when trying.
Can u link to me the .elf files you used? The link in the video is broken. Thanks again!
Click to expand...
Click to collapse
Tenho o redmi note 6 pro bloqueado no modo edl gostaria de saber se alguém tem como ajudar
MOD EDIT: Please post only in English according to the FORUM RULES or at least add an English translation below your foreign language(Google translator for example), translation added below:
I have the redmi note 6 pro locked in edl mode I wonder if anyone has how to help
Hi everyone, I’m sorry for having not replied yet.
As I wrote in my main post, I haven’t managed to recover my phone so far, so we decided to buy a brand new phone.
I hope you’ll be luckier than me.
Hi all, in order to flash your phone you will need authorized account normally, but if you try to flash stock firmware with Mi Flash tool and QFill you will face errors and errors.
What I recommend you is to re-flash full fastboot firmware the same version what you had on your phone or the latest stable fastboot firmware which you can get here:
Oreo Android 8 OEKMIXM
Pie Android 9 PEKMIXM
Latest version:
https://bigota.d.miui.com/V12.0.1.0.PEKMIXM/tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global_ac26982758.tgz
All versions:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Once you download firmware open it with 7-Zip archive tool, and again open firmware inside 7-Zip until you see normal folder with the name of firmware for example "tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global" and extract to desktop.
Once is Finish dowload this bypass auth files.
File with out Login
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
Now copy those two files:
prog_emmc_firehose_Sdm660_ddr.elf
prog_emmc_firehose_Sdm660_lite.elf
and replace those two files inside firmware that you extracted before on Desktop for example:
"C:\Users\YOUR_PC_USER_NAME\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global\images"
Next step is to use correct MiFlash tool which you can download here:
Working Mi Flash Tool:
MiFlash20160401.zip | by firmwarefile.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Now, load firmware inside Mi Flash tool:
for example:
"C:\Users\YOUR_PC_USER_NAME\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global"
Next is to remove battery cover carefully because you can damage fingerprint flat cable!or use special edl cable if you don't wanna to open your device.
- Disconect battery
- short those test point pins
https://1.bp.blogspot.com/-C8bU7S6nAaI/Xqrd_PdvLXI/AAAAAAAAaLA/PK_E4oI_qPcJhBnSwlbQ0sr5J_9Ti2ycQCNcBGAsYHQ/s1600/21-14-47-images.jpg
-Plug the usb cable while you are holding those pins, once you got your device detected in Qdowloader 9008 mode relese short from test points.
Now click on Reflash on MiFlash tool and you will see your device is detected, now click on Flash and wait (it can take some time to finish). If you got error just unpplug the phone from PC and try again.
FOR FLASH OPTION:
You can check FLASH All or Flash all except storage
Once you successfully flashed your device, unplug device from your pc, plug battery back and power up your device to see if it's working or not.
The pay part if that doesn't work is reprograming or replacing emmc chip with ufi tool or something like that...
Good luck
Teddy Lo said:
Hi all, in order to flash your phone you will need authorized account normally, but if you try to flash stock firmware with Mi Flash tool and QFill you will face errors and errors.
What I recommend you is to re-flash full fastboot firmware the same version what you had on your phone or the latest stable fastboot firmware which you can get here:
Oreo Android 8 OEKMIXM
Pie Android 9 PEKMIXM
Latest version:
https://bigota.d.miui.com/V12.0.1.0.PEKMIXM/tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global_ac26982758.tgz
All versions:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Once you download firmware open it with 7-Zip archive tool, and again open firmware inside 7-Zip until you see normal folder with the name of firmware for example "tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global" and extract to desktop.
Once is Finish dowload this bypass auth files.
File with out Login
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
Now copy those two files:
prog_emmc_firehose_Sdm660_ddr.elf
prog_emmc_firehose_Sdm660_lite.elf
and replace those two files inside firmware that you extracted before on Desktop for example:
"C:\Users\YOUR_PC_USER_NAME\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global\images"
Next step is to use correct MiFlash tool which you can download here:
Working Mi Flash Tool:
MiFlash20160401.zip | by firmwarefile.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Now, load firmware inside Mi Flash tool:
for example:
"C:\Users\YOUR_PC_USER_NAME\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global"
Next is to remove battery cover carefully because you can damage fingerprint flat cable!or use special edl cable if you don't wanna to open your device.
- Disconect battery
- short those test point pins
https://1.bp.blogspot.com/-C8bU7S6nAaI/Xqrd_PdvLXI/AAAAAAAAaLA/PK_E4oI_qPcJhBnSwlbQ0sr5J_9Ti2ycQCNcBGAsYHQ/s1600/21-14-47-images.jpg
-Plug the usb cable while you are holding those pins, once you got your device detected in Qdowloader 9008 mode relese short from test points.
Now click on Reflash on MiFlash tool and you will see your device is detected, now click on Flash and wait (it can take some time to finish). If you got error just unpplug the phone from PC and try again.
FOR FLASH OPTION:
You can check FLASH All or Flash all except storage
Once you successfully flashed your device, unplug device from your pc, plug battery back and power up your device to see if it's working or not.
The pay part if that doesn't work is reprograming or replacing emmc chip with ufi tool or something like that...
Good luck
Click to expand...
Click to collapse
I followed all the steps without any issues, since they were the same as I tried the last time, but a wanted to give a try to the files you linked me.
But... Unfortunately, I always get the same error. Probably, as you correctly pointed, that's an hw fault and there's nothing we can do.
I hope that someone will be luckier than me! I lost my hopes. RIP Redmi Note 6 Pro.
I decided to load gsi via dsu loader in the settings app, I had oem unlocking enabled, and then I installed one of the gsi--it was random, I don't know too much about these types of things, like arm64 or something, at the time, so I just did the arm64 so for a bit, it was done downloading, all I needed to do was restarting the device, and then, after restarting it, it had this boot messages that says "dm-verity corruption. Your device is corrupt. It can't be trusted and may not work properly. Or, the device will power off in 5s". The device was working correctly except it just had that message everytime it boots, and it was still android 11 as normal instead of loading android 13 gsi. I tried to fix this dm-verity problems, with everything I can: I used adb and used the dm verity command (adb reboot dm-verity enforcing, adb reboot, fastboot set active other), I also did factory reset but that doesn't work, I contacted the customer services and they said as of right now, they don't provide roms or software to end user, and the only way to fix the devices with them is to send it to them and it cost 30 dollars, so i declined instead. I found these two application while on my way to research on fixing the devices: Unlocktools, and rom2box, but I am skeptical of them. I didn't found the firmware for this specific devices, but it did gave me hope that the only thing that came close is blu g91. I don't know what else to do besides use unlock tools, or rom2box, but I don't want to get my computer in danger, so I don't have that much choice.
Does anyone have a firmware file for BLU F91 5G though? I just founded one, but I can't download them, because I had to log in, but the website (Halabtech) seems kinda odd though, so I haven't log it in yet.
Nvm, I guess I'll just flash different gsi for different type of processor or something.
I Did same thing few weeks ago on my s91pro. Got same response from Blu and I can't seem to find a trusted place to get Firmware either. Sadly I don't have a pc to flash with but soon as I get my one plus device back I can try to sideload maybe.
Curios with your idea to flash again? If that works let me know please and good luck!!
My first idea was to use the dsu sideloading/vegebobo and shizuku for using gsi, my 2nd idea was to sue adb and fastboot, I would need to get gsi file, I could load either vb.meta, or just the system one instead. It took me a while because I was using outdated drivers, outdate adb, or just incorrect command. At first before all of this, I just wanna flash normal firmware, but I guess ill do that. It worked out for me, but I had problems with scren recording and wifi related in different gsi
btw, If u thinking of flash custom gsi on ur blu phone (in case if u don'twant to, I don't wanna force u or anything, just saying, so u don't have to deal with the burden) , I don't recommend using cdroid, in my expriences, wifi connected but doesn't work, and even using mobile data doesn't work either, lineageos was less worse.
Honestly with all the hassel it seems to cause I don't see it worth it. Hell even trying to fix the issue I have already seems to be a pain. I'm gonna just leave it be. Doesn't seem to cause any real issues other than the annoying warning during boottup. Which I just press the power one time and use phone as normal.
I am only using the Blu phone till I get my one plus back from warranty service. Then it's just a back up and alternate account I use for games.