Develop Bugs

[Q] Rooting 4.0.2.A.0.62, already have an unlocked bootloader. Help?

So folks.
Just reached home with my new phone, an Xperia Arc S LT18a, I believe.
I'm stuck with this firmware 4.0.2.A.0.62 which doesn't seem to have an easy way to get a custom ROM on it yet. Sucks that I didn't read about this before heading out to buy a phone.
I went through one of the guides here and had the bootloader unlocked via Sony's website. However, the rooting instructions didn't work. So searched further and realised the issue.
I've seen people say that they've done it by downgrading to a lower firmware, rooting it and then upgrading the firmware OTA again. Then I read that upgrading firmware OTA with an unlocked bootloader will brick my phone. So I'm not trying that.
Any help on how I could go about this? Simple step by step instructions would be very welcomed, since I don't really know much about flashing various bootloaders and ROMs considering I just bought the phone.
Thanks for reading!

there are many threads relating to this problem....plz read & search before posting....
Well i believe the answer to your questions lie in this Thread ...
'
Hope i was helpful ....

Flash the zip I attached to this post through CWM. That's it, you're rooted

Thanks!
I used the above zip file, but from a different thread and got it working. Cheers to both of you!

RamEsRock said:
Flash the zip I attached to this post through CWM. That's it, you're rooted
Click to expand...
Click to collapse
How can I have CWM on my phone? If I will flash phone I will do it with rooted ROM not stock. For me it's closed circle because I need root'ed device to load CWM on it, and I need CWM to make root.
Can someone explain me it?

szaebb said:
How can I have CWM on my phone? If I will flash phone I will do it with rooted ROM not stock. For me it's closed circle because I need root'ed device to load CWM on it, and I need CWM to make root.
Can someone explain me it?
Click to expand...
Click to collapse
With unlocked bootloader, one can easily flash a custom kernel with CWM, then flash the zip file.

Try reading this http://forum.xda-developers.com/showthread.php?t=1304634
jason statham said:
So folks.
Just reached home with my new phone, an Xperia Arc S LT18a, I believe.
I'm stuck with this firmware 4.0.2.A.0.62 which doesn't seem to have an easy way to get a custom ROM on it yet. Sucks that I didn't read about this before heading out to buy a phone.
I went through one of the guides here and had the bootloader unlocked via Sony's website. However, the rooting instructions didn't work. So searched further and realised the issue.
I've seen people say that they've done it by downgrading to a lower firmware, rooting it and then upgrading the firmware OTA again. Then I read that upgrading firmware OTA with an unlocked bootloader will brick my phone. So I'm not trying that.
Any help on how I could go about this? Simple step by step instructions would be very welcomed, since I don't really know much about flashing various bootloaders and ROMs considering I just bought the phone.
Thanks for reading!
Click to expand...
Click to collapse
I when I rooted my locked bootloader ARC S, I read "The Nutshell Arc Guide" at http://forum.xda-developers.com/showthread.php?t=1304634
Before you start messing with the phone, please see the entire guide first.
Hope I can helped.
Cheers

[Q] Please help. Custom ROMs constantly rebooting

ok let me just preface this by saying that i am a complete moron and didn't make a nandroid back up. i am new to this stuf obviously and didnt research enough before i dove in.
also this is referring to the htc on v cdma on virgin mobile.
so i was able to successfully unlock and root the phone. bootloader says unlocked and root checker from the market said i had full root access.
i installed the team win recovery on the phone. the first rom i flashed was the cdma pacman rom from here. i did a full wipe and flashed the rom, and then flashed the kernel from said rom via fastboot on my pc. upon firing it up, it boots and gets through the boot animation and into the OS. but after about 10 seconds my service shuts off (it shows a little R above my reception bars) and the phone reboots. just does this over and over.
so i thought maybe it was the ROM so i tried AOKP jellybean. same issue.
any idea what i did wrong here? thanks in advance.

lol, i had the same problem as you. It happens because of the OTA update or radio version, try using this:
http://forum.xda-developers.com/showthread.php?t=2018518
I just followed Solution 1 and it worked for me, I was originally on CWM but moved to TWRP cause it's more convenient.
After using the RUU you'll be back to bone-stock and will have to unlock the bootloader and all that fun stuff all over again that's if you use solution 1; however, atleast you'll be able to get the stock-rom backed up again for just-in-case. Skip OTA updates, and then proceed to recover and then start rom flashing/fastbooting kernel and all that fun stuff.

reID_entify said:
lol, i had the same problem as you. It happens because of the OTA update or radio version, try using this:
http://forum.xda-developers.com/showthread.php?t=2018518
I just followed Solution 1 and it worked for me, I was originally on CWM but moved to TWRP cause it's more convenient.
After using the RUU you'll be back to bone-stock and will have to unlock the bootloader and all that fun stuff all over again that's if you use solution 1; however, atleast you'll be able to get the stock-rom backed up again for just-in-case. Skip OTA updates, and then proceed to recover and then start rom flashing/fastbooting kernel and all that fun stuff.
Click to expand...
Click to collapse
awesome thank you so much. i am slightly confused on which one to download though. i am assuming it is this one here, the only one i see with sprint/vm branding. RUU​_PRIMO​_C_ICS​_40A​_Sprint​_WWE​_VM_1​.08.652​.6_Radio​_1.00​... i'll give it a shot

yea that's the one, it's an executable file, just make sure you follow the directions for RUU.

reID_entify said:
yea that's the one, it's an executable file, just make sure you follow the directions for RUU.
Click to expand...
Click to collapse
worked like a charm! thanks so much!!!
now to try putting a new rom on here again lol....

For future references I suggest not updating the OTA since its known to cause a lot of problems due to radio discrepancies. I'm glad you were able to fix yours though.
Sent from my Full Android on PrimoC using xda premium

[Q] Trouble installing CWM Recovery on LG E973

Hey folks,
I hate starting new threads but unfortunately I've run out of places to look and the "answers" I've found so far have only further confused me.
I have successfully rooted and unlocked my LG E973 on Bell. My goal is to flash a copy of CyanogenMod 10.1 on to the device, however, I need to install CWM recovery first and I don't know where to start.
I'm new to this and from what I've learned is that I cannot rely on ROM manager as my device isn't fully supported yet, and that I need to find (a specific?) version of recovery files tailored to my device and install them manually to the internal storage, before continuing with ROM manager. (Please correct me if I'm wrong.)
If someone could point me in the right direction, that would be fantastic and greatly appreciated. (Plus I'll nail the crap out of that "thanks" button.)
**EDIT
Couple of additional thoughts, I was wondering if perhaps the CWM files linked here would work? http://forum.xda-developers.com/showthread.php?t=2127346
Or perhaps I was also thinking that maybe the process used to install CWM Recovery on the Nexus 4 would work as well, considering the devices are so similar.
I'd like to be careful with this and I hope there's some people out there who sympathize with my fear of bricking the phone. I'd like to have a more solid knowledge what what I'm about to do before I go ahead and give'er.
Thanks!

jwenoch said:
Hey folks,
I hate starting new threads but unfortunately I've run out of places to look and the "answers" I've found so far have only further confused me.
I have successfully rooted and unlocked my LG E973 on Bell. My goal is to flash a copy of CyanogenMod 10.1 on to the device, however, I need to install CWM recovery first and I don't know where to start.
I'm new to this and from what I've learned is that I cannot rely on ROM manager as my device isn't fully supported yet, and that I need to find (a specific?) version of recovery files tailored to my device and install them manually to the internal storage, before continuing with ROM manager. (Please correct me if I'm wrong.)
If someone could point me in the right direction, that would be fantastic and greatly appreciated. (Plus I'll nail the crap out of that "thanks" button.)
**EDIT
Couple of additional thoughts, I was wondering if perhaps the CWM files linked here would work? http://forum.xda-developers.com/showthread.php?t=2127346
Or perhaps I was also thinking that maybe the process used to install CWM Recovery on the Nexus 4 would work as well, considering the devices are so similar.
I'd like to be careful with this and I hope there's some people out there who sympathize with my fear of bricking the phone. I'd like to have a more solid knowledge what what I'm about to do before I go ahead and give'er.
Thanks!
Click to expand...
Click to collapse
yes they should work. i have a telus e973 and using cmw v14.4.7 running houstonn 4.1.2 Rom.

gentledroid17 said:
yes they should work. i have a telus e973 and using cmw v14.4.7 running houstonn 4.1.2 Rom.
Click to expand...
Click to collapse
Awesome thanks! So it looks like I'm on the right track.. one other question then if you (or anyone else who might know) would be so kind, How did you manage to install CWM properly onto your device? Using the files in the thread I linked to earlier, I attempted to use a tutorial to install CWM using terminal emulator. (Unfortunately due to my noob status, I can't post outside links)
Unfortunately it didn't work. I received and error on the 5th step telling me that no such directory exists. I assume its probably got something to do with the fact the phone doesn't have an SD card slot. (Or is the internal storage on the Optimus named sdcard? I'll have to check...)
I'm going to do some more searching, you'd figure with everyone running around with CWM on their Optimus G's and no clear instruction on how to do it, it shouldn't be that hard, so I don't know why I'm having so much trouble figuring this out.
Thanks for your patience!

http://forum.xda-developers.com/showthread.php?t=2007961
this should give you cwm if you are rooted.

wargreymon89 said:
http://forum.xda-developers.com/showthread.php?t=2007961
this should give you cwm if you are rooted.
Click to expand...
Click to collapse
I. Am. An. Idiot.
Thank you.
Turns out, considering I had done this already, I had CWM installed all along without realizing it. I'm having a good laugh over here. Thanks everyone for all your help.

Stuck on Samsung boot screen

I rooted my old milestone many years ago but havee been keeping my devices stock ever since, until today that is. Today I decided I wanted to try to root my Samsung SGH-I747M with Telus and everything seemed to start off smoothly. Once installed the SuperSU stopped working. I tried fixs I had read online such as updating the app, but this did not work. I read on a forum that you could flash something to disable know to help fix the problem. When I tried going this avenue I was not able to reboot my phone. I tried restoring from a backup taken before flashing, but I havent done any of this in so long im not entirely sure the backup took properly. At one point I got a message saying no OS was installed but after restoring this seemed to go away. I apparently do not remember anything about rooting from my milestone and am hoping someone may be able to help me get out of this mess. I am currently downloading the stock firmware and I think I will try flashing it tomorrow. I also was hoping someone could point me in the direction of a thread on xda that went into a more detailed explanation of how rooting works, what specifically roms and flashing all is and does. Any help is greatly appreciated.

cdriver said:
I rooted my old milestone many years ago but havee been keeping my devices stock ever since, until today that is. Today I decided I wanted to try to root my Samsung SGH-I747M with Telus and everything seemed to start off smoothly. Once installed the SuperSU stopped working. I tried fixs I had read online such as updating the app, but this did not work. I read on a forum that you could flash something to disable know to help fix the problem. When I tried going this avenue I was not able to reboot my phone. I tried restoring from a backup taken before flashing, but I havent done any of this in so long im not entirely sure the backup took properly. At one point I got a message saying no OS was installed but after restoring this seemed to go away. I apparently do not remember anything about rooting from my milestone and am hoping someone may be able to help me get out of this mess. I am currently downloading the stock firmware and I think I will try flashing it tomorrow. I also was hoping someone could point me in the direction of a thread on xda that went into a more detailed explanation of how rooting works, what specifically roms and flashing all is and does. Any help is greatly appreciated.
Click to expand...
Click to collapse
General section is most likely the best place for that.
Here's a How-to that should get you started: http://forum.xda-developers.com/showthread.php?t=2538991
And here is the Sticky index: http://forum.xda-developers.com/showthread.php?t=1725839 Lots of good guides and info in there!

General section is most likely the best place for that.
Click to expand...
Click to collapse
The Only problem is I already attempted to follow this and my phone will no longer boot up. Also I tried navigating through the stickies. couldn't find much info for my device. I will be trying to flash the stock firmware tonight but I want to have a clear understanding on what flashing is and what the difference is between os firmware kernel and rom and such BEFORE flashing this firmware tonight. I hope someone will be able to help.

cdriver said:
The Only problem is I already attempted to follow this and my phone will no longer boot up. Also I tried navigating through the stickies. couldn't find much info for my device. I will be trying to flash the stock firmware tonight but I want to have a clear understanding on what flashing is and what the difference is between os firmware kernel and rom and such BEFORE flashing this firmware tonight. I hope someone will be able to help.
Click to expand...
Click to collapse
Well that info is already in the Sticky Index. Understanding what you're doing (or about to do) is really important but you gotta start reading, it's all there.
OS, firmware and ROM are the same thing.
When your phone boots, it basically goes: Bootloaders -> Kernel -> ROM (OS).
The kernel has pretty much all the "underground" controls (RAM, Mhz, governor, scheduler, BT, Wifi, etc).
I won't write everything but those are the basics.
Also, having a Canadian variant of the S3 (that's what the M is for), doesn't change much other than flashing bootloaders and stock ROM (which you'll wanna use the Canadian variant bootloaders and Telus ROM for stock). Everything else is basically the same.

Also, having a Canadian variant of the S3 (that's what the M is for), doesn't change much other than flashing bootloaders and stock ROM (which you'll wanna use the Canadian variant bootloaders and Telus ROM for stock). Everything else is basically the same.
Click to expand...
Click to collapse
Sweet I will definitely check that out. So I did flash twrp to my phone. Is it possible that I flashed the version say for the i747 but not the m version and that is why the phone wont move past the samsung screen? Also should I attempt to get rid of twrp before flashing the stock firmware. This should answer all my questions and then I will explore the stickies some more.

cdriver said:
Sweet I will definitely check that out. So I did flash twrp to my phone. Is it possible that I flashed the version say for the i747 but not the m version and that is why the phone wont move past the samsung screen? Also should I attempt to get rid of twrp before flashing the stock firmware. This should answer all my questions and then I will explore the stickies some more.
Click to expand...
Click to collapse
If flashing a stock ROM, flash the Telus one. If flashing a custom ROM, it doesn't matter (I747 or M variant), as long as it's D2LTE.
Your recovery doesn't change anything to flashing with Odin, it will overwrite it.

Flashing the stock firmware fixed my problems. Thanks for all of your help and I will definitely be checking out the links that you sent me before trying to root again tomorrow.

[Q] Bumping????

Hello everyone!
I just don't get it. Can anyone explain to me what's the difference between flashing a bumped rom and flashing the same rom un-bumped? I just don't get the whole point of it! Sorry, but coming from a Nexus device (why have I ever changed!!!) I'm new to these things.
So, other questions would be: what's the point of bumping? What if I don't do it and just go about the usual way: Unlocking the bootloader, rooting and installing a custom recovery and then proceed to flash the appropriate and preferred rom, kernel, etc?
Hope somebody will bear with me and try to explain these things to a newcomer
Thanks

astrovale said:
Hello everyone!
I just don't get it. Can anyone explain to me what's the difference between flashing a bumped rom and flashing the same rom un-bumped? I just don't get the whole point of it! Sorry, but coming from a Nexus device (why have I ever changed!!!) I'm new to these things.
So, other questions would be: what's the point of bumping? What if I don't do it and just go about the usual way: Unlocking the bootloader, rooting and installing a custom recovery and then proceed to flash the appropriate and preferred rom, kernel, etc?
Hope somebody will bear with me and try to explain these things to a newcomer
Thanks
Click to expand...
Click to collapse
Because
1) Bumping is used to trick the bootloader into thinking that the boot.img is authentic and from Official LG Sources
2) Without bumping you could have to constantly run fastboot boot boot.img (an example of this was CM11 when it first started development)
3) Bootloader cant be unlocked at this time so we rely on a bootloader exploit in order to run custom recovery
4) Its all about the authenticity. If the LG bootloader does its security checks and anything fails then the system doesnt boot

Thanks for the very easy tuo understand explanation. I should have thought that the problem was unlocking the bootloader! Guess I'll have to with the Flow and bump my new phone. I wish I asked my Carrier for an HTC M8
Sent from my Xperia Tablet Z LTE using XDA Free mobile app

simple answer: bump is the only way to unlock g3 bootloader.
all roms are bumped whether displaying [BUMPED] or not.

rhystagram said:
simple answer: bump is the only way to unlock g3 bootloader.
all roms are bumped whether displaying [BUMPED] or not.
Click to expand...
Click to collapse
Ok, so by simple logic, once I have installed, either via bump, flashify or ADB a recovery, I can pretty much flash any rom that is appropriate for my model no, isn't it?
So there is one more question I have: what is the purpose of unlocking the bootloader and then what could be the problems if I don't? If everything I flash for this device (TWRP, roms, kernels, etc) is, by default, bumped, what's the purpose of installing bump at all?

astrovale said:
Ok, so by simple logic, once I have installed, either via bump, flashify or ADB a recovery, I can pretty much flash any rom that is appropriate for my model no, isn't it?
So there is one more question I have: what is the purpose of unlocking the bootloader and then what could be the problems if I don't? If everything I flash for this device (TWRP, roms, kernels, etc) is, by default, bumped, what's the purpose of installing bump at all?
Click to expand...
Click to collapse
You're making it so much harder for yourself dude.. There really is only one way to install custom ROMs and that is by Bumping your phone. That's it.
You go here and read the entire topic. Don't miss a single thing.
Then go here and flash the zip for the latest TWRP.
After that you can install any ROM in the OG and Android Development section.
That's all there is to it. You can read in those topics for more information about what they do.

if you dont bump, then you wont have twrp lol.
you cant flash any roms anyway, you'll potentially brick/soft brick your phone.
roms etc are bumped because they have a patch script implanted to run on the phones correctly.

rhystagram said:
if you dont bump, then you wont have twrp lol.
you cant flash any roms anyway, you'll potentially brick/soft brick your phone.
roms etc are bumped because they have a patch script implanted to run on the phones correctly.
Click to expand...
Click to collapse
OK. Got it! It took a while, but I give up!
Thanks for the help. Coming from the most easy to play with phones (only Nexus so far, but I hate the N6), it isn't easy to have to deal with more stuff than usually needed and hence more complications than usually had.
I thought that, after rooting I could flash TWRP via flashify or rom toolbox and then I would have TWRP without BUMP, but it must be that I'm missing something, if you say I MUST bump my phone to install TWRP.
Thanks and see you around

How to bump lg g3

DevilFan14 said:
How to bump lg g3
Click to expand...
Click to collapse
What exactly do you mean "How to bump"??? Bump and loki are bootloader exploits that allowed us to boot TWRP and all the benefits TWRP offers... On the user side of things you don't "Bump" anything- the Roms, Kernels, and recoveries are "pre-bumped" by the developers and 99.9% of the time they will say whether or not it is "bumped" or "lokied" although loki is really outdated and I doubt you'll encounter it. So in a nutshell we(the user) doesn't "Bump" anything and just make sure to really read before flashing
Sent from my DROID RAZR HD using XDA Labs