Related
after flashing ota-radio-2_22_19_26I.zip and SPL 1.33.2005 i rebooted the bootloader using the code:
fastboot reboot-bootloader
But now my problem is that the Magic will not boot no matter how i try to boot it. i have taken the battery out and put back in several times but still no lock.
When the phone is plugin charger the LED light shows that it is charging but when i try to switch it on, the LED light goes off and nothing happens.
Can someone please help me with this
Actually you've flashed à 32B Radio on your 32A
If you can't boot into fastboot mode (holding back+power), recovery mode (home+power) or hboot mode (vol.down+power) and your phone is not recognized when connected to the PC then there isn't anything you can do, unfortunately. You can't get into any of these modes right?
you are right i cant get into any of those modes.
Is there nothing that can be done? no hard reset or some fix? i dnt mind opening the phone.
is there no parts i can replace to get it to work?
I hate to bring bad news but once you're locked out like this I'm afraid that only HTC can help... I'd try to get the phone replaced if it's under warranty.
the warranty is over.
since i can repair it as i have a few times and i have opened it and changed a few things like the screen.
cant i change the logic board or something or any part to get it working.
i mean cant i replace the radio chip or something like that.
sorry it sounds like i am just carrying on but i believe there is a way to make it work.
What have you repaired for it? (Just curious)
Isn't this a software problem, not a hardware? I don't see how opening it can really help unless you change up everything inside I could be wrong though.. But seeing as how you flashed the incorrect Radio, I don't see how changing that chip could help at all really.
I really don't think there is anything left you can do.. But again, I could be wrong! I don't know everything about the phone lol
i mean if i was to get another board from another htc magic or even buy it as a part and change my one.
or cant those parts be bought?
I dunno if you can buy that or not, but if you were to do that... It sounds almost like getting a whole new phone lol
so after getting my blue led light after i did a bad flash of a mod update zip when i didnt have a rom flashed first...i was told to replace my trackball instead i ...
opened my htc magic and removed my trackball and disconnected the ribon to it let it sit for 30 seconds then put it back together i guess it resets hardware but it worked like a charm
tried ur methode on my bricked magic ... no luck
did u have the blue led with no hboot or recovery ...make sure ur battery is charge some
thatruth132 said:
so after getting my blue led light after i did a bad flash of a mod update zip when i didnt have a rom flashed first...i was told to replace my trackball instead i ...
opened my htc magic and removed my trackball and disconnected the ribon to it let it sit for 30 seconds then put it back together i guess it resets hardware but it worked like a charm
Click to expand...
Click to collapse
I can't understant why doing that the device has unbricked, I probably must do the same.
anyone else tried?
is this really working???
can anyone other than the OP confirm this works? what showed up on the screen when it was bricked? Did it have the 'arrow coming out of the box' symbol, when the phone was switched on?
i did nt get big arrow or anything my phone wouldnt boot period all i kept getting was a blue light no fastboot or adb would work until i did this the only reason i tried it was because someone mentioned to me to replace the track ball i dont know why but it worked
Did you happen to remove the little battery when you did this?
no i only disconnected the cable leading to track ball the if u look where the track ball is you can pry and pop out the track ball i did it just to look around in there ...i am not a tech but i do have a basic understanding of somethings and i think for some reason in my situation it may have reset something i really dont know but my phone was a brick for half a day with me trying to use google as my friend typing away at fastboot and adb commands only to get nothing ..but when one person told me i may need a new track ball i just decided to look inside on how that a bad flash would effect the track ball but i did what i did and i am back using my phone but i did notice one thing today i had put my phone in fastboot and the normally when it loads those command or whatever about loading img. ...its now saying no image
Thanks, I will try this. Unfortunately I gave away my battery and cable... I still have doubts about this helping me, as I flashed the wrong radio. Where as you just flashed a bad update.
did u use a 32b radio
thatruth132 said:
did u use a 32b radio
Click to expand...
Click to collapse
hi,
quick question. my friend rooted the phone and then flashed hardSPL but i think it was the wrong one. the last thing we saw was a box with a arrow on it and the phone has been dead ever since.
was this the same for you ? we would love to be able to unbrick his phone.
brick
hi,
i have a 32b magic, and since yesterday it just doesn't startup anymore.
i just get a black screen, with backlight on. (also no adb/fb/recovery)
if i hold trackball while power on, i get the blue led
i've searched, but haven't found any similar problem, cause i don't get that box with an arrow.
to unbrick this, you just disconnected the trackball?
pls be more specific
HEEEELLPPP!
fakecaker said:
i just get a black screen, with backlight on. (also no adb/fb/recovery)
Click to expand...
Click to collapse
Sounds like you erased or flashed an invalid SPL (usually people brick into boot mode 3 where the radio + SPL works but is forcing the boot of a broken recovery image) Thus the user becomes stuck at the splash screen.
Regardless if blue light mode woks and nothing else will boot [and you are not stuck in blue light mode]:
the only option at this point in time is using JTAG to force an engineering SPL to load.. then use that to fix the rest of the phone.
http://forum.xda-developers.com/showthread.php?t=668246
http://forum.xda-developers.com/showthread.php?p=6100287&highlight=radata#post6100287
The OP likely had a stuck trackball.
Holding the trackball when you power on puts you in the blue-led mode and doesn't let you do anything else. Being in blue-led mode doesn't mean you are bricked, it's just a mode in which the phone can start up. If the op's trackball got "stuck", it would explain his problem. Replacing the faulty trackball likely is what solved his problem.
It would be nice if the OP could update the first entry to reflect as much.
If your phone isn't voluntarily going into blue-led mode on it's own, this "fix" likely won't do anything for you. You still have a brick... like me
ezterry said:
Sounds like you erased or flashed an invalid SPL (usually people brick into boot mode 3 where the radio + SPL works but is forcing the boot of a broken recovery image) Thus the user becomes stuck at the splash screen.
Regardless if blue light mode woks and nothing else will boot [and you are not stuck in blue light mode]:
the only option at this point in time is using JTAG to force an engineering SPL to load.. then use that to fix the rest of the phone.
http://forum.xda-developers.com/showthread.php?t=668246
http://forum.xda-developers.com/showthread.php?p=6100287&highlight=radata#post6100287
Click to expand...
Click to collapse
hi terry ...
quick question.
the jtag de-bricking that everyone is mentioning is said to work with g1/dream/g2 ... is this also possible with the magic(sapphire) 32A ?
like i said my friend bricked his loading hardSPL and the phone is charging and i can get into the blue led mode no problem.
if it is possible would the pinouts be the same or similar for the magic? i am quite keen to give it a bash if i can be pointed in the right direction.
thanx in advance.
Thank for you response
but i didn't flash any new spl or something else.
i had my phone working fine with spl/radio/rom.
but then i shut down, and after that i couldn't power up
i reboot my working magic with froyo and then is dead.
its keeps rebooting and no fastboot or recovery mode only if i press trackball and on the phone i got blue led, any solutions ???
Regards Sn00py
But what exactly was the problem, when you turned it on it automatically turned the blue led or did that happen when you pressed the trackball+power? im going to try to debrick my magic now but must it be on with the blue led or off?
ale922 said:
But what exactly was the problem, when you turned it on it automatically turned the blue led or did that happen when you pressed the trackball+power? im going to try to debrick my magic now but must it be on with the blue led or off?
Click to expand...
Click to collapse
Who are you asking, the OP? They just had a stuck trackball, so they couldn't boot normally.
It doesn't matter, just continue.
Hey guys, I jsu bought a used G1, since I needed a phone because I've started developing apps for android. Anyhow, since I don't have much money I had to buy a used one.
So this one has a (quite big) problem - when the screen is on the keyboard (normal position) the screen turns off. You can see the backlight, but nothing else. When the screen is slid out, it works perfectly fine.
Any idea what the problem may be?
Sent from my HTC Dream using XDA App
It can be a problem with the ROM also can be a hardware problem.. Try another ROM first and report back.
I tried more than 3 roms, still does the same.
I also filmed how it turns itself off:
http://dl.dropbox.com/u/5608529/vidya/g1.avi
Forgive me for stating the obvious, but have you tried wiping?
Yup, more than once.
At this point, if it was my phone, I'd consider breaking out a screwdriver set and try to see if something came loose or is worn.
Well now it's not working at all.
Not even when the screen is slid out.
And I don't have the required screws to open it... Guess I'll have to buy them somewhere :/
EDIT:
This is weird.. I somehow managed to turn it on, but now it's stuck on a black screen with "Build: " at the bottom of it...
EDIT2:
And now when I rebooted it, only the backlight turns on...
EDIT3:
When I turn it on regularly, the T-Mobile G1 screen appears and then disappears. You can still see the backlight, but nothing else happens.
When I turn it on to recovery mode, the G1 screen appears, then disppaears and then you can see a black screen with "Build: " at the bottom.
EDIT4:
Apparently, when I start it regularly, it does boot into Android, but it's like stuck.. Seems like it's kinda bricked? No idea.
EDIT5:
Is it possible to reinstall the ROM without having access to the recovery menu?
Crembo said:
Well now it's not working at all.
Not even when the screen is slid out.
And I don't have the required screws to open it... Guess I'll have to buy them somewhere :/
EDIT:
This is weird.. I somehow managed to turn it on, but now it's stuck on a black screen with "Build: " at the bottom of it...
EDIT2:
And now when I rebooted it, only the backlight turns on...
EDIT3:
When I turn it on regularly, the T-Mobile G1 screen appears and then disappears. You can still see the backlight, but nothing else happens.
When I turn it on to recovery mode, the G1 screen appears, then disppaears and then you can see a black screen with "Build: " at the bottom.
EDIT4:
Apparently, when I start it regularly, it does boot into Android, but it's like stuck.. Seems like it's kinda bricked? No idea.
EDIT5:
Is it possible to reinstall the ROM without having access to the recovery menu?
Click to expand...
Click to collapse
Getting a set of screwdrivers/torx/etc is a good idea. I picked mine up on eBay awhile back. An investment every techy guy should make.
It also sounds like you may want to get acquainted with adb and particularly fastboot. You *should* be able to use fastboot to get a working recovery and then use the recovery to get a rom loaded. This: http://forum.xda-developers.com/showthread.php?t=532719 seems like a decent guide to get you going with what you need if it is in fact a software issue.
Since your experience keeps deteriorating, I'm beginning to wonder if a chip inside is going bad - especially with the odd things like "Build: " showing up. (Let's hope this is not the case!) Nevertheless, I think I'd start with fastboot and go from there. Good luck.
Thanks a lot, ill try it as soon as I get home.
Sent from my FROYO X using XDA App
EDIT1:
What the hell? All I did was delete the recovery (didn't even install a new one, kept on saying it's missing the file, even though I did move it using adb push) and now suddenly Android works normally.
EDIT2:
Well now it's stuck again, just like before deleting the recovery...
I'll try to reflash the recovery and then see what happens.
Hello,
EDIT - Ok I'm just adding this bit to my post to summ up the whole situation from Post 1 until Post 14 in dot points
- HTC HD2, Began randomly freezing to "HTC" screen, when reset, loads "HTC" Screen and vibrates 5-6 times, sometimes let me goto OS, but at one point stopped letting me goto OS, Stuck at "HTC" Screen with the 5-6 Mysterious vibrations.
- I tried to flash a ROM off the HTC HK Website, 1.78 I think, Stuck at 9%, Those 6-7 Vibrations, tried again, same thing stuck at 9% with Vibrations.
- Tried another factory ROM from HTC HK the latest one, Flashed 100% the first time through, but then does not boot, just stuck at "HTC" Screen with vibrating
- Tried to flash same ROM again, begins vibrating and stuck at 9%
- I wanted to try if some custom ROMS worked, flashed HSPL 1.42 on, while flashing HSPL it finished on the device but on computer I got "Unknown Error
0x1003FF"
- Continued and went on to upgrade my HSPL to 2.08 so I can flash custom ROMS, now I have 2.08 HSPL.
- I tried Artemis Custom Rom for LEO, this one after it finished I think brang me past the "HTC" Screen, it actually said "quietly brilliant" for the first time, and to some Windows config screen where this Error appeared :
ARM11 FATAL ERROR
flash_os_wm.c line 339
- So I tried resetting, and stuck at "HTC" Screen, but No constant vibrating, only 1 vibrate.
- I tried Cheetah ROM, same problem, stuck at "HTC" Screen.
- I tried "NRG" ROM, same problem stuck at "HTC" Screen, well the NRG Screen.
- I tried Kumars ROM, same problem again. stuck at at the bootup screen.
I should mention whenever flashing, on the computer it never tells me what my current Image version is, it just tells me the one i'm flashing to. e.g the "FROM" field is blank. That's it until now.
Also everytime while at the bootup screen, it cycles e.g it will Vibrate, show bootup screen, do nothing, go black... then repeat the bootup screen, vibrate etc etc etc. After ROM is flashed, if I do a soft reset it will just stay at the bootup screen and not do anything at all.
Hard reset doesn't help either, neither does battery out/in, same thing just stuck at the intro screen with all the ROMS I try.
If anybody knows what the problem could be, please post.
ORIGINAL POST BELOW BEFORE EDIT :
-------------------------------------------------
Whenever I turn on my HTC HD2 It's stuck at the white screen with "HTC" in the middle, it will vibrate on and off about 4 times, and after that it will do nothing.
A soft reset with the Red button under the battery cover just brings it to the same screen with the same problem.
Taking the battery out and putting back in does not help, same problem.
doesn't even want to respond to hard reset (Vol down + Vol Up) + Power Button briefly.
When I try to put it into the Diagnostic mode (Vol down + Power), and try to flash a ROM onto it,
It just gives a Error 294, Invalid Vendor, maybe because I was using a ROM that was not Hong Kong, I don't know but I cant try flash again as the device does not respond to anything now (like before but can't even get into boot mode).
So I'm stuck at the moment and can't do anything.
Before this it would sometimes want to start up, and then get stuck sometimes, but now it's constantly not booting up
and begin stuck at the HTC Screen with 4 vibrates.
Sometimes it even boots upto the "HTC" Screen, and doesn't vibrate at all.
And at the moment I can't even get it into Diagnostic mode, doesn't respond to anything other than the reset button.
Any ideas?
Thanks.
EDIT ----- > Now goes into boot mode, I found out that QUICKLY after reset doing vol- and power gets it into boot mode. But while trying to flash the ROM, on my computer it says NOTHING about the current Image ROM on the PC, Trying to update now, this time it goes into a Progress bar on the HD2, stuck at 9%, and funnily enough at 9% it does the same (Vibrate 4 times) thing. and is stuck at the moment.
kidcash said:
Hello,
Whenever I turn on my HTC HD2 It's stuck at the white screen with "HTC" in the middle, it will vibrate on and off about 4 times, and after that it will do nothing.
doesn't even want to respond to hard reset (Vol down + Vol Up) + Power Button briefly.
.
Click to expand...
Click to collapse
Keep trying that hard reset method. Make sure both buttons are fully pressed and briefly press power button to get HSPL to appear.
Follow this guide:
Performing a factory reset using phone buttons
1. With your phone powered off, press and hold the VOLUME UP and VOLUME DOWN buttons.
2. While holding the volume buttons, press the END/POWER button briefly and then release it.
3. When you see a warning message on screen, release the VOLUME UP and VOLUME DOWN buttons.
4. Press the VOLUME UP button to perform the reset, or press any other button to cancel the reset.
Thanks for the reply,
Sorry I was editting my post while you were replying, please read it again it has some updates on what is happening at the moment.
Got it to go into boot mode, SPL 3.03 Version, connected to USB, tried to update with HK ROM, stuck at 9% and does 4 x Vibrate, now stuck at 9% on phone and computer.
What should I do now?
Update - Error 262 on Computer (UPDATE ERROR) the ROM utility has encountered a communications errors during the update process
The computer guided me what to do :
1. Remove USB cable
2. Battery out, battery back in.
3. Start device up and flash again.
Device started at "Software update failed", i was able to plug the usb cable back in, and start flashing again.
at 4%, It vibrated 4-7 times while going from 4% to 9%, and progress stopped at 9% Again.
That vibrating I don't know why it's happening.
I even tried updating again, and it does the same thing, vibrates 4-7 times and then stops at 9% update.
Is the ROM I'm using a bad one? It's the HTC Hong Kong one from early 2010,
There is another one I can download which is from Late 2010, but it's SPL Version might be too high.
The reason I'm trying to update a ROM is to get an early SPL, so I can load HardSPL to use Custom Firmware.
EDIT -
Edit - I just tried Hard Reset, but it just goes to the "Software Update failed, please try again" screen. Tried to load ROM on again but still the same vibrating and stuck at 9% during update.
Hi,
Now I tried updating to a later HK ROM, and it updated but still now has the Green HTC Screen with the vibrating. The ROM that did the Vibrating during 3-9% and stuck at 9% was :
HTC HD2 RUU_Leo_HKCSL_WWE_1.72.831.1_Radio_CRC_Signed_15.32.50.07U_2.07.51.22_2_Ship.exe
And the one that Is Updating without problems and works fine is the newer one found on the HTC HK website :
HTC HD2 RUU_Leo_HKCSL_WWE_3.14.832.3_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship
This one it lets me update all the way through, once it's complete the device goes black and does not respond to anything, Battery out and battery in and the device starts up, but goes to the HTC Screen, and then Vibrates 5 Times.
And then does not respond.
What is the problem??
Even tried a Hard Reset, and again it does the same thing.
Boots, Vibrates once on HTC Screen, 5 seconds later, it vibrates on/off about 7 times and that's it, stuck at HTC Screen.
Since those 2 ROMS don't work, is there any ROM or Software that I can try to put on that will let me somehow get my HD2 Working again.
I had the same problem. I fixed it by flashing radio version 2.15 and then re-flashing hardspl. Then i installed a custom winmo rom. After that my phone was fine.
Sent from my HTC HD2 using XDA App
UPDATE !!
Ok this is getting very weird.
So I tried to flash the Later ROM that ORIGINALLY WENT ALL THE WAY THROUGH 100%.
THIS TIME, IT GETS STUCK AT 8%, and then the phone Vibrates 5 times just like the earlier ROM.
Does anybody know what this vibrating is indicating? I might try to ask HTC, but even though they developed the phone they would probably be of no help since they sent me a faulty phone back from Warranty.
kidcash said:
UPDATE !!
Ok this is getting very weird.
So I tried to flash the Later ROM that ORIGINALLY WENT ALL THE WAY THROUGH 100%.
THIS TIME, IT GETS STUCK AT 8%, and then the phone Vibrates 5 times just like the earlier ROM.
Does anybody know what this vibrating is indicating? I might try to ask HTC, but even though they developed the phone they would probably be of no help since they sent me a faulty phone back from Warranty.
Click to expand...
Click to collapse
Just info, I read that some users reported the same as you. And unfortunately, they have to bring it to HTC repair as this might relate to hardware malfunction.
If you are under warranty, you better bring it for repair.
Cheers
silverwind said:
Just info, I read that some users reported the same as you. And unfortunately, they have to bring it to HTC repair as this might relate to hardware malfunction.
If you are under warranty, you better bring it for repair.
Cheers
Click to expand...
Click to collapse
+1 for this. Most recently, there have been some users reporting multiple vibration patterns (usually 7 times) when turning on the phone. None of them was able to flash any ROM to bring back their HD2.
At least, most of them were able to install an original SPL before sending it to a service center. However, I never read anything about the final outcome.
The phone has already been through warranty once, and HTC's slack attitude and approach offended me greatly. They wrote on the paper "No Faults Found", which shows their reluctance towards fixing their faulty phones that they are bringing out to us. They just reflashed a ROM with appeared to "fix" the original voice problem I was having, but I didn't have enough time to test the phone out before it began malfunctioning and vibrating on startup when they send it back to me.
And the fee's and costs to get it to Hong Kong are just not worth it, having to pay the postage back from Hong Kong, plus to receive my HTC in worse condition than it was before I sent it to them.
HTC isn't what it used to be
Hi,
So i tried flashing to an older ROM I was shown to by users on the HTC HD2 forum,
It was 1.48, and It flashed all the way through, so then it didn't let me soft reset after the flash I think, so i took the battery out and put it back in.
After that It didn't do the vibrating, only vibrated once at the HTC Screen but was stuck at that.
Now though I am at SPL 1.42, so any point in trying to put HardSPL on and going to a Custom ROM? I just haven't been able to get any ROM to boot up yet past the HTC Screen.
Trying to reflash with the same ROM again this time it's stuck at 0% All the time.
So i tried updating to HardSPL, It got past the "We hacked it" Screen, but after that when it went to the Progress bar on the HTC HD2, on my computer I got the Error :
Unknown Error
0x1003FF
However now when I go into boot mode, It shows that I have HSPL Installted.
Now that I have HSPL, any tricks or Firmware I can flash to try fix these problems and try get a ROM working/booting?
I'm using Windows 7.
Another update - I put HSPL 2.08 on so I can flash Custom ROMS (well most of them i guess).
So i got Cheetah's ROM, I flashed it on and then after it was on, the HTC SCreen appeard, and then the ROM Version in Red letters at the bottom, but it did not boot up, so I did a reset, and then the HTC Screen comes up and is stuck at it.
UPDATE -- Did battery out / battery in, and It GOT PAST THE HTC SCreen, it displayed the "quietly brilliant" text, then it got into a windows screen, but then the Error
ARM11 FATAL ERROR
flash_os_wm.c line 339
I can't click "OK" on the window either its frozen.
A soft reset brings it to the "HTC" Screen with no more.
Battery out / in brings it to the Same "HTC" Screen but then it turns black for a sec, flashes,
then back to the "HTC" Screen, with no Red letters at the bottom, and it keeps going black,
then vibrate and back to HTC Screen continuously.
Sometimes though it will just be stuck at the "HTC" Screen with no Vibrating, just that screen.
I just tried flashing with the "NRG" ROM, I can't get past the "NRG" bootup screen now, soft reset or battery in/out does not help.
So far have tried 4 different custom ROMS, All give the same problem, stuck at the intro screen after the flash.
Also the installer on the computer doesn't say what my current Image is.
Any help greatly appreciated.
hello,
please try the following.
On the back of your phone, the battery cover (metalic) comes over 2 small metal pins. The phone will detect if these 2 pins make an electric contact, aka if the backplate is mounted. Some HTC have either microcontracts or magnetic sensors to prevent a phone to be flashed or to boot with the battery cover missing or improperly attached. This is because without the cover, there is a greater risk to have the battery disconnected or to fall, thus interrupting a reflash process.
Older HTC's would either prevent a bootup in case of missing cover or simply didn't start-up at all. I don't know what's with hd2 but i had one of them with exactly the same problem, and knowing that i checked those small metalic pins. One of them wasn't making a proper contact with the metalic cover, after i fixed that the phone was able to corecty flash a stock rom from the microsd card.
However, i repeat, i don't know if this is really the case with HD2, i may have just been lucky. One more thing, if in the end the phone woun't recover from this, i suspect a nand memory corruption. Kind of like bad sectors on a hard drive. Back some time ago, i only manage to fix a broken device with this problem after doing some welding on the cpu and connecting the board with a pc via jtag interface. Then i could mark the bad sectors as "unavailable" and correctly flash a bootloader.
Sorry for the english as i live in a non english speaking country.
LE. nevermind that, did a hardware check with some equipment, the battery cover issue is not the case with HD2. The problem seems thermal related, - if you cool the phone to 5-6 degrees celsius, the problem should either dissapear or occur less frequently. I suspect the CPU soldering to be crappy in this model, so when the chip heats up the small solder balls (the chip is BGA mounted) either don't make a proper contact due to dilatation in the chip itself or the solder materrial. Aah, i really don't know how to put it in english. However i still have a hd2 with this problem. It's worth disasembling it and trying some fancy soldering with a smd rework station.
HD2 vibrations
By me it was HARDWARE problem.
Try to give phone to 5 celsius for few minutes. After try to flash.
By it works, but after doesn't want to power on.
Hello, first off I will say I am a total novice when it comes to messing with my phone as my upgrade is in a month so I took the plunge and all was well at first. I used SuperOneClick to root my Flipside which runs Froyo 2.2.2. I deleted the bloatware as that was my main goal. This all took place about 2 weeks ago, and no problems existed.
Yesterday when I was reading a simple text message my flipside automatically reset itself and became lodged at the Motorola M logo. I've had this issue in the past before rooting so I just removed the battery in hopes all would work well as before, sadly that wasn't the case. My phone then booted up and only the backlight appeared on the screen causing it to become stuck in the infinite bootloop. I've tried all the different hard resets with the x button and power button, the volume down button, etc. None of them work as only the backlight comes up on my screen so I can't see anything. Is there any way to unroot it or flash it back to stock?
If any of my terminology seems out of place then sorry, I honestly have not a slightest idea what to do nor what is occurring other than the bootloop.
Any help is appreciated and can you please dumb down the answer for me if possible. Thanks!
Kippyyy said:
Hello, first off I will say I am a total novice when it comes to messing with my phone as my upgrade is in a month so I took the plunge and all was well at first. I used SuperOneClick to root my Flipside which runs Froyo 2.2.2. I deleted the bloatware as that was my main goal. This all took place about 2 weeks ago, and no problems existed.
Yesterday when I was reading a simple text message my flipside automatically reset itself and became lodged at the Motorola M logo. I've had this issue in the past before rooting so I just removed the battery in hopes all would work well as before, sadly that wasn't the case. My phone then booted up and only the backlight appeared on the screen causing it to become stuck in the infinite bootloop. I've tried all the different hard resets with the x button and power button, the volume down button, etc. None of them work as only the backlight comes up on my screen so I can't see anything. Is there any way to unroot it or flash it back to stock?
If any of my terminology seems out of place then sorry, I honestly have not a slightest idea what to do nor what is occurring other than the bootloop.
Any help is appreciated and can you please dumb down the answer for me if possible. Thanks!
Click to expand...
Click to collapse
Yup just rsd the sbf back. You will lose everything however so hopefully you've got a backup somehow. Here's the sbf
http://db.tt/H2RuCD8h
Okay so I've downloaded RSD Lite, and I have the file. The problem is I cannot get my phone into bootloader mode or recovery mode so that it will stop the infinite bootloop to stay connected to my computer. Advice?
Kippyyy said:
Okay so I've downloaded RSD Lite, and I have the file. The problem is I cannot get my phone into bootloader mode or recovery mode so that it will stop the infinite bootloop to stay connected to my computer. Advice?
Click to expand...
Click to collapse
I've had a similar problem as you with my flipside. Are you sure you're using the right key combination to get into rsd mode? If you can at the very least get it into bootloader mode by holding down the volume + key while holding the power button, I'm sure you can get it into rsd mode.
Kippyyy said:
Okay so I've downloaded RSD Lite, and I have the file. The problem is I cannot get my phone into bootloader mode or recovery mode so that it will stop the infinite bootloop to stay connected to my computer. Advice?
Click to expand...
Click to collapse
Theres a post here somewhere that has the combo of keys needed to get into bootloader mode. Sorry dont have it saved. Just do a search for it
Okay well I believe I found the thread you were talking about. It mentioned holding the up arrow on the keyboard combined with the power button for 4 seconds. Still nothing. I've tried the x button and power button, the volume up and power button. The thing is my screen won't work period. Nothing shows up but the backlight. So maybe I can or did get it to rsd or bootloader mode, but I can't really tell. I feel like something isn't right here. So I still can't connect it to my pc to use rsd lite.
Kippyyy said:
Okay well I believe I found the thread you were talking about. It mentioned holding the up arrow on the keyboard combined with the power button for 4 seconds. Still nothing. I've tried the x button and power button, the volume up and power button. The thing is my screen won't work period. Nothing shows up but the backlight. So maybe I can or did get it to rsd or bootloader mode, but I can't really tell. I feel like something isn't right here. So I still can't connect it to my pc to use rsd lite.
Click to expand...
Click to collapse
Did you by any chance have the stock launcher app frozen and using a different launcher? Just seems if you are seeing the backlight that possibly it is on the home screen but the launcher is corrupt? Not sure.
I'm not entirely sure. I assume it's stuck in the bootloop because when I power it on the backlight changes shades and then vibrates to signal the screen past the motorola M. Then I can touch the screen and feel a vibration to simulate to slide to unlock and if my usb cable is attached my computer makes the noise to signal it sees my device, but moments later my computer dings to signal device disconnected and my phone goes through the above process again.
I feel as if I can get to the factory reset screen and such because if I time it right I can stop it from doing anything mentioned above and it just hangs as if in a menu of some sort. The downfall is I see nothing and the backlight only appears.
I may just have to scrap it and say well done phone. I can't seem to find a similar issue anywhere on the internet. All the other issues can make the bootloader screen appear and that appears to be my number on problem.
I guess I was just being a complete idiot and thought I had removed my SD card when I didn't. Well now it can connect to my pc so I can flash it. I hope all goes well. I flash it then it should be back to factory settings right?
Kippyyy said:
I guess I was just being a complete idiot and thought I had removed my SD card when I didn't. Well now it can connect to my pc so I can flash it. I hope all goes well. I flash it then it should be back to factory settings right?
Click to expand...
Click to collapse
Yes like straight out the box. The backlight issue just seems to me like a launcher problem but that wouldn't explain why you can't get into bootloader mode. Hmmm strange. Here is another way I just thought of. If it connects to the computer (you said you hear the beep) reflash it via Motorola's site. All the instructions should be there (if they still support it)
Well I was able to flash it using RSD Lite. I could hear the start up tone and such (progress), but unfortunately my screen still won't show anything. I'm assuming the worst and maybe say hardware failure as to why the screen won't boot up? It randomly disappeared when it first went into bootloop and has never come back so that is why I assumed no working screen was a software issue.
Kippyyy said:
Well I was able to flash it using RSD Lite. I could hear the start up tone and such (progress), but unfortunately my screen still won't show anything. I'm assuming the worst and maybe say hardware failure as to why the screen won't boot up? It randomly disappeared when it first went into bootloop and has never come back so that is why I assumed no working screen was a software issue.
Click to expand...
Click to collapse
Yup that sounds like hardware failure. Haven't ever heard of the screen going out on the flipside but the atrix forums are full of them. Maybe you can get your upgrade early. Good luck