Hi
OP5 started acting weird, then locked up on me.
I got into the bootloader reflashed factory recovery, then I opened factory recovery and tried uploading the factory image into the phone. Can't perform that function
So I adb sideloaded the factory image successfully, but the startup has been going on for half an hour or so.
Is there anything else that I can do?
Regards
Hi all,
Well it took several hours, but it finally reformatted the userdata partition properly finally,
All is good now.
Regards
Related
I have this 8GB Nexus 4 I purchased when it was first released as a gift for someone. Anyway, when 4.3 was released the person I gifted the phone took the update and after that the screen was stuck on the X screen for about 12 hour. He finally unplugged the power and waited for the battery to drain.
The phone isn't rooted, doesn't have a custom recovery on it. It's basically a stock device.
I have the phone now and this is what I've done so far. As soon as I received the phone, I went into the recovery and cleared both cache and reset the device to default. It still didn't boot (stuck on X screen). Then I used fastboot to clear everything and reinstall the factory image for 4.3. it still wouldn't boot. I then used fastboot to flash the radio from 4.2's factory image and it booted to the main screen.
I don't know why the phone won't boot with the radio bundled with the factory image for 4.3. I waited until 4.4 became available (today) thinking that would solve my problem. No, it didn't. The phone is stuck on the new multi color (4 dots) boot screen after flashing 4.4.
Can anyone help me figure out how to get the proper radio on this phone? I don't know what else to try.
benso37 said:
I have this 8GB Nexus 4 I purchased when it was first released as a gift for someone. Anyway, when 4.3 was released the person I gifted the phone took the update and after that the screen was stuck on the X screen for about 12 hour. He finally unplugged the power and waited for the battery to drain.
The phone isn't rooted, doesn't have a custom recovery on it. It's basically a stock device.
I have the phone now and this is what I've done so far. As soon as I received the phone, I went into the recovery and cleared both cache and reset the device to default. It still didn't boot (stuck on X screen). Then I used fastboot to clear everything and reinstall the factory image for 4.3. it still wouldn't boot. I then used fastboot to flash the radio from 4.2's factory image and it booted to the main screen.
I don't know why the phone won't boot with the radio bundled with the factory image for 4.3. I waited until 4.4 became available (today) thinking that would solve my problem. No, it didn't. The phone is stuck on the new multi color (4 dots) boot screen after flashing 4.4.
Can anyone help me figure out how to get the proper radio on this phone? I don't know what else to try.
Click to expand...
Click to collapse
after flashing the factory img, and it doesnt boot, go back into the stock recovery and wipe everything. then try to boot again.
simms22 said:
after flashing the factory img, and it doesnt boot, go back into the stock recovery and wipe everything. then try to boot again.
Click to expand...
Click to collapse
Thanks for the quick response. I've done that twice now. No joy.
benso37 said:
Thanks for the quick response. I've done that twice now. No joy.
Click to expand...
Click to collapse
Same here, went in stock recovery and formatted all.. funny thing is that in openrecovery or clockwork the data partition cannot be mounted so also not formatted ; in stock no message about mounting issues so seems to be working, but I am not sure,,
edit :
cannot mount cache, sdcard either
is it unlocked?
opssemnik said:
is it unlocked?
Click to expand...
Click to collapse
Yes
PoloB12 said:
Yes
Click to expand...
Click to collapse
manually wipe data and cache using fastboot
make your phone boot into bootloader mode and connect to pc
on pc open fastboot and type fastboot erase cache and fastboot erase userdata, if there are erros probably your phone is eMMC failed, if no erros let it boot for like 20 mins
It works now, I relocked the bootloader en reboot. Then unlocked and into revovery wiped everything. Flashed all and worked.
So I bricked my N4 somehow (I don't know if it is soft or hardbricked).
I was running latest N5X AOSP 6.0 Lollipop and everything was fine, when i decided to try the AICP 0.1 experimental LP. I made a clean install but it the first boot ended in a black screen. Then i rebooted into recovery and made a factory reset and since then Im stuck in an infinite bootloop.
So here is what i tried so far:
Flashed newest Factory Image via Fastboot and ADB. Result: Bootloop
(Flashed with flash-all.bat and every img by myself, i even tried without flashing cache.img and userdata.img, but everytime i ended in a bootloop that goes longer than 30 minutes)
I tried several Toolkits but nothing helps everytime I reboot its a bootloop.
But somehow when i flash the N5X AOSP 6.0 and let it boot for some minutes and then just shut it down and boot again i can see its optimizing my apps but when it comes to start them i just stays there...
I also tried to format my /cache with TWRP into FAT and back to Ext4 (that was one solution i found) but that doesnt seem to work too..
I am very frustrated and hope someone can help me
Hi
Yesterday, my phone suddenly crashed and turned off and restarted. My phone has been rooted and unlocked for about 6 months now with no issues and I did not do anything to it last night to change that.
Now, I am stuck between the "Google" logo boot and the "Your device cannot be checked for corruption." I can get into the bootloader and the device is shown on fastboot, but not adb. I have tried flashing the Stock img and it seems to work, but then it doesn't change anything.
If anyone could offer advice/insight that would be much appreciated! Thank you
Have you tried fastboot format data, fastboot format userdata and lastly fastboot format cache?
I had this phone bricked for almost 1-2 months, now I wanted to see if I can get it back to work, I'll list here the extensive list of thing that I tryed before finding this weird problem:
All I remember from 2 months ago is that I had the pre-rooted rom 21.40.1220.1998, had a no signal problem, tried rebooting the phone and it started bootlooping, bootloader was already unlocked when this happened.
I tryed varius flashes from stock recovery, TWRP, even tried installing lineage, but I don't recall the exact steps that I tried at that time. I'm sure that were a lot.
Now, today, booted phone, it started on fastboot mode, tried booting recovery, no way. Flashed stock recovery package found on internet, got stock recovery back.
Then I started doing as follows:
Flashing the oldest stock rom package I had, installation stuck on opening update package for 1 hour, removed battery from the device
tried downloading the package same as the one maked on the first line of the recovery screen, flashed without errors, rebooted: bootloop.
tried flashing a more recent recovery and boot img from fast boot, making sure to do a fastboot erase of both partitions before. recovery doesn't start.
Tried installing TWRP recovery, and rebooting, no way, phone boots on fastboot.
done a "fastboot boot twrprecovery.img" to wipe from there the partitions. Got a mount error for each partition.
I went to the partition repair screen for system, and then I noticed the partition size was 0MB. WTF!
Checked all other partitions, all 0MB size, 0MB used, 0MB free. except for the cahce one, it is 27MB and empty.
Now, I'm pretty sure I need to repartion theese partions, but I don't know the original size. Someone here does have the partion size for system and data (and I gues also recovery?)?
There is any other way to fix this problem and get the phone back to work? I literally spend all the day trying every solution I found on internet.
motherboard is faulty
R3DC0D3 said:
I had this phone bricked for almost 1-2 months, now I wanted to see if I can get it back to work, I'll list here the extensive list of thing that I tryed before finding this weird problem:
All I remember from 2 months ago is that I had the pre-rooted rom 21.40.1220.1998, had a no signal problem, tried rebooting the phone and it started bootlooping, bootloader was already unlocked when this happened.
I tryed varius flashes from stock recovery, TWRP, even tried installing lineage, but I don't recall the exact steps that I tried at that time. I'm sure that were a lot.
Now, today, booted phone, it started on fastboot mode, tried booting recovery, no way. Flashed stock recovery package found on internet, got stock recovery back.
Then I started doing as follows:
Flashing the oldest stock rom package I had, installation stuck on opening update package for 1 hour, removed battery from the device
tried downloading the package same as the one maked on the first line of the recovery screen, flashed without errors, rebooted: bootloop.
tried flashing a more recent recovery and boot img from fast boot, making sure to do a fastboot erase of both partitions before. recovery doesn't start.
Tried installing TWRP recovery, and rebooting, no way, phone boots on fastboot.
done a "fastboot boot twrprecovery.img" to wipe from there the partitions. Got a mount error for each partition.
I went to the partition repair screen for system, and then I noticed the partition size was 0MB. WTF!
Checked all other partitions, all 0MB size, 0MB used, 0MB free. except for the cahce one, it is 27MB and empty.
Now, I'm pretty sure I need to repartion theese partions, but I don't know the original size. Someone here does have the partion size for system and data (and I gues also recovery?)?
There is any other way to fix this problem and get the phone back to work? I literally spend all the day trying every solution I found on internet.
Click to expand...
Click to collapse
If all partition showing 0 Mb in twrp and u cant change extention repair or format and reboot your phone phone motherboard is faulty
better buy new phone.
I have the MetroPCS xt1765 running lineageos 14.1. When unlocking and doing all that jazz, the guide said that you can't flash twrp, only boot it. But I got annoyed that /data wouldn't mount so I just tried to flash it anyway and it worked. On cmd it said that the file wasn't signed or corrupt, but it still wrote to the device. I thought nothing about it at first but when I tried to boot the device it automatically when into twrp. I tried to reboot to system again, and the same thing happened.
Eventually /data successfully mounted and I was able to format it and install linage. I hoped that would fix the problem but it's still there. I believe I would need the stock boot image and probably stock recovery as well. I hope someone out there has these files.
Also when booting with factory mode, my data isn't working at all. The apn setting are right and all, but it's not working.
ZacharyTheUmbreon said:
I have the MetroPCS xt1765 running lineageos 14.1. When unlocking and doing all that jazz, the guide said that you can't flash twrp, only boot it. But I got annoyed that /data wouldn't mount so I just tried to flash it anyway and it worked. On cmd it said that the file wasn't signed or corrupt, but it still wrote to the device. I thought nothing about it at first but when I tried to boot the device it automatically when into twrp. I tried to reboot to system again, and the same thing happened.
Eventually /data successfully mounted and I was able to format it and install linage. I hoped that would fix the problem but it's still there. I believe I would need the stock boot image and probably stock recovery as well. I hope someone out there has these files.
Also when booting with factory mode, my data isn't working at all. The apn setting are right and all, but it's not working.
Click to expand...
Click to collapse
When it was booting to twrp only, you just select reboot bootloader and in bootloader select start and you will get system. This twrp doesn't read and clear bootloader control block (BCB) properly which causes this. There is a fix. I'll find the link.
Do you mean fastboot/bootloader mode? If yes, try this