Hi,
I tried to change ROM (from default) ad install googleapps my Defy+ and never got to the point where I saw android load up.
During the hole process everything ran 100%.
On the last system reboot nothing happened.
Now all i get on screen is:
Boatloader 0.9.1
battery low
cannot program
I have read many forum threads ans watch many videos but nothing worked.
I installed RDS Lite but am not sure which SBF to donwdload.
Plus, even if I get the correct sbf I never get to the message needed on the phone.
All I ever see is:
Boatloader 0.9.1
battery low
cannot program
Any ideas how to get the phone back to working condition?
Thanks
Related
I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...
Have you tried the 2.2.1 leak? This gives you a new kernel and bootloader.
Stoogie said:
I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...
Click to expand...
Click to collapse
If the phone is not rooted when you take it into the Verizon store then you will be fine. I would ensure that any traces of root have been removed from the SD card (apps that require root, etc). As long as the phone is stock when they see it then it will be fine. I have had to do this several times with roms and root access.
Can't you just SBF it? I'm fairly new to the X but I've had to SBF rescue my D1 and D2 multiple times.
OOOPS didn't read the SBF part...
If it is still hosed after an SBF install I would guess that you have a hardware issue and need to replace the phone.
Stoogie said:
I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...
Click to expand...
Click to collapse
It's a known issue with 2.3.15. gmanapps, the guy that created the hdmi app in the market said it was the video driver not loading up in time because of some code changes Motorola made; but supposedly it's fixed in 2.2.1. I suggest you don't upgrade to 2.2.1 until there is a full sbf.
I get stuck on the "M" logo 7 times out of 10 after every reboot; I just hold the power button down until the pop-up window comes up (of course I can't see it) and guess where the shutdown press is on the screen to power off the phone, and then power on again after a minute or two. This trick usually works.
Check it out here:
https://supportforums.motorola.com/message/256095#256095
Hi,
Ive already looked around the forum but cannot find an answer to my question.
I know my phone is not totally bricked, I understand there are probably ways of plugging it into a PC to force an update but i downloaded the OTA update that popped up on my phone last night. As I understand it is meant to update and keep all of your apps and saved data, which I chose to do instead of wiping anything with a manual update to save all the hassle.
The phone was rooted on froyo 2.2.2 orange uk rom but apart from that there were no other mods to the OS.
The phone came up with the "power off" message and now sticks on the black Motorola screen showing
"Failed to boot 2
starting rsd mode"
I can pull the battery out and the phone turns on for about 20 seconds, and I can use the OS in this time but then the "powering off" message comes back up
and it goes back to the error message on the splash screen.
Is there a way I can stop this OTA update from powering off my phone and getting stuck in this loop or do i have to wipe the phone and flash an sbf file?
Can you point me to the sbf file for the new orange gingerbread rom?
Thanks
ryan
Anyone?
When i turn phone on it works for about 20-30 seconds, before it restarts into the splash screen. It seems as if the phone is running some sort of script to continue with the upgrade but when it reboots it cant continue or something...
The OTA update didnt even start flashing, it just downloaded, then i clicked "install now" and it just rebooted to the error.
If i cant fix it easily, can I use RSDLite and an SBF file to go back to stock? Or can you only do this on an unlocked bootloader?
My bootloader is still stock. The only thing I did when I got the phone was root it so that I could install certain apps.
PLEASE HELP!
Link to Orange UK GB SBF is in Atrix 4G Android Dev forum in the Atrix Firmwares Superthread..page 25ish.
I RSDLited this SBF onto my Atrix (unlocked bootloader running Alien #4) with no problems.
This same route may be your only option...not sure about recovery of your apps etc..I have everything backed up via Blur, Google account and Titanium Pro, so no concern for me there.
FYI, this new rom seems to have little Orange bloat and runs great for me in stock form...just rooted...and battery life is very respectable.
Hi All,
Please HELP.
I was a complete noob to rooting until I started this but spurred on by successfully rooting and overclocking / undervolting my defy I thought I would try to install Gingerbread so I can use the stupid stupid sky+ app which no longer supports 2.2.2.
Its all gone horribly wrong and I still dont know why as I checked and rechecked the prep but S..t happens so they say.
I have pretty much given up on this and will buy a new phone tomorrow if I cant sort today but would like to ask everyone that has more knowledge than myself on this subject (which doesn't narrow the field much!) if they have any ideas.
Well where do I start, I bricked my defy.
Apart from when I flash shadows rom (see below) I have only black screen, white led on usb connection, no recovery boot. phone is visible to rsd lite but nothing else. This happened after I lost sd card availability after reset / wipe trying to install a fixed gingerbread rom using RSD lite.
I could not flash back to froyo and every other recovery sbf i tried wouldn't work until I found an old sbf from shadow which actually booted up! YESS!! but then Nooo!. phone screen looks very nice - not sure what version it is but assume ICS (its got spareparts folder which I`ve not seen before) - and works as alarm clock and web browser but no phone function at all - no signal, no call or end call buttons - just not there! this (http://forum.xda-developers.com/showpost.php?p=14762402&postcount=143) is the link where I found shadows version, couldn't wipe in between each step so just flashed 3 files in turn using rsd lite and it seemed to work - phone booted up after 3rd sbf was flashed. The rom is set up for developers and has some developing tools included acr, api demo,dev tools, hstcmd & redlinecap
Main problems:-
The rom is a tmobile version and I`m on vodaphone so maybe this is why there's no phone service but I wasn't prompted for an unlock code so assume its not locked.
The 2nd boot recovery no longer works even after reroot and reinstall (see below). I can surf the web very well via wifi - much quicker than before but downloads dont seem to work but only tried shortfuse.org and that site is apparently down atm and anything that requires google wont work as Gapps got deleted. I cant install GAPPS without boot menu.
recovery from main boot menu is unavailable and zip from sd just reboots.
I also cant connect my phone to my pc via usb and have the sd card available at the same time, as soon as the USB is connected the sd card is not available to the phone, I can see it on the pc and can read / write / delete from the pc - (usb debugging is disabled). when I access the sd card via file manager on phone (with usb disconnected) I can install some programmes that I have transferred from my pc; 2ndinit installed and said 2nd init installed ok again (after re-rooting) but still no blue led on reboot.
I've since tried everything I can think of or search for - After loosing the sd card availability I copied card contents to pc and reformatted sd card on pc. copied back the files immediately before flash attempt to sd as well as the rooted froyo backup I had and nothing changes. I have a titanium backup on the card but have so far been unable to install titanium again to try and restore it. no play acces as no gapps and when I try to access via pc and send it to phone it says installed but its not on the phone. every other file on the sd card results in error parsing file or file type not supported.
BTW when I say originally that I lost sd card availability I have now realised that it was the problem with having the usb installed at the same time which caused it and if I had unplugged it may have worked but still dont understand where this problem came from but I did have usb debugging turned on at the time.
I have scoured these holy pages for 2 whole days and tried several fixes which have probably really messed up everything even more but nothing has changed with the usability (or not) of the phone. A lot of the old links found were dead or taken over by a fake install of filemanager that my antivirus caught was a trojan. Due to this I may have missed an avenue or 2 but think I`ve tried everything I can.
At this stage I do not know exactly what I`ve tried as the list is endless but it includes reflashing the green lense kernel, attempting to reflash the original rom and any other recovery, fixed or stock roms I have found which don't specifically say only for defy+ and the only rom that allows the phone to boot is shadows above and that has no functionality.
I would love to install the latest cm10 build but cant get into the 2ndinit menue so unless someone knows away to flash it using RSD lite I`m stuck.
I do not even know if the cm10 would work as I`ve probably messed up the kernel and the original rom so the 2nd init may not get a look in.
Any help would be greatly appreciated. You'll find me under the stairs mumbling to myself and probably dribbling a bit - my wife thinks I`ve gone mad and is not talking to me until I get another phone or fix this one but I hate admitting defeat on technical problems.:crying:
PS I dont mind if I fix the issues with shadows rom, go back to any stable build or get cm10 working I just need the phone.
Thanks in advance, Tim
update
Hi All,
Just a quick update on this thread as I`ve had a bit more of a play and think I`m getting somewhere possibly.
I have now eliminated the problem of not being able to see the sd card files in file manager when the usb is connected.
How? - i haven't got a clue, i just unsuccessfully tried flashing a few more roms and when I reinstalled shadows rom i could view files whilst connected.
Also the 2ndinit now gives me the green led when it installed the 2nd boot but unfortunately I still dont get the blue led on reboot.
Another strange thing is I dont get the round M logo on boot but motorola written in white??
If I could just get to the CW recovery on boot I could install cm10.
Any suggestions?
Thanks
Tim
fixed by flashing with JDGC_U6_2.13.0
YESS FIXED BY FLASHING JDGC_U6_2.13.0 SBF using RSD lite.
Many thanks to everyone that helped via another thread http://forum.xda-developers.com/showthread.php?t=1217016&page=2, I thought they were far too many issues with this phone to repair but the latest froyo rom and kernal in the above sbf worked fabulously.
As has been said on several posts flashing this SBF will not allow you to return to the uk stock rom after (to return a phone under warranty etc) but if you're stuck with a brick then this should clean up your phone to original settings to allow the install of cm10 or another rom of your choosing (as long as its build 6 or later)
Hallo all.
This is my first post so please have a bit of patience with me.
So I have a Defy MB525 red lens which I had rooted and installed CM 7.1 back when that was cutting edge. As development progressed and updates to CM 9, CM 10 and CM 10.1 became available, I upgraded with no problems.
Last year in Sept messed up a upgrade, compounded the problem and messed up the battery. Order new battery and wall charger for battery. Wait long time for battery (customs problem), at last all is here and fix frozen boot problem. Boot up to installed sbf to find I made more problems by flashing this DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf image. So now stuck with BL 7 and nowhere to go. Found this thread http://forum.xda-developers.com/showthread.php?t=1542956 which solved that problem (my thanks to the devs who sat down and found a way around this problem).
So now my Defy is rooted again, lets upgrade to CM 10 or CM10.1..........
Ooooops so what is this???????
Bootloader 09.10 ERR:A5,70,00,00,23
Every time I try to install I get this error. Every timehttp://forum.xda-developers.com/images/smilies/crying.gif. The only way to fix is to start power button and other finger on Vol+, now bootloader is OK, show no errors. The problem is that I have to start the install and root sequence from scratch using RSDlite 6.1.4, it is very time consuming.
I have searched internet and forums and found quite a few other people with the same error. But no understandable explanation for it, or a way to fix it.
I have tried CM 7.1, 7.2, 9, 10, 10.1 with kernel, without kernel, 2ndint, 2ndboot. No joy.
Is there a fix for it? Or a way around it? On one thread MSGinger 2 was mentioned, I have not tried it yet, but will look into it.
Thanks
It seems I cannot delete this post, could some one please delete it for me? For some reason my Firefox on win do not show the page properly and so I posted twice by accident.
My thanks
Hi,
A few days ago I unlocked my bootloader and tried to install a ROM on my phone, more specifically the latest version of Bootleggers, to my surprise it didn't work and now I have a serious problem, because of my lack of patience(I didn't wait for health to get better to buy a bigger memory card, mine is only 2gbs sad life), I didn't back up my phone (nooby and stupid, sry guys), and now my phone doesn't want to boot into any OS I put on it (even the original one), I've tried pretty much everything (I know off), do mind that i only have 2 days of experience so I don't know that much. If anybody knows anything that might change my phone for the better I would appreciate the help.
Stuff that happened
I think I might have deleted something I should't have when trying to install Bootleggers for the first time.
I have successfully installed a OS ones, Havoc OS 2.9 (through ADB though), but I didn't like the interface so I deleted it and tried others, Resurrection Remix and ASOP, none of them worked so I tried flashing Havoc through ADB again, but this time it failed, it stopped in the middle of booting like all the other ones.
I can get into Recovery, eRecovery and Fastboot mode.
I don't have ROOT (Magisk) on it (at least I think), I installed it ones, but my OS didn't load so I tried deleting it afterwards and I got a error in the terminal probably because I didn't have it installed.
I still don't have a bigger SD card, I'm gone buy it tomorrow tho.
Info
Phone - Huawei P10 Lite
Model - LX1A
Firmware - WAS-LX1 8.0.0.368(C432)
Software (Mentioned in the quick start guide that came in the box) - WAS-LX1AC900B049
TWRP - 3.3.1 (also 3.2.1 but only for the MTP function(sometimes it gives me a black screen after opening it))
Problem - Phones starts booting the OS I put on it, but then stops and returns or to Recovery or eRecovery.
I dont know what more info to put here, like I said earlier nooby (and pls dont hack me if ive put the wrong info online, thx).
AlphaReigN said:
Hi,
A few days ago I unlocked my bootloader and tried to install a ROM on my phone, more specifically the latest version of Bootleggers, to my surprise it didn't work and now I have a serious problem, because of my lack of patience(I didn't wait for health to get better to buy a bigger memory card, mine is only 2gbs sad life), I didn't back up my phone (nooby and stupid, sry guys), and now my phone doesn't want to boot into any OS I put on it (even the original one), I've tried pretty much everything (I know off), do mind that i only have 2 days of experience so I don't know that much. If anybody knows anything that might change my phone for the better I would appreciate the help.
Stuff that happened
I think I might have deleted something I should't have when trying to install Bootleggers for the first time.
I have successfully installed a OS ones, Havoc OS 2.9 (through ADB though), but I didn't like the interface so I deleted it and tried others, Resurrection Remix and ASOP, none of them worked so I tried flashing Havoc through ADB again, but this time it failed, it stopped in the middle of booting like all the other ones.
I can get into Recovery, eRecovery and Fastboot mode.
I don't have ROOT (Magisk) on it (at least I think), I installed it ones, but my OS didn't load so I tried deleting it afterwards and I got a error in the terminal probably because I didn't have it installed.
I still don't have a bigger SD card, I'm gone buy it tomorrow tho.
Info
Phone - Huawei P10 Lite
Model - LX1A
Firmware - WAS-LX1 8.0.0.368(C432)
Software (Mentioned in the quick start guide that came in the box) - WAS-LX1AC900B049
TWRP - 3.3.1 (also 3.2.1 but only for the MTP function(sometimes it gives me a black screen after opening it))
Problem - Phones starts booting the OS I put on it, but then stops and returns or to Recovery or eRecovery.
I dont know what more info to put here, like I said earlier nooby (and pls dont hack me if ive put the wrong info online, thx).
Click to expand...
Click to collapse
Hi,
have you tried to enter into eRecovery and click download and flash and then tried it?