To preface what happened, I will give a short story.
About 4 days ago, I tried to Frankenstein my V30S on March, Oreo, US998 build to the LS998 in order to improve the lacking functionality/compatibility of the modem on custom ROMs to make my Sprint connection work. This attempt would result in my phone not working properly once I loaded into the stock rom, I immediately went back into TWRP to wipe the partitions and restore my backup. The restore failed and I tried to format the partitions afterwards. After this seemingly took too long, I rebooted the phone via hard reset. This is where TWRP would begin to stay stuck on the splash screen similar to a bootloop caused by a bad Magisk module. This brick became more complicated as I couldn't even connect the phone via USB anymore - neither adb, drivers, or fastboot would work. This was seemingly hopeless as I tried to recover the phone looking at crossflashing back, however LGUP wouldn't work for me either.
How I fixed my bricked phone with a frozen recovery wasn't complicated. Days later, I would try to see if I do anything about it, only this time, when I connected via USB, fastboot came up underneath ADB in device manager. I'm guessing this is because the SD card was removed. Adb still was unusable for my V30S, so I had to use fastboot in cmd. To summarize:
1. I needed to go into download mode - fastboot reboot bootloader to be quicker(although the V30S went straight to this without an OS).
Get rid of the corrupted TWRP - fastboot erase recovery to wipe away TWRP clean
2. Just wiping away the recovery partition wasn't enough, in addition, I needed to wipe boot and system partitions as well.
fastboot erase system and then fastboot erase boot
3. I wanted to make sure these partitions were working to be used, so I would format them back via fastboot format boot, fastboot format system, then finally fastboot format recovery
4. Finally, the last step was redownloading the Joan TWRP, inserting it in the adb/fastboot folder
Enter fastboot flash recovery TWRP.img (whatever filename) and then fastboot boot TWRP.img (whatever filename). The recovery was properly working and my phone was unbricked and useful again.
If I can bring my phone back from the graveyard with little to no experience with this kind of a problem, you can too. Always keep a backup prepared to be restored.
Wow. I had a bit of a situation over the last few days, also the result of a bad module in Magisk. However I only kinda made things worse by panicking and long story short I lost TWRP. Then, i just upgraded to an SSD in my laptop so everything wasnt where i needed it lol. Came close to doing the "fastboot erase all" and just starting over - in hindsight probably wouldve been faster but you live and learn. I agree, backups ALWAYS but in my ordeal they werent of any help w/o TWRP. Id say that having all your go-to files in one easy to find spot is as important =)
Definitely - a corrupted exfat filesystem on microSD was cause of concern/issue for me several times already,
so it should be in a TOP 5 or TOP 10 list in a sticky post/thread
that mentions emergency/recovery steps to attempt to get the phone going again.
Glad it worked out in the end for you
Related
hi all,
i've managed to get my g-nex (vz lte) pretty badly bricked and am hoping that someone here will be able to help. here's what i did initially on the phone:
1. ran 4.0.2 update from carrier
2. installed adb sdk etc on win 7, verified connectivity and function
3. oem unlock
4. rooted phone
5. installed apps, etc.
6. used phone for a few days, rebooted at will, all working as expected, no issues
7. fully charged phone and in the settings kicked off the encryption process, entered PIN, everything looked good.
8. this morning i woke up to a failed encryption (unfortunately i didn't catch the error message) which needed to be rebooted to move on.
9. after choosing reboot, the screen went very strange - it had grainy horizontal lines that shifted in color somewhat and got dim
10. after waiting for a bit without anything happening, pulled the power and battery
11. the phone rebooted into fastboot, couldn't get into recovery to restore cwm backup, couldn't really do anything
phone shows the following:
fastboot mode - no boot or recovery img
product name - tuna
variant - toro
hw version - 9
bootloader version - primekkk15
baseband version - i515.ek02 cdma - i515.ek05
carrier info - none
serial number - XX_redacted_XX
signing - production
lock state - unlocked
here's what i've tried:
adb commands - doesn't show as there from adb devices
fastboot commands - shows up with fastboot devices, flash commands seem to start but never stop
ODIN mode - connects but writes fail to complete
different usb ports/cables, doesn't seem to make a difference
what i've found to somewhat work - but not really do much - is to oem lock and unlock the phone, once there i can fastboot flash boot boot.img, etc. but if i do a recovery and try and boot into it, it just hangs at the google screen (with the lock unlocked).
i would like maybe reformat the phone completely and reinstall, i've tried the fastboot -w and erase boot / recovery thinking that i could write a clean image to them once they had been cleared, no dice.
if anyone has some suggestions, i'd really appreciate it.
take care,
philo
Have you tried a clean install of the factory image found here? http://code.google.com/android/nexus/images.html#mysidicl53f
i have tried going back to factory, unfortunately that set of images didn't work either. i was able (after an oem lock/unlock) to flash the img files, but it errored on the fastboot reboot-bootloader command with the oddly lined screen. i've attached a picture of the screen for reference.
philo_enyce said:
i have tried going back to factory, unfortunately that set of images didn't work either. i was able (after an oem lock/unlock) to flash the img files, but it errored on the fastboot reboot-bootloader command with the oddly lined screen. i've attached a picture of the screen for reference.
Click to expand...
Click to collapse
I hope you flashed the LTE version and not the GSM
You need this one https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz and you must first flash bootloader then radio and then the update img
i have been using the lte, same as your link. i can get the bootloader on, but a reboot-bootloader gives that weird screen, if i try and flash the radio without rebooting i get:
unknown partition 'radio'
philo_enyce said:
i have been using the lte, same as your link. i can get the bootloader on, but a reboot-bootloader gives that weird screen, if i try and flash the radio without rebooting i get:
unknown partition 'radio'
Click to expand...
Click to collapse
Check here http://forum.xda-developers.com/showthread.php?t=1392336
Its the cwm for cdma edition.Check if you can flash it and in this way have access to cwm recovery
i've tried that as well, same lines even if i use the menu to go to recovery after flashing rather than reboot to bootloader first.
So long as it's back to stock, and you've locked the bootloader, it's off for a replacement you go if it was me
EddyOS said:
So long as it's back to stock, and you've locked the bootloader, it's off for a replacement you go if it was me
Click to expand...
Click to collapse
+1 to this
interestingly, i can't get the fastboot oem lock to take either. it reverts back to unlocked after the reboot fails and i have to pop the battery.
does anyone know how to straight up repartition/reformat the flash? i'm assuming that the failed encryption of the flash has put it into an unusable state and would be happy enough just wiping the damn thing clean...
It looks the encryption screwed up because of the different recovery partition which might of also messed up the partition table.
Best bet is to plead ignorance and get a replacement phone.
problem "solved"
i called samsung and pleaded for the pit + factory image with no luck, so i went over to my local vzw and had them replace the phone for me.
i'm not going to try and encrypt this one, hopefully this was just a fluke and won't affect anyone else...
nice work... let them try to fix that shiz!
Darn, I was hoping for a solution...
I am having a similar issue with a Nexus 5. Phone was working fine, started the encryption process and went to bed and woke up with a bricked phone. I can get into the Bootloader and had figured no problem, I'll just do a factory wipe. Whether trying to boot the phone or get it to do the factory restore it sits there and bootloops with the Google logo. Wish programmers would put in status messages the way we did in the 'old days.'
I was able to get a little further was able to reflash, format the partitions etc. but no luck. I am wondering if perhaps the user data may have an indicator or flag that states it is encrypted even though it isnt at this point encrypted. Figured the factory restore would have been more than enough. WUG makes a nice Root Toolkit that automates a lot of the process but even letting do what I already didnt help.
philo_enyce said:
i called samsung and pleaded for the pit + factory image with no luck, so i went over to my local vzw and had them replace the phone for me.
i'm not going to try and encrypt this one, hopefully this was just a fluke and won't affect anyone else...
Click to expand...
Click to collapse
philo_enyce said:
interestingly, i can't get the fastboot oem lock to take either. it reverts back to unlocked after the reboot fails and i have to pop the battery.
does anyone know how to straight up repartition/reformat the flash? i'm assuming that the failed encryption of the flash has put it into an unusable state and would be happy enough just wiping the damn thing clean...
Click to expand...
Click to collapse
Yep , if you can get into recovery , you can adb shell , then list the partitions with "cat proc/mounts" , from there you'll have a list of your partitions and you can use the ext4 tools to manually repartition . I believe the command is makefs_ext4 <whatever partition you wanna do > I'll try to find the exact command but you can do it .
Also if you simply type "fastboot " when at the bootloader it'll give you the help text and it should tell you how to wipe partitions from fastboot
Hack The Tuna
The same issue here ! memory locked
I ve got the same scenario on a phone i just got , brand new but with the same issue , this one boots up but its impossible to factory reset it , odin , cyanogenmod , fastboot adb flashes .... everything fails somehow .... once you reboot the phone everything comes back ! stock software with the applications and old data .... theres no way to erase it ... it seems the previous owner of the phone encrypted it and then used clockworkmod or something like that ..... the nand on the device is like hardlocked .... doesnt let you do anything !
Hi all,
I tried to install the Jellybean on my One X following instructions step by step from here - the 'guide to installing' link, under the mirrors
http://forum.xda-developers.com/showthread.php?t=1763240
However when booting up it stuck on the flashing crosses for about 20 minutes before I decided it was probably not working. I read the comments and realised the only part I didn't do was a wipe, so I wanted to try again, but before doing a wipe I wanted to make sure I could then re-send the relevant files to my phone via adb, because I assumed a wipe would wipe those files off. However when I do adb devices it doesn't bring up the phone. However if I go into recovery, (CWmod 5.8.4.0) then run adb devices it does bring up my phone on the list. Also when the phone is apparently trying to boot up and stuck on the splash screen loading and I run adb devices it also sees my phone there too. I can send files across. I tried with a recovery img, but the adb message said it was waiting for the device to respond, which it never did.
I had a CWmod backup made before starting, so I ran that, but all that did was change the splash screen it gets stuck on from the colourful crosses to the HTC One logo screen. But it still gets stuck.
Does anyone know what to do from here? I still have access to the bootloader. Do I do a factory reset from the bootloader? Do I do it from CWrecovery? I'm feeling a little bit worried now
Slaxington said:
Hi all,
I tried to install the Jellybean on my One X following instructions step by step from here - the 'guide to installing' link, under the mirrors
http://forum.xda-developers.com/showthread.php?t=1763240
However when booting up it stuck on the flashing crosses for about 20 minutes before I decided it was probably not working. I read the comments and realised the only part I didn't do was a wipe, so I wanted to try again, but before doing a wipe I wanted to make sure I could then re-send the relevant files to my phone via adb, because I assumed a wipe would wipe those files off. However when I do adb devices it doesn't bring up the phone. However if I go into recovery, (CWmod 5.8.4.0) then run adb devices it does bring up my phone on the list. Also when the phone is apparently trying to boot up and stuck on the splash screen loading and I run adb devices it also sees my phone there too. I can send files across. I tried with a recovery img, but the adb message said it was waiting for the device to respond, which it never did.
I had a CWmod backup made before starting, so I ran that, but all that did was change the splash screen it gets stuck on from the colourful crosses to the HTC One logo screen. But it still gets stuck.
Does anyone know what to do from here? I still have access to the bootloader. Do I do a factory reset from the bootloader? Do I do it from CWrecovery? I'm feeling a little bit worried now
Click to expand...
Click to collapse
First of all take a deep breath. Go get yourself a cup of coffee or whatever your favorite drink is. Preferably non-alcoholic.
In CWM, if you go to mounts & storage and mount your sdcard, you will be able to transfer files to your phone's sdcard. One reminder, reboot your phone to bootloader again after file transfer.
You have to install rom's kernel from your PC using fastboot command (even when restoring from your nandroid backup. Copy the boot.img file to your PC from CWM as I described above)
fastboot flash boot boot.img
fastboot erase cache
As for adb commands, CWM supports adb commands not fastboot commands. You have to use fastboot commands when in bootloader in fastboot usb mode such as
fastboot devices
fastboot reboot-bootloader
etc
eyosen said:
First of all take a deep breath. Go get yourself a cup of coffee or whatever your favorite drink is. Preferably non-alcoholic.
In CWM, if you go to mounts & storage and mount your sdcard, you will be able to transfer files to your phone's sdcard. One reminder, reboot your phone to bootloader again after file transfer.
You have to install rom's kernel from your PC using fastboot command (even when restoring from your nandroid backup. Copy the boot.img file to your PC from CWM as I described above)
fastboot flash boot boot.img
fastboot erase cache
As for adb commands, CWM supports adb commands not fastboot commands. You have to use fastboot commands when in bootloader in fastboot usb mode such as
fastboot devices
fastboot reboot-bootloader
etc
Click to expand...
Click to collapse
Hiya, thanks for that. Just a couple points for clarification. Do I do a wipe first? Or Format? Which wiping option should I go for? There's wipe data/factory reset, and wipe cache partition. Also there's the factor reset option on the first bootloaders screen. And if I do wipe it won't that remove the clockworkmod for recovery?
The rom's kernel... would that be, in this jellybeany case, the file tg_endeavoru-ota-33.zip, and the boot.img file?
I realise these are things I should have learned first, but I thought it seemed rather straight forward, now I'm trying to take no risks so just want to make 100% sure I understand everything involved.
Thanks for your help, knowing I'm not doomed has lifted most of the weight
Slaxington said:
Hiya, thanks for that. Just a couple points for clarification. Do I do a wipe first? Or Format? Which wiping option should I go for? There's wipe data/factory reset, and wipe cache partition. Also there's the factor reset option on the first bootloaders screen. And if I do wipe it won't that remove the clockworkmod for recovery?
The rom's kernel... would that be, in this jellybeany case, the file tg_endeavoru-ota-33.zip, and the boot.img file?
I realise these are things I should have learned first, but I thought it seemed rather straight forward, now I'm trying to take no risks so just want to make 100% sure I understand everything involved.
Thanks for your help, knowing I'm not doomed has lifted most of the weight
Click to expand...
Click to collapse
Since you will be coming back from jb, wiping would prevent any future problems. Even if you decide to stay with JB, do a wipe as below
In cwm,
Wipe cache
Under advanced, wipe Dalvik cache
Under mounts and storage, format system
Cwm will remain intact. Also, I think selecting factory reset from bootloader menu will take you to cwm anyways. It's been awhile.
Yes, it is the boot.img file inside the zip. But you must use the full rom and not the ota. Ota only includes updates to some of the already existing files. It's just an upgrade.
Sent from my HTC One X using xda premium
I've searched this and other forums, and tried virtually everything that has been suggested or that I can think of.
I have a Zenfone 2 Laser ZE551ML rooted. Phone has worked like a dream. Installed TWRP 3.0, made and saved several backups in several different places, internally and externally.
Two days ago, flashed a TWRP recovery (I was looking to get back some data I had deleted inadvertently), seemed to go well until it booted, and could not get past the screen that says "Fastboot Mode!!!". Connected to a PC and was able to execute fastboot commands; supposedly can flash various recoveries, and seemingly does so, with everything looking right on the PC, and the phone actually rebooting. But always stops at the same screen.
ADB, on the other hand, shows no devices listed. Every command results in "Error: Missing Device."
I have done everything I can think of...uninstalled and reinstalled the ADB drivers, used different ADB drivers, removed the external SD card, removed the battery (which is the ONLY way the phone will shut off...pressing the on/off button for 10 seconds just results in it booting up to the same screen. Have tried the fastboot wipe command, again it seems to do so, but always comes back to the same screen. Fastboot flashing a recovery.img appears to successfully write a recovery, then goes to same screen upon reboot.
Any ideas? I've only had this phone a couple of weeks, and really like it. But flashing what was apparently a bad TWRP backup seems to have destroyed it.
Thanks so much for any suggestions!
i have the same problem.. please help!
i have the exact same problem you had.. please tell me how you restored it
As i have a similar problem i cannot help you on the technical side.
But isn't the laser 551 KL instead of ML. Maybe you flashed the wrong files trying to restore the phone
BeachNYC said:
I've searched this and other forums, and tried virtually everything that has been suggested or that I can think of.
I have a Zenfone 2 Laser ZE551ML rooted. Phone has worked like a dream. Installed TWRP 3.0, made and saved several backups in several different places, internally and externally.
Two days ago, flashed a TWRP recovery (I was looking to get back some data I had deleted inadvertently), seemed to go well until it booted, and could not get past the screen that says "Fastboot Mode!!!". Connected to a PC and was able to execute fastboot commands; supposedly can flash various recoveries, and seemingly does so, with everything looking right on the PC, and the phone actually rebooting. But always stops at the same screen.
ADB, on the other hand, shows no devices listed. Every command results in "Error: Missing Device."
I have done everything I can think of...uninstalled and reinstalled the ADB drivers, used different ADB drivers, removed the external SD card, removed the battery (which is the ONLY way the phone will shut off...pressing the on/off button for 10 seconds just results in it booting up to the same screen. Have tried the fastboot wipe command, again it seems to do so, but always comes back to the same screen. Fastboot flashing a recovery.img appears to successfully write a recovery, then goes to same screen upon reboot.
Any ideas? I've only had this phone a couple of weeks, and really like it. But flashing what was apparently a bad TWRP backup seems to have destroyed it.
Thanks so much for any suggestions!
Click to expand...
Click to collapse
fastboot --cmdline "lge.kcal=0|0|0|x" boot twrp.img
where TWRP.img is the directory of twrp
then you should get back to TWRP
flash TWRP image again in TWRP itself because the method on line 1 only temporary flashes TWRP and will auto discard TWRP after a reboot
Resolution and happy ending detailed in answer below.
I've been running 7.1 since its release. I've had Elemental X as my kernel, with SuperSU as well.
Today, I tried using the adb sideload for the ota.zip to 7.1.1. My computer here at work was refusing to recognize my XL when in recovery via ADB - ADB works just fine when the phone is booted, and fastboot works as well. Tried reinstalling Google drivers, and a different ADB/fastboot setup, and this didn't fix the issue.
Okay, so then I decide I'll try flashing the relevant .img's from the 7.1.1 NMF26O factory image. I flashed bootloader, radio, system, system_other, modem, and boot. I then flashed EX's kernel (elex.Image) instead of using the .zip for TWRP. I then booted the SR3 boot-to-root.img since I do not want to install TWRP at this time.
I got the few typical reboots, and now my phone goes directly to recovery and states "no command." Then the phone reboots itself after about 30 seconds, and keeps on doing this.
I tried re-flashing just the factory image files that I previously mentioned, without flashing EX and without booting the SuperSU img. I am still getting the same problem. I do not want to try a flash-all.bat and erase all my userdata if I don't have to. But I also saw someone else post that they ran into this issue of hitting "no command" on boot, and couldn't even flash the full factory image because it tries to flash recovery.img which is not part of the factory image files - what in the actual ****, why would the .bat try to flash recovery if it isn't there?
Right now I am trying to re-flash 7.1's files to see if I can just get back onto 7.1 with my userdata intact... but if anyone can provide insight on how I ****ed this up (because in my opinion, I did everything right), I'd appreciate it.
Edit: Tried flashing 7.1's files, and same issue... ridiculous. Trying the flash-all.bat and a factory reset now for 7.1.1.
Edit 2: Tried the flash-all.bat, and it successfully flashes bootloader and radio. It tries sending the .zip with the rest of the .img's, and fails because of insufficient space. I formatted userdata and did a factory reset in recovery as well, and am still having this issue... going to try the Unified Toolkit next to see if it can save me. This is bull**** though. Never have I had a Google device go this ballistic and unable to be EASILY recovered with the factory image!
Same thing happened to me. I don't know how I fixed mine, if that makes sense, but do you know what boot slot your on? A or B? Also what command are you using to flash all the images.
Are you doing
Code:
fastboot flash boot boot.img
or (x being the boot slot you are currently in)
Code:
fastboot flash boot_x boot.img
I chose this IMG as example. Nothing particular
I tried both. First was fastboot flash boot.img. Once I started having the recovery issue, I tried fastboot flash boot_a and boot_b with the factory images. I also just tried the flash-all.bat, and after it flashes the bootloader and radio, it says there is not enough space to send over the ~2 GB zip file with the other .img's to be flashed.
Using the Unified Toolkit with the factory image from Google worked. It does not use the flash-all.bat, and flashes each piece of the factory image with its own commands so there was no error relating to lack of storage space. Watching the flash commands go by, it appears my error may have been using "fastboot flash system system.img" because the Toolkit used "fastboot flash system_a system.img". I was using system_b for the system_other.img, but not system_a for system.img. NONE of the articles on the web relating to flashing the factory image for a Pixel/XL said anything about system_a, so they are likely using dated flash methods.
My phone is now alive.
This was also the LEAST PAINFUL factory reset I've ever done. Using the restore from cloud option during setup, and selecting my Pixel XL (last used today), it immediately restored my home screen layout (apps grayed out until downloaded), my texts are all back, and most app data is restored as well IF you allowed them to backup to Drive during your initial setup. I basically lost nothing but my time in doing all of this.
Thanks for sharing this! I will now use this tool from now on. Glad you were able to solve your problem
I have a Redmi note 5 pro, I was using a custom rom, but was experiencing some bugs so I decided to put another ROM in it, I already did this lots and lots of times and I always followed this procedure:
Reboot into recovery(TWRP), Transfer the ROM, GAPPS and MAGISK to the phone > wipe Cache, Dalvik Cache and System. > Install ROM, GAPPS > WIPE DATA > FLASH MAGISK > WIPE INTERNAL STORAGE > DONE.
Never had a problem, but this time idiot me was doing this at 5am, dying to go to sleep, and I started by wiping everything, without moving the files to the phone beforehand.
Well, apparently once you wipe the system the phone internal storage doesn't show up in the computer anymore, I didn't know that. I always thought that since TWRP was MTP compatible, it would always be a thing, welp.
I then thought of 2 solutions to this: I remember ADB sideload was a thing, and I also could buy a memory card, put the files there, and just load into the phone, bam.
Since it was 5am the memory card would have to wait, and I couldn't get ADB sideload to work, it would't recognize my device for some reason.
I then remembered fastboot existed, and weirdly enough my phone was recognized as a fastboot device on my pc. So I went, downloaded the correct fastboot rom from xiaomi website and tried flashing it using a official tool that they provide, and then tried again using a third party tool that also does something similar.
I was getting a few errors, and then in one of my restarts the phone just stopped showing stuff. It would still turn on, but it's just a black screen, no icons, no recovery, no fastboot, nothing. The battery icon when I put the charge in is the only thing that still shows up.
I already know the answer to this, but hope is the last thing to die, so, is it irreparably ****ed up ? Is there anything I can do? Is it even worth it sending it to repair services? (It wouldn't be Xiaomi, they don't have stores here in my country)
EDL
i´m pretty sure that at least EDL Method works, many tutorials on youtube. Search for "redmi note 5 edl method"
Try to find something about edl mode as mentioned above. It might be your last chance to revive this phone, but you need to take the back cover to be able to find the edl pins and short them. There are many guides on the internet as well as on youtube. But before you try to do that, first try to enter the fastboot mode somehow, you may succeed, so tinker with it for couple of minutes.
As you are able to boot it into Fastboot mode,
1. boot into fastboot mode
2. boot into recovery using "fastboot boot twrp-name.img"
You should be able to see your device in PC after booting in TWRP
3. format data.
(If you are not able to see Internal storage of your RN5 in PC then,
1.boot in fastboot from twrp.
2. boot in twrp again using command above)
4. then copy your files and flash them.
5. wipe cache/dalvik
6. reboot
rasik107 said:
As you are able to boot it into Fastboot mode,
1. boot into fastboot mode
2. boot into recovery using "fastboot boot twrp-name.img"
You should be able to see your device in PC after booting in TWRP
3. format data.
(If you are not able to see Internal storage of your RN5 in PC then,
1.boot in fastboot from twrp.
2. boot in twrp again using command above)
4. then copy your files and flash them.
5. wipe cache/dalvik
6. reboot
Click to expand...
Click to collapse
As I said in the post
and then in one of my restarts the phone just stopped showing stuff. It would still turn on, but it's just a black screen, no icons, no recovery, no fastboot, nothing.
Click to expand...
Click to collapse
I can't boot into fastboot. Right now my only chance seem to be EDL mode, I'll give it a try as soon as I can.
Vitorvlv said:
As I said in the post
I can't boot into fastboot. Right now my only chance seem to be EDL mode, I'll give it a try as soon as I can.
Click to expand...
Click to collapse
And then dont forget to post what happened..
Whether you fixed your phone or not..
Is she dead or not... :angel:
I cant handle the suspense, you are holding...
Sreehul R said:
And then dont forget to post what happened..
Whether you fixed your phone or not..
Is she dead or not... :angel:
I cant handle the suspense, you are holding...
Click to expand...
Click to collapse
she or he posted as soon as she / he can do.