Develop Bugs

[HELP] cant go past Google logo

Hello, i do full wipe..then ROM flash regular as normal everyday ROM flash. But now i cant go into boot animation it just stay on Google logo.
i have lates TWRP 2.5.0. I can go into recovery, flash ROM, i can do anything in recovery without error message. I can do full wipe system, cache, dalvik,data then flash ROM but no matter what ROM i flash it just does not boot
i try restore backup, wipe all, fix permissions, flash other ROM, flash stock 422rooted with bussibox from bixie but nothing helps. I flashing on USB key mouned on OTG cable.
Im waiting 5-10min. then pull battery. I dont know what to do more to get it working
please help
EDIT: restoring data give me message "cant mount /data" but after reboot i can mount
EDIT2: after flashing regular ROM /system is empty.. its normal? im using TWRP file manager

Flash stock factory images through fastboot, then start over. Try another recovery version (like twrp 2.4.4.0 or cwm), even though I haven't experienced any issues.
Sent from my Galaxy Nexus using Tapatalk 4 Beta

beekay201 said:
Flash stock factory images through fastboot, then start over. Try another recovery version (like twrp 2.4.4.0 or cwm), even though I haven't experienced any issues.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
easyst way is thrue GNEX toolkit right? any mirror? goo.im have problems and i cant download it
EDIT:after ROM install it say Updating partition details...
E: Unable to mount " /data

Have you successfully installed Factoty Images like beekay201 suggested? It seems like you haven't. Please do thst and verify the phone is working well before flashing anything else.
You can do it with toolkit, or witb fastboot commands manually it doesn't matter.

My Gnexi said:
Have you successfully installed Factoty Images like beekay201 suggested? It seems like you haven't. Please do thst and verify the phone is working well before flashing anything else.
You can do it with toolkit, or witb fastboot commands manually it doesn't matter.
Click to expand...
Click to collapse
still preparing for it downloading requred files in tookit...
its weird becouse i can install ROM without any FAILED message. but if i restore some backup it say FAILED when restoring data..

ok looks like it booting. Hope nothing more will screw up. THANKS for all you help guys ill ask more if something gues wrong.
:good:

castaway1 said:
ill ask more if something gues wrong.
:good:
Click to expand...
Click to collapse
Please don't. I'm sure your future problems have already been discussed and solved. Please search before posting.
U.O.E.N.O

S2 not booting past CM logo

Okay, everything seemed fine on my s2 until the latest CM download. I install it though CWM and it seems fine but then it says
set_metadata_recursive: some changes failed
E:Error in /sdcard/firmware/cm-11-20140619-NIGHTLY-hercules.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Firmware is just the folder name for where i keep the files i may flash to it. I have tried other
I tried to install CM 10.2.0 and it seems to work. but then when i try and boot, it goes to the splash screen and just stays there. Did I do something wrong that is causing this?

Spud37 said:
Okay, everything seemed fine on my s2 until the latest CM download. I install it though CWM and it seems fine but then it says
Firmware is just the folder name for where i keep the files i may flash to it. I have tried other
I tried to install CM 10.2.0 and it seems to work. but then when i try and boot, it goes to the splash screen and just stays there. Did I do something wrong that is causing this?
Click to expand...
Click to collapse
"Set metadata recursive" probably means you are using a recovery that is too old.

@Spud37
Yes, it means your recovery is outdated. Here is a download link for the latest TWRP that you can flash in Odin as PDA. http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.7.1.0-hercules.tar
This link came from teamwins website (teamw.in)
Sent from my SGH-T989

jrc2 said:
@Spud37
Yes, it means your recovery is outdated. Here is a download link for the latest TWRP that you can flash in Odin as PDA. http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.7.1.0-hercules.tar
This link came from teamwins website (teamw.in)
Sent from my SGH-T989
Click to expand...
Click to collapse
Well there is another issue with my phone that I have actually worked around for awhile now. The MircoUSB on the phone is broken. I bought an extra battery and swap it, I also just use the SD card to copy anything to the phone. Is there a way for me to flash the phone with the new TWRP from the sd card. Why would the older TWRP not install CM 10.2.0 ROM? Do I have to go older perhaps? Thanks though. Knowing is half the battle
EDIT: Going to try and install 10.1.0 and see if it will let me boot. I figure once I can get it to boot, it will be easier to update the Recovery on the phone.
EDIT 2: No problems or errors occured when I installed CM 10.1.0.zip. However it still got stuck in a boot loop. I did however find a file called superwipe for the T mobile S2. I am wondering if that could help
EDIT 3: Okay so the superwipe worked and i am now running 10.1.0, Is it possible to install a Recovery from the phone without using odin?

What all did you wipe when you installed 10.1? There is a way to update the recovery if you can get the phone to boot. What is the latest thing you got to boot on your phone?
Sent from my HP Slate 7 using Tapatalk

jrc2 said:
What all did you wipe when you installed 10.1? There is a way to update the recovery if you can get the phone to boot. What is the latest thing you got to boot on your phone?
Sent from my HP Slate 7 using Tapatalk
Click to expand...
Click to collapse
I had wiped everything, formatted and fixed permissions, it didn't work. It wasn't until i found the Superwipe that installation worked and i was able to boot to 10.1.0. How can i update/change the recovery from the phone.
Thanks

Spud37 said:
I had wiped everything, formatted and fixed permissions, it didn't work. It wasn't until i found the Superwipe that installation worked and i was able to boot to 10.1.0. How can i update/change the recovery from the phone.
Thanks
Click to expand...
Click to collapse
It is a lot more risky if your usb port doesn't work, since you can't flash back to stock in Odin if something goes wrong. I would recommend that you get someone to fix that USB port before you make too many changes.
DISCLAIMER: I am not responsible for anything that happens to your phone. These changes could brick your phone if something goes wrong. Proceed at your own risk!
Okay, now for the tutorial. These instructions are assuming that you are already rooted. Download this file and make sure you check the md5sum. Rename it to TWRP.img and move it to /storage/sdcard. This will make the next steps easier. If you move the file somewhere else, make a note of the location of the file. If you have not already, install the terminal emulator app form the Play Store. Open it and type the following lines in it.
Code:
su
[CLICK ENTER]
Code:
dd if=/storage/sdcard/TWRP.img of=/dev/block/mmcblk0p22
(Change the path to wherever you moved the file to) [CLICK ENTER]
Reboot into recovery and wipe cache and dalvik. Reboot. If recovery says that system recovery will override it on reboot, click fix. This should update your recovery.
Have a good afternoon,
jrc2

Need HELP!! with HTC Desire 816

Hello Everyone,
I need help with my HTC Desire 816 Here is my issue :
I rooted my device using this tutoriol : http://forum.xda-developers.com/showthread.php?t=2775801
everything went smooth but when i open SuperSU it says Binary needs to be updated but i'm unable to update it in anyway.
After root the phone restarts randomly.
I even tried to unroot using SuperSU and other ways but nothing seems to work.
I also tried to Disable Write Permission and that's when it all went wrong.
Now my phone keeps rebooting and i can't even use it
N.B: I always had an iphone, it's my first android phone so i'm a Newbie in rooting.
Any help is REALLY appreciated.
Thanks.

the link doesn't work, if you mean v_superuser guide the post was for kitkat
for lollipop you need to flash supersu v 2.46 I guess, atleast that what I did
the write protection post indicated in his guide also was for kitkat
try flashing stock if you took a backup b4 rooting to stop the random restarts, flash supersu and disable write protection for lollipop http://forum.xda-developers.com/des...-disable-writeprotection-sense-stock-t3091456

[/COLOR]
MaE_sTrO said:
Hello Everyone,
I need help with my HTC Desire 816 Here is my issue :
I rooted my device using this tutoriol http://forum.xda-developers.com/show....php?t=2775801
everything went smooth but when i open SuperSU it says Binary needs to be updated but i'm unable to update it in anyway.
After root the phone restarts randomly.
I even tried to unroot using SuperSU and other ways but nothing seems to work.
I also tried to Disable Write Permission and that's when it all went wrong.
Now my phone keeps rebooting and i can't even use it
N.B: I always had an iphone, it's my first android phone so i'm a Newbie in rooting.
Any help is REALLY appreciated.
Thanks.
Click to expand...
Click to collapse
Sorry your having these problems but as long as you can get into your boatloader they should be fixable. Hopefully you did a full nandroid backup of your phone after rooting before attempting any other flashes or mods but if you didn't then that's just friendly advice for any future flashes for everybody , me included. It's an easy step to skip(I've forgotten to do one myself) but it's the most important step to being able to easily restore from any problems.
Try to get into your boatloader by holding power button then volume down and hold. That should reboot into your bootloader and from there you can enter recovery and do a factory reset then wipe cache and dalvik cache then reboot system and see if that stops the bootloops. If not then you might need to find and reflash your stock recovery and relock your bootloader then find a flashable zip or executable RUU (rom utility update) and flash back to completely stock. If your in the U.S. HTC has the RUU executable files on their website in the downloads section(RUU not kernel). These you can either run from a P.C. as an executable program with your phone in fastboot or rename to your model specific firmware image and install to and flash from your phone's external SD card from your bootloader. The only issue would be if your system has been modified by the write permission mod you flashed then that would need to be removed before any signed stock update could work. What's your specific phone model( a5_"what") and are you in the U.S. or overseas?
EDIT: it's volume down not volume up. Volume up reboots the phone. Sorry, I use an app to do all of that now not my keys.

thoctor said:
[/COLOR]
Sorry your having these problems but as long as you can get into your boatloader they should be fixable. Hopefully you did a full nandroid backup of your phone after rooting before attempting any other flashes or mods but if you didn't then that's just friendly advice for any future flashes for everybody , me included. It's an easy step to skip(I've forgotten to do one myself) but it's the most important step to being able to easily restore from any problems.
Try to get into your boatloader by holding power button then volume down and hold. That should reboot into your bootloader and from there you can enter recovery and do a factory reset then wipe cache and dalvik cache then reboot system and see if that stops the bootloops. If not then you might need to find and reflash your stock recovery and relock your bootloader then find a flashable zip or executable RUU (rom utility update) and flash back to completely stock. If your in the U.S. HTC has the RUU executable files on their website in the downloads section(RUU not kernel). These you can either run from a P.C. as an executable program with your phone in fastboot or rename to your model specific firmware image and install to and flash from your phone's external SD card from your bootloader. The only issue would be if your system has been modified by the write permission mod you flashed then that would need to be removed before any signed stock update could work. What's your specific phone model( a5_"what") and are you in the U.S. or overseas?
EDIT: it's volume down not volume up. Volume up reboots the phone. Sorry, I use an app to do all of that now not my keys.
Click to expand...
Click to collapse
Thank you thoctor , as i said i'm a newbie in rooting so i didn't make full nandroid backup but thanks to you and after doing a factory reset the bootloops stopped, i'm able to use the phone now, but i think the write protection is still disabled, as i'm trying to use apps2sd and creating a new partition in the SD is not working, one more thing i'm unable to update SuperSu's binary too, thanks to your help and i would appreciate if you can help me further.
my model number : A5_ul and cidnum: HTC__E11 , and i'm in europe.

Roberto Nigel said:
the link doesn't work, if you mean v_superuser guide the post was for kitkat
for lollipop you need to flash supersu v 2.46 I guess, atleast that what I did
the write protection post indicated in his guide also was for kitkat
try flashing stock if you took a backup b4 rooting to stop the random restarts, flash supersu and disable write protection for lollipop http://forum.xda-developers.com/des...-disable-writeprotection-sense-stock-t3091456
Click to expand...
Click to collapse
Thanks Roberto
that's the exact way i tried to disable write protection, and that's when it all went wrong, but i retried it now it went smooth, but i think it didn't work , is there anyway to make sure if it's enabled or not ?

MaE_sTrO said:
Thank you thoctor , as i said i'm a newbie in rooting so i didn't make full nandroid backup but thanks to you and after doing a factory reset the bootloops stopped, i'm able to use the phone now, but i think the write protection is still disabled, as i'm trying to use apps2sd and creating a new partition in the SD is not working, one more thing i'm unable to update SuperSu's binary too, thanks to your help and i would appreciate if you can help me further.
my model number : A5_ul and cidnum: HTC__E11 , and i'm in europe.
Click to expand...
Click to collapse
No problem buddy. We've all been there trust me on that. You can update the binaries from within the SuperSU apps settings or in custom recovery. Check to verify you have the most current version from the play store and if not download it. Also you might try to wipe your cache and dalvik cache from within your custom recovery then reboot system and see if that fixes it. As for the WP mod there are some that get it to work right off the bat and others who have to add or remove a line in the lib files using a terminal emulator app but I've never personally used this mod as I have true S off on my 816 a5_chl. I use Link2SD not the one your talking about but the partitioning for the app I use is done on a P.C. using EaseUS partition manager. Is yours the same process?

thoctor said:
No problem buddy. We've all been there trust me on that. You can update the binaries from within the SuperSU apps settings or in custom recovery. Check to verify you have the most current version from the play store and if not download it. Also you might try to wipe your cache and dalvik cache from within your custom recovery then reboot system and see if that fixes it. As for the WP mod there are some that get it to work right off the bat and others who have to add or remove a line in the lib files using a terminal emulator app but I've never personally used this mod as I have true S off on my 816 a5_chl. I use Link2SD not the one your talking about but the partitioning for the app I use is done on a P.C. using EaseUS partition manager. Is yours the same process?
Click to expand...
Click to collapse
Yup i have the latest supersu, About the Link2SD i have it also installed, and i've done the partitions on pc , tried EXT2 , EXT4 amd fat32 nothing worked, after so many tries the last error i get is something like that ( bad magic number in superblock ). that's why i thought it has something to do with the WP.
so i should wipe the cache and dalvik cache and it will do no harm right ?(coz i'm really glad now since i got rid of the rebootloop and i can use my phone .

MaE_sTrO said:
Yup i have the latest supersu, About the Link2SD i have it also installed, and i've done the partitions on pc , tried EXT2 , EXT4 amd fat32 nothing worked, after so many tries the last error i get is something like that ( bad magic number in superblock ). that's why i thought it has something to do with the WP.
so i should wipe the cache and dalvik cache and it will do no harm right ?(coz i'm really glad now since i got rid of the rebootloop and i can use my phone .
Click to expand...
Click to collapse
Lol. I know how you feel. You can wipe those two all day long and nothing bad will happen. It's just a cache cleaner that clears out our any leftover files in the firmwares cache folders. System restore wipes the whole phone except for the external SD card and your personal downloads or data files. Custom delete can add those personal data files so be careful there but otherwise your good. Check settings to see in about phone if your SElinux permissions are set to enforcing or permissive. The mod is supposed to change them to permissive for it to work properly.
Also on link2SD set the new data partition to ext2 if your on a stock rom and set as primary then set the remaining partition for your normal storage(not app data) to fat32 (as that's the format the phone will let you view in your SD card) and also as primary. It was the write permissions that wasn't letting it work not the format because I've been down that road many times before I got mine right.

thoctor said:
Lol. I know how you feel. You can wipe those two all day long and nothing bad will happen. It's just a cache cleaner that clears out our any leftover files in the firmwares cache folders. System restore wipes the whole phone except for the external SD card and your personal downloads or data files. Custom delete can add those personal data files so be careful there but otherwise your good. Check settings to see in about phone if your SElinux permissions are set to enforcing or permissive. The mod is supposed to change them to permissive for it to work properly.
Also on link2SD set the new data partition to ext2 if your on a stock rom and set as primary then set the remaining partition for your normal storage(not app data) to fat32 (as that's the format the phone will let you view in your SD card) and also as primary. It was the write permissions that wasn't letting it work not the format because I've been down that road many times before I got mine right.
Click to expand...
Click to collapse
thanks for the fast response , i wiped the cache and i still can't update the binary i get this msg
{
"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"
}
if i press normal the phone reboots, if i press TWRp/CWM ( since i rooted with cwm recovery) it reboots enters recovery starts loading then reboots and i get the same msg about the update again.
Also about the SElinux i can't find it in about :S.

MaE_sTrO said:
thanks for the fast response , i wiped the cache and i still can't update the binary i get this msg
if i press normal the phone reboots, if i press TWRp/CWM ( since i rooted with cwm recovery) it reboots enters recovery starts loading then reboots and i get the same msg about the update again.
Also about the SElinux i can't find it in about :S.
Click to expand...
Click to collapse
Find official TWRP recovery flashable zip for the a5 on their website and download and flash over CWM from your P.C. using ADB/fastboot.Just put the file in your ADB folder and rename it twrp.img and enter fastboot flash recovery"recovery name".img and either enter the name after typing recovery or just drag it down into your command prompt after typing recovery and it should flash automatically with your phone's USB debugging activated and the phone in fastboot. I use TWRP and you might be having an issue with the CWM exe recovery.Can't hurt to flash and you could always go back if you didn't like it but most everybody loves TWRP custom touch recovery. I know I do. It's on all my rooted devices.
As for the SElinux it's at the very bottom of my settings in about phone but I'm on a custom rom CM12.1 but you should be able to see it somewhat in your phone's settings on stock. I just can't remember where it is but it's there
EDIT: try to reflash in recovery the most current flashable zip for SuperSU found on chainfires website for SuperSU. I believe it's 2.4.6 but don't quote me on that just make sure it's the most current one which it will be on his site. That may help the binary issue. Even if the one you flashed is the most current flashable zip flash it again.

thoctor said:
Find official TWRP recovery flashable zip for the a5 on their website and download and flash over CWM from your P.C. using ADB/fastboot.Just put the file in your ADB folder and rename it twrp.img and enter fastboot flash recovery"recovery name".img and either enter the name after typing recovery or just drag it down into your command prompt after typing recovery and it should flash automatically with your phone's USB debugging activated and the phone in fastboot. I use TWRP and you might be having an issue with the CWM exe recovery.Can't hurt to flash and you could always go back if you didn't like it but most everybody loves TWRP custom touch recovery. I know I do. It's on all my rooted devices.
As for the SElinux it's at the very bottom of my settings in about phone but I'm on a custom rom CM12.1 but you should be able to see it somewhat in your phone's settings on stock. I just can't remember where it is but it's there
Click to expand...
Click to collapse
Just flashed TWRP.
tried to update binary same thing happend but now i see in TWRP when it tries to update it says no MD5

thoctor said:
Find official TWRP recovery flashable zip for the a5 on their website and download and flash over CWM from your P.C. using ADB/fastboot.Just put the file in your ADB folder and rename it twrp.img and enter fastboot flash recovery"recovery name".img and either enter the name after typing recovery or just drag it down into your command prompt after typing recovery and it should flash automatically with your phone's USB debugging activated and the phone in fastboot. I use TWRP and you might be having an issue with the CWM exe recovery.Can't hurt to flash and you could always go back if you didn't like it but most everybody loves TWRP custom touch recovery. I know I do. It's on all my rooted devices.
As for the SElinux it's at the very bottom of my settings in about phone but I'm on a custom rom CM12.1 but you should be able to see it somewhat in your phone's settings on stock. I just can't remember where it is but it's there
EDIT: try to reflash in recovery the most current flashable zip for SuperSU found on chainfires website for SuperSU. I believe it's 2.4.6 but don't quote me on that just make sure it's the most current one which it will be on his site. That may help the binary issue. Even if the one you flashed is the most current flashable zip flash it again.
Click to expand...
Click to collapse
Flashed TWRP reflashed SuperSU from chainfires website , same issue , but now i can see when it tries to update in TWRP it says no MD5!!!
and i assure u i can't find SElinux anywhere in about !!!!

MaE_sTrO said:
Flashed TWRP reflashed SuperSU from chainfires website , same issue , but now i can see when it tries to update in TWRP it says no MD5!!!
and i assure u i can't find SElinux anywhere in about !!!!
Click to expand...
Click to collapse
No problem , Don't worry about the permissions for now. The MD5 is the checksum that verifies the file isn't corrupt but if you got it from the chainfire site your fine. Try to update the binary thru twrp or in the SuperSU app and select your recovery as the way you want to update and see what happens.
Also did you have MD5 check enabled in TWRP? I do in mine for file verification but just wondering what yours was set to when you got that notice. It shouldn't stop SuperSU from flashing either way it's just a file verifier.
---------- Post added at 12:56 AM ---------- Previous post was at 12:18 AM ----------
the binaries are what SuperSU uses to get and maintain root . If they are incomplete or corrupt then they have to be reflashed over with an uncorrupted version. That is usually why people keep getting the notice to update the binaries and when they do they can't because they are not complete or corrupt and need to be totally removed i.e. reflashing, which you did, or unrooting from the SuperSU app itself and redownloading again from the play store. This is what I've read on several help sites for this issue. Just wanted to pass along the why not just the what.

Again thank you for giving me so much information so i can understand the way things work and what i am doing, MD5 check was disabled i tried updating binary thru twrp i also tried enabling the MD5 both gave the same result, but the weird thing that it says done proccessing zip file , but when it reboots the update msg shows again, another thing when updating through twrp i noticed this line " full SElinux is present ".

MaE_sTrO said:
Again thank you for giving me so much information so i can understand the way things work and what i am doing, MD5 check was disabled i tried updating binary thru twrp i also tried enabling the MD5 both gave the same result, but the weird thing that it says done proccessing zip file , but when it reboots the update msg shows again, another thing when updating through twrp i noticed this line " full SElinux is present ".
Click to expand...
Click to collapse
No problem. To me that's the whole point of helping here on XDA is to make these things easier to understand for the person asking for assistance so they don't have to come back for the same thing again.Also because I was here in the same situations just a year or so ago and others helped me understand and I'm not a rocket scientist by any means .
Try to verify root through the root checker app on the play store. Almost positive it will say not rooted but it can't hurt to verify. Then , again, I would try to uninstall SuperSU through the app itself in it's settings as I'm almost positive the binaries are corrupted or incomplete and that's why you keep getting the same "update binaries message". If I sound like a broken record it's because I have learned from multiple Android device issues that sometimes for whatever reason things don't take and some combination of things might happen to alter the reason and trying the same thing again fixed it after coming back to it. I would also download SuperSU again but on a different device(laptop, computer) from chainfires site and reflash it just on the off chance the file is corrupted . Although at this point it's unlikely I know.
Lastly I would do an advanced wipe in TWRP recovery and add system to Data and Dalvik cache and cache from the factory reset. Not internal storage or SD card. Then I would flash the newly downloaded SuperSU and wipe Dalvik and cache then reboot system. Back up your contacts and numbers through Google's own backup in settings and they may already be backed up and use Super Backup app as well to save to external SD card as it can backup the same things.

thoctor said:
No problem. To me that's the whole point of helping here on XDA is to make these things easier to understand for the person asking for assistance so they don't have to come back for the same thing again.Also because I was here in the same situations just a year or so ago and others helped me understand and I'm not a rocket scientist by any means .
Try to verify root through the root checker app on the play store. Almost positive it will say not rooted but it can't hurt to verify. Then , again, I would try to uninstall SuperSU through the app itself in it's settings as I'm almost positive the binaries are corrupted or incomplete and that's why you keep getting the same "update binaries message". If I sound like a broken record it's because I have learned from multiple Android device issues that sometimes for whatever reason things don't take and some combination of things might happen to alter the reason and trying the same thing again fixed it after coming back to it. I would also download SuperSU again but on a different device(laptop, computer) from chainfires site and reflash it just on the off chance the file is corrupted . Although at this point it's unlikely I know.
Lastly I would do an advanced wipe in TWRP recovery and add system to Data and Dalvik cache and cache from the factory reset. Not internal storage or SD card. Then I would flash the newly downloaded SuperSU and wipe Dalvik and cache then reboot system. Back up your contacts and numbers through Google's own backup in settings and they may already be backed up and use Super Backup app as well to save to external SD card as it can backup the same things.
Click to expand...
Click to collapse
i went through your instructions , and after the last steps now i'm stuck on HTC logo
i can't even turn it off or get into recovery!!!!
i managed somehow to get into recovery no it says no OS installed , i guess i F**k it up right ?

MaE_sTrO said:
i went through your instructions , and after the last steps now i'm stuck on HTC logo
i can't even turn it off or get into recovery!!!!
i managed somehow to get into recovery no it says no OS installed , i guess i F**k it up right ?
Click to expand...
Click to collapse
No you didn't f***k it up I f*****d it up. I was thinking of what I do on my custom rom when I can't get something fixed and I brainfarted and forgot for a second your on a stock rom. That's on me not you so be mad at me not yourself. The good thing is it's fixable. I just flash a new custom rom but with stock it's a little bit different. You need to flash back the stock recovery which I will find and link you to and then lock the bootloader and flash back your stock Rom which I will also link you to. I am so sorry. I was in a doctor's office waiting room and my mind was on other things but that's no excuse just an explanation. Below is the link to stock lollipop for the a5_ul European version
Better than what I first linked us this forum page from Nukaru a few posts down in this forum for the stock a5_ul. He had links to both the stock recovery and stock rom file with detailed instructions on how to get the stock rom back on your phone. I know it works because he had a problem and figured all this out himself then wrote a detailed tutorial on how he fixed his. Link below.
http://forum.xda-developers.com/desire-816/help/a5ul-unable-to-flash-ruu-t3294835/page2

thoctor said:
No you didn't f***k it up I f*****d it up. I was thinking of what I do on my custom rom even I can't get something fixed and I brainfarted and forgot for a second your on a stock rom. That's on me not you so be mad at me not yourself. The good thing is it's fixable. I just flash a new custom rom but with stock it's a little bit different. You need to flash back the stock recovery which I will find and link you to and then lock the bootloader and flash back your stock Rom which I will also link you to. I am so sorry. I was in a doctor's office waiting room and my mind was on other things but that's no excuse just an explanation. Below is the link to stock lollipop for the a5_up European version
Link to stock lollipop rom below
https://www.androidfilehost.com/?fid=23991606952595166
Click to expand...
Click to collapse
Never mind i have nothing to loose as long as it's fixable lol, anyway i'll try this rom now
note: when i relock boot loader it says RELOCKED with S-ON does this matters?

MaE_sTrO said:
Never mind i have nothing to loose as long as it's fixable lol, anyway i'll try this rom now
note: when i relock boot loader it says RELOCKED with S-ON does this matters?
Click to expand...
Click to collapse
No, hold off on that first link I have a better one buddy. Just edited it above. No, "relocked S on" is what it's supposed to say so your fine but don't lock it yet or if you already did unlock it using the same unlock token you used on htc developers to unlock it in the first place . Then you flash back your stock recovery. Then relock your bootloader. Then you flash back your stock rom in that order.

thoctor said:
No hold off on that first link I have a better one buddy. Just edited it above. No relocked S on is what it's supposed to say so your fine but don't lock it yet orv I'd your already did unlock it using the same unlock token you used on htc developers to unlock it in the first place .
Click to expand...
Click to collapse
Alright downloading now...

Installing T805 MM build on T800?

Yeah, im impatient. Anyone know of a way to do this? I'd be happy to try a port if anyone could point me on the right direction.

you should be able to just flash the released T805 MM zip from samsung onto a T800. all you should see is a no LTE sign as in circle with line through it once it boots to desktop. im not 100% sure though so i take no responsibility for a bricked device.

Don't they have different CPUs, Exynos and Snapdragon? So really not as simple as just flashing it.
Sent from my SM-N910F using Tapatalk

oops !!

The 805 and 800 both use same exynos CPU . It's the 807 variant that had the SD.

Regardless of CPU the file manifest won't pass hash check, there's no way to flash the 805 ROM on the 800 without unpacking and moding it.

texaspledge said:
Yeah, im impatient. Anyone know of a way to do this? I'd be happy to try a port if anyone could point me on the right direction.
Click to expand...
Click to collapse
Odin flashable.
Make a full backup with TWRP then wipe dalvik cache.
Extract tar archive from zip and flash with ODIN in AP slot.
Contains only boot, recovery, cache and modified system image.
Usually takes around 10 mins to boot. If it hangs for much longer or boot loops it may be necessary to wipe data.
MM_SM-T800_T805OXA1CPH6_REPACK
.

ashyx said:
Odin flashable.
Make a full backup with TWRP then wipe dalvik cache.
Extract tar archive from zip and flash with ODIN in AP slot.
Contains only boot, recovery, cache and modified system image.
Usually takes around 10 mins to boot. If it hangs for much longer or boot loops it may be necessary to wipe data.
MM_SM-T800_T805OXA1CPH6_REPACK
.
Click to expand...
Click to collapse
You are awesome sir! I will let you all know how it goes.

ashyx said:
Odin flashable.
Make a full backup with TWRP then wipe dalvik cache.
Extract tar archive from zip and flash with ODIN in AP slot.
Contains only boot, recovery, cache and modified system image.
Usually takes around 10 mins to boot. If it hangs for much longer or boot loops it may be necessary to wipe data.
MM_SM-T800_T805OXA1CPH6_REPACK
.
Click to expand...
Click to collapse
Unfortunately doesn't seem to be working. Reboots to recovery saying:
System/bin/e2fsck failed with status 255
Format_volume: e2fsck fail : dev/block/platform/dw_mmc.0/by-name/cache

texaspledge said:
Unfortunately doesn't seem to be working. Reboots to recovery saying:
System/bin/e2fsck failed with status 255
Format_volume: e2fsck fail : dev/block/platform/dw_mmc.0/by-name/cache
Click to expand...
Click to collapse
Are you trying to install it with twrp?
Not sure what your doing but you wouldn't get that error with odin.

ashyx said:
Are you trying to install it with twrp?
Not sure what your doing but you wouldn't get that error with odin.
Click to expand...
Click to collapse
I installed with ODIN but first time it rebooted, it applied system update and then went into recovery with those errors messages.

Just reboot. It's only trying to wipe the cache partition.
Did the system.img install ok?

ashyx said:
Just reboot. It's only trying to wipe the cache partition.
Did the system.img install ok?
Click to expand...
Click to collapse
Multiple reboots don't help. Doesn't even get to samsung splash screen. Now that I tried again, after ODIN, it reboots and the tab shows the android updating icon and it gets about 1/3rd of the way through and spits me back to recovery. I don't think it is applying the system.img.

texaspledge said:
Multiple reboots don't help. Doesn't even get to samsung splash screen. Now that I tried again, after ODIN, it reboots and the tab shows the android updating icon and it gets about 1/3rd of the way through and spits me back to recovery. I don't think it is applying the system.img.
Click to expand...
Click to collapse
Does odin flash all 4 images OK? Are running the latest LL bootloader BOL1?
The other way to flash is to extract the images from the tar archive and use the system image flashing feature in TWRP.

same problem, Odin flash everything without an error, but when the tab restarts it fail on applying update and enter in the stock samsung recovery with the the error:
System/bin/e2fsck failed with status 255
Format_volume: e2fsck fail : dev/block/platform/dw_mmc.0/by-name/cache
i'm trying to update from the stock lollipop, and I have the last bootloader

RoIlingThunder said:
same problem, Odin flash everything without an error, but when the tab restarts it fail on applying update and enter in the stock samsung recovery with the the error:
System/bin/e2fsck failed with status 255
Format_volume: e2fsck fail : dev/block/platform/dw_mmc.0/by-name/cache
i'm trying to update from the stock lollipop, and I have the last bootloader
Click to expand...
Click to collapse
Wipe cache in recovery and reboot. It could be the install script in cache is looking for something that's not there.
As I've said above flashing boot and system with twrp should suffice.
While your there check to see if the system.img got installed by using twrp file manager to look for the required folders and files.
Make sure system is mounted first.

Just tried flashing in TWRP. Started with ODIN of latest French LP and then flashed TWRP. Then flashed system and boot. No go. It just stalls at initial 'by android' splash and sits there.
Thanks for the effort but I guess I'll need to wait for official.

Should also say that in TWRP system and boot flashed with no errors.

texaspledge said:
Just tried flashing in TWRP. Started with ODIN of latest French LP and then flashed TWRP. Then flashed system and boot. No go. It just stalls at initial 'by android' splash and sits there.
Thanks for the effort but I guess I'll need to wait for official.
Click to expand...
Click to collapse
After some investigation it seems the issue is incorrect permissions as I have been able to recreate the error. I have also managed to hopefully fix the issue.
The download below is a TWRP flashable zip with permissions set correctly this time. This is tested and working just fine.
INSTALL:
Copy the zip below to your sdcard.
There shouldn't be any need to wipe data, but wipe system and cache first in TWRP then install the zip below.
Be patient it will take at least 10 mins for first boot. If it takes much longer you may need to wipe DATA.
SM-T800_T805OXA1CPH6_MM
.

ashyx said:
After some investigation it seems the issue is incorrect permissions as I have been able to recreate the error. I have also managed to hopefully fix the issue.
The download below is a TWRP flashable zip with permissions set correctly this time. This is tested and working just fine.
INSTALL:
Copy the zip below to your sdcard.
There shouldn't be any need to wipe data, but wipe system and cache first in TWRP then install the zip below.
Be patient it will take at least 10 mins for first boot. If it takes much longer you may need to wipe DATA.
SM-T800_T805OXA1CPH6_MM
.
Click to expand...
Click to collapse
Downloading now ?

Please help me save my phone

FAILED (Do not allow to flash Bootloader image on Unlock device) & TWRP - Failed to mount '/firmware' (invalid argument)
I'm using the Lenovo p2a42 32gb 3gb version (India)
My phone is stuck in fastboot mode. Bootloader is unlocked.
I have the latest twrp - 3.2.2.0 as recovery.
I flashed everything except the modem and bootloader to stock.
Bootloader & modem wont flash - cannot flash unlocked bootloader error.
I have tried everything I can think of:
1. Restore to stock 7.1 (cannot flash bootloader error)
2. Relock Bootloader (not allowed error)
3. Even gave my phone to a repair guy as last resort.
No luck yet.
Its 17000 bucks worth.
And has been laid to waste due to my ****up.
I really want to repair it myself if possible.
Please help me if you can. I'm open to any and all ideas.
Thanks in advance.

Alright mate,
Download this HERE
Extract it.
Boot phone into bootloader/fastboot mode.
Connect it via cable.
Run flashall - stock reco.bat and wait until it is done. Your phone will reboot on its own.
Gimme some details if it doesn't work. Don't worry, it'll be fine.#
Also: NEVER RELOCK THE BOOTLOADER VIA COMMAND, that is a sure-way to **** it up much more.

sm00th4f3 said:
Alright mate,
Download this HERE
Extract it.
Boot phone into bootloader/fastboot mode.
Connect it via cable.
Run flashall - stock reco.bat and wait until it is done. Your phone will reboot on its own.
Gimme some details if it doesn't work. Don't worry, it'll be fine.#
Also: NEVER RELOCK THE BOOTLOADER VIA COMMAND, that is a sure-way to **** it up much more.
Click to expand...
Click to collapse
https://forum.xda-developers.com/lenovo-p2/help/stuck-bootloop-reboots-15-holding-power-t3837278
would it work for me?

LeonDsouza123 said:
https://forum.xda-developers.com/lenovo-p2/help/stuck-bootloop-reboots-15-holding-power-t3837278
would it work for me?
Click to expand...
Click to collapse
Seems like you have a faulty battery or something on your hardware side.
Fun fact: getting into recovery(twrp) is done via Fastboot since the button combo is a ***** and isn't reliable. The timing is too stupid done.
The one team rescue files always work as long as you're in Fastboot/bootloader mode.
It's worth the try

I can't thank you enough @sm00th4f3
You are my saviour. It worked perfectly & my phone is working now.
Thank you sooooo much & keep up the good work.

MadMelman said:
I can't thank you enough @sm00th4f3
You are my saviour. It worked perfectly & my phone is working now.
Thank you sooooo much & keep up the good work.
Click to expand...
Click to collapse
Glad it worked

I restored the stock firmware.
My phone boots to the start screen , after I select the language it's unable to detect or connect to the wifi or to the mobile network.
Therfore I cannot proceed to finish the setup.
TWRP shows a firmware error-
- failed to mount '/firmware' (invalid argument)
Please advice @sm00th4f3

MadMelman said:
I restored the stock firmware.
My phone boots to the start screen , after I select the language it's unable to detect or connect to the wifi or to the mobile network.
Therfore I cannot proceed to finish the setup.
TWRP shows a firmware error-
- failed to mount '/firmware' (invalid argument)
Please advice @sm00th4f3
Click to expand...
Click to collapse
You shouldn't restore stock firmware from backup.
After using rescue tool.
Setup your phone from zero.
Or skip through setup.
Reboot to bootloader.
Flash latest twrp 3.2.3 can be found on official website
Change data system format to ext4 if it's not already.
Wipe system, data, cache and dalvik
Flash custom ROM of your choice
Flash gapps
flash magisk for root if you need it
Wipe dalvik and cache
Reboot.
Setup phone.

sm00th4f3 said:
You shouldn't restore stock firmware from backup.
After using rescue tool.
Setup your phone from zero.
Or skip through setup.
Reboot to bootloader.
Flash latest twrp 3.2.3 can be found on official website
Change data system format to ext4 if it's not already.
Wipe system, data, cache and dalvik
Flash custom ROM of your choice
Flash gapps
flash magisk for root if you need it
Wipe dalvik and cache
Reboot.
Setup phone.
Click to expand...
Click to collapse
I followed your instructions. No luck yet.
After flashing the custom rom, the phone bootlooped.
I changed the data & system to ext4 , I get the failed to mount firmware error.
SCREENSHOT:
https://drive.google.com/file/d/1dhBIadnV-olRsWbQjeL8teoPCJeg2U2L/view?usp=sharing

MadMelman said:
I followed your instructions. No luck yet.
After flashing the custom rom, the phone bootlooped.
I changed the data & system to ext4 , I get the failed to mount firmware error.
SCREENSHOT:
https://drive.google.com/file/d/1dhBIadnV-olRsWbQjeL8teoPCJeg2U2L/view?usp=sharing
Click to expand...
Click to collapse
You really are new to this.
Use the rescue tool.
Let the phone boot.
Skip through setup.
Enable developer options.
Make sure and debugging is enabled.
Connect phone to pc.
Grant always access , which popups on phone.
Open a CMD, in the folder of your adb tools.
Use adb reboot bootloader.
Or use the button combo to get to bootloader /Fastboot mode
Flash twrp.
Boot twrp
Reboot to recovery twrp via reboot menu
Change file system of data to ext4
Reboot to recovery again via reboot menu in twrp.
Now use factory reset, then wipe system partition.
Flash custom ROM
Gapps
Magisk if wanted.
Reboot.
Wait max 10min.
Should work.

sm00th4f3 said:
You really are new to this.
Use the rescue tool.
Let the phone boot.
Skip through setup.
Enable developer options.
Make sure and debugging is enabled.
Connect phone to pc.
Grant always access , which popups on phone.
Open a CMD, in the folder of your adb tools.
Use adb reboot bootloader.
Or use the button combo to get to bootloader /Fastboot mode
Flash twrp.
Boot twrp
Reboot to recovery twrp via reboot menu
Change file system of data to ext4
Reboot to recovery again via reboot menu in twrp.
Now use factory reset, then wipe system partition.
Flash custom ROM
Gapps
Magisk if wanted.
Reboot.
Wait max 10min.
Should work.
Click to expand...
Click to collapse
I 'm new to this & I appreciate your help, but
I followed your instructions again yet the error remains the same.
My phone is not detecting any wifi or cellular data - so I cant proceed /skip the process of setting up my stock phone.
And when i flashed the custom rom, the firmware error shows up.
And believe me I've tried a lot, but it just wont work.
I've come too far to give up now, any suggestions?
Here is the screenshot:
https://drive.google.com/file/d/12VTE6xs1Kozg52DhQP3fgBbNeDptXz2j/view?usp=sharing

MadMelman said:
I 'm new to this & I appreciate your help, but
I followed your instructions again yet the error remains the same.
My phone is not detecting any wifi or cellular data - so I cant proceed /skip the process of setting up my stock phone.
And when i flashed the custom rom, the firmware error shows up.
And believe me I've tried a lot, but it just wont work.
I've come too far to give up now, any suggestions?
Here is the screenshot:
https://drive.google.com/file/d/12VTE6xs1Kozg52DhQP3fgBbNeDptXz2j/view?usp=sharing
Click to expand...
Click to collapse
Before flashing twrp.
Use Fastboot oem unlock
.
Try again without custom ROM this time .
I'm looking into it.

Still stuck at the start screen,
I might be wrong but here is what I think is wrong with the phone:
The modem just won't flash therefore no wifi or cellular data.
The firmware is corrupted.
Thanks for your continued support.

MadMelman said:
Still stuck at the start screen,
I might be wrong but here is what I think is wrong with the phone:
The modem just won't flash therefore no wifi or cellular data.
The firmware is corrupted.
Thanks for your continued support.
Click to expand...
Click to collapse
Hello, well i messed up my phone really bad. deleted the bootloader. Phone wasnt working. But then used blank flash to get things working again. Just that it only charges now when i run it in bootloader mode. Now what i think u can do is delete all partitions using fastboot. I dont know the terms or words to say, but you can try to delete all partitions and then flash them again and check. use the stock files or what you call those emmc, modem and those bin files that is used to flash via fastboot. It may help but can be risky. Well hope this makes any sense

Ryan Robert said:
Hello, well i messed up my phone really bad. deleted the bootloader. Phone wasnt working. But then used blank flash to get things working again. Just that it only charges now when i run it in bootloader mode. Now what i think u can do is delete all partitions using fastboot. I dont know the terms or words to say, but you can try to delete all partitions and then flash them again and check. use the stock files or what you call those emmc, modem and those bin files that is used to flash via fastboot. It may help but can be risky. Well hope this makes any sense
Click to expand...
Click to collapse
there is no need to erase your partitions.. Unless you want to brick your device for real.
But you can try it at your own discretion at risk.
i won't help any further since i don't know that much more concerning this kinda problem.
cheers

Fatal Error
MadMelman said:
I 'm new to this & I appreciate your help, but
I followed your instructions again yet the error remains the same.
My phone is not detecting any wifi or cellular data - so I cant proceed /skip the process of setting up my stock phone.
And when i flashed the custom rom, the firmware error shows up.
And believe me I've tried a lot, but it just wont work.
I've come too far to give up now, any suggestions?
Here is the screenshot:
https://drive.google.com/file/d/12VTE6xs1Kozg52DhQP3fgBbNeDptXz2j/view?usp=sharing
Click to expand...
Click to collapse
Hey buddy, I recently ran into same problem as yours. Have you found any working fix for this issue?
Please reply.