Develop Bugs

[Q] Hard bricked. Found out something, but doubt it means anything

I accidentally flashed ktoonsez i777 rom on my i747 in a hurry to do so and when it aborted, I realized it was wrong. Not thinking about it, I just restarted from cwm because usually when it aborts, it just reverts. Now my phone does nothing. I was able to aquire the drivers for the mode it is in when it's bricked and it detects it, but odin sees nothing. It says its on COM10 in device manager. I think it was qhusb or something. Anyway, it is not an unknown device anymore and I have read all about this and how everyone does jtag, but is there any software that CAN detect the phone to add any kind of files? I read that somebody was able to find some software to detect it, but this was one person. Any help would be appreciated and I'm sorry for possibly going on a sore topic again, but I REALLY would rather not send this to jtag if I can help it.

Can you get into download mode?
Sent from my SGH-I747 using xda app-developers app

This is his buddy, no he can't. Phone is in some other mode, and unresponsive.
Sent from my Galaxy Nexus using Tapatalk 2

RicoStang said:
I accidentally flashed ktoonsez i777 rom on my i747 in a hurry to do so and when it aborted, I realized it was wrong. Not thinking about it, I just restarted from cwm because usually when it aborts, it just reverts. Now my phone does nothing. I was able to aquire the drivers for the mode it is in when it's bricked and it detects it, but odin sees nothing. It says its on COM10 in device manager. I think it was qhusb or something. Anyway, it is not an unknown device anymore and I have read all about this and how everyone does jtag, but is there any software that CAN detect the phone to add any kind of files? I read that somebody was able to find some software to detect it, but this was one person. Any help would be appreciated and I'm sorry for possibly going on a sore topic again, but I REALLY would rather not send this to jtag if I can help it.
Click to expand...
Click to collapse
Huh? You flashed Ktoonsez's i777 rom? he doesn't have an i777 rom. you mean you flashed his kernel onto this device or what? If you flashed aokp for the i777 then you would be referring to me then. Still unsure what you are talking about flashing so I can't help you out until i know.

NickS_ said:
This is his buddy, no he can't. Phone is in some other mode, and unresponsive.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
What is this other mode? Open task manager and close everything related to Kies before trying Odin.. see if that helps at all

task650 said:
Huh? You flashed Ktoonsez's i777 rom? he doesn't have an i777 rom. you mean you flashed his kernel onto this device or what? If you flashed aokp for the i777 then you would be referring to me then. Still unsure what you are talking about flashing so I can't help you out until i know.
Click to expand...
Click to collapse
I'm apologize. I used to mod the hell out of my old Motorola's before smartphones were mainstream, but I'm new to this again. I flashed his aokp for the i777. I had the 11/4 version for the i747 and I saw that something came out more recently for the aokp so I went to flash that and saw that it was the i777 version when I looked at the file after it aborted and figured I could reboot and it would work. This is when absolutely nothing happened. I accidentally did this same thing with the i747 version on my girlfriends SII and once I saw that it was the wrong version, it just reverted upon reboot which is why I thought it would do the same for me. I know you guys don't make guarantees and it was my fault. I love this aokp and I'll still use it. I'm just a bit upset that I hard bricked because I don't want to have to send my phone out to be jtagged. I can't get it into download mode and I heard on several posts that USB jigs wont work on this phone for forcing it unless the phone isn't bricked (which is kind of useless if you ask me). After this all happened, it came up in windows as QHSUSB_DLOAD as unrecognized. After searching for a while, I found and installed drivers and it now recognizes it, but it wont come up as a device in ODIN. I'm assuming I'm kind of screwed here I'd really appreciate any help or advice other than to return it. I understand I may have to do that, but I'm looking for a solution here. I see that this has happened with a lot of GS3's for various reasons and I'm surprised there isn't a fix yet. Thanks in advance for help.

Update! I'm not sure if this means anything or not, but I have QPST running and the phone is on COM11 and it is detecting it in download mode. Once again, ODIN, will not read this, but QPST is. It is asking me for a phone image to flash in the form of a .hex .hxb .pbn .bin. or .mbn
I can't do much in this software because I'm in QPST download mode, but it looks like it will allow me to flash files with these extensions. Not sure if this matters, but I'd love to find a solution to this bricking issue to save people the money of having to send a phone out or hassle insurance returns and having to run over a poor GS3 with a car to "accidentally break" it. Does anyone have files like this that I can flash?

Alright I got some .mbn files and one .bin using 7zip extracting from a stock rom. On the .bin when I try to flash it, I get "Use the phone's UI to switch it to streaming download mode" and NAK: invalid address when attempting the .mbn flash. I'm getting a bit discouraged again. The only area I can use is "software download" because I can't do anything else with the phone. I'm going to sleep though. Hopefully there will be some insight in the morning. Glad I have developers here!

Follow this thread, though it's mainly about msm8660 for now: http://forum.xda-developers.com/showthread.php?t=1914359

RussianBear said:
Follow this thread, though it's mainly about msm8660 for now: http://forum.xda-developers.com/showthread.php?t=1914359
Click to expand...
Click to collapse
Thanks!

RicoStang said:
I accidentally flashed ktoonsez i777 rom on my i747 in a hurry to do so and when it aborted, I realized it was wrong. Not thinking about it, I just restarted from cwm because usually when it aborts, it just reverts. Now my phone does nothing. I was able to aquire the drivers for the mode it is in when it's bricked and it detects it, but odin sees nothing. It says its on COM10 in device manager. I think it was qhusb or something. Anyway, it is not an unknown device anymore and I have read all about this and how everyone does jtag, but is there any software that CAN detect the phone to add any kind of files? I read that somebody was able to find some software to detect it, but this was one person. Any help would be appreciated and I'm sorry for possibly going on a sore topic again, but I REALLY would rather not send this to jtag if I can help it.
Click to expand...
Click to collapse
When i got hardbricked i sent it to samsung got it fixed completly i obviously had to pay cuz there were scratches on it but u could probably get away with it blaming a samsung software update and get it fixed for free

I like that lol. I didn't even think of that method. I am kicking myself repeatedly for not getting insurance so I could just run over the damn thing!

RicoStang said:
I like that lol. I didn't even think of that method. I am kicking myself repeatedly for not getting insurance so I could just run over the damn thing!
Click to expand...
Click to collapse
That's how I feel right about now haha

RicoStang said:
I accidentally flashed ktoonsez i777 rom on my i747 in a hurry to do so and when it aborted, I realized it was wrong. Not thinking about it, I just restarted from cwm because usually when it aborts, it just reverts. Now my phone does nothing. I was able to aquire the drivers for the mode it is in when it's bricked and it detects it, but odin sees nothing. It says its on COM10 in device manager. I think it was qhusb or something. Anyway, it is not an unknown device anymore and I have read all about this and how everyone does jtag, but is there any software that CAN detect the phone to add any kind of files? I read that somebody was able to find some software to detect it, but this was one person. Any help would be appreciated and I'm sorry for possibly going on a sore topic again, but I REALLY would rather not send this to jtag if I can help it.
Click to expand...
Click to collapse
So, I know this is basically a dead post... but I was wondering if you ever found the solution to this issue? I am experiencing basically the same thing with my i747. Luckily, I purchased a cheap HTC Inspire off of Ebay to use for the time being, but I feel like I am seriously on the brink of figuring this out and its driving me mad. If you did have any luck, I'd love to hear about it!

[Q] Nexus bought in china strange ROM

Hi. First of all this is not a standard "bought in China" thread.
Phone is Samsung Galaxy Nexus i9250
Althought the phone was sold as new it was pre rooted with a custom ROM which I believe came from SlimRoms.
I have some experience rooting my previous phones but for some reason nothing works on this phone. I've tried CM but always fails, same with downloading ROMS direct from ClockworkMod.
I would really like to change it to run CM but to be honest any change would be welcome but its like something I've never encountered before is blocking any change.
If anyone could help me I'd be a very happy man
I've attached a screenshot from the phone showing the kernel and ROM it came with.

dmeinchina said:
Hi. First of all this is not a standard "bought in China" thread.
Phone is Samsung Galaxy Nexus i9250
Althought the phone was sold as new it was pre rooted with a custom ROM which I believe came from SlimRoms.
I have some experience rooting my previous phones but for some reason nothing works on this phone. I've tried CM but always fails, same with downloading ROMS direct from ClockworkMod.
I would really like to change it to run CM but to be honest any change would be welcome but its like something I've never encountered before is blocking any change.
If anyone could help me I'd be a very happy man
I've attached a screenshot from the phone showing the kernel and ROM it came with.
Click to expand...
Click to collapse
Hi! I think in your situation the best way for your nexus is to restore all to stock flashing the google factory image (you can find it here)
After that you can start to reunclock the bootloader, flash a custom recovery or what you prefer.
Tell me if u have some problem to flashing the factory image

Hi, thanks for the advice, I thought you were onto something but unfortunatly not. I have no idea what the seller did to this phone but its like its locked out. I can't get any computer, software or comand to recognise it. It's as if once it conects to the computer its nothing more than a USB even in bootloader it's not seen.

Blu Advance 4.0 L A010U ROMs

Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance

I am really surprised no one has replied yet, but again I am facing the same problem and I've been searching the Internet for one month now and I found absolutely nothing for this phone (specifically for version A010U).
So I am going to post a different question in the hopes that someone will read it and help us out:
I have two Blu Advance 4.0 L A010U phones, which are identical except for the color (white and green). They were manufactured a month apart one in 10/2015 and one in 9/2015.
Unfortunately after only a couple of months of light use and for no apparent reason (did not drop it, or wet it, etc) it started going through a boot loop. It will start, show the "bold like us" logo then restart again without making it to the operating system at all. Like I said I've been looking for over a month to find a ROM (stock or modded) to reflash but with no luck. Then I had an idea. Since I have the other identical phone that's working fine, is there a trick I can do using the working phone to create a ROM that I can use in my broken one. By the way, the non working phone will allow me to get into the recovery menu, but unfortunately nothing happens if I wipe the cache or even if I reset to factory defaults.
Anyone knows what's causing that "boot loop", how to fix it and where to find a ROM or even "extract" or "create" one using a working Advance 4.0 L ???
Thank you very much!

Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.

Deuler93 said:
Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance
Click to expand...
Click to collapse
I just got ahold of a couple of these devices myself and am in the process of going through all the in's and out's of them....I'm a Samsung nerd so I haven't messed with something like these in a while but I got one (that was supposedly dead bricked per the lady friend of mine I got them from) at least able to boot into factory mode and recovery via ADB and just as I'm posting this I'm in adb shell going through the device's internal memory.....so we'll see what all I find and can pull out of this one and possibly know enough to post an intelligible reply with solutions next time
The boot looping sounds like a common problem with these and when I get to that point I'm going to get rid of the stock bootanimation.zip ASAP and try something else. I get the idea that these things aren't exactly power houses built for much so the littlest thing or small bug in their coding could lead to this kind of crap happening.
Hopefully you figure yours out before I toss these out the window! lol
Cheers y salud!
---------- Post added at 02:27 AM ---------- Previous post was at 02:20 AM ----------
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
Forgot to add a couple things about your post, sorry! I beleive (and I just started digging into this phone) that the no command part is the locked bootloader these phones appear to have. I think it was a combo of holding both volume buttons down from a powered off state then pressing power button on that came up with the option for factory mode or recovery (which led to the sad 'no command' droid), i went into factory mode and theres an option for Tp Upgrade which Im assuming is F/W or something similar but I just hooked up to the PC and in that mode it's reading the internal and external memory of the phone and that's about where I'm at so far.

Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.

I can't wait to try it, thank you! And btw, were you able to get root successfully and if so, how?

Deuler93 said:
Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.
Click to expand...
Click to collapse
Hey Deuler93 -
You have my respect for digging out that BLU ROMs link and sharing with the rest of us. I downloaded the one for my Advance and used SP flash tool to flash the phone that was stuck on a boot-loop. Of course first I had to download and install the MediaTeK drivers for USB connectivity with my PC. Everything worked flawlessly, no glitches what so ever. All these links are easily found and widely available online if anyone is interested I can share here too. I just hope that this boot-loop was due to some software glitch and not hardware failure. Everything seems to work fine for now, keepint my fingers crossed it will NOT happen again.
Well, one less headache to worry about. By the way we're not that far, if you're ever in the Chicago area, I owe you a beer or something. Thank you!

Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.

I got temporary root using the kingroot apk. But it messed things up and I don't trust it anymore. None of the other mentioned methods worked for me either, maybe try the PC kingroot method

well this helps one thing
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.

What might happen if a ROM is used for another blu phone. ??
A similar phone as well.
Plz advise.

Damn! This thread just keeps going!
I haven't even looked here in a while, so I will bunch my commentary here. I'm also salaried now, so I bought into a OnePlus X (onyx), a more expensive cheapo device, so I do not use the 4.0L anymore.
As for rooting tools, I used the Kingroot APK successfully in the stock environment. I never tried flashing something SuperSU myself, but it could work. Is flashing a SU app possible from the fastboot interface?
And to Steve's question - it is technically possible to flash a ROM for a different device onto your own device, but is considered a bad idea due to the possibility of introducing incompatibilities and missing proprietary requirements. I feel like this would hold especially true to stock ROMs because the manufacturer probably has no interest in supporting anything more than the device that they are manufacturing for. Doing so removes many possible "compatibility" issues from even having to be considered, but I digress. In short, try to find a ROM made for your device and your device only.

Did you find the zip file for the recovery
Marya Wynter said:
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.
Click to expand...
Click to collapse
i root my blu advance 4.0l a010u with the kingoroot PC apk, but i got some issues with the lock screen and some apps, so, i need some advice..
i was looking for a zip to use it via recovery but i can't find any..

Recover IMEI
srspinho said:
Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.
Click to expand...
Click to collapse
You dont need root to recover imei all you have to do is type *#*#84666364#*#* in your dialer and you will be entered in EngineerMode then go into connectivity ,CDS information and radio information phone 1 or 2 then you will see AT+ type something eg.A then backspace and select the first thing you see. Put a space after AT+ and then put you imei code here "IMEI" between these "" You can find your imei by removing your battery it willl be there. After sending command reboot and imei is back.

links are down....check this instead
Hey guys, links here seems to be down .
Maybe this link would be useful for you all... stock firmware can be downloaded and useful help on videos is available too... Enjoy

Help with editing firmware for Tonghai headunit

Hi guys. I have a tonghai headunit that its stuck in boot. Just reboots everytime. This is due to a corrupted logo in the /etc/logo/ folder. The file is Audi.png
This os firmware i can succesfully flash http://www.mediafire.com/?4idf16t2w5uffl4
The problem is that it wont format the logos, so after the flashing, the issue maintains.
I have no hardware buttons. Just the reset the reboots the device or send it to force flash.
Can i somehow connect the unit to PC using a cable like otg?
Can someone with knowledge edit the fw to format the unit?
I have a system dump with the original logo files of that helps.
I dont know what to do.
Thanks

bump

I can't really help but if you want those that can then you'll need to post a lot more info on your unit.
Like what is it's processor, resolution, current rom, mcu version. And it must have worked at some point. So tell then what you did between it working and not working cos that is likely the problem.
Like I said, I can't help even if you post all that but the guys that know will at least have half a clue.
Sent from my SM-G920F using Tapatalk

Hi
did you solve the problem ( i've the same)?

Note 7 SM-N930F bricked / / need help!

I flashed TWRP with odin.
After that I was not able to boot or start recovery.
Only download mode is possible.
In download mode it shows
warranty void 1 (0x030c)
I also cannot flash anything in odin anymore.
After initializing, it immidiatly stops with the error:
<ID:0/004> FAIL! (DeviceInfo)
Can anybody help me, how to get this beautiful phone running again?
Thanks so much!
MOD EDIT:
This member is talking about this.
TEKHD

bill340 said:
I flashed TWRP with odin.
After that I was not able to boot or start recovery.
Only download mode is possible.
In download mode it shows
warranty void 1 (0x030c)
I also cannot flash anything in odin anymore.
After initializing, it immidiatly stops with the error:
<ID:0/004> FAIL! (DeviceInfo)
Can anybody help me, how to get this beautiful phone running again?
Thanks so much!
MOD EDIT:
This member is talking about this.
TEKHD
Click to expand...
Click to collapse
try to download the firmware from http://samfirm.net/threads/official-rom-full-galaxy-note-7-sm-n930f-n930fxxu1apg7-xxv-23-07-2016.98/ and try to flash via odin.
Never ever try to flash anything till the time there is no evidence of success.

I tried that, but the problem is that I always get this error in Odin when trying to flash...

Did you check OEM unlock before you flash as per the instructions? not doing so will result in a boot loop.

Try different cable and USB port. I had trouble with both that had me running in circles.
Sent from my SM-N910T using Tapatalk

Yes, I did OEM unlock before the flash.
Different cable and USB port makes no difference...

Usually when I have issues I try to uninstall all drivers related to phones and only install the one I need. Then after a restart and forcing the phone into Odin I'm able to flash without issues.

It might be failing because of a Partition size error. Have you tried the Samfirm Tool to download a firmware from your region?
Have you tried Emergency Device Recovery from SmartSwitch PC ?
Also, I'm doubtful whether this is a new trick up from Samsung's sleeve. This Phone is still new, so it's quite a learning process. Maybe Samsung has implemented something to block these unofficial flash attempts. However I thank you taking the risk and trying the recovery first.

Can you help me, where I can get this?
Have you tried Emergency Device Recovery from SmartSwitch PC ?

bill340 said:
Can you help me, where I can get this?
Have you tried Emergency Device Recovery from SmartSwitch PC ?
Click to expand...
Click to collapse
Download and install SmartSwitch for PC. Then follow this Video.

I really have no luck here...
Any idea?
Googled already, but did not really find anything besides reinstalling...

I dont think theres a fix for this issue yet. There's also no subtantiated literature in the larger cummunity pertaining to rooting the Note 7.
I am guessing this is an additional precaution taken by Samsung therefore the rooting process needs a very specific set of steps in order to circumnavigate the systems Sammy has put in place. The thread itself says WIP, so I applaud you for your courage.
Nonetheless my suggestion is to instead of waiting for an answer which no one can provide, go to Sammy and bull**** to them that u plugged in the computer and it became a brick.
Theres is no possible senario whereby the internet can help you because we know next to nothing about Note 7.
I sincerely hope that you can come out of the situation with a working Note 7 in your hands whilst not burning a hole in your wallet due to the repairs. God-speed my friend, God-speed.

bill340 said:
I really have no luck here...
Any idea?
Googled already, but did not really find anything besides reinstalling...
Click to expand...
Click to collapse
This seems to be an issue in your drivers, Please uninstall all samsung related and flash box related (if exists) in your PC and try installing it again.
Alternatively, you can just walk into a Samsung Care store and get it done while you wait.

I did that already... No luck. I will try on a different pm next.

Bill sad to see this happened to you
I am exactly coming for the same forum and was following the same steps thought u were, but u took one more step forward and flashed the vitanamese firmware, your phone just messed up there. Was actually about to do the same thing but then read your comments. My phone starts but with errors and has battery drainage , i havent lost anything as it is still virgin and havent transfered anything to it yet. Will wait probably 4 to 5 days more for the official firmwares to release and fire it in.
Sorry to say but u had become the test subject...
---------- Post added at 11:07 AM ---------- Previous post was at 11:03 AM ----------
The recovery mode cannot be accessed, no matter how hard you try
Sent from my SM-N920C using XDA Free mobile app

I just was in the Samsung Care Center in Singapore with my bricked phone.
After 1 hour waiting time, a Samsung guy explained me, that they cannot do anything about it, because they don't have parts ? for this phone in Singapore because it was not launched yet and also there is no international warranty on it.
He had no idea about any software recovery or anything and suggested to get back to Dubai, where I got the phone from.
Really a bad Customerservice experience.
I also want to thank all of you for your great help and suggestions!
I think I will send the phone back to the store in Dubai now.

Well tht will be a good choice
But if u give it three more days and wait for the official firmwares to release would save you some time.
I am still following up with it.
Sent from my SM-N920C using XDA Free mobile app

I really doubt, that this will help, since I cannot flash anything in odin. After initialization I always get the error "FAIL (DeviceInfo)"

bill340 said:
I just was in the Samsung Care Center in Singapore with my bricked phone.
After 1 hour waiting time, a Samsung guy explained me, that they cannot do anything about it, because they don't have parts ? for this phone in Singapore because it was not launched yet and also there is no international warranty on it.
He had no idea about any software recovery or anything and suggested to get back to Dubai, where I got the phone from.
Really a bad Customerservice experience.
I also want to thank all of you for your great help and suggestions!
I think I will send the phone back to the store in Dubai now.
Click to expand...
Click to collapse
Same here in (Dubai) Mate, They don't even have the parts, or Tools to open the device up. If you remember me, I screwed up my Note 7 a week back, Just after two days from launch, and I still didn't receive it. They are still unable to sort it out.
I'm sure when a proper firmware for XSG (Dubai - Same as your device) and a proper ODIN is released to flash the Note 7, this will be a piece of a cake. Just hope for the best, As just like you - I too took a leap of faith and did something stupid.
Anyway, Wishing you luck !

I am not sure if this will help....
What happens when you try a older version of Odin?
Its worked for me in the past, with my s6 edge.