Hi all. I just got a Verizon Htc One M7. I bought it used and it was already updated to 4.4.2 Kit kat and sense 5.5. I am new to rooting and unlocking and I am running into issues I am hoping someone can help me with. I successfully unlocked, rooted, and got S-off. A am trying to get a custom kernel on the phone so I can have tap to wake and swipe to wake. I installed TWRP recovery 2.7.0.0. Everything appears to be working I boot into bootloader mode and it say unlocked and s-off on top of the screen. I started recovery and it appears to be working fine. I created a backup and that works. So I tried 2 different kernels elementalx and elite lunar. Both appear to install fine but when I reboot the phone gets stuck in a boot loop on the HTC screen. I then have to go back into recovery and revert back to my saved backup. The phone will then boot up fine. Not sure if I'm doing something wrong or what. I am running the stock ROM. Any help will be greatly appreciated.
Forgive and help a noop!!!!
No one knows? I also just noticed that on the bootloader screen there is no numbers after OS. Which would appear to mean i have no OS. But the phone boots and operates just fine. Any suggestions? Thinking I should get it back to factory and start over and flash the NuSenseSIX rom. If anyone could please help me out here it would be greatly appreciated!!!! I attached a picture of what my bootloader screen looks like.
Reubster24 said:
No one knows? I also just noticed that on the bootloader screen there is no numbers after OS. Which would appear to mean i have no OS. But the phone boots and operates just fine. Any suggestions? Thinking I should get it back to factory and start over and flash the NuSenseSIX rom. If anyone could please help me out here it would be greatly appreciated!!!! I attached a picture of what my bootloader screen looks like.
Click to expand...
Click to collapse
it's the rom you are on, if you go back to stock build you will see the OS-build number correctly displayed. if you are on a custom rom, and its not built correctly, it will not display properly.
you dont need to worry about it. all the info in hboot is for diagnostic purpose and wont effect you in any way.
synisterwolf said:
it's the rom you are on, if you go back to stock build you will see the OS-build number correctly displayed. if you are on a custom rom, and its not built correctly, it will not display properly.
you dont need to worry about it. all the info in hboot is for diagnostic purpose and wont effect you in any way.
Click to expand...
Click to collapse
Ok I appreciate the response. I am still on the stock ROM. Just have it rooted, unlocked and s-off with twrp custom recovery installed. Any ideas as to why I'm not able to get it to boot after installing a custom kernel? Can I just try to flash the NuSenseSIX ROM in the phones current state or should I start over?
Reubster24 said:
Ok I appreciate the response. I am still on the stock ROM. Just have it rooted, unlocked and s-off with twrp custom recovery installed. Any ideas as to why I'm not able to get it to boot after installing a custom kernel? Can I just try to flash the NuSenseSIX ROM in the phones current state or should I start over?
Click to expand...
Click to collapse
if you would like to try NuSense i would make sure you have a good backup or do one before. you'll need to wipe system - data - cache - dalvik in twrp and then install the rom.
---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------
After some discussion with fellow dev's, i think you havent flash the insecure boot.img that allows you to write to /system. this should stop the kernel bootlooping you.
ok, here we go.
Flash the attached zip in recovery.
wipe dalvik and cache (2x for good measure)
reboot the phone.
then try to flash a custom kernel and see if you boot loop. Let me know what happens. please have a working backup before trying any of this.
(credit to @buckmarble and @brymaster5000)
kernel source
synisterwolf said:
if you would like to try NuSense i would make sure you have a good backup or do one before. you'll need to wipe system - data - cache - dalvik in twrp and then install the rom.
---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------
After some discussion with fellow dev's, i think you havent flash the insecure boot.img that allows you to write to /system. this should stop the kernel bootlooping you.
Click to expand...
Click to collapse
I have everything backed up google drive with titanium backup as well as backed up in TWRP. When I wipe it doesn't remove the TWRP backup right? I have not flashed any boot.img. I am new to this and don't really know what that is. How would I find the boot.img I need. I think I'll just move forward with the NuSense Rom. Can I just download the zip for the NuSense ROM then wipe and flash it using TWRP and I'm good to go or is there other stuff I need to do?
Reubster24 said:
I have everything backed up google drive with titanium backup as well as backed up in TWRP. When I wipe it doesn't remove the TWRP backup right? I have not flashed any boot.img. I am new to this and don't really know what that is. How would I find the boot.img I need. I think I'll just move forward with the NuSense Rom. Can I just download the zip for the NuSense ROM then wipe and flash it using TWRP and I'm good to go or is there other stuff I need to do?
Click to expand...
Click to collapse
the boot.img zip above will allow you to write to the /system part of the phone.
TWRP will not wipe your backup. that is stored in a location its not allowed to wipe unless you do a "factory reset"
flash the zip above first. let it boot then flash NuSense. I'm not to familiar with that rom so i cant for sure say it will have said insecure boot.img.
Ok I flashed that file and the phone boots up fine. But it has a weird N flashing at the top of the screen now. I'll try a kernel this evening and see what happens. Any idea what the N is? Attached a zipped video of what its doing.
Reubster24 said:
Ok I flashed that file and the phone boots up fine. But it has a weird N flashing at the top of the screen now. I'll try a kernel this evening and see what happens. Any idea what the N is? Attached a zipped video of what its doing.
Click to expand...
Click to collapse
That icon is for NFC. idk why its flashing but make sure its off if you dont use it.
its under settings.
synisterwolf said:
That icon is for NFC. idk why its flashing but make sure its off if you dont use it.
its under settings.
Click to expand...
Click to collapse
Ok. It is off in settings. Tried to turn it on and it won't let me. I'll flash a kernel later and see what happens and if it stops doing it. Is there another insecure boot.img I can try?
Reubster24 said:
Ok. It is off in settings. Tried to turn it on and it won't let me. I'll flash a kernel later and see what happens and if it stops doing it. Is there another insecure boot.img I can try?
Click to expand...
Click to collapse
only need to do it once. flash any kernel that is meant for your rom or switch roms. you should be good to go.
synisterwolf said:
only need to do it once. flash any kernel that is meant for your rom or switch roms. you should be good to go.
Click to expand...
Click to collapse
Awesome thanks for all your help. I think I'm gonna flash a Rom. Any suggestions? I would like something close to the stock Rom.
Thank you for all your help!! I successfully installed the NuSense Rom.
Reubster24 said:
Thank you for all your help!! I successfully installed the NuSense Rom.
Click to expand...
Click to collapse
congrats man, you can PM me if you have anymore questions or post in the Q/A thread and i will try to help
:highfive:
Related
First day I got the phone I rooted and installed clockwork mod. I downloaded and installed cm9 but now I can't flash any other roms. Every time I try and flash a new one it boots to log screen then stays on a blank black screen. Any help would be appreciated as i would like to try something else out. Also I followed the flashing instructions of each rom and even tried formatting system with no luck.
just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.
scott0 said:
just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.
Click to expand...
Click to collapse
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.
lendmeyoureers said:
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.
Click to expand...
Click to collapse
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?
drumist said:
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?
Click to expand...
Click to collapse
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.
scott0 said:
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.
Click to expand...
Click to collapse
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download
lendmeyoureers said:
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download
Click to expand...
Click to collapse
i didn't say your's was bricked, i said i bricked mine doing what you did.
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
i'm not sure what post 29 is, but i've done machz's unbricking 2x succesfully, it's the 1st post in his thread.
either way, i know how frustrating it can be, i hope you get it all sorted out.
lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
scott0 said:
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
Click to expand...
Click to collapse
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
this is good advices. but i never was able to sort out how to use terminal emulator, ugh. i kept trying to run commands from within the phone that were ....hekk can't recall exactly. it was frustrating.
but the best advice i think is the nandroid b/u of the original ROM. although nothing necc. wrong with doing a debrick, only takes <30 minutes, as long as the debricking Gods are all in a good mood at that particular moment.
If you get hono's GB rom, then flash HONO's GB kernel, you should be able to boot into GB no problem
drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.
lendmeyoureers said:
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.
Click to expand...
Click to collapse
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)
drumist said:
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)
Click to expand...
Click to collapse
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...
hah, yeah, that command reminded me of what i was doing wrong, i was mistakenly trying to run shell commands from the emulator.
lendmeyoureers said:
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...
Click to expand...
Click to collapse
Awesome. Now make a Nandroid backup BEFORE you install another ROM, so you have an easier way to revert to your current boot image. That way you can install CM9 again later if you want without worrying about going through this again if you want to install something else.
Ok, so basically i have just gone ahead and followed these steps for flashing cyanogenmod:
wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Arc:_Full_Update_Guide
When i got up to step 7, i wasn't able to load clockwork mod, and because i am a noob and new to this, i actually didn't know that i had to install it beforehand. So now, i've got a phone which wont turn on properly (stuck with a lit up black screen) and will only connect into fastboot
Please, somebody help me!!!! I am really scared that i may have bricked my phone, if i can do anything to get it running again, i would be so happy. Please help
did you flash the CM kernel? and CM recovery comes with the kernel..you dont need to install it separately..
xperiaarcsnoob said:
Ok, so basically i have just gone ahead and followed these steps for flashing cyanogenmod:
wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Arc:_Full_Update_Guide
When i got up to step 7, i wasn't able to load clockwork mod, and because i am a noob and new to this, i actually didn't know that i had to install it beforehand. So now, i've got a phone which wont turn on properly (stuck with a lit up black screen) and will only connect into fastboot
Please, somebody help me!!!! I am really scared that i may have bricked my phone, if i can do anything to get it running again, i would be so happy. Please help
Click to expand...
Click to collapse
Alright first thing first. Which version of CM are you trying to flash? And where you downloaded it from?
---------- Post added at 04:15 AM ---------- Previous post was at 04:06 AM ----------
Ok we will come to flashing ROMs later lets first get you to boot your phone so that you can use it and not be scared. Whatever you have messed up, flashing the phone with flashtool and official FTF would make it normal. I hope you know how to do it. Google around and you can find flashtool. Get it installed to you PC then go here http://forum.xda-developers.com/showthread.php?t=1330314 and download the ftf file and flash it using flashtool. Then your phone will be back up and running. Once its done. Come back here and tell me. Ill help you with flashing ROMs.
@ arpith.fbi
Yes i flashed a boot.img that came with the CM9 zip file, but that is all.
@ gnirujan
I am flashing CM9, and i got it from the downlaods section of the CM website.
I have also downlaoded flashtool but im not sure how to flash the FTF file. By the way, that file is for LT18i, and i have a LT18a. Would it matter?
Thanks for the replies
also gnirujan,
I checked that FTF file, and its 370mb. Is it the full firmware? If it is, i will flash it but if there is a way to continue with the cyanogen flashing, i would love to avoid downloading that ftf.
P.S. LANKAN PRIDEEE!!!!
ok first tell me during startup do u see boot logo? or any logo?
When i boot up, all i see is a lit up black screen with nothing on it
Flash the attached boot.img which is the FXP CM9 kernel from this site, then install the zip.
Ok, thanks, i will try it.
That didn't work either , did the same thing as the other.
I have managed to flash a stock ics ftf file, and i have finally rooted my phone. Now i want to try Rom manager instead to install, but when i go to install Clockwork mod recovery, it says stuff about my phone not currently being officially supported.
Any ideas?
xperiaarcsnoob said:
I have managed to flash a stock ics ftf file, and i have finally rooted my phone. Now i want to try Rom manager instead to install, but when i go to install Clockwork mod recovery, it says stuff about my phone not currently being officially supported.
Any ideas?
Click to expand...
Click to collapse
Look in dev section for arc and look for post by pvyparts, his thread is all about cwm recovery check to see if your phone Is listed if not ask there.
Sent from my LT15i using xda premium
xperiaarcsnoob said:
That didn't work either , did the same thing as the other.
Click to expand...
Click to collapse
Your boot loader is unlocked right? You wanna install Cynogenmod 9 right? You dont install the one from cyanogenmod site. It has a non working kernel. In XDA there are these guys called FXP (Free Xperia Project) they are the ones responsible for CM for all Xperia devices. So do this. Go tho this thread http://forum.xda-developers.com/showthread.php?t=1356685 download the CM9 RC 1 FXP 128. Its a 130MB file. Download it and now extract it and flash that boot.img to your Arc S using fastboot. Now start your phone and you should see FXP boot screen then from there go to recovery and try flashing the CM9 RC 1 you have. That should work. I suggest if you can replace the CM9 you have in your memory cad with the FXP128 zip its better so that you can flash the latest FXP128 CM 9, which has lots of improvements.
Edit: Arc S and Arc same ZIP its called anzu
---------- Post added at 06:11 AM ---------- Previous post was at 05:53 AM ----------
xperiaarcsnoob said:
I have managed to flash a stock ics ftf file, and i have finally rooted my phone. Now i want to try Rom manager instead to install, but when i go to install Clockwork mod recovery, it says stuff about my phone not currently being officially supported.
Any ideas?
Click to expand...
Click to collapse
Allright as far as i know there are two ways you can get CMW installed on your phone. 1. Download CWM auto installer from play store and install CMW through that. 2. Flash a kernel which has CWM pre installed.
In this link http://forum.xda-developers.com/showthread.php?t=1680793 you can find stock sony kernel with CWM. You download it and flash it using fastboot. That will get you CWM. hope i helped you.
Thanks gnirujan,
I managed to find a FXP127 kernel yesterday and it worked. But this would be even better. I heard that FXP128 is much faster as well, but I've already set up my whole system and dont want to reset it now . Any way of updating it without wiping?
Thanks again !!!
xperiaarcsnoob said:
Thanks gnirujan,
I managed to find a FXP127 kernel yesterday and it worked. But this would be even better. I heard that FXP128 is much faster as well, but I've already set up my whole system and dont want to reset it now . Any way of updating it without wiping?
Thanks again !!!
Click to expand...
Click to collapse
I believe you can try flashing on top of your existing system. I personally have never tried it. But i think it is possible. I would recommend you to flash FXP 128. The improvements are very very visible. More fast and smooth.
gnirujan said:
I believe you can try flashing on top of your existing system. I personally have never tried it. But i think it is possible. I would recommend you to flash FXP 128. The improvements are very very visible. More fast and smooth.
Click to expand...
Click to collapse
Could anyone check to see if this is true
yes you can update it without wiping anything..but i recommend atleast wiping cache
arpith.fbi said:
yes you can update it without wiping anything..but i recommend atleast wiping cache
Click to expand...
Click to collapse
Will wiping cache delete any system settings or things like homescreen setup?
xperiaarcsnoob said:
Will wiping cache delete any system settings or things like homescreen setup?
Click to expand...
Click to collapse
nope...everything will be the way they were..nothing will change
Thank you very much arpith
:highfive:Just saw this over on androidpolice, wanted.to give everyone a heads up.
http://www.androidpolice.com/2012/0...s-for-the-sony-xperia-ion-now-live-at-get-cm/
This needs an unlocked bootloader? Or would it be possible use this with the stock kernel?
424aca said:
i messaged them about it...waiting for reply
---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------
question: if you do need an unlocked bootloader( i dont) and i flash...what is the worst that can happen?
Click to expand...
Click to collapse
Don't really know but I'd guess a brick. Probably have to go through the whole power drain flashmode process.
I was under the impression we could have roms, but with a locked bootloader we'd have to use the stock kernel. Now I don't know if a Rom has to be cooked in a way to allow for this and/or if the cm9 nightly will be packaged without a kernel. I'm thinking if the answers are "no" and "yes" we may have a shot.
424aca said:
i messaged them about it...waiting for reply
---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------
question: if you do need an unlocked bootloader( i dont) and i flash...what is the worst that can happen?
Click to expand...
Click to collapse
Pretty sure it just won't flash. Just like if you tried to flash the lleaked ICS in the first couple pages of the stock firmware thread (not in the first post) with a locked bootloader. Just errored during flashing and nothing happened.
Sent from my Sony Xperia S
Spectre51 said:
Pretty sure it just won't flash. Just like if you tried to flash the lleaked ICS in the first couple pages of the stock firmware thread (not in the first post) with a locked bootloader. Just errored during flashing and nothing happened.
Sent from my Sony Xperia S
Click to expand...
Click to collapse
I have try this ROM...but when flashing it says Error Status 7
If I were you, I would not flash it cause it needs format system, but the current cwm is not able to format system. If you still try it, you may brick you phone.
siuming720 said:
If I were you, I would not flash it cause it needs format system, but the current cwm is not able to format system. If you still try it, you may brick you phone.
Click to expand...
Click to collapse
Lol it will not bricked ur phone......because only system will be format....if we change kernel sometimes will brick it....but for rom it will not...u still can use seus,flashtool or pcc to restore back
did anyone test this rom? Dose it work ?
faiisfaizal said:
Lol it will not bricked ur phone......because only system will be format....if we change kernel sometimes will brick it....but for rom it will not...u still can use seus,flashtool or pcc to restore back
Click to expand...
Click to collapse
Right, so a soft brick requiring a battery drain to shut off, then recharge to get into flasmode for restoring...a 24-36 hour process. Done it once before, would rather not do it again.
I think we need to figure out the system format issue and if we can flash this Rom on our stock kernel.
Raxtinhax said:
did anyone test this rom? Dose it work ?
Click to expand...
Click to collapse
I test it already with LT28h unlock bootloader..... but something went wrong when start to flash with CWM recovery,,with error status 7
jeriku said:
Right, so a soft brick requiring a battery drain to shut off, then recharge to get into flasmode for restoring...a 24-36 hour process. Done it once before, would rather not do it again.
I think we need to figure out the system format issue and if we can flash this Rom on our stock kernel.
Click to expand...
Click to collapse
Nah....u should not wait your battery drain just do nandroid backup using CWM recovery... if you got problem when flashing it just restore the backup back...
Great news. I'll be waiting for a more stable release. :good:
jeriku said:
Right, so a soft brick requiring a battery drain to shut off, then recharge to get into flasmode for restoring...a 24-36 hour process. Done it once before, would rather not do it again.
I think we need to figure out the system format issue and if we can flash this Rom on our stock kernel.
Click to expand...
Click to collapse
Tried already, without success.
On the xperia S forum, I found how to flash it.
1. Flash the Cm9 zip
2. Flash Gapps zip.
3. Clear cache & Dalvik Cache.
4. Flash the boot.img from the Cm9 zip using fastboot
fastboot flash boot boot.img.
I could do the first three steps, but could not complete the 4th step.
But phone does not go into Soft Brick. Just Go to flash mode and flash the firmware again and restore backup.
ganeshbiyer said:
Tried already, without success.
On the xperia S forum, I found how to flash it.
1. Flash the Cm9 zip
2. Flash Gapps zip.
3. Clear cache & Dalvik Cache.
4. Flash the boot.img from the Cm9 zip using fastboot
fastboot flash boot boot.img.
I could do the first three steps, but could not complete the 4th step.
But phone does not go into Soft Brick. Just Go to flash mode and flash the firmware again and restore backup.
Click to expand...
Click to collapse
As what i experience...i just flash thet zip through CWM recovery and it should done....but is say build.prop error...they need to modified it back.....but that build.prop match mine.... i dont know why it failed to flash
faiisfaizal said:
As what i experience...i just flash thet zip through CWM recovery and it should done....but is say build.prop error...they need to modified it back.....but that build.prop match mine.... i dont know why it failed to flash
Click to expand...
Click to collapse
I removed the assert line from the updater script and was able to flash it.
But never went beyond Cyanogen mod logo.
ganeshbiyer said:
I removed the assert line from the updater script and was able to flash it.
But never went beyond Cyanogen mod logo.
Click to expand...
Click to collapse
No wonder lol...hahah but u didnt pass to bootanimation right?
Yes ... No Luck ....
Try to follow this thread.
http://forum.xda-developers.com/showthread.php?t=1782771
ganeshbiyer said:
Yes ... No Luck ....
Try to follow this thread.
http://forum.xda-developers.com/showthread.php?t=1782771
Click to expand...
Click to collapse
I followed those thread just now....but i got bootloop....damn i guess they need to rebuild this rom properly....
ganeshbiyer said:
I removed the assert line from the updater script and was able to flash it.
But never went beyond Cyanogen mod logo.
Click to expand...
Click to collapse
have you tried to go on CWM recovery flash the zip file, fix permissions?
yesterday I was having some hard time with flashing a CM10 on a SG2 and the only solution to have it without any problem was to fix permissions after flashing the ROM.
From my understanding, with my experiences with my old x10, you need the ability to flash the fxp kernel. Since we don't have a way to bypass the stock kernel yet, we probably can't use this on a locked bl.
Sent from my LT28at using xda premium
dizarmstrong said:
From my understanding, with my experiences with my old x10, you need the ability to flash the fxp kernel. Since we don't have a way to bypass the stock kernel yet, we probably can't use this on a locked bl.
Sent from my LT28at using xda premium
Click to expand...
Click to collapse
That what im thinking when this rom is not working.....i think its really need custom kernel.....i unlock my bootloader but no custom kernel to be flash
hy everybody , i have been trying to install hyperdrive rom rl10 on mt at&t galaxy s3 i have follow every step ,fix, i even flash kt747 kernel and nothing i'm still stuck on boot it won't pass the first boot animation , i also flash xone kernel and still the same it will get stuck on first animation boot even after 7 minutes it wont do anything.:crying:
angeltouch 4g said:
hy everybody , i have been trying to install hyperdrive rom rl10 on mt at&t galaxy s3 i have follow every step ,fix, i even flash kt747 kernel and nothing i'm still stuck on boot it won't pass the first boot animation , i also flash xone kernel and still the same it will get stuck on first animation boot even after 7 minutes it wont do anything.:crying:
Click to expand...
Click to collapse
What model do you have? Carrier? What option did you first choose for a kernel?
You're like the 50th user in here this week with this issue on hyperdrive. It would appear the device type in the build.prop is being is being edited and there is a conflict during the boot process causing this soft brick. Anyone with more knowledge than this please chime in.
If you can still get back into recovery, your options are probably to restore a backup or flash another rom. In download mode you could flash stock stock rooted via odin. If your s3 is not recognized on your pc, there is a flashable stock firmware zip in the link in my signature. In post #2 at the bottom
xBeerdroiDx said:
What model do you have? Carrier? What option did you first choose for a kernel?
You're like the 50th user in here this week with this issue on hyperdrive. It would appear the device type in the build.prop is being is being edited and there is a conflict during the boot process causing this soft brick. Anyone with more knowledge than this please chime in.
If you can still get back into recovery, your options are probably to restore a backup or flash another rom. In download mode you could flash stock stock rooted via odin. If your s3 is not recognized on your pc, there is a flashable stock firmware zip in the link in my signature. In post #2 at the bottom
Click to expand...
Click to collapse
hi beerdroid i have at&t sgh-i747
i choose the ziggy kernel in aroma thats the only option for at&t , i did try with the verizon with the zeus kernel,deviant kernel, and stock kernel all with no luck , yea i seen a lots of users with the same problem , yes i can still pull out the battery and do the process again with a different kernel , i have try kt747 kernel ,xone kernel and devil's reject kernel all with no luck , phone will boot but it will get stock on first animation boot , and i have no clue when you say build.prop
angeltouch 4g said:
hi beerdroid i have at&t sgh-i747
i choose the ziggy kernel in aroma thats the only option for at&t , i did try with the verizon with the zeus kernel,deviant kernel, and stock kernel all with no luck , yea i seen a lots of users with the same problem , yes i can still pull out the battery and do the process again with a different kernel , i have try kt747 kernel ,xone kernel and devil's reject kernel all with no luck , phone will boot but it will get stock on first animation boot , and i have no clue when you say build.prop
Click to expand...
Click to collapse
i'm trying to do is installing the rls 9 and then update see if this help
So the very first time you flashed hyperdrive, you selected at&t and the ziggy kernel and it didn't work? I'm assuming you gave it plenty of time on the first boot up. Someone correct me if I'm wrong but hyperdrive is a verizon base, yes? If so, this might be the source of your problem, even though it is a "multi-carrier" rom. You can try wiping data, cache and dalvik in recovery then rebooting. Like i said, though, you will probably have to another route (restore backup or flash new rom). When you successfully boot up next, I would imagine your model is different in about phone
xBeerdroiDx said:
So the very first time you flashed hyperdrive, you selected at&t and the ziggy kernel and it didn't work? I'm assuming you gave it plenty of time on the first boot up. Someone correct me if I'm wrong but hyperdrive is a verizon base, yes? If so, this might be the source of your problem, even though it is a "multi-carrier" rom. You can try wiping data, cache and dalvik in recovery then rebooting. Like i said, though, you will probably have to another route (restore backup or flash new rom). When you successfully boot up next, I would imagine your model is different in about phone
Click to expand...
Click to collapse
i'm trying to do whay tou are saying but this aroma installer keeps freezing is driving me nuts
angeltouch 4g said:
i'm trying to do whay tou are saying but this aroma installer keeps freezing is driving me nuts
Click to expand...
Click to collapse
Are you using twrp or cwm for recovery? Twrp is recommended for aroma
xBeerdroiDx said:
Are you using twrp or cwm for recovery? Twrp is recommended for aroma
Click to expand...
Click to collapse
cwm
angeltouch 4g said:
cwm
Click to expand...
Click to collapse
If you're really wanting to get this particular rom going, changing to twrp might help. In my signature there is a link. Near the bottom of post #2 flashable recovery zips are mentioned. Download the twrp one and throw it on your phone. Boot into recovery and flash it. Reboot recovery. Wipe data, cache and try flashing the rom again.
xBeerdroiDx said:
If you're really wanting to get this particular rom going, changing to twrp might help. In my signature there is a link. Near the bottom of post #2 flashable recovery zips are mentioned. Download the twrp one and throw it on your phone. Boot into recovery and flash it. Reboot recovery. Wipe data, cache and try flashing the rom again.
Click to expand...
Click to collapse
ok i'll do that to see if helps thanks
hrsema and
angeltouch 4g said:
ok i'll do that to see if helps thanks
Click to expand...
Click to collapse
now i got the boot animation hyperdrive sbreen94 how much you think i have to wait it looks like is stock?
angeltouch 4g said:
now i got the boot animation hyperdrive sbreen94 how much you think i have to wait it looks like is stock?
Click to expand...
Click to collapse
It could take 10 or so minutes for the initial boot. If it takes a lot longer, you can try booting back onto recovery to wipe data and cache again. If this does not work, I would go another route
xBeerdroiDx said:
It could take 10 or so minutes for the initial boot. If it takes a lot longer, you can try booting back onto recovery to wipe data and cache again. If this does not work, I would go another route
Click to expand...
Click to collapse
ok , if not i'll try to flash some other kernels to see if it boots up , i f not i'll just give up on this rom and go back to synergy
When you're back up and running on a rom, go into settings > about phone and tell me what your device is listed as. You may have small issues down the road if your phone has been designated as an SCH-I535 or anything other than SGH-I747. That's an easy build.prop fix, though. Good luck
xBeerdroiDx said:
When you're back up and running on a rom, go into settings > about phone and tell me what your device is listed as. You may have small issues down the road if your phone has been designated as an SCH-I535 or anything other than SGH-I747. That's an easy build.prop fix, though. Good luck
Click to expand...
Click to collapse
ok i'll do that and let you know
model number samsung-sgh-i747
baseband number i747ucdlk3
angeltouch 4g said:
model number samsung-sgh-i747
baseband number i747ucdlk3
Click to expand...
Click to collapse
Good. Congrats. What rom did you end up on?
synergy thats were i was before trying to flash hyperdrive
The upside: now you can post in development threads
ok
For some time, I have one problem which I can't fix. I mean, maybe I can, but don't know how. Since my OP3 arrive to me, I'm playing with ROMs and I tryed almost everyone for this phone. I think that when I once installed FreedomOS, I by accident selected in Aroma "swipe bottom left to lock screen". But that "feature" still persist in my phone despite of wiping system and changes ROMs. Every custom ROM that i tried have this issue except these which are stock based. Can anyone help me?
What kernel do you have? ElementalX and some others have that feature as well
That's the main problem buddy, I am not using any of custom kernels @KeelinTy
Hmm. When you installed new operating systems, do you dirty flash or wipe the entire phone and then flash?
KeelinTy said:
Hmm. When you installed new operating systems, do you dirty flash or wipe the entire phone and then flash?
Click to expand...
Click to collapse
Yes, everytime I'm doing clean flash
Could possibly be something going left over in the partitions after flashing a new image. If you really want it gone you can wipe all of the partitions from Fastboot. My freedomos boot logo would stick around until I did that
KeelinTy said:
Could possibly be something going left over in the partitions after flashing a new image. If you really want it gone you can wipe all of the partitions from Fastboot. My freedomos boot logo would stick around until I did that
Click to expand...
Click to collapse
Okay then, how command I should write to do this?
Fastboot erase system
Fastboot erase boot
If those don't work try replacing erase with format. I can't remember which works with which partition since I haven't done it in a while.
I'd suggest only doing this when youre ready for a clean install of the OS since you'll have to replace all of your data as well
KeelinTy said:
Fastboot erase system
Fastboot erase boot
If those don't work try replacing erase with format. I can't remember which works with which partition since I haven't done it in a while.
I'd suggest only doing this when youre ready for a clean install of the OS since you'll have to replace all of your data as well
Click to expand...
Click to collapse
Thanks a lot mate of course, I reckon with that and I will try this tomorrow.
No problem. If it ends up not working just let me know and I'll try to help put more
KeelinTy said:
No problem. If it ends up not working just let me know and I'll try to help put more
Click to expand...
Click to collapse
Suprisingly that doesn't work I also tryed flash again complete stock ROM with unbrick tool, but after install custom ROM, slide bottom feature still persist
Flash the compatible Ex Kernel and un-check that option. it will fix the prob
---------- Post added at 11:27 AM ---------- Previous post was at 11:25 AM ----------
inOvator71 said:
For some time, I have one problem which I can't fix. I mean, maybe I can, but don't know how. Since my OP3 arrive to me, I'm playing with ROMs and I tryed almost everyone for this phone. I think that when I once installed FreedomOS, I by accident selected in Aroma "swipe bottom left to lock screen". But that "feature" still persist in my phone despite of wiping system and changes ROMs. Every custom ROM that i tried have this issue except these which are stock based. Can anyone help me?
Click to expand...
Click to collapse
Flash a compatible Ex Kernel on top and make sure to uncheck the Swipe to lock option. I had made the same error a while back. This fixes it
ihuman007 said:
Flash the compatible Ex Kernel and un-check that option. it will fix the prob
---------- Post added at 11:27 AM ---------- Previous post was at 11:25 AM ----------
Flash a compatible Ex Kernel on top and make sure to uncheck the Swipe to lock option. I had made the same error a while back. This fixes it
Click to expand...
Click to collapse
I already tried this mate, but that also doesn't work. Do you think that I should try this again? You did this with OOS version or lineage?