Alright, here's the issue. I messed up real bad with my phone. I own a Moto E 1st gen (XT 1022). After receiving the Lollipop 5.1 update I noticed that I didn't have the multi-user option on my phone. Did a little googling and I realized this option was not available to Moto E users for some reason. After a little bit of searching, I found an apparent way to fix this by replacing the build.prop file in device/system with an edited build.prop. I tried doing that in hope to get the multi user option. But somehow it didn't work for me and then my phone didn't boot up correctly. So I tried restoring a backup I had earlier created using TWRP. That didn't work either. So then tried clearing dalvik and cache. Even that didn't work.
But here's the most terrible and stupid thing I did after that: from the wipe menu of TWRP, I checked all the boxes (cache, system, data, EXTERNAL SD EVEN) and cleared everything...!! -_- Now trying to reboot shows "No OS installed. Do you wish to reboot?"
So basically, its a complete junk now. It won't boot up. Just shows the bootloader unlocked warning.
Please could anyone help me reviving the phone...
XDA Visitor said:
Alright, here's the issue. I messed up real bad with my phone. I own a Moto E 1st gen (XT 1022). After receiving the Lollipop 5.1 update I noticed that I didn't have the multi-user option on my phone. Did a little googling and I realized this option was not available to Moto E users for some reason. After a little bit of searching, I found an apparent way to fix this by replacing the build.prop file in device/system with an edited build.prop. I tried doing that in hope to get the multi user option. But somehow it didn't work for me and then my phone didn't boot up correctly. So I tried restoring a backup I had earlier created using TWRP. That didn't work either. So then tried clearing dalvik and cache. Even that didn't work.
But here's the most terrible and stupid thing I did after that: from the wipe menu of TWRP, I checked all the boxes (cache, system, data, EXTERNAL SD EVEN) and cleared everything...!! -_- Now trying to reboot shows "No OS installed. Do you wish to reboot?"
So basically, its a complete junk now. It won't boot up. Just shows the bootloader unlocked warning.
Please could anyone help me reviving the phone...
Click to expand...
Click to collapse
Hello, and thank you for using XDA Assist!
Looks like all is not lost yet, should be about to fastboot flash those images (system, recovery, etc) back. Consider your device factory reset though (as in, all personal info lost).
Please create an account, so you can post in the rest of the site. Then, venture over to the > Motorola Moto E > Moto E Q&A, Help & Troubleshooting forum to explain your predicament in hopes of getting stock fastboot images (or any other solution they cam come up with).
Hope this helps, and good luck!
Related
Hey guys. Before I get to my issue and seek your help , please allow me to give you a bit of background about my self wrt Android OS and nexus devices. I have been a Nexus device user since the N1 days. OS flashing , Custom rom's , kernel patching , etc are nothing new to me. I can safely say that I am a custom rom addict , hence I know the mods for my devices intricately well. With this out of the way , I'd like to share the sequence of events that took place yesterday , which lead to this new thread , wherein I desperately need some expert advice.
- I was running the latest Bigxie 5.0 rom for my 32gb N5. It had root and TWRP and elementalx kernel
- I wanted to upgrade to the 5.0.1 without losing any data , so I first tried to sideload the OTA zip file , which failed with some error. I then followed this guide (http://bit.ly/1wNT36l) . I was able to therefore flash the 5.0.1 without losing data. I re rooted my phone , re flashed the recovery and the kernel
- At the same time I was upgrading my LG g3 to Lollipop. I wanted to try the "Tap & Go" data transfer feature , so I used that process to transfer the data from my current N5 to the new G3. Here is when the issue started. The data transfer didn't go through , as only the email accounts transferred to the G3. At the same time , I got this notification on the Nexus that Tap and Go was used to transfer my email accounts , and this notification couldn't be cleared from the notification panel. For some odd reason , I decided to jump back into recovery and wipe cache and dalvik cache to get rid of this notification
- As soon as I did that specific wipe and restarted the phone , the phone would just loop at the nexus image boot screen. 15 minutes later I went back into recovery and decided to use the "factory reset wipe". That too didn't solve my problem. Frustrated at the turn of events , I reflashed Bigxie's 5.0 rom from my internal storage , via twrp.
- The phone finally booted! But now the problem was that my Sdcard was showing no files. It was all blank. I checked with root explorer / es explorer and even when I hooked up my phone to my pc , the sdcard was showing no files. I could , however , see all my files in the root -- data -- media -- 0 folder. I tried my best to extract all my files from there , but each time I got an error that pretty much meant that no files could be moved from there. Interestingly , when I went into twrp , and went into file manager in the advanced options , it showed all my files on the sdcard as though nothing went wrong. So I could see everything on the sdcard in recovery , but nothing if i booted into the OS.
- Since I had made a backup of most of my data prior to any this happening , with the exception of certain whatsapp data , and after having spent almost 5-6 hours in figuring out where I had possibly gone wrong , I decided to wipe my device clean and just install the stock OS and pack this device away for good
- I downloaded the stock factory image for 5.0 from the official site and went back into bootloader and fastboot flashed each and every file. The phone booted , BUT , now my phone showed only 12GB as the size of the storage with 11GB available. This frazzled me beyond words! How did I reach this stage wherein my internal storage was screwed to this level?
- I again went back into bootloader , flashed 5.0.1 , wiped the device and now the phone is again stuck in a bootloop on the nexus bootscreen
I have finally decided to send the device to the LG service center near my office , but I wanted to share this experience with the community hear and seek their guidance on where I possibly went wrong and what I can do now to put things back together to some degree of normality. Have I somehow damaged something at the hardware level that a change of motherboard may be warranted or is this a pure software screwup?
Thank you for your patience in reading this loooooong story , but I had to explain each and every step in perfect detail.
after flashing stock image.. there is no need to wipe anything... just boot it... takes around 5-10mins max but comes up.....
When it does 12GB on a 32GB device, you just have to factory reset using the option from inside the ROM.
Sent from my Nexus 5 with the N5X LRX22C ROM
tip, just because you know and read rom´s instructions and such, dosent mean you are an experiencied user.this 99% would have save you
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
opssemnik said:
tip, just because you know and read rom´s instructions and such, dosent mean you are an experiencied user.this 99% would have save you
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
Click to expand...
Click to collapse
Well said , and understood. I followed a different set of instructions and flashed back to stock and fixed my device. Thank you for your help.
ecksreturns said:
Well said , and understood. I followed a different set of instructions and flashed back to stock and fixed my device. Thank you for your help.
Click to expand...
Click to collapse
haha no problem, i thoguth i was an experienced user too, but then i bricked mine by flashing lg g2´s rpm partition to get a different partition layout. lol. glad you got your n5 back
I have been trying to root Motorola Moto E XT1023 which comes with a standard stock Android 4.4.4 KitKat.
I have tried many ways. I have been able to unlock the boot loader and able to copy and paste various variations of the SuperSU zip file to the root directory of the phone and to unzip this file with TWRP recovery and or with CWM recovery ( have not tried stock recovery yet but I am not sure whether I have 4.4.4.KitKat stock recovery image ).
Anyway, the zip file unzips and gives all standard messages as per the YouTube videos. I have noticed, in some installation, when the SuperSU got unzippes, there is a missing line : " SETTING PERMISSIONS ". I have also noticed the " PARTITION MISMATCH " message when TWRP recovery is written. However, I have seen people also having this on YouTube and their devices rooted perfectly.
I guess, the final goal of the rooting process is to install SuperSU which I have done in many different ways and many different versions. Regardless, although SuperSU installation says " SUCCESS ", I DO NOT HAVE THE SU ICON IN THE GENERAL APP LIST AND VARIOUS ROOT CHECKERS REPORT THE CELLPHONE HAS NOT BEEN ROOTED.
I WONDER WHETHER THERE IS SOMETHING ELSE I HAVE TO DO TO SETUP THE SUPERSU AFTER UNZIPPED. OR DO I USE WRONG VERSIONS. WHICH IS THE CORRECT VERSION? which IS THE CORRECT TWRP VERSION?
I have also tried to use the popular batch installers ( version 2 and 3 ). The same result.
I have also tried to use mfastboot V 2 for everything. Also tried the general purpose fastboot for everything. The same result.
I have not slept for 2 nights because of thie problem with the inability to root the cellphone, something which normal people with normal Moto E XT1023 do on YouTube for less than 30 minutes.
PLEASE, HELP!
Hi there,
All you need is in this thread: [SCRIPT] Moto E XT1023 super easy ROOT, RECOVERY, & RESTORE
For more questions related to your device please ask directly here: Motorola Moto E Help and Troubleshooting
Good luck
Problem solved!
PROBLEM SOLVED!
USED THE BATCH SUPER UTILITY V 3. I THINK WHAT HAVE HELPED WAS TO DO A FACTORY RESET AFTER THE TWRP REBOOT. FACTORY RESET REBOOTS AFTER PREPARING THE SYSTEM. THE TWRP REBOOT DID NOT DO MUCH BUT THE REBOOT OF THE FACTORY RESET THEREAFTER DID. TWRP DID SHOW UP AFTER THE FACTORY RESET REBOOT AND INSTALLED SOMETHING.
I have tried to install XDA and some XDA APK before rooting. I have also had the Motorola protection and tracking enebled. I am not sure whether these have created the problem.
Here is what I have done to root the device :
ON THE PC :
UNINSTALLED MALWAREBYTES TO REINSTALL AFTER.
STOPPED WINDOWS DEFENDER REAL PROTECTION TO START AFTER.
KINGO ROOT DID NOT WORK.
ON THE CELLULAR TELEPHONE :
Did not remove the SIM card and signed in normally after the factory reboot. Rmoving the SIM card and not logging in after factory reset may help.
UNINSTALLED CLEAN MASTER ANTIVIRUS AND THE WHOLE PACKAGE, BATTERY DOCTOR, ES, A COUPLE OF COMMAND SHELL PROGRAMS, ALIEXPRESS, EBAY, ADOBE, SWIFT KEYBOARD, ETCETERA, SOME MAINLY STARTUP PROGRAMS.
DISABLED INFORM MOTOROLA IN TWO PLACES OF SETTINGS.
AFTER THE BATCH, TWRP AND INSTRUCTIONS, DID FACTORY RESET WITH DISCONNECTED USB CABLE.
THE FACTORY RESET REBOOTED AND THE TWRP DID SOME JOBE DURING REBOOT.
AFTER THE FACTORY RESET REBOOT, SU ICON WAS IN THE APP LIST AND WORKED. THE DEVICE WAS ROOTED.
DISABLED THE AUTOMATICALLY STARTED UPDATES AFTER THE FACTORY REBOOT RESET TO REENABLE THEM AND INSTALL THEM AFTER.
CHECKED WITH 4 ROOT CHECKERS. ALL REPORTED THE DEVICE WAS ROOTED OK.
StevenStanleyBayes said:
PROBLEM SOLVED!
Click to expand...
Click to collapse
Glad to hear that.
Thread closed.
As many of you may know, Nvidia has recalled their Shield Tablets. I'll be getting a replacement soon. I'll be rooting it as soon as possible when I get it, but first I have a few questions.
First of all, I rooted my tablet using a guide at IBTimes (that used info from XDA forums) installing CWM recovery.
After rooting I installed Link2SD, pretty much the reason I rooted, to save up some space on my internal memory. Everything was going fine, until I received the recall notice. I moved all my app files back to the internal memory, deleted Link2SD, ran a full unroot on SuperSU, (after a while of hanging on the "Please Wait" screen the app just crashed, it wouldn't load up and Root Checker said I had no root access after rebooting.
I don't know whether this was supposed to happen or whether it should have gone more smoothly, please give me an answer to this and tell me if it affected my system in any way) and fastboot flashed the stock recovery.img.
However when I tried to install the update, I got a red triangle error. After checking the log I got an error saying "Package expects build fingerprint of ... or ..., this device has ...."
I can't remember what the fingerprints were, but the first one was something that began with "nvidia/", had a bunch of numbers in the middle followed by an underscore, then it ended with "/release-keys".
However the device's current build fingerprint was exactly the same as the first, except that it cut off halfway through, right after the numbers and the underscore.
I tried resetting my cache, I tried a wipe of the user data. The only way to fix this for me was to re-install a bunch of stock images - recovery.img, boot.img, system.img, etc.
I don't want to wipe my data next time. So I ask for this in my answer:
- An explanation of what the error means
- How this error is caused
- A way to fix this error without wiping my device
- How to prevent this error
- If what happened to SuperSU in my case is normal and if it affected my device in some way
- And, if possible, a way to install the update successfully without getting this error and without having to unroot or remove CWM, and details on how to do this method and any risks.
Thanks in advance. An answer soon would be appreciated.
Hi there,
You'd be best served asking for help from the experts who own your device here:
Shield Tablet Q&A, Help & Troubleshooting
Good luck
My first post here is exactly as the title implies. I rooted my lg g3 us990 with kingroot(after attempting others) and have been using it for a while, working perfectly. I then got the idea to start learning about custom roms and attempting to install one.
So I used twrp and set up my recovery, I then backed up my current state. I found a rom that I assumed "should" work, CM12.1 and added it to my qeue on twrp. Starting out good.
I wiped my all options except internal storage and sd card and proceeded to flash CM12. All seemed well, it rebooted, with boot error message 1003 in the top left, on the LG boot page. Then, the cyanogenmod face came up, slightly uneven, and the boot went on for an hour. Not so good.
No biggie, I still had a backup to go back too right? Wrong. I went through the same steps to wipe memory, then restore my backup. LG screen, same error message, boot loop, CRAP.
Any help would be greatly appreciated to get my phone working again. I understand the rom not working, but why wouldnt my backup work?
Note, I am able to get into both twrp recovery and download mode.
Also, my twrp is displaying the wrong time, is that normal?
paul8m3 said:
My first post here is exactly as the title implies. I rooted my lg g3 us990 with kingroot(after attempting others) and have been using it for a while, working perfectly. I then got the idea to start learning about custom roms and attempting to install one.
So I used twrp and set up my recovery, I then backed up my current state. I found a rom that I assumed "should" work, CM12.1 and added it to my qeue on twrp. Starting out good.
I wiped my all options except internal storage and sd card and proceeded to flash CM12. All seemed well, it rebooted, with boot error message 1003 in the top left, on the LG boot page. Then, the cyanogenmod face came up, slightly uneven, and the boot went on for an hour. Not so good.
No biggie, I still had a backup to go back too right? Wrong. I went through the same steps to wipe memory, then restore my backup. LG screen, same error message, boot loop, CRAP.
Any help would be greatly appreciated to get my phone working again. I understand the rom not working, but why wouldnt my backup work?
Click to expand...
Click to collapse
Greetings and welcome to assist. I think your issue is related to a locked bootloader so unlocking it should fix it, I found this thread that might help you
https://forum.xda-developers.com/tmobile-g4/help/totally-screwed-secure-boot-1003-error-t3326495
Good Luck
Sawdoctor
sawdoctor said:
Greetings and welcome to assist. I think your issue is related to a locked bootloader so unlocking it should fix it, I found this thread that might help you
https://forum.xda-developers.com/tmobile-g4/help/totally-screwed-secure-boot-1003-error-t3326495
Good Luck
Sawdoctor
Click to expand...
Click to collapse
Thank you for the reply. I was fortunate enough to have a generous person give me a bunch of compatible roms and help me through my 'functionality' problem. Next is working on getting rid of that error message.
im new to all this rooting and flashing stuff and i did search quite thoroughly before resorting to posting on here. Ok so somehow i rooted and took the system app TextNow off of the phone since then ive tried hard resetting but now all the phone does after booting it has a little txt box that pops up over and over so much so that its impossible to do anything but power down and it reads" unfortunately TextNowOOBE has stopped...... Ok" . How can i fix this.... Ive reset the phone through recovery and cache partition both have been wiped. Plz someone help me
sjrjr4364 said:
im new to all this rooting and flashing stuff and i did search quite thoroughly before resorting to posting on here. Ok so somehow i rooted and took the system app TextNow off of the phone since then ive tried hard resetting but now all the phone does after booting it has a little txt box that pops up over and over so much so that its impossible to do anything but power down and it reads" unfortunately TextNowOOBE has stopped...... Ok" . How can i fix this.... Ive reset the phone through recovery and cache partition both have been wiped. Plz someone help me
Click to expand...
Click to collapse
#1 rule make a backup in recovery before tinkering
Aside from restoring a backup, the easiest way to get your phone working again would be to flash a fresh ROM. For example, Albertos AOSP is quite stable and up to date. You will need that ROM.zip and a compatible gapps.zip. wipe everything clean and flash those in recovery.
You will lose all your data.
I do not know what TextNow is, but if you need the "stock ROM" you may need to restore factory firmware via PC- you will lose all your data
What exactly are you trying to do?