Related
Buddies,
can anyone upload the original roms for Milestone XT720? (SG, Kr, and other)
So we can do more testing worry free. If anything goes wrong, we can just flash it back to original. It would be nicer if someone can also show how to flash the rom.
------- Edit ---------
Flashing Guide by Hahutzy
Hahutzy said:
Alright, I just crashed my phone into an infinite FC loop by messing with system/app, so a reflash was in order.
Here's how I successfully flashed it back to stock using Windows 7 32bit (dense text ahead):
1) Search somewhere along the lines of "RSDLite - download here" on google
2) Go inside first link, download the file that's named somewhere along the lines of "RSDLite_4.5.3.zip"
3) Install it.
4) Go to http://and-developers.com/sbf:xt720
5) Download the 2nd Full Flash rom, the one where the provider is "Southeast Asia"
6) Unzip that file, you now have a .sbf folder (not file)
7) Put that .sbf folder in C:\Users\Admin\My Documents
8) Shut down phone, take out battery
9) Hold Power + Volume Down + Camera buttons all at once
10) Put in the battery while holding those buttons
11) Phone is now in bootloader mode (screen looks like a command prompt)
12) Release the buttons, and plug USB to computer and phone
13) Open RSD Lite, your phone should be detected as connected (Device name was like "S OMAP 3440" or some BS like that)
14) Click "..." to browse for the .sbf file in C:\Users\Admin\My Documents
15) In RSD Lite, click to highlight your connected XT720, and then click "Start". The first column beside the connected phone should now have a green icon thing, and the ROM is being flashed.
16) DO NOT TOUCH YOUR PHONE, THE CABLE, OR THE COMPUTER! (I went and took a dump)
17) When the "Status" column in RSD Lite says "Please manually power up this phone", so shut it down and power it again. Note: The status stays in "Checksum Group 37" for a verrrrryyyy long time before saying "Rebooting". I thought it got stuck there, but it ended up ok.
18) Your XT720 is now reflashed to stock.
19) You can now close RSD Lite. It will complain saying you will damage the attached device, but I pulled it out wayyyy before this (I unhooked it when it told me to reboot manually) and my XT720 is not dead. You may choose to close RSD Lite before unhooking your XT720.
20) Post your results in this thread and confirm or reject my procedure.
spiderx_mm, you may quote this on your first post for others' easy access to this procedure if you so wish to.
Click to expand...
Click to collapse
I agree on this, i need a EU rom.
i am using an SG xt720. is there anyway to dump the rom?
@mariomsg1, i remember u have reflashed ur rom once before right? may i know where did u get the sg starhub rom last time? could u share it please. thanks
http://and-developers.com/sbf:xt720
xt720 said:
http://and-developers.com/sbf:xt720
Click to expand...
Click to collapse
yes, that is
there latest ROM is STR_U2_01.18.2
mine is STR_U2_02.18.3 (bought unlocked retail version from expansys europe)
anybody got same unrooted ROM? Mine has problems, I am stuck with ROOT which stopped working after couple of days, and now I can neither un-root, nor root again.
mariomsg1 said:
I agree on this, i need a EU rom.
Click to expand...
Click to collapse
can u share a step-by-step flash guide?
U can flash with RSDlite. just need a sbf file.
okie. any version do u recommend? or shall i just use the latest version?
Yes
Sent from my Milestone XT720
Sorry, can i know how to put the phone into bootloader mode? I cant not find in google and this forum for xt720.
press volume and power together
can not go to boot loader. Already press power and volume button
first you need to switch off the phone, then press camera button and power and keep those pressed until recovery icon appears. THEN press volume up and power, if I remember this correctly.
solnyshok said:
first you need to switch off the phone, then press camera button and power and keep those pressed until recovery icon appears. THEN press volume up and power, if I remember this correctly.
Click to expand...
Click to collapse
press play button and power, then press volume up and camera button
play button = small button next to the camera shutter
please help
When i do the guide, phone at first go to recovery mode, and nothing happen. RSD lite can not recognize the phone. I use recovery mode to wipe cache and data like it said factory reset. Then i get stuck. Phone can not start up, stand at motorola logo.
I still can go to recovery mode, but not boot loader mode. And it appear error in recovery mode: E:\ can't open /cache/recovery/command. Now how can i repair my phone?
flash sbf file with rsd lite on bootloader mode
Sorry i cannot put the phone to bootloader mode. It get stuck at recovery mode when i press vol up and camera. And computer did not regconize the phone also. I guess that i still missed the way to go to boot loader. Can you please do a step by step guide? What kind of windows you use?
mariomsg1 said:
flash sbf file with rsd lite on bootloader mode
Click to expand...
Click to collapse
civi309 said:
Sorry i cannot put the phone to bootloader mode. It get stuck at recovery mode when i press vol up and camera. And computer did not regconize the phone also. I guess that i still missed the way to go to boot loader. Can you please do a step by step guide? What kind of windows you use?
Click to expand...
Click to collapse
go to flashing mode directly by pressing volume up+camera button+power button. after that just flash the sbf in provided the windows can see ur phone. make sure u also install the required driver
First of all thanks for not caring. I spend days on Internet trying to find a solution. I have Blade which I bricked thanks to my noob skills with flashing and similiar ****. I just want my normal phone back. Couldn't give a **** bout roms anymore. Sorry for the lang but Im mad. When I boot it up it just sits there on green android logo not going past. I can enter download mode if it matters. As soon as I back it up Im getting rid of cwm mode and bull****. I use my sister phone to transfer files on my sd card. I cant enter my recovery mode since I installed that **** of cwm.When I try the key combo-android logo stuck with red light on. My phone has 90-100% battery Im sure. I need a solution where I can do something from pc with download mode or something that will automatecly start when I boot up my phone that I transfered on my SD card. Please guys let me have some sleep. I've been staying all night long just to unbrick it. Dont mention any flashing rooting ****ing...I developed alergy to those words. I want it simple ..please...any help is appreciated. And sorry for my language.
Solution.
I Love The Register Video said:
First of all thanks for not caring. I spend days on Internet trying to find a solution. I have Blade which I bricked thanks to my noob skills with flashing and similiar ****. I just want my normal phone back. Couldn't give a **** bout roms anymore. Sorry for the lang but Im mad. When I boot it up it just sits there on green android logo not going past. I can enter download mode if it matters. As soon as I back it up Im getting rid of cwm mode and bull****. I use my sister phone to transfer files on my sd card. I cant enter my recovery mode since I installed that **** of cwm.When I try the key combo-android logo stuck with red light on. My phone has 90-100% battery Im sure. I need a solution where I can do something from pc with download mode or something that will automatecly start when I boot up my phone that I transfered on my SD card. Please guys let me have some sleep. I've been staying all night long just to unbrick it. Dont mention any flashing rooting ****ing...I developed alergy to those words. I want it simple ..please...any help is appreciated. And sorry for my language.
Click to expand...
Click to collapse
Calm down dude. If you can get in Download Mode , you are lucky. I even know people who had not get to Download Mode and had began to cry , cause the phones were only 3-4 Weeks old. Back to your problem.]First download here the stock rom.[/URL]
Then you need the Android SDK and the platform-tools from Google , so download it , cause you need ADB. Click here to get Android SDK.Then you need the ZTE drivers. Click here to get the drivers.Now get into download mode and connect the device via USB to your PC. Copy the boot.img (or recovery.img if it is in the ZIP package) and flash it via Fastboot (command: fastboot recovery.img) . Now you got the stock recovery. Now push the FULL update.zip at your sdcard , and now go to recovery , and update from sdcard , choose the update.zip ... Flashing takes a while. DO NOT WIPE ANYTHING BEFORE OR AFTER CHOOSING "UPDATE.ZIP" . Now your Phone should fully works normally
Hello, I have also bricked ZTE BLADE 3(I flashed a wrong kernel....). It only turns the red light on when i turn it on and blank screen, does not respond to vol + and vol - key, no android logo, but when I connect it to the computer via usb in Device Manager a COM port opens with the name ZTE DFU(Diagnostic interface). If anyone has experience of reviving this device from this mess? Thank you for your time
Zmaj5 said:
Hello, I have also bricked ZTE BLADE 3(I flashed a wrong kernel....). It only turns the red light on when i turn it on and blank screen, does not respond to vol + and vol - key, no android logo, but when I connect it to the computer via usb in Device Manager a COM port opens with the name ZTE DFU(Diagnostic interface). If anyone has experience of reviving this device from this mess? Thank you for your time
Click to expand...
Click to collapse
Your download screen is destroyed , but you are still able to get into it.
Try to get into it and flash the kernel with fastboot , the screen will bug during fastboot procedure.
My screen is completely blank and black, just the red light showing when i turn it on and it is always on. It does not respond on power button + vol. down, power button + vol. up, power button + vol. down + vol. up. When I connect it to the computer it does not show me a usb flash drive although I have the zte drivers installed and another sd card inside, but in Device Manager I can see it as a COM port(DFU) Diagnostic Interface. I tried accessing the bootloader via adb but it doesnt even list it with command "adb devices". I also tried flashing the recovery image via "fastboot recovery recovery.img" and "fastboot recovery.img" and still no luck, it just hangs at "waiting for device"...
Zmaj5 said:
My screen is completely blank and black, just the red light showing when i turn it on and it is always on. It does not respond on power button + vol. down, power button + vol. up, power button + vol. down + vol. up. When I connect it to the computer it does not show me a usb flash drive although I have the zte drivers installed and another sd card inside, but in Device Manager I can see it as a COM port(DFU) Diagnostic Interface. I tried accessing the bootloader via adb but it doesnt even list it with command "adb devices". I also tried flashing the recovery image via "fastboot recovery recovery.img" and "fastboot recovery.img" and still no luck, it just hangs at "waiting for device"...
Click to expand...
Click to collapse
When the red light still comes up , you still got chances to get it fixed...
I think so too.. but how? The only method left is JTAG... I saw a thread about using a TPT image to flash low level firmware using ZTEflash.exe but that thread was for ZTE Skate I think, I could not find the tpt.img file for zte blade 3.... Is there any other method via usb cable? Or send it to the shop?
Well, here is my situation:
Got a BLADE III Pro
Tried to root it and i played with few tools found on xda and other places (android forums). No luck at all. Tried to flash a CWM and NO LUCK neither. Tried to go back to flash stock CWM (as i was afraid of bricking it), searched for stock cwm and there is my BRICKED phone. When trying to hold volume down and power botton (both for over 20 seconds even) it will show a green android and its stuck there for hours. When trying to go to fast boot mode the same happens (with volume up and power botton).
While trying these two options the PC (Windows 7 64 bit) wont recognize the phone pluged in.
The only way the PC makes a sound is when i hold both volume up and down bottons and power it or plug it in the PC (without the battery even).
I need to know how can i fix it to boot only. PLEASE. Is this a "throw on can" phone now or it can be brought to life? PLEASE TELL ME PEOPLE.
pm me or any info as soon as you guys can.
I will respond to any question you might have.
Thank you in advance.
I have sent my phone to the shop and they said that they would need a jtag box specific for this model or a new motherboard for zte blade 3.... I think this the end for my zte blade 3
I went through a lot of searching and trouble to install CM11 on my Xperia Tablet Z, and I'd like to share a tutorial I made for anyone who is also wanting to accomplish this.
All links are in Dark Green because I cannot post links yet.
1. Download and extract the ADB+Fastboot+Drivers zip (alexpja.com/sony/adb-fastboot-win.zip)
2. Now we’ll unlock the bootloader.
a. If you do not have a Phone app (like I don’t on the SGP351), you can either get the IMEI from About -> Status in the settings OR you can find the IMEI right after the IC code, nearby the barcode on the bottom of the tablet.
b. If you do have a Phone app, enter *#06# to retrieve the IMEI.
c. Save this for later use.3. Place the tablet into fastboot mode and connect it to the computer.
a. Power off the device
b. Connect USB to computer
c. While plugging in the other side of the USB cable into the tablet, hold down the Vol + button.
d. If your speakers are on, you should a sound.
e. We have to install the drivers for fastboot. Open devmgmt.msc via the Run window or in the Start menu and in Other Devices section, you should see S1 Service or S1 Fastboot (anything containing S1).
i. If it is showing a yellow exclamation mark: Follow 3.e.i.1. If it is not, continue to 3.f.
1. We need to download Flashtool and use the driver setup. Download Flashtool (unrestrict.li/flashtool) and install it.
2. Find cmd.exe, right click it, and select Run as administrator.
a. Type in
Code:
bcdedit /set testsigning on
and press enter.
b. Reboot your computer.3. Once you have rebooted the computer, open the folder where you installed Flashtool (default: C:\Flashtool).
4. Open up the drivers folder and open Flashtool-drivers.exe.
5. Select the first two driver choices (Flashmode and Fastboot) and select “Xperia Tablet Z Drivers” and continue.
6. A new window will appear, continue on with that.
7. A window like this may appear a few times, just press Install this driver software anyway.
8. Run 3.e.2. again and run
Code:
bcdedit /set testsigning off
. Reboot your PC now or after the tutorial.f. The LED pulse light above it should be emitting a blue-ish color. The screen will be dark.4. Now we’ll verify if you have fastboot running.
a. Open the tools folder that was extracted from the ADB ZIP and double-click on START.cmd to open Command Prompt in the current directory (all it does is literally open cmd.exe, you can edit the script to verify).
b. Run the command
Code:
fastboot -i 0x0fce getvar version
. If you get
Code:
<waiting for device>
, then you did something wrong. Retrace your steps! (For example, I get
Code:
version: 0.5
)5. Go to (unlockbootloader.sonymobile.com) and continue until you reach the screen where you put type in the IMEI and an email address. Type in the first 14 digits of the IMEI (remove the last one) and your email address (not sure if name is required). You should get an email instantly with the key.
6. In the Command Prompt, run
Code:
fastboot -i 0x0fce oem unlock 0xKEY
where KEY is the key you received in the email from Sony.
7. Download whatever release you would like to use on the tablet (I’m using CM 11 nightly) from (download.cyanogenmod.org/?device=pollux)
a. Optional: Also download gapps for Google apps such as Gmail, Google Play Services, etc. (wiki.cyanogenmod.org/w/Google_Apps)8. Extract the ZIP file (but don’t delete it either) and copy boot.img to the tools folder.
9. If your device is still turned off, turn it on and enable USB storage mode. Copy the CM zip to either the internal storage (sdcard) or, if one is inserted, the microSD card (sdcard1).
10. Place it into fastboot mode again (#3).
11. Go back into the Command Prompt and enter:
a.
Code:
fastboot -i 0xfce flash boot boot.img
b.
Code:
fastboot -i 0xfce reboot
c. Enter recovery.
1. Once it shuts down, rapidly tap the Vol + button in order to get into the recovery.
2. Grep_The_Truth's tip: Look at the LED. It will turn orange and afterwards it'll turn purple. You want to press Vol+ as soon as it changes colors.12. Select “wipe data/factory reset” and wipe it. Afterwards, go back to main menu.
13. Select “Install zip” and either select “Choose zip from /sdcard” (internal storage) or “Choose zip from /storage/sdcard1” (microSD card).
I’ve had varying experience with installing from the /sdcard because sometimes it doesn’t want to mount /data while wiping (/data/media which is /sdcard is safe in wipe) the tablet, so if you were to install the zip from /sdcard with the error present, it would screw things up. I prefer the microSD card route (/storage/sdcard1), and you don’t even need a big one. 512MB works just fine. The actual path would be /sdcard/0/ when looking for the cm.zip in the internal storage.
14. When you have chosen to install from either /sdcard or /storage/sdcard1, select the cm.zip and install it.
a. If you downloaded gapps.zip, install it the same way as you did with the cm.zip.15. Go back to the main menu now and select “reboot system now”
a. Once, I had the option to install root access before rebooting, I declined (was planning on rooting after tutorial) but it gave me root anyway.
That’s it! You can now use CyanogenMod with the Sony Xperia Tablet Z.
Getting in to recopvery
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
c. Once it shuts down, rapidly tap the
Code:
Vol +
button in order to get into the recovery.
Click to expand...
Click to collapse
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.
Grep_The_Truth said:
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.
Click to expand...
Click to collapse
I'll add it along with mine, because I can do it with no problem.
alexpja said:
I'll add it along with mine, because I can do it with no problem.
Click to expand...
Click to collapse
alexpja Thanks for your tutorial, this is very detailed and easy to follow.
my Xperia is SGP321.
I put it into practice and the results it gives me the "oem unlock" is:
FAILED: (remote: Command nor allowed).
I guess you should treat my tablet has the bootloader locked and not allowed (for now??) the unlocked.
I hope someone gives us the opportunity to unlock the devices and in the future can be unlocked.
I had the same experience where at times the steps were a little confusing, especially for a beginner. Each set of instructions would either leave something out or skim over it as if everyone already knew it. That's understandable since they were probably written for that audience. I soft-bricked my SGP311 at least 10 times.
I was even going to write something like this but I got lazy.
One suggestion I would offer is to request the bootloader unlock key first since it sometimes takes a little while and a person can reduce the possibility of having to stop and wait just when they are making progress.
And for anyone going this route for the first time, don't make my mistake - flash exactly what the instructions say to flash, particularly boot.img. Once you have that recovery flashed you have a lot more control over your device. If something goes wrong in a following step like getting boot loops you can still fix it. But if you get annoyed and start poking at it then you can mess up the recovery. Then you have to reset everything to stock and just about start over.
While I don't want to say something stupid like claiming the tablet is indestructible, I found that whether I got stuck in a boot loop I couldn't get out of or screwed it up so bad that all I could get from the tablet was an occasional LED flash, I could always restore it using Emma. It's annoying to have to start all over but it's a huge relief when it boots normally.
for me flashing was fine and without any error but my Tab doesn't boot up with CM flashed...any idea?
Hanging at reboot
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.
Guess my bootloader won't be unlocked. This is A lot of work. Good job on the write up though maybe one day I'll tackle it.
BOOT LOOP Step 9
All was going well, but step 9 powering on device, now its looping.....Ill use flash tools to put jelly bean on and try again, since i was trying with kitkat...why i suspect kitkat is the issue, before i used to be able to unlock and lock boot-loader with jelly bean but with kitkat it didn't work, which i then forced it via cmd
No GPS
I used the tutorial for my Pollux Windy (WiFi Only) and used the latest nightly. everything went well but my GPS is now broken. Is this a known issue?
kevinsickles said:
Is this a known issue?
Click to expand...
Click to collapse
yep! use search to find out more.
mulebreath said:
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.
Click to expand...
Click to collapse
Hi,
I've been trying with my Xperia Tablet Z Wi-Fi SGP311. Ran into the same problem. On reboot command the LED was stuck on red for 10 minutes and the cmd window was still open. I unplugged the USB and the LED would not turn off. Tried some things, I don't remember specifically what, but it got the LED to turn off. Now my device can't be detected. I've downloaded Emma and it is not recognising my tablet. I've tried to plug the USB in while hold Vol +, Vol -, and the Power button. No detection for any. All I can do with my tablet is make the LED flash white, purple and red in rapid succession by holding Vol + and Power for 5 seconds.
Anyone know what's happened? I suspect I've completely bricked it :L
EDIT: Apparently there are different modes which you can cycle through. If you hold down Vol + and Power for 5 seconds, the LED will flash according to which mode the tablet is in. The different modes give these flashes:
- 1 White flash
- 3 Rapid which flashes
- A white, purple and red flash in quick succession
To switch between the modes, I hold down Vol+ and Power, and after 5 seconds it will take around 3 more seconds to change modes. One of these modes will not appear unless plugged into a PC. What do these mean and can I do anything with it? Tablet is still bricked.
EDIT2: I've managed to get Emma to recognise my tablet. Turns out the modes do have different purposes. I should be fine now, problem solved. I will just leave the solution here in case anyone runs into the same problem.
Unplug your device and hold Vol + and Power for 10 seconds. At the 5 second mark your LED should flash white ONCE. Keep both buttons held and within 5 more seconds, your LED will flash white THREE times consecutively. This will allow you to enter Flashmode (plug in USB while holding Vol -) and Fastboot (plug in USB while holding Vol +). For Emma to recognise your device, enter Flashmode and you can restore and try again.
Bootloop
I've tried many times to flash cyanogenmod onto my Xperia Tablet Z (SGP311). This is a Wi-Fi only tablet and I have downloaded the versions of CM from (download.cyanogenmod.org/?device=pollux_windy) I've followed all of the steps and tried all of the versions of CM down to 10.2 (I used GApps10.2 for CM10.2). Each version gets stuck in bootloop. I've cleared all data (in CWM - wipe data/factory reset, wipe cache partition, wipe delvik cache) before flashing CM and GApps; however, when I try to clear data I get an error. This is what the tablet says:
-- Wiping Data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cacha
Formatting /sd-ext...
Formatting /sdcard/.android_secure!
Skiiping format...
Data wipe complete.
Click to expand...
Click to collapse
I'm thinking the "Error mounting /data" is the problem, but I'm not entirely sure, nor am I sure of how to fix it.
Any suggestions?
EDIT: Turns out I'm just really bad with Android stuff. I ended up flashing the original Xperia software, unlocking the bootloader (according to this tutorial's instructions), then I downgraded to 4.1.2, rooted my tablet (forum.xda-developers.com/showpost.php?p=53063218&postcount=14) and installed the PhilZ and TWRP custom recoveries. I didn't get to use them in the end. For some reason CWM kept coming up no matter what combination of buttons I pressed while rebooting. After downgrading and rebooting, I followed the rest of the instructions on this tutorial (from step 7). This time I got no errors while cleaning the disk, cache and delvik cache. Flashed the zip files, rebooted the device and voila, Cyanogenmod11!
Again, I'll leave this edit here in case someone runs into a similar problem. I couldn't get any version of CM until I rooted first.
I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!
tp_88 said:
I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!
Click to expand...
Click to collapse
download a proper stock (not bricked) firmware for your device and flash with flashtool.
Rootk1t said:
download a proper stock (not bricked) firmware for your device and flash with flashtool.
Click to expand...
Click to collapse
What makes you think that the stock firmwares I've tried are bricked? I've since my post tried one which I downloaded through Flashtool - same result.
Hi,
I'm not very experienced with those root things and followed a tutorial to do so.
I unlocked the bootloader, had TWRP installed and root. This worked. Now I wanted to remove Root and TWRP and go back to the original state. I couldn't find the stock recovery file, so I installed the P996A04V1.3.0B13_MR2_sd_ssl.zip via TWRP from the SD Card. Till here it worked. I could enter the stock recover and boot the phone.
Then Android wanted to install a security update. I allowed it and this is where the problem started.
The install process stood still on 25% for minutes. I thought it stuck and pressed and hold the power button to reboot that I can wipe the memory. But nothing happened. But the installation Process continued suddenly. I had the feeling that this power key worked like a skip key. So maybe it didn't install a file where it was stuck.
After the installation reached 100% the screen switched to black and nothing worked anymore. I couldn't restart the phone or anything but I think the phone was doing something cause it consumed electricity. When I checked the phone hours later I noticed it was empty.
I can reach the unlocked bootloader now, but none of the selections works. Doing nothing to boot or select Recovery lead to black screen and stuck. Then I have to wait until the battery is empty again. Fastboot, Power Off just restart the phone and I end in the Bootmenu again. I can't even fully charge the phone. As soon as it has enough power to start the Bootmenu appears. So I don't see the display of the charging process.
I don't understand how this could happen. I tried different key combinations when the phone had enough electricty to start. The phone always restarts and end in the bootmenu. Only when I press all three keys it's standing still on the ZTE Logo screen but as soon as I release the keys I end again in the bootmenu.
How can I force another Update?
regards
Let' start with the basic questions:
Do you have proper backup of your data?
Which Android Version did your Axon had before it went unusable?
You could try to reflash TWRP.
Boot your phone into bootmode.
Download a proper TWRP Image on your PC (https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547)
Open a cmd shell (press the windows key and type 'cmd' -> press enter)
Navigate to the folder where the TWRP Image is stored ('
Code:
cd C:\Users\[I]YOUR_USER_NAME[/I]\Downloads\
')
Type: '
HTML:
fastboot flash recovery [I]TWRP_IMG_NAME.img[/I]
'
Afterwards you could try to reboot into recovery mode.
I don't have a backup. But there isn't something imortant on the phone that I want to keep. I can do a full reset and reinstall, too.
Android must have been the latest offical availabe what's in the file. Was it Android 8? V1.3.0B13
The fastboot mode doesn't work. The screen turns black and the LED blinks red but only for a moment. Then the phone restarts and I'm in the bootmenu again. Windows doesn't recognize it as device.
Is there a way to force it to do an update from my SDCard without it needed to be connected to a PC?
Stevie123 said:
I don't have a backup. But there isn't something imortant on the phone that I want to keep. I can do a full reset and reinstall, too.
Android must have been the latest offical availabe what's in the file. Was it Android 8? V1.3.0B13
The fastboot mode doesn't work. The screen turns black and the LED blinks red but only for a moment. Then the phone restarts and I'm in the bootmenu again. Windows doesn't recognize it as device.
Is there a way to force it to do an update from my SDCard without it needed to be connected to a PC?
Click to expand...
Click to collapse
I don't know of any.
But you could boot into EDL Mode (Press and hold Both Volume button and then press the power button) and flash a Stock EDL rom from the Download Center i have linkd before.
It's not visible for the PC. The only thing I see is the charging screen when its total empty and you can't even boot as. As soon as it has enough power to switch to the normal screen the bootloader appears and when I do nothing the screen turns black and nothing happens. I don't even know if it is charging. The LED is off.
Follow this guide to unbrick it and then use MiFlash and flash an EDL ROM
https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229
Hi,
I have a new a20e (a202f) out of the box.
I followed another guide to root and install twrp which turns out was wrong. I unlocked the bootloader just fine.
I have no backup, no personal boot.img or anything.
Essentially I am stuck in download mode and restarting takes me straight back to download mode.
Recovery: Error validating footer.
SW REV. CHECK FAIL (BOOTLOADER) DEVICE"
Cheers guys
What guide did you follow? You have to download your stock fw from sites like sammobile then from there you can have the boot.img and etc. Have you tried flashing stock fw using odin?
Note: Usually you flash vbmeta for footer error when you flash twrp.
Deluriane said:
What guide did you follow? Have you tried flashing stock fw using odin?
Note: Usually you flash vbmeta for footer error when you flash twrp.
Click to expand...
Click to collapse
It was a guide on 'unofficialtwrp.com' - I can't link things here yet.
I have since tar'ed an unpatched twrp (TWRP-3.3.1.0_A20_by_Agrim720.img) + vbmeta.img + boot.img (from https://forum.xda-developers.com/galaxy-a20/help/boo-img-a205fxxu2asfb-t4008739), then I flashed through AP on Odin and now I think it boots past the download mode but instead it now has fuzzy dark red screen with nothing legible.
Oh bugger, I've been a class A plum.
Can I get out of this horrible mess?
craigywaigy said:
It was a guide on 'unofficialtwrp.com' - I can't link things here yet.
I have since tar'ed an unpatched twrp (TWRP-3.3.1.0_A20_by_Agrim720.img) + vbmeta.img + boot.img (from https://forum.xda-developers.com/galaxy-a20/help/boo-img-a205fxxu2asfb-t4008739), then I flashed through AP on Odin and now I think it boots past the download mode but instead it now has fuzzy dark red screen with nothing legible.
Oh bugger, I've been a class A plum.
Can I get out of this horrible mess?
Click to expand...
Click to collapse
Well you have to use your own boot.img from your fw, not all of use the same fw that's why, some are still on u2, u3 and u4. Maybe the boot.img you got isnt the same as your fw.
Well you can start from scratch and reflash your stock fw in odin.
https://www.sammobile.com/firmwares/
Deluriane said:
Well you have to use your own boot.img from your fw, not all of use the same fw that's why, some are still on u2, u3 and u4. Maybe the boot.img you got isnt the same as your fw.
Well you can start from scratch and reflash your stock fw in odin.
Click to expand...
Click to collapse
Yep, but now I can not get back to download mode. Any pointers?
craigywaigy said:
Yep, but now I can not get back to download mode. Any pointers?
Click to expand...
Click to collapse
Try holding volume - and power and your phone will turn off, as soon as it turns off press volume + & - and plug your usb cable that is connected to a computer.
No luck with that. It displays the message about running custom os etc and to press power to continue. So I press it and it boots to the messed up red/pink/black display.
craigywaigy said:
No luck with that. It displays the message about running custom os etc and to press power to continue. So I press it and it boots to the messed up red/pink/black display.
Click to expand...
Click to collapse
Do you mean like the one attached? If yes you havent booted to download mode.
Try booting to recovery by holding volume + and power while you turn on the phone.
There is a option there to boot to download mode.
Deluriane said:
Do you mean like the one attached? If yes you havent booted to download mode.
Try booting to recovery by holding volume + and power while you turn on the phone.
There is a option there to boot to download mode.
Click to expand...
Click to collapse
Yes that screen. I've tried your suggestion with volume + but that also ends up with messed up screen
Yes so currently I'm unable to get to recovery (not sure it even flashed properly), unable to get to download mode, or to get the device recognised in odin.
I'm unable to power off. The screen is blank and when I press power it flickers shortly with some black/white/red pink colours around the edges, but the screen quickly turns blank.
From this position I can only restart by holding volume - and power.
This boots to the samsung logo and then the 'bootloader unlocked' warning. No amount of button configs have proved successful so far, and then I end up back at the blank screen.
I'm happy to start from scratch. I have downloaded the stock firmware but I'm simply unable to proceed.
Aslo the device is not recognised in windows at any point.
Thanks guys
craigywaigy said:
Yes so currently I'm unable to get to recovery (not sure it even flashed properly), unable to get to download mode, or to get the device recognised in odin.
I'm unable to power off. The screen is blank and when I press power it flickers shortly with some black/white/red pink colours around the edges, but the screen quickly turns blank.
From this position I can only restart by holding volume - and power.
This boots to the samsung logo and then the 'bootloader unlocked' warning. No amount of button configs have proved successful so far, and then I end up back at the blank screen.
I'm happy to start from scratch. I have downloaded the stock firmware but I'm simply unable to proceed.
Aslo the device is not recognised in windows at any point.
Thanks guys
Click to expand...
Click to collapse
Are you sure you pressed and hold volume +&- and plugging cable before the samsung logo pops up? You have to do it quickly right after the device turns off. You shoudn't see the bootloader warning if you done this quickly and correctly.
craigywaigy said:
Yes so currently I'm unable to get to recovery (not sure it even flashed properly), unable to get to download mode, or to get the device recognised in odin.
I'm unable to power off. The screen is blank and when I press power it flickers shortly with some black/white/red pink colours around the edges, but the screen quickly turns blank.
From this position I can only restart by holding volume - and power.
This boots to the samsung logo and then the 'bootloader unlocked' warning. No amount of button configs have proved successful so far, and then I end up back at the blank screen.
I'm happy to start from scratch. I have downloaded the stock firmware but I'm simply unable to proceed.
Aslo the device is not recognised in windows at any point.
Thanks guys
Click to expand...
Click to collapse
Hello -
Please trust me when I tell you that it can be fixed. I had the EXACT same problem and drove me crazy for 24 hours. You can deffinetly fix your phone once you get to download mode.
I had the same issue where I could not turn the phone OFF it just looped back and I pushed buttons for hours to no avail... Then some one told me it WILL WORK, it is just the timing of
the button pushing, AND the USB cable plug in. Sure enough he was right. It took me alot of tries and I even took my phone apart and un plugged the battery so I could controll the power
ON / OFF better and time the button's easier. Here is what I did ...
unplug battery so phone was 100% OFF.
Plug in battery ( phone is still OFF )
Hold Vol - then Hold Power and Vol -
As soon as the power started IMEDITALY PLUG IN USB ( have USB READY to be plugged in FAST )
DONT let go of buttons ... screen will flash quickly and then Imediatly let go of power keep holding Vol -
IF you timed this right, IT WILL proced to download mode. If not, then start over again from power OFF ( step 01 )
It took me 3 tries to get it ( after 50+ tries before ) lol
Now I am not sure about the battery unplugging ... maybe you dont need to, but it mad it work for me as I could control the power ON part of this now.
Getting to your battery is not very hard and there is a you tube video on how to do it... if you need help just PM ME.
Good luck friend.
When this happened to me all I did was hold volume up and volume down. Kept cord connected to computer. Connected to device during the bootloop and boom within seconds I was in download mode. It catches it once screen goes off in between the bootloop.
Sent from my SM-N950U using Tapatalk
Thanks you guys. In the end the battery died and then I could power up whilst holding vol+, straight to recovery and then I could flash stock rom.
Much appreciation for your help guys, it got me out of a pinch - it is my mother-in-law's new phone!
craigywaigy said:
Hi,
I have a new a20e (a202f) out of the box.
I followed another guide to root and install twrp which turns out was wrong. I unlocked the bootloader just fine.
I have no backup, no personal boot.img or anything.
Essentially I am stuck in download mode and restarting takes me straight back to download mode.
Recovery: Error validating footer.
SW REV. CHECK FAIL (BOOTLOADER) DEVICE"
Cheers guys
Click to expand...
Click to collapse
can you help me i have the same problem idk how to fix it help