628 replies to this topic

[mttw2007]

I spend HOURS reading through all of the repys seeing if I could do this without having to make an account.

Then I Man-ed up and spend 2 mins making an account and it took me 30 seconds to complete the root process.

 

I had no idea that when you guys were talking about making changes, they were all being done to that first post already.

 

Fantastic work!!!

You should put a comment on the first post saying that it was recently updated and it worked as of 10/27/13 @ 11:30 and that all you have to do is get an account.

 

 

Thank you so much!

[SamuriHL]

Please Login or Register to see this Hidden Content

 

We do NOT know if this root exploit will work with this new update.  It will need the new boot.img from the update to be put in the boot_new directory overwriting the old one, but, we have no idea if that'll still work.

 

YOU HAVE BEEN WARNED

[jameskirl]

Some help please for XT926 on 9.18.79

I followed the instruction in the OP including saving the zip and unloading 

 

I seem to be getting stuck at "sending 'boot' (10240 KB)..." 

 

[*] Press enter to root your phone...

Press any key to continue . . .

[*]

[*] Waiting for device...

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

[*] Device found.

[*] Rebooting to AP Fastboot mode...

[*] Checking for system.img or system.img.ext4 ...

[*] Flashing old boot.img

< waiting for device >

sending 'boot' (10240 KB)...

 

 

 

The screen on the device shows the following

Device is LOCKED. Staus COde: 0

Battery: OK

Transfer Mode: USB COnnected

Fastboot Reason: Flash Failure 

usb connected

 

 

Heart pounding a little i disconnected and got back to Recovery Mode and did a normal powerup.

 

Any ideas?

 

thanks a lot

[SamuriHL]

USB port isn't right.  Use a different one.  Make sure it's not a USB 3 port.

[jameskirl]

Excellent - thanks a lot - changing USB worked thanks. Root successsful.

 

A separate noob question - i wanted to try some ROMS - do i need the bootloader,

I was looking at the 4,3 PACMAN ROM and i can't find an answer. EDIT - Found the answer - i can use ROM with safestrap but only for stock 4.1.2 

 

 

[*] Rooting phone...

[+] This may take a few minutes.

[+] Success!

[*] Cleaning up...

[*] Exploit complete. Press enter to restore boot.img...

Press any key to continue . . .

[SamuriHL]

For rom flashing you need to be unlocked.  Unless you have safestrap installed, then you can use safestrap roms.  And no, you can't unlock at this point.

[jameskirl]

Thanks again

[sgpapesh]

Lost root when I received the new 9.18.94/9.30.1 update that Verizon just released. 

Tried using your motochopper 1.3. This is what happened.

[*] Device found.

[*] Rebooting to AP Fastboot mode...

[*] Checking for system.img or system.img.ext4 ...

[*] Flashing old boot.img

< waiting for device >

sending 'boot' (10240 KB)...

OKAY [  0.780s]

writing 'boot'...

Preflash validation failed

FAILED (remote failure)

finished. total time: 0.911s

[*] Rebooting...

rebooting...

 

 

Please assist.

[SamuriHL]

There is no assistance.  I posted "YOU HAVE BEEN WARNED" for a reason.  It doesn't work. To fix your error you're going to have to flash the boot.img again from your update.  I wish people would take my warnings seriously before just doing things...

[SamuriHL]

Please Login or Register to see this Hidden Content

 

We do NOT know if this root exploit will work with this new update.  It will need the new boot.img from the update to be put in the boot_new directory overwriting the old one, but, we have no idea if that'll still work.

 

YOU HAVE BEEN WARNED

 

And I quote myself.  People on locked phones should not have been the ones to test this...

[livinginkaos]

Holy Cow.... Flashing stuff like this is dangerous too.  That FXZ that's been floating was modified - a big clue that it should be left alone until tested.

[CellZealot]

So, for the record, this update is a " Do NOT Take under any circumstances for rooted locked users!" PSA status update!

Just sayin'

[SamuriHL]

So, for the record, this update is a " Do NOT Take under any circumstances for rooted locked users!" PSA status update!

Just sayin'

 

Great minds think alike.  I've, uh, updated the OP with a small warning.  

[johnthehillbilly]

So, for the record, this update is a " Do NOT Take under any circumstances for rooted locked users!" PSA status update!

Just sayin'

Indeed CZ!!!

"The force is strong with this one..."

[icefloe01]

My phone has not notified of me of an available update yet. I told it to check and it says it's up to date but I'm still on 9.18.79. So when it finally says the update is ready I guess I'll be hitting the "do not update" button every 12 hours until there is an updated root tool. Unless there is a way to protect root?

[SamuriHL]

Freeze the updater so it doesn't look for the OTA.  Until a new root method is found, it's not a safe update to take.  

[icefloe01]

Posting through the phone is so flippin' slow lol. I don't have the donate version so I reckon I'll have to settle for force stopping it for now.

[icefloe01]

Stupid double posting.

[SamuriHL]

Posting through the phone is so flippin' slow lol. I don't have the donate version so I reckon I'll have to settle for force stopping it for now.

You mean of tibu? There are other ways to do it. You could rename the updater apk and reboot. That should do it.

Sent from my Xoom using Tapatalk 4

[icefloe01]

Cool, thank you for that. I renamed both the blurupdater_vzw.apk and blurupdater_vzw.odex files by adding _bak immediately after the vzw in the file name.