So i was trying to create a bootable usb for linux from my phone. I'm 90% sure my usb was mounted at /dev/block/sda, i did my "dd" command and unplugged the usb only to notice it was unchanged and my device was frozen. After powering off, i was brought directly to the download boot.
So first I tried flashing mu stock firmware, then i tried flashing Lineage Os with twrp. The boot logo just continues. I tried formatting with twrp, wiping cache with default recovery. I tried recovery. I just keep getting an error about EFS not mounting, but i thought that only affects radios/modems.
I don't know what to do Any ideas?
Related
Hi,
I'm trying to bring my N5 to life. It has bootloop on Google logo (sometimes stuck on android animation). When i got it it was stock and unrooted. Computer can see the device, adb and flashtool works fine. What i tried to do:
- erase cache and userdata,
- factory reset
- change recovery to TWRP (tried CWM too, both works)
- flashing the factory images (all from 4.4 to 6.0.1)
- flashing factory image using this tool: http://forum.xda-developers.com/goo...kit-v2-2-kwonggers-nexus-5-one-t2508817/page5
- fix persist partition using this solution: http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576 -when I'm doing this, adb see my device and after using these commands I got only something like: clean, 15/1024 files, 1109/4096 blocks, it is not asking my about repair or change anything...
Unfortunately, it still has got bootloop. I can't go into recovery when I'm using usb cable, I can start it only without cable and then plug it in. (When it is on and I'm trying to turn on recovery mode it has bootloop on Google logo).
Have you got any ideas what can I do now? Is there a way to fix it?
Try this: manually flash every partition from the stock ROM, including the userdata.img.
After flashing the userdata.img file, immediately boot into stock recovery using the power and volume buttons and perform a factory wipe.
Hey, thank you for your answer. Unfortunately after flashing every partition and factory wipe it still has bootloop. But before i did it, it wanted to charge my Nexus, I just plug USB and suddenly I realised that there is a Welcome screen! Everything was running good, WiFi was working... I turned on USB debugging and reboot it to check what happens, but it won't turn on again, now it is again with bootloop Any other ideas?
Hi,
Yesterday i was trying to switch from lineage os to the last version of resurrection remix, so I downloaded the file on RR's website, and did a nandroid back up on my OPO (i'm rooted with TWRP installed) including system, data and boot partitions.
I did a full wipe (system, cache, dalvik cache and data), then I flashed the RR's zip file, gapps, and restored only the data partition. When I boot on RR there's a black screen showing an error message "System UI has stopped working" and another "com.android.phone has stopped". So I just long pressed my power button, restart -> recovery, and restored the boot partition from my nandroid back up. Then when I try to boot I'm stucked in a bootloop and I can't go back to recovery since my volume buttons are broken (broke the flex cable when repairing my screen).
Now I think there are 2 solutions, either changing volume buttons (which means desoldering and soldering :/ ) or there is a solution with adb.
If you have any solutions, thank you in advance !
Had the same issue with the same processes and I just had to factory reset from recovery to fix it. Now the real issue are the volume buttons now, because if you didn't enable adb and gave permissions to your PC you can't use it.
Ok so i managed to replace the volume flex cable, but now i have another problem : after i failed to flash RR, i did a factory reset and tried to restore a nandroid back up (that i made just before i repaired the volume butttons) and now the phone won't boot and keeps booting on twrp... That is REALLY frustrating, please help !
croustiman27 said:
Ok so i managed to replace the volume flex cable, but now i have another problem : after i failed to flash RR, i did a factory reset and tried to restore a nandroid back up (that i made just before i repaired the volume butttons) and now the phone won't boot and keeps booting on twrp... That is REALLY frustrating, please help !
Click to expand...
Click to collapse
Try dirty flashing the ROM zip, data won't be touched and boot/system will be re-flashed. Hope it works.
I can flash roms : i flashed lineage os, tugapower... etc
For example yesterday, i pushed the latest lineage os zip file (via adb push) and flashed it. TWRP says installation is sucessful then when I reboot, its still TWRP... I went on several forums, and flashed a stock oneplus recovery. Now my phone is stuck on a bootloop with oneplus logo only, and I can't access the recovery or fastboot mode even pressing the volume keys I'm afraid I have to buy another phone...
Also i noticed that when i try to reboot with the phone being connected to the computer via USB, the phone just shuts down and i have to disconnect and reconnect the battery ribbon inside the phone so it can reboot
Up !
Hi,
I had installed TWRP 2.8.5 on Galaxy Note 4. I did a factory data reset, and formatted all the system and the data partitions as my device was encrypted. I restarted my phone, and as expected it wouldn't be able to boot to an OS as I had formatted everything, but I was hoping to get into the recovery menu, but it just shows the TWRP splash image, and the screen switches off, it again activates shows a the splash image for a second and then goes blank, and does this again, it does not load into the recovery menu. I tried installing the recovery menu again via odin but experienced the same error. Can you please advise on what should be done?
Thank you
The internal storage was empty (showing 0mb) after flashing twrp. So, I wiped and everything. Then, it showed but when I tried to boot to system, it boot looped.
I have flashed the stock firmware so it is back to normal.
The 2nd time I flashed a custom kernel before twrp and also flashed the no verity opt encrypt but this time when booting to system, it showed the Samsung logo and shut down. The internal storage was not mounted this time too.
Device: MT6572 'One Touch Pop C1' 4015A
Summary:
I have an old mobile phone that, after doing a 'wipe cache' in stock recovery, got stuck in an infinite boot loop in recovery mode and continued the task of 'formatting/cache...'.
Hello, I was trying to recover an old Android phone that was stuck on the startup logo. The first thing I tried was to see if I could enter recovery mode, and I was able to do so. Then, I had doubts about whether to do a factory reset or just try deleting the cache. Finally, I decided to try deleting the cache, but it caused the problem I describe in the summary.
I tried flashing the stock ROM with 'SP Flash Tool', but even though the tool said it flashed correctly, I don't think it's working because after several supposedly successful flash attempts, I tried formatting the entire flash and the mobile phone still kept booting into recovery mode. Shouldn't it be dead? I also tried flashing a corrupt recovery, but it's still the same.
'SP Flash Tool' connects to the preloader MTK port and transfers at a speed of 15mb/s. Is that okay, or is it a ghost transfer? It seems very fast considering the writing speed of the internal memory.
Translated with chatGPT.