Database Develop

I think my G1 is bricked.... but.. maybe you can help

I Rooted my G1 everything went fine....... then I updated to a CM with out flashing using Telenet........ now my G1 is stuck at the G1 screen.... any ideas?

YoungOP said:
I Rooted my G1 everything went fine....... then I updated to a CM with out flashing using Telenet........ now my G1 is stuck at the G1 screen.... any ideas?
Click to expand...
Click to collapse
Can you get to the Recovery by taking out the battery, then holding home+power? If so, put the update on the root of your SD, go to the Recovery, wipe, then update. Let me know what happens.

The only ways to brick a phone is to interupt a flash, or flashing the SPL before the radio. If you can enter recovery or fastboot you can recover the device. But we need more information in order to help you with your specific problem.

BlackElvis79 said:
Can you get to the Recovery by taking out the battery, then holding home+power? If so, put the update on the root of your SD, go to the Recovery, wipe, then update. Let me know what happens.
Click to expand...
Click to collapse
That worked... so im fine for now.... but im going to take another shot using this guide this time....http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod

nevermind
..........

[Q] Recovery not working and additional problems

Hi guys,
I have a few problems with my Motorola Milestone.
1. I can't get in to recovery. I only get an black screen (backlight is on)
2. I don't get any video in the bootloader. but RSD lite does recognizes it, and is able to flash it. When it's flashing I do get video only stating that there is software update busy.
3. When I boot up my phone I don’t get, a Motorola logo, but just a black screen (back light on) followed by the Android logo after a few minutes.
4. If I try to wake up the phone, the screen remains black, but the hardware keys to light up, I have to press the lock button multiple times to activate the screen. - Note when the screen remains black, it is responsive and I can unlock the phone, but it still remains black. And sometimes the colors are inverted, but when i make a screen of it with Screen Grabber (shoot me) it's in normal colors.
That kind of sums it up.
I have tried a few things to fix it. I have:
1. Cleared caches, and personal data
2. Flashed a different SBF en recovery
And since I can’t get in to recovery, I had to get Root via Z4 Root method and it works fine.
Afterwards I downloaden Rom-manger, and installed the ClockWork recovery, and tried to boot in Recovery via clockwork, but that didn’t work either. I also can’t get in to Recovery via a cold boot
I think the problems started when I was using CyanogenMod 7 RC4. It worked just fine, but after I installed it I couldn't get in to recovery.
Can I try something else to fix it? or should I flash it back to original state and RMA it?
Edit some additional information:
Frimware: 2.2.1
Frimware configuration: GAS_EMEA_UCAMS1FRYOQWRTEU_P005
Baseband version: 3GSMPU91A_U_91.09.00I
Baseband configuratuin version:UCALHLSMR2EMEAB1B806E.0R
Kernel Versuin: 2.6.32.9-ge635aa4 [email protected]#1
Build Number: SHOLS_U2_05.06.0
And is it possible to restore the orginal boot animation, without recovery?
TL.DR: Motorola Milestone --> CyanogenMod 7 RC4 --> no recovery & no video @ bootloader, plus additinal video problems --> back to orginal --> same problems.

BUMP: is there anyone with a possible soulution?

ClockWork recovery doesn't work on milestone.
So CM7 does boot up?

zeppelinrox said:
ClockWork recovery doesn't work on milestone.
So CM7 does boot up?
Click to expand...
Click to collapse
CM7 doesn't anymore as I removed it, and flashed a different SBF and recovery.
CyanogenMod 7 RC4 worked fine but I had a few video problems, and I could get in to recovery.
I will flash a different recovery tonight and try it out.

Only use androidiani open recovery
Sent from my Milestone using Tapatalk

zeppelinrox said:
Only use androidiani open recovery
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
Flashed a different .sbf and placed the androidiani open recovery files on the Sd card root, but i still can't get in to recovery. I won't even get the /!\ screen. The phone does turn on, but will only get a black screen.

Which sbf?
Sent from my Milestone using Tapatalk

UK SHOLS_U2_02.36.0
I think I bricked it, I'm going to try to restore it or buy a new phone... >.<

BloemBlaster said:
UK SHOLS_U2_02.36.0
I think I bricked it, I'm going to try to restore it or buy a new phone... >.<
Click to expand...
Click to collapse
I don't think you bricked it... but damaged it in some way.
Could also be some hardware related stuff in the end.
Anyway try to wipe everything, that could be wiped.
Start into bootloader and try to install G.O.T. 2.2.1 using RSD again.
This one got the vulnerable recovery already integrated.
Then try to use the specific G.O.T. OpenRecovery on your sdcard to check system integrity.
Please try to take care of every single step and check out what happens....
If your hardware is doing fine, i'm pretty sure that you will get a working phone again.
P.S.: How about your bootloader version?
Good luck,
scholbert

scholbert said:
I don't think you bricked it... but damaged it in some way.
Could also be some hardware related stuff in the end.
Anyway try to wipe everything, that could be wiped.
Start into bootloader and try to install G.O.T. 2.2.1 using RSD again.
This one got the vulnerable recovery already integrated.
Then try to use the specific G.O.T. OpenRecovery on your sdcard to check system integrity.
Please try to take care of every single step and check out what happens....
If your hardware is doing fine, i'm pretty sure that you will get a working phone again.
P.S.: How about your bootloader version?
Good luck,
scholbert
Click to expand...
Click to collapse
I think my boatloader is 90.47 I'm not sure as I won't get any video in the boatloader.
I flashed the G.O.T 2.2.1but I can't get in to recovery, there is still no video only a blackscreen.
Is it posible the may have deleted the files for the logo?

BloemBlaster said:
I think my boatloader is 90.47 I'm not sure as I won't get any video in the boatloader.
I flashed the G.O.T 2.2.1but I can't get in to recovery, there is still no video only a blackscreen.
Is it posible the may have deleted the files for the logo?
Click to expand...
Click to collapse
You can try upgrading your bootloader to 90.78 from here.
Then try flashing GOT 2.2.1, then see if AOR boots up.

sileshn said:
You can try upgrading your bootloader to 90.78 from here.
Then try flashing GOT 2.2.1, then see if AOR boots up.
Click to expand...
Click to collapse
I flashed 90.78, and then reflashed GOT 2.2.1, but is still can't get into te recovery. I getting the same result, no motorola logo and a black screen with no /!\ logo

If your phone is recognised in adb, then you can use the link below to get into AOR directly. Just make sure you have AOR extracted to your sdcard.
http://forum.xda-developers.com/showthread.php?t=625950
Check the commands in the last post and enter them in order.

I was just looking at QtADB for somebody else's problem but it looks like you can use QtADB to boot recovery if the phone is recognized.
http://qtadb.wordpress.com/features/

Hi guys,
sorry for the late reply, but I'm also moving at the moment.
I have tired numerous things.
If I flash the 2.2.1 Firmware SHOLS_U2_05.26, I can get to the recovery selection screen, with the /!\ screen.
But if apply update.zip I will get an error message, stating "EOCD marker occurs after start of EOCD E:signature verification failed", something like that, I don't know the specific message out of my head
And if I flash a vurnable recovery only sbf, with the SHOLS_U2_05.26 I can't get the recovery screen, only a black screen.
zeppelinrox said:
I was just looking at QtADB for somebody else's problem but it looks like you can use QtADB to boot recovery if the phone is recognized.
http://qtadb.wordpress.com/features/
Click to expand...
Click to collapse
I will try thiss when I get home.
sileshn said:
If your phone is recognised in adb, then you can use the link below to get into AOR directly. Just make sure you have AOR extracted to your sdcard.
http://forum.xda-developers.com/showthread.php?t=625950
Check the commands in the last post and enter them in order.
Click to expand...
Click to collapse
I will try this if zepplelinrox method fails becaus I don't have any experince with adb. But the phone is recognised.

...........strange....
BloemBlaster said:
If I flash the 2.2.1 Firmware SHOLS_U2_05.26, I can get to the recovery selection screen, with the /!\ screen.
But if apply update.zip I will get an error message, stating "EOCD marker occurs after start of EOCD E:signature verification failed", something like that, I don't know the specific message out of my head
Click to expand...
Click to collapse
This is standard error, if vulnerable recovery is not installed and you try to start OpenRecovery.
BloemBlaster said:
And if I flash a vurnable recovery only sbf, with the SHOLS_U2_05.26 I can't get the recovery screen, only a black screen.
Click to expand...
Click to collapse
This is strange behaviour...
My last guess is, that something might be wrong with your vulnerable recovery sbf file (file corruption ???). There should have been some errors during flash...
Anyway, you might grab it here and try again:
http://gitorious.org/droid/openrecovery/blobs/master/zips/SHOLS/vulnerable_recovery.sbf
Good luck!
scholbert

sileshn said:
If your phone is recognised in adb, then you can use the link below to get into AOR directly. Just make sure you have AOR extracted to your sdcard.
http://forum.xda-developers.com/showthread.php?t=625950
Check the commands in the last post and enter them in order.
Click to expand...
Click to collapse
Still trying this, no luck yet. ADB isn't my strongest point
zeppelinrox said:
I was just looking at QtADB for somebody else's problem but it looks like you can use QtADB to boot recovery if the phone is recognized.
http://qtadb.wordpress.com/features/
Click to expand...
Click to collapse
The same goes for you, no luck yet. QtADB, work and it recognise my phone, but i can't any (re)boot commands.
scholbert said:
This is standard error, if vulnerable recovery is not installed and you try to start OpenRecovery.
This is strange behaviour...
My last guess is, that something might be wrong with your vulnerable recovery sbf file (file corruption ???). There should have been some errors during flash...
Anyway, you might grab it here and try again:
http://gitorious.org/droid/openrecovery/blobs/master/zips/SHOLS/vulnerable_recovery.sbf
Good luck!
scholbert
Click to expand...
Click to collapse
I actually have no idea how to download the sbf, form the site you have provided.
nevermind, I found it out . but now if my phone to connect to windows it doesn't recognizes it :S

BloemBlaster said:
but now if my phone to connect to windows it doesn't recognizes it :S
Click to expand...
Click to collapse
Before or after flashing the vulnerable recovery again?
Confusing...
scholbert

scholbert said:
Before or after flashing the vulnerable recovery again?
Confusing...
scholbert
Click to expand...
Click to collapse
Sorry for being confusing, it was after flashing vulnerable recovery, but my I'm flashing with a different system now and it working just fine.
If I try the .sbf you provided RSD gives a error "Failed flashing process. failed flashing process (0x17100);phone connected"

BloemBlaster said:
Sorry for being confusing, it was after flashing vulnerable recovery, but my I'm flashing with a different system now and it working just fine.
Click to expand...
Click to collapse
No problem...
BloemBlaster said:
If I try the .sbf you provided RSD gives a error "Failed flashing process. failed flashing process (0x17100);phone connected"
Click to expand...
Click to collapse
O.K. seems that something went wrong during download grab it here:
http://forum.xda-developers.com/showpost.php?p=13039348&postcount=17
BTW the link points to the OpenRecovery developers git rep... so this file is absolutely save.
Cheers,
scholbert

Unable to reboot in download mode

I find my newly purchased tab 8.9 very laggy with the stock TouchWiz
Before returning it I wanted ti try the Overcome rom to see if it can get any smoother.
I carefully followed there instructions but I am unable to go past the downloading droid. once I validate with the right button volume, the tablet simply reboots.
Does anyone else have this issue?

josibarns said:
I find my newly purchased tab 8.9 very laggy with the stock TouchWiz
Before returning it I wanted ti try the Overcome rom to see if it can get any smoother.
I carefully followed there instructions but I am unable to go past the downloading droid. once I validate with the right button volume, the tablet simply reboots.
Does anyone else have this issue?
Click to expand...
Click to collapse
Let me get this right: you sucessfully flashed Overcome, and want to ODIN but when you try to get in Download Mode, it reboots, is that it? If so, that's the first time I've heard this issue. How are you trying to enter Download Mode?

nirogu325 said:
Let me get this right: you sucessfully flashed Overcome, and want to ODIN but when you try to get in Download Mode, it reboots, is that it? If so, that's the first time I've heard this issue. How are you trying to enter Download Mode?
Click to expand...
Click to collapse
I am still with the Samsung original
I wanted to try the overcome ROM see if the lag disapears.
I am stuck in the first step when I need to flash CWR using Odin. I can't get into the download menu

josibarns said:
I am still with the Samsung original
I wanted to try the overcome ROM see if the lag disapears.
I am stuck in the first step when I need to flash CWR using Odin. I can't get into the download menu
Click to expand...
Click to collapse
I see. The Overcome thread also has the CWM Recovery as a .zip file which is flashable through Stock Recovery (same procedure as flashing Root). You just put the file in your internal SDcard and flash away. If you still have doubts, read a little bit here, as I'm sure that will clear any doubts you might have.

josibarns said:
I find my newly purchased tab 8.9 very laggy with the stock TouchWiz
Before returning it I wanted ti try the Overcome rom to see if it can get any smoother.
I carefully followed there instructions but I am unable to go past the downloading droid. once I validate with the right button volume, the tablet simply reboots.
Does anyone else have this issue?
Click to expand...
Click to collapse
u have to press the power and the left-volume button for about 15sec

nirogu325 said:
I see. The Overcome thread also has the CWM Recovery as a .zip file which is flashable through Stock Recovery (same procedure as flashing Root). You just put the file in your internal SDcard and flash away. If you still have doubts, read a little bit here, as I'm sure that will clear any doubts you might have.
Click to expand...
Click to collapse
Perfect it worked! And I was also able to install the Overcome ROM It seems to be more battery hungry and a bit faster
DonKomposto said:
u have to press the power and the left-volume button for about 15sec
Click to expand...
Click to collapse
Yes I have done that and I get to the menu with the droid blinking with "downloading" written under it. The issues is when I validate instead of showing the dowload menue it simply reboots...

josibarns said:
Perfect it worked! And I was also able to install the Overcome ROM It seems to be more battery hungry and a bit faster.
Click to expand...
Click to collapse
Don't expect perfection from a port, ever (port = a ROM that's not native to the device). The motley kernel, along with UV can help you in the battery department.
Sent from my GT-P7310

Sorry to comeback to it but after having flashed a couple or ROM with CWM I want to come back to the stock rom using ODIN and I cannot enter the dowload menu.
My system right now is a stock ROM us retail P7310UEKHA flashed with CWM and CWM and I want to install a 3.2 stock ROM using ODIN.
The way I try to access the download menu is
1. Turn off the tab
2. wait 30 sec
3. restart with the down volume pressed
4. when the reaching the menu between recovery and dowloading. Select dowloading with the down volume button and validate with the up volume button.
Result: a black screen for 3 seconds and then the tab reboots

josibarns said:
Sorry to comeback to it but after having flashed a couple or ROM with CWM I want to come back to the stock rom using ODIN and I cannot enter the dowload menu.
My system right now is a stock ROM us retail P7310UEKHA flashed with CWM and CWM and I want to install a 3.2 stock ROM using ODIN.
The way I try to access the download menu is
1. Turn off the tab
2. wait 30 sec
3. restart with the down volume pressed
4. when the reaching the menu between recovery and dowloading. Select dowloading with the down volume button and validate with the up volume button.
Result: a black screen for 3 seconds and then the tab reboots
Click to expand...
Click to collapse
A corrupt bootloader that may be. Reflash KHA (CWM version alterbridge posted) to see if it solves it.
Sent from my SGH-T959.

Just to precise this issue was present out of the box when I got it from best buy...

josibarns said:
Just to precise this issue was present out of the box when I got it from best buy...
Click to expand...
Click to collapse
flash a stock bootloader and a stock recovery using nvflash, im in a hurry now and dont have time to explain, use google, you will find all the info in the tab 10.1 forum.

lupu666ro said:
flash a stock bootloader and a stock recovery using nvflash, im in a hurry now and dont have time to explain, use google, you will find all the info in the tab 10.1 forum.
Click to expand...
Click to collapse
Thanks lupu666ro. I've tried installing stock Rom with CMW but nothing works. I have found very sparse info about nvflash. It looks like the solution but I'm a bit wary about tring this without a instructions. Could give me more info or point me to a tutorial
Thanks!

Still no luck...
So I have tried reflashing the stock US retail ROM and ran the EULA3 OTA update over it. I can't seem to figure this out.
The OTA update entered the download mode for a few seconds during the update so I am wondering if I don't simply have a locked bootloader.
I have made a video to show the problem: http://youtu.be/b09-x31ldbs

josibarns said:
So I have tried reflashing the stock US retail ROM and ran the EULA3 OTA update over it. I can't seem to figure this out.
The OTA update entered the download mode for a few seconds during the update so I am wondering if I don't simply have a locked bootloader.
I have made a video to show the problem: http://youtu.be/b09-x31ldbs
Click to expand...
Click to collapse
here is a tutorial on how to use nvflash, this will repair you tablet. http://forum.xda-developers.com/showthread.php?t=1130574

On the download warning screen you are hitting volume down, not up. Volume up is the button closest to the headphone jack..
josibarns said:
So I have tried reflashing the stock US retail ROM and ran the EULA3 OTA update over it. I can't seem to figure this out.
The OTA update entered the download mode for a few seconds during the update so I am wondering if I don't simply have a locked bootloader.
I have made a video to show the problem: http://youtu.be/b09-x31ldbs
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I957 using XDA App

neubauej said:
On the download warning screen you are hitting volume down, not up. Volume up is the button closest to the headphone jack..
Click to expand...
Click to collapse
Ok I am really ashamed on this one, you were right I've been hitting the wrong button for all my attempts
Thanks a lot neubauej!!!!!

Lol, no problem, glad it was simple.
Sent from my SAMSUNG-SGH-I777 using XDA App

[Q] Boot loop stock

Hello, folks!
I have a Milestone with stock android (2.1 I guess, after an OTA update from the provider) that was in the drawer for ca. 2 years because the POWER/VOL/CAM flat cable was bad. I changed the cable, was able to boot normally one or twice.
Now the phone freezes with the white motorola symbol.
When I turn it on with PWR + D-pad UP, I get into the bootloader v. 90.73.
Werid thing is that when I try to boot into recovery (PWR + CAMERA), I still get into the bootloader, so I can't get into recovery to try installing another rom to circumbent the boot lock-up.
Ideas to solve this?
Thanks!

It seems like your bootloader is corrupted.
If i were you, i would upgrade it to the latest version (90.78) and try with it.
(Also you should consider using CM7 or even CM10.)

Thanks!
How can I upgrade the bootloader? Is there a zip or an img file somewhere to push?

I dont know exactly, i didnt have to do it before.
I'm pretty sure, you can brick your device with this if something goes wrong.
I think you will need the following:
-Drivers
-RSDLite
-proper SBF file from here
But i dont know if you need to boot into bootloader mode or something.
Please, be very-very careful, maybe you should wait if someone with more knowledge gives you any advice.

Erovia said:
-proper SBF file from here
Click to expand...
Click to collapse
Thanks! I'll try to flash a newer bootloader.

Nope, Didn't work.
Still freezing on boot.

Sorry, but i'm out of ideas.
Maybe someone with more knowledge could help.
Good luck.

Erovia said:
Sorry, but i'm out of ideas.
Maybe someone with more knowledge could help.
Good luck.
Click to expand...
Click to collapse
Well, thanks anyway.

Did you manage to get the Device manage to take the new boot loader via usb?
If it did load the SBL try loading the vulnerable recovery sbf then put open recovery on to your SD card. If you can get that fair then I'd imagine you could load a new OS on to it without much issue. Lots of guides out there.

motorola xt3
motorola xt3 usb diver win xp plz

Full AT&T official FIRMWARE G935AUCS4BRA1 to restore //G935A\\ with January security

Full AT&T official FIRMWARE G935AUCS4BRA1 to restore //G935A\\ with January security
G935AUCS4BRA1
Latest ODIN 3.12.10
Enjoy !!!!

norbarb said:
G935AUCS4BRA1
Latest ODIN 3.12.10
Enjoy !!!!
Click to expand...
Click to collapse
As always, thanks so much.

New BIT 5 version is released ... link needed

aamszia said:
New BIT 5 version is released ... link needed
Click to expand...
Click to collapse
There is no full firmware with Bootloader 5, there not even any of G935 was OTA updated to Bootloader 5 as of yet. . There are only combination files witch you should not flash unless you need to fix your phone. So i'm sorry but you stuck on it.

Can't seem to get it to download... through computer or phone
Edit: I got it.... thanks

norbarb said:
G935AUCS4BRA1
Latest ODIN 3.12.10
Enjoy !!!!
Click to expand...
Click to collapse
Thank you ! Quick question, I currently have 935A with May security firmware fully stock, can I just flash this directly to get latest update ? (I believe this will wipe my phone too)

bestjsg said:
Thank you ! Quick question, I currently have 935A with May security firmware fully stock, can I just flash this directly to get latest update ? (I believe this will wipe my phone too)
Click to expand...
Click to collapse
Yes. You can flash directly and this will wipe data in your phone.
Sent from my SM-N950U using XDA Premium HD app

Stock ATT firmware
Thanks tons, now stuck in a boot loop cannot even turn off. I have tried various ways to get the U version and if I get this back to stock, think I will sell it and buy a U version. Hate carrier proprietary garbage.:good:

nomad247 said:
Thanks tons, now stuck in a boot loop cannot even turn off. I have tried various ways to get the U version and if I get this back to stock, think I will sell it and buy a U version. Hate carrier proprietary garbage.:good:
Click to expand...
Click to collapse
You need to get to recovery and clean cache
Sent from my SM-N950U using XDA Premium HD app

Bootloop
You need to get to recovery and clean cache
Have a ask a really dumb question, How do I get to "clear cache" in recovery? And of course, googled it, just have to charge some. I did achieve root earlier, just trying to get the "U" mod installed. Thanks tons
edit: Did the steps so now I have a blinking message saying recovery booting...

nomad247 said:
You need to get to recovery and clean cache
Have a ask a really dumb question, How do I get to "clear cache" in recovery? And of course, googled it, just have to charge some. I did achieve root earlier, just trying to get the "U" mod installed. Thanks tons
Click to expand...
Click to collapse
Press and hold power, home and volume button up anthill Samsung splash screen. Then let go and for recovery menu to popup.
Sent from my SM-N950U using XDA Premium HD app

Boot loop and maybe bricked
I still cannot get to the cache to clear it.
Here what I have right now.
hold power button, screens goes black then have the first screen of start, S7 edge, it goes off and comes back on
i can get into down load mode, tried reloading the stock firmware but get a write error, model miss-match
if arrow down goes to start up boot loop, if arrow up does into downlaod
power off (does not really shut off)
Vol up + home + power, gets the recovery booting loop
Odin sees the phone, but any writes all seem to fail. Sometimes have to use Odin Prince sometimes 3.12.7
In 12/.6 tried to load the S7 edge qual com image file from rooting, and that said fail in red.
Tried to flash back stock but like I said earlier, says product code miss match
I had tried to use odin to do that update and that probably is what screwed the pooch.
Any ideas?

eror 404 not found broken link very nice...

error 404
can you upload the file again ?

@norbarb you need to take all your links down if you're not going to reupload them.

Boot loop and recovery boot loop
You need to get to recovery and clean cache
ok so, is there a way to fix this with boot lop and recovery in boot loop?
Odin comsy sees the phone but ADB does not... Hoping to get this fixed and working again. Had to buy a phone so using a SM-G930V. At least no more ATT for me....
Anyone???

Here you go guys enjoy.
https://drive.google.com/drive/folders/1aal95ObUmnxdNu33bac0GXosOSRLXD0i

Q: why are the files doble the size of the other updates??
bsharp8 said:
Here you go guys enjoy.
Click to expand...
Click to collapse

Disregard - sorry, didn't see the new link.

Edit: Thanks for the updated files! I'm not sure why it failed the first time, but it worked the second time.