ok, this is my first post, and yes, i have googled for a day and a half and havent found anything similar, although it might be my wording. here it goes.....
i bought a MyTouch 4g Slide on craigslist and it was working. i started the rooting process using the revolutionary method. i discovered i couldnt get perm boot because of my hboot version 1.45.0013.
i moved on to try and root an alternate way, but wasnt sure how to proceed after getting temproot.
in the process i managed to flash the kernel (worst idea ever) in fastboot, which broke the boot process, it would power on, splash, then a black screen.
i then used the all in one tool by hasoon2000 v2.0 to flash the CM recovery, i could get to the recovery but nothing would happen when i selected any of the options (i think we all know why)
i searched and found stock recovery, kernel and system images and tried to flash them but no dice.
when booting it hangs at the splash screen, when i go into hboot and go to recovery, it reboots and then goes to recovery, but i see the download screen briefly then goes to a red triangle with an exclamation point over a phone.
the problem is, at least i think, is that i cant format \data and \system to flash the stock images i have.
any ideas?
rflores3686 said:
ok, this is my first post, and yes, i have googled for a day and a half and havent found anything similar, although it might be my wording. here it goes.....
i bought a MyTouch 4g Slide on craigslist and it was working. i started the rooting process using the revolutionary method. i discovered i couldnt get perm boot because of my hboot version 1.45.0013.
i moved on to try and root an alternate way, but wasnt sure how to proceed after getting temproot.
in the process i managed to flash the kernel (worst idea ever) in fastboot, which broke the boot process, it would power on, splash, then a black screen.
i then used the all in one tool by hasoon2000 v2.0 to flash the CM recovery, i could get to the recovery but nothing would happen when i selected any of the options (i think we all know why)
i searched and found stock recovery, kernel and system images and tried to flash them but no dice.
when booting it hangs at the splash screen, when i go into hboot and go to recovery, it reboots and then goes to recovery, but i see the download screen briefly then goes to a red triangle with an exclamation point over a phone.
the problem is, at least i think, is that i cant format \data and \system to flash the stock images i have.
any ideas?
Click to expand...
Click to collapse
If you get recovery back on there. Trackpad is what selects options in recovery. Then you can wipe and flash whatever you want. Stop using power
And if your not rooted yet or whatever because the post is worded funny, you might want to follow on through with rooting so you can do a manual format of everything
Sent from my myTouch_4G_Slide using Tapatalk 2
strapped365 said:
If you get recovery back on there. Trackpad is what selects options in recovery. Then you can wipe and flash whatever you want. Stop using power
And if your not rooted yet or whatever because the post is worded funny, you might want to follow on through with rooting so you can do a manual format of everything
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
you are a genius. i was able to get recoveyr back on there and wiped. trying to load the PG59img.zip now, well see how that goes.
rflores3686 said:
you are a genius. i was able to get recoveyr back on there and wiped. trying to load the PG59img.zip now, well see how that goes.
Click to expand...
Click to collapse
no dice. still hanging at the boot screen.
im using PG59IMG_Doubleshot_TMOUS_1.63.531.2_Radio_11.59.3504.00_11.16.3504.20_2_release_245247_signed.zip changed the file name to PG59IMG.ZIP, HBoot picks it up and loads. when you reboot, the t-mobile mytouch 4g slide screen hangs.
any other ideas?
update:
tried to flash from recovery. at first zip file would abort installation. this time i used update-cm-9.0.0-alpha4-doubleshot-signed.zip, renamed to update.zip. ran update install from recovery. it completed, upon restart, hangs at the same screen.
update2:
holy crap i got it!
i had to manually flash the kernel from the zip using fastboot.
rflores3686 said:
no dice. still hanging at the boot screen.
im using PG59IMG_Doubleshot_TMOUS_1.63.531.2_Radio_11.59.3504.00_11.16.3504.20_2_release_245247_signed.zip changed the file name to PG59IMG.ZIP, HBoot picks it up and loads. when you reboot, the t-mobile mytouch 4g slide screen hangs.
any other ideas?
update:
tried to flash from recovery. at first zip file would abort installation. this time i used update-cm-9.0.0-alpha4-doubleshot-signed.zip, renamed to update.zip. ran update install from recovery. it completed, upon restart, hangs at the same screen.
update2:
holy crap i got it!
i had to manually flash the kernel from the zip using fastboot.
Click to expand...
Click to collapse
Yeah s-on users have to fastboot flash the kernel somehow. I've never had to do it and never read up on it but I should have told you since I was aware. My bad but glad your running now
Sent from my myTouch_4G_Slide using Tapatalk 2
Just use juopunutbear and gain s-off.
blackknightavalon said:
Just use juopunutbear and gain s-off.
Click to expand...
Click to collapse
thanks for the suggestion. ill give it a shot
edit: i notice the thread is for the sensation, is there any difference in the process for the MyTouch 4g Slide?
rflores3686 said:
thanks for the suggestion. ill give it a shot
edit: i notice the thread is for the sensation, is there any difference in the process for the MyTouch 4g Slide?
Click to expand...
Click to collapse
You mean the thread that's in the MT4GS Development section? I don't know for certain if it works. I haven't bothered to unroot, gain an unlocked bootloader via HTCdev, reroot, then using juopunutbear. My unlocked-via-Revolutionary bootloader works just fine.
Related
I rooted according the directions found here: http://www.droidfiles.us/nexus-s-4g/root-nexus-s-4g/ after getting a new Nexus S 4G.
Even after locking the bootloader. It goes to the Android-with-box then to the Exclaimation-point-inside triangle. When I volume-up and power-button from that screen, an "Android Recovery <3e>" comes up...
Does anyone know what might be going on? And how do I get my custom recovery to stick?
Well, that's my post, so ill try to help. First, and don't take this the wrong way, but did you follow those instructions to a T? When you boot into bootloader, your pushing CWM to you phone with the fastboot command?
Sent from my Nexus S 4G using XDA App
mikeyinid said:
Well, that's my post, so ill try to help. First, and don't take this the wrong way, but did you follow those instructions to a T? When you boot into bootloader, your pushing CWM to you phone with the fastboot command?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
TonyArmstrong said:
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
Click to expand...
Click to collapse
Apparently alot of people have this issue, me included. I seen some posts about using root explorer to change the name of the recovery image if it shows up in system /ext. Sounds crazy but I hear it doesn't show up on all phone's. IV come to terms with having to fastboot every time I flash but I'd love to see a fix. Have you tried Amons recovery?
TonyArmstrong said:
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
Click to expand...
Click to collapse
Have you flashed recovery through Rommanager when your phone boots up?
You have to flash a non-stock kernel, the recovery gets overwritten on reboot. So if you flash CWM and reboot without flashing a custom kernel you will be back to stock recovery.
Edit: oops maybe I was wrong lol, maybe it isnt the kernel. im assuming you flashed the recovery in fastboot?
mbh87 said:
You have to flash a non-stock kernel, the recovery gets overwritten on reboot. So if you flash CWM and reboot without flashing a custom kernel you will be back to stock recovery.
Edit: oops maybe I was wrong lol, maybe it isnt the kernel. im assuming you flashed the recovery in fastboot?
Click to expand...
Click to collapse
No, I dont think your wrong bro. It makes sense. Ill test your theory soon.
Tony, when you push CWM, are you able to boot into recovery by hitting volume down twice to recovery and hitting power? If so, I suggest you flash this ROM. Its stock rooted and you will not have problems with CWM sticking. You dont even have to wipe to flash it...
I've read on some methods for rooting that there is a file /system/etc/install-recovery.sh (or something like that, should be able to find it by mounting system in recovery and adb shell ls /system/etc then using adb shell rm -r /system/etc/install-recovery.sh).
Though after I fastboot flashed the recovery, booted into recovery, did a nandroid, I formatted /system before I flashed CM7, so that would've killed the file anyways.
david1171 said:
I've read on some methods for rooting that there is a file /system/etc/install-recovery.sh (or something like that, should be able to find it by mounting system in recovery and adb shell ls /system/etc then using adb shell rm -r /system/etc/install-recovery.sh).
Though after I fastboot flashed the recovery, booted into recovery, did a nandroid, I formatted /system before I flashed CM7, so that would've killed the file anyways.
Click to expand...
Click to collapse
I just had CWM, never had any issues. Im not sure what dictates whether that file is there or not. Im guessing that since tony is so quiet though he got it figured out..
whats amazing is i dont have this script and its one of the things holding the one click up :x
also its part of init.rc so technically a new kernel would.. in theory wipe that out...
mikeyinid said:
Have you flashed recovery through Rommanager when your phone boots up?
Click to expand...
Click to collapse
I did flash CWM through Rom Manager. That didn't work the first few times. It stalled...
mikeyinid said:
Tony, when you push CWM, are you able to boot into recovery by hitting volume down twice to recovery and hitting power? If so, I suggest you flash this ROM. Its stock rooted and you will not have problems with CWM sticking. You dont even have to wipe to flash it...
Click to expand...
Click to collapse
I got it to stick -- or at least i thought I had it. I followed the initial instructions provided in a previous thread. And per the instructions, I download Rom Manager and I installed CWM through it (again).
I'm going to wipe my phone fully -- reinstall the base 2.3.4 with the the stock recovery, via the IMG files for GRJ22 and start over...See what happens then.
Wait, I'm confused. Why would you flash stock images when your already stock? If you follow the instructions in the link you posted in the op there is no reason you shouldn't be rooted. Have you actually even booted into recovery?
TonyArmstrong said:
I got it to stick -- or at least i thought I had it. I followed the initial instructions provided in a previous thread. And per the instructions, I download Rom Manager and I installed CWM through it (again).
I'm going to wipe my phone fully -- reinstall the base 2.3.4 with the the stock recovery, via the IMG files for GRJ22 and start over...See what happens then.
Click to expand...
Click to collapse
Sent from my Nexus S 4G using XDA App
I realllyyy don't suggest flashing a recovery with rom manager. I'm not bashing ROM Manager, I'm a paid user, but the way that it flashes recoveries is unsafe. I've had it almost brick my Evo and I've seen it brick other phones.
Just use fastboot... if you can't get that working, you probably shouldn't be messing with the phone.
mikeyinid said:
Wait, I'm confused. Why would you flash stock images when your already stock? If you follow the instructions in the link you posted in the op there is no reason you shouldn't be rooted. Have you actually even booted into recovery?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I'm rooted successfully. I feel more comfortable (with recovery acting flaky) with unrooting and starting over from scratch...
Call me kooky, but a bone-stock unrooted phone with no user data, no nothing, is how I got it, so why not return it to that state and start over. That's the only way I know to insure that whatever I do is not influenced by any data, bad file permissions, etc. that could hose rooting and installing recovery.
TonyArmstrong said:
I'm rooted successfully. I feel more comfortable (with recovery acting flaky) with unrooting and starting over from scratch...
Call me kooky, but a bone-stock unrooted phone with no user data, no nothing, is how I got it, so why not return it to that state and start over. That's the only way I know to insure that whatever I do is not influenced by any data, bad file permissions, etc. that could hose rooting and installing recovery.
Click to expand...
Click to collapse
OCD, I know the feeling lol. What got it to stick?
derekwilkinson said:
I realllyyy don't suggest flashing a recovery with rom manager. I'm not bashing ROM Manager, I'm a paid user, but the way that it flashes recoveries is unsafe. I've had it almost brick my Evo and I've seen it brick other phones.
Just use fastboot... if you can't get that working, you probably shouldn't be messing with the phone.
Click to expand...
Click to collapse
I used fastboot to install CWM initially (fastboot flash recovery recovery-xxxxx.zip -- can't remember the filename right now). The directions for rooting the NS4G state explicitly to use ROM Manager to flash the recovery to "make sure it sticks" after initially pushing it to the phone via fastboot.
It's obviously a hack, but apparently it works more often than it fails.
I'm a paid user of ROM Manager as well. I have to admit, it was fine to flash Amon Ra to my Evo. Since I'm new(er) to the NS4G, I'm going to defer to those with more expertise and follow the directions given.
TonyArmstrong said:
I used fastboot to install CWM initially (fastboot flash recovery recovery-xxxxx.zip -- can't remember the filename right now). The directions for rooting the NS4G state explicitly to use ROM Manager to flash the recovery to "make sure it sticks" after initially pushing it to the phone via fastboot.
It's obviously a hack, but apparently it works more often than it fails.
I'm a paid user of ROM Manager as well. I have to admit, it was fine to flash Amon Ra to my Evo. Since I'm new(er) to the NS4G, I'm going to defer to those with more expertise and follow the directions given.
Click to expand...
Click to collapse
well the "make sure it sticks" flashing with rom manager doesn't make any sense. the only way the recovery would be overwritten is if the ROM you flash over writes it or in fastboot
mikeyinid said:
OCD, I know the feeling lol. What got it to stick?
Click to expand...
Click to collapse
Yeah, I'm very anal when it comes to this kind of stuff...I was a developer for a little bit (Java middleware, then on to the front-end stuff) where regression testing was important. Sometimes, it's best to reload things piece by piece to see what breaks what. Then go from there.
I haven't gotten it to stick yet; gonna get some sleep and start over tomorrow. I used fastboot to push the stock boot, bootloader, system, recovery, and userdata IMGs a moment ago, and the phone is back to bone stock.
So i was going to update to the new ICS roms and you have to flash the new firmware pg58img. So i did but as it was updating it said i had a wrong CID and it stopped there. The real problem is now my phone is boot looping and get stuck at the HTC screen. I tried wiping everything, using a super wipe script, The Restores i have, it seems like everything is restored fine.. but when i go to reboot my phone.. it stays boot looping.. i tried flashing other roms after a full wipe..nothing..stays boot looping. i just don't understand what i have to do now... all i did was try to flash that img and got that error now i cant get a rom to even boot up. Any ideas/thoughts on what the problem is?
Remove the firmware file from your ad card using a card reader on your pc.
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
Did you SuperCID your phone before you flashed ICS?
As far as I know this is a MUST.
If you follow this guide everything should work:
http://forum.xda-developers.com/showthread.php?t=1192300
JonathanFermin said:
So i was going to update to the new ICS roms and you have to flash the new firmware pg58img. So i did but as it was updating it said i had a wrong CID and it stopped there. The real problem is now my phone is boot looping and get stuck at the HTC screen. I tried wiping everything, using a super wipe script, The Restores i have, it seems like everything is restored fine.. but when i go to reboot my phone.. it stays boot looping.. i tried flashing other roms after a full wipe..nothing..stays boot looping. i just don't understand what i have to do now... all i did was try to flash that img and got that error now i cant get a rom to even boot up. Any ideas/thoughts on what the problem is?
Click to expand...
Click to collapse
Just take out the SDcard and boot as normal then delete the PB58IMG.zip file from the SDcard using your favourite file manager.
EDIT: Eek, noticed you Superwiped, so just restore the nandroid backup you presumably made. The imortant thing is to stop the phone seeing the PG58IMG.zip file on the root of the SDcard.
At this point you will HAVE to super CID. Only takes about a minute to do and is very easy to do. All you need it ADB. After reflash new firmware and your good.
Jamison904 said:
At this point you will HAVE to super CID. Only takes about a minute to do and is very easy to do. All you need it ADB. After reflash new firmware and your good.
Click to expand...
Click to collapse
Whilst I agree that SuperCID is good it's not neccessary.
Look at: http://forum.xda-developers.com/showthread.php?t=1459767 various options.
I saw that the new CleanROM was using the Aroma installer for both versions of the ROM, so I figured I'd give it a shot. I don't have any experience with Aroma, but it all seemed to be working at first. However, I guess the file may have been corrupt because it just stuck at "Installing ROM" and never finished.. I hit the next button and it said it was finished even though I never got a status update. Stuck at HTC load screen, and will NOT boot into recovery even from the bootloader.
Since I can still load the bootloader, but not recovery, I still have some hope, right?
All I should have to do is run the AT&T RUU, right?
Halp!
infamousjax said:
I saw that the new CleanROM was using the Aroma installer for both versions of the ROM, so I figured I'd give it a shot. I don't have any experience with Aroma, but it all seemed to be working at first. However, I guess the file may have been corrupt because it just stuck at "Installing ROM" and never finished.. I hit the next button and it said it was finished even though I never got a status update. Stuck at HTC load screen, and will NOT boot into recovery even from the bootloader.
Since I can still load the bootloader, but not recovery, I still have some hope, right?
All I should have to do is run the AT&T RUU, right?
Halp!
Click to expand...
Click to collapse
Relock then try the RUU
http://forum.xda-developers.com/showthread.php?t=1761429
Sent from my HTC One X
Or push twrp recovery and flash again.
Thanks for the responses -- was able to boot into recovery (CWM)... Not sure why it wouldn't work before.
Now it says it cannot mount the sdcard...
doesn't sound good.
Waiting on RUU to finish downloading, then I'll relock and try that.
infamousjax said:
Thanks for the responses -- was able to boot into recovery (CWM)... Not sure why it wouldn't work before.
Now it says it cannot mount the sdcard...
doesn't sound good.
Waiting on RUU to finish downloading, then I'll relock and try that.
Click to expand...
Click to collapse
You should not use cwm, use twrp, CleanROMs op stated that, try pushing twrp, and flashing before you ruu, it causes issues that hasn't been fixes yet.
Sent from my HTC One X
Can't use clock work. Use team win.
If everybody is saying use TWRP and the person is still using CWM; one has to wonder how intelligent that person is.
mankind 0 monkey 1
infamousjax said:
Now it says it cannot mount the sdcard...
Click to expand...
Click to collapse
This is a known issue with CWM, mount SD simply does not work. Use TWRP like everyone is saying.
Did you try wiping anything in Aroma? Because that is a known issue as well (results in soft bricks). Only wipe in recovery, and use Aroma only for picking the various ROM options (not for wiping anything).
Got it working -- used fastboot to flash TWRP and formatted SD card and now everything is lovely.
I've been flashing CleanROM since the beginning before there was TWRP and never bothered to switch recoveries. I guess I should have read the notes more closely.. oh well, no harm done
thanks for the replies and help
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
j0hnnyn said:
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
Click to expand...
Click to collapse
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
psycopanther said:
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
volume up/home/power button is recovery try that
and you used rom manger to flash rom?
j0hnnyn said:
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
PJnc284 said:
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
Click to expand...
Click to collapse
Yep, kexec rom (kernel) using a recovery that doesn't support it.
not sure if this can help but read this post I made, it may help:
http://forum.xda-developers.com/showthread.php?t=1842716
Make sure you have the right CWR version which is 6.0.1 or 6.0.2. Don't mess around with flashing things in rom manager.
To get to your recovery you need to use vol up+home+power.
The vol down puts the phone into Download/ODIN mode. It's like the bootloader/hboot screen of HTC phones.
I always super wipe)cache,data,dalvil,system) before any install, nandroid or fresh rom. And then install downloaded apps with tit backup.
To use Bean's nandroids after bootloader unlock, flash a fresh copy of bean first to install kexec, then flash your nandroid.
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1768209]
From what I have read in his original post for his new build, it does require an unlock and is running a custom non-kexec kernel, so it I would draw the same conclusion that you are and it should in theory work with the 6.0.1.2 version of CWM.
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
You should be able to use cwm6.0.1.2 to flash Imoseyons leankernel on any version of a custom touchwiz rom and enjoy no kexec
Im running beans 8 with imo's 2.2 kernel w/ no kexec...dont really like beans 9.
Alright, I have looked and tried almost everything I could find to help me on this but nothing has worked yet, my problem is my screen gets stuck in the HTC boot screen and won't move any further, what I did to get it to this is I got my shift rooted though the htcdev site, but it is not s-off, I wanted to install a cyanogen mod, the 7.2 one on it, well i went to CWM and said install aborted so I tried to reboot my phone and now stuck, i can still get into the CWM recovery but nothing has helped yet,I have tried to push several boot.img files, and tried to downgrade to 2.2 and nothing...I am all up for ideas.
EDIT: I have done some tweaking with restoring my old back up and I have come to the conclusion that my /system folder is corrupt, i know a few ways to fix that but anyone one the best way and maybe a 2.3.4 system folder to use?
EDIT2: I replaced my system folder with one that i have and now it gets past the white htc screen but will loop the sprint 4g screens.
FIXED IT,\: what I did was I managed to RUU back to 2.2 through this thread, now I am on 2.2 and will continue to get an s-off root, thank you for all your help
11telisz said:
Alright, I have looked and tried almost everything I could find to help me on this but nothing has worked yet, my problem is my screen gets stuck in the HTC boot screen and won't move any further, what I did to get it to this is I got my shift rooted though the htcdev site, but it is not s-off, I wanted to install a cyanogen mod, the 7.2 one on it, well i went to CWM and said install aborted so I tried to reboot my phone and now stuck, i can still get into the CWM recovery but nothing has helped yet,I have tried to push several boot.img files, and tried to downgrade to 2.2 and nothing...I am all up for ideas.
Click to expand...
Click to collapse
Can you get into bootloader? If so, what is your hboot version and software version?
Just in case you don't know how, to get into bootloader, you need to power off or pull battery, then press and hold VolDown+Power until the white bootloader screen comes up
At the top it tells you the hboot version
Sent from my PG06100 using xda premium
I can get into bootloader.
hboot-0.99.0001
radio-1.08.01.0111
thats all I can get about my version
11telisz said:
Alright, I have looked and tried almost everything I could find to help me on this but nothing has worked yet, my problem is my screen gets stuck in the HTC boot screen and won't move any further, what I did to get it to this is I got my shift rooted though the htcdev site, but it is not s-off, I wanted to install a cyanogen mod, the 7.2 one on it, well i went to CWM and said install aborted so I tried to reboot my phone and now stuck, i can still get into the CWM recovery but nothing has helped yet,I have tried to push several boot.img files, and tried to downgrade to 2.2 and nothing...I am all up for ideas.
Click to expand...
Click to collapse
When you went through HTC-Dev.com you did not Root the Device. All you can do at the site is Unlock the Bootloader. To resolve the issue you can try a Factory Data Restore in Bootloader, but you are going to lose all the current Data on the Device. It may or may not work. If it does not then, you may have to run an RUU. To do the Factory Restore pull the Battery on the device. Then put the Battery back in. Hold Volume Button down , now at the same time press the Power Button. It will boot into Bootloader. Once it is in Bootloader use the Volume Rockers to toggle Up, or Down. Then choose Factory Restore by pressing the Pwer Button. Since your not rooted that's your only option that I know of other than an RUU. If that does get you out of the White Screen I would suggest finding out your Android version. Then following the correct process to attain Full Root.
Maybe I was a bit unclear, I went though the htcdev site to unlock the bootloader, then i moved clockworkmod recovery instead of the stock recovery, i then installed superuser through Clockworkmod, so i had root though that, but not an s-off root, so I then installed ROM manager and thought the cyanogen 7.2 rom would be a cool one to have, I forgot it was not an s-off root, so i went ahead with downloading it though Rom manager and it prompted me to install the new rom, and brought me to clockworkmod recovery and said the install was aborted, and i rebooted and then it got stuck at the htc screen, I can get into bootloader and clockworkmod recovery, I have a backup of my stock rom on my computer and put it onto my sd card hoping i can restore to that one, but i get the md5 mismatch error, working on fixing that now.
I still believe that most of the issue is that you are not Fully Rooted. What version of Android where you on when you started ? The reason I ask is because the method you used is a bit unorthodox, so I doubt your Rooted. I would still suggest doing a factory Restore. But you can look HERE on how to fix the MD5 mismatch error.
Yeah, if you only unlocked bootloader, thats not a full root, you still have a ways to go
The best thing would be to just RUU and start over using VICODAN's method, which covers 2.2 all the way up to 2.3.4
Sent from my PG06100 using xda premium
The method i used for rooting was though this post, I got up to the step downgrading from 2.3.4 to 2.2 till about step 17 of the 2.3.4, I wasn't sure if it acutally downgraded to 2.2 because I am unable to check my version though the bootloader or clockworkmod recovery, so I most likely am still on 2.3.4
11telisz said:
The method i used for rooting was though this post, I got up to the step downgrading from 2.3.4 to 2.2 till about step 17 of the 2.3.4, I wasn't sure if it acutally downgraded to 2.2 because I am unable to check my version though the bootloader or clockworkmod recovery, so I most likely am still on 2.3.4
Click to expand...
Click to collapse
Ok so your defiantly not on 2.2 . The question is what version of 2.3.4 are you on ? Go into HBoot and go to System Info. What is the OS Ver. ? Have you tried doing a Factory Reset just to see if it will Boot back up ?
prboy1969 said:
Ok so your defiantly not on 2.2 . The question is what version of 2.3.4 are you on ? Go into HBoot and go to System Info. What is the OS Ver. ? Have you tried doing a Factory Reset just to see if it will Boot back up ?
Click to expand...
Click to collapse
There is no system info tab in my hboot menu, but i believe i know what is wrong, somehow my /system folder got corrupt, so i have to replace my /system folder with a new one, i know a few methods but what is the best method to going about that with an s-on?
11telisz said:
There is no system info tab in my hboot menu, but i believe i know what is wrong, somehow my /system folder got corrupt, so i have to replace my /system folder with a new one, i know a few methods but what is the best method to going about that with an s-on?
Click to expand...
Click to collapse
The only way I know how to do it would be using adb and just flashing all the images through that.
Sent from my PG06100 using xda premium