Related
hello everyone..
In serious need of help here and hope someone can help..
Due to the massive battery drain issue I have been having, I tried to flash the original stock rom on my nexus 7 and
things have gone downhill really bad..
in the past, I flashed using this guide (http://forum.xda-developers.com/showthread.php?t=1907796)
without any problems but last night.. I encountered errors when trying to flash the bootloader
and radio IMG files.. neeedless to say when it comes to flashing the rom in, it came out with errors and my nexus remain OS-less
the errors when trying to flash the bootloader and radio are
"failed (command write failed (Invalid Argument))"
can anyone help me?
p.s :- if anyone can even suggest me a easier way to flash custom roms in and so forth, your suggestion will be most welcomed..
also, I did try wug's rootkit plus the nexus 7 toolkit or something, both came out errors too when too do any flashing in relating to
the bootloader or system.. thanks
Why were you trying to flash the bootloader? Were you trying to update to 4.18?
Username invalid said:
Why were you trying to flash the bootloader? Were you trying to update to 4.18?
Click to expand...
Click to collapse
actually, my bootloader boots fine, it shows tilapia 4.18.
so does this mean I dont have to flash it?
if I dont have to flash the bootloader, do I have to flash the radio?
sorry, kind of a noob in these things..
Anyway, is it normal for the bootloader flash attempt to fail?
hamiksu said:
Anyway, is it normal for the bootloader flash attempt to fail?
Click to expand...
Click to collapse
No, it's not normal for it to fail.
You really don't need to flash either unless one of them is screwed up or you are upgrading to a newer version. Bootloader flashes are risky anyway. To avoid flashing them, you can either remove code from the updater script or remove them from the factory image files entirely.
korockinout13 said:
No, it's not normal for it to fail.
You really don't need to flash either unless one of them is screwed up or you are upgrading to a newer version. Bootloader flashes are risky anyway. To avoid flashing them, you can either remove code from the updater script or remove them from the factory image files entirely.
Click to expand...
Click to collapse
hmm, ok..
then I will go back home and do the system flashing and try and post out the errors it stated there..
really hope to get my nexus back on line...
This is what I get when I tried to flash the image
Hope someone can guide me on what to do next.
hamiksu said:
This is what I get when I tried to flash the image
Hope someone can guide me on what to do next.
Click to expand...
Click to collapse
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
ameinild said:
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
Click to expand...
Click to collapse
it says my bootloader is already unlocked
hamiksu said:
it says my bootloader is already unlocked
Click to expand...
Click to collapse
Then it sounds like something happened to your system partition that should not have happened.
Are you sure the system image you're trying to flash is valid, do the md5 sums match?
How about flashing another system image?
Or flash a custom recovery, and install a new ROM from there?
ameinild said:
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
Click to expand...
Click to collapse
ameinild said:
Then it sounds like something happened to your system partition that should not have happened. Sorry, can't help you there...
Click to expand...
Click to collapse
meaning my system partition is screwed?
anyone knows how to go around this problem?
p.s :- anyway ameinild, thanks for trying to help
hamiksu said:
p.s :- anyway ameinild, thanks for trying to help
Click to expand...
Click to collapse
I edited my post with some more suggestions to try first
ameinild said:
I edited my post with some more suggestions to try first
Click to expand...
Click to collapse
yup, the image i tried a few.. even tried stock rom image.
tried both nexus 7 toolkit
as well as wugs nexus root tool kit.
they all seem to encounter problems when trying to "push" the rom images in or something.
is there a way to like format the entire thing and install from scratch>?
hamiksu said:
is there a way to like format the entire thing and install from scratch>?
Click to expand...
Click to collapse
Sorry, I can't really find anything for the N7... Hope someone else can chime in.
ameinild said:
Sorry, I can't really find anything for the N7... Hope someone else can chime in.
Click to expand...
Click to collapse
Yea, I hope someone will pop in and be my guardian angel too..
Thanks again, Ameinild
tried to flash stock rom using wug's rootkit..
this is what happens...
hamiksu said:
tried to flash stock rom using wug's rootkit..
this is what happens...
Click to expand...
Click to collapse
As a rule, don't do anything with a toolkit that you don't know how to do yourself with the relevant fastboot or ADB commands. It has a nasty tendency of leaving you in a lurch.
I noticed that your last run of Wug's toolkit did claim to successfully flash your recovery. Have you been able to access it from the fastboot menu on the device? If so, that's a major step forward.
Perhaps most importantly (based on your mentioning of tilapia earlier), are you 100% certain that you are trying to flash the factory image for your model of the Nexus 7?
Rirere said:
As a rule, don't do anything with a toolkit that you don't know how to do yourself with the relevant fastboot or ADB commands. It has a nasty tendency of leaving you in a lurch.
I noticed that your last run of Wug's toolkit did claim to successfully flash your recovery. Have you been able to access it from the fastboot menu on the device? If so, that's a major step forward.
Perhaps most importantly (based on your mentioning of tilapia earlier), are you 100% certain that you are trying to flash the factory image for your model of the Nexus 7?
Click to expand...
Click to collapse
Yes, I am absolutely sure it is the image for my nexus 7.. which is 3g/wifi model, not just wifi only..
image file is downloaded using wug's rootkit too..
file name = nakasig-jdq39-factory-0798439d.tgz
as the snapshot shows.. it keeps showing failed when "sending system"
please tell me you have an idea on why it keeps failing there...
*crosses fingers*
p.s :- after that (numerous) wug's toolkit attempt to flash back stock rom, I tried booting to recovery and it shows the android on its back with a red exclamation mark on its open body chasis
I'm assuming you haven't tried this yet, if you have tried this just ignore.
1 - Download - http://techerrata.com/file/twrp2/grouper/openrecovery-twrp-2.6.0.0-grouper.img
2 - fastboot flash recovery openrecovery-twrp-2.6.0.0-grouper.img
If flashes fine:
Power off Nexus, Hold Volume down and Power on, keep holding power down until you get to recovery.
Then:
Either - Get a USB OTG and put a ROM on a USB Stick, go to "install" - "Use external storage" find the rom and flash it.
or
Plug in to PC whilst in recovery, - Mount Storage - Now the Nexus should pop up on PC, Drag ROM to Nexus. Unmount and then try to flash.
Let me know how you get on with this.
Regards.
hamiksu said:
Yes, I am absolutely sure it is the image for my nexus 7.. which is 3g/wifi model, not just wifi only..
image file is downloaded using wug's rootkit too..
file name = nakasig-jdq39-factory-0798439d.tgz
as the snapshot shows.. it keeps showing failed when "sending system"
please tell me you have an idea on why it keeps failing there...
*crosses fingers*
p.s :- after that (numerous) wug's toolkit attempt to flash back stock rom, I tried booting to recovery and it shows the android on its back with a red exclamation mark on its open body chasis
Click to expand...
Click to collapse
That's because you have stock recovery installed now and it's unable to verify that your device is in working order, hence the red mark. Find TWRP for your device, download the .img and try to flash it with fastboot flash recovery <path-to-recovery.img>. Since you can at least get into a recovery, it's possible you'll be able to use onboard recovery tools to see what state your internal partitions are in.
Until there's a little more info available, there's nothing I can say that's not pure conjecture.
I have a Nexus 4, 4.3 JWR66V , Stock ROM and on Franco's Kernel currently and am looking to OTA update to later builds and eventually KitKat.
I've got the OTA requests on my phone and am trying to return to STOCK (following Efrant's guide and other threads) so I can apply them. But I can't find a stock Kernel for JWR66V? There is one for JWR66Y which I understand should work, however when I load it to Boot (using WugFresh Nexus Toolkit) my phone does not switch on fully (blank screen).
Can you please point me in the direction of a JWR66V stock kernel that will work or help me figure out what I'm doing wrong?
Thanks!:good:
devesh254 said:
I have a Nexus 4, 4.3 JWR66V , Stock ROM and on Franco's Kernel currently and am looking to OTA update to later builds and eventually KitKat.
I've got the OTA requests on my phone and am trying to return to STOCK (following Efrant's guide and other threads) so I can apply them. But I can't find a stock Kernel for JWR66V? There is one for JWR66Y which I understand should work, however when I load it to Boot (using WugFresh Nexus Toolkit) my phone does not switch on fully (blank screen).
Can you please point me in the direction of a JWR66V stock kernel that will work or help me figure out what I'm doing wrong?
Thanks!:good:
Click to expand...
Click to collapse
Download Nexus Factory Images and flash it.
mohitgalaxy3 said:
Download Nexus Factory Images and flash it.
Click to expand...
Click to collapse
Thanks mate - again I'm struggling to find the Nexus factory images for JWR66V - I can only seem them for JWR66Y and this boot.img didn't work for me.
Flash the JWR66Y images... system, boot, recovery, radio, and bootloader. As long as you don't flash the userdata.img, your data won't get wiped.
chrisbo4 said:
Flash the JWR66Y images... system, boot, recovery, radio, and bootloader. As long as you don't flash the userdata.img, your data won't get wiped.
Click to expand...
Click to collapse
Ok thanks mate...going to try that right now and report back.
Are you (or anyone else) familiar with the Wug Fresh Nexus Root Toolkit? Is the Boot/Flash image utility in this a good way to flash images? The Boot image option lets you preview the .img and then reverts back to the old one upon reboot - sounds good to me but anything I should check/be wary of when using this?
devesh254 said:
Ok thanks mate...going to try that right now and report back.
Are you (or anyone else) familiar with the Wug Fresh Nexus Root Toolkit? Is the Boot/Flash image utility in this a good way to flash images? The Boot image option lets you preview the .img and then reverts back to the old one upon reboot - sounds good to me but anything I should check/be wary of when using this?
Click to expand...
Click to collapse
I have used Wug's toolkit in the past, however it bootlooped my device. I'm sure it was user error, but anyway decided to learn adb and fastboot. Long story short... no I'm not familiar with the toolkit, even though I used it once before. Any luck with flashing the images?
chrisbo4 said:
I have used Wug's toolkit in the past, however it bootlooped my device. I'm sure it was user error, but anyway decided to learn adb and fastboot. Long story short... no I'm not familiar with the toolkit, even though I used it once before. Any luck with flashing the images?
Click to expand...
Click to collapse
Ok thanks - have just refamiliarised with adb and fastboot now, and am mid way through flashing those img files! Shall update shortly
devesh254 said:
Ok thanks - have just refamiliarised with adb and fastboot now, and am mid way through flashing those img files! Shall update shortly
Click to expand...
Click to collapse
have flashed all of those files using adb fastboot - still says my kernel is the franco one though?!
i noticed after i flashed all of those files (the boot one being the last) that it rebooted with a blank screen. i then have to switch off, switch on, it turns on as normal but shows the kernel is still the same in settings.
just to check i am doing this right - i put the phone in fastboot mode and through a cmd prompt, flash each img one at a time. is there a way to flash them all at once? i suspect not all of them are flashing...
You can flash the "flashall.bat", that will flash all of the images in one command. That's strange that flashing the boot.img doesn't overwrite the franco kernel. Perhaps try to "fastboot reboot-bootloader" between each .img.
Hmm
Ok I managed to flash all the files now...bootloader radio boot recovery and system - but my phone is not switching on. It get's stuck at the Nexus X logo and doesn't go beyond that!
Any ideas please?
Update - just went in to the stock recovery and wiped cache too....seem to be stuck on the X but it says "Android is Upgrading too"....hopefully this will work now!
Good news - it all worked! Clearing the cache did the trick and I have now OTA'd all the way to 4.4.2!
Thanks for your help mate and everyone else :good::laugh:
So I flashed the 7.1.1 update and everything was fine. I then tried to root through TWRP with the most recent version of recovery and and SuperSu and when I went to reboot it would get to the "Google" splash screen and go back to the warning. I then tried to restore to my Nandroid that I made right before the 7.1.1 flash but it does the same thing. I ended up doing a factory reset, still looping. I tried flashing an old firmware but it still would loop. I got desperate and did a full wipe and then flashed the old firmware from September's update but it still will not boot. I'm a long time lurker I just don't post much. Any help will be appreciated. Thanks in advance!
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
jamaniek said:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
Click to expand...
Click to collapse
Ahh, great. I tried searching to see if anyone else posted anything, couldn't find it.
jamaniek said:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
Click to expand...
Click to collapse
Wait are you able to get into Recovery?
ChazLanier said:
Wait are you able to get into Recovery?
Click to expand...
Click to collapse
Nope. And so are other folks.
But if you can, there's still hope to save your device.
What version of twrp were you using?? Also what company makes the storage (not memory) on your device?
jamaniek said:
Nope. And so are other folks.
But if you can, there's still hope to save your device.
Click to expand...
Click to collapse
I can still get into recovery. I just can't get it past the Google splash screen.
ChazLanier said:
I can still get into recovery. I just can't get it past the Google splash screen.
Click to expand...
Click to collapse
Have you tried installing custom ROM, instead of a stock one?
And tell us what @ArminasAnarion asked for. There may be a pattern here. :good:
I haven't tried a custom ROM. I'll try that if I get any down time at work. Also, I'll check for you @ArminasAnarion in a bit.
Might be a noob question, but how do I get the custom rom files over to my phone to flash in recovery?
ChazLanier said:
Might be a noob question, but how do I get the custom rom files over to my phone to flash in recovery?
Click to expand...
Click to collapse
Well if you cant access twrp then your not flashing anything; did you try downloading the latest Nexus 6p factory image and using adb to flash it?? If you need help with that I can lay it out for you. Also there was an efs partition issue with twrp 3.0.2-1 and down so make sure your twrp is 3.0.2-2!
ArminasAnarion said:
Well if you cant access twrp then your not flashing anything; did you try downloading the latest Nexus 6p factory image and using adb to flash it?? If you need help with that I can lay it out for you. Also there was an efs partition issue with twrp 3.0.2-1 and down so make sure your twrp is 3.0.2-2!
Click to expand...
Click to collapse
I can access TWRP. I haven't tried the latest factory image, only September's release. I just tried a custom rom and it gets to the Google screen but then loops just after the G starts to animate.
ChazLanier said:
I can access TWRP. I haven't tried the latest factory image, only September's release. I just tried a custom rom and it gets to the Google screen but then loops just after the G starts to animate.
Click to expand...
Click to collapse
Make sure your using twrp 3.0.2-2; and download the latest factory image for the Nexus 6p (NBD90X) and use adb (fastboot) to flash that whole thing. Extract the files to your android sdk platform tools folder then run the flash-all.bat file. (If you are using a 64gb or 128gb device DONT DO THIS) Only do this with the 32gb model. If its a 64 or 128 model go here -> http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and go to sub section 10. How To Flash The Factory Images (And Return To Stock) (On post two) and follow that.
ArminasAnarion said:
Make sure your using twrp 3.0.2-2; and download the latest factory image for the Nexus 6p (NBD90X) and use adb (fastboot) to flash that whole thing. Extract the files to your android sdk platform tools folder then run the flash-all.bat file. (If you are using a 64gb or 128gb device DONT DO THIS) Only do this with the 32gb model. If its a 64 or 128 model go here -> http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and go to sub section 10. How To Flash The Factory Images (And Return To Stock) (On post two) and follow that.
Click to expand...
Click to collapse
Downloading the image now. I'm familiar on how to flash stock images, they're how I usually do all of my updates.
ChazLanier said:
Downloading the image now. I'm familiar on how to flash stock images, they're how I usually do all of my updates.
Click to expand...
Click to collapse
Oh okay cool! Good luck!
ArminasAnarion said:
What version of twrp were you using?? Also what company makes the storage (not memory) on your device?
Click to expand...
Click to collapse
Samsung storage, and I thought I was on -2 but it seems like I was on -1.
ArminasAnarion said:
Oh okay cool! Good luck!
Click to expand...
Click to collapse
Newest image didn't work either..
Have you tried WugFresh's Nexus Root Toolkit? Not sure if it will work for your situation, but it has an option to restore to factory settings and unroot if you're soft-bricked or bootlooped. Might be worth a shot if everything else isn't working.
FWIW, I successfully updated to 7.1.1 NPF10C and rooted by using fastboot to flash bootloader, radio, boot, system, and vendor. Then used TWRP 3.0.2-2 to flash SuperSU 2.78 SR1. No issues.
Howie Dub said:
Have you tried WugFresh's Nexus Root Toolkit? Not sure if it will work for your situation, but it has an option to restore to factory settings and unroot if you're soft-bricked or bootlooped. Might be worth a shot if everything else isn't working.
Click to expand...
Click to collapse
No luck on this either.
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
nhatminhng said:
Hey guys, I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Fastboot format your partitions and use flash-all.bat with a stock Google image.
nhatminhng said:
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
MidnightDevil said:
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
jhs39 said:
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
Click to expand...
Click to collapse
v12xke said:
Fastboot format your partitions and use flash-all.bat with a stock Google image.
Click to expand...
Click to collapse
Thanks guys for helping. I fixed it.
I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
nhatminhng said:
Thanks guys for helping. I fixed it. I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
Click to expand...
Click to collapse
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
v12xke said:
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
Click to expand...
Click to collapse
Yes sir of course I read it. But I dont understand this step.
Open a terminal and navigate to the unzipped system image directory.
Click to expand...
Click to collapse
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
nhatminhng said:
Yes sir of course I read it. But I dont understand this step.
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
Click to expand...
Click to collapse
Hi... Here's a pretty good detailed process on how to unlock/flash, etc...
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page549
Also, before using any toolkit, I suggest using manual commands and getting comfortable with it. At least, you learn exactly what command do what! Simply pressing a button in a program may result in a bricked device. Plus with command line you learn something. :good:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
tjchuot287 said:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
Click to expand...
Click to collapse
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
nhatminhng said:
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
Click to expand...
Click to collapse
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
tjchuot287 said:
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
Click to expand...
Click to collapse
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes i can. I tried to sideload multiple version of OTA but all have failed.
tjchuot287 said:
Yes i can. I tried to sideload multiple version of OTA but all have failed.
Click to expand...
Click to collapse
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
v12xke said:
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
Click to expand...
Click to collapse
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Click to expand...
Click to collapse
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
v12xke said:
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
Click to expand...
Click to collapse
Now i have unlocked bootloader but the phone keep restart and stuck at logo again. i followed @Heisenberg thread but same result.
I had unlocked my bootloader and then tried to flash twrp. I was unsuccessful to do that. That softbricked my phone and I had to flash stock rom via Mfastboot. Not this is the message I get
Code:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: N/A
I have no idea what to do. I went to the service centre and I was told that it might be motherboard problem and that would cost me Rs10,000. I can buy a new phone for that. Someone please help me. I am phone less since past 3 months.
P.S: I can boot into the recovery (the one we do wit power button + volume down, that is the best I can do with my phone right now) I SERIOUSLY NEED HELP!!!
Yes, nothing to do about it. Just flash a new picture to cover it.
If nothing works just reinstall stock or try putting a .zip rom on your device and flash that in recovery.
@clever_idiot
first of all, i think service center guy is making you fool...
If you Re-Lock bootloader again, it will disappear and that cost 1GB data for downloading Stock ROM and few Minutes.
Better than Re-Locking, (in addition to 2nd reply)
You can create your own Logo image to put over that message or you can flash available on link.
Following link contains everything you need to know.
https://forum.xda-developers.com/moto-g4-plus/themes/guide-t3588090
Azerox said:
Yes, nothing to do about it. Just flash a new picture to cover it.
If nothing works just reinstall stock or try putting a .zip rom on your device and flash that in recovery.
Click to expand...
Click to collapse
Thanks you for the reply, I did cover it with a stock image of moto logo, still the device wint boot up, I also flashed the stock rom, yet it didnt boot up
clever_idiot said:
Thanks you for the reply, I did cover it with a stock image of moto logo, still the device wint boot up, I also flashed the stock rom, yet it didnt boot up
Click to expand...
Click to collapse
Which ROM you flashed ?
June's security update [ 7.0_NPJS25.93-14-8 ] causes many problems.
____Mdd said:
@clever_idiot
first of all, i think service center guy is making you fool...
If you Re-Lock bootloader again, it will disappear and that cost 1GB data for downloading Stock ROM and few Minutes.
Better than Re-Locking, (in addition to 2nd reply)
You can create your own Logo image to put over that message or you can flash available on link.
Following link contains everything you need to know.
https://forum.xda-developers.com/moto-g4-plus/themes/guide-t3588090
Click to expand...
Click to collapse
I tried everything man, I flashed the stock rom twice with two different methods, non of them worked, its just shutting down and booting and stops at "this device has been unlocked..."
____Mdd said:
Which ROM you flashed ?
June's security update [ 7.0_NPJS25.93-14-8 ] causes many problems.
Click to expand...
Click to collapse
Stock ROM
clever_idiot said:
Stock ROM
Click to expand...
Click to collapse
I mean which version of STOCK ROM ?
And also check if all things are getting installed correctly (better to skip flashing of gpt and bootloader ).
Are you able to boot into bootloader ?
____Mdd said:
I mean which version of STOCK ROM ?
And also check if all things are getting installed correctly (better to skip flashing of gpt and bootloader ).
Are you able to boot into bootloader ?
Click to expand...
Click to collapse
This version of ROM :- Moto_G4_Plus_XT1643_ATHENE_MPJ24.139-63
and yeah I can boot into the ****ty bootloader
clever_idiot said:
This version of ROM :- Moto_G4_Plus_XT1643_ATHENE_MPJ24.139-63
and yeah I can boot into the ****ty bootloader
Click to expand...
Click to collapse
So you were flashing the Marshmallow fastboot ROM? What OS did you have before when you were flashing TWRP?
echo92 said:
So you were flashing the Marshmallow fastboot ROM? What OS did you have before when you were flashing TWRP?
Click to expand...
Click to collapse
nougat
@clever_idiot echo92 is asking for version of nougat you had before flashing TWRP,
If don't remember, then simply answer this
When was you last updated your phone by OTA ?
Is it last 2 months ?
____Mdd said:
@clever_idiot echo92 is asking for version of nougat you had before flashing TWRP,
If don't remember, then simply answer this
When was you last updated your phone by OTA ?
Is it last 2 months ?
Click to expand...
Click to collapse
it was 7.0
clever_idiot said:
I tried everything man, I flashed the stock rom twice with two different methods, non of them worked, its just shutting down and booting and stops at "this device has been unlocked..."
Click to expand...
Click to collapse
First, simply flash the stock rom via. fastboot made.
Then let the phone power on fully ->enable developer option-> enable oem unlock
Then , again flash stock rom by "OEM LOCK.bat" file .
sujeet_kumar said:
First, simply flash the stock rom via. fastboot made.
Then let the phone power on fully ->enable developer option-> enable oem unlock
Then , again flash stock rom by "OEM LOCK.bat" file .
Click to expand...
Click to collapse
No luck bro
now the bootloader warning is gone. I am stuck with the MOTO "M' Logo in boot loop
echo92 said:
So you were flashing the Marshmallow fastboot ROM? What OS did you have before when you were flashing TWRP?
Click to expand...
Click to collapse
No luck bro
now the bootloader warning is gone. I am stuck with the MOTO "M' Logo in boot loop
clever_idiot said:
No luck bro
now the bootloader warning is gone. I am stuck with the MOTO "M' Logo in boot loop
Click to expand...
Click to collapse
How long does your device take on the 'M' logo before it bootloops? Is this with the NPJS25.93-14-8 firmware that you're running? What happens if you press the power and volume down keys together, so you boot to the bootloader and then select 'boot to recovery'? Also, do you have a SD card present in your device?
Hmm, with the re-locking, what's your plan afterwards? I'm not sure if you can unlock now, are you going to try to claim service with a re-locked bootloader?
echo92 said:
How long does your device take on the 'M' logo before it bootloops? Is this with the NPJS25.93-14-8 firmware that you're running? What happens if you press the power and volume down keys together, so you boot to the bootloader and then select 'boot to recovery'? Also, do you have a SD card present in your device?
Hmm, with the re-locking, what's your plan afterwards? I'm not sure if you can unlock now, are you going to try to claim service with a re-locked bootloader?
Click to expand...
Click to collapse
It takes around 1 second or less than that to reboot. When I select the recovery mode options it starts bootlooping. I used this ROM: ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml .zip . Yes I do have a SD card present in my phone RN. No I dont wish to go to the service centre guys they are far from my place.
clever_idiot said:
It takes around 1 second or less than that to reboot. When I select the recovery mode options it starts bootlooping. I used this ROM: ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml .zip . Yes I do have a SD card present in my phone RN. No I dont wish to go to the service centre guys they are far from my place.
Click to expand...
Click to collapse
Try taking the SD card out and see if you can boot then.
echo92 said:
Try taking the SD card out and see if you can boot then.
Click to expand...
Click to collapse
Nope, still loops till eternity