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
Related
following some people's tips here to understand what the hell is going on and following this:
http://www.youtube.com/watch?v=DIL1iTr5vto
i unlocked and rooted my phone, everything got deleted as expected and now i decided i might want to install CM 10.1 or another mod...
going into fastboot, navigating to "Recovery mode" and getting an error picture (android with red thing above his open chest) i realized
i do not have CWM installed...
1. no idea how to install it - since i did everything else with a tool that did everything automatically but not this, help
2. all the guides i've seen say this action too will erase my whole device..., is this true? and can it be avoided?
ty!
Flashing recovery only? Nope it does not wipe. If you wanna flash recovery:
1. Download cwm.IMG (place it where adb and fastboot is)
2. Connect the phone and reboot to fastboot mode
3. Open command prompt by holding shift and right clicking the mouse and selecting open command prompt here
4. Type "fastboot flash recovery NAME_OF_FILE.img
Sent from my Nexus 4 using xda app-developers app
kyokeun1234 said:
Flashing recovery only? Nope it does not wipe. If you wanna flash recovery:
1. Download cwm.IMG (place it where adb and fastboot is)
2. Connect the phone and reboot to fastboot mode
3. Open command prompt by holding shift and right clicking the mouse and selecting open command prompt here
4. Type "fastboot flash recovery NAME_OF_FILE.img
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Hey kyokeun1234!
first of all ty for answering.
now im gonnna have to ask you to speak slowly so i can understand fast.
1.when you say "Flashing recovery" you mean "installing a costume recovery" - it being CWM?
2. how do i find ADB and Fastboot? since i installed it using a tookit i didnt manually place them. searching ADB with my file manager found a folder called "Android_Adb" (inside it i have power and Subsystem folders) but cant find "fastboot" anywhere - or do u mean in the same folder in the PC? - yet again, i do not have these files since i used a toolkit
3-4 will do after i understand 1-2.
after i do this, when i installed a mob (lets say CM), do i than lose all my data? and if so, if i use titanium recovery, will it install all my games+saves in a functional way on the new mod?
Don't use toolkits, it's better to learn what you're doing yourself
Sent from my Galaxy Nexus using xda premium
alright u can lock this.
all i needed to do is re-root using the same toolkit but check the V for custom recovery.
TY!
I'm in a bit of jam. I flashed the official zip from google to update to 4.2.2 and the flash seemed to work fine. I cleared both caches after the update
However, now I seem to be completely locked out of adb and the phone doesn't prompt me for authorization (the new feature in 4.2.2) http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/ . I am showing connected but offline just like this article. I have tried multiple reboots (phone/computer) as well as different USB ports. I have not tried another computer yet.
When I try to go to recovery I get a red exclamation point dead robot as I assume the flash wiped TWRP and I can't reflash TWRP without adb/root.
I would like to try to avoid a complete internal memory factory reset from the rom which I'm not sure would work anyway.
Please help.
update your adb / sdk.
bodh said:
update your adb / sdk.
Click to expand...
Click to collapse
Fortunately, I was able to reflash TWRP using fastboot w/o using adb. At the bootloader, I ran
Code:
fastboot flash recovery recovery.img
which got my recovery back up and running.
I decided to do a factory wipe and even after that adb was showing as offline and not prompting. I am very confident that your suggestion of updating the platform tools is going to fix my issue.
Thank you.
Locked on 4.2.2
My Nexus 7 is locked on 4.2.2. I tried to Unlock with Nexus Root Toolkit and I get "adb offline". I did the command "adb devices" and the device showed up, but when I tried to unlock again, it gets stuck on "checking adb status". I updated SDK and copied the new adb.exe, fastboot.exe, etc into the platform-tools folder and it still doesnt work. So basically my oem is locked on 4.2.2 and I can get adb or the toolkit to work properly.. Is there a way to downgrade back to 4.2.1 or get the Wugfresh Nexus Toolkit to actually unlock my Nexus 7 on 4.2.2??
Yea, there's a way to downgrade if you have a nandroid and know what you're doing. The toolkit will need to be updated, and it helps to know how to do it manually first.
bodh said:
Yea, there's a way to downgrade if you have a nandroid and know what you're doing. The toolkit will need to be updated, and it helps to know how to do it manually first.
Click to expand...
Click to collapse
If you know the steps or can link me to a page, that would be much appreciated. I want clear steps.
Basically the same thing just happened to me. I updated to the newest android sdk then followed the steps here http://forum.xda-developers.com/showthread.php?t=2010312
I had to restore the complete stock image first, then I sideloaded the update. I made sure all of my files were in C:\Development\sdk\platform-tools (thats the directory I used, yours may be different). Open a command prompt on the platform-tools folder and run fastboot devices, if you see a number there you are good to go. Just follow the steps in the link above to flash each file.
Why cant people wait..
lol
Bronk93 said:
Basically the same thing just happened to me. I updated to the newest android sdk then followed the steps here http://forum.xda-developers.com/showthread.php?t=2010312
I had to restore the complete stock image first, then I sideloaded the update. I made sure all of my files were in C:\Development\sdk\platform-tools (thats the directory I used, yours may be different). Open a command prompt on the platform-tools folder and run fastboot devices, if you see a number there you are good to go. Just follow the steps in the link above to flash each file.
Click to expand...
Click to collapse
I'm going to try this. Can i just type "fastboot devices" in the command prompt and it'll work?
EDIT: I found a simple fix for anyone with this problem: CREATE A BACKUP FIRST, THIS WILL ERASE EVERY THING
1. Go into the platform-tools and open the command prompt by pressing Shift + Right Click.
2. Type in "adb reboot bootloader"
3. Then type in "fastboot oem unlock"
4. WALA! It'll take a while to start up, don't worry. Set up your device and that's all.
AJ Bryant said:
I'm going to try this. So would I have to copy a fastboot.exe into the platform-tools folder? Or can i just type "fastboot devices" in the command prompt and it'll work?
Click to expand...
Click to collapse
If you downloaded the new android sdk fastboot should already be in there
I found a simple fix for this problem: CREATE A BACKUP FIRST, THIS WILL ERASE EVERY THING
1. Go into the platform-tools and open the command prompt by pressing Shift + Right Click.
2. Type in "adb reboot bootloader"
3. Then type in "fastboot oem unlock"
4. WALA! It'll take a while to start up, don't worry. Set up your device and that's all.
---------- Post added at 12:05 PM ---------- Previous post was at 11:55 AM ----------
XX-RAZOR-XX said:
Why cant people wait..
lol
Click to expand...
Click to collapse
No need to wait because I found the fix, by myself.
Can't wait to get home and try this. I got stuck last night at adb offline
Sent from my Nexus 4 using xda app-developers app
But with oem unlock, you'll still be on 4.2.2. This thread should offer good info on flashing, albeit for a galaxy nexus, but it should be mostly applicable for a nexus 7. http://forum.xda-developers.com/showthread.php?t=1626895
bodh said:
But with oem unlock, you'll still be on 4.2.2. This thread should offer good info on flashing, albeit for a galaxy nexus, but it should be mostly applicable for a nexus 7. http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
That's the point; we want to be unlocked and rooted on 4.2.2. I previously thought that in order to get an unlocked and rooted Nexus, I'd have to be on 4.2.1, unlock and root, then upgrade to 4.2.2 but that's not the case. I just unlocked and rooted via ADB since the Nexus Root Toolkit wasn't working for 4.2.2. I (and probably others) kept getting the "adb offline" error even after allowing USB debugging between the device and PC. Point is, if you're on 4.2.2 with a locked bootloader, you'll need to unlock and root using ADB commands. I don't know how many people have this issue but if someone requests it, I'll just post the steps on how to unlock and root 4.2.2 jelly bean using the ADB commands.
Re: [Q]Manually updated to 4.2.2... Now locked out of adb and recovery. Help
What if I'm on 4.2.2 completely stock but with an unlocked boot loader. I get the adb offline message when I try to root using a toolkit. How would I go about rooting?
Sent from my Nexus 4 using xda app-developers app
Place su.zip on sdcard. Reboot in fastboot mode, probably volume up+down+power. In terminal on pc, fastboot boot cwm.img for your device, install zip from sdcard.
bodh said:
Place su.zip on sdcard. Reboot in fastboot mode, probably volume up+down+power. In terminal on pc, fastboot boot cwm.img for your device, install zip from sdcard.
Click to expand...
Click to collapse
What do u mean by terminal on my PC fast boot cwm.img
Sent from my Nexus 4 using xda app-developers app
Rooting Jelly Bean 4.2.2 via ADB
DowntownJeffBrown said:
What if I'm on 4.2.2 completely stock but with an unlocked boot loader. I get the adb offline message when I try to root using a toolkit. How would I go about rooting?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
1. Download the SuperSU.zip from here: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip and place it on your device in the sdcard. I'm assuming you already enabled USB debugging.
2. Download the recovery-clockwork-touch-6.0.1.0-grouper.img from here: https://www.dropbox.com/s/v4hjsb4lse3dwtc/cwm6010touch_INSTALL.zip and place it in the platform-tools folder. Assuming you know where it's located on your PC
3. Locate the "platform-tools" folder on your PC, open it, and press Shift + Right Click & Open the command prompt there.
4. Type in the command "Adb reboot bootloader"
5. Then type in the command "fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img"
6. Now go to Recovery Mode on your Nexus and install the CWM-SuperSU-v0.98.zip from there.
7. Reboot the device once you're done and you have a rooted Nexus 7 via adb. Hope this helps.
AJ Bryant said:
1. Download the SuperSU.zip from here: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip and place it on your device in the sdcard. I'm assuming you already enabled USB debugging.
2. Download the recovery-clockwork-touch-6.0.1.0-grouper.img from here: https://www.dropbox.com/s/v4hjsb4lse3dwtc/cwm6010touch_INSTALL.zip and place it in the platform-tools folder. Assuming you know where it's located on your PC
3. Locate the "platform-tools" folder on your PC, open it, and press Shift + Right Click & Open the command prompt there.
4. Type in the command "Adb reboot bootloader"
5. Then type in the command "fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img"
6. Now go to Recovery Mode on your Nexus and install the CWM-SuperSU-v0.98.zip from there.
7. Reboot the device once you're done and you have a rooted Nexus 7 via adb. Hope this helps.
Click to expand...
Click to collapse
What about for a nexus 4. Do u know where I can get that cwm?
Sent from my Nexus 4 using xda app-developers app
DowntownJeffBrown said:
What about for a nexus 4. Do u know where I can get that cwm?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
For the Nexus 4 use this cwm image instead: http://download2.clockworkmod.com/re...0.2.3-mako.img
When youre doing the fastboot recovery, put in the name of this img file at the end. "fastboot flash recovery [name of the download file].img
Hello,
i had forgot downloading SmoothRom before wiping (Factory Reset, Dalvik/Cache..) my Wifi N7 without enabled USB-Debugging.
Now I don't know how to flash it, i really need your help...
i tried it with the option Flash Stock+Unroot (Soft-Bricked/Bootloop) in Wug`s toolkit but now after that the tablet insn't able to boot like before and i lost the recovery. Sorry for my bad english.
AW: Unlocked and rooted N7 fully wiped without ROM and USB Deb..
if you can enter fastboot mode just follow the instructions in one of the stickies in q&a
Sent from my Galaxy Nexus using xda app-developers app
u could flash a recovery using fastboot, and could push your rom from pc using adb straight after.
fastboot flash xxx
adb push xxx yyy
are the commands you will need
this may help: http://forum.xda-developers.com/showthread.php?t=1907796
indoh said:
u could flash a recovery using fastboot, and could push your rom from pc using adb straight after.
fastboot flash xxx
adb push xxx yyy
are the commands you will need
this may help: http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
how do i use adb without enabled usb-debug?
Power off nexus.
Hold power and volume down at same time.
You should now see a green Android lying on its back.
Download:
http://techerrata.com/file/twrp2/grouper/openrecovery-twrp-2.4.4.0-grouper.img
Put that in your fastboot folder in pc. (In your SDK/Platform Tools)
Right click in your fastboot folder whilst holding shift. And click "open command prompt here"
Now Type:
fastboot flash recovery openrecovery-twrp-2.4.4.0-grouper.img
If all goes well carry on:
Power off nexus
Power on whilst holding volume down.
Should be at green android laying on back again.
Use volume till you see "Enter Recovery"
Enter TWRP.
Go to Advanced, "Mount USB"
Now, download a ROM of your choice. Stock or Custom
Copy it to your Nexus on PC.
Go back to TWRP on nexus, go to "Install"
Find the ROM
Flash
Wipe Cache and Dalvik Cache.
Reboot
BOOM !!
n/m
Wilks3y said:
Power off nexus.
Hold power and volume down at same time.
You should now see a green Android lying on its back.
Download:
http://techerrata.com/file/twrp2/grouper/openrecovery-twrp-2.4.4.0-grouper.img
Put that in your fastboot folder in pc. (In your SDK/Platform Tools)
Right click in your fastboot folder whilst holding shift. And click "open command prompt here"
Now Type:
fastboot flash recovery openrecovery-twrp-2.4.4.0-grouper.img
If all goes well carry on:
Power off nexus
Power on whilst holding volume down.
Should be at green android laying on back again.
Use volume till you see "Enter Recovery"
Enter TWRP.
Go to Advanced, "Mount USB"
Now, download a ROM of your choice. Stock or Custom
Copy it to your Nexus on PC.
Go back to TWRP on nexus, go to "Install"
Find the ROM
Flash
Wipe Cache and Dalvik Cache.
Reboot
BOOM !!
Click to expand...
Click to collapse
Ok, thanks.
Now i got TWRP but i don't know what Mount USB means, i can't find it in Advanced...
....
Ethested said:
Ok, thanks.
Now i got TWRP but i don't know what Mount USB means, i can't find it in Advanced...
Click to expand...
Click to collapse
because you cant 'Mount' something that doesnt exist?
just adb push the rom zip
Pirateghost said:
because you cant 'Mount' something that doesnt exist?
just adb push the rom zip
Click to expand...
Click to collapse
Or ADB sideload using that option in recovery.
Sent from my Nexus 7 using Tapatalk HD
AW: Unlocked and rooted N7 fully wiped without ROM and USB Deb..
u can use adb while your phone is in recovery. if it does not find it, check advanced options for a setting called adb daemon or similar...
use adb push just as i told you in my other post... or look in my link i posted.... everything is explained there... goddamn, lazy people...
Sent from my Nexus 7 using xda app-developers app
Ok, now it works, i did it with "adb sideload ROM.zip"
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.
I tried to search, but in vain.
Hardware: Nexus 4
Software : Android 4.4.4
For reasons that are not clear to me the machine restarted and is stuck in those 4 rotating circles, and doesnt go beyond it. Tried multiple things such rebooting, rebooting into recovery and booting again, tried adb to see if it can see the machine in recovery mode, but to no avail.
Can someone please help? Thanks in advance.
Did you do anything, flash anything to get the boot loop? Boot loop can usually be cleared by doing a factory reset. But you'll have to reset up your phone afterwards
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Did you do anything, flash anything to get the boot loop? Boot loop can usually be cleared by doing a factory reset. But you'll have to reset up your phone afterwards
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
This is a stock android and have no changes whatsoever except automatic update to 4.4.4. Only thing that is different is it is unlocked.
For last one week the phone kept complaining that it was unable to back up photos and videos. So I kept the wifi on over the night, and next morning I saw what i thought was it was trying to reboot but unable to do.
Is it possible to connect to machine while it is in recovery mode? My ADB can't discover the device either in recovery mode or while it is trying to boot. Is there a way to press some button and hard reset it?
Concoran said:
This is a stock android and have no changes whatsoever except automatic update to 4.4.4. Only thing that is different is it is unlocked.
For last one week the phone kept complaining that it was unable to back up photos and videos. So I kept the wifi on over the night, and next morning I saw what i thought was it was trying to reboot but unable to do.
Is it possible to connect to machine while it is in recovery mode? My ADB can't discover the device either in recovery mode or while it is trying to boot.
Click to expand...
Click to collapse
Can you get into the bootloader? If so you can flash a custom recovery. ADB won't work in the stock recovery.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Can you get into the bootloader? If so you can flash a custom recovery. ADB won't work in the stock recovery.
Click to expand...
Click to collapse
I can get into bootloader - if you mean by pressing down volume button and powering on - so you see a few options such as 'Start', 'Restart Bootloader' et al.'
If I can get into this, what option do I have? How I can I some custom recovery such as TWRP?
Also, I saw a youtube video where a gentleman shows how to completely reset from Recovery mode (hold power button and press up volume key), but that doesn't seem to work for me.
Concoran said:
I can get into bootloader - if you mean by pressing down volume button and powering on - so you see a few options such as 'Start', 'Restart Bootloader' et al.'
If I can get into this, what option do I have? How I can I some custom recovery such as TWRP?
Also, I saw a youtube video where a gentleman shows how to completely reset from Recovery mode (hold power button and press up volume key), but that doesn't seem to work for me.
Click to expand...
Click to collapse
Yes, that's the bootloader. Google 15 second adb install xda and install that. Then download the latest version of this http://techerrata.com/browse/twrp2/mako
Rename it recovery and put it in the same directory as fastboot.exe which will be installed with the 15 second adb install
Open a Windows command prompt in the same directory as fastboot and then with your phone connected to the pc and in the bootloader type the command in the command window
fastboot flash recovery recovery.img
This will instal twrp to your phone
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Yes, that's the bootloader. Google 15 second adb install xda and install that. Then download the latest version of this http://techerrata.com/browse/twrp2/mako
Rename it recovery and put it in the same directory as fastboot.exe which will be installed with the 15 second adb install
Open a Windows command prompt in the same directory as fastboot and then with your phone connected to the pc and in the bootloader type the command in the command window
fastboot flash recovery recovery.img
This will instal twrp to your phone
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
My Biggest concern right now is not TWRP. I need to somehow get the machine to boot. It is stuck in those 4 circling things, and I need to somehow get the OS to work (or re-install if needed).
I am able to get to recovery where I see options to 'apply aupdate from ADB,' 'wipe data' and 'wipe partition'. I have wiped off everything, now I need to somehow get OS to install, and I don't know how. I tried using 'adb sideload 'image-occam-ktu84l.zip', but it fails.That file was extracted from occam-ktu84l-factory-0d3fd624.tgz from Android site.
Update: Great, now TWRP is installed. What next? I don't want CM at this point. Just stock Os. How do I get on to the machine?
Concoran said:
My Biggest concern right now is not TWRP. I need to somehow get the machine to boot. It is stuck in those 4 circling things, and I need to somehow get the OS to work (or re-install if needed).
I am able to get to recovery where I see options to 'apply aupdate from ADB,' 'wipe data' and 'wipe partition'. I have wiped off everything, now I need to somehow get OS to install, and I don't know how. I tried using 'adb sideload 'image-occam-ktu84l.zip', but it fails.That file was extracted from occam-ktu84l-factory-0d3fd624.tgz from Android site.
Update: Great, now TWRP is installed. What next? I don't want CM at this point. Just stock Os. How do I get on to the machine?
Click to expand...
Click to collapse
Adb side load this http://forum.xda-developers.com/showthread.php?p=47476426
Edit, you could also flash the .zip you mentioned in your post by
fastboot update your file.zip
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Adb side load this http://forum.xda-developers.com/showthread.php?p=47476426
Edit, you could also flash the .zip you mentioned in your post by
fastboot update your file.zip
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Now that I have TWRP, how do I install CM? I would eventually like to return to stock, but at least for now, I need to get the phone going.
UpdateOk, the TWRP wasn't functioning well (swipe function wouldn't work), so got CWM recovery, and installed CM. CM too goes into infinite loop. Now I am completely stuck, I have no idea what else I can do.
Concoran said:
Now that I have TWRP, how do I install CM? I would eventually like to return to stock, but at least for now, I need to get the phone going.
UpdateOk, the TWRP wasn't functioning well (swipe function wouldn't work), so got CWM recovery, and installed CM. CM too goes into infinite loop. Now I am completely stuck, I have no idea what else I can do.
Click to expand...
Click to collapse
Flash the factory image in fastboot
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Flash the factory image in fastboot
Click to expand...
Click to collapse
I installed both TWRP and CWM alternatively, installed factory images using flash-all.bat, install CM11. But in both cases, 1. factory image : The system get stuck in boot mode where those 4 circles keep rotating around each other, 2. In CM11, the arrow keep rotating indefinitely.
I don't know what else I can do.
Any pointers? Thanks in advance.
I am beginning to suspect hardware malfunction. In which case, is there a log somehow I can see?
As an Aside: 1. Adb refuses to see the device in fastboot mode. Not sure if this is an expected behavior. Fastboot can.
2. Stock Android USB Drivers never work. I had to get the WugFresh Development drivers.
This is Windows 8 environment.
jd1639 said:
Flash the factory image in fastboot
Click to expand...
Click to collapse
As I said earlier, both factory image and CM go into infinite loop at bootup. I have no idea what else to do.
Question now is to see if something is wrong with hardware. I don't know how to check that. Is there a way to do some diagnostics
Concoran said:
As I said earlier, both factory image and CM go into infinite loop at bootup. I have no idea what else to do.
Question now is to see if something is wrong with hardware. I don't know how to check that. Is there a way to do some diagnostics
Click to expand...
Click to collapse
You probably have a failure of the emmc. What happens if you try to lock the bootloader and then reboot? Does it stay locked?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You probably have a failure of the emmc. What happens if you try to lock the bootloader and then reboot? Does it stay locked?
Click to expand...
Click to collapse
Yes, after locking (fastboot oem lock), bootloader the status says locked and I no longer see that unlocked icon when booting.
- At the moment I have CWM, and I see advanced options to format different folders which I have already done. But what I am not able to do is to use adb to copy the image-occam-ktu84l.zip to sdcard. Only way I have been able to install any zip is using sideload. Is that normal? I wonder if I am following right steps to begin with.
- Also, are there tools that can run and check if emmc has no bad sectors etc?
- In CWM I formatted whole log of folders, and now when CWM boots, it can't find /cache/recovery/* files. Which I take as a good sign - since old stuff is now gone. From here I don't know how to proceed. Any help - very thanful.
Concoran said:
Yes, after locking (fastboot oem lock), bootloader the status says locked and I no longer see that unlocked icon when booting.
- At the moment I have CWM, and I see advanced options to format different folders which I have already done. But what I am not able to do is to use adb to copy the image-occam-ktu84l.zip to sdcard. Only way I have been able to install any zip is using sideload. Is that normal? I wonder if I am following right steps to begin with.
- Also, are there tools that can run and check if emmc has no bad sectors etc?
- In CWM I formatted whole log of folders, and now when CWM boots, it can't find /cache/recovery/* files. Which I take as a good sign - since old stuff is now gone. From here I don't know how to proceed. Any help - very thanful.
Click to expand...
Click to collapse
If you can side load you should be able to adb push a rom. When in recovery type adb devices. Does it show that your device is connected? Do you get an error?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you can side load you should be able to adb push a rom. When in recovery type adb devices. Does it show that your device is connected? Do you get an error?
Click to expand...
Click to collapse
I can sideload from adb. (adb sideload <filename>.zip while CMW is waiting for abd sideload). But can't push since adb doesn't recognize the device while in fastboot - the way fastboot can.
Concoran said:
I can sideload from adb. (adb sideload <filename>.zip while CMW is waiting for abd sideload). But can't push since adb doesn't recognize the device while in fastboot - the way fastboot can.
Click to expand...
Click to collapse
You have to be in recovery to run adb commands. The bootloader is only for fastboot commands. Try pushing while you're in recovery, not the bootloader.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You have to be in recovery to run adb commands. The bootloader is only for fastboot commands. Try pushing while you're in recovery, not the bootloader.
Click to expand...
Click to collapse
Here 's what I see when I to sideload,
In CWM, I choose 'install from zip, which takes me to next page where i chose to select from sideload. I then start sideload from 'adb sideload occam-ktu84l-factory-0d3fd624.tgz' (sometime I use the extracted zip from that tgz),
Following is what I see on CMW,
'Restarting adb
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
installation aborted'
Concoran said:
Here 's what I see when I to sideload,
In CWM, I choose 'install from zip, which takes me to next page where i chose to select from sideload. I then start sideload from 'adb sideload occam-ktu84l-factory-0d3fd624.tgz' (sometime I use the extracted zip from that tgz),
Following is what I see on CMW,
'Restarting adb
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
installation aborted'
Click to expand...
Click to collapse
Ok, you can't use that file (tgz) in cwm, adb or fastboot. What you can do is extract it and then use the zip file. But, you'll have to boot into the bootloader and then use the command
fastboot update update.zip
Sent from my Nexus 5 using XDA Free mobile app