sense port issues - Sprint Samsung Galaxy S III

Tried to use logcat to figure out why rom wasn't booting but adb daemon wasn't starting which led me to believe that the kernel hadn't loaded. So I pulled the recovery log from when I installed the rom zip. It seems that for some reason the install process skips over the kernel for some reason. here is the recovery log and both updater-scripts. I cut out a lot of crap on the recovery where it was extracting apps and stuff so you can see where it skips. I get no errors or anything that I can tell. it just doesnt install the kernel.
Recovery Log
updater-script sense port
updater-script base s3
any advice?
EDIT finally got the kernel to install. I was told that all you needed to do to get it to at least boot was copy the bootclasspath from the sense kernel to the base kernel and it would (should) boot up enough for me to run logcat and figure out where to go from there. However ive swapped out the bootclasspath and left it stock. ive even left the kernel completely stock (base cm9 kernel) or installed the pure sense kernel (sense port is evo 4g lte stock rom) and I get the EXACT same boot loop. it makes it to the second boot logo (Samsung Galaxy S III) then right before the boot animation it boot loops. Ive compared all the .rc's in the ramdisk and all are the same save for the init.rc. i tried merging the base init.rc and the sense init.rc and nothing appears to change. when i install cm9 with the same base kernel i used in the port it installs fine no issues. this is driving me bananas! i cant imagine what could be present in both separate kernels that is preventing it from booting.
I even took a guess that it wasnt the kernel and tried swapping .so files and .ko's but same thing. idk what else to do. there are sense ports for the S3 i9300 and Xperia Neo that are booting, not completely functional but booting up. ive studied the kernel of both and nothing that I can tell is different besides the obvious differences in mount points and such. what all can prevent a rom from making to the boot animation (at that point i can run logcat)? is there a list? lol
I dont have a logcat for obvious reasons and recovery.log shows no errors or anything out of the ordinary. it HAS to be something with the ROM itself. maybe a file(s) im missing or something?
Sent from my SPH-L710 using xda app-developers app

GRock84 said:
Tried to use logcat to figure out why rom wasn't booting but adb daemon wasn't starting which led me to believe that the kernel hadn't loaded. So I pulled the recovery log from when I installed the rom zip. It seems that for some reason the install process skips over the kernel for some reason. here is the recovery log and both updater-scripts. I cut out a lot of crap on the recovery where it was extracting apps and stuff so you can see where it skips. I get no errors or anything that I can tell. it just doesnt install the kernel.
Recovery Log
updater-script sense port
updater-script base s3
any advice?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Are you S-OFF?

honest1212 said:
Are you S-OFF?
Click to expand...
Click to collapse
Ah see that's the trick lol this is a sense port to the S3 from the Evo 4G LTE. I can't get the darn thing booted to troubleshoot because the kernel never gets installed. I only make it to the second samsung boot logo then boot loop.
Sent from my SPH-L710 using xda app-developers app

Related

Stock rom on ext4?

just need a stock DK28 kernel modified for ext4 support, no custom boot splash, no custom boot animation support, no custom roms, just a simple ext4 supported stock kernel with absolutely no other changes, packaged up in one of those fancy edify scripted zips for flashing after the ext4 conversion
can someone help me out?
Go through the steps to install bonsai rom. Install cwm3 with ext 4. install bonsai then boot cwm and resrore the before ext 4 backup. You got dk28 with the new kernel.
Sent from my SPH-D700 using Tapatalk
is it a stock kernel though?
Zeinzu said:
is it a stock kernel though?
Click to expand...
Click to collapse
The kernel source has not been released so they are all "stock" kernels.
The only thing that has been done to them is the initramfs portion has been re-packed, this allows support for EXT4, custom boot animations, init.d, etc.
Try this.
Or if you want a EXT4 only kernel... use the search I don't feel like finding it for you.
=]
nubecoder said:
The kernel source has not been released so they are all "stock" kernels.
The only thing that has been done to them is the initramfs portion has been re-packed, this allows support for EXT4, custom boot animations, init.d, etc.
Try this.
Or if you want a EXT4 only kernel... use the search I don't feel like finding it for you.
=]
Click to expand...
Click to collapse
are there any that aren't modified for the custom boot anim support, im looking to leave everything stock and that borks the stock boot animation
There are about 4 diffrent kernels with diffrent support,all the ext4 supported kernels have boot ani support.
Sent from my Frankenstein FROYO ROM using XDA Appboot ani...
Zeinzu said:
are there any that aren't modified for the custom boot anim support
Click to expand...
Click to collapse
I don't believe so.
Zeinzu said:
that borks the stock boot animation
Click to expand...
Click to collapse
Since when? Guess I never tried to remove a custom one to see what happens.
I just tested by renaming my bootanimation.zip and rebooting.
I got a stock (as in AOSP) looking horizontal "andriod" shimmering boot-screen. (I actually kind of liked it.)
I've found the stock sprint files (images and sound), I'm going to pack up a zip and see if I can restore the stock animation.
I'll let you know how it goes.
=]
ecooce said:
There are about 4 diffrent kernels with diffrent support,all the ext4 supported kernels have boot ani support.
Sent from my Frankenstein FROYO ROM using XDA Appboot ani...
Click to expand...
Click to collapse
Do you have any references for those (as in links or what rom it's in).
I'm just curious.
=]
Ive collected several from diffrent ROMs,some are 5.6,some are 6.1,6.32... So as for links there are none,jut download ROMs to get the diffrent kernels... Like the one I use is from Mammons ROM bonsai,it has Bash support and some other goodies.But it hasnt been hacked yet with no source,just minor addons.
Sent from my Frankenstein FROYO ROM using XDA App...
so ur telling me no one has, or is going to bother with having a choice for stock boot anims?
well that sucks, cause not everyone digs custom, if adding the support for it didnt ruin the stock anim it wouldnt matter, but it does
Well I'm not sure what is going wrong, but I can't get the animation I'm working on to work.
It's almost 7am here and that's well past bed time.
I'll continue trying tomorrow.
=[
[edit]
Zeinzu said:
if adding the support for it didnt ruin the stock anim it wouldnt matter, but it does
Click to expand...
Click to collapse
Once I get the stock files I have working it will be a simple zip flash to restore the stock animation.
Gotta be something simple.
[edit2]
I found the stock images here and the stock sound here.
I converted the mp3 into wav, and modified the bootanimation.zip so it *should* work for the Epic.
The sound is working fine, but for whatever reason I cannot get the images to display, just get a black screen.
I've attached what I have now in case someone wants to try to fix it while I nap and then work.
=[
Moved to Q&A
U cannot restore the entire animation with a zip, u can only re-add the sprint anim and sound, not the stock galaxy s (unless someone found the images for it)
It just seems redundent that no one is going to make a stock ext4 supported kernel, what about those of us who want to run the stock rom on ext4 with no other changes?
Its not like I'm asking for a huge thing honestly
Sent from my Epic 4g
Zeinzu said:
Its not like I'm asking for a huge thing honestly
Click to expand...
Click to collapse
You are asking someone to re-package the kernel with only support for EXT4.
That's a lot more work than you might expect.
You could try begging / paying Dameon87 I suppose, or someone else that has experience re-packing the kernel.
Or, you could go research how to re-pack the kernel yourself.
I'll see what I can do about getting this stock animation/sound to work.
(Even though it sounds as if that would not be good enough for you.)
=]
Zeinzu said:
U cannot restore the entire animation with a zip, u can only re-add the sprint anim and sound, not the stock galaxy s (unless someone found the images for it)
It just seems redundent that no one is going to make a stock ext4 supported kernel, what about those of us who want to run the stock rom on ext4 with no other changes?
Its not like I'm asking for a huge thing honestly
Sent from my Epic 4g
Click to expand...
Click to collapse
Actually the stock ani and sound are different than with the edited kernel. The bootani.zip is what the edited kernel points too. The stock kernel points to bootani.qmp. so adding a zip with the images from the bootani.qmp will technically be fixing a boot ani with a zip!
Sent from my SPH-D700 using Tapatalk
[Update]
OK, I got the files I have working, but there is a problem.
As you pointed out, I don't have the stock Samsung animations that play after the Sprint animation.
dreamsforgotten said:
adding a zip with the images from the bootani.qmp will technically be fixing a boot ani with a zip!
Click to expand...
Click to collapse
There seem to be 3 animation files:
Code:
bootani.qmg
bootsamsung.qmg
bootsamsungloop.qmg
But there is apparently no way to get the frames out of the .qmg files (none that I could find).
I'm going to use the closet one I can find, I know I have it around here somewhere...
OK, so attached is a zip that will restore the stock boot animation.
What it does:
restores the 3 aforementioned qmg files into /system/media
restores the stock boot sound into /system/etc
installs a single black frame bootanimation.zip into /system/media​This was the only way I was able to get the entire stock boot screen to show.
Basically it plays the single black frame and then continues into the stock animation.
The single black frame is not noticeable (at least to me).
This has been tested and is working on Bonsai v2.0.1
=]
nubecoder said:
OK, so attached is a zip that will restore the stock boot animation.
What it does:
restores the 3 aforementioned qmg files into /system/media
restores the stock boot sound into /system/etc
installs a single black frame bootanimation.zip into /system/media​This was the only way I was able to get the entire stock boot screen to show.
Basically it plays the single black frame and then continues into the stock animation.
The single black frame is not noticeable (at least to me).
This has been tested and is working on Bonsai v2.0.1
=]
Click to expand...
Click to collapse
ill check this out, and thanks
I found the images yesterday in media for the landscape android word that appears on top of the Samsung video. Alternatively you can change those images to see through although I haven't tested. System/media/video folder
Sent from my SPH-D700 using Tapatalk
dreamsforgotten said:
I found the images yesterday in media for the landscape android word that appears on top of the Samsung video. Alternatively you can change those images to see through although I haven't tested. System/media/video folder
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I can't find anything other that the "shutdown" folder in "/system/media/video" (checked the DK28 leaked files).
I'm pretty sure I read that the landscape "android" animation is contained in the framework.apk.
So maybe I'm missing something here...?
=]

[Q] compiled rom not installing

I have a question,
While trying to flash a custom ROM (ICS) it does not seem to be creating the system directory. I have enough space, I am ext 4. I could post the ROM if someone wants to look at it for me.
I flashed the ROM successfully and rebooted. Hangs on HTC screen. Pulled the battery and rebooted into recovery. Adb shell showed that /system is empty.
I have compiled and flashed several ROMS but have never had this happen.
What causes this?
Thanks,
Jeff
jeffakajeff said:
I have a question,
While trying to flash a custom ROM (ICS) it does not seem to be creating the system directory. I have enough space, I am ext 4. I could post the ROM if someone wants to look at it for me.
I flashed the ROM successfully and rebooted. Hangs on HTC screen. Pulled the battery and rebooted into recovery. Adb shell showed that /system is empty.
I have compiled and flashed several ROMS but have never had this happen.
What causes this?
Thanks,
Jeff
Click to expand...
Click to collapse
theres alot of things that could cause this... to narrow it down a little, you should give us more info... like, when flashing a ROM... does it give an error? if yes, whats that error?
—————
|RIROZIZO|
—————
Adb logcat shows system/bin/sh not found.
Sent from my HTC Vision using xda premium

Can you open up a rom zip and insert your own kernel?

I have something annoying im trying to figure out. Every time I re-partition my phone with ODIN I end up having to freshly install an MTD ROM. When I install an MTD rom for the first time, my phone reboots without allowing me to flash the kernel i desire before the ROM boots up. Some people flash kernels without fresh installs, but I cant stand doing that. I end up having to re-install the same ROM in the new recovery so my phone doesnt reboot before I flash the kernel. I hope this makes sense.
Anyone know what directory the kernel is in for the rom zip file? Can i swap it out with my desired kernel without flashing problems?
You can. But you should really just use the kernel that the rom comes with. It is what is tested by the dev and devs get annoyed by bug reports from people using other kernels.
Sent from my SPH-D700 using Tapatalk
No I think you'd need to recompile the whole ROM and incorporate the zImage aka the kernel it flashes also have the updater script prompt that....its complex and I don't even know how to do it...
Sent From My SPH-D700 Running Android 4.0
marcusant said:
You can. But you should really just use the kernel that the rom comes with. It is what is tested by the dev and devs get annoyed by bug reports from people using other kernels.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I do normally, but in this instance, im using StarksyROM. The original ROM comes with Shadow 0.3 I believe.... there is a charging issue unless the kernel is updated to 0.4 or above.
(the bug is the battery charging display doesnt show up when the phone is off)

Updated 15/8/12 CM9 for One Bugs List & Solutions GSM+CDMA

Right guys THIS thread is for reporting bugs\issues and for solutions, PLEASE USE THIS THREAD and keep the DEV THREAD CLEAR. We need that thread clear for Deving uses. i will update this with every new release\hot\bugfix. if your unsure on how to create a logcat please refer to this thread
Please post logcats and please post your error like this:
Version of rom your running
DETAILED ERROR HERE (not just wifi doesnt work, explain on how it didnt work so we can reproduce)
Any mods your running and kernel version
issues with CDMA will have (CDMA) Next to them likewise for GSM
Known BUGS
Some graphic Glitch (GSM+CDMA)
**RESERVED**
Reserved
paarthdesai said:
reserved
lols
dont just say thanks hit thanks if i helped
a true lfc supporter
and a former symbian lover
sent from my awesome HTC One V using xda premium
Click to expand...
Click to collapse
shub and paarth why you both reserved?!?!
Sent from my ONE V using xda premium
Lloir said:
shub and paarth why you both reserved?!?!
Sent from my ONE V using xda premium
Click to expand...
Click to collapse
I will test and report my views there...I dunno about paarth
Sent from my HTC One V using XDA
Passa91 said:
Equivalent of a post just saying "first"... why don't you just post your thoughts when you've actually tested it. I mean, really...
On topic - it isn't clear from the dev thread, is hold press multitasking for menu key working?
Sent from my HTC One V using XDA
Click to expand...
Click to collapse
No....i fixed it..
Long press home is multitasking and multitask button us now menu...
Sent from my HTC One V using XDA
Okay so I downloaded Lloir's version of cm9 alpha build.
Currently running adi_pat's titanium kernel build 4.
So I extracted the zip and flashed the boot image thru fastboot.
Then wiped the dalvik, cache, system and data,.
Didn't boot at all.
When I went with the original titanium boot image it got to the boot animation and got stuck there.
I guess this is cm9's way of being stuck at the HTC dev screen.
All other ROMs have worked perfectly on my device. Don't know what is going wrong this time..
tranceph0rmer said:
Okay so I downloaded Lloir's version of cm9 alpha build.
Currently running adi_pat's titanium kernel build 4.
So I extracted the zip and flashed the boot image thru fastboot.
Then wiped the dalvik, cache, system and data,.
Didn't boot at all.
When I went with the original titanium boot image it got to the boot animation and got stuck there.
I guess this is cm9's way of being stuck at the HTC dev screen.
All other ROMs have worked perfectly on my device. Don't know what is going wrong this time..
Click to expand...
Click to collapse
REFLASH titanium 4 make sure it's the 1ghz one and DO NOT flash the boot.img in the rom...DO NOT FLASH BOOT.IMG in the rom.....also i would like to remind that it does take awhile on 1st boot to load....also a how to logcat
http://forum.xda-developers.com/showthread.php?t=1726238
im off to bed for a few hours i worked last night, so i'll answer anything you put up when i wake up
Cool.
Btw will the android apps for the log cats be of any help here?
tranceph0rmer said:
Btw will the android apps for the log cats be of any help here?
Click to expand...
Click to collapse
none whatsoever, you need to adb logcat and save a text file
Yep thought so...... Any way to install adb without installing the whole sdk?
Like fastboot can be installed on its own?
Bug list updated
Hi
Just FYI: I guess for most this is not new
There is a difference where kernel modules are between
stock kernel and Titanium and KISS
Stock kernel will have its modules in /system/lib/modules
Titanium based kernels have them in the ramdisk of the
boot.img in /lib/modules. So the modules will come with the kernel
Titanium or KISS kernel is NOT abel to load modules
from /system/lib/modules
You can try by doing e.g
insmod /system/lib/modules/fm_drv.ko
And you will get the error
insmod: can't insert '/system/lib/modules/fm_drv.ko': invalid module format
So when you use Titanium or KISS make sure /lib/modules contains
the modules from the boot.img. Else e.g. WIFI will not work since the
module cannot be loaded
Regards
max
maxwen said:
Hi
Just FYI: I guess for most this is not new
There is a difference where kernel modules are between
stock kernel and Titanium and KISS
Stock kernel will have its modules in /system/lib/modules
Titanium based kernels have them in the ramdisk of the
boot.img in /lib/modules. So the modules will come with the kernel
Titanium or KISS kernel is NOT abel to load modules
from /system/lib/modules
You can try by doing e.g
insmod /system/lib/modules/fm_drv.ko
And you will get the error
insmod: can't insert '/system/lib/modules/fm_drv.ko': invalid module format
So when you use Titanium or KISS make sure /lib/modules contains
the modules from the boot.img. Else e.g. WIFI will not work since the
module cannot be loaded
Regards
max
Click to expand...
Click to collapse
that would explain a few things....... i honestly forgot all about this.....thanks dude! i keep forgetting the simple crap :silly:
Lloir said:
that would explain a few things....... i honestly forgot all about this.....thanks dude! i keep forgetting the simple crap :silly:
Click to expand...
Click to collapse
Your welcome
Actually I havnt found the exact reason why there is this "invalid format" error
Since the file has the correct format
bcmdhd.ko: ELF 32-bit LSB relocatable, ARM, version 1 (SYSV), not stripped
You can of course als replace the stock modules in /system/lib/modules with
the ones from /lib/modules if you use Titanium kernel
Regards
max
EDIT: Ok I know the reason - was just stupid
10 years of linux knowledge - should have known better
fm_drv: version magic '3.0.16-g42caf24 preempt mod_unload ARMv7 ' should be '3.0.16Titanium-KISS-svn322 preempt mod_unload ARMv7'
The reason is that Titanium or KISS use a different version "magic" which is compiled into the kernel modules
I've got some graphical glitches in settings menu, app drawer, etc., I wiped everything and formatted /system. Used TitaniumKernel and built-in kernel from zip.
Did anyone experienced that?
P.S. an insmod of /lib/modules/bcmdhd.ko worked for me, but wifi didn't work as far as I could have seen with these glitches...
TechnoLover said:
I've got some graphical glitches in settings menu, I wiped everything and formatted /system. Used TitaniumKernel and built-in kernel from zip.
Did anyone experienced that?
P.S. an insmod of /lib/modules/bcmdhd.ko worked for me, but wifi didn't work as fas as I could have seen with these glitches...
Click to expand...
Click to collapse
yes it's a problem the glitches....btw i've just pushed a new git that needs testing PM me if it needs to be reverted
btw DONT EVER EVER USE the built-in kernel....im pretty sure that's what caused my device to die...only use Titanium dude
Also try using the EGL folder from the CM9 in the DEV Thread and let me know if that removes the glitches
Lloir said:
yes it's a problem the glitches....btw i've just pushed a new git that needs testing PM me if it needs to be reverted
btw DONT EVER EVER USE the built-in kernel....im pretty sure that's what caused my device to die...only use Titanium dude
Click to expand...
Click to collapse
I haven't flashed the built-in kernel, I just booted it via "fastboot boot" - normally there should happen nothing if I use it that way. I think it's a prebuilt kernel with just another ramdisk, so there shouldn't be any issues... but as long as we don't know what's the reason I flash as less as possible maybe the built-in kernel hasn't started and rebooted so fast that it booted with titaniumkernel. I don't know.

Jellybean only boot loop

Hi guys I searched the forums but can't seem to figure this one out. I can flash and boot all ICS Roms completely fine. When I try ANY Jellybean ROM AOKP, CM whatever I get stuck on a boot screen loop. I use these steps:
Flash darkside super wipe
Flash ROM
Flash gapps
Flash darkside super wipe cache
Reboot
Now I've tried cwm 5.x.x and 6.x.x and twrp. Any suggestions?
MARINERMOOSE241 said:
Hi guys I searched the forums but can't seem to figure this one out. I can flash and boot all ICS Roms completely fine. When I try ANY Jellybean ROM AOKP, CM whatever I get stuck on a boot screen loop. I use these steps:
Flash darkside super wipe
Flash ROM
Flash gapps
Flash darkside super wipe cache
Reboot
Now I've tried cwm 5.x.x and 6.x.x and twrp. Any suggestions?
Click to expand...
Click to collapse
Download the file again. Sounds like a bad flash.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Thanks elesbb but this bootloop happens with ANY JB from I try to.flash on my hercules. So I don't think its bad downloads I wonder if I posted a log at during boot if someone could help.
MARINERMOOSE241 said:
Thanks elesbb but this bootloop happens with ANY JB from I try to.flash on my hercules. So I don't think its bad downloads I wonder if I posted a log at during boot if someone could help.
Click to expand...
Click to collapse
That's why I recommended downloading again. Sometimes packets are lost in cyberspace. I don't see how your device is the only one doing this. Gotta be something on your end. (Not trying to point fingers. Just saying it can be a million and 2 things )
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Ok, I now downloaded 4 different roms ALL Jellybean and ALL get frozen during the bootscreen and bootloop. ADB just sits at waiting for device when trying to logcat. I've reflashed to stock gingerbread just fine, reflashed to ICS AOKP just fine no loops. But going to JB after just keep causing a bootloop, its driving me crazy.
MARINERMOOSE241 said:
Ok, I now downloaded 4 different roms ALL Jellybean and ALL get frozen during the bootscreen and bootloop. ADB just sits at waiting for device when trying to logcat. I've reflashed to stock gingerbread just fine, reflashed to ICS AOKP just fine no loops. But going to JB after just keep causing a bootloop, its driving me crazy.
Click to expand...
Click to collapse
What cwm are u using? I couldn't flash any Jb roms with cwm 6
Sent from my SAMSUNG-SGH-T989 using xda premium
Rememdium said:
What cwm are u using? I couldn't flash any Jb roms with cwm 6
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Were you getting freeze bootloops?
I have tried cwm 5.x nd 6 which I'm on now. Also twrp gave me the same loop. I've even gone as far.as.formatting sdcard and eemc with no luck.
MARINERMOOSE241 said:
Were you getting freeze bootloops?
I have tried cwm 5.x nd 6 which I'm on now. Also twrp gave me the same loop. I've even gone as far.as.formatting sdcard and eemc with no luck.
Click to expand...
Click to collapse
Try switching to TWRP.
Then re-download the JB rom you want to use, put it on the root of your internal SD, make sure the MD5 matches and then try flashing again. I think most of these JB boot problems are coming from CWM recoveries.
Digital1325 said:
Try switching to TWRP.
Then re-download the JB rom you want to use, put it on the root of your internal SD, make sure the MD5 matches and then try flashing again. I think most of these JB boot problems are coming from CWM recoveries.
Click to expand...
Click to collapse
No they aren't. Teamchopsticks recommends cwm 6.0.1.1 as the optimal recovery to use.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
Teamchopsticks recommends cwm 6.0.1.1 as the optimal recovery to use.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Where did you read that? And does 6.0.1.1 still have a broken cache wipe?
Someone had a similar problem in the dev thread and switching recoveries seemed to fix it. So worth trying.
Sent from a BAMF Jedi ROM from the Lightside
Digital1325 said:
Where did you read that? And does 6.0.1.1 still have a broken cache wipe?
Someone had a similar problem in the dev thread and switching recoveries seemed to fix it. So worth trying.
Sent from a BAMF Jedi ROM from the Lightside
Click to expand...
Click to collapse
I read it on their website but i came across it in binarybishops nightly thread. And no the cache wipe is fixed. I use the touch version, tried TWRP and CWM 5 hell i tried them all! They all produced the exact same results for me as far as performance goes. But ive never had any issues with 6.0.1.1 i love it to death
Ok guys this is very puzzling. I have been flashing roms for years and have never had a loop like this.
So I flashed TWRP again verified the md5 has was correct for both AOKP JB nightly and gapps. Flashed following the correct steps posted in the thread by Whitehawkx and I still get a bootloop freeze on the AOKP unicorn. So I tried CM 10 nightly... same freeze/loop. I downloaded AOKP ICS, no loop at all boots fine.
I've tried cwm 5, 6, and twrp all with the exact same results. I have formated SD external and internal EMMC... nothing has worked.... All I want is some Jelly bean goodness.... I flashed AOKP on my nexus 7 just fine. Like I said I am really stumped on this one as to why ICS roms would flash perfectly fine and using the same steps JB roms bootloop.
MARINERMOOSE241 said:
Ok guys this is very puzzling. I have been flashing roms for years and have never had a loop like this.
So I flashed TWRP again verified the md5 has was correct for both AOKP JB nightly and gapps. Flashed following the correct steps posted in the thread by Whitehawkx and I still get a bootloop freeze on the AOKP unicorn. So I tried CM 10 nightly... same freeze/loop. I downloaded AOKP ICS, no loop at all boots fine.
I've tried cwm 5, 6, and twrp all with the exact same results. I have formated SD external and internal EMMC... nothing has worked.... All I want is some Jelly bean goodness.... I flashed AOKP on my nexus 7 just fine. Like I said I am really stumped on this one as to why ICS roms would flash perfectly fine and using the same steps JB roms bootloop.
Click to expand...
Click to collapse
It's something wrong with your flash file. Use an actual adapter to transfer the file. And download it again. Then if you still get the loop plug your phone into your computer and boot it up then run adb logcat.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
It's something wrong with your flash file. Use an actual adapter to transfer the file. And download it again. Then if you still get the loop plug your phone into your computer and boot it up then run adb logcat.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
When you say flash file do you mean the ROM? If so I've tried downloading it on my Mac and transferred it via USB mode still no dice. Also I.tried to.log at during the bootloop but adb never sees the device.
MARINERMOOSE241 said:
When you say flash file do you mean the ROM? If so I've tried downloading it on my Mac and transferred it via USB mode still no dice. Also I.tried to.log at during the bootloop but adb never sees the device.
Click to expand...
Click to collapse
Yes im saying the zip. Something isnt getting placed where it belongs or something is corrupt. And DONT use the USB mode, get an actual Mirco SD to SD adapter and a SD to USB adapter and do it that way.
elesbb said:
Yes im saying the zip. Something isnt getting placed where it belongs or something is corrupt. And DONT use the USB mode, get an actual Mirco SD to SD adapter and a SD to USB adapter and do it that way.
Click to expand...
Click to collapse
I have an adapter so I can try that right now. However, if the md5 hash is correct wouldn't that mean the zip downloaded correctly? And it still doesn't answer why every JB from bootloops while ICS does not.
MARINERMOOSE241 said:
I have an adapter so I can try that right now. However, if the md5 hash is correct wouldn't that mean the zip downloaded correctly? And it still doesn't answer why every JB from bootloops while ICS does not.
Click to expand...
Click to collapse
Yes that is usually the norm. But it is millions and millions and millions of bits of data we are talking about here... all it takes is for one of those bits to either not be there or be in the wrong place to screw it up. And yes that is extremely strange, but seeing as you are the only one experiencing this, i am sure its not the ROMs and its something you are doing or not doing. Im not trying to be rude or imply that you are dumb. its just extremely hard to pin point something weird like this when i dont have the device in my hands. See where im getting here?
elesbb said:
Yes that is usually the norm. But it is millions and millions and millions of bits of data we are talking about here... all it takes is for one of those bits to either not be there or be in the wrong place to screw it up. And yes that is extremely strange, but seeing as you are the only one experiencing this, i am sure its not the ROMs and its something you are doing or not doing. Im not trying to be rude or imply that you are dumb. its just extremely hard to pin point something weird like this when i dont have the device in my hands. See where im getting here?
Click to expand...
Click to collapse
I totally agree I don't believe its the roms themselves as they seem to work for most people. I've just never ran across this before.
MARINERMOOSE241 said:
I totally agree I don't believe its the roms themselves as they seem to work for most people. I've just never ran across this before.
Click to expand...
Click to collapse
I have on my HD2. But a complete format of the memory card using HP USB disk tools fixed it. Have you tried that yet?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
I have on my HD2. But a complete format of the memory card using HP USB disk tools fixed it. Have you tried that yet?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Formated the SD card ... used the external adapter to copy the flash to the SD same bootloop I also copied the file directly to internal storage removed the sd card and flashed same result... looks like no Jelly bean for me... so freaking odd as I can flash ICS any rom all day long just fine.

Categories

Resources