I'm not familiar with flashing rom, just root the N7 for OTG and some Apps.
But it's unable to update by system update from 421 to 422 recently.
It shows a lying Android with exclamation mark and "no command".
So I try to flash stock rom with Asus root toolkit,
but it halted at bootloader very soon, when I press the power it shows "booting failed"
It is not success when I try to flash 421 or 422
I also try to flash stock recovery, it shows lying Android.
But it's ok to flash CWM or Teamwin, and show that there is problem on mounting sd card
Please advise what I can do
Thanks in advance.
Are you able to boot into the recovery menu or boot loader?
---------- Post added at 06:28 PM ---------- Previous post was at 06:08 PM ----------
If you can get into recovery menu then wipe data/system and flash a new ROM of your choice. If you can't get into recovery but can get into the bootloader then flash CWM or TWRP recovery using fastboot, then flash a new ROM of your choice in the new recovery menu.
I see no reason why this can't be fixed unless you can't get into the bootloader menu... At that point its beyond my knowledge.
Yes, I can flash CWM and Teamwin but not stock
Bootloader ok but when press Start it shows booting failed
Can enter recovery, but both show cant mount cache and sd card
Organized_Chaos said:
Are you able to boot into the recovery menu or boot loader?
---------- Post added at 06:28 PM ---------- Previous post was at 06:08 PM ----------
If you can get into recovery menu then wipe data/system and flash a new ROM of your choice. If you can't get into recovery but can get into the bootloader then flash CWM or TWRP recovery using fastboot, then flash a new ROM of your choice in the new recovery menu.
I see no reason why this can't be fixed unless you can't get into the bootloader menu... At that point its beyond my knowledge.
Click to expand...
Click to collapse
What happens when you do it from command line using adb/fastboot? That should probably give you more detailed info on why it failed.
Jack425 said:
Yes, I can flash CWM and Teamwin but not stock
Bootloader ok but when press Start it shows booting failed
Can enter recovery, but both show cant mount cache and sd card
Click to expand...
Click to collapse
Forget about the root toolkit and use fastboot in command line. There are tutorials on this.
Download newest stock 4.2.2 from google.
Open command.
Put n7 in bootloader
Type-
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-jrn84d.zip
Replace "bootloader-grouper-3.34.img" and "image-nakasi-jrn84d.zip" with the new ones you downloaded.
Once done, you can unlock the bootloader again using "fastboot oem unlock" , and the re-root and install custom recovery, then flash custom roms all you want.
Sent from my SGH-I727 using xda premium
Organized_Chaos said:
What happens when you do it from command line using adb/fastboot? That should probably give you more detailed info on why it failed.
Click to expand...
Click to collapse
for CWM, I can see the following
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
for Teamwin
E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/cache'
E:TWFunc::Copy_Log, --Can't open destination log file: '/cache/recovery/log'
E:Unable to mount '/cache'
All wipe or Fix permission on recovery are tried, are there any information I provided are not clear, sorry that I mainly use the toolkit and not so familiar with command line, thanks
rebel1699 said:
Forget about the root toolkit and use fastboot in command line. There are tutorials on this.
Download newest stock 4.2.2 from google.
Open command.
Put n7 in bootloader
Type-
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-jrn84d.zip
Replace "bootloader-grouper-3.34.img" and "image-nakasi-jrn84d.zip" with the new ones you downloaded.
Once done, you can unlock the bootloader again using "fastboot oem unlock" , and the re-root and install custom recovery, then flash custom roms all you want.
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
Hi, I followed the steps, but after reboot-bootloader, the N7 just stay at bootloader"START", even I proceed to update image
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.18
Baseband Version.....: 1231------------
Serial Number........: 01--------------
--------------------------------------------
checking product...
OKAY [ 0.047s]
checking version-bootloader...
OKAY [ -0.000s]
checking version-baseband...
FAILED
Device version-baseband is '1231_0.10.0_1021'.
Update requires '1231_0.17.0_1205'.
finished. total time: 0.281s
After all commands are executed, the screen is staying at "START", it shows "booting failed" when I press power, and the recovery need to be flashed again
Jack425 said:
Hi, I followed the steps, but after reboot-bootloader, the N7 just stay at bootloader"START", even I proceed to update image
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.18
Baseband Version.....: 1231------------
Serial Number........: 01--------------
--------------------------------------------
checking product...
OKAY [ 0.047s]
checking version-bootloader...
OKAY [ -0.000s]
checking version-baseband...
FAILED
Device version-baseband is '1231_0.10.0_1021'.
Update requires '1231_0.17.0_1205'.
finished. total time: 0.281s
After all commands are executed, the screen is staying at "START", it shows "booting failed" when I press power, and the recovery need to be flashed again
Click to expand...
Click to collapse
So after typing "fastboot reboot bootloader" it doesnt reboot back to the bootloader? It just stays there?
Sent from my SGH-I727 using xda premium
rebel1699 said:
So after typing "fastboot reboot bootloader" it doesnt reboot back to the bootloader? It just stays there?
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
it rebooted, dark for 1-2 seconds, google screen flash less than 1sec and return the bootloader-Start again
Jack425 said:
it rebooted, dark for 1-2 seconds, google screen flash less than 1sec and return the bootloader-Start again
Click to expand...
Click to collapse
Thats exactly what it is suppose to do. The command "fastboot reboot bootloader" means reboot back into the bootloader so the bootloader flash can set in and you can issue the rest of the commands. After it reboots to bootloader, it is time to flash the os. "Fastboot flash update -w "version you downloaded here.zip
Sent from my SGH-I727 using xda premium
rebel1699 said:
Thats exactly what it is suppose to do. The command "fastboot reboot bootloader" means reboot back into the bootloader so the bootloader flash can set in and you can issue the rest of the commands. After it reboots to bootloader, it is time to flash the os. "Fastboot flash update -w "version you downloaded here.zip
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
checking product...
OKAY [ 0.031s]
checking version-bootloader..
OKAY [ 0.016s]
checking version-baseband...
FAILED
Device version-baseband is '1
Update requires '1231_0.17.0_
finished. total time: 0.187s
But it is still at Bootloader-Start when above commands finished, I press the power and got "booted Failed"
after restart bootloader, both Start and Recover Mode got "booted Failed" on left corner
Jack425 said:
checking product...
OKAY [ 0.031s]
checking version-bootloader..
OKAY [ 0.016s]
checking version-baseband...
FAILED
Device version-baseband is '1
Update requires '1231_0.17.0_
finished. total time: 0.187s
But it is still at Bootloader-Start when above commands finished, I press the power and got "booted Failed"
after restart bootloader, both Start and Recover Mode got "booted Failed" on left corner
Click to expand...
Click to collapse
It looks like you are trying to flash a custom rom through fastboot. You cant do that. You have to download the official stock image from google.
Sent from my SGH-I727 using xda premium
rebel1699 said:
It looks like you are trying to flash a custom rom through fastboot. You cant do that. You have to download the official stock image from google.
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
I was downloaded from https://dl.google.com/dl/android/aosp/nakasig-jdq39-factory-0798439d.tgz
and extract >nakasig-jdq39-factory-0798439d.tar> nakasig-jdq39
to get bootloader-tilapia-4.18.img and image-nakasig-jdq39.zip
I just tried again to download and flash again, the bootloader show "signature match." after flashed the bootloader.
Jack425 said:
I was downloaded from https://dl.google.com/dl/android/aosp/nakasig-jdq39-factory-0798439d.tgz
and extract >nakasig-jdq39-factory-0798439d.tar> nakasig-jdq39
to get bootloader-tilapia-4.18.img and image-nakasig-jdq39.zip
I just tried again to download and flash again, the bootloader show "signature match." after flashed the bootloader.
Click to expand...
Click to collapse
The image you downloaded is for the Nexus 7 3G. Do you have the wifi or 3G model?
Sent from my Nexus 7 using xda premium
rebel1699 said:
The image you downloaded is for the Nexus 7 3G. Do you have the wifi or 3G model?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yes, my one is N7 3G
Jack425 said:
Yes, my one is N7 3G
Click to expand...
Click to collapse
Ok, then if the bootloader is flashing correctly, but the image-nakasig-jdq39.zip is not, then you have yourself a brick, more than likely.
Sent from my Nexus 7 using xda premium
LOL, i just got it yesterday. i made a mistake when wipe all my data and os :laugh: so it cannot start but luckily i still start bootloader.
u can use a 2gb usb to mount image-nakasig-jdq39.zip (i try with a 4gb usb but it cannot mount). Then now it's ok. Hope this usefut 4 u
ceballos124 said:
LOL, i just got it yesterday. i made a mistake when wipe all my data and os :laugh: so it cannot start but luckily i still start bootloader.
u can use a 2gb usb to mount image-nakasig-jdq39.zip (i try with a 4gb usb but it cannot mount). Then now it's ok. Hope this usefut 4 u
Click to expand...
Click to collapse
hi, which recovery did u use ?
Thanks to everyone advised to me,
as I find that the process of fastboot -w update image-nakasig-jdq39.zip is very short,
I try to unzip and flash .img one by one,
Finally, I can boot into Android, just found that the recovery is still "Lying Android"
Related
ok so here is the deal, been running mytouch4g for a while now rooted, cm7 etc last week phone started acting funny, required batt out reboots if camera app was on when unit went to sleep, now will not boot only boots to fastboot, can not flash anything.
Any ideas? at least an idea to remove cm signs so I can exchange unit.
thanks
zendick said:
ok so here is the deal, been running mytouch4g for a while now rooted, cm7 etc last week phone started acting funny, required batt out reboots if camera app was on when unit went to sleep, now will not boot only boots to fastboot, can not flash anything.
Any ideas? at least an idea to remove cm signs so I can exchange unit.
thanks
Click to expand...
Click to collapse
There should be an option on fastboot to go to bootloader and then from there recovery should be available, is that option available to you?
yes but recovery won't boot, sits at mt4g boot screen or sits at 3 skaters in center screen, depending on how I access it (ie go to fastboot then back again)
Power down your phone, hold volume down and the power button. That will take you into the hboot screen. You can then select to go into recovery from there.
thats what I have tried, it goes to three skaters center screen does nothing
I have tried flashing recovery from fastboot
tried hboot from fastboot
tried radio from fastboot
NOTHING flashes trust me I have been androiding for a while now never had I had a problem like this.
zendick said:
thats what I have tried, it goes to three skaters center screen does nothing
Click to expand...
Click to collapse
Is three skaters your boot animation or splash screen? Not sure what that is referring to.
the three skaters is the image at bottom of hboot screen, when i select recovery they go to center screen and nothing happens
zendick said:
the three skaters is the image at bottom of hboot screen, when i select recovery they go to center screen and nothing happens
Click to expand...
Click to collapse
Oh ok, i know what your talking about now. Your on the bootloader screen under fastboot. And when you select recovery option it does not boot into recovery?
correct and like i said I have tried to reflash everything from fastboot but no go
Just tried RUU it doesn't work it says rebooting to bootloader phone reboots to mytouch4g splash and ruu eventually gives usb error
got recovery to boot but get
e:can't mount /cache/recovery/command
etc
tried to mount, tried to format
no go
What do you mean tried ruu??
zendick said:
Just tried RUU it doesn't work it says rebooting to bootloader phone reboots to mytouch4g splash and ruu eventually gives usb error
Click to expand...
Click to collapse
Edit: nvm. Is doing RUU better option than loading PD15IMG.ZIP on sdcard and doing it that way?
Sent from my SGH-T959 using XDA App
tried a pd15 and it doesn't complete, drops a failed message
Sounds like you maybe victim of fail-pu. But if thats not the case and you don't care about your "/data" and just want working phone again then I suggest from fastboot you do "fastboot flash recovery recovery.img" which will replace the current recovery.img and flash it to mmcblk0p21. Once thats done do "fastboot erase system -w" and it will nuke everything so /system, /data, ect will all be erased. After that you can enter recovery by selecting it from hboot and then do factory wipe and flash another rom.
Keep in mind you will run in to errors in recovery after -w as its normal but depending on the fail-pu if you do get the failed partition update flag you can't make any changes as the errors will stick because you can't format the drives. Also the new recovery.img for CWMR can be found in dev section if not post here and ill send you.
I don't care at all about the data (I am well backed up) but I can't flash a recovery I have tried through fastboot, I agree the partition is F_D but I will try the erase system -w and see if that lets me do anything
thanks
uhg i think i may be foooked
C:\android-sdk\tools>fastboot flash recovery recovery2512.img
sending 'recovery' (4000 KB)...
OKAY [ 1.273s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 4.161s
C:\android-sdk\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: erasing error!)
finished. total time: 0.014s
Exactly what I got too, seems we have bricked our phones. Wish I had a way of making the phone unable to boot to recovery or at all.
zendick said:
uhg i think i may be foooked
C:\android-sdk\tools>fastboot flash recovery recovery2512.img
sending 'recovery' (4000 KB)...
OKAY [ 1.273s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 4.161s
C:\android-sdk\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: erasing error!)
finished. total time: 0.014s
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App
I dont get how a phone can run for weeks since its last flash and have this happen, I made no changes updates etc just running as normal.
Is there a way to wipe evidence of cm of so I can get this phone repaired? To me this obviously a faulty emmc, I just can't see it being anything else.
or is it possible to boot recovery on sd like the nook?
any ideas on how to wipe cm bits atleast?
Hello,
After updating my Nexus 4 the phone won't boot beyond the Google logo.
I tried to hardreset the phone but when I select "Recovery mode" the phone show me the Google logo and just gets stuck there.
Any ideas?
S_Kruis said:
Hello,
After updating my Nexus 4 the phone won't boot beyond the Google logo.
I tried to hardreset the phone but when I select "Recovery mode" the phone show me a the Google logo and just gets stuck there.
Any ideas?
Click to expand...
Click to collapse
Reflash everything with fastboot or just enter the stock recovery and factory reset. You can get there by choosing recovery at the bootloader and then by pressing vol up + power when you see the green logo with the exclamation mark.
lordneopt said:
Reflash everything with fastboot or just enter the stock recovery and factory reset. You can get there by choosing recovery at the bootloader and then by pressing vol up + power when you see the green logo with the exclamation mark.
Click to expand...
Click to collapse
How can i execute either option?
S_Kruis said:
How can i execute either option?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/general/unroot-nexus-4-to-100-stock-complete-t2039162
but use 4.4.2 factory image: https://developers.google.com/android/nexus/images?hl=pt-PT#occamkot49h
C4SCA said:
http://forum.xda-developers.com/nexus-4/general/unroot-nexus-4-to-100-stock-complete-t2039162
but use 4.4.2 factory image: https://developers.google.com/android/nexus/images?hl=pt-PT#occamkot49h
Click to expand...
Click to collapse
When I'm executing "fastboot flash bootloader bootloader-mako-makoz10l.img"
I give me this error:
ako-makoz10l.img
sending 'bootloader' (2188 KB)...
OKAY [ 0.081s]
writing 'bootloader'...
FAILED (remote: not supported in locked device)
finished. total time: 0.083s
Click to expand...
Click to collapse
S_Kruis said:
When I'm executing "fastboot flash bootloader bootloader-mako-makoz10l.img"
I give me this error:
Click to expand...
Click to collapse
You're bootloader is locked. Do a factory reset in the stock recovery
Sent from my Nexus 5 using XDA Free mobile app
Finally I unlocked the bootloader but now i got a error on this command.
"fastboot -w update image-occam-jop40c.zip" the error that I get is this one...
c:\Fastboot\4.2UnrootNexus4>fastboot -w update image-occam-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 544032752 bytes
error: update package missing system.img
Click to expand...
Click to collapse
S_Kruis said:
Finally I unlocked the bootloader but now i got a error on this command.
"fastboot -w update image-occam-jop40c.zip" the error that I get is this one...
Click to expand...
Click to collapse
The.sig errors are ok. The failed to allocate error is not. Try to flash just the system.img. fastboot flash system system.img.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
The.sig errors are ok. The failed to allocate error is not. Try to flash just the system.img. fastboot flash system system.img.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Flashing went well but when it boots its stuck a the Google logo.
When I try to get it in Recovery mode I only get Download mode.
Try to flash a custom recovery then and see if it works. If it does try flashing the zip from recovery. On my HTC sometimes flashing from fastboot would result in a bootloop while from recovery it worked perfectly fine.
Sent from my Nexus 4 using XDA Free mobile app
Hi All,
Due to in ternal memory full, suddenly my home button stopped working and notifications were not appearing. I tried and followed advice written in one of the websites:
"f you didn't enabled developer settings and usb debug prior to the defect, you can create an icon to call this Activity using Nova Launcher.
After installing it and launching, long press home screen, select widgets, swipe right to find Activity icon, place on empty space in your home, search for setup wizard (it changes accordingly to your native language), select .SetupWizardTestActivity and voilá."
But, now my phone is stuck in SetupWizardTestActivity loop. I desperately need to recover my photos and other data on internal memory.
Please suggest.
Additional Info:
Using Moto X play (updated to Marshmallow)
Bootloader is unlocked
Can't you just boot into safe mode and try if that works.
Boot into Safe Mode
With the phone on, press and hold the power key until the on-screen “Power off” option shows up.
Long press on the on-screen button, and select “Boot into Safe Mode.”
or if you have an unlocked bootloader you can flash TWRP and use the build in file manager to transfer the files to your sd.
anujagraj said:
Hi All,
Due to in ternal memory full, suddenly my home button stopped working and notifications were not appearing. I tried and followed advice written in one of the websites:
"f you didn't enabled developer settings and usb debug prior to the defect, you can create an icon to call this Activity using Nova Launcher.
After installing it and launching, long press home screen, select widgets, swipe right to find Activity icon, place on empty space in your home, search for setup wizard (it changes accordingly to your native language), select .SetupWizardTestActivity and voilá."
But, now my phone is stuck in SetupWizardTestActivity loop. I desperately need to recover my photos and other data on internal memory.
Please suggest.
Additional Info:
Using Moto X play (updated to Marshmallow)
Bootloader is unlocked
Click to expand...
Click to collapse
If bootloader is unlocked then recovering data is easy, I guess you have TWRP recovery if not flash twrp then pop in a sd-card boot into recovery and copy everything to the card. Done.
Edit: the above comment says the same thing, I had not noticed that .
While flashing TWRP recovery, I am getting the following message in CMD:
target reported max download size of 268435456 bytes
sending 'recovery' (8362 KB)...
OKAY [ 0.276s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.310s
In phone's bootloader logs, I can see: "Mismatched partition size (recovery).
Please help!
Lennyz1988 said:
Can't you just boot into safe mode and try if that works.
Boot into Safe Mode
With the phone on, press and hold the power key until the on-screen “Power off” option shows up.
Long press on the on-screen button, and select “Boot into Safe Mode.”
or if you have an unlocked bootloader you can flash TWRP and use the build in file manager to transfer the files to your sd.
Click to expand...
Click to collapse
Hi,
Safe mode is not helping. Same loop is continuing.
Also, I am not able to flash TWRP custom recovery. I am getting the following message:
(bootloader) Preflash validation failed
FAILED (remote failure)
In phone bootloader logs I can see: "Mismatched partition size (recovery).
bablu048 said:
If bootloader is unlocked then recovering data is easy, I guess you have TWRP recovery if not flash twrp then pop in a sd-card boot into recovery and copy everything to the card. Done.
Edit: the above comment says the same thing, I had not noticed that .
Click to expand...
Click to collapse
While flashing TWRP recovery, I am getting the following message in CMD:
target reported max download size of 268435456 bytes
sending 'recovery' (8362 KB)...
OKAY [ 0.276s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.310s
In phone bootloader logs I can see: "Mismatched partition size (recovery).
Please help!
anujagraj said:
While flashing TWRP recovery, I am getting the following message in CMD:
target reported max download size of 268435456 bytes
sending 'recovery' (8362 KB)...
OKAY [ 0.276s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.310s
In phone bootloader logs I can see: "Mismatched partition size (recovery).
Please help!
Click to expand...
Click to collapse
is the bootloader unlocked, did you input the code to unlock??just checking
Yes. Bootlader is unlocked with input code to unlock.
I guess adb is not authorised then. when the phone is in setup wizard connect it to pc and type 'adb devices' there will be a pop-up asking you to authorise adb. select it. the try to flash recovery again .
---------- Post added at 07:47 AM ---------- Previous post was at 07:44 AM ----------
anujagraj said:
Yes. Bootlader is unlocked with input code to unlock.
Click to expand...
Click to collapse
or simply run
fastboot boot <enter twrp name>
bablu048 said:
I guess adb is not authorised then. when the phone is in setup wizard connect it to pc and type 'adb devices' there will be a pop-up asking you to authorise adb. select it. the try to flash recovery again .
---------- Post added at 07:47 AM ---------- Previous post was at 07:44 AM ----------
or simply run
fastboot boot <enter twrp name>
Click to expand...
Click to collapse
"adb devices" is not working during Setup wizard.
Do you mean to say that I run fastboot boot <enter twrp name> during setup wizard?
Also, alternatively, will flashing a rom without clearing user data help in any way?
Thanks a lot for the help..
bablu048 said:
I guess adb is not authorised then. when the phone is in setup wizard connect it to pc and type 'adb devices' there will be a pop-up asking you to authorise adb. select it. the try to flash recovery again .
---------- Post added at 07:47 AM ---------- Previous post was at 07:44 AM ----------
or simply run
fastboot boot <enter twrp name>
Click to expand...
Click to collapse
adb and fastboot are different things and are unrelated to each other. He doesn't need adb to flash the recovery.
anujagraj said:
"adb devices" is not working during Setup wizard.
Do you mean to say that I run fastboot boot <enter twrp name> during setup wizard?
Also, alternatively, will flashing a rom without clearing user data help in any way?
Thanks a lot for the help..
Click to expand...
Click to collapse
What happens when you just clear /cache in the stock recovery?
What recovery are you trying to flash?
Lennyz1988 said:
adb and fastboot are different things and are unrelated to each other. He doesn't need adb to flash the recovery.
What happens when you just clear /cache in the stock recovery?
What recovery are you trying to flash?
Click to expand...
Click to collapse
Clear /cache in the stock recovery didn't help. Also, I am trying to flash TWRP recovery 2.8.7.
no, boot phone in fastboot mode ...then run the command
fastboot boot <recovery>
try latest TWRP
bablu048 said:
no, boot phone in fastboot mode ...then run the command
fastboot boot <recovery>
try latest TWRP
Click to expand...
Click to collapse
Hi,
I tried re-unlocking the phone using code and got following message:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.008s
Any workaround?
unlocking bootloader will wipe the data in your phone.
I thought you had unlocked.
what is the problem when you try to setup the phone ? or skip the setup
---------- Post added at 05:15 PM ---------- Previous post was at 05:12 PM ----------
anujagraj said:
Hi,
I tried re-unlocking the phone using code and got following message:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.008s
Any workaround?
Click to expand...
Click to collapse
best option now is flashing the firmware manually without wiping data.
Read this, also read a few comments after it.http://forum.xda-developers.com/showpost.php?p=65715334&postcount=43
bablu048 said:
unlocking bootloader will wipe the data in your phone.
I thought you had unlocked.
what is the problem when you try to setup the phone ? or skip the setup
---------- Post added at 05:15 PM ---------- Previous post was at 05:12 PM ----------
best option now is flashing the firmware manually without wiping data.
Read this, also read a few comments after it.http://forum.xda-developers.com/showpost.php?p=65715334&postcount=43
Click to expand...
Click to collapse
Hi,
Where can I find firmware to flash on my phone?
Also RSDLite is not able to detect phone. Can I enter commands from fastboot?
Thanks!
anujagraj said:
Hi,
Where can I find firmware to flash on my phone?
Also RSDLite is not able to detect phone. Can I enter commands from fastboot?
Thanks!
Click to expand...
Click to collapse
RSD lite needs windows 7.
Yes you have to flash manually then using fastboot commands.
firmware
Just don't use the command to erase user data. Skip it. Open the zip there will be flashfile. xml/servicefile.xml open it , you will find the list of commands to run. Or the commands can be found here.
bablu048 said:
RSD lite needs windows 7.
Yes you have to flash manually then using fastboot commands.
firmware
Just don't use the command to erase user data. Skip it. Open the zip there will be flashfile. xml/servicefile.xml open it , you will find the list of commands to run. Or the commands can be found here.
Click to expand...
Click to collapse
Just to confirm, will any firmware will work or I need to download one specific to my phone/higher version?
Also, any risks of bricking the device while flashing?
anujagraj said:
Just to confirm, will any firmware will work or I need to download one specific to my phone/higher version?
Also, any risks of bricking the device while flashing?
Click to expand...
Click to collapse
If you are on 6.0.1 then flash 6.0.1...better flash the appropriate region firmware.
There is a risk of bricking if you are downgrading and flash old gpt.bin and bootloader
As long as you are flashing proper firmware it's safe thoughi haven't done it but as you can see the comments I linked previously others have done it.
bablu048 said:
If you are on 6.0.1 then flash 6.0.1...better flash the appropriate region firmware.
There is a risk of bricking if you are downgrading and flash old gpt.bin and bootloader
As long as you are flashing proper firmware it's safe thoughi haven't done it but as you can see the comments I linked previously others have done it.
Click to expand...
Click to collapse
Hi,
I have an Indian model and got the following error on flashing contents of XT1562_LUX_RETASIA_DS_6.0_MPD24.65-18.1_cid7_subsidy-DEFAULT_CFC.xml using fastboot:
AP Fastboot Flash Mode (Secure)
failed to validate system image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from charger boot mode
Please help!
Hello and thanks in advance to everyone,
I am trying to root my moto g4 but I am stuck on installing a recovery. I did unlock the bootloader and when I turn on the phone i am greeted with"this device is unlocked and can't be trusted"
Yet when i try to flash the recovery it states that it failed to install since the package is unsigned:
C:\Users\Jelle\Desktop\Nieuwe map>mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (12496 KB)...
OKAY [ 0.405s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.344s]
finished. total time: 0.748s
Re-entering my unlock code also does not work as it gives me this message:
C:\Users\Jelle\Desktop\Nieuwe map>fastboot oem unlock NYRTWS*************
...
(bootloader) invalid boot state
OKAY [ -0.000s]
finished. total time: -0.000s
Does someone have any idea on what the issue is, am I missing something?
Thank you in advance!
Twrp is for motog4 plus aka athene. Make sure your device is the same.
Just reboot to recovery after you flash twrp using fast boot. Do not reboot your device to your home screen as your recovery partition will be rewritten with the stock recovery.
Do not worry about the message. It doesn't say that flashing failed. It only gives you a warning that it's not signed. That message is displayed even if you flash the stock recovery using fast boot.
Sent from my Moto G (4) using Tapatalk
Silesh.Nair said:
Twrp is for motog4 plus aka athene. Make sure your device is the same.
Just reboot to recovery after you flash twrp using fast boot. Do not reboot your device to your home screen as your recovery partition will be rewritten with the stock recovery.
Do not worry about the message. It doesn't say that flashing failed. It only gives you a warning that it's not signed. That message is displayed even if you flash the stock recovery using fast boot.
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
that totally worked! thank you very much
same problem mentioned above but after recovery mode my devicxe says no command.
help mw plzzz
sauravchandela95 said:
same problem mentioned above but after recovery mode my devicxe says no command.
help mw plzzz
Click to expand...
Click to collapse
If you're getting a screen with 'no command', that's the stock recovery on your device.
Are you rebooting to the recovery straight after flashing TWRP? Do you have an unlocked bootloader and what version of TWRP are you flashing? What commands are you using to flash?
You may wish to try booting with TWRP first:
1)On a device with an unlocked bootloader, boot to the bootloader screen.
2)Connect your device to your computer via a high quality USB data cable or the original USB cable.
3)Ensure your TWRP image is copied to your ADB folder.
4)Open an ADB terminal. Verify your device is communicating with your computer by typing 'fastboot devices' without quotes. Press Enter. You should get a serial number response.
5)If so, then type 'fastboot boot twrp.img' without quotes. Replace twrp.img with the actual full file name of your TWRP image in your ADB folder including the file extension. For example, if your TWRP image file name is shreps_twrp_3_1_1.img, the full command would be fastboot boot shreps_twrp_3_1_1.img You can type the first few letters of the file name and press Tab on your keyboard to automatically complete the file name if you so wish.
6)Press Enter, and your device should download TWRP and boot to TWRP.
I had previously rooted my Moto G4 Plus and used multiple custom ROMs before switching back to Stock firmware.
Now, I'm unable to flash TWRP on my device. Any attempts to flash TWRP ends up with the following error:
Code:
reboot bootloader
mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (12530 KB)...
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.203s]
finished. total time: 0.608s
Any further tries to reboot via adb commands results in the following:
Code:
adb reboot recovery
error: device not found
adb reboot
error: device not found
adb reboot bootloader
error: device not found
The device says the bootloader is unlocked while rebooting. the ID field shows 'bad key'(I feel this is weird).
Can someone please help me with this?
Thanks
unknown_geek said:
I had previously rooted my Moto G4 Plus and used multiple custom ROMs before switching back to Stock firmware.
Now, I'm unable to flash TWRP on my device. Any attempts to flash TWRP ends up with the following error:
Code:
reboot bootloader
mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (12530 KB)...
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.203s]
finished. total time: 0.608s
Any further tries to reboot via adb commands results in the following:
Code:
adb reboot recovery
error: device not found
adb reboot
error: device not found
adb reboot bootloader
error: device not found
The device says the bootloader is unlocked while rebooting. the ID field shows 'bad key'(I feel this is weird).
Can someone please help me with this?
Thanks
Click to expand...
Click to collapse
It has got flashed correctly as you got "OKAY" at end of command. Try to boot into recovery and tell us what happens.
1) That TWRP message of 'Image not signed or corrupt' is normal, since the TWRP custom recovery is not signed. After you see the [OKAY], reboot to recovery directly to fix the TWRP, else the stock recovery will overwrite it. Afterwards, you can boot as normal.
2)If you're still in the bootloader on your device, adb commands do not work - you need to use fastboot commands, or use your device volume keys to select 'Start' (to boot to system) or 'Recovery mode' (to boot to recovery) and press the power key to select. Of course, in this case, after flashing TWRP, you'll want to select 'Recovery Mode' in your bootloader and press the power key. This should then boot into TWRP.
If you find yourself in the bootloader in the future, then 'fastboot reboot' or 'fastboot continue' (both commands to be used without quotes, in the ADB terminal) may get your device rebooting to system.
3)ID Bad key is normal with an unlocked bootloader, on subsequent boots this may change to ID:N/A
echo92 said:
1) That TWRP message of 'Image not signed or corrupt' is normal, since the TWRP custom recovery is not signed. After you see the [OKAY], reboot to recovery directly to fix the TWRP, else the stock recovery will overwrite it. Afterwards, you can boot as normal.
2)If you're still in the bootloader on your device, adb commands do not work - you need to use fastboot commands, or use your device volume keys to select 'Start' (to boot to system) or 'Recovery mode' (to boot to recovery) and press the power key to select. Of course, in this case, after flashing TWRP, you'll want to select 'Recovery Mode' in your bootloader and press the power key. This should then boot into TWRP.
If you find yourself in the bootloader in the future, then 'fastboot reboot' or 'fastboot continue' (both commands to be used without quotes, in the ADB terminal) may get your device rebooting to system.
3)ID Bad key is normal with an unlocked bootloader, on subsequent boots this may change to ID:N/A
Click to expand...
Click to collapse
Hi @echo92,
Thanks for pointing out what I was doing wrong. I now realize that the TWRP recovery was being overwritten by stock recovery and I didn't know adb commands don't work while still in bootloader mode.
I did boot into recovery mode from the bootloader (using the volume buttons from the phone) and it worked.
And the ID: bad key is also gone and now it shows ID: N/A.
Thanks again for your help!
Regards
____Mdd said:
It has got flashed correctly as you got "OKAY" at end of command. Try to boot into recovery and tell us what happens.
Click to expand...
Click to collapse
Hi @____Mdd,
I rebooted into recovery right after flashing TWRP and it worked fine. Now, I'm able to boot into TWRP recovery.
Thanks for your response.
Regards.
Im Facing this issue while flashing TWRP
C:\adb>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (12644 KB) OKAY [ 0.422s]
Writing 'recovery' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
vaibhavhr2010 said:
Im Facing this issue while flashing TWRP
Click to expand...
Click to collapse
Pre flash validation errors suggest that your bootloader is locked (i.e. you have not unlocked your bootloader, or it has been re locked). Can you confirm your bootloader is unlocked, e.g. if there is a warning screen on boot saying your device is unlocked?
echo92 said:
Pre flash validation errors suggest that your bootloader is locked (i.e. you have not unlocked your bootloader, or it has been re locked). Can you confirm your bootloader is unlocked, e.g. if there is a warning screen on boot saying your device is unlocked?
Click to expand...
Click to collapse
Thank You for the Reply!
Yes I have already unlocked the Bootloader.
The device status in Bootloader shows Device is Unlocked, Status Code: 3
vaibhavhr2010 said:
Thank You for the Reply!
Yes I have already unlocked the Bootloader.
The device status in Bootloader shows Device is Unlocked, Status Code: 3
Click to expand...
Click to collapse
Thanks, what device are you trying to flash TWRP to and which TWRP image are you using?
echo92 said:
Thanks, what device are you trying to flash TWRP to and which TWRP image are you using?
Click to expand...
Click to collapse
I'm Flashing my Moto G4 using the twrp-3.0.2-3-titan.
vaibhavhr2010 said:
I'm Flashing my Moto G4 using the twrp-3.0.2-3-titan.
Click to expand...
Click to collapse
That TWRP won't work, if it's for Titan. The codename for Moto G4/plus is athene, only TWRP images specifying athene in their name will work.
https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206 or https://eu.dl.twrp.me/athene/ give these a try instead