Develop Bugs

Will this phone every get a more conventional root?

Coming from HTC/Motorola phones primarily the development for this phone has confused me a bit. Those phones used to get a normal root method pretty soon after release without having to worry about messing around the kernal.
Is there going to be a day where you can just root it and leave the kernal alone or is the kernal/root thing exclusive to Samsung phones?

Whsn i was on att i would use superoneclick. I too was wondering this.
Sent from my SPH-D710 using XDA App

We need this.
Sent from my SPH-D710 using XDA App

The root for this phone is as easy as it gets. I just rooted my friends inspire and while it is only one click the process it goes through us way more complex.
Samsung Galaxy S II

stangdriverdoug said:
The root for this phone is as easy as it gets. I just rooted my friends inspire and while it is only one click the process it goes through us way more complex.
Samsung Galaxy S II
Click to expand...
Click to collapse
Yeah I have to say this was a very easy process to root coming from an evo4g
Sent from my SPH-D710 using XDA App

I think he meant the fact that ur using the kernel to get to root instaed the more conventional root method we are used to seeing on devices like htc and so on. It is pretty strange the fact u flash a kernel and then flash to get root its typically gain root then flash somethingy. Or at least thats what my noob ass is used to lol
Sent from my SPH-D710 using XDA App

stangdriverdoug said:
The root for this phone is as easy as it gets. I just rooted my friends inspire and while it is only one click the process it goes through us way more complex.
Samsung Galaxy S II
Click to expand...
Click to collapse
All the root methods are simple to execute for someone who can read. But I am referring to the fact (as edison said) that you have to flash a new kernal to achieve root. I'm personally waiting for a more typical root method before I root.
Not that I don't appreciate/love the dev community but I like a COMPLETE stock setup with root before I go messing around experimenting because I don't necessarily trust EVERY dev and don't have the technical expertise to fix stuff myself.

Only solution is to just wait, I don't think many would be working on another root method because this one isn't complex, is noob friendly and works 100% I don't see any pressing reason for another method
Sent from my SPH-D710 using xda premium

Yup I hear ya. You can always root then odin bubbys pulled stock kernel for a complete stock root. It's not one click but it's close. Only draw back it there is no recovery.
Samsung Galaxy S II

Conventional root?
What is that?

Umm...there is no other way? There's no exploit anymore guys...it's either flash a rooted kernel or flash a rooted /system. And that's easy as hell
Sent from my SPH-D710 using xda premium

Unless you can get hold of Samsung's signing keys for creating a signed update.zip or find a new exploit (which would have to be fixed eventually because exploits are essentially security holes) you are pretty much stuck with the current methods.
Sent from my SAMSUNG-SGH-I777 using XDA App

squshy 7 said:
Umm...there is no other way? There's no exploit anymore guys...it's either flash a rooted kernel or flash a rooted /system. And that's easy as hell
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Wow,so no more one click roost with cwm then we can flash any kernel and be good? Shizznit, one click was good stuff
Sent from my Nexus S 4G using xda premium

I miss z4root. Im not a newber but I know I like my simplicity redundantly simple.
Sent from my SPH-D710 Galaxy S II [suck it]

Honestly odin is pretty the one click we need.
.: sent from my Samsung Galaxy S II Epic 4G Touch :.

Dude samsung released the source and practically handed us root on a silver platter
Sent from my SPH-D710 using Tapatalk

gpgorbosjr said:
All the root methods are simple to execute for someone who can read. But I am referring to the fact (as edison said) that you have to flash a new kernal to achieve root. I'm personally waiting for a more typical root method before I root.
Not that I don't appreciate/love the dev community but I like a COMPLETE stock setup with root before I go messing around experimenting because I don't necessarily trust EVERY dev and don't have the technical expertise to fix stuff myself.
Click to expand...
Click to collapse
Why should anyone find a exploit to root the phone when the bootloader
Is open and allows you to root much easier....google keeps closing holes in software making it harder and harder to root ...its not a htc where they s-off the phone .....this will probably be the only way to root because there is no reason to find another
Sent from my SPH-D710 using xda premium

What could be easier than putting this in Odin http://forum.xda-developers.com/showthread.php?t=1282415 and hitting the start button

I think the point people are trying to make here is that they wish there was a way to have root and recovery and remain bone stock. So far there is no way to do this. Alot of people don't want to flash a custom kernel at this point because of all the problems people are reporting. Myself included. I am still stock and won't root until devs get this stuff sorted. Maybe koush will figure it out...
Sent from my SPH-D710 using Tapatalk

It's not really clear from the titles in the development section, but there is a way to root without flashing a kernel.
http://forum.xda-developers.com/showthread.php?t=1282418
That's a stock system image, simply modified to include root. No kernel at all.

Should I root my yakjuxw Gan galaxy nexus?

I'm new here and just got my first nexus phone about 2-3 weeks ago from Negro electronics...
should I root my phone so I can be on Ics 4.0.3 or should I just be patient and wait for Samsung to update my device or flash my phone to be yakju so I can get update from google
thanks
Sent from my Galaxy Nexus using XDA App

I would root it.
Benefits of rooting:
- Faster
- amazing battery life
- more apps can be used
- more customizable
You can always reroot it if you don't like it rooted.
I also recommend using francofrancisco's kernal if you are looking for something pleasurable

Rooting in itself wont change anything, other then the costumary whipe of phone to do it.. to make faster you'd need to flash costume roms and kernels
Sent from my Galaxy Nexus using xda premium

skarenboo said:
I'm new here and just got my first nexus phone about 2-3 weeks ago from Negro electronics...
should I root my phone so I can be on Ics 4.0.3 or should I just be patient and wait for Samsung to update my device or flash my phone to be yakju so I can get update from google
thanks
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Do it only if you know how to and understand the benefits and risks involved, I've rooted multiple devices yet I decided to keep this one stock (I'm also running a yakjuxw build. I'll wait for the 4.0.3 update which should not take very long to get pushed
Sent from my Galaxy Nexus using xda premium

Tjotte said:
Rooting in itself wont change anything, other then the costumary whipe of phone to do it.. to make faster you'd need to flash costume roms and kernels
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
what costume rom do you recomend? Batman??

I'm not familiar with the benefits from rooting... hence I haven't done it...
I've jail broken my ipod touch and hated it and had to un jail break it ... so not sure how it is with androids...
thanks
so you think we WILL get the updates just a matter of WHEN?

[Q] first time unlocking phone questions

Unfortunately it appears that I will have to reset my galaxy nexus. Since i bought it, the battery hasnt been too bad, but starting yesterday I have only been able to get 3 hours of usage time. Sucks. So since i cant find the problem it looks like I have to reset the phone. And if i reset my phone I guess this is a good opportunity to root my phone. I am familiar with Forum etiquette and have done a lot of reading but there is so much information out there and it is getting updated constantly. Now after reading a ton of forums including this one, I think it is a good time to finally unlock my phone. I have a couple of questions.
First question: Even if i didnt want to install any custom ROMS, etc... I should still at least unlock the bootloader as this is the first step to doing anything? Right? Even if I didnt want to add any custom roms and stay on the stock ICS 4.02 i would just unlock the bootloader?
From what I have read and understand, there are 2 procedures to do.
1. back up all your data
2. unlock the bootloader
3. flash a custom or stock rom
what i really want to do is unlock the phone and either keep ICS 4.02 or install the stock ICS 4.04 update.
I have seen instructions from these 2 links.
http://www.androidust.com/install-ice-cream-sandwich-ics-on-verizon-galaxy-nexus-android-4-0-4/
http://androidadvices.com/update-galaxy-nexus-air-ota-manual-download/
Are they good instructions as I have seen different ways of doing this or is there a better link on this forum that has better directions. I trust this forum the most as I have been on all of them and they always refer to this forum. I am really confused and if anyone can send me in the right direction I would appreciate it.
Thanks

http://forum.xda-developers.com/showthread.php?t=1392310
[GNex TOOLKIT V5.7] Drivers, Backup, Unlock, Root, CWM, Flash, Mods + MUCH MORE [GSM]
Hands down they easiest way to go about it
Sent from my Galaxy Nexus using xda premium

Tjotte said:
http://forum.xda-developers.com/showthread.php?t=1392310
[GNex TOOLKIT V5.7] Drivers, Backup, Unlock, Root, CWM, Flash, Mods + MUCH MORE [GSM]
Hands down they easiest way to go about it
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
True. That's the best way to go. Spent hours trying to root mine before discovering the Toolkit.
Sent from my Galaxy Nexus using XDA

AndIKnow said:
True. That's the best way to go. Spent hours trying to root mine before discovering the Toolkit.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Trust me, you did the right way. If your phone ever does anything you don't want it to, having knowledge of how to use fastboot greatly increases your chances of a quick fix. All in all, these toolkits are not really recommended.
Sent from my Galaxy Nexus using XDA

I do agree with above poster, i also did it "the hard way" first time rooting my GN, coming from Xperia X10 doin alot of rom'ing back and forth switching kernels/radios, so yes absolutely.. try to learn it the proper way but the toolkits are fast and easy to use so i prefer it i'm no pro in any way and all my knowledge is very ,temporary, if you like.. i read some guide and follow it to reach my result, i suck at remembering it after i'm done have fun tinkering
Sent from my Galaxy Nexus using xda premium

Idiot mistake and the company that fixed it for me

I made the ultimate mistake the other day. I flashed a kernel for another device onto my S3 and of course paid the price of bricking my phone.
To set the scenario, I had back surgery last Thursday and was released from the hospital on Friday with a supply of pain killers and orders to not do anything. Well, while sitting around doing nothing I got bored and decided to work on a couple of my friends tablets that needed rooting and roms installed. I got them done without any issue and then decided to mess with my phone. There were a couple of new kernels I wanted to test and so I decided to do this. I booted into recovery and selected the kernel and flashed. At that moment I realized that the kernel I just flashed was not for my phone and when I tried to turn on the phone and nothing happened, I knew immediately what I had done and after saying a few nasty words to myself I started searching for a way to fix it. While searching through the forums I kept reading about MobileTechVideos.com and their ability to jtag repair phones. Since I have never had to do this and my phone was not going to work anyway I decided to give them a call and see what they had to offer. I called them and asked about their services and they said that it should be no problem fixing my phone. I live in Dallas and the company is in Bryan, about 3 1/2 hr drive, I decided the easiest and fastest way to get my phone repaired was to take it to them and wait. On Tuesday morning I drove to Bryan and dropped off my phone. When I had called them they told me it might be a couple of hours to fix it, but once I told them it was a tmobile device they told me to wait because it might only take a few minutes. During this time they showed me around the office and I was really impressed. What impressed me the most is that no one working for this comany could have been over 25, even the owner. So after a brief tour of the office, about 10 minutes, my phone was fixed and was ready to go. I paid my $60, which I believe was well worth it, said thank you and was on my way with my fully functional phone.
They never asked me to post anything and I don't have any affiliation with this company. I just want to post about a company that provided the service they said they would at a price that is reasonable since without it I would have a $600 paperweight. So if anyone ever happens to make the foolish mistake that I made and you need your S3 repaired, I would 100% recommend this company. Here is the link to their website, http://mobiletechvideos.mybigcommerce.com, mods let me know if this is not allowed and I will remove it.
I know I am always questioning online companies likes these, but this particular company has earned a customer for as long as they are open and support whatever device I happen to be using. I just hope that since I made this mistake I will hopefully never make it again.
Moral of story: If on heavy doses of pain killers don't crack flash kernels. If might cost you in the end. :}

Never bricked a phone before but I've heard great things about that company. If I ever run to trouble I'll surely go to them immediately.
Thanks for the review.
Sent from my SGH-T999 using xda app-developers app

Thanks for the review - it's good to hear good comments about the company "just in case".
Hope you're feeling better.

Cool.... Drugs say No to them... Get well
Sent from my SGH-T999 using xda app-developers app

bgbagz said:
Cool.... Drugs say No to them... Get well
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Pain meds after back surgery are a definite yesssssss, just don't brick your phone. lol
Happy to read a ringing endorsement, though - also "just in case".

Hey dude. Im in Dallas too. Good to know. I read all about them. They are really good in jtag fix devices. They were the first ti have s-off on the htc one. They did it after an hour of getting the phone. I havent brick any phones yet but I have their number save just in case. I have seen where they sale the jtag device to do it yourself. It cost about $100 it is well worth it
Sent from my SGH-T999 using xda app-developers app

Good service but more expensive than some.. but local is good.
Sent while sleeping in chair.

I'm glad your device is back and operational. Thanks for letting us know about a trusted reputable service.
Sent from my SGH-T999 running Chihuahua v1 ROM

Thanks. I am not one who likes reviewing companies, but this one time I felt it was justly deserved. I read to many threads about shipping your device to someone and for a cheaper cost they will fix it. That makes me uncomfortable. I would rather pay a little more for the peace of mind. Even then I was more comfortable driving as far as I did, after just having surgery, because of my skeptism. That is why I felt the review was warranted to help someone when they are not local.
Sent from my Transformer Prime TF201 using xda premium

Josh @mobiletechvideos is certainly a trusted guy. He's been here since vibrant days.
Sent from my SGH-T999 using Tapatalk 2

I didn't realize your phone would get bricked with a bad kernel. You can't just go into odin and restore the original system image?
Not criticizing here, I'm just trying to learn something. Glad you had a good experience, as I'm sure at some point in my life I'm going to brick a phone.
Sent from my SGH-T999 using xda app-developers app

I can confirm that flashing a wrong kernel will brick your phone. I did that and still not sure if it was wrong one but in did screwed my phone, luckily I exchanged it for another device since I had it for a week.
Sent from my SGH-T999 using xda app-developers app

I have done the same thing. I flashed an international ROM on my T-999. I had also read great reviews people had using Mobiletechvideos. He had mine back to me in less than 1 week. Awesome work. If someone from MTV is on here, thank you!!

wcterp said:
I didn't realize your phone would get bricked with a bad kernel. You can't just go into odin and restore the original system image?
Not criticizing here, I'm just trying to learn something. Glad you had a good experience, as I'm sure at some point in my life I'm going to brick a phone.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It wasn't a bad kernel, it was a kernel for a different device. I was working on several devices that day and put a kernel for a nook tablet into my S3 folder by mistake. Teaches me to only work on one device at a time.
Sent from my Transformer Prime TF201 using xda premium

Yes don't take painkillers give em to me lol
thanks for the write up good to know

Can't you just re flash the entire rom stock or not with Odin or cwm?
I dunno, first time I "bricked" my phone was from an incorrect kernel also. Just downloaded stock touch wiz rom go to download mode and flash with Odin.
I'm not aware that you can brick your phone unless you mess with the bootloader itself.
Bricking means exactly what it sounds like. It's just a piece of useless hardware that you can't recover, in this case, with an incorrect kernel flash, you can, either through another kernel that is compatible with your device or re flash the entire rom; with either Odin or cwm.

wardoc22 said:
Can't you just re flash the entire rom stock or not with Odin or cwm?
I dunno, first time I "bricked" my phone was from an incorrect kernel also. Just downloaded stock touch wiz rom go to download mode and flash with Odin.
I'm not aware that you can brick your phone unless you mess with the bootloader itself.
Bricking means exactly what it sounds like. It's just a piece of useless hardware that you can't recover, in this case, with an incorrect kernel flash, you can, either through another kernel that is compatible with your device or re flash the entire rom; with either Odin or cwm.
Click to expand...
Click to collapse
When trying to connect to computer it would not recognize the device correctly. So no odin if you can't connect to computer. No flashing anything else if the phone doesn't turn on. That would be as hard bricked as you can get.
Sent from my SGH-T999 using xda premium

tmjohnsonfse said:
When trying to connect to computer it would not recognize the device correctly. So no odin if you can't connect to computer. No flashing anything else if the phone doesn't turn on. That would be as hard bricked as you can get.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Yeah but you can't hard brick it if you flash a wrong kernel unless the kernel replaces your bootloader.
Oh wait, ok I get it. You flashed a kernel that replaces the bootloader also, like with the international dual boot kernel

wardoc22 said:
Yeah but you can't hard brick it if you flash a wrong kernel unless the kernel replaces your bootloader.
Oh wait, ok I get it. You flashed a kernel that replaces the bootloader also, like with the international dual boot kernel
Click to expand...
Click to collapse
Correct!
Sent from my Transformer Prime TF201 using xda premium

4th time I had to factory restore. This is unbelievable.

Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium

If its boot looping that's not normal obviously you know that so I would exchange it. Keep swapping until you get a good one.
Sent from my Nexus 7 using Tapatalk 4

Rican Bx Bomba said:
Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
wha?? I would return immediately.

Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium

player911 said:
Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Will try that. Thanks!
Sent from my SPH-L710 using xda premium

player911 said:
Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thought I'll give you an update.. Installed CM10.2 for a few days, as you said.. No issues what so ever. Decided to try my luck with CoolRom and it bootlooped the moment I rebooted.
Decided on doing a complete wipe of the device and flashing a factory rom ( http://forum.xda-developers.com/showthread.php?t=2381582 ).
Don't want to give up hope yet.

Rican Bx Bomba said:
Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app

smurphdogg said:
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Rooted it for some apps that required root access.

smurphdogg said:
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
There are tons of apps that require root access and are mandatory for many people including me.

I wouldn't bother to unlock and root. The N7 is flawless and fast out of the box.
Sent from my Nexus 7 using xda app-developers app

Again, root access is required for most decent backup programs and cloud data syncing apps. The issue doesn't require a debate about whether you need root or not. Yes the N7 is wicked fast and if you only use it as a bathroom reader for Facebook and light use, then that's cool. I like OTG support for my thumb drives when I'm in the field working.
Glad CM is working for you. That at least shows it isn't a hardware problem. I'd reflash stock images and see where that leaves you. Worse case you use CM (oh my!) until we see a patch.
It sounds like it just has a corrupted stock image. Kernels typically cause the reboots but a bad app or system file can too.
If you flash stock back and you still have issues, try just flashing a modified stock kernel (stock rom/custom stock kernel). CM has its own kernel which might be why it was working better.
You also should do a complete wipe between stock and CM and AOSP and vice versa. It typically bootloops if you dirty flash one type of rom over another. Stock and AOSP are pretty much the same thing but some custom ROMs like CM have different structures that hose you.
Sent from my Nexus 7 using XDA Premium 4 mobile app

player911 said:
It sounds like it just has a corrupted stock image. Kernels typically cause the reboots but a bad app or system file can too.
If you flash stock back and you still have issues, try just flashing a modified stock kernel (stock rom/custom stock kernel). CM has its own kernel which might be why it was working better.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium

Rican Bx Bomba said:
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I do not understand the hassle with Google.
I told them yesterday to get a new device, as wireless charging does not work. I talked max 10 minutes on the phone and I received an email 2 minutes after saying that I'll get a new device.
Yes, they will charge you "temporarily" for this, but you do not have to pay anything.
Anyway, it's me, I found it easy with Google.

Mine bootlooped today. Stock. No root or anything. I was forced to do a factory reset from recovery. Very troubling that this seems to be happening to a few people. There's a couple of threads over on android central of people having the same problem.
Sent from my Nexus 4 using XDA Premium 4 mobile app

I will admit this device is great without root but I prefer custom ROMs and titanium backup
Sent from my HTC One using XDA Premium 4 mobile app

Just sat here rebooting the n7 a few time and it happened. Held power and got it to re start the boot process and it loaded. As soon as I unlocked it I got an android process media force close
Sent from my Nexus 4 using XDA Premium 4 mobile app

Andro_pty said:
I do not understand the hassle with Google.
I told them yesterday to get a new device, as wireless charging does not work. I talked max 10 minutes on the phone and I received an email 2 minutes after saying that I'll get a new device.
Yes, they will charge you "temporarily" for this, but you do not have to pay anything.
Anyway, it's me, I found it easy with Google.
Click to expand...
Click to collapse
I rather not do the whole process of sending, receiving, ect. Call me lazy or whatever. Either way, it seems like my problem is solved, I'm once again happy.
Sent from my SPH-L710 using xda premium

Rican Bx Bomba said:
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Super glad its worked. It worked for me. It worked for another guy. And worked for you. I think there is a bad rom image flashed on all of these that are causing lots of problems. The only fix is to clean slate and reflash the stock image, or move to custom ROMs.
Probably need to get someone to write a little app that just automates flashing the stock image again just for simplicity.
I'll probably create a new thread covering this.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

The stock images and the install script .bat file is simple enough.
Especially if you're rooted already. Since you already have the drivers installed on your computer.
Toolkits need to die a slow painful death.

You need root access a pen drive using an OTG cable, install app like titanium backup etc. Rooting doesn't mean custom rom or kernel
Sent from my Nexus 7 using xda app-developers app