Related
During the summer I rooted my phone and i have Clockworkmod v2.5.0.7 installed.
I am trying to upgrade to the latest version and it never seems to stick.
Using Rom manager. It says that im flashed to v5.0.2.0 yet when i boot to recovery from rom manager it loads to v2.5.0.7. Does the same thing if i choose to flash a rom though ROM MANAGER. each time v2XXX loads
So i fire up recover and try loading the zip. Bingo it works. The screen turns from green to blue and V5.0.2.0 is now there for me to use. But if i reboot and later return to recovery its back to the old V2xxxx..
Any ideas why this is happening? Is it really necessary to move on to the V5xxxx versions? I was going to try out some new roms and they failed to load yesterday through v2.5.0.7 yet the rom i had been using loaded fine.
Thanks in advance..
When you use Rom Manager to flash a rom or reboot into recovery from Rom Manager, it boots the recovery from a downloaded recovery file. It's known as fake flash or in other words, it's temporary. If you want a permanent recovery, you would need to flash a recovery.img through fastboot.
Meaple said:
When you use Rom Manager to flash a rom or reboot into recovery from Rom Manager, it boots the recovery from a downloaded recovery file. It's known as fake flash or in other words, it's temporary. If you want a permanent recovery, you would need to flash a recovery.img through fastboot.
Click to expand...
Click to collapse
if your Desire is s-off, then ROM Manager flashes recovery normally.
Sent from my HTC Desire using XDA App
rom manager now works only if u have s-off..no fake flash anymore is possible
revolutionary.io will upgrade cwm if you want
I think this thread answers one of my own questions but will ask it anyway to confirm; when I rooted my Desire (via Unrevoked) a few months back, the ROM Manager app that continues to be updated via the market offers the option to upgrade the version of CWM... is it OK to proceed with this?
I've been wary of upgrading from the version installed via the rooting process, just in case, but seeing this thread has made me think there isn't actually an issue with whatever version of recovery you have installed?
TKG26 said:
I was going to try out some new roms and they failed to load yesterday through v2.5.0.7 yet the rom i had been using loaded fine.
Click to expand...
Click to collapse
Out of curiosity - what roms you tried to load? As far as I know 2.5.0.7 was the last cwm supporting both amend and edify scripting and it never failed for me personally.
To upgrade recovery (or hboots) I always use Fastboot Commander and it's very easy to use and never let me down.
erklat said:
Out of curiosity - what roms you tried to load? As far as I know 2.5.0.7 was the last cwm supporting both amend and edify scripting and it never failed for me personally.
Click to expand...
Click to collapse
I agree. Unless you need to maintain an ext 4 partition (as 2.5.0.7 converts it to lower apparently when backing up) I see no reason to change from 2.5.0.7.
I use it even today. Best recovery IMHO.
I've been following xda for a while now, but this is my first post so please take it easy on me, if I posted this in the wrong thread.
I am not new to rooting and costom roms. I have successfully rooted one phone before and I used it for a more than a year, didn't have any problems at all. Yesterday I got myself HTC One X and today I tried to root it and somehow got myself stucked/bricked.
The phone is stuck on HTC Quietly brilliant screen. I can get into bootloader, but thats it. What can I do? I already tried to flash back the original ROM, but couldn't get device to connect to PC. I looked all over the forum and googled it and still can't seem to find the solution. Any help would be highly apprechiated.
*** UNLOCKED ***
ENDEAVOUR PVT SHIP S-ON RL
HBOOT-1. 39. 0000
CPLD-None
MICROP-None
RADIO-5. 1204. 162A. 29
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH : OFF
Which rom did you flash? You have to flash the boot.img from within the .zip file.
Sent from my HTC One X using XDA Premium App
Desaf said:
Which rom did you flash? You have to flash the boot.img from within the .zip file.
Sent from my HTC One X using XDA Premium App
Click to expand...
Click to collapse
Something went wrong when I tried to root it. It probably didn't go through with it. I tried to flash a stock rom back, after I got stuck but it won't go, because I can't connect with PC.
Straxer said:
Something went wrong when I tried to root it. It probably didn't go through with it. I tried to flash a stock rom back, after I got stuck but it won't go, because I can't connect with PC.
Click to expand...
Click to collapse
Which recovery have you installed? If it's twrp you can mount SD from there put a custom ROM on it with superuser (root) flash that ROM from recovery and you have root. It's by far the easiest way to flash a custom ROM to get root instead of getting root on a stock ROM.
And BTW, the hox is not easy to brick of you ask me so don't panic (yet)
Sent from my HTC One X using xda app-developers app
Straxer said:
Something went wrong when I tried to root it. It probably didn't go through with it. I tried to flash a stock rom back, after I got stuck but it won't go, because I can't connect with PC.
Click to expand...
Click to collapse
need to be more specific. did it happend just after you tried rooting? or did you try to install/flash rom/kernel/(recovery etc)
try to root again . use this tool. its the easiest. http://forum.xda-developers.com/showthread.php?t=1604439
i m no expert but from my experience your problem occurs when you flash incampatable kernel..also, we cannot s-off our one x so you have to flash the kernel (named as boot.img, if not , you rename it) manually via fastboot. (download sdk tools) when flashing new rom.
dragonflame8712 said:
need to be more specific. did it happend just after you tried rooting? or did you try to install/flash rom/kernel/(recovery etc)
try to root again . use this tool. its the easiest. http://forum.xda-developers.com/showthread.php?t=1604439
i m no expert but from my experience your problem occurs when you flash incampatable kernel..also, we cannot s-off our one x so you have to flash the kernel (named as boot.img, if not , you rename it) manually via fastboot. (download sdk tools) when flashing new rom.
Click to expand...
Click to collapse
As you said, I used that tool. I installed HTC Drivers, registered at HTCDev, got TokenID, submitted it and unlocked Bootloader. Everything went ok, the only thing that was wrong was with the MTP device driver, which failed to install every time. (I think that was the reason why it disconnected with PC). I then procceded to Perm Root where it got stuck on the phone with red explanation point screen. From there I could still reset phone to a normal state like there was no changes.
Then I tried InsecureBootAndRoot, followed the steps and shortly after it started rooting, the program closed and it was stuck here. I tried to do it again, but I got the message: Waiting for a device.
Can you explain in more detail, how to flash kernel manually, if my computer doesn't recognize device?
dragonflame8712 said:
need to be more specific. did it happend just after you tried rooting? or did you try to install/flash rom/kernel/(recovery etc)
try to root again . use this tool. its the easiest. http://forum.xda-developers.com/showthread.php?t=1604439
i m no expert but from my experience your problem occurs when you flash incampatable kernel..also, we cannot s-off our one x so you have to flash the kernel (named as boot.img, if not , you rename it) manually via fastboot. (download sdk tools) when flashing new rom.
Click to expand...
Click to collapse
Ok, I think I know how to flash kernel. Can you tell me which one to chose or give me a link to it please.
Straxer said:
Ok, I think I know how to flash kernel. Can you tell me which one to chose or give me a link to it please.
Click to expand...
Click to collapse
Have you flashed a rom yet or are you still on stock? Do you prefer sense roms or AOSP/cyanogen?
gffmac said:
Have you flashed a rom yet or are you still on stock? Do you prefer sense roms or AOSP/cyanogen?
Click to expand...
Click to collapse
No, I haven't. I am now practically without a rom (I think). I would prefer custom rom (like cyanogen).
The problem is that everytime I try to do anything for example, flash back factory RUU, I get the message: device not found. Is this because of problem with drivers. Someone please help me out
Straxer said:
The problem is that everytime I try to do anything for example, flash back factory RUU, I get the message: device not found. Is this because of problem with drivers. Someone please help me out
Click to expand...
Click to collapse
If you want cyanogen you need a custom recovery like TWRP. That recovery you can flash through fastboot but like you said there is something wrong with your drivers. Did you install HTC sync on your PC. And did you enable USB debugging in your current ROM?
Sent from my HTC One X using xda app-developers app
J_Dutch said:
If you want cyanogen you need a custom recovery like TWRP. That recovery you can flash through fastboot but like you said there is something wrong with your drivers. Did you install HTC sync on your PC. And did you enable USB debugging in your current ROM?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes, I got CWM recovery. I just discovered that. I installed and uninstalled all the latest htc drivers and htc sync many times. It enabled debugging mode, the last time I was on stock rom (don't know if you can check that now in bootloader?) If my phone is not rooted, than I can't install custom rom right, because I think it isn't. how can I check that?
Straxer said:
Yes, I got CWM recovery. I just discovered that. I installed and uninstalled all the latest htc drivers and htc sync many times. It enabled debugging mode, the last time I was on stock rom (don't know if you can check that now in bootloader?) If my phone is not rooted, than I can't install custom rom right, because I think it isn't. how can I check that?
Click to expand...
Click to collapse
No you don't need root to flash a custom ROM. Flashing a custom ROM will give you root. So you are doing things the wrong way. If you can get into cwm then make sure you have cyanogen.zip and gapps.zip on your phone. Extract(copy) the boot.IMG file from cyanogen. Then from cwm do a nandroid backup, full wipe except SD card, flash cyanogen, flash gapps. Then from cwm boot into boot loader, make sure you place the extracted boot.IMG in your fastboot folder on PC and in command line give commands: fastboot flash boot boot.img then: fastboot erase cache then: fastboot reboot Then you can unplug USB and it will start cyanogen and you have root.
Sent from my HTC One X using xda app-developers app
J_Dutch said:
No you don't need root to flash a custom ROM. Flashing a custom ROM will give you root. So you are doing things the wrong way. If you can get into cwm then make sure you have cyanogen.zip and gapps.zip on your phone. Extract(copy) the boot.IMG file from cyanogen. Then from cwm do a nandroid backup, full wipe except SD card, flash cyanogen, flash gapps. Then from cwm boot into boot loader, make sure you place the extracted boot.IMG in your fastboot folder on PC and in command line give commands: fastboot flash boot boot.img then: fastboot erase cache then: fastboot reboot Then you can unplug USB and it will start cyanogen and you have root.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Okay, so I installed latest CM10 and gapps. How to extract boot.IMG form cyanogen?
I extracted boot.img from Cyanogenmod zip file (that is the same for everybody, right?). I did a Nandroid backup like you said But now all I can do is wipe data/factory reset (CWM Recovery v5.8.4.0). I can't find an option to wipe only selected things.
I was blind, but now I see! I got it running. Everything works great. Thanks to all of you, especially to J_Dutch :victory:
Straxer said:
I was blind, but now I see! I got it running. Everything works great. Thanks to all of you, especially to J_Dutch :victory:
Click to expand...
Click to collapse
Glad you got it up and running! Hope you enjoy the custom ROM, with every other ROM you flash you will need that boot.img to be flashed separately.
Ps. Please hit the thanks button if somebody helps you. It's designed for that.
Sent from my HTC One X using xda app-developers app
J_Dutch said:
Glad you got it up and running! Hope you enjoy the custom ROM, with every other ROM you flash you will need that boot.img to be flashed separately.
Ps. Please hit the thanks button if somebody helps you. It's designed for that.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Just came back to do that. Much appreciated!
Hey guys.
So ive wanted to intall a new rom , did the WeakSauce method and then got S-off.
After doing that downloaded the Viper rom , did a full wipe , and now every time i try to install it the phone start the install and after few secounds just reboot into recovery again.
Iam not able to do any thing and iam also not able to boot the phone it stuck on the HTC logo.
Also when in TWRP i get the msg : E: unable to mount /system.
The phone is M8 Verizon (s-off)
Please help !
chundrik said:
Hey guys.
So ive wanted to intall a new rom , did the WeakSauce method and then got S-off.
After doing that downloaded the Viper rom , did a full wipe , and now every time i try to install it the phone start the install and after few secounds just reboot into recovery again.
Iam not able to do any thing and iam also not able to boot the phone it stuck on the HTC logo.
Also when in TWRP i get the msg : E: unable to mount /system.
The phone is M8 Verizon (s-off)
Please help !
Click to expand...
Click to collapse
Have you rooted weak sauce is just a temporary root
To get the phone to boot hold volume up and power or power volume down
yes but it either go to recovery mode or it just try to boot and it get stuck on the HTC logo.
So what you are sayin is that i have to install root ?
chundrik said:
yes but it either go to recovery mode or it just try to boot and it get stuck on the HTC logo.
So what you are sayin is that i have to install root ?
Click to expand...
Click to collapse
Yeah don't think you have root, did you root or only use weak
i used weak , so does it mean i have to root ?
can i please have a guide or some thing ?
chundrik said:
i used weak , so does it mean i have to root ?
can i please have a guide or some thing ?
Click to expand...
Click to collapse
Yeah you don't have root
Try this http://forum.xda-developers.com/showthread.php?t=2694925
Should be able to get root with it if you are not sure how to use it go on YouTube and search
Why search on YouTube? Everything you need to know is right here. Search here. Ask specific questions about things that confuse you. The information here is always way more accurate than anywhere else.
Sent from my HTC One_M8 using xda app-developers app
the download links in that post isnt working , any idea where can i download it ? (*tried to google it but no luck)
exad said:
Why search on YouTube? Everything you need to know is right here. Search here. Ask specific questions about things that confuse you. The information here is always way more accurate than anywhere else.
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
Sometimes it's easy to watch someone doing stuff then reading
Well is for me lol
Root doesn't matter when you're S-OFF and have a custom recovery installed. Root comes into play when the OS is actually running and from the sound of it, your internal storage got wiped, hence why it can't mount system.
When you are in TWRP, plug your phone in to the computer and it should allow you to do adb commands.
Grab the ROM of your choice, I'd recommend InsertCoin but you can use any ROM, download that to your computer.
In TWRP, do Wipe/Advanced Wipe and check Dalvik, System, Cache, Data (do not check Internal Storage, microSD, or USB-OTG) then swipe to wipe, reboot recovery.
Now open up a command prompt with adb and do adb push romnamehere.zip /sdcard/romnamehere.zip
Then install the ROM as normal.
Reboot and if you get hung at the HTC screen again, you can try the same thing but wipe internal storage as well. Note that will wipe everything on your device but it may fix it. If it does not, you may have a failing eMMC chip, something I saw a few times on the M7, which would require a replacement device. I don't believe we have a RUU out yet which would kind of mean you're SOL. You would have to use the instructions to return to 100% stock in order to get warranty service or if you have insurance you would have to pay your deductible since you modified the device.
Before wiping internal storage post here again if the above instructions fail. There are other things you can try first.
Sent from my HTC One_M8 using xda app-developers app
EtherealRemnant said:
Root doesn't matter when you're S-OFF and have a custom recovery installed. Root comes into play when the OS is actually running and from the sound of it, your internal storage got wiped, hence why it can't mount system.
When you are in TWRP, plug your phone in to the computer and it should allow you to do adb commands.
Grab the ROM of your choice, I'd recommend InsertCoin but you can use any ROM, download that to your computer.
In TWRP, do Wipe/Advanced Wipe and check Dalvik, System, Cache, Data (do not check Internal Storage, microSD, or USB-OTG) then swipe to wipe, reboot recovery.
Now open up a command prompt with adb and do adb push romnamehere.zip /sdcard/romnamehere.zip
Then install the ROM as normal.
Reboot and if you get hung at the HTC screen again, you can try the same thing but wipe internal storage as well. Note that will wipe everything on your device but it may fix it. If it does not, you may have a failing eMMC chip, something I saw a few times on the M7, which would require a replacement device. I don't believe we have a RUU out yet which would kind of mean you're SOL. You would have to use the instructions to return to 100% stock in order to get warranty service or if you have insurance you would have to pay your deductible since you modified the device.
Click to expand...
Click to collapse
yes but i dont understand one thing , how does adb help me here ? (p.s when i did try to use adb it been saying "waiting for device"
either way i have the 2 rom`s on my external SD card , iam able to flash them but bouth stuck on some point of the install and then just reboot into recovery again.
also tried to
chundrik said:
yes but i dont understand one thing , how does adb help me here ? (p.s when i did try to use adb it been saying "waiting for device"
either way i have the 2 rom`s on my external SD card , iam able to flash them but bouth stuck on some point of the install and then just reboot into recovery again.
also tried to
Click to expand...
Click to collapse
Check the MD5 of the roms you are downloading. Also, which rom are you trying to flash and which phone do you have?
What recovery are you using?
Assuming the MD5 of the roms you are flashing do matchup and this isn't just a corrupted data issue. I would redownload whatever recovery you're using,
Check the MD5 of the recovery image
Flash said recovery:
fastboot flash recovery recoveryfilename.img
then use fastboot to erase cache
fastboot erase cache
Then select recovery from the bootloader screen
Then factory reset
Then wipe system in advanced wipe
Then try flashing your rom again.
Iam have TWRP v2.7.0.2
The phone is Verizon m8.
Roms : Revolution HD and Viper
and what does it mean md5 matchup ?
when trying to flash revolution HD it gets to the point where it saying :
>>>creating toolbox symlinks
symlink: some symlinks faild
chundrik said:
Iam have TWRP v2.7.0.2
The phone is Verizon m8.
Roms : Revolution HD and Viper
and what does it mean md5 matchup ?
Click to expand...
Click to collapse
When you download a ROM, typically the md5 checksum is posted on the download page. Using an md5 checking program, you can verify the integrity of the files you download by generating the md5 checksum of the file you downloaded and comparing it to the one posted on the site where you downloaded your file from.
Use google if you do not have an md5 checking program. Flashing something like a firmware or anything that alters any emmc partitions that has data corruption could brick your phone. Hence and MD5 checking tool is invaluable when rooting/modding your phone.
---------- Post added at 09:09 AM ---------- Previous post was at 09:02 AM ----------
Hmmm on Verizon??? Hmmm Verizon does have it's own separate XDA forum.. maybe you should try roms from there?? not sure if they're different but if XDA differentiated, then probably..
http://forum.xda-developers.com/verizon-htc-one-m8
Also make sure you're using this recovery:
http://teamw.in/project/twrp2/226
exad said:
When you download a ROM, typically the md5 checksum is posted on the download page. Using an md5 checking program, you can verify the integrity of the files you download by generating the md5 checksum of the file you downloaded and comparing it to the one posted on the site where you downloaded your file from.
Use google if you do not have an md5 checking program. Flashing something like a firmware or anything that alters any emmc partitions that has data corruption could brick your phone. Hence and MD5 checking tool is invaluable when rooting/modding your phone.
---------- Post added at 09:09 AM ---------- Previous post was at 09:02 AM ----------
Hmmm on Verizon??? Hmmm Verizon does have it's own separate XDA forum.. maybe you should try roms from there?? not sure if they're different but if XDA differentiated, then probably..
http://forum.xda-developers.com/verizon-htc-one-m8
Also make sure you're using this recovery:
http://teamw.in/project/twrp2/226
Click to expand...
Click to collapse
well the viper rom is from there.
and it fails with this part :
Installing busybox
set_perm: some changed failed.
Ok try the steps I posted above.
Sent from my HTC One_M8 using xda app-developers app
exad said:
Ok try the steps I posted above.
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
well i`ve tryed but i dont seem to understand where to use them on , i open terminal type the command you provide but it say that it dont know the command , i have adb installed ofc.
(iam using macbook pro).
I see now why you're having problems. You don't understand even the most basic things regarding rooting :/ sorry I'm not into hand holding. You have a lot of reading to do or maybe someone more patience then I will be nice enough to explain everything to you
Sent from my HTC One_M8 using xda app-developers app
Q&A for [ROM] PureKat | Android 4.4 KitKat | More Than A Rom
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Will there be an Android 5.0 PureKat?
With android L/5.0 creeping closer, will there be a PureKat based on it? It seems to have a lot of goodies in it for performance and battery life.
I've been using cm-7.2.0-vision for some time and decided to try this my first KK rom. My sd card slot is corrupted so I am using Flash without SDcard procedure. After using CWM 6.0.4.5 I was able to flash this rom. It boots successfully, but after "Upgrading Android" screen, it displays Cyanogen setup wizard screen (the one with lang choice) and restarts suddenly.
I have started with full wipe and no SD card inserted. After the first restart it will not display Cyanogen setup at all, just restarts before that. Cleaning Dalvik's cache will make setup wizard appear again just to reboot a second later.
Any ideas how to debug it ?
EDIT: Solved. Flashed coolOS ICS 1.5.1 with older CWM, that went fine. It allowed me to format the SD card from Android level and from that time I'm able to boot PureKat without bootloop. Also, magically, my SD card is recognized again and working fine for now.
noccy80 said:
With android L/5.0 creeping closer, will there be a PureKat based on it? It seems to have a lot of goodies in it for performance and battery life.
Click to expand...
Click to collapse
You can use any android l theme from play store i have tested theme chooser in purekat it is working fine i'm using Herathon theme search it on google search that is very cool v8.1 is working on our device, use it and have a small experiance of android l .
Sent from my Desire Z using XDA Free mobile app
Installation aborted
Hi .. I can not install it this rom and rom superior to Android 4.0, I have the last recovery ClockworkMod touch, can you show me how to fix this? All the latest rom I install I write installation aborted ..
zakaru said:
Hi .. I can not install it this rom and rom superior to Android 4.0, I have the last recovery ClockworkMod touch, can you show me how to fix this? All the latest rom I install I write installation aborted ..
Click to expand...
Click to collapse
Hi,
You will need to update your recovery
http://forum.xda-developers.com/showthread.php?t=2734590
demkantor said:
Hi,
You will need to update your recovery
http://forum.xda-developers.com/showthread.php?t=2734590
Click to expand...
Click to collapse
I thought I had the last but I find the ClockworkMod v 5.8.1.0 seen that I have to install another what is between these I recommend?
4EXT Touch version 1.0.0.6_RC1
ClockworkMod Recovery 6.0.4.5 version
TWRP recovery version 2.6.3.0
Any should work fine but personally I'm partial to 4ext myself
demkantor said:
Any should work fine but personally I'm partial to 4ext myself
Click to expand...
Click to collapse
Fantastic! I did not think it was a problem so simple to solve many thanks! The phone is alive again :fingers-crossed:
Can anyone help me with this type of problem used many type of boost mods but still RAM consumption is on the peek !!!
Sent from my Desire Z using XDA Free mobile app
Edit: Problems solves theme was consuming RAM !
Phone hangs during boot
Hi,
I tried to get PureKat working on my phone, but I can't get past the boot animation, it simply keeps spinning. I unlocked my bootloader with the htcdev method a few years ago and I have CWM recovery 6.0.4.5 installed. Flashing the image from the SD card succeeds without errors and I also explicitly flashed the boot.img using fastboot (fastboot flash boot boot.img). I also wiped the phone but that didn't help either. Any thoughts?
//edit: never mind, it works! It seems I just didn't wait long enough for it to boot
Scaladev said:
Hi,
I tried to get PureKat working on my phone, but I can't get past the boot animation, it simply keeps spinning. I unlocked my bootloader with the htcdev method a few years ago and I have CWM recovery 6.0.4.5 installed. Flashing the image from the SD card succeeds without errors and I also explicitly flashed the boot.img using fastboot (fastboot flash boot boot.img). I also wiped the phone but that didn't help either. Any thoughts?
//edit: never mind, it works! It seems I just didn't wait long enough for it to boot
Click to expand...
Click to collapse
Are you able to flash any other rom through this recovery.???
I mean do face problems flashing other roms??
If not, you can try with latest 4ext recovery.
Thanks...
What's happend with repo for the source?
I cannot do repo sync for this branch cm-11.0 without problems. Is this manifest.xml ok, or some projects are removed from this manifest?
First time rooter HTC G2 needs help
I am sorry if this is in the wrong discussion but it seems to the most resent pos.t I just tried my first root using the guide here (http://forum.xda-developers.com/showthread.php?t=1178912). Things went great till I hit step I - 4) Downgrading . The files are either no longer online or will not open. I did fine the file PC101MG here somewhere but I don't know if its correct and I can't find another online. My HTC G2 is in the black screen with silver HTC and command is
C:\android-sdk\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\android-sdk\platform-tools>fastboot devices
HT0A1R208990 fastboot
C:\android-sdk\platform-tools>fastboot oem rebootRUU
... INFOerase sector 196609 ~ 197120 (512)
OKAY
C:\android-sdk\platform-tools>fastboot flash zip StockRom.zip
sending 'zip' (16141 KB)... OKAY
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
C:\android-sdk\platform-tools>fastboot flash zip StockRom.zip
error: cannot load 'StockRom.zip'
C:\android-sdk\platform-tools>fastboot flash zip StockRom.zip
sending 'zip' (16141 KB)... OKAY
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
C:\android-sdk\platform-tools>fastboot flash zip StockRom.zip
sending 'zip' (16141 KB)... OKAY
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
C:\android-sdk\platform-tools>
The second attempt was with the .zip extension added to the file name. Could it be the wrong zip file? I can't believe it went this smooth just to fail in the last step. Also wondering if I should unplug the phone or not? I don't know how to get out of the black and silver screen. Please someone help
A Tester
Hi,
i tested the latest build cm-02-20150630. So the Rom works fine but very slow and very often you cant do nothing because the system very busy.
yours faithfully
michel
After I installed this ROM and gapps, everything works all apps but the play store is there. Any ideas?
Sent from my One M8 using XDA Free mobile app
xavicivic said:
After I installed this ROM and gapps, everything works all apps but the play store is there. Any ideas?
Sent from my One M8 using XDA Free mobile app
Click to expand...
Click to collapse
Try to flash superwipeG2+ext4 script - http://d-h.st/FqY , then flash ROM, and then flash these GAPPS - https://yadi.sk/d/rkymH9a6iNxSe . It's fully working for me, so maybe this helps.
I get that error msg after superwipe
Sent from my One M8 using XDA Free mobile app
If it helps, it doesn't matter what ROM I flash, the play store never works or shows up regardless of flashing the appropriate gapps version. GB kk jb...it doesn't work
Sent from my One M8 using XDA Free mobile app
i flashed new firmware to my htc one m8
I got into recovery and changed the name firmware file.
but now in the recovery it doesn't recognize my internal storage, kind of. it says 0 mb.
And when I try via adb to push a file to it it fails. (adb push filename.zip /sdcard/)
so it seems like i only have the external card now working.
what can I do?
I'm currently in the stage where i have the firmware file in the right name and it keeps asking me to update, if i remove the external card, i can get into recovery change the name, and then i see it won't read the internal storage like i wrote up here.
but after I change the name i can get into fastboot mode.
I currently have recovery mode - twrp 2.8.0.3
p.s I think my internal storage does work, cause i can go into recovery mode(twrp), my external_sd was formmated
before i used to update the firmware, so it has nothing except for that file
You're not flashing the firmware through recovery, are you?
No, i flashed, with the guide here, via an external card, changing the name of the firnware so the hboot would recognize it.. and update it
josh.walker.9242 said:
You're not flashing the firmware through recovery, are you?
Click to expand...
Click to collapse
I was thinking that maybe my twrp version 2.8.0.3 is too old for this bootloader veraion maybe, and i need to update to twrp to 2.8.6 and then try to transfer the rom file and install it.
What do u think?
Do u have any suggestions?
dav_sap said:
I was thinking that maybe my twrp version 2.8.0.3 is too old for this bootloader veraion maybe, and i need to update to twrp to 2.8.6 and then try to transfer the rom file and install it.
What do u think?
Do u have any suggestions?
Click to expand...
Click to collapse
I have TWRP 2.8.0.6. You can download TWRP manager from Play Store, it has a list of TWRP versions you can install. The app installs them too. Everytime I used the app to install it, it says it failed but it actually works, just install, then say ok to the failed install pop up and reboot into recovery and it'll be there.
Edit: As soon as the firmware has flashed successfully, boot up and delete the firmware file off of your external SD card so it doesn't keep asking you to update.
josh.walker.9242 said:
I have TWRP 2.8.0.6. You can download TWRP manager from Play Store, it has a list of TWRP versions you can install. The app installs them too. Everytime I used the app to install it, it says it failed but it actually works, just install, then say ok to the failed install pop up and reboot into recovery and it'll be there.
Click to expand...
Click to collapse
I have no OS now.
I need to download it, and flash it via fastboot. I'm wondering if that's the problem that the internal storage is giving me these problems or it has nothing to do with it.
Does a different firmware require different twrp versions?
Sent from my HTC Desire HD using XDA Free mobile app
dav_sap said:
I have no OS now.
I need to download it, and flash it via fastboot. I'm wondering if that's the problem that the internal storage is giving me these problems or it has nothing to do with it.
Does a different firmware require different twrp versions?
Sent from my HTC Desire HD using XDA Free mobile app
Click to expand...
Click to collapse
Not as far as I know. Your best bet man is probably to download an RUU and just flash that through fastboot or the external sd card method. Then after that, flash the TWRP then put a ROM zip on your phone and flash that way.
josh.walker.9242 said:
Not as far as I know. Your best bet man is probably to download an RUU and just flash that through fastboot or the external sd card method. Then after that, flash the TWRP then put a ROM zip on your phone and flash that way.
Click to expand...
Click to collapse
What RUU should i use? Isn't that just firmware like the one i flashed now?
dav_sap said:
What RUU should i use? Isn't that just firmware like the one i flashed now?
Click to expand...
Click to collapse
No, an RUU is a complete system install. Completely stock with the exception of some RUUs contain root. But it will wipe everything on your phone, all your personal data and what not.