Greetings,
I'm trying to build a clockworkmod recovery for my smartphone Fujitsu Arrows X F-02E. I've got the stock recovery dumped from the phone (attachments) and the recovery.fstab. I used them to build recovery on this site builder.clockworkmod.com. Recovery compiled successfully. Then I flashed it to my phone. And when I try to boot into recovery nothing happens, the phone just boots normally into the system (the stock recovery, in its turn, booted normally). Can anyone help with making a CWM recovery?
UPDATE: I can't attach these files here so I've uploaded them to my Cubby: cubby.com/pl/Android/_1f03da99a7034dd6b5ed7cb27bcc0bb0
UPDATE2: There are source code files of firmware of F-02E here - http://spf.fmworld.net/oss/oss/f-02e/ But I'm not advanced in programming enough to use it.
Cat In Boots said:
Greetings,
I'm trying to build a clockworkmod recovery for my smartphone Fujitsu Arrows X F-02E. I've got the stock recovery dumped from the phone (attachments) and the recovery.fstab. I used them to build recovery on this site builder.clockworkmod.com. Recovery compiled successfully. Then I flashed it to my phone. And when I try to boot into recovery nothing happens, the phone just boots normally into the system (the stock recovery, in its turn, booted normally). Can anyone help with making a CWM recovery?
UPDATE: I can't attach these files here so I've uploaded them to my Cubby: cubby.com/pl/Android/_1f03da99a7034dd6b5ed7cb27bcc0bb0
Click to expand...
Click to collapse
did you use
# cat /proc/mtd
or http://forum.xda-developers.com/showthread.php?t=2334554
to get the recovery.img
hechis said:
did you use
# cat /proc/mtd
or http://forum.xda-developers.com/showthread.php?t=2334554
to get the recovery.img
Click to expand...
Click to collapse
I've used different ways. Using adb I've downloaded, for a backup, all files from phone in /dev/block/ section. I've got 45 files,from mmcblk0 to mmcblk45, and only two of them had 10240kb size, one of them was a recovery. Then I've made backup with recovery-tools and got one more .img file. Checking the md5 sums showed that mmcblk32 is equal to recovery.img. So here it is. As alternative way I could get this recovery by copying /dev/block/platform/sdhci-tegra.3/by-name/SOS . It's the same recovery and equal to mmcblck32. So there is no doubt that it's the correct file we need.
UPDATE2: There are source code files of firmware of F-02E here - http://spf.fmworld.net/oss/oss/f-02e/ But I'm not advanced in programming enough to use it.
Found this info - blogs.yahoo.co.jp/y_19980320/33484520.html (use google translate). It seems that bootloader is locked and it's divided into 2 parts. First one, BL1 (not re-writable) is checking the authenticity of the BL2 (re-writable, but without correct signature it has no sense) after that, BL2 checks the kernel and boot the phone. Can we do something with that? (hello Motorola Defy)
And in the second post - blogs.yahoo.co.jp/y_19980320/33513111.html there are some usefull info too, but I culdn't understand a bit of this, even with google translate. Does anyone knows what is said in that post?
I think I've got both of this files. BI1 and BI2 here - cubby.com/pl/Android/_1f03da99a7034dd6b5ed7cb27bcc0bb0 But I may be wrong. As mentioned in the article in the first link the first part of bootloader can not be re-written. But I've tried and both parts flashed successfully. So either I've found not the bootloader files either info in the article is wrong. How can I find out are these correct bootloader files or not?
It seems that I found wrong files. Correct files seems to be - mmcblk0boot0.img and mmcblk0boot1.img. Here - cubby.com/pl/Android/_1f03da99a7034dd6b5ed7cb27bcc0bb0
You can try this
From China:
http://bbs.xda.cn/thread-11674785-1-1.html
From xda
http://forum.xda-developers.com/showthread.php?t=2334554
Works with F03D
I have a Fujitsu F03 D , this recovery can works with it ?
Thanks , bye :fingers-crossed:
F02-E Data Recovery
Hello everybody, I don't know if I am on the right topic, but I think people here can answer because it's about the Fujitsu F02-E.
I have this phone since more than 4 years and I was plenty satisfied with this item but since yesterday, the phone don't want to work anymore...
At first, it was starting until the screen "ARROWS" and then restart again and again.
Today, the phone is trying to start by two times himself when I put the battery in it...(Orange led; green led; orange led, green led, and at last orange led twinkle two times..then, all is switch off)
When I try to charging, it try to restart like I was explaining and then all is switch off, even the orange led that tells you it is charging...
But when charging it try to restart every 5 minutes..
Now, the screen switch on very rarely and not even for one second.
The very important question is:
Do You know a trick or an application that can recovery all data, because there are A LOT of important things Inside. I have found a few data recover but they are not compatible with the F02-E.
I would be very, very grateful if You can help me, please.
ps: Sorry for my English, I'm French
Have a good day.
Thank You.
Hello everyone, I've been trying to unbrick my ZenFone 2 ZE550ML for at least 5 hours...
(first, the small history...)
I've a french ASUS ZenFone 2 ZE550ML (Z008D) with 2 Go of RAM running latest Lollipop official ROM (I never unlocked bootloader or rooted it)
I suscribed to Asus beta tester program on ZenTalk forum, so I received the Marshmallow upgrade via official OTA last night.
Everything updated normally, I had enough space, update has been completed, I saw the ASUS logo on dark background because it's not unlocked, I saw the message "Optimizing apps..."(ART compiling)... and I successfully booted to Marshmallow... but just one time.
What happened is that my ZenFone 2 is... really... slow... and... with... Marshmallow... it... had... the... same.... slowness... than... with... Lollipop :silly:
And, after playing around with Marshmallow around ten minutes (apps were updating through Play Store), my phone hung, only because of slowness. I could make it sleep (screen turning on/off, that's all, no lock screen), and I could just access to shutdown/reboot menu if I press 3 seconds the Power button. But it was frozen, like it often did in Lollipop.
I waited 15 minutes, because I thought turning off while updating apps like Google Play Services was not a brilliant idea. After 15 minutes of waiting, still frozen, but even more frozen : no power menu, and orange LED was still ON even after disconnecting the charger. I decided to reset my ZenFone 2 by pressing power button 10 seconds.
And... I rebooted it => vibration, then immediately USB logo (when POWER or POWER+UP VOLUME). Nothing more after that. No LED while charging (if I plug it to a charger, it boot loop with USB logo). It's very frustrating because... I saw ASUS logo just before optimization, and I stopped it AFTER update, not during :crying:
(now what I tried)
Today I tried to apply this guide : http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
I managed to install every driver, I downloaded every file/image I could...
Because of USB logo, my device is always recognized as a Moorefield device with known driver
Following the guide, I sent to my phone the basic 4-coulour bootloader using xFSTK, no problem
Here is the problem now : I've a working fastboot menu, fastboot is recognized by my computer, BUT almost every fastboot command fails, because my serial number was set to 0123456789ABCDEF :crying:
-> Fastboot error is systematically : FAILED (remote: flash_cmds error! (this happens after successfully downloading to phone, but it's not applying)
and, I tried "fastboot erase cache" :
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (status read failed (Too many links))
I never had any software mess in my phone :crying:
So I don't know what to do, because I would like to flash only splashscreen, recovery and boot if possible, I don't want to lose data
I'm actually downloading a RAW for WW_ZE550ML_2.20.40.149 that I'll sideload with Asus Flash Tool (without wiping data) if it's the only way to do
Where can I find working images for fastboot that can be flashed on a generic serial number?
Thanks for your answers
Edit 1 : OH WAIT... The fastboot screen on my ZenFone 2 Z008 says :
PRODUCT_NAME - Z00A
VARIANT - ASUS_Z00A
WTF ASUS ?!?!?!?!
The ONLY things I did are : OTA update to Marshmallow (I never had OTA issues before) and sending through xFSTK the FW DNx, IFWI and OS Images FOR ZE550ML given in the guide... What happened?! Please please please, can somebody give me the right files? Thank you ^^
(sorry for eventual bad english, I'm a tired french)
Have you tried to re flash fastboot (fastboot flash droidboot.img)?
About the serial number, I think 0123..DEF is normal because I mine is like yours, too. But everything is fine.
fanfan54 said:
Hello everyone, I've been trying to unbrick my ZenFone 2 ZE550ML for at least 5 hours...
(first, the small history...)
I've a french ASUS ZenFone 2 ZE550ML (Z008D) with 2 Go of RAM running latest Lollipop official ROM (I never unlocked bootloader or rooted it)
I suscribed to Asus beta tester program on ZenTalk forum, so I received the Marshmallow upgrade via official OTA last night.
Everything updated normally, I had enough space, update has been completed, I saw the ASUS logo on dark background because it's not unlocked, I saw the message "Optimizing apps..."(ART compiling)... and I successfully booted to Marshmallow... but just one time.
What happened is that my ZenFone 2 is... really... slow... and... with... Marshmallow... it... had... the... same.... slowness... than... with... Lollipop :silly:
And, after playing around with Marshmallow around ten minutes (apps were updating through Play Store), my phone hung, only because of slowness. I could make it sleep (screen turning on/off, that's all, no lock screen), and I could just access to shutdown/reboot menu if I press 3 seconds the Power button. But it was frozen, like it often did in Lollipop.
I waited 15 minutes, because I thought turning off while updating apps like Google Play Services was not a brilliant idea. After 15 minutes of waiting, still frozen, but even more frozen : no power menu, and orange LED was still ON even after disconnecting the charger. I decided to reset my ZenFone 2 by pressing power button 10 seconds.
And... I rebooted it => vibration, then immediately USB logo (when POWER or POWER+UP VOLUME). Nothing more after that. No LED while charging (if I plug it to a charger, it boot loop with USB logo). It's very frustrating because... I saw ASUS logo just before optimization, and I stopped it AFTER update, not during :crying:
(now what I tried)
Today I tried to apply this guide : http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
I managed to install every driver, I downloaded every file/image I could...
Because of USB logo, my device is always recognized as a Moorefield device with known driver
Following the guide, I sent to my phone the basic 4-coulour bootloader using xFSTK, no problem
Here is the problem now : I've a working fastboot menu, fastboot is recognized by my computer, BUT almost every fastboot command fails, because my serial number was set to 0123456789ABCDEF :crying:
-> Fastboot error is systematically : FAILED (remote: flash_cmds error! (this happens after successfully downloading to phone, but it's not applying)
and, I tried "fastboot erase cache" :
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (status read failed (Too many links))
I never had any software mess in my phone :crying:
So I don't know what to do, because I would like to flash only splashscreen, recovery and boot if possible, I don't want to lose data
I'm actually downloading a RAW for WW_ZE550ML_2.20.40.149 that I'll sideload with Asus Flash Tool (without wiping data) if it's the only way to do
Where can I find working images for fastboot that can be flashed on a generic serial number?
Thanks for your answers
Edit 1 : OH WAIT... The fastboot screen on my ZenFone 2 Z008 says :
PRODUCT_NAME - Z00A
VARIANT - ASUS_Z00A
WTF ASUS ?!?!?!?!
The ONLY things I did are : OTA update to Marshmallow (I never had OTA issues before) and sending through xFSTK the FW DNx, IFWI and OS Images FOR ZE550ML given in the guide... What happened?! Please please please, can somebody give me the right files? Thank you ^^
(sorry for eventual bad english, I'm a tired french)
Click to expand...
Click to collapse
After flashing Z008 with xFSTK IAW the procedure you tried, the product name in fastboot screen is shown as ASUS_Z00A. After flashing with Asus flashtool, the fastboot screen says correct product number Z008 and corect serial number. :good:
I tried to flash boot.img, droidboot.img, system.img and recovery.img because I did not want to lose my data. Unfortunately, my Z008 did not accept the fastboot commands just like you, so I wiped my data. :crying:
It seems that this guy has succeeded to unbrick Z00A without losing his data. I have not tried this procedure in my Z008 using Z008 raw file yet, so I don't know if this is effective for Z008.
http://forum.xda-developers.com/showpost.php?p=67474121&postcount=210
Serial number restored by Asus Flash Tool, now I can flash with fastboot
Hakataben said:
After flashing Z008 with xFSTK IAW the procedure you tried, the product name in fastboot screen is shown as ASUS_Z00A. After flashing with Asus flashtool, the fastboot screen says correct product number Z008 and corect serial number. :good:
I tried to flash boot.img, droidboot.img, system.img and recovery.img because I did not want to lose my data. Unfortunately, my Z008 did not accept the fastboot commands just like you, so I wiped my data. :crying:
It seems that this guy has succeeded to unbrick Z00A without losing his data. I have not tried this procedure in my Z008 using Z008 raw file yet, so I don't know if this is effective for Z008.
http://forum.xda-developers.com/showpost.php?p=67474121&postcount=210
Click to expand...
Click to collapse
Hello,
Thanks for your answers
I let going Asus Flash Tool for 6 hours, I saw in the Task Manager and on my Zenfone that it used fastboot2 to erase partitions.
Phone said O.K
But it's stuck for 6 hours on a500cgfastboot (these files are here : C:\Program Files (x86)\ASUS\ASUS Flash Tool\Google)
So I think I'll have to reboot phone and PC and retry (I checked integrity of the raw with 7-zip (the raw file is actually a zip file which is unzipped in the folder %USERPROFILE%\.fbrawtempdir) but I'll re-download it...)
Maybe serial number just changed...
Edit after reboot : SO COOL
I discovered that a500cgfastboot was stuck because................................... by erasing some partions, fastboot2 restored the right serial number (I had to restart fastboot to see back my legit serial number)... and it restored product name to Z008
And because a500cgfastboot (and other command ran by Asus Flash Tool) have the old serial 0123456789ABCDEF for argument, a500cgfastboot was no longer finding my phone
I'll retry downloading my img files with fastboot... But I saw Asus Flash Tool cleaned system partition too, but I'll try...
Edit after flashing with fastboot
With the right serial number, everything flashed perfectly with fastboot (but there's one problem : in the Mega folder, there is not the system image for Marshmallow)
so, without system image, my phone boots (ASUS logo, etc...) BUT nothing happens after logo because fastboot2 wiped system :crying: :crying:
I have still access to Fastboot, like before bricking (POWER + VOL UP) (but I can't figure out how to enter in recovery, I've just the droid bot with exclamation mark)
(it's unbricked but no system)
fanfan54 said:
Hello,
Thanks for your answers
I let going Asus Flash Tool for 6 hours, I saw in the Task Manager and on my Zenfone that it used fastboot2 to erase partitions.
Phone said O.K
But it's stuck for 6 hours on a500cgfastboot (these files are here : C:\Program Files (x86)\ASUS\ASUS Flash Tool\Google)
So I think I'll have to reboot phone and PC and retry (I checked integrity of the raw with 7-zip (the raw file is actually a zip file which is unzipped in the folder %USERPROFILE%\.fbrawtempdir) but I'll re-download it...)
Maybe serial number just changed...
Edit after reboot : SO COOL
I discovered that a500cgfastboot was stuck because................................... by erasing some partions, fastboot2 restored the right serial number (I had to restart fastboot to see back my legit serial number)... and it restored product name to Z008
And because a500cgfastboot (and other command ran by Asus Flash Tool) have the old serial 0123456789ABCDEF for argument, a500cgfastboot was no longer finding my phone
I'll retry downloading my img files with fastboot... But I saw Asus Flash Tool cleaned system partition too, but I'll try...
Edit after flashing with fastboot
With the right serial number, everything flashed perfectly with fastboot (but there's one problem : in the Mega folder, there is not the system image for Marshmallow)
so, without system image, my phone boots (ASUS logo, etc...) BUT nothing happens after logo because fastboot2 wiped system :crying: :crying:
I have still access to Fastboot, like before bricking (POWER + VOL UP) (but I can't figure out how to enter in recovery, I've just the droid bot with exclamation mark)
(it's unbricked but no system)
Click to expand...
Click to collapse
If you want to use Marshmallow, I recommend to flash pre-rooted lollipop first, then to flash marshmallow. In your situation, you should unbrick your Z008 at first. After that, you can change system to Marshmallow easily.
Pre-rooted Z008 systems are here. http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
In my case, I needed to have rooted and bootloader-unlocked again to enter in recovery.
Yay!
ASUS Flash Tool flashed the 2.20.40.149 successfully
It's saying "Optimizing app 45 of 119", but I think I had 179 when upgrading to Marshmallow...
And my Android was in french before. But I think I'll be able to fix this
I'll check soon if I've still all my data and apps...
(also, I tried to film everything, if it works I could eventually upload a video tutorial )
Thanks
Another problem... Edit 1
Android boots, I haven't any installation "Welcome" popup because I did not reset it, but as a consequence it crashes at start :
"Unfortunately, android.process.media stopped"
"Unfortunately, android.process.acore stopped"
And it reboots
Maybe it's because these are Marshmallow apps... Will I have to reset it?
Or where can I find system.img for Marshmallow?
Edit 2 Just managed to access to recovery menu
Definitely solved
Solved without losing any data (except settings of some non-system apps)
Hello,
I found on ZenTalk (this thread : http://www.asus.com/zentalk/forum.php?mod=redirect&goto=findpost&ptid=78184&pid=392686) a working link to Latest Marshmallow sideload zip for ZE550ML OR ZE551ML. It was the right file, finally.
ZF2/ZE550ML/Z008/Android 6.0.1/WW-4.21.40.54 ~ download --> here.
ZF2/ZE551ML/Z00A/Android 6.0.1/WW-4.21.40.61 ~ download --> here.
Click to expand...
Click to collapse
I sideloaded this file using adb and recovery mode, it worked PER-FECT-LY : my phone just rebooted without any problem, like before the problem. And with latest Marshmallow obviously : I immediately received messages, could access to my pictures, apps, with the same settings than before, in French (just one thing: settings for some non-system apps are reset)
Here is guide of everything I did to unbrick a Marshmallow ZE550ML stuck on USB logo with no bootloader :
(Note: I recommend you to charge your ZenFone for a few hours as soon as you'll get fastboot menu at step 1, so it will not shutdown... Even if it's not turning on the orange LED, it's charging )
(Note also that these are the steps I had to do in order to unbrick MY phone without losing data and installing Marshmallow. For your phone some steps might be unnecessary, if you're lucky... I know this is a very long guide but I had to do this in MY case)
1. Flash basic bootloader with xFSTK Downloader to boot fastboot
I had, first, to switch to advanced startup with support for unsigned drivers (video tutorial here),
install Asus USB drivers (link to Asus USB drivers here - note: video tutorial to install drivers from inf (repeat for every device available : ADB Interface, Bootloader Interface, etc...) )
and IntelSocUSB driver (link to IntelSocUSB driver 1.2.0 - Note: Before finishing IntelSocUSB setup it will ask you to configure a device : you'll have to connect your ZenFone 2 using an USB cable to your computer, while it's displaying USB logo, and WAIT FOR DETECTION IN Device Manager as "Moorefield device" under "Intel Soc" section),
to flash a fastboot bootloader (link to xFSTK_ZE550ML-sal358-amtech.vn for ZE550ML / link to xFSTK_ZE551ML-sal358-amtech.vn for ZE551ML) using xFSTK Downloader (link to xFSTK Downloader 1.7.0) [B
(guides for everything in this step 1: english version - same in vietnamese with screenshots and valid links - detailed PDF for xFSTK with screenshots).[/B] => phone boots on fastboot
2. Flash a lollipop ROM (or Marshmallow raw if you find it) with Asus Flash Tool to repair fastboot info (like serial number) and access recovery if you want to install Marshmallow from a zip
In order to get a working recovery menu (because I found a zip for Marshmallow but no raw, I'll have to install a recovery),
I had to install Asus Flash Tool (link to Asus Flash Tool 1.14 - Note: archive password is www.asus-zenfone.com ),
flash a Lollipop raw (link to WW_ZE550ML_2.20.40.149.raw) on my ZenFone 2 ZE550ML using Asus Flash Tool (Model: ZE550ML - wipe data : no)
(guides for everything in this step 2: english version - same in vietnamese with screenshots and valid links)
BUT because Asus Flash Tool will wipe everything except user data and change your serial number from 0123456789ABCDEF to your legit serial number, flashing will NOT work and process will be ENDLESS because serial number has changed so phone is not found and you're not warned of that by Asus Flash Tool.
After 20 minutes of "OKAY" status displayed in green text on your phone, after 20 minutes of "a500cgfastboot.exe" running in task manager,
I think you can safely unplug USB cable, abort Asus Flash Tool by closing this software, killing "a500cgfastboot.exe",
rebooting phone (notice serial number change in fastboot info on phone's screen) and flash again with same settings but the new serial number (different of 0123456789ABCDEF).
This flash should work, after an hour or less you'll see in Asus Flash Tool that it's finished.
3. Flash Marshmallow zip with adb sideload
Finally, you'll have to shut down your phone,
boot in recovery mode (guide is here),
connect it to computer, select "apply update from adb",
install adb (link to ADB Installer 1.4.3 - Note: install it system-wide but don't install Android USB drivers) on your computer,
download zip OTA for Marshmallow (link to UL-Z008-WW-4.21.40.54-user.zip for ZE550ML / link to UL-Z00A-WW-4.21.40.61-user.zip for ZE551ML),
open a command prompt in the folder where you downloaded files (using "File > Open command prompt > Open command prompt" in the Windows Explorer's ribbon), then type :
Code:
adb devices
to verify that your phone is detected (you should see your serial number in cmd),
then type the following command to flash Marshmallow stock (zip is NOT pre-rooted if you want to root you'll have to do it after) :
ZE550ML
Code:
adb sideload UL-Z008-WW-4.21.40.54-user.zip
ZE551ML
Code:
adb sideload UL-Z00A-WW-4.21.40.61-user.zip
It may take a while decompressing then sending to phone. Then select "wipe cache partition" in your recovery menu,
wait until you see again the menu (so, wait until end of wiping cache), and select "reboot").
Now pray, and your device should magically boot the latest beautiful stock Marshmallow ROM from Asus, with all your data, exactly like before you bricked it.
It worked for me, but with the right new images it should work perfectly for you...
Enjoy this small guide, I hope you'll appreciate hard googling work
Thank you all, my problem is solved
fanfan54 said:
Solved without losing any data (except settings of some non-system apps)
Hello,
I found on ZenTalk (this thread : http://www.asus.com/zentalk/forum.php?mod=redirect&goto=findpost&ptid=78184&pid=392686) a working link to Latest Marshmallow sideload zip for ZE550ML OR ZE551ML. It was the right file, finally.
I sideloaded this file using adb and recovery mode, it worked PER-FECT-LY : my phone just rebooted without any problem, like before the problem. And with latest Marshmallow obviously : I immediately received messages, could access to my pictures, apps, with the same settings than before, in French (just one thing: settings for some non-system apps are reset)
Here is guide of everything I did to unbrick a Marshmallow ZE550ML stuck on USB logo with no bootloader :
(Note: I recommend you to charge your ZenFone for a few hours as soon as you'll get fastboot menu at step 1, so it will not shutdown... Even if it's not turning on the orange LED, it's charging )
(Note also that these are the steps I had to do in order to unbrick MY phone without losing data and installing Marshmallow. For your phone some steps might be unnecessary, if you're lucky... I know this is a very long guide but I had to do this in MY case)
1. Flash basic bootloader with xFSTK Downloader to boot fastboot
I had, first, to switch to advanced startup with support for unsigned drivers (video tutorial here),
install Asus USB drivers (link to Asus USB drivers here - note: video tutorial to install drivers from inf (repeat for every device available : ADB Interface, Bootloader Interface, etc...) )
and IntelSocUSB driver (link to IntelSocUSB driver 1.2.0 - Note: Before finishing IntelSocUSB setup it will ask you to configure a device : you'll have to connect your ZenFone 2 using an USB cable to your computer, while it's displaying USB logo, and WAIT FOR DETECTION IN Device Manager as "Moorefield device" under "Intel Soc" section),
to flash a fastboot bootloader (link to xFSTK_ZE550ML-sal358-amtech.vn for ZE550ML / link to xFSTK_ZE551ML-sal358-amtech.vn for ZE551ML) using xFSTK Downloader (link to xFSTK Downloader 1.7.0) [B
(guides for everything in this step 1: english version - same in vietnamese with screenshots and valid links - detailed PDF for xFSTK with screenshots).[/B] => phone boots on fastboot
2. Flash a lollipop ROM (or Marshmallow raw if you find it) with Asus Flash Tool to repair fastboot info (like serial number) and access recovery if you want to install Marshmallow from a zip
In order to get a working recovery menu (because I found a zip for Marshmallow but no raw, I'll have to install a recovery),
I had to install Asus Flash Tool (link to Asus Flash Tool 1.14 - Note: archive password is www.asus-zenfone.com ),
flash a Lollipop raw (link to WW_ZE550ML_2.20.40.149.raw) on my ZenFone 2 ZE550ML using Asus Flash Tool (Model: ZE550ML - wipe data : no)
(guides for everything in this step 2: english version - same in vietnamese with screenshots and valid links)
BUT because Asus Flash Tool will wipe everything except user data and change your serial number from 0123456789ABCDEF to your legit serial number, flashing will NOT work and process will be ENDLESS because serial number has changed so phone is not found and you're not warned of that by Asus Flash Tool.
After 20 minutes of "OKAY" status displayed in green text on your phone, after 20 minutes of "a500cgfastboot.exe" running in task manager,
I think you can safely unplug USB cable, abort Asus Flash Tool by closing this software, killing "a500cgfastboot.exe",
rebooting phone (notice serial number change in fastboot info on phone's screen) and flash again with same settings but the new serial number (different of 0123456789ABCDEF).
This flash should work, after an hour or less you'll see in Asus Flash Tool that it's finished.
3. Flash Marshmallow zip with adb sideload
Finally, you'll have to shut down your phone,
boot in recovery mode (guide is here),
connect it to computer, select "apply update from adb",
install adb (link to ADB Installer 1.4.3 - Note: install it system-wide but don't install Android USB drivers) on your computer,
download zip OTA for Marshmallow (link to UL-Z008-WW-4.21.40.54-user.zip for ZE550ML / link to UL-Z00A-WW-4.21.40.61-user.zip for ZE551ML),
open a command prompt in the folder where you downloaded files (using "File > Open command prompt > Open command prompt" in the Windows Explorer's ribbon), then type :
Code:
adb devices
to verify that your phone is detected (you should see your serial number in cmd),
then type the following command to flash Marshmallow stock (zip is NOT pre-rooted if you want to root you'll have to do it after) :
ZE550ML
Code:
adb sideload UL-Z008-WW-4.21.40.54-user.zip
ZE551ML
Code:
adb sideload UL-Z00A-WW-4.21.40.61-user.zip
It may take a while decompressing then sending to phone. Then select "wipe cache partition" in your recovery menu,
wait until you see again the menu (so, wait until end of wiping cache), and select "reboot").
Now pray, and your device should magically boot the latest beautiful stock Marshmallow ROM from Asus, with all your data, exactly like before you bricked it.
It worked for me, but with the right new images it should work perfectly for you...
Enjoy this small guide, I hope you'll appreciate hard googling work
Thank you all, my problem is solved
Click to expand...
Click to collapse
Man, Today you saved my life and my phone's life . I had exact same problem like yours and I have tried everything to bring my phone back to life last a few days. Today I just noticed your post and it solved my problem perfectly. Thanks man ,really appreciate it ..
muhammed cy said:
Man, Today you saved my life and my phone's life . I had exact same problem like yours and I have tried everything to bring my phone back to life last a few days. Today I just noticed your post and it solved my problem perfectly. Thanks man ,really appreciate it ..
Click to expand...
Click to collapse
Hello,
Thanks for your great feedback muhammed!
Have a nice day!
help me
fanfan54 said:
Hello,
Thanks for your great feedback muhammed!
Have a nice day!
Click to expand...
Click to collapse
please share to my email link WW_ZE550ML_2.20.40.149.raw
[email protected]
tanks before
iwakpauz said:
please share to my email link WW_ZE550ML_2.20.40.149.raw
[email protected]
tanks before
Click to expand...
Click to collapse
Hello, I already sent it to you by email. Here is the link : https://yadi.sk/d/XAUyR8eRtuKdA
Hello,
Sorry for reviving this thread, but I found myself in the same situation. I followed every step, and it works flawlessly. However, after flashing the stock Marshmallow ROM, unlocking the bootloader, flashing TWRP and reinstalling the stock ROM through there, it always bricks my phone (it's the ZE551ML, by the way), so I can't root my device at all. I wonder if anyone has any way of solving this?
I also found that, after unlocking the bootloader, the serial number appears as 0123456789ABCDEF again. I'm pretty much stuck on the stock ROM at this point, with no way of rooting it at all. I can't flash SuperSU through the stock recovery either, it gives me the "signature verification failed" error.
Thanks a lot in advance.
ayuinaba said:
Hello,
Sorry for reviving this thread, but I found myself in the same situation. I followed every step, and it works flawlessly. However, after flashing the stock Marshmallow ROM, unlocking the bootloader, flashing TWRP and reinstalling the stock ROM through there, it always bricks my phone (it's the ZE551ML, by the way), so I can't root my device at all. I wonder if anyone has any way of solving this?
I also found that, after unlocking the bootloader, the serial number appears as 0123456789ABCDEF again. I'm pretty much stuck on the stock ROM at this point, with no way of rooting it at all. I can't flash SuperSU through the stock recovery either, it gives me the "signature verification failed" error.
Thanks a lot in advance.
Click to expand...
Click to collapse
Hello , Firstly , although not clear when you say > "flashing TWRP and reinstalling the stock ROM through there"
1) You can only back up stock rom and restore from TWRP - you cannot flash stock rom from TWRP .
2) Were you bricked and used xFSTK at some point and did you correct serial before upgrading to M ?
signature failed is normal after unlocking bootloader :good:
timbernot said:
Hello , Firstly , although not clear when you say > "flashing TWRP and reinstalling the stock ROM through there"
1) You can only back up stock rom and restore from TWRP - you cannot flash stock rom from TWRP .
2) Were you bricked and used xFSTK at some point and did you correct serial before upgrading to M ?
signature failed is normal after unlocking bootloader :good:
Click to expand...
Click to collapse
Hello, and thank you for the reply!
I'm rather new to this, so I apologize for the possible incorrect terms... I'll try to describe everything as detailed as possible:
My device got bricked, and I sought a solution for it, thus arriving at this thread.
I did every step the OP described to unbrick the device, using xFSTK, *except* rebooting the device after the first flash with ASUS Flash Tool (because when I did, it'd become unresponsive, so I used the flash tool a second time without rebooting and it recovered my serial number).
Next, I went to recovery and installed the Lollipop .zip through adb sideload.
Afterwards, I installed the Marshmallow .zip through adb sideload again.
It's working great this way, but I wanted to root it, so I rebooted into bootloader, and tried to "fastboot boot twrp.img" with no success.
After reading a few more threads, I figured I had to unlock the bootloader before being able to boot into twrp, so I used the bootloader unlocker.
After unlocking it, I was unable to boot into anything but the bootloader (which I presume is normal), so I tried to boot into twrp through fastboot with no success - I had to use "fastboot flash recovery twrp.img" for it to work.
I went into recovery mode, and twrp launched. Since I presumed I had to install Marshmallow from there, due to unlocking the bootloader, I did - through "install .zip".
And after doing that and rebooting the system, it became unresponsive again, - bricked: black screen, only vibrates - thus returning to its initial state.
ayuinaba said:
Hello, and thank you for the reply!
I'm rather new to this, so I apologize for the possible incorrect terms... I'll try to describe everything as detailed as possible:
My device got bricked, and I sought a solution for it, thus arriving at this thread.
I did every step the OP described to unbrick the device, using xFSTK, *except* rebooting the device after the first flash with ASUS Flash Tool (because when I did, it'd become unresponsive, so I used the flash tool a second time without rebooting and it recovered my serial number).
Next, I went to recovery and installed the Lollipop .zip through adb sideload.
Afterwards, I installed the Marshmallow .zip through adb sideload again.
It's working great this way, but I wanted to root it, so I rebooted into bootloader, and tried to "fastboot boot twrp.img" with no success.
After reading a few more threads, I figured I had to unlock the bootloader before being able to boot into twrp, so I used the bootloader unlocker.
After unlocking it, I was unable to boot into anything but the bootloader (which I presume is normal), so I tried to boot into twrp through fastboot with no success - I had to use "fastboot flash recovery twrp.img" for it to work.
I went into recovery mode, and twrp launched. Since I presumed I had to install Marshmallow from there, due to unlocking the bootloader, I did - through "install .zip".
And after doing that and rebooting the system, it became unresponsive again, - bricked: black screen, only vibrates - thus returning to its initial state.
Click to expand...
Click to collapse
Hi again , yes you did everything right up to a point .
You will have to use xFSTK again , flash in aft after till you see ` RESULT = OK ` after a couple of minutes into flash (serial will be incorrect here) ...
Close aft - force close it - keep phone connected through-out -- do not dislodge data cable--- set everything back up in aft again -- then press vol+ once --- your serial will be corrected -- start the flash and let it finish , it will boot into the system related to the raw you flashed.
upgrade like before BUT when in M , use giovix`s Modder tool to unlock bootloader flash, twrp and root etc.
You will be fine ,just remember to back-up stock rom in TWRP first before installing custom LineageOS ,so you can use` return to stock option ` in modder tool after restoring your stock back-up -- to install future updates :good:
timbernot said:
Hi again , yes you did everything right up to a point .
You will have to use xFSTK again , flash in aft after till you see ` RESULT = OK ` after a couple of minutes into flash (serial will be incorrect here) ...
Close aft - force close it - keep phone connected through-out -- do not dislodge data cable--- set everything back up in aft again -- then press vol+ once --- your serial will be corrected -- start the flash and let it finish , it will boot into the system related to the raw you flashed.
upgrade like before BUT when in M , use giovix`s Modder tool to unlock bootloader flash, twrp and root etc.
You will be fine ,just remember to back-up stock rom in TWRP first before installing custom LineageOS ,so you can use` return to stock option ` in modder tool after restoring your stock back-up -- to install future updates :good:
Click to expand...
Click to collapse
Did everything as you told me, but now whenever I "reboot to system", it boots into recovery every time... :\
To clarify, I used the command "fastboot flash recovery twrp_z00a_v24_repack.img", and then installed the latest .zip of SuperSU in TWRP (Install -> SuperSU.zip).
EDIT: Sorry, I mistook Giovix's bootloader unlocker for their full modder tool, I'll be trying that now.
EDIT 2: You saved my butt! Thank you so much for your help, I managed to succeed in everything, finally!
ayuinaba said:
Did everything as you told me, but now whenever I "reboot to system", it boots into recovery every time... :\
To clarify, I used the command "fastboot flash recovery twrp_z00a_v24_repack.img", and then installed the latest .zip of SuperSU in TWRP (Install -> SuperSU.zip).
EDIT: Sorry, I mistook Giovix's bootloader unlocker for their full modder tool, I'll be trying that now.
EDIT 2: You saved my butt! Thank you so much for your help, I managed to succeed in everything, finally!
Click to expand...
Click to collapse
Marvelous stuff. ,its been a pleasure helping you
Happy flashing
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
PS, should see the lengths some people go to restore serial
Why ? Lol When it
Only takes 3 mins max this way
LG V30 Recovery UnBrick Zips
So as some of you are aware, I released a h932 rom that soft bricked a few devices. well in the process of that I (with @runningnak3d help) figured out a way to unbrick those devices. As long as you have TWRP or download mode with ADB then you can unbrick. These zips here are NOT meant to be flashed to just flash. These zips are for those people that have a non 9008 brick only! DO NOT FLASH THESE ZIPS OR RUN THESE COMMANDS FOR ANY REASON EXCEPT FOR A NON 9008 BRICK! DO NOT FLASH OR RUN THIS COMMANDS BECAUSE YOU HAVE A BOOTLOOP! ONLY FOLLOW THIS THREAD FOR NON 9008 BRICKS! PLEASE BE SMART!
Now on to the good stuff.......
Only download and flash the zip made for your original device model. Do NOT flash whatever your converted too. for example i have a ls998 converted to us998. I would flash the ls998 THEN convert to us998 later on...
NOTE: After flashing the unbrick zip for your model youll need to have a rom zip on your sdcard or internal storage. You'll need to flash that rom zip (aosp or stock) in order to boot
Recovery Zips
H932_Dump.zip [Download]
See Post 2 [Post 2] for what to do if you do NOT have TWRP
See Post 3 [Post 3] if you want to contribute to this thread and backup your device models EMMC for others to be able to recover. ( NO PERSONAL DATA WILL BE USED )
Don´t forget to hit the thanks-button if you like this zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...
#RESERVED1
For those of you that dont have TWRP but have download mode and ADB, you have a second option of just manually running the commands to unbrick.
Step 1 - Make sure you have ADB installed on your computer
Step 2 - Download the zip for your orginal device model
Step 3 - Extract the zip and place all the files into a folder called dump
Step 4 - ADB push the folder to your device ( adb push <file path to dump> /sdcard/ )
Step 5 - Open the update-binary file inside the extracted zip inside META-INF/com/google/android
Step 6 - Run all the make_ext4fs commands in adb shell (adb shell make_ext4fs <partition name>
Step 7 - Run all the write_raw_image commands in adb shell ( NOTE : remove $INSTALLER in your commands and replace write_raw_image with dd ) ( EXAMPLE : adb shell dd if=/sdcard/<partition name> of=/dev/block/bootdevice/by-name/<partition name> )
Step 8 - Once this is done you'll need to reboot and profit.
If any questions about this guide please feel free to tag me and ask and i will help you
thank you
#RESERVED2
Make sure you have enough space on internal storage before flashing the backup zip. You'll likely need 10GB+. this new zip now checks free storage on internal and aborts if not enough. it also now creates a flashable restore zip so now youll have the restore zip internal storage/dump/backup.zip and you can flash this zip when you get a non 9008 brick
Dumps can be done with aosp or custom roms but please try to backup only stock roms if possible. Thanks Everyone!
EDIT: NEW ZIP HAS BEEN ATTACHED.
#RESERVED3
#RESERVED4
I'll be releasing the flashable zip to dump your partitions later today!
Added a flashable backup zip. please flash in twrp and then upload Backup.zip from internal storage Dump folder somewhere and send link here. ill make a restore zip so we can make the v30 almost unbrickable :good:
LG V30 bricked
Hi!
I need your help please, if there is any help... (I hope this is the right thread for my topic)
I got my LG V30 a few days ago (on 8.April 2019, EU version, H930). I schwitched it on and made the initial setup (wifi, region, ...). And the "normal" system update. (I think, it was sec.update from 1.1.2019).
After 2 days I wanted to root the phone. My mistake ....
The steps in short:
1. adb and fastboot installed (on my laptop with Windows 10). I copied SR5-SuperSU-v2.82-SR5-20171001224502.zip into the root of the phone (no sd card in the phone).
2. with adb and fastboot (and LG develpoer account + imiei & co) I managed to unlock with my unlock.bin
3. phone restarted. Since then I see an additional start screen "Lock the bootloader." for 1-2 sec at every start/restart. After this the boot process continues with the standard screen : LG V30 ThinQ powered by Andriod
4. restarting the phone with volume up + power buttons did not funtcion (I gave 4-5 times a try). It never ever succeed for me on this phone. Maybe this is an important point...
5. restarting into the new feature of the phone worked out only with adb reboot bootloader
6. I flashed TWRP in Win10's cmd with fastboot flash recovery recovery.img (I renamed TWRP-3.2.3-7-DataIMG.img to recovery.img)
7. restarting the phone with volume up + power buttons still did not funtcion (I gave it a try 4-5 times)
8. I found this hint : fastboot boot recovery.img. It did the job, TWRP was started (Version 3.2.3-7 DataIMG).
9. I made a backup in TWRP, copied the BACKUP directrory to my laptop. (maybe the only smart thing of me...)
10. TWRP started with fastboot boot recovery.img again
11. in TWRP -> intsall -> SR5-SuperSU-v2.82-SR5-20171001224502.zip selected and the 'restart' option checked.
12. I have seen, that SuRoot....zip was succesful installed (without any errors) and the phone rebooted automatically (it was connected via USB cable to the laptop, but it should not be the problem)
13. since then nothing happens, but the boot screen: for short time the screen with bootlocker text, then only the black screen with LG v30 ThinQ powered by Andriod
I can not boot in to TWRP with volume up + power buttons. This never worked for me. I tried it 20-30 times... :crying:
With volume up + power buttons I can restart, but only the screen with bootlocker text, then only the black screen with LG v30 ThinQ powered by Andriod appiers.
My laptop does not recognise the phone on USB.
Before I destroy the phone with a hammer, any hints?
sicci75 said:
Hi!
I need your help please, if there is any help... (I hope this is the right thread for my topic)
I got my LG V30 a few days ago (on 8.April 2019, EU version, H930). I schwitched it on and made the initial setup (wifi, region, ...). And the "normal" system update. (I think, it was sec.update from 1.1.2019).
After 2 days I wanted to root the phone. My mistake ....
The steps in short:
1. adb and fastboot installed (on my laptop with Windows 10). I copied SR5-SuperSU-v2.82-SR5-20171001224502.zip into the root of the phone (no sd card in the phone).
2. with adb and fastboot (and LG develpoer account + imiei & co) I managed to unlock with my unlock.bin
3. phone restarted. Since then I see an additional start screen "Lock the bootloader." for 1-2 sec at every start/restart. After this the boot process continues with the standard screen : LG V30 ThinQ powered by Andriod
4. restarting the phone with volume up + power buttons did not funtcion (I gave 4-5 times a try). It never ever succeed for me on this phone. Maybe this is an important point...
5. restarting into the new feature of the phone worked out only with adb reboot bootloader
6. I flashed TWRP in Win10's cmd with fastboot flash recovery recovery.img (I renamed TWRP-3.2.3-7-DataIMG.img to recovery.img)
7. restarting the phone with volume up + power buttons still did not funtcion (I gave it a try 4-5 times)
8. I found this hint : fastboot boot recovery.img. It did the job, TWRP was started (Version 3.2.3-7 DataIMG).
9. I made a backup in TWRP, copied the BACKUP directrory to my laptop. (maybe the only smart thing of me...)
10. TWRP started with fastboot boot recovery.img again
11. in TWRP -> intsall -> SR5-SuperSU-v2.82-SR5-20171001224502.zip selected and the 'restart' option checked.
12. I have seen, that SuRoot....zip was succesful installed (without any errors) and the phone rebooted automatically (it was connected via USB cable to the laptop, but it should not be the problem)
13. since then nothing happens, but the boot screen: for short time the screen with bootlocker text, then only the black screen with LG v30 ThinQ powered by Andriod
I can not boot in to TWRP with volume up + power buttons. This never worked for me. I tried it 20-30 times... :crying:
With volume up + power buttons I can restart, but only the screen with bootlocker text, then only the black screen with LG v30 ThinQ powered by Andriod appiers.
My laptop does not recognise the phone on USB.
Before I destroy the phone with a hammer, any hints?
Click to expand...
Click to collapse
Your mistake was not following any of the rooting Instructions in this V30 forum. If you did, you know we don't use SuperSu, we use Magisk. That's probably what messed up your phone.
I understand you obtained an "official" bootloader unlock code from LG for your H930 -- which is not necessary now for almost a year with the WTF exploit -- but you still need to follow the rooting instructions guide.
The unlocked bootloader warning screen is normal. Ignore it, it's just a harmless annoyance. You would have learned that if you read the instructions.
Try manually going into Download mode (power off completely, then hold volume up button while plugging in USB cable) -- if you can, then reflashing most recent full stock H930 KDZ via Dev Patched LGUP in "Refurbish" mode. Dev Patched LGUP is attached to post #1 of that thread.
If/when you recover, your bootloader should still be unlocked, but you'll have install TWRP again and this time use Magisk. Read the WTF instructions, but you can skip the bootloader part, as you've already done that. You can start with Section 6. Read those instructions on a web browser, not an app.
ChazzMatt said:
Try manually going into Download mode (power off completely, then hold volume up button while plugging in USB cable) -- if you can, then reflashing most recent full stock H930 KDZ via Dev Patched LGUP in "Refurbish" mode. Dev Patched LGUP is attached to post #1 of that thread.
Click to expand...
Click to collapse
Thank you for your quick reply!
I'm learning this forum threads, intstuctions and flashing... And I am now preparing for the unbricking.
After installing LGUP, what dev zip files do I need?
LGUP+V30DLL_PATCHED.zip
LGUP_common_DLL_V30_ALLVARIANTS.zip
LGUP_common_OREO.zip
I can take this kdz: H93021w_00_OPEN_EU_OP_0121.kdz, right?
sicci75 said:
Thank you for your quick reply!
I'm learning this forum threads, intstuctions and flashing... And I am now preparing for the unbricking.
After installing LGUP, what dev zip files do I need?
LGUP+V30DLL_PATCHED.zip
LGUP_common_DLL_V30_ALLVARIANTS.zip
LGUP_common_OREO.zip
I can take this kdz: H93021w_00_OPEN_EU_OP_0121.kdz, right?
Click to expand...
Click to collapse
Are you able to get into Download mode?
You want the "patched" version, but be sure to read the installation instructions.
Yes, you can use that KDZ.
If for some reason your bootloader is not still unlocked, you can run your code again.
ChazzMatt said:
Are you able to get into Download mode?
Click to expand...
Click to collapse
Yessss!!After reading very focused the guidelines you mentioned, it was everything fine.
Thank you!
sicci75 said:
Yessss!!After reading very focused the guidelines you mentioned, it was everything fine.
Thank you!
Click to expand...
Click to collapse
Glad to help.
Sent via open market LG US998 V30/V30+
So just uploaded a new zip in post 3. this new zip now checks for free space and will abort if theres not enough to create the backup and flashable restore zip. need at least 10GB in Internal Storage. the zip will now create automatically a flashable restore zip :good: i designed this around the v30 but in theory it should be able to work on all qualcomm devices and maybe even some other SoCs as well. but this has not been tested on other devices. ive fully tested this on my ls998 and everything works great! Enjoy!
john, did i ever tell you, that i like your work and efforts? good man! :good:
Lg v30 h932 brick
Hello, I need your help.
My LG V30 H932 phone is left as a BRICK after installing an erroneous kdz, it does not enter download mode or emergency mode, is there any way to revive it?
JohnFawkes said:
#RESERVED1
For those of you that dont have TWRP but have download mode and ADB, you have a second option of just manually running the commands to unbrick.
Step 1 - Make sure you have ADB installed on your computer
Step 2 - Download the zip for your orginal device model
Step 3 - Extract the zip and place all the files into a folder called dump
Step 4 - ADB push the folder to your device ( adb push <file path to dump> /sdcard/ )
Step 5 - Open the update-binary file inside the extracted zip inside META-INF/com/google/android
Step 6 - Run all the make_ext4fs commands in adb shell (adb shell make_ext4fs <partition name>
Step 7 - Run all the write_raw_image commands in adb shell ( NOTE : remove $INSTALLER in your commands and replace write_raw_image with dd ) ( EXAMPLE : adb shell dd if=/sdcard/<partition name> of=/dev/block/bootdevice/by-name/<partition name> )
Step 8 - Once this is done you'll need to reboot and profit.
If any questions about this guide please feel free to tag me and ask and i will help you
thank you
Click to expand...
Click to collapse
---------- Post added at 03:26 AM ---------- Previous post was at 03:23 AM ----------
My LG V30 H932 phone is left as a BRICK after installing an erroneous kdz, it does not enter download mode or emergency mode, is there any way to revive it?
It was a big mistake and I don't know what to do, my phone does nothing, totally dead
JohnFawkes said:
#RESERVED1
For those of you that dont have TWRP but have download mode and ADB, you have a second option of just manually running the commands to unbrick.
Step 1 - Make sure you have ADB installed on your computer
Step 2 - Download the zip for your orginal device model
Step 3 - Extract the zip and place all the files into a folder called dump
Step 4 - ADB push the folder to your device ( adb push <file path to dump> /sdcard/ )
Step 5 - Open the update-binary file inside the extracted zip inside META-INF/com/google/android
Step 6 - Run all the make_ext4fs commands in adb shell (adb shell make_ext4fs <partition name>
Step 7 - Run all the write_raw_image commands in adb shell ( NOTE : remove $INSTALLER in your commands and replace write_raw_image with dd ) ( EXAMPLE : adb shell dd if=/sdcard/<partition name> of=/dev/block/bootdevice/by-name/<partition name> )
Step 8 - Once this is done you'll need to reboot and profit.
If any questions about this guide please feel free to tag me and ask and i will help you
thank you
Click to expand...
Click to collapse
---------- Post added at 04:04 AM ---------- Previous post was at 03:26 AM ----------
Hello, I need your help.
My LG V30 H932 phone is left as a BRICK after installing an erroneous kdz, it does not enter download mode or emergency mode, is there any way to revive it?!!!
JohnFawkes said:
LG V30 Recovery UnBrick Zips
So as some of you are aware, I released a h932 rom that soft bricked a few devices. well in the process of that I (with @runningnak3d help) figured out a way to unbrick those devices. As long as you have TWRP or download mode with ADB then you can unbrick. These zips here are NOT meant to be flashed to just flash. These zips are for those people that have a non 9008 brick only! DO NOT FLASH THESE ZIPS OR RUN THESE COMMANDS FOR ANY REASON EXCEPT FOR A NON 9008 BRICK! DO NOT FLASH OR RUN THIS COMMANDS BECAUSE YOU HAVE A BOOTLOOP! ONLY FOLLOW THIS THREAD FOR NON 9008 BRICKS! PLEASE BE SMART!
Now on to the good stuff.......
Only download and flash the zip made for your original device model. Do NOT flash whatever your converted too. for example i have a ls998 converted to us998. I would flash the ls998 THEN convert to us998 later on...
NOTE: After flashing the unbrick zip for your model youll need to have a rom zip on your sdcard or internal storage. You'll need to flash that rom zip (aosp or stock) in order to boot
Recovery Zips
H932_Dump.zip [Download]
See Post 2 [Post 2] for what to do if you do NOT have TWRP
See Post 3 [Post 3] if you want to contribute to this thread and backup your device models EMMC for others to be able to recover. ( NO PERSONAL DATA WILL BE USED )
Don´t forget to hit the thanks-button if you like this zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...
Click to expand...
Click to collapse
robertojha said:
Hello, I need your help.
My LG V30 H932 phone is left as a BRICK after installing an erroneous kdz, it does not enter download mode or emergency mode, is there any way to revive it?
Click to expand...
Click to collapse
You tried to cross flashed another variant stock KDZ over your T-Mobile H932? Not sure why you would do that, but normally that results in 9008 brick which needs remote viewer Octoplus help to recover.
Lg v30 h932 brick
I was following a guide and installed a kdz different from the original of my phone, and now I have no download mode or emergency mode, it's totally a brick,...
ChazzMatt said:
You tried to cross flashed another variant stock KDZ over your T-Mobile H932? Not sure why you would do that, but normally that results in 9008 brick which needs remote viewer Octoplus help to recover.
Click to expand...
Click to collapse
ChazzMatt said:
You tried to cross flashed another variant stock KDZ over your T-Mobile H932? Not sure why you would do that, but normally that results in 9008 brick which needs remote viewer Octoplus help to recover.
Click to expand...
Click to collapse
From what I know, there is no fire hose for the H932.
Sent from my LG-H932 using XDA Labs
---------- Post added at 02:40 PM ---------- Previous post was at 02:37 PM ----------
robertojha said:
I was following a guide and installed a kdz different from the original of my phone, and now I have no download mode or emergency mode, it's totally a brick,...
Click to expand...
Click to collapse
I don't think think there is any guide that says to do this. If there was, @ChazzMatt would have gotten it shut down.
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
From what I know, there is no fire hose for the H932.
Click to expand...
Click to collapse
Ah, yeah you're right.
---------- Post added at 03:33 PM ---------- Previous post was at 02:43 PM ----------
BROKEN1981 said:
I don't think think there is any guide that says to do this. If there was, @ChazzMatt would have gotten it shut down.
Click to expand...
Click to collapse
The T-Mobile root guide does say flash the LAF partition of the H933. But only the LAF partition. Some people do not pay attention and flash the entire H933 kdz over the T-Mobile H932 and brick their phone.
Just had a guy in the Frankenstein thread who said he followed instructions. I didn't believe, told him so, and asked him to tell me step-by-step what he did... Turns out rather than flash US998 Nougat, then Master Reset, then Oreo of choice -- he flashed 20f (Oreo), Master Reset, 20g Oreo.
I asked him why he did that. He said US998 20f was Nougat. That's like saying a banana is an apple. "10" is Nougat, "20" is Oreo. Plus, in my instructions I have specific download links to all requisite firmware, which he ignored.
He said he downloaded KDZ from LG-Firmwares website who told him US998 20f was Nougat -- which they didn't. But even if they did, who cares? You're following MY instructions, so use my download links. Once he downloaded actual Nougat from my download link -- hey that worked!
Also use the Dev Patched LGUP which I recommend. Some guy over the telegram thread said he was following my instructions, but used Uppercut. Of course that's going to fail. None of my instruction mention Uppercut and never will because it doesn't work on Oreo or later and conflicts with Dev Patched LGUP. I always include the specific version of Dev Patched LGUP you should be using. (The Dev for Uppercut is amazing, but it just doesn't work on our phones past Nougat. If it's NOT in the Instructions, don't use it.)
This isn't a recipe where you can substitute your own ingredients.
You need to read carefully and pay attention.
I'm happy to help -- but while some people's problems are quite preventable, once occurred may not be fixable.