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
Related
I want to start out stating that i am very familiar with android's but have never experienced anything like this.
The first thing I tried was to oem unlock it from fastboot, which it claimed to do however i am skeptical as nothing else seems to stick, attempted to install cwm and TWRP neither with any success, even though it says the action was performed successfully.
The strangest thing is that i deleted all the apps on the device from settings/app, but when i rebooted my device they all came back!
All i wanted to do was do a factory reset, which also claims to finish successfully but after rebooting from recovery mode, i am back where i started.
App Updates also do not work as every time the tablet reboots, the apps have to be re-updated.
Its like the tablet is stuck in a read only state and when it reboots all changes are lost.
Like i said, this thing is acting weird and i have no idea where to go from here. Any help would be greatly appreciated!
[Update: Tried RSDLite, same results, Result is PASS however after system reboot everything is the same.]
Another update, tried downloading HWI69 which is the stock rom, tried to fastboot each image but nothing sticks even though it seems to say it writes it to the system. I'm starting to think the NAND memory is locked up and cannot be written to anymore if that's even a possibility.
BUMP
So it started out that CM 12 kept shutting down on me, the phone would occasionally just power off. I tried restoring some of my TWRP backups but they seemed to be corrupted.
So I decided to try RSD and reflash the stock firmware and go back to 4.4. I let it flash and then when I booted up I kept getting a message saying that the phone was going into cool down mode, but the phone never actually got hot. So I decided to try and reflash the stock 4.4 firmware again in RSD. This time I watched the phone screen as it went through and just after the system image (#7 of 17) I would get a message in "RED" letters that reads "sp space is not enough". It would continue to flash the rest of the images and then reboot. And it would have the same problem with saying the phone is going into cool down mode and sometimes it would shut off, but the phone never gets hot.
I thought maybe I had a bad download / firmware image so I tried several 4.4 images including one directly from Motorola but I get the same message every time I flash the stock 4.4 ROM.
*While it is plugged into the computer the phone stays on, but once I disconnect from the computer it shuts down again.
So I thought I would try flashing TWRP and CM 11 and then CM12, but the phone will boot up and then shortly after boot up it will shut down.
I have spent hours looking for a solution online and I do find that there have been multiple reports of this same problem along with photos of the phone screen message, but I have not found an explanation or a solution.
Does anyone have any idea what the problem is or how to fix it?
morr22066 said:
So it started out that CM 12 kept shutting down on me, the phone would occasionally just power off. I tried restoring some of my TWRP backups but they seemed to be corrupted.
So I decided to try RSD and reflash the stock firmware and go back to 4.4. I let it flash and then when I booted up I kept getting a message saying that the phone was going into cool down mode, but the phone never actually got hot. So I decided to try and reflash the stock 4.4 firmware again in RSD. This time I watched the phone screen as it went through and just after the system image (#7 of 17) I would get a message in "RED" letters that reads "sp space is not enough". It would continue to flash the rest of the images and then reboot. And it would have the same problem with saying the phone is going into cool down mode and sometimes it would shut off, but the phone never gets hot.
I thought maybe I had a bad download / firmware image so I tried several 4.4 images including one directly from Motorola but I get the same message every time I flash the stock 4.4 ROM.
*While it is plugged into the computer the phone stays on, but once I disconnect from the computer it shuts down again.
So I thought I would try flashing TWRP and CM 11 and then CM12, but the phone will boot up and then shortly after boot up it will shut down.
I have spent hours looking for a solution online and I do find that there have been multiple reports of this same problem along with photos of the phone screen message, but I have not found an explanation or a solution.
Does anyone have any idea what the problem is or how to fix it?
Click to expand...
Click to collapse
I had tried everything I could think of and it appeared that there was a partition problem. The phone continued to shut down and would only stay on while connected to the PC. If it were a PC I would reformat and re-partition the drive but I did not want to risk a permanent brick by messing with it.
So, as a last ditch effort to try and get my phone functioning again I let it download and install system updates. The phone is now working again, it has not shut down at all and there have been no warning messages about cool down mode.
BUT, I am now on "4.4.4, SU-5-24, build 23.3.24 dated 10-27-14. Since my boot loader is unlocked I flashed TWRP but it would not not accept Super SU zip so I am no longer rooted.
I finished reading up on it in the forums and realize I am pretty much screwed as far as root goes. But at this point I don't even care anymore. I just need to get the phone functioning correctly.
*So, I am still having the problem with flashing stock and getting the "red" letter message after system image boots saying "sp space not enough". So long as it is hooked up to the computer it stays on and if it is downloading or installing an update it stays on and I never get a warning about cool down mode and it does not shut off, but once I disconnect from the computer it starts all over again. The phone boots up but at random intervals it still either gets a pop up message saying that it has gone into "cool down mode" or it shuts off. It is not doing it as often as before, but it is still doing it. Does anyone have any suggestions on whats causing it or how to fix it? It sounds like a software / firmware issue but I am not sure how to fix it.
*Update. The phone is still not functioning correctly. At times it will appear to work fine for hours with frequent to heavy use at times then suddenly it will start acting up, the phone will shut down randomly and when it reboots some of my settings have changed. The temperature is usually pretty low but once in a while after a shut down I will check the temp when I'm able to reboot it and it will be high. When it shuts down like that I usually have trouble getting it to boot up again unless I plug in the factory cable, either in the PC or just the wall charge then it seems to boot up fine and I can even reboot it but once it shuts itself down it doesn't want to start again unless I use the factory cable.
It really does sound like a software / firmware / partition problem but after multiple attempts to flash the firmware with RSD I continue to get the same error message at the end of the system flash and the phone continues to have problems. Does anyone have any suggestions?
Got me an xt1080 which I'm trying to restore to stock, and in both House of Motor and RSDlite 6.2.4 at some point during the system partition flash 'so space is not enough' as well. The phone is in perpetual bootloop, unless I use a 'Factory/power' cord and starting up in fastboot (eventually). Tried both 1FF and CFC fxz files, no luck.
I was charging my phone overnight. In the morning I realized it didn't charge, I tried to turn it on and it gets stuck on the HTC screen.
I was running Viper One 3.21, I tried rebooting, entered recovery, tried to reinstal a nandroid, got stuck on the screen again.
Tried reinstalling ViperOne same problem.
Here's what I know:
Fastboot will NOT work, while I can get to fastboot, any time I reboot the phone it gets stuck.
I can't get to RUU (because it wont go past the HTC screen).
adb sideload will not work
I've let the battery drain, fully charged it; no change.
I tried wiping and doing a factory reset but it just gets stuck on the reboot, I also noticed on the File manager within TWRP that my phone was never wiped.
Any ideas?
SS823 said:
I was charging my phone overnight. In the morning I realized it didn't charge, I tried to turn it on and it gets stuck on the HTC screen.
I was running Viper One 3.21, I tried rebooting, entered recovery, tried to reinstal a nandroid, got stuck on the screen again.
Tried reinstalling ViperOne same problem.
Here's what I know:
Fastboot will NOT work, while I can get to fastboot, any time I reboot the phone it gets stuck.
I can't get to RUU (because it wont go past the HTC screen).
adb sideload will not work
I've let the battery drain, fully charged it; no change.
I tried wiping and doing a factory reset but it just gets stuck on the reboot, I also noticed on the File manager within TWRP that my phone was never wiped.
Any ideas?
Click to expand...
Click to collapse
Sorta sounds like one of the bricked ones where the entire emmc goes write protected. If you can't get fastboot or ruu mode and have no warranty left I can take a look at it for you. I'm in PA so it wouldn't take long to mail it here.
Not sure how it got bricked, it has been over a month since I flashed anything.
I am able to use adb sideload, but any file I use it says is corrupted.
Could I partition part of the drive and try to instal from there?
What part of PA are you in?
SS823 said:
Not sure how it got bricked, it has been over a month since I flashed anything.
I am able to use adb sideload, but any file I use it says is corrupted.
Could I partition part of the drive and try to instal from there?
What part of PA are you in?
Click to expand...
Click to collapse
I am down in the York/Harrisburg/Lancaster area. You don't want to partition emmc manually.
Urgent help reqd
randomly my nexus 5 restarted
google came on screen and now only those four animated circles are showing up and the phone doesnt go further
went in bootloader but cant wipe cache, cant format, or anything else from there.
usb debuggng must be off as far as i remember
trying to flash through sdk manager. have downloaded image. but stops at "waiting for device" in cmd and it doesnt go any further than that. even tried doing it manually through cmd.
when the phone is connected it is showing the drivers but it isnt installng and can see the yellow exclamation.
manually downloaded the drivers and tried installing manually but shows drivers are up to date.
uninstalled driver and reinstalled but same issue. it is connected to usb 2.0.
now how do i get it to work?
I have tried all the options i could search for on this forum but none of them solved my issue.
Is the bootloader unlocked?
How do i check that?
Ok got it
It is locked
How do i unlock?
I checked some unlocking bootloader threads but they all require usb debugging to be on.
My phone is not starting at all so i cannot do that
How do i go about it now
Tried nexus root toolkit. It isnt detecting the device.
Unlocking will wipe you device.
Google themselves have a guide on how to flash, not sure why you are using toolkits.
Also, you will wipe your device, if you haven't already. Make sure you have the right drivers, make sure you get the device to come up under "fastboot devices"
Already tried all methods mentioned by google or xda.
If you read my initial post my phone is not getting detected as well but shows installing drivers when connected but the installation fails.
Manually install the correct drivers.
Tried that but i get the error that you already have latest drivers. But its not detecting the phone
Try removing the drivers and reinstalling
Also, try different USB ports and cables.
Did all of that a number of times. Still no luck
Other phones are getting connected and detected just fine.
useruser12 said:
Urgent help reqd
randomly my nexus 5 restarted
google came on screen and now only those four animated circles are showing up and the phone doesnt go further
.
Click to expand...
Click to collapse
Hi all, i have a similar problem
this morning my n5 boots into "optimizing apps", but stops when reach around 15/20 apps and reboot (3 or 4 times)...
Now, only keeps in android animation like useruser12.
I can see my data in TWRP, battery 95%...
I wipe cache/dalvik... nothing
I reflash the kernel (ElementalX 6.17), still nothing
Any ideas?
PS: latest news. After make a backup, I made a factory reset and restore a system-boot-cache partition from old backup. Now the phone boots but i hate lose all my data xD. I want try to solve my problem using my "corrupted" backup for avoid losing data. If that fails, I can always restore this functional backup. Any ideas again?
Used the nexus root toolkit.managed to unlock bootloader but immediately the device reboots and goes into the bootloop again.
Tried the flash stock + unroot function as well which detected my factory image and everything went smooth till it came back to unlocking the bootloader and rebooting the device after that and again went into the bootloop
Though i have installed the drivers, on reboot windows 7 automatically starts installing the mtp usb device driver but fails. Manually downloaded the drivers and installed as well.
Still its not worked and whatever i do it comes back and get stuck at the bootloop.
Any expert can give a solution? Thanks
After unlocking the bootloader, does the bootloader relock when the phone is rebooted? If it does, the memory chip is defective.
Phone doesnt reboot completely.goes into a loop after the google logo and doesnt go further.
If i switch off the phone midway here without it booting up and then restart the bootloader then its locked again.
But what i read was that the process of complete reboot needs to finish and i need to turn on usb debugging. So is it because of that the bootloader locks again?
Anyways, this what im facing
Dalamar666 said:
Hi all, i have a similar problem
this morning my n5 boots into "optimizing apps", but stops when reach around 15/20 apps and reboot (3 or 4 times)...
Now, only keeps in android animation like useruser12.
I can see my data in TWRP, battery 95%...
I wipe cache/dalvik... nothing
I reflash the kernel (ElementalX 6.17), still nothing
Any ideas?
PS: latest news. After make a backup, I made a factory reset and restore a system-boot-cache partition from old backup. Now the phone boots but i hate lose all my data xD. I want try to solve my problem using my "corrupted" backup for avoid losing data. If that fails, I can always restore this functional backup. Any ideas again?
Click to expand...
Click to collapse
Lucky that you could do a factory reset. I wasnt even able to do that from the bootloader.
useruser12 said:
Lucky that you could do a factory reset. I wasnt even able to do that from the bootloader.
Click to expand...
Click to collapse
Sorry, i did it via TWRP.
If the bootloader relocks itself upon reboot, it's the memory chip that is damaged.
hello, recently i bought myself a new op6, as it was good for modding and such. unlocked the bootloader, flashed twrp, and rooted it the day after, used it for a couple of days, before I installed elementalX. was happy with that for some days. then I decided I wanted to try out lineageOS, in order to de-google my self, in my quest for privacy.
TL;TR:
mtp is not working after flashing, neither is twrp, cant even access it through fastboot with booting the .img file.
does this have something to do with the a/b partition thing on these phones, perhaps?
I would guess that I flashed lineageOS the wrong way, and that is the issue, but since I cant access twrp, I cant restore and reflash the correct way.
more detailes below
--------------------------------------
backed up before installing elementalX, to have something to go back to, in case of failure
rebooted into twrp, and wiped everything, exept internal storage (i looked this up several places, prior to flashing, that this was the way to do it, so assumed this was the correct way)
flashed lineageOS 15.1
wiped dalvik and rebooted
took ages to boot, so figured id reboot again a couple of times, with no succsess
tried to boot to twrp, to restore back state prior to flashing, but ended up in lineageOS' own recovery.
tried to boot from fastboot, and reflash twrp
goes out of bootloader and screen turns black, led turns on, and nothing. tried waiting for a bit, but nothing seems to happen
have to manually turn of phone, and reboot. tried this several times, but same result.
after reboot i turned to the recovery to look after any solutions there, but nothing
started adb, just to check, and it says "device unauthorized"
sortof gave up, so figured I could atleast get going installing apks, but after downloading f-droid, I couldnt get it to install
found out this was some sort of permission issue, so had to move it to internal storage to get it to install
after installing some apks, I was going to transfer my contacts from my pc, but cant get mtp working..
if someone know a soulution to this, I would be really greatfull, as Im at a loss. cant seem to find anyone who has had a simillar issue..
You can always use EDL and MsmDownloadTool. Check that thread
thanks, will definetly check that out.
now it apears that I have another issue, the key for adb is no longer valid. i did get the prompt when I connected the usb, but that didnt appear to do anything. have tried to revoke it, reanable, reboot both phone and pc, also delete the keys on my pc. I have no root access anymore, so cant really enter the root on my phone, to pull out the keys there, neither can i push my own keys, as it seems atleast. I may be doing it wrong too, for all i know..
If you can enable debugging and see your phone with adb devices, you can adb push /sdcard/<romfile>.zip
I am able to enable debugging mode, yes. Will this enable me to push my own key, or any other existing key for that matter, to remove the unauthorized label?
Id also like to at that i done goofed when flashing lineageOS. Ive come to and understanding that I have to flash OOS 1.5.1 (i think that was it) on both slots, before then flashing the custom rom onto the device, and reflashing twrp after that. Which i did not do. I also were running pie at that time, so theres another mistake I made to begin with. Neither was I really aware of the concept of a/b partition system at hand..
Can i switch slots in fastboot, and then boot inton twrp, and reflash back to OOS 1.5.1, on both slots, and then reflash LOS 15.1? And ofcource reflash twrp and root afterwards, which totally slipped my mind..