Develop Bugs

[Q] Possible brick? Any ideas?

Hey guys, I think I screwed up here and I'm wondering if anyone else has had this problem:
Basically, I had a rooted E4G Touch with a custom ROM installed. I went to install ANOTHER custom ROM THROUGH ODIN, as this previous ROM (I believe it was a Calkulin variant) did NOT have CWM recovery. During the ODIN process, something went wrong, and my computer/ODIN...basically, everything froze up while doing the MODEM portion. NOW I can't do anything.
- CWM was able to install on the thing...but it does not recognize my external SD card now. Every time I try to mount it, I get a "Error mounting /emmc".
- I'm still able to get into download mode on the phone, however the phone is not recognized on any computer I've tried. I've attempted multiple computers/USB cords and nothing picks it up.
I'm running out of ideas here. I picked up a USB jig that should be here soon, so I'm going to try that and reset the counter....which leads me to my next question: If I use that, can I take the thing back to Sprint and get a replacement? I have the insurance plan and everything, so if they won't take it back because of the custom software I guess I could always smash it or something...
Any help would be appreciated!

munson11 said:
Hey guys, I think I screwed up here and I'm wondering if anyone else has had this problem:
Basically, I had a rooted E4G Touch with a custom ROM installed. I went to install ANOTHER custom ROM THROUGH ODIN, as this previous ROM (I believe it was a Calkulin variant) did NOT have CWM recovery. During the ODIN process, something went wrong, and my computer/ODIN...basically, everything froze up while doing the MODEM portion. NOW I can't do anything.
- CWM was able to install on the thing...but it does not recognize my external SD card now. Every time I try to mount it, I get a "Error mounting /emmc".
- I'm still able to get into download mode on the phone, however the phone is not recognized on any computer I've tried. I've attempted multiple computers/USB cords and nothing picks it up.
I'm running out of ideas here. I picked up a USB jig that should be here soon, so I'm going to try that and reset the counter....which leads me to my next question: If I use that, can I take the thing back to Sprint and get a replacement? I have the insurance plan and everything, so if they won't take it back because of the custom software I guess I could always smash it or something...
Any help would be appreciated!
Click to expand...
Click to collapse
The ROM you flashed through ODIN was for this phone, right?
What custom ROM are you referring to that was available through ODIN?

assuming you flashed the right ROM, start with the basics..if you can get into download mode then try a simple reboot of your computer. Sometimes Odin won't recognize after it has been run
Sent from my SPH-D710 using xda premium

barnacles10 said:
The ROM you flashed through ODIN was for this phone, right?
What custom ROM are you referring to that was available through ODIN?
Click to expand...
Click to collapse
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
JohnCorleone said:
assuming you flashed the right ROM, start with the basics..if you can get into download mode then try a simple reboot of your computer. Sometimes Odin won't recognize after it has been run
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I attempted this as well Went through and rebooted the computer with the phone plugged in. Rebooted with it not plugged in. Plugged the phone in with ODIN on the screen and started it up. Started it up unplugged, went into download mode on the phone, and then plugged it in. Still nothing.
And I just realized I posted this in General and not Q&A...and chance I could get this moved since I am clearly out of my mind right now?

munson11 said:
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
Click to expand...
Click to collapse
The only odin component involved with flashing CM9 is flashing a gb kernel with a CWM recovery. I haven't seen a cm9 tar, this is why I'm confused. Finding out exactly what you flashed will help in understanding what the problem is.
To flash cm9 you need to odin a gb cwm kernel and then boot to recovery and install cm9. However, that's not a tar, its an update.zip.

barnacles10 said:
The only odin component involved with flashing CM9 is flashing a gb kernel with a CWM recovery. I haven't seen a cm9 tar, this is why I'm confused. Finding out exactly what you flashed will help in understanding what the problem is.
To flash cm9 you need to odin a gb cwm kernel and then boot to recovery and install cm9. However, that's not a tar, its an update.zip.
Click to expand...
Click to collapse
Yeah it was definitely a tar.md5 file, which leads me to believe I was incredibly dumb and possibly flashed a ROM for a different model phone. I'm having difficulty finding the post now which is very strange. This could be one of those moments where I take a good hard look in the mirror and figure out just what the heck I was thinking.
I'll keep looking for what exactly I did wrong, but in the mean time is there anything else I could attempt or look for short of attempting that USB jig and making a trip to Sprint? I'm feeling like a huge idiot right now. I've done this how many times now and when I finally make a mistake, it turns out to be huge.

munson11 said:
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
I attempted this as well Went through and rebooted the computer with the phone plugged in. Rebooted with it not plugged in. Plugged the phone in with ODIN on the screen and started it up. Started it up unplugged, went into download mode on the phone, and then plugged it in. Still nothing.
And I just realized I posted this in General and not Q&A...and chance I could get this moved since I am clearly out of my mind right now?
Click to expand...
Click to collapse
Maybe you should post the link to exactly what you were flashing...

http://www.addictivetips.com/mobile/cyanogenmod-9-galaxy-s-ii-download/
Please tell me this isnt what you flashed.
Sent from my SPH-D710 using xda premium

munson11 said:
Yeah it was definitely a tar.md5 file, which leads me to believe I was incredibly dumb and possibly flashed a ROM for a different model phone. I'm having difficulty finding the post now which is very strange. This could be one of those moments where I take a good hard look in the mirror and figure out just what the heck I was thinking.
I'll keep looking for what exactly I did wrong, but in the mean time is there anything else I could attempt or look for short of attempting that USB jig and making a trip to Sprint? I'm feeling like a huge idiot right now. I've done this how many times now and when I finally make a mistake, it turns out to be huge.
Click to expand...
Click to collapse
Well ultimately you can try uninstalling / reinstalling drivers. But you say this issue exists across multiple pcs so that likely isn't it.
You can try another cable and see if you have any success with that.
Other then that, it kinda really depends what is in that tar you flashed. Once you find it, post the link, and that will help troubleshoot your issue.

playya said:
Maybe you should post the link to exactly what you were flashing...
Click to expand...
Click to collapse
lballer69 said:
http://www.addictivetips.com/mobile/cyanogenmod-9-galaxy-s-ii-download/
Please tell me this isnt what you flashed.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Haha I am a freaking idiot. How in the heck did I manage to do this...I definitely flashed this: http://forum.xda-developers.com/showthread.php?t=1419102
I do not know what was going through my head last night...but it was not any sort of smart thoughts. A rope and a sturdy tree are what I require at this point, correct?
Whatever insults you guys would like to throw at me, I will take. I clearly deserve them :'(

munson11 said:
Haha I am a freaking idiot. How in the heck did I manage to do this...I definitely flashed this: http://forum.xda-developers.com/showthread.php?t=1419102
I do not know what was going through my head last night...but it was not any sort of smart thoughts. A rope and a sturdy tree are what I require at this point, correct?
Whatever insults you guys would like to throw at me, I will take. I clearly deserve them :'(
Click to expand...
Click to collapse
Did you flash the bootloader from that device? ie did your steps include this? \/
Make sure you're running ICS bootloaders lower than LPH: Download (flash as PDA with odin or extract and $ sudo heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin)
Click to expand...
Click to collapse

barnacles10 said:
Did you flash the bootloader from that device? ie did your steps include this? \/
Click to expand...
Click to collapse
Negative, I started right at the "Using the noob-proof ODIN method:". It said noob-proof and I decided that would be the easiest. It turns out it is very easy...if you're flashing to the correct phone Plus, I'd used ODIN before and felt comfortable with it.

Ha ha that's the first one for this method......look up jtag they may fix it for u if u don't have USB .... About 60 with shipping
Sent from my SPH-D710 using Tapatalk 2 Beta-5

munson11 said:
Negative, I started right at the "Using the noob-proof ODIN method:". It said noob-proof and I decided that would be the easiest. It turns out it is very easy...if you're flashing to the correct phone Plus, I'd used ODIN before and felt comfortable with it.
Click to expand...
Click to collapse
I just downloaded the tar to have a look at whats included.
After flashing this you'll have a bootloader for the intl. sgs2. This is a problem many ran into when original SGS2 leaked tars started surfacing as well.
JTAG might be able to fix it, I'm not sure whether people with this issue were successful or not with JTAG repair as the intl gs2 flashing boat seems to have sailed now. However, a jig will likely do nothing, unfortunately.

barnacles10 said:
I just downloaded the tar to have a look at whats included.
After flashing this you'll have a bootloader for the intl. sgs2. This is a problem many ran into when original SGS2 leaked tars started surfacing as well.
JTAG might be able to fix it, I'm not sure whether people with this issue were successful or not with JTAG repair as the intl gs2 flashing boat seems to have sailed now. However, a jig will likely do nothing, unfortunately.
Click to expand...
Click to collapse
Ok thank you for your help on this. You don't think a jig will reset the counter or anything so that I can take it back to Sprint? If not, I'm not above "dropping" it on the ground and using the insurance I have on it for a replacement.

munson11 said:
Ok thank you for your help on this. You don't think a jig will reset the counter or anything so that I can take it back to Sprint? If not, I'm not above "dropping" it on the ground and using the insurance I have on it for a replacement.
Click to expand...
Click to collapse
I don't foresee it working only because your phone isn't recognized by your pc and the problem doesnt lie on the pc side.
The problem is instead with the port on the phone which leads me to believe it won't recognize a jig either.
A jtag if successful will leave you with more money in your pocket and a non-returb. Something to consider if you've got a backup phone you can use for a few days.

barnacles10 said:
I don't foresee it working only because your phone isn't recognized by your pc and the problem doesnt lie on the pc side.
The problem is instead with the port on the phone which leads me to believe it won't recognize a jig either.
A jtag if successful will leave you with more money in your pocket and a non-returb. Something to consider if you've got a backup phone you can use for a few days.
Click to expand...
Click to collapse
I don't see sprint replacing it with cm9 On it .... And u will need mobile Odin to get back to stock but with it not mounting the Emmc probably can't do that .... That is your hope to get back to stock using mobile Odin someway .... Triangle away app will reset Odin count but with no radio you need to get apps to do it and no sd from what u said ...maybe tell insurance u lost it and get it replaced
Jtag should work also since there is no emmc failure like the blue light of death bricks ...
Sent from my SPH-D710 using Tapatalk 2 Beta-5

[Q] PA_3.99 bootloop

Again fruitless search results when browsing for a solution. So Im posting, PA_3.99 has been refusing to work right after 1st reboot after intitial flash reboot.
It started out twrp was having partition encryption issues, after reverting to PA's kernel i no longer encountered that. But the bootloop that issue caused (or atleast I thought) still continued.
Heres exactly what happens: Full format x2, flash PA, flash PA_Gapps, wipe, reboot (goes normally, go through setup, can use phone normally), second reboot (for whatever reason), bootloop at yellow sub samsung splash screen( not the PA glowing bean.
Idk if this has to do with TWRP or PA's kernel but those are the only things I can think of with my limited knowledge of android.
This will be the 8th time Ive had to format, flash, setup, reboot, and repeat. I love the PA rom and dont want to have to go to stock again just for a working phone.
pls&thx

if your having this problem like i was you wont find a fix here no one seems to know the answer. ive searched and to no avail. 4.3 wont work on your phone no matter what rom you try. ive tried them all its not the newer phone problem because it reads my card with no problem. only happens on 4.3 roms. if you find a solution please post it or pm me i would love to use 4.3. also a guy had same thing on a note or s4 cant remember. we arent the only ones lol. good luck my friend

bbrita said:
if your having this problem like i was you wont find a fix here no one seems to know the answer. ive searched and to no avail. 4.3 wont work on your phone no matter what rom you try. ive tried them all its not the newer phone problem because it reads my card with no problem. only happens on 4.3 roms. if you find a solution please post it or pm me i would love to use 4.3. also a guy had same thing on a note or s4 cant remember. we arent the only ones lol. good luck my friend
Click to expand...
Click to collapse
Mos definitely. Likewise. What did you read? I can't find anything defining the issue on any technical level. Everyone on here seems too good to answer any questions. ive read more smart ass remarks relating to questions asks then actual answer.
This forum just frustrates the **** out me. I'll pm my email. Probably won't be on here too much after this.
Goodluck

Well after fruitless and frustrating attempts to search/ask for a solution I simply tried flashing clockwork Mod through ROM manager on the successful boot. I've had 3 successful boots to PA 3.99.
I really hope I'm not the first to figure this out. No one mentioned this in paranoid androids thread or team win.
Sent from my SPH-L710 using xda app-developers app

Zenfone messed up after install echoe kernel

Hi all,
My zenfone 2 just got messed up after flashing the echoe kernel.
Rom was fine, but the kernel messed everything up. At first the fast charging went missing and the mtp didnt fucntion, also usb otg cannot be detected.
so started my twrp and wanted to flash stock 160 fw. i keep getting the error below;
E:extractTarfork() process ended with error = 255.
I have tried sideload but again, pc doesnt detect my zenfone 2.
Please help...want to go back to stock rooted.

carnby24 said:
Hi all,
My zenfone 2 just got messed up after flashing the echoe kernel.
Rom was fine, but the kernel messed everything up. At first the fast charging went missing and the mtp didnt fucntion, also usb otg cannot be detected.
so started my twrp and wanted to flash stock 160 fw. i keep getting the error below;
E:extractTarfork() process ended with error = 255.
I have tried sideload but again, pc doesnt detect my zenfone 2.
Please help...want to go back to stock rooted.
Click to expand...
Click to collapse
flash prims barebone via twrp, or else first flash stock recovery and thn adb sideload firmware
and did you reported this at his thread??

say99 said:
flash prims barebone via twrp, or else first flash stock recovery and thn adb sideload firmware
and did you reported this at his thread??
Click to expand...
Click to collapse
yes i did, but i was kicked out of the thread...

trying it now..let me see if your suggestion works...

carnby24 said:
yes i did, but i was kicked out of the thread...
Click to expand...
Click to collapse
weird I didnt see anyone else complaining such things, and yes it will work so relax

Hi, seems the same..i can only restore if i uncheck system from the list of backup options. But fast charge and mtp and otg function all doesnt seem to work.
Sent from my ASUS_Z00AD using Tapatalk

I miss my fast charge and adb function..please help guys..
Sent from my ASUS_Z00AD using Tapatalk

Reflash the latest rom v1.1 , hopefully everything will work fine then

anyone know whats the reason for this??

unmount system before flashinh prism barebone, you wont get error if you unmount system

serhangelgor said:
unmount system before flashinh prism barebone, you wont get error if you unmount system
Click to expand...
Click to collapse
is this the same if i want to flash stock?

carnby24 said:
is this the same if i want to flash stock?
Click to expand...
Click to collapse
didnt tried on stoct, idk

Guys! Is there any chance my problem (http://forum.xda-developers.com/zenfone2/help/asus-zenfone-2-recognized-pc-t3294980) is related with this issue?
Reflashing stock recovery could help? I´m afraid to do it and not be able to recover any thing else or get stuck on boot without usb connection.
Another question: This might be related to kernel? i´m using BitOkObssesion

I am not sure what went wrong on your side. But i flashed the kernel on a phone of a friend and he has no issues at all.
Did you try to download again ? Maybe a bad download..
Sometimes it happens

carnby24 said:
Hi all,
My zenfone 2 just got messed up after flashing the echoe kernel.
Rom was fine, but the kernel messed everything up. At first the fast charging went missing and the mtp didnt fucntion, also usb otg cannot be detected.
so started my twrp and wanted to flash stock 160 fw. i keep getting the error below;
E:extractTarfork() process ended with error = 255.
I have tried sideload but again, pc doesnt detect my zenfone 2.
Please help...want to go back to stock rooted.
Click to expand...
Click to collapse
Every ROM developer or Kernel developer spent a lot of his time on making better experience for user
i personally have my own ROM and i did try Echoe ROM & AEL Kernel because its from Awesome Developer and everyone loves him and he's kind to everyone
many users used his ROMs and Kernels and never experience hardware or software problems because he checks every single detail of his work
all problems that you mentioned cause by Asus and many users sent their devices to service center, so please dont blame anyone about
something they did do and research next time before post something similar
im still using AEL Kernel without any problems
BTW
TWRP backup is broken for our device, Reboot again to recovery and dont select Data or Cache in Restore options
and check this post

Wow..thanks..will try it...thanks..didnt know..cos before this used to select all data and cache..no problem..

carnby24 said:
Wow..thanks..will try it...thanks..didnt know..cos before this used to select all data and cache..no problem..
Click to expand...
Click to collapse
Good luck with it
and for adb and mtp, did you tried other pc ?
or other cable ?
if its the same then its from Asus :crying:
can you please remove "echoe kernel" from thread title and from the thread also ?

But what about the MTP function and fast charing? Doesnt seem to work now.Tried all other PC and cables as well. Still the same.

AL_IRAQI, so you´re saying thats a hardware related issue? i´m asking because i got the same issue but with another rom...
tried different cables different pcs and nothing

carnby24 said:
But what about the MTP function and fast charing? Doesnt seem to work now.Tried all other PC and cables as well. Still the same.
Click to expand...
Click to collapse
Restore Stock and go to Asus service center, Asus messed up these things in latest update

Bricked phone? Possible fix?

Attempted to go back to stock ROM. From TWRP, I wiped everything except external and shutdown. Attempted to restart and nothing. Deader than or door nail. Pulled the battery and held down the power button for over a minute with no affect. Battery was 75% charged with I performed the wipe. I connect to phone to my pc and get a "USB Device Not Recognized"
Is the phone a lost cause?
Thanks,
Jeremy

gimmezell said:
Attempted to go back to stock ROM. From TWRP, I wiped everything except external and shutdown. Attempted to restart and nothing. Deader than or door nail. Pulled the battery and held down the power button for over a minute with no affect. Battery was 75% charged with I performed the wipe. I connect to phone to my pc and get a "USB Device Not Recognized"
Is the phone a lost cause?
Thanks,
Jeremy
Click to expand...
Click to collapse
If you wipe everything but extSdCard, you must flash something. Either flash stock tar update in Odin or flash a custom ROM in recovery.
Help any?
Sent from my SM-N920P using Tapatalk

Yes, I know. I was going to go into download mode to Odin stock ROM but the phone will not even turn on anymore.

gimmezell said:
Yes, I know. I was going to go into download mode to Odin stock ROM but the phone will not even turn on anymore.
Click to expand...
Click to collapse
OK. Did you try a long battery pull and try again?
Edit: I may have misunderstood you but you did say you tried to restart. Did you mean download mode with long press of volume up, home plus power button combination.
Sent from my SM-N920P using Tapatalk

Sorry for any confusion. I pulled the batter for a good ten minutes and still unable to turn the phone on. Plugged the phone into a charger has no effects on it either.

So download and recovery key sequence fails for both? Plugging in charger or USB to PC, no beep or display?
What version of TWRP were you using? If 3.0, did you get it from official site? How did you install it?
Sent from my SM-N920P using Tapatalk

Yes, both download and recovery key sequences fail. Plugging into charger, no charge LED comes, no haptic feedback, no beep or display. When I plug it into my computer it says "USB Device Not Recognized".
EDIT - I'm pretty sure my bootloader is hosed.

gimmezell said:
Yes, both download and recovery key sequences fail. Plugging into charger, no charge LED comes, no haptic feedback, no beep or display. When I plug it into my computer it says "USB Device Not Recognized".
Click to expand...
Click to collapse
Just curious about the TWRP version. There's been a couple or more cases like yours and it seemed to show up about the time users reported issues with TWRP update.
I think you should get the phone checked by a tech or engineer. Sprint has been helpful to users having hardware failure with issues like updates bricking the phone. With flagship phones not selling well and carrier wars, retention is key and nearly economical right now.
Sent from my SM-N920P using Tapatalk

Yeah, TWRP 3.0 did come up on my searches. I did have TWRP 3.0 installed that I got from their official site.
I did see the below post on how to unbrick that tells me it may be possible to a Note 4 image onto an sd card.
http://forum.xda-developers.com/showthread.php?t=2660566

Did this work for you? I also have twrp 3.0 and hope to not run into an issue like this.

Alakazamm said:
Did this work for you? I also have twrp 3.0 and hope to not run into an issue like this.
Click to expand...
Click to collapse
I'm using 3.0 too but I waited for the official version that worked and flashed in Odin. No issues for me. Hoping it stays that way.
Sent from my SM-N920P using Tapatalk

gimmezell said:
Yeah, TWRP 3.0 did come up on my searches. I did have TWRP 3.0 installed that I got from their official site.
I did see the below post on how to unbrick that tells me it may be possible to a Note 4 image onto an sd card.
http://forum.xda-developers.com/showthread.php?t=2660566
Click to expand...
Click to collapse
Alakazamm said:
Did this work for you? I also have twrp 3.0 and hope to not run into an issue like this.
Click to expand...
Click to collapse
I did not attempt what was done in the link I posted in my previous post. Today, I mailed the phone off to someone that offers a de-bricking service. Hopefully, they can recover it. I will I knew exactly happened as I did the same procedure many times before. Right now I'm retro-ing it and rocking my Note 2 with STOCK firmware and everything works. :good: :laugh:
@samep mentioned that there were other TWRP 3.0 users that experienced to the something I did or similar. I'm just curious where those threads/posts are.

gimmezell said:
I did not attempt what was done in the link I posted in my previous post. Today, I mailed the phone off to someone that offers a de-bricking service. Hopefully, they can recover it. I will I knew exactly happened as I did the same procedure many times before. Right now I'm retro-ing it and rocking my Note 2 with STOCK firmware and everything works. :good:[emoji23]
@samep mentioned that there were other TWRP 3.0 users that experienced to the something I did or similar. I'm just curious where those threads/posts are.
Click to expand...
Click to collapse
First, I want to acknowledge that what yourself and others have experienced is personal and disappointing. eMMC flash is not the most reliable, efficient and cutting edge memory but it's common to cell phones of previous generations like ours.
It's not easy making an argument that UFS 2.0 used in 2015 Samsung phones is more reliable and less prone to failure but it is faster, lower voltage and far less prone to heat buildup with increased data transfer. So I think that makes a point in favor of the newer tech. Building ART/dalvik-cache can generate a lot of heat as well as 4k recording. The eMMC NAND contributes to that and could also be its undoing.
http://m.tech.firstpost.com/news-an...move-next-gen-ufs-2-0-memory-2015-242072.html
Interesting to see if UFS memory is any more reliable in the months ahead and if Samsung continues to use it this year with micro sdcard making a return to S7. But flashing alone, we know is risky. Proving an application or particular flash causes such would be difficult to prove and it wasn't my intent to point at a particular shared development that is shared freely on XDA. I could have worded that better when I said I hoped my phone continues with no issues- not meaning it to sound like the concern because I flashed the new TWRP. I was merely pointing to the increase of flashing lends to more hardware failure in this forum. We've seen this also with updates and increased flashing when users are confused about which stock tar to flash or thinking they can just go back to KitKat through Odin of KitKat tar. Not blaming users for their failures; anyone of us can the victim with a single flash, not to mention the many flashes and extended boots that are added to a rooted phone's life. To add to that, Samsung still has fixes pending and concerns with download mode.
http://www.slashgear.com/samsung-galaxy-smartphones-receive-security-update-25424269/
Rooted phones may not be getting these updates until another stock tar is released.
Anyway, related or not, here's some other recent failures. There may be others but I'm not trying to prove anything other than saying it seems we have more memory failures than we should on the Note 4.
http://forum.xda-developers.com/note-4-sprint/help/hard-brick-sudden-death-mobo-fried-t3316335
http://forum.xda-developers.com/note-4-sprint/help/screen-pit-partition-firmware-install-t3316162
http://forum.xda-developers.com/showthread.php?p=65018833
I do hope you get a successful and economical repair. It's good that you have a backup phone. And I hope you'll update this thread with progress and result. Best wishes.
Sent from my SM-N920P using Tapatalk

Thank for the info and links @samep.
Update
I sent my phone off last Wednesday to hopefully have it de-bricked and I am happy to report that I will have it back tomorrow. Apparently, some how the custom recovery wiped the boot partition. I'm tempted to keep it stock as my backup phone is stock, uprooted and it just works. Ha
I've ordered a pair of Acker batteries because I was told by Joe, the person who un-bricked my phone, that the battery would drop from 100% to 80% within five minutes.
Needless to say I'm happy to get my Note 4 back tomorrow.
Sent from my SPH-L900 using Tapatalk

usb device not recognized

Hey ,
the problem is caused after i upgraded from lollipop v21a(TWN) to marshmallow hongkong using LGUP , well now i have a phone with no wifi or signal or any kind of network and what is even worse is that I can't connect it to computer .. the computer wont recognize it no matter what i do , i tried changing cables , reinstalling the drivers , and trying in download mode ... well so far none helped.
anyone familiar with this problem ? is there a solution or i just destroyed my phone beyond repair :/ ? oh and if it matters the phone does charge when connected to computer
any help would be appreciated , thanks in advance.
***short version i flashed a d858 rom in to a d855 phone and now the pc cant recognize the phone even in download mode , any idea what shall i do ? ***

any idea any one please ? :crying:

It's odd that it won't even charge from the PC. Did you try charging it from just a simple wall charger to see if it would work? Or try a different PC?

my.ads0 said:
It's odd that it won't even charge from the PC. Did you try charging it from just a simple wall charger to see if it would work? Or try a different PC?
Click to expand...
Click to collapse
i said it does charge

patrs63 said:
i said it does charge
Click to expand...
Click to collapse
DOES! D'oh.
Well, first thing I'd check is the USB configuration. Go to settings, developer options, Select USB Configuration. See if for some reason it's stuck on Charging Only. Unfortunately, I don't think that will help, but might as well try.
Other than that, maybe you have an microSD Card lying around that you could load with a new ROM and associated bootstack and reload the ROM from there?

my.ads0 said:
DOES! D'oh.
Well, first thing I'd check is the USB configuration. Go to settings, developer options, Select USB Configuration. See if for some reason it's stuck on Charging Only. Unfortunately, I don't think that will help, but might as well try.
Other than that, maybe you have an microSD Card lying around that you could load with a new ROM and associated bootstack and reload the ROM from there?
Click to expand...
Click to collapse
i will try that , but is it possible to do that without root ? I'm not very positive that it would read the sd card though but it is worth a shot .. but how exactly to do that
how can i flash a rom without a twrp or root ?
(if there is way to do so) can you tell me which bootstack i need to flash for kitkat (4.4.2) and which to lolipop 5.0 , or a link to download would be even better since i can't seem to find them

patrs63 said:
i will try that , but is it possible to do that without root ? I'm not very positive that it would read the sd card though but it is worth a shot .. but how exactly to do that
how can i flash a rom without a twrp or root ?
(if there is way to do so) can you tell me which bootstack i need to flash for kitkat (4.4.2) and which to lolipop 5.0 , or a link to download would be even better since i can't seem to find them
Click to expand...
Click to collapse
Oh... You mean that you flashed a custom without a custom recovery while not rooted?

my.ads0 said:
Oh... You mean that you flashed a custom without a custom recovery while not rooted?
Click to expand...
Click to collapse
well I didnt flash a custom ( i flashed a wrong official marshmallow only-for the wrong device it seems) , and yeah i did that without a root or a custom recovery ... i did it through pc

Wish I could help more, but that territory is beyond my expertise. Sorry.

my.ads0 said:
Wish I could help more, but that territory is beyond my expertise. Sorry.
Click to expand...
Click to collapse
no problem , thanks for trying mate