Related
I unlocked BooTloader,and from 2.3.3 i went to 2.3.2
and i get this ERROR!
android.proccess.acore stopped working
i cant even acces Market >_>
i used Lyllo- something's guide
Here is the CMD for RooT:
C:\Users\Guest\Desktop\fastboot>fastboot flash system play_modded.img
sending 'system' (236189 KB)...
(bootloader) USB download speed was 5082kB/s
OKAY [ 55.564s]
writing 'system'...
(bootloader) Flash of partition 'system' requested
(bootloader) S1 partID 0x00000004, block 0x000002e4-0x00000ca7
(bootloader) Erasing block 0x00000300
(bootloader) Erasing block 0x00000400
(bootloader) Erasing block 0x00000500
(bootloader) Erasing block 0x00000600
(bootloader) Erasing block 0x00000700
(bootloader) Erasing block 0x00000800
(bootloader) Erasing block 0x00000900
(bootloader) Erasing block 0x00000a00
(bootloader) Erasing block 0x00000b00
(bootloader) Erasing block 0x00000c00
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 44.905s]
finished. total time: 100.469s
if anyone knows how to fix this,please tell me!
Another thing,im stuck at 2.3.2,i cant do OTA (Software update -> Phone Info) so what do i do...?
R800i
Cat_On_Droid said:
I unlocked BooTloader,and from 2.3.3 i went to 2.3.2
and i get this ERROR!
android.proccess.acore stopped working
i cant even acces Market >_>
i used Lyllo- something's guide
Here is the CMD for RooT:
C:\Users\Guest\Desktop\fastboot>fastboot flash system play_modded.img
sending 'system' (236189 KB)...
(bootloader) USB download speed was 5082kB/s
OKAY [ 55.564s]
writing 'system'...
(bootloader) Flash of partition 'system' requested
(bootloader) S1 partID 0x00000004, block 0x000002e4-0x00000ca7
(bootloader) Erasing block 0x00000300
(bootloader) Erasing block 0x00000400
(bootloader) Erasing block 0x00000500
(bootloader) Erasing block 0x00000600
(bootloader) Erasing block 0x00000700
(bootloader) Erasing block 0x00000800
(bootloader) Erasing block 0x00000900
(bootloader) Erasing block 0x00000a00
(bootloader) Erasing block 0x00000b00
(bootloader) Erasing block 0x00000c00
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 44.905s]
finished. total time: 100.469s
if anyone knows how to fix this,please tell me!
Another thing,im stuck at 2.3.2,i cant do OTA (Software update -> Phone Info) so what do i do...?
R800i
Click to expand...
Click to collapse
reboot the phone, if it still happens, hard reset! whatever you do, do not OTA, update via fastboot or flashtool
Nhialor said:
reboot the phone, if it still happens, hard reset! whatever you do, do not OTA, update via fastboot or flashtool
Click to expand...
Click to collapse
BIG question,will Hard Reset destroy my ROOT ,BL,and 2.3.2 ?and how do you/where do you update via fastboot? i need an Img. right and do the same thing like play_modded.img way correct?
i think i fixed the Acore problem...thanks
However,how do i upgrade to 2.3.3 with .184 ?
Cat_On_Droid said:
BIG question,will Hard Reset destroy my ROOT ,BL,and 2.3.2 ?and how do you/where do you update via fastboot? i need an Img. right and do the same thing like play_modded.img way correct?
i think i fixed the Acore problem...thanks
However,how do i upgrade to 2.3.3 with .184 ?
Click to expand...
Click to collapse
look around the development forum for an updated system image with 2.3.3 and .184 (probably gonna find it with .185), then you do the same thing, copy it into the fastboot folder and say fastboot flash system system.img and you're laughing
and yes, play_modded.img was the right thing
Also, i'm fairly confident in saying that Hard reset doesn't loose you root or anything like that, just apps and the likes get deleted!
Nhialor said:
look around the development forum for an updated system image with 2.3.3 and .184 (probably gonna find it with .185), then you do the same thing, copy it into the fastboot folder and say fastboot flash system system.img and you're laughing
and yes, play_modded.img was the right thing
Also, i'm fairly confident in saying that Hard reset doesn't loose you root or anything like that, just apps and the likes get deleted!
Click to expand...
Click to collapse
done and done.
I was using Resurrection Remix 7.1.1 Then I decided to install ElementalX.
I noticed that the unit was heating up.
Today when I woke up the device did not start anymore, it stayed on a black screen.
I decided to find a solution here in the forum.
I found this tip:
Https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
The device is back on again.
But I can not revert to stock rom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I try to upload GPT.bin it returns this error:
(Bootloader) Security version downgrade
(Bootloader) Image primary_gpt failed validation
(Bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 0.05s
Same thing with bootloader.img
E: \ cel \ motog4> fastboot flash bootloader bootloader.img
Target reported max download size of 536870912 bytes
Sending 'bootloader' (3651 KB) ...
OKAY [0.119s]
Writing 'bootloader' ...
(Bootloader) validating: bootloader.default.xml ...
(Bootloader) Invalid partition name aboot
(Bootloader) will fail: flash: aboot
FAILED (remote failure)
Finished. Total time: 0.213s
I spent the whole dawn trying a solution, downloaded all the stocks I found on the internet and had no solution.
Same thing with recovery.
E: \ cel \ motog4> fastboot flash recovery recovery.img
Target reported max download size of 536870912 bytes
Sending 'recovery' (16484 KB) ...
OKAY [0.522s]
Writing 'recovery' ...
(Bootloader) Invalid partition name recovery
FAILED (remote failure)
Finished. Total time: 0.530s
I've tried all these ROMs
My device is an XT1640
According to the getvar the information is these.
E: \ cel \ motog4> fastboot getvar all
<Waiting for device>
(Bootloader) version: 0.5
(Bootloader) version-bootloader: moto-msm8952-B1.03 (*)
(Bootloader) product: athene_16mp
(Bootloader) board: athene_16mp
(Bootloader) secure: yes
(Bootloader) hwrev: P2A
(Bootloader) radio: 6
(Bootloader) storage-type: emmc
(Bootloader) emmc: 32GB SKHYNIX HBG4a2 RV = 08 PV = E4 FV = 00000000000000E4
(Bootloader) ram: 2GB SKHYNIX LP3 DIE = 8Gb M5 = 06 M6 = 03 M7 = 00 M8 = 1F
(Bootloader) cpu: MSM8952
(Bootloader) serialno: xxxxxxx
(Bootloader) cid: 0x0032
(Bootloader) channelid: 0x19
(Bootloader) uid:
(Bootloader) securestate: oem_locked
(Bootloader) iswarrantyvoid: yes
(Bootloader) max-download-size: 536870912
(Bootloader) reason: Failed to initialize partition table
(Bootloader) imei: 000000000000000
(Bootloader) meid:
(Bootloader) date: 01-01-1970
Bootloader sku: 000000000000000
(Bootloader) battid:
(Bootloader) iccid:
(Bootloader) cust_md5:
(Bootloader) max-sparse-size: 268435456
(Bootloader) current-time:
(Bootloader) ro.build.fingerprint:
(Bootloader) ro.build.version.full:
(Bootloader) ro.build.version.qcom:
(Bootloader) version-baseband:
(Bootloader) kernel.version:
(Bootloader) sbl1.git: sbl1.git
(Bootloader) rpm.git: rpm.git
(Bootloader) tz.git: tz.git
(Bootloader) hyp.git: hyp.git
(Bootloader) keymaster.git: keymaster.git
(Bootloader) cmnlib.git: cmnlib.git
(Bootloader) aboot.git: git = MBM-NG-VB1.03-0-gb44c0ee
(Bootloader) qe:
(Bootloader) frp-state: no protection (err)
(Bootloader) ro.carrier:
All: listed above
Finished. Total time: 0.106s
Was the above flashing tested with the GPT.bin from the 93-14 stock ROM file that you have? As you've noted, you can't downgrade your GPT (though at the moment we have no GPT or a corrupted partition table), so if you haven't, try flashing with the latest GPT.bin we've got access to.
You may also like to re-try with the blank flash and procedure from this post:https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23
echo92 said:
Was the above flashing tested with the GPT.bin from the 93-14 stock ROM file that you have? As you've noted, you can't downgrade your GPT (though at the moment we have no GPT or a corrupted partition table), so if you haven't, try flashing with the latest GPT.bin we've got access to.
You may also like to re-try with the blank flash and procedure from this post:https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23
Click to expand...
Click to collapse
Yes i try with 93-14 stock ROM.
XT1640_ATHENE_NPJ25.93-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Samething at now
As you can see I tried all these roms.
All GPT.BINs that are inside of them
The question is:
How to force to enter em qboot again to make this procedure from this post:https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23
ricardomilena said:
Yes i try with 93-14 stock ROM.
XT1640_ATHENE_NPJ25.93-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Samething at now
As you can see I tried all these roms.
All GPT.BINs that are inside of them
The question is:
How to force to enter em qboot again to make this procedure from this post:https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23
Click to expand...
Click to collapse
Bro, you are on the blank bootloader, I don't think you can get back there. You might have just been flashing the wrong gpt.bin and bootloader all that time?
Retry flashing the NPJ25.93-14 gpt.bin and bootloader.img, being tired and frustrated can cause lots of damage to your focus.
MK+2017 said:
Bro, you are on the blank bootloader, I don't think you can get back there. You might have just been flashing the wrong gpt.bin and bootloader all that time?
Retry flashing the NPJ25.93-14 gpt.bin and bootloader.img, being tired and frustrated can cause lots of damage to your focus.
Click to expand...
Click to collapse
I extracted all gpt.bin and bootloader.img to each separate folder.
I tried one by one but it still does not work
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.073s
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.119s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Invalid partition name aboot
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.216s
I try with this Extracted gpt.bin and bootloader.img from this archive.
https://cloud.mail.ru/public/CKF3/AWVREk6s9
Same thing
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.073s
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.119s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Invalid partition name aboot
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.216s
ricardomilena said:
I extracted all gpt.bin and bootloader.img to each separate folder.
I tried one by one but it still does not work
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.073s
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.119s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Invalid partition name aboot
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.216s
I try with this Extracted gpt.bin and bootloader.img from this archive.
https://cloud.mail.ru/public/CKF3/AWVREk6s9
Same thing
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.073s
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.119s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Invalid partition name aboot
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.216s
Click to expand...
Click to collapse
This is weird. When it says "downgrade" then it really sees itself higher than the file version you are trying to flash! Really weird.
Since you already tried gpt.bin of NPJ25.93-14 I cannot advise you to try the gpt.bin of the latest OTA NPJ25.93-14.4: if it works it would only prove that you have hope, but you won't be able to proceed further because OTA packages do not include fastboot flashable bootloader and boot images (else I would have used them myself to get out of CID = 0xDEAD problem of my older dead XT1642)
If it does not work, however, it would only tell that something really awkward happened to your phone. Can't even tell if it would be a bad blankflash for your model?!
ricardomilena said:
I extracted all gpt.bin and bootloader.img to each separate folder.
I tried one by one but it still does not work
Click to expand...
Click to collapse
This is trivial, but please triple check what you're trying to flash. I've got this errors on older Moto Gs (the G 2015 to be specific) because I used a firmware for the 1GB version against the 2GB version. Verify carefully.
@ricardomilena Just wanted to confirm whether you installed 93-14-4 update. If you did you'll have to wait till 93-14-4 images are available. If you didn't took that update then 93-14 bootloader & gpt should work. First flash gpt then flash bootloader then reboot to bootloader & finally you can flash all stock image as usual:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
PS- See if you get success with the below attached gpt.bin it's from the new 93-14-4.
lCrD512 said:
@ricardomilena Just wanted to confirm whether you installed 93-14-4 update. If you did you'll have to wait till 93-14-4 images are available. If you didn't took that update then 93-14 bootloader & gpt should work. First flash gpt then flash bootloader then reboot to bootloader & finally you can flash all stock image as usual:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
PS- See if you get success with the below attached gpt.bin it's from the new 93-14-4.
Click to expand...
Click to collapse
Just the other day this happened to me as well I was flashing Invicta and went to reboot into recovery once I set up the ROM and I got the black screen only the notification light would blink after many attempts of trying to flash everything to get it up and running I had had to flash that 40 megabyte update of the partition table and that solved it then you have to go and Flash the entire firmware don't forget to flash the bootloader right after flash the GPT. Bin
Sent from my Moto G4 using Tapatalk
lCrD512 said:
@ricardomilena Just wanted to confirm whether you installed 93-14-4 update. If you did you'll have to wait till 93-14-4 images are available. If you didn't took that update then 93-14 bootloader & gpt should work. First flash gpt then flash bootloader then reboot to bootloader & finally you can flash all stock image as usual:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
PS- See if you get success with the below attached gpt.bin it's from the new 93-14-4.
Click to expand...
Click to collapse
Lol bricked my device again (random brick) don't know why it happens. I've already installed the 93-14-4 update & as expected flashing stock firmware failed with 93-14 gpt file. I will try this gpt & report back.
same problam bro
plz guys solution this problam request you and contact me 7688888588 plz
Anish1216 said:
plz guys solution this problam request you and contact me 7688888588 plz
Click to expand...
Click to collapse
Have you tried this blank flash in this thread? https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
the same
Anish1216 said:
plz guys solution this problam request you and contact me 7688888588 plz
Click to expand...
Click to collapse
2019 and i have the same problem, any solution?
schondan0 said:
2019 and i have the same problem, any solution?
Click to expand...
Click to collapse
How did your device get bricked? Have you tried this blankflash? https://forum.xda-developers.com/showpost.php?p=79013024&postcount=523
echo92 said:
How did your device get bricked? Have you tried this blankflash? https://forum.xda-developers.com/showpost.php?p=79013024&postcount=523
Click to expand...
Click to collapse
i've tried a lot of gpt versions, I'm gonna try this one (thanks) and see if it works, I did blanckflash and now it shows the same error: (Bootloader) validating: bootloader.default.xml ...
(Bootloader) Invalid partition name aboot
(Bootloader) will fail: flash: aboot
FAILED (remote failure)
I TRIED, BUT I HAVE ALREADY THE PHONE ALIVE, I THINK I NEED A NEW VERSION OF BOATLOADER AND GPT THAT WORKS. (I'VE TRIED 6,0 AND 7,0)
schondan0 said:
i've tried a lot of gpt versions, I'm gonna try this one (thanks) and see if it works, I did blanckflash and now it shows the same error: (Bootloader) validating: bootloader.default.xml ...
(Bootloader) Invalid partition name aboot
(Bootloader) will fail: flash: aboot
FAILED (remote failure)
Click to expand...
Click to collapse
Hmm, is that with the blankflash GPT and bootloader or with the separate GPT and bootloader files?
Do you see errors when flashing the GPT? That error suggests your device doesn't have a partition map or had corrupted flash memory.
Depending on what GPT and bootloader you had previously, you may have to flash the GPT and bootloader from the Oreo stock firmware (but only if you had updated to stock Oreo in the past).
If you're still on stock Nougat, try this April 2018 GPT and bootloader https://drive.google.com/file/d/13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI/view?usp=drivesdk if you do get your device booting, please flash the latest firmware to your device
I got it
thanks a million, this 2018 version worked, now just flash firmware
---------- Post added at 06:11 PM ---------- Previous post was at 05:20 PM ----------
IS POSSIBLE TO RE-LOCK BOOTLOADER? (I DO'T WANNA TRY TO SELL THE PHONE OR GET WARRANTY BACK) I want to lock bootloader to give it to my mother, (I got one one plus 5t). Or if you have the link to oreo rom to install via adb I will be more grateful than I already am.
schondan0 said:
I got it
thanks a million, this 2018 version worked, now just flash firmware
---------- Post added at 06:11 PM ---------- Previous post was at 05:20 PM ----------
IS POSSIBLE TO RE-LOCK BOOTLOADER? (I DO'T WANNA TRY TO SELL THE PHONE OR GET WARRANTY BACK) I want to lock bootloader to give it to my mother, (I got one one plus 5t). Or if you have the link to oreo rom to install via adb I will be more grateful than I already am.
Click to expand...
Click to collapse
Here is the link for the Oreo stock firmware
https://forum.xda-developers.com/showpost.php?p=79100802&postcount=1056
please read the initial post of the thread https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
to flash the firmware and relock your device bootloader - you will need to use fastboot. Of course, locking your bootloader will erase your device and revert your device to full stock, but if you're handing the device to your mother, that's likely for the best. Back up as necessary.
THANKS, I DID IT ALL. IT ALL WORKED WELL, NO ERROR (INCLUDE THE COMMON ERRORS LIKE FINGERPRINT ERROR OR IMEI ERROR) AND THE OSCARS GOES TO YOU. THANKS THANKS THANKS MATE:fingers-crossed:
So i unlocked the bootloader using the code that you get from the motorola official website and then installed twrp. It all went just find, but then I flashed the magisk zip and tried booting up but no response. Its like the power button doesnt work at all. Fastboot mode is still working and i can get into the recovery, tried restoring the old backup, factory reset, installing a rom (RR) but no luck. pls help this fella
Wipe data. Install the ROM of your choice.
If that fails, flash your device's stock ROM.
You have to flash a custom kernel like ElementalX before rooting because magisk roots your phone by patching the boot image which isn't supported by the stock kernel! This is why your phone is not booting up!
If you can still access bootloader mode, try this https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Saumitraa said:
You have to flash a custom kernel like ElementalX before rooting because magisk roots your phone by patching the boot image which isn't supported by the stock kernel! This is why your phone is not booting up!
If you can still access bootloader mode, try this https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Click to expand...
Click to collapse
i see, will try this right now
Darkther said:
i see, will try this right now
Click to expand...
Click to collapse
You have to flash the custom kernel before rooting only when you are on stock or stock based roms and not on custom roms! Good Luck
Saumitraa said:
You have to flash the custom kernel before rooting only when you are on stock or stock based roms and not on custom roms! Good Luck
Click to expand...
Click to collapse
while flashing the images i am getting the following error
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.054s
Darkther said:
while flashing the images i am getting the following error
Click to expand...
Click to collapse
Looks like you are trying to get back to stock, follow the steps here
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Darkther said:
while flashing the images i am getting the following error
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.054s
Click to expand...
Click to collapse
If the above firmware isn't working, it might be because the firmware you're trying to flash is too old; you may have to flash the March 2017 firmware (the latest firmware we have) which is here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
my phone is hard bricked and the oem is locked and no custom recovery
tried to unlock oem but it gives this error
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.014s]
finished. total time: 0.015s
phone wont open how do i allow oem unlock
i even tried flashing stock rom as it does not required bootloader unlocks but stock rom wont install it gives error
C:\Users\MOHIT\Downloads\Compressed\ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
OKAY [ 8.242s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.715s
plz help me out guys .....:crying::crying::crying::crying:
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
tried this too but device get recognise
Cooltango26 said:
my phone is hard bricked and the oem is locked and no custom recovery
tried to unlock oem but it gives this error
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.014s]
finished. total time: 0.015s
phone wont open how do i allow oem unlock
i even tried flashing stock rom as it does not required bootloader unlocks but stock rom wont install it gives error
C:\Users\MOHIT\Downloads\Compressed\ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
OKAY [ 8.242s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.715s
plz help me out guys .....:crying::crying::crying::crying:
Click to expand...
Click to collapse
How did your phone got bricked?
According to you,you are trying to unlock bootloader but it doesn't succed. Why are you flashing stock rom in your phone?
plzz elaborate.
ADITYA_KUMAR said:
How did your phone got bricked?
According to you,you are trying to unlock bootloader but it doesn't succed. Why are you flashing stock rom in your phone?
plzz elaborate.
Click to expand...
Click to collapse
after the official update from ....update in my device .......my device was struck in boot loop ...so i tries flashing the stock rom to repair that ....during flashing it giving the above mention error ........
Only other things I can think of is perhaps holding down your power button (for up to 2-3 minutes) to force a hard shutdown, and then try booting. Alternatively, hold down both the power and volume down key, see if you can boot into the bootloader (which it looks like you can, if you're trying to fastboot the stock ROM). If so, then try to boot into the stock recovery and try a cache wipe or a factory reset (the factory reset will obviously wipe your data).
If your device is under warranty (and you did not unlock your bootloader at any point), the service centre might be the best bet for you, as we can't do anything with a locked bootloader and you're unable to boot to get to OEM unlocking...
The new [Updated] blankflash file for Moto g4 plus [June security patch ]
Hello friends
here is the new [Updated] blankflash file for June security patch
i hope it will help you. here is complete guide https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
about how to install it.
if it's works for you please let me know:highfive:
Hi,
I bought an essential ph-1 off a guy on ebay who claimed everything was fine with the phone. I turned it on when it arrived and it is stuck on powered by android. I can access fastboot, but the bootloader is locked. I contacted essential with the serial number and came to find out it was a store demo and they won't help. The guy on ebay is also gone. So now I have two options, either throw it away or find a way to get it to either recovery or some way to bypass the fastboot lock.
Does anyone have any ideas? Even when I issue a recovery from fastboot it still goes back to powered by android.
Thanks
Have you tried to sideload a fresh install? This can be done with a locked bootloader. Instructions are on essential's website.
kboya said:
Have you tried to sideload a fresh install? This can be done with a locked bootloader. Instructions are on essential's website.
Click to expand...
Click to collapse
Hi, as I mentioned I can not access android recovery. When I select the option in fastboot it reboots and goes back to the powered by android. I never see the green guy. Its like there is no recovery console. As such I can not sideload anything since I can not access recovery. I can only access fastboot and issue cmds.
I was hoping someone knew a fastboot oem *secretcmd* I could use to get around the locked bootloader.
also here is a dump from fastboot of getvar
fastboot getvar all
(bootloader) version:0.5
(bootloader) unlocked:no
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3796
(bootloader) version-baseband:2.0.c4-M1.2
(bootloader) version-bootloader:mata-4452425
(bootloader) variant:
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1986B57000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0x100000000
(bootloader) has-slot:nvdef:yes
(bootloader) has-slot:dsp:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:cmnlib:yes
(bootloader) has-slot:boot:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:abl:yes
(bootloader) has-slot:mdtp:yes
(bootloader) has-slot:mdtpsecapp:yes
(bootloader) has-slot:bluetooth:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slotmic:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:_a
(bootloader) slot-retry-count:_b:0
(bootloader) slot-unbootable:_b:yes
(bootloader) slot-successful:_b:no
(bootloader) slot-retry-count:_a:0
(bootloader) slot-unbootable:_a:no
(bootloader) slot-successful:_a:no
(bootloader) slot-count:2
(bootloader) slot-suffixes:_a,_b,
(bootloader) secure:yes
(bootloader) serialnoM1LHMCXXXXXXXX
(bootloader) product:Mata
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
Thanks
This sounds dumb but have you tried to unlock the bootloader
have you tried to do a fastboot -w?
techfreak243 said:
have you tried to do a fastboot -w?
Click to expand...
Click to collapse
The bootloader is locked, there is no way to enter recovery, just the powered by android appears while attempting to get to recovery via fastboot. Because it is locked a -w will not work as seen below:
fastboot -w
wiping userdata...
Creating filesystem with parameters:
Size: 109634220032
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 26766167
Block groups: 817
Reserved block group size: 1024
Created filesystem with 11/6692864 inodes and 468189/26766167 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.007s
I even just built an edl 9008 mode cable today to try and do the qualcomm flash mode and it won't go into it either. Any ideas?
Are you able to switch the active slot to _b?
_b slot might still have a usable recovery.
csrow said:
Are you able to switch the active slot to _b?
_b slot might still have a usable recovery.
Click to expand...
Click to collapse
Due to the bootloader being locked it won't allow it. see below and I appreciate the help.
C:\adb>fastboot --set-active=b
Setting current slot to 'b' FAILED (remote: Slot Change is not allowed in Lock State)
Finished. Total time: 0.000s
Hello
Unfortunately there is no solution to this problem I am also stuck with the same problem
I'm looking for a solution by EDL mode seems to be effective but I can not find my own flashcard
The important thing we have seen is any development..
mouraj2 said:
Hello
Unfortunately there is no solution to this problem I am also stuck with the same problem
I'm looking for a solution by EDL mode seems to be effective but I can not find my own flashcard
The important thing we have seen is any development..
Click to expand...
Click to collapse
How did you get it to edl? I made a cable that shorts D+ and gnd but when I try it, it does not put it into edl mode. Can you tell me how you did it? I even let the battery drain all the way and still it won't go.
Thanks
hellgod12 said:
How did you get it to edl? I made a cable that shorts D+ and gnd but when I try it, it does not put it into edl mode. Can you tell me how you did it? I even let the battery drain all the way and still it won't go.
Thanks
Click to expand...
Click to collapse
Does anyone have a dump of the aboot image? I could look for potential oem exploits and find a bypass that way. I refuse to believe there is no way to restore this phone.
double post
hellgod12 said:
Does anyone have a dump of the aboot image? I could look for potential oem exploits and find a bypass that way. I refuse to believe there is no way to restore this phone.
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Str0ntium said:
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Click to expand...
Click to collapse
Hi, I do not see an aboot.img anywhere. All I see is stock images. I have no way to load them and extract the aboot. I just need an aboot.img file. Any ideas?
They are zip files....
Str0ntium said:
They are zip files....
Click to expand...
Click to collapse
Yes I know that, where is aboot.img? its not inside the stock images.
hellgod12 said:
Yes I know that, where is aboot.img? its not inside the stock images.
Click to expand...
Click to collapse
I used the 8.1 July dump and it contained two copies of the boot.img.
Str0ntium said:
I used the 8.1 July dump and it contained two copies of the boot.img.
Click to expand...
Click to collapse
thats is not aboot.img though. That is different. No where in the boot img can I find the fastboot/oem commands.
The Application Bootloader ABOOT.img boots the Android kernel/Recovery kernel.
The Primary Bootloader boot.img part is a computer program that loads the main operating system or runtime environment after completion of the self-tests.
The PBL acts as a communication engine to download the Secondary Boot Loader (SBL) into the internal RAM and then activates it.
The SBL adds functions for erase and programming of flash memory and EEPROM; it also handles the actual download of new or updated software. This allows a minimum ROM utilization by the PBL
From what I understand the only way to get aboot.img is from a working device. But I do not have one, so was hoping someone had it.
hellgod12 said:
thats is not aboot.img though. That is different. No where in the boot img can I find the fastboot/oem commands.
Click to expand...
Click to collapse
Sorry thought that was a typo. You're looking for the recovery partition img I guess. Maybe someone else can help. I'm at work ?
Str0ntium said:
Sorry thought that was a typo. You're looking for the recovery partition img I guess. Maybe someone else can help. I'm at work
Click to expand...
Click to collapse
Yes exactly, is it possible for you to dump it after work? I know it is asking a lot but would really help me in trying to get this phone working. There has to be a way and I refuse to give up.
Thanks