Related
So i was trying to root my phone and now i won't start, can't even go to bootloader menu or so. when i'm pressing the power up button its just flashes and then shuts down. It loops so frequently that even my pc won't recognize it. What i did to the phone is this:
//androidforums.com/wildfire-s-all-things-root/502772-guide-how-update-htc-wildfire-s-marvel-a510e-gsm-software-version-2-3-5-a.html
i tried to flash a new 2.3.5 to it but now it wont do anything.
Is there any ways to fix this or should i just send this to graveyard :good:
a bit more info plz
alemale said:
So i was trying to root my phone and now i won't start, can't even go to bootloader menu or so. when i'm pressing the power up button its just flashes and then shuts down. It loops so frequently that even my pc won't recognize it. What i did to the phone is this:
//androidforums.com/wildfire-s-all-things-root/502772-guide-how-update-htc-wildfire-s-marvel-a510e-gsm-software-version-2-3-5-a.html
i tried to flash a new 2.3.5 to it but now it wont do anything.
Is there any ways to fix this or should i just send this to graveyard :good:
Click to expand...
Click to collapse
I think you might have soft bricked your phone. Search the forum how to unbrick a soft-bricked phone. That might help
Are you positive that your WFS is GSM -marvel-a510e ?
Also ,Could you be a bit more specific about what happens when you try to go to boot-loader mode or when you try to boot it.
As in the provided link, did you have to perform procedure 3 or did you perform procedure 2 and was it working? A bit more info about what you did could help others analyze the issue
rishr4 said:
I think you might have soft bricked your phone. Search the forum how to unbrick a soft-bricked phone. That might help
Are you positive that your WFS is GSM -marvel-a510e ?
Also ,Could you be a bit more specific about what happens when you try to go to boot-loader mode or when you try to boot it.
As in the provided link, did you have to perform procedure 3 or did you perform procedure 2 and was it working? A bit more info about what you did could help others analyze the issue
Click to expand...
Click to collapse
At the link i did the procedure 1 because my phone couldn't update to 2.3.5 so i tried to update it that way.
when i start the phone it just flashes it's screen and then goes off. it doesn't show htc logo or anything it just flashes some pixels. the loop is so frequent that it happens in 3 sec. Even if i try to start the phone by pressing "volume -" key and "power" key it does same thing, just loops every 3 sec.
I have tried to find a way to fix this but it seem that there is nothing to do because i can't boot to recovery. Is there a way to put the phone to recovery in other way or is here a way to make factory install?
It's really hard to do anything to this phone because my pc won't recognize it in any possible ways and it won't boot to recovery mode.
Do anyone know if i split the phone in to pieces and then manage to boot it or find the system memory and change files in there.
alemale said:
At the link i did the procedure 1 because my phone couldn't update to 2.3.5 so i tried to update it that way.
when i start the phone it just flashes it's screen and then goes off. it doesn't show htc logo or anything it just flashes some pixels. the loop is so frequent that it happens in 3 sec. Even if i try to start the phone by pressing "volume -" key and "power" key it does same thing, just loops every 3 sec.
I have tried to find a way to fix this but it seem that there is nothing to do because i can't boot to recovery. Is there a way to put the phone to recovery in other way or is here a way to make factory install?
It's really hard to do anything to this phone because my pc won't recognize it in any possible ways and it won't boot to recovery mode.
Do anyone know if i split the phone in to pieces and then manage to boot it or find the system memory and change files in there.
Click to expand...
Click to collapse
Even if you want to unbrick the device using back-toback tool , you need to enter the boot-loader mode.
Even for other ways, still it needs to be detected by the PC so that we can pass commands using ADB.
Sorry Dude, I can't help much either I am new to this myself. But i hope somebody here will definitely help you
2. There is a possibility that you could "brick" or bootloop your phone. There are two types of brick: soft (recoverable) and hard (non-recoverable). With a soft brick, the phone will not boot or keeps rebooting ("bootloop"), but it can be started in bootloader mode which allows repair of the ROM. With a hard brick, the phone won't even boot into bootloader after holding the power button for 10 seconds and the phone must be returned to HTC for service.
Click to expand...
Click to collapse
Have you unlocked your Boot-Loader from HTC Dev? Also, you need to install a recovery tool in order to boot into recovery. If you have done only the steps mentioned in the
PROCEDURE 1
Click to expand...
Click to collapse
then you haven't unlocked the boot loader and no recovery is also installed (I believe) . In this case, I think this is a hard-brick(Correct me if am wrong) which is impossible to recover . Anyways, we shall await other replies from DEVs here in the Forum.
rishr4 said:
Even if you want to unbrick the device using back-toback tool , you need to enter the boot-loader mode.
Even for other ways, still it needs to be detected by the PC so that we can pass commands using ADB.
Sorry Dude, I can't help much either I am new to this myself. But i hope somebody here will definitely help you
Have you unlocked your Boot-Loader from HTC Dev? Also, you need to install a recovery tool in order to boot into recovery. If you have done only the steps mentioned in the then you haven't unlocked the boot loader and no recovery is also installed (I believe) . In this case, I think this is a hard-brick(Correct me if am wrong) which is impossible to recover . Anyways, we shall await other replies from DEVs here in the Forum.
Click to expand...
Click to collapse
I tried to unlock the bootloader but it wanted 2.3.5 so i tried to install the new version. now it can't do anything. Well this didn't broke my heart because the phone is pretty worthless . now i have to buy new phone sooner than i planned but still all help is still accepted.
Hi, exactly the same for me : I bought the phone 2 years ago and immediately unbranded it with a goldcard, but never tried to unlock it because it was my wife's and I didn't want to risk anything.
Now she got a new phone, I wanted to play a little with the Wildfire S ^^.
In order to unlock the phone on htcdev I had to update it from 2.13.401.2 to 2.13.401.3, with RUU because can't update with OTA (different CID), with goldcard inside.
After the RUU finished, it says "congratulations everything went well", but actually the phone does not boot, stocked in a loop "quick flash / turns off", can't access bootloader, no USB detection for ADB.
Can't send it to HTC because the 2 years warranty is expired, how ironic ! :laugh:
So... if anyone does know or see any trick that could help to boot anything on this "seems to be hard-bricked" kid... huge thanks to you
Hello all- I managed to completely screw up my F240S, can not get into recovery and have tried every way for 2 days now.
My main issue is that I have been trying to flash the F240S KDZ with the LG update tool and all goes well until about 20-30% into the flash process and I get a message saying "Can not continue due to low battery level, please charge fully and retry" but I am fully charged. Very frustrating.
Does anyone know anything I can do ?
I have been toying around with Android mobiles for a few years now, rooting, custom ROMs, etc.. but this is the very first time I believe I may have completely bricked my mobile, very disappointing.
Cheers for any help !! LL13-
lamplighter13 said:
Hello all- I managed to completely screw up my F240S, can not get into recovery and have tried every way for 2 days now.
My main issue is that I have been trying to flash the F240S KDZ with the LG update tool and all goes well until about 20-30% into the flash process and I get a message saying "Can not continue due to low battery level, please charge fully and retry" but I am fully charged. Very frustrating.
Does anyone know anything I can do ?
I have been toying around with Android mobiles for a few years now, rooting, custom ROMs, etc.. but this is the very first time I believe I may have completely bricked my mobile, very disappointing.
Cheers for any help !! LL13-
Click to expand...
Click to collapse
If you are trying it in Diag mode then switch to emergency mode. That might help.
Poclypse901 said:
If you are trying it in Diag mode then switch to emergency mode. That might help.
Click to expand...
Click to collapse
Cheers for that Poc... but have tried every possible combination and no luck. I actually bought it to a mobile repair guy, can't believe I had to do it but just want it working at this point. Fingers crossed !!!
Cheers, LL13-
put away your battery and do the same flashing without battery...:good:
This Battery low problem is really annoying and has no real reason........i read somewhere that you should use a downloader to download a kdz otherwise it will give error.............it worked once and i flashed successfully but couldn't repeat it....so more luck than logic
an alternate solution is to flash TOT and DLL files using LGPST tool......you may have to search Chinese forums for TOT and DLL files for your specific model. Some Chinese forums below...use chrome for auto tranlsate
http://bbs.gfan.com/forum.php?mod=forumdisplay&fid=1256&filter=typeid&typeid=8314
http://www.sonyue.com/bbs/forum.php?mod=forumdisplay&fid=1615
fortunately i could get into my recovery so i flashed a ROM via sideload and save myself
best of luck
Are you on a Windows 8 computer? I read that you have to use windows 7. For some reason W8 gives the low battery issue.
on windows 7........battery issue still present
Thank you for that information guys. I actually brought the phone to a mobile repair place and as of a week now he is completely puzzled, can not fix it. I am away at the moment so will see him on Monday and hopefully he gets it going. I will try the other methods as far as the battery issue goes, I also read about the .TOT and .DLL files but it looked very complicated. I may just have to get into it though.
lkiizm. are you saying that the battery does not have to be in the phone when you are flashing it ?
Cheers, LL13-
This mobile appears to be worse than bricked. The repair shop had never seen anything like it, they had to give up on it.
I can not use the LG flash tool and .KDZ file as I get the low battery error. I can not, repeat NOT get into any recovery at all, I have tried every method.
The phone is stuck in some half baked mode where some things work and some do not, every time I turn the phone off it goes back to the start and anything put on it is erased. Factory reset is useless.
I'm only a little while from simply tossing this mobile in the trash. Does anyone have any ideas on how to salvage this ?
Cheers, LL13-
lamplighter13 said:
This mobile appears to be worse than bricked. The repair shop had never seen anything like it, they had to give up on it.
I can not use the LG flash tool and .KDZ file as I get the low battery error. I can not, repeat NOT get into any recovery at all, I have tried every method.
The phone is stuck in some half baked mode where some things work and some do not, every time I turn the phone off it goes back to the start and anything put on it is erased. Factory reset is useless.
I'm only a little while from simply tossing this mobile in the trash. Does anyone have any ideas on how to salvage this ?
Cheers, LL13-
Click to expand...
Click to collapse
Tot + DLL should save you... That tool does not have the low battery error.. where are you getting stuck exactly in the boot process? If the mobile turns on, it can be recovered no matter what
Sent from my LG-E980 using Tapatalk
Hi vive... I been real upset over this but may be on the verge of a breakthrough as I just tried the mobile support tool for the hell of it and when my "low battery" error would normally pop up I just tried unplugging and plugging in rapidly and it made it through and now seems to be in the process of a proper upgrade.
I'm on 42% now and it's been going for about 19 minutes, fingers crossed this could be it.
I have been looking at the TOT and DLL way, a bit tricky for a guy like me but I may have to suck it up and just dig in.
The real killer is the large download size, I may have to go to an internet cafe for that.
I will report back !!
Cheers, LL13- :angel:
I have learned my lesson this time, no more dodgy Chinese ROMs for me !!
Hi,
I've searched over xda and google before but haven't found anything relevant so I've decided to post my own problem.
My G4 freezed unexpectedly while listening to music, I had to remove the battery to put it off.
But it never passed the LG logo again.
So, i've been stucked on this LG logo, looking for an answer and found about this hardware issue but I'm not certain to get the same error.
It's not a bootloop (even if I sometimes got stuck in bootloop while trying everything to revive my phone), I have been able to get to the download mode and TWRP (which I don't have anymore because I went back to stock using LGUP and LG bridge), even though I hardly get to the download mode now (I sometimes manage to do it though). I've also managed to save my data when I've managed to enter TWRP (plug in, remove battery, push volume down + power while putting battery in) which, people with hardware issue haven't, as far as I know.
I've tried everything I could and wouldn't even be able to describe it all.
Do you guys know how I could be sure if it's hardware or software related ?
Last try: update via Lg Bridge, succeed but still stuck on LG screen.
Thanks a lot !
Flash a lollipop kdz via LGUP, then try the ILAPO (works only with lollipop, no marshmellow) metod, there is a thread on xda.
There is a video on youtube too
alinnsts said:
Flash a lollipop kdz via LGUP, then try the ILAPO (works only with lollipop, no marshmellow) metod, there is a thread on xda.
There is a video on youtube too
Click to expand...
Click to collapse
Thanks, I'm going to try this and let you know !
I gave a look on what you've suggested, but is that going to let me use the phone or only backup ?
From what I understood (and I might be wrong), this only allows to backup because the phone would be worthless...
bbsugar said:
I gave a look on what you've suggested, but is that going to let me use the phone or only backup ?
From what I understood (and I might be wrong), this only allows to backup because the phone would be worthless...
Click to expand...
Click to collapse
You'll be abble to use the phone, but it would be slower duo to the fact that with ILAPO you disable the "2 more powerfull" cpu cores... this metod let only 1 core active from the other 4, if you want to use the other two you have to gain root permissions and install an .apk to reactive the other 3. It's a litle triky but better than nothing I guess ��
PS: if you dont want to deal with all this bulls**it send it to LG
Same problem
This morning my Lg G4 also got stuck in boot Lg screen. Did you manage to fix your issue or got the data backup ?
sometimes flashing stock LP firmware fix it.. sometimes you must send it back to LG for repair..
localgh0st said:
This morning my Lg G4 also got stuck in boot Lg screen. Did you manage to fix your issue or got the data backup ?
Click to expand...
Click to collapse
I managed to backup, it's a weird trick and you need to have TWRP installed I guess:
- Remove the battery
- Plug your phone (I used my laptop but I'm guessing it also work directly from the charger)
- Push volume down + power
- Insert battery holding those buttons
I managed to enter TWRP and backup with this.
It didn't work at first, I had to try it several times.
I also read you have to keep holding volume down + power until the phone reboot itself once, and then you get access to TWRP but I tried so many times differently I don't remember which one worked best. Anyway, it worked for me that way.
I didn't fix the issue and I sent it to LG... I'm so frustrated, it's been 10 years I'm into this stuff and I always managed to fix everything
Hi guys,
So my G4 just came back from LG, they replaced the motherboard and that's it... A bit disappointed to not having been able to fix it myself but at least, it worked.
I didn't have to pay anything since it was a hardware defect, LG took care of it.
Thanks for those who tried to help, I hope this post would be useful for some with the same issue.
bbsugar said:
Hi guys,
So my G4 just came back from LG, they replaced the motherboard and that's it... A bit disappointed to not having been able to fix it myself but at least, it worked.
I didn't have to pay anything since it was a hardware defect, LG took care of it.
Thanks for those who tried to help, I hope this post would be useful for some with the same issue.
Click to expand...
Click to collapse
I'm having this same issue out of the blue. Is your serial number one of the infamous "before 509" ones? I'm on TMo with the H811, so it may not be similar at all....but I'm at my wits end. I've never had a spontaneous boot loop happen to me before now. It was always something I'd done.
Dramatdude said:
I'm having this same issue out of the blue. Is your serial number one of the infamous "before 509" ones? I'm on TMo with the H811, so it may not be similar at all....but I'm at my wits end. I've never had a spontaneous boot loop happen to me before now. It was always something I'd done.
Click to expand...
Click to collapse
Indeed, my serial number was 505 something.
I've been there too, if it's spontaneous, it must be this hardware defect...
bbsugar said:
Indeed, my serial number was 505 something.
I've been there too, if it's spontaneous, it must be this hardware defect...
Click to expand...
Click to collapse
Interesting... Especially since mine was a 509 or something. I guess they missed some units. Oh well, I just JUMP'ed early with my TMo plan to the G5. That was my second G4 after a similar issue 13 days into owning the first one back in November. Having your phone spontaneously die is quite a fun way to spend your anniversary -____-. I wasn't about to give that model a 3rd try. Thanks for replying.
please help my oneplus 3 can't boot to system or recovery after unbricking with mega unbrick method 1 and 2
the phone boot to black screen and led notification shining white
i try unbricking method again and flash recovery from fastboot dosn't work
sorry my english
Did you solved? I have the same issue ... No ideea what to do... How did you solved?
bibiii79 said:
Did you solved? I have the same issue ... No ideea what to do... How did you solved?
Click to expand...
Click to collapse
If you follow the instructions for method 2, and repeatedly do it a few times, you can succeed. The important thing is to follow the instructions strictly, however silly they may look like.
I did several times, double checking all steps, still boot loop. After apply the method 2 , is doing a boot loop. Than I tried to apply again method 2 I have the successful download with green ...than I go in recovery and flash over adb sideload oos 3.2.8 ...than I start , no more boot loop, but after Oneplus logo goes into black screen with a withe stable notification led turned on ....I left over night ... But it keep staying like that until I force to power off by pressing and holding power button( after I want to turn off i cannot only going into bootloader and from there I choose power of, because is automatically turning on if I press and hold only the power button in order to turn off the device).
Pfiu difficult... I am thinking, some files are missing, this , and where I go in bootloader in missing the values on. Bootloader version- , and baseband version- ....
bibiii79 said:
I did several times, double checking all steps, still boot loop. After apply the method 2 , is doing a boot loop. Than I tried to apply again method 2 I have the successful download with green ...than I go in recovery and flash over adb sideload oos 3.2.8 ...than I start , no more boot loop, but after Oneplus logo goes into black screen with a withe stable notification led turned on ....I left over night ... But it keep staying like that until I force to power off by pressing and holding power button( after I want to turn off i cannot only going into bootloader and from there I choose power of, because is automatically turning on if I press and hold only the power button in order to turn off the device).
Pfiu difficult... I am thinking, some files are missing, this , and where I go in bootloader in missing the values on. Bootloader version- , and baseband version- ....
Click to expand...
Click to collapse
The bootloader and baseband versions were missing when i bought the phone new and are still blank today after flashing a few ROMs and Recoveries/Firmware and modems. So that is not an issue.
Are you downloading the correct files?
tnsmani said:
The bootloader and baseband versions were missing when i bought the phone new and are still blank today after flashing a few ROMs and Recoveries/Firmware and modems. So that is not an issue.
Are you downloading the correct files?
Click to expand...
Click to collapse
Yes, I am using the unbrick method with msm download tool, using the Method 2, after apply, installing all's the Qualcomm drivers 9008 , drivers signature off in windows.... The unbrick tool is passed with the green message .... Reversing back to oos 3.1.2 Android 6.0.1 ..stock, I have recovery working and bootloader also working, bootloader is locked ....so I cannot do too mutch. I start the device right away after unbrick tool and still boot to op logo that is going to vibrate as restart .... And stays in boot loop. Next step I go into recovery , and do over sideload an update with a full ROM, oos 4.0.1 , also tried with full ROM 3.2.8 ...I can sideload the whole ROM , than i start the device and after op logo goes in black screen and white motivation led lighted .... I leave it for 30 min, and still in the same, now I force turn off by going into bootloader and power off. Notice that after this sideload flash I cannot access the recovery. So I need to apply back the unbrick msm download tool for op3.
I tried also to flash over sideload a signed script from Ahmed , unified toolkit , to activate the USB debugging, but gives an error.
I run out of ideas .....any help is welcome ....
Thanks
bibiii79 said:
Yes, I am using the unbrick method with msm download tool, using the Method 2, after apply, installing all's the Qualcomm drivers 9008 , drivers signature off in windows.... The unbrick tool is passed with the green message .... Reversing back to oos 3.1.2 Android 6.0.1 ..stock, I have recovery working and bootloader also working, bootloader is locked ....so I cannot do too mutch. I start the device right away after unbrick tool and still boot to op logo that is going to vibrate as restart .... And stays in boot loop. Next step I go into recovery , and do over sideload an update with a full ROM, oos 4.0.1 , also tried with full ROM 3.2.8 ...I can sideload the whole ROM , than i start the device and after op logo goes in black screen and white motivation led lighted .... I leave it for 30 min, and still in the same, now I force turn off by going into bootloader and power off. Notice that after this sideload flash I cannot access the recovery. So I need to apply back the unbrick msm download tool for op3.
I tried also to flash over sideload a signed script from Ahmed , unified toolkit , to activate the USB debugging, but gives an error.
I run out of ideas .....any help is welcome ....
Thanks
Click to expand...
Click to collapse
Hi bro, did you solved it? Im facing the same problem here
bluuquthug said:
Hi bro, did you solved it? Im facing the same problem here
Click to expand...
Click to collapse
Unfortunately not yet ... Yes I solve it, I bought a Moto Z with dual SIM and snapdragon 820 and 64 GB and SD card with 280 euro .... I am disappointed at the moment about Oneplus 3 , I was a Nexus fan and switched to oneplus ... I thought will be opensource ... But way to expensive repair this done in service , Easter to buy another one ... You save time .. you cannot save money on it ..
bibiii79 said:
Unfortunately not yet ... Yes I solve it, I bought a Moto Z with dual SIM and snapdragon 820 and 64 GB and SD card with 280 euro .... I am disappointed at the moment about Oneplus 3 , I was a Nexus fan and switched to oneplus ... I thought will be opensource ... But way to expensive repair this done in service , Easter to buy another one ... You save time .. you cannot save money on it ..
Click to expand...
Click to collapse
Had the same problem with my oneplus x.
P
oneszero said:
Had the same problem with my oneplus x.
Click to expand...
Click to collapse
And what was the end of your story with Oneplus x?
bibiii79 said:
P
And what was the end of your story with Oneplus x?
Click to expand...
Click to collapse
RMA'd it to a service center for repair, after two tech support calls. They actually told me that they couldn't repair it due to "water damage." Funny thing is, that phone was never dropped in or on anything, let alone in WATER. Then to add insult to injury they refused to send it back to me stating that I had to pay for return shipping. My wife got on the phone with them and by the end of the phone call they said that they would send it back for free. HAHA. So I bought a Oneplus 3 after that whole ordeal. All the while the Oneplus X sat in the box on my desk for about 5 months. Last week I decided to pick it up and tinker with it some more. I scoured the net trying to find any other programs or solutions that I hadn't tried prior to sending it off. I came across somethings that I hadn't seen before. https://forum.xda-developers.com/oneplus-x/help/fastboot-mode-available-stuck-kindly-t3387918. http://rootmygalaxy.net/oneplus-x-s...w.pickmod.com/rom/4187/coloros-for-oneplus-x/. Ended up flashing Color OS via msm tool. Wouldn't load OS, but i didn't end up with a black screen and white LED, it just sat there. So right after I flashed Color OS, i Flashed the mini unbrick tool by Naman, and BOOM it booted into OS. Hope this helps.
Please share your stories or your thoughts what stupid thing you did to make your RN8 Pro Bricked (If not: tell how the first time you bricked your device :crying: )
My side story: I tried to flash Android 9 with Android 10 unofficial recovery & in result Bricked/Dead & device with no response at all, just light blinks & that's it. :crying::crying::crying:
Also Please share your story & also update your answer how you guys fixed it.
Also I will update my Story How I fixed my Hard Brick RN8 Pro Device in this Dark Time :'(
I Hope this thread will make some of you laugh by hearing someone's funny story,
or you will able to understand someone else feelings or you will able to feel better by hearing your experience or hearing someone's else story like yours in this Hard Brick World.
Hope this thread will make good people or devs to come here & start helping each other. hope soon we will get a new way to fix our device without having mi authorized account.
simply poor move
Xiaomi did the worst thing, I could imaging. I proudly recommended Xiaomi over Huawei, because the bootloader is unlockable.
I also own a Mi 9T, which easily modable.
The simple thing like flashing TWRP and a boot.img fried my Redmi Note 8 Pro after 7 days of ownership.
I opened the device (falsely first from the front removing the display, then gettin the guts that it must be done from the back. Cracked the back glass, ordered a new glass for 3 bucks). Pulling the battery and ack that this will not solve the EDL Mode issue.
The device was now a warrantly less mess, no service center in the world would take on.
I replaced the back and reglued the screen and payed a russian savior to bypass the Xiaomi Authorized Challenge ( a russian GSM forum, I don’t know if posting a link is allowed, so I won’t). It was 20$, far cheaper than a new Mainboard.
Device is now reborn, bootloader still unlocked, but I won‘t ever try to root this piece again.
Hardlocking a flash tool, which is commonly used for cheap 80$ MTK phones is strange. I understand that Xiaomi Shop Rom issue a while ago, but a flash only allowed by China and Russia seams not really better than the Huawei way...
The phone is now used as a Escooter Dashboard/Tachometer, because I don‘t value it any more.
Ceynt said:
Xiaomi did the worst thing, I could imaging. I proudly recommended Xiaomi over Huawei, because the bootloader is unlockable.
I also own a Mi 9T, which easily modable.
The simple thing like flashing TWRP and a boot.img fried my Redmi Note 8 Pro after 7 days of ownership.
I opened the device (falsely first from the front removing the display, then gettin the guts that it must be done from the back. Cracked the back glass, ordered a new glass for 3 bucks). Pulling the battery and ack that this will not solve the EDL Mode issue.
The device was now a warrantly less mess, no service center in the world would take on.
I replaced the back and reglued the screen and payed a russian savior to bypass the Xiaomi Authorized Challenge ( a russian GSM forum, I don’t know if posting a link is allowed, so I won’t). It was 20$, far cheaper than a new Mainboard.
Device is now reborn, bootloader still unlocked, but I won‘t ever try to root this piece again.
Hardlocking a flash tool, which is commonly used for cheap 80$ MTK phones is strange. I understand that Xiaomi Shop Rom issue a while ago, but a flash only allowed by China and Russia seams not really better than the Huawei way...
The phone is now used as a Escooter Dashboard/Tachometer, because I don‘t value it any more.
Click to expand...
Click to collapse
hmm in a same situation, decided to never gonna root this device again
just don't want to take any risk now, will try to use it normally.
glad i didn't opened the back panel, i don't wanted to take a risk
also my device was in warranty so i decided to send it to Xiaomi Service Care Center.
also there was a Gyro Problem in my device. hopefully they will return in a week,
& they also took my Gmail account/password for some reason.
I have a story fot my RN8P goes yo HARDBRICK, the first
I want to reflash the stock rom ( android 9 ) using LR TWRP, and reboot device is normal, no brick or bootloop, and next week I want to reflash again, because my Lucky Patcher can't instal app.
And I think if I reflash my stock Rom, my TWRP is lost, and I think flash stock is done, I flash TWRP .img using TWRP, but I wrong because I choose flash for "boot" not "recovery",
And I think the first reboot to TWRP for fix it, and my RN8P goes to HARDBRICK, from Mei until now -_-
cyberz2 said:
I have a story fot my RN8P goes yo HARDBRICK, the first
I want to reflash the stock rom ( android 9 ) using LR TWRP, and reboot device is normal, no brick or bootloop, and next week I want to reflash again, because my Lucky Patcher can't instal app.
And I think if I reflash my stock Rom, my TWRP is lost, and I think flash stock is done, I flash TWRP .img using TWRP, but I wrong because I choose flash for "boot" not "recovery",
And I think the first reboot to TWRP for fix it, and my RN8P goes to HARDBRICK, from Mei until now -_-
Click to expand...
Click to collapse
Hmmm i received my device from customer care center after 17 days but without charges that's good for me
Nouman112 said:
Hmmm i received my device from customer care center after 17 days but without charges that's good for me
Click to expand...
Click to collapse
How thet figure it?
Nouman112 said:
Please share your stories or your thoughts what stupid thing you did to make your RN8 Pro Bricked (If not: tell how the first time you bricked your device :crying: )
My side story: I tried to flash Android 9 with Android 10 unofficial recovery & in result Bricked/Dead & device with no response at all, just light blinks & that's it. :crying::crying::crying:
Also Please share your story & also update your answer how you guys fixed it.
Also I will update my Story How I fixed my Hard Brick RN8 Pro Device in this Dark Time :'(
I Hope this thread will make some of you laugh by hearing someone's funny story,
or you will able to understand someone else feelings or you will able to feel better by hearing your experience or hearing someone's else story like yours in this Hard Brick World.
Hope this thread will make good people or devs to come here & start helping each other. hope soon we will get a new way to fix our device without having mi authorized account.
Click to expand...
Click to collapse
My story isn't too funny because this is the only time I got hard bricked and fortunately had anti brick flashed.
I was just tinkering around with logo.bin, the bootlogo of device, I found a MTK boot logo editor tool on XDA, succesfully edited and gave to my tester to test, turns out it didn't work, usual bootlogo showed up but didn't go past it, turns out the flashing location of logo.bin in auto generated flashable zip was wrong, I edited it to correct one and took the courageous step to flash it on my device, my bad luck, I would't exactly say it got hard bricked because I could access vol down menu in CFW 1, but still clicking on recovery or fastboot made it reboot with backlight on, my heartbeat went rapidly up LOL, but by god's grace I easily flashed the device with SP flash tool
samuuurai said:
My story isn't too funny because this is the only time I got hard bricked and fortunately had anti brick flashed.
I was just tinkering around with logo.bin, the bootlogo of device, I found a MTK boot logo editor tool on XDA, succesfully edited and gave to my tester to test, turns out it didn't work, usual bootlogo showed up but didn't go past it, turns out the flashing location of logo.bin in auto generated flashable zip was wrong, I edited it to correct one and took the courageous step to flash it on my device, my bad luck, I would't exactly say it got hard bricked because I could access vol down menu in CFW 1, but still clicking on recovery or fastboot made it reboot with backlight on, my heartbeat went rapidly up LOL, but by god's grace I easily flashed the device with SP flash tool
Click to expand...
Click to collapse
And how did you do it, because i've tried many tutorials and none of them works... I think i'll just buy a new board.. Because its impossible to do anything, Tried sp flash with error 0xC0060005 that says i need authentication (that mi authorized account)
Any help is appreciated.