Hello everyone here, im a noob around these parts but hope that this beautiful community might help me.
So heres the deal, my gf got an xperia m, that outta the blue started acting out, what i mean for this is, rebooting, outta nowhere and eventually a couple of days later it died.
Making my investigations to get to the problem and therefore the solution, she stated that putting it on the SUS or SONY Pc Companion didn't help at all, plus keep getting error 0x0000067 or 0x000007d5 on PC Companion.
After seeing this, she says tried to unlock the bootloader to install a CWM 6.0 for the 15.4.A.1.9 software, wich it had running, didnt got through since the moment she enter the command through fastboot to check the bootloader status throgh the command fastboot flashing get_unlock_ability but no response just stuck on three dots.
Also tried to flash through FLASHTOOL installing the drivers and everything as ive done with other decives checking everything is okay, which they are, since ive succefully recovered an brick C1904 using CWM with a previous Backup, but the tool gets stuck on flashing loader and wont give a percentage.
Tried Flashing remotely the CWM.img to the boot, but it wont flash, always failed, as for specifics about the code, If really needed ill post them on the next reply.
Hope Someone can Help me,
Regards Jmaquilon
Which error are you getting while flashing the recovery? is it something like remote command not allowed ? If it is then try to flash the recovery in the boot partition (I have done the same many time cuz there are some problem s with my current kernel)and what happens is instead of system the recovery boots up ..
If this doesnt works then try xperiafirm it may bring your phone back to life!
Hope it helps!
Just flash stock rom using flashtool software. Download the Stock Sony Xperia M Rom here http://forum.xda-developers.com/showthread.php?t=2699085 and flash it using flash mode in flashtool. Good Luck
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
yakub234go said:
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
Click to expand...
Click to collapse
Thanks for the response. I've tried this a dozen times, but unfortunately (this is going to sound weird) since it's not completely bricked it is only detected as Moorefield for a few seconds when started. This allows the xfstk tool to detect it and begin the download, but not long enough to complete the process so it times out. The only development access I have to the phone now is via adb, but since I don't have root I'm very limited in what I can do via command line. Since I can't access fastboot I can't achieve root. It's just a comedy of errors now.
kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
sukhwant717 said:
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
Click to expand...
Click to collapse
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
kidnova said:
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
Click to expand...
Click to collapse
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
mrperalta said:
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
Click to expand...
Click to collapse
I've tried this many times, but it only shows Moorefield for a few seconds. I'm assuming this is because it has a fully operational OS so it doesn't stay in the generic USB device mode.
EDIT: I misread your original post. Holding power and volume DOWN does keep connect it in Moorefield. Thanks so much for that. The problem now is that once xFSTK gets to downloading the OS it reboots the phone which takes it out of USB mode and disconnects the tool. I'm still stuck where I was before, but that's a little progress. Any other thoughts?
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
kidnova said:
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
Click to expand...
Click to collapse
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
"those who are not able to keep device connected. take care of few steps
1. in xFSTK option menu change the flag override value to 0x80000807 not 0x800000807 ( don't forget to click gp value over ride)
2. while connecting to xFSTK attach usb to computer. hold power button for 20 seconds to make sure it power downs completely. then hold the power button down and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds"
Click to expand...
Click to collapse
-sukhwant717
mrperalta said:
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
-sukhwant717
Click to expand...
Click to collapse
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
kidnova said:
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
Click to expand...
Click to collapse
Hi, got the same issues, I've read many posts. Tried all of the million options. What was your final way of doing it, do you remember?
I was trying to downgrade my G3 to the original stock firmware (for rooting) following this guide: (androidexplained.com/downgrade-lg-g3/), and my phone became stuck at stage 2 and will not proceed. I've tried every solution I could find to fix the problem, but nothing has worked. For some reason it appears that the phone is not reconnecting to the serial port anymore, so the LG flash tool can't connect. I can't get the phone into download mode to start again, and I can't get the process to resume from where it is at. I was able to re-enable the recovery menu using the JTAG shorting trick, but I can't find any compatible firmware images to flash through ADB. If anyone knows how to fix this, or knows where I can find a ZV4 update zip, then I would greatly appreciate it!
joshhumpherys said:
I was trying to downgrade my G3 to the original stock firmware (for rooting) following this guide: (androidexplained.com/downgrade-lg-g3/), and my phone became stuck at stage 2 and will not proceed. I've tried every solution I could find to fix the problem, but nothing has worked. For some reason it appears that the phone is not reconnecting to the serial port anymore, so the LG flash tool can't connect. I can't get the phone into download mode to start again, and I can't get the process to resume from where it is at. I was able to re-enable the recovery menu using the JTAG shorting trick, but I can't find any compatible firmware images to flash through ADB. If anyone knows how to fix this, or knows where I can find a ZV4 update zip, then I would greatly appreciate it!
Click to expand...
Click to collapse
Please share a video or give more information about model and files used to unbrick.
LeoPosas said:
Please share a video or give more information about model and files used to unbrick.
Click to expand...
Click to collapse
I have the LS990 (Sprint).
When I was stuck in Factory Reset Status 2, I was not able to boot into recovery mode or download mode, but I was able to use this tutorial: (reddit.com/r/LGG3/comments/41wbo3/how_to_unhardbrick_your_lg_g3_jtag/) to renable recovery mode. However, I still cannot access download mode, or else I would use the LG Flash Tool.
I have tried to sideload several roms via adb. Most of them say "E:footer verification failed. E: signature verification failed." All of those were zip files with a single .tot inside. I found one zip that was different (it had a bunch of system images inside). The error I got when trying to sideload that zip was:
"Package expects build fingerprint of lge/g3_spr_us/g3:4.4.2/KVT49L.LS990ZV6/LS990ZV6.1415360315:user/release-keys or lge/g3_spr_us/g3:5.0.1/LRX21Y/150221743942c:user/release-keys; this device has lge/g3_spr_us/g3:4.4.2/KVT49L.LS990ZV4/LS990ZV4.1403169216:
E:Error in /tmp/update.zip
(Status 7)
Installation aborted".
I think this means I found a zip with the right contents inside, but it's the wrong update. If someone knows where to find the correct zip to sideload I believe that would fix the problem. I found this zip here: (twitter.com/utoprime/status/569984569195282432)
Regarding the JTAG exploit I used to get recovery mode back, most tutorials say I should also have download mode back, but I don't. If I were somehow able to get download mode back, then I could use the LG Flash Tool to fix it.
hello everyone,
After months and months of using different ROMs, I tried yesterday the RR rom, followed as always different steps & wipe, did install the ROM & Gapps, there was an error message, don't recall which one, but after it rebooted directly and arrive to:
Fastboot mode started
udc_start()
Now i'm unable to go back to recovery mode nor entering the Download mode with vol-/+ and USB or do anything else. Have i bricked it?
can anyone give me advice please?
What I'd try first - make sure your battery is charged (100 per cent preferable). If you can get it to communicate whrough ADB using some key combos, you basically won. You can just flash a stock ROM from there.
If your PC recognizes it as a G-Pad, yay for you. Use the LG Flash Tool to recover and flash a stock ROM (I assume you have the software, in case not just google it). If it's only connected to the PC discovered as a QHSUSB_DLOAD - refer to this thread and follow step by step - it might help you:
https://forum.xda-developers.com/lg-g-pad-83/help/how-recovered-lg-g-pad-detected-t3207079.
Really tho. Most problems can be helped by prperly and fully charging the tablet and trying the LG tools.
Cheers.
First Redmi Phone and trying to visualize process involved before delving into rooting and so on.
Can someone please summarize step(s) in a clear and precise manner how I can restore original firmware if something goes wrong when rooting and so on, without getting authorization code and other complications? Any tried and tested methods links would appreciated.
Which firmware to download (seems like there are two version - I am on 10 QP1A. 190711.020 / V12.0.5.0.QGGEUXM)
SP Flash Tool - tried using miui_BEGONIAGlobal_V12.0.5.0.QGGMIXM_81830ce93c_10.0.zip but getting scatter file error.
MiFlash_Pro - use begonia_global_images_V12.0.5.0.QGGMIXM_20201107.0000.00_10.0_global_65121cbd47.tar?
I would appreciate if someone can kindly share their tried and tested knowledge of different methods to restore stock image and start again. Any method like Huawei dload sdcard?
buddimanv said:
First Redmi Phone and trying to visualize process involved before delving into rooting and so on.
Can someone please summarize step(s) in a clear and precise manner how I can restore original firmware if something goes wrong when rooting and so on, without getting authorization code and other complications? Any tried and tested methods links would appreciated.
Which firmware to download (seems like there are two version - I am on 10 QP1A. 190711.020 / V12.0.5.0.QGGEUXM)
SP Flash Tool - tried using miui_BEGONIAGlobal_V12.0.5.0.QGGMIXM_81830ce93c_10.0.zip but getting scatter file error.
MiFlash_Pro - use begonia_global_images_V12.0.5.0.QGGMIXM_20201107.0000.00_10.0_global_65121cbd47.tar?
I would appreciate if someone can kindly share their tried and tested knowledge of different methods to restore stock image and start again. Any method like Huawei dload sdcard?
Click to expand...
Click to collapse
You can install stock rom again using normal mi flash tool and use fastboot rom (extract it's files)
Also keep fastboot rom files in C drive on your pc.
(Ps imp. Never disconnect cable from device or pc between flashing stock rom)
Thanks ranvirsuph,
The more guide/comments I am reading, the more confused I am getting tbh.
ROOTING :
After unlocking bootloader can't I just flash the recovery via adb like Huawei/Moto phones? And then replace if need be with stock? Will it work as seen few people are reporting of boot loop?
Which TWRP for - 10 QP1A. 190711.020 / V12.0.5.0.QGGEUXM - any link would be appreciated?
Alternatively, can I do the same with SP Flash - just flash the recovery/boot? Do I use 'MT6785_Android_scatter.txt' and select download mode? As thing stand I am getting all sorts selected (see attached image).
Mi Flash - getting error 'couldn't find the flash script' but I guess may not be following exact procedure....I am assuming it flashes everything? Any adverse consequence of this like loosing IMEI numbers, etc? Do we have A-Z instructions on using this tool i.e what to selec?