Database Info

[Q] Update Binary Script

Hey,
having a problem with installing zips
phone doesn't seem to be able to install any ROM or superuser but can install gapps, google now, recoveries, etc.
the error looks like this
E: error in sdcard/roms/path
(Status 0)
Aborted
Been looking around and people with status 0 problems normally get them by doing something wrong with the update binary when developing their own roms. I recently messed up my phone a little and although I got it working again I think the update binary might still be changed.
Since I know nothing about any of this kind of thing,
Does anyone have access to a stock or tested and working update-binary file that I can replace mine with,
or at least check to see if there's any differences, to see if that's the problem?
If anyone has any ideas about what might be causing the problem i'd appreciate help
Thanks

i would start be reflashing the recovery becasue i highly doubt that the roms that all these DEV have built is the issue with binary script if you want to pull one from a stock rom. you can grab one from Vincoms thread. and not to mention make sure you have atleast attempted to download the rom twice incase you have a bad zip folder. another thing you cant would be to flash from the internal

crashpsycho said:
i would start be reflashing the recovery becasue i highly doubt that the roms that all these DEV have built is the issue with binary script if you want to pull one from a stock rom. you can grab one from Vincoms thread. and not to mention make sure you have atleast attempted to download the rom twice incase you have a bad zip folder. another thing you cant would be to flash from the internal
Click to expand...
Click to collapse
No it's 100% a problem with the phone,
I've tried multiple recoveries, multiple roms, that were downloaded multiple times from multiple sources, and while running multiple roms (from recoveries) and all give the exact same error. TWRP's error looks a little different but I'm pretty sure its the same thing.
I thought there was just a .tar file on vincom's thread for the stock firmware
i'll check again to see if I can find what I need from there though,
thanks.

there is a zip stock recovery fashable file, but not a tar one, either revert to full stock via odin then reinstall a custom recovery, or backup your sdcards and reformat them to see if that corrrects your problem

[Q] Help Flashing ROM

Thanks for your help and time in advance. I am trying to flash a ROM to my At&T HTC One X. It is HBOOT 1.14 running ics 2.20. I am specifically trying to flash ViperXL and have failed about 3 times so far. I keep getting my phone stuck in a boot loop. It is no longer in a boot loop because I have flashed the factory ROM. My phone is rooted and I have TWRP as my recovery. I have some specific questions to ask:
1) What version of ViperXL should I use? I think I might be trying to flash the wrong version.
2) Do I leave the entire file zipped when I put it on my sd card or do I specifically extract the boot.img file and keep that file separate from the zip file?
3) If I have Flash Image GUI from the playstore should I use that to flash it? If so do I still follow step 2 above?
This is what I have been doing so far:
1) Downloading this file: ViperXL 3.2.1 - Android File Host (685MB) from http://forum.xda-developers.com/showthread.php?t=1868236
2) Using WInRar to extract its contents and move it to my sd card.
3) Using Flash Image GUI to select boot.img and then pressing flash.
4) Rebooting my phone and then wa-la, boot loop. I have actually been following a youtube video on how to do it but I'm not getting no luck.
If there is an easier way please inform me. I am a noob but love this stuff. Please be specific with instructions so I can enjoy an awesome custom ROM.
Again, thank you for your time and have a great day.

dirty2k9 said:
Thanks for your help and time in advance. I am trying to flash a ROM to my At&T HTC One X. It is HBOOT 1.14 running ics 2.20. I am specifically trying to flash ViperXL and have failed about 3 times so far. I keep getting my phone stuck in a boot loop. It is no longer in a boot loop because I have flashed the factory ROM. My phone is rooted and I have TWRP as my recovery. I have some specific questions to ask:
1) What version of ViperXL should I use? I think I might be trying to flash the wrong version.
2) Do I leave the entire file zipped when I put it on my sd card or do I specifically extract the boot.img file and keep that file separate from the zip file?
3) If I have Flash Image GUI from the playstore should I use that to flash it? If so do I still follow step 2 above?
This is what I have been doing so far:
1) Downloading this file: ViperXL 3.2.1 - Android File Host (685MB) from http://forum.xda-developers.com/showthread.php?t=1868236
2) Using WInRar to extract its contents and move it to my sd card.
3) Using Flash Image GUI to select boot.img and then pressing flash.
4) Rebooting my phone and then wa-la, boot loop. I have actually been following a youtube video on how to do it but I'm not getting no luck.
If there is an easier way please inform me. I am a noob but love this stuff. Please be specific with instructions so I can enjoy an awesome custom ROM.
Again, thank you for your time and have a great day.
Click to expand...
Click to collapse
wipe cache dalvik system and factory reset in recovery
fastboot flash boot boot.img or use the gui to flash the boot.img extracted from the viper rom
install the viper rom within recovery.
read more before you end up with a brick.
it says all this right in the second post of the viper thread
"Download the ViperXL 3.0.0 from the download section
Confirm the md5 checksum is correct on both files (it will be noted on the dl page)
Place the file somewhere on your phone storage
Reboot to TWRP recovery
Backup current ROM
Install ROM using twrp and select wipe during aroma install if coming from another base
If you have 1.14 hboot you will need to flash the boot.img in fastboot. You will need to extract this from the ROM zip. I have found the following tool useful: [TOOL] HTC Auto Boot.img Installer (One Click Tool)
Reboot and Enjoy"

All Flash Image GUI does is flash the boot.img, which is a small part of the overall ROM. You also need to have the entire ROM zip on your SD card. Boot into bootloader, then go into TWRP recovery. Once in TWRP, go to Wipe, do a factory reset (do not factory reset in bootloader, as it will corrupt your SD memory), wipe Dalvik, wipe cache. Then select Install, and navigate to the ROM zip. The ROM will begin to install. AROMA will then launch, giving you a variety of install options specific to ViperXL. Go through the AROMA options. Then when the ROM install is complete, TWRP will give you the option to reboot. Reboot and enjoy.

Do not extract rom lol. Flash it as is!
Sent from my One X using Tapatalk 2

flash successful
Thank you everyone for your replies. I got the ROM flashed and it's working great.

redpoint73 said:
(do not factory reset in bootloader, as it will corrupt your SD memory
Click to expand...
Click to collapse
Wow how did you figure this out? I now know why my sd corrupted on me once. I did click that once in my life. In fact it put me i have the "soft brick and gonna cry" category, complete with post in q&a.
There needs to be a sticky for things like this.. Little nuggets of knowledge.
The sticky should also contain the factory recovery.
And then the sticky should be mandatory before you are allowed to download roms, recoveries, etc. It would save headache for many.

wdkingery said:
Wow how did you figure this out? I now know why my sd corrupted on me once. I did click that once in my life. In fact it put me i have the "soft brick and gonna cry" category, complete with post in q&a.
There needs to be a sticky for things like this.. Little nuggets of knowledge.
The sticky should also contain the factory recovery.
And then the sticky should be mandatory before you are allowed to download roms, recoveries, etc. It would save headache for many.
Click to expand...
Click to collapse
Agreed. I too fall into the category of accidently bootloader factory resetting and almost dieing lol

it has been stated not to factory reset in bootloader, i have posted it probably almost 100 times. i'm glad this thread is finally over it was making me itch and twitch.

wdkingery said:
Wow how did you figure this out? I now know why my sd corrupted on me once.
Click to expand...
Click to collapse
Its a fairly common mistake, and as DvineLord stated, it been discussed quite a bit in various places.

can't flash kernel with odin

hi, i've got CyanogenMod 7.2 (Alpha9) on my galaxy 3, i initially used odin, then found i had the 0kb free space issue, but then used CWM to flash from a zip file and it's now working fine.
i'd like to put the MTD version on it, and i'm trying to follow the instructions here http://forum.xda-developers.com/showthread.php?t=2309390, but i can't get odin to flash the 1Ghz overclock mtd kernel.
the version of odin that i initially flashed the rom with has no problem establishing a connection with my phone, but says the .tar file is an invalid image when i try to load it in the PDA section.
i've tried a couple of other versions of odin, and they all accept it as a valid image, but none of them get past the point where it says setup connection.

alternatively, a link to a version of the same kernel that i can use CWM recovery to flash would be ideal, i've got to grips with CWM and find it easy to work with, but i'm struggling somewhat with odin.

i've realised my problem all along was that my copy of the mtd update was corrupt. i have re-downloaded it and all is going smoothly so far.

Mr Creosote said:
i've realised my problem all along was that my copy of the mtd update was corrupt. i have re-downloaded it and all is going smoothly so far.
Click to expand...
Click to collapse
Finally ! Have fun with the ROM.

marcellusbe said:
Finally ! Have fun with the ROM.
Click to expand...
Click to collapse
thanks, i'm very happy with it now that the battery isn't draining really quickly like it was with the non-mtd version. i'd been going about it the right way all along, lol, it just never occurred to me that i had a corrupt file. was only when i double clicked on it to look at the contents of the zip that i realised it was corrupt. i was beginning to worry that the world of android modding was hopelessly impenetrable.

[HELP THREAD] cm-13 on gt-p5100

Hello guys,
I installed cm-13 successfully and it was operating fine until yesterday. Today I tried to install a theme or something and it hung. So i just felt like doing a factory reset and I did it through my cwm recovery. But before that i made a backup, then i did the reset, then i did the restore...ever since then i havent been able to open the OS...it gets stuck on the samsung GALAXY Tab2 10.1 screen. I can however access the cwm recovery. I did infact try to unzip the cm-13 that i had previously used, and it doesnt work...
Please help guys!
I am pretty new to this and i feel like i cant figure out what to do next.

Is there a way to maybe restart the whole process, like get rid of the cm-13 that is already installed and redo the whole thing again?
Kindly help guys, i was really enjoying the cm experience and i messed it up :/

killermara said:
Is there a way to maybe restart the whole process, like get rid of the cm-13 that is already installed and redo the whole thing again?
Kindly help guys, i was really enjoying the cm experience and i messed it up :/
Click to expand...
Click to collapse
you did a backup before factory reset, then you restored the same data after reset. this hardly changed anything. the reason it didn't boot, is that The problem lies at the system partition, you should wipe system partition, data partition as well and flash the same cm-13 zip again along with gapps, if you had.
now let the system start. it should boot up with a clean installation. you can then try to advance restore and chose only data partition.
later just switch to twrp recovery by Android-Andi

HELP!
billysam said:
you did a backup before factory reset, then you restored the same data after reset. this hardly changed anything. the reason it didn't boot, is that The problem lies at the system partition, you should wipe system partition, data partition as well and flash the same cm-13 zip again along with gapps, if you had.
now let the system start. it should boot up with a clean installation. you can then try to advance restore and chose only data partition.
later just switch to twrp recovery by Android-Andi
Click to expand...
Click to collapse
Hello, actually I did exactly that, i wiped system partition and all of that...then i did try with cwm, and it didnt work, what is happening is that i select the option to flash the ROM, then the screen goes blank for a second and comes back to the home screen of the cwm recovery. So basically i selected the zip and nothing happened! I then tried flashing using twrp and the problem now was that there was the "no md5 file found" message and the installation would not stop, it would go on for too long, like some sort of loop. I then switched back to cwm and tried again and it still doesnt seem to work...kindly advice on what to do next

killermara said:
Hello, actually I did exactly that, i wiped system partition and all of that...then i did try with cwm, and it didnt work, what is happening is that i select the option to flash the ROM, then the screen goes blank for a second and comes back to the home screen of the cwm recovery. So basically i selected the zip and nothing happened! I then tried flashing using twrp and the problem now was that there was the "no md5 file found" message and the installation would not stop, it would go on for too long, like some sort of loop. I then switched back to cwm and tried again and it still doesnt seem to work...kindly advice on what to do next
Click to expand...
Click to collapse
first thing check if you have updated to last official stock jellybean rom prior to cm13 upgrade.
this thread will help you to update your bootloader to jb from ics. if you have a jb bootloader already. you can skip this.
forum.xda-developers.com/showthread.php?t=2642005
next thing you should get twrp 3.0.2.8
https://www.androidfilehost.com/?w=files&flid=48848&sort_by=date&sort_dir=DESC
after wiping, restart recovery, then flash the Rom zip
it takes time with the new CM13 builds to complete installation. some earlier twrp recoveries had issues(3.0.0.1 and 0.2, not sure right now, try latest only). cwm is not supported and twrp is the only preferred recovery by the Rom developers to flash the newer roms.
remember p5100 tab is called espresso3g now, since development has been unified. you need files marked as espresso3g for your p5100.
I don't which files are you using, development has changed so confirm the files that you're using are for unified builds and not device specific.

billysam said:
first thing check if you have updated to last official stock jellybean rom prior to cm13 upgrade.
this thread will help you to update your bootloader to jb from ics. if you have a jb bootloader already. you can skip this.
forum.xda-developers.com/showthread.php?t=2642005
next thing you should get twrp 3.0.2.8
https://www.androidfilehost.com/?w=files&flid=48848&sort_by=date&sort_dir=DESC
after wiping, restart recovery, then flash the Rom zip
it takes time with the new CM13 builds to complete installation. some earlier twrp recoveries had issues(3.0.0.1 and 0.2, not sure right now, try latest only). cwm is not supported and twrp is the only preferred recovery by the Rom developers to flash the newer roms.
remember p5100 tab is called espresso3g now, since development has been unified. you need files marked as espresso3g for your p5100.
I don't which files are you using, development has changed so confirm the files that you're using are for unified builds and not device specific.
Click to expand...
Click to collapse
I followed all the steps that you suggested, and the thread suggested.
I installed custom recovery, then I updated the bootloader.
Then i flashed the new twrp, which is alot more easier to operated compared to the cwm .
then i wiped , restarted recovery, then flashed the rom,
the exact same thing that was previously happening with the cwm happened : I tapped on the rom, then a blank screen appeared and it went back to the main menu of the twrp...
The ROM i am using is: cm-13.0-20160220-1347-UNOFFICIAL-p5100.zip
i also tried using the ROM i got from get.cm : cm-11-20160822-NIGHTLY-p5100.zip
Okay so i played a slow mo video to see what the screen says before it goes back to the welcome screen:
Updating partition details. . .
. . . done
Full SElinux support is present.
MTP Enabled
Then after this pops up, it goes back to the main menu of the twrp.
What if i just reinstall the stock OS then do the whole process of getting cyanogenmod again from rooting onwards?
Kindly assist!!

killermara said:
I followed all the steps that you suggested, and the thread suggested.
I installed custom recovery, then I updated the bootloader.
Then i flashed the new twrp, which is alot more easier to operated compared to the cwm .
then i wiped , restarted recovery, then flashed the rom,
the exact same thing that was previously happening with the cwm happened : I tapped on the rom, then a blank screen appeared and it went back to the main menu of the twrp...
The ROM i am using is: cm-13.0-20160220-1347-UNOFFICIAL-p5100.zip
i also tried using the ROM i got from get.cm : cm-11-20160822-NIGHTLY-p5100.zip
Okay so i played a slow mo video to see what the screen says before it goes back to the welcome screen:
Updating partition details. . .
. . . done
Full SElinux support is present.
MTP Enabled
Then after this pops up, it goes back to the main menu of the twrp.
What if i just reinstall the stock OS then do the whole process of getting cyanogenmod again from rooting onwards?
Kindly assist!!
Click to expand...
Click to collapse
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...

killermara said:
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...
Click to expand...
Click to collapse
do what @billysam said.
dont use device specific stuff. the latest twrp will only work with unified builds. for your device you need espresso3g builds.
you will find the latest roms on android-andis github site http://andi34.github.io/index.html

killermara said:
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...
Click to expand...
Click to collapse
you're using device specific Rom build, cm13.0 unofficial p5100, the latest twrp recovery you have, is a unfied espresso3g one.
latest roms, are build upon espresso3g for p5100,p3100 and espressowifi for p5110,p5113 p3113.
use latest cm13 rom zip, marked espresso3g.
there are device specific roms and recovery, which developers have stopped working on, your issue is because of this. get unified recovery and rom.

billysam said:
you're using device specific Rom build, cm13.0 unofficial p5100, the latest twrp recovery you have, is a unfied espresso3g one.
latest roms, are build upon espresso3g for p5100,p3100 and espressowifi for p5110,p5113 p3113.
use latest cm13 rom zip, marked espresso3g.
there are device specific roms and recovery, which developers have stopped working on, your issue is because of this. get unified recovery and rom.
Click to expand...
Click to collapse
Yea i thought so too, thats why i downloaded the cm-13.0-20161117-NIGHTLY-espresso3g.zip, then i wiped and tried to flash this rom, this also gave me the same error,
i also noticed that before the lines
Zip file is corrupt
there was:
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.

killermara said:
Yea i thought so too, thats why i downloaded the cm-13.0-20161117-NIGHTLY-espresso3g.zip, then i wiped and tried to flash this rom, this also gave me the same error,
i also noticed that before the lines
Zip file is corrupt
there was:
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
Click to expand...
Click to collapse
maybe the zip got corrupted, checked your pc with anti-virus? are you downloading the zip file from androidfilehost of android-andi? or some other source? checked your sd card as well?

Unable to flash twrp in J7 Nxt(Oreo-8.1.0)

Every time i tried to flash twrp recovery via Odin it failed or stucked.i tried many times but failed.i reset my phone and try again but again it failed.also changed the data cable but same result.
Note that i tried Izzy12 sir's final and stable recovery.img by making it a .tar format by PeaZip.Help someone to successfully flash the twrp.I want to flash a custom rom.Please help!:crying::crying:

You'll want to check that you have the latest version of Odin. It was necessary with Oreo.
Also, I had a problem making a tar file with the newer TWRPS initially and while it finally worked taking off by making my changing the filename from .tar.mdb to just .tar but before getting this right, I flashed just the recovery part of the following TWRP and not the bootloader part. Notice that its a little buggy but you can go straight from flashing it to flashing the recovery image of the recent version that you want from the image file on the sdcard and reboot to the newer recovery https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009

PantsDownJedi said:
You'll want to check that you have the latest version of Odin. It was necessary with Oreo.
Also, I had a problem making a tar file with the newer TWRPS initially and while it finally worked taking off by making my changing the filename from .tar.mdb to just .tar but before getting this right, I flashed just the recovery part of the following TWRP and not the bootloader part. Notice that its a little buggy but you can go straight from flashing it to flashing the recovery image of the recent version that you want from the image file on the sdcard and reboot to the newer recovery https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
Click to expand...
Click to collapse
Thank you for replying.But the lates twrp didn't work.so i tried a little bit older and it worked!:laugh:
Thank you again!:victory: