Am unlocked, S-off, rooted, otherwise stock 4.4.3. Was trying to update to the latest 4.4.4 so replaced TWRP with stock recovery. First attempt failed, red triangle. I figured this was due to Viper4android and the buildprop tweaks that required so I uninstalled the driver and replaced the buildprop with stock version. At this point, I had turned fastboot on and USB debugging off.
After this the phone will not reboot to OS. I can get the HTC screen to flash for a few seconds by pressing Power+VolUp, which then goes black and nothing happens. I can also sometimes get to bootloader, but cannot get my PC to recognize the phone in ADB so not much luck there.
I assume something went wrong with Viper4Android uninstallation or I screwed up the buildprop replacement. Am out of ideas, should I do a factory reset in the bootloader? I do have a TWRP backup, but I can't replace the recovery or anything else through ADB for that matter.
Edit: I did notice in bootloader that OS gets no version info, so something obviously gone wrong there. I just have no idea what to do without ADB. I guess I'm screwed.
Thanks for any help!
MrDelicious said:
Am unlocked, S-off, rooted, otherwise stock 4.4.3. Was trying to update to the latest 4.4.4 so replaced TWRP with stock recovery. First attempt failed, red triangle. I figured this was due to Viper4android and the buildprop tweaks that required so I uninstalled the driver and replaced the buildprop with stock version. At this point, I had turned fastboot on and USB debugging off.
After this the phone will not reboot to OS. I can get the HTC screen to flash for a few seconds by pressing Power+VolUp, which then goes black and nothing happens. I can also sometimes get to bootloader, but cannot get my PC to recognize the phone in ADB so not much luck there.
I assume something went wrong with Viper4Android uninstallation or I screwed up the buildprop replacement. Am out of ideas, should I do a factory reset in the bootloader? I do have a TWRP backup, but I can't replace the recovery or anything else through ADB for that matter.
Edit: I did notice in bootloader that OS gets no version info, so something obviously gone wrong there. I just have no idea what to do without ADB. I guess I'm screwed.
Thanks for any help!
Click to expand...
Click to collapse
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
---------- Post added at 02:02 AM ---------- Previous post was at 01:57 AM ----------
str8str said:
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
Click to expand...
Click to collapse
Also best way to update your firmware is thru a bootlloader flushable zip as well you don't have to worry about restoring stock recovery and doesn't matter what rom your on etc. There are threads on how to do it very easy.
str8str said:
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
---------- Post added at 02:02 AM ---------- Previous post was at 01:57 AM ----------
Also best way to update your firmware is thru a bootlloader flushable zip as well you don't have to worry about restoring stock recovery and doesn't matter what rom your on etc. There are threads on how to do it very easy.
Click to expand...
Click to collapse
Thanks! I shall look into this.
Hi all, my nexus is a very poorly little thing at the moment. Bootloops on the google screen on start and can't get to recovery from the bootloader. I have tried flashing with a stock rom but it is still bootlooping. I'm assuming the next step is to try flashing the bootloader, something I'm very scared of doing without being absolutely sure that I'm not about to turn my critically ill nexus into a completely dead nexus. Could anyone give me the exact commands I need to use to do this?
cthulhu_tentacles said:
Hi all, my nexus is a very poorly little thing at the moment. Bootloops on the google screen on start and can't get to recovery from the bootloader. I have tried flashing with a stock rom but it is still bootlooping. I'm assuming the next step is to try flashing the bootloader, something I'm very scared of doing without being absolutely sure that I'm not about to turn my critically ill nexus into a completely dead nexus. Could anyone give me the exact commands I need to use to do this?
Click to expand...
Click to collapse
I think all you need to do is reflash the recovery. Your bootloader may be fine. Did you accidentally erase your recovery partition? What were you doing when you first saw the problem?
DroidIt! said:
I think all you need to do is reflash the recovery. Your bootloader may be fine. Did you accidentally erase your recovery partition? What were you doing when you first saw the problem?
Click to expand...
Click to collapse
I didn't do anything unusual. Went to sleep. Woke up in the morning and it was frozen. Gave it a long press on the power key and has been stuck ever since. Just tried the one-click restore here http://forum.xda-developers.com/showthread.php?t=2381582 and it is still bootlooping after that.
OK, I'd download a recovery to your computer and fast boot flash it that way. I've not used that tool, but I did the same once. I accidentally erased my recovery partition. So I just redownloaded the latest twrp .IMG and did fast boot flash recovery and all was fine. That's what I'd suggest for a start.
---------- Post added at 10:13 PM ---------- Previous post was at 10:10 PM ----------
Ah I see, that tool wipes your entire device. So I'd go here https://developers.google.com/android/nexus/images and download the latest factory image. While in your boot loader, connect to your computer and run the .bat file from the download. That all return you to stock. Be patient it takes some time, but that should solve your issue.
Thanks, giving it a shot now
Yep, download, unzip, connect to computer while in bootloader, and double click the .bat file. It will go through a series of flashings. It's restoring everything to factory. Just leave it plugged in until it starts to boot up. ?
I followed directions found online to unroot and restore the SIII to factory. Everything went fine I followed all the directions: downloaded the Stock ROM onto the phone along with Mobile Odin, Mobile Odin Flash Kernel and Triangle Away. Ran Triangle Away successfully then loaded the Stock Rom with Mobile Odin and even Flashed the Kernel without a hitch! Phone rebooted and I was presented with messages about the phone having to reboot to install updates, etc... I let it - the phone reboots and now ceases to turn on. Nothing works! I've tried pulling the battery, holding down the power button with and without the a battery, tried turning the device on while plugged in to wall - nothing!
I'm thinking maybe the main board got fried? If that's the case is all lost with this phone? I really do like this phone and would hate to lose it to such a dumb mistake especially when I was just trying to restore it to it's original state.
Any way to save this phone? Anyone else have had a similar problem and solution?
Thanks!
Never stock flash a Full Official ROM with mobile Odin, youre bootloader got corrupted and you'll need a 16gb class 10 sdcard to repair it, search this forum for the debrick image.
Official Stock can only be done PC Odin and Kies.
---------- Post added at 08:09 AM ---------- Previous post was at 08:08 AM ----------
Or 32gb if you have that model
I have what's probably a unique situation, though I hope not. For background info, I bought two I747s, one white and one blue, each with issues, but I intended to put parts together to end up with one good one.
When I did a factory reset on the blue one via the recovery menu, it returned a bunch of errors along the lines of "failed to mount /data." Then when it rebooted it would hang on the Samsung logo. Back in recovery mode it returns more of the same errors just booting into recovery mode, and factory reset still returns more of the same errors and doesn't fix anything. I flashed 4.3 with Odin in an attempt to fix it, but I got the boards mixed up, and that one had 4.4 on it, not 4.1 like I thought. I'm pretty sure it's hard bricked now (that whole can't downgrade thing) because it's unresponsive to everything. Though my computer does recognize that it's plugged in, more on that later.
So I figured, fine, I screwed up, I'll just use the other board with 4.1 on it from the white phone. Except when I did a factory reset on that one, it did the exact same thing! Same errors, same problem stuck at the Samsung logo. Except this time I'm not flashing sh*t until I know exactly what I need to do to fix it. In another post where the guy had the same issue with 4.1.1, it was solved by flashing 4.3 with Odin. And another post where the guy had no idea what version he had, he just knew it was lower than 4.3, his problem was also solved by flashing 4.3, But since my last efforts failed miserably, I'm very reluctant to try it until I get some knowledgeable input. I don't remember exactly which version is on there, it's 4.1.something. I'd also prefer not to upgrade beyond 4.1 because I'd like to unlock it and from what I'm reading you can only do it for free if you're on 4.1. So I guess I need a link to an Odin flashable 4.1 package?
As for the poor blue phone that used to have 4.4.something, and was mistakenly flashed with 4.3, I've heard about JTAG but I don't quite understand it, and I'm not sure it would work in my case since a lot of what I'm reading says that bricking which occurs from downgrading is often unfixable. However, Windows recognizes that a device is plugged in when I attach it via USB. It shows up in the Device Manager as QHSUSB_DLOAD. I am currently researching more on this and the method of booting from an SD card, except I don't have an SD card reader at the moment.
Any assistance, advice, links, information, and plain ole encouragement are always welcome and appreciated.
For the phone running 4.1, flash any stock rom in Odin. After flashing, boot into recovery and perform a factory reset, then boot the phone and use the free method to sim unlock. The important thing is to have the stock 4.1.1 dialler in order to access the hidden menu options?
For home hard bricked phone, you will have to try the debrick image method. If it doesn't work, a jtag service should be able to force flash a rom to the phone.
Wow, that was like a crazy fast reply!
What if the phone is 4.1.2? Can I still flash 4.1.1? I'm on the hunt for a 4.1.1 stock rom now.
Yes, you can flash 4.1.1 from 4.1.2.
audit13 said:
Yes, you can flash 4.1.1 from 4.1.2.
Click to expand...
Click to collapse
Apparently not always. I downloaded and flashed 4.1.1 with Oden 3.07, it rebooted, showed the android image like it was updating, progress bar finished, and then it just went blank. Now both phones are in the same condition of being hard bricked and showing QHSUSB_DLOAD in the device manager.
This is strange. I have downgraded approximately 10 i747m phones from 4.1.2 to 4.1.1, unlocked using the free method, and re-flashed back to 4.1.2 after unlocking.
http://forum.xda-developers.com/showthread.php?t=2371897
What options did you check in Odin? Where did you get the 4.1.1 ROM? I ask because the stock ATT 4.1.1 rom was apparently removed from sammobile.com.
How did you confirm that the phone was running 4.1.2?
I checked only auto reboot in Odin.
I found this link sammobile.com/firmwares/database/SGH-I747/ in this thread http://forum.xda-developers.com/galaxy-s3-att/help/downgrade-att-running-stock-4-4-2-rom-t3170938 , 7th post
The download was going absurdly slow, so I googled the exact file name being downloaded which was, I747UCDLK3_I747ATTDLK3_ATT, and found a google drive link at https://drive.google.com/file/d/0B_UTWXKFnZoNVFdSVjJEZlMwZjA/edit which was the first result after searching for the file name if that link doesn't work. I'm downloading the slow one now to compare it to the one I got from google drive.
I'm unsure if the phone was 4.1.1 or 4.1.2, that's why I asked if it's possible to flash 4.1.1 on top of 4.1.2. I was only trying to do a factory reset originally and had no intentions of flashing anything. I just wanted to wipe out all the crap on it from the previous user so I had only glanced at the version out of curiosity to see if it was unlockable via the free method. I remember it was 4.1.something.
I have an SD card reader on order. Hopefully I'll be able to unbrick one of them.
Do you, or anyone else, have any idea why a simple factory reset would cause errors like I described and then hang on reboot? At that point both phones were 100% factory and I hadn't done anything to them except put a battery in them to power them on. I've done a factory reset on four other S3s and this didn't happen.
It is definitely possible to flash 4.1.1 over 4.1.2 because the bootloader could not be downgraded until the mjb version.
That's what I've been reading. So where did I go wrong? Any idea why a factory reset would screw up like that?
Did you confirm the bootloader before flashing?
audit13 said:
Did you confirm the bootloader before flashing?
Click to expand...
Click to collapse
No, because I had no intentions of flashing it when I tried to do a factory reset. Then after that went bad it wouldn't boot, and I don't know how to check the boatloader when a phone will only go into recovery mode.
Where did you see reference to 4.1? It's possible that the modem or baseband was 4.1 but the bootloader was 4.3.
Under about device and then Android version. The one where if you tap it a lot you get the jellybean android that pops up. It wasn't the baseband version because that's a much longer number with the model number in it.
That screen doesn't tell you the bootloader.
As I said, I didn't check for the bootloader version before I ran into trouble because I only wanted to do a factory reset and I didn't intend to flash anything. I wouldn't imagine that it would have a different bootloader than the OS version unless that can happen without any user intervention because the previous owner was only concerned with selfies and games. She certainly didn't modify anything.
I cant explain what happened. This has never happened to me after flashing about 10 phones.
I believe it has something to do with the errors that were produced while trying to do a factory reset. What bothers me is that both phones did the exact same thing. Normally I'd say it was something I did, except that I didn't do anything but put a battery in them, boot up, find lots of junk installed, and then attempt a factory reset. On the first phone, I rebooted into recovery and tried it from there. On the second phone I tried it from inside the OS. Same results on both. The phones ran fine before that.
Any advice on how to do the boot from an SD card, or how to do the JTAG thing? I've been reading a lot but the information jumps around a lot. I'm comfortable with soldering and have an IT background if that helps.
It's possible that the recovery was corrupt or the partitions were corrupt.
Whenever I factory reset a phone, I always boot into recovery to do that, not from within the ROM.
Sounds to me like you did nothing wrong.
Did the previous owner have the phone from the time it was new?
Edit: for the phone that you flashed with 4.1.1, Odin said "pass" in the status window and the it auto rebooted?
audit13 said:
Did the previous owner have the phone from the time it was new?
Edit: for the phone that you flashed with 4.1.1, Odin said "pass" in the status window and the it auto rebooted?
Click to expand...
Click to collapse
I don't know for sure if she had it from new. Yes, for both phones Odin said pass in the window and then it rebooted. I had walked away when Odin finished with the first phone. I came back and it was dead. The second one I watched and it showed the android with the wireframe in his guts and the progress bar which moved across, and then it just went blank.
There were error messages about the partitions when I did the factory reset IIRC. Perhaps the recovery or the partition was corrupted like you said. It's just odd that both had the exact same identical problem with the exact same results. That's why I think that it must have been something I did, except that I didn't DO anything other than initiate a factory reset.
I took an i747m and reflashed stock the Telus 4.4.2 ROM.
In download mode, you should see the green Android guy with the words "Downloading...Do not turn off target" and a blue progress bar moving from left to right.
I did not check reset in Odin. Once it finished flashing the ROM, I removed the USB cable, removed the battery, replaced the battery, and booted the phone. I the Android guy with the wire frame for a few seconds, the screen went blank, and the phone started up with the Samsung logo.
Since you were getting errors with mounting the different partitions, you may have needed to flash the PIT and PDA files but I can't really say for sure as I have never encountered this problem.
I normally verify everything before I use Odin because phones that I have been given to fix have had all sorts of weird configurations.
You'll have to try the debrick guide. of use a jtag service. You could also do what I did and that is to look for people with phones that have a damaged screen and buy they at a steep discount.
Need some guidance on this one. Went through trying to root my Note 4. Upgraded from 4.4.4 to 5.1.1 after all this time waiting. From there, continually hitting soft bricks (referring to endless boot loop in regards to soft brick) and a lot of the issue I believe to be my battery. However, was originally able to flash the 5.1.1 FW (N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar.md5) and the brick would be remedied. At this point however, the note just goes into a endless boot loop where only thing it displays is the "Samsung Galaxy Note 4 Powered by Android" splashscreen (Never displays the oval samsung or verizon splashscreens) and vibrates twice as the screen display goes off for about 3 secs and pops back up with the same screen over again. At this point, the only thing I have found to remedy this is the Verizon Software Update program, which instantly updates to 6.0.1 (newest FW). This wouldn't be an issue, with the exception that the 5.1.1 FW still puts the phone into the soft brick state. Anyone have an idea why the FW is now putting into a brick and how to fix the issue so I can downgrade successfully?
In case it matters, to get the Verizon program to work, I would flash "N910VVRU2BPA1_StockRestore.tar.md5" via Odin and from there, download mode would then populate a screen stating update failed and to utilize the program. Seems to be the only way to get it to be able to connect.
Also, with all that said, the one thing I have thought about doing, but haven't is re-partitioning with a PIT file. However, I have not come across any threads on re-partitioning the Note 4 and those that refer state not to. With that said, I wouldn't mind attempting it if someone else feels like it may work. If so, please lead me to a thread with instructions along with a correct PIT file in order to run through the process please.
hey man I'm actually running into a similar issue. Ran into it while attempting to Root via Kingroot on 5.0.1 I was following a guide, the phone rebooted on it's own during the process and didn't have any issues rebooting, but at one point I wanted to reboot and instead of pulling the battery like normal, I decided to press the reboot option in the power menu, bad idea, now I'm bricked and Odining PA1 is not allowing a proper boot... have you found a solution to your problem? maybe it would help me with mine
---------- Post added at 10:52 PM ---------- Previous post was at 10:50 PM ----------
well after a really long battery pull, its booting up for me, I hope you were able to resolve this issue