Hello. The subject matter says it all.
I currently have a rooted and unlocked AT&T Atrix on 1.26 version (yeah...still in ice age ) with a locked bootloader. Im with a non-US telco carrier. It came unlocked and rooted so that was great. No hassle but now I have started doing research on custom roms and webtop mods. I am trying to get around the info overload, so pls bear with my questions.
The overall goal is to have a stock/custom rom devoid of all the bloatwares and can run webtop2sd, and if that is not possible then, webtop. Very simple needs.
Option 1
======
To remain on stock rom and update to 1.83 version, and then to install the webtop2sd mod. Ideally I would like to boot off Debian from the microsd card. There was a post in which a forumer mentioned that he was able to "frankenstein" the webtop2sd and webtop mods. Thats great if I understood correctly.
Option 2
======
To update to 4.5.91 (probably a custom rom like Aura) and then install the webtop2sd/webtop mod.
What should be done?
I am going to update 1.26 -> 1.57 -> 1.83 -> 4.5.91 via system update. (which means I now have to signed with moto account...yes I have not as I read that there were some privacy issues.)
Through the update process, I would lose root. To keep everything clean, I am going to go through factory reset and then perform the update.
Once I am in 1.83 or 4.5.91, I will apply the root and unlock the bootloader. Which is the best way to go about this? Should I just follow the instruction here or this way. Or is there any other better way?
This is all I have for now until I install the webtop mod or the custom rom...
update your phone to wherever you want it at, then use this script to unlock the bootloader:
http://forum.xda-developers.com/showthread.php?t=1182871
after that, you can easily root your phone using the preinstall method found here:
http://forum.xda-developers.com/showthread.php?t=1138204 (second post)
if you update to 4.5.91 though, as you attempt to unlock the bootloader you will get a semi-hard brick, just have it boot up into fastboot mode and continue using the script. easy as pie!
I never got a semi-hard or *soft* brick from unlocking but that's just cause I must love to eat pudding =D . Do all the OTA updates, unlock / root, and then install the 2.3.4 fruitcake and install webtop. Best option by far, IMO, as far as the ease of transition goes. Should be cake. That's what I did and as long as you don't RSD lite with an .SBF back once on 2.3.4 OTA yer good to go.
eat yer fruitcake once updated to 2.3.4 OTA *stock gingerbread*-http://forum.xda-developers.com/showthread.php?t=1163009
Install a custom kernel if ya wanna overclock or undervolt, I would personally suggest Faux123's. -http://forum.xda-developers.com/showthread.php?t=1156040
aaand freeeze all that bloatware!-http://forum.xda-developers.com/showthread.php?t=972459
I read that its easier to update via SBF than OTA? What have your experiences been so far?
Alcapone263 said:
if you update to 4.5.91 though, as you attempt to unlock the bootloader you will get a semi-hard brick, just have it boot up into fastboot mode and continue using the script. easy as pie!
Click to expand...
Click to collapse
Maybe I should try to unlock it now... And then update.
tech_girl said:
I read that its easier to update via SBF than OTA? What have your experiences been so far?
Click to expand...
Click to collapse
well, i can't find it anymore but there is an SBF in the development forum that will allow you to update to 2.3.4 android without getting the brickable bootloader, but i personally don't see a point in using SBF. it's not meant for the end user, and using it can be risky.
SBF flashing is faster i believe, but as i said can also potentially harm your device if you're unsure of what you're doing.
SamCripp, one of the most esteemed devs here, suggests for the average person to completely stay away from sbf flashing after you've unlocked your bootloader unless you absolutely have to use it for something.
remember though, if you use the OTA update you CANNOT downgrade your device through SBF flashing, you HAVE to use the fruitcakes method. it WILL brick your device to downgrade, but only with the OTA update.
EDIT: and it's a semi-hard brick, it doesn't hurt your device in the least. you might panic at first, but it's as simple as booting into fastboot mode and finishing the script. or if you're more tech inclined, you can just do the fastboot oem unlock command through fastboot.
Phalanx7621 said:
....
eat yer fruitcake once updated to 2.3.4 OTA *stock gingerbread*-....
Click to expand...
Click to collapse
Alcapone263 said:
......
remember though, if you use the OTA update you CANNOT downgrade your device through SBF flashing, you HAVE to use the fruitcakes method.....
Click to expand...
Click to collapse
Fruitcakes??? All this jargon.... Hmmm...gotta check this out.
http://forum.xda-developers.com/showthread.php?t=1163009
yep, Fruitcakes. it's a CWM alternative to sbf flashing, much safer since it doesn't edit the bootloader at all, so there's no risk in hard bricking your device.
after you unlock your bootloader, you should install Romracer's CWM recovery here: http://forum.xda-developers.com/showthread.php?t=1204500
do all of your flashing through CWM after you unlock your bootloader, just remember to clear cache/dalvik/data between each ROM or you might get stuck in a bootloop.
Ok...CWM sounds more familiar....
If I understand correctly, I actually dont have to go via OTA. As long as I have the img file for flashing to each version, I could just use the CWM and not via OTA, right?
tech_girl said:
Ok...CWM sounds more familiar....
If I understand correctly, I actually dont have to go via OTA. As long as I have the img file for flashing to each version, I could just use the CWM and not via OTA, right?
Click to expand...
Click to collapse
well, you have to have an unlocked bootloader to get CWM. and to unlock your bootloader, you have to update to 1.8.3 or later.
after you unlock your bootloader, you can install CWM and proceed to just use CWM for your flashing needs.
i repeat again though, after you unlock your bootloader you should stay away from SBF flashing altogether. it's the quickest way to brick your device.
Alcapone263 said:
well, you have to have an unlocked bootloader to get CWM. and to unlock your bootloader, you have to update to 1.8.3 or later.
after you unlock your bootloader, you can install CWM and proceed to just use CWM for your flashing needs.
i repeat again though, after you unlock your bootloader you should stay away from SBF flashing altogether. it's the quickest way to brick your device.
Click to expand...
Click to collapse
+1
Once you unlock and get CWM installed its just a case of wiping the device and flashing zip files.
Yep after unlocking and getting rom racers cwm in, you get to have lots of fun and almost zero chance of hard bricking. Make sure you understand the pudding part. After you unlock throw rsd lite away.
After updating to 1.83 and unlocked, can I immediately installing a GB custom rom like Aura or Alien? Or do I need to update to 4.5.91 stock before I can install a custom rom? Which I assume is pre-rooted, which mean I dont have to root it..
tech_girl said:
After updating to 1.83 and unlocked, can I immediately installing a GB custom rom like Aura or Alien? Or do I need to update to 4.5.91 stock before I can install a custom rom? Which I assume is pre-rooted, which mean I dont have to root it..
Click to expand...
Click to collapse
You should be able to start flashing if you used pudding. No need to upgrade to .91 stock. I didn't. I think most roms are pre rooted now. Not that the rooting method was hard for the atrix.
I voided my warranty.
pukemon said:
You should be able to start flashing if you used pudding. No need to upgrade to .91 stock. I didn't. I think most roms are pre rooted now. Not that the rooting method was hard for the atrix.
I voided my warranty.
Click to expand...
Click to collapse
Yep thats how it works. once BL unlocked and CWM installed you can flash anything, including yes .91 stock.
Note that .91 stock OTA is not only the operating system but also modifies the bootloader hence all the hard brick warnings about flashing sbfs. When you flash zip files you don't touch the bootloader, so there is no chance of hard bricking. i.e. if you flash .91 stock from zip file from CWM as opposed to OTA, you get only the OS, not the bootloader update (which doesn't matter ).
Sorry for the noob question, but do these ROMs require the phone to be rooted?
Yes, all ROM's require the phone to be rooted.
yo
Start out with HTC Unlock. Lots of info on this site about it.
Then install a custom rom. It will already be Rooted,
After you've learned more, then you make it S-0ff.
Then you can go backward and forward in radio and other
options without worries.
hellhawk741 said:
Yes, all ROM's require the phone to be rooted.
Click to expand...
Click to collapse
Wrong. You don't need root. You need to unlock the boot loader. All instructions for that are in HTCDev.com
you need to Unlock your bootloader first in order to flash a Recovery like CWM or AmonRA which will then allow you to flash/install rooted roms.
Note: if you are on Gingerbread and are going to flash an ICS rom, PLEASE download the required kernel they provide for you to flash as well as the ICS rom. but kernels are flashed through the bootloader/hboot and not in recovery. unless your S-off. if your'e S-on, flash kernels in bootloader.
what does that mean. apparently there is a technique to root the phone and put CWR on it to flash things. but why is unlocking the bootloader so important.
kidhudi said:
what does that mean. apparently there is a technique to root the phone and put CWR on it to flash things. but why is unlocking the bootloader so important.
Click to expand...
Click to collapse
Unlocked Bootloader allows one to flash custom Kernel/ROMs.
If you don't know what flashing means or don't care about anything custom, then you're all good to go...
Methods have been discovered so far to boot custom recoveries, root, and boot custom kernels. Still cant flash a new bootloader. What that basically means as far as I understand it, is that while we can run custom kernels, etc, the exploit can be quickly patched by an OTA, and anyone using said method will not be able to take OTA updates.
Its a workaround, not a polished solution (yet), but the devs are doing amazing work, and if you care about the cause then be sure to donate to them!
I thought it was necessary to unlock the bootloader on android phones before i could root them and flash different roms. A buddy of mine had rooted his old s3 but forgot to unlock the bootloader, so when he tried restarting it, it soft bricked. For the longest time I thought you had to unlock the bootloader then root the phone in order to flash custom roms, have I been wrong all this time?
Think of the Loki workaround as a way to trick the bootloader into flashing improperly signed files. Its like using a credit card on the bolt of a locked door. The door is still locked but you get through anyway.
brizey said:
Think of the Loki workaround as a way to trick the bootloader into flashing improperly signed files. Its like using a credit card on the bolt of a locked door. The door is still locked but you get through anyway.
Click to expand...
Click to collapse
And what are the risks of using the loki tool if you use it correctly? if there is an OTA update to the phone, will it mess it all up?
You don't you the tool...the developers do. And technically, it is only used for flashing a recovery and flashing ROMS with the recovery. You can root without unlocking the bootloader because there is an pre-release official rootable kernel than can be flashed with Odin. It flashes because it is legit.
So I should be able to just go to the how to root page on here http://forum.xda-developers.com/showthread.php?t=2290798 and follow the instructions and flash one of the roms as usual?
yes,go ahead
Im sorry if this has been answered in other threads im simply trying to help a friend out with rooting and possibly unlocking the boot loader? Can someone point me in the rite direction? It would be most appreciated
I would check the Verizon LG G3 forums where there are many instances of your questions having been already thoroughly answered.
What you will find is that you must be on v10b firmware, which you can downgrade to using either the .kdz or the .TOT method, then you can root v10b (only) with StumpRoot, or ioRoot, or PurpleDrake, before the phone updates back to v12b. With SuperSu in survival mode root can be retained through either of the current OTA updates (which provide very little enhancement beyond patching root exploits), so far, and with root you can install a specially modified TWRP recovery which will allow the flashing of unsigned kernels and roms.
There. You are on your own from hete on.
Sent from my VS985 4G using Tapatalk
use flashify to install the bumped version of twrp (get it from the original development section). Worked like a charm. Plenty of bumped roms to grab in the dev section.
gothicasshole said:
Im sorry if this has been answered in other threads im simply trying to help a friend out with rooting and possibly unlocking the boot loader? Can someone point me in the rite direction? It would be most appreciated
Click to expand...
Click to collapse
There is no unlocking of the bootloader. Bumping doesn't unlock the bootloader. However, it fools the phone into allowing the flashing of custom ROMs and kernels without unlocking the bootloader. Basically, the phone "believes" that whatever is being flashed (via TWRP) is acceptable and allows the image to pass the "security check" that is done when flashing. It's the same thing as IF the bootloader were unlocked, but in reality, it isn't unlocked. It's a security exploit, kind of like rooting this phone is a security exploit.
However, a quick OTA patch from Verizon or LG could make either or both no longer work. In fact, some OTAs have fixed the root exploit on some models, so you have to flash back to a previous version to root.
You have to root first, then you can flash TWRP.
As stated, there are plenty of FAQs in the general G3 section that help explain all of this.
OK thanks guys. Um just used to seeing a sticky on root under original android development I have no idea what firm ware he's running ik how restrictive big red can be at&t is no better but that's why when they offered a nexus I went and grabbed it
He's wanting a lollipop rom
gothicasshole said:
He's wanting a lollipop rom
Click to expand...
Click to collapse
Go here which gives a whole list of things, including how to root, how to bump, how to flash, etc:
http://forum.xda-developers.com/lg-g3/help/help-thread-lg-g3-question-t2947298
It's where I went before I got this phone to be sure I could do all the things I wanted to.
Thank you
I'll definitely refer him