[Q] Tough time going back to stock - Motorola Atrix HD

I've been running CM 11 for a little more than a month and have been really enjoying it. So, I have no idea why I decided to download the MythTools and revert back to stock At&t. Doing so, I messed something up on my phone.
To start, I'm using Windows 7 64bit and when selecting option 1 (install ADB-fastboot-apkTools) I get the new cmd window that states "please select install button after new window is opened press any key to continue...." when I press any key the cmd window would just close. Hoping it would help, I then chose option 6 to update my Motorola drivers. When my browser window opened I got the ADB installer window and clicked install. It seemed to have installed fine. I then updated my moto drivers. Thinking I was all set I went for option 2 to flash the stock firmware which I had put in the firmware folder. With my phone in fastboot I started the process and it failed. Reading through the cmd prompts I had noticed it said something like 'you selected 2- instal cwm.img cannot load cwm.img' . I unplugged my phone and tried to restart it and it was stuck on the bootloader screen. I then restarted into recovery and my PhilZ recovery did start up. However it displays "E: could not mount /data to setup /data/media path!" . I was still able to go through the process of a clean re-install of CM 11 but am stuck on the startup splash screen for CM.
I definitely got myself in way too deep and am clueless on how to fix this. Would someone mind instructing me on what to try next? Many thanks in advance.

I am not sure if it would make a difference in your situation but I do everything for my phone on an x86 system. I have had issues with LG and Samsung phones in the past when trying things on an x64 computer.

ifixgse said:
I've been running CM 11 for a little more than a month and have been really enjoying it. So, I have no idea why I decided to download the MythTools and revert back to stock At&t. Doing so, I messed something up on my phone.
To start, I'm using Windows 7 64bit and when selecting option 1 (install ADB-fastboot-apkTools) I get the new cmd window that states "please select install button after new window is opened press any key to continue...." when I press any key the cmd window would just close. Hoping it would help, I then chose option 6 to update my Motorola drivers. When my browser window opened I got the ADB installer window and clicked install. It seemed to have installed fine. I then updated my moto drivers. Thinking I was all set I went for option 2 to flash the stock firmware which I had put in the firmware folder. With my phone in fastboot I started the process and it failed. Reading through the cmd prompts I had noticed it said something like 'you selected 2- instal cwm.img cannot load cwm.img' . I unplugged my phone and tried to restart it and it was stuck on the bootloader screen. I then restarted into recovery and my PhilZ recovery did start up. However it displays "E: could not mount /data to setup /data/media path!" . I was still able to go through the process of a clean re-install of CM 11 but am stuck on the startup splash screen for CM.
I definitely got myself in way too deep and am clueless on how to fix this. Would someone mind instructing me on what to try next? Many thanks in advance.
Click to expand...
Click to collapse
you said you are stuck on startup splash meaning bootloop? if it is you should try again with rsd lite.
else you may lose all your data in the memory but do a format media/data and sdcard, so that it can mount /data, it worked for me. then format system mount everyting and do a fresh install of any rom you can sideload or just have it in the sdcard.

I'm pretty sure I am doing something wrong with MythTools. When I select option 2 in the tool to install stock firmware the following happens,
- asks for fimware folder example and I select "N"
- asks if firmware files are finished copying.. I press enter and continue
-then it says "the system cannot find the path specified
the system cannot find the path specified
the system cannot find the path specified
'7z' is not recognized as an internal or external command
operable program or batch file
Are you ready to flash stock fimware...
at this point i stupidly hit enter and that was it with my phone. I'm guessing the tool could not locate the firmware .xml file for extracting and I have no idea why. The compressed folder is IN the firmware folder.
One other question with Mythtools, when installing the tools what path do you want them installed in? I did them in the same file the Myth tools are in.

ifixgse said:
I'm pretty sure I am doing something wrong with MythTools. When I select option 2 in the tool to install stock firmware the following happens,
- asks for fimware folder example and I select "N"
- asks if firmware files are finished copying.. I press enter and continue
-then it says "the system cannot find the path specified
the system cannot find the path specified
the system cannot find the path specified
'7z' is not recognized as an internal or external command
operable program or batch file
Are you ready to flash stock fimware...
at this point i stupidly hit enter and that was it with my phone. I'm guessing the tool could not locate the firmware .xml file for extracting and I have no idea why. The compressed folder is IN the firmware folder.
One other question with Mythtools, when installing the tools what path do you want them installed in? I did them in the same file the Myth tools are in.
Click to expand...
Click to collapse
Disclaimer: Even though this worked for me I am not responsible if you brick your phone, I am simply sharing my experience
Okay, this is not for the faint of heart and is going to sound a little backward but it just worked for me 5mins ago. I am running Windows 8.1 Pro 64bit, so there shouldn't be a problem with your setup. I was having the same problem until I just double clicked on flashing.bat or main.bat instead of running as admin. After all I AM the admin of my PC. Then, it worked perfect...until flashing the tz.mbn file and froze up while writing the file. I thought mmm...it shouldn't take that long to write such a small file, and writing happens on the phone side (I believe) so I hit the phone's power button while leaving the Myth Tools window open, which disconnected the phone obviously. I booted back into fastboot and it continued from where it left off. (Note: I did this a few weeks ago when I lost my radios and manually flashed the modem file, which froze, but I followed the same procedure and it successfully flashed it) Then when it got to the last system.img chunk (it writes it in small chunks of 30mb and the last one is smaller, that's how I knew it was the last one) it froze again. I let it sit for about 5mins just to make sure it was written to the phone the repeated the sequence to reboot manually into fastboot and bang, once again it continued right where it left off. one or two more freezes and voila...it rebooted right back to stock. Any questions don't hesitate to ask.
If this helps you hit that thanks button!

Related

Boot loop problem

Hello,
I tried installing a custom ROM on my 7310 and it had issues. I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop. I think I need to repartition, but when I click the repartition checkbox in ODIN I get an error.
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Thanks.
A few questions:
spazlon said:
I tried installing a custom ROM on my 7310 and it had issues.
Click to expand...
Click to collapse
What did you try to flash and how did you try doing it (CWM, ODIN, ...)?
What 'issues'?
I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop.
Click to expand...
Click to collapse
How far into the boot sequence does it get?
Are you able to get into recovery?
If so, what recovery do you have (Stock vs CWM)?
Have you tried seeing what is causing the boot-loop using adb?
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Click to expand...
Click to collapse
This is an action of last resort. Exhaust all other avenues first.
boscorama said:
What did you try to flash and how did you try doing it (CWM, ODIN, ...)?
What 'issues'?
Click to expand...
Click to collapse
I used CWM to flash AOSP 4.1.2. It seemed to work fine for a day or two, but then it needed charging (as normal). I let it charge over night and in the morning it had less battery. I figured the charger or cable were flaky so I tried another set on another outlet and same thing. Then it finally ran out of battery. I let it charge again over night and when I tried to turn it on it was really slow. The boot animation was only 1 frame every couple seconds. It would eventually boot all the way up, but it was still REALLY slow. So I went into CWM and reflashed the same ROM. Then I got a boot loop of the boot animation. I couldn't get into CWM any more, so then I went into download mode and flashed the official firmware and flashed it with ODIN.
boscorama said:
How far into the boot sequence does it get?
Click to expand...
Click to collapse
Now when I turn it on it just says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I can flash again with ODIN and it will get to the Samsung boot animation and just pulse SAMSUNG.
boscorama said:
Are you able to get into recovery?
If so, what recovery do you have (Stock vs CWM)?
Click to expand...
Click to collapse
If I hold power and volume down I can get into download mode or Samsung recovery, not CWM, and power with volume up doesn't do anything.
boscorama said:
Have you tried seeing what is causing the boot-loop using adb?
Click to expand...
Click to collapse
I don't know anything about adb and I'm not sure what I would be looking for. Is there a tutorial I can follow somewhere?
Thanks for any help!
This worked for me with similar problem
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Thanks! I'll give this a try when I get home. I'll let you know how it works out.
Don't ever try to 'repartion unless you really know what you're doing. You're soft bricked. Repartion and you'll hard brick.
I'd go back and get hc from sammobile and flash that with Odin. Ics has had some problems.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
Don't ever try to 'repartion unless you really know what you're doing. You're soft bricked. Repartion and you'll hard brick.
I'd go back and get hc from sammobile and flash that with Odin. Ics has had some problems.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Agreed - my procedure avoids manual repartitioning - I tried lots of other procedures but none worked. I think my data partition had become corrupt because I kept getting error messages. My first try was to recover with my cwm recovery file I made originally but I kept getting back to the boot loop .
spazlon said:
Hello,
I tried installing a custom ROM on my 7310 and it had issues. I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop. I think I need to repartition, but when I click the repartition checkbox in ODIN I get an error.
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Thanks.
Click to expand...
Click to collapse
I always got something like that ...
After bootloop just go to recrovery mode then factory riset ... its 100% WORK
Sent from my GT-P7300 using xda premium
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
spazlon said:
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
Click to expand...
Click to collapse
Sorry - being a newbie myself I'm at a loss. It worked a charm for me.
spazlon said:
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
Click to expand...
Click to collapse
did a format /system before installing the custom roms? This is an important step.
prince93 said:
did a format /system before installing the custom roms? This is an important step.
Click to expand...
Click to collapse
This fixed it. Never had to do it with any of my other devices. CM10 loaded quickly after that. Loving how fast JB is!
Thanks!
Sent from my GT-P7310 using Tapatalk HD
It worked
mobjunky said:
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Click to expand...
Click to collapse
WOw! This fixed my Tablet! thank you ever so much!!
mjramos15 said:
WOw! This fixed my Tablet! thank you ever so much!!
Click to expand...
Click to collapse
mobjunky said:
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Click to expand...
Click to collapse
Gee thanks. This saved my tab. I'd almost given up on it and then voila.

[Q] Help: Bootloop after installing CWM (video) (tried google)

So I brought myself in a bad situation.
Here's a video showing what the phone does and me trying to get into CWM:
http ://www .youtube. com/watch?v=5F2Gg_eU7Yw
I was trying to root my sony xperia z1 compact using this guide: http ://techglen. com/2014/02/05/root-xperia-z1-compact-d5503-4-3-14-2-a-1-114-official-firmware/
Following the steps it asked me to CWM 6 using this guide: http ://techglen. com/2014/02/05/install-cwm-6-on-xperia-z1-compact-d5503-4-3-14-2-a-1-114-official-firmware/2
I checked firmware and version of my phone and everything was correct.
I must admit I have no clue as to what I'm doing but I'm normally ok with tech stuff and the guide seemed detailed and trust worthy so I thought I could do it following the guide.
I got the bootloading unlocked just fine and started to install CWM. I made it this far:
- After downloading CWM kernel zip (Its not the actual name of file, just a reference name), place it in internal or external SD Card of your smartphone
- Now extract CWM kernel zip on your PC’s desktop and copy boot.img
- Paste this file inside the folder where you have installed Minimal ADB and Fastboot
- Now turn off your smartphones completely
- Plug in mobile’s USB in cable in PC port only
- Hold Volume up button and plug in USB cable in mobile’s port
- LED will turn blue (If it does not remain blue for long, then read Optional part in bootloader unlocking method explained above
- Once you are successfully in fastboot mode, then you can continue
- Now type Fastboot flash boot boot.img and press Enter
- It will flash boot.img file on your device
- Now unplug the device and boot it up
- As soon as you see purple colored LED, start pressing volume up and down buttons repeatedly, until you are in CWM mode
- In CWM Mode, select “Install Zip”
Click to expand...
Click to collapse
I downloaded CWM .img file, placed it in my ADB folder and placed a copy on my phone. Using ADB I flashed the CWM .img (bolded step), unplugged the phone and the CWM screen came up and I was able to navigate using the volume buttons. So far so good.
At this point I realized that the CWM .img file I had downloaded and placed on my phone was not a zip file and I couldn't find it. So I hit reboot to boot up my phone normally so I could place the .img packed as a .zip file on the phone. Some error message came up, but I didn't manage to read it but caught something saying root I think.
As it rebooted the sony logo came up but then the purple led turned on and it seemed to boot into CWM again. A brief screen explaining how to navigate came up as you see in the video below (but with no menu options to actually navigate) before it rebooted and repeated.
I can still use ADB and fastboot, but I can't get into CWM and I can't boot normally.
Edit: Just tried "adb devices" and it says "list of devices attached" and then it's just blank. I can't push files onto the phone (error: device not found) but I can still reboot the device fusing fastboot and there's no error when I try and reflash cwm. Reading up on this it would seem that usb debugging has somehow been turned back on so adb can't acces the phone but fastboot can. Any way to turn on usb debugging through fastboot?
I tried a forced shutdown using the off button next to the sim card but it didn't help.
The phone is not recognized by my computer so I can't place or delete files from it.
Here's a video showing what the phone does and me trying to get into CWM:
http ://www .youtube. com/watch?v=5F2Gg_eU7Yw
If I don't press the volume button it will just keep looping in the sony logo and purple led light.
What I want to do is get back to a normal boot, remove the CWM .img file and put the .img file packed as .zip file onto the phone and retry the process.
I have googled a lot of options, but most results are a year old and I hardly understand half of what is being suggested. If anyone could please walk me through the process in a language that a total idiot can understand I would be so grateful and hopefully get my sleep back.
ravneravn said:
So I brought myself in a bad situation.
Here's a video showing what the phone does and me trying to get into CWM:
http ://www .youtube. com/watch?v=5F2Gg_eU7Yw
I was trying to root my sony xperia z1 compact using this guide: http ://techglen. com/2014/02/05/root-xperia-z1-compact-d5503-4-3-14-2-a-1-114-official-firmware/
Following the steps it asked me to CWM 6 using this guide: http ://techglen. com/2014/02/05/install-cwm-6-on-xperia-z1-compact-d5503-4-3-14-2-a-1-114-official-firmware/2
I checked firmware and version of my phone and everything was correct.
I must admit I have no clue as to what I'm doing but I'm normally ok with tech stuff and the guide seemed detailed and trust worthy so I thought I could do it following the guide.
I got the bootloading unlocked just fine and started to install CWM. I made it this far:
I downloaded CWM .img file, placed it in my ADB folder and placed a copy on my phone. Using ADB I flashed the CWM .img (bolded step), unplugged the phone and the CWM screen came up and I was able to navigate using the volume buttons. So far so good.
At this point I realized that the CWM .img file I had downloaded and placed on my phone was not a zip file and I couldn't find it. So I hit reboot to boot up my phone normally so I could place the .img packed as a .zip file on the phone. Some error message came up, but I didn't manage to read it but caught something saying root I think.
As it rebooted the sony logo came up but then the purple led turned on and it seemed to boot into CWM again. A brief screen explaining how to navigate came up as you see in the video below (but with no menu options to actually navigate) before it rebooted and repeated.
I can still use ADB and fastboot, but I can't get into CWM and I can't boot normally.
Edit: Just tried "adb devices" and it says "list of devices attached" and then it's just blank. I can't push files onto the phone (error: device not found) but I can still reboot the device fusing fastboot and there's no error when I try and reflash cwm. Reading up on this it would seem that usb debugging has somehow been turned back on so adb can't acces the phone but fastboot can. Any way to turn on usb debugging through fastboot?
I tried a forced shutdown using the off button next to the sim card but it didn't help.
The phone is not recognized by my computer so I can't place or delete files from it.
Here's a video showing what the phone does and me trying to get into CWM:
http ://www .youtube. com/watch?v=5F2Gg_eU7Yw
If I don't press the volume button it will just keep looping in the sony logo and purple led light.
What I want to do is get back to a normal boot, remove the CWM .img file and put the .img file packed as .zip file onto the phone and retry the process.
I have googled a lot of options, but most results are a year old and I hardly understand half of what is being suggested. If anyone could please walk me through the process in a language that a total idiot can understand I would be so grateful and hopefully get my sleep back.
Click to expand...
Click to collapse
I hope you made a backup of your phone.
It may be worth wiping everything and flashing the Z1 stock firmware on to your phone. Stock firmwares can be found relatively easily by using Google. There are also lots of different video tutorials on YouTube on how to how to revert back to stock firmware and on how you can escape bootloops. Try this: www. youtube. com/watch?v=j4gm9VeQCHA
You're on the wrong forum, this one is for Xperia Z, for Xperia Z1 Compact go here:
http://forum.xda-developers.com/sony-xperia-z1-compact

[Q] Huawei p7 Bootloop

A couple of days ago my Huawei p7 started to shut itself down and after that it keeps rebooting.
It starts itself up and I get into the choose your language screen and then it shuts down.
When i try to get into the system recovery (using volume & power) I get the following screen:
Android system recovery <3e>
Huawei software installed failed.
Please retry!
Shutdown system now
There is no UPDATE.APP
.............................................
FAIL
And even in system recovery it keeps rebooting.
Im kinda helpless at the moment not knowing what to do.
Did this occur to anyone ? Is there a solution for this problem ?
Thanks in advance.
You should download firmware update file from Huawei Official web site. Extract dload folder from downloaded archive and put it on your SD card. After that you should try to trigger firmware update with factory reset (method which is usually called "force update") by holding all three buttons when the phone is turned off.
But maybe your phone have some hardware problem if it restarts even in recovery mode.
UPDATE:
Does phone restarts itself when it's in fastboot mode (you can get into that mode by holding VOLUME DOWN and POWER button while phone is turned off and connected into USB port of computer just before pressing that button combination) ??
wekii said:
You should download firmware update file from Huawei Official web site. Extract dload folder from downloaded archive and put it on your SD card. After that you should try to trigger firmware update with factory reset (method which is usually called "force update") by holding all three buttons when the phone is turned off.
But maybe your phone have some hardware problem if it restarts even in recovery mode.
UPDATE:
Does phone restarts itself when it's in fastboot mode (you can get into that mode by holding VOLUME DOWN and POWER button while phone is turned off and connected into USB port of computer just before pressing that button combination) ??
Click to expand...
Click to collapse
I've downloaded the update file and proceeded with your steps. I continued to trigger the firmware update with the factory reset.
At first it seemed to work, the phone started updating but after a couple of seconds it started to reboot itself again
I got the phone in fastboot mode and at this moment it does not restart itself !
I went on downloading Hisuite and at this moment it keeps searching for drivers on the network.
The searching for drivers is taking quite some time is this normal ?
Thank you very much for your help so far !
OK, maybe these are good news if you say that your phone doesn't restart when it's in fastboot mode.
I would recommend you to try to reflash your phone's stock recovery and boot images with those extracted from firmware that you are trying to install.
Follow these steps:
Download Huawei Extractor tool from here,
Open update.app with Huawei Extractor and extract next two images: RECOVERY and BOOT (you can do that by selecting those two images while holding CTRL button, then right click > Extract Selected),
When extracted, rename those two images into "recovery.img" and "boot.img",
Copy those two images into "platform-tools" folder of Android SDK,
Run command prompt and go to "platform-tools" folder by using "cd" command,
Start your phone into fastboot mode,
Enter following command into command prompt: "fastboot devices" (without quotes), you should get your phone's serial number listed, if that's right, go to the next step,
Enter: "fastboot oem get-bootinfo", it needs to say that your bootloader is unlocked. If it's not you need to enter the next command "fastboot oem unlock 1234567812345678", where "1234567812345678" should be replaced with unlock code that is unique for your device. Instructions which explain how to obtain unlock code for your device can be found here,
Flash your phone's recovery with "fastboot flash recovery recovery.img",
Flash your phone's boot image with: "fastboot flash boot boot.img",
After successful flashing of both images, turn your phone off by holding POWER button for a several seconds,
Prepare SD card on your PC by formatting SD card and copying "dload" folder of phone's firmware onto SD card,
After you insert SD card into phone, start your phone with "forced install" method by holding all three buttons on your phone.
After that your phone should process firmware install successfully if there is no some hardware issues. Good luck and inform us about your progress.
wekii said:
OK, maybe these are good news if you say that your phone doesn't restart when it's in fastboot mode.
I would recommend you to try to reflash your phone's stock recovery and boot images with those extracted from firmware that you are trying to install.
Follow these steps:
Download Huawei Extractor tool from here,
Open update.app with Huawei Extractor and extract next two images: RECOVERY and BOOT (you can do that by selecting those two images while holding CTRL button, then right click > Extract Selected),
When extracted, rename those two images into "recovery.img" and "boot.img",
Copy those two images into "platform-tools" folder of Android SDK,
Run command prompt and go to "platform-tools" folder by using "cd" command,
Start your phone into fastboot mode,
Enter following command into command prompt: "fastboot devices" (without quotes), you should get your phone's serial number listed, if that's right, go to the next step,
Enter: "fastboot oem get-bootinfo", it needs to say that your bootloader is unlocked, if it's not read this,
Flash your phone's recovery with "fastboot flash recovery recovery.img",
Flash your phone's boot image with: "fastboot flash boot boot.img",
After successful flashing of both images, turn your phone off by holding POWER button for a several seconds,
Prepare SD card on your PC by formatting SD card and copying "dload" folder of phone's firmware onto SD card,
After you insert SD card into phone, start your phone with "forced install" method by holding all three buttons on your phone.
After that your phone should process firmware install successfully if there is no some hardware issues. Good luck and inform us about your progress.
Click to expand...
Click to collapse
Hi,
I've got the same issue.
When I start to "force install" method, my phone doesn't boot.
It just stay in a state of "charging" but nothing append.
I flashed boot and recovery with Fastboot.
But now, when I start the phone in Fastboot&Rescue Mode, the device doesn't appear in the liste when I run adb devices.
But when I start in the "force install" mode, adb devices returns the serial of the phone (but it doesn't respond to fastboot command).
Are there other files to flash on the phone than juste recovery and boot ?
Thank's for those steps, i'll continue to try to flash again.
Edit :
Ok phone is back !
The problem came from my SD Card, I had not only the dload folder, but an other file.
Format SD Card -> dload folder -> "force install" method -> ENJOY !
Thank's a lot !
wekii said:
OK, maybe these are good news if you say that your phone doesn't restart when it's in fastboot mode.
I would recommend you to try to reflash your phone's stock recovery and boot images with those extracted from firmware that you are trying to install.
Follow these steps:
Download Huawei Extractor tool from here,
Open update.app with Huawei Extractor and extract next two images: RECOVERY and BOOT (you can do that by selecting those two images while holding CTRL button, then right click > Extract Selected),
When extracted, rename those two images into "recovery.img" and "boot.img",
Copy those two images into "platform-tools" folder of Android SDK,
Run command prompt and go to "platform-tools" folder by using "cd" command,
Start your phone into fastboot mode,
Enter following command into command prompt: "fastboot devices" (without quotes), you should get your phone's serial number listed, if that's right, go to the next step,
Enter: "fastboot oem get-bootinfo", it needs to say that your bootloader is unlocked, if it's not read this,
Flash your phone's recovery with "fastboot flash recovery recovery.img",
Flash your phone's boot image with: "fastboot flash boot boot.img",
After successful flashing of both images, turn your phone off by holding POWER button for a several seconds,
Prepare SD card on your PC by formatting SD card and copying "dload" folder of phone's firmware onto SD card,
After you insert SD card into phone, start your phone with "forced install" method by holding all three buttons on your phone.
After that your phone should process firmware install successfully if there is no some hardware issues. Good luck and inform us about your progress.
Click to expand...
Click to collapse
I followed all your steps but i get stuck at step 7. When I give the command fastboot devices it doesn't show my phone's serial number. Instead it shows a ? (question mark).
Did I do something wrong or is there a solution for this?
Thanks in advance!
Maybe you should try other version of platform tools. I would recommend you to download adt-bundle-windows-x86_64-20140702.zip (x64) or adt-bundle-windows-x86-20140702.zip (x32) from "Android SDK" official web pages (I assume that your are using Windows OS). After download extract only "platform-tools" directory to the root of Windows C:\ partition and try described procedure again.
However if you are still getting question marks instead of phone's serial number, you should ignore that step and go onto the next one. I had the same problem in the past and flash commands were successful even serial number wasn't been displayed.
Keep us informed about your progress. Good luck zbnd !!
wekii said:
Maybe you should try other version of platform tools. I would recommend you to download adt-bundle-windows-x86_64-20140702.zip (x64) or adt-bundle-windows-x86-20140702.zip (x32) from "Android SDK" official web pages (I assume that your are using Windows OS). After download extract only "platform-tools" directory to the root of Windows C:\ partition and try described procedure again.
However if you are still getting question marks instead of phone's serial number, you should ignore that step and go onto the next one. I had the same problem in the past and flash commands were successful even serial number wasn't been displayed.
Keep us informed about your progress. Good luck zbnd !!
Click to expand...
Click to collapse
Thanks for your response !
So I followed through like you said. Gave the fastboot oem get-bootinfo command and then I got (bootloader) locked. So I followed the bootloader's unlock code (official way), entered my product SN and product IMEI, used the Huawei Product ID generator followed the procedure and all I get is : Please input the correct Product ID
What did I do wrong this time ? I'm not sure if it's even possible to do this wrong. Is there another way around ?
You can unlock with Vroot, like I did. I didn't try to get a serial from Huawei.
For the Fastboot command 'Fastboot device's I had a ? too, but with 'adb devices' command, I got my serial number.
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Pboguet said:
You can unlock with Vroot, like I did. I didn't try to get a serial from Huawei.
For the Fastboot command 'Fastboot device's I had a ? too, but with 'adb devices' command, I got my serial number.
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Click to expand...
Click to collapse
I've downloaded Vroot (english version) but when i connect my phone it says not support mode
I tried to connect while in fastboot&rescue mode, because this is the only way the phone stays on without restarting.
I then tried to connect without fastboot&rescue mode. But my phone keeps rebooting. I did get a message that USB debugging is disabled. However I can't enable usb debugging because my phone won't boot up normally.
@Pboguet
You should read carefully because your answer has no sense for the phone which is in state like zbnd's phone is.
 @zbnd
Maybe you are doing something wrong. You can send me your's phone serial number and IMEI in PM inbox, I will try to generate unlock code for you.
wekii said:
@Pboguet
You should read carefully because your answer has no sense for the phone which is in state like zbnd's phone is.
@zbnd
Maybe you are doing something wrong. You can send me your's phone serial number and IMEI in PM inbox, I will try to generate unlock code for you.
Click to expand...
Click to collapse
Thank you very much for all your help!
Despite following all your steps my phone keeps rebooting
Sorry to hear that. Did you manage to make all steps that I described to you? Can you share more informations about your current efforts please.
wekii said:
Sorry to hear that. Did you manage to make all steps that I described to you? Can you share more informations about your current efforts please.
Click to expand...
Click to collapse
Ik
After unlocking my phone I got the message unlocked in CMD.
I then flashed recovery and boot. Both times it said that the flash was succesfull, this only took a few seconds I don't know if thats normal? I then followed your last steps ( dload folder etc) and put the SD card in my phone.
It start installing but after approximetaly 25 seconds the phone shuts itself down and then reboots.
The procedure then starts again and it starts installing followed by shutting down and rebooting.
I'm sorry to hear that. Seems like it's some hardware issue.
However I still have one more idea that you can try in fastboot mode. I would recommend you to install entire firmware manually with fastboot commands.
By following previously described procedure try to extract with "Huawei Extractor" tool next images also: SYSTEM, USERDATA, CUST and CACHE.
After step number 10, try to use next commands also:
"fastboot flash system system.img"
"fastboot flash cust cust.img"
"fastboot flash userdata userdata.img"
"fastboot flash cache cache.img"
When you are finished with flashing of all images, use "fastboot reboot" command to restart your phone. Steps 11, 12 and 13 should be ignored this time.
Let me know the result
Hey, I'm glad I found this forum, because I have exactly the same problem! Since zbnd did not reply I wanted to let you know that flashing boot.img, recovery.img, cache.img, userdata.img, cust.img and system.img via fastboot did not work
The commandline for each file said "OKAY" and "finished" therefore I assume the process(es) completed succesfully.
Maybe I should tell you some information and the steps I did with my P7:
- my device is a branded german telekom version with firmware P7-L10-V100R001C150B122​- because of crappy pink telekom bootlogo und bloatware I wanted to flash the original huawei firmware so I downloaded the B126 from the official website and updated via force update method​- at the end of the update process i got the messages "huawei cust fail" and "update_post_process fail" but when I rebootet the B126 was installed and showed a message "Defect report reminders - This is an internal test version. Please report defects to Yangyexiao 00143718" - can't be correct, I thought​- after googling a lot and reading through several forums I rooted my device with RootGenius, installed HiSuite and Android-SDK (driver were installed correctly, adb devices showed a device with serial) and deleted the "cust" directory on my phone - at that point everything still worked​- next step: I installed TWRP 2.7.1.0, made an updateable zip file with huawei update extractor (including system.img, userdata.img, cust.img and boot.img) and flashed it via TWRP. The process completed succesfully, but needed only a few seconds. After that I got this bootloop at the language selection​- then I wanted to return to the last functioning state, so I flashed the stock recovery via fastboot and started with force update method. But after a few seconds the device rebooted during the update process which led to another (maybe the same) bootloop. I had to remove the sd card, but the device continued to reboot in recovery mode. So i installed TWRP 2.7.1.0 again​- Then I tried to restore a B133 backup I got from another forum, but it obviously did not work (see attached image)​
Now I just don't know what to do ... I get a bootloop in stock recovery and I get a bootloop in TWRP 2.8.0.0.
Only TWRP 2.7.1.0 does not reboot. What is about the other files inside the UPDATE.APP (modemimage.img, efi.img, etc)? Is it possible that some of these files are needed?
Thanks in advance...
mbert said:
Hey,
Only TWRP 2.7.1.0 does not reboot.
Thanks in advance...
Click to expand...
Click to collapse
If this recovery works than try:
1. Save this Se7en or this HRT or this custom MIUI ROM on SD card
2 .Wipe in TWRP everything (dalvik, system,data,cust, internal) except external (SD card). Internal only if You have a backup or not important data there.
4. Install zipp ROM from external memory. Sometimes try more than one time in fail case. For HRT ROM especially.
Let me know if helped.
Ziółek said:
If this recovery works than try:
1. Save this Se7en or this HRT or this custom MIUI ROM on SD card
2 .Wipe in TWRP everything (dalvik, system,data,cust, internal) except external (SD card). Internal only if You have a backup or not important data there.
4. Install zipp ROM from external memory. Sometimes try more than one time in fail case. For HRT ROM especially.
Let me know if helped.
Click to expand...
Click to collapse
failed
I tried se7en and miui.
I wiped dalvik,system,data,internal,cache and custom, which only lasted about 2 seconds, but said succesful (Is that enough to delete all partitions?).
Installation of both custom roms completed succesfully and lastet several seconds (max 1 min I think).
Se7en: reboot -> huawei logo -> reboot -> language selection (in the style of stock rom?) -> reboot ...
Miui: reboot -> miui logo -> reboot -> language selection (miui style) -> reboot -> wifi selection (I skipped) -> searching for sim card -> reboot
mbert said:
Hey, I'm glad I found this forum, because I have exactly the same problem! Since zbnd did not reply I wanted to let you know that flashing boot.img, recovery.img, cache.img, userdata.img, cust.img and system.img via fastboot did not work
The commandline for each file said "OKAY" and "finished" therefore I assume the process(es) completed succesfully.
Maybe I should tell you some information and the steps I did with my P7:
- my device is a branded german telekom version with firmware P7-L10-V100R001C150B122​- because of crappy pink telekom bootlogo und bloatware I wanted to flash the original huawei firmware so I downloaded the B126 from the official website and updated via force update method​- at the end of the update process i got the messages "huawei cust fail" and "update_post_process fail" but when I rebootet the B126 was installed and showed a message "Defect report reminders - This is an internal test version. Please report defects to Yangyexiao 00143718" - can't be correct, I thought​- after googling a lot and reading through several forums I rooted my device with RootGenius, installed HiSuite and Android-SDK (driver were installed correctly, adb devices showed a device with serial) and deleted the "cust" directory on my phone - at that point everything still worked​- next step: I installed TWRP 2.7.1.0, made an updateable zip file with huawei update extractor (including system.img, userdata.img, cust.img and boot.img) and flashed it via TWRP. The process completed succesfully, but needed only a few seconds. After that I got this bootloop at the language selection​- then I wanted to return to the last functioning state, so I flashed the stock recovery via fastboot and started with force update method. But after a few seconds the device rebooted during the update process which led to another (maybe the same) bootloop. I had to remove the sd card, but the device continued to reboot in recovery mode. So i installed TWRP 2.7.1.0 again​- Then I tried to restore a B133 backup I got from another forum, but it obviously did not work (see attached image)​
Now I just don't know what to do ... I get a bootloop in stock recovery and I get a bootloop in TWRP 2.8.0.0.
Only TWRP 2.7.1.0 does not reboot. What is about the other files inside the UPDATE.APP (modemimage.img, efi.img, etc)? Is it possible that some of these files are needed?
Thanks in advance...
Click to expand...
Click to collapse
To use fastboot you need to unlock bootloader first. And before flash, you need to erase partition first, for a proper job. Please read well about the fastboot procedure is a dangerous procedure
My bootloader is unlocked, but fastboot sais I don't have permission to erase partitions ...
Gesendet von meinem HUAWEI P6-U06 mit Tapatalk

Official ROM for AT&T ASUS MeMo Pad 7 LTE (me375cl aka K00X) and root on Lollipop

Where I can find official ROM for asus me375cl based on android 5.1.1?
Finaly, i find zip with official ROM on 4pda:
4pda-ru/forum/index.php?showtopic=799982
(put '.' (dot) instead '-' in url)
A special thank to alexoid79 for instruction.
little_pindos said:
Finaly, i find zip with official ROM on 4pda:
4pda-ru/forum/index.php?showtopic=799982
(put '.' (dot) instead '-' in url)
A special thank to alexoid79 for instruction.
Click to expand...
Click to collapse
Thank you so much for posting where you found this, this is exactly what I needed!!! You saved my tablet, it is much appreciated! :good:
Flashing Factory Image
The following instructions worked for me when trying to reflash the factory firmware for the ATT Asus MemoPad 7 LTE (ME375CL). I did originally try using the Asus Flash Tool and the raw firmware file (link below) but the tool said it could not unzip the package for some reason or another. So the steps below show how I did it using ADB with fastboot.
I ASSUME NO LIABILITY SHOULD THIS GO WRONG FOR YOU! However, it probably shouldn't matter if you are bricked, I doubt it will make it any worse Either way, I will not replace your tablet or be responsible for troubleshooting it should you mess it up more...
This scenario is based on the tablet stuck on the Asus boot screen and not going any further. I was trying some in depth rooting attempts and bricked it badly. I was then trying to install a custom recovery and that is why I could not reset it and bricked it.
PRE-REQS:
1. ADB installed - Download: https://drive.google.com/open?id=0B0fKccJIuWsna04wMjY1eG9YREU
2. Asus Drivers installed
3. Firmware - Download: https://drive.google.com/open?id=0B0fKccJIuWsnWGhwYzA0Vkluc2s (file is 1 Gb + in size, may take a bit)
SETUP:
If you already have a working ADB setup, do not download the one above. If you are using the one above, I extracted the folder into my C: drive, so the path for ADB would be C:\adb (to keep it simple and less typing).
MAKE SURE THE ASUS DRIVERS ARE INSTALLED! If you have plugged the tablet in to a pc before, they should already be there. Otherwise search, download and install the appropriate drivers.
INSTRUCTIONS:
Extract the firmware zip file to somewhere easily accessible like your desktop. In there, you should see the boot.img, recovery.img and system.img files, copy/paste those files to your ADB folder (for easier typing later on). There are also additional files like these but start with "unsigned_", do NOT use those!
1. Ensure you probably have at least 30% battery charge, I would still recommend more though.
2. Put the tablet in Fastboot mode by ensuring the tablet is completely powered down and then press/hold the VOLUME UP and POWER keys at the same time. When the Asus screen appears, let go of the POWER button but continue to hold the VOLUME UP button. Let go of the VOLUME UP button when the fastboot screen appears.
3. Plug the tablet in to the computer and then open a CMD prompt as administrator.
4. The following uses the ADB downloaded and placed in the folder as listed above, you may need to adjust the location path as needed if you already have ADB installed or located in a different path.
Type in the following without the quotes: "cd c:\adb" (this will change the path to the ADB files for the CMD prompt)
Type in the following without the quotes: "fastboot devices" (you should then see a device listed)
Type in the following without the quotes: "fastboot flash recovery recovery.img" (flashes the factory recovery image)
Type in the following without the quotes: "fastboot flash system system.img" (flashes the factory system image, may take a while to flash)
Type in the following without the quotes: "fastboot flash boot boot.img" (flashes the factory boot image)
5. Once those 3 images have been flashed, you should have seen a message that says "OKAY" after each one. You should be fine as long as you do not have any red error messages on your tablet.
Type in the following without the quotes: "fastboot reboot" (reboots device normally)
6. If all goes well, it should now boot to the Asus screen and then go to the ATT screen. If so, it will stay on the ATT screen for a while, just wait it out. Mine took about 12-15 minutes and then it opened to the new setup screen to set the tablet up as if its new!
This is how I was able to recover my bricked tablet, hopefully it can help someone else that may run into this.
John, thank you for the write-up. Just bought my ME375CL with 4.4.4.4.
When I try to flash the recovery partition, I get the following error:
C:\Users\Myself\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11312 KB)...
OKAY [ 1.047s]
writing 'recovery'...
(bootloader) Official image.
FAILED (remote: flash_cmds error!
)
finished. total time: 2.344s
Click to expand...
Click to collapse
and on the tablet's screen:
FASTBOOT CMD WAITING...
RECEIVE DATA...
E:recovery flash failed!
FLASH FAILED!
RESULT: FAIL(flash_cmds error! )
Click to expand...
Click to collapse
I haven't tried the other commands for system.img or boot.img as I don't want to do anything out of order from the write-up. Ever run into this?
The firmware in the download is 5.1.1, not 4.4.4. That is probably the issue. If you are running good on that, I would try rooting it instead. If you are just wanting to upgrade, you will need to have an active AT&T SIM in the tablet to upgrade over the air. I am not sure if there is a flashable upgrade or not somewhere.
Oh ok John. I misread the title of the thread. I thought it was for updating from 4 to 5.
Quick question then: Is it possible, using the adb / fastboot tools, to backup the current 4.4.4.4 before I allow the tablet to update to Lollipop? After reading around, I understand that Lollipop can't be rooted but I have no real concern for it. But just in case I need the tablet to do something else in the future, I'd like to be able to return it to kit kat to be able to root.
Once you upgrade to lollipop, there is no downgrading for this tablet. There really is not much development for this device. I have kind of been working on a lollipop root when I can. Between my limited time and knowledge of android, I can't promise anything.
Overcoming red messages?
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Gor- said:
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Click to expand...
Click to collapse
Sounds odd that it did 2 out of 3 flashes. After you flashed those and rebooted, are you still on KitKat or did it actually update to Lollipop (5.1)? I ask because I assume the system image that flashed would be the operating system.
I still want to stress that this post is for recovering a bricked tablet that will not boot at all. I would not suggest using this as a flashing upgrade as I do not know if it will truly work. If you are still on KK (even after flashing) you could try installing the Asus Flash Tool and use the raw firmware that you downloaded and try it that way. It did not work for me so that is why I used fastboot. It might work for you.
Here is a link for the Asus Flash Tool:
https://drive.google.com/open?id=0B0fKccJIuWsndXJUa1FEbXVzTjA
johnkirchner said:
Sounds odd that it did 2 out of 3 flashes. After you flashed those and rebooted, are you still on KitKat or did it actually update to Lollipop (5.1)? I ask because I assume the system image that flashed would be the operating system.
I still want to stress that this post is for recovering a bricked tablet that will not boot at all. I would not suggest using this as a flashing upgrade as I do not know if it will truly work. If you are still on KK (even after flashing) you could try installing the Asus Flash Tool and use the raw firmware that you downloaded and try it that way. It did not work for me so that is why I used fastboot. It might work for you.
Here is a link for the Asus Flash Tool: ]
Click to expand...
Click to collapse
As a follow up on your question above, Tab restart stalled at a screen (after the Asus logo), presenting some options to do recovery, reboot, factory reset, etc. (factory reset did not help), and red error messages at bottom.
To the GOOD news for anyone interested. I used the Asus Flash Tool and the firmware zip for 5.1.1 (many thanks for the advice).
Note: Tool did not install correctly on Win10 pc, citing error in installing some devcon.exe or similar file (guess that may be a firewall/antivirus issue).
Flash tool took some 15 or so mins unzipping firmware, after which I saw some action on the tab. Another 15 mins, and it rebooted to the At&t logo, stayed here for another 15 mins and unraveled a whole new device on Android 5.1
Glad to hear it worked for you and that I guess you can use this to flash upgrade from kitkat!
There is working way to root our device on lollipop! It is for the other Asus model, but it works for our
http://4pda.ru/forum/index.php?s=&showtopic=640814&view=findpost&p=53047686
I will check this out!
The root works, installed without any issues and verified with a root checker!
Here is a direct download from my Drive folder: https://drive.google.com/open?id=0B0fKccJIuWsnN21ZbnZpc2F6b1E
1. Download the file above.
2. Extract the zip contents.
3. Plug your ME375CL tablet in to pc via usb cable.
4. Make sure you have enabled Developer Mode and allowed USB Debugging first!
5. Open the folder you extracted and double click the "Root-One-Click.cmd" file.
6. It should reboot to fastboot mode and flash the needed files and then reboot again.
You should now have root access. Verify this by installing a root checker app from the play store. Keep in mind, it may say root not installed on the first run. Sometimes it will take a moment for superuser to initially run or prompt for access.
Side note: the root uninstall did not seem to work, got an error...but oh well, the point is to have root!
Thanks go to @little_pindos for finding this file...you are a rockstar!
Anyone get xposed on LP?
ATT Boot Up Sound
Tired of the ATT boot sound? If you used the rooting method above, then you can get rid of the annoying ATT startup sound by doing the following:
1. Install a Root Browser app (I recommend Rom Toolbox Pro, it has a built in file manager)
2. Navigate to the following path:
root/system/media
3. Find the file named "powerup.wav"
4. Simply rename the file by adding .bak to the end (ex - powerup.wav.bak)
5. Make sure it took the name change (some file managers have issues with that)
6. Reboot and see if it got rid of the sound!
You can also use your own startup sounds as long as they are in a .wav format, I believe. Make sure that the name of the file is powerup.wav.
You can also change your boot animation with "boot animation" app.
Best tweak IMO is adding "ro.config.low_ram=true" to build prop, or installing the low ram device xposed module if we can get it to work (both do the same thing). You gain about 100mb more free RAM on average.
TimmyP said:
You can also change your boot animation with "boot animation" app.
Best tweak IMO is adding "ro.config.low_ram=true" to build prop, or installing the low ram device xposed module if we can get it to work (both do the same thing). You gain about 100mb more free RAM on average.
Click to expand...
Click to collapse
I'll have to try that!
AT&T no longer has updates in system for this tablet
Gor- said:
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Click to expand...
Click to collapse
AT&T removed the last update for this tablet months ago and no longer supports it. ASUS states AT&T has all the updates. Total cluster.

[Guide] Get out of Qualcomm Crashdump Mode for Android 11

Before you start, make sure to put all of the files that you need in the same folder as your adb.exe and fastboot.exe because it will make things easier when you have to fastboot files to your phone. Make sure to follow the directions from the original developers of the tools below. Also, in the windows file explorer, right click on the "Name" tab, in the pop up click "More," select "Path," and also select "Folder Path," then click "Okay." This will make it easier to find the file path name if you need it when you are flashing a specific file to your phone using ADB.
Once you navigate to your android fastboot/adb folder, at the top of your file explorer, click in the address bar, this will highlight the text blue in the address bar, delete the text in the address bar, type CMD and then press enter. The adb/fastboot command window will pop up and be ready for you to use. You may as well leave that command window, the MSM tool, credits: Lucifer6: https://forum.xda-developers.com/t/msm-tool-guac-for-all.3934691/ and the Tool all in One, credits: mauronofrio: https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/ , https://toolaio.tk/ open in case one of these tools decides to bite you in the brain so hard your phone melts into booting itself properly.
You'll be needing this Twrp.img from this post if you're on android 11 like I am, credits: Nebrassy:
https://forum.xda-developers.com/t/recovery-11-unofficial-teamwin-recovery-project.4289455/
And Magisk, credit: topjohnwu, which can be downloaded from Step 1 in this article https://www.xda-developers.com/how-to-install-magisk/
Credit: Sumukh for the article (code word the instructions in this article are for a different breed of TWRP then the one needed for rooting android 11 OnePlus 7 Pro, so please after booting into TWRP go to "Advanced," then in the list click "Flash Current TWRP," then reboot straight back to TWRP, flash Magisk, then reboot straight back to TWRP, then flash Magisk again, and then reboot the system ((if possible at this time)) or you'll have boot loops for breakfast), credits: topjohnwu for Magisk
And the android 11 stock rom of your oneplus 7 pro which can be found here, credit OPTeam: https://forum.xda-developers.com/t/...a-oxygen-os-repo-of-oxygen-os-builds.3930585/
I wasn't able to use MSM Tool by Lucifer6 because my phone didn't want to be recognized by my computer and I am not sure the files exist for android 11 to work with the MSM Tool, but if they do exist or there is a way to use the android 11 zip with the MSM Tool, please someone post it with detailed instructions so that everyone can find it.
I couldn't get the Tool All in One to work because I don't know, however, there are important files in mauronofrio's zip file in this post: https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/ Grab the zip file from the link next to "All Roms on AFH." This can help get your phone back from the nightmare of the qualcomm crashdump scenario. If you are on android 11, do not flash the images in this zip folder because the zips in this post are for android 10 and I don't think you can downgrade. There are more directions about this in number 3 of this post.
If at any point you are able to boot your phone into the system, DO NOT put a password, fingerprints, facelock, swipe pattern, nudey collage on your phone to lock it up until AFTER you are sure you are completely done using TWRP, because Nebrassy's TWRP, as far as I know, is not supposed to be able to decrypt the phone once it has a nudey papier-mâché password on it. So, once you put a password on your phone, you may not be able to use TWRP again unless you like pain.
And yes, I did try, in the past week to clean install my rom, made sure to not create a password, flash TWRP and magisk, make a password for the phone, realized I needed to do something else in TWRP, deleted my papier-mâché password and the fingerprints to go along with and then try to get back into TWRP. It's really a hit or miss. You may get back in, you may end up flashing something only for it to get stuck in a TWRP booting boot loop like I did.
It's risky. Take off your password to your phone, then TWRP it up, say your goodbyes to TWRP and then finish setting up your phone with a password. Also, you may have to try plugging the OEM charging cable into different USB ports on your computer at specifically any time.
There are three different recipes that I tried to get my phone to work again after crash dumping. Any one of these could help. For me, it took doing all three, trial and error and error and error for my phone to get booted and rooted after the crash dump so you can try doing the easiest looking ones first, which are number 1 and number 2, see if that works, and then move on to the harder one.
Read all three recipes first before you try anything because some things from number two you can use in one or three. You're in for a real one right now so relax and get comfy. Take your time and make sure you follow the directions in the original posts by the developers because it will waste less of your time if you make sure you extract everything and other scientific ratchet. And you'll make less of a mess of your phone than it already is.
It's bricked, not dead. Hopefully. Hopefully, it's not dead. And I'm not much for hope nor am I much for being blamed if your phone slips into an endless hell pit, it contacts a plane's black box and directs said plane to land onto your roof, or some other maniacal nonsense backwater dribble okay let's get started.
1.) Easy: I used a combination of movements buttons including power off and volume down, only volume up and volume down which did other things, and power off and volume up. At first, none of these movements buttons would take me to fastboot mode. It would just keep rebooting to qualcomm crashdump mode no matter what.
Flustered, red, breathing hard because I don't walk enough, I tried these movements buttons again and again and again and again and not always in the order I wrote them down. I kept trying until I saw some Chinese writing.
Choose the first option even if you can't read the text. Guess where the "Okay" (bottom right) is and click it. The text--the first option--is highlighted in blue, which I should have said in the first place. Hopefully after twitching that phone for a good 30-45 minutes or more depending on how long you like crying, it will finally boot into fastboot mode. Plug the phone to the windows, fastboot boot the twrp.img from Nebrassy in the CMD window. If you are still trying to root, grab a usb or an external hard drive that has the rom zip and the latest magisk.apk that you need for your phone (directions below). If you are not trying to root, grab a usb or an external hard drive that has the rom zip and just flash the rom and that's it (directions below).
Plug the USB storage into your phone. On twrp go to "Mount," click the checkbox next to "USB Storage," click "Select Storage," then in the pop up click the circle next to your USB or external hard drive or whatever you're using. Go to "Install," select the zip of the rom on your USB Storage, click "Install."
You can then flash twrp afterwards by going back in the past and selecting to have TWRP flashed automatically after a rom installation; it's in the options. Or by going to "Advanced," then click "Flash Current TWRP" (mind you this is for the Oneplus 7 Pro using the TWRP 3.5.2_11-Nebrassy image in October of 2021, so if you're reading this and have a different phone or you're from the future, please, don't laugh at me if the current way of flashing TWRP is outdated by the time you read this).
Then you must flash magisk, reboot to TWRP recovery, and then flash magisk again or else the phone won't boot. After flashing magisk that second time, you may reboot the system. Once you get past those sussy terms and voluntary agreements, magisk will look like an android 1 icon. Click it.
The phone will ask you for your hand in marriage by asking if you are truly ready to jump off the deep end by allowing magisk to install unknown apps. Click I do, and magisk will install. Then, magisk will ask you to install the other half of itself, and again, make that app yo baby momma by saying yes, yes, yes. And now you have a new phone with none of your old life to spy on you and tell you how good you weren't in the past or whatever.
3.) Not so easy, but manageable. Caution, read slowly: Another thing I did try was to flash all of the images in the stock rom zip. You can download the correct rom for your phone in this post, credit OPTeam: https://forum.xda-developers.com/t/...a-oxygen-os-repo-of-oxygen-os-builds.3930585/ ,search the googles, or use the OEM website. Then, use the payload dumper method from here: credits to djsubterrain
https://forum.xda-developers.com/t/...ot-image-and-apply-root-to-the-phone.4263811/
After I djsubterrained my payload, all of this sounding unnecessarily dirty, I put it in this other thing that I tried (directions below): credits to mauronofrio
https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/
I downloaded the zip file from the above post in the link next to "All roms on AFH." Extract it. Once I did the dump on my payload, I took all of the extracted images from the "payload_output" folder, put them in a new folder inside of mauronofrio's extracted zip folder, named that new folder "images," and just renamed the original "images" folder that was in the zip file to something else.
In mauronofrio's extracted zip folder, I copied the file named "flash-all-partitions-fastboot.bat" from the "Others_flashall" folder and pasted it into my new "images" folder. I double clicked on the "flash-all-partitions-fastboot.bat" file. An alluring window opened and I typed "Y" for yasss and then clicked "Enter."
And then that flashed most of the images to the phone. Not all of the images flashed. Some of them said "failed," but the important ones like the system.img and boot.img, among others, flashed successfully. I have no idea if using that specific ".bat" file was the right one for my situation because I wasn't sure if I was wearing comfy enough pants to be seen by the oracle.
After that, I did the the whole fastboot boot to TWRP and flashed the zip rom over again using my USB storage because it was easier for me to do that than to figure out how to adb sideload when the adb sideload button in TWRP wasn't working and while I was crash dumping for qualcomm, my phone refused to be recognized by the Tool All In One and the MSM Tool. Then I flashed TWRP, then I flashed magisk, rebooted to recovery, flashed magisk again, and then I tried to reboot to the system. But my phone booted back to twrp, a lot, a lot of times before the end of this story.
2.) Also easy: I think from TRWP (or you can use the power and volume buttons mantra from number one) I clicked on reboot the bootloader from fastboot mode. I used the up and down volume buttons to select "Bootloader" or "Start" (do both until the "Boot Reason" screen shows up for you).
For whatever reason I clicked "Boot Reason" and the reason was something made up like fs_mgr_mount_all. I clicked "Next" at the bottom of the screen and it asked me to wipe everything like music and photos which I already thought were long gone. But I have a backup of my music and my photos so no big deal.
I clicked on "wipe all data," and my phone finally booted back up into the OS. I went through the completely voluntary terms and conditions and voluntarily, completely voluntarily, and no one else is here with me, agreed to the voluntary terms and conditions. And then I clicked on the android 1 icon for magisk and...
At some point in time I formatted the system using TWRP after flashing the zips and the stuffs and now even though my phone says encrypted, the first time I booted back to twrp after finishing setting up my phone and putting a password on it, TWRP said that it decrypted USER 0 after putting my password into TWRP. I have no idea how it happened.
Nebrassy's TWRP is not supposed to be able to do that for android 11 as far as I know. About 30 mins later I booted back to TWRP just to see what would happen, and sure enough it took my password and decrypted my phone. Even though I am on android 11, rooted with a TWRP that is not supposed to be able to decrypt USER 0. I don't know how. Maybe I'll try to upload a log file so that can be figured out, or maybe by now it has already been figured out. Don't know.
So, that was fun, I hope you were able to get out of the crashdump by any of the means used here or not here. If you were able to get out of the qualcomm crashdump some other way or have advice on how any of the recipes could have been cooked better please post it in a forum or in this thread or sector B.92-80 of space so that no one ever comes close to using the very last tears their body has to offer.
I'm sorry if I forgot to give credit to anyone but at this point you'll have to flash me into recovery to get it. Or just say "I belong in here too," and post a link to your something helpful.

Categories

Resources