Related
There is a guide on how to flash a new radio on the One S, but its outdated and obsolete.
While we still dont have S-OFF yet, there is a trick that lets you flash radio images.
Requirements.
The latest TWRP recovery image. Available here.
Grab the latest US or EU radio here and copy it to your SD Card. (adb push filename.zip /sdcard/radio.zip) Click the changelog-button to see which radio's are US and EU.
Lets get flashing
Reboot your device into the bootloader.
Code:
adb reboot bootloader
Use fastboot to boot up into recovery.
Code:
fastboot boot openrecovery-twrp-2.3.1.0-ville.img
You will boot directly into recovery from the recovery image, and no restrictions apply. Now simply flash the radio.zip file that you pushed over earlier, and you're all set!
Enjoy!
Credits to xkonni for the tip!
Is it really bad if I flash a EU radio on my TMOBUS device? I have done so 24hrs ago and notice very fast speeds and good signal strength. I don't get why there is a difference.
Closed Source Project said:
Is it really bad if I flash a EU radio on my TMOBUS device? I have done so 24hrs ago and notice very fast speeds and good signal strength. I don't get why there is a difference.
Click to expand...
Click to collapse
i would like to know the answer to this also
No it works great on my tmobile one s no problems here
sent from a guy living in a van down by the river
Untouchab1e said:
There is a guide on how to flash a new radio on the One S, but its outdated and obsolete.
While we still dont have S-OFF yet, there is a trick that lets you flash radio images.
Requirements.
The latest clockwork recovery image. Available here. Make sure you get the latest version for the Ville. (released on or after 29-apr-2012).
Grab the latest US or EU radio here and copy it to your SD Card. (adb push filename.zip /sdcard/radio.zip) Click the changelog-button to see which radio's are US and EU.
Lets get flashing
Reboot your device into the bootloader.
Code:
adb reboot bootloader
Use fastboot to boot up into recovery.
Code:
fastboot boot recovery-clockwork-5.5.0.4-ville.img
You will boot directly into recovery from the recovery image, and no restrictions apply. Now simply flash the radio.zip file that you pushed over earlier, and you're all set!
Enjoy!
Credits to xkonni for the tip!
Click to expand...
Click to collapse
got the same result by just rebooting into bootloader, then choosing fastboot>recovery.....then chose radio.zip i placed on "sdcard"...never having to plug phone into PC
On leedroid without the radio it gets about 12mb but with this radio i get 10mb, when i load the same site, this radio loads about 2seconds faster..tmobUS thanx btw
I too just flashed the .zip from Clockwork Recovery from my T-Mobile US phone for the EU radio. Working just fine.
I'm getting an error when I enter stock recovery that it can't find /sdcard cause the file doesn't exist... a little help please
ralph96gt said:
I'm getting an error when I enter stock recovery that it can't find /sdcard cause the file doesn't exist... a little help please
Click to expand...
Click to collapse
Had the exact same problem as you.
I just flashed the recovery with CWM recovery image. The one in this topic didn't work for me cause it wouldn't mount the /sdcard either. I used a different version.
Then I just installed the radio.zip from this topic.
So if I have the last CWM, just I have to put the zip to the SD, and flash it from recovery?
Edit: The radio I have now is the 0.15.31501S.19_2_10.13.31501S.06L
cualla84 said:
So if I have the last CWM, just I have to put the zip to the SD, and flash it from recovery?
Edit: The radio I have now is the 0.15.31501S.19_2_10.13.31501S.06L
Click to expand...
Click to collapse
From what Ive been told, and what I did, was to boot directly into the latest recovery image. Meaning, you dont flash the recovery image first, you simply fastboot boot into it, then you flash the radio.zip from there.
Again, make sure you pick the newest version of the recovery image.
Untouchab1e said:
From what Ive been told, and what I did, was to boot directly into the latest recovery image. Meaning, you dont flash the recovery image first, you simply fastboot boot into it, then you flash the radio.zip from there.
Again, make sure you pick the newest version of the recovery image.
Click to expand...
Click to collapse
Thank you! I have the CWM 5.8.3.1. I have to wipe before flashing?
cualla84 said:
Thank you! I have the CWM 5.8.3.1. I have to wipe before flashing?
Click to expand...
Click to collapse
No, you dont have to wipe data before flashing a new radio.
Untouchab1e said:
No, you dont have to wipe data before flashing a new radio.
Click to expand...
Click to collapse
Thank you very much! I'll make a nandroid my rom, and flash radio and alpha8 of CM9
cualla84 said:
Thank you very much! I'll make a nandroid my rom, and flash radio and alpha8 of CM9
Click to expand...
Click to collapse
Sounds like a good plan! Enjoy Alpha8. Nightly builds are available too (check signature)
Untouchab1e said:
Sounds like a good plan! Enjoy Alpha8. Nightly builds are available too (check signature)
Click to expand...
Click to collapse
Better then flash the nightly? What improvements have regarding alpha8? I can´t see the features!
cualla84 said:
Better then flash the nightly? What improvements have regarding alpha8? I can´t see the features!
Click to expand...
Click to collapse
No Ville-specific improvements, just the latest CM9 commits. Its basically the exact same ROM, just with the latest CM9 improvements.
Thanks Untouchab1e!
Untouchab1e said:
No Ville-specific improvements, just the latest CM9 commits. Its basically the exact same ROM, just with the latest CM9 improvements.
Click to expand...
Click to collapse
OK! I will charge the battery and I get to it!
Flashed 1.78 EU radio to stock tmous and I'm getting zero issues and excellent battery life so far. Thx
Sent from my HTC VLE_U using xda premium
flash directly from cwm?
having already unlocked, root and flashed the latest cwm, can't i just move the radio.zip file to the phone and flash directly in cwm instead of all commands?
Wanting to try a different kernel but wanting to go back to stock if it doesn't go well (stock kernel). I know how to flash a kernel but not sure how to get back to stock kernel.
Just flash the stock kernel like anything else.
iElvis said:
Just flash the stock kernel like anything else.
Click to expand...
Click to collapse
Not sure exactly where to find that though. I believe also there is a difference between cm10 and sense kernel though, correct?
Also curious if since I've flashed a jb sense rom if my kernel also updated to jb kernel
scabbard1 said:
Not sure exactly where to find that though. I believe also there is a difference between cm10 and sense kernel though, correct?
Also curious if since I've flashed a jb sense rom if my kernel also updated to jb kernel
Click to expand...
Click to collapse
You need a sense kernel for sense roms, and cm/aosp/aokp kernels for those roms.
Stock no-wp sense kernel here: http://forum.xda-developers.com/showthread.php?t=2150219
Check About>Software information>More and it will tell you what kernel you're on.
If you flash a ROM, it will flash a kernel with the ROM. You can find that kernel in the ROM zip file (boot.IMG). Extract that file and flash it using fastboot to return to the kernel that was packaged with your ROM.
Sent from my One X using Tapatalk 2
jeffwyeh said:
If you flash a ROM, it will flash a kernel with the ROM. You can find that kernel in the ROM zip file (boot.IMG). Extract that file and flash it using fastboot to return to the kernel that was packaged with your ROM.
Click to expand...
Click to collapse
If hboot is <1.14 (or you are S-off), the kernel will just flash as the ROM. You can just dirty flash the ROM again.
If hboot is 1.14 or greater (and S-on), just extract boot.img and flash in fastboot as mentioned above. Kernel is part of boot.img.
Thanks so much for this info. I was going to post the same question
Question: Is the boot.img the kernel file? Thanks
petey006 said:
Thanks so much for this info.
Click to expand...
Click to collapse
There's a button for that.
petey006 said:
Question: Is the boot.img the kernel file? Thanks
Click to expand...
Click to collapse
Yes. But you can't flash just a boot.img in recovery. You would need fastboot for that. If you want the commands they're in the general stickies or I can post them here.
Sent from Xparent Red using my Venomized Evita
ImagioX1 said:
Yes. But you can't flash just a boot.img in recovery. You would need fastboot for that.
Click to expand...
Click to collapse
Depends on the hboot version and S-On or Off. But I already discussed those above.
---------- Post added at 11:30 AM ---------- Previous post was at 11:26 AM ----------
petey006 said:
Question: Is the boot.img the kernel file?
Click to expand...
Click to collapse
As I already said, the kernel is a part of boot.img.
There are other things in boot.img besides just the kernel:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images#Structure_of_boot_and_recovery_images
Although the terms boot.img and kernel are used nearly synonymously here. When "kernels" are posted, I think its always the entire boot.img package.
And in regards to your original question, it doesn't really matter.
To return to the stock kernel, just flash the stock boot.img.
redpoint73 said:
Depends on the hboot version and S-On or Off.
Click to expand...
Click to collapse
So you can flash a straight boot.img not in a zip or anything through recovery with s-off?
Sent from Xparent Red using my Venomized Evita
ImagioX1 said:
So you can flash a straight boot.img not in a zip or anything through recovery with s-off?
Click to expand...
Click to collapse
Wait, no. I was misunderstanding you. The kernel has to be a flashable zip to be able to install from recovery. Otherwise, I think you are right, if you just have the boot.img, you need to install with fastboot.
I've noticed that some kernel only works with sense roms (ElementalX).
Say for example, i want to flash another rom without sense ui.
Do i need to reflash stock kernel first? Or flash the boot.img (kernel?) inside the new rom zip file?
Also the stock kernel from the link has two files. One is "installer" and the other is boot.img. I need to install the installer file thur Recovery, correct? And also flash the boot.img to go back to stock?
Thanks i'm such a n00b.
petey006 said:
I've noticed that some kernel only works with sense roms (ElementalX).
Say for example, i want to flash another rom without sense ui.
Do i need to reflash stock kernel first? Or flash the boot.img (kernel?) inside the new rom zip file?
Click to expand...
Click to collapse
Sense requires a Sense kernel.
AOSP based ROMs require an AOSP kernel.
In general, you should install the kernel for the ROM that you are flashing. Some kernels may work over more than one ROM (do the research before you try it), but never a Sense kernel for an AOSP ROM, or vice versa.
petey006 said:
I've noticed that some kernel only works with sense roms (ElementalX).
Also the stock kernel from the link has two files. One is "installer" and the other is boot.img. I need to install the installer file thur Recovery, correct? And also flash the boot.img to go back to stock?
Click to expand...
Click to collapse
One or the other, you don't need both. If you are hboot 1.14 or higher, I don't know if the installer way will work. The boot.img way (in fastboot) will work, no matter what hboot you are on.
redpoint73 said:
Wait, no. I was misunderstanding you. The kernel has to be a flashable zip to be able to install from recovery. Otherwise, I think you are right, if you just have the boot.img, you need to install with fastboot.
Click to expand...
Click to collapse
I was about to say!! Thanks for clarifying.
Sent from Xparent Red using my Venomized Evita
Hiya. Any help appreciated here, Got hold of a Rogers One X (evita)
Heres where I am at right now:
I unlocked the bootloader and attempted to flash CM11 (Got an error regarding update package) *I made no backup- Noob, I know.*
Now, at the very most all I can get into is CWM/TWRP (I can flash both of these without issue using fastboot)
I have attempted to re-lock the bootloader (which says relocked) but I have tried the 2 rogers RUU files I managed to find and both fail with an error 115 and leave me on the htc logo, and boot to bootloader only.
I tried to flash some custom roms, some seem to flash ok but just boot-loop.
I am not SuperCID, and the phone is S-ON.
Hboot-2.14.0000
Radio-0.23a.32.09.29
Nov 26, 2012
I cannot figure what to do next. I dont care what goes on the phone as long as i can get it working. Its been a long time since I messed with android, I only bought this phone for this reason lol, but I made the mistake of staying up too late and probably skipping half of the tutorials i was following.
Any help appreciated.
:laugh:
What version of TWRP are you using? Why did you relock the bootloader? You should unlock that again. Did you flash the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP? You need to do this because you're s-on. You should read the Evita FAQ thread in my signature, as well as the How-To Guide For Beginners thread.
Sent from my Evita
timmaaa said:
What version of TWRP are you using? Why did you relock the bootloader? You should unlock that again. Did you flash the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP? You need to do this because you're s-on. You should read the Evita FAQ thread in my signature, as well as the How-To Guide For Beginners thread.
Sent from my Evita
Click to expand...
Click to collapse
Wow, timmaaa, thanks for the superfast answer chap!
So, unlock the bootloader, flash the Rom (CM11), then the Boot.img extracted from the rom via fastboot?
Sounds like a plan. I will try that now. I think to be honest, I came home last night and ended up following a bit of one tut, a bit of another, and never really read properly. Call it friday evening alcohol induced noobness syndrome.
That should be it. You need to make sure you use the correct version of TWRP though, you're looking for the unofficial modified TWRP 2.6.3.0 by jrior001 in our Original Android Development section.
Sent from my Evita
timmaaa said:
That should be it. You need to make sure you use the correct version of TWRP though, you're looking for the unofficial modified TWRP 2.6.3.0 by jrior001 in our Original Android Development section.
Sent from my Evita
Click to expand...
Click to collapse
Thank you. The boot.img thing got me a bit further so far. I will get that version of TWRP installed and try the CM11 again, as i think thats where I want to be at. It should be as simple as CM11 flash, Boot.img flash, then Gapps and im done, right?
Perform a full wipe (cache/dalvik cache/factory reset/system), flash CM, flash gapps, flash boot.img, reboot into ROM.
Sent from my Evita
timmaaa said:
That should be it. You need to make sure you use the correct version of TWRP though, you're looking for the unofficial modified TWRP 2.6.3.0 by jrior001 in our Original Android Development section.
Sent from my Evita
Click to expand...
Click to collapse
Ok one last question Timmaaa, I have installed that TWRP, flashed CM11, also Gapps and the boot.img , and now I just get the rom bootlogo (spinning cyanogen etc) and nothing, it just sits there. Is there anything else that may need to be done? If theres not anything obvious, ill go read some more!
Thanks for the help so far!
scibot said:
Ok one last question Timmaaa, I have installed that TWRP, flashed CM11, also Gapps and the boot.img , and now I just get the rom bootlogo (spinning cyanogen etc) and nothing, it just sits there. Is there anything else that may need to be done? If theres not anything obvious, ill go read some more!
Thanks for the help so far!
Click to expand...
Click to collapse
What is the filename of the ROM zip you flashed? Did you check the md5 of the file after you downloaded it? Are you sure the flashing of the boot.img was successful?
Timmaaa, it seems it just took ages. I went downstairs for some juice, came back up and there it was, the setup screen! Beautiful.
Thanks for the help, it seems its not the technical i need to brush up on, but my paying attention and reading - lol!
Thanks again man! :good:
Hey guys,
today I got my HTC One S s4. I directly opened the bootloader, installed twrp2.5.0.0 and flashed vanir rom. Afterwards I stuck in a bootloop. Went back into recovery and flashed TwistedKat, next bootloop. Flashed twrp2.6.3.0 from the cm11.2 thread. Reboot into recovery and installed the cm11 rom another time bootloop. So i flashed ClockworkMod 6.0.4.5 and flashed cm11 another time and bootloop. Now I don't really don't know what to do and what the problem is.
Hope you guys can help me out
cheers,
finn
Finnit0 said:
Hey guys,
today I got my HTC One S s4. I directly opened the bootloader, installed twrp2.5.0.0 and flashed vanir rom. Afterwards I stuck in a bootloop. Went back into recovery and flashed TwistedKat, next bootloop. Flashed twrp2.6.3.0 from the cm11.2 thread. Reboot into recovery and installed the cm11 rom another time bootloop. So i flashed ClockworkMod 6.0.4.5 and flashed cm11 another time and bootloop. Now I don't really don't know what to do and what the problem is.
Hope you guys can help me out
cheers,
finn
Click to expand...
Click to collapse
Did you flash the kernel (boot.img) via fastboot immediately after flashing the rom?
As LS. xD already said: You have to flash the Kernel in fastboot.
Extract the boot.img from the cm zip and type in fastboot
flash boot boot.img
Gesendet von meinem HTC One S mit Tapatalk
LS.xD said:
Did you flash the kernel (boot.img) via fastboot immediately after flashing the rom?
Click to expand...
Click to collapse
?jonas! said:
As LS. xD already said: You have to flash the Kernel in fastboot.
Extract the boot.img from the cm zip and type in fastboot
flash boot boot.img
Click to expand...
Click to collapse
Actually thats it! Thanks a lot! Didn't read about it in any flashing instructions. And I don't really understand why it is necessary to flash the boot.img [Kernel] seperately?
cheers,
Finn
Finnit0 said:
Actually thats it! Thanks a lot! Didn't read about it in any flashing instructions. And I don't really understand why it is necessary to flash the boot.img [Kernel] seperately?
cheers,
Finn
Click to expand...
Click to collapse
Security flag (S-ON) blocks writing boot partition via Recovery. Unlocked bootloader allows writing boot partition via fastboot only. Have you tried getting S-OFF yet?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
LS.xD said:
Security flag (S-ON) blocks writing boot partition via Recovery. Unlocked bootloader allows writing boot partition via fastboot only. Have you tried getting S-OFF yet?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
So far I haven't, future plans because I would like to update to the 1.35a.32.45.27 radio from the One XL and sounds like it makes flashing quiet easier. But so far I don't see a way without windows pc? I am on mac .
cheers Finn
Finnit0 said:
So far I haven't, future plans because I would like to update to the 1.35a.32.45.27 radio from the One XL and sounds like it makes flashing quiet easier. But so far I don't see a way without windows pc? I am on mac .
cheers Finn
Click to expand...
Click to collapse
Working adb on your PC. Yes, that means OS X, linux, Windows, etc. are all supported. --> FIREWATER S-OFF
LS.xD said:
Working adb on your PC. Yes, that means OS X, linux, Windows, etc. are all supported. --> FIREWATER S-OFF
Click to expand...
Click to collapse
Thanks man, you have helped quiet a lot with the start of using my One S. One more question. Is it worth it to update to hboot 2.16.00?
cheers Finn
Finnit0 said:
Thanks man, you have helped quiet a lot with the start of using my One S. One more question. Is it worth it to update to hboot 2.16.00?
cheers Finn
Click to expand...
Click to collapse
Just some Sense based roms are running on HBoot 2.16. I prefer AOSP based roms e.g. PAC or TwistedKat Most roms are for HBoot 2.15
Sent from my beloved HTC One S using (most time buggy) Tapatalk
I have a one xl cid rogers001 hboot 2.14, baseband 0.23a.3 2.09.29.... jb 4.1 with sense 4+
I tried unlock bootloader by htcdev => ok
install recovery => ok. and when i installed this rom: http://forum.xda-developers.com/showthread.php?t=1868236, it was stuck in bootloader. i fogot root my phone before.
so i relock my device, and tried to flash this stock rom using adb : OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.3 2.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl 6j.zip (was found in this thread: http://forum.xda-developers.com/showthread.php?t=2119610)
On cmd via fastboot i type fastboot erase cache =>ok
fastboot oem rebootRUU => ok
fastboot flash zip "filename.zip" It says " (remote: 12 signature verify fail") in the end cmd
What should i do now?
Thanks for reading and help me pls!!!!
Ok, first mistake is that you thought you needed to be rooted to flash the Viper ROM, you don't. All you need is an unlocked bootloader and custom recovery, which you had. You were probably stuck in the bootloader because you forgot to flash the boot.img from the ROM zip with fastboot, you need to do this because you're s-on.
The next mistake you made was attempting to flash an OTA. I don't know what made you think that you could do that but it definitely wasn't found in this forum (or anywhere for that matter). An OTA is only a partial OS, it relies on the correct stock OS to already be installed on the device to build on top of to update the existing OS. It failed for obvious reasons.
Unlock your bootloader again, flash a custom recovery again, and flash the ROM again. Make sure you flash the boot.img this time and it should boot right up. I'd strongly recommend you read the Evita FAQ thread and the How-To Guide For Beginners thread in my signature. Diving into modifying your device without the proper level of knowledge is a really bad idea.
Sent from my Evita
timmaaa said:
Ok, first mistake is that you thought you needed to be rooted to flash the Viper ROM, you don't. All you need is an unlocked bootloader and custom recovery, which you had. You were probably stuck in the bootloader because you forgot to flash the boot.img from the ROM zip with fastboot, you need to do this because you're s-on.
The next mistake you made was attempting to flash an OTA. I don't know what made you think that you could do that but it definitely wasn't found in this forum (or anywhere for that matter). An OTA is only a partial OS, it relies on the correct stock OS to already be installed on the device to build on top of to update the existing OS. It failed for obvious reasons.
Unlock your bootloader again, flash a custom recovery again, and flash the ROM again. Make sure you flash the boot.img this time and it should boot right up. I'd strongly recommend you read the Evita FAQ thread and the How-To Guide For Beginners thread in my signature. Diving into modifying your device without the proper level of knowledge is a really bad idea.
Sent from my Evita
Click to expand...
Click to collapse
fisrt, thanks for helping me. but i've flash boot boot.img file in .zip after i install rom from sdcard. after that, phone stuck in bootloader.
i've unlock bootloader and flash recovery again, and now it says can't mount sdcard. how can i copy viper rom into internal storage? sideload? flash zip? and after all, my phone still not root, can flash viper rom without root?
sorry for my english. thanks again!
somebody help me pls
veveve said:
somebody help me pls
Click to expand...
Click to collapse
Please be patient, we all have lives outside XDA.
veveve said:
fisrt, thanks for helping me. but i've flash boot boot.img file in .zip after i install rom from sdcard. after that, phone stuck in bootloader.
i've unlock bootloader and flash recovery again, and now it says can't mount sdcard. how can i copy viper rom into internal storage? sideload? flash zip? and after all, my phone still not root, can flash viper rom without root?
sorry for my english. thanks again!
Click to expand...
Click to collapse
Did you perform a factory reset from the bootloader at some point? If so you've corrupted your sd card, you should never perform a factory reset from the bootloader. If this is the case you'll need to use TWRP to wipe your sd card, then you should be able to mount it to Windows and use Windows Explorer to format. Once this is done you can for a ROM across again.
Exactly which build of Viper did you try to flash? What's the exact filename? Did you check the md5 before flashing?
Sent from my Evita
timmaaa said:
Please be patient, we all have lives outside XDA.
Did you perform a factory reset from the bootloader at some point? If so you've corrupted your sd card, you should never perform a factory reset from the bootloader. If this is the case you'll need to use TWRP to wipe your sd card, then you should be able to mount it to Windows and use Windows Explorer to format. Once this is done you can for a ROM across again.
Exactly which build of Viper did you try to flash? What's the exact filename? Did you check the md5 before flashing?
Sent from my Evita
Click to expand...
Click to collapse
yes, i did it more than once, now it's fixed, but when i mount it to Windows using TWRP, nothing happen, so i can't format it. and the same things when i tried to sideload. But in fastboot mode, it usual.
and i flashed the newest rom in this thread: http://forum.xda-developers.com/showthread.php?t=1868236 ViperXL 4.2 and i didn't check the MD5
back to my previous question, can i fash a custom rom without root?
I asked for the exact filename of the ROM for a reason, I need that please. Also, exactly which recovery are you using?
Sent from my Evita
Yes, you can flash a custom Rom without root. He already answered that. I strongly recommend reading up on your device before flashing anything else. I'd suggest starting with getting your phone s-off.
nem1yan said:
Yes, you can flash a custom Rom without root. He already answered that. I strongly recommend reading up on your device before flashing anything else. I'd suggest starting with getting your phone s-off.
Click to expand...
Click to collapse
I disagree. I think it's a better idea for him to get his head around the simple operations like flashing ROMs before attempting s-off.
Sent from my Evita
timmaaa said:
I asked for the exact filename of the ROM for a reason, I need that please. Also, exactly which recovery are you using?
Sent from my Evita
Click to expand...
Click to collapse
Full ROM:
Jelly Bean - Android 4.2.2 / Sense 5
ViperXL 4.2.0
Main Link: http://www.androidfilehost.com/?fid=23134718111254927
Mirror 1: http://goo.im/devs/Turge/ViperXL/ViperXL_4.2.0.zip
Mirror 2: http://d-h.st/z4Q
Click to expand...
Click to collapse
and at the first time, i used ClockworkMod Touch 6.0.2.8 Official from here: http://forum.xda-developers.com/showthread.php?t=2148909
after, i used this: twrp-2.7.0.8-evita.img
Thanks!
I know which ROM you're flashing, I need the filename, as it appears in your file browser or Windows Explorer or something. Like this:
Code:
Romname.zip
Sent from my Evita
---------- Post added at 01:19 AM ---------- Previous post was at 01:18 AM ----------
And you should always check the md5 of anything you're about to flash. You should do that now to make sure the file isn't corrupt.
Sent from my Evita
timmaaa said:
I know which ROM you're flashing, I need the filename, as it appears in your file browser or Windows Explorer or something. Like this:
Code:
Romname.zip
Sent from my Evita
---------- Post added at 01:19 AM ---------- Previous post was at 01:18 AM ----------
And you should always check the md5 of anything you're about to flash. You should do that now to make sure the file isn't corrupt.
Sent from my Evita
Click to expand...
Click to collapse
it is ViperXL_4.2.0.zip
i'll do it next time!
No sure, but i think you need to have an older version of twrp to flash the Viper like 2.6.1.0...
veveve said:
it is ViperXL_4.2.0.zip
i'll do it next time!
Click to expand...
Click to collapse
Did you check the md5? Does it match?
Sent from my Evita
---------- Post added at 08:49 AM ---------- Previous post was at 08:49 AM ----------
bzhmobile said:
No sure, but i think you need to have an older version of twrp to flash the Viper like 2.6.1.0...
Click to expand...
Click to collapse
You might be onto something.
Sent from my Evita
timmaaa said:
Did you check the md5? Does it match?
Sent from my Evita
---------- Post added at 08:49 AM ---------- Previous post was at 08:49 AM ----------
You might be onto something.
Sent from my Evita
Click to expand...
Click to collapse
I mean, i didn't do it and i will do it next time
bzhmobile said:
No sure, but i think you need to have an older version of twrp to flash the Viper like 2.6.1.0...
Click to expand...
Click to collapse
thanks, i will try.
Make sure you check the md5 before flashing. A corrupt zip could brick your phone.
Sent from my Evita
timmaaa said:
Make sure you check the md5 before flashing. A corrupt zip could brick your phone.
Sent from my Evita
Click to expand...
Click to collapse
but i still have trouble with mounting internal storage using TWRP on windows, should i try the older TWRP?
What version do you have installed?
Sent from my Evita
timmaaa said:
What version do you have installed?
Sent from my Evita
Click to expand...
Click to collapse
here
and at the first time, i used ClockworkMod Touch 6.0.2.8 Official from here: http://forum.xda-developers.com/show....php?t=2148909
after, i used this: twrp-2.7.0.8-evita.img
Click to expand...
Click to collapse