I have a mojo that will not boot properly. I have flashed many of these boxes and never had any issues. This was fully working 12.1 that I gave to a friend about a year ago. When plugged in it does absolutely nothing I found with USB plugged in and rapidly plugging and unplugging the power I can get into fastboot. Through fastboot I can get to TWRP and from there I have re flashed rom tried 202ww 205 and even restored backup no matter what it will not boot not even back to TWRP without fast boot command also have to do the rapid plug and unplug of the power I have found that I can boot into the ROMs by loading the boot.img through fast boot. I have even tried factory reset through Android but it does nothing everything still appears. This is now over my head and I'm not sure what to do. I do have another fully-working unit here but I don't even know what files would help me or if they would. Thank you all in advance this is a great forum and I would not have gotten anywhere without it
Hi Kal357, it sounds similar to an issue i had with a phone, where in a nutshell the storage became corrupt, and ran in write protect mode. So I could boot to TWRP, flash a ROM, reboot, but be back at square one... was a bit like ground hog day... the end result was binning it unfortunately. That said I do hope that this isn't your problem.
Thank you for replying. I kind of hoped more people would respond buy now. As far as write protect wouldn't make much sense as I have flashed different ROMs and been able to fully boot into the rom. Then again I don't even know what to think anymore? does anyone think I should be posting this somewhere else? I do not have any social media Accounts.
Related
Hi all,
Yesterday my Jiayu S3 crashed and rebooted, after setting an alarm clock and using the Spotify app. However, it did not reboot into the OS as usual. It did not even show the Jiayu logo, but the phone vibrated (sign that it's booting), screen turned on, phone turned off again, repeating this cycle over and over (not the traditional bootloop as I know it). I was running a rom based on the original rom, with some slight modifications. This rom was running stable for more than a week. I know my way around Android, and am used to switching roms, flashing etc.
Right away, I checked the following things:
- Battery removal didn't help (I did not forget to put it in again ofcourse )
- Phone doesn't go into it's charging cycle when charger is connected
- I do NOT have access to recovery
- I can, however, access the boot menu (Volume up + power key, options: Normal boot, recovery, fastboot)
- I can get into fastboot mode (haven't tested ADB yet), that's the only thing that's still working
I tried to flash the original firmware using SP flashtool, and I am still able to upload firmware on the phone! I am sure that I'm using the correct ROM, and tried different PC's and drivers. Got a few succesful flashes, but still bootlooping.
I also had the idea that my battery was empty (didn't charge it overnight), and measured the battery at 3.52 V. So it was pretty empty but not that empty that it doesn't boot. In an effort to charge the phone, I left it bootlooping for an hour or so, and later on it turned out that it only drained the battery further, 2.99 V.
I didn't want to kill this battery so I did use 2 other batteries from an old Jiayu G4, which appear to work if you turn them around and hold them against the pins (note: I knew what I was doing here ). After a lot of Googling, and seeing a lot of generic "how to fix any brick" stuff I was not able to revive my phone again.
I still believe (and hope) that the error is on the software side of the phone. All the partitions should be ok and in working order according to SP flashtool.
Now this is where my knowledge stops and where (hopefully) your help comes in. What can be corrupted that I haven't checked yet? Do you guys have any suggestions to revive this "high-end" phone again? Once again, it did not happen because of bad flashing or something like that, it happened randomly when I was using the phone normally. I tried to be as accurate as possible (long story), but if there are any questions I'm happy to answer them.
Any suggestion is welcome!
Thanks in advance.
Bump..
Anyone?
bump
So, my friend came down to visit in FL from GA.. Her phone ended up snapping in half, but she found an older one in her car. We have since been trying to fix said phone, but nothing has worked. I've used Odin to try and install an OG firmware (which is nearly impossible to find, might I add) and that didn't work. It only made the bootloop issue worse. I also tried to use Odin to put TWRP on it, which showed signs of hope, but gave no real progress to the issue. The recovery menu doesn't exist. The power + vol up + home button doesn't boot to recovery which is why I figured I'd try a custom one. ADB doesn't work because USB debugging wasn't turned on before the phone got destroyed. Idk what happened to the phone before to cause this, neither does she. We simply found it in her car this way. She's going back tomorrow, but has no GPS to find her way, so I'm in desperate need of help. I've tried almost everything I can think of and this stupid phone still won't boot to recovery. I know if I can get it to recovery, I can fix it. Google hasn't been much help either. Everyone always suggests recovery mode, but I can't get to recovery.
Thanks for any help, guys.
Edit: Model # - SM-S920L
Hi.
So, I decided to root my 3s. Googled some instructions, everything went fine and I installed TWRP and SuperSU. Well, it turned out that a certain app won't work on a rooted device, and simply unrooting via SuperSU isn't good enough either - it seemed that the only way to make it work again is to flash a new ROM.
I downloaded an (official) recovery one, tried to flash it with TWRP... bootloop. I probably messed up and did something incorrectly; even recovery mode stopped working. Fastboot, thankfully, still did, so I got another (bootloader) ROM and tried MiFlash.
Except it didn't work that great either, eventually getting stuck on 100% and never finishing. What's even worse, when I was about to try again with EDL, the phone ran out of charge - now, when connected to a charger, it automatically powers on, shows the same bootlooped MI logo for about half a minute, then seemingly runs out of power and turns off - only to reboot again and repeat the process. Fastboot still works, but with so little time it's nigh impossible to do anything with. It feels like I'm out of options.
Any advice would be really appreciated.
EDIT: Managed to get into TWRP directly and can charge the phone now, so situation looks far less grim. Advice would still be helpful, but I'm pretty confident I can handle it now. Thanks for reading anyway!
I just aquired a used Nexus 10 that I wanted to flash with Lineage. Before that, I had successfully flashed every android device I have ever owned, so I thought there'd be no problem. After unlocking the bootloader I tried flashing TWRP recovery (on Linux using fastboot in the terminal), but it took several minutes and when suddenly the sreen started flickering and the flash still wasn't done, I tried to CTRL+C to no avail. I figured that I'd at most corrupt the recovery which would be quite fixable, so I unplugged the cable and tried restarting the tablet. I could still select the options in the bootloader, but when I selected anything, it didn't work (not even shutdown).
Whenever I try to start the tablet now, nothing happens. When it is plugged in to the wall, it shortly shows the "full battery" symbol and the goes black again. No combinations for bootloader or recovery work anymore. I suspect that the unsuccessful flash corrupted the bootloader, so how could I fix that. I do have FTDI and STM32 flashing devices, if that is any help.
P.S.: I already tried removing the battery in case there was anything in volatile memory preventing the boot.
I kind of jumped the gun on this one. As I had suspected, aborting the recovery flash did not corrupt the bootloader. The solution was simply an empty battery. I didn't notice, because it showed me a full 100% when I initially tested it, so it might be a broken battery, after all.
But still, got it to work now. Thanks for this great community, I could not have learned all the android stuff without it.
Atreus said:
I kind of jumped the gun on this one. As I had suspected, aborting the recovery flash did not corrupt the bootloader. The solution was simply an empty battery. I didn't notice, because it showed me a full 100% when I initially tested it, so it might be a broken battery, after all.
But still, got it to work now. Thanks for this great community, I could not have learned all the android stuff without it.
Click to expand...
Click to collapse
Good to hear:good:
Please mark your thread as [SOLVED] if it is, or give us an update on how did you go about the battery perhaps?
Cheers
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"...