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
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
Hi everyone,
I tried using a script which automated the install for the the custom recovery, but I started to get messages that it ran out of disk space (I can't link to the file due to my noob status). I probably should have come here first before using that script, but such as life..
I have no important data on the phone, if I lose it all that's ok.
It rebooted and my p500 waits with the following
"Fastboot mode started"
"udc_start()"
It also gives some info when USB is connected ie.
"- suspend -"
"- reset -"
Do I have a paperweight?
thanks and sorry for the newb post ..
edit: so I found this : http://forum.xda-developers.com/showthread.php?t=1003790 and
http://forum.xda-developers.com/showthread.php?t=875881
and have gotten it to the yellow emergency mode, not sure how to flash it from here though.
edit2: dling the stock firmware from http://forum.xda-developers.com/showthread.php?t=1073827
edit3: there's this as well.. http://forum.xda-developers.com/showthread.php?t=1088046 If I try this method, will it screw up again from too little free disk space?
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
thank you very much, I appreciate it haha
Your phone has booted in fastboot mode. Go to development section and read a tutorial how to recover from fastboot.
Sent from my LG-P500 using XDA Premium App
setTopbox said:
thank you very much, I appreciate it haha
Click to expand...
Click to collapse
Then did u unbricked now
Mahesh
go here....
http://forum.xda-developers.com/showthread.php?t=1088046
or here
http://forum.xda-developers.com/showthread.php?p=13813493
How to install Android SDK /ADB
http://lgoptimusonep500.blogspot.com/2011/01/how-to-install-android-sdk-adb.html
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Most honest post I've seen on the entire forum.
Sent from my Kyocera Echo.
mvgadagi said:
Then did u unbricked now
Mahesh
Click to expand...
Click to collapse
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
setTopbox said:
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
Click to expand...
Click to collapse
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
shhbz said:
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
Click to expand...
Click to collapse
Erm... reading all the posts about fastboot after using ROM Manager for this, I guess I would rather stick with the custom script using flash_image.
doktornotor said:
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
Click to expand...
Click to collapse
hmm, I'm not sure (when I dl'd the file I did compare the hash as per instructions). I used the following instructions:
manast.com/2011/05/07/how-to-install-custom-recovery-on-lg-optimus-one-p500
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
setTopbox said:
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
Click to expand...
Click to collapse
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
doktornotor said:
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
Click to expand...
Click to collapse
I'm getting permission denied when trying to use flash_image. Gingerbreak says the device is rooted, and the terminal does ask for superuser permission when i open it (su works in the terminal). I also tried chmod 755 flash_image but that didn't work either.
the permissions for flash_image are r-xr-x any thoughts ?
edit: apparently the sdcard is mounted with -noexecute ? So I tried copying flash_image to / but it's read only. Is there somewhere where I can execute this?
This rf.sh script seems most notorious, I too went into fastboot after that. Doktornotor's method worked (in fact I think he/she was the one who bailed me out back then as well).
If you got into fastboot, most probably you have a rooted phone.
To use flash_image you need to get the flash_image.sh on the root of your sd card. Search the forum for Amon-Ra custom recovery, and you shall find this file in that thread (it is required for Amon ra setup). Log in to your adb console, and use fastboot to push the new image in the recovery partition.
Unless your recovery.img or flash_image.sh is corrupted, it will work for sure.
Keep in mind, fastboot is a very powerfull tool, if you can access it, you're safe.
Cheers,
Alex
did you get out??
just flash stock firmware with kdz worked for me bro
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Dr.Alani said:
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
setTopbox said:
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
Click to expand...
Click to collapse
I do not see how you need to use adb.
Sent from my LG-P500 using XDA App
Hi GUys
I was using Ram Manager . I changed the Heap size to 128 Byte and Noow the phone is stuck on Boot Logo.
I'm rooted on Stock Firmware.
Please help, urgent
Did you backup?
Sent from my GT-I9300 using xda app-developers app
Try another kernel
Nandroid ftw!!
Sent from my GT-I9300 using xda premium
philicibine said:
Try another kernel
Nandroid ftw!!
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
No backup. I've not made any backup beacuse I'm stupid.
Please help; will Reset to factory setting help?
Boot into recovery, connect to your computer, open command prompt and type adb pull /system/build.prop
Edit the build.prop with notepad++ and fix the VM size, chances are that app set the VM size as 128 or 128mb instead of 128m which it should be.
Then once its fixed just adb push it back to /system/build.prop
Sent from my GT-I9300 using xda premium
nodstuff said:
Boot into recovery, connect to your computer, open command prompt and type adb pull /system/build.prop
Edit the build.prop with notepad++ and fix the VM size, chances are that app set the VM size as 128 or 128mb instead of 128m which it should be.
Then once its fixed just adb push it back to /system/build.prop
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I'm Really noob . Please tell how to :
Boot into Recovery?
How do I push adb ?
eggman89 said:
I'm Really noob . Please tell how to :
Boot into Recovery?
How do I push adb ?
Click to expand...
Click to collapse
Hold volume down, home button and power button together and it will boot into recovery.
I take it you don't have the android sdk on your computer? You need that to use adb.
If not then the easiest option is to factory reset, or maybe someone will make you a flashable zip that will replace your build.prop.
Sent from my GT-I9300 using xda premium
How do I :
"open command prompt and type adb pull /system/build.prop" .
Is it the windows Command Propmt?
If you have these questions you honestly shouldn't be messing with heap size.
Sent from my LG-E739 using Tapatalk 2
eggman89 said:
How do I :
"open command prompt and type adb pull /system/build.prop" .
Is it the windows Command Propmt?
Click to expand...
Click to collapse
Yes, that's it.
First type "adb devices" (no" ")
If you get a long serial number then adb is set up on your computer but I doubt it seeing as you are asking how to boot into recovery.
I take it you have a custom recovery?
If you give me a few mins I'll make you a flashable zip that will replace your build.prop, tell me what rom you are on
Sent from my GT-I9300 using xda premium
Lutin said:
If you have these questions you honestly shouldn't be messing with heap size.
Sent from my LG-E739 using Tapatalk 2
Click to expand...
Click to collapse
I know. I made a stupid mistake and I don't even know why I changed it?
How do I do factory reset?What will I lose?
nodstuff said:
Yes, that's it.
First type "adb devices" (no" ")
If you get a long serial number then adb is set up on your computer but I doubt it seeing as you are asking how to boot into recovery.
I take it you have a custom recovery?
If you give me a few mins I'll make you a flashable zip that will replace your build.prop, tell me what rom you are on
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hi
I'm on stock LFB (Indian Version).
I am on CWM-based Recovery c5.5.0.4
nodstuff said:
Yes, that's it.
First type "adb devices" (no" ")
If you get a long serial number then adb is set up on your computer but I doubt it seeing as you are asking how to boot into recovery.
Click to expand...
Click to collapse
I get adb is not a recognized internal or external command.
I also deleted dalvik cache; but it didn't help
eggman89 said:
I get adb is not a recognized internal or external command.
I also deleted dalvik cache; but it didn't help
Click to expand...
Click to collapse
Get me a build.prop from that firmware and I'll make you a zip you can flash in cwm.
You'll find it in the system folder.
Sent from my GT-I9300 using xda premium
nodstuff said:
Get me a build.prop from that firmware and I'll make you a zip you can flash in cwm.
You'll find it in the system folder.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I'm unable to access filesystem
Let me ask someone?
eggman89 said:
I'm unable to access filesystem
Let me ask someone?
Click to expand...
Click to collapse
Download another one from samfirmware.com
I'm not downloading it for you.
Sent from my GT-I9300 using xda premium
nodstuff said:
Download another one from samfirmware.com
I'm not downloading it for you.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Yes. I'm already downloading it. It's about 800mb and it'll take about 36minutes more.
Once I get that I'll provide it to you.
Thanks a lot for the help
But how will I push the build.prop ?
nodstuff said:
Download another one from samfirmware.com
I'm not downloading it for you.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
he needs adb to push the zip to his mobile first.
bala_gamer said:
he needs adb to push the zip to his mobile first.
Click to expand...
Click to collapse
How do I get adb?
eggman89 said:
Yes. I'm already downloading it. It's about 800mb and it'll take about 36minutes more.
Once I get that I'll provide it to you.
Thanks a lot for the help
But how will I push the build.prop ?
Click to expand...
Click to collapse
man if you are downloading the full rom, better flash it via odin . job done. almost all the stock roms are non wipe
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
Hi so I just got an HTC one x+ and unlocked and it and rooted it. I flashbooted a boot.img from a custom and realized I forgot to put the custom ROM itself on the phone. My phone now can't use WiFi or show up on the computer unless in fastboot. I really need help please let me know what to do. Thanks!!!
Sent from my SGH-T999 using xda app-developers app
brianisawesome1 said:
Hi so I just got an HTC one x+ and unlocked and it and rooted it. I flashbooted a boot.img from a custom and realized I forgot to put the custom ROM itself on the phone. My phone now can't use WiFi or show up on the computer unless in fastboot. I really need help please let me know what to do. Thanks!!!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Within a custom recovery, ex. TWRP. Go into advance and select adb sideload. Use adb to sideload the Rom using the command adb sideload Rom.zip to your phone
Sent from my HTC One X+ using Tapatalk
nheolon thous
I have a similar problem here.
I wanted to try this"adb sideload" but I can get ti to work because when I use "adb devices". I get nothing listed.
can I get an extra help please?
Thank you
XAlexander_AlexanderX said:
Within a custom recovery, ex. TWRP. Go into advance and select adb sideload. Use adb to sideload the Rom using the command adb sideload Rom.zip to your phone
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
I got cannot read ROM.zip anything more specific I didn't do
Sent from my SGH-T999 using xda app-developers app
brianisawesome1 said:
I got cannot read ROM.zip anything more specific I didn't do
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Use the name of the Rom. For example. If the Rom name is cm10. You type adb sideload cm10.zip
Sent from my HTC One X+ using Tapatalk
XAlexander_AlexanderX said:
Use the name of the Rom. For example. If the Rom name is cm10. You type adb sideload cm10.zip
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
Ya I did that and still sane problem
Sent from my SGH-T999 using xda app-developers app
brianisawesome1 said:
Ya I did that and still sane problem
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Is the Rom in the same folder as adb (if your using windows )?
Sent from my HTC One X+ using Tapatalk
XAlexander_AlexanderX said:
Is the Rom in the same folder as adb (if your using windows )?
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
Ill tell u step by step what I do:
1. Recovery to adb sideload on phone
2. Move ROM to c:\android where fastboot and adb are located
3. Run cmd
4. cd c:\android
5. Adb sideload "ROM name"
6. I get the error
Sent from my SGH-T999 using xda app-developers app
brianisawesome1 said:
Ill tell u step by step what I do:
1. Recovery to adb sideload on phone
2. Move ROM to c:\android where fastboot and adb are located
3. Run cmd
4. cd c:\android
5. Adb sideload "ROM name"
6. I get the error
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Adb is located in platform tools. Put Rom there and CD cmd there and run the command.
Sent from my HTC One X+ using Tapatalk
brianisawesome1 said:
Ill tell u step by step what I do:
1. Recovery to adb sideload on phone
2. Move ROM to c:\android where fastboot and adb are located
3. Run cmd
4. cd c:\android
5. Adb sideload "ROM name"
6. I get the error
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
open platform-tools(or the folder where adb is found) shift + right click on any empty space, you will find "open command prompt here" press on it, then type ADB devices, if it is read, simply type " adb sideload " then drag and drop the rom zip into the command prompt. it will automatically write its location and prevent the spelling mistakes.
IF: ADB devices can't read your device try the following:
1-Try another usb port, if you tried 2.0 then try 3.0 and vice versa.
2- If you are on windows vista or above, open start menu and search for cmd, right click on it and run as administrator, however you will have to cd to the platform tools location, " cd C:\Android\sdk\platform-tools " then you type in adb devices should read your device fine now. however running cmd as admin prevents the drag and drop technique (atleast here on windows 8.1 it does) so you have to type in the location of your rom and rom name correctly, and dont forget the .zip
Ghand0ur said:
open platform-tools(or the folder where adb is found) shift + right click on any empty space, you will find "open command prompt here" press on it, then type ADB devices, if it is read, simply type " adb sideload " then drag and drop the rom zip into the command prompt. it will automatically write its location and prevent the spelling mistakes.
IF: ADB devices can't read your device try the following:
1-Try another usb port, if you tried 2.0 then try 3.0 and vice versa.
2- If you are on windows vista or above, open start menu and search for cmd, right click on it and run as administrator, however you will have to cd to the platform tools location, " cd C:\Android\sdk\platform-tools " then you type in adb devices should read your device fine now. however running cmd as admin prevents the drag and drop technique (atleast here on windows 8.1 it does) so you have to type in the location of your rom and rom name correctly, and dont forget the .zip
Click to expand...
Click to collapse
Ok great thanks it worked! Question: can u flash a custom kernel that's not in the same and ROM? I got viper ROM and everything is slow and I'm trying to make it fast
Sent from my SGH-T999 using xda app-developers app
brianisawesome1 said:
Ok great thanks it worked! Question: can u flash a custom kernel that's not in the same and ROM? I got viper ROM and everything is slow and I'm trying to make it fast
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Since we have the stupid s-on, your choice of custom kernels is very limited and they make almost no difference, if you are on viper rom which is sense based, you can use the stock kernel (I THINK<<< Not sure) or insertcoin kernel's , but no they don't make any difference as far as i know. Try and see