Related
Hey, ive recently updated the rom on my phone from cm 6.1 (stable) to cm7 nightly (vendor ace) -
initially i did it to test it and to see if it would fix my problem were the phone screen would automatically turn off when reciveing and sending calls, which resulted in taking out the battery and turning back on(which is now randomly working again)
after i flashed the cm7(via rom mamanger) it worked fine, got back onto the phone and i didnt have market and my phone wasnt connecting to google accounts aswell, so i then installed gapps. it worked the first time and it said it was succesful.
Restarted my phone and its the same, no market..etc..
so i tried it again, same thing, then for some reason when ever i try and load into the recovery from rom manager or from the inital vol - and power, it just freezes on the HTC startup screen.
The only thing i think i may have done different was adding this file to my phone (recovery-ace-3.0.0.5.img) because someone on cm7 told me i needed it, but i have no clue what it was for nor how to load or flash it.
So my main problem is, gapps wouldnt install and now ic ant access the recovery manager either and im getting kinda bored without my precious DHD
Can someone please help me
Just to make this clear, you cannot access your recovery even through bootloader? Can you get to the bootloader?
jkoljo said:
Just to make this clear, you cannot access your recovery even through bootloader? Can you get to the bootloader?
Click to expand...
Click to collapse
i cant access the recovery manager through the boot loader either but yes i can access the boot loader
Okay, then download this file:
http://dl.dropbox.com/u/18138289/reco.img
And then download radio flash.zip from radio.img flash guide sticky, extract it, open "start here", drop reco.img to the radio flash folder and type:
fastboot flash recovery reco.img
Click to expand...
Click to collapse
Your device has to be in bootloader>fastboot mode. After that you can access recovery, do a full wipe and flash CM6.
Ill try this now and reply once its done, erm why flash cm6? or do you think the same fault will happen if i try and reinstall cm7?
do i have to be in the bootloader from the beginning?
plus is there htc sync for MACs?
Thanks alot btw
Well, you can try to flash the cwm 3.img like I described and then install CM7, but I know for sure that the recovery I linked works with CM6.
You have to be in bootloader fastboot when you issue the command, yes.
I do not have a MAC, so I am not really sure. I think that you would have to get Android SDK and forget about radio flash toolkit if you want to use a MAC.
And then download radio flash.zip from radio.img flash guide sticky, extract it, open "start here", drop reco.img to the radio flash folder and type:
right so whilst i do all of this, i need to be in the bootloader > fast boot - sorry just want to clarify, ive not done this before but i have faith!!
Yeah, it does not really matter, but I would put my phone to bootloader fastboot so it is ready. The important thing is that your device is in fastboot mode when you enter the fastboot flash command.
Kool Kool, well thanks alot im going to try this now
right so i successfully entered the recovery, thanks alot for the help with that.
I tried to reinstall cm7 -worked and gapps - said it worked, but it still wont bring up the market app, why is this?
i reinstalled a back up and everything is working again, im so confused why it wont bring up the market app in cm7
o0jaz0o said:
right so i successfully entered the recovery, thanks alot for the help with that.
I tried to reinstall cm7 -worked and gapps - said it worked, but it still wont bring up the market app, why is this?
i reinstalled a back up and everything is working again, im so confused why it wont bring up the market app in cm7
Click to expand...
Click to collapse
when you boot into recovery, not just through rom manager, does it say you have cwm 3.x installed? if so try re-flashing the gapps, if not go back into fastboot and flash cwm3.
Wow, really sorry about that, i thought the cwm was a custom firmware i thought t was optional, sorry for the inconvenience, but thank you alot this has been daunting :/
flashed the right recovery, and everything is working as it should be, thankyou both very much
I updated my android to 4.3. since then I lost the root permissions. The phone shows as being unlocked when I start it up. when I have tried different programs or apps, I can't get the permissions back. One program I have tried, sorry, don't remember the name, said it was going to reboot the phone, but that never happened. I used it with my older version of android and it worked fine.
When I got into recovery mode, I the the android robot with the red !, saying no command.
I wanted to see if anyone knew what might be going on and what I could do to get back my permissions.
Thanks
jrwn said:
I updated my android to 4.3. since then I lost the root permissions. The phone shows as being unlocked when I start it up. when I have tried different programs or apps, I can't get the permissions back. One program I have tried, sorry, don't remember the name, said it was going to reboot the phone, but that never happened. I used it with my older version of android and it worked fine.
When I got into recovery mode, I the the android robot with the red !, saying no command.
I wanted to see if anyone knew what might be going on and what I could do to get back my permissions.
Thanks
Click to expand...
Click to collapse
Android 4.3 contains security fixes that require root to be updated. Download the SuperSu v1.55 zip from http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip and copy the file to the Nexus' internal storage. Reboot the phone to recovery and install UPDATE-SuperSU-v1.55.zip from Clockworkmod or TWRP, then reboot the phone. You should now be able to grant privileges to the apps that require root access.
BobWalker said:
Reboot the phone to recovery and install UPDATE-SuperSU-v1.55.zip from Clockworkmod or TWRP, then reboot the phone. You should now be able to grant privileges to the apps that require root access.
Click to expand...
Click to collapse
The big issue I am running into is when I try to go to recovery, I get the dead android and "no command" error.
jrwn said:
The big issue I am running into is when I try to go to recovery, I get the dead android and "no command" error.
Click to expand...
Click to collapse
you updated stock, so you now have the stock recovery, thats the "dead" android. flash a custom recovery via fastboot, then flash the supersu su binaries via your new custom recovery. youll be fine, make sure to stay away from root toolkits or you will nwver learn anything, like this. this is such a basic thing to know to do, yet people that use root toolkits dont know.
OK, I'll have to try that tonight or over the next couple of days when I have a chance. Thank you.
jrwn said:
OK, I'll have to try that tonight or over the next couple of days when I have a chance. Thank you.
Click to expand...
Click to collapse
if you dont know how, read a little. its really easy. its a matter of typing one line into a command window
OK, I've tried it, but it doesn't seem as if the computer is communicating with the phone. I have also tried one of the auto programs to do it, but it gets stuck at "waiting for device." If I reboot the device and try to get into recovery mode, I just get a dead android saying "no command" I can't get any other options to try to reset the devices back to factory settings.
I have tried the reset option in the settings menu, but It still saves information and doesn't take the phone back to 4.2, which is what I first had.
I'm hoping someone has some ideas on what I can do. On the other hand, I am planning on upgrading my wife's phone. I might just get a new one, and give her this one, although I'm not sure if I want to get a nexus, maybe a different one this time.
jrwn said:
OK, I've tried it, but it doesn't seem as if the computer is communicating with the phone. I have also tried one of the auto programs to do it, but it gets stuck at "waiting for device." If I reboot the device and try to get into recovery mode, I just get a dead android saying "no command" I can't get any other options to try to reset the devices back to factory settings.
I have tried the reset option in the settings menu, but It still saves information and doesn't take the phone back to 4.2, which is what I first had.
I'm hoping someone has some ideas on what I can do. On the other hand, I am planning on upgrading my wife's phone. I might just get a new one, and give her this one, although I'm not sure if I want to get a nexus, maybe a different one this time.
Click to expand...
Click to collapse
install the right drivers. and dont use one of those "auto" programs, thats why you dont know what you are doing now.
simms22 said:
install the right drivers. and dont use one of those "auto" programs, thats why you dont know what you are doing now.
Click to expand...
Click to collapse
I did try to do it manually, the phone didn't respond. This is why I also tried a program. You are correct, I don't know what to do from this point.
jrwn said:
I did try to do it manually, the phone didn't respond. This is why I also tried a program. You are correct, I don't know what to do from this point.
Click to expand...
Click to collapse
you need to get the driver installed to your computer, fastboot as well. when its all ready, open fastboot and a command window then and type.. fadtboot devices. then itll see your device(or not if the driver isnt installed). when it sees your device, you need fastboot flash your recovery.. fastboot flash recovery recoveryname.img. then you need to flash the latest su binaries via your recovery(latest supersu will work).
I'm not sure exactly what I did wrong, but in the process of trying to root my B15 A2017U, it ended up in a state of, I'm guessing, permanent EDL mode. The phone gives absolutely no response to any buttons or attempts to boot it (no vibration, no lights, just a black screen, whether I try to boot normally, boot to recovery, or boot to EDL), it does show up in device manager as Qualcomm HS-USB QDLoader 9008 (COM10), but adb won't recognise it, and it shows up in MiFlash but any attempt to flash anything results in "cannot receive hello packet", "try to reset status" and eventually "error:The write timed out."
I've been reading through a lot of threads here, but at this point I'm pretty much out of ideas, and I'd really like to have a phone for work in 6 hours. Can anyone help, please?
Not sure how useful it will be, but here's everything I can remember about what I've done just so there's something to go on. First, I tried a few days ago as detailed in this post, and put it aside after that post. Aside from not being able to get to recovery at that point, the phone was working perfectly. Today, seeing the new Axon7Toolkit, I decided to give it a try. I managed to unlock the bootloader and get into TWRP recovery (during the process, it asked me for a decryption password and I hit cancel). I've done a lot of reading and searching since then so I can't recall the exact steps I took after that, but I wiped the device (I didn't change the filesystem or anything) and got errors, and then after seeing the "your device can't be checked for corruption" message I searched and found that I need to mount system, so I did so (not in read-only), and wiped again, this time with no error messages. I can't remember if I did anything else in TWRP aside from looking through the options available. After that, I think what I did was "Flash TWRP and/or root" again in Axon7Toolkit, and I think something went wrong at that point. That's pretty much all I know.
Aspoehro said:
I'm not sure exactly what I did wrong, but in the process of trying to root my B15 A2017U, it ended up in a state of, I'm guessing, permanent EDL mode. The phone gives absolutely no response to any buttons or attempts to boot it (no vibration, no lights, just a black screen, whether I try to boot normally, boot to recovery, or boot to EDL), it does show up in device manager as Qualcomm HS-USB QDLoader 9008 (COM10), but adb won't recognise it, and it shows up in MiFlash but any attempt to flash anything results in "cannot receive hello packet", "try to reset status" and eventually "error:The write timed out."
I've been reading through a lot of threads here, but at this point I'm pretty much out of ideas, and I'd really like to have a phone for work in 6 hours. Can anyone help, please?
Not sure how useful it will be, but here's everything I can remember about what I've done just so there's something to go on. First, I tried a few days ago as detailed in this post, and put it aside after that post. Aside from not being able to get to recovery at that point, the phone was working perfectly. Today, seeing the new Axon7Toolkit, I decided to give it a try. I managed to unlock the bootloader and get into TWRP recovery (during the process, it asked me for a decryption password and I hit cancel). I've done a lot of reading and searching since then so I can't recall the exact steps I took after that, but I wiped the device (I didn't change the filesystem or anything) and got errors, and then after seeing the "your device can't be checked for corruption" message I searched and found that I need to mount system, so I did so (not in read-only), and wiped again, this time with no error messages. I can't remember if I did anything else in TWRP aside from looking through the options available. After that, I think what I did was "Flash TWRP and/or root" again in Axon7Toolkit, and I think something went wrong at that point. That's pretty much all I know.
Click to expand...
Click to collapse
I think you got the "cannot receive hello packet", because your bootloader is locked. Using this method https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254 to unlock it, then flash twrp, then firmware
The bootloader was unlocked (though it may have been unintentionally re-locked somehow?), and MiFlash works with a locked bootloader, so I don't think that's the issue. Axon7tool also doesn't help, because just like adb it can't find the device.
Now, trying again today, MiFlash is working for some reason. I haven't done anything differently, but I can flash whatever I want with MiFlash now. But it doesn't really make a difference, because the phone is still entirely unresponsive, I can't enter recovery or boot in any way. Any suggestions for what else to try?
Aspoehro said:
I'm not sure exactly what I did wrong, but in the process of trying to root my B15 A2017U, it ended up in a state of, I'm guessing, permanent EDL mode. The phone gives absolutely no response to any buttons or attempts to boot it (no vibration, no lights, just a black screen, whether I try to boot normally, boot to recovery, or boot to EDL), it does show up in device manager as Qualcomm HS-USB QDLoader 9008 (COM10), but adb won't recognise it, and it shows up in MiFlash but any attempt to flash anything results in "cannot receive hello packet", "try to reset status" and eventually "error:The write timed out."
I've been reading through a lot of threads here, but at this point I'm pretty much out of ideas, and I'd really like to have a phone for work in 6 hours. Can anyone help, please?
Not sure how useful it will be, but here's everything I can remember about what I've done just so there's something to go on. First, I tried a few days ago as detailed in this post, and put it aside after that post. Aside from not being able to get to recovery at that point, the phone was working perfectly. Today, seeing the new Axon7Toolkit, I decided to give it a try. I managed to unlock the bootloader and get into TWRP recovery (during the process, it asked me for a decryption password and I hit cancel). I've done a lot of reading and searching since then so I can't recall the exact steps I took after that, but I wiped the device (I didn't change the filesystem or anything) and got errors, and then after seeing the "your device can't be checked for corruption" message I searched and found that I need to mount system, so I did so (not in read-only), and wiped again, this time with no error messages. I can't remember if I did anything else in TWRP aside from looking through the options available. After that, I think what I did was "Flash TWRP and/or root" again in Axon7Toolkit, and I think something went wrong at that point. That's pretty much all I know.
Click to expand...
Click to collapse
Hi, I'm the dev for the toolkit and I think I know what the problem is. Can you go into C:\Axon7Development\Axon7Toolkit\twrp and see what the size of the image is? It may have been a bad download. Either that or there is issues with the latest version of SupersSU if you chose the root option.
bkores said:
Hi, I'm the dev for the toolkit and I think I know what the problem is. Can you go into C:\Axon7Development\Axon7Toolkit\twrp and see what the size of the image is? It may have been a bad download. Either that or there is issues with the latest version of SupersSU if you chose the root option.
Click to expand...
Click to collapse
twrp-3.1.0-0-ailsa_ii.img is 14.1 MB
Aspoehro said:
twrp-3.1.0-0-ailsa_ii.img is 14.1 MB
Click to expand...
Click to collapse
Ok so TWRP is definitely not the problem. Can you remember exactly when the problem happened, like after SuperSU was flashed since you mentioned using the Flash TWRP and root option?
I don't remember any specific details, but I'm fairly certain I didn't get to the point of flashing SuperSU. I think the most likely cause is me doing something wrong in TWRP (I was trying to follow vague guides mixed with scattered information throughout various threads), and when I did "Flash TWRP and/or root" after flashing TWRP, I think I got some error messages right away.
One problem I do remember is that the toolkit would sometimes say something like "device not found", but still try to continue whatever it was doing and move on to the next step as if there were no problems. Unfortunately I don't remember exactly when it did that, so I can't give any details on how you could reproduce it.
Hey, I had exactly the same problem. Are you saying miflash is now working (you get success at the end!) ? If so, I don't understand why it wouldn't boot afterwards.
If not, in my case, a computer reboot, switching to MiFlash Beta and switching com ports eventually allowed me to flash successfully B15 full package after 3 hours of cannot receive hello packet. You could always try full B13 (Chinese rom) or other similar packages to see if it makes a difference. You'll be able to revert afterwards.
Aspoehro said:
I don't remember any specific details, but I'm fairly certain I didn't get to the point of flashing SuperSU. I think the most likely cause is me doing something wrong in TWRP (I was trying to follow vague guides mixed with scattered information throughout various threads), and when I did "Flash TWRP and/or root" after flashing TWRP, I think I got some error messages right away.
One problem I do remember is that the toolkit would sometimes say something like "device not found", but still try to continue whatever it was doing and move on to the next step as if there were no problems. Unfortunately I don't remember exactly when it did that, so I can't give any details on how you could reproduce it.
Click to expand...
Click to collapse
So you're sure that your problem is not because of my toolkit? Regardless looks like now I have to fix the ADB check
Gnreux said:
Hey, I had exactly the same problem. Are you saying miflash is now working (you get success at the end!) ? If so, I don't understand why it wouldn't boot afterwards.
If not, in my case, a computer reboot, switching to MiFlash Beta and switching com ports eventually allowed me to flash successfully B15 full package after 3 hours of cannot receive hello packet. You could always try full B13 (Chinese rom) or other similar packages to see if it makes a difference. You'll be able to revert afterwards.
Click to expand...
Click to collapse
MiFlash does seem to be working, I don't get any errors and it says it flashed successfully. I tried flashing B15 full and fastboot unlock from here, neither allowed the phone to boot.
Any suggestions for specific files to try flashing?
bkores said:
So you're sure that your problem is not because of my toolkit? Regardless looks like now I have to fix the ADB check
Click to expand...
Click to collapse
I can't be sure since I don't know exactly what the problem is or how I caused it. All I really have are guesses at this point.
Aspoehro said:
MiFlash does seem to be working, I don't get any errors and it says it flashed successfully. I tried flashing B15 full and fastboot unlock from here, neither allowed the phone to boot.
Any suggestions for specific files to try flashing?
Click to expand...
Click to collapse
I rebricked myself last night (lol), so I had to reflash full package, from the same link you posted, and here are some notes:
It seemed on first boot that it didn't work: usual three blinks of LED followed by a black screen
Second boot worked (and I now remember that the same thing had happened the first time I bricked my device), but Android asked me for a password even though I had formatted /data
From there, install TWRP via fastboot (and fastboot_unlock prior to that if bootloader is locked, it shouldn't be), format /data using TWRP, reboot, and you should have a working device
Hope it helps!
Gnreux said:
It seemed on first boot that it didn't work: usual three blinks of LED followed by a black screen
Click to expand...
Click to collapse
I don't even get that much, nothing I do gets any response from the phone at all. No LED when trying to boot (including EDL or recovery), no LED when charging, the only indication that the phone isn't perfectly dead is that it shows up in device manager and MiFlash.
You could try not flashing fastboot_unlock right away and booting first instead... This is the only thing we are doing differently, although I don't see how it could have an impact.
You could also try flashing this EDL package (B13) instead and flash your device specific bootstack afterwards.
Still no luck with anything I try to flash in MiFlash. But I tried reinstalling drivers with Zadig, and axon7tool is working this time. Trying to read gpt works fine, but if I try to read/write boot or recovery, I get "W: bad lba in partition entry 26" and "Cannot find partition boot"/"Cannot find partition recovery". I tried writing TWRP and a couple stock boot/recovery images despite the error, still no change.
Do those error messages give any new information that might be helpful?
Try miflash firmware from offical:
https://www.zteusa.com/axon-7#support
Not sure if this will help you but that miflash utility is a piece of ******** to work with I found.
When extracting the zip files there will usually be 2 folders in them, one is meta-something and the other one has the full name of the zip file, you have to select the full name one beside the meta folder not the parent folder.
Also Sometimes you need to hold all the buttons again and "restart" edl mode before the "hello packet" issues go away.
lipe123 said:
Not sure if this will help you but that miflash utility is a piece of ******** to work with I found.
When extracting the zip files there will usually be 2 folders in them, one is meta-something and the other one has the full name of the zip file, you have to select the full name one beside the meta folder not the parent folder.
Also Sometimes you need to hold all the buttons again and "restart" edl mode before the "hello packet" issues go away.
Click to expand...
Click to collapse
Thank you. This helped me. Why the *$*# can't the program just pick the zip file, or tell you which folder to pick? Until I found your post, I had no idea which folder to pick.
Thanks!!!
:victory:
Flapjack said:
Thank you. This helped me. Why the *$*# can't the program just pick the zip file, or tell you which folder to pick? Until I found your post, I had no idea which folder to pick.
Thanks!!!
:victory:
Click to expand...
Click to collapse
Glad it helped someone!
I am super new to rooting I mainly use it for PokemonGo. I am following this video on YouTube.
Basically when I flashed via Odin, I then install Magisk. Then everything is working and rooted BUT when I restart my phone my Magisk is then magically unrooted (I dont know if this is the right term) it says 'Magisk is not installed' and underneath that is says 'Magisk Manager is up to date'
So why does it keep doing this? Everytime this happens I need to Flash again via Odin and do the whole procedure again. This only happens when I restart the phone. Why does it keep doing this and how do I fix this? I will pay someone who can fix this for me. Ive been trying to figure out for the past day and Im going insane. I have no knowledge about rooting etc like i said i just want to play Pokemongo location spoofing.
Appreciate everyones help.
Dude you're giving me......double vision! Oh oh
StoneyJSG said:
Dude you're giving me......double vision! Oh oh
Click to expand...
Click to collapse
What do you mean lol
littlepuppies said:
I am super new to rooting I mainly use it for PokemonGo. I am following this video on YouTube.
Basically when I flashed via Odin, I then install Magisk. Then everything is working and rooted BUT when I restart
Click to expand...
Click to collapse
Are You aware that you have to reboot via keycombo, just as you would boot into recovery and then release the buttons, after vibrate and samsung logo, or alternatively use an app like quick reboot pro ?
You have a double post of the same topic.
blackspy_ said:
Are You aware that you have to reboot via keycombo, just as you would boot into recovery and then release the buttons, after vibrate and samsung logo, or alternatively use an app like quick reboot pro ?
Click to expand...
Click to collapse
Yes but I'm not 100% sure if I'm doing it correctly. Well my magisk is installed so I'm doing it right? But like I said when I restart my mobile magisk is not installed in the app. May I ask what's this reboot Pro? If that will solve the restart problem I would.happily pay. Can you tell me more?I'm really nooby thank you sir
Im seeing doubles.
Hello. I recently tried to flash the latest fastboot global rom which included locking the bootloader. I used the latest miflash unlock program and everything went well and displayed the green "successful' when it was done. But when I rebooted to the system it loaded directly into stock recovery and boot loops by itself, restart>recovery>restart>recovery etc. It also displays at the bottom of the recovery screen "This MIUI version can't be installed this devise' but I'm sure I flashed the right one.
Now I don't know what to do. If I try to reunlock the bootloader it doesn't go through because I haven't linked my account to the phone (and cant do that because it wont boot up properly). I've tried wiping data in recovery but that doesn't change anything. I can however boot the phone into fastboot and also ADB but I don't know what to do from there. If I try to erase the data via fastboot I get an error saying it can't do that on a locked devise.
So I'm really stuck here and if someone knows what I can do (if anything) I would really appreciate your help.
yurtal said:
Hello. I recently tried to flash the latest fastboot global rom which included locking the bootloader. I used the latest miflash unlock program and everything went well and displayed the green "successful' when it was done. But when I rebooted to the system it loaded directly into stock recovery and boot loops by itself, restart>recovery>restart>recovery etc. It also displays at the bottom of the recovery screen "This MIUI version can't be installed this devise' but I'm sure I flashed the right one.
Now I don't know what to do. If I try to reunlock the bootloader it doesn't go through because I haven't linked my account to the phone (and cant do that because it wont boot up properly). I've tried wiping data in recovery but that doesn't change anything. I can however boot the phone into fastboot and also ADB but I don't know what to do from there. If I try to erase the data via fastboot I get an error saying it can't do that on a locked devise.
So I'm really stuck here and if someone knows what I can do (if anything) I would really appreciate your help.
Click to expand...
Click to collapse
Unfortunately, classical case to seek a paid EDL support
Btw, I don't know did the ROM really forced relocking BL or you didn't pay attention - there was an option in MiFlash to avoid relocking BL (unfortunately, by default it is enabled and many users then come to the same situation and have to seek for and pay EDL support, if anything goes wrong while flashing the ROM - one must disable relocking BL to stay on the safe side)
You should look around XDA if you can find somebody (it's not allowed to advertise, hence most posts would be deleted) or ask on Telegram or similarly
zgfg said:
Unfortunately, classical case to seek a paid EDL support
Btw, I don't know did the ROM really forced relocking BL or you didn't pay attention - there was an option in MiFlash to avoid relocking BL (unfortunately, by default it is enabled and many users then come to the same situation and have to seek for and pay EDL support, if anything goes wrong while flashing the ROM - one must disable relocking BL to stay on the safe side)
You should look around XDA if you can find somebody (it's not allowed to advertise, hence most posts would be deleted) or ask on Telegram or similarly
Click to expand...
Click to collapse
Hi thank you for your reply. I wanted to lock the bootloader as I was going to sell the phone and wanted it all back to stock standard. What does EDL do exactly?
yurtal said:
Hi thank you for your reply. I wanted to lock the bootloader as I was going to sell the phone and wanted it all back to stock standard. What does EDL do exactly?
Click to expand...
Click to collapse
Please google about
It's very deep flashing. Something like how they flash the phones when they are assembled - they have to flash Bootloader and everything
zgfg said:
Please google about
It's very deep flashing. Something like how they flash the phones when they are assembled - they have to flash Bootloader and everything
Click to expand...
Click to collapse
Oh ok. Yes I'll read up on it. Thanks for your help.
zgfg said:
Please google about
It's very deep flashing. Something like how they flash the phones when they are assembled - they have to flash Bootloader and everything
Click to expand...
Click to collapse
Hey, just to follow up. I managed to get it back up and running from someone with EDL support.