Related
Whenever I try to flash a rom, i get this error:
E:Can't chown/mod /system/etc/init.d (No such file or directory)
E:Failure at line 64: set_perm etc.
Installation aborted!
The roms i have tried are: Pinky's Rom, Leedroid, Official(rooted) rom
Hboot; Version: 0.93
I can't figure out what to do! Someone please help!
Did you root with alpharev?
If not do it and install alpharev recovery as you root it and will be fine.
I had same issue and that fixed it
Sent from my HTC Desire using XDA Premium App
08r3308 said:
Did you root with alpharev?
If not do it and install alpharev recovery as you root it and will be fine.
I had same issue and that fixed it
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
You cannot root with alpharev! Alpharev seets you s-off. Before alpharev can do this, you need root access. This you get by rooting your phone e.g. with unrevoked. Alpharev does not have an own recovery, it is clockworkmod.
@Umair.K:
Did you root your phone already?
So you run unrevoked then alpharev? Or only unrevoked? Because with mine i had to run untrvoked then alpha to be able to use recovery
Sent from my HTC Desire using XDA Premium App
08r3308 said:
So you run unrevoked then alpharev? Or only unrevoked? Because with mine i had to run untrvoked then alpha to be able to use recovery
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
Yes. First unrevoked to get root + recovery and then alpharev to s-off.
Ok thank you i hope this helps op as well
Sent from my HTC Desire using XDA Premium App
Oh sorry should have given all those details before, here you go:
Bravo Pvt3 S-off
Hboot- 0.93.1000
Radio: 5.09.00.20
And as you can see, I am rooted and plus S-off with Alpha rev... The weird part is that I can flash Cm7-Stable mod and its working but whenever i try to flash any other rom, i get the error!
E:Can't chown/mod /system/etc/init.d
(No such file or directory)
E: Failure at line 65:
set_perm_recursive 0 0 0777 0777 SYSTEM:etc/init.d
Installation aborted.
and the last rom i tried to flash was "Bravo_WWE_2.29.405.5_v5"
Umair.K said:
Oh sorry should have given all those details before, here you go:
Bravo Pvt3 S-off
Hboot- 0.93.1000
Radio: 5.09.00.20
And as you can see, I am rooted and plus S-off with Alpha rev... The weird part is that I can flash Cm7-Stable mod and its working but whenever i try to flash any other rom, i get the error!
E:Can't chown/mod /system/etc/init.d
(No such file or directory)
E: Failure at line 65:
set_perm_recursive 0 0 0777 0777 SYSTEM:etc/init.d
Installation aborted.
and the last rom i tried to flash was "Bravo_WWE_2.29.405.5_v5"
Click to expand...
Click to collapse
You have partition for CM7, so any sense rom don't have enough space in /system.
Repartition your phone (look in alpharev site) as sense (default) partition. /system must be 250mb
Sent from my pocket using a pen
mendozinas said:
You have partition for CM7, so any sense rom don't have enough space in /system.
Repartition your phone (look in alpharev site) as sense (default) partition. /system must be 250mb
Sent from my pocket using a pen
Click to expand...
Click to collapse
Oh Thankyou soo much man! Thats exactly what I didn't think of before
But could you give me a guide line on how to partition my sd card like that? Because I purchased the phone from someone else, and he had done all the work himself!
It would be really helpful! Thanks!
You cant partition your sd like that ... you should flash STOCK HBOOT... find it at Alpha Rev pages... and there you will find diferent HBOOT's and everything will be clear for you... You partition your SD for needs of diferent ROM's but when it comes to HBOOT there is only few of them... I suggest CM7 HBOOT.. the one with 130 Mb for system, but pay attention on which ROM you flash...
bluzermajstor said:
You cant partition your sd like that ... you should flash STOCK HBOOT... find it at Alpha Rev pages... and there you will find diferent HBOOT's and everything will be clear for you... You partition your SD for needs of diferent ROM's but when it comes to HBOOT there is only few of them... I suggest CM7 HBOOT.. the one with 130 Mb for system, but pay attention on which ROM you flash...
Click to expand...
Click to collapse
Ha ha.
He is having problems because of CM7 hboot and you suggest to flash it? He needs stock hboot.
Sent from my pocket using a pen
bluzermajstor said:
You cant partition your sd like that ... you should flash STOCK HBOOT... find it at Alpha Rev pages... and there you will find diferent HBOOT's and everything will be clear for you... You partition your SD for needs of diferent ROM's but when it comes to HBOOT there is only few of them... I suggest CM7 HBOOT.. the one with 130 Mb for system, but pay attention on which ROM you flash...
Click to expand...
Click to collapse
Alright thats quite clear but the instructions aren't quite clear on Alpha Rev's page!
It says "If you are already S-OFF, you can get our newest patched HBOOTs from here. (without going through the entire procedure again).
Please read the entire table and pick the partition table with the correct sizes for your ROM. One easy way to switch partition tables, is to nandroid backup,
and verify that the sizes of your backup are indeed the ones listed in the table (or smaller), and restore after flashing hboot"
-So afterwards I tried to use the PB99.img by placing it on the root of my sd card and flashing it via recovery, but didn't work!
-Then i tried to use "Android Flasher(1.76)" to flash the new hboot, but that failed aswell! :S
So do i have to repeat the whole S-off procedure again or do i need to use cmd and type in commands to flash a new H-boot? This is getting confusing :O!
If your phone is s-off, you do not have to s-off again. To recognize if your phone is s-off:
1.) Splash screen is the joker
2.) If you boot into hboot (starting with pressed volume down button) first line should be "alpharev" and in the second line the last should be "s-off".
When you use android flasher, you must not use the file PB99_IMG-XXX.zip. You have to use the file bravo_alphaspl-xxx.img ("xxx" stands for the hboot you want).
When you use the method with PB99IMG_XXX.zip, you have to rename the file into PB99IMG.zip and copy it to the root of you sd-card (just watch out, you do not rename it to PB99IMG.zip.zip, because windows hides known file extensions).
Wether you decide for android flasher or directly the method with the zip files, make a complete nandroid backup first. Then download the hboot you want and you need for the method you decided (Do not forgot to check md5 after downloading the hboot!) and run the update.
How you do this:
Android flasher:
1.) Make sure you have usb debug mode on, the behaviour when usb is connected is on "only load" and you have installed hboot dand htc drivers
2.) Connect the phone with your computer
3.)
4.) Choose the file bravo_alphaspl-xxx.img and run the update (android flasher will say you when it's finished)
PBIMG99.zip:
(...)Start the phone in HBOOT mode (VolDown+POWER) to flash the HBOOT without a PC.
Click to expand...
Click to collapse
(from alpharev website)
In both methods now boot into recovery, wipe everything and restore the nandroid backup.
No warranty for any damage!
I get this while using android flasher
adb.exe reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* daemon started successfully *
fastboot.exe flash hboot hboot.img
< waiting for device >
sending 'hboot' (512 KB)...
sending 'hboot' (512 KB)...
OKAY [ 0.087s]
writing 'hboot'...
OKAY [ 0.161s]
finished. total time: 0.248s
rebooting into bootloader...
OKAY [ 0.096s]
finished. total time: 0.096s
finished. total time: 0.096s
erasing 'cache'...
FAILED (command write failed (No such file or directory))
finished. total time: -0.000s
Del hboot.img
fastboot.exe reboot
rebooting...
Is this right or is there something wrong?
finished. total time: 0.000s
Umair.K said:
I get this while using android flasher
adb.exe reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* daemon started successfully *
fastboot.exe flash hboot hboot.img
< waiting for device >
sending 'hboot' (512 KB)...
sending 'hboot' (512 KB)...
OKAY [ 0.087s]
writing 'hboot'...
OKAY [ 0.161s]
finished. total time: 0.248s
rebooting into bootloader...
OKAY [ 0.096s]
finished. total time: 0.096s
finished. total time: 0.096s
erasing 'cache'...
FAILED (command write failed (No such file or directory))
finished. total time: -0.000s
Del hboot.img
fastboot.exe reboot
rebooting...
Is this right or is there something wrong?
finished. total time: 0.000s
Click to expand...
Click to collapse
Download and install the app quick system info pro:
http://www.appbrain.com/app/quick-system-info-pro/org.uguess.android.sysinfo.pro
After starting you can compare the showed partition sizes to these of downloaded hboot. If it's fitting, everything is all right. I remember i had the same "issue" and everything is fine.
hi, i'm new to tis, i've root my phone (i thought so) ...
i've root using Unrevoked and S-OFF using AlphaRev....
---AlphaRev---
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051D
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30_2
Aug 10 2010, 17:52:18
i've done it for quite a while, but until now i still cant flash any ROM to my phone... really meant it, cant flash any ROM...
when i try to flash, smthing like this pop out...
--Installing: SDCARD:update-cm-6.1.1-Desire-signed.zip
E:Can't find MISC:
Finding update package...
Opening Update package...
Installing update...
Welcome to CyanogenMod-6.1.1-Desire!
assert failed: write_raw_image('/tmp/boot.img'.'boot')
E:Error in /sdcard/update-cm-6.1.1-Desire-signed.zip
(status 7)
Installation aborted.
is it because of my SD Card...??? Im using Samsung 16G, but i've tried using few other brand of 2Gb SD Card, still unsuccessfull...
can anyone help me...??? sorry coz i'm a noob...
MatDrOiD said:
You cannot root with alpharev! Alpharev seets you s-off. Before alpharev can do this, you need root access. This you get by rooting your phone e.g. with unrevoked. Alpharev does not have an own recovery, it is clockworkmod.
@Umair.K:
Did you root your phone already?
Click to expand...
Click to collapse
you don't need a rooted rom for revolutionary or alpharev... When the utility runs it gains temp root and is able to continue. The proof is in the wildfire AND me running it straight after I used a RUU on my Desire and used it without rooting
HTC Desire (ojan) said:
is it because of my SD Card...??? Im using Samsung 16G, but i've tried using few other brand of 2Gb SD Card, still unsuccessfull...
can anyone help me...??? sorry coz i'm a noob...
Click to expand...
Click to collapse
I doubt it's your sd-card. Okay since you've got S-OFF lets flash a different recovery. Follow these steps:
All you have to do is downlaod fastboot commander, and the java jdk for the tool to work.
Then, download the Ra Desire recovery
Once you've got that, but into fastboot (power off, hold back key & power), and plug in via USB.
run fastboot commander, navigate to the "misc" tab, select "recovery" "boot" "userdata" "system" "cache" "sd-ext"and nothing else and click "erase chosen partition(s)", then go back to the "Hboot, radio & rec" tab, choose "recovery", and find the recovery.img you have downloaded.
Then, simply press "flash recovery"
Once that's done, power off and reboot into recovery (power off, volume down & power, then use volume down key to navigate to RECOVERY and press power to select)
Then flash a ROM of your choice. For me this is the best way to flash new ROMs since it's a good, clean install and you don't get remaining crap left over from old ROMs
Did you wipe everything before flashing the rom?
Swyped from Oxygen with Transparent XDA App
yes, i'll try this and let u know if its working... thanks...
by the way, i've wipe everything before i try to flash a new ROM, wiping DalvikCache is unsuccesfull...
Solution in 5th post!
Hi, i have decided to get the HD2 by selling my desire. I was requested to put it back to stock. Unfortunately, i dont know what went wrong along the way. I need help. Firstly i made a gold card then i ran an ruu. It went successfully through all the way until it finished system partition and then it failed on the data partition. after that i searched for other problems by others. i saw that if you had the Data++ or other hboots you will have problems flashing and thats what happened.
So i used Android Flasher to flash a the hboot downgrade and it did not succesfully write the hboot by saying failed at that part. At the end it says success though.
Now i flashed stock hboot same problem. After flashing all this my device isn't able to flash anything because boot loader signature failed. I dont know what to do plus i gotta sell the device by tomorrow
Please help me..... Thank you,
Should i try a RUU thats version 2.1+? Can i have a link? all the ones i got are below version 2. Thanks
By the way the phone is now turning on with the black htc screen with the four triangles. I cant get into the bootloader menu too only when the ruu fails and i take out the power cable and old it shows is the version and "RUU"
I have tried the asia RUU and the Europe RUU. I need help with the PB99IMG.
The error i recieve is this:
ERROR[140]:BOOTLOADER VERSION ERROR
The rom update utility cannot update your android phone.
Please get the correct rom update utility and try again.
Click exit to quit.
Thanks!
Heres what i get with Android flasher:
operable program or batch file.
operable program or batch file.
cd data\
'taskkill' is not recognized as an internal or external command,
taskkill /F /IM adb.exe
operable program or batch file.
taskkill /F /IM fastboot.exe
adb.exe reboot bootloader
* daemon not running. starting it now on port 5037 *
error: device not found
* daemon started successfully *
fastboot.exe flash hboot hboot.img
sending 'hboot' (512 KB)...
OKAY [ 0.109s]
OKAY [ 0.109s]
writing 'hboot'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.172s
rebooting into bootloader...
fastboot.exe erase cache
OKAY [ 0.031s]
finished. total time: 0.031s
< waiting for device >
erasing 'cache'...
OKAY [ 0.516s]
finished. total time: 0.516s
Del hboot.img
fastboot.exe reboot
rebooting...
finished. total time: 0.031s
So you can't even enter into bootloader?
however if you want a guide "FOR INSTALLING ANY RUU AS PB99IMG.ZIP", you find it here: http://forum.xda-developers.com/showthread.php?t=880268
paolo-red1 said:
So you can't even enter into bootloader?
however if you want a guide "FOR INSTALLING ANY RUU AS PB99IMG.ZIP", you find it here: http://forum.xda-developers.com/showthread.php?t=880268
Click to expand...
Click to collapse
Hey man thanks for the reply. Great news, i just fixed it! Im having tuition now so will post it later
Alright heres how i fixed it:
I just flashed the latest froyo ruu, i realised that i could not use the old one. LOL
Also remember that the hboot has to be put back to stock. Use the Android flasher for ease of use with fastboot.
Why i had trouble:
1- i was very very panicky.
2- i had to trade in my phone for a HD2 tomorrow! i had to fix it or my chance of getting the hd2 would be lost
3- i couldn't think when i got the problem, scared to death. Now i realise how gay it was.
I guess this is good bye to all the fun and great awesome time i had with the desire. My first android phone that has been a pleasure and been a great phone. I will miss this amazing community of the desire.
I want to thank:
-EddyOS, last time i used to help others with problems and wheever i went to the thread Eddy would post something very helpful.
-Xavier John, he lives in the same country as me and i hope to learn from him. He gave alot to the community.
- Richard Trip
- Adam G
- Insert Coin
- Robocik
- Coolexe
and many many many other ppl i forgot, i love this phone and you guys haha.
Thanks for your feedback
Hello, I want to install a custom rom on my Virgin Mobile HTC Wildfire S. It is rooted, and i already know which ROM I want to install. The problem is, when attempting to make a backup using ROM Manager, It just reboots the phone (with the little "Tell HTC" icon at the top). I also cannot boot into recovery. I have alreay searched far and wide but all i see are " enable erase recovery and flash clockwork mod again" I have but to know avail I would be really grateful for any help (i'm a bit of a noob)
here is the info i see at HBOOT
MARVELC PVT SHIP S-OFF RL
HBOOT-1.06.0000
MICROP-0354
RADIO-0.94.00.0824
Aug 14 2011,22:34:38
Have you flashed the recovery yet?
If not, you won't be able to make backups nor will you be able to flash ROMs.
have you tried manually booting into recovery by powering off then holding volume - and power and then selecting recovery?
i had some issues with rom manager in the past, but when i went to backup manually it seemed ok.
Yes I have I flashed CWM Recovery and have also tried rebooting into it by that method >.<
GabbyKitty said:
Yes I have I flashed CWM Recovery and have also tried rebooting into it by that method >.<
Click to expand...
Click to collapse
Mind trying my all in one tool? Try flashing the recovery from there and see if it works.
Sent from my HTC Wildfire S A510e using xda premium
rezo609 said:
Mind trying my all in one tool? Try flashing the recovery from there and see if it works.
Sent from my HTC Wildfire S A510e using xda premium
Click to expand...
Click to collapse
Yeah, I tried it (very cool tool btw) but it didn't work it still wont boot into recovery :/ when i run it it goes into fastboot and everything and restarts but CWM still wont show up :c
this is exactly what it says in the tool:
1 Remove Superuser, Su binary, and Busybox
2 Flash Stock Recovery 2.3.3
3 Flash Stock Recovery 2.3.5
4 Lock Bootloader (1.08.0099/1.09.0099)
5 Install Drivers (Windows)
6 Unlock Bootloader (1.08.0099/1.09.0099)
7 Root Device (rezo609's One Root Method)
8 WiFi Password Recover Tool
9 Install CWM Recovery
10 About
11 Changelog
Enter Selection/ENTER to exit: 9
< waiting for device >
sending 'recovery' (4494 KB)...
OKAY [ 1.748s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.749s
downloading 'boot.img'...
OKAY [ 1.749s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.750s
error: device not found
Recovery is now flashed
Press any key to continue . . .
GabbyKitty said:
Yeah, I tried it (very cool tool btw) but it didn't work it still wont boot into recovery :/ when i run it it goes into fastboot and everything and restarts but CWM still wont show up :c
this is exactly what it says in the tool:
1 Remove Superuser, Su binary, and Busybox
2 Flash Stock Recovery 2.3.3
3 Flash Stock Recovery 2.3.5
4 Lock Bootloader (1.08.0099/1.09.0099)
5 Install Drivers (Windows)
6 Unlock Bootloader (1.08.0099/1.09.0099)
7 Root Device (rezo609's One Root Method)
8 WiFi Password Recover Tool
9 Install CWM Recovery
10 About
11 Changelog
Enter Selection/ENTER to exit: 9
< waiting for device >
sending 'recovery' (4494 KB)...
OKAY [ 1.748s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.749s
downloading 'boot.img'...
OKAY [ 1.749s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.750s
error: device not found
Recovery is now flashed
Press any key to continue . . .
Click to expand...
Click to collapse
Go and try these ....
http://forum.xda-developers.com/showthread.php?p=27534816#post27534816
---------- Post added at 09:34 AM ---------- Previous post was at 09:18 AM ----------
rajanand said:
Go and try these ....
http://forum.xda-developers.com/showthread.php?p=27534816#post27534816
Click to expand...
Click to collapse
YUP that tool is only to revert back ur phone to life/STOCK ROM.
wildfire s new models have newer display parameters b'coz of that CWM cannot compete anymore ,
so we wll have to w8 for new make,or some changes.
but blank screen dosent means that cwm not working...
TRY MY ABOVE POST
rezo609 said:
Mind trying my all in one tool? Try flashing the recovery from there and see if it works.
Sent from my HTC Wildfire S A510e using xda premium
Click to expand...
Click to collapse
Your tool is for GSM is it not? I understand it works with both, but the recovery is different between Marvel and Marvelc. Marvelc users should the Marvelc recovery.
Problems with my HTC one X.
adb devices returns 'no devices found'. fastboot devices works though.
CWM recovery seems to be working.
Can't install CM9 from SD-card, when i do the phone hangs at the loading screen of CM9.
Can't adb push another .zip to the phone since ADB doesn't work.
Fastboot:
c:\Users\user\Desktop\HTC\onexroot>fastboot erase cache
erasing 'cache'...
FAILED (command write failed (Unknown error))
finished. total time: 0.588s
also:
c:\Users\Rik de Vroom\Desktop\HTC\onexroot>fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru.img
sending 'recovery' (5732 KB)...
FAILED (unknown status code)
finished. total time: 0.026s
How can I get another .zip file on the sdcard? was hoping to try InsertCoin (since bluetooth isn't working on CM9 and a lot of apps keep crashing).
why isn't adb working? I have updated my JDK and android SDK...
adb devices DOES working in the hanging loading screen of CM9; but unable to do anything "waiting for device" ...
Im stuck :<
CWM
1st flash new CWM that has USB mount, so you can send any file to phone
2dn did you flash the kernel? >> boot.img for the CM9 ROM?
FabioPBX said:
1st flash new CWM that has USB mount, so you can send any file to phone
2dn did you flash the kernel? >> boot.img for the CM9 ROM?
Click to expand...
Click to collapse
looking into the new cwm now; hadn't figured that was so outdated.
i did flash the kernel; used cm9 before but that was behavving strangely; so figured a reinstall might help. tried miui in the meantime but man, i'm used to cm9
maybe you got a corrupted download but if you can access recovery then you should be fine
give TripNDroid's CM9 port a go, he was first to have almost fully functional CM9 port and works quite decently, with just few minor bugs
FabioPBX said:
maybe you got a corrupted download but if you can access recovery then you should be fine
give TripNDroid's CM9 port a go, he was first to have almost fully functional CM9 port and works quite decently, with just few minor bugs
Click to expand...
Click to collapse
Well, what doesn't work is bluetooth and GPS.. both of which i want to use.. Also; a lot of apps seem to 'stop responding' after a while.. Guess im back to stock rom untill a fully working CM9 comes out.
I've rooted my HTC One X (International version) phone and tried putting cyanogenmod 10.1 onto it but that failed (it came up with an error that I can't remember).
After that, when I started it up, it hanged on the HTC logo screen. I tried to put another ROM onto the memory of my phone but my computer won't recognise my device (I tried putting it in recovery mode [clockworkmod recovery], fastboot mode and hboot mode)
The phone has been relocked (I think that's because I was playing around with it too much) and I don't know how to unlock it again.
When I try the unlock command I get this message:
Code:
C:\Users\----\Desktop\phone>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.008s]
writing 'unlocktoken'...
FAILED (remote: battery low)
finished. total time: 0.218s
So I tried this: http://forum.xda-developers.com/showthread.php?t=1658084 to try and fix the battery message.
It still doesn't work.
Now the phone doesn't start when I try to turn it on (by pressing the power button, holding down the power button, holding the power and volume buttons etc.). When I connect my phone via USB to my computer, it turns on for 3 minutes (into fastboot USB mode), turns off for 3 minutes, turns back on for 3 minutes and so on...
Can anyone help?
Use the script you linked for a couple of hours or so. It's supposed to reboot hone over and over again.
Then after you're good to flash, unlock the bootloader and flash a custom recovery.
Your hboot version is too low for cm10.1. You need to bump it up, just search how to.
Next, make sure you did these two things while installing cm10.1:
1. Flash boot.img
2. Install vendor installer in recovery (read the cm thread)
Sent from my IceCold One X
TToivanen said:
Use the script you linked for a couple of hours or so. It's supposed to reboot hone over and over again.
Click to expand...
Click to collapse
Okay so the script ran for about a minute and then it came with this:
Code:
< waiting for device >
battery-voltage: 2859mV
finished. total time: 0.170s
rebooting into bootloader...
OKAY [ 0.224s]
finished. total time: 0.224s
< waiting for device >
battery-voltage: 2848mV
finished. total time: 0.124s
rebooting into bootloader...
OKAY [ 0.204s]
finished. total time: 0.205s
< waiting for device >
battery-voltage: 2829mV
finished. total time: 0.104s
rebooting into bootloader...
OKAY [ 0.228s]
finished. total time: 0.228s
< waiting for device >
battery-voltage: 2814mV
finished. total time: 0.102s
rebooting into bootloader...
OKAY [ 0.229s]
finished. total time: 0.229s
< waiting for device >
battery-voltage: 2792mV
finished. total time: 0.107s
rebooting into bootloader...
OKAY [ 0.218s]
finished. total time: 0.218s
< waiting for device >
battery-voltage: 2769mV
finished. total time: 0.105s
rebooting into bootloader...
OKAY [ 0.241s]
finished. total time: 0.242s
< waiting for device >
battery-voltage: 2743mV
finished. total time: 0.139s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.214s
< waiting for device >
Now the phone is staying off and won't turn on...
(Also, is the battery voltage supposed to slowly drop after each script cycle?)
EDIT:
Nevermind, it's restarting over and over again, here's the continuation:
Code:
FAILED (status read failed (Too many links))
finished. total time: 0.214s
< waiting for device >
battery-voltage: 2997mV
finished. total time: 0.167s
rebooting into bootloader...
OKAY [ 0.244s]
finished. total time: 0.245s
< waiting for device >
battery-voltage: 2980mV
finished. total time: 0.183s
rebooting into bootloader...
OKAY [ 0.245s]
finished. total time: 0.245s
< waiting for device >
That ain't looking good... 2750mV is the lowest safe voltage for lipo cells. You went under that already, it shouldn't be even possible because the circuit should shut down the phone before that happens.
Damn. Try the script one more time, also if you manage to boot to recovery, you can charge there, just plug in normally. If the voltage still decreases, you probably have to open up the phone and charge it "the hard way"
Sent from my IceCold One X
TToivanen said:
That ain't looking good... 2750mV is the lowest safe voltage for lipo cells. You went under that already, it shouldn't be even possible because the circuit should shut down the phone before that happens.
Damn. Try the script one more time, also if you manage to boot to recovery, you can charge there, just plug in normally. If the voltage still decreases, you probably have to open up the phone and charge it "the hard way"
Click to expand...
Click to collapse
Ooh... that really doesn't sound good. Um, well firstly I left the script running for an hour. The maximum voltage that it ever got to was 3002mV. I tried the batch file again and again, for like 10 minutes, and still the same results.
Right now, things are looking better.
I realised that my computer's USB won't charge my phone above 3 volts, and will cause it to slowly drop, so I connected the mains battery charger and manually pressed 'reboot bootloader' over and over and over again. This actually charged it. Right now when I check it on my computer, it says 3617mV, and I have successfully unlocked the relocked bootloader using the instructions in htcdev.com.
I can get to the recovery mode.
When I start my phone normally, it hangs on the HTC logo screen.
Would it charge in recovery mode if I only have clockworkmod 5.8.2.7 installed?
I tried updating it to clockworkmod 5.8.3.1 but it says battery low and so I probably have to keep charging it by manually restarting the bootloader?
Right now I'm sorta underway.
I need to update the clockworkmod, update the hboot version, and then somehow copy a ROM onto my phone when it's in recovery mode (I don't know how to do this bit). And then it should install the new ROM...
once you can get into custom recovery there is a option somewhere to mount your phone to the pc.
just copy it to your phone, unmount and flash. might have to do a reflash of the boot.img after the rom.. just try.
If you charge your phone and boot into recovery you can mount usb storage or push rom via adb :
Copy rom to adb folder and open cmd in thst folder and type:
adb push romname.zip /sdcard/
Sent from my HTC One X using xda app-developers app
Is there any way to upgrade the hboot version? When I check the cid I get this:
Code:
C:\Users\----\Desktop>fastboot oem readcid
< waiting for device >
...
(bootloader) DEBUG: cid: TELNZ001
OKAY [ 0.086s]
finished. total time: 0.087s
I can't find a hboot firmware.zip that matches that cid...
Do also
fastboot getvar version-main
Sent from my IceCold One X
davidk-il said:
If you charge your phone and boot into recovery you can mount usb storage or push rom via adb :
Copy rom to adb folder and open cmd in thst folder and type:
adb push romname.zip /sdcard/
Click to expand...
Click to collapse
How do you do that? I have CWM 5.8.3.1 on it but when I select 'mount USB storage' nothing happens. It doesn't mount it.
When I run the command I get this:
Code:
C:\Users\****\Desktop>adb push Slim-endeavoru-4.2.2.build.2.5-OFFICIAL.zip /sdcard/
error: device not found
TToivanen said:
Do also
fastboot getvar version-main
Click to expand...
Click to collapse
Here's the output:
Code:
C:\Users\----\Desktop>fastboot getvar version-main
< waiting for device >
version-main: 1.26.781.2
finished. total time: 0.108s
You need clockworkmod 5.8.4.0 the older versions can't mount as USB mass storage or charge.
BenPope said:
You need clockworkmod 5.8.4.0 the older versions can't mount as USB mass storage or charge.
Click to expand...
Click to collapse
Oh thanks, I've upgraded it to CWM 5.8.4.0 and now my computer recognises it!
At the moment I don't know what to do.
Can I update the hboot version? Can I put Cyanogenmod 10.1 onto it? Or another ROM like slim?
If not, how can I restore the old original android on it? Right now it just hangs at the HTC logo if I start it normally.
Here's the info for my phone:
Code:
HTC One X internation version
cid: TELNZ001
version-main: 1.26.781.2
hboot: 0.43.0000
Clockworkmod: 5.8.4.0
Here is the ruu you need to go back to full stock
http://bugsylawson.com/index.php/fi...812-radio-112049013-release-251287-signedexe/
After the ruu you can update with official ota :thumbup:
Put the phone in the bootloader and relock the bootloader.
Fastboot oem lock
Then keep the phone in the bootloader and select the ruu by clicking on it with the right mouse button. Then select : run as administrator
It will bring the phone to full stock and you be able to update after that from witin the OS menu .....
Note : backup what you need. It erases everything
Thanks, everything is fixed now. I have used someone e'se's nandroid backup and it works alright now.
Failed Installation
Hello all. Since I have a situation very similar, I am seeking advice as well. I have the HTC One X Plus International with TWRP v2.5.0.0. installed and I had put a compatible ROM from CM for this phone on the SD card. But every time I attempt to install it, I receive the message 'assert failed: getprop', etc. There currently is no ROM installed on the device since I wiped it clean. I figured out how to adb push the ROM onto the SD card but that did me no good since it continually fails when attempting to install. I seem to have run out of ideas. Anyone who may be able to assist, is greatly appreciated. Thanks.
Jussi31 said:
Hello all. Since I have a situation very similar, I am seeking advice as well. I have the HTC One X Plus International with TWRP v2.5.0.0. installed and I had put a compatible ROM from CM for this phone on the SD card. But every time I attempt to install it, I receive the message 'assert failed: getprop', etc. There currently is no ROM installed on the device since I wiped it clean. I figured out how to adb push the ROM onto the SD card but that did me no good since it continually fails when attempting to install. I seem to have run out of ideas. Anyone who may be able to assist, is greatly appreciated. Thanks.
Click to expand...
Click to collapse
You can mount storage from recovery....
For adb -
put the Rom in the adb folder and in cmd - adb push /sdcard/*rom name*.zip
Sent from my HTC One X using xda app-developers app
Yes, I have already copied two different compatible ROMs onto the SD card; attempted to install them but each time it fails (assert failed: getprop). I am confused about putting them both into the adb and in cmd? Am I to create folders on the SD card with those names? From what I can gather there just seems to be a problem installing any ROM as of this point, and I cannot figure out as to why.
Jussi31 said:
Yes, I have already copied two different compatible ROMs onto the SD card; attempted to install them but each time it fails (assert failed: getprop). I am confused about putting them both into the adb and in cmd? Am I to create folders on the SD card with those names? From what I can gather there just seems to be a problem installing any ROM as of this point, and I cannot figure out as to why.
Click to expand...
Click to collapse
Just copy the ROM.zip file in your ADB/Fastboot folder... then run the following code in cmd:
Code:
adb push /sdcard/ROM.zip
Where rom.zip = the zip file you had copied in your adb folder... It will send that file in the root of the sd card
I have tried that multiple times already without any results, unfortunately. I also have made matters worse--I decided to flash a no-touch CWM, thinking that may have been the culprit in all of this, and now it no longer even goes into CWM, and the screen remains blank and dark. Not good. At least I still have the ability to go into bootloader mode.