Related
I have the Evo LTE S-on (HTC bootloader unlocked) and TWRP installed. The only problem I'm having is that I cannot seem to get .zip files to open from the install menu in TWRP (recovery). I factory reset and try to open the zip from the install menu but it just says "Failed". Specifically I am trying Kushdeck's new CM10 ROM. Any help would be greatly appreciated. Thanks.
PS. Not sure if this will help but on the install menu my files show up twice, the first time with the normal naming and the second with "/." in front of them.
Did u try and re download it again? Sounds like a bad DL if it keeps failing after a couple of attempts
Sent from my EVO using Tapatalk 2
Ok I'm trying that now. I'm also wondering if there's a problems with my /ext-sd because everytime I factory reset it says it couldn't access that. Do you think that has anything to do with it? Is reinstalling TWRP an option?
Ok thanks so much the re-download did it. But now I'm at a black/blank screen after start up. I factory reset, installed the CM10 ROM then Gapps and wiped the dalvik/cache. Then when I reboot it just goes to the HTC screen and after that nothing. Ideas?
This is going to sound strange but try factory restet, wipe cache/dalvik and then just reboot without trying to flash anything.. I've been having some similar issues as mine isn't recoglizing any MD5 when i try to flash a new rom.. I wiped my phone and have tried to flash a few roms and it fails every time and in wiping my phone it somehow took out my backup so without any other options (that I knew of) I just rebooted and luckily it loaded a completely bare vipor rom like what I started out with when I originally rooted.. BTW, did you create a backup before trying to flash? Should always make a backup....
Ya I had backed up. Turns out I needed to manually flash the boot.img which fixed the issue
elitelimfish said:
Ya I had backed up. Turns out I needed to manually flash the boot.img which fixed the issue
Click to expand...
Click to collapse
Thanks for this. I had the same problem, (S-ON, TWRP. black screen on boot). I was able to flash stock-based ROMs, but not CM10, so I suspected it had something to do with the things that HTCDev won't allow the recovery access to, but the logs from TWRP didn't throw any errors, so while I suspected boot, I didn't know what to do about it. And everyone knows that it's easy to be caviler with everything is working, but as soon as you start having problems, you get gun shy about trying things.
Your post was the solution for me. Extract the boot.img file found inside the zip or your chosen ROM, and flash it using fastboot:
"fastboot flash boot boot.img"
heywetried said:
Thanks for this. I had the same problem, (S-ON, TWRP. black screen on boot). I was able to flash stock-based ROMs, but not CM10, so I suspected it had something to do with the things that HTCDev won't allow the recovery access to, but the logs from TWRP didn't throw any errors, so while I suspected boot, I didn't know what to do about it. And everyone knows that it's easy to be caviler with everything is working, but as soon as you start having problems, you get gun shy about trying things.
Your post was the solution for me. Extract the boot.img file found inside the zip or your chosen ROM, and flash it using fastboot:
"fastboot flash boot boot.img"
Click to expand...
Click to collapse
Hey out of curiosity did you like any of the stock based ROMs? If so which ones? I kinda wanna try one out but haven't settle on one
I have SGP311 4.2.2 stock rooted with this kernel and regularly I am trying to install varius custom ROMS but I am always getting Error Status 7 and flashing stops. The only way to overcome this issue is to install first the boot.img from the ROM that I am going to install and then through the Recovery of the new boot.img I can install the custom ROM without errors.
I know this is not a normal behaviour and I am trying to figure out what's wrong. I tried to edit updater-script by removing all the getprop lines but then I got the same error when the set_perm command is executed.
Could you help me ?
Thanks!
i had the same issue
nikal said:
I have SGP311 4.2.2 stock rooted with this kernel and regularly I am trying to install varius custom ROMS but I am always getting Error Status 7 and flashing stops. The only way to overcome this issue is to install first the boot.img from the ROM that I am going to install and then through the Recovery of the new boot.img I can install the custom ROM without errors.
I know this is not a normal behaviour and I am trying to figure out what's wrong. I tried to edit updater-script by removing all the getprop lines but then I got the same error when the set_perm command is executed.
Could you help me ?
Thanks!
Click to expand...
Click to collapse
i had the same issue while i was flashing cyanogen mod 10.1.3 , any ways i kept trying, i still recieved an error
afterwards i tried to download the rom again and then i placed it into my internal sd storage, after soo many tries, i finally got it working
maybe its the issue with your zip file, try downloading it again, place it into your internal storage, not external, then flash it
hassanman1997 said:
i had the same issue while i was flashing cyanogen mod 10.1.3 , any ways i kept trying, i still recieved an error
afterwards i tried to download the rom again and then i placed it into my internal sd storage, after soo many tries, i finally got it working
maybe its the issue with your zip file, try downloading it again, place it into your internal storage, not external, then flash it
Click to expand...
Click to collapse
Hi and thank you for the reply.
I tried to install from the internal flash though I didn't believe that the result would be different and I had the message (set_perm Error Status 7). It's very strange that no other users mentiong this problem. I am thinking maybe it's something with my stock ROM or some other setting.
nikal said:
Hi and thank you for the reply.
I tried to install from the internal flash though I didn't believe that the result would be different and I had the message (set_perm Error Status 7). It's very strange that no other users mentiong this problem. I am thinking maybe it's something with my stock ROM or some other setting.
Click to expand...
Click to collapse
i think you have mentioned that you flashed the boot.img before you tried flashing the rom, i would recommend to flash the right boot.img again from the rom, this is the most common issue when u get status 7 error,
other wise, backup all of your important data, return to stock by using flash tool / factory data reset, root again and then flash the boot.img and then flash the rom
thats what i do when im desperate for the rom :laugh:
Hello ,
since two days i am trying to install a custom rom on my htc desire x. I repeated every single step several times to make sure everything still is fine.
(unlook, flash boot, flash recovery / tried twmp and cwm, etc..)
The only rom which works for me ist the cM10-2-20138004-unofficial. But with restrictions. WLAN doesn't work, media manager isn't starting. Cant hear the partner when calls are incoming.
I tried mySense, Half_Sense, myOnedx, but after finishing installation the device hangs on startup. I waited hours and minutes but nothing happened.
I tried several RUU´s but can't find the right ones for me, or i got the 155 error message.
There is no OS installed on the device. How can i get the device up an running? I would be really happy if somebody can give me a hint whats going wrong.
Thx in advance
Dont worry all ****s can be fixed.Wha is ur hboot ? Or simply before to try to install custom rom U was with ICS rom or JB ?.You have to use the right recovery.Look what rom you want to flash, if you on ics hboot u cant just flash jb room (Some roms already have this funcion)
Ps:
After flasing the rom go in boothloader and flash boot.img And away do full wipe
What you need to make sure when installing a ROM: Install a suitable kernel. When installing a Sense ROM, install a Sense custom kernel or the stock kernel. Installing CM isn't advisable, because it's not ready for daily use yet. Also, make sure you use the right recovery for right hboot.
Good Morning,
thx for reply. I want to install the myOnedx_RC4.0 FX. I extracted the boot.img from zip. Installed the rom, wiped, reboot and installed the boot.img.
But that failed. Again, the cyanogen start up occurs for hours and hours. The device doesnt start.
Also tried the same wir the mySENSEdx5_RC4
I evem tried to install the nexuskernelv3.img
I am on hboot 1.25.002
Anyone an idea what wrong with my installation?
Thx
Again: Which custom recovery are you using? Please post a link to the thread here, so we can see what you've installed. Also, as first time user, you should check this and this.
Sorry i forgot. I am using TWRP 2.6.3.0 as custom recovery
Ok, strange, as this one works for me without problems. However, try the 2.5.0.0 version for JB and see if it goes without problems then. Also be sure to wipe system, dalvik cache, cache and data partition before installing a new ROM.
Same with version 2.5.0.0. I tried clockworkmod recovery, but as soon as i try to wip i got the error messages:
cant mount cache/recovery
cant open cache/revocery
So how can i get back to a stock rom? I tried the way described in here: http://forum.xda-developers.com/showthread.php?p=41327224
, but restore failed.
Any other ideas?
If you want to get back to stock, you need to know your CID first. After that, check this thread: http://forum.xda-developers.com/showthread.php?t=2324815
As you have JB hboot, you need to restore a JB backup. In the thread I linked you to are backups of several CIDs. If yours isn't there, you won't be able to return to stock.
Ok thanks. So it is not in there. I got the cid VODAP102.
Does that mean my device is gone? Or can i even try other workarounds?
Thanks
So i installed odexed rom and this one works fine. Do not know why all the other roms not working to me.
Maybe anyone an idea.
Otherwise thanks for your support.
Lastmenstanding said:
Does that mean my device is gone? Or can i even try other workarounds?
Thanks
Click to expand...
Click to collapse
Your hboot : 1.25.0002
Recovery to flash - JB recovery download from here : http://d-h.st/VjM
fastboot flash recovery command : fastboot flash recovery recovery.img
For a test ROM to flash, flash this stock ROM : http://forum.xda-developers.com/showthread.php?t=2239511
also make sure to fastboot flash boot boot.img
(boot.img is attached on OP)
Once everything run, it is up to you to try any other ROM and any other boot.img
Lastmenstanding said:
So i installed odexed rom and this one works fine. Do not know why all the other roms not working to me.
Maybe anyone an idea.
Otherwise thanks for your support.
Click to expand...
Click to collapse
It's either you flash ROM with wrong recovery type or wrong boot.img type or ROM which is not supported on your hboot.
Simple rules:
1) Recovery must be a recovery for JB.
2) Correct boot.img for correct ROM
ICS ROM that support hboot 1.25.0002
Recovery : JB recovery is a must
Boot.img : ICS boot.img is a must
JB ROM which should run fine on hboot 1.25.0002
Recovery : JB recovery is a must
Boot.img : JB boot.img is a must
ICS ROM that does not support hboot 1.25.002 - you need to manually change the mountpoint in updater-script, then
Recovery : JB recovery is a must
Boot.img : ICS boot.img is a must
Yeah, that was the problem, I see now... Have been blind a bit... The ROMs OP has installed on his phone are all ICS ROMs which need changing of updater-script mountpoints. That's why they won't work. @Lastmenstanding: Try any JB ROM available in Android Development section, should work without problems. The ROMs you tried were ICS ROMs especially written for ICS hboot, that's why they didn't work on your phone.
dansou901 said:
Yeah, that was the problem, I see now... Have been blind a bit... The ROMs OP has installed on his phone are all ICS ROMs which need changing of updater-script mountpoints. That's why they won't work. @Lastmenstanding: Try any JB ROM available in Android Development section, should work without problems. The ROMs you tried were ICS ROMs especially written for ICS hboot, that's why they didn't work on your phone.
Click to expand...
Click to collapse
OP mentioned about installing my ICS ROMs. Both ICS ROMs work on JB hboot without a need to edit the updater-script. My guess is he either use wrong recovery (ICS recovery is wrong) or wrong boot.img (JB boot.img is wrong) as it should be JB Recovery and ICS boot.img
..do not know how to use the thank meter, but..
Thank you guys for your excellent support.
Lastmenstanding said:
..do not know how to use the thank meter, but..
Thank you guys for your excellent support.
Click to expand...
Click to collapse
Just thank them at the bottom of their posts...
There is a thanks button at the bottom of every post.
Hey,
I got a problem with my S2g. I'm currently on Android 4.1.2, with cwm 6 and blazing v-5 kernel. Both were flashed per odin and work fine. However I can't flash a custom rom. Every time I try it I'll get a Status 7 error. I've already tried 4 different ROMs and I'm really annoyed by now. I also tried to factory reset the phone before I flash the ROM, but it didn't make any difference. I also tried deleting the assert command in the updater-script file but somehow my changes in the file won't be saved.
If anyone could help me I would be really thankful!
http://forum.xda-developers.com/galaxy-s2/help/to-mod-s2-t3189884
I've just tried this, didn't work also. I even had to flash the recovery and the kernel again after trying to flash the file in the link, because the phone wouldn't boot normal or in recovery mode.
mcb25 said:
Hey,
I got a problem with my S2g. I'm currently on Android 4.1.2, with cwm 6 and blazing v-5 kernel. Both were flashed per odin and work fine. However I can't flash a custom rom. Every time I try it I'll get a Status 7 error. I've already tried 4 different ROMs and I'm really annoyed by now. I also tried to factory reset the phone before I flash the ROM, but it didn't make any difference. I also tried deleting the assert command in the updater-script file but somehow my changes in the file won't be saved.
If anyone could help me I would be really thankful!
Click to expand...
Click to collapse
Try using philz recovery on your phone. It should flash most ROMs fine.
gsstudios
gsstudios said:
Try using philz recovery on your phone. It should flash most ROMs fine.
Click to expand...
Click to collapse
I just did, I still get the Status 7 error. I tried to flash the cm 12.1 and the cm 13.0 nightly rom. I also tried deleting the assert command in the updater-script file but it still won't work. There was no Status 7 error but it still said "Installation aborted".
Does anyone else got an idea how to fix this?
http://forum.xda-developers.com/galaxy-s2/development/kernel-blazing-kernel-v16-t2275275
I used this Kernel, I just noticed, that it's only compatible with Android 4.1, 4.2 or 4.3.
I then tried to install the DorimanX Kernel for LP and MM (http://forum.xda-developers.com/galaxy-s2/development-derivatives/kernel-dorimanx-lp-5-x-x-t3145879) but my phone stucks at the boot screen.
mcb25 said:
http://forum.xda-developers.com/galaxy-s2/development/kernel-blazing-kernel-v16-t2275275
I used this Kernel, I just noticed, that it's only compatible with Android 4.1, 4.2 or 4.3.
I then tried to install the DorimanX Kernel for LP and MM (http://forum.xda-developers.com/galaxy-s2/development-derivatives/kernel-dorimanx-lp-5-x-x-t3145879) but my phone stucks at the boot screen.
Click to expand...
Click to collapse
Apologies, I only just noticed you have a i9100g, not a i9100. You can't just flash i9100 kernels as they simply won't work!
You can follow the guide in the CM13 OP here:
http://forum.xda-developers.com/galaxy-s2/development/rom-cyanogenmod-13-0-t3381511
gsstudios
Somehow I feel like a noob. I wanted to see what the new stock Android 10 was like, so I installed it via Odin. But now I can't get back to a custom ROM because TWRP fails to flash. The tablet's bootloader is still unlocked and I've enabled Dev mode. Download the latest twrp-3.4.0-3-gts4lvwifi.img.tar and put it in AP. When I click start, I get this error "Can't open the specified file (Line 1892)"
edit: Still don't know what I did wrong the first time, but I started over from scratch, flashed stock 10 again, vbmeta, twrp and it worked. Of course I let it boot and set Dev mode between each flash. Once into TWRP, formated data, wiped and install cDroid and gapps and it is now working.
lewmur said:
Download the latest twrp-3.4.0-3-gts4lvwifi.img.tar and put it in AP.
Click to expand...
Click to collapse
Glad you got it working. Figured I'd mention though there is a newer TWRP. 3.4.0-4 didn't give me any issues.
lewmur said:
Somehow I feel like a noob. I wanted to see what the new stock Android 10 was like, so I installed it via Odin. But now I can't get back to a custom ROM because TWRP fails to flash. The tablet's bootloader is still unlocked and I've enabled Dev mode. Download the latest twrp-3.4.0-3-gts4lvwifi.img.tar and put it in AP. When I click start, I get this error "Can't open the specified file (Line 1892)"
edit: Still don't know what I did wrong the first time, but I started over from scratch, flashed stock 10 again, vbmeta, twrp and it worked. Of course I let it boot and set Dev mode between each flash. Once into TWRP, formated data, wiped and install cDroid and gapps and it is now working.
Click to expand...
Click to collapse
Stock a10 sucked?