yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] :
We probably live in different time zones ( I'm in GMT+5:30 ). I dunno whether I'll be free then. I'm free all the time though (student, lulz), so I'll stay online as long as I can. Maybe we can find a bug/error together. Or, I've derped something.:)

Yeah, it's weird. It seems like I'm the only one with that problem?

I've sent you a 'Hi!' message and added you on G+. :)

Thanks!
[Nexus 4 Original Android Development] keanyiap:
Awesome toolkit, cant find a better toolkit than your's, wugfresh toolkit is just easy and easy for me, thanks for your hard work!!:good:
[Nexus 4 Original Android Development] :
After the unlock, I flashed a CM10 stable, it works great. No problem with that.

And yesterday i tried to launch the recovery again to add some features and same as Quinte on a previous post, i have "a android on its back with a red exclamation mark".

So I understand i have reflashed "standard recovery" ??

As i made some configurations i don't want to lose, is it possible to flash "twrp" or "cwm" again without making a full wipe ?
[Nexus 4 Original Android Development] WugFresh:
Yup. Its very simple with v1.6.4. In advanced utilities just press the flash 'recovery' button. Cheers.

{{ WugFresh }}
[Nexus 4 Original Android Development] geokilla:
I did a search with keywords CWM so forgive me if it's been answered before.

I prefer CWM over TWRP, so naturally, I want CWM installed on the Nexus 4. However when I use the Root Toolkit to install CWM, it finishes successfully, but then I actually don't have CWM Recovery. TWRP Recovery flashes successfully though, as I'm able to boot into TWRP using both the script and going into it via the Bootloader.
[Nexus 4 Original Android Development] WugFresh:
The default is set to flash TWRP when rooting. Change it to CWM in the options menu. Yo can also use the flash 'recovery' button in advanced utilities.

{{ WugFresh }}
[Nexus 4 Original Android Development] geokilla:
Which is what I did. I selected to flash CWM and not TWRP. But when I boot into Recovery, CWM Recovery doesn't work. Only TWRP works.
[Nexus 4 Original Android Development] WugFresh:
During the root script, even if it is set to flash CWM recovery it actually also uses TWRP temporarily to then flash the root.zip files. TWRP is utilized because it allows for the use of openrecoveryscript for automating tasks in custom recovery. CWM should still be flashed to your device however. If you use the toolkits advanced utilities button "reboot recovery" or manually boot into recoery from the bootloader your device should sucessfully boot into CWM.

What do you mean by "CWM doesn't work"? Can you please elaborate? I just tested the root script again right now with CWM selected and it successfully flashed CWM for me. Please confirm if it flashed successfully then let me know. Cheers.

{{ WugFresh }}
[Nexus 4 Original Android Development] geokilla:
Manual boot from Bootloader or using the scripts and booting into CWM doesn't work. It's like CWM didn't get installed.
[Nexus 4 Original Android Development] WugFresh:
Again, can you please explain what actually happens? Do you see an android on its back with an exclamation mark? Try and avoid saying "doesn't work".

Are you certain that you selected the correct device and build? Did the toolkit at least download the latest CWM for your device? If you still have problems please add me on gchat.

{{ WugFresh }}
[Nexus 4 Original Android Development] geokilla:
It just hangs on the Google splash screen as it tries to boot into CWM. I'm on custom ROM now as I flashed custom ROM via TWRP. Don't have gchat.... Maybe PM?
[Nexus 4 Original Android Development] WugFresh:
Ahh. Ok. That is a strong indication that you have specified the wrong device or build in the toolkit. It is trying to boot an incompatible cwm img file.

{{ WugFresh }}
[Nexus 4 Original Android Development] geokilla:
Nope... I was on Android 4.2.2. The JDQ39 build.
[Nexus 4 Original Android Development] WugFresh:
I just figured out what was wrong. I just hash checked the cwm-mako file on goo.im and it wasn't correct, it must have been an incomplete upload. I just reuploaded it now and updated the masterlists. Delete the "recovery-clockwork-touch-6.0.3.1-mako.img" file thats in the toolkits directory

\data\Recovery_Custom\CWM

Then update the toolkit [Ctrl + U]. Then start over and everything should work. Thank you for notifying me.

{{ WugFresh }}
[Nexus 4 Original Android Development] Globespy:
Thanks, but will this leave TWRP so i can copy a new custom ROM over via USB?
[Nexus 4 Original Android Development] geokilla:
Yes
[Nexus 4 Original Android Development] Globespy:
Thanks.
[Nexus 4 Original Android Development] tylercarter:
[MENTION=3110798]WugFresh[/MENTION] could you please elaborate on the force flash option? tyty :highfive:
[Nexus 4 Original Android Development] WugFresh:
Sure. Just so you know if you try enabling it in the options menu it will bring up a message box explaining it in some detail. Since you asked here though, I will provide a more in depth description.

When flashing stock normally, the factory image package gets extracted and the contents look like this:

[Fore the occam-jdq39-factory-345dc199.tgz package:]

bootloader-mako-makoz10o.img
radio-mako-m9615a-cefwmazm-2.0.1700.48.img
image-occam-jdq39.zip

Notice the zip file "image-occam-jdq39.zip".

The way that package then gets flashed is that the script issues two fastboot flash commands, i.e.

fastboot flash bootloader-mako-makoz10o.img
fastboot flash radio-mako-m9615a-cefwmazm-2.0.1700.48.img

And then another special fastboot command that looks like this

fastboot -w update image-occam-jdq39.zip

That "-w update" command actually performs some checks before proceeding. More specifically, within that zip file there is an "android-info.txt" which specifies certain requirements that must be met before that package is flashed.

The android-info.txt for the occam-jdq39-factory-345dc199.tgz package looks like this:

require board=mako
require version-bootloader=MAKOZ10o
require version-baseband=M9615A-CEFWMAZM-2.0.1700.48

That means, its looking for the Nexus4 motherboard (mako), that specific bootloader version, and that specific baseband version. If all the checks pass, then the contents of that zip package get flashed.

With Force Flash Mode, that "-w update" command is never issued, but rather that zip package is further extracted (which contains a boot.img, recovery.img, system.img ...etc) and the individual img files are flashed one at a time. So;

fastboot flash boot.img
fastboot flash recovery.img
fastboot flash system.img
fastboot flash userdata.img

That means no CHECKS are performed at all. This is useful if you are on a build/custom-build that doesn't meet the requirements for flashing stock. In previous toolkit versions if the user had this problem, the solution would be for the end user to go ahead and find that zip file, extract it and individually flashed the required img file needed -- and then try reflashing stock. [Too many steps in my opinion, so I made this feature].

It should be noted that 'Force Flash' mode should ONLY be used if the user is CERTAIN they have specified the correct device in the toolkit. If the user accidentally selected the wrong device then the toolkit would flash incompatible firmware.

Only use "Force Flash" mode if you get an error when flashing stock about not meeting a certain requirement.

Do NOT use 'Force Flash' mode if the requirement error you get is about the board type.. That means that you specified the wrong device.

I hope that explains it. Cheers.

{{ WugFresh }}
[Nexus 4 Original Android Development] tylercarter:
Excellent! Thank you.
[Nexus 4 Original Android Development] sayogs:
May I know how to install twrp on gnex and start without connected to USB????
[Nexus 4 Original Android Development] wizshaw:
Ok.. Here is my situation

I wiped the SD card on my phone. But I still have recovery on it as well as the bootloader.

I would like to manually push a rom file as well as the gapps to my phone so I can flash it.

But how can I do this without having it booted and loaded into debug mode.

The kit requires this, sooo is there a way to do it through the user interface? And what are the commands?

If anybody can help that would be great.

(If already installed the toolkit, and it reads that my phone is connected when I have the bootloader active)

Chris
[Nexus 4 Original Android Development] Virus1x:
If I purchased my n4 straight from google do I still need to select UNLOCK in the toolkit?
[Nexus 4 Original Android Development] Hishighness731:
In any case you need to unlock your device first to install custom roms,kernels,mods..

Sent using Tapatalk
[Nexus 4 Original Android Development] Rashiel:
Hej..

Need this TK for a Galaxy Nexus and a Nexus 4...

No problem, to use this for this two different phones, right?

Ah - ive got many Problems to install the driver - i followed the Instruktion..

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] WugFresh:
Yes you can use it on multiple devices. You may have to switch usb ports, but it should work. Try alternate driver solutions, there are four options included.

{{ WugFresh }}
[Nexus 4 Original Android Development] Rashiel:
Okay, so maybe the recommended one is not the best?

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] WugFresh:
Its computer dependant. I chooses the one with the highest success rate, but it may not be the one that works for your setup.

{{ WugFresh }}
[Nexus 4 Original Android Development] Sorty:
Thanks for everything rooted and ready to go!
[Nexus 4 Original Android Development] Rashiel:
#3 is working with Galaxy Nexus ;)

Now rooting and then taking care to my Nexus 4;)

If everything will work right - youll get a donation :P

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] Soundchasr:
I need to return my phone back to Google for warranty replacement. Will "Back to Stock" take care of everything so I can send it back with no issues from Google?
[Nexus 4 Original Android Development] Irthu:
I spend the last three hours trying to get my drivers installed. I tried all the 4 methods i am still not able to get my adb detected.

I am using a windows 8 (64bit) . i have np clue whats going. Wrong i havent rooted or made any modifications. Any help ? :/
[Nexus 4 Original Android Development] matthewgwilt:
Yeah and lock your bootloader back up obviously
[Nexus 4 Original Android Development] kicksilver:
Hello fellows,

I tried using the toolkit yesterday, and in driver installation guide step 1, I uninstalled everything related to my Nexus, or Google.

Now, whenever I plug the device into my PC, I get a message saying the USB Device was not recognized...

It does it regardless of being with USB Debugging on or off.

It doesn't even charge anymore.

Is this possible to be undone?
[Nexus 4 Original Android Development] WugFresh:
Proceed to step 2 and install drivers.. If one solution doesn't work, try another.

{{ WugFresh }}
[Nexus 4 Original Android Development] Irthu:
I have been trying to get my drivers running from two days. Not happening.. I am using a win8 i did the signature enforcement thing and evrything.

And when i try installing adb and bootloader drivers... It says they are up to date. But when i do the final test it tells it fails.
[Nexus 4 Original Android Development] lmarranzino:
Okay got a real NOOB question here. Finally going to pick up the Nexus4.

Just follow the guide to Unlock first than proceed with Root correct _ This will leave me with Rooted unlocked correct ? No worried about back up as I wont't have all my stuff loaded as of yet.

Saying goodbye to Samsuck once and for all...:cool:

EDIT: Got it thanks.....
[Nexus 4 Original Android Development] aelsharawi:
great and powerful app,thanks

I think you will have to upgrade the app to fit the new android 4.3
[Nexus 4 Original Android Development] WugFresh:
Thank you! When google releases the official factory images for 4.3 I will.

{{ WugFresh }}
[Nexus 4 Original Android Development] Soundchasr:
Also running win8 64 bit and can't get it to work. Have installed the drivers multiple times. The computer "sees" it as an attached device because it will let me eject it but doesn't "see" it in a way that the toolkit recognizes it or that Windows Explorer recognizes it.
[Nexus 4 Original Android Development] Soundchasr:
Aha! Found this solution and it worked!

Device Manager - right click device (Android ADB OR Nexus 4 ADB interface)

- Update Driver Software

- Browse my computer for driver software

- Let me pick from a list of device drivers on my computer

- then choose "MTP USB Device" OR "USB composite driver"

- Next

here you go instant discover
[Nexus 4 Original Android Development] randomnoob83:
If I flash back to stick will it delete my internal storage I.e my pictures, music, and downloads etc.
[Nexus 4 Original Android Development] WugFresh:
Yes.

{{ WugFresh }}
[Nexus 4 Original Android Development] justin11141:
to flash the 4.3 factory image do i need to relock my bootloader or unroot or can i just flash it using this toolkit and im done?
[Nexus 4 Original Android Development] TecQuality:
no.
[Nexus 4 Original Android Development] derDoctor:
Can I flash an android 4.3.3 image rooted or unrooted?

Can I flash an android 4.3.3 image rooted or unrooted with that tool or is there an update of the tool necessary???

I only ask because i dont wont to ruin my device
[Nexus 4 Original Android Development] matthewgwilt:
4.3 (from developer site)

I cant seem, for the life of me, to install the 4.3 image using this toolkit... Am I doing something wrong? Like do I have to wait for the toolkit to update or something?
[Nexus 4 Original Android Development] sid21:
I guess its already released..official images of 4.3 by google on their site
[Nexus 4 Original Android Development] Rashiel:
Let Wugs do his work.. We can flash it early enough

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] WugFresh:
Yeah, it was just updated on Google's site. I am just one person :)

In the toolkit turn on auto updating in the options. When I get back from the gym around 6/6:30 I will go home and update the necessary things and upload necessary files for full 4.3 support.

So ETA would be sometime after that this evening.

If any of you are impatient you can go ahead and flash the 4.3 factory image from Google's site with the "I downloaded the image myself" option in the flash stock interface. Then when it asks you for the hash, enter the corresponding md5 value posted on Google's site. Then you can root with "any build".

I always will try my best to keep the toolkit up to date with the latest files. It just got released today, I will have it updated tonight. Cool? :)

{{ WugFresh }}
[Nexus 4 Original Android Development] TecQuality:
Yes, already flashed manually using fastboot commands.?
[Nexus 4 Original Android Development] matthewgwilt:
Thanks man... BTW i already tried what you said and it doesnt work... i tried downloading image several times too just to make sure but nothing flashes... something about wrong baseband... and one message was cant work with locked bootloader??

EDIT: REMOTE: DOES NOT WORK WITH LOCKED DEVICE.. is the message I get followed by "wrong baseband"
[Nexus 4 Original Android Development] sid21:
For people who have used his toolkit and updated their phones to 4.3 ota

Then no worries you guys are already rooted..

For those who have flashed google images by downloading them..please wait..the toolkit needs to be updated and roms developers are also working so we need to give them time..

Hope i am clear about the toolkit..
[Nexus 4 Original Android Development] WugFresh:
Well if your device is locked, then yeah.. You can't flash stock. If you do unlock and still get the baseband error then you can enable "force flash" mode in the toolkit options menu to override all checks when flashing.

{{ WugFresh }}
[Nexus 4 Original Android Development] WugFresh:
Typically taking otas will break root. You can reroot with the toolkit with "any build" mode, or wait until later tonight and the toolkit will list 4.3 as a build in the device selection.

{{ WugFresh }}
[Nexus 4 Original Android Development] sid21:
Ohh i see..no conflicts with rooting..then i guess roms and kernels are only things which get the work..

Well would update the toolkit when you do soo cause now it would be handy for flashing new 4.3 roms and rooting ;)
[Nexus 4 Original Android Development] derDoctor:
the question is

is it possible to flash the google 4.3 stock image. for me its not necessary if its rooted or not.
[Nexus 4 Original Android Development] matthewgwilt:
Force flash caused a bootloop... No worries I can wait
[Nexus 4 Original Android Development] bigsky2:
I know this is not directly related to Wug's toolkit (great work!), but if I have installed Rootkeeper (Voodoo) and protected my root, can I proceed to update via OTA to 4.3 and restore root?

Or would it be preferable to root again using Wug's toolkit?

I originally rooted and unlocked my Nexus using Wug NRT 1.6.4.
[Nexus 4 Original Android Development] WugFresh:
If that app succeeds at preserving root, no need to use the toolkit to root again.

{{ WugFresh }}
[Nexus 4 Original Android Development] shobuddy:
I'm currently on rooted 4.2.2. I did not use the Wug toolkit to root. Do I need to unroot/go back to full stock before taking the OTA? Or can I just take the 4.3 OTA on my rooted phone and then root? I keep reading conflicting reports that say if you take OTA over rooted phone, it will mess up the phone. Other say its safe to take the OTA on rooted but you will just have to reroot.
[Nexus 4 Original Android Development] bigsky2:
Fair enough! I'll wait for a few courageous souls to try it out.

This is the app I was mentioning - Voodoo OTA RootKeeper. Please disregard if you are already familiar with it ;)

I wanted to also take a moment to t

hank you for your great work on the toolkit

. The Nexus community appreciates it very much!

---------- Post added at 02:15 PM ---------- Previous post was at 02:10 PM ----------

You can proceed to update via OTA to 4.3, but you will lose root status by doing so. I think this is what you refer to as "it will mess up the phone".

In this case, you could easily reroot your device (using Wug's NRT or Voodoo's OTA RootKeeper - assuming it works) after you have successfully updated.

If you want to be totally safe, you could revert your phone back to unroot state, locked bootloader state, stock rom/kernel/recovery, and then proceed to update via OTA. This is probably a more time consuming option and you'd have to backup and restore your data since returning to stock state will wipe your phone, and also re-root and unlock the bootloader again.
[Nexus 4 Original Android Development] Alienfreak:
$10 for you for your new Toolkit! :)

Have a few beer on me :)

I am already prone to my flash addiction... ;)

The downsides of once having a CM nightly phone...

I am hitting F5 like mad :)
[Nexus 4 Original Android Development] xploPR:
Im trying to unroot my device, but when im on the bootloader screen, that is installing the factory image it says "fails on checking version baseband." Then it just sits on the bootloader until i manually reboot the device, Any help would be greatly appreciated.
[Nexus 4 Original Android Development] matthewgwilt:
I had that too... The toolkit will be updated in the next few hours... then everything will work
[Nexus 4 Original Android Development] xploPR:
Oh cool, didn't know it was due to the toolkit version, thanks for letting me know. :good:
[Nexus 4 Original Android Development] bigsky2:
Hi Wug,

Looks like 4.3 has introduced some new things that prevent an app such as Voodoo OTA RootKeeper to restore root.

Note to all who wish to use this app to preserve/restore root after updating to 4.3 - it will not work!

See here: http://xdaforums.com/showpost.php?p=17117779&postcount=1
[Nexus 4 Original Android Development] Slymobi:
@ xplopr / Matthew

have you updated your radio !! when I was trying to go back to stock and unroot I was on .83 and got errors. I downgraded back to (edit) .48 and it all went smooth as usual.

make sure you are not using any newer bootloaders or radios.

MokeeOs Flying
[Nexus 4 Original Android Development] WugFresh:
Just to clarify - no need to refresh my webpage. The support for 4.3 should not require me to release a full toolkit update. v1.6.4 will be the version that supports it. I am currently working on modifying, uploading, and updating certain files to the web, and the toolkit automatically will gain support as long as you enable autoupdates in the toolkits options menu, or initiate an update check using CTRL+U in the toolkit. I will announce here when everything is done. Cheers.

{{ WugFresh }}
[Nexus 4 Original Android Development] xploPR:
It worked!!!!!!!! thanks alot :laugh::good:
[Nexus 4 Original Android Development] elderap:
You can use the file directly from google and install the rom 4.3 by the program rather than go back to 4.2.2 and wait via ota?
[Nexus 4 Original Android Development] Zeebz:
So I can't find a fix for this. Searched the thread and everything. So I downloaded the 4.3 update and went to flash it manually with the "I downloaded a factory image" option and it doesn't flash anything. The phone is unlocked. It just skips to the "Booting up your freshly flashed stock device..." screen. It skips the screen completely where it says it's flashing the system and all that.
[Nexus 4 Original Android Development] saeedscorpion:
same problem / knock knock anybody home?
[Nexus 4 Original Android Development] benryu:
I am on CM 10.1 with franco kernel. Used the toolkit to root the phone initially. How do i go about flashing 4.3 now?
[Nexus 4 Original Android Development] :
I had this same result but flashed successfully through fastboot. It was even easier to hit the included windows batch file (included in the Google image) after putting the files in the fastboot folder.
[Nexus 4 Original Android Development] -viper-:
If i update to 4.3 via googles image will i loose my sd card data?
[Nexus 4 Original Android Development] saeedscorpion:
yes u will lose all of it / backup what u want before flash
[Nexus 4 Original Android Development] KerryWood34:
Did you place the tgz image file in the folder called something like "place google factpry image here"? If not, then that might be why it didn't work.

Sent from my Nexus⁴ running stock 4.3
[Nexus 4 Original Android Development] -viper-:
Flash .84 radio via cwm and run script again...worked for me and i had the same issue as you and Zeebz

Sent from my Nexus⁴
[Nexus 4 Original Android Development] jcnbama:
So.. Is the toolkit updated? I woke up this morning ready to root!
[Nexus 4 Original Android Development] Alienfreak:
Not as far as I see it...

No 4.3 available inside the kit
[Nexus 4 Original Android Development] Zeebz:
Yeah, I just ended up using the other Nexus 4 toolkit and flashed it through there.
[Nexus 4 Original Android Development] Fall Guy:
I had this if you read the CMD window it will say Wrong Baseband or something similar. Wug said that you can use the force flash in the options or wait until he updates it. I used the force option after CAREFULLY checking that I had downloaded the correct image.

Worked fine but wipes everything.
[Nexus 4 Original Android Development] matthewgwilt:
I think there are root issues with 4.3 so I think Wug is just waiting to see any developments on that
[Nexus 4 Original Android Development] Alienfreak:
Whats wrong with root on 4.3? :)
[Nexus 4 Original Android Development] WugFresh:
Right now I have a working root solution, it just worked on my N7 with 4.3. I am just doing some more testing.

{{ WugFresh }}
[Nexus 4 Original Android Development] Alienfreak:
Yay Wug! :)
[Nexus 4 Original Android Development] MalindaD:
Good news :good: BTW is the root based on Chainfire's SuperSU v1.41 :confused: