Related
I just recently tried to flash the Rom DeFroST using the Clockworkmod.
I can now not boot into the Rom (I get a looping splash, the cool colourfull nexus one X animation) and if I try boot into clockworkmod, it stalls at the Telstra splash (still image). I also cannot browse any files on the SD card, I have to remove it and insert it into the adpater.
I'm really afraid I've bricked it :/ Can someone help me? I can still get into HBOOT.
a1m said:
I just recently tried to flash the Rom DeFroST using the Clockworkmod.
I can now not boot into the Rom (I get a looping splash, the cool colourfull nexus one X animation) and if I try boot into clockworkmod, it stalls at the Telstra splash (still image). I also cannot browse any files on the SD card, I have to remove it and insert it into the adpater.
I'm really afraid I've bricked it :/ Can someone help me? I can still get into HBOOT.
Click to expand...
Click to collapse
your phone is not bricked.
did you root your phone first?
I have a Telstra phone and I had to flash an official WWE ROM first, then use gold card to root my phone and now I can flash any ROM.
My phone came unlocked, it was unlocked by the company from whom I ordered it from. Yes I did root it first. Atleast, I assume I did...
I used the linux version of rewvoked 3 and it completed with out errors. It has been trying to boot for approximately 13 minutes now and is still stuck on the animated nexus one splash...
It is now into its 21st minute, I somehow doubt it's going to boot
a1m said:
My phone came unlocked, it was unlocked by the company from whom I ordered it from. Yes I did root it first. Atleast, I assume I did...
I used the linux version of rewvoked 3 and it completed with out errors. It has been trying to boot for approximately 13 minutes now and is still stuck on the animated nexus one splash...
Click to expand...
Click to collapse
Unlocked and rooted are two different things. Is this your first flash of a custom ROM for the Desire?
Whenever you flash a ROM for the first time it does take a LONG time for it to process. I don't remember how long, can't tell you if 15 min is to long. You can always re-flash by putting the phone into recovery mode manually and using the USB method for flashing.
Yes this is my first ROM.
That's the problem, the phone stalls if I try and put the phone into recovery mode... :/ Unless that too is meant to take a very long time?
Ok, surely 1/2 an hour is beyond what it should take?
a1m said:
Ok, surely 1/2 an hour is beyond what it should take?
Click to expand...
Click to collapse
you need to start over.
did you read ALL of this before you started (not trying to insult you in anyway, just question) http://forum.xda-developers.com/showthread.php?t=696189
it will tell you how to put is into recovery mode and then how to flash using USB
Yes I did, although I did end up following separate guides as my boot loader was 0.83 as opposed to 0.8 and 0.75 or whatever those guides included. Ok, start over. Sounds good... I'll try that, but you'll likely hear back from me!
a1m said:
Yes I did, although I did end up following separate guides as my boot loader was 0.83 as opposed to 0.8 and 0.75 or whatever those guides included. Ok, start over. Sounds good... I'll try that, but you'll likely hear back from me!
Click to expand...
Click to collapse
My boot is .80, I am not sure if it changed when I flashed an official ROM first. I did that to get rid of all the Telstra stuff.
One thing you can try is to flash an official WWE ROM first. Then after you can go onto a custom ROM.
Ok, clockwork mod is working again, now to install thisWWE ROM, what exactly is it, where can I get it and what should I do?
Double post sorry
a1m said:
Ok, clockwork mod is working again, now to install thisWWE ROM, what exactly is it, where can I get it and what should I do?
Click to expand...
Click to collapse
here is the link to official ROM for the HTC Desire http://forum.xda-developers.com/showthread.php?t=695667
They may have a radio in them as well. Once you flash one make sure your desire works. Then try flashing your custom ROM. Many custom ROM's need to have the latest radio so make sure you follow the instruction for that ROM and the radio that ROM uses.
alwayslearning said:
here is the link to official ROM for the HTC Desire http://forum.xda-developers.com/showthread.php?t=695667
They may have a radio in them as well. Once you flash one make sure your desire works. Then try flashing your custom ROM. Many custom ROM's need to have the latest radio so make sure you follow the instruction for that ROM and the radio that ROM uses.
Click to expand...
Click to collapse
one more thing, once you get an official ROM working, go to market and download ROM manager, use it to flash a custom ROM, it might work better for you.
Ok thankyou! But to me a radio is a small transistor based device that uses variable capacitance in order to change frequencies... What is it in this case?
By the way, I thank you for your help, you've been of great assistance!
EDIT: One more thing, that's a lot of roms, which one do I want? Any? do I want signed or unsigned?
Ok I'm even more confused, they're mostly .exe's, how do I use them?
EDIT: It also says they're not rooted, does that mean I have to re-root my phone again?
Having the exact same problem as you, also a telstra phone.
Boots and gets stuck on the "X" colored animation.
If you get it going, please post here what you did
a1m said:
Ok I'm even more confused, they're mostly .exe's, how do I use them?
EDIT: It also says they're not rooted, does that mean I have to re-root my phone again?
Click to expand...
Click to collapse
A radio is the software that works your phone, GPS and wifi portions of the device.
use the first ROM on the list. Hold the volume down key and press the power key at the same time, hold them until you enter the recover screen. it will take about 30 sec to process, use the volume down key to select clear storage follow the instructions and this should set your phone back to factory setting (using the last ROM that worked on your phone). Your phone should be working and you should be able to boot-up.
From this point you will be able to connect your phone to your PC then click on the ROM (exe file) and follow the instructions to flash the official ROM
let me know what happens.
Ok so i need a windows PC? I'm on Ubuntu.
My Windows decided to implode after an update earlier this evening. Will probably leave that to download and go to bed. I'll post here tomorrow with how I get on tomorrow morning!
Hello there,
I just rooted and flashed a custom recovery to my S3 today. Afterwards, I installed CyanogenMod through the CWM recovery and rebooted, however,after the reboot the device powered off completely. Now when I try to turn on the device I get a grey battery icon with a static circle on it, and it does not proceed any further. I cannot access recovery mode or even get to the Samsung loading screen. Plugging the device into the wall charger doesn't seem to be doing anything as it has been 'charging' for over 30 minutes and still does not power on. I've been scouring the net for hours looking for answers, but the few people who seem to have the same problem have not found any sort of resolution. There are all sorts of tricks people are suggesting such as putting your battery in and plugging the cable in, vice versa..etc but nothing seems to work. The phone was working just fine and the battery still had a good 30-40% charge when this happened. Does anyone know what the issue could be? I cannot even get it serviced because I had JUST rooted/custom recovery'd it when this happened, so just my luck with that. If anyone could help me it would mean a lot. Thank you for reading.
Regards,
Mike
Cryceratops said:
Hello there,
I just rooted and flashed a custom recovery to my S3 today. Afterwards, I installed CyanogenMod through the CWM recovery and rebooted, however,after the reboot the device powered off completely. Now when I try to turn on the device I get a grey battery icon with a static circle on it, and it does not proceed any further. I cannot access recovery mode or even get to the Samsung loading screen. Plugging the device into the wall charger doesn't seem to be doing anything as it has been 'charging' for over 30 minutes and still does not power on. I've been scouring the net for hours looking for answers, but the few people who seem to have the same problem have not found any sort of resolution. There are all sorts of tricks people are suggesting such as putting your battery in and plugging the cable in, vice versa..etc but nothing seems to work. The phone was working just fine and the battery still had a good 30-40% charge when this happened. Does anyone know what the issue could be? I cannot even get it serviced because I had JUST rooted/custom recovery'd it when this happened, so just my luck with that. If anyone could help me it would mean a lot. Thank you for reading.
Regards,
Mike
Click to expand...
Click to collapse
Copy and paste the name of the zip that you downloaded and flashed for me so I can better determine what you did bud, I don't want to say hard brick because this could be battery cells going bad coincidentally
Danvdh said:
Copy and paste the name of the zip that you downloaded and flashed for me so I can better determine what you did bud, I don't want to say hard brick because this could be battery cells going bad coincidentally
Click to expand...
Click to collapse
Hello there,
Thanks for the reply. I followed the instructions as per this thread:
http://forum.xda-developers.com/showthread.php?t=2179330
The CWM mod version I got from following Step 2 of that guide, which led me to this: http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html
Afterwards, everything seemed to be working fine, so I grabbed a copy of the official CM latest nightly for my device, wiped/factory reset, and installed the ROM + gapps. After I reboot, the phone shut off, and this has been going on since. I am able to get into download mode, as I have just discovered, but I cannot get into recovery mode or turn the phone on past this mysterious grey battery icon.
Thanks for your time,
-Mike
Cryceratops said:
Hello there,
Thanks for the reply. I followed the instructions as per this thread:
http://forum.xda-developers.com/showthread.php?t=2179330
The CWM mod version I got from following Step 2 of that guide, which led me to this: http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html
Afterwards, everything seemed to be working fine, so I grabbed a copy of the official CM latest nightly for my device, wiped/factory reset, and installed the ROM + gapps. After I reboot, the phone shut off, and this has been going on since. I am able to get into download mode, as I have just discovered, but I cannot get into recovery mode or turn the phone on past this mysterious grey battery icon.
Thanks for your time,
-Mike
Click to expand...
Click to collapse
kk download you're stock firmware and flash it in odin, something went wrong my friend so you're going to have to start over
stock roms are here http://forum.xda-developers.com/showthread.php?t=1968625
the good news is download mode = soft brick so you are in luck! My guess is the ROM was corrupt or just a very horrible flash =/
Danvdh said:
kk download you're stock firmware and flash it in odin, something went wrong my friend so you're going to have to start over
stock roms are here http://forum.xda-developers.com/showthread.php?t=1968625
the good news is download mode = soft brick so you are in luck! My guess is the ROM was corrupt or just a very horrible flash =/
Click to expand...
Click to collapse
Thanks very much! I was able to use the stock firmware in conjunction with Odin to get myself back up and running!
Now the issue remains, is there any way to install CM 10~ on this device? I cannot find a proper version of CWM aside from the 'universal' one which I mentioned above, however, if I try and flash any version of CM using that recovery, it gives me a Status 7 error, which people say is due to an old recovery version. Any idea as to where I can find a working (new) version of CWM for this device?
Kind Regards,
Mike
All up to dates CWM are there:
http://www.clockworkmod.com/rommanager
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
---------- Post added at 10:38 PM ---------- Previous post was at 10:34 PM ----------
And here show to install it:
http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
I've solved the issue. Thanks for all the help.
The problem was that apparently I had an outdated bootloader which wasn't compatible with newer versions of CM and CWM. I installed the new bootloader from a thread here in the S3 forums and then flashed a new version of CWM and managed to get CM running.
I'm having new, unrelated issues now, but I'm sure I will be able to solve those.
Thanks again
[Q] Samsung Galaxy tab S "Not for sale" version with "retail mode" app, problem!
this may seem strange, but I have a Samsung galaxy tab S, demo version, with a "NOT FOR SALE" text hacked on the back, it has a "retail mode" app on it (even after factory reset) so I can't remove it, is it possible to install a (stock) ROM on this tablet?
I would imagine installing a stock firmware with odin should do the trick
same here, i flashed with stock firmware and it works no more ldu
Thanks for your response,
the devise's model is " SAMSUNG SM-T800X " and i can't find a thread on xda for a ROM for this version!
flash with t800 rom dude .
is this (ThunderRom800 ) ok? I want a easy to install ROM.
SelfAwareDroid said:
is this (ThunderRom800 ) ok? I want a easy to install ROM.
Click to expand...
Click to collapse
yes but u need a custom recovery : http://forum.xda-developers.com/gal...recovery-twrp-2-7-1-0-touch-recovery-t2817100 then u can flash custom rom
everything ok for now, sorry!
I rooted the device (with Odin), then installed the latest TWRP successfully, then went to boot menu and noticed TWRP's touch interface in scrambled (where i tap the screen isn't where it get clicked on screen, it was kindda on random places) and it filled half the screen, so for a long time I tried to tap randomly on screen and finally I could wipe the first 4 check-boxes, then i guess the battery charge went out, so after successfully wiping the device it got shut down.
now I can't go to TWRP boot menu, but I can go to other boot menu (home button + vol up + power ) , and i can't turn the damn thing off! so what should i do?
SelfAwareDroid said:
I rooted the device (with Odin), then installed the latest TWRP successfully, then went to boot menu and noticed TWRP's touch interface in scrambled (where i tap the screen isn't where it get clicked on screen, it was kindda on random places) and it filled half the screen, so for a long time I tried to tap randomly on screen and finally I could wipe the first 4 check-boxes, then i guess the battery charge went out, so after successfully wiping the device it got shut down.
now I can't go to TWRP boot menu, but I can go to other boot menu (home button + vol up + power ) , and i can't turn the damn thing off! so what should i do?
Click to expand...
Click to collapse
use openrecovery-twrp-2.7.1.1-chagallwifi
Thank you very much for your help, it did work.
SelfAwareDroid said:
Thank you very much for your help, it did work.
Click to expand...
Click to collapse
you' re welcome.
cheers
My guess this should work for the tab s 8.4 as well? Root and install a custom rom?
NJ_RAMS_FAN said:
My guess this should work for the tab s 8.4 as well? Root and install a custom rom?
Click to expand...
Click to collapse
Should but make sure your battery is at at least 80% before starting......battery dying while flashing is not good and can lead to bricked device.
pinsb said:
Should but make sure your battery is at at least 80% before starting......battery dying while flashing is not good and can lead to bricked device.
Click to expand...
Click to collapse
yup, that I know. I done many flashes before. All my devices (except wife s4) are rooted. She doesn't want me touching her phone. ha.. anyways.. this is the first time I come across retail demo item.
update.. Rooted the Tab S 8.4 and install TWRP. used custom rom and no more retail mode.. So happy.. For the price I paid, it was a steal.. lol...
Note 4 LDU
I saw this thread and I was wondering if I could flash a stock Note 4 firmware to my LDU Note 4.
RedZobe said:
I saw this thread and I was wondering if I could flash a stock Note 4 firmware to my LDU Note 4.
Click to expand...
Click to collapse
as long as its the stock rom for that particular model, i don't see why not..
NJ_RAMS_FAN said:
as long as its the stock rom for that particular model, i don't see why not..
Click to expand...
Click to collapse
What stock rom should I use?
hey
pls help .
I rooted the device with Odin, then installed TWRP manager successfully from GOOGLE PLaY and installed Thunder Rom V3 from SDcard in recovery mode and now device show new firmware ( KOT49H. ThunderRom800V3) and new device name (SM-T800 before SM-T800X) but I still have the Retail Mode .
What I've done wrong?
I am in need of some serious help. My AT&T M8 won't boot past the HTC logo screen and won't allow me to go into recovery or the hboot screen. I believe I may have wiped the OS on it; this is the only thing I can think of that makes sense. Furthermore, when I try to power down the device by long pressing the power button, it doesn't respond at all. It just stays on the logo screen. It was so bad that I just left it plugged in overnight and I don't have a clue as to how long it took to power off because I fell asleep before it did. If there's a video tutorial out there that someone has or simply a link that can show me how to install something via backdoor on this device, that would be great!
alpinesun said:
I believe I may have wiped the OS on it; this is the only thing I can think of that makes sense. !
Click to expand...
Click to collapse
Recount as best you can, all the steps that got the phone to this point.
What were you trying to do when this happened?
Also, need much more info in order to help:
1) bootloader unlocked?
2) custom or stock recovery
3) custom ROM?
4) what hboot number?
5) s-on or s-off
6) did you make a nandroid with custom recovery?
alpinesun said:
Furthermore, when I try to power down the device by long pressing the power button, it doesn't respond at all. It just stays on the logo screen.
Click to expand...
Click to collapse
Hold power and vol up for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of those buttons, and just hold vol down. Don't let go until the hboot screen appears.
Thanks already. I didn't realize I had to hold down the volume down button after it goes dark. It got me into twrp. I believe I should be good from here after I download a new rom to sideload. But to give you a run down, I was prepping the phone to sell it by wiping the data and installing the rom the guy said he wanted on it. When I was going thru the normal procedure to install the rom (wipe, flash, etc) that's when the phone started sticking on the logo screen. My assumption was that I downloaded a bad rom, so since then I've been trying to get back into twrp so I can load a new rom and finally was able to after you told me this. I'll report back if a new rom actually didn't help the situation. I only thought I wiped the OS because something similar happened with my Note when I was tinkering and that was the result.
alpinesun said:
I'll report back if a new rom actually didn't help the situation.
Click to expand...
Click to collapse
If you need any further help, please answer all the questions I previously asked.
Good luck.
redpoint73 said:
Recount as best you can, all the steps that got the phone to this point.
What were you trying to do when this happened?
Also, need much more info in order to help:
1) bootloader unlocked?
2) custom or stock recovery
3) custom ROM?
4) what hboot number?
5) s-on or s-off
6) did you make a nandroid with custom recovery?
Hold power and vol up for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of those buttons, and just hold vol down. Don't let go until the hboot screen appears.
Click to expand...
Click to collapse
So, it seems I'm still having the problem, even while trying to install cyanogen. Here are the answers to those questions...
1) bootloader unlocked?... YES
2) custom or stock recovery... TWRP
3) custom ROM?... It was a custom AOSP Rom
4) what hboot number?... 3.16.0.0000
5) s-on or s-off... S-OFF
6) did you make a nandroid with custom recovery?... It was erased
Any help you can give from this point would be awesome. Thanks again!
alpinesun said:
So, it seems I'm still having the problem, even while trying to install cyanogen.
Click to expand...
Click to collapse
Failure to flash ROMs can often be solved with fastboot erase cache, then install TWRP by fastboot again. Update TWRP version, if you are using an outdated one.
Also, if you try to flash any ROMs based on Sense software beyond version 1.x (huge majority of them are past 1.x at this point) you will likely experience extremely long boot times (10 minutes or more) and broken WiFi due to outdated firmware. But CM should be okay.
alpinesun said:
6) did you make a nandroid with custom recovery?... It was erased
Click to expand...
Click to collapse
It was erased, or you wiped it?
Okay. Do you suggest trying an older sense rom to see if it works? The last time touched the phone was when I picked up my Note 4, so I will look for something that predates that.
As for the nandroid being erased, I can only assume it was my actions that caused it to be deleted, but I don't recall intentionally doing it.
alpinesun said:
Okay. Do you suggest trying an older sense rom to see if it works?
Click to expand...
Click to collapse
Sure, it couldn't hurt. With your current firmware, you will need a ROM based on 1.x software. There aren't a heck of a lot of those left. But there are a few. GoldenEye is one I can personally vouch for, since I was running it for a while back in the day:
http://forum.xda-developers.com/showthread.php?t=2705640
But I would definitely recommend just trying fastboot erase cache and re-install TWRP first. I've lost count how many times suggesting this simple fix has helped other users here on XDA, when ROMs fail to flash.
alpinesun said:
As for the nandroid being erased, I can only assume it was my actions that caused it to be deleted, but I don't recall intentionally doing it.
Click to expand...
Click to collapse
Fair enough. Just FYI, don't do a factory reset in bootloader (in the OS settings or recovery is OK). On modded phones this may cause the internal storage to become corrupted. Nandroids have sometimes been lost this way. This may or may not be what happened to you. Just wanted to throw that out there.
Also, there has been the occasional occurrence of internal storage being corrupted, possibly by TWRP. It may not even have been something you caused.
Hi,
I have an HTC One M8 (AT&T) . I had 5.02 on it earlier today and wanted to upgrade it. I don't have service so can't use the ATT Updated. I unlocked the boot loader and loaded a boot.img. Now my phone turns on the the HTC and goes to the HTC screen. It does says that the image should not be distribute outside of HTC.
Any help in getting past this?
You didn't brick. You didn't install a ROM. You just installed the kernel when you flashed boot.img, which is like 1% of what it takes to have a working OS. A kernel is about 25 MB, where a Sense ROM is around 1.5 GB.
You're not the only person to make this mistake. But I'm at a loss to understand why folks think that a boot.img is the same as a ROM. They are 2 completely different (although related) things.
Flash the entire ROM. No need to flash boot.img seperately (it flashes with the ROM/system partition).
Also, the red text on the boot screen is perfectly normal, once you've installed a custom recovery (TWRP).
Any particular ROM you recommend? What you say makes sense, as to how I got there, I was following a set of steps.
redpoint73 said:
You didn't brick. You didn't install a ROM. You just installed the kernel when you flashed boot.img, which is like 1% of what it takes to have a working OS. A kernel is about 25 MB, where a Sense ROM is around 1.5 GB.
You're not the only person to make this mistake. But I'm at a loss to understand why folks think that a boot.img is the same as a ROM. They are 2 completely different (although related) things.
Flash the entire ROM. No need to flash boot.img seperately (it flashes with the ROM/system partition).
Also, the red text on the boot screen is perfectly normal, once you've installed a custom recovery (TWRP).
Click to expand...
Click to collapse
salevine said:
Any particular ROM you recommend? What you say makes sense, as to how I got there, I was following a set of steps.
Click to expand...
Click to collapse
Where did you get the boot.img, was it from a ROM?
What steps were you following? I know you can't link, due to not enough posts. But you can describe if its an XDA thread, describe the guide, ROM thread, or process in question. Just saying you were "following a set of steps" doesn't really tell us anything.
I actually managed to finally get it fixed. Just in case anyone else has the issue, here is what I had to do. I left it on until the battery completely died. Then I was able to finally get it on and into HBOOT. Since I had made the mistake of installing TWRP but not making a backup, I could not restore from a backup. I took the SD card out of my phone and downloaded venomROM and put it on my SD card. I then was able to get into HBOOT, Recover and install using TWRP and the ROM from the SD card. All is well now.
redpoint73 said:
Where did you get the boot.img, was it from a ROM?
What steps were you following? I know you can't link, due to not enough posts. But you can describe if its an XDA thread, describe the guide, ROM thread, or process in question. Just saying you were "following a set of steps" doesn't really tell us anything.
Click to expand...
Click to collapse
salevine said:
I actually managed to finally get it fixed. Just in case anyone else has the issue, here is what I had to do. I left it on until the battery completely died. .
Click to expand...
Click to collapse
No need to have done that (let the battery die) but I guess if it worked, power to you. I would have pointed out how to reboot, but got sidetracked when you asked for ROM recommendations, and referenced some guide, but not telling us what guide, which confused the conversation.
For future reference, next time, hold power+vol up to force a reboot (may need to hold a minute or so, in the case of stuck on HTC logo screen or similar condition). The moment the screen goes dark, slide your finger from vol up, to vol down (no need to keep holding power button at this point) and keep holding vol down until bootloader screen appears. If it doesn't, just repeat, as you got the timing wrong (either started pressing vol down to late, or let go of it too early).
Whatever guide you were following was wrong (or possibly for an older device) as you don't need to flash boot.img seperately, unless the intent is to install a custom kernel (different thing from flashing a ROM).