Develop Bugs

[Q] Misc. Questions, Flashing to Ginger help

Thanks for taking your time and helping me, I saw you guys(and girls) have done some pretty amazing things here at XDA. I just need some help with getting this Gingerbread ROM to work.
I'm using Supersonic 2.2.1 first off, and using the alter. recovery rom from Rom Manager.
Ok, so I rooted my phone using rEVOked and chose a ROM called Bc-Gingerbread-beta4. I'm not sure of the eact title used, but if anyones faimilar with Gingerbread ROMS, they should know what that is... It was on the EVO ROM page.
So at first, I was using ClockWorkMod Recovery (2.6.*) to try and install the ROM. I eneded up with status 7 ever time, so I tried to upgrade to 3.0.* (newest one) and recieved a error about not being able to flash. No details were given.
I tried flashing to the alternate recovery, and it worked. From their, i (un?)successfully installed the ROM according to the recovery application.
The status bar didn't move past the halfway mark, but i figured it was just how it worked..
Then, I tried to boot into the new ROM. I was on the HTC screen for about 3~5 minutes, then it showed me the android load screen instead of the usual Sprint/4G screen. From their, it was in a constant loop because every 3 to 4 seconds, it would take off the android logo, then place it back. I waited approx. 10 minutes... Nothing. Unfortunetly, the alternate screen doesn't have the option to browse for your nandroid back ups (mine aren't in /android) So i'm left with a relativly bricked phone until I can find a working ROM.
I have a microsd card reader.. so I'm not too terribly screwed, I just need help on what I did wrong, how can I fix it (if im able to), and what Gingerbread ROM I should use. It needs to be relativly stable. I don't care about 4G support, even though its almost everywhere in Atlanta. I'd like to have video rec. if possible. and 8MP support.
If it fits those standards, please, I'd like to hear what the community thinks is a great Ginger ROM.
Also, I'm using Windows. I have the adb shell installed, and im familair with basic-medium level terminal commands.
Edit: I'm going to flash again, using cm_supersonic_18.zip. It says installing update, but it says flash zip from sdcard in the main menu...
Edit #2: apparently it's a Cyanogen mod (#7)
Just keeps looping the android on the skateboard screen... I'm going to figure out how to get back to the clockwork recovery console and -hopefully- get this thing working.

[Q] clockwork problems

I've just got my first Android phone (an HTC Desire from Telstra - quite a good phone from all reports but hobbled almost to the point of unusability by Telstra). My Android guru (also a member of this forum) has had little success rooting it so it can be made more useful because, although most of the process works, it seems that Clockwork is not going in successfully and doesn't seem to be able to recognise the SD card (8GB, partitoned at 7GB (FAT32) and 1 GB (EXT3)). It claims that it can't find several of the files it needs to work.
The upshot is that, although the screen comes up with the options of things to do (restore etc.), when selected it just hangs with a black screen.
I checked some other similar threads but couldn't come up with anything.
Please pardon any inanity - I'm very new to this.
Any help most gratefully accepted. Thanks

when selected it just hangs with a black screen.
Click to expand...
Click to collapse
When selecting the option use the centre trackpad to select not the power button...
However i'm also new to a Desire (i have a desire hd) and have exactly the same on the Desire i rooted with Unrevoked last night, for example if i try to wipe system or data it just comes up with an error message...
Any ideas thanks...

Just tried to run unrevoked again to see if recovery would install properly this time.
Yesterday it said it was a triumph this time it says failed to get root is the software to new...
Is that because its already rooted or it didn't actually work properly yesterday ?
Thanks

After reading a bit on google and on this forum seems that Unrevoked may be the issue someone else with the same problem got it sorted by using Unrevoked 3.21 rather than the 3.32 that the unrevoked website installs...
Next question anyone know where i can get 3.21 been googling and can't find anything that will actually download..
Again many thanks

wakers said:
After reading a bit on google and on this forum seems that Unrevoked may be the issue someone else with the same problem got it sorted by using Unrevoked 3.21 rather than the 3.32 that the unrevoked website installs...
Next question anyone know where i can get 3.21 been googling and can't find anything that will actually download..
Again many thanks
Click to expand...
Click to collapse
How about PMing the person who sorted the problem out to see if they still have 3.2.1 on their machine? I thought I did but on checking I've got 3.3.2 - sorry!

Hi
I had to use AlphaRev to be able to flash custom firmware. Unrevoked did root the phone but didn't s-off. If you plan to use Unrevoked VirtualBox method get VBox v3.xx, v4.xx has something messed with usb passthrough
Sent from my HTC Desire using Tapatalk

I managed to find a version of the unrevoked that was suggested but it hasn't made any difference...
I've been ages reading and going around in circles
The Hboot is 0.93.0001
The phone appears to be rooted as superuser is on it and appears to be working.
THe phone will boot into recovery but recovery doesn't work
I've tried using a different recovery with rom manager but it makes no difference when i boot into recovery its the same Clockworkmod recovery 2.5.0.7 even though in Rom manager it says its changed...
As it boots into recovery there are a few messages underneath
e:cant find misc:
e:cant mount cache : recovery/command
and a few other lines which i can't remember but similiar
I've tried removing and flashing a different recovery via adb and i get a message saying "remote not allowed"
I've tried flashing recovery with a terminal emulator but can't get it to work either.
Do i need to do the alpharev to get S-Off first before i can sort out recovery ? and if so any info on how to do this, again many thanks and sorry for so many questions.
I've rooted Magic's, Legends, HD2's and my Desire HD but this desire for my missus does have me a bit stumped...

I wonder if fake flash would help in this situation?
Might be a viable way to get recovery functioning...
http://forum.xda-developers.com/showthread.php?t=698403

As it boots into recovery there are a few messages underneath
e:cant find misc:
e:cant mount cache : recovery/command
and a few other lines which i can't remember but similiar
These look like about the same as the ones I get

OK... I don't know why, but this worked for me (and my guru). Instead of pressing the power button as the enter button during the rooting and restore process, we pressed the mouse button and it all worked fine. The errors still showed up but they didn't cause any problems. I think this might have been one of the first suggestions but I seem to have missed it (this is what you get when you stay up 'til stupid-o'clock trying to sort stuff out).
I'm up & running now and I hope this helps some others having the same issues.
Thanks to all those who provided suggestions.

gen_scheisskopf said:
Hi
I had to use AlphaRev to be able to flash custom firmware. Unrevoked did root the phone but didn't s-off. If you plan to use Unrevoked VirtualBox method get VBox v3.xx, v4.xx has something messed with usb passthrough
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Just to clarify this point, Rooting and S-OFF are 2 totally different things.
Root access is to the loaded ROM on the phone. It allows you to gain access to places you normally can't go inside android like \system and \recovery
S-OFF is turning signature verification off in the Bootloader. the bootloader is the lowest system level you can go and as such can do some pretty serious things there.

jimmytheflea said:
Just to clarify this point, Rooting and S-OFF are 2 totally different things.
Click to expand...
Click to collapse
Yes, I know this. S-Off option was selected in Unrevoked menu (and didn't work). AlphaRev 1.8 (LiveCD) didn't work on unrooted phone but after rooting did it's job

Finally success i think sometimes you can read so much info you get confused.
Did alpharev via CD and installed alpharev-cwm recovery option and its all working as it should be, can't believe how simple it turned out to be in the end...
Thanks to all who replied much appreciated...

Hello, i am using oxygen 2.0.3 ROM now. I had been flashing roms with recovery for a few times. But now, it seems like recovery is unable to detect changes to my sdcard.
Whenever i boot into recovery to install zip from sdcard, it will show me the folders and zip files that i had before. Any changes i made to the sdcard was not reflected.
I search through the web and this forum and you seems to have the closest issue that i am experiencing. It would be great if you can advice if your method can solve my problem as well and what are the detail steps you took to solve it. Thanks alot man.

Hi mate the issue i had was that recovery didn't seem to install properly at all and i could see the rom etc on the sdcard and any changes i made but it wouldn't work, i also had issue's with not being able to push commands through adb.
What worked for me was creating the Alpharev ISO image on a CD and running it following the instructions, it was incredibly simple but i had a stock rooted rom on my desire.
The alpharev instructions are here
http://alpharev.nl/
Downloadf the Flash utility then burn the flash utility (still zipped) to a CD shut down your laptop press F12 as it boots choose boot from CD once the laptop screen goes black plug your phone in (i had mine on charge only) you also need to make sure USB debugging is checked...
And follow the instructions for me it S-Off'd the phone and installed the Alpharev-CWM recovery which is working as it should...
Not sure thats going to cure your issue though as it seems you have an issue with your recovery reading the SDcard this wasn't an issue for me...

cheongster said:
Hello, i am using oxygen 2.0.3 ROM now. I had been flashing roms with recovery for a few times. But now, it seems like recovery is unable to detect changes to my sdcard.
Whenever i boot into recovery to install zip from sdcard, it will show me the folders and zip files that i had before. Any changes i made to the sdcard was not reflected.
I search through the web and this forum and you seems to have the closest issue that i am experiencing. It would be great if you can advice if your method can solve my problem as well and what are the detail steps you took to solve it. Thanks alot man.
Click to expand...
Click to collapse
Do you see changes made to sd card when booted rather than in recovery i.e. if you add a zip to SD and reboot to your rom, do you see the SD, then you don't see it if you reboot again to recovery?

stringer7 said:
Do you see changes made to sd card when booted rather than in recovery i.e. if you add a zip to SD and reboot to your rom, do you see the SD, then you don't see it if you reboot again to recovery?
Click to expand...
Click to collapse
Yes. I see the changes made to the SD card in my ROM. But the changes don't get reflected when i am in recovery.

Is your issue occurring after you mount the card in usb mode in recovery and then adding file and then trying to flash that zip? if so, then you can see that file by choosing reboot recovery option
Swyped with my Starburst Classic based Desire with Intelligent Data2sd

I transfer the files while i turn on the usb for data transfer in the rom. Do i have to do the file transfer while i'm in recovery?
I used to be able to do it previously. I am not sure what happened along the way and it stopped working now. I did delete all the files on my SD card before having this issue. Not sure if thats the course and if there is a fix for that.
Thanks!

Well if you were doing it while booted up, sorry I have no idea why it doesn't work then.
Solution is to reflash your recovery
Swyped with my Starburst Classic based Desire with Intelligent Data2sd

[Q] eMMC issues - how do i tell if i have a bricked Desire Z?

Not sure how to start this...
first off, i'm pretty sure my phone now has a fried eMMC chip, but in reality, i don't really know...
the reason i say i think it's fried is because no matter what method i try to flash anything to my phone with...it simply won't do it...most fastboot commands will not work anymore, my computer won't load the devise anymore so no adb commands, bootloader fails everything when trying to flash a stock rom and gets hung up updating the radio_v2....i've tried running official RUU's but it keeps telling me my phone has less then 30% battery life, wich is simply false. and i can't get into my recovery without it crashing the phone and not letting me turn it back on (till battery pull).
i went onto the #g2root and #xda-devs channels on the freenode server in mIRC, and had talked to a couple people there who also think i probably fried the eMMC chip (making it impossible to write or read anything from the phone), but again...i'm really going on word of mouth rather then first hand knowledge here.
but again today, i ran into yet another possible solution and i just want to know if i should bother trying or if i have a chance.
http://forum.xda-developers.com/showthread.php?t=1314629 is the thread, but i think this is for a desire s, so i suppose my question would be...would this method still work if i just used the right files or, again, am i screwed?
i have an HTC Desire Z that i got from Bell in Canada. it has gotten an OTA firmware update, and does not have root or s-off
if i remember right, everything is still stock, completely. minus the now possibly fried eMMC chip lol
thank you in advance and i will try to edit this post as neccessary so as to update any needed info.
please ask me questions as to what i have done and i will try my best to let you know. i know i had followed probably too many guides for rooting with too many methods lol next time, xda-dev's wiki guide, and that's it!
[edit:] i just found this too...lemme know if this helps..... http://forum.xda-developers.com/showthread.php?t=1284196
[edit:] i do know that when i go into my recovery, it does say those things (e: can't mount cache, blah blah) but it crash's out and doesn't actually get me into the recovery console. if so i would be able to envoke some adb commands and just finish this, but that's adding to the issue really...not being able to get into my recovery.

i feel with you.
it happend for me just today morning.
got my desire z on thursday, installed usual apps.
it started to freeze in random app installations. the last softreset threw it into a boot loop with the same problems you stated above.
you can get pre formated desire z emmc's for around 30 - 40 euro i think. but soldering them on your own requires some skill and tools since their contacs are below and not on the side.
this accident threw me back to my old htc touch diamond (with windows mobile 6.1 D: )

[Q]I'm kinda confused on a bootloop problem

Hi guys,
I just got into flashing my phone a few weeks ago when my stock desire started giving me endless low memory notifications, so I was attracted by A2SD. Anyways I've read and read, then read some more and I've been able to answer all my own problems up to now.
I rooted, S-offed etc. I installed Pyramid with sense 3.0 as my first ROM but it felt laggy and frustrating to use. So after reading I decided to try CM7. It's super fast and stable but I was finding I just could not figure out how to install apps. It has no market app so I'd go to the market website and install then I just couldn't find the app anywere. Plus it would tell me I had apps installed I didn't, but did on the first rom. I just wiped everything when I installed CM7. I guess I was used to the user friendly sense but I was finding CM7 not as simple.
So as fast and stable as it is I wanted to play with some other ROMs so tonight I got MIUI. It installed nice but as soon as it loaded after about 5 seconds it would reboot. and again and again. I read about boot loops in the thread but couldn't find a definitive answer. I read the boot loop help thread and then tried formatting boot, system, cache, sd=ext and whatever else the instructions said. Wiped again, installed MIUI and same thing.
It's getting late and I need my phone for tomorrow so I thought I'd try Insertcoin. The problem doesn't seem to be just MIUI though because that ROM did the same bootloop. About 5 seconds after everything seems to load properly. Now I'm a little worried.
Tried the last known good ROM, CM7, and viola! Everything is good and stable again. I'm wondering about partition table I didn't flash a new HBOOT. Mostly because I'm not sure how to? I'm unsure about this step (from the alpharev site)
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl.img' (change into the correct filename for the HBOOT you downloaded).
The part after the arrow is were I'm not sure.
The thing is MIUI says it will go on a stock HBOOT so I figured my bases were covered?
Sorry about the long thread and honestly I've read and I'm ready to ask the community for advice. I've solved several problems on my own and here I am! Hopefully got this in the right fora. Also hope I got all the relevant info in. Any advice or idea on why those two ROMs boot looped would be awesome I still want to try MIUI.
Cheers

Can you give more info, like how you partitioned your sd card. What info does the bootloader in the top left of the screen give you. Wright it all down here. Maybe then its easyer to help.
Sent from my HTC Desire using XDA App

Your phone setup NEEDS TO MATCH developer requirements for that rom... so read instruction and set your phone up

I can't help you with your boot problems,
but I can however help you understanding the
third point in the alpharev description, as I was
facing the same understanding problem 2 days ago.
The command 'fastboot flash hboot bravo_alphaspl.img' is used
via your cmd / konsole/ terminal on your pc.
So what you must do is,
- install android sdk
- connect your desire via usb, go into fastboot-mode
- navigate via cmd / konsole / terminal to the 'platform-tools' folder (there is
the fastboot script you need to trigger) within your android sdk folder
(- you can test if your device is found with the command "fastboot devices")
and..yeah. Enter the commands from the alpharev page in your terminal.
/*Just remembered, you need to install the desire usb drivers, when you
are using windows, or something like that. I'm not using windows, but I'm
sure it's easy to google if you need help on either the usb drivers OR
on how to install the android sdk under windows.*/

MarcelHofs said:
Can you give more info, like how you partitioned your sd card. What info does the bootloader in the top left of the screen give you. Wright it all down here. Maybe then its easyer to help.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I used Gparted to partition the stock 8GB micro SD card that came with my Desire. I have a fat 32 partition followed by a 1000mb EXT4 partition. Bootloader info is:
-----AlphaRev-----
BRAVO PVT4 SHIP S-OFF
HBOOT- 0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.027
Aug 10 2010, 17:52:18
Hope this helps if you have any idea what the problem is. The only thing I haven't played with is the radio.
Malso thanks very much for the info I was really unsure how to proceed there! I'll flash the CM7 HBOOT. Cheers.
kotag82 Thats the problem I can't figure out why Pyramid and CM7 work and MIUI or Insertcoin don't I can't figure out where the difference is between CM7 and MIUI that would prevent one from working. I thought my phone was matched exactly for MIUI. an't figure out what changed that one would work and the other just reboots 5 seconds after loading. The flashing of both MIUI and Insertcoin seemed to go perfectly.

Wondering if a full SD format would help? I've read and re-read the MIUI thread it it really looks like I should be good to go?

Yeah never did get my MIUI working. Allways with the rebooting problem. Did get RunnyMede AIO going and I'm loving that. Except for the battery drain issue. It will be fine untill about 50% and then I'll use about a percent every few minutes even with the phone off and in my pocket!

[Q] Bootlooping

So I've done some searching, and have yet to find a solution to the issue I'm having. GF's phone is the HTC Incredible as you can probably already guess by what subforum this is posted in. It's been running the CyanogenMod 7.1.0 Rom for quite some time alright. From everything I've seen, most people that have had issues with bootloops is because they have been flashing to a new rom/radio and skipped something/pulled the battery/or something along those lines. This phone has been running fine, and then out of nowhere I guess, started to restart itself continuously yesterday. I can get into HBOOT no problem, but that's about it. When I try to select Recovery, it just kicks right back into the bootloop. Anyone have any suggestions??? Phone isn't under warranty anymore, and her contract ends in a month and a half, so we don't want to have to buy a new phone before then if at all possible.

try reflashing recovery.
first start with a freshly formatted FAT32 sd card, download this file and place it on it
http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
this should be the only file on your SD card. now turn off your phone and put the sd card in. now boot into hboot (vol down+power) and it should prompt you to update by pressing vol up. do this and when it boots back into hboot, remove the sd card and delete the file. then try booting into recovery

Tried it and still no change

there was a similar situation (stangely similar ) here
http://forum.xda-developers.com/showthread.php?t=1628585
both cases happened to be running cm 7 too...and randomly started boot looping and stuck with no recovery.
i would read through that thread and see if any of the steps will help you

Just read threw it all, and everything sounds exactly like it does in my case. That one ended up not so well. Do I just assume that this one is done as well???

downwardzspiral said:
Just read threw it all, and everything sounds exactly like it does in my case. That one ended up not so well. Do I just assume that this one is done as well???
Click to expand...
Click to collapse
you can try doing the steps in that thread. you may have better luck. Perhaps someone else on this board knows of another method that may help

Just because it didnt work for that guy, dosent mean it wont work for you. Are you s-off? Have you tried reflashing recovery yet?

it's S-Off and I've tried to reflash recovery

How about an ruu?

tried that. tried through the pc and the computer wouldn't recognize it. tried by updating it in HBOOT, and after the update, it would still just bootloop

Sounds like another possible hardware failure. My only other sugestion would be to try the fastboot flash of the misc img, but it probably wont work either. Its very strange, i have seen this 4 or 5 times now in the past couple months, all on cm7, and all unfixable. I dont want to start a war, but mabey something with cm7 or cm7 and a certain program or combination of programs, is causing this. Or mabey its just cause these phones are getting up there in age.

i too find it odd each one is cm7..

Well thanks for all the help anyways. A new phone it is I guess

the basic problem is CM 7 (for the Dinc). it is extremely common. i have seen it happen to so many people now. it drives me insane when i see people suggesting CM 7 "stable" to others (for the Dinc). i have tried to communicate this here and other places too... i have given up hope of people ever accepting this obvious situation. the "stable" version of CM 7 is simply not stable.
however...
a reflash of clockwork recovery has always gotten people out of the CM 7 bootloop. then they are able to get a working rom installed.
i don't understand why you can't get a recovery re-flashed.

Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A