hboot is 1.15 i am running 1.22.651.3 i have s-on and am unlocked... i am trying to get s off i am trying to flash to cm10 but i cannot get any were can someone please point me in the right direction ... i have read and read and read and nothing adds up to what happens.. .i use clock work mod to download and install when it boots into recovery it says it installs but the screen stays black i have to hard reset (power vol down and camera) it to get anywere then it goes back into recovery and i use the back up file i had to get my phone to work... what am i doing wrong...
No offense to the developer but I would steer clear on CM10 on the Evo. It ran fine on my Nexus but it really didn't do well on my Evo. The MMS didn't work worth a darn. The biggest issue I had was no data. I reflashed it. I wiped everything. I read the instruction 20 times. It just doesn't work well and has some bugs. There seems to always be some major bugs in the AOSP line of roms. Even on the Nexus G AOKP was a constant headache. I wish I could just say do these three steps and all will be flawless. Sorry, that just isn't the case.
Sorry to point this out but this topic goes on the q&a section not on development
HTC EVO LTE
Not sure what kc is talking about I have flawless data and mms on cm10. I have 4g and it works totally fine with no data issues whatsoever. Now the op is posting in the wrong place, but I would gladly help if the post was more clear. So are you s-off or not? If not it will require you to either get s-off or flash the boot.img separately. If you are s-off try using twrp not clockwork. I have been on twrp since I got the Evo in July and have had zero flashing issues.
Sent from my EVO using xda premium
---------- Post added at 09:52 PM ---------- Previous post was at 09:48 PM ----------
I will add mms has been flawless since using Gosms as has been discussed in the cm10 thread multiple times. Not sure if mms works otherwise, but go sms solves it if it is still being worked on. If you don't like/want to us Gosms then just install it solely for mms because it does send and receive them and they show up in the stock messaging app as well.
Sent from my EVO using xda premium
i have s on and all i can access is twrp and hboot
I'm not entirely sure how you managed to put [Q] in your thread title AND ignore the box that says "Is this a question?". There is a very, very clearly labeled section for questions and answers, and your question is one of the most asked here.
Here's your two step fix:
1. Learn where to post. (please)
2. You are S-ON. The reason why you see a black screen is because S-ON users can't flash kernels from recovery. You have to do it seperately. Custom ROMs like AOSP or ROMs that use custom kernels can't be flashed normally on S-ON.
3. No, you did not read. At all. We can tell because the very first thread in the Questions and Answers forum (http://forum.xda-developers.com/showthread.php?t=1869377) says the following:
Note: To those of you with CWM Recovery, it is recommended that you use TeamWin Recovery as it is better suited for our phones.
Brick This is a very serious problem, your device is catatonic and will not respond to the usual methods of power on/off or sim-pull. In some cases the phone comes back when the battery dies and is recharged, this isn't very often. There are un-bricking tools written by OEMs when they screw up (Samsung / Motorola) and there are tools written by developers working on S-OFF. They notice a very real danger and will supply the tool just in case (this is not possible in all cases). Bricking can and will be permanent in many situations
Boot loop There a different kinds of boot loop situations (also referred to as soft brick, please do not cry brick in the forums if it is a boot loop) the most common are a mismatch of kernel and ROM.
Help, my phone is stuck in a boot loop or my phone is stuck on HTC! Not a problem at all. Hold down the power button and continue to hold it, the capacitive buttons will begin flashing and phone will reboot. After the screen turns off let go of power for one second and the press and hold power and volume down to boot into the boot loader. This is known as a simulated battery pull. HTC built this in as a fail safe to reboot your phone, and it gives us a chance to jump into the boot loader should anything go wrong. Once you have successfully made it to the boot loader read through these forms of boot loop to understand what went wrong.
Known forms of boot loop
Generic Boot loop You have a working recovery and now you have installed your first ROM. There's just one problem every ROM you try boot loops but if you restore your back up and it runs fine. This is common when you haven't taken the time to wipe your phone before you flash. You can use a wipe script to clean your phone or you can systematically wipe Dalvik, Cache, Factory Restore, and then wipe System. Now you can flash your custom ROM (HBOOT 1.15+ requires you to flash the kernel separately)
Help my phone won't boot past the splash screen similar to a generic boot loop, the most common fix is to wipe the phone before flashing your ROM. Wipe your dalvik and cache, the factory reset and wipe system. You can now flash your new ROM
Kernel Issue You have flashed a kernel that may be corrupt, originate from a different base, or is just not supported by the ROM (not really the case these days, most developers are willing to share tweaks and custom code) The result is a phone that boots to a black screen and will hang or reboot.
Note: HBOOT 1.15+ requires you to flash the kernel separately, all relevant info to do so is in this guide.
Click to expand...
Click to collapse
In the future, if you have a question, consider placing it the forum that is meant for that. Sorry to sound like an ass, but I'm in a bad mood.
thank for the help...
I am running Cyanogen Mod 10.0 on the phone for 2 weeks and not even one issue. I updated to the latest TWP before I installed the ROM. I am never going back to gay Sense. Sorry but I can't stand sense. I love the build quality of the EVO more than any other phone on the market. I really hope they come out with a Nexus Device.
Download CyanogenMod from their site and you will not have an issue.
Go to the aokp thread and at the beginning says how to push the boot.img vías fast boot after that you should be fine flashing the rom
Sent from my EVO using xda premium
Can someone delete this thread? or move it? or help this guy read instructions on how and where to post things?
Yes I'm closing this. And OP WATCH your language. YOU posted in the wrong area, not the other way around... So it's YOUR fault and No ONE herer owes you ANYTHING.
On a side note, if everyone quotes the offensive language I have to delete that too... just an FYI
Related
I was running infectedROM Sense 3.0, and I had successfully set up several other ROMs via boot manager previously. Today I just installed Playground ICS to an SD slot through boot manager and I backed up my phone ROMs boot img and clicked reboot to playground. The phone rebooted and showed the splash screen. After about 10 seconds on the splash screen, it shut off and won't turn back on. No charge light, regular boot and vol down + power both don't work. All I need to do is get to recovery, then I have to flash the update.zip for my phone ROM in the bootmanager folder. Can anyone help me get into recovery or the bootloader?
edit: I installed playground by installing the zip, and I didn't install any other mods/kernels on top of playground. On the other ROMs I have installed in boot manager, I installed them via a nandroid backup.
If you look through the last few pages of the Playground ICS thread, it is an issue and can be fixed, but its not that easy unless you know what you are doing. I hope you have a linux box.
Look at these posts for help.
http://forum.xda-developers.com/showpost.php?p=23963768&postcount=257
http://forum.xda-developers.com/showpost.php?p=23960522&postcount=250
http://forum.xda-developers.com/showpost.php?p=23968691&postcount=274
netwokz said:
If you look through the last few pages of the Playground ICS thread, it is an issue and can be fixed, but its not that easy unless you know what you are doing. I hope you have a linux box.
Look at these posts for help.
http://forum.xda-developers.com/showpost.php?p=23963768&postcount=257
http://forum.xda-developers.com/showpost.php?p=23960522&postcount=250
http://forum.xda-developers.com/showpost.php?p=23968691&postcount=274
Click to expand...
Click to collapse
looks like I've got my work cut out for me. Glad I have a dual boot with Ubuntu...anyway thanks for your help.
no problem. You might want to post anything further in that thread, you will probably get more help over there. But either way let us know if you succeed.
Sent from my Ice Creamed 3D
w0rdOo said:
I was running infectedROM Sense 3.0, and I had successfully set up several other ROMs via boot manager previously. Today I just installed Playground ICS to an SD slot through boot manager and I backed up my phone ROMs boot img and clicked reboot to playground. The phone rebooted and showed the splash screen. After about 10 seconds on the splash screen, it shut off and won't turn back on. No charge light, regular boot and vol down + power both don't work. All I need to do is get to recovery, then I have to flash the update.zip for my phone ROM in the bootmanager folder. Can anyone help me get into recovery or the bootloader?
edit: I installed playground by installing the zip, and I didn't install any other mods/kernels on top of playground. On the other ROMs I have installed in boot manager, I installed them via a nandroid backup.
Click to expand...
Click to collapse
Do you know how many times I tried to brick this thing when I was downgrading? I almost gave up! And you do it by accident? Lucky you
Edit... Sorry bout your luck, hope all goes well.
no luck so far, I opened windows sda13 thru sdk13 and none of them found the device. i guess i'll reboot and try sda13-sdz13 lol.
Just took my phone to a sprint store, after about 30 min the repair guy came back and handed me the phone. He told me he doesn't have the tools necessary to fix it so I need to come back tomorrow, but he said I'm going to have to lose all my data in order to get the phone working again using his method. I hope the emmc_recover works tonight, or tomorrow I'll probably have hboot 1.5 and s-on
Is it possible that emmc_recover won't work because I'm on the engineering hboot?
I just realized I should probably post in the downgrade hboot thread, so I'm doing that now.
EDIT: fixed my phone flawlessly, the only reason it didn't work the first time is I forgot to pull the battery before plugging it in. Thanks again for your guys' help!
Post-trial of ICS Playground
w0rd,
I had the same problem with my EVO after playing around with this as well. For all others that may have this problem here was my solution...
Symptoms:
After trying to re-flash from ICS Playground to another ROM my phone was stuck at the HTC splash screen and would not do anything. I restarted into recovery and was unsuccessful; even tried to recover to my original files and after that it passed the splash screen and then the screen went black.
Resolution:
Finally used fastboot into recovery and flashed another ROM and it worked. Morale of the story use fastboot from your computer to get into recovery and Flash your ROM.
Hope this helps...
____________________
Device: EVO 3D unlocked via HTCdev
TeamWin Recovery v1.1.1
HBOOT 1.5 (ehh)
MilkRunny 3vo CDMA v.1.13
rugbykj said:
w0rd,
I had the same problem with my EVO after playing around with this as well. For all others that may have this problem here was my solution...
Symptoms:
After trying to re-flash from ICS Playground to another ROM my phone was stuck at the HTC splash screen and would not do anything. I restarted into recovery and was unsuccessful; even tried to recover to my original files and after that it passed the splash screen and then the screen went black.
Resolution:
Finally used fastboot into recovery and flashed another ROM and it worked. Morale of the story use fastboot from your computer to get into recovery and Flash your ROM.
Hope this helps...
____________________
Device: EVO 3D unlocked via HTCdev
TeamWin Recovery v1.1.1
HBOOT 1.5 (ehh)
MilkRunny 3vo CDMA v.1.13
Click to expand...
Click to collapse
I appreciate the reply. However, the problem I had was with one specific release of playground which bricked my phone once installed. I couldn't boot into recovery or the bootloader; the screen wouldn't turn on no matter what. Fastboot won't work from this state. The only way to unbrick at that point without going to a sprint store is to use the emmc_recover tool that's part of the hboot 1.5 downgrade process (in case this happens to you or anyone else, you have to follow step 3 ONLY in the downgrade process in order to recover from bricking your phone)
w0rdOo said:
I appreciate the reply. However, the problem I had was with one specific release of playground which bricked my phone once installed. I couldn't boot into recovery or the bootloader; the screen wouldn't turn on no matter what. Fastboot won't work from this state. The only way to unbrick at that point without going to a sprint store is to use the emmc_recover tool that's part of the hboot 1.5 downgrade process (in case this happens to you or anyone else, you have to follow step 3 ONLY in the downgrade process in order to recover from bricking your phone)
Click to expand...
Click to collapse
Just curious. How do you know it was a specific release, and did it happen to anyone else? Do you know the cause of it?
wikdNoob said:
Just curious. How do you know it was a specific release, and did it happen to anyone else? Do you know the cause of it?
Click to expand...
Click to collapse
The links netwokz provided above showed me that it was a specific release. TwistedUmbrella was experimenting (and I downloaded the experimental ROM, not one of the more "stable" releases) to try to get usb mount to pc to work, and something was wrong in the build I downloaded because it wiped the emmc so I couldn't boot to the phone, recovery, or bootloader. Basically, the ROM bricked my phone in the same way that you're supposed to brick your phone when downgrading from hboot 1.5. Luckily, Twistedumbrella is a great dev who helped people who bricked their devices out. In case you're worried about running into the same issue I did, the build that bricked me is no longer online, as he's updated the experimental and regular download links.
I know it was a specific release because I wasn't the only person who reported this problem. I think it was the 1 am experimental build from 03/22. Anyway, I'm now downloading twistedumbrella's latest experimental. Back to the ROM flashing game
With boot manger they say you must be running the same os as your phone rom or you could brick it. If your phone rom is GB I would recommended running GB roms instead of ICS roms
emarlatt said:
With boot manger they say you must be running the same os as your phone rom or you could brick it. If your phone rom is GB I would recommended running GB roms instead of ICS roms
Click to expand...
Click to collapse
I haven't had any sort of issue from running an ICS ROM in boot manager while running a sense 3.0/3.5 ROM as my default OS. This reported brick was caused by one specific release of playground ICS that would have bricked my phone in the exact same way if I just installed it through my recovery instead of through boot manager. Boot manager wasn't at fault here.
This thread was resolved several days ago. Can I close this thread or something? I've never tried to before so idk how to go about doing that...Well in the meantime, I guess I can just hope nobody else decides not to read page one before posting...
To summarize:
Rogers EVO 3D GSM
No SIM Card currently in the phone
Had Stock ICS Update
Rooted the phone, causing it to become stuck in an irreversible restarting pattern
Phone (if left alone for a while) will turn itself off within 4-6 minutes, and restart. It will repeat. If it is plugged-in and charging, it (occasionally) does not turn off. If the music player is playing in the background, it will not turn off.
Problem will persist even if the SD Card is not present.
Have tried multiple solutions (see page 2) which haven't worked.
Could really use some help!
Hi there, I was hoping that the more experienced phone users here could help me with my problem.
My phone is an EVO 3D (Rogers GSM). A while back, I decided to try and root my phone (I had the ICS update at the time). I managed to S-OFF it and later unlock it, but I had a lot of trouble rooting the phone through conventional guides.
In trying to root my phone, it became stuck in a boot loop that would cause it to turn on, flash the HTC logo, but then turn off and repeat the process. This was a really annoying issue for me, that I couldn't resolve until as a last-ditch effort, I managed to install a stock RUU and fix the problem.
Finally, I was able to root the phone last week. But as soon as I did so, it began performing erratically again. This time, the phone would turn itself off and turn back on (and repeat the process infinitely) if I left it alone for 5-7 minutes.
I tried everything I could think of to fix the problem, even wiping the partition caches/dalvik drives and factory resetting it multiple times. But even with all that, it wouldn't resolve the issue. I heard that the SD card could've been the root of the problem, but even after taking it out the problem still occurs. I've also tried factory resetting it without the SD card, but to no avail.
So I decided to install my first ROM; Viper3D (1.0.0-Multi-8_14).
I was successful in installing it, and the new software was great, but unfortunately, the issue still carried over. Unless I was constantly doing something on my phone, the phone would shut reboot after 5-7 minutes. And it would keep repeating without end. More factory resets would not do anything, and I find myself unable to install Stock ROMs now.
A sort of "temporary" fix (when I want to keep the phone on for a bit) is to keep the music player playing. As long as a song is playing (even if the volume's off), the phone won't reboot.
Nothing else works.
I'm really at my wits' end here, and I hope that someone can help me with my problem. If you have any further questions you need answered before you can help me, by all means ask.
(Also, I'm not sure if this has any bearing on the issue, but my HBOOT downgraded after the root from 1.58 to 1.49. Could that be related to my problem at all?)
Thank you very much for your time.
ReversaI said:
Hi there, I'm relatively new in terms of anything phone-related, so I was hoping that the more experienced people here could try to help me with my issue.
My phone is an EVO 3D (Rogers GSM). A while back, I decided to try and root my phone (I had the ICS update at the time). I managed to S-OFF it and later unlock it, but I had a lot of trouble rooting the phone through conventional guides.
In trying to root my phone, it became stuck in a boot loop that would cause it to turn on, flash the HTC logo, but then turn off and repeat the process. This was a really annoying issue for me, that I couldn't resolve until as a last-ditch effort, I managed to install a stock RUU and fix the problem.
Finally, I was able to root the phone last week. But as soon as I did so, it began performing erratically again. This time, the phone would turn itself off and turn back on (and repeat the process infinitely) if I left it alone for 5-7 minutes.
I tried everything I could think of to fix the problem, even wiping the partition caches/dalvik drives and factory resetting it multiple times. But even with all that, it wouldn't resolve the issue. I heard that the SD card could've been the root of the problem, but even after taking it out the problem still occurs. I've also tried factory resetting it without the SD card, but to no avail.
So I decided to install my first ROM; Viper3D (1.0.0-Multi-8_14).
I was successful in installing it, and the new software was great, but unfortunately, the issue still carried over. Unless I was constantly doing something on my phone, the phone would shut reboot after 5-7 minutes. And it would keep repeating without end. More factory resets would not do anything, and I find myself unable to install Stock ROMs now.
A sort of "temporary" fix (when I want to keep the phone on for a bit) is to keep the music player playing. As long as a song is playing (even if the volume's off), the phone won't reboot.
Nothing else works.
To summarize:
Rogers EVO 3D GSM
Had ICS installed before root
Rooted, now phone is stuck in irreversible restarting pattern
Problem persists even without SD Card
Now using Viper3D ROM, but the problem remains
Could really use some help
I'm really at my wits' end here, and I hope that some of you can help me with my problem. If you have any further questions you need answered before you can help me, by all means ask.
(Also, I'm not sure if this has any bearing on the issue, but my HBOOT downgraded after the root from 1.58 to 1.49. Could that be related to my problem at all?)
Thank you very much for your time.
Click to expand...
Click to collapse
Sounds like a possible bad flash, you are obviously using the stock kernel, did you flash the new firmware, check setting about phone and will see baseband etc, that will tell if you have flashed the correct firmware, I too am with rogers. also using viper rom multi, hboot is the same and I have no such problem, here a screeny baseband, never mind the kernel
Please don't quote an op of that size next time but I'm on the correct firmware on my CDMA device and reboots happen occasionally it is most likely the ics update in general or just the kernel try a different one
Sent from my PG86100 using xda premium
No, mistake using tapatalk on my phone, anyways as I am a gsm phone and you already have a thread opened, wait for an answer from someone as I have no experience with cdma evo's, I would advice you to put more info as what rom you are using, hboot, firmware and service provider
sent on my Evil Evo running the special sauce kernel
It says:
UNLOCKED
SHOOTER_U PVT SHIP S-OFF RL
HBOOT-1.49.0008
RADIO-11.25.3504.06_M
OpenDSP-v02.6.0.2226.00.0202
eMMC-boot
Jul 15 2011, 14:39:25
Kernal Version
3.0.16-ge733189
[email protected] #1
SMP PREEMPT
(everything else is identical to yours, I think)
Baseband Version
11.77.3504.00U_11.25.3504.06_M
Build Number
1.11.401.110 CL68035 release-keys
Browser Version
WebKit/534.30
Yes, new firmware, what I would try is in recovery wipe all partitions except sdcard, wioe dalvik and cashe and factory wipe, then reflash the rom, I do have a custom kernel which might interest you, I do know that some people have had issue's with the viper rom, pm me if you want more info
sent on my Evil Evo running the special sauce kernel
Could you please help provide some step-by-step instructions, assuming you can remember them? Sorry. D:
Ok, 4ext recovery is hopefully what you have installed on your rooted phone? Have you made a nandroid back up of your existing rom?Boot into recovery you will see wipe and format, press that and you should see down near the bottom format all partitions except sdcard, press that also on that screen you will also see wipe dalvik & cashe and factory wipe. Then install zip from sd card and find the rom zip and flash, and wait, now just to let you know all your data will be erased, so contacts should be back up with gmail
sent on my Evil Evo running the special sauce kernel
I have ClockworkMod, actually. o-o
Should I get 4ext instead?
ReversaI said:
I have ClockworkMod, actually. o-o
Should I get 4ext instead?
Click to expand...
Click to collapse
yes that could be why you have an issue, 4ext is much better and prefered
Is there a way to get rid of one and add the other? Like, flash a new recovery or something?
Since your phone is rooted, you can just use the 4ext app to install the recovery. See my Web signature for a link to the free version.
Read, Search, Read again, ... Then Ask with Tapatalk 2
ReversaI said:
Is there a way to get rid of one and add the other? Like, flash a new recovery or something?
Click to expand...
Click to collapse
I believe if you install 4ext it over rides cwm but it was months ago since i did the upgrade, viper rom has an aroma installer which works much better with 4ext recovery, who rooted your phone?
flashallthetime said:
I believe if you install 4ext it over rides cwm but it was months ago since i did the upgrade, viper rom has an aroma installer which works much better with 4ext recovery, who rooted your phone?
Click to expand...
Click to collapse
It will overwrite, so no need to erase first.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Still working on it...
ReversaI said:
Still working on it...
Click to expand...
Click to collapse
yap it;s so easy just read the recovery b4 you make any selection and take your time
---------- Post added at 11:50 PM ---------- Previous post was at 11:47 PM ----------
coal686 said:
It will overwrite, so no need to erase first.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
us old folks forget things:laugh: first sign of dementia :laugh::laugh::laugh::laugh::laugh::laugh:
---------- Post added at 11:57 PM ---------- Previous post was at 11:50 PM ----------
coal686 said:
It will overwrite, so no need to erase first.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
flashallthetime said:
yap it;s so easy just read the recovery b4 you make any selection and take your time
---------- Post added at 11:50 PM ---------- Previous post was at 11:47 PM ----------
us old folks forget things:laugh: first sign of dementia :laugh::laugh::laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
i'll give you the apn's for rogers as I remember them by heart
Name rogers
apn rogers-core-appl1.apn
mmsc http://mms.gprs.rogers.com
mms proxy 10.128.1.69
mms port 80
apn types default,supl,mms
those are the settings for mobile and mms
Ok here is the deal you flashed Vipers ics rom unless you flash the latest kernel from that other guy you are going to experience random reboots.
So my suggestion is go download that other guy's kernel and install it.
spirithandler said:
Ok here is the deal you flashed Vipers ics rom unless you flash the latest kernel from that other guy you are going to experience random reboots.
So my suggestion is go download that other guy's kernel and install it.
Click to expand...
Click to collapse
gave him it already:good:
List of attempted solutions that have not worked:
Wiping everything (and formatting it) except for SD Card.
Wiping (and formatting) the SD Card
Installing a new ROM
Flashing a different kernel
Factory Resets
Wiping Dalvik & Cache
Wiping Dalvik/Cache BEFORE & AFTER installing a ROM
Stuff I haven't tried:
Re-locking the Phone
Reinstalling a stock RUU (not ROM)
Unrooting
Welcome to the world of the EVO 3D. Hate to be the one to say this but it's just one of those 3ds. Mine had random reboot problems and lockups no matter what ROM, kernel, firmware, root access, anything. Just happens to a lot of them. Some people report success with relocking and unlocking the bootloader and making sure you're S-Off but I've tried it all.
Maybe that's not the case for you but it seems to be for a lot of people.
You can follow me on Twitter - @NotSo1nter3stin
I was running CM10 experimental (supposedly stable) build and was having way too many issues: reboots 5+ times a day, random freezes requiring hard reboot, etc etc. I tried uninstalling latest apps...nope. Tried fixing permissions...nope. Finally decided to reinstall the ROM. Used CWM wiped all 3 times, went to istall from zip, couldn't find the ROM anywhere. I installed an older ICS ROM I found in there and it did it's thing until it was time to boot up...now it's stuck in boot loop. I tried removing battery, turning off with both buttons, connecting to usb...not recognized. It just keeps going thru the booting process until it says "Have a nice day!" and then starts over. How do I get in to fix this? I'm screwed....and of course use my phone all day for business......sheesh. Are there ANY JB ROMs out there that are actually stable...like in real life?
Love this site, love all of you helpful folks....pulling my hair out at this point...;-(
You're kinda asking a lot since jb has to be ported over at the moment which naturally leads to glitches such as the restarts. This is the price you pay to run jb months and months before the note is officially updated. at which time the source code will be come available and we will have rock solid jellybean builds. Until then we take what we get. Run the latest release candidate of cm9 until then if you want something super stable.
Also don't you have a backup you can restore? I'm not allowed to feel sorry for you if you never backed up your device.
Sent from my SAMSUNG-SGH-I717 using xda premium
Thanks for the reply JR, your statement " jb has to be ported over at the moment which naturally leads to glitches such as the restarts" is Greek to me. Are you saying that since it is not an official JB update, there will always be glitches? um...ok.
Yes, I have a few backups in there...but as I said, it is stuck in opening boot loop and I don't know how to get in there to restore or flash another ROM. I may be missing a simple fix here but until I know what it is, I don't know what it is. I have used search under boot loop, for an hour and have not found one thread explaining how to get out of it.
Hopefully someone will excuse my ignorance and point me to a thread or explanation of how to get past the boot loop.
Cheers
do you know how to boot into recovery?
if you can, then do that, and restore one of your backups..
if you dont know how to boot into recovery, you shouldn't be flashing roms until you do
AFAIK that means pressing volume up, home, and power until recovery lights up. Done that many times and all I get is the intermittent vibe, no flash, no screen at all.
I've poured over threads and google all day...no love. Just people telling me to restore my backups...gee thanks.
I CAN get it into Odin....can I flash a ROM from there? I followed one tutorial but when selecting a ROM, it wanted a tar file and I either had the ROM zip or unzipped, a bunch of folders with no tar file in any of them.
I'm not a moron, just screwed myself somehow and am looking for some help fixing it. I thought that's what these forums were for.
hold volume up and down and power at the same time; after the first "samsung" on the screen, release the power button, and keep holding the volume up and down, until recovery appears...
XDA is a development forum, not a newbie forum, and there is an assumption that people who flash stuff to their phones will have the basic knowledge to know how to recover from some of the problems that arise when you do something to your phone that requires the knowledge on how to fix things
The fact that you dont know how to get into recovery properly tells me you didnt bother to read and study enough on how to recover from a problem if you have one, sort of like trying to replace your water pump without actually practicing on a car..
search the forums if you need to find .tar files to restore your phone via Odin back to stock; there are several posts and threads that will show you how, but, try to recover your back up first
This ^^^^^. You have jumped into the deep end without knowing how to swim. Watch videos, read how-to's and look up words if you don't understand them. A basic knowledge of computer hardware and how a computer works pre-boot will also go a long way
redman9 said:
Thanks for the reply JR, your statement " jb has to be ported over at the moment which naturally leads to glitches such as the restarts" is Greek to me. Are you saying that since it is not an official JB update, there will always be glitches? um...ok.
Click to expand...
Click to collapse
It means there is no official jelly bean for the note at this time. Our devs have to take jelly bean code and modify it to work on the note which generally means a few hickups here and there.
Sent from my SAMSUNG-SGH-I717 using xda premium
Well thank you all for the help you have given. I was not releasing the power button after the first Samsung flash and thus not finding recovery. I have a functioning phone now, at least. I do, dig deep trying to find answers, and only post when I am truly stuck.
glad you got it fixed!
Hey all,
I should be upgrading my EVO OG to the new LTE model late next week. But I just wanted to get some of the basic questions out of the way. I'm sure there's already existing threads like this, but the forums can be difficult to search sometimes. So apologies if this stuff has been answered 20 times already.
1. Is root achievable on all known versions of the stock OS?
2. S-off is limited to Hboot x.15 and earlier correct?
3. Since the batter is not removable how do I force the phone off in case of a boot loop or other problem
4. Is the partition mod available for this phone? It was a very useful tool with my old Hero and the EVO OG.
5. What is the preferred recovery?
6. Are there any details that I should know about or fixes I should apply right away?
Thanks for answering these questions guys. Again I apologize if this stuff has been answered before.
1. So long as the hboot can be unlocked the phone can be customized.
2. S-OFF is only available for hboot 1.12 and the is a toolkit being worked on right now for downgrade. It's been achieved and is being refined.
3. Hold power for 10 seconds and phone will reboot.
4. Not familiar with the particular mod you mentioned.
5. Twrp by TeamWin, right now there are a few issues with the latest 2.3 but 2.2 is still available.
6. Only issue is that unlocked phones with HBOOT 1.15 and higher must flash the kernel separately, there are several methods of doing so. Check my thread Don't Panic for all kinds of info
Brian419 said:
Hey all,
I should be upgrading my EVO OG to the new LTE model late next week. But I just wanted to get some of the basic questions out of the way. I'm sure there's already existing threads like this, but the forums can be difficult to search sometimes. So apologies if this stuff has been answered 20 times already.
1. Is root achievable on all known versions of the stock OS?
2. S-off is limited to Hboot x.15 and earlier correct?
3. Since the batter is not removable how do I force the phone off in case of a boot loop or other problem
4. Is the partition mod available for this phone? It was a very useful tool with my old Hero and the EVO OG.
5. What is the preferred recovery?
6. Are there any details that I should know about or fixes I should apply right away?
Thanks for answering these questions guys. Again I apologize if this stuff has been answered before.
Click to expand...
Click to collapse
1. Yes u can root
2. S-off for all hboot's is possible now. Making it easier for the non-dev masses is a wip.
3. Boot loops or freezes never happen to me like on og EVO. But to simulate a battery pull hold down power for 10 seconds and wait til capacitive buttons stop blinking to release. To boot into bootloader hold power and volume down.
4. Not sure. Never had a use for it. Will need to check and get back to u.
5. Team Win Recovery Project TWRP. CWM does not agree w EVO LTE. Likes to corrupt misc/partition.
6. The multitasking mod is absolutely necessary for me. But I use Flex360's stock w/ goodies rom where it is baked in. There's another mod by zeppelinrocks that works as well.
Hope that does u well.
Thanks for the answers, I'm this will come in handy once I get the phone and start playing around with it.
I haven't heard of the multitasking mod, I'll have to look that up.
The partition mod I mentioned was made by Firerat a few years back. I used it on my old Hero and EVO OG to change the size of the system, data, and cache partitions. Here's link to the EVO version: http://forum.xda-developers.com/showthread.php?t=855424&highlight=firerat
Here's one I forgot. To boot into recovery when the phone is off we press power and volume down like with other devices? Or is that changed with the EVO LTE?
Brian419 said:
Thanks for the answers, I'm this will come in handy once I get the phone and start playing around with it.
I haven't heard of the multitasking mod, I'll have to look that up.
The partition mod I mentioned was made by Firerat a few years back. I used it on my old Hero and EVO OG to change the size of the system, data, and cache partitions. Here's link to the EVO version: http://forum.xda-developers.com/showthread.php?t=855424&highlight=firerat
Here's one I forgot. To boot into recovery when the phone is off we press power and volume down like with other devices? Or is that changed with the EVO LTE?
Click to expand...
Click to collapse
Most of the custom roms will have improved multitasking built in so you shouldn't have to worry about that.
You won't need the partition mod, this phone is a beast!!
The recovery entry procedure is the same as before.
Thanks cruise!
I figured that with the amount of memory the device has I wouldn't need to repartition. But it's been such a useful tool I thought I'd ask about it.
Is there a guide in the Don't Panic thread or anywhere else that explains flashing methods in detail? I've always been able to do everything through recovery and it seems that this device requires more use of Fastboot.
If I'm understanding what I've read correctly, we download a ROM and extract the boot.img. Flash the ROM through recovery then use Fastboot to flash the boot.img? What about just flashing a stand alone kernel?
You guys don't have to explain everything here. A link to a thread would be enough.
Again thanks for the help. All this info will come in handy soon!
Brian419 said:
Thanks cruise!
I figured that with the amount of memory the device has I wouldn't need to repartition. But it's been such a useful tool I thought I'd ask about it.
Is there a guide in the Don't Panic thread or anywhere else that explains flashing methods in detail? I've always been able to do everything through recovery and it seems that this device requires more use of Fastboot.
If I'm understanding what I've read correctly, we download a ROM and extract the boot.img. Flash the ROM through recovery then use Fastboot to flash the boot.img? What about just flashing a stand alone kernel?
You guys don't have to explain everything here. A link to a thread would be enough.
Again thanks for the help. All this info will come in handy soon!
Click to expand...
Click to collapse
Yep, you've got it. This thread outlines the process of flashing via fastboot as well as some other options. The same applies to flashing kernels with a ROM or standalone.
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
Some roms like MeanRom, have written a boot script to automatically install the kernel when the rom installs so no need to fastboot the kernel with MeanRom. Fastbooting kernels is only needed if you are s-on. There has been a major breakthrough in achieving s-off in the last couple of days and they are working on a refined method for everyone's use.
Sent from my A500 using Tapatalk
cruise350 said:
Fastbooting kernels is only needed if you are s-on.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Good to know, I was under the impression that it didn't matter if you were s-off or s-on.
Brian419 said:
Good to know, I was under the impression that it didn't matter if you were s-off or s-on.
Click to expand...
Click to collapse
That is one of the benefits of being s-off, you can write to boot partitions.
Sent from my icrap 2 using Tapatalk HD
Well I think I'm set. I've been checking other threads and reviewing various guides and descriptions. Provided all goes well and I get the phone next week I should be able to do everything I want with it.
If I have anymore questions I'll be sure to post them.
Again, thanks for taking the time to answer my questions, I really appreciate it
Update: I got my LTEVO today. Rooted, unlocked, and flashed MeanROM with no serious problems.I just wanted to thank you guys again, the info you gave me really helped.
So thanks!
Happy new owner of Amaze after three plus years on my Nexus One.
My device is unlocked, rooted, with S-On.
I purchased and successfully used 4ext, tried two CM ROMs in the last week.
Before trying these Roms, I Nandroid backed up the ROM installed on the phone when I first got it, which was running ICS 4.0.3 / Sense 3.6. (Didn't like Sense UI - was dissatisfied with one UI over another); I like the mimimalism of the CM ROM, as I've gotten used to CM7 on my Nexus one.
Anyways, settled on a CM10 ROM. This too is backed up in addition to the first Sense Rom. Man.... wish the audio skip wasn't there when playing music and was really not thrilled with low speaker volume after putting up with that on my Nexus One for years.
So I decided to try CM9.
Downloaded a CM9 zip from Goo and the correct Gapps.
Before asking for help, I have Googled several variants of my problem until I see purple links highlighted: translation, I have not been lazy to not try and look and find a solution - the links on the page aren't blue anymore, but purple because I looked and read those. I have seen plenty of threads describing my problem; maybe I've overlooked something , but this is the first time in years I have decided to ask for help. Moreover, I spent a good week bookmarking over 40 threads - organized into specific headings - in order that I could fast search for typical problems like I have now. Hate being defensive, but I see the last couple years the landscape is rife with folks rightfully being told to search before asking questions.
'nuff talk, here's the problem.
I placed the CM9 and Gapps thread onto my internal sd card as usual, then booted into recovery, into 4ext no problem. Prepared to wipe "data/factory rest/wipe and wipe cache, wipe dalvik cache".
This is what I did different from previous flash. After wiping data/factory reset... I choose "format all partitions (except sdcard" I had read enough tutorials to see that was an additional option to the wipe cache/wipe dalvik cache. Also, I was prompted to - (and this was maybe the stupid thing I did differently) - prompted with an option to uninstall smartflash. I choose the tick box... big no-no? (But I have seen in several repeated attempts to recover and restore either Rom back up, the option to "enable or disable" smartflash.
So maybe it never was actually uninstalled from 4ext? since I can see it as an option when I return to recovery. Of course I have done this after my first attempt to reboot - after installing CM9... which is described next
So after wiping data/factory reset and "format all partitions (except sdcard" ...then I installed the CM9 zip and the gapps zip, then selected reboot.
Upon selecting 'reboot' - got the infamous HTC splash screen. Then I calmly read many threads, thinking I'd solve the problem.
So far, here's what I tried as an attempt to fix/restore or learn something useful that will help me with any future steps i need to take.
1) I tried to reflash the CM9 zip. (Still did the wipe/rest but then wiped cache/dalvik cache" (no change, got splash screen)
2) Tried to restore either back up a couple times. (Each time did the wipe/reset but then wiped cache/dalvik cache" (no change, got splash screen)
3) Tried to reflash the 4 ext zip. (Hmm... won't install it aborts installation)
4) I can toggle usb storage
5) Looked at all the options within the 4ext UI just to be a 'rat in the maze' and get familiar with all the options so when i ask fort help i can perhaps navigate their faster with some confidence.
6) Went to sleep at 4am... not complaining at all.. we all have done this playing with these devices. This is just an inconvenience, I get it. I'll be putting my sim card into my Nexus one to be phone functional today while I stay on the road to figuring this out. (I know I need a 4g sim card if I want to use wifi callling on my Amaze.... but I don't care about that right now)
7) Fully charged Ruby just in case battery power could be an issue. Tried to reflash again this morning. No dice.
I know there's an answer. I know I have probably read the answer.. or the steps I need to take are in a thread somewhere... but I am a rat in a maze and don't know where to turn.
Thanks fellas.
Ed
Instead of wiping
additonal info/may help
Update:
I'm still reading, and I just read:
"There are some ROM specific files on the SDcard but a full wipe (all partitions except sdcard) clears them too"
This seems to say it was wrong to 'wipe all partitions except sdcard'. Was this cause of my problem?
Also:
1) I have enabled "smart flash" under the option. (so I assume smartflash was never uninstalled)
2) Looking in the 4-ext "boot_backup" folder. I see boot.img files. There are three new ones that were added after my problems started.
I just read:
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just what thee name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of something called a Linux kernel. This means that your bootloader boots the Linux kernel and the hardware of the device. The Linux kernel then boots the Android OS. The kernel is also the connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on the system partition you will have troubles like Wifi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for the ROM or you will more than likely have troubles.
3) Is the wrong boot.img being appplied and causing the splash screen issue?
Thanks...
discslinger said:
Update:
I'm still reading, and I just read:
"There are some ROM specific files on the SDcard but a full wipe (all partitions except sdcard) clears them too"
This seems to say it was wrong to 'wipe all partitions except sdcard'. Was this cause of my problem?
Ed
Click to expand...
Click to collapse
do a full wipe from 4ext recovery,reflash cm9 and gapps,
and for splash screen,you are missing kernel as you are S-ON,use hasoon tookit to flash your kernel here
http://forum.xda-developers.com/showthread.php?t=1493905
read above mentioned thread instructions completely...and for your kernel,its in your cm9 zip file named as boot.img,extract it and you will find it...
if i've helped you,don't forget to hit the thanks button
---------- Post added at 09:59 PM ---------- Previous post was at 09:00 PM ----------
discslinger said:
3) Is the wrong boot.img being appplied and causing the splash screen issue?
Thanks...
Click to expand...
Click to collapse
thats what i am talking about.. glad to see a good reader
Read the cm9 thread (just after the last release date). I believe cm9 is messed up. Missing or a bad boot.IMG. there are steps there to fix.
Sent from my HTC_Amaze_4G using xda app-developers app
Thanks guys!
Fixed.:good: