Related
Hi all,
after some time in trials to recover the dead LG G2 D802 it has become true. With help of another member of the xda forum I have succeeded to recover the phone. ... But strange things appear after that. The phone does not want to start from the Power-off/on button. Also I can not enter recovery by pressing VolDown+Power. The only thing I can do is to put in DownloadMode. I mean it react to pressing VolUp and plugging it to the PC. Then I can flash it with LG_Flash_Tool_2014 and after that the phone starts.
Then I am doing all the initial steps of setting the Android and it is working. I am testing the functionality of VolUp and VolDOwn buttons and seems that they are working fine.
If I am not turning the phone OFF all is fine. If I decide to turn it off (by PowerOff) it works a bit strange - when I pres it long it does not give me the options PowerOff, Reboot etc. , but just turn-off the phone.
Then no way to turn it ON again. The only way is to put it in download mode and to flash it again.
If it is powered-off and I put it on the charger it is charging normally and when reach 100% it show the picture on the screen. And that it is.
But no way to power it ON by button.
I hope someone could help with this symptoms.
How was your phone got bricked to go into only qdloader 9008? What were you flasng or what rom were you using?
The phone was bricked during flashing of update. Then I found the tread about No Download No Recovery etc. Via the test point I moved it to qdloader 9008. Then with some help and the program similar (or same I can't exactly remember) like BoardDiag3.99c we managed to upload the main parts from the OS and the soft in case to wake up the phone. Then the phone was able to go in Download Mode and using LG Flash Tool 2014 I have flashed the official FW for it (downloaded on my PC - D80220C_00.kdz). The phone is D802 (aftabalam8c2 asked me to dismount the board and to look on it to verify the model). On the box of the phone is written that it is 16G version 6WT. I checked and seems to be Taiwan version with open soft (no operator locked). Now the phone is working very good except the problem that the button Power OFF is not working. If I press it long it is not coming the menu "Power Off - Resrat - etc." but just the phone is turning off. Then the only thing is is able to do is to go on Download again. No Recovery, No simple turn ON. Then in download I can flash it again and then the soft turn it ON after the flash is done.
I made few trials with different FW for Taiwan/HonkKong (D80220C_00.kdz - 1,62 GB (1*743*288*886 bytes) and Hong Kong D80220C_00.kdz - 1,60 GB (1*723*173*312 bytes)) but the result is always the same.
Also I disconnected and checked the buttons. They are working fine - measured wirh Ohm meter on the connector.
Also I made few trials with another equipment - Octopus Box. It is possible not to flash the whole phone. In Octopus there is an option to read the NVRAM in DOwnload Mode. If I do it the the Octopus Soft after that turns / restarts the phone and it start in normal mode.
Unfortunately this friend does not remember what FW he was trying to flash when he got bricked. One time he told me he was trying to update the FW (OTA) after that he mentioned he was trying to flash another ROM. It was mess done 2,5 months ago, but just last week I was able to pay some attention to his phone.
I assumed it was OTA and downloaded the official FW according to the model, region and the memory.
The only difference was that during the qdloader 9008 mode the phone was flashed with files for (d802 32GB mbn) 32G version. Not 16G.
Regards
Maybe something got fried on the motherboard? Anyway here are the service manuals for G2 (not all model). I hope you could track what goes wrong from the power button with the help of the service manual. https://mega.co.nz/#F!HhhQiSqA!ESK4rT7LJB3MJCRJOU2GhQ
Thank you so much. I see there is a good diagram about the power and the TPs I need to check. Next days when I have a little free time will try to read and check according to the manual. I hope it could be repaired ... but despite my hope my logic whispers me that probably your suggestion is right - something got fried on the board.
If I find something which is reasonable will inform here.
Have a nice day
I have a D800 I'm working on for someone. They did a real number on it. It was semi-functional, but would randomly lose all screen function and had no service. Also had a persistent "ERROR" right above the home keys.
I performed a TOT reset to 20c, and everything seemed fine. I verified functionality and downloaded some apps using my google account, so once everything was fine I performed a standard Factory Reset via Volume - + Home/Home. Now, all hell has broken loose. It retained download mode - for a while - and I was able to flash all 3 available TOT's with semi-success. OS was bootable, sometimes, other times it was pure bootloop. Factory resets performed before and after TOT flashes. Confirmed MD5's, correct TOT+DLL combinations, etc etc. The phone is just pissed. Currently, the IMEI is now gone, but I know it. I wrote it down prior to doing anything the moment I got it. It also matches the IMEI on the inside of the back cover. I have confirmed this is not a frankenstien refurb - D800 on rear of mainboard / all panels / battery ribbon cables / etc. I lost download mode at one point, had fastboot. Couldn't get fastboot mode to work with my pc to repair it, so I manually put the phone into QHUSB 9008 mode, then 9006, then repaired fastboot so Download mode would work. Back to step one....Bootloops, hard freezes, random reboots, "ERROR" during RANDOM boots sometimes no ERROR, etc etc.... Something somewhere is just not meshing. I thought MAYBE the lack of an IMEI might be throwing the OS for a loop, so I tried the qualcomm and EFS Professional programs with no luck. The phone throws an error when trying to backup the memory, as well as write the HEX IMEI. I've tried various ports. Drivers are all current, and I've tried every available version of drivers I've been able to locate.
Anyone have any ideas? At all....? I'm familiar with most of the processes involved here, I just can't figure out how a full TOT reflash isn't wiping the issue...
Sorry, meant to put in Troubleshooting. Apologies!
adamlee06 said:
I have a D800 I'm working on for someone. They did a real number on it. It was semi-functional, but would randomly lose all screen function and had no service. Also had a persistent "ERROR" right above the home keys.
I performed a TOT reset to 20c, and everything seemed fine. I verified functionality and downloaded some apps using my google account, so once everything was fine I performed a standard Factory Reset via Volume - + Home/Home. Now, all hell has broken loose. It retained download mode - for a while - and I was able to flash all 3 available TOT's with semi-success. OS was bootable, sometimes, other times it was pure bootloop. Factory resets performed before and after TOT flashes. Confirmed MD5's, correct TOT+DLL combinations, etc etc. The phone is just pissed. Currently, the IMEI is now gone, but I know it. I wrote it down prior to doing anything the moment I got it. It also matches the IMEI on the inside of the back cover. I have confirmed this is not a frankenstien refurb - D800 on rear of mainboard / all panels / battery ribbon cables / etc. I lost download mode at one point, had fastboot. Couldn't get fastboot mode to work with my pc to repair it, so I manually put the phone into QHUSB 9008 mode, then 9006, then repaired fastboot so Download mode would work. Back to step one....Bootloops, hard freezes, random reboots, "ERROR" during RANDOM boots sometimes no ERROR, etc etc.... Something somewhere is just not meshing. I thought MAYBE the lack of an IMEI might be throwing the OS for a loop, so I tried the qualcomm and EFS Professional programs with no luck. The phone throws an error when trying to backup the memory, as well as write the HEX IMEI. I've tried various ports. Drivers are all current, and I've tried every available version of drivers I've been able to locate.
Anyone have any ideas? At all....? I'm familiar with most of the processes involved here, I just can't figure out how a full TOT reflash isn't wiping the issue...
Click to expand...
Click to collapse
baseband is known or unknown.
kalpesh patil said:
baseband is known or unknown.
Click to expand...
Click to collapse
Unknown. I just PMd you as well, but my XDA PMs havent been sending all week. Maybe you're went through
I have a D800 I'm working on for someone. They did a real number on it. It was semi-functional, but would randomly lose all screen function and had no service. Also had a persistent "ERROR" right above the home keys.
I performed a TOT reset to 20c, and everything seemed fine. I verified functionality and downloaded some apps using my google account, so once everything was fine I performed a standard Factory Reset via Volume - + Home/Home. Now, all hell has broken loose. It retained download mode - for a while - and I was able to flash all 3 available TOT's with semi-success. OS was bootable, sometimes, other times it was pure bootloop. Factory resets performed before and after TOT flashes. Confirmed MD5's, correct TOT+DLL combinations, etc etc. The phone is just pissed. Currently, the IMEI is now gone, but I know it. I wrote it down prior to doing anything the moment I got it. It also matches the IMEI on the inside of the back cover. I have confirmed this is not a frankenstien refurb - D800 on rear of mainboard / all panels / battery ribbon cables / etc. I lost download mode at one point, had fastboot. Couldn't get fastboot mode to work with my pc to repair it, so I manually put the phone into QHUSB 9008 mode, then 9006, then repaired fastboot so Download mode would work. Back to step one....Bootloops, hard freezes, random reboots, "ERROR" during RANDOM boots sometimes no ERROR, etc etc.... Something somewhere is just not meshing. I thought MAYBE the lack of an IMEI might be throwing the OS for a loop, so I tried the qualcomm and EFS Professional programs with no luck. The phone throws an error when trying to backup the memory, as well as write the HEX IMEI. I've tried various ports. Drivers are all current, and I've tried every available version of drivers I've been able to locate.
Anyone have any ideas? At all....? I'm familiar with most of the processes involved here, I just can't figure out how a full TOT reflash isn't wiping the issue...
Imgur Album of components to confirm full D800: http://imgur.com/a/PciLM
EDIT: BASEBAND UNKNOWN
How to unbrinck an SM-J510MN using another one that is working to get the files needed for odin.
Does having a working device help me?
When I try to use odin I get the message "Volume Size is Too big"
Thanks
Gianlucas94 said:
How to unbrinck an SM-J510MN using another one that is working to get the files needed for odin.
Does having a working device help me?
When I try to use odin I get the message "Volume Size is Too big"
Thanks
Click to expand...
Click to collapse
Wrong firmware.
I had my original SM-J510MN bricked last night because I tried to install a corrupt or incompatible TWRP image on it, so, in the way all through the hell I did the following:
1. There is no information on Google about this exact machine (MSM8960).
2. I messed up with SmartSwitch PC Software piece of junk by reinstalling the driver which never worked, provided by its own SmartSwitch option menu.
3. That driver installed before was never going to work because you have to boot Windows 7 in a way to avoid signed drivers checking (Pressing F8 at boot).
4. After research I found out that I had to downgrade the SmartSwitch version to a one with the enabled tab "Device initialization".
5. Finally, I had the driver and a correct SmartSwitch version just to realize I had to type the Model name of my device in UPPERCASE because those Samsung engineers didn't realize a normal user may be would type in lowercase ().
6. I typed the S/N (serial number) located on the backside of the phone and I got the message "Please check the model name and S/N, and enter them again". I triple checked the inserted values, to this point I was feeling I'm totally lost.
7. I downloaded at least 10 Gibibytes (Gigabytes but in the right terms) in stock ROMs which none of them worked for multiple and different reasons.
So this beautiful COVID-19 lockdown morning I woke up inspired thanks Jehovah God and I just tried the old way to inspect this whole site by using Google like this: "site:xda-developers.com j510mn" and I found a compatible fully working TWRP that I flashed using Odin v3.14.1 and then the phone booted normally.
While I was looking for a custom ROM then I didn't realize the WiFi stopped working so I am looking for a solution.
2020-06-06
To bring the Wi-Fi back to my device I had to flash LineageOS 14.1, and then you will be able to flash any custom ROM you may find.
I hope this helps, greetings from Colombia.
akira_yuki said:
I had my original SM-J510MN bricked last night because I tried to install an incompatible TWRP on it (wrong device with similar name), so, in the way all through the hell I did the following:
1. There is no information in Google about this exact machine (MSM8960).
2. I messed up with SmartSwitch PC Software piece of junk by reinstalling the driver which never worked, provided by its own SmartSwitch option menu.
3. That driver installed before was never going to work because you have to boot Windows 7 in a way to avoid signed drivers checking (Pressing F8 at boot).
4. After a research I found out that I had to downgrade the SmartSwitch version to a one with the enabled tab "Device initialization".
5. Finally I had the driver and a correct SmartSwitch version just to realize I had to type the Model name of my device in UPPERCASE because those Samsung engineers didn't realize a normal user may be would type in lowercase ().
6. I typed the S/N (serial number) located on the backside of the phone and I got the message "Please check the model name and S/N, and enter them again". I triple checked the inserted values, to this point I was feeling I'm totally lost.
7. I downloaded at least 10 Gibibytes (Gigabytes but in the right terms) in stock roms which none of them worked for multiple and different reasons.
So this beautiful COVID-19 lockdown morning I woke up inspired thanks Jehovah God and I just tried the old way to inspect this whole site by using Google like this: "site:xda-developers.com j510mn" and I found a compatible fully working TWRP that I flashed using Odin v3.14.1
I hope this helps, greetings from Colombia.
Click to expand...
Click to collapse
When you open your device hold power button + Down volume + home button and flash the stock ROM, its a soft brick, not hard brick. J510MN is fully compatible with every version of TWRP.
NecromancerViper said:
When you open your device hold power button + Down volume + home button and flash the stock ROM, its a soft brick, not hard brick. J510MN is fully compatible with every version of TWRP.
Click to expand...
Click to collapse
OK, sorry for not having been that explicit, but I'm going to be right now:
Last night I had a useless phone...
satisfied?
does your correction help in any way? does that help with the initial post at all? is there any difference between hard and soft bricked that could help on that?
akira_yuki said:
OK, sorry for not having been that explicit, but I'm going to be right now:
Last night I had a useless phone...
satisfied?
does your correction help in any way? does that help with the initial post at all? is there any difference between hard and soft bricked that could help on that?
Click to expand...
Click to collapse
I mean, 3.2 and 3.3 versions of TWRP support MN
Samsung S10 + SM-F975F/DS IMEI stating Taiwan (Update: Very contradicting information if the phone is Snapdragon OR Exynos) if it even matters to solve the issue I dont know
Owner of the above since 2019 without issues; USB debugging mode activated in 2019 and never changed since then.
Samsung always updated which I assume the UI 3 Android got updated in January of my vague memory/recollection (honestly never paid attention of what is being updated, only that the phone needs to be on charge while doing ANY update)
Issue: phone in constant bootloop every 4 minutes with top message in red color "ERASE FAIL: READ ONLY" see photo attached
Cause: happened 4 days ago: Watched video stream on chrome browser; phone froze and applied a 10sec. power shut off (never had to do that before, 1st time)
Investigation:
I tried (found out by doing so) to interrupt the bootloop with pressing Power button and same time Volume Down Button in order to restart it and follow the following commands found on the internet as per UI 3 update:
Recovery Mode as followed does nothing:
Hold the Power button of your device till the power menu pops up and select Power Off. = does not apply as in bootloop
Wait for your device to turn off completely. = it does never turn off completely UNLESS I press Power button and same time Volume Down Button und plug into USB C Data cable of which the charging circle with the lightening strike appears without any percentage % of which photo is attached (phone charge can keep up with its bootloop in order to avoid battery drainage as there is no % indication)
Plug-in a USB-C data cable connected to your PC or USB-C earphones in your device. = I start from here whenever the phone restarts every 4 minutes or whenever I do it manually by pressing the buttons as I described in point 2.
Now, check if your device has a Bixby Button (Such as Galaxy S10/Note10):
Without Bixby Button: Press Volume Up + Power Button for a few seconds.
With Bixby Button: Press Volume Up + Bixby Button + Power Button for a few seconds
After the above steps, you will boot into Recovery mode.
Download Mode as followed does nothing: IT DOES WORK NOW you need to be very fast before the phone starts (recovery mode does not work)
Make sure you have a USB cable connected to the computer
Then press and hold the Volume Down and Bixby buttons at the same time
Continue holding these two buttons down while you insert the USB cable that is connected to the PC
Recovery Mode before update instructions as followed does nothing:
Step 1: Start by turning off your Galaxy S10.
Step 2: After it’s powered down, press and hold Volume Up button and Bixby button (this is the button underneath the volume buttons in case you didn’t know).
Step 3: Without letting go of the Volume Up and Bixby buttons, press and hold the Power button.
Step 4: As soon as your device turns on, let go of the Power button.
Step 5: After you see a blue screen, let go of the remaining two buttons. Now you are in Recovery mode.
Download Mode before update instructions as followed does nothing:
Step 1: Turn off your Galaxy S10.
Step 2: When it’s turned off, press and hold the Volume Down button and Bixby button.
Step 3: Without letting go of the two buttons, press and hold the Power button.
Step 4: You will get into Download Mode.
Have tried all the above methods several times the past 4 days.
Have drained the battery in terms of keeping the phone in bootloop resulting in no power.
Unhooked the battery by means of removing the rear panel and unhooking the battery cable for more then 15minutes and repeat the 4 different methods
Unhooked the mainboard from various connections and put together and repeat the 4 different methods
No indications in Windows 10 Device manager
Questions, doubts and thoughts:
Is it possible in this state to access with ADB of a professional in order to perhaps clear the cache, resolve the issue without having access to recovery mode?
Should I simply try to purchase a new battery even though I never had any battery issues?
I am aware that a motherboard change will resolve it to the cheapest way possible but as I like to save the data such as different accounts this is not an option besides the phone is physically in good condition (never went under water or dropped). maybe to unsolder the flash memory onto a new mainboard as recovery mode might be part of the processor where the RAM is saved.
Any way to drain the entire phone further which may resolve the issue without loosing data. Similar in removing a CMOS battery on a PC mainboard and using a jumper.
Willing to pay and currently living in Europe.
UPDATE: Odin firmware performed by skilled professional member of xda forum, but still not working. EMMC issue which needs to be addressed with ISP in order to fix the issue. unfortunately I was told by local professionals that they do not have the tools for it. Therefor I wonder if someone knows someone who knows someone who can be of help. Location is Spain but Europe would also work.
UPDATE2: Got the phone back from technician who has experience with ISP but still same Error remains as to his conclusion that this is not an Exynos phone of which he has not the hardware tool to fix it and probably no one in Europe will have it.
Thank you very much in advance
Sorry... my english not so good...
so the point is whether you can enter recovery or download mode or not ?
Vuska said:
Sorry... my english not so good...
so the point is whether you can enter recovery or download mode or not ?
Click to expand...
Click to collapse
I am able now to enter download mode.
snakebite3 said:
I am able now to enter download mode.
Click to expand...
Click to collapse
and do you able to flash stock again ? (newest one, because we cant downgrade the bootloader)...
Vuska said:
and do you able to flash stock again ? (newest one, because we cant downgrade the bootloader)...
Click to expand...
Click to collapse
Thank you for following up.
these ones were tried out:
Samfw.com_SM-G975F_DBT_G975FXXS9DTI8_fac
Samfw.com_SM-G975F_DBT_G975FXXU9FUCD_fac
Samfw.com_SM-G975F_XSG_G975FXXU9FUBD_fac
I am not sure but that person who helped me remotely may explain better
According to technician its Qualcomm Snapdragon which can only be fixed with the right tools. Not in europe.
I been getting different information and do require some expertise if someone can please help me
any further advice, input or suggestion?
I also Own Samsung S10+.
its showing the same thing.
tried Flashing Via Odin it failed.
Tried to enter Recovery Mode but also failed to enter recovery mode.
OMG. I thought I was the only one in the world. I sent it yesterday to a data recovery technician to see what they will do since according to some insider in order to recover the data they would have to access the phone and fix the boot of which the problem get solved itself since they can not remove the memory chip itself as it would get ruined. They will diagnose the problem first before they do anything. Obviously a mainboard change would be the easiest but thats not an option.
Was your phone also updated to UI Android 3.0?
How did it happen if I may ask?
I wont give up since my phone is physically totally fine.
Update from a data recovery company its communication:
What we tried to do in order to recover your device's data was to load through the phone's bootloader (in Download Mode) a software agent that allows us (in some cases) to transfer the data stored in the data partition. This software agent has been developed by us together with some of our partners and as we are sure you will understand we cannot give you more details about what this particular software does or how it does it, since this information is covered by professional and business secrecy.
In this case the phone's firmware was damaged to a degree that made it impossible for the information to be accessed with this software.
At this moment, we doubt the data could be recovered by any software available now in the market. That's our opinion, but you can of course send it to other companies to see if they can recover it.
Since I am not the only one anymore with the same issue I recommend for people to come forward in order to get help
So far there is a tool needed to reprogram EMMC but I dont know which tool neither do I know where to find that person with this knowledge
snakebite3 said:
So far there is a tool needed to reprogram EMMC but I dont know which tool neither do I know where to find that person with this knowledge
Click to expand...
Click to collapse
Your device is powered by Snapdragon or Exynos?
LinhBT said:
Your device is powered by Snapdragon or Exynos?
Click to expand...
Click to collapse
I honestly dont know anymore since numerous people said contradicting things.
I am under the impression it is Exynos as of the research of the model SM-G975F/DS
Need to know exactly if it's Snap or not. If it is, then there're 2 options you can try.
1. Ask some one have the same device model as you, do a ROM dump ( you can google for more detail ). Once you got that, I can share with you the tool needed for restore your device from that dump.
2. Try find your device's Factory Images ( similar to Fastboot ROM, but a little different ), and an authenticated prog of your SoC ( this I can share too if you choose this option ) then boot your device into EDL mode by using fastboot2EDL script ( on Git, you can google too ) then use QFIL ( one tool in QPST Tools by Qualcomm ) and force flash the images into the device.
So far as my experience and understanding, there're only these 2 solutions to fix your device ( if it's Snap powered ).
According to the seller: "The phone is Taiwanese version and CPU should be Exynos 9820"
Maybe someone can help me please.. still
If its Exynos powered, then I have no solution for it. Sorry bro!!!
LinhBT said:
If its Exynos powered, then I have no solution for it. Sorry bro!!!
Click to expand...
Click to collapse
Thank you for your reply.
Can you please explain me why and who I should be looking for.
Anyone has knowledge how to fix this issue, please? USA based
LinhBT said:
Need to know exactly if it's Snap or not. If it is, then there're 2 options you can try.
1. Ask some one have the same device model as you, do a ROM dump ( you can google for more detail ). Once you got that, I can share with you the tool needed for restore your device from that dump.
2. Try find your device's Factory Images ( similar to Fastboot ROM, but a little different ), and an authenticated prog of your SoC ( this I can share too if you choose this option ) then boot your device into EDL mode by using fastboot2EDL script ( on Git, you can google too ) then use QFIL ( one tool in QPST Tools by Qualcomm ) and force flash the images into the device.
So far as my experience and understanding, there're only these 2 solutions to fix your device ( if it's Snap powered ).
Click to expand...
Click to collapse
Hi mate, My phone is Snapdragon powered..
My problem is almost similar.. But not exactly.. After almost 2 months I am not able to find a solution.. But after this period of researching and googling about things related to my problem.. I feel now, either any one of the following is the cause of problem:
1. Emmc is stuck or locked in read-only mode `(Can move files from pc , delete already present files anywhere in any directory, but all changes vanish after reboot... all file and directory structure remain intact- moved files from pc gets deleted.. and deleted files which were already present come back after reboot )
2. Corrupted /data and /cache partition, as e2fsck in twrp terminal results shows "filesystem still has errors" and "e2fsck: unable to set superblock flags on /dev/block/mmcblk0p** ) in both these file system (I think they are preventing flashing procedures- Odin stock firmware flashes and twrp custom ROM flashes both are successful, but after reboot no changes can be seen... - Even Recovery.img and boot.img flashes don't seem to work even both are shown successfully flashed in twrp) After reboot current version twrp boots again instead of newly flashed different version recovery.img ... same with boot.img even after running magisk uninstaller zip files.. running uninstall.zip 2nd or 3rd time also shows magisk patched image detected in log which should be removed in 1st iteration itself..
3. Might be magisk is preventing these changes to be made.. or It might be the /System_root creation as mountpoint for system partition which used to be previously /system normally. This might be the superblock creation which not used to be there
My Samsung's twrp and Download Mode seems to be working but no changes made by them even after successful operations by both.
Can you suggest anything? You can look my thread as to get even more detailed overview of what's happening and whatever I'have tried here - https://forum.xda-developers.com/t/...t-not-changing-anything-after-reboot.4462639/
You can see my attachments in my above thread to see my directory structure of system_root and my download mode pictures and odin system ROM flash pictures.
LinhBT said:
Need to know exactly if it's Snap or not. If it is, then there're 2 options you can try.
1. Ask some one have the same device model as you, do a ROM dump ( you can google for more detail ). Once you got that, I can share with you the tool needed for restore your device from that dump.
2. Try find your device's Factory Images ( similar to Fastboot ROM, but a little different ), and an authenticated prog of your SoC ( this I can share too if you choose this option ) then boot your device into EDL mode by using fastboot2EDL script ( on Git, you can google too ) then use QFIL ( one tool in QPST Tools by Qualcomm ) and force flash the images into the device.
So far as my experience and understanding, there're only these 2 solutions to fix your device ( if it's Snap powered ).
Click to expand...
Click to collapse
any tips here?
S20 FE bootloop after security update
So I never posted here but I usually pass by some topics so sorry for any mistake in creating this discussion. Today I deleted some stuff from my S20 FE and downloaded via OTA the march security update in my device, then I was caught by surprise...
forum.xda-developers.com