What Is This?
I have repacked and mirrored Aorth's builds of ClockWorkMod 6.0.1.9 for various versions of the GT Plus in Odin format. Aorth has posted about these in his CM10 nightly thread here, but the links are sometimes hard to find.
The process of "converting" them is pretty easy if you have access to Linux, you run the following commands:
Code:
mv t869_clockworkmod_6.0.1.2.img recovery.img
tar -H ustar -c recovery.img > recovery.tar
md5sum -t recovery.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
Odin Links
-i815 (Odin) (Heimdall) (Heimdall-Goo.im)
-p6800 (Odin) (Heimdall) (Heimdall-Goo.im)
-p6810 (Odin) (Heimdall) (Heimdall-Goo.im)
-p6200 (Odin) (Heimdall) (Heimdall-Goo.im)
-p6210 (Odin) (Heimdall) (Heimdall-Goo.im)
-t869 (Odin) (Heimdall) (Heimdall-Goo.im)
Odin 1.85
Let me know if any of the links are incorrect.
As I said in my previous post like this, if you find this useful, consider donating to / thanking Aorth, or donating to Android File Host. You can also send me Thanks if you want, of course ;P
Working fine with my p6200 with odin mobile (using the odin file)
Thx soo much!
Enviado desde mi GT-P6200 usando Tapatalk 2
Euphoria_ said:
Working fine with my p6200 with odin mobile (using the odin file)
Thx soo much!
Enviado desde mi GT-P6200 usando Tapatalk 2
Click to expand...
Click to collapse
Oh yeah, I forgot about Odin Mobile. Glad to hear it works
Working fine..installed in a few second..via mobile odin..
Sent from my GT-P6200 using xda premium
Works OK. Flashed thru mobile Odin also. But when I try to reboot from recovery it says root might be lost and ask me fix su/bin? I select no and it reboots fine and root works fine
Edit: allowed recovery to fix and error message goes away. Works perfect now
Sent from my GT-P6200 using Tapatalk 2
attempted with Odin 1.85 on my P6200l. Message received was " MD5 hash value is invalid".
After multiple unsuccessful tries with Heimdall on both Windows 7 and Linux machines, I'm beginning t think maybe it's me... although I had no probs with my SG2..
Any advice would be hugely appreciated.
subdriver57 said:
attempted with Odin 1.85 on my P6200l. Message received was " MD5 hash value is invalid".
After multiple unsuccessful tries with Heimdall on both Windows 7 and Linux machines, I'm beginning t think maybe it's me... although I had no probs with my SG2..
Any advice would be hugely appreciated.
Click to expand...
Click to collapse
MD5 being invalid means the file has somehow become corrupted. I would download it from Aorth and test that via Heimdall next.
The p6200 odin link doesn't seem to work. Will you please check the links?
Sent from my GT-N7100 using xda premium
wtfshouldidonow said:
The p6200 odin link doesn't seem to work. Will you please check the links?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
It looks like AndroidFileHost is having some kind of problem.
In my file management interface, the entire directory I created for the CWM stuff is just straight up gone, and all the links I posted go nowhere.
However, they have a notice up:
"SYSTEM NOTICE: Aware that some of the uploads are not showing up on site. Fixing this now. SQL did not merge completely"
Ostensibly the files/directories are still there, but the system doesn't currently display them since the database that runs the show is broken. That notice is all they posted, no ETA on a fix
If it hasn't been put back online later today I can re-build the needed files as needed, just takes some effort. I can host them on one of the web hosts I actually run if anyone really needs them.
DivinityCycle said:
It looks like AndroidFileHost is having some kind of problem.
In my file management interface, the entire directory I created for the CWM stuff is just straight up gone, and all the links I posted go nowhere.
However, they have a notice up:
"SYSTEM NOTICE: Aware that some of the uploads are not showing up on site. Fixing this now. SQL did not merge completely"
Ostensibly the files/directories are still there, but the system doesn't currently display them since the database that runs the show is broken. That notice is all they posted, no ETA on a fix
If it hasn't been put back online later today I can re-build the needed files as needed, just takes some effort. I can host them on one of the web hosts I actually run if anyone really needs them.
Click to expand...
Click to collapse
I am also desperately looking for the Odin flash files as heimdall does not seem to be responding to my commands.
heimdall flash p6200-clockworkmod-6.0.1.9 was a command that once worked for me, but now that command is just giving me a load of different options of which iv read little about. if anyone could upload these files that would be great
Awology said:
I am also desperately looking for the Odin flash files as heimdall does not seem to be responding to my commands.
heimdall flash p6200-clockworkmod-6.0.1.9 was a command that once worked for me, but now that command is just giving me a load of different options of which iv read little about. if anyone could upload these files that would be great
Click to expand...
Click to collapse
All the files are back online at Android File Host. As with my link in OP
http://www.androidfilehost.com/?fid=9390169635556426744
Just click the big green down arrow
MD5 is invalid ~ oh no does this mean these files have become corrupt. ?
Awology said:
MD5 is invalid ~ oh no does this mean these files have become corrupt. ?
Click to expand...
Click to collapse
Yeah usually means something along the way broke em. In order to convert them, I had to download them to my desktop, upload them to my Linux server, convert them, download them back to my desktop, and then upload them to Android File Host. Its possible that the source files are bad, or that they became corrupted somewhere during that process, or somewhere during your download.
If you have access to a Linux box, its really easy to "convert" the file to work with Odin. That'd be your best bet, re-download them from the original builds Aorth made and uploaded to goo.im, then convert them over, then flash.
DivinityCycle said:
Yeah usually means something along the way broke em. In order to convert them, I had to download them to my desktop, upload them to my Linux server, convert them, download them back to my desktop, and then upload them to Android File Host. Its possible that the source files are bad, or that they became corrupted somewhere during that process, or somewhere during your download.
If you have access to a Linux box, its really easy to "convert" the file to work with Odin. That'd be your best bet, re-download them from the original builds Aorth made and uploaded to goo.im, then convert them over, then flash.
Click to expand...
Click to collapse
Unfortunately iv only got access to windows 7 64bit, iv had it installed via hemidall before and it was pretty easy, so im sure im making a real novice mistake.
This is my screenshot of command prompt, do or anyone else have any suggestions on where i might be going wrong.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Awology said:
Unfortunately iv only got access to windows 7 64bit, iv had it installed via hemidall before and it was pretty easy, so im sure im making a real novice mistake.
Yeah, I believe the correct syntax is heimdall flash --recovery (filename here).
So like if you're in the same directory as the file and the filename is somefile.img, the command would be heimdall flash --recovery somefile.img.
I always got this far but then couldn't get it to work under Windows due to driver issues.
Click to expand...
Click to collapse
DivinityCycle said:
Awology said:
Unfortunately iv only got access to windows 7 64bit, iv had it installed via hemidall before and it was pretty easy, so im sure im making a real novice mistake.
Yeah, I believe the correct syntax is heimdall flash --recovery (filename here).
So like if you're in the same directory as the file and the filename is somefile.img, the command would be heimdall flash --recovery somefile.img.
I always got this far but then couldn't get it to work under Windows due to driver issues.
Click to expand...
Click to collapse
Thanks your day saver. i knew i was doing some thing stupid with the commands.
that worked like a charm
Click to expand...
Click to collapse
Here is a link to the Odin package courtesy of "MaxiTheMan", iv not checked it myself but apparently it works..
https://www.box.com/s/9ej7dbekuwcl4w6yurkw
Awology said:
Here is a link to the Odin package courtesy of "MaxiTheMan", iv not checked it myself but apparently it works..
https://www.box.com/s/9ej7dbekuwcl4w6yurkw
Click to expand...
Click to collapse
Hi, I have tried with both the p6800 and p6200 versions. Both give the MD5 invalid message.
Edit 8.30pm : Installed Mobile Odin and flashed ..skipped verifying MD5 ... worked OK. Have since done a system backup and all OK
gazjglusk said:
Hi, I have tried with both the p6800 and p6200 versions. Both give the MD5 invalid message.
Edit 8.30pm : Installed Mobile Odin and flashed ..skipped verifying MD5 ... worked OK. Have since done a system backup and all OK
Click to expand...
Click to collapse
That is one of those "seems like that shouldn't work" type situations. I'm not sure why it'd flash and be OK if the MD5 failed.
DivinityCycle said:
That is one of those "seems like that shouldn't work" type situations. I'm not sure why it'd flash and be OK if the MD5 failed.
Click to expand...
Click to collapse
Yes it's got me tricked. I tried everything about 10 times each and the only way was via Mobile Odin.
Anyway just did a full restore and again all is fine.:good:
Related
We have 3 major works here... So I gonna to make it seperated
-1st post is HOW TO EXTRACT kernel.img (boot.img)
-2nd post is HOW TO CONVERT PICTURE FILE to BOOT.RLE
-3rd post is HOW TO REPACK THE KERNEL PAKAGE into boot.img
Requiredment
-Window machine
-installed cygwin
-the full boot.img/kernel (some kernel won't work because there is no full pakage/ i mean we can't)
-bootimg.zip (tool for UNPACK and REPACK kernel)
-boot_screen_logo_creation_package.rar
Thank and Credit
i- Credit to DooMLoRD Recognized Developer over most of XPERIA devices for his own tool and tutor that I learned before
ii- Credit to jimbo77 Senior Member for his tutorial that I used and learned and tool for unpack and repack
ii- Don't forget to give them a thanks meter
=============================================================================
Here we go
1-This section I will show u how to unpack and repack the boot.img
just see from original thread by jimbo77 from here and download the UNPACK and REPACK tool by him HERE
this is a fast guide from me:-
1-extract the bootimg-tools.zip into new folder (name it 'boot' folder)
2-move it into cygwin directory (cygwin/boot)
3- move your fav kernel into same directory
4-run cygwin.bat
cd /boot
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5-Now, unpack your boot.img by running the following command:
./extractboot boot.img
Click to expand...
Click to collapse
If your output looks like this, then the extraction has worked correctly! Note that the Command Line string has also been read from the source file, this will be used later when you go to re-pack your file.
Your script folder should now look like this:
boot.img-kernel is the compiled kernel blob that was inside the source boot.img, if you want to replace the kernel with another compiled kernel image, you can replace this file with another one (but leave the file name the same)
boot.img-ramdisk.gz is the gzipped ramdisk image which has been split from the boot.img, you should leave this file alone.
The “out” folder contains the EXTRACTED ramdisk, and this is where you should make your changes to the ramdisk.
Important Note!
Remember, when editing files in the ramdisk through Windows, such as init.rc, Windows notepad will not format the files correctly, making them almost impossible to read, wheras Wordpad will LOOK like it is formatting the files correctly, if you save one of these files from the Wordpad application it will BREAK the file and it will no longer be able to be read correctly by Android. To edit these files you MUST use an editor such as Notepad++ which you can download for free.
AGAIN...
Special thanks/credit to jimbo77 for his excellent guide
So.. NEXT step to change a kernel logo is here
Requiredment
1-a picture what are u like to look into the 1st boot screen (kernel logo) (make sure it size/resolution same your device resolution)
2-boot_screen_logo_creation_package.rar
3-some infos and knowledges here
4-window machine like i explained on 1st post
My quick guide
-extract the tool.rar
-move extracted files into new folder (name it 'rle' folder without quote)
-move into cygwin folder (to make it easy to follow my simple guide)
-copy your own logo.png (a picture u want to use on a kernel) into same rle folder
(for 4 steps above it shold look like tis)
-now launch cygwin.bat
cd /rle
Click to expand...
Click to collapse
./convert_image_to_rle.bat logo.png
Click to expand...
Click to collapse
Ah...my mistake..don't forget to move/copy/replace new logo.rle into
C/cygwin/boot/out/ramdisk/here
if you done good...follow next step on next post (to repack your moded kernel)
Last step before you flash a new look kernel (boot.img) is
Repack your moded kernel
./packboot
Click to expand...
Click to collapse
One thing to note that people may mention in other guides, is that when packing boot.img files, you will usually have to declare a base address, and a command line to the packaging tool. This set of scripts reads the existing command line and base address from the boot.img file you originally provided at the time of repacking, so always make sure you leave your original source boot.img file in the folder and do not re-name it after extraction, your newly created boot.img file will be named boot_new.img and will NOT overwrite the original.
Done! If your screen looks like the image above, then you should now have a freshly created boot_new.img file, ready to be flashed to Android for testing, you can now go ahead and flash it through FASTBOOT one thing I'll recommend though is to first do
I need this for extra (extra thanks..)
(may U?)
does this work on hboot 1.14?
byliu88 said:
does this work on hboot 1.14?
Click to expand...
Click to collapse
double that?
Will this remove the HTC red warning at the very bottom??
Sent from my HTC One S using Tapatalk 2
Elloco305 said:
Will this remove the HTC red warning at the very bottom??
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Nothing removes that except SOFF.
Sent from my HTC One S running ViperOneS!
invasion2 said:
Nothing removes that except SOFF.
Sent from my HTC One S running ViperOneS!
Click to expand...
Click to collapse
Don't scream at me Bro!
I figured that much though just thought I'd ask. Lol
Sent from my HTC One S using Tapatalk 2
Hmm think I might try this tomorrow to see if it works on 1.14.
---------- Post added at 03:07 AM ---------- Previous post was at 02:38 AM ----------
Changed my mind lol but unpacking the boot.img is not working.
I fixed that but all I get is a bootloop and nothing has changed. Here the boot.img I did, don't if anybody wants to try it on a lower Hboot or can see if I did it wrong. Boot.img is from aokp_ville_experimental_Nov-01-12.
Darknites said:
I fixed that but all I get is a bootloop and nothing has changed. Here the boot.img I did, don't if anybody wants to try it on a lower Hboot or can see if I did it wrong. Boot.img is from aokp_ville_experimental_Nov-01-12.
Click to expand...
Click to collapse
Darn... no luck for hboot 1.14 I see. Updating was such a bad decision.
byliu88 said:
Darn... no luck for hboot 1.14 I see. Updating was such a bad decision.
Click to expand...
Click to collapse
nelikp is have a go doing it because he says the image I did didn't convert right.
I have a Nandroid of the axiom build (an awesome sense ROM popular here a few months ago before the devs fell under the SG3 spell) which I had been using on my phone until about a week ago, and for whatever reason this ROM, which has custom boot animation, has a splash screen without the red overlay text. I don't know why.. But if anyone wants to look at it, let me know. Because a pristine splash screen without S-Off is possible. I would think you could look at the partitions for the splash and maybe figure out if there is something different.
Just thought I would offer. I am trying to get up to speed on building ROMs, but am not quite there yet, otherwise I would examine it.
Sent from my HTC One S using xda premium
syntropic said:
I have a Nandroid of the axiom build (an awesome sense ROM popular here a few months ago before the devs fell under the SG3 spell) which I had been using on my phone until about a week ago, and for whatever reason this ROM, which has custom boot animation, has a splash screen without the red overlay text. I don't know why.. But if anyone wants to look at it, let me know. Because a pristine splash screen without S-Off is possible. I would think you could look at the partitions for the splash and maybe figure out if there is something different.
Just thought I would offer. I am trying to get up to speed on building ROMs, but am not quite there yet, otherwise I would examine it.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
As far as I know we can't flash those partitions without the need of S-OFF or using adb to push those partitions manually.
So it should be not possible flashing those from recovery, same reason we can't flash the kernel in it.
Gesendet von meinem HTC One S
v3n3 said:
As far as I know we can't flash those partitions without the need of S-OFF or using adb to push those partitions manually.
So it should be not possible flashing those from recovery, same reason we can't flash the kernel in it.
Gesendet von meinem HTC One S
Click to expand...
Click to collapse
There is another way here but need to be 1.09 lower Hboot for it to work. I think this boot.img mod just dont work for us and nelikp never got back to me.
Darknites said:
I fixed that but all I get is a bootloop and nothing has changed. Here the boot.img I did, don't if anybody wants to try it on a lower Hboot or can see if I did it wrong. Boot.img is from aokp_ville_experimental_Nov-01-12.
Click to expand...
Click to collapse
How did you fixed that error?
alexeius said:
How did you fixed that error?
Click to expand...
Click to collapse
When you install Cygwin you be asked if you like to install plug-ins or something like that, when it does that search for cpio and select to install all and do the same for perl.
Darknites said:
I fixed that but all I get is a bootloop and nothing has changed. Here the boot.img I did, don't if anybody wants to try it on a lower Hboot or can see if I did it wrong. Boot.img is from aokp_ville_experimental_Nov-01-12.
Click to expand...
Click to collapse
I had the same problems. I followed your guide step by step and encountered boot loop without the change. Im on Hboot 1.09.0000. I realy wanted to get this image as my kernel logo -=*( woah is me...
essentialmindz said:
I had the same problems. I followed your guide step by step and encountered boot loop without the change. Im on Hboot 1.09.0000. I realy wanted to get this image as my kernel logo -=*( woah is me...
Click to expand...
Click to collapse
I got same thing so give up. Boot you in luck with that Hboot you can use this thread here to do what you want to.
Pre Rooted Stock ROM
Here is complete stock Pre rooted ROM
( MUST READ THIS before flashing DMF2/ME6 or any newer )
July13
N7100XXDMG1_N7100ODDDMG1_N7100DDDMG1- Deodexed - India - Download - Detail here
N7100XXDMG1_N7100ODDDMG1_N7100DDDMG1- Odexed - India - Download
June13
N7100XXDMF2_N7100OLBDMD2_XME - Malaysia - Download - - - Mirror
SuperSu updated to latest 1.34
Package have addition mod zip file which is optional, If you want to install that mod, instead using packed one use this
April 2013
N7100XXDMC3_N7100ODDDMD1_N7100DDDLK6 (INU) -India - Download
March 2013
N7100XXDMC3_N7100OXXDMC2_N7100XXDLK7 (XEO) - Poland - Download
Installation Instruction
- Download ROM and extract to ***.tar.md5 (unzip tool)
- Make sure you have installed Kies OR Samsung USB driver
- Open up the S/W Installation Program by executing the Odin3 v3.04.exe
1. Enable the check mark by click on the following options(default Option)
- Auto Reboot, and F. Reset Time
- Check PDA, and point to ROM file you have extracted
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
File name shown in above image is for demo purpose, you have to select according ROM you have download
2. Now switch off device and Enter into Download Mode
- Enter into Download Mode by pressing Volume Down button, Home Key and
Power Button simultaneously. And then, press Volume UP button in Warning Page to enter the Download Mode.
3. Connect the device to PC via Data Cable.
Make sure that the one of communication port [ID:COM] box is highlighted in
light blue. The device is now connected with the PC and ready to download the
binary file into the device.
4. Start downloading binary file into the device by clicking Start Button on the screen.
the green colored "PASS!" sign will appear on the upper-left box if the binary file has been successfully downloaded into the device.
5. Disconnect the device from the Data cable.
6. Once the device boots up, you can check the version of the binary file or name
by pressing the following code in sequence;
*#1234#
After flashing your device will have SuperSU in application drawer. If you want to unroot it, open SuperSu - settings - Full unroot.
First thing I do recommend after rooting device is
EFS Backup
Why so?
EFS folder contains some important and some basic info related to our device identity like Wi-Fi address, Bluetooth MAC address and the very main IMEI address (nv_data.bin).
Now if this EFS partition accidently corrupted then your phone’s IMEI no. will erased and you can not make voice call further. This kind of damage is often not accepted by the service center of your respected handset’s company.
Here your backup can only be savior for you.
-This is pure samsung stock ROM as it is + Root
-Non wipe
-Won't raise flash counter.
- Non Hotfile link
Again to make it clear, there is no any additional changes except pushing superSU (busybox added to April 2013 and onward), so there won't be have any difference from stock ROM, but you will not need to Root / reset counter. Just note that, flashing prerooted ROM doesn't reset counter, If your flash counter already raised flashing this ROM doesn't reset it, but you can use triangle away to reset counter after flashing this ROM. later you can uninstall triangle away.
Rooting is not difficult but still many users scare from it, this will come handy to them.
There is no plan to make every release Pre rooted, when there will be major update and myself update device that time will make that ROM pre rooted.
There is already thread in dev section by as i9000, which also have deodexed version and many other ROMs with multi CSC and regularly updating too. This thread will update only ROMs which i am using, as well basic aim is to write tutorial abiut how to make pre rooted ROM.
There are two other MB6 and DMB2 India are ready but really finding difficulty to upload. still i will try my best to upload it.
- Password to unzip - when there is any password to unzip, file name itself will have it.
- difference in file size from sammobile stock rom size is just due to different compression method, once you extract it will be same.
How to make prerooted stock ROM.
Requirements :
Ubuntu and login as Root user.
Ext4_utils - extract to home directory
Root files (su and Superuser.apk) - copy to home directory
busybox - copy to home directory (optional)
Procedure :
1.Download ROM you need to preroot and rename stock.tar.md5 (just to make command line input easy)
2.Extract ROM
Code:
tar xvf stock.tar.md5
3.convert system.img to ext4 so we can mount it.
Code:
./simg2img system.img newsys.img
4.delete system.img
Code:
rm -f system.img
5.Create temp folder and mount it
Code:
mkdir temp
mount -o loop newsys.img temp
6.Push root and busybox file to system and change permission
Code:
cp su temp/xbin/su
chmod 06755 temp/xbin/su
Code:
cp Superuser.apk temp/app/Superuser.apk
chmod 0644 temp/app/Superuser.apk
Code:
cp busybox temp/xbin/busybox
chmod 04755 temp/xbin/busybox
7.Conver newsys img to samsung system.img format
Code:
./mkuserimg.sh -s temp system.img ext4 tempdir 2048M
8.unmount and delete temp folder
Code:
umount temp
rmdir temp
9.create odin flashable tar file (here file names depends on files you have got by extracting ROM)
Code:
tar cvf prerooted.tar boot.img cache.img hidden.img modem.bin recovery.img sboot.bin system.img tz.img
10. add md5 checksum
Code:
md5sum -t prerooted.tar >> prerooted.tar
mv prerooted.tar prerooted.tar.md5
Now Flash prerooted.tar.md5 with odin.
Delete following files from home directory to make it clean
stock.tar.md5
newsys.img
and all files extracted while unpacking tar in step 1.
Credits :
Chainfire for his SuperSu
Phil3759
Credits to following user for referring their works on different forum
jazzor, rizdroid, das7982, faria
Where is it sir?
Sent from my GT-N7100 using xda premium
As I have said
What's your opinion?
Do I update rom
Or
You want guide, how to make it yourself.
Sent from my GT-N7100 using xda premium
My choice is 2
Please provide complete guide
Sent from my GT-N7100 using Tapatalk 2
Make a guide. That way, people learn more.
Sent from my GT-N7100 using xda premium
i thought it was just about placing su in xbin and supersu.apk in app -.-
yeah unpacking repacking and all can be a damn headache
No offense, leave the dev part to those who deserve this denomination and stick with the Guide Guru image that you have built for yourself and for which you get lots of credits and praise. I'd choose option 2.
Thanks for your excellent work of guiding noobs like me and troubleshoot their problems.
P_
))))))
That's the same there! And for a long time!
http://forum.xda-developers.com/showpost.php?p=32260125&postcount=1
:laugh:
2 with noobie detailed please
Sent from my GT-N7100 using xda app-developers app
UBUNTU needed for this)
alexyuh said:
UBUNTU needed for this)
Click to expand...
Click to collapse
+1
Sent from my GT-N7100 using xda app-developers app
alexyuh said:
UBUNTU needed for this)
Click to expand...
Click to collapse
Not with cygwin.
Sent from my GT-N7100 using xda premium
UtkarshGupta said:
Not with cygwin.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
There are some limitations in cygwin. Ubuntu is best for this.
Sent from my GT-N7100 using xda premium
Please post guide so that we'd learn ourselves
Sent from my GT-N7100 using xda premium
---------- Post added at 09:22 PM ---------- Previous post was at 09:15 PM ----------
sharjackmission said:
2 with noobie detailed please
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
+1
Sent from my GT-N7100 using xda premium
Ok,
So will make complete Guide with link to all needed utilities. But may take some time.
Meanwhile try to upload pre rooted rom too, and will add link in op. (I have made two roms mb6 and mc3)
But really difficult to upload every rom, or to make specific on request.
Whenever there is major update and if I will update my device, that time will make that rom pre rooted.
Thanks for patience.
Sent from my GT-N7100 using xda premium
dr.ketan said:
Ok,
So will make complete Guide with link to all needed utilities. But may take some time.
Meanwhile try to upload pre rooted rom too, and will add link in op. (I have made two roms mb6 and mc3)
But really difficult to upload every rom, or to make specific on request.
Whenever there is major update and if I will update my device, that time will make that rom pre rooted.
Thanks for patience.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I can help
How?
Sent from my GT-N7100 using xda premium
Option 1
madhuranand007 said:
Option 1
Click to expand...
Click to collapse
Sure
Within 5 min updating OP
dr.ketan said:
How?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Advice to you ladies
http://forum.xda-developers.com/showthread.php?p=39848357#post39848357
http://forum.xda-developers.com/showthread.php?p=39286842#post39286842
You have incorrectly assembled system img.The composition of the image.
No busybox.No su in bin)))
resolution:
Code:
cd app
chmod 0644 Superuser.apk
My version:
https://hotfile.com/dl/202764580/bcb9aa2/system.img.zip.html
Please note, this software is no longer maintained. Due to my hectic work life sadly, I no longer have time for programming. I have attached a copy of the last version to this post.
[ ABOUT ]
Tar To Flashable Zip is a multi-platform utility designed to build flashable Android recoveries from various input formats. The supported input formats are .img from your local filesystem as well as compressed .tar or .tar.md5 archives.
Tar To Flashable Zip runs on Windows XP and newer, Linux/Ubuntu, and on OSX ( supposedly, not tested )
I'll also be putting this utility on my web site within the next couple of days
[ REQUIREMENTS ]
Tar To Flashable Zip is written in Python, so it needs Python to be installed on your machine as well.
Windows users will need to install either of the software pairs listed below from their prospective developers or drop down to the "REQUIRED SOFTWARE" section and download the zip archive I'm hosting which contains the first required software pair listed below.
Linux/Ubuntu users should use their update mechanism to update Python and install wxPython to the equivalent of either of the software pairs listed below.
Mac users will need to do what ever they need to do, sorry for the lack of information, to install/update Python to their equivalent of either of the software pairs listed below.
Python 2.7.5 + wxPython 2.8
OR
Python 3.3 + wxPython 2.9 Phoenix ( Snapshot nightly builds )
NOTE::
I feel I must explain why the above softwares are required. For those of you who already know me, I've written a couple tools for Android that run on Windows only as I am a Windows programmer. In any case, I've had several requests to make Linux versions of the same utility apps. Since I'm not a Linux programmer, I was unable to grant those requests.
I'm here to help everyone that I can help. That's just me... That being said, after some reasearch I found Python to be the easiest way for me to be able to help more people with the utilities that I develop. Python will enable me to develop more and more useful utilities for the Android community while requiring less of my time to develop them. So in the end, installing Python is a win - win situation
[ REQUIRED SOFTWARE ]
Tar To Flashable Zip was written in Python. Therefore the Python interpreter is required. Tar To Flashable Zip's GUI uses wxPython. The archive linked below for Windows users has both Python 2.7.5 and wxPython 2.8. Obviously after extracting the archives contents you need to run Python's installer msi to install Python first. Then install wxPython. The installers will install 32-bit versions of Python and wxPython. This is fine even if you are using a 64-bit machine.
Windows XP and newer users -> python-2.7.5_win32+wxPython-2.8_win32.zip
Linux/Ubuntu users -> Please use your update tool to update Python to 2.7.5 and wxPython 2.8 or update Python to 3.3 and wxPython to 2.9 Phoenix
Mac users -> Please see the "REQUIREMENTS" section above
[ DOWNLOADS ]
See belowhttp://d-h.st/QFr
[ THANKS ]
@CodyF86 - For his Python expertise and beta testing
Works great! Everyone should learn Python btw, it's amazing!
Working on P3110 =) Good work
Waiting for tar.md5 to zip
Thanks @Android-Andi.
Support for .tar.md5 as well as .IMG files coming soon
Update available. Check the OP
Support for extracting from .tar.md5 archives had been added however there is no checksum verification provided at this time.
View "CHANGELOG.txt" for complete details;
What about 64bit Windows 7 users
Sent from my GT-I9152 using XDA Premium 4 mobile app
BalaN83 said:
What about 64bit Windows 7 users
Sent from my GT-I9152 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Install the 32 bit versions of python and wxpython. I develop on a windows 7 64 bit PC. 32 bit works on 64 bit too
Sent from my LG-P509
Somewhat new to this stuff so I'm kinda learning as I go, so please be gentle with me
I'm not sure what my "mount" point is for my phone, Samsung Epic 4g touch SPH-D710
I am currently looking for a file I can open and look at it to learn this stuff but am not sure where to look or what file to go to.
Only thing I have is a tar file, and it has a zimage file in it (the kernel), it's the EL29 direct boot tar file.
Only 2 files available that I can find and that's the odin one click exe and this tar file, no zips, so I'm not even sure this will work, but I'd sure like to find out.
What I wanna do in short is make a flashable zip of this tar file to use in CWM recovery.
Hope that's not to much info, I always tend to do that
---------- Post added at 12:01 PM ---------- Previous post was at 11:54 AM ----------
Somewhat new to this stuff so I'm kinda learning as I go, so please be gentle with me
I'm not sure what my "mount" point is for my phone, Samsung Epic 4g touch SPH-D710
I am currently looking for a file I can open and look at it to learn this stuff but am not sure where to look or what file to go to.
Only thing I have is a tar file, and it has a zimage file in it (the kernel), it's the EL29 direct boot tar file.
Only 2 files available that I can find and that's the odin one click exe and this tar file, no zips, so I'm not even sure this will work, but I'd sure like to find out.
What I wanna do in short is make a flashable zip of this tar file to use in CWM recovery.
Hope that's not to much info, I always tend to do that
I found my mountable according to the files I have as a zip, it shows as /dev/block/mmcblk0p5 and /dev/block/mmcblk0p6.
I've tried putting both those in the recovery mount space and hit convert, but nothing happens.
The file name I am useing is E4GT-EL29-directbootCWM-v3.tar.md5 from rwilco site here http://www.rwilco12.com/downloads.p...ls/Recovery Kernels/GB/Noobnl Direct Boot/TAR
Not sure if that helps or not
easyrider77 said:
Somewhat new to this stuff so I'm kinda learning as I go, so please be gentle with me
I'm not sure what my "mount" point is for my phone, Samsung Epic 4g touch SPH-D710
I am currently looking for a file I can open and look at it to learn this stuff but am not sure where to look or what file to go to.
Only thing I have is a tar file, and it has a zimage file in it (the kernel), it's the EL29 direct boot tar file.
Only 2 files available that I can find and that's the odin one click exe and this tar file, no zips, so I'm not even sure this will work, but I'd sure like to find out.
What I wanna do in short is make a flashable zip of this tar file to use in CWM recovery.
Hope that's not to much info, I always tend to do that
---------- Post added at 12:01 PM ---------- Previous post was at 11:54 AM ----------
Somewhat new to this stuff so I'm kinda learning as I go, so please be gentle with me
I'm not sure what my "mount" point is for my phone, Samsung Epic 4g touch SPH-D710
I am currently looking for a file I can open and look at it to learn this stuff but am not sure where to look or what file to go to.
Only thing I have is a tar file, and it has a zimage file in it (the kernel), it's the EL29 direct boot tar file.
Only 2 files available that I can find and that's the odin one click exe and this tar file, no zips, so I'm not even sure this will work, but I'd sure like to find out.
What I wanna do in short is make a flashable zip of this tar file to use in CWM recovery.
Hope that's not to much info, I always tend to do that
I found my mountable according to the files I have as a zip, it shows as /dev/block/mmcblk0p5 and /dev/block/mmcblk0p6.
I've tried putting both those in the recovery mount space and hit convert, but nothing happens.
The file name I am useing is E4GT-EL29-directbootCWM-v3.tar.md5 from rwilco site here http://www.rwilco12.com/downloads.p...ls/Recovery Kernels/GB/Noobnl Direct Boot/TAR
Not sure if that helps or not
Click to expand...
Click to collapse
Sorry, currently this tool does not support zImage format. Does your device support fastboot? If so and my memory serves me correctly, fastboot can flash zImage formatted images.
I tried your advice today to convert an .tar.md5 rom to .zip.
Everything worked as you say but the .zip file I'm taking as result is 7.5 mb from a tar.md5 rom 2.02 giga. ..
Is me or something else ? Regards
Sent from my GT-N7100 using XDA Premium 4 mobile app
Well this is good!
I tested it successfully... on my Windows XP SP3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think there is a misunderstanding about this tool. Most of the users think that this tool can convert the whole tar/tar.md5 file to a ROM zip file. Actually it does with recovery.img only.... It's already specified in the thread... but not in the thread title....
zaharakis said:
I tried your advice today to convert an .tar.md5 rom to .zip.
Everything worked as you say but the .zip file I'm taking as result is 7.5 mb from a tar.md5 rom 2.02 giga. ..
Is me or something else ? Regards
Click to expand...
Click to collapse
zaharakis said:
I tried your advice today to convert an .tar.md5 rom to .zip.
Everything worked as you say but the .zip file I'm taking as result is 7.5 mb from a tar.md5 rom 2.02 giga. ..
Is me or something else ? Regards
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm not sure what exactly the problem is. This tool is only supposed to extract "recovery.img" from a .tar.md5 archive and then create a flashable zip. I've never seen a recovery of any kind that is 2+ GB in size. Most recoveries average around 10 MB, give or take a few MB.
Thread title has been update to reflect that this tool is for recoveries only.
shinobisoft said:
I'm not sure what exactly the problem is. This tool is only supposed to extract "recovery.img" from a .tar.md5 archive and then create a flashable zip. I've never seen a recovery of any kind that is 2+ GB in size. Most recoveries average around 10 MB, give or take a few MB.
Thread title has been update to reflect that this tool is for recoveries only.
Click to expand...
Click to collapse
No recovery,I tried to make a full rom.tar.md5 file to zip..
Sent from my GT-N7100 using XDA Premium 4 mobile app
zaharakis said:
No recovery,I tried to make a full rom.tar.md5 file to zip..
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry, you'll need to use ODIN to flash a ROM from .tar.md5 archive.
shinobisoft said:
Sorry, you'll need to use ODIN to flash a ROM from .tar.md5 archive.
Click to expand...
Click to collapse
Thank u mate ☺ I know it. I just wanted to make a flashable .zip file of rom to have it in my sdcard .
Sent from my GT-N7100 using XDA Premium 4 mobile app
Reverse?
is it possible to make a flashible zip into a tar? Just curious
majicmazo said:
is it possible to make a flashible zip into a tar? Just curious
Click to expand...
Click to collapse
Yes, but not with this utility.
Sent from my LG-P769 using Tapatalk
How to use on Mac
For those who wanna use this on a Mac OS X here is what you do.
Go to:
https://www.python.org/downloads/
Download the 2.7.7 python .dmg.
Mount the .dmg and run the Python.mpkg
Once the installer is done go to your applications folder. There will be a new folder there called Python 2.7.
Open that folder. Inside will be a Python Launcher.app (Looks like a Rocket Ship). The Python preferences window will come up.
Under Settings for file Type, change it from Python Script to Python GUI Script. Close out the preferences.
In the menu bar it should still say Python Launcher. Go to File / Open. Search for the TarToFlashableZip_1.0.0.1 folder you get from the zip you download in the original post. Find the TarToFlashableZip.pyw.
The tool will open. Load in your recovery.img or .tar file. Make sure you have chosen the right recovery partition and hit convert.
Thanks to the op for this tool. Very handy.
No way to use it on windows 7?
shinobisoft said:
[ ABOUT ]
Tar To Flashable Zip runs on Windows XP and newer, Linux/Ubuntu, and on OSX ( supposedly, not tested )
Click to expand...
Click to collapse
Hello
Thanks for this tool.
Is there no way to use this tool on windows 7?
Regards
Dr.Ghobar
Dr.Ghobar said:
Hello
Thanks for this tool.
Is there no way to use this tool on windows 7?
Regards
Dr.Ghobar
Click to expand...
Click to collapse
It requires Python to be installed on your system. I believe I stated such in the OP. This was developed on a computer running Windows 7 Professional...
Sent from my SM-G360P using Tapatalk
A lot of people were having issues with designgear's instructions on rooted their official roms.
Please read this guide (link below) first if you have no experience with this URDLV rooting method (a root method that avoids triggering KNOX counter).
http://www.theandroidsoul.com/universal-root-de-la-vega-script/
Here's a set of steps that worked
------------------------------------------------------------------
To URDLV your offical ROM (worked on MF4)
Some Assumptions:
1.) Snapdragon Processor
2.) Current Bootloader on your phone, MJ1 or lower. If higher, you'll likely trip KNOX
3.) Reactivation Lock = Disabled
Procedure:
Applying URDLV to Official ROM:
- Install Cygwin (64bit or 32 bit depending on your OS)
- Started the Cygwin terminal
- cd'ed to proper drive and URDLV folder
-----ie: cd urdl
- chmod +x URDLV.bat
- ./URDLV.bat full c:/URDLV/blahblah....tar.md5 (drag-n-dropped the path to the file)
-----this will take a while on regular HD
The following steps are folked into two alternate methods.
Method 1 can work for MF4, because it seems to work with the MF1 files, so not uploading the accompanying files from the official MF4 rom neglected by URDLV's process can work.
Method 2 is more complete, and includes the uploading of all files EXCEPT the bootloader, this should minimize any mismatches of files causing issues.
Method 1: Upload only System and Cache First, other files individually
-Use ODIN to send the file over to Phone (follow designgear's OP instructions)(or PART 2 in HERE: http://www.theandroidsoul.com/universal-root-de-la-vega-script/ )
-Put the root files on the phone
Extra Reading (optional):
- follow designgear's OP instructions
- PART 2 in HERE: http://www.theandroidsoul.com/universal-root-de-la-vega-script/
-----extract root_de_la_vega_sdcard.zip
-------- root_de_la_vega.sh (file)
-------- root_files (folder)
-----put into the directory: \sdcard
-Reboot
-Delete the Root files
-Reboot
-Extract the Modem.bin and NON-HLOS.bin file from the Official ROM (optional for MF4) (some later roms REQUIRE matching NON-HLOS.bin and MODEM.bin files)
-----these files were excluded by URDLV's output ROM (for reasons unknown with other ROM version, but the NON-HLOS.bin and modem files from MF4 seem to integrate fine)
-Use ODIN to send Modem.bin and NON-HLOS.bin to the phone via CP slot
If for some reason your WiFi passwords keep getting forgotten:
http://forum.xda-developers.com/showthread.php?t=2522629
-Done
Method 2 (which includes all files except the bootloader):
1.) Extract the System.img and Cache file FROM the URDLV tar.md5 TO [Folder]
--------You could use 7Zip
2.) Extract all files EXCEPT ABOOT and Cache file FROM the Official ROM TO [Folder]
3.) Now [Folder] should contain 10 files
4.) Tar up those files in [Folder].
----In Cygwin:
Change directory to the [Folder]
Enter the following commands to tar up your files into a TAR.MD5 file:
tar -H ustar -c *.* > your_odin_package.tar
md5sum -t your_odin_package.tar >> your_odin_package.tar
mv your_odin_package.tar your_odin_package.tar.md5
How your TAR.MD5 should look like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5.) Send your your_odin_package.tar.md5 package via ODIN (AP Slot) to your phone
6.) -Put the root files on the phone (follow designgear's OP instructions) (or PART 2 in HERE: http://www.theandroidsoul.com/universal-root-de-la-vega-script/ )
-----the directory: \sdcard
-Reboot
-Delete the Root files
-Reboot
If for some reason your WiFi passwords keep getting forgotten:
http://forum.xda-developers.com/showthread.php?t=2522629
-Done
------------------------------------------------------------------------------
For future rom updates (applicable to rooted users):
Reports claim that Mobile Odin works: http://forum.xda-developers.com/showthread.php?t=2522729
-------------------------------------------------------------------------------
Download Links in case if needed:
Working link:
https://mega.co.nz/#!co1jRKYY!p94iENAmHkqd9wD3c0T1qC_dz03o7n8xmmkuIiVxCLQ
OLD DELETED:
Universal RDLV script (v0.2)
https://mega.co.nz/#!ugJFUTCL!NrME135Mia6-x4e0E-21uQXmh8wMbhrksHG0HjTtg4g
Root de la Vega sdcard files
https://mega.co.nz/#!qoQnmAQD!U_dQMRsZ7UFMpEicnnGIFAtvn7V6Ti_gbyPDt9TDmmY
Odin v3.09
http://filecloud.io/cp43ua5j
Sammobile Firmwares
http://www.sammobile.com/firmwares/
Good guide m8 if I may tell you something to put in top of everything and This is that URDLV works only in mj1 bootloader and below, if with any way you have updated with OTA/KIES/SERVICECENTER or bought with mj3 and above you cannot use any of Vega ways.
Sent from my SM-N9005 using Tapatalk
You should write that old bootloader is needed and you should modify the process : boot, hidden and recovery images should be added to the tar
geek78 said:
You should write that old bootloader is needed and you should modify the process : boot, hidden and recovery images should be added to the tar
Click to expand...
Click to collapse
Are there any risks to triggering KNOX by integrating those files ?
I thought we don't want the boot file beyond mf1 since it makes it impossible to root without triggering KNOX later?
Figure there are reasons why designgears neglected to include those files.....
klau1 said:
Are there any risks to triggering KNOX by integrating those files ?
I thought we don't want the boot file beyond mf1 since it makes it impossible to root without triggering KNOX later?
Figure there are reasons why designgears neglected to include those files.....
Click to expand...
Click to collapse
No it won't as those are not the bootloader. I made a URDLV system image of MJ7 and added all the other files from the original rom (MINUS aboot --> bootloader) and flashed with odin. Got root and knox counter not tripped. :good:
Nice, I dont feel like uploading the system image again (and reroot), just to get the other files in.
Can I just tar.md5 up the left over files and Odin them in?
If so, which Odin slot?
klau1 said:
Nice, I dont feel like uploading the system image again (and reroot), just to get the other files in.
Can I just tar.md5 up the left over files and Odin them in?
If so, which Odin slot?
Click to expand...
Click to collapse
Yes you can just tar.md5 the rest and flash it. Not really sure where to place it but you can try ap or wait for others to reply.
Yes, I tar.md5 them up and ODIN them up from the AP slot.
It works
Was this thread moved over the General?
If not, could a MOD please move it over to Original Development where the URDLV thread also resides?
Thanks,
klau1 said:
Was this thread moved over the General?
If not, could a MOD please move it over to Original Development where the URDLV thread also resides?
Thanks,
Click to expand...
Click to collapse
Guides don't go in Development threads.
@klau1
Can you remove the download links please and link to the thread. I am going to be updating soon and don't want you to have dead links or links to older versions up. Thanks.
This guide will NOT work and brick your camera and wifi (did for me)
Real solution: http://forum.xda-developers.com/showthread.php?p=47390175
@klau1 u are allowed to copy my guide if you put my name on the op
My guide is 100% working for me 0x0 root camera wifi dmj7
Sent from my SM-N9005 using XDA Premium 4 mobile app
It didn't work for you, I suspect because your mj7 rom requires the matching modem and nos file. Where as the MJ4 can work without it.
In the case of mj7, the other files designgears urdlv neglected to include are required.
@designgears Let me know once you've updated your guide so I can update and reflect the changes here thanks.
Hi all!
I own SGN 3 with exynos octa processor.
Versions of installed firmware:
AP: N900XXUBMJ1
CP: N900XXUMI2
CSC: N900OJVBMI5
Can I root this device with URDLV method without any problem with KNOX and warranty?
Can I update firmware in the future with KNOX trigger = 0x0 and so on?
Thanks.
No, UDRLV only works with Snap Dragon version.
klau1 said:
It didn't work for you, I suspect because your mj7 rom requires the matching modem and nos file. Where as the MJ4 can work without it.
I thought it didn't work on any bootloader under MJ1?
If it does work on MJ4, I'm on N900W8OYABMJ4 (Rogers Canada), which method would work best for rooting it.
Thanks! Sorry for being a noob:crying:
Click to expand...
Click to collapse
SimerToor said:
klau1 said:
It didn't work for you, I suspect because your mj7 rom requires the matching modem and nos file. Where as the MJ4 can work without it.
Click to expand...
Click to collapse
I thought it didn't work on any bootloader under MJ1?
If it does work on MJ4, I'm on N900W8OYABMJ4 (Rogers Canada), which method would work best for rooting it.
Thanks! Sorry for being a noob:crying:
Click to expand...
Click to collapse
If the phone is ALREADY on MJ4 it's impossible to root with the current URDLV.
This method requires you to START OFF with MJ1 ROM because once your phone already has been upgraded beyond MJ1, the newer bootloader can detect changes in the URDLV rom and trigger KNOX.
Whereas the bootloader in MJ1 can be exploited.
You can't factory reset the bootloader back to MJ1 after you've upgraded AFAIK.
efs safe?
Hi,
Is the efs partition safe when flashing all those files ?
Could it be overwritten ?
Thx.
Masterz said:
Hi,
Is the efs partition safe when flashing all those files ?
Could it be overwritten ?
Thx.
Click to expand...
Click to collapse
100% safe
leave a 'thanks' if i helped
SM-N9005 URDLV 0x0
XDA Developers 4 premium app
Frickin amazing. Worked perfectly on my T-Mobile Note 3. No flag tripped, have root, will party. Had to use Cygwin to do it BTW.
I got the notification to install and I tried. Shield restarted and the little green android guy showed up and it started installing the update. Half way through it showed a red explanation mark with the words "error". I had to hold down the shield+home keys to restart. The shield restarted just fine. I deleted the data in google frameworks (read to do that here) and tried the update again, same outcome.
I'm new to android (came from iphone) and now have a galaxy S4. So I apologize about the noobiness.
My shield is rooted and bootloader unlocked. As far as I know I did not install any custom recovery. I thought that users should be able to install OTA if they are running the stock OS and no custom recoveries. Am I wrong about that? Anyways, I have SuperSU installed along with a few rooted apps. My guess is that I will need to install a custom recovery so I can flash this update, is this correct? I would be very grateful if someone would explain whats going on here =P
You should not need a custom recovery for this.
Due to the download size of this update it appears to be an incremental update.
the download size i see is 22.3 MB
You would need to see the exact error to try an figure out more.
UPDATE
Installed fine for me
Custom recovery is definitely not needed. Root by itself also does not interfere. I updated without trouble.
Maybe try reflashing the boot and system partitions to stock and try the update again?
Gnurou said:
Custom recovery is definitely not needed. Root by itself also does not interfere. I updated without trouble.
Maybe try reflashing the boot and system partitions to stock and try the update again?
Click to expand...
Click to collapse
a quick how to on reflashing the boot and system would be awesome!!
--edit:nevermind... im trying out Kwonggers program--
ok somehow i softbricked my shield. I've tried Kwonggers program and I've manually flashed recovery,boot, and system and afterwards all I get is the flashing green controller during boot. I know I did it right because all messages were positive.
I also downloaded the most up to date shield files from nvidia (update64) which is extract-nv-recovery-image-shield-01.00.13216_261.5912.sh however I dont know how to use a *sh file.
Rhokk said:
a quick how to on reflashing the boot and system would be awesome!!
--edit:nevermind... im trying out Kwonggers program--
ok somehow i softbricked my shield. I've tried Kwonggers program and I've manually flashed recovery,boot, and system and afterwards all I get is the flashing green controller during boot. I know I did it right because all messages were positive.
I also downloaded the most up to date shield files from nvidia (update64) which is extract-nv-recovery-image-shield-01.00.13216_261.5912.sh however I dont know how to use a *sh file.
Click to expand...
Click to collapse
it needs a factory rest.
my suggestion is to re-flash system (again) using the command fastboot -w flash system system.img
the .sh file is for use on Linux, cygwin can probably do that if you have the correct things installed with it.
chevyowner said:
it needs a factory rest.
my suggestion is to re-flash system (again) using the command fastboot -w flash system system.img
the .sh file is for use on Linux, cygwin can probably do that if you have the correct things installed with it.
Click to expand...
Click to collapse
Chevyowner you are the best! After reading your suggestion, I tried just the system.img this time and presto! This time it took. Not sure why it didn't take the 2 times I tried it last night.
Thanks for helping newer guys like me. Really appreciate it!
Rhokk said:
Chevyowner you are the best! After reading your suggestion, I tried just the system.img this time and presto! This time it took. Not sure why it didn't take the 2 times I tried it last night.
Thanks for helping newer guys like me. Really appreciate it!
Click to expand...
Click to collapse
glad you got it working
chevyowner said:
glad you got it working
Click to expand...
Click to collapse
hi.
i am a new guy from far far away China, language is the biggist problem.
the same issue, i can't fix it, error in updating ota 65.
re-flash system (again) using the command fastboot -w flash system system.img
Click to expand...
Click to collapse
how to do? where i can get /system.img/? and how to push the img to my Shield?
except a PC and a cable, i don't have any tools, no software. and i can't get that what you guys talking about. but the same issue.
if you guys can help, i will be very appreciated
if u do know Chinese.....=P
Hi, I have the same issue, OTA 64 installed with bootloader unlocked and rooted. Will my data be preserved if I flash only the system image?
Nikojiro said:
Hi, I have the same issue, OTA 64 installed with bootloader unlocked and rooted. Will my data be preserved if I flash only the system image?
Click to expand...
Click to collapse
how can you get the /system image/? thanks
starfriend.y said:
how can you get the /system image/? thanks
Click to expand...
Click to collapse
Here's how I fixed my system:
Downloaded OTA 65 image from https://developer.nvidia.com/develop4shield
As per instructions (see https://developer.nvidia.com/sites/default/files/akamai/mobile/shield/HowTo-Flash-Recovery-Image_1.txt), flashed only boot, recovery and system images (so it wouldn't wipe your user partition, e.g. apps and data)
Rebooted the unit, waited for the upgrade to complete. Root will be lost if you had it.
Rerooted the unit (see https://github.com/linux-shield/shield-root)
It works perfectly now.
Nikojiro said:
Here's how I fixed my system:
Downloaded OTA 65 image from https://developer.nvidia.com/develop4shield
As per instructions (see https://developer.nvidia.com/sites/default/files/akamai/mobile/shield/HowTo-Flash-Recovery-Image_1.txt), flashed only boot, recovery and system images (so it wouldn't wipe your user partition, e.g. apps and data)
Rebooted the unit, waited for the upgrade to complete. Root will be lost if you had it.
Rerooted the unit (see https://github.com/linux-shield/shield-root)
It works perfectly now.
Click to expand...
Click to collapse
thanks for your help.
is that /ota 65 image/ a 1.0GB .sh file? i can't unzip it.
i think that i have to unzip the .sh file with a linux pc.
starfriend.y said:
thanks for your help.
is that /ota 65 image/ a 1.0GB .sh file? i can't unzip it.
i think that i have to unzip the .sh file with a linux pc.
Click to expand...
Click to collapse
Yes the .sh file is a linux shell script. I can repack it in a standard zip and upload it later today on a share if you want.
Sent from my GT-I9100 using Tapatalk
Ok I uploaded a repacked zip of the OTA 65 images for linux-less people
https://mega.co.nz/#!ccRCQTAS!FylQx29ZE7RUvi-kzbwb53woZGRZUu9_RAQNk9_FkMI
Please note that you'll need to have the Android SDK installed, as well as the proper USB driver.
Nikojiro said:
Ok I uploaded a repacked zip of the OTA 65 images for linux-less people
https://mega.co.nz/#!ccRCQTAS!FylQx29ZE7RUvi-kzbwb53woZGRZUu9_RAQNk9_FkMI
Please note that you'll need to have the Android SDK installed, as well as the proper USB driver.
Click to expand...
Click to collapse
thanks a lot! you are so kind!
Nikojiro said:
Ok I uploaded a repacked zip of the OTA 65 images for linux-less people
https://mega.co.nz/#!ccRCQTAS!FylQx29ZE7RUvi-kzbwb53woZGRZUu9_RAQNk9_FkMI
Please note that you'll need to have the Android SDK installed, as well as the proper USB driver.
Click to expand...
Click to collapse
here i come again...
as your guide, i've flash my Shield /recovery.img/ and /boot.img/, they all done. but failed when i flash /system.img/, "FAILED (remote: insufficient memory)"
why?
starfriend.y said:
here i come again...
as your guide, i've flash my Shield /recovery.img/ and /boot.img/, they all done. but failed when i flash /system.img/, "FAILED (remote: insufficient memory)"
why?
Click to expand...
Click to collapse
Hi, sorry with so little background information I'm afraid I can't help. I'd recommend a full reflash of your unit.
Sent from my GT-I9100 using Tapatalk
Nikojiro said:
Hi, sorry with so little background information I'm afraid I can't help. I'd recommend a full reflash of your unit.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
thank you first.
I do as you said, download the file, unzip it, and i got /system.img/, /boot.img/ and /recovery.img/.
i opened cmd and type /fastboot flash system system.img/ and i got failed information: /FAILED (remote: insufficient memory)/
im sure i wipe my shield first, and i flash recovery, boot very well.
can't update
hello,
I would very much appreciate some real help.
I want to be able to update to 65 WITHOUT loosing my userdata. I very much care for all my settings, software and setup.
I am bootloader unlocked from the very beginning and rooted. I was able to update OTA just fine until this update, and the root back very easily each time afterwards.
I knew that this ($#@@ing) delta update will give me trouble so I made some research first. With no use... I still couldn't update..
What I did:
-> downloaded custom CMW for shield and booted. made a nandroid (again: I very much care for my data and I won't update until and can do it without wiping) - all fine
-> downloaded the extracted image of OTA 65 from this thread, booted into boot loader and did:
fastboot flash recovery recovery.img
- OK
fastboot flash boot boot.img
- OK
fastboot flash system system.img
- insufficient memory crap.. (hoped I won't get it but... (( )
-> booted back into JB.. booted fine but my SD card storage partition wasn't where file managers read it anymore (it was mounted and OK on /system/storage but just lost some symlink of some sort... no big deal.. I guess it was the new bootloader at fault but since the 65 system image wasn't flashed I guessed it will work again afterwards..)
-> opened supersu, full unrooted, took a leap of fate and tried the delta update OTA... gave me the killed andoid at about 50% (
-> tried fastboot flash system system.img on another computer.. insufficient memory crap again....
-> so I booted again into CMW and restored my nandroid. Luckily everything worked fine...
So if someone knows how can I go 65 without userdata wipe, please help me!
thank you very much
Same problem here
Surprise, surprise! .... =(
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
//cc @Nikojiro