The summary of what happened is as follows.
I have the HDX 7 and it auto updated to 13.3.2.3.2, so I modified the build.prop to spoof it as being 13.3.0.9
I had done this successfully before (OTA update was NOT stopped by hdxposed) so I was feeling super confident
Here's where I made my mistake though
I forgot to reset my permissions
So, once I rebooted, it obviously didn't work.
In a panic, I tried to factory reset. I should have guessed it wouldn't touch /system .
Now, I personally can't think of any way I could possibly fix this device, but maybe someone here has some wizard magic I could use, I've honestly all but given up hope.
I can still see the low battery icon if it's low and I try to boot it, and I can still get into Amazon's extremely limited bootloader (your kindle could not boot, reboot, factory reset) but other than that I don't think I can do much with it.
Please, if anyone has any suggestions... ;-;
Pretty sure there's not a fix based on all the other threads where people have done the same thing.
Reboot into fastboot and try to flash amazon's stock firmware.
Demonoid111 said:
Reboot into fastboot and try to flash amazon's stock firmware.
Click to expand...
Click to collapse
Would this work?
amazon/gp/product/B0099E59SG (sorry, can't submit URL due to being a new user)
If I can actually boot into fastboot and have it work properly, I would be able to flash a .bin to it? I'm sorry for being so ignorant about the subject.
You may be able to flash a .bin if you can get into fastboot mode, but from what I understand, there is no hardware button combo that will get you into fastboot mode unless you have an unlocked bootloader. If you have any sort of adb when it tries to boot, then adb reboot-bootloader may put you in the right place, but if not, then I'm not sure there is much to be done.
I would check out this thread to get some more info on the state of fastboot.
http://forum.xda-developers.com/showthread.php?t=2799793
good luck!
Hmm, unless I can get some confirmation on that fastboot cable, I don't think I have much hope it seems ._.
The only current way to access fastboot mode is via adb, correct?
Tumbtack said:
Hmm, unless I can get some confirmation on that fastboot cable, I don't think I have much hope it seems ._.
The only current way to access fastboot mode is via adb, correct?
Click to expand...
Click to collapse
Hi! You can use the Wugfresh's nexus 7 tool, it will let you go into fastboot but as far as I know you cant flash .bin may be I'm wrong but you can try...
http://forum.xda-developers.com/showthread.php?t=2389107
SiulGM said:
Hi! You can use the Wugfresh's nexus 7 tool, it will let you go into fastboot but as far as I know you cant flash .bin may be I'm wrong but you can try...
http://forum.xda-developers.com/showthread.php?t=2389107
Click to expand...
Click to collapse
Does this actually do anything special or is it just an adb/fastboot GUI? Because I'm currently in Linux and installing windows is a /huge/ pain and I'm sure messing with it in WINE would just make things worse... Though if it does actually do something special I would be more than willing to do it for that.
Still looking for some type of answer.
Even if I did somehow access fastboot mode, would it even help me?
Try this (if you haven't already):
1. Setup a Linux environment (Ubuntu 13.04 - is being used on the tutorial) - you can install it on a USB stick and then boot the PC from the USB without making any changes.
2. Install the Android SDK (that you can have adb and fastboot installed) - (follow this guide: http://forum.xda-developers.com/showthread.php?t=2302780 )
3. Boot the tablet while pressing all the HW buttons (VOL+ , VOL - , POWER Button) - I've read somewhere from @Hashcode that the original firmware has code to boot into fastboot while pressing all the buttons without the need of a "special" fastboot cable.
4. Check the fastboot commands and see if recognizes it.
aaronkatrini said:
Try this (if you haven't already):
1. Setup a Linux environment (Ubuntu 13.04 - is being used on the tutorial) - you can install it on a USB stick and then boot the PC from the USB without making any changes.
2. Install the Android SDK (that you can have adb and fastboot installed) - (follow this guide: http://forum.xda-developers.com/showthread.php?t=2302780 )
3. Boot the tablet while pressing all the HW buttons (VOL+ , VOL - , POWER Button) - I've read somewhere from @Hashcode that the original firmware has code to boot into fastboot while pressing all the buttons without the need of a "special" fastboot cable.
4. Check the fastboot commands and see if recognizes it.
Click to expand...
Click to collapse
Will definitely try tomorrow, only difference being I'll be in arch rather than ubuntu, though that shouldn't be a big enough difference to pose a problem. I'll keep you updated with how it goes. Thanks!
Return?
Why don't you just try to give the device back? I'm pretty certain other people have done it.
I don't think
aaronkatrini said:
Try this (if you haven't already):
1. Setup a Linux environment (Ubuntu 13.04 - is being used on the tutorial) - you can install it on a USB stick and then boot the PC from the USB without making any changes.
2. Install the Android SDK (that you can have adb and fastboot installed) - (follow this guide: http://forum.xda-developers.com/showthread.php?t=2302780 )
3. Boot the tablet while pressing all the HW buttons (VOL+ , VOL - , POWER Button) - I've read somewhere from @Hashcode that the original firmware has code to boot into fastboot while pressing all the buttons without the need of a "special" fastboot cable.
4. Check the fastboot commands and see if recognizes it.
Click to expand...
Click to collapse
That it really matters if you get it to recognize it or not the device will not accept through fast boot unless it is unlocked from what I understand. What good is fastboot if we don't have any fastboot files in any public way at least anyway that I know. The fastboot commands will work from what I have read but you cannot flash any bin files or any system files. Until it is unlocked and Hashcode says once unlocked everything flashes fine .
Besides he should be working with this thread it has fixed several people with the same problem http://forum.xda-developers.com/showthread.php?t=2588608 not specifically just OP but there is very in-depth discussion throughout the thread with useful information
Related
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
tawhid111 said:
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script to get into fastboot at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
Click to expand...
Click to collapse
So you solve it! :good:
:/
tawhid111 said:
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
Click to expand...
Click to collapse
Still unable to do it, when I plug the cable holding vol+ it just reboot normally :/
foreverman said:
Still unable to do it, when I plug the cable holding vol+ it just reboot normally :/
Click to expand...
Click to collapse
Then try enter in lelus fastboot mode, ad then flash x-loader, uloader, boot.img and recovery.img from stock rom for your device type model. Then repeat steps 1 and 2
Where can I find the lelus script?
Sent from my Note II
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
ciccillover said:
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
Click to expand...
Click to collapse
Then you need a Technician with a Octopus Box to repair your partition table...
ciccillover said:
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
Click to expand...
Click to collapse
Can you boot into recovery? We now have a custom recovery for locked bootloaders (and CM roms). If you can get into recovery, I would try some adb commands to mount the partitions.
No, no recovery. Just to make sure that I'm not doing it wrong, what is the key combination to boot to recovery?
I have also tried:
Code:
fastboot boot some_recovery_image.img
It says ok, but the phone just hangs at the black screen and becomes undetectable as a fastboot device, until I pull the battery. So, unless the some_recovery_image.img is unsuitable for my P760 (which may be!), there is something seriously wrong I think.
Or maybe I can try the same command with the custom recovery for bootloader locked phones... Where can I find it?
ciccillover said:
No, no recovery. Just to make sure that I'm not doing it wrong, what is the key combination to boot to recovery?
I have also tried:
Code:
fastboot boot some_recovery_image.img
It says ok, but the phone just hangs at the black screen and becomes undetectable as a fastboot device, until I pull the battery. So, unless the some_recovery_image.img is unsuitable for my P760 (which may be!), there is something seriously wrong I think.
Or maybe I can try the same command with the custom recovery for bootloader locked phones... Where can I find it?
Click to expand...
Click to collapse
Your EMMC partition is wiped or fried... you really need a JTAG service or a Box like octopus because your L9 is Hard-bricked...
Thanks for your opinion. Yet, I still want to hear from others.
I'm running into more and more problems with the L9 as their me grows.
-Fastboot doesn't work under Windows 8.1 and 10, but under the now obsolete(for me) Windows 7, unlike my other devices, which are fine with Win 10.
-ADB seems to work, but requiring the device to be still able to boot.
-I always boot to recovery from within Android as long as the L9 ain't bricked. After a failed rom install, during which the sd card failed(could no longer write or be formatted afterwards, the last time stamps of files and folders were set during the failed install) I discovered a problem with TWRP(Artas182x's and Edwin's), which may have been present since a long time: Trying to invoke TWRP via keypress will brick the device!
So, if my P760 no longer boots, there's only download mode available, sort of the final line of defense.
-There's sort of a trick if even download mode fails: After a failed attempt unplug phone, force switch-off, if the phone is in brick state. Then switch on, force switch-off again, and only then attempt download mode again. And have patience while holding down the vol button, it might take up to 20 seconds for the phone to switch itself on into download mode. (A single forced powerdown will cause Fastboot NOT to work the next time)
But I'm absolutely clueless about the recovery issue, for now TWRP is semi-working, can only be accessed via Android, as long as the phone is fully working.
W/o Fastboot, I now have flashed stock rom several times and rooted it with Kingo rooter just to be able to run Flashify to install TWRP. If Flashify is the culprit for the TWRP issues, I could need a recommendation for a better working app.
ciccillover said:
Thanks for your opinion. Yet, I still want to hear from others.
Click to expand...
Click to collapse
Tried OMAP flasher ? It needs memory configuration file in order to work with our device
No, I didn't. I have sold the phone for spares.
Inviato dal mio LG-D855 utilizzando Tapatalk
I never needed the OMAP drivers and tools. As they are ancient, they will probably make even more problems with newer Windows versions.
I could by no means invoke Fastboot on this device with Windows 8.1 and 10, Seven worked. So you had to go for Download Mode instead to recover to stock rom, then root with the Kingo tool, then install TWRP via Rashr or Flashify, the most time consuming way to recover from the frequent bricks.
And the LG Flash Tool 2014 always needed several attempts to get the job done. The latest official recovery tool from LG works in D/L Mode, but will always download the rom image anew.
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Download mfastboot and redownload the recovery img
hetor99 said:
Download mfastboot and redownload the recovery img
Click to expand...
Click to collapse
Thanks.
Decided to install it on my desktop. While trying various files, my laptop accidentally got hit with Chromium virus. It looked like all required files were there, but kept having problems with a couple of those sdk files (tools/platform tools).
I'm still getting the following error:
( bootloader) has-slot :recovery: not found
And once again the Android SDK Tools and Android SKD Platform-tools that are under Tools (preview channel) are unchecked. Not sure if they are needed.
Follow the instructions of how to install on the general section
hetor99 said:
Follow the instructions of how to install on the general section
Click to expand...
Click to collapse
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
L8Show said:
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
Click to expand...
Click to collapse
How to Install TWRP Recovery and Root MOTO E
https://www.youtube.com/watch?v=9Jh-O2LGL3Y
OK, it is done.
Took a couple days with several hours of clicking, and checking settings, and reading and researching, and watching videos, and downloading, and installing/uninstalling, and restarting, but it's now rooted! Way too much time wasted even though it was raining and the gf and I were just watching movies for a lot of it. She kept asking me why I'd waste so much time and remind me I had a perfectly fine iphone nearby. Today I finally got to the point where I had given up. I figured something was screwed up with the phone after that reset on my computer.
Some highlights that may or may not be helpful for the next moto e rooter:
USB debugging was somehow switched to off a few times after I turned it on. Might have been after resetting phone, but who knows exactly.
I set screen to stay while connected via USB.
I removed all the apps I could and took out the sd card.
Kingoroot stuck at 66% many, many times, and then phone would restart. Research showed it may be accessing the wrong ADB instance or something. So I uninstalled SDK, fastboot, Minimal, etc. Anywhere it could have been hiding. Even did a system restore to last week the day I reinstalled windows. Didn't help one bit. Which is to also say... there are a half dozen or more legit options. Try different ones if you are relatively confident you followed directions the 1st 10 times.
Ministro didn't have moto e in their data base.
Finally back to XDA after checking a dozen videos (I have to admit I was completely dumbfounded and was mad at the whole process). I found XDA Kingroot and right away it worked, but it needed permission to allow apps that were not certified or some thing. I can see how people would think this is so easy. If I had started with this, I'd never have had to ask for help here. Btw, was this my problem all along? Did I miss that in the instructions or was it something else possibly? I don't remember if I did that before since it was 3 days ago.
So far I am thoroughly impressed with the this moto e. I paid $40 for it on a whim and now that I can remove a bunch of bloatware and customize it a bit, I think it may be a good gateway into android devices.
Thanks for looking and all your suggestions.
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
faheyd said:
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
Click to expand...
Click to collapse
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
L8Show said:
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
Click to expand...
Click to collapse
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
-z3r0- said:
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
Click to expand...
Click to collapse
Thanks for that information. I thought I saw adb devices command working in fastboot mode in one of the videos so I thought that was the problem. I thought adb needed to root the phone.
In order of what I've done with the phone so far:
Sent/got codes and unlocked moto e.
Turned on developer options and USB debugging.
Was then unable to get TWRP or the other cw something to work using the command fastboot flash recovery (file name) or fastboot boot... commands.
Gave up and installed Kingroot and everything worked fine.
Decided to try to install TWRP and superSU since kingroot had worked. I read that the phone needed to be flashed back to stock to do this and watched/read a couple of guides. http://forum.xda-developers.com/showthread.php?t=2759495
I used the following named file:
SURNIA_ACG_LTE_5.1_LPI23.29-30_cid9_subsidy-DEFAULT_CFC
The phone was changed back, but data doesn't work. I can't access wifi because as soon as I switch it on, it switches back off. 4G, etc is not working either. So after trying to figure that out I decided to just proceed and put TWRP/superSU on the phone.
I powered off the phone. Powered into fastboot mode connected the phone to my computer.
I opened Minimal fastboot folder and shift/right click to bring up the command prompt.
In the command promt i typed fastboot devices and it shows my phone.
I then type fastboot flash recovery (file name or renamed to recovery or renamed to TWRP or I click the actual file and drag it to the command prompt) and then hit enter.
It says it's doing stuff in so many seconds, but after nothing happens. The phone doesn't reset like some of the videos. If I reset it, it powers on, but not into the TWRP screen.
After that I did more reading and found out that adb doesn't always play nice with windows 8.1 and that you might need to force other drivers to make it work right. I did this next and was going to try all the available options from universal naked driver later, but there were no motorola drivers.
Then I came here and learned something new. ADB devices command doesn't work when the phone is in fastboot mode so that has no effect on installing twrp...
Right now I am considering trying to install the other stock files I have access to:
SURNIA_ACG_LTE_5.1_LPI23.29-20_cid9_subsidy-DEFAULT_CFC (20 instead of 30).
After that I am out of ideas if it's not the adb problem. Might kingroot again and go from there.
Ok after researching, it seems that LTE file may not work on sprint and there was success using the boost file from
http://www.filefactory.com/file/6be...XI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml.zip
(2 hour dl make that 5+ lol)
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'll try that next to get the wifi working and then figure out why it won't root.
Thx!
L8Show said:
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Click to expand...
Click to collapse
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
---------- Post added at 05:30 AM ---------- Previous post was at 05:29 AM ----------
rakeshwipr said:
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
Click to expand...
Click to collapse
and open the command prompt with admin rights
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
d
Thanks! The devices shows up when on as ADB and in fastboot too. I had to take a break when the kernel download took 8 hours, but I think I got the file that will work to fix the wifi issue. I can't mess with it til I get home tomorrow, but I will read and follow all advice.
For the previous poster, I did do the admin rights and did rename TWRP file to recovery... I aslo tried many other combinations, but will keep it in mind for all further attempts.
Appreciate the help so far. I almost left it with the kingroot, but it was bugging me that I couldn't get it to go. Hopefully I'll have good new tomorrow.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
Device shows up in both instances.
It's stock now and the wifi works. Flashed it back to stock by following Mdkcheatz guide here:
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'm stuck where I was when I first started this thread. I've set my account up as administrator. Developer is enabled and so is USB debugging. I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
I confirmed the connection:
fastboot devices
I try to flash it with the:
fastboot flash recovery recovery.img
It says:
target reported max download size of 268435456 bytes
sending 'recovery' (6928 KB)...
OKAY [ 0.359s]
writing 'recovery'...
OKAY [ 0.359s]
finished total time: 0.578s
C: |Program Files (x86)\Minial ADB and Fastboot>
I'm running windows 8.1 (64 bit). I read that some people had had problems with windows 8. Kingroot worked through the app store. It has been flashed with various stock kernels and that usually takes a few minutes so I don't think it's doing much in half a second. I'll research a bit more, but I think it just a bad combination of this version phone and windows 8.1.
I started the phone after this last attempt. Are there any files in internal storage that I should look for?
L8Show said:
I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
Click to expand...
Click to collapse
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
-z3r0- said:
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
Click to expand...
Click to collapse
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
L8Show said:
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
Click to expand...
Click to collapse
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
-z3r0- said:
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
I am on v2.65. Should I use this version? I checked root and it's rooted, but I needed to use no bloat app (instead of free titanium) to remove some apps. Is that normal? I thought once rooted and set up, I would have complete control. Some apps seem very invasive so I haven't grabbed many yet. I have some questions about apps, etc., but will probably research and ask in another forum if needed.
Thx again for all the help and pointing out my mistake.
Generic Disclaimer: By doing any of the process listed below you accept complete responsibility over any of your actions, I will not be responsible if you end up causing hard brick, data loss or any kind of loss to your personal property.
Hii XDA fellows,
So I have seen many people asking for noob friendly guide to restore original oxygen os firmware or basically unbrick device. There are several thread on this already but trust me I have tried them all and in my case I had to use my own brain. So I have compiled a noob friendly guide which I,myself have used to unbrick my device.
small warning this will wipe all of your data.
Firstly I wants to thank Some_Random_Username for bringing up MSM Unbrick tool for OnePlus Nord. His guide to unrick nord is also fairly good enough but in my case I was stuck in bootloop after installing a rom. My phone was not even booting to Qualcomm EDL Mode so that I can use MSM Tool.
Lets start with pre-requisites:
You must have unlocked bootloader.
Original Oneplus Type - C cable.
Windows PC.
ADB debugging turned on your phone.
Firstly Switch off your device, which I think most of you have already have as the device is bricked but in case your phone is stuck in bootloop or recovery or bootloader menu itself then try holding down voume up button and power button together hold them down till you get heptic feedback and screen goes off. Let it be cool down for about a minute.
Now Setup your PC:
Download MSM tool to from this guide : Click here
Setup adb environment in your PC if you havent already setup follow this guide
Download Qualcomm EDL drivers from here: Click here
Now download Unofficial TWRP recovery by Mauronofrio from here
On your PC right click on start menu icon and start Windows Powershell(Admin) and type this command bcdedit /set testsigning on This will turn off driver signature verifications on windows you will be required to restart your pc now after you restart your pc will boot into test mode and you'll see a watermark stating the same in bottom left of your desktop. Worry not we will undo this after we have finished restoring.
install Qualcomm EDL drivers by running the setup listed above.
Unzip MSMTool there you will see a file named MsmDownloadTool V4.0.exe run it, it'll take some time but after you see a pop up asking for user type user name and password, Select other as user type and leave other stuffs blank as it is and click next.
In the next window, In the target button select O2 while using global tool or India while using indian tool or EU when using european tool.
Now you have to boot into Qualcomm Emergency Download Mode
You can do this in several diffrent ways but one I am listing here is recommended :
Boot into fastboot/bootloader mode by pressing and holding Volume up, Volume down and power button together when you see a Menu pop up on your screen you can let go all the fingers at once.
Now connect your phone to your PC and go to that folder where TWRP recovery is located. Hold Shift button and Right click inside that folder you'll see an option "Open powershell window here click on it. In the powershell window type
fastboot devices and press enter your device will be listed as fastboot devices in powershell window. Now type
fastboot boot twrp1.img press enter
your device will boot up in TWRP recovery in twrp recovery go to reboot section and select Edl, This will boot your phone Edl mode your screen will go off as soon as it happens in the MSM tool window you'll see a device listed as com3/com5/com7.
Click on start button the restoration process will begin. Wait for about 400 secs and your device will automatically boot up.
Voila you've successfully unbricked your phone.
If you want to exit from Driver test mode on your pc simply start a powershell window with admin rights and type
bcdedit /set testsigning off
and restart your PC.
So first off all i want to say thanks for this guide.
So , i have a problem with my phone getting reconized by my pcs, so, my Phone just works fine but i want to restore it to stock, i'm using aospex 8.3.
Since a few days my phone dosnt get reconzied by my pc, i've tried windows and linux, both installations cant find my phone, i tried diffrent pc's,usb cables, driver, new installations of windows and linux mint, other phones dont have this problem, tried resetting , everything, do you have a idea what i could try or could it be just my phone port thats damaged and cant transfer data anymore, if anyone has an idea i would really be happy about an answer , thanks!
peppanzer said:
So first off all i want to say thanks for this guide.
So , i have a problem with my phone getting reconized by my pcs, so, my Phone just works fine but i want to restore it to stock, i'm using aospex 8.3.
Since a few days my phone dosnt get reconzied by my pc, i've tried windows and linux, both installations cant find my phone, i tried diffrent pc's,usb cables, driver, new installations of windows and linux mint, other phones dont have this problem, tried resetting , everything, do you have a idea what i could try or could it be just my phone port thats damaged and cant transfer data anymore, if anyone has an idea i would really be happy about an answer , thank
Click to expand...
Click to collapse
Seems like it's a software issue probably a bug in your rom rich out to the developer he might help you, as you have tried both with Linux and windows i don't think it's a driver issue, it could be an issue with the hardware also but chances are pretty low for this to happen. Try flashing other roms if you have backup of your phone, use orange fox recovery it has an option of taking nandroid backup.
IamAlok said:
Seems like it's a software issue probably a bug in your rom rich out to the developer he might help you, as you have tried both with Linux and windows i don't think it's a driver issue, it could be an issue with the hardware also but chances are pretty low for this to happen. Try flashing other roms if you have backup of your phone, use orange fox recovery it has an option of taking nandroid backup.
Click to expand...
Click to collapse
the thing is that i cant flash other roms, my phone dosn't gets recognized in fastboot, recovery and edl, so with the aex recovery installed i have no chance to change the rom without a pc, reached out to the dev but seems i'm the only person with the proplem, but thanks for helping.
Hey everyone. Today I've finally unbricked my Zenfone 7 after my dumbass locked the oem with fastboot since I've already rooted my phone and didn't want to use adb anymore (I was getting tired of the warranty voided message at boot too). Right after locking the oem, the phone booted and displayed a message that says: " Your device is corrupted. It cannot be trusted and won't boot". You already could tell I was scared as hell, so all I did the past hours was to look around until I found this solution!
Have in mind I'm not an expert or a developer, I'm only hoping you find this thread if you ever find yourself locked in fastboot with no access to recovery, oem, adb or usb debugging, just fastboot commands.
Having said that, you need to flash the raw firmware for your device. For the Zenfone 7 the one you need is "WW__ZS670KS_29.14.53.5_MR1.3_20201111_release-user.raw".
You also need:
- Android sdk and platform tools (minimal adb works too but I recommend original google software)
- Usb asus drivers
- Usb google drivers (installable from android studio just like sdk and platform tools)
Turn on your device on fastboot and connect it to your pc, then open cmd or powershell on your platform-tools folder and execute
Code:
fastboot devices
to check if your zenfone is detected. Close the command prompt.
Now, on the raw rom folder open flashall_AFT.cmd as administrator, then it should start flashing all of the stock firmware files. Once the prompt closes itself, reboot your phone using volume keys and power button to select.
In my case, right after booting, the phone displayed a message that said "your phone is corrupted" but with a wipe data option this time around. Choose wipe data/factory reset (all your data will be gone).
There you go! The phone should reboot into stock clean rom now.
I get Flashing is not allowed in Lock State
RickJF said:
I get Flashing is not allowed in Lock State
Click to expand...
Click to collapse
did you unlock bootloader?
IronSingh said:
did you unlock bootloader?
Click to expand...
Click to collapse
No, to do so I need go get into developer tools,
wich I can't because android won't boot
[ROM][OFFICIAL] Omnirom for zenfone7/7pro [Android-13.0]
What is Omnirom ? Selinux Status: Enforcing Instructions : Follow this Steps by steps You need to be lastest firmware on both slots Please. How to have lastest FW on both slots: Reboot twrp Flash stock + twrp on opposite reboot recovery do...
forum.xda-developers.com
RickJF said:
No, to do so I need go get into developer tools,
wich I can't because android won't boot
Click to expand...
Click to collapse
RickJF said:
I get Flashing is not allowed in Lock State
Click to expand...
Click to collapse
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
tommydotwav said:
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
Click to expand...
Click to collapse
What is the problem?
tommydotwav said:
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
Click to expand...
Click to collapse
thanks, I've searched enough and tried it all, sent ticket to Asus support,
they say considering all that it's probably physically corrupted,
nothing much I can do at home
RickJF said:
thanks, I've searched enough and tried it all, sent ticket to Asus support,
they say considering all that it's probably physically corrupted,
nothing much I can do at home
Click to expand...
Click to collapse
DM me, make sure you are able to do test Point, we can fix it via EDL
I tried to root my phone using this guide, followed it down to the word and yet my phone's stuck in a bootloop. It keeps restarting to the Poco start screen.
Ive got the stock recovery, and for some odd reason fastboot commands work only in the "FASTBOOTD" screen and not the the "FASTBOOT" screen which you get from "adb reboot bootloader" command.
I try to shut it down and it boots up back again in the same screen and is stuck there.
Im clueless and I really dont know what to do. Some help would be greatly appreciated.
edit: I tried to use the stock recovery and wipe data. No progress.
I tried to connect the phone with the MIAssistant but the app doesnt recognise the device.
I tried using the MiFlash tool to flash the stock rom, it goes on infinitely. Im currently trying to use the SP Flash tool and MediaTek Bypass tool but I havnt got any progress yet.
I promise I'm never buying MediaTek devices ever again.
Careful with the Flash and Bypass tools, they can cause problems.
What can you achieve with the hardware buttons on the phone? Can you get it into recovery?
Fastbootd working but fastboot not sounds like a USB drivers problem - there are some driver options here.
aricooperdavis said:
Careful with the Flash and Bypass tools, they can cause problems.
What can you achieve with the hardware buttons on the phone? Can you get it into recovery?
Fastbootd working but fastboot not sounds like a USB drivers problem - there are some driver options here.
Click to expand...
Click to collapse
It was a driver issue, thanks for the link.
What I did to get out of the bootloop:
1. Download the latest Miui rom for your version, make sure it's the recovery version and not the fastboot one.
2. Press ALL the buttons, Vol+ Vol- and Power button to shut it down for a few seconds (assuming you can't switch it off as it keeps powering back up again).
3. After it's switched off, quickly press the power and vol- button until you see the FASTBOOT screen.
4. Connect with PC, make sure you have the proper drivers and have connected with the right USB port.
5. Download OrangeFox custom recovery. It is a unofficial custom recovery, so its stability is questionable. But it does the job here.
6. Copy the OrangeFox zip and the Miui rom file to your phone's SD card or any external storage which your phone can access.
7. In your PC, extract the OrangeFox zip folder in your platform-tools folder. (The folder where you run your cmd fastboot/adb commands)
8. Open up cmd, and enter the command:
fastboot flash boot recovery.img
9. Your phone should boot up to the OrangeFox recovery. If not switch the phone off (Step 2) and press power + vol+ button for booting up to the recovery.
10. Locate your OrangeFox zip installer file in the recovery and flash it.
11. Reboot to the recovery again.
12. Locate the Miui rom and flash that. Before swiping to flash the rom, there is a check box which says something like "flash OrangeFox once the rom has been flashed". If you want to keep OrangeFox as your recovery then check it, or else leave it unchecked. Flashing roms remove custom recoveries.
13. Your phone must reboot to miui.
NOTE: You can use fastboot commands to flash the rom but I'm not very familiar with fastboot commands (I actually forgot most of them). Hence I use the recovery method.
warhead1721972 said:
It was a driver issue, thanks for the link. Should I delete this post? It isnt much big of an issue imo.
Click to expand...
Click to collapse
Great, glad you got it sorted! No, leave it up, you never know someone might stumble across it and find it useful