Database Info

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

Nvidia Shield- How Can I Avoid The Kill Switch?

I have my old Nvidia shield tablet and i have WiFi off and powered off.
I've been reading you can stop the kill switch from i guess changing the boot loader or operating system?
I new to this stuff.
Could someone just give me some directions on how to go threw this process please.
I don't know if it's to late cause i have the most recent update? but like i said it's turned off and WiFi is off and i heard that the kill switch is sent over the internet to your device and you don't have to confirm it.
So i hope my system is safe until i can do what ever you guys advise me to do.
Thank you...

treat your old tablet before connecting the new one to internet
Hello. You have to delete a folder (/system/apps/TegraOTA if you are on last firmware, with OTA 3.1) but to do this, you need root as folders in /system are not visible for the normal (unrooted) user. Or you flash a custom firmware, and flash nomoreOTA.zip that you'll find in the same forum : http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489
Be sure to act before you use your new tablet, and ideally do the same to the new one before connecting it to internet. Then the kill switch maybe will not even be sent to you/your old tablet.
:fingers-crossed:
edit : do a search here for 'root shield tablet lollipop' if you need info to get root or flash custom recovery : http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
Note also that if you choose to (and succeed to) flash another (custom) ROM, such as Blisspop, you'll be safe as those custom roms avoid the kill switch (no /system/apps/TegraOTA folder in them)

If your new tablet is never activated then in theory the killswitch should never be sent out. So as far as I can see flashing a custom rom on the new device before letting it boot into android or connect to the internet should prevent device from showing as having been activated.
Also blocking Nvidia's OTA servers on the network level (you'll need custom firmware on your router) should do the trick as well.
Block all of these:
Code:
23.32.163.186
e886.g.akamaiedge.net
ota.nvidia.com.edgekey.net
ota.nvidia.com
Also it might be worth looking into whether flashing nomoreOTA.zip on the new tablet works to the same effect.

I used my new tablet and the both were working for the day, both have no problems so far.
I've been reading that they are sending out kill switches in 4 segments, by using the last 2 digits of the serial numbers system.
So mine hasn't gone threw yet i don't think.
So i need to root it?
Then delete the OTA file?
Then flash a custom firmware?
Thanks guys...

Just root it, do a full wipe=factory reset in TWRP and flash a custom Rom like Bliss and you will be OK.

Jarocks said:
If your new tablet is never activated then in theory the killswitch should never be sent out. So as far as I can see flashing a custom rom on the new device before letting it boot into android or connect to the internet should prevent device from showing as having been activated.
Also blocking Nvidia's OTA servers on the network level (you'll need custom firmware on your router) should do the trick as well.
Block all of these:
Code:
23.32.163.186
e886.g.akamaiedge.net
ota.nvidia.com.edgekey.net
ota.nvidia.com
Also it might be worth looking into whether flashing nomoreOTA.zip on the new tablet works to the same effect.
Click to expand...
Click to collapse
Just for info, I found out today that, even if my new tablet was also flashed with nomoreOTA.zip, and even if I did it before there was any internet connexion from it, my old tablet is now flagged and an urgent OTA (in fact the kill switch) is waiting to be sent to it. Of course it still works, thanks to nomoreOTA.zip. But Nvidia did flag the old tablet after 10 days use of the new one (maybe they check serial numbers of tablets connected to grid or to another Nvidia server). Both my old and my new tablets are still working.

Snah001 said:
Just root it, do a full wipe=factory reset in TWRP and flash a custom Rom like Bliss and you will be OK.
Click to expand...
Click to collapse
I see lots of root programs, is there a best one?
Can you flash with TWRP?
And someone said all i have to do is...
"Full Process
1) Unlock Bootloader.
2) Flash TWRP Recovery.
3) Get the no more OTA.zip from XDA and flash it via TWRP
4) Check if the update option is removed from Settings, if not flash it again.
Done! "
Is that ok also?
Thank you...

You need to root to flash twrp?

EowynCarter said:
You need to root to flash twrp?
Click to expand...
Click to collapse
No, but you do need an unlocked bootloader to fastboot flash anything.

amartolos said:
No, but you do need an unlocked bootloader to fastboot flash anything.
Click to expand...
Click to collapse
Yeah, that the conclusion i reached.
Flash done, now runing bliss pop. First start got me loads of errors. I went until i realized i had forgotten to wipe. It's been a while since i last played with custom roms.

oliwek said:
Just for info, I found out today that, even if my new tablet was also flashed with nomoreOTA.zip, and even if I did it before there was any internet connexion from it, my old tablet is now flagged and an urgent OTA (in fact the kill switch) is waiting to be sent to it. Of course it still works, thanks to nomoreOTA.zip. But Nvidia did flag the old tablet after 10 days use of the new one (maybe they check serial numbers of tablets connected to grid or to another Nvidia server). Both my old and my new tablets are still working.
Click to expand...
Click to collapse
Well, that's disappointing

oleg77 said:
Hello. You have to delete a folder (/system/apps/TegraOTA if you are on last firmware, with OTA 3.1) but to do this, you need root as folders in /system are not visible for the normal (unrooted) user. Or you flash a custom firmware, and flash nomoreOTA.zip that you'll find in the same forum : http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489
Be sure to act before you use your new tablet, and ideally do the same to the new one before connecting it to internet. Then the kill switch maybe will not even be sent to you/your old tablet.
:fingers-crossed:
edit : do a search here for 'root shield tablet lollipop' if you need info to get root or flash custom recovery : http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
Note also that if you choose to (and succeed to) flash another (custom) ROM, such as Blisspop, you'll be safe as those custom roms avoid the kill switch (no /system/apps/TegraOTA folder in them)
Click to expand...
Click to collapse
Ok i followed the http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
I got to "On the tablet, select "recovery reboot"
But i didn't see it so i selected reboot, i rebooted and was on stock i think?
1) I can see that a few more steps and i'm rooted.
But i'm nervous to try this again from that point.
Should i just start at unlocking the boot loader?
2) Is rooting the device permanently unlocking the boot loader?
3) can i just no OTA from unlocking the boot loader part?

Ok i got to side loader and in the command it says error can't find device and there's an android guy on his back with a red statement mark.
So I'm in developer USB.
I have unlocked the boot loader
I'm flashing the recovery
And i get to restart in recovery.
Then i get the menus to side load the supersu.zip
I renamed it with out caps, i even made a folder in C:\Program Files\Minimal ADB and Fastboot.
Cause it installed at C:\Program Files (x86)\Minimal ADB and Fastboot.
just to avoid the (x86)
when i try and leave the menu to reset it asked me to root, but i had the error so don't want to brick it if rooting with an error on side loading supersu.zip
What do i do?
Thank you...

says
loading: 'supersu.zip'
error: device '(null)' not found
And no android guy on his back this time.
A hat with a refresh orange symbol.

l337g0g0 said:
says
loading: 'supersu.zip'
error: device '(null)' not found
And no android guy on his back this time.
A hat with a refresh orange symbol.
Click to expand...
Click to collapse
You have unlocked bootloder and installed cwm recovery so yay! Download the SuperSU file on your tablet. Make sure you know where it downloaded to. Boot your tablet o to fastboot menu using the power/vol down. Select recovery mode using volume then power to select. Chose install zip then from sdcard (not the sdcard1) chose 0/ then search for where you put SuperSU and select it. Install. Then navigate to reboot. If asked to fix root pick yes
Sent from my Nexus 5 using Tapatalk

frenziedfemale said:
You have unlocked bootloder and installed cwm recovery so yay! Download the SuperSU file on your tablet. Make sure you know where it downloaded to. Boot your tablet o to fastboot menu using the power/vol down. Select recovery mode using volume then power to select. Chose install zip then from sdcard (not the sdcard1) chose 0/ then search for where you put SuperSU and select it. Install. Then navigate to reboot. If asked to fix root pick yes
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I don't have an SD card ATM. LOL
Why is the command with ADB not working?

l337g0g0 said:
I don't have an SD card ATM. LOL
Why is the command with ADB not working?
Click to expand...
Click to collapse
You don't need a card the sdcard referee to is your internal memory on your tablet. Not sure why ADB isn't working but I had a similar issue with cwm once.

frenziedfemale said:
You don't need a card the sdcard referee to is your internal memory on your tablet. Not sure why ADB isn't working but I had a similar issue with cwm once.
Click to expand...
Click to collapse
Ok that installed it.
WOW thank for that.
I guess I'm rooted, how do i test it and what does being rooted do for me?
Thank you....

Did you go back and flash the nomoreOTA zip? That is the most important part!
Sent from my Nexus 5 using Tapatalk

frenziedfemale said:
Did you go back and flash the nomoreOTA zip? That is the most important part!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok i just flashed nomoreOTA.zip.
It said the file was deleted and was a success.
I guess i can use the internet now?
I'm so nervous to turn the internet on and have the thing reset...
Did i need to run supersu to keep it rooted or always rooted until i use supersu to full unroot.
Thank you...

Xposed?

Has anyone attempted to install xposed on the honor 8?

Yes, works. Arm64.

I can confirm, XPosed can be installed...
Albeit it seems to have a "small" bug - for me the dialer did stop working when xposed was installed (could not make any call)
V86 ARM64 xposed by rovio...
will need to investigate further.
Can anyone confirm/deny/did find a workaround?

I have xposed and dialer is working fine. Maybe it's some particular mod you've installed.

I tried installing xposed from this link http://dl-xda.xposed.info/framework/sdk23/arm64/ but I'm always getting a bootloop. Did you use another zip file?

ppalfinger said:
I tried installing xposed from this link http://dl-xda.xposed.info/framework/sdk23/arm64/ but I'm always getting a bootloop. Did you use another zip file?
Click to expand...
Click to collapse
For me, xposed did work using magisk + systemless xposed (material xposed intaller + v86.5); as well as using v86 - i think the version you posted.
I could revert my previous dialer problem by rebooting several times till all files have been treated by xposed as they should have been...

DThought said:
I can confirm, XPosed can be installed...
Albeit it seems to have a "small" bug - for me the dialer did stop working when xposed was installed (could not make any call)
V86 ARM64 xposed by rovio...
will need to investigate further.
Can anyone confirm/deny/did find a workaround?
Click to expand...
Click to collapse
I confirm the 'Dialer' bug you're facing. I have faced the same bug on all of the Honor devices I have owned. Whenever I hit the 'Call' button, the app crashes. A simple reboot does fixes the problem but it soon re-appears. No fix for it though.

DThought said:
For me, xposed did work using magisk + systemless xposed (material xposed intaller + v86.5); as well as using v86 - i think the version you posted.
I could revert my previous dialer problem by rebooting several times till all files have been treated by xposed as they should have been...
Click to expand...
Click to collapse
so how did you do this? i only read quick on the magisk thread but it said to flash magisk on a unrooted newly wiped phone.
is this true or can i flash it on my newly rooted honor 8?
hackslash said:
I confirm the 'Dialer' bug you're facing. I have faced the same bug on all of the Honor devices I have owned. Whenever I hit the 'Call' button, the app crashes. A simple reboot does fixes the problem but it soon re-appears. No fix for it though.
Click to expand...
Click to collapse
is it still possible to accept calls when the dialer is bugged and crashes?
also, which xposed version did you use?

JimZiii said:
so how did you do this? i only read quick on the magisk thread but it said to flash magisk on a unrooted newly wiped phone.
is this true or can i flash it on my newly rooted honor 8?
is it still possible to accept calls when the dialer is bugged and crashes?
also, which xposed version did you use?
Click to expand...
Click to collapse
About magisk,
you have to unroot your device from SuperSU. After that flash the stock boot image if available (unrooting from SuperSU usually suffices but if it doesn't works, it better to flash stock boot image)
About Xposed dialer bug (on EMUI only), yes as far as I know, I never experienced any crashes while accepting calls.

hackslash said:
About magisk,
you have to unroot your device from SuperSU. After that flash the stock boot image if available (unrooting from SuperSU usually suffices but if it doesn't works, it better to flash stock boot image)
About Xposed dialer bug (on EMUI only), yes as far as I know, I never experienced any crashes while accepting calls.
Click to expand...
Click to collapse
i feel extremely stupid here. i'm reading on the magisk thread and i don't understand at all.
i got a honor 8 (FRD-L09) and i've rooted it, like i mentioned earlier.
can you please help me with the steps i need to take to unroot and whatever else i need to do to flash magisk?
i can't find stock rom for my FRD-L09, so what do you suggest? just doing a full factory reset, flashing twrp, flashing magisk, rooting, restoring to the backup i create before doing the factory reset.
what do you think about those steps and in that order? if you think i need to change something or add another step please let me know.
not sure if that's enough to unroot the device, i'm also really uncertain about the correct magisk version/file i need to flash for my device. other xposed versions have different files for arm, arm64 and x86, but here there's only one file. am i missing something or does this work on all versions? or have i misunderstood how it works?
sorry about throwing so many questions at you but i'm really confused about this.

JimZiii said:
i feel extremely stupid here. i'm reading on the magisk thread and i don't understand at all.
i got a honor 8 (FRD-L09) and i've rooted it, like i mentioned earlier.
can you please help me with the steps i need to take to unroot and whatever else i need to do to flash magisk?
i can't find stock rom for my FRD-L09, so what do you suggest? just doing a full factory reset, flashing twrp, flashing magisk, rooting, restoring to the backup i create before doing the factory reset.
what do you think about those steps and in that order? if you think i need to change something or add another step please let me know.
not sure if that's enough to unroot the device, i'm also really uncertain about the correct magisk version/file i need to flash for my device. other xposed versions have different files for arm, arm64 and x86, but here there's only one file. am i missing something or does this work on all versions? or have i misunderstood how it works?
sorry about throwing so many questions at you but i'm really confused about this.
Click to expand...
Click to collapse
Take a complete backup just in case.
Perform a full unroot via SuperSU (find it in Settings). It will restore the modded files with the original ones hence reverting your boot image to the stock one.
Perform a full Factory reset. (remember to backup crucial data before attempting it)
Download B101 FRD-L09 stock ROM from here: http://loadbalancing.modaco.com/download.php?file=dload-honor-8-frdl09-frd-b101.zip
Extract the downloaded zip. There will be two folders, 'Part 1' and Part 2'. On your external SD card, create a folder 'dload'. Copy 'Update.APP' from 'Part 1' to the dload folder in your SD card. Power down the device. Hold Power Button + Volume Up + Volume Down buttons until you see the Honor logo. Your device will now automatically start installing the complete stock ROM. If in case your device boots to TWRP, then follow the below steps:
Download Huawei Update Extractor from here: http://forum.xda-developers.com/showthread.php?t=2433454
Use Huawei Update Extractor to extract RECOVERY from the Update.APP inside 'Part 1'.
Use 'fastboot' to flash the stock recovery.
Now try installing the Update.APP. This time it will work. Repeat the steps for Update.APP inside 'Part 2'
You're now on fresh stock ROM.
Download magisk from http://forum.xda-developers.com/devdb/project/dl/?id=19960&task=get and flash it via TWRP.

hackslash said:
Take a complete backup just in case.
Perform a full unroot via SuperSU (find it in Settings). It will restore the modded files with the original ones hence reverting your boot image to the stock one.
Perform a full Factory reset. (remember to backup crucial data before attempting it)
Download B101 FRD-L09 stock ROM from here: http://loadbalancing.modaco.com/download.php?file=dload-honor-8-frdl09-frd-b101.zip
Extract the downloaded zip. There will be two folders, 'Part 1' and Part 2'. On your external SD card, create a folder 'dload'. Copy 'Update.APP' from 'Part 1' to the dload folder in your SD card. Power down the device. Hold Power Button + Volume Up + Volume Down buttons until you see the Honor logo. Your device will now automatically start installing the complete stock ROM. If in case your device boots to TWRP, then follow the below steps:
Download Huawei Update Extractor from here: http://forum.xda-developers.com/showthread.php?t=2433454
Use Huawei Update Extractor to extract RECOVERY from the Update.APP inside 'Part 1'.
Use 'fastboot' to flash the stock recovery.
Now try installing the Update.APP. This time it will work. Repeat the steps for Update.APP inside 'Part 2'
You're now on fresh stock ROM.
Download magisk from http://forum.xda-developers.com/devdb/project/dl/?id=19960&task=get and flash it via TWRP.
Click to expand...
Click to collapse
thnx. i followed your steps, with a few added ones. i didn't realize that my bootloader would lock up again after flashing stock so i had to unlock it and reflash twrp.
i did wonder about the root since all phones have different root versions and he's offering a one for all version, but i flashed it and i now got working root.
still not done tho, still got to install the magisk manager and xposed
but thank you so much for you help, really felt like i was fumbling in the dark there for a moment before asking you lol
EDIT:
that it let's you turn the root on and off with a switch is ingenious. but what does it mean that google pay is not working while root is on?

JimZiii said:
that it let's you turn the root on and off with a switch is ingenious. but what does it mean that google pay is not working while root is on?
Click to expand...
Click to collapse
Yes, while the root is on, all applications that include the 'SafetyNet' check will refuse to work (such as Android Pay, Pokemon Go). When you switch it off, everything will start to work again.

hackslash said:
Yes, while the root is on, all applications that include the 'SafetyNet' check will refuse to work (such as Android Pay, Pokemon Go). When you switch it off, everything will start to work again.
Click to expand...
Click to collapse
yea that was just me remembering it wrong, thought it said google pay instead of android pay, so when i googled it i didn't really find anything which made me wonder what this mysterious google pay app was lol
but now i googled the correct name and found it right away.
but yea, thnx a lot for you help and time

Does anyone have issues playing videos with magisk installed, and I mean the flashable magisk not just the magisk manager app

Hello
I'm looking for a module which permit to center clock in statut bar .
Someone can help me please ?

Someone has tested Gravity Box ?
Works fine ?

Some features of GravityBox are working, some not.
Changes in statusbar are not working.

Nas42O said:
Hello
I'm looking for a module which permit to center clock in statut bar .
Someone can help me please ?
Click to expand...
Click to collapse
Not a perfect solution but try Flat Style Indicators.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
Nas42O said:
Someone has tested Gravity Box ?
Works fine ?
Click to expand...
Click to collapse
There is a rule to check if modules will work flawlessly on your device or not. It's simple. All modules that were designed keeping AOSP in mind will not work. EMUI is a completely different iteration if Android and hence many of the options in Gravity Box will not work on EMUI.

hackslash said:
Not a perfect solution but try Flat Style Indicators.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
There is a rule to check if modules will work flawlessly on your device or not. It's simple. All modules that were designed keeping AOSP in mind will not work. EMUI is a completely different iteration if Android and hence many of the options in Gravity Box will not work on EMUI.
Click to expand...
Click to collapse
Thanks for your answer..
I already tested flat style bar but i got some issues .. :/
Gravity box has many customisations, but if almost all not working.. :s

UHANS Note 4 - Development & Support

In order to keep this thread clean, please use this one to discuss about Development, Support or Software Updates.​
HOW-TO Root, Install Custom Recovery (TWRP) and Restore Stock ROM guide: https://docs.google.com/presentation/d/1NJcDBkLk8zMwyv2BTqRjn2NB_ZOWKjP1fRpSVr44Oxk
ROMs:
To avoid any possible issue, do not forget to backup your NVRAM so that you won't risk to lose your IMEI. How-to: http://www.anythingultimate.in/2015/11/how-to-backup-your-nvram-partition.html
Stock (Android 7.0)
- 20170731: https://mega.nz/#!9FkjwBCD!d6fSR7Pptp9h71tgdbH5TDVf6OihNjlUGnYeKriiqTg
DO NOT USE THE "Format All & Download" OPTION IF YOU CARE ABOUT YOUR IMEI! Choose "Firmware Upgrade" instead.
Previous Releases:
None yet.
Flash Tool
- Latest SP Flash Tool for Windows and Linux: https://mega.nz/#F!dYUm0TbB!SWeMLb5Wu1NbRzTPQ8-s_A​
Recovery:
- TWRP 3 by @jemmini : https://mega.nz/#F!YAtgQbxZ!N3H1P3NFH9O5zA5qyzTYBQ​
Root:
Rooting Methods (if you are on Stock ROM)
- SuperSU (flashable using TWRP): http://forum.xda-developers.com/apps/supersu​
Extras (Root-Only):
Customization
- Xposed Framework (not available on Nougat yet): http://forum.xda-developers.com/showthread.php?t=3034811​
Useful Third-Party Apps:
Battery Life
- Amplify: https://play.google.com/store/apps/details?id=com.ryansteckler.nlpunbounce&hl=en
- Greenify: https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en​

This ROM is for MT6737M, I want another for MT6737, Can anybody send me? Cause I didn't save and my phone is in bootloop now. Thanks..

robotomi1996 said:
This ROM is for MT6737M, I want another for MT6737, Can anybody send me? Cause I didn't save and my phone is in bootloop now. Thanks..
Click to expand...
Click to collapse
Don't worry, that's how Mediatek handles the scatter on MT6737 devices. You can use it without any issue.

Alberto96 said:
Don't worry, that's how Mediatek handles the scatter on MT6737 devices. You can use it without any issue.
Click to expand...
Click to collapse
But not working. The .zip is injured. The system part is not okay.

robotomi1996 said:
But not working. The .zip is injured. The system part is not okay.
Click to expand...
Click to collapse
I used it yesterday, this is weird. I'll check again and let you know what happened with the upload.
P.S.: meanwhile, try to redownload the archive.

Alberto96 said:
I used it yesterday, this is weird. I'll check again and let you know what happened with the upload.
P.S.: meanwhile, try to redownload the archive.
Click to expand...
Click to collapse
I tried to root with many variations, but not worked, and now **** everything.. But it's a good phone.
NOW, DOANLOADED AGAIN THE ROM AND NOW WORKING, THANK YOU VERY MUCH. =))))))
Have you got an idea to root uhans note 4?

robotomi1996 said:
I tried to root with many variations, but not worked, and now **** everything.. But it's a good phone.
NOW, DOANLOADED AGAIN THE ROM AND NOW WORKING, THANK YOU VERY MUCH. =))))))
Have you got an idea to root uhans note 4?
Click to expand...
Click to collapse
Oh great. I will add the link to a working TWRP soon in order to root it.
UPDATE: Done.

I installed your twrp without problem in the flashtool, but if I push the buttons the original recovery comes in.
My biggest problem that after the rom installing, i haven't got IMEI numbers and I can't calling. I tried some options for the imei write, but not working.
Have you got an idea?
Thank!

robotomi1996 said:
I installed your twrp without problem in the flashtool, but if I push the buttons the original recovery comes in.
My biggest problem that after the rom installing, i haven't got IMEI numbers and I can't calling. I tried some options for the imei write, but not working.
Have you got an idea?
Thank!
Click to expand...
Click to collapse
I guess you flashed the firmware incorrectly (Format All option instead of Firmware Upgrade/Download Only probably).
On XDA-Developers it isn't allowed to talk about IMEI modifications so you need to use Google for that.

I used Download and Format all.
And can you help me in privat message?
And what about recovery?
I think if I can install the twrp, I could root, and change the imei too.
Thank you very much your support!

robotomi1996 said:
I used Download and Format all.
Click to expand...
Click to collapse
Then you missed my alert in the first post, it is clearly written.
Alberto96 said:
DO NOT USE THE "Format All & Download" OPTION IF YOU CARE ABOUT YOUR IMEI! Choose "Firmware Upgrade" instead.
Click to expand...
Click to collapse
robotomi1996 said:
And can you help me in privat message?
Click to expand...
Click to collapse
No i am sorry, i cannot provide any support for IMEI.

And Can you send me your Uhans Note 4 nvram.bin? I just want to write back my original imei adress. Please..

Thank you very much your support bro!
Finally I rooted my phone with your twrp and made an NVRAM from my scatter file and now everything is working. I wrote back my imei with just some number.. *#6813#*
Have a nice day

Thank you for ROOT solution.
I have one question. Why Uhans is killing my RECENT APPS every time i turn off display? Apps should work in background but Uhans or maybe Android is killing them. It's frustratin becouse I have a lot of free RAM. Do you have same problem? Any solution?
Regards

How to install Miui Custom OS on Uhans Note 4
Pls guys. I need help on how to install miui custom os on my uhans note 4 that is run pure android 7.0
Pls reply asap.

OTA update
My stock note4 will not update,it says new update available but download stays at 0%

Moto One 5G Ace Rooted with TWRP using stock Firmware

First of all, I am not a dev and this write up contains steps used by various devs to achieve fulll root. For some, these steps have worked out well. But, not for me. I had issues with some of the steps not fully working as they should, so I did some research until I could piece together something that worked for me. Here's what I did and managed to get fully rooted using the boot.img from the stock firmware after doing all the steps from this link Articul8Madness's Rooting Guide and couldn't get full root access even after using the steps from this link Articul8Madness's Guide for R/W Access. As I have said, these steps worked for most people. I wasn't one of them.
I followed the steps up to the step where the boot.img is modded by Magisk. This is where I omitted using the modded boot.img and used the original boot.img from the stock firmware and I then ran the flashfile script as mentioned in the steps. After everything was applied I then, rebooted the phone, started setup, disabled System Updates, and I then proceeded to install TWRP using the steps from this link https://drive.google.com/drive/folders/1KZ0xhstQ9V_7TYt3xs7P5XdroYX61CEA after opening Minimal ADB and Fastboot applying these scripts
adb reboot fastboot
then apply this
fastboot flash recovery twrp-3.5.2_10-kiev.img
I then rebooted into recovery and installed TWRP to all available partitions. I then installed Magisk, enabled Systemless Hosts in settings, and rebooted. Afterwards, I used the steps here Munjeni's RW in Super Partition Tool to get RW in super partitions after downloading and using superrepack. I had omitted the ./superrepack /dev/block/bootdevice/by-name/super system_a in order to have it applied to all available partitions. Everything worked out great. I then rebooted, updated Magisk, installed Root Checker and Root Explorer with Superuser root access. I then installed Adaway from https://github.com/AdAway/AdAway and clicking on the Get It On AdAway image. Anything that requires root access here on out, can now be installed. As for the SafetyNet issue, I have not had any problem with it at all even though the check had failed. All is now working well and I sincerely hope that this guide will help others as it have helped me. I may have done this write up but, all credits goes to the true devs.
Time for devs to start making custom Roms now that TWRP can be installed.

Your first link doesn't work for me. The Adaway link works. FYI.

RETIEF said:
Your first link doesn't work for me. The Adaway link works. FYI.
Click to expand...
Click to collapse
WOW!!! I see what I did wrong. All links are now working.

Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?

eurovive said:
Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?
Click to expand...
Click to collapse
Sorry, but you will have to ask one of the Devs in the links that I've provided in the OP. Perhaps they are more suited to help with that.

eurovive said:
Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?
Click to expand...
Click to collapse
Linux will work fine. All the commands required are done thru a terminal session. Use a text editor to get the long unlock code from the phone.
Good luck.

Ok about terminal. I used cmd , but bootloader cannot be unlocked official way nor at&t unlockable coz i don't live in usa.I will try 3rd party helpers.

iceman19631 said:
First of all, I am not a dev...
Click to expand...
Click to collapse
You did a fantastic job. This worked perfectly. Some notes:
1) You must install the Motorola device driver in Windows. Doesn't work with leftover drivers that seem to communicate just fine with the phone.
2) You have to unlock the bootloader via Motorola's website if it is locked. Key step not communicated: when you enter in the code to unlock at the computer with a fastboot command the phone will ask you to confirm that you want it unlocked. If you don't look at your phone and answer the question it will time out.
3) When you boot into TWRP it will ask for a password if you have a screen lock set. The password is your screen lock. No big deal.
4) Once you are in TWRP install the Magisk Zip file and let it do its magic.
5) Enjoy a fully unlocked stock firmware. It's awesome.
Thanks again.

egalambos said:
You did a fantastic job. This worked perfectly. Some notes:
1) You must install the Motorola device driver in Windows. Doesn't work with leftover drivers that seem to communicate just fine with the phone.
2) You have to unlock the bootloader via Motorola's website if it is locked. Key step not communicated: when you enter in the code to unlock at the computer with a fastboot command the phone will ask you to confirm that you want it unlocked. If you don't look at your phone and answer the question it will time out.
3) When you boot into TWRP it will ask for a password if you have a screen lock set. The password is your screen lock. No big deal.
4) Once you are in TWRP install the Magisk Zip file and let it do its magic.
5) Enjoy a fully unlocked stock firmware. It's awesome.
Thanks again.
Click to expand...
Click to collapse
You're very welcome. And thanks for the added info, I forgot to add that in the steps. Thanks again.

iceman19631 said:
You're very welcome. And thanks for the added info, I forgot to add that in the steps. Thanks again.
Click to expand...
Click to collapse
Any plans for an update to 3.6.0 for Android 11??

egalambos said:
Any plans for an update to 3.6.0 for Android 11??
Click to expand...
Click to collapse
Sorry for the late reply. I really haven't decided yet if I'll update to Android 11. I would imagine it'll be rooted in the same manner. If I could get ahold of the US version, I may give it a shot.

iceman19631 said:
Sorry for the late reply. I really haven't decided yet if I'll update to Android 11. I would imagine it'll be rooted in the same manner. If I could get ahold of the US version, I may give it a shot.
Click to expand...
Click to collapse
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.

egalambos said:
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.
egalambos said:
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I don't have an answer for that at this time since I'm still on 10. That'd be too much like a blind man in a desert looking for shade and telling another which way to go.

Greetings, I have a few questions. re the Moto G 5G (One 5G Ace)
I've not found a TWRP for this phone yet which were you using?
In other phones it was important to backup the IMEI (EFS ) and 'persistent' partitions. Do we not do that with this phone as well?
Thx in advance

Sorry for the late reply. I used this version of TWRP twrp-3.5.2_10-kiev.img. As far as the IMEI (EFS) question, it wasn't required when using this root process. However, you can back those up if you like.