Related
I seem to have got myself into a bit of a pickle here.
I had a rooted N7 on 4.2.2. Tried to unroot (in lieu of going up to 4.3). Disaster struck! It wouldn't boot. It would just get stuck at the bootloader and go "Booting failed" or something similar.
So bother, I could get into the bootloader. So I tried to fastboot flash a stock image using this (http://forum.xda-developers.com/showthread.php?t=1907796) guide.
I got a bit further now, it would get the X loading screen but then no amount of waiting would have it boot.
So I tried factory reset from the recovery menu (the one with the Android and the red triangle).
No good, still did the same thing.
So I tried using Nexus Root Toolkit to flash stock + unroot from a soft-bricked/bootloop state. Nope! No good. Still does the same thing.
I've been through every combination of flashing, clearing, resetting but to no avail!
I've tried flashing CWM and TWRP but when I try to get into recovery mode, I just get the Google logo forever. This is a nightmare!
What's going on Have I managed to brick this thing...
evenstevens said:
I seem to have got myself into a bit of a pickle here.
I had a rooted N7 on 4.2.2. Tried to unroot (in lieu of going up to 4.3). Disaster struck! It wouldn't boot. It would just get stuck at the bootloader and go "Booting failed" or something similar.
So bother, I could get into the bootloader. So I tried to fastboot flash a stock image using this (http://forum.xda-developers.com/showthread.php?t=1907796) guide.
I got a bit further now, it would get the X loading screen but then no amount of waiting would have it boot.
So I tried factory reset from the recovery menu (the one with the Android and the red triangle).
No good, still did the same thing.
So I tried using Nexus Root Toolkit to flash stock + unroot from a soft-bricked/bootloop state. Nope! No good. Still does the same thing.
I've been through every combination of flashing, clearing, resetting but to no avail!
I've tried flashing CWM and TWRP but when I try to get into recovery mode, I just get the Google logo forever. This is a nightmare!
What's going on Have I managed to brick this thing...
Click to expand...
Click to collapse
Hey,
did you try doing all these manually :
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot -w update image.zip
PS : Edit these according to images you are trying to flash.
You mentioned you tried the guide but try this once again.
Unlock your bootloader / keep your bootloader unlocked while doing this.
If you want to you can even try running the .bat files and / or .sh files while in the bootloader.
If it still doesnt work , download the latest custom recovery and just try flashing it through
Code:
fastboot flash recovery recovery.img
Please mention the errors you have a bit more in detail during these steps !
Red Devil said:
Hey,
did you try doing all these manually :
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot -w update image.zip
PS : Edit these according to images you are trying to flash.
You mentioned you tried the guide but try this once again.
Unlock your bootloader / keep your bootloader unlocked while doing this.
If you want to you can even try running the .bat files and / or .sh files while in the bootloader.
If it still doesnt work , download the latest custom recovery and just try flashing it through
Code:
fastboot flash recovery recovery.img
Please mention the errors you have a bit more in detail during these steps !
Click to expand...
Click to collapse
Okay, I've managed to get TWRP up and running.
Now... how do I get a ROM onto there to try to flash? >_<
PS. I did all those commands manually many many times. It's got to a stage now where the X logo never actually comes up... Just the Google logo and the little padlock
evenstevens said:
Okay, I've managed to get TWRP up and running.
Now... how do I get a ROM onto there to try to flash? >_<
PS. I did all those commands manually many many times. It's got to a stage now where the X logo never actually comes up... Just the Google logo and the little padlock
Click to expand...
Click to collapse
Code:
adb sideload ROM.zip
in advance options > adb sideload
And about the ROM getting stuck at the Nexus boot animation , try getting a logcat.. maybe that will help. !
Red Devil said:
Code:
adb sideload ROM.zip
in advance options > adb sideload
And about the ROM getting stuck at the Nexus boot animation , try getting a logcat.. maybe that will help. !
Click to expand...
Click to collapse
Amazing. I actually managed to flash a copy of Cyanogen on there and it all booted perfectly.
Now I wonder if I can get it back to stock from here easily..
Thanks
evenstevens said:
Amazing. I actually managed to flash a copy of Cyanogen on there and it all booted perfectly.
Now I wonder if I can get it back to stock from here easily..
Thanks
Click to expand...
Click to collapse
You can ... just make sure you have downloaded the right factory images and flash the use the .bat / .sh to flash the images .. keep in mind that you will lose all your data including that on the internal sd. All the best
Red Devil said:
You can ... just make sure you have downloaded the right factory images and flash the use the .bat / .sh to flash the images .. keep in mind that you will lose all your data including that on the internal sd. All the best
Click to expand...
Click to collapse
So I tried to reflash a stock image... same issue again! Just freezing at the Google logo screen :/
Properly stumped as to why it's doing that. Maybe I'm stuck with Cyanogen...
evenstevens said:
So I tried to reflash a stock image... same issue again! Just freezing at the Google logo screen :/
Properly stumped as to why it's doing that. Maybe I'm stuck with Cyanogen...
Click to expand...
Click to collapse
So close...
Downloaded the new SDKs from Google and managed to actually flash and get into a stock version of Android... but it's constantly saying "Google keyboard has stopped working! Launcher has stopped working! etc" and it's practically useless
Gaaaaaaaaah
evenstevens said:
So close...
Downloaded the new SDKs from Google and managed to actually flash and get into a stock version of Android... but it's constantly saying "Google keyboard has stopped working! Launcher has stopped working! etc" and it's practically useless
Gaaaaaaaaah
Click to expand...
Click to collapse
Okay my solution to this:
Just keep flashing it with the flash-all.bat command until it just... worked.
Must've done it about 15 times.
Well that's that ordeal over.
Hello to everybody, so i was thinking my nakasi was really dead this time, the last thing i did was flashing a 5.1.1 rom next when i rebooted got stuck on lolipop boot loop so i restarted the tablet
manually to access the recovery, and to my awe, i couldn't no more access the recovery ! (latest twrp) tried again and again nothing, no recovery no bootloader, can't start the OS
always stuck on google logo with the options above, start, bootloader, recovery etc, today i realized i could access the bootloader and fastboot mode (ADB recognize my device when i type fastboot devices)
so i tried flashing stock image and stuff with no luck, tried many stock roms, tried wug's toolkit and the flash all.bat still no luck, i get all kind of error messages here is a screenshot, help is really appreciated if there is anything i can do to save it :
View attachment 3305126
the problem seems to be that i can't write the things i send to the tablet via ADB, tried the NVflash recovery today and got :
View attachment 3306049
Have you tried not imputing the full file address as you have the emulator already running from that location.
So recovery command would be.
Fastboot flash recovery "name of recovery Img file here"
Just make sure that the image file is in the platform-tools folder.
Probably not your issue but its going to save you some typing.
Good luck
gaosphappy said:
Have you tried not imputing the full file address as you have the emulator already running from that location.
So recovery command would be.
Fastboot flash recovery "name of recovery Img file here"
Just make sure that the image file is in the platform-tools folder.
Probably not your issue but its going to save you some typing.
Good luck
Click to expand...
Click to collapse
Thank you for the tip I'll certainly use it, but i don't think it is the culprit since as you can see in the screenshots
the files get sent successfully but cannot be written, my bootloader is unlocked by the way
Homurato said:
Thank you for the tip I'll certainly use it, but i don't think it is the culprit since as you can see in the screenshots
the files get sent successfully but cannot be written, my bootloader is unlocked by the way
Click to expand...
Click to collapse
Did you try the latest factory image? I noticed you are flashing a very old bootloader, possibly the first one? 4.23 is the current version.
Where is flatline_grouper.img coming from? I've never seen that.
adomol said:
Did you try the latest factory image? I noticed you are flashing a very old bootloader, possibly the first one? 4.23 is the current version.
Where is flatline_grouper.img coming from? I've never seen that.
Click to expand...
Click to collapse
Hello kind sir, of course at first i tried the 5.1.1 full factory image with the NRT toolkit and got the same writing errors next i tried many bootloaders
(one of them found it here as a 100% working bootloader) the Flatline is the recovery of the NVflash tool where you can access it to unbrick full bricked N7s
if you got blobs.bin of your N7 backed up (clearly not my case)
the flashing writing error i get it with everything i try to flash, recoverys bootloader system etc
when i send them with the flash all command they got sent to the tablet okay, but when writing i get the errors
i don't know but there is a small informations if that can help, before it broke my system was in EXT4 and all the rest in F2FS
It's entirely possible your memory has failed. I'm reading more and more people running into corrupted memory issues.
You can get a replacement motherboard cheap on eBay if nothing else works.
fwayfarer said:
It's entirely possible your memory has failed. I'm reading more and more people running into corrupted memory issues.
You can get a replacement motherboard cheap on eBay if nothing else works.
Click to expand...
Click to collapse
I'm still hoping for a software solution since my fastboot works fine, I'll let the motherboard solution my last i guess
Hello some news about the still staggering situations : when the tablet is off and i put the charger i get the battery refiling animation ! so that mean the bootloader isn't broken
and i still can access fastboot mode, even when i push a bootloader i get a signature match message, but the problem is still that the things i push can't be written as i'm still getting a :
FAILED <Remote: <FileWriteFailed>> changed usb cables, changed ports, the last time the tablet was working i had the system on EXT4 and the rest on F2FS, maybe if i can convert everything to EXT4 ?
So this is what happened, I was on I MedroM v3, so I was there was a firmware in beta (the 7.0 update) so I've done it and now I'm stuck in a bootloop
, I flashed the Nougat recovery so it locked my bootloader
and removed TWRP so I can't even go to flash the old rom
again. I also can't get the product id now cause I don't have an OS installed, there's no way to pull it without it an OS. I have tried every existing method possible and nothing (including the sd
card method with update.app and bla bla bla)
So I can't flash files through fastboot It says " Command not allowed"
Can somebody please help me, I have experience with flashing and everything but I in my entire life have not seen that a phone company so big doesn't have a ******** flashtool
or some other way of recovering hard bricked devices instead of buying a new motherboard or something..
If somebody could help me I would be so grateful! Please excuse my language I'm very mad and frustrated, I need my phone for work and now I'm offline..
- Fastboot is available but the bootloader is locked
- No TWRP
- No OS Installed
Download a firmware you want, extract the update.app and put it in sd card folder. From the phone completely shutdown, press vol +, vol - and power at the same time hold it until the updater with percentage progress moving appears.. you should be fine after that.. ? i believe. Maybe try it. That's what i did on my case
No, It says "Software Install failed! Incompatability with current software version"
When I go to eRecovery t says that it cant connect to WIFI.
As I said i tried every known method and I can't get it to work. Spent my whole day trying to fix it, I'm out of ideas
akseon said:
So this is what happened, I was on I MedroM v3, so I was there was a firmware in beta (the 7.0 update) so I've done it and now I'm stuck in a bootloop
, I flashed the Nougat recovery so it locked my bootloader
and removed TWRP so I can't even go to flash the old rom
again. I also can't get the product id now cause I don't have an OS installed, there's no way to pull it without it an OS. I have tried every existing method possible and nothing (including the sd
card method with update.app and bla bla bla)
So I can't flash files through fastboot It says " Command not allowed"
Can somebody please help me, I have experience with flashing and everything but I in my entire life have not seen that a phone company so big doesn't have a ******** flashtool
or some other way of recovering hard bricked devices instead of buying a new motherboard or something..
If somebody could help me I would be so grateful! Please excuse my language I'm very mad and frustrated, I need my phone for work and now I'm offline..
- Fastboot is available but the bootloader is locked
- I can't boot into TWRP
- No OS Installed
Click to expand...
Click to collapse
I had the same problem, but with the L31.
First try to use https://www.xda-developers.com/how-to-install-twrp/
Then with the file i send you attached (MAF32)
- Fastboot flash boot boot.img
- Fastboot flash system system.img
- Fastboot flash cust cust.img
- and finally TWRP
After that i puted the first exctrated uppdate.pp in my memory card and with the "3 buttons" process i flashed it. Then i repeated the same process with the second one (http://forum.xda-developers.com/hua...droid-nougat-dev-build-huawei-t3488360/page33). After this finished, again with the 3 buttons i made a factory reset.
5 minutes later, it was working.
i don't understand how to boot to fastboot ? and where to get these img files i am really stuck here pleaase
You don't understand, In order to unlock the bootloader i need the product ID which you get by typing some number combination in the dialer. I cant get to the dialer cause I dont have any OS installed, cause the old was dirty flashed. So thats why i cant flash TWRP etc..
hello, i'm using Huawei P9 Lite VNS-L21. i tried to flash the stock nougat Firmware Which i actually did and it worked flawless! but there was a little problem because there wasn't any Software update option in there, so after that i wanted to downgrade to stock MM. IDK what happened wrong while installing that, my phone got BRICKED. i don't have the Erecovery and twrp either. i cant flash firmware via DLOAD Method. the only thing i have is FASTBOOT mode..
i tried literally everything.. but nothing working..
I sent it to HUAWEI CUSTOMER CARE and they returned it back after a couple of days...
im really very worried because ive been using this phone for like 2 months ... and now im helplesss, If anybody is reading this please help/ assist me out of this.. i'd be really greatfull if anybody's going to help me out..
hash26 said:
hello, i'm using Huawei P9 Lite VNS-L21. i tried to flash the stock nougat Firmware Which i actually did and it worked flawless! but there was a little problem because there wasn't any Software update option in there, so after that i wanted to downgrade to stock MM. IDK what happened wrong while installing that, my phone got BRICKED. i don't have the Erecovery and twrp either. i cant flash firmware via DLOAD Method. the only thing i have is FASTBOOT mode..
i tried literally everything.. but nothing working..
I sent it to HUAWEI CUSTOMER CARE and they returned it back after a couple of days...
im really very worried because ive been using this phone for like 2 months ... and now im helplesss, If anybody is reading this please help/ assist me out of this.. i'd be really greatfull if anybody's going to help me out..
Click to expand...
Click to collapse
Why don't you flash TWRP in fastboot mode?
fasboot flash recovery recovery.img
PS: You need to start your own thread, really, rather than hijack someone else's
StrangerWeather said:
Why don't you flash TWRP in fastboot mode?
fasboot flash recovery recovery.img
PS: You need to start your own thread, really, rather than hijack someone else's
Click to expand...
Click to collapse
I'm new to this forum, if i did something that i shoud not I'm sorry about that and thanks for replying..
Ive tried many times to flash twrp recovery through fastboot it says installed but when i try to go to recovery there isnt any recovery...
i have a post with a same problem but with frp active, any sugestions?
hash26 said:
I'm new to this forum, if i did something that i shoud not I'm sorry about that and thanks for replying..
Ive tried many times to flash twrp recovery through fastboot it says installed but when i try to go to recovery there isnt any recovery...
Click to expand...
Click to collapse
What happens when you type : adb reboot recovery?
StrangerWeather said:
What happens when you type : adb reboot recovery?
Click to expand...
Click to collapse
Nothing happens it just reboots itself again n again but recovery doesn't open itself
hash26 said:
Nothing happens it just reboots itself again n again but recovery doesn't open itself
Click to expand...
Click to collapse
Ok, this is what I would do if I were you. I would pick a rom in the development section, eg. RR. Then I would extract it and get the system image and boot image and fastboot flash them. To extract the rom, use SuperR's Kitchen.
Hope this helps.
StrangerWeather said:
Ok, this is what I would do if I were you. I would pick a rom in the development section, eg. RR. Then I would extract it and get the system image and boot image and fastboot flash them. To extract the rom, use SuperR's Kitchen.
Hope this helps.
Click to expand...
Click to collapse
I'm about to do this! Thanks you
StrangerWeather said:
Ok, this is what I would do if I were you. I would pick a rom in the development section, eg. RR. Then I would extract it and get the system image and boot image and fastboot flash them. To extract the rom, use SuperR's Kitchen.
Hope this helps.
Click to expand...
Click to collapse
thank you so much for replying but there is something i want to ask you about..
the tool you told me about "SuperR's Kitchen" works on Linux.. and i'm a windows user is there any other software that runs on Windows and works as same as super'R ..
Waiting for your reply!!
hash26 said:
thank you so much for replying but there is something i want to ask you about..
the tool you told me about "SuperR's Kitchen" works on Linux.. and i'm a windows user is there any other software that runs on Windows and works as same as super'R ..
Waiting for your reply!!
Click to expand...
Click to collapse
Hi!
There is this but I haven't tested it: https://forum.xda-developers.com/android/help/extract-dat-marshmallow-lollipop-easily-t3334117
Let us know how it goes!
Hi. Looks like I fkced my phone. Was using Darkobas twrp, flashed this room and it boot-looped at the beginning (phone was turning on and off on the "Coolpad" screen). I can enter the recovery however can't transfer roms into the card. While pushing big files with ADB push (it takes few minutes) it randomly stops responding/hangs in the middle of a transfer. Tried multiple times and it stops randomly ( I've wiped/formatted whole storage )
I managed to flash another recovery 3.1.0.0 but still I need to push some rom to see if I can flash it. After PC reboot it stopped detecting my phone...
Fastboot is not working, power + vol down goes to black screen / turning off the phone.
Tool_all_in_one does not detect my phone. In fact I do not see it in Windows Device Manager. Tried different usb 3/2 ports
Commands in console like fastboot oem device info gives:
< waiting for any device >
adb reboot bootloader gives:
adb server version (39) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found
It's done guys?
Update: somehow managed to restore connection, so phone is visible in Device Manager as "Android Composite ADB Interface" .
Managed to push AICP ROM with adb but can't see it on sdcard. Usually, it was in the main directory, now nothing is there.
Adb sideload? It still seems to me like youre having connection issues w/the pc. Tried rebooting to fastboot from twrp menu?
1 - Enter Twrp Recovery
2 - Wipe -> Format Data then type "yes". This command gonna wipe your internal storage behold.
3 - After this reboot recovery and go to mount then enable mtp.
4 - Transfer rom file.And after a clean wipe flash it.
That rom have bootloader and some modem file that can bring up some issue mate.And those files belongs to Changer not to our beast.
Both device very very familiar but its different product anyway you can't trust it.
I RECOMMEND ALL OF PEOPLE GONNA FLASH ROM please first check the firmware files .If there, then clean it and wipe from the updater-script.
For an alternative you can flash your stock firmware files from QFİL but it's risky too.
Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries, I managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?
Thes1ev said:
Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?
Click to expand...
Click to collapse
Make sure you are not using a USB hub, or extension cable. Also make sure you are plugged directly into the PC motherboard, not one of the front ports. I had transfers stalling and it was my USB extension cable.
Thes1ev said:
Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries, I managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?
Click to expand...
Click to collapse
Sure, you need to flash the firmware files, download 23s from the official site, and fastboot flash all the files, that'll return you to stock fastboot, splash, etc.
Follow this guide (no need to format data, and flash system again, just the files in firmware update folder).
https://forum.xda-developers.com/le-pro3/how-to/guide-how-to-manually-upgrade-firmware-t3609786
trizex said:
Sure, you need to flash the firmware files, download 23s from the official site, and fastboot flash all the files, that'll return you to stock fastboot, splash, etc.
Follow this guide (no need to format data, and flash system again, just the files in firmware update folder).
https://forum.xda-developers.com/le-pro3/how-to/guide-how-to-manually-upgrade-firmware-t3609786
Click to expand...
Click to collapse
Can't flash anything using fastboot - "fastboot flash xxx.img" gives me: < waiting for any device > and nothing happens.
At the moment trying to flash stock 23s but it's hanging on "Patching system image unconditionally" for 5+ minutes already.
This JUI fcked bootloader in my phone somehow. It's blocked/can't be replaced or no idea what's going on here.
Edit: so ye after 20+ minutes of "Patching system image unconditionally" looks like I'm unable to flash stock 23s using TWRP 3.1.0.0.
Probably it wants to replace this fkn JUI bootloader and freeze there.
Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda
trizex said:
Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda
Click to expand...
Click to collapse
Yap, was flashing official stock 23s from this site via twrp.
Okay today gonna try Alba ROM as you suggested.
trizex said:
Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda
Click to expand...
Click to collapse
That helped, thanks a lot!
Is there any solution to restore Leeco bootloader? I just cant flash anything because device is unknown during fastboot mode. Tried to uninstall and reinstall driver but no luck.
I am stuck with coolpad bootloader which is not recognised from my pc. Serves me right because i didnt check the zip of jui which i flashed that had another bootloader, fml.
If any kind soul has any info on that please say it, thanks.
testreaper said:
Is there any solution to restore Leeco bootloader? I just cant flash anything because device is unknown during fastboot mode. Tried to uninstall and reinstall driver but no luck.
I am stuck with coolpad bootloader which is not recognised from my pc. Serves me right because i didnt check the zip of jui which i flashed that had another bootloader, fml.
If any kind soul has any info on that please say it, thanks.
Click to expand...
Click to collapse
That is litterally what this whole topic was about? See my responses, if you still have access to twrp (dont see why wouldnt you), you can use it to flash a 23s "stock" rom through it (such a package will contain, among others, the leeco bootloader etc)
---------- Post added at 08:00 PM ---------- Previous post was at 07:59 PM ----------
Thes1ev said:
That helped, thanks a lot!
Click to expand...
Click to collapse
Youre welcome, everything back to normal?
trizex said:
Youre welcome, everything back to normal?
Click to expand...
Click to collapse
Yeah, I got rid of this JUBU bootloader after flashing stock-like rom. Also thanks to this there is no more strange noise during the boot sequence.
Thes1ev said:
Yeah, I got rid of this JUBU bootloader after flashing stock-like rom. Also thanks to this there is no more strange noise during the boot sequence.
Click to expand...
Click to collapse
Ya, I heard that squeeling too, when booting, and in fastboot mode
Thes1ev thank you so much pal, i flashed 2 different 23s with all wipes and they gave me errors but your rom installed perfectly.
Alright so where i'm at now is basically the aftermath of a failed attempt to install a cyanogen unofficial rom for my phone.
I have a p9 lite VNS-L23 dual sim and well basically, i unlocked the bootloader and i rooted it with twrp and installed superuser using the srk tool. Everything worked fine up to this point until i booted into recovery, cleared cache and data etc to do a clean install and the install failed with an error code 7.
I thought doing a twrp backup before the flash was effective but because it didnt take any length of time, i sort of thought it definitely wasnt a full backup but i didnt pay it any attention and tried to flash it anyway since iv'e never had probs flashing anything with other of the phones ive had before which was my main mistake.
Usb debugging was enabled before trying to flash. I thought it failed because i didnt change my file system but i had no idea how to do that so i avoided it and tried to install a newer version of twrp to see if the rom would work with the updated version instead. When flashing the twrp img file, it asked where i wanted to install and i think i selected bootloader instead of boot cause there were only 2 options.
After than finished and i chose to restart in recovery, recovery never loaded. I was getting erecovery but that couldnt help me either. I was just stuck with no os and a phone stuck on the bootscreen. I tried to unbrick my phone by installing the update file for the international version firmware which i downloaded which was the only one not to fail after trying 2 others before it before realizing the error i was making. I read online that it would restore my phone back to ofw and that was great considering i had no os installed. Now, after the update, i think i reached like 100% then it went blank. I tried to wait a couple seconds to see if it was rebooting but nothing happened. tried all button combinations with and without the charger for varying lengths of time but no luck. I hear a sound when its connected to my laptop tho so idk if that matters. Its a bit frustrating right now and i have no clue how to fix this problem and i havent even had the phone for a long time. If someone. anyone can help me, id more than appreciate it
So far, nothing is responding to anything. No lights, no vibrations and i dont see anything when it conencts to my laptop, my laptop just makes the connected sound. I see Fastboot 2.0 detected but the srk tool cannot detect any emulators or devices :/ im so depressed at this point. More or less just bought the ****.
Sounds bad, try using the dload method and if that doesn't work you are ******.
What is the output of "fastboot devices"
vidra said:
Sounds bad, try using the dload method and if that doesn't work you are ******.
What is the output of "fastboot devices"
Click to expand...
Click to collapse
its the dload method that has me in this mess. It didnt reboot from the upgrade and since then i think ive been in fastboot mode. I get a response with the fastboot devices cmd and i manage to flash the boot, recovery and system of the stock firmware but still no luck. Think my only option is to use dc phoenix but i cant buy credits for that
bessonster said:
its the dload method that has me in this mess. It didnt reboot from the upgrade and since then i think ive been in fastboot mode. I get a response with the fastboot devices cmd and i manage to flash the boot, recovery and system of the stock firmware but still no luck. Think my only option is to use dc phoenix but i cant buy credits for that
Click to expand...
Click to collapse
Have you tried flashing MM with dload?
vidra said:
Have you tried flashing MM with dload?
Click to expand...
Click to collapse
not getting to the upgrade screen with dload, the phone restarts but nothing on screen. I can use fastboot only to flash and unlock bootloader, check specifications but thats it. I flashed the stock image which is mm thru fastboot but no luck. I read that i might wait for my battery to drain since my battery isnt rly made to be removable. Can i still use dload without any on screen response?
Have you also tried flashing vendor, cust ... partitions ?
vidra said:
Have you also tried flashing vendor, cust ... partitions ?
Click to expand...
Click to collapse
Fastboot doesnt flash certain img's such as xloader etc, no vendor img included inside the update but i doubt i'd be able to flash it anyway, but i flashed everything i was allowed to incl. cust, boot, recovery, system, cache, . Everything else is giving error: command not allowed. I've hit a brick wall so far til my battery drains or i take it to a repair shop which is i guess, last resort. Can't seem to find help anywhere on the internet, nothing returns anything to the screen.
Looks like a hard brick, take it to an official repair shop. But remember: unlocking the bootlader does NOT void the warranty.