Hello,
I try to Unbrick my A500 with Acer_A500_0.000.00_1.122.01_EMEA_GEN5_update.zip.
At the first time it works, I can boot and I want to flash the system.ing and boot.img for Acer_A500_1.141.07_COM_GEN1 with the Acer ROM Flasher to get german language support.
The HowTo in den Android-hilfe tells my that I will get an error after reboot (right) and than I have to flash another update (can´t post link because I´m a noobie)
Now I´m stick in a bootloaderloop (android logo) and nothing will help.
I try flash the unbrick update again, but the only thing I get is the Bootloop at the android logo.
I need some serious help for this.
Thanks guys
triebstahl
Doesn't sound like your getting into recovery with the update.zip. make sure you keep holding down the vol- button until you see the little green man. Don't let go of it when you see the big "Acer".
After doing the update.zip to unbrick, run itsmagice BEFORE running Acer Rom Flasher. Then flash the boot and system images from that thread. Then reboot after the 6 minute window. It should boot normally.
Or just stick to the instructions in the other thread... I think your just not getting into recovery correctly.
PS.. Acer Rom Flasher is going to get an update when I get the chance.
triebstahl said:
Hello,
Now I´m stick in a bootloaderloop (android logo) and nothing will help.
Click to expand...
Click to collapse
Have you already tried to wipe your device?
sc2k said:
Have you already tried to wipe your device?
Click to expand...
Click to collapse
this seems to be the solution. Thanks for your [TIP]
Well now I´m chinese, but I try the Acer_A500_0.000.00_1.122.01_EMEA_GEN5_update now.
Edit: It does work. Now I try the boot.img and system.img.
i had same problem
I had the same problem with that zip. It was corrupted. Found an other source update.acer.zip and it worked, but some chinese apps came with it. List few other thing. The update.acer.zip would hot boot. The zip had folder with an other update.acer.zip in it. After extracting the zip from the zip it worked.
triebstahl said:
Hello,
I try to Unbrick my A500 with Acer_A500_0.000.00_1.122.01_EMEA_GEN5_update.zip.
At the first time it works, I can boot and I want to flash the system.ing and boot.img for Acer_A500_1.141.07_COM_GEN1 with the Acer ROM Flasher to get german language support.
The HowTo in den Android-hilfe tells my that I will get an error after reboot (right) and than I have to flash another update (can´t post link because I´m a noobie)
Now I´m stick in a bootloaderloop (android logo) and nothing will help.
I try flash the unbrick update again, but the only thing I get is the Bootloop at the android logo.
I need some serious help for this.
Thanks guys
triebstahl
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1132760 try this
Hi to All,
I am from Germany and ordered the KF three days ago.
I just gave my jailbroken IPAD1 to my wife and am looking for new adventures...
I want to be prepared for this gadget so I did a lot of reading in these forums here.
Some questions did come up and I hope you will help me.
My strategy when I get it are:
I) Connect KF with adb and Root KF
II) Install Recovery
III) Install FireFireFire
IV) Install MoDaCo Custom ROM or Energy 3.15 Rom
V) Have fun
I am a little confused about the different options for Rooting and Recovery
1) Use the Kindle Fire Utlity 0.9.3
a) Permanent Root (#3)
b) TWRP (#5)
c) FireFireFire (#6)
d) Do I have to switch a bootmode ? (#1)
2) a) Root the Device with Burrito ?
b) Install CWM-Based Touch Recovery 5.0.2.7 for Kindle Fire
3) Also when I have successfully rooted and installed recovery and want to flash the rom, do I have to press certain buttons in TWRP ? Wipe,clean, and so on ?
4) How much space do I have for Apps ? It is depending on the rom or is it fix so that I have to partition certain sections ?
If I have to partition the device what are recommended sizes and do I do it before I flash the rom or after ?
5) I also downloaded a cm7wipeall.zip. For what do I need this ?
You see, a lot of questions I hope I don´t overwhelm you guys...
I cant wait for the Kindle...
bambi007 said:
Hi to All,
I am from Germany and ordered the KF three days ago.
I just gave my jailbroken IPAD1 to my wife and am looking for new adventures...
I want to be prepared for this gadget so I did a lot of reading in these forums here.
Some questions did come up and I hope you will help me.
My strategy when I get it are:
I) Connect KF with adb and Root KF
II) Install Recovery
III) Install FireFireFire
IV) Install MoDaCo Custom ROM or Energy 3.15 Rom
V) Have fun
I am a little confused about the different options for Rooting and Recovery
1) Use the Kindle Fire Utlity 0.9.3
a) Permanent Root (#3)
b) TWRP (#5)
c) FireFireFire (#6)
d) Do I have to switch a bootmode ? (#1)
2) a) Root the Device with Burrito ?
b) Install CWM-Based Touch Recovery 5.0.2.7 for Kindle Fire
3) Also when I have successfully rooted and installed recovery and want to flash the rom, do I have to press certain buttons in TWRP ? Wipe,clean, and so on ?
4) How much space do I have for Apps ? It is depending on the rom or is it fix so that I have to partition certain sections ?
If I have to partition the device what are recommended sizes and do I do it before I flash the rom or after ?
5) I also downloaded a cm7wipeall.zip. For what do I need this ?
You see, a lot of questions I hope I don´t overwhelm you guys...
I cant wait for the Kindle...
Click to expand...
Click to collapse
Ok I can answer some of your questions...
In TWRP no you do not need to change bootmodes to root.
Yes you should wipe everything in TWRP before you flash(unless otherwise instructed).
This includes cashe/dalvik cashe and factory reset. No need to wipe SDcard.
As for #5 You don't need that file... I flashed CM7/CM9 with trouble without that file.
I hope this helps. Good luck with your kindle!
Ganz ruig.
Erstmal http://forum.xda-developers.com/showthread.php?t=1399889&highlight=german Installieren.
Ggf. das beachten http://forum.xda-developers.com/showpost.php?p=21638862&postcount=745
Dann einfach Roms runterladen und twrp oder cwm starten ( wenn du den Kindle einschaltest auf die LED achten und wenn das grün dunkler wird nochmal den Powerknopf drücken und kuz halten
Ok, thanks for your contribution.
But what about partitioning ?
Would you recommend repartition the kindle ?
Or is there enough space to install apps ?
My path was:
- Stock Kindle Fire (622 I think)
- Used KFU to install perma root
- Installed TWRP
- Backed up everything in TWRP
- Flashed a ROM (Butta ICS, it works pretty well)
I didn't bother with FireFireFire or butta.
You dont have to repartitioning your device. there would be enough space for the apps may about 1 GB.
Hi there. I've been a member to your site yesterday. ZTE Blade phone does not work for a few months. After installing the rom was brick my phone. I have tried various methods, but the result did not get on your site. Opens up the phone in recovery mode after flash. I installed rom in recovery mode, but the phone still did not work. Just opening up recovery mode. What should I do after installing the rom Recovery mode? I need immediate help. Continuous recovery mode does not opening the boot rom installed on the phone. The methods I tried, I still do not get results. Please help me. I tried but it was good though the site is written matters. Finally, I'm sorry I have opened this topic in the wrong place. If you can help me fix my phone thank you very much.
dr_jones12 said:
Hi there. I've been a member to your site yesterday. ZTE Blade phone does not work for a few months. After installing the rom was brick my phone. I have tried various methods, but the result did not get on your site. Opens up the phone in recovery mode after flash. I installed rom in recovery mode, but the phone still did not work. Just opening up recovery mode. What should I do after installing the rom Recovery mode? I need immediate help. Continuous recovery mode does not opening the boot rom installed on the phone. The methods I tried, I still do not get results. Please help me. I tried but it was good though the site is written matters. Finally, I'm sorry I have opened this topic in the wrong place. If you can help me fix my phone thank you very much.
Click to expand...
Click to collapse
Do you can get into recovery?
Telefonu recovery moda alabiliyorum flash yaparak. Ancak rom yükledikten sonra telefona reset atmama rağmen yine recovery modda açılıyor. Kurtarma derken ne tür bir kurtarmadan söz ediyorsunuz?
dr_jones12 said:
Telefonu recovery moda alabiliyorum flash yaparak. Ancak rom yükledikten sonra telefona reset atmama rağmen yine recovery modda açılıyor. Kurtarma derken ne tür bir kurtarmadan söz ediyorsunuz?
Click to expand...
Click to collapse
Please only write in english , this even stands in the forum rules.
Sorry about that. I can flash recovery mode by phone. However, despite me take reset the phone after installing the rom recovery mode opens. You are talking about saying what kind of recovery can recover?
Great news, we can flash nougat with the new flashtool 0.9.23.0.
https://twitter.com/Androxyde
Download: http://www.flashtool.net/downloads_windows.php
just wanted to share that flashtool by default won't flash F5122 with 34.2.A.0.266 (Nougat) as there's no specific script for it
I've tested copying F5121 34.2.A.0.266 file and renaming it by just changing to F5122, flashed successfully and phone is working great
my first Sony phone so I've unlocked the bootloader (thought it would be necessary) and now I just found out about the functionality loss related to it... great
F5122 does not work with flashtool
Gesendet von meinem SGP621 mit Tapatalk
Random reboot after flashing
have a US Xperia X and I flashed the "Customized UK" ftf. It flashed successfully, however, my device restarts randomly.( It restarted twice during the initial device setup and then randomly while using the phone.)
While flashing (34.2.A.0.266), I wanted to wipe my phone completely and I checked "DIAG" and "SSD" in the wipe window of the flash tool. Then realized according to a thread that they were new options.
There is no flash script for the current US firmware (34.0.A.2.292) Is there any way to recover my phone to normal working state?
Yesterday i was installed flashtool latest version but after installation flashtoon is not running it is showing some java error.
Fashtool Firms Support
F5121_34.0.A.1.264
F5121_34.0.A.1.277
F5121_34.2.A.0.266
F5122_34.2.A.0.266
Does not Support 5122. 266
Gesendet von meinem F5122 mit Tapatalk
EDIT: Magisk V13 is fully compatible with Sony stock roms. Please refer to the official release! https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Let me explain before you complain about: "Magsik v12 is already Sony compatible!"
Yes, the installer is - but it only works on devices with disabled Sony RIC service.
TL;DR: Download in attachments.
Do you need this?
If you are using Sonys stock unpatched boot image or drm-fix without RIC disabler you should use this version of magisk, since it includes a RIC disabler.
Recommended workaround without altered Magisk:
1. Patch your boot image with rootkernel tool (disable sony ric at least): https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
2. Use orignal magisk with the patched boot image: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Original thread:
How and why
I was stuck with debugging an issue regarding MagiskSU for hours. The Magisk installation was fine, but somehow MagiskSU was not there which made Magisk useless for me (=> no MagiskHide, no modules, no hosts support, etc). I finally realized that Sonys RIC service prevents the magic_mask.sh script (the script that enables Magisk and its features during boot) from symlinking the su binary and magiskpolicy in /sbin
But it works for me without your patch!?
Did you use rootkerneltool from @tobias.waldvogel with your current kernel? It is capable of disabling Sony RIC aswell and maybe you did that or are using a kernel without Sony RIC.
The fix (for developers) @topjohnwu
magic_mask.sh, add this in late_start service mode:
Code:
#Try to disable Sony RIC
echo 0 > /sys/kernel/security/sony_ric/enable
if [ $? -eq 0 ]; then
log_print "* Sony RIC service disabled";
else
log_print "* Sony RIC service NOT disabled :("
fi
Proof that it works and passes SafetyNet (Z5 compact with Android 7)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Original thread
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Flashing on z3+ and working flawlesly
If using kernel that use ta_poc got bootloop, but if use kernel with drmfix its work
Fauzi alaik said:
Flashing on z3+ and working flawlesly
If using kernel that use ta_poc got bootloop, but if use kernel with drmfix its work
Click to expand...
Click to collapse
Just tried latest ta_poc (yesterdays release) and it works for me. But since latest ta_poc also supports disabling Sony RIC, you dont need this patched magisk version if you've disable it with ta_poc (or rootkerneltool).
@[email protected],
reicht es nicht aus, ein custom kernel zu flashen bei dem die sony_ric schon deaktiviert wurde?
Gestern habe ich die original magisk v12 geflasht und es hat funktioniert.
Also ich habe auf meinem z5 den androplus kernel, chainfires supersu, die letzte marshmallow rom und es funktioniert.
Oder hab ich irgendwas falsch verstanden?
MysticEnforcer said:
@[email protected],
reicht es nicht aus, ein custom kernel zu flashen bei dem die sony_ric schon deaktiviert wurde?
Gestern habe ich die original magisk v12 geflasht und es hat funktioniert.
Also ich habe auf meinem z5 den androplus kernel, chainfires supersu, die letzte marshmallow rom und es funktioniert.
Oder hab ich irgendwas falsch verstanden?
Click to expand...
Click to collapse
Nope, all well,
take a look at OP's edit:
EDIT: Only required if you didn't patch your boot image with ta_poc or rootkerneltool and disabled Sony RIC with it, if you already patches Sony RIC with these tools, go to this thread instead:
Click to expand...
Click to collapse
i... appear to have bricked my z3 my flashing this. i'm sure i must've missed something crucial.
Check magisk.log in /cache using recovery
Which android version did you use? Modified boot image? Other mods?
I keep getting the CTS profile mismatch on the Z5 Compact, even with a freshly installed ROM. Any tips?
Enable magisk hide, it works on my z5c
[email protected] said:
Enable magisk hide, it works on my z5c
Click to expand...
Click to collapse
That works for me. Thanks
Enviado desde mi D6603 mediante Tapatalk
[email protected] said:
Enable magisk hide, it works on my z5c
Click to expand...
Click to collapse
Already enabled. Even tried toggling and restarting, still fails the safetynet. Also checked the thread for solutions, tried them all and still fails... What firmware are you on?
Thats weird. Please share a copy of /cache/magisk.log
Does safetynet pass without magisk?
iArvee said:
Already enabled. Even tried toggling and restarting, still fails the safetynet. Also checked the thread for solutions, tried them all and still fails... What firmware are you on?
Click to expand...
Click to collapse
See attachment
This mod works for me with untouched stock kernel. Safety net passed, root works, everything went well. However, stock kernel also means that the phone can detect that it has been unlocked, drm-related features will not function. Is there a way to bypass this? I tried your mod with Poc-patched kernel and got bootloop (same with SuperSU or Superuser for some reason). I got my Ta backed up btw.
kientrongtran said:
This mod works for me with untouched stock kernel. Safety net passed, root works, everything went well. However, stock kernel also means that the phone can detect that it has been unlocked, drm-related features will not function. Is there a way to bypass this? I tried your mod with Poc-patched kernel and got bootloop (same with SuperSU or Superuser for some reason). I got my Ta backed up btw.
Click to expand...
Click to collapse
It's only required with stock boot bundle (and at the time I developed the fix, POC TA was broken and didn't patch Sony RIC -> see this post: https://forum.xda-developers.com/cr...ad-drm-fix-t3552893/post71663359#post71663359)
So if you use latest POC TA and disable Sony RIC with it, Magisk v12 from @topjohnwu should work
Edit: Latest PoC TA (and maybe in combination with latest .33 fw) is incompatible to Magisk. Use rootkerneltool in this case
[email protected] said:
Thats weird. Please share a copy of /cache/magisk.log
Does safetynet pass without magisk?
Click to expand...
Click to collapse
Hi! Sorry for the delay, was on vacation. Anyways, magisk.log attached. I'm not sure why it says "Permissive detected" when I didn't do anything to change the SELinux settings.
As for your other question, no. It still failed the safetynet even without magisk, and after a full wipe.
This is weird, it should pass safetynet even with unlocked bootloader (after stock reflash)
It actually sound like you are not using a stock boot image (therefore its permissive)
[email protected] said:
This is weird, it should pass safetynet even with unlocked bootloader (after stock reflash)
It actually sound like you are not using a stock boot image (therefore its permissive)
Click to expand...
Click to collapse
I can't pass SafetyNet too, when I flashed the stock firmware and boot image with unlock boot loader on Z5P .33 fw.
Is "Basic integrity" true and CTS false?
[email protected] said:
It's only required with stock boot bundle (and at the time I developed the fix, POC TA was broken and didn't patch Sony RIC -> see this post: https://forum.xda-developers.com/cr...ad-drm-fix-t3552893/post71663359#post71663359)
So if you use latest POC TA and disable Sony RIC with it, Magisk v12 from @topjohnwu should work
Edit: Latest PoC TA (and maybe in combination with latest .33 fw) is incompatible to Magisk. Use rootkerneltool in this case
Click to expand...
Click to collapse
So that's why MagiskSU wasn't installing on my phone even though I had used PoC TA...
If it's not too much to ask though could you provide a link with where to find rootkerneltool? I haven't heard of that before and are unable to find it by searching either, as I don't know what to look for, or if it's a generic Android or just Sony tool. Never mind I found it.
I want to see if I can get Magisk working on the Concept firmware for Xperia X bu it sounds like ta_poc probabbly won't be able to work with it.