Ok I installed kushdeck nightly it boots perfectly but after a while it restarts and stays at the boot animation or if I reboot it myself it stays at the boot animation I'm on s-on and hboot 1.5 I have installed other rims perfectly including aokp but I can't figure this one out
Sent from my EVO using Tapatalk 2
Try using a wipe script and remember the kernel has to be flashed separately
om4 said:
Try using a wipe script and remember the kernel has to be flashed separately
Click to expand...
Click to collapse
Where can I get the wipe script do I just flash that?.....yes I always use fastboot but I will try a wipe script
Sent from my EVO using Tapatalk 2
http://forum.xda-developers.com/showthread.php?p=27166189
Still keeps freezing on the boot animation i tried the superwipe
1stloc said:
Still keeps freezing on the boot animation i tried the superwipe
Click to expand...
Click to collapse
How long does it stay on the bootscreen? Is it the "cyanogenmod" bootscreen, or the HTC one?
Sometimes it takes a while to boot up...I haven't had issues with any of my attempts, and I've done them "wrong" on purpose, to see if it makes a major difference. The only time I have issues is when I do it completely wrong and not flash the boot.img.
Are you installing other things? A different kernel as well, maybe? Might also want to try to redownload -- maybe you had a bad zip..?
That is a bit odd, but have you tried official nightly to see how it acts?
jkrlvgn said:
How long does it stay on the bootscreen? Is it the "cyanogenmod" bootscreen, or the HTC one?
Sometimes it takes a while to boot up...I haven't had issues with any of my attempts, and I've done them "wrong" on purpose, to see if it makes a major difference. The only time I have issues is when I do it completely wrong and not flash the boot.img.
Are you installing other things? A different kernel as well, maybe? Might also want to try to redownload -- maybe you had a bad zip..?
Click to expand...
Click to collapse
I have downloaded the rom many times...it stays on the cyanogenmod bootscreen...the rom it self boots but if i restart the phone it just hangs on the cyanogenmod bootscreen i have let it sit there for 30 mins already
Yea i have tried all of them
om4 said:
That is a bit odd, but have you tried official nightly to see how it acts?
Click to expand...
Click to collapse
Sounds to me like you're not doing something right. Are you sure that you're flashing the right boot.img? Take us through an exact step by step of what you're doing....this isn't a problem that anyone else is having as far as I'm aware.
Sent from my EVO using xda premium
I had this problem when I was first trying to install CM10 as well. I used TWRP as my recovery, and was HTC Dev unlocked with HBOOT 1.15 (I used the RegawMOD one-click root method)
Note: I'm not going into complete detail on all of the steps, but I'll go into detail on where I made the mistake
1. Use adb/fastboot to flash the boot.img from the CM10 zip file. Reboot into recovery.
2. Select wipe, then do a factory reset, then a system wipe, then a cache wipe, and then a dalvik cache wipe (in that order). Stay in recovery.
3. Flash CM10. Stay in recovery.
4. Flash gapps. Stay in recovery.
5. Select Reboot > system
Step 2 is where I was messing up. I wasn't doing the factory reset (or wasn't doing the resets in the right order). After that, it did take awhile for it to boot up (5-10 minutes, maybe more). It only takes that long the first time it boots, every time since has been pretty quick.
Also, I got my instructions from a youtube video, but I couldn't find it after searching for 20 minutes. Although it's late, and my brain is fried, so I might have found it and just not recognized it.
Hope this helps.
(Also, I'd suggest doing ALL of the steps over again, from the top, not just the one that you think you might have missed. I don't think that all of the steps have to be done in order, but doing some of them out of order is what was causing my issue, so better just to start from the beginning)
when i download the zip i extract the boot.img to where ever im going to fastboot it
then i superwipe my phone
i install the nightly then the gapps
after i boot to bootloader and fastboot
the phone starts up but then if i ever reboot the phone it just hangs on the boot animation
i have done this proccess with every rom and no problems just with this one
jkrlvgn said:
Sounds to me like you're not doing something right. Are you sure that you're flashing the right boot.img? Take us through an exact step by step of what you're doing....this isn't a problem that anyone else is having as far as I'm aware.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
1stloc said:
when i download the zip i extract the boot.img to where ever im going to fastboot it
then i superwipe my phone
i install the nightly then the gapps
after i boot to bootloader and fastboot
the phone starts up but then if i ever reboot the phone it just hangs on the boot animation
i have done this proccess with every rom and no problems just with this one
Click to expand...
Click to collapse
Ok. My first rule of thumb is that if you are trying multiple roms, make sure you rename the boot.img accordingly. I change the name to correspond with the date and rom (like 915cm10boot.img). I don't get them confused and they're always right.
Download the rom.
Extract boot.
Boot into recovery and wipe everything that isn't your sd card. I always do them in order from TWRP, starting from the left top. I don't superwipe, so let's skip that for now.
Install your rom and your gapps. Rom first, gapps after.
Once that's done, navigate back to the main tarp and choose the reboot option, then choose bootloader.
Fastboot flash your renamed boot.img file.
Reboot device.
Do not...do not sync/restore apps from Google during the initial setup. Just do the bare minimum that you have to to get through setup.
Reboot.
report back.
Sent from my EVO using xda premium
jkrlvgn said:
Ok. My first rule of thumb is that if you are trying multiple roms, make sure you rename the boot.img accordingly. I change the name to correspond with the date and rom (like 915cm10boot.img). I don't get them confused and they're always right.
Download the rom.
Extract boot.
Boot into recovery and wipe everything that isn't your sd card. I always do them in order from TWRP, starting from the left top. I don't superwipe, so let's skip that for now.
Install your rom and your gapps. Rom first, gapps after.
Once that's done, navigate back to the main tarp and choose the reboot option, then choose bootloader.
Fastboot flash your renamed boot.img file.
Reboot device.
Do not...do not sync/restore apps from Google during the initial setup. Just do the bare minimum that you have to to get through setup.
Reboot.
report back.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Yea I have done everything mentioned above and still get stuck there I gave up on and went to aokp and now I get the same error which I never did before so now I'm just on meanrom instead going to try again when there's new updates thanks for the help by the way
Sent from my EVO using Tapatalk 2
Related
I am s-off and using the latest 4ext recovery. I upgraded from revolutionary CMW to 4ext so i could try CM9. It was alright but nothing special. Afterwards i tried to update to the latest vitrous sense 4.0 rom and i couldn't get past with the boot animation. Every single ROM i tried has been like this. Im wiping the data before I flash and using supewipe.zip. I never faced issue with CMW is it the recovery or am i doing something wrong?
UnderZone7 said:
I am s-off and using the latest 4ext recovery. I upgraded from revolutionary CMW to 4ext so i could try CM9. It was alright but nothing special. Afterwards i tried to update to the latest vitrous sense 4.0 rom and i couldn't get past with the boot animation. Every single ROM i tried has been like this. Im wiping the data before I flash and using supewipe.zip. I never faced issue with CMW is it the recovery or am i doing something wrong?
Click to expand...
Click to collapse
have you tried using the app Flash GUI to install this ROM?
what is Flash GUI? and if its an app i cant boot into any roms right now. everything i try will only take me to the boot screen.
UnderZone7 said:
what is Flash GUI? and if its an app i cant boot into any roms right now. everything i try will only take me to the boot screen.
Click to expand...
Click to collapse
how long are you waitng at this boot screen... i know when i installed CM9 it took over 5 minutes at the boot screen to set it all up ... flash GUI is an app to flash roms from the phones ROM but you wont use that ...which part of the boot are you getting stuck at... the one with the CM9 logo and the rotating electric ? or at the first splash screen showing the htc logo?
wloftus said:
how long are you waitng at this boot screen... i know when i installed CM9 it took over 5 minutes at the boot screen to set it all up ... flash GUI is an app to flash roms from the phones ROM but you wont use that ...which part of the boot are you getting stuck at... the one with the CM9 logo and the rotating electric ? or at the first splash screen showing the htc logo?
Click to expand...
Click to collapse
Any rom i try to install in general wont work. They all take to their boot animations and then nothing i even let them try to boot untill my phone dies. I just tried flashing cm9 and that seems like the only rom which still works.
UnderZone7 said:
Any rom i try to install in general wont work. They all take to their boot animations and then nothing i even let them try to boot untill my phone dies. I just tried flashing cm9 and that seems like the only rom which still works.
Click to expand...
Click to collapse
have you tried extracting the boot.img file from your ROM and then manually flashing it? try MeanROM 2.3 as well its a new one that is ICS based and loads fairly fast ... atleast i had no issues with it...also on your first time boot make sure the phone is NOT plugged up to the data cable
i dont know if you know this but if you download the PG86IMG from Goo im you can put that on the root of your sd card which is the first thing you see when you click sd card you can run that from bootloader and reset the phone
I fixed the problem. I just had to use flash image gui.
UnderZone7 said:
I fixed the problem. I just had to use flash image gui.
Click to expand...
Click to collapse
Are you sure you are s-off? I ask because I have never seen anyone need Flash Image GUI who is.
Sent from my ICS 3VO with Tapatalk 2
coal686 said:
Are you sure you are s-off? I ask because I have never seen anyone need Flash Image GUI who is.
Sent from my ICS 3VO with Tapatalk 2
Click to expand...
Click to collapse
99% sure it says in my hboot I am. But is their any way to go back to revolutionary cwm i never had any problems with it.
UnderZone7 said:
99% sure it says in my hboot I am. But is their any way to go back to revolutionary cwm i never had any problems with it.
Click to expand...
Click to collapse
this one?
thats it but how do i flash it?
UnderZone7 said:
I am s-off and using the latest 4ext recovery. I upgraded from revolutionary CMW to 4ext so i could try CM9. It was alright but nothing special. Afterwards i tried to update to the latest vitrous sense 4.0 rom and i couldn't get past with the boot animation. Every single ROM i tried has been like this. Im wiping the data before I flash and using supewipe.zip. I never faced issue with CMW is it the recovery or am i doing something wrong?
Click to expand...
Click to collapse
4ext works great, under wipe, select wipe dalvich + cache, then the format all partitions(besides sd card) option near the bottom.
Then flash your Rom, by chance is 4extsmartflash on? That's for s on devices so turn it off if enabled, as you are s off.
Sent from my HTC EVO 3D X515m using Tapatalk 2
UnderZone7 said:
thats it but how do i flash it?
Click to expand...
Click to collapse
just to make it simple download the file ad rename it to recovery.img and move it to the same place the fastboot.exe is located... take your phone and boot into your hboot by holding volume down and then the power button.. scroll down to the fastboot option and press the power button... youll see the screen change and then plug your phone up to your computer you should see on your phone screen now the phrase "fastboot usb"... from there open up a ms-dos window and direct yourself to the directory with the fastboot.exe and recovery.img files.. then type in
fastboot flash recovery recovery.img
it should send and then write , when completed power your phone and then reboot into recovery and it should be then revclockmod version...and probs feel free to PM me
Happen before
This is something that happened me to me before, my problem was I erased a bunch of important stuff and tried to install a kernel using recovery. I'm on hboot 1.50 so yeah **** turn messy. But I unrooted, then re-rooted and used GUI to flash my kernel of any choice but ext to flash my rom. Revolutionary recovery doesn't work too good on my phone, so it also varies depending on recovery:fingers-crossed:, just word of advice do a factory reset+wipe dalvich cache(do it at least 2 times) and it has worked for me whenever I flash a new rom. Whenever you reboot give it some time and don't rush or press anything. Once your rom kicks in let it sit for at least a couple mins and then proceed with whatever you need to do. Hope this helps!
Hello,
I've been all over google and this site for the last two days trying to find a way to get my Evo 3d work! I tried searching the forum and unfortunately i kept getting server errors So i figured I would make a new thread in the hopes of figuring this out!
What happened:
I went through the rooting process, and I went to flash a ROM on to the phone and it would not load pass the HTC screen. I had a ROM on there of the stock version of the Sprint Evo 3d, unfortunately it wasn't the proper version and it did not allow 4G and such. So i tried to place another ROM on to the SD Card and flash it over, and for some dumb reason, I deleted the version of the Stock Rom that atleast enabled me to get the phone to turn all the way on. All I'm able now is to boot up to recovery, but I can't figure out what ROM to download to place on the phone to get me back to square one!!!
Help please!!
-Mike
jerseybizzle said:
Hello,
I've been all over google and this site for the last two days trying to find a way to get my Evo 3d work! I tried searching the forum and unfortunately i kept getting server errors So i figured I would make a new thread in the hopes of figuring this out!
What happened:
I went through the rooting process, and I went to flash a ROM on to the phone and it would not load pass the HTC screen. I had a ROM on there of the stock version of the Sprint Evo 3d, unfortunately it wasn't the proper version and it did not allow 4G and such. So i tried to place another ROM on to the SD Card and flash it over, and for some dumb reason, I deleted the version of the Stock Rom that atleast enabled me to get the phone to turn all the way on. All I'm able now is to boot up to recovery, but I can't figure out what ROM to download to place on the phone to get me back to square one!!!
Help please!!
-Mike
Click to expand...
Click to collapse
Hi jerseybizzle, I can certainly try to help you but you have to help me first.
1. Are you doing a factory reset and wiping dalvik cache before flashing?
2. What hboot version do you have?
3. Is your phone s-on or s-off?
4. Which rom did you try to flash that wouldn't boot?
wikdNoob said:
Hi jerseybizzle, I can certainly try to help you but you have to help me first.
1. Are you doing a factory reset and wiping dalvik cache before flashing?
2. What hboot version do you have?
3. Is your phone s-on or s-off?
4. Which rom did you try to flash that wouldn't boot?
Click to expand...
Click to collapse
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
jerseybizzle said:
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
Click to expand...
Click to collapse
If it was an ics Rom and you are having bootloops, it is most likely because you are s-on. I recommend getting s-off. The wire trick is easy to do, but you need to be careful.
http://forum.xda-developers.com/showthread.php?t=1585846
Sent from my ICS 3VO with Tapatalk 2
Did you flash the rom through fastboot? If you just booted into your recovery and attempted to flash the ICS version of that rom coming from GB it won't work since you still have S-ON and that doesn't let you flash certain things like kernels. You can still flash roms but you have to take a couple extra steps or achieve S-OFF.
To get your phone working again...
If you were just coming from a stock rooted rom before attempting to flash a new rom, simply download a stock rooted rom from the dev section, put it on your SD card, boot into recovery, wipe and reflash. Your phone should then boot up again.
Sent from my PG86100 using xda app-developers app
jerseybizzle said:
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
Click to expand...
Click to collapse
I'm guessing it was the ics version of vipermod, and since you're s-on your boot image didn't flash. So you're trying to boot an ics rom with a gingerbread kernel.
If you want to use an ics rom, you have a few choices. My favorite... Put a recovery image in the folder on your computer that has fastboot in it. Put the phone in fastboot mode and type in the command window, fastboot boot recovery.img, make sure that you name the recovery image on your comp. to "recovery.img". It should boot to recovery and you can flash away.
Something that's easier is to use 4ext recovery smart flash. I'm sure it works but I've never used it.
If you want to get back to your stock rom unrooted rom you could run an ruu.
Also, take coals advice and s-off that phone, you won't have nearly as many issues once you s-off, and you can use one of the splash screens in my Sig
flonker said:
Did you flash the rom through fastboot? If you just booted into your recovery and attempted to flash the ICS version of that rom coming from GB it won't work since you still have S-ON and that doesn't let you flash certain things like kernels. You can still flash roms but you have to take a couple extra steps or achieve S-OFF.
To get your phone working again...
If you were just coming from a stock rooted rom before attempting to flash a new rom, simply download a stock rooted rom from the dev section, put it on your SD card, boot into recovery, wipe and reflash. Your phone should then boot up again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
jerseybizzle said:
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
Click to expand...
Click to collapse
Here's an idea, get flash image GUI, its free here at xda, google it. Then use it to flash the kernel from the stock rom that you have running and reboot. This should fix your WiFi. Let me know if I'm not being clear enough.
wikdNoob said:
Here's an idea, get flash image GUI, its free here at xda, google it. Then use it to flash the kernel from the stock rom that you have running and reboot. This should fix your WiFi. Let me know if I'm not being clear enough.
Click to expand...
Click to collapse
Where would I find the stock Kernel?
jerseybizzle said:
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
Click to expand...
Click to collapse
So, it sounds like wifi turns on just fine, you just get the error when attempting to connect to a network?
Have you tried resetting your router and rebooting your phone? Maybe remove that network from your saved preferences and resign in.
Sent from my PG86100 using xda app-developers app
jerseybizzle said:
Where would I find the stock Kernel?
Click to expand...
Click to collapse
Inside the rom that you flashed, just choose that rom with flash image GUI and it'll pull the kernel out for you
flonker said:
So, it sounds like wifi turns on just fine, you just get the error when attempting to connect to a network?
Have you tried resetting your router and rebooting your phone? Maybe remove that network from your saved preferences and resign in.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
The wifi won't turn on period. I'll click the icon for the Wi-Fi to turn on, and it just says error. No option to even try to connect!
jerseybizzle said:
The wifi won't turn on period. I'll click the icon for the Wi-Fi to turn on, and it just says error. No option to even try to connect!
Click to expand...
Click to collapse
If the app that was suggested to didn't do the trick, hit the stickies in the dev section on how to flash a rom with hboot 1.5 S-ON. I recommend the fastboot method, however, if you're so inclined, you can also go the route of getting S-OFF.
Most likely, some problems occurred when you tried to flash that ROM before and broke your wifi. So, if I were you, I'd grab a ROM (that viper ics should be fine if you still got it) and flash it through fastboot using a guide in the dev section. Be sure to read and understand the guide before attempting it.
The guide would be something like this...
1. Install the appropriate drivers and place a recovery on your PC.
2. Boot into your boot loader, select fast boot, and connect your device to your PC via USB.
3. Open a command prompt on your computer, switch to the directory containing drivers/recovery image
4. Type fastboot boot thenameofyourrecovery.img
5. Install the rom as you otherwise normally would using your phone, wiping data, clearing caches, installing zip.
NOTE: The above is not a guide, just an illustration of the guide you're looking for in the dev section.
Flashing a rom by this method allows you to flash roms with non stock kernels, so you can pretty much flash any rom made for your phone. This is the method I have used since day 1 and have never experienced any problems. You may also want to look into getting S-OFF, but I can't say much about that because I haven't done it myself (being content flashing through fastboot).
Hope this helps.
Sent from my PG86100 using xda app-developers app
flonker said:
If the app that was suggested to didn't do the trick, hit the stickies in the dev section on how to flash a rom with hboot 1.5 S-ON. I recommend the fastboot method, however, if you're so inclined, you can also go the route of getting S-OFF.
Most likely, some problems occurred when you tried to flash that ROM before and broke your wifi. So, if I were you, I'd grab a ROM (that viper ics should be fine if you still got it) and flash it through fastboot using a guide in the dev section. Be sure to read and understand the guide before attempting it.
The guide would be something like this...
1. Install the appropriate drivers and place a recovery on your PC.
2. Boot into your boot loader, select fast boot, and connect your device to your PC via USB.
3. Open a command prompt on your computer, switch to the directory containing drivers/recovery image
4. Type fastboot boot thenameofyourrecovery.img
5. Install the rom as you otherwise normally would using your phone, wiping data, clearing caches, installing zip.
NOTE: The above is not a guide, just an illustration of the guide you're looking for in the dev section.
Flashing a rom by this method allows you to flash roms with non stock kernels, so you can pretty much flash any rom made for your phone. This is the method I have used since day 1 and have never experienced any problems. You may also want to look into getting S-OFF, but I can't say much about that because I haven't done it myself (being content flashing through fastboot).
Hope this helps.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I ended up finally finding a ROM (CM) that would load on to the phone. The Wi-Fi is working now!
I just need to find a fix for the camera, neither the regular nor 3D camera will function now.
jerseybizzle said:
Thanks. I ended up finally finding a ROM (CM) that would load on to the phone. The Wi-Fi is working now!
I just need to find a fix for the camera, neither the regular nor 3D camera will function now.
Click to expand...
Click to collapse
Which cm rom exactly? I thought the camera works with all the cm roms. It sounds like you still have kernel issues, and until you figure out how to flash a kernel or boot image, you'll always have these types of issues, bootloop, broken WiFi/camera. I know that the instructions that flonker gave you are intimidating but after you've done it once you'll see how simple it is.
One limitation of HTC dev unlocking is that you can't write to the boot partition from recovery, the kernel resides in the boot partition. You can, however, write to boot from within the android system. That's why flash image GUI is so handy for people with s-on and HTC dev unlocked. Just open the app, find the rom you'd like to flash and select it, the GUI will extract the kernel from the rom zip and flash it. Then you just boot into recovery and flash the same rom that you selected with the GUI. It'll flash everything but the boot image, but that's ok because you already flashed the kernel with flash image GUI. Make sure you do a factory reset and wipe the dalvik cache.
When I was s-on I always chose fastbooting to recovery, when you do that it actually loads the recovery onto the boot partition and gives you permission to write to boot, so its like flashing should be. Just wipe, flash, enjoy.
Hope this helps.
Wikd said:
Which cm rom exactly? I thought the camera works with all the cm roms. It sounds like you still have kernel issues, and until you figure out how to flash a kernel or boot image, you'll always have these types of issues, bootloop, broken WiFi/camera. I know that the instructions that flonker gave you are intimidating but after you've done it once you'll see how simple it is.
One limitation of HTC dev unlocking is that you can't write to the boot partition from recovery, the kernel resides in the boot partition. You can, however, write to boot from within the android system. That's why flash image GUI is so handy for people with s-on and HTC dev unlocked. Just open the app, find the rom you'd like to flash and select it, the GUI will extract the kernel from the rom zip and flash it. Then you just boot into recovery and flash the same rom that you selected with the GUI. It'll flash everything but the boot image, but that's ok because you already flashed the kernel with flash image GUI. Make sure you do a factory reset and wipe the dalvik cache.
When I was s-on I always chose fastbooting to recovery, when you do that it actually loads the recovery onto the boot partition and gives you permission to write to boot, so its like flashing should be. Just wipe, flash, enjoy.
Hope this helps.
Click to expand...
Click to collapse
I have been flashing roms and kernels and such for awhile on several different phones and literally almost everything you said makes no sense and that goes for the other guy 2 posts above yours. WTF is flash image GUI? Is that an app, you never even say.
The other guy is telling him to flash a rom but describes to him how to flash a recovery image to his phone...have you guys ever done this before or are you just making stuff up as you go?
flukeSG2 said:
I have been flashing roms and kernels and such for awhile on several different phones and literally almost everything you said makes no sense and that goes for the other guy 2 posts above yours. WTF is flash image GUI? Is that an app, you never even say.
The other guy is telling him to flash a rom but describes to him how to flash a recovery image to his phone...have you guys ever done this before or are you just making stuff up as you go?
Click to expand...
Click to collapse
Those guys probably don't even have EVO 3D's anymore. Do you read dates before posting? Threads a year old :screwy:
Sent from my PG86100 using xda app-developers app
RayTrue04 said:
Those guys probably don't even have EVO 3D's anymore. Do you read dates before posting? Threads a year old :screwy:
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Yes I do, I was looking for information and I read the entire thread. Just because they posted it a year ago doesn't make the info any less wrong.
Hey folks,
So the end of Q3 came with no ICS so I decided it was time to learn about modding these phones. I have modded Xboxes etc so I figured I would try to take this on.
My Phone:
AT&T MB860 bone stock with 4591 on it when I started.
I was able to unlock the phone following a tutorial on youtube. Then I tried to reflash CWM and CM7 using AUTOMATIC_UNLOCK_V4.2. Thats where things went wrong. The phone got stuck at the Dual core screen (to be honest I might not have waited 10 minutes after flashing).
So now here I am the battery is drained so I am using a cut off USB cable for power. When the phone is booting it says "unlocked" in the top left corner I can access all of the menus. When I choose recovery the phone boots into ClockWork Mod recovery. I am hoping I am half way there and the kind folks here can guide me to the finish. If not I'm open to starting from scratch whichever is going to be fastest. I'll attach a few pics for reference
Mycotopian said:
Hey folks,
So the end of Q3 came with no ICS so I decided it was time to learn about modding these phones. I have modded Xboxes etc so I figured I would try to take this on.
My Phone:
AT&T MB860 bone stock with 4591 on it when I started.
I was able to unlock the phone following a tutorial on youtube. Then I tried to reflash CWM and CM7 using AUTOMATIC_UNLOCK_V4.2. Thats where things went wrong. The phone got stuck at the Dual core screen (to be honest I might not have waited 10 minutes after flashing).
So now here I am the battery is drained so I am using a cut off USB cable for power. When the phone is booting it says "unlocked" in the top left corner I can access all of the menus. When I choose recovery the phone boots into ClockWork Mod recovery. I am hoping I am half way there and the kind folks here can guide me to the finish. If not I'm open to starting from scratch whichever is going to be fastest. I'll attach a few pics for reference
Click to expand...
Click to collapse
(I went through this today, I needed to use option 6 in automatic unlock 4.2 before I could get a Rom on my phone.) this was wrong, tried so many things I got confused, go to this thread:
[Unlocked Only][RECOVERY][2011-11-14] Custom CWM-based Recovery 5.0.2.7-atrix5 in ATRIX android development
and download one of the zipped recoveries, flash through recovery to get a modified CWM that left me install a Rom. I was stuck at the same screen as you before I did this now I'm up and running with MROM.
Your recovery is too old. Get a newer version of CWM. Try flashing this. If you can't you will have to fastboot flash a newer recovery.
Flash ROMs with CWM, not automated tools. CWM is the safest way. As soon as you get a new recovery installed create a backup. Good luck!
okay guys I'm jammed up I download the file CWM_Atrix4G_5.0.2.0 and copied it to a clean microsd. Then I went through the recovery menu
Install zip from sdcard>choose zip from sdcard>
In the next folder list I am unable to find the CWM file. Any tips on how to get the file straight onto the phones internal flash? Maybe through RSD?
Dude, you're trying to install recovery from the recovery... Doesn't really make sense, does it?
Use fastboot instead.
Avoid RSD at all costs.
ravilov said:
Dude, you're trying to install recovery from the recovery... Doesn't really make sense, does it?
Use fastboot instead.
Avoid RSD at all costs.
Click to expand...
Click to collapse
You can't do a first install of recovery from recovery. But you can update (assuming recovery is functioning - even partially).
upndwn4par said:
You can't do a first install of recovery from recovery. But you can update (assuming recovery is functioning - even partially).
Click to expand...
Click to collapse
Yeah, I know. You posted a flashable ZIP, the only one I am aware of.
I'd still recommend a standard fastboot flash though.
ravilov said:
Yeah, I know. You posted a flashable ZIP, the only one I am aware of.
I'd still recommend a standard fastboot flash though.
Click to expand...
Click to collapse
Huh? The only one? Did you search?
upndwn4par said:
Huh? The only one? Did you search?
Click to expand...
Click to collapse
No... Not really.
Hey, I said "that I'm aware of".
ravilov said:
No... Not really.
Hey, I said "that I'm aware of".
Click to expand...
Click to collapse
I have flashed recovery with fastboot exactly once - when I unlocked by bootloader. Ever since it has been flashable zips.
Okay I successfully flashed the new recovery to v5.0.2. Then I chose "apply /sdcard/update.zip" I received the "Install from sdcard complete message" I then chose "+Go Back+" then "reboot". The phone rebooted and sat at the logo with "unlocked" in the corner for a few minutes. I thought maybe I needed to clear it by pulling the battery for a few seconds, which I did. then I let it sit on my desk for 20 minutes at the logo screen.
do need to go in and clear cache? is there another file I should try to flash?
Any input would be appreciated.
Mycotopian said:
Okay I successfully flashed the new recovery to v5.0.2. Then I chose "apply /sdcard/update.zip" I received the "Install from sdcard complete message" I then chose "+Go Back+" then "reboot". The phone rebooted and sat at the logo with "unlocked" in the corner for a few minutes. I thought maybe I needed to clear it by pulling the battery for a few seconds, which I did. then I let it sit on my desk for 20 minutes at the logo screen.
do need to go in and clear cache? is there another file I should try to flash?
Any input would be appreciated.
Click to expand...
Click to collapse
You probably need to re-flash your ROM.
Wipe data, cache, Dalvik, then flash ROM.
upndwn4par said:
You probably need to re-flash your ROM.
Wipe data, cache, Dalvik, then flash ROM.
Click to expand...
Click to collapse
I ran the wipe, cache, davlik then reran the update.zip.
I am still stuck at dual core screen with unlocked the corner.
Mycotopian said:
I ran the wipe, cache, davlik then reran the update.zip.
I am still stuck at dual core screen with unlocked the corner.
Click to expand...
Click to collapse
Umm... That would just install the recovery again. You need to flash a ROM. Seems like your boot partition (aka. the kernel) is borked.
ravilov said:
Umm... That would just install the recovery again. You need to flash a ROM. Seems like your boot partition (aka. the kernel) is borked.
Click to expand...
Click to collapse
Success!
Thank you to everyone that helped.
Now that its done is there a link to outline what all my new perks and features are now that I am rooted and running?
Mycotopian said:
Success!
Thank you to everyone that helped.
Now that its done is there a link to outline what all my new perks and features are now that I am rooted and running?
Click to expand...
Click to collapse
I just installed CM7 on my Atrix last week. Don't forget to install gapps like I did. I had to install them as a zip from the recovery, but I think it's also possible to use the ROM Manager app.
Look for the Google Apps section on this thread: forum.xda-developers.com/showthread.php?t=1257574 This will have the Market (now Google Play) so you can download more apps.
After that, play with all the features! I started with Menu > Settings > CyanogenMod Settings and started playing around. Don't play with the performance settings without knowing what they do.
Also, Make a backup! Make a backup! Make a backup! It may save you when little else will.
Sent from my MB860 using xda app-developers app
Mycotopian said:
Success!
Thank you to everyone that helped.
Now that its done is there a link to outline what all my new perks and features are now that I am rooted and running?
Click to expand...
Click to collapse
Awesome! Enjoy!
I have officially stressed myself to the brink. I try to be calm but nowhere do I find how to fix my problem. I have tried flash image gui, I have tried htc dumlock, and I have also tried flashing the .img manually through fastboot usb then flashing the entire zip with twrp 2.2.2.0. Almost every time, I must recover from my TWRP and then use bootimg flasher v1.1 to stop my evo from getting stuck at the boot screen.
Everytime I attempt, I wipe the system and cache, then flash the boot.img, then flash the zip, then the gapps and reboot and it gets stuck on the splashscreen. I must note also that when I had first rooted, and installed Rom toolbox pro, I picked out a boot animation and installed it, restarted the phone, and it didnt work. BUT NOW sometimes after i flash the CM10 that random boot animation appears. WTF? even after i wipe the memory and everything. So I turned off the boot animation, and even deleted them from the phone off the app and it still comes up. I believe this is part or maybe IS the problem. But either way, I do not know how to deal with it. I have had the Cyanogenmod 10 boot animation ONCE out of the many times I have tried flashing but it was stuck on that screen forever like I have read other users have had happen. I REALLY, REALLY would like to be able to use the rom, as it has the new google now voice and all the cool features that i would like to have now that I am rooted.
NOTES:
I am running my stock rom. I have not installed any other ROMS on my phone. The backup i created was after I installed the stupid boot animation. (In case thats another problem)
When i tested the "current" boot animation from within rom toolbox pro, the normal htc evo 4g lte Sprint one loaded but yet, the retarded one i chose for ****s and giggles is what keeps loading. FML (I shouldve chose at least a cool one.)
My backup works fine. I am damn glad i made it!!!
Sorry for any grammatical errors, lowercase i's and what not. im too lazy to press the shift key sometimes. (Caps lock is broken. FML.)
Also sorry for it being so long. I am trying to be thorough to give you experts what you need to help me out.
If you need anymore info as far as detail instructions i will be happy to write back on this forum.
PLEASE do not tell me that my answer is on another forum, because I believe that it is not due to the special situation I have. I have tried looking for days for an answer.
I will be periodically checking this forum for any replies and will reply ASAP, whenever i am available.
Thank you for your time and patience!
Here is my phone's specs. I tried to get as much as possible. Again, if there is more info that would be needed I will gladly get it and post it here.
I am running on booloader:
Tampered
Unlocked
Jewel PVT SHIP S-ON RL
HBOOT- 1.19.0000
Radio- 1.12.11.0009
OpenDSP-v29.1.0.45.0622
eMMc-boot
Aug 9, 2012, 15:14:25
About Phone:
Hardware Version 0003
Android Version 4.0.4
Sorftware 2.13.651.1 710RD
HTC Sense Version 4.1
HTC SDK API level 4.24
HTCExtension_403_1_GA_22
PRI Version 2.45_003
PRL Version 25006
Anyone?
Sent from my EVO using xda app-developers app
What happens when u fastboot the kernel? Does it say success?
Sent from my EVO using xda premium
Use fastboot to flash the kernel, if you still have trouble wipe the partion and try again
Fastboot flash boot boot.img extract it from the Rom and place in adb folder.
Fastboot erase boot to wipe partition
I had problems trying out CM10 also. This worked for me.
Edit:: I'm assuming you have TWRP recovery and are unlocked before you start this...
Buy Flash GUI from app store. Worth the 99 cents!
Open it and point it to the CM10 zip. It will extract the parts it needs and flash the kernel.
Once that is done have it reboot (it prompts you) into recovery and then wipe system, do factory reset, then flash the CM10 zip and gapps zip.
Reboot one last time
The CM10 animation went on for a couple/few minutes the first time, don't panic.
You should be good after that.
Make sure to install Flash GUI again though. You will need to use it to go back to a ICS/Sense ROM later (using same method). And my guess is you might want to.
CM10 is incredible on this phone but it's not quite ready. I have tons of data connection issues and NEVER get 4G in the places where I've always had good signal. Also, the camera is just about worthless. No disrespect to the devs working on it. I'd have no idea how to work the magic they are doing and I appreciate their time.
Good luck.
I did the very same thing earlier today. I flashed CM10 without paying attention tot he fact that I was unlocked but still had S-On so the phone would continually get stuck on the boot screen. I must have reflashed and formatted with TWRP 10 times before diving into it deeper.
In terms of workflow the only way I could make it work properly was to:
1. Use TWRP to flash CM10 and gapps (just add both zips)
2. Reboot into bootmanager using TWRP.
3. Use fastboot to flash boot.imgfrom the CM10 zip (fastboot flash boot /path/to/boot.img)
If I did the boot.img first it didn't seem to work, it should so maybe that wasn't the real issue but the above process worked and I'm now running CM10.
When I fast boot the kernel everything says success with no errors
Sent from my EVO using xda app-developers app
How do you partition? Do you think that is my problem?
Sent from my EVO using xda app-developers app
You don't need to partition anything, just flash kernel and reboot
Hey guys thanks to everyone replying! I'm currently at work as a delivery driver trying to write back.... Dangerous! Lol but also I have the 5 min limit to post so I will try and do some of these methods when I get home and report my findings to you all ASAP! But to anyone with more suggestions please keep bringing Em!
Thanks!
Sent from my EVO using xda app-developers app
Hey guys its me again. I just got home and I'm dead beat tired. I had to work later than I thought. Im gonna get some sleep but once again thank you everyone for giving me some answers that I can try tomorrow! I will, without a doubt, try some of them tomorrow after my classes. But first I would like to leave you all with a VERY important question that I did not think of. Is there a stable release of cm10 that has worked for you all that I can try? Perhaps that was the problem too? I was trying the nightly release that came out October 2. Once again thank you all for replying and i will try to do this ASAP after class. Sorry to leave you guys hanging so much!
Sent from my EVO using xda app-developers app
Thing is it's a nightly, some people have flashed back to earlier versions and others upgrade with out any issues. Ymmv
padrino121 said:
I did the very same thing earlier today. I flashed CM10 without paying attention tot he fact that I was unlocked but still had S-On so the phone would continually get stuck on the boot screen. I must have reflashed and formatted with TWRP 10 times before diving into it deeper.
In terms of workflow the only way I could make it work properly was to:
1. Use TWRP to flash CM10 and gapps (just add both zips)
2. Reboot into bootmanager using TWRP.
3. Use fastboot to flash boot.imgfrom the CM10 zip (fastboot flash boot /path/to/boot.img)
If I did the boot.img first it didn't seem to work, it should so maybe that wasn't the real issue but the above process worked and I'm now running CM10.
Click to expand...
Click to collapse
Which nightly did you use?
Hey guys so I used padrino121s suggestion for flashing. At first I tried flash gui again like you had suggested but it got stuck in the boot screen. So I decided to download a different nightly release (20121002) and it flashed perfectly and everything transferred over correctly! Thank you guys so much for all of your help! Now one more question... If I decide to get a new nightly build, do I have to flash everything all over again like I had to the first time? Or because I have flashed cyanogen mod already do I just do something else to update it?
Sent from my EVO using xda app-developers app
So I've had the joy of rooting/unlocking a Thunderbolt and a Galaxy Nexus and now my DNA, so I'm vaguely familiar with how it works.
I had unlocked and rooted the phone about two months ago. I think I'm running a stock ROM with all the bloat removed I couldn't tell you exactly which one, but I think it's just the one that's deodexed with bloat removed. Had been running fine for awhile. Decided to use the Cubed DNA Kernel 2.4.2, roughly after I did this my phone would start to randomly reboot, which started about 2 weeks ago.
I didn't think anything of it up to this point and thought I'd fix it at some point. Today it rebooted once again, but this time it would never make it back into the Android OS, or if it did make it it would immediately freeze and I'd have to force reboot it. At this time I could still get into the CWR and the Bootloader. But that's really all I could do. I attempted to roll back to previous backups, this didn't work. So then I thought maybe it's the Kernel, so I was going to put it back to stock. Per the instructions I attempted to flash the boot.img file before flashing the stock kernel modules zip file.
After I did the flash for the boot.img, I can no longer get into CWR. I can still get into the bootloader, but that's really about it.
Unfortunately I have no device to fall back on. So any help or suggestions would be extremely helpful.
What happens when you try to go into recovery?
And just so you know, it was your kernel that was causing the reboots. It is a known issue with cubed kernel that dsb is working hard to fix.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
What happens when you try to go into recovery?
And just so you know, it was your kernel that was causing the reboots. It is a known issue with cubed kernel that dsb is working hard to fix.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
It basically just reboots. It says "entering recovery" at the top of the HTC boot screen, then reboots immediately after that again and attempts to boot normal, it then goes into the droid boot animation and just hangs there.
cowprince said:
It basically just reboots. It says "entering recovery" at the top of the HTC boot screen, then reboots immediately after that again and attempts to boot normal, it then goes into the droid boot animation and just hangs there.
Click to expand...
Click to collapse
Try redownloading and reflashing the boot.img in fastboot. And if that doesn't work than flash a different recovery and see if that helps.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Try redownloading and reflashing the boot.img in fastboot. And if that doesn't work than flash a different recovery and see if that helps.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Thanks Big, I was going to try it before I went to work this morning, but now it seems like the device is completely dead.
Will not power on and I get no lights when I attempt to charge it. I've tried multiple USB cables and charging methods, none result in any charging LED...
cowprince said:
Thanks Big, I was going to try it before I went to work this morning, but now it seems like the device is completely dead.
Will not power on and I get no lights when I attempt to charge it. I've tried multiple USB cables and charging methods, none result in any charging LED...
Click to expand...
Click to collapse
I should have been more clear there now that I've reread it, I never got the chance to try your suggestion, it's as if the battery died overnight and won't charge now.
cowprince said:
I should have been more clear there now that I've reread it, I never got the chance to try your suggestion, it's as if the battery died overnight and won't charge now.
Click to expand...
Click to collapse
Plug it in & Hold the power button down for about 15 to seconds for a hard reboot. If you can get it to boot, then try to flash the original stock kernal (link is located in dsb cubed kernel thread or here http://d-h.st/Ma1 ).
Once you flashed the original kernel flash dsb's other kernel stock cubed kernal here http://forum.xda-developers.com/showthread.php?t=2064066 . This one works real good, its basically stock but you can read/write and it has the hsic fix for a little better battery life.
You can use the stock cubed until the full cubed kernel is up and running with its fixes.
Hope this helps...
Jrocker23 said:
Plug it in & Hold the power button down for about 15 to seconds for a hard reboot. If you can get it to boot, then try to flash the original stock kernal (link is located in dsb cubed kernel thread or here http://d-h.st/Ma1 ).
Once you flashed the original kernel flash dsb's other kernel stock cubed kernal here http://forum.xda-developers.com/showthread.php?t=2064066 . This one works real good, its basically stock but you can read/write and it has the hsic fix for a little better battery life.
You can use the stock cubed until the full cubed kernel is up and running with its fixes.
Hope this helps...
Click to expand...
Click to collapse
Thanks Jrocker, I just hope I can get the thing to charge and/or boot when I get home.
Well it's not completely dead. Looks like I made it back into the bootloader. I can't seem to flash the boot.img file though:
fastboot flash boot boot.img
sending 'boot' (5412 KB)...
OKAY [ 0.839s]
writing 'boot'...
FAILED (remote: battery low)
finished. total time: 0.863s
So first thought would be, well ok charge the phone. However, I'm not so sure it's actually charging.
I have it plugged into the AC adapter while the bootloader is showing and it says FASTBOOT AC, however I see no solid orange LED telling me that the device is charging.
Also is there a way to push files to the SD card using fastboot. For example the stock kernel zip file?
OK I'm pretty sure I know what happened. Same thing has happened to me a few times. Apparently it only happens on some phones. I think the /data partition on your phone got borked. As in corrupted. It has done this to me about 3 times, each time I was running a custom kernel. Now that I know that my phone is one of the susceptible ones, I've been running DSB's stock system write kernel and have not had any issues since.
If this is the case, it sucks but the only thing you can do to fix it is to factory reset. When this has happened to me I have run fsck2 (disk checker) on my /data partition and it comes up with multiple errors and fixes them, but the phone still won't boot. I know dsb is aware of the issue, as are others, but there is no fix as of now besides either running stock kernels until it is fixed, or getting a new device (which may or may not be susceptible.) You can run fsck2 on your data partition and see if maybe it boots after fixing the errors, but I've had no luck 3 out of 3 times. Hope this helps.
EDIT: didn't realize that your recovery partiton got borked too, that's weird. Never had that happen. Reflash your recovery and then you should be able to go from there.
BotsOne said:
OK I'm pretty sure I know what happened. Same thing has happened to me a few times. Apparently it only happens on some phones. I think the /data partition on your phone got borked. As in corrupted. It has done this to me about 3 times, each time I was running a custom kernel. Now that I know that my phone is one of the susceptible ones, I've been running DSB's stock system write kernel and have not had any issues since.
If this is the case, it sucks but the only thing you can do to fix it is to factory reset. When this has happened to me I have run fsck2 (disk checker) on my /data partition and it comes up with multiple errors and fixes them, but the phone still won't boot. I know dsb is aware of the issue, as are others, but there is no fix as of now besides either running stock kernels until it is fixed, or getting a new device (which may or may not be susceptible.) You can run fsck2 on your data partition and see if maybe it boots after fixing the errors, but I've had no luck 3 out of 3 times. Hope this helps.
EDIT: didn't realize that your recovery partiton got borked too, that's weird. Never had that happen. Reflash your recovery and then you should be able to go from there.
Click to expand...
Click to collapse
So ultimately if I just do a factory reset and then restore one of my old backups after flashing the stock kernel boot.img I should be good then? Or should I still run fsck2?
cowprince said:
So ultimately if I just do a factory reset and then restore one of my old backups after flashing the stock kernel boot.img I should be good then? Or should I still run fsck2?
Click to expand...
Click to collapse
If you plan on restoring a backup there's no need to wipe. Recovery will wipe the data partition before it restores the old one. After that just flash your kernel and modules and you should be back up and running.
Fsck2 is not necessary. The only reason you might want to run fsck2 would be to:
1. verify that this is indeed your problem.
2.you have have a (slim) chance of fixing your data partition, saving you from wiping. Like I said I tried it and it did fix the disk errors, but still wouldn't boot.
Well it looks like I cannot do a restore of an old backup, I get an error saying that it can't mount /system
Am I doing this all in the right order?
reboot to bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
reboot to bootloader
reboot to recovery
factory reset
flash kernel
restore recovery backup
reboot
cowprince said:
Well it looks like I cannot do a restore of an old backup, I get an error saying that it can't mount /system
Am I doing this all in the right order?
reboot to bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
reboot to bootloader
reboot to recovery
factory reset
flash kernel
restore recovery backup
reboot
Click to expand...
Click to collapse
You might be able to fix that error by flashing a newer version of whatever recovery you are using. Not sure, never had that error. If you can't get your backup to flash do this (I'm assuming you already have a custom recovery installed/working since you tried to restore a backup)
1. reboot into bootloader
2. fastboot flash boot boot.img (dsb's stock kernel img)
3. reboot into recovery
4. factory reset
5. flash modules (dsb's stock kernel modules)
6. wipe cache and dalvik for good measure
7. cross fingers
8. reboot
If it doesn't boot after that I think I would reflash the rom and try again starting at step 4, but I think that^^ should do the trick.
Looks like I'm back in business, went ahead and flashed the stock system writable kernel and CWR, then the kernel module zip, a fresh ROM the Genome ROM and was good to go again.
However I still have one remaining problem. The wifi errors out and won't turn on.
cowprince said:
Looks like I'm back in business, went ahead and flashed the stock system writable kernel and CWR, then the kernel module zip, a fresh ROM the Genome ROM and was good to go again.
However I still have one remaining problem. The wifi errors out and won't turn on.
Click to expand...
Click to collapse
Glad to hear you're back up and running! Wifi not turning on is a telltale sign that you need to reflash your modules for whatever reason.
BotsOne said:
Glad to hear you're back up and running! Wifi not turning on is a telltale sign that you need to reflash your modules for whatever reason.
Click to expand...
Click to collapse
That's kinda what I had assumed.
Now I just need to hope for an AOSP ROM and some email widgets not bound to the Sense UI...
Actually no dice on the reflashing of the kernel modules. Maybe I should do the boot.img as well?
cowprince said:
Actually no dice on the reflashing of the kernel modules. Maybe I should do the boot.img as well?
Click to expand...
Click to collapse
U should do the boot.img 1st then boot into recovery and wipe cache/davik cache and flash the module. If u still having problems then get the stock DNA kernel
sent from my beastly powered viper DNA using Tapatalk 2