[Bricked] So finally I managed to "brick?" my phone I guess, but maybe still hope?
Hello everyone!
So after rooting and unrooting my phone already 2 times successfully since I have it, my stupidity went out and so I managed to brick it (OEM Unlock greyed out and bootloader is re-locked). So here some important points:
I am able to get into the OS
SIM and Wi-Fi module (and probably more) aren't working
I cannot check the OEM Unlock as it is greyed out and it says I have to connect to the internet or contact provider
I cannot unlock the bootloader. I have to check the OEM Unlock switch (which is as already said greyed out and not checkable)
I have access to fastboot and recovery mode
I can enter via cmd/terminal into fastboot and issue commands
Lenovo Smart Assistant Recovery feature does not recognize the phone anymore in fastboot
Blankflash didn't work, stuck on <waiting for device>. Probably too not recognizing fastboot
Qualcomm unbrick method not working as the driver does not recognize the phone as such
I am just a small step away of giving up and selling the phone as a parts replacer
Well I think it's not possible to fix this phone anymore, but maybe you Gurus know a way? That's why I resorted here before giving up.
Thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, just unlock the bootloader?
weazie said:
So, just unlock the bootloader?
Click to expand...
Click to collapse
Read 3 and 4 again on the list
solution!
I have the same problem, MY SOLUTION, share Internet access through another phone via Bluetooth and re unlock the bootloader, then flash stock rom android 9
gonza_30 said:
I have the same problem, MY SOLUTION, share Internet access through another phone via Bluetooth and re unlock the bootloader, then flash stock rom android 9
Click to expand...
Click to collapse
You marvelous genius. That did the trick. I was so bluffed with the case that neither sim nor wifi was working so the rest was also dead so I wasn't even considering it. And the bluetooth trick did the trick and was able to unlock the bootloader again.
I had to reflash the modem and fsg again after stock flash to get both working again, but in the end it is unbricked and works.
Thank you so much, may your life will be plastered with joy and happiness.
You are the hero of the day!
KnSZXS said:
You marvelous genius. That did the trick. I was so bluffed with the case that neither sim nor wifi was working so the rest was also dead so I wasn't even considering it. And the bluetooth trick did the trick and was able to unlock the bootloader again.
I had to reflash the modem and fsg again after stock flash to get both working again, but in the end it is unbricked and works.
Thank you so much, may your life will be plastered with joy and happiness.
You are the hero of the day!
Click to expand...
Click to collapse
moto G never die! haha
Hi @KnSZXS and @gonza_30, I have the same problem. After flashing Havoc OS, somewhere down the line I have bricked the phone and followed the unbrick process. I had problems with fastboot telling me that it cannot accept commands or something on those lines when unbricking but when I unplugged and re-pluuged USB to system, the fastboot commands worked. So, between every command, I had to unplug my USB cable and re-plug and execute the next command. Somehow, I have finished flashing. The only error was that no matter what, fastboot erase DDR never worked for me. But the phone booted up and everything works except wifi and phone signal. What do I do.
I tried
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
as only two commands but still no signal or wifi. It does not detect driver at all. What do I do?
aveemashfaq said:
Hi @KnSZXS and @gonza_30
as only two commands but still no signal or wifi. It does not detect driver at all. What do I do?
Click to expand...
Click to collapse
Had the same problem, this fixed it for me:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
When you are done flashing the rom, boot up and when you get to language selection turn off and boot into fastboot again. Then hit those commands
can you post the modem and fsg files here. I have downloaded a leaked pie image and the stock image from unbrick guide. Both of them do not work.
If you want to unbrick, then just use the official stock rom:
https://mirrors.lolinet.com/firmware/moto/evert/official/
Pick the right folder for your device and download the latest stock rom. There is no need to post them here as those files are in the .zip anyway
KnSZXS said:
If you want to unbrick, then just use the official stock rom:
https://mirrors.lolinet.com/firmware/moto/evert/official/
Pick the right folder for your device and download the latest stock rom. There is no need to post them here as those files are in the .zip anyway
Click to expand...
Click to collapse
As hard as I have tried, I simply cannot match the right rom to my phone. I get the general drift, and I've worked out which folder relates to the EU, but I have already tried three roms and each of them give me the dreaded OEM warning message and the ROM will not run.
Help!!
david_inuk said:
As hard as I have tried, I simply cannot match the right rom to my phone. I get the general drift, and I've worked out which folder relates to the EU, but I have already tried three roms and each of them give me the dreaded OEM warning message and the ROM will not run.
Help!!
Click to expand...
Click to collapse
Dude go to fastboot mode and below your screen it will say this Evert or the kind off official Tom that It was originally installed in your phone
Related
hi everyone, i accidentaly used the AutoRecLs980 app to flash the recovery to a D800 and now the device is bricked and wont boot on recovery nor on android,,, just keep showing those lines:
[850] Fastboot mode started
[900]udc_start()
i tried the command "fastboot devices" on sdk and i got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
like is partially recognizing the device..
>>can i try flashing a TWRP.img? or what i did has broken other than recovery partitIon on the devices and that wont solve my problem..
i also founded this: http://forum.xda-developers.com/showthread.php?t=2582142 but dont know if will help me..
thanks so much for triying to help me.
elmy2424 said:
hi everyone, i accidentaly used the AutoRecLs980 app to flash the recovery to a D800 and now the device is bricked and wont boot on recovery nor on android,,, just keep showing those lines:
[850] Fastboot mode started
[900]udc_start()
i tried the command "fastboot devices" on sdk and i got this:
like is partially recognizing the device..
>>can i try flashing a TWRP.img? or what i did has broken other than recovery partitIon on the devices and that wont solve my problem..
i also founded this: http://forum.xda-developers.com/showthread.php?t=2582142 but dont know if will help me..
thanks so much for triying to help me.
Click to expand...
Click to collapse
jump on irc, freenode, lg-g2 channel. Tell them you used the wrong auto-rec and u are able to get into fastboot. They will give you/direct you to partitions for your phone. You will then need to flash these partitions. Probably the correct aboot and laf(downloadmode), and recovery(maybe not). You will then be able to get into download mode, where you can flash a stock rom. Or possibly give you old aboot and directly flash a custom recovery. Not sure. Go and ask.
elmy2424 said:
hi everyone, i accidentaly used the AutoRecLs980 app to flash the recovery to a D800 and now the device is bricked and wont boot on recovery nor on android,,, just keep showing those lines:
[850] Fastboot mode started
[900]udc_start()
i tried the command "fastboot devices" on sdk and i got this:
like is partially recognizing the device..
>>can i try flashing a TWRP.img? or what i did has broken other than recovery partitIon on the devices and that wont solve my problem..
i also founded this: http://forum.xda-developers.com/showthread.php?t=2582142 but dont know if will help me..
thanks so much for triying to help me.
Click to expand...
Click to collapse
Damn please report back if you resolve your issue. I'm sure you'll help anyone else who might themselves in a similar situation
You can install the Stock ROM For KDZ file, the G2 will be restored...
Search in Google/Youtube: Back To Stock ROM LG G2
PS. You can only enter the Download Mode with the G2 connected with PC by USB
he can't enter dld mode.
1. download autorec for your version
2. extract aboot - boot - laf
3.
fastboot flash aboot aboot.img
fastboot flash boot boot.img
fastboot flash laf laf.img
I did the same thing. Recovered by flashing the correct laf.img with fastboot, which repaired download mode. Then use download mode with a .kdz file and the (un)official LG rescue tool.
Sent from my LG-D801 using XDA Free mobile app
did you readed the title of mi post???
NO DOWNLOAD MODE...
@bender_007 @jug6ernaut@ahilliard
really thanks:laugh: ill do it as soon as i get in my house.
i was thinking to flash all the partitions since i didn´t know which one had the DOWNLOAD MODE xD, thanks again
elmy2424 said:
@bender_007 @jug6ernaut@ahilliard
really thanks:laugh: ill do it as soon as i get in my house.
i was thinking to flash all the partitions since i didn´t know which one had the DOWNLOAD MODE xD, thanks again
Click to expand...
Click to collapse
Just the ones I wrote. Don't touch others.
Solved
elmy2424 said:
Solved
Click to expand...
Click to collapse
I'm sorry that I write here but if I do not want to create a new topic. Maybe someone is able to help?
Hello my problems started up in the morning as I came up with a kernel update.
Mistakenly threw versions of the D800 and the phone went into fastboot.
I tried the method with a live CD of Ubuntu but it does not fit me these many partitions so I can not write it these paintings partition.
I tried to unpack the correct kernel to a file boot.img fastboot flash I uploaded by write and quite like to be spoiled because I wrote that there is no certificate or something - so as to completely fell boot.
But after some time did enter into download mode I uploaded versions V220D and went.
Now phone can enter to download mode but charges only to the logo and the LED flashes blue and green.
The computer sees the phone software from LG emergency phone does not play because he writes with is the newest version but see the battery level and what I currently versions.
What else to do to restore phone?
I would be very grateful.
will find some time for you later
bender_007 said:
will find some time for you later
Click to expand...
Click to collapse
thank you very much
sarzyk said:
thank you very much
Click to expand...
Click to collapse
hm..I see you managed to flash the rom ?
so the problem is you didn't wipe.
turn the device OFF
hold power + volume down until you see the LG logo, release the buttons for a moment and then hold volume down + volume up. On the white screen confirm 2-3 times with power button. After the factory reset (the thing you just did) it will boot.
bender_007 said:
hm..I see you managed to flash the rom ?
so the problem is you didn't wipe.
turn the device OFF
hold power + volume down until you see the LG logo, release the buttons for a moment and then hold volume down + volume up. On the white screen confirm 2-3 times with power button. After the factory reset (the thing you just did) it will boot.
Click to expand...
Click to collapse
you are a god.
Cleans all day interencie but nowhere have written about this to keep the volume + and - raze ..
For now operates proof, and write exactly what and how.
We would like to thank my friend.
Please write more as I'll official* Rom from LG is the site can check if a ROOT or another Rom if it was uploaded?
Where can I check whether they were any signs of interference?
Is it only in Download Mode it says?
Hi guys, this is my first time posting problems like these as I've never encountered anything I can't fix by myself or with help from fine developers and the community here, but now I'm desperate so I wanted to give it a shot.
Anyways here's what happened. My battery died, along with my USB port (the latter of physical damage - it's not burned just the port got damaged from usage I guess). Anyways, I got original replacement parts, put them in all good. And now when I plug in the charge cable, the LED briefly flashes green and after that nothing happens. However, I found out that if I hold power and volume down and plug in the USB cable then, bootloader turns on. It's interesting how the bootloader was marked as locked even though I unlocked it ages ago. Anyways, when I try to start it normally it shows the Google logo, and after a second or so, it shuts down completely (after the screen goes off, the green LED flashes again). I tried doing rebooting bootloader and recovery, same thing occurs. I tried using factory images and here's the weird/interesting part. When I manually flash the images from the latest 5.1.1 set, everything passes except when I tried doing fastboot flash data userdata.img . It downloads as it should, but it stops after the write part (it says that it can't flash a filesystem with type ' ' - Same goes for fastboot format and fastboot wipe and fastboot erase). However, when I use flash-all batch, it passes as it should (write phase included - or that's at least what it says), but still, the phone won't turn on. I can't do fastboot boot recovery.img as it gives the same result. I should note that I did try fastboot oem unlock, and it pops up the confirmation screen and all, and when I press yes, it works as it should, unlocks the bootloader (I know since when I booted into bootloader again, it showed that it's unlocked, and on the Google logo it shows the little symbol on the bottom), but shuts down on the Google logo again. Flashing any other custom made image (for example this http://dmitry.gr/index.php?r=06.+Thoughts&proj=02.%20Android%20M%20on%20Nexus4 Android M image) gives the same outcome. I really ran out of ideas and could appreciate any help or at least ideas on what could be broken on it so I can let it rest in peace.
Also might be noteworthy that my Ubuntu didn't recognize anything when I attached it in fastboot. As in nothing happened.
Here are screenshots of the fastboot output if someone's interested (ignore the red marking on the screenshot, it was for a friend ):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think you flash the recovery the wrong way.
To flash via fastboot, this is the command:
fastboot flash recovery twrp-2.8.x.x-xxx.img
Source: http://androiding.how/how-to-install-twrp-recovery-via-fastboot/
You tried to flash a recovery in the kernel location.
To flash a kernel via fastboot:
fastboot flash boot boot_name_img
dcop7 said:
I think you flash the recovery the wrong way.
To flash via fastboot, this is the command:
fastboot flash recovery twrp-2.8.x.x-xxx.img
Source: http://androiding.how/how-to-install-twrp-recovery-via-fastboot/
You tried to flash a recovery in the kernel location.
To flash a kernel via fastboot:
fastboot flash boot boot_name_img
Click to expand...
Click to collapse
Yeah sorry those are typos, I came from work and I was tired as hell while I was posting this. If you are referring to the first screenshot, I wasn't flashing the recovery, I was simply trying to boot it off my PC without actually flashing it. Anyways, the recovery flash that I did afterwards was ok, as well as any other except for /data. I think that's the culprit, but it still wouldn't explain why the phone shuts down as soon as it tries to (at least to my understanding) load the kernel. Boot.img is ok, so that can't be the problem.
Hi,
Have you had any luck? I am having the exact same problem with my new battery and charging port replacement which are all genuine parts.
Thanks
Hi, i have Zenfone 5 with stock rom "2.19.40.18" KK 4.4.2
How uninstall Droidboot??
I have been problem with GSM signal and this problem isn't solved. I want return back this phone to Asus while i have warranty.
Thank you for help
You should lock bootlaoder using unoffical unlock method.
link? i have tried lock with ZenfoneAssist and didn't work
Simply flash raw fw..thats it..
Everything will become factory default including the bootloader locked....
prathmesh pande said:
Simply flash raw fw..thats it..
Everything will become factory default including the bootloader locked....
Click to expand...
Click to collapse
i have stock firmware.. but (sadly) still with droidboot..
link raw firmware to try again?
Simple download 2.22.40.54 fastboot (or any fastboot image from any KitKat firmware) and flash it using:
fastboot flash fastboot fastboot.img
leonardohenrique10 said:
Simple download 2.22.40.54 fastboot (or any fastboot image from any KitKat firmware) and flash it using:
fastboot flash fastboot fastboot.img
Click to expand...
Click to collapse
i tried and still with droidboot..
LukyCami said:
i tried and still with droidboot..
Click to expand...
Click to collapse
Then use the xfstk method, and after finished, sideload the firmware you want.
leonardohenrique10 said:
Then use the xfstk method, and after finished, sideload the firmware you want.
Click to expand...
Click to collapse
i'm not bricked, or stuck on usb logo, i just haven't got gsm signal and i want give revert back zenfone to rma.
android is working, but with droidboot which i don't want
LukyCami said:
i'm not bricked, or stuck on usb logo, i just haven't got gsm signal and i want give revert back zenfone to rma.
android is working, but with droidboot which i don't want
Click to expand...
Click to collapse
If "fastboot flash fastboot fastboot.img" doesn't work, the only way I know to revert back to fastboot is using xfstk...
LukyCami said:
i'm not bricked, or stuck on usb logo, i just haven't got gsm signal and i want give revert back zenfone to rma.
android is working, but with droidboot which i don't want
Click to expand...
Click to collapse
"fastboot" is part of the phone.
The only thing that matters is if it is unlocked or locked.
As people said, all you need is a RAW firmware and flash it.
It's very simple.
Here it is a RAW Firmware and use this tool to restore it.
Once you do that, you're good to send your phone to Asus.
dgadelha said:
"fastboot" is part of the phone.
The only thing that matters is if it is unlocked or locked.
As people said, all you need is a RAW firmware and flash it.
It's very simple.
Here it is a RAW Firmware and use this tool to restore it.
Once you do that, you're good to send your phone to Asus.
Click to expand...
Click to collapse
hi,
so i flashed via zenfone assist, again still with droidboot menu..
here is screen from zenfoneassist with FAILED (fastboot erase spare) problem is here?
please help me, thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: ADDED PHOTO DROIDBOOT
LukyCami said:
hi,
so i flashed via zenfone assist, again still with droidboot menu..
here is screen from zenfoneassist with FAILED (fastboot erase spare) problem is here?
please help me, thanks
View attachment 3811801
EDIT: ADDED PHOTO DROIDBOOT View attachment 3811812
Click to expand...
Click to collapse
Hi.
Your phone is now back to original state.
As you can see, sometimes it appears
Code:
(bootloader) secure device
There's no why to worry about "FAILED" on erase spare.
And, you can't remove droidboot, it's part of the phone.
Your phone is now ready to be sent to Asus.
Thanks.
dgadelha said:
Hi.
Your phone is now back to original state.
As you can see, sometimes it appears
Code:
(bootloader) secure device
There's no why to worry about "FAILED" on erase spare.
And, you can't remove droidboot, it's part of the phone.
Your phone is now ready to be sent to Asus.
Thanks.
Click to expand...
Click to collapse
What happen if asus support recognize droidboot? reject rma? thanks
LukyCami said:
What happen if asus support recognize droidboot? reject rma? thanks
Click to expand...
Click to collapse
As I said, droidboot is part of your phone, you can't simply remove it.
Your phone comes with that when you buy it.
What RMA checks is if it is unlocked or locked, and as you restored the RAW file, it is locked, which is the original state.
You can send your phone to ASUS without any worries.
dgadelha said:
As I said, droidboot is part of your phone, you can't simply remove it.
Your phone comes with that when you buy it.
What RMA checks is if it is unlocked or locked, and as you restored the RAW file, it is locked, which is the original state.
You can send your phone to ASUS without any worries.
Click to expand...
Click to collapse
okay, last question null imei does not matter on rma?
LukyCami said:
okay, last question null imei does not matter on rma?
Click to expand...
Click to collapse
I think they will try to fix it.
Happened when I was updating twrp:
I downloaded the .img from their website, booted into my older version of twrp, went to flashing pressed the butting in the bottom right corner, selected the file and selected 'recovery'
Said it was successful, so I rebooted, then it wouldn't do anything anymore except for fastboot.
1. Can't boot into recovery
2. Can't boot normally
3. USB debugging disabled
4. oem locked
Only thing I can enter is fastboot.
I followed this guide, but no luck on my end.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Have you tried this?
http://forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606
and
All in one toolbox by mauronofrio.
I my self had lost recovery myself and flashed stock image in toolbox and then flashed image from above link to restore to stock and started custom rom process again.
Should not erase twrp once recovered if it has reflash your previous version of twrp or hybrid version.
Hope this helps.
passion8059 said:
Have you tried this?
http://forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606
and
All in one toolbox by mauronofrio.
I my self had lost recovery myself and flashed stock image in toolbox and then flashed image from above link to restore to stock and started custom rom process again.
Should not erase twrp once recovered if it has reflash your previous version of twrp or hybrid version.
Hope this helps.
Click to expand...
Click to collapse
It's no use because oem is locked. That means I can't flash anything.
toolbox should still help you unlock bootloader again
Just use the Qualcomm factory restore image to return the phone to original shape of things.
passion8059 said:
toolbox should still help you unlock bootloader again
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pitrus- said:
Just use the Qualcomm factory restore image to return the phone to original shape of things.
Click to expand...
Click to collapse
I have no idea how I would do this without being able to flash anything.
Do you mean that the Qualcomm download program also crashes like fastboot? Sounds like you either have some problems with your windows installation or perhaps you haven't searched for and downloaded the Qualcomm restore if your still trying to flash the ordinary way instead of the emergency way.
Was able to fix it when I was messing around. Not sure what I did but it worked.
Thank you for all your help guys
Theevilsocks said:
Was able to fix it when I was messing around. Not sure what I did but it worked.
Thank you for all your help guys
Click to expand...
Click to collapse
I'm having this problem too, and this isn't helpful. What were the last steps, or at least some of them, that you took to get it working? Which toolkit/script/program were you using? etc
Redjax said:
I'm having this problem too, and this isn't helpful. What were the last steps, or at least some of them, that you took to get it working? Which toolkit/script/program were you using? etc
Click to expand...
Click to collapse
I used this tool: http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
I fiddled around a bit with it, but I'm not sure what I did, and I already deleted the files.
Theevilsocks said:
I used this tool: http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
I fiddled around a bit with it, but I'm not sure what I did, and I already deleted the files.
Click to expand...
Click to collapse
Literally JUST finished with this guide, and my OP2 is alive again! I was going to come back and post. Thanks for the link.
Anyone trying to use this guide without success:
There's one very important step I somehow missed. You MUST disconnect your phone, hold the power button for ~15-20 seconds until it's off, and hold the Volume+ button, THEN plug it back in. Your computer will make the "device connected" sound, but the screen will stay black. THIS IS OK! That means you're in a special recovery, which is where you need to be for the tool.
I also installed the certificate file in the folder I downloaded, then rebooted (it did not work before a reboot, but did work after).
So, the steps:
1. Download the files, make sure your signature signing for drivers is off.
2. Install the trusted certificate, then the driver.
3. Reboot PC
4. Power off phone (hold power for 15-20 secs), hold volume+, then connect through USB (wait for device connected sound, screen on phone will still be black)
5. Run the tool (I ran as admin, not sure if that's required)
6. Weep with joy that you finally found a solution that works.
Hello Everyone, my Huawei Y6 (SCL-L21) is dead, it doesn't power up anymore so no fastboot or recovery (I think damaged GPT Table), when I connect it to my pc, I have a qualcomm serial port and phone's led start blinking red...
Let me say that I have the original firmware downloaded some time ago (it's an UPDATE.APP) and looking inside that file I found the original GPT table (and all the others partitions), so I think that nothing is lost!
So I need help restoring the firmware using tools like QPST or any tool that can "rewrite" my original firmware, any advice or help to guide me in this journey?
P.S: Here's some partitions found inside the original GPT table (with a tool that I developed for this "occasion" [sorry for the software name])
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Darkness1 said:
Hello Everyone, my Huawei Y6 (SCL-L21) is dead, it doesn't power up anymore so no fastboot or recovery (I think damaged GPT Table), when I connect it to my pc, I have a qualcomm serial port and phone's led start blinking red...
Let me say that I have the original firmware downloaded some time ago (it's an UPDATE.APP) and looking inside that file I found the original GPT table (and all the others partitions), so I think that nothing is lost!
So I need help restoring the firmware using tools like QPST or any tool that can "rewrite" my original firmware, any advice or help to guide me in this journey?
P.S: Here's some partitions found inside the original GPT table (with a tool that I developed for this "occasion" [sorry for the software name])
Click to expand...
Click to collapse
Is ur boot loader unlocked
Amaan007 said:
Is ur boot loader unlocked
Click to expand...
Click to collapse
Yes, it was unlocked (before flashing a wrong rom, overwriting the damned gpt)
Darkness1 said:
Yes, it was unlocked (before flashing a wrong rom, overwriting the damned gpt)
Click to expand...
Click to collapse
Extract system IMG ,boot.IMG and recovery IMG and flash them with fastboot
Amaan007 said:
Extract system IMG ,boot.IMG and recovery IMG and flash them with fastboot
Click to expand...
Click to collapse
Sorry, but if you look at my first post you will see that my phone doesn't power up anymore, so fastboot it's impossible (that's why I wrote Hard Brick)
Darkness1 said:
Sorry, but if you look at my first post you will see that my phone doesn't power up anymore, so fastboot it's impossible (that's why I wrote Hard Brick)
Click to expand...
Click to collapse
OK take the battery out connect the phone to a PC and then hold down volume down before connecting and of boots up to fastboot put the if it boots up put the battery back in and let it charge for 10 mins and the flash stock rom
Sent from my GT-I9506 using Tapatalk
Amaan007 said:
OK take the battery out connect the phone to a PC and then hold down volume down before connecting and of boots up to fastboot put the if it boots up put the battery back in and let it charge for 10 mins and the flash stock rom
Sent from my GT-I9506 using Tapatalk
Click to expand...
Click to collapse
Already tried hundreds of times but do not work, that's why I say that it's Hard Bricked, GPT is dead and gone, so every Huawei method will not work (even putting dload folder with UPDATE.APP on an sd card)
Darkness1 said:
Already tried hundreds of times but do not work, that's why I say that it's Hard Bricked, GPT is dead and gone, so every Huawei method will not work (even putting dload folder with UPDATE.APP on an sd card)
Click to expand...
Click to collapse
hello,yesterday i have scl-l21 bad emmc health.
n now i've change with new emmc.unfortunately my phone cant't connect to network.i'n need to unlock bootloader.so i went to huawei unlock page.after get unlock code,but it come useless.remote say invalid code.can you upload your sbl1 n aboot partition for me?
after that,i'll give you rawprogram0.xml,so you cant revive your phone from bricked.thanks
vrizz said:
hello,yesterday i have scl-l21 bad emmc health.
n now i've change with new emmc.unfortunately my phone cant't connect to network.i'n need to unlock bootloader.so i went to huawei unlock page.after get unlock code,but it come useless.remote say invalid code.can you upload your sbl1 n aboot partition for me?
after that,i'll give you rawprogram0.xml,so you cant revive your phone from bricked.thanks
Click to expand...
Click to collapse
Here's your files, taken from the stock firmware of scl-l21
https://sendit.cloud/8rqxtnkl2fc7
https://sendit.cloud/xfbbpl0v631r
Did you replace your emmc? or did you recovered from hard brick?
https:// drive.google. com/file/d/1ZPHjWy1qqF1g9OP6s7DLbJxpH0vNNHL6/view
those my backup
When you connect your phone with your pc is it detected at all?
-If yes,
What's the driver's name?
Does the name of it include something like HS-USB?
Please let me know if your phone haven't been repaired yet.
when i connect huawei scl-u31 it appears like " unkown device" in device manager !! i installed drivers qualcoom but always shown unkonwn device!!!
what to do?