i dont know what i did..i was trying to unlock the bootloader and root my n4 but it came to an end that the only way to boot into android is if i fastboot boot boot.img..if i reboot my n4 it will get stock in bootloop and one more thing..by accident i deleted mms.apk and now it is no where to be found..the only way is to flash the whole rom?
If all you did was fastboot oem unlock and fastboot boot boot.img, then all you should have to do is reboot the phone. It will take a minute to boot since you wiped your data when you unlocked the bootloader
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Related
So I used the Nexus Root Toolkit to flash stock and unroot it, but after using it, I got stuck at the bootloader screen. So I pushed the start button to reboot, and my nexus 7 is still rooted. Help plz?
Give it a try again? I have use this 5 times, work great for me, u have adb fastboot mode on ur desktop?
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Download the stock image and flash in fastboot .
Sent from my Nexus 7 using xda premium
So when i try to fastboot the bootloader .img manually, it says:
sending bootloader ... okay
'writing bootlader'.... failed (remote: (invalid state))
so what do i need to do to fix that?
zeiloz said:
So when i try to fastboot the bootloader .img manually, it says:
sending bootloader ... okay
'writing bootlader'.... failed (remote: (invalid state))
so what do i need to do to fix that?
Click to expand...
Click to collapse
Is your bootloader locked?
Sent from my Nexus 7 using xda premium
it said lock status: unlock
So i would presume its unlocked...
zeiloz said:
it said lock status: unlock
So i would presume its unlocked...
Click to expand...
Click to collapse
OK. I've never seen that error before. And a quick google search doesn't come up with anything either.
You could try restarting the bootloader with
Code:
fastboot reboot-bootloader
and trying again.
The only thing I can think of is you could be trying to flash the wrong bootloader (which i doubt) Just to confirm you are trying to flash bootloader-grouper-3.34.img
Also, to just unroot you don't need to reflash the bootloader. Just boot.img and system.img
El Daddy said:
OK. I've never seen that error before. And a quick google search doesn't come up with anything either.
You could try restarting the bootloader with
Code:
fastboot reboot-bootloader
and trying again.
The only thing I can think of is you could be trying to flash the wrong bootloader (which i doubt) Just to confirm you are trying to flash bootloader-grouper-3.34.img
Also, to just unroot you don't need to reflash the bootloader. Just boot.img and system.img
Click to expand...
Click to collapse
Yes, I am trying to flash bootloader.grouper-3.34.img
And Im flashing bootloader because its I'm told to do in this thread? http://forum.xda-developers.com/showthread.php?t=1781250
I will try what you told me and see if it will work
So i rebooted the bootloader, and it still gives me the same thing. Whats the command to boot.img and system .img?
zeiloz said:
So i rebooted the bootloader, and it still gives me the same thing. Whats the command to boot.img and system .img?
Click to expand...
Click to collapse
Both the boot.img and the system.img are in the image-nakasi-jro03d.zip you must extract them first.
Then run: fastboot devices (to make sure you're connected) if it returns the serial number then proceed.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot erase cache
fastboot reboot
This should maintain your data and unroot your nexus.
However, I am a bit concerned about the invalid state error. I can't find anything about it at all. I'm worried your nand might be corrupted and proceeding with this might lead to an unrecoverable state. Maybe someone else can weigh in on this... I don't want to scare you but I don't want to be responsible if something goes wrong.
hmm... I hope more people would weigh in on this? Cuz im exchanging the nexus 7 due to flickering screens, and im new to the rooting/unrooting stuff so i dont want to brick this device cuz im a n00b.
hmm... I hope someone else weigh in on this to help, cuz I'm going to exchange this nexus 7 for another 1 because of flickering issues...
Restart, carefully check
My nexus had the ghosting issue and I had to unroot my device to ship back today. Heres how I did it.
1. Download stock ROM from Google.
2. Unzip stock ROM from Google. The unzipped file will have 4 files in it. (Boot loader grouper image, flash all.sh, flash base.sh and the image.zip)
3. Unlock your device by clicking the unlock button on nexus root toolkit
4. When your device wakes turns on set it back up. No need to log into Google.
5. turn a dB back on in development
6. Click flash stock + unroot
7. click other/browse
8. For choice click I did this already.
9. Click OK
10. browse to your unzipped file location with the 4 files in it.
11. click OK
12. Done
Sent from my Desire HD using xda premium
I'm facing a similar problem.
http://forum.xda-developers.com/showthread.php?p=31128926
Did you find a way to flash the Bootloader?
I'm thinking about a hardware issue as well. Are there any Devices, with corrupted NAND's known?
Marcus
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
helo friends i need help.i just wanna know how can i unroot and relock the boot loader of my nexus 4 if i want to send to for replacement.i used the Mskips toollkit to root and unlock the boot loader and i know that there is a option to relock and unroot but can someone plz explain me the full procedure properly.
Flash the stock image following this guide: http://forum.xda-developers.com/showthread.php?t=2010312
Then to lock use the command: fastboot oem lock
Sent from my Nexus 4 using xda premium
Hi i had some problem too had just solve it.
I pushed Stock Rom then i had tried re lock. But toolkit couldnt do it.
Then i pushed stock recovery too then toolkit locked my phone...
Hi guys,
In front of me, I have my friend's very stubborn LG Nexus 4. It's about 7 months old and a month ago, he dropped it and cracked the screen's glass (and the case's glass back as well). The phone still worked fine for a few weeks after that after that, but the touchscreen was not always responding correctly. He decided to give it to a service center for repair, but they returned it in a few days claiming there's a bootloop and they won't repair it (even if he paid) since the phone wasn't purchased in the same country. (Such BS, isn't it?)
An easy thing to fix, I thought, after fixing all sorts of bootloops on my SGT, SGS1 and my other friend's SGS2. Turns out, it's anything but.
Regardless of whether I flash stock following this guide or CM11 following the CM wiki, the phone is stuck on boot animation. 4 swirling colored balls for stock or an arrow rotating aroud Cid in case of CM11.
I have tried both stock recovery and CWM. I have tried wiping cache, data, Dalvik cache, any combination of only one or two or all three, tried waiting for an hour on first boot (someone suggested the first boot can take up to 15 minutes... find that hard to believe since even my sluggish SGS1 will manage in 3 minutes tops after a flash, but still tried) - all in vain. All I get is the screen's backlight level suddenly jumping up about 5 minutes into the boot process, as if the "Welcome to Android!" menu is about to appear - but it's still bootlooping until the battery runs out. (It gets quite warm too.)
TL;DR Nexus 4 flashes successfully with both stock 4.4.2 and CM11 but bootloops no matter what.
What can I do at this point to troubleshoot it? I'm out of ideas.
Its possible that this is a hardware issue but for now what I would try is download latest stock, Google search
android factory images
And choose the latest for your device, KOT49H
Now boot to fastboot
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now
fastboot flash bootloader nameofbootloader.img
fastboot flash radio nameofradio.img
Now either double click the flashall.bat or I prefer just extracting the rest an manual flash
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
Now
fastboot reboot
If this doesn't work than a good chance of hardware issue from all the falls, if it does work then my guess is you want to root it so go back to fastboot and flash the latest twrp or cwm recovery
Then either boot to recovery and flash su or wipe all and flash a custom ROM
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Its possible that this is a hardware issue but for now what I would try is download latest stock, Google search
android factory images
And choose the latest for your device, KOT49H
Now boot to fastboot
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now
fastboot flash bootloader nameofbootloader.img
fastboot flash radio nameofradio.img
Now either double click the flashall.bat or I prefer just extracting the rest an manual flash
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
Now
fastboot reboot
If this doesn't work than a good chance of hardware issue from all the falls, if it does work then my guess is you want to root it so go back to fastboot and flash the latest twrp or cwm recovery
Then either boot to recovery and flash su or wipe all and flash a custom ROM
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As I said, I've already tried CWM, custom ROM (CM 11 - which required rooting, which I did) and followed the guide I linked for flashing the latest stock ROM I got from Google. The only thing I haven't tried is the fastboot erase commands - thanks for suggesting that, I will try them ASAP before trying to flash stock again though I don't have much hope left
Give it a shot, if you do everything in this order you will be good if its a software issue, if it doesn't work than possibly hardware
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hi everyone !
My phone has recently shown a defect on the lower border of the touch screen. It's still less than one year so I will send it to google.
The thing is I have cyanogenmod installed, rooted etc. I am planning the restore the phone as it was brand-new: original rom, kernel...
I Have followed everything on the first comment of this post:http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Do you think that will be enough or I have to do something more in order to they won't realise i changed anything ?
Thank you all !
Last time I have sent my N4, I just restore the Stock Rom / Kernel, and lock the bootloader. Didn't have any issue.
Best advice would be to
Boot to recovery and make a full backup
Transfer this and anything else you want to PC
Reformat all in recovery (including SD data)
If you want to go overboard then format all with fastboot like such
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Then flash latest stock firmware through fastboot (run the flashall.bat)
Then lock bootloader
fastboot oem lock
Reboot , power off, send in for rma
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Best advice would be to
Boot to recovery and make a full backup
Transfer this and anything else you want to PC
Reformat all in recovery (including SD data)
If you want to go overboard then format all with fastboot like such
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Then flash latest stock firmware through fastboot (run the flashall.bat)
Then lock bootloader
fastboot oem lock
Reboot , power off, send in for rma
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks man ! the only problem is that I don't know how to block my bootloader because I am not longer root user
"fastboot oem lock"
Don't need root, just connect the phone to your PC in fastboot mode and fire that command.
Sent from my Nexus 4 using XDA Free mobile app
Hello.
Long story short:
I have a OnePlus2, I can boot in Fastboot mode and my PC does recignize the fastboot device.
fastboot oem device-info says that Bootloader is locked and when I try to unlock (fastboot oem unlock) it states "okay" but cannot boot into system because there is none installed. -> Bootloop
I cannot boot into recovery nor install a recovery due to the locked bootloader.
My Question:
Is there a way to unlock the bootloader in fastboot and/or install a boot.img?
I am happy for any help that I get.
Have a good day/night
SoulSnatcher
No, but why you don't have system?
You have stock recovery download official signed full zip and flash it. Recovery.
Also unbrick guide using the one you need Qualcomm drivers
Sent from my ONE A2005 using Tapatalk