Related
I was hoping some of the kernel devs can help me with a quick question. I am familiar with unpacking and repacking boot.imgs for the Droid but not for the Evo, I usually use the method found here. Is there an alternate method or even some perl scripts that will make the job as easy as it is for the Droid? Note: I am not trying to compile a boot.img, I just want to be able to edit the ramdisk of existing ones. Thanks in advance!
BuglessPete said:
I was hoping some of the kernel devs can help me with a quick question. I am familiar with unpacking and repacking boot.imgs for the Droid but not for the Evo, I usually use the method found here. Is there an alternate method or even some perl scripts that will make the job as easy as it is for the Droid? Note: I am not trying to compile a boot.img, I just want to be able to edit the ramdisk of existing ones. Thanks in advance!
Click to expand...
Click to collapse
reading through the tutorial you linked to, i see perl scripts and directions. is there a certain part of that tutorial you've used on the EVO and have had trouble or its resulted in some kind of error? guess i didn't catch what isn't working for you?
edit: reviewing the tutorial again, i have been wondering which partitions are which on our phone? boot mtd2/3 ? recovery mtd2/3? i know system is mtd4 and data is mtd5 ...
once i know which partition for sure is boot, it might be worth while for me to grab the kernel and post up the stock ramdisk as a starting point for all those looking to do simple kernel mod'n ...
Not sure why this got moved out of development section, as it is related to developing a boot.img although it was a question.
I used the unpack perl script and it threw an error. I will also try the split script when I get off work.
Sorry to resurrect a dead topic, but I'm looking into this as well, and I haven't been able to modify a ramdisk successfully (I'm basically looking to set ro.secure=0 in default.prop). I typically use the same procedure as Pete outlined in the link, but using that for the EVO results in a hang at the bootscreen. (the white HTC EVO 4G screen seen on boot) Any help would be appreciated.
Resurrecting this topic once again.
ADB functionality is broken in Sense FroYo roms, maybe all froyo roms. I can communicate appropriately through fastboot and through ADB in Recovery, but not when running.
The /sbin/adbd process isn't running like it is on other ROMS, such as eclair and gingerbread.
Following this link:
http://code.google.com/p/android/issues/detail?id=9437
I found that some nexus one devs had the same issue, and had to replace the adbd process on the ramdisk with one from another build that worked in froyo.
Following this guide that everyone links to:
http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
I was not able to use the included unpack/repack perl scripts without modifying them. It appears that the Evo has another file at the end and that script wasn't meant to handle that. Others commented out that line that kills it, I did so, but apparently that script doesn't grab the header appropriately, and the repack doesn't work appropriately for another. I get the white boot screen and it stays indefinitely.
I took the Boot.img and went through a hex editor to do it manually, and wasn't able to get the ramdisk to unzip correctly.
I'm at the end of my rope, and need someone else who's much smarter than I am to assist in what steps to take next.
I am developing a new app, and desperately need to have ADB working inside FroYo. I would run CM7, but it doesn't work right all the time, and has bad battery life for me. I use my phone for business too, so it all has to be stable.
Any ideas? I have lots of this stuff available as I've been working on it for the past couple days, so I can post links and the like to help bring anyone up to speed with what I've done. Thanks a crap-ton in advance. If you can help me get this working, I will send you a donation!
Also, this will fix ADB in all Froyo roms too, so you'd be doing the community a great favor as well.
-Nathan
kmartburrito said:
Resurrecting this topic once again.
ADB functionality is broken in Sense FroYo roms, maybe all froyo roms. I can communicate appropriately through fastboot and through ADB in Recovery, but not when running.
The /sbin/adbd process isn't running like it is on other ROMS, such as eclair and gingerbread.
Following this link:
http://code.google.com/p/android/issues/detail?id=9437
I found that some nexus one devs had the same issue, and had to replace the adbd process on the ramdisk with one from another build that worked in froyo.
Following this guide that everyone links to:
http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
I was not able to use the included unpack/repack perl scripts without modifying them. It appears that the Evo has another file at the end and that script wasn't meant to handle that. Others commented out that line that kills it, I did so, but apparently that script doesn't grab the header appropriately, and the repack doesn't work appropriately for another. I get the white boot screen and it stays indefinitely.
I took the Boot.img and went through a hex editor to do it manually, and wasn't able to get the ramdisk to unzip correctly.
I'm at the end of my rope, and need someone else who's much smarter than I am to assist in what steps to take next.
I am developing a new app, and desperately need to have ADB working inside FroYo. I would run CM7, but it doesn't work right all the time, and has bad battery life for me. I use my phone for business too, so it all has to be stable.
Any ideas? I have lots of this stuff available as I've been working on it for the past couple days, so I can post links and the like to help bring anyone up to speed with what I've done. Thanks a crap-ton in advance. If you can help me get this working, I will send you a donation!
Also, this will fix ADB in all Froyo roms too, so you'd be doing the community a great favor as well.
-Nathan
Click to expand...
Click to collapse
Adb does work in sense froyo roms. It works on mine and I nandroid between my daily sense rom and my dev sense rom when I need to. I prefer to use adb through recovery but I have successfully adb pulled and pushed com.htc.resources from the framework while my device was running just last night. I have also not changed the adb file in the ramdisk (even though I could if I wanted to) so I doubt adb not working in sense roms is the issue unless the rom maker did in fact mess with the ramdisk and inadvertently messed something up.
lovethyEVO said:
Adb does work in sense froyo roms. It works on mine and I nandroid between my daily sense rom and my dev sense rom when I need to. I prefer to use adb through recovery but I have successfully adb pulled and pushed com.htc.resources from the framework while my device was running just last night. I have also not changed the adb file in the ramdisk (even though I could if I wanted to) so I doubt adb not working in sense roms is the issue unless the rom maker did in fact mess with the ramdisk and inadvertently messed something up.
Click to expand...
Click to collapse
It's not working for me on Fresh 3.5, Evio 1.8, or Mik's Z rom that was just released. I can go back to my PC36IMG.zip (eclair) or CM7, and it works just fine.
I've tried stock and custom kernels, to no avail. I'm absolutely NOT the only person with this issue. As you can see in the post above, Nexus one users are having the same problem, as are tablet owners with Tegra 2 chipsets, etc.
So, let me ask you, what ROM are you using? Is that the only ROM you've used since upgrading from Eclair?
I am at a loss for why this isn't working. As I said before, the /sbin/adbd process is NOT running, and I get a segmentation fault when attempting to launch it. It works fine on CM7 and Eclair, but NOT froyo. Not brand new, unaltered ROM installs, nothing. Whatever it is, the only thing in common is Sense and FroYo.
Thanks for responding, I think at this point I just need people to provide other things to look at that I haven't thought of. I'd still like to learn how to unpack and repack though, it could be a last resort.
kmartburrito said:
It's not working for me on Fresh 3.5, Evio 1.8, or Mik's Z rom that was just released. I can go back to my PC36IMG.zip (eclair) or CM7, and it works just fine.
I've tried stock and custom kernels, to no avail. I'm absolutely NOT the only person with this issue. As you can see in the post above, Nexus one users are having the same problem, as are tablet owners with Tegra 2 chipsets, etc.
So, let me ask you, what ROM are you using? Is that the only ROM you've used since upgrading from Eclair?
I am at a loss for why this isn't working. As I said before, the /sbin/adbd process is NOT running, and I get a segmentation fault when attempting to launch it. It works fine on CM7 and Eclair, but NOT froyo. Not brand new, unaltered ROM installs, nothing. Whatever it is, the only thing in common is Sense and FroYo.
Thanks for responding, I think at this point I just need people to provide other things to look at that I haven't thought of. I'd still like to learn how to unpack and repack though, it could be a last resort.
Click to expand...
Click to collapse
For my daily I use a rom based on miks eng base that I rooted and edited myself. For my dev rom I use joeykrims odexed rom that I deodexed. I also use a barebones 3.70 taken directly from the ruu, rooted and edited myself as well as deodexed it.
My two dev roms provide me with at least some sort of variables since joeykrim adds some extras to his rom.
In all three roms, the only thing I changed in the ramdisk is the kernel I compile and use (htc15 compiled to have sbc, havs, undervolt, etc.).
It could be (possible though unlikely since others do have success with adb on the roms you mention) that the ramdisk may have been edited in a way that prevents adb from starting in the init files.
Again just last night, both on my replacement evo and my wifes evo (she runs what I put on her evo which is usually a more polished version of mine) I used adb while the devices were running to pull some system apps and do some editing and then pushed them back. These are both sense based 3.70 roms using the same kernel.
Your situation is puzzling me at the moment since you said it works fine on cm7 and eclair but not on any sense based froyo roms. I would have drawn the same conclusion but since I personally can use adb on a sense based froyo rom I have to think the problem lies somewhere else and not solely on froyo. I'll try to duplicate this situation though I don't think I can without seeing what your device looks like.
Well I could not get out the bootloader and bootloop after running the stock ruu.exe and updating several recovery images PC36img none of em work so I had to go to sprint to order a new one. I really want to come back to MYN ROm when I get my new Evo..But I do not want to brick it again. The only dilemma is I really do not have the total idea of what made my phone just crash force close android and start bootlooping.
I used the unrevoked one click root method and the unrevoked forever to nand unlock it. I was flashing several different kernels at first. When I saw still no improvement in battery life I went to start off flashing Fresh, then AVA then Myn. I had got a force close to with AVA rom and bootloop but i was able to get into recovery and to the splash screen. I wished I had pay attention to what kernel I flashed which was 24hrs before my phone crashed same thing happened when I flashed Myn's rom. However, I was getting crazy bootloops when I first used the battery tweak and after I saw the battery drain I tried a different kernel. At first i was wiping both cache in between but since so many kernels even the stock kernel was giving me a loop at the splash screen (where myn warm 2.2. would come up) I started wiping less just to finally get a kernel which would be stable. The last kernel I flashed I remember was netarchy 4.1.8 cfs fresh compatible around saturday 3pm and around 3am the phone just crashed android crashed and the worst bootloop started happening.
So can anyone give me some feedback please that has their device running smooth with this Rom and/or have had this issue before? Do you recommend unrevoked forever? Does anyone may think its due to flashing so many kernels?
Are you paying for the new phoneor is the warranty taking fare of it.
I'm new to to android scene, but it seems like you shot first and asked questions later... approach could have cost you a new phone.
Anyways have you given up on your old phone. I'm sure there's ways to fix.
What recovery version do you have?
Depending on what recovery you have, you should have usb access still, if so drop a another rom in there and flash via recovery.
Sent from my PC36100 using XDA App
you more then likely didnt actually brick that phone. i would wager if you had asked and tried a few more things that you could have gotten it to work. If the phone boots at all and goes to a boatloader or fastboot then it is 99.999% of the time not bricked and can be fixed.
for example (and you may have tried) the only PC36IMG that normally works most of the time is the original eng bootloader in toasts old root method. if you tried any others most have them dont seem to rewrite everything to get it working.
as far as what caused it there is no way of knowing with the information you provided. I have run the rom and it has been stable. I doubt it was flashing so much as myself and many others flash daily with out problems.
At a lost but luckily I did not have to pay for a new phone
omegasun18 said:
you more then likely didnt actually brick that phone. i would wager if you had asked and tried a few more things that you could have gotten it to work. If the phone boots at all and goes to a boatloader or fastboot then it is 99.999% of the time not bricked and can be fixed.
for example (and you may have tried) the only PC36IMG that normally works most of the time is the original eng bootloader in toasts old root method. if you tried any others most have them dont seem to rewrite everything to get it working.
as far as what caused it there is no way of knowing with the information you provided. I have run the rom and it has been stable. I doubt it was flashing so much as myself and many others flash daily with out problems.
Click to expand...
Click to collapse
I agree I do not think i bricked it but I have tried so many PC36IMG and different bootloaders I am now way more familiar with android and recovery than before lol. I saw your posts in another thread about a guy with the same issue flintr i think but the toast 2 eng still was not working however those were the first i was trying it may work now since I'm sure I was using a different hboot the 97 version then.
I am not sure if there is anyway its going to work now since even though it still says im Ship S-off I have tried running the stock ruu. I tried the fastboot and i flashed an older hboot to get my fastboot commands..so i ran the command fastboot flash recovery recovery-1.8ra. img but it still would not get into recovery i really do not have any idea what happened.
I really think somehow my kernel is affecting everything. I tried to flash a kernel through fastboot and i was getting error it could also be though i do not have the right format for my kernel file.
potna said:
Are you paying for the new phoneor is the warranty taking fare of it.
I'm new to to android scene, but it seems like you shot first and asked questions later... approach could have cost you a new phone.
Anyways have you given up on your old phone. I'm sure there's ways to fix.
What recovery version do you have?
Depending on what recovery you have, you should have usb access still, if so drop a another rom in there and flash via recovery.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I can't get into recovery..as soon as i select recovery it starts bootlooping.
I'm not paying for the new phone I went to a small sprint store so they just looked at it tried to clear data in bootloader and then ordered me a new phone.
Fair enough, sometimes a fresh start can be good. Good luck
Sent from my PC36100 using XDA App
I've run into a very strange issue where ADB isn't functioning properly in two of the sense Roms I've tried recently, both Fresh 3.5.0.1 and the newest Evio Rom by Caulkin, 1.8 I believe.
I can't get the phone to go into USB debugging mode, although it works just fine in CM7 and another gingerbread rom I tried yesterday.
Here's some of the things I've tried, give me something I haven't tried, I dare ya!
Wiping properly in recovery (with Amon Ra 2.3, 1.8.0, and clockwork recoveries 3.x and 2.5.x)
Using Caulkin's Format All in recovery
my golden nandroid backup of Fresh didn't work, neither did a fresh fresh install
ADB works in fastboot or recovery, but not in the ROM
ADB works just fine in CM7 and non-sense ROMS (tried 2)
I tried going back to the roots by flashing my post nand-unlocking PC36img.zip and it worked fine, new fresh 3.5 install, borked.
Different USB ports
Different USB cables
Different Android SDKs
Different Android USB Drivers
My wife's HTC Hero works fine on those same ports on the same machines
two machines, one XP 32 bit and one win7 64 bit, wifes works on both, my evo works on neither.
doesn't work on stock fresh kernel, doesn't work on netarchy custom kernel.
Used to work, because I use my Evo for a test device on my apps, but I can't remember if it has ever worked on Fresh 3.5
Tried formatting my SD just to be sure there wasn't a remnant on it.
And oh yes, I made sure USB Debugging was checked.
As you can see I tried a lot. I'm very familiar with ADB and its nuances. This is genuinely stumping me, as I feel I've eliminated nearly all variables and tried nearly all configurations.
Any ideas, or anyone have something similar happen?
Not sure if this is it, but could it be something to do with boot.img.
http://modmymobile.com/forums/403-m...x-remount-failed-operation-not-permitted.html
I have the same problem. Mine is a stock rom thats been rooted by unrevoked but I haven't flashed anything on it yet. Apparently there is a line in default.prop for ADB and if it is deactived some features do not work well. You can change it but the only way to get it permanent is to edit the default.prop in boot.img.
Not sure if this is remotely the case because these are custom roms ... but its worth getting it out there because I never knew this before.
trimeijer said:
Not sure if this is it, but could it be something to do with boot.img.
http://modmymobile.com/forums/403-m...x-remount-failed-operation-not-permitted.html
I have the same problem. Mine is a stock rom thats been rooted by unrevoked but I haven't flashed anything on it yet. Apparently there is a line in default.prop for ADB and if it is deactived some features do not work well. You can change it but the only way to get it permanent is to edit the default.prop in boot.img.
Not sure if this is remotely the case because these are custom roms ... but its worth getting it out there because I never knew this before.
Click to expand...
Click to collapse
I'll flash back to Fresh tonight and check the build.prop to see if you're right.
I did notice that Flipz said he took the debug message out so it shouldn't pop up, but maybe that meant he disabled those lines in the build.prop. I would think he would know better than to do that, though, as that would disable ADB altogether, something he surely would see. It's totally possible though.
is there any way that mine could have gotten modified or something I wonder? I'd think no, because that would have to come from his install, especially on my new installs I did. Weird.
Unfortunately, my default.prop is the same as in the correct version in the link you posted. I'm literally at a loss of what else to try. Hoping some more pop in to share as I doubt we're the only two with this or have experienced this before.
I think I've figured out what's going on, now I just need to figure out how to fix it.
Like this post below, I think that the ADBD process isn't running because I couldn't find it in my process list. They used one from another build image and replaced their current one.
http://code.google.com/p/android/issues/detail?id=9437
Anyone done this before or could provide some guidance in addition to that thread?
I'd really appreciate the help.
My problem is that I can't write to /system but I think that might be something wrong with my root, even though I have s-OFF and I did flash a rooted rom ... not sure whats going on. I can only write to it in recovery.
Other ADB things work for my, like writing else where, shell, logcat ..etc
trimeijer said:
My problem is that I can't write to /system but I think that might be something wrong with my root, even though I have s-OFF and I did flash a rooted rom ... not sure whats going on. I can only write to it in recovery.
Other ADB things work for my, like writing else where, shell, logcat ..etc
Click to expand...
Click to collapse
Have you tried the "adb remount" command prior to trying to write to system? That will get you sometimes.
I pulled the boot.img from CM6 and replaced the /sbin/abdb process with the one from CM6 inside the Fresh boot.img. When I repacked, everything looked good, I installed Fresh Rom, and then it won't boot. Not at all. Wish I knew more about how to do that. I think I'm going to try again, but was following the perl scripts he posts on this page:
http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
I had to suppress a message in one of them because there was a fourth file, and it says it was not created to be able to handle those. Read on another forum to comment it out. Anyway, it didn't work but I'm going to keep trying.
Installed CM7 again, and there it is as a process, /sbin/adbd. That's got to be the key.
Yeah adb remount doesn't do anything for me. Still errors.
I looked for my processes using ps ux and got nothing. Then in my default.prop is a line
"persist.service.adb.enable=0"
which they said was a problem and it sounds like my/our problem of there being no service. So i'm going to try another stock rom. I am using the OTA from teshxx but when I tried to modify it in the kitchen it said it had no boot.img (which could be why the setting is disabled and I don't have 'root adb'.)
@kmartburrito sounds like a signing issue right? I mean I messed with stuff like that before but I could never get it to boot properly after editing anything. Never really pursued it too much though. Read through the guide and it doesn't really have anything to do with signing ... but i know the space allocated for each section of the RAM is very specific so maybe there was a mismatch.
trimeijer said:
Yeah adb remount doesn't do anything for me. Still errors.
I looked for my processes using ps ux and got nothing. Then in my default.prop is a line
"persist.service.adb.enable=0"
which they said was a problem and it sounds like my/our problem of there being no service. So i'm going to try another stock rom. I am using the OTA from teshxx but when I tried to modify it in the kitchen it said it had no boot.img (which could be why the setting is disabled and I don't have 'root adb'.)
@kmartburrito sounds like a signing issue right? I mean I messed with stuff like that before but I could never get it to boot properly after editing anything. Never really pursued it too much though. Read through the guide and it doesn't really have anything to do with signing ... but i know the space allocated for each section of the RAM is very specific so maybe there was a mismatch.
Click to expand...
Click to collapse
Yep, I'm betting that's your problem. My line with that has a value of 1, so I'm not going to be any help from that standpoint. However, when you remount your filesystem as writable, you can modify that default.prop file and it SHOULD stick, in case you hit that same issue on your next rom.
I'm still trying to figure out what the hell is going on with my situation. I talked to another guy in a different thread and he explained that he is able to ADB in froyo sense roms, so even though I'm getting the same issue in multiple roms and not in non-sense roms, there's another person somewhere without the problem, so it logically can't be the ROM, unless it's a per-rom basis, and I've just hit the wrong rom three times in a row. Who the eff knows! This is really frustrating, but I guarantee you I will figure this out soon. I need to continue working on my app, so this needs to get fixed. Soon.
kmartburrito said:
Yep, I'm betting that's your problem. My line with that has a value of 1, so I'm not going to be any help from that standpoint. However, when you remount your filesystem as writable, you can modify that default.prop file and it SHOULD stick, in case you hit that same issue on your next rom.
I'm still trying to figure out what the hell is going on with my situation. I talked to another guy in a different thread and he explained that he is able to ADB in froyo sense roms, so even though I'm getting the same issue in multiple roms and not in non-sense roms, there's another person somewhere without the problem, so it logically can't be the ROM, unless it's a per-rom basis, and I've just hit the wrong rom three times in a row. Who the eff knows! This is really frustrating, but I guarantee you I will figure this out soon. I need to continue working on my app, so this needs to get fixed. Soon.
Click to expand...
Click to collapse
Have you tried the SprintLovers Rom? It is the closest to Stock you can get and it has regular updates. If that works maybe you can examine the difference with Fresh.
Maybe a logcat would help.
From a # prompt try the following
stop adbd
setprop persist.service.adb.enable=1
start adbd
Then try connecting via usb/adb shell.
JusticeAA said:
Have you tried the SprintLovers Rom? It is the closest to Stock you can get and it has regular updates. If that works maybe you can examine the difference with Fresh.
Maybe a logcat would help.
Click to expand...
Click to collapse
Hey, trying this now, will let you know what I find. Thanks for the idea!
gpz1100 said:
From a # prompt try the following
stop adbd
setprop persist.service.adb.enable=1
start adbd
Then try connecting via usb/adb shell.
Click to expand...
Click to collapse
Unfortunately, this is already set as such in my properties. I tried it anyway though on Mikz rom, and ADBD still isn't starting or working afterwards.
You know what it seems like? It seems that this is an issue with the HTC Kernel after one of the first versions that they released after FroYo. I say that because it works on Fresh's 3.1.0.2 rom which was one of the first FroYo builds, and it doesn't really work after that, which was a newer base build and newer Kernel. Doesn't work on really any other sense-based ROM for me either.
It DOES, however, work on any AOSP rom (which also uses a diff kernel) Which is one thought as to why it might not be working for me. The strange thing is though that this is somewhat isolated to my Evo. Maybe I have a lot of bad blocks or something, but something's fishy in that it works with early FroYo roms and any AOSP roms consistently, but not new Sense roms. So, either the majority of Sense devs are using Fresh's stuff as a base, or the problem is a bigger one related to the base build or Kernel itself.
I tried using the old HTC Kernel on a new build of Fresh, and found that the ADBD process did in fact appear when using a ps command, but it still did not function properly.
And furthermore, there is absolutely jack **** on documentation out there on what makes ADB work, or what could make it not work.
Since you mentioned kernels, have you tried a different one than what's in fresh?
I'm using the net's latest cfs kernel, and was using the previous 4.3.2 before. I'm not a big fan of the #15 kernel as it breaks the processing of scripts in init.d .
gpz1100 said:
Since you mentioned kernels, have you tried a different one than what's in fresh?
I'm using the net's latest cfs kernel, and was using the previous 4.3.2 before. I'm not a big fan of the #15 kernel as it breaks the processing of scripts in init.d .
Click to expand...
Click to collapse
Yep, several versions of Netarchy's kernel, several HTC, no dice. I suppose that should rule out the Kernel and point to the base build. What is really weird though is that it's happening mostly just to me, although there are a couple others for the Evo I'm sure (many might not even know it) and there are definitely others affected like I am on different devices.
Hardware 002 and rooted using part 1 and part 2 of toast's method.
Hi
Guys i need your help. Pleas can someone tell me for now what mods is much better for I927R (Also withe very stability and with much less bugs) ?!
I found Liquid Smooth but it have some problem so i need your guide about other mods.
Thank you
ICS Roms are the best and most stable... Stock ICS from AT&T UCLJ3 or any roms based off of it ... Dman's daily driver, Ice Pop Rom by RawRaw, LiteRom by TheGreaterGood...
Unfortunately none of those are being maintained but I had been running Dman's for the last couple months, great battery life when paired w/ JuiceDefender (20+hours of heavy use when I'm not sleeping).
Now the newest CM10.1 by Spyke seems pretty solid ... Just a couple of issues.
ICS is the only one you'll get bug free, though. Stock is hard to compete with when we're pairing up roms without a true Devdeloper.
On this subject, I've just reverted back to using IcePop ROM after (unhappily) downgrading from Spyke's latest 10.1 ROM - just mainly because of the Bluetooth headset issue, which I really need working for work purposes.
I'm just wondering if there are any ICS builds that have GPS working correctly? I tried flashing the Rogers modem (since my phone was originally a Rogers import, flashed to AT&T ICS, then played with ICS from there) and first time I ran GPS status it took 771 seconds... I'm going to keep trying just in case that was the first time only, but 12 minutes is still a very long time for an initial fix .
Also - I've found that I'm getting more and more bootloop problems even with clean installs - so wiping cache, data, dalvic, etc. Is there some way to do a *thorough* wipe without bricking the phone? I can back all my data up no worries, but next time I move to JB (in the optimism that the BT issues will be fixed soon, judging by the positive progress being made by Spyke ) I would like to do a clean build from scratch and not have to gamble being able to start the phone up again
David - I always go into mount options of CWM and format /system prior to a new flash .. I'm not sure if flashing with Odin will get rid of any previous settings, its something to attempt though.
I, also, had reverted to using JB Because GPS wouldn't work ... There's a thread in here (search for it) that shows the solution to the GPS fix, its editing sirgps.conf and gps.conf ... I was getting a fix on GPS in under 30 seconds.... GPS was a huge let down in the stock ICS rom, Even when using TheGreaterGoods LiteRom w/ GPS fix I found after a couple of days my gps didn't hold....
Thanks for the reply.
I was considering formatting /system this morning when I was getting stuck in a boot loop from trying to get M3 running, but decided it was a risk I'd have to check up on first . Next time I do a build from scratch (I'm going to resist until the BT stuff is working - fingers crossed!) I'll do that.
I remember having a look at the gps.conf fix but don't recall anything about sirgps.conf - so I will look it up, thanks!
As an aside, I've been checking the GPS fix a couple of times since my last post and it is coming up in under 30 seconds each time... I'm wondering if my attempt to flash the Rogers modem did in fact fix the issue... I'd do a reboot but I'm too scared I won't get the phone up again XD
EDIT:
Found the fix, I did a few of the changes (rather than all of them), and it's now picking up 8 satellites instead of 3-5, and getting a stronger signal from each... and all I did was point it to the AU ntp server, and tell it I'm not on the ATT network . I'll save the suggested settings to a text file on my SD card so next time I'm out and about and if it plays up I'll have access to the details.
yohan4ws said:
David - I always go into mount options of CWM and format /system prior to a new flash .. I'm not sure if flashing with Odin will get rid of any previous settings, its something to attempt though.
Click to expand...
Click to collapse
Had to restart my phone tonight and got caught in a boot loop again... after trying a few things I flashed Lite Kernel (I'm still using ICS again at the moment) and that seems to have solved the boot loop issues. I'm thinking that with all the ROM flashing I've been doing the fact that I actually had the phone running without flashing an ICS specific kernel (after running JB) was screwing things up.
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
davidpartay said:
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
Click to expand...
Click to collapse
That has to be very concerning to you, I've never had an issue booting any ROM. And very strange flashing the Kernel separately would resolve your booting issues...
Did you try to flash any of the stock roms w/ Odin ? I have read that we can only flash back to stock Gingerbread from JellyBean if we flash a GB or ICS CWM ROM and then go back with Odin otherwise there will be boot issues.
If I were in your position I would try and do a full revert back to the earliest version of gingerbread I could find on samfirmware and then use Kies to udpate - THEN I would retry flashing to a newer JB or ICS Rom.
Pretty time consuming but that is the price we pay to mod
davidpartay said:
Had to restart my phone tonight and got caught in a boot loop again... after trying a few things I flashed Lite Kernel (I'm still using ICS again at the moment) and that seems to have solved the boot loop issues. I'm thinking that with all the ROM flashing I've been doing the fact that I actually had the phone running without flashing an ICS specific kernel (after running JB) was screwing things up.
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
Click to expand...
Click to collapse
My phone has an issue, simple I couldnt reboot it, I must power off and wait a little. You can try it when you flash something, just remove battery and usb cable, and wait 2 minutes, before you turn on.
yohan4ws said:
Did you try to flash any of the stock roms w/ Odin ? I have read that we can only flash back to stock Gingerbread from JellyBean if we flash a GB or ICS CWM ROM and then go back with Odin otherwise there will be boot issues.
Click to expand...
Click to collapse
Not yet. I'll have to check which ones I have - I'm certain I have the AT&T ICS rom from November but then I'd have to go digging through my email for the unlock code again, so I'm trying to avoid doing that at this point . If i can find the stock GB Rogers rom at some point I might flash that one back on before I do any more upgrades. The phone is up and running at this point though, so I'm not too fussed. I've also noticed that it's a little quicker than before so I think the version of LiteKernel I installed was a good idea anyway.
bubor said:
My phone has an issue, simple I couldnt reboot it, I must power off and wait a little. You can try it when you flash something, just remove battery and usb cable, and wait 2 minutes, before you turn on.
Click to expand...
Click to collapse
I've tried pulling the battery a few times, but probably no longer than 30 seconds. Next time I'll give it a couple of minutes. I tend to do this late at night when I'm not expecting any calls (except fire brigade but I have a pager for that too) so time without a phone is no issue to me
Yesssss
After much irritation at continually getting stuck in boot loops again, I've 'Oneclicked' the phone twice, got fed up with the AT&T ICS ROM within about 5 minutes, gave up on IcePop because of buggy GAPPS...
And thought, bugger it. Format /system. Factory reset. Clear cache + Dalvik. Installed in this order:
Jellybean 4.2 ROM from 0217
Spyke's M3 update
PAC rom
GAPPS dated 0427
"Kick-ass Kernel"
and it BOOTED FIRST GO
I am pleased
Does JB need already to be installed before putting the M3 revisions on? Maybe that's where I've been going wrong all along, because my attempts at running both the standard M3 and PAC ROM (even immediately after OneClicking) resulted in boot loops or eternal boot loading.
Uhh... what do you mean by "One Clicking" ??
I know there's a "superoneclick" that will flash and root the rom all at once, but I never personally found it to work for our glides.
Using CWM and installing the ROM through the CWM boot menu is severaly key presses so ... not too sure what you're referring to.
Also, I've always downloaded to a hardwired computer then copied over USB to my phone and flashed ... sometimes the download will have errors if I grab it from my phone.
I'm assuming it's a variant of SuperOneClick... The title is 'Odin3Excution v1.85' and then underneath it says 'I927UCLG9_OneClick'.
And it worked just fine, I did have a stock rom that I tried to flash with Odin but it kept giving me errors, the OneClick method worked.
davidpartay said:
I'm assuming it's a variant of SuperOneClick... The title is 'Odin3Excution v1.85' and then underneath it says 'I927UCLG9_OneClick'.
And it worked just fine, I did have a stock rom that I tried to flash with Odin but it kept giving me errors, the OneClick method worked.
Click to expand...
Click to collapse
Interesting... for future reference, www.samfirmware.com has the stock firmwares, then there's the superUser file floating around the forums that allows you to root by flashing it. Passed that, remove bloat.
Glad you got it working! Welcome to JB
Hello, Im new to all of this so please understand. Okay, I have a Sprint GS3, I rooted it using the toolbox thing it worked but I decided that I didnt want the root anymore. I loaded stock software and booted it up normal. The only problem now is my wifi isnt turning on. Ive searched page after page on google, ask and bing. I dont know what to do anymore. Im just about to just say screw it and give up. Any help will be much appreciated.
You Odin'd back to Stock, and now your WiFi is not working correctly ? Are you certain your connecting to your Router ? Did you check the Router to make sure it's working correctly ? Did you try to connect to the Router with another Device ?
If you still have a custom recovery installed, I'd say to just flash another rom. The toolbox kills your WiFi fir sine reason, which can only be fixed by flashing another kernel, and roms have the kernels built in so, you might as well kill two birds with one stone
You could just flash stock rooted though, no need to go full out custom
Wifi not turning on
What I mean is my phone's wifi wont turn on at all. How do I get everything back to normal like before I rooted it?
Brblank44 said:
What I mean is my phone's wifi wont turn on at all. How do I get everything back to normal like before I rooted it?
Click to expand...
Click to collapse
Ok, this method should work and do exactly what you wanted, but you'll still have root access.
Below, I have quoted a post I made a while back when trying to help someone out.
Down below I link to Freeza's stock Rom, which is what you want if you want the stock phone with root. The one you want to download is the DeOdex MD4 one:
DeOdex:
Sprint Touchwiz Jelly Bean 4.1.2 L710VPBMD4 | Mirror
MD5: 77262D9D6CF1A6AF30A8981A95A75D57
Click to expand...
Click to collapse
In step #4, the wipe system is very important. It's most likely that something in your /system folder is messing up your wifi. Just flashing a new Rom over might not fix it. I'd also wipe /data, 'cause a fresh wipe is much less likely to have issues.
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to the rooting guide and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
Brblank44 said:
What I mean is my phone's wifi wont turn on at all. How do I get everything back to normal like before I rooted it?
Click to expand...
Click to collapse
Yes. The toolbox kills your WiFi completely and you have to flash another rom to fix it. Flash stock rooted from freezas thread and you should be good to go.
CNexus said:
If you still have a custom recovery installed, I'd say to just flash another rom. The toolbox kills your WiFi fir sine reason, which can only be fixed by flashing another kernel, and roms have the kernels built in so, you might as well kill two birds with one stone
You could just flash stock rooted though, no need to go full out custom
Click to expand...
Click to collapse
Why do people use a toolbox on a phone that's so easy to root without it?
flastnoles11 said:
Why do people use a toolbox on a phone that's so easy to root without it?
Click to expand...
Click to collapse
When I first rooted my phone (back pre LJ7 days), I used it because I came from the EVO 4G, which was notoriously difficult to root (and which needed a toolkit). So when I came to the GS3, I figured it'd be the same way. Fortunately, the toolkit worked better back then and I didn't have an issue. Now that I've helped others use Odin (and have used it myself a number of times), I don't point to the toolkit anymore.
But my point is, sometimes people assume it's difficult, see a toolkit that is meant to make it easier and decide that's the way to go.
topherk said:
Ok, this method should work and do exactly what you wanted, but you'll still have root access.
Below, I have quoted a post I made a while back when trying to help someone out.
Down below I link to Freeza's stock Rom, which is what you want if you want the stock phone with root. The one you want to download is the DeOdex MD4 one:
In step #4, the wipe system is very important. It's most likely that something in your /system folder is messing up your wifi. Just flashing a new Rom over might not fix it. I'd also wipe /data, 'cause a fresh wipe is much less likely to have issues.
Click to expand...
Click to collapse
Thank you very much. I will try this as soon as I can.
topherk said:
When I first rooted my phone (back pre LJ7 days), I used it because I came from the EVO 4G, which was notoriously difficult to root (and which needed a toolkit). So when I came to the GS3, I figured it'd be the same way. Fortunately, the toolkit worked better back then and I didn't have an issue. Now that I've helped others use Odin (and have used it myself a number of times), I don't point to the toolkit anymore.
But my point is, sometimes people assume it's difficult, see a toolkit that is meant to make it easier and decide that's the way to go.
Click to expand...
Click to collapse
I get that, but just a tiny bit of reading around well show you the toolkit is actually the harder way to root this phone in my opinion... Just saying
flastnoles11 said:
I get that, but just a tiny bit of reading around well show you the toolkit is actually the harder way to root this phone in my opinion... Just saying
Click to expand...
Click to collapse
I totally agree that the toolkit is much more complicated and a bit of a "black box." Hence why I don't recommend it anymore.
But back then, even though I read a whole lot, I decided to go with the toolkit because it felt safer. Heck, I eevn donated so I could get the "pro" features! And for people who aren't that comfortable "hacking" things, it's tempting to use something that'll do the "hard work" for you, even if the normal way of doing it is relatively simple.
That's why I always try to spell things out very clearly for people (I do like numbered lists, don't I?). If someone responds to a thread with "just wipe data and flash a new rom," most "noobs" will hesitate because while they may know those terms, they don't know the procedure and will be afraid of messing it up. With the numbered list of instructions, they typically feel much more comfortable with doing it themselves.
Just my two cents.
Yeah, very true (@topherk). The first time I rooted my firdt phone, I saw all the guides and stuff, but settled on a toolkit sort of program to do it for me...subsequent phones I've always rooted by hand. For me it kinda sucks that there's no way to root the S3 manually (as in like, push this to.the phone, reboot, run this command then flash recovery)
Having come from 2 HTC devices (evo and evo shift), I kinda feel like ODIN is a "cheating" way to root lol. But that's just me.
Whats a md5? It says no md5 file and gives me an error.
Brblank44 said:
Whats a md5? It says no md5 file and gives me an error.
Click to expand...
Click to collapse
Thats normal,.the great majority of flashable zips do not include an md5 file.
What that is referring to is a hashing function, called the md5sum, that can be used to verify the integrity of a file. Most devs will provide this (in number format) so that you can check the md5sum of your local copy/download against what they provide. If anything goes wrong in a download or file transfer, the md5sum of your copy will not match the expected value, confirming that it was a bad download or that something went wrong along the way.
For your case, TWRP always checks to see if the flashable zip includes an md5sum check file that it can check your file against as an added precaution that you're not flashing something corrupted.
Brblank44 said:
Whats a md5? It says no md5 file and gives me an error.
Click to expand...
Click to collapse
Don't do the md5 verification in the Recovery. That typically fails, even if the md5 is correct.
I typically do it in Windows (I use this program, works great). If it's a really large file or I don't feel confident about the cable I'm using, I'll also check the md5sum in ES Explorer on the phone after I transfer it.
Okay I flashed it and I have the same problem. Wifi not turning on. The detox whatever its called didn't work. So I took it to sprint today after having flashed it and everything and they did a hard reset. I lost everything. Sprint couldn't swap the phone out for a new one. I am thinking about sending it back to samsung. So they can fix it. Any other ideas guys? Also thank you for your understanding and helping me.
Brblank44 said:
Okay I flashed it and I have the same problem. Wifi not turning on. The detox whatever its called didn't work. So I took it to sprint today after having flashed it and everything and they did a hard reset. I lost everything. Sprint couldn't swap the phone out for a new one. I am thinking about sending it back to samsung. So they can fix it. Any other ideas guys? Also thank you for your understanding and helping me.
Click to expand...
Click to collapse
Brblank,
Try this easy method to return to stock everything including recovery, flash count reset and device status normal. It worked perfectly for me.
Before flashing wipe Cache and Dalvik and factory reset.Then flash the file. Make sure you choose the correct file (16gb or 32gb version).
Even if it doesn't fix your WiFi issue it will put your phone in the proper state to send to Samsung.
You can place the file on your internal or external card.
Return to Stock Link
With much thanks to billard412
Hope this helps you.