Database Develop

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

:( Random Problem......Help, Please! :(

Right then,
Already searched on this one and not yet seen a solution to my problem. I own a T-mobile G1 and my phone crashes after it has booted up, or will not boot up properly: either the T-mobile G1 screen stays on for 5-6 seconds then I get a black screen, or it boots up then freezes with a black screen, or it won't switch on at all.
I currently have:
T-Mobile G1 with Root
2.22.19.26I radio installed
1.33.2005 "Death" SPL installed
Amon_RA's RA-v1.2.3 recovery installed
MghtyMax "What a feeling" 1.9.1 Hero ROM installed
fat32, ext3 and linux-swap on class 6 8Gb sdcard
I can get to recovery (sometimes.....it doesn't always get that far) and fastboot, so hopefully it's not bricked. I have already tried wiping (ALT+W) and formatting the ext2 (from the option in RA's recovery menu and also via console); removing all the partitions and starting afresh recreating them (after removing them of course), and as I can get to recovery (sometimes) I have tried flashing a different ROM (SENSEhero 1.3.3 unthemed) but still get the same issue.
I have flashed quite a few ROMs recently and not had any issues, so any help on this one would be most appreciated!

matthenry87 said:
Check your SD Card. My buddy had the same "black screen" problem and I discovered his SD card was slightly popped out. I clicked it back in and boom. problem solved. For him at least!
Click to expand...
Click to collapse
I'll give it a go..........

Seems like it is a problem with the sd card. Removed it and plugged it into my pc via a card reader and it couldn't recognise the card. Amazon here we come! Thanks for the help!

Give us a logcat from ddms.bat.

Binary100100 said:
Give us a logcat from ddms.bat.
Click to expand...
Click to collapse
he already solved it....

Not again......
B-man007 said:
he already solved it....
Click to expand...
Click to collapse
Okay,
It is still doing it and I'm not sure if it is the sdcard. Tried a different card I have at home and I still have the same problem.
I'm also getting extra coloured pixels appear on the T-Mobile G1 screen.
I can still get to bootloader and recovery (sometimes.....).
How do I pull a logcat?
MrZ

adb logcat
you can also run ddms.bat and get the log from there

misterzak said:
Okay,
It is still doing it and I'm not sure if it is the sdcard. Tried a different card I have at home and I still have the same problem.
I'm also getting extra coloured pixels appear on the T-Mobile G1 screen.
I can still get to bootloader and recovery (sometimes.....).
How do I pull a logcat?
MrZ
Click to expand...
Click to collapse
well trying to solve the problem by trying another sdcard is not a fix... since some roms do rely on the ext contents for things to work properly. what i suggest is having the 3nd card completely wiped and partitioned correctly..then move a rom onto the card and flash like u normally would.

Thanks for the info.
That was one of the first things I tried. I managed on Tuesday to install AOSP_ADP_1.6_r1.2_DRC92_rooted_base_v2.zip, and it worked for a short period of time, but it now crashes or doesn't boot up.
Getting worried now.......

misterzak said:
Thanks for the info.
That was one of the first things I tried. I managed on Tuesday to install AOSP_ADP_1.6_r1.2_DRC92_rooted_base_v2.zip, and it worked for a short period of time, but it now crashes or doesn't boot up.
Getting worried now.......
Click to expand...
Click to collapse
Something may be wrong with the phone itself
Try flashing the RC29 and seeing if the problem persists. if it does, then its probably a hardware problem. You can talk to tmobile or HTC about it and see what they say

B-man007 said:
Something may be wrong with the phone itself
Try flashing the RC29 and seeing if the problem persists. if it does, then its probably a hardware problem. You can talk to tmobile or HTC about it and see what they say
Click to expand...
Click to collapse
Thanks for that. I assume if they ask me to return it to them to reflash the original bootloader and recovery screens so that they cannot tell I've been "playing" with my phone...

Haha well once you flash the RC29 you wont have to because it will all be stock. If Tmo replaces phones for missing text messages, which is for sure a software problem (yes ive seen them do this), then they definitely will for this issue.

B-man007 said:
Haha well once you flash the RC29 you wont have to because it will all be stock. If Tmo replaces phones for missing text messages, which is for sure a software problem (yes ive seen them do this), then they definitely will for this issue.
Click to expand...
Click to collapse
If I flash RC29 (or RC7 for me) will this brick the phone as I currently have Death SPL. I'm sure I've read that somewhere on here?

Unrooted.......
I've now reverted back to RC7 (as I'm in the UK) and all seems okay....for now.
I will run it like this for a day to see if it still crashes or does anything funny. If it doesn't, I will re-root and start again!
Thanks for the help with this. I will update if it continues to crash.

Alright lets hope this fixed it lol
also it may be a little late but you should be fine flashing the RC7 as it replaces the SPL and radio

EVT Board.........
B-man007 said:
Alright lets hope this fixed it lol
also it may be a little late but you should be fine flashing the RC7 as it replaces the SPL and radio
Click to expand...
Click to collapse
Now this is interesting, RC7 was fine. Re-rooted the phone, fine. Flashed AOSP_ADP_1.6_r1.2_DRC92_rooted_base_v2.zip ROM, fine. Flashed Amon_RA's v1.2.3.img recovery, fine. This is where it gets fun, partitioned my card within the recovery to FAT32, ext2 and linux-swap, then rebooted into recovery. The phone crashed. So, I thought there must be an issue with the sdcard. Put in the stock 2Gb card with the RC7 DREAIMG.nbh file on and pressed camera+power to go back to RC7. It came up with an red code 00058002, then went back to the bootloader screen. It stated at the top that it was an EVT board. Searched all of the Dream Q&A section for EVT and absolutely nothing. Tried going into bootloader again and that screen started to warp and the graphics and pixels started to jumble up.
Any ideas?

wow.....it changed board types on you?
did you manage to flash cyan at all before that happened?
you should flash cyan and boot on it before flashing amonra's recovery.
you can then flash the recovery then partition the card and wipe just to be safe

B-man007 said:
wow.....it changed board types on you?
did you manage to flash cyan at all before that happened?
you should flash cyan and boot on it before flashing amonra's recovery.
you can then flash the recovery then partition the card and wipe just to be safe
Click to expand...
Click to collapse
I flashed the AOSP_ADP_1.6_r1.2_DRC92_rooted_base_v2 ROM and booted it up fully. Then using the Terminal Emulator within Dev Tools I flashed Amon_RA's recovery. All went well until I partitioned the sdcard. It won't boot up at all into the home screen or recovery, just bootloader, although it did this before when it first started crashing. I'm gonna leave it tonight and try again tomorrow.
Do you know anyone else on here who has any idea on this one? Seems like I'm the first!

This is probably an issue with the recovery itself...though ive never read about anything like your having.
ill bump this thread and see if anyone can help...maybe david can (ill tell him to get on here)

why dont you give a differant recovery image and dont try to partition just try with a fat32 sdcard on a cyan rom or something see what happens with that

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?

[Q] Stuck at Clockwork Recovery screen? HELP!??!

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!

[HELP THREAD] HTC One M8S - Back to Stock - HOWTO

HOW TO get your HTC One M8S back to Factory / stock.
Attention 1: This is NOT for the regular HTC One M8.
Attention 2: This is for the HTC One M8S also known as the M8_QL_UL
(The One M8S does not have a separate subforum on XDA.)
Hi everyone! I saw that many people who have a HTC One M8S have problems with restoring the stock HTC RUU. It is a little bit difficult. So here I'll supply you again with steps that worked for me.
Most of this is a copy from a post I made earlier. But I saw that many of you still have some problems. So here is a dedicated thread.
I have used this method multiple times to restore my phone back to factory defaults. I hope it works for you too!
Warning. You will lose your settings. Everything will be reset to the defaults.
Read these important notes before you begin!
When you need fastboot: only HTC's own fastboot program will work. You will use fastboot, for example, when you want to flash a custom recovery.
Other fastboot applications will not work correctly in my experience! So be sure you use HTC's.
If you need it: HTC will send you a link when you unlock your bootloader. But you can also find fastboot via the same page as where you can find the RUUs.... see below.
Do you have an SDCard ready? You must have one to get this to work and it must be big enough. ADB sideload will NOT work!
Is your phone relocked? It must be! If not, relock it, then come back.
Most of the problems happen because people read too fast. This stuff just takes a long time.. so don't do it if you are in a hurry. And do read carefully.
Are you ready? Ok! Here we go.
Download the RUU zip you want to use. I have used ...HTC_Europe_1.16... BUT later I found this did not allow the newest OTA update (as of august 30th, 2015). Maybe I will test 1.11 some day later.
However, I think that 1.11 is the right version. Not sure where to download the RUU or fastboot? Click the button.
For me, I downloaded the RUU zip via the generous hosting by @El-Conkistador. You can find it via his post here. On his page there is a directory called Firmware (Expert). In there is a directory called Firmware Crypted (Original HTC). In that directory are multiple directories containing RUUs. Choose one for your device, download it, then come back here.
Open your sdcard. It must be fat32 or exFAT formatted.
Copy the RUU zip file onto the root of the sdcard. Do NOT extract it. Just copy it.
You must now rename it to: 0PKVIMG.zip. The first character is the number 0 (zero), not the letter O!
If you know how to do this, take the md5sum from the RUU zip on your computer, and 0PKVIMG.zip on your SDcard. They must be the same! If not, there can be a problem with your SDCard.
Safely unload and remove the SDCard from your computer.
Power off your phone.
Are you sure you want to continue? Then insert the SDCard into the phone..
Take a deep breath..
Boot the phone to the bootloader: hold Volume Down. Press the power button. Release both buttons when you are inside the bootloader.
When you are in the bootloader, press power once to enter fastboot mode.
The restoration process should will now start. Confirm on the screen when it's asked. Then wait patiently, it takes a long time!
Nice detail: there is a small sidebar at the top right side of the screen that will show you progress. Sometimes it will go back to 0; it will fill up more than once.
In case of failure
In my case it failed the first time. Probably because a sector on my SDCard was faulty. I found out by verifying the md5sum of the file on the sdcard, it was not the same as the RUU zip on my computer, but it has to be.
To fix it, I copied the RUU zip to the sdcard for the second time, *then* deleted 0PKVIMG.img, and *then* renamed the RUU zip to 0PKVIMG.zip. Then I looked at the md5sum again. Now it was the same as on my computer... and then the restoration worked.
Still need help?
If you have questions, ask and wait patiently. I am not on this page 24/7, no one is. Just don't panic. Don't demand help. Maybe read this stuff again and see if you made a mistake somewhere.
It is logical that you are annoyed if this stuff doesn't go how you want, sure, it is not the easiest thing to do. I have tried to make it easier, but again, if it still fails, just ask your questions and wait patiently. Treat others like how you want to be treated yourself. :angel:
Good luck!
-voidzero.

(reserved)

voidzero said:
(reserved)
Click to expand...
Click to collapse
Exactly what RUU do you need and when i click hboot in the bootloader it fails finding the 0PKVIMG.zip. so idk what to do

Alex-M8 said:
Exactly what RUU do you need and when i click hboot in the bootloader it fails finding the 0PKVIMG.zip. so idk what to do
Click to expand...
Click to collapse
The exact filename of the RUU I used:
Code:
0PKVIM[email protected]50311_15.00_016_F_release_430101_signed.zip
Do you see a few green lines that say "searching for 0pkvimg.zip" when you go to hboot? They disappear pretty quickly.

voidzero said:
The exact filename of the RUU I used:
Code:
0PKVIM[email protected]50311_15.00_016_F_release_430101_signed.zip
Do you see a few green lines that say "searching for 0pkvimg.zip" when you go to hboot? They disappear pretty quickly.
Click to expand...
Click to collapse
Yeah i saw the green lines but nothing happend after they disappear

Alex-M8 said:
Yeah i saw the green lines but nothing happend after they disappear
Click to expand...
Click to collapse
Is it a fat32 or exfat sdcard? Is the md5sum for 0pkvimg.zip correct? It should be 70eece34781f0b1449f98f03e842f249

voidzero said:
Is it a fat32 or exfat sdcard? Is the md5sum for 0pkvimg.zip correct? It should be 70eece34781f0b1449f98f03e842f249
Click to expand...
Click to collapse
i checked and it is fat32 and i still don't get where the md5sum is located and where i should put it .-.

the md5sum is a long string of characters called a checksum. It scans a file and calculates what number it should get. Other types of checksums are SHA-1, SHA-256, RIPE-MD160 and so on.
MD5 is fairly lightweight so that's why we usually choose md5 for files.
md5sum itself is a program that you can run from the command line. If you use linux, it should be on your computer already, so just do 'md5sum 0pkvimg.zip'. On windows, well, you need md5sum.exe and run that from a command line. But I have not used Windows in so many years that I don't know where to find md5sum.exe. I'm sure you can find it easily... I would google for this, but you can do that too so I'll leave that part up to you.
So: you don't put the md5sum anywhere.. you calculate an md5sum and compare it with the number I gave you previously. Hope this makes sense, keep asking if you need more help.

Hi guys,
Im new to all this I just want to ask for little help here my m8s has unlocked bootloader and modified (unofficial) software (says in bootloader)
Im running 5.0.2 soft ver
Soft number 1.16.401.10
Custom recovery TWRP
Phone is rooted but i need to send it back to htc as its dropping calls randomly within 25secs. All i need is the right ruu so its stock again and says relocked (i know how to relock) official soft and that OTAs would work.
Also do i leave this custom recovery there or before the ruu will i put in the stock one, relock the BL and then the ruu?
Any help is much appreciated.
Sent from my HTC One M8s using XDA Free mobile app

Just relock. The Ruu does the rest! I used 1.11, the exact filename is in my OP. If you have a vendor phone I'm not sure but I think you can still use the same RUU as I have; if not, you will be notified from hboot. Does that answer your question?

Yes thank you.
Sent from my HTC One M8s using XDA Free mobile app

Tried on windows twice then got a blue screen (on the pc) did the 1.11 on my macbook and phone is now back to official and relocked!
I owe you a pint of beer sir. Thank you!
Sent from my HTC One M8s using XDA Free mobile app

Great! Glad to hear.

Cyanogenmod is still in the works. I have finally gotten a preliminary version to boot, so to those of you who are interested, head over to the CyanogenMod 12 on M8s thread...
HTC One M8S: Cyanogenmod 12 Discussion

hi all,
I give up, downloaded three zips from this link:
http://forum.xda-developers.com/htc-one-m8/help/make-custom-recovery-htc-one-m8s-t3114245
1.03
1.11
1.11 - combined signed
and every time I get error "no image or image wrong....no gift file....loading image 0Pkvidiag.zip - No image! loading 0PKVIDIAG.nbh...no image or wrong image"
...inside the zip file there is no 0PKVIMG.img file so dont realy know what to rename . . .
...yes checked md5 sum and they are OK
...sd card is fat32 (tried copying zip file from two different laptops , no difference)
...Custom recovery TWRP
this is m8s european version which was rooted , fastboot shows now RELOCKED and this images just dont work ,
this phone is giving all sort of issues, no custom roms with updates, SIM_Card error sometimes 10+ times a day causing call disconnections and reboots, cant update to lates htc soft as on custom rom it just dont work.....
what I am doing wrong here? probably something stupid easy :laugh: help please
Thanks in advance !

new-noob said:
what I am doing wrong here? probably something stupid easy :laugh: help please
Click to expand...
Click to collapse
Hiya. Ugh I get how frustrating this can be!! But you're close, so we'll get you sorted out. FYI on saturday and sunday I'm not around much (family comes first ), so replies might take me a while... but we'll figure it out.
You need this exact file:
Code:
0PKVIM[email protected]50311_15.00_016_F_release_430101_signed.zip
Copy that to the sdcard and rename it to 0PVKIMG.zip, don't extract it just rename it. The md5sum should be:
Code:
70eece34781f0b1449f98f03e842f249
If that won't work, we need to figure out why. That comes next. :good:

voidzero said:
Hiya. Ugh I get how frustrating this can be!! But you're close, so we'll get you sorted out. FYI on saturday and sunday I'm not around much (family comes first ), so replies might take me a while... but we'll figure it out.
You need this exact file:
Code:
0PKVIM[email protected]50311_15.00_016_F_release_430101_signed.zip
Copy that to the sdcard and rename it to 0PVKIMG.zip, don't extract it just rename it. The md5sum should be:
Code:
70eece34781f0b1449f98f03e842f249
If that won't work, we need to figure out why. That comes next. :good:
Click to expand...
Click to collapse
HI voidzero and thanks for taking the time and replaying!
I ended up installing Android Pandora 1.2 and ...waiting on feedback re: SIM errors, hopeful they are gone with new ROM,
I'll post quick update tomorrow.
Thanks again and enjoy ur weekend !

new-noob said:
HI voidzero and thanks for taking the time and replaying!
I ended up installing Android Pandora 1.2 and ...waiting on feedback re: SIM errors, hopeful they are gone with new ROM,
I'll post quick update tomorrow.
Thanks again and enjoy ur weekend !
Click to expand...
Click to collapse
You should use Cyanogenmod, not Pandora. Pandora is old, is not updated, and contains a very problematic security issue with libstagefright. Use cyanogenmod for your own good!

voidzero said:
You should use Cyanogenmod, not Pandora. Pandora is old, is not updated, and contains a very problematic security issue with libstagefright. Use cyanogenmod for your own good!
Click to expand...
Click to collapse
hey, yeap, pandora gives same SIM card error!
Thanks for advise, I will definitely try Cyanogenmmod, think this is the link : http://forum.xda-developers.com/htc-one-m8/general/htc-m8s-cyanogenmod-t3142668
?
Thank you!

hello.
i need help. my htc m8s is relock, my sd card is format fat 32, md5sum match, but still not recognize when i restart in fastboot.