[Completed] HELP! status 7 on possibly unrooted, factory resetted moto g 2014 - XDA Assist

Hi all,
I tried to update my Motorola Moto G 2014, but it showed status 7 error. So I contacted Motorola and they said that I rooted my phone. So I connected my phone to my PC and found supersu246.apk. I never installed this, but I guessed somehow some app rooted my phone once. I began thinking and suspected it was when I was desperate to recover my lost photos and downloaded all sorts of programs (possibly Dr. Phone).
So: I deleted supersu246.apk from my internalized SD card and factory resetted my phone. Status 7 still pops up. How do I fix this? I do not want to have a rooted phone btw.
Should I follow the instructions in this link: https://forum.xda-developers.com/moto-g-2014/general/official-firmware-titan-xt1068-t3312933 or not?
And specifically the Easy installer attached in the first post at the bottom: it says: 'easy installer.zip to flash your firmware in one click. This also has an option lock or unlock bootloader and warning logo fix.'
Android 6.0
Smalband: MSM8626BP_1032.3116.99.00R EMEA_DSDS_CUST
Kernel: 3.4.42-gef77327
[email protected] #1
Wed 6 jan 12:29:54 CST 2016
System: 24.41.34.titan_retaildsds.retaildsdsall.en.03 reteu
Build: MPB24.65-34
BTW I AM A NOOB!!

LXXV* said:
Hi all,
I tried to update my Motorola Moto G 2014, but it showed status 7 error. So I contacted Motorola and they said that I rooted my phone. So I connected my phone to my PC and found supersu246.apk. I never installed this, but I guessed somehow some app rooted my phone once. I began thinking and suspected it was when I was desperate to recover my lost photos and downloaded all sorts of programs (possibly Dr. Phone).
So: I deleted supersu246.apk from my internalized SD card and factory resetted my phone. Status 7 still pops up. How do I fix this? I do not want to have a rooted phone btw.
Should I follow the instructions in this link: https://forum.xda-developers.com/moto-g-2014/general/official-firmware-titan-xt1068-t3312933 or not?
And specifically the Easy installer attached in the first post at the bottom: it says: 'easy installer.zip to flash your firmware in one click. This also has an option lock or unlock bootloader and warning logo fix.'
Android 6.0
Smalband: MSM8626BP_1032.3116.99.00R EMEA_DSDS_CUST
Kernel: 3.4.42-gef77327
[email protected] #1
Wed 6 jan 12:29:54 CST 2016
System: 24.41.34.titan_retaildsds.retaildsdsall.en.03 reteu
Build: MPB24.65-34
BTW I AM A NOOB!!
Click to expand...
Click to collapse
I can see you have already posted this in the correct forum here
https://forum.xda-developers.com/showthread.php?t=3539457
so I will close this one up and let you continue your journey there
Good Luck
Sawdoctor

Related

Moto G OTA Software Update Failure

I have a Canada version of Moto G and use it in AT&T network; so far so good. Firmware was updated a while back when Android 5.0 first came up. The Android version became 5.0.2.
Baseband version: MSM86826BP_1032.3105.93.00R TELUS_CUST
Kernel version: 3.4.42-g5bed184 [email protected] Fri Jan 23 19:56:40 CST 2015
System version: 220.21.32 falcon_umts.Telus.en.CA tkpca
Build number: LXB22_46-32
In last week, I kept receiving Software Update Notice. I accepted the update. Update was downloaded to phone and I proceeded to install the update. Update failed to install in the middle of the process. Phone reboot and back to version 5.0.2. A message showed up saying that Software Update failed to install.
There was no error message indicating what went wrong. The Software Update keep showing up few times a day.
How to fix the update issue ? If it cannot be fixed, how could I turn off the software update notification ?
Thanks,
Ching-Ho Cheng
Do u have a custom recovery or changed something in /system?
Andus1988 said:
Do u have a custom recovery or changed something in /system?
Click to expand...
Click to collapse
No change to the phone system since day 1 except to unlock bootloader. Everything is stock.
During software update, I saw the Android icon in middle of display with "star" thingy spinning in Android's "stomach". A progress bar was below the Android icon. Once the progress bar hit around 40%, Android icon changed to something else very quickly and disappeared (blank screen). Then phone rebooted.
I could not see the "error" icon at all, thing changed so fast .....
So also not rooted?
Andus1988 said:
So also not rooted?
Click to expand...
Click to collapse
Not rooted.
i too face exactly same problem
I got no response from this thread. So I reflash stock 5.1 ROM to replace 5.0.2 ROM. So far so good.

[HELP] Trying to Root Samsung Galaxy J1 mini sm-j105y

I am trying to root my Samsung Galaxy J1 Mini and am not having any luck, here are some details from the About Device in settings:
Details: Samsung Galaxy J1 Mini SM-J105Y
Model : SM-J105Y
Android v : 5.1.1
Baseband v: J105YDVU0AQI1
Kernel v : 3.10.65-12258773
[email protected] #2
Thu Nov 28 13:40:24 KST 2017
Build number : LMY47V.J105YDVS0AQK1
SE For Android Status: Enforcing
SEPF_SM-J105Y_5.1.1_0073
Tue Nov 28 13:49:58 2017
Security Software Version: ASKS v1.2 Release 161011
Android Secutiry patch level: 1 November 2017
I have OEM Unlock and USB debugging enabled in developer options
I tried rooting using Kingoroot on PC and Kingroot on the phone itself, both say my phone is unsupported
I have tried to root this phone using cf-root images gathered from firmware.mobi (link https://desktop.firmware.mobi/device:483/firmware:14717 ), this comes up with the error RECOVERY IS NOT SEANDROID ENFORCING before rebooting normally
I have also tried using TWRP, but all the tutorials show pressing vol+ & menu & power to access, but this does not work with my phone either (it takes ages even to power on then just sits at the RECOVERY IS NOT SEANDROID ENFORCING until I remove the battery & reboot)
Is there any way to root this model of J1 mini? I am at the end of my tether here
Sparky Kestrel said:
Details: Samsung Galaxy J1 Mini SM-J105Y
Model : SM-J105Y
Android v : 5.1.1
Baseband v: J105YDVU0AQI1
Kernel v : 3.10.65-12258773
[email protected]4714 #2
Tue Mar 13 11:40:40 KST 2018
Build number : LMY47V.J105YDVS0ARC1
SE For Android Status: Enforcing
SEPF_SM-J105Y_5.1.1_0073
Tue Mar 13 11:50:08 2018
Security Software Version: ASKS v1.2 Release 161011
SMR Mar-2018 Release 1
Android Secutiry patch level: 1 March 2018
Click to expand...
Click to collapse
I remember having trouble finding out how to root my J1 Mini.
My device info differs slightly from yours (marked in red in the quote) so I can't guarantee we have the exact same phone. I suspect it's because I have a later firmware version than you (and my phone is rooted!).
Search for SM-J105: ROOT + TWRP Fácil! and you will find the video that got me rooted (sorry I can't post links).
When I initially rooted, the video description contained direct links to the needed files. The current video description links to a site where you can scroll down to "ROOT SM-J105Y" and download the files; I assume they are the same as the files I used.
I can't guarantee this will work so make sure you have a way to restore your phone in case anything goes wrong.
It might be worth looking up Magisk as this seems to be the new way to root phones however I haven't tried it.
Thanks for the info, but searching for that just showed a load of Youtube videos, most of which just show the exact same methods that don't work for me, so unless you can post a direct link then I don't even know what I should be looking for really.
And I looked up info on Magisk, but that requires TWRP to be installed, which as I noted above I just can not get to work no matter what.
I must have the only Samsung phone in the known multiverse that can't be rooted.
Enter firmware.mobi (desktop.firmware.mobi) and search for your sm-j105y. Chose the exact type of your phone's security patch, build date, etc. Configure CF-Auto-Root (better don't modify anything), generate the pack, wait for it to be ready, download start automatically, unpack it, read instructions very, very carefully and root your phone.
I did it successfully with my sm-j106h.
Video:
www . youtube . com/watch?v=I31ZMO35Eoo
Files:
garagemandroid . blogspot . com/2016/12/sm-j105.html
(remove spaces from links)
I've checked the files and they are the same ones I used to root my own phone.
I have since tried out magisk and it works using TWRP from the files above.
Magisk also works and seems to be a better way of rooting but I haven't managed to get xposed working with it.
@shahinul: read my first post again, I already tried firmware.mobi, I even put a link to what I downloaded there. It doesn't work.
jatan666 said:
Video:
www . youtube . com/watch?v=I31ZMO35Eoo
Files:
garagemandroid . blogspot . com/2016/12/sm-j105.html
(remove spaces from links)
I've checked the files and they are the same ones I used to root my own phone.
I have since tried out magisk and it works using TWRP from the files above.
Magisk also works and seems to be a better way of rooting but I haven't managed
to get xposed working with it.
Click to expand...
Click to collapse
Thanks for the link jatan. After loading the video, I thought "hey this looks familiar" and sure enough, my comment was there about it not working.
Since my last post, the new firmware update (the one that you already had, with the same info you marked in red above) came up, but would not install (it came up something about not having the right recovery image or something, and to take it to a Samsung repair centre), after trying a number of different methods, I finally went into recovery and wiped the cache which did the trick and allowed the latest official firmware to install successfully, so now I am on the same firmware you documented in your first post.
So, since I am on the same firmware as you, I thought I'd try again, but now, even using the package you linked to, when trying to install the image file, this time it won't even install, instead coming up with
SECURE CHECK FAIL : (recovery)
even though I still have OEM UNLOCK and USB DEBUGGING enabled in developer options.
That's it, I completely give up now. I honestly must have the only Samsung phone that is simply incapable of being rooted by every method known to man.
I think if I wanted to continue, it would be quicker and easier for me to do what a friend suggested and go to a pawn shop and pick up a second hand S4 or something.
omg so actually impossible to root j1105y and 106h; i find since few day and nothing twrp work and no roms custom available too

I need drivers for my moto g 2013 xt1032

I recently gave this cell phone and wanted to force the update of this, so I installed an update apk and after this I jumped an update to 5.1 and all right until I realized that I did not read the SIM and the IMEI was "0 "
Then I got scared so I started to research and I got to learn a lot from the rom system, recovery, adb, fastboot. the first time I connected my cell phone was AFTER updating the firmware and simply the pc did not recognize the mobile, I did not see any notification or anything, as if nothing was connected. I need you to help me install the drivers, please be patient and I will be aware of any response. Thank you.:crying::crying:
Baseband version:
MSM8626_1032.3116.98.00a MOVSTLA_CUST
System version:
221.201.2 falcon_umts.Movistar.en.PE tefla

[Solved] Root for 8.0 / semi-bricked phone

Hi guys,
I've a brand new Nokia 3 (TA-1032) and updated it OTA with Android 8.0.0 and sec patches from July 5th. Now I'm trying to root that phone and as far as I've understood the various thread, I've to downgrade to Android 7.0. However, it seems I mixed up some guides...
When starting my phone, the following message is displayed: "Orange state, can't be trusted". After a couple of seconds the phone boots normally.
Any ideas how I can root my phone? I'm damn sure the solution is somewhere out there on xda dev, but a wealth of information creates a poverty of attention.... meaning I've no idea where to start.
Thanks and enjoy the weekend
Youser
===
Update: I could successfully go back to Android 7 with OST and root my device. Problem is solved.

Tesco Hudl 2 in 2021

Hi.
I have a Hudl 2 that I managed to defeat the Wi-Fi issue at first boot, however I wanted to flash a rooted stock ROM and all the links are from way back and the images links are all expired and go nowhere.
I did manage to get some images, but not for my build number, which must have been the latest before Tesco pulled the plug on the support servers.
Does anyone have images for my build number: 20151102.170607 please?
All I want to do is remove the Tesco bundled bloatwear.
Kind regards.
To remove bloatware it's NOT needed to flash another ROM but to root tablet's actual Android KitKat.
jwoegerbauer said:
To remove bloatware it's NOT needed to flash another ROM but to root tablet's actual Android KitKat.
Click to expand...
Click to collapse
Hi thanks for the reply.
I've looked everywhere for a method to root it and all links are outdated or dead.
Basically, rooting just means to push a binary (su) and a helper app ( SuperUser/SuperUser or SuperSU ) to Android's system partition.
KingoRoot may do this job within 2 minutes.
jwoegerbauer said:
Basically, rooting just means to push a binary (su) and a helper app ( SuperUser/SuperUser or SuperSU ) to Android's system partition.
KingoRoot may do this job within 2 minutes.
Click to expand...
Click to collapse
mediaseller said:
Hi thanks.
I tried that and a few others but the Hudl firmware is blocking it.
Click to expand...
Click to collapse
lollipop isn't rootable on the hudl 2 afaik
Hi,
In case anyone is looking for clear instructions on how to overcome the problem after a factory reset of the Tesco Hudl 1 & 2 you will find them here (works for Hudl 2 as well). Use a date between 27 June 2019 and 26 June 2020 :
HUDL bricked after factory reset and how to fix it - Hey Munky!
I did a factory reset on my HUDL and bricked it. Here's a quick step-by-step guide on how to unbrick it after a factory reset.
www.heymunky.co.uk
Or the same with pictures but remember to use a date between 27 June 2019 and 26 June 2020 :
Rob's stuff - Hudl - Fix
Update 23 May 2023: This mechanism for recovery of a factory reset Hudl 1 no longer works. Due to the Tesco server at https://device.tesco.mobile.com/ no longer responding correctly to requests this technique no longer works and will fail after Step 18. As far as I know my Custom ROM is now the
rob.themayfamily.me.uk
(If this date solution ever fails then another option is to create a new user in the settings menu and reboot into it.)
Post if it works for you

Categories

Resources