Related
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.
hi all . so i was on aurora 4.1 . clean install etc and all was fine. then one day phone decided to restart itself. at first it wouldnt boot past samsung logo. then i went into reocvery and changed kernel from h vitamin to ram kernel v1 . and cleared dalvik etc. phone booted fine. then earlier was charging phone at home (official charger) . went ot check phone about 20 mins after and no response. even tried removing battery waiting 10 mins then power on nothing. no vibrate no light. so i realised somehow the phone had hard bricked itself. so started googling about for a solution. found this thread which lets me enter download mode at least. and if i follow the complete guide i can actually boot to setup screen and phone works. only problem is the external sd card only shows 76 mb free as its still partition form before. here is the link for reference http://pastebin(dot)com/7KQxRRNF remove dot and replace with .
right so what i want to know is how do i set boot to emmc so i can actually reformat that sd card so i can use it normally? i tried to install cf root via odin. it flashed fine but when it came to booting phone it wouldnt go past the black screen (that only says kernel in yellow at the top left) . left it on for about 20 mins and it was still on that screen. tried to boot into recovery and it totally messed up and said writing tf flash xxxsectors . then i was only able to boot to that screen no matter what i tried. so had to go reformat card again and re apply steps from that link.
so is there a solution so i can boot my phone normally again then root it and installl custom roms?
im stumped as to why this all even happened as i dont use xposed. and i hadnt changed anything once i installed aurora 4.1 .
phone = n910f .
now bootlooping
now bootloop
after trying to get into recovery it now loops and shows this message
boot recovery mode (in green)
check boot partitions
copy from t-flash
boot recovery
write 54464 sectors..
reboot
even if i remove battery wait put it back in and try boot into download that same set of messages come up and keep looping. anyone know wtf is going on lol
Have you referred this thread: http://forum.xda-developers.com/showthread.php?t=3488114
It also gives the same steps as the paste.bin site.
If you want to repartition your sd card, then you might have to use the EPM.
You can find all that you need, in the thread mentioned above.
Reporting Via N910G
constant looping
yashthemw said:
Have you referred this thread: http://forum.xda-developers.com/showthread.php?t=3488114
It also gives the same steps as the paste.bin site.
If you want to repartition your sd card, then you might have to use the EPM.
You can find all that you need, in the thread mentioned above.
Reporting Via N910G
Click to expand...
Click to collapse
hi thanks. the only problem is that now the phone only shows this message and nothing else no matter what i do.
boot recovery mode (in green)
check boot partitions
copy from t-flash
boot recovery
write 54464 sectors..
reboot
and it keeps rebooting then showing the message again and again.
bump
bump again? please surely someone has a solution . i dont want to move to another phone and then see my note 4 as a paper weight.
?????
dead4ngel said:
?????
Click to expand...
Click to collapse
Try this assuming you can get to Download Mode, credits to https://forum.xda-developers.com/showpost.php?p=70652492&postcount=10
Mi A1 bricked, hard resetted it by opening the back cover and shorting two points.
It gets detected by mi flash tool but I cannot flash the stock room. It is giving me "cannot receive hello packet" and then it times out.
Any help will be appreciated.
Thank you.
I'm in the same boat, it's showing up in device manager under ports (COMS & LPT) and in flash tool, yet i cant flash anything
Any help for us?
foggs said:
I'm in the same boat, it's showing up in device manager under ports (COMS & LPT) and in flash tool, yet i cant flash anything
Any help for us?
Click to expand...
Click to collapse
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
udaan said:
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
I've also tried different ports, still the same message of the hello packet thing. Also when I have the phone connected to the computer I've a white led light blinking.
From reading other threads here and Xiaomi site the deep flash cable opens the com port, I already have this but won't work. There was something about a loader.img, flashing this to an sdcard and holding power and vol down button it then should boot the loader IMG and rescue the phone, this also fails for me.
foggs said:
I've also tried different ports, still the same message of the hello packet thing. Also when I have the phone connected to the computer I've a white led light blinking.
From reading other threads here and Xiaomi site the deep flash cable opens the com port, I already have this but won't work. There was something about a loader.img, flashing this to an sdcard and holding power and vol down button it then should boot the loader IMG and rescue the phone, this also fails for me.
Click to expand...
Click to collapse
Yup, I ruined one of my usb-C cable trying do do deep flash that way. I failed, so I went to one repair shop and open up the device and did the "two point short thing", which helped to be recognized by the flash tool. Then it showed me that "hello packet" thing.
Then I dug around the Internet for couple of hours and changed the USB port on laptop. I also restarted the laptop after I reinstalled the drivers. Then it actually flashed that ROM I mentioned above. But just that ROM. I tried the latest to oldest versions and all of those ROM would flash but then they will brick the phone again. Only that one worked, i.e. helped me to get to bootloader. But alas it is stuck there, no matter how many times I clean flashed it, it is refusing to boot to system. It gives me "Your SYSTEM HAS BEEN DESTROYED" message on every boot. It only goes to bootloader if I press Volume Up + Power button while booting. And it's a dead end for now. I don't know what else to do.
Also this phone was bought in Hong Kong and its warranty won't work where I am right now. I already took it to the authorized service center and those lazy people told me to change the motherboard and it will cost around $180. So I took it back. lol
Disable driver enforcment to get the hello packet.
TrueMS said:
Disable driver enforcment to get the hello packet.
Click to expand...
Click to collapse
still no hello packet
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
:victory: Held the power button, clicked flash.. Success :good: it's in the process of flashing now. Thank you
Edit: successful flash now to just let it charge up. Thanks again guys for the help/suggestions ?
Update, i flashed the Oreo stock it gave my a successful flash, let the phone charge to near full. Booted the phone up, got as far as sending information to Google option and the screen became non responsive and the phone rebooted, it did this a few times and I gave up and put it in fastboot mode.
I did another flash using a different option clean flash still with Oreo ROM, I think first time I did it with keeping data not 100% though.. but ended up with the same result of it going into random reboots at different points in the setting the phone up stage.
I've now tried two 7.1.2 stock ROMs with the same results ???
I'll try a custom ROM tomorrow see if that sorts it, if not I'm out of ideas. So freaking close ?
foggs said:
Update, i flashed the Oreo stock it gave my a successful flash, let the phone charge to near full. Booted the phone up, got as far as sending information to Google option and the screen became non responsive and the phone rebooted, it did this a few times and I gave up and put it in fastboot mode.
I did another flash using a different option clean flash still with Oreo ROM, I think first time I did it with keeping data not 100% though.. but ended up with the same result of it going into random reboots at different points in the setting the phone up stage.
I've now tried two 7.1.2 stock ROMs with the same results ???
I'll try a custom ROM tomorrow see if that sorts it, if not I'm out of ideas. So freaking close ?
Click to expand...
Click to collapse
Ur presist partition is damaged..thr are many guides here about recovering it
Do the "factory flash" mode in MiFlash under EDL mode as a last resort. May wipe your IMEI and MAC's, not sure.
Could not receive magic packet is solved by using USB2 port, Windows 7 x86 (32-bit) in a VM, or power-cycling the device and starting over, any or all of the above.
Deep flash cable is only for kicking the phone out of diagnostic mode and into QDFlash mode. Not necessary if using test point. I had to use testpoint method myself, couldn't get deepflash cable to work for getting out of diagnostic mode. I hope I can get it working next time though when I inevitably brick it from repartitioning; as I broke my screen when disassembling
apexashwin said:
Ur presist partition is damaged..thr are many guides here about recovering it
Click to expand...
Click to collapse
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
foggs said:
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
Click to expand...
Click to collapse
Did you find the guide about fixing constant reboot? It's around somewhere, might be on MIUI forum.
foggs said:
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
Click to expand...
Click to collapse
Please try presist resurrector from guides section
I think i've got it back to life.
first tried to flash 7.1.2 stock the earliest one (tissot_images_7.8.23_7.1), it hung on flashing it for nearly an hour with no success, closed the miflash application then tried another 7.1.2 (tissot_images_7.10.30_7.1)flash successful, then in stalled twrp did the persist command and reboot nearly got to the home screen just never getting over the line. then i flashed January 8.0 oreo (tissot_images_8.1.10_8.0) and was able to get on to the home screen/go into settings/enable developer options but it would eventually reboot itself, went back into twrp and did the persist command again and reboot.. success (fingers crossed) now downloading/applying April security update as i type this.
Boo installation problem with the update
looks like i lost my imei, https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190 this is going to be a pain.. i'll post back when i try this. need a break from this mess ive made lol
thanks for the help/suggestions appreciated big time.
edit: up to the latest update April 1 security patch.
all done, down to 7.8.23 rom, did the stuff to get the imei back then flashed latest oreo rom
emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
Man, I was trying to fix my Redmi Note 4X for the past 6 hours and you were the ONLY guy to talk about this. Thank you so much. :victory:
THANK YOU
udaan said:
it was solved after i changed the usb port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then twrp. But after flashing aosp extended rom it gave me "the system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
man you just solved my problem and saved for me like 180 eur thank you you are a god !!!! Thanks for using this site !!!!!!!!!! <3 <3 <3
udaan said:
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
I was unable to flash on MiFlash and after changing USB port I managed to do it!.
Many thanks!
emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
I love you!
Hey there guys i think im having a major problem.
i tried to flash Magisk-v16.0 in 7to TWRP 3.1.1. but after a succesful i forgot to clean cash and system.
And after the reboot i got this message on my screen in yellow letters.
Your device has loaded a different operating system.
ID..........
Your device will shutdown in 30 seconds..
I tried to boot in download mode pwr button , vol-
and also to boot in recovery but no luck because i get immediately the screen with the message above.
And also tried to fastboot or adb but the pc dont recornize the the phone/
So i hope somebody wil and can help me thanks for reading
GReetz Jorrit
PS Sorry for my bad english
Hey LUcky me i fixed my phone with OST after a couple of hours it worked for me also the guide unbrick your Nokia 5
But i tried these guides before i posted this post and now it worked so
I am at a loss here. After almost 2 years of working flawlessly, my s5e won't boot.
The screen got frozen while using anydesk, and had to force a restart (power button + up and fown volume buttons).
I can see the Samsung logo for less than a second, and then it switches off. Without touching anything, after some seconds the same thing happens.
I tried charching it and similar behaviour: i see charging circle for less than a second, and off again.
I AM AT A LOSS.
I managed to boot it pressing power+volume_up buttons and this is what i see (attached). It can stay like that for a long time so I guess battery and it's connection to the tablet are fine.
PLEASE ANY HELP WOULD BE VERY WELCOME
UPDATE:
I have tried MANY things in the 6 hours since I wrote this post. I am able to put the tablet in download mode and ODIN (and my PC) recognizes it. I am able to flash VBMETA but now TWRP (fail).
At some point the tablet rebooted in normal mode (why?) but got frozen again and had to reboot it.
Anyone can point me to how to recover it? I don't mind right now to loose what is in the internal memory.
Did you try to hard reboot (power_button + volume_down ) for more than 9 seconds.
If did not work then you may have to charge the phone? If its fully charged try to flash stock rom using Odin. When your device does not boot that means the stock firmware is corrupted and needs to be flashed again. That happened to me before and now my phone is working fine. Wanna know how to flash it? Look it up online!
Abd El-Rahman El-Batal said:
Did you try to hard reboot (power_button + volume_down ) for more than 9 seconds.
If did not work then you may have to charge the phone? If its fully charged try to flash stock rom using Odin. When your device does not boot that means the stock firmware is corrupted and needs to be flashed again. That happened to me before and now my phone is working fine. Wanna know how to flash it? Look it up online!
Click to expand...
Click to collapse
I did try a hard reboot. Same result. I already rooted and installed a custom rom on it (first thing i did).
Twrp is installed but I'm unable to boot to it.
Any more ideas?
iruiz2 said:
I did try a hard reboot. Same result. I already rooted and installed a custom rom on it (first thing i did).
Twrp is installed but I'm unable to boot to it.
Any more ideas?
Click to expand...
Click to collapse
Listen up carefully. There is a truck to boot into recovery. When you hard reboot screen will turn black then show logo. While screen is
Black quick hold vol up button and power.
Worked on my galaxy a10. Tell meh the results bro
Abd El-Rahman El-Batal said:
Listen up carefully. There is a truck to boot into recovery. When you hard reboot screen will turn black then show logo. While screen is
Black quick hold vol up button and power.
Worked on my galaxy a10. Tell meh the results bro
Click to expand...
Click to collapse
It just loads the screen attached in my first post.
Try flash via Odin, it still in download mode with this warning.
The tablet was still covered by warranty so I called the seller and they took it to a Samsung repair store. They replaced the motherboard, so I guess it was not recoverable.
The bad news is that they updated to android 11, I was quite happy with old 9.0 because I had TWRP and Magisk working.
Thank you for all that tried to help.