Related
How can I flash the Stock Recovery ROM for my Desire Z?
Basically, I want to remove what ClockWorkMod did. Even when I turned Fast Boot off, turned off the phone, it wouldn't, and will startup ClockWorkMod instead. That said, I can't boot into HBOOT at all since wanting to go into HBOOT means I'm required to turn the phone off completely first.
I'm also having trouble finding my shipped ROM (1.34.707.5), and from the other threads I read, it seemed like a bad idea to grab other DZ ROMs and try flashing it.
Can anyone help/guide me with this? Thanks!
Edit: Prior to this, I was trying to overclock my DZ using this guide for noobs http: //androidforums.com/desire-z-all-things-root/233729-ultimate-guide-rooting-overclocking-your-bell-desire-z-newb-friendly.html. I followed every step, inclusive of the backup.
Kudos to Blue1k for the guide and gtrab for the amazing overclock script
Code:
adb reboot bootloader
will get you into fastboot usb.
Hm,fastboot at settings menu deactivated.
Turned phone off,then holding trackpad down and turning phone
on works for me!
Thanks keinengel for the tip!
@Ganli I can't turn phone off using the menu (and with Fast Boot turned off). I tried removing the battery and I got into HBOOT successfully.
That said, I didn't like the way ClockWorkMod disabled my turning off phone (I do appreciate the backup features it provided). Is there anyway I could restore the original recovery back?
n3ph said:
That said, I didn't like the way ClockWorkMod disabled my turning off phone (I do appreciate the backup features it provided). Is there anyway I could restore the original recovery back?
Click to expand...
Click to collapse
There's a known issue with ClockworkMod where, when you have your phone turned off and you plug in the charger, it automatically then starts up in Clockwork. Is this what you're seeing ? Because if not, that sounds very odd (Clockwork disabling turning off your phone ).
You can flash a new recovery from fastboot, if you have the eng hboot installed. I presume you can take the recovery.img file from one of the stock ROMs, then do "fastboot flash recovery recovery.img".
steviewevie said:
There's a known issue with ClockworkMod where, when you have your phone turned off and you plug in the charger, it automatically then starts up in Clockwork. Is this what you're seeing ? Because if not, that sounds very odd (Clockwork disabling turning off your phone ).
You can flash a new recovery from fastboot, if you have the eng hboot installed. I presume you can take the recovery.img file from one of the stock ROMs, then do "fastboot flash recovery recovery.img".
Click to expand...
Click to collapse
Bingo. It turned off completely when I non-fast boot powered it down without the charger plugged in!
I would like to flash the original recovery like what you mentioned. I am afraid of hardware incompatibilities as mine has a different software version than the ones I've seen here. I wonder if I could use them. (By the way, I haven't seen any recovery.img around, only PC10IMGs)
n3ph said:
I would like to flash the original recovery like what you mentioned. I am afraid of hardware incompatibilities as mine has a different software version than the ones I've seen here. I wonder if I could use them. (By the way, I haven't seen any recovery.img around, only PC10IMGs)
Click to expand...
Click to collapse
The PC10IMG is a zip file containing various stuff to make up a ROM, mainly these are partition images. One of them is recovery.img. So you can get recovery.img from one of those ROM images.
What ROM are you running exactly ?
Stock ROM. Probably one of the Asian version.
Baseband
12.28b.60.140eU_26.03.02.02_M
Kernel
2.6.32.21-gd2764ed
[email protected] #1
Tue Oct 26 16:04:03 CST 2010
Build number
1.34.707.5 CL273326 release-keys
Software
1.34.707.5
I haven't seen any ROM with this version on XDA yet. I saw about the RUU in other threads. Will I be able to select flashing only the recovery from RUU? Or is it a full flash only?
n3ph said:
I haven't seen any ROM with this version on XDA yet. I saw about the RUU in other threads. Will I be able to select flashing only the recovery from RUU? Or is it a full flash only?
Click to expand...
Click to collapse
I have never tried the RUU. At a complete guess I would think it is only a full flash.
You can run the RUU then leave it at the first screen, then open up another window and find where Windows has put the temp files it has extracted from the RUU. Amongst those will be the ROM image, which you can open up (it's a zip file) and find the "recovery.img" file, which you can flash via fastboot if you have the eng hboot installed.
Understood. One more question, my HBOOT is stock. Not sure if this is different from "eng hboot" By Fastboot, you meant this program http: //forum.xda-developers.com/showthread.php?t=463627 right?
Im confused here and just thinking out loud for myself but maybe to provoke some logic here --
without clockworkmod you are unable to flash any roms. you must have clockworkmod to tinker with your phone. no clockworkmod = unroot, or semi root psuedo root whatever.
the only way people can flash stuff is with clockworkmod. its the only recovery available at this time.
if i am missing something or being redundant, my sincere regards.
??
n3ph said:
Understood. One more question, my HBOOT is stock. Not sure if this is different from "eng hboot" By Fastboot, you meant this program http: //forum.xda-developers.com/showthread.php?t=463627 right?
Click to expand...
Click to collapse
You can tell which hboot you have if you shut down the phone (fully, not HTC's confusingly-named "fast boot" mode, which is a sleep state) and then hold Volume down and then hold Power till it turns on.
If it says "SHIP" on the first line, it is the stock hboot. The engineering hboot says "ENG". The eng hboot gives you more options.
No need to install that program, if you go through the steps in my adb guide to setup adb via the SDK, you will have fastboot too.
androidcues said:
without clockworkmod you are unable to flash any roms. you must have clockworkmod to tinker with your phone. no clockworkmod = unroot, or semi root psuedo root whatever.
the only way people can flash stuff is with clockworkmod. its the only recovery available at this time.
Click to expand...
Click to collapse
Yes, the only recovery options we have at the moment are stock recovery or ClockworkMod recovery (installed from ROM Manager). Maybe we will get some more custom recoveries in the future, who knows ?
But you don't need ClockworkMod to flash a ROM. You can flash stock ROMs on a stock phone, though only ones designed specifically for your sub-model of phone (e.g. European ROMs if it's a European phone, T-Mobile ROMs if it's a G2, etc, etc).
If you get S-OFF then you can flash custom ROMs to your phone, or stock ROMs from a different stock Vision (e.g. flashing a stock European ROM onto an Asian DZ).
ClockworkMod is very very useful for letting you do a full backup (nandroid backup) of your ROM.
You can also flash other ways, e.g. flashing from your SD card via hboot, or if you have the eng hboot installed then you can use the fastboot mode/utility to flash too.
thank you i stand corrected.
Thanks for the help. After researching more on what you said, I have a better idea on the flashing process =)
I'll try to reserch more while waiting for a compatible ROM for my phone before trying anything again (in case I brick it)
n3ph said:
Thanks for the help. After researching more on what you said, I have a better idea on the flashing process =)
I'll try to reserch more while waiting for a compatible ROM for my phone before trying anything again (in case I brick it)
Click to expand...
Click to collapse
I'd like to know if anyone was able to make a copy of the stock ROM or has found the RUU for this specific version.
Hi!
I bought a Desire HD a week ago and today I decided to try one of the custom roms. I rooted it with Visionary+, turned s-off with the one-click tool found in another thread, installed Rom Manager and Clockwork mod and then flashed it with a custom rom from the recovery/boot screen without wiping anything.
The problem is, when I later tried to install another rom, it wouldn't boot, it's stuck on the HTC boot screen. I've tried reflashing it, wiping everything there is to wipe and I even tried RUU but it won't recognize the phone. Can anyone help me how to restore to the normal stock rom?! I can bring up the Clockworkmod recovery menu if I take out the battery and put it back in.
I would be very grateful if someone could help me with this! Consider that I'm a noob though so try to write the instructions as simply as possible
Hi, I'm basically in the same boat (I take it you tried one of the stable CM6 builds?).
Digged through an awful lot of stuff, found something about downgrading clockwork.
Maybe this'll help you, I'm still having trouble.
I've found an older clockwork recovery image, gathered all the SDK bits and pieces, got my USB drivers set up after even more digging - now this:
D:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
It's rooted, S-OFF, all that good jazz. Halp. :<
enectrixx said:
Hi!
I bought a Desire HD a week ago and today I decided to try one of the custom roms. I rooted it with Visionary+, turned s-off with the one-click tool found in another thread, installed Rom Manager and Clockwork mod and then flashed it with a custom rom from the recovery/boot screen without wiping anything.
The problem is, when I later tried to install another rom, it wouldn't boot, it's stuck on the HTC boot screen. I've tried reflashing it, wiping everything there is to wipe and I even tried RUU but it won't recognize the phone. Can anyone help me how to restore to the normal stock rom?! I can bring up the Clockworkmod recovery menu if I take out the battery and put it back in.
I would be very grateful if someone could help me with this! Consider that I'm a noob though so try to write the instructions as simply as possible
Click to expand...
Click to collapse
Which version clockwork mod are you using? And what is the ROM you tried to flash?
Sometimes custom ROMs can take 5 minutes to boot...so give it some more time and see if that helps.
Headwoünd said:
Hi, I'm basically in the same boat.
Digged through an awful lot of stuff, found something about downgrading clockwork.
Maybe this'll help you, I'm still having trouble.
I've found an older clockwork recovery image, gathered all the SDK bits and pieces, got my USB drivers set up after even more digging - now this:
D:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting--- FAILED (remote: not allowed)
It's rooted, S-OFF, all that good jazz. Halp. :<
Click to expand...
Click to collapse
seems like your pc is not recognizing your phone. And should not you flash the recovery first and then boot?
I did flash the recovery via Rom Manager, which gave me Clockwork Recovery version 3.0.0.5.
Then I had Rom Manager download CM6, it rebooted the phone, phone gets stuck in HTC splash screen.
According to the thread I linked above, I needed to downgrade Clockwork Recovery, hence flashing 2.5.x.x via command prompt.
The drivers are installed correctly, I'm at least sure of that.
Recovering my previously backed up stock ROM won't get me further than the splash screen either, same with wiping everything that can be wiped before that.
Headwoünd said:
I did flash the recovery via Rom Manager, which gave me Clockwork Recovery version 3.0.0.5.
Then I had Rom Manager download CM6, it rebooted the phone, phone gets stuck in HTC splash screen.
According to the thread I linked above, I needed to downgrade Clockwork Recovery, hence flashing 2.5.x.x via command prompt.
The drivers are installed correctly, I'm at least sure of that.
Recovering my previously backed up stock ROM won't get me further than the splash screen either, same with wiping everything that can be wiped before that.
Click to expand...
Click to collapse
Then use ROM manager to downgrade the CWM to 2.x. You can do it under the option "All recoveries" in ROM manager. People are reporting problems with the latest version of CWM. Check if you get the same if you wipe everything and install another custom ROM.
Can't find a way to even get past the first splash screen - only thing I can properly access is the Bootloader.
Same here. When I boot I just see the initial "HTC" logo, nothing else.
I had Mike's Revolution HD ROM installed and working just fine, and then I tried to install another mod, which got me to this situation.
I have CWM 3.0.0.5 and I have a nandroid backup of the working system from before installing the last mod.
I tried recovering the nandroid, which goes smoothly (including the MD5 validation of the backup) but it still doesn't boot afterwards. I wiped the boot, system and data partitions and tried restoring again - same result.
I assume my next step is to flash a new ROM but unfortunately I don't have any ROMs on my SDCARD, so I need a way to push it there. I tried with fastboot but it doesn't recognize a partition called "sdcard". I believe adb should work while I'm in CWM but it just says "error: device not found".
Any suggestions?
sphuyal said:
Which version clockwork mod are you using? And what is the ROM you tried to flash?
Sometimes custom ROMs can take 5 minutes to boot...so give it some more time and see if that helps.
Click to expand...
Click to collapse
Sorry, no idea which version, but it's the default that comes with Rom Manager. I downloaded Rom Manager yesterday so I guess it's the most recent Clockwork mod.
Left it for 15 minutes, still nothing. I used Android Revolution HD 2.0.11 for the first flash which worked and then when I tried to install Pays-ROM HD Sparta 1.0 I got stuck on the boot screen. I've tried recovering from the previous backup I made on the recovery screen with no result.
Just got mine back alive
Flashed CWM 2.5.1.3 and restored the nandroid with it.
Spending the last few hours searching the forums my best advice is to avoid 3.0.0.5
Went a different approach - finally figured out that you could mount the sdcard via Clockwork Recovery, threw newest CM7 nightly on there and installed it with Clockwork as well.
CHRIST that was a pain in the ass... and I thought downgrading the stock ROM was annoying.
as a rule i have found out cwm3 is for flashing gingerbread and cwm2 is for froyo
Headwoünd said:
Went a different approach - finally figured out that you could mount the sdcard via Clockwork Recovery, threw newest CM7 nightly on there and installed it with Clockwork as well.
CHRIST that was a pain in the ass... and I thought downgrading the stock ROM was annoying.
Click to expand...
Click to collapse
Thanks for the advice! It worked for my DHD too Except that I, after flashing ut with CM7, restored it to stock with RUU! Thanks to everyone here who tried to help
erank said:
Just got mine back alive
Flashed CWM 2.5.1.3 and restored the nandroid with it.
Spending the last few hours searching the forums my best advice is to avoid 3.0.0.5
Click to expand...
Click to collapse
how do I get 2.5.1.3 onto the device when I can't even get the darn thing to load?
encrypshun said:
how do I get 2.5.1.3 onto the device when I can't even get the darn thing to load?
Click to expand...
Click to collapse
Read here: http://forum.xda-developers.com/showthread.php?t=855490&page=132 (jump to page 132 #1312)...
Take your battery off, then put it back in. Hold power button and volume down button at the same time. You come to recovery...or alternately you can use adb.
sphuyal said:
Read here: http://forum.xda-developers.com/showthread.php?t=855490&page=132 (jump to page 132 #1312)...
Take your battery off, then put it back in. Hold power button and volume down button at the same time. You come to recovery...or alternately you can use adb.
Click to expand...
Click to collapse
mate you're a STAR. I actually downloaded a recovery image (from post 1315) in the same thread but it kept saying "connecting to device". When I downloaded the recovery image from 1312 and ran "fastboot flash recovery recovery.img" it say's
sending recovery ... OK
writing recover ... OKAY
What do I do next? Just reboot the device?
oh mother looks like I got somewhere. I did a format device and it went into the CWM 2.3.XX screen as below, reloaded Cyanogen 6.1.3 and boom I'm in. Man I though the device was a goner....I'm almost feeling brave enough to install Cyanogen 7.X
encrypshun said:
oh mother looks like I got somewhere. I did a format device and it went into the CWM 2.3.XX screen as below, reloaded Cyanogen 6.1 and boom I'm in. Man I though the device was a goner....
Click to expand...
Click to collapse
So you are happy with your device now?
Well not really, I went back to HTC Sense because Internet Pass Through wasn't available on Cyanogen and now I cannot get the phone to login and create my google account no matter what
Headwoünd said:
Can't find a way to even get past the first splash screen - only thing I can properly access is the Bootloader.
Click to expand...
Click to collapse
the REMOTE NOT ALLOWED error means you only have radio s-off, so you cannot issue fastboot commands to your device.
Sorry if this is a repeat question, but after searching I still can't seem to find a solution (that I can understand anyway.) I relatively new, having only rooted this phone once before, successfully, but a year ago. I've been reading up for the past two days, but I can't seem to find the soft-brick solution to the new Knox problem.
Short history: Rooted 4.2 a while back, but the speakers stopped working (constant headphone mode) so I thought a software update was finally in order. Did the 4.3 update (not knowing about Knox) to see if that fixed the headphone issue (it didn't) then installed TWRP and tried to install the 4.4 OMNI nightly. After install, it hangs on Samsung logo (soft brick?). Restored to backup, but still hangs. Tried installing SlimKat 4.4, but the install fails. Unsure where to go from here.
Phone still powers up, goes into both Download and Recovery mode. TWRP is the current bootloader(?)/recovery(?).
So, is there a simple reason I'm soft-bricked? I read that Knox is in the bootloader, so is it because I'm using TWRP that it hangs? I find it odd that after restoring to previous settings it still doesn't function. Also, I don't care about the warranty bit, so anything is on the table for me.
Much love to those who spend the time to help out, please link to any resources for me and others who have the same problem. I'll append the working solution to this post for quick access in the future!
Ripptor said:
Sorry if this is a repeat question, but after searching I still can't seem to find a solution (that I can understand anyway.) I relatively new, having only rooted this phone once before, successfully, but a year ago. I've been reading up for the past two days, but I can't seem to find the soft-brick solution to the new Knox problem.
Short history: Rooted 4.2 a while back, but the speakers stopped working (constant headphone mode) so I thought a software update was finally in order. Did the 4.3 update (not knowing about Knox) to see if that fixed the headphone issue (it didn't) then installed TWRP and tried to install the 4.4 OMNI nightly. After install, it hangs on Samsung logo (soft brick?). Restored to backup, but still hangs. Tried installing SlimKat 4.4, but the install fails. Unsure where to go from here.
Phone still powers up, goes into both Download and Recovery mode. TWRP is the current bootloader(?)/recovery(?).
So, is there a simple reason I'm soft-bricked? I read that Knox is in the bootloader, so is it because I'm using TWRP that it hangs? I find it odd that after restoring to previous settings it still doesn't function. Also, I don't care about the warranty bit, so anything is on the table for me.
Much love to those who spend the time to help out, please link to any resources for me and others who have the same problem. I'll append the working solution to this post for quick access in the future!
Click to expand...
Click to collapse
TWRP is your recovery. How were you wiping in between flashes? Sounds like the phone wasnt wiped correctly, causing it to hang. You should be able to flash any ROM zip, because ROM zips dont flash the bootloader, they just flash the system and the kernel. You can flash 4.3 stock tar file in ODIN, but you cant flash anything under 4.3 in ODIN, because tar files flash all parts including the bootloader. If you flash a 4.2 stock tar in ODIN, you will brick instantly.
joeyhdownsouth said:
TWRP is your recovery. How were you wiping in between flashes? Sounds like the phone wasnt wiped correctly, causing it to hang. You should be able to flash any ROM zip, because ROM zips don't flash the bootloader, they just flash the system and the kernel. You can flash 4.3 stock tar file in ODIN, but you cant flash anything under 4.3 in ODIN, because tar files flash all parts including the bootloader. If you flash a 4.2 stock tar in ODIN, you will brick instantly.
Click to expand...
Click to collapse
I used ODIN to flash TWRP, then wiped using TWRP, factory reset/dalvik cache. It seems that the problem was actually with TWRP, however. Apparently it doesn't install 4.4 KitKat ROMs correctly, from another post that I read. I installed PhilzTouch Recovery instead, and it installed just fine. Phone is working just fine running the latest SlimKat, however I still have no audio output.. So, still gotta figure that out.
Yo. (sorry if this thread is already on the board, I couldn't see it after a quick check)
So, I've hit upon quite a snag while trying to update my custom ROM (Android Revolution HD). I made a rookie error of installing this without installing the new firmware.zip first , but I was able to flash the correct firmware.zip (my phone if S-OFF, CID = 02__001). However, after this, my phone went into Android stock recovery <3e> after being in a bootloop, even though I'd already had TWRP installed. Also, ADB on my computer no longer recognises my phone, so I can't flash an img on it; the only option I can now see is to find a zip which I can install from the stock recovery via my SD card, but I can't seem to find one which the stock recovery will let me install.
Anyone have any ideas?
Strangiato said:
Yo. (sorry if this thread is already on the board, I couldn't see it after a quick check)
So, I've hit upon quite a snag while trying to update my custom ROM (Android Revolution HD). I made a rookie error of installing this without installing the new firmware.zip first , but I was able to flash the correct firmware.zip (my phone if S-OFF, CID = 02__001). However, after this, my phone went into Android stock recovery <3e> after being in a bootloop, even though I'd already had TWRP installed. Also, ADB on my computer no longer recognises my phone, so I can't flash an img on it; the only option I can now see is to find a zip which I can install from the stock recovery via my SD card, but I can't seem to find one which the stock recovery will let me install.
Anyone have any ideas?
Click to expand...
Click to collapse
the stock recovery can be easily replaced by going to bootloader/FASTBOOT USB, and
Code:
fastboot flash recovery <name of twrp>.img
so that's easy, but it sounds to me like you flashed a firmware pulled from an OTA, which could have a potential problem:
If you didnt flash "OTA firmwares" incrementally, then you may have missed updates.... ie firmwares pulled from OTAs are incremental, because they expect all previous updates to already there, flashing the "latest" does not mean you actually have all the firmware updates
I recommend using "Combined" "NoWipe" firmwares, such as the ones found here: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
(^^ those also happen to include TWRP, but you can still reflash a newer version using above fastboot command)
this is what a firmware flash would look like: http://forum.xda-developers.com/showpost.php?p=60259359&postcount=2
nkk71 said:
the stock recovery can be easily replaced by going to bootloader/FASTBOOT USB, and
Code:
fastboot flash recovery <name of twrp>.img
so that's easy, but it sounds to me like you flashed a firmware pulled from an OTA, which could have a potential problem:
If you didnt flash "OTA firmwares" incrementally, then you may have missed updates.... ie firmwares pulled from OTAs are incremental, because they expect all previous updates to already there, flashing the "latest" does not mean you actually have all the firmware updates
I recommend using "Combined" "NoWipe" firmwares, such as the ones found here: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
(^^ those also happen to include TWRP, but you can still reflash a newer version using above fastboot command)
this is what a firmware flash would look like: http://forum.xda-developers.com/showpost.php?p=60259359&postcount=2
Click to expand...
Click to collapse
Thanks for this info and links to the relevant threads, btw.
My biggest problem was that my computer wouldn't find my phone, so I couldn't use fastboot, but now for some reason, using the HTC One Toolkit that was in the post you linked me to, my computer can now see it. I've hit another snag, though, whereby I'm just after flashing the newest version of TWRP, but now for some reason, it didn't seem to install correctly, as the phone has booted into recovery mode, according to my computer, but is stuck on the opening screen with the pink "Entering Recovery..." message on the top. Also, my computer can't seem to touch it now, as even though the toolkit finds it and sees it in recovery mode, any time I try to reboot it or do any other command, the program crashes. I've no idea what's happened, unfortunately :/
Update: after fiddling around with the HTC Toolkit, I was eventually able to boot my phone into bootloader which, from there, I could install what I needed, so my problem's been resolved. Thanks again for your help, as those links proved very useful.
Glad everything worked out.
By the way:
Strangiato said:
but is stuck on the opening screen with the pink "Entering Recovery..." message on the top.
Click to expand...
Click to collapse
^^ is usually caused by using a new version of TWRP with old firmware
A couple days ago, I tried to flash my i747 back to stock, but unfortunately it froze at the Samsung Galaxy S III logo, and is no longer accessible. Another mistake that I think I made was I failed to realize that my phone would go back to stock recovery with flashing the stock rom. As a result, I now can't flash any custom rom or recovery due to "signature verification failed" error. Lastly, my phone can't seem to connect to the computer, so I can't use Odin either. When I connect my phone (in download mode) to the computer, an error would pop up saying that "one of the USB devices has malfunctioned"...I already tried to use different USB cables, different computers, update driver, battery pull, wipe data/factory reset, wipe cache, etc...but nothing prevailed. I'm a newbie to the android system, and I would really appreciate any suggestion on how I might get out of this conundrum, and get my phone back. Thank you!
Before you attempted to flash back to stock what ROM were you running?
What bootloader and modem were on your device before trying to flash stock?
Which stock rom did you attempt to flash to your phone?
If you were not flashing an older bootloader than was on your phone, you may need to do a factory reset from the stock recovery and reflash the stock rom. If you attempted to flash an older bootloader than had been on the device, you may need to search the forums for a debrick image with the same bootloader that was on the device before this started.
Before you attempted to flash back to stock what ROM were you running? __Dirty Unicorns 5.1.1__
What bootloader and modem were on your device before trying to flash stock? Baseband version: I747UCUFNJ1 (DU rom); does flashing a custom rom change the bootloader/modem? if not, i think the modem is I747UCUEMJB
Which stock rom did you attempt to flash to your phone? Jellybean 4.1.1 _I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5_
Actually, I was able to successfully flash back to the stock rom before the hanging at logo problem occurred, except for the fact that there was no sound and apps such as youtube failed to function properly. And so, what I did was I put a debrick.img into the internal storage and run "su dd if=/sdcard/debrick.img of=/dev/block/mmcblk0" in terminal, because I have bricked my phone and this has worked to bring back the sound in the past. If I remember correctly, I've used the the "debrick command" several times before and occasionally the phone would hang just like now, but then I just had to reflash the rom with the custom recovery and the phone would go back to normal. However, im stuck with the stock recovery this time and can't flash anything. Anyway, is there something that i can try with the new infos? Thank you for helping!
zynl said:
...what ROM were you running? __Dirty Unicorns 5.1.1__
...before trying to flash stock? Baseband version: I747UCUFNJ1 (DU rom);
i think the modem is I747UCUEMJB
Which stock rom did you attempt to flash Jellybean 4.1.1 _I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5_
Click to expand...
Click to collapse
No, flashing a custom ROM will not change bootloader and modems, but stock ROMs will.
Baseband and modem are the same thing, as is radio (in most instances). Since you had DU running successfully, in all probability your bootloader and modem were both NJ1. Everything I have seen indicates all AOSP and CM 5.x.x and their derivatives must be on at least NE4 bootloader and modem. If you can get into download mode, and their is anything on the screen about "Warranty Bit" you were on a 4.3 or higher bootloader.
Now for the negative; if you were on a 4.3 or higher bootloader downgrading the bootloader will brick the device. Once you are on any of the 4.4.2 bootloaders, NE4 or newer, you must keep the bootloader and modem versions paired. That is: they must both be NE4, or both NJ1, or both NJ2 otherwise you risk bricking the device. (This is why I think your bootloader was NJ1.) More negative is that the 4.1.1 stock rom you flashed contains the LK3 bootloader and modem.
zynl said:
Actually, I was able to successfully flash back to the stock rom before the hanging at logo problem occurred, except for the fact that there was no sound and apps such as youtube failed to function properly. And so, what I did was I put a debrick.img into the internal storage and run "su dd if=/sdcard/debrick.img of=/dev/block/mmcblk0" in terminal, because I have bricked my phone and this has worked to bring back the sound in the past. If I remember correctly, I've used the the "debrick command" several times before and occasionally the phone would hang just like now, but then I just had to reflash the rom with the custom recovery and the phone would go back to normal. However, im stuck with the stock recovery this time and can't flash anything. Anyway, is there something that i can try with the new infos? Thank you for helping!
Click to expand...
Click to collapse
I am surprised you were able to boot at all after flashing the stock ROM. If you are still able to boot froman external sdcard, flashing a debrick image is what I would suggest next. Once you boot, install a custom recovery and verify bootloader and modem on the device from the recovery terminal if possible. The next step would be flashing the NJ1 bootloader and modem. Two threads for reference:
http://forum.xda-developers.com/galaxy-s3-att/general/solution-hard-brick-fix-amazing-t2962611
http://forum.xda-developers.com/showthread.php?t=2549068
If this doesn't work you may be looking needing a jtag service. Worse than that would be a new motherboard for the phone.
Hello
To me it look like you get stuck in boot. First you will need to download correct ATT ROM. Then you will need to select appropriate option in ODIN. Let me know if you have any question. I will help you out. Guaranteed))
If you are able to boot into recovery and download mode, the debrick sdcard method won't do any good. Not saying to not try it if you want to, but I've never seen it work unless the device is truly hard bricked (totally unresponsive). It's only in those cases that it will even look for the image on an SD.
When you boot download mode and connect to the computer, does Odin show a COM# in the upper left? Does it respond in any way at all?
Also check to make sure kies is NOT installed on the computer. It can interfere with Odin. If you still cannot connect, try an older driver version. (See my sig).
Uninstall the old first. Then install the other version and reboot. Connect the device and open device manager. Right click on the USB device that isn't working and update driver. Try auto if you want, but if that doesn't work select manual. Browse to the Samsung folder in Program files and try selecting it that way. (I can't recall the exact location, but you should be able to find it if you poke around a little).
Hope that helps.
Good luck!
Sent from my SGH-T999 using Tapatalk
thanks everyone for helping. after abt a week trying to revive my phone, i finally gave up. recently though, i bought a bricked motherboard for cheap and successfully unbricked it. everything seems to be working fine except i can't switch on the wifi. I already tried wiping cache, factory reset, and even reflashing stock rom (4.3 from samsung) via odin but nothing worked. So, i wonder what could be the source of this? (hardware?.... software??... bc the volume up button also does not work!) and is there something that i can try to possibly fix this? The phone is currently on 4.3, bootloader and modem are both i747UCUEMJB.