I have been running the snow jelly bean rom for months, its the only thing that has ever been done to phone the best i can remember. Everytime i try to install another rom other than that one or stock it soft bricks my phone. and help would be appreciated.
creed106 said:
I have been running the snow jelly bean rom for months, its the only thing that has ever been done to phone the best i can remember. Everytime i try to install another rom other than that one or stock it soft bricks my phone. and help would be appreciated.
Click to expand...
Click to collapse
Have you ever flashed teenybin or stock 4.1 with lgnpst or accepted the 4.1 OTA update? If not, and you are attempting to flash current 4.2 releases, that is your problem. You need to update to the current TZ. Read the teenybin thread.
Sent from my Optimus G using Tapatalk 4 Beta
roms
dandrumheller said:
Have you ever flashed teenybin or stock 4.1 with lgnpst or accepted the 4.1 OTA update? If not, and you are attempting to flash current 4.2 releases, that is your problem. You need to update to the current TZ. Read the teenybin thread.
Sent from my Optimus G using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok that has to be it I tried lgnpst with teenybin but when you have to select the .dsl nothing was in the menu and I couldn't find it so I gave up.
Related
I have been waiting patiently on the Jelly Bean update for the SGH-I777, and finally got frustrated and decided to root and get a custom rom. The walkthrough that I followed apparantly had the I9100 kernel linked so after I finished, I had no modem. I found a flash to stock, but it put me back to Gingerbread and rooted. Also, CWM does not work properly either, I keep getting errors when trying to boot into recovery. So, my question is, how can I fix this or how can return the phone to ICS and wait for Jelly Bean official?
rpeterson251 said:
I have been waiting patiently on the Jelly Bean update for the SGH-I777, and finally got frustrated and decided to root and get a custom rom. The walkthrough that I followed apparantly had the I9100 kernel linked so after I finished, I had no modem. I found a flash to stock, but it put me back to Gingerbread and rooted. Also, CWM does not work properly either, I keep getting errors when trying to boot into recovery. So, my question is, how can I fix this or how can return the phone to ICS and wait for Jelly Bean official?
Click to expand...
Click to collapse
Install mobile odin lite, and flash Siyah gingerbread kernel. That should give you cwm. And then you can flash whatever rom you want.
Ok, got Siyah installed. Now, can you recommend a solid Jelly Bean build?
rpeterson251 said:
Ok, got Siyah installed. Now, can you recommend a solid Jelly Bean build?
Click to expand...
Click to collapse
Just flash a few and find one that meets your needs. Lots to choose from. Good luck, happy flashing
Ok, things have progressed a bit, I have now gotten Siyah to run and downloaded/flashed AOKP's Jelly Bean build but the phone seems to be stuck on the unicorn screen "Initiating Swagger". Any ideas?
Update: After wiping Dalvik and Cache and Data, I have a successful boot!
It's in the Q A section..
Sent from my SAMSUNG-SGH-I777 using xda premium
bqudamith said:
It's in the Q A section..
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
You're a little late..he figured it out.
bqudamith said:
It's in the Q A section..
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Dude. Replying to answered threads or replying with non useful info isn't a good way to increase post count. I've seen you do this on like 4 threads today.
Just a heads up. Your chancesnof getting official JB armless then 1% as att has dropped all update support for it.
Batcom2
zelendel said:
Just a heads up. Your chancesnof getting official JB armless then 1% as att has dropped all update support for it.
Batcom2
Click to expand...
Click to collapse
I've still got faith in the Pirate. Eagerly awaiting Jellybean Binnacle wooot!
Phalanx7621 said:
I've still got faith in the Pirate. Eagerly awaiting Jellybean Binnacle wooot!
Click to expand...
Click to collapse
U mean Beannacle?
brandonarev said:
U mean Beannacle?
Click to expand...
Click to collapse
Hellz yes!
Hi all, thanks for having such a helpful support forum. I just picked up a new Note 2 and it is on FW 4.1.1. I want to unlock and root/ROM and was wondering about the recommended sequence.
Should I first use Casual to unlock, or should I take the OTA (which I believe updates the bootloader) then unlock? Is there any benefit or detriment to using one way or the other? Thanks for any help.
Sent from my SCH-I605 using xda premium
Over in origional dev section adam has the new root,jailbreak, recovery for the new 4.1.2 ota. So if you want stock 4.1.2 with root and all that you would be safe to take the ota on stock then run CASUAL. I beleive either way your reallywanting 4.1.2 unlocked so you can have custom roms and ive seen some of the roms being updated for the vramc3 base anyhow. So if want you could run casual now with 4.1.1 that you have (you just picked it up so im assuming its all stock) and flash a cust9m rom that has 4.1.2 already implimented. cheak out the rooting/custom rom guide and the jailbreak thread and decide. In the end both paths will lead to the same place.
Just root/unlock 4.1.1 and flash a 4.1.2 VRAMC3 rom of choice in recovery...
Thanks for the help, I appreciate it. I thought it might be six of one half dozen of the other, but after recently going through OTA he11 on the DNA I'm really leery of any updates.
Sent from my SCH-I605 using xda premium
MunkinDrunky said:
Over in origional dev section adam has the new root,jailbreak, recovery for the new 4.1.2 ota. So if you want stock 4.1.2 with root and all that you would be safe to take the ota on stock then run CASUAL. I beleive either way your reallywanting 4.1.2 unlocked so you can have custom roms and ive seen some of the roms being updated for the vramc3 base anyhow. So if want you could run casual now with 4.1.1 that you have (you just picked it up so im assuming its all stock) and flash a cust9m rom that has 4.1.2 already implimented. cheak out the rooting/custom rom guide and the jailbreak thread and decide. In the end both paths will lead to the same place.
Click to expand...
Click to collapse
Yes, it was 4.1.1 stock. I took your advice and unlocked/rooted in 4.1.1. What is the difference in having a base of vrall4 vs. vramc3? I flashed Jelly Beans and am showing 4.1.2 on vrall4. If I went to a different ROM based on vramc3,would it cause any issues? Thanks for the help and sorry for the n00b questions or if they've been answered a lot, I haven't modded Samsung in a while.
Sent from my SCH-I605 using xda premium
eakeller said:
Yes, it was 4.1.1 stock. I took your advice and unlocked/rooted in 4.1.1. What is the difference in having a base of vrall4 vs. vramc3? I flashed Jelly Beans and am showing 4.1.2 on vrall4. If I went to a different ROM based on vramc3,would it cause any issues? Thanks for the help and sorry for the n00b questions or if they've been answered a lot, I haven't modded Samsung in a while.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Jelly Beans builds 15 and 16 are on the new base, VRAMC3, which is 4.1.2.
eakeller said:
Yes, it was 4.1.1 stock. I took your advice and unlocked/rooted in 4.1.1. What is the difference in having a base of vrall4 vs. vramc3? I flashed Jelly Beans and am showing 4.1.2 on vrall4. If I went to a different ROM based on vramc3,would it cause any issues? Thanks for the help and sorry for the n00b questions or if they've been answered a lot, I haven't modded Samsung in a while.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Many sites have a change log of all the changes that vramc3 brings to the Note 2. I flashed a stock vramc3 ROM that VZW pushed OTA. The only difference is that the Jelly Beans developer (beanstown106) rooted it, replaced the secure bootloader and made it flashable. So I've basically accepted the OTA but I'm still rooted and unlocked.
larry_thagr81 said:
Many sites have a change log of all the changes that vramc3 brings to the Note 2. I flashed a stock vramc3 ROM that VZW pushed OTA. The only difference is that the Jelly Beans developer (beanstown106) rooted it, replaced the secure bootloader and made it flashable. So I've basically accepted the OTA but I'm still rooted and unlocked.
Click to expand...
Click to collapse
Here's what I did: Stock 4.1.1 VRALL4 -> Unlocked/rooted with Casual --> Flashed Jelly Beans build 16
Now in my "About Phone" setup, i have this: Android version 4.1.2; Baseband version I605VRALL4; Build number JZO54K.I605VRAMC3
The build flashed just fine and it appears I'm on VRAMC3. However the baseband remains at VRALL4, I assume because JBeans doesn't update the baseband. Is there any reason to care about the "mismatch" between the baseband and the build? Should I go through the work to update the baseband, and if so what is the best method? I've been looking around the net and have found a bunch of conflicting answers to this question, so hopefully someone can straighten things out regarding the Note 2 specifically.
Thanks for the discussion.
Baseband is the modem. Just download and flash the zip.
Sent from my Note II using Tapatalk 2
eakeller said:
Here's what I did: Stock 4.1.1 VRALL4 -> Unlocked/rooted with Casual --> Flashed Jelly Beans build 16
Now in my "About Phone" setup, i have this: Android version 4.1.2; Baseband version I605VRALL4; Build number JZO54K.I605VRAMC3
The build flashed just fine and it appears I'm on VRAMC3. However the baseband remains at VRALL4, I assume because JBeans doesn't update the baseband. Is there any reason to care about the "mismatch" between the baseband and the build? Should I go through the work to update the baseband, and if so what is the best method? I've been looking around the net and have found a bunch of conflicting answers to this question, so hopefully someone can straighten things out regarding the Note 2 specifically.
Thanks for the discussion.
Click to expand...
Click to collapse
If you look at post #2 in the beans thread, there is a link to the new radio. Flash that and you will be completely up to date.
Sent from my SCH-I605 using Tapatalk 2
randy6675 said:
If you look at post #2 in the beans thread, there is a link to the new radio. Flash that and you will be completely up to date.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Thanks guys, found Scott's zip and flashed the baseband. Everything looks to be consistent, so I'm good.
Sent via Note2 with XDA Premium
Alright so my phone isn't being detected by any computer I plug it in to, recovery, bootloader, nothing.
Rom: 4.3 CM 10.2 by Dvhexer (same issues on other roms though so I don't think it's rom specific)
Kernel: hhouston's 4.3 kernel
Baseband: ATT-JB Stock
Bootloader: MAKOZ20i (I think this might be the issue)
I had converted to nex4 a LONG LONNNGGG time ago, but flashed the ICS tot to get back (again a lonnggg time ago) then updated to JB when it came out using a tot as well. Also attempted the JB camera fix... seemed to work since everything was working on RootBox.
Any help would be appreciated!
Jakeroxs said:
Alright so my phone isn't being detected by any computer I plug it in to, recovery, bootloader, nothing.
Rom: 4.3 CM 10.2 by Dvhexer (same issues on other roms though so I don't think it's rom specific)
Kernel: hhouston's 4.3 kernel
Baseband: ATT-JB Stock
Bootloader: MAKOZ20i (I think this might be the issue)
I had converted to nex4 a LONG LONNNGGG time ago, but flashed the ICS tot to get back (again a lonnggg time ago) then updated to JB when it came out using a tot as well. Also attempted the JB camera fix... seemed to work since everything was working on RootBox.
Any help would be appreciated!
Click to expand...
Click to collapse
No idea if the bootloader is your issue or not. But houstonn has posted links to the new 4.2 and 4.3 bootloaders in his root box thread. They should both be fairly near the end of the thread. I haven't updated to the 4.3 version yet, but 4.2 is working fine for me.
Sent from my Optimus G using Tapatalk 4
dandrumheller said:
No idea if the bootloader is your issue or not. But houstonn has posted links to the new 4.2 and 4.3 bootloaders in his root box thread. They should both be fairly near the end of the thread. I haven't updated to the 4.3 version yet, but 4.2 is working fine for me.
Sent from my Optimus G using Tapatalk 4
Click to expand...
Click to collapse
It's the 4.3 bootloader that I found on his thread
Does anyone have a link for the stock ATT JB bootloader?
Jakeroxs said:
It's the 4.3 bootloader that I found on his thread
Does anyone have a link for the stock ATT JB bootloader?
Click to expand...
Click to collapse
Doh. Guess that's not the answer then.
Sent from my Optimus G using Tapatalk 4
Bump still need help :/
Sent from my Optimus G using Tapatalk 4
Stupidly I updated to jelly bean through the Asus ota a while back and have recently decided it is sluggish and terrible. I have root and a custom recovery (TWRP) but it seems flashing an ICS ROM will give me a soft brick.
This isn't urgent, I can restore back to jelly bean using my back ups. But is there anything special that needs to be done to revert back to ICS?
I have been doing what I think is kind of the usual for flashing Roms .
Full wipe
Flash ROM
Flash gapps
Sent from my SGH-I337 using xda app-developers app
From my limited experience with Tf201, I read that to avoid a brick its important to flash the correct bootloader and recovery first? Not sure which though. You can also install Nvflash for Jellybean TF201 which apparently makes the device ’unbrickable’, theres a thread on this forum how to do it. Also, before you downgrade, try the unofficial cyanogenmod 4.3 jelly bean rom. Its very smooth and fast compared to the ota official Asus official JB, which is terrible as you said.
rust991 said:
Stupidly I updated to jelly bean through the Asus ota a while back and have recently decided it is sluggish and terrible. I have root and a custom recovery (TWRP) but it seems flashing an ICS ROM will give me a soft brick.
This isn't urgent, I can restore back to jelly bean using my back ups. But is there anything special that needs to be done to revert back to ICS?
I have been doing what I think is kind of the usual for flashing Roms .
Full wipe
Flash ROM
Flash gapps
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
You cannot go back to ICS unless you have nvflash backups.
You can now create nvflash backups while you are on Jellybean tho which you couldn't do before.
I would advise trying one of the Hairybean Roms which is a big improvement over stock. If you do not want to go to the latest one you can flash Hairybean 1.51 which will flash ok on your bootloader and recovery without you changing anything.
I'm running 4.0.3 ics now but I want to be running jellybean. I followed all instructions on a few videos but cannot get the right version of cm10....any suggestions?
abrain08 said:
I'm running 4.0.3 ics now but I want to be running jellybean. I followed all instructions on a few videos but cannot get the right version of cm10....any suggestions?
Click to expand...
Click to collapse
Go here http://forum.xda-developers.com/showthread.php?t=1982728 and click on ROMS then find the jelly bean ROM you want and follow the instructions of the developer to install it, just read and you will be fine.
Sent from my SGH-T959 using Tapatalk 2
I would recommend installing the latest helly bean release. It's one of the smoothest ROMs out there and I don't get any troubles from it.
abrain08 said:
I'm running 4.0.3 ics now but I want to be running jellybean. I followed all instructions on a few videos but cannot get the right version of cm10....any suggestions?
Click to expand...
Click to collapse
Did you do a full reset to Recovery? If not - are unlikely to be able to install. I have no problems with the installation of assembly OFFICIAL CM, when I did a full reset. Try it and you!