This is the second time this has happened!! i happen to reboot my phone, i cant get it to fully boot back up. it only gets as far as the Samsung Galaxy Note3 screen with the yellow and red writing in the top corner. The only way i can get back up and running is if i flash a rom or an old backup. Any pointers or ideas would be greatly appreciated..
btw... Im running fre3 2.13 with calm kernel
Thanks
UPDATE: I re-flashed fre3 rom did a clean install. What im finding out is when i "Titanium Backup" freeze an like "Polaris Office" or any other bloat, i cannot defrost it back and if i reboot the phone right after good luck getting it booted back up. Now im really left clueless...
ImEVO said:
This is the second time this has happened!! i happen to reboot my phone, i cant get it to fully boot back up. it only gets as far as the Samsung Galaxy Note3 screen with the yellow and red writing in the top corner. The only way i can get back up and running is if i flash a rom or an old backup. Any pointers or ideas would be greatly appreciated..
btw... Im running fre3 2.13 with calm kernel
Thanks
UPDATE: I re-flashed fre3 rom did a clean install. What im finding out is when i "Titanium Backup" freeze an like "Polaris Office" or any other bloat, i cannot defrost it back and if i reboot the phone right after good luck getting it booted back up. Now im really left clueless...
Click to expand...
Click to collapse
That may help me as well, I reflashed everything this morning, with that 2.13 update, clean install. Then proceeded to debloat, I typically don't freeze anything I just uninstall what I don't want. Today was the first time I uninstalled Polaris, would not boot, had to flash again and start fresh. I know this doesn't really help, but at least maybe this narrows things down a bit.
Update: It's not Polaris, left that intact, just cleaned up the rest of the crap that I usually do and now my phone won't boot. Wonder if it has anything to do with the ART framework that was added in this update, Think I'm going back to 2.12
SanityBroken said:
That may help me as well, I reflashed everything this morning, with that 2.13 update, clean install. Then proceeded to debloat, I typically don't freeze anything I just uninstall what I don't want. Today was the first time I uninstalled Polaris, would not boot, had to flash again and start fresh. I know this doesn't really help, but at least maybe this narrows things down a bit.
Update: It's not Polaris, left that intact, just cleaned up the rest of the crap that I usually do and now my phone won't boot. Wonder if it has anything to do with the ART framework that was added in this update, Think I'm going back to 2.12
Click to expand...
Click to collapse
I'm thinking its the kernel ,I flashed previous version of beast.. I'm going to debloat some now, I'll report back
ImEVO said:
I'm thinking its the kernel ,I flashed previous version of beast.. I'm going to debloat some now, I'll report back
Click to expand...
Click to collapse
Went back to 2.12, uninstalled all of the same things and booted right up. I'm really leaning towards the framework changes in the update being the culprit. Let me know how the Kernel change works.
SanityBroken said:
Went back to 2.12, uninstalled all of the same things and booted right up. I'm really leaning towards the framework changes in the update being the culprit. Let me know how the Kernel change works.
Click to expand...
Click to collapse
Kernel was no go same problems.. I re flashed free rom and 2.12 update and debloated and I have no issue now. .
you may have found the culprit lol
Same thing happened to me yesterday I thought I just removed something important but seeing this makes me think differently I want to ditch all the crap I have never even once used and I did a reboot and got the Samsung screen with the lettering then black screen lame
harrybear25 said:
Same thing happened to me yesterday I thought I just removed something important but seeing this makes me think differently I want to ditch all the crap I have never even once used and I did a reboot and got the Samsung screen with the lettering then black screen lame
Click to expand...
Click to collapse
Just go back to 2.12 and go nuts on the debloating lol.. That's what I did
SanityBroken said:
Went back to 2.12, uninstalled all of the same things and booted right up. I'm really leaning towards the framework changes in the update being the culprit. Let me know how the Kernel change works.
Click to expand...
Click to collapse
Have you tried debloating in 2.12 and flashing 2.13 on top??
UnAshamed 1:1six
ImEVO said:
Have you tried debloating in 2.12 and flashing 2.13 on top??
UnAshamed 1:1six
Click to expand...
Click to collapse
No, I did a clean install. That might be worth a shot, nothing wrong with a little dirty flashing now and then. Today is my monday, don't like taking too many chances with the phone during the week. If you get the chance to try it lmk how it works out.
ImEVO said:
Have you tried debloating in 2.12 and flashing 2.13 on top??
UnAshamed 1:1six
Click to expand...
Click to collapse
Got bored, dirty flashed 2.13 over de-bloated 2.12, so far, so good. Kind of a pain, but it's a workaround. Good thinking thx
SanityBroken said:
Got bored, dirty flashed 2.13 over de-bloated 2.12, so far, so good. Kind of a pain, but it's a workaround. Good thinking thx
Click to expand...
Click to collapse
What was the pain?
UnAshamed 1:1six
ImEVO said:
What was the pain?
UnAshamed 1:1six
Click to expand...
Click to collapse
Only a hassle if you start fresh again. Plus, I found another app I want to get rid of, but I can't. I'm going to try to remove it manually when I get home from work, see if TiBu is the problem.
In original post, you stated you get stuck at Sammy screen with yellow and red writing... are you referring to the pre recovery screen? If so, try booting into download mode, but select reboot phone when the option comes up. I've experienced issues with the N3 not wanting to boot a couple times after rooting and/or flashing, but was able to get it to fire up by doing that...
Sent from my SM-N900P using xda app-developers app
SanityBroken said:
Only a hassle if you start fresh again. Plus, I found another app I want to get rid of, but I can't. I'm going to try to remove it manually when I get home from work, see if TiBu is the problem.
Click to expand...
Click to collapse
Which app? Maybe I removed it already..lol
UnAshamed 1:1six
emazzy72 said:
In original post, you stated you get stuck at Sammy screen with yellow and red writing... are you referring to the pre recovery screen? If so, try booting into download mode, but select reboot phone when the option comes up. I've experienced issues with the N3 not wanting to boot a couple times after rooting and/or flashing, but was able to get it to fire up by doing that...
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
I'll try it next time thanks
UnAshamed 1:1six
ImEVO said:
Which app? Maybe I removed it already..lol
UnAshamed 1:1six
Click to expand...
Click to collapse
Ok, just got home. Went to system-app with Root Browser, deleted the app I didn't want, rebooted, everything is fine. Kinda makes me want to wipe everything, and flash without 2.12 and see if it is Titanium that was screwing everything up. Haven't decided yet, I'll let ya know what happens if I do.
Problem Solved
@ImEVO, just wiped everything and did a clean install of 2.1 and went straight to 2.13. I downloaded a random "root uninstaller" from the playstore and debloated with no issues, must be something with Titanium not playing well with the update.
SanityBroken said:
@ImEVO, just wiped everything and did a clean install of 2.1 and went straight to 2.13. I downloaded a random "root uninstaller" from the playstore and debloated with no issues, must be something with Titanium not playing well with the update.
Click to expand...
Click to collapse
Nice, I'm going to have to do that, thanks
I guess it's just us 2 with this issues lol
UnAshamed 1:1six
Related
I'm running UnNamed 1.3.0 right now with no themes applied but I have everything setup the way I like it. I'd like to do a full 1.3.1 flash and try the Blue Monkey theme.
Is the best way to do this
A) backup apps with Titanium, backup with CWM, full wipe, flash 1.3.1 full, then flash blue monkey, restore apps with Titanium
B) backup with CWM, flash 1.3.1 over 1.3, then flash blue monkey theme
C) other
I'm unclear on whether I need to do a wipe going from 1.3 to 1.3.1 if it's a full flash and not the 1.3to1.3.1 update.
Thanks in advance for any help.
dont need to wipe. just flash it.
You can wipe cache and dalvik to clean up, but you don't need to wipe.
Alright, I did a backup then installed 1.3.1 and rebooted. Everything works fine and the phone looks exactly how I left it except in the about phone area it says I'm running 1.3.1 now.
Rebooted and backed up again.
Installed from zip the Blue Monkey theme and rebooted. I'm running Go Launcher Ex so I went in and cleared it as the default. Pressed the home button and chose TwLauncher. Everything looks fine but I'm not seeing the theme applied. I still have the same background live wallpaper and icons. The lock screen is still WidgetLocker.
Thoughts?
EDIT:
Apparently installing the theme a second time did the trick. I now see the new icons.
Knips178 said:
EDIT:
Apparently installing the theme a second time did the trick. I now see the new icons.
Click to expand...
Click to collapse
Right on. That's good advice for everyone. Sometimes things need more than one flash.
Sent from my páhhōniē
I had the same thing happen with that theme on 1.3.1. I knew something was up when it flashed really fast. A second flash took longer and worked properly.
Sent from my SAMSUNG-SGH-I777 using xda premium
Can anyone give a quick reply as to why that happens with flashing? Is it a problem with CWM, the zip files, or the process?
Knips178 said:
Can anyone give a quick reply as to why that happens with flashing? Is it a problem with CWM, the zip files, or the process?
Click to expand...
Click to collapse
Lol, I think alot of us wish we knew why. I don't think anyone has figured it out. It's not limited to our phone.
Sent from my páhhōniē
gr8hairy1 said:
Lol, I think alot of us wish we knew why. I don't think anyone has figured it out. It's not limited to our phone.
Sent from my páhhōniē
Click to expand...
Click to collapse
I think I have posted this twice today and the third time might...be the charm. You guys have to remember to check and mount your system and data in recovery before flashing ROM's or Themes. It should alleviate any re-flashing or multi-flash scenarios for you guys.
Additional: Also if some of you guys are having a bad or fast install you might want to re-download the Theme. I know in talking with Jivy26 (Blue Monkey Themer) the initial release of the update of 1.3 (For you quick and early adopters) had an issue and was pulled, repacked and posted again. Try a fresh copy.
hkeyman said:
I think I have posted this twice today and the third time might...be the charm. You guys have to remember to check and mount your system and data in recovery before flashing ROM's or Themes. It should alleviate any re-flashing or multi-flash scenarios for you guys.
Click to expand...
Click to collapse
Very true. But it's still only a 'should' not have to flash twice, not a certainty that it won't need the flash again.
It doesn't explain the times we do that and it still needs a reflash (usually cm7).
Sent from my páhhōniē
gr8hairy1 said:
Very true. But it's still only a 'should' not have to flash twice, not a certainty that it won't need the flash again.
It doesn't explain the times we do that and it still needs a reflash (usually cm7).
Sent from my páhhōniē
Click to expand...
Click to collapse
I used to see the same thing with flashing multiple times, thought it might have been a bad root install or something wrong with the ROM itself. Ever since implementing the mentioned procedure into my regimen of updates. I only flash once (Unless of course there is in fact something wrong with the package).
I have an i777 (rooted, ROMd, etc) and my friend does also. She put a passcode on hers for some reason and apparently there was some type of software malfunction and she can't get her phone unlocked. So instead of making her wait weeks for Samsung to fix it, I volunteered to fix it myself.
I've already tried Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package from this thread: http://forum.xda-developers.com/showthread.php?t=1311081
Everything worked fine but, when the phone booted, the screen asking for the passcode was still present.
Does anyone know of another way to try this out? I promised her I'd have it done by tomorrow and that I'd also put ICS on it . And I really don't want to have to tell her I couldn't do it.
Thanks!
EDIT: I've solved this issue (thankfully)! I went into the stock Samsung recovery and chose to wipe data. It asked for a password and I kept entering random characters until it told me if I kept entering them it was going to wipe the phone's data. So it wiped the phones data and everything is now fine. I've rooted it using Entropy's tool from above and I am currently putting AOKP on it .
It's impossible
Sent from my SGH-T989 using XDA
gokrisgo said:
It's impossible
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Is there a way to do it with an official Samsung firmware through the recovery that is preloaded on the device?
gokrisgo said:
It's impossible
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Oh really? my previous ROM was passcode protected,, I installed ICS over the weekend and it's never prompted me since then.passcodes seem to be flaky, sometimes mine would carry over from one ROM to another, other times it wouldn't.
Don't know exactly what causes it, I guess maybe try some different ROMs and just be sure to do a full wipe each time and cross your fingers that it disappears
twiggums said:
Oh really? my previous ROM was passcode protected,, I installed ICS over the weekend and it's never prompted me since then.passcodes seem to be flaky, sometimes mine would carry over from one ROM to another, other times it wouldn't.
Don't know exactly what causes it, I guess maybe try some different ROMs and just be sure to do a full wipe each time and cross your fingers that it disappears
Click to expand...
Click to collapse
See, I would wipe it, but when I go to wipe it (it doesn't have CWM, just the stock Samsung recovery), it asks for a password. I think I'm screwed .
Nevermind! I've got through the password by getting it wrong too many times. This caused the phone to wipe, and now I have exactly where I need it!
Able to push a kernel with CWM via adb? (sorry don't remember if USB debug is checked by default)
This is interesting.
I really want Entropy looks into it.
votinh said:
This is interesting.
I really want Entropy looks into it.
Click to expand...
Click to collapse
Lol I'm sure he could come up with something
Good evening XDA -people.
I do not really want to bother anyone, but I'm sure I do.
SO. I'm quite stressed about this as it happens all the time.
I got the PredatorUnity Rom (1.1 I guess, but it already happened before)
And if I try to do a nandroid backup it says it does work, sometimes it does NOT work though. so, I restart after that backup (or just a normal reboot, any kind of reboot causes this, even if I just go into recovery and don't change anything) the rom starts and boots alright for a few seconds and then does a hot restart.
So once this made me SO angry, I changed rom. then it actually went alright until I restored my apps via Titanium. then the same thing happened. Don't worry, I'm not that dumb anymore to backup my system apps. Anyway I located the apps that caused my bootloops. Chrome, Busybox etc. I THOUGHT SO. It looks like theres more.
The problem now is, everything worked well for a few days. EVEN 1 REBOOT WORKED! so now, I went into recovery to do a nand backup via rom manager and then just this..
so sorry. wi'll give thanks to any useful comment
oh yea. just for you to know if you need it;
S-Off
HBOOT-1.49.1107
Radio: 0-11.23.3504.09_M2
GSM
yes.
Don't hate. I've looked around and haven't found any case like this..
Comments Withdrawn
zcink said:
It almost sounds like you've got a bad recovery. I would reflash it.
which recovery are you using? The latest 4ext seems to work best. Lots of roms here support it.
If you get everything working again, I would redo all your backups also.
Click to expand...
Click to collapse
Thanks man
I am using the latest 4ext touch.. and I flashed it only about a week ago! I've had these problems before- and after the recovery change. should I reflash it anyway?
Comments Withdrawn
zcink said:
It wouldn't hurt anything to reflash it but if you've had these problems before and after then its probably not your problem.
Have you tried other roms? And still get these problems?
One guy had a thread where he was getting bootloops and turned out to be a physical problem where his battery was loose:
http://forum.xda-developers.com/showthread.php?t=1705261
Click to expand...
Click to collapse
Okay I won't take it as an option then. At least not for now..
I did, but as I said it broke after I restored my apps via titanium..
Yeah, I've seen that thread and I can be sure it isn't this as it doesn't reboot randomly. only afer a reboot. Like, you wanna break your phone? reboot it! haha
I really love Sense 4 and the predators' rom is really awesome, but I'd even try a AOSP rom. Onbly problem is, I don't think I could restore sms (I saved them via the stock sense sms)
Oh and if this could be a problem; today I downloaded BootManager lite and saved my boot.img? didn't do anything but might have been a problem for the backup?? Ah I dunno...
Comments Withdrawn
zcink said:
Guess I'm out of ideas also.
Wondering about Titanium backup pro though. It updated when I went on the market the other day. I bought the pro version awhile back. Now after the update when I go in and try to remove something from a rom, it tells me it can't.
I used to make user app and then delete or uninstall. Won't do it anymore with Titanium Backup. However, Rom Toolbox pro will.
Click to expand...
Click to collapse
aw man.. Thansk anyway
I don't know exactly what you mean, because all I ever did was backup and restore
I do have Pro, but just because of Lucky Patcher haha
So Rom Toolbox Pro is better? (got that too, not using it tho)
Alright. it seems like all I can do right now is; flash the latest radio, do a super wipe, (now comes the worst) restore an old nand. sense backup, restore my sms, download another sms backup program, use it, do a super wipe, etc etc etc. and install the aosp rom (sense 3.6 feels ugly after sense 4..) or whatever else I find and restore the sms that way and then live like never before.
OR I try to install the latest predator, which has a new base.
I'll do the last thing haha
Use twrp everyone says 4ext is great but get twrp
Hit the thanks button if i helped
My SGS2 has been running AOKP for a few months now, all of a sudden today the phone keeps rebooting itself every few minutes. I have tried wiping cache, full wipe etc.... I tried installing a different kernel and also a different rom, now it's on ShoStock, but it continues to loop. Also I have flashed the newest version of CWM but everytime I reboot the phone it reverts back to the old version. Any ideas help?
Still Mostly Harmless said:
My SGS2 has been running AOKP for a few months now, all of a sudden today the phone keeps rebooting itself every few minutes. I have tried wiping cache, full wipe etc.... I tried installing a different kernel and also a different rom, now it's on ShoStock, but it continues to loop. Also I have flashed the newest version of CWM but everytime I reboot the phone it reverts back to the old version. Any ideas help?
Click to expand...
Click to collapse
How do you flash CWM?
I got no clue on the issue at hand other than to go back to stock and see if it persists, if it does its hardware.
Is your name a throwback to the movies/books or something else? In hoping something else...
Good luck bro!
Clay
Team Pirate
Sent from my PINK GS2 using xda app
Thanks guys, another issue I noticed is that the power button was acting really strangely. When you pressed it it wouldnt turn off the phone it would just bring up the restart menu or it wouldn't register at all, so I thought I had a hardware issue. Any finally I ran this kernel cleaner:
http://forum.xda-developers.com/showthread.php?t=1363738
did a full wipe etc...installed rom and then kernel and that has seem to do the trick. Going to hope that it continues to work and I don't have to go out and buy a new phone!
Looks like I have some donating to do.
Don't use ROM manager to flash cwm. As that is what it sounds like u did when u said u "flashed" cwm. Our kernels have recovery built in.
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
Don't use ROM manager to flash cwm. As that is what it sounds like u did when u said u "flashed" cwm. Our kernels have recovery built in.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thats what I was thinking :highfive:
I download the latest CWM (6.0.1.0), put the zip on my SD then boot into recovery and installed it as a zip, is that incorrect?
Still Mostly Harmless said:
I download the latest CWM (6.0.1.0), put the zip on my SD then boot into recovery and installed it as a zip, is that incorrect?
Click to expand...
Click to collapse
Yeah, that's probably incorrect.
For our phones, CWM is included in all custom kernels and isn't separate from the kernel at all. The only way to update CWM is to flash an updated custom kernel, like if Siyah or NEAK were to update for instance.
Don't bother trying to update CWM all the time, there's honestly little to no benefit from even trying and you'll likely end up with problems instead like you did this time. The version of CWM included with the custom kernels available is more than sufficient, just stick with those instead of trying to update it separately.
So I thought I fixed it but at last I haven't. After running the kernel cleaner, installing different roms/kernels the phone still boots for no reason after a while, not as often but at least 2-5 times a day. I am have no idea what's going on.
Still Mostly Harmless said:
So I thought I fixed it but at last I haven't. After running the kernel cleaner, installing different roms/kernels the phone still boots for no reason after a while, not as often but at least 2-5 times a day. I am have no idea what's going on.
Click to expand...
Click to collapse
You tried going to stock and seeing if the problem persists? For my brother it was an app so keep that in mind as well
clay101eve said:
Is your name a throwback to the movies/books or something else? In hoping something else...
Good luck bro!
Clay
Team Pirate
Sent from my PINK GS2 using xda app
Click to expand...
Click to collapse
still awaiting an answer!
Have you noticed if the phone is getting really hot around the time it's rebooting?
Clay
Team Pirate
Sent from my PINK SGH-I777
clay101eve said:
still awaiting an answer!
Have you noticed if the phone is getting really hot around the time it's rebooting?
Clay
Team Pirate
Sent from my PINK SGH-I777
Click to expand...
Click to collapse
Yes it is definitely from my favorite series of books. This is one of the only forums I visit that I couldn't get just Mostly Harmless.
Doesn't really get hot, but after a while the power button stops responding and only time fixes this or a fresh install of a kernel. I formatted my SD card and the internal memory (without grabbing my pictures ) and any app I install is new from the market.
There were two main roms I wanted to try after I finally S-OFF'd my phone yesterday. Hatka Supreme 1.1.0 and Carbon. Neither of these worked and I'm glad that I backed up my S-OFF rooted stock rom. Hatka Supreme, the guy states its best to use Beast Mode kernal with the rom, which I flashed after I installed the room, and it just randomly reboots at the splash screen/a few seconds after getting into Android, so I restored my stock and everything worked fine. Next, I tried Carbon, and it just sat there at the carbon flash screen for like 20 minutes, so again, I had to restore to stock. Is there something I'm doing wrong? Is there a difference between Original Android Development and Android Development? Should I be looking at the original or what? I'm really lost, I'm going to try another rom, hopefully someone replies to this before it finishes downloading. Thanks for the help.
EDIT: I'd rather just sit and wait to see if someone replies before I waste time downloading another rom...any help would be appreciated.
rejectedjs said:
There were two main roms I wanted to try after I finally S-OFF'd my phone yesterday. Hatka Supreme 1.1.0 and Carbon. Neither of these worked and I'm glad that I backed up my S-OFF rooted stock rom. Hatka Supreme, the guy states its best to use Beast Mode kernal with the rom, which I flashed after I installed the room, and it just randomly reboots at the splash screen/a few seconds after getting into Android, so I restored my stock and everything worked fine. Next, I tried Carbon, and it just sat there at the carbon flash screen for like 20 minutes, so again, I had to restore to stock. Is there something I'm doing wrong? Is there a difference between Original Android Development and Android Development? Should I be looking at the original or what? I'm really lost, I'm going to try another rom, hopefully someone replies to this before it finishes downloading. Thanks for the help.
EDIT: I'd rather just sit and wait to see if someone replies before I waste time downloading another rom...any help would be appreciated.
Click to expand...
Click to collapse
Did you do a full wipe? System, factory reset, dalvik?
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
Did you do a full wipe? System, factory reset, dalvik?
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
It's probably your recoverys fault. On my last DNA I had nothing but failures. Once it took at least 30 times to get a Rom installed. Never solved the issue on that phone. I just soffed my new DNA yesterday, installed the newest cwm touch and flashed 4 different roms with no problem. Try re-flashing cwm touch.
pio_masaki said:
Did you do a full wipe? System, factory reset, dalvik?
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
Yes, still the same thing, I'm not saying I didn't do that the first time though, that's like the basics of installing a rom.
str8upx said:
It's probably your recoverys fault. On my last DNA I had nothing but failures. Once it took at least 30 times to get a Rom installed. Never solved the issue on that phone. I just soffed my new DNA yesterday, installed the newest cwm touch and flashed 4 different roms with no problem. Try re-flashing cwm touch.
Click to expand...
Click to collapse
Do you think its TWRP's fault? After I found out there was no way to mount USB storage in TWRP I wanted to switch to CWM, but sadly I don't know how.
rejectedjs said:
Yes, still the same thing, I'm not saying I didn't do that the first time though, that's like the basics of installing a rom.
Do you think its TWRP's fault? After I found out there was no way to mount USB storage in TWRP I wanted to switch to CWM, but sadly I don't know how.
Click to expand...
Click to collapse
You could use the goomanager from the play store or use fastbook flash recovery cwm.img
Edit: for the touch version of cwm fastboot is required.
str8upx said:
You could use the goomanager from the play store or use fastbook flash recovery cwm.img
Edit: for the touch version of cwm fastboot is required.
Click to expand...
Click to collapse
I would rather use goomanager, because it seems easier, but the only thing it seems to be able to download is the twrp image. How would I set it to cwm?
I have canvas 2 running on suvi6 Jupiter rom i have some prob with this when i reboot some icon on home screen will disappear, i found that those apps which r installed on ext sd card its icon will disappear from home screen, but apps working in apps list, only icon from home screen disappeared.
Other problem is that while incoming a call i cannot see full picture of caller becoz half screen is black and half picture can be seen.
Please help me
Sent from my Micromax A110 using xda app-developers app
rejectedjs said:
I would rather use goomanager, because it seems easier, but the only thing it seems to be able to download is the twrp image. How would I set it to cwm?
Click to expand...
Click to collapse
Sorry I was mistaken, goomanager installs twrp not cwm.
Fastboot is easy to use, I'm at work so I can't to a step by step til I get home later. You should be able figure it out but if not I will help when I get home.
str8upx said:
Sorry I was mistaken, goomanager installs twrp not cwm.
Fastboot is easy to use, I'm at work so I can't to a step by step til I get home later. You should be able figure it out but if not I will help when I get home.
Click to expand...
Click to collapse
I don't know if you knew this already but I s-offed using moonshine, is that a problem? I installed cwm and tried installing hatka again and it did the same thing, restart like every three seconds into android. I don't know what to do anymore.
kundan.lohar said:
I have canvas 2 running on suvi6 Jupiter rom i have some prob with this when i reboot some icon on home screen will disappear, i found that those apps which r installed on ext sd card its icon will disappear from home screen, but apps working in apps list, only icon from home screen disappeared.
Other problem is that while incoming a call i cannot see full picture of caller becoz half screen is black and half picture can be seen.
Please help me
Sent from my Micromax A110 using xda app-developers app
Click to expand...
Click to collapse
Pretty sure you're in the wrong forum.
From my S-Off BadSeed DNA
rejectedjs said:
There were two main roms I wanted to try after I finally S-OFF'd my phone yesterday. Hatka Supreme 1.1.0 and Carbon. Neither of these worked and I'm glad that I backed up my S-OFF rooted stock rom. Hatka Supreme, the guy states its best to use Beast Mode kernal with the rom, which I flashed after I installed the room, and it just randomly reboots at the splash screen/a few seconds after getting into Android, so I restored my stock and everything worked fine. Next, I tried Carbon, and it just sat there at the carbon flash screen for like 20 minutes, so again, I had to restore to stock. Is there something I'm doing wrong? Is there a difference between Original Android Development and Android Development? Should I be looking at the original or what? I'm really lost, I'm going to try another rom, hopefully someone replies to this before it finishes downloading. Thanks for the help.
EDIT: I'd rather just sit and wait to see if someone replies before I waste time downloading another rom...any help would be appreciated.
Click to expand...
Click to collapse
I'm no expert, but when u flashed hatka, did u reboot into the system before flashing beast mode kernel? Flashing a kernel in the same recovery session is a no no. Also, beast mode is not compatible with carbon, fyi.
Sent from my HTC6435LVW using Tapatalk 4 Beta
kelvinnotcalvin said:
I'm no expert, but when u flashed hatka, did u reboot into the system before flashing beast mode kernel? Flashing a kernel in the same recovery session is a no no. Also, beast mode is not compatible with carbon, fyi.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I did that the first time, and thats when I started experiencing it, so I figured that was the problem. So I restored to stock, and then just tried flashing the rom and booting, still same thing, rebooting every 5 seconds. Sometimes I'm able to get into settings, scroll up and down a few times, and then it reboots.
EDIT: If I remember correctly, I didn't even flash beast mode kernel after I flashed carbon.
rejectedjs said:
EDIT: If I remember correctly, I didn't even flash beast mode kernel after I flashed carbon.
Click to expand...
Click to collapse
If you had you never would have seen the carbon boot animation I don't think, just a white scrambled screen.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
If you had you never would have seen the carbon boot animation I don't think, just a white scrambled screen.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
What exactly is the problem I'm experiencing here? x.x Of all roms I REALLY wanted to try Hatka, why me...
rejectedjs said:
What exactly is the problem I'm experiencing here? x.x Of all roms I REALLY wanted to try Hatka, why me...
Click to expand...
Click to collapse
I've had the same sort of thing happen to me when we first started working with CM. I had to lock up and run the RUU then unlock again, started flashing normally again after that.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
I've had the same sort of thing happen to me when we first started working with CM. I had to lock up and run the RUU then unlock again, started flashing normally again after that.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
You mean you want me to go back to pure stock and soff all over again?
rejectedjs said:
You mean you want me to go back to pure stock and soff all over again?
Click to expand...
Click to collapse
I don't want you to do anything, in was just saying what I did to correct it when it happened to me.
And no, I didn't day s-on, I said relocked, the RUU won't run on an unlocked device. Locked and son are different.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
I don't want you to do anything, in was just saying what I did to correct it when it happened to me.
And no, I didn't day s-on, I said relocked, the RUU won't run on an unlocked device. Locked and son are different.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
I've never had so many problems just trying to flash a Rom before, this is crazy...I'm seriously at a loss about what to do other than stay on rooted stock
bump?..I really want some help..
Did you figure it out? I'd do what pio said. He's kind of amazing. He's a very smart man who most likely knows what he's doing
Sent from my HTC6435LVW using xda app-developers app