Database Info

[ROM] New stock Rom DEFY JRDNEM_U3_2.51.1 UK

New official version stock English rom for UK v2.51.1 released.
DOWNLOAD: Defy Rom v2.51.1

thanks, but where can we find the changelog of this new rom ?

Great! Will give it a try.

might try this tomorrow, although I can't see it being anything major, at the end of the day its not been push OTA as an update yet. I just tried the supposedly "no blur" firmware too and there was still loads of blur on it!

it is unrootable for the moiment.

Are z4root (or other rooting methods) and tenfar's recovery working with this ROM? 'Cause someone in another topic said, that he flashed this ROM, and now he can't flash back anything older than this. (http://forum.xda-developers.com/showpost.php?p=10023019&postcount=7)
And stuck with this ROM, without root and recovery, would be a huge pain in the *ss.
Edit: I think I got my answer from bihariel's post.

TPGamer said:
Are z4root (or other rooting methods) and tenfar's recovery working with this ROM? 'Cause someone in another topic said, that he flashed this ROM, and now he can't flash back anything older than this. (http://forum.xda-developers.com/showpost.php?p=10023019&postcount=7)
And stuck with this ROM, without root and recovery, would be a huge pain in the *ss.
Edit: I think I got my answer from bihariel's post.
Click to expand...
Click to collapse
i don´t know, but i have the "deblured" 2.34.1 firm rooted with z4root and with the clockwork recovery working

Thanks, have installed and its a nice improvement.
Not a giant leep but more of a polish. I must be one of the few people that likes the email client in motoblur.

i aint going anywhere near this it its not rootable then - there nothing wrong with 2.21 imo. And I like the blur email app too lol

If this rom isn't rootable, doesn't that mean that the guys at motorola "fixed" the exploit, that we used, to get root access (and because of that, we need to find another exploit)?

the problem is that you can not flash any older than this and without root you can not flash custom recovery and can not restore nand backup.
if you flash older the phone wont boot.

Yep now unable get root access. Oh well

im stuck on this UK rom too! im not giving up so easy though... just need root and we are good.

TPGamer said:
If this rom isn't rootable, doesn't that mean that the guys at motorola "fixed" the exploit, that we used, to get root access (and because of that, we need to find another exploit)?
Click to expand...
Click to collapse
i don't think so, because 2.34.1 central europe firm, wich also was uploaded today, is rootable and keeps clockwork mod recovery working

andyirons said:
i don't think so, because 2.34.1 central europe firm, wich also was uploaded today, is rootable and keeps clockwork mod recovery working
Click to expand...
Click to collapse
we need another exploit for this rom atleast

jboogie3 said:
im stuck on this UK rom too! im not giving up so easy though... just need root and we are good.
Click to expand...
Click to collapse
I´ve just flashed back from 2.34.1 to 2.21.0 with no major problem.
Looks like 2.51.1 UK comes with a secret within.

jboogie3 said:
we need another exploit for this rom atleast
Click to expand...
Click to collapse
yes, indeed

ya... moto patched it.. my devices goes offline after doing the - ./rageagainstthecage-arm5.bin using the droid2root method... if only it could stay online then we could have root

what the fnck....I just flash the 2.51 two hours ago. i've try atleast 3 method to root this ...all failure....Fnck moto.....

see what they did is baited you in with "noblur" and now your stuck without root!

Unbricked TF101, but no Updates?

Hey,
My TF101 got bricked by a simple reboot - "encryption unsuccessful" splash screen.
I used the nvflash-package from the devel-section "[Tool] Nvflash unbricking released!" for getting back a fresh, clean install of 3.2.1, which seems to work well.
Sadly, no OTA-Update to ICS is found and no microSD-Update is recognized.
Wipe, another cold-boot tried.
Q:
nvflash repartition and format - thus there couldn't be hassle with my old "broken" Android, right?
Q2:Anyone has an idea why updates dont work? Within the thread mentioned above I found some posts about updates which where recognized.
Searched a lot but nothing specific to the nvflash image solution...
BR / Adarof

NvFlash the RougeXM touch recovery CWM and use that to flash a new ICS firmmware/ROM. That's probably the easiest route to take. You can flash total stock that overwrites the custom recovery if you'd like too. Should fix your ota problem too.

removed

Okay, I have flashed ww-9.2.1.11-CWM-full-rooted.zip.
Wipeing everything tried.
But still no updates...
I found http://forum.xda-developers.com/showthread.php?t=1655976, which are the same log-entries like I found
But no luck on googling further on

If you have anything but a stock recovery, you will not get an OTA. You need to here to get the stock recovery and flash it through CWR. Then when you boot to recovery, using the power+vol down wait to see the text at top right corner and then hit volume up, method, you'll see an android laying on his back with a ! above him. This is stock recovery. Should be able to push OTA through settings after this.

Wohu - Thanks, thats one of the very gernal infos I missed :-/
I tried your mentioned tutorial. The process itself seems to be fine.
But...still no updates (it takes ages for the 1st update-check and is very fast for the 2nd and ongoing checks)
I'm from Germany, thus I would expect to require a firmware and recoveryimage for DE but the tutorial just links a WW for firmware and just US for reecovery?
Well ... DE has gone to WW since .21, thus I tried ... but the process uses a repacked Android3, thus I should care about DE ?
Might this be the reason? Is there a repacked-CWM-enabled firmware-image with recovery for DE?
Thanks again so far!
BR / Adarof

adarof said:
Wohu - Thanks, thats one of the very gernal infos I missed :-/
I tried your mentioned tutorial. The process itself seems to be fine.
But...still no updates (it takes ages for the 1st update-check and is very fast for the 2nd and ongoing checks)
Click to expand...
Click to collapse
When the file goes to update, it will fail if there are any apps missing from /system/app that ASUS put in there. There is a checker that looks for these app. If you deleted any of these or any were deleted in the CWR version you flashed earlier, you'll have to replace them before the update will install.
adarof said:
I'm from Germany, thus I would expect to require a firmware and recoveryimage for DE but the tutorial just links a WW for firmware and just US for reecovery?
Click to expand...
Click to collapse
All you need from that link I posted above is the SURecovery image and nothing else. You can get the firmware.zips from Asus directly. The SURecovery is universal, meaning it will work no matter what region you are in. It is the ROM/Blobs that are region specific. Don't forget that if you download one from the Asus site, that you need to extract it first and then push the zip that was inside the original file you downloaded.
So it would look like this WW.zip->extract->firmware.zip<<<---This is your ROM
adarof said:
Well ... DE has gone to WW since .21, thus I tried ... but the process uses a repacked Android3, thus I should care about DE ?
Might this be the reason? Is there a repacked-CWM-enabled firmware-image with recovery for DE?
Click to expand...
Click to collapse
Not sure about these questions.

Woodrube said:
When the file goes to update, it will fail if there are any apps missing from /system/app that ASUS put in there. There is a checker that looks for these app. If you deleted any of these or any were deleted in the CWR version you flashed earlier, you'll have to replace them before the update will install.
Click to expand...
Click to collapse
Okay, I havent known this either...
Is there a list of asus-default installed apps? I havent found :/
Woodrube said:
All you need from that link I posted above is the SURecovery image and nothing else.
You can get the firmware.zips from Asus directly.
Click to expand...
Click to collapse
SURecoverty means the USRecovery.zip, right?
So, in summarize
1) Rogue XM Touch recovery via nvflash from http://forum.xda-developers.com/showthread.php?t=1446019
2) Use RogueXM to flash original asus-firmware (decompressed download archive)
3) Use RogueXM to flash USRecovery.zip from http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
Am I right?
...on 2) I get
Code:
assert failed: write_raw_image("/tmp/blob","staging")
E: Error in /sdcard/WW_epad-user-9.2.1.24.zip
(Status 7)
Installation aborted.
...but I could install the repacked-8.2.3.13_WW+root-CWR-update(su_removed).zip.
I assume the RogueXM requires a blob-File within the zip, which is not provided by asus-original-downloads?
A bit confused ;-)
BR / Adarof

adarof said:
Okay, I havent known this either...
Is there a list of asus-default installed apps? I havent found :/
Click to expand...
Click to collapse
That is a tough one. i would suggest looking at the OP's for the custom ROMs and see if the have an Add-on pack that will put them in their custom ROMs. That way you'll be able to extract the apps from them and push to /system/app on your own (don't forget to set permissions also on the ones you push). If not, I will see if I can pull them from mine, zip them up and them send a link to you, but that won't be until I 1 get home and 2 get some time which unfortunately won't be tonight.
adarof said:
SURecoverty means the USRecovery.zip, right?
Click to expand...
Click to collapse
Yes sorry about that. I was typing too fast. :/
adarof said:
Am I right?
...on 2) I get
Code:
assert failed: write_raw_image("/tmp/blob","staging")
E: Error in /sdcard/WW_epad-user-9.2.1.24.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
This is the 3rd Status 7 I have seen today from someone. The other two were in my phone forums and it is bc of a mismatched CWR version. In my phone forum, they just needed to flash a different kernel. Not sure what is going on with it here, but see below...
adarof said:
...but I could install the repacked-8.2.3.13_WW+root-CWR-update(su_removed).zip.
Click to expand...
Click to collapse
If you can get this far, then NVflash this and get it to boot up completely. That way you shoudl have all the /system/apps anyways. You can root it (if you lose it somehow) with Razerclaw since it is HC.13 (if you accidentally update all the way to ICS .11 without rooting, you can use ViperMod or any of the other root tools out there) Remember that once you root it, you can use OTA Rootkeeper to preserve your Root status, accept the OTA and then restore Root (this is what I have done since HC). Then install this app and flash the USRecovery.zip and you should be good to go. Reboot to full boot up and then try to reboot into recovery using Key Combo. It should throw the Android on his back with ! above him.
I would then uninstall the Recovery Installer to make sure you don't accidentally hit it and you are back where you started. But you'll have the APK to reinstall whenever you want later on.
Sorry for the long post, just trying to cover everything bc I have log out for a bit and won't be on until later on. Maybe Thing O Doom will swing through, though.
Edit::: Check this out too.

Woodrube said:
That is a tough one. i would suggest looking at the OP's for the custom ROMs and see if the have an Add-on pack that will put them in their custom ROMs.
Click to expand...
Click to collapse
Well, Ok...since I "just" would like to have back a real stock system, with OTA - there should be another way ;-)
Woodrube said:
This is the 3rd Status 7 I have seen today from someone. The other two were in my phone forums and it is bc of a mismatched CWR version. In my phone forum, they just needed to flash a different kernel. Not sure what is going on with it here, but see below...
Click to expand...
Click to collapse
Okay! This explains why I cant find any 1000000 hits on google related to my prop, which seems to me rather "simple" in principle ;-)
Woodrube said:
If you can get this far, then NVflash this and get it to boot up completely. That way you shoudl have all the /system/apps anyways.
Click to expand...
Click to collapse
Agreed...apps should be there. But even the Asus storage app was missing? Thus no stock-apps included?
Its an old Andoroid 3.0.1 and it wouldn't find OTA updates - thats correct?
Woodrube said:
Then install this app and flash the USRecovery.zip and you should be good to go. Reboot to full boot up and then try to reboot into recovery using Key Combo. It should throw the Android on his back with ! above him.
Click to expand...
Click to collapse
Okay, while Power-VolDown -> VolUp (this gave me Rogue XM before but since I installed USRecovery it was overwritten, right?) -> a Droid on its back with a "!" comes up.
...and now?
The .24 update on SDCard is recognized but when I try to install the knocked-out droid with "!" comes on reboot again and next reboot yields to a popup "failed update, reverted to old system" or so.
Woodrube said:
Sorry for the long post, just trying to cover everything bc I have log out for a bit and won't be on until later on. Maybe Thing O Doom will swing through, though.
Click to expand...
Click to collapse
THANKS for your time so far and dont stress anything
I really appriciate it! Im feeling lost on android...even I work with Linux/Unices since a decade or so :-/
Woodrube said:
Edit::: Check this out too.
Click to expand...
Click to collapse
Thats a Win-solution :-/
Most propably I need a stock DE .21 or WW .24 , repacked for flashing with CWM ... right? But that doesnt exists?!?! Cant imagine...
BR - Adarof!

Im still on this problem and have no idea - searched a lot, but havent found any real howtos for DE-tf101 for unbricking.
So my main thoughts are about this Error7, which is really ...strange.
I could flash the repacked, which is available for .11. But I dont have a change to get anz further...
I SHOULD be able to flash a original asus stock Firmware with the Rogue XM Touch recovery, right?
Since Im not able to ... should I try an older version of Rogue XM?
BTW: Is the region info somewhat hard-wired thus it couldnt be changed?
BR - Adarof

There's a WW .24 available for tf101 and I'm making a 9.2.2.6 for the Tf101G,
so there is the latest FW available.

If you are flashing, then that means you have a custom recovery. That is why no OTA.
I'm mobile now but IIRC from before, you flash a working CWR version of the ROM. Thne boot up. Then flash the stock recovery. Then you should be able to OTA after that.
Just make sure whatever ROM you flash is full. If you can nvflash that would be better and then put stock recovery in after your first boot.

Thanks to both of you!
@Woodrube: Flashing means using RogueXM...
Summary:
1) Rogue could flash me either CWR/rooted images or the repacked one - both without OTA.
Just RogueXM is left as bootloader, which shouldnt prevent OTA?!
2) Rogue gives Error7 on flashing the asus-downloaded-onetime-depacked-firmwares, doesnt matter if the DE.21 or current WW.24. :-/
Trying to make the long story short:
For comming back to a "known" system I would like to really go back to a stock system.
I conclude that using nvflash would be the best for this, right?
But where do I get the img-Files for flashing using nvflash?
I just found one package which included a download.sh: It repartitioned, formated and installed a WW android3 (3.2.1) version and deleted the RogueXM. It mentioned its a stock firmware (thus should have all apps).
Sadly no updates afterwards...
I think it could be since its the WW version and I would need a WW .21/.24 (since 21/24 dont distinguish DE and WW anymore) or an older DE-version. But for nvflash I need the img files of these firmwares, which I dont find. ...
Maybe you could simply point me to such img files for nvflash, please?
BR / Adarof

Finally I managed to borrow a win pc and thus could give EasyTool of your posting #8 a try: http://forum.xda-developers.com/showthread.php?t=1688012
After some hassle with the driver I managed to flash asus stock download DE_epad-user-9.2.1.21, which is "DE_Special" for coming to WW of german tf101s. the tf was wiped and boots just fine - it states that it has
IML74L.WW_epad9.2.1.21-20120413 - as I think is fine.
Sadly no update again:
The OTA doesnt find any.
The microSD recognizes WW_epad-user-9.2.1.24.zip, but during rebooting I get the Droid with ! and after another reboot a popup with something like "update failed (12)" (in german Systemaktuallisierung fehlgeschlagen (12)). It mentiones that the new version in not compatible ...but ....the .24 is for the DE_special .21 the next ... ?!
I could flash the .24 using Easytool, but this would mean to loose always all data for an update ....
Installing rogue still gives error7 on flashing stock (once decompressed) .zip

I've been reading and Rouge gives errors with stock otas X.x
You can manually install the stock blobs with adb shell, but they will overwrite recovery and etc..
If you want total stock you need to NvFlash, and for whatever reason your tf does NOT like updates.
Rouge V1.3 will take otas, if you don't mind the downgrade.

Thanks for the hint - but I was to lazs to install the rogue 1.3.
I found a .zip, which I tried to install by Rogue 1.5 hoping for a downgrade overall, but during installation it stated "Returning to recovery" and still 1.5 was installed .
What I finally found is a ww-9.2.1.21-to-9.2.1.24-CWM-v1.0.zip image.
I installed this using rogue 1.5 and got a clean .24 installation.
So I'm using this installation hopeing either
1) OTA will work, if asus releases .24++ or
2) I find an ww-9.2.1.24-to-9.2.1.24++
Still I dont get why the EasyTool .21 installation yields to a non-OTA state ... but ...
So, THANKS all of you for your support and hints!
I'll come back here and report further on, if .24++ is out
BR / Adarof

bad luck
....meanwhile my tf101 has started to ignored the dock battery, while the keyboard still works. I tried cleaning ....no luck, the dock battery does not come up within the menues ...
Thus it was returned and I'm waiting for repairing or refunding ...
BR / Adarof

Somewhat worried...

Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?

redheadplantguy said:
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
Click to expand...
Click to collapse
go to the root of your external sd card and delete all the zip file(s), you probably left it there when you downgrade. Also delete file from internal sdcard in /cache/recover if any. Once you unlocked you shouldn't receive anymore OTA.

redheadplantguy said:
I finally got the nerve to unlock. I had to downgrade doing it.
Click to expand...
Click to collapse
Strange, many people said the unlock tool works fine on JB.
redheadplantguy said:
Now, I heard after unlocking, an ota will brick tablet.
Click to expand...
Click to collapse
Where?
I don't say it cannot brick your tablet, but I am not aware of any reports that it does.

redheadplantguy said:
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
Click to expand...
Click to collapse
As said by the first responder, you can delete the cached firmware file. I do not expect the OTA to brick your tablet, but you could interrupt the process if you really wanted to.
Even with a brick, there are loads of possibilities of flashing a firmware file from ASUS' repository. Then you'd have a fresh tablet OS to your convenience. The situation you describe above does not exactly ruffle any my feathers.
EDIT: just in case you are not yet on .30 or higher... get Nvflash on there!

MartyHulskemper said:
As said by the first responder, you can delete the cached firmware file. I do not expect the OTA to brick your tablet, but you could interrupt the process if you really wanted to.
Even with a brick, there are loads of possibilities of flashing a firmware file from ASUS' repository. Then you'd have a fresh tablet OS to your convenience. The situation you describe above does not exactly ruffle any my feathers.
EDIT: just in case you are not yet on .30 or higher... get Nvflash on there!
Click to expand...
Click to collapse
i could be mistaken. alas, i can't get nvflash. i wish i could. i didnt expect firmware to come in after unlock.

redheadplantguy said:
i could be mistaken. alas, i can't get nvflash. i wish i could. i didnt expect firmware to come in after unlock.
Click to expand...
Click to collapse
If you unlocked your device, there will be NO OTA update, unless the download happened before you unlocked or you may have the update software sitting in your external SDcard or in internal SDcard /cache/recovery.

buhohitr said:
If you unlocked your device, there will be NO OTA update, unless the download happened before you unlocked or you may have the update software sitting in your external SDcard or in internal SDcard /cache/recovery.
Click to expand...
Click to collapse
It downloaded, showing a progress bar. Later I reset, and this morning, it downloaded again. It showed it actually downloading.

redheadplantguy said:
It downloaded, showing a progress bar. Later I reset, and this morning, it downloaded again. It showed it actually downloading.
Click to expand...
Click to collapse
You must be "the chosen one", first I heard of OTA stills working after you unlocked. Just verify that you actually "unlocked", by reboot your device and it should shows "your device is unlock" during booting up. If it does, then you are the chosen one. You can update as long as you are pure stock rom, and if you have root, just use OTA root keeper to keep root then you can update your pure stock rom to the new version. If you mod/freeze system apps then the update will fail. I never heard of updating of a stock rom with unlocked bootloader will brick your device. It will brick your device if you modded or using custom rom.
EDIT: If you don't want to do through OTA, you could download full package rom from Aus site, unzip then copy the new zip file to the root of your external SDcand. Disabled wifi (no more download) then delete the update file located in your internal memory /cache/recovery. Turn off your device, go into recovery mode by hold down volume down+power button, then install from there.

buhohitr said:
You must be "the chosen one", first I heard of OTA stills working after you unlocked. Just verify that you actually "unlocked", by reboot your device and it should shows "your device is unlock" during booting up. If it does, then you are the chosen one. You can update as long as you are pure stock rom, and if you have root, just use OTA root keeper to keep root then you can update your pure stock rom to the new version. If you mod/freeze system apps then the update will fail. I never heard of updating of a stock rom with unlocked bootloader will brick your device. It will brick your device if you modded or using custom rom.
EDIT: If you don't want to do through OTA, you could download full package rom from Aus site, unzip then copy the new zip file to the root of your external SDcand. Disabled wifi (no more download) then delete the update file located in your internal memory /cache/recovery. Turn off your device, go into recovery mode by hold down volume down+power button, then install from there.
Click to expand...
Click to collapse
Thanks. Yeah, says "the device is unlocked." In tiny white letters very top left. I hope my glitch doesn't interfere in me flashing new ROM's
Odd, did factory reset, and lost root AND twrp. Had to reflash it.

redheadplantguy said:
Thanks. Yeah, says "the device is unlocked." In tiny white letters very top left. I hope my glitch doesn't interfere in me flashing new ROM's
Odd, did factory reset, and lost root AND twrp. Had to reflash it.
Click to expand...
Click to collapse
That does sound like it actually flashed something (at least partly). I would run that unlock tool another time just to be sure I wouldn't get into trouble down the road (Having an ASUS OTA flash right on top of your CleanROM/CM10/AOKP could be a minor disaster, or a pretty disastrous disaster, depending on what ROM of these you were on. Flashing over stock, well... minor nuisance, but it would be majorly inconvenient to have to flash root and stuff all the time.)

MartyHulskemper said:
Having an ASUS OTA flash right on top of your CleanROM/CM10/AOKP could be a minor disaster, or a pretty disastrous disaster, depending on what ROM of these you were on.
Click to expand...
Click to collapse
No, it just doesn't work. The updater-script inside the OTA package compares the checksums of the system apps to be patched, and aborts as soon as one doesn't match the previous stock ROM.
The only potential danger I see is the communication with the bootloader which kernel to boot - the OTA downloader (DMClient) somehow has to instruct the bootloader to load the recovery kernel to install the dlpkgfile from /cache, and if that process is still not understood by custom recovery creators (there were some problems apparently, I don't know if they are solved), you might end up with a device that only boots into the recovery and not into Android.

Thanks. I will.
Sent from my SGH-T679 using Xparent ICS Blue Tapatalk 2

[Q] How to take OTA update after Sunshine

Please forgive me for having to ask what I'm sure sounds like a stupid question, but I have no idea how to accept the OTA update Verizon is attempting to send me to version 4.4.4 on my HTC One M8 now that I have used Sunshine to attain S-Off and have TWRP and SuperSU installed.
I have used ADB, but am not very familiar with it at all.
I saw threads talking about flashing ROMS, but for the most part it really seems like Greek to me.
I had only gone down the Sunshine road because I wanted root access mainly for one app--Lightflow. In retrospect I'm feeling like I opened a can of worms. But the can is open, and the worms are out there, so now I need to learn how to handle them.
I know I am supposed to keep S-off, no matter what I do. I think perhaps I'm supposed to revert back somehow to a "stock" bootloader (instead of TWRP--is that right?) but I don't have any idea how to do that (though I expect ADB is involved), and I also don't know what effect that would have on SuperSu, as I vaguely recall TWRP may have been required for SuperSU to work.
I'm really lost.
Any help, in very easy to understand terms (pretend you're trying to explain this to your grandmother) would be appreciated.
Thanks!

Andyw2100 said:
Please forgive me for having to ask what I'm sure sounds like a stupid question, but I have no idea how to accept the OTA update Verizon is attempting to send me to version 4.4.4 on my HTC One M8 now that I have used Sunshine to attain S-Off and have TWRP and SuperSU installed.
I have used ADB, but am not very familiar with it at all.
I saw threads talking about flashing ROMS, but for the most part it really seems like Greek to me.
I had only gone down the Sunshine road because I wanted root access mainly for one app--Lightflow. In retrospect I'm feeling like I opened a can of worms. But the can is open, and the worms are out there, so now I need to learn how to handle them.
I know I am supposed to keep S-off, no matter what I do. I think perhaps I'm supposed to revert back somehow to a "stock" bootloader (instead of TWRP--is that right?) but I don't have any idea how to do that (though I expect ADB is involved), and I also don't know what effect that would have on SuperSu, as I vaguely recall TWRP may have been required for SuperSU to work.
I'm really lost.
Any help, in very easy to understand terms (pretend you're trying to explain this to your grandmother) would be appreciated.
Thanks!
Click to expand...
Click to collapse
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.

The Stig 04 said:
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
Click to expand...
Click to collapse
Thanks for the response.
So the question is how do I go back to my stock recovery instead of TWRP?
And then after taking the update, what do I need to do to reinstall TWRP and then flash the latest SuperSU.zip file?
I realize I should know this stuff, but I had help from the Sunshine folks last time, so I really don't remember everything that went on, or exactly what I did vs. what they did, etc.
Thanks again!

Andyw2100 said:
Thanks for the response.
So the question is how do I go back to my stock recovery instead of TWRP?
And then after taking the update, what do I need to do to reinstall TWRP and then flash the latest SuperSU.zip file?
I realize I should know this stuff, but I had help from the Sunshine folks last time, so I really don't remember everything that went on, or exactly what I did vs. what they did, etc.
Thanks again!
Click to expand...
Click to collapse
You don't need to do any of that.
Download the exe from this thread: http://forum.xda-developers.com/showthread.php?p=56211035
run it and you will be on stock 4.4.4.
To get TWRP back you have to flash it fastboot (lots of tutorials all over the forum for that) and with the recovery installed you can just flash SuperSU in recovery to gain root again.

The Stig 04 said:
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
Click to expand...
Click to collapse
berndblb said:
You don't need to do any of that.
Download the exe from this thread: http://forum.xda-developers.com/showthread.php?p=56211035
run it and you will be on stock 4.4.4.
To get TWRP back you have to flash it fastboot (lots of tutorials all over the forum for that) and with the recovery installed you can just flash SuperSU in recovery to gain root again.
Click to expand...
Click to collapse
Thanks. That thread says that using that .exe is going to wipe my phone, which would then mean I need to restore it from a backup. I think I'd really just rather take the OTA update to 4.4.4, since in the future I'm going to want to take other OTA updates as well. So if I can learn how to return to my stock recovery now, and the rest of it for this OTA update, I should be good to go for future OTA updates.
Thanks, though.
So my questions above remain about how to revert to the stock recovery, and then how to reinstall TWRP and SuperSU.
Thanks!

Andyw2100 said:
Thanks. That thread says that using that .exe is going to wipe my phone, which would then mean I need to restore it from a backup. I think I'd really just rather take the OTA update to 4.4.4, since in the future I'm going to want to take other OTA updates as well. So if I can learn how to return to my stock recovery now, and the rest of it for this OTA update, I should be good to go for future OTA updates.
Thanks, though.
So my questions above remain about how to revert to the stock recovery, and then how to reinstall TWRP and SuperSU.
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2723159
Download the file "Stock Recovery 4.4.3" from the thread above. Flash that using ADB, once you take the OTA and are on 4.4.4 Flash TWRP using ADB again.
http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu from the thread above and place that in your SD Card. Boot into recovery and install it. Though you should already have this on your computer or SD Card.
Edit: I believe there is an even easier way, just have never done it/tried it so I don't wanna lie and act like I know what to do.

The Stig 04 said:
http://forum.xda-developers.com/showthread.php?t=2723159
Download the file "Stock Recovery 4.4.3" from the thread above. Flash that using ADB, once you take the OTA and are on 4.4.4 Flash TWRP using ADB again.
http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu from the thread above and place that in your SD Card. Boot into recovery and install it.
Click to expand...
Click to collapse
You have to flash the stock recovery in fastboot - not ADB. And you gotta make sure all the bloatware that comes with the original stock rom is in place or the OTA will fail (it does a "system integrity check" prior to applying the OTA). That can be a headache if you do not have a backup of apps you may have removed...
Each future update will be available within days of release here on XDA, either as a standalone firmware update or stock rooted rom or both. I would not take OTAs - ever.
Develop a solid backup routine and restoring your device is a 20 minute exercise...

Thanks to both of you.
I don't believe I removed any bloatware, so I think the OTA update should work.
How do I flash the stock recovery in fastboot?
Again, many thanks!

I just checked my ADB folder, and see a fastboot.exe there, so I imagine it's just a command like ADB. I'll give this a shot later. Again, many thanks to both of you for the assistance. I will post again with, hopefully, my good results, or with additional questions.
Thanks!

berndblb said:
You have to flash the stock recovery in fastboot - not ADB. And you gotta make sure all the bloatware that comes with the original stock rom is in place or the OTA will fail (it does a "system integrity check" prior to applying the OTA). That can be a headache if you do not have a backup of apps you may have removed...
Each future update will be available within days of release here on XDA, either as a standalone firmware update or stock rooted rom or both. I would not take OTAs - ever.
Develop a solid backup routine and restoring your device is a 20 minute exercise...
Click to expand...
Click to collapse
Sorry I thought fastboot and ADB was kinda that same thing seeing as it was refereed to as "fastboot/adb directory"? If not my bad! Also this is the method I always use to take OTA's and have never ever had a problem.

Andyw2100 said:
I just checked my ADB folder, and see a fastboot.exe there, so I imagine it's just a command like ADB. I'll give this a shot later. Again, many thanks to both of you for the assistance. I will post again with, hopefully, my good results, or with additional questions.
Thanks!
Click to expand...
Click to collapse
Put the recovery image into the same folder with your fastboot.exe
Open a command prompt from that folder (shift + right click > open cmd window here)
check connection with
Code:
fastboot devices
if successful
Code:
fastboot flash recovery <name of recovery>.img

Would you need to remove root before taking the OTA? Just curious.
Sent from my GT-N5110 using xda app-developers app

mumbles202 said:
Would you need to remove root before taking the OTA? Just curious.
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
No. You will lose root after the ota so it doesn't matter but you can always get it back as long as you are S-OFF by flashing a custom recovery like TWRP and then flashing SuperSu.

Well, I have run into a snag right off the bat.
While the command "ADB Devices" sees the phone, "Fastboot Devices" does not.
Any ideas as to how to rectify this?
Thanks!

I did some googling, and this problem I solved on my own.
I had to use adb to get into fastboot USB mode or something with adb reboot bootloader, and then fastboot devices worked.
I'm now continuing on.

Well, so much for this being easy.
I believe I successfully flashed my stock recovery.
But apparently I no longer have the OTA update ready to install, as at some point I tried to run it again just to get TWRP up, and now it's not showing as available. And when I try to check for updates in Settings/Software update/Check new I get an error message that says Download Unsuccessful. We were not able to download this update.
For now I guess I'll wait and see if Verizon tries to send me the update again, or if it works if I check for it myself some other time. (Or if anyone here has any suggestions.)
Also, I still seem to have root access. I thought that I wouldn't, since I believe I have replaced TWRP with the stock recovery.

I'm also now getting a constant error message about Google Play Services having stopped. And my wi-fi doesn't seem to be connecting properly.
I'm really wondering just what the heck I've done.

Well, for anyone still following my saga...
Things are somewhat better, but not totally resolved.
I kept checking, and eventually I was able to download the OTA update to 4.4.4. I did, I updated, and all went smoothly. I then was able to flash TWRP and then install Super SU and I have root access again. So on that front, all is well.
The problems that remain, though, are that I still am having issues with Google Play Services quitting and my Wi Fi not connecting. Could these things be related somehow? I've tried clearing the cache and then actually all data from Google Play services, but that has not helped. I have deleted my networks, and then tried reconnecting to them, but that also has not helped. It shows my networks in range as "saved" or "disabled" but won't connect to any of them.
Any ideas for me?
Thanks.
And thanks for the help in getting the 4.4.4 OTA update. At least that worked!

I realize I am basically having a conversation with myself at this point, but just to wrap things up, in case anyone does come along and read any of this...
I have solved all my issues.
The Google Play Services issue must have been related to the Wi-Fi not connecting, and the Wi-Fi not connecting was due to my main network actually having an issue and the fact that I had never authorized the phone on the other networks. I guess this is what happens after being up almost 24 hours. At least I think everything is OK now.
Again, thanks to those that helped!

Andyw2100 said:
I realize I am basically having a conversation with myself at this point, but just to wrap things up, in case anyone does come along and read any of this...
I have solved all my issues.
The Google Play Services issue must have been related to the Wi-Fi not connecting, and the Wi-Fi not connecting was due to my main network actually having an issue and the fact that I had never authorized the phone on the other networks. I guess this is what happens after being up almost 24 hours. At least I think everything is OK now.
Again, thanks to those that helped!
Click to expand...
Click to collapse
Not sure why I stopped receiving notifications from your thread. But at least you got your phone in working order! lol

Locking bootloader removes root? Also more Questions. [Phone Gone Now]

I'm gifting my father in law an Honor 6X. I already unlocked the bootloader and rooted, but I'd like for him to be able to install updates when they're released. If I uninstall all the bloatware while rooted and then relock the bootloader, will root be retained? Will TWRP be removed? Will OTA updates be allowed? This is all on the stock ROM.

Superorb said:
I'm gifting my father in law an Honor 6X. I already unlocked the bootloader and rooted, but I'd like for him to be able to install updates when they're released. If I uninstall all the bloatware while rooted and then relock the bootloader, will root be retained? Will TWRP be removed? Will OTA updates be allowed? This is all on the stock ROM.
Click to expand...
Click to collapse
I believe you should be able to receive updates with the bootloader unlocked. The OTA might relock the bootloader and will most likely remove root. In order to update you will need to also have stock recovery installed so there would be no way for him to root again without unlocking the bootloader and flashing twrp.

BakedOnSomeSour said:
I believe you should be able to receive updates with the bootloader unlocked. The OTA might relock the bootloader and will most likely remove root. In order to update you will need to also have stock recovery installed so there would be no way for him to root again without unlocking the bootloader and flashing twrp.
Click to expand...
Click to collapse
Ok. He's clueless when it comes to even using stock phones, so I'll probably completely return the phone to stock and call it a day. Is there a thread floating around here to do relock, unroot, and completely return to stock?

Superorb said:
Ok. He's clueless when it comes to even using stock phones, so I'll probably completely return the phone to stock and call it a day. Is there a thread floating around here to do relock, unroot, and completely return to stock?
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985

BakedOnSomeSour said:
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
Click to expand...
Click to collapse
That says it's for after you've flashed custom ROMs. I've never flashed a ROM on mine, only unlocked and rooted. Haven't even uninstalled any apps yet. Is there a quick way to relock and unroot?

Superorb said:
That says it's for after you've flashed custom ROMs. I've never flashed a ROM on mine, only unlocked and rooted. Haven't even uninstalled any apps yet. Is there a quick way to relock and unroot?
Click to expand...
Click to collapse
Its also if you flashed twrp not only custom roms. You can uninstall root in the superSU app when selecting full unroot in the settings. I believe a factory reset can do it too. The next step would be to download the firmware for the phone and using fastboot to flash a boot and recovery image and then to lock the bootloader. Those steps are all in the link. That is the quickest way.

BakedOnSomeSour said:
Its also if you flashed twrp not only custom roms. You can uninstall root in the superSU app when selecting full unroot in the settings. I believe a factory reset can do it too. The next step would be to download the firmware for the phone and using fastboot to flash a boot and recovery image and then to lock the bootloader. Those steps are all in the link. That is the quickest way.
Click to expand...
Click to collapse
Damn, I was hoping it would be as easy as "fastbook oem lock" and be done with it.

Superorb said:
Damn, I was hoping it would be as easy as "fastbook oem lock" and be done with it.
Click to expand...
Click to collapse
Same. if you need any additional help with the process just let me know.

BakedOnSomeSour said:
Same. if you need any additional help with the process just let me know.
Click to expand...
Click to collapse
Thanks! Where can I find the EMUI 5.0.1 image? Mine is BLN-L24.

Superorb said:
Thanks! Where can I find the EMUI 5.0.1 image? Mine is BLN-L24.
Click to expand...
Click to collapse
There's a PC application called firmware finder. https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
You can download firmware finder on your phone too and download the files from there. It's on the play store.

BakedOnSomeSour said:
There's a PC application called firmware finder. https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
You can download firmware finder on your phone too and download the files from there. It's on the play store.
Click to expand...
Click to collapse
Ok, downloaded the Firmware finder and I have no idea how to use it. Directions don't make any sense and I have no idea what I'm doing after entering in my phone model.
I'm trying, but this phone is so different from my old LG G2 to play around with.

Superorb said:
Ok, downloaded the Firmware finder and I have no idea how to use it. Directions don't make any sense and I have no idea what I'm doing after entering in my phone model.
I'm trying, but this phone is so different from my old LG G2 to play around with.
Click to expand...
Click to collapse
When you get into the Firmware Finder(PC) app youll notice your on a tab labeled "Main Page". Click on the tab labeled "common base" and type BLN-L24 into the search bar at the top right and then click on FIND. A list of firmware will pop up. Find the one that matches your build number and then click on the link under the "filelist" section. There will be two or three different zips you need to download. When you have the three downloaded let me know.

BakedOnSomeSour said:
When you get into the Firmware Finder(PC) app youll notice your on a tab labeled "Main Page". Click on the tab labeled "common base" and type BLN-L24 into the search bar at the top right and then click on FIND. A list of firmware will pop up. Find the one that matches your build number and then click on the link under the "filelist" section. There will be two or three different zips you need to download. When you have the three downloaded let me know.
Click to expand...
Click to collapse
Ok, I've downloaded all 3 zip files from my build at over 2gigs.

Superorb said:
Ok, I've downloaded all 3 zip files from my build at over 2gigs.
Click to expand...
Click to collapse
Ok now extract the files from the update.zip folder. Then take the UPDATE.app from the extracted files and open it with update extractor: https://forum.xda-developers.com/showthread.php?t=2433454
After that your ready to follow the steps on the other guide.

So I screwed up. Before you posted I unrooted via unSU flashable zip. Then I fastboot flashed boot and recovery to the stock one from the update.app file. Now it's got some verification error on power on and OTA updates fail. I tried moving the update.app to a dload folder on sdcard, but when it starts up it fails at 5% when restoring from the sdcard.
ETA: Tried the 360 FW which updated successfully. Booted and asked for password. After panicking shutdown and copied the HW contents to Sdcard and did the update again which succeeded. Booted and asked for password again and I panicked again. Pulled the Sdcard and booted into stock recovery. Wiped everything and then restarted crossing fingers. Started up like normal, no password request! So it looks like the phone is back on totally stock EMUI 5.0. I'll hope for the update and will try with fingers and toes crossed. Thanks for your help. I may be back, but hopefully not.
ETA2: There's no update option above the last About option in settings... How do I get the update option?

Superorb said:
So I screwed up. Before you posted I unrooted via unSU flashable zip. Then I fastboot flashed boot and recovery to the stock one from the update.app file. Now it's got some verification error on power on and OTA updates fail. I tried moving the update.app to a dload folder on sdcard, but when it starts up it fails at 5% when restoring from the sdcard.
ETA: Tried the 360 FW which updated successfully. Booted and asked for password. After panicking shutdown and copied the HW contents to Sdcard and did the update again which succeeded. Booted and asked for password again and I panicked again. Pulled the Sdcard and booted into stock recovery. Wiped everything and then restarted crossing fingers. Started up like normal, no password request! So it looks like the phone is back on totally stock EMUI 5.0. I'll hope for the update and will try with fingers and toes crossed. Thanks for your help. I may be back, but hopefully not.
ETA2: There's no update option above the last About option in settings... How do I get the update option?
Click to expand...
Click to collapse
Edit: Before trying below steps. Just put the files from "BLN-L24_hw_usa"(b360) into dload folder and flash with dload. It might update the version.img without the needs for the steps below. if that brings the build number back to b360 use the hisui(PC) application to connect to the phone and update
Ok i forgot to mention something. The reason you dont have a update option is because you are on b360 which never had a button. Your build number on your phone will say b366 but thats incorrect. You cant receive an ota automatically because the phone thinks its already on the latest version. You need to take the UPDATE.APP from the "BLN-L24_hw_usa" (b360) folder and extract the VERSION.IMG file. It needs to be flashed with TWRP because fastboot wont work for some reason. That file will fix the build number and change it back to b360 so you can receive the OTA which will also restore the missing apps and features. That means you have to unlock the bootloader. Flash twrp. Flash the vendor.img with twrp and then do the dload method.
You have all the files and have done it already so this time will be easier. Ive done this way too many times with this phone. Sorry i forgot the mention the one step

Build number on my phone is already 360, and it has never been 366. Tried flashing the 360 like you said via dload and nothing seems to have changed.
Also the SIMtray eject tool seems to just go into the phone without ejecting the tray. A paperclip worked, but man this phone is really frustrating.

Superorb said:
Build number on my phone is already 360, and it has never been 366. Tried flashing the 360 like you said via dload and nothing seems to have changed.
Also the SIMtray eject tool seems to just go into the phone without ejecting the tray. A paperclip worked, but man this phone is really frustrating.
Click to expand...
Click to collapse
Oh ok my build number always got stuck at b366. Try connecting with the HiSuite program and getting an OTA. And yes this is the strangest, most difficult phone to work with that ive ever owned.

BakedOnSomeSour said:
Oh ok my build number always got stuck at b366. Try connecting with the HiSuite program and getting an OTA. And yes this is the strangest, most difficult phone to work with that ive ever owned.
Click to expand...
Click to collapse
Wife made me box it up and ship to her dad, so I no longer have the phone. I did install the HiSuite when I first powered on the phone and it was never able to connect and see the phone, so who knows what's going on.
Thanks for all your help. I have another one, but I'm just going to sell it and be done with it. No idea what other phone I can get with the same specs for the same price that's not so difficult to flash, but I'll keep looking I guess.

Superorb said:
Wife made me box it up and ship to her dad, so I no longer have the phone. I did install the HiSuite when I first powered on the phone and it was never able to connect and see the phone, so who knows what's going on.
Thanks for all your help. I have another one, but I'm just going to sell it and be done with it. No idea what other phone I can get with the same specs for the same price that's not so difficult to flash, but I'll keep looking I guess.
Click to expand...
Click to collapse
Its not difficult. In order to connect to hisuite you need to enable developer settings and allow usb debugging or type hisuite in the settings search bar and click "allow HiSuite to use HDB". I got this phone for christmas and i already know a ton about it. It may seem complicated now but its really nothing.