Related
I was running Eternity version 116 for a long time, and decided i should upgrade to a more recent rev. I tried flashing v236 (and 238 and various versions in between) and all appears to go well, I get a message for successfully installing, but on first reboot, I get stuck on the splash screen. While I haven't tried many ROMs, I always wipe first. I am currently running Bamf Forever. But for whatever reason, I just can't get Eternity to load. Any suggestions? Thanks!
If you wiped data first and didn't get a bad download (if you've tried multiple versions, that would be very unlikely) then there really wouldn't be a logical reason for it not to work. All I can tell you is that it takes a long time (5 minutes maybe) to boot up the first time you flash a new ROM, I think it's because it zipaligns your apps. Hope you figure it out, if you find out what the problem was, let me know.
I've let it boot up for hours, but it never gets past the splash screen.
are you wiping data/cache/dalvik
Bigandrewgold said:
are you wiping data/cache/dalvik
Click to expand...
Click to collapse
Yes, wiping everything. I don't seem to have a problem installing other ROMs, just Eternity.
disregard. i got 216 to work. i don't know wtf was going on. but i'm happy now.
Glad you got it working. There have been some significant changes since 216 that makes it worth your time to upgrade to R238.
I figured out what the problem was. turns out all i needed to do was update CWM. now all versions flash fine. I was using a 3.0 version of CWM.
I don't know what happened. Or why it won't work.
When Safestrap was originally finished, I installed Hyperdrive without a problem. An update came, I downloaded and installed. It made it so I couldn't use HotSpot anymore. So, I figured it was the Rom, and I installed Jellybean Rom. I didn't like it. I tried to install the original Hyperdrive I had, and once its installed and reboots, the lights come on for one second and shut off. Downloaded the newest Hyperdrive, same issue.
The instructions say wait for 10 minutes. I did, and longer. (Range usually 20-40 minutes)
Last night I wanted to try again, (downloaded newest hyperdrive. I have sloooooow internet. Took 5 hours to finish). So, I tried installing today following the instructions, same issue. It installs and says everything is fine, reboot, safestrap pops up, loads normally through that, and the lights are on after like it starts with Stock, lights shut off, phone stops working.
When this happens, the phone does not respond to anything. Power does nothing. I waited 45 minutes the 3rd time trying to reboot after install. The phone will not turn on, respond, or anything unless I pop the battery out and put it back in. I can get back into Safestrap that way.
I really want to use Hyperdrive, but it just won't reboot for my phone.
I do have the Verizon i545 version, ME7, Safestrap, Rooted, and newest Hyperdrive Rom. Used the Safestrap Kernel, but the phone locks up.
I've tried default settings, different Rom settings, (2gb and 3gb), removing almost everything from install, adding what I want, adding what I like, etc. No combination of settings will let me phone boot into Hyperdrive.
Any thoughts?
Are you completely removing then re-creating the slot when trying all these flashes?
Are you flashing the ME7 kernel module.zip ?
I redo the rom slot each time and act like it's the first time.
And i can't install the module... Tried multiple times but it fails almost instantly through ss.
Sent from my SCH-I545 using xda app-developers app
Excessumcarcer said:
I redo the rom slot each time and act like it's the first time.
And i can't install the module... Tried multiple times but it fails almost instantly through ss.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Have you tried to re-download the module? Preferably on the computer then transfer to your ExtSDCard with the ROM.
So... The one I downloaded to my computer failed, but the one I did with my phone worked.
Still the same issue. Won't boot past the SS message.
Sent from my SCH-I545 using xda app-developers app
Excessumcarcer said:
So... The one I downloaded to my computer failed, but the one I did with my phone worked.
Still the same issue. Won't boot past the SS message.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
While you were trying to install did you notice if zip signature was checked if so uncheck when you install and uncheck when you install module other than that don't know what else to say. When i first started i found that to be my problem.
The zip signatures were not checked. : /
Sent from my SCH-I545 using xda app-developers app
And I've tried the older version Hyperdrive with the new ME7 Modules, still won't work. I can't understand because everything says it was successful and ready to go, but it just doesn't.
Also double checked my i545 version, it is still ME7 and not the new one. The new update is pushy and wants to be installed more aggressively than the ME7 did. Highly annoying...
Excessumcarcer said:
And I've tried the older version Hyperdrive with the new ME7 Modules, still won't work. I can't understand because everything says it was successful and ready to go, but it just doesn't.
Also double checked my i545 version, it is still ME7 and not the new one. The new update is pushy and wants to be installed more aggressively than the ME7 did. Highly annoying...
Click to expand...
Click to collapse
Get off 3.62 and go back to 3.6 if you can. use root uninstaller to get rid of the current SS and shut down normally. ( all in stock rom ) reboot to stock recovery and factory reset. put the 3.0 SS back on and install twrp through that and reboot fully. then you can go into SS and reboot to recovery and you should be good
EDIT: go back to 3.6 SS not 3.0 haha
EDIT 2: always wipe even after you just created the slot and flash the modules with HD10 and advanced wip the dalvik and the cache only. and chill for 10 and boot her up..... and make sure you didnt accdentally get the dreadful OTA!!!
!Led*Eyes! said:
Get off 3.62 and go back to 3.6 if you can. use root uninstaller to get rid of the current SS and shut down normally. ( all in stock rom ) reboot to stock recovery and factory reset. put the 3.0 SS back on and install twrp through that and reboot fully. then you can go into SS and reboot to recovery and you should be good
EDIT: go back to 3.6 SS not 3.0 haha
EDIT 2: always wipe even after you just created the slot and flash the modules with HD10 and advanced wip the dalvik and the cache only. and chill for 10 and boot her up..... and make sure you didnt accdentally get the dreadful OTA!!!
Click to expand...
Click to collapse
FINAL EDIT!!! always pick the safestrap kernel during the Aroma install
If I helped at all, shoot me a Thanks and happy flashing!!
!Led*Eyes! said:
FINAL EDIT!!! always pick the safestrap kernel during the Aroma install
If I helped at all, shoot me a Thanks and happy flashing!!
Click to expand...
Click to collapse
I promise you this makes no sense....and I think there was something wrong with the stock rom...only thing I can conclude. I did a factory reset and bricked my phone. I can't even get into Safestrap now...whatever the issue was with the custom rom is now the issue with the stock rom. So, i'm just going to wipe my phone and start over from scratch as that is the only available step. Ill let you know if it fixed the issue or not.
Excessumcarcer said:
I promise you this makes no sense....and I think there was something wrong with the stock rom...only thing I can conclude. I did a factory reset and bricked my phone. I can't even get into Safestrap now...whatever the issue was with the custom rom is now the issue with the stock rom. So, i'm just going to wipe my phone and start over from scratch as that is the only available step. Ill let you know if it fixed the issue or not.
Click to expand...
Click to collapse
Did you have 3.62? my buddy did and his phone wouldnt let him delete it! crazy. i dont like 3.62 but i was running HDrls10 like a champ. not a single issue. With the me7 base i want to say i didnt even flash the modules over it but i cant remember. but basically ( by what i wrote down) you were going to start from scratch anyway.. there is a better root out now anyway. use the dialer codes and get a REAL factory reset!! There are a lot of people that arent digging the 3.62..... it was causing bootloops for a while but there are def still some lingering issues i think.
!Led*Eyes! said:
Did you have 3.62? my buddy did and his phone wouldnt let him delete it! crazy. i dont like 3.62 but i was running HDrls10 like a champ. not a single issue. With the me7 base i want to say i didnt even flash the modules over it but i cant remember. but basically ( by what i wrote down) you were going to start from scratch anyway.. there is a better root out now anyway. use the dialer codes and get a REAL factory reset!! There are a lot of people that arent digging the 3.62..... it was causing bootloops for a while but there are def still some lingering issues i think.
Click to expand...
Click to collapse
Well...nothing has worked.
Update for everyone, I was using the older SS, 3.60.
I killed everything, put the original Verizon ME7 Rom on the phone, re-rooted, put 3.62 SS on, (Done like it), installed the HDrls10, Installed the module, (both successful), restarted, exact same thing. Right after Safestrap Enabled pops up, the phone goes dark and the battery needs to be removed and put back in for it to turn on again.
So, I tried something crazy and for whatever reason it worked as far as HD is concerned...but...I went outside of the instructions.
I have the HD rls9 Final. I installed it through SS, used the modded Kernel, (non SS), and restarted. It popped right up in about 45 seconds. (Wasnt working before I reset everything and started over)
I tried HD rls10 Final that way, and nothing.
I will be redownloading it tonight to make sure it isn't the download. (I have slow internet, itll take all night likely.) : /
If anyone is looking to actually uninstall SS (which you need to do to roll back a version) you need to use the commands hashcode has provided. Using Terminal Emulator on the stock side will accomplish that. Read up on hashcode's SS OP.
My phone will not accept HDrls 10....no matter what I try. It accepted HDrls9 without issue, minus the hotspot not working. But it will not accept HDrls10...
Im out of ideas...
EDIT: I downloaded the HDrls 10 rom from two locations, tried both, both failed this morning.
Excessumcarcer said:
My phone will not accept HDrls 10....no matter what I try. It accepted HDrls9 without issue, minus the hotspot not working. But it will not accept HDrls10...
Im out of ideas...
EDIT: I downloaded the HDrls 10 rom from two locations, tried both, both failed this morning.
Click to expand...
Click to collapse
All I can think of is somehow you are getting bad downloads. Have you checked the MD5s to match per the download sites listing?
lazer9 said:
All I can think of is somehow you are getting bad downloads. Have you checked the MD5s to match per the download sites listing?
Click to expand...
Click to collapse
I just double checked the MD5. It matches the download. How frustrating. Double checked the build, double checked the MD5, double checked install procedure, etc. It flat doesn't work on my phone, and there is no logical reason to it. I tried from a fresh build twice now, doing the rooting and SS install from stock everything.
It locks up right after SS, still.
Electronics hate me, it has been determined before. This is just further proof.
: /
So, I've done pretty much everything feasible. Guess Ill have to stick with an older HD or different rom. : (
Also, hotspot doesn't work HD 9 for me, (nor Jellybeans). I installed the module when I did the rom, but there is no hotspot for one. And two, when I download and use FoxFi, which I paid for to use on the Stock Rom before SS, it will try to turn it on and then it freezes and crashes.
All I want is a non-Verizon Rom with working Hotspot!!!! AHHHHH!!!! Looks like that aint happening.
Well played Verizon...well played. Perahps I should get an international phone and go to another company. Expensive, but tempting.
So, the final verdict for those following -
Hyperdrive 10 - Does not work on my i545 no matter what I tried.
Hyperdrive 9 - Works but the hotspot is glitched and froze no matter what I tried.
Jellybean - Works the same as HD 9
Synergy - Works. Everything on it works, hotspot, install, etc.
Not sure why the others did not work. But, for whatever reason Synergy works flawlessly for my i545. Installed and downloaded the same ways as the others, yet it worked.
: /
I was planning on trying a few others first, but Synergy claims to block Samsung from logging information from my phone. I realize this doesn't stop every company from doing it, but its the thought that counts. lol. So, Im trying this Rom out now. It's no hyperdrive, but it works.
After a BUNCH of tries I finally got it to work!!
I have a Verizon i545 with ME7. I basically started as if I'd never installed HD 9.1 in the first place.
Here's what I did.
1. Double check that your device is rooted. I used Root Checker Basic. I actually re-rooted my device just to be sure (I venture to guess it might have been unnecessary) and it worked.
2. I used a 4GB SD formatted to ex-fat and put the HD RLS10 AND the ME7 modules .zip file on it (Both on the SD)
3. I then booted into recovery.
4. Make a new ROM slot.
5. Name it whatever you like.
6. When you go to flash HD, hit the add zip button and select the ME7 modules.zip
7. When HD gets done flashing UNCHECK the "Reboot" box up top and then hit the reboot tab at the bottom right.
8. It will automatically flash the ME7 modules next. When it says 'Successful', then reboot.
9. Give it a few seconds and hopefully it will work for you as well. Good luck.
Latest installable version for Me7?
What is the latest installable version of HD for verizon locked Me7 bootloader, i currently have rls10.0 installed and ive tried 10.1, 10.2, and now 12 and none of them boot up.
Hi XDA,
For the past several days I've tried to Safestrap a custom ROM to my phone. I'm running a rooted Samsung Galaxy S4 with ME7 (Verizon), Android 4.2.2. It's worth noting that the phone has not received an official Verizon update since August; I tried using Loki back then before knowing about the locked bootloader, and it has not affected anything except that the phone softbricks into the ODIN screen whenever it tries to install a Verizon update. (I hope this is not the cause of the problem, but let me know if you think it is.) It's also worth noting that I deleted the stock messaging app (SecMMS.apk and SecMMS.odex.) I am using Safestrap 3.65.
So far, I've tried three different ROMs (Hyperdrive RLS10.2, Jelly Beans Build 7, Google Play Edition for 4.2.2.) Each install produced the same results: it installs just fine in the ROM slot (along with the ME7 modules afterwards), but when I reboot the system, it shows the Samsung logo, the Safestrap splash screen, and then the screen goes black indefinitely. A battery removal is required.
I've tried every trick I could find to get the ROMs working. I've done a full factory reset each time (data + both caches), tried downloading each mod several times on both my phone and my computer (verified MD5 each time) and same with the modules, waited at least 20 minutes during each boot attempt, tried installing each ROM with default settings and minimal apps, used Stock kernels each time, made sure the modules are installed before rebooting (I also tried without the modules to make sure they weren't the problem--same result.) Each time I try an install, I delete the ROM slot and format it again (usually a 1GB-2GB-300MB split.) I've searched and searched and can't seem to find anyone with this problem that hasn't solved it through one of the fixes I've unsuccessfully tried.
I'm plum out of ideas now, and am hoping someone may have more wisdom to share. Please help!
had been trying roms for months now, and 2 weeks ago just starting bootlooping. was running carbon rom when the bootloop started. changed to padawan v2, bootloop went away for a few days and then came back. thought it was power button but when im in cwm it doesnt bootloop.
even all my backups they bootloop. today i went back to stock and using odin and reboots after the att logo.
is my phone done for? thanks
Try an emergency recovery with kies.
fixed it!
i would try it but keeps rebooting. would reboot within 1 minute.
so it turns out it was my radio, even the one in the stock rom would be no good.
i had to flash padawan twice so i would reboot much less frequent, i know why but it worked. then i downloaded a different radio version and seems to be working great. no more reboots after a few days, and i still get 4g on simple mobile.
i dont know how the radio was messing with the reboot but good thing it stopped, was about to give up on my phone.
ufuknut said:
i would try it but keeps rebooting. would reboot within 1 minute.
so it turns out it was my radio, even the one in the stock rom would be no good.
i had to flash padawan twice so i would reboot much less frequent, i know why but it worked. then i downloaded a different radio version and seems to be working great. no more reboots after a few days, and i still get 4g on simple mobile.
i dont know how the radio was messing with the reboot but good thing it stopped, was about to give up on my phone.
Click to expand...
Click to collapse
Hi, I wanted to know what radio version you flashed, because I'm getting the exact same error but none of the radios works for me, I'm also using padawan because of what you said.
Here's a Stockish ROM for your N915P. This ROM has Knox, Sprint ItsOn, and secure storage removed. Nothing else was done to this ROM. I'm new to the Note Edge so I may upload patches to remove any other traces of Knox or ItsOn or optimizations I happen to find while making my own ROM.
Prereq: OG1 Baseband. Download it below.
Modified stock kernel (BeastMode Stock): Kernel modified to allow root by disabling "Root Restriction in defconfig"
Download
MD5: 75bd507e3b4296a128f1c0c48fd2359c
Version 1.1: Enabled many TCP Congestion options via defconfig. Added init.d ability via ramdisk.
Odex:
Download
MD5: 59d544ef6a4bc12d969f4efd9577d36d
DeOdex DEBLOATED:
Download
MD5: 00b5246b9c2074e7ff04f6af2bad1ec2
OG1 Baseband:
Download
MD5: 3bc88209d60117fb573e0f5a2e50f4e9
Patches and fixes:
None yet.
[size=+3]DeOdex note:[/size]
The first boot time for this DeOdex ROM is very long. Approximately 5-8 minutes. Your phone will get hot as the splash screen remains on the yellow Sprint boot animation. I recommend keeping your phone in a cool environment while this is happening. The heat, if not properly checked, can make boot times even longer as the system throttles speed in order to deal with the heat. This doesn't happen on the Odex version.
[size=+3]Install instructions:[/size]
-Are you currently on the OC8 bootloader and would like to stay on it?
--Simply flash the baseband with Odin, and the ROM.
-Are you on the update from OTA or flashed the OG1 TAR?
--Flash kernel only.
-Are you one of the unlucky ones to take the OTA and hose your system trying to root and are now on another ROM?
--Flash ROM only.
-Are you on any build after OC8 but not the current OG1?
--Flash the baseband and ROM. Bootloader is optional and not available in this thread as of yet.
Wiping is only necessary if you are coming from a different base, such as AOSP/CM. If you are coming from a touchwiz ROM, wiping isn't needed, but won't hurt.
Changelog:
9/5/15: Initial Release.
Kernel source code: Download
Thanks, will flash tomorrow.
Thank you so much freeza!! Patiently waiting for the deodexed version and for the baseband.
Added modified stock kernel v1.1 and baseband.
Freeza if I'm on 5.0.1 still just flashing the baseband may give me better service ? Technically...
Downloading now still waiting on the deodex will play with the stock to see how it is thanks
Ok, flashed rom, kernel, and modem. Took a while to boot but all is running well at the moment. Thanks for supporting our device!!
DeOdex uploading....
What What!!! By far the best developer on a Samsung!! Thank you so much for your hard work brother!! Real Talk, i still have your rom on my Note 3! It runs flawlessly!! XD
Get your DeOdex on, guys! ;D
Thanks so much for this!!! I love the separate edge screen and have no reason to "upgrade" to the Note 5
Thank you freeza NICE WORK WITH THE KERNEL
When I saw you had been requested to come help this phone achieve root I knew great things were going to come to those who waited. I've had other devices where you were there to help gain root and again you came through. I purposely didn't take the OG1 update because I knew in time this device wasn't going to be ignored. IMO it is the best NOTE device out there and it will be mine until they make a NOTE EDGE 2 (With SD card and removable battery). Thank you for the quick response and the hard work you do to make this happen.
Cant get either one of them to boot. Both the odex and the deodex wont boot, they both flash fine and then after the phone reboots it stays on the yellow sprint screen Maybe for up to a minute then reboots and it cycles that way. Never boots. I've tried not wiping/Factory restarting as well as wiping/Factory resetting. Have also tried formatting through TWRP to no avail. Have also tried flashing the kernel and wiping caches after flashing but Nothing is working. Have also flashed the baseband.
Im currently on OF6 if that should matter.
Edit: md5 Sums have also match up. Have downloaded both from my phone and a pc to no avail.
Edit 2: tried both TWRP 2.8.6.0 and 2.8.7.0. Also tried clockworkmod recovery and that didn't work either.
I had success but it took some time. I downloaded the deodexed debloated rom, the kernel, and the baseband. I had a method to how I wanted to do this and here is how i got there.
I was running OC8 rom rooted.
1. I odened the baseband tar file and rebooted. But unfortunately it bootlooped on the initial splash screen (note edge) so
2. I ran TWRP recovery and installed the kernel file. Rebooted phone and it ran fine. I looked at the settings about phone and saw that the baseband and the rom all said OG1 but i had not installed the rom yet. So i figure it was a trick to get the baseband to install. So
3. I went back into recovery. Wiped dalvik cache and regular cache and installed the new rom. It installed fine and i waited the length of time for the initial boot up. But this time as it was "Android is starting" it rebooted and got stuck on the sprint splash screen and kept randomally vibrating. Having the ability to remove the battery
4. Rebooted back into recovery, wiped everything including internal storage, and reinstalled the deodexed rom. It installed fine and went to the initial startup screen where it tries to initialize and it rebooted one time, back to the initialize screen but continued without a hitch.
I currently am running OG1 5.1.1. With root.
At times during setting up the phone it would randomally vibrate for no reason...short bursts...but it hasn't yet again rebooted, restarted, or crashed. It is faster from what i see. Probably because there are almost no google apps installed. I've had to install chrome, youtube, and maps. But all seems fine. My signal and speeds are the same so the baseband didn't do much to change that. But so far so good.
---------- Post added at 11:30 AM ---------- Previous post was at 11:27 AM ----------
I did try to install over my odexed OC8 with this new rom but because there is so much different about the files that are installed IMO formatting the phone was the only way to get this to work.
---------- Post added at 12:16 PM ---------- Previous post was at 11:30 AM ----------
One final thing just in case it isn't known: when you wipe everything in TWRP, excluding external storage, you have to restart the recovery before trying to install a rom. It will say you have no OS installed, but you are restarting the recovery not booting a rom, so that's fine, but you do lose root status when wiping. So the next screen gives you the ability to gain root again, but you have to restart TWRP to do that. In the past i tried to figure out why installing after wiping didn't work, and 99% of the time it was because of that. I also don't like installing new roms over older roms (even if they are the same base (touchwiz to touchwiz)) because i feel I would spend more time troubleshooting why something isn't working instead of just starting over. I find less hassle doing it this way.
I odin baseband .tar file, than reboot it to recovery, and flash kernal and odex room at the same time, saw some red messages when kernel was flashing, than odex rom was next but it was successful when it was done. (I did not know if kernel falsh ok so i reflash kernel again) reboot to system and after the android system updated all its ok. No problems so far.
Oh and i inclided the supersu at the same time i flash kernel, odex rom and supersu.
1. Odin baseband tar file.
2. Flash kernel, odex rom and supersu.
3. Re-flash kernel.
4. Reboot to system and profit.
(Maybe i did un necessary steps, but its working. )
Was running great but have been experiencing Google account and store issues. Tried odex and deodex versions with similar results. Anyone else having issues?
Johnny Halo III said:
Was running great but have been experiencing Google account and store issues. Tried odex and deodex versions with similar results. Anyone else having issues?
Click to expand...
Click to collapse
Just starting to have random freezing. And not able to select my apps froms the edge screen, i can only scroll through it. Will remove all the app shorcuts and re-add tham again.
**update 1.
I removed all shorcuts from the edge screen and added them back, all work but some i have to select them a few times before they open.
Maybe i have to reflash, reset, clean and wipe.
**update 2.
Clean install of odex rom, and kernal 1.1.
No more lagg but the edge screen does not work properly. Not able to select and open some of the favorite app shorcuts.
**update 3.
Factory reset, cleaned and wype, odin sprint lollipop update (uf something), downloaded OG1 update. Installed all apps from scratch. And the edge screen does not work. I can scroll, side to side, up and down, but when i select an app it does not open it.
** update (last one)
Foud the code to test the phone hardware.
*#0*# on dial screen. Tested all and it came out good. But i notice that some how the edge screen its not as whide as it used to be ( like its more to the right of the phone) so where i use to touch to select an app its now more to the right emd of the edge, thats why i was able to scroll but not select the app.
Its all good now. Now second round of flashing.
Will give it another try at the room.
Thanks Freeza and sorry about the problems i had and hopefully did not cause anyone from not trying this great work pr yours.
I left all the problems i had so tje next person trying this room does not get discureged from trying. But allways fallow direction.
:thumbup:
** last update
After setting and resetting, flashing and un-flashing, rooting and un-rooting. I can finally wrote that all is good. Running latest lollipop 5.1.1 and freeza's new 1.1 kernel, I can reprt that all is smooth as butter.
Thanks for the hard work.
Thank you so much for your hard work Freeza! So glad I'm finally running 5.1.1 on this beast :]
The ROM is working pretty well, but I have noticed that every now and then, the phone will be rather laggy. Turning the screen off and on again seems to fix the issue, making me think that the processor is being throttled while the screen is off (good) but isn't being sped back up when the screen is turned on..sometimes.
It's not a huge deal, but I was wondering if anyone was experiencing the same thing.
No issues here.
Starting on OG1 had to flash bootloader, kernel, deodex rom and supersu to make it stick. Two days now and battery, signal and speed seem improved.
Thanks freeza!