Related
Hi, i've been using LeeDroid for a few months now and all has been well, however yesterday my Desire turned itself off and now won't come back on. Each time i try and power it up it freezes at the Alpharev S-Off screen. I went into the menu's with volume down + power, but i can't get into my recovery - it takes me to the same frozen screen as does trying to reboot etc. And i don't think it's being recognized by usb either. So i really don't know what to do now.. is my phone bricked? I was a complete noob before rooting and flashing a custom rom before, so now that i've hit a problem i'm clueless all over again. Any help would be greatly appreciated
can you use fastboot? If so just flash a new recovery and all should be fine... chill out it can be fixed
What would i need for that? That's going into new territory
j3nni said:
What would i need for that? That's going into new territory
Click to expand...
Click to collapse
Can you access recovery? If no can you access bootloader (vol down + power on)
I can get onto the menu with the options 'fastboot, recovery, clear storage and simlock' if that's what you mean? The recovery option takes me back to my frozen alpharev screen, but i can get onto fastboot and after reading around i can get my pc to recognize it from fastboot usb from my pc using cmd.. Am i going the right direction at all? Eek. What i don't get now is the recovery image i'm supposed to use
j3nni said:
I can get onto the menu with the options 'fastboot, recovery, clear storage and simlock' if that's what you mean? The recovery option takes me back to my frozen alpharev screen, but i can get onto fastboot and after reading around i can get my pc to recognize it from fastboot usb from my pc using cmd.. Am i going the right direction at all? Eek. What i don't get now is the recovery image i'm supposed to use
Click to expand...
Click to collapse
Use amon_RA ... Download and flash onto ur phone and ur phone should be fixed
Plenty of guides around man, good way of learning fastboot
to use fastboot you need to download several things. Instead of using fastboot with cmd, I'd just recommend using fastboot commander, which does the job for you. In order to use that however, you will need the adb drivers, and Java SDK.
Once you've got all that, simply boot into fastboot, run "fastboot commander.exe", go into the "misc" tab, wipe Recovery, system, cache, boot, and userdata. Once you've done that download recovery, navigate to the "Hboot, radio & Rec" tab on fastboot commander, select recovery, find the recovery.img you just downloaded, and flash it. Once you've done that just boot into recovery and install any ROM you want.
Thanks for the replies guys. I did what you said to do (using fastboot commander), and when trying to boot into recovery to install my ROM it froze again at the alpharev screen. I'm stuck again now. When the files show up as you turn on into fastboot, i'm getting this..
SD Checking...
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nhh]
No Image or Wrong Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99IMG.nhh]
No Image or Wrong Image!it's saying my pb****.img files arn't found
which i gather can be normal. Other than that i'm stumped again
j3nni said:
Thanks for the replies guys. I did what you said to do (using fastboot commander), and when trying to boot into recovery to install my ROM it froze again at the alpharev screen. I'm stuck again now. When the files show up as you turn on into fastboot, i'm getting this..
SD Checking...
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nhh]
No Image or Wrong Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99IMG.nhh]
No Image or Wrong Image!it's saying my pb****.img files arn't found
which i gather can be normal. Other than that i'm stumped again
Click to expand...
Click to collapse
try do a full wipe of everything like I've mentioned before and then a different HBOOT
Okiedoke, how do i use a different hboot? And where do i find one from? At the moment i believe it's 0.93
j3nni said:
Okiedoke, how do i use a different hboot? And where do i find one from? At the moment i believe it's 0.93
Click to expand...
Click to collapse
www.alpharev.nl download a HBOOT and flash it through fastboot. Just make sure to check MD5 (you need a MD5 utility AFAIK)
I'm not sure which one is the right one for my ROM, i'm using LeeDroid.. Sorry for all the questions!
j3nni said:
I'm not sure which one is the right one for my ROM, i'm using LeeDroid.. Sorry for all the questions!
Click to expand...
Click to collapse
For any sense UI ROMs you would use the Sense HBOOT, remember to nandroid backup before you do so! because you might find that you get a bootloop after flashing the HBOOT.
And don't worry about asking questions! it's what we're all here for.
By the way if you don't know what different HBOOTs do: they change the partition sizes for /system /cache and /data. So by using a different HBOOT instead of the stock one you may get more storage for apps etc. if you choose one with a larger /data partition.... if that makes sense
Ok the sense one it is =)
Ah i see! Thanks for explaining cos underneath the nerd in me would have been wondering what it did lol.
Not sure how to get a nandroid done when i can't get into recovery though
I still havn't got anywhere with my problem, if anyone could advise me further i'd really appreciate it, as this is really stressing me out now.
The only screen i can still ever see is a frozen alpharev screen, and i still can't enter recovery. I've cleared everything using fastboot commander and flashed a new recovery which did nothing. Then i took the next advice and flashed a new hboot. The hboot has changed on my hboot menu (vol down + power) but still goes to the frozen alpharev screen when i try to go to recovery or turn the phone on. I then flashed a LeeDroid rom, which came up with an error at the end of it..
"sending 'zip' (173060 KB)... OKAY [ 23.469s]
writing 'zip'... FAILED (remote: not allowed)"
And that's as far as i've got.
Reading further i've been trying to work out how to flash a stock ruu to see if that works. However my phone was a branded Orange UK phone before so there is no ruu for that. So my question is, bearing in mind i can't get into the phone at all, how can i go about downgrading the hboot and installing a htc stock ruu. Can anyone point me to the right files i would need. I really don't know what i'm doing and i think the amount of searching i've been doing is just confusing me further
j3nni said:
I still havn't got anywhere with my problem, if anyone could advise me further i'd really appreciate it, as this is really stressing me out now.
The only screen i can still ever see is a frozen alpharev screen, and i still can't enter recovery. I've cleared everything using fastboot commander and flashed a new recovery which did nothing. Then i took the next advice and flashed a new hboot. The hboot has changed on my hboot menu (vol down + power) but still goes to the frozen alpharev screen when i try to go to recovery or turn the phone on. I then flashed a LeeDroid rom, which came up with an error at the end of it..
"sending 'zip' (173060 KB)... OKAY [ 23.469s]
writing 'zip'... FAILED (remote: not allowed)"
And that's as far as i've got.
Reading further i've been trying to work out how to flash a stock ruu to see if that works. However my phone was a branded Orange UK phone before so there is no ruu for that. So my question is, bearing in mind i can't get into the phone at all, how can i go about downgrading the hboot and installing a htc stock ruu. Can anyone point me to the right files i would need. I really don't know what i'm doing and i think the amount of searching i've been doing is just confusing me further
Click to expand...
Click to collapse
Hi.
As I can see the only way to restore is using a RUU to go back to stock then root and S-Off the phone again.
First: Preparation.
1. If you have a custom HBOOT (e.g.: 6.93.0001) you need first to flash the HBOOT Downgrader (found on alpharev site), then flash the RUU.
2. You will gonna need a Gold Card if your phone was branded.
Second: Starting
1. Make your Gold Card using someone's else phone (it has to be running Android) - the Gold Card is unique per SD Card, not per phone.
2. Use this tool to make the Gold Card: HERE
3. Guide how to make a Gold Card in Linux: HERE
4. get the latest RUU WWE 2.29.405.5. Extract the PB99IMG.zip file from the RUU: here it is how: http://forum.xda-developers.com/showthread.php?t=880268 -2nd post.
5. Reboot in bootloader (Volume-Down + Power)
7. Select fastboot
8. Flash the HBOOT Downgrader (don't forget to check the MD5 of the file you have downloaded from alpharev)
9. Extract the PB99IMG.zip and put it on root of SD Card.
10. Reboot in bootloader (scroll to REBOOT and select)
11. It will automatically load the img and ask you if you want to install
12. Check Yes and follow onscreen progress.
13. Wait untill it finnishes
14. I think it will reboot itself, if not scroll down to the Reboot obtion and press Power button to select.
IMPORTANT WARNING!!!
droidzone said:
Whatever you do, DO NOT turn off the device manually unless the software tells you to. If something goes wrong, dont switch off phone. Keep the phone on while trying a solution. Newer RUUs dont usually wreck a phone, and with a goldcard, you can always recover. But, the flash SHOULD NOT be interrupted by switching off or disconnecting the cable.
Always start with a battery with >50% power (full recommended).
Click to expand...
Click to collapse
Or if you want to go to stock and it is an unbranded phone you can just run ur ruu when the phone is in fastboot
Sent from my HTC Desire using XDA App
Think i may be the happiest girl in the world today lol i finally got it all fixed. I had a bit of trouble making the goldcard as at first my sd card kept saying it needed to be reformatted after, but after formatting it with SD Formatter program rather than Vista's own, it worked. All the rest went without a hitch. Now just gotta root, s-off and grab my new ROM and this past week can all get forgotten about =)
Thankyou so much to everyone that helped!
Incase anyone does read this far, is the procedure still the same as when i first used it back in April.. from here? http://forum.xda-developers.com/showthread.php?t=1016084
It is still the same.
If you like sense -
http://forum.xda-developers.com/showthread.php?t=1054435
░█░ [ROM][28/06] ✰.Reflex S v2.1.7 Gingerbread 2.3.3· ░█░ · |SenseGingerB 2.1+3.0|
You might like it...
installed CM7 port 7.2 yesterday, and it seemed to all go fine, but whenever i need to reboot the phone, i get loads of FC's, the calendar doesn't work, my FB and twitter accounts don't get any notifications sync'd, and their accounts are actually totally removed from the sync and accounts section upon every reboot.
overall, considering this is supposed to be the most "stable" of the custom roms, i'd rather just go back to the stock, at least it works, even if i have less space and it eats up battery a bit quicker...at the moment, the phone is pretty useless :s
go to http://forum.xda-developers.com/showthread.php?t=1074445, choose the stock rom for your device and flash it.
it's that simple? awesome! thanks so much
::EDIT::
not working
it keeps bringing up an error when trying to install the rom :s
also tried to install using the rom.zip by choosing install from zip in recovery menu...no joy
::EDIT::
trying a completely fresh install of CM7, wipe everything, format and repartition Sd card, totally start from scratch...as this is the only thing i seem to be able to do at this point....none of the RRU's are installing....wish I hadn't tried this CM7 now :s
My cm7 is completely stable and much more responsive and less bloated than any stock rom
Dunno where your problems are coming from but I don't have any.
I'd recommend doing a full wipe and reflash of CM7. Some bugs appear at first.
Make sure you wipe dalvik, cache and full wipe before flashing.
ok guys, just completely restarted everything from scratch, wiped everything, reformated everything, cleared every possible option.
this time i installed CM7, then the google pack, then DATA2SD (before anything i partitioned the sd card 1GB/256MB)...
seems to be working a bit better...my facebook and twitter accounts are still signed in and show under the sync and accounts settings etc...
i haven't got all those FC's at boot so far....but then i didn't initially yesterday either....so we'll see how it plays out tomorrow :s
however the calendar still doesn't work well, and infact if i open it, goto menu then select calendars, i still get FC on that app :s
maybe i should just get another calendar app?
i think alot of the preview errors might have been due to the fact that i had just manually chose the "move to sd" option for all my apps instead of installing data2sd (which tricks the phone into thinking the 1gb partition on the sd card is the internal memory?)
so fingers crossed it will hold up a bit better now. like i said, i actually can't go back from CM7 now, since none of the RUU's will install. but so far so good, hopefully it will last more than a day this time :s
Gloris said:
installed CM7 port 7.2 yesterday, and it seemed to all go fine, but whenever i need to reboot the phone, i get loads of FC's, the calendar doesn't work, my FB and twitter accounts don't get any notifications sync'd, and their accounts are actually totally removed from the sync and accounts section upon every reboot.
overall, considering this is supposed to be the most "stable" of the custom roms, i'd rather just go back to the stock, at least it works, even if i have less space and it eats up battery a bit quicker...at the moment, the phone is pretty useless :s
Click to expand...
Click to collapse
Give it one more shot but in CWM do this:
Factory reset
Then Mounts/ Format System
Then Advanced/Wipe Dalvik Cache
Then install zip and gapps zip.
See if that clears up any ghosts in the machine. That behaviour shouldn't happen Gloris. I can assure you I've been running the release 1218 since well...1218 and it's been a pleasure.
Same as d33ps1x this is a great rom.
Everything's working fine with no force closing
If your problems continue follow d33ps1x instructions carefully and all should be fine.
Are you using the latest nightly or RC version?
using the nightly version....was all going ok, but now, not only is the calendar still FCing, but i can no longer download ANYTHING from the market...i just get error 492....
I wish i'd never tried this damned CM7, totadl waste of time.
Yes, i've got 1GB of "internal storage", but what's the use if i can't add any more apps???
anyone got any more suggestions for how to go back to stock?
I've tried the RUU, and tried it with goldcard via the .exe installed and via recovery (install from .zip), both with no luck.
I wish i could just go back to stock, these custom roms are a total waste of time
Gloris said:
using the nightly version....was all going ok, but now, not only is the calendar still FCing, but i can no longer download ANYTHING from the market...i just get error 492....
I wish i'd never tried this damned CM7, totadl waste of time.
Yes, i've got 1GB of "internal storage", but what's the use if i can't add any more apps???
anyone got any more suggestions for how to go back to stock?
I've tried the RUU, and tried it with goldcard via the .exe installed and via recovery (install from .zip), both with no luck.
I wish i could just go back to stock, these custom roms are a total waste of time
Click to expand...
Click to collapse
this is the reason why you should have made a nand backup of your rom with cwm BEFORE installing a custom rom.
Gloris said:
using the nightly version....was all going ok, but now, not only is the calendar still FCing, but i can no longer download ANYTHING from the market...i just get error 492....
I wish i'd never tried this damned CM7, totadl waste of time.
Yes, i've got 1GB of "internal storage", but what's the use if i can't add any more apps???
anyone got any more suggestions for how to go back to stock?
I've tried the RUU, and tried it with goldcard via the .exe installed and via recovery (install from .zip), both with no luck.
I wish i could just go back to stock, these custom roms are a total waste of time
Click to expand...
Click to collapse
Have you got the unlocked bootloader if so extract the ruu an flash the boot and system images via fastboot
Sent from my HTC Wildfire S using xda premium
eoghan2t7 said:
Have you got the unlocked bootloader if so extract the ruu an flash the boot and system images via fastboot
Sent from my HTC Wildfire S using xda premium
Click to expand...
Click to collapse
can you elaborate on that and give the exact commands
Gloris said:
can you elaborate on that and give the exact commands
Click to expand...
Click to collapse
Downloaded my PG76IMG.zip version.
Unzip it with 7zzip.
put the boot.img and system.img in the same directory as fastboot
Start your phone with vol down/power after removing and replacing the battery
Choose fastboot
Connect usb cable
issue fastboot commands:
fastboot flash boot boot.img
fastboot flash system system.img
dont forget fastboot -w to wipe the data of the previous rom
d33ps1x said:
Downloaded my PG76IMG.zip version.
Unzip it with 7zzip.
put the boot.img and system.img in the same directory as fastboot
Start your phone with vol down/power after removing and replacing the battery
Choose fastboot
Connect usb cable
issue fastboot commands:
fastboot flash boot boot.img
fastboot flash system system.img
Click to expand...
Click to collapse
I can confirm this working.
if you flash recovery, too from the zip, you can return to stock from cwm.
then apply "fastboot oem lock" and the bootloader will be locked again.
This can be used as a way back to warranty maybe, since then everything is stock again
d33ps1x said:
Downloaded my PG76IMG.zip version.
Unzip it with 7zzip.
put the boot.img and system.img in the same directory as fastboot
Start your phone with vol down/power after removing and replacing the battery
Choose fastboot
Connect usb cable
issue fastboot commands:
fastboot flash boot boot.img
fastboot flash system system.img
Click to expand...
Click to collapse
thanks, do you have the link?
eoghan2t7 said:
dont forget fastboot -w to wipe the data of the previous rom
Click to expand...
Click to collapse
fastboot -w is not allowed.
>fastboot -w
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.004s
Click to expand...
Click to collapse
also, the only RUU i have in rom.zip format is the gingerbread 2.3.5 update....the others are all .exe only...how do i extract those? as i'm not sure the zip i have will work as it's 151Mb (i think the phone only has a genuine 150Mb total internal storage?)
for extracting from ruu exe:
- clear temp folder on windows
- run ruu.exe until first dialog
- go to temp files
- search in the folders for a rom.zip
- extract
- flash
this method is definitely not working
tried flashing the using fastboot, and not my phone won't even boot, it just starts up in recovery mode (it's actually lucky the recovery mode is there or else i'd have a definite brick on my hands).....for those that are wanting to back to stock, DO NOT TRY THIS....NOT WORKING!
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.
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.
I can't wipe my phone. So far I've tried:
Factory reset from Settings menu
Hard reset from recovery mode
fastboot -w
Flashing latest version of Yakju from Google
Locking and unlocking bootloader
Wiping from TWRP
Formatting userdata
In addition, I've tried uninstalling apps and removing files via adb shell. In both cases, the apps/files would return on reboot. (And the phone will reboot spontaneously when booted normally, although uninstalling some apps will make it take longer.)
Some background: I forgot to plug in my phone Friday night, and when I checked on it Saturday evening, it was dead. I plugged it into the wall charger, but it wouldn't charge. I poked around the charger port a bit, and got it working again. At 1/4 charge, I tried booting it, only to find that when doing a normal boot, it would stall at the Google start-up screen, while a recovery boot would show the dead android image with no text.
I had some more trouble getting it to charge, and ultimately damaged the USB port. (I got it replaced earlier today (Monday).) To fix the booting problem, I downloaded the latest yakju image from Google and tried flashing it. Not realizing that it would take 25 minutes to write system, I pulled the battery before that point. In spite of this, I was now able to boot the phone, even if it could no longer charge.
Today I got the USB port replaced, but found that the phone would crash every minute or so. I suspect that this is symptomatic of the larger problem of the phone not wanting to change from how it was Saturday morning when it died. No settings changes seem to stick. Every time I start up, I get the same SMS notification from Friday night. Deleted files are restored, and even my attempts to replace the recovery img with TWRP failed. (I managed to load it with fastboot boot, but it didn't do me much good.)
I've also run it through a successful flash of yakju, once I realized it would take half an hour to run. So far the only thing I can think of that I haven't tried is ODIN!
I have three sets of logs from logcat running up until the time of a crash, and the output of adb bugreport, if those are helpful.
Does anyone have any other suggestions?
I've attached the logs.
I've poked around a bit more, trying to get things working, or failing that, not working in a different manner. I started it up TWRP and ran a few tests. I uploaded the zipped image files to /sdcard, downloaded them again, and verified that result was identical. I used dd to copy the recovery partition to a file, grabbed it from the phone, and tried to use dd to copy TWRP over top. dd seemed to think it was successful, but grabbing the partition again, I get the same contents as before.
I'd assume it's something like the flash memory is never actually flushing its cache, so none of the changes I make get committed. I can run 'sync', and it will pause briefly if there was recent activity, but if I write data to a partition, unmount then remount it, the change is gone. If this is the case, I have no idea how I'd go about fixing it - the problem is sufficiently low level that the OS doesn't seem to be aware of it. If there are any tools available to test this, could you let me know?
At this point, I'm considering cutting my losses and getting a new phone.
Have you tried
fastboot erase boot
Fastboot erase system
Etc etc with userdata and cache also?
Might not work but worth a try.
G-Nexus Sent
ifly4vamerica said:
Have you tried
fastboot erase boot
Fastboot erase system
Etc etc with userdata and cache also?
Might not work but worth a try.
G-Nexus Sent
Click to expand...
Click to collapse
"userdata"
Sent from my Nexus
Yeah userdata! Thanks man.
G-Nexus Sent
alfedenzo said:
I can't wipe my phone. So far I've tried:
Factory reset from Settings menu
Hard reset from recovery mode
fastboot -w
Flashing latest version of Yakju from Google
Locking and unlocking bootloader
Wiping from TWRP
Formatting userdata
In addition, I've tried uninstalling apps and removing files via adb shell. In both cases, the apps/files would return on reboot. (And the phone will reboot spontaneously when booted normally, although uninstalling some apps will make it take longer.)
Some background: I forgot to plug in my phone Friday night, and when I checked on it Saturday evening, it was dead. I plugged it into the wall charger, but it wouldn't charge. I poked around the charger port a bit, and got it working again. At 1/4 charge, I tried booting it, only to find that when doing a normal boot, it would stall at the Google start-up screen, while a recovery boot would show the dead android image with no text.
I had some more trouble getting it to charge, and ultimately damaged the USB port. (I got it replaced earlier today (Monday).) To fix the booting problem, I downloaded the latest yakju image from Google and tried flashing it. Not realizing that it would take 25 minutes to write system, I pulled the battery before that point. In spite of this, I was now able to boot the phone, even if it could no longer charge.
Today I got the USB port replaced, but found that the phone would crash every minute or so. I suspect that this is symptomatic of the larger problem of the phone not wanting to change from how it was Saturday morning when it died. No settings changes seem to stick. Every time I start up, I get the same SMS notification from Friday night. Deleted files are restored, and even my attempts to replace the recovery img with TWRP failed. (I managed to load it with fastboot boot, but it didn't do me much good.)
I've also run it through a successful flash of yakju, once I realized it would take half an hour to run. So far the only thing I can think of that I haven't tried is ODIN!
I have three sets of logs from logcat running up until the time of a crash, and the output of adb bugreport, if those are helpful.
Does anyone have any other suggestions?
Click to expand...
Click to collapse
i have the exact same issue.. i cant wipe anything, after rebooting everything comes back to the phone, even if the flash or odin success, the same old files and OS come back again and nothing changes.
and as in your case, system take like 30 min to write, or even more.
i've tried fastboot erase userdata, fastboot erase system, etc, odin, format partitions from adb, toolkits, etc everything you can think of, and nothing works.
please, post if you fix your phone, because mine has been dead for a month atleast, id like to fix it but i dont know how.
ifly4vamerica said:
Have you tried
fastboot erase boot
Fastboot erase system
Etc etc with userdata and cache also?
Might not work but worth a try.
G-Nexus Sent
Click to expand...
Click to collapse
Sorry I didn't see this earlier. I ran the commands just now:
Code:
$ ./fastboot devices; ./fastboot erase boot; ./fastboot erase system; ./fastboot erase userdata; ./fastboot erase cache 130 ↵
016B75D71500B013 fastboot
erasing 'boot'...
OKAY [ 0.006s]
finished. total time: 0.006s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.007s]
finished. total time: 0.007s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.032s]
finished. total time: 0.032s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.881s]
finished. total time: 1.882s
Then it just boots up into the same old. (I'd tried at least some of those earlier, but I couldn't remembe which ones.)
This happened on the incredible to one of my rom users. Emmc or hardware related most likely. Either way there's not much hope to fix it if the usual methods don't work.
Sent from my Galaxy Nexus using Tapatalk 2
can't wipe & phone powers down right after boot
Ok it looks like I have the same problem as alfadenzo, except when my Nexus finishes booting, I get a buzz, a red exclamation point in the battery icon, and a popup saying "battery is not charged, please plug in charger", and powers down.
I've flashed 3 or 4 different stock firmares via Odin.
I've flashed complete sytem img's via fastboot, first wiping everthing.
Despite all this, the same splash screen loads. I think its a from CM7
I've flashed cwm by itself via fastboot , but it doesnt stick. Instead I get the "exclamation point android" , and then the stock recovery which I cant do anything with.
I have *3* whole smacking batteries that I've used, allong with two seperate usb cables. One that came with the phone, and on that came with a different Nexus.
Is this a kernel or bootloader issue? Im all out of the options that I know of
Galaxay Nexus I505
Tuna
variant - toro
bootloader - primekk15
baseband I515 EK02 CDMA
carrier - none
Unlocked
Hi,
I am having the same issue. I tried everything. The recovery mode shows that partitions and files are erased/deleted. However, on next boot all comes live ! and my phone boots. but restarts within a few seconds!
When trying to flash using ODIN, the "system" update fails!
Anyone to help?
Hi, I'm having the same problem.
Have you found the solution??
I'm trying to
- Flash ROM from fastboot
- Flash TWRP from fastboot
- Erase partition from fastboot
- Go to recovery and delete all data in /sdcard using adb
- Trying to delete 1 widget from home screen and reboot
- Try to restore stock image using Odin, Fail in system.img
Nothing happened. My gnex boot like usual to the old home screen and nothing changed.
Then it reboot by itself.
Any ideas?
Same problems with me as I reported earlier! Some are saying that the internal memory has gone readonly and its permanent!
Do you think you can contact Samsung service for a solution? I have thought of so, but need to bring out some time for that.
rakun123 said:
Hi, I'm having the same problem.
Have you found the solution??
I'm trying to
- Flash ROM from fastboot
- Flash TWRP from fastboot
- Erase partition from fastboot
- Go to recovery and delete all data in /sdcard using adb
- Trying to delete 1 widget from home screen and reboot
- Try to restore stock image using Odin, Fail in system.img
Nothing happened. My gnex boot like usual to the old home screen and nothing changed.
Then it reboot by itself.
Any ideas?
Click to expand...
Click to collapse
sudiptochoudhury said:
Same problems with me as I reported earlier! Some are saying that the internal memory has gone readonly and its permanent!
Do you think you can contact Samsung service for a solution? I have thought of so, but need to bring out some time for that.
Click to expand...
Click to collapse
I haven't contact samsung service center yet. This is my old phone, it's already out of warranty so it might be costly.
I thought read only mode should give you an error message at least.
In this case, I'm feeling like using Deep Freeze but for Android
Looks like my gnex chip have emmc brickbug. I cannot check anymore using brickbug app checker because it always crashed after booting. But the symptoms is the same.
Still haven't found a way to fix it
Indeed sounds like a fried emmc. Sorry guys.
Sent from my Galaxy Nexus using XDA Free mobile app
On the same boat as you guys !
Same Scenario here ! :silly: ..... i got a GT-9250 brand new in box , was pulled out only once to try it out and it's in the EXACT same condition as mentioned by previous posters ! i have tried : Odin , fastboot flashes , Cyanogenmod Installer ( the one i had the most progress but failed as well ) , the regular reset procedure , nothing works ! its impossible to clean wipe the device !!! no matter what you do .... once the phone restarts , everything comes back again ! old apps , old data , old software !
I've read somewhere that the problem was related to the READ , WRITE permissions on the phone partitions , somehow .... and i know everyone of us come from different specific scenarios , but it may be worth to give it a try if someone knows how to help us out on that part because it makes sense, it seems the filesystem on the device is protected somehow and when we try to overwrite everything things go wrong ...
Too many people with that crazy issue without a solution , warranty claims or checks on that device are long gone blues ... so dont even think about it .... not with samsung or with the carriers ... its over for us , so we need to figure out a solution for this issue and get our devices back working properly ! :highfive: