Here are all of the radio images that are currently available for the Note 2. These are packaged for flashing in recovery (CWM/TWRP). I'm posting these here because apparently the other images are all offline or unavailable anymore. I make no promises about these working, improving signal, or doing much of anything, but they're here anyway. If you need to know how to use these, flash your phone to stock and leave it locked, I'm not here to support stupidity. Enjoy.
VRALJB Modem
VRALL4 Modem
VRAMC3 Modem
VRUEMJ9 Modem
Than you!!!!
Sent from my SCH-I605 using Tapatalk
Thanks for putting some updated links Imnuts. I try to keep them perma-saved so I don't have to worry about that problem when I need a modem lol.
Do you know if we're safe mix-matching modems and ROMs? Like could I run VRALL4 with the new 4.3 leak? I'm not liking this MJ9 on my phone atm.
Is the latest radio from today or is it from the leak?
Does this avoid us having to use ODIN to install the modem?
Anyone try the latest yet with official ota?
Sent from my SCH-I605 using xda app-developers app
Skilover said:
Does this avoid us having to use ODIN to install the modem?
Click to expand...
Click to collapse
Is this a trick question? Did you not read the op??? It says pretty clearly that it can be flashed through twrp/cwm....my goodness
Sent from my SCH-I605 using xda app-developers app
npainter7 said:
Is this a trick question? Did you not read the op??? It says pretty clearly that it can be flashed through twrp/cwm....my goodness
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
I got that part. I am so sorry, I didn't ask this correctly. What I'm trying to ask is, does this achieve everything that the ODIN package floating around does, which includes the modem and perhaps other things. I know it takes the phone back to stock as well. I have no idea why that would be necessary to install a radio. I've flashed radios before.
My goal is to be able to install one of the 4.3 TW roms that requires the MJ9 radio for wifi to work. If this achieves that goal, then flashing this file is clearly the way to go!!!
Thanks for this @imnuts !
Sent from my SCH-I605 using Tapatalk
Tried flashing j9 radio and don't seem to work on cm11 nightly
Skilover said:
I got that part. I am so sorry, I didn't ask this correctly. What I'm trying to ask is, does this achieve everything that the ODIN package floating around does, which includes the modem and perhaps other things. I know it takes the phone back to stock as well. I have no idea why that would be necessary to install a radio. I've flashed radios before.
My goal is to be able to install one of the 4.3 TW roms that requires the MJ9 radio for wifi to work. If this achieves that goal, then flashing this file is clearly the way to go!!!
Click to expand...
Click to collapse
I second this question. I am not going to bust out Odin. But if this is the same I will flash this and a new room at my leisure. I have been reading threads for thirty minutes and now I know I am not the only one that is wondering this.
Sent from my SCH-I605
JustusIV said:
I second this question. I am not going to bust out Odin. But if this is the same I will flash this and a new room at my leisure. I have been reading threads for thirty minutes and now I know I am not the only one that is wondering this.
Sent from my SCH-I605
Click to expand...
Click to collapse
Ive been on the leak for 5 days. I flashed modem in recovery with this same type of file from another thread. I had no issues. Just flashed official, this modem in recovery, and then latest devil kernel. I can confirm this works just fine instead of odin. Im wondering if the odin flashing might be causing issues for some. In 5 days i had no fcs and no reboots with leak.
Sent from my SCH-I605 using xda app-developers app
donnyp1 said:
Ive been on the leak for 5 days. I flashed modem in recovery with this same type of file from another thread. I had no issues. Just flashed official, this modem in recovery, and then latest devil kernel. I can confirm this works just fine instead of odin. Im wondering if the odin flashing might be causing issues for some. In 5 days i had no fcs and no reboots with leak.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
I flashed the official, this modem and left the default kernel. For some reason, it would flash the sammy boot screen twice, then take me right back to recovery. Do you have to use an alternate kernel?
MADDAN18 said:
I flashed the official, this modem and left the default kernel. For some reason, it would flash the sammy boot screen twice, then take me right back to recovery. Do you have to use an alternate kernel?
Click to expand...
Click to collapse
I dont know if you do or not. It runs perfect on devil with great battery just on stock settings.
Sent from my SCH-I605 using xda app-developers app
I flashed the zip, it said successful, installed new rom-and it says modem still is VRALL4.
This doesn't seem right.
Please excuse me if I'm being stupid-tough crowd here!
When I try to flash VRUEMJ9 Modem with twrp 2.3.2.3 it fails on an assert:
asser filed: getprop("ro.product.device") == "t0ltecdm
getprop("ro.product.device") == i605" ||
getprop("ro.product.device") == SCH-II605
Error in /external_sdcard/.../VRUEMJ9_.. (status 7)
(yes I verified the md5sum as 881d4b58aaf...a31b38 using MD5Checker)
I used this same setup to flash the previous radio.
(part of the message is truncated because of bad linewraps)
Skilover said:
I got that part. I am so sorry, I didn't ask this correctly. What I'm trying to ask is, does this achieve everything that the ODIN package floating around does, which includes the modem and perhaps other things. I know it takes the phone back to stock as well. I have no idea why that would be necessary to install a radio. I've flashed radios before.
My goal is to be able to install one of the 4.3 TW roms that requires the MJ9 radio for wifi to work. If this achieves that goal, then flashing this file is clearly the way to go!!!
Click to expand...
Click to collapse
I think that Odin isnt just for the radio but other parameters also. Im not sure but from what ive read thats what it sounds like. There was another zip that was supposed to work but it never did for me anyway so i had to use odin. It will be worth it to have it done right 4.3 is great i run jellywiz
Sent from my SCH-I605 using Tapatalk
jake21 said:
When I try to flash VRUEMJ9 Modem with twrp 2.3.2.3 it fails on an assert:
asser filed: getprop("ro.product.device") == "t0ltecdm
getprop("ro.product.device") == i605" ||
getprop("ro.product.device") == SCH-II605
Error in /external_sdcard/.../VRUEMJ9_.. (status 7)
(yes I verified the md5sum as 881d4b58aaf...a31b38 using MD5Checker)
I used this same setup to flash the previous radio.
(part of the message is truncated because of bad linewraps)
Click to expand...
Click to collapse
You're on a pretty old version of twrp
http://goo.im/devs/OpenRecovery/t0ltevzw//openrecovery-twrp-2.6.3.1-t0ltevzw.zip
Here's the latest....flash in recovery.
Sent from my SCH-I605 using XDA Premium HD app
Yea I know and you can also reference it via google play. My problem is I am a bit of a newbie and it was not obvious to me how to install. You might ask how I got the current version - well that was a side effect of the folks making it really easy to crack the note 2 back in Dec (2012). You just ran this script and it cracked the boot loader and installed twrp (I believe it used odin) so I never really did learn how to update twrp.
This afternoon I tried the version of google play but it wanted to isntall an 'open bootloader" and I wasn't sure why it wanted to do that since my bootloader was already cracked and all I wanted it to do is to update twrp.
=
So I guess this begs the question do I download this zip file and then use twrp 2.6.3.1 to install it like a rom ?
MADDAN18 said:
You're on a pretty old version of twrp
http://goo.im/devs/OpenRecovery/t0ltevzw//openrecovery-twrp-2.6.3.1-t0ltevzw.zip
Here's the latest....flash in recovery.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
jake21 said:
Yea I know and you can also reference it via google play. My problem is I am a bit of a newbie and it was not obvious to me how to install. You might ask how I got the current version - well that was a side effect of the folks making it really easy to crack the note 2 back in Dec (2012). You just ran this script and it cracked the boot loader and installed twrp (I believe it used odin) so I never really did learn how to update twrp.
This afternoon I tried the version of google play but it wanted to isntall an 'open bootloader" and I wasn't sure why it wanted to do that since my bootloader was already cracked and all I wanted it to do is to update twrp.
=
So I guess this begs the question do I download this zip file and then use twrp 2.6.3.1 to install it like a rom ?
Click to expand...
Click to collapse
That is correct. Simply download the zip, copy it to your sd card, boot into recovery, choose the zip and flash (just like you would a ROM. When you reboot, twrp will be updated. You can also download goo manager from the market. And choose "install custom recovery" I just find flashing the zip eliminates several steps ie software down loads etc.
Sent from my SCH-I605 using XDA Premium HD app
Related
I didn't see this posted anywhere yet, did anyone else get this update yet?
http://community.sprint.com/baw/message/442160#442160D
nm, saw it on posted somewhere else. how the heck do I delete a post anyways!??
nck4857 said:
I didn't see this posted anywhere yet, did anyone else get this update yet?
http://community.sprint.com/baw/message/442160#442160D
nm, saw it on posted somewhere else. how the heck do I delete a post anyways!??
Click to expand...
Click to collapse
For future reference, I'm pretty sure this is not considered development.
The moderators will eventually close the thread for you.
to update this kinda stuff when youre rooted with CWM, it says install failed after i tried to update.... how would i normally get updates on a rooted gs3??
Just like you would stock
Mine tried installing but cwm stopped it of course. My PRL was messed up afterwards. Kept getting error #67 so I had to restore to stock rom with Odin. All fixed now.
About to post up the rooted update.
freeza said:
About to post up the rooted update.
Click to expand...
Click to collapse
Awesome, I need to throw you some beer money
bizdady said:
Mine tried installing but cwm stopped it of course. My PRL was messed up afterwards. Kept getting error #67 so I had to restore to stock rom with Odin. All fixed now.
Click to expand...
Click to collapse
I got the same thing. Now I can't make the update re-run. Anyone know where it is stored?
LilRico said:
I got the same thing. Now I can't make the update re-run. Anyone know where it is stored?
Click to expand...
Click to collapse
Same issue, same question.
I'm guessing that since we made modification to the system ie removed system apps or whatever, that's the cause of it not working? I looked around and I couldn't find the OTA in any system folder, so I now wonder if anyone has the OTA in a flashable .zip.
LilRico said:
I'm guessing that since we made modification to the system ie removed system apps or whatever, that's the cause of it not working? I looked around and I couldn't find the OTA in any system folder, so I now wonder if anyone has the OTA in a flashable .zip.
Click to expand...
Click to collapse
It didn't work because we don't have the stock recovery installed. You'd have to flash the stock recovery back before running the update for it to work. I don't see any stock recovery .md5's posted though so I'm not sure how you'd go back to it short of a full restore.
Anyone know what this update consist of?
Sent from my SPH-L710 using xda premium
lordelfkin said:
Anyone know what this update consist of?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
A security fix, says the changelog
Sent from my SPH-D700 using XDA Premium App
How can you tell if the update took? I no longer get the notification but where can I check for the change?
I did the return to full stock using the epiccm teams method, got the update and it installed fine. Now I'm having trouble trying to boot into CWM after flashing it through odin. Just boot loops using the three finger method unless i just let it boot up normal.
CapsLockKey said:
I did the return to full stock using the epiccm teams method, got the update and it installed fine. Now I'm having trouble trying to boot into CWM after flashing it through odin. Just boot loops using the three finger method unless i just let it boot up normal.
Click to expand...
Click to collapse
"The update contains a file that will reflash the stock recovery every single time you reboot your phone if the digital signature doesn't match" is probably whats creating the bootlooping. install the root friendly update thats being uploaded atm...
edit: are you using the new v4 recovery? might want to flash that in odin if your using the old one..
Anybody know what the update is for or fixes? I got the notification but I'm not installing it since I'm rooted LOL
OneStepAhead said:
"The update contains a file that will reflash the stock recovery every single time you reboot your phone if the digital signature doesn't match" is probably whats creating the bootlooping. install the root friendly update thats being uploaded atm...
edit: are you using the new v4 recovery? might want to flash that in odin if your using the old one..
Click to expand...
Click to collapse
Yes, I got the latest one from their blog.
Edit: I posted this in another thread, but was finally able to get into CWM by just leaving auto reboot checked when flashing recovery in odin, then just holding volume up and home after the phone vibrates. No need to hold the power button.
An this is done
I've tried a million and one things with my phone. All I want is to get it out like it is fresh out of the box. I can't find a RUU that works, I downloaded a recovery ROM, now there's a *security warning* on my Bootloader so I can't even get to my recovery...please help. I just want my phone back...
ADashOfCapers said:
I've tried a million and one things with my phone. All I want is to get it out like it is fresh out of the box. I can't find a RUU that works, I downloaded a recovery ROM, now there's a *security warning* on my Bootloader so I can't even get to my recovery...please help. I just want my phone back...
Click to expand...
Click to collapse
use this guide to go back to stock
http://forum.xda-developers.com/showthread.php?p=37687025
Sent from my One S using Tapatalk 2
So my phone is working because I'm using Harmonia 3.17 ROM and the only problem is the WIFI won't come on. It just says error.
ADashOfCapers said:
So my phone is working because I'm using Harmonia 3.17 ROM and the only problem is the WIFI won't come on. It just says error.
Click to expand...
Click to collapse
That is usually a kernel issue.
I would suggest using flash image GUI, and flashing a kernel, I suggest mirage.
Both downloads are in his first post here:
http://forum.xda-developers.com/showthread.php?t=2175191
Sent from my PG86100 using xda app-developers app
I tried Flash Image and it said it wasn't compatible with my phone.
ADashOfCapers said:
I tried Flash Image and it said it wasn't compatible with my phone.
Click to expand...
Click to collapse
It works, don't know why it doesn't for you.
Other things you can try is flash boot.IMG through fastboot
Or using 4ext make sure smartflash is enabled and do a fresh install of your rom
Also you can flash some kernels through recovery
Sent from my PG86100 using xda app-developers app
I have rooted my GS4 successfully, but upon attempting to flash the ClockworkMod Recovery I have run into an issue. When I attempt to go into the recovery mode for a split second it flashes the blue legend in the top left of the screen but then immediately goes into ODIN mode and reads in red text: "could not do normal boot." No matter what I try I cannot seem to get past this issue. I have also attempted to use the loki method where you run the terminal emulator on the phone and attempt to run the program through that but it keeps reading an error message with something along the lines of "does not match build." I'm a little stuck and cannot figure out what is going wrong with any of these methods I have tried.
McSonboy said:
I have rooted my GS4 successfully, but upon attempting to flash the ClockworkMod Recovery I have run into an issue. When I attempt to go into the recovery mode for a split second it flashes the blue legend in the top left of the screen but then immediately goes into ODIN mode and reads in red text: "could not do normal boot." No matter what I try I cannot seem to get past this issue. I have also attempted to use the loki method where you run the terminal emulator on the phone and attempt to run the program through that but it keeps reading an error message with something along the lines of "does not match build." I'm a little stuck and cannot figure out what is going wrong with any of these methods I have tried.
Click to expand...
Click to collapse
What build are you on?
If you're not on MDK then you can't install a custom recovery. Your only option is Safestrap. Find your build number then research as much as possible before you brick your phone.
Sent from my NCC 1701 using Tapatalk 4
riker147 said:
What build are you on?
If you're not on MDK then you can't install a custom recovery. Your only option is Safestrap. Find your build number then research as much as possible before you brick your phone.
Sent from my NCC 1701 using Tapatalk 4
Click to expand...
Click to collapse
My build is VRUEMK2.
McSonboy said:
My build is VRUEMK2.
Click to expand...
Click to collapse
That's the newest build. No custom recovery. Your only option is Safestrap and you can only flash 4.3 TW based ROMS. Like I said earlier. Do your research.
Sent from my NCC 1701 using Tapatalk 4
riker147 said:
That's the newest build. No custom recovery. Your only option is Safestrap and you can only flash 4.3 TW based ROMS. Like I said earlier. Do your research.
Sent from my NCC 1701 using Tapatalk 4
Click to expand...
Click to collapse
Forgive my ignorance, but what do you mean by "TW based"? I did just look up how to do the flashing via Safestrap and the demo the guy did ran successfully for the Hyperdrive mod, but I am curious as to whether or not I can use this to flash the Gummy 4.4 ROM that has recently come out.
McSonboy said:
Forgive my ignorance, but what do you mean by "TW based"? I did just look up how to do the flashing via Safestrap and the demo the guy did ran successfully for the Hyperdrive mod, but I am curious as to whether or not I can use this to flash the Gummy 4.4 ROM that has recently come out.
Click to expand...
Click to collapse
TW=Touchwiz wiz. You can't flash any CM or AOSP ROMs. Only 4.3 Touchwiz based ROMS.
Sent from my NCC 1701 using Tapatalk 4
Thank you for the help. Do you know if at any time in the foreseeable future there will be the capability to flash other types of ROMs?
Sent from my SCH-I545 using Tapatalk
McSonboy said:
Thank you for the help. Do you know if at any time in the foreseeable future there will be the capability to flash other types of ROMs?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
probably not, the lockdown on the bootloader may never be cracked.
Well with safe strap, I found that you are able to flash ROMs for my build by tricking the system into running multiple slots so that it doesn't mess with the actual system files. So if it's running on a separate slot to run a ROM such as Hyperdrive then shouldn't it able to run any other kind of ROM running on the same principle of a "ghost" slot?
Sent from my SCH-I545 using Tapatalk
McSonboy said:
Well with safe strap, I found that you are able to flash ROMs for my build by tricking the system into running multiple slots so that it doesn't mess with the actual system files. So if it's running on a separate slot to run a ROM such as Hyperdrive then shouldn't it able to run any other kind of ROM running on the same principle of a "ghost" slot?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Not really sure what you mean by "tricking the system", but if you think you can run any ROM, give it a shot and let us know. It would be a major breakthrough.
Sent from my NCC 1701 using Tapatalk 4
What I mean is that the way safe strap works is by running a different port instead of modifying the way original system ROM. Picture like a computer with multiple USB ports. The new ROM is like a USB thumb drive. You plug it in to run your program (in this case the new ROM) without actually modifying the system info. It's like a virtual port so as to not modify system data. I'm not sure if there are ROMs that won't work because they are not TouchWiz based. Any thoughts?
Sent from my SCH-I545 using Tapatalk
McSonboy said:
What I mean is that the way safe strap works is by running a different port instead of modifying the way original system ROM. Picture like a computer with multiple USB ports. The new ROM is like a USB thumb drive. You plug it in to run your program (in this case the new ROM) without actually modifying the system info. It's like a virtual port so as to not modify system data. I'm not sure if there are ROMs that won't work because they are not TouchWiz based. Any thoughts?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
That's not how Safestrap works.
Safestrap basically allows the phone to boot, then just before the stock ROM begins executing start-up programs, it intervenes, mounts the ROM slot over the top of the original ROM (technically, it loopback mounts it and uses chroot() to make the mounted ROM the root file system).
Once the slot is loaded, the start-up scripts in that slot are allowed to run.
The Android Kernel that's used to run the slot is the stock kernel, so you can only run ROMs that will boot with the stock kernel.
The AOSP and CM ROMs have not been ported to the TouchWiz kernel, so they can't run on a Safestrap device.
And we can't change the kernel because the bootloader is locked and prohibits that. (Except for the MDK bootloader, which can be bypassed.)
k1mu said:
That's not how Safestrap works.
Safestrap basically allows the phone to boot, then just before the stock ROM begins executing start-up programs, it intervenes, mounts the ROM slot over the top of the original ROM (technically, it loopback mounts it and uses chroot() to make the mounted ROM the root file system).
Once the slot is loaded, the start-up scripts in that slot are allowed to run.
The Android Kernel that's used to run the slot is the stock kernel, so you can only run ROMs that will boot with the stock kernel.
The AOSP and CM ROMs have not been ported to the TouchWiz kernel, so they can't run on a Safestrap device.
And we can't change the kernel because the bootloader is locked and prohibits that. (Except for the MDK bootloader, which can be bypassed.)
Click to expand...
Click to collapse
Okay, thank you for the clarification. Well that stinks. And as of right now no one has figured out how to unlock to bootloader for this build?
McSonboy said:
Okay, thank you for the clarification. Well that stinks. And as of right now no one has figured out how to unlock to bootloader for this build?
Click to expand...
Click to collapse
If someone had figured it out, it would be posted all over this site. Based on everything I've read, the future is not looking to bright.
Sent from my NCC 1701 using Tapatalk 4
riker147 said:
If someone had figured it out, it would be posted all over this site. Based on everything I've read, the future is not looking to bright.
Sent from my NCC 1701 using Tapatalk 4
Click to expand...
Click to collapse
Well ****...
Please help!!
My Gt-i9505 is stuck in odin mode "could not do normal boot" .. i turned it off took battery out and waiting 10 to mins and retried
I had cm11 installed and i am only new to this custom rom business and tried installing a nightly update but kept getting status 7 error .... eventaully fixed that and got status 6 error instead .
I got so fed up i just wanted to completely restart get rid of cm11 and install the stock rom which i have downloaded on my pc
I havnt rooted the device .I just need help to get out of this odin mode 'downloading do not turn off target !!' im so annoyed with it!
Remember im only new at all this
Any help is much appreciated :good:
irishboy1234 said:
My Gt-i9505 is stuck in odin mode "could not do normal boot" .. i turned it off took battery out and waiting 10 to mins and retried
I had cm11 installed and i am only new to this custom rom business and tried installing a nightly update but kept getting status 7 error .... eventaully fixed that and got status 6 error instead .
I got so fed up i just wanted to completely restart get rid of cm11 and install the stock rom which i have downloaded on my pc
I havnt rooted the device .I just need help to get out of this odin mode 'downloading do not turn off target !!' im so annoyed with it!
Remember im only new at all this
Any help is much appreciated :good:
Click to expand...
Click to collapse
Well you're in the Verizon i545 forum not the i9505 but that's OK !
Id suggest re down loading your proper Odin file... Do you know what build your phone was on? although it doesn't matter much for you since your phones bootloader isn't locked... Just good practice to know.
If you're still having issues with Odin I'd say update your USB drivers on your computer and possibly trying another USB cable.
After you get through Odin you can just use Chainfire to root your phone.. I can link you to it if you need..
Then you can Odin an updated recovery on your phone which by the way.... Would have taken care of those recovery errors you were getting.
Your phone is quite easy to deal with. You'll do all these things through Odin.
Sent from my SCH-I545 using Tapatalk
McSonboy said:
Well ****...
Click to expand...
Click to collapse
basic research would tell you the prospects of finding an exploit to unlock the S4 locked bootloader is extremely unlikely...
---------- Post added at 06:32 AM ---------- Previous post was at 06:31 AM ----------
irishboy1234 said:
My Gt-i9505 is stuck in odin mode "could not do normal boot" .. i turned it off took battery out and waiting 10 to mins and retried
I had cm11 installed and i am only new to this custom rom business and tried installing a nightly update but kept getting status 7 error .... eventaully fixed that and got status 6 error instead .
I got so fed up i just wanted to completely restart get rid of cm11 and install the stock rom which i have downloaded on my pc
I havnt rooted the device .I just need help to get out of this odin mode 'downloading do not turn off target !!' im so annoyed with it!
Remember im only new at all this
Any help is much appreciated :good:
Click to expand...
Click to collapse
really in the wrong forum for your phone....
Mistertac said:
Well you're in the Verizon i545 forum not the i9505 but that's OK !
Id suggest re down loading your proper Odin file... Do you know what build your phone was on? although it doesn't matter much for you since your phones bootloader isn't locked... Just good practice to know.
If you're still having issues with Odin I'd say update your USB drivers on your computer and possibly trying another USB cable.
After you get through Odin you can just use Chainfire to root your phone.. I can link you to it if you need..
Then you can Odin an updated recovery on your phone which by the way.... Would have taken care of those recovery errors you were getting.
Your phone is quite easy to deal with. You'll do all these things through Odin.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
so far so good proper odin installed and it shows up in a yellow box o:[COM5]
now what?
irishboy1234 said:
so far so good proper odin installed and it shows up in a yellow box o:[COM5]
now what?
Click to expand...
Click to collapse
OK. Now you put that Odin tar file into the PDA/AP slot . make sure repartition is NOT checked out and once that file loads into Odin you should be good to hit start.
There are walk thrust and YouTube videos on how to do this. Maybe you should Google it so you don't make any mistakes that could screw up your phone
Sent from my SCH-I545 using Tapatalk
---------- Post added at 07:50 AM ---------- Previous post was at 07:40 AM ----------
irishboy1234 said:
so far so good proper odin installed and it shows up in a yellow box o:[COM5]
now what?
Click to expand...
Click to collapse
Here.... Check this out too
http://forum.xda-developers.com/showthread.php?p=41072377
Sent from my SCH-I545 using Tapatalk
Ok, been away from the note 2 for a min. Anyone want to give me the low down on all this 4.3 stuff? I'm seeing roms say that MJ9 has to be flashed in Odin before a the rom can be flashed? Is this a one time deal or does it have to be done every time I want to flash a tw rom? Do I have to do anything to go back to an aosp rom? I'm sure I could figure all this out on my own but I'm impatient. Lol. TIA
Sent from my SCH-I605 using Tapatalk
KBizzle said:
Ok, been away from the note 2 for a min. Anyone want to give me the low down on all this 4.3 stuff? I'm seeing roms say that MJ9 has to be flashed in Odin before a the rom can be flashed? Is this a one time deal or does it have to be done every time I want to flash a tw rom? Do I have to do anything to go back to an aosp rom? I'm sure I could figure all this out on my own but I'm impatient. Lol. TIA
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
You have to flash MJ9 firmware that has the tz, params and modem in it.. This allows wifi to work.. then flash away! Just do not flash MJ9 official OS KIES bc you'll lock your bootloader..
Once your done flashing the firmware you can flash in between roms no problem doesn't matter what version,4.1.2, 4.3 or aosp 4.4.2:good:
Edit: here's the thread http://forum.xda-developers.com/showthread.php?t=2578458
lacoursiere18 said:
You have to flash MJ9 firmware that has the tz, params and modem in it.. This allows wifi to work.. then flash away! Just do not flash MJ9 official OS KIES bc you'll lock your bootloader..
Once your done flashing the firmware you can flash in between roms no problem doesn't matter what version,4.1.2, 4.3 or aosp 4.4.2:good:
Edit: here's the thread http://forum.xda-developers.com/showthread.php?t=2578458
Click to expand...
Click to collapse
Thank you. It's been a while.
Sent from my SCH-I605 using Tapatalk
Alright, got one more question. So I thought I had bricked my phone last night. Accidentally flashed an S4 stock rom. I know, dumb. Anyway, after 3 hours of trying to Odin multiple stock roms, I finally got one to take and the phone booted. So I immediately went and used casual to root the device. Everything went fine there. I went ahead and updated TWRP to the latest and proceeded to flash aokp. It locked up at the boot animation. So I then tried to flash a 4.1.2 tw rom. This is where it got weird. It flashed fine but then it never booted. Just a black screen after the Samsung splash screen. I then decided to try and Odin a rooted 4.1.3 rom. Still nothing. So last ditch effort I odin'd the pit file. Back in business on an unrooted tw rom. Now when I try to use casual, it won't download the proper driver to root again. Gives a perpetual error and requests the driver be installed over and over until I pull the USB cable. Is there something I'm missing?
Sent from my SCH-I605 using Tapatalk
Try this. With the phone booted, go into device manager on your computer and uninstall the driver. Then boot the phone into download mode and uninstall the driver for it in device manager. Boot phone back up and try casual again. Also make sure your Antivirus is off before you run casual.
Sent from my SCH-I605 using XDA Premium 4 mobile app
I have followed all instructions for flashing carefully. I have tried going back to TWRP 2.7.0.0b I have tried putting ROM zip on internal and external storage. I have rebooted recovery after wiping also tried without wiping. Tried to flash: Beanstalk, Paranoid, Carbon, PAC. All for new partition layout. I am S-off with firewater hboot 2.10.5555. The only ROM that has flashed successfully is Omni. I keep getting this error:
See picture.
Any help or info would be much appreciated.
Sent from my Nexus 5 using XDA Premium 4 mobile app
After wiping did you reboot to recovery before trying to flash again?
HTC Jewel
HBOOT 2.10 S-OFF (rumrunner)
Android 4.3 Sense 5.5 V3
Yes.
Sent from my Nexus 5 using XDA Premium 4 mobile app
I think the ROM you want to flash doesn't seems for your device. Contact the rom developer it looks like the developer doesn't get the assert file correctly.
Try the toggle signature verification option in recovery before installing the rom. Check that the rom is for your device or not. The recovery prevent the user to install any incorrect ROM as it can hard brick your device. So make sure that ROM is for your device or not.
Sent from unnamed ROM using xda premium app
naveen6252 said:
I think the ROM you want to flash doesn't seems for your device. Contact the rom developer it looks like the developer doesn't get the assert file correctly.
Try the toggle signature verification option in recovery before installing the rom. Check that the rom is for your device or not. The recovery prevent the user to install any incorrect ROM as it can hard brick your device. So make sure that ROM is for your device or not.
Sent from unnamed ROM using xda premium app
Click to expand...
Click to collapse
Thanks but I am sure I'm flashing the right ROM for my device. This just started happening recently. I just flashed the newest Omni just posted and that flashes too. Superuser flashes as well as gapps. I thought this might have been related to updating my TWRP to 2.7.0.4b which is why I flashed back to 2.7.0.0b and I got the same errors. Backups restore with out issue as well.
Sent from my EVO using XDA Premium 4 mobile app
Could this possibly be an issue with the firewater hboot?
EVOlved human
Evolution_Freak said:
Could this possibly be an issue with the firewater hboot?
EVOlved human
Click to expand...
Click to collapse
Don't see that being an issue, unless you're on the older partition setup, which it seems you aren't. Have you tried an older version of TWRP that's built for the updated partition setup?
After looking at your picture of the failed flash, it appears that the issue is with the updater script. You can extract all the files and edit the updater script, then zip everything back up. You might also disable signature checking in TWRP if it's enabled. I've run across the same issue using CWM Touch and I usually either revert to TWRP or edit the updater script.
Sent from my EVO LTE
FinZ28 said:
Don't see that being an issue, unless you're on the older partition setup, which it seems you aren't. Have you tried an older version of TWRP that's built for the updated partition setup?
After looking at your picture of the failed flash, it appears that the issue is with the updater script. You can extract all the files and edit the updater script, then zip everything back up. You might also disable signature checking in TWRP if it's enabled. I've run across the same issue using CWM Touch and I usually either revert to TWRP or edit the updater script.
Sent from my EVO LTE
Click to expand...
Click to collapse
Thanks Fin! I will check on the signature checking. I did try going back to 2.7.0.0b but didn't try any older versions. As I said, this just started happening and is only with some ROMs.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Just checked and signature checking was disabled already. I will try your other recommendations next.
EVOlved human
Are those roms that were on your device from before? Or are they all new downloads?
I really suggest rolling ball to TWRP 2.6.3, and see if you have better luck. I have had zero issues, and I have no reason to update TWRP until there's a new feature that I will actually want/need.
aarsyl said:
Are those roms that were on your device from before? Or are they all new downloads?
I really suggest rolling ball to TWRP 2.6.3, and see if you have better luck. I have had zero issues, and I have no reason to update TWRP until there's a new feature that I will actually want/need.
Click to expand...
Click to collapse
New downloads.
EVOlved human
And you are sure that you are downloading the correct files? Maybe it's just me, but it took me a while to find the correct version of numel's PAC rom.
aarsyl said:
And you are sure that you are downloading the correct files? Maybe it's just me, but it took me a while to find the correct version of numel's PAC rom.
Click to expand...
Click to collapse
Yes, I'm sure. I just reverted back to TWRP 2.6.3.1b and I'm downloading Paranoid at the moment. Will update if it flashes.
Sent from my EVO using XDA Premium 4 mobile app
I'll be waiting for your response.
aarsyl said:
I'll be waiting for your response.
Click to expand...
Click to collapse
Negative. Failed with the same error. From what I can determine, the updater script is looking for HBOOT 2.10.0000 and I have firewater 2.10.5555. I'm pretty sure this is why some ROMs are failing and others are not. I've got to learn how to edit the updater script as I've never done that before.
Sent from my EVO using XDA Premium 4 mobile app
Evolution_Freak said:
Negative. Failed with the same error. From what I can determine, the updater script is looking for HBOOT 2.10.0000 and I have firewater 2.10.5555. I'm pretty sure this is why some ROMs are failing and others are not. I've got to learn how to edit the updater script as I've never done that before.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can't the script be updating in simple notepad? There is a lot of English in the updater-script file. Not entirely sure what you'll have to do, but I will surely check for you.
Update:
I re-ran the RUU to bring my HBOOT back to 2.10.0000. I remained unlocked and S-off as is well known. I installed twrp 2.7.0.0b via bootloader and I'm now about to try flashing again. Will update again after trying.
Sent from my EVO using XDA Premium 4 mobile app
aarsyl said:
Can't the script be updating in simple notepad? There is a lot of English in the updater-script file. Not entirely sure what you'll have to do, but I will surely check for you.
Click to expand...
Click to collapse
I always edit it with Root Explorer on my phone. You just have to edit out the lines dealing with the bootloader & device name. Fairly simple. It takes longer to extract the files and zip everything back up once you're done:thumbup:
Sent from my EVO LTE
FinZ28 said:
I always edit it with Root Explorer on my phone. You just have to edit out the lines dealing with the bootloader & device name. Fairly simple. It takes longer to extract the files and zip everything back up once you're done:thumbup:
Sent from my EVO LTE
Click to expand...
Click to collapse
That's what I figured, but I'm at work, so my assistance is limited.
aarsyl said:
That's what I figured, but I'm at work, so my assistance is limited.
Click to expand...
Click to collapse
No worries. The biggest thing is to make sure you don't flash the wrong ROM on the wrong device when you edit out those parts of the updater script. Could spell trouble
Sent from my EVO LTE