I've never had a phone with a locked bootloader so I have a question
If I edit/replaces apps in the /system without unlocking the bootloader, everything goes to hell right?
dre89 said:
I've never had a phone with a locked bootloader so I have a question
If I edit/replaces apps in the /system without unlocking the bootloader, everything goes to hell right?
Click to expand...
Click to collapse
No you only need to be rooted to mess with system apps, but that doesn't mean you can't easily screw stuff up. Unlocking the bootloader is for flashing new rooms and kernels.
Sent from my MB855 using xda premium
Cool thanks for the info
Sent from deep space on a Photon
Related
so i'm about to install 4.5.91 in a few hours.. gonna backup lots of data first..
im trying to avoid bootloader unlocking for the meanwhile cause of the warranty issue and the fact u cannot re-lock.
anyway i just grabbed ATT-2.3.4_Pudding_preroot.rar and ill flash it over the gladiatrix 1.8.3 i have currently on the device (will it work?)
later i intend to use the preroot method and root and of course.. install a recovery BUT.. since the new recovery needs an unlocked bootloader.. ill use the previous one with the battery charging hack
so.. what do you think guys? will it work?
p0xer said:
so i'm about to install 4.5.91 in a few hours.. gonna backup lots of data first..
im trying to avoid bootloader unlocking for the meanwhile cause of the warranty issue and the fact u cannot re-lock.
anyway i just grabbed ATT-2.3.4_Pudding_preroot.rar and ill flash it over the gladiatrix 1.8.3 i have currently on the device (will it work?)
later i intend to use the preroot method and root and of course.. install a recovery BUT.. since the new recovery needs an unlocked bootloader.. ill use the previous one with the battery charging hack
so.. what do you think guys? will it work?
Click to expand...
Click to collapse
I would assume the att-2.3.4_pudding_preroot already is preunlocked (hence the pudding) which defeats your purpose?
Also, what would the purposed of the old plugged in Recovery? It won't install any of the new ROMs and I don't think the nandroid back up really works that well.
not quite.. its just have the "pudding" in it.. you'll have to perform an unlock with fastboot to void warranty.
p0xer said:
not quite.. its just have the "pudding" in it.. you'll have to perform an unlock with fastboot to void warranty.
Click to expand...
Click to collapse
Ok, so the other question - point of the old recovery? Just to help you wipe data/cache/batterystats?
The old recovery will still save him... You shouldn't need to be unlocked to do that.
Mgamerz said:
The old recovery will still save him... You shouldn't need to be unlocked to do that.
Click to expand...
Click to collapse
save him from what and how? other than wiping data... he can't flash anything that can save him...
Indeed I think he can backup with old tenfar's recovery. The problem is that the sfb he wants to flash is the incorrect one, you can't use the prerooted without unlock the BL at least for the version I know. In other hand The update process is kinda complicated without unlocking the BL, if you do it OTA you will also update the BL and that one can't be unlocked now also could leave you bricked if flash back to 1.8.3.
Sent from my MB860 using XDA App
http://forum.xda-developers.com/showthread.php?t=1163342
gives stock 2.3.4 without touching bootloader.
you should be able to use preinstall method to root then i think.
He needs to unlock the BL to flash kennp image files.
Sent from my MB860 using XDA App
Kelvin0007 said:
He needs to unlock the BL to flash kennp image files.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
yeah my bad.
It disables the auto brightness yay. Unlock bootloaders do not update will brick ur plat.
should be in the general section. good man anyways
Hasn't this been live for a few days and there is already a thread on this in general.
Sent from my R800x using Tapatalk
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
for serial, it really bricks your phone! I had to get a replacement because of this crap. Do not do it...however, now that i got a replacement for that phone, i can say it is better. I dont know why i am still writing in caps. I am yelling the first sentence though. Take it seriously!!! @@@@@@@@@@@@@@@@@@@@@@@@@@@@@
doua27 said:
it disables the auto brightness yay. Unlock bootloaders do not update will brick ur plat.
Click to expand...
Click to collapse
Cubsfan3493 said:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
for serial, it really bricks your phone! I had to get a replacement because of this crap. Do not do it...however, now that i got a replacement for that phone, i can say it is better. I dont know why i am still writing in caps. I am yelling the first sentence though. Take it seriously!!! @@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Click to expand...
Click to collapse
I forgot to relock and it did brick but following the UNBRICKING thread i got it back working. RELOCK bootloader then update then UNLOCK and REROOT all works fine now of course after root probably best to relock bootloader anyway just incase.
Post the ftf file please
Sent from my R800i using XDA App
Cat_On_Droid said:
Post the ftf file please
Sent from my R800i using XDA App
Click to expand...
Click to collapse
It's in the first post of the relock thread
Not the relock one, the 2.3.4 r800x ftf
Sent from my R800i using XDA App
Once we have an .ftf of the new 2.3.4 VZW OTA update we will be able to flash that via fastboot, and re-root while keeping our bootloader unlocked?
With flashtool not fastvoot, and yes
Sent from my R800i using XDA App
Yeah, flashtool. Haha.
So I relocked my bootoader, and now I want to unlock it again, it fail. I even tried to just use fastboot commands to boot into recovery and it comes back as
failed phone must be rooted." I did use flashtool to reflash back to stock r800x firmware 2.3.2 I dont know what it s going on. I have flashed my phone before and unlocked the bootloader but now it wont.
I relocked my bootlaoder to ota to 2.3.3. but decided to go back to 2.3.2. for the time being.
Any ideas why this is happening?
tried to unlock the bootloader and it fails everytime. Using fastboot commands for recoveryPLAY comes back with a "phone must be rooted" line.
Is it possible to get temp root only in such a way it doesn't mark the bootloader as TAMPERED?
For what it's worth, there is only a handful of reasons I would ever need root access and quite honestly I don't see the need to be rooted 100% of the time.
However, I don't feel the need to have to unlock the entire bootloader from HTC Dev just to install an APK or two.
Thanks for any pointers!
ttmcmurry said:
Is it possible to get temp root only in such a way it doesn't mark the bootloader as TAMPERED?
For what it's worth, there is only a handful of reasons I would ever need root access and quite honestly I don't see the need to be rooted 100% of the time.
However, I don't feel the need to have to unlock the entire bootloader from HTC Dev just to install an APK or two.
Thanks for any pointers!
Click to expand...
Click to collapse
You only need to unlock the bootloader if you want to flash custom roms and such. If you just want root access for apps just use zedomax's root and dont unlock the bootloader. You only get the tampered messages if you unlock the bootloader.
njfoses said:
You only need to unlock the bootloader if you want to flash custom roms and such. If you just want root access for apps just use zedomax's root and dont unlock the bootloader. You only get the tampered messages if you unlock the bootloader.
Click to expand...
Click to collapse
Actually that's wrong. They're two different things. If you root, it'll show tampered, whether unlocked or not. Locking or unlocking will not effect tampered status. Any root will show tampered. It goes away if you use RUU.
To answer the question asked, no. At the current time it is not possible to root without tampered bootloader
Sent from my EVO using XDA
chickut123 said:
Actually that's wrong. They're two different things. If you root, it'll show tampered, whether unlocked or not. Locking or unlocking will not effect tampered status. Any root will show tampered. It goes away if you use RUU.
To answer the question asked, no. At the current time it is not possible to root without tampered bootloader
Sent from my EVO using XDA
Click to expand...
Click to collapse
Yea i didnt word it very well. I assumed the reason the op was asking is so he could get back completely to stock if need be. If he only roots and then runs the ruu he would be back to stock. Thanks for clearing it up.
Thanks for the info - I didn't understand the mechanism that triggers the bootloader to show tampered.
Ultimately, I was looking into determining whether or not ICS encrypted the mail (not gmail) database, regardless of the device itself being encrypted or not.
OK I am just looking for opinions. I can purchace an atrix in a boot loop for $100 US. This is without knowing if i can go into recovery or what firmware is on it. I have unlocked used custom roms and recoveries and stock recovery before. I recently got a new locked down atrix and am looking for one i can unlock. Just asking opinions as to likelihood of fixing. Thank you in advance for info
affiatic said:
OK I am just looking for opinions. I can purchace an atrix in a boot loop for $100 US. This is without knowing if i can go into recovery or what firmware is on it. I have unlocked used custom roms and recoveries and stock recovery before. I recently got a new locked down atrix and am looking for one i can unlock. Just asking opinions as to likelihood of fixing. Thank you in advance for info
Click to expand...
Click to collapse
if the only problem its the bootlop i say yes. a bootlop its a very easy problem to fix
thought about it. with the issues i have had with 3 other atrixes risk of other problems is high so i think i will pass
I would think go into recovery and flash a new ROM would do the trick to fix it.
Sent from my MB860 using xda app-developers app
Deggy said:
I would think go into recovery and flash a new ROM would do the trick to fix it.
Click to expand...
Click to collapse
That would be assuming it has an unlocked bootloader and a custom recovery already. But what if it isn't so? What if it has a LOCKED (meaning unlockable) bootloader? He did say he knows nothing about its overall condition, just that it's stuck in bootloop.
ravilov said:
That would be assuming it has an unlocked bootloader and a custom recovery already. But what if it isn't so? What if it has a LOCKED (meaning unlockable) bootloader? He did say he knows nothing about its overall condition, just that it's stuck in bootloop.
Click to expand...
Click to collapse
True. Would it be possible to continue the unlocking process at this point?
Sent from my MB860 using xda app-developers app
Deggy said:
True. Would it be possible to continue the unlocking process at this point?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Flash SBF files maybe would solve this....
Sent from my MB860 using xda premium
I second the sbf idea... even without an unlocked bootloader officially signed sbf's will work unless the internal storage is dead, which still is fixable by using the external storage. (but i doubt its dead)
EDIT: Be very careful while flashing sbf's though. Make sure the cable and everything is secure, your phone is charged, computer securely plugged in, etc... if something goes wrong it could hard brick, but that is not too likely as long as you take precautions.
I'm thinking of unlocking my bootloader. I've checked that it is possible for me, but I just have a couple of concerns about doing so and wanted to ask about them here, before I proceed with the unlocking procedure.
First off, I remember reading that with an unlocked bootloader, you are able to brick the phone completely, is this correct? How vulnerable will the phone be and is it easy to brick, will something go wrong easily?
Secondly, can you install roms that have been developed for the locked bootloader even when you have an unlocked bootloader?
Hmm... unlocking the bootloader voids my warranty but I remember that there were tutorials somewhere to re-lock the bootloader. If I lock it again, will my warranty be back to normal? (Are there traces that I have messed with the bl?)
I think that's all. Is there anything else that I should keep in mind before going ahead with the procedure?
Thank you in advance for your responses! Happy Thanksgiving!
Sent from my Xperia U using xda app-developers app
There will be no traces only Samsung traces such things
You will not brick it but you should follow all steps correctly
Sent from my Xperia U using xda premium
If you follow all steps, you cant brick your device
With unlocking, you loose data - something like factory reset - so save your messages and contacts.
With data, you will loose DRM keys too - relocking wont give back these, keys are lost forever.
But with unlocked booloader, you can install new kernels..
And roms for locked bootloader? For example, there is cm9 for lockedBL and for unlockedBL - i would not worry about this.
Sent from my XGO using fingers