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?
Related
***TL;DR AT THE BOTTOM***
*^*EDIT 2!!*^*
Utilizing Cerberus, I was able to get passed the boot animation into the lock screen, though the Launcher is, for all intents and purposes, nonexistent. However, I was able to install Nova Launcher and can go to a home screen just fine. THIS IS NOT SATISFACTORY. I want to get back to STOCK Launcher, but it apparently does not exist anymore. I've managed to copy over my backup of Launcher2.apk, but it still refuses to acknowledge its existence. Can I get an update.zip that'll reinstall the default launcher from someone? I can boot into recovery via ROM Manager now I suppose!
+++EDIT!+++
+++~~~I have discovered that my problem is not the device being stuck in boot up, but that the boot animation will not cease--as +in the device is actually powered on, just displaying the boot animation like a screen saver. I cannot boot into recovery as I get +the Google splash screen and it never goes anywhere, my bootloader is freezing every time I plug it into my computer, and the +drivers will not install. My computer cannot detect fastboot and I can't connect to the Nexus via adb either. I CAN access internal +storage but that's about the extent of what I can do.+++~~~
Long version:
I decided I wanted to change the App Drawer icon from stock to a Nexus X that inverted its colours when pressed. I found the icon, converted it to png, inverted the colours and everything was going fine.
After a while I finally managed to find the right icons to replace in the system apk file "launcher2.apk". "ic_allapps.png" and "ic_allapps_pressed.png" or something very similar. I simply replaced them with my two icons, installed my modified launcher2.apk, and that was it.
Immediately, my home wouldn't open at all, no matter how many times I pressed the home button. It just would not exit the app I had up. So I started backing and ended up in an infinite back loop. I powered off the device, waited a minute, and powered it back on.
It came to the usual "Google" screen with the unlocked symbol at the bottom, no problems. However, then it started playing the boot animation. The boot animation never stopped. It looped infinitely. I tried resetting the tablet a few times for the same result. It was after 3 am and I had to get up for work in 4 and a half hours. I thought that maybe it was gonna take a while. So I flipped the Nexus over while it was "booting up" and went to sleep.
When I woke up and checked the tablet at 7:30, it was STILL booting up. Obviously I had screwed something up.
Now, stupid me, I had never flashed CWM recovery on my Nexus 7 (haven't had it that long), so all I'm stuck with is STOCK Recovery. I'm pretty sure I can rescue the Nexus by factory resetting it or something similar, but I'd rather try to save it first. All I modified was a LAUNCHER application, so I'm pretty sure the current state of the Nexus itself shouldn't be too far gone. Is there any way to save the Nexus WITHOUT a data wipe? And if the data wipe DOESN'T fix my problem, is it possible to somehow flash a stock ROM through stock Android Recovery?
***TL;DR***
I modified launcher2.apk and replaced "ic_allapps.png" and "ic_allapps_pressed.png" with two customized .png files (which I renamed to their appropriate file names). Now my Nexus is stuck on the boot animation indefinitely. I would like to save all of my data, as a data wipe would be inconvenient, but if I must do one I shall. I am on a stock ROM and a stock Recovery. If a data wipe/factory reset will not save my device, is it possible to flash a stock ROM through regular Android Recovery?
===Related but irrelevant to the problem===
Is it completely impossible to change the stock App Drawer icon to something different? I'd rather not have to get a different launcher app just to create a Nexus theme! I did a little more research and found that I should've modified the "all_apps_button_icon.xml" file as well, but I have NO idea how to do that.
Many thanks,
VonDerThWood.
As long as you can get into the bootloader you can flash back to stock using fastboot and the image from here
NeoMagus said:
As long as you can get into the bootloader you can flash back to stock using fastboot and the image from here
Click to expand...
Click to collapse
no need to flash back to stock, silly advice. just flash a custom recovery and flash a stock rooted rom. flashing a stock rooted rom will replace what you messed up on. dont wipe.
simms22 said:
no need to flash back to stock, silly advice. just flash a custom recovery and flash a stock rooted rom. flashing a stock rooted rom will replace what you messed up on. dont wipe.
Click to expand...
Click to collapse
How can I reflash the ROM on stock Android recovery? Googling that returns CWM results.
He is suggesting you flash custom recovery with fastboot and just flash over top of what you did thru the custom recovery which you can do as well, what I suggested just returns it to factory state I don't see whats so silly about it I understand he wants to keep his data but worse comes to worse as long as you can get into the bootloader you're fine
NeoMagus said:
He is suggesting you flash custom recovery with fastboot and just flash over top of what you did thru the custom recovery which you can do as well, what I suggested just returns it to factory state I don't see whats so silly about it I understand he wants to keep his data but worse comes to worse as long as you can get into the bootloader you're fine
Click to expand...
Click to collapse
youre right about if worse comes to worse. reflashing the factory image should be the very last thing to do, when all other options have been tried. im just trying to save his data
If you don't have fastboot set up you might want to give this post a look he describes how to get it set up.
simms22 said:
youre right about if worse comes to worse. reflashing the factory image should be the very last thing to do, when all other options have been tried. im just trying to save his data
Click to expand...
Click to collapse
I don't use custom recoveries and backup my data regularly with Titanium, so restoring after a reflash is really just an afterthought here, to each there own
The problem is not as it seems.
When I plug the Nexus into the computer when in Fastboot mode, it freezes the Recovery. I cannot select anything OR move the selection to anything else. The hell?
I noticed that when the Nexus attempts to boot up, the boot animation gets brighter.
__
Wait, when it attempted to boot up when plugged into my PC, AutoPlay recognized the device as Nexus 7. There is nothing on my screen but the boot animation, however I can browse internal storage.
I cannot, however, connect to it via adb apparently. ADB devices returns nothing.
____
Okay, the problem is NOWHERE near what I thought it was. The boot animation is replacing the lock screen/home screen/everything. I just received an email (I could tell because of the notification noise the tablet made). It is booting up, just not displaying anything passed the boot animation and ADB cannot detect the device. I KNOW it has USB Debugging mode activated and all, but what can I do now?
===
I usually make backups and nandroids but I've barely owned this device. ;P
Does fastboot detect the device?
janedoesmith said:
Does fastboot detect the device?
Click to expand...
Click to collapse
Fastboot doesn't detect the device while booted up like this, and when I plugged it into the computer when in recovery/fastboot mode it not only froze the device, but fastboot wouldn't detect it.
I can get into the internal storage (just not the root of the device unfortunately). So what can one do when he cannot connect to the device via fastboot or adb, nor flash a custom recovery image because he can't access fastboot?
This is getting more complicated the more I dig into it. What the hell did I do?
Are you on the correct screen? I see how you are lumping Fastboot/recovery together, Fastboot is used on the screen with the android with his chest open after holding down the power/vol buttons from complete off , has version info/ unlock status in the lower left.. not sure if you can do that in the recovery but that is where I put the commands in
the freezing in the bootloader is a n7 bug. try a few times. try going into the bootloader then plugging in usb, and try plugging in via usb then going into the bootloader. try a few times, eventually you will get it.
VonDerThWood said:
Fastboot doesn't detect the device while booted up like this, and when I plugged it into the computer when in recovery/fastboot mode it not only froze the device, but fastboot wouldn't detect it.
I can get into the internal storage (just not the root of the device unfortunately). So what can one do when he cannot connect to the device via fastboot or adb, nor flash a custom recovery image because he can't access fastboot?
This is getting more complicated the more I dig into it. What the hell did I do?
Click to expand...
Click to collapse
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.
NeoMagus said:
Are you on the correct screen? I see how you are lumping Fastboot/recovery together, Fastboot is used on the screen with the android with his chest open after holding down the power/vol buttons from complete off , has version info/ unlock status in the lower left.. not sure if you can do that in the recovery but that is where I put the commands in
Click to expand...
Click to collapse
Fastboot has the "Recovery mode" option but it just gives me the Google logo with the unlocked icon at the bottom indefinitely...which means I cannot access recovery either? Why didn't I notice this before? >_<
simms22 said:
the freezing in the bootloader is a n7 bug. try a few times. try going into the bootloader then plugging in usb, and try plugging in via usb then going into the bootloader. try a few times, eventually you will get it.
Click to expand...
Click to collapse
Tried 10 times by booting into bootloader first, then 10 times by plugging it in and booting into it while it's plugged in. This is a very...odd bug.
janedoesmith said:
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.
Click to expand...
Click to collapse
Nothing at all. Won't detect it or anything.
it is an odd bug. i think every n7 owner who likes to flash roms/kernels has had to deal with it at least once.
VonDerThWood said:
janedoesmith said:
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.
Click to expand...
Click to collapse
Nothing at all. Won't detect it or anything.
Click to expand...
Click to collapse
What about in device manager? Does it at least show an unknown device or something similar? Try reinstalling the drivers.
janedoesmith said:
What about in device manager? Does it at least show an unknown device or something similar? Try reinstalling the drivers.
Click to expand...
Click to collapse
Now that I think about it, it DID say something about failing to install an unknown driver the first time I plugged it in. Let me uninstall/reinstall the drivers.
____
After reinstalling the drivers (and removing both of the Nexus7 specific ones), I also removed one named "Android", which, coincidentally, is the driver that the tablet is trying to install upon being plugged in. I have tried to reinstall it several times, but it fails each time, AND I just reinstalled the real Nexus 7 drivers.
___
The Nexus drivers won't reinstall now. I even went to Asus's website and downloaded them, but I have no clue how to install it in this format.
Is there a way to open/install an app through JUST the Internal Storage? If so, I have the stock launcher2.apk file right here...I just need to reinstall it! Damn, how can I get to the Root folder without ADB?
Whoa! Stroke of GENIUS!
I have Cerberus installed on my tablet. Since I know the tablet is booting up, just not displaying passed the boot animation, I decided to give it a try.
I started an alarm, which forced the tablet to the lock screen...I can open apps through the Play Store (as I got an update notification) and the like, but I can NOT get to the home screen.
I opened Total Commander via Play Store, but I can't do anything with it. The app that I used was NinjaMorph and I'm pretty sure the only way I can correct my mistake is through that app. What do I do?
Found NinjaMorph in the Play Store, it couldn't fix my problem. Oh hell.
I tried to copy/replace the launcher2.apk file I screwed up with a backed up one but TotalCommander couldn't do it. It was even granted SuperUser permissions. Attempting with Root Explorer.
Success! I have copied the original Launcher2.apk back into the /system/app folder. HOWEVER, I can NOT install it.
Managed to connect via adb! Things are looking up! Now, how to install this stuff...?
When trying to reinstall the launcher2.apk, it gives me the following error:
INSTALL_FAILED_UID_CHANGED
So I tried uninstalling it to no avail. Troubling.
SO! Now what? I am into the device, and any app I have downloaded through the Play Store is available to me, but I cannot go to the home screen. I need to reinstall the original Launcher2.apk!
Retrying NinjaMorph. It supposedly installed my Launcher2.apk. However, I still cannot return to the Home screen. WTF.
I'm going to install a different Launcher. Hope that works!
Success. I can now return home to Nova Launcher. HOWEVER...
This is not satisfactory. I want my STOCK launcher. Anybody know how I can fix this? The stock launcher is acting like it doesn't exist anymore. Is there a way to just wipe THAT data and keep all the other data on my device?? (Though I admit, I do like how I already was able to change my App drawer icon to my Nexus X <3.)
Edit: I see you resolved it. Good job! I'll just leave this here... :good:
Is there a way to open/install an app through JUST the Internal Storage? If so, I have the stock launcher2.apk file right here...I just need to reinstall it! Damn, how can I get to the Root folder without ADB?
Click to expand...
Click to collapse
You sound to be in Windows driver hell. If you have access to a Linux machine or someone who does, this entire driver mess can be avoided.
You can't install an apk via the MTP or PTP usb interface. You have a few options to fix this, but all depends on getting your drivers sorted.
Otherwise, grab the latest Windows USB drivers from Google - https://dl-ssl.google.com/android/repository/usb_driver_r07-windows.zip and follow these instructions to install them - http://developer.android.com/tools/extras/oem-usb.html
With the drivers installed and the nexus 7 plugged in, try adb devices again. Assuming you can resolve the driver issue, run
Code:
adb install path\to\launcher2.apk
comminus said:
You sound to be in Windows driver hell. If you have access to a Linux machine or someone who does, this entire driver mess can be avoided.
You can't install an apk via the MTP or PTP usb interface. You have a few options to fix this, but all depends on getting your drivers sorted.
Otherwise, grab the latest Windows USB drivers from Google - https://dl-ssl.google.com/android/repository/usb_driver_r07-windows.zip and follow these instructions to install them - http://developer.android.com/tools/extras/oem-usb.html
With the drivers installed and the nexus 7 plugged in, try adb devices again. Assuming you can resolve the driver issue, run
Code:
adb install path\to\launcher2.apk
Click to expand...
Click to collapse
I managed to get ADB working (via adbWireless) after the above post I made, however I cannot get launcher2.apk to install. This time I got the "INSTALL_FAILED_DEXOPT" error instead of the "INSTALL_FAILED_UID_CHANGED" one.
Hi folks,
My wife dropped her 2-week old Nexus 4 which caused part of the front glass to crack and portions of the touchscreen to be dead, so we had to send it into LG for repairs (at quite a price tag). Fine.
So we get it back, I turn it on, and it's in something called "FTM Mode" (file transfer mode, I think)? I can't seem to get it out of it.
Things I've tried:
Rebooting (have to hold the power button down for 5-10 sec).
Factory data reset (the settings are available through the notification menu in FTM Mode).
In recovery mode:
[*]Start (goes right back to FTM Mode)
[*]Power off (duh)
[*]Restart bootloader (gets me right back to the same screen)
[*]Recovery mode (gives me a little android with its stomach open, a red exclamation point, and says "No command.")
I attempted LG support, but they asked me to do a few of these (after asking me to hit the "home" button...), then told me to mail it back to them because they probably have to flash it.
So, the obvious question: how the hell can I get out of FTM Mode?
Secondary question: if none of the above worked and I do have to flash the OS, can I flash it myself to default Jellybean? Any idiot-friendly step-by-step guides out there?
Here you are! (I was the one talking to you on Reddit)
Since you can get to fastboot you can just flash the stock image files and you should be fine! The toolkit is in the original dev section but you cannot download the images from it anymore. A few people here have the images though so hopefully someone will pop up with them shortly
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
Here you are! (I was the one talking to you on Reddit)
Since you can get to fastboot you can just flash the stock image files and you should be fine! The toolkit is in the original dev section but you cannot download the images from it anymore. A few people here have the images though so hopefully someone will pop up with them shortly
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Haha!
I have located an image... just need to figure out the fastboot stuff. I'm not a terribly adventurous user, you see.
Depressio said:
Haha!
I have located an image... just need to figure out the fastboot stuff. I'm not a terribly adventurous user, you see.
Click to expand...
Click to collapse
No worries! You can use the toolkit without knowing fastboot, I just recommended learning it in case you ever need to flash without it. I believe after you download the toolkit there will be a folder you can place the stock image into then you can use the toolkit to flash the image from that folder. I'm not 100% what folder that is though but I believe the name makes it fairly obvious if you look for it
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
No worries! You can use the toolkit without knowing fastboot, I just recommended learning it in case you ever need to flash without it. I believe after you download the toolkit there will be a folder you can place the stock image into then you can use the toolkit to flash the image from that folder. I'm not 100% what folder that is though but I believe the name makes it fairly obvious if you look for it
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Unfortunately, I haven't even been able to install the bloody USB driver, so fastboot/adb can't even see the device. I've described by problem here. I think the source issue is what LG did during repairs... the device is named "Full JellyBean on Mako" instead of something like "Nexus 4", so the drivers in that post aren't being recognized by Windows as valid for the device. At least that's my guess.
OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!
Depressio said:
OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!
Click to expand...
Click to collapse
For future reference ADB only works in recovery and when booted into android, never in boot loader. Bit glad you got it working
Sent from my Nexus 4 using Tapatalk 2
drives
Depressio said:
OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!
Click to expand...
Click to collapse
how did you can install the adb drivers,have same problem
ramonrecio said:
how did you can install the adb drivers,have same problem
Click to expand...
Click to collapse
plug your phone into your computer, then restart it in bootloader mode. the drivers will automatically install
same
hi,thank you,ok i can go to fastboot mode and select restart bootloader but when i hit power ,they turn off for a second and go back to fastboot mode initial page ,the pc do the sound when disconnect and connect back to usb pc,but that's it,no drivers installation ,what can i do!! this make me crazy,please help
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
Okay, I was trying to load android 6.0 on my oneplus one and I don't have any idea what I've done. I was following the instructions in this video https:/ /m.youtube.com/.watch?v=x8zuQcJHQy4 but I wanted to try to do it without using my laptop. So I downloaded the gapps from here http: //opengapps.org/ directly onto my phone. I restored my phone back to factory setting from the settings menu on my phone, and then tried to follow the instructions from the YouTube video. So I removed my existing op system and then tried to install the the new gapps from the recovery menu. The instal failed, so I went back and fired up the laptop and started to follow the instructions in the video. The problem is that my laptop won't connect with my phone for some reason. I plug it in to the computer but it won't recognize my phone. So I am unable to transfer the new gapps from my laptop to my phone. Now the problem is that my phone will not start up, it just sits on the starting screen (picture attached). What do i do?! I should mention that I have no idea what I'm doing if that isn't already extremely obvious. Please help!
Look as you described there maybe more than one solution to this..
As for me the easiest method would be is to flash a custom recovery by going into fastboot mode. And from there you can boot into your recovery and transfer whatever files you need from laptop to your phone. Then flash your custom ROM.
Recovery link : https://twrp.me/devices/oneplusone.html
Custom ROM: http://forum.xda-developers.com/oneplus-one/development/rom-ressurrection-remix-m-t3270147
Look my advice is don't make this whole process as few steps guide.
Divide it into small parts like first installing recovery. Then second part flashing custom ROM. It makes its easy. And for individual part you can find tutorial online.
Thanks me if I have helped and if you have any more doubt PM me.
Sent from my A0001 using Tapatalk
i started this process for the "recovery" in the link you gave me and i cant complete the instruction that tells me to go into the device settings and tap on the build number 7 times. I can even start the phone enough to get into the settings area. Any ideas?
Just go into fastboot mode and flow the given instruction..
Sent Using Awesome Nethunter Device.
Mr.Jlu said:
Just go into fastboot mode and flow the given instruction..
Sent Using Awesome Nethunter Device.
Click to expand...
Click to collapse
By fastboot do you mean where I power it up and hold the "down volume" button for a few seconds??
OnePlus One Fastboot
Power Down the OnePlus One
Press and Hold the Volume Up and Power Button at the Same Time
Hold These Buttons Down Until You See the Text “Fastboot”
When You See the Text “Fastboot”, Let Go of the Power and Volume Up Buttons
Sent Using Awesome Nethunter Device.
---------- Post added at 12:34 AM ---------- Previous post was at 12:34 AM ----------
In order to issue commands to your OnePlus One via tools like ADB and Fastboot, you need to boot your device up into Fastboot Mode. So, instead of allowing your OnePlus One to boot up into regular Android, you are going to do something special which tells the device to boot up into Fastboot Mode. This might take you a few tries until you get the hang of it. There’s no need to panic or worry if you get it wrong. Simple power down the OnePlus One again and give it another shot.
Sent Using Awesome Nethunter Device.
I can boot it up into fast boot mode without any problems, I just don't know what do do once there. That's the part I need help with.
turbo224 said:
I can boot it up into fast boot mode without any problems, I just don't know what do do once there. That's the part I need help with.
Click to expand...
Click to collapse
1. You need configured fasboot tools first.
2. Flash twrp using fastboot
3. Reboot to recovery
4. Connect your phone with the computer
5. Copy ROM and gapps to your phone and disconnect.
6. Make a full wipe in recovery
7. Flash ROM and gapps
8. Reboot
1. Follow this guide on setting up adb and fastboot - http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
2. Download twrp-3.0.2-0-bacon recovery from here - https://dl.twrp.me/bacon/
3. Put the recovery image in the same folder fastboot and adb exe is.
4. Put your phone in fastboot mode and connect to pc
5. Open a command prompt and type "fastboot flash recovery twrp-3.0.2-0-bacon.img"
6. Do Not issue the fastboot reboot command, instead press and hold power and vol down till phone reboots into recovery
I give up, i'm way over my head. I cant do any of this **** because I can't even get the right ****ing usb driver on my computer so it even recognizes my phone. I've tried three different methods and none of them work.
turbo224 said:
I give up, i'm way over my head. I cant do any of this **** because I can't even get the right ****ing usb driver on my computer so it even recognizes my phone. I've tried three different methods and none of them work.
Click to expand...
Click to collapse
Don't give up.
That's pretty simple if you follow the guide below TO THE LETTER.
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Basically, you just erased the Android operating system from your phone. The gapps is NOT the Android system. Gapps stands for Google Apps (play store, calendar, youtube, etc...). They are just additional apps, like Office for Windows for example.
Good luck!
Turbo224,from which country you are from? If you don't mind me asking!
Sent Using Awesome Nethunter Device.