I need help too. So, I own a Moto G5s plus sanders. I unlocked its bootloader the day I got it. Didn't keep any backup and rooted it. I Also installed dot os based on android 11. But my 4G Volte connection was finicky. So, I decided to use a Volte zip patch. But, anyways I flashed the zip via TWRP and tried to reboot. But the phone didn't turn on after that. After a few minutes to my shock I understood that I hardbricked my mobile. No button combos, nothing worked. Anyways in my desperation I found a YouTube video showing the use of blankflash to revive a phone and lo and behold I used the procedure to again restore my device. It booted to the fastboot interface. But my happiness was short lived. My baseband was unknown at this point and the bootloader was I dunno downgraded to 0.5 inplace of 2.12. But, more importantly the unlock status was lost. I unlocked it again and all went well. I could even flashed TWRP. but then I realised I couldn't upgrade my bootloader. I couldn’t do anything. It's always gives a "security downgrade", "preflash validation failed" and "permission denied" error. I even tried RSA official rescue tool from Lenovo but even it was unsuccessful. It was never unsuccessful before that. Not even with a unlocked bootloader. I researched for days and tried custom ROMs. I flashed stock images. Nothing brought back my baseband and IMEI. When I type "fastboot oem unlock critical" it gives me permission denied error with a message. "Need OEM signed bootloader." I think the blankflash bootloader is the root of all evil. I need to change it and therefore I need to enter the edl mode. I have tried all adb commands and fastboot commands. The phone reboots okay after those commands but never goes into edl mode whatsoever. I am also ready to do a controlled hardbrick of my device to go into the edl mode so that I can use my device again with a proper bootloader and a properly working fastboot. Please help
i think this vid will help
Greetings everyone. Sorry if I posted this in the wrong forum. Please move this in appropriate forum if I made a mistake. Believe me, for the last 7 days I have searched all of xda and internet, followed innumerable guides, FAQs and workarounds and none worked. So, as a last resort I am starting this thread
Device: Motorola Moto G5s Plus XT1804 ......4GB _64GB variant
Problem: 1) Baseband not found (unknown) Original Baseband: M8953_52.61.07.98R SANDERS_INDIADSDS_CUST
2) IMEI 0 (Sim cards are not detected).
I bought this refurbished phone about an week ago after my last LG went kaput. I was happy by the build quality of the phone. But it only ran Android 8.1 Oreo. So, I decided to put a custom ROM in it. I am not exactly a newbie to the world of CyanogenMods, Lineage OSes and Pixel Experiences. Or, so I thought. Anyways, after a lot of searching I finally decided on Dot OS 5.2 Official Android 11 version. The ROM looked very pleasing and the reviews looked positive. So, I got the unlock key from Motorola website, unlocked the bootloader, put in official TWRP recovery in it. Everything went like a breeze and in all that excitement I forgot to take a backup of the persist, efs and other partitions. A very costly mistake it seems. DotOS booted fine and looked really fresh till I found that there is a small cross near the SIM card network signal triangle up righthand side corner and the signal is only LTE and not VOLTE. I was using a Vodafone Sim card at the time. Although VOLTE option was enabled in SIM settings. To confirm my doubts regarding VOLTE I switched to a JIO Simcard and alas I was not able to make a call without redirecting through the horrid JIO calling app. VOLTE was indeed not working. So, I looked up for a fix and I found a Volte ZIP file from here https://www.google.com/url?sa=t&sou...0QFnoECBAQAQ&usg=AOvVaw0YgJvCjQWXXV8WQSJkxBOK . This was the starting of my troubles. I flashed the universal VOLTE fix zip from TWRP and it flashed fine. On rebooting, I found to my shock that my phone was not turning on. I pressed and held the power key and there was no sign of life. I couldn’t go to the fastboot bootloader or recovery. Only the white led blinked at the top when connected to the charger. My phone was apparently hard bricked. I searched frantically for a solution in this forum and YouTube wherein I found that one can bring it back to life by doing a blankflash. Found the blankflash file here https://www.google.com/url?sa=t&sou...wQFnoECAsQAQ&usg=AOvVaw1eVdBWGVFr8aiqLdP-ZkeT followed the instructions and it flashed my bricked device back to fastboot. I was relieved for a moment but the next I found that the Bootloader version has downgraded from BL C2 07 to BL C0 05. I knew something was wrong as bootloader downgrade shouldn't be possible. Also the unlock and rooted status were also lost and the baseband was unknown at this point. Anyways the device was recognised as a fastboot device and I tried to flash the stock ROM latest version using the fastboot. But, only then I realised there was something wrong with the bootloader. It gave errors like security downgrade, permission denied, preflash validation failed, remote command failed. At this point I was truly confused and worried. Why would it think the latest bootloader to be a security downgrade to a supposedly old bootloader and prevent me from flashing it. However it did flash the other files like gpt.bin for partition, oem.img, boot.img, system.img sparsechunks and everything else. I booted back to Android 8.1 Oreo and everything seemed working except my IMEI now read zero and my Simcard was not recognised by the device. After that I again unlocked my bootloader. Somehow the original unlock key worked and the bootloader screen said flashing unlocked but the bootloader didn't behave like an unlocked bootloader. The TWRP installed fine but couldn’t install the latest Pixel Experience. The flash screen said PE 11 was for Sanders and my device is (blank no name). I tried both the normal and plus and both behaved similarly. Lineage OS unofficial builds behaved similarly. I again tried Dot OS and Arrow OS and both installed fine except there was no signal. For a moment I tried to forget about the bootloader but concentrated on recovering my IMEI and Baseband but I couldn’t. For nearly 5 days I tried different guides including a detailed guide using Validus Sanders ROM but none worked. My EFS folder has files around 12 megabytes but my Persist seems deleted at zero bytes. The IMEI keeps changing between null, zero and unknown depending on the 20 something ROMs I tasted on this device. At this point, I am at a loss. This was to be my main phone and I am financially crunched. I can't buy another phone right now. I think that blankflash bootloader is corrupted and it is giving me permission denied errors. Even Magisk won't work properly. I even tried using the official rescue and smart assistant tool by Lenovo and it failed at 47 percent. I tried in different computers and Win7 to Win 11 OSes but it was of no use. I also tried getting a QCN file but I couldn’t get one for the device to recover the IMEI. Please suggest something if anyone of you can save this poor device of mine. Thanks in advance
Raghaov said:
i think this vid will help
Click to expand...
Click to collapse
Thanks for the quick reply but my phone is soft bricked now. It was hardbricked and I uses a faulty blankflash bootloader to bring it back to life. My device is softbricked now. I have lost my baseband and I have no IMEI. I cannot take calls and no mobile data. Can you show me a way to go to edl mode in my device. Thanks again.
can your phone turn on if yes can you root it with magisk
if yes then pls tell me i will tell you
I can do everything except calling and mobile data. Yes, I have rooted with Magisk and have root access. But my baseband is unknown and my IMEI is showing zero. I can't call or access mobile data. Although I can use wifi
I have tried what is shown in this video already. Didn't work
I think the blank flash bootloader was corrupt or of a different region.
so go to magisk manager and on top-right corner you will see setting click the button right next to it and click on reboot to edl
I didn't even knew that. Trying asap. Will update
Doesn’t work. Reboots back to system.
Updated Magisk to latest and tried both edl and download mode like you said brother. Everytime boots back to system. Am I missing something. The phone was not connected to the PC at the time
I am on stock Oreo now. Rooted and twrp installed
An interesting observation while installing Xposed, it gave an error that the device is not rooted properly
I have an untouched dump file for my model. The whole thing. Could you please guide me how I can restore my smartphone from that.
can you flash it through adb sideload fastboot twrp etc
I don't know but I sold the device. I bought a new one. Thanks @Raggaov for the help.
you're welcome
Related
I have never had a phone that has caused headaches like this one!!!
I have a jeter xt1922-2 and for nearly a month now.....suffered problems galore..... Ill explain....so take a seat.....and listen
I unlocked the bootloader the official way, all went swimmingly, then i followed quiksilvers guide to twrp....etc
but suffered problems with the phone in a reboot loop....
so, i thought, as its early days, i will flash a stock rom (i could only find a ALIJETER image, which was the only firmware i could find.....
So i did all the fastboot commands but the bootloader.img and partition thing said fail (phone said BAD KEY) but phone booted, after encrypting......
so for a week or so, I disabled a lot of items, and used non-root adblocker......was enjoying using the phone...
after a bit more time....I thought i would do the ota.....well that installed, and funnily enough, my OEM locking in dev settings was usable again.....so i did that, and installed twrp and root (phone now saying N/A), and had the phone purring like a cat.....but.......
i started to see firmware images becoming available, including JETER firmware, so naturally i downloaded the only one for my region - the UK.... file name : JETER_RETAIL_8.0.0_OPP27.91-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
so i tried flashing, but after the same sort of errors as before, it booted into the blue moto screen, and stayed there...
I saw somewhere, that if you relocked bootloader, it should be okay.....
so i tried fastboot oem lock ......... it gave a lot of errors and didnt lock........so i read a few more forums
and was told to try 'fastboot flashing lock' ......... and it worked.....locked again! but when trying to flash anything it failed.....so i tried everything to unlock again, but spent 6 hours trying to sort it, no luck....so i went to bed....
this morning, i thought to myself.........try unlocking via the way i did before, get code from motorola, so did all that, still not unlocked, and thought i would try fastboot flashing unlock .... it unlocked again!!!
and that brings me to the present time.......
tried the jeter firmware.....still the same as before........
tried the original alijeter firmware as i first tried, it boots and works, albeit with the BAD KEY message.....
How did i get that OEM option NOT GREYED OUT in dev settings???
How can i get the OTA to update again, as when i try again, it downloads, but when updating, it goes straight to the BOOTLOADER ...... ?!?!?!
I just want the phone to get back to normal......working twrp, root....etc like i did have it....
Fellow Moto G6 play users....please help a old man!!!!
biggary said:
I have never had a phone that has caused headaches like this one!!!
I have a jeter xt1922-2 and for nearly a month now.....suffered problems galore..... Ill explain....so take a seat.....and listen
I unlocked the bootloader the official way, all went swimmingly, then i followed quiksilvers guide to twrp....etc
but suffered problems with the phone in a reboot loop....
so, i thought, as its early days, i will flash a stock rom (i could only find a ALIJETER image, which was the only firmware i could find.....
So i did all the fastboot commands but the bootloader.img and partition thing said fail (phone said BAD KEY) but phone booted, after encrypting......
so for a week or so, I disabled a lot of items, and used non-root adblocker......was enjoying using the phone...
after a bit more time....I thought i would do the ota.....well that installed, and funnily enough, my OEM locking in dev settings was usable again.....so i did that, and installed twrp and root (phone now saying N/A), and had the phone purring like a cat.....but.......
i started to see firmware images becoming available, including JETER firmware, so naturally i downloaded the only one for my region - the UK.... file name : JETER_RETAIL_8.0.0_OPP27.91-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
so i tried flashing, but after the same sort of errors as before, it booted into the blue moto screen, and stayed there...
I saw somewhere, that if you relocked bootloader, it should be okay.....
so i tried fastboot oem lock ......... it gave a lot of errors and didnt lock........so i read a few more forums
and was told to try 'fastboot flashing lock' ......... and it worked.....locked again! but when trying to flash anything it failed.....so i tried everything to unlock again, but spent 6 hours trying to sort it, no luck....so i went to bed....
this morning, i thought to myself.........try unlocking via the way i did before, get code from motorola, so did all that, still not unlocked, and thought i would try fastboot flashing unlock .... it unlocked again!!!
and that brings me to the present time.......
tried the jeter firmware.....still the same as before........
tried the original alijeter firmware as i first tried, it boots and works, albeit with the BAD KEY message.....
How did i get that OEM option NOT GREYED OUT in dev settings???
How can i get the OTA to update again, as when i try again, it downloads, but when updating, it goes straight to the BOOTLOADER ...... ?!?!?!
I just want the phone to get back to normal......working twrp, root....etc like i did have it....
Fellow Moto G6 play users....please help a old man!!!!
Click to expand...
Click to collapse
Bad key is on all Moto devices after you unlock the bootloader. Once you get rid of dmverity it should change to n/a. Don't know why you keep flashing things like that. Your lucky the bootloaders didn't flash.
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
--> From Motorola, but do at your own risk, as always! <---
Lenovo Motorola Smart Assistant - "lmsa"
I've played with, and done some more research on lmsa.
I am wondering if this would help some folks here.
Please report back success or failure and your particular symptom so others will know.
NOTE: my phone is bootloader unlocked XT1900-1 One fi which OTA'ed itself up from 8.1 to 9 Oct 1 '19 security.
If you are able to back anything up, do so before you do this - if successful, it will flash your phone.
go here
https://www.motorola.com/us/lenovo-motorola-smart-assistant
and download it.
Watch the video for software issues(lower left of that page).
Install it.
Start it up.
You want flash/ rescue.
follow the instructions and put your phone into fastboot mode and connect to PC via USB.
If it offers you something(takes a minute), click the little download arrow and when it's downloaded, click rescue.
This is what it looks like for me before I would click the download arrow.
I believe this tool is for people who have a locked bootloader, never unlocked? LMSA won't recognize my device. RSD lite won't either.
Persistent memory has some value that is not overwritten by Wipe All twrp? Of course I will never relock.... just a heads up to others.
I am one of the few.... 1900-1 Fi working fine on Aug Pie factory and wanted to try ionOS. Flashed fine and working good. Now 3 carriers in my area only US Cellular has service. T-Mob--, Sprin- coverage area 10 - 0% Found as I have before No ROM other than stock for ME can get Data services to work on all three carriers in my area. So for data services trying to reflash back to stock. NO factory image successfully flashed will have modems working. For me. Tried many forms of flash modems only via fastboot, nope.
Different flavors of ADB don't help. Now I haven't tried "Hardware tools loader" style because if wrong will brick it. Unless some one has? Various forms of flashing modems, flash all scripts, ADB versions, Hardware only flash from two ROMs (which is why I am here I think) the Wipe All needed for those two roms some how did it? No blame, just for some reason can't flash back to stock. Others have but....I can't. So hoping a forward update by Motorola Factory Image will do a complete modem working Flash.
kkjb said:
I believe this tool is for people who have a locked bootloader, never unlocked? LMSA won't recognize my device. RSD lite won't either....
Click to expand...
Click to collapse
My phone IS bootloader unlocked - I bought it used(ebay) and it came to me that way with a fresh 8.1 It gives the usual bootloader unlocked error message on boot. It has OTA updated itself to 9 Oct 1 '19 security. I have not tried to modify it because that would prevent me from getting future OTAs.
RSDlite latest (6.2.4) does not recognize my phone. That is RSDlite's fault. I don't think it is yet capable of an A/B phone, let alone a full Treble (ours, on 9, are not full Treble, only partial but DO have A/B sets of partitions).
From the attached pic you can see it was ready to flash my phone with the latest stock ROM appropriate for my device which is a 1900-1 One fi, even though it was unlocked.
I am guessing that Motorola invented lmsa to stem the flow of trashed phones to Moto factory repair. It wouldn't surprise me if it would auto blankflash if necessary.
Try it - it only takes a minute or 2 to test! The worst it can say is "no"!
Understand, tried all the options and LMSA needs I think a stock recovery, boot, fastboot flash mode. The various options show "phone not recognized" no mode available with twrp installed to goto Factory Flash as LMSA appears to wait for in Bootloader Mode. So the drop down box screen will not appear since not recognized.
This post was just a update as you had asked for others to give their results. So going to do hand flash of factory images again, see if try many times... and some how one works
kkjb said:
Understand, tried all the options and LMSA needs I think a stock recovery, boot, fastboot flash mode. The various options show "phone not recognized" no mode available with twrp installed to goto Factory Flash as LMSA appears to wait for in Bootloader Mode. So the drop down box screen will not appear since not recognized.
This post was just a update as you had asked for others to give their results. So going to do hand flash of factory images again, see if try many times... and some how one works
Click to expand...
Click to collapse
Thanks.
Bummer this didn't work for you.
Yeah phone definitely needs to be in fastboot mode.
Hopefully it will help others.
Yeah, back when RSDlite worked you could "sledge hammer" just about anything if it would boot to fastboot! Hopefully they will upgrade it...
No Thank You, you gave me some ideas about the a/b devices thoughts. We have the odd ball not 9.0 at release device so the a/b script is different than some devices. So with the newest ROMs using fastboot "flash all zip scripts" for a/b boot slots I think the problem is factory images want something else for the modems. Oddly the factory images flash fine with no errors just that no modems...imei, wifi, blutooth. 8.0,8.1,9.0 all. Its a weird problem.
kkjb said:
No Thank You, you gave me some ideas about the a/b devices thoughts. We have the odd ball not 9.0 at release device so the a/b script is different than some devices. So with the newest ROMs using fastboot "flash all zip scripts" for a/b boot slots I think the problem is factory images want something else for the modems. Oddly the factory images flash fine with no errors just that no modems...imei, wifi, blutooth. 8.0,8.1,9.0 all. Its a weird problem.
Click to expand...
Click to collapse
Yeah I was thinking a-/b prob
If you ran the "flash all fi bat" to install ionOS it would have worked well since, with Aug 9, you were in a 2 file system phone. so i am guessing
a) you would only have success flashing a 9 stock (fi or not)
b) you would probably have to do a preliminary flash with just the stock 9 bootloader etc (the stuff before the ping. as well as maybe the 2 modem erases later in the command stack - some playing needed there...) tons of guesswork and luck needed here!
c) I found it humorous that ionOS script made b active but I hope the dev knew what he/she were doing.
edit d) so what partitions set is active after you flash your tests? ie you flash something, but what are you then booting to - unless you set something active... I don't believe there is a default - just last successful - though I assume if one fails it will try the other. Perhaps endlessly.
But, yeah, I can see why that flash went well. But of course you are then stuck with the modems they flashed and how that particular opsys planed to use them. US cellular is apparently known to be iffy on the X4 since I saw that caveat on a number of ebay x4 sales - "not guaranteed for...". And Sprint, of course is cdma but is supposedly accessible as LTE by fi??? I have zero knowledge there!!!
WARNING WHEN DEALING WITH ME - I TEND TO MAKE A POST AND THEN KEEP EDITING IT ENDLESSLY>>> SORRY!
Most of the time I am the guy helping people out. This time I think I did something pretty dumb.
I have an old "beater" P9 plus that I was using as a casual gaming device. Most of the apps I was using were beginning to no longer be supported because for some reason the device NEVER updated. Any time I check for a possible update the phone stated it was up to date. After much searching I discovered that this device SHOULD have updated quite a few times.
I used firmware finder to find a supported update and the first one went somewhat unexpected. The firmware was downloaded and put in the correct folders but kept failing after 5%. I decided that the next thing to do was to find a cool rom and go through the process of unlocking and installing TWRP. I usually try to install the latest TWRP. This turned out not working at all so I went for an older version and it booted into TWRP, however it found the update and installed it!
I kind of wanted to keep it stock, but updated stock so I went for a bigger upgrade to Android 7 firmware. This only worked partially and (stupid and I know better) forgot to do a backup. I did not know that TWRP was gone and root was gone. The battery died and I rebooted like normal and there was a much improved interface. However, a good bit of stuff stopped working like bluetooth and the boot screen was in red stating the device can't be verified and ended up in something like a NOR905 test keys build. I did a backup, selected a downgrade package that was checked and "updated" to the downgraded firmware through Project Menu. It successfully stated it was 100% complete.
Now it is stuck on the boot screen for an unlocked device.
What works (or is possibly a good thing):
The hardware keys can get me to the bootloader (fastboot)
ADB recognizes the device is in fastboot
Phone is Unlocked
FRP is unlock
What doesn't work:
Everything else. All I have is fastboot and an unlocked bootloader. I can try to flash recovery but that never boots, it just stays suck on the recovery boot screen. The system will not boot at all.
UPDATE:
I broke down and spent the money to use the DC-Phoenix software to unbrick the phone. Several of the options for firmware did NOT work. The one file set that did work was to use this firmware:
VIE-L29_C900B101_Firmware_countryValue_Nonspecific_Android_6.0_EMUI4.1
Then use this as the customization:
update_data_C900B101_hw_default
The phone originally started out as VIE-L29C636B130. This changed it to VIE-L29C900B101 and is on EMUI 4.1 android version 6.
Now the fun part is going to see if I can find a version of TWRP that will work and see if I can root it. Maybe even try a custom ROM. We'll see though. The device is just an old beater for fun. But at least, she's not broken anymore. Guess I'll grab a beer and celebrate my "unbricked" device.
Well, i tried to flash a custom rom on my Moto g5s plus (XT1805 dual sim) i made a EFS backup through TWRP. At some point i got an error in the fastboot screen, something that says like "Startup failed", i fixed it with Lenovo RSA, then when i try to install the stock rom, with efs backup and everything, it doesn't have signal, and in the moto actions app doesn't appear the "one button navigation" option, then i installed different kernels to try to fix it, the thing is that it hardbricked, i don't remember exactly what i did to hardbrick because it was a couple months ago, but i'm pretty sure it was a custom kernel.
The phone was completely dead, except for a white led blinking when i connected it to my computer. Did a bit of research here on XDA and some forums, and found a "blankflash" file, it worked like magic and my phone was again alive, but without signal and moto fingerprint gestures option not appearing, everything else was fine, Wi-Fi, Bluetooth, Camera. Then i tried to flash again the kernel that hard bricked it, believing it would work this time, and big surprise, hard bricked again. I tried to fix it using the method that worked me in the past, but then the blankflash file was giving me an error, i tried to search another blankflash but no luck, no one was working. Then i found a reddit post and finally worked, alive again but in same conditions, no signal and moto actions not working.
I don't really know what is wrong with my phone, i'm believing that Lenovo RSA installed a wrong version of whatever it fixed. I'm on a dead end, and i cannot find more info about a similar problem anywhere, and Lenovo RSA now says something like "The model associated with the IMEI for your device is not currently supported by RSA."
I'm out of options, and my last chance is to ask here if someone can give me a hand.
Edit: I also tried fastboot erase abl and fastboot erase bootloader idk why, but it gives me an error like "Permission denied".
p.s that command deletes bootloader partition, high risk of hardbrick