Hey guys, maybe someone can help here:
My G-Slate randomly decided to power off after setting a wallpaper and when I pushed the reset button on the device it now only comes back on to a black screen with the unlock circle on the screen - but the screen doesn't let me select anything.
The only option I can think of is to factory reset the device/wipe it - but the only way I know to do this is via the system menus. Is there a way to wipe the device with the buttons? Fastboot? Anything?
Is it rootable? Do you have recovery? I have heard that there were problems with rooting I don't know this device but there should be reset button or something like that under sim card.
I had ADB interfacing with it, not rooted though. Is there a command I can use to wipe the data via ADB?
Try:
Code:
adb shell
format SYSTEM
format DATA
format CACHE
But i'm afraid that you need root and type su after adb shell
Right now the device is unrootable and unlockable. I've been trying for the past week to do both with little success. There are multiple threads already (although still no forum yet) on XDA about trying to develop the G-Slate. If you want to view them all in one place, then you can check out this bit.ly bundle I made. I updated it today (to include your thread). Other than that, sorry there's not much I can do to help. I suggest that, if all you were really trying to do was change out the wallpaper and the device bricked itself, you should take it back to the store and see if they can fix it or swap it out with a new one.
Here's the LINK to the bundle.
Thanks for the help guys, looks like I'll be sending it back to get a new one - oh well
xda
Xda-help us wiht the g-slate
yes it can be rooted
Rooting is possible and as rooting new devices goes its not that hard if runing Ubuntu
Related
The Motorola i1 is the newest android fone out for SouthernLinc and soon Boosst Mobile........yes thats right Boost Mobile. Now has anyone got there hands on one yet and if so have you rooted it? Cuz I would love to know how to root it cuz I will soon have one when it comes to Boost Mobile. Well thanx for reading.
i got mine to and would love to root it and have a new rom any roms in development ? for the moto i1 ?
i was wondering the same thing im getting one today but my friend has one and there is no debbugging mode in settings i dont know if this will be a issue or if im loking in the wrong place iv have several android phones and rooted them all, so i didint think it would be so tricky to find debugging
UPDATE
i found debugging mode its in the usb menu....i guess im just curious about root...
I just got mine today. The USB drivers from motorola work, so we can play around in ADB. I hope for an easy root, but I have a feeling the i1 shares alot of hardware with the backflip and or the cliq XT. I don't think either of those have root yet, so I don't know what our chances will be.
taylorn8369 said:
I just got mine today. The USB drivers from motorola work, so we can play around in ADB. I hope for an easy root, but I have a feeling the i1 shares alot of hardware with the backflip and or the cliq XT. I don't think either of those have root yet, so I don't know what our chances will be.
Click to expand...
Click to collapse
i was thinking the same thing...
Has anyone figured out how to get into recovery or fastboot yet? I have tried every button combination i think and have not yet found it.
I did some how get into a diagnostic type app on boot (tested screen colors and touch calibratsion) but I have been unable to replicate that.
I am pretty sure we are SOL when it comes to root. I tried to run flash_image recovery from adb shell to push a new recovery img to the phone and it dies saying can't find recovery partition.
Unless it is possible to mount the system and writable with a custom boot.img I don't see how this could be done.
I 2 just bought the i1 and can't wait to push a new flash. I hope we are not SOL and that some1 more experienced then I will show us the light and find a way.
I am confident I could get us a root, I just need to find a way into recovery. Or fastboot for that matter. In your free time guys, reboot while mashing different button configs to see if you can find it.
I tried to push a custom recovery but adb said recovery partition not found. So either there isn't one (I hope this is untrue) or it has a different name.
Rooting !!!
Hold the green send key and the center key on boot up you get a screen that looks like it would be fastboot but the device doest show in fastboot devices from the SDK.
Is the Moto i1 going to get its own forums on xda? Who decides/creates the forums?
Is there anyone with experience making android apps?
I have found that /data/local is read/writable so I put the su bin in that DIR and installed superuser whitelist. If in ADB shell I run /data/local/su the superuser app asks for permission but fails because it is looking for su in /system/bin.
I am trying to compile the superuser app from source to have it look in /root/local, but the build is failing. If we can get that then we should be able to remount mtdblock7 to /system as read/writable and put su where it belongs.
rubensbasket said:
Hold the green send key and the center key on boot up you get a screen that looks like it would be fastboot but the device doest show in fastboot devices from the SDK.
Click to expand...
Click to collapse
Thank you for copy/pasting my post from another thread.... With that possible fastboot though, I know fastboot has had some issues with drivers in window7 64. So can someone try that on a XP machine and see if it shows in fastboot devices?
I am running x64 windows 7 also so I guess my button mashing has been in vein... looks like we are on the right track though...
navyguy said:
Is the Moto i1 going to get its own forums on xda? Who decides/creates the forums?
Click to expand...
Click to collapse
I am guessing we won't get a forum for the Moto i1 Until it get's rooted, as I don't see people being to interested/developing/hacking for it until then.
hope u guys get ur forum . i luv boost!
I don't know how helpful this is but messing around I found IDEN phonebook manager from Motorola. Installed it and changed USB communication to Modem and was able to see the phone reboot and read sim data. Check it out and let me know what you think.
here is the link to their site to get and test it out.
http://servicemyphone.motorola.com/iden/support/software/organizer_upd.jsp
Ok, so as the previous post states I was able to access my sim card from the program which had me wondering if all IDEN phones from motorola had a special way of flashing so I looked around and found this link:
http://servicemyphone.motorola.com/iden/support/software/html/firmware_utility.html
I found a firmware update for my old boost mobile i776 and downloaded upon running the program I noticed it launched a program called Iden upgrade utility. I am now thinking that is going to be our ticket into the phone.
Again let me know what you think.
how to do the hard reset this phone i1 (with password)?
thanks
This was all I could find. If you get the external figured out let us know...
Factory Data Reset is a tool used to remove everything that was imported, added or installed on the device. Keep in mind, when using this feature; everything is deleted. Nothing stored on the MicroSD will be affected.
To reset your phone to factory settings and erase all the data on your phone,
1. Touch the app tab, in the home screen to open the app menu.
2. Touch Settings
3. Touch SD card & phone storage
4. Touch Master Clear
Warning: All data on your phone will be deleted.
Contact your Service provider/Carrier or Motorola Customer Service Agent for help with external Hard Reset / Master Clear button sequence for i1.
Click to expand...
Click to collapse
https://motorola-global-portal.cust...2560/~/i1---factory-data-reset-(master-clear)
Laph9979 said:
This was all I could find. If you get the external figured out let us know...
https://motorola-global-portal.cust...2560/~/i1---factory-data-reset-(master-clear)
Click to expand...
Click to collapse
the password for the master reset is 000000
EDIT:
SOLVED! Thanks for the support!
In the end I decided to flash back to stock factory image from Google downloaded at the following link (https://developers.google.com/android/nexus/images) and installed using the very easy method of inputting a single command. Exactly the kind of solution I needed after pulling hair out.
Hopefully this post is of assistance to others in need.
In the end I used the Chain Fire auto root. Worked a treat - so now running stock Nexus 5 image with root, just the way I wanted it.
http://forum.xda-developers.com/showthread.php?t=2507211
Original question:
Need help - I think I bricked my Nexus 5 (was running KOT49H stock ROM). And would really appreciate some sage advice now to get me out of trouble.
Not my first root, custom ROM experience - have done on 3 previous devices, but first Nexus 5 and first stuff up for me. Not a complete noob, but please be clear in your advice. Thanks.
I "followed" this guide (http://www.teamandroid.com/2013/12/10/root-nexus-5-android-442-kot49h-kitkat-install-cwm-recovery/2/)
However, at Step 13-15 I was unable to mount an SD card (Nexus 5 is all internal), and I then opted to sideload the UPDATE-SuperSU-v1.80.zip file using "adb sideload". It is now stuck in a boot animation loop (say 10mins of waiting?). So what has gone wrong here?
I also guides from the same site to unlock bootloader and install CWM - that all worked.
I am able to get back to the bootloader and can get into CWM still, just cannot boot.
Not sure if my phone is charging, but I believe I still have some juice so looking for a solution. Have I somehow replaced all of the ROM software with just the SuperSU file? Is that possible? This is my first outing with the Nexus 5 but I have rooted and custom ROMed many phones before, but this is my first with no external SD card.
I could not mount any / partition from what I could tell.... such as /data (not sure if this helps your advice?)
In another thread, someone mentioned a catch all solution might be this : http://forum.xda-developers.com/showthread.php?t=2513701
As I said, I can get into the bootloader and CWM and phone is still recognised by PC.
If I am not mistaken, this would basically sideload everything back to factory?
Would this matter if my phone was at KOT49H before everything went wrong, or will that just come down via OTA later anyway (I was getting OTA updates just fine).
I think I should still have about 50% battery charge, but I don't know if it is charging (nothing shows) and the battery is completely internal on these.
Your help = much appreciated! Please - its Christmas afterall...
Cheers Adriaan
Sorry to hear about your troubles! I know how frustrating it can be when you softbrick for no apparent reason. However, the fact the phone still boots into recovery and all that means that there shouldn't be anything we can't recover from. The link you provided would work. You might also check out one of the toolkits that helps automate most of the stuff you are looking for, like this: http://forum.xda-developers.com/showthread.php?t=2525026 .
That being said, me personally, I would attempt some fixes via CWM first (though I much prefer TWRP). It could be something as simple as wiping the caches and fixing permissions. Possibly a factory reset could help, though I suspect probably not at this stage. Are you comfortable with manual ADB and fastboot commands? I would download a rom zip and adb push it to /sdcard, perform resets and reboot. Should be fine at that point and rooted to boot. If you're all about the stock root experience (never really understood that, but to each their own ) then try this: http://forum.xda-developers.com/showthread.php?t=2557523
Once you would download that, and are able to get ADB access in recovery (should work if you have the right drivers and all - if not, would recommend switching to TWRP) then you would use this command:
adb push rom.zip /sdcard/ - where rom.zip is the name of whatever that one downloads as...
Then wipe factory reset and caches (system too if you want to be thorough) then install the rom and reboot. Should be back to where you want.
If you would like some more 1 on 1 type help, feel free to hit me up on Hangouts with this username. Good luck!
You can flash the factory images directly from Google which should get you back up and running again.
Download and extract them.
Boot your phone to the bootloader and plug into your PC.
Run the flashall.bat
Note that this will fully wipe your phone
Sent from my Nexus 4 using xda app-developers app
First reboot recovery and factory reset the phone. If it boots your good. If not install the google factory image.
Everyone, thank you for your input. My phone is back alive and well.
In the end, I decided to flash all back to a stock factory image from Google. Only had 1% battery left by the time it booted into the fresh flash. Figured this was the best place to recommence my efforts to gain root again, and hopefully this time with a better outcome.
I will probably give the chain fire auto method a shot this time, after a bit more research.
Thank you again for your help and for the very quick responses. Great community.
In the end I used the Chain Fire auto root. Worked a treat - so now running stock Nexus 5 image with root, just the way I wanted it.
http://forum.xda-developers.com/showthread.php?t=2507211
HI, I love learning about my phone and wanted to gain root access and have clearly made a HUGE meal of it. I desperately would love some one to explain if I can save be beloved Nexus 5.
When turned on it loads to the 4 colours and just wont go past that stage. I can access recovery mode but it wont mount on my Mac so i can access the SD card.
I'd just be happy to reset my phone now to factory can someone please help me do that!!!!
Thank you VERY much to anyone that could explain to me how....
Recovery doesn't mount storage. Google "adb on mac" then learn to configure adb.
Sent from my Nexus 5 using Tapatalk
It is hard to know the best way to fix your issue, because it isn't really clear what you have done and when the boot looping started. I think that what you need to do is to reflash the factory firmware and that will require you to set up adb and fastboot correctly (as mentioned in the post above). This tutorial and this begginner's guide are probably a good places to start. If you don't understand something, search that thread and look in the "stickies" in Nexus 5 General...if you are still confused go a head and ask in the most appropriate guide thread or in the Nexus 5 Q&A thread.
i highly recommend WUG's nexus root toolkit.
this have saved my ass many times.
http://forum.xda-developers.com/goo...olkit-wugs-nexus-root-toolkit-v1-8-0-t2517778
but you must sort out your ADB problems first.
many ppl have run this on Parallels or WINE, or borrow a PC from somewhere to restore to stock.
Never use toolkits! They tend to do more damage than good.
@thegrapher : Go to stock recovery and do a factory reset and see whether the phone boots or not.. If it doesn't, do what rootSU suggested and setup adb/fastboot on mac and flash the stock factory images!
Thanks heaps guys....really appreciated all the replies. .
Firstly, thanks for the advice i will avoid toolkits in the future.
However...i did manage to sort it out i think. All seems ok so i hope so. Yeah it was loading the google screen showing the padlock on the bottom but the four colours just bounced on and on and nothing... so i couldnt mount it. I could go to recovery (a teamwin logo appeared so i guess that was installed). but in all the options it had nothing on the sd card or didnt appear to after going into every option and clicking mount or sideload. tried to reset it and finally i formatted decrypted data under that option and boom all good. even got it unlocked and working so i guess i found my way eventually.
Would like to know what i did so i can learn but i feel i went about it in such a way i didnt really learn anything. just happy its sorted i guess. and sort proud it is unlocked now i can move that annoying volume bar to the top where it should be!!! lol
hope some of that made sense or can explain what i did. cheers
thegrapher said:
Thanks heaps guys....really appreciated all the replies. .
Firstly, thanks for the advice i will avoid toolkits in the future.
However...i did manage to sort it out i think. All seems ok so i hope so. Yeah it was loading the google screen showing the padlock on the bottom but the four colours just bounced on and on and nothing... so i couldnt mount it. I could go to recovery (a teamwin logo appeared so i guess that was installed). but in all the options it had nothing on the sd card or didnt appear to after going into every option and clicking mount or sideload. tried to reset it and finally i formatted decrypted data under that option and boom all good. even got it unlocked and working so i guess i found my way eventually.
Would like to know what i did so i can learn but i feel i went about it in such a way i didnt really learn anything. just happy its sorted i guess. and sort proud it is unlocked now i can move that annoying volume bar to the top where it should be!!! lol
hope some of that made sense or can explain what i did. cheers
Click to expand...
Click to collapse
Cheers mate!! enjoy N5. boot it manually if required only
I'm sure it's been beaten like a dead horse... Yes I have searched all over XDA and other resources. It seems every time I think I find something... I'm one setting short or one model away from what would work.
Been working on this way too long and now I ask for your help.
I have a client who lost her daughter. (She drown). She has her phone (S3 I535 verizon) but no idea what the lock pin would be and has tried a couple but none work. Unfortunately she's on attempt 8/10 so two more tries and the phone factory resets and all is lost.
She really wants to recover her daughter's pictures and if possible remove the screen lock without losing data (either works for her if it can be done).
I've tried everything I can find.
While she has her gmail and password, when we logged in device manager listed no active devices. (was able to recover some pictures from a backup, but it appears gmail didn't back up more than a couple from a couple years ago.)
Logged into samsung to remote unlock it, but again, no devices on account.
ADB is a no-go because USB debugging is OFF
Tried to put TWRP on it but odin failed
(Found a thread here that seems to be quality but can't load the program in stock recovery and cant get CWM or TWRP on it without debugging.)
Any ideas?
I do not know the android version, but I suspect it is the newest. I used my old S3 to replicate it so I could try these things without damaging her phone and losing the data, and it's running 4.4.2
If you couldn't flash a recovery using Odin then you're probably right about it being on one of the newer versions(your phone), the boot loader got locked up tight and the only recovery we have available is Safestrap. This is a tough one. I'm no expert by far, take what I'm saying with a grain of salt and do your own researching before taking any action after reading this! I see two ways of recovering some or all data if the bootloader is locked(and the device storage isn't encrypted)
1. If you don't have equipment to directly read/write to the internal storage then point her somewhere that specializes in data recovery on smart phones.
2. Factory reset the device, try to recover "deleted" data.
If the bootloader wasn't/isn't locked down then you could probably flash a rom that didn't have the lock screen pin/pattern ect implemented. I don't have the i535 but I know that the prepaid version checks the system partition when flashing via Odin so this probably wouldn't work if it's locked but I can't confirm wether or not this is checked on the i535
Can you enter the stock recovery on the daughters phone just to verify if its updated or not. Should be a string near the top. If it ends with ne1 its on 4.4.2 and I don't recall the one for 4.3. If you're unable to enter the recovery because you have to enter the pin before there's an actual lock screen(with the clock, status bar, wallpaper ect) then it's likely encrypted and there's nothing that you can do about that.
OpenSourcererSweg said:
If you couldn't flash a recovery using Odin then you're probably right about it being on one of the newer versions(your phone), the boot loader got locked up tight and the only recovery we have available is Safestrap. This is a tough one. I'm no expert by far, take what I'm saying with a grain of salt and do your own researching before taking any action after reading this! I see two ways of recovering some or all data if the bootloader is locked(and the device storage isn't encrypted)
1. If you don't have equipment to directly read/write to the internal storage then point her somewhere that specializes in data recovery on smart phones.
2. Factory reset the device, try to recover "deleted" data.
If the bootloader wasn't/isn't locked down then you could probably flash a rom that didn't have the lock screen pin/pattern ect implemented. I don't have the i535 but I know that the prepaid version checks the system partition when flashing via Odin so this probably wouldn't work if it's locked but I can't confirm wether or not this is checked on the i535
Can you enter the stock recovery on the daughters phone just to verify if its updated or not. Should be a string near the top. If it ends with ne1 its on 4.4.2 and I don't recall the one for 4.3. If you're unable to enter the recovery because you have to enter the pin before there's an actual lock screen(with the clock, status bar, wallpaper ect) then it's likely encrypted and there's nothing that you can do about that.
Click to expand...
Click to collapse
I can enter recovery mode and I do believe it is 4.4.2.
because of the delicate nature of her phone (being her passed on daughter's and she used 9 of 10 attempts to guess her pin) I pulled my S3 out of the drawer (coincidentally I stopped using it about 2 weeks after she passed) and everything is identical down to the recovery string at the top. I know it's running the same software and I have all kinds of old pictures and texts on it like she would have and I am logged into gmail on it like she is. I locked the screen on MINE and I know the PIN on MINE. I also saved a backup of my stuff so I'm using my phone as the tester since I was able to put in in the identical situation
I have room to play because of that. Once I have success on mine, I'll try what worked on mine on hers.
So far I've tried...
play.google unlock... While I have now been able to get her device to appear on device manager on google's site, they changed it so that when I remote lock it the screen lock pin does NOT change.
I called Google, Samsung, and VERIZON. None have the ability to change or remove lock screen pin.
I tried ADB, but it doesn't detect any devices when I ADB shell or ADB device.
USB DEBUGGING IS OFF (or we wouldn't be having this convo)
It has stock recovery and not CWM or TWRP (again if I could get one of those on there, we wouldn't be having this convo) (tried ODIN flashing TWRP on, but fails)
---------------------------
Every direction I head I hit a brick wall.
I've never heard of being able to recover data from internal SDcard after reset. Didn't think that was possible.
FYI. recovery mode string is...
ANDROID system recovery <3e>
KOT49H.I535VRUDNE1
Wking46 said:
I can enter recovery mode and I do believe it is 4.4.2.
because of the delicate nature of her phone (being her passed on daughter's and she used 9 of 10 attempts to guess her pin) I pulled my S3 out of the drawer (coincidentally I stopped using it about 2 weeks after she passed) and everything is identical down to the recovery string at the top. I know it's running the same software and I have all kinds of old pictures and texts on it like she would have and I am logged into gmail on it like she is. I locked the screen on MINE and I know the PIN on MINE. I also saved a backup of my stuff so I'm using my phone as the tester since I was able to put in in the identical situation
I have room to play because of that. Once I have success on mine, I'll try what worked on mine on hers.
So far I've tried...
play.google unlock... While I have now been able to get her device to appear on device manager on google's site, they changed it so that when I remote lock it the screen lock pin does NOT change.
I called Google, Samsung, and VERIZON. None have the ability to change or remove lock screen pin.
I tried ADB, but it doesn't detect any devices when I ADB shell or ADB device.
USB DEBUGGING IS OFF (or we wouldn't be having this convo)
It has stock recovery and not CWM or TWRP (again if I could get one of those on there, we wouldn't be having this convo) (tried ODIN flashing TWRP on, but fails)
---------------------------
Every direction I head I hit a brick wall.
I've never heard of being able to recover data from internal SDcard after reset. Didn't think that was possible.
Click to expand...
Click to collapse
With HDDs I know it's possible as I have done it before. The only issue is not overwriting the data when reinstalling a operating system ect. Flash is abit dififfrent but still doesnt overwrite deleted data as soon as its deleted. If you're willing to try it on your gs3 first then go for it. Since the data is very important, I would have her take it to someone who specializes in data recovery instead of trying to wipe it and get the data off it just in case.
Are you able to remotely install applications though the Google Play site or by other means? Might be able to get a shell from one of the ssh server apps if they run the server on startup. If you can get a shell you should be able to work from there.
OpenSourcererSweg said:
With HDDs I know it's possible as I have done it before. The only issue is not overwriting the data when reinstalling a operating system ect. Flash is abit dififfrent but still doesnt overwrite deleted data as soon as its deleted. If you're willing to try it on your gs3 first then go for it. Since the data is very important, I would have her take it to someone who specializes in data recovery instead of trying to wipe it and get the data off it just in case.
Are you able to remotely install applications though the Google Play site or by other means? Might be able to get a shell from one of the ssh server apps if they run the server on startup. If you can get a shell you should be able to work from there.
Click to expand...
Click to collapse
I can remotely install apps via google play site. If I could find a shell that works on startup... please let me know what that does for me?
Wking46 said:
I can remotely install apps via google play site. If I could find a shell that works on startup... please let me know what that does for me?
Click to expand...
Click to collapse
SSH access may let you transfer some files on the device to another machine. (Assuming that it will connect to known wifi networks while locked)
OpenSourcererSweg said:
SSH access may let you transfer some files on the device to another machine. (Assuming that it will connect to known wifi networks while locked)
Click to expand...
Click to collapse
No such luck. Looks like all of them would need me to log in to set them up, which defeats the purpose.
I may have to wait and see if tech changes over time and keep trying until it does.
Wking46 said:
No such luck. Looks like all of them would need me to log in to set them up, which defeats the purpose.
I may have to wait and see if tech changes over time and keep trying until it does.
Click to expand...
Click to collapse
Take a look at this, https://www.nowsecure.com/blog/2015/06/16/remote-code-execution-as-system-user-on-samsung-phones/ may be able to remove the pin. Sorry if discussion about this isn't allowed or frowned upon. Seems like a pain and it may not work for the s3
OpenSourcererSweg said:
Take a look at this, https://www.nowsecure.com/blog/2015/06/16/remote-code-execution-as-system-user-on-samsung-phones/ may be able to remove the pin. Sorry if discussion about this isn't allowed or frowned upon. Seems like a pain and it may not work for the s3
Click to expand...
Click to collapse
Doesn't effect S3 vzw. only S4 and up
Wking46 said:
Doesn't effect S3 vzw. only S4 and up
Click to expand...
Click to collapse
Ah I read "swift" as Swype and my Prepaid Verizon GS3 came with Swype preinstalled.
I have an idea, perhaps try the Verizon repair software "repair" the device to back up data while in Odin mode? I don't recall if it will require a password or anything.I don't believe it required USB debugging to be enabled, don't know if it works while in Odin mode. I don't know if the backups are encrypted or not. You can try using sandboxie to see where it keeps the backed up data. I don't know if it will backup data while you're in Odin mode though. Worth trying I suppose. Don't have time try my The self or I would. Sorry for the rushed message, I'll be home in about an hour though.
rooted bricked boost mobile moto G. 4.4.4. i messed up my phone while editing "build.prob" with es root file i believe and when i was done editing i clicked on the folder looking icon on the top right corner which i thought was enter/save but itwas something else that rearranged the letters after it booted i only got bootloader unlocked warning screen and a plain black screen after and thats it however i can also get to the the fastboot menu. so any way can i get my phone back with maybe just using adb and fastboot. i just rooted my phone like a week ago so never got to play around with it so i have alot to catch up with on terms and research dont worry i'll look up what you tell me to do rather than keep on asking how how and how. well guys hope you can help me thank you.
XDA Visitor said:
rooted bricked boost mobile moto G. 4.4.4. i messed up my phone while editing "build.prob" with es root file i believe and when i was done editing i clicked on the folder looking icon on the top right corner which i thought was enter/save but itwas something else that rearranged the letters after it booted i only got bootloader unlocked warning screen and a plain black screen after and thats it however i can also get to the the fastboot menu. so any way can i get my phone back with maybe just using adb and fastboot. i just rooted my phone like a week ago so never got to play around with it so i have alot to catch up with on terms and research dont worry i'll look up what you tell me to do rather than keep on asking how how and how. well guys hope you can help me thank you.
Click to expand...
Click to collapse
Hello, and thank you for using XDA Assist!
Quite possibly my easiest problem of the night.
Your bootloader is unlocked. So....flash custom recovery. One that can do adb as well (unless you Moto G also has an SD card slot, but if we are talking about the original 2013 model, then one won't be there).
Then, reboot into recovery. Make a backup. Pull the backup files to your PC (either by adb or MicroSD, if available). Extract the system backup file (is a tarball) in a Linux filesystem. Fix up your build.prop mistakes. Tar system back up, and bundle the backup as a second set to push back to your device. Restore that backup (need only be system partition). Profit.
Any further questions, can ask in the following thread (assuming you have the 2013/1st gen non-LTE version - otherwise reply here with variant details for further instructions):
> Moto G > Moto G Q&A, Help & Troubleshooting > [RC-FAQ] >> Frequently Asked Questions for Motorola Moto G [Updated : 2015/09/23]
Please note, you will need to register for an account in order to post there.
Hope this helps, and good luck!
joel.maxuel said:
Hello, and thank you for using XDA Assist!
Quite possibly my easiest problem of the night.
Your bootloader is unlocked. So....flash custom recovery. One that can do adb as well (unless you Moto G also has an SD card slot, but if we are talking about the original 2013 model, then one won't be there).
Then, reboot into recovery. Make a backup. Pull the backup files to your PC (either by adb or MicroSD, if available). Extract the system backup file (is a tarball) in a Linux filesystem. Fix up your build.prop mistakes. Tar system back up, and bundle the backup as a second set to push back to your device. Restore that backup (need only be system partition). Profit.
Any further questions, can ask in the following thread (assuming you have the 2013/1st gen non-LTE version - otherwise reply here with variant details for further instructions):
> Moto G > Moto G Q&A, Help & Troubleshooting > [RC-FAQ] >> Frequently Asked Questions for Motorola Moto G [Updated : 2015/09/23]
Please note, you will need to register for an account in order to post there.
Hope this helps, and good luck!
Click to expand...
Click to collapse
im sorry man i shouldve updated and listed that i have usb debugging off -_- i was trying a stock fastboot method but ended up putting 4.3 or 4.4 instead without realizing so now its in a bootlooop still access to stock recovery tho. and so i was going to fastboot the 4.4.4 download from file factory but its down due to maintenance. so on to motorolla website i go and what ya know "cant unarchive". any ideas man? its a 45 dollar phone couldve easily replace it but something about leaving it as paper weight that will bug me forever haha plus lets not forget the satisfaction of solving the problem haha. and i have yet to read up on custom recovery which i will do if you believe it'll work. thanks for your reply man
jasj0410 said:
im sorry man i shouldve updated and listed that i have usb debugging off -_- i was trying a stock fastboot method but ended up putting 4.3 or 4.4 instead without realizing so now its in a bootlooop still access to stock recovery tho. and so i was going to fastboot the 4.4.4 download from file factory but its down due to maintenance. so on to motorolla website i go and what ya know "cant unarchive". any ideas man? its a 45 dollar phone couldve easily replace it but something about leaving it as paper weight that will bug me forever haha plus lets not forget the satisfaction of solving the problem haha. and i have yet to read up on custom recovery which i will do if you believe it'll work. thanks for your reply man
Click to expand...
Click to collapse
No problem.
USB debugging being off is only a consequence if planning to ADB in from system. Recovery has it's own rules.
Not sure about the "cannot unarchive" message, but if you can get the stock ROM, that's a viable option as well.
joel.maxuel said:
No problem.
USB debugging being off is only a consequence if planning to ADB in from system. Recovery has it's own rules.
Not sure about the "cannot unarchive" message, but if you can get the stock ROM, that's a viable option as well.
Click to expand...
Click to collapse
no luck with installing Stock Rom thru Custom Recovery im using twrp. suddenly my terminal wont let me fastboot the zip file because of
"unknown partition 'Rom.zip'
error: cannont determine image filename for 'Rom.zip'
and if it helps i tried using stock recovery with this method (installed. 4.4):
androidforumsDOTcom/threads/cdma-boostmobile-only-guide-on-returning-to-stocDOT.826108/
and adb works when im on custom recovery if that helps out
and i never got to do the back up build.prop method because i had already done the first stock recovery method which i feel mightve messed things up. thanks for your replies man it really means alot
jasj0410 said:
no luck with installing Stock Rom thru Custom Recovery im using twrp. suddenly my terminal wont let me fastboot the zip file because of
"unknown partition 'Rom.zip'
error: cannont determine image filename for 'Rom.zip'
and if it helps i tried using stock recovery with this method (installed. 4.4):
androidforumsDOTcom/threads/cdma-boostmobile-only-guide-on-returning-to-stocDOT.826108/
and adb works when im on custom recovery if that helps out
and i never got to do the back up build.prop method because i had already done the first stock recovery method which i feel mightve messed things up. thanks for your replies man it really means alot
Click to expand...
Click to collapse
Hello,
Fastboot is unable to flash zips unfortunately. That's the recoveries job.
If you can find fastboot images of stock, you can flash back that way.
Especially at this point, I would urge you to take advantage of the help thread I mentioned earlier. They know more about your device (particularly what's available and what not) they I would.
Hope this helps!