Related
I get an error with the viper 1.0.3 rom. Sometimes when i open file explorer the program stops and quit the app. When i open it after that it works oke. I rooted my phone yesterday and put the viper rom + viper repacked kernel on my phone by doing the following steps.
- unlock bootloader and root the phone with the all in one toolkit
-make a twrp recovery with the all in one toolkit.
- make a backup in recovery mode
-install rom in recovery mode
-wipe cache partition in recovery mode
- boot phone and follow the setup wizard
-the phone rebooted a couple of times by itself.
-reboot phone in fastboot and flashed the viper repacked kernel with kernal flasher.
did i do something wrong and how can i fix it/ should i do it?
Was it because i did not Wipe Cache, Dalvik, Factory Reset?
Reflashed the rom again.
Before flashing i wiped the cache partion, wiped dalvik cache and factory reset (user data)
I still get the force close with file explorer
Somebody can help me out? (I can not post in to the viper custom rom topic)
Don´t know why you can´t post in the thread there. But you have to use the special Viper TWRP Recovery in the newest version. Look in the thread, there it´s written.
Neo XL said:
Don´t know why you can´t post in the thread there. But you have to use the special Viper TWRP Recovery in the newest version. Look in the thread, there it´s written.
Click to expand...
Click to collapse
Oké thanks. Does it really make much difference? Can I just flash the venom recovery with the venom kernel flasher? And after that flash the kernel again? I have now installed a lot of apps and installed nova launcher and created custom icons. Is it possible to save that and my settings of viper?
Hello.
I have only been able to install ViperX+ 1.08 ROM successfully. I wanted to experience other ROMs in comparison and have found ROMs specifically for this model, HTC One X Plus International, only to have them fail to fully install successfully. I have read up here on how to go about it and followed the steps dutifully but to no avail.
Does it make a difference on which Recovery you have installed for it to be successful or not? I currently have the latest TWRP 2.5.0.0 for my model. I have tried installing CyanogenMod and AOKP. CyanogenMod never makes it pass the installation because it fails right after attempting to install. AOKP installs but hang at the opening picture, and yes, I tried flashing the boot.img in Fastboot thinking that would solve it but it continued hanging anyway. Anyone have any help they can offer me? Thanks.
Jussi31 said:
Hello.
I have only been able to install ViperX+ 1.08 ROM successfully. I wanted to experience other ROMs in comparison and have found ROMs specifically for this model, HTC One X Plus International, only to have them fail to fully install successfully. I have read up here on how to go about it and followed the steps dutifully but to no avail.
Does it make a difference on which Recovery you have installed for it to be successful or not? I currently have the latest TWRP 2.5.0.0 for my model. I have tried installing CyanogenMod and AOKP. CyanogenMod never makes it pass the installation because it fails right after attempting to install. AOKP installs but hang at the opening picture, and yes, I tried flashing the boot.img in Fastboot thinking that would solve it but it continued hanging anyway. Anyone have any help they can offer me? Thanks.
Click to expand...
Click to collapse
The aokp uses the 4.2 kernal so you will have to instal that. But I'm not sure on the recovery .. maybe it might be worth trying clockwork as if the twrp you are useing is especially for the viper Rom? Have a go at installing the different recovery maybe that will help and double check what you have to do to install on the thread hope this helps
Ilike the viper Rom... But if I get time tomorrow I will try for myself ... If no one else helps you out by the time I do it I will update you on how I done it and any problems I faced maybe I will end up in the same situation.
Sent from my HTC One X+ using xda premium
Appreciate it. Insofar as the Recovery is concerned, the initial Recovery that I installed from the All-In-One kit when installing ViperX+ is different from the one I have now. Unless it is just a newer version, I now have Venom TWRP 2.5.0.0., just FTR. Thanks again, I will be interested to hear what happens for you.
Jussi31 said:
Appreciate it. Insofar as the Recovery is concerned, the initial Recovery that I installed from the All-In-One kit when installing ViperX+ is different from the one I have now. Unless it is just a newer version, I now have Venom TWRP 2.5.0.0., just FTR. Thanks again, I will be interested to hear what happens for you.
Click to expand...
Click to collapse
TWRP is the ideal solution for our HOX+ - at least as of now.
I hope you are doing the following:
1. Wiping Data & System.
2. Installing boot.img.
The Venom customized TWRP does not have any issues because I also used it for some time (as of now I am back on the official TWRP).
You can download the lastes verison from here:
http://techerrata.com/browse/twrp2/enrc2b
And install it using Hox+ All in one toolkit by hasoon.
Make sure you wipe data & system before you install the ROM.
I also changed from ViperX 1.08 to ARHD, InsertCoin & Elegancia.. no issues
Hmmm. I'll have to putz around with it some more and see what happens. Thanks.
Here's a brief summary of what I attempted to do.
I wiped Delvik Cache; I wiped Cache; I did Factory Reset; I wiped System.
Next I tried installing CyanogenMod and received the following error messages:
assert failed: getprop
E: error executing updater binary in zip
Error flashing zip
So I wiped everything again and tried installing AOKP. It successfully installs. I try rebooting prior to flashing boot.img. It hangs on horse picture opening screen. So I flash the boot.img in Fastboot and reboot after erasing cache. When rebooting it hangs on opening white screen.
I'm baffled. What am I doing wrong?
Jussi31 said:
Here's a brief summary of what I attempted to do.
I wiped Delvik Cache; I wiped Cache; I did Factory Reset; I wiped System.
Next I tried installing CyanogenMod and received the following error messages:
assert failed: getprop
E: error executing updater binary in zip
Error flashing zip
So I wiped everything again and tried installing AOKP. It successfully installs. I try rebooting prior to flashing boot.img. It hangs on horse picture opening screen. So I flash the boot.img in Fastboot and reboot after erasing cache. When rebooting it hangs on opening white screen.
I'm baffled. What am I doing wrong?
Click to expand...
Click to collapse
I guess your recovery is not able to detect that your phone is one x+.. that's why assert failed error.. try changing the recovery( maybe CWM) and try again
Through trial-and-error, and reading hard, I figured out I had to install a compatible Kernel. I then was able to install, successfully, AOKP and it seems to work very smoothly. I'm just learning the ins-and-outs of everything. Thanks for your help.
Jussi31 said:
Through trial-and-error, and reading hard, I figured out I had to install a compatible Kernel. I then was able to install, successfully, AOKP and it seems to work very smoothly. I'm just learning the ins-and-outs of everything. Thanks for your help.
Click to expand...
Click to collapse
:good::good::good:
that is cool!
I can't flash CM11 on my Verizon Fascinate after using the following thread. http://forum.xda-developers.com/showthread.php?t=2521427.
I did stock rom EH03, cwm4 for CM7 and bml-i500 via odin still not able to install [ROM][4.4] Unofficial CyanogenMod 11.0. Getting following error after try to install from zip sd card. I am able to install 2-kernel_cm11__11-10-13-fascinatemtd. Please help.Thank You
e:error executing updater binary in zip '/sdcard
err0r flashing zip '/sdcard/cm-11-20131125-unoff
e:unable to mount '/system.
mohan2k2 said:
I can't flash CM11 on my Verizon Fascinate after using the following thread. http://forum.xda-developers.com/showthread.php?t=2521427.
I did stock rom EH03, cwm4 for CM7 and bml-i500 via odin still not able to install [ROM][4.4] Unofficial CyanogenMod 11.0. Getting following error after try to install from zip sd card. I am able to install 2-kernel_cm11__11-10-13-fascinatemtd. Please help.Thank You
e:error executing updater binary in zip '/sdcard
err0r flashing zip '/sdcard/cm-11-20131125-unoff
e:unable to mount '/system.
Click to expand...
Click to collapse
Cant mount system huh?
I believe you are getting this error because you are coming from stock. Update the phone to another rom like JellyBean 4.1 and then try to flash this then.
Still no go
Payton95 said:
Cant mount system huh?
I believe you are getting this error because you are coming from stock. Update the phone to another rom like JellyBean 4.1 and then try to flash this then.
Click to expand...
Click to collapse
Still no go with JB 4.1 or CM 10.1. Cant mount e:data or e:system
Flashed a GB bootloader with Odin?
jason_streak said:
Flashed a GB bootloader with Odin?
Click to expand...
Click to collapse
if he's having a problem coming from stock, then its either or. attempted a flash from Slim Bean 4.2, having same issue...
try from stock again(odin-flashed+re-partitioned), flash cwm-fixed-for-cm7(odin-flashed, do NOT RE-PARTITION!), flash the kernel in the cm11 OP(it will boot into TWRP recovery; note DO NOT FLASH A TWRP-INJECTED ROM FOR TWRP TO APPLY ONLY THE RECOVERY, IT WILL CORRUPT /SYSTEM AND /DATA PARTITIONS AS IT WAS MOUNTING THEM BEFORE THE TWRP RECOVERY INJECTION REBOOT!!, THUS HAVING ERRORS WHEN FLASHING!! TO FIX RESTORE ANY WORKING TWRP BACKUP, OR USE ODIN TO START OVER!! ), (did over-killing CAPS LOCK make it look important enough to remember) XD, anyways...
when in TWRP flash the following(as all checked with a blue "x", incase u dont use TWRP much):
-data
-cache
-dalvik-cache
-system
flash the newest version in @Unjustified Dev 's thread for (unofficial) CM11(as its the rom u are currently having troubles with, and u had a glitched version where the update-binary was not signed all the way in his rom, as if u look at the difference in the binary from it and the newer rom version, it didnt transfer all the way), then the special GAPPS in one of the comments ON A SEPARATE FLASH!, or goto paranoid-android's forum and flash the newest Modular-mini 4.4 GAPPS AGAIN!! ON A SEPARATE FLASH!,, then any mods/add-ons u want(can be on same flash as GAPPS, along with any other additional zips, with the exclusion of data restoring ones like Titanium-Backup-made "update.zip", as that will only restore the system-apps at the moment as it requires data partition to be setup, e.g. first_boot=completed_successfully, then u can goto recovery and flash it for a quicker data recovery)
the only reason why i didn't tell u to make a backup is cause when u flashed the kernel to get the TWRP, its an incompatible kernel for stock, but if u are on a rom u like, make a backup for it first, then flash to stock for a cleaned-out partition, i always suggest making regular/routine backups(about every 3-7 days, or when trying a new rom/Rooted-or-flashed-mod)+(and routinely deleting/cleaning older ones, or ones u don't use), or at least update the titanium-backup-made "update.zip" for faster data recovery(DO NOT INCLUDE SYSTEM-APPS BUILT WITH THE ROM INSIDE THE ZIP, AS SOMETIMES IT WILL OVERLAP THE ROMS ZIP AND CAUSE SOME ERRORS, SAME WITH ITS DATA!!) (opps caps-lock of remembering again, where did that come from)
note: in case u(the OP, or others who see this comment) the key-combos(or requirements) for the following partition loading(s) are:
-(ANY)recovery = Volume_DOWN+Volume_UP+Power
-Download-Mode = Plugged into USB-Cable(From AC(Wall-Adapter), DC(Car-Port)(may or may-not work, as it only did for me literally twice since ive owned the phone XD), or Computer(USB-Port( duh )))+Vol_DOWN
-System= (any other combination, as long as POWER is pushed down for ~2-5 seconds (and other partition combinations are not pressed+held after the second "samsung" popup, and/or for two consecutive "samsung" popups or more in some cases)
ADB Commands for rebooting partitions arenon-adb-shell-based, as in shell there is ALOT more ways u could do it)
-System (method1)= adb reboot
-System (method2)= adb reboot system
-Recovery (method1) = adb reboot recovery
-Recovery (method2) = adb reboot-recovery
-Download = adb reboot download
-POWER_OFF = adb reboot -p
Glad if i could be any help with this mini-thread comment now that i see the length XD but i tried to be through and user-friendly as i could think XD if u have any other things wrong or needed to know, feel free to ask on here =)
---------- Post added at 08:49 PM ---------- Previous post was at 08:45 PM ----------
Payton95 said:
Cant mount system huh?
I believe you are getting this error because you are coming from stock. Update the phone to another rom like JellyBean 4.1 and then try to flash this then.
Click to expand...
Click to collapse
im not trying to sound like a [email protected]$$, but if u look into the errors on the thing, like alot of systems it usually tends to load from top-to-bottom, and in that specific version build it was the update-binary not signed all the way in the transfer in sign-apk (notice the first error, "e:error executing updater binary in zip '/sdcard", and without the binary even if the recovery is compiled right for the phone model(e.g. with the right partition labels for system, data, cache, etc, it wont be able to know for the specfic code to use it by without the binary that is unique for each individual phone(in the update-binary file), by my observations in the systems used anyways =S, cause i manages to fix that specfic zip later after downloading the newer version, just for testing of THAT error, and replaced the update-binary and re-signed and it worked =)
jkok said:
try from stock again(odin-flashed+re-partitioned), flash cwm-fixed-for-cm7(odin-flashed, do NOT RE-PARTITION!), flash the kernel in the cm11 OP(it will boot into TWRP recovery; note DO NOT FLASH A TWRP-INJECTED ROM FOR TWRP TO APPLY ONLY THE RECOVERY, IT WILL CORRUPT /SYSTEM AND /DATA PARTITIONS AS IT WAS MOUNTING THEM BEFORE THE TWRP RECOVERY INJECTION REBOOT!!, THUS HAVING ERRORS WHEN FLASHING!! TO FIX RESTORE ANY WORKING TWRP BACKUP, OR USE ODIN TO START OVER!! ), (did over-killing CAPS LOCK make it look important enough to remember) XD, anyways...
when in TWRP flash the following(as all checked with a blue "x", incase u dont use TWRP much):
-data
-cache
-dalvik-cache
-system
thanks for this, I spent longer than I should have before asking for help.
I have no problems flashing pre 4.4 roms, I am not a developer, and I am stuck
odined back to stock
flashed just the kernel
booted into twrp and then it gets messy
if I advanced wipe cache, dalvik, system data .......it fails
I can factory reset but any wipe after that fails
I know persistence is key, but ive been at this for a while and went back to stock like four times.........any insights?
Click to expand...
Click to collapse
after it fails the 1st time, can you reboot to TWRP? if you can, wipe davlik, reflash the rom.
tsdsbrk said:
after it fails the 1st time, can you reboot to TWRP? if you can, wipe davlik, reflash the rom.
Click to expand...
Click to collapse
yes, flashing the kernel is successful, but the wipe is not going well. when I advanced wipe either all four together or starting with the sysystem (one at a time) I get red letter failed.
thought maybe it had something to do with mounting so I tried a 16 gig class 10 chip instead of the 32 gig chip. no difference.
Im not giving up but am going to rtry ri go from stock to helly, to kit kat and see if that makes a difference.
aircooledbusses said:
thanks for this, I spent longer than I should have before asking for help.
I have no problems flashing pre 4.4 roms, I am not a developer, and I am stuck
odined back to stock
flashed just the kernel
booted into twrp and then it gets messy
if I advanced wipe cache, dalvik, system data .......it fails
I can factory reset but any wipe after that fails
I know persistence is key, but ive been at this for a while and went back to stock like four times.........any insights?
Click to expand...
Click to collapse
-odin to stock (or GeeWiz odin from its thread) (dont forget to repartition)
-!!!!!!BOOT THE DEVICE ONCE!!! OR /system + Data PARTITIONS ARE NOT MADE!!!"
-(after that if odin'd from GeeWiz go in its recovery and convert partitions (labeled volumes) to efs not ext4)
-if odin'd to stock odin the cm4 fixed for cm7(no repartition), if odined from geewiz(and completed above step), goto next step from its recovery
-go in the recovery then flash the kernel (as u were in a cwm based recovery it will update to TWRP)
-When booted into TWRP do the ALL wipes (except SDCARD)
-Flash Rom ONLY IN THIS ZIP QUE!!! (NO GAPPS!)
-Flash Gapps+other .ZIP packages
-Reboot /system and watch the first boot =)
Sorry i wasnt as clear, but sometimes its faster with the GeeWiz odin since it is already 4.2.2 + comes with boot.img + bootloader from Gingerbread/ISC/JB (as its the same), it only seems to take longer from the convert partitions (rfs) step, buts its easier in the long run =)
I have a spare fassy and just successfully flashed 11.1. Heres what I did.
Odin back to stock.
Flashed sc_milestone2_full
Flashed hellybean 4.2.2
Flashed TWRP then turned my phone off
Turned phone on and booted to recovery (TWRP at this point)
Flaahed 11.1 without doing any type of wipe.
jkok said:
-odin to stock (or GeeWiz odin from its thread) (dont forget to repartition)
-!!!!!!BOOT THE DEVICE ONCE!!! OR /system + Data PARTITIONS ARE NOT MADE!!!"
-(after that if odin'd from GeeWiz go in its recovery and convert partitions (labeled volumes) to efs not ext4)
-if odin'd to stock odin the cm4 fixed for cm7(no repartition), if odined from geewiz(and completed above step), goto next step from its recovery
-go in the recovery then flash the kernel (as u were in a cwm based recovery it will update to TWRP)
-When booted into TWRP do the ALL wipes (except SDCARD)
-Flash Rom ONLY IN THIS ZIP QUE!!! (NO GAPPS!)
-Flash Gapps+other .ZIP packages
-Reboot /system and watch the first boot =)
Sorry i wasnt as clear, but sometimes its faster with the GeeWiz odin since it is already 4.2.2 + comes with boot.img + bootloader from Gingerbread/ISC/JB (as its the same), it only seems to take longer from the convert partitions (rfs) step, buts its easier in the long run =)
Click to expand...
Click to collapse
man.....I feel like a moron and I have to be doing something wrong. I can follow directions and my wife says im a good listener. but this is kicking my butt!! I appreciate the help and feel like im bothering asking for hand holding- so I really appreciate your patience.
going ge whiz route..........
after converting to rfs and flashing the kernel from cm11 it boots into TWRP and here in my problems begin.
"-When booted into TWRP do the ALL wipes (except SDCARD)"
if I factory reset all other wipes fail
if I advance wipe first either all four fail or one at a time each fail.
its embarrassing to ask how do I wipe my device, so at least I am glad this is the trouble shooting thread. lol
and thans for the sc_milestone advice, but I don't have that file otherwise I would go that route since you tried it and it works. I searched for milestone but did not find a file named the one you used.
The sc milestone he mentioned is probably the Superclean rom. http://forum.xda-developers.com/showthread.php?t=1350621
Sent from my SCH-I500 using Tapatalk
lightningdude said:
The sc milestone he mentioned is probably the Superclean rom. http://forum.xda-developers.com/showthread.php?t=1350621
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
link
http://d-h.st/ih2m13vt442z/sc3_milestone2_full.zip
tsdsbrk said:
link
http://d-h.st/ih2m13vt442z/sc3_milestone2_full.zip
Click to expand...
Click to collapse
coming from stock, ge whiz (rfs converted) or milestone I am receiving status 7, status 0 or get prop errors in recovery trying to flash anything other than the cm11 kernel
I thought it might be an error in reading sd card error so I changed it once, but it flashes the milestone from the sd card so I am not sure what is going on
did you flash a flash a jelly bean rom before flashing CM 11.1? are you trying to flash the 6 Dec 11.1? I had problems with prior versions also.
tsdsbrk said:
did you flash a flash a jelly bean rom before flashing CM 11.1?
Click to expand...
Click to collapse
yes, Android 4.2.2 runs well
it is the milestone rom flashed through recovery from the sd card.
---------- Post added at 06:19 PM ---------- Previous post was at 05:38 PM ----------
tsdsbrk said:
did you flash a flash a jelly bean rom before flashing CM 11.1? are you trying to flash the 6 Dec 11.1? I had problems with prior versions also.
Click to expand...
Click to collapse
sorry, I didn't see the second question.
yes, 12.6 is the cm 11 build
- First time flashing CM-11.0 to your Galaxy S (or coming from another ROM)?1. Download Rom , Gapps and zip from the below step to sdcard.
2.Reboot into Recovery using 3-button-combo
3.Flash 4.4 kernel zip to gain twrp http://www.androidfilehost.com/?fid=23212708291679682 flash through recovery
4.Reboot recovery and you will now be in twrp
5.Select WIPE: go to advanced (wipe data/factory reset + wipe cache + dalvik cache partition)
6.Install the ROM then install Gapps don't install them simultaneously
my problems begin in step 5
I didn't do the wipe in your step 5. I just flashed the rom.
which jelly bean rom? try helly bean below
http://andromirror.com/file/1386
tsdsbrk said:
I didn't do the wipe in your step 5. I just flashed the rom.
which jelly bean rom? try helly bean below
http://andromirror.com/file/1386
Click to expand...
Click to collapse
Ill try just about anything at this point. Ive been using the helly 20131024, but ill try that one.
this is getting real curious. I do so enjoy pushing these older phones to their limit- this will all be worth it WHEN it works I am sure.
aircooledbusses said:
yes, Android 4.2.2 runs well
it is the milestone rom flashed through recovery from the sd card.
---------- Post added at 06:19 PM ---------- Previous post was at 05:38 PM ----------
sorry, I didn't see the second question.
yes, 12.6 is the cm 11 build
- First time flashing CM-11.0 to your Galaxy S (or coming from another ROM)?1. Download Rom , Gapps and zip from the below step to sdcard.
2.Reboot into Recovery using 3-button-combo
3.Flash 4.4 kernel zip to gain twrp http://www.androidfilehost.com/?fid=23212708291679682 flash through recovery
********4.Reboot recovery and you will now be in twrp********
5.Select WIPE: go to advanced (wipe data/factory reset + wipe cache + dalvik cache partition)
6.Install the ROM then install Gapps don't install them simultaneously
my problems begin in step 5
Click to expand...
Click to collapse
i highlighted the problem in alot of stars( *** ) once u are in TWRP from kernel flash u dont reboot to recovery again, that is whats causeing your errors, i tried to word it as "when u reboot into recovery" as-in when it boots up from kernel flash
try it once moire and it might work better, as when u do that the only partition it thinks u have is the kernel (boot.img, or /boot), thus /syste/ and /data arent being read to flash
as for the status 7, it might be cause the assert (getprop) on the top of the updater-script inside the zip under
META-INF>com>google>android>updater-script
edit it in NOTEPAD++!! and then put back in (without compression to solve some read-errors that could happen sometimes, but compression does make zip work, but sometimes uncompressed works faster for personal use),
then ill attach a zip for u to extract to your desktop, its a program called SignApk (notice its used to sign android zips), u will need to do this EVERY TIME u edit a flashable zip for it to flash right, to use it just extract it all into the same folder, make sure u have java (jre6+, and maybee jdk1.6.0_**+), then drag+drop the zip onto the DragApk.bat program and it will flash it with the same name with an added _signed before the zip, if u put it where your %path% system variable is u can go on command prompt and just type "signapk (zip name u edited) (zip name u want, that has to be different then the edited zip name or u get an empty zip for both)" u can leave out the second zip name and it will just do same name with a "_signed" before the extention, hope this helps =)
Hi everyone !
First, excuse me for my English if it's not perfect, but it's not my main language, so I'll probably do some mistakes
I was with the last official update, un jelly bean.
I wanted to install a custom ROM on my Desire X, so I unlocked my bootloader with the HTCDev website.
It worked perfectly.
Then, I flashed the ClockWorkMod recovery.
I did a full wipe and flashed the ROM SuperSENSE-dx5 1.01
I finally flashed the boot.img of the ROM with the "Boot.img installer RC 4.0". (I did a reboot to bootlader / fastboot to do this)
But I when the phone rebooted, I was on the basic ROM... (just some infos about phone changed) and the other ROM was installed too.
(I know this cause my phone memory "other" was about 2.53go instead of 1.75go like usually)
Someone said me to change the recovery, what I did and flashed the TWRP 2.6.3 ==> Same problem
Used TWRP 2.5 ==> Same problem.
Then, he said me to use the SuperWipe script. I flashed it (ran for 20s, then said "failed", but I had no more OS into my phone, TWRP said it).
So I flashed the ROM and the boot.img like I did al time before.
But now, I have the white screen 'HTC quietly brilliant" and then, a black screen (with the backlight)... It never changes. LED never light up and the phone reboot every 10 minutes, but always stucks on the black screen....
For information:
- Now, if I do the full wipe (3 in 1, in TWRP), it's ok, but if I check cache / Dalvik (into advanced), the recovery says "failed" (If I check system alone, it works).
- If I try a factory reset, now, it runs for 10s then says "failed" too. Anf if I reboot the phone, I'm stuck still stuck to the black screen...
If someone could help me, it would be so nice...
Thanks in advance,
MiMilz
MiMilz said:
Hi everyone !
First, excuse me for my English if it's not perfect, but it's not my main language, so I'll probably do some mistakes
I was with the last official update, un jelly bean.
I wanted to install a custom ROM on my Desire X, so I unlocked my bootloader with the HTCDev website.
It worked perfectly.
Then, I flashed the ClockWorkMod recovery.
I did a full wipe and flashed the ROM SuperSENSE-dx5 1.01
I finally flashed the boot.img of the ROM with the "Boot.img installer RC 4.0". (I did a reboot to bootlader / fastboot to do this)
But I when the phone rebooted, I was on the basic ROM... (just some infos about phone changed) and the other ROM was installed too.
(I know this cause my phone memory "other" was about 2.53go instead of 1.75go like usually)
Someone said me to change the recovery, what I did and flashed the TWRP 2.6.3 ==> Same problem
Used TWRP 2.5 ==> Same problem.
Then, he said me to use the SuperWipe script. I flashed it (ran for 20s, then said "failed", but I had no more OS into my phone, TWRP said it).
So I flashed the ROM and the boot.img like I did al time before.
But now, I have the white screen 'HTC quietly brilliant" and then, a black screen (with the backlight)... It never changes. LED never light up and the phone reboot every 10 minutes, but always stucks on the black screen....
For information:
- Now, if I do the full wipe (3 in 1, in TWRP), it's ok, but if I check cache / Dalvik (into advanced), the recovery says "failed" (If I check system alone, it works).
- If I try a factory reset, now, it runs for 10s then says "failed" too. Anf if I reboot the phone, I'm stuck still stuck to the black screen...
If someone could help me, it would be so nice...
Thanks in advance,
MiMilz
Click to expand...
Click to collapse
Can you give me your cid and hboot number (it should be 1.24 or 1.25)
3845 39594683
GtrCraft said:
Can you give me your cid and hboot number (it should be 1.24 or 1.25)
Click to expand...
Click to collapse
Can you explain what's the "cid" please ? First time I heard about this.
Hboot: 1.25.0002
Radio: 1.15.40.04
MiMilz said:
Can you explain what's the "cid" please ? First time I heard about this.
Hboot: 1.25.0002
Radio: 1.15.40.04
Click to expand...
Click to collapse
It seems you need to use a recovery for JB, and you use a recovery ICS. that's why the flashing fails.
The cid is not important anymore
I tried to flash the each one of the 2 recoveries of this thread: http://forum.xda-developers.com/showthread.php?t=2316662
I boot my phone into Fastboot and use Windroid to flash the recovery.
But with the 2 recovery, when I reboot into bootloader and select recover, I'm still with TWRP 2.5...
I don't understand what's wrong with my phone...
MiMilz said:
I tried to flash the each one of the 2 recoveries of this thread: http://forum.xda-developers.com/showthread.php?t=2316662
I boot my phone into Fastboot and use Windroid to flash the recovery.
But with the 2 recovery, when I reboot into bootloader and select recover, I'm still with TWRP 2.5...
I don't understand what's wrong with my phone...
Click to expand...
Click to collapse
Never use a toolkit if something doesn't work, flash the 2.5 JB version from this thread: http://forum.xda-developers.com/showthread.php?t=2099513
When you are in fastboot do the command fastboot flash recovery ''name of recovery''.img or follow the thread you posted (part 2.4)
had same issue:
I flashed now twrp 2.5 with toolkit, since i remembered reading somewhere, there are problems with 2.6.3.
Superwipe script by xpirt doesn't work for me; either on 2.5, or on 2.6.3.
for now everything's working...
Thank you GtrCraft !
Now, the phone is booting, and the ROM says "Finish boot." (or finishing boot", doesn't really matter), and juste after, I get this message:
"process com.android.phone has stopped"
If I click on "ok", I have the same message with all application (like Google+, etc)...
I have the same issue with and without my sdcard into my phone...
And if i let the phone like this, or click "ok" on every windows, the phone reboot and restart at "finish boot", etc.
MiMilz said:
Thank you GtrCraft !
Now, the phone is booting, and the ROM says "Finish boot." (or finishing boot", doesn't really matter), and juste after, I get this message:
"process com.android.phone has stopped"
If I click on "ok", I have the same message with all application (like Google+, etc)...
I have the same issue with and without my sdcard into my phone...
And if i let the phone like this, or click "ok" on every windows, the phone reboot and restart at "finish boot", etc.
Click to expand...
Click to collapse
You wiped data, dalvik and cache before flashing the rom? and you didn't flash any mods?
GtrCraft said:
You wiped data, dalvik and cache before flashing the rom? and you didn't flash any mods?
Click to expand...
Click to collapse
I flashed the SuperWipe.zip.
But now, I did the wipe (all wipe are ok now !) and it works fine !
Thanks guy, I love you ! :good:
You made my day !
(I wason this problem for 3 days...)
A big thank you ! :highfive:
MiMilz said:
I flashed the SuperWipe.zip.
But now, I did the wipe (all wipe are ok now !) and it works fine !
Thanks guy, I love you ! :good:
You made my day !
(I wason this problem for 3 days...)
A big thank you ! :highfive:
Click to expand...
Click to collapse
You are making me happy for just using my rom :good:
GtrCraft said:
You are making me happy for just using my rom :good:
Click to expand...
Click to collapse
No problems for that, there is not so much ROM and your look like to be the best, so all congratulations go to you and your work dude !
SOLVED
hi, sorry bad english
i got a htc desire x and begann to read this tut about unlockinging, rooting, installing custom roms
http://forum.xda-developers.com/showthread.php?p=36138808#post36138808
i unlocked and rooted the dx, then i installed this rom: STOCK Jelly Bean with Sense 4+ build 2.20.401.6 for Desire X
http://forum.xda-developers.com/showthread.php?t=2239511
were not so happy, would try this one: ViMiRo ROM v1.0-1
http://forum.xda-developers.com/showthread.php?t=2797110
did a full wipe, installed the vimiro rom, Flashed boot.img from zip via fastboot and rebooted
but then the dx stuck on the cyanogenmod logo and nothing more happen
has anyone please a solution for this, or some tipps
SOLVED
4js said:
hi, sorry bad english
i got a htc desire x and begann to read this tut about unlockinging, rooting, installing custom roms
http://forum.xda-developers.com/showthread.php?p=36138808#post36138808
i unlocked and rooted the dx, then i installed this rom: STOCK Jelly Bean with Sense 4+ build 2.20.401.6 for Desire X
http://forum.xda-developers.com/showthread.php?t=2239511
were not so happy, would try this one: ViMiRo ROM v1.0-1
http://forum.xda-developers.com/showthread.php?t=2797110
did a full wipe, installed the vimiro rom, Flashed boot.img from zip via fastboot and rebooted
but then the dx stuck on the cyanogenmod logo and nothing more happen
has anyone please a solution for this, or some tipps
Click to expand...
Click to collapse
what recovery version do you have \ installer ? and post your bootloader details
the rom vimiro has not cyanogenmod logo
[
nek46 said:
what recovery version do you have \ installer ? and post your bootloader details
the rom vimiro has not cyanogenmod logo
Click to expand...
Click to collapse
recovery = twrp 2.6.30
bootloader details - not sure what you mean?
maybe this: hboot 1.25.002
i thought that the vimiro has no cm logo, but when i flashed the rom and fastboot the boot.img i got no errors, it says sucessfully and ok
4js said:
[
recovery = twrp 2.6.30
bootloader details - not sure what you mean?
maybe this: hboot 1.25.002
i thought that the vimiro has no cm logo, but when i flashed the rom and fastboot the boot.img i got no errors, it says sucessfully and ok
Click to expand...
Click to collapse
everything is correct, try another rom, I do not understand why not start the rom
4js said:
hi, sorry bad english
i got a htc desire x and begann to read this tut about unlockinging, rooting, installing custom roms
http://forum.xda-developers.com/showthread.php?p=36138808#post36138808
i unlocked and rooted the dx, then i installed this rom: STOCK Jelly Bean with Sense 4+ build 2.20.401.6 for Desire X
http://forum.xda-developers.com/showthread.php?t=2239511
were not so happy, would try this one: ViMiRo ROM v1.0-1
http://forum.xda-developers.com/showthread.php?t=2797110
did a full wipe, installed the vimiro rom, Flashed boot.img from zip via fastboot and rebooted
but then the dx stuck on the cyanogenmod logo and nothing more happen
has anyone please a solution for this, or some tipps
Click to expand...
Click to collapse
Try flashing another kernel. You somehow flashed the CM boot.img.
nightwalkerkg said:
Try flashing another kernel. You somehow flashed the CM boot.img.
Click to expand...
Click to collapse
Not quite... If he flashed CM boot.img for Sense ROM, he shouldn't see boot animation at all. What he obviously did is flashing a CM ROM and CM boot.img, but one that won't boot the CM ROM. Bootanimation is part of the ROM, not of kernel... So what I would suggest for @4js: Redownload ViMiRo Rom, also redownload any Sense JB kernel from Original Development you like, wipe your phone and reflash everything. That should solve your issues.
nek46 said:
everything is correct, try another rom, I do not understand why not start the rom
Click to expand...
Click to collapse
i tried [ROM][PA 2.99][4.1.2] Paranoid Android UNOFFICIAL [protou] with the double wipe and the gapps and finally
i now stuck at the new paranoid android logo,
nightwalkerkg said:
Try flashing another kernel. You somehow flashed the CM boot.img.
Click to expand...
Click to collapse
i did not, i really double checked it
dansou901 said:
Not quite... If he flashed CM boot.img for Sense ROM, he shouldn't see boot animation at all. What he obviously did is flashing a CM ROM and CM boot.img, but one that won't boot the CM ROM. Bootanimation is part of the ROM, not of kernel... So what I would suggest for @4js: Redownload ViMiRo Rom, also redownload any Sense JB kernel from Original Development you like, wipe your phone and reflash everything. That should solve your issues.
Click to expand...
Click to collapse
i will try and give feedback
not succeded
got it cheap from 2nd hand, could a hardware defect cause the problems?
4js said:
not succeded
got it cheap from 2nd hand, could a hardware defect cause the problems?
Click to expand...
Click to collapse
ok, what exactly did you try?
cause im a beginner in flashing smartphones, there are some things i don't understand
1) when i do a factory reset with twrp 2.6.3.0, there should be wiped data, cache and dalvik, .android_secure
but when i afterwards do a advanced wipe everything succeded, exept dalvik cache, there it fail
2) after a succeded factory reset without os installed, i reboot, and then also i stuck at a boot logo
shouldn't that not be wiped too?
could an other recover.img from http://forum.xda-developers.com/showthread.php?t=2502327 help?
the last succesful rom installed was cm-10.1-20140624-UNOFFICIAL-protou_v2.zip, not the one i wrote in first post
@dansou901
i tried different roms, exactly how it was explained, but never succedded, after rebooting i always stuck at the boot logo
4js said:
cause im a beginner in flashing smartphones, there are some things i don't understand
1) when i do a factory reset with twrp 2.6.3.0, there should be wiped data, cache and dalvik, .android_secure
but when i afterwards do a advanced wipe everything succeded, exept dalvik cache, there it fail
2) after a succeded factory reset without os installed, i reboot, and then also i stuck at a boot logo
shouldn't that not be wiped too?
could an other recover.img from http://forum.xda-developers.com/showthread.php?t=2502327 help?
the last succesful rom installed was cm-10.1-20140624-UNOFFICIAL-protou_v2.zip, not the one i wrote in first post
@dansou901
i tried different roms, exactly how it was explained, but never succedded, after rebooting i always stuck at the boot logo
Click to expand...
Click to collapse
Try the TWRP 2.5.0.0 for JB, it is reported to be most stable. Hopefully this resolves the issues for you.
dansou901 said:
Try the TWRP 2.5.0.0 for JB, it is reported to be most stable. Hopefully this resolves the issues for you.
Click to expand...
Click to collapse
thanks for quick reply, i will try and give then feedback
twrp 2.5.0.0 did it
it was a really full wipe, and now i'm at vimiro 1.01
thanks to everybody for the help, special thanks to dansou901 for helping and his excellent tutorial