Hi,
I am trying in vain to fix my friend's Nexus 4. She started having problems with a boot loop around the same time as 4.4.3 (I think) but it just went away. Two days ago it came back, possibly around the time of 4.4.4 seeding, however this time it won't go away. I have been looking at threads throughout XDA for help and tried this thread for help. I have a GS4 myself and very little experience with ADB/SDK.
All efforts have failed. As well as the boot loop issue, recovery is broken limiting my options. I tried the "not lose any data" method in the link above but this didn't work. Next the Nexus Root Toolkit, however most of the time the program fails as it says the download failed due to an MD5 mismatch. I have tried downloading the images directly from Google but still no luck - of all the 4.X images available only a couple will even allow me to try and install.
The first install didn't install, I noticed it mentioned the bootloader been locked several times - it recommended 'force flashing' providing I definitely have the right image. Several attempts later I managed to get the install working but it is still stuck on a boot loop (waited at least 15 minutes). Recovery is still broken. The only thing I have been able to do is unlock the bootloader.
So is there any hope? The device is pure stock, no alternative custom recovery or ROMs. Thanks.
I think half the problem is I can't the USB drivers installed properly as the device isn't showing in Device Manager. Without been able to turn on the phone or enable USB Debugging, it won't let me.
EDIT - I tried another toolkit and eventually managed to get 4.2.2 installed. I have just updated the phone to 4.3 but it's been on the Google X screen for a while now
EDIT 2 - Fixed the above. I needed to downgrade the radio. Updating to 4.4 - no doubt I will go through the same hurdles.
EDIT 3 - An error occurred during installation.
Related
Hello there everyone.
First off, I know this might seem like a subject that's already been covered. Trust me, I've spent the last few days going through every thread I could find on here trying everything out as well as other threads on tips on the net. So I'm posting this because I've tried everything and run out of troubleshooting methods to have a go with. The experts here may relish the challenge of solving this one. Or tear their hair out just like I'm doing. Hence my username. I'm worn out after countless hours of doing this.
Background:
I had a rooted Nexus 7 with superuser and TWRP. Jellybean 4.2.1 update would never work, always got an assert failed or some other error when it tried to do so. I then decided to go back to a previous backup in case something had gone wrong since in order to get on with installing the update.
Previous backup loaded fine. Unfortunately WiFi was not working and just kept on searching forever. After lots of googling and trying all the fixes with my router and so on which failed to solve anything, took the advice of going back to a factory reinstall.
Reinstalled, booted up, selected language on Google Welcome Screen then onto Wifi screen. Stuck on seaching forever. More googling and took advice. Decided to do Nexus Root Toolkit's flash stock+unroot to get back to clean state. After install there's an issue that just won't go away and that is:
Problem:
Google Nexus 7 (Wifi model) won't go past Google screen (this is not the coloured logo, just the word "Google" in white).
Associated problems:
Going into recovery just shows the same screen or sometimes an android lying on its back with a red triangle.. So no stock recovery available. Using fastboot to lock and unlock the bootoader as a recommended fix has no apparent effect with the result just being the same Google screen (padlock icon unolocked or locked depending upon locking status) even after a long wait.
Flash stock+Unroot in Nexus Root Toolkit has the same result. I left the thing on for a long time each time after a factory install because of advice saying to wait and still the same screen all that time. Longest time was 6 hours left on due to frustration and waiting to see if anything at all would happen. It didn't.
I can't access ADB in bootloader. I can only access ADB when the device is in TWRP or CWM menus. (In other words Nexus Root Toolkit complains it can't connect when I'm in the bootloader for example if I want to do any operation that requires ADB, but doesn't complain when in in those two recovery menus). Nexus Toolkit will quite happily do the Flash stock+ unroot and get to the screen where it says wait a while for device to reboot and you can press any key to exit.
I have wiped system, cache, boot, recovery, userdata using both fastboot and JROM Flasher. I can install TWRP or CWD using the Nexus Toolkit and wipe stuff using those but still no joy. I have gone through every permutation many times step by step. I have even used different Jellybean factory images from 4.1.0 to 4.2.1 as well as past backups with the same result each time.
Have used soft bricked and device is on options in Roolkit. No joy.
I have also disconnected the battery as part of the troubleshooting process.
Basically, nothing I can do using the information I've been able to get hold of can get past that screen.
Other quirks:
I have also noticed when installing a factory image a message comes up:
writing bootloader FAILED (remote: (invalid state))
It continues with the rest of the installation however as normal.
Also PdaNet comes up with the message:
Wrong WinUSB Pipes found
If I try Connect Internet (USB) option.
I have downloaded Nexus 7 tablet USB driver revision R06 and tried to use them but my PC will only recongise the device as an MTP device with failed driver install when the tablet is in that endless Google screen.
With the install of the Naked Universal Driver it only recognises the device in the Device Manager as Google Nexus 7 Bootloader Interface.
Driver tests in Nexus Root Toolkit fail. It advises enabling USB debugging as one of the fixes which of course I cannot do as I can't boot up to reach those options.
From this I surmise there is some problem with the drivers. I have tried on two different PCs as well.
Software I have used in all my efforts: Nexus Root Toolkit 1.6.2, Gnex, JROMFlasher, TWRP, CWM, PdaNet, SDK Manager, Nexus 7 tablet USB driver revision R06, Naked Universal Driver 0.72 .
I'd appreciate any advice (apart from sending the thing back), epescially if it's in a step by step easy to follow format. So basically, my question is, how do I fix this? Is it possible to fix?
Many thanks in advance!
I just thought I'd update this, mainly to let people know what to do if they find they have a similar problem to the above.
Basically, as said before none of the fixes worked. I spent a huge amount of time trying everything. So in order to save people massive amounts of time who have pretty much the same problems as I had and spending hours upon hours trying fixes like I did, then the best thing to do is to return your Nexus 7 to where you bought it for a return.
Mine was subsequently discovered to have a hardware fault so I was basically trying to fix the impossible. If you find yourself in the same boat after trying the fixes, and they don't work after a couple of tries, don't do it multiple times like I did. It's just easier, less frustrating and will save you much hair loss, anger and general irritation to let Asus fix it.
Yes, I know some of us get a bee in our bonnet about fixing it ourselves and see returning it as the last resort (like me), but anyway, trust me, just send it back, and save yourselves the trouble in a case like the above.
My tablet has arrived back repaired and works again. The hardware fault was covered by the warranty.
I hope anyone who encounters the same issues as I have manages to find this of use in the future!
Hey guys,
My Nexus 4 (in previously perfect working condition!) was rooted with an unlocked bootloader. It was still running stock Android. Then, purely out of the blue, I couldn't start my phone. It would get stuck in the four bouncing circles after the Google logo. After waiting a few hours, I tried again. Failed again. Then I used Wug's toolkit to flash stock 4.4.4 and unroot. Immediately trying to start the device didn't work, but a few hours later it booted up successfully. This went on for a few days till it happened again - I accidentally let it turn off and it wasn't booting. After waiting several hours, it began to work again. Then last night, I accidentally turned it off again. The boot failed once again. In the morning, I tried again. Failed. I tried again throughout the day, and it repeatedly failed. I then reflashed 4.4.4, but it failed to boot. I'm looking for a solution - any explanation or reason this would suddenly crop up or what i can do to fix it.
Notes: Under Wug's toolkit, I did select the soft brick option. When my phone was on, it worked perfectly. No particular event triggered this problem, it happened in what seems like a completely random fashion.
avpatel said:
Hey guys,
My Nexus 4 (in previously perfect working condition!) was rooted with an unlocked bootloader. It was still running stock Android. Then, purely out of the blue, I couldn't start my phone. It would get stuck in the four bouncing circles after the Google logo. After waiting a few hours, I tried again. Failed again. Then I used Wug's toolkit to flash stock 4.4.4 and unroot. Immediately trying to start the device didn't work, but a few hours later it booted up successfully. This went on for a few days till it happened again - I accidentally let it turn off and it wasn't booting. After waiting several hours, it began to work again. Then last night, I accidentally turned it off again. The boot failed once again. In the morning, I tried again. Failed. I tried again throughout the day, and it repeatedly failed. I then reflashed 4.4.4, but it failed to boot. I'm looking for a solution - any explanation or reason this would suddenly crop up or what i can do to fix it.
Notes: Under Wug's toolkit, I did select the soft brick option. When my phone was on, it worked perfectly. No particular event triggered this problem, it happened in what seems like a completely random fashion.
Click to expand...
Click to collapse
The exact same thing happened to me, i finally flashed 4.2.2. it booted, but then my IMEI disappeared and i couldnt make any calls. It was completely random. It is possible that the same thing is happening to you. If that is the case, the only fix I know is to change the board.
if you can flash CWM or TWRP, try wiping the system files and then flashing a rom to see what happens.
What do you mean change the board?
And for the rest of the suggestions I'd really appreciate a bit of an explanation - I'm not terribly experienced with messing with Android;
Well I did some research and I flashed TWRP, wiped system and data. I then flashed 4.4.4, but it didn't boot. I'll try to turn it on again tomorrow.
^^On stock 4.2.2, does your phone have an imei number? If not, you will need to send the phone to LG for repair.
avpatel said:
Hey guys,
My Nexus 4 (in previously perfect working condition!) was rooted with an unlocked bootloader. It was still running stock Android. Then, purely out of the blue, I couldn't start my phone. It would get stuck in the four bouncing circles after the Google logo. After waiting a few hours, I tried again. Failed again. Then I used Wug's toolkit to flash stock 4.4.4 and unroot. Immediately trying to start the device didn't work, but a few hours later it booted up successfully. This went on for a few days till it happened again - I accidentally let it turn off and it wasn't booting. After waiting several hours, it began to work again. Then last night, I accidentally turned it off again. The boot failed once again. In the morning, I tried again. Failed. I tried again throughout the day, and it repeatedly failed. I then reflashed 4.4.4, but it failed to boot. I'm looking for a solution - any explanation or reason this would suddenly crop up or what i can do to fix it.
Notes: Under Wug's toolkit, I did select the soft brick option. When my phone was on, it worked perfectly. No particular event triggered this problem, it happened in what seems like a completely random fashion.
Click to expand...
Click to collapse
Did you wipe the system cache and dalvik cache BEFORE AND AFTER flashing a zip?
I've seen many instances of an unsucessful boot becuase the cache wasn't cleared AFTER flashing the zip.
If it still doesn't work I'd recommend you to redownload the system zip from the factory image site.
Hi guys,
I have searched around the forums and still unsure, weary of what to do. I got my nexus when they first came out. I used it for a while and eventually unlocked it so that i could get certain apps that needed root access. I dont think i flashed a custom rom on it though. I havnt updated android to 4.4 yet. Its been a long time since i updated anything. Hence the start of my dilemma. I went to backup my tablet. It told me SuperUser or the bootloader needed to be updated. So im like oh fine update. Tablet then restarts brings me to my boot screen and says downloading target do not turn off. Its been stuck like this and nothing happens. I held down the power and rocker buttons and got back to boot option screen. Here's where im lost and dont remember what to do. I have tried start, recovermode, restartbootloader, and nothing seems to work. They all bring me back to the dead little android guy
Here's the device info.
product name: manta
variant: wifi
h/w version 8
bootloader version: mantam03
carrier info: none
serial: ****
lock state: unlocked
reboot mode flag: recovery
I slightly recall when i first unlocked it using twrp or clockworkmod? I could be wrong. Either way i no longer have the rootkit nor the computer i originally used to unlock it. What software do i need to install to get me back up and running. I was worried i may brick it if i installed the wrong version kit. That maybe newer version wouldn't work with my n10 because it was running an old version. Any advice would be much appreciated.
Jshannon22 said:
... I was worried i may brick it if i installed the wrong version kit. That maybe newer version wouldn't work with my n10 because it was running an old version. Any advice would be much appreciated.
Click to expand...
Click to collapse
Considering that you have not used the N10 in a very long time your user data may not be all that important so here are some options.
1) You could flash the factory image for Android 5 which will wipe out your user data but give you a clean system including stock recovery.
2) You could flash the factory image for Android 5 but first you need to change the "flash-all".(bat,sh) script by removing the "-w" option which will prevent your userdata from being wiped. That takes some knowledge to edit the script but all you need is a simple text editor.
After either of those options you can root and replace your recovery. Root before you change your recovery or you will run into an issue due to specific changes in Android 5.
Instructions for installing a factory image.
Nexus 10 lollipop factory image.
How to install Android Lollipop factory image on Nexus 5, 7 and 10 (and keep your data)
Good Luck
I'm having similar issues! When trying to install lollipop over sideload it always errors and states not enough space.
I've formated all the data so I'm at a loss.
Any ideas to install lollipop?
Sent from my Galaxy Nexus using XDA Free mobile app
I'm concerned I've bricked the device. To be honest I'd be happy just to get kitkat back!
When the device powers up it automatically goes into a "no command" bootloop. With the android on its side with an exclamation point sign coming out.
Holding power and the volume it then goes to the android recovery where I have four options: reboot, apply update from adb, factory reset, wipe cache.
When in command, typing adb devices shows my device.
Using adb sideload I've tried to update, but I always get the error "creating parent of system/app/KoreanIME/KoreanIME.apk failed. error no space left on device
E:Error in /tmp/update.zip
status 7 installation aborted"
So I downloaded the kitkat image and tried to run the script "flash all". But then the command screen just says "waiting for device"
After all that failed, I tried to hold power and the volume button when it restarts. That takes me to the odin screen, where it just states "downloading, do not remove target" The volume buttons do nothing. pressing the power button just reboots.
Any help would be much appreciated!
I have the same issue. There does not seem to be a way to install any (old) version of android. All I get is the same error message "creating parent of system/app/KoreanIME/KoreanIME.apk failed. error no space left on device
E:Error in /tmp/update.zip status 7 installation aborted"
I did not root my device nor did I install a custom rom. I just started installing the OTA update and that's when the tablet got stuck in the boot loop thingy.
I also searched the internet and all I found were similar instructions on how to install factory images etc. using adb sideload.... as I mentioned, following those instructions lead to the error message.
I can' believe this.
Thanks for your help
I also have similar issue. I had non rooted Kitkat 4.4.4 installed on N10. I received update intimation to Lollipop hence downloaded the update. While installing, message regarding error came followed with message "No command" . Now nothing is done further. Even tablet is not getting power off. Periodically screen displaying Google is coming followed with message "No command" I just checked. I can enter in to download and recovery. I now downloaded also Lollipop update for manual updating.
While connecting to PC, it starts searching for driver and after sometime message flashed "Driver not installed successfully" might be due to non detection of MTP. In such case if I try to maually install then ADB also is not recognising the connected device. As novice even I do not know to install ADB sideloaded.
Can you suggest how best I can revive N10?
Regards,
Guys,
I also had the exact problem. What finally worked for is to flash custom recovery (TWRP latest version) with "fastboot flash recovery <recovery.img>" command.
Then from the recovery I installed custom ROM (http://forum.xda-developers.com/showthread.php?t=1998585), as the official ROM also failed.
Hope it will help someone.
Shleim, this seems to just have worked out fine. Many thanks for your help!
I'm still kinda wondering why it wouldn't work with the official ROM. In any case, this is by far better than having a bricked tablet and at least now I know it still works.
Awesome, thanks for this tip!!!
fliuwoek said:
Shleim, this seems to just have worked out fine. Many thanks for your help!
I'm still kinda wondering why it wouldn't work with the official ROM. In any case, this is by far better than having a bricked tablet and at least now I know it still works.
Awesome, thanks for this tip!!!
Click to expand...
Click to collapse
No worries, glad it helped you.
I have a Samsung Galaxy Tab 4 8” SM-T330NU running 5.1.1. The box tells me the ‘real’ model is SM-T330NYKAXAR. I decided to root the phone, because I want to get to Marshmallow and to get rid of this extra bloat where. (I will mention I have a good amount of experience rooting, including just rooting my Droid Turbo).
Anyway, after a lot of looking around the forums, I decided to use the CF-AutoRoot method (CF-Auto-Root-milletwifiue-milletwifiue-smt330nu) to root. I got Odin and installed it (along with the Samsung drivers) onto my Windows 10 PC; set debugging, on; and ran Odin. I followed the directions and it appeared to root properly; and I got to CWM recovery. Woo hoo! (Or so I thought)
So then after making sure I can get into recovery, I rebooted back into my stock ROM. Unfortunately, I got stuck at the Samsung logo; tried rebooting multiple times; even did a factory reset/wipe (as per instructions I saw on the forum) but to no avail. (Even let it set for over an hour but it never got past the Samsung logo).
After some more reading, I figured I might as well go ahead and flash a new ROM; so I think (if I remember correctly) I tried the JazzROM. It got up to about 69% and then it just quit - screen went black, and then it rebooted back to Odin mode. Obviously it didn’t work; then when I tried to get back into recovery to wipe and try the flash again, I got the message ‘Cannot mount \system - invalid argument’.
Again, after much reading and trying, I was able to get TWRP recovery installed and then wiped/formatted the system partition, which I had read would help get rid of that error. And it did seem to fix it.
So I can re-root with Odin without any issues; I can get to Recovery (either CWM or TWRP depending on which I flash), but no matter what I do, it either gets about 2/3 the way thru the flash process and then reboots back to Odin mode; or (using TWRP) I can get it certain ROMS to flash successfully, but after rebooting it goes right to Odin mode (saying it could not do normal boot). I even tried loading a stock, with the same result.
Which leads me to my first question: Exactly which ‘stock’ file should I be loading? I am having a hard time finding one - either it leads me to a dead end, or the download doesn’t work.
- When in CWM recovery, it shows the following:
At the top:
LMY47X.T330NUUEU1BOI1
Bottom:
#Manual Mode#
— Applying Multi-CSC...
Applied the CSC-code : XAR
Successfully applied multi-CSC.
Are these correct?
- When TWRP is installed (3.0.0-3) it starts by asking me about the ‘Unmodified System Partition’ and whether it should be kept read-only or allow modifications. I assume allow mods? Otherwise I don’t see how you could apply a new ROM? (I haven’t seen this in a while, not in my install of TWRP to the Droid Turbo). So just want to make sure I am selecting the right option.
- I am also concerned about whether I am using the right packages for this tablet. Based upon what I see on the box and sticker (which I still have) this should use the stock ROM LMY47K.T330NUUEU1BOI1 model; but I’ve also seen things referring to a BOG1 model? Mine is the T330NU English and (I assume) US model since I am in the US.
Any ideas as to what is going on? If I can at least get back to stock I could then start from scratch with the appropriate info; or just install one of the new ROMS (I’ve tried Jazz, Dirty Unicorns, UltraStock). I don’t think I am ‘bricked’ because if so I wouldn’t be able to get to Odin or recovery. Any help appreciated here. Thanks!
-Tom (Chimp)
NM, finally got it working, running DU and running fantastically, if I may say so. Getting TWRP to install finally fixed everything.
Sent from my SM-T530 using XDA-Developers mobile app
So basically, few months ago i tried to root the phone, get new recovery and different rom. If I remember correctly I got stuck trying to get custom recovery to work, because everytime I restarted phone it would be replaced by the stock one. So I left the phone as it was, and disabled the TWRP app on it. Problem was, I could not update phone. Today I tried to completely revert to stock.
I flashed stock recovery but when I tried to install update from the phone storage, it did not even give me option to select a file.
I tried to update the recovery to newer one which gave me the option to select a file, but the installation got canceled after few seconds, putting me back on the file selection screen in recovery.
I tried to instal TWRP but I can't even boot into it at all because the phone is just stuck with blackscreen and lightblue led light.
I tried to ADB sideload the newest stock rom that I downloaded from OP5 site but this one went to around 50% and then crashed as well.
I also tried to do the update using the Settings>System update > Local Upgrade but this one also fails once it gets into recovery.
I tried wiping cache/reset system settings or wiping every data on the phone before any update but none of it seems to help and everytime I restart the phone afterwards the TWRP app is still there needing an update.
I tried to just lock the bootloader but I got the "Your device is corrupt. It can't be trusted and will not boot" message followed by link to google support. I assume that is because of the TWRP app that is on the phone but I can't get rid of it no matter what I try. I tried searching for people having simillar problems but I couldn't find anything that would help me.
Any suggestions?
Thanks in advance.
You can go with the last resort and use the Unbrick tool.
https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706