I have a Galaxy S5 900A running on Phoenix 11 rom, on OF3 build and I ended up soft-bricking my phone after flashing Viper4Android 2.6.0.6, most likely of other audio mods I had installed. It had a kernel panic and now it boot-loops. All I have is a system back up that I made with Safestrap, but anything that involves USB is useless for me, since I have a broken charge port. I tried applying the G900A-OF3toOI5-ota-2400258.zip via external SD but got a verification error. Now I'm completely stuck. If worst comes to worst I'll have the charge port replaced. I just want to know if there's any way I can debrick without using ODIN or anything that requires a USB connection.
Related
Hello I recently got my refurbished Captivate from AT&T and it came running 2.1 Android. First thing I did with it was go and root it by downloading the update.zip to it, and that went all fine and well.
Next thing I did was get ROM Manager and installed Clockwork Recovery Mod, then went ahead and made a backup of my ROM. So from here I was getting ready to get myself ready for Cyanogen Mod 7, and grabbed the Clockwork Mod version with speedmod and installed that through the Clockwork Recovery.
After I did this the boot screen changed on my phone and would lock up at the Galaxy S SGH-1897 Samsung screen, which had replaced the 3g one by AT&T. The phone will just hang at this bootscreen for infinite amount of time, any suggestions on how to help?
I'd like to point out that I currently have no USB cable for this phone, I did not receive a micro USB with it as it is a refurbished product and do not happen to have any laying around. I do however have a micro SD card, in which Clockwork doesn't seem to support this.
I come to you asking for help to resolve said issue, I can no longer use my phone as a result. I've tried restoring my backup but the same replaced boot logo appears and refuses to actually start up the phone.
The 3 zips that I can access on the internal SD are
-the root.zip
-clockworkmod
-clockworkmod with SpeedMod
Any ideas?
First of all, you will definitely need a micro USB cable. You need to flash back to stock at the moment. Don't worry though, if it's still showing the boot screen your phone "should" be fine.
Second of all, for CM7 you need to follow the EXACT instructions to install CM7 (you can risk bricking your phone with CM7, unlike any other usual ROMs). Do you know, and understand all of the steps involved?
Sorry, but what were you doing? You need odin to install cm7 & without a cord you were never going to succeed.
As mentioned above you need a cord, and need to reread the instructions
CM7
Hiya!
Been on the forums for years modding my Nexus One and would like to thank everyone for their humongous contribution! 3 years of constant upgrading and improving of what turned out to be the best phone ever!
Now, I've come to an end where my self-confidence took over caution and preparation and i think i've made a boo-boo.
Long story short, i have a unlocked Nexus One that has been running a CM10 ROM with Blackrose for a good 6 months. Most of the functions were working fine, except for a few glitches, but last night i decided to go back to the roots, and install a stock Gingerbread ROM. I found a unrooted GB ROM, and went straight on to renaming it to PASSIMG, throwing it on card and rebooting. Now that's where the funny things started:
First, all goes well, click Volume Up, get it started, and than a screen with all OKs except for [7] BOOTLOADER - Fail-PU and a message saying 'Only Blackrose can be flashed'
Next, I get 7 OKs, except for BOOTLOADER, and the following: Partition update fail! Update fail! Do you want to reboot? Y/N
Figuring i forgot to uninstall Blackrose and need to do so, i let it restart, it comes up with a clean un-rooted GB ROM, and here's where my troubles start.
1. USB Connection: Plug it in, laptop doesn't recognize it at all. Classifies it as 'Unknown Device' and that's it. Tried fresh drivers, Universal Naked Drivers, SDK drivers, ASUS tablet drivers, nothing. Tried 3 cables, the HTC one, a Blackberry one and a Samsung one. Nothing. Uninstalled all USB hubs/devices, restarted the laptop multiple times. Debugging ON/OFF, no difference. I'm at a loss here, no clue what else to try!
2. Fine, i thought, let's flash a rooted rom! PASSIMG on the card, phone finds it, gets to the line 'Parsing... Passimg.zip' and goes back to the neutral screen. Tried it multiple times, different ROMs, nothing.
3. At this point, figured maybe an earlier ROM will cause an OTA update and fix things up. FROYO PASSIMG on the card, flashed 'succesfully', just like in #1, reboot to clean un-rooted FROYO. Checked USB connection, same again. OTA Update - constantly failed.
Been reading through Wikis and Q&A's here all day today, everything seems to be so easy to fix as long as you get a live ADB connection, and i know i could fix it, but i just can't get the laptop to recognize the bloody phone! Do not have access to another computer just now, so can't check whether it's just my Vaio.
So now, the questions:
1. Any other ideas on the USB issue? The phone does not display the usual 'choose your option/mass storage...' when connected, and nowhere in the menu is there an option for that.
2. When booting into recovery, i get the green droid with the white triangle and the !, and then get into the 3e recovery that has an 'update.zip' option. can i install a custom recovery without the phone being rooted? just of the sdcard? is there an update.zip that can re-stock my HBOOT?
any other ideas will be greatly appreciated, as of right now i am stuck with a FROYO handset that is perfectly capable of running JB, and it's really frustrating!
thanks in advance for all your help, cheers!
Hello,
I was on stock/rooted OC3, OTA'd to OE2, then rooted.
Here's a breakdown of what I did so far:
Original problem - Tried build.prop memory tweak which caused boot loop that I was unable to recovery from.
I did OC3 Odin, no service, would not activate, constant rebooting after about 30 seconds of use or plugging in USB to PC, with or w/o USB debugging.
I did the full OE3 Odin, from Sammobile, same results as OC3 Odin. Says "unknown" for Baseband in both cases and continuously reboots.
Then I flashed "Trailblazer101_925V_OE2_FLASH_ME.tar" but it still didn't work.
I've tried "Factory Reset" through Android and through the stock recovery, with the same results. At one point it rebooted and gave a message "due to failed factory reset....."
I don't know what else to try. Can anyone shed any light on this issue?
*edit* Today, of course after posting this threat I flashed "Trailblazer101_925V_OE2_FLASH_ME.tar" again and for some reason it stuck and it now seems to work.
Mods can delete this post, if need be. Thank you.
Hi Guys,
Decided to finally update my Samsung Note 1 N7000 as the 4.0.3 stock ROM was struggling with Google Maps and I use this as an in- car GPS. I read about a thousand different how to guides on the net and tried as best I could to back everything up and proceed carefully but I think I have stuffed the phone regardless.
I tried installing a custom recovery (tried both CM and CWM custom recoveries) before installing the latest CM11 ROM. I tried Heimdall and I installed SuperSU and Busybox. Everything I tried seems to either fail or crash half way through and so many of the guides were vague on what to do or their instructions didn't quite match what I saw on the screen. In the end I tried resetting the phone and wiping the cache and now I am stuck. Yes, I probably did too many things but all the guides were contradictory and it is darned confusing for a beginner!
TLDR:
Phone is now in bootloop mode (seems to still be Samsung factory recovery installed) and can't get it out using any of the usual methods
Can put phone into download mode and connect to Odin (phone connection inside Odin is recognised) but Odin eventually gives error message when trying to upload a clean stock Samsung N7000 ROM image of "serial (COM) failure". Have tried connecting to another phone (Note 3) and hardware appears OK but swapped USB ports and cables to make sure.
Is the phone stuffed or am I missing something here?
Cheers
...and the answer is NO! It wasn't bricked...
Tried again today, installed Philz recovery (PhilZ-cwm6-XXLT4-OXA-4.93.6-signed.zip) by copying the .zip file directly onto the SD Card via a USB adapter and executing that .zip through the stock recovery mode.
Rebooted and at last had something different as PhilZ recovery mode now working. Couldn't install anything directly off the SD card and the bootloop was still happening though.
...but...
Now Odin worked. Loaded stock ROM (N7000XXLT6_N7000XSALS8_XSA - 4.1.2) via Odin 3.10.6 (opened ROM in the AP field) and this time it loaded and flashed perfectly. I now have a fully functioning 4.1.2 phone again.
Phew.
Ive been lurking on this forum for a while but ive finally hit a wall I cant find an answer to
I successfully rooted my tablet using magisk and TWRP about 4 months ago, everything was going great. about 2 months ago my tablet booted up into TWRP and would not get out, no matter what I tried. eventually I fixed it by wiping everything and reflashing stock ROM from ODIN and going through the root process again, not a big deal. cut to 2 days ago, my tablet restarts and boots into TWRP again and wont boot into system, basically seemed like the same as before, until I plugged it into my computer
For some reason, my tablet no longer connects to ODIN or my laptop at all. Ive used the same cable and different device and same usb port and it worked just fine, ODIN picked up the connection and everything. Ive updated and unistalled and reinstalled drivers for all the USB ports and I dont think that is the issue. I even deleted and reinstalled ODIN but still nothing.
I thought maybe there was some setting on the tablet that might be preventing a connection to ODIN, so I wiped the rooted ROM off the tablet (im new to this, dont know if this was a bad idea) and tried again but got nothing. now with a soft bricked tablet I got a micro SD card, put a TWRP flashable version of the ROM onto it and plugged that into the tablet and flashed this new ROM onto the tablet, and that worked from what I can tell (system folder went from like 8mb to 17000 or something) but I still cannot get the tablet to boot into system.
I can access download mode (there appears to be two versions, one where it just says downloading and another where a bunch of text appears on the top left, some of it mentioning ODIN) and all the functions of TWRP, but ODIN does not connect and I cant get it to boot into the system.
TWRP version 3.1.0.1_ashyx
link to the post where I got the stock lite version of the ROM currently flashed to my tablet:
https://forum.xda-developers.com/tab-s2/development/rom-nougat-stock-lite-v1-t3746583
any help would be greatly appreciated, sorry for the wall of text.
Wish I had something useful to add. I'm having the same issue. TWRP 3.4.0.0 and LineageOS. I've had this issue forever. I flash a clean ROM, it works for a week or two, then I come back to it and all I get is recovery.
I can access Odin however.
Usually it takes wiping and installing a ROM to get the device working again, in fact it issue takes several rounds of that. But of course, in all of that I've lost my setup and some files.
Is there an actual solution to this?
On my T810 I'm having TWRP 3.3.1-0 with this ROM https://forum.xda-developers.com/tab-s2/development/rom-aospextended-rom-v6-7-t3979381
plus Magisk and Pico Gapps.
Of course it's only Pie and not Q, but working well.
3.4.4-0 not tested yet.
Once had an issue with black screen, but at that time I was using case with a screen cover.
Since that I've switched to TPU case only covering the back.
No more issues after that, perhaps it was a problem with FlipFlap like on other devices.