[Q] Help need to restore hboot - G2 and Desire Z Q&A, Help & Troubleshooting

Tried to change to the desire-z hboot to add extra space when running kitkat 4.4.2. Used the PC10IMG.zip file in developer forum.
It replaced the hboot and the radio, plus the recovery.img. The recovery.img was from 3.0.2.4. Before running the PC10IMG.zip I was using
the latest Clockwork Recovery file. Needles to say the phone won't boot. I need to make a PC10IMG.file that will replace the files
that were in the in the original files on the phone. Needless to say I can't us ADB because that fastboot is not working. I tried update files
form earlier versions(PC10IMG.Zip), they didn't work because hboot was different and I got a version error. Got any suggestions where I can
some later .img files to restore the bad ones.
Thanks,
Clyde

boot into recovery and write down everything from that screen here

Restore prceedure
Clyde909 said:
Tried to change to the desire-z hboot to add extra space when running kitkat 4.4.2. Used the PC10IMG.zip file in developer forum.
It replaced the hboot and the radio, plus the recovery.img. The recovery.img was from 3.0.2.4. Before running the PC10IMG.zip I was using
the latest Clockwork Recovery file. Needles to say the phone won't boot. I need to make a PC10IMG.file that will replace the files
that were in the in the original files on the phone. Needless to say I can't us ADB because that fastboot is not working. I tried update files
form earlier versions(PC10IMG.Zip), they didn't work because hboot was different and I got a version error. Got any suggestions where I can
some later .img files to restore the bad ones.
Thanks,
Clyde
Click to expand...
Click to collapse
Found a file cwmr_6045_vision.PC10IMG.zip (used Google). Deleted every char before PC in file name and wrote file to SDrom then rebooted
and was able to get into recovery and recovered from there.
This might be a plan for those who can't get anything to work.
Thanks,
Clyde

I meant to say write all info from bootloader not recovery, but anyway glad its working
(Future reference be careful flashing random PC10IMG.zips, they can lead to a quick a brick)
Sent from my Nexus 7 using XDA Premium 4 mobile app

Related

Wildfire ROM update - backup questions

Hi everyone,
I'm using a HTC Wildfire and am considering changing from stock (HTC non-branded) to CyanogenMod for a number of minor reasons. Could anyone just confirm that I got a few points right before I get started:
- Recovery is totally independent from the ROM itself, right? So I can flash ClockWorkMod Recovery only, continue to use the stock ROM, but have the additional features of ClockWorkMod available, such as backup, with which I can create a complete backup of the stock ROM. In case I don't like CyanogenMod, I can restore the stock image and be exactly where I left it, Apps, Settings and everything (of course the new Recovery will still be installed.) Is this correct?
- I'm planning to do the following steps (I read about the details, just want to confirm the basics):
x use the Revolutionary way to S-OFF and install new Recovery
x create full image backup of the stock ROM using the new Recovery
x install new ROM (ClockWorkMod)
x if I don't like CM: restore image created before to return to stock
-> This should work, shouldn't it?
- One more: What will happen if the the phone is S-OFF, an alternative Recovery is installed, and a HTC Firmware-Update is attempted? Will this work at all, will it update just the ROM, or will it update the Recovery, too? S-OFF will not be changed back to S-ON, right?
Thanks for your help.
Regards
1. Yes, the recovery is in it's own partition and is independent from the ROM
2. The recovery creates a "snapshot" of your current ROM. So when you restore, it'll be just the way you left it.
3. There's no need to do any HTC Firmware updates after installing a custom ROM (infact, I'm almost 100% sure that it won't work)
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
As for HTC firmware update question,if your talking about the over the air updates I'm not sure but I think it would update your hboot thus reverting back to s-on status again so best not accept it if you do get one (turn off in settings)
Edit : ninja'd lol
Sent from my HTC Wildfire using XDA App
slymobi said:
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
Click to expand...
Click to collapse
Yes, of course.
As for HTC firmware update question,if your talking about the over the air updates [...]
Click to expand...
Click to collapse
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
150d said:
Yes, of course.
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
Click to expand...
Click to collapse
Ah sorry never dealt with any firmware updates. There are ruu.exe to help get back to stock if something goes wrong I think.
Sent from my HTC Wildfire using XDA App
You can go completely back to stock, s-on and all but believe me once you have cwm installed there really is no point unless its for warranty reasons, backup fails are rare with the latest recoveries + if it does fail with your first backup you can always post here and we will explain how to extract a stock Rom from an ruu to put things back to how they where before or you can flash a custom sense Rom and modify it to your liking.
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
You can go completely back to stock, s-on and all
Click to expand...
Click to collapse
That's great.
[...] but believe me once you have cwm installed there really is no point unless its for warranty reasons[...]
Click to expand...
Click to collapse
Yea, exactly. I'm a little on the paranoid side, I know... ;-)
Ok, I'm on my way now. I've performed the "Revolutionary" S-OFF and am now running "Revolutionary CWM v4.0.1.4". Is this an out-of-date version?
I've read about ROM-Manager being able to auto-check for and flash a new Clockworks Recovery, but I've also read that ROM-Manager needs root. I have not yet flashed a new ROM, so I assume that I'm not yet rooted, am I? Can I find a ZIP of CWM that I can directly flash from the SD-card?
Does the CWM-version I'm running have any effect on the "quality" of the image backup? In other words, if I create a backup now, will I be able to restore it later running a different version of CWM?
The "different version backup restore" is a bit wonky and won't always work.
To flash a different recovery from the SD card do this:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
2. Boot into the bootloader
3. Wait a bit and then it should prompt you to update
4. Click the volume+ key to update
5. Remove SD card
6. Boot into the new recovery and insert the SD card
7. Go under mounts and select Mount USB storage
8. Delete the PCIMG file from your computer
nejc121 said:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
Click to expand...
Click to collapse
I tried to, but I couldn't use the link. The whole domain seems to be down - maybe another holy crusade of Big Content, who knows. They sure leave fans in their wake, don't they.
Since you indicated that updating would be ok for the wildfire I went to http://www.clockworkmod.com/rommanager and downloaded the file recovery-clockwork-5.0.2.0-buzz.zip.
However, I'm not sure how to handle it: If I put it on the card under this name, nothing happens on bootloader-start. In recovery, I can select the file and install it, and then I immidiatly get a newly colored menu with the new CWM version 5.something. However, once I restart, the old CWM (v4.x) is there again.
I assume I need to use a magic filename so that the bootloader performs the update, not the (already running) recovery. Right?
**EDIT: Ah, disregard. I believe I found the answer myself.
Do you have fastboot?
If you do I can give you the recovery.img I'm using, which you can flash via fastboot.
Yes, fastboot is available.
Thank you.
Okay, here's how you flash a recovery via fastboot.
1. Extract the .zip I attached to the location where you fastboot is
2. Reboot phone in the bootloader
3. Select fastboot and attach USB cable
4. Open up the command prompt and type in "cd [location of fastboot]
5. Type in "fastboot flash recovery recovery.img"
6. You're done
Oh and by [location of fastboot] I mean that you type in the location of fastboot.
Wow - this was fun. There was something really curious going on with my device: Whatever I tried, no "official" way worked to modify CWM v4 to v5. In every case, the menu of the new version showed up and was usable, but was gone again after restart. After the file-on-card method got me nowhere (file was not recognized), I tried the high road and installed ROM-Manager. This complained about missing su. So I installed su. After that ROM-Manager downloaded CWM v5 and put it onto the card (into a file named update.zip - ahh... ) On restart, the CWM-install-screen came up, then the v5 menu.
And after restart, it was gone again. Even ROM-Manager was confused: He showed v5 as "installed", when in fact it was still v4. ;-)
So finally I downloaded the Android SDK (to get fastboot.exe) and performed the flash as you suggested in the first place. And it worked. First try, without hitch, permanently.
Thank you very much for your help!
Regards
The problem with ROM Manager's version is that it's only temporary and can only be accessed from the ROM Manager itself

Sprint Restore To Stock! (Nandroids CWM+TWRP & Recovery IMG)

Forget to make a backup before trying to flash a rom?
Need to return your phone to sprint?
TWRP NANDROID
Unzip then Place these in your TWRP Folder by using ADB (lookup your standard ADB guide) Then restore the nandroid
CWM NANDROID
Unzip then place in your CWM folder sub folder backups then boot to clockwork mod and restore
Stock Recovery Image
use this while in fastboot mode (hold vol up + down + power while phone is off) then on your computer issue cmd fastboot flash recovery recovery.img (search for how to setup adb)
Need Help Rooting? How To Videos Thanks to QBking77!
Need More Help? Join the IRC channel!
Coming Soon:
Radio Fix (if you flashed a verizon radio)
If this helped Donate To Me
Updated with CWM Nandroid and Stock Recovery Image
Sweet thanks
Sent from my Galaxy Nexus using Tapatalk 2
thanks to raiderep for giving me the stock recovery
Well Thanks Let the flashing begin ;P
Here is a link for the drivers from Samsung as well maybe helpfull
http://www.samsung.com/us/support/owners/product/SPH-L700ZKASPR
its the exe file and works well
thanks.. ill get how to videos up soon
qbking77 said:
thanks.. ill get how to videos up soon
Click to expand...
Click to collapse
You a good guy, so is OP.
added thanks to all the guys over on the IRC channel
shabbypenguin said:
thanks to raiderep for giving me the stock recovery
Click to expand...
Click to collapse
Glad to help when I can as always, go android!
Sent from my Galaxy Nexus
Im using twrp rec.
I dont like/trust twrp recovery, where can i get a sprint compatible cwm recovery?
Sent from my Xoom using XDA Premium HD app
malibu_23 said:
Im using twrp rec.
I dont like/trust twrp recovery, where can i get a sprint compatible cwm recovery?
Sent from my Xoom using XDA Premium HD app
Click to expand...
Click to collapse
We do the CWM for the verizon version is the one that works......
What if...
Wordlywisewiz said:
Forget to make a backup before trying to flash a rom?
Need to return your phone to sprint?
TWRP NANDROID
Unzip then Place these in your TWRP Folder by using ADB (lookup your standard ADB guide) Then restore the nandroid
Click to expand...
Click to collapse
What if I tried to use twrp recovery and now my phone refuses to activate. It says there is no sim card installed. I called sprint and they can't make it happen over the phone. They want me to come into the store, but i suspect that it isn't going to work their either. Any suggestions?
Thanks guys!
turbo2125 said:
What if I tried to use twrp recovery and now my phone refuses to activate. It says there is no sim card installed. I called sprint and they can't make it happen over the phone. They want me to come into the store, but i suspect that it isn't going to work their either. Any suggestions?
Thanks guys!
Click to expand...
Click to collapse
same here...says "no sim card"...WTF...
Try doing a factory data reset. Just a shot in the dark...
turbo2125 said:
What if I tried to use twrp recovery and now my phone refuses to activate. It says there is no sim card installed. I called sprint and they can't make it happen over the phone. They want me to come into the store, but i suspect that it isn't going to work their either. Any suggestions?
Thanks guys!
Click to expand...
Click to collapse
same thing has happened to my phone but not with this immage what happened is i accidently flashed a image from a verizon phone to the sprint phone and now is all kinds of messed up
my friend is currently trying to fix it for me (hes a hell of a lot smarter than i am)
ill let u know the results
Same Song.. Several Verses Later
I would really like to find out if any of you figured this out??
I find myself in the same position as I'm finding that many have on here as well. I found this thread interesting because it is dealing with the Sprint Galaxy in particular. I have hosed the radio and the baseband on the Galaxy - likely the EFS parition, not sure.. at this point. It needs to be made very clear to everyone that even has a thought of flashing with this phone to make triplicate backups of the EFS partition before they turn the phone on (exxageration for affect).
That being said - I don't think that gets the rest of us anywhere. I'm a OG owner and a Bionic owner - and the first 72 hours of Samsung ownership has felt like non-stop triage to me..
I have this here.. but this really isn't the specific image for the Sprint the phones...
The link below points to a post for the IMM761 GSM+HSPA - which I believe these phones to be identical.. and since Sprint had locked code for the CDMA versions - is this one the same - in other words, is there an image out there that can be downloaded, flashed, and from there we can we can either fix the EFS and restore IMEI folder and baseband function or at least call warranty?
At this point - I can't reset the counter on the phone, I can't take it to the store (as if the 7 iployees would know what I was talking about) and I'm not about to pay $800 to learn that the EFS partition is the "short" in the term "got you by the short hairs"..
androidforums -
Heat57 says:"
It sounds as so you are on the GSM "maguro" device. In that case I suggest you download the complete ICS 4.0.4 factory image from Google at ... file. Beware! if you have a Windows PC the original download with a .tgz extension will be renamed by Windows automatically to a .tar file, which means that you'll have problems extracting it. In that case simply rename the file by changing the extension to .tgz and all will be well. Note: you'll need the Galaxy Nexus bootloader unlocked in order to flash a factory image and at the end of the procedure you can leave it unlocked and flash a Superuser file to root, if so desired. You'll need the Android SDK installed on your PC and then copy the bootloader, radio and image .img files to your ...android-sdk\platform tools-tools folder and run the adb commands in the windows command shell (note: you must flash each image in this order and wait until each image is flashed completely >bootloader >radio > image). Finally, flash the "image-soju-imm76d.zip" through your cwm recovery. You should end up with a healthy Galaxy Nexus on ICS 4.0.4 and everything working"​
Wordlywisewiz said:
Forget to make a backup before trying to flash a rom?
Need to return your phone to sprint?
TWRP NANDROID
Unzip then Place these in your TWRP Folder by using ADB (lookup your standard ADB guide) Then restore the nandroid
CWM NANDROID
Unzip then place in your CWM folder sub folder backups then boot to clockwork mod and restore
Stock Recovery Image
use this while in fastboot mode (hold vol up + down + power while phone is off) then on your computer issue cmd fastboot flash recovery recovery.img (search for how to setup adb)
Need Help Rooting? How To Videos Thanks to QBking77!
Need More Help? Join the IRC channel!
Coming Soon:
Radio Fix (if you flashed a verizon radio)
If this helped Donate To Me
Click to expand...
Click to collapse
I think you are right but I do have cwm Also when I followed techfanatic's vid to unroot it said my phone was unrooted but the radio failed error came up. Also I am still on codeandroid. can I actually be unrooted and still be on that? Must I root again? Thanks.

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.

Help needed no network signal after root!

Hi everyone.
Yesterday I decided it was about time to root my One X and get rid of all the bloatware and nastiness that comes on the phone and open up some cool new options.
Anyway I followed this guide on how to root and install custom ROMs, as it was my first time (ok cant post the link, but its on theandroidroom.com called How to update android rev HD on htc one x)
I follwed the guide to the letter:
1) Backed up my important stuff and app data.
2) Unlocked my phone through the HTCdev bootloader online.
3) Installed ClockWorkModRecovery.
4) Copied Android revolution 19.2 across onto phone storage.
5) Cleared cache, Wiped data factory reset, Wiped dalvik cache.
6) Loaded the Android revolution.zip in recovery.
7) Went through install process.
Now when I load up the phone the ROM works fine, but I cant get any network access and I have no idea what to do?
On the android revolution page it links to firmware regarding CID numbers. I checked mine and its under the x.xx.161.x - Vodafone UK (United Kingdom) (VODAP001). I downloaded this file and tried to flash it the same way as before like the ROM. But it kept aborting.
Anyway I know im probably doing something stupid, but any help is much obliged as currently my One X is a big hunk of s***t that cant do much.
You need to flash boot.img.
Take the ROM.zip and extract the boot.img to your fastboot folder. Boot your phone to bootloader mode. Flash the image by typing fastboot flash boot boot.img
Also check that your hboot version is higher than 1.28!!
My hboot is 1.36
So I need to take my ROM as in Android Revolution 19.2 HD and extract the boot.img using winrar/7zip type program?
Kl will give it a go, thanks for the help.
Correct, let me know how it goes.
Just tried that well the only boot.img I could find was in the vodafone firmware folder, so I flashed that and it still hasnt worked, still no network access :crying:
Scrollax said:
Just tried that well the only boot.img I could find was in the vodafone firmware folder, so I flashed that and it still hasnt worked, still no network access :crying:
Click to expand...
Click to collapse
It is in root of the zip. See attachment.
Ok ROM was corrupted so couldnt find the boot.img, so downloaded it again and flashed it and it appears to have worked!!!
thanks you so much for the help your a life saver.!!!
No problem, mate!!
Remember to flash it every time you change or update your ROM.
Sent from my One X using xda premium

HTC One X Semi Bricked NEED HELP.

Hello,
Well, I was trying to install some new kernels but somehow my phone went into Boot Loop.
After that, I accidentally formatted my system and system memory. End Result: Their is nothing in my SD Card Right now.
I have searched in this forum and others for 2 days and still can not find a proper solution. Now, my laptop and computer does not recognize my device through adb device. I tried to insall stock rom through RUU but it gave an Boot Loader Version Error. However, I managed to install philz recovery and tried to mount memory but still no luck, I can not push files through adb as it can not recognize my device.
My CID is 02_001. I downloaded the matched CID RUU (RUU_ENDEAVOR_U_ICS_40_O2_UK_1.26.206.2_Radio_1.1204.90.13_release_251230_signed) but it didnt work. My image number of the phone (I dont know what is this actually) is like 4.xxxx and the image number of the RUU is 1.xxxx.
The HBOOT version is 1.72 S ON.
Can someone by someway, please give me the link of UPDATED RUU so that I can flash to stock rom or just help me to find a way to transfer custom rom to my phone memory so that I can flash a custom rom.
I was using VIPERX ROM 4.1.1,as the phone was draining alot of battery so over efficiently I tried to FLASH BRICKED KERNEL.
NOW I AM STUCK, HELPLESS and after losing the battle I am posting this thread.
PLEASE HELP ME WITH A SUITABLE ANSWER.
I would prefer to install stock rom but it wont work I guess because of the updated HBOOT version.
WaleedUQ said:
Hello,
Well, I was trying to install some new kernels but somehow my phone went into Boot Loop.
After that, I accidentally formatted my system and system memory. End Result: Their is nothing in my SD Card Right now.
I have searched in this forum and others for 2 days and still can not find a proper solution. Now, my laptop and computer does not recognize my device through adb device. I tried to insall stock rom through RUU but it gave an Boot Loader Version Error. However, I managed to install philz recovery and tried to mount memory but still no luck, I can not push files through adb as it can not recognize my device.
My CID is 02_001. I downloaded the matched CID RUU (RUU_ENDEAVOR_U_ICS_40_O2_UK_1.26.206.2_Radio_1.1204.90.13_release_251230_signed) but it didnt work. My image number of the phone (I dont know what is this actually) is like 4.xxxx and the image number of the RUU is 1.xxxx.
The HBOOT version is 1.72 S ON.
Can someone by someway, please give me the link of UPDATED RUU so that I can flash to stock rom or just help me to find a way to transfer custom rom to my phone memory so that I can flash a custom rom.
I was using VIPERX ROM 4.1.1,as the phone was draining alot of battery so over efficiently I tried to FLASH BRICKED KERNEL.
NOW I AM STUCK, HELPLESS and after losing the battle I am posting this thread.
PLEASE HELP ME WITH A SUITABLE ANSWER.
I would prefer to install stock rom but it wont work I guess because of the updated HBOOT version.
Click to expand...
Click to collapse
Flash Philz 5.15.9 recovery munt sd card and copy your rom to sd card after this install it and flash the boot.img from your rom archive
Thant said:
Flash Philz 5.15.9 recovery munt sd card and copy your rom to sd card after this install it and flash the boot.img from your rom archive
Click to expand...
Click to collapse
Ohkay, I tried the way you told me .
I have Philz Version 6.19.3 however now,
I am getting this error
asset failed: getprop('ro.product.device')=='endeavoru'
II getprop('ro.build.product')=='endeavoru' II
getprop('ro.product.board')=='endeavoru'
WaleedUQ said:
Ohkay, I tried the way you told me .
I have Philz Version 6.19.3 however now,
I am getting this error
asset failed: getprop('ro.product.device')=='endeavoru'
II getprop('ro.build.product')=='endeavoru' II
getprop('ro.product.board')=='endeavoru'
Click to expand...
Click to collapse
Man, @Thant trying to help and you skip his instructions?
Do what he said,flash philz 5.15.9.
WaleedUQ said:
Ohkay, I tried the way you told me .
I have Philz Version 6.19.3 however now,
I am getting this error
asset failed: getprop('ro.product.device')=='endeavoru'
II getprop('ro.build.product')=='endeavoru' II
getprop('ro.product.board')=='endeavoru'
Click to expand...
Click to collapse
witch Rom are you try to install?

Categories

Resources