Database Info

[Q] Part-Bootloop

Hello guys, I've got a weird problem. I messed around with my Transformer a bit, rooted etc on 8.4.4.11. CWM isn't working, and I can't even boot into recovery. It just sits at the "Loading recovery kernel...". Anyway, its freezing at the eeePad screen on bootup and doesn't do anything (this has stopped me from reflashing a blob, or Asus OTA updating). I've tried reflashing stock and rooted images quite a few times, but it always does the same thing. Now, I can get around the freeze by going to the hard reset screen and declining, and it boots into Android.
Whats wrong? Bootloader? Has to be something in startup, but I cant figure it out.

Re-flash using NVFlash method, in dev section (and don't forget to put the NVFlash ROM version in the folder)

bud77 said:
Re-flash using NVFlash method, in dev section (and don't forget to put the NVFlash ROM version in the folder)
Click to expand...
Click to collapse
Nope, that actually made it worse. Anyway, each root that I tried to go through did the exact same thing. Now it doesnt show anything on boot.
Is there some way to completely return it to stock? Just flash an official firmware pack with nvflash and have everything back to the day it was shipped?
EDIT: Fixed it, I had the wrong type of ROM unpacked. Thanks Bud.

padd3r said:
Nope, that actually made it worse. Anyway, each root that I tried to go through did the exact same thing. Now it doesnt show anything on boot.
Is there some way to completely return it to stock? Just flash an official firmware pack with nvflash and have everything back to the day it was shipped?
Click to expand...
Click to collapse
How could it make it worse .... ?
What's the error you're getting while NVFlashing ?
For the stock, if you can't NVFlash a rom, you won't be able to flash stock too, as the process is identical

[Q] Clockworkmod Recovery updated, can't enter recovery mode

Hi, I've searched and can't find an answer. I've managed to root my Infuse and got Infinitum rom installed. It was working great until just this evening when Clockworkmod updated (sorry, I can't find the version number). It went into a boot loop. It took me a bit, but I managed to get it out of the boot loop and back to stock, now it's rooted again with Infinitum running again.
I'm trying to get back to a recovery point that I do have on the phone, but I can't get the phone to boot to recovery no matter what I do. When I try using the vol and power buttons combination or from ROM manager I get the same thing. It goes past the stock Samsung logo into the Galaxy S/Cyanogen(mod) logo, but freezes there.
I can, of course, take the loss of my setup and redo everything manually. I would really prefer to be able to get that backup back. I'm also concerned should I ever need to get into recovery mode for any other reason. My guess is that I need to downgrade the CWM version, but I haven't been able to find how to do it.
Can anyone give me any help? Please let me know if there's info that I can give that would be useful...I'm noobie, I know!

VyCariously said:
Hi, I've searched and can't find an answer. I've managed to root my Infuse and got Infinitum rom installed. It was working great until just this evening when Clockworkmod updated (sorry, I can't find the version number). It went into a boot loop. It took me a bit, but I managed to get it out of the boot loop and back to stock, now it's rooted again with Infinitum running again.
I'm trying to get back to a recovery point that I do have on the phone, but I can't get the phone to boot to recovery no matter what I do. When I try using the vol and power buttons combination or from ROM manager I get the same thing. It goes past the stock Samsung logo into the Galaxy S/Cyanogen(mod) logo, but freezes there.
I can, of course, take the loss of my setup and redo everything manually. I would really prefer to be able to get that backup back. I'm also concerned should I ever need to get into recovery mode for any other reason. My guess is that I need to downgrade the CWM version, but I haven't been able to find how to do it.
Can anyone give me any help? Please let me know if there's info that I can give that would be useful...I'm noobie, I know!
Click to expand...
Click to collapse
There are many layers to your questions.
You may need to read a bit more to get a better understanding.
Here is two points I can offer that may be helpful.
1. Don't use ROM Manager for the Infuse.
2. To downgrade a cwm version, you will need to flash a GB or FROYO kernel in download mode via heimdall or odin. You can also use any one of the return to stock that is flashed in download mode also.
If you think you lost recovery, try flashing the kernel for the rom you were running in cwm, if you can get back into cwm again.

qkster said:
There are many layers to your questions.
You may need to read a bit more to get a better understanding.
Here is two points I can offer that may be helpful.
1. Don't use ROM Manager for the Infuse.
2. To downgrade a cwm version, you will need to flash a GB or FROYO kernel in download mode via heimdall or odin. You can also use any one of the return to stock that is flashed in download mode also.
If you think you lost recovery, try flashing the kernel for the rom you were running in cwm, if you can get back into cwm again.
Click to expand...
Click to collapse
I believe you about the ROM Manager. Too late, unfortunately. I'll take it off.
I had the phone back to stock with Odin. I went through all of the steps that I went through to first root it and install Infinitum. I had red cwm at the time. I just can't seem to get into it now. I don't think I lost it, I'm just unsure of how to get to it, since it freezes at the cm startup. I can just power off from there after I give up waiting, and it will boot to ICS normally when I power it on normally. I have Titanium Backup Pro, and it can access the nandroid backup that I have to get the apps and data. I was just hoping to recover the whole setup. I had an issue last weekend (oops to me) when I tried to install a JB rom where it went into a boot loop. I recovered everything after backtracking like I did tonight, and was hoping to be able to do the same. Is there any hope, do you think, if I go back and return to stock and start over from the beginning again? If not, I'll just suffer and redo the whole thing.
By the way, I really appreciate you answering. I've been lurking for a few weeks, and realize that you know a LOT about these phones.

VyCariously said:
I believe you about the ROM Manager. Too late, unfortunately. I'll take it off.
I had the phone back to stock with Odin. I went through all of the steps that I went through to first root it and install Infinitum. I had red cwm at the time. I just can't seem to get into it now. I don't think I lost it, I'm just unsure of how to get to it, since it freezes at the cm startup. I can just power off from there after I give up waiting, and it will boot to ICS normally when I power it on normally. I have Titanium Backup Pro, and it can access the nandroid backup that I have to get the apps and data. I was just hoping to recover the whole setup. I had an issue last weekend (oops to me) when I tried to install a JB rom where it went into a boot loop. I recovered everything after backtracking like I did tonight, and was hoping to be able to do the same. Is there any hope, do you think, if I go back and return to stock and start over from the beginning again? If not, I'll just suffer and redo the whole thing.
By the way, I really appreciate you answering. I've been lurking for a few weeks, and realize that you know a LOT about these phones.
Click to expand...
Click to collapse
Okay, so next question. I've been reading and searching and reading some more. I can get the phone back to stock and work up again, but I still reach a point where it will freeze on the Samsung/CM startup screen. In reading the Infinitum Project thread, I found this (yes, it's pretty easy to find):
"Recovery/CWM messed up?
Here is how to fix it...
1) Download uclb3 heimdal by qkster
2) open the program
3) put phone in download mode
4) click flash (leave program open when finished DO NOT CLOSE)
5) after it finishes and your phone reboots, put the phone back in download mode and reconnect to PC
6) click flash bootloader on the heimdal program you left running
7) flash, let reboot and your recovery problems should be gone"
I used that to get back to stock before...doesn't that remove the root? Do I have to go through all that, then the bootloaders, and then go back and root all over again to get back to a working CWM? I'm sorry to ask so many questions, but it seems that I've done most of this already, though I admit to not doing the flash for the bootloader. I'm just unclear since it says "your recovery problems should be gone" at the end of that, like I have to do nothing more.

That does remove root access. However, root isn't really necessary, at least for the stock ROM, if you have no intentions of staying stock. The ROM .zips you'll subsequently flash are pre-rooted. After you Heimdall back to stock, and flash it again with "flash bootloaders" selected, then use Heimdall to flash this kernel:
http://d-h.st/6KA
That'll flash both a new kernel and CWM Red recovery. It'll take a few minutes to boot up the first time, as it's installing the lagfix. Once it boots up, just shut it down and boot back up in recovery. From there, you can do whatever you need to do.

VyCariously said:
Okay, so next question. I've been reading and searching and reading some more. I can get the phone back to stock and work up again, but I still reach a point where it will freeze on the Samsung/CM startup screen. In reading the Infinitum Project thread, I found this (yes, it's pretty easy to find):
"Recovery/CWM messed up?
Here is how to fix it...
1) Download uclb3 heimdal by qkster
2) open the program
3) put phone in download mode
4) click flash (leave program open when finished DO NOT CLOSE)
5) after it finishes and your phone reboots, put the phone back in download mode and reconnect to PC
6) click flash bootloader on the heimdal program you left running
7) flash, let reboot and your recovery problems should be gone"
I used that to get back to stock before...doesn't that remove the root? Do I have to go through all that, then the bootloaders, and then go back and root all over again to get back to a working CWM? I'm sorry to ask so many questions, but it seems that I've done most of this already, though I admit to not doing the flash for the bootloader. I'm just unclear since it says "your recovery problems should be gone" at the end of that, like I have to do nothing more.
Click to expand...
Click to collapse
As Apex pointed out, each time we bring the phone back to stock, we lose root access and all the previous setup. It's a fact of flashing.
No big deal though, rooting is easy and is not really needed. What is needed is the insecure kernel with cwm. The link Apex gave you is the same as the posted kernel in post #2 of the thread. That kernel will give you the cwm. Review that thread if you haven't yet.
Flash the heimdall uclb3 repartition package. Immediately after it successfully boot your phone, don't close the program. check the bootloader box and put the phone back into dl mode and flash it again to get your gb bootloaders...
then flash the kernel.
review my how to thread if you need to.
Andros11 also made a how to for JB if you want to live vicariously.
gl

qkster said:
Andros11 also made a how to for JB if you want to live vicariously.
gl
Click to expand...
Click to collapse

Thanks guys
It's been a crazy busy week and I just didn't have time to deal with the phone. I've been dealing with stock gingerbread. It's getting kind of annoying, though, it seems less stable than the custom ICS that I had on it before. Not sure when I'm going to have time to play with it again and try to get it to where I want it. I think I'm going to try to totally wipe all of the old stuff out of the memory before I do it again, though. There's something that wasn't allowing me to do what you guys are telling me to do successfully. I'm also thinking of finding a GS2 and just selling the Infuse, not because of my confusion, but because the GS2 was what I was originally looking for anyway.
I'll try to get this one set up first, though, as it's just a matter of me being obsessive about it.
qkster, I'll look into the JB, too, lol.
qkster said:
As Apex pointed out, each time we bring the phone back to stock, we lose root access and all the previous setup. It's a fact of flashing.
No big deal though, rooting is easy and is not really needed. What is needed is the insecure kernel with cwm. The link Apex gave you is the same as the posted kernel in post #2 of the thread. That kernel will give you the cwm. Review that thread if you haven't yet.
Flash the heimdall uclb3 repartition package. Immediately after it successfully boot your phone, don't close the program. check the bootloader box and put the phone back into dl mode and flash it again to get your gb bootloaders...
then flash the kernel.
review my how to thread if you need to.
Andros11 also made a how to for JB if you want to live vicariously.
gl
Click to expand...
Click to collapse

Hey I am not the Infuse user... But I faced similar problem in my xperia some days back after updating the recovery.
I was also not able to enter recovery at boot time using my usual volume down way...
What the change was the new recovery checks for tap on the screen (repeatetive) instead of volume down button...
Not sure if it will work or not for you... But you can give a try...
Hit thanks if it works
Sent from my MT11i using xda app-developers app

XperiaNeoVNoob said:
Hey I am not the Infuse user... But I faced similar problem in my xperia some days back after updating the recovery.
I was also not able to enter recovery at boot time using my usual volume down way...
What the change was the new recovery checks for tap on the screen (repeatetive) instead of volume down button...
Not sure if it will work or not for you... But you can give a try...
Hit thanks if it works
Sent from my MT11i using xda app-developers app
Click to expand...
Click to collapse
I didn't get a chance to try it, sorry! I ended up wiping my phone totally back to stock Gingerbread with nothing on the sd card, either, and starting all over again. It seems to be working really well this time (fingers crossed). RemICS-UX is pretty much awesome

VyCariously said:
I didn't get a chance to try it, sorry! I ended up wiping my phone totally back to stock Gingerbread with nothing on the sd card, either, and starting all over again. It seems to be working really well this time (fingers crossed). RemICS-UX is pretty much awesome
Click to expand...
Click to collapse
No probs...
:thumbup:
Sent from my MT11i using xda app-developers app

[Q] Houston, boy do I have a problem!

Just rooted my new SGS3 using New Root Method Released for Verizon’s Galaxy S3, No Odin Required. i did the data & kelvic wipe then install Clean Rom 5.0. All progressed without a hitch. Even backed up with CWM prior to flash.
I rebooted into the new rom and got this: System software not authorized by Verizon Wireless... rebooted several time with same result.
What can I do now? Thanks for your help.

Just a wild guess, but me thinks your bootloader is still locked! But I'm not sure that will even apply because I rooted my device before unlocking the bootloader. But I rooted my device via ODIN first.
You can try EZ-Unlock via the Market. The GUI is still very buggy and will show the status as unknown but the internal workings of the app works good.
You got nothin to loose in trying. Go back to stock and give it another whirl after you've unlocked the bootloader.
Of that fails then I would suggest using the tried and true method..ODIN.
G'luck!

yup your bootloader is still locked
check the downloads thread and use version 1.2.

That means your boatloader is locked. You now must Odin back to stock and start over. Droid style has a guide stickied in the development thread. Follow section 6 of it.
Next time use ez unlock version 1.2 to unlock you boatloader.
Sent from my SGS3 running Eclipse 2.1

downloads list
http://forum.xda-developers.com/showthread.php?t=1850506

tekrhino said:
Just a wild guess, but me thinks your bootloader is still locked! But I'm not sure that will even apply because I rooted my device before unlocking the bootloader. But I rooted my device via ODIN first.
You can try EZ-Unlock via the Market. The GUI is still very buggy and will show the status as unknown but the internal workings of the app works good.
You got nothin to loose in trying. Go back to stock and give it another whirl after you've unlocked the bootloader.
Of that fails then I would suggest using the tried and true method..ODIN.
G'luck!
Click to expand...
Click to collapse
Thanks. I can't get past the warning dialogue screen. Pulled the battery, no good. PC can't see the phone with USB.

Prophotog said:
Thanks. I can't get past the warning dialogue screen. Pulled the battery, no good. PC can't see the phone with USB.
Click to expand...
Click to collapse
Yikes, ok
You have to get into DOWNLOAD MODE.. Power+ Volume Down+ Home key at the same time after a fresh battery pull.
Do a search on the Development forum to set up Odin on your PC.
YOU Must FOLLOW directions EXACTLY our you will have very expensive BRICK!
This forum could help:
http://forum.xda-developers.com/showthread.php?t=1762709
Or even better, this one:
http://forum.xda-developers.com/showthread.php?t=1840030

tekrhino said:
Yikes, ok
You have to get into DOWNLOAD MODE.. Power+ Volume Down+ Home key at the same time after a fresh battery pull.
Do a search on the Development forum to set up Odin on your PC.
YOU Must FOLLOW directions EXACTLY our you will have very expensive BRICK!
This forum could help:
http://forum.xda-developers.com/showthread.php?t=1762709
Or even better, this one:
http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
Thanks to everyone!! Looks to be a long night. :>)

tekrhino said:
Yikes, ok
You have to get into DOWNLOAD MODE.. Power+ Volume Down+ Home key at the same time after a fresh battery pull.
Do a search on the Development forum to set up Odin on your PC.
YOU Must FOLLOW directions EXACTLY our you will have very expensive BRICK!
This forum could help:
http://forum.xda-developers.com/showthread.php?t=1762709
Or even better, this one:
http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
I lol'ed at your post. A little dramatic, don't you think? He's not even close to bricked. Just Odin from download mode back to stock, and redo the steps with bootloader unlock.
Here is a gift (working ez-unlock v1.2)
http://dl.dropbox.com/u/42057363/com.mmmeff.ez.unlock_3.apk

@Techsavvy
Yeah, perhaps a tad overdone on the theatricals.
Cut me some slack, I'm taking acting classes..lol
And... I know... I know..don't quit my day job!

Still having issues. I "think" I am in the download mode. Screen says Downloading.... It has Odin in red in top left corner. Device connects with Odin. BUT I am not getting a PASS message when flashing VRALEC bootchain. Last text line in Odin is: <OSM> Leave CS...
I have tried several attempts.
Suggestions?

Prophotog said:
Still having issues. I "think" I am in the download mode. Screen says Downloading.... It has Odin in red in top left corner. Device connects with Odin. BUT I am not getting a PASS message when flashing VRALEC bootchain. Last text line in Odin is: <OSM> Leave CS...
I have tried several attempts.
Suggestions?
Click to expand...
Click to collapse
No need to do the boot chains. Just follow section 5 of this guide and I recommend root 66 for the ROM you flash
http://forum.xda-developers.com/showthread.php?p=28530394
Sent from my SGS3 running Eclipse 2.1

tekrhino said:
@Techsavvy
Yeah, perhaps a tad overdone on the theatricals.
Cut me some slack, I'm taking acting classes..lol
And... I know... I know..don't quit my day job!
Click to expand...
Click to collapse
I appreciate the theatricals...however, I am having issues with Odin. Can't get the Pass message. I assume the "Downloading..." text means I'm in the download mode. Tried several attempts. I AM glad I'm not close to bricked too! Can't afford $600 or a divorce. Might have to sell a camera instead.

Prophotog said:
Just rooted my new SGS3 using New Root Method Released for Verizon’s Galaxy S3, No Odin Required. i did the data & kelvic wipe then install Clean Rom 5.0. All progressed without a hitch. Even backed up with CWM prior to flash.
I rebooted into the new rom and got this: System software not authorized by Verizon Wireless... rebooted several time with same result.
What can I do now? Thanks for your help.
Click to expand...
Click to collapse
And just for future reference, it's Dalvik, not Kelvic
Sent from my SCH-I535 using xda app-developers app

Prophotog said:
I appreciate the theatricals...however, I am having issues with Odin. Can't get the Pass message. I assume the "Downloading..." text means I'm in the download mode. Tried several attempts. I AM glad I'm not close to bricked too! Can't afford $600 or a divorce. Might have to sell a camera instead.
Click to expand...
Click to collapse
Just a heads up. You can get a real brick with Odin and easy. Follow the guide I linked earlier to a t and you'll be fine
Sent from my SGS3 running Eclipse 2.1

kintwofan said:
Just a heads up. You can get a real brick with Odin and easy. Follow the guide I linked earlier to a t and you'll be fine
Sent from my SGS3 running Eclipse 2.1
Click to expand...
Click to collapse
You are a scholar and a gentleman!! THANK YOU very much. You can have a portrait session on me any time. Name the time and place.

Prophotog said:
You are a scholar and a gentleman!! THANK YOU very much. You can have a portrait session on me any time. Name the time and place.
Click to expand...
Click to collapse
Cool, I take it you're up and running again. Just make sure you use ez unlock 1.2 next time. And the positive is you're an Odin pro now!
Sent from my SGS3 running Eclipse 2.1

Hi, I have a Verizon S3 flashed to Boost Mobile. I tried to gain root by flashing a stock rooted Rom and messed up the flash. I had to take it back to be flashed again  Now I'm more cautious before hand. I should have backed it up before attempting it, I know I know lol can anyone shed some light on how to update a flashed phone as well as how to root it. I could really use the help 
Also after I messed up the boost flash I paniced and flashed a sprint kernel hoping this would fix the problem. Since then anything that I've tried to view including taking camera shots and web browsing if done in landscape mode will be upside down, any remedy for this problem? I know now... root first, flash later. 
Sent from my SPH-L710 using XDA HD

Alex0826 said:
Hi, I have a Verizon S3 flashed to Boost Mobile. I tried to gain root by flashing a stock rooted Rom and messed up the flash. I had to take it back to be flashed again  Now I'm more cautious before hand. I should have backed it up before attempting it, I know I know lol can anyone shed some light on how to update a flashed phone as well as how to root it. I could really use the help 
Also after I messed up the boost flash I paniced and flashed a sprint kernel hoping this would fix the problem. Since then anything that I've tried to view including taking camera shots and web browsing if done in landscape mode will be upside down, any remedy for this problem? I know now... root first, flash later. 
Sent from my SPH-L710 using XDA HD
Click to expand...
Click to collapse
Sprint kernel is causing the inversion. Flash a vzw kernel. Read first flash later.
Sent from my SCH-I535 using xda app-developers app

Who ever did your flash might not done it right cause ya not supposed to lose a flash like that unless he didn't do things right. I can factory reset mine and I wont loose flash
Sent from my SPH-L900 using Tapatalk 2

[Q] First time rooting/S-Off/new ROM

Is there such thing as a guide like this one but that is up to date and with working links? I want to flash a new ROM onto my phone, but the guides I've found here and elsewhere have broken links, or use language that I don't understand, or skip vital steps. I've been working on this for four hours straight and I haven't gotten a single guide to work, or get stuck, or something else that's really dumb. For someone who has worked on computers for the last 17 years this is extremely frustrating. I'm very new to the android modding scene and apparently it's not just a community, but an entirely different culture and I'm feeling a bit shocked and confused. I have like 30 tabs open with guides, info, different ROMs, different ways to do it, etc and the more I learn the less I understand how to do this :/ I just want to get my phone working with a ROM that's very similar to stock Sense but without the crappy bloatware and memory issues. Miktouch is the one I thought I wanted, but apparently hasn't been updated in almost a year, and bulletproof/doubleshot is confusing. I can't even figure out how to root and get S-Of... Gah!
Please help.
This guide is confusing and skips steps or lacks real explanations.
Thank you.

First thing you want to do is root your phone, this is done by unlocking you bootloader through the HTC dev website. There is a tutorial that is stickyed in the developer section called something like root from any bootloader. I suggest to read that a bit.
Once you followed those steps and unlocked your bootloader you can decide if you want to remove all security flags (highly recommend this, but some find it difficult) in the same guide it explains what radio s-off is and links you to the jbear site to do the wire trick (needs Linux) (or find weekendstoshort for a way to do it in windows)
Feel free to ask more questions but all answers should be found in these xda threads and jbear site, no need to Google anything for this
Sent from my Nexus 4 using xda premium

I hope so...I'll give it another go tomorrow. I'm still quite frustrated at it. I wish I knew someone who had done it and could show me in person.

GiftigDegen said:
I hope so...I'll give it another go tomorrow. I'm still quite frustrated at it. I wish I knew someone who had done it and could show me in person.
Click to expand...
Click to collapse
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta

First timer here as well (although long time computer user/programming familiar so I might have a better understanding of some things than you) and I was able to fully unlock, S-OFF, and load up a JB rom to my phone using the guide right on this site (http://forum.xda-developers.com/showthread.php?t=1801106) and some help from some online friends that have done this kind of thing before. I found all links to be working, and pretty much all steps to be covered. The I guess hardest part was the permanent S-OFF using the wire trick. I had to burn an Ubuntu live cd and boot a laptop with it, but I was even able to get that step done. A little frustrating with the timing, I think it took me about 8 tries until it finally unlocked. The only thing I think I initially missed was wiping all 3 caches, so I did a dirty flash that got stuck on the boot screen. After I wiped and loaded again, no problems. If you'd like any additional help, I get pretty bored at work, so find me on aim or gchat, or just shoot me a PM here, I think I should get notified
Good luck, it's not as bad as I thought it would be
Also I haven't personally tried it, but feel free to peruse this thread as well: http://forum.xda-developers.com/showthread.php?t=1696373
Note you'll need to have already achieved HTCDev unlocked and be rooted to use this (covered in that first link)
Hope that helps!

PsychoPhreak said:
First timer here as well (although long time computer user/programming familiar so I might have a better understanding of some things than you) and I was able to fully unlock, S-OFF, and load up a JB rom to my phone using the guide right on this site (http://forum.xda-developers.com/showthread.php?t=1801106) and some help from some online friends that have done this kind of thing before. I found all links to be working, and pretty much all steps to be covered. The I guess hardest part was the permanent S-OFF using the wire trick. I had to burn an Ubuntu live cd and boot a laptop with it, but I was even able to get that step done. A little frustrating with the timing, I think it took me about 8 tries until it finally unlocked. The only thing I think I initially missed was wiping all 3 caches, so I did a dirty flash that got stuck on the boot screen. After I wiped and loaded again, no problems. If you'd like any additional help, I get pretty bored at work, so find me on aim or gchat, or just shoot me a PM here, I think I should get notified
Good luck, it's not as bad as I thought it would be
Also I haven't personally tried it, but feel free to peruse this thread as well: http://forum.xda-developers.com/showthread.php?t=1696373
Note you'll need to have already achieved HTCDev unlocked and be rooted to use this (covered in that first link)
Hope that helps!
Click to expand...
Click to collapse
I'm following the first guide you linked. So far it's working I just flashed CWmod on and I loaded it according to the instructions in the guide "After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping. "
But I forgot to d/c my phone. It still loaded CWmod and I navigated to backup/restore and clicked it. Right now my phone has the clockwork logo in the middle but it didn't give me any prompts after selecting backup/restore. What's it doing? It's been doing this for like 5 minutes. Should I be worried that I forgot to d/c the cable and whatnot?
Thanks

GiftigDegen said:
I'm following the first guide you linked. So far it's working I just flashed CWmod on and I loaded it according to the instructions in the guide "After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping. "
But I forgot to d/c my phone. It still loaded CWmod and I navigated to backup/restore and clicked it. Right now my phone has the clockwork logo in the middle but it didn't give me any prompts after selecting backup/restore. What's it doing? It's been doing this for like 5 minutes. Should I be worried that I forgot to d/c the cable and whatnot?
Thanks
Click to expand...
Click to collapse
I wouldn't worry, and I'm not entirely sure what it's trying to do, perhaps the possibility of USB storage is throwing it off. At this point I'd say just try to disconnect it, pull the battery, and start back up into recovery, but without the USB attached this time. I imagine then you'll be fine and able to backup the stock image like they say for safe keeping.
One more dummy question (tech support for many years, always check the simple stuff first...) you do have SOME SD card in there right?

PsychoPhreak said:
I wouldn't worry, and I'm not entirely sure what it's trying to do, perhaps the possibility of USB storage is throwing it off. At this point I'd say just try to disconnect it, pull the battery, and start back up into recovery, but without the USB attached this time. I imagine then you'll be fine and able to backup the stock image like they say for safe keeping.
One more dummy question (tech support for many years, always check the simple stuff first...) you do have SOME SD card in there right?
Click to expand...
Click to collapse
Yeah, 32gb =)

booted into recovery, clicked on bacup/restore...still just showing the logo in the middle.
(PS any mods out there listening, I'd love to have that 5 minute restriction removed =D )
Okay, so the select button changes from power to the scroll pad once in recovery...good to know.

GiftigDegen said:
booted into recovery, clicked on bacup/restore...still just showing the logo in the middle.
(PS any mods out there listening, I'd love to have that 5 minute restriction removed =D )
Okay, so the select button changes from power to the scroll pad once in recovery...good to know.
Click to expand...
Click to collapse
NVMD....You got it now.

strapped365 said:
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Using CWM to flash Miktouch now. Hopefully it works... =D

Just remember, if you are "S-On" you're going to need to fastboot flash boot boot.img after your ROM is thru flashing or you will hang up at the boot animation.

strapped365 said:
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
K. First impressions:
When I restart the phone, the first thing it does is force stop Gmail and Youtube several times. Is this supposed to happen?
Also, I'm extremely impressed with the speed of the restart. It's at LEAST twice as fast as stock.
And, Genius button doesn't work even after installing the patch linked to on your website (universal.zip).

WeekendsR2Short said:
Just remember, if you are "S-On" you're going to need to fastboot flash boot boot.img after your ROM is thru flashing or you will hang up at the boot animation.
Click to expand...
Click to collapse
Thanks Weekends. I did that and it's installed, though I fastboot flash boot boot.img before I used CWM to flash the rom. Does that make a difference? Do you think doing it that way will fix the force close mentioned above?

If there's not a fix for the gmail/youtube force closes, is it possible to do bulletproof with s-on? Thoughts? I really want to stick as close to stock MT4GS but with as solid a system as possible.

Flashing boot image before ROM will overwrite kernel
Wipe all
Flash ROM
Flash boot
Reboot
Sent from my Nexus 4 using xda premium

demkantor said:
Flashing boot image before ROM will overwrite kernel
Wipe all
Flash ROM
Flash boot
Reboot
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Another noob question. How do I wipe all?
Also, when I use CWM to install Mikrom it atuo restarts and loads up. Then do I restart again and go fastboot the new kernal?
Thank you all for how much help you have given me.

At the end of the updater-script there must be a reboot command, but being this ROM is based of stock you may not need to flash the kernel anyway.
Best methods for wiping is one of bluex's superwipe scripts or with fastboot
fastboot erase system -w
But being you are s-on that command may fail.
But always do a wipe data/factory reset, wipe cache, and wipe dalvik in recovery.
It also good practice to make a nandroid of current ROM before you flash anything
Sent from my Nexus 4 using xda premium

demkantor said:
At the end of the updater-script there must be a reboot command, but being this ROM is based of stock you may not need to flash the kernel anyway.
Best methods for wiping is one of bluex's superwipe scripts or with fastboot
fastboot erase system -w
But being you are s-on that command may fail.
But always do a wipe data/factory reset, wipe cache, and wipe dalvik in recovery.
It also good practice to make a nandroid of current ROM before you flash anything
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Mmkay, working doing this now.
Quick question, hopefully someone can give me a link, but I'd love the install the depaginated app drawer, genius fix and menu wake up mods for this, but the links are broken (dev-host times out). Any help?

See weekends mirror thread
Sent from my Nexus 4 using xda premium

Getting into TWRP from soft brick

Greetings. I found myself in a situation of being stuck at Alcatel splash screen after rebooting following a flash. Phone wouldn't respond to adb/fastboot commands, or upgrade tool. I kept powering off, and rebooting holding combo of power, vol up, down, and both. Finally after several tries, it booted into TWRP! I wish I could say it was a particular combo, but it was just repetition of power off, and combo of power/ vol buttons. Was able to do this twice with this "method". I have 60450 (Cricket). This Phone doesn't respond how I am used to getting into download (power+vol down), or recovery (power+vol up) Hope this helps if you find yourself in a similar situation.

I've developed an issue as well. I can get into twrp just fine and all is fine there but any combination of ROM or kernel even stock makes my phone reboot every 2-5 minutes. Last night after messing around with a few cm builds and then going back to stock after I couldn't get the phone to cool down..... Stock no longer wanted to cool down either. It's been running way to hot so I turned it off for the night. Turn it back on today and same issues. It even restarts on the powered off battery charging screen , I took it a step further and deleted system, data, cache, and internal storage as well as removing my external sd so no ROM or files was on it at all and it still wanted to reboot at the charging screen! Only place it doesn't is in TWRP. I'm not sure if it's a battery safety issue because it's noticing how hot the device is but I was proven wrong with that too, put it in the freezer for 3 mins and it rebooted then too lol. I'm not sure what to do as even download mode reboots. Wtf. Idk if maybe there's some stock files I could attempt to flash through adb? Can anyone help?

have you tried to flash some stock rom? there is a thread around here which has some twrp backups on stock roms. maybe it helps to get into download mode and repair the phone with the Q.

jani0417 said:
have you tried to flash some stock rom? there is a thread around here which has some twrp backups on stock roms. maybe it helps to get into download mode and repair the phone with the Q.
Click to expand...
Click to collapse
Just did. Damn i thought for sure it was the answer, but nope, the phone has rebooted 3 times since i just restored the backup from that thread 20 mins ago. It feeezes for a sscond and then will reboot. Whats even worse is it soemtimes doesent let me charge the phone when powered down. Instead of showing the charging battery screen it just boots up into Android. Its highly annoying. I can get into download mode, it just won't stay there.

that suxx. did you unlocked the bootloader? maybe you should relock it.... it's just an idea, really don't have any more idea

jani0417 said:
that suxx. did you unlocked the bootloader? maybe you should relock it.... iitt's just out oan idea, really don't have any more idea
Click to expand...
Click to collapse
i want to see if twrp is causing the pgone to reboot of download mode. i need ghe stock recovery img for 60450 bu i cant find it.

carnivalrejectq said:
i want to see if twrp is causing the pgone to reboot of download mode. i need ghe stock recovery img for 60450 bu i cant find it.
Click to expand...
Click to collapse
HEre's the original recovery
https://mega.nz/#!NsEXkJZY!S-W9OtDSHVi3EBVcHBKdLX_Ru0yKrGI8g4saaHAtgPY

aleksandar.d123 said:
HEre's the original recovery
https://mega.nz/#!NsEXkJZY!S-W9OtDSHVi3EBVcHBKdLX_Ru0yKrGI8g4saaHAtgPY
Click to expand...
Click to collapse
Thanks. Unfortunately it didn't work. No matter what I do the phone reboots out of DL mode during the process and ruins it. I'm at My wits end with this phone. Have never had this many issues before. I've done everything. I even used the backup from that old thread to restore stock for 6450. All should've been well but I got reboots even on stock at 90% charged. What's very strange is the only thing I can do to keep this from rebooting is use YOUR kernel from the latest Flyme ROM. No idea why but reboots are minimal with it. They still happen but a lot less. All other ROMs and kernels have issues.

carnivalrejectq said:
Thanks. Unfortunately it didn't work. No matter what I do the phone reboots out of DL mode during the process and ruins it. I'm at My wits end with this phone. Have never had this many issues before. I've done everything. I even used the backup from that old thread to restore stock for 6450. All should've been well but I got reboots even on stock at 90% charged. What's very strange is the only thing I can do to keep this from rebooting is use YOUR kernel from the latest Flyme ROM. No idea why but reboots are minimal with it. They still happen but a lot less. All other ROMs and kernels have issues.
Click to expand...
Click to collapse
Sorry for your trouble, but i dont know why you havent send your device to warranty repair allready and instead of that you wrote your troubles across several threads

DallasCZ said:
Sorry for your trouble, but i dont know why you havent send your device to warranty repair allready and instead of that you wrote your troubles across several threads
Click to expand...
Click to collapse
I found him a flashable stock that he got to work. Part of, if not all, of his problem is I think he only has access to a sub-par pc or tablet or something. Anyway, I remember when I didn't know how important it is to have patience and not freak out, and quite a few people had the patience for me , and guided me. I learned. Perhaps this is where he is at. I post things that I have run into, and figured out to try and repay the kindness shown to me. He was trying on his own to figure it out, and that is WAY better than people who don't even try to search, and expect others to do everything for them. This is a community, and just like life, people are at different places. As long as someone is trying, I will try to help if I can. You can't send a rooted phone running CM for warranty.

EDIT: Turns out the reason the upgrade app wasn't working is because i didn't have enough space for the update to download on the PC . I didn't realize because the app never stated why it was restarting my phone or disconnecting so I just assumed it was related to why my phone kept restarting on all ROMs. Wow lol I feel so damn stupid for not thinking of this 2 days ago. Its installing now and hopefully this fixes my reboot issues. Thanks to everybody here for helping and answering my 1000 question's on every post. Really appreciate it.

carnivalrejectq said:
EDIT: Turns out the reason the upgrade app wasn't working is because i didn't have enough space for the update to download on the PC . I didn't realize because the app never stated why it was restarting my phone or disconnecting so I just assumed it was related to why my phone kept restarting on all ROMs. Wow lol I feel so damn stupid for not thinking of this 2 days ago. Its installing now and hopefully this fixes my reboot issues. Thanks to everybody here for helping and answering my 1000 question's on every post. Really appreciate it.
Click to expand...
Click to collapse
Hey......we all get flustered and forget the basics sometimes. Plus, for me, this phone doesn't respond like all the HTC, Nexus, and Samsung phones I've rooted and modded. That, and the insistence for every carrier/region to have their own variant, even on these cheaper phones. The T-Mobile Note 3 and 4 were even different depending on whether you had the black or white one! Hope this gets you back to normal, and if you don't have an SD card, at least get a cheap 8gb, and keep a stock backup on it. I've had that be a lifesaver more than once. Good luck my friend, and maybe stick to stock rooted? Lol

dongarritas said:
Hey......we all get flustered and forget the basics sometimes. Plus, for me, this phone doesn't respond like all the HTC, Nexus, and Samsung phones I've rooted and modded. That, and the insistence for every carrier/region to have their own variant, even on these cheaper phones. The T-Mobile Note 3 and 4 were even different depending on whether you had the black or white one! Hope this gets you back to normal, and if you don't have an SD card, at least get a cheap 8gb, and keep a stock backup on it. I've had that be a lifesaver more than once. Good luck my friend, and maybe stick to stock rooted? Lol
Click to expand...
Click to collapse
All is back to normal, no reboots. I do have an SD card and did have a backup the thing is though I accidentally saved another back up over the original with custom kernel so it was useless lol. And oddly the reboots sort of stopped happening right before but I was using the custom kernel from Flyme which is the only one that seemed to be working. I'm hoping that the issue is with root and not a hardware one from the phone getting to hot flashing things.