Hi people, this has been discussed many times, but no solution works for me, so this is my last try before trashing my phone.
I did a big mistake and tried flashing the whole ROM of my P500, including modem area (not the KDZ only, but the whole ROM). Now I have a dead phone: no recovery mode, no lights, no nothing. With battery or not, with USB plugged in or not, pressing vol+power+home or any other key combination does nothing. So, the phone is completely dead.
Already tried using a JTAG, but there's no response. It seems IMPL is active in my phone, so the JTAG connection is blocked (Qualcomm security protection).
Anything else I can try? Any suggestion? Is there a way to revive JTAG communication so that I can rebuild the firmware? Any way to clear the security area on flash memory, to neutralize JTAG blocking on Qualcomm chipset?
Many thanks.
Marcovecchio said:
Hi people, this has been discussed many times, but no solution works for me, so this is my last try before trashing my phone.
I did a big mistake and tried flashing the whole ROM of my P500, including modem area (not the KDZ only, but the whole ROM). Now I have a dead phone: no recovery mode, no lights, no nothing. With battery or not, with USB plugged in or not, pressing vol+power+home or any other key combination does nothing. So, the phone is completely dead.
Already tried using a JTAG, but there's no response. It seems IMPL is active in my phone, so the JTAG connection is blocked (Qualcomm security protection).
Anything else I can try? Any suggestion? Is there a way to revive JTAG communication so that I can rebuild the firmware? Any way to clear the security area on flash memory, to neutralize JTAG blocking on Qualcomm chipset?
Many thanks.
Click to expand...
Click to collapse
can u tell us what rom were u flashing and what do u mean by including modem area, also what mistake did u make??? u can refer to threads started for recovering phone in developement section and also in general saection.
Thanks for the reply. I had the openOptimus ROM in my phone, it was all fine. But then I tried to flash a stock Gingerbread official release, using LG MDP tool, and my mistake was to flash the stock ROM, instead of flashing the KDZ update. In other words: it flashed the complete phone.
The file I got included the whole ROM image, including the lower level Qualcomm radio code (this is what I call modem area). Later I learned that we can't flash this area, because Qualcomm chipsets have a protection which makes it block JTAG communication if this area is violated. That's why even JTAG is not enough to unbrick my phone.
So, theorically, my last chance is to somehow reset the chipset and/or flash memory where this protection is stored. As soon as I do that, the JTAG should be back online, and then I'll be able to restore everything back.
So you know what you gotta do.
Sent from my LG-P500 using XDA App
Related
Full story: Sold my phone, tried unrooting, soft brick, went back to stock, flashed Cameleon ROM 3.0.2, starts acting weird (more frequent freezes and reboots, vibrates for about 5-10 seconds when it's been off for a while), charge and boot up this morning, and now phone refuses to connect to any network. IMEI's not blocked or anything. TriangleAway formatted my internal SD, so no backups. Also said the battery was at 100% every time I rebooted, even though it was ~85%. Clean flashing CM10.1 didn't help. I've searched everywhere and nothing seems to help. Warranty's out long ago. I'm incredibly frustrated and desperate for a solution
Who knew running low on battery could cause this?
Running on low battery didn't cause it, tho it could be a simple case of needing a new battery. Might want to try that first, tho it does sounds like the USB board is on the way out. This gets discussed here all the time, search for these threads & read them very carefully. There's 4 different revisions of the board; you need to order the same one that's currently in the phone or your phone may not work properly. Other than that, it's quick/cheap to replace yourself.
So if a new battery doesn't do it, replace the USB board.
Edit - Re: the phone not connecting to networks, how do you know for certain the IMEI isn't blocked ?
MistahBungle said:
Running on low battery didn't cause it, tho it could be a simple case of needing a new battery. Might want to try that first, tho it does sounds like the USB board is on the way out. This gets discussed here all the time, search for these threads & read them very carefully. There's 4 different revisions of the board; you need to order the same one that's currently in the phone or your phone may not work properly. Other than that, it's quick/cheap to replace yourself.
So if a new battery doesn't do it, replace the USB board.
Edit - Re: the phone not connecting to networks, how do you know for certain the IMEI isn't blocked ?
Click to expand...
Click to collapse
Of course, I don't know for certain. I used AMTA's checker, and apparently it's not blocked.
I'll try repairing the board. In the meantime, I'll contact the police to find out about the IMEI. Thanks!
Something similar happened to me, try to flash your device with an official ROM, preferable Android 2.3 root your device, then search the GB's Modem or baseband, find the one compatible for your network or country and then you need to flash it via CWM recovery of course you need to be rooted, do a full wipe before you flash anything. Doing this you device should be fully functional and then you can install any Custom Rom. Hope that helps..!
Hello,
I have a Samsung Galaxy S2.
After reading this post http://forum.xda-developers.com/showthread.php?t=2382579 I decided to root my phone.
So I went ahead and started with this step http://forum.xda-developers.com/showthread.php?t=1118693 because I was unsure if I had a kernel with the MMC-SUPERBRICK-BUG.
After I flashed CWM-SuperSU-v0.97.zip using Odin version 1.85 and after the phone rebooted it was stuck at the "triangle screen" for a few seconds then the display went black and I couldn't do anything further.
Up to this point the phone was still accessible in download mode (volume up, power and center button). I believe this is called "download mode". Sorry but I am a complete noob with rooting phones, etc...
So I panicked and took the phone to a repair shop (big mistake). The guy ran it in download mode then tried to flash something onto the phone (I think he used all 4 fields: Bootloader, PDA, Phone and CSC.
Then, in the middle of the operation, Odin froze when writing "setting up connection". Then the phone died ! pressing the 3 famous buttons does nothing and the phone just stays dead.
I had to leave the phone there as the guy said they will try to bypass stuff and try to connect to the CPU directly (sorry again if this sounds noobish). I did update my modem firmware and my computer BIOS in the past... but I guess this one was more complicated.
At the shop, they asked me to check again in 3 days. I am lost here. I don't know what to do anymore.
Is the phone hard bricked ? Should they bear all expenses for what they did ? I would bring back my phone and try something like this http://forum.xda-developers.com/showthread.php?t=1878255 or even a stock flash but I am afraid I cannot do that as the phone isn't even powering up anymore after they tried to repair it at the shop.
Any advice is appreciated.
Nope. You borked it. You tried to flash custom firmware to the phone & obviously failed spectacularly at it. Instead of trying to flash it yourself via download mode (which you could easily have done unless the NAND was borked), you paid them to do it. Sometimes flashes go bad. Sounds like that's what happened in this case.
Reading between the lines they sound like they're going to try & JTAG it (or have someone else do it). And if that fails I presume they'll change motherboards. You could always get the phone back & take it to someone who does JTAGs if that shop doesn't themselves.
MistahBungle said:
Nope. You borked it. You tried to flash custom firmware to the phone & obviously failed spectacularly at it. Instead of trying to flash it yourself via download mode (which you could easily have done unless the NAND was borked), you paid them to do it. Sometimes flashes go bad. Sounds like that's what happened in this case.
Reading between the lines they sound like they're going to try & JTAG it (or have someone else do it). And if that fails I presume they'll change motherboards. You could always get the phone back & take it to someone who does JTAGs if that shop doesn't themselves.
Click to expand...
Click to collapse
Yes I know I failed at it
Or maybe the shop technician is the one who broke it. At least when I had the phone with me I was still able to boot in Odin mode.
Do you think I could have recovered my phone if I had kept it with me and it was booting in download mode ?
I feel so pissed that I took it to that shop. I just wish I hadn't panicked and I had tried, instead, to fix it at home by asking for more help.
Anyway I still haven't paid them anything so far.
We agreed that they will pay for the motherboard because I brought in a working phone (that would power up at least). The owner of the shop was nice enough to agree that he would only charge me fees for installing new software on the phone (even if they have to change the motherboard) because he knows the phone was booting in Odin mode when I came in to the shop and his technician flashed the wrong firmware.
I also wrote down the board serial number so I can be sure they changed it (if they say they did that). So you are telling me the phone can still be fixed ? What does JTAG mean ?
Even if it is fixed I think I will be too scared to try and root it again. Unless I can understand in advance, step by step, what I need to do and what file version(s) I need to use.
Ok, I got my phone today in good working condition.
According to the shop, they had to replace an IC (I don't know what damaged the IC, I am assuming this happened when they tried to electrically jolt the phone) then JTAG it to get it to work again. They charged me a small fee (and they did end up bearing more than 50% of the expenses) because I brought in a phone that was booting in download mode and they take responsibility for what happened after that (flashing wrong files which caused the phone to completely stop booting).
Anyway, long story short, this was my first attempt to root a mobile phone and I learned my lesson.
I am running the following:
Model Number: GT-I9100
Android Version: 4.0.3 (which I will need to upgrade to 4.1.2 of course)
Baseband Version: I9100XXLPW
I know you will say read the sticky posts or the guides but the truth is, that's exactly what I did (you can see the links to the guide I tried to follow in my original post) and I still ended up failing at rooting/installing cyanogen on my phone right after installing Clockwork Mod.
The truth is I am scared to try again and mess up the phone. So this time I would rather be safe than sorry.
What can I do, this time, to safely root it and install a mod like Cyanogen.
Detailed steps are appreciated:
- Do I need to upgrade to 4.1.2 before rooting as 4.0.3 might have the superbrick bug ?
- How to backup the phone.
- Odin version to use, ClockWork Mod version to use, Cyanogen version to use
- How to connect the phone, how to reboot in download mode and all the necessary actions to avoid bricking my phone.
No spoon feeding aloud on XDA.better to read and learn how to do this and that but before you flash anything after learning how to do that learn how to fix it if it doesn't work. :thumbup:
andrewwright said:
No spoon feeding aloud on XDA.better to read and learn how to do this and that but before you flash anything after learning how to do that learn how to fix it if it doesn't work. :thumbup:
Click to expand...
Click to collapse
Fair enough, I figured I'd get that reply from someone and it's normal to be honest.
I decided not to try anything on my phone before I re-read the guides and be sure I know what I am doing.
I will also keep the phone running on stock firmware (after upgrading to JB 4.1.2) to check the battery consumption behavior which, I hope, will be fine since someone tampered with my phone's electronic components at the shop.
Hi,
I'm a new member here.
8 months ago, I purchased two "Samkimoke T710 LA-I" Android phones. It has Spreadtrum SC6820, Mail 300 GPU, 256 MB RAM, MTK6517, Camera (idk spec needed for driver? I guess).
(I know the above from an App I installed in another T710 mobile.)
The OS was said to be "4.0.2" in 'About Device', i personally think it's Android GingerBread though.
Today, I got a miss call, and after that I just pushed the Power button (to turn the display off), it did so. Now the thing does NOT start, no display while charging.
I've googled a LOT, I tried other batteries, connected mobile to USB and then inserted battery, as was said online, nothing came, I also tried Volume buttons + Power button, and also charge to Power Outlet trick. Nothing worked.
After that I went to a local repair shop, after checking it he said the phone does boot, but is not starting (i think he was referring to it's ROM), he said "he would try to re-install a software", from what I understood, he wanted to flash it or something.
So the questions are:
1. Was my phone "dead" or "hard brick" with OUT any problem/s (just out of nowhere) ?
2. Can i flash it (or even any "hard brick" Android device) myself, and expect it to work? If yes, how?
3. Where can i find a custom ROM this manufacturer used (or it's alternative)? What tool should i use to Flash?
(i guess, personally, driver issue will arise in these cases) I checked the Samkimoke DOT com website, their service is available in China only, and NO Email given for me to ask question about their custom ROM)
Thank you ...
(You can say I'm too greedy to forget that .. i can't throw a device that was working in the morning, and that's just 8 months old )
What's happening here?
I left it for the shop to flash (I've never flashed an Android before), and also since it's Chinese Android - I was unsure of the ROM. So he said he tried to flash it (or flashed it) but it still isn't booting!
Back home, I pressed the Power Button, and I noticed this.
http:\\i.share.pho.to/e7653bef_o.png
1. Before Pressing Power Button
2. After Pressing Power Button (the display starts, as if trying to display something)
3. The display fading away (back to off state -- state 1)
4. Back to State 1
All this happens within a second. Is the phone trying to launch the ROM and not finding it or something? Does the above mean it's not the Hardware issue?
I downloaded the MTK Droid Tool and it does NOT show any info, it doesn't detect it at all.
What should I do in such cases?
Thanks ....
Umm.. Am I posting this in the wrong forum section or something?
stream13 said:
I left it for the shop to flash (I've never flashed an Android before), and also since it's Chinese Android - I was unsure of the ROM. So he said he tried to flash it (or flashed it) but it still isn't booting!
Back home, I pressed the Power Button, and I noticed this.
http:\\i.share.pho.to/e7653bef_o.png
1. Before Pressing Power Button
2. After Pressing Power Button (the display starts, as if trying to display something)
3. The display fading away (back to off state -- state 1)
4. Back to State 1
All this happens within a second. Is the phone trying to launch the ROM and not finding it or something? Does the above mean it's not the Hardware issue?
I downloaded the MTK Droid Tool and it does NOT show any info, it doesn't detect it at all.
What should I do in such cases?
Thanks ....
Umm.. Am I posting this in the wrong forum section or something?
Click to expand...
Click to collapse
i don't think this is your fault, its just the faulty Chinese firmware is terribly developed and half of the time this happens to all Chinese phones. they decide not to work anymore or the usb drivers decide to not like your computer anymore. if there is not life from the device (no boot, no recovery) then its hard bricked. the only why you could fix it is using a jtag and finding the firmware online for your specific device and using that to write the Firmware back onto your device. but that can cost lots of moola $.
stream13 said:
I left it for the shop to flash (I've never flashed an Android before), and also since it's Chinese Android - I was unsure of the ROM. So he said he tried to flash it (or flashed it) but it still isn't booting!
Back home, I pressed the Power Button, and I noticed this.
http:\\i.share.pho.to/e7653bef_o.png
1. Before Pressing Power Button
2. After Pressing Power Button (the display starts, as if trying to display something)
3. The display fading away (back to off state -- state 1)
4. Back to State 1
All this happens within a second. Is the phone trying to launch the ROM and not finding it or something? Does the above mean it's not the Hardware issue?
I downloaded the MTK Droid Tool and it does NOT show any info, it doesn't detect it at all.
What should I do in such cases?
Thanks ....
Umm.. Am I posting this in the wrong forum section or something?
Click to expand...
Click to collapse
Sounds like a hard brick to me, too. Since you didn't "tweak" the phone in any way, it's not your fault. You can do only 2 things: either go to another service shop and ask for repair, or find a toolkit and the necessary firmware files to flash it on your own. From what you're describing, it seems like the firmware is all messed up.
Okay, thank you .. and I didn't tweak it, it just simply stopped working.
the only why you could fix it is using a jtag and finding the firmware online for your specific device and using that to write the Firmware back onto your device. but that can cost lots of moola $
Click to expand...
Click to collapse
find a toolkit and the necessary firmware files to flash it on your own.
Click to expand...
Click to collapse
Where can I find/buy this thing called jtag? Or is it simply the same thing as "jig"? If not, How much would it cost?
Since I bought two of them, I have another T710 mobile (same manufacturer) working with me. I'm kinda scared for it too, should I use CWM or something and back it up right now?
Back to the topic, the working mobile has MTK6515 (as opposed to MTK6517 that the damaged one has), can I still backup/extract the image of one to use in the damaged Android phone?
Thank you ...
So, i was inserting and ejecting this device back and forth, and this time, the device decided to show up in the Device Manager, At 1st, it showed up in the Other Devices, then under the "USB Controllers" as "Unknown Device":
http:\\i.share.pho.to/80f316eb_o.png
It was still not showing up in the MTK Droid Tools, although i had installed already MTK65xx drivers. Then i installed the SpreadTrum Phone Driver, and after connecting the device, i pressed Power + Volume [+] button, and it showed up under USB Controllers as "SPRD COM Enumerator".
http:\\i.share.pho.to/3001fb77_o.png
At first, it said "The device is working properly":
http:\\i.share.pho.to/1ad975d3_o.png
And then it refreshed again and said "The device cannot start":
http:\\i.share.pho.to/dd9ee409_o.png
So this means my phone is SpreadTrum phone so maybe that's why it did not show up in MTK Droid Tools?
Which Programs are available to backup and flash Spreadtrum phones?
Thank you. .....
EDIT: I pressed the Power button in my other t710 phone, and it also does the same blinking as the damaged one does. So that means the phone was, i guess, testing if it's "on" and should display or something, and since it has no contents or has, as a member pointed out, a damaged firmware, it's not working properly..
stream13 said:
Okay, thank you .. and I didn't tweak it, it just simply stopped working.
Where can I find/buy this thing called jtag? Or is it simply the same thing as "jig"? If not, How much would it cost?
Since I bought two of them, I have another T710 mobile (same manufacturer) working with me. I'm kinda scared for it too, should I use CWM or something and back it up right now?
Back to the topic, the working mobile has MTK6515 (as opposed to MTK6517 that the damaged one has), can I still backup/extract the image of one to use in the damaged Android phone?
Thank you ...
Click to expand...
Click to collapse
a Usb jig and a JTag/Riff box are a little different. usb jigs are used for only samsung to force the device into download mode, otherwise known as a easy way to get into download mode. the Jtag and riff box's attach pins to Certain parts of a phone or another device and it Write firmware onto that device since its corrupt or does not want to turn on. these can cost up from $100-200, i would just get another phone my friend .
So, although it shows under Device Manager, I'm already screwed with this device? Can I not flash it by using a Computer?
Thank you ..
stream13 said:
So, although it shows under Device Manager, I'm already screwed with this device? Can I not flash it by using a Computer?
Thank you ..
Click to expand...
Click to collapse
Nope, from what i understand when a device is hard bricked or you have nothing showing, the OS is corrupt and that means the USB drivers are Screwed up so it wont recognize your device.
Hmm ... I have flashed it a couple of times, and it's not starting because I don't have the right ROM It gives the usual short vibration when I press power button to start it. The screen is not displaying anything, as expected. and there is no light.
The device is SpreadTrum and the screen size is 4.3 inch, the roms I downloaded either seem to be that for 3.5 inch or 5 inch
1. Is there something like Custom Barebone ROM which will "work on any device"? OR at least compatible ROM?
[ I purchased the phone for 5860, "repairing" it will cost me 1500 So I'm trying to not go to the repair shop. ]
--------------------------------------------
2. I rooted my working phone with vroot, and used adb to backup the images, the total size is 309 MB, trying to flash it in my device, it's giving me "Failed: Download size is over it's partition" error or "Failed: Operation Failed" error.
Regardless of which FDL.bin file I use, my PAC always gives errors. And those that I download from the web flash fine.
(I'm using ResearchDownload -> Packet option, it makes the PAC file, but the flashing process always results in errors.)
Is there some proper Guide to make the PAC file?
Thanks ...
UPDATE: Read this!
TLDR: Don't flash 20j update and try to revert....== HARD BRICK
Long version:
The new 20j update has the Anti-Rollback feature tag set that you can NOT revert back to 20e.......You will HARD BRICK your V10 if you do so. I have...and a few others have.
I was on Eliminater74 20e rom, which is excellent. But he released a P1 .zip for the new 20j update. This contains new bootloader etc. (no P2 which is the actual rom for 20j yet.)
This will boot on 20e, but users (myself included) noticed video issues with YouTube and soon after, others reporting that video recording is broken now.
Naturally, we thought to revert and flash back to the 20e bootloader P1. zip.......and that caused HARD BRICK. Phone gets stuck in Qualcomm Emergency Bootloader mode that is not recoverable.
FIX: Contact " tungkick" http://forum.xda-developers.com/member.php?u=4965298
He helped me un-brick phone. No data was lost! Was quite easy actually. ( I don't see his methods or files he used released here on XDA publicly) (if it is i'm blind.) So don't ask me...contact "" tungkick" .
See post here for instructions: http://forum.xda-developers.com/tmobile-lg-v10/development/debrick-phone-h901-qualcomm-9008-t3440359
I did the same thing, flash tool isnt picking up phone either, I think we are hard bricked at this point...
speedingcheetah said:
I flashed V10_H901_V20J_Stock_BootStock_Part1_20160810.zip ...that booted fine. But then I used pheon for a while and noticed YouTube was having issues of videos freezing but audio playin...a few others posted they had the same thing.
So I booted to TWRP and flashed the olde rP1 .zip for the orginal bootstock and hit reboot system and no...Nothing!
Black screen. No vibrate when I try vol down + power. When i try Vol up and connect usb to my computer...It shows "Qualcomm HS-USB QDLoader 9008 (COM8). LG Up says it cant find anything.
Usb device descriptor failed in Device manager when I do vol down and plug in.
I have no idea what do? Help? I have been searching a few forums, but not really sure what is happening.
Click to expand...
Click to collapse
I was just about to start a new thread asking if I could flash back to previous marshmallow. Anti rollback may be in effect. If you have all the correct drivers installed it sounds to me like a hard brick. Hopefully I'm wrong and someone can help you
headcreepz said:
I was just about to start a new thread asking if I could flash back to previous marshmallow. Anti rollback may be in effect. If you have all the correct drivers installed it sounds to me like a hard brick. Hopefully I'm wrong and someone can help you
Click to expand...
Click to collapse
And....I assume a hard brick is very bad...not easy to fix? I messed up my G3 once, but at least it would show some sign of life.
I am not at all experienced with adb or fastboot..and how to get all that to work...I have tried, but with no success. Don't suppose there is someone I can send my phone to have it unbricked?
Same predicament here
Sent from my SM-T337T using XDA-Developers mobile app
Oh guys.... I am pretty sure that I've read around here and there that when you get that Qualcomm message you're not recoverable. I surely hope I'm wrong!
Sent from my pretty nifty brand new LG V10
Yea....it sucks. I have literally been up all night trying every method I can to recover from the Qualcomm Emergency Bootloader mode I'm stuck in. There are some LG programing tools that seem to be fake/scam by some user...but those were for the G3 and G4 anyway. Nothing I tried worked.
Just bought the V10 2 months ago used off swappa, already rooted, twrp etc..about $300. Just got the thing all setup the way I wanted it too...sigh. THis is what I get for not being patient and seeing what others experience before flashing something so new.
I was slightly aware of an "Anti-rollback" thing,,,but had no idea it would apply to same and inter-version version of OS. I still don't get why flashing the 20j bootstack on top of the current 20e rom would have caused the video freezing of youtube issue. Standard troubleshooting measures dictated to flash back to the 20e Bootstack to see if the issue went away(I have flashed back and forth bootstack etc on my G3 before with no issues).
Whelp......I guess myself and the other user (SIGMAxB) the 2 confirmed hard bricks served as the community warning........and my very first hard brick and loss of a device in such a fashion. THankfully, I was able to find last night another used V10 on Swappa that is already root and TWRP...for slightly less money that what I paid for my now bricked device. Least I had made an LG backup last week, and all my data is on the External SD card...but still gonna be annoying to have to start over......
Any mad scientist or master flasher who knows how to recover such a bricked device... I would be interested in sending it to them to fix....(I doubt T Mobile will give me a new one, nor wil LG Service the device. It's still under LG warranty, but their site requires u upload a copy of the receipt, and their terms state only covers original owner. So used phone off Swappa.....does not qualify. )
Dropped off my phone at a place called CPR (Cell Phone Repair). Thier location near me is more advanced than most others in that they can do data recovery and software kind of things. They said they may be able to fix phone, but he isn't very sure. Said there will be some techs in tomorrow that are more advanced that may be bale to help. I personally don't have much hope, but worth a shot at this point.
Until then...using my Moto X Pure for now...while I wait for the replacement V10 i bought off Swappa to arrive.
That really bites man.....I'm sorry.
I'm a prepay customer....they have different policies for us vs post paid customers.
I called 611 and got transferred around a bit. But finally got them to process a warranty exchange. I have to ship them the phone and they will send me a new one....hopefully. They didn't mention anything about a charge.
So at least I have that option to pursue should CPR place fail to reflash phone.
speedingcheetah said:
I flashed V10_H901_V20J_Stock_BootStock_Part1_20160810.zip ...that booted fine. But then I used pheon for a while and noticed YouTube was having issues of videos freezing but audio playin...a few others posted they had the same thing.
So I booted to TWRP and flashed the olde rP1 .zip for the orginal bootstock and hit reboot system and no...Nothing!
Black screen. No vibrate when I try vol down + power. When i try Vol up and connect usb to my computer...It shows "Qualcomm HS-USB QDLoader 9008 (COM8). LG Up says it cant find anything.
Usb device descriptor failed in Device manager when I do vol down and plug in.
I have no idea what do? Help? I have been searching a few forums, but not really sure what is happening.
Click to expand...
Click to collapse
I did the same thing. It really sucks because I been doing this for over 5 years and this is my first brick. I guess thats what we get for having faith in a developer that should of known or properly tested this before putting a rom out.
supreme329 said:
I did the same thing. It really sucks because I been doing this for over 5 years and this is my first brick. I guess thats what we get for having faith in a developer that should of known or properly tested this before putting a rom out.
Click to expand...
Click to collapse
While I agree that things should be tested...or otherwise noted that it has or hasn't been so.... (OP does have Status: Testing posted)
It wasn't the rom, his 20e rom runs great. But the updated P1 20j(bootloader)zip....it was the act of reverting and flashing the previous Bootloader version that caused the Hard Brick.
Until this point, I (and many others here) had not seen anything about the Anti-Rollback feature being an issue while on the same Android OS version (LP or MM builds). Now we know it is.
Additionally, the other posts on Eliminater74, rom forum....are indeed users reporting issues with the 20j zip...(mainly Video recording and YouTube streaming). However, the phone is not bricked.
Unfortunately, it's on us folks who flashed it right after it was released and then tried to revert who got screwed. It is definitely a good idea to wait a few days after something is posted to be sure others, mainly early adopters, don't report issues. If your phone is mission critical and you can not be without it or risk having a issue, then modding is not what you should be doing. Or at the very least, once you do get something flashed and stable.....stick with it (that voice in the back of my head was telling me this when i decided to try the update).
I am not sure as to how Eliminater74, had tested the P1 20j bootstack flashed to his 20e rom....but yes,,,,it does suck that this happened...but I am kicking myself in the head...not the dev. At least mine and the 2 others gave him waring and he was able to post a big red warning on the OP. Though I would suggest he remove the 20j part.....but that is up to him.
Least i had a backup phone to make use of until i can get a new V10...very annoying to have do so...but its something.
PS: I am actually starting to like my Moto X Pure more. Dual front facing speakers really nice. ON stock rom now, but used Bliss or while....that's is very nice and super tweakable. Screen isnt has sharp as the v10....and camera is just super basic. I also miss tap to unlock and the other LG specific features...but stock android is growing on me. The BT toggle has a dropdown to select devices to connect to right there, very convenient.
I'm definitely buying LG phones
this latest LG phone
wised
If someone is being Qualcomm 9008 brick please contact tungkick to unbrick Done
PjLyTam said:
If someone is being Qualcomm 9008 brick please contact tungkick to unbrick Done
Click to expand...
Click to collapse
left my phone with a place called CPR, Cell Phone Repair. I doubt they will be able to do anything with it. But once i get it back...probably tomorrow if they don't get back to me. I will see about that. Although, I did get t-mobile to approve an exchange, but i have to ship them my phone back first.
Just got a replacement V10 used off of Swappa. It already has Eliminator rom on it, though not sure what build. Attempting to restore my backup file to it.
debrick done ^^
So... tungkick is awesome! Phone unbricked.. without data wipe
BUt stuck on 20j now...
BUT....now i have a 2nd v10.....lol!.
tungkick said:
debrick done ^^
Click to expand...
Click to collapse
I assume there is a reason you haven't released this method and files publicly on XDA right?
I also am assuming you don't want me or others spreading this to others.
If i am wrong, please let me know.
speedingcheetah said:
I assume there is a reason you haven't released this method and files publicly on XDA right?
I also am assuming you don't want me or others spreading this to others.
If i am wrong, please let me know.
Click to expand...
Click to collapse
no it new because i get phone brick customer of vietnam yesterday then find solution unbrick it.
---------- Post added at 07:17 AM ---------- Previous post was at 06:49 AM ----------
http://forum.xda-developers.com/tmobile-lg-v10/development/debrick-phone-h901-qualcomm-9008-t3440359
tungkick said:
debrick done ^^
Click to expand...
Click to collapse
Hello
Hard Brick H901
I applied right here commands
http://lgviet.com/forum/threads/huo%CC%81ng-da%CC%83n-unbrick-v10-h901-qualcomm-9008.59550/
phone is opened from sd card
but it does not switch to download mode
When switching to download mode puts reset
the picture looks
So, this is what happened, and I have no idea how to fix this, nor I am going to try something made for other devices unless it's my only choice.
I woke up one day after wanting to revive this phone, and I realise it's bricked, totally. No Charging animation, bootup, not even Fastboot Mode.
If I connect it to Windows just the way I do to activate Fastboot, I get a ton of drives on the main computer folder, which all need formatting. (http://imgur.com/hoxrbaw) Only one can be read, but it has quite some weird files. (http://imgur.com/fAHyaly).
The Device Manager shows me quite a weird driver, called QHSUSB_BULK (http://imgur.com/b9KPIVT).
I did re-flash the Factory ROM using the correct drivers, the correct ROM and Coolpad Download Assistant v1.86.
There is nothing else I know about...
http://imgur.com/a/D4QCo
Is there any way I can recover my phone?
Thanks,
-TheTNTLovers
The Only thing I managed is to do nothing because I don't have an identical phone. Can someone send me an eMMC file of Vodafone Smart 4 Turbo 890N?
-TheTNTLovers
Take out the battery and put it in again. I've got that exact phone model and it happens all the time. It was especially scary as it happened after I first backed up via FlashFire.
Unfortunately, I did this quite a lot of times, for over 20 times, and nothing.
Do you have the same phone and can you provide me a eMMC image from it? so I can re-flash it and make it work again...
Thanks!
I managed to get a red Charging LED for about 5 seconds, then it stopped. I re-plugged it in and nothing.
I took the battery out and re-plugged it in, then I got the same LED, but shorter.
Unfortunately, that is quite all I got.
I can't do much but trying YGDP, but this is all I know for now.
Is there something I am missing?
I believe that I hard bricked by trying to install another OS on it, but the cable got damaged and we got a bit of an error that hard bricked the device.
Can you guys give me any bit of advice on this specific phone?
TheTNTLovers said:
Unfortunately, I did this quite a lot of times, for over 20 times, and nothing.
Do you have the same phone and can you provide me a eMMC image from it? so I can re-flash it and make it work again...
Thanks!
Click to expand...
Click to collapse
I do, but I literally have no idea what an eMMC image is. I CAN provide you with everything else. To my understanding, there are actually no ROMs for this phone, which is disappointing.
It means a backup image made from the phone with a certain flash tool. If you make one, I need both the image AND the flash tool you used.
I already sent the phone to service, and I will have it replaced. If you can supply me with ANY info about this phone I had trouble with, then please do.
Thanks,
TheTNTLovers.
Would a *complete* FlashFire backup work? It backs up literally everything.
Can someone send me an eMMC file of Vodafone Smart 4 Turbo 890N?
Hi, we need proper loader for this device. All other files can be extracted from cpb. I have nck, umt and infinity boxes, but they don't support it. If anybody can share a loader to flash in edl mode it will be great.