Related
Someone Please Help
I was Rooting my Nexus S using the step by step guide to ROOT Nexus S using clockwork Mod posted by AllGamer and am stuck in the 2nd Part now.
I have unlocked the phone now but the next step is not working. Everytime I hit the command fastboot flash recovery recovery.img I get an error saying unable to load recovery.img
I have checked everything, its all fine. i tried downloading the recovery image from other sources and tried it as well, still no luck.
Someone please help me with this!
Thanks in advance!
Cheers.
PS. Im using a Nexus S running on Gingerbread 2.3.3
You may try this > http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
If your PC already has the phone driver and fastboot, you can skip several steps including downloading the sdk.
I used this yesterday to root my ns and to install a custom rom.
Cheers!
rajeevkr said:
Someone Please Help
I was Rooting my Nexus S using the step by step guide to ROOT Nexus S using clockwork Mod posted by AllGamer and am stuck in the 2nd Part now.
I have unlocked the phone now but the next step is not working. Everytime I hit the command fastboot flash recovery recovery.img I get an error saying unable to load recovery.img
I have checked everything, its all fine. i tried downloading the recovery image from other sources and tried it as well, still no luck.
Someone please help me with this!
Thanks in advance!
Cheers.
PS. Im using a Nexus S running on Gingerbread 2.3.3
Click to expand...
Click to collapse
Is cwm downloaded to the directory you are ruining the command from and also named recovery.img?
Sent from my Nexus S using XDA Premium App
.cruiser said:
You may try this > http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
If your PC already has the phone driver and fastboot, you can skip several steps including downloading the sdk.
I used this yesterday to root my ns and to install a custom rom.
Cheers!
Click to expand...
Click to collapse
Thanks a ton bro!
Worked like a charm, my phone is rooted now Finally!
krohnjw said:
Is cwm downloaded to the directory you are ruining the command from and also named recovery.img?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Thanks for the help mate.
Had made a silly mistake, i didnt navigate to the directory first, had some issues there thats all.
all sorted now! Cheers!!
Hey there!
I will explain how to install Cyanogenmod 9 OR 7(the FXP ones), found here: http://forum.xda-developers.com/showthread.php?t=1447542, and here: http://forum.xda-developers.com/showthread.php?t=1780322
You will need an unlocked bootloader, and the nessecary files to get into fastboot etc. This is not covered in my tutorial. You will have to find someone else's tutorial for that.
I made a step-by-step tutorial.
For CM10, you need a custom recovery beforehand.
If you want to install CM10, you need to flash the kernel last. (Do steps 4 - 7 after 12. Manually reboot in step 8, and instead of pressing reboot during step 12, power off and flash the kernel (step 4 - 7)
1. Make sure you have all the drivers installed, made a nandroid backup (only if you already have a custom kernel installed, if not, you can skip this) and have an usb cable, usb port (preferably no hub) and your phone near you.
2. Download the CM10/CM9/CM7 rom from their respective threads.
3. Open (don't extract!) it with WinRAR or your program of choice. Copy the boot.img to the folder your fastboot.exe is in (for me, this is C:\Program Files\Android\android-sdk\platform-tools). Then, put the zip file on your phones memory card.
3.5 (optional) Also download the Gapps (Google Play etc.) suited for your rom of choice and put the zip file on your memory card. I strongly advise you to install this.
4. Put your phone in fastboot mode (hold the search key while connecting it to your pc using the usb cable. The notification light should light up blue. When it's blue, you can release the search key.
4.5 Read steps 5-7 carefully. I have made a .bat file that will do this for you. If you choose to use it, place it in the same folder as your boot.img, and then launch. This won't work if you have renamed the boot.img. If you don't trust this, you can right-click it and hit edit. This way you'll see it says exactly the same as steps 6 and 7. Feel free to do it manually though. http://www.2shared.com/file/fPzWv4of/Flash_kernel.html
5. I assume you have Windows Vista or 7. If you do, shift-click on a empty place in your fastboot folder and click "open command prompt here" or something similar (my Windows version is Dutch, so I don't know what it's called in English).
6. Flash the kernel using this command: fastboot -i 0xfce flash boot boot.img. Note: it might be 0x0fce
7. Reboot the phone using this command: fastboot -i 0xfce reboot. Same for this one
8. While the phone is rebooting, spam the volume down key. You will now go into a recovery. Use the volume keys to navigate, and the home key to select (unless instructed otherwise on the recovery's thread). (You can now unplug the cable, but it can't hurt to keep it plugged in) If you haven't already, make a backup under "backup and restore".
9. Press wipe data/factory reset (this will of course wipe your data. Don't worry, we made a backup, remember? Note that restoring this backup will also restore your rom. Use Titanium Backup to back up your apps (requires root)). After that, also wipe your cache and Dalvik cache.
10. Select "install zip from sdcard", then "choose zip from sdcard". Navigate to the zip you put on the sdcard during step 3. It will now install the rom.
11. (optional) Also install the Gapps, same way as the rom itself.
12. After you finished installing, press reboot system now, and it will boot Cyanogenmod.
Congratulations, you just installed Cyanogenmod!
If I made any mistakes, please let me know.
I am not responsible for any bricked phones, broken GPU's, force-closes and killed pets.
If this helped you, I would appreciate a "thanks".
Good luck!
Ridder
(If you want others to be able to use this guide, leave a comment. This will bump it up =))
I thought it was 0x0fce? -I 0x0fce is not necessary either.
Sent from my R800x using XDA
Oh well, it works for me so.. I copy-paste it anyway.
savage24x said:
I thought it was 0x0fce? -I 0x0fce is not necessary either.
Sent from my R800x using XDA
Click to expand...
Click to collapse
You're right about the command correction, but I've been told that on some machines, that command is necessary to communicate with the phone correctly. So it's not that it's not necessary across the board, but it's not necessary for you. Nor is it necessary for me.
um can someone enlighten me why this is posted when there have been multiple other guides if you use the search button? sorry if i miss understood
Xperia4life said:
um can someone enlighten me why this is posted when there have been multiple other guides if you use the search button? sorry if i miss understood
Click to expand...
Click to collapse
Because the other guides are imo not very clear. Mine says exactly when to press/release buttons, how things work (CWM recovery) etc. That's why I made this.
0x0fce is the same as 0xfce in hex iirc
Sent from my Dark R800i using Tapatalk 2
Just an FYI, I linked to this thread, because it is the most comprehensive install guide for CM9,
Thanks!
paxChristos said:
Just an FYI, I linked to this thread, because it is the most comprehensive install guide for CM9,
Thanks!
Click to expand...
Click to collapse
Thank you, I really appreciate it.
You could add instead of booting the phone and then entering cwm just boot in cwm with fastboot and booting the rom. Guess it really doesn't matter now that almost all kernels have included recovery.
Thanks for the guide, ridder!
Regarding the flashing of the kernel, can a kernel (pax's modified boot.img in my case) be flashed using either Fastboot or FlashTool?
Solar.Plexus said:
Thanks for the guide, riddler!
Regarding the flashing of the kernel, can a kernel (pax's modified boot.img in my case) be flashed using either Fastboot or FlashTool?
Click to expand...
Click to collapse
Well, to be honest, I don't have any experience with FlashTool for kernels. Fastboot does what it needs for me.
Yeah, I'm just curious if Fastboot Mode is simply Fastboot inside of FlashTool.
Solar.Plexus said:
Yeah, I'm just curious if Fastboot Mode is simply Fastboot inside of FlashTool.
Click to expand...
Click to collapse
Pretty much. It pushes the kernel to a fastboot device the same way command prompt does.
captain67 said:
Pretty much. It pushes the kernel to a fastboot device the same way command prompt does.
Click to expand...
Click to collapse
Thanks for clearing that up!
I have to say that im very happy with my actual setup
A2SD Amarullz dont work for me on stock rom so i have decided to go to CM7
i have 4GB of Internal Memory and this is enough for me ... My CM7 look like stock and i have install PS Pocket/LiveWallpaper/Stock Games and Widgets + Timescape, i can say its like CM7 Hybrid
eh....
CM7.2 is more stable, anyway.
thanks so much for this b4 i was using this command for fastboot - fastboot flash boot boot.img
hey Ridder,
thank you for your guide it was very helpful for me, without it i don't know if was able to flash the cell phone of my wife. good work!
savage24x said:
I thought it was 0x0fce? -I 0x0fce is not necessary either.
Sent from my R800x using XDA
Click to expand...
Click to collapse
It's necessary for me! Needed for some PCs. Usually AMD based PCs are affected by this.
Hi guys,
Got my Nexus 4 today and want to root it, allready unlocked it but can get the recovery to get flashed. On earlier Nexuses i recall placing the recovery.img in android-sdk/platform-tools and in fastboot the command fastboot flash recovery recovery.img would do the job. But now it isn`t, what an i doing wrong? Fastboot drivers are properly installed as i was able to unlock the phone with adb.
Would appreciate some helpfull tips.
did you rename it recovery.img?
Sent from my Nexus 4 using xda premium
Does it return an error or is it just not sticking?
El Daddy said:
Does it return an error or is it just not sticking?
Click to expand...
Click to collapse
Yes i named it recovery.img and it doesn`t seem to find to file, no other messages like misstakes/fc.
gee2012 said:
Yes i named it recovery.img and it doesn`t seem to find to file, no other messages like misstakes/fc.
Click to expand...
Click to collapse
Why not just use the toolkit...makes it 1000000000 times easier...
gee2012 said:
Yes i named it recovery.img and it doesn`t seem to find to file, no other messages like misstakes/fc.
Click to expand...
Click to collapse
This may be a silly suggestion but windows auto names the extension. So really you just have to name the file "recovery"
zbt1985 said:
Why not just use the toolkit...makes it 1000000000 times easier...
Click to expand...
Click to collapse
That`s true, but i would like to be able do it with adb also.
El Daddy said:
This may be a silly suggestion but windows auto names the extension. So really you just have to name the file "recovery"
Click to expand...
Click to collapse
Will try that bro, thanks
zbt1985 said:
Why not just use the toolkit...makes it 1000000000 times easier...
Click to expand...
Click to collapse
Because he won't be the one to come crying when he "bricks" his phone...
And he'll be learning.
And cutting out the middle man...
All the toolkit is is a GUI interface for fastboot commands.
One wrong line on the developer's side could literally brick devices (yes, unlikely).
Why don't YOU stop relying on toolkits?
ADB and fadtboot are even simpler.
whats the error message
Did you CD into the fastboot folder properly?
Sent from my Nexus 4 using Tapatalk 2
After renaming the recovery the flash succeeded, but when in CWM i cannot see the SU/Busybox zip. Do i need to flash a unsecure boot first?
Sorry for the noobish questions, been with Samsung devices a long time, and they didn`t have fastboot
gee2012 said:
After renaming the recovery the flash succeeded, but when in CWM i cannot see the SU/Busybox zip. Do i need to flash a unsecure boot first?
Sorry for the noobish questions, been with Samsung devices a long time, and they didn`t have fastboot
Click to expand...
Click to collapse
I'm not familiar with how you are rooting, I just flashed everything with fastboot. I assume you flashed recovery and are flashing su in recovery? I do believe you need an insecure boot first.
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
Did you CD into the fastboot folder properly?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Yes i guess so, cd c:\android-sdk\platform-tools , fastboot is located in platform-tools afaik.
gee2012 said:
Yes i guess so, cd c:\android-sdk\platform-tools , fastboot is located in platform-tools afaik.
Click to expand...
Click to collapse
I thought it was in the adb folder?
Forgive me, but I keep a folder called adb on the root of my C: drive with fastboot.exe in it.
Sent from my Nexus 4 using xda app-developers app
Adb is also in platform-tools
Sent from my Nexus 4 using xda premium
Did you place the .zip file on your phone before or after you unlocked the bootloader?
Unlocking the bootloader completely wipes the phone so the file would be gone.
The good news is you can push the file with adb while booted into recovery.
adb push nameoffile.zip /storage/sdcard0
Sent from my Nexus 4
gee2012 said:
After renaming the recovery the flash succeeded, but when in CWM i cannot see the SU/Busybox zip. Do i need to flash a unsecure boot first?
Sorry for the noobish questions, been with Samsung devices a long time, and they didn`t have fastboot
Click to expand...
Click to collapse
make sure you're looking in the correct path in cwm i think its sdcard0 or something like that. or just flash twrp it goes straight to the storage directory by default
Sent from my Nexus 4 using xda premium
The 2 files i see in CWM are not located on sdcard0 but in the emulated file. So how to get in sdcard0 when in CWM, that is the question.
Is this the correct adb command: adb push C:/android-sdk/platform-tools/SU_Busybox_Package sdcard0/SU_Busybox_Package for pushing the file to sdcard0?
gee2012 said:
The 2 files i see in CWM are not located on sdcard0 but in the emulated file. So how to get in sdcard0 when in CWM, that is the question.
Is this the correct adb command: adb push C:/android-sdk/platform-tools/SU_Busybox_Package sdcard0/SU_Busybox_Package for pushing the file to sdcard0?
Click to expand...
Click to collapse
if u can get to them from the emulated irectory , just flash from there. it shouldn't make a difference
Sent from my Nexus 4 using xda premium
Hey all...I'm sorry for sounding like such a noob (trust me i'm not as big as one as you may think) I'm just having a hard time grasping the idea of updating my Nexus. Let me explain:
I'm currently running stock rom but have Matr1x kernel on my phone. The only thing I've changed so far are a few icons (by pulling files from the nexus toolkit, replacing the icons and pushing them back to my phone).
I would prefer not to have to go through and redo all my icons, and would just like to get 4.2 onto my phone.
I looked over the directions on how to do this, but for the life of me (and IDK why) i can't seem to get my head around it...and it's making me feel real real stupid...
can someone please explain to me like i'm 5 how to do this? Or maybe just point me in the direction of a youtube video that will walk me through it...?
Thanks in advance and sorry for being such a noob...
Why not just backup the apk's+data you edited, save them to your computer, flash the stock images, root and restore the apps+data?
Edit: And flash a 4.2.2 kernel.
estallings15 said:
Why not just backup the apk's+data you edited, save them to your computer, flash the stock images, root and restore the apps+data?
Edit: And flash a 4.2.2 kernel.
Click to expand...
Click to collapse
Do I backup via toolkit or with titanium backup?
Also, i tried getting back to stock but for some reason couldn't get it to flash the img file...idk what i was doing wrong...maybe u can give me some pointers on it.
Idk y i'm having such trouble with this, i've been on android since the very begining (had a g1 2 months after it came out)...I guess I was just spoiled with my vibrant being so easy...
zbt1985 said:
Do I backup via toolkit or with titanium backup?
Also, i tried getting back to stock but for some reason couldn't get it to flash the img file...idk what i was doing wrong...maybe u can give me some pointers on it.
Idk y i'm having such trouble with this, i've been on android since the very begining (had a g1 2 months after it came out)...I guess I was just spoiled with my vibrant being so easy...
Click to expand...
Click to collapse
First of all, ditch the toolkit. You don't learn anything when you use toolkits. Probably why you're in the situation you're in.
Backup with titanium, or just make a nandroid and use titanium to extract the apps later.
To flash stock images:
Reboot into bootloader.
Open command prompt and "cd" to the directory where fastboot lies.
Type these commands -
fastboot flash system system.img
fastboot flash boot boot.img
Optional -
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Then reboot
estallings15 said:
First of all, ditch the toolkit. You don't learn anything when you use toolkits. Probably why you're in the situation you're in.
Backup with titanium, or just make a nandroid and use titanium to extract the apps later.
To flash stock images:
Reboot into bootloader.
Open command prompt and "cd" to the directory where fastboot lies.
Type these commands -
fastboot flash system system.img
fastboot flash boot boot.img
Optional -
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Then reboot
Click to expand...
Click to collapse
Here's where the confusion lies...what do u mean cd where fastboot lies...I know how to cd, but not sure what you mean by where the fastboot would be...
zbt1985 said:
Here's where the confusion lies...what do u mean cd where fastboot lies...I know how to cd, but not sure what you mean by where the fastboot would be...
Click to expand...
Click to collapse
I extract the adb folder from the android SDK and drop it in C:\.
So for me, it's "cd C:\adb"
I believe in the SDK it's in platform-tools or some such jazz. You can always do a search on your computer...
You have installed the android SDK, right? If not, your toolkit might have the adb and fastboot files in it. Grab them from there. Make it work. You can do it.
estallings15 said:
I extract the adb folder from the android SDK and drop it in C:\.
So for me, it's "cd C:\adb"
I believe in the SDK it's in platform-tools or some such jazz. You can always do a search on your computer...
You have installed the android SDK, right? If not, your toolkit might have the adb and fastboot files in it. Grab them from there. Make it work. You can do it.
Click to expand...
Click to collapse
Yes I have the SDK as I use eclipse to complie the apps i make (i cheat)...
I see adb.exe, but not the folder for adbe...
Thanks for all the help man, I hit the thanks button for u!
zbt1985 said:
Yes I have the SDK as I use eclipse to complie the apps i make (i cheat)...
I see adb.exe, but not the folder for adbe...
Thanks for all the help man, I hit the thanks button for u!
Click to expand...
Click to collapse
There should be a fastboot.exe and a few .dll files, as I recall.
Could someone upload all the latest files needed for adb and fastboot in a zip for him? Won't take you 5 minutes. I'm not by my computer.
Why not flash CM10.1 or latest Xylon.
Back up apps with titanium, flash ROM, flash gapps, restore via titanium.
Or do you want stock?
[Nexus⁴]
dEris said:
Why not flash CM10.1 or latest Xylon.
Back up apps with titanium, flash ROM, flash gapps, restore via titanium.
Or do you want stock?
[Nexus⁴]
Click to expand...
Click to collapse
I wanted stock...i only want this for 1) getting updates faster than cm 2) being able to update the hard way and not be a kiddy about it...
Better for me to learn...
http://forum.xda-developers.com/showthread.php?t=2145848
Scenario #3
Continue to section C.
Sent from my Nexus 4 using xda premium
just follow efran's guide, he got the step by step: http://forum.xda-developers.com/showthread.php?t=2010312
gravitysandwich said:
http://forum.xda-developers.com/showthread.php?t=2145848
Scenario #3
Continue to section C.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
That's what is confusing me...
Sent from my Nexus 4 using xda app-developers app
Download this http://d-h.st/iy0. Unzip it. Plug your phone I'm the computer, go to the directory where you installed the toolkit. (Right click on the shortcut/properties it should say it there) go in the directory, FLASH ITEMS HERE folder. Put the boot.img and system.img in there. (Radio.img is optional). Open the toolkit and go to flash images. Flash boot.img first. The directions should be on the toolkit. Then system and etc... Make sure you put it in fast boot or type no when the toolkit asks if your in fastboot mode. This will NOT delete your data. When you flashed everything, go to settings on your phone. (If there is a bug with updating it through settings, clear cache and data for Google services framework and force stop it. Then go to cache on root explorer (/cache) and delete the corrupt/partial update and try Again). Once you reboot, cwm will ask if you want to install update. Hit yes and install untrusted package. Then it will try to replace cwm with stock recovery so hit no. If you lost your root then get supersu from the play store and install the binaries via cwm.
Hope this helps.
Sent from my Nexus 4 using xda premium
---------- Post added at 12:11 AM ---------- Previous post was at 12:02 AM ----------
Btw I chose to flash it through toolkit because I was afraid you would've got the commands mixed up and you would never get it. One day you probably will
Sent from my Nexus 4 using xda premium
Muchos gracias.
Would thank but on my phone
Sent from my Nexus 4 using xda app-developers app
zbt1985 said:
Muchos gracias.
Would thank but on my phone
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You can thank you your phone.
So it worked? Your welcome. I'm guessing you lost root. Here is the zip if you need it
http://download.chainfire.eu/314/SuperSU/UPDATE-SuperSU-v1.20.zip
Sent from my Nexus 4 using xda premium
gravitysandwich said:
So it worked? Your welcome. I'm guessing you lost root. Here is the zip if you need it
http://download.chainfire.eu/314/SuperSU/UPDATE-SuperSU-v1.20.zip
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Haven't had a chance to try it, doing it now...thanks!
hello guys this guide helps you to root your nexus 4 (4.3) and install custom recovery
things needed
1)superuser http://d-h.st/Hhw
2)twrp http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.0.0-mako.img
3)andriod sdk (google it)
* [dont have sdk? then download this http://d-h.st/jCU a replacement for sdk/platformtools (this tools include stuff for windows,linux and mac too.)]
4)adb drivers installed (follow the below mentioned guide)
note:- this is almost same process as this guide http://forum.xda-developers.com/showthread.php?t=2018179 but just updated for 4.3 version
ROOTING process
1)I hope your boot loader is unlocked, if not first unlock it and then start the rooting process and turn on usb debugging (follow above mentioned guide for unlocking bootloader and to turn on usb debugging) after unlocking bootloader reboot device and then copy root.zip(links above) into your phones storage and then reboot to fastboot
2)now download the twrp recovery image and rename it to twrp and move it to sdk/platform tools. in the same directory(i.e platformtools directory) open cmd prompt(to open cmd prompt press shift+rightclick at the same time and select open cmd prmpt window option) and type (without quotes) "fastboot flash recovery twrp.img" and thats it you have flashed twrp
3)now go to twrp (recovery mode) and flash the root.zip (that u copied to the phones storage earlier) and that's it u have obtained the root access.
im not responsible if u bricked your device do it at your own risk
follow this wonderful video if u have any problem or trouble http://www.youtube.com/watch?v=jn5ih0omlxI
hit thanks button if this thread helped ya
There is new SuperSU v1.51:
http://forum.xda-developers.com/showthread.php?t=1538053
Your uploaded SuperSU is still v1.44.
thank you
gogol said:
There is new SuperSU v1.51:
http://forum.xda-developers.com/showthread.php?t=1538053
Your uploaded SuperSU is still v1.44.
Click to expand...
Click to collapse
Thank you I will update that!
thank you
gogol said:
There is new SuperSU v1.51:
http://forum.xda-developers.com/showthread.php?t=1538053
Your uploaded SuperSU is still v1.44.
Click to expand...
Click to collapse
BTW you can update that manually via WiFi from playstore as chainfire mentioned in the thread that "if u already have root root access then update it from playstore"
Except the bug fixed version of supersu, there's nothing different from the original thread...
*****Save your fingers the work and hit "Thanks" instead of typing it...!!*****
NEXUS⁴ Stock Android 4.3
---------- Post added at 12:40 AM ---------- Previous post was at 12:39 AM ----------
gogol said:
There is new SuperSU v1.51:
http://forum.xda-developers.com/showthread.php?t=1538053
Your uploaded SuperSU is still v1.44.
Click to expand...
Click to collapse
The latest su version is not compatible with 4.3 yet...only v1.43 is compatible presently...
*****Save your fingers the work and hit "Thanks" instead of typing it...!!*****
NEXUS⁴ Stock Android 4.3
when i enter the command line the command window gets stuck at <waiting for device> ........ I made sure that i have the drivers are properly configured and the nexus unlocked ...... any ideas why this happens ??
M.Zaki said:
when i enter the command line the command window gets stuck at <waiting for device> ........ I made sure that i have the drivers are properly configured and the nexus unlocked ...... any ideas why this happens ??
Click to expand...
Click to collapse
Hi,
I can suggest you some thing but i am not responsible if u bricked your device do it at your own risk
I had same issue " waiting for device" SO you need to install correct drivers for your device i can suggest you to download nexus 4 toolkit version 2 from here http://forum.xda-developers.com/showthread.php?t=1995688 and you need disconnect your nexus from usb and open your toolkit and you need :
1.choose option 13 "13. Android 4.2.2 [Build JDQ39]" (I know that your version is 4.3 but the drivers for PC is samething)
2.It will download drivers for your pc
3.Now choose option 1 that say " 1. Install Device Drivers on your PC [DO THIS FIRST] [UnPlug Device First] "
4. After driver installation you can close this tool and try again to flash your recovery like you did it before with (See above "ROOTING process")
Let me know if you succeed
Good luck
When I try to load the YT vid it says "invalid request"...
Oh its more than a vid. I am sorry in the android app it doesnt show the whole post for any reason.
And why download the whole sdk? Grab the platform tools from efrant's tutorial on how to flash a factory image. Then just place the desired recovery in the same directory and you can flash the recovery.
Sent from my Nexus 4 using xda app-developers app
amnon.m said:
Hi,
I can suggest you some thing but i am not responsible if u bricked your device do it at your own risk
I had same issue " waiting for device" SO you need to install correct drivers for your device i can suggest you to download nexus 4 toolkit version 2 from here http://forum.xda-developers.com/showthread.php?t=1995688 and you need disconnect your nexus from usb and open your toolkit and you need :
1.choose option 13 "13. Android 4.2.2 [Build JDQ39]" (I know that your version is 4.3 but the drivers for PC is samething)
2.It will download drivers for your pc
3.Now choose option 1 that say " 1. Install Device Drivers on your PC [DO THIS FIRST] [UnPlug Device First] "
4. After driver installation you can close this tool and try again to flash your recovery like you did it before with (See above "ROOTING process")
Let me know if you succeed
Good luck
Click to expand...
Click to collapse
I succeeded but I don't know exactly what I did to make it work ....... I got bored after posting my question when I returned I tried it again without looking to the thread and it worked ..... but thnx for your concern
M.Zaki said:
I succeeded but I don't know exactly what I did to make it work ....... I got bored after posting my question when I returned I tried it again without looking to the thread and it worked ..... but thnx for your concern
Click to expand...
Click to collapse
I am very happy
M.Zaki said:
I succeeded but I don't know exactly what I did to make it work ....... I got bored after posting my question when I returned I tried it again without looking to the thread and it worked ..... but thnx for your concern
Click to expand...
Click to collapse
so it might not have recognized your adb drivers at the first time.or you could have just downloaded the nexus4toolkit by mrskip and installed adb from it. anyways did u root it?
Thibaultvw said:
When I try to load the YT vid it says "invalid request"...
Oh its more than a vid. I am sorry in the android app it doesnt show the whole post for any reason.
And why download the whole sdk? Grab the platform tools from efrant's tutorial on how to flash a factory image. Then just place the desired recovery in the same directory and you can flash the recovery.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
now try the link i fixed it
punitthereddevil said:
Except the bug fixed version of supersu, there's nothing different from the original thread...
*****Save your fingers the work and hit "Thanks" instead of typing it...!!*****
NEXUS⁴ Stock Android 4.3
---------- Post added at 12:40 AM ---------- Previous post was at 12:39 AM ----------
The latest su version is not compatible with 4.3 yet...only v1.43 is compatible presently...
*****Save your fingers the work and hit "Thanks" instead of typing it...!!*****
NEXUS⁴ Stock Android 4.3
Click to expand...
Click to collapse
as i mentioned in the thread "this is the similar guide as that is mentioned above just updated for 4.3 version"
Just one question do the recovery flashed this way stick after reboot even on stock ROM? I remember something about having yo flash an additional ZIP for that...
Sent from my Nexus 4 using Tapatalk 4 Beta
Hi guys,
I know this topic is about installing custom recovery, but does anybody knows hot to root android 4.3 without flashing custom recovery? Yesterday I tried to boot both CWM and TWRP using:
Code:
fastboot boot recovery.img
All I got was a blank screen...
bartiki said:
Hi guys,
I know this topic is about installing custom recovery, but does anybody knows hot to root android 4.3 without flashing custom recovery? Yesterday I tried to boot both CWM and TWRP using:
Code:
fastboot boot recovery.img
All I got was a blank screen...
Click to expand...
Click to collapse
i have the same problem with "fastboot boot xxxx.img"!! both CWM and TWRP , return blank!
I actually found this today:
http://forum.xda-developers.com/showthread.php?t=2380675
they say:
the new version of bootloader shipped with Android 4.3 factory image changed some of the "fastboot boot" command so you need to specify a kernel commandline to use "fastboot boot" command.
Click to expand...
Click to collapse
for Nexus 4, it's:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
although I don't have time to test it out right now
bartiki said:
I actually found this today:
http://forum.xda-developers.com/showthread.php?t=2380675
they say:
for Nexus 4, it's:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
although I don't have time to test it out right now
Click to expand...
Click to collapse
yes.. now i find this me too and work!!!
i install the SuperSU , but now do n't installing the binary file. stuck on "installing, please wait..." any ideas?
EDIT: uninstall the update of SuperSU (v.1.51) and return to stock (that flashed before v1.43) AND WORKING!! ( no prompt to update the binary file..) any ideas? the v.1.51 maybe not working??
bbsnick said:
yes.. now i find this me too and work!!!
i install the SuperSU , but now do n't installing the binary file. stuck on "installing, please wait..." any ideas?
EDIT: uninstall the update of SuperSU (v.1.51) and return to stock (that flashed before v1.43) AND WORKING!! ( no prompt to update the binary file..) any ideas? the v.1.51 maybe not working??
Click to expand...
Click to collapse
Somebody mentioned this on first page newest su not compatible only v1.43
Sent from my Nexus 4 using Tapatalk 4 Beta
boysetsfire said:
Just one question do the recovery flashed this way stick after reboot even on stock ROM? I remember something about having yo flash an additional ZIP for that...
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yep it still works after reboot . no problem with that