4.1.2 wifi broken - want to try fastbooting, but want to make sure there's no fix...
#1
Posted 08 April 2013 - 03:05 PM
But I can't do without wifi... so I just wanted to triple check before fastbooting to see if anybody has seen or knows of a fix for this wifi "issue" that seems to be plaguing a small percentage of users.
TIA!
PS - Maxx HD rooted with no system mods, and yes, I already know I shouldn't have taken 4.1.2...
#2
Posted 08 April 2013 - 04:04 PM
With an unlocked boot-loader regaining root should be as simple as flashing a root.zip file.
I would wait for someone with more knowledge to back this up, but it sounds like it should work given what I've read on the subject.
#3
Posted 08 April 2013 - 04:14 PM
Search XDA for chainfire's supersu thread -- its CWM zip works just fine. Tested on both ICS and JB fastboot flashes.
#4
Posted 08 April 2013 - 06:43 PM
If you're rooted on 4.1.2 why don't you just unlock your boot-loader and then re-flash 4.1.2.
With an unlocked boot-loader regaining root should be as simple as flashing a root.zip file.
I would wait for someone with more knowledge to back this up, but it sounds like it should work given what I've read on the subject.
I had in my mind that the fastboot file would've re-locked the bootloader?
I can confirm that works on an unlocked Atrix HD.
Search XDA for chainfire's supersu thread -- its CWM zip works just fine. Tested on both ICS and JB fastboot flashes.
Thanks, but I'm going to just have to hope for an exploit for 4.1.2 in the future. Had to get wifi going so I fastbooted the 4.1.2 file. For what it's worth, it did fix the wifi problem...
#5
Posted 08 April 2013 - 07:08 PM
I can also confirm now that flashing 4.1.2 after the boot-loader is unlocked will not re-lock it. I have been on rooted 4.0.4 for quite some time, so I gave it a try.
I actually edited the xml file and added TWRP recovery to the directory so that when I flashed in rsdlite it automatically installed TWRP instead of stock android. I then pushed supersu.zip to the storage and flashed. I am now unlocked, rooted and on fresh install of 4.1.2.
I wonder if it would be possible if someone could create a modified boot.img that could be flashed on non boot-loader unlocked phones to give others root.
#6
Posted 08 April 2013 - 07:19 PM
I am under the assumption the only way they can re-lock the boot-loader is if they push an update that replaces the boot-loader with a new locked one. Now that we are unlocked though, we can just remove that and flash the rest of the system as normal. I hope that they do not find a way to prevent the new system.img's to be blocked from install on our devices (not sure if that is even possible).
I can also confirm now that flashing 4.1.2 after the boot-loader is unlocked will not re-lock it. I have been on rooted 4.0.4 for quite some time, so I gave it a try.
I actually edited the xml file and added TWRP recovery to the directory so that when I flashed in rsdlite it automatically installed TWRP instead of stock android. I then pushed supersu.zip to the storage and flashed. I am now unlocked, rooted and on fresh install of 4.1.2.
I wonder if it would be possible if someone could create a modified boot.img that could be flashed on non boot-loader unlocked phones to give others root.
Well for my sake, and others in my position now, I hope so
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users