[Q] Stuck at Clockwork Recovery screen? HELP!??! - G1 Q&A, Help & Troubleshooting

I am currently stuck at the clockwork recovery screen. BTW i did the one click root...didnt break stock bootloader. not sure if this makes a difference or not. i was told it didnt...? i cant get back to stock firmware and i cant load zx2.1 sense i keep getting errors on both and i really have no idea what the hell to do from here. error on zx2.1 is as E:cantchown/mod/system/xbin (no such file or directory)
E:failure at line 17: set_perm_recursive 0 2000 0755 -6755 system:xbin
installation aborted

If you have stock SPL those roms will not fit ito your system partition. They need danger spl or the recent mtd partiton hack.
You can also try a donut rom without sense, they usually fit stock spl system.
€: If you want to go back to stock rom, you need the correct dreamimg.nbh for your device on your sd card and flash it via bootloader. This will obviously break root.
Sent from my HTC Dream using XDA App

mblaster said:
If you have stock SPL those roms will not fit ito your system partition. They need danger spl or the recent mtd partiton hack.
You can also try a donut rom without sense, they usually fit stock spl system.
€: If you want to go back to stock rom, you need the correct dreamimg.nbh for your device on your sd card and flash it via bootloader. This will obviously break root.
Sent from my HTC Dream using XDA App
Click to expand...
Click to collapse
How can i get it flashed via bootloader when i cannot load anything on it? i cant get past the clockwork recovery screen. ive downloaded the dreamimg and i just dont know wth to do

BenDiesel said:
How can i get it flashed via bootloader when i cannot load anything on it? i cant get past the clockwork recovery screen. ive downloaded the dreamimg and i just dont know wth to do
Click to expand...
Click to collapse
This is the guide I used to downgrade. Make sure you have the right image file for your phone, and make sure your battery is fully charged and the process is not interrupted.
http://forum.xda-developers.com/sho...&highlight=original+spl+downgrade#post5640154

oldnoob said:
This is the guide I used to downgrade. Make sure you have the right image file for your phone, and make sure your battery is fully charged and the process is not interrupted.
http://forum.xda-developers.com/sho...&highlight=original+spl+downgrade#post5640154
Click to expand...
Click to collapse
ive given up. my computer will not read my g1. its like its not there. and ive downloaded 5 dreamimg's and for some reason the g1 says theres no image file. i just boot to clockwork recovery and thats it...

BenDiesel said:
ive given up. my computer will not read my g1. its like its not there. and ive downloaded 5 dreamimg's and for some reason the g1 says theres no image file. i just boot to clockwork recovery and thats it...
Click to expand...
Click to collapse
The computer doesn't need to see the phone. Put the file on the root of the sd card, the name of the file has to be correct and is case sensitive, DREAIMG.nbh IIRC. Power down the phone, insert the sd card, press and hold the camera button while you power it on until you see the bootloader screen. The phone should see the file and take it from there.

oldnoob said:
The computer doesn't need to see the phone. Put the file on the root of the sd card, the name of the file has to be correct and is case sensitive, DREAIMG.nbh IIRC. Power down the phone, insert the sd card, press and hold the camera button while you power it on until you see the bootloader screen. The phone should see the file and take it from there.
Click to expand...
Click to collapse
It was already in all caps...exactly as you said it had to be. not sure what the iirc means but it still is doing the same. some people have said it could be corrupted but how the hell can it be corrupted after 5 different ones. i feel like throwing the damn thing in the furnace!

BenDiesel said:
It was already in all caps...exactly as you said it had to be. not sure what the iirc means but it still is doing the same. some people have said it could be corrupted but how the hell can it be corrupted after 5 different ones. i feel like throwing the damn thing in the furnace!
Click to expand...
Click to collapse
Sorry, IIRC = If I Remember Correctly.
The file name is upper case, the .nbh is lower case. To check the validity of the file you can search for and download an MD5 sum checker, but after 5 attempts I doubt that would be it. The only things I can think of is either a problem with the card, or something with the phone. Try reformatting the card making sure it's a FAT32 full format, not a quick format. Hopefully one of the Android gods around here will see this have some better ideas.

oldnoob said:
Sorry, IIRC = If I Remember Correctly.
The file name is upper case, the .nbh is lower case. To check the validity of the file you can search for and download an MD5 sum checker, but after 5 attempts I doubt that would be it. The only things I can think of is either a problem with the card, or something with the phone. Try reformatting the card making sure it's a FAT32 full format, not a quick format. Hopefully one of the Android gods around here will see this have some better ideas.
Click to expand...
Click to collapse
ya its jus like this DREAIMG.nbh man i did the one click root didnt break bootloader....tried to boot load the regular rom and nothing man. im done with it. its tottally effed in my opinion....ive tried everything i can think of...

You really have to make sure you got the right DREAMIMG.nbh. If you have e.g. a T-Mobile G1 get the newest for T-Mobile. Be sure to have the newest, as it is possible that older versions are not flashable either. There are lots of those images around, and if you try them at random they are quite sure not to work.
Also there might be problems if the SD-Card is not formated properly. If you have an external reader, take it out and format it on your pc. Then put the (correct) image on it.
Perhaps if you tell us the brand of your mobile, we can try to guide you to the right image.

mblaster said:
You really have to make sure you got the right DREAMIMG.nbh. If you have e.g. a T-Mobile G1 get the newest for T-Mobile. Be sure to have the newest, as it is possible that older versions are not flashable either. There are lots of those images around, and if you try them at random they are quite sure not to work.
Also there might be problems if the SD-Card is not formated properly. If you have an external reader, take it out and format it on your pc. Then put the (correct) image on it.
Perhaps if you tell us the brand of your mobile, we can try to guide you to the right image.
Click to expand...
Click to collapse
no longer a newb....got this f'er working again and boy flashed a rom! back in the game!

Related

So if i intentionally brick my phone...

...the insurance company wont ever be able to figure out that i rooted it and come for money?
I downgraded to the original bootloader but cant get rc29 back on, i just get the gray screen to flash for a split second (it says 'no file...') i still have cyanogen 1.3.1 and i flashed ion to have something to work with but i read that i can pull the battery during a flash and just brick it. thanks
DMaverick50 said:
...the insurance company wont ever be able to figure out that i rooted it and come for money?
I downgraded to the original bootloader but cant get rc29 back on, i just get the gray screen to flash for a split second (it says 'no file...') i still have cyanogen 1.3.1 and i flashed ion to have something to work with but i read that i can pull the battery during a flash and just brick it. thanks
Click to expand...
Click to collapse
Are you sure that your sdcard is formatted to fat32? The no file found usually indicates that it isn't.
h.nocturna said:
Are you sure that your sdcard is formatted to fat32? The no file found usually indicates that it isn't.
Click to expand...
Click to collapse
good call thanks, i may have put it on the new card that came with the new phone, which i suppose isnt set to fat32 by default. But the boot flashed ok, would it do that if it wasnt fat32?
DMaverick50 said:
good call thanks, i may have put it on the new card that came with the new phone, which i suppose isnt set to fat32 by default. But the boot flashed ok, would it do that if it wasnt fat32?
Click to expand...
Click to collapse
No problem, seen it before and just passing the info along. I don't think it should affect the boot.img as that is flashed from terminal, and I don't think terminal is as discriminating as the bootloader.
h.nocturna said:
No problem, seen it before and just passing the info along. I don't think it should affect the boot.img as that is flashed from terminal, and I don't think terminal is as discriminating as the bootloader.
Click to expand...
Click to collapse
that worked its updating, however my trackball doesnt work and i think im supposed to use it after the install. wonder if theres a workaround...
edit: i wound up pulling the battery and it booted up just fine so i think im set to send it back in, thanks again for the help it wouldve cost me up to $300 to the insurance if anything went wrong on my end...the build number says "kila-..." i cant remember if thats original

how to flash a new room to an already rooted phone?

Hi
I have flashed my G1 T-mobile following the the one-click process in here! i have now root access. The ROM is CyanogenMod-3.9.11.2
After all that i bought a trascend SDcard 8GB class 6, formatted about 600MB to EXT4 using gparted on a live cd, winxp and my G1.
The first thing i noticed is that the phone is slower to load up. it stays about 35secs on the G1 logo and then move to android for a total of about 1min to be ready.
Second thing my free space on internal memory went from 38MB to 68MB, i believe somehow the phone moved the cache on the sdcard...if i install new programs they get installed on the phone memory as far as i understand...however i could be wrong on this. i never started the phone without sdcard since, I'm not sure if this could damage the phone in some way.
I would like to have some feedback on this (the slow boot and memory thing) if someone has experienced a similar situation.
I'm thinking to flash my phone again and move to a stable version of Cyanogen so that i can use app2Sd and Cyanogen updater!!
- how can i flash a new room, considering that i have the latest radio but not HARDspl. (as far as i understand the oneclick method doesn't change the SPL)
I was looking at using again the small oneclick software and flash the Cyanogen 4.0 this time, would that make sense since i have already root access on the phone?
thank you for the help
kirk
update
After installing and unistalling few softwares i found out that all programs are actually on the SDcard however the Mobile uses still the internal memory for the cache. This doesn't bother me for now since i still have about 68MB free. Basically if you install CyanogenMod and you don't have a partitioned SDcard all software get installed on the internal memory however as soon as you put in an partioned card all programs get transfered automatically after the first boot. At least this is what happen to me. Somehow i got what i wanted and because of this i don't need to flash my phone anymore... maybe I'll flash it again when android 2 is out, if i don't have to change spl, image recovery or anythingelse too risky
I used the 1-click method as well, and I just download the latest cyanogen rom, rename it to update, boot into cm-recovery and apply the update.
One more thing, the latest versions of Cyanogen's rom have auto apps2sd built into the rom. It will automatically move all apps to the sd card as long as you have an ext2/ext3/ext4 partition on your sd card.
Your still going to have the same boot time. It's still going to take awhile to boot, just because you have a custom rom doesn't mean it will boot faster. And to load a new rom either rename to update.zip and update or if you have the newest recovery then you can just flash whatever rom without renaming because you can flash any .zip file.
In reading your post I think you said you wanted to use the small 1 click software to download cm4.0 You are done rooting your phone you no longer need to use the 1 click software.
Just copy new rom (cm4.0.4) to sd card
unplug phone from computer
turn off phone
boot into recovery (home and power at the same time)
flash new rom
when you use one root, it flashes cm-recovery 1.4 so there is no need to rename, just put on the root of your sd and flash from recovery
supremeteam256 said:
Your still going to have the same boot time. It's still going to take awhile to boot, just because you have a custom rom doesn't mean it will boot faster. And to load a new rom either rename to update.zip and update or if you have the newest recovery then you can just flash whatever rom without renaming because you can flash any .zip file.
Click to expand...
Click to collapse
Are you aware of any reason for the slow boot after partition of the sdcard??
is it the stock 1GB sdcard?
Cause it has to read from the sd during boot up and it has to run the script for the apps2sd
Fingerlickin said:
is it the stock 1GB sdcard?
Click to expand...
Click to collapse
no is a transcend 8GB class 6.
gridlock32404 said:
Cause it has to read from the sd during boot up and it has to run the script for the apps2sd
Click to expand...
Click to collapse
As far as i know i'm not using app2sd yet. I partitioned my SDcard ONLY after i flashed my phone. however like i said i think the phone is somehow using the ext4 partition for something.
You reckon this would be a normal boot time i mean it takes between 50secs and 1.05 min to be ready. Phone is stable as far as i can tell.
I myself am not concerned with the boot time, the ext4 is another filesystem that it has to read and recongize, you basicly have a little mini computer in your hands so how long does your pc take to load up, there are many files and system checks that it has to go through starting up not to mention all the settings and components it has to turn on
Bottom line, if you want something to boot up quickly than get a basic phone because there is a very good way to speed up a mini computer to do the same
gridlock32404 said:
I myself am not concerned with the boot time, the ext4 is another filesystem that it has to read and recongize, you basicly have a little mini computer in your hands so how long does your pc take to load up, there are many files and system checks that it has to go through starting up not to mention all the settings and components it has to turn on
Bottom line, if you want something to boot up quickly than get a basic phone because there is a very good way to speed up a mini computer to do the same
Click to expand...
Click to collapse
Well i'm aware of all this and i'm not concerned too much about the boot time. I'm only trying to gather information and learn a bit more from other ppl experiences. I come from windows mobile and android OS is all new world for me.
have you a similar configuration to my G1? Do you run app2sd? is yor boot time similar to mine??
maybeoneday said:
Just copy new rom (cm4.0.4) to sd card
unplug phone from computer
turn off phone
boot into recovery (home and power at the same time)
flash new rom
Click to expand...
Click to collapse
Just a quick question for future reference...
do i need to put Cyanogen recovery image on the root of the sd card when i boot into recovery mode?
thank you
Kirk
Why did you root your phone? You have no desire to search to even do one of the most well documented things to your phone in these forums. What you need to do is take a DREAIMG.nbh file and put it in the root of your sdcard (or in no folders), then open up terminal emulator and type su then reboot bootloader once that happens wait for it to flash that image. Then you will have the most pimping room on your phone. Also you have amazing boot times. Everything you want.
david1171 said:
Why did you root your phone? You have no desire to search to even do one of the most well documented things to your phone in these forums. What you need to do is take a DREAIMG.nbh file and put it in the root of your sdcard (or in no folders), then open up terminal emulator and type su then reboot bootloader once that happens wait for it to flash that image. Then you will have the most pimping room on your phone. Also you have amazing boot times. Everything you want.
Click to expand...
Click to collapse
Hi David
I had specific reason to root 2 different G1 and this is not to play with it or try a new ROM or even experiment new things. I may change my ROM again when a major relase is out (i.e. Android 2 if it has something that i need)
Going back to reflashing the phone.
You now suggest me to use DREAIMG.nbh which is actually mentioned on the guide "hoe to downgrade-root-flash your phone" here
....am I missing something here?? thank you for taking the time to reply anyway.
..I have read quite a bit on this forum and i decided to use the one-click method (because is the quickest and safiest one). I thought reflashing should be as easy. go in safe mode wipe and reflash it. Anyway for my nature i tend to ask/investigate one thing before go and actually do it. My questions are:
- if i press home power right now, considering that i have nothing on my sdcard would it take me to the safemode screen?
- Consequently do i need to have Cyanogen image revovery together with the ROM on my sd card in order to flash a new version of CyanogenMod?
Thank you
Kirk
you can boot into recovery at any time by pressing home and power when the phone is powered down. it will go into recovery no matter what is on the sdcard.
Also the recovery image you have on your phone does not determine what rom you can flash.
wow... i am at a loss for words...... do you even know why you did any of the things you did? did you even read the release notes for cyan's rom's? ALL OF THE ANSWERS TO YOUR QUESTIONS ARE THERE...
if you have an ext partition on your sd card....it WILL AUTOMATICALLY be used for apps2sd with 80%-90% of the ROM's out there today... ITS IN ALL OF THE ROMS' CHANGE LOGS/RELEASE NOTES
I had specific reason to root 2 different G1 and this is not to play with it or try a new ROM or even experiment new things. I may change my ROM again when a major relase is out (i.e. Android 2 if it has something that i need)
Click to expand...
Click to collapse
if you didnt root to try a new rom or experiment with new things, your better off with the stock firmware...which is why david suggested you flash DREAIMG.nbh
go in safe mode wipe and reflash it
Click to expand...
Click to collapse
going into safemode wont flash anything.... i suggest you search and find out what exactly safemode is, especially since there was a thread only a few threads below yours detailing it.
All you need to flash a new ROM is the rom on your sd card and a working recovery, as well as anything that the ROM your installing has required which are noted in the changelog/release notes....
nothing else is needed on your SD card, except maybe specific partitioning, which will be noted in the ROM's requirements.
I try to help out here as much as i can when i have time (most of my posts are in Q&A helping out people) but it seems as though no one even bothers to look at the actual forums anymore. They just create an account, create a thread, bug people till a simple question is answered, and disappear forever.....
I came to this site simply to get roms, but i stayed because there was so much to learn and i created an account to help out people as well...i did all of my major modifications without asking any questions....all the questions are already answered somewhere...
i understand its hard to go through all the clutter, but it is starting to look as if no one even cares anymore
@B-man007 i am starting to feel like you do, i had my phone rooted and all that good stuff at least a month before i made an account just to download something uploaded to the forum. I wish i could see how many post i have in a ceratin forum bc i imagine at least 450 or 500 of them would be in this one helping people. Its getting to the point where i no longer care to help people and i thought i had a lot of patience. I porbably do but people are sinking to new lows with the questions they ask...
I think I have maybe 5 posts in dev, most of my posts are q&a and general, but then again half of those posts are from hijacking threads. I just got tired of answering the same questions over and over and over
gridlock32404 said:
I think I have maybe 5 posts in dev, most of my posts are q&a and general, but then again half of those posts are from hijacking threads. I just got tired of answering the same questions over and over and over
Click to expand...
Click to collapse
u hijack the hell outa threads. there should some type of entrance exam for xda. like do u know how to search, can u read do u have a brain. i mean god i actually helped a guy who couldnt open the terminal

Kind of stuck....

My better half bought a used Gi that we were gonna root and take over to cyanagens 4.04. but ran into a prob it has no root but the recovery operates similer to cyanagins with the list it refuses to take any unsigned updates. including the roll back to rc 29 for rooting . any thoughts or suggestions would be useful
Is it a uk g1 if so try th rc 7
its US (ishould think here in missouri) it keeps checking signing doesnt find what its looking for and refuses to update
trystlore said:
its US (ishould think here in missouri) it keeps checking signing doesnt find what its looking for and refuses to update
Click to expand...
Click to collapse
make sure you format the sdcard to fat32.... please post questions in the correct forum or at the STICKY at the top of the thread!
Moved to Q&A as not Development, please post in correct sub forums, thankyou, stylez.
Moved to Q&A
grr sorry on the post area thing.. this has me annoyed. the SD is fat32 interesting thing about this (not sure if it is causing the issue) i get a check media for errors warning when i mount the SD card. Would (or could) a possable corrupt file system on the sd card maybe be the issue? Just a thought i'll look into that meantime.
Try reformatting the sdcard again and see if that helps
is it a modified or stock recovery img? And are you trying to flash the dreaimg.nbh as an update.zip thru recovery? Cuz you flash that from the serial0 page on the spl, boot holding camera, file should be named DREAIMG.nbh if I'm not mistaken. if your recovery img is stock then its looking for release keys, hacked recovery img's check for development "test" keys...
lookslike a modified recovery just for home to reformat the SDcard gonna see if that helps
Could you possibly post a pic of what it looks like? The recovery is different from the bootloader/spl. Sounds weird tho.
ok put the dreaming.nbh on again and didn't change it to update this time still no joy. its refusing to take it at all
I think it has to be all caps, for the name, and lowercase for the extension. DREAIMG.nbh If you downloaded it from a zip file, make sure you extract it first.
pic in a sec no screen cap atm but ill see about a pic taken from my phone.
DREA100 PVT 32B
HBOOT-0.95.0000
cpld-4
newest radio
as features goes. Hero rom = Flash within the Browser. CM/Cupcake build, no flash yet.
Thats one feature I know of
this is my recovery that keeps refusing to see my updates due to failing verification
odd part is never had issues like this before
Is that also what you get when you try to boot into the bootloader? Holding the camera and power buttons or holding the back and power buttons?? That's where you would use the DREAIMG.nbh file
nope it grey screens for just a split sec and says no image found then back to multi colored screen
Not sure. Sounds like the sdcard is bad, or sdcard slot on the phone is damaged. Does the phone read the sdcard?
Another idea I got is too.....look for and download all the signed updates you can find on the net, and try each one, making note of who signed it. Maybe the phone will accept one of the original signed updates.
Other then that, idk.

Nexus one only going to the "Android system recovery <2e>" screen

When booting the Nexus One I get an Android with an explanation point, then I am able to toggle the volume key and power to get into "Android system recovery <2e>" screen which gives me the options
-reboot system now
-apply sdcard:update.zip
-wipe data/factory reset
-wipe cache partition
when it's in this screen I can NOT access it through fastboot or adb.
It looks like it is only allowing me to push "officially" signed update.zip files to it and nothing else.
I cannot get it in to hboot or anything else it ONLY boots into "Android system recovery <2e>"
Maybe someone has an official update.zip boot image they can send me to or some other idea it would be much appreciated since I cannot use the phone at all.
Thank you in advanced, Please help!!!
Did you try holding trackball and power button when the phone is turned off to bring you directly to fastboot?
irishrally said:
Did you try holding trackball and power button when the phone is turned off to bring you directly to fastboot?
Click to expand...
Click to collapse
Yes, with no luck, it just goes straight to the Android and explanation point
Are you rooted? Unlocked bootloader? What did you do to get you into this situation?
Not to worry you, but usually not being able to boot into fastboot is not a good thing.
hyperandy said:
Maybe someone has an official update.zip boot image they can send me to or some other idea it would be much appreciated since I cannot use the phone at all.
Thank you in advanced, Please help!!!
Click to expand...
Click to collapse
Heres a thread that contains the official 2.1 update1 zip.
http://forum.xda-developers.com/showthread.php?t=627823
Maybe the volume key or trackball is stuck/damaged?
irishrally said:
Are you rooted? Unlocked bootloader? What did you do to get you into this situation?
Not to worry you, but usually not being able to boot into fastboot is not a good thing.
Click to expand...
Click to collapse
ya at this point I was kinda figuring that but I am hopeful ...I unlocked the boot loader and everything was going great until I partitioned the sd in the recovery image, then I started getting a weird MISC error and couldn't boot up at all, only in recovery but fastboot and everything still worked. Then I saw a post about applying the original image to the device via fastboot, preformed that and ever since then I have had a $500 brink that lights up
I don't think you can brick the N1 by just flashing a ROM, usually this only happens when changing the radio or spl.
I would try taking out your sd card, copy all your files you your computer, format your sd card, copy your files back to your sd card and see what that does for you. Maybe some issue arose when you partitioned your sd card, although you said fastboot still worked until you flashed the ROM. Worth a shot though.
If you can access fastboot then, I would flash Amon Ra's custom recovery image via fastboot and take it from there.
well I actually tried a completely different sdcard and then none at all. No luck. If it's not letting me into hboot do you think it may have gotten corrupted or something
hyperandy said:
well I actually tried a completely different sdcard and then none at all. No luck. If it's not letting me into hboot do you think it may have gotten corrupted or something
Click to expand...
Click to collapse
Honetly, I don't know. Did you try copying the .zip in the link posted above to your sdcard and then applying that zip in recovery?
Hopefully someone that knows more than me will chime in and have some better ideas.
irishrally said:
Honetly, I don't know. Did you try copying the .zip in the link posted above to your sdcard and then applying that zip in recovery?
Hopefully someone that knows more than me will chime in and have some better ideas.
Click to expand...
Click to collapse
maybe it's because I just woke up but I am not clear what you are asking, can you rephrase that? The link above my SD card?
hyperandy said:
maybe it's because I just woke up but I am not clear what you are asking, can you rephrase that? The link above my SD card?
Click to expand...
Click to collapse
Did you try copying the .zip file in the link below to your sd card and trying to flash it in recovery?
http://forum.xda-developers.com/showthread.php?t=627823
Thank you, ya I didn't see the link the first time. duh. Yep I tried that and I get a build.prop error (although this update says installing for a second and i see a progress bar, I have tried that same file from a few download locations to make sure it wasn't a bad download too):
file_getprop: Failed to stat "/system/build.prop": No such file or directory
E:Error in /sdcard/update.zip
(status 7)
Installation aborted
Thank you for all your help!! but I am afraid this isn't looking to good.
I also tried creating that file just to see but since it wasn't officially signed it gave me an error about that
I think at this point it is looking for a specific signed update.zip file, where I find that, I have no idea.
It almost seems like I need the whole update.zip officially signed by google and/or HTC and then it would flash. I highly doubt they are going to hand that over. I am half temped to see if I could send it in to them to be reflashed even for a fee if it means I can get this thing working again, but I don't even know if they would offer that. It's only 2 months old and I think the file I need maybe out there but damned if I have been able to find it anywhere.
hyperandy said:
I think at this point it is looking for a specific signed update.zip file, where I find that, I have no idea.
It almost seems like I need the whole update.zip officially signed by google and/or HTC and then it would flash. I highly doubt they are going to hand that over. I am half temped to see if I could send it in to them to be reflashed even for a fee if it means I can get this thing working again, but I don't even know if they would offer that. It's only 2 months old and I think the file I need maybe out there but damned if I have been able to find it anywhere.
Click to expand...
Click to collapse
I wouldn't give up yet. I'm sure there is someone out there that can tell you you are completely hosed, or help you fix the problem.
If you can't fix it, I have heard it will cost $196 for a new motherboard if you send it in to HTC. They could just reflash your phone but I heard they handle a case like this by charging you for a motherboard swap. Second hand information though.
irishrally said:
I wouldn't give up yet. I'm sure there is someone out there that can tell you you are completely hosed, or help you fix the problem.
If you can't fix it, I have heard it will cost $196 for a new motherboard if you send it in to HTC. They could just reflash your phone but I heard they handle a case like this by charging you for a motherboard swap. Second hand information though.
Click to expand...
Click to collapse
I believe that, I work in the field service industry and I see stuff like that all the time. Although I would rather pay the 196 instead of 560+ again. I am almost 100% certain this could be re-flashed with the right file. but I have so far spent 2 full days trying different things, I think I will give it until tomorrow and then send it in (by then I should be good an sick of searching). Unfortunately, I am in love with my Nexus. it's been a while since I had a phone I really enjoyed as much. If I knew another great phone was coming out in a week I would probably say the heck with it and just buy the next one but this is still an awesome device.
hyperandy said:
I believe that, I work in the field service industry and I see stuff like that all the time. Although I would rather pay the 196 instead of 560+ again. I am almost 100% certain this could be re-flashed with the right file. but I have so far spent 2 full days trying different things, I think I will give it until tomorrow and then send it in (by then I should be good an sick of searching). Unfortunately, I am in love with my Nexus. it's been a while since I had a phone I really enjoyed as much. If I knew another great phone was coming out in a week I would probably say the heck with it and just buy the next one but this is still an awesome device.
Click to expand...
Click to collapse
Have you tried every option in all the other "HELP BRICK" posts?? I don't really have time to search (and my nexus is working fine) but I know there has been plenty of threads like this before. Multiple options where tried, some successfully and some not. I would not give up unless it won't power on at all. Does ADB logcat work during a boot? Fastboot Devices? anything??????
martin0285 said:
Have you tried every option in all the other "HELP BRICK" posts?? I don't really have time to search (and my nexus is working fine) but I know there has been plenty of threads like this before. Multiple options where tried, some successfully and some not. I would not give up unless it won't power on at all. Does ADB logcat work during a boot? Fastboot Devices? anything??????
Click to expand...
Click to collapse
No haven't tried those checking the Help Brick post I will see what I can find. No adb and not fastboot devices, just says waiting for device if I try anything.
Since you have unlocked the bootloader have you tried a complete reload?
fastboot: flash boot, flash recovery
recovery: wipe everything, reset, install latest CM.
Did you ever figure this out?

Update from 10.6.1.14.10 -> 10.26.1.18

So,
In an attempt to install CWM, I've got to update to 10.26.1.18 for the version I want to go to.
I've attempted to use the manual process to no avail
Download the image
Put it on SD card at root after unzipping ONLY ONCE.
File name is UL-K00C-US-20.26.1.18-user.zip
Yes, it's a US SKU tablet, it's currently running JOP40D.US_epad-10.6.1.14.10-20130801
The card is formatted with FAT32, it's a 2g MicroSD card (I've tried a 32g SDHC Card as well)
I've cleared out the CMClient and the DMClient apps
I've even attempted to download it directly from ASUS support to the tablet itself, extracting locally, etc. no dice.
I've attempted to cold boot numerous times, wiped once, but I never get the notification in the lower right hand corner that there is an available update.
TL;DR TF701 can't find files for manual update, I'm about ready to throw it out the window.
kzersatz said:
So,
In an attempt to install CWM, I've got to update to 10.26.1.18 for the version I want to go to.
I've attempted to use the manual process to no avail
Download the image
Put it on SD card at root after unzipping ONLY ONCE.
File name is UL-K00C-US-20.26.1.18-user.zip
Yes, it's a US SKU tablet, it's currently running JOP40D.US_epad-10.6.1.14.10-20130801
The card is formatted with FAT32, it's a 2g MicroSD card (I've tried a 32g SDHC Card as well)
I've cleared out the CMClient and the DMClient apps
I've even attempted to download it directly from ASUS support to the tablet itself, extracting locally, etc. no dice.
I've attempted to cold boot numerous times, wiped once, but I never get the notification in the lower right hand corner that there is an available update.
TL;DR TF701 can't find files for manual update, I'm about ready to throw it out the window.
Click to expand...
Click to collapse
You put it at location /sdcard/
You dont put it on the microSD afaik
I thought also there is an update in settings before you do it? I dont remember exactly.
YayYouFixedIt said:
You put it at location /sdcard/
You dont put it on the microSD afaik
Click to expand...
Click to collapse
I have a copy of it there too...
No dice.
Also, to add to it, I have the device unlocked.
kzersatz said:
I have a copy of it there too...
No dice.
Also, to add to it, I have the device unlocked.
Click to expand...
Click to collapse
That doesnt sound good. Id wait to see what sbdags has to say. Not sure what you can do at that stage.
YayYouFixedIt said:
That doesnt sound good. Id wait to see what sbdags has to say. Not sure what you can do at that stage.
Click to expand...
Click to collapse
If I've gotta drop on an older version of CWM to flash a newer version of an OS to jocky it all around, i'm not adverse to the foot work, it's all just annoying lol
If you have 10.1.6.14.10 on it then you have flashed a TF700 boot loader on it.
Game over in my opinion. Not sure how you can recover from that.......
Unless you have a TF700? In which case you are in the wrong forum....... And flashing the wrong firmware.....
sbdags said:
If you have 10.1.6.14.10 on it then you have flashed a TF700 boot loader on it.
Game over in my opinion. Not sure how you can recover from that.......
Unless you have a TF700? In which case you are in the wrong forum....... And flashing the wrong firmware.....
Click to expand...
Click to collapse
Ha... you... wow.
I'm going to go hide now
Let me go test one thing and I'll report back
kzersatz said:
Ha... you... wow.
I'm going to go hide now
Let me go test one thing and I'll report back
Click to expand...
Click to collapse
Yeaaa, lock this.
Stupidity reigns supreme.
TF700; wrong guide, wrong recoveries, I'm very lucky I didn't brick it.
Thanks guys!

Categories

Resources