Related
Hi everyone, had a weird thing happen after I tried to upgrade to the Perfect Storm 1.5 ROM. I flashed the new radio & installed the ROM - everything seemed to go fine, but after I my phone came up, any app that I went into that required root didn't work. They all said my phone wasn't rooted... The superuser was still there. I tried doing a factory data reset but still ran into the same thing. So I flashed the previous radio back to my phone & went back to the other ROM that I was using - my phone at least acknowledges that it's rooted now & all my rooted apps work. But what the heck happened? Why did my phone want to act like it wasn't rooted? I thought about trying the other Gingerbread ROMS but I'm afraid of running into the same thing as I did with the Perfect Storm. Any thoughts / ideas? Thanks!
Gingeritis....try it
The Perfect Storm 1.5 ROM acting like it's NOT rooted?
Ok, thanks! How long have you been using this rom?
My issue has been plaguing me for several weeks now. I just stared developing for Android, so I'm a bit of a noob (forgive any obvious mistakes that I have made, or do make)
I have an HTC EVO 3D that I got about 8 months ago. One of the first things I did after I got it was root the puppy and flash a custom Gingerbread ROM to it. That worked great as a development tool for a while, with no issues, whatsoever.
After some time, I updated my custom Gingerbread ROM to a custom ICS ROM, which again, worked fine, minus the minor inconvenience of it occasionally rebooting when I would hit the debug icon on my IDE (Eclipse). That would only happen every once and a while. However, one day last week, all it did, when I hit debug, was reboot. I figured that the ROM was bad in some way, and flashed a custom JellyBean ROM to it. Same issue. I flashed another JB ROM(CM 10), with the same issue. After that, I've done everything that I can think of to fix this issue. I've tried flashing everything that Clockwork would let me flash (Dalvik, cache, did a factory reset, etc) I tried reformatting the SD card, and even tried 3 new ones. I tried reflashing the ROM, I tried 3 other computers, and even re installed Windows on one of them! In my experimentation, I have discovered that it also reboots when I try to record video with the native JB camera (I say that because I installed another camera app from the Play Store, and that works fine).
I'm thinking maybe a memory leak? I honestly have no idea.
HTC EVO 3D
HBOOT 1.40
S-OFF
Thanks in advance
So here is the issue. I have a verizon note 2 sch i605. I have had it for a few months. I used the casual method to unlock the bootloader and install a rooted rom. From there i installed jedi x rom since it was the best i could find at the time. Didnt really like any of the other roms out there, especially ones without touchwiz. Makes no sense to have a note 2 without s pen functionality right?
So i kept jedi x for a while. And in my searchings a month ago i saw it had a new version. I also saw a new version for jellybeans which i sort of liked before, and a jedimaster rom. I figured id try both since i am a flashaholic.
I went to install the jellybeans rom and it installed fine. Rebooted and it got to the galaxy note 2 screen (first screen) rebooted, and went right back into twrp. I figured it was strange. So i wiped dalvik and cache and rebooted again. Same thing. Strange x2. I then did factory reset, wiped dalik and cache. Same. I gave up on jellybeans figuring it was a bum rom.
After that i tried installing jedimaster. Installed fine. Wipe dalvik and cache. Reboot. Same issue as with jelly beans... strange x13... not sure what was happening, and figuring it had nothing to do with the roms, i quit on the new ones.
I then went to to new version of jedix titled jedixv12. I wanted to see if it would dirty flash, so i tried it. It did just fine. Wiped dalvik and cache. Rebooted. Booted up perfect. In playing around with it i noticed that superuser was gone and supersu replaced it. Opened supersu and it informed me there was no superuser binary! All my old apps still had permission, but no new ones could gain... weirrrrrd. So obviously that rom would do no good. I then wiped everything and fresh installed the rom. Worked fine again. No superuser binary still.
Ok so that rom sucked. I tried then to go to jellybeans from this new version of jedix. Still same problem.
So heres the question. Am i doing something wrong? I have flashed other roms to this device many times. I actually went from jedi x to jellybeans when i first got the device rooted! Now it wont? I can not flash any new roms to my device. I am stuck with jedi x for good unless i can fix this! I have no idea what the problem is since another version of jedi x installs perfectly and boots. It just seems like my device wont let go of jedi x.
Please help if you have any ideas. I am open to anything. I have exausted my knowledge base and i would like to pick yours now.
Also... looked around the internet and i cant find anyone with this issue at all. Not even close.
You may want to install twrp again, but this is just a blind suggestion. I seemed to have this problem before. Do you have check md5 selected in twrp?
Sent from my SCH-I605 using Tapatalk 2
JeramyEggs said:
You may want to install twrp again, but this is just a blind suggestion. I seemed to have this problem before. Do you have check md5 selected in twrp?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Nope. I have everything checked that was checked originally. I have changed nothing. As i said before, it used to be fine, and is fine when installing fresh copies of jedi x.
I havent tried reinstalling twrp. But i cant see why that should be an issue since it installs things fine.
w4rped said:
Nope. I have everything checked that was checked originally. I have changed nothing. As i said before, it used to be fine, and is fine when installing fresh copies of jedi x.
I havent tried reinstalling twrp. But i cant see why that should be an issue since it installs things fine.
Click to expand...
Click to collapse
Are you sure you are on the latest TWRP 2.5.0.0?
Also, in superuser you may have an option to update binaries.
But it sounds like your root might be borked and a complete and fresh unlock/reroot might not be a bad idea.
Also, as already mentioned. Are you verifying the md5 is good on your rom downloads?
JBeXX said:
Are you sure you are on the latest TWRP 2.5.0.0?
Also, in superuser you may have an option to update binaries.
But it sounds like your root might be borked and a complete and fresh unlock/reroot might not be a bad idea.
Also, as already mentioned. Are you verifying the md5 is good on your rom downloads?
Click to expand...
Click to collapse
The issue with superuser only happens when i install jedixv12. It is fine on my rom that i use right now. SuperSU is the problem i believe. It says that it cant find the binary and cant install one. Basically says screw you you arent rooted. But as soon as i revert back to my original jedi x rom it is fine.
I dont check md5 but i have downloaded the roms multiple times so i am pretty sure that one of the downloads should have been good. I am attempting to install a new recovery to see if it fixes my issues.
w4rped said:
The issue with superuser only happens when i install jedixv12. It is fine on my rom that i use right now. SuperSU is the problem i believe. It says that it cant find the binary and cant install one. Basically says screw you you arent rooted. But as soon as i revert back to my original jedi x rom it is fine.
I dont check md5 but i have downloaded the roms multiple times so i am pretty sure that one of the downloads should have been good. I am attempting to install a new recovery to see if it fixes my issues.
Click to expand...
Click to collapse
May not necessarily need a new recovery, maybe just make sure you're on the updated one. Are you still on the twrp version included with casual unlock? If so, it is likely out of date. If you aren't already aware, you can just install the goo manager app from playstore, tick menu, then install open recovery script and it will flash and bring you current
JBeXX said:
May not necessarily need a new recovery, maybe just make sure you're on the updated one. Are you still on the twrp version included with casual unlock? If so, it is likely out of date. If you aren't already aware, you can just install the goo manager app from playstore, tick menu, then install open recovery script and it will flash and bring you current
Click to expand...
Click to collapse
I was on the original one that came with casual. I just updated to the newest using rom toolbox pro.
Just as a weird side note... i updated and tried to install jellybeans again. After the install it says "your device does not seem to be rooted. Install supersu now?" I swiped to install and it just rebooted. Then same thing as before. Stuck at samsung galaxy note 2 screen then restarts itself and goes back to twrp. I am soooo confused. Thinking about trying to use cwm see if it makes a difference.
UPDATE:
Tried cwm. Same results. Obviously not a problem with recovery. Very confused.
Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
r1k1v1 said:
Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
Click to expand...
Click to collapse
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
kunal1540 said:
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Hmm, I don´t remember that the BlackBox 2.0.2 had any Framework...thats why I did a manual installation. But I will try the new version 2.1. Hopefully the problems may have been solved.
boomboomer said:
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Interesting. So I have to apply mods one by one? Or can I add multiple mods because corruption has already been solved?
On a side note, when I boot the phone the red exclamation mark that used to appear has disappeared. Does that means that I somewhat reseted the flash counter to 0?
I purchased an AT&T SGH-i717 and was told everything worked. When I checked it out, everything seemed fine too. After using it for a couple hours I realized it just seemed to reboot at random. I rebooted into recovery and did a factory reset and wiped the cache. After rebooting it...it would get stuck at the AT&T screen. I then installed the latest stock rom 4.4.2 using Odin and it booted up fine but I got the no sim card error. I put in an AT&T sim card and rebooted but got a sim not provisioned error. I then tried a T-Mobile card and I didn't get the error and it showed signal bars but when I tried to dial it said emergency calls only. I tried a Verizon sim card just to see what kind of error I would get but it was just the same as the T-Mobile sim. I thought it might a corrupted rom so I tried installing the latest nightly CyanogenMod using CWM but got error status 7. I then tried various custom and stock roms including AOKP, BeanStalk, and several different versions of CyanogenMod but always got the same error status 7 msg. I then came across a forum posts stating that CWM no longer works for the SGH-i717. I downloaded the latest TWRP touch recovery and was able install the latest stable CyanogenMod but it would not boot past the animated CyanogenMod logo even after sitting for over an hour. At that point I gave up and decided to just go back to the stock rom. I rebooted into TWRP and the slide to unlock would not work anymore. I had to install CWM using Odin which allowed me to flash back to the stock 4.4.2 rom. After doing another factory reset and wiping the cache then rebooting...the touch screen stopped working. I then flashed it back to the stock 4.0.4 rom but the touch screen still does not work. While trying to figure out what happened I realized the pen still works and touch screen buttons on the bottom but thats it. Also the pen only works on the screen and not on the touch screen buttons. I've been messing with this for 3 days and will probably just sell it for parts but wanted to post this problem so if anyone else had this problem they would know what I've already tried. I did also take apart the phone and clean the connections but that didn't help either.
If anyone has a suggestion for something I haven't tried...please let me know. My last attempt will be install the Padawan JB rom from this post:
http://forum.xda-developers.com/showthread.php?t=1907203
Thanks
Right out of tge gate, there is no stock 4.4.2 for this device. Not official anyway. 4.1.2 is official OS.
Status 7 means your recovery needs updating.
CWM does work and the newest CWM touch is just dandy.
I would try going all the way back. You need to be totally clean.
Factory
Cache
Davlik
Format
Go to Kies and go with emergency firmware recovery.
Get back to stock and see what is working.
Clean clean clean, the best way for anyone to help you. You would be at the best starting point.
Maybe do a little reading as many of your issues have been documented and solved. None of them are major.
Start from scratch and folks can get you running again.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
captemo said:
Right out of tge gate, there is no stock 4.4.2 for this device. Not official anyway. 4.1.2 is official OS.
Status 7 means your recovery needs updating.
CWM does work and the newest CWM touch is just dandy.
I would try going all the way back. You need to be totally clean.
Factory
Cache
Davlik
Format
Go to Kies and go with emergency firmware recovery.
Get back to stock and see what is working.
Clean clean clean, the best way for anyone to help you. You would be at the best starting point.
Maybe do a little reading as many of your issues have been documented and solved. None of them are major.
Start from scratch and folks can get you running again.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Click to expand...
Click to collapse
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
cycloneus said:
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
Click to expand...
Click to collapse
well my friend, you had the phone apart once already, I am no expert, but my guess is this is no software issue. maybe some connections came loose. in my time here, I have not come across this issue. I do not have the brain pan nor the courage to take my phone apart.
good luck to you.
maybe someone else will mosey on by.
cycloneus said:
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
Click to expand...
Click to collapse
My guess is the digitizer has gone bad if odin &/or kies can't fix the issue at hand.