[SOLVED] Did I just brick my device??? - Xperia Z1 Compact Q&A, Help & Troubleshooting

Here's my situation:
I was attempting to sideload a custom rom (AICP) onto my Z1C.
I successfully wiped the device and sideloaded AICP and Open Gapps.
But then, like an idiot, I rebooted, with no OS installed.
Did I brick the device? Or is there some way I can still get it to install the zip file that's on there?
Right now I'm trying the ADB install command, but I keep getting "error: no devices found".
Is this the end of this device????

Wait... I reflashed the boot img and was able to get back to TWRP Recovery. Now I'm going to attempt sideload again but I WON'T REBOOT BEFORE I INSTALL

Ok, sorry for freaking out there. I'm back in TWRP and sideloadin successfully, except....
I can't find the sideloaded files now that I want to install them? Where do they go?
I don't have a MicroSD card at the moment.

Related

[Q] KFU Stuck trying to remove root checker.

I have been trying to reroot my Kindle Fire for some time now but recently when I try to run KFU it gets to the point where it installs TWRP but gets stuck in there trying to remove the root checker. The only way I can go back and actually use the kindle is by flashing the update.zip from the amazon website. Any help?
Were you actually successful in getting TWRP installed? Have you tried to access it?
soupmagnet said:
Were you actually successful in getting TWRP installed? Have you tried to access it?
Click to expand...
Click to collapse
It boots into TWRP while its rooting the Kindle. The problem is that it stays there and doesn't continue. TWRP is also missing some options and some text. I have to flash the update to gt out of TWRP
notdeadyet01 said:
It boots into TWRP while its rooting the Kindle. The problem is that it stays there and doesn't continue. TWRP is also missing some options and some text. I have to flash the update to gt out of TWRP
Click to expand...
Click to collapse
Download this and push it to your sdcard
http://forum.xda-developers.com/attachment.php?attachmentid=1286034&d=1346085105
It is a flashable version of TWRP that can be installed in recovery (this is to fix any potential bad installation of TWRP).
Reboot and access TWRP again.
Once in TWRP, enter the following code to remove the root check:
Code:
adb shell mv /system/bin/check_rooted /system/bin/check_rooted.bak
If you get an error message that says:
Code:
mv: can't rename '/system/bin/check_rooted': No such file or directory
You have nothing to worry about. It just means the "check_rooted" file does not exist.
While in TWRP, you can do whatever else you need to do to root your device or just flash a ROM (they're pre-rooted). If you do flash a ROM, be sure to wipe "system" and "factory reset" first. Otherwise you're looking at possibly needing a factory cable (or firekit) to fix the problem.

[Q] Bricked my Ouya

Hallo,
i bricked my Ouya. I have CWM installed. I started my Ouya and get a Update, then I rebooted in Recovery an I stock there. I took my Keyboard, powered OUYA of, restarted without Ethernet and rebootet to recovry.
Then i format the /system to get rid of mod-Collection. Then i want to install update.zip, but it wasen´t there. Now I have a Ouya only with CWM.
CWM did not find my USB-Stick. And when i connect my Laptop to the Ouya I can not find a USB-Memory. My Ouya-Driver did not recocnize the Ouya!
But the i a topic in CWM load from Sideloading! How can I put a *-ota.zip an the OUYA to flash system angain?
Thanks.
gueschmid
DONE!
I FOUND ADB SIDELOAD *-OTA.ZIP
gueschmid said:
Hallo,
i bricked my Ouya. I have CWM installed. I started my Ouya and get a Update, then I rebooted in Recovery an I stock there. I took my Keyboard, powered OUYA of, restarted without Ethernet and rebootet to recovry.
Then i format the /system to get rid of mod-Collection. Then i want to install update.zip, but it wasen´t there. Now I have a Ouya only with CWM.
CWM did not find my USB-Stick. And when i connect my Laptop to the Ouya I can not find a USB-Memory. My Ouya-Driver did not recocnize the Ouya!
But the i a topic in CWM load from Sideloading! How can I put a *-ota.zip an the OUYA to flash system angain?
Thanks.
gueschmid
DONE!
I FOUND ADB SIDELOAD *-OTA.ZIP
Click to expand...
Click to collapse
If anyone has this problem in the future, you could use sideload or you could just adb push ie.
adb push update.zip /sdcard/update.zip
prophetjinn said:
If anyone has this problem in the future, you could use sideload or you could just adb push ie.
adb push update.zip /sdcard/update.zip
Click to expand...
Click to collapse
I did it this way all the time. But now it doesn't seem to work anymore.
I flashed the latest update I downloaded from https://ouyafw.skumler.net/
and getting this error when applying the update.zip from SDK or sideloading it (both doesn't work)
Code:
assert failed: !less_than_int(1391471878, getprop("ro.build.date.utc"))
I tried removing this line from the updater-script. Doesn't work. The progress stops with "Installation aborted." without an error code.
seems with further firmwares, there is no way to restore anymore.
PS: I don't have CWM. only Stock recovery and a system that stucks in bootloop even after factory reset.
nex86 said:
I did it this way all the time. But now it doesn't seem to work anymore.
I flashed the latest update I downloaded from https://ouyafw.skumler.net/
and getting this error when applying the update.zip from SDK or sideloading it (both doesn't work)
Code:
assert failed: !less_than_int(1391471878, getprop("ro.build.date.utc"))
I tried removing this line from the updater-script. Doesn't work. The progress stops with "Installation aborted." without an error code.
seems with further firmwares, there is no way to restore anymore.
PS: I don't have CWM. only Stock recovery and a system that stucks in bootloop even after factory reset.
Click to expand...
Click to collapse
The firmware on the site you mentioned is not up to date!
Here is the official link for the latest firmware.
If you have adb access, you could try to fastboot CWM recovery.

[Q] Help - Stuck in No-Man's Land (TWRP 2.6.3.0 with no ROM to flash)

I recently picked up a new-to-me LS970 after an unfortunate encounter with gravity :/
I went to root/unlock the phone and all seemed to go well. I loaded TWRP 2.6.3.0 and proceeded to make a backup of my stock rom/settings/ESN. I then attempted to flash a new ROM and found that the MIUI port wasn't functional for me. I tried to flash CM12 as well but cannot get past the setup wizard.
Unfortunately, TWRP doesn't recognize my backup. If I go to the file manager, I can see the directory and files that compose my backup, but if I go to restore it, I get a blank menu with no restore options.
The ADB sideload option fails to connect (It says 'Starting ADB sideload feature...' forever until I cancel it) and I cannot get far enough into either ROM to enable me to push files over MTP. in CM12, I can get ADB to see my phone (appears when I use 'ADB devices') but if fails to push a file due to permission being denied.
What are my options here? How can I move forward with having a functional phone?
I was able to tinybin my way back to TWRP 2.6.0.0 and that has allowd me to ADB push files. Sideload still will not function. I tried flashing several ROMs but they always fail. I treid reformating my SD card, and that also fails (unable to read partition table). Any guess as to what is going on? MIUI successfully works now, so at least I'm through the worst of it.
LordKyleOfEarth said:
I recently picked up a new-to-me LS970 after an unfortunate encounter with gravity :/
I went to root/unlock the phone and all seemed to go well. I loaded TWRP 2.6.3.0 and proceeded to make a backup of my stock rom/settings/ESN. I then attempted to flash a new ROM and found that the MIUI port wasn't functional for me. I tried to flash CM12 as well but cannot get past the setup wizard.
Unfortunately, TWRP doesn't recognize my backup. If I go to the file manager, I can see the directory and files that compose my backup, but if I go to restore it, I get a blank menu with no restore options.
The ADB sideload option fails to connect (It says 'Starting ADB sideload feature...' forever until I cancel it) and I cannot get far enough into either ROM to enable me to push files over MTP. in CM12, I can get ADB to see my phone (appears when I use 'ADB devices') but if fails to push a file due to permission being denied.
What are my options here? How can I move forward with having a functional phone?
Click to expand...
Click to collapse
LordKyleOfEarth said:
I was able to tinybin my way back to TWRP 2.6.0.0 and that has allowd me to ADB push files. Sideload still will not function. I tried flashing several ROMs but they always fail. I treid reformating my SD card, and that also fails (unable to read partition table). Any guess as to what is going on? MIUI successfully works now, so at least I'm through the worst of it.
Click to expand...
Click to collapse
If it is your original TWRP backup (TWRP that Freegee installed) it might not restore, I had that problem a long time ago. Try installing an updated TWRP, that one is really old at this point.
If you have an updated TWRP you can mount MTP from recovery and transfer any files to your internal storage. I suggest starting out with the stock ZVC so you can have a fully working stock device and make sure everything works. From there you can copy zips to your device and flash away.
If you have issues copying a recovery to your device you can always use adb to flash. I believe it is
"fastboot flash recovery (name of recovery.img)" without quotes or parenthesis.
EDIT: On the CM 12 setup thing, @Shelnutt2 just posted in the CM12 thread that the bug is fixed and will be pushed to tonight's nightly.
Here is a newer recovery built by an international dev but this is the one I used when I had the OG.
http://dl.kevinjoa.me/recovery-geehrc/twrp/

Oneplus 3 do not boot after installing OxygenOS 4.0.2

Hello everyone!
My oneplus3 is actually running no OS and I'm having a boot loop.
I will try to explain what happened to me with the most details I can.
Before I ****ed everything up, I think I was running OxygenOS 3.28, not really sure about it but im 100% sure it was below 4.0, and it was rooted with TWRP 3.0.2 installed.
1) Today I had a pop up saying OxygenOS 4.0.2 was available (the official one that pops on the screen on boot) "Yay so coooool Nougat!"
1.1) I downloaded it, 1.4Go, then I pressed install
1.2) TWRP showed up, I didn't know what to do and that's where I ****ed up, I set my phone "factory new" in TWRP.
1.3) Phone restarted fresh new, I thought I had 4.0.2 but naaaaah would've been too easy so the official pop up showed again, I was still 3.28 I think.
1.4) Downloaded it once more, TWRP opened again, this time i was looking for the update i just downloaded in the "install" section. I browsed for quite a while and couldn't find it.
1.5) Master ****-up here: I tried to restore a backup. Then the bootloop happened. The black screen with "Oneplus" written in white. I was able to go back in TWRP by pressing power + volume down
1.6) Tried every kind of restore unsuccessfully, and tried ADB but it wouldn't load. Also TWRP said that I was running no OS when I wanted to turn off my phone for example.
2) I downloaded 4.0.2 from one plus website on my mac, and i flashed the official recovery instead of TWRP.
2.1) Transferred the update from my mac to my PC (seems important to me) and installed ADB & everything on both PC/O+3.
2.2) so adb worked in forceboot, i've been able to flash official recovery, tried once more to wipe & everything, but clearly I have no OS now, as TWRP said.
2.3) so i had the update in a folder (not a zip, probably due to the download being done from a mac), I made it a .ZIP with winrar, but "adb sideload update.zip" crashed at 0% everytime
2.4) looked at the archive then i noticed it was first a folder "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883" then inside it i had the content like "boot.img" & everything. So i zipped it again but without that first folder because I thought it was the problem, but it kept on crashing 0%.
2.5) restarted my PC, looked on several forums, but i couldn't find any fix. Now adb can't even open update.zip anymore, it fails even before 0%.. I tried naming it .zip.zip, keeping the name "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip", using a third party app to allow more RAM to the cmd app...
I've been trying hard for 4 hours but I still have a O+3 without any OS... My last idea is downloading "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip" from my PC so it downloads it directly .zip unlike on my mac...
I hope I said everything, sorry for the long post but i'm desperate.. thanks for your attention,
Valentin
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
dbabaev21 said:
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
Click to expand...
Click to collapse
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Try to install the new official TWRP version i think it is 3.0.3-0 through fastboot. Boot up TWRP, wipe every partiton and copy the update.zip onto the phone. You can copy it by connecting it normaly via USB(like you would do in OOS) and install the zip file afterwards.
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
install stock recovery and then try installing official OS. Or install modded twrp 3.0.2-1.28 and then try installing Freedom OS 2.3 via sideload or through internal storage.
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
Stop fiddling with the ROM. Download the ROM afresh directly to your Windows PC/laptop. Check the md5. Then start experimenting with the other suggestions but don't again meddle with the ROM!
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
I read your post again and here are a few things:
* Don't update Stock OOS via "System updates" in Settings if you are rooted and have TWRP
* Back up your data before updating, wiping or doing something with your phone.
* For the ADB error, see the FAQ #17 in the guide I provided.
Now, try this:
Flash TWRP via fastboot > boot to TWRP > connect your phone to your PC and copy the full Stock OOS v4.0.2 OTA to your phone > reboot to fastboot and flash Stock Recovery.
It didn't touch the internal storage. So, try to install from internal storage when you are in Stock Recovery.
Let me know if it worked.

OP3 bricked - Please help!

In an attempt to unroot my OP3 I managed to (almost?) brick it. Fastboot still works so I could flash back TWRP which I already had replaced by the stock recovery. Also I have a backup available on the phone which I hoped to be able to restore. And here is where my problem comes in: I cannot choose any partition to restore because there are none and hence the restore fails with "No partitions selected for restore.".
What can I do now? Originally I was trying to sideload the current Oxygen OS using the stock recovery but that didn't work. Any ideas?
simu_lacrum said:
In an attempt to unroot my OP3 I managed to (almost?) brick it. Fastboot still works so I could flash back TWRP which I already had replaced by the stock recovery. Also I have a backup available on the phone which I hoped to be able to restore. And here is where my problem comes in: I cannot choose any partition to restore because there are none and hence the restore fails with "No partitions selected for restore.".
What can I do now? Originally I was trying to sideload the current Oxygen OS using the stock recovery but that didn't work. Any ideas?
Click to expand...
Click to collapse
Your not bricked at all. Just stuck with a phone without OS I think? Why does ADB sideload not work? Do you get the "cannot read" error? Use adb push file directory then manually flash it with twrp. Make sure you are in the latest one from Bluspark!
Yes, I'm stuck with a phone without OS. I did get the "cannot read" error but I don't know why because all the necessary files were in the very same directory from where I issued the adb commands. Where do i find or define an adb push file directory? Currently I habe TWRP 3.0.3-0. installed. Will that be sufficient?
Please keep in mind that I've also lost my partition information. adb sideload alfeady didn't work before that because of the "cannot read" error. Still I don't know what's the reason for that error.
Here you will find everything you need to recover your phone:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700

Categories

Resources