Phone dead, help needed! - Milestone 2 Android Development

Hello everyone!
Recently I have installed, Danik's ROM and Kernel on my Milestone 2, but I wanted to flash back the CM11 and the original Kernel. So I went to bootloader mode, and flashed the right sbf, but now the phone is dead... when I plug into computer, the white charge led lights but the screen is black, and Windows doesn't recognise the device.
What should I do, to get back to the roots?
Thanks in advance

rkrisi said:
Hello everyone!
Recently I have installed, Danik's ROM and Kernel on my Milestone 2, but I wanted to flash back the CM11 and the original Kernel. So I went to bootloader mode, and flashed the right sbf, but now the phone is dead... when I plug into computer, the white charge led lights but the screen is black, and Windows doesn't recognise the device.
What should I do, to get back to the roots?
Thanks in advance
Click to expand...
Click to collapse
factory reset your phone with stock recovery
-turn off your phone
-Hold button key X on keyboard with power key

Hello,
in case of big troubles, follow precisely in each step this guide: http://forum.xda-developers.com/showthread.php?t=1032372
to find RDSlite use google to avoid any driver/permission problem, if you can, use an old Win XP computer or a virtual machine.. let us know if it works..

thanks for the replies, I always use XP for flashing, because Win 8.1 isn't supported. Now the only problem is, that windows doesn't recognise the phone, I think the battery is too low, now I am trying to charge it up with an external charger... Anyway someone know what to do if I used Danik's kernel and I want the original back? I don't have to flash some kernel sbf or something like that before flashing the original rom with rsd lite?

Now if I connect the phone to the PC it recognises, but the screen is black. If I start flashing it with the right sbf, the phone screen shows the SW Update In progress screen, and when the flashing complete, the phone reboots, but always gets back to Bootloader mode with black screen

I think I have this BL version problem, because before bricking my phone the original rom was 2.2 AsiaRetail.. What should I try, I dont know what bootloader version installed last, but I read that this problem is caused when trying to flash a rom with an older bootloader than installed

rkrisi said:
I think I have this BL version problem, because before bricking my phone the original rom was 2.2 AsiaRetail.. What should I try, I dont know what bootloader version installed last, but I read that this problem is caused when trying to flash a rom with an older bootloader than installed
Click to expand...
Click to collapse
Did you try one of these ?
http://sbf.droid-developers.org/phone.php?device=29

rkrisi said:
I think I have this BL version problem, because before bricking my phone the original rom was 2.2 AsiaRetail.. What should I try, I dont know what bootloader version installed last, but I read that this problem is caused when trying to flash a rom with an older bootloader than installed
Click to expand...
Click to collapse
hello, sorry for the late reply.. I hope I have understood your problem but if I'm wrong, tell me.. well, I always kept my MS2 to the first *.sbf version (froyo) to avoid problems but in your case, you may try using the latest *sbf (the gingerbread one) and then upgrade to the rom you want.. or, if you have upgraded you can try the downgrade procedure: http://forum.xda-developers.com/showthread.php?t=1497263
or, I have found this: http://forum.xda-developers.com/showthread.php?t=1236296 have a read, it may be usefull..

Related

[Q] Reverting X10 mini pro back to stock help

I have tried to look through the numerous threads but still dont seem to beable to find the answer to my question, I bought a x10 mini pro from someone and it has cyanogenmod 7 v005 on it but i want to revert it back to stock.As i bought this with cyanogenmod already on it i dont have the stock rom. I have checked and it does have xrecovery installed so can i just find a stock rom and install it using xrecovery or do i need another custom rom. If anyone can point me to the right thread (i know there prob is one and ive missed it) or to the stock rom? It would be greatly appreciated. TIA.
anyone able to help??
so am i stuck on this custom rom?
if you find a stock rom that is in a format that the recovery mode can use, yes.
if not you will probably have to use a flash program like odin and flash the stock rom that way.
argggh i got impatient waiting for a response and read elsewhere using pc companion to restore would work and now stuck in SE logo loop, is it now bricked? or is there a solution ???
Dark3n said:
if you find a stock rom that is in a format that the recovery mode can use, yes.
if not you will probably have to use a flash program like odin and flash the stock rom that way.
Click to expand...
Click to collapse
thanks for that odin never heard of it b4 but it worked a charm
big thanks ....
fatc2k3 said:
thanks for that odin never heard of it b4 but it worked a charm
big thanks ....
Click to expand...
Click to collapse
Sure thing, always happy to help .
If you still have download mode or something similar it is not fully bricked.
On the sgs you can even make a custom usb plug to get it into flash mode when your download mode is broken, it just takes more expertise to get it working again the more you brick it .
**SOLVED**
I did a repair in PC Companion, and that gave me stock ROM - but I didn't get the correct hardwarekeyboard...
And I lost Root I guess, so I can't replace/change the keyprint.xml file.
xRecovery seems to be gone, but what about JIT(what is that?)?
I want to be all stock due to warranty.
Oh, and how should I format my sd card?! I have an ext3 and a fat32 partition now, to support apps2sd, but dont want that. should i just format whole card to fat32?
Not sure about the SD card. However I would first backup any data/files on the SD card before trying anything.
Regarding JIT, it basically boots the performance of your phone, its related to Android's software compiler.
I think Android versions 2.2 & above already have JIT enabled, however to have this on version 2.1 you may need to root the device.
Dark3n said:
if you find a stock rom that is in a format that the recovery mode can use, yes.
if not you will probably have to use a flash program like odin and flash the stock rom that way.
Click to expand...
Click to collapse
Heyy!! I tried Graphical flash software.. but it wont detect my phone when i connect it while holding the <-- (back) button.. Can u kindly post a link to ODin for x10 mini pro.. and is there any video on youtube that shows how to do it??
I must have the Stock ROM for the U20i in German, Can youre help???

[Q] can not go in download mode

Hi,
folow problem:
i made the upgrade from 2.2 to 2.3 and found out that there are some apps, language (German), try to downgrade to 2.2 since this was done (for 3Weeks) i can not use the phone because it shows AT&T when i push the power button, when i plug in the usb it shows just the charging symbol. Itry the 3 button reset nothing changed.
Yesterday i spend the hall day to find out is this a waranty case or not ?
Futureshop where i boughtthe phone said as long the phone is not running or show the ROGERS screen they can do nothing ???!!! Costumersupport - no comment.
At Rogers plus they said they have to send it in because its on a Rogers contract.
I tried the reset method with the Roger customer service the same result nothing changed. Just the AT&T screen.
My question is what else can i do to get the phone back so that it works befor i did this update.
I don`t no what downgrate it was, the only thing i know it was the update from samsung kies.
Have u any solutions ?
THX n Regards
Cooper21
Sounds like you have a soft-brick. You have to either buy a jig ( Which you can find here: http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-download-mode-jig/ ) Or follow this guide: http://forum.xda-developers.com/showthread.php?t=889128 Use either one of these to get into download mode, and flash back to stock with odin.
try using JIG to get it into download mode and do a reset with ODIN
Cooper21 said:
Hi,
folow problem:
i made the upgrade from 2.2 to 2.3 and found out that there are some apps, language (German), try to downgrade to 2.2 since this was done (for 3Weeks) i can not use the phone because it shows AT&T when i push the power button, when i plug in the usb it shows just the charging symbol. Itry the 3 button reset nothing changed.
Yesterday i spend the hall day to find out is this a waranty case or not ?
Futureshop where i boughtthe phone said as long the phone is not running or show the ROGERS screen they can do nothing ???!!! Costumersupport - no comment.
At Rogers plus they said they have to send it in because its on a Rogers contract.
I tried the reset method with the Roger customer service the same result nothing changed. Just the AT&T screen.
My question is what else can i do to get the phone back so that it works befor i did this update.
I don`t no what downgrate it was, the only thing i know it was the update from samsung kies.
Have u any solutions ?
THX n Regards
Cooper21
Click to expand...
Click to collapse
This is not a soft brick............don't panic. This is a kernel mismatch or bootloader problem. DON"T USE KIES FOR ANYTHING...except if you really want to brick you phone. I hate that program (my personal opinnion!!).
Have you tried the button combos to go to download?
see this link for some http://samsungcaptivate.wikia.com/wiki/Putting_the_Phone_into_Download_Mode
or google "Captivate Download Mode".
CHECK YOUR USB DRIVER VERSION. http://www.capfaq.com/w/USB_drivers Use the link to Samsung (click on "Software" blue link on top).....works best with Win XP, WIn Vista. You can also use 32-bit or 64-bit driver but see next comment IF YOU ARE ON WIN 7.
ALSO, DONT USE WINDOWS 7 64-bit, unless you have to. My opinion again............but a lot of experience behind it. The USB drivers are for 32-bit and is in my opinion flaky. If you can use Win XP then great, otherwise go with Win 7 32-bit. Even Win Vista is good.
THEN USE ODIN.
YOU HAVE TO FLASH THE STOCK 2.1 I897UCJF6 from here http://forum.xda-developers.com/showthread.php?t=1300843. The work upwards to 2.3. It is better to flash JF6 since I do not know what bootloaders are there on you phone.
.........if you can get download, then post back if you do not know how to get stock. There is always a chance of bricking your phone during flashing, but it is slim.
chappatti said:
This is not a soft brick............don't panic. This is a kernel mismatch or bootloader problem. DON"T USE KIES FOR ANYTHING...except if you really want to brick you phone. I hate that program (my personal opinnion!!).
Have you tried the button combos to go to download?
see this link for some http://samsungcaptivate.wikia.com/wiki/Putting_the_Phone_into_Download_Mode
or google "Captivate Download Mode".
CHECK YOUR USB DRIVER VERSION. http://www.capfaq.com/w/USB_drivers Use the link to Samsung (click on "Software" blue link on top).....works best with Win XP, WIn Vista. You can also use 32-bit or 64-bit driver but see next comment IF YOU ARE ON WIN 7.
ALSO, DONT USE WINDOWS 7 64-bit, unless you have to. My opinion again............but a lot of experience behind it. The USB drivers are for 32-bit and is in my opinion flaky. If you can use Win XP then great, otherwise go with Win 7 32-bit. Even Win Vista is good.
THEN USE ODIN.
YOU HAVE TO FLASH THE STOCK 2.1 I897UCJF6 from here http://forum.xda-developers.com/showthread.php?t=1300843. The work upwards to 2.3. It is better to flash JF6 since I do not know what bootloaders are there on you phone.
.........if you can get download, then post back if you do not know how to get stock. There is always a chance of bricking your phone during flashing, but it is slim.
Click to expand...
Click to collapse
I must disagree with your recommendation for jf6. I would recommend KB1 or KB2. They are both available in the development section.
mrhaley30705 said:
I must disagree with your recommendation for jf6. I would recommend KB1 or KB2. They are both available in the development section.
Click to expand...
Click to collapse
Agreed. But his 'case hsitory' is murky. In fact, I actually first posted KB1 then changed to JF6, since though he says 2.2 who knows what state his phone's in. He may also be stuck somehwere in between on 2.3, where GB bootloaders may or may not be on. JF6 without bootloaders would be safest.
At this point, it looks as if he should start over. Completely start over. With bootloaders. Yes I know the danger involved in flashing bootloaders, but in this state it may be the only choice. Attempting to use jf6 w/out bootloaders could result in another boot loop. Their is the option of using Heimdall to flash kb1, taking out the bootloaders before flashing.
mrhaley30705 said:
At this point, it looks as if he should start over. Completely start over. With bootloaders. Yes I know the danger involved in flashing bootloaders, but in this state it may be the only choice. Attempting to use jf6 w/out bootloaders could result in another boot loop. Their is the option of using Heimdall to flash kb1, taking out the bootloaders before flashing.
Click to expand...
Click to collapse
Yes fully agree.
hi,
1 thx for the help n support but i have no experience how this all work.
2 i send it in after phone caal with rogers tech support, they try to fix it, when its not fixable i geet a new phone.
3 when i get a new one maybee i have to downgrade it.
King regards
Cooper21

[Q] Samsum Galaxy Fit No Boot

Greetings.
It doesn´t boot.
First details:
Galaxy Fit rooted and 2.3.4 Gingerbread (worked fine)
I downloaded rom-manager and wanted to change to custom roms.
So far.
As I tried to install clockwork I found this in your forum:
http://forum.xda-developers.com/showthread.php?t=1339640
and did everything exactly written there
then restartet, started rom-manager and chose the first option (Clockworkthingy).
As there was a choice of the device, I didn´t find my device and chose the last in list (which did´t work and then I picked the first in list and accepted.
downloaded syanogen 7.0 and after download and backup-chose it told me it would reset and start in recovery ... that was the last I´ve seen from my galaxy ...
Is it broken now.
Please help!
note: tried to start recovery with vol+, home and power as well as usual way to start it. without success
Come on. Some of you Guys are able for sure to tell me, if it is hopeless or there IS something I can do to get it working again.
I know nearly nothing about Smartphones and stuff so
Please!
Rodsengard said:
Come on. Some of you Guys are able for sure to tell me, if it is hopeless or there IS something I can do to get it working again.
Please!
Click to expand...
Click to collapse
Sorry to say that your phone is bricked.
First, rom manager doesn't support your device.
Second, you are an idiot that you selected unknown device from list to make it work.
Third, the thread doesn't have any tutorial about rom manager it is CWM that is meant to be flashed using odin.
Fourth, I probably this is hard brick and nothing can be done.
IN MY VIEW GO TO THE SAMSUNG SERVICE CENTER AND TELL THEM THAT YOU LEFT YOUR FOR CHARGING OVERNIGHT AND ITS NOT BOOTING.
THEY WILL SURELY HELP FOR FREE AS THEY DON'T KNOW WHAT YOU DID AND THIS IS AN APPROPRIATE REASON.
Thank you for your honesty.
Your phone still can be fix up. Your phone not brick yet.. Your phone might get bricked if it running out of battery during flashing, like a half way flashing, then you are in the worse case scenario.
Recovery mode unavailable? Forget about recovery since it has been.broken. What important now is to get access to download mode by pressing vol down + power + home key. If you can access download mode, then your phone can be fixed in 5min.
Read this, before you go any further, if you sure that you already successfully flashed any rom before it went brick. Just do this simple step, for cm7, u need siyah kernel, go download (siyah 2.1.1 .tar)... Not .zip.
Remove your battery then put it back, get into download mode then flash siyah 2.1.1 with Odin 1.85.if your phone already flashed cyanogenmod7, then your phone should boot up and work properly.
If it doesnt work, click the link on my signature, follow all steps provided tp get back your to work as stock. Then start flashing again.
Ps : dont use backup, dont use romanager.
Sent from my GT-I9100 using xda premium
My guide is for SGS2 International. Not ATNT, please find stock rom for your phone version. But the flashing method are just the same..
Sent from my GT-I9100 using xda premium
Thank you for your efforts neobirdrio, but as I wrote above, nothing works.
No combination with vol+ or - and the 2 other HW-Keys.
But if we are still in Topic, what exactly do I have to do with an intact Galaxy fit to flash it to a custom ROM.
What Custom ROMS would run with it?
Where Do I get the Newest Version?
And is it worth changing it?
I wanted something special, something faster than Gingerbread and (of course the original Froyo on it), including something needs less Space.
Could you advice me?
(I ordered a new one swince it happened)
Try read this post,
http://forum.xda-developers.com/showthread.php?t=1120880
Latest stock firmware for galaxy fix is 2.3..which is gingerbread.
Sent from my GT-I9100 using xda premium
Still trying this out.
Did it in this way press three Keys, push batery in and so on ... One time on my netbook it came to life by meaning system told me, that it installs driver (seemed to be recognized right) and ODIN told, there is a connection. I started ODIN (which was prepared to do Gingerbread onto it) But it did nothing. I am not sure if I startet Odin with Adminrights, soooo ... Do now backup of the partition, put a much earlier backup on my PC and try it again (I am running out of PCs, so I simulate, that this is a new Computer )
I keep you informed.
Thanks again so far.
Tried it again, but it didn´come back to life
So Thanks to all ppl helped me.

[Q] Motorola Defy default restore

Hello, I have a Motorola Defy which i have rooted and installed clockworkmod on it. I tried to install Cyanogen mod 7.1 from the website. The phone got to the boot screen where it continued to cycle through it thing and nothing more. I restarted the phone and now it gets stuck at the first screen where its says "google". I tried to enter recovery again (power + volume down) and clockworkmod is completely gone. I want to go back to the stock OS so it atleast works again. Ive tried using the update.zip option in the stock recovery mode but I keep getting an error "failed to verify whole-file signature" when using a signed copy of cyanogen mod. I also tried putting my backup in a zip with the same error. Ive even tried formatting my sd card. What do i do?
I was more or less where you are around June or so. I'm no expert by any means, but perhaps I can help. If memory serves I used a program called RSD Lite to flash it back to the stock unlocked rom I got from the "bl7 finally rooted" thread - if you unlocked a different way, I'd try to find your original rom.
Once you get to where you understand how to get back to stock it makes the whole thing a lot less scary, or it did for me. Once you get back up and running, try flashing Whiterabbit. I didn't have luck getting anything else to run, but that one worked the first time I tried it, and I'm very happy I persevered. Miles better than the stock OS.
Marvelicious75 said:
I was more or less where you are around June or so. I'm no expert by any means, but perhaps I can help. If memory serves I used a program called RSD Lite to flash it back to the stock unlocked rom I got from the "bl7 finally rooted" thread - if you unlocked a dirrerent way, I'd try to find your original rom.
Once you get to where you understand how to get back to stock it makes the whole thing a lot less scary, or it did for me. Once you get back up and running, try flashing Whiterabbit. I didn't have luck getting anything else to run, but that one worked the first time I tried it, and I'm very happy I persevered. Miles better than the stock OS.
Click to expand...
Click to collapse
I cant use the program as my phone doesnt get detected when connected to my pc.
OK, lets start with the basics, if I can remember it right... Have you used RSD Lite successfully before this? Drivers installed? Using bootloader mode? If any of this is unfamiliar go hit the beginner's thread - if you have done all this you may be beyond my help and in need of someone a bit more experienced.
Marvelicious75 said:
OK, lets start with the basics, if I can remember it right... Have you used RSD Lite successfully before this? Drivers installed? Using bootloader mode? If any of this is unfamiliar go hit the beginner's thread - if you have done all this you may be beyond my help and in need of someone a bit more experienced.
Click to expand...
Click to collapse
I fixed it, there were a different set of buttons to hold to get into boot loader. The default recovery was not over written as i thought (happened to all my other phones). Thank you very much for you help. It has been very much appreciated.
Glad to hear it.

Need help! Touch Screen not working.

I unlocked my bootloader and flashed boot.img with Magisk and patched, however now after rebooting my touchscreen no longer works and I cant access my phone.
Its basically a brick unless I can somehow undo this, but I cant find any instructions on flashing back to the stock firmware
If anyone could help I would really thank you.
It seems most phones shipping with android 10 lose touch response in TWRP. Yes you don't have TWRP but I think you're seeing the same behavior.
Plug in a USB c mouse and navigate with that should help you restore normal use.
try this thread https://forum.xda-developers.com/t/stock-rom-for-motorola-g-stylus-retail.4104451/
tatsunn said:
I unlocked my bootloader and flashed boot.img with Magisk and patched, however now after rebooting my touchscreen no longer works and I cant access my phone.
Its basically a brick unless I can somehow undo this, but I cant find any instructions on flashing back to the stock firmware
If anyone could help I would really thank you.
Click to expand...
Click to collapse
Where did you get the boot.img? The non functional touch screen usually means the ROM version the boot.img came from doesn't match the version of the ROM running on the phone.
EDIT - Whoops, didn't notice the age of the post. Didn't mean to bring this back from the dead.

Categories

Resources