Related
I bought a nexus 7 today, rooted it no problems, but i changed the pdi settings to 160 to see if i could get the tablet ui, and now it wont boot fully, i can get into recovery and all but it wont boot past the google splash screen :/ HELP!
Here is stock build.prop for JRO03D, you can try pushing it via adb only other thing I can think of is complete reflash with the factory image
good luck
Is there a way to get the image onto the table in recovery?
Pretty sure you flash that image in fastboot
Sent from my Nexus 7 using Tapatalk 2
yes you use fastboot to flash the image via cmd prompt on your PC
I apologise, I've never had to use ADB or fastboot before, do you just give the file location and then it'll flash it on the tablet?
if you can get to recovery, try plugging the tablet with cable to a pc and mount the storage and move a rom over to it and flash it?
i dont have a nexus 7 yet but that would be my fix for a phone
Beagan said:
Is there a way to get the image onto the table in recovery?
Click to expand...
Click to collapse
adb push
adb is enabled in clockwork recovery. There's no way to mount the "sdcard" in recovery like you can on devices that have a physical SD card device.
I used nexus toolkit worked great!
Sent from my GT-I9100 using xda premium
Please help, I downloaded ChameleonOS Rom for Mako and I was on PA. I did a backup in TWRP and after I wiped data and cache I tried tp flash CHAOS ROm. It said success but it won't boot passed Google and If I try to restore PA it says failed and now I have no rom to flash to boot up and also I can't turn on debug to use ADB.
Zehlek said:
Please help, I downloaded ChameleonOS Rom for Mako and I was on PA. I did a backup in TWRP and after I wiped data and cache I tried tp flash CHAOS ROm. It said success but it won't boot passed Google and If I try to restore PA it says failed and now I have no rom to flash to boot up and also I can't turn on debug to use ADB.
Click to expand...
Click to collapse
i'm not on twrp at the moment but you may be able to try this
you may also try the nexus toolkit
Nexus 4 toolkit says device not found when trying to push file to device. It shows serial under fastboot mode but not ADB Mode. Is that because I can't turn on debug?
Zehlek said:
Nexus 4 toolkit says device not found when trying to push file to device. It shows serial under fastboot mode but not ADB Mode. Is that because I can't turn on debug?
Click to expand...
Click to collapse
hmm... can you try setting the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot? might be able to get you back to square one.
if you can get into twrp you might be able to run adb commands from the recovery even if you didnt have it enabled before using the toolkit.
efan3719 said:
hmm... can you try setting the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot? might be able to get you back to square one.
if you can get into twrp you might be able to run adb commands from the recovery even if you didnt have it enabled before using the toolkit.
Click to expand...
Click to collapse
That might work, how do I set the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot?
Zehlek said:
That might work, how do I set the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot?
Click to expand...
Click to collapse
On the main screen of the nexus tool kit there is a radio button option you can click for it.
Sent from my Nexus 4 using xda premium
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
exb0 said:
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
Click to expand...
Click to collapse
This guy sounds like he knows what he's doing.
Sent from my Nexus 4 using xda premium
exb0 said:
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
Click to expand...
Click to collapse
It says fastboot is not recognized as an internal command
In twrp, it keeps saying starting adb sideload feature
i posted this in another thread. try this...
1. First make sure that you have fastboot driver installed.
2. Power down your Nexus 4 (hold the power button until it shuts off) before rebooting into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
3. Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
4. Type fastboot devices into the command line, and you should then see your device’s ID, which means fastboot is setup correctly. if not, check to make sure Google Nexus 4 drivers are installed correctly.
5. now open Nexus 4 toolkit and Flash Google Factory stock Rom. Once you are back to stock continue on from there...
Good Luck!
Zehlek said:
It says fastboot is not recognized as an internal command
Click to expand...
Click to collapse
my bad, it's fastboot-toolkit. But since you have a recovery with sideload already, just download a rom that's working, put it in your nexus 4 toolkit folder, rename it to flash.zip, and type in CMD
"adb-toolkit sideload flash.zip"
Thank you all for your help. What I had to end up doing was extracting the factory image and flash boot, system, and use data IMG files manually with nexus 4 toolkit. My Nexus 4 is alive. Again thank you all very much
Sent from my Nexus 4 using Tapatalk 2
Zehlek said:
Thank you all for your help. What I had to end up doing was extracting the factory image and flash boot, system, and use data IMG files manually with nexus 4 toolkit. My Nexus 4 is alive. Again thank you all very much
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Glad to here it. My heart sank when I read your issue. Happy to see it resolved.
Sent from my Nexus 4 using xda premium
efan3719 said:
Glad to here it. My heart sank when I read your issue. Happy to see it resolved.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thank you. I was beginning to panic when I saw there nothing working that would transfer a rom to my sdcard. Again thank you for all your help
Sent from my Nexus 4 using Tapatalk 2
I have a rooted nexus 4 and I installed today the newest cm and it booted normally but then I went to the recovery mode (twrp) and did a factore reset and when I try to reboot to system it says no os installed and it stucks at the google screen but it doesn't connect to the pc to copy the rom so what should I do ?
PLEASE HELP ME
EDIT: the pc detects the nexus but I can't copy files to it because it isn't shown in my computer
Sysou said:
I have a rooted nexus 4 and I installed today the newest cm and it booted normally but then I went to the recovery mode (twrp) and did a factore reset and when I try to reboot to system it says no os installed and it stucks at the google screen but it doesn't connect to the pc to copy the rom so what should I do ?
PLEASE HELP ME
Click to expand...
Click to collapse
You can try flashing a rom with TWRP in adb sideload https://www.google.nl/url?sa=t&rct=...v4l4QSOgEwWvPXvTXm_X0Kw&bvm=bv.51495398,d.d2k or https://www.google.nl/url?sa=t&rct=...ZGmpgOaC9H-lOqowATpMSIw&bvm=bv.51495398,d.d2k or flash a factory image in fastboot mode.
gee2012 said:
You can try flashing a rom with TWRP in adb sideload https://www.google.nl/url?sa=t&rct=...v4l4QSOgEwWvPXvTXm_X0Kw&bvm=bv.51495398,d.d2k or https://www.google.nl/url?sa=t&rct=...ZGmpgOaC9H-lOqowATpMSIw&bvm=bv.51495398,d.d2k or flash a factory image in fastboot mode.
Click to expand...
Click to collapse
I don't have the cmd so what should I do please help me
Sysou said:
I don't have the cmd so what should I do please help me
Click to expand...
Click to collapse
Are you running windows? Else flash the factory image from here https://developers.google.com/android/nexus/images with the Nexus 4 Toolkit from here http://forum.xda-developers.com/showthread.php?t=1995688.
You can definitive flash a Factory Image via Fastboot without an Custom Recovery
Did you install nexus 4's usb driver? if you didn't install it and flash custom recovery by using abd siderode
Sent from my Nexus 4 using Tapatalk 4
Nexus 4 running 4.4.2 bootloader version MAKOZ30d
I used Wug's root toolkit to unlock my bootloader but after reboot into fastboot, neither my windows 7 machine nor my linux mint machine will mount the phone without MTP turned on. I can run adb commands while MTP is on but drivers fail to load if mtp is off.. So now I have an unlocked bootloader and am unable to complete the rooting proces..
Any help is much appreciated.
Cheers!
go to settings/storage open 3dots menu /usb computer connection. if nothing is selected that is why your phone doesn't connect. select mtp an problem solved.
if it's not that i cannot help you except suggesting to reinstall android from scratch using wug toolkit.
wasabitobiko said:
Nexus 4 running 4.4.2 bootloader version MAKOZ30d
I used Wug's root toolkit to unlock my bootloader but after reboot into fastboot, neither my windows 7 machine nor my linux mint machine will mount the phone without MTP turned on. I can run adb commands while MTP is on but drivers fail to load if mtp is off.. So now I have an unlocked bootloader and am unable to complete the rooting proces..
Any help is much appreciated.
Cheers!
Click to expand...
Click to collapse
You can't "mount storage" in Fastboot mode.... what exactly are you trying to do?
acejavelin said:
You can't "mount storage" in Fastboot mode.... what exactly are you trying to do?
Click to expand...
Click to collapse
Trying to finish the rooting process by using adb.. by "mount" I mean get access in fastboot from either of my computers. Didn't have this problem with my other N4.. when I plug the phone into my computer while in fastboot and try any adb commands.. I get <waiting for device> nothing... It seems like the adb drivers aren't loading while in fastboot. I'll try to back things out using the toolkit again..
wasabitobiko said:
Trying to finish the rooting process by using adb.. by "mount" I mean get access in fastboot from either of my computers. Didn't have this problem with my other N4.. when I plug the phone into my computer while in fastboot and try any adb commands.. I get <waiting for device> nothing... It seems like the adb drivers aren't loading while in fastboot. I'll try to back things out using the toolkit again..
Click to expand...
Click to collapse
OK, so your fastboot commands are not working, that would likely be a driver issue? If you do
Code:
fastboot devices
and get a result, then keep going, if you don't, use one of the driver options in Wugfresh's toolkit, follow the instructions TO THE LETTER...
If you are just trying to get root and are unlocked, download the latest SuperSU.zip (to your phone preferably) from http://download.chainfire.eu/supersu and openrecovery-twrp-2.7.0.0-mako.img then start phone in Fastboot mode and enter:
Code:
fastboot boot openrecovery-twrp-2.7.0.0-mako.img
this will start TWRP on your device WITHOUT flashing it.
If the SuperSU zip file is on your phone, just use TWRP's Install button and navigate the file and flash it, then reboot and enjoy.
If the SuperSU zip is on your PC, then in TWRP go to Advanced, and start ADB Sideload, give it a few seconds for it to be recognized by your PC, you should be able to enter
Code:
adb devices
and get a result of SIDELOAD back, then enter:
Code:
adb sideload UPDATE-SuperSU-v1.94.zip
Or whatever the current SuperSU zip file is named. Then reboot and enjoy, your rooted!
Remember that adb commands only work in android and custom recovery NOT in fastboot mode.
Sent from my Nexus 4 using XDA Free mobile app
Ok.. If I can't run adb commands from fastboot, how do I enter that command in fastboot?
Sent from my Nexus 4 using XDA Free mobile app
wasabitobiko said:
Ok.. If I can't run adb commands from fastboot, how do I enter that command in fastboot?
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
ADB sideload is a special mode that recovery can be placed into, it only allows the "sideload" command to be used. Fastboot is different, it uses the fastboot.exe program and fastboot mode on the android device to allow a limited list of features to be used.
I don't know what you are using for a rooting guide, but basically the end result is to flash SuperSU via recovery, that is all that is really needed.
Sent from my Nexus 4 using Tapatalk
Well, basically if your boot loader is unlocked and you have a custom recovery installed just download the latest superSU zip to your SD card. Reboot into recovery, install SuperSU, reboot. Alas, you're rooted.
Sent from my Nexus 4 using XDA Free mobile app
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
wasabitobiko said:
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
If you unlocked your bootloader your drivers should be working fine. If you rebooted your phone now you'd see it works fine. Next step in rooting is to flash custom recovery. Download a custom recovery, I recommend latest version of TWRP, then flash the recovery image. 'fastboot flash recovery recovery.img' (replace recovery.img with whatever .img file you are flashing.
Once custom recovery is installed you can boot into it to flash supersu. If using TWRP it will prompt you to root when you reboot it.
Thanks.. And please don't take offense to this but re-read the thread. Ever since I used wug's rootkit to unlock the bootloader, neither my pc nor linux machine will recognize the Nexus 4. When I plug it in I get a usb error "device failed to load".. When I look at the device mgr it's listed as unknown device. Btw.. I've restarted both my phone and machine multiple times to no avail.
Sent from my Nexus 4 using XDA Free mobile app
Unknown device? Youve probably installed no or wrong fastboot drivers.
Sent from my Nexus 4 using XDA Free mobile app
wasabitobiko said:
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Google tool 15 second adb xda
Sent from my Nexus 5 using XDA Free mobile app
UPDATE: It looks like the micro usb port on the phone is fried... had been charging fine until today. I'll keep you posted. Thanks for all the help. Does anyone know if this is a relatively easy fix?
Update: Fixed..
Replacing the usb port on the Nexus 4 is super easy. Thanks for the help guys. Everything's working and root has been achieved.
Hello everyone, I would need to understand if my Nexus 7 2012 WiFi is definitely Hard Bricked or not.
The other day I installed Slimkat ROM and had the error 7 during installation...
I like it better: In Nexus it's root and it unlock with the Recovery CWM, which start with the sequence of Volume Down- Power On keys. I have done the wrong not to do before installing a backup with the Recovery CWM and now I am in the situation of having the Nexus that normally light up on the Google logo and if I start shooting, it is not copied on the sdcard the right ROM, unable to install anything. I seem to have read that I had installed the TWPR Recovery instead of an external USB with an OTG cable, which is impossible with the CWM.
This is my question: Is there any way to copy files to the SDCard? If I don't see the Nexus in ADB, can I install TWRP Recovery up the CWM? (for use the USB/OTG performance)
Thanks for the help and congratulations for the forum ...
luca
Hard to understand you actually... but boot to bootloader and fastboot flash the TWRP, use MTP to copy over what you need to flash and go ahead, in case you never used fastboot check Google there're plenty of guides out there, good luck...
Sent from my Nexus 7 using XDA Labs
Sam Nakamura said:
Hard to understand you actually... but boot to bootloader and fastboot flash the TWRP, use MTP to copy over what you need to flash and go ahead, in case you never used fastboot check Google there're plenty of guides out there, good luck...
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
Thank you so much for your answer. But I installed CWM Recovery and I can not access to Nexus in fastboot or adb, so I can not install the Recovery TWRP. I've tried both with MAC OSX and Windows, but the Nexus is not seen by the system. Exist an alternative method for flashing the recovery TWRP without using fastboot or adb?
lucafict said:
Hello everyone, I would need to understand if my Nexus 7 2012 WiFi is definitely Hard Bricked or not.
The other day I installed Slimkat ROM and had the error 7 during installation...
I like it better: In Nexus it's root and it unlock with the Recovery CWM, which start with the sequence of Volume Down- Power On keys. I have done the wrong not to do before installing a backup with the Recovery CWM and now I am in the situation of having the Nexus that normally light up on the Google logo and if I start shooting, it is not copied on the sdcard the right ROM, unable to install anything. I seem to have read that I had installed the TWPR Recovery instead of an external USB with an OTG cable, which is impossible with the CWM.
This is my question: Is there any way to copy files to the SDCard? If I don't see the Nexus in ADB, can I install TWRP Recovery up the CWM? (for use the USB/OTG performance)
Thanks for the help and congratulations for the forum ...
luca
Click to expand...
Click to collapse
Tried with Nexus root toolkit ?
twrp better than cwm
lucafict said:
Thank you so much for your answer. But I installed CWM Recovery and I can not access to Nexus in fastboot or adb, so I can not install the Recovery TWRP. I've tried both with MAC OSX and Windows, but the Nexus is not seen by the system. Exist an alternative method for flashing the recovery TWRP without using fastboot or adb?
Click to expand...
Click to collapse
Bootloader is not Recovery nore ADB, it's independent from those!
Boot up by holding power & volume down till you have the bootloader screen (picture attached), if you see it plug it in your (windows) computer and check "fastboot devices", there then fastboot flash TWRP image...
Sent from my OnePlus 3T using XDA Labs
Sam Nakamura said:
Bootloader is not Recovery nore ADB, it's independent from those!
Boot up by holding power & volume down till you have the bootloader screen (picture attached), if you see it plug it in your (windows) computer and check "fastboot devices", there then fastboot flash TWRP image...
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Attacched my Fastboot page, but nothing... no devices show with “fastboot devices” command.
lucafict said:
Attacched my Fastboot page, but nothing... no devices show with “fastboot devices” command.
Click to expand...
Click to collapse
Have you another device at hand to check weather fastboot is working with a different device, just to make sure that your fastboot environment is working properly...
Sent from my OnePlus 3T using XDA Labs
Yes, with another Nexus 7, if I connect it to pc, the device is show in section device list of pc. I think the problem is that this Bricked Nexus in fastboot not start the usb driver...