Related
Hi,
I just tried performing the ICS update on my Transformer. However during this process, the tablet showed a yellow triangle with a black exclamation mark in it. I waited for about 10 minutes to see if anything would happen, but it just stayed on this screen. So I powered it down and tried turning it back on, but it just gets stuck on the Asus/Nvidia splash screen on boot.
I have tried holding the power button and volume down and entering recovery mode, however I get the same yellow triangle as I had before. If I wait without going in to recovery I get the option of performing a cold boot or wiping the data on the tablet. If I select cold boot, it just hangs, I have left it there for 10 minutes or so to see if it would work but get nothing. I have also tried wiping the data from this menu then retrying all the steps I have mentioned above, but it still doesn't work.
It is not rooted and I have applied all other updates to it without trouble so far. Is there anything I can do to fix this?
Thanks,
Ryan
I had the exact same problem. Got it fixed. Use the method from this thread: tabletroms.com/forums/transformer-rom-development/1071-asus-transformer-nvflash-stock-3-1-stock-3-2-recovery-roms-unbricking-tools.html
Thanks for your reply. I noticed on that page that it says that if the serial number is BD70 or above (which mine is) do not use the tool. Has there been an update that allows this to be used on the newer units?
Thanks,
Ryan
Hi there!
I got a similar problem yesterday and the error was that a file inside the DATA partition could not be deleted. I noticed when doing a factory reset from CWM.
If you have CWM and you can flash the "super wipe tool" you can fix the problem. Then you re-flash the ROM. I got it working and now I'm on a clean clean clean clean.... clean shiny install
check my threat if you want:
http://forum.xda-developers.com/showthread.php?t=1516204
Hope it helps!
I'm guessing I do not have CWM as I do not know what it is?
Thanks,
Ryan
sh.assassin said:
Hi,
I just tried performing the ICS update on my Transformer. However during this process, the tablet showed a yellow triangle with a black exclamation mark in it. I waited for about 10 minutes to see if anything would happen, but it just stayed on this screen. So I powered it down and tried turning it back on, but it just gets stuck on the Asus/Nvidia splash screen on boot.
I have tried holding the power button and volume down and entering recovery mode, however I get the same yellow triangle as I had before. If I wait without going in to recovery I get the option of performing a cold boot or wiping the data on the tablet. If I select cold boot, it just hangs, I have left it there for 10 minutes or so to see if it would work but get nothing. I have also tried wiping the data from this menu then retrying all the steps I have mentioned above, but it still doesn't work.
It is not rooted and I have applied all other updates to it without trouble so far. Is there anything I can do to fix this?
Thanks,
Ryan
Click to expand...
Click to collapse
Ok, I'm going to help you unbrick your device. But you need to forget everything other people in here have told you. Ok? And just do. Don't question. Just follow the steps.
(1) Go to the following asus webpage, choose android as OS and download your version of the 21 firmware. WW, US, TW, etc.
http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download
(2) Rename the downloaded zip file to "EP101_SDUPDATE.zip"
(3) Move zip file to a micro sdcard.
(4) Insert microsdcard into the TF.
(5) Turn off TF.
(6) Power on by pressing power button and volume down buttons at the same time. When white texts appear on upper left hand corner, release power button and volume down buttons and press volume up button.
(7) Watch your TF unbricking itself.
(8) Leave it alone to do its thing.
(9) Write me a check for 2,000 yen.
Thanks, that has sucessfully unbricked the tablet.
However if I try to attempt the ICS update again it says checking integrity of firmware file and then says update failed.
Does anyone have any ideas as to why this is happening?
Thanks,
Ryan
british.assassin said:
Thanks, that has sucessfully unbricked the tablet.
However if I try to attempt the ICS update again it says checking integrity of firmware file and then says update failed.
Does anyone have any ideas as to why this is happening?
Thanks,
Ryan
Click to expand...
Click to collapse
Download is corrupted. Have you tried again?
Yes I have, about 10 times and it always comes up with that error.
I had the same failure and had to install .13 and update 3times to get to ICS. Got it from the Unlockr link. Worked great and then rooted with ViperMod.
A clean install is seemingly not having as many issues. Plus I already have an AOKP ICS rom on my phone, so I already know most of the ICS features.
I did try downloading .13 and installing it the same way as I did .21 (putting in on the micro sd and powering on with power & vol - to get into recovery mode), however when I try this I get the yellow triangle and black exclamation mark again, only this time it does not stop my tablet from booting back in to .21.
british.assassin said:
Yes I have, about 10 times and it always comes up with that error.
Click to expand...
Click to collapse
This error comes up when you have a corruption in your stock recovery.
You won't be able to "downgrade" to .13 the way you did with this. Unfortunately, there's no easy way for you to go about this. Here is what you need to do. Yeah, it will be a little long.
(1) Root via nachoroot.
(2) Install CWM via recovery installer. Can be found in the app portion of this forum.
(3) Download the repacked .13 version from the following link.
http://dl.project-voodoo.org/transformer-roms/3.0.x/
(4) Download stock recovery.
http://forum.xda-developers.com/attachment.php?attachmentid=606402&d=1306284085
(5) Flash the repacked .13 version via CWM.
(6) Restart the TF.
(7) Flash the stock recovery.
(8) Restart TF.
(9) Upgrade via OTA. One of the updates will give you the appropriate stock recovery.
Failure to follow my instructions precisely will result in brick.
Yesterday, I started unlocking my bootloader on Xperia J ST26i in order to eventually finish with installing ParanoidAndroid 3. It all went successful until I got to the last step of rooting the device. This - http://forum.xda-developers.com/showthread.php?t=2183737 - is the method I used. I was confused when I got to step 16, because the kernel I copied for flash didn't show up. So, I'd finish with two choices after shutting the phone down, having exited CWM Recovery. I would either open CWM again, after seeing LEDs glowing purple/blue in order to press Volume down key to enter CWM - or to ignore and finish seeing grayscreen. Luckily, I was able to find a JB 4.1.2 kernel for my rooted Xperia J, so I put it and flashed it instead of the ICS kernel provided on the thread I referred to. That solved the problem. I had JB 4.1.2 installed and rooted with ROM Manager installed along with SuperSU app. The next step I was going to do was to install a ClockWork Recovery, I hesitated installing PA3 directly without a recovery image. Ironically, CW Recovery is what really made all the problems now. Searching on Google I found a way to boot directly to ClockWork Recovery, I pressed and held the buttons for initiating it but I ended up with literally no way to normally boot the phone. So, I couldn't turn on the phone except in fastboot mode. In fastboot, I whiped all the data, reset to defaults, reinstalled the boot.img and JB kernel, however after all the resets and whipping anything that, according to many sites and devs, should make the phone function again...it failed. After a dozen times of taking out the battery, button combos I ended up not being able to access neither fastboot mode with CWM showing all those options for whipping, installing etc. Only phone's upper LED was working and it blinked red so I recharged the phone, then it was all the same but it'd blink green. After another hour of trying to turn on the phone in any mode, nothing good happened. When I held the power button, it vibrated but after a minute or so only green LED activated. Then I downloaded recovery exit zips that I'd install if ever got to CWM again. I tried once again to directly boot into CWM recovering by holding the power button down and both sides of volume rocker. It blinked light blue, then green and later blue. Device flasher couldn't read the phone, so I opened flash mode. It read it, but any installation of boots or kernels failed because of the phone that either disconnected or simply failed. There was no way for me to put more files on Internal Storage or SD Card, only those LEDs started behaving the way I described. After another twenty times of battery removing, 10 second and 30 s waiting, button combos, anything I could find on Google, nothing changed. Except, suddenly, the computer is able to link with the phone after holding power button for boot that only activated the green/blue/violet LED. Still, no response from flashing program, still failed to enter fastboot, CWM, direct CWM Recovery etc. But, now when my phone is, let's say, turned on with green or blue light, I can access SD Card and Internal Storage via Windows Explorer. Just below the hard drives, I can see my phone. Great? No, it's not Xperia J as it should be, PC detects Xperia Tipo. I also noted that it's mistaken SD Card for Internal Storage... Let's see what happens when I remove SD card from the device. Please help...
Bricked
And yes, this means it's bricked. Can't boot into CWM or anything. It's only good as a storage unit, energy consuming or as a brick. I got this phone in January so please don't tell me it's irreversibly hard bricked.
dave96m said:
And yes, this means it's bricked. Can't boot into CWM or anything. It's only good as a storage unit, energy consuming or as a brick. I got this phone in January so please don't tell me it's irreversibly hard bricked.
Click to expand...
Click to collapse
Okay, so first calm down. Any sign of life means it's not hard bricked but just soft bricked.
1st download flashtool: link
2. download ur stock ftf link
3. flash it with flashtool
and u should be fine again, back to stock with a fresh phone.
Can't fastboot device - remember: button combos don't work
I've also found some solutions for more severe soft-bricking, by the way. Anyway, how to make phone open fastboot? I've said it's unresponsive to all of the button combo commands. Though, I tried one more time.
Opened the flashtool... Held volume up and plugged in the USB cable...
17/009/2013 22:09:51 - INFO - <- This level is successfully initialized
17/009/2013 22:09:51 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
17/009/2013 22:09:51 - INFO - You can drag and drop ftf files here to start flashing them
17/009/2013 22:09:57 - INFO - Device disconnected
17/010/2013 22:10:12 - INFO - Device connected with USB debugging off
17/010/2013 22:10:12 - INFO - For 2011 devices line, be sure you are not in MTP mode
Immediately, upper LED started glowing green, then it turned itself off after a minute. The phone is still connected.
Remember to pull up battery (and pull in of course ) than go to flashtool, fastboot PWR + Vol Up.
Solved
http://forum.xda-developers.com/showthread.php?p=41506173#post41506174 See my last post, scroll down. Thanks for help, guys
sony xperia j - alarm problem
Hi guys,
I bought Sony Xperia J and 2 months ago I upgraded the Android to the latest version 4.1.2 (Jelly Bean).
After the upgrade the Alarm on the phone does not go off, it starts to ring (the alarm) only when I press the button to unlock the phone, I've read somewhere that when the screen is off the clock is not refreshes properly or something like that.
Can you please, help me?
Regards
Lol I know that feel bro.... It happened to me few days ago but no worries i just flashed the firmware using flashtool whenever i failed. Now i'm happy with my CM10 with vengeance kernel... its not the phone that's causing the problem its up to us how we handle it and i didnt find PA3 that interesting it was too laggy for me...
I didn't experience any of such problems that you have, but still listen to the man's advice. Install CM10. It speeds up your device, gives you options, frees your Android. My friend knows the feeling of switching from iPhone to Nexus 4 and he's like he's enlightened or something, well once again, the feeling is the same if you switch from stock Android to CM or Paranoid. I suggest you install CM because Paranoid made me a lot of problems when installing even though I did everything right, and people claim that CM is more stable...
http://forum.xda-developers.com/showthread.php?t=1997251
I was on stock 4.1.2 (9.18.94), unlocked and rooted with stock recovery. Decided to take the 4.4.2 OTA that got pushed to my phone and left it there. Next thing I know an hour has passed and it's stuck on the red Moto logo. Pressing and holding Vol Down + Power just "resets" the phone and sends me right back to the logo. Vol Up + Power does nothing. What's more, it looks like this logo will be on my screen until the battery drains out, a solemn reminder of my folly.
So basically, am I right in thinking that no recovery == brick? Or is there hope for me yet?
I was in the same boat. I bricked my phone I think now my battery is dead. I'm waiting for my fastboot cable to arrive I ordered. In going to try a kkfix I found on it. Not sure I'd it's going to work or not.
Sent from my DROID RAZR HD using Tapatalk
jimmalachi said:
I was on stock 4.1.2 (9.18.94), unlocked and rooted with stock recovery. Decided to take the 4.4.2 OTA that got pushed to my phone and left it there. Next thing I know an hour has passed and it's stuck on the red Moto logo. Pressing and holding Vol Down + Power just "resets" the phone and sends me right back to the logo. Vol Up + Power does nothing. What's more, it looks like this logo will be on my screen until the battery drains out, a solemn reminder of my folly.
So basically, am I right in thinking that no recovery == brick? Or is there hope for me yet?
Click to expand...
Click to collapse
You should be able to get it into fastboot, but your recovery may have been mangled. To do that you may have to use all three keys together, then release power (the newer recovery uses all 3). check the kitkat tracking thread; a number of people had soft bricks as a result of not flashing EVERYTHING first. (myself included). They suggest HoM solution to get it back to stock, then flash the OTA, but you can probably just flash your previous load back, wipe all (cache, system etc) and redo the update. I also successfully ran my update before I got any further in the setup than activating the cell connection (didn't setup google or anything).
Also note that this is the xt926 for me. I can't speak to the xt925 if that's your model.
jimmalachi said:
I was on stock 4.1.2 (9.18.94), unlocked and rooted with stock recovery. Decided to take the 4.4.2 OTA that got pushed to my phone and left it there. Next thing I know an hour has passed and it's stuck on the red Moto logo. Pressing and holding Vol Down + Power just "resets" the phone and sends me right back to the logo. Vol Up + Power does nothing. What's more, it looks like this logo will be on my screen until the battery drains out, a solemn reminder of my folly.
So basically, am I right in thinking that no recovery == brick? Or is there hope for me yet?
Click to expand...
Click to collapse
over the past week i did about everything bad to my phone i could think of just to see what is possible with this new update. at one point my phone was borked exactly like yours, no recovery, wont shut off, wont boot. you have to be unlocked to fix it. assuming you are, follow the instructions here http://www.droidrzr.com/index.php/topic/44920-xt926-update-1824610-update/?p=432463 and you will be back up and running in no time. if you are locked, your hosed until the fxz gets leaked.
x40sw0n said:
You should be able to get it into fastboot, but your recovery may have been mangled. To do that you may have to use all three keys together, then release power (the newer recovery uses all 3). check the kitkat tracking thread; a number of people had soft bricks as a result of not flashing EVERYTHING first. (myself included). They suggest HoM solution to get it back to stock, then flash the OTA, but you can probably just flash your previous load back, wipe all (cache, system etc) and redo the update. I also successfully ran my update before I got any further in the setup than activating the cell connection (didn't setup google or anything).
Also note that this is the xt926 for me. I can't speak to the xt925 if that's your model.
Click to expand...
Click to collapse
...I'm an idiot. That worked perfectly. I'm downloading the OTA right now! I can't thank you enough!
Please guys, my galaxy S2 SHW-M20K (Korean) is in trouble.
I bought it from a 2nd hand shop , and it was runing Android 4.1.2 Jelly Bean (rooted stock rom). I had no problem with it till today when I tried to install "CWM Recovery", After searching the web i found a post with two files that supposedly could do the task. These files are:
1. CWM_KT_M250K.tar
2. Tegrak-Kernel-Build-39-for-SHW-M250K-UE18.tar
Using Odin, I triedd the first file but it couldn't work, and the phone could not boot so i downloaded the "rooted factory firmware" and flashed the phone. Everything was ok. Later I tried the second file. Again the phone could not boot and stuck at the logo with a yellow triangle. After waiting for about 5 minutes I tried to shut it down by pressing the power button it did'nt respond. (Now this is a point that I regret), I removed the battery as a way of forcing to turn it off.
Now my phone cannot boot. It doesn't respond to power button, neither does it allow me to enter recovery mode nor download mode. But When i connect to the charger or pc, it start charging and keeps cutting off the charging frequently. But it only allows me to enter download mode when connected to pc. When I tried to flash the "rooted factory firmware", again, the flashing goes smoothly but when the phone starts rebooting it fails as if there is a power cut. Is my battery damaged? Can someone give me a guide on how to fix it?
I need your help gus, I am not an expert in the rootings and roms,
Pardon My English. It's a foreign language to me.
Gombyz said:
Please guys, my galaxy S2 SHW-M20K (Korean) is in trouble.
I bought it from a 2nd hand shop , and it was runing Android 4.1.2 Jelly Bean (rooted stock rom). I had no problem with it till today when I tried to install "CWM Recovery", After searching the web i found a post with two files that supposedly could do the task. These files are:
1. CWM_KT_M250K.tar
2. Tegrak-Kernel-Build-39-for-SHW-M250K-UE18.tar
Using Odin, I triedd the first file but it couldn't work, and the phone could not boot so i downloaded the "rooted factory firmware" and flashed the phone. Everything was ok. Later I tried the second file. Again the phone could not boot and stuck at the logo with a yellow triangle. After waiting for about 5 minutes I tried to shut it down by pressing the power button it did'nt respond. (Now this is a point that I regret), I removed the battery as a way of forcing to turn it off.
Now my phone cannot boot. It doesn't respond to power button, neither does it allow me to enter recovery mode nor download mode. But When i connect to the charger or pc, it start charging and keeps cutting off the charging frequently. But it only allows me to enter download mode when connected to pc. When I tried to flash the "rooted factory firmware", again, the flashing goes smoothly but when the phone starts rebooting it fails as if there is a power cut. Is my battery damaged? Can someone give me a guide on how to fix it?
I need your help gus, I am not an expert in the rootings and roms,
Pardon My English. It's a foreign language to me.
Click to expand...
Click to collapse
As u mentioned, I think that your phone has gone to a Soft Brick. I don't know much about the Korean build, so Google it to solve the Soft Brick. Try flashing the stock rom via odin but I don't recommend it since it may cause your phone to be hard bricked if not done properly.
So go to the service centre, you'll get more help there
Sushant Rohan said:
As u mentioned, I think that your phone has gone to a Hard Brick. I don't know much about the Korean build, so Google it to solve the Hard Brick. But it is very hard to solve
Click to expand...
Click to collapse
I thank you sir for responding to this. From what you have said, I think the best decision is to take it to Samsung service center. (For I have tried to google it but I couldn't get a solution). I would also like to know if it is repairable, and about the cost, is it worth repairing or should I think of buying a new phone?
I am stranded.
Gombyz said:
Please guys, my galaxy S2 SHW-M20K (Korean) is in trouble.
I bought it from a 2nd hand shop , and it was runing Android 4.1.2 Jelly Bean (rooted stock rom). I had no problem with it till today when I tried to install "CWM Recovery", After searching the web i found a post with two files that supposedly could do the task. These files are:
1. CWM_KT_M250K.tar
2. Tegrak-Kernel-Build-39-for-SHW-M250K-UE18.tar
Using Odin, I triedd the first file but it couldn't work, and the phone could not boot so i downloaded the "rooted factory firmware" and flashed the phone. Everything was ok. Later I tried the second file. Again the phone could not boot and stuck at the logo with a yellow triangle. After waiting for about 5 minutes I tried to shut it down by pressing the power button it did'nt respond. (Now this is a point that I regret), I removed the battery as a way of forcing to turn it off.
Now my phone cannot boot. It doesn't respond to power button, neither does it allow me to enter recovery mode nor download mode. But When i connect to the charger or pc, it start charging and keeps cutting off the charging frequently. But it only allows me to enter download mode when connected to pc. When I tried to flash the "rooted factory firmware", again, the flashing goes smoothly but when the phone starts rebooting it fails as if there is a power cut. Is my battery damaged? Can someone give me a guide on how to fix it?
I need your help gus, I am not an expert in the rootings and roms,
Pardon My English. It's a foreign language to me.
Click to expand...
Click to collapse
Download stock firmware (like xxxx.tar.md5 full Odin package) of ur device ,enter into Download mode of ur device & flash stock firmware with Odin.
Try this...
Few weeks ago my phone started closing apps every now and then, sometimes even restarting itself when under "heavy" load like opening Snapchat filters with face recognition for example (maybe the processor is failing?).
The reboot sometimes took 5 minutes, sometimes more. One time it took the phone 1 hour to reboot.
A few days ago it rebooted itself and got stuck on the M logo for hours, I waited literally until battery drained.
Anyways, I tried to flash Android back on it on fastboot mode with RSD but it always stops at the system img step.
It says "PHONE returned FAIL" on RSD.
My Bootloader is Unlocked btw. Battery says OK. Status Code says 3. Fastboot reason says Sticky bit fastboot after the RSD restarts the phone.
I have tried with 3 different files and all stop at flashing system step. I had flashed 4.4 on it before. My phone is originally from Telcel (Mexico)
mauber said:
Few weeks ago my phone started closing apps every now and then, sometimes even restarting itself when under "heavy" load like opening Snapchat filters with face recognition for example (maybe the processor is failing?).
The reboot sometimes took 5 minutes, sometimes more. One time it took the phone 1 hour to reboot.
A few days ago it rebooted itself and got stuck on the M logo for hours, I waited literally until battery drained.
Anyways, I tried to flash Android back on it on fastboot mode with RSD but it always stops at the system img step.
It says "PHONE returned FAIL" on RSD.
My Bootloader is Unlocked btw. Battery says OK. Status Code says 3. Fastboot reason says Sticky bit fastboot after the RSD restarts the phone.
I have tried with 3 different files and all stop at flashing system step. I had flashed 4.4 on it before. My phone is originally from Telcel (Mexico)
Click to expand...
Click to collapse
Did you ever solve this issue?? I've got pretty much the same issue here, except mine is bricked... Won't even turn on, but if I connect to my pc the led turns green and after a few minutes it turns on, straight to fastboot. Same fastboot reason and everything. When I try to flash with rsd, it stays at step 2, trying to flash the sbl1 file... Then it fails and says PHONE returned FAIL... Any info from anyone is greatly appreciated!!
Luisit0 said:
Did you ever solve this issue?? I've got pretty much the same issue here, except mine is bricked... Won't even turn on, but if I connect to my pc the led turns green and after a few minutes it turns on, straight to fastboot. Same fastboot reason and everything. When I try to flash with rsd, it stays at step 2, trying to flash the sbl1 file... Then it fails and says PHONE returned FAIL... Any info from anyone is greatly appreciated!!
Click to expand...
Click to collapse
Nope Gave up and getting a Moto G 3rd gen
mauber said:
Nope Gave up and getting a Moto G 3rd gen
Click to expand...
Click to collapse
Ahh darn... Well, hopefully someone else sees this thread and is able to help out... Thanks anyways!
Hello, Luisit0 if your battery went bad then it could do that. Did you try hitting the power button when device is plugged into the home charger of the wall outlet? If you get to the M logo when you do that then its just the battery. If It does not do that and nothing happens you need a fastboot cable so you can flash the stock firmware. the fastboot cable will allow you to go to fatsboot mode without a battery.
OGdroidster said:
Hello, Luisit0 if your battery went bad then it could do that. Did you try hitting the power button when device is plugged into the home charger of the wall outlet? If you get to the M logo when you do that then its just the battery. If It does not do that and nothing happens you need a fastboot cable so you can flash the stock firmware. the fastboot cable will allow you to go to fatsboot mode without a battery.
Click to expand...
Click to collapse
HI, thanks for the reply. The thing is, the phone won't even get to the M logo. It charges and everything, but it powers up and goes straight to fastboot... It even said battery low, and after a while plugged in, it said battery ok, so I guess it's charging right. But like I said, no matter what combination I use, even the volume up + power button, it only goes straight to fastboot... I've tried numerous times to flash the Brazil and PR latam firmwares, and even after deleting the getvar and the md5 lines, it still gives me an error on step 2 when attempting to flash the sbl1 file and says FAIL on rsd lite 6.1.4...
Luisit0 said:
HI, thanks for the reply. The thing is, the phone won't even get to the M logo. It charges and everything, but it powers up and goes straight to fastboot... It even said battery low, and after a while plugged in, it said battery ok, so I guess it's charging right. But like I said, no matter what combination I use, even the volume up + power button, it only goes straight to fastboot... I've tried numerous times to flash the Brazil and PR latam firmwares, and even after deleting the getvar and the md5 lines, it still gives me an error on step 2 when attempting to flash the sbl1 file and says FAIL on rsd lite 6.1.4...
Click to expand...
Click to collapse
I am going to give you a two download links one to download proper drivers and another link for another version of rsd to try and flash your device back to life but first i need to know if your running 64bit system or 32bit system.
OGdroidster said:
I am going to give you a two download links one to download proper drivers and another link for another version of rsd to try and flash your device back to life but first i need to know if your running 64bit system or 32bit system.
Click to expand...
Click to collapse
That would be perfect!! I'm running 64bit windows 8
Luisit0 said:
That would be perfect!! I'm running 64bit windows 8
Click to expand...
Click to collapse
first install the drivers download link Here http://forum.xda-developers.com/attachment.php?attachmentid=3187938&d=1425146663 then install them on your windows 8 then install this rsd version after you uninstall the one you currently have and here is the link http://forum.xda-developers.com/attachment.php?attachmentid=3388466&d=1435873884 if this does not work hit me up after monday im in the middle of finals and working on a big programming project due monday after that I can help you figure this out if this does not work.
OGdroidster said:
first install the drivers download link Here http://forum.xda-developers.com/attachment.php?attachmentid=3187938&d=1425146663 then install them on your windows 8 then install this rsd version after you uninstall the one you currently have and here is the link http://forum.xda-developers.com/attachment.php?attachmentid=3388466&d=1435873884 if this does not work hit me up after monday im in the middle of finals and working on a big programming project due monday after that I can help you figure this out if this does not work.
Click to expand...
Click to collapse
Great!! Thanks so much!! I'll try this as soon as I get home in a few minutes, and hit you up after. Thanks again!!
EDIT: Okay so just a little update... I installed the drivers and it seems those were exactly the ones I had already installed, then I installed rsd lite 6.2.4 which you provided... Who wouldve known it was all in the version lol I was using 6.1.5 and, apparently, all I needed was to update... 6.2.4 did the trick!! However, not exactly... The firmware did finally flash completely and successfully, however it still boots directly to fastboot. The difference is, I can now actually access the boot menu holding volume down + volume up + power buttons, though every option I select only makes the bootloader unlocked warning come up and freeze there until I manually turn the phone off holding down the power button. If I select Normal Powerup, after a few seconds the warning goes away, but it never boots up. The other difference is, that now on fastboot, the reason now says "Sticky bit factory_fastboot". I'm going to attempt and flash the same firmware again, or my claropr latam firmware, or pretty much any other latam firmware and see if one of them works. Thanks again so much for your help so far!!!!
EDIT 2: IT LIVES!!!!!! Lol using rsd lite v6.2.4 did the trick. Apparently all I needed was to use the latest version of rsd lite... Man, I honestly cant thank you enough, you saved me a few 3 digit bucks on a new phone!! Lol, thanks so much for all your help!!
Luisit0 said:
Great!! Thanks so much!! I'll try this as soon as I get home in a few minutes, and hit you up after. Thanks again!!
EDIT: Okay so just a little update... I installed the drivers and it seems those were exactly the ones I had already installed, then I installed rsd lite 6.2.4 which you provided... Who wouldve known it was all in the version lol I was using 6.1.5 and, apparently, all I needed was to update... 6.2.4 did the trick!! However, not exactly... The firmware did finally flash completely and successfully, however it still boots directly to fastboot. The difference is, I can now actually access the boot menu holding volume down + volume up + power buttons, though every option I select only makes the bootloader unlocked warning come up and freeze there until I manually turn the phone off holding down the power button. If I select Normal Powerup, after a few seconds the warning goes away, but it never boots up. The other difference is, that now on fastboot, the reason now says "Sticky bit factory_fastboot". I'm going to attempt and flash the same firmware again, or my claropr latam firmware, or pretty much any other latam firmware and see if one of them works. Thanks again so much for your help so far!!!!
EDIT 2: IT LIVES!!!!!! Lol using rsd lite v6.2.4 did the trick. Apparently all I needed was to use the latest version of rsd lite... Man, I honestly cant thank you enough, you saved me a few 3 digit bucks on a new phone!! Lol, thanks so much for all your help!!
Click to expand...
Click to collapse
So you were able to boot into your ROM.
OGdroidster said:
So you were able to boot into your ROM.
Click to expand...
Click to collapse
Yeah, finally it's back to life and working again. Turns out all I needed was to use the 6.2.4 version. Thanks for the link! I would've never thought it was just that :highfive:
Luisit0 said:
Yeah, finally it's back to life and working again. Turns out all I needed was to use the 6.2.4 version. Thanks for the link! I would've never thought it was just that :highfive:
Click to expand...
Click to collapse
Your welcome, happy that it booted. Awsome! You ever need something or some help just hit me up.
xt 925 bricked?
Hi together...
need help...I wanted to reactivate my RAZR HD.....I flashed the Stock without any problem -> then ota dowload....and then only Fastboot mode...
gratis bilder