I was thinking about this for a while and decided to put this idea out.
So the OTA zip in default is encrypted which I assume you can encrypt it with Condi's tool.
What if we decrypt it with desklunvr.exe, find SKUList in the META-INF folder within the zip, you can change the SKU values in that file to the matching ones you have on your device, this will not count up or anything so you will have to type in the SKUs in order which are all matched in the android versions which you can choose from, after that's done you can just decrypt it with Condi's tool but the problem is now that Sony uses a special signing tool with some type of signing type, I'm not sure if it is platform but you can try with ZipSigner.
What do you think about this idea?, post anything below that would be useful or something.
andyabc said:
I was thinking about this for a while and decided to put this idea out.
So the OTA zip in default is encrypted which I assume you can encrypt it with Condi's tool.
What if we decrypt it with desklunvr.exe, find SKUList in the META-INF folder within the zip, you can change the SKU values in that file to the matching ones you have on your device, this will not count up or anything so you will have to type in the SKUs in order which are all matched in the android versions which you can choose from, after that's done you can just decrypt it with Condi's tool but the problem is now that Sony uses a special signing tool with some type of signing type, I'm not sure if it is platform but you can try with ZipSigner.
What do you think about this idea?, post anything below that would be useful or something.
Click to expand...
Click to collapse
I tried it with increasing the incremental value of zip, you can sign it with test keys but you can't encrypt it again with desklunvr. And recovery fails.
Sent from my Sony Tablet S using xda app-developers app
smgdev said:
I tried it with increasing the incremental value of zip, you can sign it with test keys but you can't encrypt it again with desklunvr. And recovery fails.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
I mean that you can encrypt it with Condi's tool and then sign it.
By increasing the SKU value do you mean putting it to the same matching one that the current rom has?
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
I mean that you can encrypt it with Condi's tool and then sign it.
By increasing the SKU value do you mean putting it to the same matching one that the current rom has?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
When I try the flashing zip recovery says cant desklunvr package. And what is sku value? Is that incremental value?
Sent from my Sony Tablet S using xda app-developers app
smgdev said:
When I try the flashing zip recovery says cant desklunvr package. And what is sku value? Is that incremental value?
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Yes, it is pretty much that.
It is used in the OTA Updater and the Recovery if the OTA script specifies it.
The zip needs encrypting but the problem is that I found it is not on Condi's tool, we just need to be able to encrypt it again and then we are done.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Yes, it is pretty much that.
It is used in the OTA Updater and the Recovery if the OTA script specifies it.
The zip needs encrypting but the problem is that I found it is not on Condi's tool, we just need to be able to encrypt it again and then we are done.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
We should do reverse engineering on desklunvr, shouldn't we?
Sent from my Sony Tablet S using xda app-developers app
smgdev said:
We should do reverse engineering on desklunvr, shouldn't we?
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Yep, we need to see how it decrypts so we can do the opposite of what it does.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Yep, we need to see how it decrypts so we can do the opposite of what it does.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
I was thinking it for a while but I don't have enough knowledge of asm and cpp.
Sent from my Sony Tablet S using xda app-developers app
smgdev said:
I was thinking it for a while but I don't have enough knowledge of asm and cpp.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Mmmmm..., maybe Condi or the other users of the community could help out.
Sent from my Nexus 4 using Tapatalk 4
@<robin> compiled the desklunvr for windows, but i couldn't saw him for a while.
http://forum.xda-developers.com/showthread.php?t=2068261
Sent from my Sony Tablet S using xda app-developers app
andyabc said:
Mmmmm..., maybe Condi or the other users of the community could help out.
Click to expand...
Click to collapse
Not really wanting to rain on your parade, but Condi and several others have "been there, done that". Without Sony's signature key, signing an encrypted file that their tablets will install through System Recovery is a no-go. Condi was successful with tricking the early versions of System Recovery into installing his "signed" files, but Sony changed/updated System Recovery and disabled adb shell during recovery, which put an end to being able to trick System Recovery into installing files not signed by Sony.
Cat McGowan said:
Not really wanting to rain on your parade, but Condi and several others have "been there, done that". Without Sony's signature key, signing an encrypted file that their tablets will install through System Recovery is a no-go. Condi was successful with tricking the early versions of System Recovery into installing his "signed" files, but Sony changed/updated System Recovery and disabled adb shell during recovery, which put an end to being able to trick System Recovery into installing files not signed by Sony.
Click to expand...
Click to collapse
We can sign zips but we can't encrypt them. I think it is the problem. Or can we?
Sent from my Sony Tablet S using xda app-developers app
smgdev said:
@<robin> compiled the desklunvr for windows, but i couldn't saw him for a while.
http://forum.xda-developers.com/showthread.php?t=2068261
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Ok, let's see what he can do.
Sent from my Nexus 4 using Tapatalk 4
smgdev said:
We can sign zips but we can't encrypt them. I think it is the problem. Or can we?
Click to expand...
Click to collapse
Are you saying you have Sony's signature key?
Cat McGowan said:
Are you saying you have Sony's signature key?
Click to expand...
Click to collapse
What about test keys? If I'm right condi was signing the files with them.
http://forum.xda-developers.com/showthread.php?t=2086517
Sent from my Sony Tablet S using xda app-developers app
Cat McGowan said:
Not really wanting to rain on your parade, but Condi and several others have "been there, done that". Without Sony's signature key, signing an encrypted file that their tablets will install through System Recovery is a no-go. Condi was successful with tricking the early versions of System Recovery into installing his "signed" files, but Sony changed/updated System Recovery and disabled adb shell during recovery, which put an end to being able to trick System Recovery into installing files not signed by Sony.
Click to expand...
Click to collapse
There must be a way to find and exploit that security hole in the recovery or/and bootloader.
Sent from my Nexus 4 using Tapatalk 4
smgdev said:
What about test keys? If I'm right condi was signing the files with them.
http://forum.xda-developers.com/showthread.php?t=2086517
Click to expand...
Click to collapse
Again, Condi was tricking the early versions of System Recovery, via adb shell during recovery mode, into installing his "signed" file. The current versions of System Recovery block adb shell during recovery mode and therefore can no longer be tricked into installing a file not signed with Sony's signature key.
Cat McGowan said:
Are you saying you have Sony's signature key?
Click to expand...
Click to collapse
Most likely not, would you be referring to the DSA?
There are many Sony's such has Sony Entertainment, Sony Mobile and Sony VAIO.
Sony VAIO is working too hard on preventing exploits and unlocking.
Even Customer Support even tries to hide it under the sheets after a few times trying to convince them.
I kept on going on higher levels of support but they say that it is simple, saying that everyone except me are not that advanced and not so keen about it.
Finally got the answer why but it was just the skin of the answer which was the fact that it is closed source.
Sent from my Nexus 4 using Tapatalk 4
Cat McGowan said:
Again, Condi was tricking the early versions of System Recovery, via adb shell during recovery mode, into installing his "signed" file. The current versions of System Recovery block adb shell during recovery mode and therefore can no longer be tricked into installing a file not signed with Sony's signature key.
Click to expand...
Click to collapse
What can I say, totally right.
Sent from my Sony Tablet S using xda app-developers app
Wait, because we have root what if we get the recovery from the decrypted version of the OTA zip and flash it with Flashify?
Flashify also backups the recovery so what if someone backups the recovery which works with ADB and then we restore that recovery?
Sent from my Nexus 4 using Tapatalk 4
Related
I have a question, I need help repacking a system.img. This is what i have done, i unpacked it, removed unnessasary apps and added a different frame work, so now i want to repack back to a system.img file.But have had no luck. I do have ubuntu and windows so no matter what operating system i use.
frankinstine said:
I have a question, I need help repacking a system.img. This is what i have done, i unpacked it, removed unnessasary apps and added a different frame work, so now i want to repack back to a system.img file.But have had no luck. I do have ubuntu and windows so no matter what operating system i use.
Click to expand...
Click to collapse
If you intend on flashing it with a custom recovery, you could also zip the whole package and name it update.zip
There's an excellent guide over here.
The problem is, I used mkcramfs and when I unpacked it again it showed empty
Sent from my HTC HD2 using XDA App
frankinstine said:
The problem is, I used mkcramfs and when I unpacked it again it showed empty
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
I see. But what will the .img be used for?
Thijs96 said:
I see. But what will the .img be used for?
Click to expand...
Click to collapse
I want to edit and change some things in it. I'm doing this for the HD2. The new nand flash. So that's why a zip will not help me, I do know how to make a Rom into an zip. The nand flashs the boot.img and system.img
Sent from my HTC HD2 using XDA App
To be clear I have the system file ready I just need to reach it
Sent from my HTC HD2 using XDA App
frankinstine said:
To be clear I have the system file ready I just need to reach it
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Yes, yes, I know what you mean.
You've got to have /system in a folder, not compressed.
*You've got to be on linux!
Issue:
Code:
mkfs.yaffs2 yourdir yourimage
But you've got to find that command on Google, I didn't find it. Otherwise, flash it to your device and make a Nandroid backup.
Edit: I've found mkfs.yaffs2, but it's ARM only. That means you've got to do it on your device (Busybox/Terminal)
It's here.
Thijs96 said:
Yes, yes, I know what you mean.
You've got to have /system in a folder, not compressed.
*You've got to be on linux!
Issue:
Code:
mkfs.yaffs2 yourdir yourimage
But you've got to find that command on Google, I didn't find it. Otherwise, flash it to your device and make a Nandroid backup.
Edit: I've found mkfs.yaffs2, but it's ARM only. That means you've got to do it on your device (Busybox/Terminal)
It's here.
Click to expand...
Click to collapse
I'll give it a shot then
Sent from my HTC HD2 using XDA App
You can get yaffs2 tool for x86 Linux from here: http://jiggawatt.org/badc0de/android/mkfs.yaffs2.x86.tar.gz
I don't remember off hand what to search for as its been a while since I used it. I'll upload them when I get home if I still have them.
Sent from my HERO200 using XDA App
copy the folder to the sd on the phone, (eg /sdcard/myimg/ open a terminal on the phone, issue mkyaffs2image /sdcard/myimg/ /sdcard/system.img
bgcngm said:
You can get yaffs2 tool for x86 Linux from here: http://jiggawatt.org/badc0de/android/mkfs.yaffs2.x86.tar.gz
Click to expand...
Click to collapse
It's awesome! I've actually copied it into /bin/ on my computer, I'm using it an awful lot
pls help me!!!
how to upack and repack system.img ang boot.img...because i cant understand the guide..i think its missing something..pls help me
Is that for samsung devices?If yes,you can have a look at my sig
Sent from my GT-N7000 using xda app-developers app
Has anyone tried this yet via editing the build prop file? I want to give it a try but some phones don't play nice with changing the density.
Sent from my HTC6435LVW using xda premium
I tried. Wouldn't stick. So gave up lol. I assume that you could make a copy and upload via bootloader.
sent from my rooted DNA
That stinks. Oh well.
Sent from my HTC6435LVW using xda premium
chrisjm00 said:
That stinks. Oh well.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I got it to work. Copy the build.prop file to your computer and make your changes there. Then reboot your phone into recovery (TWRP is what I used), mount System (in TWRP), ADB push the edited file back onto your phone, and then use the TWRP file manager to apply CHMOD 755 onto the file. Then reboot and enjoy.
That last step (CHMOD) may not be necessary. I never tried leaving that step out to confirm one way or the other.
S121Guy said:
I tried. Wouldn't stick. So gave up lol. I assume that you could make a copy and upload via bootloader.
sent from my rooted DNA
Click to expand...
Click to collapse
You can't edit it while booted in android, you need to flash it.
Sent from my HTC6435LVW using xda app-developers app
Sometimes.. you see apps on xda.. that are required to be flashed.. and are in the form of zip files. Now how are these different from apk files with their regular installation? is it something to do with giving these apps you flash a deeper level permission? if so.. if your rooted can't you just give those apps those permissions after a normal install?
Usually making them flashable is just easier for some and if you were to extract the .apk from the zip and install it from sdcard it would work the same. Sometimes the app may require extra libs that are flashed at the same time as the app so they are bundled together as a zip. Or possibly it is being flashed to system for whatever reason and can't be done this way installed through os.
There are lots of varying reasons why it may be a .zip but you could also install it probably any way you'd like (including pushing with adb) if you want to know what's in the .zip just extract its contents, if you want to know what happens when you flash it look at the updater-script
Sent from my Nexus 4 using xda premium
Thank you!
demkantor said:
Usually making them flashable is just easier for some and if you were to extract the .apk from the zip and install it from sdcard it would work the same. Sometimes the app may require extra libs that are flashed at the same time as the app so they are bundled together as a zip. Or possibly it is being flashed to system for whatever reason and can't be done this way installed through os.
There are lots of varying reasons why it may be a .zip but you could also install it probably any way you'd like (including pushing with adb) if you want to know what's in the .zip just extract its contents, if you want to know what happens when you flash it look at the updater-script
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thank you..! I have one more question.. in some cases.. you are instructed to "copy apk's to system\app folder with a file manager with root permissions and then reboot" ... why this? does this produce the same effect as flashing it?
I guess it depends on the app, but it may only function properly as a system app, and yes it would be just as possible to flash it through recovery or push with adb to get the same effect
Sent from my Nexus 4 using xda premium
Thank you again!
demkantor said:
I guess it depends on the app, but it may only function properly as a system app, and yes it would be just as possible to flash it through recovery or push with adb to get the same effect
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
hey, thanx alot!
rjspark89 said:
hey, thanx alot!
Click to expand...
Click to collapse
And if it's an system app, or framework it's better to flash via Recovery
thanks!
superdragonpt said:
And if it's an system app, or framework it's better to flash via Recovery
Click to expand...
Click to collapse
thanks this is valuable info for a newbie..! any more imp tips related to my question is should know?
rjspark89 said:
thanks this is valuable info for a newbie..! any more imp tips related to my question is should know?
Click to expand...
Click to collapse
Yes
DON'T let you battery go all the way down.
This way it will lst longer (no Joke)
Update: Apparently the phone will connect via USB to my iMac but not my regular PC (while my brother's identical phone will connect to both), so I slapped Windows in a VM and now can use LGNPST. Makes sense, it does not.
My computer (using either Windows or Linux) won't recognize my phone anymore but I need to get it back to stock everything (including bootloader, recovery, etc). Can't use LGNPST or KDZ for the aforementioned reason. Stupidly, I failed to retain backups of my /sdcard/freegee directory (with aboot, sbl{1,2,3}, boot and recovery).
Anyone feel like making an archive of their /sdcard/freegee backup tree and uploading it somewhere?
Feel free to laugh, since I've been doing Android-related development since 2010.
I just made an efs backup with efsflashablemaker.zip.... Maybe that will help? I believe u can push the files thru adb if ur phone is unbootable.. Just don't ask me the command lines cuz I couldn't help lol
Sent from my LG-E970 using xda app-developers app
lsmrfydgaf said:
I just made an efs backup with efsflashablemaker.zip.... Maybe that will help? I believe u can push the files thru adb if ur phone is unbootable.. Just don't ask me the command lines cuz I couldn't help lol
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
No, I have EFS backups. I just need the backups made by FreeGee (the bootloader, sbl, etc).
Ahhh OK.. I have those also.. Can I email them to u??
Sent from my LG-E970 using xda app-developers app
lsmrfydgaf said:
Ahhh OK.. I have those also.. Can I email them to u??
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Perfect. Check your PM box.
Sent... Check ur inbox. Let me know if that's right
Sent from my LG-E970 using xda app-developers app
drewwalton19216801 said:
Update: Apparently the phone will connect via USB to my iMac but not my regular PC (while my brother's identical phone will connect to both), so I slapped Windows in a VM and now can use LGNPST. Makes sense, it does not.
My computer (using either Windows or Linux) won't recognize my phone anymore but I need to get it back to stock everything (including bootloader, recovery, etc). Can't use LGNPST or KDZ for the aforementioned reason. Stupidly, I failed to retain backups of my /sdcard/freegee directory (with aboot, sbl{1,2,3}, boot and recovery).
Anyone feel like making an archive of their /sdcard/freegee backup tree and uploading it somewhere?
Feel free to laugh, since I've been doing Android-related development since 2010.
Click to expand...
Click to collapse
Hi, if you've got what you were looking for can you please share with me also? Got into the same situation - lost freegee directry by mistake (I sitll have my EFS backup). Need to revert to stock but LG software does not see my phone. I have e975.
Many thanks in advance.
Does anybody from this thread still have access to the folder that was needed by the OP? I also need that folder, as I am having the same problem.
jimsal82 said:
Does anybody from this thread still have access to the folder that was needed by the OP? I also need that folder, as I am having the same problem.
Click to expand...
Click to collapse
just want to ask the same question if anyone can share their stock recovery backup file on freegee
as it seems that i cant make offline charging work with unlock bootloader using mako and when i try to re-lock using freegee this message pop up
"backup aboot" and says that no folder/file exist and when i checked at the location of the file theres no backup folder
hope anyone can share/help thanks
So I'm an avid rooter, and have rooted and messed around with loads of devices. (particularly, nexus) Well, I was rooting my nexus 9, about 3 weeks ago and everything went smooth. Today I noticed my device was reportedly no longer rooted, and I kept trying to reroot using WugFresh's NexusRootToolkit, Well I ****ed up.. It kept messing up so I decided I'd do a factory reset, and that did nothing. So I went into TWRP, and I did an advanced wipe and that other one you have to type 'yes' too.. and then I lost my OS, and even when I put it back to stock, even selecting "Bootlooped" absolutly nothing happens. Possibly need a new cable or something? Like all the commands worked, even while I was still trying to root, however nothing ever happened..
Edit: My device no longer has twrp on it. Also when I try to boot it up in any way it instantly goes to fastboot.. It doesn't even go to the boot screen
Flash the factory image with fastboot. And stay away from tool kits.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Flash the factory image with fastboot. And stay away from tool kits.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Could you expand more? I'm kind of a noob unless its tool kits..
godsobscure said:
Could you expand more? I'm kind of a noob unless its tool kits..
Click to expand...
Click to collapse
Download the factory image. Google nexus factory image. You'll download a .tgz file. Extract it using 7-zip. Inside you'll find a flash-all.bat file. Boot your device into the bootloader and connect it to your pc. Then done click on the flash-all. Backup your device first as it will wipe it. If the flash-all doesn't work then your going to have to flag the image files manually. That's a little more tedious
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Download the factory image. Google nexus factory image. You'll download a .tgz file. Extract it using 7-zip. Inside you'll find a flash-all.bat file. Boot your device into the bootloader and connect it to your pc. Then done click on the flash-all. Backup your device first as it will wipe it. If the flash-all doesn't work then your going to have to flag the image files manually. That's a little more tedious
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Well the cmd runs, and it does all its stuff and.. I get
finished. total time: 0.024s
< waiting for device >
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1814205204 bytes
error: update package missing system.img
Press any key to exit...
If you help me throough all of this id be more than happy to shoot ten dollars your way via paypal..
godsobscure said:
Well the cmd runs, and it does all its stuff and.. I get
finished. total time: 0.024s
< waiting for device >
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1814205204 bytes
error: update package missing system.img
Press any key to exit...
If you help me throough all of this id be more than happy to shoot ten dollars your way via paypal..
Click to expand...
Click to collapse
Don't need the money but I'll help you. The flash-all isn't working for the n9 so I thought you'd have a problem. First, Google 15 second adb install xda. Install that on your pc. Try not to use the dev host download. It's a bad site. It'll install fastboot and adb to your pc
Edit, inside the factory image you extracted is a zip file. Extract that too. You should find a number of image files in there. Recover.img, system.img, etc
Edit,edit this is for the nexus 5 but it's the exact same process. Follow method 2 but use the image files and file names in the factory image you downloaded. I'll be here to help when you need it. http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Don't need the money but I'll help you. The flash-all isn't working for the n9 so I thought you'd have a problem. First, Google 15 second adb install xda. Install that on your pc. Try not to use the dev host download. It's a bad site. It'll install fastboot and adb to your pc
Edit, inside the factory image you extracted is a zip file. Extract that too. You should find a number of image files in there. Recover.img, system.img, etc
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Did this. Any more steps?
godsobscure said:
Did this. Any more steps?
Click to expand...
Click to collapse
See this and my edit, edit
http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 9 using XDA Free mobile app
---------- Post added at 08:00 PM ---------- Previous post was at 07:55 PM ----------
Oh, one big difference is there is no userdata.img for the n9. Instead there is a vendor.img. where you see fastboot flash userdata userdata.img use fastboot flash vendor vendor.img
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
See this and my edit, edit
http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 9 using XDA Free mobile app
---------- Post added at 08:00 PM ---------- Previous post was at 07:55 PM ----------
Oh, one big difference is there is no userdata.img for the n9. Instead there is a vendor.img. where you see fastboot flash userdata userdata.img use fastboot flash vendor vendor.img
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I honestly cannot make any sense of a lot of that... I opened a cmd window in the folder that I extracted the zip, and I get that fastboot is not recognized as an internal or external command..
godsobscure said:
I honestly cannot make any sense of a lot of that... I opened a cmd window in the folder that I extracted the zip, and I get that fastboot is not recognized as an internal or external command..
Click to expand...
Click to collapse
Did you Google 15 second adb install xda and install that?
Edit, I see you're doing that now
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Did you Google 15 second adb install xda and install that?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I did, twice on accident. Could be an issue?
godsobscure said:
I did, twice on accident. Could be an issue?
Click to expand...
Click to collapse
No out shouldn't be an issue. Boot your device into the bootloader and then plug it into your pc. Open a command prompt and then type fastboot devices. What does it show? It should show your devices serial number
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
No out shouldn't be an issue. Boot your device into the bootloader and then plug it into your pc. Open a command prompt and then type fastboot devices. What does it show? It should show your devices serial number
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I get the same unrecognizable message.. Could I be opening a command prompt in the wrong place? (The folder the extracted everything to) ?
godsobscure said:
I get the same unrecognizable message.. Could I be opening a command prompt in the wrong place? (The folder the extracted everything to) ?
Click to expand...
Click to collapse
Are you on Windows 8 or 7? See if there is an adb folder on your machine with fastboot and adb in it
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Are you on Windows 8 or 7? See if there is an adb folder on your machine with fastboot and adb in it
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I am on windows 7.
I found one.
It also has 2 other files in it..
When I type fastboot devices in this one I get the serial number!
godsobscure said:
I am on windows 7.
I found one.
It also has 2 other files in it..
Click to expand...
Click to collapse
Ok open a command window in there, shift right click on an open area. Then with your device booted into the bootloader type fastboot devices
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Ok open a command window in there, shift right click on an open area. Then with your device booted into the bootloader type fastboot devices
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Did so and it worked. Now I have these commands from that other thread, but how do I change them to be personalized to the android file I have downloaded from googles website? something called volantis-lrx22c
godsobscure said:
Did so and it worked. Now I have these commands from that other thread, but how do I change them to be personalized to the android file I have downloaded from googles website? something called volantis-lrx22c
Click to expand...
Click to collapse
Good, we're getting some where. Move the image files you downloaded into that folder. The ltx22c file is the 5.0.1 android. You should have a bootloader and radio image file and then in the zip you extracted there should be a recovery, system, cache, boot, and vendor image files. I might have missed one as I'm going by memory but move all those image files into the same folder as fastboot and adb are in. For ease also rename the bootloader and radio files to just bootloader and radio.
Edit, now just to make sure everything is working boot into the bootloader and type fastboot devices. If you get the serial number then type the following commands
fastboot flash bootloader bootloader.img
fastboot -w
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
fastboot flash system system.img
System will take a long time. Then reboot and you should be good to go.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Good, we're getting some where. Move the image files you downloaded into that folder. The ltx22c file is the 5.0.1 android. You should have a bootloader and radio image file and then in the zip you extracted there should be a recovery, system, cache, boot, and vendor image files. I might have missed one as I'm going by memory but move all those image files into the same folder as fastboot and adb are in. For ease also rename the bootloader and radio files to just bootloader and radio.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I renamed the bootloader, however I see no 'Radio' file
(Just a reminder that I thank you very much for bearing with me)
godsobscure said:
I renamed the bootloader, however I see no 'Radio' file
(Just a reminder that I thank you very much for bearing with me)
Click to expand...
Click to collapse
Ignore the radio. There is no radio, it's a Wi-Fi only device, my bad
Sent from my Nexus 9 using XDA Free mobile app