Full error message: Failed flashing process. phone(0000) Phone is not compatable with multi-interface super-file. (ox703b): phone connected
This is information only hopefully for someone who experienced the same issue that I did.
Long story short, I ended up boot looping my X by replacing a system file through Root Explorer and not setting the permissions properly before. Going into a panic, I started gathering the files to re-flash 2.1. When I tried to run RSD, I received the above error message. I tried different versions of RSD, different "gifts", different computers and operating systems. I hit google and was unable to find anything to help. I ended up returning my phone to Wal*Mart and got a new one (told them it bricked during an OTA update...)
After sending some messages to rootzwiki and alldroid for some help, I found that it was because the battery was not at 50% or higher (which makes sense because I let the phone loop for a couple hours disconnected from the PC in HOPES that it would come back). I'm not saying this may be the fix for all issues with the above error message, but it may be something else to try if you have tried everything and just about pulled your hair out...
Hope this helps!
FYI the only version of RSD Lite that will work with the X is veriosn 4.7, but you also have to have the OMAP patch file installed otherwise it will still not work. That said I'm not sure which version you tried or if you had it setup correctly but that could be why you wer having issues also besides the battery not being charged enough.
will2live said:
FYI the only version of RSD Lite that will work with the X is veriosn 4.7, but you also have to have the OMAP patch file installed otherwise it will still not work. That said I'm not sure which version you tried or if you had it setup correctly but that could be why you wer having issues also besides the battery not being charged enough.
Click to expand...
Click to collapse
I started with 4.7 and worked backwards with RSD. I have been able to flash my second X with the same config settings on 4.7. The only thing that changed was the charge on the battery
Where can I find the omap patch file is it the ini file located in the rdslite 4.7+patch.zip? Im getting the same error above but my battery is 96% full. This is happening on two differnt Windows 7 32 bit machines..
Sent from my DROIDX using XDA App
Never mind it is the patch and its now restoring.
I can upload my version of RSD and the patch I have when I get home from school.
It is going to be about 3 hours.
No need, found here: http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X/Page-3.html
Direct link to SBF: http://www.wikifilez.com/Root Files/MotoDroidX/RSDLite-4.7+patch.zip
uninstall all the moto drivers and re-install them again. see if that works.
Related
I've seen a few similar threads, but no one has a solution to this problem yet.
My Milestone tried to reboot while using the Motorola Update program, and has been stuck at the M screen since.
It is impossible to get into Recovery Mode.
Bootloader mode works. I have tried flashing an sbf, both with RSD and sbf_flash on Linux.
RSD always finishes and asks me to reboot the phone manually. sbf_flash simply tells me it's finished.
Either way, I'm right back where I started. I can remove the battery, get into bootloader, and reconnect and RSD will tell me it Passed. It has not.
I have tried a plain vulnerable recovery, GOT, Stock 2.2.1 and stock 2.1 sbfs for Great Britain, Southeast Asia, and Europe. I have downloaded each at least 2 times.
I have used RDS lite versions 4.6, 4.7, and 5.0, and sbf_flash for linux. I have tried Windows XP and 7.
I can still charge my phone with a wall charger, though very slowly.
What do I do? Are there some kind of error logs that could help? Some other, fool-proof image to try flashing? I appreciate any help, I'm rather desperate.
Have you tried updating your USB drivers for your phone? Perhaps there is something there that is not allowing a successful flash.
Several times, and the problem isn't just in Windows.
Surely someone must have some ideas. Please help me.
So anyone figure out why some ROMs fail to flash on to some devices?
I have a theory, I think it has something to do with "fastboot flash partition gpt_main0.bin" failing to flash on certain devices depending on which rom it's sourced from, also depending on which the device currently has already flashed successfully..
Although this is beyond my comprehension, I don't know the reasoning and or the correct wording. Perhaps someone with more knowledge could shed some insight..
I.E. I can successfully "fastboot flash partition gpt_main0.bin" on my device using MX retail, Bell and AT&T versions/copies will fail to flash on my device and I think it is because the last complete successful flash I was able to do with RSDlite was MX retail.
Anyone got any ideas?
The Atrix HD can be a pain
Hey @clockcycle does the flashing of gpt_main0.bin actually "fail" or does it freeze up? I know that you cannot flash an earlier version of "gpt_main0.bin" over a newer one. I had the same issue as you've described while manually flashing and RSD doesn't work for me anymore. It took me a month of trying different approaches to get back to stock just so I could make a nandroid because my original backup corrupted. Anyway, Myth Tools would get the furthest while flashing stock, but would freeze up. I'm assuming you've tried Myth Tools and failed. However, I discovered something (in frustration and desperation) that totally worked for me. Soft bricks don't scare me anymore so I tried the method I describe in this post
[TheJeremyWhite;49794944]Disclaimer: Even though this worked for me I am not responsible if you brick your phone, I am simply sharing my experience
Okay, this is not for the faint of heart and is going to sound a little backward but it just worked for me 5mins ago. I am running Windows 8.1 Pro 64bit, so there shouldn't be a problem with your setup. I was having the same problem until I just double clicked on flashing.bat or main.bat instead of running as admin. After all I AM the admin of my PC. Then, it worked perfect...until flashing the tz.mbn file and froze up while writing the file. I thought mmm...it shouldn't take that long to write such a small file, and writing happens on the phone side (I believe) so I hit the phone's power button while leaving the Myth Tools window open, which disconnected the phone obviously. I booted back into fastboot and it continued from where it left off. (Note: I did this a few weeks ago when I lost my radios and manually flashed the modem file, which froze, but I followed the same procedure and it successfully flashed it) Then when it got to the last system.img chunk (it writes it in small chunks of 30mb and the last one is smaller, that's how I knew it was the last one) it froze again. I let it sit for about 5mins just to make sure it was written to the phone the repeated the sequence to reboot manually into fastboot and bang, once again it continued right where it left off. one or two more freezes and voila...it rebooted right back to stock.
But honestly, I have no clue why some ROM's fail, but I now know how to flash any one of them without any issues.
TheJeremyWhite said:
Hey @clockcycle does the flashing of gpt_main0.bin actually "fail" or does it freeze up? I know that you cannot flash an earlier version of "gpt_main0.bin" over a newer one. I had the same issue as you've described while manually flashing and RSD doesn't work for me anymore. It took me a month of trying different approaches to get back to stock just so I could make a nandroid because my original backup corrupted. Anyway, Myth Tools would get the furthest while flashing stock, but would freeze up. I'm assuming you've tried Myth Tools and failed. However, I discovered something (in frustration and desperation) that totally worked for me. Soft bricks don't scare me anymore so I tried the method I describe in this post
[TheJeremyWhite;49794944]Disclaimer: Even though this worked for me I am not responsible if you brick your phone, I am simply sharing my experience
Okay, this is not for the faint of heart and is going to sound a little backward but it just worked for me 5mins ago. I am running Windows 8.1 Pro 64bit, so there shouldn't be a problem with your setup. I was having the same problem until I just double clicked on flashing.bat or main.bat instead of running as admin. After all I AM the admin of my PC. Then, it worked perfect...until flashing the tz.mbn file and froze up while writing the file. I thought mmm...it shouldn't take that long to write such a small file, and writing happens on the phone side (I believe) so I hit the phone's power button while leaving the Myth Tools window open, which disconnected the phone obviously. I booted back into fastboot and it continued from where it left off. (Note: I did this a few weeks ago when I lost my radios and manually flashed the modem file, which froze, but I followed the same procedure and it successfully flashed it) Then when it got to the last system.img chunk (it writes it in small chunks of 30mb and the last one is smaller, that's how I knew it was the last one) it froze again. I let it sit for about 5mins just to make sure it was written to the phone the repeated the sequence to reboot manually into fastboot and bang, once again it continued right where it left off. one or two more freezes and voila...it rebooted right back to stock.
But honestly, I have no clue why some ROM's fail, but I now know how to flash any one of them without any issues.
Click to expand...
Click to collapse
Fails to downgrade.
clockcycle said:
Fails to downgrade.
Click to expand...
Click to collapse
Haha, you're absolutely right. Thanks for pointing that out.
Sent from my MB886 using XDA Premium 4 mobile app
OK, this post might be long. Feel free to skim. I just want to let people know everything that I've done.
So, my VS980 was rooted and I was trying to install a new ROM. I was going to try out Cloudy G2, but the installation routine only gave me international variants to choose from. I picked one anyway and my phone has been hosed since. I didn't have any download mode or recovery or anything.
I was able to get download mode back by extracting part of the firmware out with the LG Firmware Extractor and flashing that through fastboot. So, that part worked. I have download mode. I was going to try to restore my 24A firmware with a KDZ file and the old LG flash tool v 1.8.1 (the one where you put the ADB interface on COM41, and you use the updated megaunlock.dll, etc), but that no longer works for me. It keeps giving me the "failed previous load" error. I can't find a fix for that.
So, I've been trying to flash it (or firmware 26) with the LG Flash Tool 2014 (the one where you pick "Republic of Korea"). That will only get to between 25 and 49%, and then crash with an unknown error.
In between trying that option, I found instructions for extracting all of the bits out of the firmware and then flashing them to the phone partitions one by one. That seemed to work except I kept getting a security error on bootup. The only fix I found for that was to flash with the first flash tool I mentioned. Ugh.
The last time I rooted my phone and ran a custom ROM, my desktop USBs couldn't communicate with my phone very well, but my laptop could. This time not even the laptop's working. I even bought a new USB addon card (I needed it anyway, the USB3 ports on this suck). That seemed to get the computer to see the phone better, but it didn't solve my problems.
Can anyone help with this? I've scoured tons of directions already.
Thank you for any help
Wackman
A little bit of progress
So, I finally got the older flash tool v 1.8.1 to start working. I've almost got it to flash the stock .TOT file (the KDZ file keeps giving me the "failed previous load" error). Now, I've kinda hit a new roadblock.
I think I mentioned that I got into this mess by trying to flash the CloudyG2 ROM, but that it's for international variants. When the flash tool tries to flash the firmware for the VS980, it thinks I have an F320S, and says wrong phone. Anyone know a way around this? I still only have access to download mode. No fastboot, no recovery, no ADB.
any luck? I bricked my G2 last night and I'm trying the flashtool to get back to stock 27A right now. Did you update your C++ library? I read somewhere that that can cause issues with flashtool..
Found my fire tablet with a black screen and in Amazon system recovery <3e> this morning - not sure how it got into that state & how to get out of it. To my knowledge I didn't press any combination of keys that would get me into that state. It had been only very low battery when I plugged it into the electrical socket last night but I didn't touch it until the morning when I found it in this black screen state.
From searching I think this is the Amazon version of Android System Recovery screen. The exact options are:
-------
Amazon system recovery <3>
Volume up/down to move highlight;
enter button to select.
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
----------
I haven't rooted the tablet although I did apply the "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)"
(http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122)
I've had it for about a month without problems although a couple of days ago it kept trying to update several times in succession.
It has attempted to update a couple of times in the past, which put me into a panic at the time but when I'd check afterwards it would still show 5.0.1. firmware. Also the difference this time was that in the past it would only attempt to update the once, not several times in succession.
I'd assumed that installing "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)" doesn't stop the fire downloading updates but prevents them being installed. So when it happened in the past I didn't worry.
I'm not sure what to do (logically I'd assume I should just select the 1st option and reboot) but I'm not sure how I even got into this screen and if there's a reason for it so hoped someone might be able to advise me.
With thanks & crossed fingers
Frankie
Sorry - one other question!
Which key is the "enter button"?
FrankieChen said:
Sorry - one other question!
Which key is the "enter button"?
Click to expand...
Click to collapse
I've not used it but as we only have three buttons I'm going with the power button.
Pond-life said:
I've not used it but as we only have three buttons I'm going with the power button.
Click to expand...
Click to collapse
That's what I suspected!
Update
Well I ran out of power so the tablet switched off.
When I plugged it into an electricity socket, I decided to try the "reboot system now" option but it just rebooted and cam back to the same screen. I tried it about 4 times with the same result so I tried the "power down" option but it still returned to the same screen when switched back on.
Would really appreciate anyone's help.
Hmm, is there anything in the recovery logs?
Maybe reboot to bootloader, and see if it'll let you twrp to it from a pc, head to the twrp thread and grab the files.
fastboot boot TWRP_Fire_2.8.7.0.img
If it'll do that it's not on 5.1.1 at least, if not it might have tried to get there.
I haven't followed your instructions yet as after I posted last, it started to flash an error message along the lines of battery was too low to "factory reset" and something else - I don't recall what though. I didn't actually select any options apart from reboot and power down.
It was plugged in at the time but I unplugged it & replugged it in, in case for some reason it wasn't charging.
Since then the error message has stopped flashing and I just have a blank screen although you can see it is backlit. Pressing the power button has no effect
And that's on the charger it came with?
It's not looking good.
FrankieChen said:
...I haven't rooted the tablet although I did apply the "Installing Google Framework/Playstore...
...I'd assumed that installing "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)" doesn't stop the fire downloading updates but prevents them being installed....
Click to expand...
Click to collapse
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
julianpaul said:
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
Click to expand...
Click to collapse
True but the thread he's referring to does offer that function as an option in the batch file.
http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122
Tomsgt has put together a little install bat (Amazon-Fire-5th-Gen-Install-Play-Store.zip)
Now includes Removing Advertising and Blocks Over the Air System Updates (02 Nov 2015)
Click to expand...
Click to collapse
julianpaul said:
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
Click to expand...
Click to collapse
It's still useful information - thanks
It's on the charger it came with and it has finally returned to the same Amazon system recovery screen.
In regards to preventing the updates - I think I did that when I installed the google apps but it was the 1st time i ever did this (it's my 1st tablet), and as it was over a month ago I can't be sure - this is all very new to me.
There are 4 recovery logs, completely meaningless to me.
/cache/recovery/last_kmsg
/cache/recovery/last_log
/cache/recovery/last_log1
/cache/recovery/last_log2
the kmsg log zooms past too fast to read with endless pages dealing with "swapper/0"
the last_log seems to have stuff reffering to tzdata, build, product.cpu, ro.product, dalvik and so on . Log1 and log2 seem to be similar stuff but shorter.
Any idea what I should be looking for?
I hoped it would be readable, build number might yield clues.
Given it will show something seems worth trying to see if twrp can see it in bootloader.
It may not have any thing to do with the updates as it was working after the updates had tried to install though I have to admit I only used it for a few minutes and I didn't check it before I plugged it in to charge the night before I found the black screen.
I don't actually have a clue what you mean when you say "twrp can see it in bootloader." so I will have to spend some time reading the forums to figure out what to do.
In desperation this morning I took the wipe data/factory reset option but it didn't work. It returned with the same screen and the error message
E:Error in /cache/recovery/dropbox_last_kmsg (Read-only file system)
I had installed the dropbox app but I had never actually signed in so there wouldn't be any data there.
After rebooting and being returned to the same screen, I attempted again to wipe data/factory reset.
This time it gave the message "data wipe complete" but still returned to the Recovery screen.
I've read the term "bricked" in several of the forums - is this what has happened to my device?
I wondered if I should contact Amazon about it as it's still under warranty but wondered if by installing gapps (and most likely having prevented updates as I followed all the instructions), whether I'd have invalidated my warranty.
FrankieChen said:
After rebooting and being returned to the same screen, I attempted again to wipe data/factory reset.
This time it gave the message "data wipe complete" but still returned to the Recovery screen.
I've read the term "bricked" in several of the forums - is this what has happened to my device?
I wondered if I should contact Amazon about it as it's still under warranty but wondered if by installing gapps (and most likely having prevented updates as I followed all the instructions), whether I'd have invalidated my warranty.
Click to expand...
Click to collapse
At this point, if you have adb drivers (or are comfortable installing them) you may as well try sideloading an update bin file. Links are here. I'd get the 3820 file.
If you want to do this, post back and I or someone will give you the steps. Otherwise, Amazon has been good about replacing tablets if you just describe what you say in the 1st paragraph of your post.
FrankieChen said:
It may not have any thing to do with the updates as it was working after the updates had tried to install though I have to admit I only used it for a few minutes and I didn't check it before I plugged it in to charge the night before I found the black screen.
I don't actually have a clue what you mean when you say "twrp can see it in bootloader." so I will have to spend some time reading the forums to figure out what to do.
Click to expand...
Click to collapse
use the reboot to bootloader option
set pc up with fastboot and see if it can be booted into twrp by fastboot
http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9
http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548
Thank you for the replies. Sorry not to have responded earlier, I had a busy few days and although I have spent a lot of hours trying to read through the forums and find out about twrp, this is the 1st opportunity I have had to get back to trying to resolve the problem.
If I understand correctly, DoLooper has suggested sideloading an update bin file. (3820). I just started trying to do this but as the file to be downloaded is over 600MB and I am on a very slow connection it's showing it's going to take between 7-8 hours to download. If I take this option I will need to wait until tomorrow when I can get to a faster internet.
Pond-life, you have suggested that I
1. "use the reboot to bootloader option"
I'm presuming that this means that I have to select this option from the recovery screen on the tablet - does the tablet have to be attached to the pc via the USB cable when I select the option?
What should I expect once I have selected this option?
Would the tablet not need to be rooted to access the bootloader (as it isn't)?
2. "set pc up with fastboot and see if it can be booted into twrp by fastboot"
When I 1st got the tablet I had difficulties getting the adb drivers to install on my pc and after several days of trying I ended up doing it on another pc which I no longer have access to.
I have tried again to reinstall the drivers using rootjunkies file but again without success. I tried doing it using that method as I remember trying to do it that way (what felt like a billion times) though I don't remember if I finally ended up succeeding with that method or another.
I followed your link "http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9" and tried the 1st method
"[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by Snoop05"
running the "adb-setup-1.4.3.exe" I get "0 files copied" after selecting "Yes to install ADB system-wide" which I recall was the problem (zero files copied) that I had previously.
Openning Device Manager after this does show any Fire or Android devices even when the tablet is connected so I'm assuming that the adb driver installation is failing.
I tried again with "adb-setup-1.3.exe". This time I had 4 files copied and got fire listed in the device manager but when I tried to update the driver I am not given the Android option in the list when I select the option to install driver.
I googled to see if anyone else had this error and I found that some peoplehad difficulties installing on XP but seems that MTP not being supported is the reason and it is resolved by installing WMP v10 and above. I have v11 so presume that's not the problem.
I don't have access to another computer at the moment to try and install the adb drivers but should be able to use another one tomorrow. Last time when I got the drivers to install it was on a vista machine so I wondered if that might have something to do with it.
The other thing that occurred to me was maybe there is something wrong with the cable as I only get the fire shown in the device manager for a few moments before it refreshes and then the fire is no longer shown.
I wondered if I should try to use USBDeview (as per http://www.inlovewithandroid.com/android-usb-connection-problems.html) to see if that is the problem. Certainly if I can the drivers installed on another pc it might suggest that there's a problem with mine.
Anyway, if I get the adb drivers to install successfully on another pc, could you explain what I am trying to do by "booted into twrp by fastboot"? Sorry to be so useless!
Huge thanks
Yeah the files needed will all be pretty hefty. So if thinking about going to a custom rom this would be a good time. Though wouldn't download one or the stock until you've seen if you can use it.
1. Yeah I did mean choose that option on that menu you have onscreen. Doesn't need to be attached to go to the screen technically, but won't be able to do anything there until it is connected so no benefit in not waiting until you are. No doesn't need to be rooted. You'd expect it to go to an almost blank screen with =>FASTBOOT mode.... on it in landscape.
2. On plus side you wouldn't need the adb drivers... But the fastboot ones are probably similarly tricky. These ones worked for me https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Though I've not used XP.
If it will fastboot into twrp then you can put the original stock rom on or either of the custom ones from there, so it's not dead and can get to downloading. (or 5.1.1 stock using the safe twrp method)
Did you use a different cable on the machine you got it to work on then? If not probably not the cable.
Pond-life said:
Yeah the files needed will all be pretty hefty. So if thinking about going to a custom rom this would be a good time. Though wouldn't download one or the stock until you've seen if you can use it.
1. Yeah I did mean choose that option on that menu you have onscreen. Doesn't need to be attached to go to the screen technically, but won't be able to do anything there until it is connected so no benefit in not waiting until you are. No doesn't need to be rooted. You'd expect it to go to an almost blank screen with =>FASTBOOT mode.... on it in landscape.
2. On plus side you wouldn't need the adb drivers... But the fastboot ones are probably similarly tricky. These ones worked for me https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Though I've not used XP.
If it will fastboot into twrp then you can put the original stock rom on or either of the custom ones from there, so it's not dead and can get to downloading. (or 5.1.1 stock using the safe twrp method)
Did you use a different cable on the machine you got it to work on then? If not probably not the cable.
Click to expand...
Click to collapse
Thanks for all your help Pond Life.
I had such difficulties get the files to download that in the end I gave up and rang Amazon and they offered to send me a replacement.
Sorry to bail out, this is all new to me and most of what everyone has said has me completely baffled so I've decided to take the easy way out.
Thank you again - I really appreciated all your advice.
FrankieChen said:
Thanks for all your help Pond Life.
I had such difficulties get the files to download that in the end I gave up and rang Amazon and they offered to send me a replacement.
Sorry to bail out, this is all new to me and most of what everyone has said has me completely baffled so I've decided to take the easy way out.
Thank you again - I really appreciated all your advice.
Click to expand...
Click to collapse
Better luck with the new one
Hello! If you're reading this i hope you can help me, cause right now i have no idea what to do. First I'm going to tell my phone specs. I have a rooted, Moto X 2nd Edition XT1092, without any custom ROM installed, running Android Lollipop, with the option to upgrade to marshmallow and an unlocked bootloader. It uses the google launcher by default. I am pretty experienced with root as i have used rooted android phones for more than 4 years now (my first one was a Samsung Galaxy S2) and haven't had any problems until now. I had recently downloaded FaceNiff, one of the sniffing apps for android, and when i pressed start, it would automatically stop. I thought it was maybe a problem of the apps compatibility with my phone, but after researching for a long time, nothing came up so i decided to try another sniffing app. I moved on to DroidSniff, yet, I had the same problem, but this one wouldn't only stop, it would crash. I researched on this app too. Nothing. So I later downloaded one called DroidSheep, and when I started this one, I was lucky that an error was displayed, it was something about Position Independent Executables (PIE), it said "Only Position Independent Executables are supported" or something around those lines. So I decided to research PIE, and I found on the XDA Forums that you could fix this by changing the system/bin/linker file for a custom linker file, which a download link was provided for. I downloaded the file, changed it for the old linker file and tried the apps again. Apparently, I didn't have root access anymore! None of the root apps worked, I thought maybe I had to reboot my phone for my root to come back or for the custom linker to work. So i powered off my phone, turned it on, but instead of turning on, it would say the "Warning unlocked bootloader" thing, and then show a picture of and Android lying down with a caution sign, with the text "No Command" underneath. It's currently in this state, and the phone won't stop repeating this until it runs out of battery. The good thing is I can hold the power and volume down button to enter the fastboot menu, and i can then go into recovery. After this happened, I went to recovery and factory reset my phone, but it still didn't work, so I factory reset it again. It still charges, with a wall plug and with a computer. I think the computer recognises the phone, and I'm pretty sure I have USB Debugging enabled.
To sum this up, I changed the file system/bin/linker for a modified version of it and my phone won't boot up.
Custom linker file: http://forum.xda-developers.com/attachment.php?attachmentid=2821644&d=1403933203
Link to the website where it said you can change the linker files to fix the PIE problem: http://forum.xda-developers.com/google-nexus-5/development/fix-bypassing-pie-security-check-t2797731/page1
AgusC said:
Hello! If you're reading this i hope you can help me, cause right now i have no idea what to do. First I'm going to tell my phone specs. I have a rooted, Moto X 2nd Edition XT1092, without any custom ROM installed, running Android Lollipop, with the option to upgrade to marshmallow and an unlocked bootloader. It uses the google launcher by default. I am pretty experienced with root as i have used rooted android phones for more than 4 years now (my first one was a Samsung Galaxy S2) and haven't had any problems until now. I had recently downloaded FaceNiff, one of the sniffing apps for android, and when i pressed start, it would automatically stop. I thought it was maybe a problem of the apps compatibility with my phone, but after researching for a long time, nothing came up so i decided to try another sniffing app. I moved on to DroidSniff, yet, I had the same problem, but this one wouldn't only stop, it would crash. I researched on this app too. Nothing. So I later downloaded one called DroidSheep, and when I started this one, I was lucky that an error was displayed, it was something about Position Independent Executables (PIE), it said "Only Position Independent Executables are supported" or something around those lines. So I decided to research PIE, and I found on the XDA Forums that you could fix this by changing the system/bin/linker file for a custom linker file, which a download link was provided for. I downloaded the file, changed it for the old linker file and tried the apps again. Apparently, I didn't have root access anymore! None of the root apps worked, I thought maybe I had to reboot my phone for my root to come back or for the custom linker to work. So i powered off my phone, turned it on, but instead of turning on, it would say the "Warning unlocked bootloader" thing, and then show a picture of and Android lying down with a caution sign, with the text "No Command" underneath. It's currently in this state, and the phone won't stop repeating this until it runs out of battery. The good thing is I can hold the power and volume down button to enter the fastboot menu, and i can then go into recovery. After this happened, I went to recovery and factory reset my phone, but it still didn't work, so I factory reset it again. It still charges, with a wall plug and with a computer. I think the computer recognises the phone, and I'm pretty sure I have USB Debugging enabled.
To sum this up, I changed the file system/bin/linker for a modified version of it and my phone won't boot up.
Custom linker file: http://forum.xda-developers.com/attachment.php?attachmentid=2821644&d=1403933203
Link to the website where it said you can change the linker files to fix the PIE problem: http://forum.xda-developers.com/goo...x-bypassing-pie-security-check-t2797731/page1
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. For the best available help, I'm going to move your question to your device's Q&A forum. Good luck!
AgusC said:
Hello! If you're reading this i hope you can help me, cause right now i have no idea what to do. First I'm going to tell my phone specs. I have a rooted, Moto X 2nd Edition XT1092, without any custom ROM installed, running Android Lollipop, with the option (...)
Click to expand...
Click to collapse
I do not know if finally you fixed the problem with your moto, but you can do a clean install of a stock rom, or maybe cm12/cm12.1...
How to, and link with the rom: http://forum.xda-developers.com/moto-x-2014/general/img-5-0-reteuall-xt1092-lxe22-46-19-t2997745
cyker31 said:
I do not know if finally you fixed the problem with your moto, but you can do a clean install of a stock rom, or maybe cm12/cm12.1...
How to, and link with the rom: http://forum.xda-developers.com/moto-x-2014/general/img-5-0-reteuall-xt1092-lxe22-46-19-t2997745
Click to expand...
Click to collapse
Hey! Thanks a lot for the advice, ill try to do what you said, although im not sure how to use fastboot. Ill tell you if it worked.