Develop Bugs

Custom ROM infinite first boot

Firstly: I'm a total n00b for this. I have flashed custom ROMs before, but not for Nexus, so this is my first attempt, so far failing spectacularly.
That said, I'd appreciate advice on both what I did wrong and how to un-brick my phone.
I searched and my problem seems strictly linked to bad flashing, but all solutions are phone specific and I haven't found a thread for Galaxy nexus, so here goes:
I chose this firmware for my flash. I also used the toolkit from stickied post above.
I unlocked the bootloader and then ran (not installed) the CWM tools. Using them I flashed the image directly. The phone was not rooted though I later ran the rooting procedure and it finished without reporting any particular errors. Android naturally never booted during this procedure.
Anyway, my phone now stays in boot animation indefinitely. Recovery mode with fastboot works, but no android joy.
Help greatly appreciated.

More info is needed you didn't mention toro, toro plus, maguro. Ask you need to do is bout into bootloader and fastboot your images back to stick look in your models thread on how to do that so you can get the correct ones.
Sent from my Galaxy Nexus using xda premium

Sorry for panicking too soon. Phone unbricked. Would still appreciate info on what I did wrong to brick it in the first place.

Beamer9408 said:
More info is needed you didn't mention toro, toro plus, maguro. Ask you need to do is bout into bootloader and fastboot your images back to stick look in your models thread on how to do that so you can get the correct ones.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hm, I've been reading on toolkit and roms for a couple of days now and I still can't really say what toro or maguro is. In what way would they be important for my troubles?

velis74 said:
Hm, I've been reading on toolkit and roms for a couple of days now and I still can't really say what toro or maguro is. In what way would they be important for my troubles?
Click to expand...
Click to collapse
It's very important to know what type of google nexus you have. Majority of custom ROMs are only compatible to certain type of GNex. Maguro is for GSM GNex while TORO is for CDM/LTE GNex. Check the link below for more info:
https://groups.google.com/forum/#!msg/android-building/qzSxFEqWvNg/qanfxMkzXHMJ
One more thing, aside from Maguro and Toro, you still need to know what build or version of GNex you have (yakju or takju). This can also be considered when flashing new custom ROMs. I know majority (or all) of the ROMs works well with either yakju or takju, there is still a slight possibility that you will encounter an issue with the version. Check out the links below for more info regarding yakju and takju:
http://forum.xda-developers.com/showthread.php?t=1778543
http://forum.xda-developers.com/showthread.php?t=1617685

Oh, in that case, I have a GSM version, Maguro it would seem.
The ROM I downloaded doesn't specifically say, but the same developer posted another ROM for which he confirmed GSM compatibility.
So can I myself find out what ROM this is since I can't ask the question in the development thread (I don't have 10 posts yet)?

did you clear all the caches via custom recovery? Although I haven't hit issues with my nexus while flashing, past devices, a factory reset sorts the bootloop most often (unless it was a bad flash). Just note that factory resetting the nexus gets rid of ALL of your data since there isn't an external SD to house your files and keep them protected from a wipe.
I would recommend you making a nandroid backup now that you're up and running again btw
Just my 2 cents

Kohawk09 said:
did you clear all the caches via custom recovery? Although I haven't hit issues with my nexus while flashing, past devices, a factory reset sorts the bootloop most often (unless it was a bad flash). Just note that factory resetting the nexus gets rid of ALL of your data since there isn't an external SD to house your files and keep them protected from a wipe.
I would recommend you making a nandroid backup now that you're up and running again btw
Just my 2 cents
Click to expand...
Click to collapse
Yes, I cleared everything I found in main menu and advanced menu of CWM.
Do I *NEED TO* root my phone in order to install a custom ROM? I would think not, but one can't be sure. That's why I only unlocked bootloader before flashing.
Edit: Yes, I found about the factory reset the hard way. Executed full wipe, then tried to flash...

velis74 said:
Yes, I cleared everything I found in main menu and advanced menu of CWM.
Do I *NEED TO* root my phone in order to install a custom ROM? I would think not, but one can't be sure. That's why I only unlocked bootloader before flashing.
Click to expand...
Click to collapse
I would think you should have rooted... my logic is that you're flashing a zip, so you're making changes to /system, which requires root. I'm not technical enough to say whether or not installing a zip can work around not having root access, but I would think not. If you were flashing system images, I would think you could get by without rooting, but not for just a zip file.
Have you taken a look at the toolkit? Soon as I got my nexus I did the one click to unlock, root, install CWM. Took less than 10 min. I already knew fastboot commands, so no reason for me to do it manually if I can get it done automatically.

Kohawk09 said:
I would think you should have rooted... my logic is that you're flashing a zip, so you're making changes to /system, which requires root. I'm not technical enough to say whether or not installing a zip can work around not having root access, but I would think not. If you were flashing system images, I would think you could get by without rooting, but not for just a zip file.
Have you taken a look at the toolkit? Soon as I got my nexus I did the one click to unlock, root, install CWM. Took less than 10 min. I already knew fastboot commands, so no reason for me to do it manually if I can get it done automatically.
Click to expand...
Click to collapse
no to toolkits... just no...
you do not need root to flash custom roms, only an unlocked bootloader and CWM or TWRP for your recovery.

Zepius said:
no to toolkits... just no...
you do not need root to flash custom roms, only an unlocked bootloader and CWM or TWRP for your recovery.
Click to expand...
Click to collapse
Why all the hate for the toolkit? Probably the only confusing thing to me since moving to the nexus is why so many seem to be against its use... I think its a great and helpful tool.

Kohawk09 said:
Why all the hate for the toolkit? Probably the only confusing thing to me since moving to the nexus is why so many seem to be against its use... I think its a great and helpful tool.
Click to expand...
Click to collapse
go look at Q&A
everyday there are at least 5-10 threads saying "HELP I BRICKED MY NEXUS... i used this toolkit but i have no idea what happened to my phone"
if someone is too lazy to type in these 2 commands and then flash su.zip to their phone, they dont need to be dinking with custom ROMs
Code:
fastboot oem unlock
fastboot flash recovery nameofclockworkortwrp.img
nexus phones are some of the easiest phones to unlock and root. there is no real need for a toolkit.

I'm currently making another attempt, but this time I'm rooting the phone and trying an image that is confirmed GSM.

Zepius said:
go look at Q&A
everyday there are at least 5-10 threads saying "HELP I BRICKED MY NEXUS... i used this toolkit but i have no idea what happened to my phone"
if someone is too lazy to type in these 2 commands and then flash su.zip to their phone, they dont need to be dinking with custom ROMs
Code:
fastboot oem unlock
fastboot flash recovery nameofclockworkortwrp.img
nexus phones are some of the easiest phones to unlock and root. there is no real need for a toolkit.
Click to expand...
Click to collapse
makes sense.... agree its probably more of a hinder than a help for those without basic fastboot knowledge. Especially since that knowledge is needed for getting out of a bind many times. Was just curious why I see some much negativity towards it...I still think its a useful tool to save time, at least from my perspective, if you already have that background. The files are all downloaded together and it was more of a convenience thing for me at least. The driver piece is probably the most helpful, since they can be a real PITA if there are leftovers from previous devices...

Just thought I pop my head in and say you were bootlooped. Not bricked. Not even soft bricked as that would constitute you had no recovery, which you did have. Just getting you clear on the lingo we use here.
Sent From My Toro+ via SkyBlue Tapatalk

Seems I chose a bad ROM after all. Flashing to CdTDroid's other ROM worked immediately.
Well, almost: after flash it would continuously report "system UI stopped working" or some such. I had to perform another factory reset before it actually worked as it should.
Now to go test if my issues with this phone are finally over or not.

velis74 said:
Seems I chose a bad ROM after all. Flashing to CdTDroid's other ROM worked immediately.
Well, almost: after flash it would continuously report "system UI stopped working" or some such. I had to perform another factory reset before it actually worked as it should.
Now to go test if my issues with this phone are finally over or not.
Click to expand...
Click to collapse
before you install a rom, always wipe data/cache.

That's the problem: I thought I did. Anyway, it's working now. Will have another go at CM later. Since I'm on custom ROM I might as well go all the way
Sent from my Galaxy Nexus using xda app-developers app

velis74 said:
I'm currently making another attempt, but this time I'm rooting the phone and trying an image that is confirmed GSM.
Click to expand...
Click to collapse
You don't need to root, as flashing the ROM will wipe the root. Most ROMs come with root access already, so people don't notice when they flash.

Yeah, figured as much + stopped doing all the unnecessary crap. Turns out flashing takes few steps but I dare not be as careless to say it's easy.
I have now successfully flashed the CM10 ROM by CdTDroiD straight from stock 4.0.4.
Turns out I misinterpreted "wipe data/factory reset" in CWM. It doesn't clear the filesystem (/sdcard) as I thought. Seems I managed to delete my files some other way during the first flashing attempt. Not clearing data was the cause of bootloop as Über reminds me it's called.
I did all that plus kept the original ICS animation which I like better than JB one. I'm really happy thus far having used it for a couple of hours.

My phone sometimes crashes, how can I rule out a software issue?

Hello everyone,
First of all my problem. Since about 2 weeks I started getting random crashes. The phone is unresponsive and the screen goes from really bright to a greenish/grey color (hard to explain). I googled but I didn't find an answer. If anyone here knows the problem that'd be great but I doubt it since there are so many this that could cause this. So now my question is, how can I be certain it's not an software issue? Further info: My phone is rooted, and I didn't change the ROM. However, I don't actually have root permissions and when I open SuperSU it asks me to update the binary which always fails. I tried to Root it again with the Galaxy Toolkit and it says it's already rooted. Also, Under the google logo is a unlocked lock sign.
Thanks

I would recommend you to try some custom stable ROM, based on 4.1.2. CM, AOKP are among top ones.
better make a backup using recovery, and flash a new ROM. It will give you a fresh start with SU too.
If you dont like using a custom ROM, restore an earlier backup if you already have..
marcusabu said:
Hello everyone,
First of all my problem. Since about 2 weeks I started getting random crashes. The phone is unresponsive and the screen goes from really bright to a greenish/grey color (hard to explain). I googled but I didn't find an answer. If anyone here knows the problem that'd be great but I doubt it since there are so many this that could cause this. So now my question is, how can I be certain it's not an software issue? Further info: My phone is rooted, and I didn't change the ROM. However, I don't actually have root permissions and when I open SuperSU it asks me to update the binary which always fails. I tried to Root it again with the Galaxy Toolkit and it says it's already rooted. Also, Under the google logo is a unlocked lock sign.
Thanks
Click to expand...
Click to collapse

ahsanali.pk said:
I would recommend you to try some custom stable ROM, based on 4.1.2. CM, AOKP are among top ones.
better make a backup using recovery, and flash a new ROM. It will give you a fresh start with SU too.
If you dont like using a custom ROM, restore an earlier backup if you already have..
Click to expand...
Click to collapse
My only expercience with custom roms got me into a boot loop, so I don't prefere that. I actually want a "out-of-the-box" phone without any modifications. Therefore I tried a factory reset but that keeps the root and unlock.

marcusabu said:
My only expercience with custom roms got me into a boot loop, so I don't prefere that. I actually want a "out-of-the-box" phone without any modifications. Therefore I tried a factory reset but that keeps the root and unlock.
Click to expand...
Click to collapse
ok, if you want to get the total old look, relock the bootloader, and install official GNex image that comes straight from Google. Hope this sorts the issue out.
Yes, Custom ROMs are a bit time taking to setup in the start, but thats the whole point - a lot of options. I flashed alot of ROMs and luckily, I have had no boot issue still. I think following the proper instructions(which are simply wiping and formatting data, cache, and dalvik) are easily gonna keep the boot loops away.

You can rule out a sw issue by starting fresh.
http://forum.xda-developers.com/showthread.php?t=1626895
Sent from my i9250

[Q] Problem after trying to root Arc S

Hello,
First of all, I did try to look for other topics about this issue. However, working through sometimes a couple of hundred pages in a thread and to sift through all the topics here could mean I missed something. If so, I'm sorry, feel free to point me to a fix, and then I'll try that.
So here's my problem,. While trying to root my SE Arc S I seem to have put it in some kind of situation I can't fix: I'm now stuck at running stock ICS 4.04 (4.1.B.0.431), lost my root (and looks like i also lost CWM recovery), can't flash anything and can't root the phone again.
So, would anoyone know how to fix this? Please, keep any instructions as easy and clear as possible. As you'll probably see in the rest of my post i'm pretty new/noob at this stuf.
Here are the things I did to get to this point (before all this I started out with ICS 4.04 build 4.1.B.0.587)
- First I unlocked my bootloader, that seemed to work. I followed the steps on the sony instruction page
- Second, I rooted the phone, by following a combination of the steps in this thread: http://forum.xda-developers.com/showthread.php?t=1683957 and on another non xda page (the steps seemed similar, but the non xda page was a little clearer/easier/more noob friendly for me.) That also worked, since I could use Titanium Backup (can't now)
- Third, I installed CWM with RecoverX. That worked, since I could enter CWM.
- Fourth, I tried installing different ROM's (cyanogenmod) by storing it on my sd card and installing it via CWM. That's where the problems started.
First of all I couldn't install any of the ROM's i tried. CWM would start installing it and then gave a status 7 error and aborted the installation. After trying the same process a couple of times my phone got stuck on the Sony screen after rebooting.
To fix this i flashed a stock android thingy (not sure if it's a rom, kernel, or whatever, anyway it's the version i'm running now) That worked and my phone at least functioned again.
However, since I don't wanna run this version I looked for ways to flash/install a different one. That's when I noticed I lost my root (an app i dl'ed that needs superuser privilleges didn't work) I tried rooting the phone again, but found I couldn't even flash anything. If i tried that, flashtool would give an error about not recognising the phone and stopped the flashing process. Then i tried to unlock the bootloader again, to see if that might work. But that didn't work either cause again my pc didn't seem to recognise the phone. I also tried using the doomlord root app. That seemed to work, but somehow after finishing it i didn't end up with root priviliges (again, I checked this by trying to use a root required app)
So, now I can't unlock the bootloader, I can't flash anything and I can't root my phone. All I can do is use it. And thought that's obviously the most important thing, I would like to be able to do more with it.
So, does anyone know how to fix this? It all seems to boil down to my phone not getting recognised while in fastboot/flash mode. But I wouldn't know how to fix that...
A lot of thanks in advance for any help!

ilporro said:
Hello,
First of all, I did try to look for other topics about this issue. However, working through sometimes a couple of hundred pages in a thread and to sift through all the topics here could mean I missed something. If so, I'm sorry, feel free to point me to a fix, and then I'll try that.
So here's my problem,. While trying to root my SE Arc S I seem to have put it in some kind of situation I can't fix: I'm now stuck at running stock ICS 4.04 (4.1.B.0.431), lost my root (and looks like i also lost CWM recovery), can't flash anything and can't root the phone again.
So, would anoyone know how to fix this? Please, keep any instructions as easy and clear as possible. As you'll probably see in the rest of my post i'm pretty new/noob at this stuf.
Here are the things I did to get to this point (before all this I started out with ICS 4.04 build 4.1.B.0.587)
- First I unlocked my bootloader, that seemed to work. I followed the steps on the sony instruction page
- Second, I rooted the phone, by following a combination of the steps in this thread: http://forum.xda-developers.com/showthread.php?t=1683957 and on another non xda page (the steps seemed similar, but the non xda page was a little clearer/easier/more noob friendly for me.) That also worked, since I could use Titanium Backup (can't now)
- Third, I installed CWM with RecoverX. That worked, since I could enter CWM.
- Fourth, I tried installing different ROM's (cyanogenmod) by storing it on my sd card and installing it via CWM. That's where the problems started.
First of all I couldn't install any of the ROM's i tried. CWM would start installing it and then gave a status 7 error and aborted the installation. After trying the same process a couple of times my phone got stuck on the Sony screen after rebooting.
To fix this i flashed a stock android thingy (not sure if it's a rom, kernel, or whatever, anyway it's the version i'm running now) That worked and my phone at least functioned again.
However, since I don't wanna run this version I looked for ways to flash/install a different one. That's when I noticed I lost my root (an app i dl'ed that needs superuser privilleges didn't work) I tried rooting the phone again, but found I couldn't even flash anything. If i tried that, flashtool would give an error about not recognising the phone and stopped the flashing process. Then i tried to unlock the bootloader again, to see if that might work. But that didn't work either cause again my pc didn't seem to recognise the phone. I also tried using the doomlord root app. That seemed to work, but somehow after finishing it i didn't end up with root priviliges (again, I checked this by trying to use a root required app)
So, now I can't unlock the bootloader, I can't flash anything and I can't root my phone. All I can do is use it. And thought that's obviously the most important thing, I would like to be able to do more with it.
So, does anyone know how to fix this? It all seems to boil down to my phone not getting recognised while in fastboot/flash mode. But I wouldn't know how to fix that...
A lot of thanks in advance for any help!
Click to expand...
Click to collapse
I had the same problem. First of all if you have bootloader unlocked it is still unlocked even if you had flashed another rom.
What rom did you exactly flashed? What OS do you use on your computer? When I started to flash different stock roms and then to root them then I unlocked my bootloader then the same problem appeared on Windows 8 (I could find no way to make my phone recognisable - don't know why). I tried to flash rom again on another one running on Winows 7 and after instaling drivers from flashtools and instaling sony companion phone started to be recognized.
So try to connect your phone to another Pc (if possible) and then flash any stock rom (for example ICS 4.04 build 4.1.B.0.587) and then (if you have unlocked you bootloader) flash any pre-rooted kernel (http://forum.xda-developers.com/showthread.php?t=2159411).

ilporro said:
Hello,
First of all, I did try to look for other topics about this issue. However, working through sometimes a couple of hundred pages in a thread and to sift through all the topics here could mean I missed something. If so, I'm sorry, feel free to point me to a fix, and then I'll try that.
So here's my problem,. While trying to root my SE Arc S I seem to have put it in some kind of situation I can't fix: I'm now stuck at running stock ICS 4.04 (4.1.B.0.431), lost my root (and looks like i also lost CWM recovery), can't flash anything and can't root the phone again.
So, would anoyone know how to fix this? Please, keep any instructions as easy and clear as possible. As you'll probably see in the rest of my post i'm pretty new/noob at this stuf.
Here are the things I did to get to this point (before all this I started out with ICS 4.04 build 4.1.B.0.587)
- First I unlocked my bootloader, that seemed to work. I followed the steps on the sony instruction page
- Second, I rooted the phone, by following a combination of the steps in this thread: http://forum.xda-developers.com/showthread.php?t=1683957 and on another non xda page (the steps seemed similar, but the non xda page was a little clearer/easier/more noob friendly for me.) That also worked, since I could use Titanium Backup (can't now)
- Third, I installed CWM with RecoverX. That worked, since I could enter CWM.
- Fourth, I tried installing different ROM's (cyanogenmod) by storing it on my sd card and installing it via CWM. That's where the problems started.
First of all I couldn't install any of the ROM's i tried. CWM would start installing it and then gave a status 7 error and aborted the installation. After trying the same process a couple of times my phone got stuck on the Sony screen after rebooting.
To fix this i flashed a stock android thingy (not sure if it's a rom, kernel, or whatever, anyway it's the version i'm running now) That worked and my phone at least functioned again.
However, since I don't wanna run this version I looked for ways to flash/install a different one. That's when I noticed I lost my root (an app i dl'ed that needs superuser privilleges didn't work) I tried rooting the phone again, but found I couldn't even flash anything. If i tried that, flashtool would give an error about not recognising the phone and stopped the flashing process. Then i tried to unlock the bootloader again, to see if that might work. But that didn't work either cause again my pc didn't seem to recognise the phone. I also tried using the doomlord root app. That seemed to work, but somehow after finishing it i didn't end up with root priviliges (again, I checked this by trying to use a root required app)
So, now I can't unlock the bootloader, I can't flash anything and I can't root my phone. All I can do is use it. And thought that's obviously the most important thing, I would like to be able to do more with it.
So, does anyone know how to fix this? It all seems to boil down to my phone not getting recognised while in fastboot/flash mode. But I wouldn't know how to fix that...
A lot of thanks in advance for any help!
Click to expand...
Click to collapse
1. Why did you use XParts? Unlocked bootloader means you can flash a stock kernel with CWM in it.
2. CM ROMs use different kernel, that's why you get status 7. Maybe you can Google a bit on CWM status 7 error? To install Cyanogen ROM, use the included kernel or look for a list of recommended kernels.
3. Flashtool should still work. Can you enter flashboot? Connect your cable to the PC, hold down the back button and connect your cable to it. A blue light means it's successfully connected in flash mode.
僕のLT18iから送られてきた

Thanks both for the different bits of advice. I dunno how, but it finally works now! In the end I installed sony's pc companion, switched off antivirus and then all of a sudden i could flash things again. Then i just followed the steps to rooting the phone for the second time, and it finally worked. Got my root back and also managed to install a ROM from CWM.
Again, not sure how, maybe i should have just turned off my antivirus from the start, or maybe in retrying all the steps I somehow stumbled across the sollution, but at least it works now
popthosegaskets said:
1. Why did you use XParts? Unlocked bootloader means you can flash a stock kernel with CWM in it.
2. CM ROMs use different kernel, that's why you get status 7. Maybe you can Google a bit on CWM status 7 error? To install Cyanogen ROM, use the included kernel or look for a list of recommended kernels.
3. Flashtool should still work. Can you enter flashboot? Connect your cable to the PC, hold down the back button and connect your cable to it. A blue light means it's successfully connected in flash mode.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
What is XParts? I don't think i used that program. The steps i previously followed might have been redundant in part, but I wanted to be on the safe side and just try all options i could find.
I tried googling for the CWM status 7 error, but couldn't really find any sollution i could work with. And anyway, it's fixed now (i hope, didn't try CM again though)
Flashtool didn't work yesterday. Or at least, it did work but i just couldn't flash anything cause it didn't recognise my phone.
Anyway, thanks again. This is fixed now

ilporro said:
Hello,
First of all, I did try to look for other topics about this issue. However, working through sometimes a couple of hundred pages in a thread and to sift through all the topics here could mean I missed something.
Click to expand...
Click to collapse
Which is why senior members in all sections create guides like - [GUIDE] All Things XPERIA - Debranding - Rooting - BL Unlocking - Theming to make it easier for People like yourself, and in those guides you'll find things like...
XperienceD said:
Rooting:
UPDATE: One click root [4.1.B.0.587 /.431 /.562 ] All 2011 Xperias
- What is rooting and why should I do it? The pros & cons of Android rooting
Rooting methods for the XPERIA line of Phones has constantly changed from apps to Pre-Rooted ROMs and Kernels. A Google search of "root -insert device name-" should help to find the specific method for your Phone but the following link is well worth reading - [How-To] Rooting guide for 2011 xperia devices
References:
[Arc/S] [PRO] Root for 4.0.4 ICS Update [4.1.B.0.431+4.1.B.0.587]
Root MANY ANDROID! [Upd: 18.12.2012]
[ROOT+BB+CWM] ICS and non rootable GB build
[ROOT][NOOB GUIDE][for unlock BL] For Official ICS 4.0.4
[HOW-TO][FTF] Root and CWM with the latest 9.0.1.D.0.10 firmware
[ROOT&MORE]Xperia 2012 line Flashtool + prerooted system.img + Sony fw FTF + addons
[Tutorial]Root.Xperia 4.0.4 ROM [all h/m(dpi)] | 4.1.B.0.431
Click to expand...
Click to collapse
...so when a new members start new threads about something that's been covered a gazillion times, it can be quite frustrating.

XperienceD said:
Which is why senior members in all sections create guides like - [GUIDE] All Things XPERIA - Debranding - Rooting - BL Unlocking - Theming to make it easier for People like yourself, and in those guides you'll find things like...
...so when a new members start new threads about something that's been covered a gazillion times, it can be quite frustrating.
Click to expand...
Click to collapse
Well, I did follow the steps in at least one of those guides. And that worked. So the problem wasn't in working out how to root the phone, but in fixing what went wrong afterwards. The first attempt at rooting worked, but then flashing a ROM failed, the phone stopped working and after fixing that i lost the root and couldn't find a way to reroot it (even ater following all the steps in the guides i previously used, it just didn't work)
So, with all do respect to those guides and their usefullness, as far as I can tell my problem/question wasn't answered in them.

Verizon Galaxy S4 (SCH-I545) Build JSSI5J.I545VRUEMK2

Okay, I just replaced my Google Galaxy Nexus with the Verizon Galaxy S4 (SCH-I545) Build JSSI5J.I545VRUEMK2
first I downloaded the odin and stock rom to have on hand, just in case...
I first tested to see if I could use odin to go from stock rom to stock rom, just as a test and we are all set there..
second I rooted the phone...awesome great, right? Wrong
after rooting and confirming root with root checker, I loaded Rom Manager, flashed it with the latest recovery...rebooted to recovery and bam I get an error message "android system recovery <3e>"
I have even manually downloaded the recovery from CWM
I have tried rooting with both saferoot&disableKNOX as well as I545ALL-IN-ONE-TOOL, the VerizonGalaxyS4RootMDK, and I have done the LOKI method, I still get the same recovery error message.
So as far as I can get is a rooted device, I cannot get a custom recovery loaded successfully even though CWM say the flash is successful
Anyone, have any ideas where I am going wrong? this is driving me crazy and I am pulling all my hair out...oh wait, I don't have any...lol
Please help, it would be much appreciated!

xanuri said:
Okay, I just replaced my Google Galaxy Nexus with the Verizon Galaxy S4 (SCH-I545) Build JSSI5J.I545VRUEMK2
first I downloaded the odin and stock rom to have on hand, just in case...
I first tested to see if I could use odin to go from stock rom to stock rom, just as a test and we are all set there..
second I rooted the phone...awesome great, right? Wrong
after rooting and confirming root with root checker, I loaded Rom Manager, flashed it with the latest recovery...rebooted to recovery and bam I get an error message "android system recovery <3e>"
I have even manually downloaded the recovery from CWM
I have tried rooting with both saferoot&disableKNOX as well as I545ALL-IN-ONE-TOOL, the VerizonGalaxyS4RootMDK, and I have done the LOKI method, I still get the same recovery error message.
So as far as I can get is a rooted device, I cannot get a custom recovery loaded successfully even though CWM say the flash is successful
Anyone, have any ideas where I am going wrong? this is driving me crazy and I am pulling all my hair out...oh wait, I don't have any...lol
Please help, it would be much appreciated!
Click to expand...
Click to collapse
Have you tried UNLOCKING your device first? Sometimes this happens when the phone is locked to a certain company and when you try to do custom roms they aren't successful sometimes due just this fact, at least for me this worked on my Verizon S4 (I don't care much about warranties anymore once I change roms)
Hope this works

firemex said:
Have you tried UNLOCKING your device first? Sometimes this happens when the phone is locked to a certain company and when you try to do custom roms they aren't successful sometimes due just this fact, at least for me this worked on my Verizon S4 (I don't care much about warranties anymore once I change roms)
Hope this works
Click to expand...
Click to collapse
after rooting and during boot, I get the "Samsung Custom" with a unlocked padlock screen...so I assume that means it is unlocked??

firemex said:
Have you tried UNLOCKING your device first? Sometimes this happens when the phone is locked to a certain company and when you try to do custom roms they aren't successful sometimes due just this fact, at least for me this worked on my Verizon S4 (I don't care much about warranties anymore once I change roms)
Hope this works
Click to expand...
Click to collapse
Or are you talking about CARRIER unlocking the SIM? If so do you happen to have a reference for doing this to a Verizon Phone?

xanuri said:
Okay, I just replaced my Google Galaxy Nexus with the Verizon Galaxy S4 (SCH-I545) Build JSSI5J.I545VRUEMK2
first I downloaded the odin and stock rom to have on hand, just in case...
I first tested to see if I could use odin to go from stock rom to stock rom, just as a test and we are all set there..
second I rooted the phone...awesome great, right? Wrong
after rooting and confirming root with root checker, I loaded Rom Manager, flashed it with the latest recovery...rebooted to recovery and bam I get an error message "android system recovery <3e>"
I have even manually downloaded the recovery from CWM
I have tried rooting with both saferoot&disableKNOX as well as I545ALL-IN-ONE-TOOL, the VerizonGalaxyS4RootMDK, and I have done the LOKI method, I still get the same recovery error message.
So as far as I can get is a rooted device, I cannot get a custom recovery loaded successfully even though CWM say the flash is successful
Anyone, have any ideas where I am going wrong? this is driving me crazy and I am pulling all my hair out...oh wait, I don't have any...lol
Please help, it would be much appreciated!
Click to expand...
Click to collapse
i got exact same problem only i can root my device so far any solution ?

Verizon locked bootloaders. I tried this with twrp and had that issue too
Sent from my SCH-I545 using xda app-developers app

I realize this a 2-year-old post, but would you happen to still have the stock firmware (I545VRUEMK2) for this thing? I have an older Jellybean unit that I need to fix (and want to keep JB as I can root it easily).
Thanks

SGH-T999 Custom ROM with working 4G

Greetings,
I really don't want this to be a repeat post, so I have spent many days now searching for this answer, not just here on XDA if I was honest, I have links to prove it
The aim is to give a little new life to my old phone, and get off the 4.1 build it is on.
With that said, in summary, I have tried a few different custom ROMs; Cyanogenmod 11 - 13, stable to nightly. PAC MAN ROM for Lollipop, some other roms for KitKat I found else where, but in all these I have not been able to get 4G to work. I understand about updating the Modem, and got the latest version from DocHoliday77's post for the Galaxy S3, in point of fact I tried every modem version for 4.3+ on there
But for all this, and it's been time consuming I never managed to actually get 4G to work as stated
I tried playing with settings in Test Mode (*#*#4636#*#*), changed preferred settings, added APN's, rebooting during certain phases of the moon ... but somehow it all avails me diddly.
Finally I have genuinely tried searching for info on if this just isn't going to happen and that's how it is, but somehow I found lots of posts about other models or networks that made it work more than something saying this won't work (putting aside the info on CM 11 that states it's a known issue and won't work on some build I forget).
Which leads me to this post: I wondered if anyone could point me in either the direction of a 4.4+ custom ROM or other ROM, compatible for SGH-T999 (T-Mobile Galaxy S3), that has working 4G. Or how I can get 4G to work on one of the ROMs I have already tried, kind of partial to a nice CM but I am willing to venture.
Also happy to just hear other input about giving new life to the phone so any feedback welcome
Thanks for your time!
NOTES
======
Using TWRP 3.x for flashing
Phone is rooted
IMEI is visible & fine on custom ROM
4G works on stock ROM
not experienced at this but willing to read
Edit: something I had not noticed before, I install Gapps for most of my tests but never use it. I just tried to download from Play Store, it acts as though I have no connection; waiting to download appears, then eventually it says waiting for network. Yet I am able to browse the net fine with the phone floating between 3G & H+. I don't know if that might help, so figured I should add it.

Is the phone running the latest bootloader and modem? Maybe both are needed to properly get 4g on all Roms?

audit13 said:
Is the phone running the latest bootloader and modem? Maybe both are needed to properly get 4g on all Roms?
Click to expand...
Click to collapse
That's a really good question, let me see if I can find out how to get my bootloader info and I'll get back to you.
May I ask what the latest bootlader is for the SGH-T999, or where I could find this so I can compare it? I couldn't seem to find it, though the most resourceful post I did find related was T999 UVDMD5 Firmware / Bootloader by mnasledov, though it is also a little outdated it appears, I haven't read my entire way through it yet sorry, I also know the phone is a little outdated too .

So that wasn't too bad to find out
I don't have the latest bootloader if that should match the baseband I install.
Where after a ROM install I get my baseband to T999UVUEOH1, but the bootloader stays on T999UVDLJA.
I haven't quite found where to get the latest bootloader just yet, though I did really spend the last few minutes discovering about the bootloader; if you or someone could find the time to point me in that direction that would be awesome

Simplest way to make sure you have the latest would be to flash the most recent stock rom from sammobile.com in Odin.

Thank you very much @audit13, I do appreciate the time you took out to help me and I also appreciate the point in the direction of what next.
I'll go dig into that for a while and see what to do to be sure, before I start
Looks like this is the latest one, so I will give this a shot : PDA T999UVUEOH1 & CSC T999TMBEOH1, version 4.3.
So just as a quick question, since I've never upgraded the bootloader in this fashion etc., from what I have read this is a one way street correct? And since I am upgrading to stock, then I guess will I lose root, which I will have to go back down the path of for a reinstall, or could I flash my old back up over this from TWRP and in that fashion have the latest bootloader, but keep everything I have for the moment as I investigate a ROM that will offer 4G.
I guess what I am getting at is even if having the latest bootloader and some other ROM with the latest baseband doesn't give me 4G still, can I go back in terms of the OS version to my 4.1.1 and keep things as is with a newer bootloader?
I will investigate this myself too, I just always preferred some additional input when discovering things where possible.
I do appreciate your time, thanks again!

No, you cannot run stock 4.1.1 on a 4.3 bootloader unless it is a custom 4.1.1 rom based on a stock touch wiz rom.
I do not think it is a problem to run the latest bootloader and modem as the latest custom ROMs often require an updated bootloader and modem.
Once on a 4.3 bootloader, you can't downgrade to something older.

Thanks again @audit13, that matches what I have read, I appreciate the confirmation!
Looks like I will be undergoing a re-root etc. so I'll get my information together, have a little more read, see what I need to back up and then jump down the rabbit hole
I'm grateful for your time and help.

If you decide to run a custom rom, just flash a stock rom, then immediately flash twrp via Odin, then install the rom and gapps. No need to root before hand.

Ahh ok, that would have made the most sense. However I didn't have an opportunity to check back on this thread until now so even though you had awesome speedy reply I missed it.
I did manager to successfully flash the stock ROM from Sam's. It did also update the bootloader so THANK YOU very much for that.
I had to fiddle a little to get Odin to recognize the my Galaxy S3 in the end it was simple: after I installed Kies to get the drivers on, I disabled WI-Fi (I use it for my dev work, and then it didn't try to spend time getting other drivers and it all went great. But that's just a note incase maybe one day someone else reads the thread and wonders how, this might help.
I'm just actually restoring a couple f things on the stock ROM, I figured I would have it ready in the event a custom ROM doesn't suit immediately, as I find one I like, then I have a back up of the stock ROM on 4.3 to revert to. Incidentally I just used TWRP manager from Google play store to install TWRP, hopefully it's the same as the flash, except now I know I rooted when I didn't have to
@audit13 Thanks, I know I keep saying that but I appreciate your time the same way I would hope someone else appreciated mine.
Incidentally once ready I will post an update here about the success of getting 4G on Cyanogenmod 12 or even 13 maybe, or someone of the other custom ROM I try, to share that info.

So just an update, I can confirm even with both an updated bootloader and matching updated baseband there is still no 4G on Lollipop Cyanogenmod 12, haven't quite tried any other yet, that was the one I liked the most but I will carry on and get a list as I have time then update here.
If there are any further suggestions I'm all open to them
Thanks [email protected]

Do you get 4G on a stock ROM? You have an LTE capabale sim? You get 4G on another phone with the same sim card?

Right, this SIM gets 4G on 2 other phones it's been in, on this phone on stock ROM it gets 4G too. Reverting back to stock backup in TWRP, from CM12 looks like it tripped knox I think it is, so now the warranty bit is 1 oops. But I managed to Odin back to 4.3 stock, so now I also need to see if I can try to flash maybe to CM 11, which is 4.4.x, or if maybe I'm stuck here. If I can find out I certainly will update the result of 4G testing.
You've been really patient & helpful thanks!

First let me say I'm a noob. I've rooted and jailbroken devices but I admit it's all from falling instructions. I rooted my s3 a while ago and installed twrp 1.0.8.7 yesterday. I did a full wipe including system and all catches and installed the latest nightly of cm13. Everything is running great. I don't know if this helps but maybe it's your process. Good luck!
Sent from my Amazon Jem using Tapatalk

Shack70 said:
First let me say I'm a noob. I've rooted and jailbroken devices but I admit it's all from falling instructions. I rooted my s3 a while ago and installed twrp 1.0.8.7 yesterday. I did a full wipe including system and all catches and installed the latest nightly of cm13. Everything is running great. I don't know if this helps but maybe it's your process. Good luck!
Sent from my Amazon Jem using Tapatalk
Click to expand...
Click to collapse
That's really helpful thanks @Shack70, since updating to 4.3 I have only tried CM 12, I can certainly give 13 a shot, & you have 4G working then please?
incidentally I have actually recorded every step I performed, in the event I repeat this again or I had to explain it. But my process maybe at fault I agree; I rooted my phone with towelroot. Installed TWERP manager (3.0.2 something, maybe I should try 1.0.8?), rebooted into recovery & first thing was take a full backup on stock. Then I did a factory wipe, & advanced wipe. Then installed the ROM, wiped dalvik/cache. Installed Apps, wipe dalvik/cache, reboot
Hopefully that's not too much? I just wonder if any of those steps raise alarm?
Edit: mind if I throw a few questions on here at you please @Shack70?
what do you wipe from the options please?
after the install, do you run any other wipes please?
how did you get TWRP on your phone? Not sure if that or version matters but I'm willing to try

Morrigon said:
That's really helpful thanks @Shack70, since updating to 4.3 I have only tried CM 12, I can certainly give 13 a shot, & you have 4G working then please?
incidentally I have actually recorded every step I performed, in the event I repeat this again or I had to explain it. But my process maybe at fault I agree; I rooted my phone with towelroot. Installed TWERP manager (3.0.2 something, maybe I should try 1.0.8?), rebooted into recovery & first thing was take a full backup on stock. Then I did a factory wipe, & advanced wipe. Then installed the ROM, wiped dalvik/cache. Installed Apps, wipe dalvik/cache, reboot
Hopefully that's not too much? I just wonder if any of those steps raise alarm?
Edit: mind if I throw a few questions on here at you please @Shack70?
what do you wipe from the options please?
after the install, do you run any other wipes please?
how did you get TWRP on your phone? Not sure if that or version matters but I'm willing to try
Click to expand...
Click to collapse
In twrp I wiped system and all caches before installing the rom and gapps. I installed an older version of twrp using Odin and updated it to 2.0.8.7 using the twrp app in the play store. Yes I have 4g/lte. I've seen it switch from lte to h+ to 3g depending on my location so I'm sure it's working correctly. The camera and Bluetooth also work fine. I hope this helps, I'm still learning and most of what I've done is just by following others instructions here at XDA.
Sent from my Amazon Jem using Tapatalk

I definitely appreciate the reply thanks!
I gave the latest nightly CM 13 a shot just now, 7/31/16 version essentially. Not finding any issues with the ROM, can't get 4G to show up no matter what though , even with changes and attempts to APN settings etc. None the less maybe to give my phone a rest I'll just stick with this a while and decide if a newer nightly comes out I want to try, or better yet a stable version at some point. Then I can verify how much I really miss my 4G I guess.
All the previous attempts, including this one always results in 3G to H+ network with no issue, it's just that 4G that never shows up for me.
Incidentally without a serious search around I couldn't even find TWRP 2.0.8.7, it's not on the TWRP manager version I have so curious, I ended up just going with 2.8.0.7, thinking maybe it was a typo?
Otherwise I basically run the same type of install you mention, I also clean dalvik, cache, system & data in my case. Just to confirm that.
I have a slightly off topic question here, if I decide to go back to to stock I was wondering, if i went from UVUEOH1 4.3 JB build, to the previous UVUENC2 4.3 JB build; because I've seen this available as a clean route 66 version, is this still considered a downgrade and a bad idea? I'd be flashing with Odin from @DocHoliday77 post here.
@Shack70, thanks for the input, thanks for the guide on your steps, glad I've confirmed I'm doing the same even if I can't get my 4G, hopefully someone on a Galaxy S3 T-Mobile, went through this found a solution, and maybe will let me know what they did too, not sure if you are on T-Mobile or not. 
 @audit13, also thanks, you've been replying plenty too and I appreciate that also!

One small thing I just came across looking over the logs of the install.
When flashing CM 13 with TWRP, I noticed it said the Target: samsung/d2tmo/d2tmo:4.3/JSS15J/T999UVUEMJC:user/release-keys.
Is it normal and OK for it the be referencing a different baseband/bootloader than what I actually have on my phone?
UVUEMJC vs the UVUEOH1? Where the one as named by TWRP flash is 2 versions older than what I have installed? Not necessarily stating this is an issue, just asking please if this is normal, and I also understand it could be something I have overlooked in my reading, it's been a lot of reading

I would not worry about the referenced baseband as flashing CM13 does not change the bootloader or baseband during the flash process.

audit13 said:
I would not worry about the referenced baseband as flashing CM13 does not change the bootloader or baseband during the flash process.
Click to expand...
Click to collapse
That makes sense thanks @audit13, just a few of the questions I had building up.
So that my previous question doesn't get lost, and although I know it's a dying phone for users hopefully this might get some visual
if I decide to go back to to stock I was wondering, if i went from UVUEOH1 4.3 JB build, to the previous UVUENC2 4.3 JB build; because I've seen this available as a clean route 66 version, is this still considered a downgrade and a bad idea? I'd be flashing with Odin from @DocHoliday77 post here.
Click to expand...
Click to collapse