Database Develop

[Q] lost recovery menu all that comes up is bootloader .

hi there , last time i used this forum i had forced android onto a htc diamond and you guys helped me a great deal with the problems i encountered .. this time i have a problem with my milestone .
i updated to root and 2.1 with no problems a few months ago , i was going to attempt to flash froyo onto my handset in the near future but for now i just fancied clearing everything off it .
i tried to boot into recovery menu (camera and power button) and all that came up was a bootloader that looked like normal except for an extra line of :
Err:A5,69,35,00,2F
under the bootloader version .
i also tried to boot into the bootloader and flash using rsdlite after reading about that method , ( D-pad up and power ) , this bootloader doesnt have that error line . Although my device is being recognised by rsd i am unable to flash it .
The wierdest thing about all of this is that it isnt bricked completely in that it will still boot up and allow me to make calls etc , anyhelp you guys casn offer will be appreciated .
thankyou in advance
Sean

have you tried to hold 'x' on the hardware keyboard instead of camera-button to get into recovervy?
with rsdlite try to hold the up-dpad to avoid booting before flashing the vulnerable recovery is finished.

thankyou for your fast response . holding the x button did nothing phone just booted as normal .
rsd still wouldnt flash after i held up -dpad device in rsd looks like ..
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x009074
DRM Version: N / A
AP Die ID: 04200117737b0304000000000400
which i assume isnt right :S

plug the phone into rsd while booted and rsd will recognise it so you can flash as normal. this happened to me before. no biggie.

well that worked ... kinda .. it recognised the device and after several 0x7100 errors by moving the sbf file around my computer i managed to get it to flash ... only to find although it said pass it had done nothing to my phone at all and i was still unable to enter a recovery menu :S
And i can no longer access memory card :S

Ok. That is weird.
try complete uninstall and reinstall of motorola drivers and rsd. Also reseat your sd card. Redownload a fresh copy of the sbf and try again.
Sounds like something somewhere is corrupt so clean clean clean.

well ive tried about six times now and all it seems to do each time i flash it is update the bootloader and seeing as i cant get into the menu where i have the update from sd card option i cant change anything else ..
I think for now i will just be happy to use it as a phone i get to upgrade in a couple of months anyway .
Thankyou so much for your help guys .

Well one thing is clear your recovery partition is damaged/not formated properly.
But as a recovery is able to restore the bootloader, bootloader togehter with ROM is able to restore the recovery, so if one is not working phone is still not bricked at least this is how it is intended.
But with flash .sfb you got errors, that could imply bootloader also has some problems..
There is posibility that recovery part of phone is hardware damaged, so even working bootloader cant restore it, or damaged in some other way that bootloader cant repair it, maybe that were the errors for.
Than you say flashing sfb did nothing? What exactly did you mean, even phone ROM didnt get changed, or just recovery didnt? Couse maybe you can still flash sfb to change ROM. This way you will just have to stick to stock ROMs that are provided as .sfb files.
Try flashing sfb again and check if firmware is changed.

[Q] Stock rom keeps hanging on boot screen.

I haven't touched my Rogers G1 rom, it is as stock as they come. One day the battery died, so I plugged the phone to charge and also tried to start it up.
My problem started after that.
I will try to restart the phone and it'll get stuck on boot screen - where it says HTC or sometimes even just the Rogers screen.
Only solution is to take battery out, do hard reset.
I've searched the forums but everybody else asks regarding modded roms and not stock.
Any idea how I could resolve this issue without flashing new roms? Or is that my only way out?
Thanks.

Did you apply Rogers mandatory 911 update that was released about a year ago? You can check by booting into fastboot mode (hold the camera button while powering it on). If your radio version is 3.22.26.17 you have the update. Rogers locked down fastboot in this latest update and the only way to root it is through the ROM. If you don't have this update I can walk you though the steps to root your phone though fastboot.

Just checked and it does have the update.
Should I just go ahead and flash new roms?
I keep having the same issue as before.

With the latest update Rogers locked down fastboot so it is useless. So, I don't believe that there is any way to flash a new ROM without first booting into your existing ROM.

Sorry but I'm inexperienced with flashing roms...
If I can't flash by the fastboot method, I can still flash by rooting the phone, correct?

JiggyNS said:
Sorry but I'm inexperienced with flashing roms...
If I can't flash by the fastboot method, I can still flash by rooting the phone, correct?
Click to expand...
Click to collapse
I'm not completely sure, but usually you need to be able to get into the rom to root. Maybe there is another way.

6 hours later and i got nowhere...
I rooted phone, flashed new cyanogen rom, setup amon ra's recovery but I didn't do new radio since my current is one of the newer ones.
The booting goes nowhere as soon as the rogers logo shows at the beginning of boot up.
Would a new radio help? Could that be the issue?
edit:
The phone rebooted properly and now I have a working fone!

Wait, how did you root the phone without getting into the ROM?

beav_35 said:
Wait, how did you root the phone without getting into the ROM?
Click to expand...
Click to collapse
I used the Androot method, copied onto sd card, launched file via file manager app on phone and it rooted the phone. This is how I remember anyways - I fiddled with the phone for good part of the afternoon so my memory is all over the place with the specifics.
I used this site for rooting.

I thought you said in the op that you couldn't boot into the ROM (got stuck on boot screen). So, what was the problem in the first place? (or how did you fix the ROM?)

Sorry I guess I wasn't clear enough in op.
The only way I could get to use the phone was to do a hard reset and let the phone boot up from there, however if I ever wanted to turn the phone off or restart the phone it would get stuck on the next boot up.
I was able to flash the rom by constantly hard reseting the phone every time I needed to put files onto the memory card.

Keep phone on long enough to transfer files?

I have had a ATT captivate for almost 2 years now. It falls in the IMEI range specified by ATT. But it wasn't really a problem until very recently.
It got much worse about 3 weeks ago when the phone kept constantly rebooting. It would load the OS, begin media scanning, once that concluded, it would immediately reboot (almost every 20 seconds). Only way to stop the reboot cycle is to take out the battery. No new apps were installed, no system changes were made when this happened.
I am able to get the phone's menu which allows me to wipe and I am able to get the phone into download mode.
I have read (4) of this article regarding sleepdeath and all corresponding articles referenced.
This is what I did...
1) Performed hard reset, cleared storage. This eliminated all third party apps, returned the phone to stock (I think), but the phone is still rebooting.
2) Attempted to install a brand new rom (CM) via CWM = Problem got much worse. Still rebooting but this time, after the ATT logo appears, the screen changes to static (noise) and reboots. Followed instructions and diles from here.
3) Since the phone became useless, I hunted around to return it to stock again and used this. The phone now boots up into the OS, but now it's back to rebooting.
I repeated steps 2 and 3 just to make sure I didn't miss a step, but same problem.
I have 2 goals:
1) Get the phone working, if at all possible!
2) If that's not possible, recover the 300 pictures that are on the device.
My challenge is that since the phone keeps rebooting every 20 seconds, by the time it connects to my PC via USB as external storage, it reboots! This ofcourse is also preventing me from loading a ROM directly on to the SD card.
So if anyone can help me to do the following:
1) Point me in the right direction to how I can keep the phone in a certain mode or setting (download mode doesn't work) where I can transfer files, recover my pics, and perhaps load a custom ROM?
2) Next steps?? Am I even on the right track? Since the stock rom keeps the phone rebooting, will a custom ROM solve the problem (have not been able to get a conclusive answer on this on the threads referring to sleep death (which this is an exaggerated version of) or is the phone a lost cause?
I know I can call ATT and try to haggle a replacement (since the phone is out of warranty), the only benefit being they don't renew my contract, and I don't have to upgrade.
Any help or guidance is much appreciated.

Wow, bummer
Well i don't know if you can mount the sd card in stock recovery (never used it) but if you can't then you could flash one of the stock one click roms with cwm recovery from this thread.... http://forum.xda-developers.com/showthread.php?t=1300843
In cwm recovery there is an option to mount sd while connected to pc so you can backup your stuff.
For the reboots, could it be your power button? Mine is acting up, and often seems to cause reboots. There are threads about fixing that. Idk just a thought.
Hope that helped a bit
Sent from phone with app

Like the previous post says, maybe try a custom recovery, go to mounts and storage, and mount USB storage. While you're at it, try flashing a compatible ROM through that recovery i.e. GB rom if its a GB kernel with CWM recovery or ICS rom if its an ICS recovery.

Did you try to do a dump of SD card data with adb?
Sent from my GT-I9000 using xda premium

The static issue is because you flashed a gingerbread kernel but you don't have gingerbread bootloaders. You can fix this by flashing an AT&T stock one click with bootloaders.
Once there, you can flash corn kernel and use recovery to mount the sd card.
Or I guess you could flash a froyo kernel.. there's a number of ways to do this.
Sent from a jelly bean

Weir flash / memory problem on my m8

I just got and m8 from Cl, it was cheap and I was told the phone had a software issues so I took the plunge.
The phone seems normal, its pack o apps and you can play with it, then I decided to do a factory restore, but it failed (after the reboot it goes to a error screen showing a phone with and exclamation mark)
I tried the same from hboot, same result..
Tried to unlock bootloader, it appears to work but after boot the phone I still the same (loked and with all the user info intact )
Tried to erase the user accounts, it works, I can do a new setup of the Google account, but after restart the phone goes back to the initial state (user accounts are back)
I am not sure what's going on, but it looks like if the memory was protected and after every reboot it goes back to the original state.
Any suggestions of what to do? I am starting to see of there is any way to get warranty thru htc,
Thanks in advance.
The phone is in 4.4.2, can't take updated (it reboots itself on the process)

The phone with the exclamation point indicates the stock Android system recovery is installed. You could try and install TWRP recovery, at which time you could install a custom ROM. My only other thought is to run the RUU for the latest system update. If that doesn't straighten out your issues, something else is going on. Hit the link below and follow the instructions for the manual system update. This is the non-HK RUU. If you need the RUU for the HK version I can post it, also.
http://www.htc.com/us/support/htc-one-m8-sprint/news/

Thanks, I tried to install twrp but it fails, the bootloader is still locked and won't unlock, is there a way to install twrp without unlocking bootloader?
Will give it a try with the RUU, when tried to update thru fastboot it fails, it starts to do all the file checks and it just send you to the "press the power button message" , but no update was perform.

You might give this a try to get your bootloader unlocked and TWRP installed. There is no way around it. You have to unlock the bootloader first before you install TWRP.
http://forum.xda-developers.com/showthread.php?t=2727900

Thanks a lot for the help, nothing has work so far, the phone keeps having random reboots and every time it comes back its like it load an old backup, havent been able to do a firmwware upgrade (from android over wifi, fastboot, or windowsPC).
Is there an utility to test hardware? (possibly memory)
thanks

At the end I contacted HTC support and after some test I was told my phone was still under warranty and I got and RMA (great service)....
Thanks a lot for the help...

please help a person who doesn't know much about ROMs, kernels, root and so on.

i'm in desperate need for guide please,
so i first off i had some questions (excuse my stupidity but i really couldn't find any answers around)
1) can an never-rooted android device's build number change or is it always the same? like with stock/official updates only?
2) my recovery mode (stock/system recovery) aborts every single installation file (official rom from the Asus website) without even opening the package, it's like i press 'install update from sd card' then as i press the zip file, it immediately says 'installation aborted' without even typing any other significations/steps, and the same happened for the kernals zip files too. so does that mean my recovery mode is corrupted or something is wrong with it?
3) i noticed some slight changes in my recovery since the last bootloop i had and had to use it back then, for example the dead android screen appearing after choosing the recovery mode, at first it used to say 'no command' under the dead android, but this time it doesn't say anything, just the dead android image only until i press power button and volume up to get the recovery options. so does that mean my firmware version changes since last time or my recovery is corrupted or it just means nothing?
4) is there aNYWAY to know my build number of a phone in bootloop (not rooted but bootloader unlocked)
so my initial problem is; i had my asus zenfone go zc500tg on march 2016. it was working so fine actually (using it like a default user not actually knowing anything about roms/flashing/recovery etc) until july of 2017 when i noticed my phone was a bit slow (out of the ordinary) and it used to get SO hot while using it normally and battery drained pretty faster than before, but i didn't know what to do tbh so i just kind of ignored something was off. but not long after these symptoms, the booting of my phone got slower and slower, until it reached its max by staying more than three hours just doing the 'optimizing apps' on the booting screen until it booted, so i thought it was a virus that would go away after a factory reset, and after the reset, it got worse, until it stopped booting and got into a bootloop. I panicked then because i didn't have the slightest idea what was happening until some internet searching guided me into the world of bootloops and custom roms and recovery. so i eventually managed to fix the bootloop and it worked fine for several months until it started to lag again and boot slowly and got the second bootloop, and that i fixed like the first one by installing the rom from the asus website then putting it on the sd card sand flashing it through recovery,
the third bootloop was quite the same, except that i did something additional in recovery mode, i pressed "backup user data" and that did a nandroid backup then i restored it smoothly after flashing the rom.
the fourth bootloop was a bit different, i as always downloaded the same firmware as the times before and flashed it and backed up user data too, but the odd thing that happened was me getting a message box that won't go away that said "unfortunately, the process com.android.phone has stopped" the phone worked but the sim cards weren't recognized and the message box was coming and going every second, so i noticed that the message box went away (nearly) when i got my sd card out, but still the phone app and the sim cards were corrupted,i thought the issue was from my sd card at first but i eventually, (coincidentally tbh) managed to fix it by doing the OTA update that was due, (that bootloop was fixed on the date of January 13th 2018)
then my phone was working so fine and everything was alright.
then shortly after (january 20th 2018) i was on whatsapp normally then suddenly ALL the things on my phone came crashing in front of me : TONS of endless message boxes saying things like "unfortunately, the process com.(any app on my phone) has stopped"
that i literally panicked and tears welled up in my eyes, so i rebooted the phone and while rebooting it did a (relatively quick) "optimizing apps" but as it booted everything was the dreaded same, all the apps crashing, then with the second rebooting was the current bootloop. i thought it was the same as before and just downloaded the usual zip file i use everytime but while flashing it (it did the same as mentioned in question 2 above) but it aborted instantly so i went and downloaded every rom there but it was the same so i went and tried the kernal zips too but always the same (i can't read my build number through the system recovery because it is like not fitting well in the screen si half the number isn't there that's why i asked question number 4)
so can anyone help me please? i'm in desperate need for help, i'm literally crying while typing this because i can't afford another phone and i'm so scared.

also is there a way to install custom recovery to not rooted device while in bootloop?
or if the system recovery was actually corrupted what do i do? :crying: