Database Users

[Q] Magic 32a Flashing problems

Hey you guys
I recently installed amon ra's recovery v. 1.7 on my magic 32a (radio 6.3.5 something) after I rooted my phone, of course.
Now, I thought that with the new recovery I would be easily able to flash a custom rom onto my magic. This was however not so easy, because the recovery behaves in a very weird way. Whenever I tell it to flash a new rom from a .zip image, or wipe the phone, or anything, it just reboots my magic and thats it. Also, the recovery happens to freeze quite regularly when I don't act very quickly. E.g. when I boot into recovery mode and don't touch the phone for the first 5 seconds, it wont respond any longer.
So, I'm probably doing something wrong here. I would appreciate any help from anyone. (and btw, i have the official android 1.5 sense rom installed on my magic, os I cant use rom manager either, since it only supports android 1.6 upwards.)

Look at the root guide in my signature..
Do step 0, 1, 2, 5 and 7 only.
It should flash the recovery partition one more time.
Hopefully it will fix your problem :0)

mumilover said:
Look at the root guide in my signature..
Do step 0, 1, 2, 5 and 7 only.
It should flash the recovery partition one more time.
Hopefully it will fix your problem :0)
Click to expand...
Click to collapse
hey, thanks for the quick response. I still have a few questions though, since I am quite a newb. So when I type all of those commands into cmd, doesnt my device need to be connected to the computer somehow? I read somewhere earlier that I simply connect it using the "mount" funtion, the problem is that that doesnt seem to work anymore for my magic, because after I hit "mount" it simply goes back to "usb connected" without acutally mounting. So ..how do I connect the device to the PC while entering the commands?

ok... my bad..
Try to read the ENTIRE guide... then do the steps i mentioned above :0)
Don't mount it... just connected... but again.. read the guide.

thanks a lot
I didnt use your method to flash the image, but the hero recovery works way better than the one I had before. I managed to flash a rom now. So happy ;D

ok i think i just did a bad mistake
i installed rom manager after i had flashed an android 2.1 rom on my magic. THen i told it to flash some rom from my sd card and also wipe some data, or something. Now my magic gets stuck on the magic bootscreen, like it keeps looping. Did i brick my phone ..or is there a way to fix this? please help me, (

most likely is that the rom you flashed doesn't have a compatible kernel for your phone.
Just boot into recovery and flash a rom that is compatible.

cant boot into recovery ..it just keeps looping

Then you will need to boot into fastboot and reflash a working recovery.
Clockwork has issues flashing the clockwork recovery sometimes.

to boot into fastboot i need to hold power and back, right? ..that doesnt work either. again, it just keeps looping.

so, guys ..did i brick my phonne..?? :S

da robat said:
to boot into fastboot i need to hold power and back, right? ..that doesnt work either. again, it just keeps looping.
Click to expand...
Click to collapse
you're probably not doing it right. you should still be able to get into recovery or fastboot and install a different recovery. i'm using RA-magic+v1.7.0.1 recovery it has bugs but pretty stable.

so what am i doing wrong??

just realized when i connect the phone to my pc over usb and then boot it, it connects to the pc for a second or less and then disconnects again. Dont know if this helps anyhow.

pull battery, put battery back in. hold back and push power.
Should be good.

tried that like 50 times. phone just keeps looping ..like, it restart over and over again.

What you have is what hundreds before you had when they used Rom manager.
The system will not boot into anything.
My advice is to never use Rom manager for 32A device.
The fix:
Keep pushing the back button while the system reboots... just mash the **** out of it..
I helped out someone before you, and he did it for over an hour or so...
It's a timing issue...
Good luck

haha ..so is there still hope?
cheers for all the answers ;D

i do have one question though, actually.
Shall i just press the back button continuously ...while it keeps looping, or should i rather restart the device after each loop and hold the back button?

just mash the back button.

Phone gone?! please help!!!

Hi, I think this should go into Dev section, but i dont have enough Posts yet... This forum is my last hope. I already did Custom Recovery, Root and Custom Rom on a different phone, but I think this time ive briked my Phone
I rooted my brandnew Play yesterday and landed in a bootloop today, i think i had a wifi Problem, however, I then tried out FrAsErTaG's FTS Customrom and everything worked fine. Afterwards I wanted to flash the DooMLoRD Kernel. Now I cant access my phone anymore... Cant get into Bootloader mode nor into flashmode or anything, the led on the Powerbutton stays black. But when i press the Powerbutton, the phone vibrates for a second and a blue or green light flashes for a millisec. When i do the same while connected via usb, the phone does nothing, and the phone isnt recognized by the pc. any Help PLEASE??? Phone was brandnew

Somehow i can access Fastboot mode now, but though i flashed another rom, the phone wont bootup.. no animation, nothing, just the vibration for a sec again.

arihellmichimich said:
Somehow i can access Fastboot mode now, but though i flashed another rom, the phone wont bootup.. no animation, nothing, just the vibration for a sec again.
Click to expand...
Click to collapse
You need to flash a new kernel/boot.img by the looks of it, maybe try flashing the stock kernel as you know it works, if boot partition is corrupt or badly flashed, flashing a rom wont solve the problem
Sent from my R800i using Tapatalk

I think i now realize what i ve done... While using fastboot, i renamed the img files by numbers - also the ClockWorkMod Recovery from this Post http://forum.xda-developers.com/showthread.php?t=1130639 where it is clearly stated that i should not flash it. I think I mixed up the numbers and flashed it and thats why i cant boot anymore... Stupid me!!! Any Idea??? I could kick my own butt right now!!! By the way, i can access CWM now via Fastboot, but booting up normaly still doesnt work of course...

arihellmichimich said:
I think i now realize what i ve done... While using fastboot, i renamed the img files by numbers - also the ClockWorkMod Recovery from this Post http://forum.xda-developers.com/showthread.php?t=1130639 where it is clearly stated that i should not flash it. I think I mixed up the numbers and flashed it and thats why i cant boot anymore... Stupid me!!! Any Idea??? I could kick my own butt right now!!! By the way, i can access CWM now via Fastboot, but booting up normaly still doesnt work of course...
Click to expand...
Click to collapse
Just flash doomlords kernel from fastboot, that has CWM embedded into the kernel, so you get to keep your recovery and get to boot your phone
just to be safe, use the command "fastboot erase boot" before you flash a kernel, this will format the boot partition so you can make a clean install
doomlord thread:
http://forum.xda-developers.com/showthread.php?t=1176502

Thanks a lot! Right now, when i connect it to the Powercable, the red led flashes every few seconds. I will try as soon, as my battery is charged again..

... I have a really bad feeling again. After the red led stopped blinking, i connected via Fastboot (blue light), erased the Boot partition and flashed DoomLords Boot Image. Sais 1 bad block encountered! (it told me already, that i had 10 bad sectors when i flashed the rom before but i didnt think this was the problem, because it bootet up at that time).
For now, i cant even get into this fastboot mode, only red light blinking.
Any other ideas please???

arihellmichimich said:
... For now, i cant even get into this fastboot mode, only red light blinking.
Any other ideas please???
Click to expand...
Click to collapse
Good luck with this. I basically did the same thing on Sunday. I gave up trying to fix late Sunday night, but when I tried again yesterday evening I'm only getting the blinking orange light. I did leave the device on charge last night, but the light didn't come on to say it was charging. How do you know your battery is charged?
I'll take AH's advice and if I ever manage to get the blue light back I'll erase boot, installed DoomLords custom kernel and then hope recovery can fix the rest.
I'll post back here if I make any progress before you (and please let us know how, if you manage to fix it in the mean time).
Daeron.

I've spent the last couple of days searching the forum, search google, search the forum some more and I've made a bit of progress.
After finding similar threads in the X10 forum I believe the flashing red light is related to the battery. Also my inability to get a fastboot blue light was caused by uninstalling SE Companion while trying to use other drivers for a Flashtool stock image flash (I didn't get that to work either). I have reinstalled SE Companion and can now connect to my PC in fastboot mode (with the blue light).
This is where my progress ends. I have tried using using this and the commandline outputs this
Code:
F:\Xperia Play\Boot Unlock\fastboot>fastboot boot recoveryPLAY.img
downloading 'boot.img'...
(bootloader) USB download speed was 41547kB/s
OKAY [ 0.549s]
booting...
(bootloader) Download buffer format: boot IMG
OKAY [ 0.003s]
finished. total time: 0.552s
but the phone does nothing except the blue light goes out. Which leads me back to the battery.
After trying to fastboot the recovery image the only thing I can do is disconnect, take out the battery, put battery back and plug into mains charger. The red light starts flashing again for a short while then I can try again with fastboot.
Next step is to leave it on charge for a few hours (only did 30mins last time) and try again. I think the reason the recovery didn't work is the battery won't hold enough charge to boot on its own, so I need a new battery
The only other thing I haven't tried is to erase partitions before booting recovery. I'll give that a go before booting recovery image in a few hours.
D.

When i boot into CWM from the boot image via fastboot. It will shut off the phone. Just unplug the device, wait a sec, and try to enter fastboot again. Usually it hangs and then goes to CWM. And when you flash a new rom, You need to factory reset in CWM clearing data and cache or else it will bootloop. Thats just basic Android rommage right thurrrr. Mine was stuck, and i just flashed the stock system.sin and kernel.sin and erase the /data and /cache with Clockwork.
fastboot flash system system.sin
fastboot flash boot kernel.sin

Sooo sorry, i didnt post before, but i moved out of my flat and had a lot of other stuff to do last week...
In the End this helped for me.
1. FULLY CHARGE YOUR PHONE!!! I was told to remove battery for 30minutes, then put it back in but without sim card and withough SD Card. Then plug the charger back and charge for at least 5-10 hours!!!
2. Connect your Phone in Fastboot mode (blue light) by pressing the searchbutton before connecting.
3. Do the steps of relocking your play through Fastboot
4. Try SE Update again with the official Sony Software, it said software could be updated :-D
So in the end, the blinking red light was just a battery problem, i couldnt imagine it was such a big deal, because i always charged for at least an hour and i thought the usb port of my netbook was at least strong enough to provide power during the flashing progress BUT IT WAS NOT!!!
Thank you soo much for the help!!!

Everything worked out fine that way.

[Q] How to reboot into recovery?

I rooted my G2 about two months ago. I'm currently using MIUI, not the latest but the one before it. Somehow, my phone got turned off and when I tried to turn it back on, it was stuck in a bootloop. I have a custom recovery image so I don't know if that affects anything. I tried to reboot into recovery by pressing volume down and power, nothing happened. I then did volume up and power. It vibrated three times and the orange light started flashing. I pulled the battery and now when I try to turn it on, nothing happens. So how do I reboot into recovery and so I can restore my backup? Any help/suggestions would be greatly appreciated.

Never pull the battery during something like that. It sounds like your bricked. Someone else confirm?

I don't think it's bricked. I plugged it up and then Clockwork came up so I selected reboot now. Clockwork came up again so I tried to restore my latest backup and the screen went black. I'm going to let it charge and then give it another try.

Ok good. That's lucky because whenever you pull on a boot like that, it usually bricks. If you have the option, try to re-flash your ROM. Maybe even try stock. If you were getting a black screen, it's most likely you flashed incorrectly.

Ok, I was able to boot into recovery and now I'm restoring my backup. I don't think I had a custom recovery image with this one so hopefully I won't get stuck in a bootloop. When you say stock, do you mean before I flashed MIUI (it was the first rom I flashed)? Thank you for your suggestions and all of your help.

first install adb on you PC, it helps a lot in these kind of cases.
1. try "adb logcat", it would tell you about what's going on in your machine.
2. once you get your adb working, try "adb reboot recovery" to see if it could boot your phone in recovery.
3. if after doing everything you fail to boot either your phone or in recovery then try using PC10IMG to boot a stock rom and then re-root your phone.

I got it back working. For some reason, I'm just starting to think that it needed charging (the battery had been out for about a day or two). I do have adb installed and configured on my computer since I needed it to root. Thank you for your suggestions, I will definitely rember them if this happens again.

lol of course when you get black screen and led blnking means your battery begging for juice, you're lucky that when the phone booted back in recovery and you tried to restore a backup the phone went off before actually starting to restore, that would've bricked your phone
DO NOT FLASH ANYTHING WITHOUT AT LEAST 40% OF JUICE LEFT

help! my oppo find 5 completely bricked after Sd partition by TWRP

my phone couldn't launch to fastboot or recovery..... plz give me some advices. ( i guess my phone hot hard-bricked problem)

See here maybe this can help you... http://www.oppoforums.com/threads/guide-fix-oppo-device-wont-boot.26272/
BTW where are you from

fancyfree said:
See here maybe this can help you...
BTW where are you from
Click to expand...
Click to collapse
thanks...... i hope this will work

i can't move with the final step
plz help me!!1

Try this method http://www.oppoforums.com/threads/oppo-find-5-bricked.7645/page-4#post-386815

fancyfree said:
Try this method....
Click to expand...
Click to collapse
it finally work! thanks for your help. but it's very complicated. i didn't know how it work. although i want to share how to fix it. this is the hardest brick problem i ever seen

I also tried to partition my sd card using twrp.
Flashing of twrp seemed not successful using fastboot. So I unplugged the USB-Cable and restarted in recovery and twrp was there!
So I went further and tried to partition sd. Unsuccessful. Then I decided to give up and rebooted to system.
Phone screen remained black. I tried everything to boot phone. No reaction at all. No vibration, nothing. Only when I connect the charger the buttons light up for 5 secs. But no way to boot, not fastboot, nor recovery or system. Just nothing.
I tried then to disconnect the battery (It's a replaced battery already) but also this did not help.
No I really need help...
Unfortunately above links are outdated....

Has noone an idea what else I could try please??
zorbas2 said:
I also tried to partition my sd card using twrp.
Flashing of twrp seemed not successful using fastboot. So I unplugged the USB-Cable and restarted in recovery and twrp was there!
So I went further and tried to partition sd. Unsuccessful. Then I decided to give up and rebooted to system.
Phone screen remained black. I tried everything to boot phone. No reaction at all. No vibration, nothing. Only when I connect the charger the buttons light up for 5 secs. But no way to boot, not fastboot, nor recovery or system. Just nothing.
I tried then to disconnect the battery (It's a replaced battery already) but also this did not help.
No I really need help...
Unfortunately above links are outdated....
Click to expand...
Click to collapse

troubleshooting, bricked overnight

Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.

PinkElf said:
Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.
Click to expand...
Click to collapse
Hi, try to flash the stock firmware otherwise I really don't know :/

I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?

PinkElf said:
I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?
Click to expand...
Click to collapse
Are you using Lineage OS? If yes, then definitely yes. On my Xiaomi, I couldn't get into fastboot mode or into recovery, I don't know why and somehow I got there, I don't even know how I think I held the power mode for a long time and when the phone turned on I held the volume up button to get into recovery finally succeeded on the umpteenth attempt and from recovery I restarted the phone in fastboot mode and flashed the stock firmware. And yes, being able to boot your phone into fastboot is a good sign. It would be worse if it wasn't possible.

I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.

PinkElf said:
I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.
Click to expand...
Click to collapse
Yes, you can use download mode to install the firmware via Odin. Look

That means giving up hope for my personal data...
But even if I want to do this, I run into the problem, that I can't install anything due to "could not find PIT partition"...