Dont know what i did :( - Motorola Atrix HD

not clue what i did wrong to be honest. im trying to flash back to stock with rsd and i keep getting sticky bit fastboot. any help ?

What were you trying to do?
Sent from my PACMAN MATRIX HD MAXX

i tried to flash back to stock, and i get this ive never had it before. tried using rsd and i put in stock firmware i try flashing and i get that.

http://forum.xda-developers.com/showthread.php?t=2312662
Sent from my PACMAN MATRIX HD MAXX

tried that didnt do anything...... i dunno if its because i dont have stock motorola cables.

emmabellachristian said:
tried that didnt do anything...... i dunno if its because i dont have stock motorola cables.
Click to expand...
Click to collapse
That shouldn't matter, I've done the fastboot commands with both Moto and Samsung usb cables. I'm gonna guess that you having the usual permission/wrong fastboot problem. I can tell you first hand that Linux, Root, and SnapDragon Fasboots have never once failed me for any flash command (that's supported by our phone). I've never done adb from Windows, but from what I understand ya gotta right click the snap-fastboot.exe and enable Administrator Permissions for it.
To make life much easier for you, download the correct fastboot from Batakang and overwrite any fastboot.exe on your system with it if this is your only android phone that uses fastboot commands and do the permissions crap for all of them (how many can there actually be ).
If its not the permission/fastboot crap then reinstall any Motorola or Android driver you have. For some reason for some people they just quit working properly and need a reinstall...that's just proper Windows maintenance .
/I've always believed that Windows wasn't named after its windowed desktop, but after actual windows because, like real windows, if it breaks its just easier to install a new one versus fixing the old...I mean, yeah you can get a crack or a star filled, but ya gotta be covered by insurance (pc warranty) or cough up the $$$...And, just like glass windows, if you don't know how ya gotta pay to install the new one.
//Kids, learn how to use tools, some basic home maintenance skills, and enough auto mechanic skills to at least do a complete tune up, a brake job, and install an alternator\bolt on engine parts.

so i feel like a tard was battery close to dead problem :-x just outta curiousity when flashing i get to step 17 flash "system img" then phone returned fail phone connected

take it no one has a clue ?

emmabellachristian said:
take it no one has a clue ?
Click to expand...
Click to collapse
I don't, not for Windows anyways. I've had that error, but it was because I typed fastboot flash instead of snap-fastboot flash...what I rename them to so they don't conflict with the Android SDK from the AUR.
I didn't realize you had replied....but yeah, I've had my low battery flash scare. After 2 days the Bravo would not take a charge, wall, pc, car, and I was desperate. For me I ended up taping speaker wire to some razr (flip phone) batteries and wiring them to the connection prongs on my Bravo, put actual Bravo battery in and flashed the sbf... it worked
If possible, do this all on Linux...doesn't really matter the distro or version. You'll hardly have any errors or issues with our fastboot as root on Linux.
While it won't help you now, I've been looking into Manjaro's system builder tool to make a Manjaro system with adb and fastboot setup, various programs I use...basically the crap I use on a daily basis to make an installer for myself so I can install my custom system wherever I need it. It would also be worth sharing cause it would be an easy way for a new Linux user to get started and not have to follow multiple mile long guides on xda just to install a bunch of crap to get started.

Related

n1 issues

hi everyone, im new to these forums. i want to love my n1, but cant. my service is horrible here in miami florida. so bad that tmobile keeps giving me free months of service instead of a solution.
i was told about holding the phone a certain way, but its so unnatural. but i understand that a few firmware updates helped out the signal issues. me and my sons nexus ones are fluctuating 20-50 dB's at a time.
so i try to root using the cyanogen wiki's instructions. the second i type in adb devices into my windows 7 cmd window, i get the following. "adb is not recognized as an internal or external command"
i repeated the steps in the wiki and have no idea what i am doing wrong.
can anyone assist please?
Mod, if i posted in the wrong section i am sorry; feel free to move thread.
thanks all!
Here bro, this might help... "How to set up adb"
http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
Did you run the adb command from the sdk directory?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
You need to download the SDK and use the adb from the SDK directory....
MaximReapage said:
Did you run the adb command from the sdk directory?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
No I used the windows cmd window. I saw the android cmd window but it wouldn't let me type in it. Was I supposed to type in the android window?
Before you go and unlock the phone and install cyanogen, are you sure you want to go down that road? I don't think there are any reception improvements in any of the custom ROMs, so if that's what you are hoping for you might be disappointed.
You may lose your warranty if you do it, and you are going to permanently lose the over-the-air upgrade system that Google uses to push upgrades out with.
sheek360 said:
No I used the windows cmd window. I saw the android cmd window but it wouldn't let me type in it. Was I supposed to type in the android window?
Click to expand...
Click to collapse
You need to read up a lot more on how your computer works, and directory structures, and cmd windows and all that. If you are already confused you could just end up breaking your phone. First thing is to install the SDK. Get that done, then read some more, etc. Do it slowly.
Clarkster said:
You need to read up a lot more on how your computer works, and directory structures, and cmd windows and all that. If you are already confused you could just end up breaking your phone. First thing is to install the SDK. Get that done, then read some more, etc. Do it slowly.
Click to expand...
Click to collapse
Thanks for the heads up. The sdk is definately installed.
I heard that the other radios perform better. I need a miracle, I drop 60% of my calls according to tmo. So does my sons n1's. My daughters cliq and wife's bold9700 are always on 3g
What Baseband version do you have installed on your phone? It's under Settings -> About phone.
You should be running the newest radio firmware already I would think.
PrawnPoBoy said:
What Baseband version do you have installed on your phone? It's under Settings -> About phone.
You should be running the newest radio firmware already I would think.
Click to expand...
Click to collapse
I don't know it off the top of my head. But its definately current.
Well if you want to check it out, I believe "32.26.00.24U_4.04.00.03_2" is the newest. If that's what your phone has then I don't think there is any value in unlocking.
An update from Google should be coming or announced before the end of the month, so maybe it'll have some fixes for you. If not, than at that point I would go ahead and unlock it.
i went ahead and successfully unlocked the boot loader. im trying to load the recovery.img via a terminal app on my phone but i get a message saying permission denied. i heard that there was a way of loading the recovery.img through rom manager, so i tried it.i got a message saying an error occurred while attempting to run privileged commands.
any ideas?
thanks!
seems like i dont have superuser.....
Yup, when I type su in terminal I get a message telling me that I don't have those privaleges. Any ideas? I'm Googling but can't find results.
i find the instructions in here relatively newb friendly. But read all carefully before rushing into action.
Stock to Root:
http://forum.xda-developers.com/showthread.php?t=636795
Recovery Image:
http://forum.xda-developers.com/showthread.php?t=611829
CM ROM (if that is what you would like to have)
http://forum.xda-developers.com/showthread.php?t=623496
and... do all the above first, before you mess with the radio image. all over the above is relatively safe/cannot brick your phone but wrongly flashing radio image can brick your phone permanently (especially if you run out of power or pull the battery during the radio update process)
Thanks. I'm er27. Do I flash with or without himen?
to make it very simple, i'd just recommend first:
1) flash Amon_Ra's recovery image 1.70 (i sent you the link earlier)
2) flash Cyanogen CM5.0.6 (I sent you the link earlier)
3) flash CM's google-addon (on the same page)
CM5.0.6 includes Himem, no need to flash separately.
See how it goes.... THEN you can try flashing radio to EPE54B, but please read all related to that careful. the command is simple, but if you pull your battery during the update, or the phone runs out of power, or you otherwise try to interrupt the process, your phone WILL BE permanently broken. Sometimes the radio update takes a long while (15 min or so), and it seems unresponsive, then you have 2 automatic reboots - those moments can be frightening. best would be to leave the phone plugged into the power socket while you doing it
shmigao said:
to make it very simple, i'd just recommend first:
1) flash Amon_Ra's recovery image 1.70 (i sent you the link earlier)
2) flash Cyanogen CM5.0.6 (I sent you the link earlier)
3) flash CM's google-addon (on the same page)
CM5.0.6 includes Himem, no need to flash separately.
See how it goes.... THEN you can try flashing radio to EPE54B, but please read all related to that careful. the command is simple, but if you pull your battery during the update, or the phone runs out of power, or you otherwise try to interrupt the process, your phone WILL BE permanently broken. Sometimes the radio update takes a long while (15 min or so), and it seems unresponsive, then you have 2 automatic reboots - those moments can be frightening. best would be to leave the phone plugged into the power socket while you doing it
Click to expand...
Click to collapse
damn you just scared me straight. is it possible that future cm roms include new radios?
sheek360 said:
damn you just scared me straight. is it possible that future cm roms include new radios?
Click to expand...
Click to collapse
just achieved root! but my google apps arent in the phone. gotta get epe54b in
All done. Thank you all for your help!8

[Q] Any way to put Safestrap Recovery on without APK?

My Droid 4 is bricked, but out seems to me that if I could get safestrap recovery in, I could boot any working "safe" ROM and leave my non-functioning "unsafe" system alone until the day a fastboot image becomes available.
The only wrinkle is that since the current OS is bricked, I can't load the Safestrap recovery via Apk. Is there any way to load it using one of the remaining capabilities in the phone (normal recovery, fastboot, etc.)?
I definitely don't have the full technical ability to answer your question, but to get the ball rolling:
Can you get adb up and running? If you can't, my guess is no... If you can, somebody who knows more than I do might be able to get you going...
Call Motorola or the wireless vendor where you got your phone and play dumb.
How did you brick your phone?
I bricked mine the first time by restoring a saved stock rom that I had made. Little did I know, but I got the webtop save mixed up, and totally soft-bricked my handset.
Safestrap is a good alternative to having nothing, but you should read everything there is to know about it before installing it. Conceptually, it doesn't share a whole lot with the original clockworkmod recovery.
RueTheDayTrebek said:
Call Motorola or the wireless vendor where you got your phone and play dumb.
Click to expand...
Click to collapse
I've thought about it. (1) there's stuff on the internal "sdcard" (/sdcard, as distinct from the removable real SDC) I'd like to recover if I could, so restoring the phone I have right now is preferable, unless restoring from a fastboot recovery wipes /sdcard).. and (2) I hate the idea of "cheating" on a warranty for a self-inflicted product failure, both on the ethics of it and on the remote possibility I could get caught.
How did you brick your phone?
Click to expand...
Click to collapse
I had safely rooted the phone (Droid 4 Utility is awesome) and installed Titanium Backup Pro. I was playing around with freezing bloatware, deleting bloatware, and the like... the last thing I did before rebooting and never coming back was integrating system application dalvik cache into the ROM and then undoing that integration. But I can't be sure that was the killer, since I hadn't rebooted for a while before that... one of the other changes earlier could have been it.
Safestrap is a good alternative to having nothing, but you should read everything there is to know about it before installing it. Conceptually, it doesn't share a whole lot with the original clockworkmod recovery.
Click to expand...
Click to collapse
Yeah, I recognize it's a very different world because of the locked bootstrap, so I'd obviously have to adapt to the differences, but just the ability to get some use out of the phone before the fastboot recovery leaks would be a good start. My needs are not great. Something besides repeated reboots ("Droid..." every 10 seconds until the battery runs flat) would make me happier than a pig in slop.
podspi said:
I definitely don't have the full technical ability to answer your question, but to get the ball rolling:
Can you get adb up and running? If you can't, my guess is no... If you can, somebody who knows more than I do might be able to get you going...
Click to expand...
Click to collapse
Yeah. The times I've tried, the phone never boots to the point that the USB debugging driver on the PC ever sees the phone ("adb devices" lists nothing).
About the only interaction I can get to is to force the phone into fastboot and plugging in with the fastboot USB driver on the PC. RSD Lite does see the phone then. Too bad I don't have a fastboot recovery to use at that point.

Nexus 6 is horrible

I have a nexus 6. The sound quality is horrible with headphones and the speakers. I unlocked the bootloader, rooted the nexus 6. A lot of the custom roms I have tried freeze during installation and soft brick the phone. The only rom that works is the stock rom.
alucke
That's a rather non-descript post. Who's your carrier, what Rom's are you talking about, any custom kernels, did you perform a wipe before installing? As far as the Audio goes, I've got no complaints from the speakers nor using headphones (both hardwired and BT headphones). You do realize that the first boot after installing a fresh Rom can take several minutes, some as long as 8 minutes while everything is set in place. More info so that we can help, please.
alucke said:
I have a nexus 6. The sound quality is horrible with headphones and the speakers. I unlocked the bootloader, rooted the nexus 6. A lot of the custom roms I have tried freeze during installation and soft brick the phone. The only rom that works is the stock rom.
alucke
Click to expand...
Click to collapse
lol your doing something wrong.
i have flashed most of the available roms, in total hundreds of times, never failed to boot, not even once.
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Is this a rant or are you asking for help? This is a development forum, so not really the place to rant. If you want help, please ask specific questions whilst supplying relevant information
Need education
simms22 said:
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Click to expand...
Click to collapse
You are correct. Where do I go for help and advice upon this phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus6 is back in order. I some how managed to use the Root Tool Kit and "pushed" the factory to the phone. I assume this restored my ABD and debug thereby establishing USB connection between PC and phone. I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the phone and enable it.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
---------- Post added 21st September 2015 at 12:09 AM ---------- Previous post was 20th September 2015 at 11:59 PM ----------
simms22 said:
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Click to expand...
Click to collapse
You are correct. Where do I go for help and advice upon this Android phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online by self at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus 6 is back in order. I some how managed to use the Root Tool Kit v2.0.4 and "pushed" the factory, I downloaded from Google, to the phone. I assume this restored my ABD allowing debug thereby establishing USB connection between PC and Nexus 6, I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the Nexus 6 bootloader or Fastboot.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
This is the most idiotic post I've seen here all day. Seriously sell your nexus 6 and go buy a different phone if you don't like the phone or face the fact that you either don't know how to use a nexus device or you have a defective phone. But I'm almost entirely convinced this is 100% user error
Sent from my Nexus 6 using XDA Free mobile app
ray6279 said:
You are correct. Where do I go for help and advice upon this phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus6 is back in order. I some how managed to use the Root Tool Kit and "pushed" the factory to the phone. I assume this restored my ABD and debug thereby establishing USB connection between PC and phone. I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the phone and enable it.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
Click to expand...
Click to collapse
here is a good place to start
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
good luck!
Android documentation is kinda lacking
Its not terrible... Its just not entirely coherent, well organized or complete. A lot of poking around and learn by doing, patching together threads that document how things work ect...
Here is my suggestion:
Follow the second link posted by simms22 above, this one here: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Go here: https://developers.google.com/android/nexus/images?hl=en
And download the latest image for your phone (shamu, the images at the bottom of the list are most recent. All carriers currently use same build, unless your on tmobile or Fi)
Use some kind of unzipping program (not sure if winrar can do .tgz, if not just google "Windows .tgz") to decompress the image you download. This will have a few .img files in it and a .zip Unzip the .zip for the rest of the partition images for the phone.
With these you can use fastboot to re-format partition to stock.
Here is an older guide, while devices may vary a little... and things have changed since 2011, were still mostly talking about system, boot, recovery, data....
http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
I would say read through the above guides thoroughly, then manually update your phone to stock.
You will notice the stock flash-all script will
Code:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.10.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.101.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy48m.zip
You probably don't want to do all this... You will notice the last command I showed is fastboot -w update image-shamu-lmy48m.zip (assuming you downloaded the lmy48m image)
We already unzipped this, so rather then flash it in bulk (flashing userdata.img will wipe device) lets flash everything but leave data in place.
So get fastboot working, go to bootloader, and as the script does
With fastboot:
Flash the bootloader
then use fastboot to reboot, to the bootloader
flash the radio
then use fastboot to reboot to the bootloader
then fasboot flash system, recovery, boot and cache images, skipping userdata to avoid wiping the sd card.
At this point reboot. It may take a while for the first boot as android sets itself up and optimizing applications. If things appear to be hung give it 10 minutes before forcing a reboot checking your images and trying again. Pay attention to the output of the commands and make sure there are no errors. If there are read them, and google them.
Now you should be able to boot, and you will be fully stock. This is what it takes to recover from almost any situation. Often you can just flash system to update. Boot will overwrite your kernel, so it is often skipped when custom kernels are used... particularly when not encrypted.
Now find the website for twrp and find the image for your device, then go back to bootloader mode and flash recovery, after flashing reboot directly to recovery.
Also find chainfire's website with the recovery flashable supersu (should be a .zip)
Make sure the supersu install zip is on your phone, and the recovery is on your computer.
Reboot to bootloader and fastboot flash twrp to your recovery partition, then immediately reboot to recovery mode to finish the install.
In recovery make a backup of your working stock system.
After that install supersu
Reboot, and you should be stock and rooted with a backup of your completely stock system.
From here if your want to install a rom reboot to recovery, wipe caches, system and data. On future upgrades backup first, and try only wiping system and caches, then flash the new version of the rom and you wont have to set anything back up. You will have to reinstall xposed if your use it, as well as supersu if your rom does not include it for some reason.
If you do all that, read those guides to the point where you understand each step, and read the thread or at least the last hand full of pages of any rom or utility that you use... Things should work pretty good.
It so easy for some to assume user error, the phone might be a defective I know hate the layout of mine, and out of 13 android phones currently this d*m thing is the only one that freezes on me and will not show up in Linux (two versions) or windows 7 and it still stock. I have hated the phone from day two and tried very hard to use it stock for as long i could. I finally said screw it and went back to my old lg g flex till just died.. I wish i could sell this...but I am stuck trying to make it work. still cant even make it show up in any os and that makes it a bit hard to do anything (and yes my USB ports and drivers and cables are fine i have checked)
And likewise to this post , useless as well
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
nevermind
simms22 said:
nevermind
Click to expand...
Click to collapse
:laugh: :laugh:
Was going to post, and had this thought also....
btw JJD loves his N6 and his speakers Rock!
#nuffsaid
Nexus 6 ftw!
disturb1 said:
It so easy for some to assume user error, the phone might be a defective I know hate the layout of mine, and out of 13 android phones currently this d*m thing is the only one that freezes on me and will not show up in Linux (two versions) or windows 7 and it still stock. I have hated the phone from day two and tried very hard to use it stock for as long i could. I finally said screw it and went back to my old lg g flex till just died.. I wish i could sell this...but I am stuck trying to make it work. still cant even make it show up in any os and that makes it a bit hard to do anything (and yes my USB ports and drivers and cables are fine i have checked)
Click to expand...
Click to collapse
It is user error.
SOME hardware is bad... But people like to view their phones as these temperamental beasts that "need to settle" and "all have their own intricacies"
Its a computer. Is this the way we look at laptops?
Two, or two hundred version of linux... Doesn't really matter because linux is a kernel and MTP implementation is handled separately. Not Nexus' fault that you didn't configure linux correctly, or that you expected someone else to do it for you for free, and they didn't do it either.
What file manager do you use, and did you have gvfs-mtp or kio-mtp installed?
What utilities were you using to mount the mtp drive?
These instructions are for arch linux, https://wiki.archlinux.org/index.php/MTP#simple-mtpfs (I use simple mtpfs), adapt them to your distro, find your distros documentation.
But then you don't really need it to show up in the OS? Does fastboot recognize it? Have you installed udev rules for it?
ok, thanks for all the input. I will give the nexus 6 a try again, root it. Can anyone point me to a custom rom that is somewhat close to stock?
I like Pure Nexus
scryan said:
It is user error.
SOME hardware is bad... But people like to view their phones as these temperamental beasts that "need to settle" and "all have their own intricacies"
Its a computer. Is this the way we look at laptops?
Two, or two hundred version of linux... Doesn't really matter because linux is a kernel and MTP implementation is handled separately. Not Nexus' fault that you didn't configure linux correctly, or that you expected someone else to do it for you for free, and they didn't do it
Click to expand...
Click to collapse
Not sure if I just have issues with lollipop or the hardware and lollipop
I have it rooted now and also still hate it I don't have the sound issues that some have but freezing was a constant with nexus T-Mobile stock ROM or maybe I have a lucky lemon ether way
I don't blame others or look to others to do my rooting rom installation or themes nor do I assume that it the phone every time all I am saying is we need to stop blaming every confused user as noob and assume people are not trying to learn
I been here 3 years but I lurk and learn and move on but I constantly see issues of flaming it is sad ...I see your reply and that fact that you offered help is what I like to see what I would offer if I knew an answer..
Honestly I am just not a fan of the phone but I made my bed and in it I must... hack at it till I am happy...

LG G3 LS990ZVG: LG One Click Root Doesn't Work (Lollipop 5.0.1)

Maybe a thread like this has been created before, I don't really know, but I kinda feel like my case is a little bit different.
I wanted to try to root my phone, considering Sprint is literally doing no updates for the LG G3, which stinks but that's another thread for another day. Anyhow...
I've followed the instructions of trying to root this phone, making myself a developer on said phone, USB Debugging is on, plug the bad boy into the PC. I have the LG Drivers as well as the "One Click" root system. First issue is the one click installer doesn't find the LG ports ever, so I have to hold the Volume Up button to put it manually into download mode. I've done this multiple times now and not much has changed. When I do go into download mode, down in the gray box it usually shows the the SuperSU command in the box, but the numbers have changed multiple times. First time it said SuperSU27 on COM4 (can't remember the exact verbiage it used for the file name) the next attempt was 25 on COM3, 21 on COM3 and last time it was 79 on COM3.
While all of that is going on, I get the message that it is rebooting my phone through one click, which it isn't, it's still trying to supposedly download SuperSU, which, always sat at 0% and never progressed.
I've noticed that many people haven't been using ZVG to root their LG G3's. I would attempt reseting my entire phone completely scratch, but I don't really dig the sketchy sites that LG Flash is on, so I've never downloaded anything from them for that. Then again, I would like to avoid totally resetting my phone like that, because I'm not very fluent in phones like that to trust myself to do something that could potentially mess it up.
Does anyone have a work around for my issue or know what could be going on.
did you figure this out? I'm in the exact same predicament..
tri0xinn said:
did you figure this out? I'm in the exact same predicament..
Click to expand...
Click to collapse
No I haven't. I have absolutely no experience at rooting phones, so it's basically something I can't figure out.
I've seen people completely reset their phones manually but I don't feel competent enough to try it.
I had an incident while flashing a ROM and had to use LG flash tool. I let the phone update to ZVG, but cannot get Root. Realistically, all I want is to be able to use wifi tether for now. I'm running into the same problem, the one click root is not noticing my device after i manually put it into Download Mode. Maybe it has to do with using Wimdows 10? Which operating system are you using? Have you figured it out?
ZVG is rooted!!
runningbandit said:
I had an incident while flashing a ROM and had to use LG flash tool. I let the phone update to ZVG, but cannot get Root. Realistically, all I want is to be able to use wifi tether for now. I'm running into the same problem, the one click root is not noticing my device after i manually put it into Download Mode. Maybe it has to do with using Wimdows 10? Which operating system are you using? Have you figured it out?
Click to expand...
Click to collapse
Well, I figured it out... Go Here if you're still looking... Do Method B, download the zip and go manually through it... Worked fantastic!
https://forum.xda-developers.com/sp...-zvb-rooted-stock-t3211878/page8#post70645157
thanks runningbandit!
now to get twrp

Delete all files and re-partition all?

If you ever had loaded into recovery in temporary TWRP you'll note that even after formating /data/ and doing an advance wipe (selecting everything), then enter the file manager there is still a bunch of folders and some files throughout your device.
Is there a way to wipe out everything and start completely 100% fresh?
DO NOT DO THIS --- OR --- DO but do not cry about it
I have an answer to my question and it is as I suspected. The short and more official answer is, no. The longer answer is, yes, technically. -- But you should not try it unless you are 100% sure you can live without your phone (forever).
As it turns out no one had a full 100% flash for the whole device and its complete file system structure (except for Motorola). But as it turns out without a manufacturing cable it would be useless anyway. This is because part of your phone is protected and cannot be wiped clean and flashed so blindly... ie... Unlike your desktop computer. But if you're like me you have noticed some orphan files (a few logs).
Is it worth taking the risk just to clear some orphan files? Probably not. But since you do not have a manufacturing cable and technically, your phone can recover, what you can do is the following.
Do NOT use the TWRP installed on your phone. Rather use it in memory
Code:
sudo fastboot boot twrp-3.3.1-0-payton.img
Load TWRP and format DATA
Reboot, go to advance wipe, wipe everything.
Reboot to TWRP (again)
In TWRP via the terminal type in
HTML:
rm -r -f *
You will see a lot of things that cannot be deleted. This is because you do not have permission to do so. What little is removed will likely be restored after reboot from the master rom hidden somewhere on your phone which cannot be played with unless you have a manufacturing cable (so I am told). ---- If you have such a cable --- DO NOT DO THIS. --- If you suspect you have such a cable --- Do NOT do this. -- I did this with just my normal charging cable.
After you have run the command which will take forever. Tell TWRP to reboot to bootloader. You will now have a BLACK screen. This is where I panicked. I waited a while and long pressed down the power button (presumably turning off my device). Then I pressed down the power button and the lower volume button. -- Keep holding the buttons. -- It will take longer than you like but your phone will boot up. And low and behold everything that was in the master rom (chip?) has been restored and you will now see the bootloader screen (finally). Load TWRP and install your ROM of choice.
How many times have I done this successfully? 2x
Does this mean this is dependable? Unlikely
Do I recommend this? No.
Should you depend on this? No.
Are you taking a large gable? YES
Can this brick your device? YES, more than likely.
Should you do this if you have any doubts? NO.
Will you get any help if this goes wrong? NO.
So why did I do it? As I look to possibly upgrade my phone in the future I feel a little more daring and can afford to do so. lol
you say "yes, technically", but I have yet to see someone get back to a fully operational stock. The best they can do is get to a mostly operational custom ROM. I (and a bunch of other folks here) would love to be proven wrong.
KrisM22 said:
you say "yes, technically", but I have yet to see someone get back to a fully operational stock. The best they can do is get to a mostly operational custom ROM. I (and a bunch of other folks here) would love to be proven wrong.
Click to expand...
Click to collapse
After performing this I installed only the official firmware. No additional ROM or GSI. The firmware itself includes the stock software.
A word of caution. --- I did this on 3 phones now. 2 work just fine. But 1 does not. The one that does not reports my IMEI as 0. This means it boots, it loads, it will play games and apps and update via Google Play Store, but it will never make a single phone call ever again. --- Food for thought.
Thanks. That got me thinking - I wonder if you took the one with no IMEI and plugged it to Moto's Smart Assistant, would it recognize it? Would it allow you to force flash it?
KrisM22 said:
Thanks. That got me thinking - I wonder if you took the one with no IMEI and plugged it to Moto's Smart Assistant, would it recognize it? Would it allow you to force flash it?
Click to expand...
Click to collapse
The world will never know. lol --- I'm a Linux user and their app doesn't seem to like Wine. I suppose I could set up a virtual machine with Windows and hope to connect through that. But I was once informed you really cannot do that via a virtual machine. Unless I was misinformed?! In any case, flashing the phone is not a problem. I can wipe it and reinstall any ROM or GSI at the moment. Or I can repeat my process too back to stock under a full wipe. The results appear to be the same.
I already have ordered a cheap Moto G7 from Google as a replacement. My current plan will be to find a very light (small), bare-bones ROM / GSI and install it onto this Moto X4. From there I'll load it up with games and such and let the kids play with it. Figure since it cannot make or receive calls anymore (or text messages either) it will make for a fun little toy.
MotoX4 said:
The world will never know. lol --- I'm a Linux user and their app doesn't seem to like Wine. I suppose I could set up a virtual machine with Windows and hope to connect through that. But I was once informed you really cannot do that via a virtual machine. Unless I was misinformed?! In any case, flashing the phone is not a problem. I can wipe it and reinstall any ROM or GSI at the moment. Or I can repeat my process too back to stock under a full wipe. The results appear to be the same.
I already have ordered a cheap Moto G7 from Google as a replacement. My current plan will be to find a very light (small), bare-bones ROM / GSI and install it onto this Moto X4. From there I'll load it up with games and such and let the kids play with it. Figure since it cannot make or receive calls anymore (or text messages either) it will make for a fun little toy.
Click to expand...
Click to collapse
Thanks! Yeah, in the past I have been a lot on Ubuntu and stuff like this is not forgiving for wine.
It's a darn shame that we can't just send these phones to Moto with $25 and get it fixed. Oh well!
KrisM22 said:
Thanks. That got me thinking - I wonder if you took the one with no IMEI and plugged it to Moto's Smart Assistant, would it recognize it? Would it allow you to force flash it?
Click to expand...
Click to collapse
Moto smart assistant can`t recognize the phone in rescue mode..
St.Noigel said:
Moto smart assistant can`t recognize the phone in rescue mode..
Click to expand...
Click to collapse
I know it can't on yours, and most folks with this prob. I was wondering about MotoX4's case. But thanks for trying it!
I had high hopes for that smart assistant when I discovered it, but no joy. When we lost RSDlite, we lost a lot - unless they upgrade it...
KrisM22 said:
I know it can't on yours, and most folks with this prob. I was wondering about MotoX4's case. But thanks for trying it!
I had high hopes for that smart assistant when I discovered it, but no joy. When we lost RSDlite, we lost a lot - unless they upgrade it...
Click to expand...
Click to collapse
RSDlite? Lost? Is this what you seek? https://rsdlitetool.com/
MotoX4 said:
RSDlite? Lost? Is this what you seek? https://rsdlitetool.com/
Click to expand...
Click to collapse
6.2.4 won't recognize a Moto X4 after it is upgraded to Pie.
I used RSDLite since the times of the P2K and MAGX (Linux)... but since it's easier to use fastboot commands...
I have a stock X4 Android One around, if I want to flash Pixel Experience, can I go back to stock in the future?
joel_sinbad said:
...snip...
I have a stock X4 Android One around, if I want to flash Pixel Experience, can I go back to stock in the future?
Click to expand...
Click to collapse
In all probability, NO.
Then I'm gonna stay on Stock Rom, so... If I want to flash custom Roms, there's not way back...
joel_sinbad said:
Then I'm gonna stay on Stock Rom, so... If I want to flash custom Roms, there's not way back...
Click to expand...
Click to collapse
If you read a lot on this forum, that's the message I see.
I agree, NO going back. You can, I have... flash any factory Pie rom . All will flash fine and no IMEI, wifi. Radios are gone. I use Google Fi and cell data services go wierd on custom roms, if you want carrier switching.
This makes me think that the Moto X4 is more dangerous than the back then Atrix 4G with their Tegra 2 chipset...
joel_sinbad said:
This makes me think that the Moto X4 is more dangerous than the back then Atrix 4G with their Tegra 2 chipset...
Click to expand...
Click to collapse
I don't recall thinking that the Moto Atrix 4g was at all dangerous when I had one - a rather nice phone imho, though that was a very long time ago. I don't think of the Moto X4 as "dangerous" - it is simply that there is not a correct understanding of the Pie file structure by the custom ROM devs such that their ROMs would not so change the file structure of the phone as to prevent it from being flashed back to stock.
Users need to recognize that, with this phone, you can't get back to stock if you flash any custom ROM.
afaik.
This change happened with the file structure and boot structure changes of the Pie update. Prior to that, folks could get away with all manner of mods. Devs for this phone need to approach modifications with the idea of assuring that any mod can be flashed back to stock, BEFORE it is released. That has not happened. And likely won't. User beware!
KrisM22..... Thank you for stating what I could not do as well.
kkjb said:
KrisM22..... Thank you for stating what I could not do as well.
Click to expand...
Click to collapse
we ALL do it, and CAN do it - all in hopes of saving some newbie from disaster!

Categories

Resources