I just got a refurb'd htc one m8 off insurance, I unlocked with sunshine and rooted with kingroot and have twrp 3.0.0-1 .
I tried flashing CleanRom 4.0 after factory reset and I got the error the zip was corrupt
then I tried Android Revolution HD did a factory reset , after a few moments it reboots back into recovery with no install
Then I tried Adrenaline 2.4 vzw port final and I got the error the zip was corrupt
I'm not sure if it's worth noting I have no access to a windows PC I can only liveboot different linux distros such as Caine, Backbox, Kali, and Parted Magic
is it possible that because I'm live booting when it downloads the zip it re-writes over because I'm running off of the RAM and the isn't enough??
in desperate need of help I've been up 2 days reading, learning and trying everything
Related
This thread might be a warning not to install CWM through ROM Manager until it's fixed. Aplogies to koush if it isn't broke and it was just my incompetence.
So... I got my TF101 on Saturday and after checking everything worked on it I rooted it with ViperMOD PrimeTime v4.5, installed Team Rogue recovery using the recovery installer apk and flashed Revolution HD ROM.
(I had to use ViperMOD for the rooting becasue I had already done the ASUS ICS update via Wifi)
Anyway, a few hours ago I saw on Twitter that ClockworkMOD recovery for the TF101 was now available. I thought great and installed ROM Manager from the market, clicked on flash CWM recovery and selected my device. It flashed CWM and rebooted into CWM.
Only problem is my device now boots up to CWM recovery every time I turn it on. Also I was expecting CWM to be better than the Team Rogue one but it turns out that the Team Rogue one lets you select a zip from your MicroSD card where CWM does not.
If I want to boot into the OS on my EeePad I have to hold the Vol Down on startup, wait 5 seconds at the recovery prompt and then I get the screen which allows you to wipe data or cold boot into Linux/Android. So I choose boot into linux and the OS starts loading.
This is a bit of a pain in the arse, and not what the device was designed to do so I'd like to get it back to nornal, preferably with Team Rogue recovery due to the better options it has.
I've tried running the Team Rogue recovery installer apk and also reflashing Revolution HD and it always boots up with ClockworkMOD!
My guess is that ROM Manager has placed CWM in an area of memory that it isn't supposed to go in, ahead of where the EeePad recovery should be.
Is there a hardcore recovery/kernel flashing utility I could use?
I've done a lot of flashing with phones but this is my first tablet so I'm a bit of a noob with the TF101.
I've been thinking: would flashing a stock ASUS ROM, complete with ASUS kernel and recovery, fix this?
I can't use nvflash because it's one of the SBKv2 models.
Is there a complete package I could flash with ADB/Fastboot?
Try wiping everything and install the rom again?...
Or.. download an older rom version from asus website and follow their instructions to load perhaps ?
I found out even though I've got a B70KAS serial device I'm lucky to be able to NVFlash. I've flashed a complete, stock Honeycomb image on there and it's sorted out my recovery sector.
It had me scratching my head as I thought I would be able to NVFlash, but I tried and it worked.
where did u find file?
Had same problem ,went to Asus site wouldn'tlet me downloads us version
Here is the page for the NVFlash of the Worldwide/UK version of the file mate:
http://www.wupload.co.uk/file/2628149097/Revolver_TF_3.11_nvflash_gnufabio.zip
I ended up finding out which file I needed and just did a google search for 'Revolver_TF_3.11_nvflash_gnufabio.zip'.
Then when I flashed that I had a brand new installation of Revolver Honeycomb which was rooted and an older version of ClockworkMod installed.
Make sure that you have the NVflash/APK drivers on your PC and you should be OK. I used Windows 7 64 bit and the flash went fine.
I then rebooted Revolver and used CWM to wipe and install the latest Revolution HD zip file from my microSD card. I'm back to Ice Cream Sandwich now and it's running OK.
Now first off I'd like to start saying that I've seen a few threads from a search with this issue but none of them matched my case perfectly or solved the issue.
I have an AT&T HTC One X and was running CleanRom DE 1.0
I saw there was an upgrade out and tried installing the upgrade. I tried running the RUU but it gave me an error 155 (Unknown error). Thinking that it did not matter to much, I tried to install the new version anyway. This got me stuck in a boot loop of the boot animation for about 1 second, then rebooting. I have CWM recovery installed and can adb/fastboot but I cannot do much else. I pushed a 1.7 rom to my sdcard but CWM gives me the message, "Error: Cannot mount /sdcard/"
My phone is unlocked but locking it did not change anything, still could not load anything or use the RUU.
I've seen other threads saying to Lock the phone, then flash the ruu and I guess I'm a little confused on that. By saying "flash the ruu" do you mean just running the .exe file or doing something with fastboot flash? I'm stuck without a phone right now and any help would be appreciated.
In my situation, I deleted the user memory and dalvik cache. I then did some research on my phone's exact stock ROM. I flashed the ROM and basically started off fresh. It may not be the most convenient. But, it may be what is needed. It sounds as if your phone is 'soft-bricked' so this should work as the last ditch effort.
Best of luck!
Sent from my MB865 using xda premium
Thankyou for your reply, I'm new to android and I'm wondering what exact steps went into flashing the stock rom onto your phone? Let's assume I already have that stock rom. Are you just using fastboot flash boot rom.zip ? or using CWM?
EDIT: My phone is now booting! I kept launching the RUU and after about four times it decided to work. Back to the stock AT&T rom, and right now I'm great with that.
I hate to post this but after 3 days of trying to get this damned phone serviceable I am seeking higher powers.
I have viewed just about every thread I can, and everytime i think I'm getting close only to be disappointed.
I was attempting to root a Rogers HTC One X for a friend. Ive rooted 3 other devices prior to this one without issue and constantly custom rom my own device (HTC Raider).
As of now, I CAN: Boot to Hboot (1.11.000), Flash Custom Recovery (Have tried TWRP and CWM, can enter successfully cant do much else), flash things via fastboot.
I CANNOT boot to OS. Its apparently gone. so as such, i have no access to the SD-ext. I CAN mount USB in TWRP but while it shows up in windows as a storage device, I CANT see it on the phone, so i cant flash it. I CANNOT mount in CWM.
I have attempted to RUU via fastboot. I have gotten errors for signature, size and model. Even the stock, non-root one (1.94) stated that the size is incorrect. Im also seeing alot of Errors regarding android-info.txt.
I really desperately need to get this running. Which ever rom. i dont care. If i can get stock, fine, if not Custom rom/kernel.
My biggest issue is not having access to the sd-ext and this phone, for some stupid reason, does not have a microSD slot, which would have made this whole issue alot easier.
I dont know if im missing a file or a step. Im really not sure where to go next.
If you have files that will work and can tell me how to do it, I will forever be in your debt.
It seems to me that i SHOULD be able to run fastboot update xxx.zip and just have it fix it but thats when im getting the android-info.txt errors.
If i could manually flash the 3 files through fastboot (system and boot more than recovery), i would think it would work but nooooooo.
Is there any way any of you know how to get me to atleast being able to see my sd-ext on both windows and TWRP so i can flash it that way? ANYTHING?
So, Got it up and running with Team Nocturnals Rom.
What I had to do was wipe SD and caches in TWRP. Flashed CWM from fastboot. Wiped SD and cache AGAIN. Flashed back to TWRP. Wiped SD and Cache. Rebooted to fastboot. Flashed the boot.IMG. Rebooted to recovery. Mounted USB. Windows detected it. Formatted to fat32. Copied the .zip to SD and installed. Problem solved.
Stock 2.20 Rom that's around didn't work, deodexed rooted stock didnts, nor did Android Revolution HD.
I still thank all of you, because even though I got this working myself, it was bits and pieces of every other thread that got me to that point. Thank you all.
Sent from my HTC Velocity 4G X710s using xda app-developers app
Kesler84 said:
So, Got it up and running with Team Nocturnals Rom.
What I had to do was wipe SD and caches in TWRP. Flashed CWM from fastboot. Wiped SD and cache AGAIN. Flashed back to TWRP. Wiped SD and Cache. Rebooted to fastboot. Flashed the boot.IMG. Rebooted to recovery. Mounted USB. Windows detected it. Formatted to fat32. Copied the .zip to SD and installed. Problem solved.
Stock 2.20 Rom that's around didn't work, deodexed rooted stock didnts, nor did Android Revolution HD.
I still thank all of you, because even though I got this working myself, it was bits and pieces of every other thread that got me to that point. Thank you all.
Sent from my HTC Velocity 4G X710s using xda app-developers app
Click to expand...
Click to collapse
Ummmm android revolution is for the international one x.... Maybe that's how u f'd it up in the first place? Idk just be careful the threads are kinda similar ...
No, I didn't even touch Revolution until it was already not working. I was originally just rooting the stock. It wasn't until it softbricked that I attempted any customs.
Sent from my HTC Velocity 4G X710s using xda app-developers app
Hey all, been a member here for years but dont post offten. Normally able to get the info i need from other posts but this time i am stuck Just wondering if anyone has had the same issue flashing a One S C2 with the S3 CPU that im having now. It was stuck with 4.0.3 with hboot 2.09.001, raido 16.05.2.24_M and CID OPTUS001...
Last night i dev unlocked it via the HTC site and flashed TWRP 2.4.4.0 recovery. Tried to put on luxandroidROM v4 but it failed part way through ROM install. The progess bar just got to a point and stopped?? I noticed i had a hboot that was too old for the JB ROM so tried BackToBasics v3 (ICS) ROM but that did the same thing...
Thinking it was maybe just a issue with the ROMs, i tried TrickDroid 6 and CM10 Unofficial build but that was doing the exact same thing... Tried redownloading all the ROMs and looking into SupoerCID but as other with the S3 CPU have reported, it all appears to have worked but does not change the CID Oddly enough when i was in ADB Shell while the phone was sitting on the TWRP recovery mode the SU command was not working. Relevent?
I'm now thinking the issue is the phone is not getting permissions to write the ROMs but have no idea how to correct this. I made sure TWRP has all sections mounted (not sure if this is needed as i normally use CWM) but didn't help.
TWRP keeps saying device isnt rooted when i go to reboot it but fails to root when i tell it to on exit. I have manually flashed SuperSU through TWRP and tried fixing permissions. Tried full factory wipe, Bulletproof-S3-1.3 Kernal and SuperSU again. Still nothing.
Not able to find a RUU for the OPTUS001 CID. Tried extracted version of RUU_VILLEC2_U_ICS_40_hTC_Asia_WWE_1.11.707.112_Radio_16.12.20.02U_16.05.20.16_M2 with CID changed in texts files but it still saied with carrier ID issue
This would be the first time i think i have bricked a phone Does anyone have any suggestions? At this point i would be happy for a nandroid backup to go back to sock and just like with 4.0.3
$40 reward to whoever provides me the info i need to fix this
On the s4 versions of TWRP newer than 2.4.0.0 have issues. I'm not sure if they affect the c2 version but I shouldn't hurt to try an older version.
Sent from my HTC One S using xda app-developers app
TWRP 2.4.4.0 has known bugs. Downgrade to 2.3.3.0 or 2.3.3.7.
And remember to open (BUT NOT EXTRACT) the .zip and to copy and paste the boot.img into your fastboot working environment and manually flash it with this command:
fastboot flash boot boot.img
Then try to flash the ROM that you got the boot.img from. This should work.
Sent from my One S using xda premium
Managed to get this working, figured i would post in case anyone else runs in this issue.
Tried multiple versions of TWRP and no matter what one i tried the roms were unable to write to the stoage. Had to format the phone storage using boot cd - I used GParted through a virtual to do so.
Once that was done TWRP 2.4.4.0 worked fine to flash rom. Still stuck with 4.0.3 with hboot 2.09.001 due to the optus CID but phone is atleast alive. Thanks all for the input
Alright guys, I hate to do this. I've been messing around with this stuff for years now, but I'm still an amateur compared to most everybody around here. I've messed up a lot of phones and have been able to pull them from the brink before through a combination of google-fu and dumb luck. This time I haven't been able to do it yet after about 10 hours of work. Here's the rundown:
Had a stock HTC One S (T-mobile and updated OTA to jellybean) until yesterday.
Unlocked the bootloader the official HTC way.
Got root access.
Flashed TWRP 2.5(hopefully the right version)
Flashed a Rom
Bootloop
Mess with stuff, wipe some things, reflash, but still bootloop. No recovery.
Here's where I am now:
I can get into the bootloader and recovery and I have fastboot access.
I can push files in adb and do whatever with fastboot.
Now here is where I am stuck. Every time I try to wipe, flash or anything I get the message E:Unable to mount /fat
I would love some help from anybody on this. I have searched high and low for the same problem but came back empty handed except for feeling that it has something to do with partitioning.
srk10 said:
Alright guys, I hate to do this. I've been messing around with this stuff for years now, but I'm still an amateur compared to most everybody around here. I've messed up a lot of phones and have been able to pull them from the brink before through a combination of google-fu and dumb luck. This time I haven't been able to do it yet after about 10 hours of work. Here's the rundown:
Had a stock HTC One S (T-mobile and updated OTA to jellybean) until yesterday.
Unlocked the bootloader the official HTC way.
Got root access.
Flashed TWRP 2.5(hopefully the right version)
Flashed a Rom
Bootloop
Mess with stuff, wipe some things, reflash, but still bootloop. No recovery.
Here's where I am now:
I can get into the bootloader and recovery and I have fastboot access.
I can push files in adb and do whatever with fastboot.
Now here is where I am stuck. Every time I try to wipe, flash or anything I get the message E:Unable to mount /fat
I would love some help from anybody on this. I have searched high and low for the same problem but came back empty handed except for feeling that it has something to do with partitioning.
Click to expand...
Click to collapse
not sure but it can be possible that some partitions are damaged.
run the latest ruu to restore all the partitions.
twrp 2.5.0.0 have some problems with custom roms,
try twrp 2.3.3.0, it seems that this version has mostly no problems with flashing roms.
do not forget to flash the boot.img after flashing the rom or you will get a bootloop.
before flashing a rom wipe 3x system 3x data 3x cache to be sure that your phone is clean of old system stuff.
here is the link for twrp 2.3.3.0
https://www.dropbox.com/s/pvspwkekl42zkqa/openrecovery-twrp-2.3.3.0-ville.img
Thanks so much for the reply. I downgrade to twrp 2.3 and managed to use the windows utility to reformat my sd card. Wasn't sure that wasn't going to shoot me in the foot, but it worked and I am back in business with a phone that boots.