I've been having a few issues with the root and rom as time has went on. First my fingerprint reader went, then I would have random crashing and shutdowns. Those errors began to get more frequent, and now the internal memory card decided it will wipe itself clean. So I'm done with what ever I had installed. According to the phone that was on April 4th.
I've read some confusing stuff on here about rooting and unrooting, and none of the information is the same. I imagine thats because of all the updates the phone has gone through.
I would like to install cm7 or cm9 since it seems much more stable.
Any help at all to even simply unroot the phone would be appreciated. I need full functionality back.
Atrix 4g
android ver. is 2.2.1
kernel ver is 2.6.32.9
Build number is 1.5.7
Rom: GingerBlur
Just wipe data,cache and dalivk from recovery and install which ever rom u want if u have a unlocked bootloader for completely erasing the previous rom u can use fastboot wit these commands.
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
And if u have not unlocked the bootloader check this link first
THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs
terminator1983 said:
Just wipe data,cache and dalivk from recovery and install which ever rom u want if u have a unlocked bootloader for completely erasing the previous rom u can use fastboot wit these commands.
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
And if u have not unlocked the bootloader check this link first
THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs
Click to expand...
Click to collapse
Actually, if you want the cleanest and least likely to cause problems method, you should do a full fastboot wipe prior to installing any new ROM. Just wiping data, cache, and dalvik does not give you a completely clean wipe and prep properly for the new ROM.
If you are updating a ROM from a previous release, you are usually OK with just wiping Dalvik and cache. The dev will normally state what to do in their thread.
Thanks for the replies. How would I be able to check if I've unlocked the boot loader? I did this almost a year ago so I don't remember if I also did that.
21q said:
Thanks for the replies. How would I be able to check if I've unlocked the boot loader? I did this almost a year ago so I don't remember if I also did that.
Click to expand...
Click to collapse
We couldn't unlock the bootloader a year ago. Was around end of June we had this ability.
If ur phone bootloader is unlocked u can see unlocked written on top corner of boot screen logo.
terminator1983 said:
If ur phone bootloader is unlocked u can see unlocked written on top corner of boot screen logo.
Click to expand...
Click to collapse
Not necessarily. If a SBF has been flashed after unlock, the word "unlocked" is not there.
So going off of what you two have said and another thread I looked at. I have time to do this sunday.
First I will unlock the bootloader
then run through these steps
boot to recovery
Wipe Dalvik
wipe cache
factory reset/data
boot into fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot
From here I can then load cm7 rom onto my sd card and install it via recovery?
Also, reading further into cm7, it doesnt support he fingerprint reader or web/lap-top huh. Are there any nightly releases that have it? I've seen ONE, but I've been out of this scene too long to really know what good right now.
21q said:
So going off of what you two have said and another thread I looked at. I have time to do this sunday.
First I will unlock the bootloader
then run through these steps
boot to recovery
Wipe Dalvik
wipe cache
boot into fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot
From here I can then load cm7 rom onto my sd card and install it via recovery?
Also, reading further into cm7, it doesnt support he fingerprint reader or web/lap-top huh. Are there any nightly releases that have it? I've seen ONE, but I've been out of this scene too long to really know what good right now.
Click to expand...
Click to collapse
Download CM7.2 RC1 > http://forum.xda-developers.com/showthread.php?t=1556246. It has full FP reader support, both security and navigation. (No webtop though).
After unlocking the bootloader (assuming you will be following these instructions > http://forum.xda-developers.com/showthread.php?t=1136261) You will need root again (instructions also in the previously linked thread), and then you will want to flash Romracers recovery through fastboot before flashing any ROM >
http://forum.xda-developers.com/showthread.php?t=1204500
After this you will be able to get into recovery and flash whatever you want. There is an automated script here for unlocking the bootloader also located here > http://forum.xda-developers.com/showthread.php?t=1182871.
Been a while since I did all this myself, but I think I covered everything!
Good luck.
***Ignore this post***
So I don't need to run any of those fastboot commands??
And should I update my phone to 2.3.4?
I just updated it to 1.8.3 by flashing the sbf so I've lost root and everything.
I ended up flashing using this method
http://forum.xda-developers.com/showthread.php?t=1138204
I used the sbf that was supposed to already have the bootloader unlocked and the do some things for root.
When I went to install romracers though I was getting the error (180002)
From what I have read that means the boot loader wasnt actually unlocked?
So I'm guess I should flash the regular 2.3.4sbf. Then manually unlocked the bootloader myself and then root?
Or could I still manage with whats currently installed some how?
Again thanks in advance for any advice.
CaelanT said:
Not necessarily. If a SBF has been flashed after unlock, the word "unlocked" is not there.
Click to expand...
Click to collapse
Does it mean u have relocked the bootloader or it is still unlocked ?
Sent from my MB860 using xda premium
Does doing a full fastboot wipe delete the cwm recovery?
arpit85 said:
Does it mean u have relocked the bootloader or it is still unlocked ?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I don't believe it was ever unlocked
When I flashed the sbf via rdslite it would go to 100% but would be stuck saying "in process"
I made a new thread though since my problem is completely different now
http://forum.xda-developers.com/showthread.php?t=1568347
21q said:
I ended up flashing using this method
http://forum.xda-developers.com/showthread.php?t=1138204
I used the sbf that was supposed to already have the bootloader unlocked and the do some things for root.
When I went to install romracers though I was getting the error (180002)
From what I have read that means the boot loader wasnt actually unlocked?
So I'm guess I should flash the regular 2.3.4sbf. Then manually unlocked the bootloader myself and then root?
Or could I still manage with whats currently installed some how?
Again thanks in advance for any advice.
Click to expand...
Click to collapse
If you flashed sbf with rsdlite and text unlocked is gone, thats mean that you have relocked BL.
You can unlock again by flashing via RSDLite this:
ATT ONLY(It works for 4.5.91 and 4.5.141- Tested myself yesterday) - http://diamantephoto.com/pudding.rar
It is from post:
http://forum.xda-developers.com/showthread.php?t=1136261
How can we relock the bootloader?
I am trying to flash a recovery but the recovery seems to need a locked bootloader.
My device came with unlocked bootloader. Before anything I made a complete backup with TWRP (alka). Then my bootloader got relocked and I intended to restore to unlock it officialy. But surprisingly after restore the bootloader was unlocked again. Which partition (of the around 40) which are also shown here holds the locked / unlocked status?
paul_damian said:
My device came with unlocked bootloader. Before anything I made a complete backup with TWRP (alka). Then my bootloader got relocked and I intended to restore to unlock it officialy. But surprisingly after restore the bootloader was unlocked again. Which partition (of the around 40) which are also shown here holds the locked / unlocked status?
Click to expand...
Click to collapse
"Firmware" I think so because while installing the official CM13 we have flash a separate firmware zip. I extracted the zip and there was file named emmc_appsboot.mbn which is the bootloader.
adwait.bhandari said:
"Firmware" I think
Click to expand...
Click to collapse
No, it's not. When I'm restoring the nandroid backup to restore the original state of my device, so that the bootloader is unlocked again, "Firmware" is the only partition I am not restoring (it gives an error, and other users say that it should be skipped).
I took a look at the updater script and the Bootloader file is written to the aboot partition.
http://imgur.com/HqtIlsp
Aha! Next time I will relock the bootloader I will try to restore, for testing, just this partition and then check it's status. Thanks.
Later edit: Did restored only the aboot partition and got a brick
Anyone know how to unlock the bootloader on a Evanpo T95Z?
If you can reboot into bootloader mode than the usual ADB commands should work.
With the OTA firmwares for my X96 this is not possible in any way but thankfully the bootloader here is already unlocked.
Why do you need it unlocked?
I can't boot to bootloader. I want to install TWRP. What brand do you have?
I have a X96 and can't boot into fastboot either.
But I use TWRP from the SD and leave the original untouched.
Just curious, if I flash full stock on my phone after having TWRP, will the bootloader be relocked? And will the OEM unlocked 7 day issue come?
If it doesn't relock, I should be to just flash TWRP again right after? Thanks.