Related
i tried installing a system font from the rom toolbox and when it rebboted it wasnt booting up... i can switch on my device but it remains in the glowing (X) and doesnt load up... i tried a factory reset i didnt work... i dont have a custom recovery nor do i have a nandroid backup on my device. i have rooted it using wugfresh's toolkit.
i have been trying many methods over the day and nothing seems to work. i have dowloaded a stock image from google's site but its on my pc. some help pls!!!!
i have the drivers installed on my windows 8 . atleast they were wokring intially when i got the root done on it . i have no clue what to do now !!
Your gonna have to flash the stock image from download mode. Never make changes to system files without doing a nandroid backup.
Wayne Tech Nexus
zelendel said:
Your gonna have to flash the stock image from download mode. Never make changes to system files without doing a nandroid backup.
Wayne Tech Nexus
Click to expand...
Click to collapse
i am sorry but i am new to nexus 4 ... how do i get into the download mode?
Irthu said:
i am sorry but i am new to nexus 4 ... how do i get into the download mode?
Click to expand...
Click to collapse
Read the stickies. They will get you all the info you need. If you are gonna try mods like this I would advise a full custom set up. As what your gonna do is gonna fully wipe your device.
Wayne Tech Nexus
zelendel said:
Read the stickies. They will get you all the info you need. If you are gonna try mods like this I would advise a full custom set up. As what your gonna do is gonna fully wipe your device.
Wayne Tech Nexus
Click to expand...
Click to collapse
is it possible to flash the img. file if my phone is recognised only in the bootloader mode? and i am assuming we have to flash the img. file using an adb software ?
Irthu said:
is it possible to flash the img. file if my phone is recognised only in the bootloader mode? and i am assuming we have to flash the img. file using an adb software ?
Click to expand...
Click to collapse
yes you will need to use fastboot which is part of adb
follow this thread: http://forum.xda-developers.com/showthread.php?t=2010312
PhantomGamers said:
yes you will need to use fastboot which is part of adb
follow this thread: http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
i have downloaded a zip from google's site and its about 300 odd mb. i am assuming i have to extract the the img. files and then do it ? but there are about 3-4 img. files such as :
system
boot
boot loader
radio
recovery
user data
since my phone does get into bootloader can u pls tell me which all img. files i need to flash? do i have to everyone of them?
the thread i linked answers all of your questions
(you really only need to flash the system image but to avoid confusion i would just follow the thread verbatim)
PhantomGamers said:
the thread i linked answers all of your questions
(you really only need to flash the system image but to avoid confusion i would just follow the thread verbatim)
Click to expand...
Click to collapse
thanks alot i will try doing it... i havent used the command prompt in windows ever before guess its time to learn how to do this..
I was restoring a twrp backup and when it reaches "flashing system image" in the restore process it just reboots. Ive tried a few things but cant get it going. It just bootloops.
dontbeweakvato said:
I was restoring a twrp backup and when it reaches "flashing system image" in the restore process it just reboots. Ive tried a few things but cant get it going. It just bootloops.
Click to expand...
Click to collapse
Flash the factory images with fastboot, see section 9 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Did you actually backup "system image" or just "system"? It should be only system, not the system image.
Heisenberg said:
Flash the factory images with fastboot, see section 9 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Did you actually backup "system image" or just "system"? It should be only system, not the system image.
Click to expand...
Click to collapse
That was my first rooted twrp backup on 6p. I checked everything under what to backup. It has a system and system image to backup along with everything else. I thought it was weird to have both of them because I've never seen that before in twrp.
Well im back to normal. I must of screwed up the restore with the "system" and "system image" business. What's the difference in twrp restore between the two?
dontbeweakvato said:
Well im back to normal. I must of screwed up the restore with the "system" and "system image" business. What's the difference in twrp restore between the two?
Click to expand...
Click to collapse
Honestly, I don't know. I only know that you only need to backup system, boot, and data (if you want your apps and settings).
Heisenberg said:
Flash the factory images with fastboot, see section 9 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Did you actually backup "system image" or just "system"? It should be only system, not the system image.
Click to expand...
Click to collapse
I have a soft bricked phone... I have done everything in your thread and flashing all the files worked except i get an error when flashing the system.img
it says error unable to allocate xxxxxxx bytes...? i really want my phone back to normal.. PLEAS HELP
taylorleach said:
I have a soft bricked phone... I have done everything in your thread and flashing all the files worked except i get an error when flashing the system.img
it says error unable to allocate xxxxxxx bytes...? i really want my phone back to normal.. PLEAS HELP
Click to expand...
Click to collapse
Try to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files.
indian84 said:
Try to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files.
Click to expand...
Click to collapse
I am sorry what do you mean?? what commands should I try?
taylorleach said:
I am sorry what do you mean?? what commands should I try?
Click to expand...
Click to collapse
Try this.
Reboot Bootloader again
1. fastboot erase userdata
And then follow the guide. Hopefully this will help.
indian84 said:
Try this.
Reboot Bootloader again
1. fastboot erase userdata
And then follow the guide. Hopefully this will help.
Click to expand...
Click to collapse
so, just to clarify... run the command "fastboot erase userdata" then run all of the IMG files?
taylorleach said:
so, just to clarify... run the command "fastboot erase userdata" then run all of the IMG files?
Click to expand...
Click to collapse
My bad.
use command fastboot format userdata
This will erase everything on your phone. Including photos and all the media.
After this use below command
fastboot reboot bootloader
And then follow guide and flash all IMG files.
indian84 said:
My bad.
use command fastboot format userdata
This will erase everything on your phone. Including photos and all the media.
After this use below command
fastboot reboot bootloader
And then follow guide and flash all IMG files.
Click to expand...
Click to collapse
that did not work same problem
"load_file: could not allocate 2014315040 bytes
error: cannot load 'C:\angler\images\system.img"
all other .img files i get OKAY except for system.img
PLEASE HELP ME UGG I REALLY NEED MY PHONE TO WORK AGAIN. I even tried re downloading the 6.0.1 again and also tried rebooting PC and multiple USB ports...
taylorleach said:
that did not work same problem
"load_file: could not allocate 2014315040 bytes
error: cannot load 'C:\angler\images\system.img"
all other .img files i get OKAY except for system.img
PLEASE HELP ME UGG I REALLY NEED MY PHONE TO WORK AGAIN. I even tried re downloading the 6.0.1 again and also tried rebooting PC and multiple USB ports...
Click to expand...
Click to collapse
You need to update your fastboot on your PC update everything in Android SDK or install latest minimal adb and fastboot. The system needs to be sent/flashed in parts as it's a big file. That will/should fix your issue.
matt1515 said:
You need to update your fastboot on your PC update everything in Android SDK or install latest minimal adb and fastboot. The system needs to be sent/flashed in parts as it's a big file. That will/should fix your issue.
Click to expand...
Click to collapse
I really appreciate your reply.. But i am a bit new to the Nexus and fastboot (sdk) environment. How do I update fastboot? I believe I have updated my Android Studio properly already. Is there a way to flash that system.img in stages then? I am so confused. Thanks again in advance!!!
taylorleach said:
I really appreciate your reply.. But i am a bit new to the Nexus and fastboot (sdk) environment. How do I update fastboot? I believe I have updated my Android Studio properly already. Is there a way to flash that system.img in stages then? I am so confused. Thanks again in advance!!!
Click to expand...
Click to collapse
Assuming you have Windows go to this site and download latest version(1.31) https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Read Heisenberg's thread on how to flash everything but put all your files(system, boot, bootloader, radio, boot, vendor, cache, userdata in the minimal adb and fastboot folder hold shift right click and open cmd window and flash away it will work follow Heisenberg's thread and you should be good! Good luck!
taylorleach said:
I really appreciate your reply.. But i am a bit new to the Nexus and fastboot (sdk) environment. How do I update fastboot? I believe I have updated my Android Studio properly already. Is there a way to flash that system.img in stages then? I am so confused. Thanks again in advance!!!
Click to expand...
Click to collapse
matt1515 said:
Assuming you have Windows go to this site and download latest version(1.31) https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Read Heisenberg's thread on how to flash everything but put all your files(system, boot, bootloader, radio, boot, vendor, cache, userdata in the minimal adb and fastboot folder hold shift right click and open cmd window and flash away it will work follow Heisenberg's thread and you should be good! Good luck!
Click to expand...
Click to collapse
If you already have the Android SDK it probably isn't a good idea to start installing other versions. Just go to where you installed the SDK on your PC, open SDK Manager, and update the platform-tools package.
matt1515 said:
Assuming you have Windows go to this site and download latest version(1.31) https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Read Heisenberg's thread on how to flash everything but put all your files(system, boot, bootloader, radio, boot, vendor, cache, userdata in the minimal adb and fastboot folder hold shift right click and open cmd window and flash away it will work follow Heisenberg's thread and you should be good! Good luck!
Click to expand...
Click to collapse
YOUR ARE MY BEST FRIEND THANK YOU SO MUCH!! I knew I was close to figuring it out but I seriously appreciate your help good sir.
So, to ask one more question. I flashed TWRP totally fine, but when I when to reboot after failing to find my SU.zip in my phones directory (due to 0MB detected.. i don't know why) it asked me if I wanted to root because I was currently not rooted and I just said yes.. was that why it got stuck in a bootloop? I never actually directed it at my specific SU.zip file because it wouldn't appear in the phones files?
taylorleach said:
YOUR ARE MY BEST FRIEND THANK YOU SO MUCH!! I knew I was close to figuring it out but I seriously appreciate your help good sir.
So, to ask one more question. I flashed TWRP totally fine, but when I when to reboot after failing to find my SU.zip in my phones directory (due to 0MB detected.. i don't know why) it asked me if I wanted to root because I was currently not rooted and I just said yes.. was that why it got stuck in a bootloop? I never actually directed it at my specific SU.zip file because it wouldn't appear in the phones files?
Click to expand...
Click to collapse
Yes that's why it was stuck in a boot loop, the version of SuperSU that's included in TWRP is incompatible. Which version of TWRP did you flash? You need the latest in order for it to be able to successfully decrypt your storage so you can view it.
Heisenberg said:
Yes that's why it was stuck in a boot loop, the version of SuperSU that's included in TWRP is incompatible. Which version of TWRP did you flash? You need the latest in order for it to be able to successfully decrypt your storage so you can view it.
Click to expand...
Click to collapse
To be honest, I moved the file to my phones directory from my PC and did not just copy it so I lost it lol. Could you please tell me what one I should flash so I don't mess anything up. PLEASE and THANK YOU
taylorleach said:
YOUR ARE MY BEST FRIEND THANK YOU SO MUCH!! I knew I was close to figuring it out but I seriously appreciate your help good sir.
So, to ask one more question. I flashed TWRP totally fine, but when I when to reboot after failing to find my SU.zip in my phones directory (due to 0MB detected.. i don't know why) it asked me if I wanted to root because I was currently not rooted and I just said yes.. was that why it got stuck in a bootloop? I never actually directed it at my specific SU.zip file because it wouldn't appear in the phones files?
Click to expand...
Click to collapse
+1 on Heisenberg you should use Android SDK and update properly but I knew you needed to get back up and running and figured that was the fastest way to help you. Read his thread like you would a book you will learn all you need to learn! But glad to hear I was able to help! Always use latest TWRP and SuperSU and you will be fine if you can decrypt then install SuperSU that way if not just hit cancel and adb sideload it. Look in general thread for the TWRP thread. Good luck and enjoy your working phone again!
*** NOTE: Please excuse my English.
*** WARNING: I'm not responsible if anything happens to your device, I'm just sharing my experience and what I did to fix my own phone. Proceed at your own RISK.
I bought my Nexus 6p 64gb and as soon as I took it out of the box, I went directly and followed the guide here. So i unlocked the bootloader, flashed TWRP as a custom recovery, flashed CM13 + OpenGapps.
I noticed that every time I boot my device I get this warning:
Your device is corrupt. It can’t be
trusted and may not work properly.
Visit this link on another device:
go.co/ABH
and it does not seem to be a normal warning because when my OS boots up it shows me this
"Android system:
There’s an internal problem with your device. Contact your manufacturer for details"
Later on when I updated to the latest nightly image my camera crashes and doesn't function properly. I also already has an issue with Bluetooth and "Bluetooth share" crashing but that was unrelated. Anyways I was crippled in my day to day usage. Then I thought that I need to fix this asap because it might cause performance/security/hardware problems in the future.
So basically the fix is you should flash the latest bootloader image and radio image. Personally I wanted to start clean and make sure I have no corrupted files so here is what I did,
1. What i did is erase all boot, system, kernel & recovery files by typing the below command using fastboot just incase they were corrupted,
(Note: YOU DONT NEED TO DO THIS STEP, but i prefer starting clean incase i had some corrupted files. YOU WILL ALSO LOSE ENCRYPTION DOING THE FIRST STEP)
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
Source: http://devs-lab.com/...i-nexus-6p.html
2. Then i flashed the latest factory images in this sequence using fastboot, which can be found here: https://developers.g...s/images#angler
(Note: 6.0.1 (MMB29M) was latest image at the time i did this. For people who are doing this for the first time, then you just need to download the image then extract the needed files from it)
fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
fastboot format userdata
fastboot reboot
Source: http://forum.xda-dev...operly-t3268407
3. From there i reflashed TWRP using fastboot, then flashed the latest beta SuperSU v2.62 at the time, and then CM13, then OpenGapps, then again reflashed SuperSU v2.62 just incase, lol. (Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When using TWRP before you've actually flashed SuperSU 2.50+, when you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this.)
What got fixed ?
-FIXED, this won't show up anymore:
Your device is corrupt. It can’t be
trusted and may not work properly.
Visit this link on another device:
go.co/ABH
-FIXED, this won't show up anymore:
Android system:
There’s an internal problem with your device. Contact your manufacturer for details.
-FIXED, Camera is working !
-NOT FIXED, "Bluetooth share" still crashes but I think its unrelated to this issue.
Hope this helps everyone as it helped me, thanks.
Sent from my Nexus 6P using Tapatalk
\*O / Thank you !!
Thanks, but better option? Don't reboot.
Sent from my Nexus 6P using Tapatalk
bob_mord_les said:
\*O / Thank you !!
Click to expand...
Click to collapse
Ur welcome [emoji1]
Sent from my Nexus 6P using Tapatalk
Followed your guide, thanks, but the message "Your device is corrupt. It can’t betrusted and may not work properly." still appears during a CM boot.
The message "There’s an internal problem with your device. Contact your manufacturer for details" appears when I boot into recovery (TWRP)
The camera is working now.
Also, before I was able to flash CM-13 I had to do "WIPE >> Format Data" from TWRP, otherwise CM was exiting with error 7.
The following packages were used:
original 6.0.1 (MMB29P) factory image
BETA-SuperSU-v2.66-20160103015024.zip
cm-13.0-20160115-NIGHTLY-angler.zip
open_gapps-arm64-6.0-micro-20160115.zip
twrp-2.8.7.2-angler.img
I also noticed that when rebooting into factory image, the same warning message appears as well.
Any way to fix it or did I do something wrong?
Why are people trying to fix an non issue? To get rid of the message you need to relock the bootloader which is more of a risk if your rooted. Its a message that only appears for a few seconds when you reboot and you don't need to do anything to get past it.
There is no corruption and the phone is trusted by YOU as you unlocked it and nothing else cares. Where is the issue?
g_kos said:
Followed your guide, thanks, but the message "Your device is corrupt. It can’t betrusted and may not work properly." still appears during a CM boot.
The message "There’s an internal problem with your device. Contact your manufacturer for details" appears when I boot into recovery (TWRP)
The camera is working now.
Also, before I was able to flash CM-13 I had to do "WIPE >> Format Data" from TWRP, otherwise CM was exiting with error 7.
The following packages were used:
original 6.0.1 (MMB29P) factory image
BETA-SuperSU-v2.66-20160103015024.zip
cm-13.0-20160115-NIGHTLY-angler.zip
open_gapps-arm64-6.0-micro-20160115.zip
twrp-2.8.7.2-angler.img
I also noticed that when rebooting into factory image, the same warning message appears as well.
Any way to fix it or did I do something wrong?
Click to expand...
Click to collapse
It's just telling you what you already know. You modified your system partition yourself so don't worry about it.
https://support.google.com/nexus/answer/6185381?hl=en
XxMORPHEOUSxX said:
It's just telling you what you already know. You modified your system partition yourself so don't worry about it.
https://support.google.com/nexus/answer/6185381?hl=en
Click to expand...
Click to collapse
Thanks. I read it in the original Heisenberg's unlock guide and was surprised when I read this post that it was possible to get rid of the warning message without locking the bootloader .
I'm new here in the forum's..I usually just read and carry on..the one think I'd like to say is..I don't understand why people got to say 'why you doing that for, ya don't need to' far as I know..this an educational site to learn..if he wants learn how to get rid of the warning..I don't see any problems in that whatsoever.
The message "There is an internal problem with your device..." seems to be related to the security patch version. This was my biggest issue, the message I get when booting the phone was annoying and I knew it was not a big deal, but having an internal problem warning was concerning, flashing the vendor image was the solution for me. But if you like to start clean then I have the steps written, but if you update then again you'll get the warning when booting up.
Sent from my Nexus 6P using Tapatalk
zooman31 said:
I'm new here in the forum's..I usually just read and carry on..the one think I'd like to say is..I don't understand why people got to say 'why you doing that for, ya don't need to' far as I know..this an educational site to learn..if he wants learn how to get rid of the warning..I don't see any problems in that whatsoever.
Click to expand...
Click to collapse
I think what people are trying to say is the risk/reward for getting rid of the message is not worth it. Especially since its just a brief warning you only see during boot. Just flashing twrp recovery will give the red message. SuperSU will help get rid of it which is why the OP was able to remedy it. It will not work for everyone though. Modifying the bootloader is the only sure fire way to snuff it out for good and you would be a fool to try and mess with your bootloader for something aesthetic. That's how most real bricks happen, is when a bootloader gets corrupted.
XxMORPHEOUSxX said:
I think what people are trying to say is the risk/reward for getting rid of the message is not worth it. Especially since its just a brief warning you only see during bouot. Just flashing twrp recovery will give the red message. SuperSU will help get rid of it which is why the OP was able to remedy it. It will not work for everyone though. Modifying the bootloader is the only sure fire way to snuff it out for good and you would be a fool to try and mess with your bootloader for something aesthetic. That's how most real bricks happen, is when a bootloader gets corrupted.
Click to expand...
Click to collapse
I assume that most people know the drill..you proceed to test at your own risk..the how to in the first post seemed to have worked after it was tested by the author.
zooman31 said:
I assume that most people know the drill..you proceed to test at your own risk..the how to in the first post seemed to have worked after it was tested by the author.
Click to expand...
Click to collapse
Basically just flash SuperSU last in whatever sequence, and as long as it boots,the red message will be gone. But change anything after and it will probably come back. I have nothing negative to say about this thread. I originally posted the nexus link just so people can rest assured that it is not an actual problem and a normal, albeit annoying, side effect of modifying the Nexus 6p. Happy Flashing
XxMORPHEOUSxX said:
Basically just flash SuperSU last in whatever sequence, and as long as it boots,the red message will be gone. But change anything after and it will probably come back. I have nothing negative to say about this thread. I originally posted the nexus link just so people can rest assured that it is not an actual problem and a normal, albeit annoying, side effect of modifying the Nexus 6p. Happy Flashing
Click to expand...
Click to collapse
all i did was flash twrp and unlocked the bootloader and still got the red message. so all i have to do is flash supersu and root? to get rid of it?
TechMillz93 said:
all i did was flash twrp and unlocked the bootloader and still got the red message. so all i have to do is flash supersu and root? to get rid of it?
Click to expand...
Click to collapse
Yes. The SuperSU beta 2.66 is what I use.
XxMORPHEOUSxX said:
Yes. The SuperSU beta 2.66 is what I use.
Click to expand...
Click to collapse
so i just reflashed the vendor and now im in bootloop ;(
TechMillz93 said:
so i just reflashed the vendor and now im in bootloop ;(
Click to expand...
Click to collapse
Why did you flash vendor? Try clearing caches and then reboot. Let it sit for 10 min too while starting up.
XxMORPHEOUSxX said:
Why did you flash vendor? Try clearing caches and then reboot. Let it sit for 10 min too while starting up.
Click to expand...
Click to collapse
im good now i just reflashed all the images im good.
but i have to feflash twrp now, what would u recommend
systemless or traditional ?
TechMillz93 said:
im good now i just reflashed all the images im good.
but i have to feflash twrp now, what would u recommend
systemless or traditional ?
Click to expand...
Click to collapse
Systemless unless you want to use xposed otherwise it doesn't matter. Systemless just makes it so you can use root apps like android pay. I use the 2.66 systemless. The instructions are a little all over the place on that thread. You no longer need a modified boot.IMG. the SuperSU zip patches whatever boot.IMG you have. So all you need to flash is the supersu2.66 for systemless or the traditional zip if going that route.
XxMORPHEOUSxX said:
Systemless unless you want to use xposed otherwise it doesn't matter. Systemless just makes it so you can use root apps like android pay. I use the 2.66 systemless. The instructions are a little all over the place on that thread. You no longer need a modified boot.IMG. the SuperSU zip patches whatever boot.IMG you have. So all you need to flash is the supersu2.66 for systemless or the traditional zip if going that route.
Click to expand...
Click to collapse
so i dont need gapps etc?
its all in there?
I'm looking for a way to root "A910F" via google, but no results.
I tried "how to root for A9100" but without success.
Please help me.
Not so far
sanglxagdm said:
I'm looking for a way to root "A910F" via google, but no results.
I tried "how to root for A9100" but without success.
Please help me.
Click to expand...
Click to collapse
Hey there, I have a Google alert set for anything posted about this phone but so far nothing has come up on how to root it. Just two sites on how to update its version of android. (Sorry, I'm not allowed to post links as I'm a brand new user to xda, but likely these sites are not of use to you)
I'm still waiting for a way to buy it! And I've been waiting a long time. May I ask how you purchased it? Any help you could give I would really appreciate!
rapidrem11 said:
Hey there, I have a Google alert set for anything posted about this phone but so far nothing has come up on how to root it. Just two sites on how to update its version of android. (Sorry, I'm not allowed to post links as I'm a brand new user to xda, but likely these sites are not of use to you)
I'm still waiting for a way to buy it! And I've been waiting a long time. May I ask how you purchased it? Any help you could give I would really appreciate!
Click to expand...
Click to collapse
in italy here : http://brenovia.it/samsung/samsung-a9100-galaxy-a9-pro-dual-32gb-211.html
TWRP 3.0.2-1
sanglxagdm said:
I'm looking for a way to root "A910F" via google, but no results.
I tried "how to root for A9100" but without success.
Please help me.
Click to expand...
Click to collapse
TWRP 3.0.2-1. for the Samsung Galaxy A9 pro SM-A910F - Qualcomm MSM8976
Needs someone to test and report what works what doesn't giving plenty of detail and if possible the recovery log. It may boot, it may not.
Stock Recovery is posted below if TWRP doesn't boot.
NOTE:
FLASHING CUSTOM STUFF VOIDS YOUR WARRANTY. THIS WILL TRIP THE KNOX FLAG.
Install:
Boot to download mode.
Flash with Odin using the AP slot.
Uncheck Auto-reboot.
Reboot to recovery immediately after flashing using POWER + HOME + VOL DOWN, as soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
TWRP should now boot.
NOTE: ON SOME ANDROID 5.1.1 and 6.01 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Install with ODIN:
twrp_3.0.2-1_sm-a910f_25716
Stock recovery:
A910FXXU1APFC_stock_recovery
TO ROOT
Flash the file below in twrp.
https://download.chainfire.eu/964/Su...0519174328.zip
.
Installed fine on my A9100! No more Chinese when I enter TWRP!!!! Thank u!
steberg said:
Installed fine on my A9100! No more Chinese when I enter TWRP!!!! Thank u!
Click to expand...
Click to collapse
Can you post the recovery.log as a file or on pastebin?
Sent from my SM-T280 using XDA-Developers mobile app
@ashyx
Attached the recovery file.
steberg said:
@ashyx
Attached the recovery file.
Click to expand...
Click to collapse
OK, twrp cannot mount data or storage at the moment because your device has encryption enabled and TWRP does not support Samsung encryption at the moment.
To mount data and storage data needs to formatted to remove encryption and a custom boot.img used to disable forced encryption.
Sent from my SM-T280 using XDA-Developers mobile app
ashyx said:
TWRP 3.0.2-1. for the Samsung Galaxy A9 pro SM-A910F - Qualcomm MSM8976
Needs someone to test and report what works what doesn't giving plenty of detail and if possible the recovery log. It may boot, it may not.
Stock Recovery is posted below if TWRP doesn't boot.
NOTE:
FLASHING CUSTOM STUFF VOIDS YOUR WARRANTY. THIS WILL TRIP THE KNOX FLAG.
Install:
Boot to download mode.
Flash with Odin using the AP slot.
Uncheck Auto-reboot.
Reboot to recovery immediately after flashing using POWER + HOME + VOL DOWN, as soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
TWRP should now boot.
NOTE: ON SOME ANDROID 5.1.1 and 6.01 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Install with ODIN:
twrp_3.0.2-1_sm-a910f_25716
Stock recovery:
A910FXXU1APFC_stock_recovery
TO ROOT
Flash the file below in twrp.
https://download.chainfire.eu/964/Su...0519174328.zip
.
Click to expand...
Click to collapse
Hello I can be use this Files on SM A910F/DS Series??? Please reply me my phone is Dual Sim
hello please reply me can i use this file on A910/DS
ashyx said:
OK, twrp cannot mount data or storage at the moment because your device has encryption enabled and TWRP does not support Samsung encryption at the moment.
To mount data and storage data needs to formatted to remove encryption and a custom boot.img used to disable forced encryption.
Click to expand...
Click to collapse
I did format data and in TWRP I was then able to save recovery.log on internal storage. But after reboot it's back to encryption... I don't know how to make custom boot.img.
Thanks for your effort!
steberg said:
I did format data and in TWRP I was then able to save recovery.log on internal storage. But after reboot it's back to encryption... I don't know how to make custom boot.img.
Thanks for your effort!
Click to expand...
Click to collapse
I will provide the custom boot.img to disable encryption.
Ah that is awesome!!!
steberg said:
Ah that is awesome!!!
Click to expand...
Click to collapse
Flash with ODIN or extract the boot.img and flash with TWRP.
Boot to TWRP format DATA(not wipe). Please note this will delete all user data.
Reboot to TWRP, should now be able to mount data and make backups.
Boot to OS, forced encryption should be disabled.
A910FXXU1APFC_no_encryptable_boot
.
ashyx said:
Flash with ODIN or extract the boot.img and flash with TWRP.
Boot to TWRP format DATA(not wipe). Please note this will delete all user data.
Reboot to TWRP, should now be able to mount data and make backups.
Boot to OS, forced encryption should be disabled.
A910FXXU1APFC_no_encryptable_boot
.
Click to expand...
Click to collapse
Would this boot image work with the latest firmware for the A9100? Would you mind posting one if it won't? Could you also provide paypal info I'd like to contribute for your efforts.
trafficontrolr said:
Would this boot image work with the latest firmware for the A9100? Would you mind posting one if it won't? Could you also provide paypal info I'd like to contribute for your efforts.
Click to expand...
Click to collapse
It may do, but if it doesn't post up your boot.img.
If you go to the xda website the donate button should be on the left. Or use the link below. Thanks for your support. [emoji106]
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
ashyx said:
Flash with ODIN or extract the boot.img and flash with TWRP.
Boot to TWRP format DATA(not wipe). Please note this will delete all user data.
Reboot to TWRP, should now be able to mount data and make backups.
Boot to OS, forced encryption should be disabled.
A910FXXU1APFC_no_encryptable_boot
.
Click to expand...
Click to collapse
Yes It works fine now, even after reboot there is full access! I can now mount Data partition in twrp!
I get my paycheck tomorrow, so beer is incoming!
But there are some issues now in OS, most probably because the boot.img is for A910F and I'm on A9100... The navigation keys does not light up and is not working, also it will not turn on wifi even though I flip the switch. But finally some developer is taking the time for A9!
steberg said:
Yes It works fine now, even after reboot there is full access! I can now mount Data partition in twrp!
I get my paycheck tomorrow, so beer is incoming!
But there are some issues now in OS, most probably because the boot.img is for A910F and I'm on A9100... The navigation keys does not light up and is not working, also it will not turn on wifi even though I flip the switch. But finally some developer is taking the time for A9!
Click to expand...
Click to collapse
Those issues are almost certainly because of the kernel. Post your boot.img from the stock firmware.
Sent from my SM-T280 using XDA-Developers mobile app
It is great that such a serious developer starts to work for a9 pro and there are results immediately. @ashyx is there any way to put somehow anyhow a910f firm into a9100?
thanks
ashyx said:
Those issues are almost certainly because of the kernel. Post your boot.img from the stock firmware.
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
I thought so as well, that is why we cannot crossflash the A910F firmware to A9100. Anyway here is the boot.img from A9100! Thank u once again!
Btw, beer incoming!
No way to use international kernel somehow for a9100?
I'm struggling the whole weekend to get the device starting again and cannot find this firmware.
I need the Stock Firmware for my Huawei M3. It would be nice if someone could provide a link to Huawei where I can download the firmware or post an alternative download source. The Huawei eRecovery always throws an error: "Getting package info failed" When trying to recover.
I also sent a mail to Huawei support. If I get a answer there I will post the link here.
Even i am searching for the same
Huawei Support doesn't respond per email and the repair service wants minimum 80€ D
I'm not sure if Huawei ever published a stock image. If i look at: http://consumer.huawei.com/de/search/index.htm?keywords=Honor 8 Stock
There is something called "Honor 8 Firmware(FRD-L09, Android 6.0, EMUI 4.1, C432B131, Germany)". Is this the Stock image for the Honor 8?
Is it possible to load this into my Mediatab? The specs are almost the same.
sebbo2015 said:
Huawei Support doesn't respond per email and the repair service wants minimum 80€ D
I'm not sure if Huawei ever published a stock image. If i look at: http://consumer.huawei.com/de/search/index.htm?keywords=Honor 8 Stock
There is something called "Honor 8 Firmware(FRD-L09, Android 6.0, EMUI 4.1, C432B131, Germany)". Is this the Stock image for the Honor 8?
Is it possible to load this into my Mediatab? The specs are almost the same.
Click to expand...
Click to collapse
Look here for latest stock image:
https://www.androidfilehost.com/?w=files&flid=125388
*zahni* said:
Look here for latest stock image:
https://www.androidfilehost.com/?w=files&flid=125388
Click to expand...
Click to collapse
Thank you very much!! Can you give some explanation for the files? What is what file? I installed greatslon Bootloader and it worked like a charm but I don't see the other files linked in this forum. So I'm a little suspicious.
Is the honor 8 file for the LTE version or the other or both
//edit
OK it runs thxs. This is not the real stock image. Looks like a prerelease version but my tablet is alive again. I installed the M3 zip file.
*zahni* said:
Look here for latest stock image:
https://www.androidfilehost.com/?w=files&flid=125388
Click to expand...
Click to collapse
It's my ROM, not stock!
greatslon said:
It's my ROM, not stock!
Click to expand...
Click to collapse
i´m sorry, i thought it would be stock.
Your ROM seems to work very well, the only thing i dont linke is the font. Is it possible to change to stock font?
Greatslon, can you also provide a stock image?
THX for your help!
*zahni* said:
i�m sorry, i thought it would be stock.
Your ROM seems to work very well, the only thing i dont linke is the font. Is it possible to change to stock font?
Greatslon, can you also provide a stock image?
THX for your help!
Click to expand...
Click to collapse
Theme Editor is an app to edit EMUI themes. I hope with the Android 7 update we will get a stock image from Huawei. Nevertheless thank you very much greatslon!!
*zahni* said:
i´m sorry, i thought it would be stock.
Your ROM seems to work very well, the only thing i dont linke is the font. Is it possible to change to stock font?
Greatslon, can you also provide a stock image?
THX for your help!
Click to expand...
Click to collapse
All about my ROM here (you can use translator).
And i have only Chinese stock rom BTV-DL09C233B017 (fastboot), welcome.
greatslon said:
All about my ROM here (you can use translator).
And i have only Chinese stock rom BTV-DL09C233B017 (fastboot), welcome.
Click to expand...
Click to collapse
ThX for the share. When I try to install the stock file I get the error that the zip is corrupt? Mayby because of the charset of the inner folders? When I look at them in windows they look like grap.
//EDIT
OK I got it. I have to unzip it and flash the different img files
Its enough to flash the system image.
http://cfqrom9.xianshuabao.com/{965297}_华为_BTV-DL09_BTV-DL09C233B026_中国(China)_6.0.zip
Here is latest B026 rom. All fastboot files.
bark1234 said:
http://cfqrom9.xianshuabao.com/{965297}_华为_BTV-DL09_BTV-DL09C233B026_中国(China)_6.0.zip
Here is latest B026 rom. All fastboot files.
Click to expand...
Click to collapse
What is the difference from the B017?
No idea. Got my tablet 2 days back. moved from B009 to B022. Stil lin process of setting it up to my likings.
Uh ****, i think i bricked my Tablet.
I cannot boot android and also not TWRP...i just can boot eRecovery, but it doesnt download latest version to flash.
How can i enter fastboot without enter the Android System? How can i unbrick my mediapad?
Thank you for all your help!
*zahni* said:
Uh ****, i think i bricked my Tablet.
I cannot boot android and also not TWRP...i just can boot eRecovery, but it doesnt download latest version to flash.
How can i enter fastboot without enter the Android System? How can i unbrick my mediapad?
Thank you for all your help!
Click to expand...
Click to collapse
Connect tablet to PC and press vol- & power buttons until entering to fastboot.
greatslon said:
Connect tablet to PC and press vol- & power buttons until entering to fastboot.
Click to expand...
Click to collapse
Oh man, thank you soo much!!! :good:
bark1234 said:
No idea. Got my tablet 2 days back. moved from B009 to B022. Stil lin process of setting it up to my likings.
Click to expand...
Click to collapse
OK and the image was not made by you, was it? If it was, is the region China? The name seems obvious...
Thank you for uploading.Perhaps we should push all these images in the right forums section??
greatslon said:
Connect tablet to PC and press vol- & power buttons until entering to fastboot.
Click to expand...
Click to collapse
ok now i have an other problem...i flashed twrp and can boot into recovery but i cannot mount the data partition. twrp always says: failed to mount /data (Invalid argument) i tried to format the data and system partitions in fastboot mode, but it doesnt work...
any idea how to fix that?
*zahni* said:
ok now i have an other problem...i flashed twrp and can boot into recovery but i cannot mount the data partition. twrp always says: failed to mount /data (Invalid argument) i tried to format the data and system partitions in fastboot mode, but it doesnt work...
any idea how to fix that?
Click to expand...
Click to collapse
What do you need to do with the data partition? Do you want to install the chinese ROM?
sebbo2015 said:
OK and the image was not made by you, was it? If it was, is the region China? The name seems obvious...
Thank you for uploading.Perhaps we should push all these images in the right forums section??
Click to expand...
Click to collapse
No It wasn't made by me. I found it from china vmall forum.
---------- Post added at 03:16 AM ---------- Previous post was at 03:14 AM ----------
sebbo2015 said:
What do you need to do with the data partition? Do you want to install the chinese ROM?
Click to expand...
Click to collapse
This tablet is made in china, Chinese roms get faster updates. Once booting you choose your language and region, then almost everything is changed to your language. Rarely something is left in chinese.