Repackaging a ROM? - HTC One X

Hi there,
Over the past few days I've been "messing" around with rooting my One X, starting with Cyanogen and then I was stupid and soft bricked it trying to put on a wrong ROM. I managed to sort all that out with a recovery and went back to Cyanogen.
I've just put Paranoid Android 3.10 on through the method that a youtube user "cursed4eva" followed which was the "standard" process as I was going from CM of which was just a "fastboot flash boot boot.img" in fastboot, then using recovery install the ROM and GApps from zip.
It's all working fine, apart from the WiFi won't turn on when you click the button in settings it flashes blue then back to grey.
Googling around it appears you have to repackage the ROM with a new Kernel (Seen XM 295 was meant to be good) So I have that downloaded but now I can't find any tutorials on how to go about actually repackaging the ROM for PA3.10 or XM295 with a One X.
Any help with getting this sorted or any other methods of getting my WiFi working would be great.
Thanks,
Tom.

You dont repack a rom......only repack the kernel. After that flash it. Google on nibble repack

Thanks for the reply,
my bad on the terms as mentioned I'm fairly new to the rooting of phones, Ok that site has finished,
Just to confirm, you use the new image file it's made, move that back into the PA zip file then do the normal process to install the ROM to the phone?

Ah i think you forgot to flash the boot.img from the rom.zip
The boot.img won't be flashed with the rom install. It needs to flashed via fastboot

Thanks for the reply,
First time around I flashed the boot image across I just wanted to ask if you move the "new boot.img" the website has made with the repackaged kernel into the paranoidandroid zip file or if you keep the standard one in there.
I'm aware I need to fastboot flash the new image across just not sure if it's also needed in the zip on the phone or not.

Ah no not needed

Thanks for all the help

Hi again.
It's all finished and the WiFi still doesn't want to turn on fully. To go with it Bluetooth also now doesn't want to turn on xD
Out of interest do you have any recomendations of kernels to use that can fix this issue?

Never used aosp roms. Check the thread OP. If the delivered boot.img won't work properly it should say something about in there.
It says repack with any aosp kernel. So repack the boot.img and flash the new boot.img, then flash the modules.zip via recovery of the kernel you repacked it with.
Did you try this one too ?
http://forum.xda-developers.com/showthread.php?t=2174855

Whilst trying to install the zip for that one it gets up to
"installing update..." then errors with:
"assert failed: getprop("ro bootloader") == "1.28.000" and repeats for the numbers from changing for 1.28, 1.31, 1.36 and 1.39.
I assume that is something to do with the bootloader rather than the rom?
on the bootloader screen all I can see is the HBOOT-1.72.000 etc. so not quite sure about that :/ that is with the 3.65 version on the link, attempting 3.99 now if all else fails will just go back to Cyanogen for now
Within the thread for the rom I was trying to start it didn't mention it, a few posts did which was met with repackage the kernel and that the XM 295 one worked for them.

Ah then you have to edit a file in the meta inf folder of the rom.zip.....hold on i for it somewhere
http://forum.xda-developers.com/showthread.php?t=2478409
Easiest is to remove for instance 1.39 and replace it with your bootloader version

Edit - Feel stupid, sorry didn't full read it xD HBOOT version is my bootloader.
Thanks once again.

Sorry for the double post but would just like to say a big thanks for all the help.
Phone is now running Paranoid Android 3.65 with working WiFi and signal So once again a big thanks

TrueSlawter said:
Sorry for the double post but would just like to say a big thanks for all the help.
Phone is now running Paranoid Android 3.65 with working WiFi and signal So once again a big thanks
Click to expand...
Click to collapse
Nice ! Good news then. Well enjoy

Related

[Q] HOX stuck in loop, hboot 1.12 need help

Sorry if this may or may not be another noob thread but my HOX is stuck in looping splash screen. I have installed CWM and i can still access bootloader. I have not yet flashed any ROM (still on stock) because i was stuck on this when i tried.
my HOX is unlocked as well.
one thing more, i downloaded 2-3 times JB and ICS ROMS but everytime i extract them, there's this error: zip error unexpected error end of archive
i really need some help guys, thank u and ur efforts are very much appreciated..
frostbyte007 said:
Sorry if this may or may not be another noob thread but my HOX is stuck in looping splash screen. I have installed CWM and i can still access bootloader. I have not yet flashed any ROM (still on stock) because i was stuck on this when i tried.
my HOX is unlocked as well.
one thing more, i downloaded 2-3 times JB and ICS ROMS but everytime i extract them, there's this error: zip error unexpected error end of archive
i really need some help guys, thank u and ur efforts are very much appreciated..
Click to expand...
Click to collapse
2 things you should try:
Flash TWRP not CWM, TWRP is better in my opinion, and can make it much easier when using the recovery.
Re-download the ZIP and if possible compare the MD5/CheckSUM's to see if they match
Also, are you making sure your flashing the correct boot.img after flashing the ROM?
for a start, the zips aren't meant to be unzipped... secondly can you actually enter the recovery?
Wilks3y said:
2 things you should try:
Flash TWRP not CWM, TWRP is better in my opinion, and can make it much easier when using the recovery.
Re-download the ZIP and if possible compare the MD5/CheckSUM's to see if they match
Also, are you making sure your flashing the correct boot.img after flashing the ROM?
Click to expand...
Click to collapse
tried redownloading the roms and still the same error/s pops up., i dont know if its just in my laptop so right now im using a different unit to see if i can successfully get what i want.,
im successful in flashing the boot.img as well coming from the same ROM., the ROMs don't install., there's something about "zip...bad" then the installation aborts, that's when i tried extracting those that i downloaded and the zip extract errors appear., i believe (if not mistaken) zips can always be unzipped, there shouldn't be any errors at any case right?
by the way, thanks to both of you for your immediate response..
360nitrous said:
for a start, the zips aren't meant to be unzipped... secondly can you actually enter the recovery?
Click to expand...
Click to collapse
yes sir, i can go to recovery., i can flash twrp or cwm.,
frostbyte007 said:
tried redownloading the roms and still the same error/s pops up., i dont know if its just in my laptop so right now im using a different unit to see if i can successfully get what i want.,
im successful in flashing the boot.img as well coming from the same ROM., the ROMs don't install., there's something about "zip...bad" then the installation aborts, that's when i tried extracting those that i downloaded and the zip extract errors appear., i believe (if not mistaken) zips can always be unzipped, there shouldn't be any errors at any case right?
by the way, thanks to both of you for your immediate response..
Click to expand...
Click to collapse
No worries, as stated mate the ZIP shouldn't even be un-zipped. It should be downloaded, placed on the device and then flashed from your recovery or by sideloading it using ADB.
Also, are you using WinRAR? If not get WinRAR from Rarlab.co.uk
That may help.
Let us know how you get on
Wilks3y said:
No worries, as stated mate the ZIP shouldn't even be un-zipped. It should be downloaded, placed on the device and then flashed from your recovery or by sideloading it using ADB.
Also, are you using WinRAR? If not get WinRAR from Rarlab.co.uk
That may help.
Let us know how you get on
Click to expand...
Click to collapse
ok sir thanks., example for the viper ROM (i cant post in their thread yet coz i have less than 10 posts atm) it said there that i should extract the boot.img inside the ROM., did i read that right?
most of the ROMs in ICS dont have separate boot.img where can i get them?
thanks everyone for all the responses., I'm way past the zip problem.,darn wasted so much time redowloading the ROMs.,
gonna flash my device later on to see if everything will be fine., ^^
frostbyte007 said:
thanks everyone for all the responses., I'm way past the zip problem.,darn wasted so much time redowloading the ROMs.,
gonna flash my device later on to see if everything will be fine., ^^
Click to expand...
Click to collapse
Great, what was your resolution for the ZIP Problem?
And yes, you should take the boot.img out, as thats flashed separately in order to actually boot the Phone.

Both CM9/CM10 hangs at boot.

My procedure in chronological order:
Flashed recovery TWRP 2.3
Wiped everything possible in the wipe-tab
Installed CM9/10 from zip on SD-card (zip contains META-INF, system and boot.img)
Flashed boot.img from the zip file CM9/10
Issued the command fastboot erase cache
Unplugged cable and reboot
What happens is that I am stuck at the HTC booting screen. I have been here for about 30-40 minutes. If I try any adb shell command I receive this error: - exec '/system/bin/sh' failed: No such file or directory (2) -. Clearly, something is not right here. I will not speculate because I lack the knowledge to do so. Any help is appreciated because I have been phone-less for a day now and it is getting irritating. Thanks!
Seems you did everything correctly.
Try to flash via ClockWorkMod recovery.
Sent from my HTC One X
TToivanen said:
Seems you did everything correctly.
Try to flash via ClockWorkMod recovery.
Click to expand...
Click to collapse
I just did the same procedure as before but with clockworkmod instead. Still hung at booting screen. I get the same error as before. Is root access a must? I have not done any exploit, only thing I have done is unlocked my boot loader at HTCDev.
zettez said:
I just did the same procedure as before but with clockworkmod instead. Still hung at booting screen. I get the same error as before. Is root access a must? I have not done any exploit, only thing I have done is unlocked my boot loader at HTCDev.
Click to expand...
Click to collapse
Root should not be needed since most roms are rooted by default.
Did you flash gapps?
TToivanen said:
Root should not be needed since most roms are rooted by default.
Did you flash gapps?
Click to expand...
Click to collapse
No, I have not. Maybe I should give it a try? Or is it not required? Should I not be able to start the phone without any gapps?
Do you by chance have any ROM you can recommend that works so I could try it out and exclude problems? Would very like to know if it is my phone or ROM that is buggy.
It should boot without them, but better to give it a try.
Ironically, I've been using CM10 for more than a month now and never had any problems booting.
Sent from my HTC One X
If you have an hboot newer than 1.12 you need a different boot.img, check the bottom if the ROM OP.
TToivanen said:
It should boot without them, but better to give it a try.
Ironically, I've been using CM10 for more than a month now and never had any problems booting.
Click to expand...
Click to collapse
Would you mind telling me which CM10 build you are using and which boot.img you flashed?
BenPope said:
If you have an hboot newer than 1.12 you need a different boot.img, check the bottom if the ROM OP.
Click to expand...
Click to collapse
I have hboot 1.3 or something I think. I downloaded the different builds at get.cm. Where can I get the boot.img if not the one in the zip file? Do you mean whichever thread that CM have posted themselves here on xda? Would you mind sending a link to where I can find the boot.img?
zettez said:
I have hboot 1.3 or something I think. I downloaded the different builds at get.cm. Where can I get the boot.img if not the one in the zip file? Do you mean whichever thread that CM have posted themselves here on xda? Would you mind sending a link to where I can find the boot.img?
Click to expand...
Click to collapse
Normally it would be found in the bottom of CM10 threads OP but the link is down.
Here you go:
http://forum.xda-developers.com/showpost.php?p=34829297&postcount=9173
Remember to repack it with the one found in zip. Repack tool stickied on android development forum.
Sent from my HTC One X
TToivanen said:
Normally it would be found in the bottom of CM10 threads OP but the link is down.
Here you go:
http://forum.xda-developers.com/showpost.php?p=34829297&postcount=9173
Remember to repack it with the one found in zip. Repack tool stickied on android development forum.
Click to expand...
Click to collapse
Thanks, but still a no go. What I did was take the modified boot from your link and the boot.img from the zip file, do the online converter as stickied on the forum, then did the procedure all again but this time I flashed the new boot.img I got from combining the old and the new boot.img. Still hangs at boot. Very annoying. I am currently using a modified stock ROM and I dislike it very much.
Hey,
I have exactly the same issue. I've unlocked my bootloader using the method as specified by htcdev.com. Then I flashed the newest CWM recovery. But if I flash any ROM, I'm stuck at its boot animation. However if I then unzip the boot.img from the ROM, and flash that (fastboot flash boot boot.img), my phone won't boot past HTC screen. Even erasing the cache didn't help (fastboot erase cache).
I've restored the stock ROM using the RUU, however during the process something went wrong and it formatted my sd-card. So I'm stuck with the stock ROM, without any applications or data.
Can anybody help me flash CM10?
My Hboot version is 1.36.0000
And I'm trying to flash the cm-10-20121210-NIGHTLY-endeavoru.zip ROM.
Thanks in advance
Han
irundaia said:
Hey,
I have exactly the same issue. I've unlocked my bootloader using the method as specified by htcdev.com. Then I flashed the newest CWM recovery. But if I flash any ROM, I'm stuck at its boot animation. However if I then unzip the boot.img from the ROM, and flash that (fastboot flash boot boot.img), my phone won't boot past HTC screen. Even erasing the cache didn't help (fastboot erase cache).
I've restored the stock ROM using the RUU, however during the process something went wrong and it formatted my sd-card. So I'm stuck with the stock ROM, without any applications or data.
Can anybody help me flash CM10?
My Hboot version is 1.36.0000
And I'm trying to flash the cm-10-20121210-NIGHTLY-endeavoru.zip ROM.
Thanks in advance
Han
Click to expand...
Click to collapse
You cannot use the boot.img that comes with the zip out of the box if you have Hboot 1.36. What you have to do is repack it, taking the boot.img from the zip file and then a modified boot.img here http://forum.xda-developers.com/show...postcount=9173 (thanks TToivanen), then as I understood it, repack it for instance here http://forum.xda-developers.com/showthread.php?t=1815607, download the repacked boot.img and flash that.
With that said, I could not get it running but it might be something wrong with my phone. Please try this out and tell me if it works or not so I may start to conclude where the error lies.
zettez said:
Thanks, but still a no go. What I did was take the modified boot from your link and the boot.img from the zip file, do the online converter as stickied on the forum, then did the procedure all again but this time I flashed the new boot.img I got from combining the old and the new boot.img. Still hangs at boot. Very annoying. I am currently using a modified stock ROM and I dislike it very much.
Click to expand...
Click to collapse
Sorry, but all I can say is that you did a mistake at some point.
Try installing again with full wipe and remember to wipe cache and dalvik.
You are referring to the official CM10 and not Trip's or any other builds right?
TToivanen said:
Sorry, but all I can say is that you did a mistake at some point.
Try installing again with full wipe and remember to wipe cache and dalvik.
You are referring to the official CM10 and not Trip's or any other builds right?
Click to expand...
Click to collapse
Will try again. I got the latest build from http://get.cm/?device=endeavoru. Will try cm-10-20121213-NIGHTLY-endeavoru.zip as it came out today.
zettez said:
You cannot use the boot.img that comes with the zip out of the box if you have Hboot 1.36. What you have to do is repack it, taking the boot.img from the zip file and then a modified boot.img here http://forum.xda-developers.com/show...postcount=9173 (thanks TToivanen), then as I understood it, repack it for instance here http://forum.xda-developers.com/showthread.php?t=1815607, download the repacked boot.img and flash that.
With that said, I could not get it running but it might be something wrong with my phone. Please try this out and tell me if it works or not so I may start to conclude where the error lies.
Click to expand...
Click to collapse
I did that and now my phone is still stuck on the HTC screen. Trying to restore my backup of the stock ROM atm.
---------- Post added at 04:35 PM ---------- Previous post was at 04:30 PM ----------
hmm the backup was useless... Off to the RUU it is....
irundaia said:
[/COLOR]hmm the backup was useless... Off to the RUU it is....
Click to expand...
Click to collapse
You flashed the stock boot.img before restoring?
irundaia said:
I did that and now my phone is still stuck on the HTC screen. Trying to restore my backup of the stock ROM atm.
Click to expand...
Click to collapse
I see, then it is not only I who have this problem.
And a heads up, if the backup would go wrong, I currently use this ROM and it works pretty good if you want stock or cannot be arsed to get a root exploit for the stock ROM. http://forum.xda-developers.com/showthread.php?t=2035203.
Would be great if anyone has any ideas why irundaia and I cannot make CM10 work?
TToivanen said:
You flashed the stock boot.img before restoring?
Click to expand...
Click to collapse
You're right, I forgot to do that. I does boot now, still at a loss though. Can't we downgrade our Hboot to a version in which we know that CM can be flashed?
Kinda out of ideas here...
Can you confirm that the boot.img flashes ok? (should say OKAY)
Also confirm that you have endeavoru and not evita.

One X stuck at "HTC ONE X"

ok im truely frustrated after trying to figure this out in past 2 days and reading more than 60 threads/websites.
Problem:
my one x was running 4.0.4 rooted +supre user+CWM, till i got the notification for 4.1 update. i pressed install now and downloaded around 380 MB, during the update phase a red exclamation icon appeared and phone rebooted into 4.0.4.
relocked bootloader, flashed stock recovery and downloaded it again and this time copied the OTA file before pressing install. so i installed and same issue.
uninstalled Avast AV (android) and ran through the same process again, same thing, started up into 4.0.4 again.
unlocked the bootloader, flashed CWM 5.8.4, copied ota file into phone and renamed it to update.zip. ran it from recovery menu and got status 7 error.
downloaded and ran JBFWTOOL21 and followed the instructions, during one of the steps i encountered an error and after restarting the phone i was stock at "HTC One x" with "beatsound" logo at bottom.
NOW NOTHING WORKS
what ive tried so far:
relocked loader and flashed stock recovery and tried Factory Reset, no luck.
unlocked loader and flash CWM and tried wiping cache and wiping disk. nothing.
relocked loader,flashed recovery and ran stock RUU "RUU_ENDEAVOR_U_ICS_40_HTC_ARA_1.28.415.9_Radio_1.1204.103.14_release_25679_signed" but it doesnt work, give an error related to version numbers or something.
extracted system.img, boot.img from RUU temp folder ROM.zip and tried to flash but cant flash system.img (918mb). something about not enough HEAP i think.
from the OTA JB zip extracted recovery.img, boot.img and recovery.img and flashed them. nothing.
downloaded "One_X_All-In-One_Kit_v2.1" and tried kernel flash, nothing.
clearing cache via fastboot command also doesnt work
really appreciate any helpful input guys, im really frustrated. thanks
Oh my.. First, stop unlock and relock of bootloader. Do you have a cwm backup from before all this started? Flashing cwm and restoring that backup will get you far.
The first ota attempt failed due to cwm, always return to stock recovery (recovery.img from your cwm backup image) before applying ota update!
Kind Regards
TwinAdk
unfortunately, no. no backup.
since it all started from the official update i didnt make any backups.
Stop trying flash randomly. Run the following command:
fastboot getvar version-main
it wasnt just random flashing, i starting reading different posts and so tried them all one-by-one to see which works, anyway the output:
version-main: 3.16.415.4
woomera said:
it wasnt just random flashing, i starting reading different posts and so tried them all one-by-one to see which works, anyway the output:
version-main: 3.16.415.4
Click to expand...
Click to collapse
Well that's why the older RUU wouldn't work. You have the latest.
You'll need to go to the ROM backups thread and see if you can get a backup and flash its boot.img and restore it from CWM.
Actually, reboot your PC and try to flash system.img and boot.img again. You will probably need to be locked.
but isnt that the boot.img from "OTA_ENDEAVOR_U_JB_45_S_HTC_ARA_3.16.415.4-2.17.415.2_release_304331jrfus698taf4vm1x"?
cause i have already tried it, didnt work. i have the OTA file.
Modified my post. Look up.
i have boot.img from firmware with hboot 3.16 and 3.19, which one to use?
and the system.img is from stock RUU which is "RUU_ENDEAVOR_U_ICS_40_HTC_ARA_1.28.415.9_Radio_1.1204.103.14_release_25679_signed", will that work?
the OTA JB is a zip file and doesnt have system.img.
Err.. 1.39?
yes
the firmware included in "JBFWTOOL21" is 1.36 which is used by many to manually upgrade to JB but the firmware inside the OTA file itself is 3.19 which is also the version i updated to since i thought its the reason the update doesnt work.
the Hboot version on my phone is 1.39 at the moment.
Hmmm. Looks like you'll have to find a backup in the backups thread and flash it.
BenPope said:
Hmmm. Looks like you'll have to find a backup in the backups thread and flash it.
Click to expand...
Click to collapse
i dont understand, a backup of what? the system.img?
Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?
sridheepan said:
Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?
Click to expand...
Click to collapse
I thought about suggesting that too, but I'm new to flashing so I didn't feel confident enough to do it..
But off the top of my head, a custom rom, complete with boot.img and everything should work..
I'm using http://forum.xda-developers.com/showthread.php?t=2013506, it's super great and support all hboot versions.
No guarantees it will work though.
Kind Regards
TwinAdk
sridheepan said:
Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?
Click to expand...
Click to collapse
guess it worth a try even though i'd rather fix the problem in hand in another fashion.
gonna give it a try and post the results.
k so i downloaded the Blade rom and it worked, thanks "TwinAdk".
so now about JB. should i just use "JBFWTOOL21" or better if i do it manually?
and is this the right order to do it manually: ?
-unlock bootloader
-flash CWM
-flash boot.img
-install from zip in CWM
woomera said:
i dont understand, a backup of what? the system.img?
Click to expand...
Click to collapse
A nandroid backup, like what Clockworkmod recovery makes.
woomera said:
k so i downloaded the Blade rom and it worked, thanks "TwinAdk".
so now about JB. should i just use "JBFWTOOL21" or better if i do it manually?
and is this the right order to do it manually: ?
-unlock bootloader
-flash CWM
-flash boot.img
-install from zip in CWM
Click to expand...
Click to collapse
NP, glad it worked! So now you have a phone that can actually boot up and make phone calls.. Not on the stock rom you wanted, but it's better than when you started this thread
From this point on, you can use a "return to stock" thread for the HOX.
1. Make a NANDROID backup via CWM (so you can get back to what you have now!)
2. Move the backup to your computer, to avoid anything happening to it
3. See this tutorial ([TUT] Getting back to stock after flashing custom roms [Noob friendly])
NOTE: The thread says the following in the top:
NOTE: These instructions require that you have one of the ICS hboot versions in order to work (1.12.0000 or lower). If you have one of the new JB hboots 1.28, 1.31 or 1.33 there is currently no way to return to stock until a JB ruu is released for your device.
Click to expand...
Click to collapse
The "new jb hboots" also refers to 1.39.
I have the 1.39 myself, and i believe i am able to return to stock via my CWM backup of my stock phone, from before i flashed a custom rom the first time.. Is that assumption wrong? Someone more experienced than me to the rescue, please
Kind Regards
TwinAdk
BenPope said:
A nandroid backup, like what Clockworkmod recovery makes.
Click to expand...
Click to collapse
thanks for the clarification
TwinAdk said:
NP, glad it worked! So now you have a phone that can actually boot up and make phone calls.. Not on the stock rom you wanted, but it's better than when you started this thread
From this point on, you can use a "return to stock" thread for the HOX.
1. Make a NANDROID backup via CWM (so you can get back to what you have now!)
2. Move the backup to your computer, to avoid anything happening to it
3. See this tutorial ([TUT] Getting back to stock after flashing custom roms [Noob friendly])
NOTE: The thread says the following in the top:
The "new jb hboots" also refers to 1.39.
I have the 1.39 myself, and i believe i am able to return to stock via my CWM backup of my stock phone, from before i flashed a custom rom the first time.. Is that assumption wrong? Someone more experienced than me to the rescue, please
Kind Regards
TwinAdk
Click to expand...
Click to collapse
i have read the same thing, also "BenPope" mentioned it. so with this version of Hboot (1.39) i cant restore unless its a nandroid backup.
but i dont wanna go back to stock ICS! i wanna finish what i was trying to do in first place, Upgrade to JB.
but no matter what i do i get the "status 7 error". i have tried it with the OTA my phone downloaded and also downloaded it again directly from HTC website via a link from one of the threads in forum.
so status 7 apparently is related to CRC error but how can that be? and what is my option right now to do the upgrade? also bear in mind that before all these happened the normal upgrade process via the "system update" also failed with a red icon error.

[Recovery] TEST BUILDS AT&T Fusion 2 CWM

I have built a CWM recovery image for the AT&T Fusion 2. If anybody would like to test it out, here is the link.
http://jenkins.cyanogenmod.com/job/recovery/18266/
Doesn't work:
Basically everything. You can only boot into CWM, and scroll using the Volume keys, but you can't select anything.
WiFi glitches on first reboot. To get WiFi working again, forget the connected WiFi network, and disable WiFi, then reboot.
NOTE: I have personally flashed this recovery image, and works, but FLASH AT YOUR OWN RISK. Enjoy! :cyclops:
Built second test build!
RoboticBuddy said:
I have built a CWM recovery image for the AT&T Fusion 2. If anybody would like to test it out, here is the link.
http://jenkins.cyanogenmod.com/job/recovery/18266/
NOTE: I have not personally flashed this recovery image as of now, so FLASH AT YOUR OWN RISK. Enjoy! :cyclops:
Click to expand...
Click to collapse
Flashed the img I am able to scroll up and down in CWM but not select anything. I went ahead and make a second build using recovery.img and the fstabs file. Still no more functionality, so I am searching for the graphics.c file and the postrecoveryboot.sh file.. I cannot find them.. YET
here is my version of the second build for the fusion 2 https://www.dropbox.com/s/r281aa12zko1brr/recovery.img try it with the installador tools from the fusion 1! (i will write a guide later..)
Anyone have any advice on how to find the files? I am guessing they are needed to get CWM working. This is my first build though, and any help will be GREATLY appreciated.
Just built my second build and third total for the fusion 2. The second worked fine, but not any better than the first. The third wouldn't boot into recovery. The third incorporated what I thought was the postrecoveryboot.sh
Shagerty said:
Flashed the img I am able to scroll up and down in CWM but not select anything. I went ahead and make a second build using recovery.img and the fstabs file. Still no more functionality, so I am searching for the graphics.c file and the postrecoveryboot.sh file.. I cannot find them.. YET
here is my version of the second build for the fusion 2 https://www.dropbox.com/s/r281aa12zko1brr/recovery.img try it with the installador tools from the fusion 1! (i will write a guide later..)
Anyone have any advice on how to find the files? I am guessing they are needed to get CWM working. This is my first build though, and any help will be GREATLY appreciated.
Just built my second build and third total for the fusion 2. The second worked fine, but not any better than the first. The third wouldn't boot into recovery. The third incorporated what I thought was the postrecoveryboot.sh
Click to expand...
Click to collapse
I have been searching for those files as well, but being new to this, I don't know what they are used for
And your own build of CWM, isn't it the same thing as mine?
And you can just flash it over to the phone using fastboot; "fastboot flash recovery recovery.img". . . .
RoboticBuddy said:
I have been searching for those files as well, but being new to this, I don't know what they are used for
And your own build of CWM, isn't it the same thing as mine?
And you can just flash it over to the phone using fastboot; "fastboot flash recovery recovery.img". . . .
Click to expand...
Click to collapse
In the second build I used the recovery.img and fstabs files. No more functionality. Third build I used the recovery.img and the fstabs and what I thought was the postrecoveryboot.sh. it wouldnt load on the third build.
I found a tool that pushes the recovery.img files with the click of a button.
Thanks guys!
Hey guys it's great that you two are working on a CWM recovery for this 'not very well known' device. I would love to help, if you need me to do anything just ask! My brother is getting into some more development with his device (Galaxy Player 4.2) and he might be able to help, I'm not a developer but I could start learning . Anyways, will you guys be able to build a CM10/JB for this device?
I am certainly shooting for it! But am in the same boat! I'm just getting into developing. Learning java code right now but I am just scratching the surface.. I would greatly appreciate your assistance as much or as little as you know the help is awesome! Like you said it is a little known device. We need all the help we can get!
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
CenterTurkHD said:
Hey guys it's great that you two are working on a CWM recovery for this 'not very well known' device. I would love to help, if you need me to do anything just ask! My brother is getting into some more development with his device (Galaxy Player 4.2) and he might be able to help, I'm not a developer but I could start learning . Anyways, will you guys be able to build a CM10/JB for this device?
Click to expand...
Click to collapse
I'm too busy with school to start learning Android development, so I just can't really work on this device that often.
First of all, we need a working CWM before we can move on to ROM development.
Thanks for your future help!
Sounds great
Wow, sounds great guys! And I will keep completely up to date with this. I am also busy with school, but I do have time at home to do things with this [project]. I'll post and keep you guys updated if I can find or improve on anything!

HTC One X brick? Help me

Today i tried to install this crappy Custom Rom http://forum.xda-developers.com/showthread.php?t=1705334&highlight=bootloop Renovate 1.1 i installed 2 other Roms before and all of those was succesfully , then i tested this and i got into a bootloop , so i restored my backup , this bootloops too and the 2 other roms bootloop too , i tried so much things now i can go to bootloader but its Relocked Security Warning what can i do?
go0dlife said:
Today i tried to install this crappy Custom Rom http://forum.xda-developers.com/showthread.php?t=1705334&highlight=bootloop Renovate 1.1 i installed 2 other Roms before and all of those was succesfully , then i tested this and i got into a bootloop , so i restored my backup , this bootloops too and the 2 other roms bootloop too , i tried so much things now i can go to bootloader but its Relocked Security Warning what can i do?
Click to expand...
Click to collapse
Unlock the bootloader, go to adb/fastboot folder and store your ROM's boot.img there. Shift + Right Click within that folder and Open command window (be in fastboot mode on your phone in the meantime) :
fastboot flash boot boot.img
fastboot erase cache
Go to recovery, wipe all except SD (you can if you don't need your files) and flash a fresh ROM. Also, lock the bootloader and never ever flash any custom ROM again if you're going to call it crap whenever you fail.
edit: it isn't that easy to brick the device, and finally, your topic doesn't belong in this subforum.
how to update hboot version? i need 1.31
ok i unlocked now i have hboot 1.12.0000
but i cant install the rom i followed your instruction and get bootloop..
go0dlife said:
Today i tried to install this crappy Custom Rom http://forum.xda-developers.com/showthread.php?t=1705334&highlight=bootloop Renovate 1.1 i installed 2 other Roms before and all of those was succesfully , then i tested this and i got into a bootloop , so i restored my backup , this bootloops too and the 2 other roms bootloop too , i tried so much things now i can go to bootloader but its Relocked Security Warning what can i do?
Click to expand...
Click to collapse
The rom is crap because it didn't work or because you don't have a clue what your doing? It's not nice to say the roms crap when so many people have used without problem and without a doubt the problem will be down to you. People put a lot of time and effort into roms for free so try to be more respectful.
Sent from my Nexus 7 using Tapatalk 2
Agree
As previously said - These guys are all doing soooo much work for us (the community) and it's NOT paid - anyone who makes a ROM, ANYONE - needs to be applauded even for trying, but I'm sure that most ROM chefs test their roms to a point before releasing them and that you've probably missed a step or flashed incompatible zips or something...
Did you extract the boot.img from the roms zip file and "fastboot flash boot boot.img" it? It sounds like you might have been playing with ROMS which all worked on the same kernel and now you've flashed one which uses a different one, resulting in a bootloop like you say - I'm a noob and have done this a few times. Boot into bootloader, fastboot flash your boot.img, then boot into recovery and flash the rom (factory reset / wipe all data / cache / dalvik) and you might be lucky enough to boot into the rom!
These steps MAY not fix your problem if it is something else - but from my experience they are not steps which will brick your device, if you don't think you've flashed the boot.img - then I'd start there.
With our HOX's you ALWAYS need to remember (ALWAYS ALWAYS ALWAYS) to flash (in fastboot mode) your boot.img (which is 99% of the time, included inside the roms ZIP file...
Hope I've helped!
(Hit thanks if I did! )
Before saying those "crappy" words to the rom. Read alot first. All the answers are in the forum. Rom chefs dedicate time to cook a good rom.
Sent from my HTC One X using xda app-developers app
Guys......its not the rom, its not the boot.img.........surprise ! Its his hboot (1.12)
Get that updated otherwise it will never run.
And please loose the attitude towards roms that don't boot. They all boot but check the requirements first
Its your phone/hboot that does not support it
AW: HTC One X brick? Help me
http://m.youtube.com/#/watch?v=wwleOote5M0&desktop_uri=/watch?v=wwleOote5M0&gl=DE

Categories

Resources