Hello there, hope you are doing fine.
I been using my OnePlus One phone for a long time with no problems until now, when I tried to update to the latest LineageOS.
During the process I did, by mistake I wiped all the data in the phone thinking I was formatting but ended up also deleting the OS.
Currently my phone is in a a FastBoot Loop with nothing else.
Can't access anything.
This is the 2nd time it happened to me and I fixed it the first time.
That happened like 2-3 years ago and I don't have the means to do it again.
I have been searching for a solution around the internet for the last 2-3 days but with no success.
Most "solutions" I have found have missing steps (due to broken links or old apps, etc...)
ALL IN ALL
1. FastBoot Loop
(Now even with a new problem that every time I reboot it even goes into "Low Battery / FastBoot Loop" even though my battery is probably full)
2. OEM Not Unlocked
(Even though the ADB "fastboot oem unlock" command completes successfully in the end it does not unlock it)
3. No OS
(Can't access anything else, not sideload, not recovery, not system, not bootloader)
Would love if anyone could help me with this one.
GOD BLESS!
Trying to fix the "low battery / fastboot loop"
Not sure if this is working properly cause the command doesn't show anything.
Could it be cause it has no OS?
So your phone reboot only Fastboot?
TheXIX said:
Trying to fix the "low battery / fastboot loop"
Not sure if this is working properly cause the command doesn't show anything.
Could it be cause it has no OS
Click to expand...
Click to collapse
No. Even the phone has no OS it's still said low battery when your phone's battery it's too low
Related
Hello,
So here it how it goes:
My N5 freezes suddenly and shortly after it goes into a bootloop ( stuck at Google logo ). And from there on, the only thing I can do is just go into the bootloader.
If I go to recovery mode I can see that I get "msm_sdcc.1/by-name/misc no such directory" or something like that.
The only thing that helps make this issue dissapear is performing an oem unlock in fastboot mode, but this is not a good solution since this is the 2nd time it has happened to me in the past 3 months.
What do you guys suggest I should check/do to prevent this issue from ever happening?
Thanks!
Does the bootloader relock itself at reboot? If it does, the emmc chip is going or gone.
@audit13
The bootloader doesn't relock itself. It remains unlocked even after reboot.
I just unlock it to perform this "trick" that helps me get out of the bootloop. ( also after unlocking it, I perform a fastboot oem lock, done this both times ).
Also, don't know if it is related, when i go into recovery mode i get the android with an X or an ! (forgot which one) which is most probably due to files missing.
The screen with the dead android is normal. No need to relock the bootloader in my opinion.
Have your tried flashing a completely stock rom, including th userdata.img file to see if that solves the issue?
@audit13 Wanted to keep the stock rom with which it had come. Also doesn't an update ( from L to M for example) change the rom completely?
An ota update will move the phone to the latest of the current version (e.g. 5.0 to 5.01). The the ota will move from LP to mm.
Personally, I prefer mm.
So.. The phone did it again today, same behavior, same result ( bootloop out of nowhere ). This time I performed a complete new install of the OS ( wipe cache, factory reset + reflashed a factory image).
At this moment the phone is working as usual and now I will wait and see if the issue reoccurs (hope not).
If someone else has any other ideas an how to prevent or read some logs from the phone ( even if I performed an oem unlock ) please reply.
EDIT: title is incorrect, model is actually S2109A-F
Hi, I'm pretty novice but have searched a solid 2 days about this topic on this device.
The lenovo a2109a-f I recently got (I know, its like 4-5 years old, but for 40$, not a bad 9+" tablet) was in fine working order, but did have some bloatware. Feeling ballsy, I attempted a root, and now it boot loops, meaning it will constantly reboot and show the animated splash screen, and play the synthetic chime sound. Each loop lasts about 1-2 minutes.
Since I can still access the fastboot and the boot recovery I've tried the following:
1) attempt the install of a new rom (original ICS or JB for this device) from a micro SD card inserted into the slot
- no go, it says it mounts the sd card, but wont read from it
2) attempt factor reset (cache, factory reset etc)
- no change and same root file still shows up in the tablet "/sdcard/"
3) Rerun the flash recovery process
- Tablet seems to accept linux (from windows) commands via cmd (fastboot -i <address/commands go here>), but no change for the boot loop
4) attempted other recovery images in fastboot mode
- thought I actually damaged it more. Since it stopped boot looping but wouldn't even boot to recovery at all. I then flashed the original recovery ("CWM_S2109.img") and was able to get the bootloader back and the bootlooping behavior again.
My question for you all, is there something I need to do via the fastboot method to clear the cache of the bootloader, or the memory of the device and install the bootloader that way and hope it accepts a basic OEM rom? Again, I'm no programmer, but am able to follow instructions and would love to be able to fix my 40$ mistake here sometime. Thanks in advance for all your help. I've used a lot of your tips and resources here over the years and have learned a lot from your skills and experience.
Hello, so i was using my phone last night browsing instagram, when all of a sudden it froze and restarted(happened to me from time to time), so i thought it will bootloop for a few times and it will boot up just fine. But no. It got stuck there and i could access recovery only when my phone has been off for 10 minutes, and fastboot was accessible at will. I accessed recovery a few times, and i tried:
Wiping cache and delvik cache - No luck
Let it charge into recovery to 100% overnight and try flashing in the morning
Wiping data - no luck
Re-flashing sultan rom - no luck, phone just freezes halfway into installation and restarts
Since i can only access fastboot, i tried some fastboot commands, but nothing serious(like flashing, formatting, wiping...), and cmd shows that they were successfully executed, but nothing happens with phone ("fastboot reboot" cmd)
Removing sim card - no luck (but i am desperate)
Usually when reboots happen, i can plug it in a charger, and it will power on with battery charging animation, but not these times, it just reboots at oneplus logo
On one occasion it got past the oneplus logo, and showed a small blue cyanogen circle, but it froze there as well.
I did not try sideloading, and nothing with adb, since i am not experienced in those fields
I had similar thing happen to me the night before, but it eventually turned on and i could use it whole day without reboots
Also it seems to have happened both times while battery was at around 15%
I live in a small city in Serbia where there are no professional who know these kinds of phones, so i can't take it to repair shop.
EDIT: I can enter sideload if that matters, and my pc seems to detect it, because i can hear windows chime
EDIT 2: i can no longer enter recovery, it just wont enter there anymore
Tried flashing twrp via fastboot but i get (command write failed too many links) error
I tried some repair shops they said it's the motherboard, so is it really dead, because i still have oneplus logo
Any suggestions?
MY FIX
I connected my phone to friends laptop and flashed stock cyanogen os 6.0.1, fastboot worked like charm and phone booted up just fine
Recently I found out my device having battery drain quicker than normal, then I decided to do a factory reset. But the factory reset is taking much longer than usual (usually its around 4-5minutes but this one takes more than 10 min). I thought there must be something wrong and I decided to do a factory image flash.
When I tried to unlock the bootloader the device freezes at the screen where there's two option (unlock or do not unlock) after I selected the unlock option. Waiting did not help so I did the good ol power up + volume down combo and the device arrive at bootloader mode unlocked. I then proceed to do the factory image flash and at the end of the it says
Erasing 'userdata' FAILED ERR(Check device console) <-- something along those lines
and the device does not auto reboot after the flashing is done like it normally does
It took a few reboot to get the device to setup screen and after the setup the device is working fine (for now) and the battery drain still persists.
Any idea on what is going on with my devices? I've tried factory image flashing and sideloading ota updates with no problem and this is the first time I encountered one. Any help would be appreciated :fingers-crossed:
Did you read this https://developers.google.com/android/images especially the part that starts with For Pixel 2 XL only. I would also make sure you have the latest platform tools and try a 2.0 usb port and maybe a different cable .
Hi,
Since yesterday, my phone suddenly went into a bootloop (I wasn't even using it, but it suddenly started vibrating every half a minute or so). I'm able to get into fastboot mode, but from there if I try to boot into TWRP, it just shows the splash screen for a bit, and then crashes and reboots again. I should say that this is my brother's old phone he gave to me, so I'm not exactly sure what he's done to it, and I'm also not particularly familiar with Android stuff myself.
Is there anything I could try to retrieve data from the device? I've managed to run a different recovery img (included in here: https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_One/), which allowed me to use ADB from my MacBook, and from there I tried to use the adb backup command, but this just gives me "Now unlock your device and confirm the backup operation..." without actually showing anything on the phone.
And even if I can't recover anything, is there anything I could try to bring the device back into a working state?
since your fastboot is working, you can try downloading the bacon roottoolkit and restore stock rom, before doing that install all the drivers like it mentions in the app. https://androidfilehost.com/?fid=95916177934555863;
Let me know if this works