Related
Hi all,
I am completely at my wits end here and just don't know what to do
I have successfully unlocked my stock Nexus One boatloader, and have installed superboot to root it.
- I am using Windows 7 64 bit with all USB drivers for the nexus one correctly installed
- I have remembered to reset debuggingt mode in the Nexus USB settings
- Rooted apps seem to be working fine - I've just been playing with the LED torch app and I have a 'Superuser Permission' icon in my programs list
I am attempting to install the Amon_Ra recovery file - I've tried two different versions of it with no joy so far.... 1.7.0 and 1.6.2
I am able to boot into fastboot (with the skateboarding droids) with no probs. I can see the device using fastboot devices. However, when I try to send any recovery image using fastboot, it just hangs there with an empty progress bar on the right hand side of the screen in green that doesn't fill up.... Here is the terminal output:
---
C:\AndroidSDK\android-sdk-windows\tools>fastboot devices
HT9C(-REMOVED-) fastboot
C:\AndroidSDK\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3948 KB)...
---
Anybody have any idea why it hangs here and if there is anything else I can do to maybe figure out why? I'm pretty certain I've almost cracked it - installing this recovery image is a problem
Thanks in advance!
Gil
don't rename the recovery.img file.
Then if that still doesn't work...maybe try using a terminal on your phone. Not sure myself which terminal app works.
SiNJiN76 said:
don't rename the recovery.img file.
Then if that still doesn't work...maybe try using a terminal on your phone. Not sure myself which terminal app works.
Click to expand...
Click to collapse
Thanks for the quick response!
It still fails even when I don't rename the recovery image.
Re 'using a terminal on my phone' - is there a guide to this anywhere? Do I download a shell or something?
TIA!
Gil
Go to market and search Android Terminal Emulator.
Then follow these instructions:
via terminal app
Code:
Copy recovery-RA-nexus-v1.7.0.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.img(press enter)
reboot recovery(press enter)
Got those instructions from the Recovery thread.
It looks like fastboot is not properly detecting your device? Also, did you install "superroot" before attempting to flash recovery image?
Thanks everyone for the help so far.
SiNJiN76 said:
Go to market and search Android Terminal Emulator.
Then follow these instructions:
via terminal app
Code:
Copy recovery-RA-nexus-v1.7.0.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.img(press enter)
reboot recovery(press enter)
Got those instructions from the Recovery thread.
Click to expand...
Click to collapse
I have tried these steps - when I issue the su command, I get root and a dialog box prompting me to allow it. However, when I type the flash_image command, I get the following message:
flash_image: not found
How is it that I don't have the flash_image command on my Nexus?!
aoch88 said:
It looks like fastboot is not properly detecting your device? Also, did you install "superroot" before attempting to flash recovery image?
Click to expand...
Click to collapse
I think fastboot is detecting my device, because I managed to display the serial number (I obsficated most of the output above for security reasons) and I also successfully unlocked the bootloader. After I unlocked the bootloader, I tried to copy over the recovery image, and it just hung, so I then went and installed Modaco's superboot version ERD27 with himem enabled. This allowed me root access but still will not allow me to flash with the recovery image.
In addition, I have noticed that since I installed superboot himem, I am having a couple of network issues. Firstly - my 3G signal has now dropped from virtually full strength all the time to now never more than 50% strength, and frequently gives network errors when accessing the android store. It has also said "emergency calls only" a couple of times and probably worst of all (!) no longer checks my gmail automatically (I have plenty of emails but don't get notified - texts work fine though and my contacts are all still there and my account seems to be linked) - could the superboot have affected this in any way?
Thanks all for your help - I'm getting a little worried I may have totally borked my phone now
Gil
A little extra info if it helps anyone - I just tried to erase the recovery image in fastboot to see if I could then write a new recovery image. Here is the output:
---
C:\AndroidSDK\android-sdk-windows\tools>fastboot devices
HT9CXP8##### fastboot
C:\AndroidSDK\android-sdk-windows\tools>fastboot erase recovery
erasing 'recovery'... FAILED (remote: not allowed)
---
Anybody have any clue what this means?
Try to redownload the recovery image, maybe you got a bad download.
thisisgil said:
when I try to send any recovery image using fastboot, it just hangs there with an empty progress bar on the right hand side of the screen in green that doesn't fill up....
Click to expand...
Click to collapse
Can you try a different USB port? I found when flashing mine that it didn't like USB1.1 only worked on USB2.0
thisisgil said:
A little extra info if it helps anyone - I just tried to erase the recovery image in fastboot to see if I could then write a new recovery image. Here is the output:
---
C:\AndroidSDK\android-sdk-windows\tools>fastboot devices
HT9CXP8##### fastboot
C:\AndroidSDK\android-sdk-windows\tools>fastboot erase recovery
erasing 'recovery'... FAILED (remote: not allowed)
---
Anybody have any clue what this means?
Click to expand...
Click to collapse
Another thing I discovered recently: Never use a port on a USB hub. Always use a USB port on the PC directly. I was having trouble flashing ROMs on my Acer Liquid and they went away when I stopped using a port on the hub.
without a doubt i bet its a naming issue, this is one of those things that go unmentioned and overlooked. either u do or dont have file extensions showing or not and or the .img does or does not need to be changed to .zip, i messed with this for days last year when flashing my g1. just go and change whatever you hide/show known file extensions is set to and see if ur problem is solved.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
AndyBurns said:
Can you try a different USB port? I found when flashing mine that it didn't like USB1.1 only worked on USB2.0
Click to expand...
Click to collapse
Thank you AndyBurns. I registered just to say that. You saved me a lot of time.
I had the same problem. Had the USB cable plugged into my front 1.1 ports instead of the back 2.0 ports. Switch ports and now I'm good to go.
Thank you.
Hi all -
Just wanted to post a follow up to this message, in the hope that it may help someone in the future!
Basically, I was not using the original USB cable that came with the nexus one (lost it), and instead was using a cable that I bought from a mobile phone retailer - it was basically one of those 6-in-1 multi USB cables where I had to put an adaptor on the end to switch it from mini to micro USB to fit the Nexus one.
Anyhow, for some reason, despite the fact that I could charge the phone using this new cable, and access it through device manager, explore the contents of the phone, root it etc etc, it would not do the flash as described above. I went out and bought a dedicated 1 metre gold plated micro USB cable, and it worked great
Dodgy cables - should have thought of this before I spent days frigging around and maybe even almost bricking the phone with a bad flash
Hi guys, first at all, I'm noob with android, and I'm trying to root+up room for my first android device : the Nexus 7.
I used Nexus root tool kit 1.6.3 to unlock and root successfully my device; however, when I tried to up rom for the device, I screwed up everything. I tried Smooth room first and stuck with the "boot loop" screen :
"The green robot with the green circle around"_I can't upload pics because I have less than 10 post.
Luckily I could use Nexus root tool kit to restore my device to factory setting. But I decided to give it a try one more time with the other rom, the ATOM flash rom. This time after I swipe out all factory data, catch data.... the installer say "fail to install" and give me the option to: "try again", "swipe data again", "reboot". I choice "reboot" and this time the screen stuck at this :
"The white word GOOGLE in the middle and the CLOCK in the middle end"
I tried to reset to factory setting like before but I wasn't that lucky this time, the Nexus root tool kit keep saying "ADB device was not found". (noticed that I already have the right driver for the device because ADB was found before).
Right now I can return to bootloader by holding power button and volume down button, but I can't do anything else.
Please, people, can anyone help me with this? I really need some help here.
Thanks.
quocviet114 said:
Hi guys, first at all, I'm noob with android, and I'm trying to root+up room for my first android device : the Nexus 7.
I used Nexus root tool kit 1.6.3 to unlock and root successfully my device; however, when I tried to up rom for the device, I screwed up everything. I tried Smooth room first and stuck with the "boot loop" screen :
"The green robot with the green circle around"_I can't upload pics because I have less than 10 post.
Luckily I could use Nexus root tool kit to restore my device to factory setting. But I decided to give it a try one more time with the other rom, the ATOM flash rom. This time after I swipe out all factory data, catch data.... the installer say "fail to install" and give me the option to: "try again", "swipe data again", "reboot". I choice "reboot" and this time the screen stuck at this :
"The white word GOOGLE in the middle and the CLOCK in the middle end"
I tried to reset to factory setting like before but I wasn't that lucky this time, the Nexus root tool kit keep saying "ADB device was not found". (noticed that I already have the right driver for the device because ADB was found before).
Right now I can return to bootloader by holding power button and volume down button, but I can't do anything else.
Please, people, can anyone help me with this? I really need some help here.
Thanks.
Click to expand...
Click to collapse
Get the FACTORY IMAGE for your device from here...
https://developers.google.com/android/nexus/images
Unzip to the folder wherever your FASTBOOT.EXE and ADB.EXE files are located and run the FLASHALL script... and with the device in BOOTLOADER mode.
This should reflash back to stock.
Rgrds,
Ged.
GedBlake said:
Get the FACTORY IMAGE for your device from here...
Unzip to the folder wherever your FASTBOOT.EXE and ADB.EXE files are located and run the FLASHALL script... and with the device in BOOTLOADER mode.
This should reflash back to stock.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you for the reply but where are the files FASTBOOT.EXE and ADB.EXE located? I can't access to the internal storage of the device, and how to run the Flashall script?
There have been many similar cases like yours on this forum and I see it usually after the use of toolkits. Not that toolkits are badly written, but people who usually use them don't know what to do when things go wrong. As long as you can get into bootloader mode (=fastboot mode), you can restore your device with fastboot. Take this time to learn a bit about your device and the two only programs you'll ever need for it: ADB and FASTBOOT. You use fastboot when in bootloader mode and adb outside the bootloader.
Use this sticky to return to stock: http://forum.xda-developers.com/showthread.php?t=1907796 . You can skip a few steps in it though. For example, if your drivers are already set up and you have adb en fastboot somewhere (you can find them somewhere in the installation folder of the toolkit) then you don't need to download java and the android SDK. You also don't need to reflash the bootloader if you already use the latest version. Just read and think while you follow one of the best guides you can find on this forum.
To learn more about adb and fastboot, just type the name of the program in a terminal window and you will see a list with all commands associated with it. My recommendation is to flash a custom recovery (for example TWRP): you can type fastboot flash recovery name of recovery. You can use TWRP to root your device afterworths (TWRP will present you with a warning when you reboot your device through it). You can also make nandroid backups with it. In the future, make nandroid backups, because they will help you when you soft brick your device again.
Good luck!
quocviet114 said:
Thank you for the reply but where are the files FASTBOOT.EXE and ADB.EXE located? I can't access to the internal storage of the device, and how to run the Flashall script?
Click to expand...
Click to collapse
FASTBOOT.EXE and ADB.EXE are part of the Android SDK and as such should be on your PC... so you don't need to access internal storage on your Nexus 7.
(In fact you can't, if the N7 is in BOOTLOADER MODE, which of course it needs to be to flash back to STOCK).
The Flash-all script is part of the Factory image, and is run in a COMMAND PROMPT window... to completely reflash back to STOCK.
-----
The toolkit you're using must use FASTBOOT to accomplish flashing... so you must have FASTBOOT somewhere on your PC.
Rgrds,
Ged.
Are you using twrp to flash your custom rom? Some of the custim rom must be flash it with cwm.
Try to install cwm thru fastboot or adb. Then flash again.
Good luck mate.
Sent from my GT-N7100 using xda premium
I'll try your instruction as soon as I go back from work. Thank a lot you guys. I appreciated!
I did it! Thank you so much everyone! I think just root and use the stock rom is ok with me, I don't want to risk again!
quocviet114 said:
I did it! Thank you so much everyone! I think just root and use the stock rom is ok with me, I don't want to risk again!
Click to expand...
Click to collapse
Awesome! Hopefully it was an informative (an maybe even fun) experience.
Also, as long as pushing all three buttons on the side of your nexus simultaniously (for up to 15 or more or less) seconds enters bootloader/fastboot mode, nothing is ever bricked and your nexus can (almost allways) be safed. The only ways to really hard brick and ruin your nexus is to flash wrong or corrupt bootloaders (so always be extra carefull if that ever needs to happen).
quocviet114 said:
I did it! Thank you so much everyone! I think just root and use the stock rom is ok with me, I don't want to risk again!
Click to expand...
Click to collapse
Well, that's very good news indeed, quocviet114... glad you got it sorted.
I remember when I was a beginner and had similar issues to yours,... upon resolution, the relief was palpable.
-----
ps. you should edit your thread title to include the word SOLVED...
Rgrds,
Ged.
I used the toolkit for mac and it unlocked me, but when it came to the next steps it said device not found and then told me to highlight recovery and press start, when I do I get the android with the red ! symbol.
Can someone help me?
That symbol is a security feature within the stock recovery, volume up and power to access the stock recovery.
Sent from my Nexus 4 using Tapatalk 4
I tried that it's not working I press up then power the phone reboots and the red ! symbol shows up...
I searched and saw hold power and press up when I see the red ! but it just reboots the phone...
help please?
Sent from my GT-N5110 using Tapatalk 4
ADB wont work in stock recovery
roguedroid said:
I tried that it's not working I press up then power the phone reboots and the red ! symbol shows up...do you know the adb instructions on how to push supersymmetric and cwm?
edit my adb now won't recognize my phone even though it did a few mins ago...
I'm frustrated, been trying to access the stock recovery for the past several mins and simply can't.
help please?
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
For me also Stock recovery never worked. Just try to flash CWM or TWRP.
Btw, What toolkit did you use and how did you install the drivers. Please answer these, so that someone can help you better.(Or is it just the 'mac toolkit' ?)
My suggestion: PLZ DO NOT USE TOOLKIT. If you are stuck at some point while using the toolkit, then you'll not know what went wrong and how you can correct it. Do it manually. It is the most hassle-free method. Trust me.
I think that ADB will not work in stock recovery(may be you can boot normally into your phone and then try adb). The thing which you are looking for is 'fastboot'.
1) Restart ur phone (Power Button + Volume Down, i guess) and land in the bootloader and connect your phone to PC.
2) In CMD prompt(or Terminal), type 'fastboot devices'. If your device gets listed here, then fastboot is working and drivers are properly installed. If not, then drivers are not properly installed in your PC. You need both ADB and FASTBOOT drivers. Install them properly.
PS: For MAC, i think the command is slightly different. Something like './fastboot devices' . Please look for the same in this forum or just google it and find out.
3) Follow this guide for flashing CWM and Rooting.
http://forum.xda-developers.com/showthread.php?t=2266654
4) For properly installing the Drivers, read " A. Install the drivers " in the below thread (actually you can read the entire thread )
http://forum.xda-developers.com/showthread.php?t=2010312&highlight=cwm+6+0+3+5
My knowledge is limited to Windows PC, sorry if I am not of much help. Thanks !
badhri said:
For me also Stock recovery never worked. Just try to flash CWM or TWRP.
Btw, What toolkit did you use and how did you install the drivers. Please answer these, so that someone can help you better.(Or is it just the 'mac toolkit' ?)
My suggestion: PLZ DO NOT USE TOOLKIT. If you are stuck at some point while using the toolkit, then you'll not know what went wrong and how you can correct it. Do it manually. It is the most hassle-free method. Trust me.
I think that ADB will not work in stock recovery(may be you can boot normally into your phone and then try adb). The thing which you are looking for is 'fastboot'.
1) Restart ur phone (Power Button + Volume Down, i guess) and land in the bootloader and connect your phone to PC.
2) In CMD prompt(or Terminal), type 'fastboot devices'. If your device gets listed here, then fastboot is working and drivers are properly installed. If not, then drivers are not properly installed in your PC. You need both ADB and FASTBOOT drivers. Install them properly.
PS: For MAC, i think the command is slightly different. Something like './fastboot devices' . Please look for the same in this forum or just google it and find out.
3) Follow this guide for flashing CWM and Rooting.
http://forum.xda-developers.com/showthread.php?t=2266654
4) For properly installing the Drivers, read " A. Install the drivers " in the below thread (actually you can read the entire thread )
http://forum.xda-developers.com/showthread.php?t=2010312&highlight=cwm+6+0+3+5
My knowledge is limited to Windows PC, sorry if I am not of much help. Thanks !
Click to expand...
Click to collapse
I used the nexus 4 Mac rootkit I found in here.
It unlocked my phone fine. But when it came to installing a recovery and root it didn't.
Neither my adb or fastboot are working now before I unlocked and I messed around and they worked now nada ...
I went to YouTube saw my problem tried pressing volume up and power like in the video and it just gives me a black screen and either turns the phone off or reboots it normally...not sure if in supposed to hold power and let go of volume or vice versa.
I placed all the files on the storage I just need to access stock recovery which I strangely cannot now...
Tried framearoot and got nowhere.
Very frustrating
Sent from my GT-N5110 using Tapatalk 4
Sort out the drivers and adb,fastboot
roguedroid said:
I used the nexus 4 Mac rootkit I found in here.
It unlocked my phone fine. But when it came to installing a recovery and root it didn't.
Neither my adb or fastboot are working now before I unlocked and I messed around and they worked now nada ...
I went to YouTube saw my problem tried pressing volume up and power like in the video and it just gives me a black screen and either turns the phone off or reboots it normally...not sure if in supposed to hold power and let go of volume or vice versa.
I placed all the files on the storage I just need to access stock recovery which I strangely cannot now...
Tried framearoot and got nowhere.
Very frustrating
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
Just as I mentioned, i also had the same problem with stock recovery. So I simply flashed a Custom one(CWM, in my case)
Get the ADB and FASTBOOT working and that'll solve your recovery problem. Try fiddling with your drivers again. Not sure how to do that in MAC. If FASTBOOT is working, the you can boot into a Custom Recovery(you need not even flash it) and perform whatever you need to.
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Again, look at the efrant's guide i referred above; i took this from there only.Remember to replace 'customrecovery.img', with the actual downloaded custom recovery image name.
Or you can try posting your problem with the toolkit, in mac toolkit's thread.
I have been youtubing everything and finally got to
Reboot system
apply update from adb
wipe data/factory reset
wipe cache partition.
I now can get adb working so I tried ./adb sideload cwm from my desktop and it is giving me signature verification failed. installation aborted.
What can I do to resolve this?
I searched xda and no one can solve this issue from the threads I've read.
I fixed it! Whooohoooo! Installed cwm and root ....now to install pa rom.
Thanks for the help!
Sent from my GT-N5110 using Tapatalk 4
I apologize if this question has been answered already, but I just spent 15 minutes using the search button and could not find a response.
I just installed Matr1x v10.5 (http://forum.xda-developers.com/showthread.php?t=2007231) onto my Nexus 4 but it had JB 4.2. Based on the version notes of the thread, I assumed that it was backwards compatible with my phone and therefore installed the new version on my Nexus 4. Now every time I turn on my Nexus 4 the screen is blank. What can I do to fix this issue? Will it require a reset so that all my data is lost? Thanks.
What do you mean with '... The screen is blank'?
Can you get past the google bootanimation?
Sent from my Nexus 4 using xda app-developers app
failly said:
What do you mean with '... The screen is blank'?
Can you get past the google bootanimation?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Nope, basically once I turn it on I see the "Google" text, and then the screen goes blank as in it's black. Basically the back light is on and you can see that it's on but the background is still black.
pooq said:
Nope, basically once I turn it on I see the "Google" text, and then the screen goes blank as in it's black. Basically the back light is on and you can see that it's on but the background is still black.
Click to expand...
Click to collapse
Go into recovery and flash the stock kernel. If that doesnt work you need to do a full wipe and reflash the rom.
failly said:
What do you mean with '... The screen is blank'?
Can you get past the google bootanimation?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Chromium_ said:
Go into recovery and flash the stock kernel. If that doesnt work you need to do a full wipe and reflash the rom.
Click to expand...
Click to collapse
Theoretically, if I flash v10.0 (which accommodates JB 4.2) it should fix the issue right?
I'm at a dilemma because I do not know if there are any other ways to insert the kernel into my phone as there is no microSD option on the Nexus 4. Does anyone know how I could potentially get the file into my phone?
pooq said:
Theoretically, if I flash v10.0 (which accommodates JB 4.2) it should fix the issue right?
I'm at a dilemma because I do not know if there are any other ways to insert the kernel into my phone as there is no microSD option on the Nexus 4. Does anyone know how I could potentially get the file into my phone?
Click to expand...
Click to collapse
Can you access recovery? If yes mount your storage and you can transfer the files.
Sent from my Nexus 4 using xda app-developers app
failly said:
Can you access recovery? If yes mount your storage and you can transfer the files.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I had already tried that, but once I connected my usb into my laptop I still couldn't transfer any files over.
In the end I reset my phone to factory settings, so the display still shows "Google". Just to confirm, the reason why this logo has been displayed on my phone for a while is because it is working to restore the factory setting (e.g. OS) correct?
pooq said:
I had already tried that, but once I connected my usb into my laptop I still couldn't transfer any files over.
In the end I reset my phone to factory settings, so the display still shows "Google". Just to confirm, the reason why this logo has been displayed on my phone for a while is because it is working to restore the factory setting (e.g. OS) correct?
Click to expand...
Click to collapse
I can't tell for sure since it never happend to me but I don't think if you choose to reset your phone to factory settings it will stay at the google logo.
If you choose to reset to facory settings I think you just will boot into recovery with that an android standing with something in his belly with a loading bar.
You can try this.
1.Boot into bootloader.
2A.Flash TWRP with the fastboot command and go to step 3.
2B.Flash stock N4 image with the fastboot command and profit!
3a.Try to mount storage and transfer another rom.
3b.Restore a backup.
Hopefully this works.
Sent from my Nexus 4 using xda app-developers app
failly said:
I can't tell for sure since it never happend to me but I don't think if you choose to reset your phone to factory settings it will stay at the google logo.
If you choose to reset to facory settings I think you just will boot into recovery with that an android standing with something in his belly with a loading bar.
You can try this.
1.Boot into bootloader.
2A.Flash TWRP with the fastboot command and go to step 3.
2B.Flash stock N4 image with the fastboot command and profit!
3a.Try to mount storage and transfer another rom.
3b.Restore a backup.
Hopefully this works.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I have tried the above instructions up to step 3 because it did not work for me.
It shows the only files in my internal storage(/sdcard) are a file that says (Up A Level) and TWRP. Also, whenever I want to reboot it prompts "No OS Installed! Are you sure you wish to reboot?" At this point I am only interested in a factory reset now so that I can reinstall the initial JB 4.0 that came with the Nexus 4 and then upgrade to JB 4.3. However, whenever I do factory reset via recovery mode, I am stuck with an empty phone with the files I mentioned above.
What can I do to fix the situation? Thanks.
pooq said:
I have tried the above instructions up to step 3 because it did not work for me.
It shows the only files in my internal storage(/sdcard) are a file that says (Up A Level) and TWRP. Also, whenever I want to reboot it prompts "No OS Installed! Are you sure you wish to reboot?" At this point I am only interested in a factory reset now so that I can reinstall the initial JB 4.0 that came with the Nexus 4 and then upgrade to JB 4.3. However, whenever I do factory reset via recovery mode, I am stuck with an empty phone with the files I mentioned above.
What can I do to fix the situation? Thanks.
Click to expand...
Click to collapse
I think the reason that a factory reset won't help since there is no OS on the phone so it cannot reset something that isn't there.
And with the steps I mentioned, can you get into bootloader or does it directly boot into recovery.
Another thing you can try(I don't think it will work but I never tried it so you never know)
Download this toolkit:
http://forum.xda-developers.com/showthread.php?t=2015469
There is an option to flash to stock completly, that will maybe do the trick.
Good luck!
Sent from my Nexus 4 using xda app-developers app
failly said:
I think the reason that a factory reset won't help since there is no OS on the phone so it cannot reset something that isn't there.
And with the steps I mentioned, can you get into bootloader or does it directly boot into recovery.
Another thing you can try(I don't think it will work but I never tried it so you never know)
Download this toolkit:
http://forum.xda-developers.com/showthread.php?t=2015469
There is an option to flash to stock completly, that will maybe do the trick.
Good luck!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I can get into bootloader fine, it does not boot directly into recovery.
My Nexus 4 is already flashed with TWRP. I have installed the program from the link you provided, however, I have not used it to flash my phone again as one of the prerequisites to using the program is selecting which OS version I am using (at this point I am not using any) and want to prevent any further issues from occurring.
It seems like I can't really do anything with my phone unless I get a JB OS reinstalled, which is what I am currently struggling with. I am presently trying to find a way to copy the downloaded Nexus image files provided online into my internal storage so I can install them.
pooq said:
I can get into bootloader fine, it does not boot directly into recovery.
My Nexus 4 is already flashed with TWRP. I have installed the program from the link you provided, however, I have not used it to flash my phone again as one of the prerequisites to using the program is selecting which OS version I am using (at this point I am not using any) and want to prevent any further issues from occurring.
It seems like I can't really do anything with my phone unless I get a JB OS reinstalled, which is what I am currently struggling with.
Click to expand...
Click to collapse
Okay since you can get into bootloader thats great news!
Have you tried to manually download the nexus 4 image from google?
NOTE this are direct download links:
4.3:
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
4.2.2:
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
Here is an excellent guide:
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
Scenario #2 on that guide suits you!
I think this will do the trick!
Sent from my Nexus 4 using xda app-developers app
You just have to do the following :
A) flash a recovery via fastboot (fastboot flash recovery recovery.zip)
B) now go ahead and boot from your recovery, and push the rom of your choice, in case you don't have one already inside your sdcard (adb push ROM.zip /sdcard/ROM.zip)
C) flash your recently copied rom of choice to your phone. (if necessary, wipe data, cache and dalvik cache)
failly said:
Okay since you can get into bootloader thats great news!
Have you tried to manually download the nexus 4 image from google?
NOTE this are direct download links:
4.3:
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
4.2.2:
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
Here is an excellent guide:
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
Scenario #2 on that guide suits you!
I think this will do the trick!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I just spent a couple of hours reading through the guides (and trying them out) which led me to several other guides. To be incredibly honest, I am completely confused as there is a plethora of new information thrown at me. I have to pose several questions before I continue:
1) When you say bootloader, are you referring to the fastboot bootloader screen that pops up after holding the volume down button and the power button? I just wanted to confirm this as I am starting to feel you are referring to something different after reading several guides.
2) Is the scenario 2 guide you posted basically a method to "sideload" the JB 4.3 into the storage of my Nexus 4 so I can install it via Recovery Mode?
I tried installing the drivers but I cannot seem to do it successfully as I do not even have a starting OS for my phone in the first place. I can not access a theoretical "Developer Mode" either from when I first rooted my phone.
So basically, I do not understand how I can get the direct downloads from Google (the JB 4.3 files) and get them into the internal storage of my Nexus 4 to install the OS.
Is there a simpler way to do this? If not, here is my current progress. At the moment I am stuck at this guide (http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1) from the previous link you linked and am between C-D. I cannot get my laptop to recognize my device via fastboot devices in command prompt (D). To be honest, this is the second time I've seen this guide but could not get it working properly which is why I used the file provided at (http://forum.xda-developers.com/showthread.php?t=2015469) to root my Nexus 4.the OS[/B]. Is there a simpler way to do this? At the moment I am stuck at this guide (http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1) from the previous link you linked and am between C-D. I cannot get my laptop to recognize my device via fastboot devices in command prompt (D). To be honest, this is the second time I've seen this guide but could not get it working properly which is why I used the file provided at (http://forum.xda-developers.com/showthread.php?t=2015469) to root my Nexus 4.
Yes, the bootloader is the one where you press vol down and the power button together, that's the place where you select to go to the recovery, use fastboot.
First thing you got to do is turn on your phone on the bootloader as mentioned above. Then, assuming you downloaded this: [NEXUS 4 TOOLKIT V2.0.0] from here http://forum.xda-developers.com/showthread.php?t=1995688, open up command prompt and go to this address with "cd C:\Google_Nexus_4_ToolKit" or where you decided to install your toolkit. On windows explorer, go there and rename fastboot-toolkit or whatever it is called to fastboot to make things simpler.
Type in cmd: fastboot devices to check if it recognizes your phone.
If it doesn't; then install these drivers (you should have your device already connected via USB to your computer): https://www.dropbox.com/s/a808emeelvxkwyc/usb_driver.rar
Go to Control Panel\Hardware and Sound > Device Manager. Your phone should appear with an exclamation mark somewhere, right click it and click on update driver:
-Click on browse my computer software
-Let me pick from a list of device drivers on my computer
-Have disk
-Browse for where you downloaded the drivers I linked you to then click ok.
-You should find within the next page something that says Android Bootloader Interface, double click it and finish the installation.
After that's done, then type in fastboot devices on cmd again, it should show up now.
Then, go to here and download TWRP 2.6.0.0 http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.0.0-mako.img , that will be your recovery. After you've downloaded move it to C:\Google_Nexus_4_ToolKit to make matters easier.
NOTE: IF YOUR BOOTLOADER IS LOCKED YOU WILL HAVE TO UNLOCK IT , this can be done by typing fastboot oem unlock on command prompt
Now, simply type in this command: fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img you will now have a recovery on your device.
With the volume keys, choose to boot from the recovery. TWRP will load, while its loading, rename adb-toolkit to adb to make things easier. When its done loading, type in adb devices to see if it recognizes your phone, if it doesn't use your drivers again but this time instead of choosing Android Bootloader Interface, pick the one that says ADB.
When that's done, and it recognizes your device with the adb devices command you can now proceed to "push" or "copy/move a ROM you've downloaded in your computer towards your phone".
Of course you have to download a ROM, like Paranoid Android for example: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-3.69-20130722.zip , along with its GApps: http://goo.im/devs/paranoidandroid/roms/gapps/pa_gapps-full-4.2-20130719-signed.zip
You might have to even update your radio and bootloader in the future too, but let's leave it at that for now.
After you are done downloading the ROM of your choice, then type in these commands (assuming ADB works)
adb push pa_mako-3.69-20130722.zip /sdcard/
adb push pa_gapps-full-4.2-20130719-signed.zip /sdcard/
Having moved these two files inside your phone, now its time to flash them.
1) Go to Wipe on TWRP and simply swipe to factory reset
2) Go back and click on Install, look for pa_mako-3.69-20130722.zip and then add pa_gapps-full-4.2-20130719-signed.zip to the queue, swipe to install.
After that's done, simply reboot your phone and it should start booting up Paranoid Android and you're done. Might give you a few issues if you have an old radio and bootloader, but that can be fixed by flashing the new versions of these two in TWRP. Can be found here: https://www.copy.com/s/JniBu/4.3 files (mako) (these can be pushed via ADB like before, or you can simply download them on your phone when its working)
Hope this helps, don't think I can be more detailed.
wammie said:
Yes, the bootloader is the one where you press vol down and the power button together, that's the place where you select to go to the recovery, use fastboot.
First thing you got to do is turn on your phone on the bootloader as mentioned above. Then, assuming you downloaded this: [NEXUS 4 TOOLKIT V2.0.0] from here http://forum.xda-developers.com/showthread.php?t=1995688, open up command prompt and go to this address with "cd C:\Google_Nexus_4_ToolKit" or where you decided to install your toolkit. On windows explorer, go there and rename fastboot-toolkit or whatever it is called to fastboot to make things simpler.
Type in cmd: fastboot devices to check if it recognizes your phone.
If it doesn't; then install these drivers (you should have your device already connected via USB to your computer): https://www.dropbox.com/s/a808emeelvxkwyc/usb_driver.rar
Go to Control Panel\Hardware and Sound > Device Manager. Your phone should appear with an exclamation mark somewhere, right click it and click on update driver:
-Click on browse my computer software
-Let me pick from a list of device drivers on my computer
-Have disk
-Browse for where you downloaded the drivers I linked you to then click ok.
-You should find within the next page something that says Android Bootloader Interface, double click it and finish the installation.
After that's done, then type in fastboot devices on cmd again, it should show up now.
Then, go to here and download TWRP 2.6.0.0 http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.0.0-mako.img , that will be your recovery. After you've downloaded move it to C:\Google_Nexus_4_ToolKit to make matters easier.
NOTE: IF YOUR BOOTLOADER IS LOCKED YOU WILL HAVE TO UNLOCK IT , this can be done by typing fastboot oem unlock on command prompt
Now, simply type in this command: fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img you will now have a recovery on your device.
With the volume keys, choose to boot from the recovery. TWRP will load, while its loading, rename adb-toolkit to adb to make things easier. When its done loading, type in adb devices to see if it recognizes your phone, if it doesn't use your drivers again but this time instead of choosing Android Bootloader Interface, pick the one that says ADB.
When that's done, and it recognizes your device with the adb devices command you can now proceed to "push" or "copy/move a ROM you've downloaded in your computer towards your phone".
Of course you have to download a ROM, like Paranoid Android for example: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-3.69-20130722.zip , along with its GApps: http://goo.im/devs/paranoidandroid/roms/gapps/pa_gapps-full-4.2-20130719-signed.zip
You might have to even update your radio and bootloader in the future too, but let's leave it at that for now.
After you are done downloading the ROM of your choice, then type in these commands (assuming ADB works)
adb push pa_mako-3.69-20130722.zip /sdcard/
adb push pa_gapps-full-4.2-20130719-signed.zip /sdcard/
Having moved these two files inside your phone, now its time to flash them.
1) Go to Wipe on TWRP and simply swipe to factory reset
2) Go back and click on Install, look for pa_mako-3.69-20130722.zip and then add pa_gapps-full-4.2-20130719-signed.zip to the queue, swipe to install.
After that's done, simply reboot your phone and it should start booting up Paranoid Android and you're done. Might give you a few issues if you have an old radio and bootloader, but that can be fixed by flashing the new versions of these two in TWRP. Can be found here: https://www.copy.com/s/JniBu/4.3 files (mako) (these can be pushed via ADB like before, or you can simply download them on your phone when its working)
Hope this helps, don't think I can be more detailed.
Click to expand...
Click to collapse
The first thing I'd like to do before reporting my progress report is to thank you and failly for taking the time to help me out. You both have contributed tremendously in trying to help me out with this, so I would like to thank you both for that.
1) I had installed the sdk program and changed the adb path (following this guide http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/)
Following wammie's guide:
2) Booted into bootloader
3) Downloaded and installed NEXUS 4 TOOLKIT V2.0.0 (had used it before but it didn't work for me so I relied on a different program to root my phone). Renamed fastboot-toolkit to fastboot
4) Typed fastboot devices in in cmd, does not recognize phone
5) Uninstalled current usb drivers and installed usb drivers provided. The driver I chose to install for was titled "Android". The other ! mark was "Base System Device" which was something I had never seen before until today when I had reinstalled usb drivers
6) Typed fastboot devices in cmd again and still nothing has changed
I am unable to continue any further as fastboot does not recognize my phone when I have it under bootloader. I had downloaded all the files that were recommended in your post. I think the reason why I cannot access fastboot devices is because there is literally no OS running in my phone. I could be wrong though.
I guess I'll take a break and call it a night since I've been trying to fix this problem the past 13 hours or so. Any additional feedback and support is appreciated!
Additional Notes: I have tried this both on my laptops (Windows 8) and on my desktop PC (Windows 7)
Luckly, if windows doesn't recognize your device while in fastboot it isn't because you don't have a OS installes but because not correctly set up drivers.
I posted a link some posta ago about a toolkit:
http://forum.xda-developers.com/showthread.php?t=2015469
When opening the program at the top there is a button called full driver installation, press it and follow the instructions.
Sent from my Nexus 4 using xda app-developers app
http://i.imgur.com/sOT7FGh.png
http://i.imgur.com/WNEKb0z.png
http://i.imgur.com/vUmTDcZ.png
http://imgur.com/da7NGwB
http://i.imgur.com/bjmhXZv.png
This is what you should do when you are updating the drivers, its imperative you get those drivers working. Otherwise, you won't get access to fastboot.
Oh I would recommend using a Windows 7 PC.
Windows 8 can also do the trick but you maybe need to disable driver signature enforcement, so you better go with windows 7 for now.
Sent from my Nexus 4 using xda app-developers app
Status Update:
I had spent a whole day reformatting my Windows 7 machine and am back at it. I have made a bit more progress than before.
1) After typing in fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img in command prompt, under the "List of devices attached" it is blank (i.e. there is no device attached). http://i.imgur.com/TnyBCKS.png
2) I have successfully installed the usb driver on my PC the first time when the only explanation mark was titled "Android", however the only Android option at the moment now is labelled "Android Bootloader Interface". No such thing as ADB (or any variations including Android ADB Interface) exists.
3) In TWRP Recovery mode, I see an exclamation mark titled mako but I believe that is irrelevant. I have tried installing the drivers to this just in case but failed. I then tried it again in Bootloader mode and mako is gone and Android Device pops up again with "Android Bootloader Interface"
4) I have tried restarting my PC and repeating the above steps.
Edit:
5) The only time I see an Android Composite ADB Interfaces is when I boot normally to the "Google" screen. However, I cannot move any of my ROMS over into my phone. When I typed "adb devices" it shows a bunch of characters with offline beside it. I do not have any options to reinstall any drivers for this.
From my understanding,I should be able to access the Android Composite ADB Interface while in recovery mode, which should let me transfer my ROMs over... but the issue is I cannot access Android Composite ADB Interface while in recovery mode.
Also, is there any reason why I shouldn't use the official JB 4.3 img as the ROM I want to install on my phone?
I have the lg g2 from at&t and yesterday i went from cm10.2 back to the stock backup i had for the g2 and received the OTA update. I didnt think much of it and downloaded it, now i am stuck on the endless loop ending in the TWRP screen, I have about 3 back ups but every time i try to restore it it just ends up back in the recovery screen. I've tried to do what i've found on the forum as far as using terminal command from twrp , but all i get is a list of folders, i tried using adb but because of the phone being in it's current state the drivers wont install correctly on the computer, so it doesnt register. Pretty stuck right now and dont know what else to try or do , any help will be appreciated. thank you
Look this
forum.xda-developers.com/showthread.php?t=2451696
I cant do that method because option 1 , adb cant communicate with my phone due to the drivers not being able to install correctly and i tried option 2 but i dont see where to enter the command in terminal command , all i see is a directory of folders
In Twrp,go in Terminal and Press Select
Write this line:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
And go - finish
Here again accurately described
dd[space]if=/dev/zero[space]of=/dev/block/platform/msm_sdcc.1/by-name/fota
[Space] stands for space bar
I can't thank you enough for taking the time to help me out with this, thank you and forgive my ignorance with the whole terminal thing i am still new at all of this .