Related
So.. My Huawei P10 won't boot neither into system nor recovery, the screen is off and there's no LED indication.
It is recognized in fastboot, I can erase and flash both system and recovery, though rebooting the device does nothing, it just shows up in fastboot again, still with screen off.
Is there any way to save this phone? I installed a new battery too.
dc pheonix and hcu client did not help either.
:crying:
I have the same issue. Hard brick, doesnt turn on after I upgraded to oreo.
Guys, I have this issue, too and worked a bit with DC Phoenix support.
The reason why my P10 didn't boot anymore is simple: I just flashed the wrong firmware files for rolling back from Pie to Oreo.
Now I have a shiny black piece of junk.
I tried to flash with DC Phoenix, also with test point. The device was recognized as serial device, so the test point was working. But DC Phoenix failed at flashing.
DC support says, that Dec 18 security patches are preventing to flash old firmwares but DC needs to flash the original factory firmware, OTA isn't working.
So at the end of an 8 hour day trying to fix my P10 my result was a nice chat and a fast refund of my 19€ for DC pheonix.
If you can't get it working even with test point method, your phone is is a piece of junk.
Mostly it's caused by doing something wrong at downloading firmwares or flashing them, also while flashing wrong Magisk modules, Xposed or wrong boot images.
Since Pie don't have a boot partition anymore it's important to download a rollback firmware (2 files instead of 3) so the recovery is able to reformat before flashing.
Jannomag said:
Guys, I have this issue, too and worked a bit with DC Phoenix support.
The reason why my P10 didn't boot anymore is simple: I just flashed the wrong firmware files for rolling back from Pie to Oreo.
Now I have a shiny black piece of junk.
I tried to flash with DC Phoenix, also with test point. The device was recognized as serial device, so the test point was working. But DC Phoenix failed at flashing.
DC support says, that Dec 18 security patches are preventing to flash old firmwares but DC needs to flash the original factory firmware, OTA isn't working.
So at the end of an 8 hour day trying to fix my P10 my result was a nice chat and a fast refund of my 19€ for DC pheonix.
If you can't get it working even with test point method, your phone is is a piece of junk.
Mostly it's caused by doing something wrong at downloading firmwares or flashing them, also while flashing wrong Magisk modules, Xposed or wrong boot images.
Since Pie don't have a boot partition anymore it's important to download a rollback firmware (2 files instead of 3) so the recovery is able to reformat before flashing.
Click to expand...
Click to collapse
were you able to send flash erecovery through adb ? or did it show success read and failed write?
thank you
NowLearn said:
were you able to send flash erecovery through adb ? or did it show success read and failed write?
thank you
Click to expand...
Click to collapse
For adb it’s needed that the phone starts completely into system or twrp - both not possible for me.
With fastboot it’s not possible to flash eRecovery, just recovery.
Jannomag said:
Guys, I have this issue, too and worked a bit with DC Phoenix support.
The reason why my P10 didn't boot anymore is simple: I just flashed the wrong firmware files for rolling back from Pie to Oreo.
Now I have a shiny black piece of junk.
I tried to flash with DC Phoenix, also with test point. The device was recognized as serial device, so the test point was working. But DC Phoenix failed at flashing.
DC support says, that Dec 18 security patches are preventing to flash old firmwares but DC needs to flash the original factory firmware, OTA isn't working.
So at the end of an 8 hour day trying to fix my P10 my result was a nice chat and a fast refund of my 19€ for DC pheonix.
If you can't get it working even with test point method, your phone is is a piece of junk.
Mostly it's caused by doing something wrong at downloading firmwares or flashing them, also while flashing wrong Magisk modules, Xposed or wrong boot images.
Since Pie don't have a boot partition anymore it's important to download a rollback firmware (2 files instead of 3) so the recovery is able to reformat before flashing.
Click to expand...
Click to collapse
Yes, I tried the same, and also got the security patch warning, though little did I know I could get a refund. I did not try the 'test point' method. Not sure if I get it, do you connect/solder usb-cable onto the phone's motherboard?
You need to connect the test point to ground, you can use the shielding right beside of it. Take a small wire or tweezers for it.
I did it like this:
- connect the phone to pc, it should be recognized as fastboot device
- Short test point with ground
- hold down the power button until the computer recognizes the device again
- install the serial driver
DC should work now. But if it doesn’t, write it in the dc forums and you’ll get refund
Huawei P10 Successfully Recovered from Fastboot black screen on latest Security 9.
Alham Do Lillah With the help of Allah Almighty today I successfully recovered my p10 from black display stuck in fastboot mode on latest Security 9..
I used 2 tools
1: Dc phoenix
2: chimera
chsaim said:
Alham Do Lillah With the help of Allah Almighty today I successfully recovered my p10 from black display stuck in fastboot mode on latest Security 9..
I used 2 tools
1: Dc phoenix
2: chimera
Click to expand...
Click to collapse
Can you explain exactly how?
Jannomag said:
Can you explain exactly how?[/QUOTE
you need to know exactly build number and flash latest firmware according to build number with chimera tool.
make sure that phone is in fastboot mode... am sorry if i cant explained well ... for more details write me at [email protected]
Click to expand...
Click to collapse
Yes, please share some information how can we recover our dead p10. It would greatly help the community. Thank you
I tried it with DC and Chimera. Both aren't working for me, because of the security patches. Huawei did some deep changes between October and December 2018 and made it very hard to flash even with test points - another reason for me to leave Huawei to my alltime smartphone enemy Samsung...
The DC-Phoenix and Chimera teams are working hard on a solution, take a look at their forums and you'll notice that many people have this problems, just because Huawei ****ed it up.
I mean, we did all something wrong, otherwise this threat won't exist. But Huawei made it hard for us to revive the devices and this reminds me of Apples politics. Huawei doesn't need to give support to unlocked phones but it's very unfair to prevent their customers from doing what they want including unlocking.
Back to topic:
Follow the forums of DC and Chimera. If you found any solution or fix, please post it here.
My device, also bricked while flashing the wrong firmware for rolling back from pie, shows just black screen and fastboot is working.
Test point didn't work, also Chimera couldn't flash anything.
My device gets quiet warm while in fastboot, so I disconnected the battery to prevent deep discharging.
Dear the same situation was happened with my p10 but i recovered... So if you want to recover your phone then give ultra view id and pass....... If you have chimera and dc phoenix you can make it possible.. But remember you must need to know exactly build number
If any one needs my help here is my WhatsApp contact me anytime... +923007969629
If you can share the steps. It would help the community thank you @chsaim
Yes, please share the steps to help the community.
Thanks!
There's absolutely no reason for not sharing the steps in a simple tutorial. Instead @chsaim is begging for remote access to our computers, I don't know why.
I chatted a lot with Chimera support and they told me that there's currently not way to recover, with faulty partitions caused by flashing, with the Dec.2018 security patches and newer. This included the firmware 382, on some 380 devices it doesn't work either.
They also want to send me an E-Mail when they find a solution for this. For now I got my money back from them - great support, also the DC team.
I'm happy to get a used mainboard from local market and now have my P10 as spare phone.
yeap.same **** again with Huawei phones.ı want to try pie rom and when ı try rollback oreo phones turn off and not open again.this is not like a other hard or soft brick problem because I have a experiance about other problems.phone cant charge or pc can't see the device ı cant see red led too.just dead.ı use this phone 2 years but never buying huawei again neverrrr.anybody found a solition ?
Jannomag said:
You need to connect the test point to ground...
- connect the phone to pc, it should be recognized as fastboot device
- Short test point with ground
- hold down the power button until the computer recognizes the device again
- install the serial driver
...
Click to expand...
Click to collapse
Testpoint should be connected till pc recognize it properly or connected all the time during flashing? Do you have any logs at what point dc crashed in your case?
lukastob said:
Testpoint should be connected till pc recognize it properly or connected all the time during flashing? Do you have any logs at what point dc crashed in your case?
Click to expand...
Click to collapse
I can access fastboot with dc-phoenix. Once I tried to send erecovery, recovery, or kernel w
Through cmd. It reads but it can't write. That's where I get stuck. If dc it's able to write then I would be able to recover my dead phone. Thank you
lukastob said:
Testpoint should be connected till pc recognize it properly or connected all the time during flashing? Do you have any logs at what point dc crashed in your case?
Click to expand...
Click to collapse
Test point needs to be shorted until the computer recognizes the P10 as an USB serial device. You need drivers for this, which you can get from DC Phoenix.
DC couldn't flash the bootloader:
Code:
BOOTLOADER File to update: Kirin960_T0_A7.0_V1
20.02.2019 21:34:26 Starting to write device...
Writing bootloader...
Error writing Bootloader
20.02.2019 21:35:36 Writing device finished - INCOMPLETE
Hi. So I decided it was time to move to EMUI 9 and after looking at various posts on here I believe the easiest way was to you EMUI Flasher to flash the ROM (coming from 8.1 rooted).
The phone restarted and went to EMUI installer but after 10% or so I got an error. It asked if I wanted to go to erecovery or reboot the device (I think). As far as I was concerned it was only checked that the ROM was OK and hadn't installed anything so I selected reboot. Now the phone won't come on. I've tried holding the power button for an inordinate period of time but it's not happening.
Is there anything I can do?
EDIT - I've tried a different USB port on my PC and can see something in the device manager now ---- Kedacom USB Device > Android Bootloader Interface ---- which gives me a sliver of hope this can be fixed.
EDIT2 - I could send img files through fastboot all day (phone was recognised even though it wouldn't turn on) but couldn't fix this. Gave DC Phoenix a try but no luck there either. Think I've killed it.
EDIT3 - Just in case anyone ever comes across this. I tried below but nothing would work so I contacted someone on Telegram who said the only option was to open the phone up and short it out. No way I was attempting that so I eventually contacted Huawei UK and told them it had died during an update, never let on that it was MY fault! Anyway, they sent out a prepaid envelope to send to a their repair partner. I won't name them here but they have terrible reviews on Yelp so I was a bit apprehensive. I know the phone arrived with them last Friday as I checked the post tracking but I never heard anything from them. Today out of the blue my phone has come back to me in full working order, repaired under warranty! Considering there was only one thing I was really using root for and it was only a slight convenience, I think I'll just leave it as is.
Are you able to flash anything in fastboot?
Are you able to boot to recovery via fastboot? Disconnect the cable after you give the reboot recovery command in fastboot.
You may be able to flash each component of emui, system, vendor, oeminfo, kernel etc. Seems that it's missing most or all of it.
Bootloader sounds like it's intact.
Btw. The easiest way to update to emui would be to wait for an OTA from Huawei.
Personally I don't see a point, pie is not as efficient as Oreo nor does it have any features to merit an upgrade, in fact you would lose features (4k zooming, functional TWRP)
I am a long time user of Xiaomi devices, and have rooted every one I have. I recently purchased the Redmi Note 9 for my girlfriend and intended to root and block ads etc. I am quite proficient with rooting processes and the tools needed to make that work.
I could find a working TWRP for the phone, and used ADB and Fastboot to program this. However, it seems the MTK Helio G85 is a bit more tricky than a Qualcomm based device. So I basically failed to get root working. In the end through a late night error I managed to delete the Boot.img of the device leading to the dreaded 'hard brick'. I have read on the Forum others who have the same symptoms - basically boot loop, no access to Recovery or to Fastboot. Bad luck my friends this is a Service Centre repair.
So I took to Googling on the issue and found a Russian who advertised a Service Centre repair service but over TeamViewer. This was advertised at US$29 for a fix. Why could he do it? Well he has the Service Centre auth codes needed to do a full recovery of the phone. So taking pot luck I sent my US$29 and they did exactly what they promised. Accessed my PC remotely worked with me to get the correct files set up, and then loaded up their authorised service build on my PC and re-programmed the bricked device. After a 2 hour re-charge (best to do this reset with no battery power) I performed the 3 button re-set and the phone came back to life. Never left my house, and the phone re-booted with a full build of MIUI.
I am not sure if the mods allow me to provide their details, so I in order to keep my XDA status OK I'll ask you to PM me if you need the details.
Saved my phone, and to be honest was worth the cash for the no hassle repair. I am not in a Service Centre area, and this quick reliable fix was great. Took a risk, but the provider is genuine and authorised repair agent. Their English was great, instructions clear, and all the hard work they do remotely on your PC. I scanned for viruses after the session - was all clean.
If you get in a fix, this is a good reliable and convenient solution.
pepsimaxmjs said:
I am a long time user of Xiaomi devices, and have rooted every one I have. I recently purchased the Redmi Note 9 for my girlfriend and intended to root and block ads etc. I am quite proficient with rooting processes and the tools needed to make that work.
I could find a working TWRP for the phone, and used ADB and Fastboot to program this. However, it seems the MTK Helio G85 is a bit more tricky than a Qualcomm based device. So I basically failed to get root working. In the end through a late night error I managed to delete the Boot.img of the device leading to the dreaded 'hard brick'. I have read on the Forum others who have the same symptoms - basically boot loop, no access to Recovery or to Fastboot. Bad luck my friends this is a Service Centre repair.
So I took to Googling on the issue and found a Russian who advertised a Service Centre repair service but over TeamViewer. This was advertised at US$29 for a fix. Why could he do it? Well he has the Service Centre auth codes needed to do a full recovery of the phone. So taking pot luck I sent my US$29 and they did exactly what they promised. Accessed my PC remotely worked with me to get the correct files set up, and then loaded up their authorised service build on my PC and re-programmed the bricked device. After a 2 hour re-charge (best to do this reset with no battery power) I performed the 3 button re-set and the phone came back to life. Never left my house, and the phone re-booted with a full build of MIUI.
I am not sure if the mods allow me to provide their details, so I in order to keep my XDA status OK I'll ask you to PM me if you need the details.
Saved my phone, and to be honest was worth the cash for the no hassle repair. I am not in a Service Centre area, and this quick reliable fix was great. Took a risk, but the provider is genuine and authorised repair agent. Their English was great, instructions clear, and all the hard work they do remotely on your PC. I scanned for viruses after the session - was all clean.
If you get in a fix, this is a good reliable and convenient solution.
Click to expand...
Click to collapse
Maybe this is kind a ethical question. I don't consider its ok to pay someone to be able to flash your device, specially if you have to send money to some anonymous russian guy and hopping you are not getting scamed. Clearly its not a comfortable method and it shouldn`t be that way.
If I ever need that service I would use it just to record username and password with a keylogger and post it freely, its ridiculous to pay for flashing your phone.
Yes but...
ma259 said:
Maybe this is kind a ethical question. I don't consider its ok to pay someone to be able to flash your device, specially if you have to send money to some anonymous russian guy and hopping you are not getting scamed. Clearly its not a comfortable method and it shouldn`t be that way.
If I ever need that service I would use it just to record username and password with a keylogger and post it freely, its ridiculous to pay for flashing your phone.
Click to expand...
Click to collapse
If you actually hard brick your device (mine shipped from China direct) you have a lot of hassle to get it fixed. If you don't have a service centre nearby, double the hassle and significant costs / risks to ship overseas. Sat at home, someone with the skills and the important EDL keys (i.e. registered repairer with Xiaomi) could fix the device. Mine was an unlocked phone, therefore technically I had removed the warranty. $29 to flash a bricked device and fully recover from my ****-up. OK value for me.
Hello, could you show me how to do it?
If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
For removing modules, you have two methods.
For first method, you need to boot in emergency mode, open magisk manager, remove module and reboot.
(It works only with magisk +v21.)
(To boot in emergency mode, keep pressed volume down after boot starts.)
For second method, you need to flash the original stock boot.img, open magisk manager, remove module, reboot and then flash the magisk patched boot.img again.
If you are using V12.0.5.0 or higher, TWRP will not work.
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
CruisaderX said:
he probably used [SPAM] that you can avail 3 months subscription for 19.19 usd, planning to get one when i have the money
Click to expand...
Click to collapse
It doesn't work for redmi note 9, my friend.
I'm sorry.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
pepsimaxmjs said:
I am a long time user of Xiaomi devices, and have rooted every one I have. I recently purchased the Redmi Note 9 for my girlfriend and intended to root and block ads etc. I am quite proficient with rooting processes and the tools needed to make that work.
I could find a working TWRP for the phone, and used ADB and Fastboot to program this. However, it seems the MTK Helio G85 is a bit more tricky than a Qualcomm based device. So I basically failed to get root working. In the end through a late night error I managed to delete the Boot.img of the device leading to the dreaded 'hard brick'. I have read on the Forum others who have the same symptoms - basically boot loop, no access to Recovery or to Fastboot. Bad luck my friends this is a Service Centre repair.
So I took to Googling on the issue and found a Russian who advertised a Service Centre repair service but over TeamViewer. This was advertised at US$29 for a fix. Why could he do it? Well he has the Service Centre auth codes needed to do a full recovery of the phone. So taking pot luck I sent my US$29 and they did exactly what they promised. Accessed my PC remotely worked with me to get the correct files set up, and then loaded up their authorised service build on my PC and re-programmed the bricked device. After a 2 hour re-charge (best to do this reset with no battery power) I performed the 3 button re-set and the phone came back to life. Never left my house, and the phone re-booted with a full build of MIUI.
I am not sure if the mods allow me to provide their details, so I in order to keep my XDA status OK I'll ask you to PM me if you need the details.
Saved my phone, and to be honest was worth the cash for the no hassle repair. I am not in a Service Centre area, and this quick reliable fix was great. Took a risk, but the provider is genuine and authorised repair agent. Their English was great, instructions clear, and all the hard work they do remotely on your PC. I scanned for viruses after the session - was all clean.
If you get in a fix, this is a good reliable and convenient solution.
Click to expand...
Click to collapse
Paid solutions are no longer needed. Redmi Note 9 factory firmware is out, so you can unbrick your phone, even if it's hardbricked, without authorised account.
Communos said:
Paid solutions are no longer needed. Redmi Note 9 factory firmware is out, so you can unbrick your phone, even if it's hardbricked, without authorised account.
Click to expand...
Click to collapse
If you are on MIUI V12.0.5.0 or higher, you can NOT flash without authorised account using flash tool.
You really need the EDL auth if you are on MIUI V12.0.5.0 or higher.
My phone suddenly get stucked into Redmi boot logo, cannot access system recovery but can access fastboot menu.
The problem is I hadn't enabled OEM unlock and developer options before. All the methods that I found so far requires bootloader unlock for that I also don't have MI account . What might be my next move? Thank you.
its hard to say what we can|t do with a still locked bootloader. if going to an authorized service center is out of reach, all we can do is try i guess. id still suggest going there if you can easily access your google account.
there are a few threads that say we can flash a still locked bl, but im not so sure.
Flash stock ROM/Recovery, lock bootloader?
Is there any guide on how I can complete return phone to stock and lock bootloader? Thank you.
forum.xda-developers.com
official stock roms can be hard to find on their site, heres an easier to navigate 1.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
gl
With EDL mode? I'm in a similar situation, a friend's mother forced a shutdown during a firmware update and destroyed the system that way. Of course the bootloader is blocked. I find it extremely stupid of Xiaomi to rely on a working system to give you the chance to unlock the bootoader but I guess that's how you sell some extra phones.
So far I've taken out the rear cover and the plastic that goes on top of the motherboard, unplugged the battery and with an arduino cable and some fiddeling shorted the "boot" pins while connecting the USB cable. Seems to be working given that MiFlash has changed the locked bootloader error for "indice fuera de limites" or in English "index out of limits error". I guess I don't have the right ROM so I'm downloading another one, but I'm struggilng to find the correct original fastboot ROM. The first one I've downloaded from Mi Community, the second one is from xiaomifirmwareupdater, but is gonna take forever to download. And I mean... F-O-R-E-V-E-R
Jaki1122 said:
With EDL mode?
...
Click to expand...
Click to collapse
gl with that, as only authorized people can properly flash from there. while i havent used EDL, there are some trusty people who can help us out (ive seen it in tg groups)
a site did say maybe using another version can help, who knows it might do the trick
https://c.mi.com/thread-2027947-1-0.html
also seems weird how goolag hasnt fixed half flashing from destroying, last time i had that happen was '12
Foreword: My time with Vivo has come to an end. After flashing a wrong devicecfg and accidentally rebooting my device it is now in a hard bricked state.
Vivo has locked down EDL, there is absolutely no way to flash or backup anything in EDL mode without the official Tools (namely Vivo AFTool 5.9.80).
Vivo India refers me to Vivo Germany - Vivo Germany has outsourced its customer support to bulgaria.
The people on the other side of the line know absolutely nothing about the technical aspect and refuse to put me through to anyone with any kind of knowhow.
Due to their anti consumer and anti repair attitudes I will not buy another Vivo phone.
With this out of the way: You might end up like me with a hard brick. Or without signal.
Even if this will not save you from a hard brick I can not stress this enough: Make a BACKUP! And backup your data. This will wipe your phone.
This process is IRREVERSIBLE unless you have a split ROM of the chinese Firmware or your own Backup.
THIS or BL UNLOCK will break your portrait mode. No more bokeh, neither in Origin OS nor FunTouch.
Do NOT flash fsg, modemst1 and modemst2. They are commented out in the COMMANDS file.
You do this at your own risk. As said before this might brick your device.
Unlock your Bootloader
Backup your Partitions
Download my Flash Folder and Extract it: Android File Host
Open 01COMMANDS.txt and read the instructions
Open a command shell in the same folder that you can find 01COMMANDS.txt in
Run the given commands in blocks or one after the other
If you do not have signal after flashing you might have to erase modemst1 and modemst2 partitions, so that they get replaced by the backup in fsg.
A magisk flashed boot.img and adb-modded recovery is included so you can flash it after booting up FunTouch once and backup all your partitions again.
Thanks again to @Pervokur for helping me along the way. There is definitely an easier method that involves less risky flash operations.
My phone died on the cross while I was trying to figure it out, so maybe someone else will pick up the torch.
I will not be able to offer any kind of support.
RIP @Killuminati91's Vivo, who died for the cause.
Sorry to hear that, man, you were so close to what looked like an easy switch between ROMs.
I know you said you were no developer but you are still a leap ahead of most of us here. Long do we miss the good old days where ROMs, kernels and pure innovation shortly followed our much-wanted phone when flashing a few ROMs a week was normal.
Thanks for all your help, perhaps one day there will be a way to recover your phone.
Many thanks, may I relock the bootloader when i finished change to Global rom?
amos0609 said:
Many thanks, may I relock the bootloader when i finished change to Global rom?
Click to expand...
Click to collapse
Same question
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
how did you relock the bootloader, does the portrait mode work again?
does any one change the origin os /ocean into funtouch？
version？ how to relock after it can switch to funtouch？
by the way, I saw the post on the taiwan vivo phone of fb
the second hand goods, it wrote he change the origin os into funtouch
and he sell this service , it charge 2000 nt dollars in taiwan.
maybe someone can save your phone.
Killuminati91
I think the only problem that keeps the phone from being recognized as official FunTouch is dm-verity.
In theory both phone versions have the same exact hardware.
i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)
I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!
stevenkh168 said:
i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)
Click to expand...
Click to collapse
Message?
silence360 said:
I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!
Click to expand...
Click to collapse
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.
Killuminati91 said:
Message?
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.
Click to expand...
Click to collapse
did you try using the OriginOS's camera app on FuntouchOS ? I find it when u use the front facing camera, the portrait mode still work. In the other hand, the back camera is not working in portrait mode. I follow your guide and using the FuntouchOS about 2 days. Everything works fine, except the portrait mode and the AOD. Cant use it anymore.
Oh I see, now that is weird that the portrait mode is not working. So even if you switch not all functionality has returned. Thanks for the explanation. Hopefully someone can continue your work, and find a solution for a seamless transition.
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
hope to see some good news from you sir.
hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3
Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
Update us...
have you been able to solve it?
amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
NHQ Thang said:
how did you relock the bootloader, does the portrait mode work again?
Click to expand...
Click to collapse
same question
adkana4310 said:
Update us...
have you been able to solve it?
Click to expand...
Click to collapse
If u asking me so no im still on the same cant flash
redwatch99 said:
hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3
Click to expand...
Click to collapse
Someone who can help me solve it ?