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!!
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:
As there's no thread on this device I decided to start one
The hardware of this device is really nice, but the stock ROM on it is total garbage. It has some built in power saving that closes all background apps no matter what the settings are, so after an hour so so you won't receive any more notifications from messaging apps such as telegram and outlook.
Since there are not even stock ROMs available anywhere I decided to take the risk of a brick and install phh's AOSP 10 GSI, no need for TWRP as everything can be done using ADB and fastboot. The procedure is the same as with any other phone: Unlock the bootloader, wipe all partitions in fastboot, install system image, restart and hope for the best. Luckily it booted up just fine and everything except VoLTE and VoWIFI works, @lucian.w153 found two little bugs which I didn't notice:
lucian.w153 said:
- In call volume not working, it is stuck at max which is very annoying
- You can't disable the second sim card, you need to take it out if you don't want it to consume battery.
Click to expand...
Click to collapse
It's an arm64 AB device, so any matching GSI should run fine on it.
I have tested phh's vanilla, FLOSS and GAPPS variants, they all work flawlessly barring those two bugs mentioned above.
GAPPS version is my daily driver now, the phone runs blazingly fast and battery lasts forever. All hardware (bluetooth, sensors, cameras etc.) works perfectly, no force closing or other issues.
Hope some more share their experience to help others.
Cheers
Finished. Done!
Joergelmann said:
Please provide complete instructions. I am an absolute beginner. Please a step to step instruction with links.
Click to expand...
Click to collapse
Ok, just the usual disclaimer: You may void your warranty or brick your device in the process, you do everything on your own risk and I'm not responsible if anything goes wrong.
Of course you will also loose any data on your device as it will be formatted in the process.
Prerequisites:
You need ADB and fastboot installed on your computer, follow these instructions for windows or these for MacOS or Linux.
Also you'll need to download the system image from phh's releases, it has to be arm64 AB but you can choose whichever one suits you best, with or without google apps, FLOSS etc. If you don't know what those are, please do some research in the forum first.
For most people system-quack-arm64-ab-gapps.img.xz will be the most suitable one as it's closest to a stock ROM with google apps. After downloading extract the .img to the same folder you installed ADB and fastboot to. Also rename it to something simpler like system.img for later.
Make sure you have sufficient battery in your phone before you start, at least 50%.
Once those are ready you need to unlock the bootloader of your phone. First enable developer options: Go to settings -> about device and tap on build number 7 times in a row quickly, you'll get a confirmation that developer options are enabled. Go to settings -> system -> developer options, there enable USB debugging and OEM unlock.
When done, connect you phone to your computer with the USB cable. Your phone will show an info in the statbar that USB debugging is enabled.
On you computer open a terminal in the folder where you installed ADB and type in the upcoming commands and press enter after each.
First type: adb devices
ADB should now detect your device, and a request for access will pop up on your phone asking to allow permission. Allow it.
Next type: adb reboot bootloader
The phone will reboot into fastboot mode, wait a few seconds until "fastboot mode" is shown on the bottom left of your phone's screen.
Now type: fastboot devices
Fastboot should detect your device
Next type: fastboot flashing unlock
Fastboot and your phone will ask you to confirm that you want to unlock your bootloader, confirm it using the volume buttons on your phone according to the instructions on your phones screen.
After the bootloader has unlocked successfully you need to format your device, type: fastboot erase userdata
You'll receive a confirmation that data has been formatted.
Type: fastboot erase system
You'll receive a confirmation that system has been formatted.
Now you can flash the system image, type: fastboot flash system system.img
This will take a while until all the data is sent and installed on your phone. You will receive a progress report and confirmation when it's done.
Finally type: fastboot reboot
You phone will reboot and load the new system for the first time, this takes around 2-3 minutes, be patient. You can disconnect the USB cable now. When the welcome screen pops up set up everything as usual and enjoy
Thanx a lot for the instructions.
It's worked out. Everything works fine.
Great to hear!
AOSP really is a blessing, big thanks to @phhusson for all his work on this too.
This device even beats the legendary K10000 in endurance, my current record stands at 12 days and 34h SOT xD
The only things missing is double tap to wake and the ability to disable the second sim card. Otherwise almost perfect. :good:
After watching the WP6 violence test video and also seeing several other positive reviews I decided to buy one...
Recieved it a couple of days ago and seems like a great phone, very impressed with the speed, battery, heft and general rugged feel of it etc..
However... this morning I dropped it out of my pocket (from no higher than 3ft) onto some gravel and was horrified to discover around 7 little scratches/idents/scuffs to the screen!
How can this possibly be after all I saw it put through? In the advert video it shows someone dropping the phone and picking it up without even needing to check it's OK which kind of implies it's not gonna get scratched easily. Either way I'm gutted!!
By contrast, I've had my HTC M8 for 3 years and has been dropped loads of times and doesn't have a single one of these indented scuffs to the screen, despite it not making any of the claims to ruggedness like the WP6.
I bought my WP6 just last week, and am really impressed with it running Nova launcher, battery life and performance are great! Unfortunately the sheer mass of the phone means it will damage itself in a fall. My old Runbo X5 would probably fare better in a fall, being much lighter, but nowhere near as good a phone.
Are you running the stock ROM or also AOSP @markpab ?
v220 is out here, in-call volume not fixed, maybe the SIM issue mentioned above, would someone like to try?
@TpX Thinnr, that's surprising. Mine fell on some gravel as well last week, but the only thing I can see is a little scratch on the rubbery corner top left of the device.
Yes, I'm running totally stock ROM, been ages since I last rooted a phone (Runbo X5). 5 days since first full charge, and still at 34%!
GroovyG said:
Are you running the stock ROM or also AOSP @markpab ?
v220 is out here, in-call volume not fixed, maybe the SIM issue mentioned above, would someone like to try?
No. No changes regarding bugs in v220.
I have installed Havoc-OS 3.6 now.:
https://sourceforge.net/projects/ha...00613-Official-GApps-arm64-ab.img.xz/download
This allows you to set at least two separate tones for the simcards. I then created a silent tone for the second simcard. If you can't deactivate the second card, at least I am at peace.
Click to expand...
Click to collapse
markpab said:
Yes, I'm running totally stock ROM, been ages since I last rooted a phone (Runbo X5). 5 days since first full charge, and still at 34%!
Click to expand...
Click to collapse
And you don't have the problem that all background apps are closed and no more notifications arrive after a while?
I get notifications from emails and texts no problem, but apps from the Playstore don't update or stop, such as battery widgets, status bar calendars, and some clock widgets. All the built in apps are fine.
Hi, My New wp6 is bricked. I need stock firmware [emoji20]
Enviado desde mi F5321 mediante Tapatalk
oscarhugo said:
Hi, My New wp6 is bricked. I need stock firmware [emoji20]
Enviado desde mi F5321 mediante Tapatalk
Click to expand...
Click to collapse
You can download the original stock rom directly from the oukitel website:
https://mega.nz/file/3NFFQaxZ#Wk8S5G-iqBpJI5HDK-AXMGebNDiRVdUMAGthW_JANS0
You don't need to create an account there.
But I don´t know how to install the rom. Someone else would have to explain that here please.
Doesn't work, i tried to flash and is not possible say: chip type not match!! target chip type is mt6771 load scatter chip type is mt6737.
old firmware?
What exactly did you do to "brick" it? You can't really totally brick those devices.
Can you still access it with ADB and/or fastboot? If so, just flash a GSI and you're back in business.
Totally bricked, no power... black screen. I try to flash with sp flash tool
Enviado desde mi F5321 mediante Tapatalk
Did you manage to recover it with SP Flash Tool?
I'm still curious what you did to cause the brick, would be helpful for others too if you let us know what you did.
Was a New phone, works great without sim. Once i put sim, crashing... And Black screen.. Bricked. [emoji20]
I can flash with sp tools but i need firmware for mt6771
Hey there! I'm new around here and I'm not sure if this has been asked before... I found this thread but there are a couple differences between our cases and none of the solutions given in the comments seem to work:
"The system has been destroyed" Poco X3 NFC
So here's the thing -- I've been using this phone for a few months as a replacement for an iPhone. I used to be in the custom ROM scene back in 2015-2016 with an old Huawei I had, so I more or less know how all of this works. Since MIUI is visually horrible (in my opinion) I decided to try my luck at installing PixelExperience (great ROM, btw!). Since I've recovered my previous phone, this one has been sitting in a drawer for a couple months already, so I wanted to restore it to factory settings and sell it.
Aaaaand this is where **** happened. I had this weird intrusive thought of using "fastboot oem lock" before doing anything else just to see what would happen. The result? The phone is now bricked. I can access fastbook but that's about it, trying to boot into the system or recovery just gives me a "The system had been destroyed - Press power button to shutdown".
I know you can fix this by unlocking it again, but every tool I find online is meant for Windows and there are barely any solutions for macOS. I have found two of them: XiaoMiTool V2 (but needs adb to be enabled) and XiaomiADBFastbootTools, which seems to kind of work.
It detects the device when put in fastboot mode, but when clicking on "OEM Unlock" it just says "Token Verify Failed, reboot the device" (screenshot attached).
Trying to unlock it from the Terminal does pretty much the same thing (obviously).
Before you ask - Yes, I have all the required drivers installed as this is the exact same computer that I used to unlock the bootloader and flash OFRP. Everything works normally, it's just that I don't have access to the OEM unlock tokens to do it directly from the Terminal the same way I used to do it with previous phones.
So uhh... What can I do? Is it going to stay this way forever? Are there any solutions for macOS users that don't require having to use BootCamp or VM? I don't mind doing it but I'd rather have it as the very last resort, since it's too much of a hassle to do it. I have Xubuntu installed on my secondary drive, so if there is anything that could work on Linux, I'll take it too.
Thank you all for your help!
Edit 1: By the way! If this gets solved, could anyone be kind enough to guide me through the steps on how to mark it as [SOLVED] and close the thread? I'm really really bad at forums.
To the best of my knowledge, MIUI tools check online if the device is currently associated with a MI account -- and in case it isn't, nothing else goes...
My guess would be to try to run MiFlash with its last fastboot stock ROM in a Windows VM.
In case that doesn't work, taking it to Xiaomi tech support would be the best bet...
pnin said:
To the best of my knowledge, MIUI tools check online if the device is currently associated with a MI account -- and in case it isn't, nothing else goes...
My guess would be to try to run MiFlash with its last fastboot stock ROM in a Windows VM.
In case that doesn't work, taking it to Xiaomi tech support would be the best bet...
Click to expand...
Click to collapse
Thanks for taking your time to answer! I'll just have to install Windows in an external disk and see how it goes
I'm guessing MiFlash works offline, without checking anything about the phone on their servers, right?
kakuluva said:
I'm guessing MiFlash works offline, without checking anything about the phone on their servers, right?
Click to expand...
Click to collapse
I'm not really sure about that (haven't done it myself), but it has been the general recommendation here when faced with serious trouble so I would expect so. YMMV, though.