Related
Hi everyone,
I was on here a few months ago with issues regarding my rooted NT. I was told that after I ran Chainfire 3D, it somehow changed the internal memory to Read Only- no changes can be permanently made. Every time it is rebooted, it resets to how it was setup prior to running Chainfire 3D. I just wanted to know if anyone has resolved this issue yet, since I saw before that a few others had the same issue.
Any help appreciated!
Thanks,
Ashlee
My NT is in this state for 5 month already. This is not related to Chainfire 3D, I never used it. We need hardware guys here, Adam Outler perhaps.
My bad...someone on the forums told me that's what messed up my NT. Anyways, yes, I've had the problem for about the same time as you!
Hopefully someone can help us out
Can you try to be more clear about your problem guys? Can you flash new cwm/twrp? Do you have a adb shell access with root privileges?
Just some question that need answering so we can help you out.
Also only 8gb or 16gb too? Thanks.
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
We can't change ANYTHING on internal emmc. So no, we can't flash twrp/cwm. But we can run it from sdcard.
Do you have a adb shell access with root privileges?
Click to expand...
Click to collapse
Yes, I do. Both in CWM and Android.
Also only 8gb or 16gb too?
Click to expand...
Click to collapse
16G only, I think.
Related topics:
1
2
3
4
Ditto...
ok then, go get chris's jelly bean 5.1 or any rom that will give you Cyanoboot and fastboot mode.
Prepare sd card with that rom.
Download this recovery:
http://www.multiupload.nl/ZPSLTX4223
Access fastboot from booting from sd card and stop boot at cyanoboot pressing N.
Then flash that recovery image and tell me if it flashes ok or you have errors.
If flash ok proceed to wipe everything and flash cm10/whatever (tm) rom except stock.
Code:
[[email protected] ~]$ fastboot flash recovery downloads/cwm_6013_emmc.img
sending 'recovery' (8220 KB)...
OKAY [ 4.134s]
writing 'recovery'...
OKAY [ 0.752s]
finished. total time: 4.886s
[[email protected] ~]$ fastboot reboot
rebooting...
finished. total time: 0.000s
Nothing changed. I still have stock recovery.
Hmm strange indeed..
ok dont reboot and try this,
Flash recovery then
fastboot continue then volume rocket select recovery from menu and boot into it.
Tell me what you have, stock or new one.
Code:
[[email protected] ~]$ fastboot flash recovery downloads/cwm_6013_emmc.img
sending 'recovery' (8220 KB)...
OKAY [ 4.202s]
writing 'recovery'...
OKAY [ 0.752s]
finished. total time: 4.954s
[[email protected] ~]$ fastboot continue
resuming boot...
OKAY [ 0.000s]
finished. total time: 0.000s
Still stock.
Well,
I can only state here that i don't in anyway have any responsibility for anything that can happen to your Nook Tablet following my recomendations.
All am trying here is to help you and others with same problem to have a functional Nook Tablet with no one blame me for any bad side effects that maybe arise.
I type these words because next steps are going to fully wipe your Nook and you maybe as well need to recover it by your self if it works. You have to look into forum for solutions.
Ok now for the trial and error:
1St download the factory image from Barnes and Noble in zip state dont unzip it dont mess with it and place it where fastboot.exe or binary is.
Boot into fastboot and
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Then:
fastboot flash recovery (stock barnes and noble recovery).img
fastboot -w update factory-image-1.4.x.zip
Fastboot reboot.
Edit:
Stock Recovery 1.4.3, Go thank lavero.burgos for this here:http://forum.xda-developers.com/showthread.php?t=1640958
http://www.multiupload.nl/9CVIXNOFAM
Stock Rom 1.4.3
http://su.barnesandnoble.com/nook/n...0ZKAA8MujlFdXFU08/nooktablet_1_4_3_update.zip
Nothing changed.
Code:
[[email protected] ~]$ fastboot erase boot
erasing 'boot'...
OKAY [ 1.479s]
finished. total time: 1.479s
[[email protected] ~]$ fastboot erase cache
erasing 'cache'...
OKAY [ 40.361s]
finished. total time: 40.361s
[[email protected] ~]$ fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.389s]
finished. total time: 1.390s
[[email protected] ~]$ fastboot erase system
erasing 'system'...
OKAY [ 57.639s]
finished. total time: 57.639s
[[email protected] ~]$ fastboot erase userdata
erasing 'userdata'...
OKAY [201.688s]
finished. total time: 201.688s
[[email protected] ~]$ fastboot flash recovery downloads/bnstock143.img
sending 'recovery' (3132 KB)...
OKAY [ 1.578s]
writing 'recovery'...
OKAY [ 0.315s]
finished. total time: 1.893s
[[email protected] ~]$ fastboot -w update downloads/nooktablet_1_4_3_update.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
error: Segmentation fault
[[email protected] ~]$ fastboot reboot
rebooting...
finished. total time: 0.000s
So lets us keep hammering it.
This time dont flash recovery boot it from memory.
Place cwm-recovery.img where fastboot is then:
Fastboot boot cwm_6013_emmc.img
Here it is:
http://www.multiupload.nl/ZPSLTX4223
While you are in Recovery wipe everything.I hope this time we succeed!
And find a way to flash a cm10 rom like 0.5.1 etc
Like:
fastboot -w update cm10-rom.zip
I was trying to wipe everything multiple times before, with all methods on forum, and every time after reboot I was still having the same CM7 with all my data, as 5 month ago. I'm just want to determine, whether this is faulty chip or some kind of software lock.
Sorry, my English is horrible.
Maybe it has to do with the locked bootloader.
Something you did and doesn't play well with it.
Did you try dd the bootloader from a working one?
Did you try dd the bootloader from a working one?
Click to expand...
Click to collapse
Yes, I did.
My personal opinion would be to return the unit back to B&N for an exchange.
How? I'm from Ukraine, not from US. Besides that, I have some personal data stored on internal memory, that I cannot erase.
Unbrick NT & return to Stock
mm_d said:
How? I'm from Ukraine, not from US. Besides that, I have some personal data stored on internal memory, that I cannot erase.
Click to expand...
Click to collapse
The process here: http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/ should clear up the Nook and return it to real stock. Once that is done, I have guides for installing CM7, CM9, or CM10 on the same site.
I have tried this method before, with no results
Yesterday afternoon I upgraded my C6802/Z Ultra to 14.4.A.0.108 aka 4.4.4 and to persuade the Sony PC Companion program on windows to download the update, I used flashtool to lock my bootloader.
I've used the phone happily all day but I want to root it so I can use Titanium Backup Root/Pro, and hack the platform.xml file so as to allow full use of the microSDHC card.
I went to the service menu with the *#*#7378423#*#* and it says my bootloader is unlockable. I then put the phone into fastboot mode and ran the unlock sequence, but it failed the first time and reported device already unlocked.
I am using the tools from the full Android SDK
Code:
$ ./fastboot -i 0x0fce getvar version
< waiting for device >
version: 0.5
finished. total time: 0.003s
$ ./fastboot -i 0x0fce oem unlock 0xXXXXXXXXXXXXXXXXXX
...
FAILED (remote: Command did not succeed)
finished. total time: 0.018s
$ ./fastboot -i 0x0fce oem unlock 0xXXXXXXXXXXXXXXXXXX
...
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
$ ./fastboot -i 0x0fce oem unlock 0xXXXXXXXXXXXXXXXXXX
...
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
So then I tried to flash Jackie's 108 Dual Recovery kernel and it failed; I tried again as root just to make sure:
Code:
# ./fastboot flash boot ~/download/android/sony/xperia_z_ultra/C68xx_kernel_108_DualRec_Jackie099.bin
sending 'boot' (17728 KB)...
OKAY [ 0.557s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.560s
I get the same result if I use FlashTool's built-in tools. I have tweaked the phone's configuration to allow/disallow USB ADB debugging, allow/disallow side-loading, verification of apps etc etc, makes no difference.
I suspect that the phone is falsely reporting its bootloader is already unlocked, but where do I go from here?
thanks for any ideas
Paul
first off you may have lost your DRM keys by not doing a TA backup before unlocking the bootloader.
try and flash doomkernel's boot.img and see if that works? (unpack the zip)
I think I can remember someone not beinf able to flash jackie's .bin but doomlord's boot.img worked?
blueether said:
first off you may have lost your DRM keys by not doing a TA backup before unlocking the bootloader.
try and flash doomkernel's boot.img and see if that works? (unpack the zip)
I think I can remember someone not beinf able to flash jackie's .bin but doomlord's boot.img worked?
Click to expand...
Click to collapse
thanks, I'll give the doomkernel a go.
I lost my DRM keys the same day I received my XZU.. what you've never used you don't miss
Looks like the problem that I had:
http://forum.xda-developers.com/xperia-z-ultra/help/reunlocking-bootloader-error-t2808395
Long story short, I tried to flash new rom on my Mt2-L02 mate2 and failed and its bootlooping (at Huawei Ascend screen and keep rebooting) now. using the SDcard udload to load new rom don't work either. I cannot go into recovery, or boot into system.
My phone is bootloader unlocked, so I tried to flash (extract from a rom) boot.img, recovery.img and is ok but when flashing system.img, it stucked in writing 'system'... for long time.... so I tried fastboot erase system -w and get FAILED (remote: Command not allowed)... why is it so? my phone is already unlocked. I tried unlock again and flash the system.img, same problem.
So... I'm screwed?
You're not screwed. Impatient maybe. Try on a different computer if you have one. If not, update drivers and try a different port on the existing computer. Are you flashing an MT2-L02 ROM?
kimtyson said:
You're not screwed. Impatient maybe. Try on a different computer if you have one. If not, update drivers and try a different port on the existing computer. Are you flashing an MT2-L02 ROM?
Click to expand...
Click to collapse
Only have 1 pc, yes, I'm flashing MT2-L02 ROM, tried alot of version but discovered only these version rom (b408, b603, b606, b607) able to write the system.img, original out of box android version for my phone is 4.4.2. but still bootlooping after flashing boot.img, recovery.img and system.img. I think only custom recovery can save now, but there is none for this model... or maybe there is no hope for my phone? Maybe my phone got some system modified lock so that I'm not able to erase using flashboot?
C:\adb>fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.001s
C:\adb>fastboot erase data
erasing 'data'...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.001s
If I'm able to erase those, I'm might solved the bootlooping problem..
Try using this thread as reference, http://forum.xda-developers.com/asc...to-fix-soft-bricked-phone-using-twrp-t2886630. It's for a different model so just use your stock ROM in place of the L03 ROM. I'm not sure how to help beyond that. There has to be a way to return to stock on the L02.
Maybe this message is late, pls try following
http://pan.baidu.com/s/1dDpc4eP
http://www.huaweirom.com/rom/mate2/2619.html
usb flash instructions:
http://www.huaweirom.com/guide/2621.html
You may need to use google translate since all the info is in Chinese
Basically they are saying you should use B117 if B4xx not working.
Hi,
I was trying to flash stock rom to my Moto E Indian version. It was running Cm 12 but suddenly it stopped detecting sim card. so I used this script to flash the stock firmware
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
pause
mfastboot.exe reboot
but flash wasnt successful and its now stuck at recovery loop. If I try to flash any custom rom from recovery it says unable to mound data and system. Tried everything I know but doesnt help.
when I flash the above script it shows CM boot logo and gets stuck there
Using this stock firmware RETAILDSDSALL_XT1022_4.4.4_KXC21.5-40_cid7_CFC
C:\MotoTool\ADB>"Retail+lock.bat"
C:\MotoTool\ADB>mfastboot.exe oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 0.089s]
finished. total time: 0.092s
C:\MotoTool\ADB>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.028s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.577s
C:\MotoTool\ADB>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1669 KB)...
OKAY [ 0.099s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.574s
C:\MotoTool\ADB>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (460 KB)...
OKAY [ 0.083s]
writing 'logo'...
OKAY [ 0.144s]
finished. total time: 0.233s
C:\MotoTool\ADB>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.391s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.101s
C:\MotoTool\ADB>mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.399s]
writing 'recovery'...
OKAY [ 1.757s]
finished. total time: 2.161s
C:\MotoTool\ADB>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (243072 KB)...
OKAY [ 7.676s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.348s
C:\MotoTool\ADB>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (257254 KB)...
OKAY [ 8.128s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.197s
C:\MotoTool\ADB>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (201709 KB)...
OKAY [ 6.381s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.447s
C:\MotoTool\ADB>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (46132 KB)...
OKAY [ 1.507s]
writing 'modem'...
OKAY [ 4.589s]
finished. total time: 6.101s
C:\MotoTool\ADB>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.012s]
finished. total time: 0.013s
C:\MotoTool\ADB>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.022s]
finished. total time: 0.025s
C:\MotoTool\ADB>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (649 KB)...
OKAY [ 0.106s]
writing 'fsg'...
OKAY [ 0.127s]
finished. total time: 0.237s
C:\MotoTool\ADB>mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.366s]
finished. total time: 0.369s
C:\MotoTool\ADB>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 1.415s]
finished. total time: 1.419s
C:\MotoTool\ADB>mfastboot.exe oem lock
...
(bootloader) sst lock failure!
OKAY [ 0.043s]
finished. total time: 0.046s
C:\MotoTool\ADB>pause
Press any key to continue . . .
C:\MotoTool\ADB>mfastboot.exe reboot
rebooting...
finished. total time: 0.002s
C:\MotoTool\ADB>
Hi, even I'm experiencing the same issue, it started after installing 2nd soak test. I tried downgrading but it showed few errors like you. Now my phone is stuck at 'M' logo, please let ne know if you have got any solution.
rizzee said:
Hi, even I'm experiencing the same issue, it started after installing 2nd soak test. I tried downgrading but it showed few errors like you. Now my phone is stuck at 'M' logo, please let ne know if you have got any solution.
Click to expand...
Click to collapse
Try the 5.1 factory images
please provide me the link of 5.1 if you have.
Here you go : Link
rizzee said:
please provide me the link of 5.1 if you have.
Click to expand...
Click to collapse
Why u all gave lock command at first?
Flashed with 5.1 stock image, now phone is booting in recovery mode and 'failed to validate system image' is flashing in pink color. Please help
rizzee said:
Flashed with 5.1 stock image, now phone is booting in recovery mode and 'failed to validate system image' is flashing in pink color. Please help
Click to expand...
Click to collapse
@abhi98228 You probably messed up the partitions. You ran useless commands which were not meant to be run. Never blindly download any script and run it without knowing what you are doing, be careful. Those unnecessary lock commands messed up your system. I don't know how to fix your partitions but try this.
Run each command ONE BY ONE in the order given below manually via command prompt. Don't download some stupid script from the internet and run it.
Code:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Now see if it works.
nilanko said:
@abhi98228 You probably messed up the partitions. You ran useless commands which were not meant to be run. Never blindly download any script and run it without knowing what you are doing, be careful. Those unnecessary lock commands messed up your system. I don't know how to fix your partitions but try this.
Run each command ONE BY ONE in the order given below manually via command prompt. Don't download some stupid script from the internet and run it.
Code:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Now see if it works.
Click to expand...
Click to collapse
tried, not working. it is the primary phone of my younger brother. if possible reach me on whatsapp 8986834888
rizzee said:
tried, not working. it is the primary phone of my younger brother. if possible reach me on whatsapp 8986834888
Click to expand...
Click to collapse
Sorry I was talking to the OP. Can you tell us what did you do just before this problem started? Which commands did u run?
nilanko said:
Sorry I was talking to the OP. Can you tell us what did you do just before this problem started? Which commands did u run?
Click to expand...
Click to collapse
phone was running on 5.0.x soak test 1, i downloaded soak test 2 and updated it with system update. Updating went fine, but the phone got stuck at 'M' Logo after booting. Tried recovery and cleared cache and restored factory but in vain. then I tried downgrading with stock firmware 4.4.4 but nothing happened. Phone was still getting stuck at 'M' logo while booting. then I downloaded the 5.1 stock firmware from the link given above, used the commands you mentioned every thing during the process went ok but after completion thing got worse. when I try to turn it on it enters fastboot mode directly and shows "failed to validate system image".
rizzee said:
phone was running on 5.0.x soak test 1, i downloaded soak test 2 and updated it with system update. Updating went fine, but the phone got stuck at 'M' Logo after booting. Tried recovery and cleared cache and restored factory but in vain. then I tried downgrading with stock firmware 4.4.4 but nothing happened. Phone was still getting stuck at 'M' logo while booting. then I downloaded the 5.1 stock firmware from the link given above, used the commands you mentioned every thing during the process went ok but after completion thing got worse. when I try to turn it on it enters fastboot mode directly and shows "failed to validate system image".
Click to expand...
Click to collapse
Okay, the thing I am going to tell you is extremely important... So listen to me carefully:
1) Download TWRP and flash it using fastboot flash recovery recovery.img
2) Now reboot into recovery from the bootloader mode
3) after entering TWRP, Select Wipe, Advanced Wipe and Select all Partitions EXCLUDING your SD Card
After that is done, go to the Home menu of TWRP and select Reboot, Power Off
A warning will come saying no OS is installed and to fix root etc... Select DO NOT INSTALL, and your phone will power off.
Now boot into the bootloader mode, and flash the 5.1 image i gave you, executing each command as @nilanko told you to.
I have attached TWRP below:
Download
Rohitagni said:
Okay, the thing I am going to tell you is extremely important... So listen to me carefully:
1) Download TWRP and flash it using fastboot flash recovery recovery.img
2) Now reboot into recovery from the bootloader mode
3) after entering TWRP, Select Wipe, Advanced Wipe and Select all Partitions EXCLUDING your SD Card
After that is done, go to the Home menu of TWRP and select Reboot, Power Off
A warning will come saying no OS is installed and to fix root etc... Select DO NOT INSTALL, and your phone will power off.
Now boot into the bootloader mode, and flash the 5.1 image i gave you, executing each command as @nilanko told you to.
I have attached TWRP below:
Click to expand...
Click to collapse
I'm confused which one to download and install, there are many different versions available.
rizzee said:
I'm confused which one to download and install, there are many different versions available.
Click to expand...
Click to collapse
I made a correctin to the previous post
rizzee said:
phone was running on 5.0.x soak test 1, i downloaded soak test 2 and updated it with system update. Updating went fine, but the phone got stuck at 'M' Logo after booting. Tried recovery and cleared cache and restored factory but in vain. then I tried downgrading with stock firmware 4.4.4 but nothing happened. Phone was still getting stuck at 'M' logo while booting. then I downloaded the 5.1 stock firmware from the link given above, used the commands you mentioned every thing during the process went ok but after completion thing got worse. when I try to turn it on it enters fastboot mode directly and shows "failed to validate system image".
Click to expand...
Click to collapse
You currently have the 5.0.2 booloader. Maybe your bootloader and gpt needs to be upgraded and since it's the old one, it's failing to validate the newer 5.1 system. This is just a wild guess. If it shows that message with a green dead android, its not the fastboot mode. That image is inside the logo.bin of the 5.1 system. So nothing has changed, you are still stuck at the logo only, the difference being, the old logo.bin didn't show that the system validation was failing but this time it's showing up because of the upgraded logo.bin that's it.
You should also try unlocking your bootloader, maybe that will bypass the validity checks for originality. After unlocking, try flashing the firmware again. If still doesn't work, you gotta be brave and flash motoboot.img and gpt.bin as well. I DO NOT TAKE ANY GAURANTEE AND PLEASE DON'T BLAME ME IF ANYTHING GOES WRONG AFTER FLASHING BOOTLOADER AND GPT. DO IT AT YOUR OWN DISCRETION. I JUST TOLD YOU ABOUT SOME POSSIBILITIES, NOT ASKING YOU TO FOLLOW THEM.
nilanko said:
You currently have the 5.0.2 booloader. Maybe your bootloader and gpt needs to be upgraded and since it's the old one, it's failing to validate the newer 5.1 system. This is just a wild guess. If it shows that message with a green dead android, its not the fastboot mode. That image is inside the logo.bin of the 5.1 system. So nothing has changed, you are still stuck at the logo only, the difference being, the old logo.bin didn't show that the system validation was failing but this time it's showing up because of the upgraded logo.bin that's it.
You should also try unlocking your bootloader, maybe that will bypass the validity checks for originality. After unlocking, try flashing the firmware again. If still doesn't work, you gotta be brave and flash motoboot.img and gpt.bin as well. I DO NOT TAKE ANY GAURANTEE AND PLEASE DON'T BLAME ME IF ANYTHING GOES WRONG AFTER FLASHING BOOTLOADER AND GPT. DO IT AT YOUR OWN DISCRETION. I JUST TOLD YOU ABOUT SOME POSSIBILITIES, NOT ASKING YOU TO FOLLOW THEM.
Click to expand...
Click to collapse
Maybe you're right... He does have the 5.0.2 bootloader... So, flashing the 5.1 gpt.bin won't do any harm.
At least that is what I think
Rohitagni said:
Okay, the thing I am going to tell you is extremely important... So listen to me carefully:
1) Download TWRP and flash it using fastboot flash recovery recovery.img
2) Now reboot into recovery from the bootloader mode
3) after entering TWRP, Select Wipe, Advanced Wipe and Select all Partitions EXCLUDING your SD Card
After that is done, go to the Home menu of TWRP and select Reboot, Power Off
A warning will come saying no OS is installed and to fix root etc... Select DO NOT INSTALL, and your phone will power off.
Now boot into the bootloader mode, and flash the 5.1 image i gave you, executing each command as @nilanko told you to.
I have attached TWRP below:
Download
Click to expand...
Click to collapse
Hi, I downloaded TWRP from the like you provided. Now, please guide me the steps to flash it.
rizzee said:
Hi, I downloaded TWRP from the like you provided. Now, please guide me the steps to flash it.
Click to expand...
Click to collapse
Rename the file you have downloaded to recovery.img (ignore the img part if it is already present).
Now go to the bootloader mode of your phone, and then connect to your computer.
Open up the command prompt and type in fastboot flash recovery recovery.img.
On your phone something will appear like Partition Size mismatch or something. Ignore it.
Then when you get the message "OKAY" in the command prompt, disconnect your phone and USING ONLY the Vol Down button navigate to Recovery and press vol up.... Now u should be greeted with the TWRP screen.
Do this and tell me....
Rohitagni said:
Rename the file you have downloaded to recovery.img (ignore the img part if it is already present).
Now go to the bootloader mode of your phone, and then connect to your computer.
Open up the command prompt and type in fastboot flash recovery recovery.img.
On your phone something will appear like Partition Size mismatch or something. Ignore it.
Then when you get the message "OKAY" in the command prompt, disconnect your phone and USING ONLY the Vol Down button navigate to Recovery and press vol up.... Now u should be greeted with the TWRP screen.
Do this and tell me....
Click to expand...
Click to collapse
failed bootloader preflash validation failed
rizzee said:
failed bootloader preflash validation failed
Click to expand...
Click to collapse
It won't work unless you unlock your bootloader.
http://forum.xda-developers.com/showthread.php?t=2753110
Hello. Today i tried to flash the phone to the stock ROM twice but it didnt work probably cause unlocked bootloader and custom recovery (TWRP).
So i brick the phone and now i cant access the rom or the recovery. All i can do is access the fastboot mode. I tried to install the new recovery through fastboot but it doesnt work.
I tried the twrp 3.0.2.0 and 3.0.1.0 for yuga.
Code:
C:\Users\Kubo\Downloads\platform-tools>fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (10704 KB)...
OKAY [ 0.342s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.347s
Tried various of commands that i found on google and this forum but nothing worked. I unlocked the bootloader before when i was installing various of custom roms. Could somehow stock rom affect the bootloader when i was flashing through flashtool ? I tried to only boot the recovery from the img, the command worked but the recovery did not boot.
Code:
C:\Users\Kubo\Downloads\platform-tools>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.341s]
booting...
OKAY [ 0.033s]
finished. total time: 0.378s
Tried to check the status of bootloader but the command is just showing ... and nothing happend. Tried to get the IMEI through fastboot getvar command but no output is given. Im desperate. Sorry for english not my native language. I'll appreciate all the help.