Hi,
I accidentally applied an OTA in my rooted device and then Did somethings that caused a brick. Now my device is detected in the PC as Port 3 (Qualcomm HS-USB QDLoader 9008) and since Motorola is
not providing the Blankflash file needed to rescue the device, the only way to rescue my device is to generate a Loader.img from any of the good people who are using a Motorola g7.
Somebody Please help me out.
I will post the steps below.
1. Get another exact variant of your device and INSERT an SD Card on it. The device chipset must be the same. Thus, if your device (bricked) is MSM8269, the required device CPU has to be MSM8269, too.
2. Root the working (exact variant) device and install Terminal Emulator on it.
3. Download and install Busybox on the device. You may download Busybox from here
4. Once BusyBox is installed, launch/open it and run/install its dependencies/files by clicking on the appropriate key.
5. Now, launch/open Terminal Emulator on the device and follow these procedures:
a. On Terminal EmulatorType:
Code:
su
and hit/tap the Enter key. You will be prompted to GRANT Terminal emulator a Root Access, click GRANT.
b. Then, type:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
and hit/tap the Enter key.
6. Wait few minutes or until Terminal Emulator completes the process.
7. Now, check the Root Folder/Directory of the SD Card inserted on the phone. You will notice that a file named Loader.img has been created.
GOOD! That's your Qualcomm device Unbrick file.
I have referred this article here
https://www.aryk.tech/2017/02/how-to-unbrick-debrick-qualcomm-android.html?m=1
Someone please be kind enough to post a Loader for Moto g7 as there are many people who needs it.
Thanks in advance.
Here is my Loader.img for:
Model Number (SKU): XT1962-1
Baseband Version: M632_12.52.01.86R RIVER_NA_CUST
Bootloader: MBM-2.1-river_retail-b89272e-190401
Kernel: 4.9.112-perf+ #1 Mon Apr 1 21:51:39 CDT 2019
Build #: PP029.114-16-5-2
https://drive.google.com/open?id=1Bb45SC7YU2NnyIlGsHJKbbnq7mKHQ1aj
MD5 (zip): 533fd344eb29590ec285f3e5fd50e47e
MD5: a1a03e2225dd723c5c3549568ad7f4b1
Good luck!
skuppej said:
Here is my Loader.img for:
Model Number (SKU): XT1962-1
Baseband Version: M632_12.52.01.86R RIVER_NA_CUST
Bootloader: MBM-2.1-river_retail-b89272e-190401
Kernel: 4.9.112-perf+ #1 Mon Apr 1 21:51:39 CDT 2019
Build #: PP029.114-16-5-2
https://drive.google.com/open?id=1XYk5ulnZO_k7srEAo76FsBHG9DNrbYS6
Good luck!
Click to expand...
Click to collapse
Thanks a lot skuppej. You saved my phone. Let me try with this file and post the results for other people here.:good::good::fingers-crossed::fingers-crossed::fingers-crossed::victory::victory::victory:
Thanks a lot again for spending the time needed to extract the Loader file. Only if there were more people like you.
thanks for the loader.img - im not unbricked yet
Thank you for taking the time to generate the loader.img file skuppej. (and Phillen13 for posting a possible solution)
I hard-bricked my XT1962-1 with magisk somehow, and it only shows up in windoze dev manager as the qualcomm 9008 com3:
i used rufus and then diskimagerev2 to write the image to a 8GB card, but then had no luck getting the phone to do anything using the buttons. i will try to write the loader.img using my linux box and see what happens.
the referenced article is a bit weak when it comes to the step of booting the loader.img and i have not been able to find any secondary reference for using a loader.img as a process for recovering.
i would like to know what the file size (and ideally a MD5 hash) for the loader.img its possible that the 165M file on GD is too small?
i tried a 16GB card and imaged with disk imager in ubuntu, inserted card into phone, and could not see any action no lights etc, by holding down the power button for various time lengths, then holding down power and vol down buttons.. the only response i discern is the windows sound of a USB device being inserted three tones down, then recognised three tones up. (Qualcomm HS-USB QDLoader 9008 in DevMan as COM3
to respond below, yes i used unofficial TWRP then magisk to patch boot.img and got a bunch of red errors...
Phillen13 said:
Hi,
I accidentally applied an OTA in my rooted device and then Did somethings that caused a brick..
Click to expand...
Click to collapse
May I ask how you successfully rooted your Moto G7?
I successfully unlocked my bootloader but when I used Magisk to patch the boot.img I got stuck in bootloops that finally required a phone reset to get out of.
So, how did you root your G7? Did you use the unofficial twrp? (As far as I know there's no official twrp yet).
Thanks.
Phillen13 said:
Thanks a lot skuppej. You saved my phone. Let me try with this file and post the results for other people here.:good::good::fingers-crossed::fingers-crossed::fingers-crossed::victory::victory::victory:
Thanks a lot again for spending the time needed to extract the Loader file. Only if there were more people like you.
Click to expand...
Click to collapse
No problem! But I am still dubious. Did this actually work for you? I've been in a pickle and had to use a loader.img file for a previous phone and it worked, but I just want to make sure what I produced is good.
khawks said:
Thank you for taking the time to generate the loader.img file skuppej. (and Phillen13 for posting a possible solution)
I hard-bricked my XT1962-1 with magisk somehow, and it only shows up in windoze dev manager as the qualcomm 9008 com3:
i used rufus and then diskimagerev2 to write the image to a 8GB card, but then had no luck getting the phone to do anything using the buttons. i will try to write the loader.img using my linux box and see what happens.
the referenced article is a bit weak when it comes to the step of booting the loader.img and i have not been able to find any secondary reference for using a loader.img as a process for recovering.
i would like to know what the file size (and ideally a MD5 hash) for the loader.img its possible that the 165M file on GD is too small?
i tried a 16GB card and imaged with disk imager in ubuntu, inserted card into phone, and could not see any action no lights etc, by holding down the power button for various time lengths, then holding down power and vol down buttons.. the only response i discern is the windows sound of a USB device being inserted three tones down, then recognised three tones up. (Qualcomm HS-USB QDLoader 9008 in DevMan as COM3
to respond below, yes i used unofficial TWRP then magisk to patch boot.img and got a bunch of red errors...
Click to expand...
Click to collapse
I will try making another loader.img and checking/comparing the hashes. I feel you man!
maybeme2 said:
May I ask how you successfully rooted your Moto G7?
I successfully unlocked my bootloader but when I used Magisk to patch the boot.img I got stuck in bootloops that finally required a phone reset to get out of.
So, how did you root your G7? Did you use the unofficial twrp? (As far as I know there's no official twrp yet).
Thanks.
Click to expand...
Click to collapse
For me, on both G7's I've owned, I updated to the latest OTA, unlocked the BL, installed unofficial TWRP, and then just flashed magisk.zip in TWRP. Crazy to me that other people are running into issues with this! My phone is US Retail, purchased directly from Motorola.
---------- Post added at 12:07 PM ---------- Previous post was at 11:12 AM ----------
I re-generated the loader.img and compared the MD5 and it was the same as the last one I generated.
Updated my link & added the MD5.
skuppej said:
No
For me, on both G7's I've owned, I updated to the latest OTA, unlocked the BL, installed unofficial TWRP, and then just flashed magisk.zip in TWRP. Crazy to me that other people are running into issues with this! My phone is US Retail, purchased directly from Motorola.
Click to expand...
Click to collapse
I'm one of those who ran into loads of trouble following the instructions from
https://forum.xda-developers.com/moto-g7/how-to/root-g7-magisk-t3907084
I was wary of using the unofficial twrp but will do so now. Thanks.
My bootloader is already unlocked but when I needed to reset the phone to get out of the bootloops I lost my ota system update. Is there a way to flash the system updates after rooting?
Yeah I don't recommend following those older instructions...the latest magisk.zip flashes just fine in TWRP....
When it comes to it, I'm hoping I won't have any trouble flashing the latest OTA from https://mirrors.lolinet.com/firmware/moto/river/official/RETAIL/ or from LMSA (I'd probably try this first..since it seems like it would be more 'official')
Right now I am on PP029.114-16-5-2 which I think is the latest...at least OTA didn't want to go any further before I rooted etc.
If you are having trouble with OTA and you don't mind losing your data, I'd do a full magisk uninstall, re-lock of the bootloader/flash using LMSA files.
loader.img failing MD5
I downloaded loader.img using this link: (Thank you skuppej)
xxxx://drive.google.com/file/d/17Wd...GkJygj25PjEYJU - hmm cant post links yet thats ridiculous
MD5: ec2ff9fd90ba8869a1cc5d9021d8f175
actually downloaded it twice and both times failed MD5 hash:
my check....a1a03e2225dd723c5c3549568ad7f4b1
so i added the file to my google drive (assuming that GD uses hash checking, pretty sure it does with file & sync). I am now figuring out how to generate MD5 data on my google drive to see if its good. OK google drive MD5 fails as well.
i have ran into this kind of thing before, skuppej would you be willing to put the loader.img into a container such as a .zip file and out that on your GD please?
khawks said:
I downloaded loader.img using this link: (Thank you skuppej)
xxxx://drive.google.com/file/d/17Wd...GkJygj25PjEYJU - hmm cant post links yet thats ridiculous
MD5: ec2ff9fd90ba8869a1cc5d9021d8f175
actually downloaded it twice and both times failed MD5 hash:
my check....a1a03e2225dd723c5c3549568ad7f4b1
so i added the file to my google drive (assuming that GD uses hash checking, pretty sure it does with file & sync). I am now figuring out how to generate MD5 data on my google drive to see if its good. OK google drive MD5 fails as well.
i have ran into this kind of thing before, skuppej would you be willing to put the loader.img into a container such as a .zip file and out that on your GD please?
Click to expand...
Click to collapse
That's odd!
OK NP, I've updated https://forum.xda-developers.com/showpost.php?p=79702551&postcount=2 with the .zip and the MD5 for both.
I was able to download it/extract/get matching MD5 sums from an external location, so it should all be good..
skuppej said:
No problem! But I am still dubious. Did this actually work for you? I've been in a pickle and had to use a loader.img file for a previous phone and it worked, but I just want to make sure what I produced is good..
Click to expand...
Click to collapse
I have not tried flashing it till now. Been busy with work. I will let you know once I have finished. Thanks for the updated .zip file .You are really a very helpful person.
trying loader.img
Phillen13:
Did you find time to try the loader.img file?
The MD5 hash for the .zip file matches, but I am having trouble getting the loader.img file itself to agree with:
MD5 (zip): 533fd344eb29590ec285f3e5fd50e47e
MD5: ec2ff9fd90ba8869a1cc5d9021d8f175 ----my check....a1a03e2225dd723c5c3549568ad7f4b1
It would be helpful to have more members messing with this.
K.
khawks said:
Phillen13:
Did you find time to try the loader.img file?
The MD5 hash for the .zip file matches, but I am having trouble getting the loader.img file itself to agree with:
MD5 (zip): 533fd344eb29590ec285f3e5fd50e47e
MD5: ec2ff9fd90ba8869a1cc5d9021d8f175 ----my check....a1a03e2225dd723c5c3549568ad7f4b1
It would be helpful to have more members messing with this.
K.
Click to expand...
Click to collapse
Hi khawks. I just generated another and checked the MD5 and it is actually a1a03e2225dd723c5c3549568ad7f4b1, the same as you have checked.
So I guess the new Loader file in the zip is the correct one..extremely sorry for the wild goose chase! I must have confused it with the old one
anyone else had luck getting loader.img to boot?
I have not been able to get my G7 to boot (holding vol down and power keys) (or all three) using a UHS-1 8GB card or a class 4 16gb card with loader.img on it.
Anyone else have any luck?
skuppej said:
Here is my Loader.img for:
Model Number (SKU): XT1962-1
Baseband Version: M632_12.52.01.86R RIVER_NA_CUST
Bootloader: MBM-2.1-river_retail-b89272e-190401
Kernel: 4.9.112-perf+ #1 Mon Apr 1 21:51:39 CDT 2019
Build #: PP029.114-16-5-2
https://drive.google.com/open?id=1Bb45SC7YU2NnyIlGsHJKbbnq7mKHQ1aj
MD5 (zip): 533fd344eb29590ec285f3e5fd50e47e
MD5: a1a03e2225dd723c5c3549568ad7f4b1
Good luck!
Click to expand...
Click to collapse
So I was able too boot using this Loader file..... but I'm stuck from that point. The bootloader shows as locked, won't allow me to unlock it, won't allow me to boot anything, and most fastboot commands return FAILED (remote failure). Does anyone have any advice on how to proceed from this point?
TerrestrialHost said:
So I was able too boot using this Loader file..... but I'm stuck from that point. The bootloader shows as locked, won't allow me to unlock it, won't allow me to boot anything, and most fastboot commands return FAILED (remote failure). Does anyone have any advice on how to proceed from this point?
Click to expand...
Click to collapse
Could you please post specific into such as the size and class of your SD card you used to put the loader.img on?
khawks said:
Could you please post specific into such as the size and class of your SD card you used to put the loader.img on?
Click to expand...
Click to collapse
Yeah, I used a 128GB Class 10 which I had empty. I used this software to put the image on the SD card: https://www.balena.io/etcher/
I then completely turned my phone off, and then booted using Power/VolDown with the card inserted.
I'm wondering if the BL version needs to match? OTAs I've noticed do change BL versions..
I'll give it a shot myself if I can find a spare microsd card somewhere
skuppej said:
I'm wondering if the BL version needs to match? OTAs I've noticed do change BL versions..
I'll give it a shot myself if I can find a spare microsd card somewhere
Click to expand...
Click to collapse
I think there's a good possibility that my problem is related to the bootloader version. I had just flashed the PPOS29.114-16-7-2 version stock rom.
Anyone here have that version, and might be willing to create a Loader.img file? Hell, I'd appreciate it enough to send them some bitcoin in gratitude, or whatnot.
TerrestrialHost said:
I think there's a good possibility that my problem is related to the bootloader version. I had just flashed the PPOS29.114-16-7-2 version stock rom.
Anyone here have that version, and might be willing to create a Loader.img file? Hell, I'd appreciate it enough to send them some bitcoin in gratitude, or whatnot.
Click to expand...
Click to collapse
I would help if I know how.
I just checked and I have PPO29.114-16-7-2 installed. Note that it is PPO29 not "PPOS29". Mine has no S in case that makes a difference.
Related
HOW TO UNBRICK:
Debrick.img:
Courtesy of @jtl999 https://mega.co.nz/#!xZxBwRDa!HupJL9sNXANhTk3Dl1IJslT6NmfZMqwV4kNFNV25Fhc
Courtesy of @turilo https://drive.google.com/file/d/0Bx0cWHq6jupFcUZMNnh3b2JkQjA/edit?usp=sharing (This zip contains TWO IMG files. Just use ONE..)
UNBRICK METHOD:
Following directions taken and modified from: http://forum.xda-developers.com/showthread.php?t=2583603
Part 1: What you need
A SD Card that is the Same Size as your Phone's internal memory.
The unbrick image as above
A program to put the image on a SD Card which is here for windows users: http://sourceforge.net/projects/win32diskimager
The Stock ROM. I got mine here. http://samsung-updates.com/device/?id=SM-N900W8
ODIN 3.0x
Part 2: Prep
Get the battery charged to 100%.
Find a PC and plug the powercord (microUSB Cord) directly into the motherboard. NOT ANY OTHER PORT.
Format the SD Card to ExFAT you need from Part 1.1.
Using the #3 Program from Part 1.3, burn the image to the SD Card. Its simple.
Part 3: Turn it on
Put the battery into the phone.
Plug the charging cord into the phone.
Put the phone into download mode by holding: <Volume Down> + <Home Button> + <Power>
Once you are in download mode press <Volume Up> to enter download mode. Now go to part 4
Part 4: Putting the ROM back on
Don't Deviate from anything here or do extras.
Open Odin from Part 1.5.
Press PDA and Select your STOCK ROM from Part 1.4
Wait a min for Odin to analyze the file.
Hit Start on Odin.
Click to expand...
Click to collapse
MY OP:
SaHiLzZ said:
Hello,
I am in URGENT need of someone who can help me with an UNBRICK img. You should be on stock and/or rooted firmware, but not on leaked TW KitKat bootloader. Please flash the following two files here in custom recovery:
http://forum.xda-developers.com/attachment.php?attachmentid=2540537&d=1390754238
and http://shabbypenguin.com/getdownload.php?file=Tools/Unbrick-Creator.zip
This will NOT flash anything on your device, but it will create a debrick.img file, and Debrick folder. This does NOT contain any sensitive IMEI or anything like that information. Please either PM me directly, or post it here. I will appreciate it greatly.
Trying to follow the Note 3 unbrick threads, and in need of one now..
Unbricking on Note 3..
http://forum.xda-developers.com/showthread.php?t=2625332
http://forum.xda-developers.com/showthread.php?t=2531224
Click to expand...
Click to collapse
SaHiLzZ said:
Hello,
I am in URGENT need of someone who can help me with an UNBRICK img. You should be on stock and/or rooted firmware, but not on leaked TW KitKat bootloader. Please flash the following two files here in custom recovery:
http://forum.xda-developers.com/attachment.php?attachmentid=2540537&d=1390754238
and http://shabbypenguin.com/getdownload.php?file=Tools/Unbrick-Creator.zip
This will NOT flash anything on your device, but it will create a debrick.img file, and Debrick folder. This does NOT contain any sensitive IMEI or anything like that information. Please either PM me directly, or post it here. I will appreciate it greatly.
Trying to follow the Note 3 unbrick threads, and in need of one now..
Unbricking on Note 3..
http://forum.xda-developers.com/showthread.php?t=2625332
http://forum.xda-developers.com/showthread.php?t=2531224
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2507403
try this one this is for 4.3 looks like the one you tried are for 4.4.2
jaythenut said:
http://forum.xda-developers.com/showthread.php?t=2507403
try this one this is for 4.3 looks like the one you tried are for 4.4.2
Click to expand...
Click to collapse
You may want to realize the difference between a EFS-based bootloop, versus what I am looking for after a hard brick.
But thank you for your input.
How did you brick it? - Reason I ask, is cause the w8 is downgradable from 4.4.2 so bootloader playing should not have affected you. Unless you flashed something on it you shouldn't have?
Its not mine, but for someone else who asked me to help. I am not sure how it was bricked. Regardless it is a hard brick..
Bump
sent from my mobile device
SaHiLzZ said:
Bump
sent from my mobile device
Click to expand...
Click to collapse
Unfortunately I can't help on the W8, but have you tried any other note 3 debrick image? Any difference with that?
I have the n900w8 but currently on leaked 4.4.2 kk. I will downgrade and flash the 2 files and see if I can help you out..
EDIT: I have created the N900W8 Canada debrick.img
Uploading now.
---------- Post added at 01:53 PM ---------- Previous post was at 01:51 PM ----------
Try this.
https://mega.co.nz/#!xZxBwRDa!HupJL9sNXANhTk3Dl1IJslT6NmfZMqwV4kNFNV25Fhc
It sure is fun uploading at over 900KB/ps on Telus DSL
here is the N900W8 Canada latest 4.3 Mj4 debrick.img https://drive.google.com/file/d/0Bx0cWHq6jupFcUZMNnh3b2JkQjA/edit?usp=sharing :good::good:
Much appreciated
sent from my mobile device
SaHiLzZ said:
Much appreciated
sent from my mobile device
Click to expand...
Click to collapse
very welcome, Thanks button be greatly appreciated also
Absolutely will do when I'm on a computer. Xda doesn't let me do that out select the lay post of a page!
sent from my mobile device
Also which zip did you flash to create this file?
sent from my mobile device
SaHiLzZ said:
Also which zip did you flash to create this file?
sent from my mobile device
Click to expand...
Click to collapse
Like I just messaged you Shabby's Unbrick_Creator.zip
Hello i'm about to perform this method..Just wanted to confirm with someone that I can use any of the debrick.img provided for version 4.4.2 on my w8. Thanks! I hope to god this works!
Just and FYI -
You don't mention it in the steps about actually putting the sdcard with the unbrick image into the phone again. I assume at or after 3.3 .
Unbelievable ! This worked for me as well. This feature of the Note 3 makes it tinkerer's dream, it makes it virtually brick-proof. I thought I was done when I could not get back to download mode. I was starting to plan out what I was going to do for my next phone.
By the way in my case it was a N900W8 from Puerto Rico. I purchased it locked to Clairo and unlocked it and flashed to Telus stock ROM. If anyone else has gone this route this method works to unbrick. At first it would not go into download, I had to pull the battery and let it sit for a day. The next day I put in a fresh battery and it booted right to the download selector screen. WAhooo! ...and I was off to the races. Much thanks to the OP and the OOP for this solution.
FYI - formatting the sdcard with the boot recovery partition makes it unusable in the state. Just reformat it again to Fat32 and you can use it as a sdcard again. If you have trouble formatting it I used Mini Tools Partition Wizard, it does the trick.
Alawishis said:
Unbelievable ! This worked for me as well. This feature of the Note 3 makes it tinkerer's dream, it makes it virtually brick-proof. I thought I was done when I could not get back to download mode. I was starting to plan out what I was going to do for my next phone.
By the way in my case it was a N900W8 from Puerto Rico. I purchased it locked to Clairo and unlocked it and flashed to Telus stock ROM. If anyone else has gone this route this method works to unbrick. At first it would not go into download, I had to pull the battery and let it sit for a day. The next day I put in a fresh battery and it booted right to the download selector screen. WAhooo! ...and I was off to the races. Much thanks to the OP and the OOP for this solution.
FYI - formatting the sdcard with the boot recovery partition makes it unusable in the state. Just reformat it again to Fat32 and you can use it as a sdcard again. If you have trouble formatting it I used Mini Tools Partition Wizard, it does the trick.
Click to expand...
Click to collapse
Hey friend, Can you please explain me what's the procedure in your FYI? and also, has your phone been working correctly since then? Do I have to keep the debrick.IMG for ever on my SD card? What do you mean by boot recovery partition?
Thanks in advance
Do u have a debrick for lollipop. Pls help
So my s5 g900v hardbricked. I've seen multiple threads on the subject at this site, but none have linked a debrick.img for 5.0(lollipop). If anyone has one i would be grateful.
Debrick image only works if it is exact. What firmware? What bootloader?
Example : PB1, Latest (Locked)
QT_BULK occurs in device I assume? If not, not hardbricked.
smokerbond said:
Debrick image only works if it is exact. What firmware? What bootloader?
Example : PB1, Latest (Locked)
QT_BULK occurs in device I assume? If not, not hardbricked.
Click to expand...
Click to collapse
Yeah, qt_bulk.
Unfortunately, i don't know the firmware/bootloader. It just bricked on me back in March.
Going by sammobile's database, it could be BOG5, BOK3, or BPB1
evmftw said:
Yeah, qt_bulk.
Unfortunately, i don't know the firmware/bootloader. It just bricked on me back in March.
Going by sammobile's database, it could be BOG5, BOK3, or BPB1
Click to expand...
Click to collapse
I'm making an OG5 debrick image for myself and will happily share with you
---------- Post added at 07:43 PM ---------- Previous post was at 07:29 PM ----------
Alright here you go this is my unbrick image made from my G900V:
https://www.androidfilehost.com/?fid=24545065934258334
Anyone have a PB1 Locked bootloader G900V Unbrick.img?
leotakacs said:
Anyone have a PB1 Locked bootloader G900V Unbrick.img?
Click to expand...
Click to collapse
http://forum.xda-developers.com/ver...brick-images-hardbrick-recovery-plan-t3387010
second post
Lightn1ng said:
I'm making an OG5 debrick image for myself and will happily share with you
---------- Post added at 07:43 PM ---------- Previous post was at 07:29 PM ----------
Alright here you go this is my unbrick image made from my G900V:
https://www.androidfilehost.com/?fid=24545065934258334
Click to expand...
Click to collapse
Is this definitely OG5? Not working on an OG5 brick
Edit: The PB1 img worked for me
G900v Hardbricked
Stock, standard S5 G900v. Started Occasionally giving error msg "System Service is not responding".
Googled this & found a common cause is an almost full SD card. Had a 2 gig card almost full, replaced with a 16 gig card, phone started constantly rebooting to splash screen, phone is now Hardbricked. How can I tell which bootloader & firmware are/were on the phone? As I stated, never rooted, took all ota updates, etc. device is recognized by my PC as Quallcom HS-USB QD Loader 9008. Thanks in advance for any/all advice.
Update: I found the original box from the phone & the SW version printed on the box ends in PF4 . Anyone have an unbrick image for this?
hello got a verizon s5 to fix from a friend. it was showing secure modem fail please connect to verizon upgrade software to fix. I did try to connect with the stated software but it didn't connect to the phone. i therefore went and flash the latest firmware for the device. upon flashing the software, the same secure modem fail connect to verizon upgrade software. i tried again to flash over firmware..this time i was succesful, but then i was waiting on the verizon logo for 20 full minutes... i pulled the battery out. thinking it got stuck. now the phone is hard brick blank screen no light no charging. i tried looking for a debrick image for G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1 firmware but no joy... is there anything i can do to revive this phone? it shows up as qusb_bulk in device manager and says device driver not succesfully installed. please help..thanks..using windows 7 on a mac. thanks
SPANISH2 said:
hello got a verizon s5 to fix from a friend. it was showing secure modem fail please connect to verizon upgrade software to fix. I did try to connect with the stated software but it didn't connect to the phone. i therefore went and flash the latest firmware for the device. upon flashing the software, the same secure modem fail connect to verizon upgrade software. i tried again to flash over firmware..this time i was succesful, but then i was waiting on the verizon logo for 20 full minutes... i pulled the battery out. thinking it got stuck. now the phone is hard brick blank screen no light no charging. i tried looking for a debrick image for G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1 firmware but no joy... is there anything i can do to revive this phone? it shows up as qusb_bulk in device manager and says device driver not succesfully installed. please help..thanks..using windows 7 on a mac. thanks
Click to expand...
Click to collapse
Technically any 6.0 debrick image should work. For s***s and giggles, you could even try the PB1 img posted earlier - it's also bootloader revision 2, so it theoretically might work. Really, you just need the img to get you back to a working Download mode so you can flash firmware again. If it doesn't work, I'd recommend looking on eBay for an S5 from a seller that accepts returns. Root it, create the img yourself (instructions are here on XDA), and then return the phone
iBowToAndroid said:
Technically any 6.0 debrick image should work. For s***s and giggles, you could even try the PB1 img posted earlier - it's also bootloader revision 2, so it theoretically might work. Really, you just need the img to get you back to a working Download mode so you can flash firmware again. If it doesn't work, I'd recommend looking on eBay for an S5 from a seller that accepts returns. Root it, create the img yourself (instructions are here on XDA), and then return the phone
Click to expand...
Click to collapse
ok thanks much....tried the PB1 image but no download mode using a class 10 32gb microsd card
SPANISH2 said:
ok thanks much....tried the PB1 image but no download mode using a class 10 32gb microsd card
Click to expand...
Click to collapse
You did actually burn/write it to the card, correct? You didn't just simply transfer the Img to the card storage?
QL1 firmware verizon s5 debrick image if anyone can create or send me that would be great.
iBowToAndroid said:
You did actually burn/write it to the card, correct? You didn't just simply transfer the Img to the card storage?
Click to expand...
Click to collapse
Yes i did...using the win32 burner
Hey guys i couldn't get in the beta so i was wondering if anyone has the Nougat update file that i can flash with odin.
Thanks
Join the club. No one has the VZW one for the flat s7 either....
Illogi.xbone said:
Join the club. No one has the VZW one for the flat s7 either....
Click to expand...
Click to collapse
Someone said they are going to try. I offered help if need be
billydroid said:
Someone said they are going to try. I offered help if need be
Click to expand...
Click to collapse
I cannot post outside links so please PM me if you would like to test the file. I will also upload it to Android File Host when I am approved.
jakemastaflash said:
I cannot post outside links so please PM me if you would like to test the file. I will also upload it to Android File Host when I am approved.
Click to expand...
Click to collapse
Hey, send me the link. Other than the files, the proccess should be the very basic odin proccess right?
diego97yey said:
Hey, send me the link. Other than the files, the proccess should be the very basic odin proccess right?
Click to expand...
Click to collapse
I believe it can be flashed from Recovery. It's being tested now, I will be checking for updates\consistency tomorrow with a clean flash and update.
jakemastaflash said:
I believe it can be flashed from Recovery. It's being tested now, I will be checking for updates\consistency tomorrow with a clean flash and update.
Click to expand...
Click to collapse
Keep us posted man
Footer and verification error so far
Same here
Sent from my SM-G930P using XDA-Developers mobile app
dgr581 said:
Same here
Sent from my SM-G930P using XDA-Developers mobile app
Click to expand...
Click to collapse
Sounds like it is throwing errors for everyone . I will be trying to grab a fresh copy today, or tomorrow. Link removed until we have a working update.
jakemastaflash said:
Sounds like it is throwing errors for everyone . I will be trying to grab a fresh copy today, or tomorrow. Link removed until we have a working update.
Click to expand...
Click to collapse
I tried using winrar to repair it but still got error code my recovery has been acting strange tho. It says install system update when i boot to it then gives me a dead droid with yellow triangle but then enters recovery like normal.
vegoja said:
I tried using winrar to repair it but still got error code my recovery has been acting strange tho. It says install system update when i boot to it then gives me a dead droid with yellow triangle but then enters recovery like normal.
Click to expand...
Click to collapse
I believe I have a solution. I am working on it now. Additionally, I'm getting close 10 posts!
jakemastaflash said:
I believe I have a solution. I am working on it now. Additionally, I'm getting close 10 posts!
Click to expand...
Click to collapse
Another update pull failed verification and resulted in another footer error. If installed without any modification it works, but after rooting and pulling the update.zip, trying to install it results in an error. It could be a security measure introduced to the update.zip to prevent installing on a phone without the matching signature assigned during the initial download.
Whenever i tried to follow the link it asked me for a security key ????
footer error
I read on another nougat beta thread that if you get a footer error then you should decrypt your SD and try agian
N3ksta said:
I read on another nougat beta thread that if you get a footer error then you should decrypt your SD and try agian
Click to expand...
Click to collapse
I did not have my SD Card encrypted. I have also noticed some discrepancies between the update.zip I am extracting and the working VZW update.zip. Things like: the boot.img is 0kb, and there are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
I have tried extracting it in several different ways\environments and get problems with every pull.
Other variants are working on the same thing with the same issues. I have the last pull I made, but I can't continue working on this as heavily since I'm using my daily driver. I'll try again as new info\solutions come up.
Seems like getting root (with current methods) may be disturbing the file structure. There may be something else at play here since all the pulls still come with a boot.img that is 0kb, and are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
Here is the link to the WIP update.zip. I'm going to stop working on this until someone can suggest a better way to root or pull the file without it coming out corrupt\incomplete. Good luck!
Link to the update.zip.
Here is the flashing method used by the VZW folks:
Originally Posted by zimgir124
A method has been found to install the beta without being accepted!
Thanks @jrkruse for finding this method!
1. reboot to download mode (power + volume up +home) and make sure phone says Official under system and binary.
2. If it does not then you must odin the PH1 firmware, use the pit file and the full csc not the home csc file
3. go through setup
4. enable developer options
5. turn OEM unlock off
6. enable USB debugging
7. place Update.zip on Ext sd card in folder named fota
8. power off phone
9. reboot to download mode make sure both system and binary are official.
10. reboot to recovery (Power + volume down + home)
11. choose apply Update.zip from SD card
12. find Update.zip in the fota folder you created on your Ext sdcard
13. click yes to apply
After this it should update to the Android 7.0 beta and hopefully will be able to download future beta OTAs.
You will not lose anything as this is an OTA
You do not want to be rooted. You must be stock for this to work!
There is no gear VR available on the beta.
Troubleshooting:
"E: footer is wrong" followed by "E: signature verification failed" : Decrypt SD Card and try again.
Click to expand...
Click to collapse
jakemastaflash said:
Seems like getting root (with current methods) may be disturbing the file structure. There may be something else at play here since all the pulls still come with a boot.img that is 0kb, and are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
Here is the link to the WIP update.zip. I'm going to stop working on this until someone can suggest a better way to root or pull the file without it coming out corrupt\incomplete. Good luck!
Link to the update.zip.
Here is the flashing method used by the VZW folks:
Click to expand...
Click to collapse
So should this method work for us?
jakemastaflash said:
Seems like getting root (with current methods) may be disturbing the file structure. There may be something else at play here since all the pulls still come with a boot.img that is 0kb, and are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
Here is the link to the WIP update.zip. I'm going to stop working on this until someone can suggest a better way to root or pull the file without it coming out
Here is the flashing method used by the VZW folks:
Click to expand...
Click to collapse
Is it for the flat or edge? also have you tried using adb to pull the file (you probably have, but just asking)
15jpenni said:
So should this method work for us?
Click to expand...
Click to collapse
Ideally it should. However, I have not been able to successfully reproduce the same results as installing the update file without modification.
---------- Post added at 09:04 PM ---------- Previous post was at 09:00 PM ----------
N3ksta said:
Is it for the flat or edge? also have you tried using adb to pull the file (you probably have, but just asking)
Click to expand...
Click to collapse
This is for the SM-G930P regular S7 (not edge). I have pulled it via filemanager app after full root, and via adb on linux and windows after eng kernel root and full root. All of them yielded an apropriately sized update.zip, but it seems to get corrupted during the rooting or extraction process.
Also, there may be a reason behind our update.zip not having a boot.img. We may not need a new boot.img after updating to PJ2, so it isnt packaged in our update. If someone can repackage the update.zip so it passes verification we may have more luck.
Need Help!,
Updated my xt1643 indian g4 plus to the June Security Patch (NPJS25.93.14-8) build.
Post that I unlocked the bootloader and installed AOSPX rom after which I wanted to go stock nougat.
I flashed the marshmallow rom and took the ota to nougat and now my screen is all black, not even being able to boot the device to fastboot.
By exploring the forums I got to know that I've hard bricked my device but this thing never happened before the june update.
I'm not even able to use the blank files method to revive my device:crying::crying:
Please help
Only choice
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
drmuruga said:
Only choice
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Click to expand...
Click to collapse
thank you, but it did not work. Also I read around the forum that I would be needing the latest blank flash files which would be capable enough to be flashed on the June Security Rom(NPJS.25.93.14-8)
gautamchawla195 said:
thank you, but it did not work. Also I read around the forum that I would be needing the latest blank flash files which would be capable enough to be flashed on the June Security Rom(NPJS.25.93.14-8)
Click to expand...
Click to collapse
You must Press Power Button and Volume down for 2-3 Minutes and Hold them. ( Handy must be connected to the charger !!! )
This means more then 120 Seconds.Then your handy will boot to Recovery.
then navigate to "start" in recovery with volume buttons and hit "power button" that it starts normally.
Try this please it helped me....and say us if it worked for you !
this solutions helps if android gets freezed .I first tough also my handy was death.But it worked for me.
But remember it must be connected to charger and press more then 120 seconds and hold !!!This will work on all Motorola Handys with Android.
majo3000 said:
You must Press Power Button and Volume down for 2-3 Minutes and Hold them. ( Handy must be connected to the charger !!! )
This means more then 120 Seconds.Then your handy will boot to Recovery.
then navigate to "start" in recovery with volume buttons and hit "power button" that it starts normally.
Try this please it helped me....and say us if it worked for you !
this solutions helps if android gets freezed .I first tough also my handy was death.But it worked for me.
But remember it must be connected to charger and press more then 120 seconds and hold !!!This will work on all Motorola Handys with Android.
Click to expand...
Click to collapse
This is something new apart of which I've been researching around forums.
Btw, would work as per the given fix and keep you posted
gautamchawla195 said:
This is something new apart of which I've been researching around forums.
Btw, would work as per the given fix and keep you posted
Click to expand...
Click to collapse
Nupp, not working, I too think that I should wait for the full june security rom and post that the blank flash files to get my device alive again. I would please request someone to gain access to the blank flash files after the june rom is released.
June security update won't let you downgrade and has bricked many devices. You have to wait until full rom of 6/17 is released as you've said. If under warranty, you can send it in. If insured, you can try to kill your phone by dropping in water and collect insurance.
HueyT said:
June security update won't let you downgrade and has bricked many devices. You have to wait until full rom of 6/17 is released as you've said. If under warranty, you can send it in. If insured, you can try to kill your phone by dropping in water and collect insurance.
Click to expand...
Click to collapse
Yes, we would be needing the updated blank flash files for the june update, can you please tell me about how long the june blank flash files are released after the full fastboot rom is released as per the past experiences and would that increase chances for my device to get revived?
June full ROM lauched:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
How can I extract the blankflash from this ROM? It's possible? Please, help me! I didn't found in Google a way to get these files to save my moto g4+ hard briked
pekenolucas said:
June full ROM lauched:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
How can I extract the blankflash from this ROM? It's possible? Please, help me! I didn't found in Google a way to get these files to save my moto g4+ hard briked
Click to expand...
Click to collapse
Well, we're gonna need a copy first to see what's inside - that link keeps giving me access denied. Presumably it's only for service centres or for developers. Strange, it's working now...
This link is OK! I downloaded it right now using Chrome from my phone. I'm from Brazil.
pekenolucas said:
This link is OK! I downloaded it right now using Chrome from my phone. I'm from Brazil.
Click to expand...
Click to collapse
Ah, you're right - dunno why the link gave me access denied initially - it's downloading okay too now.
EDIT - just downloaded the ROM and had a look - no sign of a new blank flash that could help us unfortunately.
Looks like the only resolution, unfortunately, for a bricked device involving the NPJS25.93-14-8 update, (whether it was downgraded with a stock ROM, or you somehow downgraded from the June update, and then updated with the June OTA) is to send it for service or save up for a new device.
echo92 said:
Ah, you're right - dunno why the link gave me access denied initially - it's downloading okay too now.
Click to expand...
Click to collapse
echo92, can you plzz check and also ask vache and some of the other developers too, to go through the june rom and see if there's any file which we can use to revive our devices.
Edit: sorry, didn't saw ur reply
Gpt.bin from ROM have same archives from blankflash, but gpt.bin have 32kb and blankflash more than 3Mb! Anyone know how to put gpt.bin data inside blankflash to update the partition table and possible unbrick the device? It's just an idea!
pekenolucas said:
Gpt.bin from ROM have same archives from blankflash, but gpt.bin have 32kb and blankflash more than 3Mb! Anyone know how to put gpt.bin data inside blankflash to update the partition table and possible unbrick the device? It's just an idea!
Click to expand...
Click to collapse
is there anyway to edit contains of singleimage.bin ?
The blankflash stays the same.. only the gpt.bin and bootloader.img are to be changed accordingly
echo92 said:
Well, we're gonna need a copy first to see what's inside - that link keeps giving me access denied. Presumably it's only for service centres or for developers. Strange, it's working now...
Click to expand...
Click to collapse
Can you upload a copy if you've downloaded it? The link doesn't work now. Seems to have been removed.
gpt.bin of the latest firmware and singleimage.bin file from the Blankflash seems to be having the same contents.
I tried renaming gpt as singleimage and tried using blankflash
It didn't work. Also the size of both the files are not even comparable one is 32kb and another is 4mb
tywinlannister7 said:
The blankflash stays the same.. only the gpt.bin and bootloader.img are to be changed accordingly
Click to expand...
Click to collapse
Yes, but I think that Bootloader.img and GPT.bin are inside singleimage.bin data, because it rewrite these information on bricked phones. I don't know singleimage.bin have signed data. If it had signed data, no chance to patch/modify it!
I'll try some hex editor and run some tests!!!
zeomal said:
Can you upload a copy if you've downloaded it? The link doesn't work now. Seems to have been removed.
Click to expand...
Click to collapse
tywinlannister7's kindly uploaded the ROM for us [EDIT - link removed as the ROM appears to cause loss of SIM for some devices]
Hello everyone.
You all might have read in the xda news that @XCnathan32 fixed the Nexus 6p and now also the Nexus 5 bootloop issue (same as on our G4s) by disabling the big faulty cores and running the phone on only the small ones. Now our beloved dev @steadfasterX has come up with a similar fix for our G4.
it works by flashing modified boot and TWRP image onto the LG G4 so that it only works on the small four cores
UPDATE: Tested and found working by @the_naxhoo on his H815
Requirements
An unlocked G4
@steadfasterX 's FWUL for ease and required tools (lglaf)
Patience and prayers (optional though)
NOTE: the attached files are only for the T-Mobile variant which had 20o software before boot looping and the International H815 (BGR) variant which had 20g software before bootlooping
Guide:
(A)For unlocked devices that can access Fastboot
Access Fastboot mode by using the following method:
Pull out battery then connect usb cable, press volume down, put battery back while keeping volume down pressed
Click to expand...
Click to collapse
If you just reached the Fastboot mode, Congrats. Now execute the following commands in fastboot
Code:
fastboot flash boot boot.img
fastboot flash recovery twrp_4cores_3.1.1-1-g4.img
Now you have a kernel and twrp with max 4 CPUs and the faulty CPUs disabled. Enjoy your resurrected phone.
(B)For Devices that can not acess Fastboot(unlocked only)
For a backup of your existing data you need an external SD Card big enough for a full backup of your device (64 GB if you want to backup the /data partition - otherwise you will be fine with 8 GB) best is to format the SD card with ext4 !! fat32 will fail for backup
For just flashing a boot image any SD card will fit..
1)extract both files you downloaded(see attached files) and put them on the SD card
2)boot FWUL and login
3)put the external SD card in your phone
4)boot phone to download mode and connect it to your PC with FWUL running
5)in FWUL find the folder LG on the desktop and open it
double click on the lglaf (auth) icon
6)you should see the lglaf shell now. Type in the command:
Code:
uname -a
(it should print out the line with your current kernel version which just indicates that you're connected)
7)mount external SD:
Code:
mount -t ext4 /dev/block/mmcblk1p1 /storage/external_SD
8)Now backup first (recommended but optional):
Update regarding backing up:
Check out the new guide here: https://tinyurl.com/dlbackup
9)Now flash:
Code:
dd if=/storage/external_SD/boot.img of=/dev/block/mmcblk0 seek=491520 bs=512
Code:
dd if=/storage/external_SD/twrp_4cores_3.1.1-1-g4.img of=/dev/block/mmcblk0 seek=573440 bs=512
Now you have a kernel and twrp with max 4 CPUs and the faulty CPUs disabled. Enjoy your resurrected phone.
Please test and leave comments
Support / IRC Channel
IRC means Internet Relay Chat and you will get best support there only.
Choose how to get in:
PC (HexChat and Pidgin are only 2 of them! This list is not complete!)
Android (Yaaic, AndChat, HoloIRC, AndroIRC are only a few of them! This list is not complete!)
Web (KiwiIRC-Web,FreenodeWebchat])
When you have to choose a channel it is: #Carbon-user
When you be asked for a server network choose: freenode
Update: File for h815 20i is here: https://forum.xda-developers.com/g4/general/fix-lg-g4-bootloop-issue-t3647538/post73282829
File for h815 20p is here: https://forum.xda-developers.com/g4/general/fix-lg-g4-bootloop-issue-t3647538/post73610856
File for H811 20r is here: https://forum.xda-developers.com/g4/general/fix-lg-g4-bootloop-issue-t3647538/post73636261
Any chance of getting this for international H815 version with H81520g firmware?
Sent from my iPad using Tapatalk
Stransky said:
Any chance of getting this for international H815 version with H81520g firmware?
Click to expand...
Click to collapse
sure I'll update the OP with it soon
Stransky said:
Any chance of getting this for international H815 version with H81520g firmware?
Click to expand...
Click to collapse
please give me the link to the v20g kdz firmware
XeniX_Force said:
please give me the link to the v20g kdz firmware
Click to expand...
Click to collapse
hi,
Here you find it all:
https://lg-firmwares.com/lg-h815-firmwares/
ist there a way to disable the big cores on any rom (original/custom) for all time?
skdubg said:
hi,
Here you find it all:
https://lg-firmwares.com/lg-h815-firmwares/
ist there a way to disable the big cores on any rom (original/custom) for all time?
Click to expand...
Click to collapse
there might be @steadfasterX is currently working on this. he'll tell you after that hopefully
XeniX_Force said:
please give me the link to the v20g kdz firmware
Click to expand...
Click to collapse
As posted by (skdubg) and select GBR version.
skdubg said:
hi,
Here you find it all:
https://lg-firmwares.com/lg-h815-firmwares/
ist there a way to disable the big cores on any rom (original/custom) for all time?
Click to expand...
Click to collapse
Atm the method is ROM specific. That means I need a direct link or the EXACT file name to the used kdz. E.g. H815 has several country versions.
Disabling the cores on any ROM means modifying aboot which is not an option because even when your device is unlocked the try may soft or hard brick.
Instead once I have the time I will make a flashable TWRP zip for this which patches the boot image after flashing a ROM but this is a manual task everytime after flashing a ROM.
Stransky said:
As posted by (skdubg) and select GBR version.
Click to expand...
Click to collapse
Perfect thx.
Sent from my LG-H815 using XDA Labs
Anyone with an bootlooped H811 who can try this?
The file for h815 will be uploaded soon
Stransky said:
As posted by (skdubg) and select GBR version.
Click to expand...
Click to collapse
find attached the patched boot image for your ROM version.
just to mention it again: the modded twrp image is highly recommended to flash as well bc TWRP will make use of all cores it can find when backing up/restore
when your device is unlocked AND you have fastboot access you can just do a
Code:
[COLOR="Blue"]fastboot flash boot boot_4cores.img
fastboot flash recovery twrp_4cores.img[/COLOR]
The download mode way I described in the OP is required when you cannot access fastboot and for locked devices. I will try to create a KDZ out of this but atm this is the way to go then.
I cannot say for sure that this way will soft brick locked devices or not. it should not but i cannot test it..!!
It mainly depends on the fact if the whole boot image gets verified or just the kernel + initrd.
afaik its not the whole boot partition... so it should work with the download mode way even on locked devices.
@XeniX_Force : attach the file and fastboot cmds to the OP as well pls.
.
Stransky said:
Any chance of getting this for international H815 version with H81520g firmware?
Click to expand...
Click to collapse
The OP has been edited with a fastboot method. you can either use it or the download mode method to try and revive your G4 your requested file has been attached please try and report to us as soon as possible
The only fix for a G4 rebooting is the remove the LPDDR3, reball and replace it.
rustybronnco said:
The only fix for a G4 rebooting is the remove the LPDDR3, reball and replace it.
Click to expand...
Click to collapse
not necessarily. the problem is with the bigger cores. why replace ram?
The issue is failed solder joints between the SOC and the LPDDR3. Disabling cores will not keep it from occurring.
rustybronnco said:
The issue is failed solder joints between the SOC and the LPDDR3. Disabling cores will not keep it from occurring.
Click to expand...
Click to collapse
but we tested on the_naxhoo's bootlooped phone and it's back to working
https://en.wikipedia.org/wiki/LG_smartphone_bootloop_issues
When officially acknowledging the bootloop issues with the G4, LG stated that it was caused by a "loose contact between components";
Click to expand...
Click to collapse
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
XeniX_Force said:
but we tested on the_naxhoo's bootlooped phone and it's back to working
Click to expand...
Click to collapse
Applying pressure to the chip may also bring it back to a non-boot loop condition.
My G3 has a credit card 'shim' between the LPDDR3 and the housing. It cured? the fad out to black for a period of time. They also blue or green screened as well. On the G4 it shows up as a boot looping or stop (stuck) booting condition. My G4 is currently at LG awaiting a motherboard.
rustybronnco said:
https://en.wikipedia.org/wiki/LG_smartphone_bootloop_issues
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
Applying pressure to the chip may also bring it back to a non-boot loop condition.
My G3 has a credit card 'shim' between the LPDDR3 and the housing. It cured? the fad out to black for a period of time. They also blue or green screened as well. On the G4 it shows up as a boot looping or stop (stuck) booting condition. My G4 is currently at LG awaiting a motherboard.
Click to expand...
Click to collapse
understood
the thread has been renamed
our phone is hopeless
Don't get me wrong, this may help extend the life of certain units. But as they say, it might be just a matter of time before the problem rears its ugly head once again.
https://www.reddit.com/r/lgg4/comme...boot_looping_g4_replaced_for/#bottom-comments
XeniX_Force said:
The OP has been edited with a fastboot metho,chave d. you can either use it or the download mode method to try and revive your G4 your requested file has been attached please try and report to us as soon as possible
Click to expand...
Click to collapse
Hi
Thanks for the files. Have a new problem in that my G4 has stopped bootlooping, in fact it is not doing anything now.
Have tried another battery but no response, Was on the Lifes Good screen and it suddenly
went blank and it will not boot to anything. Tried spare battery and connected to charger but nothing.
Any ideas?
Stransky said:
Hi
Thanks for the files. Have a new problem in that my G4 has stopped bootlooping, in fact it is not doing anything now.
Have tried another battery but no response, Was on the Lifes Good screen and it suddenly
went blank and it will not boot to anything. Tried spare battery and connected to charger but nothing.
Any ideas?
Click to expand...
Click to collapse
yea bootloop is the first stage. next one is what u describe. send it to repair.
there are good chances that it went into QDL 9008 mode. Just connect it to your PC and watch unknown devices in your device manager (or type lsusb on linux) and see what happens.
.
.