Related
As you probably all know, the Advanced Hack Kit (a.k.a Hack Kit) has been retired for good yesterday. Does that mean that you can not achive root privilege anymore? NO
NO, YOU DON'T NEED S-OFF TO FLASH ROMS....
Getting root acces
Unlock your bootloader with HTCDEV or using this tool: http://forum.xda-developers.com/showthread.php?t=2133336
Then flash CWM or 4ext recovery in fastboot per this guide: http://forum.xda-developers.com/showpost.php?p=30020025&postcount=7 and make a nand backup.
Then reboot into recovery and flash SU or SuperSU.
Reboot the device and voilá. You are done
IF YOUR BUILD VERSION IS NOT SUPPORTED TO UPDATE THEN:
Create a goldcard using this tool: http://forum.xda-developers.com/showthread.php?t=970157 (you need a working phone for this)
Find a RUU which main version is supported and higher than yours and flash it in the PD98IMG.zip way, that is what is the goldcard for.
Re run the tool and you will be able to update the hboot and unlock it
The other way to achive root access is to flash a custom rom after unlocking the bootloader.
As you can notice root access is easy to be gained but not S-OFF. If you are skilled in android and working with terminal or cmd commands, then you can use this: http://tau.shadowchild.nl/attn1/?p=411
Flashing roms with an unlocked bootloader
Unlock your bootloader and flash a custom recovery (CWM or 4ext)
Download the rom zip file you are willing to flash to your PC.
Extract the the boot.img from inside the zip file (do not extract the whole rom)
Put the zip file in your sdcard.
Boot into recovery and do a full wipe (wipe data/factory reset, wipe cache partition, format system)
Flash rom (install zip from sdcard)
Reboot into bootloader again and plug the phone to the PC.
You need to be in fastboot usb (if you see HBOOT USB PLUG in the phone, just press power to toggle)
Open a cmd/terminal and navigate to where the boot.img file is located.
Type: fastboot flash boot boot.img If you don´t how to do that, watch this video (it is in spanish, thou you can follow it without listening to the instructions)
Reboot and now you should be enjoying your custom rom
Rooting without the Ace kit!
Hi there
Is there a thread or some sort of a step by step manual on how to install ROM with unlocked boot loader (s on) without ace advance hacking kit or perhaps a working method where you can install CWM on a Gingerbread. (I have successfully unlocked the boot loader on htcdev)
Thanks a million
simopesh said:
Hi there
Is there a thread or some sort of a step by step manual on how to install ROM with unlocked boot loader (s on) without ace advance hacking kit or perhaps a working method where you can install CWM on a Gingerbread. (I have successfully unlocked the boot loader on htcdev)
Thanks a million
Click to expand...
Click to collapse
Check the guide in my signature, you will find the information you need in there. Don't forget to flash the boot.img of the custom rom in fastboot. Enjoy...
Not registering to mobile network!
Thanks Glevitan
I found the manual and all went smooth and easy. I have one problem though.
The phone does not register to any mobile network. Any idea how to bypass that? It was originally locked on Orange UK network.
Thanks again
glevitan said:
Check the guide in my signature, you will find the information you need in there. Don't forget to flash the boot.img of the custom rom in fastboot. Enjoy...
Click to expand...
Click to collapse
simopesh said:
Thanks Glevitan
I found the manual and all went smooth and easy. I have one problem though.
The phone does not register to any mobile network. Any idea how to bypass that? It was originally locked on Orange UK network.
Thanks again
Click to expand...
Click to collapse
That is weird. What ROM did You flash?
Phone locked on Orange UK!
glevitan said:
That is weird. What ROM did You flash?
Click to expand...
Click to collapse
CM-7.2.0-ace.zip and then I tried aospX-1.0.0-MR1-DHD.zip.
I flashed it many times these two ROM's after Ace Kit without any issues. Also I noticed that every time I restart the phone it requires the network unlocking code. It is weird!
the pdf file to flash a custom rom/recovery, i dont understand.. how exactly do i flash a custom rom?? for example codefirex??
Hello,
I try to unlock my bootloader with HTCDEV or by using that tool but have some problems.
At step 8 (HTCDEV) Type in Command Prompt: fastboot oem get_identifier_token
After that you should see a long block of text. But I only get this:
<bootloader> [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
what's going wrong? what can I do?
Albert-Jan said:
Hello,
I try to unlock my bootloader with HTCDEV or by using that tool but have some problems.
At step 8 (HTCDEV) Type in Command Prompt: fastboot oem get_identifier_token
After that you should see a long block of text. But I only get this:
<bootloader> [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
what's going wrong? what can I do?
Click to expand...
Click to collapse
or your build version does not supported or you didn't update your hboot....
Boot in fastboot usb and type:
Code:
fastboot getvar all
Then paste all that info in here (delete the imei)
glevitan said:
or your build version does not supported or you didn't update your hboot....
Boot in fastboot usb and type:
Code:
fastboot getvar all
Then paste all that info in here (delete the imei)
Click to expand...
Click to collapse
Microsoft Windows [versie 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle rechten voorbehouden.
C:\Users\Albert-Jan>cd \Android
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0027
(bootloader) version-baseband: 26.14.52.27
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 3.12.405.2
(bootloader) serialno: HT0AERX05199
(bootloader) imei:
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9810000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3847mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 743ca94a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.031s
Albert-Jan said:
Microsoft Windows [versie 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle rechten voorbehouden.
C:\Users\Albert-Jan>cd \Android
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0027
(bootloader) version-baseband: 26.14.52.27
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 3.12.405.2
(bootloader) serialno: HT0AERX05199
(bootloader) imei:
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9810000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3847mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 743ca94a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.031s
Click to expand...
Click to collapse
Your build nor your hboot version support unlocking the bootloader. You can try updating the hboot manually by flashing 0029 hboot. However that is a dangerous process. Otherwise, you can create a goldcard and flash a RUU with a Main version that supports the update.
glevitan said:
Your build nor your hboot version support unlocking the bootloader. You can try updating the hboot manually by flashing 0029 hboot. However that is a dangerous process. Otherwise, you can create a goldcard and flash a RUU with a Main version that supports the update.
Click to expand...
Click to collapse
I'm not a professional.
how can I create a goldcard and flash a RUU?
is there a step by step manual somewhere?
thanks
Excellent guide.
Albert-Jan said:
I'm not a professional.
how can I create a goldcard and flash a RUU?
is there a step by step manual somewhere?
thanks
Click to expand...
Click to collapse
I would try the hboot update. It should work...There is a guide I think in the development section, not sure thou.
Does this Sim unlock the device or only gives root ?
sizzlers said:
Does this Sim unlock the device or only gives root ?
Click to expand...
Click to collapse
Only root. No sim unlock.
cannot get CWM Recovery loaded on DHD GB
glevitan said:
As you probably all know, the Advanced Hack Kit (a.k.a Hack Kit) has been retired for good yesterday. Does that mean that you can not achive root privilege anymore? NO
Getting root acces
Unlock your bootloader with HTCDEV or using this tool: http://forum.xda-developers.com/showthread.php?t=2133336
Then flash CWM or 4ext recovery in fastboot per this guide: http://forum.xda-developers.com/showpost.php?p=30020025&postcount=7 and make a nand backup.
Then reboot into recovery and flash SU or SuperSU.
Reboot the device and voilá. You are done
The other way to achive root access is to flash a custom rom after unlocking the bootloader.
As you can notice root access is easy to be gained but not S-OFF. If you are skilled in android and working with terminal or cmd commands, then you can use this: http://tau.shadowchild.nl/attn1/?p=411
Click to expand...
Click to collapse
domasxxm said:
Yes!! I did it just had to flash boot img from zm7 zip fastboot flash boot boot.img
Click to expand...
Click to collapse
Phone: DHD, 3.20.502.52, ATT
I have successfully unlocked the phone (via HTCDev)
And have successfully rooted the phone.
I installed the ROM Manager and Titanium Backup.
I have the ADB drivers successfully installed on my computer.
I also have HTC Quick Root running on my computer.
I am NOT able to get the CWM Recovery installed on the phone. I always get a " /cache/recovery..." error.
I've searched and read a number of threads that have indicated the DHD Gingerbread is particularly difficult to get ROM Manager fully working. I tried the process outlined here (http://forum.xda-developers.com/showthread.php?p=39016279), using the easyunlock tool. the script appears to run fine, i've even gone through the redundant step of putting the unlockcode received from htcdev into the tools directory and allowing the script to complete, which it appears to do fine. However, the script indicates the phone should execute some commands as a final step, at which point my phone is already sitting in the bootloader menu and does nothing.
I'm reasonably comfortable with ADB commands and the terminal emulator on the phone.
Can anyone help me understand why I'm failing and what I might do to get the CWM Recovery installed and get ROM Manager working?
My end goal is to install a more battery efficient ROM.
smericle said:
Phone: DHD, 3.20.502.52, ATT
I have successfully unlocked the phone (via HTCDev)
And have successfully rooted the phone.
I installed the ROM Manager and Titanium Backup.
I have the ADB drivers successfully installed on my computer.
I also have HTC Quick Root running on my computer.
I am NOT able to get the CWM Recovery installed on the phone. I always get a " /cache/recovery..." error.
I've searched and read a number of threads that have indicated the DHD Gingerbread is particularly difficult to get ROM Manager fully working. I tried the process outlined here (http://forum.xda-developers.com/showthread.php?p=39016279), using the easyunlock tool. the script appears to run fine, i've even gone through the redundant step of putting the unlockcode received from htcdev into the tools directory and allowing the script to complete, which it appears to do fine. However, the script indicates the phone should execute some commands as a final step, at which point my phone is already sitting in the bootloader menu and does nothing.
I'm reasonably comfortable with ADB commands and the terminal emulator on the phone.
Can anyone help me understand why I'm failing and what I might do to get the CWM Recovery installed and get ROM Manager working?
My end goal is to install a more battery efficient ROM.
Click to expand...
Click to collapse
That stament is normal and it appears always in recovery. How come flashing a custom recovery is failing?
edit: nevermind i got cwm recovery flashed
is there any way to s-off for people not advanced in android?
rooternoober said:
edit: nevermind i got cwm recovery flashed
is there any way to s-off for people not advanced in android?
Click to expand...
Click to collapse
Unfortunately no.
I've been searching for hours here but can't find a solution that works...
My wife's Wi-Fi Nexus 7 (running stock, unrooted) suddenly got stuck in a boot loop during the white Google logo (never gets to the Nexus "X" animation). I figured I'd simply restore to stock through fastboot/adb.
The problem is when I try to unlock the bootloader (which is needed to be able to flash the factory image) I get this error message:
Code:
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
[COLOR="Red"][B]FAILED (remote: ()[/B][/COLOR]
finished. total time: 2.736s
Because of this, I can't go any further. I can't flash anything because it tells me I need to unlock the bootloader. I tried a couple of different toolkits with the same results.
I get fastboot access, and the device is listed when I type "fastboot devices" but I don't get adb access. When I type "adb devices" I simply see:
Code:
>adb devices
List of devices attached
...and nothing else. No devices listed. If I try other adb commands, I get "error: device not found".
I've tried installing the Google drivers as well as other USB drivers from toolkits. No change. But I can send it commands through fastboot fine.
{
"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"
}
I can get into recovery, but can't flash anything. I am able to factory reset from recovery, but it doesn't help. The tablet just keeps boot-looping.
Am I screwed? Any ideas? Thanks in advance to anyone who responds
I had to put mine in PTP mode to get it recognized. I also had a heck of of time getting the drivers installed correctly. I had to un-install and re-install several times before it worked correctly
bigdaddy619 said:
I had to put mine in PTP mode to get it recognized. I also had a heck of of time getting the drivers installed correctly. I had to un-install and re-install several times before it worked correctly
Click to expand...
Click to collapse
What's PTP mode? Were you having the same issue I'm having?
The thing is my tablet is getting recognized, at least in fastboot. Just not in adb but I'm thinking that's because it never had debugging turned on.
Wrong input.
grisoxxl said:
If you can acces recovery make full wipe.
Click to expand...
Click to collapse
Already did that several times. Doesn't help Still stuck in a boot loop and still can't unlock the bootloader to try to flash stock image.
ecaggiani said:
Already did that several times. Doesn't help Still stuck in a boot loop and still can't unlock the bootloader to try to flash stock image.
Click to expand...
Click to collapse
Why don't you flash the Google stock firmware?
Edit: i don't think unlock is necessary for flashing Google stock image
Sent from my Nexus 7 using xda premium
ganeshp said:
Why don't you flash the Google stock firmware?
Edit: i don't think unlock is necessary for flashing Google stock image
Click to expand...
Click to collapse
That's what I'm trying to do! The guides I've seen have me unlock the bootloader to be able to flash stock firmware. Can you point me to a guide? Is there an RUU maybe?
ecaggiani said:
Am I screwed?
Click to expand...
Click to collapse
Most likely. Is it still in Warranty? (The tab should be less than 1 year old)
The whole narrative smells like some kind of failure with the EMMC flash memory chip.
There's no point in fooling with adb. It only exists in the booted OS or a custom recovery, and you have neither.
Sorry... but you should probably be contacting Asus at this point.
bftb0 said:
Most likely. Is it still in Warranty? (The tab should be less than 1 year old)
The whole narrative smells like some kind of failure with the EMMC flash memory chip.
There's no point in fooling with adb. It only exists in the booted OS or a custom recovery, and you have neither.
Sorry... but you should probably be contacting Asus at this point.
Click to expand...
Click to collapse
Yeah I was afraid of that. Thanks for the response. I'll be contacting either Google or ASUS soon.
ecaggiani said:
Yeah I was afraid of that. Thanks for the response. I'll be contacting either Google or ASUS soon.
Click to expand...
Click to collapse
Hi, im having the exact problem you're having, did you end up contacting ASUS? how was your experience like? Did you get it resolved? I think I voided my warranty by trying to pull the battery ):
Hi all,
I've also got what seems to be a similar problem.
I've tried many (all?) the options to get this thing unlocked.
All I get is:
Code:
fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: 4.753s
or if I try a factory flash:
Code:
fastboot flash bootloader bootloader-tilapia-4.13.img
sending 'bootloader' (2096 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.013s
Also a "restart bootloader" from the recovery screen or
Code:
fastboot reboot-bootloader
takes me to a blank screen.
Holding the power button to reset the Nexus then the power + Vol Down takes me back to recovery with no change.
(I'm looking at this for a friend so not sure exactly what he did, but I doubt it was anything major!)
the machine vars are:
Code:
fastboot getvar all
(bootloader) version-bootloader: 4.13
(bootloader) version-baseband: N/A
(bootloader) version-hardware: ER3
(bootloader) version-cdma: N/A
(bootloader) variant: grouper
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) product: grouper
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: no
(bootloader) partition-size:bootloader:
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000c00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000028a00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001bb00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000700f00000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.161s
your help please?
regards
Ricey
Ricey_uk said:
Hi all,
I've also got what seems to be a similar problem.
I've tried many (all?) the options to get this thing unlocked.
All I get is:
Code:
fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: 4.753s
or if I try a factory flash:
Code:
fastboot flash bootloader bootloader-tilapia-4.13.img
sending 'bootloader' (2096 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.013s
Also a "restart bootloader" from the recovery screen or
Code:
fastboot reboot-bootloader
takes me to a blank screen.
Holding the power button to reset the Nexus then the power + Vol Down takes me back to recovery with no change.
(I'm looking at this for a friend so not sure exactly what he did, but I doubt it was anything major!)
the machine vars are:
Code:
fastboot getvar all
(bootloader) version-bootloader: 4.13
(bootloader) version-baseband: N/A
(bootloader) version-hardware: ER3
(bootloader) version-cdma: N/A
(bootloader) variant: grouper
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) product: grouper
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: no
(bootloader) partition-size:bootloader:
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000c00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000028a00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001bb00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000700f00000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.161s.
your help please?
regards
Ricey
Click to expand...
Click to collapse
Hi, Ricey_uk...
Mmm... not sure, but I think you're trying to flash the wrong factory image for your device...
Reason being, is because (QUOTE: fastboot flash bootloader bootloader-tilapia-4.13.img) 'tilapia' refers to the 3G/GSM variant of the Nexus 7.
But you appear to have a (QUOTE: (bootloader) product: grouper) 'grouper' device. Which is WiFi only... this seems to be supported by the two lines in your output...
(bootloader) version-baseband: N/A
(bootloader) version-cdma: N/A
... which suggests your N7 has no 'radio' capability.
You need the factory stock image for "nakasi" for Nexus 7 Wi-Fi only (device board "grouper").... NOT "nakasig" for Wi-Fi & Mobile (device board "tilapia").
(See my sig for download links).
-----------
In short, there is an incongruity/contradiction in your reported outputs.... the device is either 'grouper' or it's 'tilapia'
It can't be both.
If it has a SIM card (like a mobile phone), or a space for a SIM card, then it's 'tilapia'... if it doesn't, then it's 'grouper'.
Ensure you are flashing the correct factory stock for your device.
-----------
But having said all of that... (and if there is confusion, it needs to be cleared up)... it doesn't explain why something as straightforward and innocuous as...
Code:
fastboot oem unlock
...isn't working.
Two possibilities occur to me...
1) A bad USB connection. Try a different USB port on your PC... Or, maybe, a different USB cable.
Once the fastboot oem unlock command is issued at the PC end, it will need to be confirmed at the Nexus 7 end (see attached thumbnail). Use either of the two VOL buttons to choose YES and confirm by pressing the POWER button.
2) It's possible there could be a hardware failure... some problem with the EMMC flash memory chip. As alluded to by a previous poster...
bftb0 said:
Most likely. Is it still in Warranty? (The tab should be less than 1 year old)
The whole narrative smells like some kind of failure with the EMMC flash memory chip
There's no point in fooling with adb. It only exists in the booted OS or a custom recovery, and you have neither.
Sorry... but you should probably be contacting Asus at this point.
Click to expand...
Click to collapse
Whilst I don't discount the possibility that it COULD be EMMC chip failure, I'm not inclined to think that this is a likely possbility. More prosaic explanations need to be explored first.
First... check the integrity of of your USB connections - at both ends; change to different USB ports on your PC; if you can, try a different PC; try a different USB cable. And confirm at the Nexus 7 end, once the unlock command has been issued. (again, see attached thumbnail).
Second... if you are going to try to fastboot flash back to Android factory stock... make sure you do so with correct version for your device. If you're device is Wi-Fi only, you need the 'grouper' version... if not, the 'tilapia' version.
Hope this helps.... and good luck.
Rgrds,
Ged.
Hi Ged,
thanks for the info, I was wondering about the .img versions - but I can't seem to find the 'grouper' version of 4.13 anywhere. It's not on the factory downloads page (google)
As for the unlock, it does indeed come up with the screen as you showed, and pressing the power button for 'yes' says that it is unlocking. When it then reboots itself it just stays blank. A hard power cycle back to recovery states that it is still locked.
thought?
cheers
Ricey_uk said:
Hi Ged,
thanks for the info, I was wondering about the .img versions - but I can't seem to find the 'grouper' version of 4.13 anywhere. It's not on the factory downloads page (google)
As for the unlock, it does indeed come up with the screen as you showed, and pressing the power button for 'yes' says that it is unlocking. When it then reboots itself it just stays blank. A hard power cycle back to recovery states that it is still locked.
thought?
cheers
Click to expand...
Click to collapse
Hi, Ricey_uk...
Yeah... that, unfortunately, does not sound good at all. Unlocking the bootloader just sets some 'flag state' on the internal EMMC flash chip. Specifically, somewhere in the mmcblk0boot0 partition, where the bootloader lives.
There's some technical info here... http://forum.xda-developers.com/showthread.php?t=2068207
If fastboot oem unlock is performing as you describe, then it strongly suggests some sort of hardware failure. It just shouldn't behave that way... once you have confirmed the oem unlock request on the Nexus 7, the PC should display (if I remember correctly), the following...
Unlocking....
The device is unlocked now...
The whole procedure should take no more than a few seconds. Blank screens and forced reboots have happened many times on my Nexus 7... but never whilst unlocking the bootloader (and yes, I have locked and relocked several times, when I was experimenting with the 'motochopper' root exploit).
----------------------------------
Incidentally, you won't find 4.13 on the factory downloads page, as that number refers to the bootloader version for JellyBean 4.2 and 4.2.1. (It's not always the case that with each new version of JellyBean the bootloader is updated).
Anyway... looking through my collection of system images on my laptop, I find the following...
JellyBean 4.1.2 -> bootloader-grouper-3.41.img
JellyBean 4.2.0 -> bootloader-grouper-4.13.img
JellyBean 4.2.1 -> bootloader-grouper-4.13.img
JellyBean 4.2.2 -> bootloader-grouper-4.18.img
JellyBean 4.3.0 -> bootloader-grouper-4.23.img
With JellyBean 4.3 being the latest, and it updating the bootloader to 4.23.
If you're still stuck on bootloader version 4.13, then that means it was last updated with the rollout of JellyBean 4.2, sometime around November 2012.
----------------------------------
All of which is technically interesting... but probably doesn't help you.
I think there is a hardware problem on your Nexus 7, that is preventing the bootloader-lock-state flag from being correctly set.
Wish I could be of more assistance.
Rgrds,
Ged.
Thanks Ged,
great info - I was looking for the factory image for JB 4.2.0 to get the bootloader image out of, but that version of JB isn't on the factory page
my theory being if I re-flash the same version it might fix the bootloader?? But it being locked it would need the exact same version?
perhaps if you could mail me the .img file I could try it? I can pm you my address??
cheers!
Ricey_uk said:
Thanks Ged,
great info - I was looking for the factory image for JB 4.2.0 to get the bootloader image out of, but that version of JB isn't on the factory page
my theory being if I re-flash the same version it might fix the bootloader?? But it being locked it would need the exact same version?
perhaps if you could mail me the .img file I could try it? I can pm you my address??
cheers!
Click to expand...
Click to collapse
Give me half an hour or so, and I'll upload it to my dropbox and I'll post a link. Gotta get it of my laptop first.
Although I'm not convinced it will solve your problem... but I suppose you have nothing to loose by trying.
Rgrds,
Ged.
---------- Post added at 12:53 PM ---------- Previous post was at 12:21 PM ----------
OK... here is the bootloader .img file - v4.13... extracted from nakasi-jp40d-factory-6ac58a1a.tar... or in English, Jellybean 4.2.1.
https://dl.dropboxusercontent.com/u/37483979/bootloader-grouper-4.13.img
Code:
File size: 2.05 MiB (2,146,892 bytes)
MD5: a119629c89ad06c7e49bebd260df9cf3
SHA-1: fd60a0d9da5c814e2c1ee049f537700cbbe2c3cc
Flash as follows....
Code:
fastboot flash bootloader bootloader-grouper-4.13.img
---------------
Be careful with this.
Flashing a bootloader is the riskiest single operation you can undertake on the Nexus 7.
All it takes is one false step, and you have a hardbrick.
The device will never boot again.
Make sure you have good USB connections at both ends... and before flashing... type...
Code:
fastboot devices
If you don't see a serial number, you have either a driver problem OR a possible dodgy USB connection.
Do not proceed with this flash until you see a serial number.
Normally, I would suggest test flashing something innocuous first, like a recovery, for example.... but since your bootloader is locked, that's not possible.
I'm not even sure flashing a bootloader is possible with a locked bootloader... but then, I've never directly flashed a bootloader before.
Very best of luck - really hope this fixes your problem.
Rgrds,
Ged.
Many thanks Ged,
tried it to no avail - still getting the 'Bootloader is locked'
It won't even re-flash the existing
I checked all the cables and used a different USB port.
thanks for your help
Ricey
Ricey_uk said:
Many thanks Ged,
tried it to no avail - still getting the 'Bootloader is locked'
It won't even re-flash the existing
I checked all the cables and used a different USB port.
thanks for your help
Ricey
Click to expand...
Click to collapse
Damn... thought that might happen... but wasn't 100% sure.
You can't use fastboot with a locked bootloader, even to flash a bootloader... and you can't unlock it because - well, who the hell knows why (but I suspect a problem with the internal EMMC).
What is the precise current status of your Nexus 7?
Android version?
Rooted?
Stock or Custom ROM/kernel?
Custom recovery (CWM/TWRP) installed?
Did you receive any OTA notifications regarding the recent release of Android 4.3? and if so did you allow the OTA update to proceed? What happened?
Rgrds,
Ged.
I know! I'm stuck in a loop!
I don't know the exact Android version, but it's fairly new and the owner hasn't updated it as far as I know.
Apart from that, completely stock and unrooted!
The last thing to happen was that it was left for a while to go flat (battery) then when re-started it got stuck at the Google logo and no further.
All I can get apart from the Google logo is the recovery with the andoid on his back with his tummy open
cheers
Ricey_uk said:
I know! I'm stuck in a loop!
I don't know the exact Android version, but it's fairly new and the owner hasn't updated it as far as I know.
Apart from that, completely stock and unrooted!
The last thing to happen was that it was left for a while to go flat (battery) then when re-started it got stuck at the Google logo and no further.
All I can get apart from the Google logo is the recovery with the andoid on his back with his tummy open
cheers
Click to expand...
Click to collapse
You can get the Android version info by going to SETTINGS>>ABOUT TABLET.
Without further details, what is odd about your predicament is this...
If your bootloader is v4.13, then that means the device hasn't been updated since November of last year. Since then, there have been, I think, 3 official updates from Google... the most recent being JellyBean 4.3 about a couple of weeks ago
Normally, when an OTA update is pending, you get pestered endlessly with an endless stream of notifications.
Upon the user accepting the lastest update (whatever that might be - but is currently JellyBean 4.3)... the device downloads the OTA, runs a checksum test on the current files in /system... and then'patches' them, meaning it brings them up to date.
The very last thing the OTA does is update the bootloader, by dropping BOOTLOADER.RAW into the USP(staging) partition. Upon automatic reboot, the new bootloader is then copied (from the USP/staging partition) into the bootloader partition proper... thus obviating the risks associated with flashing the bootloader partition directly.
Since November, the bootloader has been updated by this means twice... 4.13->4.18 (in, I think February, when JellyBean 4.22 was rolled out) and just recently 4.18->4.23 when JellyBean 4.3 was rolled out.
It's odd you haven't received any notifications of any OTA updates.
----------------------------------
Anyway.... A possible workaround...
A slightly rhetorical question... why do you want to unlock the bootloader anyway?
I assume it's because you want to root... or maybe flash a custom ROM...
That 'might' still be possible...if you're running a version of Android THAT ISN'T JellyBean 4.3, you can root via 'exploit'.
Details here - http://forum.xda-developers.com/showthread.php?t=2233852
This requires no fastboot commands and thus, no need for an unlocked bootloader.
It's really simple to implement. Indeed, I ran my Nexus 7 for several month BOOTLOADER locked, but rooted.
(But with the advent of JellyBean 4.3, root exploits no longer work.... so I've had to root the old fashioned way).
But it might be useful to you...
Anyway... once you are rooted, you can then flash a Custom Recovery... like CWM or TWRP.
Normally this would be done via fastboot. But there are two great apps available that will 'write' a recovery partition... directly from the Nexus 7.
These are Flash Image GUI and Flashify.
Both will request root access.
It doesn't matter which one you use, as they essentially do the same job... but IMHO, Flashify is the better of the two.
Once you have a Custom Recovery installed, the metaphorical gateway is open to whatever Custom ROMs or Custom Kernels you like.
----------------------------------
It's possible none of the above will work... maybe for the same reason why you can't unlock the bootloader. A suspected fault with the internal EMMC chip.
But it just might... and it's gotta be worth a shot.
To summarize
Root via 'exploit'
Use Flashify or Flash Image GUI to install a Custom Recovery
Good luck.
Rgrds,
Ged.
Ahh, hind sight is a wonderful thing.
After trying to use kingroot to get root access, it failed. And a few days later after rebooting.
I'm now stuck at bootup with Start Up Failed.
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
I've now tried lot's of different things, over the last few hours.
RSDLite (show device brings no thing up)
Unlock bootloader (request key, but error regarding OEM unlock not being set - no access to now set it LOL)
Downloaded stock X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip, and tried using various guides on fastboot but keep getting remote failed.
I'm on stock recovery (obviously still locked).
Any thoughts, or hope from anyone?
Obviously, not sure what support Motorola would provide for what is essentially my own fault?
Have you tried manually flashing each bit of the stock firmware/image. That might help. There's a good guide here which I followed to unbrick my device. Just follow the instructions http://theunlockr.com/2015/09/22/how-to-unroot-the-motorola-moto-x-play/
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
sharebubbles said:
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
Click to expand...
Click to collapse
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
DTLblaze said:
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
Click to expand...
Click to collapse
I run the unlock command, with my unique key but I get ..
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.013s
And since I can't get into the phone, I can't therefore check the "allow OEM unclock"
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
DTLblaze said:
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
Click to expand...
Click to collapse
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Sickaxis79 said:
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Click to expand...
Click to collapse
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
sharebubbles said:
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Click to expand...
Click to collapse
That really does sound like you bricked the device. If you where on lollipop software you wouldn't have the issue with check bootloader OEM unlock. If it was me I would either contact Motorola or go to a repair shop and have a motd experienced person take a look at it.
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
sharebubbles said:
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
Click to expand...
Click to collapse
Strange. This is the tool I used to unlock my bootloader.
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
I've ben used the latest rom so far why trying to flash (and failing) when I look at recovery I have a LPD23.118-10 number that matches to an earlier 5.1.1 rom (I had been upgraded to 6.0.1 via OTA updates) - do I therefore take that LPD ID to mean that I should actually use the 5.1.1 rom - I'm in the UK, so I'm assuming I'd use the UK one rather than Europe (I'm looking at roms on https://github.com/motoxplay/stock).
Thanks
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
And also never try kingroot.
sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
Most in the threads suggesting using rsdlite or manual flash/root and you decided to use kingroot,haha.
Welcome back.
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
---------- Post added at 05:26 AM ---------- Previous post was at 05:14 AM ----------
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
Tried restoring it, deleted everything and the phone is still on bootloader (LOCKED) and i dont even know how to fix it, I know nothing on how to root, friend suggested it, downloaded it, installed it, didnt work and then i restarted my phone and now its stuck on bootloader screen and the screen has the message "Start up failed: your device didnt start up successfully. Use the software repair assisstant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant." <- Downloaded it, tried it and it was stuck on 6% on repairing, left it over night and it was still on 6%.
ALSO under the message "AP Fastboot Flash Mode(Secure) is there)
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
pravin kkr said:
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
Click to expand...
Click to collapse
Download and flash this firmware
https://mega.nz/#!H5YlDCrD!T8tAAW7nHVS-erizRiqg5-Yp_p23hKParMjjHD4diQA credits @kumeipark
Use RSD lite to flash the firmware
http://rsdlite.com/rsd-lite-download/
Moto drivers
http://motorola-mobility-en-in.custhelp.com/app/answers/detail/a_id/88481
If you have problems installing device drivers using Windows 8.1 or Windows 10 follow this guide
https://www.youtube.com/watch?v=gmw86KplqmU
And don't post your contact no. in public forums for everyone to see.
what is the decryption key for the mega link
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
provide the decryption key
Hi guys, first time posting.
I have now a moto g4 plus that was OTA updated from Android 6.x to Android 7.0 and that caused it to bootloop and die later. Before that I had no knowledge of ROMs, bootloaders, fastboot, flashing, sideloads, ADB, RSD or anything like that. But this last week I acquired a superficial knowledge thanks to google, foruns of all kinds and you guys from XDA.
My phone started doing nothing at all and I progressed, solving the not charging battery problem (disconnecting and reconnecting it), the not lighting up led (with the original turbo charger and a three minute hold of the vol - and power up buttons) and finally accessing the fastboot mode and later the recovery mode which allowed me to dive into all kinds of tutorials about the reasons that I could not use ADB (usb debugging disabled) or flash custom ROMs (unlocked bootloader and unchecked "allow oem unlock"). All the research ended up to the conclusion that the only thing I could do was to flash the stock rom of Android 7.0 through RSD or fastboot/mfastboot. Did that, wiped cache and users data/factory reset and... nothing. The phone installed the stock ROM but it still doesn't pass the Motorola logo screen.
After that I came to three possible solutions:
1) Try to install the brasilian ROM version I have in my sister's Moto G4 plus (NPJS 25.93-14.4), but I can't find it anywhere (thought about backing it up from her phone, but root would be needed and her phone is still in warranty).
2) To wait till Android 7.1.1 or 7.1.2 stock ROM be released for Moto g4 plus flash it and hope it do the trick.
3) Send to Motorola assistance so they change it's motherboard (last resource considering the phone is not in warranty anymore).
Well, as I said my knowledge is new and superficial so I need your help and opinion about my conclusions and other possible solutions.
I thank you all for all I've learned so far and for any tips you can spare on me. Thanks again and keep doing what you do here.
Kyrohn said:
Hi guys, first time posting.
I have now a moto g4 plus that was OTA updated from Android 6.x to Android 7.0 and that caused it to bootloop and die later. Before that I had no knowledge of ROMs, bootloaders, fastboot, flashing, sideloads, ADB, RSD or anything like that. But this last week I acquired a superficial knowledge thanks to google, foruns of all kinds and you guys from XDA.
My phone started doing nothing at all and I progressed, solving the not charging battery problem (disconnecting and reconnecting it), the not lighting up led (with the original turbo charger and a three minute hold of the vol - and power up buttons) and finally accessing the fastboot mode and later the recovery mode which allowed me to dive into all kinds of tutorials about the reasons that I could not use ADB (usb debugging disabled) or flash custom ROMs (unlocked bootloader and unchecked "allow oem unlock"). All the research ended up to the conclusion that the only thing I could do was to flash the stock rom of Android 7.0 through RSD or fastboot/mfastboot. Did that, wiped cache and users data/factory reset and... nothing. The phone installed the stock ROM but it still doesn't pass the Motorola logo screen.
After that I came to three possible solutions:
1) Try to install the brasilian ROM version I have in my sister's Moto G4 plus (NPJS 25.93-14.4), but I can't find it anywhere (thought about backing it up from her phone, but root would be needed and her phone is still in warranty).
2) To wait till Android 7.1.1 or 7.1.2 stock ROM be released for Moto g4 plus flash it and hope it do the trick.
3) Send to Motorola assistance so they change it's motherboard (last resource considering the phone is not in warranty anymore).
Well, as I said my knowledge is new and superficial so I need your help and opinion about my conclusions and other possible solutions.
I thank you all for all I've learned so far and for any tips you can spare on me. Thanks again and keep doing what you do here.
Click to expand...
Click to collapse
Hello Kyrohn, before I go into any specific idea on what you should do have you ever tried considering flashing Lineage OS onto your device?
if your phone has charge i would suggest you to do the following
1. make sure it's switched off, drain the charge and then recharge if you can't be sure if it's switched off or not.
2. install your drivers properly.
3. then connect your device(in switched off condition) via usb cable while simultaneously holding power button and volume down button only.
4. the phone should enter into a black area and from there reboot to bootloader.
5. follow this link properly
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
this should do it. cuz it should always boot to recovery/bootloader from moto screen
HIT LIKE IF IT HELPED
justinwgeiger said:
Hello Kyrohn, before I go into any specific idea on what you should do have you ever tried considering flashing Lineage OS onto your device?
Click to expand...
Click to collapse
Hi Justin, thanks for reply. Lineage OS is a custom ROM, right? So the stock bootloader won't allow me to flash this ROM considering my bootloader is locked and the OEM unlock option is unchecked (and inaccessible).
Have you tried flashing stock marshmallow?
Kyrohn said:
Hi Justin, thanks for reply. Lineage OS is a custom ROM, right? So the stock bootloader won't allow me to flash this ROM considering my bootloader is locked and the OEM unlock option is unchecked (and inaccessible).
Click to expand...
Click to collapse
Okay I understand, I will guide you through the process of unlocking your bootloader then.
Requirements:
A computer and a usb cord,
Moto G4/G4 Plus,
ADB/Fastboot Drivers: https://www.androidfilehost.com/?fid=745425885120698566,
Moto G4/G4 Plus Drivers: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481,
Once you have installed the Minimal ADB and Fastboot tool, launch the tool from the desktop icon named Minimal ADB and Fastboot. You should be brought to a command window.
Now power down your phone and hold the volume down and power button at the same time. you should see a screen pop up. then press the volume down button until you see bootloader and leave it there.
Now at the command window, type:
Code:
fastboot oem get_unlock_data
It should return with something like this:
Code:
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
After that, go to paste it all into notepad (A Windows application) and delete the bootloader text and all other spaces so it looks like this:
Code:
0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
Go to Motorola’s bootloader unlock site and login with Google. Paste the entire code from notepad into the input box there. Then click can my device be unlocked and agree to the terms.
You will then be sent an email to unlock your bootloader.
Put the key that they send you into notepad and put it in the command line like shown below:
Code:
fastboot oem unlock "YOURKEY" (Replace YOURKEY with the key you received)
It will unlock your device. Congratulation you have successfully unlocked your device.
Credits:
devs-lab
If you have any questions or concerns just ask me and I will try my best to help you out. From this point forward you should be able to find your way throughout the forums to install a custom recovery. If not just ask me and I will guide you through that too. Glad to help, .
MisterSteve said:
Have you tried flashing stock marshmallow?
Click to expand...
Click to collapse
Hi Steve, yes I tried, but I can't downgrade the system, the stock bootloader doesn't allow me
justinwgeiger said:
Okay I understand, I will guide you through the process of unlocking your bootloader then.
Requirements:
A computer and a usb cord,
Moto G4/G4 Plus,
ADB/Fastboot Drivers: https://www.androidfilehost.com/?fid=745425885120698566,
Moto G4/G4 Plus Drivers: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481,
Once you have installed the Minimal ADB and Fastboot tool, launch the tool from the desktop icon named Minimal ADB and Fastboot. You should be brought to a command window.
Now power down your phone and hold the volume down and power button at the same time. you should see a screen pop up. then press the volume down button until you see bootloader and leave it there.
Now at the command window, type:
Code:
fastboot oem get_unlock_data
It should return with something like this:
Code:
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
After that, go to paste it all into notepad (A Windows application) and delete the bootloader text and all other spaces so it looks like this:
Code:
0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
Go to Motorola’s bootloader unlock site and login with Google. Paste the entire code from notepad into the input box there. Then click can my device be unlocked and agree to the terms.
You will then be sent an email to unlock your bootloader.
Put the key that they send you into notepad and put it in the command line like shown below:
Code:
fastboot oem unlock "YOURKEY" (Replace YOURKEY with the key you received)
It will unlock your device. Congratulation you have successfully unlocked your device.
Credits:
devs-lab
If you have any questions or concerns just ask me and I will try my best to help you out. From this point forward you should be able to find your way throughout the forums to install a custom recovery. If not just ask me and I will guide you through that too. Glad to help, .
Click to expand...
Click to collapse
Thanks for the reply and patience again Justin. But as I said before the option "Allow OEM Unlock" in Android Settings > Developer Options is unchecked. So when I try unlock the bootloader with the commands you passed I get the following error: Check 'Allow OEM Unlock' in Android Settings > Developer Options. But I can't do that considering the phone doens't boot Android.
Ayan Uchiha Choudhury said:
if your phone has charge i would suggest you to do the following
1. make sure it's switched off, drain the charge and then recharge if you can't be sure if it's switched off or not.
2. install your drivers properly.
3. then connect your device(in switched off condition) via usb cable while simultaneously holding power button and volume down button only.
4. the phone should enter into a black area and from there reboot to bootloader.
5. follow this link properly
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
this should do it. cuz it should always boot to recovery/bootloader from moto screen
HIT LIKE IF IT HELPED
Click to expand...
Click to collapse
Hi Ayan, thanks for reply. Tried all of that before, but tried again now just in case I had made something wrong the first time. It does everything as it's supposed to do, but after reboot it still doesn't pass the logo screen
Kyrohn said:
Hi Steve, yes I tried, but I can't downgrade the system, the stock bootloader doesn't allow me
Click to expand...
Click to collapse
You should no use the bootloader and gpt commands as the bootloader is not downgraded once it has been updated.leave those two and try to fastboot stock marshmallow.
[email protected] said:
You should no use the bootloader and gpt commands as the bootloader is not downgraded once it has been updated.leave those two and try to fastboot stock marshmallow.
Click to expand...
Click to collapse
Hi Chaitu. I tried that now but I'm getting an "invalid PIV signed" error. Could you check the commands I'm using?
mfastboot oem fb_mode_set
mfastboot flash logo logo.bin
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Maybe I'm using one I shouldn't. The first error appears on this command line "mfastboot flash oem oem.img" and the error is "Invalid PIV signed oem image". I also tried the next line "mfastboot flash system system.img_sparsechunk.0" and the error is "Invalid PIV signed system image". Isn't that an error when we use an incorrect ROM for a region? I'm trying the asian ROM cause I couldn't found a brasilian one.
Just tried to flash a supposed brasilian retailed marshmallow ROM, but got the same PIV error. Any ideas about the reason why?
Kyrohn said:
Just tried to flash a supposed brasilian retailed marshmallow ROM, but got the same PIV error. Any ideas about the reason why?
Click to expand...
Click to collapse
Could redownload your ROM to double-check it's not corrupted. Also, is your device carrier unlocked or provided by a carrier? I've had a quick look on that error and in a few cases may be due to a carrier restriction.
However, in order to downgrade, you need an unlocked bootloader which isn't achievable as you've mentioned. And the fast boot won't work either...
When did you buy your device? I recall reading on the Motorola website the warranty is 12 months in Brasil, unless you've been told different? (Edit:https://help.motorola.com/hc/apps/settings/legal/global/pt-br/index.html?t=T1700272834 unless this is out of date)
echo92 said:
Could redownload your ROM to double-check it's not corrupted. Also, is your device carrier unlocked or provided by a carrier? I've had a quick look on that error and in a few cases may be due to a carrier restriction.
However, in order to downgrade, you need an unlocked bootloader which isn't achievable as you've mentioned. And the fast boot won't work either...
When did you buy your device? I recall reading on the Motorola website the warranty is 12 months in Brasil, unless you've been told different? (Edit:https://help.motorola.com/hc/apps/settings/legal/global/pt-br/index.html?t=T1700272834 unless this is out of date)
Click to expand...
Click to collapse
Hi Echo, thanks for reply. I'm almost sure the phone isn't locked by carrier, but can't assure that. Your're right about the warranty but I didn't buy the phone new, it's a used phone and due to Motorola legal contract the warranty is intransferable. And even if wasn't I asked for the bootloader unlock code in one of the tutorials, so I lost the warranty cause of that too.
About this "PIV", what does it mean? How can I find out the required PIV for my phone, do you have any ideia about that?
Thanks again.
Kyrohn said:
Hi Echo, thanks for reply. I'm almost sure the phone isn't locked by carrier, but can't assure that. Your're right about the warranty but I didn't buy the phone new, it's a used phone and due to Motorola legal contract the warranty is intransferable. And even if wasn't I asked for the bootloader unlock code in one of the tutorials, so I lost the warranty cause of that too.
About this "PIV", what does it mean? How can I find out the required PIV for my phone, do you have any ideia about that?
Thanks again.
Click to expand...
Click to collapse
Ah okay, so we've got no warranty/Motorola will charge for repairs, gotcha (and is probably looking like a motherboard repair )
As for PIV - I've read that is read by the bootloader to verify if your image is signed properly (i.e. by Motorola) and thus if it's not the right signature will fail to flash. Short of obtaining the correct, signed, image for your device (what is your device btw?), I'm not sure if you'll be able to bypass that. You may wish to have a look here, see if there are any images for your device (though I cannot say if they'll flash properly). https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/
The strange thing is that flashing the stock Nougat ROM as you mentioned (and Ayan suggested) should have worked (since the NPJ25.93-14 build seems to be a global, universal build), the only thing I can think of was that something happened with the Marshmallow build on there (either a bad flash or an incorrect ROM, for example), but without asking the former owner, we just don't know.
For information, are you able to reboot into the bootloader, attach your device to your computer and in minimal ADB, execute 'fastboot getvar all' and post the info here, please? You may wish to remove your IMEI and serial number from the output.
echo92 said:
Ah okay, so we've got no warranty/Motorola will charge for repairs, gotcha (and is probably looking like a motherboard repair )
As for PIV - I've read that is read by the bootloader to verify if your image is signed properly (i.e. by Motorola) and thus if it's not the right signature will fail to flash. Short of obtaining the correct, signed, image for your device (what is your device btw?), I'm not sure if you'll be able to bypass that. You may wish to have a look here, see if there are any images for your device (though I cannot say if they'll flash properly). https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/
The strange thing is that flashing the stock Nougat ROM as you mentioned (and Ayan suggested) should have worked (since the NPJ25.93-14 build seems to be a global, universal build), the only thing I can think of was that something happened with the Marshmallow build on there (either a bad flash or an incorrect ROM, for example), but without asking the former owner, we just don't know.
For information, are you able to reboot into the bootloader, attach your device to your computer and in minimal ADB, execute 'fastboot getvar all' and post the info here, please? You may wish to remove your IMEI and serial number from the output.
Click to expand...
Click to collapse
I didn't know this firmware center, surely will be usefull in the future. Got the latest version updated there for my XT 1640 (answering your question). Flashed it and still the same, flashs ok but don't leave bootloop (I was afraid to find out it's a motherboard problem )
Here is the result of that command line:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(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 SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno:
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: EC9AEB0100000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 11-22-2016
(bootloader) sku: XT1640
(bootloader) battid: SNN5966B
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Apr 21 23:34:21 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: 25.93-14/16:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.16.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62R ATHENE_BRAZIL_DS
(bootloader) version-baseband[1]: DS_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-g478d03a (hudsoncm
(bootloader) kernel.version[1]: @ilclbld26) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Fri Jan 6 05:12:56 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB1.03-0-ge433b40
(bootloader) rpm.git: git=a970ead
(bootloader) tz.git: git=119e5b2-dirty
(bootloader) hyp.git: git=119e5b2-dirty
(bootloader) keymaster.git: git=119e5b2-dirty
(bootloader) cmnlib.git: git=119e5b2-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.03-0-gb44c0ee
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (75)
(bootloader) ro.carrier: retbr
Thanks for the patience
justinwgeiger said:
Okay I understand, I will guide you through the process of unlocking your bootloader then.
Requirements:
A computer and a usb cord,
Moto G4/G4 Plus,
ADB/Fastboot Drivers: https://www.androidfilehost.com/?fid=745425885120698566,
Moto G4/G4 Plus Drivers: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481,
Once you have installed the Minimal ADB and Fastboot tool, launch the tool from the desktop icon named Minimal ADB and Fastboot. You should be brought to a command window.
Now power down your phone and hold the volume down and power button at the same time. you should see a screen pop up. then press the volume down button until you see bootloader and leave it there.
Now at the command window, type:
Code:
fastboot oem get_unlock_data
It should return with something like this:
Code:
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
After that, go to paste it all into notepad (A Windows application) and delete the bootloader text and all other spaces so it looks like this:
Code:
0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
Go to Motorola’s bootloader unlock site and login with Google. Paste the entire code from notepad into the input box there. Then click can my device be unlocked and agree to the terms.
You will then be sent an email to unlock your bootloader.
Put the key that they send you into notepad and put it in the command line like shown below:
Code:
fastboot oem unlock "YOURKEY" (Replace YOURKEY with the key you received)
It will unlock your device. Congratulation you have successfully unlocked your device.
Credits:
devs-lab
If you have any questions or concerns just ask me and I will try my best to help you out. From this point forward you should be able to find your way throughout the forums to install a custom recovery. If not just ask me and I will guide you through that too. Glad to help, .
Click to expand...
Click to collapse
I already had unlocked my bootloader and then installed twrp later, without resatring the device. Now I re locked the bootloader and I am stuck with the MOTO "M" logo, please help
Hi
I'm having a little problem, I initially unlocked my bootloader and installed magisk on my G6 Plus when I bought it. I wanted to upgrade to 9.0 and so tried to flash the new firmware through fastboot. I ended up soft bricking the device and after hours of searching the internet for solutions and trying a lot of different fastboot commands, it suddenly started working again.
It's great that it's working again, however, I'm stuck on OPW27.113-45 and now I can't install magisk or take OTA.
I try going to bootloader and boot into twrp, I get the following command:
C:\mfastboot>fastboot boot twrp-3.2.3-0-evert.img
downloading 'boot.img'...
It basically hangs while sending or downloading anything within fastboot.
I've experimented with multiple versions of mfastboot, platform-tools etc. I have also downloaded multiple firmware versions without success.
I wonder if anyone has come across this problem in the past and has a solution.
I can boot into recovery and could potentially update via adb, however, to do so I need a special update file with signature verification that I can't find.
Ultimately, I want to boot into TWRP, flash Lineage Gapps and Magisk. But with the bootloader "broken" I get stuffed at the first step.
Just some extra information.
I have tried 4 different cables from both usb 2.0 slots and my 3.0 slot. I went and bought a USB c to c cable which also didn't work.
The phone is recognized when I type FASTBOOT DEVICES
Any help greatly appreciated
some more commands and the outcome
C:\mfastboot>mfastboot getvar current-slot
current-slot: _a
finished. total time: 0.001s
C:\mfastboot>mfastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-bf761ac-180403
(bootloader) product: evert
(bootloader) board: evert
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: EMEA
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ufs: N/A
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5=06 M6=04 M7=00 M8=11
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: XXXXXXXXXXXX
It hangs here
my bootloader is unlocked, usb debugging is on.
Fixed
Cracked out my old laptop today to give it a go and see if the issue was my computer.
Turns out it was. I've now been able to update and all is good.
gilljohniez said:
Cracked out my old laptop today to give it a go and see if the issue was my computer.
Turns out it was. I've now been able to update and all is good.
Click to expand...
Click to collapse
I've had this same problem and solution, did you get to what is the problem of the PC? Maybe specs or something?
gilljohniez said:
Hi
I'm having a little problem, I initially unlocked my bootloader and installed magisk on my G6 Plus when I bought it. I wanted to upgrade to 9.0 and so tried to flash the new firmware through fastboot. I ended up soft bricking the device and after hours of searching the internet for solutions and trying a lot of different fastboot commands, it suddenly started working again.
It's great that it's working again, however, I'm stuck on OPW27.113-45 and now I can't install magisk or take OTA.
I try going to bootloader and boot into twrp, I get the following command:
C:\mfastboot>fastboot boot twrp-3.2.3-0-evert.img
downloading 'boot.img'...
It basically hangs while sending or downloading anything within fastboot.
I've experimented with multiple versions of mfastboot, platform-tools etc. I have also downloaded multiple firmware versions without success.
I wonder if anyone has come across this problem in the past and has a solution.
I can boot into recovery and could potentially update via adb, however, to do so I need a special update file with signature verification that I can't find.
Ultimately, I want to boot into TWRP, flash Lineage Gapps and Magisk. But with the bootloader "broken" I get stuffed at the first step.
Just some extra information.
I have tried 4 different cables from both usb 2.0 slots and my 3.0 slot. I went and bought a USB c to c cable which also didn't work.
The phone is recognized when I type FASTBOOT DEVICES
Any help greatly appreciated
Click to expand...
Click to collapse
I'm having the same issue, i don't get the fix, just change computer and it should work?
I solved the described issue without changing computer in the following way:
1. Disconnect phone from computer
2. In cmd type fastboot boot twrp.img (or whatever the filename is)
3. Press enter
4. Connect the phone back to the computer
It should then send the img and boot into twrp successfully. Hope this helped someone.