Hi guys, I'm normally the one who reads these forums, not starts them, so i'm in pretty desperate help.
I have a Samsung Nexus S phone that somehow got stuck in a bootloop after my dad attempted to fix the problem by wiping everything he could from the recovery; cache, system, data, factory reset. I am able to access fastboot (obviously). In fastboot mode, the only 4 options it gives are POWER OFF, REBOOT, RECOVERY, REBOOT BOOTLOADER. None of these options leads to any progress. Only one that makes sense is to click and run recovery. When recovery loads, i can:
Reboot system now
apply update from ADB
apply update from sd card
wipe/factory reset
wipe cache partition
I recently rooted and custom ROMed my Galaxy J7 Pro, and as you experts may know it wasn't too easy finding the correct files or even the support for it.
I know you have to have developer options enabled and OEM and USB Debugging as the prereqs for rooting, but this phone has nothing. I'm not sure what to do. The bootloader is locked and I obviously can't enable developer options. I guess where I'm stuck is how i can flash a custom recovery like twerp for a phone that has a locked bootloader that can't be unlocked through developer options.
As I'm writing this, i was thinking, can i prepare an SD card with the lollipop OS for the nexus to install and run on. Ive already wiped the internals and cache of the phone, meaning there is nothing on it?
Help would be appreciated, bringing back a phone that has the potential (working hardware) to run would be great.
Just do a manual restore using the google factory images (google them, first result usually and a VERY user friendly page, thanks google!).
Don't use the script, just reformat everything via fastboot, then manually flash the images to their respective partitions.
"cd [path to unzipped images]"
"fastboot format /[partition] ext4"
"fastboot flash /[partition] [path to image]"
and so on and so on. Then after, "fastboot reboot". I assume you've found a fix by now but maybe someone else will stumble on this. Keep in mind, I'm writing this from memory and with no drivers or way to test this on my mac, my Nexus S is coming in the mail soon so take what I say with a grain of salt and try to double check the commands. For the most part however, they should be correct. format, reflash, reboot. All you should have to do.
padhpataka said:
Hi guys, I'm normally the one who reads these forums, not starts them, so i'm in pretty desperate help.
I have a Samsung Nexus S phone that somehow got stuck in a bootloop after my dad attempted to fix the problem by wiping everything he could from the recovery; cache, system, data, factory reset. I am able to access fastboot (obviously). In fastboot mode, the only 4 options it gives are POWER OFF, REBOOT, RECOVERY, REBOOT BOOTLOADER. None of these options leads to any progress. Only one that makes sense is to click and run recovery. When recovery loads, i can:
Reboot system now
apply update from ADB
apply update from sd card
wipe/factory reset
wipe cache partition
I recently rooted and custom ROMed my Galaxy J7 Pro, and as you experts may know it wasn't too easy finding the correct files or even the support for it.
I know you have to have developer options enabled and OEM and USB Debugging as the prereqs for rooting, but this phone has nothing. I'm not sure what to do. The bootloader is locked and I obviously can't enable developer options. I guess where I'm stuck is how i can flash a custom recovery like twerp for a phone that has a locked bootloader that can't be unlocked through developer options.
As I'm writing this, i was thinking, can i prepare an SD card with the lollipop OS for the nexus to install and run on. Ive already wiped the internals and cache of the phone, meaning there is nothing on it?
Help would be appreciated, bringing back a phone that has the potential (working hardware) to run would be great.
Click to expand...
Click to collapse
I have the same problem.I know this was 4 years ago but as a noob I find that guides tend to assume greater levels of knowledge than I have. Trying to bypass FRP as I think this is what is causing the "system error" message when I try to access play store or Google plus. I haven't even been able to unlock bootloader or root phone . In fact I find "fastboot" and ADB downloads a mystery? How to get them to work?
Related
So, newb me did a bad thing. I managed to install TWRP Recovery on my Nexus 5 to attempt rooting it. It didn't work a t first so I tried cleaning up some existing data. I did a factory reset, a format data, and... drumroll... advanced wipe, where I selected everything.
When I went to reboot, TWRP told me there was no OS.
I've already downloaded the stock KitKat for my device and the sdk tools (and even the unified android toolkit found here in the forums). I couldn't find a way to flash stock yet
It seems my device does not connect on USB in ADB mode, it only shows Recovery mode. Trying "fastboot flash" gets stuck on "< waiting for device >". Using "adb devices" shows something like "some_number recovery".
Any suggestions? I can do adb shell but I don't know how to restore the files I deleted without flashing or how to make flashing work.
Thanks a lot
Someone resolved this same issue. http://forum.xda-developers.com/showthread.php?t=2533148
That worked like a charm.
Thanks a lot!
I recently changed back my build.prop to the original one that i backed up before. Then my device cannot boot anymore. It is stuck in the ASUS splash screen when i boot the device.
Then I flash the latest CWM recovery. But the latest version CWM cannot do anything like factory reset or flash zip.
After that, i tried to use the "wipe data" in the bootloader, it doesn't work either (still stuck in the splash screen).
And then i tried cold boot linux and it also doesn't work. Up to this point, I cannot find anyway to fix it.
However, I found that adb is somewhat working in CWM recovery. I tried "adb push build.prop /system/build.prop" (the build.prop is extracted from the US_epaduser_10_26_1_7_UpdateLauncher.zip package from ASUS official site), it doesn't work either.
I put the US_epaduser_10_26_1_7_UpdateLauncher.zip package from asus support site in sd card and tried to flash it by CWM recovery, it doesn't work either.
AFTER ALL THESE PROCEDURE, i think the system is corrupted because of some possible dirty wipe
IS THERE ANY WAY TO WIPE EVERYTHING AND RESET THE whOLE SYSTEM?
i feel like my device is completely dead... so i need help and solution asap
my device is unlocked, rooted, and updated to 10.26.1.7 android 4.3.
it is a US version.
btw i asked ASUS support and they said they would charge CAN$330 for fixing it (replacing the main board), which is.........
So is there any ways to fix it without sending it to asus repair ccenter?
I want to make sure that
1. The wipe data function in the bootloader works
2. Does wiping data in bootloader fix the build.prop problem
Or do anyone of you have any idea of solving tthis problem?
ANYWAY TO WIPE EVeRUTHING INCLUDES SYSTEM thROUGH BOOTLOADER?
sorry for my bad english
Have you tried to install Full Recovery Mode ?
First Enable USB Debugging and watch if your Device is correctly recognized on you Device Manager .
Search and install the software , for first use i suggest to search some Tutorials about this.
Then you can use the Full Recovery Mode and format / wipe cache and system .
Ive finished a simple tutorial i found on a trusted site but that basically said the same as CWM's guide.
the device is an xt1032 running rooted, bootloader unlocked, stock android 4.4
what i did:
1) download adb/fastboot and check their PATH
2) shift-roghtclick its folder and open command prompt
3) fastboot devices (and found mine)
4) mfastboot flash recovery "name of the recovery".img (everything fine, phone gave the "usual" partition size error)
5) when i try to go into recovery mode, the phone first plays its "warning devices bootloader is unlocked" screen and then, instead of actually loading the recovery, it starts displaying graphic glitches, at which point i usually freak out and reboot it into normal mode.
what might have gone wrong? need more info?
The reason behind doing all this is that i want to install this ROM http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
think ive softbricked it
after another unsuccesfull attempt at installing a recovery, the phone displayed the same kind of wrid lines and blank screen as it did before. when i resetted it, that persisted, therefore i cant get it to load android either.
any help would be extremely apreciated.
now i have also being able to get into recovery mode with the command "fastbot boot recovery_image.img" but it only wants to stay for 10s tops
i have already wiped data/cache and dalvik cache with those 10s i have cause they seem to be enough. 2-3s after that ends, the phone reboots anyways.
any help to be given? i feel quite alone here...
also, i cant get enough time to sideload a rom, and i fear it will restart before finishing the installation
I unlocked the bootloader on an old HTC One S through the directions on the HTC Developer website. I then loaded the CWM recovery and did the rooting and installed the Rom manager app. The SuperSU update had to be added with the abd sideloader and the rootcheck said it had root access. Both of those programs seemed to be working fine. Then I send the Zip file of a ROM (idk which one because I renamed it so it would be easier to enter) and from the ROM manager I select the one I just sent and go to install it.
Then the phone turns off and a long string of code ends with "transfer successful" or something to that effect but stays there. I rebooted and tried again and the same thing. Tried again and did a factory reset from the recovery but nothing would get the phone to boot past the HTC screen. I tried Wiping the davlik cache and the regular wipe and hard reset and adding the recovery again but NOW MY PHONE DOESNT SHOW UP WITH ADB DEVICES CMD.
I am already in over my head but I have been enjoying learning from this and other websites about how android works. However I think I have exhausted my research options and I am at dead end...
How can I get the adb commands to work again?
bmckeeoneill said:
I unlocked the bootloader on an old HTC One S through the directions on the HTC Developer website. I then loaded the CWM recovery and did the rooting and installed the Rom manager app. The SuperSU update had to be added with the abd sideloader and the rootcheck said it had root access. Both of those programs seemed to be working fine. Then I send the Zip file of a ROM (idk which one because I renamed it so it would be easier to enter) and from the ROM manager I select the one I just sent and go to install it.
Then the phone turns off and a long string of code ends with "transfer successful" or something to that effect but stays there. I rebooted and tried again and the same thing. Tried again and did a factory reset from the recovery but nothing would get the phone to boot past the HTC screen. I tried Wiping the davlik cache and the regular wipe and hard reset and adding the recovery again but NOW MY PHONE DOESNT SHOW UP WITH ADB DEVICES CMD.
I am already in over my head but I have been enjoying learning from this and other websites about how android works. However I think I have exhausted my research options and I am at dead end...
How can I get the adb commands to work again?
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
Good luck.
I was using package disabler pro to disable some Samsung apps, like galaxy apps, billing etc. I have had the phone like this for months without problem. Today I re enabled galaxy apps and rebooted phone and now my phone is boot-looping, stuck on samsung logo. I re flashed the EXACT same rom that is on there via ODIN, (XSA g920i) and it STILL boot loops. Normally this fixes problems like this. The phone is stock, uprooted. Don't tell me I have to factory reset it all?
Will not even boot up in safe mode.
This can be moved to the Q and A section but I also didn't realise you can soft brick your phone without root.
I am definitely sure it was re enabling some apps in package disabler pro that did it. Is there some way to ABD console re enable all apps or undo whatever the program has done?
I'm willing to install twrp recovery on the phone so I can mount system and undo whatever the program has done. Does anyone know what to alter?
$10 paypal for solution that doesn't involve loosing data.
If I factory reset, will I be able to recover the files on there like pictures and images with a program?
Install custom recovery, then mount you sd partition in recovery and connect to pc then move all your pics etc to pc, then factory reset
rosso22 said:
Install custom recovery, then mount you sd partition in recovery and connect to pc then move all your pics etc to pc, then factory reset
Click to expand...
Click to collapse
Yea Im aware I would be able to do that but I want to be able to undo the programs influence so I can boot into my phone again.
So I take it I use the latest twrp and just flash via odin? I dont need to also flash a custom kernel?
Yeah just flash recovery with odin, you could probably try using the file manager in recovery to delete the galaxy apps apk, or fixing permissions may work, or possibly wipe cache and dalvik and may be able to boot, the custom recovery gives you a few options
I contacted the dev and he said there is a way to fix it via ABD. The stock s6 mm recovery has an ABD option, is this the same as a proper abd when the phone is booted up, or does it only allow you to push signed files and updates accross?
So does this mean it is possible to fix the issue without flashing custom recovery?
Is there another section this can be moved to? Im surpised there isnt more information for such a popular app with a common problem.
I just realised I have reactivation lock enabled. Does this mean I CANNOT flash custom recovery? If thats the case I dont even want to try.
How to enable 'Android system' back?
Hello!
I have disabled 'Android system' in 'packagedisabler pro' in Samsung sm-9005 and now the phone is stuck with Samsung logo and stars during booting. The phone cannot boot. How to enable 'Android system' back?