Related
[solved] (forgot to flash new kernel)
after working 6 straight hours on my girlfriends captivate trying to un brick it (succeed) i think its time for me to figure out whats up with my incredible
i have flashed redemptive rom on my phone, and i tried to flash many other roms over it a day after and they keep going into boot loop (i think because it just stays at the "htc incredible" screen). is their some trick to getting a new rom flashed over the stock rom? did i miss something on all the tutorials and XDA wikis? im stumped! any advice?
i have searched for the past day for the answer (kinda why i almost bricked my girlfriends captivate because it was doing the exact same thing) thats why i came here. this is my last resort
Did you do a full wipe between flashes? You really shouldn't have to do anything special. Ill help you get through it. Oh is your inc an amoled or slcd screen. If its slcd you need an slcd enabled kernel. Do you have adb installed? If so are thaere any errors.
It can take up to 15min for a first boot. Adb will show you if every thng is going smoothly
If it doesn't boot after flashing a rom through recovery it is most likely the rom not flashing right for some reason, most likely an improperly finished download. Try downloading it again. Happened to me before on ruby rom.
Sent from Conical. 07
linuxmotion said:
Did you do a full wipe between flashes? You really shouldn't have to do anything special. Ill help you get through it. Oh is your inc an amoled or slcd screen. If its slcd you need an slcd enabled kernel. Do you have adb installed? If so are thaere any errors.
It can take up to 15min for a first boot. Adb will show you if every thng is going smoothly
If it doesn't boot after flashing a rom through recovery it is most likely the rom not flashing right for some reason, most likely an improperly finished download. Try downloading it again. Happened to me before on ruby rom.
Sent from Conical. 07
Click to expand...
Click to collapse
i have an slcd screen and im running kings kernel #5 on my stock install. maby i need to flash the kernel again before first boot just in case the new rom changes the kernel
i have adb on my computer but i dont know how to do anything but the classic "adb shell" to remove bloat-ware and "adb Push" from working on my girls captivate
whats weird is it has done it on both my incredible and her captivate, but then again, ive done the flashing on both.
do i need to restore to stock before i install another after market rom?
You most definatly will need to flash the kernel again. Every full rom flash will flash the kernel that comes with the rom.
No you will not need to return to stock. Just flash away just remember your kernel. Most roms for the inc have amoled as the default screen type in the rom kernel.
Sent from Conical. 07
linuxmotion said:
You most definatly will need to flash the kernel again. Every full rom flash will flash the kernel that comes with the rom.
No you will not need to return to stock. Just flash away just remember your kernel. Most roms for the inc have amoled as the default screen type in the rom kernel.
Sent from Conical. 07
Click to expand...
Click to collapse
im trying it now. Fingers crossed
It Worked!!!!!!!!!! You made my day!! i missed something that simple!! unfortunately it is boot looping but i think its probably the rom ha, but it made it far as i need to use other roms, thank you!
Well glad to help. Which rom is it.
For a sense rom i personally like virtous. Very smooth. Close to stock. Has great mods.
Sent from Conical. 07
it was Cyanogen but I'm going to give that one a try now that u mention it. And now that I understand this a little better
I'm going to try to keep this description as brief as possible while still including enough detail to properly ask for help... I have been searching for a resolution for a couple hours now and am confident that my issue has not been covered before, but if I'm wrong I'm happy to be shown the light. I cannot post this in the kernel thread as it's in a development forum and I don't have enough posts to post there.
I've installed the Stock+ v3.0 ROM today after release, per his instructions on a clean wipe. Rom install worked fine with the black dialer and restore rotate mods listed in the Stock+ ROM thread. I decided I wanted to install the EXT4 mod so I followed these instructions exactly using Convert2Ext4_no_data_limit_normal_dalvik EXT4 mod and 2.6.35.jermaine151_stock_ext4 Stock+ kernel. As soon as I reboot after installing the kernel I get stuck at a cycling of the boot animation. This is my second time through the rom install, which works, and then the mod/kernel install, which borks. Results were exactly the same both times.
I appreciate any help I can get. TIA for your time.
EDIT1: I didn't expect it to work, but i reinstalled the rom without wiping, and the results were as I expected. Now it sticks at the boot splash instead of the boot animation.
lackskill said:
I'm going to try to keep this description as brief as possible while still including enough detail to properly ask for help... I have been searching for a resolution for a couple hours now and am confident that my issue has not been covered before, but if I'm wrong I'm happy to be shown the light. I cannot post this in the kernel thread as it's in a development forum and I don't have enough posts to post there.
I've installed the Stock+ v3.0 ROM today after release, per his instructions on a clean wipe. Rom install worked fine with the black dialer and restore rotate mods listed in the Stock+ ROM thread. I decided I wanted to install the EXT4 mod so I followed these instructions exactly using Convert2Ext4_no_data_limit_normal_dalvik EXT4 mod and 2.6.35.jermaine151_stock_ext4 Stock+ kernel. As soon as I reboot after installing the kernel I get stuck at a cycling of the boot animation. This is my second time through the rom install, which works, and then the mod/kernel install, which borks. Results were exactly the same both times.
I appreciate any help I can get. TIA for your time.
Click to expand...
Click to collapse
with the ext4 mod i think you need the kernel installed and booted once before flashing the ext4 mod. please try this and report back.
synisterwolf said:
with the ext4 mod i think you need the kernel installed and booted once before flashing the ext4 mod. please try this and report back.
Click to expand...
Click to collapse
Thank you for the reply. I was in the process of editing the OP when you posted this. I'll work back to the place I was originally and report back ASAP.
lackskill said:
Thank you for the reply. I was in the process of editing the OP when you posted this. I'll work back to the place I was originally and report back ASAP.
Click to expand...
Click to collapse
yeah just let me know. im leaving work now but i can check on my phone. i hope it works. with installing the kernel after it formats partitions and that might be causing the problem. this is all guessing. but im thinking that the kernel is breaking the link so the phone cant boot.
synisterwolf said:
yeah just let me know. im leaving work now but i can check on my phone. i hope it works. with installing the kernel after it formats partitions and that might be causing the problem. this is all guessing. but im thinking that the kernel is breaking the link so the phone cant boot.
Click to expand...
Click to collapse
I wanted to add. Can you link the rom you are using so I can check it out.
Sent from my sexy assistant. (AMOLED HTC Incredible)
synisterwolf said:
with the ext4 mod i think you need the kernel installed and booted once before flashing the ext4 mod. please try this and report back.
Click to expand...
Click to collapse
I have:
* Wiped
* Installed v3.0 of the rom
* Rebooted and completed initial setup stuff
* Flashed Stock+ Kernel
* Rebooted - still booting fine at this point
* Installed EXT4 mod
It's still booting fine at this point, but Stock+ kernel is replaced by gingertiny kernel. I'm going to try reinstalling the Stock+ kernel, just because. If that doesn't work I'll stick with gingertiny and I'll report back with any more updates.
synisterwolf said:
I wanted to add. Can you link the rom you are using so I can check it out.
Sent from my sexy assistant. (AMOLED HTC Incredible)
Click to expand...
Click to collapse
Stock+ ROM
I like it a lot. It's based on the newest (4.06.605.3) Sense OTA with a couple nice tweaks. With EXT4 mod, black dialer, restore rotate, and 802.11n support it's how this update should have come from HTC, IMO.
lackskill said:
I have:
* Wiped
* Installed v3.0 of the rom
* Rebooted and completed initial setup stuff
* Flashed Stock+ Kernel
* Rebooted - still booting fine at this point
* Installed EXT4 mod
It's still booting fine at this point, but Stock+ kernel is replaced by gingertiny kernel. I'm going to try reinstalling the Stock+ kernel, just because. If that doesn't work I'll stick with gingertiny and I'll report back with any more updates.
Click to expand...
Click to collapse
Stock+ kernel is working. Looks like it was the EXT4 mod/stock+ kernel in the same step that was getting me before.
This question is resolved.
lackskill said:
Stock+ kernel is working. Looks like it was the EXT4 mod/stock+ kernel in the same step that was getting me before.
This question is resolved.
Click to expand...
Click to collapse
Yeah. After formatting to ext4 dalvik needs to be built. Its always good to reboot between system upgrades. Glad it works. Might want to post what you did on his thread so others know.
Sent from my sexy assistant. (AMOLED HTC Incredible)
synisterwolf said:
Yeah. After formatting to ext4 dalvik needs to be built. Its always good to reboot between system upgrades. Glad it works. Might want to post what you did on his thread so others know.
Sent from my sexy assistant. (AMOLED HTC Incredible)
Click to expand...
Click to collapse
Thanks again for the help.
I can't post in that thread yet. I still need a few more posts. Maybe someone can link this thread over there so they're aware this thread is here?
good info. i recently installed ext4 using incredikernel.
now i've found this stock+ rom/kernel and am debating trying it. i like the stock sense rom so i'm looking for something close to stock.
aha!
thank you!
lackskill said:
I have:
* Wiped
* Installed v3.0 of the rom
* Rebooted and completed initial setup stuff
* Flashed Stock+ Kernel
* Rebooted - still booting fine at this point
* Installed EXT4 mod
It's still booting fine at this point, but Stock+ kernel is replaced by gingertiny kernel. I'm going to try reinstalling the Stock+ kernel, just because. If that doesn't work I'll stick with gingertiny and I'll report back with any more updates.
Click to expand...
Click to collapse
stock+ kernel... is this made by the same dev that makes the rom? i've tried searching but can't find this kernel... can anyone help me with a link?
EDIT - found it... http://forum.xda-developers.com/showthread.php?t=1342278
Hey Guys,
sorry for creating a new thread but I am at a loss right now.
I followed the instructions in this post:
http://forum.xda-developers.com/showthread.php?t=1233340
at the point (in step 2)
Once this is done, do NOT reboot. Go to Advanced Again and select Reboot Recovery
Click to expand...
Click to collapse
i got a problem! I started clockworkmod recovery v2.5.0.2 (pretty sure about that)out of rom manager and did all above the mentioned point. step by step. but after flashing the bravo-recovery-v1.5.3-CustomMTD.zip, my display just went black. light on but black. sorry for my bad english - hope u guys know what I mean. ^^ no matter if I pressed the ok button or the P-OFF of my wildfire.
after taking out the battery I only was able to boot in recovery mod version 2.5.0.1
I thought i just go on with the next step -
Once Clockworkmod Recovery Reboots, Restore your previously taken nandroid backup
Click to expand...
Click to collapse
but here i get the error: error while restoring /system/!
what can I do? I think the version of the recovery is the problem!? while making the nandroid backup no errors occurred!
please help me I need this nasty phone
When you are trying to create custom partitions, do not boot into recovery from ROM Manager. (ROM Manager uses Temporary ZIP recoveries which cannot be modded. I should have added this to that guide :/).
Power off your phone, start in HBoot, navigate to RECOVERY, and use this Clockworkmod to create Custom MTD partitions. For now, to get your phone in working order, just flash any ROM temporarily. Then try again. Use the same version of CWM to restore as you did when creating the backup.
Also, are you sure it is 2.5.0.2? AFAIK, there isn't a version like that.
3xeno said:
Also, are you sure it is 2.5.0.2? AFAIK, there isn't a version like that.
Click to expand...
Click to collapse
Lol, maybe he means 5.0.2.0?
To OP, try flashing a PC49IMG.zip of Clockworkmod Recovery 5.0.2.0, and try again.
Sent from my Wildfire using Tapatalk 2 Beta-5
thanks guys got the same idea later on time. long night indeed.
Yes i meant this version sry - as mentioned, laaate night ^^ no power after 3 days of bootloops (because of supercharger script, LOVE IT!! and have to beat the odds)and I dont wonder - same thing today. fresh rom, got the gapps on it, V6_SuperCharger_for_Android-Update9_RC8.1 and then bootloop bootloop.
A few hours earlier, I intuitionally did as you wrote in the post above. BTW when the wildfire has about 300mb internal space - your mtd guide worked ain't it!? ^^
... so i flashed CM update-cm-7.2.0-RC1, via the installed CWM v2.5.0.1
everything fine until now because I do whole thing again. Your custom MTD Partition guide first, then installing update-cm-7.2.0-RC1 (is it possible to update to a stable version, when its finished, out from that?) or better a stable or nightly build? Lastly I try to supercharge my mobile again. The wildfire is definitly in need of this oom fixings. (I think the built-in kernel tweaks make my buzz unhappy...) THIS SCRIPT IS GREAT NEED NEED NEED haha.
\\edit:
Right now I try flashing clockworkmod recovery v5.0.2.0 via the old version. Sometimes when I am in the recovery I get a black screen after selecting a menueitem. Then I press P-OFF and get back to the superior menue - it does not work this way everytime. Every second time I stuck on the black screen. Problems problems everywhere
scarfur said:
thanks guys got the same idea later on time. long night indeed.
Yes i meant this version sry - as mentioned, laaate night ^^ no power after 3 days of bootloops (because of supercharger script, LOVE IT!! and have to beat the odds)and I dont wonder - same thing today. fresh rom, got the gapps on it, V6_SuperCharger_for_Android-Update9_RC8.1 and then bootloop bootloop.
A few hours earlier, I intuitionally did as you wrote in the post above. BTW when the wildfire has about 300mb internal space - your mtd guide worked ain't it!? ^^
... so i flashed CM update-cm-7.2.0-RC1, via the installed CWM v2.5.0.1
everything fine until now because I do whole thing again. Your custom MTD Partition guide first, then installing update-cm-7.2.0-RC1 (is it possible to update to a stable version, when its finished, out from that?) or better a stable or nightly build? Lastly I try to supercharge my mobile again. The wildfire is definitly in need of this oom fixings. (I think the built-in kernel tweaks make my buzz unhappy...) THIS SCRIPT IS GREAT NEED NEED NEED haha.
Click to expand...
Click to collapse
Good to know. Welcome to the Wildfire
Thanks if I helped
\\edit:
Right now I try flashing clockworkmod recovery v5.0.2.0 via the old version. Sometimes when I am in the recovery I get a black screen after selecting a menueitem. Then I press P-OFF and get back to the superior menue - it does not work this way everytime. Every second time I stuck on the black screen. Problems problems everywhere
Click to expand...
Click to collapse
I am S-OFF but didn't wanted to update the recovery right now. getting impatient. So I did exactly the same as the last time (described above. black screens in recovery - or hopping to steps like "apply this zip?" even if i didn't selected one, then I press the P-OFF button and selected the zip.)
Somehow everything works -.-
Now I've my second try in CM 7.2 RC1
I doesn't rly have the heart to try the supercharger script again - want to prevent stucking in bootscreen. What should I do?
Nandroid backup, run the script, if bootloop then restore (flashing the bravo-boot file after restore to get your partitions back as always). Thats what i did last time, and didn't try the script again. Too bored of bootloops.
Sent from my HTC Wildfire using Tapatalk 2 Beta-5
yes, god save the nandroid backup!
Second try - suddenly everything worked fine for me, thanks to everyone
can be closed
greetz
I've been trying to flash CM 7.2.0 and every time I do it, it either A) freezes on the kernel or B) freezes on the boot animation. My bootloader is unlocked. Here are the steps that I've tried.
1. Flash R800x_3.0.1.E.0.88_Verizon.ftf
2. Activated phone, wifi, and whatnot. Play around with it for a few minutes.
3. Flashed the kernel that came with FXP CM7.2.0 zeusc.
4. Boot up into recovery. Wipe user data, cache, dalvik cache.
5. Flash CM7.2.0 zeusc zip.
6. Reboot and the boot animation freezes. I've waited up to 30 minutes and no change. Pulled the battery out, turned on, still freezes on boot animation.
I've done the same thing with R800x_4.0.2.E.57_Verizon.ftf and still no luck. Any ideas?
game_guy said:
I've been trying to flash CM 7.2.0 and every time I do it, it either A) freezes on the kernel or B) freezes on the boot animation. My bootloader is unlocked. Here are the steps that I've tried.
1. Flash R800x_3.0.1.E.0.88_Verizon.ftf
2. Activated phone, wifi, and whatnot. Play around with it for a few minutes.
3. Flashed the kernel that came with FXP CM7.2.0 zeusc.
4. Boot up into recovery. Wipe user data, cache, dalvik cache.
5. Flash CM7.2.0 zeusc zip.
6. Reboot and the boot animation freezes. I've waited up to 30 minutes and no change. Pulled the battery out, turned on, still freezes on boot animation.
I've done the same thing with R800x_4.0.2.E.57_Verizon.ftf and still no luck. Any ideas?
Click to expand...
Click to collapse
have you ever flashed a rom and kernel before? also are you till in stock rom?
x1rocket said:
have you ever flashed a rom and kernel before? also are you till in stock rom?
Click to expand...
Click to collapse
Yes I've flashed a ROM before. Following these same steps, I was able to boot CM9. I've also managed to get AokPlay, Paranoid Android and a few other ROMs running on my device. I always flash back to stock before attempting to flash a new ROM.
game_guy said:
Yes I've flashed a ROM before. Following these same steps, I was able to boot CM9. I've also managed to get AokPlay, Paranoid Android and a few other ROMs running on my device. I always flash back to stock before attempting to flash a new ROM.
Click to expand...
Click to collapse
on the thread you have downloaded the file are the users facing the same problems or just you? must be not supported by your model or the compiled file was not a success to let you boot... if you do check, make sure you read all the pages on that thread...
x1rocket said:
on the thread you have downloaded the file are the users facing the same problems or just you? must be not supported by your model or the compiled file was not a success to let you boot... if you do check, make sure you read all the pages on that thread...
Click to expand...
Click to collapse
It's definitely compatible with my device, it even says it is. I read through the thread and it looks like one or two people are having the same issues.
game_guy said:
It's definitely compatible with my device, it even says it is. I read through the thread and it looks like one or two people are having the same issues.
Click to expand...
Click to collapse
wait a couple of days and see if those users have a fix for it... as no one else posted on this thread they wouldn't know the problem the same as I don't know...
at least I tried to help
game_guy said:
I've been trying to flash CM 7.2.0 and every time I do it, it either A) freezes on the kernel or B) freezes on the boot animation. My bootloader is unlocked. Here are the steps that I've tried.
1. Flash R800x_3.0.1.E.0.88_Verizon.ftf
2. Activated phone, wifi, and whatnot. Play around with it for a few minutes.
3. Flashed the kernel that came with FXP CM7.2.0 zeusc.
4. Boot up into recovery. Wipe user data, cache, dalvik cache.
5. Flash CM7.2.0 zeusc zip.
6. Reboot and the boot animation freezes. I've waited up to 30 minutes and no change. Pulled the battery out, turned on, still freezes on boot animation.
I've done the same thing with R800x_4.0.2.E.57_Verizon.ftf and still no luck. Any ideas?
Click to expand...
Click to collapse
If you are still having trouble flashing CM7, I would suggest downloading from zeusc section of http://get.cm
Or, you can try one of the many CDMA optimized ICS/JB ROMs.
You may have to wipe everything a few times. Of course you can always use my modified cm7 which has autorotation unlike any other cm7 for zeusc lol
Leraeniesh said:
If you are still having trouble flashing CM7, I would suggest downloading from zeusc section of get.cm
Or, you can try one of the many CDMA optimized ICS/JB ROMs.
Click to expand...
Click to collapse
I might switch back to CM9 or Paranoid. I've tried the JB ports. One has working data but no sound, and the other CDMA has everything working except I couldn't get data to work.Thanks for that URL, which one would you recommend? RC1, 2, 3 or stable?
agraceful said:
You may have to wipe everything a few times. Of course you can always use my modified cm7 which has autorotation unlike any other cm7 for zeusc lol
Click to expand...
Click to collapse
If the get.cm doesn't work either, I'll go ahead and try the one in your signature. If all else fails, I'll probably go back to CM9 or Paranoid.
Thanks for all of the help you guys, this is a pretty nice community. :3
Sorry to double post, but I tried the ones from get.cm and the modified one from agraceful, but both froze on the boot animation then crashed and froze on the kernel. I think I'm just gonna give up on this particular ROM.
Check what kind of kernel you using.
I had simillar problem whed used kernel from XDA downloaded file. When used from file downloaded from CM project site it runs with no problems.
I have no idea why that happen, maybe on XDA forum is different modificated version for 800x or 800i etc. and not working with all phones.
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