Hey all, hope everyone is having a great day (I'm not),
I own a SM-T510 Samsung Galaxy Tab A 10.1 WiFi.
It all started when I tried to flash Nexus and it worked partially, but I didn't gain access to my internal storage for some reason, so I reverted back to stock rom.
Then for some reason part of the nexus rom was still there, but I was afraid of damaging my device further.
For some reason, netflix wasn't working, so I tried to apply a software update to my device using Smart Switch.
The update didn't work and I was caught in a Nexus bootloop. I entered download mode and I tried flashing twrp using odin. I thought it worked until I realised that it wouldn't get past the teamwin screen.
I re-entered download mode and there it gave me an option to factory reset the device while locking the bootloader. This is where I screwed up as I thought what else could possibly happen to my device?
SO I locked my bootloader and whatever I did I couldn't get out of download mode. AND here I screwed up even more. I tried to flash the stock ROM again using odin as a last resort but it just wouldn't complete after 10 minutes, so I closed Odin and restarted my device and here I am, stuck in a screen that says, "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." Now obviously this wouldn't work because my device isn't even listed there. But to note, my device is recognised by Odin and my PC.
Note: I am an absolute noobie at rooting so be easy on me.
Note 2: adb and fastboot doesn't work for me for some reason, my powershell says, "The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again."
Thank you all for any help. I am at my wit's end.
Related
Phone specs:
Samsung Galaxy S3 Verizon SCH-i535
It was already running KitKat 4.4.2 before I rooted
This is my first time rooting and flashing ROMs to my Samsung Galaxy s3 and I have bricked it. I'm pretty sure it can be salvaged but have yet to find anything that works.
I have written the long version for those who need it, but the short version is that I screwed up and can no longer boot into recovery mode or normal mode, I'm not even sure if Download mode is working, and my device isn't recognized by Kies or Odin on my PC so I cannot yet do a recovery from there.
As of now my phone only boots into Odin Mode and gives the following info:
ODIN MODE
PRODUCT NAME: SCH-I535
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
QUALCOM SECUREBOOT: ENABLE
BOOTLOADER AP SWREV: 2
and displays the yellow triangle error and says: Firmware upgrade encountered an issue. Please use Software repair Assistant & try again.
I tried to use Samsung Kies which has an emergency firmware tool but my device will not connect and become recognized by the program.
This is pretty much where I'm stuck.
Keep reading if you need additional info.
Steps leading up to problem:
I was able to Root the device succesfully
I then downloaded the latest CM11 package (cm-11-20140217-NIGHTLY-d2vzw.zip) and Gapps
I also downloaded the TWRP recovery img (openrecovery-twrp-2.7.1.0-d2vzw.img)
Once I had these downloaded I got the app [ROOT] Rashr - Flash Tool
I opened the app and tried to do a backup but I'm pretty sure it failed, or at least it said it failed. I couldn't find out how to check, but was not worried since I have already backed up my important files to the verizon cloud.
On the app I went to recover using other file and found the TWRP recovery img I downloaded.
From here I booted into recovery manually, but it did not bring up the TEAMWIN screen for TWRP like I've seen in other video tutorials so I rebooted into normal mode went to the Rashr app again and followed the prompt to do a Recovery boot using the TWRP img.
THIS IS WHERE THE PROBLEMS BEGAN:
It began to lead into recovery mode but it gave a message that said something along the lines that I have tried installing a custom OS and to take my phone to the nearest verizon store.
I turned it off and tried to boot back normally but got the same error.
I tried to boot into Download mode and was successful! So I thought yaay!
Read a tutorial to reload a stock version of android here: http://forum.xda-developers.com/showthread.php?t=2586319
I followed all the steps but when i got to 7. which said You should see your phone under ID:COM (you should also see it has been added in message) I was not seeing my phone there. I figured it may be OK since I was able to install the drivers so that meant the USB was working so I went ahead and ran Odin to recover Jelly Bean 4.3 onto the device.
My thoughts and guesses as to what the problem is:
I think that it may be because I was already running 4.4.2 and/ or didn't have the proper bootloader when I tried to do the TWRP recovery.
Am I on the right track? Thanks for any help!
Please ask. In correct forum this is int'l s3 (i9300) forum
Device: Nexus 9 (Wi-Fi), Bootloader Unlocked
Computer: Windows 10 (Bootcamp on a Retina MacBook Pro)
After and unsuccessful attempt to install CM 12.1 on my Nexus 9 (Wi-Fi) using TWRP, I tried using this method to return to stock:
http://forum.xda-developers.com/nexus-9/general/guide-nexus-9-to-stock-guide-unbrick-t2975668/
I thought it had worked perfectly, but the tablet still would not boot. I went back and looked at the command prompt log and realized I had made a grave error: I had flashed everything except for the system image. I re-entered fastboot in an attempt to fix it by flashing the system, but now the tablet will not connect to my computer at all. I have tried to remove and reinstall the ADB drivers, but it doesn't show up at all in Device Manager. I tried booting into recovery via fastboot, but got an image of the android mascot knocked-out with an exclamation point, presumably since I over-wrote it with the method above.
Any ideas on how to restore the fastboot/adb connection with my computer? If I can accomplish that I can presumably just flash the system image and that would restore the stock ROM.
Any insight at all would be much appreciated.
dgindra said:
Device: Nexus 9 (Wi-Fi), Bootloader Unlocked
Computer: Windows 10 (Bootcamp on a Retina MacBook Pro)
After and unsuccessful attempt to install CM 12.1 on my Nexus 9 (Wi-Fi) using TWRP, I tried using this method to return to stock:
http://forum.xda-developers.com/nexus-9/general/guide-nexus-9-to-stock-guide-unbrick-t2975668/
I thought it had worked perfectly, but the tablet still would not boot. I went back and looked at the command prompt log and realized I had made a grave error: I had flashed everything except for the system image. I re-entered fastboot in an attempt to fix it by flashing the system, but now the tablet will not connect to my computer at all. I have tried to remove and reinstall the ADB drivers, but it doesn't show up at all in Device Manager. I tried booting into recovery via fastboot, but got an image of the android mascot knocked-out with an exclamation point, presumably since I over-wrote it with the method above.
Any ideas on how to restore the fastboot/adb connection with my computer? If I can accomplish that I can presumably just flash the system image and that would restore the stock ROM.
Any insight at all would be much appreciated.
Click to expand...
Click to collapse
Hello,
I have reported this thread to be moved to right Q&A section in order to get expertise help.
-Vatsal
Have you ever tried to connect your tablet to another computer?
Turns out I forgot to actually press the button in fastboot that enables the USB connection (I feel even more stupid now). Was able to return to stock, albeit with the "This device is corrupt" message during boot.
dgindra said:
Turns out I forgot to actually press the button in fastboot that enables the USB connection (I feel even more stupid now). Was able to return to stock, albeit with the "This device is corrupt" message during boot.
Click to expand...
Click to collapse
I got the same message yesterday after I returned to stock kernel from a custom one. What I did to get rid of that warning message was to flash all img file(boot, cache, recovery, system, vendor) in MMB29K factory image. (Bootloader is optional) [After that I also performed a factory reset but this step might be unnecessary, do it if the message still exist after flashing stock images] If you don't like that warning you can try these procedures.
So I'm stuck at this blue screen in my Samsung Tab A 8.0 with the message: "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
See what had happened was...
I was having problems with the battery and when I booted into recovery it said a message (can't remember it now) along the lines of: E: can't load bitmaps /poc0008 No such file or directory! & successfully verified DM-Verity hash & E: can't load /dev/block/(something) No such file or directory!
So here went I, Mrs. Pseudo-developer and I upgraded the firmware via Odin ver 3.13.1 Previously I think it was N7.0.1 and then it became N7.1.1. It was a much smoother experience and my battery didn't die as quick. Yay!
But there I had to go tinkering... Again, via Odin (which I'm comfortable with, btw. I have all my devices firmwares' backed-up. All my devices are rooted) tried to flash cf-autoroot and something happened, I couldn't read the argument and I booted into recovery and then into bootloader and started to reflash my firmware only for my usb to get unplugged in the midst of it. This sucks and does anybody has a tissue, because my tablet just died.
dilcia said:
So I'm stuck at this blue screen in my Samsung Tab A 8.0 with the message: "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
See what had happened was...
I was having problems with the battery and when I booted into recovery it said a message (can't remember it now) along the lines of: E: can't load bitmaps /poc0008 No such file or directory! & successfully verified DM-Verity hash & E: can't load /dev/block/(something) No such file or directory!
So here went I, Mrs. Pseudo-developer and I upgraded the firmware via Odin ver 3.13.1 Previously I think it was N7.0.1 and then it became N7.1.1. It was a much smoother experience and my battery didn't die as quick. Yay!
But there I had to go tinkering... Again, via Odin (which I'm comfortable with, btw. I have all my devices firmwares' backed-up. All my devices are rooted) tried to flash cf-autoroot and something happened, I couldn't read the argument and I booted into recovery and then into bootloader and started to reflash my firmware only for my usb to get unplugged in the midst of it. This sucks and does anybody has a tissue, because my tablet just died.
Click to expand...
Click to collapse
Can you still go into recovery mode? Or the device was hard bricked? If the device is not booting you can try to patch boot.img
Hello androids, I have a big problem or a good challenge, depends on your optimism. I've been looking for and trying solutions for hours and hours, but I think I've come across a wall and I need your help:
Originally I wanted to root my s7 Edge / SM - G935F (OS Marshmallow 6.0.1) by following a tutorial using an autoroot ROM for this phone. I remember I had USB debugging and OEM unlock enabled. I also installed the USB / ADB drivers correctly.
I used Odin v3.11, since they recommended using it for this mobile and MM 6.0.1. According to Odin, the rom was installed successfully, but my phone entered a loop with the Samsung logo and "RECOVERY IS NOT SEANDROID ENFORCING". Something failed in the process and I decided to install a S7 Edge stock ROM in 8.0.0 from SAMMobile (this one) with Odin v3.13 using HOME_CSC so that I don't lose certain data
Unfortunately everything was going well until just at the end when "hidden.img" did not process correctly and resulted in FAIL. I've been since then stuck with this error:
"An Error has occurred while updating the device software. Use the Emergency Recovery in the Smart Switch PC Software."
It won't even turn off. From there I can only access the Download Mode and neither the Smart Switch or the ADB & Fastboot console won't detect the device. Odin does recognize the phone, but every time I try to install a rom, the log gets stuck in "SetupConnection ..".
I have tried a bunch of solutions such as removing the "hidden.img" from the package, reinstalling the drivers, changing the USB port, changing Odin's version, installing only the BL, etc., but nothing shows progress...
I'm sorry if during the process I managed to do some stupidity that I am not aware of. Other phones I have never had problems, but now I feel defeated and lost. I need a savior! :crying:
Any way to make Odin work, ADB detect my device or access a working bootload? Thanks in advance!
Hi everyone! So, I have an Huawei Mate 10 lite that suddenly stopped working. It isn't rooted and its bootloader is locked. It was working fine up until that point and then it turned off starting a bootloop that is still going on after a long a time.
Since going into fastboot&rescue is the only shortcut key that seems to be working, I tried doing what it said "Please connect USB cable to your computer and open Hisuite". However, HiSuite says that is cannot support system recovery in my phone which is simply hilarious...
I tried putting and update.app file on a dload folder in the root of the sd card after seeing some people suggesting that - but I can't access the upgrade mode (volume up and down + power does absolutely nothing). Also, since Huawei decided they should just turn their backs on this phone, all download links to the update roms are down and I had to download it from a Russian website - perhaps it not being the correct version is the problem with me not being able to go into upgrade mode, but I honestly have no idea how to even get another version.
I tried flashing through adb but since the bootloader is locked, it gives me a "command not allowed" message.
Going into recovery is impossible, it goes into bootloop also, just like upgrade mode.
I'm getting quite desperate since nothing seems to be working... Please, if you have any suggestions, HELP! I'll be throwing this damn thing against a wall if I'm not able to fix it soon