HTC One X+: cannot flash ClockWorkMod (touch) Recovery - Upgrading, Modifying and Unlocking

Maybe this is an obvious problem, but I couldn't find a solution neither searching Google nor XDA forums... hence this post here.
I'm trying to flash Android Revolution HD 6.2 Jelly Bean Custom Rom on HTC One X+ 1.17.401.1 using tutorial: how-to-install-android-revolution-hd-6-2-jelly-bean-custom-rom-on-htc-one-x-1-17-401-1 on theandroidrom site.
The prerequisites are:
1. Unlock my device using HTCDev account - which I did (the first line on the boot screen: *** UNLOCKED ***).
2. Install ClockWorkMod Recovery from a downloaded IMG file using fastboot - which doesn't seem to work on my device.
Code:
fastboot flash recovery recovery.img
says everything went OK. But when I reboot my device into recovery mode it just reboots or powers off. When I switch it on again, it just boots into Android (Sense).
I tried both: touch and regular IMG files for HTC One X (GSM) (there is no IMG file dedicated for HTC One X+ as I understand) from clockworkmod site:
1. recovery-clockwork-5.8.4.0-endeavoru.img
2. recovery-clockwork-touch-5.8.4.0-endeavoru.img
In both cases fastboot says everything went ok, but I cannot boot into recovery. Do I make some stupid mistake? (I'm a noob...)
Maybe it's also worth mentioning, that I rooted my device about a week ago using some tutorial on the web - I don't recall the adress anymore. It was on the factory 1.14.401.1 software version then. Root checker said, that the phone has root access. A few days later there was an OTA update to 1.17.401.1 software version, which I installed. Root checker says "no root access" now.
Did I mess something up?
Otherwise the phone works OK. My goal is just to install the Android Revolution ROM, hoping mainly for better battery life (is it reasonable? I already use JuiceDefender on balanced setting...)
Thanks in advance for any help.

Ok, this is weird...
Today I tried to flash the stock revovery for HTC One X+.
Fastboot said all went good, just like before:
Code:
C:\Android>fastboot flash recovery recovery_v.0.3.img
sending 'recovery' (6736 KB)...
OKAY [ 0.989s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.378s]
finished. total time: 1.379s
And now, when I boot into recovery mode, the first line says: "ClockworkMod Recovery v5.8.4.0"
This is the "touch" version as I presume, since menus can be navigated using touches (and volume/power buttons as well).
Someone can explain this to me, please?
Does it mean I can proceed with installing Android Revolution HD 6.2 now? (after proper backup of course)

Related

[Q] Unable to root..

First off, yes I know there are a bagillion threads on not being able to root, and I have spent hours looking through them and my issue isn't resolved, so hear me out.
I just got a Droid Incredible (has Froyo and an AMOLED screen) after my Droid 1 cracked its screen (easily rooted, btw), and tried rooting this with unrevoked 3.32 (newest from his site). I followed this explicit guide verbatim (here).
Unrevoked fails to root, install recovery, or turn off security, giving me the ERROR "Backup CID is Missing" that is mentioned in the guide, so I follow the linked instructions on how to manually flash a recovery image to the device (here)
After booting into hboot with the PC36IMG.zip file on my SD card, hboot scans and says no image or wrong image found for all four checks.
SUMMARY: I cannot flash a custom recovery, so cannot flash a ROM, so no root, and security is still enabled.
I tried using ADB to flash it manually following this, but I get the following error in cmd prompt
fastboot flash recovery recovery.img
sending 'recovery' (4200 KB)... OKAY [ 0.606s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.183s
Some notes that people said to try:
- I have tried three SD cards that all work in my Droid 1
- I reformatted all of them to FAT32 to be sure
- I have tried two windows 7 computers with ADB and unrevoked
- I do not have HTC sync, but I tried installing it and uninstalling like the guide suggests
- I have removed all drivers and reinstalled the unrevoked once again
- I uninstalled Dropbox
- Debugging is enabled, as is everything else in the first guide
- I tried many PC36IMG.zip files (clockwork, RA, stock, different versions) (named them .zip, extracted .img, PC31, etc)
Help would be much appreciated because I am too used to root on my Droid 1!
You mention PC36IMG.zip more than once in your posting, so I assume it isn't a typo.
OTOH, no such file has anything to do with the Incredible. That's a filename for the EVO.
On the Incredible we have files called (or renamed to) PB31IMG.zip,
True, I was following an Incredible guide that sent me there. My bad, not used to dealing with this from my old phone. Thanks for pointing that out.
Well I tried the correct PB31IMG.zip files and the same thing happens in hboot. It says loading...all the zip files... checking... then goes away. Like this one for instance, I took the clockwork PB31IMG.zip. I never get prompted to install the zip.
If I go to recovery, I see a phone with a red triangle on it and the phone is frozen.
I'm in the same boat with my incredible replaement i just got, idk wtf is up with it. i wish i had a old unrevoke version before 3.2 cause i only flashed my last replacement a month ago without a hitch. can anyone pleasssssee upload the version before the one thats currently out for unrevoked so i can try it? It might just cure both of our issues.
do you have the correct modified hboot driver from unrevoked installed? you need to boot your phone into hboot and connect the usb cable let it install driver then go into device manager and maually change the driver to the one they provide... I have rooted 5 SLCD fresh out of box incredibles in the past 2 weeks with unrevoked with 0 issues...
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
two_cents said:
do you have the correct modified hboot driver from unrevoked installed? you need to boot your phone into hboot and connect the usb cable let it install driver then go into device manager and maually change the driver to the one they provide... I have rooted 5 SLCD fresh out of box incredibles in the past 2 weeks with unrevoked with 0 issues...
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
My droid shows up fine, the entire process runs, my phone reboots into Hboot starts the rooting process it gets to the final step of flashing clockwork recovery and bam i get the error unable to validate :: Cid is missing, along those lines like was mentioned above.
I think the issue is on Unrevokeds side. i flashed my replacement before this not more then a month ago but deleted that version of unrevoked. if you have the older jan 8th version id love if you could upload it or upload your current version if its different please.

[Q] Desire Bricked?

Hey Guys,
Right I've been up all night trying to fix this but now I'm at the stage where I need your wisdom!
Problem:
Got a rooted, s-off'd HTC desire (originally on 3 UK running a 3 branded rom, rooted via goldcard method)
It was running Redux and the hboot I was using was CM7. I decided to change back to Oxygen, and proceeded to flash the Oxygen Hboot. I also flashed the latest version of Clockwork Mod Recovery. All was done through terminal in ubuntu using fastboot. I also erased cache, system and boot, before rebooting into recovery and flashing Oxygen. Seemed to install fine so I rebooted into Oxygen and it loaded up. During the setup process my phone informed me that it couldn't find a SIM card. Rebooted into recovery and wiped everything (including dalvik) and still the same problem persisted.
It was at this time I found out that I couldn't mount my SD card either (either in Oxygen or in recovery).
Followed the usb-brick-rickrolled-b0rked-fixed method to resolve the SD card problem.
I used the OP's zip file attached, missed out step 1 and carried on from step 2 (used my Blackberry to get the update file on the SD card).
Anyway it all seemed fixed and Oxygen was booting up fine, sim card was being read, but I found that most of the time my laptop would not discover my phone when attached in storage mode.
Then I decided to start from scratch and restore my desire to a stock htc rom. After preparing my goldcard and getting the RUU I ran the update. The ROM I installed was: RUU_Bravo_H3G_UK_1.22.771.1_Radio_32.36.00.28U_4.0 6.00.02_2_release_127568_signed.exe
(I tried installing a stock froyo RUU before that one and I couldn't. It came up with an error that said invalid vendor ID or something similar)
The restore seemed to go fine until the update utility told me everything was done and rebooted my phone. End result was that the phone's LCD is now not working at all. I've checked the back of my phone's box and all that is written in there is:
Display - 3.7-inch touch-sensitive screen.
The phone boots (it's making all the noises etc). I can get it into fastboot as well and get fastboot oem bootloader info etc. But ADB is not working and I've got a feeling the wrong RUU has been flashed hence screen death.
To make things worse, when I plug the desire into my laptop (with a fresh install of htc sync to flash new rom etc) device manager sees it as: qualcomm cdma technologies msm.
It won't recogize it as a htc desire at all. Tried a different laptop with new htc sync install etc but still the same issue.
Spent like 5/6 hours last night trying to figure this out but now I'm stuck.
Seems like the only access I have to the phone is via fastboot. Is there anything I can do to recover this phone?
Any help would be appreciated.
http://forum.xda-developers.com/showthread.php?t=768256
Try this.. in that thread go to post 2 .. their is section Recovery from broken screen
jhonybravo4u said:
http://forum.xda-developers.com/showthread.php?t=768256
Try this.. in that thread go to post 2 .. their is section Recovery from broken screen
Click to expand...
Click to collapse
had a look at that, however thing is I can't access adb at all..and i got a feeling my goldcard didn't work so I can't create a new one as i cannot find out the CID..
The only thing I can do is use fastboot to reboot into rebootRUU and try to flash the ROM manually. It keeps failing and giving the following error:
c:\android-sdk-windows\tools>fastboot flash zip rom.zip
sending 'zip' (164913 KB)...
OKAY [ 29.190s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 58.717s
Tried flashing a h3G rom and it flashes but still no screen...I can only find two h3g roms. anyone come across any other [uk] three network RUU?
Fixed!!!!
After much google searching/reading over here at XDA and modaco I finally figured it out
1) Made a new gold card, flashed a froyo RUU via fastboot which brought the SLCD back to life and gave me a working froyo unrooted rom (still with no adb/usb access)
2) Created a new misc partition img file using various guides available.
3) Used quanchi's guide to use rageagainstthecage exploit, to allow the misc partition to be flashed.
Laptop is correctly recognizing the desire now
Quitly Brilliant .. ;-) I guess 1st thing you need to do is create a goldcard while your mobile is working

Rom Advice / Steps please

Good Afternoon everyone,
Here once again. I have been having lots of problems recently with my phone memory getting low, crashes freezing, un-expected reboots etc. I have been using the same rom for a few months and was fine at first but just broke down. So I went into recovery and did a wipe now when powered on for the first time it doesnt get past boot animation just stay on the screen no matter how many reboots or further wipes. I also got a brand new 32GB Micro SD card for xmas that I haven't used yet so my idea was to get a new cool rom and use the SD card
First of all which rom. Now I know people say try different roms and see which you like but so many roms I dont know what to go for and was wondering for some advice. My requirements are that it is not ICS version as I get a phone upgrade on contract in July and want to leave ICS for a new phone so Gingerbread it is.
Now the rom requirements are:
> HTC Sense, prefferably a latest 3D version but if it doesn't work or very laggy then no.
> Camera needs to be fully working
> USB Tethering
> As much as possible on the SD card to save phone space
> Dont need super battery life but at least something that lasts a day and doesnt drain it
> Music Working nicely
> Not too buggy and fairly stable
Now secondly I still have not got myself familiar with Android flashing etc. If I want to start again from scratch new memory card does anyone know the steps. Is there any plain step by step instructions out there that tells me completly what I need to do as I can get confused quite easily.
Thanks in advance for any responses,
Regards,
Max
For this moment(in my opinion) this is the one from the best ROM for HTC Desire...including everything what you questing...
http://forum.xda-developers.com/showthread.php?t=1315961
Thanks. I was already interested in this rom and you saying that has swayed by boat. The next problem is how to go about it. the first steps appears to be installing EXT4 Recovery but its an APK and they are installed with the phone botted up normally correct? My phone isnt booting only in Recovery Mode which is the clockwork mod (from about 8 months ago)
4ext has an app to download its recovery. If you are s-off, the app will flash the recovery img.
Sent from my HTC Desire using Tapatalk
Ok I beleive I do have S-OFF from previous flashing however I can no longer boot the rom up so what do I do?
I can boot into recovery mode but as soon as I boot normally it just sits on the boot animation completly animated but never going further (left it for 3 hours until battery died) also tried wiping about 5 times after a wipe and I just cannot get it on. So what do I do?
I'll upload it for you (from my sd card).
If you are s-off, you can fastboot flash it (see link to my guides for info on fastboot flash - Forget adb, not relevant...)
Thanks but I am a little confused as to what I am doing.
Is there any step by step?
i have the 4EXT now not installed yet. What about HBOOT, radio rom I have no idea what I am doing in what order now due to my phone not botting :-(
If you don't have 4EXT recovery-reboot phone normally, install this app and update you're recovery from the list...
But if you read above I cannot boot my phone normally!
1.update the recovery(like i say)
2.change the hboot:downolad file PB99IMG.zip, put it on your sdcard, then start the phone in HBOOT mode (VolDown+POWER) to flash(update) the HBOOT.
3.Restart phone in recovery,perform full wipe(format all partition without FAT32)
4.Download file with ROM, put into your SDCARD and reflash...
I am sorry not having much luck. I have put both the EXT4 recoevry zip and the pb99img zip on my memory card rebooted into the boot loader with vol down went into the fastboot option and the only options there are bootloader (takes me back to main screen) reboot, reboot bootloader and power down.
I am so lsot and need my phone working again :-(
max_carpenter said:
But if you read above I cannot boot my phone normally!
Click to expand...
Click to collapse
If you'd bothered to read the fastboot faq I told you to read, you'd know that you fastboot flash from the fastboot screen NOT in Android!
max_carpenter said:
Irebooted into the boot loader with vol down went into the fastboot option and the only options there are bootloader (takes me back to main screen) reboot, reboot bootloader and power down.
Click to expand...
Click to collapse
Again, all in the FAQ you were supposed to read!!!
Sorry missed the link couldnt see one very tired. I appreciate your help. I am looking over it now trying to figure it out.
max_carpenter said:
Sorry missed the link couldnt see one very tired. I appreciate your help. I am looking over it now trying to figure it out.
Click to expand...
Click to collapse
OK good luck, although if you're tired, it may be better to wait until tomorrow. Its not broken so its just a case of remaining calm and doing the required.
Ok I think I got it phone is plugged in with the HBOOT drivers I h ave extracted that EXT4 zip you sent me to the C Drive and I run the following command:
fastboot flash recovery c:\recovery.img
Just wanted to check before I did it.
Hmm ok I have done something wrong :-(
sending 'recovery' (3730 KB)... FAILED (status malformed (1 bytes))
finished. total time: 0.004s
Ok I went into FASTBOOT on the phone screen then tried running the command again and I get this:
sending 'recovery' (3730 KB)... OKAY [ 0.676s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.197s
Are you sure you're s-off? Should say on the hboot screen
Sent from my HTC Desire using Tapatalk
Ahh its on damn I am sure it was off. Dont you have to be booted into a rom to get it off though?
Ok so who is clever enough to figure out the mess I am in now then..
1: Custom rom Won't boot even after wipe/several reboots
2: HBOOT Version = PVT1 0.93.0001
3: Radio Version = 5.09.05.30_2
4: Recovery Image is ClockworkMod v2.5.0.7
5: S-ON is set
6: Running the HTC Official RUU returns this error after a little while:
ERROR[140]: Bootloader version error
7: I have been asked to run the following commands with the following files and results are on each line after the = sign:
fastboot erase cache = OK
fastboot oem rebootruu = ... INFO[ERR] Command error !!!
fastboot flash zip C:\rom.zip = INFOsignature checking...
FAILED (remote: not allowed)
fastboot flash zip C:\PB99img.zip = FAILED (remote: signature verify fail)
rom.zip was extracted from the official HTC RUU utility.
Any ideas? At the moment i will be pleased jsut to get back to stock.

[Q] Flashed EU HOX with AT&T stuff and BRICKED! Please help

I'm desparate, please help me!
I flashed the remove-3-dot for the AT&T HOX, but I have another one. Now I cannot go back, since the device doesn't completely boot.
It is stuck with the HTC figures showing up and halfway the music stops and the device hangs.
I can go to recovery, but since the Àll-In-One Kit from Hasoon2000 doesn't see the device when in recovery (CWM 5.8.2.7 Touch), I cannot even put anything to the SD card, so I cannot even flash anything else!
Please help me before the battery dies out!! (I cannot turn it off since lonng press of the power button only restarts the booting)
If you have CWM did you made a nondroid backup?
Bright.Light said:
I'm desparate, please help me!
I flashed the remove-3-dot for the AT&T HOX, but I have another one. Now I cannot go back, since the device doesn't completely boot.
It is stuck with the HTC figures showing up and halfway the music stops and the device hangs.
I can go to recovery, but since the Àll-In-One Kit from Hasoon2000 doesn't see the device when in recovery (CWM 5.8.2.7 Touch), I cannot even put anything to the SD card, so I cannot even flash anything else!
Please help me before the battery dies out!! (I cannot turn it off since lonng press of the power button only restarts the booting)
Click to expand...
Click to collapse
THIS will help you
@muamers: Thanks!!
I already found out how to turn the device off, not draining the battery anymore.
I also flashed the new CWM 5.8.3.1 so it should have some ability to charge.
I am currently downloading the latest stock 1.29.401.11 and will try to flash that one.
I did search, but it's difficult currently. However, I made a permanent link to the Wiki - it's more than useful (the reason it exists, I know...)
Oh - it wasn't bricked (because it still did some stuff)
@jeyml: No, I did not do that (didn't know it was possible)
Does that mean that I could recover with the rom exactly as it was put on the device? (including installed ZIP files)
Bright.Light said:
@muamers: Thanks!!
I already found out how to turn the device off, not draining the battery anymore.
I also flashed the new CWM 5.8.3.1 so it should have some ability to charge.
I am currently downloading the latest stock 1.29.401.11 and will try to flash that one.
I did search, but it's difficult currently. However, I made a permanent link to the Wiki - it's more than useful (the reason it exists, I know...)
Oh - it wasn't bricked (because it still did some stuff)
@jeyml: No, I did not do that (didn't know it was possible)
Does that mean that I could recover with the rom exactly as it was put on the device? (including installed ZIP files)
Click to expand...
Click to collapse
Yup.It is actualy quite simple,i always do a backup before i flash something or update my ROM and other stuff.You keep the volume down + power button.After that you enter recovery mode (you will need to have CWM) and you have an option there "backup and restore",enter there and make a backup.Next time if you have any problems just enter again in the CWM,go to "backup and restore" and restore the backup you've made.It saves everything you have (i mean the ROM setting and such.Apps and other stuff must be backed up with Titanium Backup).
The backups you made are saved in the SD card in the nandroid directory if i remember corectly,so if you update you're ROM to...1.29 for example and have a 1.28 backup just enter there and delete it and make a new backup of the 1.29 so you don't get confused in so many backups and if you ever have problems and restore a 1.28 backup on you'r 1.29..well...you realize that the phone isn't going to work anymore.So,be carefoul.
Didn't work... I downloaded this rom: RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed
did everything this page told us: http://forum.xda-developers.com/showthread.php?t=1609190
But I do not see anything change... It's still stuck in the boot process.
I don't know what I am doing wrong...
I also didn't find a clear guide for how to do things - it's all pieces which everyone has to put together, making it hard when there is a real problem.
If this can be solved, I will investigate the nand backup for certain!
For now I need my phone, but it does not work...
Oh - how does the charging with the new clockwork work? I don't see anything happen, so I am afraid the battery will be down soon.
edit: It was on power all night and when I looked it had the screen on. Unplugging and replugging and the gren light went on. Does that mean the battery is filled?
One important fact: the adb command cannot find the device and I don't know why!
How did you flash the RUU? You have to connect the phone in FASTBOOT to the PC and then run it (with a locked bootloader) and it replaces the entire system
EddyOS said:
How did you flash the RUU? You have to connect the phone in FASTBOOT to the PC and then run it (with a locked bootloader) and it replaces the entire system
Click to expand...
Click to collapse
with a LOCKED bootloader?
Mine is unlocked...
I will try to relock the boorloader (saw somewhere a snippet)
Tried with a locked one:
Code:
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot oem lock
... INFOLock successfully...
OKAY [ 0.143s]
finished. total time: 0.143s
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot flash boot boot_signed.img
sending 'boot' (4288 KB)... OKAY [ 0.667s]
writing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.874s
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot flash system system.img
sending 'system' (963584 KB)... FAILED (remote: (00000008))
finished. total time: -0.000s
The bootloader loocks relocked ok (as it shows on top of that screen)
But flashing is impossible and, of cause, I don't know why
Adb will work in recovery but only if you boot the recovery from fastboot.
Fastboot boot recovery recovery.img
ok, next approach:
- Booted to fastboot
- unlocked bootloader with the unlock .bin file
- fastboot boot Recoveries\CWM5.8.3.1.img
- adb push rom.zip /sdcard/
- waited 5 minutes until done
- in recovery: Install zip from sdcard
- manual selected the rom.zip (yes, it was actually on the SDcard, so adb did its job)
- got an error that the image was bad:
ClockworkMod Recovery v5.8.3.1
-- Installing: /sdcard/rom.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/rom.zip
I think I will have to get another image, right?
This one was extracted from
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed.exe
I started the program and searched for the rom.zip in my temp folder. Was this ok?
Run .11 RUU, wait until load all completely, now go to %temp% in your pc and find a folder that contain a ROM.ZIP file... Unzip the files and flash the boot_signed.img and the recovery_signed.img, then relock your phone fastboot oem lock) do a factory reset (with the new recovery) and then try to run the .11 RUU.
THAT SHOULD WORK
pd: sorry for my poor english.
Sent from my HTC One X using XDA
Bright.Light said:
ok, next approach:
- Booted to fastboot
- unlocked bootloader with the unlock .bin file
- fastboot boot Recoveries\CWM5.8.3.1.img
- adb push rom.zip /sdcard/
- waited 5 minutes until done
- in recovery: Install zip from sdcard
- manual selected the rom.zip (yes, it was actually on the SDcard, so adb did its job)
- got an error that the image was bad:
ClockworkMod Recovery v5.8.3.1
-- Installing: /sdcard/rom.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/rom.zip
I think I will have to get another image, right?
This one was extracted from
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed.exe
I started the program and searched for the rom.zip in my temp folder. Was this ok?
Click to expand...
Click to collapse
You haven't a clue have you?
You don't flash an RUU from CWM, it's a Windows application!
1. Boot phone into FASTBOOT
2. Connect to the PC
3. Lock the bootloader
4. Run the RUU
Job done
@wolfraim: Yes, the factory reset was the one culprit, it seems!
EddyOS: Tried that so many times, but finally wolfraim added a crucial point: Factory reset!
Now the RUU install from the PC is working... (Have to wait for some time ...)
* I have to go for now, right after the flash is done.
When I've got the time, I will try to make some more notes and maybe another step-by-step story on how to make the device work again.
Thank you very much for your patience and help!
This is why I love the xda-developers site so much!
(and all possible ways included on XDA to brick my device is the reason why I hate xda sometimes... )
edit: Flashing has succeeded! Software number: 1.29.401.11, so it seems I also have the latest ROM update now.
I'll make a recovery backup asap and will try the titanium backup too.
Oh, this one is SU-locked of cause, so I will have to install the SU zip file again... Much work is to be done yet. Maybe I should look for a good ROM in the Android development area.

Nexus 7 completely bricked?

So I have no OS on my Nexus 7, nor can I flash one. All conventional methods of installing an operating system on to this POS have met with utter failure.
Brief histroy:
-Had CM 11 nightly build until it "imploded" (any shortcut would take me to a PIN screen, users deleted profiles deleted themselves, random reboot every 5 minutes) and stopped functioning.
-Decided to return to an earlier of CM, so I dl'd an earlier version and pushed the .zip to CWM recovery. Big mistake. CWM decided to repartition everything in an erroneous manner rather than just wipe Dalvik cache.
-Now CWM will not open any .zip pushed through ADB. Just a generic "failed to open file" message.
-Sheer desperation and four hours of driver Hell finds me in fastboot and trying to flash a stock image.
-Latest Android system image will not flash. Period. Using the flashall.bat script, the error about a missing system.img pops up. I am staring at system.img right next to the .bat.
-Download Android L preview and run flashall.bat, operating system installs after about 30 minutes and numerous errors that the script "seemed" to fix about missing partitions.
-Reflash TWRP
-Android L gets stuck in non-bootable state (spinning colored ball logo thing) after a random restart.
-Now TWRP cannot find any .zip that I manually push through ADB. I can see it in File Manager, but nowhere else. Flashing custom ROM at this point not possible.
-Return to Android KitKat stock image and manually flash system.img through fastboot. Tablet will not boot, goes directly to black screen after bootloader.
So WTF do I do at this point? I have just about had it with all things Android right now. CWM doesn't work. TWRP doesn't work. Stock images don't work. Fastboot doesn't work. What else is there?
Cortimi said:
So I have no OS on my Nexus 7, nor can I flash one. All conventional methods of installing an operating system on to this POS have met with utter failure.
Brief histroy:
-Had CM 11 nightly build until it "imploded" (any shortcut would take me to a PIN screen, users deleted profiles deleted themselves, random reboot every 5 minutes) and stopped functioning.
-Decided to return to an earlier of CM, so I dl'd an earlier version and pushed the .zip to CWM recovery. Big mistake. CWM decided to repartition everything in an erroneous manner rather than just wipe Dalvik cache.
-Now CWM will not open any .zip pushed through ADB. Just a generic "failed to open file" message.
-Sheer desperation and four hours of driver Hell finds me in fastboot and trying to flash a stock image.
-Latest Android system image will not flash. Period. Using the flashall.bat script, the error about a missing system.img pops up. I am staring at system.img right next to the .bat.
-Download Android L preview and run flashall.bat, operating system installs after about 30 minutes and numerous errors that the script "seemed" to fix about missing partitions.
-Reflash TWRP
-Android L gets stuck in non-bootable state (spinning colored ball logo thing) after a random restart.
-Now TWRP cannot find any .zip that I manually push through ADB. I can see it in File Manager, but nowhere else. Flashing custom ROM at this point not possible.
-Return to Android KitKat stock image and manually flash system.img through fastboot. Tablet will not boot, goes directly to black screen after bootloader.
So WTF do I do at this point? I have just about had it with all things Android right now. CWM doesn't work. TWRP doesn't work. Stock images don't work. Fastboot doesn't work. What else is there?
Click to expand...
Click to collapse
Is this an LTE or WiFi model? Do you have the nexus root tool kit installed on your computer and able to get to fastboot?
someolddude said:
Is this an LTE or WiFi model? Do you have the nexus root tool kit installed on your computer and able to get to fastboot?
Click to expand...
Click to collapse
WiFi model, fastboot and adb are fine, no toolkits.
Cortimi said:
WiFi model, fastboot and adb are fine, no toolkits.
Click to expand...
Click to collapse
Get the toolkit by wugfresh and you should be able to restore it.
someolddude said:
Get the toolkit by wugfresh and you should be able to restore it.
Click to expand...
Click to collapse
Nope. Using the Flash Stock + Unroot option gives the exact same error as doing it manually.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
OKAY [ 1.283s]
finished. total time: 1.412s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 754455404 bytes
error: update package missing system.img
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
Click to expand...
Click to collapse
Attempting to flash CWM recovery (found here: http://forum.xda-developers.com/showthread.php?t=2583845) results in a stuck bootloader screen. I was able to re-flash TWRP, but it is still useless as it simply does not function in any useful manner whatsoever.
Cortimi said:
Nope. Using the Flash Stock + Unroot option gives the exact same error as doing it manually.
Attempting to flash CWM recovery (found here: http://forum.xda-developers.com/showthread.php?t=2583845) results in a stuck bootloader screen. I was able to re-flash TWRP, but it is still useless as it simply does not function in any useful manner whatsoever.
Click to expand...
Click to collapse
Same problem with mine, cm11 as well.
I like some of the CM features but ever device Ive flashed and had trouble with it has been when Ive went with "Cyanide Mod"
You figure something out, please let me know and I will do the same.
I've got the LTE but my daughter has the WiFi only and is also unlocked. I can make a bone stock backup of here's which is on 4.4.4 if you want to try and restore it to yours.

Categories

Resources