Develop Bugs

Wiped SDcard after flashing custom rom = Bricked!

I think I bricked my HOX.
I have custom recovery installed and lots of battery left. I tried to install a new rom (android revolution) and it worked fine, then I noticed that I had lots of left overs on my sd card from earlier installations. So I decided to format it and cleaned /data /system and /cache. The result is that the phone is stuck at "HTC - Quietly brilliant".
Is there anyway possible for me to connect the phone to the usb and transfer the rom files again to flash them?
Or what should I do to have my phone working again.
I have read the guide and I am currently downloading a RUU file, but I prefer not to lock the bootloader > revert to stock > flash rom again.
Please advice,

Samiii2 said:
I think I bricked my HOX.
I have custom recovery installed and lots of battery left. I tried to install a new rom (android revolution) and it worked fine, then I noticed that I had lots of left overs on my sd card from earlier installations. So I decided to format it and cleaned /data /system and /cache. The result is that the phone is stuck at "HTC - Quietly brilliant".
Is there anyway possible for me to connect the phone to the usb and transfer the rom files again to flash them?
Or what should I do to have my phone working again.
I have read the guide and I am currently downloading a RUU file, but I prefer not to lock the bootloader > revert to stock > flash rom again.
Please advice,
Click to expand...
Click to collapse
What is stoping you from booting into recovery, plugging it in via USB and sticking a new ROM on there... Sorry if I'm wrong, don't have the phone yet but seems like what I'd try to do...

bortak said:
What is stoping you from booting into recovery, plugging it in via USB and sticking a new ROM on there... Sorry if I'm wrong, don't have the phone yet but seems like what I'd try to do...
Click to expand...
Click to collapse
I am trying, but the phone is not showing up in my explorer so I can not transfer any files?? Tried both in recovery and in the stucked mode. However I might be doing it wrong?

Samiii2 said:
I am trying, but the phone is not showing up in my explorer so I can not transfer any files?? Tried both in recovery and in the stucked mode. However I might be doing it wrong?
Click to expand...
Click to collapse
When you boot into recovery do you not have an option to toggle USB storage when you plug the phone in via usb?

bortak said:
When you boot into recovery do you not have an option to toggle USB storage when you plug the phone in via usb?
Click to expand...
Click to collapse
There is an option under Mounts and storage menu in CWM that allows me to "mount UBS storage" However it is not working and returning an error, "Unable to open ums lunfile (No such file or directory)"

I guess boot into bootloader and then push your desired .zip over...
Sent from my HTC One X using xda premium

USB is not yet working in recovery for the HOX, I don't see any other option then going back to stock....
Send from CM9 powered Galaxy Note

Klyupp said:
USB is not yet working in recovery for the HOX, I don't see any other option then going back to stock....
Send from CM9 powered Galaxy Note
Click to expand...
Click to collapse
Oh, well in that case the only reasonable thing would be to also disable the "erase sd-card" feature also, to prevent issues like this
Woaahh just saw your signature, you got a 4s over the SGS II? (I'm guessing) ohh dearrr

why did you format /system? ROFL thats ur problem right there.
Your only options are
a.) wait till recovery is released w/ USB mounting currently there is none.
b.) obtain the correct official HTC RUU (HTC vendor tool) and flash in fastboot. This WILL WORK but you need the exact correct RUU for your specific build

c) use adb push commands
And btw bricked means the phone is completely dead, you can boot but not in rom
Sent from my HTC One X using xda premium

Ok, i got this baby running again. Have to say it was real dead at one time too. No battery left and no possibility to charge. Promised myself not to play anymore with it if I bring it back to life again.
However, I read somewere that I could use the iphone charger to get some batterylife to boot it and it sure worked. Left it on and the next day the light was green on the phone. My face went from to
With full battery I downloaded the 1.29 RUU but it still didnt work. Read somewere else agian that I had to relock the phone again to be able to use the RUU. So I did and it sure worked. Brought it back to stock and here I am again with a working phone in my hand.
I couldnt stay away from ARHD so I unlocked the bootload again, flashed it and customized
Must be real real hard to brick this phone completely!

Flashed revolution 4.3 and phone wont boot....

Hey everybody, I flashed the revolution rom from TWRP. It went through the setup menu and then finished flashing and went to reboot. Nothing. No button combinations have been able to start the phone and when I put the battery in the camera flash blinks once and thats it. If I charge the phone without the battery I get a solid red LED on the front but still no boot. I tried the unbrick by sd card method and that doesn't work either. What happened?
Thanks for your help!

Are you sure the rom was for an i747, i747m, or d2lte?
Do you have a link to the ROM?

audit13 said:
Are you sure the rom was for an i747, i747m, or d2lte?
Do you have a link to the ROM?
Click to expand...
Click to collapse
Yes,
This is the page that led me to the ROM:
http://joyofandroid.com/10-best-custom-roms-samsung-galaxy-s3/
And this is the actual ROM:
http://forum.xda-developers.com/gal...m-android-revolution-hd-52-0-android-t1797334
I noticed on the ROM page it says "improved CPU support". There were a bunch of tweak apps I checked in the installation menu. Not sure if it's possible they cooked the CPU?
Thanks for taking the time to help me.

The ROM you linked is for the international version of the s3 (i9300, i9305, look at the top of the forum heading), not the North American version.
What happens when you connect the phone to your computer with the USB cable? Do you see this in device manager: qhsusb_dload ?

audit13 said:
The ROM you linked is for the international version of the s3 (i9300, i9305, look at the top of the forum heading), not the North American version.
What happens when you connect the phone to your computer with the USB cable? Do you see this in device manager: qhsusb_dload ?
Click to expand...
Click to collapse
After your post I also noticed it wasnt the right model number. Unfortunately the USB only worked for charging. I bought the phone with a known bad usb port, replaced it with a new usb and it only worked for charging after that. I have been flashing roms from the SD Card. Is there a way to unbrick other than JTAG (if that will even work)?

What ROM was on your phone before you flashed Revolution? You could try following one of the debrick threads.
http://forum.xda-developers.com/showthread.php?t=2549068&page=3

audit13 said:
What ROM was on your phone before you flashed Revolution? You could try following one of the debrick threads.
http://forum.xda-developers.com/showthread.php?t=2549068&page=3
Click to expand...
Click to collapse
I had Dirty Unicorns on there before. I tried the solution in the link but the phone behaves exactly the same with the SD Card in or out. I have been flashing roms for years and never bricked a phone but it looks like I got too careless. Do you know if a working USB is required for a Jtag repair and return to stock rom to work?

For JTAG, I don't think they use the USB port. They need to get access to the rom chip to program it.
http://www.forensicswiki.org/wiki/JTAG_Samsung_Galaxy_S3_(SGH-I747M)

ughhh
I believe I just did the same thing as you. I followed the same link and go to the same page.
Downloaded from here http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
Now my phone wont even turn on, red charging light comes on with battery out and plugged into PC.
I do see : qhsusb_dload in device manager... I thought my phone was i9300, should've double checked. Was just in such a rush to try something new because my phone was pretty horrible with Cyanogenmod on there.

79TAKid said:
ughhh
I believe I just did the same thing as you. I followed the same link and go to the same page.
Downloaded from here http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
Now my phone wont even turn on, red charging light comes on with battery out and plugged into PC.
I do see : qhsusb_dload in device manager... I thought my phone was i9300, should've double checked. Was just in such a rush to try something new because my phone was pretty horrible with Cyanogenmod on there.
Click to expand...
Click to collapse
Looks to me like your phone is hard-bricked. You could always try booting the phone with a de-brick image.

audit13 said:
Looks to me like your phone is hard-bricked. You could always try booting the phone with a de-brick image.
Click to expand...
Click to collapse
Thanks, I had read about this in another thread. I gave it a shot and used a debrick image on a 16gb micro SD... it booted! :laugh:
I was able to get into the phone and follow the guide to move the debricked bootloader over to the internal storage (phone would then boot without SD card). After that I used ODIN and got it to load a stock 4.1.1 image to the phone. Phone is up and running but IMEI is '0' and serial is wrong so 4g is not working... Trying to figure out how to fix this now.
I'll try to post the links I used here shortly to help others out.

Congratulations on getting it to work.
What is the bootloader on your phone? The imei is probably 0 because your bootloader is not compatible with your modem.

audit13 said:
Congratulations on getting it to work.
What is the bootloader on your phone? The imei is probably 0 because your bootloader is not compatible with your modem.
Click to expand...
Click to collapse
Is there any easy way to check which boot loader i'm using?
In case this helps, here is what I did last night to get my phone going again:
I followed these instructions
http://forum.xda-developers.com/showthread.php?t=2660566
(grabbing the AT&T unbrick image here https://drive.google.com/folderview?id=0B612qYHFMILfWUlMTTEwdUstcXM&usp=sharing )
That got me back up and running into Cyanogenmod (I believe version 4.4?) From there I continued on with the steps
"Restoring stock bootloader
1) You were able to boot into the ROM
2) Plug your phone into a computer and use MTP mode
3) Move the debrick file onto your internal sdcard (/sdcard/debrick.bin)
4) Disconnect your phone
5) Open up a Terminal Emulator on your phone and input this code
Code:
su
dd if=/sdcard/debrick.bin of=/dev/block/mmcblk0
Click to expand...
Click to collapse
I then flashed I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 with Odin.
I've tried a few little quick things i've read about typing in a *# number to get into service mode but that didn't change anything or fix IMEI. I also just rooted it (a few walkthroughs I was starting to look into required a rooted phone.
I also read a few times that people said to just flash the stock rom/modem onto the phone again? I'm just being very cautious this time around :silly:

Install terminal emulator and type this in: "getprop ro.bootloader" without the quotes but with the spaces. Press enter and let us know what it says on the screen.
The LK3 firmware is 4.1.1. What is the baseband on your phone? If your baseband is LK3 and your bootloader is MJB, this may be why you have no imei.

audit13 said:
install terminal emulator and type this in: "getprop ro.bootloader" without the quotes but with the spaces. Press enter and let us know what it says on the screen.
The lk3 firmware is 4.1.1. What is the baseband on your phone? If your baseband is lk3 and your bootloader is mjb, this may be why you have no imei.
Click to expand...
Click to collapse
i747ucdlk3

79TAKid said:
i747ucdlk3
Click to expand...
Click to collapse
SO your phone now boots from internal storage and the bootloader is LK3. What is the baseband?

audit13 said:
SO your phone now boots from internal storage and the bootloader is LK3. What is the baseband?
Click to expand...
Click to collapse
Sorry yes, after I used the command to copy the bootloader over from the debrick file, I was then able to use the phone without a SD card from that point on.
Baseband says I747UCDLK3 as well..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Weird that you have no IMEI when you bootloader matches your modem.
If you still have Philz on your phone, create a nandroid backup and try a custom ROM to see if anything changes.
If nothing changes, you may need to use nvwriter to inject the imei.
http://forum.xda-developers.com/showthread.php?t=1804117

audit13 said:
Weird that you have no IMEI when you bootloader matches your modem.
If you still have Philz on your phone, create a nandroid backup and try a custom ROM to see if anything changes.
If nothing changes, you may need to use nvwriter to inject the imei.
http://forum.xda-developers.com/showthread.php?t=1804117
Click to expand...
Click to collapse
Thanks for the advice, I will try this when I get time (at work right now). I've never used Philz, had to look up what it was! I've always used CWM. Would you recommend I use Philz? I will get a backup before I do anything else and reply back.

Philz is based on CWM but with a few advanced features. Either version should do the job.

[Q] Need help fixing my Gnex

Hi,
it is the second time my Gnex went into endless reboot loop sessions.
It will boot, load crash after few seconds and reboot again.
I had it unlocked in the store i bought it, and had stock rom (Not sure about the version).
Tried to do factory reset from fastboot, from recovery, and from android. Also tried to flash custom boot loader, Nothing works.
Although fastboot writes it successfuly completed the action so does the factory reset. The phone will work for few seconds but no more.
Also tried using WugFresh, for factory reset and for Flash Stock + unroot in soft-break status
I have no ideas what to do next,
Please help.
Mike

Hi Mike, I think more information is required.
- What action did you take immediately prior to having your phone get stuck in the bootloop? Were you trying to install a Custom Recovery or ROM?
- You mention that this is the second time this has happened. Do you know what caused it to bootloop the first time, and if yes what fixed it?
- When your Gnex is in Fastboot/Bootloader mode, and using a tool like Minimal ADB and Fastboot on your computer, does the tool recognize the Device ID after using the fastboot devices command?
You may also want to read through this thread.

AvidPhisherman said:
Hi Mike, I think more information is required.
- What action did you take immediately prior to having your phone get stuck in the bootloop? Were you trying to install a Custom Recovery or ROM?
- You mention that this is the second time this has happened. Do you know what caused it to bootloop the first time, and if yes what fixed it?
- When your Gnex is in Fastboot/Bootloader mode, and using a tool like Minimal ADB and Fastboot on your computer, does the tool recognize the Device ID after using the fastboot devices command?
You may also want to read through this thread.
Click to expand...
Click to collapse
Hi thanks for the reply, i am a simple user, prior to the bootloop i was using whatsapp, actually the android crashes few seconds after getting a whatsaap message (i recieve notification and it goes down). Previous time also i didn't do anything special. i never installed custom recovery or roms... previous time it was fixed by a lab the phone was on warranty.
And yes the tool recognize the device.

So your device receives a WhatsApp message/notification, restarts, and then gets stuck in a bootloop?
That is very strange, as personally I've only ever encountered bootloops after bad ROM flashes (usually after I accidentally skipped a step somewhere during the process). Bootloops usually don't happen to regular users who are just using their phone purchased as-is from a store/carrier.
If you can get it to boot back into Android, try uninstalling WhatsApp and see if that helps. Hopefully it's still under warranty, as you may have to take it back to the store and have them look at it.

AvidPhisherman said:
So your device receives a WhatsApp message/notification, restarts, and then gets stuck in a bootloop?
That is very strange, as personally I've only ever encountered bootloops after bad ROM flashes (usually after I accidentally skipped a step somewhere during the process). Bootloops usually don't happen to regular users who are just using their phone purchased as-is from a store/carrier.
If you can get it to boot back into Android, try uninstalling WhatsApp and see if that helps. Hopefully it's still under warranty, as you may have to take it back to the store and have them look at it.
Click to expand...
Click to collapse
Tried to uninstall whatsapp but it crashes before i manage to do so.
even managed to access memory via TWRP and delete whatsaap manually but somehow it appears again after restart.
Something is terribly wrong

Have you tried using Odin to repartition and restore to stock? Could be a corrupted partition. Check out this guide

nthnlee said:
Have you tried using Odin to repartition and restore to stock? Could be a corrupted partition. Check out this guide
Click to expand...
Click to collapse
Why???
Just use fastboot, Odin is evil. Nexus aren't Touchwiz crap phones.

beekay201 said:
Why???
Just use fastboot, Odin is evil. Nexus aren't Touchwiz crap phones.
Click to expand...
Click to collapse
When fastboot didn't work. i had to try something else. But, odin didn't work either.

mishkap said:
When fastboot didn't work. i had to try something else. But, odin didn't work either.
Click to expand...
Click to collapse
Let's see then. Be prepared to spend at least 30min reading, and re-reading, until you actually feel comfortable in what you're doing/typing in. If you're not sure about the technical terms and what lies behind them, read this thread's #1 First Post.
What's your device variant? maguro? toro? toroplus? This will tell which factory image you need to flash.
You need to flash latest factory image, which is (for maguro variant) Android Build 4.3 (JWR66Y). Read #1 First Post on this thread. And I mean, READ IT! Do not do anything else to your device until you do.
After you flash the factory image, that first boot will take a while to reach Android. Chill out. Go get yourself a drink. Take your time. It should have booted into Android already when you get back. It should be fine, but if not, you need to enable USB debugging under Settings > Developer Options, to check the system log.
If after 15min, it still has booted yet, pull the battery out, wait a few secs, put it back in.
Use the 3bc (3-button combo) to reach fastboot mode again. Flash a custom recovery. That's done by downloading the latest TWRP or CWM (i'll leave that choice up to you, be mindful that you might wanna try them both in the future), and running on the host (the PC):
Code:
fastboot flash recovery recovery_filename_here.img
Don't reboot the device. Use the volume keys to "Reboot to recovery" straight from fastboot. After a few seconds, you should be seeing the custom recovery you've flashed with the fastboot command above.
Now comes the part where ADB is required. I hope you've already read the answers to questions "Where do I get the driver for my PC?" and "Why do I need to install the driver twice?". If not, read them now. Also, read "What is ADB?". TIP: When a custom recovery is actually running on the device, ADB mode is already active by default, so when hooking up to the pc the device will show as an ADB interface, so installing the driver (if needed/not done yet) is piece of cake.
After you get ADB to recognize your device (like, you see your device's SN on the output of command `adb devices`).. You need to copy a custom ROM to your device, and flash it. That will get you, most likely than not, Android's USB debugging by default (read answer to "What is an insecure boot image?" on the first link), and that will allow you to see the system log, WHILE Android is booting up. Why do we wanna do this? Cos we want to see if any errors show up, something that may tell us what's failing.
When choosing a ROM from the Android Development section, ask around in the thread if the ROM has USB debugging enabled by default.
Read "What are the ADB commands?" in the thread I first linked to. You'll need to learn at least `adb push` for now.
Once you get the ROM in your /sdcard/ or whatever folder you like, disconnect the USB cable, wipe data/factory reset, then install zip from sdcard (that zip you pushed before).. Forget about gapps for now.
Connect the usb cable, reboot, and once you see padlock screen go away, start trying to run `adb devices`. Do you see your SN in the output? Once you see it, good, it already connected to adb on the device. Run `adb logcat` and try to look out for errors. Logcat is the system log.
To know how to grab that output to a text file so that you can share it with us.. Google it, my fingers hurt.

Thanks beekay201,
As a matter a fact. shortly before you posted this answer i gave up and gave my phone to a local lab.
But unfortunately they were useless and didn't manage to do anything claiming they don't have spares for my phone, tried to explain that it is not a hardware issue, but all in vain .
Anyway, ill go over your instructions and ill update the results soon.

Bricked 5T - locked recovery

Hi im having a hard time figuring this out, this is a brand new 5t that bricked itself while ota updating
the device is in a boot loop (wont go any further than the oneplus logo)
if i enter to the recovery it says LOCKED, and the oem unlock option on android is not enabled
im in argentina so i cant send the phone to oneplus rma
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is there any way to unlock the bootloader? then i would be able to flash it and save the phone
Ps: a level 2 OnePlus tech guy tried a remote fix with the official brand software and it did not work

https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Hope that helps. If you can get it to load in that mode, it'll fix about anything.

es0tericcha0s said:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Hope that helps. If you can get it to load in that mode, it'll fix about anything.
Click to expand...
Click to collapse
Thanks a lot! i think that oneplus did use that file and did not work but i will try it again (at least 10 times)

I think it might be tricky to get it into the QHUSB mode unless it's hard bricked. I've fixed a 3t like that but luckily haven't had issues on the 5t yet. I think the only way might be via test point (which would require some hardware work that's not recommended for beginners). Thinking about it now, this might not have been the best solution to provide for your particular issue.
Just thought about this after re-reading your post. When you say that you booted into Recovery and it says locked but you posted a picture of the Fastboot screen showing just that the bootloader is locked - which is to be expected unless you went through the bootloader unlock process.
What happens when you actually boot to recovery? Have you tried factory resetting it there? I imagine the remote desk guy might have tried to adb sideload the update?

This is why I wish we had a fastboot OEM image install option like Google provides.
Maybe we do though and I just haven't found it yet.
Haven't looked very hard.

es0tericcha0s said:
I think it might be tricky to get it into the QHUSB mode unless it's hard bricked. I've fixed a 3t like that but luckily haven't had issues on the 5t yet. I think the only way might be via test point (which would require some hardware work that's not recommended for beginners). Thinking about it now, this might not have been the best solution to provide for your particular issue.
Just thought about this after re-reading your post. When you say that you booted into Recovery and it says locked but you posted a picture of the Fastboot screen showing just that the bootloader is locked - which is to be expected unless you went through the bootloader unlock process.
What happens when you actually boot to recovery? Have you tried factory resetting it there? I imagine the remote desk guy might have tried to adb sideload the update?
Click to expand...
Click to collapse
if i boot to recovery and press the power button to select factory reset or any usefull option, the phone resets, i think that the problem is a corrupt recovery, thats why i want to unlock it, install TWRP and then try to flash android

CZ Eddie said:
This is why I wish we had a fastboot OEM image install option like Google provides.
Maybe we do though and I just haven't found it yet.
Haven't looked very hard.
Click to expand...
Click to collapse
maybe this is an anti thief security measure? (since android 6.0 )

es0tericcha0s said:
I think it might be tricky to get it into the QHUSB mode unless it's hard bricked. I've fixed a 3t like that but luckily haven't had issues on the 5t yet. I think the only way might be via test point (which would require some hardware work that's not recommended for beginners). Thinking about it now, this might not have been the best solution to provide for your particular issue.
Just thought about this after re-reading your post. When you say that you booted into Recovery and it says locked but you posted a picture of the Fastboot screen showing just that the bootloader is locked - which is to be expected unless you went through the bootloader unlock process.
What happens when you actually boot to recovery? Have you tried factory resetting it there? I imagine the remote desk guy might have tried to adb sideload the update?
Click to expand...
Click to collapse
why would i have a problem putting the 5t on qhusb? i did not know that it could be done via testpoint
the phone works, the problem seems to be a faulty file on the bootloader or maybe an internal damage from factory (i hope this is not the case)
in a few hours i will try it all and post the result

Typically a phone will only go into the Qualcomm QHUSB mode when it's hard bricked. You're only soft bricked. What happens when you actually get into Recovery?

es0tericcha0s said:
Typically a phone will only go into the Qualcomm QHUSB mode when it's hard bricked. You're only soft bricked. What happens when you actually get into Recovery?
Click to expand...
Click to collapse
I did the entire process and the result is the same as before doing it, the phone turns on and gets stuck on the oneplus logo, it does nothing else, the recovery works but doesnt do anything usefull

Do you get any errors when performing a factory reset? As in a partition not mounting? Since your baseband doesn't show in the fastboot mode, I'm thinking maybe an /efs error. If you got it new, I'd talk to 1+ about an RMA since this was caused by an official update and one of their technicians already failed to fix it.

es0tericcha0s said:
Do you get any errors when performing a factory reset? As in a partition not mounting? Since your baseband doesn't show in the fastboot mode, I'm thinking maybe an /efs error. If you got it new, I'd talk to 1+ about an RMA since this was caused by an official update and one of their technicians already failed to fix it.
Click to expand...
Click to collapse
It may well be a partition error, one+ is not being helpfull right now
I did comit an error saying that the recovery works, it doesnt work, the pone only goes into fastboot and qhusb mode, after that it will allways get stuck on the oneplus logo
On adb i get feedback if i try to flash the phone says "not allowed, locked device"
I think that the problem is a corrupt bootloader
The msmdownloader tool works, i dont know what It copies on to the terminal but i want to flash the recovery and bootloader using that tool, i dont know if it is possible

this the md5sum file that i found in a compilation for oneplusone (msmdownloader tool)
so i shoud be able to do the same with the 5t

es0tericcha0s said:
Typically a phone will only go into the Qualcomm QHUSB mode when it's hard bricked. You're only soft bricked. What happens when you actually get into Recovery?
Click to expand...
Click to collapse
that is no true, u just have the phone powered off and then hold the volume + and plug the device in, if u saw the video in the unbrick post he was not bricked at all and everything was working good and still did a restore, not sure why it is not working for the OP but it should fix it.

Yes i can enter into qhusb, and i can flash the phone with msm downloader, but i used the origibal file that oneplus technicians use amd it didnt work, now i want to flash hydrogen os or the recovery file only into the terminal but i dont know how to modify the msm downloader (the unbrick tool)

Had the same error message tonight after spontaneous reboot of my (unmodified and locked) device. Fortunately, reimaging with stock ROM from downloads.oneplus.net via adb sideload worked for me, without losing any data. Tried that?

sascha224 said:
Had the same error message tonight after spontaneous reboot of my (unmodified and locked) device. Fortunately, reimaging with stock ROM from downloads.oneplus.net via adb sideload worked for me, without losing any data. Tried that?
Click to expand...
Click to collapse
I remember that the device wouldnt flash anything because it was locked, but I will try the sideload right away

It has been impossible to fix, this is the best i got doing fastboot boot recovery.img

AT&T Galaxy s3 won't boot to Android

Okay not sure how many people still frequent this forum, but hopefully someone can help. So yesterday my phone was charging up and I decided to reboot it because it was time for a weekly reboot. So I held the power button and selected reboot to reboot it. It shut down then started to boot, the samsung logo appeared then disappeared followed by the galaxy s3 logo.
After that it just shut off. When I tried to turn it on again, all it did was vibrate vibrant and vibrant in a loop every time I pushed the power button. Finally I decided to try recovery mode (stock recovery) and wipe cache...no dice. So I tried download mode and that came up fine. I rebooted out of download mode and plugged the phone in. The charge animation came up as well as the LED red charge light. I let it charge for a few hours then unplugged it, removed the battery for a minute and put it back in and tried to turn it on. I even tried a different/another battery and got the same result.
All it did was the vibrate loop sequence again i mentioned above. I don't want to loose all my stuff I have on it. I heard dirty flashing in ODIN will wipe your data. I'm not sure if the debrick image is for Android 4.4.2 because that's what I'm on. Does anyone know how to fix this or have had similar issues and got it working again?

StoneyJSG said:
Okay not sure how many people still frequent this forum, but hopefully someone can help. So yesterday my phone was charging up and I decided to reboot it because it was time for a weekly reboot. So I held the power button and selected reboot to reboot it. It shut down then started to boot, the samsung logo appeared then disappeared followed by the galaxy s3 logo.
After that it just shut off. When I tried to turn it on again, all it did was vibrate vibrant and vibrant in a loop every time I pushed the power button. Finally I decided to try recovery mode (stock recovery) and wipe cache...no dice. So I tried download mode and that came up fine. I rebooted out of download mode and plugged the phone in. The charge animation came up as well as the LED red charge light. I let it charge for a few hours then unplugged it, removed the battery for a minute and put it back in and tried to turn it on. I even tried a different/another battery and got the same result.
All it did was the vibrate loop sequence again i mentioned above. I don't want to loose all my stuff I have on it. I heard dirty flashing in ODIN will wipe your data. I'm not sure if the debrick image is for Android 4.4.2 because that's what I'm on. Does anyone know how to fix this or have had similar issues and got it working again?
Click to expand...
Click to collapse
You could try reflashing system and boot partition.

iloveoreos said:
You could try reflashing system and boot partition.
Click to expand...
Click to collapse
Is this done in ODIN? Will it wipe all my data? I'm trying to avoid anything like a data factory reset as I want to recover my stuff that wasn't saved to my SD card.

StoneyJSG said:
Is this done in ODIN? Will it wipe all my data? I'm trying to avoid anything like a data factory reset as I want to recover my stuff that wasn't saved to my SD card.
Click to expand...
Click to collapse
I don't know why it would, but I have never tried it on a Samsung. Flashing something like TWRP doesn't erase data when you flash it.

Which ROM is currently on the phone?
AT&T never released a stock ROM for the sgh-i747 after 4.1.1 or 4.1.2. All system updates were pushed to the phone via OTA; therefore, you can't re-flash the ROM using Odin unless you use a file that was specfically create for Odin.

audit13 said:
Which ROM is currently on the phone?
AT&T never released a stock ROM for the sgh-i747 after 4.1.1 or 4.1.2. All system updates were pushed to the phone via OTA; therefore, you can't re-flash the ROM using Odin unless you use a file that was specfically create for Odin.
Click to expand...
Click to collapse
Would the one for sgh i747m work if you just flashed system and boot? You can get that in 4.4.2.

Before flashing anything, I recommend booting into download mode and confirm the the model is SGH-i747 and whether there is a line that makes reference to Knox or warranty bit.
If it is the sgh-i747 and there is reference to warranty bit, you should look at the possibility of flashing a ROM from here: https://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If it is an sgh-i747 with no reference to warranty bit, this means the phone is not running a 4.3 or newer bootloader.

​
audit13 said:
Before flashing anything, I recommend booting into download mode and confirm the the model is SGH-i747 and whether there is a line that makes reference to Knox or warranty bit.
If it is the sgh-i747 and there is reference to warranty bit, you should look at the possibility of flashing a ROM from here: https://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If it is an sgh-i747 with no reference to warranty bit, this means the phone is not running a 4.3 or newer bootloader.
Click to expand...
Click to collapse
It is on Android 4.4.2 with bootloader NE4. It's the sgh-i747 AT&T variant. My warranty bit is 0. I can boot into download mode and stock recovery fine, just it won't boot into Android. I read somewhere that it might be an IC chip or emmc issue?
Someone took the NE4 OTA and made some ODIN files out of it so I downloaded them. I just want to be able to recover my files from the internal storage so I haven't flashed anything yet.

Glad you are on top of things.
Flashing the same ROM should be fine and it does not normally wipe your data. That being said, there is always a chance that flashing will result in data loss.
If it is an errant app that is causing the issue, you may have no choice but to wipe the data.

Ah ok, that's a bummer. Well I guess I will try flashing the same ROM over it and see what happens. Hopefully my data and apps stay in tact. I thought it might be a chip on the logic board so I took it to a repair shop over the weekend. Now to get it back from them and try flashing the ROM over the ROM.

audit13 said:
Glad you are on top of things.
Flashing the same ROM should be fine and it does not normally wipe your data. That being said, there is always a chance that flashing will result in data loss.
If it is an errant app that is causing the issue, you may have no choice but to wipe the data.
Click to expand...
Click to collapse
Just an update. I managed to fix my phone with Odin. I flashed the NE4 kit kat BL, AP, CSC, and CP files. It did wipe everything and put it back to factory stock like a factor data reset would do, so I lost all my files and apps.

Sorry to hear that the data was wiped.
Thanks for the update.

CrDroid O/S works good on my old Samsung Galaxy S3 i747
audit13 said:
Before flashing anything, I recommend booting into download mode and confirm the the model is SGH-i747 and whether there is a line that makes reference to Knox or warranty bit.
If it is the sgh-i747 and there is reference to warranty bit, you should look at the possibility of flashing a ROM from here: https://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If it is an sgh-i747 with no reference to warranty bit, this means the phone is not running a 4.3 or newer bootloader.
Click to expand...
Click to collapse
Firstly, I am a newbie. I don't understand about this "warranty bit" . The Samsung S3 i747 is a very old phone ( hence no warranty after 8+ years ). Please explain !
---------- Post added at 04:46 PM ---------- Previous post was at 04:37 PM ----------
StoneyJSG said:
Okay not sure how many people still frequent this forum, but hopefully someone can help. So yesterday my phone was charging up and I decided to reboot it because it was time for a weekly reboot. So I held the power button and selected reboot to reboot it. It shut down then started to boot, the samsung logo appeared then disappeared followed by the galaxy s3 logo.
After that it just shut off. When I tried to turn it on again, all it did was vibrate vibrant and vibrant in a loop every time I pushed the power button. Finally I decided to try recovery mode (stock recovery) and wipe cache...no dice. So I tried download mode and that came up fine. I rebooted out of download mode and plugged the phone in. The charge animation came up as well as the LED red charge light. I let it charge for a few hours then unplugged it, removed the battery for a minute and put it back in and tried to turn it on. I even tried a different/another battery and got the same result.
All it did was the vibrate loop sequence again i mentioned above. I don't want to loose all my stuff I have on it. I heard dirty flashing in ODIN will wipe your data. I'm not sure if the debrick image is for Android 4.4.2 because that's what I'm on. Does anyone know how to fix this or have had similar issues and got it working again?
Click to expand...
Click to collapse
I'm not sure how many of us are out there, tinkering around with the 8+ year old Samsung Galaxy S3 i747 . While I am a newbie, I have enjoyed flashing Custom ROM's , from CyanogenMod, thru various versions of Lineage, and now CRdroid.
You spoke of: " . . . dirty flashing in ODIN . . . "
I have always used ODIN to INSTALL a 'recovery' system such as TWRP ( which is a .Tar file )
After TWRP is installed ( using ODIN ) I unplug phone from my computer. Then boot into TWRP recovery ( holding down the three buttons ). I do a clean install (flash) of the newest O/S that I can find ( Android 4.4 is really old ). It is that .Zip file that I flash, then reboot the phone. Always works for me.
Eventually I learned how to back up all my contacts, SMS, logs, photos, etc.
BTW I am totally free of Google; no Google Play Store, no Google Pay, no Google Framework, no Gapps, no Google spyware, no Google bloatware, no Google tracking etc.
I download all my apps as APK's which are readily available on the Net ( Google them . . . just kidding! ).
My older Samsung S3 i747 was a 'd2att' originally locked to Rogers, in Ottawa, Ontario, Canada. Then switched over to MTS (Manitoba Telephone System). Now running on Bell Canada. My replacement is also a Samsung S3 i747, originally running T-Mobile in Arizona, now running on Bell Canada.
These are damn fine phones.

DavidWCS said:
Firstly, I am a newbie. I don't understand about this "warranty bit" . The Samsung S3 i747 is a very old phone ( hence no warranty after 8+ years ). Please explain !.
Click to expand...
Click to collapse
Do you see anything in the download mode screen that has the term "warranty bit"?
Is the phone model in download mode screen shown as an sgh-i747 or sgh-747m?

audit13 said:
Do you see anything in the download mode screen that has the term "warranty bit"?
Is the phone model in download mode screen shown as an sgh-i747 or sgh-747m?
Click to expand...
Click to collapse
Curious, I rebooted my phone into download mode ( holding volume down in the 3 finger format ).
There is nothing in the download mode screen that has the term "warranty bit". Just the WARNING !! A custom OS can cause critical problems . . .
There is no phone model in download mode screen shown as an sgh-i747 or sgh-747m
Sorry, but I still don't understand the importance of warranty in an 8+ year old phone. Am I still missing something?

DavidWCS said:
Curious, I rebooted my phone into download mode ( holding volume down in the 3 finger format ).
There is nothing in the download mode screen that has the term "warranty bit". Just the WARNING !! A custom OS can cause critical problems . . .
There is no phone model in download mode screen shown as an sgh-i747 or sgh-747m
Sorry, but I still don't understand the importance of warranty in an 8+ year old phone. Am I still missing something?
Click to expand...
Click to collapse
You are not in download mode.
The warranty bit term is not about warranty, it is about whether the phone has a locked bootloader.

audit13 said:
You are not in download mode.
The warranty bit term is not about warranty, it is about whether the phone has a locked bootloader.
Click to expand...
Click to collapse
OK, I tried it again. This time I went one step further. Aha! Tiny print on upper left of screen. Have attached a sample photo showing what I see. And yes, I can see what you mean: " Warranty Bit: 1 " . Thank you, it makes sense now.
.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

DavidWCS said:
OK, I tried it again. This time I went one step further. Aha! Tiny print on upper left of screen. Have attached a sample photo showing what I see. And yes, I can see what you mean: " Warranty Bit: 1 " . Thank you, it makes sense now.
.View attachment 4991379
Click to expand...
Click to collapse
The phone is not an AT&T S3, it is a T-Mobile s3 sgh-t999?

audit13 said:
The phone is not an AT&T S3, it is a T-Mobile s3 sgh-t999?
Click to expand...
Click to collapse
There are 2 i747 phones; d2Can & T999. In the past, the O/S's that I flashed, were designed for d2att. No difference in how they functioned, as far that I could notice.

DavidWCS said:
There are 2 i747 phones; d2Can & T999. In the past, the O/S's that I flashed, were designed for d2att. No difference in how they functioned, as far that I could notice.
Click to expand...
Click to collapse
Yes, there are two models of the i747: sgh-i747 (AT&T, d2att) and sgh-i747m (non-AT&T, d2can)
The T-Mobile s3 is sgh-t999 (d2tmo).