Hello guys, I really hope you could help me on this one, I screwed up really really bad.
Let me explain the problem, I wanted to be a smart ass, and install an unofficial version of Nougat, and I succeeded, but then I wanted to remove it because I wasn't satisfied of it.
So I went on recovery mode and "accidentally" erased everything... I said that I screwed up ok, at leat I'm aware of it haha
So now my problem is that my phone is completely empty, cant get into recovery mode, only in fastboot mode, adb and fastboot don't recognize my phone, and that's logical because there is nothing in it.
So, is my phone completely dead, or is there a way to put the original os in it?
Thank you guys so much for helping me, i'm desperate...
PS/ I know this is probably the wrong category for this topic, but since it's my firt post, I hope you could understand, appreciate
did you install all the needed oneplus drivers to your computer in order to recognize it? If that's your problem, then you could flash twrp onto your phone and get stock OOS back.
Gwennito said:
Hello guys, I really hope you could help me on this one, I screwed up really really bad.
Let me explain the problem, I wanted to be a smart ass, and install an unofficial version of Nougat, and I succeeded, but then I wanted to remove it because I wasn't satisfied of it.
So I went on recovery mode and "accidentally" erased everything... I said that I screwed up ok, at leat I'm aware of it haha
So now my problem is that my phone is completely empty, cant get into recovery mode, only in fastboot mode, adb and fastboot don't recognize my phone, and that's logical because there is nothing in it.
So, is my phone completely dead, or is there a way to put the original os in it?
Thank you guys so much for helping me, i'm desperate...
PS/ I know this is probably the wrong category for this topic, but since it's my firt post, I hope you could understand, appreciate
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/one...ga-unbrick-guide-hard-bricked-t3272108/page19
shravanv3 said:
Try this
http://forum.xda-developers.com/one...ga-unbrick-guide-hard-bricked-t3272108/page19
Click to expand...
Click to collapse
The thing is, my phone is detected by my PC, as Kedacom USB Device > Android Bootloader Interface.
I tried to follow the guide from page 1, but since my phone is not detected as Qualcomm whatever, I don't if I can follow this procedure.
And also, when I turned on my phone, I juste have the logo One plus and Power by Android. If i try a recovery mode reboot, it's same screen, over and over. The only thing I can get into, is the FastBoot mode, by holding Volume up + Power, but I don't know if I can do anything with it, because even in this mode, adb won't recognize it.
Related
I recently bricked my tablet after having it rooted for a very long time...a Samsung-issued update apparently screwed with something crucial.
Anyway, I tried the nvflash recovery methods as mentioned in this thread: http://forum.xda-developers.com/showthread.php?t=1130574
However, it seems that I have what they called a "locked" tablet. I get the 0x4 error he mentions and absolutely nothing happens when I send the command in nvflash.
Is there any update on this recovery method with locked tabs? I tried seeking paid services where they hook up devices to a JTAG and whatnot, but I've only seen that for the original Galaxy and not the 10.1--if you have any information about that route, that would help too.
Thanks!
you can try flashing a old rom if you can thats what i did and it worked for me
samwest39 said:
you can try flashing a old rom if you can thats what i did and it worked for me
Click to expand...
Click to collapse
The thing is I can't flash to different ROMs or even get the Tablet to boot up into download mode...
go to recovery mode
I can't get into recovery mode too. All of the partitions are screwed, and the only way of reviving this device is by flash through the NVidia Recovery Console (nvflash). The thing is, my device is one of the lucky ones that are locked..Thus, it requires a special key to unlock it before I can do anything in nvflash.
I have no idea if this would work, but you could try it ...
A few months ago I was flashing a ROM on a friends phone and something went wrong, the phone wouldn't even boot up any more, the screen stayed blank all the time, no matter which combination of buttons I pressed of how long I held them down for. ODIN didn't recognise it being connected to the PC etc... nothing worked.
Then I tried hooking the phone to the PC again and tried to do something with adb. And somehow, the phone was connected on adb. Tried an adb restart-to-download command and after a minute or two, the phone booted up and I could flash through ODIN again.
I have no idea why it worked, but it did ... lucky me .
So while I doubt it will work, it might still be worth a try. And if adb connects in any way you could maybe figure what was wrong and somehow fix it?
I also heard about some phones being locked out in a similar way and a procedure in the lines of "take the battery out, hold down 3 buttons, slide the battery in WHILE STILL HOLDING the buttons" worked, maybe there's something similarly "hidden" on the tab?
I hope you find your answer!
Hi everyone! As stated in the title my phone(p769) wont boot completely, I was in the middle of doing the bootloader unlock when I accidecntly replaced the bin during the root process of it with the wrong bin. Instead of replacing it with the v6 tmobile usa one I used the v5 canadian one. Now when I boot my phone up the lg screen is there and then eventually it just hits an android with a red exclamation point. I've tried Re-flashing while its in s/w upgrade mode with the flasher set to emergency, and Ive tried pressing the home button + vol down + power to no avail(it goes through the process but the same thing happens)
Any help at all would be greatly appreciated and many thanks in advance!
Edit: Also when I try to reflash, it just says it cant communicate with my phone. Ive uninstalled and reinstalled the drivers several times but seeing as how I cant acutally get into the phone Im not sure what else to do.
Edit 2: So ive been trying do something witht his for the past three hours and I cant get anywhere with it. I cant get the phone to show up as an adb device while its in s/w upgrade mode, and at the red exclamation point screenit shows up but as recovery and the lg tools fail to communicate with it. I would really appreciate if anyone knew how to deal with this.
Just in case anyone stumbles upon this and has the same issue I would like to say that i finally got mine fixed.
It has been a long day of frustrations but I finally got it there with the help of some awesome tutorials.
In order to fix it I had to fastboot my phone and flash the default loader and boot then my device would show up in my adb devices and I could sucessfully flash and root it.
hufger said:
Just in case anyone stumbles upon this and has the same issue I would like to say that i finally got mine fixed.
It has been a long day of frustrations but I finally got it there with the help of some awesome tutorials.
In order to fix it I had to fastboot my phone and flash the default loader and boot then my device would show up in my adb devices and I could sucessfully flash and root it.
Click to expand...
Click to collapse
how you resolve it?
saman_z1384 said:
how you resolve it?
Click to expand...
Click to collapse
I followed the fastboot tutorial and searched around in the help forum for people with similar issues and found a post where lelus posted both of the files I needed to flash with fastboot, from there I just put my phone in s/w upgrade mode and followed Lelus guide for root/flash
Phone Info: AT&T Galaxy S3, Cyanogenmod 10.2
So, I was messing around, trying to get the WiFi to work on my phone when I tried a solution I found on the forums: updating one of the files involving the radio. After flashing the file, my phone shut off and opened in Download mode. Now I can't leave download mode, can't enter recovery mode, and can't boot my phone. Oh, and my computer can't recognize the phone either. I've searched for hours looking for a solution and I'm freaking out. I seriously need some help with this.
Basically it says:
Could not do normal mode
Odin Mode
Phone Model, etc.
I really don't care how its done, what ROM I end up with, or anything else. I just need this phone to be able to work properly again. Thanks for any help!
I think it's emmc sds
?★Sent from My GT-9300★?
Isuru cs said:
I think it's emmc sds
��★Sent from My GT-9300★��
Click to expand...
Click to collapse
That's sudden death syndrome right? Is there any good fix for it or way to get it replaced despite it being rooted and the ROM changed? (I did know that going into rooting might cause problems like this, just hopeful that there's a way)
Edit: If there's a way to get the phone to be recognized by a computer; I can still access download mode and would have no problem doing a full restore from there. I've tried installing drivers for the phone, it seems like the phone is unable to be recognized by any computer I try also.
Finally did get Recovery Mode to work. Don't know if that can help much
JacobH9 said:
That's sudden death syndrome right? Is there any good fix for it or way to get it replaced despite it being rooted and the ROM changed? (I did know that going into rooting might cause problems like this, just hopeful that there's a way)
Edit: If there's a way to get the phone to be recognized by a computer; I can still access download mode and would have no problem doing a full restore from there. I've tried installing drivers for the phone, it seems like the phone is unable to be recognized by any computer I try also.
Finally did get Recovery Mode to work. Don't know if that can help much
Click to expand...
Click to collapse
add a screenshot of recovery mod,download mod
SDS is when the phone is completely dead, doesn't boot at all.
You are posting in the wrong forum, this is for the i9300 only.
If you've flashed a file meant for another phone then you have probably hard bricked it.
If download mode doesn't connect to pc then you need a repair centre.
Sent from my GT-I9300 using Tapatalk
Solved the issue! So I managed to load my original ROM file onto my external SD and install it from recovery. For anyone else who has this problem, I just loaded the zip file onto the SD, stuck it in my phone, powered off and clicked Volume Up Home and Power to get into recovery, (phone specific for Gs3 on getting to recovery) and went to install from zip and installed the file. Problem solved for me, although it did wipe all the data which isnt a big deal really. Phew. That was a scare. And it fixed my WiFi problem, so all in all a good learning experience for me
Anyhow, thanks for all the help, I appreciate it! And sorry for hitting up the wrong forum, its my first time on it.
Thanks again!
JacobH9 said:
Solved the issue! So I managed to load my original ROM file onto my external SD and install it from recovery. For anyone else who has this problem, I just loaded the zip file onto the SD, stuck it in my phone, powered off and clicked Volume Up Home and Power to get into recovery, (phone specific for Gs3 on getting to recovery) and went to install from zip and installed the file. Problem solved for me, although it did wipe all the data which isnt a big deal really. Phew. That was a scare. And it fixed my WiFi problem, so all in all a good learning experience for me
Anyhow, thanks for all the help, I appreciate it! And sorry for hitting up the wrong forum, its my first time on it.
Thanks again!
Click to expand...
Click to collapse
you are a lucky one, look at mine:
http://forum.xda-developers.com/galaxy-s3/help/emmc-problem-t2722684
I was trying to figure out some info on my phone and learn to root it (it had a bad previous root apparently), this is the thread where i originally asked but looks like i messed something up. Explanation below (keep in mind that i am new to the rooting scene and have a very basic understanding of how it works)
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Hi,
So I've had a lot of trouble getting TWRP flashed to this phone. After a bunch of tries I got stuck in a bootloop but I was still able to enter fastboot and recovery. I then flashed the stock fastboot ROM which fixed it and I was able to get back into the system.
I then hooked it up to my laptop again, but when I went to turn it off to get back into fastboot mode it just doesn't do anything except bootloop. I get to see the Redmi logo for a few seconds, and then it just endlessly reboots.
I can't enter fastboot nor the recovery, otherwise this would've been an easy fix. I also can't turn off the phone. Does this mean I'm ****ed? I saw the post before me where somebody seems to have the same issue, but their phone doesn't show anything on the screen at all, which is why I'm not sure if I hard bricked it or not.
It's strange too, because I have plenty of experience flashing bootloaders and ROMs, even with other Xiaomi phones, but this one has been a pain in the ass from day one. I made sure to not use anything not meant for my region (EEA) or phone model (Camellian) so I have no clue what went wrong. Any ideas?
iamkaruna said:
Hi,
So I've had a lot of trouble getting TWRP flashed to this phone. After a bunch of tries I got stuck in a bootloop but I was still able to enter fastboot and recovery. I then flashed the stock fastboot ROM which fixed it and I was able to get back into the system.
I then hooked it up to my laptop again, but when I went to turn it off to get back into fastboot mode it just doesn't do anything except bootloop. I get to see the Redmi logo for a few seconds, and then it just endlessly reboots.
I can't enter fastboot nor the recovery, otherwise this would've been an easy fix. I also can't turn off the phone. Does this mean I'm ****ed? I saw the post before me where somebody seems to have the same issue, but their phone doesn't show anything on the screen at all, which is why I'm not sure if I hard bricked it or not.
It's strange too, because I have plenty of experience flashing bootloaders and ROMs, even with other Xiaomi phones, but this one has been a pain in the ass from day one. I made sure to not use anything not meant for my region (EEA) or phone model (Camellian) so I have no clue what went wrong. Any ideas?
Click to expand...
Click to collapse
I think you are on the wrong forum, this is for Redmi Note 10 (mojito/sunny)