I've been teaching my girl about the whole rooting and running other roms thing. I've been messing with Android Devices for a while, But never messed with a G1, I currently own a DINC and GS.
she got it rooted and running the newest CWM. But we hit a snag getting any sort of custom rom working. One of the roms required the DangerSPL... lol since that, it will not pass the G1 screen and will not boot into Recovery.
I need help getting this phone back. Any thing anyone can think of?
Did you try flashing the proper radio first?
One of my Schnauzers posted this.
We followed all instructions given, Radio, SPL, and Rom. I made sure she followed the instructions given by the dev that made the specific roms.
The problem is still the same. only the G1Logo, No Recovery or Bootloader starts. You attempt to, and just that logo pops up.
lol stupid "how to fix your bricked g1" threads, every single one of them can easily get into the boot loader or recovery and they call it bricked.
Android G1 mobile software required (urgent)
hi,
My mobile set does not proceed after G1 logo. I need mobile software and method to do that.
i shall be grateful.
Regards,
Khurram
khurramsarwar, Press and hold the Camera Button and while holding, press the power. What happens? Try Home+Power. What happens?
See a real brick is when these things don't work. Like what I'm trying to fix.
You have a lovely new paperweight.
Your only option is the following...
http://forum.xda-developers.com/showthread.php?t=591048
Yeah I know. I told her to get another, we have already found like 3 or 4 for around 25 bucks! Just waiting for her to get it so I can do it right this time. I told her to be patient and wait for me to do it. But she is anything but.
So buy four G1's for a cool hundo...and split them. Let her do two and you do two. I'm sure she's capable of a second chance alone. If she wants it...shell get it.
I have DEFY(Green Lens).If i flash stock DEFY+ rom on DEFY, what issues will i face other than camera and battery issues. Will i be able to flash froyo sbf again and go back to froyo.
if you flash defy+rom your camera wont work. and do not use sbf.it will update the bl version and it will be difficult to go back to 2.2
Sent from my MB525 using xda premium
Battery wont be recognised and you won't be able to charge the device unless you flash a patch.
Sent not from your device!
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Don't flash Defy+ sbf on Defy. It will become a mess. You can't downgrade is not that easy so don't try.
What if that has been done? And why the phone reboots when cold?
Greetings,
I am about to start a new question before I catch this thread, so I write a reply. If the admin thinks this should be a new thread, please do appropriate operation.
This is my situation: My phone is given by others, and I don't know much about its history. Upon receiving it has been flashed a system (not original) which says (I write down from the "about phone" info menu):
System version
45.3.109.ME525+.ChinaRetail.cn.CN
Model
ME525+
Android version
2.3.6
Baseband version
EPU93_U_00.60.00
Kernel version
2.6.32.9-ga28fcc4
[email protected] #1
Internel verion number
4.5.3-109_DPP-11_WSL
So it seems to be a Defy+. But, after studied information from internet including this forum, I think it's actually a Defy:
1, On a label inside the box it says MB525;
2, The battery is 1500mAh instead of 1650mAh;
And, my camera lens looks green. Using method from http://forum.xda-developers.com/showthread.php?t=1116694 , "Detected SOC device" appeared. The ROM has been rooted when using ADB.
Though unlike the previous replies of this thread said, camera and battery is OK, The phone has a very BIG problem: it reboots when cold. When the temperature is under 15℃ or so, it will reboot. The reboot process seems raised some heat, and after temperature is down it reboots again, until the battery is drained out. If it is really cold, the phone will reboot continuously and never get into system.
I think maybe it has something to do with the modified ROM, So after studying the beginner's guide of http://forum.xda-developers.com/showthread.php?t=1216982, I flashed a stock ROM from http://sbf.droid-developers.org/umts_jordan/list.php, which, as it should be, get my phone "fake bricked " (dark screen when boots). I realized that because the phone has been flashed a defy+ ROM, with the BL=5, I cannot flash any stock ROM listed in that page. So in a haste I flashed a ME525+ ROM again from another site (claiming this is an stock ROM), which says ME525+, Android 2.3.4, 4.5.3-109_DPP-6, and the phone can boot now, but the reboot-when-cold problem persists, besides the camera is useless.
I appreciate that you read my lengthy description. So my question is:
1, Is this reboot-when-cold problem related to the ROM? or, can the problem be fixed (without sending back to moto-factory, for it's long out of the warranty)?
2, If the reboot-when-cold problem can not be fixed, Which ROM should I flash now?
luweitest said:
Greetings,
I am about to start a new question before I catch this thread, so I write a reply. If the admin thinks this should be a new thread, please do appropriate operation.
This is my situation: My phone is given by others, and I don't know much about its history. Upon receiving it has been flashed a system (not original) which says (I write down from the "about phone" info menu):
System version
45.3.109.ME525+.ChinaRetail.cn.CN
Model
ME525+
Android version
2.3.6
Baseband version
EPU93_U_00.60.00
Kernel version
2.6.32.9-ga28fcc4
[email protected] #1
Internel verion number
4.5.3-109_DPP-11_WSL
So it seems to be a Defy+. But, after studied information from internet including this forum, I think it's actually a Defy:
1, On a label inside the box it says MB525;
2, The battery is 1500mAh instead of 1650mAh;
And, my camera lens looks green. Using method from http://forum.xda-developers.com/showthread.php?t=1116694 , "Detected SOC device" appeared. The ROM has been rooted when using ADB.
Though unlike the previous replies of this thread said, camera and battery is OK, The phone has a very BIG problem: it reboots when cold. When the temperature is under 15℃ or so, it will reboot. The reboot process seems raised some heat, and after temperature is down it reboots again, until the battery is drained out. If it is really cold, the phone will reboot continuously and never get into system.
I think maybe it has something to do with the modified ROM, So after studying the beginner's guide of http://forum.xda-developers.com/showthread.php?t=1216982, I flashed a stock ROM from http://sbf.droid-developers.org/umts_jordan/list.php, which, as it should be, get my phone "fake bricked " (dark screen when boots). I realized that because the phone has been flashed a defy+ ROM, with the BL=5, I cannot flash any stock ROM listed in that page. So in a haste I flashed a ME525+ ROM again from another site (claiming this is an stock ROM), which says ME525+, Android 2.3.4, 4.5.3-109_DPP-6, and the phone can boot now, but the reboot-when-cold problem persists, besides the camera is useless.
I appreciate that you read my lengthy description. So my question is:
1, Is this reboot-when-cold problem related to the ROM? or, can the problem be fixed (without sending back to moto-factory, for it's long out of the warranty)?
2, If the reboot-when-cold problem can not be fixed, Which ROM should I flash now?
Click to expand...
Click to collapse
Try a defy SBF. If it leads to a soft brick then try a defy plus SBF. The camera can be fixed by using only 2ndboot ROMs.
Sent from my MB526 using Tapatalk
hotdog125 said:
Try a defy SBF. If it leads to a soft brick then try a defy plus SBF. The camera can be fixed by using only 2ndboot ROMs.
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
That's what I have done; it seems I have to try those Defy+ SBFs until find a one that suites for Defy.
solved
I struggled through finally. After I flashed CyanogenMod 7 stable, cm-7.2.0-jordan.zip, the phone does not reboot at low temperature again. Before that I flashed a modified BL5 JDGC_2.12.0.sbf from other sites. I can't imagine why other ROMs will cause low temperature rebooting, but anyway the phone now works in winter and I am happy! :victory:
HELP
I apologize for flooding.
Dear doctors, I need your help VERY!
The problem is this: Download Firmware "CM10 (18.11 + fixBlue). Sbf" decided to ask ..
Turned off the phone, turned on while holding the top of the rocker gromkasti through RSD sew phone, at the end of installation, the phone asks him to reboot manually, generally overloaded, nothing should be loaded, worked the battery, the identity thing, then threw this thing, after a while the phone stopped included at connection to a computer white LED lights up, and the sound came from the connection on the PC .. decided to postpone until the phone as he waited for the new display and touch screen, just 3 days before receiving parts, decided to try to flash .. diode zagoraetsya only when connected to fraction of a second, and gave sound on the PC. Now the identity thing, not only delivers sound on the PC .. and not simply vklyuchaetsya (bought a frog, thought battery low, etc., loaded it as it is .. and no results ..
Doctors ask for your help regarding my vostonavleniya Defayki ..
ps Tried different Mutko with USB, battery and buttons, nothing pomaglo (RSD does not see (sorry for the google translate
So I've been out of the game for a while.. I haven't checked the threads since before the offical OTA update.. in fact, i didnt even know it was out until tonight.
I have a rooted Acer A500 running a very early version of thor2002's version of ICS.. It's on a honeycomb bootloader and on an early version of CWM..
I generally am pretty decent about being able to read the dev section and find my answers throughout different threads but I am so totally lost on what I need to do to update to the offical ICS..
From what I'm gathering I need to update the bootloader and then install a rom.. if that's the case, what's the easiest way to update the bootloader? at that point do all roms work or only offical ICS roms? Sorry for the noob questions.. I've missed a few months and for some reason this is totaly jibberish to me.
Powell730 said:
From what I'm gathering I need to update the bootloader and then install a rom.. if that's the case, what's the easiest way to update the bootloader? at that point do all roms work or only offical ICS roms?
Click to expand...
Click to collapse
I used Civato's guide here and went the manual way on three a500s so far. It is very easy, but a bit frightening until you've done it once or twice. APX mode is a pain to do manually, but there's a tool by blackthund3r included in the guide that is supposed to help if the manual method doesn't work for you. I have had great luck getting into APX by holding reset press and hold power for (exactly it seems) 3 seconds, then one more second before you release the reset button. Also blackthund3r posted in a different guide that he holds reset, then the power button until the power light comes on. Release the power button as soon as you see the light. One second more then release the reset. Also when it goes into APX the screen is blank and the power light is on.
From what I understand you can flash just about any rom that is using the ICS bootloader. Honeycomb stuff will mess you up... So none of that after the V4 bootloader. There are many smarter people here that can give you a better and more accurate explaination about the specifics than I can. But that should be pretty close.
I'm usually very resourceful; search, read, and try to resolve my own issues with the many threads online and here on xda but I am at a complete loss at this point and hope one of you can give me some guidance.
I have a Tmobile US Defy. Green Lens. I was able to root and install cwm. It was on Android 2.2.1.
I wanted to make sure everything was ok prior to beginning to flash anything so i downloaded JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.0R_JORDANTMO_P022_HWp3_Service1FF.sbf
This obviously reverted my Android to 2.1 but upon completely booting it begins to slow to a freeze on my homescreen within a minute or two.Completely freezes. It did not prompt me to enter Blur account and if there isn't a SIM in, it will not allow me to interact with the phone beyond emergency calling. I can't update through OTA since it just locks up.
Thought I'd try to wipe/reset. I'm able to get to the android guy with the exclamation point but pressing vol up/down does not get me into recovery. I've tried many button variations as well.
I'm not sure what I need to do at this point anymore. I can enter bootloader (v9.10) still and use RSD but I'm afraid to flash non US sbf files.
Any help would be greatly appreciated. I apologize if this has already been covered. I've been searching and reading for the last 6 hours and have no idea what to do next.
If you under 2.1 and you are on the screen with the android guy have you touched the screen above the magnifier.
Much Appreciated
RATTAR said:
If you under 2.1 and you are on the screen with the android guy have you touched the screen above the magnifier.
Click to expand...
Click to collapse
I did not do that. Thank you! Sorry for such a ridiculous/pointless [Q]. I spent hours reading and never ran across such a simple solution. Everything was smooth sailing after that simple suggestion on your part; tried out a few different ROMs here and there already. Thank you again!
I used 4.1.2 custom ROM before, and surely, It was really smooth and fast. (That is a major characteristic you can find from jelly bean port.)
And I heard that there was another jelly bean update to 4.2.1, so I immediately flashed the rom to my a500. But It was somewhat slow compared to 4.1.2 rom so I decided to WIP and get back to my 4.1.2 rom.
But whenever I try to get into recovery mode, It showed a green android with his stomach open, and next to the android there is an exclamation mark. so I wasn't able to go further on. So I rebooted my tab, and then waited 2 seconds, and then I tried it again, but it failed.
How can I exactly fix this problem? I have already unlocked the bootloader using Blackthud3r's APX flash tool and I already started using that like a month ago, but it happened yesterday.
Any solutions If you know what the problems specifically are?
jlee4923 said:
I used 4.1.2 custom ROM before, and surely, It was really smooth and fast. (That is a major characteristic you can find from jelly bean port.)
And I heard that there was another jelly bean update to 4.2.1, so I immediately flashed the rom to my a500. But It was somewhat slow compared to 4.1.2 rom so I decided to WIP and get back to my 4.1.2 rom.
But whenever I try to get into recovery mode, It showed a green android with his stomach open, and next to the android there is an exclamation mark. so I wasn't able to go further on. So I rebooted my tab, and then waited 2 seconds, and then I tried it again, but it failed.
How can I exactly fix this problem? I have already unlocked the bootloader using Blackthud3r's APX flash tool and I already started using that like a month ago, but it happened yesterday.
Any solutions If you know what the problems specifically are?
Click to expand...
Click to collapse
Sorry dude, I have no answer however for what it's worth, I believe the best bet for you is to look around the bricked messages. I think the Android icon is telling you that there is no image to boot. See this post http://forum.xda-developers.com/showthread.php?t=2093867