Problems with flashing OS - Moto E4 Plus ROMs, Kernels, Recoveries, & Other De

Hello guys! I want help about my case.Firstly i unlocked bootloader and installed custom recovery,everything went fine.So i decided to try custom rom.Flashed it via recovery and after it boots i saw that sim card is not working.Checked if there is imei but it wasnt, so i go in engineering mode to add imei in fm receiver,but this tab was grey and i cant enter it. Than i tried via terminal but without success.Also i got wifi and gps problems and decided to flash stock rom,so formated phone via sp flash tool and give it a clean os.Everything was fine till it start booting i saw it was too fast and phone started.There was the same bug i cant enter imei and baseband is unknown .I tried diffrent stock roms but no luck.Everytime after flash it was like nothing happend and booting super fast.BTW i cant lock the bootloader also,it says device unlocked.

flashing with mfastboot worked
here is the link with instructions : https://www.hardreset.info/devices/motorola/motorola-moto-e4-plus/faq/firmware-flash/

Related

High debolated,, lg k7 rom's , twrp flashable zip's

Expired
Access to doc-00-2k-docs.googleusercontent.com was denied
I cant access the page.
sorry ,, the for the useless google drive broken links ,, i will update the links now
I updated all,,links now u see
This is fantastic. I'm using the t-mobile version. It's excellent, but I'm having a problem with wifi. Does anyone have any recommendations?
change ur wifi region in router webpage to north america and see
i tested this,, this both zips 5 to 6 times ,,but there is no problem for me ,,
go to ur router webpage ,,,and change ur wifi region to north america ,,and then ur phone will start detecting ur region
even i use to change my wifi region in router page to north america,,the my wifi started working
u follow this link here for ur problem :- https://youtu.be/IJ6Vj9_S4QE
So, i was working on an lg k7 and was told to remove the factory reset protection. Which that is apart of the set up wizard for lg so I removed that. Yes it was rooted. But, when I rebooted the device It said security error, authentication error #9 (modification). Ok, so I researched and it is fixable, but the lg download tool will not find the device. The download driver screen goes to 100% and I left it there for a couple hours and theres nothing. and the same exit button remains. I have tried the kdz download and that didnt work either. tried odin or twrp, which twrp is already on the device, but I cannot access anything. Any help with this? been working on it for weeks and its nothing but a head ache.
one thing u did completely wrong process,, setup wizard is a part of LG OS ,,IF U REMOVE IT WILL BREAK UR OS
THE MAIN REASON WHY YOU ARE NOT ABLE TO BOOT INTO RECOVERY IS THIS ONE :- [KERNEL/RECOVERY IS NOT SEANDROID ENFORCING] ON BOOT ,, IF U REMOVE IT FROM BOOT IMG ,THEN IT WILL MAKE U TO BOOT INTO RECOVERY,, AS IT WILL PROTECT U TO BOOT INTO CUSTOM TWRP RECOVERY ,,SO ULTIMATELY U NEED ONE [KERNEL/RECOVERY IS NOT SEANDROID ENFORCING] ON BOOT ,,REMOVED BOOT IMG
So, how do I obtain that one kernal/recovery and flash it on that phone?
Thank you for the quick and detailed reply.
My router is set up correctly.
I also have two identical LG K7 devices. The only difference is that one has your rom and the other is rooted stock.
The one without your rom can connect to Wifi with no issue.
The other one cannot. I enable Wifi and it hangs, as does Bluetooth. The Wifi Icon flashes consistently. Bluetooth just gives an error and goes off.
I believe that another member is having a similar issue, as posted here.
First of all ,,u unlock it boot loader ,,,boot up it android
Go to settings
,,after that go to software info
,,then after go to about phone,and,, Tap the build number until u see you are a developer message
Get into developer options now
Then enable USB debbuging and OEM unlock
Then download Android SDK platform tools
After that open a command windows ,,on the directory where u extracted adb ,,now type adb devices ,,,u will get one pop up like allow RSA key in it phone,,u just allow it,,
Now type command :- adb reboot bootloader
After that it will reboot bootloader,,note bootloader unlock commands are present on the display of the mobile
Note if it device does not support bootloader unlock ,,then it will not allow ur phone into bootloader
After that root ur phone with kingroot or kingroot
Then use flashify to flah twrp
RahulMantha said:
Expired
Click to expand...
Click to collapse
Oh no!

Dead phone

Hello guys,
I'm not a noob when we speak about flashing ROMs and unlocking bootloaders. I've been doing that for some years. Yesterday I flashed the new stock ROM for LG G4 - v29a, android 7.0. Everything went fine. Later this day, I've seen a post claiming that it was possible to relock your bootloader with this specific ROM using the fastboot oem lock. And it worked indeed. The problem now is that when I turn on the phone the following message shows up on RED: "Your device is corrupt. It cannot be trusted and may not work properly".
So, here's the problem:
1 - Can't access recovery;
2- Can't access download mode;
3 - Can't boot normally;
4 - Can't re-unlock since (i guess) the IMEI is now 0;
5 - Can't flash stock ROM using LGUP;
6- Can't erase any partition via adb since the bootloader is now locked;
So, basically all my ways are locked. Any fix you know and want to share?

Moto Z bricked OEM Locked

Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
I'm with same problem here!
Suckmymfdick17 said:
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
Click to expand...
Click to collapse
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
knjigo said:
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
Click to expand...
Click to collapse
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Suckmymfdick17 said:
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Click to expand...
Click to collapse
What do you mean with "I blocked my bootloader"?
Twrp is easy to flash. Root is integrated in ressurection remix rom. And this rom is great. Just try to flash twrp in Fastboot and than ressurection remix with twrp.
Can you boot in Fastboot?
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
tjgibri said:
I'm with same problem here!
Click to expand...
Click to collapse
I solved it, I finally flashed the stock rom to my phone and it works.
Apparently my pc was not flashing the stock rom in adb, and the phone turned off when loading the software. I did it 3 times until I load correctly and start well.
if you have the same problem apparently then OEM Blocking is not responsible. You have to flash the most current rom or the one that you had by default when the brick happened to you, you flash it in a normal way with commands of adb and ready, I would have to come back to life.
download from firmware center MotoZ Griffin the most current rom stock at 7.1.1
echo92 said:
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
Click to expand...
Click to collapse
Thanks for your help friend, I finally flashed it with a recent android 7.1.1 update. Apparently the OEM lockout was not the culprit, but it was an interrupted flash of android 7.1.1 at some point when loading the software to the phone, it would shut down on its own and not complete the installation, which showed me the mentioned message. I didn't realize that and thought it was the OEM blockade.
I finally did it on another pc and it worked. the phone came back to life.
I have one Moto Z2 Force (XT1789-05), bought from coolicool.com, I didn't know device came Unlocked Bootloader, Device rom had problem with many apps, I googled and found one topic in XDA developer to Install Stock Rom, I downloaded and Installed India Rom, it's worked somehow fine, but still had problem, I downloaded Verizon Rom, Android 8, after Installed Android 8 Verizon Rom, Locked device bootloader immediately, now device stuck at Welcome Wizard in Android 8, after select language I got this message: (Please wait, this may take a few minutes) this is proof video (http://ahmn.co/Upload/IMG_0161.MOV), after this issue, device already locked, I can't unlock, because need to go to the Developer Option in Setting, I stucked in Welcome Wizard, there isn't any bypass, So, I start to search in Google, XDA-Forum, Android Central and more, I created many threads, many requests, no one can't help me, I tried to reach google developer support to the tell to me how can I bypass Android 8 Welcome Wizard, there is must be a way, but I can't find it, now I can access to Android Recovery and Bootloader
1. if you help me to FORCE UNLOCK device without need Developer Option in setting my problem will solve
2. If you help me to Bypass Android Welcome Wizard, access setting and enable OEM Unlock
3. If you help me to update the device from Android 8 to Android 9 Verizon ROM via ADB Sideload or Update from SD card in Recovery mode
4. If you have any idea to how can I fix it
Extra Information: I bought Belkin and Uni USB-C to Ethernet Adaptor to help me bypass Android 8 Welcome Wizard, I bought WSKY WIFI Adaptor because device Wifi can't find any network (I found QR setup by tap several times in Language Selection), after this section need to download google device policy apk, my device can't find any Wifi Network and my Ethernet Adaptor can't help me either, So, I just remained with my phone, and I can't do anything,
Please, someone, help me
My Device SKU: XT1789-05

IMEI not showing up in Fastboot... while beeing recognized in stock system

hello guys, yesterday i just thought lets reflash a .kdz, because my phone was having problems with the MAC adress on Lineage.
i flashed v20d, phone worked, MAC was still 00:00:00:00:00, but i thought tf, i dont care, lets unlock and flash lineage again.
then i suddently realised that my unlock.bin didnt work.
if i check imei it says:
fastboot getvar imei
imei:
finished. total time: 0.016s
empty? the system recognizes the IMEI... maybe wrong bootloader/modem? i cant flash any bootloaders nor modems, because of my bootloader beeing locked/unlockable.
have a nice day
EDIT: thanks to my dumbness searching a whole night everywhere and trying to dump nv/reset imei and other (maybe even illegal) things i found a thread that describes the same situation:
flash .kdz in UPGRADE mode, then immediatly (without reboot) boot into stock recovery (which means data wipe). after this fastboot found my real IMEI.

Bootloader mode broken

This might be the first problem that everyone didn't encountered yet
So recently I unlocked my bootloader in order to flash custom ROM, but recently I reverted back to stock and decided to lock my bootloader in order to get OTA updates.after getting OTA updates I decided to unlock the bootloader again, when I was trying to boot to bootloader mode, it just shows the bootloader icon and boot back to system. I tried to use the in depth test app but it only shows me to request to exit deeptesting and the query status is not submitted.i tried to request to exit deeptesting but it only says no internet connection. I tried almost everything including flashing previous ROM, changing region, etc but none of it works
My device is Realms GT Master Edition (RMX3360) C.09In

Categories

Resources