Okay guys, here's the deal:
I decided to go for a new ROM, and now I can't get the phone to boot up after installing any ROM. Even the last ROM that I KNOW worked wont start up. They install fine, bit wont boot. I wanted to repartition my SD card, so I did, which I have now set to a 1GB etx4 partition and all the rest to FAT32.
All I get is that white HTC screen, and it'll stay there infinitely.
Any ideas?
Did you wipe before flashing the ROM? You need to do a full wipe (in. Dalvik cache) before flashing a new ROM otherwise it will hang on the boot screen. Another thing to bare in mind is if you're moving to a ROM using A2SD/D2SD that first boot can take a good few minutes so patience is also needed
I did, yes. Wiped absolutely everything, and it still wont boot. I've left it for at least 20 minutes and still had nothing
Was there a specific way my card should be formatted? I basically followed this guide:
http://forum.xda-developers.com/showthread.php?t=905089&highlight=partition
Except, I did all the work in Ubuntu, and with the memory card plugged into an Xperia X10 (I don't have a card reader.
Your first partition needs to be fat, the second ext. Also if you did it while the xperia was booted it probably messed up the process, best bet is to redo the partitioning while in recovery.
DAE_JA_VOO said:
Okay guys, here's the deal:
I decided to go for a new ROM, and now I can't get the phone to boot up after installing any ROM. Even the last ROM that I KNOW worked wont start up. They install fine, bit wont boot. I wanted to repartition my SD card, so I did, which I have now set to a 1GB etx4 partition and all the rest to FAT32.
All I get is that white HTC screen, and it'll stay there infinitely.
Any ideas?
Click to expand...
Click to collapse
I am experiencing the same thing at the moment. Except I can flash the latest CM7 stable (7.0.2.1) and it works fine. Any other ROM however, just won't boot.
I have tried all Alpharev HBOOT images and several other Sense based ROMs.
My SD has first partition FAT32 and 1GB ext3
I have tried wiping everything with ClockworkMod Recovery 2.0.5.7 and 3.0.2.7 and still no success with loading other ROMs apart from CM7.
The wierd thing is that I have been happily flashing ROMs for months now. The last one I successfully loaded was ][Sense2.1 GingerBread]InsertCoin CM7 v07 and the first one that failed for me was AuraxTremeGinger v8.5-test Gingerbread 2.3.3· (GRI40 |720p|A2SD+|Fast)
It's almost as if the Boot.img is not being correctly written to the boot partition?
Any ideas?
Which recovery do you have ? I had the same issue until I've flashed Ra-Recovery or you have to upgrade your CWM.
paul.c said:
Which recovery do you have ? I had the same issue until I've flashed Ra-Recovery or you have to upgrade your CWM.
Click to expand...
Click to collapse
I currently have ClockworkMod 3.0.2.7 but I tried with 2.0.5.7 as well.
Have not tried RA yet.
hey I too have the same problem of the white HTC screen after bootup.
Background: upgraded the Orange FR 2.1 Desire to the OTA upgrade recommended without thinking. It went through partially and finally wiped out the bootloader or corrupted the bootloader on the phone. There was no backup take nor an gold card made with the phone.
So. even I am struck with a non-booting Orange FR Desire at the moment.
Boot menu shows HBOOT 0.93.001. There is no recovery program either. Can only enter into the system menu for recovery.
Tried the following:
1. Tried update using some orange ROM (update.zip) through the sdcard, but the signature verification failed.
2. Tried a couple of RUUs, but it fails with error 131. I do not have a gold card with me nor do I know the CID.
3. Access through ADB : Does not list the device itself with the 'adb devices' command. Hence no access to the phone memory. So, goldcard ultility wasnt really helpful to get the CID
RUU is able to talk to the phone. This means that the USB port is still functional.
What can I do? suggest please.
It depends on which ROM you intend to install. Desire S ports didn't support ext4 until a today when baadnewz and snq (not necessarily in that order) issued a patch. This can cause bootloops.
I had CWM 2.0.5.7 and tried to install Robocik's RCMixS and it stuck at splash screen until I switched to RaRecovery. Subsequent versions of CWM are reported to work. That is my experience.
If you need further assistance please state which ROM do you intend to install. Good luck !
Related
Both experiencing the same problem,
One UD 8.0 got stuck in loop after I tried installing Koush Kernel
2nD one is running CM6.0.1, was fine until I tried using to read Phone #1s MicroSD to figure out what was wrong.
2nd phone (CM6) then restarted randomly while plugged into PC, which started the bootloop.
Tried everything, nandroid (Couldn't mount /Data), I wiped, factory reset, tried reflashing update.zip for CM6 phone.
Both phones are completely useless, not sure what to do at this point and CM6's owner was leaving town.
Any ideas? Ultimate way to unbrick a DINC? If you know of anything, please help.
A boot loop is not a brick. I would nandroid back to stock(you did this right?) or use an RUU.
grnmons said:
Both experiencing the same problem,
One UD 8.0 got stuck in loop after I tried installing Koush Kernel
2nD one is running CM6.0.1, was fine until I tried using to read Phone #1s MicroSD to figure out what was wrong.
2nd phone (CM6) then restarted randomly while plugged into PC, which started the bootloop.
Tried everything, nandroid (Couldn't mount /Data), I wiped, factory reset, tried reflashing update.zip for CM6 phone.
Click to expand...
Click to collapse
Does this mean you can get into hboot?
If yes, you should be able to ruu an official release..
Sent from my ADR6300 using XDA App
I do not have a great deal of experience, but since you can get in recovery, place King Kernel #3 on your SD card, boot into recovery and apply the KingKernals #3 zip file from your SD card for the 1st phone. See if that fixes it. Just sounds like incompatibility with the kernel if it happened right after you flashed it.
ziggymanILT said:
I do not have a great deal of experience, but since you can get in recovery, place King Kernel #3 on your SD card, boot into recovery and apply the KingKernals #3 zip file from your SD card for the 1st phone. See if that fixes it. Just sounds like incompatibility with the kernel if it happened right after you flashed it.
Click to expand...
Click to collapse
UD is an AOSP Rom, King's kernel does not support it at this time.
I would try a fresh install of the 8-26 leak. Do wipe first, then do dalvik wipe under advanced settings. Get deodexed version of rom Here
If that does not work let's get some information
Did you run unrevoked forever and get S-off status?
What radio version are you using?
You should not be borked if you are getting into recovery you should be fine.
@ToyTank
BOTH phones are - 2.05.00.6.11 S-ON, Neither are unrevoked forever.
Problem with phone 1 (UD) is that the SD card is completely messed up now. It's an 8GB that has nothing on it, the compuiter is reading it at 758MB. Any function of Recovery leads to errors mounting, so flashing stuff isn't working, nandroid as well.
Phone 2 (CM6) let's me flash stuff onto it, "Install from sdcard complete." but will continue into a bootloop when I restart the phone.
I attempted RUU last night and maybe I'm doing it wrong but the software is giving me an error connecting to USB. How should I go about installing the 8-26 leak? Just wipe > throw in PB31IMG and install?
I assume I don't need unrevoked forever for this, I tried 8-26 and flashed PB31IMG.zip, Device 2 Starts dancing until it says "Main Version is older! Update Fail". Anybody know a workaround?
Try formating the sd card to FAT32 using a computer. That might help with phone #1. Error with usb can be solved using these steps.
1. Try the RUU executable. it will give you that usb error, taking you to the black htc screen.
2. Exit the ruu program (leaving phone in that state) and run it again. This worked for me when I RUU'd mine.
Who knows though. It may have been a one shot deal.
sounds like you are trying a bunch of stuff without READING about what you are doing. you flashed kernels with a rom that CLEARLY states that they will not work and then you tried to flash unsigned roms through hboot which will not work without s-off and then you try to downgrade when you have the ota leak (radio 2.05) which will not work.
you either need to get the ruu working, get s-off applied or follow the steps to go back to stock hboot.
time for you to start doing your homework to get yourself out of this mess.
Neither are bricked. Ruu back to stock.
yeah bro not good practice
@Fretless, @Lafester, @GermanBrat. Thanks for the comments - going to try RUU 3.21.605 and report back.
Hey guys RUU worked for Phone 2 (CM6) but is not playing nice with Phone 1. USB connection error. I appreciate the help so far, any more ideas for this phone?
It's basically stuck in white htc inc screen and will go no further. It's completely wiped and nothing will mount in recovery. RUU can't detect a usb connection but the PC beeps when I connect via usb
Hello, I got a problem when I flash the ROM for my desire with Clockwork 3.0.0.5 , need your help !!!
Thanks at first !!!
before flash the ROM, I have do the completely wipe and right partition for SD card (Fat32 +EXT4+EXT4+SWAP) or (FAT32+EXT4) according to the ROM requirement.
then after flashing, the flashing successful is displayed. but when I reboot the phone, it will keep in the first screen, and dead there.
And I have also connect it to the computer with ADB logcat, but nothing reported , it seems dead .
I have tried so many ROMs, only one or two ROMs can be flashed successfully and working ,also the information can be reported via the ADB logcat, others just display successful in recovery mode, but dead after reboot( I have waited for nearly 40 minites, nothing happed only the first screen ).
I only want to flash a ROM with new sense and data2EXT, but failed all the times!
please help me and tell me why !
thank you very much!!!
Does anyone know why?
I only want to flash a ROM with new sense and data2EXT, but failed all the times!
Click to expand...
Click to collapse
Why does it fail?
Try booting up with a completely FAT32 SD card and see if that changes anything. You could also try flashing with ClockworkMod 2.1.0.7 (what ever version it is) because you can get some errors with CWM 3.
Yes, I have tried for many times, and every time it is successful in the recovery mode and no error message reported,
but after reboot, it still dead at the first screen
why?
No idea. Devices are tempremental sometimes
I guess you could just wipe your phone clean with an RUU, root it again and then see if anything changes. Something could be corrupted.
Help! no one knows why???
Hi all!
So I go into recovery and try to do a backup. It works fine until about halfway in the process, when the phone suddenly reboots and I'm back into the main ROM.
I've tried different versions of clockwork recovery and RA-desire recovery, reformated/repartioned SD-card, reinstalled ROM but so far I am unable to make a backup. SD-Card is close to empty and phone is fully charged.
This never happened before.
Current CWM is recovery-clockwork-5.0.2.0-bravo
Phone is PVT-1 Bravo. S-off
Please help if you are able.
cheers!
this is a longshot but you could try ERASING the recovery, then flashing one you haven't tried before (links on my guide in #resources)..
Also, have you tried using a different SD-Card? or your SD-Card in a different phone?
Longshots are the only thing left to me my friend. Is erasing covered in your guides? Can you show me where?
Haven't tested SD card in another phone yet, but it "seems" to work fine in windows and Gparted. but it's also a prime suspect..
to erase recovery:
Code:
fastboot erase recovery
Ha! After unrooting and doing the whole root process all over again I discovered what might be the real problem. It's not that my phone reboots while doing nand back up, it's that my phone reboots after a period of time in recovery!
And because backing up takes some time, it usually occurs while doing just that.
So OK, new problem: My recovery randomly reboots after a period of time, any thoughts/ideas?
Hi,
I've got a HTC Wildfire S, rooted and S-OFF.
But it's stuck in bootloop, I messed with the system/apps folder...
So now it's pretty much messed up.
Didn't install ROM-manager, I know it was kinda stupid.
How can I reïnstall a custom ROM?
Can anyone help me?
Go into recovery and flash from there, or if you backed-up then restore the rom. If you don't have any roms then you can also mount your sd card from CWM recovery. If you don't have any custom recovery then you'll have to flash it through fastboot. I would tell you the process but I'm really busy right now, but I'm sure someone will explain it to you.
Hi, thanks anyway... hopefully some other kind guy can help me
I don't have any custom recovery, only a ROM which I want to flash on to the device...
seanw712 said:
Hi,
I've got a HTC Wildfire S, rooted and S-OFF.
But it's stuck in bootloop, I messed with the system/apps folder...
So now it's pretty much messed up.
Didn't install ROM-manager, I know it was kinda stupid.
How can I reïnstall a custom ROM?
Can anyone help me?
Click to expand...
Click to collapse
Don't install custom ROM's from Rom Manager's Download list. None of them are for Wildfire S.
Install CWM Recovery either through Hboot as a PG76IMG.zip or using Eoghan2t7's Windoze tool.
From there you should make a backup of your working ROM before trying any new ones in case of times like this...
Hi,
yes if I install the CWM recovery... can I then install my ROM? It's just a slightly modified Wildfire S Stock Rom...
And, I'm sorry to ask... But how do you install CWM through the boot menu?
seanw712 said:
Hi,
yes if I install the CWM recovery... can I then install my ROM? It's just a slightly modified Wildfire S Stock Rom...
And, I'm sorry to ask... But how do you install CWM through the boot menu?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1431969
Download that and connect your WFS to your PC, follow the steps which are quite easy. Then boot into recovery (volume down + power button, choose recovery by the volume buttons and power button), then choose install zip from SD and you can install the zip file (the rom) by selecting that file.
Let me know if this works
I have the same problem when using OC ROMs.
What am I doing wrong?
Now it's loading for ages or simply stuck in the bootscreen.
I too have the same problem when using OC ROMs. Why?
Hi, thanks for the help!
But I'm not quiet through yet... so I downloaded the WFS Manager, then I connected up my phone to the pc.
It was switched on, and just doing the bootloop again, showing the "Quietly Brilliant" sign over and over again.
And then I ran the tool, and it said "Please connect up your device" after I ticked on the first option ("Root And Install Recovery").
I guess this is because the WFS was bootlooping, and so the pc didn't recognise it. I also tried with the HBOOT menu on, but still the pc didn't recognise my phone. Is there anything I did wrong?
My pc (Windows 7 Ultimate x64), showed a popup saying there couldn't be found any driver for "Android 1.0". However it did work before the bootloo
If you have a card reader, or a phone that can take your SD card, then just remove your SD card, place it in an SD card reader or a device which can take your SD card, plug that device into your PC, place the ROM you want to flash onto the SD card, place your SD card back into your Wildfire, boot into recovery and flash the ROM from there.
I had a similar situation where I had an invalid xxxxIMG.zip file on the root of my SD card and a ROM that kept rebooting my device. Naturally, I started panicking, but when I got myself together, I just realized I could remove my SD card and then go into recovery, then reinsert my card and flash a working ROM.
Hope this works for you
Hi, thanks for the help. But I don't think you fully understand my problem.
So I have a stock ROM, rooted. And I messed with the system/app folder.
Now it's stuck into bootloop.
What does recovery mean? is it the menu entry in the HBOOT menu?
Because if I go to "recovery" and click it, after a few seconds I get a phone icon with a red triangle above it.
I tried putting the PG76IMG.zip file on the root of my SD card, but then in the HBOOT Menu, I get the message:
"CID incorrect !
Update Fail!
Press <POWER> to reboot."
What do I have to do?
find the cwm recovery thread and download the PG76IMG.zip then copy it to your sdcard then reboot to hboot. when it asks you if you want to flash recovry press volume up. then when finish instead of rebooting take out your battery. wait for 25 secs reinsert it then boot to hboot then choose recovery see new ui instead of the old one.
---------- Post added at 03:19 PM ---------- Previous post was at 03:16 PM ----------
here you go forum.xda-developers.com/showthread.php?t=1213229
Hi, when I do what you say I get the error:
"CID incorrect!
Update Fail!
Press <POWER> to reboot."
This is my course of actions:
I download the PG76IMG.zip file from the CWM recovery thread.
I place it in the root of my SD-card.
I start my phone pressing the volume-down button.
It automatically finds the .zip file and tries to update, but then I get the error.
What should I do?
I got what you were trying to say, I just didn't realize you had no recovery installed. I had the same error message pop up when I tried to install the recovery. I think it had something to do with the hboot being newer than something, something, blah, blah, bliddity-blah.
Anywho, I think I had the recovery installed along with the root using SuperTool.exe, but that won't work for you, since you obviously can't boot up, so you can't connect to the PC. All I can remember is I had some sort of app on my PC that allowed me to push the CWM Recovery without going through all that hboot stuff, since the S-ON wouldn't let me install PG76IMG.zip. Again, this is useless to you
My best advice is to try another PG76IMG.zip file and just keep trying until you find one that'll work, which you'll place onto your SD card from another device, of course.
EDIT: Link to where I got CWM Recovery from.
In this post there's an auto-installer that I used to flash it onto my device.
The reason you are having bootloop problems with OC roms is because your phone doesn't support OC. Don't worry though it's not just you, even my phone doesn't support OC. The best ROM to go with right now is Alquez's CM7, but I'm sure other developers will make non-OC roms.
Hi, THANKS!
I used the auto installer, and now I have the CWM recovery!
Can someone tell me now which options I should use to install the new ROM?
Maybe an advice of which ROM would be the best one?
I'd like something fast and stable, it would be handy to have one which doesn't have any stock apps installed with it...
I'd go with Jikantaru's ROM, if I wanted a more Sense-ish experience (which I, personally, don't). It does away with the bloatware, but it keeps Sense UI. I couldn't use this one, since my SD card is only 2 gigs and I can't partition it correctly :\
Therefore, my pick would be Cyanogenmod 7, which gives you a pure Android experience (no trace of HTC's bloatware, spyware or crapware). It takes away everything you don't need or most likely don't use and keeps it all clean and speedy, since there's no Sense, MotoBlur, TouchWiz or any other company-created user interface, leaving you to run everything right on top of the Android system. However, I've had some trouble with this one. First I had no mobile data connection or WiFi, and when I finally fixed that problem, I noticed I had no phone app -.-
So, now I'm using m1ndh4x8r's ROM, and I'm pleased enough with it. It lets me overclock and stuff, though I fear I might have effed something up while reverting to it from my non-fully-working CM7 flash, and now I can't install most apps :\
Now I'm pretty much waiting for a fully-operational CM7 build to come out so I can finally use my phone's full potential.
white htc screen
Hey hey =)
I installed the cm7 by alquez (already tried the RC and the nightly build) and I'm stuck at a white boot screen - I don't know if this is the boot loop error - I only see the green HTC sign with white background
Yesterday, I unlocked the phone, rooted it and today, I installed the CWM and from there, resetted the phone, data, and installed the zip.
Now, the white screen doesnt go away, even after 15min or so
Is there a thing i'm missing?
Thanks in advance!
Saftpackl said:
Hey hey =)
I installed the cm7 by alquez (already tried the RC and the nightly build) and I'm stuck at a white boot screen - I don't know if this is the boot loop error - I only see the green HTC sign with white background
Yesterday, I unlocked the phone, rooted it and today, I installed the CWM and from there, resetted the phone, data, and installed the zip.
Now, the white screen doesnt go away, even after 15min or so
Is there a thing i'm missing?
Thanks in advance!
Click to expand...
Click to collapse
Wipe all data and cache including dalvik from within clockwork mod
ok, shall I also format boot?
because I read it's pretty nasty deleting it if you don't install a new one, is that right? ^^
Dunno what has changed but thank you for your tip, it worked now!! =)
PS: didnt format boot ;-)
Hi guys!
Today, I was messing with my Desire (S-OFF, rooted, stock android 2.3.3) and I had to do a factory reset (I went to settings and wiped all data (including SDcard))...
So after that, the phone DID work, but Superuser had constant crashes and I didn't have root (no matter how many times I flashed the su or su binary .zip).
And I decided to go with a custom ROM, so I put a NAND backup of Aurora v6 (sense 3.0 rom) into sdcard>clockworkmod>backup.
Tried that and it didn't work... I was stuck in a loop:
boot logo>boot animation>power off>repeat
So I took the battery out, went to recovery and mounted my SDcard to my PC and put the ROM's zip file onto it... Tried installing and it didn't work (again, the boot loop). I also tried with a different ROM (runnymede's sense 3.5), but the result was the same...
Does anyone know what I did to pi** my Desire off so much?
And how do I fix it?
I've been at it for hours now, but no matter what I do in recovery (or hboot or fastboot), nothing seems to work!
EDIT1: Downloading a stock RUU, hope this helps...
EDIT2: The stock RUU didn't work... Guess I'd have to have a working Desire for this...
EDIT3: I've noticed that the boot animation isn't HTC's anymore... It's text, saying 'android'... Now I'm really out of ideas...
EDIT4: I pressed the 'clear data' or something similar button in bootloader... Seems that caused the weird boot animation? Trying to flash ROMs now
A few questions first:
1. Which hboot do you have?
2. Which RUU did you use?
3. What error did you get using RUU?
4. Which method for RUU did you use (run from PC or PB99IMG.zip?
5. How you did partition your sd card and did you make sd-ext (all advance roms sense 3.0 and 3.5 require sd-ext)?
Do these ROMs require ext partitions. Check in ROM threads. If nothing works best to downgrade hboot and run ruu 2.3. Thereafter run revolutionary.
Sent from my HTC Desire
A few answers (only correct if RUU is sort of an android installer)
1.I have the stock hboot (unless I broke that somehow with all my button pressing...)
2.The RUU's name is RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed
3.Well, since I was only able to try in the bootloader and in the recovery (mount USB storage), both times the error was the same; the installer was unable to detect my Desire...
4.I don't quite understand that (I'm a noob when it comes to 'codenamed' thingies)... What I did was I just downloaded the .exe file and ran it
5.I've tried both with a completely blank SDcard and a partitioned one (256MB size, 0MB swap size)...
Just to point out though that the Aurora ROM didn't need a partitioned SDcard the first time I installed it (when my Desire wasn't in this weird state).
Thanks for your quick reply!
EDIT1:
@handy5876: Yes, they both recommend an ext3 or ext4 SDcard partition. But as said above, the Aurora v6 ROM worked just fine with no partition at all!
someone755 said:
A few answers (only correct if RUU is sort of an android installer)
1.I have the stock hboot (unless I broke that somehow with all my button pressing...)
2.The RUU's name is RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed
3.Well, since I was only able to try in the bootloader and in the recovery (mount USB storage), both times the error was the same; the installer was unable to detect my Desire...
4.I don't quite understand that (I'm a noob when it comes to 'codenamed' thingies)... What I did was I just downloaded the .exe file and ran it
5.I've tried both with a completely blank SDcard and a partitioned one (256MB size, 0MB swap size)...
Just to point out though that the Aurora ROM didn't need a partitioned SDcard the first time I installed it (when my Desire wasn't in this weird state).
Thanks for your quick reply!
Click to expand...
Click to collapse
Ok, if you mean stock hboot, which stock Alpharev or HTC? If you have HTC one continue reading. If not reboot phone with power and volume down and see what is written on the top of the screen.
Download 2.3 RUU you have a guide in my signature.
Run RUU from bootloader, not recovery just reboot phone with power-volume down and run it from white screen.
I tried with the Aurora ROM again... Now it's just stuck at the bootimage!
Time to listen to a pro
My Hboot doesn't say anything about alpharev... But nobody ever changed that, so it must be HTC, right?
So, the *almost* top of the screen should say 'HBOOT USB PLUG' while running the RUU...?
I already tried that with (I think) Android 2.2 but it didn't detect my phone...
Downloading the 2.3 RUU
someone755 said:
I tried with the Aurora ROM again... Now it's just stuck at the bootimage!
Time to listen to a pro
My Hboot doesn't say anything about alpharev... But nobody ever changed that, so it must be HTC, right?
So, the *almost* top of the screen should say 'HBOOT USB PLUG' while running the RUU...?
I already tried that with (I think) Android 2.2 but it didn't detect my phone...
Downloading the 2.3 RUU
Click to expand...
Click to collapse
Then you're ready to go with RUU, just run it from that screen.
Sorry for the slow response, I had to eat meh lunch (while the battery was charging)
I'm getting the 'LOW MAIN BATTERY POWER' error [120]... apparently the battery level is under 30%, even after a 1h charge...
Waiting some more for it to charge, and I have a feeling this 2.3.3 RUU thing just might fix meh problems
Lol the 2.3 upgrade has saved a good few phones this past week
Sent from my HTC Desire
jmcclue said:
Lol the 2.3 upgrade has saved a good few phones this past week
Click to expand...
Click to collapse
Yeah, tell me about it
This is the ultimate HTC Desire un-brick tutorial in this thread
Here is the explanation how all that works.
Okay, so my phone is still not working, as the RUU thinks its battery is under 30%, even though my Desire is fully charged up...
Is wiping battery stats a good idea?
@nlooooo: Thanks! Now I finally! have at least part of the idea how it all works
EDIT: The RUU thinks my battery is less than 30%, even though it has been charging since my last post (and the green LED confirms it's full).
Why?? I just wiped the battery stats, should I do anything else?
EDIT2: Switched from BOOTLOADER USB to FASTBOOT USB, it now seems to work...
As I understand, from here on I can restore NAND backups?
I'm only asking so I wont have to go through this all again -.-'
EDIT3: Just installed Revolutionary CWM (the easiest way to get CWM), flashed su zip... Superuser finally works and my su binary was auto-updated (after many months of manual updates)
Still, can I do NAND restores safely right now?
You'll have to s-off your device and the tool you need to use will flash recovery.
For s-off see this:
revolutionary.io
And read the guide given. Don't worry it will ask you for your IMEI when you start download it's just for the purpose of building your beta license key.
After you flash recovery I think you know what to do...
I already s-off'd the first day I got the thing seems like S-OFF never disappears...?
Just flashed CWM with revolutionary, too (I'll update later) and just flashed su zip.
But is it safe for me to restore NAND backups of other roms? Or must I first install the rom and then restore the NAND?
Now you are on stock hboot with data partition at 147 MB. If your NAND backup data partition is more than 147MB you will get into trouble.
How can my NAND backup partition be different than the one I have now (stock) if I've always had it...? This is sort of confusing... :S
someone755 said:
I already s-off'd the first day I got the thing seems like S-OFF never disappears...?
Just flashed CWM with revolutionary, too (I'll update later) and just flashed su zip.
But is it safe for me to restore NAND backups of other roms? Or must I first install the rom and then restore the NAND?
Click to expand...
Click to collapse
You can restore just backup you don't need to flash rom. But first try to boot with stock 2.3.
So RUU finished with no problems? Now I'm not sure which hboot you have cause if you s-off with revolutionary on the top of the screen pink revolutionary should be written, and it doesn't disappear because RUU can't overwrite custom flashed hboots (alpharev or revolutionary).
---------- Post added at 05:39 PM ---------- Previous post was at 05:35 PM ----------
handy5876 said:
Now you are on stock hboot with data partition at 147 MB. If your NAND backup data partition is more than 147MB you will get into trouble.
Click to expand...
Click to collapse
He was on stock before so no problems should occur.
I'd be much happier if you wrote that in your native language (Serbian), since I didn't get any of that... (and yes, I understand Serbian)
I think I have the stock hboot, but I never changed it, so what else could it be?
I S-OFF'd my Desire using Revolutionary, and no RUU, ROM flash or ZIP install could ever make it S-ON'd...
And on top of hboot there is a pink 'Recolutionary' sign...