Related
Due to my sensors being completely gone in 5.1 on my Nexus 4, I decided to flash the new 5.1.1 image. Did a backup in CWM (which is now lost, CWM recovery wipe/reset removes its own backups pffft ), flashed the factory image except userdata.img ... and boot loop. Did a backup of everything (CWM), repeated, still the boot loop. Tried CWM reset (which is supposed to leave backups), no joy. Tried restoring backup, GONE. Sigh. (Should've adb pulled /sdcard/ , I know. )
Okay, so flashed everything again incl. userdata.img. Still boot loop.
Flashed 4.4.4 on it and performed stock recovery reset. No joy. LOcked bootloader, then unlocked again, JOY. Booted up into 4.4.4, and lo and friggin' behold, sensors are all there.
So flashed 5.1.1 factory image completely (bootloader, radio, recovery, boot, cache, system, userdata images). And again the infinite boot animation. Tried locking and then unlocking bootloader. no joy.
Each time I'm giving the phone 5 minutes of the animation to continue to setup, more than enough.
The flash-all.bat file hasn't worked in the past (missing sig file warnings),[1] so I'm unpacking image-occam-lmy47v.zip and fastboot flashing each partition by hand.
[1] This time it's working, so ... patience wins.
sending 'bootloader' (2264 KB)...
OKAY [ 0.078s]
writing 'bootloader'...
OKAY [ 0.312s]
finished. total time: 0.391s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 2.781s]
writing 'radio'...
OKAY [ 2.375s]
finished. total time: 5.188s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.062s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 14129561600
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3449600
Block groups: 106
Reserved block group size: 847
Created filesystem with 11/863264 inodes and 95427/3449600 blocks
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
--------------------------------------------
Bootloader Version...: MAKOZ30f
Baseband Version.....: M9615A-CEFWMAZM-2.0.1701.07
Serial Number........: 018ce19f988a6159
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.000s]
checking version-baseband...
OKAY [ 0.000s]
sending 'boot' (6398 KB)...
OKAY [ 4.125s]
writing 'boot'...
OKAY [ 0.328s]
sending 'recovery' (6960 KB)...
OKAY [ 1.281s]
writing 'recovery'...
OKAY [ 0.375s]
erasing 'system'...
OKAY [ 0.812s]
sending 'system' (834754 KB)...
OKAY [ 39.891s]
writing 'system'...
Click to expand...
Click to collapse
Anyone else encountering problems with the 5.1.1 factory image?
ChromeJob said:
Due to my sensors being completely gone in 5.1 on my Nexus 4, I decided to flash the new 5.1.1 image. Did a backup in CWM (which is now lost, CWM recovery wipe/reset removes its own backups pffft ), flashed the factory image except userdata.img ... and boot loop. Did a backup of everything (CWM), repeated, still the boot loop. Tried CWM reset (which is supposed to leave backups), no joy. Tried restoring backup, GONE. Sigh. (Should've adb pulled /sdcard/ , I know. )
Okay, so flashed everything again incl. userdata.img. Still boot loop.
Flashed 4.4.4 on it and performed stock recovery reset. No joy. LOcked bootloader, then unlocked again, JOY. Booted up into 4.4.4, and lo and friggin' behold, sensors are all there.
So flashed 5.1.1 factory image completely (bootloader, radio, recovery, boot, cache, system, userdata images). And again the infinite boot animation. Tried locking and then unlocking bootloader. no joy.
Each time I'm giving the phone 5 minutes of the animation to continue to setup, more than enough.
The flash-all.bat file hasn't worked in the past (missing sig file warnings),[1] so I'm unpacking image-occam-lmy47v.zip and fastboot flashing each partition by hand.
[1] This time it's working, so ... patience wins.
Anyone else encountering problems with the 5.1.1 factory image?
Click to expand...
Click to collapse
5 minutes? Takes at least 10 min to boot from flashing images on 5.0+. You likely are not looping, it just takes a very long time. You will see the screen dim at one point, and that signals like the last 25% or so of your wait, but if you do not see any errors, you are 99.99% likely just not waiting long enough.
Actually, my first flash of the 5.1.1 image files failed. Not sure if it was fastboot crashing on my laptop, or the fact my hyper kids were able to momentarily disconnect the USB while flashing, but I got an error sending system the first time.
ariesgodofwar said:
5 minutes? Takes at least 10 min to boot from flashing images on 5.0+. You likely are not looping, it just takes a very long time. You will see the screen dim at one point, and that signals like the last 25% or so of your wait, but if you do not see any errors, you are 99.99% likely just not waiting long enough.
Actually, my first flash of the 5.1.1 image files failed. Not sure if it was fastboot crashing on my laptop, or the fact my hyper kids were able to momentarily disconnect the USB while flashing, but I got an error sending system the first time.
Click to expand...
Click to collapse
Thanks, seems I have to go through this at least once a year ... not taking time to copy my CWM backup (adb pull /sdcard/ . ), etc. Not waiting for flash-all.bat to finish. Yada yada yada. I know that I'd set the N4 booting for more than 10 minutes (taking a shower and getting dressed, doing my 1-1/2 mile run -- 15 minutes -- etc).
Successfully installed and configured 4.4.4 again (good to clean out a system a bit. Will try again now that I've got a backup in hand, on a USB drive. Thanks for the feedback.
Having made and stored a successful backup, have been trying the 5.1 and 5.1.1 factory image install scripts with and without the -w userdata switch ... in all cases, the phone stays in a boot animation loop for longer than 15 minutes.
Is this Google's passive aggressive way of telling us the N4 is no longer supported? I.e. issue a broken factory image and leave us to stew in our juices?
I tried further tests last night and this morning with pure, straight factory image scripts, and the 5.1, 5.1.1 image just won't boot up on a Nexus 4. Pffft. I really wanted to see if the sensor problems were from an upgrade I did, or if it's a clear fault on a new vanilla install of stock 5.1.x. But it never worked. (I think I was running 5.0.1 until yesterday.)
This is infuriating.
Back to 4.4.4 because ... I need my phone, darn it!
I have the same problem. i tried everything, its now looping for a hour...
Maybe you might give installing 4.4.4 stock a try, and then upgrading via the OTAs instead of the images? The 5.1.1 images are not broken as I was able to flash without issue, so I am not thinking it is a problem with the images themselves.
If you are sure you are waiting long enough, I do know the was an issue with the 4.4.4->5.0 flash from the images where you literally had to flash and if you just left it, the dots would spin endlessly. This was remedied by then rebooting to bootloader, wiping the cache partition from bootloader, and rebooting. It would then boot just fine. It was just the N4 I found this to be the case on. I am pretty sure Wug even made an allowance for it in the NRT code (2.0.3 I think). Are you using 2.0.5 NRT to flash the images? If not, you might give it a try.
Adding- Are you trying to go from 4.4.4 to 5.1.1 directly? I can't recall if there were changes, but you might try flashing the 5.0 images from 4.4.4, and then going up to 5.1.1 just in case there is some issue with the version leap which is causing your issue.
Yes i tried have formated the partition and everything. I just go take a step backwards, i am currently installing 5.0.1, if thats not working i gonna flash 4.4.4. I wil give a update if i succeeded.
joostburg said:
Yes i tried have formated the partition and everything. I just go take a step backwards, i am currently installing 5.0.1, if thats not working i gonna flash 4.4.4. I wil give a update if i succeeded.
Click to expand...
Click to collapse
Just to be clear, when in bootloop, try rebooting to bootloader (hold Volume- and power) to get the android laying down with his chest open, and then I think it is hold Vol+ and tap pwr that will get you to the menu you are looking for.
Go in and just wipe the cache partition and reboot. Do not reformat it or anything. Just wipe cache, reboot, and then give it 10-15 minutes.
Still nothing works, damn tried now everything. How long should i see the 4 dots spinning approximately? 15, 30 or 60 minutes? Normally i just see it for about 5 minutes with a fresh installation.
edit: now its optimizing my apps, hope i am finally there now.
"The idea is simple. After you dirty flash the required images (boot, system and radio), install a custom recovery (CWM or TWRP) and clear "cache" AND "dalvik-cache". Bootloop avoided.You might think it's enough to just clear the cache. It's not. Trust me, I've tested this extensively." http://www.reddit.com/r/nexus4/comments/36r8s2/how_to_avoid_a_bootloop_when_flashing_the_511_or/
joostburg said:
Still nothing works, damn tried now everything. How long should i see the 4 dots spinning approximately? 15, 30 or 60 minutes? Normally i just see it for about 5 minutes with a fresh installation.
edit: now its optimizing my apps, hope i am finally there now.
"The idea is simple. After you dirty flash the required images (boot, system and radio), install a custom recovery (CWM or TWRP) and clear "cache" AND "dalvik-cache". Bootloop avoided.You might think it's enough to just clear the cache. It's not. Trust me, I've tested this extensively." http://www.reddit.com/r/nexus4/comments/36r8s2/how_to_avoid_a_bootloop_when_flashing_the_511_or/
Click to expand...
Click to collapse
I told you it takes an ungodly amount of time. I have more than a few times almost pulled the plug too early thinking it was taking too long.
Afters apps are optimized, i get a starting apps screen or something like that. After 8 hours its still showing that screen, pffff.
Edit: When i try to wipe data or internal storage i get:
e:Unable to mount /data
e:Unable to mount usb-otg
ariesgodofwar said:
Just to be clear, when in bootloop, try rebooting to bootloader (hold Volume- and power) to get the android laying down with his chest open, and then I think it is hold Vol+ and tap pwr that will get you to the menu you are looking for.
Go in and just wipe the cache partition and reboot. Do not reformat it or anything. Just wipe cache, reboot, and then give it 10-15 minutes.
Click to expand...
Click to collapse
Let's be clear about how to wipe cache, you can't do it in the bootloader.
Power off
Hold Power and VOL DOWN => bootloader
VOL to select Recovery
Power to enter Recovery.
In stock Recovery "fallen Android" icon, hold POWER and VOL UP => Recovery menu
Now use vol and power buttons to select Wipe cache partition.
My final attempt after doing factory reset/wipe data in stock recovery, using the factory image flash-all.bat and NOT removing the -w switch (so /userdata/ is overwritten as well), the N4 didn't boot after waiting > 30 minutes.
INteresting about clearing cache and Dalvik cache during factory flash ... Dalvik cache should be irrelevant with ART being default in Lollipop....
ChromeJob said:
Let's be clear about how to wipe cache, you can't do it in the bootloader.
Power off
Hold Power and VOL DOWN => bootloader
VOL to select Recovery
Power to enter Recovery.
In stock Recovery "fallen Android" icon, hold POWER and VOL UP => Recovery menu
Now use vol and power buttons to select Wipe cache partition.
My final attempt after doing factory reset/wipe data in stock recovery, using the factory image flash-all.bat and NOT removing the -w switch (so /userdata/ is overwritten as well), the N4 didn't boot after waiting > 30 minutes.
Click to expand...
Click to collapse
I did exact the some for the fifth time and after an hour still 4 dancing dots. OMG gonna throw my phone trough a wall! BTW if i wipe the dalvik cache the phone will boot then get a infinite loop after optimizing apps with android is starting apps.
Same. Tried the instructions on that reddit article, posted this:
... I cleared the cache with stock recovery, no joy. Powered off, flashed CWM recovery, cleared cache and Dalvik-cache with CWM, then reflashed stock recovery, then rebooted, endless "starting apps."
Now that I know this, I'm flashing 5.0.1 with existing apps, will either wait a day for OTA, or try flashing the factory image again over 5.0.1 with the caches clearing. Maybe some app is causing the problem. I know I was able to flash 5.0.1 previously over 4.4.4....
I just don't get how the 5.1.1 image is working for some people. It seems that as Android progresses, there are more and more little undocumented tricks and gimmicks that we have to use to update a factory image without wiping data....
And my kitchen In-Sink-Erator just bit the dust, so I've got that to deal with as well. (sigh)
I give up... Hope someone can post the solution. I gonna borrow a other phone, this is not gonna work.
Oh, I got caught up in several things ... 5.0.1 didn't work, though I previously installed it OVER 4.4.4. Pffft.
Frankly, I think 4.4.4 was a fine OS version running on the N4. ART, Material Design, etc....
5 has its enhancements, but I can't live without my sensors working properly.[1] They've got some bug fixin' to do....
[1] I didn't even know 5.1 or 5.1.1 was out, I was troubleshooting the sensors being gone in 5.0.1, searched online for similar reports, saw the new OTA announcements.
So ChromeJob and joostburg, were you guys at least able to manually flash back to 4.4.4?
Also, ChromeJob, on my post, you commented:
For your problem, download the factory image, then edit flash-all.bat/sh and remove the -w from the last flash command (-w rewrites /userdata partition). Whether you use 5.0.1 or 4.4.4 is up to you.
Click to expand...
Click to collapse
May you please explain this a little?
No i tried but the 4 dots won't disappear. I am phone less for more than 48 hours now lol, and all the stores are closed till Tuesday, fml.
About the -w flag, when you download the stock roms from google you have a file flash-all.bat, when you edit this file with notepad you will see -w, that stand for wiping your device (remove all data), when you remove the -w (backspace, backspace) save the file and execute your data will NOT be removed.
By the way, when i try to clear my sd card in custom recovery i get: e:mount -o bind '/data/media/0' '/sdcard' proces ended with error=255, is this the cause?
hmmzz, i did a last try with 4.4.4, did first factory reset and then a cache wipe and it booted again, finally.
After updates around 5.1.* my phone started playing up and was taking longer and longer to boot, eventually getting stuck with the four coloured dots swirling around.
Time to root the phone which I duly achieved with chainfires CF-Auto-Root via fastboot (since the phone wouldn't boot up/start). I then installed TWRP and sideloaded via adb the Cataclysm ROM (both the last Lollipop and the new Marshmallow versions), performing a full factory reset first, then for good measure making sure to wipe cache and dalvik cache again (should have wiped during factory reset).
All looks good, but on booting after optimizing the applications it hangs on "Cataclysm is installing... Starting apps" and will not progress any further. I left it five hours and no progress. Powered off and rebooted and back to where I started, hangs with the four coloured dots swirling around. This was with the Lollipop version of Cataclysm so I decided to give Marshmallow a go, same result, currently stuck on "Starting apps" now for 40 minutes.
Wiping cache and dalvik cache again just results in the the applications needing to be optomised each time.
Any thoughts, advice, suggested ROMs, kernels, tricks to try or ideas on how to recover the phone would be very much appreciated.
Thanks in advance,
enilkcals
Wipe from TWRP and Install just the Rom but do not install GAPPS. There may be problem with your GAPPS package. If the ROM boots perfectly, download and install different GAPPS package.
NEXUSg4 said:
Wipe from TWRP and Install just the Rom but do not install GAPPS. There may be problem with your GAPPS package. If the ROM boots perfectly, download and install different GAPPS package.
Click to expand...
Click to collapse
Cataclysm includes Gapps so I've had a go at flashing MinimalOS (5.1.1) which doesn't (after wiping Cache, Data and Dalvik Cache of course). Still hangs on boot animation and I left it half an hour just to make sure.
Tried with XenonHD without Gapps and it too just hangs at the boot animation.
Pretty stumped now as to whats going on or how to solve it.
Try flashing a factory image. That should return it to complete stock.
This guide tells you how: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
You should download the image from here though since the one in the guide is outdated. https://developers.google.com/android/nexus/images
theminikiller said:
Try flashing a factory image. That should return it to complete stock.
This guide tells you how: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
You should download the image from here though since the one in the guide is outdated. https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I'll give it a go, but it was on stock when the problem first arose and wiping cache/dalvik/data didn't help.
I'm slightly confused as to which to download though. There are only "occam" for Nexus 4 listed, so I guess its one of those (likely 5.1.1 (LMY48T) as its the most recent). But for the other ROMs I've been installing they've all been for "mako" and when I boot into Fastboot the display reads...
Code:
FASTBOOT MODE
PRODUCT_NAME - mako
VARIANT - mako 8GB
HW VERSION - rev_10
BOOTLOADER VERSION - MAKOz30f
BASEBAND VERSION - M9615A-CEFWMAZM-2.0.1701.07
CARRIER INFO - None
SERIAL NUMBER - 002fff0a560d4e29
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
Wary of flashing the wrong ROM and screwing up the bootloader, as the instructions you linked (and on the image page itself) suggest the bootloader will be flashed and if I get that wrong there seems a high chance it will brick the phone.
How do I go about reconciling the device I have with the images available?
Occam is the right one. There is just several names for the device for some reason.
theminikiller said:
Occam is the right one. There is just several names for the device for some reason.
Click to expand...
Click to collapse
Thanks for the confirmation/sanity check.
Code:
# fastboot devices -l
002fff0a560d4e29 fastboot usb:2-2
occam-lmy48t # fastboot flash bootloader bootloader-mako-makoz30f.img
sending 'bootloader' (2264 KB)...
OKAY [ 0.080s]
writing 'bootloader'...
OKAY [ 0.332s]
finished. total time: 0.413s
occam-lmy48t # fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.050s
occam-lmy48t # fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.07.img
sending 'radio' (45537 KB)...
OKAY [ 1.445s]
writing 'radio'...
OKAY [ 2.540s]
finished. total time: 3.986s
occam-lmy48t # fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.050s
occam-lmy48t # fastboot -w update image-occam-lmy48t.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 6189744128
Block size: 4096
Blocks per group: 32768
Inodes per group: 8048
Inode size: 256
Journal blocks: 23612
Label:
Blocks: 1511168
Block groups: 47
Reserved block group size: 375
Created filesystem with 11/378256 inodes and 50366/1511168 blocks
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
--------------------------------------------
Bootloader Version...: MAKOZ30f
Baseband Version.....: M9615A-CEFWMAZM-2.0.1701.07
Serial Number........: 002fff0a560d4e29
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6448 KB)...
OKAY [ 0.211s]
writing 'boot'...
OKAY [ 0.337s]
sending 'recovery' (7008 KB)...
OKAY [ 0.237s]
writing 'recovery'...
OKAY [ 0.401s]
erasing 'system'...
OKAY [ 0.813s]
sending 'system' (834934 KB)...
OKAY [ 28.409s]
writing 'system'...
OKAY [ 47.296s]
erasing 'userdata'...
OKAY [ 1.400s]
sending 'userdata' (98413 KB)...
OKAY [ 3.401s]
writing 'userdata'...
OKAY [ 5.233s]
erasing 'cache'...
OKAY [ 0.056s]
sending 'cache' (10984 KB)...
OKAY [ 0.377s]
writing 'cache'...
OKAY [ 0.629s]
rebooting...
finished. total time: 88.871s
Rebooted and sitting on the booting screen with four coloured dots swirling around. Off to bed, will see if anything has happened tomorrow. Thanks again.
I think when this happened to be I had the wrong modem radio , I flash a new one appropriate for 5.1 and I was working after that.
Left it over night and still stuck on the boot animation.
Any more suggestions/ideas of things to try would be very welcome, but its looking like this phone has given up the ghost which is a bit of a shame as it would have made a nice backup.
Sadly, I don't have any other ideas.
In any case, good luck fixing it!
Thanks for your suggestions and help, appreciated.
cloneman1 said:
I think when this happened to be I had the wrong modem radio , I flash a new one appropriate for 5.1 and I was working after that.
Click to expand...
Click to collapse
Do you happen to have details of which modem radio you used? Not much for me to go on otherwise.
I've tried the official stock ROM from Google as theminikiller suggested and would expect that to have the correct modem radio included within it (which for 5.1.1 was the file radio-mako-m9615a-cefwmazm-2.0.1701.07.img that was bundled in with occam-lmy48t-factory-416938f1.tgz).
enilkcals said:
Thanks for your suggestions and help, appreciated.
Click to expand...
Click to collapse
hi i too had a similar issue.it was somewhat similar.my battery was dying.i tried installing stock rom.it never gotten past optimising apps screen.i tried some custom rom without gapps which booted fine. i used it a few days without gapps then the battery eventually died.it couldnt get past bootanimation.it can however stay in stock/twrp recovery.
so if you can try booting up the phone with a charger connected then the battery may be the issue. if it still didnt bootup go to a local service center ask them to open up nd remove battery and connect it directly to a power source in battery terminals.if the phone boots up fine you can order a new oem battery.[emoji3]
Sent from my Nexus 4 using Tapatalk
jaison thomas said:
hi i too had a similar issue.it was somewhat similar.my battery was dying.i tried installing stock rom.it never gotten past optimising apps screen.i tried some custom rom without gapps which booted fine. i used it a few days without gapps then the battery eventually died.it couldnt get past bootanimation.it can however stay in stock/twrp recovery.
so if you can try booting up the phone with a charger connected then the battery may be the issue. if it still didnt bootup go to a local service center ask them to open up nd remove battery and connect it directly to a power source in battery terminals.if the phone boots up fine you can order a new oem battery.[emoji3]
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Hi,
Thanks for the suggestion, I have already tried booting with the charger plugged in (both USB from cable and a micro-USB charger from the mains).
I sent the phone back to LG last year and had the battery replaced under warranty then (just checked and last email communication was 2014-10-22) having bought the phone 2013-08-17. I guess since thats about a year its not unreasonable to think the battery could be worn out again. Not sure whether LG will replace under warranty and wary of throwing cash down the drain, but might see if can find one and replace it.
Thanks for the idea.
slackline
Hi,
Had a very similar thing happen to me. Turned out the radio was dying - something basic about loading firmware to it during very early hardware boot up.
Figured this out after a long process - and solution was to keep on soft rebooting it until the firmware loaded successfully - then Android booted ok - otherwise it would hang at starting apps.
James
enilkcals said:
Hi,
Thanks for the suggestion, I have already tried booting with the charger plugged in (both USB from cable and a micro-USB charger from the mains).
I sent the phone back to LG last year and had the battery replaced under warranty then (just checked and last email communication was 2014-10-22) having bought the phone 2013-08-17. I guess since thats about a year its not unreasonable to think the battery could be worn out again. Not sure whether LG will replace under warranty and wary of throwing cash down the drain, but might see if can find one and replace it.
Thanks for the idea.
slackline
Click to expand...
Click to collapse
**PLEASE NOTE THE MOTO E3 BOOTLOADER IS UNLOCKED BY DEFAULT**
I JUST BROUGHT THIS PHONE THE OTHER DAY WITH A FEW OF MY FRIENDS AND MOST OF YOU AINT GOT A CLUE WHAT UR DOING LOL...... HERE IS A SIMPLE QUICK GUIDE TO SWAG UP UR E3...#
GET MY AIO PACKAGE drive.google (DOT) com/open?id=0B2jNSSNkWwEJY1Y1V2pNRDd0WWs
[SORRY CANT POST LINKS YET... (DOT) = .
Preparation:- Go To Settings -> About Phone -> Tap On “Build Number” 7 Times To Enable Developer Options.. Enable USB Debugging. .Go To Your Settings -> Developer Options -> Tick The “Usb Debugging” Checkbox. Enable OEM Unlock. Go To Your Settings -> Developer Options -> Tick The“Oem Unlock” Check boX. **BACK UP DATA**
STEP 1: INSTALL MotorolaDeviceManager_2.5.4.EXE
STEP 2: INSTALL Mtk_Usb_1.01.EXE
STEP 3: POWER OFF DEVICE
STEP 4: HOLO POWER + VOL UP TOGETHER THEN USE VOL DOWN TO SELECT FASTBOOT MODE
STEP 5: IN EXTRACTED FOLDER HOLD LSHIFT AND RIGHT CLICK > OPEN CMD HERE
STEP 6: USE COMMAND > fastboot format userdata
STEP 7: USE COMMAND > fastboot flash recovery TWRP_3.0.2.2-moto_E3_power.img
STEP 8: USE COMMAND > fastboot reboot
STEP 9: HOLD POWER + VOL UP TOGETHER THEN USE VOL DOWN TO SELECT RECOVERY MODE.
STEP 10: USE TWRP TO INSTALL THESE FILES > SR1-SuperSU-v2.79-SR1-20161221223537.ZIP / xposed-v87-sdk23-arm.ZIP / no-verity-opt-encrypt-3.2.ZIP / ultimate_performance_v8_b1.ZIP
STEP 11: AFTER REBOOT AND LONG LOAD YOU SHOULD BE ALL READY TO PWN IT [INSTALL XposedInstaller_3.1.1.apk]
I APOLOGISE IF I HAVENT POSTED THIS CORRECTLY OR IN THE RIGHT FORMAT AS THIS IS MY FIRST XDA GUIDE
HOPEFULLY YOU FIND IT USEFUL
IF YOU GET STUCK ADD ME ON WA 447856538891
Hello ! Im searching some devs that can help me to port the stock rom of the moto e3 for the wiko rainbow up 4g device, can you help me ?
No sorry i can't personally im new here but im sure if u post in the q&a section the guys will help u they are all epic
iv been trying this all evening, rooted plenty of phones before. but i cant even get it to erase user data (not support on security)?
fastboot says "unlock_ability=0."
fastboot oem unlock - "operation not allowed"
fastboot oem get_unlock_data - "remote:unknown command"
moto e3 xt1700
have tried different drivers & fastboot exe (mfastboot) all to no avail.
any ideas?
limbo7 said:
iv been trying this all evening, rooted plenty of phones before. but i cant even get it to erase user data (not support on security)?
fastboot says "unlock_ability=0."
fastboot oem unlock - "operation not allowed"
fastboot oem get_unlock_data - "remote:unknown command"
moto e3 xt1700
have tried different drivers & fastboot exe (mfastboot) all to no avail.
any ideas?
Click to expand...
Click to collapse
Have you enabled "Allow OEM unlock" in developer settings?
Yes, have enabled allow OEM unlock. Have been able to enable fastboot via ABD.
Command, Fastboot Devices - "Fastboot"
So I know it's communicating properly between phone & PC.
Will try it with Windows 7 as could be a driver issue?
Also using the dialpad to enter a system code to check if bootloader is locked doesn't work either.
Big thanks, although I found it wouldn't boot with that version of SuperSU UNLESS you installed the other three at the same time.. Very strange.
Works fine with just SR3-SuperSU-v2.79-SR3-20170114223742 though. Thanks again, this should be sticky. Any custom ROMs yet?
question?
Does this same method work for Moto e3 power?
Bloody phone!
limbo7 said:
iv been trying this all evening, rooted plenty of phones before. but i cant even get it to erase user data (not support on security)?
fastboot says "unlock_ability=0."
fastboot oem unlock - "operation not allowed"
fastboot oem get_unlock_data - "remote:unknown command"
moto e3 xt1700
have tried different drivers & fastboot exe (mfastboot) all to no avail.
any ideas?
Click to expand...
Click to collapse
bubba1601 said:
Have you enabled "Allow OEM unlock" in developer settings?
Click to expand...
Click to collapse
Hi guys,
I'm getting similar problems to limbo7 when trying to unlock, format userdata, etc
fastboot oem unlock returns the output below:
C:\Users\Ceriain\Desktop\moto>fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
fastboot format userdata returns:
C:\Users\Ceriain\Desktop\moto>fastboot format userdata
Creating filesystem with parameters:
Size: 838860800
Block size: 4096
Blocks per group: 32768
Inodes per group: 7328
Inode size: 256
Journal blocks: 3200
Label:
Blocks: 204800
Block groups: 7
Reserved block group size: 55
Created filesystem with 11/51296 inodes and 6651/204800 blocks
target reported max download size of 134217728 bytes
erasing 'userdata'...
FAILED (remote: format for partition 'userdata' is not allowed
)
All drivers are installed (wife and kids have Moto phones - rooted by me), USB Debugging on, OEM unlocking is enabled,. Like limbo7, I've rooted dozens of phones over the years (all makes), but have never come acroos this before. Usually, this takes me all of 5 minutes; this has got me totally flumoxed.
System version is: 23.0.XT1700_S303_160829_UK
Build number: XT1700_S303_160829_UK
Happy to listen to any ideas. bubba1601, like you, this is a Tesco UK phone; got any input?
Ceriain said:
Hi guys,
I'm getting similar problems to limbo7 when trying to unlock, format userdata, etc
fastboot oem unlock returns the output below:
C:\Users\Ceriain\Desktop\moto>fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
fastboot format userdata returns:
C:\Users\Ceriain\Desktop\moto>fastboot format userdata
Creating filesystem with parameters:
Size: 838860800
Block size: 4096
Blocks per group: 32768
Inodes per group: 7328
Inode size: 256
Journal blocks: 3200
Label:
Blocks: 204800
Block groups: 7
Reserved block group size: 55
Created filesystem with 11/51296 inodes and 6651/204800 blocks
target reported max download size of 134217728 bytes
erasing 'userdata'...
FAILED (remote: format for partition 'userdata' is not allowed
)
All drivers are installed (wife and kids have Moto phones - rooted by me), USB Debugging on, OEM unlocking is enabled,. Like limbo7, I've rooted dozens of phones over the years (all makes), but have never come acroos this before. Usually, this takes me all of 5 minutes; this has got me totally flumoxed.
System version is: 23.0.XT1700_S303_160829_UK
Build number: XT1700_S303_160829_UK
Happy to listen to any ideas. bubba1601, like you, this is a Tesco UK phone; got any input?
Click to expand...
Click to collapse
Yeah, this happened to me several times.
Like you, I'm a rooting and flashing master, i did my Moto e2 as soon as i unboxed it!
But the E3 is a different thing altogether, it's such a stupid thing and seems to do what it likes, hence why I've now given it to my wife (lol) and jumped ship to another manufacturer and just had an update from 6.0 to 7.0 on my new device!!
Anyway, sorry for off topic but but this is how i did it.
Turn off E3.
Turn back on, go back to settings make sure "allow OEM unlock" is ticked.
Also check usb debugging is turned on, it can turn off at times.
As tedious as it sounds, changing usb cable and then switching off and on E3 cured it!!!
Plug in phone to pc, make sure pc makes connection noise (sometimes it don't)
Open command prompt IN THE FOLDER on your pc where the fastboot/adb folders are located (it won't work if you don't follow this step)
Type ADB devices
Should get a message back like GSV 1456 or something similar.
Type ADB reboot bootloader
Device should now reboot into bootloader ( black screen with TINY while words)
Use vol + to move to fastboot, press vol - to confirm.
Then type fastboot devices (you should see some letters and numbers like before)
Fastboot OEM unlock
You should get a warning in white letters that you must press vol up to confirm.
Fastboot OEM unlock......
Then
Fastboot format userdata.
Then fastboot reboot.
Done.
bubba1601 said:
Yeah, this happened to me several times.
Like you, I'm a rooting and flashing master, i did my Moto e2 as soon as i unboxed it!
But the E3 is a different thing altogether, it's such a stupid thing and seems to do what it likes, hence why I've now given it to my wife (lol) and jumped ship to another manufacturer and just had an update from 6.0 to 7.0 on my new device!!
Anyway, sorry for off topic but but this is how i did it.
Turn off E3.
Turn back on, go back to settings make sure "allow OEM unlock" is ticked.
Also check usb debugging is turned on, it can turn off at times.
As tedious as it sounds, changing usb cable and then switching off and on E3 cured it!!!
Plug in phone to pc, make sure pc makes connection noise (sometimes it don't)
Open command prompt IN THE FOLDER on your pc where the fastboot/adb folders are located (it won't work if you don't follow this step)
Type ADB devices
Should get a message back like GSV 1456 or something similar.
Type ADB reboot bootloader
Device should now reboot into bootloader ( black screen with TINY while words)
Use vol + to move to fastboot, press vol - to confirm.
Then type fastboot devices (you should see some letters and numbers like before)
Fastboot OEM unlock
You should get a warning in white letters that you must press vol up to confirm.
Fastboot OEM unlock......
Then
Fastboot format userdata.
Then fastboot reboot.
Done.
Click to expand...
Click to collapse
Thanks for the reply, mate but...
Nope! Doesn't work! Wierdest thing I ever saw!
Got given an old Moto G the other day to give to my autistic son (he breaks phones easily) and unlocked it, then rooted it in less than 5 minutes. This piece of ****, on the other hand, I can't do a thing with.
Edit: I've now tried this on 4 PCs, using God knows how many USB cables... Nada!
Anyone else got any ideas? Must be some way to root this!.
Come on, XDA geniuses, I need you!
working oem unlock
i did this today and it worked moto e3 xt1700:
unlock oem in dev. settings
into fastboot mode
fastboot flashing unlock_critical
fastboot oem unlock
vol up
fastboot format userdata
fastboot flash recovery TWRP_3.0.2.2-moto_E3_power.img
battery out then back in power + vol up
select recovery vol down
i used LOVE'S package it worked a treat =)
TheLastAlphaUK said:
i did this today and it worked moto e3 xt1700:
unlock oem in dev. settings
into fastboot mode
fastboot flashing unlock_critical
fastboot oem unlock
vol up
fastboot format userdata
fastboot flash recovery TWRP_3.0.2.2-moto_E3_power.img
battery out then back in power + vol up
select recovery vol down
i used LOVE'S package it worked a treat =)
Click to expand...
Click to collapse
What firmware was that on? Thanks.
Only thing I see different from the posts above is "fastboot flashing unlock_critical".
After installing twrp i went into to recovery mode and my internal storage is 0 my rom is gone? Tried doing factory reset but it cant mount partition so my internal storage is totally clean. If i find a rom for E3 can i just flash it and it would be fine again? How could this happen!?! And i cant find any stock Moto E3 rom can i use E3 power roms?
DOes this support E3 Power 3gen?
---------- Post added at 11:22 AM ---------- Previous post was at 10:47 AM ----------
My bootloader is unlocked had no problem last time i did this. Same computer with drivers and all. Getting this when flashing recovery.
target reported max download size of 134217728 bytes
sending 'recovery' (13734 KB)...
OKAY [ 1.371s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 1.377s
---------- Post added at 11:40 AM ---------- Previous post was at 11:22 AM ----------
wackyleaks said:
**FIXED** After installing twrp i went into to recovery mode and my internal storage is 0 my rom is gone? Tried doing factory reset but it cant mount partition so my internal storage is totally clean. If i find a rom for E3 can i just flash it and it would be fine again? How could this happen!?! And i cant find any stock Moto E3 rom can i use E3 power roms?
Click to expand...
Click to collapse
After using flash tool for mkt chips. I was gonna install twrp again and the same thing happens.....
E:Unabel to find partition size for ' /custom'
Could not mount /data and unabel to find crypto
footer.
Failed to mount ' /data' (Invalid argument)
...Done
I had to mount system and when i try to mount Data it won't let mount it.
This morning my phone (with a recent lineage nightly) was off when I got up and when I tried to turn it on it said my password was wrong, which I am positive it was not. For some reason I decided to "solve" the problem by going into TWRP and wiping/formating everything (including system) and then installing a fresh copy of lineage, and flashing the bootloader and vendor. Once I did that it started bootlooping, I could get into bootloader but not recovery. After some playing with it I found that the 4 cores modified twrp would work, so I tried installing some roms from there with no luck. Then tried flashing a variety of factory images, none of which work, including the 48C 7.12 image with the 4 cores boot image, as well as the same with the ex4.12 kernel flashed over it.
Is there anything I can do, or is it just time to shop for a new phone?
Dacull said:
This morning my phone (with a recent lineage nightly) was off when I got up and when I tried to turn it on it said my password was wrong, which I am positive it was not. For some reason I decided to "solve" the problem by going into TWRP and wiping/formating everything (including system) and then installing a fresh copy of lineage, and flashing the bootloader and vendor. Once I did that it started bootlooping, I could get into bootloader but not recovery. After some playing with it I found that the 4 cores modified twrp would work, so I tried installing some roms from there with no luck. Then tried flashing a variety of factory images, none of which work, including the 48C 7.12 image with the 4 cores boot image, as well as the same with the ex4.12 kernel flashed over it. Is there anything I can do, or is it just time to shop for a new phone?
Click to expand...
Click to collapse
Have you tried the workaround of disabling big cores with EX Kernel? There is an XDA thread dedicated to it. From your post I'm not sure if you disabled the cores or not.
v12xke said:
Have you tried the workaround of disabling big cores with EX Kernel? There is an XDA thread dedicated to it. From your post I'm not sure if you disabled the cores or not.
Click to expand...
Click to collapse
I didn't, I thought it has already been done. But now even the 4 core twrp just gives me a splash screen followed by a momentary page of text and then crash.
Edit: Nevermind, I misunderstood you. I installed the EX kernel from this thread.
I also just managed to somehow override whatever was crashing twrp by pushing the power button right when the text screen was showing. Flashed the EX kernel again, but still not working. I'm thinking the problem is something more than/other than the regular bootloop issue, but it is odd that only the 4 cores twrp will work.
Did you flash boot?
ItsMason said:
Did you flash boot?
Click to expand...
Click to collapse
In the most recent effort I flashed the entire n2g48c factory image but substituted the 4 cores boot image and 4 cores twrp recovery, then once I managed to get into twrp I installed the EX kernel from the thread listed above. Now, after that, it will bootloop once and then try to boot twrp which still crashes after showing the splash screen.
Dacull said:
In the most recent effort I flashed the entire n2g48c factory image but substituted the 4 cores boot image and 4 cores twrp recovery, then once I managed to get into twrp I installed the EX kernel from the thread listed above. Now, after that, it will bootloop once and then try to boot twrp which still crashes after showing the splash screen.
Click to expand...
Click to collapse
Try to fastboot FORMAT Boot, System and Userdata to see if they will format without errors. You may have a hardware issue (eg. bad eMMC). If so, the formatting process will not complete and give you a specific error code. If these 3 all complete, then flash a full image using flash-all.bat.
v12xke said:
Try to fastboot FORMAT Boot, System and Userdata to see if they will format without errors. You may have a hardware issue (eg. bad eMMC). If so, the formatting process will not complete and give you a specific error code. If these 3 all complete, then flash a full image using flash-all.bat.
Click to expand...
Click to collapse
This is what I got, I'm guessing the response on "boot" might be related to the problem?
Code:
[[email protected] angler-n2g48c]$ sudo fastboot format boot
[sudo] password for cullen:
Formatting is not supported for file system with type ''.
[[email protected] angler-n2g48c]$ sudo fastboot format system
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
Creating filesystem with parameters:
Size: 3221225472
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 12288
Label:
Blocks: 786432
Block groups: 24
Reserved block group size: 191
Created filesystem with 11/196608 inodes and 25785/786432 blocks
target reported max download size of 494927872 bytes
erasing 'system'...
OKAY [ 0.557s]
sending 'system' (52216 KB)...
OKAY [ 1.941s]
writing 'system'...
OKAY [ 0.732s]
finished. total time: 3.231s
[[email protected] angler-n2g48c]$ sudo fastboot format userdata
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
Creating filesystem with parameters:
Size: 58688266240
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14328190
Block groups: 438
Reserved block group size: 1024
Created filesystem with 11/3588096 inodes and 271280/14328190 blocks
target reported max download size of 494927872 bytes
erasing 'userdata'...
OKAY [ 0.640s]
sending 'userdata' (141002 KB)...
OKAY [ 5.181s]
writing 'userdata'...
OKAY [ 2.109s]
finished. total time: 7.930s
Dacull said:
This is what I got, I'm guessing the response on "boot" might be related to the problem?
Click to expand...
Click to collapse
Something is up with boot. Have you tried manually flashing just the Boot.img? Sorry I meant format System, Cache & Userdata. Did you then flash a full image with flash-all.bat? Was there any error on the Cache partition? If you still can't successfully enter Recovery, you could try to fastboot boot TWRP it rather than fastboot flashing. If you can access a stable Recovery you then have ADB and can sideload, etc.
v12xke said:
Something is up with boot. Have you tried manually flashing just the Boot.img? Sorry I meant format System, Cache & Userdata. Did you then flash a full image with flash-all.bat? Was there any error on the Cache partition? If you still can't successfully enter Recovery, you could try to fastboot boot TWRP it rather than fastboot flashing. If you can access a stable Recovery you then have ADB and can sideload, etc.
Click to expand...
Click to collapse
I cache formated ok. I have been flashing everything manually, including boot, since flash-all.sh ends on an error, but manually flashing seems to work fine.
Here's the output from flash-all.sh
Code:
[[email protected] angler-n2g48c]$ sudo ./flash-all.sh
target reported max download size of 494927872 bytes
sending 'bootloader' (3544 KB)...
OKAY [ 0.152s]
writing 'bootloader'...
OKAY [ 0.209s]
finished. total time: 0.361s
rebooting into bootloader...
OKAY [ 0.022s]
finished. total time: 0.072s
target reported max download size of 494927872 bytes
sending 'radio' (48728 KB)...
OKAY [ 1.862s]
writing 'radio'...
OKAY [ 2.164s]
finished. total time: 4.026s
rebooting into bootloader...
OKAY [ 0.022s]
finished. total time: 0.072s
target reported max download size of 494927872 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
W/ziparchive( 3437): Zip: unable to allocate 2860210996 bytes at offset 0 : No space left on device
failed to extract 'system.img': I/O Error
I was able to get a stable twrp using the 4 cores twrp and fastboot boot twrp, what would I want to sideload in this situation? The ota for the whatever version I just flashed?
Dacull said:
I cache formated ok. I have been flashing everything manually, including boot, since flash-all.sh ends on an error, but manually flashing seems to work fine.
I was able to get a stable twrp using the 4 cores twrp and fastboot boot twrp, what would I want to sideload in this situation? The ota for the whatever version I just flashed?
Click to expand...
Click to collapse
Have you updated fastboot/adb recently? I don't use the whole SDK, just the stand alone binaries. Some older versions weren't able to handle the multiple system packages.... but..... I/O error sounds like bad memory to me. The current versions were published 12-May-17. On the adb, I was just going to suggest flashing SU because it modifies boot and if it found something it wasn't expecting you may receive a better error message. Now sounding more like bad onboard memory. I don't think you have a valid system partition so maybe why it's not booting. Just a guess. Many ppl with BLOD have reported manually flashing completes with no error yet the OS won't boot.
Ok, I was running a slightly older version of fastboot, but I get the exact same results after switching to the latest binary, so it looks like the phones just toast. Huge thanks for all the help, even if it didnt end up working.
Hi so I want to revert back to factory image, however I keep on getting "file not found" or "target didn't report max-download-size" error. I already installed the drivers, unlock the bootloader and when I check fastboot devices, the phone shows up.
Any help would be greatly appreciated.
Ive had similar performance within the bootloader menu. Some things to check on your pc verify that the phone is showing up in device manager as essential phone fastboot. You may need to restart the pc or change usb port to get it to properly communicate.
You should also be able to revert to the factory image through the normal recovery; instead of attempting to install twrp to flash the stock image (sounds like what you might be trying to do your post is a little unclear) you can always just run the normal essential recovery partition and then use adb sideload from there to restore the factory image.
From essential's website
https://www.essential.com/developer/beta-builds
Your device is now in Recovery mode. An Android logo with red exclamation mark should appear on screen.
Hold the Power button, then press the Volume-Up button one time. When the menu appears, select Apply update from ADB.
Run the following command: adb devices. Then check that your device shows up with “sideload” next to its name
Run the following command: adb sideload ota_file.zip where ota_file.zip is the name of the file you downloaded and verified
Once the update finishes, select Reboot system now to reboot your phone
I tried this and it seems to work great but if I select slot b it will not boot properly. Has anyone else tried this?
I don't believe that the Essential bath file flashes both slots. I had to use the BTS file to fix my phone.
Halp
Zargone said:
I tried this and it seems to work great but if I select slot b it will not boot properly. Has anyone else tried this?
I don't believe that the Essential bath file flashes both slots. I had to use the BTS file to fix my phone.
Click to expand...
Click to collapse
Did you manage to successfully flash the stock image? If yes, would you kindly provide the steps that you performed? Im trying to get back to Oreo from Android P Beta so that I can have my unit replaced
I just got one of these phones as payment for some consulting. I booted into fastboot mode and checked fastboot devices before agreeing on the deal and I see the device listed. I get home and start to unlock bootloader etc...only to continue getting this error...
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.005s
This was a simple process on my Huawei. WHats going on here does anyone know?
lolifer said:
I just got one of these phones as payment for some consulting. I booted into fastboot mode and checked fastboot devices before agreeing on the deal and I see the device listed. I get home and start to unlock bootloader etc...only to continue getting this error...
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.005s
This was a simple process on my Huawei. WHats going on here does anyone know?
Click to expand...
Click to collapse
Have you enabled oem unlock in developer options?
I cannot boot into android to check. I literally got this phone a couple hours ago. Is there anyway to enable it via fastboot?
The guy that I got it from told me it was stuck on boot logo. I simply hooked it up to laptop, installed adb/fastboot, and drivers and booted to fastboot and ran fastboot devices which gave me the serial #. So i figured I would be able to restore it no matter as long as fastboot could see the device.
lolifer said:
I cannot boot into android to check. I literally got this phone a couple hours ago. Is there anyway to enable it via fastboot?
The guy that I got it from told me it was stuck on boot logo. I simply hooked it up to laptop, installed adb/fastboot, and drivers and booted to fastboot and ran fastboot devices which gave me the serial #. So i figured I would be able to restore it no matter as long as fastboot could see the device.
Click to expand...
Click to collapse
There is no way to unlock bootloader if you can't enable oem unlock option in developer menu.
You can try to boot to recovery and do a factory reset,or try switching slots a/b and see if you can boot ur phone.
gm007 said:
There is no way to unlock bootloader if you can't enable oem unlock option in developer menu.
You can try to boot to recovery and do a factory reset,or try switching slots a/b and see if you can boot ur phone.
Click to expand...
Click to collapse
i already did those options. each time FB fails to write because of locked state. I cannot access recovery. I tried to> fastboot boot boot.img and this is what I get:
platform-tools_r28.0.1-windows\platform-tools>fastboot boot boot.img
Downloading 'boot.img' OKAY [ 0.935s]
booting FAILED (remote: 'unknown command')
Finished. Total time: 0.962s
EDIT**** Just specified a USB device using fastboot -s. Looks like the partitions were created but just couldnt wipe userdata. What is SuperBlocks backup?
C:\Users\Leebo\Downloads\platform-tools_r28.0.1-windows\platform-tools>fastboot -s PM1LHMD762601033 -w
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 26768215 4k blocks and 6692864 inodes
Filesystem UUID: 672d99c8-c617-11e8-8c24-45c467b7c233
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Erasing 'userdata' FAILED (remote: 'Erase is not allowed in Lock State')
Finished. Total time: 1.068s
lolifer said:
i already did those options. each time FB fails to write because of locked state. I cannot access recovery. I tried to> fastboot boot boot.img and this is what I get:
platform-tools_r28.0.1-windows\platform-tools>fastboot boot boot.img
Downloading 'boot.img' OKAY [ 0.935s]
booting FAILED (remote: 'unknown command')
Finished. Total time: 0.962s
EDIT**** Just specified a USB device using fastboot -s. Looks like the partitions were created but just couldnt wipe userdata. What is SuperBlocks backup?
C:\Users\Leebo\Downloads\platform-tools_r28.0.1-windows\platform-tools>fastboot -s PM1LHMD762601033 -w
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 26768215 4k blocks and 6692864 inodes
Filesystem UUID: 672d99c8-c617-11e8-8c24-45c467b7c233
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Erasing 'userdata' FAILED (remote: 'Erase is not allowed in Lock State')
Finished. Total time: 1.068s
Click to expand...
Click to collapse
You will need to side load the OTA.
You cannot flash.
tech_head said:
You will need to side load the OTA.
You cannot flash.
Click to expand...
Click to collapse
But I cannot get adb to work, only fastboot. I install essentials ADB, download Essential drivers. Am I missing something? In Device Manager while in fastboot it says Essential Fastboot Phone.
Im starting to think the original owner must have had twrp and installed OTA update without going back to stock recovery. If I were to assume this the case, what would be the next step to recover?
tech_head said:
You will need to side load the OTA.
You cannot flash.
Click to expand...
Click to collapse
How do I go about sideloading from fastboot?
Don't know. My phone is rooted and bl unlocked
lolifer said:
How do I go about sideloading from fastboot?
Click to expand...
Click to collapse
Pretty sure you cannot sideload with fastboot. Anything flashing related in the bootloader with fastboot requires an unlocked bootloader. If twrp was previously installed than he would unlocked the bootloader at some point. What happens when you boot to recovery from the bootloader? Or the hardware buttons?
galakanokis said:
Pretty sure you cannot sideload with fastboot. Anything flashing related in the bootloader with fastboot requires an unlocked bootloader. If twrp was previously installed than he would unlocked the bootloader at some point. What happens when you boot to recovery from the bootloader? Or the hardware buttons?
Click to expand...
Click to collapse
when I boot into recovery the phone simply restarts and gets stuck on the boot screen "powered by Android" screen. What do you mean the hardware buttons? VOL UP+POwer?
lolifer said:
when I boot into recovery the phone simply restarts and gets stuck on the boot screen "powered by Android" screen. What do you mean the hardware buttons? VOL UP+POwer?
Click to expand...
Click to collapse
Yeah, was just curious about what you were seeing in recovery. If your bootloader is locked and you have somehow lost recovery I am not to sure what else you can do. You said you switched slots and still were unable to boot to recovery?
lolifer said:
when I boot into recovery the phone simply restarts and gets stuck on the boot screen "powered by Android" screen. What do you mean the hardware buttons? VOL UP+POwer?
Click to expand...
Click to collapse
Ok...
Let's try this thing...
Grab the fastboot images from the Essential website...
Download and unzip it...
Try flashing boot to it's partition...
Theory- signed by the OEM?
Once you can get to recovery... You can use ADB
rignfool said:
Ok...
Let's try this thing...
Grab the fastboot images from the Essential website...
Download and unzip it...
Try flashing boot to it's partition...
Theory- signed by the OEM?
Once you can get to recovery... You can use ADB
Click to expand...
Click to collapse
...downloading images for PIE now.
EDIT**Here is the fastboot result..
C:\Users\Administrator\Downloads\PH1-Images-PPR1.180610.091\PH1-Images-PPR1.180610.091>fastboot flash boot boot.img
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'boot_b' (20769 KB)...
OKAY [ 0.830s]
writing 'boot_b'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.845s
lolifer said:
...downloading images for PIE now.
EDIT**Here is the fastboot result..
C:\Users\Administrator\Downloads\PH1-Images-PPR1.180610.091\PH1-Images-PPR1.180610.091>fastboot flash boot boot.img
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'boot_b' (20769 KB)...
OKAY [ 0.830s]
writing 'boot_b'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.845s
Click to expand...
Click to collapse
Damn...
I woulda thought for sure you could flash signed image...
just fired up miraclebox and did a read info under the qualcomm section and this was my result.
Starting..
Waiting for Phone...
Phone Found..
version:0.5
unlocked:no
off-mode-charge:1
charger-screen-enabled:1
battery-soc-ok:yes
battery-voltage:3721
version-baseband:2.0.c4-M1.2
version-bootloader:mata-4452425
variant:
partition-type:userdata:ext4
partition-size:userdata: 0x1987357000
partition-type:system_b:ext4
partition-size:system_b: 0x100000000
has-slot:nvdef:yes
has-slot:dsp:yes
has-slot:vendor:yes
has-slot:devcfg:yes
has-slot:cmnlib64:yes
has-slot:cmnlib:yes
has-slot:boot:yes
has-slot:keymaster:yes
has-slot:abl:yes
has-slot:mdtp:yes
has-slot:mdtpsecapp:yes
has-slot:bluetooth:yes
has-slot:modem:yes
has-slotmic:yes
has-slot:hyp:yes
has-slot:tz:yes
has-slot:rpm:yes
has-slot:xbl:yes
has-slot:system:yes
current-slot:_b
slot-retry-count:_b:0
slot-unbootable:_b:no
slot-successful:_b:no
slot-retry-count:_a:0
slot-unbootable:_a:yes
slot-successful:_a:no
slot-count:2
slot-suffixes:_a,_b,
secure:yes
serialnoM1LHMD762601033
product:Mata
max-download-size:0x20000000
kernel:uefi
all:
0.011s
>>Process Done...