Database Develop

[Q] bricked htc magic 32b?

hey guys, i hope somebody can help me...
i tried to load a new rom to my magic and rooted it. after some flashing i cant get into fastboot or recovery menue. i onle see the "htc magic" screen at my vodafone branded magic.
so is there anybody who can help? - i cant establish a connection via usb too

are you keeping hold of home+back whilst turning the phone on to enter fastboot?

I just posted this for someone on the cyanogenmod forum, hopefully it helps...
I had the same problem the night before last, I was flashing the newest ra revovery through terminal and I believe I made some typos or did not wait long enough and of course I forgot to type su the first couple times... silly me
but after trying a couple times I got it back through terminal.
You can try it through terminal, although theres issues with doing this in cyanogen mod 5.0.7, I'm not sure if the newer roms have the same issues.
but I believe the problem was a few people lost their recovery completely (which obviously wont matter to you) I've done it succsessfully from a donut rom, but havent tryed it from anything higher so I cant promise it will work.
if you want to try:
Open terminal emulator
type: su
hit enter and allow superuser permissions.
type: flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img
(or the name of whatever ra recovery is on your sd card)
hit enter and wait a few minutes just to be sure.
then close terminal and try to reboot into recovery.
if it doesent work the first time check and make sure everything was typed correctly and try again.
Also you can just re-root the phone, that should fix it, its a pain though lol

I just rooted & flashed my Rogers Dream with cm 5.0.8 last weekend and it would freeze on the boot logo (Rogers) and I thought the same thing had happened. I could get to the recovery though.
I realized that you have to install the ROM and the Kernel Patch (I didn't do this) and once I applied the Brian Cook Kernel Patch, the phone booted immediately.
I don't know if this is the same problem you have but hopefully this info will help.
Cheers.

I would try re-rooting if you can. Unlockr . com has kinda an interesting method that might work.
D-

[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.

BIG bootloader problem. Please help!

Hey guys,
Something's gone wrong here and I need some help to fix it.
Basically my milestone always boots to bootloader no matter what i do.
I tried to flash the stock 2.0.1 sbf to put the phone back in it's factory state coming from cm7. RSD completed the flash and said the phone was being rebooted and instead of booting it just went straight to bootloader and RSD gave me the "PASS" notification and it now wont do anything but go straight to bootloader.
I've tried reflashing with RSD with varios sbf files. I've tried flashing just the vulnerable recovery, i've tried all the different versions of the bootloader and i get the same result every time. RSD says the flash has worked and then it just goes right back to bootloader. No "M" logo, no recovery. Nothing.
Any ideas?

http://forum.xda-developers.com/showthread.php?t=1143631&highlight=bootloader+stock&page=2
check last post.
http://forum.xda-developers.com/search.php?searchid=85911831
if the link doesn't work anymore i just searched for bootloader

Are you getting any type of error code when it enters bootloader mode? There should be something if theres a problem, if not, you should at least get to the m logo.
If you dont have any error code, check the keys are stuck (Up on the keypad, also camera and volume up or down (forgot which one!) is used to access bootloader)

i2gh0st said:
http://forum.xda-developers.com/showthread.php?t=1143631&highlight=bootloader+stock&page=2
check last post.
http://forum.xda-developers.com/search.php?searchid=85911831
if the link doesn't work anymore i just searched for bootloader
Click to expand...
Click to collapse
i've already read basically every thread on google about bootloaders, none of them are relelvant because of the next question...
the one thing in that thread i havent tried is using sbf_flash because it's a million tons of hassle but if there are no other suggestions i guess i'll HAVE to do that.
jason600 said:
Are you getting any type of error code when it enters bootloader mode? There should be something if theres a problem, if not, you should at least get to the m logo.
If you dont have any error code, check the keys are stuck (Up on the keypad, also camera and volume up or down (forgot which one!) is used to access bootloader)
Click to expand...
Click to collapse
there is no error code, just the normal ready to program dialogue. i've also verified that there are no stuck keys the painful way (i actually took apart the keyboard and volume button, physically removing the contacts making it impossible for there to be any unwanted connections.
didnt make a difference.

First, flash any froyo (2.2) rom.
Then, take out the battery, then connect to the wall charger (not the PC) without the battery. Put the battery back in if you get the android logo.
I use this method to boot my Milestone when its being problomatic. At the moment, its the only way mine will boot. With mine, I'll get the m logo, then it will panic and reboot. It does this for 5 to 10 minutes, then boots up. Once its booted, everything works fine.
This method 'appears' to bypass some of the checks for normal booting. If I try to boot normally, it will bootloop for hours or until the battery runs out.
You need to flash froyo because when there is a problem, 2.2 kernal panics and tries rebooting. In eclair (2.1) when theres a problem, it just locks at the m logo, so this method wont work.
Also, I dont think flashing with sbf_flash will make a diference, since your not getting any bootloader error messages, the flash is apparently good, something else is causing your problem.
Just to check, you are flashing non-service roms, aren't you? Also try taking out your sim card and sd card, just to make sure they aren't causing problems.

when i plug the phone into AC with no battery, sim or sd after flashing GOT 2.2.1 (non service, full rom) all i get is bootloader with "battery low cannot program". the phone makes no attempt to boot whatsoever.

The only other thing I can suggest is trying sbf_flash.
If you use the command:
Bash sbf_flash -r -f got_froyo.sbf
It will read and display the partition info from the phone. If you get an start_addr mismatch error, your partitions are out of alignment. I haven't found any way to fix that yet.
You can also try:
Bash sbf_flash -r -v
It will give detailed info about your partitions, compare this with the info on the and-developers site.
You can also try flashing the partitions that aren't in the motorola sbf's such as misc, cid, lblbackup:
Bash sbf_flash -r -f --lblbackup lblbackup.img got_froyo.sbf
Someone uploaded all 22 partitions in another bricked milestone thread that was created through adb with the dd command (you'll need to search for it). Use the uncompressed version and flash individually the partitions not in the sbf. There are 4 you cannot flash: mbmbackup, pds, sp and rsv. When you try, it sends the erase command and errors out. Trying this wont brick your milestone any more than it is now. Doing this with the pds partitions seems to erase and recreate it, I had a slightly diferent imei number after I tried this.
Good luck!

Cannot flash any custom recovery - help needed

The problem: Although I was able to do it perfectly before, now for some reason I cannot flash a custom recovery on my K3 Note. I tried doing it according to this tutorial https://forum.xda-developers.com/k3-note/general/sp-flash-tool-tutorial-to-install-twrp-t3346041 and the process looks like it finishes successfully with the Download Ok message, but when I actually boot into recovery it is the still the one from the stock rom (In my case, it just displays the message "Have been in media mode, long press the power button and the [sic] normal boot").
The background: I have been doing a lot of things with my phone, and so unfortunately it's hard to say when exactly the problem started and what caused it. But here is how the story goes:
1. I kept flashing lots of different roms and testing them. Often, I would do this without inserting the sim card, but when I did get to it, it would connect to the network and work fine.
2. When I finally thought I found the perfect rom, I insert my sim and... it won't connect to the network. It is seen by the device and even displays my operator's name and my phone number, but I can't make calls or use data.
3. At first I think it may be a problem in the rom. So I try another similar rom: same thing. I then download another rom I've never tried before, and when I flash that, the phone becomes soft bricked and shows no signs of life.
4. I am able to revive the phone by flashing the stock. But the sim still doesn't work, even though it definitely used to work on this rom before. Already at this point, I replaced the stock recovery.img with the custom one I used. I discover that the sim not connecting is a problem with the IMEI.
5. One apparent solution to the IMEI that I read about was to open Flashtool, go to the Format tab choose Auto Format Flash/Format whole flash except bootloader, check the "Validation" box, and start the formatting process. I do this and then re-flash stock, but the IMEI problem persists.
6. I find instructions online that tell me to root my phone (I used KingRoot for this), install the Engineering Mode app, and enter the correct IMEI using the command AT+EGMR=1,7,”Your IMEI Number”. I try it and it doesn't work. When typing "AT+EGMR..." the error is "This command is not allowed in userbuild", if I type "AT +EGMR...", it becomes AT command is sent: Error".
7. I decide to go back to a pre-rooted rom that has worked quite fine in the past and re-try this procedure from there, and that's where I discover that my custom recovery hasn't installed and would't do so when I tried flashing it again.
So yes, I pretty much have two problems in one here. My priority is to solve the recovery problem, but if someone knows how to fix the IMEI one, please let me know too.

"=> Device lockbroken" message when turning on Moto E4 Plus

My problem goes a little further than that. I flashed the stock ROM back onto my phone after having RROS 5.8.5 for quite some time and all of a sudden now I cannot boot my phone past this message on the Lenovo/Motorola splash screen:
Code:
=>FASTBOOT mode...
=>Device lockbroken
on top of this, I'm sure something has happened to he phone through a possible incorrect/incomplete flashing when trying to get my SP Flash Tools to work like it used to (It worked fine before, but this time SPFT didn't want to work giving me BROM errors and mostly error 6045 - FYI I sorted this out by running CCleaner registry clean a few times).
So now, my phone is stuck on this message and when I enter fastboot mode to try to query the phone with
Code:
fastboot devices
, my serial apparently has changed to 0123456789ABCDEF?!
How do I restore my original serial number and get rid of the "lockbroken" message (is there anything to do with NVRAM? Did I wipe it or something?), so I can get on with unlocking and re-rooting my phone? I've not been able to use my phone for about two weeks when I first wiped the OS and my PC just decided not to let SPFT work properly, so now, I've finally got it to flash the stock ROM back on, the last hurdle now is to get past this lockbroken crap!
Thanks in advance,
(don't be afraid to talk techy - I'm not that bad!)
Nathan

try to roll back like on this link: roll back