Update android 4.4.2 fail/error7 - Nexus 4 Q&A, Help & Troubleshooting

Lots of people having the same problem, they get an error when they install the update on there rooted nexus.
I tried this, and i wanna share it with you guys.
First download the update file from google. (The occam-kot49h-factory-02e344de file)
Then extract it, when you get the zip extract this too. (Till you get the image-occam-kot49h folder, in this folder you can find: android-info.txt, boot.img, recovery.img, system.img and userdata.img)
Connect your device to the pc.
Now you have to use adb,
Open your terminal or cmd for Windows : cd C:\Users\YOUR_DIRECTORY\sdk\platform-tools
Then get into the bootloader:
Adb reboot-bootloader ( or start manually: Volume up + unlock button.)
Enter this in cmd:
fastboot erase system
(fastboot erase data)
(fastboot erase userdata)
fastboot erase boot
Now you can flash Android Kitkat 4.4.2:
fastboot flash system system.img
(or Fastboot flash system C:\YOUR_DIRECTORY\occam-kot49h-factory-02e344de\occam-kot49h-factory-02e344de\occam-kot49h\image-occam-kot49h\system.img)
fastboot flash boot boot.img
(or again Fastboot flash boot C:\YOUR_DIRECTORY\occam-kot49h-factory-02e344de\occam-kot49h-factory-02e344de\occam-kot49h\image-occam-kot49h\boot.img )
And reboot.
This worked for me, I'm not responsible for anything. I used this method and it worked for me. Personally I didn't use the fastboot erase, just fastboot erase system and fastboot flash system system.img and fastboot flash boot boot.img. I updated from android 4.4 to 4.4.2.
Sorry for my bad english, still learning..
Sent from my Nexus 4 with kitkat 4.4.2using xda app-developers app

I hope this solves the problem for you, leave some feedback or hit thanks when I helped you.
Have a nice day
Sent from my Nexus 4 using xda app-developers app

Thanks, there is nothing wrong with your English. Unfortunately I am too much of a noob to understand what you are saying. I have had the Error 7 twice now with failed automatic updates and it's scaring me.
I followed step by step instructions to make Flash run on my N5 - which were hard, but worth it because it meant the phone would actually work on the internet, even though Dolphin has that much-hatedl dolphin button right in the way that I hit at least 200 times a day when I scroll.
Can anyone please re-write these instruction into TOTAL noob-speak, including things like 'this next step will trash all your apps, data and photos so back up you phone first by doing X, Y and Z'.
Many thanks

G1MFG said:
Thanks, there is nothing wrong with your English. Unfortunately I am too much of a noob to understand what you are saying. I have had the Error 7 twice now with failed automatic updates and it's scaring me.
I followed step by step instructions to make Flash run on my N5 - which were hard, but worth it because it meant the phone would actually work on the internet, even though Dolphin has that much-hatedl dolphin button right in the way that I hit at least 200 times a day when I scroll.
Can anyone please re-write these instruction into TOTAL noob-speak, including things like 'this next step will trash all your apps, data and photos so back up you phone first by doing X, Y and Z'.
Many thanks
Click to expand...
Click to collapse
Follow this gudie using the latest occam images: http://forum.xda-developers.com/showthread.php?t=2010312
I have restored the occam 4.4 stock image and it upgraded to 4.4.2 with no issues.

G1MFG said:
Thanks, there is nothing wrong with your English. Unfortunately I am too much of a noob to understand what you are saying. I have had the Error 7 twice now with failed automatic updates and it's scaring me.
I followed step by step instructions to make Flash run on my N5 - which were hard, but worth it because it meant the phone would actually work on the internet, even though Dolphin has that much-hatedl dolphin button right in the way that I hit at least 200 times a day when I scroll.
Can anyone please re-write these instruction into TOTAL noob-speak, including things like 'this next step will trash all your apps, data and photos so back up you phone first by doing X, Y and Z'.
Many thanks
Click to expand...
Click to collapse
Hey I rewrote some things, when you don't use the commands: (fastboot erase data) and (fastboot erase userdata) you won't lose any data, but i recommend you to make a full backup with CWM or something like that.
I used android adb from the sdk kit.
https://developer.android.com/sdk/index.html
Start your phone with volume up + unlock button to enter the bootloader

I had actually this problem too, but then decided not to flash the update, as lots of people complaining from it being buggy. Thanks for the quick guide though!

Related

[Q] phone won't boot....please help!

Last night I was using my Nexus 4 and it wouldn't connect to any web pages so I thought I'd reboot to see if that fixed it. I powered off then back on and it won't get past the Nexus logo on the start up screen.
I'm unlocked and rooted but haven't installed any Roms ever. I used Wug's toolkit to root.
the only thing I can think of is that I was copying fonts from the system folder and maybe I moved a font instead of copying it, but I really don't think moved anything without replacing. Either way, i really don't think that moving a font would cause the phone to not boot up.
The phone booted up just fine an hour or so before this happened, so the font thing is the only thing I can come up with. I tried to use Wug's toolkit to push the font file to the N4 but the script gets stuck when trying to reboot.
Please help!! any suggestions?
------
addt'l info:
CWM not installed, phone does not bootloop, just gets stuck at X
nvillamob said:
Last night I was using my Nexus 4 and it wouldn't connect to any web pages so I thought I'd reboot to see if that fixed it. I powered off then back on and it won't get past the Nexus logo on the start up screen.
I'm unlocked and rooted but haven't installed any Roms ever. I used Wug's toolkit to root.
the only thing I can think of is that I was copying fonts from the system folder and maybe I moved a font instead of copying it, but I really don't think moved anything without replacing. Either way, i really don't think that moving a font would cause the phone to not boot up.
The phone booted up just fine an hour or so before this happened, so the font thing is the only thing I can come up with. I tried to use Wug's toolkit to push the font file to the N4 but the script gets stuck when trying to reboot.
Please help!! any suggestions?
------
addt'l info:
CWM not installed, phone does not bootloop, just gets stuck at X
Click to expand...
Click to collapse
do a factory reset via recovery
by copying system fonts which are not made for jb, your system could be damaged and thats the reason why you are in a bootloop..
What font did you push and how?
Sent from my HTC6435LVW using Tapatalk 2
pa.pn2 said:
do a factory reset via recovery
by copying system fonts which are not made for jb, your system could be damaged and thats the reason why you are in a bootloop..
Click to expand...
Click to collapse
I'd really like to avoid doing a factory reset if possible, but that may be inevitable.
What I did was copy (move?) fonts from the system folder to a folder on the sd card so the fonts would be accessible to something I was making in UCCW.
When I boot into recovery all I see is the Android laying on its back with a red triangle and beneath that it says "No command."
And this is why you don't use a toolkit. It gives you ability to do things when you didn't know how to get there.
You should just factory reset and get your phone booting. I don't think you're in a position to be trying to save your data because you did things without know what was going to happen. Don't ever touch things in system unless you truly know what you're doing. Especially not without a nandroid backup.
Sent from my Nexus 4 using xda premium
I'm in over my head now, but I knew what I was doing at the time. I *think* I moved a ttf file instead of copying it. A brain fart led to all this. Live and learn and hopefully the community can help me out.
I do have a nandroid from a couple weeks ago that I'd be happy to flash but I'm not familiar with adb but I'm willing to give it a shot if anyone could help. Google hasn't brought me much luck.
nvillamob said:
I'm in over my head now, but I knew what I was doing at the time. I *think* I moved a ttf file instead of copying it. A brain fart led to all this. Live and learn and hopefully the community can help me out.
I do have a nandroid from a couple weeks ago that I'd be happy to flash but I'm not familiar with adb but I'm willing to give it a shot if anyone could help. Google hasn't brought me much luck.
Click to expand...
Click to collapse
Best thing I can say is to fastboot flash back to stock. Google on how to do it, there's a guide on XDA on how to restore factory stock images.
Start all over as if you just got your phone and don't do the same mistakes again. Spend the 25-30 minutes and read how to use fastboot, and don't do things without asking or thinking beforehand. If you don't know what you're going to be modifying or whatever, don't do it.
You don't flash a nandroid. You restore it via recovery in recovery mode.
So I booted into recovery, chose wipe data/factory reset.
After that runs, I reboot the phone and I'm still stuck on the X.
I've got the factory image tgz file but I don't know how to flash it
nvillamob said:
So I booted into recovery, chose wipe data/factory reset.
After that runs, I reboot the phone and I'm still stuck on the X.
I've got the factory image tgz file but I don't know how to flash it
Click to expand...
Click to collapse
Use search + read stickies in the future.
Here is the thread you're looking for, http://forum.xda-developers.com/showthread.php?t=2010312
D. Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10l.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.33.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Optional (NOT optional for n00bs) -- Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Optional (NOT optional for n00bs) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Click to expand...
Click to collapse
the files within the tgz will contain those imgs that you need. you may skip on fastboot flashing the radio, recovery, bootloader
do flash the system and boot flash for sure.
thanks again. I must be awful at searching because I can never find what I'm looking for.
In the mean time, I figured out how to use the toolkit to flash the stock image and I'm back in business. i sincerely appreciate the help.
nvillamob said:
thanks again. I must be awful at searching because I can never find what I'm looking for.
In the mean time, I figured out how to use the toolkit to flash the stock image and I'm back in business. i sincerely appreciate the help.
Click to expand...
Click to collapse
It's all good, I mainly use Google and type random tags on google like "how do i restore nexus 4 back to stock" or something between those lines and something would pop up. In general, Q&A there are stickied threads that has an index with a link to all the other pages that you're looking for.
It all comes with experience.
Errrrrrrr. Um.... you kinda killed me when you said toolkit. Don't use them it's what got you in this situation in the first place. Learn from your mistakes. The toolkit didn't necessarily bring you to this situation but you're not familiar with what the toolkit is actually doing and you're doing changes to the system because you aren't aware of what's going on in your surroundings.
http://forum.xda-developers.com/showthread.php?t=1469909 is a good thread on why you don't use toolkits. How do you think I know all this knowledge? Certainly not by using a toolkit. You have to know how to do these things, otherwise the next problem you'll have you'll ask questions some more. Please just take the time and read it and figure it out how to do it. It's not difficult by any means.
Good luck and glad I can help. I hope I could change your mind on the dangers of using toolkits and do it the traditional way with backgrounds of why you're doing this and that. If everyone used a toolkit then no one would be in Q&A forums could help others, like myself. If i used a toolkit, i wouldn't know how to fix your situation either. Thanks.

Rooting my Nexus 4 - Kinda scared to do

The title may sound strange but it's true.
I have this phone for just one week and haven't used it to call (reason: moving from T-Mobile to Tele2, this takes time. Date: 25e).
Rooting will allow me to do some stuff like a different boot animation which caught my attention. What I just don't want to happen is that I brick my phone to the point that it doesn't work anymore. Secondly I void my warranty which is something I don't feel so good about seeing I just got the phone.
I don't know this yet but if I root is. Can I back up everything from the phone? Contacts, Apps, settings etc etc? So when something goes wrong I can install a image of my back up?
Sadly I am pretty dark now. It's all new and while I would like to give it a shot, some things don't feel right for me just yet as stuff is unclear to me on how do it it.
Can XDA help me maybe? Also what are some really cool ROM's? I wanted to get Touchwiz but there is no (lol) and Cyanogenmod is like Stock Android so it seems ...pointless?
Best regards,
Robert Oortwijn
ZyreHD said:
The title may sound strange but it's true.
I have this phone for just one week and haven't used it to call (reason: moving from T-Mobile to Tele2, this takes time. Date: 25e).
Rooting will allow me to do some stuff like a different boot animation which caught my attention. What I just don't want to happen is that I brick my phone to the point that it doesn't work anymore. Secondly I void my warranty which is something I don't feel so good about seeing I just got the phone.
I don't know this yet but if I root is. Can I back up everything from the phone? Contacts, Apps, settings etc etc? So when something goes wrong I can install a image of my back up?
Sadly I am pretty dark now. It's all new and while I would like to give it a shot, some things don't feel right for me just yet as stuff is unclear to me on how do it it.
Can XDA help me maybe? Also what are some really cool ROM's? I wanted to get Touchwiz but there is no (lol) and Cyanogenmod is like Stock Android so it seems ...pointless?
Best regards,
Robert Oortwijn
Click to expand...
Click to collapse
setup adb and learn how to flash back to stock in fastboot. you will never brick your device beyond repair as long as you are capable of following directions for flashing and rooting and such
Here's the sticky from the other forum.
That is very useful and they talk in layman's terms. When I first got my N4, I followed this and got custom everything following the instruction posted there.
I'm no expert, but I rooted my N4 in the first week very easily, and as long as you follow all the instructions in the XDA thread then you won't go wrong. If you are really worried then you can use a toolkit as that will automate everything, but I'd never recommend that as you aren't really learning.
As for backing everything up, you can back up some things like your contacts, WiFi passwords and so on to your Google account. Apps is a lot harder if you want the data, but I believe an ABD backup will work - again, look at the appropriate thread (or use the toolkit for backing up).
And Roms, most of them have a stock feel with more features such as extra customization, but if you want a different look you can use themes - you can get touchwiz themes on the play store for ROMs like CM.
Sent from my Nexus 4 using xda premium
you dont need root to flash roms or kernels, you need a custom recovery(and an unlocked bootloader). you need root to run root apps and to mess around with the root file system.
I agree with tom about the toolkits. There is a large correlation between people who use toolkits and people who break their phone and have no idea what they are doing. Learning fastboot will save you from huge headaches and regret in the future.
username8611 said:
I agree with tom about the toolkits. There is a large correlation between people who use toolkits and people who break their phone and have no idea what they are doing. Learning fastboot will save you from huge headaches and regret in the future.
Click to expand...
Click to collapse
Finally got it rooted and installing CM10.1 went easy!
What I only want to know now is:
How do I relock the phone from rooted to unrooted again? Same for bootloader.
Removal of Clockwork.
And remove CM10.1 and get stock android back.
Thats all!
ZyreHD said:
Finally got it rooted and installing CM10.1 went easy!
What I only want to know now is:
How do I relock the phone from rooted to unrooted again? Same for bootloader.
Removal of Clockwork.
And remove CM10.1 and get stock android back.
Thats all!
Click to expand...
Click to collapse
Read this thread http://forum.xda-developers.com/showthread.php?t=2010312 well, it will show you exactly how to get back to stock if need be.
We were all scared and nervous too when we first rooted an android device. Lol. When you get it done you soon realize how easy it was. :thumbup:
Sent from my Nexus 4 using Tapatalk 2
Can someone help? So I have Cyanogenmod installed on the phone and got USB debug on. When i unplug and go into the bootloader and then plug the micro-usb in my PC doesn't detect the phone. I do have the drivers installed.
It did work, now it doesn't meaning I can't perform the stuff needed.
ps: If your wondering if I use the SDK to put everything to stock well sorry but I can't get the SDK to work. Java issues and errors. Pain in the ass so I stop with that.
In the bootloader and then recovery I get a Android logo with a red /!\ ?
Edit 1: I tried a reboot and now it doesn't hang. The X logo is moving but nothing yet.
Edit 2: 5min later and still at the X logo. It does move but nothing. Is my phone dead?
ZyreHD said:
In the bootloader and then recovery I get a Android logo with a red /!\ ?
Edit 1: I tried a reboot and now it doesn't hang. The X logo is moving but nothing yet.
Click to expand...
Click to collapse
if you are getting and android with a red "!", it sounds like you didnt flash a custom recovery. you need to be on either cwm, or twrp.
edit: it sounds like something got jacked and you need to start over again. it sounds like you are going back to stock, right?
start from the bootloader with fastboot. format/erase all the partitions and reflash everything and you should be golden
im not sure if i reading it right, but from what i can gather, you flashed cm10.1, then found out adb doesnt work right so you are ditching it and going back to stock? i wouldnt worry about it too much. as long as you can still use fastboot in the bootloader, thats all you need to do anything to save yourself from certain death. adb is more helpful for gathering up data if you cant lose it before flashing back to stock
username8611 said:
if you are getting and android with a red "!", it sounds like you didnt flash a custom recovery. you need to be on either cwm, or twrp.
edit: it sounds like something got jacked and you need to start over again. it sounds like you are going back to stock, right?
start from the bootloader with fastboot. format/erase all the partitions and reflash everything and you should be golden
Click to expand...
Click to collapse
For some reason. I pressed the buttons to get into the bootloader I get this:
Download Mode. Do not unplug?
Edit: I'm back in the bootloader. I didn't press the combination right sending me into Download Mode.
Edit 2:
So what I did was this. I followed these instruction on how to install custom ROMS: http://www.androidrootz.com/2013/02/how-to-install-custom-roms-on-nexus-4.html I also followed them in the procedure of rooting your phone.
I tried it out and now wanted to go back to stock. So I found a article also by them and did that: http://www.androidrootz.com/2012/12/how-to-unroot-nexus-4-to-stock-42-jelly.html
When I was at the point where the cmd said: erasing use rdata the article said: 5min, but it took longer so I unplugged the USB.
Now I'm here where I can't boot the OS anymore. Bootloader does work but recovery doesn't as I get the /!\
Edit 3:
Retrying in the meantime. Now at writing system (done)
Edit 4:
Now I'm at the point where it's erasing userdata....
Edit 5: couple of minutes later and still going.
ZyreHD said:
For some reason. I pressed the buttons to get into the bootloader I get this:
Download Mode. Do not unplug?
Click to expand...
Click to collapse
unplug anything that is plugged into your phone. make sure it is completely turned off. hold volume down and power until it vibrates. it should take you straight to the bootloader
---------- Post added at 02:21 PM ---------- Previous post was at 02:16 PM ----------
yeah something is amiss, hold on let me type this up real quick
go here and download OCCAM factory image. open up the file you downloaded and you should see userdata.img, system.img, etc.... take all the files that end in img and move them to your directory for fastboot aka: /platform-tools, or whatever you use for fastboot.
boot your phone to the bootloader. type this in fastboot, pressing enter after each line:
fastboot format userdata
fastboot format system
fastboot format cache
fastboot erase boot
fastboot erase recovery
fastboot reboot-bootloader
now for the flashing,
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
OPTIONAL... if you think your radio is messed up -----> fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
fastboot reboot
voila
username8611 said:
unplug anything that is plugged into your phone. make sure it is completely turned off. hold volume down and power until it vibrates. it should take you straight to the bootloader
---------- Post added at 02:21 PM ---------- Previous post was at 02:16 PM ----------
yeah something is amiss, hold on let me type this up real quick
go here and download OCCAM factory image. open up the file you downloaded and you should see userdata.img, system.img, etc.... take all the files that end in img and move them to your directory for fastboot aka: /platform-tools, or whatever you use for fastboot.
boot your phone to fastboot. type this, pressing enter after each line:
fastboot format userdata
fastboot format system
fastboot format cache
fastboot erase boot
fastboot erase recovery
fastboot reboot-bootloader
now for the flashing,
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
OPTIONAL... if you think your radio is messed up -----> fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
fastboot reboot
voila
Click to expand...
Click to collapse
I got a different option now. format userdata and I get options. Flash all, erase, update filename etc.
ZyreHD said:
For some reason. I pressed the buttons to get into the bootloader I get this:
Download Mode. Do not unplug?
Edit: I'm back in the bootloader. I didn't press the combination right sending me into Download Mode.
Edit 2:
So what I did was this. I followed these instruction on how to install custom ROMS: http://www.androidrootz.com/2013/02/how-to-install-custom-roms-on-nexus-4.html I also followed them in the procedure of rooting your phone.
I tried it out and now wanted to go back to stock. So I found a article also by them and did that: http://www.androidrootz.com/2012/12/how-to-unroot-nexus-4-to-stock-42-jelly.html
When I was at the point where the cmd said: erasing use rdata the article said: 5min, but it took longer so I unplugged the USB.
Now I'm here where I can't boot the OS anymore. Bootloader does work but recovery doesn't as I get the /!\
Click to expand...
Click to collapse
When you see the android laying down that is stock recovery. Press volume up and power to open the menu. Then you can factory reset.
Sent from my Nexus 7 using xda premium
El Daddy said:
When you see the android laying down that is stock recovery. Press volume up and power to open the menu. Then you can factory reset.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I only have 4 options there.
Reboot system now
apply update from ADB
wipe data/factory reset....
Oh I got it. It formatted and I rebooted. For now it only shows the X logo. Will go downstairs in the meantime to get something to drink. It might take some time maybe?
THANKS YOU SO MUCH!!!
Just as I wanted to go it booted!!!!!!!!!!!!!!!!! 2 hours of hard search and it was this small thing to do? I was really afraid that I had wiped the factory reset of the phone!!!!
Thank you again, all of those who helped!!!!:laugh::laugh::good::highfive:
nevermind, you were talking about the options in recovery
ZyreHD said:
THANKS YOU SO MUCH!!!
Just as I wanted to go it booted!!!!!!!!!!!!!!!!! 2 hours of hard search and it was this small thing to do? I was really afraid that I had wiped the factory reset of the phone!!!!
Thank you again, all of those who helped!!!!:laugh::laugh::good::highfive:
Click to expand...
Click to collapse
Congrats. That's why I wrote what I did in your other thread. Read, read, read. Its better to know how to fix things before they happen then frantically trying to find out how fix them while they happen.
Sent from my Nexus 7 using xda premium

Stuck In BootLoop While updating lollipop

i used nexus root tool kit to update nexus 4 from 4.4 to 5.0... all done in pc but mobile is stuck in boot loop. can anyone tell me how can i restore my phone to normal working...
Please help me i am noob here
is there any one who can help me here
i thought i will get ans with in 1hr... still waiting if someone can help
letsnexus said:
i thought i will get ans with in 1hr... still waiting if someone can help
Click to expand...
Click to collapse
This is why we don't recommended using tool kits. You should try flashing the factory image using fastboot.
Sent from my Nexus 9 using XDA Free mobile app
Same here, i tried re-flashing many times. Darn that nexus root toolkit
any suggetion or link which can help me to use fastboot use and install stock rom
thank alot for help
I am currently in the same position ! Used a toolkit too, always have.
This is why you never use a Toolkit, it's always been mentioned around in XDA that this has always been a developer website of learning and knowledge. You must always know what goes on behind than just blindly flashing things. It's a rule of thumb that you're more likely to brick your phone with a Toolkit than by yourself. Easiest step as follows.
1. Download factory image
2. Download ADB files
3. Make a folder and extract the adb files and factory image inside the same folder.
4. Plug the phone in bootloader mode or simply type adb reboot bootloader (Developer options must be enabled and USB Debugging) by exiting the folder, holding shift, right clicking the folder and pressing open command window and typing the command.
5. Every factory image comes with a flashall.bat, double click it and voila. Updates like it should. (User data will be wiped)
If you don't want your userdata to be wiped, simply open flashall.bat with notepad++, erase the '-w' in "fastboot -w update image" and save the file and launch it again.
Sent from my HTC One_M8 using Tapatalk
I will try that way later when I get in, I would have assumed that the toolkit did exactly those steps though, just an easy to use frontend
hazwheel said:
I will try that way later when I get in, I would have assumed that the toolkit did exactly those steps though, just an easy to use frontend
Click to expand...
Click to collapse
Go to stock recovery and do factory data reset and reboot phone. First time boot takes very long time (around 10 to 15 minutes). After successfully boot into android L check for the storage space. If it says only 5 GB available instead of 12 GB (My nexus is 16GB) then Go to Settings > Backup & Reset and select Factory data reset.
I had experienced these issues when upgrading to Lollypop and solved them on my own.
Note: If you were not able to boot into stock recovery, try twrp recovery. you have to install it using fastboot
fastboot flash recovery <filename.img>
letsnexus said:
any suggetion or link which can help me to use fastboot use and install stock rom
thank alot for help
Click to expand...
Click to collapse
although the link is for kitkat but the same method applies to flashing lollipop
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
moorthidaniel said:
Go to stock recovery and do factory data reset and reboot phone. First time boot takes very long time (around 10 to 15 minutes). After successfully boot into android L check for the storage space. If it says only 5 GB available instead of 12 GB (My nexus is 16GB) then Go to Settings > Backup & Reset and select Factory data reset.
I had experienced these issues when upgrading to Lollypop and solved them on my own.
Note: If you were not able to boot into stock recovery, try twrp recovery. you have to install it using fastboot
fastboot flash recovery <filename.img>
Click to expand...
Click to collapse
OK, I was able to get into recovery with this method, and wipe but I get can't mount cache errors during the wipe , waiting for the phone to reboot now, hopefully it will and get out of the bootloop. stupid thing is I'm not a noob, but stumped by this. Good excuse to upgrade to the N5 I guess
---------- Post added at 03:14 PM ---------- Previous post was at 02:55 PM ----------
Wow, this method worked! Brilliant! Thanks, and dammit, it worked, 10 minutes after she agreed to me getting am upgrade !
For all of you whom are stuck in bootloop a fastboot oem lock comand when in fastboot will solve the problem.
So go into bootloader and run "fastboot oem lock" for some reason on some devices Android 5.0 won't boot with unlocked bootloader.
hazwheel said:
OK, I was able to get into recovery with this method, and wipe but I get can't mount cache errors during the wipe , waiting for the phone to reboot now, hopefully it will and get out of the bootloop. stupid thing is I'm not a noob, but stumped by this. Good excuse to upgrade to the N5 I guess
---------- Post added at 03:14 PM ---------- Previous post was at 02:55 PM ----------
Wow, this method worked! Brilliant! Thanks, and dammit, it worked, 10 minutes after she agreed to me getting am upgrade !
Click to expand...
Click to collapse
OK great. Cheers, I helped someone today in this forum.
bett3rthan said:
For all of you whom are stuck in bootloop a fastboot oem lock comand when in fastboot will solve the problem.
So go into bootloader and run "fastboot oem lock" for some reason on some devices Android 5.0 won't boot with unlocked bootloader.
Click to expand...
Click to collapse
That did NOT work for me, the getting into recovery and wiping the device DID work though.
---------- Post added at 04:05 PM ---------- Previous post was at 04:03 PM ----------
moorthidaniel said:
OK great. Cheers, I helped someone today in this forum.
Click to expand...
Click to collapse
Yes, Thanks, unfortunately, she has withdrawn the offer of an early upgrade :silly:
thax
Misledz said:
This is why you never use a Toolkit, it's always been mentioned around in XDA that this has always been a developer website of learning and knowledge. You must always know what goes on behind than just blindly flashing things. It's a rule of thumb that you're more likely to brick your phone with a Toolkit than by yourself. Easiest step as follow
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thank you alot, you help in really good manner
and teached us not to use toolkit
will learn more abt rooting and flashing thank you once again
I am hitting this problem now, I got a OTA. After restarting its keep on looping waiting for more than 20mins still it's looping.
Tried going to boot-menu and did factory reset and it booted good after ~10 mins.
sububack said:
I am hitting this problem now, I got a OTA. After restarting its keep on looping waiting for more than 20mins still it's looping.
Click to expand...
Click to collapse
Power off, hold Vol Down + Power, when you get to the Android laying down, press volume up + pwr, then wipe the /cache from the menu (you do not need to do a full factory wipe, just wiping cache will do), and then reboot and wait. It will boot this time properly. @WugFresh is aware of the issue and said will put a fix in 1.9.9 for the N4
Thanks , I have tried clearing the cache and started waiting for an hour. Since it was still looping tried after factory reset/wiping user data. And then after 10min it came good.
I post this on Google Product Forum 2 days ago. Hope it helps
https://productforums.google.com/fo...ce=footer#!msg/nexus/Lv8fHtyJOPQ/wDzRUm4b2UsJ
(updated 29/11/2014)[not perfect but it is a SOLUTION]
The idea of this is to downgrade your nexus 4 without wiping your data, which means stuff you will need includes:
1. adb and fastboot on your computer (I am using mac but you can find it on windows as well. There are tones of website and forums telling you the latest method of getting it onto your computer)
2. factory image of nexus 4(I use 4.4.4, since that's what it was. I don't have the time and energy to try to do the same thing with lollipop. you can try can leave a comment).
update: do NOT try to flash 5.0 rom using this method. You will be stuck at boot loop again
3. usb cable
4. nexus 4 with unlocked bootloader(the process of unlocking bootloader will wipe your device)
5. computer
steps
1. unzip the factory image (something.tgz)
2. for me, after unzipping the .tgz, I still find another .zip inside. unzip that too.
3. hold vol+, vol-, and power button simultaneously to enter fastboot mode
4. open terminal(mac)(it would probably be cmd for windows)
5. connect your nexus 4(in fastboot)
6. to make sure it connect successfully, type "fastboot devices". if something like "005040c0d54bb291 fastboot" appears, you are good. Otherwise, try reconnect your device/boot to fastboot again/use another usb cable
7.now we need to tell the terminal to navigate to the location of the unzipped factory image. to do that, i suggest you put the unzipped folder to somewhere easy to find, like desktop. these are some commands to help you navigate:
"ls" allows you to look at whats inside the current directory of the terminal. For example, this is the output after typing "ls" for me:
some folder Photos
nexus4image.tgz how many folders do you have
5.zip occam-ktu84p
more folder occam-ktu84p.zip
after knowing where you are, use "cd" (below) to go to your folder
"cd" means change directory. For example. "cd Photos" will brings me to the "Photos" folder. And then if I type ls, I will see a whole bunch of photos in my photos. If you go to the wrong folder, type "cd ..", and it will bring you back to the previous folder.
8. flash bootloader.
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash bootloader bootloader-mako-makoz30d.img
9. reboot bootloader. just copy and paste
fastboot reboot-bootloader
10. flash radio
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.03.img
11. reboot bootloader. just copy and paste
fastboot reboot-bootloader
12. flash system
system.img is located inside the zip, use ls to help you navigate. This steps takes the longest time, total time on this step is 87 seconds while the others are less then 1 second
fastboot flash system system.img
13. flash boot
boot.img is located inside the zip, use ls to help you navigate.
fastboot flash boot boot.img
14. flash recovery
fastboot.img is located inside the zip, use ls to help you navigate.
fastboot flash recovery recovery.img
15. format cache(not the memory, so everything should be fine)
fastboot format cache
16. reboot and wait
this will reboot your device. You probably have to wait for a while to initialise all the apps. after than you are good to go!
fastboot reboot
credit: my friend for giving me this idea + http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312 + HelpMyNexus

Bricked while trying to install Full Android rom.. Now Boot loop into twrp. Pls help.

Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
puppinoo said:
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
Click to expand...
Click to collapse
Theres a hardware method to boot into the bootloader, this i think you can test, just to see if you can at least get into bootloader.....nothing more
Details in the official nvidia link
http://nv-tegra.nvidia.com/gitweb/?...ob_plain;f=README_SHIELD;hb=rel-22r18-partner
There's a thread here on the "questions" thread with users reporting that the timing of the hardware method can be a pain in the you know where.............might be worth looking into that thread for their experiences in booting the bootloader using the hardware method
Disclaimer:If your brave enough to risk a brick, read on
I suspect this might be the 2.1 stock/twrp issue........current twrp, or current stock dont play nice
Its a good sign that SOMETHINGS loading, rather then NOTHING booting, but dont know if theirs a solution
My analysis of the situation, of what little i know, the -w (wipe) command was expecting a stock recovery but instead got twrp, which is why your in this situation.........maybe, i stress maybe, if you could reflash stock again, you might be able to boot into android stock again and try full android again, leaving out twrp, until a twrp fix is found
Edit
Saying that, if the bootloader is, as i suspect, now using twrp to flash things, then you might be boned....... im no expert on bootloaders, stock "recoveries" and how they work, so i might be wrong on that
Reports around here say that 1.3 stock firmware is the recommended back to stock firmware, apparently, flashing any other firmware versions, bring their own issues.............
From 1.3 stock, use nvidias official OTA to upgrade from 1.3 stock, to 2.1 stock, then try 2.1 full android again...........note, i dont think you can skip firmwares i.e. you have to upgrade to 1.4, then to 2.0, then to 2.1, alot of downloading.......the OTA does'nt give you any other choice
Before doing anything that ive suggested, wait till someone with more experience to come along........i dont want to be responsible for you fully bricking your shield..........just wanna give you an idea of what i think has happened
If worse comes to worse, if you have warrenty, get a replacement
Gd luck........remember, this is an analysis of your predicament of what i THINK might of happened, and what steps, i likely might of entertained.......after looking into it more thouroughly, knowing that i could get a replacement if it went downhill.........so your mileage might vary
Edits
Crappy grammer, further musings, clarifications
Thanks.[/QUOTE]
puppinoo said:
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
Click to expand...
Click to collapse
I had something similar about... shield goes booting in recovery and trying delete some cache and keeps repeat and repeat
Hardware boot in fastboot / bootloader mode
Accessing Bootloader via Hardware
Unplug power from the Shield Android TV. *
Wait a few seconds.
Hold down the power button.
Plug in power
Count to three
Release the power button
You should see the bootloader screen.
If you hold it down too long or not long enough, it simply doesn’t work.
Restore Shield Android TV to Stock
P.s. Personally me I followed this instructions and kind of magically got it in bootloader mode. First done by instruction and then just gave up and pressed randomly and fastboot screen appear. Thanks God I had to done only once, if I would do again I wouldn't had patients
Good luck with this, hope you will get sorted
Here will be link about where I got instructions about hardware boot
http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/
Sent from my Nokia 3310 using free xda app
Thanks a lot fro your help.
I was able to put the box in fastboot mode.
Since I'm not that expert can you tell me where and which rom I have to download (I have a french 16gb version of the box).
Then I'd need to know exactly what commands to performs (even a link to a tutorial is fine).
I really appreciate your help. It seems I can (hopefully) save the box.
EDIT: The fastboot command gave me a (not enough space) when I bricked the box. Is there a risk it could happen again while flashing stock? No idea how much space I have left on the box really.
EDIT2: I found this page: https://developer.nvidia.com/shield-open-source
and I'm downloading this rom called nv-recovery-image-shield-atv-upgrade2_1.zip
and Intend to follow these instructions: http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Can anyone please confirm I'm doing right?
EDIT with joy : I followed all the steps using that rom and it seems everything worked. I reconfiguring the box now. Thanks for help.
basically the procedure I intend to follow is this part (please confirm it's ok):
To flash this recovery image to your SHIELD, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader. Get
DTB file name to use for flashing for your product(see below):
P.s. maybe Since past fastboot commands failed and I only flashed system from zulu99 I could skip the 'fastboot flash boot boot.img' command so if it fails again I still can attempt the fastboot process again?
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb <DTB file name>
puppinoo said:
Thanks a lot fro your help.
I was able to put the box in fastboot mode.
Since I'm not that expert can you tell me where and which rom I have to download (I have a french 16gb version of the box).
Then I'd need to know exactly what commands to performs (even a link to a tutorial is fine).
I really appreciate your help. It seems I can (hopefully) save the box.
EDIT: The fastboot command gave me a (not enough space) when I bricked the box. Is there a risk it could happen again while flashing stock? No idea how much space I have left on the box really.
EDIT2: I found this page: https://developer.nvidia.com/shield-open-source
and I'm downloading this rom called nv-recovery-image-shield-atv-upgrade2_1.zip
and Intend to follow these instructions: http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Can anyone please confirm I'm doing right?
Click to expand...
Click to collapse
You are on the right way with those links
P.s. You can do manual one by one entering or paste and copy those commands or (I'm doing) drag and drop file "flash-all.bat" on cmd previous opened there where you have abd/fastboot etc files and extracted RIGHT FIRMWARE (like shift and right click mouse "open command prompt here"
And after this all sit down and relax
Anyway you are on the right way.
P.s. Hope you download adb fastboot drivers somewhere from Internet !?!
Sent from my Nokia 3310 using free xda app

Att Skipsoft.. all I have now is a large white Google on my Screen..

I had a M build from the original D which I flashed and I saw the LTE was no different from the L so I tried to go back to MDA..D and I made an error or the file was corrupted as all I have is a large white Google. I can get to the bootloader and lock/unlock it but when it is unlocked there is an error message about unable to check corrupted files and press Pause and when I did that it still had message and to press Continue and still it only will go back to the large Google ?
Is my phone beyond repair now as I tried your toolkit and must not have chosen the right options as there is no escaping the White google screen?
I have used and supported your toolkit since the Nexus 5 days but now I am really stumped..
just fastboot flash the factory images. you should be good to go since you can get into the bootloader.
painfree said:
I had a M build from the original D which I flashed and I saw the LTE was no different from the L so I tried to go back to MDA..D and I made an error or the file was corrupted as all I have is a large white Google. I can get to the bootloader and lock/unlock it but when it is unlocked there is an error message about unable to check corrupted files and press Pause and when I did that it still had message and to press Continue and still it only will go back to the large Google ?
Is my phone beyond repair now as I tried your toolkit and must not have chosen the right options as there is no escaping the White google screen?
I have used and supported your toolkit since the Nexus 5 days but now I am really stumped..
Click to expand...
Click to collapse
Like the guy above said to fastboot the factory image.
See the link below, follow step 9
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
Also note in these commands that the xx.xx.img, the xx's are numbers. Just make sure you change the xx to whatever the number is. It will vary depending on version you flash.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
So you are saying that the Skipsoft Toolkit is NOT able to resolve this situation by using any of its options?
painfree said:
So you are saying that the Skipsoft Toolkit is NOT able to resolve this situation by using any of its options?
Click to expand...
Click to collapse
Why use a toolkit in the first place? As you've found out they're more trouble than they're worth. Plus, with a Nexus you really shouldn't need one anyway, these phones are simple to work with. Check out my guide, it has everything you need to know:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
Why use a toolkit in the first place? As you've found out they're more trouble than they're worth. Plus, with a Nexus you really shouldn't need one anyway, these phones are simple to work with. Check out my guide, it has everything you need to know:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I am using windows 10 and I cannot for the life of me figure out the file locations .. How do I do a simple thing as find a file called fastboot.exe on my PC using windows 10 ? this is what I have so far :
http://screencast.com/t/qhapdJk8
I have no idea where bootloader.exe is located and I cannot figure out how to do a simple file search on Windows 10. As a result I cannot open up a command prompt there if I cannot find it..
painfree said:
I am using windows 10 and I cannot for the life of me figure out the file locations .. How do I do a simple thing as find a file called fastboot.exe on my PC using windows 10 ? this is what I have so far :
http://screencast.com/t/qhapdJk8
I have no idea where bootloader.exe is located and I cannot figure out how to do a simple file search on Windows 10. As a result I cannot open up a command prompt there if I cannot find it..
Click to expand...
Click to collapse
Did you follow the instructions in the beginning of the thread to install the SDK and in turn install adb/fastboot? I make no mention of bootloader.exe so I'm not sure where you're getting that from, there's no such thing, you don't know what the bootloader is? It might be a good idea for you to read the prerequisites section and the quick tips section at the beginning of the first post, and the FAQ section in the second post.
Heisenberg said:
Did you follow the instructions in the beginning of the thread to install the SDK and in turn install adb/fastboot? I make no mention of bootloader.exe so I'm not sure where you're getting that from, there's no such thing, you don't know what the bootloader is? It might be a good idea for you to read the prerequisites section and the quick tips section at the beginning of the first post, and the FAQ section in the second post.
Click to expand...
Click to collapse
yes I completed part 1 with all the command prompt tests and someone said to skip to step 9... I read this regarding bootloader and I assumed it was an exe file.. sorry..
"Like the guy above said to fastboot the factory image.
See the link below, follow step 9
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
Also note in these commands that the xx.xx.img, the xx's are numbers. Just make sure you change the xx to whatever the number is. It will vary depending on version you flash.
http://forum.xda-developers.com/nexu...nners-t3206928 "
painfree said:
yes I completed part 1 with all the command prompt tests and someone said to skip to step 9... I read this regarding bootloader and I assumed it was an exe file.. sorry..
"Like the guy above said to fastboot the factory image.
See the link below, follow step 9
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
Also note in these commands that the xx.xx.img, the xx's are numbers. Just make sure you change the xx to whatever the number is. It will vary depending on version you flash.
http://forum.xda-developers.com/nexu...nners-t3206928 "
Click to expand...
Click to collapse
Are you following my instructions as they're written? They're very thorough so should be easy to follow.
Heisenberg said:
Are you following my instructions as they're written? They're very thorough so should be easy to follow.
Click to expand...
Click to collapse
OK I am back to system but there is a message about internal system problem yet it is factory now. .." Android System There's an internal problem with your device. Contact your manufacturer for details"
painfree said:
OK I am back to system but there is a message about internal system problem yet it is factory now. .." Android System There's an internal problem with your device. Contact your manufacturer for details"
Click to expand...
Click to collapse
Which images did you flash? And which build?
Heisenberg said:
Which images did you flash? And which build?
Click to expand...
Click to collapse
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-
01.31.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-01.29.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
MDA089D I have t mobile and all the other builds K L M crippled my in home reception..
painfree said:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-
01.31.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-01.29.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
MDA089D I have t mobile and all the other builds K L M crippled my in home reception..
Click to expand...
Click to collapse
Ok, but you're able to actually boot into Android, right? Or are you not able to? If you're able to it's probably worth trying a factory reset (Settings>Backup & Reset>Factory Data Reset).
Heisenberg said:
Ok, but you're able to actually boot into Android, right? Or are you not able to? If you're able to it's probably worth trying a factory reset (Settings>Backup & Reset>Factory Data Reset).
Click to expand...
Click to collapse
I am able to set up the phone as I normally would but my replacement via RMA just arrived so I will be sending this one back but now I know to avoid the toolkits.

Categories

Resources